Every weird test returns false, and Steven keeps breaking expectations.

#coding #debugging #javascript

Coding bugs still make me yell at Python sometimes today.

#coding #python #debugging

Just wasted an hour or more debugging a flatpak extension problem because I was building the extension on a different machine 🤦 clearly sleep is necessary, but it works now 😜

#pidgin #opensource #debugging

In Defold 1.12.0, there’s a new Breakpoints tab that lets you manage all your breakpoints in one place, including conditional ones, for easier debugging 🪲

Have you tried it yet? What’s your favorite use case?

#defold #gamedev #indiedev #debugging #programming #lua #coding

Monitor (The tool). Stop debugging with "Notify()" messages! Use the Monitor tool in Power Apps to see the network trace. You can see exactly how long the data retrieval took and which query is slowing you down. It’s the F12 of Power Platform.

#Debugging #ProTips #PowerApps

Is your code showing up as a jumble of weird symbols? 😵‍💫
Your HTML might be encoded, not broken.

Decode & clean your markup properly 👇
https://genoralab.com/en/tools/html-encoder

#WebDevelopment #HTML #Frontend #DevTools #CleanCode #Debugging #Coding

Sự sửa lỗi hiệu năng ngớ ngẩn nhất: Bài viết từ /u/Kyn21kx chia sẻ câu chuyện về một cách tối ưu hóa hệ thống gây tranh cãi, kèm ví dụ từ blog computergoblin. #PerformanceFix #Debugging #Lập_trình #Hiệu_năng

https://www.reddit.com/r/programming/comments/1qrysmp/the_dumbest_performance_fix_ever/

It seems like I managed to troubleshoot something!

I "recently" moved my Radeon RX 9060 XT GPU from my Windows gaming PC to my Linux box so I could test how well games run on Proton. There was just one extremely annoying problem: if I had both of my monitors connected, one of them started repeatedly disconnecting. There was no system logs or dmesg output, monitor just flickers. Everything worked in previous PC: same monitors and same cables, just different OS.

So I have been running with only one monitor for while because games have been running really well on this machine (even though CPU and RAM are not near the ones in the Windows box). Which is lovely! But this monitor situation has been bothering me more and more as time went on.

Debugging these kind of display problems is bit painful for me as flickering monitors can trigger migraine and low refresh rates trigger dyslexia.. which in turn can trigger migraines. So I kinda had to collect some spoons and annoyance/spite for debugging to happen. Well, spite was collected and it was time to collect some observations:

• one of the monitors started flickering, not both of them
• display refresh rate list was bit weird looking 143.98, 120, 59.95
• having same/different refresh rates didn't have effect
• curiously having 59.95 on both monitors was stable
• everything above repeats on KDE and Gnome, both on Wayland
• this is not solution though, I can't stand the 60hz lagging cursor (and absolutely no-go for games). Also it tires eyes quicker -> migraine territory
• so maybe GPU cannot keep the refresh rate stable enough and monitor does not like it?
• could also explain why there is no log output, happens at too low level for default log levels?
• time to enable "variable refresh" in monitor settings and put "adaptive sync - always" on
• idea was that if refresh rate doesn't stay stable but monitor somewhat expects this, it might be fine?

....aaaaaand it seems to work? So far there hasn't been monitor flickering/disconnecting. Haven't been driving GPU hard yet though, so needs some more testing to see if this was the solution. Got bit of migraine buildup from this, but worth it if this works.

#amdgpu #debugging