loguru | A lightweight C++ logging library
kandi X-RAY | loguru Summary
kandi X-RAY | loguru Summary
A lightweight C++ logging library
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of loguru
loguru Key Features
loguru Examples and Code Snippets
Community Discussions
Trending Discussions on loguru
QUESTION
I have a pure python package(let's call it main) that has a few functions for managing infrastructure. Alongside, I have created a FastAPI service that can make calls to the main module to invoke functionality as per need.
For logging, I'm using loguru. The API on startup creates a loguru instance, settings are applied and a generic UUID is set (namely, [main]). On every incoming request to the API, a pre_request function generates a new UUID and calls the loguru to configure with that UUID. At the end of the request, the UUID is set back to default UUID [main].
The problem that I'm facing is on concurrent requests, the new UUID takes over and all the logs are now being written with the UUID that was configured latest. Is there a way I can instantiate the loguru module on every request and make sure there's no cross logging happening for parallelly processed API requests?
Implementation:
In init.py of the main package:
...ANSWER
Answered 2022-Mar-20 at 13:06I created this middleware, which before routing calls, configures the logger instance with the UUID with the user of context manager:
QUESTION
I'm not able to disable the traceback on exceptions even after setting LOGURU_BACKTRACE environment variable as False. I've also tried logger.configure() method like this.
ANSWER
Answered 2022-Feb-28 at 11:15The backtrace attribute controls the length of the traceback (if enabled, Loguru displays the entire traceback instead of stopping at the try/except frame like the standard exception does).
However, Loguru respects the sys.tracebacklimit value. You can disable traceback by settings it to 0:
QUESTION
For a third party library* I have to provide a function which consumes some data. My implementation of the consumption requires the data to be posted to an API. So I came up with this structure below:
...ANSWER
Answered 2022-Feb-26 at 21:07It depends on the context manager. In the code you wrote, the HTTPClient you created stays alive because the function it returns maintains a reference to it, even though the variable http_client defined in consumer_provider goes out of scope.
However, HTTPClient.__exit__ is still called before consumer_provider returns, so the consumer function may not work as intended.
You may want to do something like
QUESTION
is there a way clear the log file before using it with the python log library 'loguru'?
Thanks!
...ANSWER
Answered 2022-Feb-20 at 11:21Loguru API does not have the ability to remove/clean up log files. Instead of that, you could either use open('output.log', 'w').close() if you want to erase all contents of the log file. Or check the ability to use log rotation in Loguru if it's suitable for your use case (something like that logger.add("file_{time}.log"))
QUESTION
I'm still reaseaching about Loguru, but I can't find an easy way to do this. I want to use the default options from Loguru, I believe they are great, but I want to add information to it, I want to add the IP of a request that will be logged.
If I try this:
...ANSWER
Answered 2022-Feb-06 at 14:13I make the same question in the Github Repository and this was the answered by Delgan (Loguru maintainer):
I think you simply need to add() your handler using a custom format containing the extra information. Here is an example:
QUESTION
So I have program written in a python file (main.py) that uses classes in an api wrapper file (bluerev.py). I want to use the loguru logger in main.py to collect all exceptions from the program + all requests made in the api wrapper. So the logging set up in the bluerev.py api wrapper looks like this:
...ANSWER
Answered 2022-Jan-07 at 10:59The problem is that loguru uses a completely different mechanism for logging than the classic logging library. The classic logging library constructs a hierarchy of loggers, and log records are propagate up to the root (see the Advanced logging tutorial from the Python docs for reference). But loguru does not use at all this hierarchy, it operates in a totally disjointed way from it.
So if you want the logs emitted using the classic logging library to be ultimately handled by loguru, you have to intercept them.
Here is a Minimal Reproducible Example of my solution :
QUESTION
I'm trying to set up an object instance that will provide values to the Cheetah3 text templating engine.
This is my text template script...
...ANSWER
Answered 2021-Dec-18 at 10:36For reasons I don't yet understand, Cheetah does not follow normal conventions to access object instance attributes and methods.
To fix the problem, I had to replace the $myinfo.keyword_string call with $keyword_string. Then I added searchList=[myinfo] to the Template() call...
QUESTION
from fastapi import FastAPI
from fastapi.middleware.cors import CORSMiddleware
import uvicorn
import time
from loguru import logger
from apscheduler.schedulers.background import BackgroundScheduler
app = FastAPI()
app.add_middleware(
CORSMiddleware,
allow_origins=["*"],
allow_credentials=True,
allow_methods=["*"],
allow_headers=["*"],
)
test_list = ["1"]*10
def check_list_len():
global test_list
while True:
time.sleep(5)
logger.info(f"check_list_len：{len(test_list)}")
@app.on_event('startup')
def init_data():
scheduler = BackgroundScheduler()
scheduler.add_job(check_list_len, 'cron', second='*/5')
scheduler.start()
@app.get("/pop")
async def list_pop():
global test_list
test_list.pop(1)
logger.info(f"current_list_len:{len(test_list)}")
if __name__ == '__main__':
uvicorn.run(app="main3:app", host="0.0.0.0", port=80, reload=False, debug=False)
ANSWER
Answered 2021-Nov-25 at 09:31You're getting the behavior you're asking for. You've configured apscheduler to run check_list_len every five seconds, but you've also made it so that function runs without terminating - just sleeping for five seconds in an endless loop. That function never terminates, so apscheduler doesn't run it again - since it still hasn't finished.
Remove the infinite loop inside your utility function when using apscheduler - it'll call the function every five seconds for you:
QUESTION
Using the python logger I can obfuscate data like this:
...ANSWER
Answered 2021-Nov-17 at 17:01This is how it works:
QUESTION
I have a rather complex peewee query that looks like that:
...ANSWER
Answered 2021-Nov-13 at 23:13Eventually found the Select function in the documentation, which allows me to kind of wrap the previous query:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install loguru
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page
