style: format code with Autopep8, Black, ClangFormat, dotnet-format, Go fmt, Gofumpt, Google Java Format, isort, Ktlint, PHP CS Fixer, Prettier, RuboCop, Ruff Formatter, Rustfmt, Scalafmt, StandardJS, StandardRB, swift-format and Yapf #1005
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…Go fmt, Gofumpt, Google Java Format, isort, Ktlint, PHP CS Fixer, Prettier, RuboCop, Ruff Formatter, Rustfmt, Scalafmt, StandardJS, StandardRB, swift-format and Yapf This commit fixes the style issues introduced in e3ff1b5 according to the output from Autopep8, Black, ClangFormat, dotnet-format, Go fmt, Gofumpt, Google Java Format, isort, Ktlint, PHP CS Fixer, Prettier, RuboCop, Ruff Formatter, Rustfmt, Scalafmt, StandardJS, StandardRB, swift-format and Yapf. Details: None
Contributor
|
Here's the code health analysis summary for commits Analysis Summary
|
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| except Exception as e: | ||
| logger.error(f"Error creating transaction: {e}") | ||
| return web.Response(text=json.dumps({'error': str(e)}), status=500) | ||
| return web.Response(text=json.dumps({"error": str(e)}), status=500) |
Check warning
Code scanning / CodeQL
Information exposure through an exception
| except Exception as e: | ||
| logger.error(f"Error getting transaction: {e}") | ||
| return web.Response(text=json.dumps({'error': str(e)}), status=404) | ||
| return web.Response(text=json.dumps({"error": str(e)}), status=404) |
Check warning
Code scanning / CodeQL
Information exposure through an exception
| except Exception as e: | ||
| logger.error(f"Error creating user: {e}") | ||
| return web.Response(text=json.dumps({'error': str(e)}), status=500) | ||
| return web.Response(text=json.dumps({"error": str(e)}), status=500) |
Check warning
Code scanning / CodeQL
Information exposure through an exception
| except Exception as e: | ||
| logger.error(f"Error getting user: {e}") | ||
| return web.Response(text=json.dumps({'error': str(e)}), status=404) | ||
| return web.Response(text=json.dumps({"error": str(e)}), status=404) |
Check warning
Code scanning / CodeQL
Information exposure through an exception
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit fixes the style issues introduced in e3ff1b5 according to the output
from Autopep8, Black, ClangFormat, dotnet-format, Go fmt, Gofumpt, Google Java
Format, isort, Ktlint, PHP CS Fixer, Prettier, RuboCop, Ruff Formatter, Rustfmt,
Scalafmt, StandardJS, StandardRB, swift-format and Yapf.
Details: None