Hm, this screenshot made me dig a bit into the whole thing, so here is what I've found:
First, my date format is different because of my settings:

• Default settings of this instance: F5042482, with date format: F5042480
• My default settings: F5042481 with my date format: F5042479

Here's the proof: F5042439

This looks like the update changed the behaviour, not sure if this is intended, but it broke configs, that worked before. I currently fixed this by chaning my config to:

{
  "100": {
    "name": "Unbreak Now!",
    "short": "Unbreak!",
    "color": "pink",
    "keywords": [
      "unbreak"
    ]
  },
  "90": {
    "name": "Needs Triage",
    "short": "Triage",
    "color": "violet",
    "keywords": [
      "triage"
    ]
  },
  "80": {
    "name": "High",
    "short": "High",
    "color": "red",
    "keywords": [
      "high"
    ]
  },
  "70": {
    "name": "Higher than normal",
    "short": "Higher than normal",
    "color": "orange",
    "keywords": [
      "high-than-normal"
    ]
  },
  "50": {
    "name": "Normal",
    "short": "Normal",
    "color": "yellow",
    "keywords": [
      "normal"
    ]
  },
  "25": {
    "name": "Lower than normal",
    "short": "Lower than normal",
    "color": "green",
    "keywords": [
      "lower-than-normal"
    ]
  },
  "1": {
    "name": "Low",
    "short": "Low",
    "color": "sky",
    "keywords": [
      "low"
    ]
  },
  "0": {
    "name": "Wishlist",
    "short": "Wishlist",
    "color": "skyblue",
    "keywords": [
      "wishlist"
    ]
  }
}

I was able to track this down: This is happening since rP8008ade9af46: Use keywords instead of ints to update task priority in ManiphestEditEngine.

Should not, but looks like there are. I updated to master now, and it works now.

That's weird since I exactly did the same with my version from above. Did you used the current or my version? Or should I update and try if I can reproduce it at the master?

Thanks :)

Version infos are:

phabricator
    0d1654446be6de43b2bd12fcc247db0dc1a46464 (Sat, Jun 10) 
arcanist
    c04f141ab0231e593a513356b3832a30f9404627 (Fri, Jun 9) 
phutil
    74a1350416eb2df825c2315d6519bee03f77bee9 (Mon, Jun 5)

There's a typo in the headline, but I can't it :(

Unless you can define a different default dashboard for logged in and logged out users, yeah.
The problem I see:

• I run a phabricator instance where the main part is only accesible for logged in users, but logged out users can still see some tasks.
• My problem: I want to inform my users about different upcoming events etc, for example per text panel
• The logged out users should not be able to see these messages, so I restricted some panels
• The whole problem would be easy to solve, if admins can define: logged in users get dashboard a), logged out users get dashboard b) in my situation

ah, found it. My fault before was, that I only digged into DB phabricator_auth, but i found it now at phabricator_user, table phabricator_session.

In which table can I find them?

Thank you very much, I'll take a look :)

It's like before: Neither the orange thing appears nor am I listed as "busy" at my profile. I'm listed as available there.

I created a test-event now, it starts in an hour, and I will take a look if this occurs again.

@chad Can you land this revision yourself, or give me the permissions to do so? I'm currently not able too :-/

• Fixed issue pointed out by @chad

hm, ok, that was the reason. I don't checked that, sorry. Feel free to comandeer that rev, and upload a better patch.

At least it did what I wanted, and it worked without an error:
Before:

Going to upload a fix myself.

FYI, there is a report about a regression from multiple users at WMFs-Phabricator: https://phabricator.wikimedia.org/T144338

Maybe it might be a good idea to allow people to create own Guides? Could be helpful for recuring setup stuff for newusers for example, like we got it at our instance.

This instance isn't updated yet, is it? We got that error still....

I hope this is ok, since this is my first patch actually...

I'm going to upload a patch in a few minutes (I can't claim the task :-/).

I got code 500 as I checked out from this instance, was about 23:50 UTC, yesterday. Maybe related? After getting that code, I tried it again after about 10 seconds, then, everything was ok.

I expect, that I can a) don't add commits etc, no matter, if I press the button at the task nor at the commit for example, or b) I can do it at both ways.

@epriestley Why? Actually I think this is confusing.

Thanks :).

A few questions...

Ah, ok, that was my fault. I actually had no saved querys, so I didn't see that option ;) Thanks for helping :)

Yep, sry, I didn't know that that was your test account, but @epriestley told me at IRC.

@chad some of your commits are affected too, for example rP695f0b09b23761c813b015c2b62075cbdee1de59, better if you add for example a Ref T99999 ;)

Strange. I tried it again, now I can't reproduce it too, but the history said, that I didn't make a fault.