Skip to content

Persistent Enterprise server connection warnings/errors over restart when offline #6913

Description

@ElykDeer

The following warnings/errors show up every time I open Binary Ninja Ultimate. I have an enterprise server configured in my settings, but it's behind a VPN, and I don't always want to be connected to it.

[Default] Attempt 1 to GET [url] failed, trying again in 1000ms
[Default] Attempt 2 to GET [url] failed, trying again in 2000ms
[Default] Attempt 3 to GET [url] failed, trying again in 4000ms
[Default] Error loading remote metadata: error sending request for url ([url]): error trying to connect: dns error: failed to lookup address information: nodename nor servname provided, or not known
[Default] 0   libbinaryninjacore.1.dylib          0x00000001184e89f0 libbinaryninjacore.1.dylib + 248304
[Default] 1   libbinaryninjacore.1.dylib          0x00000001188ddce8 BNRemoteProjectCanUserAdmin + 27364
[Default] 2   libbinaryninjacore.1.dylib          0x00000001188ebfd4 BNRemoteLoadMetadata + 24
[Default] 3   binaryninja                         0x000000010271cbf8 UIPluginABIVersion + 1627880
[Default] 4   binaryninja                         0x00000001025741ac binaryninja + 115116
[Default] 5   binaryninja                         0x0000000102574034 binaryninja + 114740
[Default] 6   binaryninja                         0x0000000102573f10 binaryninja + 114448
[Default] 7   QtCore                              0x0000000106b91884 _ZN17QThreadPoolThread3runEv + 252
[Default] 8   QtCore                              0x0000000106b89ee0 _ZN14QThreadPrivate5startEPv + 360
[Default] 9   libsystem_pthread.dylib             0x0000000198fc6c0c _pthread_start + 136
[Default] 10  libsystem_pthread.dylib             0x0000000198fc1b80 thread_start + 8
[Default] Could not connect to Remote: Failed to load metadata

I feel the large, persistent "Connection Failed" icon is sufficient notification, and doesn't clutter (and move) my log when I'm trying to look at other actionable log items that are relevant to me; Either debugging startup issues, trying to see that a plugin has been registered, or seeing the output of a plugin as I Restart and reopen files and then re-run my script; my current workaround is to actually just wait for it to stop complaining, clear the log, then run my plugin actions....it's a short delay, but very frustrating.

Image

Additionally, the traceback is not helpful for our users. Additionally additionally, these should probably not be in the default logger.

My preferred solution: make these all debug logs.

A solution I'll accept: add a setting that disables these logs or makes them debug logs.

A solution I won't accept: any of these continuing to be info, warn, error, or alert logs in all cases when I have an Enterprise server configured.

Another solution I won't accept: having to remember/write down my Enterprise server URL and dynamically remove/add it when I want to use the server.

There are some other solutions I'd accept that (I suspect) would be higher effort:

  • Being able to disable enterprise servers through a boolean setting (though again, less ideal to change a setting whenever I want to use the server)
  • Adding these logs to an [Enterprise] (or similar) logger, and being able to specify a persistent logger blacklist.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Component: UIIssue needs changes to the user interfaceEffort: TrivialIssues require < 1 day of workState: IntendedIssue is actually intended behavior

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions