| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## main #189 +/- ##
==========================================
- Coverage 88.35% 88.24% -0.12%
==========================================
Files 63 64 +1
Lines 2997 3002 +5
Branches 376 376
==========================================
+ Hits 2648 2649 +1
- Misses 349 353 +4 ☔ View full report in Codecov by Harness.
|
Sorry, something went wrong.
|
Wasm tests succeed in https://github.com/QuantStack/git2cpp/actions/runs/37608961186. |
Sorry, something went wrong.
|
The code coverage is reduced as this change is in wasm-specific code and we do not check coverage for such code paths. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This PR overrides the core.filemode config setting so that it is false in wasm builds. Without this, if you git clone a repo in JupyterLite that contains files with executable flags set, after refreshing the browser tab those file retrieved from the JupyterLite drive no longer have those executable flags set and are hence identified as changed.
The cockle emscripten filesystem does support storing of file permissions, it is only the JupyterLite shared drive that does not. The workaround here essentially means that wasm use of git2cpp is like on Windows where file permissions do not work via chmod. Longer term the correct fix for this is for the JupyterLite drive to fully support file permissions (and timestamps, etc).