Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Git traffic and tokenless authentication charts empty after GHE upgrade

See original GitHub issue

Hello there,

We have hubble as service on a dedicated machine and we recently did GHE upgrade from v2.11 to v2.12.6 and after this hubble does not show the git traffic/ there is no data in git-download.tsv

fyi, there are no errors reported when we run update-stats.py.

In general do we need to do anything before or after we apply an update to GHE.

Regards Piyush

Issue Analytics

State:
Created 6 years ago
Comments:29 (16 by maintainers)

Top GitHub Comments

1reaction

pluehnecommented, Mar 21, 2018

Hi @talktopiyush! Thanks for reaching out about these two issues. We noticed the issues with the Git traffic charts as well, and they should be fixed by #138.

I’d like you to check out the latest commit in the master branch and to run the Hubble updater again. This should resolve the first part of the issue. (The context is that we made changes to the naming of the data series, and unfortunately, these weren’t reflected in the data files that the updater produces. Hence, the dashboard couldn’t find the data anymore and would show empty charts.)

Concerning the tokenless authentication chart, there was a change in GitHub’s log file format from 2.11 to 2.12 that broke our script for that chart’s data. I’m currently working on this and hope to have a patch out later today.

As a general suggestion, we recommend that you use the latest release (currently, 0.2.0) and not the master branch directly. Also, we’re trying to avoid issues on master as best as we could, but we can’t guarantee forward compatibility with new GitHub Enterprise versions unfortunately.

0reactions

pluehnecommented, Apr 16, 2018

@talktopiyush: Yep, I should have thought about this. In these cases, it’s necessary to remove the most recent Hubble commit, at least for testing 🙂.

I’m happy to help. Feel free to stay in touch with us should you have suggestions or other comments.

Top Results From Across the Web

Message "Support for password authentication was removed ...

From 2021-08-13, GitHub is no longer accepting account passwords when authenticating Git operations. You need to add a PAT (Personal Access ...

Deprecations by version - GitLab Docs

When we implemented this feature, we deprecated values in the GitLab Helm Chart configuration that were specific to GitLab Runner. These fields are...

Enabling access to a Git repository - IBM

For an empty project: Select to integrate the project with Git. · Select this token on the create project page. · After the...

7.14 Git Tools - Credential Storage

If you use the SSH transport for connecting to remotes, it's possible for you ... When saving credentials, Git will send the username...

octokit/rest.js

Note that authentication is not applied when retrieving request options from the ... If true pull requests are omitted from the response (empty...