-
Notifications
You must be signed in to change notification settings - Fork 20
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
Refactor tasks to not fork, and always run in-process of the main execution pipeline #1613
Merged
+1,011
โ787
Merged
Changes from all commits
Commits
Show all changes
31 commits
Select commit
Hold shift + click to select a range
24e157a
Check that Deno v1.23.x is used when building Taqueria
bc977f5
Temporary commit
6d4c9b0
Added means of registering internal tasks, and to process those tasksโฆ
81c3a8f
Segmented global and internal tasks
2cc3bb8
Ensure that internal tasks are invoked
eddbde7
Fixed memory leak in test/e2e/utils
ebe670c
Fix broken test due to help output changing
ded3e1e
Fixed failing test spec due to help output changes
ca98a5c
Re-add afterAll hook to cleanup
ecd86da
Fix broken tests due to help output
e7b9aac
Fixed help output for contract types test spec
6412863
Committing work thus far
60b72ed
Accomodate aliases when determining whether a task is runninng
4dfd48f
Fixed problem with taq not outputting in non-taquified directory
1736d8d
Merged main into refactor-internal-tasks
38e3a76
Skip pinata help output tests
897629a
Skipping some tests due to help output changing
7f15da8
Assure that we can identify whether tasks are being run which have spโฆ
da066d3
Fixed issue with parsedArgs._ being modified after parseArgs is run
f704bbf
Ensure that detection for whether a given task is running is working
c1d4a33
Merge branch 'main' into refactor-internal-tasks
aca2f32
Skip some tests that fail due to change in help output
d36d379
Add missing aliases to some registered tasks
4c10da2
Skipped more tests due to changes in help text output
faf30f1
Fixed issues with failing tests in metadata test suite due to legacy โฆ
79f3556
Fixed broken ligo test due to skipping a previous test
19f6a91
Removed debugger statements
94408ce
Fixed typo
10caa14
Added link to issue for todo item
752ea15
Addressed PR comments
b405eb0
Merge branch 'prerelease-0.25.0' into refactor-internal-tasks
hu3man File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we still need it? I thought this would not be needed after the internal task refactor
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure to be honest. If not, I assume we'll address that in a different ticket/PR.
The acceptance criteria for this particular issue/PR was:
As that criteria is a little vague, I interpreted it to be:
The motive for that , as far as I was aware, was to resolve a) memory leaks; b) concurrency issues; c) make the code easier to reason about; d) ability to ask for
--help
for built-in tasksI had thought that the only thing holding back GA tracking was issue B above.
--
I modified the following code strictly for type correctness, as this section of code was returning Future<string, unknown> instead of Future<TaqError, unknown>:
Before:
After:
If the above code isn't needed anymore, great - but I'd probably prefer making that adjustment in a different PR, as I cannot recall the reason why Jimmy added this code, and too, I think that's outside of the scope I had in mind in this PR. Would you be fine if we created an issue for this instead, Ali? I would do so, but given that you recognized this, I assume you might have more context/recollection about why this code was here to start with.