package not auto-updated #200
Comments
|
is your token right in the hook config ? |
|
Yes, I compared them, and copied the one shown in packagist over again just Am 22.08.2012 18:16, schrieb Christophe Coevoet:
|
|
There have been a few reports of some packages not auto-updating even though everything looks good. I'm not sure if it's a GitHub API issue or what, but I haven't had time to look into it yet. |
|
+1 on this. The repo is http://packagist.org/packages/mheap/silex-mongo |
|
Just wanted to bump this ticket shortly, because I get messages from users very now and then, complaining that the packagist version is out of date (or, if they don't realize that, they'll open tickets about bug that have been fixed a long time ago). Are there any news on this or is there anything I can do to help debug? If it's impossible to fix, would it be an option to just delete the package from packagist and then reigster it again? |
|
Can someone with a failing repo give me admin access to it so I can try to debug it by triggering the hook when I have time to look into this? It only happens with a few repos (seemingly at random) and I can't figure out why. |
|
Added you to https://github.com/mheap/Silex-Mongo |
|
@mheap thanks, but can you give me admin access to it so I can press the "test hook" button instead of having to push random stuff to the repo to trigger the hook? |
|
As far as I can tell, the only way to give you admin access is to transfer the repo to you as it's not owned by an organisation. How do you want to proceed? I can transfer it to you, you can fork it, or we can jump on Skype/Jabber at some point and I can just hit test hook whilst you look at logs. |
|
Ah damn ok. Well let's do skype then (I'm seldaek there too) - probably won't have much time for this this week though, but add me and I'll ping you when I do. |
|
I'm experiencing the same thing when adding the package using the HTTP URL, i.e. https://github.com/WrittenGames/AuditBundle or https://github.com/WrittenGames/AuditBundle.git - but when I add it using the SSH URL, git@github.com:WrittenGames/AuditBundle.git, it works fine (i.e. it auto-updates). |
|
Just tried that on my package, but it doesn't seem to make a difference, Am 24.10.2012 11:28, schrieb Moritz Kraft:
|
|
Hmm. You're right, I've still got that in my account view as well. However, it's gone from the package view itself (reproducably, it's there when I use the HTTP URL but gone when I use the SSH one). |
|
@userfriendly that's just because ssh URLs aren't fully supported by packagist and aren't seen as github URLs. They kinda work but cause issues and you shouldn't use them unless you run a private packagist with private repos. |
|
Oh. :( Ah well. I guess that means I'm back to being stuck with a non auto-updating package. And yes, I've tried deleting and resubmitting it. I've got two hooks in use on GitHub, for Travis & Packagist. The former works perfectly fine, the latter not so much. |
|
I have the same issue, tried both types of URI: git and https. The package name is myak/packager. |
|
@hinikato I did a mistake and auto-updates failed for a while today so try again it's most likely fixed for you. |
|
So what do I have to do to make it auto-update? I've added my Packagist token to the GitHub service hook, I've got a valid composer.json in that bundle, and I've used the normal HTTPs URL. It should auto-update, right? |
|
@userfriendly Yes that looks all good, though as said above it seems to be failing with some packages for no apparent reason. |
|
But why me? :'( Can't it go and fail for someone else for no apparent reason? Eh, nae bother... going to try with another bundle soon. |
|
@Seldaek now it works, thanks! |
|
@userfriendly ok can you try to push or use the "test hook" button see if it's fixed? Same for @flack and whoever else had this issue. |
|
Used the "test hook" button as well as deleted and re-added the package. Still not auto-updating. I think it just really hates my bundle. |
|
@userfriendly I tried posting to the packagist API like github would, and it flipped your package to autoupdated (I reset it again). So at this point I would assume you got the wrong api token set up in github, or something like that.. please check on https://packagist.org/profile/ and try hitting test hook again, I'm now logging everything on the server and if it really fails let me know and I'll check the logs. |
|
Oh my god. It's not the token. It's because the repo is under an org and not under my username, and I didn't add the username to the hook. When I did, the package switched to auto-updating immediately. So sorry for wasting your time. >.< |
|
Eh well, shit happens :) Glad there is no other bug then. I'll close this for the time being. |
|
Just did a test commit to my repo and it looks like the issue is still there. github says the repo was updated two minutes ago, while packagist says it was updated yesterday. Or is there some delay that I should be aware of? |
|
P.S.: I also still see the notification "This package is not auto-updated" when I'm logged in at Packagist |
|
@danmichaelo when enabling the hook on github, have you configured the username or only the token ? By default, if you don't configure the username in the Packagist service hook, the name of the repo owner will be used. But this works only if there is a packagist user with the same name than the repo owner, which is likely not the case for the organization, while it can be the case for your personal account |
|
Ups, had it set it to my email address.. which is not the username on packagist. Silly, but thanks for helping, @stof ! |
|
my package also doesn't auto-update even though the username on github and packagist is the same (and i've entered it anyways) |
|
+1... seems to be a recurring issue? |
|
If it fails try deleting the hook and re-creating it. In some instances it seems that solves the problem on the github side. |
|
during the weeks before posting i've recreated the hook over 10 times which didn't fix it |
|
Your canonical URL was not a case-sensitive match for the github URL, that might have caused issues although we normally don't check for that anymore. But anyway I edited the URL, if you want to try again the test service button. Otherwise check that the domain is empty and the API key is correct. |
|
The only thing that seemed to clear this out was 1) removing the Packagist service from Github 2) re-adding the Packagist service on Github 3) Testing the service. If you don't test the service, your repo is never green-lit it seems... |
|
Step 1/2 seem to be required sometime but I think that's a @github failure. Step 3 is only necessary if you want to green-light a package immediately, otherwise it should happen first time you push. |
|
It does seem like it's a Github problem, but I can confirm that the package never updated after doing a push. Only after doing the test of the service did it work. |
|
Why does it not seem like a GitHub problem? We treat all github hook messages equally, and only read the package URL from them.. It's really rather weird that hitting test hook would change anything on either side. |
|
@fireproofsocks i re-added the hook several times and I've hit Test service on each try and the light has always been green but that didn't change a thing |
|
I'm having the same issues (had a repo called lamoni/NetConf, renamed it to lamoni/netconf), and the auto-update service hook to Packagist won't work. |
|
@lamoni if the settings are correct try to delete it and re-create it, sometimes it helps. |
|
@Seldaek did that and it fixed it, thanks! |
|
I'm having the same issues, I don't know if it is a GitHub problem or not, my repo is ginsen/photosort and the auto-update service hook to Packagist don't work. |
|
even if this this ticket is closed, i'd like to add this post witch can help such people. And... it works :) |
|
it happened to me too.
and its work |
|
Hey guys, thought I'd just pipe in and say watch out because similar issues can occur when you have a bitbucket repo because of this issue: bitbucket.org/site/master/issue/7775. I've personally struggled with this for a long time before I realised where the issue lay. If you're paying for bitbucket I highly suggest moving on from them as they have not been bothered to fix this issue in over 2 years. Hope this helps! |
|
FYI for me the issue was that I was forcing the version of the project on the version params in my composer.json file and I wasn't bumping it on each new tag |
|
I was fighting with this for an hour so here is what fixed it for me. As @Seldaek said - delete the package and create it again. After that it worked. |
|
@TVart method just works! Thanks! |
|
This still does not work for most of my repos. I am using username, token is correct, as well as url. |
|
请问现在解决了这个问题没有？我依然不能自动更新。 |
|
Throwing my +1 onto this. The auto-update will work 95% of the time, but fail the other 5% of the time. I tested this by adding a tag onto a repository, and it would show under packagist. Then deleting the tag, it would remain under packagist. If you look under settings, there's a "last delivery failed due to timeout" error. Pushing another tag, it appears under packagist and the previous tag is now gone. I've also tried doing a "force update" directly from packagist, and it actually took two attempts before the deleted tag was removed, so it's definitely hit and miss from either end. This doesn't only happen when deleting a tag, as I've had the same issue when trying to create a new tag. |
|
Good, this works randomly. If you have 2 branches and one tag, the tag never is updated while the branches shows the updated project. |
|
#200 (comment) @TVart : thanks, your second point about the url, fixes the Problem for me |
and others
The following package
http://packagist.org/packages/midgard/createphp
is not auto-updated since 2012-07-26 13:57 UTC
If I look into the github admin settings, everything looks good, and when I click "Test hook" it tells me that the payload is deployed. Could it be that something doesn't work right on the packagist side of things? In my other repos, I have the same configuration and they work fine, it's just this one that gives problems
The text was updated successfully, but these errors were encountered: