Unlisted package doesn't show login information

[FMorschel]

I'm not 100% sure this is a bug, but I figured I should raise it anyway:

I'm logged in. If I go to the home or search, or even open a specific package from the search list, from all pages, I see my data above as logged in.

But if I open https://pub.dev/packages/analysis_server_plugin (WIP package that doesn't show on search), I can't see my data above as logged in and pressing the button for login doesn't do anything (splitted both from the same window for the screenshot):

[isoos]

There are couple of things that are strange here:

1. The package is the first name match hit for me:

2. The signed-in information is present for me.

However, there was a change that may affect this (#9027). Could you try to verify the following: on the package page, when the page seems to be not signed in, hit force reload (e.g. ctrl+shift+reload button or similar), and see what happens? My theory is that the browser cached the previous state of the page and didn't even went to the server for re-validating it.

[FMorschel]

Yes, I can see the login information after doing that. I did press refresh some times, but I guess I forgot about force reload. Thanks!

I've also just tried searching for the package name again, and it does show up... I figured it was set as unlisted before. So weird!

Is there anything I can do to help you see if there was some underlying bug here? If there isn't, feel free to close this.

[isoos]

I figured it was set as unlisted before.

Did you set/unset the unlisted status recently?

[FMorschel]

No, I didn't. This is a tools.dart.dev package, and I'm not a Googler. Maybe @srawlins would know if this was actually unlisted once. I just said so because I could not search for it, as you can see in the screenshot above.

[isoos]

Ah, ok, we've figured out the search part: you were sorting by downloads. In such cases, we don't promote exact name matches. At least that part is not a bug, it is intended behavior.

The other parts seem to be a caching issue, I am bit unsure whether it is only client-side, or we also cache at a CDN too much.

[FMorschel]

Oh, I must've selected that by mistake somehow. I didn't touch the sorting. Maybe it came from opening trending-like options on home, I can't remember. Alright, thanks for figuring that out! I'll keep it in mind.

The other parts seem to be a caching issue, I am bit unsure whether it is only client-side, or we also cache at a CDN too much.

If I hit anything like that again, is there anything I can do to help you identify this?

[isoos]

If I hit anything like that again, is there anything I can do to help you identify this?

This is an unintended side-effect of #9027, considering it as a bug, and should fix it soon (hopefully we will have somebody to roll back the live site too until that happens).