storage-api | S3 compatible object storage service that stores | Key Value Database library

If you are looking at the data in a normal view (not a User-ID view) you will not see them because the request contains only the uid as identifier, while you also need the cid (clientId).

By default, the OAuth 2.0 Login Page is auto-generated by the DefaultLoginPageGeneratingFilter.
The login page for a client defaults to this: OAuth2AuthorizationRequestRedirectFilter.DEFAULT_AUTHORIZATION_REQUEST_BASE_URI + "/{registrationId}". As per your configuration, registrationId: "keycloak", this means (/oauth2/authorization/keycloak).

Please check your WebSecurityConfigurerAdapter configuration. Try to override the default login page by configuring oauth2Login().loginPage() and (optionally) oauth2Login().authorizationEndpoint().baseUri().

The following listing shows an example:

It was happening to me too, after git-cloning a repo I had been working in (different computer). Symfony4 project. I had ran yarn install and composer install, then set up db, and then this manifest file error was happening. The way for me to fix it, after a bit of research: run encore to build the assets :-)

You are right, 2017-01-19 is not a valid Storage service version, see all versions here. The documentation article Versioning for the Azure Storage services also suggests the latest API version at the top.

Recommend you to use the latest if there is no specific requirement.

Update

See three points to fix:

Just use Vuex combined with this plugin nativescript-localstorage. I say it's untested on Nativescript 6. I can say it works because I use it my self.

Example of the store.js

So the problem was that I used the wrong project_id when gcloud config set project and gcloud defaulted to organization for some reason.

So I had to find correct project id using gcloud projects list and then use gcloud config set project {PROJECT-ID} (not the project name!)

I think this line:

Today I had the same problem with one of our apps. We were using rails-assets-tether gem from https://rails-assets.org. We notice that the same gem is available in the main repository (https://rubygems.org). The solution was to remove source block from the Gemfile.

I think that if you need those gems, then you have to wait for the certificate to be renewed (by website owners) or find an alternative source of those gems.

Update:

You can replace https://rails-assets.org with http://insecure.rails-assets.org. Please remember to switch back to https endpoint after this issue has been fixed

It may not be obvious, but the google-api-client version in the latest stable GCS connector is actually 1.20.0.

The reason is that this was the commit which rolled the api client version forward to 1.23.0, and it was part of a series of commits including this dependency-shading commit with the overall goal of no longer leaking the transitive dependency into the job classpath at all, precisely to avoid version collision issues in the future, at the cost of everyone having to bring their own fat jar containing the full api client dependencies themselves.

However, it turns out that many people have already grown to depend on the GCS-connector-provided api client to be on the classpath, so there are production workloads out there which cannot survive such a change inside of a minor version upgrade; thus, the upgraded GCS connector which uses 1.23.0 but also shades it so that it won't appear in the job classpath anymore is reserved for a future Dataproc 1.3+ or 2.0+ release.

In your case, you could try using a 1.20.0 version of your dependencies (you may also have to downgrade the version of the google-cloud-storage dependency you included, though a 1.22.0 version of that may still work assuming no breaking changes, since setBatchPath was indeed introduced only in 1.23.0), or otherwise you can try to shade all your own dependencies using sbt-assembly.

We can verify that setBatchPath was introduced only in 1.23.0: