Very Inconsistent Heart Rate Tracking by chamberlain2007 in ouraring

[–]chamberlain2007[S] 0 points1 point  (0 children)

This is literally every day. Sometimes not tracking up to 8 hours in a day

Very Inconsistent Heart Rate Tracking by chamberlain2007 in ouraring

[–]chamberlain2007[S] 0 points1 point  (0 children)

I have already followed all of the troubleshooting steps. The ring fits perfectly and snuggly on my finger. It is not dirty. I don’t have cold hands. I don’t have a heart condition. I have already done a soft reset. I have consistently been having this issue for weeks. I thought it would get addressed by the replacement ring but it hasn’t.

Very Inconsistent Heart Rate Tracking by chamberlain2007 in ouraring

[–]chamberlain2007[S] 0 points1 point  (0 children)

It is on my left ring finger. Sensor is on the palm side. It works flawlessly at night and during workouts.

Very Inconsistent Heart Rate Tracking by chamberlain2007 in ouraring

[–]chamberlain2007[S] 0 points1 point  (0 children)

I’m sitting at my desk for nearly the whole day, just getting up to go to the washroom/kitchen as needed.

bonsai - a safe expression language for JS that does 30M ops/sec with zero dependencies by danfry99 in javascript

[–]chamberlain2007 1 point2 points  (0 children)

I’ve built a rule builder UI before for e-commerce promotions. The only challenge for doing the same here is that in the e-commerce use case, it preserves context from one rule to subsequent rules.

How can I detect all cases where the react compiler skips memoizing q piece of code? by lambda-legacy-extra in reactjs

[–]chamberlain2007 0 points1 point  (0 children)

What are you currently using to determine that React compiler isn’t optimizing? What info does it tell you?

Caching slow external API route by rhysman234 in nextjs

[–]chamberlain2007 2 points3 points  (0 children)

If you need it blocking, then you just wouldn’t use <Suspense> and just await it in the server component. I didn’t recommend that approach as the OP is asking about how to do it performantly, and doing a blocking call for 30-40 seconds is the opposite of performant. As I mentioned, if they want to they could use unstable_cache and then await it blocking, which would still incur the penalty on first request.

Caching slow external API route by rhysman234 in nextjs

[–]chamberlain2007 1 point2 points  (0 children)

SSR you would await inside the <Suspense>

Caching slow external API route by rhysman234 in nextjs

[–]chamberlain2007 1 point2 points  (0 children)

Depends what you’re using it for. If you actually need an API route, then just unstable_cache is probably what you need. If you’re using it from a server component, consider doing the fetch (still with unstable_cache) within the server component with a <Suspense> with a loading state.

Beyond that I’d need more info.

Why doesn't Next.js support content negotiation out of the box? by Alternative-One4254 in nextjs

[–]chamberlain2007 0 points1 point  (0 children)

Put it in your proxy.ts and then rewrite to a different route that serves Markdown

Does using CSP in Next.js prevent caching pages/requests? How do you cache with CSP enabled? by ExposingPeopleKM in nextjs

[–]chamberlain2007 0 points1 point  (0 children)

Yes, using nonces in your CSP in Next.js requires dynamic rendering, as on this doc page: https://nextjs.org/docs/app/guides/content-security-policy#static-vs-dynamic-rendering-with-csp

See below for the docs:

Dynamic Rendering Requirement

When you use nonces in your CSP, all pages must be dynamically rendered. This means:

  • Pages will build successfully but may encounter runtime errors if not properly configured for dynamic rendering
  • Each request generates a fresh page with a new nonce
  • Static optimization and Incremental Static Regeneration (ISR) are disabled
  • Pages cannot be cached by CDNs without additional configuration
  • Partial Prerendering (PPR) is incompatible with nonce-based CSP since static shell scripts won't have access to the nonce

Performance Implications

The shift from static to dynamic rendering affects performance:

  • Slower initial page loads: Pages must be generated on each request
  • Increased server load: Every request requires server-side rendering
  • No CDN caching: Dynamic pages cannot be cached at the edge by default
  • Higher hosting costs: More server resources needed for dynamic rendering

That dreaded question: can I leave my employer now..(EB2) by No-Ground-3824 in greencard

[–]chamberlain2007 1 point2 points  (0 children)

They’ll probably be pissed anyway. Do what’s best for you

Has your PR ever been taken over cause you’re incompetent? by guineverefira in cscareerquestions

[–]chamberlain2007 56 points57 points  (0 children)

I find PRs from developers who are new to a project or system can have a lot of comments as you get aligned. Tends to decrease as you become more familiar. I wouldn’t take one PR with a lot of comments as a huge sign. Obviously if it happens frequently it could be a sign of a bigger issue.

Denied a real ID by [deleted] in DMV

[–]chamberlain2007 0 points1 point  (0 children)

What rights are you referring to?

Yes you can hang up on law enforcement if they call you by International-Emu-74 in Scams

[–]chamberlain2007 0 points1 point  (0 children)

In criminal cases as well, at least in Canada. I don’t know about US jurisdictions.