| Time |
Nickname |
Message |
|
00:07
🔗
|
GLaDOS |
[13seesaw-kit] 15chfoo pushed 2 new commits to 06development: 02 https://github.com/ArchiveTeam/seesaw-kit/compare/876fc8eefe07...a5cd630f572b |
|
00:07
🔗
|
GLaDOS |
13seesaw-kit/06development 14232d179 15Christopher Foo: Merge branch 'topic/six' into development |
|
00:07
🔗
|
GLaDOS |
13seesaw-kit/06development 14a5cd630 15Christopher Foo: Really delete socket.io file. Closes ArchiveTeam/seesaw-kit#40 |
|
00:17
🔗
|
GLaDOS |
13seesaw-kit/06development 14c544e73 15Christopher Foo: externalprocess.py: Don't use bytes() for encoding in Py2. |
|
00:17
🔗
|
GLaDOS |
[13seesaw-kit] 15chfoo pushed 1 new commit to 06development: 02 https://github.com/ArchiveTeam/seesaw-kit/commit/c544e73f7f970393e85f39b6b4278df16aadd1a5 |
|
00:19
🔗
|
chfoo |
hurray, no more python 2/3 in separate branches |
|
00:22
🔗
|
aaaaaaaaa |
And the peasants rejoice. |
|
00:26
🔗
|
GLaDOS |
[13seesaw-kit] 15chfoo pushed 1 new commit to 06development: 02 https://github.com/ArchiveTeam/seesaw-kit/commit/0543c54265b268931cb09c28cf223d455db1dc96 |
|
00:27
🔗
|
GLaDOS |
13seesaw-kit/06development 140543c54 15Christopher Foo: readme: Mention Py 2/3 compatibility... |
|
00:33
🔗
|
phuzion |
chfoo: You are a beast |
|
08:36
🔗
|
ersi |
chfoo: Nicely done! |
|
16:57
🔗
|
GLaDOS |
13seesaw-kit/06development 1496005d8 15Christopher Foo: __init__.py: Remove seemingly useless __all__ |
|
16:57
🔗
|
GLaDOS |
13seesaw-kit/06development 149878946 15Christopher Foo: Fix various pylint warnings (no-member, compare None, dangerous defaults) |
|
16:57
🔗
|
GLaDOS |
13seesaw-kit/06development 14b1aa44e 15Christopher Foo: Reformat to PEP8. Closes ArchiveTeam/seesaw-kit#30. |
|
16:57
🔗
|
GLaDOS |
[13seesaw-kit] 15chfoo pushed 3 new commits to 06development: 02 https://github.com/ArchiveTeam/seesaw-kit/compare/0543c54265b2...b1aa44e473a0 |
|
17:10
🔗
|
GLaDOS |
13seesaw-kit/06development 1456c8e3e 15Christopher Foo: fixup! Fix various pylint warnings (no-member, compare None, dangerous defaults) |
|
17:10
🔗
|
GLaDOS |
[13seesaw-kit] 15chfoo pushed 1 new commit to 06development: 02 https://github.com/ArchiveTeam/seesaw-kit/commit/56c8e3ef3d482f09db268153fb57c7a686aa4ced |
|
17:37
🔗
|
aaaaaaaaa |
I made the following changes in a fork. I hope they do what I think they do. |
|
17:37
🔗
|
aaaaaaaaa |
https://github.com/12As/seesaw-kit/commit/2c37ba0ec75fa6b99615f06a82ec3442c2399118 |
|
17:42
🔗
|
yipdw |
aaaaaaaaa: what is that supposed to do |
|
17:43
🔗
|
yipdw |
PATMAW doesn't exist as a tracker field |
|
17:43
🔗
|
aaaaaaaaa |
I know that |
|
17:43
🔗
|
aaaaaaaaa |
I was thinking as a way to send messages to all warriors. |
|
17:44
🔗
|
aaaaaaaaa |
Add a special item type and the data is the message you want the warriors to display in a log. |
|
17:44
🔗
|
yipdw |
eh |
|
17:44
🔗
|
yipdw |
I'd rather a separate endpoint |
|
17:44
🔗
|
aaaaaaaaa |
That way people can know if a project is done and they should switch back. |
|
17:44
🔗
|
yipdw |
items have a pipeline that they go through |
|
17:45
🔗
|
yipdw |
FYI, https://github.com/ArchiveTeam/archiveteam-dev-env to test |
|
17:47
🔗
|
aaaaaaaaa |
wait, task not item; the nomenclature throws me off. |
|
17:47
🔗
|
yipdw |
aaaaaaaaa: another problem with special item types: the data model is that one worker at a time has an item, so it isn't a broadcast system |
|
17:47
🔗
|
yipdw |
a CheckForMessage task is fine |
|
17:47
🔗
|
yipdw |
that'd allow us to use any app for it |
|
17:47
🔗
|
yipdw |
that can be its own file |
|
17:48
🔗
|
yipdw |
hell, CheckForMessage could pull the latest tweet off of @at_warrior |
|
17:48
🔗
|
yipdw |
or whatever |
|
17:48
🔗
|
yipdw |
no reason to bloat the tracker :P |
|
17:49
🔗
|
aaaaaaaaa |
Sorry. I'm not that good of a programmer and can barely understand what seesaw does at any given time. Thought I'd try something simple. |
|
17:49
🔗
|
yipdw |
it's not a problem |
|
17:49
🔗
|
yipdw |
I just recommend making a separate Seesaw task |
|
17:50
🔗
|
yipdw |
that has a few benefits: it doesn't require changing the pipeline, it works in warriors *and* in manual runners |
|
17:50
🔗
|
yipdw |
and it can be included/excluded in any pipeline as necessary |
|
17:51
🔗
|
yipdw |
er, any project pipeline |
|
17:51
🔗
|
yipdw |
there's pipelines and then there's the abstract definition of a pipeline |
|
17:51
🔗
|
yipdw |
seesaw-kit contains the latter as well as some useful pipeline tasks |
|
18:00
🔗
|
aaaaaaaaa |
I'll go back to the drawing board and see if I don't drown.. |
|
18:06
🔗
|
yipdw |
if you need help, just ask here |
|
18:06
🔗
|
yipdw |
a Seesaw task isn't too bad actually |
|
18:06
🔗
|
yipdw |
take a look at the SimpleTask class |
|
18:06
🔗
|
yipdw |
most tasks derive from that |
|
18:07
🔗
|
yipdw |
archivebot has some examples of custom tasks; see e.g. https://github.com/ArchiveTeam/ArchiveBot/blob/master/pipeline/archivebot/seesaw/tasks.py#L91 |
|
18:07
🔗
|
ersi |
aaaaaaaaa: Your experimentation is very welcomed though! It's nice that you're fiddlign with the code |
|
18:08
🔗
|
yipdw |
yeah |
|
18:08
🔗
|
yipdw |
we need more people doing it |
|
18:08
🔗
|
aaaaaaaaa |
I sort of wish the documentation were better. Especially with the code spread over so many files. |
|
18:08
🔗
|
yipdw |
please do investigate :P |
|
18:08
🔗
|
yipdw |
I often forget where something is |
|
18:08
🔗
|
aaaaaaaaa |
s/sort of/really |
|
18:09
🔗
|
yipdw |
chfoo has a good start with e.g. http://archiveteam.org/index.php?title=Dev/Seesaw |
|
18:13
🔗
|
aaaaaaaaa |
Maybe it is because they are trying to make it easier on us at work, but what little code I see there has comments inline. Probably been spoiled. |
|
18:17
🔗
|
aaaaaaaaa |
Plus, they get paid by the hour, so the longer it takes the better. |
|
18:19
🔗
|
aaaaaaaaa |
so are two files called pipeline.py used? one by the project and one by seesaw? |
|
18:22
🔗
|
aaaaaaaaa |
that makes more sense now. |
|
18:22
🔗
|
yipdw |
pipeline.py in seesaw is the abstract notion of a pipeline |
|
18:22
🔗
|
yipdw |
pipeline.py in a project is the project's pipeline |
|
18:22
🔗
|
yipdw |
it doesn't have to be named pipeline.py; that's convention |
|
22:52
🔗
|
aaaaaaaaa |
I've tried that warrior dev appliance and the tracker is giving me "Web application could not be started" |
|
22:57
🔗
|
aaaaaaaaa |
Is it supposed to do that until I configure it or some other step I am missing? |
|
23:01
🔗
|
aaaaaaaaa |
I'll try looking through the docs on the machine again. |
|
23:17
🔗
|
aaaaaaaaa |
I don't see what I missed but may have something to do with an SSL/TLS connection it makes with oss-binaries.phusionpassenger.com. |
|
23:50
🔗
|
chfoo |
aaaaaaaaa: except for the bugs mention in the github issues tracker, the appliance should work out of the box. let me try importing the appliance |
|
23:54
🔗
|
chfoo |
no issues for me. did you download it from the dropbox link or did you rebuild your own image? |
|
23:55
🔗
|
aaaaaaaaa |
dropbox link |
|
23:55
🔗
|
aaaaaaaaa |
I'll try reimporting it. |
|
23:57
🔗
|
aaaaaaaaa |
while we wait, you tried looking at tracker page in your browser? |
|
23:59
🔗
|
chfoo |
yes, everything looked fine |