| Age | Commit message (Collapse) | Author |
|---|
|
The original overflow logic used __spm[tm_mon] as the current month's
length when normalizing tm_mday. This produced incorrect dates after
crossing month boundaries and left zero or negative days unnormalized.
Use the difference between adjacent cumulative day offsets with
leap-year handling. Normalize overflow in tm_sec, tm_min, tm_hour,
tm_mday, and tm_mon to keep the affected broken-down fields normalized.
Add regression tests for month boundaries, leap years, large offsets,
zero and negative days, negative time fields, combined overflow, and
boundary carry cases.
Close #11686
Signed-off-by: Hui Su <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* ci: add armclang BSP build coverage
* components/libc: avoid armclang errno include recursion
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Signed-off-by: GuEe-GUI <[email protected]>
|
|
Signed-off-by: CYFS <[email protected]>
|
|
This is a builtin fdt example BSP
Signed-off-by: GuEe-GUI <[email protected]>
|
|
|
|
- add i686-atxhua-picolib-elf-gcc toolchain
- add picolib option to bsp/x86
- add necessary picolib require library
|
|
* add i686 x86 newlib toolchain
* add missing x86 gcc option to manual_dist.yml
* fix typo
|
|
|
|
|
|
|
|
Move user-controlled GitHub Actions context expressions
(github.event.pull_request.head.ref, head.repo.full_name,
pull_request.number, event.action) from direct interpolation
in run: blocks to env: variables.
Direct interpolation of these values in shell scripts allows
attackers to inject arbitrary commands via crafted branch names
under pull_request_target, which runs in the base repo context.
Using env: variables ensures values are treated as literal
strings by the shell, preventing command injection.
Ref: https://securitylab.github.com/research/github-actions-untrusted-input/
Reported-by: Wilson Cyber Research (@sourcecodereviewer)
Security: expression-injection
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Initial plan
* Add CI results comment workflow
Co-authored-by: supperthomas <[email protected]>
* Improve CI results comment formatting and PR detection
Co-authored-by: supperthomas <[email protected]>
* Add documentation for CI results comment feature
Co-authored-by: supperthomas <[email protected]>
* Add ToolsCI and pkgs_test to monitored workflows
Co-authored-by: supperthomas <[email protected]>
* Add immediate CI status comment via direct workflow integration
Co-authored-by: supperthomas <[email protected]>
---------
Co-authored-by: copilot-swe-agent[bot] <[email protected]>
Co-authored-by: supperthomas <[email protected]>
|
|
|
|
* feat:[sal][utest] added test cases for the sal api
* improve[net][utestcase]: standardize script construction
* ci[auto utest run]: standardize naming and add sal testcases
* add sal utest auto run configure and standard Information
|
|
The current test environment is mainly based on Ubuntu
22.04 LTS and doxygen version is 1.9.1.
But when we switch to Ubuntu 24.04, the default Doxygen
version on Ubuntu 24.04 is 1.9.8.
The supported configuration and layout file formats
differ from those in 1.9.1 (Ubuntu 22.04).
In particular, the layout XML file format of 1.9.8 is
incompatible with the older format(1.9.1). Therefore,
to support Doxygen on Ubuntu 24.04, we need to load
different configuration and layout files. (The layout
file is specified using the LAYOUT_FILE parameter in
the configuration file.)
Solution: Provide corresponding configuration and layout
files for different Doxygen versions, distinguished by
the Doxygen version number.
Currently, only Doxygen versions 1.9.1 and above are supported.
If the doxygen version is >= 1.9.1 but < 1.9.8, the 1.9.1
configuration and layout are used by default. If the doxygen
version is >= 1.9.8, the 1.9.8 configuration and layout are used.
Only 1.9.1 and 1.9.8 have been tested, as these are the
default doxygen versions on Ubuntu 22.04 LTS and Ubuntu
24.04. Other versions have not been tested yet. If
necessary, we will change the configuration based on
the same approach in the future.
Signed-off-by: Chen Wang <[email protected]>
|
|
ci: add concurrency control to GitHub Actions
|
|
|
|
|
|
reviewers #10729
|
|
|
|
* tools: add clang-format formatting script for CI
* improve[ci]: standardize the naming of CI files related to clang-format
|
|
|
|
|
|
|
|
|
|
|
|
issue (#10524)
* Modify the reference path of the header file in the middle section
* format
* Fix smart serial_v2 bypass compile error issue
* add allwinner/d1s ci
|
|
object name version #10537
|
|
CI comment
|
|
|
