Skip to content

Conversation

@adamraine
Copy link
Contributor

@adamraine adamraine commented Mar 2, 2022

Steps 4 & 5 of #13364. I combined them because I needed step 5 to test step 4 🤷

Lol +900,000 from the artifacts file. It contains the DT logs and traces inline for the equivalent of 3 normal LH runs.

Ref
#11313

@adamraine adamraine requested a review from a team as a code owner March 2, 2022 21:21
@adamraine adamraine requested review from connorjclark and removed request for a team March 2, 2022 21:21
Copy link
Collaborator

@connorjclark connorjclark left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I expected this to work with -GA, but I guess that will come later? If so, please rename the PR title to reflect that this isn't actually loading or saving artifacts to disk during normal operation.

@adamraine adamraine changed the title core(user-flow): save/load flow artifacts json core(user-flow): audit flow artifacts json Mar 3, 2022
const configJson = gatherStep.config || flowConfig;
const {gatherMode} = artifacts.GatherContext;
const {config} = initializeConfig(configJson, {...configContext, gatherMode});
runnerOptions = {
Copy link
Collaborator

@connorjclark connorjclark Mar 3, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems we could add a second property like _gatherStepRunnerOptions or something, and keep runner options data there. could be an array or a weakmap (if array, this loop changes to for (let i ..., if weakmap can keep for loop as is). I think conceptually the weakmap makes sense here.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I decided to go with the weak map approach here. Keeps GatherStep type clear of any extra stuff

@adamraine adamraine changed the title core(user-flow): audit flow artifacts json core(user-flow): audit flow from artifacts json Mar 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants