| --- Log opened Tue Apr 04 00:00:24 2023 |
| 00:22 | | himi [sjjf@Nightstar-1drtbs.anu.edu.au] has joined #code |
| 00:22 | | mode/#code [+o himi] by ChanServ |
| 00:38 | | himi [sjjf@Nightstar-1drtbs.anu.edu.au] has quit [Ping timeout: 121 seconds] |
| 01:08 | | Kizor_ [a@Nightstar-nfsqa7.yok.fi] has quit [Ping timeout: 121 seconds] |
| 01:23 | | Kizor [a@Nightstar-nfsqa7.yok.fi] has joined #code |
| 01:46 | | gizmore|2 [kvirc@Nightstar-gckocs.dip0.t-ipconnect.de] has joined #code |
| 01:48 | | gizmore [kvirc@Nightstar-l5lvbi.dip0.t-ipconnect.de] has quit [Ping timeout: 121 seconds] |
| 02:41 | | himi [sjjf@Nightstar-v37cpe.internode.on.net] has joined #code |
| 02:41 | | mode/#code [+o himi] by ChanServ |
| 03:04 | | Degi [Degi@Nightstar-vplejk.pool.telefonica.de] has quit [Ping timeout: 121 seconds] |
| 03:05 | | Degi [Degi@Nightstar-tehkak.pool.telefonica.de] has joined #code |
| 04:36 | | Kizor [a@Nightstar-nfsqa7.yok.fi] has quit [Ping timeout: 121 seconds] |
| 08:38 | | Kizor [a@Nightstar-nfsqa7.yok.fi] has joined #code |
| 08:39 | | Emmy [Emmy@Nightstar-qo29c7.fixed.kpn.net] has joined #code |
| 08:41 | | Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has joined #code |
| 08:41 | | mode/#code [+qo Vornicus Vornicus] by ChanServ |
| 11:12 | < abudhabi_> | I am very angry at Zimarev and whoever else decided that the v107 breaking changes were a good idea. |
| 11:12 | < abudhabi_> | (RestSharp, I mean.) |
| 11:13 | < abudhabi_> | It's like python 2 vs python 3 but worse. |
| 11:13 | < abudhabi_> | By all means, get rid of underlying insecure garbage the project uses. But DON'T CHANGE THE WHOLE FUCKING INTERFACE. 😠|
| 11:14 | < abudhabi_> | "Oh, you used our public interfaces? Fuck you." |
| 11:14 | < abudhabi_> | "Oh, you liked setting base url after instantiation? Fuck you." |
| 11:16 | < abudhabi_> | "Oh, you would like to avoid having to use another third party library to make ours mockable? Fuck you." |
| 11:17 | < abudhabi_> | "Oh, you want to use dependency injection for our client? Fuck you." |
| 11:18 | < abudhabi_> | "Oh, you don't want to make a custom wrapper around the client like it's a piece of shit? Fuck you." |
| 11:45 | | abudhabi__ [abudhabi@Nightstar-j39vd4.adsl.tpnet.pl] has joined #code |
| 11:48 | | abudhabi_ [abudhabi@Nightstar-ej562v.adsl.tpnet.pl] has quit [Ping timeout: 121 seconds] |
| 13:42 | | Kizor [a@Nightstar-nfsqa7.yok.fi] has quit [Ping timeout: 121 seconds] |
| 16:17 | | Emmy [Emmy@Nightstar-qo29c7.fixed.kpn.net] has quit [NickServ (RECOVER command used by M-E)] |
| 16:17 | | Emmy [Emmy@Nightstar-qo29c7.fixed.kpn.net] has joined #code |
| 16:23 | | Netsplit Krikkit.Nightstar.Net <-> Deepthought.Nightstar.Net quits: @celticminstrel, @McMartin, Degi, @ErikMesoy, @Kindamoody |
| 16:27 | | Netsplit over, joins: Degi, &McMartin, @ErikMesoy, @celticminstrel, @Kindamoody |
| 18:11 | | Kizor [a@Nightstar-nfsqa7.yok.fi] has joined #code |
| 19:25 | <@mac> | abudhabi__: Sometimes you need to bite the bullet and change your interface. Like, say, Python 2 vs. Python 3. Modern Python has added a lot of powerful and useful language features which simply could not have been implemented if they were still stuck trying to maintain backwards compatibility with Python 2 syntax. |
| 19:26 | <@mac> | (I'm not familiar with RestSharp, so I can't comment if it was Worth It in your particular case. But in general, there are definitely times when such things must be done.) |
| 19:27 | <@mac> | --- |
| 19:27 | <@mac> | Need some Windows sysadmin advice. A few minutes ago, my laptop suddenly hibernated for no appearent reason. |
| 19:27 | <@mac> | This has happened a couple times before. |
| 19:29 | <@mac> | I've got a couple guesses as to possible causes, including some rogue scheduled task, or simply a problem in the physical switch under the power button sending false-positives. |
| 19:30 | <@mac> | Is there some log somewhere I can check to determine where the command to hibernate came from? |
| 19:30 | <@mac> | If it is a scheduled task, where should I look for it? |
| 19:31 | <@mac> | (HP EliteBook 850 G6 running Win10, if that's relevent.) |
| 19:48 | < Emmy> | task scheduler (just type it in the start menu) should generally show any scheduled events |
| 19:50 | <@Tamber> | anything in the event-log? |
| 19:51 | < Emmy> | if any event is logged, iit might show in the event viewer under > Windows Logs > System |
| 19:56 | <@mac> | Aha! Thank you. Event log shows it... |
| 19:56 | <@Tamber> | \o/ |
| 20:00 | <@mac> | 2:17:14: Power source change |
| 20:00 | <@mac> | 2:17:14: Critical Battery Trigger Met |
| 20:00 | <@mac> | 2:17:15: Power source change |
| 20:00 | <@mac> | 2:17:28: The system is entering sleep. Sleep Reason: Battery |
| 20:00 | <@Tamber> | Oho |
| 20:01 | <@mac> | So, it switched to battery power momentarily, during which time it measured the battery level as critically low and dutifully put the system to sleep. |
| 20:02 | <@mac> | My battery currently reads 100% and I've been plugged in this whole time, so that low battery reading was clearly spurious. |
| 20:04 | <@mac> | I also didn't notice a power glitch - the lights didn't dim and my screen didn't die, that I noticed at least - so its possible the switch to battery power was itself an error. |
| 20:06 | <@mac> | Not sure what to do with this information, though. I don't want to disable low-battery shutdown entirely. |
| 20:07 | <@mac> | The obvious solution would be something like 'if you see a low battery, wait 5s and check again; only shut down if the battery still reads low'. |
| 20:09 | <@mac> | But I've no idea how I might do anything like that. |
| 20:10 | <@mac> | Actually, what I'd /like/ to do is 'If you see a low battery, give me a pop-up with options to either sleep or ignore it; if I don't make a selection in 30s default to sleep'. Honestly, I'm not sure why that isn't the default behaviour; its a lot more user-friendly than 'immediate shutdown with warning or message'. |
| 20:19 | < abudhabi__> | mac: The changes are so bad that they were (regretfully only) partly reverted two versions later. |
| 21:08 | | Kizor [a@Nightstar-nfsqa7.yok.fi] has quit [Connection closed] |
| 21:11 | | Emmy [Emmy@Nightstar-qo29c7.fixed.kpn.net] has quit [Ping timeout: 121 seconds] |
| 21:20 | | Kizor [a@Nightstar-nfsqa7.yok.fi] has joined #code |
| 21:53 | | Kizor [a@Nightstar-nfsqa7.yok.fi] has quit [Ping timeout: 121 seconds] |
| 21:54 | | Kizor [a@Nightstar-nfsqa7.yok.fi] has joined #code |
| 22:08 | < Alek> | mac: how old is the battery and laptop? |
| 22:09 | < Alek> | also I'd look at the contacts, see if they need cleaning. |
| 22:09 | < Alek> | just my 2c |
| 22:10 | <@mac> | Alek: 3 years old. And this model doesn't have a removable battery, so no contacts there. |
| 22:11 | < Alek> | eq |
| 22:11 | < Alek> | ew |
| 22:14 | < Alek> | too many possibilities in my experience. the power cable/brick, the power port, the internal battery, maybe even something in the power circuits is intermittently failing... or even something else, like in the software. |
| 22:21 | <@mac> | Alek: There's definitely /some/ internal error. The system thought my battery was critically low when it was actually fully charged; there's no way a malfunctioning power brick could cause that. |
| 22:22 | <@mac> | So either the battery, the circuitry, or the software. |
| 22:24 | <@mac> | It's possible there is additionally some problem in the brick or port which caused the momentary switch to internal power, but it's equally possible that that was cause by the aforementioned internal fault or by a genuine power flicker. |
| 22:26 | <@mac> | And even if there is a fault in the brick or the port, as long as it works /most/ of the time, I don't care about the occasional loss of mains power. |
| 22:47 | | himi [sjjf@Nightstar-v37cpe.internode.on.net] has quit [Ping timeout: 121 seconds] |
| --- Log closed Wed Apr 05 00:00:26 2023 |