404s on source files, in pkg.go.dev

Source files shown at https://pkg.go.dev/dagger.io/dagger#section-sourcefiles lead to 404s.
example:

error.go

I tried to understand/reverse with @helderco, but did not manage to find how/where to fix (seems related to releases):

The Repository link in picture above
github.com/dagger/dagger/tree/main/sdk/go links to a main branch
the error.go URL links to github.com/dagger/dagger/tree/main/sdk/go/blob/v0.3.1/error.go

We see that the error url == repository url +  blob/v0.3.1/error.go, however, this file is not present in v.0.3.1 on dagger/dagger repo
It does exist on main though, and in go-dagger-skd on v.0.3.1
cc @aluzzardi @vito @sipsma

You can access it here: https://github.com/dagger/dagger/blob/sdk/go/v0.3.1/sdk/go/error.go
I guess the pkg.go.dev doesn't correctly write the full path if the go.mod is not on top of the repo. It just adds the relative path from the go.mod instead of adding the relative path from the repo root.
We should report it upstream.

It didn't seem this issue was reported earlier, so I did: https://github.com/golang/go/issues/56666

@aluzzardi, in order to make this advance. Our current go-source and go-import are composed of such:
     <meta
      name="go-import"
      content="dagger.io/dagger git https://github.com/dagger/dagger-go-sdk"
    />
    <meta
      name="go-source"
      content="dagger.io/dagger     https://github.com/dagger/dagger/tree/main/sdk/go https://github.com/dagger/dagger-go-sdk/tree/main{/dir} https://github.com/dagger/dagger-go-sdk/blob/main{/dir}/{file}#L{line}"
    />

I don't recall the reason why we are referencing the dagger-go-sdk on the go-import (cf. comment)


blog: add post "Getting a Tech Job as an Undergraduate"

New blog post about tips for undergraduates to land a full time job in software engineering.

Thank you so much! :) will note some of the changes for future contributions!


Updating rocm and compiler versions

This PR should do 5 things:

Fix my conflict rule in Umpire's package.py file to actually detect the version of rocm
Add rocm updated versions 5.4.1 and 5.4.3 for tioga
Add the clang@15 compiler associated with rocm 4.5.1 for tioga -----> Will this version also work for 5.4.3?
remove older rocm versions < 5.0 for tioga
Remove older rocm versions < 5.0 for corona

@kab163 My only worry about this is that I am actually updating to 5.4.3 in another branch, and it’s causing failures. TBC...

@kab163 My only worry about this is that I am actually updating to 5.4.3 in another branch, and it’s causing failures. TBC...

I could keep this just at 5.4.1 - but I need at least 5.4.0 to include the RDC fix in rocm

@kab163 I'm just saying please test your change, and I'll trust you with it ;)
If you need help testing it, let me know.

@kab163 I'm just saying please test your change, and I'll trust you with it ;)
If you need help testing it, let me know.

Hmm, ya, when I use the updates I made to this branch in my Umpire branch, I just see:
[exe: spack/bin/spack dev-build --quiet -d /g/g0/belcher6/Umpire -u initconfig 'umpire@develop~shared +fortran +openmp +rocm +device_alloc tests=basic amdgpu_target=gfx906<EMAIL_ADDRESS><EMAIL_ADDRESS>^blt@develop']
==> Error: Spack doesn't support the requested compiler: rocm

Now I'm not convinced these changes will work...

You want rocmcc, not rocm, for the compiler name.


Conti Radar driver question

Hi team!
Can You answer me if it's not difficult?
Can I use this device for launch a radar driver?
I changed this file
can_conf {

  can_card_parameter {
    brand:SOCKET_CAN_RAW
    type: USB_CARD
    channel_id: CHANNEL_ID_ZERO
  }

  enable_debug_mode: false
  enable_receiver_log: false
}

But, when I run the driver, I cannot get data from the radar
System information

OS Platform and Distribution (e.g., Linux Ubuntu 18.04): Linux Ubuntu 18.04
Apollo installed from (source or binary): source
Apollo version (3.5, 5.0, 5.5, 6.0): master

The driver is only tested to work for Conti radar with CAN interface. If you have radars from other manufacturers or with different interfaces, you have to make sure that CAN messages are correctly parsed with the given driver (mostly likely not and you need to implement your own driver).
This issue is being closed. Should you have other issues, please feel to raise new ones. Tnanks for using Apollo.


Can i add padding inside the circular generator?

It seems the text is very large. Is there any way to add padding to it or make the letter a little smaller?

It will support that in the next release.
Soon

is there way to add a gradient color in background?


Remove process.exit when simctl prerequisite does not pass

The init() function will return a shell return code. In the CLI context, when the return code is non-zero, it will then call process.exit with that return code.
Since the behaviour has changed, the version is bumped a major so that dependents don't pick this up automatically and encounter unexpected results.

I am in the process of testing this on macOS, Windows 10 and Linux.


Set locust parameters via env vars & config file

It would be useful to be able to set locust's command line parameters via env vars (particularly to be able to provide defaults, to shorten the command that you have to type).
I suggest we use LOCUST_ for env vars.
Command line should override env vars of course.
I can make a PR if this sounds good to everyone. I'd probably use https://pypi.org/project/ConfigArgParse/ to do it.

I can't think of any drawbacks so I'm +1/+0.

PR:ed. What does +0 mean? :)

What does +0 mean? :)

I believe it's the Django project that uses it (or at least used to use it) to indicate that you are positive to something, but don't feel strongly about it (it wouldn't matter so much to you that you're willing to champion it). I think they havethe policy that a -0 (or -1 obviously) from any core developer would have to be converted to a +0 or +1 before it can get implemented.

Fixed!


[BUG]: Bash exited with code '1'

New issue checklist

[x] I searched for existing GitHub issues
[x] I read pipeline troubleshooting guide
[x] I checked how to collect logs

Task name
Azure Pipeline
Task version
No response
Issue Description
Bash exited with code '1' when running npm install. It breaks all pipelines although I haven't changed any code.
Environment type (Please select at least one enviroment where you face this issue)

[ ] Self-Hosted
[ ] Microsoft Hosted
[ ] VMSS Pool
[ ] Container

Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
I don't know
Relevant log output
https://dev.azure.com/unipet-bespok/25d9a951-b5d0-409a-a1fa-03877f6c61bf/_apis/build/builds/11083/logs/7

Full task logs with system.debug enabled

 [REPLACE THIS WITH YOUR INFORMATION]

Repro steps

Hi @akib1997, sorry for the late answer. I think this is related to this issue: https://github.com/npm/cli/issues/7986
Seems like it has been fixed on the npm side since then. Is the pipeline working for you now?


Added Night Mode

Just like tittle

old shadowware features xd

Not needed to put Visuals::NightMode() somewhere in Hooks.cpp?

what's the point when u already have option to change world color.

Not needed to put Visuals::NightMode() somewhere in Hooks.cpp?

I forget to do this haha

old shadowware features xd

pls give me you dicord thanks. I lost my old discord

Can u add legit aa too?

Can u add legit aa or resolver too?

I can add legit AA. but  for resolver -- I must to learn more about resolver

Can u add legit aa or resolver too?

I can add legit AA. but for resolver -- I must to learn more about resolver

i think it would be good if theres resolver in ragebot like most p2c hehe, but dont worry keep learn
+rep

you are amazing, much love <3

pls give me you dicord thanks. I lost my old discord

itscraused#5786

This pr needs resolver and doubletap(maybe baim key too) then osiris will ready to hvh

This pr needs resolver and doubletap(maybe baim key too) then osiris will ready to hvh

if you tap hs you dont need dt and pasted animfix should do the job for now

add legit aa pls

I'll add legit AA , baim key, damage override key soon

Sorry....

And missed ,total shots,hits shots cout.
I will use ImGui to finish it

are u gonna add legit aa from this pr #1546 or no?

I will use Lbybreaker from there.
Just lbybreaker

Why have all these features in 1 pr?

What its mean missed cout? And i tested this osiris in hvh server ragebot misses even onetap crack

And one more thing in misc when i click enabled he doesn`t enable other function

@Frouk3 merge AA and animfix from #1546 and you can pretty much play hvh with this. I'm able to beat 1tap consistently in mm.

I will use Lbybreaker from there.
Just lbybreaker

his lby doesnt breaking

I will use Lbybreaker from there.
 I'll add antiAim when I have enough time

What its mean missed cout?
It wont change your viewangles

Add ImGui Watermark, same as onetap, etc.
Osiris | 60 fps | 24 ping | 64 tick | <IP_ADDRESS> | 13:37
(mb with colored text)

Add ImGui Watermark, same as onetap, etc.
Osiris | 60 fps | 24 ping | 64 tick | <IP_ADDRESS> | 13:37
(mb with colored text)

i was wondering how to make watermark like this?

Add ImGui Watermark, same as onetap, etc.
Osiris | 60 fps | 24 ping | 64 tick | <IP_ADDRESS> | 13:37
(mb with colored text)

i was wondering how to make watermark style like this

Add ImGui Watermark, same as onetap, etc.
Osiris | 60 fps | 24 ping | 64 tick | <IP_ADDRESS> | 13:37
(mb with colored text)

i was wondering how to make watermark style like this

i think, as Purchase list

yeah first windowflags noinputs ，begin a window then add beginchild, drawlist->addText this would be like otc watermark
I will add it tommorow

Dude u still didint add me on dc im waiting :)

Dude u still didint add me on dc im waiting :)

... I can't connect to dc

Dude u still didint add me on dc im waiting :)

... I can't connect to dc

u live in china? have u use vpn?

Dude u still didint add me on dc im waiting :)

... I can't connect to dc

u live in china? have u use vpn?

haha i have no vpn

watermark ss pls?

老哥 能不能加个独立压枪：）

点击misc会崩溃

老哥 能不能加个独立压枪：）

对于OSIRIS来说
RCS的需求并不大
加了会让你再DEMO里看起来有点诡异

Fixed bugs and I need animation fix to Update Legit AA.
And who can tell me how to get Fps and Ping?

have u ad legit aa chams?

Fixed bugs and I need animation fix to Update Legit AA.
And who can tell me how to get Fps and Ping

u can take a look from this #1819

This animation Fix still working?

can u make arrow indicator for antiaim invert like this https://prnt.sc/u1ospy

can u make arrow indicator for antiaim invert like this https://prnt.sc/u1ospy

#1257 paste from here

can u make arrow indicator for antiaim invert like this https://prnt.sc/u1ospy

yep the bad way is add a circle and put a magic thickness into the function. then the inverter will looks like that

if you have any better way to finish this. You can tell me

good game

can u make arrow indicator for antiaim invert like this https://prnt.sc/u1ospy

#1257 paste from here

i did but the arrow not moving when i invert the aa maybe i do something wrong

watch him rejecting this pr for no reason

watch him rejecting this pr for no reason

türk görcegimi hiç düşünmemiştim burda

was trying to use this hack
but after injecting i was stuck
i cant move and when i unhook  then its back to normal
is something wrong i have done while building .sln file or is there something else
let me know
Thanks

was trying to use this hack
but after injecting i was stuck
i cant move and when i unhook then its back to normal
is something wrong i have done while building .sln file or is there something else
let me know
Thanks

check maybe change your speed's functions

was trying to use this hack
but after injecting i was stuck
i cant move and when i unhook then its back to normal
is something wrong i have done while building .sln file or is there something else
let me know
Thanks

check maybe change your speed's functions

like fast stop? auto stop?

Now that there is an automatic stop, will there be a shooting stop?

i added new style for watermark u can check in my repo
https://github.com/aljawary/RageSiris/commit/0eca93a98a5899629804c624276b4cd9f6921b34

can you try and add legit aa chams? also the lby mode is sway, could you change it to opposite or have an option like onetap to change it to different (Normal, opposite, sway)

tyiyuiyuyui

was trying to use this hack
but after injecting i was stuck
i cant move and when i unhook then its back to normal
is something wrong i have done while building .sln file or is there something else
let me know
Thanks

check maybe change your speed's functions

like fast stop? auto stop?

player dosent even move

Severity	Code	Description	Project	File	Line	Suppression State
Error	C2039	'to_string': is not a member of 'std'	Osiris	D:\github\not-osiris-x-mutiny\Osiris\GUI.cpp	30
Error	C3861	'to_string': identifier not found	Osiris	D:\github\not-osiris-x-mutiny\Osiris\GUI.cpp	30
Warning	C4244	'argument': conversion from 'double' to 'int', possible loss of data	Osiris	D:\github\not-osiris-x-mutiny\Osiris\GUI.cpp	84
Warning	C4244	'argument': conversion from 'double' to 'int', possible loss of data	Osiris	D:\github\not-osiris-x-mutiny\Osiris\GUI.cpp	85
Warning	C4244	'argument': conversion from 'double' to 'int', possible loss of data	Osiris	D:\github\not-osiris-x-mutiny\Osiris\GUI.cpp	89
Warning	C4244	'argument': conversion from 'double' to 'int', possible loss of data	Osiris	D:\github\not-osiris-x-mutiny\Osiris\GUI.cpp	90
Warning	C4244	'argument': conversion from 'double' to 'int', possible loss of data	Osiris	D:\github\not-osiris-x-mutiny\Osiris\GUI.cpp	92
Error	C2398	Element '2': conversion from 'int' to 'float' requires a narrowing conversion	Osiris	D:\github\not-osiris-x-mutiny\Osiris\GUI.cpp	104
Warning	C4244	'argument': conversion from 'int' to 'float', possible loss of data	Osiris	D:\github\not-osiris-x-mutiny\Osiris\GUI.cpp	104
Warning	C4244	'argument': conversion from 'double' to 'int', possible loss of data	Osiris	D:\github\not-osiris-x-mutiny\Osiris\GUI.cpp	108
Warning	C4244	'argument': conversion from 'double' to 'int', possible loss of data	Osiris	D:\github\not-osiris-x-mutiny\Osiris\GUI.cpp	118
Error	C2398	Element '2': conversion from 'int' to 'float' requires a narrowing conversion	Osiris	D:\github\not-osiris-x-mutiny\Osiris\GUI.cpp	120
Warning	C4244	'argument': conversion from 'int' to 'float', possible loss of data	Osiris	D:\github\not-osiris-x-mutiny\Osiris\GUI.cpp	120
Error	C2398	Element '2': conversion from 'int' to 'float' requires a narrowing conversion	Osiris	D:\github\not-osiris-x-mutiny\Osiris\GUI.cpp	149
Warning	C4244	'argument': conversion from 'int' to 'float', possible loss of data	Osiris	D:\github\not-osiris-x-mutiny\Osiris\GUI.cpp	149
Error	C2398	Element '1': conversion from 'int' to 'float' requires a narrowing conversion	Osiris	D:\github\not-osiris-x-mutiny\Osiris\GUI.cpp	163
Error	C2398	Element '2': conversion from 'int' to 'float' requires a narrowing conversion	Osiris	D:\github\not-osiris-x-mutiny\Osiris\GUI.cpp	163
Warning	C4244	'argument': conversion from 'int' to 'float', possible loss of data	Osiris	D:\github\not-osiris-x-mutiny\Osiris\GUI.cpp	163
Warning	C4244	'argument': conversion from 'int' to 'float', possible loss of data	Osiris	D:\github\not-osiris-x-mutiny\Osiris\GUI.cpp	163
Warning	C4390	';': empty controlled statement found; is this the intent?	Osiris	D:\github\not-osiris-x-mutiny\Osiris\GUI.cpp	391
Warning	C4390	';': empty controlled statement found; is this the intent?	Osiris	D:\github\not-osiris-x-mutiny\Osiris\GUI.cpp	392
getting these errors while building

Why i don't have these errors？

not working no more.

How do I fix these errors? These are all the errors I get:

How do I fix these errors? These are all the errors I get:

This osiris's ver is so old. Pls copy my codes and update them on the newest osiris

O~K

I could compile it though :)) Project Properties, Configuration Properties, General, Character Set). The problem was I used "Use Unicode" instead of "Use Multi-Byte".

I could compile it though :)) Project Properties, Configuration Properties, General, Character Set). The problem was I used "Use Unicode" instead of "Use Multi-Byte".

I'm using Unicode


Fork Sync: Update from parent repository

@Valentin-Metz since there is no issues page to this repo, I'm going to ask here... Is it normal for the docker container to randomly exit after running for a bit and start back up again just to repeat the process again after a while?
(everything is running perfectly from what I can tell short of just the above little thing happening)

Yes, there were multiple situations in the past where streaming progress stopped to progress after a while. That's why the entire container is on a timeout and will restart itself regularly.
It's not a beautiful solution, but it has worked consistently for multiple years.

Ah got it understood. I eventually found the timeout thing in the command and removed it for now myself to see how things are, so far it's been running pretty smooth without the timeout for the past 7 hours (so no restarting of the container). Every so often it does seem to drop the websockets but they pick right back up after and everything continues to chug along just fine but I'll keep my eye on it.
Either way though thanks for making a dockerfile and all that :D I know that Devil never wanted to make one himself because he has some weird "project goals" he set for his application+repository and I've been wanting to run this thing headless for a very long time.

Ah, maybe the original issue was fixed since then in upstream.
Feel free to report back if everything still works in a month, then I can adjust the restart time upwards.

@JourneyOver do you do you have an update on this?
Did you notice any crashes, if yes, what interval did they usually occur in?

@Valentin-Metz Nope, it hasn't had any crashes or anything of the sort over the past 2 weeks. Everything has been running pretty smoothly with the timeout from the command completely removed.
I did notice that you did an update today that added a health check. One thing to note is that if there are no drops active (or no channels online for drops) at the start of the container, it will just sit there in an "unhealthy" state (even if everything is working correctly) until either a drop becomes active or a channel comes online that has drops going for something in the prio list that is active. Then, it goes into a "healthy state." I'm unsure if it goes back into an "unhealthy" state or not after the drop is done and no other drops are active, but I'll know within the next hour if this is going to be the case or not.

So it does look like it goes back to an "unhealthy" state after whenever either the channels for the drops are offline or the active drops are finished, so tbh I don't think running the willfarrell/docker-autoheal container would really be all that great like what you suggested in https://github.com/Valentin-Metz/TwitchDropsMiner/commit/60ab70a6b7ef3e339d596ccab5c3f8b960449076, due to the container being in an unhealthy state whenever there are no drops to farm unless you changed how the healthy/unhealthy states are determined.

So it does look like it goes back to an "unhealthy" state after whenever either the channels for the drops are offline or the active drops are finished, so tbh I don't think running the willfarrell/docker-autoheal container would really be all that great like what you suggested in 60ab70a, due to the container being in an unhealthy state whenever there are no drops to farm unless you changed how the healthy/unhealthy states are determined.

If the container goes into an unhealthy state due to no drops being available to farm, that is a bug (although that should not impact anything, since it'll only restart the container and it'll continue as planned once it has stuff to watch).
I'll still look into fixing that.
The status update "no_channels" should also reset the healthcheck timestamp, but I'm not sure about how frequent these are.
If your miner is currently in a state with no active drops, can you provide a complete log output until it gets restarted by the autoheal?

I currently do not use the autoheal container, and I have no real plans to, to be honest. I was just mentioning it since you had made that commit with the autoheal as one of the suggested Docker containers to run.
But I can at least give you a log of my test run with the latest container with the health check stuff in it:
2024-03-07 21:49:24: Started new container
2024-03-07 21:49:24: Starting: Twitch Drops Miner
2024-03-07 21:49:24: Logging level: CALL
2024-03-07 21:49:25: INFO: Checking login
2024-03-07 21:49:25: INFO: Restoring session from cookie
2024-03-07 21:49:25: INFO: Login successful, user ID: {blankedout}
2024-03-07 21:49:25: INFO: Websocket[0] connecting...
2024-03-07 21:49:26: INFO: Websocket[0] connected.
2024-03-07 21:49:30: CALL: Maintenance task waiting until: 22:19:30 (Points)
2024-03-07 21:49:30: Watching: ItsToptimus
2024-03-07 21:49:30: INFO: Websocket[1] connecting...
2024-03-07 21:49:30: INFO: Websocket[1] connected.
2024-03-07 21:49:41: CALL: No drop update from the websocket received
2024-03-07 21:49:41: Progress: 1/20 - Campaign(Dead Island 2, From Dusk Collection, 0/2)
2024-03-07 21:49:41: CALL: Drop progress from active search: FOMOrian Claws (Dead Island 2, 1/20)
2024-03-07 21:50:40: CALL: No drop update from the websocket received
2024-03-07 21:50:40: Progress: 2/20 - Campaign(Dead Island 2, From Dusk Collection, 0/2)
2024-03-07 21:50:40: CALL: Drop progress from active search: FOMOrian Claws (Dead Island 2, 2/20)
2024-03-07 21:51:40: CALL: No drop update from the websocket received
2024-03-07 21:51:40: Progress: 3/20 - Campaign(Dead Island 2, From Dusk Collection, 0/2)
2024-03-07 21:51:40: CALL: Drop progress from active search: FOMOrian Claws (Dead Island 2, 3/20)
2024-03-07 21:52:39: CALL: No drop update from the websocket received
2024-03-07 21:52:39: Progress: 4/20 - Campaign(Dead Island 2, From Dusk Collection, 0/2)
2024-03-07 21:52:39: CALL: Drop progress from active search: FOMOrian Claws (Dead Island 2, 4/20)
2024-03-07 21:53:30: Earned points for watching:  10, total: 10
2024-03-07 21:53:38: CALL: No drop update from the websocket received
2024-03-07 21:53:38: Progress: 5/20 - Campaign(Dead Island 2, From Dusk Collection, 0/2)
2024-03-07 21:53:38: CALL: Drop progress from active search: FOMOrian Claws (Dead Island 2, 5/20)
2024-03-07 21:54:38: CALL: No drop update from the websocket received
2024-03-07 21:54:38: Progress: 6/20 - Campaign(Dead Island 2, From Dusk Collection, 0/2)
2024-03-07 21:54:38: CALL: Drop progress from active search: FOMOrian Claws (Dead Island 2, 6/20)
2024-03-07 21:55:37: CALL: No drop update from the websocket received
2024-03-07 21:55:37: Progress: 7/20 - Campaign(Dead Island 2, From Dusk Collection, 0/2)
2024-03-07 21:55:37: CALL: Drop progress from active search: FOMOrian Claws (Dead Island 2, 7/20)
2024-03-07 21:56:36: CALL: No drop update from the websocket received
2024-03-07 21:56:36: Progress: 8/20 - Campaign(Dead Island 2, From Dusk Collection, 0/2)
2024-03-07 21:56:36: CALL: Drop progress from active search: FOMOrian Claws (Dead Island 2, 8/20)
2024-03-07 21:57:35: CALL: No drop update from the websocket received
2024-03-07 21:57:35: Progress: 9/20 - Campaign(Dead Island 2, From Dusk Collection, 0/2)
2024-03-07 21:57:36: CALL: Drop progress from active search: FOMOrian Claws (Dead Island 2, 9/20)
2024-03-07 21:58:29: Earned points for watching:  10, total: 20
2024-03-07 21:58:31: INFO: gilledchaos goes OFFLINE
2024-03-07 21:58:32: CALL: Channel update from websocket: gilledchaos
2024-03-07 21:58:35: CALL: No drop update from the websocket received
2024-03-07 21:58:35: Progress: 10/20 - Campaign(Dead Island 2, From Dusk Collection, 0/2)
2024-03-07 21:58:35: CALL: Drop progress from active search: FOMOrian Claws (Dead Island 2, 10/20)
2024-03-07 21:59:34: CALL: No drop update from the websocket received
2024-03-07 21:59:34: Progress: 11/20 - Campaign(Dead Island 2, From Dusk Collection, 0/2)
2024-03-07 21:59:34: CALL: Drop progress from active search: FOMOrian Claws (Dead Island 2, 11/20)
2024-03-07 22:00:32: CALL: gilledchaos stays OFFLINE
2024-03-07 22:00:33: CALL: No drop update from the websocket received
2024-03-07 22:00:33: Progress: 12/20 - Campaign(Dead Island 2, From Dusk Collection, 0/2)
2024-03-07 22:00:33: CALL: Drop progress from active search: FOMOrian Claws (Dead Island 2, 12/20)
2024-03-07 22:01:33: CALL: No drop update from the websocket received
2024-03-07 22:01:33: Progress: 13/20 - Campaign(Dead Island 2, From Dusk Collection, 0/2)
2024-03-07 22:01:33: CALL: Drop progress from active search: FOMOrian Claws (Dead Island 2, 13/20)
2024-03-07 22:02:32: CALL: No drop update from the websocket received
2024-03-07 22:02:32: Progress: 14/20 - Campaign(Dead Island 2, From Dusk Collection, 0/2)
2024-03-07 22:02:32: CALL: Drop progress from active search: FOMOrian Claws (Dead Island 2, 14/20)
2024-03-07 22:03:25: Earned points for watching:  10, total: 30
2024-03-07 22:03:25: Claimed bonus points: 50
2024-03-07 22:03:26: Earned points for watching:  50, total: 80
2024-03-07 22:03:32: CALL: No drop update from the websocket received
2024-03-07 22:03:32: Progress: 15/20 - Campaign(Dead Island 2, From Dusk Collection, 0/2)
2024-03-07 22:03:32: CALL: Drop progress from active search: FOMOrian Claws (Dead Island 2, 15/20)
2024-03-07 22:04:31: CALL: No drop update from the websocket received
2024-03-07 22:04:31: Progress: 16/20 - Campaign(Dead Island 2, From Dusk Collection, 0/2)
2024-03-07 22:04:31: CALL: Drop progress from active search: FOMOrian Claws (Dead Island 2, 16/20)
2024-03-07 22:05:27: INFO: champi_mp goes OFFLINE
2024-03-07 22:05:28: CALL: Channel update from websocket: champi_mp
2024-03-07 22:05:30: CALL: No drop update from the websocket received
2024-03-07 22:05:30: Progress: 17/20 - Campaign(Dead Island 2, From Dusk Collection, 0/2)
2024-03-07 22:05:30: CALL: Drop progress from active search: FOMOrian Claws (Dead Island 2, 17/20)
2024-03-07 22:06:30: CALL: No drop update from the websocket received
2024-03-07 22:06:30: Progress: 18/20 - Campaign(Dead Island 2, From Dusk Collection, 0/2)
2024-03-07 22:06:30: CALL: Drop progress from active search: FOMOrian Claws (Dead Island 2, 18/20)
2024-03-07 22:07:29: CALL: champi_mp stays OFFLINE
2024-03-07 22:07:29: CALL: No drop update from the websocket received
2024-03-07 22:07:29: Progress: 19/20 - Campaign(Dead Island 2, From Dusk Collection, 0/2)
2024-03-07 22:07:29: CALL: Drop progress from active search: FOMOrian Claws (Dead Island 2, 19/20)
2024-03-07 22:08:23: Earned points for watching:  10, total: 90
2024-03-07 22:08:28: CALL: No drop update from the websocket received
2024-03-07 22:08:28: CALL: No active drop could be determined
2024-03-07 22:08:29: CALL: Maintenance task waiting until: 22:38:29 (Points)
2024-03-07 22:08:29: INFO: Websocket[1] stopped.
2024-03-07 22:08:29: INFO: Websocket[1] connecting...
2024-03-07 22:08:30: INFO: Websocket[1] connected.
2024-03-07 22:08:39: CALL: No drop update from the websocket received
2024-03-07 22:08:39: Progress: 21/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:08:39: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 21/60)
2024-03-07 22:08:41: INFO: DJ_CYBER_The_Drolf goes OFFLINE
2024-03-07 22:08:42: CALL: Channel update from websocket: DJ_CYBER_The_Drolf
2024-03-07 22:09:39: CALL: No drop update from the websocket received
2024-03-07 22:09:39: Progress: 22/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:09:39: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 22/60)
2024-03-07 22:10:39: CALL: No drop update from the websocket received
2024-03-07 22:10:39: Progress: 23/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:10:39: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 23/60)
2024-03-07 22:10:42: CALL: DJ_CYBER_The_Drolf stays OFFLINE
2024-03-07 22:11:38: CALL: No drop update from the websocket received
2024-03-07 22:11:38: Progress: 24/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:11:38: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 24/60)
2024-03-07 22:12:37: CALL: No drop update from the websocket received
2024-03-07 22:12:37: Progress: 25/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:12:37: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 25/60)
2024-03-07 22:13:30: Earned points for watching:  10, total: 100
2024-03-07 22:13:37: CALL: No drop update from the websocket received
2024-03-07 22:13:37: Progress: 26/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:13:37: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 26/60)
2024-03-07 22:14:36: CALL: No drop update from the websocket received
2024-03-07 22:14:36: Progress: 27/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:14:36: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 27/60)
2024-03-07 22:15:35: CALL: No drop update from the websocket received
2024-03-07 22:15:35: Progress: 28/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:15:35: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 28/60)
2024-03-07 22:16:35: CALL: No drop update from the websocket received
2024-03-07 22:16:35: Progress: 29/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:16:35: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 29/60)
2024-03-07 22:17:34: CALL: No drop update from the websocket received
2024-03-07 22:17:34: Progress: 30/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:17:34: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 30/60)
2024-03-07 22:18:25: INFO: kafofodakaty goes OFFLINE
2024-03-07 22:18:25: Earned points for watching:  10, total: 110
2024-03-07 22:18:25: Claimed bonus points: 50
2024-03-07 22:18:26: Earned points for watching:  50, total: 160
2024-03-07 22:18:26: CALL: Channel update from websocket: kafofodakaty
2024-03-07 22:18:33: CALL: No drop update from the websocket received
2024-03-07 22:18:33: Progress: 31/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:18:33: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 31/60)
2024-03-07 22:19:33: CALL: No drop update from the websocket received
2024-03-07 22:19:33: Progress: 32/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:19:33: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 32/60)
2024-03-07 22:20:26: CALL: kafofodakaty stays OFFLINE
2024-03-07 22:20:32: CALL: No drop update from the websocket received
2024-03-07 22:20:32: Progress: 33/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:20:32: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 33/60)
2024-03-07 22:21:31: CALL: No drop update from the websocket received
2024-03-07 22:21:31: Progress: 34/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:21:31: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 34/60)
2024-03-07 22:22:31: CALL: No drop update from the websocket received
2024-03-07 22:22:31: Progress: 35/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:22:31: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 35/60)
2024-03-07 22:23:24: Earned points for watching:  10, total: 170
2024-03-07 22:23:30: CALL: No drop update from the websocket received
2024-03-07 22:23:30: Progress: 36/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:23:30: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 36/60)
2024-03-07 22:24:23: INFO: KalAnn98 goes OFFLINE
2024-03-07 22:24:25: CALL: Channel update from websocket: KalAnn98
2024-03-07 22:24:29: CALL: No drop update from the websocket received
2024-03-07 22:24:29: Progress: 37/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:24:29: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 37/60)
2024-03-07 22:25:29: CALL: No drop update from the websocket received
2024-03-07 22:25:29: Progress: 38/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:25:29: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 38/60)
2024-03-07 22:26:25: CALL: KalAnn98 stays OFFLINE
2024-03-07 22:26:28: CALL: No drop update from the websocket received
2024-03-07 22:26:28: Progress: 39/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:26:28: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 39/60)
2024-03-07 22:26:53: INFO: dranzer1986 goes OFFLINE
2024-03-07 22:26:54: CALL: Channel update from websocket: dranzer1986
2024-03-07 22:27:27: CALL: No drop update from the websocket received
2024-03-07 22:27:27: Progress: 40/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:27:27: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 40/60)
2024-03-07 22:28:20: Earned points for watching:  10, total: 180
2024-03-07 22:28:27: CALL: No drop update from the websocket received
2024-03-07 22:28:27: Progress: 41/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:28:27: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 41/60)
2024-03-07 22:28:54: CALL: dranzer1986 stays OFFLINE
2024-03-07 22:29:26: CALL: No drop update from the websocket received
2024-03-07 22:29:26: Progress: 42/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:29:26: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 42/60)
2024-03-07 22:30:21: INFO: ThatOtherDoomguy goes OFFLINE
2024-03-07 22:30:23: CALL: Channel update from websocket: ThatOtherDoomguy
2024-03-07 22:30:25: CALL: No drop update from the websocket received
2024-03-07 22:30:25: Progress: 43/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:30:25: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 43/60)
2024-03-07 22:31:25: CALL: No drop update from the websocket received
2024-03-07 22:31:25: Progress: 44/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:31:25: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 44/60)
2024-03-07 22:32:23: CALL: ThatOtherDoomguy stays OFFLINE
2024-03-07 22:32:24: CALL: No drop update from the websocket received
2024-03-07 22:32:24: Progress: 45/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:32:24: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 45/60)
2024-03-07 22:33:16: Earned points for watching:  10, total: 190
2024-03-07 22:33:17: Claimed bonus points: 50
2024-03-07 22:33:17: Earned points for watching:  50, total: 240
2024-03-07 22:33:23: CALL: No drop update from the websocket received
2024-03-07 22:33:23: Progress: 46/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:33:23: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 46/60)
2024-03-07 22:33:53: INFO: BulletSponge506 goes OFFLINE
2024-03-07 22:33:54: CALL: Channel update from websocket: BulletSponge506
2024-03-07 22:34:23: CALL: No drop update from the websocket received
2024-03-07 22:34:23: Progress: 47/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:34:23: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 47/60)
2024-03-07 22:35:22: CALL: No drop update from the websocket received
2024-03-07 22:35:22: Progress: 48/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:35:22: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 48/60)
2024-03-07 22:35:54: CALL: BulletSponge506 stays OFFLINE
2024-03-07 22:36:21: CALL: No drop update from the websocket received
2024-03-07 22:36:21: Progress: 49/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:36:21: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 49/60)
2024-03-07 22:37:21: CALL: No drop update from the websocket received
2024-03-07 22:37:21: Progress: 50/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:37:21: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 50/60)
2024-03-07 22:37:34: CALL: Channel update from websocket: BossC86, game changed: Dead Island 2 -> Tomb Raider I•II•III Remastered
2024-03-07 22:38:13: Earned points for watching:  10, total: 250
2024-03-07 22:38:20: CALL: No drop update from the websocket received
2024-03-07 22:38:20: Progress: 51/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:38:20: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 51/60)
2024-03-07 22:38:29: CALL: Maintenance task waiting until: 23:08:29 (Reload)
2024-03-07 22:39:19: CALL: No drop update from the websocket received
2024-03-07 22:39:19: Progress: 52/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:39:19: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 52/60)
2024-03-07 22:39:34: INFO: BossC86 status has been updated (🎁: ✔ -> ❌)
2024-03-07 22:40:19: CALL: No drop update from the websocket received
2024-03-07 22:40:19: Progress: 53/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:40:19: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 53/60)
2024-03-07 22:41:18: CALL: No drop update from the websocket received
2024-03-07 22:41:18: Progress: 54/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:41:18: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 54/60)
2024-03-07 22:42:17: CALL: No drop update from the websocket received
2024-03-07 22:42:17: Progress: 55/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:42:17: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 55/60)
2024-03-07 22:42:59: INFO: soykova goes OFFLINE
2024-03-07 22:43:00: CALL: Channel update from websocket: soykova
2024-03-07 22:43:11: Earned points for watching:  10, total: 260
2024-03-07 22:43:17: CALL: No drop update from the websocket received
2024-03-07 22:43:17: Progress: 56/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:43:17: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 56/60)
2024-03-07 22:43:20: CALL: Channel update from websocket: sleepyheadelite, game changed: Dead Island 2 -> Apex Legends
2024-03-07 22:43:20: CALL: Channel update from websocket: sleepyheadelite
2024-03-07 22:44:16: CALL: No drop update from the websocket received
2024-03-07 22:44:16: Progress: 57/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:44:16: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 57/60)
2024-03-07 22:44:20: INFO: jpdae73 goes OFFLINE
2024-03-07 22:44:23: CALL: Channel update from websocket: jpdae73
2024-03-07 22:45:00: CALL: soykova stays OFFLINE
2024-03-07 22:45:15: CALL: No drop update from the websocket received
2024-03-07 22:45:15: Progress: 58/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:45:15: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 58/60)
2024-03-07 22:45:20: INFO: sleepyheadelite status has been updated (🎁: ✔ -> ✔)
2024-03-07 22:46:15: CALL: No drop update from the websocket received
2024-03-07 22:46:15: Progress: 59/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:46:15: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 59/60)
2024-03-07 22:46:23: CALL: jpdae73 stays OFFLINE
2024-03-07 22:47:14: CALL: No drop update from the websocket received
2024-03-07 22:47:14: Progress: 60/60 - Campaign(Dead Island 2, From Dusk Collection, 1/2)
2024-03-07 22:47:14: CALL: Drop progress from active search: Legless FOMOrian Skin (Dead Island 2, 60/60)
2024-03-07 22:48:07: Earned points for watching:  10, total: 270
2024-03-07 22:48:07: Claimed bonus points: 50
2024-03-07 22:48:08: Earned points for watching:  50, total: 320
2024-03-07 22:48:12: CALL: Maintenance task waiting until: 23:18:12 (Points)
2024-03-07 22:48:12: No active campaigns to mine drops for. Waiting for an active campaign...
2024-03-07 22:48:12: INFO: Websocket[1] stopped.
2024-03-07 22:48:14: CALL: No drop update from the websocket received
2024-03-07 22:48:14: CALL: No active drop could be determined
2024-03-07 23:18:12: CALL: Maintenance task waiting until: 23:48:12 (Reload)
2024-03-07 23:48:12: CALL: Maintenance task requests a reload
2024-03-07 23:48:14: No active campaigns to mine drops for. Waiting for an active campaign...
2024-03-07 23:48:15: CALL: Maintenance task waiting until: 00:18:15 (Points)
2024-03-08 00:18:15: CALL: Maintenance task waiting until: 00:48:15 (Reload)

From at least the 2024-03-07 21:49:24: Started new container up until the 2024-03-07 21:49:30: CALL: Maintenance task waiting until: 22:19:30 (Points) part, it was in an unhealthy state (this is  probably normal as it's starting everything up). It moved to a healthy state once it started farming a drop, until around the 22:48 timestamps, when the drop it was currently farming was finished and I had no other drops to farm. Then, it moved back to an unhealthy state again and as of this writing it is still currently sitting in an unhealthy state since there are no drops to farm.

From at least the 2024-03-07 21:49:24: Started new container up until the 2024-03-07 21:49:30: CALL: Maintenance task waiting until: 22:19:30 (Points) part, it was in an unhealthy state (this is probably normal as it's starting everything up). It moved to a healthy state once it started farming a drop, until around the 22:48 timestamps, when the drop it was currently farming was finished and I had no other drops to farm. Then, it moved back to an unhealthy state again and as of this writing it is still currently sitting in an unhealthy state since there are no drops to farm.

Should be fixed in latest commit.
Please let me know if the issue persists.

Should be fixed in latest commit.
Please let me know if the issue persists.

Looks good so far! I'll keep an eye on it over the next week or two and will report back on things or if an issue ends up cropping up over time.

2024-03-08 01:08:30: Started new container
2024-03-08 01:08:30: Starting: Twitch Drops Miner
2024-03-08 01:08:31: Logging level: CALL
2024-03-08 01:08:32: INFO: Checking login
2024-03-08 01:08:32: INFO: Restoring session from cookie
2024-03-08 01:08:32: INFO: Login successful, user ID: {blankedout}
2024-03-08 01:08:32: INFO: Websocket[0] connecting...
2024-03-08 01:08:33: INFO: Websocket[0] connected.
2024-03-08 01:08:52: No active campaigns to mine drops for. Waiting for an active campaign...
2024-03-08 01:08:52: CALL: Maintenance task waiting until: 01:38:52 (Points)

Hmm, I presume after 1:08:52 it stopped outputting logs at all?

It seems a bit weird to wait 30 mins between refreshing campaigns; maybe that'd be something to adjust. I'll look into it.

Yeah, we might need to do something along those lines. If things are left with default values for the health check, it would pretty much sit in an unhealthy state after a few minutes between every Maintenance task requests a reload until another one happens if there are no drops to farm. Right now, it seems that these are the only times when the No active campaigns to mine drops for. Waiting for an active campaign... message comes up, as evident by my log below:
2024-03-08 01:08:30: Started new container
2024-03-08 01:08:30: Starting: Twitch Drops Miner
2024-03-08 01:08:31: Logging level: CALL
2024-03-08 01:08:32: INFO: Checking login
2024-03-08 01:08:32: INFO: Restoring session from cookie
2024-03-08 01:08:32: INFO: Login successful, user ID: 82698666
2024-03-08 01:08:32: INFO: Websocket[0] connecting...
2024-03-08 01:08:33: INFO: Websocket[0] connected.
2024-03-08 01:08:52: No active campaigns to mine drops for. Waiting for an active campaign...
2024-03-08 01:08:52: CALL: Maintenance task waiting until: 01:38:52 (Points)
2024-03-08 01:38:52: CALL: Maintenance task waiting until: 02:08:52 (Reload)
2024-03-08 02:08:52: CALL: Maintenance task requests a reload
2024-03-08 02:08:55: No active campaigns to mine drops for. Waiting for an active campaign...
2024-03-08 02:08:55: CALL: Maintenance task waiting until: 02:38:55 (Points)
2024-03-08 02:38:55: CALL: Maintenance task waiting until: 02:59:59 (Cleanup)
2024-03-08 03:00:00: CALL: Maintenance task requests channels cleanup
2024-03-08 03:00:00: CALL: Maintenance task waiting until: 03:08:55 (Reload)
2024-03-08 03:00:00: No active campaigns to mine drops for. Waiting for an active campaign...
2024-03-08 03:08:55: CALL: Maintenance task requests a reload
2024-03-08 03:08:58: No active campaigns to mine drops for. Waiting for an active campaign...
2024-03-08 03:08:58: CALL: Maintenance task waiting until: 03:30:00 (Cleanup)
2024-03-08 03:30:00: CALL: Maintenance task requests channels cleanup
2024-03-08 03:30:00: CALL: Maintenance task waiting until: 04:00:00 (Points)
2024-03-08 03:30:00: No active campaigns to mine drops for. Waiting for an active campaign...
2024-03-08 04:00:00: CALL: Maintenance task waiting until: 04:08:58 (Reload)
2024-03-08 04:08:58: CALL: Maintenance task requests a reload
2024-03-08 04:09:01: No active campaigns to mine drops for. Waiting for an active campaign...
2024-03-08 04:09:01: CALL: Maintenance task waiting until: 04:39:01 (Points)
2024-03-08 04:39:01: CALL: Maintenance task waiting until: 05:09:01 (Reload)
2024-03-08 05:09:01: CALL: Maintenance task requests a reload
2024-03-08 05:09:03: CALL: Maintenance task waiting until: 05:39:03 (Points)
2024-03-08 05:09:04: Watching: kalon75
2024-03-08 05:09:15: CALL: No drop update from the websocket received
2024-03-08 05:09:15: Progress: 1/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:09:15: CALL: Drop progress from active search: Display - Glyph (Warframe, 1/30)
2024-03-08 05:10:14: CALL: No drop update from the websocket received
2024-03-08 05:10:14: Progress: 2/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:10:14: CALL: Drop progress from active search: Display - Glyph (Warframe, 2/30)
2024-03-08 05:11:13: CALL: No drop update from the websocket received
2024-03-08 05:11:13: Progress: 3/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:11:13: CALL: Drop progress from active search: Display - Glyph (Warframe, 3/30)
2024-03-08 05:12:13: CALL: No drop update from the websocket received
2024-03-08 05:12:13: Progress: 4/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:12:13: CALL: Drop progress from active search: Display - Glyph (Warframe, 4/30)
2024-03-08 05:13:05: Earned points for watching:  10, total: 810
2024-03-08 05:13:12: CALL: No drop update from the websocket received
2024-03-08 05:13:12: Progress: 5/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:13:12: CALL: Drop progress from active search: Display - Glyph (Warframe, 5/30)
2024-03-08 05:14:11: CALL: No drop update from the websocket received
2024-03-08 05:14:11: Progress: 6/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:14:11: CALL: Drop progress from active search: Display - Glyph (Warframe, 6/30)
2024-03-08 05:15:11: CALL: No drop update from the websocket received
2024-03-08 05:15:11: Progress: 7/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:15:11: CALL: Drop progress from active search: Display - Glyph (Warframe, 7/30)
2024-03-08 05:16:10: CALL: No drop update from the websocket received
2024-03-08 05:16:10: Progress: 8/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:16:10: CALL: Drop progress from active search: Display - Glyph (Warframe, 8/30)
2024-03-08 05:17:09: CALL: No drop update from the websocket received
2024-03-08 05:17:09: Progress: 9/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:17:09: CALL: Drop progress from active search: Display - Glyph (Warframe, 9/30)
2024-03-08 05:18:02: Earned points for watching:  10, total: 820
2024-03-08 05:18:09: CALL: No drop update from the websocket received
2024-03-08 05:18:09: Progress: 10/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:18:09: CALL: Drop progress from active search: Display - Glyph (Warframe, 10/30)
2024-03-08 05:19:08: CALL: No drop update from the websocket received
2024-03-08 05:19:08: Progress: 11/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:19:08: CALL: Drop progress from active search: Display - Glyph (Warframe, 11/30)
2024-03-08 05:20:07: CALL: No drop update from the websocket received
2024-03-08 05:20:07: Progress: 12/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:20:07: CALL: Drop progress from active search: Display - Glyph (Warframe, 12/30)
2024-03-08 05:21:07: CALL: No drop update from the websocket received
2024-03-08 05:21:07: Progress: 13/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:21:07: CALL: Drop progress from active search: Display - Glyph (Warframe, 13/30)
2024-03-08 05:22:06: CALL: No drop update from the websocket received
2024-03-08 05:22:06: Progress: 14/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:22:06: CALL: Drop progress from active search: Display - Glyph (Warframe, 14/30)
2024-03-08 05:23:00: Earned points for watching:  10, total: 830
2024-03-08 05:23:00: Claimed bonus points: 50
2024-03-08 05:23:00: Earned points for watching:  50, total: 880
2024-03-08 05:23:05: CALL: No drop update from the websocket received
2024-03-08 05:23:05: Progress: 15/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:23:05: CALL: Drop progress from active search: Display - Glyph (Warframe, 15/30)
2024-03-08 05:24:05: CALL: No drop update from the websocket received
2024-03-08 05:24:05: Progress: 16/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:24:05: CALL: Drop progress from active search: Display - Glyph (Warframe, 16/30)
2024-03-08 05:25:04: CALL: No drop update from the websocket received
2024-03-08 05:25:04: Progress: 17/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:25:04: CALL: Drop progress from active search: Display - Glyph (Warframe, 17/30)
2024-03-08 05:26:03: CALL: No drop update from the websocket received
2024-03-08 05:26:03: Progress: 18/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:26:03: CALL: Drop progress from active search: Display - Glyph (Warframe, 18/30)
2024-03-08 05:27:03: CALL: No drop update from the websocket received
2024-03-08 05:27:03: Progress: 19/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:27:03: CALL: Drop progress from active search: Display - Glyph (Warframe, 19/30)
2024-03-08 05:27:57: Earned points for watching:  10, total: 890
2024-03-08 05:28:02: CALL: No drop update from the websocket received
2024-03-08 05:28:02: Progress: 20/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:28:02: CALL: Drop progress from active search: Display - Glyph (Warframe, 20/30)
2024-03-08 05:29:01: CALL: No drop update from the websocket received
2024-03-08 05:29:01: Progress: 21/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:29:01: CALL: Drop progress from active search: Display - Glyph (Warframe, 21/30)
2024-03-08 05:30:01: CALL: No drop update from the websocket received
2024-03-08 05:30:01: Progress: 22/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:30:01: CALL: Drop progress from active search: Display - Glyph (Warframe, 22/30)
2024-03-08 05:31:00: CALL: No drop update from the websocket received
2024-03-08 05:31:00: Progress: 23/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:31:00: CALL: Drop progress from active search: Display - Glyph (Warframe, 23/30)
2024-03-08 05:31:59: CALL: No drop update from the websocket received
2024-03-08 05:31:59: Progress: 24/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:31:59: CALL: Drop progress from active search: Display - Glyph (Warframe, 24/30)
2024-03-08 05:32:53: Earned points for watching:  10, total: 900
2024-03-08 05:32:59: CALL: No drop update from the websocket received
2024-03-08 05:32:59: Progress: 25/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:32:59: CALL: Drop progress from active search: Display - Glyph (Warframe, 25/30)
2024-03-08 05:33:58: CALL: No drop update from the websocket received
2024-03-08 05:33:58: Progress: 26/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:33:58: CALL: Drop progress from active search: Display - Glyph (Warframe, 26/30)
2024-03-08 05:34:57: CALL: No drop update from the websocket received
2024-03-08 05:34:57: Progress: 27/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:34:57: CALL: Drop progress from active search: Display - Glyph (Warframe, 27/30)
2024-03-08 05:35:57: CALL: No drop update from the websocket received
2024-03-08 05:35:57: Progress: 28/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:35:57: CALL: Drop progress from active search: Display - Glyph (Warframe, 28/30)
2024-03-08 05:36:56: CALL: No drop update from the websocket received
2024-03-08 05:36:56: Progress: 29/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:36:56: CALL: Drop progress from active search: Display - Glyph (Warframe, 29/30)
2024-03-08 05:37:48: Earned points for watching:  10, total: 910
2024-03-08 05:37:48: Claimed bonus points: 50
2024-03-08 05:37:49: Earned points for watching:  50, total: 960
2024-03-08 05:37:55: CALL: No drop update from the websocket received
2024-03-08 05:37:55: Progress: 30/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:37:55: CALL: Drop progress from active search: Display - Glyph (Warframe, 30/30)
2024-03-08 05:38:55: CALL: No drop update from the websocket received
2024-03-08 05:38:55: Progress: 30/30 - Campaign(Warframe, Weekend Community Drops 35, 0/1)
2024-03-08 05:38:55: CALL: Drop progress from active search: Display - Glyph (Warframe, 30/30)
2024-03-08 05:38:55: CALL: Maintenance task waiting until: 05:59:59 (Cleanup)
2024-03-08 05:38:55: No active campaigns to mine drops for. Waiting for an active campaign...
2024-03-08 06:00:00: CALL: Maintenance task requests channels cleanup
2024-03-08 06:00:00: CALL: Maintenance task waiting until: 06:00:59 (Cleanup)
2024-03-08 06:00:00: No active campaigns to mine drops for. Waiting for an active campaign...
2024-03-08 06:01:00: CALL: Maintenance task requests channels cleanup
2024-03-08 06:01:00: CALL: Maintenance task waiting until: 06:31:00 (Points)
2024-03-08 06:01:00: No active campaigns to mine drops for. Waiting for an active campaign...
2024-03-08 06:31:00: CALL: Maintenance task waiting until: 06:38:55 (Reload)
2024-03-08 06:38:55: CALL: Maintenance task requests a reload
2024-03-08 06:38:58: No active campaigns to mine drops for. Waiting for an active campaign...
2024-03-08 06:38:58: CALL: Maintenance task waiting until: 07:08:58 (Points)
2024-03-08 07:08:58: CALL: Maintenance task waiting until: 07:38:58 (Reload)
2024-03-08 07:38:58: CALL: Maintenance task requests a reload
2024-03-08 07:39:00: No active campaigns to mine drops for. Waiting for an active campaign...
2024-03-08 07:39:00: CALL: Maintenance task waiting until: 08:00:00 (Cleanup)
2024-03-08 08:00:00: CALL: Maintenance task requests channels cleanup
2024-03-08 08:00:00: CALL: Maintenance task waiting until: 08:30:00 (Points)
2024-03-08 08:00:00: No active campaigns to mine drops for. Waiting for an active campaign...
2024-03-08 08:30:00: CALL: Maintenance task waiting until: 08:39:00 (Reload)
2024-03-08 08:39:00: CALL: Maintenance task requests a reload
2024-03-08 08:39:03: No active campaigns to mine drops for. Waiting for an active campaign...
2024-03-08 08:39:03: CALL: Maintenance task waiting until: 09:00:00 (Cleanup)
2024-03-08 09:00:00: CALL: Maintenance task requests channels cleanup
2024-03-08 09:00:00: CALL: Maintenance task waiting until: 09:30:00 (Points)
2024-03-08 09:00:00: No active campaigns to mine drops for. Waiting for an active campaign...
2024-03-08 09:30:00: CALL: Maintenance task waiting until: 09:39:03 (Reload)
2024-03-08 09:39:03: CALL: Maintenance task requests a reload
2024-03-08 09:39:06: No active campaigns to mine drops for. Waiting for an active campaign...
2024-03-08 09:39:06: CALL: Maintenance task waiting until: 10:09:06 (Points)

Well doing that and it seems like it runs into a different issue in the maintenance tasks lists. As you'll see in the log below:
2024-03-08 15:33:14: Started new container
2024-03-08 15:33:14: Starting: Twitch Drops Miner
2024-03-08 15:33:15: Logging level: CALL
2024-03-08 15:33:16: INFO: Checking login
2024-03-08 15:33:16: INFO: Restoring session from cookie
2024-03-08 15:33:16: INFO: Login successful, user ID: {Doomed}
2024-03-08 15:33:16: INFO: Websocket[0] connecting...
2024-03-08 15:33:17: INFO: Websocket[0] connected.
2024-03-08 15:33:35: No active campaigns to mine drops for. Waiting for an active campaign...
2024-03-08 15:33:35: CALL: Maintenance task waiting until: 15:38:35 (Reload)
2024-03-08 15:38:35: CALL: Maintenance task requests a reload
2024-03-08 15:38:37: No active campaigns to mine drops for. Waiting for an active campaign...
2024-03-08 15:38:37: CALL: Maintenance task waiting until: 15:43:37 (Reload)
2024-03-08 15:43:37: CALL: Maintenance task requests a reload
2024-03-08 15:43:40: No active campaigns to mine drops for. Waiting for an active campaign...
2024-03-08 15:43:40: CALL: Maintenance task waiting until: 15:48:40 (Reload)
2024-03-08 15:48:40: CALL: Maintenance task requests a reload
2024-03-08 15:48:43: No active campaigns to mine drops for. Waiting for an active campaign...
2024-03-08 15:48:43: CALL: Maintenance task waiting until: 15:53:43 (Reload)
2024-03-08 15:53:43: CALL: Maintenance task requests a reload
2024-03-08 15:53:45: No active campaigns to mine drops for. Waiting for an active campaign...
2024-03-08 15:53:45: CALL: Maintenance task waiting until: 15:58:45 (Reload)
2024-03-08 15:58:45: CALL: Maintenance task requests a reload
2024-03-08 15:58:48: No active campaigns to mine drops for. Waiting for an active campaign...
2024-03-08 15:58:48: CALL: Maintenance task waiting until: 16:03:48 (Reload)
2024-03-08 16:03:48: CALL: Maintenance task requests a reload
2024-03-08 16:03:50: No active campaigns to mine drops for. Waiting for an active campaign...
2024-03-08 16:03:50: CALL: Maintenance task waiting until: 16:08:50 (Reload)
2024-03-08 16:08:50: CALL: Maintenance task requests a reload
2024-03-08 16:08:52: No active campaigns to mine drops for. Waiting for an active campaign...
2024-03-08 16:08:52: CALL: Maintenance task waiting until: 16:13:52 (Reload)

it now seems to only do the "reload" maintenance tasks and that is it, while before there was both a "reload" task and a "points" task and every so often a "cleanup" task
I'm honestly thinking this is more hassle than it's really worth as everything was working perfectly fine (with me removing the timeout command) before all this healthcheck stuff ngl..
also the 5 minutes reload seems to be applying to even when farming an active drop as evident by:
2024-03-08 16:13:43: Started new container
2024-03-08 16:13:43: Starting: Twitch Drops Miner
2024-03-08 16:13:44: Logging level: CALL
2024-03-08 16:13:45: INFO: Checking login
2024-03-08 16:13:45: INFO: Restoring session from cookie
2024-03-08 16:13:45: INFO: Login successful, user ID: {HI}
2024-03-08 16:13:45: INFO: Websocket[0] connecting...
2024-03-08 16:13:45: INFO: Websocket[0] connected.
2024-03-08 16:13:52: CALL: Maintenance task waiting until: 16:18:52 (Reload)
2024-03-08 16:13:52: Watching: Hooks
2024-03-08 16:13:52: INFO: Websocket[1] connecting...
2024-03-08 16:13:52: INFO: Websocket[1] connected.
2024-03-08 16:14:03: CALL: No drop update from the websocket received
2024-03-08 16:14:03: Progress: 15/60 - Campaign(Stream Raiders, Phantom Drops, 0/5)
2024-03-08 16:14:03: CALL: Drop progress from active search: 10 Phantom Scrolls (Stream Raiders, 15/60)
2024-03-08 16:15:02: CALL: No drop update from the websocket received
2024-03-08 16:15:02: Progress: 16/60 - Campaign(Stream Raiders, Phantom Drops, 0/5)
2024-03-08 16:15:02: CALL: Drop progress from active search: 10 Phantom Scrolls (Stream Raiders, 16/60)
2024-03-08 16:16:01: CALL: No drop update from the websocket received
2024-03-08 16:16:01: Progress: 17/60 - Campaign(Stream Raiders, Phantom Drops, 0/5)
2024-03-08 16:16:01: CALL: Drop progress from active search: 10 Phantom Scrolls (Stream Raiders, 17/60)
2024-03-08 16:17:01: CALL: No drop update from the websocket received
2024-03-08 16:17:01: Progress: 18/60 - Campaign(Stream Raiders, Phantom Drops, 0/5)
2024-03-08 16:17:01: CALL: Drop progress from active search: 10 Phantom Scrolls (Stream Raiders, 18/60)
2024-03-08 16:17:53: Earned points for watching:  10, total: 21230
2024-03-08 16:18:00: CALL: No drop update from the websocket received
2024-03-08 16:18:00: Progress: 19/60 - Campaign(Stream Raiders, Phantom Drops, 0/5)
2024-03-08 16:18:00: CALL: Drop progress from active search: 10 Phantom Scrolls (Stream Raiders, 19/60)
2024-03-08 16:18:52: CALL: Maintenance task requests a reload
2024-03-08 16:18:54: CALL: Maintenance task waiting until: 16:23:54 (Reload)
2024-03-08 16:18:54: INFO: Websocket[1] stopped.
2024-03-08 16:18:55: INFO: Websocket[1] connecting...
2024-03-08 16:18:55: INFO: Websocket[1] connected.
2024-03-08 16:18:59: CALL: No drop update from the websocket received
2024-03-08 16:18:59: Progress: 20/60 - Campaign(Stream Raiders, Phantom Drops, 0/5)
2024-03-08 16:18:59: CALL: Drop progress from active search: 10 Phantom Scrolls (Stream Raiders, 20/60)
2024-03-08 16:19:59: CALL: No drop update from the websocket received
2024-03-08 16:19:59: Progress: 21/60 - Campaign(Stream Raiders, Phantom Drops, 0/5)
2024-03-08 16:19:59: CALL: Drop progress from active search: 10 Phantom Scrolls (Stream Raiders, 21/60)
2024-03-08 16:20:58: CALL: No drop update from the websocket received
2024-03-08 16:20:58: Progress: 22/60 - Campaign(Stream Raiders, Phantom Drops, 0/5)
2024-03-08 16:20:58: CALL: Drop progress from active search: 10 Phantom Scrolls (Stream Raiders, 22/60)
2024-03-08 16:21:58: CALL: No drop update from the websocket received
2024-03-08 16:21:58: Progress: 23/60 - Campaign(Stream Raiders, Phantom Drops, 0/5)
2024-03-08 16:21:58: CALL: Drop progress from active search: 10 Phantom Scrolls (Stream Raiders, 23/60)
2024-03-08 16:22:52: Earned points for watching:  10, total: 21240
2024-03-08 16:22:57: CALL: No drop update from the websocket received
2024-03-08 16:22:57: Progress: 24/60 - Campaign(Stream Raiders, Phantom Drops, 0/5)
2024-03-08 16:22:57: CALL: Drop progress from active search: 10 Phantom Scrolls (Stream Raiders, 24/60)
2024-03-08 16:23:54: CALL: Maintenance task requests a reload
2024-03-08 16:23:56: CALL: No drop update from the websocket received
2024-03-08 16:23:56: Progress: 25/60 - Campaign(Stream Raiders, Phantom Drops, 0/5)
2024-03-08 16:23:56: CALL: Drop progress from active search: 10 Phantom Scrolls (Stream Raiders, 25/60)
2024-03-08 16:23:57: CALL: Maintenance task waiting until: 16:28:57 (Reload)
2024-03-08 16:23:57: INFO: Websocket[1] stopped.
2024-03-08 16:23:57: INFO: Websocket[1] connecting...
2024-03-08 16:23:58: INFO: Websocket[1] connected.
2024-03-08 16:24:07: CALL: No drop update from the websocket received
2024-03-08 16:24:07: Progress: 26/60 - Campaign(Stream Raiders, Phantom Drops, 0/5)
2024-03-08 16:24:07: CALL: Drop progress from active search: 10 Phantom Scrolls (Stream Raiders, 26/60)
2024-03-08 16:25:07: CALL: No drop update from the websocket received
2024-03-08 16:25:07: Progress: 27/60 - Campaign(Stream Raiders, Phantom Drops, 0/5)
2024-03-08 16:25:07: CALL: Drop progress from active search: 10 Phantom Scrolls (Stream Raiders, 27/60)
2024-03-08 16:25:56: INFO: ShanChan goes OFFLINE
2024-03-08 16:25:57: CALL: Channel update from websocket: ShanChan
2024-03-08 16:26:06: CALL: No drop update from the websocket received
2024-03-08 16:26:06: Progress: 28/60 - Campaign(Stream Raiders, Phantom Drops, 0/5)
2024-03-08 16:26:06: CALL: Drop progress from active search: 10 Phantom Scrolls (Stream Raiders, 28/60)
2024-03-08 16:27:06: CALL: No drop update from the websocket received
2024-03-08 16:27:06: Progress: 29/60 - Campaign(Stream Raiders, Phantom Drops, 0/5)
2024-03-08 16:27:06: CALL: Drop progress from active search: 10 Phantom Scrolls (Stream Raiders, 29/60)

so idk at this point, it felt like things was just going smoother without all the headache of the healthcheck xD

A bit of debugging effort is worth it to make it run smoothly in the future :)
I've reverted the sleep decrease. Instead the maintenance task sets the healthcheck timestamp to the sleep target time.

Well it at least seems to be normalized now, stays in a healthy state and it's doing all three maintenance tasks at least going by the current log:
2024-03-08 22:19:19: Started new container
2024-03-08 22:19:19: Starting: Twitch Drops Miner
2024-03-08 22:19:20: Logging level: CALL
2024-03-08 22:19:21: INFO: Checking login
2024-03-08 22:19:21: INFO: Restoring session from cookie
2024-03-08 22:19:21: INFO: Login successful, user ID: {BLANKED}
2024-03-08 22:19:21: INFO: Websocket[0] connecting...
2024-03-08 22:19:21: INFO: Websocket[0] connected.
2024-03-08 22:19:27: No active campaigns to mine drops for. Waiting for an active campaign...
2024-03-08 22:19:27: CALL: Maintenance task waiting until: 22:29:59 (Cleanup)
2024-03-08 22:30:00: CALL: Maintenance task requests channels cleanup
2024-03-08 22:30:00: CALL: Maintenance task waiting until: 23:00:00 (Points)
2024-03-08 22:30:00: No active campaigns to mine drops for. Waiting for an active campaign...
2024-03-08 23:00:00: CALL: Maintenance task waiting until: 23:19:27 (Reload)
2024-03-08 23:19:27: CALL: Maintenance task requests a reload
2024-03-08 23:19:30: No active campaigns to mine drops for. Waiting for an active campaign...
2024-03-08 23:19:30: CALL: Maintenance task waiting until: 23:49:30 (Points)

will keep an eye on things and report back if I see any issues crop up over the next 24 hours or so.


fix(ui): adjust sizes of launchpad inputs

Description:
Adjust sizes of launchpad inputs.
Motivation and Context:
Input sizes a bit wonky and inconsistent.
How Has This Been Tested?
Manually
Screenshots (if appropriate):
Before:

After:

Types of changes:
UI fix
Checklist:

[x] My code follows the code style of this project.
[x] I have reviewed and updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes where needed.
[ ] All new and existing tests passed.
[x] My commits have been squashed into a concise set of changes.

Coverage remained the same at 20.22% when pulling 5945eec872e44037005b41295a4e9988a28d6113 on mrfelton:fix/home-input-width into e4237e3fd078d7372354bcf793b67a5e170b4cb1 on LN-Zap:next.

tested ACK 9875177


Remove put operation in arrays

Array as put body is invalid, we will add such linter https://github.com/Azure/cadl-azure/issues/2194. So remove it from cadl-ranch.

Agree with Tim, conceptually this is not wrong, I wouldn't remove it


Special:Preferences unaffected by pivot.css changes

Setup

Browsers and versions: Firefox (latest)
MediaWiki version: 1.30
Pivot version: 2.0.0

Issue
I changed the color styling via the MediaWiki:Pivot.css page and it works fine for all pages except the Special:Preferences page where the old color-scheme comes back up.
Any idea what could be causing this and how I could fix it? Thanks!

https://www.mediawiki.org/wiki/Manual:$wgAllowSiteCSSOnRestrictedPages

Thanks... sorry still new to MediaWiki.


HBW-296 Fix displaying errors in select and select_table

I guess select was broken since replacing select2.
And select-table never worked at all.


Synchronize triage configuration.

This pull request was created automatically by the sync-triage-config workflow.
Closes https://github.com/Homebrew/brew/pull/9368.

This change was approved in both https://github.com/Homebrew/brew/pull/9368 and https://github.com/Homebrew/.github/pull/4 I'm going to go ahead and merge.


janet: 1.16.1 -> 1.19.2

Motivation for this change
New janet release.

It works fine:

(+ 1 2 3)
(print "Hello, World!")
(os/exit)

The test test/suite0009.janet fails on macOS.
[0/1] Running all tests.
 1/11 test/suite0000.janet         OK              0.03s
 2/11 test/suite0002.janet         OK              0.02s
 3/11 test/suite0001.janet         OK              0.04s
 4/11 test/suite0003.janet         OK              0.03s
 5/11 test/suite0004.janet         OK              0.03s
 6/11 test/suite0005.janet         OK              0.03s
 7/11 test/suite0006.janet         OK              0.03s
 8/11 test/suite0008.janet         OK              0.03s
 9/11 test/suite0007.janet         OK              0.05s
10/11 test/suite0010.janet         OK              0.03s
11/11 test/suite0009.janet         TIMEOUT        30.02s   killed by signal 15 SIGTERM
>>> MALLOC_PERTURB_=216 /private/tmp/nix-build-janet-1.19.2.drv-0/source/build/janet /private/tmp/nix-build-janet-1.19.2.drv-0/source/build/../test/suite0009.janet
 ✀
stderr:
Starting suite 9...

Summary of Failures:

11/11 test/suite0009.janet TIMEOUT        30.02s   killed by signal 15 SIGTERM

Ok:                 10
Expected Fail:      0
Fail:               0
Unexpected Pass:    0
Skipped:            0
Timeout:            1

I wonder if this is caused by the Nix sandboxing? I am not familiar with mac.

1.16.1 builds fine.
The stuck test is this: https://github.com/janet-lang/janet/blob/1c937ad960d3319f7dad6a534046e2f7f4aaca6c/test/suite0009.janet#L178-L184
The official binary distribution runs the test without errors.

AFAIK these are new tests that weren't in 1.16.1, so that isn't too relevant. I personally don't mind disabling mac support until someone with a mac can debug it.

net/write don't return if net/read is being called in another fiber.  If we insert (ev/sleep 1) before net/read, it works.  The official binary don't suffer from this; it works even if (ev/sleep 1) is inserted before net/write.
1.16.1 also have this problem.  I propose disabling that test and merging this PR anyway.

@taku0 does the test need to be disabled if the package is marked broken? I have added the broken change.

This patch
diff --git a/test/suite0009.janet b/test/suite0009.janet
index 6095bc60..25360d60 100644
--- a/test/suite0009.janet
+++ b/test/suite0009.janet
@@ -174,15 +174,6 @@
   (defer (:close stream)
     (check-matching-names stream)))

-# Test localname and peername
-(repeat 20
-  (with [s (net/server "<IP_ADDRESS>" "8000" names-handler)]
-    (defn test-names []
-      (with [conn (net/connect "<IP_ADDRESS>" "8000")]
-        (check-matching-names conn)))
-    (repeat 20 (test-names)))
-  (gccollect))
-
 # Create pipe

 (var pipe-counter 0)

fixes the build on my M1 machine.
Also this update will remove jpm. Are we ok with that? It would have to be bundled separately then.

Disabling tests might just be hiding the problem - it would be better to work out the cause and fix it upstream.

Also this update will remove jpm. Are we ok with that? It would have to be bundled separately then.

We absolutely should do jpm as a separate package with this.

Makes sense, I will add the patch when we are on macos.

@cideM I added your patch and added you as a co-author, I hope that is ok.

Tested compilation on my M1 machine with NIXPKGS_ALLOW_BROKEN=1 nix-build -A janet . and (+ 1 2 3) and works fine 👍🏻

Anyone feels like taking a stab at jpm so we can get this merged as well?

@peterhoeg do you mean this shouldn't be merged until jpm is packaged? I was hoping they could be separate.

I still have zero knowledge of Janet but it seems to me that if this is merged we end up with a Janet without any package manager in Nixpkgs, right?

@cideM Your choice is an outdated janet or one without jpm unless you want to do the jpm package yourself.

but it seems to me that if this is merged we end up with a Janet without any package manager in Nixpkgs, right?

That was my point as well. At least things work right now (albeit on an older version), whereas no jpm is most definitely a regression.

I would argue is not a regression, but it is a breaking change - jpm is no longer included with janet, it is a separate program. I agree a jpm package would be nice, but it is going to be a breaking change regardless since people will need to update their nix configs.

I don't know when that will be.
Right about now! ;-)

@cideM , I just ripped out aarch64 as it wasn't evaluating there - it's just temporary.

Really appreciated! thank you.

I need to squash these commits but it requires me to force push to your branch @andrewchambers - ok with that?

Sure I don't mind.


[WIP] [RHBA-450] upgrade RHBA image artifacts from 7.0.0.ER1 to 7.0.0.DR4

[RHBA-450] upgrade RHBA image artifacts from 7.0.0.ER1 to 7.0.0.DR4
https://issues.jboss.org/browse/RHBA-450
Signed-off-by: David Ward<EMAIL_ADDRESS>

Note that many env vars described in the image.yaml files were duplicated, and thus removed. They are already included by the concreate tool because they exist in referenced module.yaml files. For example, for jolokia and hawkular env vars. @spolti , we will want to do this in RHDM as well.


Admin creating vaults for other players also creates vault for admin

From Bukkitdev issue:

Making a Vault for another player also makes the chest a Vault for the admin who placed the chest, so when the admin buys/sells etc the money goes to this players Vault and not his own, is there not a way to make a Vault for just the other player without it linking to the admin as well?

Unable to reproduce. Waiting for feedback.


Introduce AudioProcessor::before_drop pre-destructor hook

This allows the processor to send some final events, or move some items to the garbage collector thread. This will help with https://github.com/orottier/web-audio-api-rs/pull/368
In this commit we use the before_drop hook to ensure that the ended event is sent for all AudioScheduledSourceNodes when the stop time is implicit. This fixes https://github.com/orottier/web-audio-api-rs/issues/489

/bench

Really nice!


vago might be broken after recent changes in varnish

As per https://github.com/varnishcache/varnish-cache/issues/2377, recent changes to varnish might have broken vago and any software using it (e.g. varnishstatbeat).

Since vago is using type and ident from fantom, this change doesn't have any effect.
Thanks for the heads up.

👍


Update source code repo on rubygems.org

The source code repository listed for Bundler on rubygems.org is http://github.com/carlhuda/bundler/.  While this is configured to redirect to https://github.com/bundler/bundler, it'd be helpful for API clients if the value were updated in RubyGems.

You should open an issue on their repo: https://github.com/rubygems/rubygems.org

They don't maintain that metadata.  The owner of a gem is responsible for supplying the values.

Oh sorry I thought you meant the link t bundler on rubygems in general not on the actual bundler gem page.

Just updated the rubygems.org metadata, thanks for the heads up @nirvdrum !


fixed Parse overwritting buf_

If Parse() returns true, the while loop will still run once after(I am guessing because there is still data in the serial RX buffer), overwritting the buffer.
This is a non issue under normal conditions, as it would just overwrite near identical data.
However if the second byte is equal to the header (0x0F), Parse() will assume that second byte to be the footer.
This is because the execution branch at the end does not do "prev_byte_ = curr_byte_", while still having set curr_byte_ to the current package, hence skipping the header in the evaluation.

I should note my hardware: Its an ESP32 devboard with an ESP32-WROOM-32.
I am not sure this issue appears on other platforms.

Thanks! This helped me find a bug with our timing. I'm not going to pull it, because we solved the problem by altering the Parse method and I still need the Read method to go through all available SBUS packets - sometimes, we have a delay before the code starts and a lot of packets to read through. Thanks again.


Cannot run mnist example after building from source

Hi, guys:
I am a newbie on mxnet and have encountered issues when deploying mxnet on my machine.
The detailed description is provided as follows.
Any suggestion would be appreciated.
Thanks in advance.
Environment info
Operating System: Ubuntu 16.04 LTS
Compiler: g++ 5.3.1
Package used (Python/R/Scala/Julia): Python
MXNet version: 0.9.4
Or if installed from source: YES
MXNet commit hash (git rev-parse HEAD): a5edbf94094581ee27157eae4f2113115a3994e7
If you are using python package, please provide
Python version and distribution: 2.7.11+
If you are using R package, please provide
R sessionInfo():
Error Message:
Please paste the full error message, including stack trace.
Traceback (most recent call last):
  File "train_mlp.py", line 101, in <module>
    data = mx.sym.var('data')
AttributeError: 'module' object has no attribute 'var'

Minimum reproducible example
if you are using your own code, please provide a short script that reproduces the error.
import os
import logging
import gzip
import struct
try:
    import requests
except ImportError:
    # in rare cases requests may be not installed
    pass

import numpy as np
import mxnet as mx

def download(url, fname=None, dirname=None, overwrite=False):
    """Download an given URL

    Parameters
    ----------

    url : str
        URL to download
    fname : str, optional
        filename of the downloaded file. If None, then will guess a filename
        from url.
    dirname : str, optional
        output directory name. If None, then guess from fname or use the current
        directory
    overwrite : bool, optional
        Default is false, which means skipping download if the local file
        exists. If true, then download the url to overwrite the local file if
        exists.

    Returns
    -------
    str
        The filename of the downloaded file
    """
    if fname is None:
        fname = url.split('/')[-1]

    if dirname is None:
        dirname = os.path.dirname(fname)
    else:
        fname = os.path.join(dirname, fname)
    if dirname != "":
        if not os.path.exists(dirname):
            try:
                logging.info('create directory %s', dirname)
                os.makedirs(dirname)
            except OSError as exc:
                if exc.errno != errno.EEXIST:
                    raise OSError('failed to create ' + dirname)

    if not overwrite and os.path.exists(fname):
        logging.info("%s exists, skipping download", fname)
        return fname

    r = requests.get(url, stream=True)
    assert r.status_code == 200, "failed to open %s" % url
    with open(fname, 'wb') as f:
        for chunk in r.iter_content(chunk_size=1024):
            if chunk: # filter out keep-alive new chunks
                f.write(chunk)
    logging.info("downloaded %s into %s successfully", url, fname)
    return fname

def get_mnist():
    """Download and load the MNIST dataset

    Returns
    -------
    dict
        A dict containing the data
    """
    def read_data(label_url, image_url):
        with gzip.open(download(label_url)) as flbl:
            struct.unpack(">II", flbl.read(8))
            label = np.fromstring(flbl.read(), dtype=np.int8)
        with gzip.open(download(image_url), 'rb') as fimg:
            _, _, rows, cols = struct.unpack(">IIII", fimg.read(16))
            image = np.fromstring(fimg.read(), dtype=np.uint8).reshape(len(label), rows, cols)
            image = image.reshape(image.shape[0], 1, 28, 28).astype(np.float32)/255
        return (label, image)

    # changed to mxnet.io for more stable hosting
    # path = 'http://yann.lecun.com/exdb/mnist/'
    path = 'http://data.mxnet.io/data/mnist/'
    (train_lbl, train_img) = read_data(
        path+'train-labels-idx1-ubyte.gz', path+'train-images-idx3-ubyte.gz')
    (test_lbl, test_img) = read_data(
        path+'t10k-labels-idx1-ubyte.gz', path+'t10k-images-idx3-ubyte.gz')
    return {'train_data':train_img, 'train_label':train_lbl,
            'test_data':test_img, 'test_label':test_lbl}

mnist = get_mnist()

batch_size = 100
train_iter = mx.io.NDArrayIter(mnist['train_data'], mnist['train_label'], batch_size, shuffle=True)
val_iter = mx.io.NDArrayIter(mnist['test_data'], mnist['test_label'], batch_size)

data = mx.sym.var('data')
# Flatten the data from 4-D shape into 2-D (batch_size, num_channel*width*height)
data = mx.sym.flatten(data=data)

# The first fully-connected layer and the corresponding activation function
fc1  = mx.sym.FullyConnected(data=data, num_hidden=128)
act1 = mx.sym.Activation(data=fc1, act_type="relu")

# The second fully-connected layer and the corresponding activation function
fc2  = mx.sym.FullyConnected(data=act1, num_hidden = 64)
act2 = mx.sym.Activation(data=fc2, act_type="relu")

# MNIST has 10 classes
fc3  = mx.sym.FullyConnected(data=act2, num_hidden=10)
# Softmax with cross entropy loss
mlp  = mx.sym.SoftmaxOutput(data=fc3, name='softmax')

logging.getLogger().setLevel(logging.DEBUG)  # logging to stdout
# create a trainable module on CPU
mlp_model = mx.mod.Module(symbol=mlp, context=mx.cpu())
mlp_model.fit(train_iter,  # train data
              eval_data=val_iter,  # validation data
              optimizer='sgd',  # use SGD to train
              optimizer_params={'learning_rate':0.1},  # use fixed learning rate
              eval_metric='acc',  # report accuracy during training
              batch_end_callback = mx.callback.Speedometer(batch_size, 100), # output progress for each 100 data batches
              num_epoch=10)  # train for at most 10 dataset passes

Steps to reproduce
or if you are running standard examples, please provide the commands you have run that lead to the error.

What have you tried to solve it?

When building MXNet from source, I encountered the issue, then I commented out these lines to make sure the build passed. And I tested python binding according to the official instruction and it's OK.
But I cannot successfully import get_mnist() from mx.test_utils, thus I copied the very function and its dependencies, ie, download() and some py modules. Then, the dataset is successfully downloaded but received the above error messages.

Solved by myself.
A legacy version of mxnet had been installed using pip by someone else and the newly compiled mxnet is not installed.
When uninstalled the legacy one and properly installed the newly compiled version, the error gone!


METRON-2270 Update to reflect bro project rename

Contributor Comments
This is a substantial change in order to update the plugin to work with more recent versions of zeek (previously bro).  There were a few cascading issues that required upgrades, most notably due to this, this and this.
As of this PR, zkg.meta points to a librdkafka 1.4.2-RC2.  We may want to wait to merge until 1.4.2 or 1.5.0 are released and update zkg.meta.
Testing
Run ./run_end_to_end.sh
Pull Request Checklist
Thank you for submitting a contribution to Apache Metron's Bro kafka writer plugin.
In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
For all changes:

[X] Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
[X] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
[X] Has your PR been rebased against the latest commit within the target branch (typically master)?

For code changes:

[X] Have you included steps to reproduce the behavior or problem that is being changed or addressed?
[X] Have you included steps or a guide to how the change may be verified and tested manually?
[X] Have you ensured that the full suite of tests and checks have been executed via:bro-pkg test $GITHUB_USERNAME/metron-bro-plugin-kafka --version $BRANCH

[ ] Have you written or updated unit tests and or integration tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] Have you verified the basic functionality of the build by building and running locally with Apache Metron's Vagrant full-dev environment or the equivalent?

We should mention specifically in the PR description that we are updating to zeek version XXXXX.  If this is the PR that does it

Done

My concern with writing it in a README is that it would be prone to being incorrect.  In zkg.meta do we say it requires zeek >=3.0.0.  I tested against 3.0.5 and 3.1.2.  I would rather us pursue a CI process that has a testing matrix for multiple zeek versions, and embed that into the README.  What do you think?

End to end tests are succeeding, but the unit tests appear to be failing so that needs addressed.  Converting this PR to a draft since it's still WIP it seems.

@ottobackwards Unit tests and e2e are both passing now.

for the love of puppies, merge this already

@JonZeolla thanks for the heads up. @rocknsm does still use this plugin. Looks like this PR was closed without merging though? Is this still happening?

That's just a side effect of our merging process, which doesn't use the github built-ins.  This was squash merged as 587e9dac9beeee915f7d0c1116a4432447b5d92e meaning it's in master.  At some point probably not too far out I expect to cut a 1.0.0 release


Add yarn constraints rules requiring that dual CJS/ESM builds and type declarations be exposed for all export subpaths in package manifests

Descriptions

Adapt these rules so that they are applied to all subpath exports, not just 'exports["."]'.
Fix package manifests that violate the new rules.

https://github.com/MetaMask/core/blob/main/packages/notification-services-controller/package.json
https://github.com/MetaMask/core/blob/main/packages/profile-sync-controller/package.json

References

Follow-up from https://github.com/MetaMask/core/pull/4648

See https://github.com/MetaMask/core/pull/4648#discussion_r1758671441

What should we check here? In the case of . we can reasonably expect that the output JS files are located at dist/index.mjs and dist/index.cjs and that the output declaration files are at dist/index.d.mts and dist/index.d.cts. However, that may not be the case for subpath exports, which may be in different directories. For instance, @metamask/notification-services-controllers has a subpath export at ./notification-services/ui, and this points to the relevant files in dist/NotificationServicesController/ui.
Perhaps all we can check is the following?

import.types ends in /index.d.mts
import.default ends in /index.mjs
require.types ends in /index.d.cts
require.default ends in /index.cjs
types are listed first in both import and require


Fix usage of dev-orb-version parameter

@lokst, I see what you're talking about.  It makes me think trigger-integration-tests-workflow was actually using the default dev:alpha version all along, and was therefore broken.  I see where that command passes in the default pipeline-param-map, but this config never actually used it.

It used to be the case that this did not work which was the reason for the current design. I am fairly confident this now works. I will test this shortly and respond asap. If this works now this is a great addition :+1:

@KyleTryon I tried it out on my own orbs' workflow, and it seems to work correctly. :-)


[RTM] Surface sample

Building on #362, this uses the registration produced by bbregister to sample volumes to the subject-native and fsaverage surfaces.
Looks like this will be fairly simple, but mri_vol2surf is pretty flexible in its sampling strategy. For each vertex on the surface, there is a normal vector from the white matter surface to the pial surface, and you can choose a point along that vector (in mm or as a fraction of the cortical thickness from 0-1), the average value along a range (start, stop, step; again in mm or fraction) or the maximum value on a range.
As a starter, I've set it to sample the midpoint of the normal vectors.
Looks like this'll be the thing that finally makes me learn to use JoinNode.
Closes #355.

So we have generated (in #362) a FreeSurfer .dat that goes from the mean EPI (outputted by explicit_mask_epi) to FreeSurfer-conformed T1.mgz space.
Am I correct in reading that we never actually save motion-corrected EPIs in native space? From what I can see, transforms are accumulated and include a template normalization prior to application. If this is the case, what would be the best point to insert into existing workflows (ideally general enough to plug into both basic_wf and basic_fmap_sbref_wf)?

Proposed derivatives target (not yet coded):
fmriprep/
    func/
        lh.sub-<subject_label>_task-<task_label>_run-<run_index>_bold_space-fsaverage_preproc.gii
        lh.sub-<subject_label>_task-<task_label>_run-<run_index>_bold_space-fsnative_preproc.gii
        rh.sub-<subject_label>_task-<task_label>_run-<run_index>_bold_space-fsaverage_preproc.gii
        rh.sub-<subject_label>_task-<task_label>_run-<run_index>_bold_space-fsnative_preproc.gii

Question is mainly how to describe the space. fsaverage seems straightforward. fsnative would be an indicator that the subject is sub-<subject_label>. Should this also reflect the sampling technique (point, average, max)? And should that be in space or a new key/value?
And as to sampling technique, FreeSurfer defaults to nearest-neighbor interpolation, though also provides trilinear.
We can save the sampling/interpolation parameters as JSON. It might make more sense than trying to encode these concepts in the filename.

The file naming scheme looks good to me. In terms of space naming I wonder if we should be more explicit about the resolution of the space we are using - aren't there multiple versions of fsaverage with different number of vertices? I don't know what is the current naming convention in HCP/FreeSurfer world for those.
I would prefer using trilinear interpolation instead of nearest neighbours.
The details of interpolation and samplint technique should be explained in the documentation (and hopefully one day in README - see #268), but I would leave them out of the filename unless we want to provide multiple versions (but I don't see the need for that now).
BTW I checked and FSL's film_gls can take gifti files: https://github.com/Washington-University/Pipelines/blob/master/TaskfMRIAnalysis/scripts/TaskfMRILevel1.v1.0.sh#L156, but I'm not sure if FreeSurfers mri_glmfit can https://surfer.nmr.mgh.harvard.edu/fswiki/mri_glmfit

It would probably be good to figure out the HCP/FS naming conventions for README or parameter recordings, but I think that at the moment  the "which fsaverage" question is answered: "The fsaverage in the derivatives/freesurfer/fsaverage directory."
As an aside, I do think it would be good to be able to choose an alternative template space, though, but it should be also in the derivatives/freesurfer directory, and I'm writing with the assumption that we'll at some point want to make a non-fsaverage template.
So wrt GIFTI, mri_glmfit can't take it directly... it needs surfaces concatenated into a "volume"-based file, and provides mris_preproc for this purpose. I'll try to pin down whether that can take GIFTI, but I have a strong suspicion it can, since mri_vol2surf and mri_surf2surf work facilely with .gii files.

BTW I'm looking through the standard: https://www.nitrc.org/frs/download.php/2871/GIFTI_Surface_Format.pdf
and it seems we should follow the:
fmriprep/
    func/
        sub-<subject_label>_task-<task_label>_run-<run_index>_bold_space-fsaverage_preproc.L.time..gii
        sub-<subject_label>_task-<task_label>_run-<run_index>_bold_space-fsnative_preproc.R.time.gii
        sub-<subject_label>_task-<task_label>_run-<run_index>_bold_space-fsaverage_preproc.L.time.gii
        sub-<subject_label>_task-<task_label>_run-<run_index>_bold_space-fsnative_preproc.R.time.gii

convention.
It's also worth checking if Connectome workbench can read those files and does not complain about any metadata (such as Intent is set to NIFTI_INTENT_TIME_SERIES, AnatomicalStructurePrimary is set to CortexLeft and CortexRight, TimeStep is set to correct TR )

Marked [RTM] for review. Preparing to run ds114 on Sherlock to get FreeSurfer reconstructions to test that a surface-based GLM gives sensible outputs.

Could you mention the new derivatives and a short description of the sampling strategy in the docs?

Was just working on that.

This LGTM assuming the ds114 models fits look reasonable.

At least for film_gls, it looks like we'd need subsampled surfaces and functionals to keep it from taking a very long time: https://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind1404&L=FSL&F=&S=&P=345205 (Also, nipype needs updating for film_gls in surface mode.)
I'm going to test with FreeSurfer's GLM.

On Wed, Apr 5, 2017 at 10:58 AM, Chris Markiewicz<EMAIL_ADDRESS>wrote:

At least for film_gls, it looks like we'd need subsampled surfaces and
functionals to keep it from taking a very long time:
https://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind1404&L=
FSL&F=&S=&P=345205 (Also, nipype needs updating for film_gls in surface
mode.)
I'm going to test with FreeSurfer's GLM.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/poldracklab/fmriprep/pull/391#issuecomment-291944559,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOkp5pXfnAKbS_11M5I0iZexRjC-KxAks5rs9ZVgaJpZM4MdEVE
.

I think it makes sense to go ahead and continue producing at least the fsaverage datasets as we are, because a FreeSurfer-based GLM would typically be in that space that. But I'm not sure how much value there is in producing fsnative time series on the high-res mesh.
Maybe what makes the most sense is to have functionals in three spaces:

fsaverage for FreeSurfer analyses
Sub-sampled fsaverage and fsnative for film_gls-based analyses

So we'd need to output the sub-sampled GIFTI meshes. Possibly in place of the meshes we're currently producing?

Is there an advantage of using full resolution fsaverage? Why is it ok to use it with freesurfer but not with film_gls?

The advantage of using full-resolution fsaverage is that I don't have to figure out how to make my data work with the fsaverage space. It just works like usual, if I'm doing analyses in FreeSurfer.
I assume the difference is that FreeSurfer was designed to work with high-res meshes, while surface analysis was hacked into film_gls? Or possibly FSL users are used to faster analyses from working in the volume. I'm not really clear on how much time the FSL thing should take. I expect a FreeSurfer analysis to take a few hours.

So this really boils down to the question: "If I want to use an atlas, parcellation or segmentation do I need to downsample it first?". For our volume outputs (both native and MNI) the answer is "yes". This is because we downsample the outputs to the native resolution to save space. From a consistency point of view it would make sense to do the same for surfaces (both native and fsaverage).
Does freesurfer GLM even care about the space (other making sure it's consistent across participants)? How much space would we save by downsampling?
BTW did we figure out if freesurfer glm can take gifti as input?

This could be usful:
https://brainder.org/2016/05/31/downsampling-decimating-a-brain-surface/

In that case, I think we also need to distribute the down-sampled fsaverage surface so people can visualize results using FS tools. If it's a non-deterministic process (I'd suspect it is), we might want to piggy-back on HCP's work so that functionals sampled in FMRIPREP and HCP are comparable.

I'm working on figuring out how to shoehorn externally preprocessed data into a FreeSurfer GLM, now.

Good point about visualisation - I forgot that surface viewers in contrast to volume ones do not do resampling on the fly. Not sure what is the best compromise between space saving and ease of use. Have you looked into the Conte69 and 32k_fs_LR spaces?

Not in depth. 32k_fs_LR was on my radar, but I'll also have a look at Conte69.

FSFAST-preprocessed EPI, mapped to fsaverage surface:

FMRIPREP-preprocessed EPI, mapped to `fsaverage surface:

These two images have the exact same color scaling, so we're clearly getting something very close.
I realized that using the bbregister-made registration file was double-dipping, since we apply it to our functional data. In FSFAST land, the volumes are not moved; the registration is calculated and then applied at the time of sampling.
Getting closer to a working GLM.

Reply from a user:

Regarding FMRIPREP: gifti format would be perfect, and I would suggest making a few resolution options available. We tended to go with fsaverage5, but the HCP 32k surface could also be quite useful...

These are level 1 GLM results for ds000114/sub-01/ses-test.
FSFAST (from BIDS source functionals):

FMRIPREP surfaces -> FSFAST:

So I think we're in pretty good shape here. Not only are we
I want to write up some notes on what I actually had to do to get this to run, because it was non-trivial. I started with Doug's advice, but had to also create a global mean and produce an AFNI-ish motion parameter file and hack selxavg3-sess to be a little flexible in that regard. (These aren't the notes. They're just off the top of my head.)
Talked with @chrisfilo and will be emailing the list to get feedback on what would be useful output to them in terms of formats and "stage" of preprocessing. I can also, probably in a separate thread, discuss the issues I had with injecting pre-computed surface datasets into FSFAST. It would be nice if their pipeline were a little more modular; though I suppose only people trying to go from FMRIPREP to FSFAST would think so.
Remaining work to close this issue:

[ ] Find out preferred sampling surfaces (should this be an option, similar to --skip-native, e.g. --conte69? )
[ ] Double check data types in GIFTI files... Was getting some noisy output from wb_view and film_gls, so it could be the FreeSurfer-generated GIFTIs need a little cleaning here, too.

wb_view was complaining about an absence of AnatomicalStructurePrimary field in the metadata, so the latest commit cleans that up. Re-ran ds000114/sub-01/ses-test, and the resulting file produces no complaints in wb_view.