| Time |
Nickname |
Message |
|
13:11
🔗
|
balrog |
Nemo_bis: how do you want errors to be treated? |
|
13:12
🔗
|
Nemo_bis |
balrog: in a way that takes as little manual intervention as possible and doesn't lie about success :P |
|
13:13
🔗
|
Nemo_bis |
It's fine to fail often. |
|
13:13
🔗
|
Nemo_bis |
If there's a way in requests to do some magic without hardcoding status code handling in our code, better so; if not, better avoid. |
|
13:24
🔗
|
balrog |
Nemo_bis: http://pastie.org/private/y6k52loaulcfxwvurnkfq |
|
13:24
🔗
|
balrog |
how does that look? |
|
13:27
🔗
|
Nemo_bis |
There's also status code 4229 |
|
13:27
🔗
|
Nemo_bis |
* 429 |
|
13:28
🔗
|
Nemo_bis |
Hm I'm not sure, we could try that at least for the checkapi / checkindex I guess? |
|
13:35
🔗
|
balrog |
https://kev.inburke.com/kevin/urllib3-retries/ |
|
13:35
🔗
|
balrog |
it doesn't seem to be merged yet though |
|
13:40
🔗
|
Nemo_bis |
ooh I love this guy |
|
13:41
🔗
|
Nemo_bis |
We should probably just wait for it to be merged/released and then use it immediately. :-) More and more benefits from the migration to requests. ;-) |
|
13:45
🔗
|
balrog |
requests itself is written/maintained by kennethre |
|
13:45
🔗
|
balrog |
whom I haven't seen around here for a while... |
|
13:53
🔗
|
Nemo_bis |
sometimes he shows up |
|
13:54
🔗
|
SketchCow |
I can ping him |
|
13:54
🔗
|
SketchCow |
But his wife is sick |
|
13:55
🔗
|
balrog |
Ah, fair enough :( |
|
13:55
🔗
|
balrog |
You don't have to |
|
13:55
🔗
|
SketchCow |
https://twitter.com/kennethreitz/status/482019175595278338 |
|
13:57
🔗
|
balrog |
I see :( |
|
13:58
🔗
|
balrog |
SketchCow: no, I only thought it was interesting that he did requests :) |
|
13:59
🔗
|
ersi |
kenneth is pretty busy with a lot of non-AT stuff |
|
18:16
🔗
|
balrog |
So, any feedback on that? |
|
18:41
🔗
|
SketchCow |
On which |
|
18:42
🔗
|
Nemo_bis |
http://pastie.org/private/y6k52loaulcfxwvurnkfq |
|
18:44
🔗
|
balrog |
no, the PRs |
|
18:44
🔗
|
balrog |
I updated them |
|
18:44
🔗
|
balrog |
https://github.com/WikiTeam/wikiteam/pull/138 and https://github.com/WikiTeam/wikiteam/pull/139 |
|
20:46
🔗
|
balrog |
Nemo_bis: what tools do we have for dokuwiki? |
|
20:48
🔗
|
Nemo_bis |
balrog: easy, none :) |
|
20:49
🔗
|
Nemo_bis |
other than perhaps someone running wget over a certain parameter that sometimes exports text (IIRC) |
|
20:49
🔗
|
balrog |
I see :/ |
|
20:49
🔗
|
balrog |
there is a text export feature |
|
20:49
🔗
|
balrog |
https://www.dokuwiki.org/devel:xmlrpc |
|
20:49
🔗
|
balrog |
there seems to be an api too |
|
20:50
🔗
|
balrog |
http://www.mess.org/lib/exe/xmlrpc.php |
|
20:50
🔗
|
balrog |
probably disabled by default :( |
|
20:50
🔗
|
balrog |
yep |
|
20:51
🔗
|
Nemo_bis |
I should have created a ticket for each wiki engine, add info to each of them as you find something |
|
20:51
🔗
|
balrog |
honestly? I preferred google code |
|
20:51
🔗
|
Nemo_bis |
We also need ideas on how to prioritise efforts. |
|
20:51
🔗
|
balrog |
its bug tracker was more useful |
|
20:51
🔗
|
Nemo_bis |
Yes I like it more too |
|
20:52
🔗
|
Nemo_bis |
I also like bugzilla, but folks hate such stuff nowadays. For instance Wikimedia will migrate to Phabricator even if basically nobody before did it |
|
20:52
🔗
|
balrog |
hmm, first time I hear of phabricator |
|
20:53
🔗
|
balrog |
it looks better than most |
|
21:00
🔗
|
balrog |
Nemo_bis: is emijrp the project maintainer for all of wikiteam? |
|
21:05
🔗
|
balrog |
looks like https://www.dokuwiki.org/export has to be used |
|
21:05
🔗
|
balrog |
I don't think that exports history though |
|
21:06
🔗
|
Nemo_bis |
I'm not sure what "all of wikiteam" could mean :) |
|
21:07
🔗
|
Nemo_bis |
Well every time I file a bug in phabricator I have to file 7 bugs I find in my way |
|
21:07
🔗
|
Nemo_bis |
The last time I almost forgot was there for in the first place, till I found again my original problem one hour later |
|
21:08
🔗
|
Nemo_bis |
Yes, the MediaWiki export feature is more an unicuum than something you can expect to find for many wiki engines |