Railway•15mo ago

Deploy Logs Incorrectly Highlighting Logs as Error

I'm having this issue with a custom log formatter on python defined like this:

formatter = logging.Formatter(
    '%(asctime)s | %(levelname)s | %(process)d | %(name)s | %(funcName)s | %(message)s',
    datefmt='%d/%m/%Y %I:%M:%S')

formatter = logging.Formatter(
    '%(asctime)s | %(levelname)s | %(process)d | %(name)s | %(funcName)s | %(message)s',
    datefmt='%d/%m/%Y %I:%M:%S')

As you can see from the image, every single line of code is highlighted in red as if it was an error traceback. When I search for "Error" or "Traceback" in the logs, nothing comes up. As far as I know, the application is outputting the logs to the stdout not stderr. This wasn't happening with other deployments of this project. But started happening after one of the deployments produced an error, and now it has spread to this deployment somehow. Project ID: 204612d4-9eda-4816-94fe-b72b0c4919ff Service ID: 8556487e-c1bf-4c48-b4bb-ba5921f9453b Deployment ID: c22d10b5-8bd3-43ad-8329-34e3da556cb1

2 Replies

Percy•15mo ago

Project ID: 204612d4-9eda-4816-94fe-b72b0c4919ff,8556487e-c1bf-4c48-b4bb-ba5921f9453b,c22d10b5-8bd3-43ad-8329-34e3da556cb1

Brody•15mo ago

it's well known that a lot of loggers do print to stderr

Gaming

Programming

Deploy Logs Incorrectly Highlighting Logs as Error