PHI27 is likely adjacent here.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Aug 4 2017
Aug 3 2017
I'm just going to merge this into T5258. There are two separate issues here:
I retargeted this; I think the proposed solution is not the best solution we can find to the problem.
Aug 2 2017
See Planning for information on progress and priorities.
This is an unusually low-tech solution but I can't think of any reasons why it won't work.
Is there any reason that the rule "if any menu items have the same link target as the request URI, highlight the first one" wouldn't work?
- What's the root problem?
- Why can't they use links?
- How is this different from T12374?
We should probably just remove this workflow, it's not clear to me that there's ever any reason for anyone to run bin/files purge in the modern codebase.
Have you enabled diffusion.allow-http-auth?
Aug 1 2017
Just keeping an eye on this: growth on these shards is slow and both are still below the 80% caution threshold, so I'm punting this for another week.
Jul 31 2017
Jul 30 2017
Jul 29 2017
Most browsers can only give us a timezone offset, like "UTC-7", not a locale name like "America/Los_Angeles". We already attempt to read this value (D15962, T3025#176547) but when I wrote that stuff it was only available in Chrome and not necessarily reliable. We do try to guess the default zone selection based on the information we get from the browser, but currently ask the user to confirm it in all cases.
@kfsone Are you aware of arc diff --only (briefly mentioned above -- "just generate a diff to look at in the web UI, without other slow/complicated steps")? How do you picture arc selfreview differing from arc diff --only?
Jul 28 2017
The simplest way to approach this is probably to do double writes: start writing the new tables, switch readers over, stop writing the old tables.
This could also just go on the existing page at the bottom. We tell people to copy/paste it when submitting bug reports, but it's probably fine if they're including more information, especially since there is a nice walled garden moat around my personally having to deal with it.
See also PHI22.
T12941 is a third case of a user with no mysql or mysqli.
Jul 27 2017
The particulars in T8918 are slightly different, but the root issue (showing too much stuff to users with partial sessions) is the same.
This is vague and may not actually identify a problem; I don't plan to pursue it.
We've closed registration on this install, mooting this.
Dropping these doesn't seem to have caused any major pushback.
This presumably counts as "not much interest" or should move to Discourse now or something, maybe.
This seems to mostly be a matter of taste, and we already have behavior similar to the behavior of git, which seems reasonable.
We don't have reproduction steps for this and thus can't move forward.
This doesn't affect us, but more fuel on the fire -- XSS in example code which ships with PHPMailer (we don't distribute this code):
We appear to have survived this.
Per above, this is not a bug.
No one but me cares.
We kinda did some of this, it can live on in subtasks.
This appears to lack reproduction steps, so we can't move forward.
We aren't going to implement a bin/phd start-missing-daemon command.
What is the network speed of transferring a similar file (e.g., a 400MB file from /dev/urandom) via ssh cat <file>?
Per above, the decision to color the default state is explicit so this is likely just a design tradeoff in the short term. I can test things locally if you want to keep fishing.
There's probably no reason for us to have color: ... on the <select />
Is this the current status here?
I'm just going to merge this into T10448.
This almost certainly has nothing to do with being invited via a project. I'm just going to merge this into T10448, which will moot it.
I suspect this is actually more like: actions on Ponder answers are not covered by the "Ponder Questions" email preferences, because a "Ponder Answer" is not the same type of object as a "Ponder Question".
Jul 26 2017
I think it should be possible to backfill this from the transaction record, but definitely a bit involved. Holding it until we do history (and major/minor versions) makes sense.