Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

stuck on "lets go" after adding a project if there is no network access (firewall) #2640

Open
c33s opened this issue Feb 13, 2024 · 3 comments
Labels
bug Something isn't working UX/UI Focusing on user satisfaction, usability, and overall experience

Comments

@c33s
Copy link

c33s commented Feb 13, 2024

in the firewall logs i see repeated accesses to gravatar. i would vote for allowing gitbutler to work without network access

image

@KroniK907
Copy link
Contributor

I would agree that any network required aspect to the program should fail gracefully and still allow basic offline functionality.

@mtsgrd mtsgrd added the bug Something isn't working label Feb 14, 2024
@omitter
Copy link

omitter commented Feb 19, 2024

I have blocked all gravatar connections on my pc. With this this setting, Gitbutler loads forever with

ERROR get_base_branch_data: gitbutler-app/src/assets.rs:121: failed to proxy gravatar url gravatar_url=https://www.gravatar.com/avatar/xxx?s=100&r=g&d=retro error=error sending request for url (https://www.gravatar.com/avatar/xxx?s=100&r=g&d=retro): error trying to connect: tcp connect error: connection timeout (os error 110)

It would be really nice if Gitbutler wouldn't have such hard dependencies on a rather unimportant feature. Also for privacy reasons, it's grossly negligent to send all private email addresses to an external service without even asking.

@pinguo-lixin
Copy link

I have blocked all gravatar connections on my pc. With this this setting, Gitbutler loads forever with

ERROR get_base_branch_data: gitbutler-app/src/assets.rs:121: failed to proxy gravatar url gravatar_url=https://www.gravatar.com/avatar/xxx?s=100&r=g&d=retro error=error sending request for url (https://www.gravatar.com/avatar/xxx?s=100&r=g&d=retro): error trying to connect: tcp connect error: connection timeout (os error 110)

It would be really nice if Gitbutler wouldn't have such hard dependencies on a rather unimportant feature. Also for privacy reasons, it's grossly negligent to send all private email addresses to an external service without even asking.

Same here. Especially as a developer in China!

2024-03-07T02:44:32.820964Z ERROR get_base_branch_data: gitbutler-app/src/assets.rs:121: failed to proxy gravatar url gravatar_url=https://www.gravatar.com/avatar/94d221f4c77115aef643d3bdb2697639?s=100&r=g&d=retro error=error sending request for url (https://www.gravatar.com/avatar/94d221f4c77115aef643d3bdb2697639?s=100&r=g&d=retro): error trying to connect: tcp connect error: Operation timed out (os error 60)

Caused by:
0: error trying to connect: tcp connect error: Operation timed out (os error 60)
1: tcp connect error: Operation timed out (os error 60)
2: Operation timed out (os error 60) project_id="7bbac76b-10e6-4412-97ff-9b58245bc4e0"
2024-03-07T02:45:48.423685Z ERROR get_base_branch_data: gitbutler-app/src/assets.rs:121: failed to proxy gravatar url gravatar_url=https://www.gravatar.com/avatar/94d221f4c77115aef643d3bdb2697639?s=100&r=g&d=retro error=error sending request for url (https://www.gravatar.com/avatar/94d221f4c77115aef643d3bdb2697639?s=100&r=g&d=retro): error trying to connect: tcp connect error: Operation timed out (os error 60)

Caused by:
0: error trying to connect: tcp connect error: Operation timed out (os error 60)
1: tcp connect error: Operation timed out (os error 60)
2: Operation timed out (os error 60) project_id="7bbac76b-10e6-4412-97ff-9b58245bc4e0"

@Byron Byron added the UX/UI Focusing on user satisfaction, usability, and overall experience label Apr 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working UX/UI Focusing on user satisfaction, usability, and overall experience
Projects
None yet
Development

No branches or pull requests

6 participants