JFSIII
JFSIII
PostsComments
CDCloudflare Developers
Created by JFSIII on 9/20/2024 in #general-help
Dashboard for Pages project settings won't load / throw JS error
This behavior started ~12 hours ago. Around 7-8pm US Eastern 1) From Workers & Pages https://dash.cloudflare.com/ACCOUNT_ID/workers-and-pages 2) Click a Pages product name, sent to https://dash.cloudflare.com/ACCOUNT_ID/pages/view/PAGES_PROJECT_NAME 3) Click Settings, sent to https://dash.cloudflare.com/ACCOUNT_ID/pages/view/PROJECT_NAME/settings which quickly becomes https://dash.cloudflare.com/ACCOUNT_ID/pages/view/PROJECT_NAME/settings 4) See loading skeleton, then quickly "It looks like we're having some internal issues." page Stack trace in the JS console is attached
16 replies
CDCloudflare Developers
Created by JFSIII on 5/6/2024 in #pages-help
Github integration for Pages apps in monorepo
I had mixed success this weekend attempting to use the Github integration in a monorepo with some Pages apps. The main reason I'm doing this is to get the UI for branch controls . I don't want to control Production/Preview rules with an API request. I started out trying to add the Pages project by pointing to the directory where it was located. That found the wrangler.toml but failed running the build command (seemingly because remix wasn't in the path I also tried from the monorepo root and that failed to find the wrangler.toml (expected. there isn't one in the root) but the build command (scoped to the app directory) did work. I'd like to run/specify things relative to the app directory, but am not sure what the issue is or how to debug/fix it. Here are some lightly redacted/edited logs: 
## From app directory
### Settings
build command: npm run build
build output directory: build/client
root directory: apps/pages-remix-a

### Logs
Using v2 root directory strategy
Checking for configuration in a wrangler.toml configuration file (BETA)
Found wrangler.toml file. Reading build configuration...
pages_build_output_dir: build/client
Successfully read wrangler.toml file.
Executing user command: npm run build
    
> build
> remix vite:build
    
sh: 1: remix: not found
npm ERR! Lifecycle script `build` failed with error: 
npm ERR! Error: command failed 
npm ERR!   in workspace: lift-practice 
npm ERR!   at location: /opt/buildhome/repo/apps/lift-practice  
## From app directory
### Settings
build command: npm run build
build output directory: build/client
root directory: apps/pages-remix-a

### Logs
Using v2 root directory strategy
Checking for configuration in a wrangler.toml configuration file (BETA)
Found wrangler.toml file. Reading build configuration...
pages_build_output_dir: build/client
Successfully read wrangler.toml file.
Executing user command: npm run build
    
> build
> remix vite:build
    
sh: 1: remix: not found
npm ERR! Lifecycle script `build` failed with error: 
npm ERR! Error: command failed 
npm ERR!   in workspace: lift-practice 
npm ERR!   at location: /opt/buildhome/repo/apps/lift-practice  
## From monorepo root
### Settings
build command:  npm run build -w apps/pages-remix-a
build output directory: apps/pages-remix-a/build/client
root directory: (empty)

### Logs
Using v2 root directory strategy
Checking for configuration in a wrangler.toml configuration file (BETA)
No wrangler.toml file found. Continuing.
Executing user command: npm run build -w apps/pages-remix-a

> build
> remix vite:build
Finished
Found _worker.js in output directory. Uploading.
✨ Compiled Worker successfully
## From monorepo root
### Settings
build command:  npm run build -w apps/pages-remix-a
build output directory: apps/pages-remix-a/build/client
root directory: (empty)

### Logs
Using v2 root directory strategy
Checking for configuration in a wrangler.toml configuration file (BETA)
No wrangler.toml file found. Continuing.
Executing user command: npm run build -w apps/pages-remix-a

> build
> remix vite:build
Finished
Found _worker.js in output directory. Uploading.
✨ Compiled Worker successfully
3 replies
CDCloudflare Developers
Created by JFSIII on 7/28/2023 in #workers-help
Tail worker stopped working between deploys (~a week apart) without any code changes
1) I have a worker that is using itself as a tail worker. Call it worker-a 2) the worker with that setup was initially deployed ~2 weeks ago and then a few more times with code changes over the next week (up to ~1 week ago) 3) those deploys sent logs to datadog for ~2 weeks but stopped when we deployed yesterday. 4) The only difference between the working week old code and yesterday was the version number for our release inside a package.json. In other words, no dependencies change, no library or app code changed. 5) A different worker, worker-b, was using worker-a as its Tail Worker and it continued to sends logs to datadog for almost a day after worker-a stopped logging. worker-b only stopped when it's week-old deployment was replaced. In this case, it was identical code to the working code. Literally just wrangler deployed the same SHA again The workers otherwise seem to behave as expected. There's just zero logs coming into datadog and the gaps start at the same time as the worker deployments. The (total?) lack observability for tail workers makes this extra challenging. I don't know if code inside the tail worker is failing or otherwise logging helpful info. Just that logs are down to zero. Are there any theories on what the issue could be? Any thing I could do to further debug and/or narrow it down? Can I give someone here my account id and some worker names and have them look into it, or is sending a "usually takes three days" support ticket the only option?
1 replies
CDCloudflare Developers
Created by JFSIII on 7/14/2023 in #workers-help
Is it ok to have fetch and tail in a single worker?
I have it working fine, but I wondered if there's any reason no to or anything to watch out for, etc.
2 replies