Read article by @neciudan about naming useEffect callbacks. Actually great and simple idea. Now @getsaleor Dashboard will have an @geteslint rule for that
https://t.co/q15w63WTjK
https://t.co/oBHPFOGPVQ
Looks like suddenly @vercel starts injecting `AWS_SESSION_TOKEN` variable into functions, which breaks IAMs. This variable takes precedence over access key secret. Day of debugging 🥲
@ING__Polska 3. Apka mobilna to wrapper na HTML. Zrozumiałe jeśli się nie chce zainwestować w technologie bliższe natywnym, ale błagam, podstawowe CSSy które blokują user-select czy zoom można by dodać...
@ING__Polska 2. Walka z natywnymi inputami HTML. Clipboard highjacking, niedziałające CMD+A itd. Zamiast walidować na "blur", praktycznie nadpisują i psują natywne zachowania kontrolek
@ING__Polska 1. Walka z password managerami poprzez wymuszanie maskowania haseł. Ludzie ustawiają proste hasła, bo te trudne są niemożliwe do spamiętania
#esp#esphome I temporary moved my ESP-based dimmer to another room and it's on wifi now. It failed with OTA update due to "timeout" error. Eventually it happened not to be physical issue (like wifi strength) but software. Restarting ESPHome sever worked for me.
@EuroPromocje próbuje obchodzić zgody marketingowe. Dzwonią "porozmawiać o dostawie" (umówionej podczas zamówienia), żeby robić upselling dodatkowych gwarancji i innych usług.
Nieładnie
@zeeg The decision to rely on OTEL also infers using an unstable, experimental, and apparently broken Next.js instrumentation hook. Btw at Saleor, we managed to set up OTEL with Next without it - by proxying requests just like Sentry pre-8 was doing
@zeeg@mitsuhiko@getsentry Yea, good question. But at least some of them are >1.0.0 and don't introduce BC every release ;)
I was very excited to bump Sentry to 8x due to bundle sizes. It was a huge improvement for our cold starts. Is it possible for you to introduce this to 7x?
Reverted Sentry (js) from v8 to v7. Cold starts in v8 raised by 5 seconds (due to Next.js instrumentation hook setup). Our Open Telemetry setup conflicted with Sentry, making it stop working.
Controversial decision to build last SDK on so many experimental APIs @getsentry
@mitsuhiko@getsentry btw we are OSS, we do now rollback, but if you like to check on larger, real-life stack, you can try here https://t.co/brepTedkbJ
We have custom Otel instrumentation with Next.js. I can help you checking this, I have interest to make it work too :)
@getsentry Also, a huge chunk of open telemetry APIs are pre-1.0.0 and they introduce breaking changes often. We can't pin our own OTEL versions to versions used by Sentry - and most likely they conflict