search

quirrel-dev / quirrel

The Task Queueing Solution for Serverless.
https://quirrel.dev
MIT License
885 stars 67 forks source link

sveltekit codespaces cron job not working #1121

Closed JonathonRP closed 1 year ago

JonathonRP commented 1 year ago

Bug Report

Current Behavior similar to #1089 I have a running in codespaces with a single cron job in sveltekit that shows in status but doesn't show in cron tab and is not running.

Input Code

Expected behavior/code cron should be picked up, running and visible in cron tab

Environment

Skn0tt commented 1 year ago

Hi @JonathonRP, thanks for the report! There was a bug where the --host arg wasn't respected everywhere in the codebase. https://github.com/quirrel-dev/quirrel/pull/1122 fixes that, i'll let you know once it's released.

@all-contributors please add @JonathonRP for bug

allcontributors[bot] commented 1 year ago

@Skn0tt

I couldn't determine any contributions to add, did you specify any contributions? Please make sure to use valid contribution names.

I've put up a pull request to add @JonathonRP! :tada:

Skn0tt commented 1 year ago

https://github.com/quirrel-dev/quirrel/releases/tag/v1.13.2 contains the PR, please let me know if that fixes it for you.

JonathonRP commented 1 year ago

@Skn0tt, this did not resolve my issue, if it helps here are the errors I get in UI dev console. image urls: image image

Also note I am using port 5000 for sveltekit app dev server

Skn0tt commented 1 year ago

Okay, re-opening.

5000 isn't the default sveltekit app dev server, right? If you're changing the port, then you need to tell your app what the new port is. You can do this by setting the env var QUIRREL_BASE_URL=0.0.0.0:5000.

JonathonRP commented 1 year ago

Thank you @Skn0tt, I tried a few work ways to tell Quirrel port 5000 but never changed the results. also, note that working in my local environment now with no changes, Quirrel works and picks up CronJob.

Skn0tt commented 1 year ago

Okay, so did this fix your problem, or should I look into it again?

JonathonRP commented 1 year ago

@Skn0tt please look into it again.

Skn0tt commented 1 year ago

When running QUIRREL_BASE_URL=http://0.0.0.0:5000 npx quirrel in a codespace with your repo, things are running fine. I noticed it doesn't work with .env, could it be that you've tried that instead? The quirrel CI doesn't pick up your .env automatically, you can take a look at https://www.npmjs.com/package/dotenv-cli if you're looking for that.

JonathonRP commented 1 year ago

I will give this a try, and it is good enough for me to close this issue now.