- User Since
- Jul 10 2018, 12:38 PM (80 w, 3 d)
Is this still "a thing"?
Since T1914 is high priority, this one is too.
What is the status of this issue? Do we still face this bug?
Agreed, this no longer need to be a high priority task.
Mon, Jan 20
Fix typos and address ardumont's comments
closed by 490c2454749679186ffca9cdd3f480e50d2147c2
Fri, Jan 17
Thu, Jan 16
Not a definitive solution but as discussed IRL, let's quick fix the cran lister then refactor it "the proper way"
Wed, Jan 15
I'm fine with the code, but as I already said, I'd really like the commit message to have a paragraph on why this is needed and what problem it solves.
Tue, Jan 14
Mon, Jan 13
Oh maybe it's a mixed up 'arc diff --update' (with D2515)
I'm a bit puzzled by the 2 revisions in this diff. Are they related? I don't really see how/why.
Fri, Jan 10
I would have loved to see a better ci message (with an explanation of the fixed error in there rather than depending on a 2-level external source, aka phab + sentry_ Otherwise OK.
Thu, Jan 9
comment why the build stage is currently disable
IMHO this should be a 'standalone' repo/project. I mean it should be possible to pip install it at least.
Am I reading this wrong, or is the new behavior implemented in this diff not really tested?