Skip to content

[Bug] Git sync and API calls timeouts - using Gitlab token #60

Description

@zeigerpuppy

The Git sync feature is very useful to synchronise with a git repository. However, there appear to be some bugs in the implementation (at least when working with Gitlab.

What's working:

  • initial sync
  • push changes
  • pull changes (to .md files)

Tests:

  • api container can access gitlab server and resolves it properly
  1. when reading a commit history, it looks like the API is not loading the commits properly:
  • Gateway Timeouts occur

  • console shows the following errors:

    XHR GET
    https://refmd.server.net.au/api/git/diff/commits/bb42ee3d894b8eaf5036519c2f7d6a5863801fee^/bb42ee3d894b8eaf5036519c2f7d6a5863801fee
    [HTTP/2 504  60013ms]
    

This almost looks like it is trying to query the refmd api server instead of the gitlab server, but maybe those requests are translated by the api container....

Image
  1. once a change has been made, a pull brings up "Resolve conflicts" even if no conflict is present
  • this does not appear to affect function, but is a bit confusing
Image
  1. git actions are slow
  • in general, the sync actions appear to take longer than expected (the Gitlab server in this case is co-located on the same hypervisor, so should be very fast)

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions