Searched full:bug (Results 1 – 25 of 149) sorted by relevance
123456
/Zephyr-latest/scripts/ |
D | dump_bugs_pickle.py | 34 issue_has_label(issue, 'bug')) 45 for bug in sorted(bugs, key=lambda bug: bug.number): 46 title = bug.title.strip() 47 print(f'- :github:`{bug.number}` - {title}')
|
D | requirements-extras.txt | 24 # used by scripts/release/bug_bash.py for generating top ten bug squashers
|
/Zephyr-latest/.github/ISSUE_TEMPLATE/ |
D | 001_bug_report.md | 2 name: Bug report 5 labels: bug 12 are available to first verify that the issue is a genuine Zephyr bug and not a 16 (https://github.com/zephyrproject-rtos/zephyr/). If the bug is for a project 21 **Describe the bug** 23 A clear and concise description of what the bug is.
|
/Zephyr-latest/.github/workflows/ |
D | issues-report-config.json | 4 "labels": ["bug", "priority: high"], 9 "labels": ["bug", "priority: medium"], 14 "labels": ["bug", "priority: low"],
|
D | bug_snapshot.yaml | 7 name: Bug Snapshot 57 PUBLISH_ROOT="${REPOSITORY_NAME}/bug-snapshot/daily" 59 PUBLISH_ROOT="${REPOSITORY_NAME}/bug-snapshot" 66 echo "Bug pickle is available at: ${PUBLISH_DOWNLOAD_URI}" >> ${GITHUB_STEP_SUMMARY}
|
/Zephyr-latest/doc/security/ |
D | vulnerabilities.rst | 22 - `Zephyr project bug tracker ZEPSEC-12 40 - `Zephyr project bug tracker ZEPSEC-17 59 - `Zephyr project bug tracker ZEPSEC-18 77 - `Zephyr project bug tracker ZEPSEC-20 97 - `Zephyr project bug tracker ZEPSEC-25 121 - `Zephyr project bug tracker ZEPSEC-26 148 - `Zephyr project bug tracker ZEPSEC-28 176 - `Zephyr project bug tracker ZEPSEC-29 204 - `Zephyr project bug tracker ZEPSEC-30 230 - `Zephyr project bug tracker ZEPSEC-35 [all …]
|
/Zephyr-latest/doc/project/ |
D | issues.rst | 3 Bug Reporting 21 In this case, providing directly the guilty commit when submitting the bug 22 gains a lot of time in the eventual bug fixing.
|
D | release_process.rst | 26 changes such as bug fixes and documentation will be merged unless granted a 76 cosmetic changes, tests, bug and doc fixes are allowed (See :ref:`table 125 Blocker bug process kicks in during the release process and is in effect after the 130 A fix for a bug that is granted ``blocker`` status can be merged to 'main' and included in 140 the bug present. 176 - No new features after RC1, ONLY stabilization and cosmetic changes, bug and doc 181 …- No new features after RC2, ONLY stabilization and cosmetic changes, bug and doc fixes are allowe… 185 - Only blocker bug fixes after RC3, documentation and changes to release notes are allowed. 235 - **Extended Stabilisation period**: Allow for more testing and bug fixing 246 support and maintenance which includes general stability and bug fixes, [all …]
|
D | dev_env_and_tools.rst | 18 and linked to any relevant :ref:`bug or feature tracking issues<bug_reporting>` 276 - To classify the impact and importance of a bug or 279 Note: Issue priorities are generally set or changed during the bug-triage or TSC 283 - Something, which was working, but does not anymore (bug subtype). 307 Any issue must be classified and labeled as either *Bug*, *Enhancement*, *RFC*, 328 straightforward one-liner bug fixes, etc. 368 …:guilabel:`area: Coding Style`, :guilabel:`area: MISRA-C`) affected by the bug or the pull request. 392 * - :guilabel:`bug` 393 - The issue is a bug, or the PR is fixing a bug.
|
D | communication.rst | 16 In general, bug reports and other issues should be reported as `GitHub Issues
|
/Zephyr-latest/doc/services/device_mgmt/ |
D | mcumgr_backporting.rst | 44 Creating a bug report 47 Every proposed fix requires a bug report submitted for the specified version of Zephyr affected by … 49 In case the reported bug in a previous version has already been fixed in the current version, the d… 50 of the bug must be copied with the following: 52 * Additional references to the bug in the current version 56 You must also apply the ``backport v2.7-branch`` label to the bug report. 92 When the fix needed does not have a corresponding fix in the current version, the bug report
|
/Zephyr-latest/scripts/release/ |
D | bug_bash.py | 6 """Query the Top-Ten Bug Bashers 8 This script will query the top-ten Bug Bashers in a specified date window. 11 ./scripts/bug-bash.py -t ~/.ghtoken -b 2021-07-26 -e 2021-08-07 12 GITHUB_TOKEN="..." ./scripts/bug-bash.py -b 2021-07-26 -e 2021-08-07 125 'bug'], since=self._start_date) 162 """Print the top-ten bug bashers"""
|
/Zephyr-latest/tests/bsim/bluetooth/host/misc/hfc_multilink/tester/ |
D | prj.conf | 14 # Work around bug in throughput calculation
|
/Zephyr-latest/tests/bsim/bluetooth/host/l2cap/split/tester/ |
D | prj.conf | 14 # Work around bug in throughput calculation
|
/Zephyr-latest/tests/bsim/bluetooth/host/misc/hfc/ |
D | prj.conf | 23 # FIXME: enable those to see a bug
|
/Zephyr-latest/doc/develop/api/ |
D | overview.rst | 30 compatible bug fixes are introduced. A bug fix is defined as an internal
|
/Zephyr-latest/doc/develop/west/ |
D | release-notes.rst | 57 Bug fixes: 110 Bug fixes: 129 Bug fixes: 164 Bug fixes: 207 Bug fixes: 213 - A bug in the way west looks for the zephyr repository was fixed. The bug 236 Bug fix: 256 Bug fixes: 326 Bug fixes: 345 Bug fixes: [all …]
|
/Zephyr-latest/include/zephyr/dt-bindings/interrupt-controller/ |
D | esp-xtensa-intmux.h | 15 #define BT_BB_NMI_SOURCE 5 /* BT BB, NMI, use if BB have bug to fix in NMI */ 18 #define RWBT_NMI_SOURCE 8 /* RWBT, NMI, use if RWBT has bug to fix in NMI */ 19 #define RWBLE_NMI_SOURCE 9 /* RWBLE, NMI, use if RWBT has bug to fix in NMI */
|
D | esp32s2-xtensa-intmux.h | 16 #define BT_BB_NMI_SOURCE 6 /* BT BB, NMI, use if BB have bug to fix in NMI */ 19 #define RWBT_NMI_SOURCE 9 /* RWBT, NMI, use if RWBT has bug to fix in NMI */ 20 #define RWBLE_NMI_SOURCE 10 /* RWBLE, NMI, use if RWBT has bug to fix in NMI */
|
/Zephyr-latest/doc/connectivity/networking/ |
D | qemu_user_setup.rst | 85 * There is a bug in the SLIRP implementation which filters out all IPv6 packets 86 from the guest. See https://bugs.launchpad.net/qemu/+bug/1724590 for details.
|
/Zephyr-latest/scripts/coccinelle/ |
D | unsigned_lesser_than_zero.cocci | 2 /// comparisons 'unsigned (<|<=) 0' often indicates a bug,
|
/Zephyr-latest/modules/lvgl/include/ |
D | lv_conf.h | 48 * Needed because of a workaround for a GCC bug,
|
/Zephyr-latest/boards/digilent/arty_a7/ |
D | CMakeLists.txt | 10 # This ought to be done using the objcopy verilog bfd, but it contains a bug
|
/Zephyr-latest/cmake/compiler/xt-clang/ |
D | compiler_flags.cmake | 26 # Older xcc/clang cannot use "-g" due to this bug:
|
/Zephyr-latest/cmake/modules/ |
D | zephyr_default.cmake | 53 # Test and error-out if we are affected by the PyPI CMake 3.22.1 / 3.22.2 bug 59 " the \n 'cmake_path(... PARENT_PATH)' bug, see: \n"
|
123456