[urbit] cooking while %camping

[c***@gmail.com]

I think I hosed my pier. Someone in :talk mentioned that the whitepaper was
removed from happut-fopnys, but since we have a full versioned filesystem I
was trying to get :tree to request a specific version. I ended up trying
http://localhost:8080/~happut-fopnys/home/2/tree/pub/0-release, which was
evidently a bad idea: My ship, through trying to load ~happut-fopnys'
version of :tree, is now sequentially [%camping %y] and then [%camping %x]
the resources that :tree needs. It looks like a combination of two bugs
made it quite a bit worst though: One, %camping for a file doesn't happen
in parallel, so loading all the resources take a while, and two, it's
compiling /all/ the resources, not just ones that :tree needs. It's pulling
and compiling all the marks, libs, surs, and gens from the galaxy, not just
the ones that it needs. Which is a bad thing, since it's hogging 100% of a
core of my CPU, and looks to be unstoppable - ^C throws a stack trace and
stops the current cook, but doesn't stop the entire request and so is just
reissued...

[Anton Dyudin]

https://github.com/urbit/urbit/issues/357 relevant

Post by c***@gmail.com
I think I hosed my pier. Someone in :talk mentioned that the whitepaper
was removed from happut-fopnys, but since we have a full versioned
filesystem I was trying to get :tree to request a specific version. I ended
up trying http://localhost:8080/~happut-fopnys/home/2/tree/pub/0-release,
which was evidently a bad idea: My ship, through trying to load
~happut-fopnys' version of :tree, is now sequentially [%camping %y] and
then [%camping %x] the resources that :tree needs. It looks like a
combination of two bugs made it quite a bit worst though: One, %camping for
a file doesn't happen in parallel, so loading all the resources take a
while, and two, it's compiling /all/ the resources, not just ones that
:tree needs. It's pulling and compiling all the marks, libs, surs, and gens
from the galaxy, not just the ones that it needs. Which is a bad thing,
since it's hogging 100% of a core of my CPU, and looks to be unstoppable -
^C throws a stack trace and stops the current cook, but doesn't stop the
entire request and so is just reissued...
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an
.
For more options, visit https://groups.google.com/d/optout.