00:46 <politas> !tell kisuke You need to use the the mod identifiers, not the names. There are no spaces in the identifiers for exactly that reason.

00:46 <Qboid> politas: I'll redirect this as soon as they are around.

00:48 <ckanbot> [CKAN] politas commented on issue #2156: Good point https://git.io/vFUy5

00:49 <ckanbot> [CKAN] politas commented on issue #2156: I'm tempted to leave it in, since it may come in useful in the future, and it's only 1493 bytes. https://git.io/vFUyj

02:02 <ckanbot> [CKAN] HebaruSan commented on issue #2156: I suppose it's not important, and the new icon definitely works fine. I'll take a stab at following the full merge process, including change log updates... https://git.io/vFUQf

02:15 <ckanbot> [CKAN] politas commented on issue #2163: My suspicion would be that as events ahave been removed from IUser's main sections, the editors have left them in the NullUser part by accident, not necessarily realising they were there. This PR seems to be removing a bunch of code, but I can't see any impact. Is it possible some of it is used in obscure commandline cases? I mean, the IDE/build process should flag that, I suppose. https://git.io/vFUQg

02:25 <ckanbot> [CKAN] HebaruSan pushed 4 new commits to master: https://git.io/vFU7J

02:25 <ckanbot> CKAN/master ac8c053 Myk: Add filter.png to resources

02:25 <ckanbot> CKAN/master c70b4c4 Myk: Change Filter toolbutton to filter.png

02:25 <ckanbot> CKAN/master 59eef26 Myk: Run Custom Tool on GUI Resources in VStudio

02:35 <ckanbot> [CKAN] politas commented on issue #2156: We've been putting "Merge #<pr> Blah blah blah" as the comment on the Merge commit, to make the merge commits stand out in the history. Other than that, <3<3<3!!!! https://git.io/vFU7C

02:38 <ckanbot> [CKAN] politas closed pull request #2163: Simplify IUser (master...fix/simplify-iuser) https://git.io/vFfKl

02:39 <ckanbot> [CKAN] HebaruSan commented on issue #2163: "Obscure command line cases" is the story behind `DisplaySelectionDialog` / `RaiseSelectionDialog` / `AskUserForSelection`; the command line code uses this to talk to itself in some places, and it has no other current function, in GUI or Core. I wanted to keep this PR's scope narrow, though, so I left that alone.... https://git.io/vFU7u

02:41 <ckanbot> [CKAN] politas commented on issue #2163: NullUser is about allowing tests to run without interrupting the build process, I gather. https://git.io/vFU7w

02:43 <ckanbot> [CKAN] politas commented on issue #2163: Great work, by the way, and very much appreciated! It's very easy for codebases like this to get filled up with unused cruft that no one dares touch. https://git.io/vFU7i

02:49 <ckanbot> [CKAN] HebaruSan commented on issue #2163: Yes, `NullUser` does that, but it also has a strange dual role as a base class for UI-specific child classes. Currently `GUIUser` "is a" `NullUser`, as are `Netkan.ConsoleUser` and `Cmdline.ConsoleUser`, which means that all real errors/notifications the users sees in practice are routed through a class that is named after the idea of _discarding_ them. That's another thing that I decided to leave alone for no

02:52 <ckanbot> [CKAN] HebaruSan commented on issue #2163: Yes, `NullUser` does that, but it also has a strange dual role as a base class for UI-specific child classes. Currently `GUIUser` "is a" `NullUser`, as are `Netkan.ConsoleUser` and `Cmdline.ConsoleUser`, which means that all real errors/notifications the user sees in practice are routed through a class that is named after the idea of _discarding_ them. That's another thing that I decided to leave alone for now

02:53 <ckanbot> [CKAN] HebaruSan commented on issue #2156: That's a good idea; I've added it to the wiki's merging notes to help me remember for next time. Thanks! https://git.io/vFU7A

03:07 <ckanbot> [CKAN] politas commented on issue #2163: That seems odd. Well, if you want to tackle those issues as future projects, it would be most welcome. I find myself flailing in the wind trying to make sense of this code a lot of the time. See #1971 for a good example of that. https://git.io/vFU56

17:11 <schnobs> anyone around, and able to help me cleaning up my ckan installation?

17:11 <schnobs> there must be a hidden config file somewhere, runining my day.

17:12 <schnobs> Linux user.

20:13 <schnobs> repeat question: anyone around, awake, and willing to help me clean up a borked ckan?

20:13 <schnobs> Because I managed to create a situation where it will no longer start at all, not throwing errors either.

20:15 <schnobs> starting point here https://github.com/KSP-CKAN/CKAN/issues/2129

20:15 <Qboid> [#2129] title: ckan just won't start | **CKAN Version:** v1.22.2 Mahia... | https://github.com/KSP-CKAN/CKAN/issues/2129

20:16 <schnobs> Trying to clean things up, I rendered my workaround non-functional.

20:43 <ckanbot> [CKAN] Schnobs opened issue #2164: "check for updates" window is not on the taskbar https://git.io/vFkzK

20:45 <schnobs> ^^^

20:45 <schnobs> I hereby present my submission for the "dork of the week" award.

20:57 <politas> schnobs, I feel your pain.

20:57 <politas> That dialog really ought to appear wherever the CKAN window is.

21:18 <Micha> Good evening.

21:18 <Qboid> Micha: politas left a message for you in #ckan [21.10.2017 08:51:23]: "KDEX installation fix https://github.com/KSP-CKAN/NetKAN/pull/5977 - You can find the status of automated bot runs here: http://status.ksp-ckan.org/"

21:32 <schnobs> politas: in my case, there was no ckan window yet. First run of a new ckan: before we draw a window let's ask about updates. Putting that smack in the middle rather than upper left corner would probably help.

21:33 <schnobs> Or imbuing it with whatever properties it takes to show up in the taskbar.

21:35 <schnobs> Still, I have a weird setup and am well aware of it's quirks. It should not have taken me that long to figure out what's going on.