IRC logs for #buildstream for Thursday, 2020-06-11

*** xjuan has quit IRC01:41
*** tristan has quit IRC02:24
*** tristan has joined #buildstream05:11
*** ChanServ sets mode: +o tristan05:11
tristanGreat, crazy job pickles are broken05:11
tristanhttps://gitlab.com/BuildStream/buildstream/-/jobs/589968432, by branch doesnt break it, it adds tests which reveal that pickled jobs are insane05:12
* tristan doesnt understand `AttributeError: 'ElementFactory' object has no attribute '_types'`, clearly according to pluginfactory.py, that exists; __getstate() wipes it clean and makes it an empty dict, but doesn't cause it to not exist05:13
*** tristan has quit IRC05:52
*** hasebastian has joined #buildstream07:31
*** traveltissues has joined #buildstream07:33
*** cphang has joined #buildstream08:15
*** tristan has joined #buildstream08:38
*** ChanServ sets mode: +o tristan08:38
*** santi has joined #buildstream08:54
*** phildawson has quit IRC09:24
*** phildawson has joined #buildstream09:29
tristanjuergbi, do you prefer to have both Project.get_default_target() and also Project.invoked_from_workspace_element() ?09:31
* tristan sees that the latter was added a long while back by jonathanmaw, and that juergbi added the former afterwards, and wonders why we have both09:32
tristanI suppose the cli and the stream are using this for completely different purposes09:33
*** phildawson has quit IRC09:34
tristanoddly, it looks like the only justification for this extra stuff, is to give the user a message informing them that they can no longer run commands in the directory where a closed workspace once was (while closing it)09:36
tristanhttps://gitlab.com/BuildStream/buildstream/-/blob/master/src/buildstream/_frontend/cli.py#L107909:37
tristanI think that is a very silly feature to have :-S09:38
tristanwhen I type "rm file.txt", I don't get a message saying "Removed file.txt, therefore you can no longer access it"09:38
juergbitristan: get_default_target() is used in more places09:38
tristanyeah, that appears to be the right API09:39
juergbiah, you were talking about the other one09:39
tristanAlso it seems like a sensible contract, the cli doesnt need to know *why* the target is default09:39
juergbiexactly, I'd prefer keeping get_default_target()09:40
tristanI'd like to remove Project.invoked_from_workspace_element(), Stream.workspace_is_required() (what makes this workspace "required" anyway ?) and the silly echo() statement in cli.py09:40
juergbiI'm ambivalent on that hint to the user09:40
juergbiit is somewhat of special situation that you can issue a bst command that makes it impossible to issue any further bst commands for the same project (while in the same directory)09:42
juergbihowever, if the user thinks about what they're doing, it shouldn't be a surprise at all09:42
juergbiso I don't mind removing it09:43
tristanThat does make the assumption that the user was actually in that directory also, rather than typing `bst -C directory...`09:43
juergbiyes but bst -C into the workspace directory seems rather odd09:43
tristanI'm not sure it does09:44
juergbithe point of allowing bst commands from the workspace directory is convenience to avoid the need to `cd` or `-C`09:44
juergbiwell, it's also a shortcut to deal with the workspace element but still09:44
tristanI mean, I first of all think the expectation that bst commands work in a workspace at all is odd, but once it does work, I'm not sure -C is far fetched09:45
* tristan uses -C frequently enough, but mostly from the perspective of running tests on projects in buildstream/tests/ after `tox -e venv /bin/bash`09:46
*** hasebastian has quit IRC09:48
tristanjuergbi, interestingly, if you follow the usage pattern which I recall sander and cs-shadow thought was normal (but I thought was strange), then I think commands would even keep working09:51
tristani.e. if you open the workspace as a subdirectory of the project itself, bst searches higher level directories for the project.conf09:52
tristanAnyway, I'll throw a patch up and try to get back into these confusing duplicates09:52
tristanI'm still unclear on how exactly I should manage these data structures09:53
* tristan throws up https://gitlab.com/BuildStream/buildstream/-/merge_requests/196310:05
tristanand adds some pings10:05
*** tristan has quit IRC11:40
*** tristan has joined #buildstream11:42
*** ChanServ sets mode: +o tristan11:42
WSalmonnow that https://gitlab.com/BuildStream/buildstream/-/issues/1318 is merged can we have a dev tag?11:44
WSalmonis it just as simple as pushing one? i think i can do that, or do you have to do some other magic too?11:45
WSalmonalso as 1.93.3 needs a diffrent project.conf to 1.93.3  i am confused as to why we have not moved to 1.95.1?11:46
WSalmonalso as 1.93.3 needs a diffrent project.conf to 1.93.2/1  i am confused as to why we have not moved to 1.95.1?11:46
WSalmontristan, etc ^11:47
*** toscalix has joined #buildstream12:05
*** Trevinho has quit IRC12:31
*** Trevinho has joined #buildstream12:37
*** Trevinho has quit IRC12:38
*** Trevinho has joined #buildstream12:42
*** xjuan has joined #buildstream14:04
*** toscalix has quit IRC14:57
*** xjuan has quit IRC17:20
*** toscalix has joined #buildstream17:52
*** toscalix has quit IRC18:00
*** hasebastian has joined #buildstream18:26
*** hasebastian has quit IRC18:43
*** santi has quit IRC19:09
*** toscalix has joined #buildstream20:07
*** toscalix has quit IRC20:19

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!