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
feat: resolveAndTestFacts with async polling #2025
Conversation
plugin, | ||
scanResultsByPath, | ||
); | ||
} |
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.
At the current stage I preferred to keep this logic as part of testDependencies
instead of create a completely new flow for resolveAndTestFacts
, have time to change it when required
src/lib/ecosystems/test.ts
Outdated
options, | ||
2000, | ||
); | ||
results.push(response); |
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.
Keeping the current approach where we test/resolve one scanResult at the time.
Depending of resolution AVG
time for C/C++ unmanaged, we can change it to something like:
- Please generate a token (resolution process) for all the scanResults (if they are resolvable kind)
then go over that list and keep polling each token in order to see if any is available, if yes then take out of the list till all the scanResults' token are processed either successfully or not
e8e6092
to
9288497
Compare
|
||
expect(testResults).toEqual([ | ||
{ | ||
components: [ |
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.
this will change to depGraph & issuesData
9288497
to
abe74f5
Compare
src/lib/ecosystems/polling.ts
Outdated
attemptsCount, | ||
), | ||
); | ||
}), |
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.
Are you missing the second argument to setTimeout here?
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.
🤦 yes, thanks!
name: 'my-unmanaged-c-project', | ||
facts: [ | ||
{ | ||
type: 'signatures', |
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.
We called this 'cpp-signatures'
in feat/support-c-addon here.
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.
Good point, we are moving to fileSignatures
e645519
to
653448e
Compare
bf81d23
to
99894bc
Compare
08df3a6
to
4fd0858
Compare
Introduces async request for C/C++ with polling, where its Facts are resolved/computed in our platform
4fd0858
to
9ed6542
Compare
Initial support for async test of unmanaged ecosystems e.g. c/c++ adding polling to resolve and test fileSignatures fact. The pr that will introduce the active usage of it will come later on. These changes comes from #2025 Using chore as prefix, because at the moment it's not bringing any effective feat yet.
Initial support for async test of unmanaged ecosystems e.g. c/c++ adding polling to resolve and test fileSignatures fact. The pr that will introduce the active usage of it will come later on. These changes comes from #2025 Using chore as prefix, because at the moment it's not bringing any effective feat yet.
Introduces async request for C/C++ with polling, where its Facts are resolved/computed in our platform