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

[bug] Brutaldon cannot be connected to a GtS instance #113

Closed
tsmethurst opened this issue Jul 24, 2021 · 3 comments
Closed

[bug] Brutaldon cannot be connected to a GtS instance #113

tsmethurst opened this issue Jul 24, 2021 · 3 comments
Labels
bug Something isn't working enhancement New feature or request

Comments

@tsmethurst
Copy link
Contributor

Currently Brutaldon (https://brutaldon.org/login) gives a 500 server error when trying to log into gts.superseriousbusiness.org. We should investigate why this is and make sure Brutaldon can connect to GtS.

@tsmethurst tsmethurst added bug Something isn't working enhancement New feature or request labels Jul 24, 2021
@egon0
Copy link

egon0 commented Aug 10, 2021



Request Method: POST
Request URL: http://localhost:8002/login

Django Version: 3.2.6
Python Version: 3.9.0
Installed Applications:
['django.contrib.admin',
 'django.contrib.auth',
 'django.contrib.contenttypes',
 'django.contrib.sessions',
 'django.contrib.messages',
 'django.contrib.staticfiles',
 'widget_tweaks',
 'sanitizer',
 'django.contrib.humanize',
 'brutaldon']
Installed Middleware:
['django.middleware.security.SecurityMiddleware',
 'django.contrib.sessions.middleware.SessionMiddleware',
 'django.middleware.common.CommonMiddleware',
 'django.middleware.csrf.CsrfViewMiddleware',
 'django.contrib.auth.middleware.AuthenticationMiddleware',
 'django.contrib.messages.middleware.MessageMiddleware',
 'django.middleware.clickjacking.XFrameOptionsMiddleware',
 'brutaldon.middleware.timezone.TimezoneMiddleware']



Traceback (most recent call last):
  File "/root/.local/share/virtualenvs/app-4PlAip0Q/lib/python3.9/site-packages/django/core/handlers/exception.py", line 47, in inner
    response = get_response(request)
  File "/root/.local/share/virtualenvs/app-4PlAip0Q/lib/python3.9/site-packages/django/core/handlers/base.py", line 181, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/root/.local/share/virtualenvs/app-4PlAip0Q/lib/python3.9/site-packages/django/views/decorators/cache.py", line 44, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
  File "/app/brutaldon/views.py", line 442, in login
    client.version = mastodon.instance().get("version")
  File "/root/.local/share/virtualenvs/app-4PlAip0Q/lib/python3.9/site-packages/decorator.py", line 232, in fun
    return caller(func, *(extras + args), **kw)
  File "/root/.local/share/virtualenvs/app-4PlAip0Q/lib/python3.9/site-packages/mastodon/Mastodon.py", line 99, in wrapper
    raise MastodonVersionError("Version check failed (Need version " + version + ")")

Exception Type: MastodonVersionError at /login
Exception Value: Version check failed (Need version 1.1.0)

it's basically the mastodon lib that only accepts versions => 1.1.0 when pulling infos from /api/v1/instance

@tsmethurst tsmethurst added this to the 0.1.0 milestone Sep 3, 2021
@tsmethurst tsmethurst removed this from the 0.0.1 milestone Nov 16, 2021
@tsmethurst tsmethurst changed the title Brutaldon cannot be connected to a GtS instance [bug] Brutaldon cannot be connected to a GtS instance Dec 20, 2021
@tsmethurst tsmethurst added this to To Be Investigated in Client Compatibility Issues May 4, 2022
@daenney
Copy link
Member

daenney commented Jul 9, 2023

This has been fixed in Brutaldon: https://gitlab.com/brutaldon/brutaldon/-/merge_requests/11 (the branch is named fix/support-gts 😄). They updated their calls to the mastodon.py library to disable the version checking.

That commit went in 5 months ago but unfortunately they haven't tagged a new version. The last one is from 3 years ago. I've verified this works fine now if you use a Brutaldon built from main. At this point all we can do is wait for them to do a release. I think we can close this now.

@tsmethurst
Copy link
Contributor Author

Alright, thanks for investigating :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
Development

No branches or pull requests

3 participants