Incorrect status code for duplicate email on registration, using 500.

[mattsmithies]

Problem description

Using the API, when you attempt to register a new account with a username that has already been used, and the validation passes, the server throws a 500 error, indicating a server crash, this is incorrect.

Step to reproduce

Steps to reproduce the behavior:

1. API register new user that duplicates a present user.

Expected behavior

The server should not crash, nor provide an exception, status code should be 409 rather then 500 as the username is a state in the system that already exists.

Screenshots

[Nana-EC]

Thanks @mshakeg we'll take a look. As usual if it's a simple change on the command line it's just a case of scheduling the work or approving a PR of your own. Some of these items are likely consensus node changes which require much more design and coordination. Just FYI as we look into this.

[mshakeg]

@Nana-EC all 3 of the config options listed would likely require changes to the consensus node. The last option i.e. allowUnlimitedContractSize will likely also require changes to the relay assuming the relay validates contract bytecode size to be <24KB before attempting to create the file.

[Nana-EC]

Hey @mshakeg , The team looked into this and as we discussed earlier on it does seem this requires consensus node changes and in other places relies on Hardhats ability to inform the modification. This isn't something we're able to explore further at this time.

However, we'll look to revisit once the modularized hedera services is completed. There may some potential options in that case.

[Nana-EC]

Additionally, we're going to check to see if any of these items directly map to current node configs. If so developers can be unblocked by configuring their local properties to set these items ahead of running hardhat tests