Previous day | Jump to hour: 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 | Next day

Seconds: Show Hide | Joins: Show Hide | View raw
Font: Serif Sans-Serif Monospace | Size: Small Medium Large

Click in the nick column to highlight everything a person has said.
The Logo icon identifies that the person is a core developer (has commit access).

#rockbox log for 2020-06-26

00:05:48 Join michaelni [0] (
00:08:34fs-bluebotBuild Server message: Build round completed after 1507 seconds.
00:08:35fs-bluebotBuild Server message: Revision 7c29125 result: 4 errors 0 warnings
00:09:27fs-bluebotBuild Server message: New build round started. Revision aa4ec91, 292 builds, 9 clients.
00:19:57***Saving seen data "./dancer.seen"
00:27:34 Quit __Bilgus_ (Ping timeout: 245 seconds)
00:27:38 Quit koniu (Remote host closed the connection)
00:27:48fs-bluebotBuild Server message: Build round completed after 1100 seconds.
00:27:49fs-bluebotBuild Server message: Revision aa4ec91 result: All green
00:28:05 Join koniu [0] (~koniu@gateway/tor-sasl/koniu)
01:19:18 Join ZincAlloy [0] (
01:24:13 Quit ZincAlloy (Ping timeout: 264 seconds)
01:40:26 Join ZincAlloy [0] (~Adium@2a02:8108:943f:d824:6c29:e41:4583:b836)
01:45:01 Quit ZincAlloy (Ping timeout: 272 seconds)
02:12:22 Quit ufdm (Ping timeout: 256 seconds)
02:20:01***Saving seen data "./dancer.seen"
03:50:42 Quit dys (Ping timeout: 265 seconds)
04:12:17 Quit craftyguy (Quit: WeeChat 2.8)
04:13:39 Join craftyguy [0] (~craftyguy@qutebrowser/dev/craftyguy)
04:16:51 Join sakax [0] (~r0b0t@unaffiliated/r0b0t)
04:20:04***Saving seen data "./dancer.seen"
04:47:49 Join pamaury [0] (~pamaury@rockbox/developer/pamaury)
05:25:45 Join petur [0] (~petur@rockbox/developer/petur)
05:53:03 Join dys [0] (~dys@2003:5b:203b:100:a64c:c8ff:fef4:13a6)
06:00:34 Quit petur (Remote host closed the connection)
06:20:08***Saving seen data "./dancer.seen"
07:14:33fs-bluebotBuild Server message: New build round started. Revision d9e084b, 292 builds, 10 clients.
07:20:26 Join Soap_ [0] (~Soap@rockbox/staff/soap)
07:32:14 Join ac_laptop [0] (~ac_laptop@
07:33:52fs-bluebotBuild Server message: Build round completed after 1158 seconds.
07:33:53fs-bluebotBuild Server message: Revision d9e084b result: All green
07:58:54 Join massiveH [0] (
08:05:37 Quit Oksana (Ping timeout: 264 seconds)
08:20:10***Saving seen data "./dancer.seen"
08:32:59 Quit ac_laptop (Quit: WeeChat 2.8)
08:33:17 Join ac_laptop [0] (~ac_laptop@
08:35:08 Quit dys (Ping timeout: 260 seconds)
08:37:44 Quit sakax (Remote host closed the connection)
08:40:38gevaertsWell, that *is* the documented hard reset sequence
08:41:10*gevaerts was going to type that yesterday and the pressed enter accidentally today...
08:43:32 Quit blackyus17 (Ping timeout: 256 seconds)
08:47:17 Join blackyus17 [0] (
09:20:10 Quit massiveH (Quit: Leaving)
09:34:23 Join eevan [0] (~eevan@
09:57:02 Join dys [0] (~dys@2003:5b:203b:100:a64c:c8ff:fef4:13a6)
09:57:34 Quit mendel_munkis (Ping timeout: 240 seconds)
10:01:18 Quit pamaury (Quit: this->disconnect())
10:04:09 Join pamaury [0] (~pamaury@rockbox/developer/pamaury)
10:08:47 Join __Bilgus_ [0] (41ba23be@
10:13:36 Quit speachy (Read error: Connection reset by peer)
10:17:41 Join speachy [0] (~speachy@
10:20:13***Saving seen data "./dancer.seen"
10:56:29 Join mendelmunkis [0] (
11:08:36 Join ZincAlloy [0] (
11:13:19 Quit ZincAlloy (Ping timeout: 260 seconds)
11:22:34 Quit ac_laptop (Ping timeout: 240 seconds)
11:24:09 Join ZincAlloy [0] (~Adium@2a02:8108:943f:d824:b404:47f:a1b8:22f2)
11:24:45 Join ac_laptop [0] (~ac_laptop@
11:37:16 Quit megal0ma1iac (Ping timeout: 256 seconds)
12:20:14***Saving seen data "./dancer.seen"
12:40:52 Join jdarnley [0] (
12:41:34 Quit J_Darnley (Ping timeout: 240 seconds)
13:39:24 Quit dys (Ping timeout: 244 seconds)
13:43:27__Bilgus_found another bug in buflib if you pass too small a buffer to init it crashes when it tries to free up space
13:44:46__Bilgus_I'm not sure if I should make it panic or if I should let it fail and pass the error back up to the caller
13:46:06__Bilgus_on one hand the panic has less overhead but on the other its not necessarily an absolute failure for anything else already allocd
13:53:58 Quit JanC (Remote host closed the connection)
13:54:20 Join JanC [0] (~janc@lugwv/member/JanC)
14:07:15 Join dys [0] (
14:20:18***Saving seen data "./dancer.seen"
14:24:14 Quit __Bilgus_ (Ping timeout: 245 seconds)
15:53:03 Quit koniu (Ping timeout: 240 seconds)
15:54:43 Join koniu [0] (~koniu@gateway/tor-sasl/koniu)
16:06:26speachydoes the panic tell us what/where that bad call was made?
16:20:20***Saving seen data "./dancer.seen"
16:32:12 Join PimpiN8 [0] (~PimpiN8@
17:03:24 Quit PimpiN8 (Remote host closed the connection)
17:14:02 Join MrZeus [0] (
17:50:53 Join __Bilgus_ [0] (41ba23be@
17:51:22__Bilgus_speachy: no it wouldn't show where it was called only the parameters it was called with like the other buflib panics
17:51:38 Join Oksana [0] (~Wikiwide@Maemo/community/ex-council/Wikiwide)
17:55:16mendelmunkisare there instructions for building the manual?
18:20:22***Saving seen data "./dancer.seen"
18:37:37 Quit _3dsv (Ping timeout: 265 seconds)
18:39:31 Join _3dsv [0] (
18:42:40 Quit pixelma (Quit: .)
18:42:40 Quit amiconn (Quit: - Chat comfortably. Anywhere.)
18:43:25 Quit __Bilgus_ (Ping timeout: 245 seconds)
18:43:32 Quit Rower- (Ping timeout: 258 seconds)
18:43:49 Quit _3dsv (Ping timeout: 246 seconds)
18:45:30 Join pixelma [0] (marianne@rockbox/staff/pixelma)
18:45:30 Join amiconn [0] (jens@rockbox/developer/amiconn)
18:46:10 Join _3dsv [0] (
18:51:14 Quit _3dsv (Ping timeout: 240 seconds)
18:51:29 Quit pixelma (Quit: .)
18:51:29 Quit amiconn (Quit: - Chat comfortably. Anywhere.)
18:51:45 Join amiconn [0] (jens@rockbox/developer/amiconn)
18:51:45 Join pixelma [0] (marianne@rockbox/staff/pixelma)
18:54:53 Join _3dsv [0] (
19:08:54 Quit MrZeus (Ping timeout: 256 seconds)
19:31:41__builtinmendelmunkis: `make manual'
19:32:25mendelmunkisyeah I figured that out. I'm trying to figure out a nice way to get all the errors and warnings.
19:35:38 Quit pamaury (Ping timeout: 264 seconds)
19:42:33 Join sakax [0] (~r0b0t@unaffiliated/r0b0t)
19:42:46 Quit ZincAlloy (Quit: Leaving.)
19:57:09__builtinhmm, I'd like to make the software poweroff overridable from plugin code
19:58:23__builtinit's a bit annoying when a plugin has a cursor and the device shuts down from you holding it too long
20:20:24***Saving seen data "./dancer.seen"
20:21:15 Join massiveH [0] (
20:56:05__builtincan someone take a look at g#2446?
20:56:06fs-bluebotGerrit review #2446 at : button: allow disabling software poweroff by Franklin Wei
20:57:24fs-bluebotBuild Server message: New build round started. Revision f49442d, 292 builds, 10 clients.
21:01:16speachymy main concern about it is it could leave to behavioral differences between sw-controlled poweroff and hard-poweroff operation
21:02:13speachyalso, doesn't some hardware have a hardware-controlled poweroff/reset failsafe? Wouldn't want to trip over that in a plugin either. :)
21:02:48 Quit sakax (Remote host closed the connection)
21:03:50__builtinwhat do you mean by behavioral differences?
21:05:35__builtinthe mechanism of hardware vs. software poweroff is already different, of course
21:05:57speachyI guess plugins have unique keymaps per device anyway
21:06:36speachybut it does lead to not being able to power off a device consistently no matter the context.
21:07:45__builtinthat's true to an extent I suppose
21:07:53__builtinyou'll always have the hard-reset sequence
21:12:08speachyoh, one more thought −− we should unconditionally force sw_poweroff back on when plugins terminate.
21:12:38__builtinrather than the disable/restore mechanism I've got now?
21:12:54speachyas a backstop from the plugin misbehaving
21:13:48__builtinprobably a better option, yes
21:14:33speachythough since you mention it, Can you think of a scenario where a plugin would want to ever want to toggle it back and forth, rather than "always off while we're running"?
21:15:21__builtinyes, actually
21:15:36__builtinin going between "in-game" and menu sections
21:15:45speachyah, okay.
21:15:50*speachy scraps that line of thought
21:16:53speachywas thinking it might be saner to add a flag to the plugin header so the rb core would manage the sw_pwoeroff state directly rather than leaving it up to plugins.
21:20:05fs-bluebotBuild Server message: Build round completed after 1361 seconds.
21:20:07fs-bluebotBuild Server message: Revision f49442d result: All green
21:25:54speachyI have to say, it's nice to see the recent commit logs filled with names other than mine
21:29:31__builtinI think I said that before
21:32:19__builtinalso, regarding the unconditional restore, I don't think it's necessary
21:32:54__builtinwe already have precedent for settings which are the plugin's responsibility to restore (e.g. backlight)
21:45:41*speachy nods.
21:48:43__builtinit might be nice to expose this as a user-facing setting eventually
21:57:10 Quit prg318 (Quit: ZNC 1.7.5 -
21:58:12 Join prg318 [0] (~prg@deadcodersociety/prg318)
22:20:28***Saving seen data "./dancer.seen"
23:04:41 Quit Oksana (Read error: Connection reset by peer)
23:33:06 Join reductum [0] (
23:43:57 Quit TheSeven (Ping timeout: 260 seconds)
23:44:22 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven)

Previous day | Next day