I am having a similar issue, with same context as that one.
What's actually happening for me is that on_ready is fired before all on_shard_ready are fired. And it's in a completely random order, sometimes it can do that when only one shard has been connected, but also after 5 shards connected, for a total of 9 shards. So as long as ready event has been dispatched, all missing shards are waiting forever on_shard_ready.

However, after looking at changelogs of discord.py 1.3, I saw changes to those two events, so I tried without PR #2504, and everything was working fine.

I actually have attempted both also on a bare bones test bed on a new venv with a fresh install of d.py:

fetch_offline_members=True

and

fetch_offline_members=False

Both still fail to fire for on_shard_ready() and on_ready() is being fired still. (Tested the events seperately)

Just a quick note that your second example contains your bot token *.*

was regenerated before being sent and i editied it with a link that didnt directly show it, good catch tho

However, after looking at changelogs of discord.py 1.3, I saw changes to those two events, so I tried without PR #2504, and everything was working fine.

Thought I'd reply. shard_ready is dispatched per shard if _ready_state.guilds is populated in the first place. I tested out a few variations of the code changes to verify if it was actually my PR, or something else.

Tests

With _fetch_offline as True:

1. cd9135b and f95ccf5 (Normal) - No guilds are in _ready_state.guilds before Line 1063 is executed. (Verified 10 times)
2. (Revert both changes) - No guilds are in _ready_state.guilds before the same line (in the old commit). (Verified 10 times)

With _fetch_offline as False:

1. cd9135b and f95ccf5 (Normal) - No guilds are in _ready_state.guilds before Line 1063 is executed. (Verified 10 times)
2. (Revert both changes) - shard_ready wasn't ever dispatched in the first place. (Verified 10 times)

These all seemed to have a correlation of not ever receiving the guilds before shard_ready were dispatched so I decided to see if guild_create was even dispatched by Discord.

With cd9135b and f95ccf5:

1. _fetch_offline as True - 4 guilds are created before Line 1063, 2 guild after ready was dispatched (relatively large servers). All guilds are available. They are not added to _ready_state.guilds before ready.
2. _fetch_offline as False - Same as above.

So, I decided to look at where parse_guild_create added the guild to _ready_state.guilds.

Conclusion

Guilds are only added to _ready_state.guilds if they're large guilds, and the large guilds don't seem to be created until after ready has been dispatched, hence why I think shard_ready was never dispatched. Large guilds also aren't added after ready since _ready_state is purely for before ready being dispatched and subsequently deleted after it is dispatched, so it will raise an AttributeError at Line 761.

Feel free to correct me on this.

After some more testing and with the new commit it seems that on_shard_ready() is firing reliably for large bots that need sharding which is fine for what I need now, altho makes testing on a one guild test bot impossible to use on_shard_ready() but that can be solved by just using a basic count system I guess.