Searched refs:issue (Results 1 – 25 of 158) sorted by relevance
1234567
| /Zephyr-latest/scripts/ |
| D | dump_bugs_pickle.py | 25 def issue_has_label(issue: Issue, label: str) -> bool:
26 for lbl in issue.labels:
31 def is_open_bug(issue: Issue) -> bool:
32 return (issue.pull_request is None and
33 issue.state == 'open' and
34 issue_has_label(issue, 'bug'))
39 return [issue for issue in pickle.load(f) if
40 is_open_bug(issue)]
|
| D | make_bugs_pickle.py | 56 open_bugs = [issue for issue in get_open_bugs() if not issue.pull_request]
|
| D | set_assignees.py | 237 issue = gh_repo.get_issue(number)
241 if issue.assignees:
266 for label in issue.labels:
283 issue.add_to_assignees(maintainer)
319 for issue in issues:
320 pull = issue.as_pull_request()
357 elif args.issue:
358 process_issue(gh, maintainer_file, args.issue)
371 for issue in pulls:
372 process_pr(gh, maintainer_file, issue.number)
|
| D | valgrind.supp | 2 getpwuid() libC issue
|
| /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/security/ |
| D | reporting.rst | 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
73 - Public: The embargo period has ended. The issue will be made
[all …]
|
| /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 | 68 Any change that is a fix to an issue that blocks developers from doing their
182 to questions and provide clarifications regarding the issue or the change.
251 This saves us all time when searching, reduces the chances of the PR or issue
252 being forgotten, speeds up reviewing, avoids duplicate issue reports, etc.
288 - This issue is a duplicate of another issue (please specify).
290 * - :guilabel:`Good first issue`
297 Any issue must be classified and labeled as either *Bug*, *Enhancement*, *RFC*,
305 The issue or PR describes a change to a stable API.
314 - Fix for an issue blocking development.
364 - An issue or PR which affects only a particular platform.
[all …]
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-1.10.rst | 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…
360 * :github:`4036` - Coverity issue seen with CID: 175360 , in file: /subsys/bluetooth/host/mesh/prov…
361 * :github:`4037` - Coverity issue seen with CID: 175359 , in file: /subsys/bluetooth/host/hci_core.c
362 * :github:`4038` - Coverity issue seen with CID: 175358 , in file: /subsys/bluetooth/host/hci_core.c
[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/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/soc/nuvoton/npcx/npcx9/ |
| D | Kconfig | 21 Workaround the issue "Possible Hang-Up After VCC1_RST Reset"
|
| /Zephyr-latest/soc/nxp/rw/ |
| D | firmwares.ld | 11 * issue, so add a padding of one word */
|
| /Zephyr-latest/drivers/interrupt_controller/ |
| D | Kconfig.npcx | 19 Workaround the issue "MIWU Any Edge Trigger Condition"
|
| /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/scripts/release/ |
| D | list_backports.py | 237 issue = self._repo.get_issue(issue_number)
238 if not issue:
248 issues_for_this_pr[issue_number] = issue
|
| /Zephyr-latest/doc/services/llext/ |
| D | load.rst | 89 If any of this happens, the following tips may help understand the issue:
98 the issue.
103 If the issue persists, please open an issue in the GitHub repository, including
|
| /Zephyr-latest/doc/develop/west/ |
| D | troubleshooting.rst | 99 west issue 373`_ for details. Some versions of **Ubuntu** and **Linux Mint** are known to
102 Neither macOS nor Windows users have reported this issue. There have been no
103 reports of this issue on other Linux distributions, like Arch Linux, either.
105 .. _this comment in west issue 373:
193 The easiest way to resolve this issue is to upgrade west and retry as follows:
223 To resolve this issue, unset :envvar:`ZEPHYR_BASE` and try again.
|
| /Zephyr-latest/doc/contribute/ |
| D | proposals_and_rfcs.rst | 36 For a Major Feature, first open an issue and outline your proposal so that it
40 will increase the chances of your issue being dealt with quickly:
57 The process in itself consists in creating a GitHub issue with the :ref:`RFC
|
| 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
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/subsys/rtio/ |
| D | Kconfig.workq | 34 to issue, the bigger this pool should be.
|
| /Zephyr-latest/cmake/ |
| D | extra_flags.cmake | 4 # Note: zephyr_get MERGE should not be used until issue #43959 is resolved.
|
| /Zephyr-latest/dts/arm/nxp/ |
| D | nxp_k8xfn256vxx15.dtsi | 15 * someone to extend sram0 without solving this issue, we define two
|
| D | nxp_ke1xf256vlx16.dtsi | 15 * someone to extend sram0 without solving this issue, we define two
|
1234567
