Skip to content

chore: use the correct environment variable for proof params path#12891

Merged
masih merged 1 commit intomasterfrom
masih/proof-params-env-var-fix
Feb 11, 2025
Merged

chore: use the correct environment variable for proof params path#12891
masih merged 1 commit intomasterfrom
masih/proof-params-env-var-fix

Conversation

@masih
Copy link
Copy Markdown
Member

@masih masih commented Feb 11, 2025

The actual environment variable that sets the proof params fetch path is FIL_PROOFS_PARAMETER_CACHE according to go-paramfetch implementation. See:

Fix it in Dockerfile to avoid redundant download of params if the wrong env var is set.

The actual environment variable that sets the proof params fetch path
is `FIL_PROOFS_PARAMETER_CACHE` according to `go-paramfetch`
implementation. See:

* https://github.com/filecoin-project/go-paramfetch/blob/62ad5888f87076c9589d2b63af904b1f89a91b86/paramfetch.go#L31

Fix it in `Dockerfile` to avoid redundant download of params if the
wrong env var is set.
@masih masih requested a review from ZenGround0 February 11, 2025 13:23
@masih masih added the skip/changelog This change does not require CHANGELOG.md update label Feb 11, 2025
@masih masih self-assigned this Feb 11, 2025
@masih masih enabled auto-merge (squash) February 11, 2025 13:23
@rjan90
Copy link
Copy Markdown
Contributor

rjan90 commented Feb 11, 2025

Gave a head-up to Curio here in Slack, as I see they are also using FILECOIN_PARAMETER_CACHE here: https://github.com/filecoin-project/curio/blob/82c295b69d37f91eb0015a90e5b1d16ccfb4c128/Dockerfile#L71-L74

@masih masih requested a review from rjan90 February 11, 2025 17:19
@masih masih merged commit 47a3e3f into master Feb 11, 2025
@masih masih deleted the masih/proof-params-env-var-fix branch February 11, 2025 18:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip/changelog This change does not require CHANGELOG.md update

Projects

Status: ☑️ Done (Archive)

Development

Successfully merging this pull request may close these issues.

2 participants