tpb has quit [Remote host closed the connection]
tpb has joined #symbiflow
Degi has quit [Ping timeout: 265 seconds]
Degi has joined #symbiflow
_whitelogger has joined #symbiflow
krogozinski has quit [Quit: ZNC 1.7.5 - https://znc.in]
citypw has joined #symbiflow
az0re has quit [Remote host closed the connection]
az0re has joined #symbiflow
OmniMancer has joined #symbiflow
citypw has quit [Ping timeout: 240 seconds]
FFY00 has quit [Ping timeout: 272 seconds]
FFY00 has joined #symbiflow
kgugala has joined #symbiflow
kgugala_ has quit [Ping timeout: 258 seconds]
kgugala has quit [Read error: Connection reset by peer]
kgugala has joined #symbiflow
_whitelogger has joined #symbiflow
kgugala_ has joined #symbiflow
kgugala has quit [Read error: Connection reset by peer]
kgugala has joined #symbiflow
krogozinski has joined #symbiflow
kgugala_ has quit [Ping timeout: 256 seconds]
_whitelogger has joined #symbiflow
citypw has joined #symbiflow
kgugala_ has joined #symbiflow
kgugala has quit [Ping timeout: 264 seconds]
kgugala has joined #symbiflow
kgugala_ has quit [Ping timeout: 258 seconds]
futarisIRCcloud has joined #symbiflow
tux3 has quit [Changing host]
tux3 has joined #symbiflow
<_whitenotifier-f> [prjxray] fox6666 opened issue #1490: PR bitstream size - https://git.io/Jke6S
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
citypw has quit [Ping timeout: 240 seconds]
whitequark has joined #symbiflow
<whitequark> mithro: i figured out why the conda installer doesn't work on debian
<whitequark> when your install script runs pip, it really does run pip from the conda environment, and that uses the conda python
<whitequark> however... conda python, for some incomprehensible reason, loads a third of the packages from the conda env, a third from ~/.local, and a third from /usr
<whitequark> in other words, a classic conda experience
<whitequark> here's why it's broken: https://stackoverflow.com/a/51640558/254415
<tpb> Title: Global pip referenced within a conda environment - Stack Overflow (at stackoverflow.com)
kgugala has quit [Ping timeout: 258 seconds]
kgugala has joined #symbiflow
az0re has quit [Remote host closed the connection]
az0re has joined #symbiflow
<mithro> @whitequark: I like you wish there was a better option than Conda, but so far have not found one.
<mithro> We are slowly working towards supporting both docker and static compiled binaries
<mithro> umarcor is doing some excellent work in that direction
<mithro> Pip and yowasp style stuff is also interesting
<whitequark> mithro: I'm not actually opposed to using Symbiflow's conda with isolated environments
<whitequark> conda in this case is an implementation detail that I (in theory) do not ever have to touch or care about
<whitequark> unfortunately, in practice, the way symbiflow invokes conda is deeply flawed, and I'm having to fix that
<whitequark> why does it download a 12 MB file from sharepoint and feed it into tar?!
<mithro> @whitequark: any idea how we could "poison" the system stuff so CI explodes if it is accidentally used?
<whitequark> run it on a fresh debian install *grin*
<mithro> @whitequark: that is the VPR architecture description - it should be more sensibly generated by CI soon
<whitequark> let me do a more serious check though
<mithro> Brb just getting up
<whitequark> i'm not completely certain what the conditions for blowup are
<whitequark> mithro: with the conda env activated, run: python -c "import sys; assert all('/usr' not in path for path in sys.path)"
<mithro> @whitequark BTW the way the install "should work" is -- (step 1) download+install conda, (step 2) create environment using environment.yml file, (step 3) start doing stuff
<mithro> There is currently a (step 2b) which is "manually download the vpr configuration data" which will hopefully go away soon
<mithro> @whitequark Where we are and where we want to be are never quite the same :-/
<whitequark> it's not really that hard to write a working install script, which i have demonstrated by spending a hour today to do so
<whitequark> all i had to do was to read the conda docs
<whitequark> anyway, as long as you fix it, it's fine
andrewb1999 has joined #symbiflow
mkru has joined #symbiflow
OmniMancer has quit [Quit: Leaving.]
<_whitenotifier-f> [make-env] mithro opened issue #19: Convert to using GitHub actions for CI (rather than Travis CI). - https://git.io/Jkvmy
<whitequark> great!
<mithro> whitequark: I think a bunch of the issues we see in conda world stem from there being is a pretty strong mismatch between what the people who are paying the conda devs to do work (mostly enterprises like universities) and the majority of users (scientists/programmers) really want.
mkru has quit [Quit: Leaving]
<whitequark> I used to have a very negative opinion of conda; I no longer really think that for a few different reasons
<whitequark> I think Symbiflow shipping a conda-based toolchain that does not expose the end user to conda issues is basically fine. not perfect, but fine
titanbiscuit has quit [Ping timeout: 265 seconds]
<whitequark> what I really hate though is having to work around conda issues myself, having spent several years doing that as an employee
<whitequark> anyway, once you address all of the issues I filed, I think the Conda distribution of the toolchain should be usable for most people as long as they never actually touch the conda environment inside
titanbiscuit has joined #symbiflow
andrewb1999 has quit [Quit: Konversation terminated!]
<mithro> whitequark: I'm mostly distracted with finishing off getting stuff published for the skywater-pdk stuff, hopefully acomodi or someone else will be able to finish off that stuff
<whitequark> sure, that works