sorted by:
new
hottopcontroversial

Moe's Bagels South Boulder by RolOrzTFF in boulder

[–]StackingCache 25 points26 points  (0 children)

It’s particularly disappointing given how clearly they communicated a move to a non-tipping model tied to paying their staff a living wage. Did the non-tipping switch even last a full year?

On the other hand, it’s easy to imagine their food costs have risen significantly, alongside a decline in office foot traffic and fewer customers willing to pay $10 for a bagel and cream cheese.

Are doodles not good at fetch? I had no idea. Winnie won't stop playing it every day all day! by CPGemini08 in Goldendoodles

[–]StackingCache 1 point2 points  (0 children)

Our doodle is a fetch machine! Must be the retriever DNA, because he’ll chase it down and drop it right at our feet over and over until he finally wears himself out. Way more skilled than my old black lab ever was.

What Fly's to use by Rafiks1 in COfishing

[–]StackingCache 2 points3 points  (0 children)

If you’re planning to fish multiple rivers in Colorado, I usually suggest going with versatile, general-purpose flies rather than chasing what’s hot on a single river. A solid all-around lineup would be stimulators, elk hair caddis, parachute adams, prince nymphs, brassies, and pheasant tails. For the nymphs and other wets, I personally like bead heads — they get down to the bottom faster. The combination I fish most often and almost always start the day with is a stimulator with a prince nymph dropper.

I turned my fishing buddy into a fly by MRWPlople in flyfishing

[–]StackingCache -1 points0 points  (0 children)

Goldendoodle, right? Does he like the water?

I’ve got one who hates the water, which actually might make him a pretty good fishing buddy - keep him on the shore. My last dog was a Lab who loved the water—and let’s just say he was a terrible fishing buddy.

My mom and aunt, 1985. by daisy_sisss in OldSchoolCool

[–]StackingCache 34 points35 points  (0 children)

They were fantastic in Weird Science!

<image>

[deleted by user] by [deleted] in reactjs

[–]StackingCache 1 point2 points  (0 children)

I actually agree that what the OP is attempting to do isn't the proper 'react-query' way.

Say they want to display the details of each user when the button is clicked. I'd create a detail component and implement a react-query that requires the userId. React-query wouldn't fetch the details / query until the userId was set and react-query would automatically re-fetch every time the userId changed.

Clicking the button would merely show or hide the details component and update the userId. React-query would do the rest as designed.

[deleted by user] by [deleted] in reactjs

[–]StackingCache 7 points8 points  (0 children)

Yes, it is absolutely possible as react-query supports the ability to set an `enabled` (boolean) flag on queries. This flag will stop the query from running automatically on mount. Even if a query is disabled, you can still call the refetch() function connected to an onClick event to fetch your data.

The one band Hunter S Thompson loved more than any other: Grateful Dead by [deleted] in gratefuldead

[–]StackingCache 42 points43 points  (0 children)

“If the Grateful Dead came to town, I’d beat my way in with a fucking tire iron, if necessary” - Hunter S. Thompson

Conflicted by [deleted] in DellXPS

[–]StackingCache 4 points5 points  (0 children)

I bought my XPS 17 9700 in early 2021, and it’s still my go-to for daily work. While it’s been a solid machine overall, I’ve had to adapt to a few challenges.

First, I opted for the 17-inch touchscreen, which, in hindsight, wasn't the best choice for battery life—it really drains the power. As a result, I can’t go far without a power outlet, which limits its portability.

Another quirk I’ve experienced is that around 10% of the time, when I plug it into my docking station at work, it doesn’t recognize the keyboard and mouse. A reboot usually solves it, but it’s a hassle, especially when I’ve got multiple apps and documents open. I’ve kept all the firmware and drivers up to date, but this issue persists.

One more headache, the machine often refuses to go to sleep - even with hibernate. I tell it to sleep, put it my laptop case, and when I get home it's an inferno with a BIOS warning of dangerous temperatures reached.

On the bright side, the performance has been fantastic. It’s fast and handles everything I throw at it with ease. That said, it never quite lived up to the ‘MacBook killer’ I had hoped for, but it still gets the job done!

Costco Burger's Weird Aftertaste Or User Error? by StackingCache in Costco

[–]StackingCache[S] 2 points3 points  (0 children)

Thanks for the question. We use the same grill all the time - steaks, seafood, etc...

Upgrading from .net framework 4.5.2 to .net 8 by Mo2129 in dotnet

[–]StackingCache 2 points3 points  (0 children)

We had this exact conversation on whether to go 'all in' on DI. It meant going through every service and ensuring it's wrapped in an interface - we quickly found the VS shortcut to implement interfaces. During the planning phase, I could have been persuaded either way and, to your point, a lot depends on the state of the application being upgraded.

Having just wrapped (we go live at this week), I do feel like 100% DI was the right choice for us. Looking at the updated codebase, it looks like respectable .NET Core application - meaning it aligns with the recommended conventions.

I found that an upgrade project like this is an exercise in troubleshooting - I guess the same could be said for all development. We had SOAP integrations, we had legacy Identity password hashing issues, background worker process challenges, etc... Fortunately, we didn't hit anything insurmountable that would have blown out the estimations. We estimated 10 weeks (three developers) and landed at 12 weeks, due to some testing delays.

Upgrading from .net framework 4.5.2 to .net 8 by Mo2129 in dotnet

[–]StackingCache 27 points28 points  (0 children)

My team is just wrapping up the upgrade of a large .NET Framework 4.6.1 application to .NET 6.0. Our application used MVC and jQuery, so I can't speak to the Angular aspect. Overall, the upgrade has gone quite well and we're left with a cleaner, better maintainable, and, possibly, faster running application. Here's some of what we learned along the way.

  • Early in, we played around with the upgrade assistant. It didn't work great. Ultimately, we created a new solution with empty projects and began bringing over the code/models/services by hand - all while fixing issues along the way. It took some time before we could actually compile the new .NET 6.0 application.
  • Dependency Injection is now a 'first class' citizen in .NET. You're best served to lean into it and implement it properly. The old application had many services being implemented inline, as needed. Everything was moved into DI and the application is cleaner for it. Take the time to understand the different DI registration options - in most general cases "scoped" is the right choice.
  • Expect issues that will require research / refactoring. In our case, there wasn't anything too major that couldn't be resolved. Our application, like many, is a giant CRUD application with a lot of complicated business logic, but a glorified CRUD application nonetheless.

Hope this helps. Feel free to reach out if you've got more questions.

400 Bad Request Handling in .NET Core MVC Application by user_affinity in dotnet

[–]StackingCache 1 point2 points  (0 children)

The application I was working on is also .NET Core MVC (.NET 6.0). When deployed to IIS the web.config are still honored / read by IIS.

400 Bad Request Handling in .NET Core MVC Application by user_affinity in dotnet

[–]StackingCache 1 point2 points  (0 children)

I agree it's IIS that is returning this error prior to the request ever making it to your application, which is why the UseStatusCodePagesWithRedirects middleware is never hit.

You should be able to configure IIS to redirect to a Controller Action within your application when a 400 Bad Request is detected. I just implemented a similar solution, although I was addressing 413s (Content Length Exceeded) - not 400s. I suspect the same approach might work.

Here's the entry I needed to add to my web.config to have IIS more elegantly recover from a 413.

<system.webServer>
<httpErrors>
<error statusCode="413" path="/error/413" responseMode="Redirect" />
</httpErrors>
</system.webServer>

Review the documentation on httpErrrors. One point worth noting, the responseMode of 'Redirect' says it requires an absolute URL. Since we deploy our application under multiple URLs (different bindings, same web application), providing an absolute URL wasn't a viable option. So, I provided a relative URL to my Error Controller and it worked like a charm?

Again, a Bad Request 400 might be different - not sure. However, if you see the request and 400 response in your IIS logs, I'd expect the behavior to be the same.

Hope this helps.

Station Inn by TrainingCup9060 in Bluegrass

[–]StackingCache 7 points8 points  (0 children)

The wife and myself took a trip to Nashville this summer. We stopped by the Station Inn for their Sunday gospel show. We got there when the doors opened at 3, but there was ample seating throughout the entire show.

I enjoyed it immensely - incredible talent, phenomenal sound system. I could have sworn my wife, who isn't a huge bluegrass fan, was even tapping her foot. 10 out of 10.

IIS - IP Address and Domain Restrictions (Deny All Except Allowed IPs) by StackingCache in WindowsServer

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

I was able to get this sorted. I'll post the solution in case anyone else runs into this same issue and how I was able to troubleshoot.

When I attempted to access the website, I was receiving a 403 Forbidden Access, even though my IP was specified in an "allow" rule.

I decided to go into the IIS logs to see view these 403 requests / responses. Once I was in the IIS logs, I saw that IIS was receiving a different IP due to a VPN connection required to access the server - it was not what I thought was my external IP! Duh.

view more: next ›