extenddb version prints the first build's commit after a rebuild in the same target directory
Maintainers usually reply within 4 days
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- rust
- Domain
- build-system
Research direction
Start with crates/bin/build.rs and inspect how it emits Cargo rebuild directives; read how git rev-parse --git-dir identifies the Git directory, including in a worktree. Rebuild in the same target directory after a commit and check extenddb version; done means it reports the current commit and build time, including for a worktree.
Written by the indexing model from the issue text.
Description
crates/bin/build.rs bakes the commit hash and the build time into the binary, and tells cargo to run it again only when EXTENDDB_GIT_HASH or EXTENDDB_BUILD_TIME changes (cargo:rerun-if-env-changed). A later build in the same target directory recompiles the crates that changed and links a new binary, but does not run the build script again, so extenddb version still prints the commit and time of the first build there.
Seen on 30 October: a release binary rebuilt in the same target directory after three commits printed the commit it was first built at, with the old build time.
Setting EXTENDDB_GIT_HASH for each build works around it. A fix is to also emit cargo:rerun-if-changed for the git HEAD file and the ref it points to, found through git rev-parse --git-dir so that a worktree works too.
- Dominant language
- Rust
- Stars
- 517
- Forks
- 60
- Avg merge
- 4d 19h
- Merged PRs (30d)
- 50
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ExtendDB/extenddb
-
bug security
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 4 days
-
Scan: ExpressionAttributeValues without an expression answers with a ": FilterExpression is null" suffix the service does not sendPossibly taken @LeeroyHannigan claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
ExtendDB/extenddb#722 · 1 assignee ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 4 days
-
init writes the TLS private key at the umask mode before setting it to 0600Possibly taken @LeeroyHannigan claimed this today. Openbug security
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 4 days
-
Export and import paths can write CR, LF and terminal escape sequences into the server logPossibly taken @LeeroyHannigan claimed this today. Openbug security
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 4 days
All issues in ExtendDB/extenddb
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
could docs good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
README em inglêsOpengood first issue help wanted priority:p2 type:docs
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
lucacasanova/homedeck#122 ·
-
needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 78/100
bherbruck/solvecraft#11729 · 1 comment · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day