umd-mith / airwaves

Unlocking the Airwaves
https://mith.umd.edu/airwaves/
MIT License
9 stars 2 forks source link

Development build issue #1

Closed trevormunoz closed 4 years ago

trevormunoz commented 4 years ago

Running npm run develop throws a fatal error:

> airwaves@0.0.1 develop /Users/umd-laptop/Code/airwaves
> gatsby develop

success open and validate gatsby-configs - 0.039s
success load plugins - 0.820s
success onPreInit - 0.023s
success initialize cache - 0.074s
success copy gatsby files - 0.108s
success onPreBootstrap - 0.029s
success createSchemaCustomization - 0.014s
success source and transform nodes - 11.910s
warn Plugin `gatsby-source-filesystem` tried to define the GraphQL type `File`, which has already been defined by the plugin `null`.
warn Plugin `gatsby-source-filesystem` tried to define the GraphQL type `File`, which has already been defined by the plugin `null`.
warn Plugin `gatsby-source-filesystem` tried to define the GraphQL type `File`, which has already been defined by the plugin `null`.
success building schema - 1.138s
episode missing aapbId [Object: null prototype] { aapbId: null }
a-radio-and-a-microphone
the-organizational-structure-of-the-naeb
success createPages - 10.490s

 ERROR 

UNHANDLED REJECTION ENOENT: no such file or directory, chmod '/Users/umd-laptop/Code/airwaves/public/rss/programs.opml'

  Error: ENOENT: no such file or directory, chmod '/Users/umd-laptop/Code/airwaves/public/rss/programs.opml'

not finished createPagesStatefully - 18.593s
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! airwaves@0.0.1 develop: `gatsby develop`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the airwaves@0.0.1 develop script.

The referenced OPML file is present. I haven't provided AIRTABLE_API_KEY if that might be causing a problem?

edsu commented 4 years ago

What happens if you run it again?

trevormunoz commented 4 years ago

Yes. I should have mentioned that I ran the command twice more with the same result.

edsu commented 4 years ago

@trevormunoz thanks for spotting this! Hopefully pulling the latest code fixes it? If not please reopen.