sthagen
Follow
Create your own GitHub profile
Sign up for your own profile on GitHub, the best place to host code, manage projects, and build software alongside 50 million developers.
Sign up
sthagen
Follow
Highlights
- Arctic Code Vault Contributor
- GitHub Sponsor
- Developer Program Member
- Pro
Pinned
11,629 contributions in the last year
Activity overview
Contribution activity
August 2020
- sthagen/python-spdx_license_matcher Python
- sthagen/python-spdx_tools Python
- sthagen/spdx-license-list-xml Makefile
- sthagen/kotlin-oss_review_toolkit Kotlin
- sthagen/python-dependency_track_auditor Python
- sthagen/go-dtrack-audit Go
- sthagen/python-ciphey Python
- sthagen/cpp-pipes C++
- sthagen/hadolint Haskell
- sthagen/python-json_schema_tangle_weave Python
- sthagen/python-rich Python
- sthagen/fd Rust
- sthagen/hexyl Rust
- sthagen/hyperfine Rust
- sthagen/bat Rust
- sthagen/tools-image Dockerfile
- sthagen/python-inventory_vulnerability_analysis Python
- sthagen/flit Python
- sthagen/pipx Python
- sthagen/RustPython Rust
- sthagen/Nuitka Python
- sthagen/pep517 Python
- sthagen/uuid-readable JavaScript
- sthagen/dijo Rust
Created a pull request in JSBSim-Team/jsbsim that received 3 comments
Implemented iterator update after erase (suggested by Sean McLeod)
Details at #309 discussion esp. latest comment from Sean Closes #309
+2
−0
•
3
comments
- Shortened name
- Removed leftover from refactoring
- Fixed style
- Enable unreachable code
- Fixed signature and comment
- Load repo map upon successful session init
- Some crude initial implementation of the metadata fetch (the repo map)
- Added missing import for HTML parsing
- Added fetch client method
- Added missing import for the throttling implementation
- And the other missing import for the broken cert case
- Added one missing import
- Added simplistic fetch method
- Added caveat emptor on status
- Added missing import
- Update test_brm_rest_walk.py
- Update test_brm_rest_walk.py
- Fixed implementation (experimental)
- Added negative test case for class init
- Added tree walker class with some init
- Added missing import
- Syntax fix
- Update test_brm_rest_walk.py
- Remove unused import
- Create test_brm_rest_walk.py
- Some pull requests not shown.
- Added tangle test case and fixed test data
- Added negative test case
- Added second cli test case
- Update README.md
- Update README.md
- Create test_json_schema_tangle_weave.py
- Create test_cli.py
- Create json_schema_tangle_weave.py
- Create cli.py
- Create __main__.py
- Create setup.py
- Create setup.cfg
- Create pyproject.toml
- Create __init__.py
- Created tests folder
- Create __init__.py
- Merge pull request #1 from sthagen/default
- Update README.md
- Use #error instruction to shield against iterator use after erase()
- Use #error directive shielding against iterator use after erase()
- Fixed the class documentation.
- Revert "Implement iterator update after erase (suggested by Sean McLeod"
- Implement iterator update after erase (suggested by Sean McLeod
- Fix one off error in array iteration (#311)
- Fix one off error in array iteration (#311)
- Fix one off error in array iteration
- Sync Fork from Upstream Repo
135
repositories not shown
Created an issue in JSBSim-Team/jsbsim that received 7 comments
Possible iterator use after call of erase on element
In src/initialization/FGTrimAnalysis.cpp the iterator iControls may be used after calling eraseon the element. cppcheck 1.82 warns on that one ... …
7
comments
- Document the short comings of json text fields for providing structured information
- Explain the rationale
- Define dependencies via requirements
- Document contributor guidelines
- Provide info on other packages of similar functionality
- Explain what exactly tangle means in this context
- Explain what exactly weave means in this context
- Create examples
- Generate test data
- Find a better name for the package
- Document what is out of scope
- Document use cases
- Document constraints for use
- Write functional tests
- Write unit tests
- Evaluate build tools and actions
- Provide initial implementation
- Write tests for infrastructure mechanics
- Decide on packaging tool
- Evaluate packaging tool
- Document the MVP
- Add a caveat emptor on the status of the project
- Evaluate throttling strategies besides a single global float value
- Document the risk when storing secrets in environment variables
- Should we offer a vault adapter for secrets?
- Move from environment variables to configuration (service) or command line parameters
- How to derive the data classification from the REST calls?
- How to derive the data classification from the hash storage
- Define a straw puppet for expected BRM file and rest posture
- Is there proven stability of the REST API across major BRM product versions?
- How does one timestamp a tree from the hashed storage?
- How does one assemble a tree from the hashed storage?
- Add pyproject.toml preparing for pep51(7|8)
- Provide minimal setup.py
- Provide setup.cfg shim
- Decide on packaging
- Evaluate packaging
- Evaluate security testing in build pipelines / actions
- Evaluate build pipelines / actions
- Decide on packaging strategy
- Provide contributor guidelines (when initial implementation in place)
- Evaluate packaging options
- Add functional tests
- Add unit tests for implementation
- Add tests for package mechanics
- Add initial implementation