VITAS changed the topic of #spacedock to: Problems?: https://github.com/KSP-SpaceDock/SpaceDock/issues | Matrix/Riot Chat: https://im.52k.de +spacedock:52k.de Feel free to ask for help, we only bite a little bit! | If you want to help, please check https://github.com/KSP-SpaceDock/SpaceDock-Backend/issues/5 :) | <VITAS> inet users have the attentionspan of a squirrel....oh a nut!
oeuf has joined #spacedock
egg has quit [Ping timeout: 190 seconds]
HebaruSan has left #spacedock [#spacedock]
AllisTauri[m] has joined #spacedock
<AllisTauri[m]> Ok, let's try this:
VITAS[m] has joined #spacedock
<VITAS[m]> wow
<AllisTauri[m]> I'm sorry I couldn't split it in a more convenient way; usually I try to make atomic commits, but in this case many of the changes rely on each other.
<VITAS[m]> the amount is huge. thank you
<VITAS[m]> i just merged it
<AllisTauri[m]> Thanks!
<AllisTauri[m]> I've tested in using existing docker environment as much as I could manually.
<AllisTauri[m]> Want to make some kind of automated API test that would at least call ALL the methods there are with appropriate arguments/data. A kind of smoke-test.
<AllisTauri[m]> Thanks!
<AllisTauri[m]> I've tested it using existing docker environment as much as I could manually.
<AllisTauri[m]> Want to make some kind of automated API test that would at least call ALL the methods there are with appropriate arguments/data. A kind of smoke-test.
<VITAS[m]> e
<VITAS[m]> What do you need from me to do that?
<VITAS[m]> You cant imagine how happy iam to see some development progress on the code
<AllisTauri[m]> I'll make it (smoke-test) to work locally in dev environment first; then we could try to add it to alpha/beta by changing its config.
<VITAS[m]> Im happy to give you acc to the alpha and beta host if you like.
<AllisTauri[m]> Certainly to alpha -- to be able to test the changes. Along with some instructions on how to use it)
<VITAS[m]> Send me your key and ill add you as soon as im at one of my computers
<VITAS[m]> (do that via irc or matrix. I dont use discord)
AllisTauri[m] has quit [Quit: Idle timeout reached: 10800s]
VITAS[m] has quit [Quit: Idle timeout reached: 10800s]
HebaruSan[m] has joined #spacedock
<HebaruSan[m]> Any gunicorn experts available for a chat about logging?
VITAS[m] has joined #spacedock
<VITAS[m]> you can ask djerun i think
<VITAS[m]> when hes arround :/
<Lartza> I mean, what about logging
<Lartza> HebaruSan[m]
<HebaruSan[m]> I want more output from the GitHub web hook handler, since it's still not working (if VITAS populated the secret string)
<HebaruSan[m]> There's a --log-file command line argument for gunicorn that might help, and I wanted to discuss how best to set it up, or if there were better alternatives
<Lartza> Oh, my gunicorn thingy just logs to systemd journal
<HebaruSan[m]> Do you know if that's set up for SpaceDock?
<Lartza> I mean if it runs with systemd... :S
<Lartza> Then stderr etc will go to journal
<Lartza> Apparently depends on gunicorn version also, but I'm using Arch so I have the latest that logs to console
<HebaruSan[m]> Ahh yes, SD uses R19 which says it doesn't log to console
<HebaruSan[m]> However the log file flag can be used to enable that, so maybe that's the way to go
<HebaruSan[m]> So I run `journalctl` to see those logs?
<Lartza> yeah, journalctl -u <servicename> to get just that service
<HebaruSan[m]> Awesome, this is just what I was looking for. It has entries for a syntax error from two pulls ago that wasn't outputting anywhere else. Thanks!
<Lartza> Hehe, git deploy took waaay to long for me to get working too, than it should have taken
<RockyTV> are you guys going to merge any other changes to alpha?
<HebaruSan[m]> Is there a way to propagate errors out to the command line so I can see them when I'm restarting services?
<HebaruSan[m]> Last time it just said something about a dependency failing. Not which dependency, nothing about what happened to it.
<HebaruSan[m]> It was a syntax error in a Python file, which AllisTauri helpfully fixed in PR 205
<HebaruSan[m]> RockyTV as I understand it the plan is that from now on, everything will be merged to the alpha branch first
<HebaruSan[m]> Should we try to upgrade to a more recent gunicorn? Or is it not important?
<djerun> HebaruSan[m]: the problem is that the way home after work takes so long I'm way too tired to do anything when I arrive at home and I still haven't deviced on which broken mobile internet option is the least broken, Saturdays are currently fully blocked so only Sundays remain for everything I wanted to do that week... I hope it'll change rather soonish
<RockyTV> just wondering
<RockyTV> all the changes we had (such as renaming the namespace to SpaceDock) were discarded then?
<HebaruSan[m]> I rebased and cleaned them up, but apparently they do not actually work: https://github.com/KSP-SpaceDock/SpaceDock/pull/202
<HebaruSan[m]> So it has been suggested to cherry-pick a few or re-develop them from scratch instead
<HebaruSan[m]> That whole question is kind of in limbo but it's looking like that's how it'll shake out
<RockyTV> okay, file version commit is rebased
VITAS[m] has quit [Quit: Idle timeout reached: 10800s]
<RockyTV> HebaruSan[m], DasSkelett do you prefer if I just squash the commits or do you want to do it?
<RockyTV> like, should I amend the commit and force push or push a new commit?
<HebaruSan[m]> I would defer to the project policy, but as far as I know there isn't one. Personally I have a slight preference for amending since it leaves the revision history easier to browse.
<RockyTV> done