when I success config the Repositories
but it start has error;
the error is:
Unable to Retrieve History
Ref "HEAD" is ambiguous or does not exist.
Unable to Retrieve Paths
Ref "HEAD" is ambiguous or does not exist.
This just means the repository is empty. We should show a better error message, but empty repositories were rare until we added repository hosting. This message will go away once you make some commits.
You can follow this task for progress on fixing this to say "This repository is empty.":
https://secure.phabricator.com/T1493
Related
I am trying to implement ADM I followed all the steps here https://developer.amazon.com/docs/adm/integrate-your-app.html the only thing I didn't put yet is app.text file, because am not yet sending or receiving message, at the moment I just want to get the registration id that's it, but app is crashing. When i use compileOnly files('libs/amazon-device-messaging-1.1.0.jar') I am getting bellow error Failed resolution of: Lcom/amazon/device/messaging/ADM and when I use implementation files('libs/amazon-device-messaging-1.1.0.jar') I am getting bellow errorStub! You are bundling a stubbed jar in the apk! Please move it to the classpath instead
I tried this https://developer.amazon.com/docs/adm/integrate-your-app.html
We've migrated from Nexus 3.01.01 to 3.5.1-02. In the process we had to migrate internally published npms. One of those is the kendo-ui (commercial one) from Telerik/Progress. We have downloaded the licensed copy from Telerik and publishing it to our local nexus for consumption by our developers.
However the publishing fails with an error during payload parsing. I can publish the same tar without an issue to the older (3.01.01) nexus, so the tar/payload it self is OK.
The error seem to be at the point of trying to parse the npm payload. I can also publish a demo/simple npm (both scoped and non-scoped) without an issue. Spend the whole day trying to figure this out with no luck - appreciate any pointers or advice.
2017-09-06 18:49:09,160+0800 WARN [qtp762281666-4116] MIDALLE
org.sonatype.nexus.repository.httpbridge.internal.ViewServlet -
Failure servicing: PUT /repository/npm-hosted/#progress%2fkendo-ui
java.lang.IllegalStateException: Unexpected token VALUE_NULL at
[Source: java.io.InputStreamReader#1ebad5c7; line: 1, column: 896] at
com.sonatype.nexus.repository.npm.internal.NpmPublishParser.parseValue(NpmPublishParser.java:150)
at
com.sonatype.nexus.repository.npm.internal.NpmPublishParser.parseObject(NpmPublishParser.java:174)
at
com.sonatype.nexus.repository.npm.internal.NpmPublishParser.parseValue(NpmPublishParser.java:136)
at
com.sonatype.nexus.repository.npm.internal.NpmPublishParser.parseObject(NpmPublishParser.java:174)
at
com.sonatype.nexus.repository.npm.internal.NpmPublishParser.parseValue(NpmPublishParser.java:136)
at
com.sonatype.nexus.repository.npm.internal.NpmPublishParser.parsePackageRoot(NpmPublishParser.java:123)
at
com.sonatype.nexus.repository.npm.internal.NpmPublishParser.parse(NpmPublishParser.java:98)
at
com.sonatype.nexus.repository.npm.internal.NpmRequestParser.parseNpmPublish(NpmRequestParser.java:81)
at
com.sonatype.nexus.repository.npm.internal.NpmRequestParser.parsePublish(NpmRequestParser.java:60)
at
com.sonatype.nexus.repository.npm.internal.NpmHostedFacetImpl.putPackage(NpmHostedFacetImpl.java:85)
at
com.sonatype.nexus.repository.npm.internal.NpmHandlers$3.handle(NpmHandlers.java:172)
at
org.sonatype.nexus.repository.view.Context.proceed(Context.java:80)
Here's the gist for the full error from the nexus log.
This issue was resolved in scope of https://issues.sonatype.org/browse/NEXUS-14385
Fix Version/s:
3.6.1
There was a problem with parsing null values in package.json
I got this to work however I'm still trying to figure out the impact of the change. Please be cautious if you apply the same 'hack' to get this to work. I had to do this, because there was several other project teams that was getting affected.
In a nutshell I had to strip out few keys from the package.json of the kendo-ui package. My analysis is that these settings makes npm issue a network call that fails in our constraint environment.
The package.json keys that I removed are as follows.
First section
"_resolved": "https://registry.npm.telerik.com/#progress%2fkendo-ui/-/kendo-ui-2017.2.621.tgz",
"_shasum": "09a652ead21700716dd5a50f9e86e9bffcea640e",
"_shrinkwrap": null,
Second section
"dist": {
"shasum": "09a652ead21700716dd5a50f9e86e9bffcea640e",
"tarball": "http://registry.npm.telerik.com/#progress%2fkendo-ui/-/kendo-ui-2017.2.621.tgz"
},
I'd really appreciate if someone who know more about npm and npm definitions can inform the purpose of these settings in the package.json and potential impacts of removing them.
I need help understanding an error why I'm seeing an error.
The feature api is already enabled with the correct ApiListener object, and Api logs are being updated in /var/lib/icinga2/api/log/current .
But I'm getting this error when I restart icinga2:
Error: Error while evaluating expression: The type 'ApiUser' is unknown: in /etc/icinga2/conf.d/api-users.conf: 1:0-1:20
I'm running version r2.3.10-1 of Icinga2 on Ubuntu.
Can someone explain what the problem is?
You are probably mixing the current snapshot packages with the released stable versions. The 'ApiUser' object is part of the upcoming Icinga 2 v2.4 release and only available in git master (and therefore snapshot packages as well as docs). The stable 2.3.x tree does not have that kind of configuration object type and therefore bails out with an error.
Remove that file or its content, you don't need it for 2.3.x.
I've been trying to follow several different tutorials for building web APIs and web apps using clojure, but I keep receiving the same errors. From googling the errors it seems like the problem is definitely with my network, but I'm having trouble identifying the exact problem and figuring out how to resolve it.
This is the error message I receive every time when I try to run: lein run
Could not find artifact org.clojure:clojure:jar:1.2.0-beta1 in central (https://repo1.maven.org/maven2/)
Could not find artifact org.clojure:clojure:jar:1.2.0-beta1 in clojars (https://clojars.org/repo/)
Could not find artifact org.clojure:clojure-contrib:jar:1.2.0-beta1 in central (SAME AS FIRST LINK)
Could not find artifact org.clojure:clojure-contrib:jar:1.2.0-beta1 in clojars (SAME AS SECOND LINK)
This could be due to a typo in :dependencies or network issues.
If you are behind a proxy, try setting the 'http_proxy' environment variable.
If anyone knows how to resolve this, please let me know. Thanks!
I have a maven2 repository from which I'm trying to fetch an snapshot artifact with an appended timestamp. I'm (unsurprisingly) able to retrieve it fine when building with maven2 but when building with simple-build-tool (sbt), much preferred by me, I can't pull it down.
I can see from this question about snapshots in Ivy that it is possible to configure Ivy to get snapshot artifacts but I don't know how to tell sbt to do it.
The relevant bits of my current configuration:
val snapshotsName = "Snapshots Repository"
val snapshotsUrl = new java.net.URL("http://host:port/path/to/root")
val snapshotsPattern = "[organisation]/[module]/[revision]/[artifact]-[revision](-[classifier]).[ext]"
val snapshots = Resolver.url(snapshotsName, snapshotsUrl)(Patterns(snapshotsPattern))
Credentials(Path.userHome / ".ivy2" / ".credentials", log)
Update: After some more tinkering it looks like I can get it to point at the correct artifact url with the following pattern.
val snapshotsPattern = "[organisation]/[module]/[revision]-SNAPSHOT/[artifact]-[revision](-[timestamp]).[ext]"
With that I still need to specify the timestamp extra in the dependency
val dep = "group" % "artifact" % "0.0.1" extra("timestamp" -> "20101202.195418-3")
but it does pull the artifact. However it does NOT pull the artifact's dependencies. So it seems I've still got something wrong.
Alright, I got this sorted out but it wasn't actually an SBT problem it was 100% user error.
The Nexus I was using required authentication. I didn't have the authentication credentials set up correctly (see my authentication question) and because it wasn't properly authenticating it wasn't finding the metadata pom files and so SBT printed out the error message that it was failing I, incorrectly, assumed it was authenticating but not resolving. So I started messing with the patterns as evidenced in the actual question.
However, now that I have authentication setup correctly I changed back to just a regular repository declaration like so:
val snapshotsRepo = "Snapshots Repository" at "http://host:port/path/to/snapshots/root/"
and everything works. Artifacts are retrieved and dependencies resolved.