|
00:10
Sgeo joined
02:04
hulk joined
02:06
kylese left
02:08
Aedil left
03:02
kylese joined
03:03
hulk left
03:15
kylese left,
kylese joined
03:51
oodani left
03:53
oodani joined
04:24
lichtkind_ joined,
El_Che left
04:26
lichtkind left
04:59
abraxxa joined
05:58
Aedil joined
06:28
sibl joined
07:06
sibl left
07:10
sibl joined
08:27
kst left
08:41
Sgeo left
09:12
dakkar joined
10:08
sibl left
11:55
xkr47 left
11:57
zjmarlow joined
12:19
El_Che joined
|
|||
| lizmat | weekly: dev.to/lizmat/cases-of-upper-imn | 12:24 | |
| notable6 | lizmat, Noted! (weekly) | ||
|
12:54
zjmarlow left
13:01
zjmarlow joined
13:02
zjmarlow left
13:03
zjmarlow joined
13:04
abraxxa left
13:06
zjmarlow left
13:45
abraxxa joined
|
|||
| [Coke] | Voldenet++ font listing. | 14:01 | |
|
16:07
librasteve_ joined
16:20
Romanson joined
16:21
human_blip left
16:23
human_blip joined
|
|||
| [Coke] | makes sense. (did our bridge bot lose its name?) | 16:45 | |
| Voldenet | hm, Tiny::HTTP has very weird assumptions for reusing handles that may not work with default scheduler | 17:27 | |
| As long as you start requests on the same thread, you can reuse the handle | |||
| so if you do `my $response = HTTP::Tiny.new.get: 'httpbin.org/get'; await Promise.in(1); $response<content>.decode` it might not work | 17:28 | ||
| in multithreaded scenarios handle should use `react/supply whenever` syntax for handling concurrency, because then handle can be just a single boring process | 17:32 | ||
| that's what Cro does | |||
| (<content>.decode will work, data-callback may not) | 17:36 | ||
|
17:39
dakkar left
|
|||
| ugexe | in the real world Cro is probably the only client you can use multi thread due to openssl | 18:44 | |
| curl based things like HTTP::Tinyish would be fine, but you then have the overhead of spawning processes | 18:45 | ||
|
18:55
nort joined
|
|||
| tbrowder | i've filed an issue with App::Mi6 to allow the default branch (which is currently 'master') to be defined in the 'dist.ini' file with a line like this: 'default-branch = main'. upvotes (or someone taking on a PR) would be helpful. i've started on a PR but stumblng. | 18:58 | |
| *stumbling | 18:59 | ||
| ugexe | you should be doing that at the git level | 19:00 | |
| tbrowder | it's not so easy | 19:01 | |
| ugexe | oh i see what you mean | ||
| it could probably run the command `git config init.defaultBranch` to get the default branch from the repo itself | 19:02 | ||
| "it" being App::Mi6 | |||
| then it works for people who use main or master | |||
| [Coke] | hurm. is our roast default branch mis-configed? (running that in roast gets me main) | 19:38 | |
|
19:41
Romanson left
20:00
abraxxa left
|
|||
| [Coke] | Looks that that doesn't necessarily reflect the github setting. | 20:04 | |
| might need something like `git remote show origin | grep HEAD` (but with cleanup and maybe some work to get 'origin') | 20:05 | ||
|
20:08
abraxxa joined
20:14
abraxxa left
20:15
abraxxa joined
20:27
abraxxa left
20:30
nort left
|
|||
| ugexe | hmm, maybe my example shows what the global default is and not that of the repo you are in | 22:26 | |
| git symbolic-ref --short refs/remotes/origin/HEAD | 22:27 | ||
| that seems to work | 22:28 | ||
|
22:49
arkiuat joined
|
|||