00:55 <ckanbot> [CKAN] Ruedii commented on issue #2398: The best way to implement this is a series of two alterations:|... https://git.io/vpCEB

00:56 <ckanbot> [CKAN] Ruedii commented on issue #2398: The best way to implement this is a series of three alterations:... https://git.io/vpCEB

01:05 <ckanbot> [CKAN] Ruedii commented on issue #2391: It looks like CKAN is relying on web sessions staying open.... https://git.io/vpCEb

01:14 <ckanbot> [CKAN] HebaruSan commented on issue #2391: @Ruedii , where do you see that in the code? https://git.io/vpCuE

13:22 <ckanbot> [CKAN] DasSkelett commented on issue #2418: Interestingly, the GUI switches to the Modlist tab afterwards, and I have no idea why, as it shouldn't do it on errors though, and I see no code difference between handling errors and handling user cancellation regarding tab switches.... https://git.io/vpOnl

13:25 <ckanbot> [CKAN] DasSkelett commented on issue #2418: So, I created a new `FailWaitDialog()` with error messages as parameters wich executes all GUI calls.... https://git.io/vpZwR

15:57 <ckanbot> [CKAN] DasSkelett opened issue #2428: Mods don't get added to changeset https://git.io/vpWiT

16:01 <ckanbot> [CKAN] DasSkelett commented on issue #2428: So uninstalling and reinstalling worked perfectly. https://git.io/vpWiK

17:15 <ckanbot> [CKAN] HebaruSan commented on issue #2428: Confirmed that the weird self-conflict is a factor. I installed `v0.0329_for_1.4.2` and clicked Refresh and Add available updates, then saw the empty changeset problem as reported. Then I restarted after manually editing my `registry.json` to remove the conflict of Scatterer with Scatterer, and now it's not empty:... https://git.io/vpWHf

17:22 <ckanbot> [CKAN] DasSkelett commented on issue #2428: Maybe a solution would be ignoring self-conflicts on updates?... https://git.io/vpWHF

17:30 <ckanbot> [CKAN] HebaruSan commented on issue #2428: Well, first I'd like to get a better understanding of exactly how and why it breaks and whether this is in fact a recent problem. It's possible that this is highlighting some logic error deep within the relationship resolver, the fixing of which could improve general robustness. Or it's possible that the upgrade logic is tripping over itself somewhere along the line as it attempts to reconcile removing and ins

17:33 <ckanbot> [CKAN] DasSkelett commented on issue #2418: So I added the check if the installation completed despite "canceling", Abit hacky, but working (I think)... https://git.io/vpW7m

18:26 <ckanbot> [CKAN] HebaruSan commented on issue #2428: Confirmed the speculation about `provides`: KSP-CKAN/NetKAN#4809, KSP-CKAN/NetKAN#5414... https://git.io/vpWAB

18:29 <ckanbot> [CKAN] DasSkelett commented on issue #2418: So I added the check if the installation completed despite "canceling", Abit hacky, but working (I think)... https://git.io/vpW7m

18:42 <ckanbot> [CKAN] DasSkelett commented on issue #2418: So I added the check if the installation completed despite "canceling", Abit hacky, but working (I think)... https://git.io/vpW7m

18:42 <ckanbot> [CKAN] DasSkelett commented on issue #2418: So I added the check if the installation completed despite "canceling", Abit hacky, but working (I think)... https://git.io/vpW7m

20:47 <ckanbot> [CKAN] DasSkelett opened pull request #2429: Fix "Apply changes"-button gets enabled without actual changes on "Add available updates"-click (master...FIX/AddUpdatesActivatesApplyButton) https://git.io/vplL5

21:23 <ckanbot> [CKAN] HebaruSan commented on issue #2428: This exception is being caught:... https://git.io/vplO4

21:44 <ckanbot> [CKAN] HebaruSan commented on issue #2428: And this is the content of that exception:... https://git.io/vplGy

21:48 <ckanbot> [CKAN] HebaruSan commented on issue #2428: That's coming from here:... https://git.io/vplZL

22:44 <ckanbot> [CKAN] HebaruSan commented on issue #2428: OK, it looks like what's happening is that `SanityChecker` is being asked to validate a hypothetical situation in which updates are installed _without removing the old versions_. And it always worked that way, but prior to #2339, the exception was avoided because conflicts were done only in terms of identifiers without regard to versions, so the old version of a mod was always considered not to conflict with t

22:45 <ckanbot> [CKAN] HebaruSan commented on issue #2428: OK, it looks like what's happening is that `SanityChecker` is being asked to validate a hypothetical situation in which updates are installed _without removing the old versions_. And it always worked that way, but prior to #2339, the exception was avoided because conflicts were done only in terms of identifiers without regard to versions, so the old version of a mod was always considered not to conflict with t

22:46 <ckanbot> [CKAN] HebaruSan commented on issue #2428: OK, it looks like what's happening is that `SanityChecker` is being asked to validate a hypothetical situation in which updates are installed _without removing the old versions_. And it always worked that way, but prior to #2339, the exception was avoided because conflicts were done only in terms of identifiers without regard to versions, so the old version of a mod was always considered not to conflict with t