You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to render a landscape locally for test purposes. Unfortunately when I attempt to run a render, during yarn fetch, specifically at the addExternalInfo.js step, all the crunchbase data from the processed landscape is lost, despite the output saying:
CRUNCHBASE_KEY_4 is not set. Using processed_landscape.yml as a source for crunchbase info
I'm pretty sure this didn't happen when I first tried playing with Landscapeapp, though perhaps it always had. Either way, this isn't very helpful when I need to run builds locally to test the effect of changes to landscapeapp and want to ensure I'm not breaking official landscapes in doing so.
Is there a convenient way for me to ensure that the already cached data is not lost so that I can render these landscapes locally?
The text was updated successfully, but these errors were encountered:
Sorry for the noise, I have discovered the bug, introduced in 933ac23 we no longer retain the saved crunchbase data if the key is not set. I shall file a PR to fix this immediately
I am trying to render a landscape locally for test purposes. Unfortunately when I attempt to run a render, during
yarn fetch
, specifically at theaddExternalInfo.js
step, all the crunchbase data from the processed landscape is lost, despite the output saying:CRUNCHBASE_KEY_4 is not set. Using processed_landscape.yml as a source for crunchbase info
I'm pretty sure this didn't happen when I first tried playing with Landscapeapp, though perhaps it always had. Either way, this isn't very helpful when I need to run builds locally to test the effect of changes to landscapeapp and want to ensure I'm not breaking official landscapes in doing so.
Is there a convenient way for me to ensure that the already cached data is not lost so that I can render these landscapes locally?
The text was updated successfully, but these errors were encountered: