-
-
Notifications
You must be signed in to change notification settings - Fork 107
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
Error when the folder is already a git repo #14
Comments
This shows up when the .git repo is already initialised . In your case you can find it in the path |
Did you already have a folder named |
Nope, though I did run it once before with the same result.
…On Sat, Jun 1, 2019 at 02:53 Mathieu Dutour ***@***.***> wrote:
Did you already have a folder named bradbarrish-blog before?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#14?email_source=notifications&email_token=AAEWFPBBHCXQBZY3AQ4E6LDPYJBLDA5CNFSM4HR6VLYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWW5C2I#issuecomment-497930601>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAEWFPBTOZS7NGZ7ZD4SB5DPYJBLDANCNFSM4HR6VLYA>
.
|
Try running |
We could perhaps check at the beginning if the folder already exists, and if so ask if we should continue. If we continue, then we can just ignore errors on |
I ran Results...
|
ah so that was the first error probably. The error comes from the fact that you haven't really used git yet (haven't tested that scenario sorry). So to fix, run
then
and then
and it should be all good. Sorry for the confusing error |
New machine, which explains that. Successfully got through that step, but the deploy failed. deploy logs2:56:39 PM: Build ready to start 2:56:45 PM: build-image version: 9e0f207a27642d0115b1ca97cd5e8cebbe492f63 2:56:45 PM: build-image tag: v3.3.2 2:56:45 PM: buildbot version: 75cd99f62ada9e21edea53208e8baf0eab85a045 2:56:45 PM: Fetching cached dependencies 2:56:45 PM: Failed to fetch cache, continuing with build 2:56:45 PM: Starting to prepare the repo for build 2:56:45 PM: No cached dependencies found. Cloning fresh repo 2:56:45 PM: git clone https://github.com/bradbarrish/bradbarrish-blog 2:56:46 PM: Preparing Git Reference refs/heads/master 2:56:47 PM: Found netlify.toml. Overriding site configuration 2:56:47 PM: Starting build script 2:56:47 PM: Installing dependencies 2:56:48 PM: Downloading and installing node v10.16.0... 2:56:49 PM: Downloading https://nodejs.org/dist/v10.16.0/node-v10.16.0-linux-x64.tar.xz... 2:56:49 PM: ### 2:56:49 PM: 5.1% 2:56:49 PM: ################################# 2:56:49 PM: ############################## 88.4% 2:56:49 PM: ####################################### 2:56:49 PM: ################################# 100.0% 2:56:49 PM: Computing checksum with sha256sum 2:56:49 PM: Checksums matched! 2:56:52 PM: Now using node v10.16.0 (npm v6.9.0) 2:56:52 PM: Attempting ruby version 2.6.2, read from environment 2:56:54 PM: Using ruby version 2.6.2 2:56:54 PM: Using PHP version 5.6 2:56:54 PM: Started restoring cached node modules 2:56:54 PM: Finished restoring cached node modules 2:56:54 PM: Installing NPM modules using NPM version 6.9.0 2:56:57 PM: npm WARN deprecated [email protected]: This module has moved and is now available at @hapi/joi. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues. 2:57:00 PM: npm 2:57:00 PM: WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). 2:57:01 PM: npm WARN 2:57:01 PM: deprecated [email protected]: This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues. 2:57:01 PM: npm WARN 2:57:01 PM: deprecated [email protected]: This module has moved and is now available at @hapi/topo. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues. 2:57:03 PM: npm WARN deprecated 2:57:03 PM: [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). 2:57:03 PM: npm WARN deprecated 2:57:03 PM: [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). 2:57:06 PM: npm WARN deprecated [email protected]: core-js@<2.6.8 is no longer maintained. Please, upgrade to core-js@3 or at least to actual version of core-js@2. 2:57:42 PM: > [email protected] install /opt/build/repo/node_modules/sharp 2:57:42 PM: > (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy) 2:57:42 PM: info 2:57:42 PM: sharp 2:57:42 PM: Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.7.4/libvips-8.7.4-linux-x64.tar.gz 2:57:44 PM: > [email protected] install /opt/build/repo/node_modules/pre-commit 2:57:44 PM: > node install.js 2:57:45 PM: > [email protected] postinstall /opt/build/repo/node_modules/core-js 2:57:45 PM: > node scripts/postinstall || echo "ignore" 2:57:45 PM: Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library! 2:57:45 PM: The project needs your help! Please consider supporting of core-js on Open Collective or Patreon: 2:57:45 PM: > https://opencollective.com/core-js 2:57:45 PM: > https://www.patreon.com/zloirock 2:57:45 PM: Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -) 2:57:45 PM: > [email protected] postinstall /opt/build/repo/node_modules/core-js-pure 2:57:45 PM: > node scripts/postinstall || echo "ignore" 2:57:45 PM: Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library! 2:57:45 PM: The project needs your help! Please consider supporting of core-js on Open Collective or Patreon: 2:57:45 PM: > https://opencollective.com/core-js 2:57:45 PM: > https://www.patreon.com/zloirock 2:57:45 PM: Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -) 2:57:45 PM: > [email protected] postinstall /opt/build/repo/node_modules/spawn-sync 2:57:45 PM: > node postinstall 2:57:45 PM: > [email protected] postinstall /opt/build/repo/node_modules/gatsby-telemetry 2:57:45 PM: > node src/postinstall.js 2:57:46 PM: > [email protected] postinstall /opt/build/repo/node_modules/cwebp-bin 2:57:46 PM: > node lib/install.js 2:57:46 PM: ✔ cwebp pre-build test passed successfully 2:57:46 PM: > [email protected] postinstall /opt/build/repo/node_modules/mozjpeg 2:57:46 PM: > node lib/install.js 2:57:47 PM: ✔ mozjpeg pre-build test passed successfully 2:57:47 PM: > [email protected] postinstall /opt/build/repo/node_modules/pngquant-bin 2:57:47 PM: > node lib/install.js 2:57:47 PM: ✔ pngquant pre-build test passed successfully 2:57:49 PM: npm notice 2:57:49 PM: created a lockfile as package-lock.json. You should commit this file. 2:57:49 PM: npm WARN [email protected] requires a peer of [email protected] but none is installed. You must install peer dependencies yourself. 2:57:49 PM: npm WARN [email protected] requires a peer of typescript@* but none is installed. You must install peer dependencies yourself. 2:57:49 PM: npm WARN 2:57:49 PM: optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents): 2:57:49 PM: npm WARN 2:57:49 PM: notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) 2:57:49 PM: added 2026 packages from 1118 contributors and audited 30299 packages in 54.316s 2:57:49 PM: found 0 vulnerabilities 2:57:49 PM: NPM modules installed 2:57:50 PM: Started restoring cached go cache 2:57:50 PM: Finished restoring cached go cache 2:57:50 PM: unset GOOS; 2:57:50 PM: unset GOARCH; 2:57:50 PM: export GOROOT='/opt/buildhome/.gimme/versions/go1.12.linux.amd64'; 2:57:50 PM: export PATH="/opt/buildhome/.gimme/versions/go1.12.linux.amd64/bin:${PATH}"; 2:57:50 PM: go version >&2; 2:57:50 PM: export GIMME_ENV='/opt/buildhome/.gimme/env/go1.12.linux.amd64.env'; 2:57:50 PM: go version go1.12 linux/amd64 2:57:50 PM: Installing missing commands 2:57:50 PM: Verify run directory 2:57:50 PM: Executing user command: gatsby build 2:57:52 PM: success open and validate gatsby-configs — 0.010 s 2:57:53 PM: success load plugins — 0.815 s 2:57:53 PM: success onPreInit — 0.005 s 2:57:53 PM: success delete html and css files from previous builds — 0.006 s 2:57:53 PM: success initialize cache — 0.007 s 2:57:53 PM: success copy gatsby files — 0.019 s 2:57:53 PM: success onPreBootstrap — 0.012 s 2:57:54 PM: error Plugin gatsby-mdx returned an error 2:57:55 PM: 2:57:55 PM: SyntaxError: unknown: Expected corresponding JSX closing tag for |
So I think that a different issue. |
Got it. Thanks for all the help and patience. The site now seems to be working and looks great. 🙏 |
close this issue |
No let's keep it open and do this:
|
@bradbarrish So did you remove the drafts from your medium blog? |
I believe so, yes. Will confirm and let you know.
…On Wed, Jun 5, 2019 at 12:46 Julian ***@***.***> wrote:
Got it. Thanks for all the help and patience. The site now seems to be
working and looks great. 🙏
So did you remove the drafts from your medium blog?
(i tried creating a new repo, and redoing it all, still getting the same
error)
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#14?email_source=notifications&email_token=AAEWFPHROWSACTS3RWUI6YDPY73YNA5CNFSM4HR6VLYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXAPT6I#issuecomment-499186169>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAEWFPDKJKL2SPOMZ7DRHNLPY73YNANCNFSM4HR6VLYA>
.
|
So the deploy to Netlify breaks when it gets empty date or any other field. The docs say that we can keep it empty for drafts until we publish it. |
Ah interesting. Could you open another issue? It’s a bit different from this one |
The text was updated successfully, but these errors were encountered: