-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix clobbering of process vs component vs forc #668
Draft
alfiedotwtf
wants to merge
1
commit into
master
Choose a base branch
from
alfie/resolve-proxy
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alfiedotwtf
force-pushed
the
alfie/resolve-proxy
branch
from
October 4, 2024 10:11
e16411b
to
e5318c2
Compare
JoshuaBatty
reviewed
Oct 10, 2024
JoshuaBatty
reviewed
Oct 10, 2024
alfiedotwtf
changed the title
Fix clobbering of process vs component vs forc (#654)
Fix clobbering of process vs component vs forc
Oct 27, 2024
- Checking whether or not the executable was published by forc - Checking whether or not the executable was in the store - Used to generate the tarball target - Used to generate the tarball URL - Used to generate the final target executable to run from the store Each of the above was breaking in subtle ways depending on which executable was being run. After separating out these functions based on the properly resolved component from the executable, and along with the previous commits, these problems above were resolved.
alfiedotwtf
force-pushed
the
alfie/resolve-proxy
branch
from
October 29, 2024 00:55
e5318c2
to
7329e4e
Compare
Can we add some tests to show how this change works? |
Yep, no problem. |
Keeping this PR in DRAFT but backgrounding for now... 90% of the tests have been done, I just have to do the other 90%. Backgrounding for now, but will leave this as a downtime task to complete. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These issues were found while investigating #654.
Currently,
component_name
was being repurposed for multiple functions:forc
Each of the above was breaking in subtle ways depending on which executable was being run.
After separating out these functions based on the properly resolved component from the executable, and along with the previous commits, these problems above were resolved.