Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

How to disable debug logging?#467

Unanswered
Massukio asked this question inQ&A
Jun 18, 2025· 1 comments· 8 replies
Discussion options

I was developing python project and the program has its own logging.

But somehow the robotcode lsp prints the debug log into my program logs like the following.

2025-06-18 15:25:41,210 - [CRITICAL] - robotcode.language_server.common.parts.diagnostics.DiagnosticsProtocolPart - End analyzing workspace for 2 documents took 0.0000 seconds2025-06-18 15:25:41,211 - [CRITICAL] - robotcode.language_server.common.parts.diagnostics.DiagnosticsProtocolPart - Start collect workspace diagnostic for 2 documents2025-06-18 15:25:41,218 - [CRITICAL] - robotcode.language_server.common.parts.diagnostics.DiagnosticsProtocolPart - End collect workspace diagnostic for 2 documents took 0.0150 seconds2025-06-18 15:25:41,231 - [CRITICAL] - robotcode.language_server.common.parts.diagnostics.DiagnosticsProtocolPart - Start analyzing workspace for 2 documents2025-06-18 15:25:41,233 - [CRITICAL] - robotcode.language_server.common.parts.diagnostics.DiagnosticsProtocolPart - End analyzing workspace for 2 documents took 0.0000 seconds2025-06-18 15:25:41,234 - [CRITICAL] - robotcode.language_server.common.parts.diagnostics.DiagnosticsProtocolPart - Start collect workspace diagnostic for 2 documents2025-06-18 15:25:41,240 - [CRITICAL] - robotcode.language_server.common.parts.diagnostics.DiagnosticsProtocolPart - End collect workspace diagnostic for 2 documents took 0.0000 seconds

Is there a way I can disable these logs to be printed?

You must be logged in to vote

Replies: 1 comment 8 replies

Comment options

I'm not sure I understand your situation completely.

To better assist you, could you please provide some additional information:

  • Are you using/starting the RobotCode language server or the RobotCode analyzer in your project?
  • What IDE/Editor are you using?
  • Where exactly are you finding these logs?
  • Where do you expect to find your logs instead?

A bit more context would be helpful.

These logs should normally only appear in the process where RobotCode is being executed. RobotCode uses Python's standard logging functionality, so you can disable these logs with the appropriate Python logging configuration. However, I don't have a specific example readily available at the moment.

You must be logged in to vote
8 replies
@d-biehl
Comment options

Thank you for that information. However, I need to clarify:
As long as you haven't directly integrated the RobotCode language server or analyzer into your project, you shouldn't be seeing these logs.
To better help you, could you please provide more details:

What type of project are you working on? Is it a Robot Framework library or a RobotCode extension?
Where exactly are these log messages appearing?

This information will help me understand the issue and provide a more targeted solution.

@Massukio
Comment options

I am working on a robotframework library, and when executing the robot file to run the test, the following logs will keep printing in my debug.log.

2025-07-01 11:46:28,930 - [DEBUG] - robotcode.robot.diagnostics.namespace.Namespace - Start Initialize Namespace for c:\Users\...2025-07-01 11:46:28,934 - [DEBUG] - robotcode.robot.diagnostics.namespace.Namespace - Start importing default libraries for c:\Users\...2025-07-01 11:46:28,934 - [DEBUG] - robotcode.robot.diagnostics.imports_manager.ImportsManager - Start loading library BuiltIn()2025-07-01 11:46:28,934 - [DEBUG] - robotcode.robot.diagnostics.imports_manager.ImportsManager - End loading library BuiltIn() took 0.0000 seconds2025-07-01 11:46:28,936 - [DEBUG] - robotcode.robot.diagnostics.imports_manager.ImportsManager - Start loading library Easter()2025-07-01 11:46:28,937 - [DEBUG] - robotcode.robot.diagnostics.imports_manager.ImportsManager - End loading library Easter() took 0.0000 seconds2025-07-01 11:46:28,937 - [DEBUG] - robotcode.robot.diagnostics.imports_manager.ImportsManager - Start loading library Reserved()2025-07-01 11:46:28,937 - [DEBUG] - robotcode.robot.diagnostics.imports_manager.ImportsManager - End loading library Reserved() took 0.0000 seconds2025-07-01 11:46:28,938 - [DEBUG] - robotcode.robot.diagnostics.namespace.Namespace - End importing default libraries for c:\Users\... took 0.0000 seconds2025-07-01 11:46:28,938 - [DEBUG] - robotcode.robot.diagnostics.namespace.Namespace - Start loading imports for c:\Users\...2025-07-01 11:46:28,938 - [DEBUG] - robotcode.robot.diagnostics.imports_manager.ImportsManager - Start getting namespace and libdoc for ../../Keywords/Main.robot2025-07-01 11:46:28,938 - [DEBUG] - robotcode.robot.diagnostics.imports_manager.ImportsManager - Start getting resource entry ../../Keywords/Main.robot2025-07-01 11:46:28,939 - [DEBUG] - robotcode.robot.diagnostics.imports_manager.ImportsManager - End getting resource entry ../../Keywords/Main.robot took 0.0000 seconds2025-07-01 11:46:28,939 - [DEBUG] - robotcode.robot.diagnostics.imports_manager.ImportsManager - Start getting namespace ../../Keywords/Main.robot2025-07-01 11:46:28,939 - [DEBUG] - robotcode.robot.diagnostics.imports_manager.ImportsManager - End getting namespace ../../Keywords/Main.robot took 0.0000 seconds2025-07-01 11:46:28,939 - [DEBUG] - robotcode.robot.diagnostics.imports_manager.ImportsManager - Start getting libdoc ../../Keywords/Main.robot2025-07-01 11:46:28,939 - [DEBUG] - robotcode.robot.diagnostics.imports_manager.ImportsManager - End getting libdoc ../../Keywords/Main.robot took 0.0000 seconds2025-07-01 11:46:28,939 - [DEBUG] - robotcode.robot.diagnostics.imports_manager.ImportsManager - End getting namespace and libdoc for ../../Keywords/Main.robot took 0.0000 seconds2025-07-01 11:46:28,940 - [DEBUG] - robotcode.robot.diagnostics.namespace.Namespace - Start loading imports for c:\Users\...2025-07-01 11:46:28,940 - [DEBUG] - robotcode.robot.diagnostics.imports_manager.ImportsManager - Start loading library qnaplib.errinj.main.ErrorInjection()2025-07-01 11:46:28,941 - [DEBUG] - robotcode.robot.diagnostics.imports_manager.ImportsManager - End loading library qnaplib.errinj.main.ErrorInjection() took 0.0000 seconds2025-07-01 11:46:28,941 - [DEBUG] - robotcode.robot.diagnostics.imports_manager.ImportsManager - Start loading library tool.robotdtc.DynamicTestCases()2025-07-01 11:46:28,941 - [DEBUG] - robotcode.robot.diagnostics.imports_manager.ImportsManager - End loading library tool.robotdtc.DynamicTestCases() took 0.0000 seconds2025-07-01 11:46:28,941 - [DEBUG] - robotcode.robot.diagnostics.imports_manager.ImportsManager - Start loading library String()2025-07-01 11:46:28,942 - [DEBUG] - robotcode.robot.diagnostics.imports_manager.ImportsManager - End loading library String() took 0.0000 seconds...
@d-biehl
Comment options

When do you configure your logger?

I believe these messages end up in your log when the RobotCode Language Server tries to analyze your library. That should really only happen when the Language Server is initialized. If you start a test without the IDE, there shouldn’t be any log messages from the Language Server.

That would mean you’re setting up your log configuration/initialization already in the constructor or during the initialization of your library. The library initializer, i.e. your library’s__init__, is also called when RobotCode analyzes the library. Here you need to be careful to distinguish between the code needed for analyzing the library and the code that runs only at runtime. If the library is only being analyzed, you don’t need to initialize the logger. Take a look here in the Robot Framework documentation:detecting-is-robot-framework-running

@Massukio
Comment options

I’ll need to find my own solution for this, since Robot Framework isn’t the only entry point — my project also supports running scripts purely with Python.

Back to the original question — is there an option or setting to disable debug logging?

@d-biehl
Comment options

Back to the original question — is there an option or setting to disable debug logging?

No. There is no switch or anything to disable logging; there’s only a switch to enable it. And enabling logging is just setting the basic logging config level. Still, I’m curious how you managed to get RobotCode messages appearing for you when you’re not using RobotCode in your code.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Category
Q&A
Labels
None yet
2 participants
@Massukio@d-biehl
[8]ページ先頭
©2009-2025 Movatter.jp