aboutsummaryrefslogtreecommitdiff
path: root/examples/05_command_framework/src
diff options
context:
space:
mode:
authorZeyla Hellyer <[email protected]>2017-04-13 12:04:33 -0700
committerZeyla Hellyer <[email protected]>2017-04-13 12:04:33 -0700
commitf0d1157212397ae377e11d4205abfebc849ba9d8 (patch)
treea69d5e1618b427bb3ee1ab595e8e632fea4b6666 /examples/05_command_framework/src
parentAdd Shard Id helpers (diff)
downloadserenity-f0d1157212397ae377e11d4205abfebc849ba9d8.tar.xz
serenity-f0d1157212397ae377e11d4205abfebc849ba9d8.zip
Default to using [0, 1] shards
When using an unsharded client, the shard data sent in the IDENTIFY should default to `[0, 1]`, as sending a null value results in a 4010 response code. The response code for the error looks like: ``` WARN:serenity::client: Failed to boot shard: Gateway(Closed(Some(4010), "Invalid shard.")) WARN:serenity::client: Error starting shard None: Client(ShardBootFailure) ```
Diffstat (limited to 'examples/05_command_framework/src')
0 files changed, 0 insertions, 0 deletions