lightseek-bot opened a new issue, #614:
URL: https://github.com/apache/tvm-ffi/issues/614

   Hi @tqchen @junrushao 
   
   It would be great to add a `TVM_FFI_LOG_LEVEL` environment variable that 
controls the logger level for **both the C++ and Python sides**.
   
   CuteDSL depends on `apache-tvm-ffi`, and we're currently seeing a number of 
warning logs emitted during runtime initialization. These messages are quite 
noisy and can be distracting for end users. Having a unified log-level control 
would allow downstream projects to suppress or adjust these logs as needed 
without modifying code.
   
   This would make integration cleaner and provide a more consistent logging 
experience across the entire `apache-tvm-ffi` stack.
   
   example
   ```
   Warning: NING] Field "binding_blocks" in type 
"script.ir_builder.relax.FunctionFrame" duplicates an ancestor field in 
"script.ir_builder.relax.SeqExprFrame". Child types should not re-register 
inherited fields.
   Warning: NING] Field "output" in type 
"script.ir_builder.relax.FunctionFrame" duplicates an ancestor field in 
"script.ir_builder.relax.SeqExprFrame". Child types should not re-register 
inherited fields.
   Warning: NING] Field "binding_blocks" in type 
"script.ir_builder.relax.FunctionFrame" duplicates an ancestor field in 
"script.ir_builder.relax.SeqExprFrame". Child types should not re-register 
inherited fields.
   Warning: NING] Field "output" in type 
"script.ir_builder.relax.FunctionFrame" duplicates an ancestor field in 
"script.ir_builder.relax.SeqExprFrame". Child types should not re-register 
inherited fields.
   /home/runner/.local/lib/python3.12/site-packages/tvm_ffi/registry.py:85: 
UserWarning: Field 'span' in 'ir.TupleType' duplicates an ancestor field. Child 
types should not re-register inherited fields.
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to