Does anyone have an idea on how to get details about internal server errors in the #Microsoft#Graph API?
The problem: We make a PATCH request on a specific resource. The request is correct (following the documentation) and successful (all changes are applied), but nevertheless we receive an internal server error in response with no details.
We've had to deal with a lot of bugs in the API, but if you can't distinguish successful requests from incorrect ones, that's very unfortunate.
After #Spotify canceled me because I didn't want to accept their price increase, I went without it for exactly 15 days… Have now upgraded back to Premium. 😂
We have successfully completed the first day of ISO 27001 certification. Went really well after not knowing exactly what to expect. Now I'm a little more relaxed about the last two days.
#BaldursGate3 on #PS5 is truly impressive and incredibly addictive. In the last 24 hours I have played more than 16 hours. :)
I wouldn't have thought that the controls could be implemented so well and intuitively. Well done!
I highly recommend it, although there are still some bugs, some of which are really annoying - most of them could be worked around, but once I had to restart the PS5 (so saving often is advisable).
Creating a library to work with #timezones before they became part of PHP (think they were added in PHP 5.1). It had a lot of bugs but worked well enough for about ten years, even after timezones have been added to PHP (because the library was used everywhere and it took some time to completely replace it).
Updating the timezones rules (several times a year) was awful.
@ziegenberg Forwarding emails based on couple of rules while changing headers From / To. This around 2005. Often had issues with email attachments or recomposing headers from ill-behaved clients such as Outlook Express.