trac-hacks / trac-github Goto Github PK

The /github handler doesn't appear to be working in my install.

http://mydomain.com/cgi-bin/trac.fcgi/github

This is the same response whether it's GET or POST.

It requires a deploy key.

Requested in #10.

Hi,

would it be possible to hide the email address from the ticket updates or replace it with a generic?
Even better would be matching them to our Trac users, but we're not using github auth.

Could not find anything documented.

Mentioned in #97, I'll document the steps for testing the plugin in a local development environment against the GitHub OAuth API. I used ngrok.

Related: steps for setting up a webhook were adapted to the new GitHub page layout in 14f0ae0.

@embray has raised the point that use of tracext without declaring a namespace package can lead to collisions (discussed here). I may have screwed up the implementation in 5c15d88 and 7275086.

if two packages are installing the file tracext/__init__.py the second one to be installed will override the first one. Being that tracext is a namespace package it should either have no __init__.py at all (the new Python 3 mechanism) or if there is an __init__.py it should have that boilerplate for extending the package's __path__.

Here I've installed TracMercurial alongside trac-github:

$ python setup.py bdist_wheel
[...]
$ pip install dist/trac_github-2.4.dev0-py2.py3-none-any.whl
[...]
$ find pve/lib/python2.7/site-packages/tracext/ -name "*.py"
pve/lib/python2.7/site-packages/tracext/__init__.py
pve/lib/python2.7/site-packages/tracext/hg/hooks.py
pve/lib/python2.7/site-packages/tracext/hg/backend.py
pve/lib/python2.7/site-packages/tracext/hg/__init__.py
pve/lib/python2.7/site-packages/tracext/github.py

I don't understand this well enough, but I think we want the github code in pve/lib/python2.7/site-packages/tracext/github.

The changes I'll propose will yield:

$find pve/lib/python2.7/site-packages/tracext/ -name "*.py"
pve/lib/python2.7/site-packages/tracext/github/__init__.py
pve/lib/python2.7/site-packages/tracext/hg/hooks.py
pve/lib/python2.7/site-packages/tracext/hg/backend.py
pve/lib/python2.7/site-packages/tracext/hg/__init__.py

I was seeing a lot of sync failure that I first assumed were just associated with #111, but after syncing failed a half dozen consecutive times I looked into it.

www-data@trac:~$ git --git-dir bugs.jqueryui.com/private/repositories/jquery-ui.git/ remote update --prune
Fetching origin
fatal: Unable to create '/var/www/bugs.jqueryui.com/private/repositories/jquery-ui.git/refs/pull/1755/merge.lock': Permission denied
error: Could not fetch origin

I suspect what happened is that I fixed a sync failure as root rather thanwww-data, which resulted in some git internal files having incorrect permissions.

It would be useful if we could detect and log any failures when git.remote('update', '--prune') is called. I didn't see any hints of the failure in the logs, just the downstream error message:

2017-03-03 17:42:33,075 Trac[github] ERROR: Payload contains unknown commit 032ddc3349f625e0840aa8e266b5d8ebee994853

Logout button doesn't work due to changes in [12379]. Logout requires a POST request.

Me again... finally trying to get my trac/git setup into production.

For the time being, I'll be using GitHub.com for source control, but Trac will be within my firewall, so GitHub won't be able to use a web hook to tell Trac about commits.

Is there some way for trac-github to just poll the repositories on an interval? Or if I made a script to do that myself, would the result be the same as having a webhook?

I tried to install trac-github as an egg (which is at least one of recommended ways to do it), but every time I got this error:

2014-11-28 10:50:06,318 Trac[loader] DEBUG: Loading github from /home/ubuntu/trac-plugins/trac-github
2014-11-28 10:50:06,320 Trac[loader] ERROR: Skipping "github = tracext.github":
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/trac/loader.py", line 68, in _load_eggs
    entry.load(require=True)
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2088, in load
    entry = __import__(self.module_name, globals(),globals(), ['__name__'])
ImportError: No module named github

Installing it with easy_install works fine, but I don't feel comfortable with installing Python packages not using OS package manager when I could keep them in certain place, and that makes hacking trac-github much messier (than with setup.py develop -mxd).

Is there some way to let our existing trac accounts keep working and add github auth as well? I'm not sure of how the internals work so I might be off base, but would some sort of integration with accountmanager plugin work?

I was also wondering if the HTTPS is really a hard requirement for github login. I'm serving a Discourse instance over HTTP and github login works fine there.

I've only just barely started work on this, but thought I'd drop a note in case anyone was interested in helping out with it or has some early feedback, ideas, suggestions, or recommendations...

I'm already using this plugin to keep git mirrors on Trac in sync with our authoritative repos on GitHub, but have found the lack of any Trac plugins with the ability to sync GitHub pull requests over to Trac, or sync activity on Trac back over to the appropriate GitHub pull requests to be painful. I'm sure others like us find GitHub issues severely lacking where Trac excels, or have just been using Trac issues for so long that it wouldn't be cost effective to switch have also wished for this kind of functionality. Everyone wants an official repository on GitHub for visibility and collaboration, but finds it annoying that pull requests can't be disabled when you still want patches submitted to Trac.

I've decided to extend this plugin with the ability to sync issue activity between Trac and GitHub. At least initially, I'm aiming mostly just for creating new Trac tickets for every new pull request, and automatically attaching patches generated from those pull requests to them, along with any updates to those pull requests. That's my primary priority.

After that, I'm planning to look into syncing ticket updates to those issues back to their original GitHub pull requests (which will likely require a GitHub account to post on behalf of, involving API keys), so developers only need to update the ticket on Trac, and the original contributor will still be notified on GitHub, and can still leave comments and updates there.

Others might be interested in turning on GitHub issues, and also syncing new Trac tickets over to GitHub if the plan is to eventually just switch to GitHub issues, but I'm not planning on doing that at all myself for now. Also, that workflow can mostly be avoided by just removing the TICKET_CREATE permission from Trac users, and directing them to GitHub.

I'll be working on this within my issue-sync branch here:
master...tierra:issue-sync

Hi

trac-github is working well for me, but I was wondering whether the possibility of having selective behaviour for branches had been considered?

For example, I would like references to tickets to be possible on branches, but fixes/closes to only apply to master. This way tickets won't be closed until pull requests are complete.

https://github.com/aaugustin/trac-github/blob/master/tracext/github.py#L121

Is git update an aliased command? With the default msysgit install that command seems to be missing. Changing it to git fetch works though.

Thank you for the plugin.

See this downstream ticket I opened on the MacPorts Trac: https://trac.macports.org/ticket/68357
Basically, when a project has a presence on both Trac and GitHub, sometimes people will miss things on one place because they only check their notifications on one of the two places. Syncing notifications would help keep people up-to-date about things they may have missed on the other end of the bridge.
(N.B. I'm not sure if this is actually possible; if it isn't, feel free to close)

On navigating to a page which the user doesn't have permission to view the following message is displayed: You are currently not logged in. You may want to do so now. The phrase do so is a link to /login. When using trac-github plugin the login path is /github/login. It can be seen here that clicking on do so links to an error page No handler matched request to /login.

Was the intent of using /github/login as the path to allow trac-github to function side-by-side with Trac's login module?

Hello,

First of all thank you for this great plugin. We've been using it for a few weeks on http://dev.piwik.org and it is great!

However, today we have a problem that the plugin seems disabled, and we can't find a way to enable it again. There has been no change in the files. Do you know, how or why the plugin could stop working and appear disabled, very suddenly ? It was working 24 hours ago: http://dev.piwik.org/trac/ticket/3668#comment:2

We have tried reinstalling via;
$ cd /path/www/dev.piwik.org/trac/plugins
$ pip install -e git://github.com/aaugustin/trac-github.git#egg=TracGitHub-dev

To test I use:
$ curl --data "test=1" http://dev.piwik.org/trac/github
But that returns the "Error handler not found".

Also our timeline: http://dev.piwik.org/trac/timeline is not showing git commits anymore.

We compared the whole filesystem to backup and nothing changed in the last 24 hours.

Thank you very much for your help!

Matt

It would be nice if trac-github could monitor pull requests and post a comment with a link to the pull request in tickets that are mentioned in pull requests.

Sometimes we get users generating spam with their GitHub accounts. I guess there's probably a way to report these users, but it would be nice if we could just ban users by username. So far we haven't had a problem since these users go away after making a few comments and we are running TracSpamFilter so some stuff gets trapped. It would probably be simple enough though to have a list of users on a wiki page, and to reject login by users matching one of the usernames.

I'd like to create a release for version 2.3. It looks like the change log needs a few updates. I'll go through the commit history, but for anyone that's made changes, if you don't mind adding to the change log that would help.

Hi,

I met #9 problem and it is occurred by Python version.
When I run it on python 2.6, I got same error.

Is Python 2.6 supported?

The README states "This plugin is included in Trac >= 1.0 — you only have to enable it in trac.ini" I don't believe this is true. There are people on the trac mailing list who swear it's not true. If it's not true, it would be helpful to remove this, and add some guidance for installing this plugin in Trac >= 1.0.

I volunteer to write this missing documentation, either for configuring the plugin if it's already included in 1.0, or for installing and configuring if it's not. I'd appreciate any tips to help me figure it out. Thanks!

You mention in the readme this setting:

[github]
repository = <user>/<project>

I have multiple github repos in the same TRAC env. How should I set them in this config?
As list?

I've been noticing tracebacks like this in the logs, at least twice in the past week. I'm unsure of how to reproduce the issue, but maybe we can trap and display a nicer error to the user. Most likely, the error results in the standard Trac error page with a traceback.

2016-02-15 01:33:21,870 Trac[main] ERROR: Internal Server Error: <RequestWithSession "GET '/github/oauth?code=1042415f1e75a2ef5c07&state=o5EZcGeiCqVJ5zZqShpAuWIchPdUmn'">, referrer 'https://bugs.jqueryui.com/ticket/10458'
Traceback (most recent call last):
  File "/var/www/bugs.jqueryui.com/private/pve/local/lib/python2.7/site-packages/trac/web/main.py", line 554, in _dispatch_request
    dispatcher.dispatch(req)
  File "/var/www/bugs.jqueryui.com/private/pve/local/lib/python2.7/site-packages/trac/web/main.py", line 247, in dispatch
    resp = chosen_handler.process_request(req)
  File "/var/www/bugs.jqueryui.com/private/pve/local/lib/python2.7/site-packages/tracext/github.py", line 56, in process_request
    self._do_oauth(req)
  File "/var/www/bugs.jqueryui.com/private/pve/local/lib/python2.7/site-packages/tracext/github.py", line 77, in _do_oauth
    client_secret=client_secret)
  File "/var/www/bugs.jqueryui.com/private/pve/local/lib/python2.7/site-packages/requests_oauthlib/oauth2_session.py", line 203, in fetch_token
    self._client.parse_request_body_response(r.text, scope=self.scope)
  File "/var/www/bugs.jqueryui.com/private/pve/local/lib/python2.7/site-packages/oauthlib/oauth2/rfc6749/clients/base.py", line 409, in parse_request_body_response
    self.token = parse_token_response(body, scope=scope)
  File "/var/www/bugs.jqueryui.com/private/pve/local/lib/python2.7/site-packages/oauthlib/oauth2/rfc6749/parameters.py", line 376, in parse_token_response
    validate_token_parameters(params)
  File "/var/www/bugs.jqueryui.com/private/pve/local/lib/python2.7/site-packages/oauthlib/oauth2/rfc6749/parameters.py", line 386, in validate_token_parameters
    raise MissingTokenError(description="Missing access token parameter.")
MissingTokenError: (missing_token) Missing access token parameter.

After successfully logging in via Github Oauth using my company's SSO provider and being redirected back to the Trac instance, clicking the "Logout" button returns the error: Missing or invalid form token. Do you have cookies enabled?

Relevant portion of the logs:

2023-02-12 21:45:30,231 Trac[main] DEBUG: Dispatching <RequestWithSession "POST '/github/logout'">
2023-02-12 21:45:30,231 Trac[main] DEBUG: Chosen handler is <Component tracext.github.GitHubLoginModule>
2023-02-12 21:45:30,232 Trac[main] WARNING: [100.97.53.206] HTTPBadRequest: 400 Bad Request (Missing or invalid form token. Do you have cookies enabled?), <RequestWithSession "POST '/github/logout'">, referrer 'https://<my_instance>/trac/admin/general/logging'

Running Trac 1.4.3 and trac-github 2.3.

Discussed near the end of #8, I continue to see cases in which a changeset does not sync from GitHub and therefore the post-commit hook is not triggered. Running a git fetch and trac-admin $env changeset added for the changeset always triggers the update of the relevant ticket.

The following is always seen in the logs when the issue occurs:

2016-07-12 13:07:06,356 Trac[github] ERROR: Payload contains unknown commit 55cd9488ccd897bb9b75450852c100d13cf0df02

I've considered that it might work to implement a simple retry of git remote update --prune.

The plugin will only use a user's name and email from GitHub if they are public, as previously described. In the case that [notification] always_notify_updater is true, users with a public email in their GitHub profile will receive notifications, whereas users without a public email in their GitHub profile will not unless they have explicitly set their email address in their Preferences. For the jQuery Trac sites we'd like to make the behavior more consistent, or at least more explicit. Therefore, I've considered the following and would like to get some feedback on whether you think one or both is a good idea:

• Add a notice on login for a user that doesn't have a public email address in their GitHub profile. The notice would be something like: You will not receive email notifications unless you set your email address in preferences [x] (with preferences being a link to /prefs and [x] being a dismiss button). The notice could persist on every page until the name and email are set, or until the notice is explicitly dismissed (AccountManagerPlugin has similar behavior for verification of emailed registration tokens).
• Allow users with a private name and email in their GitHub profile to explicitly opt-in to having their name and email set in Trac preference data (is it even possible?).

When using cached_repository:

2013-02-03 01:32:28,259 Trac[main] ERROR: Internal Server Error:
Traceback (most recent call last):
  File "/usr/local/lib/python2.6/dist-packages/Trac-1.0.1-py2.6.egg/trac/web/main.py", line 497, in _dispatch_request
    dispatcher.dispatch(req)
  File "/usr/local/lib/python2.6/dist-packages/Trac-1.0.1-py2.6.egg/trac/web/main.py", line 214, in dispatch
    resp = chosen_handler.process_request(req)
  File "/home/trac/src/tracgithub/tracext/github.py", line 116, in process_request
    repos.git.repo.remote('update', '--prune')
AttributeError: 'GitCachedRepository' object has no attribute 'git'

Works fine with cache off

With the GitHubBrowser component enabled, Trac is showing this error:

Trac detected an internal error:
error: redefinition of group name u'it_changeset' as group 29; was group 22

A quick Google shows a similar problem with another plugin.
http://trac.edgewall.org/ticket/9652

If I disable GitHubBrowser, the error goes away.

Seems like whenever somebody creates a pull request on github, it shows up in trac timeline as a commit

In the post-commit-hook section of the documentation, it looks like there needs to be an initial sync of the cache:

trac-admin $env repository resync "<project>"

or

trac-admin $env repository resync "(default)"

Does that seem correct?

Also, author names that Trac caches look like Full Name <[email protected]>. In order for the CommitTicketUpdater to function, I suspect that reverse mapping from email address to Trac user id needs to be enabled. It is disabled by default.

[git] trac_user_rlookup = enabled

I will edit the documentation if you agree with the changes.

Hey everybody,

I think github has changed their PostCommitHooks (no clue when) does this still work? And if it does, how does it need to be configured, as the readme is talking about settings we don't get offered.
https://github.com/trac-hacks/trac-github#post-commit-hook

Thx

Under some circumstances, GitHub will repeatedly include the same commit in the webhook payload. This results in duplicate notifications in Trac. For instance, I've seen some tickets end up with 10 or more identical comments.

I think this might be trigged by merging a branch A into a branch B, then B back in A, then A in B, etc.

GitHub's docs say that each payload contains "the push and the commits it contained". It seems to me that a commit with a given hash can never be included in more than one push. But the same hash obviously shows up in several payloads.

As far as I can tell, this is a case of garbage in, garbage out. It's hard to qualify this as a bug in trac-github.

However, if someone understands how GitHub builds its webhook payloads, I'm all ears, and I'll try to work around this problem in trac-github.

I am running Trac version 1.0.2 and I installed this plugin per the instructions in the REAMDME with the exclusion of putting repository information in the [trac] area, I have it in the [repositories] area.

With that being said, here are those 2 sections:

[repositories]
stormbot7.alias = sb7
stormbot7.description = Stormbot v7 Git repository
stormbot7.dir = /home/bhnet/bhtrac/Stormbot7.git
stormbot7.type = git
stormbot7.url = https://github.com/StormbotTCL/Stormbot7

[trac]
auto_preview_timeout = 2.0
auto_reload = false
base_url = trac.stormbot.org
database = database information
debug_sql = false
default_date_format = iso8601
default_language = en_US
default_timezone = America/New_York
genshi_cache_size = 128
mainnav = wiki, blog, timeline, browser, tickets, newticket, search
repository_type = git
secure_cookies = false
use_base_url_for_redirect = false

Here are my [git] and [github] settings of my configuration as well.

[git]
git_bin = /usr/bin/git
post_request_ips = 204.232.175.64/27List of IPs (in CIDR format) POST request is accepted from.192.30.252.0/22
shortrev_len = 7
wiki_shortrev_len = 40
wikishortrev_len = 40

[github]
repository = StormbotTCL/Stormbot7

http://trac.stormbot.org/github does show the endpoint

Setup of the webhook is pointing to that address with the content type of application/json. The initial test passed but any updates to the repo come back with a 500 error with "AttributeError: 'NoneType' object has no attribute 'repos' reported in the GitHub log for the webhook.

If there is any more information I need to provide, I will do so.

The trac-github plugin is using a deprecated GitHub API endpoint for /teams/ that will be removed on 2022-03-15. Right now on 2022-03-01, GitHub has some brownouts in effect to make users of the API aware of the deprecation. I see the following log message:

Trac[github] ERROR: Error communicating with GitHub API at https://api.github.com/teams/3156412/members: You are receiving this error due to a service brownout. Please see https://github.blog/changelog/2022-02-22-sunset-notice-deprecated-teams-api-endpoints/ for more information.

The easiest route seems to be to replace the /teams/ endpoint with /organizations/:org_id/team/:team_id. I have not yet checked whether they are fully compatible, though.

The package on PyPI is listed as 2.1.2. The master branch shows 2.1.1 in setup.py.

Hello,

I have been trying to install the trac-github plugin, but I keep running into the "No handler matched request to /github" when trying to access the /github -page on our trac.

I am using Trac 1.0.1. The trac is installed on a virtual machine, and it is being accessed via HTTPS at a non-standard port (the virtual machine has a redirect from 443 to our chosen port). I am trying to integrate Trac with a private github repo.

I have completed the steps laid out in the Setup section of the readme file. I have set up a mirror of our github repository on the same machine as Trac. I have also set up SSH key access for the www-data user to this repository. I have verified that the access works.

Here is the relevant part of my trac.ini
https://gist.github.com/jlehikoi/18c1a4c2e0762569d9bb

The gist also includes trac.log after restarting apache and sending the test payload from Github. The only warning in the log file is the 404 error on line 65. When I point my browser to /github, I get the "No handler matched request to /github" error.

Could this problem be caused by the fact that we use Trac over HTTPS and/or not in port 443? That's the only thing that I can think of, I'm pretty sure I've done the setup otherwise correctly.

Maybe it could be nice to add a example of how to restrict the access (as mentioned in the readme)

<Location "/github">
  Order deny,allow
  Deny from all
  Allow from 127.0.0.1
  Allow from 207.97.227.253
  Allow from 50.57.128.197
  Allow from 108.171.174.178
  Allow from 50.57.231.61
</Location>

127.0.0.1 can be used for debugging purposes

Hi,

I'm an administrator for trac-hacks.org. We've created an organization on GitHub and are inviting authors of trac-hacks plugins to join the organization. Your repository could be transferred into the organization as described in the GitHub docs. You'd retain full control over the repository, but the hope is that it will be easier for users on GitHub to find trac-hacks plugins, such as yours, by viewing the trac-hacks organization.

In the future, if you choose to no longer maintain the plugin, the organization would be able to provide commit access to new developers. This would only be done with your permission, as has been the policy for plugins hosted on trac-hacks.org. If you've already decided to no longer maintain the plugin, we would particularly appreciate you transferring the plugin to the trac-hacks organization so that we can help find new maintainers for it.

Finally, creating the trac-hacks organization is a work in progress. I appreciate if you have any suggestions on how to best support the community of trac plugin developers on GitHub. More information can be found in the blog post.

Kind regards,
Ryan

(Apologies if I open a ticket against two of your plugins. I'm doing a manual search of GitHub to find Trac plugins and invite plugin authors; it's sometimes difficult to keep everything straight).

It's my understanding that trac-github replaces the /browser portion of the Trac system with a redirect to the GitHub repository browser.

It is possible to configure Trac with multiple repositories. One could have a GitHub repository, and also a Subversion repository.

Is it possible to configure trac-github so that links to the GitHub repository are redirected to the GitHub repository browser, while links to the Subversion repository continue to be served by the Trac browser? If so, how? If not, please make that possible.

I've been seeing the following error when attempting to authenticate through GitHub.

2015-08-04 21:38:45,841 Trac[main] ERROR: Internal Server Error: 
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/trac/web/main.py", line 550, in _dispatch_request
    dispatcher.dispatch(req)
  File "/usr/local/lib/python2.7/dist-packages/trac/web/main.py", line 243, in dispatch
    resp = chosen_handler.process_request(req)
  File "build/bdist.linux-x86_64/egg/tracext/github.py", line 45, in process_request
    self._do_oauth(req)
  File "build/bdist.linux-x86_64/egg/tracext/github.py", line 66, in _do_oauth
    client_secret=client_secret)
  File "/usr/local/lib/python2.7/dist-packages/requests_oauthlib/oauth2_session.py", line 203, in fetch_token
    self._client.parse_request_body_response(r.text, scope=self.scope)
  File "/usr/local/lib/python2.7/dist-packages/oauthlib/oauth2/rfc6749/clients/base.py", line 409, in parse_request_body_response
    self.token = parse_token_response(body, scope=scope)
  File "/usr/local/lib/python2.7/dist-packages/oauthlib/oauth2/rfc6749/parameters.py", line 376, in parse_token_response
    validate_token_parameters(params)
  File "/usr/local/lib/python2.7/dist-packages/oauthlib/oauth2/rfc6749/parameters.py", line 406, in validate_token_parameters
    raise w
Warning: Scope has changed from "" to "".

The following patch seems to have fixed the issue:

diff --git a/tracext/github.py b/tracext/github.py
index 6b2bcfd..835d68c 100644
--- a/tracext/github.py
+++ b/tracext/github.py
@@ -79,7 +79,7 @@ class GitHubLoginModule(LoginModule):
         redirect_uri = req.abs_href.github('oauth')
         # Inner import to avoid a hard dependency on requests-oauthlib.
         from requests_oauthlib import OAuth2Session
-        return OAuth2Session(client_id, redirect_uri=redirect_uri, scope=[])
+        return OAuth2Session(client_id, redirect_uri=redirect_uri, scope=['user:email'])

     def _client_config(self, key):
         assert key in ('id', 'secret')

I'm interested to hear what you think about the change. Thanks.

Just wanted to mention that it is not needed to create a ssh key for each private repo.

You can also use a .netrc file in the apache users home dir, by setting a generated token as the password. This way, you can even define logins for github.com or any other GitHub Enterprise installation:

machine github.com
login myghcomuser
password <ghcomtoken>

machine ghe.sample.local
login mygheuser
password <ghetoken>

Of course the permission of the .netrc file must be as tight as possible.

See https://github.com/trac-hacks/trac-github/blob/master/tracext/github.py#L111 -- it doesn't call read, it tries to strip it :)

The documentation says the endpoint URL must be /github. I've been trying to help a user on the mailing list with configuration issues, and found the following in his logs:

2017-02-01 14:17:51,334 Trac[PyGIT] DEBUG: PyGIT.Storage instance for '/var/lib/git/efistrac/efistrac.git' is constructed
2017-02-01 14:17:51,334 Trac[PyGIT] DEBUG: requested weak PyGIT.Storage instance for '/var/lib/git/efistrac/efistrac.git'
2017-02-01 14:17:51,334 Trac[git_fs] DEBUG: disabled CachedRepository for '/var/lib/git/efistrac/efistrac.git'
2017-02-01 14:17:55,944 Trac[main] DEBUG: Dispatching <RequestWithSession "GET '/github'">
2017-02-01 14:17:55,945 Trac[github] WARNING: No such repository (/)

It looks like the endpoint must include the repository name for a non-default repository. I'm going to do some testing, and will modify the documentation as needed.