| /Zephyr-latest/scripts/ |
| D | dump_bugs_pickle.py | 14 from github.Issue import Issue
25 def issue_has_label(issue: Issue, label: str) -> bool: argument
26 for lbl in issue.labels:
31 def is_open_bug(issue: Issue) -> bool: argument
32 return (issue.pull_request is None and
33 issue.state == 'open' and
34 issue_has_label(issue, 'bug'))
36 def get_bugs(args: argparse.Namespace) -> List[Issue]:
39 return [issue for issue in pickle.load(f) if
40 is_open_bug(issue)]
|
| D | make_bugs_pickle.py | 15 from github.Issue import Issue
29 them to a new pickle file as a list of github.Issue.Issue objects.
34 - github.Issue.Issue:
35 https://pygithub.readthedocs.io/en/latest/github_objects/Issue.html
44 def get_open_bugs() -> List[Issue]:
56 open_bugs = [issue for issue in get_open_bugs() if not issue.pull_request]
|
| D | set_assignees.py | 37 group.add_argument("-I", "--issue", required=False, default=None, type=int,
38 help="Operate on one issue only.")
237 issue = gh_repo.get_issue(number)
239 log(f"Working on {issue.url}: {issue.title}")
241 if issue.assignees:
242 print(f"Already assigned {issue.assignees}, bailing out")
266 for label in issue.labels:
281 log(f"Adding {maintainer} to {issue.html_url}")
283 issue.add_to_assignees(maintainer)
319 for issue in issues:
[all …]
|
| /Zephyr-latest/doc/security/ |
| D | reporting.rst | 18 Security Issue Management
54 response to an email, the issue shall be transitioned directly to
57 - Triage: This issue is awaiting Triage by the response team. The
58 response team will analyze the issue, determine a responsible
60 issue to the Assigned state. Part of triage will be to set the
61 issue's priority.
63 - Assigned: The issue has been assigned, and is awaiting a fix by the
66 - Review: Once there is a Zephyr pull request for the issue, the PR
67 link will be added to a comment in the issue, and the issue moved to
70 - Accepted: Indicates that this issue has been merged into the
[all …]
|
| D | secure-coding.rst | 128 request in the issue tracker. Commits without a valid reference
252 The Zephyr project shall have an issue tracking system (such as GitHub_)
258 Because security issues are often sensitive, this issue tracking
259 system shall have a field to indicate a security issue. Setting this
260 field shall result in the issue only being visible to the Zephyr Security
263 have visibility to a given issue.
269 The time necessary shall be clearly annotated in the issue itself.
275 issue. The embargo should **not** be lifted via an automated means, but
|
| /Zephyr-latest/.github/workflows/ |
| D | stale_issue.yml | 18 stale-issue-message: 'This issue has been marked as stale because it has been open (more
20 would like to have the label removed otherwise this issue will automatically be closed in
21 14 days. Note, that you can always re-open a closed issue at any time.'
24 stale-issue-label: 'Stale'
27 … exempt-issue-labels: 'In progress,Enhancement,Feature,Feature Request,RFC,Meta,Process,Coverity'
|
| D | backport_issue_check.yml | 1 name: Backport Issue Check
15 name: Backport Issue Check
17 group: backport-issue-check-${{ github.ref }}
30 - name: Run backport issue checker
|
| D | greet_first_time_contributor.yml | 20 issue-message: >
21 Hi @${{github.event.issue.user.login}}! We appreciate you submitting your first issue
|
| D | issue_count.yml | 1 name: Issue Tracker
16 name: "Collect Issue Stats"
|
| /Zephyr-latest/.github/ISSUE_TEMPLATE/ |
| D | 001_bug_report.md | 12 are available to first verify that the issue is a genuine Zephyr bug and not a
15 This issue list is only for bugs in the main Zephyr code base
17 fork (such as NCS) specific feature, please open an issue in the fork project
28 - What have you tried to diagnose or workaround this issue?
50 What impact does this issue have on your progress (e.g., annoyance, showstopper)
58 explain the issue. (if unable to obtain text log, add a screenshot)
69 Add any other context that could be relevant to your issue, such as pin setting,
|
| /Zephyr-latest/doc/project/ |
| D | issues.rst | 9 Any changes that originate from a tracked feature or issue should contain a
10 reference to the feature by mentioning the corresponding issue or pull-request
16 Reporting a regression issue
19 It could happen that the issue being reported is identified as a regression,
|
| D | dev_env_and_tools.rst | 70 Any change that is a fix to an issue that blocks developers from doing their
192 to questions and provide clarifications regarding the issue or the change.
261 This saves us all time when searching, reduces the chances of the PR or issue
262 being forgotten, speeds up reviewing, avoids duplicate issue reports, etc.
279 Note: Issue priorities are generally set or changed during the bug-triage or TSC
298 - This issue is a duplicate of another issue (please specify).
300 * - :guilabel:`Good first issue`
307 Any issue must be classified and labeled as either *Bug*, *Enhancement*, *RFC*,
315 The issue or PR describes a change to a stable API.
324 - Fix for an issue blocking development.
[all …]
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-1.10.rst | 197 Issue Related Items
203 .. comment List derived from Jira/GitHub Issue query: ...
211 * :github:`1270` - Issue : Information CC3220SF LaunchXL
257 * :github:`2035` - doc: remove workaround for sphinx issue once 1.5 is released
354 * :github:`4030` - Coverity issue seen with CID: 175366 , in file: /subsys/bluetooth/host/smp.c
355 * :github:`4031` - Coverity issue seen with CID: 175365 , in file: /subsys/bluetooth/controller/hci…
356 * :github:`4032` - Coverity issue seen with CID: 175364 , in file: /subsys/bluetooth/host/mesh/prox…
357 * :github:`4033` - Coverity issue seen with CID: 175363 , in file: /subsys/bluetooth/host/smp.c
358 * :github:`4034` - Coverity issue seen with CID: 175362 , in file: /subsys/bluetooth/host/smp.c
359 * :github:`4035` - Coverity issue seen with CID: 175361 , in file: /samples/bluetooth/eddystone/src…
[all …]
|
| D | release-notes-1.9.rst | 29 * STM32 PWM prescaler issue fixed
358 * ``ZEP-2523`` - Static code scan (Coverity) issue seen in file: /samples/net/zoap_server/src/zoap-…
359 * ``ZEP-2525`` - Static code scan (Coverity) issue seen in file: /samples/net/zoap_server/src/zoap-…
360 * ``ZEP-2531`` - Static code scan (Coverity) issue seen in file: /tests/net/lib/dns_resolve/src/mai…
361 * ``ZEP-2528`` - Static code scan (Coverity) issue seen in file: /samples/net/nats/src/nats.c
362 * ``ZEP-2534`` - Static code scan (Coverity) issue seen in file: /tests/kernel/irq_offload/src/irq_…
363 * ``ZEP-2535`` - Static code scan (Coverity) issue seen in file: /tests/net/lib/zoap/src/main.c
364 * ``ZEP-2537`` - Static code scan (Coverity) issue seen in file: /tests/crypto/ecc_dh/src/ecc_dh.c
365 * ``ZEP-2538`` - Static code scan (Coverity) issue seen in file: /arch/arm/soc/st_stm32/stm32f1/soc…
366 * ``ZEP-2539`` - Static code scan (Coverity) issue seen in file: /tests/net/ieee802154/l2/src/ieee8…
[all …]
|
| /Zephyr-latest/dts/bindings/dsa/ |
| D | microchip,ksz8794.yaml | 17 0x02: 1) CAT-5E/6 Short Cable with a Link Issue for the KSZ8795 Family
18 0x04: 2) CAT-5E/6 Short Cable with a Link Issue for the KSZ8795 Family
|
| /Zephyr-latest/doc/develop/api/ |
| D | api_lifecycle.rst | 136 #. An :ref:`RFC issue <rfcs>` must be opened on GitHub with the following
154 Instead of a written description of the changes, the RFC issue may link to a
156 #. The RFC issue must be labeled with the GitHub ``Breaking API Change`` label
157 #. The RFC issue must be submitted for discussion in the next `Zephyr
160 to the RFC issue title and that links to the RFC issue
162 The RFC will then receive feedback through issue comments and will also be
173 - A title that matches the RFC issue
174 - A link to the RFC issue
240 `GitHub issue <https://github.com/zephyrproject-rtos/zephyr/labels/deprecation_tracker>`_
|
| /Zephyr-latest/doc/_extensions/zephyr/ |
| D | gh_utils.py | 15 of pages, direct links to open a GitHub issue regarding a page, or date of the most recent commit
22 * ``gh_link_get_open_issue_url``: Returns a URL to open a new issue regarding the given page.
120 """Link to open a new Github issue regarding "pagename" with title, body, and
128 URL to open a new issue if applicable, None otherwise.
141 title = quote(f"doc: Documentation issue in '{pagename}'")
151 << Please describe the issue here >>
152 << You may also want to update the automatically generated issue title above. >>
|
| /Zephyr-latest/doc/contribute/ |
| D | bin_blobs.rst | 90 - The Zephyr build system, during its configuration phase, will issue a warning.
203 without investigation. For example, the issue may be exposing a bug in a Zephyr
208 able to determine if a given issue is due to a bug in Zephyr or the blob itself,
211 Blobs must have designated maintainers that must be responsive to issue reports
238 issue in the Zephyr project issue tracking system on GitHub with details
246 #. Use the :github:`New Binary Blobs Issue
247 <new?assignees=&labels=RFC&template=008_bin-blobs.md&title=>` to open an issue
251 link to it from the issue
253 GitHub issue comments
|
| /Zephyr-latest/dts/bindings/fpga/ |
| D | lattice,ice40-fpga-base.yaml | 42 Prior to sending the bitstream, issue this number of leading clocks with SPI_CS pulled high.
48 After sending the bitstream, issue this number of trailing clocks with SPI_CS pulled high.
|
| /Zephyr-latest/include/zephyr/linker/ |
| D | app_smem.ld | 12 * issue:
29 * Note: Ninja generator does not suffer from this issue.
|
| D | app_smem_pinned.ld | 16 * issue:
33 * Note: Ninja generator does not suffer from this issue.
|
| /Zephyr-latest/doc/develop/getting_started/ |
| D | installation_win.rst | 17 Windows 10 version 1803 has an issue that will cause CMake to not work
19 More information can be found in :github:`Zephyr Issue 10420 <10420>`.
|
| /Zephyr-latest/samples/drivers/video/capture/boards/ |
| D | frdm_mcxn947_cpu0.conf | 3 # Workaround for issue where SDMA driver needs to start before camera, so that
|
| /Zephyr-latest/tests/kernel/interrupt/src/ |
| D | regular_isr.c | 96 /* QEMU seems to have an issue in that interrupts seem to post on in ZTEST()
98 * can cause an issue if the instruction after the 'sti' ends up looking in ZTEST()
105 * See GitHub issue zephyrproject-rtos/sdk-ng#629 for the qemu bug. in ZTEST()
|
| /Zephyr-latest/doc/services/llext/ |
| D | load.rst | 85 If any of this happens, the following tips may help understand the issue:
94 the issue.
105 If the issue persists, please open an issue in the GitHub repository, including
|
