-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Crash while using Build --serve and modifying vault content live #798
Comments
Was able to replicate a second time, however no continuing edit was made to the content, ie didn't do step 4 in STRs
|
@aarnphm can you take a look at this actually LOL i cannot reproduce this at all |
Can you give us a link to a vault? Does this happen to you on the default vault? |
No, didn't seem to happen on default vault. |
And it just crashed without any action on my part...
If you want I can hop into a call in your discord to troubleshoot or get what you need, I have backups so I can mess with things |
Can you link to the source? Want to see if I can reproduce
|
Source: Shillelagh.zip I removed the entire setup (saving the config and layout files), redownloaded Quartz and then re-established the symlink. And it hasn't crashed yet. Looking at some other unrelated things, its possible there might be an issue with the symlink, but only on my computer which will take some time to troubleshoot this. I'm not sure if its related or not yet. |
Super weird, keep me posted. I haven't been able to reproduce this yet but let me know if you have something consistent |
@jackyzha0 might be a apple silicon issue. |
They are on a Windows machine |
oh ok I forgot to ready the description 😄 |
I can reliably recreate this after editing source code and spamming refresh. Will share some findings here later on. |
I've completed what troubleshooting I can to isolate this from my setups quirks and while I can't get everything isolated, I have been able to replicate this again still using a symlink, so I'll be removing the symlink in a second and trying again.
|
Interesting, @aarnphm does your setup also use symlinks or separate? |
This is probably its own problem but when using build -serve it shows everything is linked correctly, however when uploaded to the website, all of the links just break down and throw 404s. Separate issue I assume? |
separate. |
separate. |
Non-symlink still crashes:
Is there a flag I can set so that it gives more helpful information or is this all you need? |
Can you run it in verbose mode (with the |
Will do. And also the quartz version in use is 4.2.1 not 4.1.2 as mentioned above |
Looks like it something that its not happy about with
|
Seems like something |
is there a |
No lol, I already know the exact line it dies on |
Describe the bug
Not really a clue... Seems to hang when attempting to emit files after they have been updated in some way.
To Reproduce
Reliable replication not possible or unknown
build
command with--serve
argumentDetected change, rebuilding
message, modify it again(These steps are best achieved one immediately after the other, typing a long sentence can work)
Expected behavior
Either
A. Emitting to complete and reprocessing to start occurring immediately
B. Emitting to self cancel and pause for a set period before reprocessing
Screenshots and Source
Entire log from start of command to error and crash:
Desktop (please complete the following information):
node
Version: v20.11.0npm
version: 10.2.4Additional context
Content and vault are symlinked through command
mklink
Additional files and/or vault available on request.
The text was updated successfully, but these errors were encountered: