Udesh Senaratne

> Noting that we'll need to change the name in such a way that the current git history is not lost. It seems we might be able to do it...

Side note, currently the outcome of each source query is dumped to STDERR (instead of STDOUT). Perhaps this is by design? npm info using [email protected] npm info using [email protected] -...

@accforgithubtest if you are not looking for a dev container, are you looking for a container to host the evidence site ? Or to build it ?

When the dataset is empty, we can end up with undefined errors here: https://github.com/evidence-dev/evidence/blob/6baafc11f7568aedf8845809144087ce61d15fe3/packages/core-components/src/lib/unsorted/viz/sankey/SankeyDiagram.svelte#L122 

@hughess found that removing the `ssl` in the env var name `EVIDENCE_SOURCE__sourcename__ssl__rejectUnauthorized="false" -> EVIDENCE_SOURCE__sourcename__rejectUnauthorized="false"` causes ~the `rejectUnauthorized` flag to be picked up~ `rejectUnauthorized=true` during `npm run sources`

I think what’s happening is by default, we set rejectUnauthorized=false However, when var EVIDENCE_SOURCE__sourcename__ssl__rejectUnauthorized is set, regardless off the value (true/false), we are setting rejectUnauthorized=true That explains how Sean was...

@zachstence Probably related: https://github.com/evidence-dev/evidence/issues/2437 This seems to be affecting a wide range of projects with no actual apparent issues otherwise - impacting cloud logs and builds

Think it would be really helpful if `npm run sources` logs includes under each source query 1) the total time of the query exec, and 2) and where possible depending...

> Think it would be really helpful if `npm run sources` logs includes under each source query 1) the total time of the query exec, and 2) and where possible...

I don't know if this is still the case anymore but I recall once being able to write a test while that showed boolean env vars set to "false" were...