-
Notifications
You must be signed in to change notification settings - Fork 521
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
Cannot use personal access token to connect to GitLab #1968
Comments
Same problem here. It returns 401 |
Same issue as well. Is there a work around known for this? |
Logging in returns 400 for me. Extension version: 1.8.1 |
I get error code 400 too, using gitlab username or email with gitlab access token Extension version: v1.9.0 |
Marking this for re-triage, and making this a bug instead of enhancement. OAuth is no longer realistically an option since it now requires a client app ID and secret, so personal or project access tokens are basically the only option. Using GitLab is blocked until we implement this. |
This fix is now released in Docker extension version 1.10.0. |
Issue Type: Bug
Extension version: 1.1.0
VS Code version: Code 1.45.0 (d69a79b73808559a91206d73d7717ff5f798f23c, 2020-05-07T16:10:24.511Z)
OS version: Linux x64 5.4.0-29-generic snap
System Info
flash_3d: disabled_software
flash_stage3d: disabled_software
flash_stage3d_baseline: disabled_software
gpu_compositing: disabled_software
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: disabled_off
rasterization: disabled_software
skia_renderer: disabled_off_ok
video_decode: disabled_software
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off_ok
webgl: unavailable_software
webgl2: unavailable_software
The text was updated successfully, but these errors were encountered: