chore(common): extend getRequiredEnvVar method to check empty values#2156
Conversation
c8b49b1 to
ac6fed9
Compare
zmalatrax
left a comment
There was a problem hiding this comment.
library-solidity/tasks/utils/loadVariables.tshas an identicalgetRequiredEnvVarfunction that was not updated. It still has the old behavior (no empty check) and even retains the comment
// We only check if the variable is set, not if it's empty.This means deployments using the
library-soliditytasks still silently accept empty env vars.
library-solidity should be updated as well, or not used?
Otherwise lgtm
|
@Mergifyio queue |
Merge Queue Status
This pull request spent 1 minute 37 seconds in the queue, with no time running CI. ReasonThe pull request conflicts with pull requests ahead in queue: #2157, #2163, #2158 HintThere is nothing you can do for now. If the pull request ahead in the queue is merged, this pull request will become conflicting and you'll have to update it. |
18c8190 to
4555946
Compare
|
@Mergifyio queue |
Merge Queue Status🛑 Queue command has been cancelled |
4555946 to
90a12a3
Compare
|
@Mergifyio queue |
08358a5 to
8d01ffa
Compare
|
@Mergifyio refresh |
✅ Pull request refreshed |
|
@Mergifyio queue |
Merge Queue Status
This pull request spent 2 hours 16 minutes 5 seconds in the queue, including 1 hour 14 minutes 55 seconds running CI. Required conditions to merge
|
Closes https://github.com/zama-ai/fhevm-internal/issues/157