visual studio code - Flutter - how to filter debug console in vscode

Question

For a few days, and without changing anything, at least deliberately, in DEBUG CONSOLE in VSCODE I get messages like:

W/.arae_blueprin(14366): Accessing hidden method Lsun/misc/Unsafe;->getInt(Ljava/lang/Object;J)I (greylist, linking, allowed)
W/.arae_blueprin(14366): Accessing hidden method Lsun/misc/Unsafe;->compareAndSwapObject(Ljava/lang/Object;JLjava/lang/Object;Ljava/lang/Object;)Z (greylist, linking, allowed)
W/.arae_blueprin(14366): Accessing hidden method Lsun/misc/Unsafe;->compareAndSwapObject(Ljava/lang/Object;JLjava/lang/Object;Ljava/lang/Object;)Z (greylist, linking, allowed)
W/.arae_blueprin(14366): Accessing hidden method Lsun/misc/Unsafe;->putObject(Ljava/lang/Object;JLjava/lang/Object;)V (greylist, linking, allowed)
D/EGL_emulation(14366): eglMakeCurrent: 0xe1641400: ver 2 0 (tinfo 0xd5f83710)
D/EGL_emulation(14366): eglMakeCurrent: 0xc1f7c2e0: ver 2 0 (tinfo 0xbd495c10)
D/eglCodecCommon(14366): setVertexArrayObject: set vao to 6 (6) 0 0
W/.arae_blueprin(14366): Accessing hidden method Lsun/misc/Unsafe;->getInt(Ljava/lang/Object;J)I (greylist, linking, allowed)
I/DynamiteModule(14366): Considering local module com.google.android.gms.ads.dynamite:0 and remote module com.google.android.gms.ads.dynamite:21200
I/DynamiteModule(14366): Selected remote version of com.google.android.gms.ads.dynamite, version >= 21200
D/eglCodecCommon(14366): setVertexArrayObject: set vao to 4 (4) 0 0
D/eglCodecCommon(14366): setVertexArrayObject: set vao to 0 (0) 1 2
D/eglCodecCommon(14366): setVertexArrayObject: set vao to 0 (0) 1 2
D/eglCodecCommon(14366): setVertexArrayObject: set vao to 4 (4) 1 30

These messages make it difficult for me to read the logs that I send by console.

How can I filter them so they don't appear, or at least filter my own logs?. Thanks.

Answer 1

According to this issue it looks like it is not currently possible to filter the debug console in Visual Studio Code, however you could use the filter text field in the logging tab of the Dart DevTools in order to filter the logs that are sent to the console. I appreciate that this means that you would need to have the Dart DevTools open in addition to Visual Studio Code, however this would be a useable workaround until such a time as the ability to filter the debug console is implemented in Visual Studio Code.