no response from server after migrating to 9.0

see here:
https://stackoverflow.com/questions/64269197/google-ads-api-no-response-from-server-after-migrating-to-9-0
We were recently forced to migrate our Java Google Ads backend from 4.1.0 (v2) to 9.0.0 (v5). While all requests are now functioning normally in our local development environment, the identical requests fail from our Heroku server, in both test & prod.
Specifically:
    final GenerateKeywordIdeasPagedResponse response = keywordPlanIdeaServiceClient.generateKeywordIdeas(request);

never responds. This is only true on the deployed app. Locally, everything is fine. Account ID, client ID, client secret, developer token, login customer ID, refresh token, and service account user are all identical in both dev and test environments.
No error is thrown. Requests simply fail to respond. The Heroku server simply gives a 503 after timing out after 30 seconds, with no further information provided.
We've been rolling back to previous SDK/API versions. Here are the results:
SDK 9.0.0/API v5 FAIL
SDK 9.0.0/API v4 FAIL
SDK 8.0.0/API v4 FAIL
SDK 7.0.0/API v4 FAIL
SDK 6.0.0/API v4 WORKS!!! miraculously

Can you grab the gRPC logs for a call that hangs? They are logged to slf4j, and instructions for configuring this are available here.
The logger we're looking for is io.grpc=ALL.
BE VERY CAREFUL TO REDACT AUTHENTICATION CREDENTIALS BEFORE POSTING HERE
The gRPC logs will contain unredacted authentication headers (starting Authentication: Bearer: ....) and developer token (developer-token: ....). Please strip these before posting.

Also this sounds like it's probably a dependency related issue. I would suggest verifying that you have a consistent set of dependencies between your local and Heroku environments. Which build system are you using for each?

Thanks for that.  And yep, logging was our first thought.  We even found the same article to which you linked us.  Sadly, however:
https://stackoverflow.com/questions/64277081/how-to-log-to-googleads-requests
We've followed the advice given here: https://developers.google.com/google-ads/api/docs/client-libs/java/logging
Neither of the proposed solutions have any visible effect on what is logged to the console, either in dev or in deployment.

I'm guessing that log4j isn't picking up your configuration file. You can try running with -Dlog4j.debug which should print some helpful debugging info about where it's looking for configs.
Also, can you post your command line invocation and which slf4j dependencies you're using please?

Thanks for that!
Here is my local command line, as created by Eclipse:
"C:\Program Files\Java\jdk-13.0.2\bin\javaw.exe" -agentlib:jdwp=transport=dt_socket,suspend=y,address=localhost:61794 -Dmaven.home=EMBEDDED -Dclassworlds.conf=C:\Users\mad\eclipse-workspace-java.metadata.plugins\org.eclipse.m2e.launching\launches\m2conf8504121200360559788.tmp -Dm2e.workspace.state=C:\Users\mad\eclipse-workspace-java.metadata.plugins\org.eclipse.m2e.core\workspacestate.properties -Dmaven.multiModuleProjectDirectory=C:\Users\mad\git\balloonary-backend -Xmx1g -Djava.util.logging.config.file=./resources/jdk-logger.properties -Dlog4j.debug -javaagent:C:\Users\mad\eclipse\java-2020-06\eclipse\configuration\org.eclipse.osgi\222\0.cp\lib\javaagent-shaded.jar -Dfile.encoding=Cp1252 -classpath C:\Users\mad.p2\pool\plugins\org.eclipse.m2e.maven.runtime_<IP_ADDRESS>00610-1735\jars\plexus-classworlds-2.6.0.jar org.codehaus.plexus.classworlds.launcher.Launcher -B -X -e clean compile exec:java
as for Heroku, here is the Procfile:
web: java $JAVA_OPTS -Dserver.port=$PORT -Djava.util.logging.config.file=./jdk-logger.properties -cp target/classes:target/dependency/* io.balloonary.Main
Locally, I see this on startup (with or without the -Dlog4j.debug option you suggested, which seems to be ignored):
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/C:/Users/mad/.p2/pool/plugins/org.eclipse.m2e.maven.runtime.slf4j.simple_<IP_ADDRESS>00610-1735/jars/slf4j-simple-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [file:/C:/Users/mad/eclipse/java-2020-06/eclipse/configuration/org.eclipse.osgi/5/0/.cp/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.SimpleLoggerFactory]
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/C:/Users/mad/.p2/pool/plugins/org.eclipse.m2e.maven.runtime.slf4j.simple_<IP_ADDRESS>00610-1735/jars/slf4j-simple-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [file:/C:/Users/mad/eclipse/java-2020-06/eclipse/configuration/org.eclipse.osgi/5/0/.cp/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.SimpleLoggerFactory]
Heroku, however, nothing has nothing whatsoever to say about any logs, neither on build nor on startup.

So there's a couple of issues which will stop logs being generated here.

It looks like there's multiple slf4j implementations on the classpath. slf4j is only a facade and requires a binding to a logger implementation to actually produce logs. However, in your case you have multiple such bindings and as a result it's likely that you'll get no useful output.
It looks like you're specifying JUL configuration, so -Dlog4.debug won't do anything. I inferred that you were using log4j from your stackoverflow thread.

I'm assuming that your project already logs to java.util.logging. In this case you should add the following dependency to your project:
<dependency>
  <groupId>org.slf4j</groupId>
  <artifactId>slf4j-jdk14</artifactId>
  <version>1.7.25</version>
</dependency>

Next you should run mvn dependency:tree and find any other slf4j implementations on the classpath and remove them in favour of slf4j-jdk14. Then you should be able to enable the io.grpc=ALL logging in your ./jdk-logger.properties

First, thanks for your patience, I know this must be about as much fun for you as it is for me! You've been great so far.
Now, here is what I see when I examine the dependency tree for slf4j in Eclipse:

So, as you can see, there appears to be only the slf4j-jdk14 implementation in the dependencies.
Nonetheless, I've tried various "exclusions", all to no avail.
This seems to be a fairly well-known issue, as you can see here:
https://stackoverflow.com/questions/14024756/slf4j-class-path-contains-multiple-slf4j-bindings
Sadly, none of these solutions have been useful to me (so far).
Here is what I have at the moment:
	<dependency>
		<groupId>org.slf4j</groupId>
		<artifactId>slf4j-jdk14</artifactId>
		<version>1.7.25</version>
		<exclusions>
			<exclusion>
				<groupId>org.slf4j</groupId>
				<artifactId>slf4j-log4j12</artifactId>
			</exclusion>
			<exclusion>
				<groupId>log4j</groupId>
				<artifactId>log4j</artifactId>
			</exclusion>
			<exclusion>
				<groupId>org.eclipse.m2e.maven.runtime.slf4j.simple</groupId>
				<artifactId>slf4j</artifactId>
			</exclusion>
			<exclusion>
				<groupId>org.eclipse.osgi</groupId>
				<artifactId>log4j</artifactId>
			</exclusion>
		</exclusions>
	</dependency>

None of this, however, makes any difference to the behavior described previously.

So I'm not familiar with the Eclipse dependency view so I can't really advise based on that. If you had the output of mvn dependency:tree that would be useful.
I can see though that your exclusion is in the wrong place. When you specify an exclusion it has to go on the parent dependency which includes the dependency you want to exclude. In your case, it seems extremely unlikely that slf4j-jdk14 depends on anything from eclipse.
Can you also share your JUL config file please?

Progress... maybe?
Since I have no idea where this "org.eclipse.m2e.maven.runtime.slf4j.simple" dependency is defined (it's certainly not in the pom, so just weird), I replaced the Eclipse's embedded maven with the external system maven, and... no more "multiple SLF4J bindings" errors!
However! Still, no logs.
Here is jdk-logger.properties.  It lives under src/main/resources, but I'm not at all convinced it's being used at all:
handlers=java.util.logging.ConsoleHandler
com.google.ads.googleads.lib.logging.request.level=FINE
com.google.ads.googleads.lib.logging.request.level=FINE
java.util.logging.ConsoleHandler.level=FINE
java.util.logging.ConsoleHandler.formatter=java.util.logging.SimpleFormatter
io.grpc=ALL
Since you asked, here is the result of mvn dependency:tree
deps.txt
As you can see, there is only one reference to org.slf4j:slf4j-jdk14:jar:1.7.25 here

Looks like this is the offending dependency: com.google.guava:guava:jar:25.1-android:compile This should be version 28.2-android.

OK, I used an absolute path to specify the location of jdk-logger.properties.  No change.
Funny, though... I see this on the console:
[DEBUG] ignoreDelta true
[INFO] Copying 3 resources
[DEBUG] file application.properties has a filtered file extension
[DEBUG] copy C:\Users\mad\git\balloonary-backend\src\main\resources\application.properties to C:\Users\mad\git\balloonary-backend\target\classes\application.properties
[DEBUG] file jdk-logger.properties has a filtered file extension
[DEBUG] copy C:\Users\mad\git\balloonary-backend\src\main\resources\jdk-logger.properties to C:\Users\mad\git\balloonary-backend\target\classes\jdk-logger.properties
[DEBUG] file log4j.properties has a filtered file extension
[DEBUG] copy C:\Users\mad\git\balloonary-backend\src\main\resources\log4j.properties to C:\Users\mad\git\balloonary-backend\target\classes\log4j.properties
[DEBUG] no use filter components
I see this whether I use a relative path, like before, or the absolute path you recommend.
So.... any idea what "ignoreDelta" means or whose idea that is? Not mine.  Google search was unproductive.
I've been searching for a way to specify these properties in an XML file instead, but no luck so far.

I think the ignoreDelta is coming from the maven resources plugin:
https://issues.apache.org/jira/browse/MSHARED-516
Before we get too involved in this logging question, did you try the suggestion from @nwbirnie in his previous comment? I don't want to distract from the main goal of getting your app to run again. :)

Well, it was a nice idea.  This guava thing was being dragged along by something called guice, which it turns out was totally superfluous. So I removed that, and here is the new dependency tree:
deps2.txt
com.google.guava:guava:jar:28.2-android
Great.
But.... no change in behavior.  Still, no response from server.

Looks like you're also missing io.grpc:grpc-core:jar:1.30.0:compile.

OK then, added:

grpc-core
io.grpc
1.30.0

This has no effect, which is somewhat expected, since the project compiles fine without that.
Also, none of this explains why everything works (worked) locally, but not when deployed to the Heroku server.

Back to the logging issue, bear in mind that, of course, Heroku never had any of these extraneous Eclipse dependencies, and the whole "multiple SLF4J bindings" misadventure was never really an issue in deployment.  So, back to square 1... why no logs??

The configuration file for JUL is incorrect:
This line:
io.grpc=ALL

Should be:
io.grpc.level=ALL

Can you also add a Logger.getLogger("io.grpc.test").warn("some message") to check that the logging is configured correctly please?

Also what artifact do you publish to Heroku? Is it a .war file? How is this generated?

No .war file here.  Heroku simply builds (maven) from the specified git branch, and then launches, based on the command found in Procfile (see above).  The Java version used by Heroku is 1.8.
Could you please specify the classpath for "Logger"?  I see five possibilities (not including the interfaces), but none of them allow Logger.getLogger("io.grpc.test").warn("some message") to compile.

This is the one: https://docs.oracle.com/en/java/javase/11/docs/api/java.logging/java/util/logging/Logger.html
Should be warning("some message") rather than warn("some message")

Yep. So now I see:
WARNING: some message
Nothing more interesting than that. And only locally. Heroku server doesn't even show this message.

You mentioned earlier that you tried setting java.util.logging.config.file to an absolute path. When deploying to Heroku, are you confident that path exists on the Heroku server where the app is deployed?
Another brute force approach you could take would be to configure the LogManager at runtime, when your application starts up (at some point before your first request).
Option 1 - try to get LogManager to read your config file from your classpath
As mentioned earlier, java.util.logging.config.file won't work with resources on the classpath, but you can do this at runtime via something like:
LogManager.readConfiguration(Resources.getResource("jdk-logger.properties").openStream());

Option 2 - skip the config file and configure LogManager manually
LogManager.getGlobal().setLevel(Level.ALL);
Handler handler = new java.util.logging.ConsoleHandler();
handler.setLevel(Level.ALL);
LogManager.getGlobal().setHandler(handler);

Success!!!
but I think you meant:
	LogManager.getLogManager().readConfiguration(Resources.getResource("jdk-logger.properties").openStream());

but yeah, that kicked it in the right place! Great idea.
Unfortunately, I'm not sure how fruitful this was. Here are the annotated logs:
logs.docx

I agree that the stacktrace about InternalCensusStatsAccessor doesn't appear to be related to the issue.
Please can you attempt to construct a minimal failing example? Starting with an empty project, add the client library as a dependency and call generageKeywordIdeas(). Next add a few of your projects dependencies and try again. Keep doing this until you find a dependency that when added breaks the configuration. The upload the project here and I'll try to debug.

Here is my little test project:
v5-test.zip
on Github:
https://github.com/madc0w/google-ads-v5-test
Of course, all this works fine locally.
Deploying to Heroku is proving problematic, but I'm not sure what would be gained anyway, as you would have no access to that server. Anyway, I'll keep trying to do that.

I'm looking now. Your test app contains Google account credentials in the file ./v5-test/V5Test.launch. I would strongly suggest revoking these credentials (1) revoke the refresh token on accounts.google.com, and (2) reset your developer token on ads.google.com.

Ugh, you're right, of course. I figured these were all test-related values (not prod), so not too worried about them... but the developer token is of course the same in both environments.
We will reset it soon.

So I think this appears to be caused by having dots in your environment variable names. I just changed the app to pass these with underscores and it appears to just work...
2020-10-13T11:32:21.816593+00:00 heroku[worker.1]: State changed from starting to up
2020-10-13T11:32:23.174634+00:00 app[worker.1]: Picked up JAVA_TOOL_OPTIONS: -Xmx300m -Xss512k -XX:CICompilerCount=2 -Dfile.encoding=UTF-8
2020-10-13T11:32:23.294870+00:00 app[worker.1]: building google ads client
2020-10-13T11:32:27.250837+00:00 app[worker.1]: starting...
2020-10-13T11:32:28.093917+00:00 app[worker.1]: starting request
2020-10-13T11:32:29.815212+00:00 app[worker.1]: Exception in thread "main" com.google.ads.googleads.v5.errors.GoogleAdsException: errors {
2020-10-13T11:32:29.815223+00:00 app[worker.1]: error_code {
2020-10-13T11:32:29.815224+00:00 app[worker.1]: authorization_error: CUSTOMER_NOT_ENABLED
2020-10-13T11:32:29.815225+00:00 app[worker.1]: }
2020-10-13T11:32:29.815225+00:00 app[worker.1]: message: "The customer can\'t be used because it isn\'t enabled."
2020-10-13T11:32:29.815225+00:00 app[worker.1]: }
2020-10-13T11:32:29.815228+00:00 app[worker.1]:
2020-10-13T11:32:29.815356+00:00 app[worker.1]: at com.google.ads.googleads.v5.errors.GoogleAdsException$Factory.createException(GoogleAdsException.java:42)
2020-10-13T11:32:29.815402+00:00 app[worker.1]: at com.google.ads.googleads.v5.errors.GoogleAdsException$Factory.createException(GoogleAdsException.java:34)
2020-10-13T11:32:29.815436+00:00 app[worker.1]: at com.google.ads.googleads.lib.BaseGoogleAdsException$Factory.createGoogleAdsException(BaseGoogleAdsException.java:105)
2020-10-13T11:32:29.815472+00:00 app[worker.1]: at com.google.ads.googleads.lib.GoogleAdsExceptionTransformation.transform(GoogleAdsExceptionTransformation.java:35)
2020-10-13T11:32:29.815511+00:00 app[worker.1]: at com.google.ads.googleads.lib.ExceptionTransformingCallable$ExceptionTransformingFuture.onFailure(ExceptionTransformingCallable.java:83)
2020-10-13T11:32:29.815546+00:00 app[worker.1]: at com.google.api.core.ApiFutures$1.onFailure(ApiFutures.java:68)
2020-10-13T11:32:29.815617+00:00 app[worker.1]: at com.google.common.util.concurrent.Futures$CallbackListener.run(Futures.java:1039)
2020-10-13T11:32:29.815644+00:00 app[worker.1]: at com.google.common.util.concurrent.DirectExecutor.execute(DirectExecutor.java:30)
2020-10-13T11:32:29.815692+00:00 app[worker.1]: at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1165)
2020-10-13T11:32:29.815772+00:00 app[worker.1]: at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:958)
2020-10-13T11:32:29.815808+00:00 app[worker.1]: at com.google.common.util.concurrent.AbstractFuture.setException(AbstractFuture.java:749)
2020-10-13T11:32:29.815843+00:00 app[worker.1]: at com.google.api.gax.retrying.BasicRetryingFuture.handleAttempt(BasicRetryingFuture.java:179)
2020-10-13T11:32:29.815878+00:00 app[worker.1]: at com.google.api.gax.retrying.CallbackChainRetryingFuture$AttemptCompletionListener.handle(CallbackChainRetryingFuture.java:135)
2020-10-13T11:32:29.815914+00:00 app[worker.1]: at com.google.api.gax.retrying.CallbackChainRetryingFuture$AttemptCompletionListener.run(CallbackChainRetryingFuture.java:117)
2020-10-13T11:32:29.815957+00:00 app[worker.1]: at com.google.common.util.concurrent.DirectExecutor.execute(DirectExecutor.java:30)
2020-10-13T11:32:29.815989+00:00 app[worker.1]: at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1165)
2020-10-13T11:32:29.816023+00:00 app[worker.1]: at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:958)
2020-10-13T11:32:29.816057+00:00 app[worker.1]: at com.google.common.util.concurrent.AbstractFuture.setException(AbstractFuture.java:749)
2020-10-13T11:32:29.816102+00:00 app[worker.1]: at com.google.api.core.AbstractApiFuture$InternalSettableFuture.setException(AbstractApiFuture.java:95)
2020-10-13T11:32:29.816141+00:00 app[worker.1]: at com.google.api.core.AbstractApiFuture.setException(AbstractApiFuture.java:77)
2020-10-13T11:32:29.816173+00:00 app[worker.1]: at com.google.api.gax.grpc.GrpcExceptionCallable$ExceptionTransformingFuture.onFailure(GrpcExceptionCallable.java:97)
2020-10-13T11:32:29.816209+00:00 app[worker.1]: at com.google.api.core.ApiFutures$1.onFailure(ApiFutures.java:68)
2020-10-13T11:32:29.816244+00:00 app[worker.1]: at com.google.common.util.concurrent.Futures$CallbackListener.run(Futures.java:1039)
2020-10-13T11:32:29.816319+00:00 app[worker.1]: at com.google.common.util.concurrent.DirectExecutor.execute(DirectExecutor.java:30)
2020-10-13T11:32:29.816401+00:00 app[worker.1]: at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1165)
2020-10-13T11:32:29.816437+00:00 app[worker.1]: at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:958)
2020-10-13T11:32:29.816471+00:00 app[worker.1]: at com.google.common.util.concurrent.AbstractFuture.setException(AbstractFuture.java:749)
2020-10-13T11:32:29.816504+00:00 app[worker.1]: at io.grpc.stub.ClientCalls$GrpcFuture.setException(ClientCalls.java:545)
2020-10-13T11:32:29.816552+00:00 app[worker.1]: at io.grpc.stub.ClientCalls$UnaryStreamToFuture.onClose(ClientCalls.java:515)
2020-10-13T11:32:29.816586+00:00 app[worker.1]: at io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)
2020-10-13T11:32:29.816713+00:00 app[worker.1]: at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23)
2020-10-13T11:32:29.816714+00:00 app[worker.1]: at io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40)
2020-10-13T11:32:29.816714+00:00 app[worker.1]: at com.google.ads.googleads.lib.logging.LoggingInterceptor$1$1.onClose(LoggingInterceptor.java:111)
2020-10-13T11:32:29.816748+00:00 app[worker.1]: at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:426)
2020-10-13T11:32:29.816788+00:00 app[worker.1]: at io.grpc.internal.ClientCallImpl.access$500(ClientCallImpl.java:66)
2020-10-13T11:32:29.816844+00:00 app[worker.1]: at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.close(ClientCallImpl.java:689)
2020-10-13T11:32:29.816878+00:00 app[worker.1]: at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.access$900(ClientCallImpl.java:577)
2020-10-13T11:32:29.816918+00:00 app[worker.1]: at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal(ClientCallImpl.java:751)
2020-10-13T11:32:29.816949+00:00 app[worker.1]: at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:740)
2020-10-13T11:32:29.817003+00:00 app[worker.1]: at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
2020-10-13T11:32:29.817031+00:00 app[worker.1]: at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123)
2020-10-13T11:32:29.817066+00:00 app[worker.1]: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
2020-10-13T11:32:29.817155+00:00 app[worker.1]: at java.util.concurrent.FutureTask.run(FutureTask.java:266)
2020-10-13T11:32:29.817192+00:00 app[worker.1]: at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
2020-10-13T11:32:29.817228+00:00 app[worker.1]: at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
2020-10-13T11:32:29.817263+00:00 app[worker.1]: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
2020-10-13T11:32:29.817361+00:00 app[worker.1]: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
2020-10-13T11:32:29.817382+00:00 app[worker.1]: at java.lang.Thread.run(Thread.java:748)
2020-10-13T11:32:29.817548+00:00 app[worker.1]: Suppressed: com.google.api.gax.rpc.AsyncTaskException: Asynchronous task failed
2020-10-13T11:32:29.817591+00:00 app[worker.1]: at com.google.api.gax.rpc.ApiExceptions.callAndTranslateApiException(ApiExceptions.java:57)
2020-10-13T11:32:29.817612+00:00 app[worker.1]: at com.google.api.gax.rpc.UnaryCallable.call(UnaryCallable.java:112)
2020-10-13T11:32:29.817644+00:00 app[worker.1]: at com.google.ads.googleads.v5.services.KeywordPlanIdeaServiceClient.generateKeywordIdeas(KeywordPlanIdeaServiceClient.java:188)
2020-10-13T11:32:29.817699+00:00 app[worker.1]: at v5test.V5Test.run(V5Test.java:34)
2020-10-13T11:32:29.817743+00:00 app[worker.1]: at v5test.V5Test.main(V5Test.java:78)
2020-10-13T11:32:29.818171+00:00 app[worker.1]: Caused by: io.grpc.StatusRuntimeException: PERMISSION_DENIED: The caller does not have permission
2020-10-13T11:32:29.818224+00:00 app[worker.1]: at io.grpc.Status.asRuntimeException(Status.java:533)
2020-10-13T11:32:29.818294+00:00 app[worker.1]: ... 20 more
2020-10-13T11:32:30.198524+00:00 heroku[worker.1]: Process exited with status 1
2020-10-13T11:32:30.239581+00:00 heroku[worker.1]: State changed from up to crashed

Here's my code for reference. I removed loginCustomerId and serviceAccountUser since they weren't relevant to my authentication (I don't think this should make any difference).
Also here's a screenshot of the Heroku config for reference (with sensitive info removed).

Strange. These env vars with dots work fine in prod.  Anyway, I did as you suggested, but still can't deploy to Heroku.
Anyway, I had to move all the files up one directory so that Heroku could find the pom.xml, and I also added the  section you have in your pom.  Now everything works! So, thanks for that.
Now I'll be adding dependencies one by one, as you suggested. So stay tuned!

Oh yes - the dependency copy? That could be it as well... it was needed because Heroku couldn't locate GoogleAdsClient so was throwing ClassNotFoundException on startup. I noticed in your Procfile that dependencies were loaded from target/dependencies.
If so it's probably worth trying adding that directly to your project and see if it fixes things.

Well, that's that.  It works!!!
I don't pretend to understand why, but these changes to pom.xml make everything better.

Thanks so much for your help! You've been awesome.


proposal: x/sys/unix: add MmapPtr/MunmapPtr

Proposal Details
In github.com/ncruces/go-sqlite3 I'm go:linknaming mmap (I know, I'm sorry!) because I need unix.MAP_FIXED, which makes no sense for the version currently exported by either syscall or x/sys/unix.
Note that I'm currently link-naming syscall but could just as well use x/sys/unix (as I do for most everything else).
Link-naming is understandably discouraged, and on a path to being curtailed in https://github.com/golang/go/issues/67401.
I know my package is pretty much irrelevant, but exposing the autogenerated bits that allow mmap to be called from a bunch of different Unixes would help. For example, I have no chance to test z/OS, but IBM is incentivized to add a portable version to x/sys/unix.
Hence, I'd like to propose x/sys/unix exports the uintptr version (or *byte?) of mmap, munmap and maybe mremap.

I managed to miss #56123, I'm sorry.


Color is not the same that EmbedColor describes

EmbedColor.OrangeRed

and etc..

Odd, the colors themselves are from a color code list, so it might be worth going through and checking them.


I need help to debug my 405 Error

I really don't know what to do anymore. After hours I cannot find my problem.
To make it short. I'm developing a project since last year. In the beginning, I implemented Laravel Echo Server and it worked always. But I don't know when it should be in the last two month suddenly I cannot authenticate my user.
I did not notice it because I was working on all my little bugs. I have never touched the code for Broadcasting, nor is the route different. But somehow I get this error:
⚠ [16:32:06] - _bf6f2ruMazSXJewAAAA could not be authenticated to private-App.User.av0bQG6O7o
<!DOCTYPE html><!--
Symfony\Component\HttpKernel\Exception\MethodNotAllowedHttpException:  in file /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Routing/RouteCollection.php on line 255
Stack trace:
  1. Symfony\Component\HttpKernel\Exception\MethodNotAllowedHttpException->() /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Routing/RouteCollection.php:255
  2. Illuminate\Routing\RouteCollection->methodNotAllowed() /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Routing/RouteCollection.php:242
  3. Illuminate\Routing\RouteCollection->getRouteForMethods() /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Routing/RouteCollection.php:176
  4. Illuminate\Routing\RouteCollection->match() /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Routing/Router.php:636
  5. Illuminate\Routing\Router->findRoute() /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Routing/Router.php:625
  6. Illuminate\Routing\Router->dispatchToRoute() /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Routing/Router.php:614
  7. Illuminate\Routing\Router->dispatch() /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:176
  8. Illuminate\Foundation\Http\Kernel->Illuminate\Foundation\Http\{closure}() /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php:30
  9. Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}() /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/nova/src/Http/Middleware/ServeNova.php:26
...
Client can not be authenticated, got HTTP status 405

I really don't have any clue what could be the case.
How can I debug this? I don't know at which point it fails.
And one additional question. Looking at the laravel-echo-server.json file I've "devMode": true,. What does it do? Is there somewhere a log file?

Have you tested performing a POST to /broadcasting/auth of your Laravel app to ensure that everything is setup correctly?

@tlaverdure thank you for your fast answer.
I'm actually not sure how to do it. I just consoled axios.post('/broadcasting/auth') but this gives me a 403.
I want you to show the error from the terminal maybe it helps:

The setup is untouched and worked all the time. So something in my web.php should be fishy, but I don't get it. The route is listed:

I'm currently destroying every route I have to a minimum. Now I get the error 404!
Besides, I found the debug option now. Maybe it helps you.
Starting server in DEV mode...

  express:application set "x-powered-by" to true +0ms
  express:application set "etag" to 'weak' +3ms
  express:application set "etag fn" to [Function: generateETag] +1ms
  express:application set "env" to 'development' +0ms
  express:application set "query parser" to 'extended' +0ms
  express:application set "query parser fn" to [Function: parseExtendedQueryString] +0ms
  express:application set "subdomain offset" to 2 +1ms
  express:application set "trust proxy" to false +0ms
  express:application set "trust proxy fn" to [Function: trustNone] +1ms
  express:application booting in development mode +0ms
  express:application set "view" to [Function: View] +0ms
  express:application set "views" to '/Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/views' +0ms
  express:application set "jsonp callback name" to 'callback' +1ms
  express:router use '/' query +25ms
  express:router:layer new '/' +1ms
  express:router use '/' expressInit +4ms
  express:router:layer new '/' +1ms
  socket.io:server initializing namespace / +0ms
  socket.io-parser encoding packet {"type":0,"nsp":"/"} +0ms
  socket.io-parser encoded {"type":0,"nsp":"/"} as 0 +1ms
  socket.io:server creating engine.io instance with opts {"path":"/socket.io","initialPacket":["0"]} +2ms
  socket.io:server attaching client serving req handler +35ms
✔  Running at localhost on port 6001
  ioredis:redis status[localhost:6379]: [empty] -> connecting +50ms
✔  Channels are ready.
  ioredis:redis status[localhost:6379]: [empty] -> connecting +5ms
  express:router:route new '/apps/:appId/status' +1ms
  express:router:layer new '/apps/:appId/status' +1ms
  express:router:route get '/apps/:appId/status' +1ms
  express:router:layer new '/' +0ms
  express:router:route new '/apps/:appId/channels' +0ms
  express:router:layer new '/apps/:appId/channels' +1ms
  express:router:route get '/apps/:appId/channels' +0ms
  express:router:layer new '/' +0ms
  express:router:route new '/apps/:appId/channels/:channelName' +1ms
  express:router:layer new '/apps/:appId/channels/:channelName' +0ms
  express:router:route get '/apps/:appId/channels/:channelName' +0ms
  express:router:layer new '/' +1ms
  express:router:route new '/apps/:appId/channels/:channelName/users' +0ms
  express:router:layer new '/apps/:appId/channels/:channelName/users' +0ms
  express:router:route get '/apps/:appId/channels/:channelName/users' +0ms
  express:router:layer new '/' +0ms
  express:router:route new '/apps/:appId/events' +0ms
  express:router:layer new '/apps/:appId/events' +1ms
  express:router:route post '/apps/:appId/events' +0ms
  express:router:layer new '/' +0ms
✔  Listening for http events...
  ioredis:redis queue command[0] -> psubscribe(*) +1ms
  ioredis:redis status[<IP_ADDRESS>:6379]: connecting -> connect +31ms
  ioredis:redis write command[0] -> info() +1ms
  ioredis:redis status[<IP_ADDRESS>:6379]: connecting -> connect +4ms
  ioredis:redis write command[0] -> info() +0ms
  ioredis:redis status[<IP_ADDRESS>:6379]: connect -> ready +5ms
  ioredis:redis status[<IP_ADDRESS>:6379]: connect -> ready +47ms
  ioredis:connection send 1 commands in offline queue +0ms
  ioredis:redis write command[0] -> psubscribe(*) +1ms
✔  Listening for redis events...

Server ready!

  engine intercepting request for path "/socket.io/" +0ms
  engine handling "GET" http request "/socket.io/?EIO=3&transport=polling&t=MTwVm_g" +0ms
  engine handshaking client "vYoNj4839ob-XuK3AAAA" +3ms
  engine:socket sending packet "open" ({"sid":"vYoNj4839ob-XuK3AAAA","upgrades":["websocket"],"pingInterval":25000,"pingTimeout":5000}) +0ms
  engine:socket sending packet "message" (0) +0ms
  engine:polling setting request +0ms
  engine:socket flushing buffer to transport +1ms
  engine:polling writing "96:0{"sid":"vYoNj4839ob-XuK3AAAA","upgrades":["websocket"],"pingInterval":25000,"pingTimeout":5000}2:40" +2ms
  engine:socket executing batch send callback +6ms
  socket.io:server incoming connection with id vYoNj4839ob-XuK3AAAA +2s
  socket.io:client connecting to namespace / +0ms
  socket.io:namespace adding socket to nsp / +0ms
  socket.io:socket socket connected - writing packet +0ms
  socket.io:socket joining room vYoNj4839ob-XuK3AAAA +0ms
  socket.io:socket packet already sent in initial handshake +1ms
  socket.io:socket joined room vYoNj4839ob-XuK3AAAA +3ms
  engine intercepting request for path "/socket.io/" +28ms
  engine handling "POST" http request "/socket.io/?EIO=3&transport=polling&t=MTwVn0B&sid=vYoNj4839ob-XuK3AAAA" +0ms
  engine setting new request for existing client +0ms
  engine:polling received "136:42["subscribe",{"channel":"private-App.User.p7xbY9b3WL","auth":{"headers":{"X-CSRF-TOKEN":"x5Lf215pEMQO7Utds12SwoLADpS4Cx8QgKtXJnWN"}}}]" +27ms
  engine:socket packet +23ms
  socket.io-parser decoded 2["subscribe",{"channel":"private-App.User.p7xbY9b3WL","auth":{"headers":{"X-CSRF-TOKEN":"x5Lf215pEMQO7Utds12SwoLADpS4Cx8QgKtXJnWN"}}}] as {"type":2,"nsp":"/","data":["subscribe",{"channel":"private-App.User.p7xbY9b3WL","auth":{"headers":{"X-CSRF-TOKEN":"x5Lf215pEMQO7Utds12SwoLADpS4Cx8QgKtXJnWN"}}}]} +2s
  socket.io:socket got packet {"type":2,"nsp":"/","data":["subscribe",{"channel":"private-App.User.p7xbY9b3WL","auth":{"headers":{"X-CSRF-TOKEN":"x5Lf215pEMQO7Utds12SwoLADpS4Cx8QgKtXJnWN"}}}]} +18ms
  socket.io:socket emitting event ["subscribe",{"channel":"private-App.User.p7xbY9b3WL","auth":{"headers":{"X-CSRF-TOKEN":"x5Lf215pEMQO7Utds12SwoLADpS4Cx8QgKtXJnWN"}}}] +0ms
  socket.io:socket dispatching an event ["subscribe",{"channel":"private-App.User.p7xbY9b3WL","auth":{"headers":{"X-CSRF-TOKEN":"x5Lf215pEMQO7Utds12SwoLADpS4Cx8QgKtXJnWN"}}}] +0ms
  engine intercepting request for path "/socket.io/" +31ms
  engine handling "GET" http request "/socket.io/?EIO=3&transport=polling&t=MTwVn0D&sid=vYoNj4839ob-XuK3AAAA" +1ms
  engine setting new request for existing client +0ms
  engine:polling setting request +29ms
  engine upgrading existing transport +40ms
  engine:socket might upgrade socket transport from "polling" to "websocket" +68ms
  engine:ws received "2probe" +0ms
  engine:ws writing "3probe" +0ms
  engine:socket writing a noop packet to polling for fast upgrade +111ms
  engine:polling writing "1:6" +151ms
  engine:ws received "5" +107ms
  engine:socket got upgrade packet - upgrading +8ms
  engine:polling closing +11ms
  engine:polling transport discarded - closing right away +0ms
⚠ [19:33:27] - vYoNj4839ob-XuK3AAAA could not be authenticated to private-App.User.p7xbY9b3WL
<!doctype html>
<html lang="en" dir="ltr">
	<head> 404 not found

Client can not be authenticated, got HTTP status 404
  socket.io-parser encoding packet {"type":2,"data":["subscription_error","private-App.User.p7xbY9b3WL",404],"nsp":"/"} +451ms
  socket.io-parser encoded {"type":2,"data":["subscription_error","private-App.User.p7xbY9b3WL",404],"nsp":"/"} as 2["subscription_error","private-App.User.p7xbY9b3WL",404] +0ms
  socket.io:client writing packet ["2[\"subscription_error\",\"private-App.User.p7xbY9b3WL\",404]"] +475ms
  engine:socket sending packet "message" (2["subscription_error","private-App.User.p7xbY9b3WL",404]) +266ms
  engine:socket flushing buffer to transport +0ms
  engine:ws writing "42["subscription_error","private-App.User.p7xbY9b3WL",404]" +268ms
  engine:ws received "2" +25s
  engine:socket packet +25s
  engine:socket got ping +0ms
  engine:socket sending packet "pong" (undefined) +0ms
  engine:socket flushing buffer to transport +0ms

I hope you don't mind @tlaverdure when I comment my process to find this bug. (maybe it's useful for someone)
Now in handler.php I added
public function render($request, Exception $exception)
{
    logger('request', toArray($request));
    logger($exception);

And it results:
[2018-12-04 19:58:07] local.DEBUG: request {"attributes":[],"request":[],"query":[],"server":[],"files":[],"cookies":[],"headers":[]}
[2018-12-04 19:58:07] local.DEBUG: Symfony\Component\HttpKernel\Exception\NotFoundHttpException in /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Routing/RouteCollection.php:179
Stack trace:
#0 /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Routing/Router.php(636): Illuminate\Routing\RouteCollection->match(Object(Illuminate\Http\Request))
#1 /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Routing/Router.php(625): Illuminate\Routing\Router->findRoute(Object(Illuminate\Http\Request))
#2 /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Routing/Router.php(614): Illuminate\Routing\Router->dispatchToRoute(Object(Illuminate\Http\Request))
#3 /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(176): Illuminate\Routing\Router->dispatch(Object(Illuminate\Http\Request))
#4 /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(30): Illuminate\Foundation\Http\Kernel->Illuminate\Foundation\Http\{closure}(Object(Illuminate\Http\Request))
#5 /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/fideloper/proxy/src/TrustProxies.php(57): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#6 /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(151): Fideloper\Proxy\TrustProxies->handle(Object(Illuminate\Http\Request), Object(Closure))
#7 /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#8 /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php(31): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#9 /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(151): Illuminate\Foundation\Http\Middleware\TransformsRequest->handle(Object(Illuminate\Http\Request), Object(Closure))
#10 /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#11 /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php(31): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#12 /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(151): Illuminate\Foundation\Http\Middleware\TransformsRequest->handle(Object(Illuminate\Http\Request), Object(Closure))
#13 /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#14 /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/ValidatePostSize.php(27): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#15 /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(151): Illuminate\Foundation\Http\Middleware\ValidatePostSize->handle(Object(Illuminate\Http\Request), Object(Closure))
#16 /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#17 /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/CheckForMaintenanceMode.php(62): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#18 /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(151): Illuminate\Foundation\Http\Middleware\CheckForMaintenanceMode->handle(Object(Illuminate\Http\Request), Object(Closure))
#19 /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#20 /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(104): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#21 /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(151): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#22 /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(116): Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter(Object(Illuminate\Http\Request))
#23 /Users/shadrix/Dropbox/Business/insta.food/Website_W_Laravel/instafood/public/index.php(56): Illuminate\Foundation\Http\Kernel->handle(Object(Illuminate\Http\Request))
#24 /Users/shadrix/.composer/vendor/laravel/valet/server.php(147): require('/Users/shadrix/...')
#25 {main}

🎉🎉 I FOUND IT.
SO don't ask me why, but somehow the code for reading authHost changed.
Before that I had:
"authHost": "https://instafood.test/",
"authEndpoint": "/broadcasting/auth",

Although this worked one year long, I don't know what happened but now it needs to be
"authHost": "https://instafood.test",
"authEndpoint": "/broadcasting/auth",

So without the slash!


[Enhancement] Recently used maps or commands

Firstly, thanks for such an amazing plugin. Our correspondence on Reddit last night convinced me to try this out. Totally revolutionising how I use Neovim.
One thing I thought would be a great, low priority enhancement, would be to open legendary and see my most commonly used commands at the top of the window.
Appreciate this would be an additional dependency (likely on sqlite.lua) so this should be an optional add in for people.

Hey, thanks for the GitHub Sponsorship! Really, really appreciate that!
I'm open to a change like this, but it would definitely be optional and opt-in due to needing an extra dependency.
I'm also not entirely sure if it's possible, exactly. I spent a lot of time trying to figure out custom sorting, and it basically looks like that's up to the implementer of vim.ui.select() to handle.
I think a feature like this might need to be implemented as a separate plugin, and it would be an integration with your vim.ui.select() provider (e.g. you'd need a Telescope plugin to handle it, since I want this plugin to stay agnostic to the vim.ui.select() provider).
Alternatively I could make a separate command that shows only your top n most commonly used commands, where n would be a number configurable via setup.
I'm curious which of these approaches the community would like to see more. With the latter, we could keep that controlled in this plugin and agnostic to vim.ui.select(), but not having everything available at once might be a weird UX.
Thoughts?

It's my pleasure. Feels wrong not to sponsor given my whole Neovim workflow will now focus on the plugin ❤ . (Plus I see you work for a certain company which is another huge love of mine!).
I'll be honest and say I don't like the idea of an external dependency like sqlite as it feels bulky. Also, likely to soak up time in support and maintenance instead of core improvements to the plugin.
Your suggestion on a top n list is a great idea though! Much simpler and at least I have a choice in the matter. If I accidentally hit the wrong command a couple of times and it's in my damn list of most recently used then I may be forced to clear the whole list to remove it 😆 .

I'm not sure how exactly to do it without something like sqlite. It could be stored in a file in ~/.cache/nvim/ somewhere, but I'm not sure if using a file would be slow, since you'd have to read from it every time you want to find your most common commands, and write to it every time you run a command (also I think we could only track commands run through legendary, I don't think there would be a way for me to track when you type a command manually).
I'd also need to do some research on "frecency" algorithms, as I think that's what we'd want (basically what shows up would be a function of both how recently and how frequently you used each command, it's used for example in Firefox's address bar suggestions, and I think there's a Telescope plugin for frecency sorting as well).

Yeah I actually use that plugin regularly. It's quite clever in that when I boot up Neovim it will sometimes alert me that it's cleared some unused commands.
The more I think about my enhancement, the more I'm now sceptical...because in reality I use my mappings for the most common actions. So if I can't remember the keymap or the command is too verbose, then I reach for legendary. And if I can't remember it or I've made the command verbose, it's because it's a low frequency item.
Crikey. Long day.

Really, really great! And per session is a really sensible idea too. Thanks for implementing so quickly!

No problem, the idea came to me last night.


Feature: support uploading image for Image column

Type

[x] Bug Fix
[x] New Feature
[ ] Sample

Related Issues?
NA
What is in this Pull Request ?
Supports uploading image to the site assets library for image column

@gautamdsheth What will we do with this one for the next release as I believe we discussed this implementation is quite minimalistic?

@KoenZomers - I guess we can squeeze it in for this release ?

@KoenZomers Don't you think we'll make it difficult for ourselves to evolve on this in a future version with backwards compatibility if we do? If you think we can work our way through that, let's merge and see what kind of feedback we receive on shortcomings.

@KoenZomers - we should be ok now. Was a bit difficult in current format because we were reliant on existing uploaded files. The parameter -ServerRelativePath makes more sense IMHO for that scenario. We can use -Path parameter for file to be uploaded from the local file system, which makes more sense.
Thoughts?

Let's do it then


bazel repository context has empty string for native.bazel_version

Discovered this while debugging the following runs: https://github.com/buildfarm/buildfarm/actions/runs/11227508099/job/31209992929
This differs from my local installation (and every other one I've found) that reflects, for instance, 7.3.2 into the string "7.3.2", which is used by bazel_features to discover whether a ProtoInfo should be available globally.
There's a substantial amount of debug output in that run, but the notable piece is (see EOL for difference in version):
DEBUG: /home/runner/work/buildfarm/buildfarm/test_extension.bzl:10:10: Proto Info is struct(CcSharedLibraryInfo = <provider>, DefaultInfo = <function DefaultInfo>, JavaInfo = None, JavaPluginInfo = None, PackageSpecificationInfo = <function PackageSpecificationInfo>, ProtoInfo = None, PyCcLinkParamsProvider = None, PyInfo = None, PyRuntimeInfo = None, RunEnvironmentInfo = <function RunEnvironmentInfo>, __TestingOnly_NeverAvailable = None) for native.bazel_version=``

While a local environment that can extract native.bazel_version would print out there:
DEBUG: /home/werkt/dev/bazel-buildfarm/test_extension.bzl:10:10: Proto Info is struct(CcSharedLibraryInfo = <provider>, DefaultInfo = <function DefaultInfo>, JavaInfo = <provider>, JavaPluginInfo = <provider>, PackageSpecificationInfo = <function PackageSpecificationInfo>, ProtoInfo = <provider>, PyCcLinkParamsProvider = <provider>, PyInfo = <provider>, PyRuntimeInfo = <provider>, RunEnvironmentInfo = <function RunEnvironmentInfo>, __TestingOnly_NeverAvailable = None) for native.bazel_version=`7.3.2`

Note the version output at the end. Repo rule and bzlmod shenanigans available here
Is it possible the bazel 7.3.2 (same thing happens with 7.3.1) is polluted in the version this retrieves? I tried this with and without bazelisk-cache, no change. How could the bazel this pulls differ like this?

I am not sure I follow what is the issue there. Can you elaborate how you use the action and what's actually wrong?

We use the action to build and perform codeql analysis/validation.
The problem is that very-new @protobuf is using bazel version detection to determine the type to use for ProtoInfo, and this is in conflict with a legacy @googleapis repository using the deprecated @rules_proto.
The basic reproducer is that bazel version does not yield a well formed Build label like 7.3.2 (this is emblematic of the problem's effect internally, where native.bazel_version is aligned to this output), only on github actions images, for reasons I don't yet understand (I suspect some java injection).
This seems to go much deeper, as every actions image for ubuntu seems to exercise this problem, and it is easily reproducible. I'll bring it up perhaps with the actions/remote-images project.


Add systemd support

We may be able to rely on ansible_service_mgr for detecting which init system to use.

Closed by #124


Error: Cannot find module './enable.json'

Error: Cannot find module './enable.json'

We no longer support this bot, and this is because you didn't include an enable.json file.


Fix SimStore NumPy deprecations

Removes some old tostring() calls that should be tobytes().

This is ready for review and comment. I will leave it open for at least 24 hours, merging no earlier than Wed 07 Apr 17:00 GMT (19:00 local).


Improve documentation about cross-namespace references

This is a Feature Request

What would you like to be added
CustomResourceDefinitions and new internal APIs might refer to objects across namespaces. However, there are risks / challenges.
Document these.
Why is this needed

People who are considering using a cross-namespace reference in the API they are designing will want an opportunity to read about these.
Someone else providing feedback on that API might like a stable URI for the page that warns about the risks.

Comments
@deads2k suggested this list of risks / shortcomings / whatever:
Cross namespace references

create issues with leaking information about one namespace into another namespace - (status messages for instance)
[risk] potential invasions into other namespaces - "give me that one over there" that either require exceptional checks
[can add] referential integrity issues that one party cannot solve - referencing a namespace doesn't imply the power to control the other namespace
[have] unclear semantics on deletion - if a namespace is referenced by other namespaces, what should a delete do?  should it clean up or force the namespace to remain alive?
[have]    unclear semantics on creation - if a namespaces is created after its reference, is it the one we're waiting for or is it a different one created in the same name

/kind feature
/sig api-machinery
/language en

/triage accepted

Looks like a list was typed up here: https://github.com/kubernetes/community/pull/5455/files - I guess we can re-use the same content?
@sftim where should this be documented?

/assign

/remove-lifecycle stale


"Then add the Smelte Rollup plugin (after svelte but before css)." Where do I do this?

In the instruction there is the following sentence.
"Then add the Smelte Rollup plugin (after svelte but before css)."
There is no detailed instructions as to what file this is or the directory it is in etc.
I have no idea what this pertains to or where to place the code.
I installed Svelte using the instructions at the following link under the title of "use Degit".
https://svelte.dev/blog/the-easiest-way-to-get-started
Where do I add this "Svelte rollup plug in" ?
Thank you.

I think I see it. it is rollup.config ?
You should mention that in the instructions :)
Thank you!


Add pandas.Dataframe examples in doc

See also: milvus-io/pymilvus#1122

Great, thanks!
Minor comments:

small typo in the commit message: dock instead of doc
another small typo: word_cound instead of word_count

/assign @shanghaikid


Fix the ssh url validation tom include a few cases with - in the url

Description

Update the regex which validates the ssh url to include a few cases as listed in the issue.

Fixes # (issue)
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Locally
JUnit

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

/ok-to-test sha=7bf8375


In merge.ThreeWay(), use Diff() across the board

Initially, this code used DiffLeftRight() for some kinds
of collections. Standardize on Diff().
Towards #148

This one's even shorter, and we agreed we wanted to do this yesterday, right?

LGTM

yes


[unit test] improve unit test coverage for yurtingress

What would you like to be added:
improve unit test coverage for yurtingress:
target coverage: 70%
Why is this needed:
improve unit test coverage for OpenYurt project.
others
/kind feature

/assign

The issue was fixed by #85


Don't Merge! PR real time test for webhook case

Docs Build status updates of commit 6e84972:
:clock10: Pending: waiting for processors (19 builds ahead of you)
:warning: Docs Build is busy, currently there are 19 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 6e84972:
:clock10: Full build: the average full build time is 7 min(s) 15 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit 6e84972:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-conceptual/testing.md
:warning:Warning
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)
Details

docs-ref-conceptual/testing.md

[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Support decoding 64 bit lengths

At present, it will only decode 8, 16, and 32 bit lengths. 64 bit is unsupported.

Incorrectly linked to PR


Void the Maven coordinates for react-native and hermes-engine

Summary:
This diff moves the publishing coordinates from:
com.facebook.react:react-native
com.facebook.react:hermes-engine

to
com.facebook.react:react-android
com.facebook.react:hermes-android

I've picked those they are the most layout friendly when building from source, but we can discuss if we want others.
I've updated the Gradle plugin to have a dependencySubstitution rule + update the template with those changes.
It should now be possible to still use implementation("com.facebook.react:react-native:+") inside libraries
on 0.71+ and RNGP will resolve dependencies correctly.
Changelog:
[Android] [Changed] - Void the Maven coordinates for react-native and hermes-engine
Differential Revision: D41380525

This needs a bump + release of the Gradle Plugin in order for the CI to be green

This needs a bump + release of the Gradle Plugin in order for the CI to be green

ok so it sounds like we need to do the bump here in main (so to RNGP 0.72) and then to cherry-pick the necessary changes + new release of RNGP on 0.71


Imgur Running into Rate Limit

Imgur appears to be running into a rate limit, but only for certain items.

Very difficult to reproduce.

Retrying on my PC with the same post results in a success.


[Doc] adjust JSON function TOC and optimize release notes

What type of PR is this：

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] I have added user document for my new feature or new function

run starrocks_admit_test


Ver 1.6.2rc2: "Update Tor" breaks Tor (will not connect)

Warning: I am a noob without really any decent understanding of coding, so apologies.
I have a Raspi Blitz (Fulmo) that was working with 1.6.2rc2
I then (foolishly?) chose "update tor from the source code" and many many screens filled with updates (see tor_update.txt)
After that (and even after a reboot), I have this error:
*** LND SYSTEMD STATUS ***
● lnd.service - LND Lightning Daemon
   Loaded: loaded (/etc/systemd/system/lnd.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Sat 2020-11-28 19:09:51 CET; 34s ago
  Process: 5383 ExecStartPre=/home/admin/config.scripts/blitz.systemd.sh log lightning STARTED (code=exited, status=0/SUCCESS)
  Process: 5385 ExecStart=/usr/local/bin/lnd --tor.active --tor.streamisolation --tor.v3 --listen=<IP_ADDRESS>:9735 ${lndExtraParameter} (code=exited, status=1/FAILURE)
 Main PID: 5385 (code=exited, status=1/FAILURE)

...so it seems that I've lost some important configuration? Or maybe the "updated" source code is incompatible with raspian?
In any case, I can't seem to roll back the tor install and I don't have the hardware (new mini sd card or even a mini reader) to start again from a clean image.
So I am hoping to repair, configure or roll back Tor.
Any ideas?
Thanks in advance!
tor_update.txt

@openoms do you see anything here we need to fix for v1.6.2 release?

We tested the Tor update method successfully before.
I have advised on Telegram already that for now there is no way around having an SDcard writer to be able to flash clean images as a fallback and update.

Thanks for looking at this issue.
I just logged in (via terminal) and see this:
945 RESTARTS DETECTED - LND might be in a error loop
Nov 29 10:53:46 zPi lnd[1593]: dial tcp <IP_ADDRESS>:9050: connect: connection refused
Nov 29 10:54:46 zPi lnd[2614]: dial tcp <IP_ADDRESS>:9050: connect: connection refused
err='Tor tcp connection refused'
More Error Detail:
err='Tor tcp connection refused'

In response to sudo journalctl -u lnd, I get:
-- Logs begin at Sat 2020-11-28 19:04:15 CET, end at Sun 2020-11-29 10:56:56 CET. --
Nov 28 19:06:49 zPi systemd[1]: Starting LND Lightning Daemon...
Nov 28 19:06:49 zPi systemd[1]: Started LND Lightning Daemon.
Nov 28 19:06:50 zPi lnd[3068]: dial tcp <IP_ADDRESS>:9050: connect: connection refused
Nov 28 19:06:50 zPi systemd[1]: lnd.service: Main process exited, code=exited, status=1/FAILURE
Nov 28 19:06:50 zPi systemd[1]: lnd.service: Failed with result 'exit-code'.
Nov 28 19:07:51 zPi systemd[1]: lnd.service: Service RestartSec=1min expired, scheduling restart.
Nov 28 19:07:51 zPi systemd[1]: lnd.service: Scheduled restart job, restart counter is at 1.
Nov 28 19:07:51 zPi systemd[1]: Stopped LND Lightning Daemon.
Nov 28 19:07:51 zPi systemd[1]: Starting LND Lightning Daemon...
Nov 28 19:07:51 zPi systemd[1]: Started LND Lightning Daemon.
Nov 28 19:07:51 zPi lnd[3914]: dial tcp <IP_ADDRESS>:9050: connect: connection refused
Nov 28 19:07:51 zPi systemd[1]: lnd.service: Main process exited, code=exited, status=1/FAILURE
Nov 28 19:07:51 zPi systemd[1]: lnd.service: Failed with result 'exit-code'.

[skipping 7000 lines...]

Nov 29 10:55:47 zPi systemd[1]: lnd.service: Service RestartSec=1min expired, scheduling restart.
Nov 29 10:55:47 zPi systemd[1]: lnd.service: Scheduled restart job, restart counter is at 945.
Nov 29 10:55:47 zPi systemd[1]: Stopped LND Lightning Daemon.
Nov 29 10:55:47 zPi systemd[1]: Starting LND Lightning Daemon...
Nov 29 10:55:47 zPi systemd[1]: Started LND Lightning Daemon.
Nov 29 10:55:47 zPi lnd[4197]: dial tcp <IP_ADDRESS>:9050: connect: connection refused
Nov 29 10:55:47 zPi systemd[1]: lnd.service: Main process exited, code=exited, status=1/FAILURE
Nov 29 10:55:47 zPi systemd[1]: lnd.service: Failed with result 'exit-code'.
Nov 29 10:56:47 zPi systemd[1]: lnd.service: Service RestartSec=1min expired, scheduling restart.
Nov 29 10:56:47 zPi systemd[1]: lnd.service: Scheduled restart job, restart counter is at 946.
Nov 29 10:56:47 zPi systemd[1]: Stopped LND Lightning Daemon.
Nov 29 10:56:47 zPi systemd[1]: Starting LND Lightning Daemon...
Nov 29 10:56:47 zPi systemd[1]: Started LND Lightning Daemon.
Nov 29 10:56:47 zPi lnd[5315]: dial tcp <IP_ADDRESS>:9050: connect: connection refused
Nov 29 10:56:47 zPi systemd[1]: lnd.service: Main process exited, code=exited, status=1/FAILURE
Nov 29 10:56:47 zPi systemd[1]: lnd.service: Failed with result 'exit-code'.

In response to curl --socks5 localhost:9050 --socks5-hostname localhost:9050 -s https://check.torproject.org/ | cat | grep -m 1 Congratulations | xargs <== I removed the extra ")" at the end
... I get a line skip [no output]
So, pretty sure tor is not running and LND is pinging itself to death...

So there's no way to fix Tor?

Can you run the above to know if Tor is broken at all?

@rootzoll to double check ran the Tor update on a node which was not a fresh install, but updated to v1.6.2RC2 scripts. Got noe errors with lnd or else.
Finished running lintian.
# Stopping the tor.service before updating
# Update ...
(Reading database ... 107829 files and directories currently installed.)
Preparing to unpack tor_<IP_ADDRESS>-1~d10.buster+1_armhf.deb ...
Unpacking tor (<IP_ADDRESS>-1~d10.buster+1) over (<IP_ADDRESS>-1~d10.buster+1) ...
Setting up tor (<IP_ADDRESS>-1~d10.buster+1) ...
Something or somebody made /var/log/tor disappear.
Creating one for you again.
Processing triggers for systemd (241-7~deb10u4+rpi1) ...
Processing triggers for man-db (2.8.5-2) ...
# Starting the tor.service
# Installed Tor version <IP_ADDRESS>.
Starting the main menu ...

Can you run the above to know if Tor is broken at all?

What "above"?

@rootzoll to double check ran the Tor update on a node which was not a fresh install, but updated to v1.6.2RC2 scripts. Got no errors with lnd or else.

So, I've got some other "mix" of config and apps that's broken Tor? Perhaps that means I cannot fix the problem by removing or reinstalling tor (assuming I tried that)?
I can see how a clean restart is better, but it would be helpful to know what is broken :(

See just:
curl --socks5 localhost:9050 --socks5-hostname localhost:9050 -s https://check.torproject.org
can remove Tor with:
sudo apt remove tor
sudo apt purge tor
then
sudo apt install tor
Anyway the solution here which does not take a disproportionate amount of time and effort is to get an SDcard writer and flash a clean image.
The PATCH menu is recommended only to advanced users.

curl --socks5 localhost:9050 --socks5-hostname localhost:9050 -s https://check.torproject.org
results in no output.
Removing tor, I get this:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
	LANGUAGE = (unset),
	LC_ALL = (unset),
	LC_CTYPE = "UTF-8",
	LANG = "en_GB.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_GB.UTF-8").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
(Reading database ... 107852 files and directories currently installed.)
Removing tor (<IP_ADDRESS>-1~d10.buster+1) ...
Processing triggers for man-db (2.8.5-2) ...

How can I set local settings? I think that's an issue with Tor (see the log in my first comment).
I think I need to fix that before I try to reinstall Tor.

not sure, can try setting in
sudo raspi-config

Update: I tried (via sudo raspi-config) to edit local settings but got rejected:
Generating locales (this might take a while)...
  en_GB.UTF-8... done
  en_US.UTF-8... done
Generation complete.
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
	LANGUAGE = (unset),
	LC_ALL = (unset),
	LC_CTYPE = "UTF-8",
	LANG = "C"
    are supported and installed on your system
```.

The pi is very unhappy about locale :(
admin@zPi:~ $ sudo apt purge tor Reading package lists... Done Building dependency tree        Reading state information... Done The following package was automatically installed and is no longer required:   torsocks Use 'sudo apt autoremove' to remove it. The following packages will be REMOVED:   tor* 0 upgraded, 0 newly installed, 1 to remove and 2 not upgraded. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Y perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: 	LANGUAGE = (unset), 	LC_ALL = (unset), 	LC_CTYPE = "UTF-8", 	LANG = "en_GB.UTF-8"     are supported and installed on your system. perl: warning: Falling back to a fallback locale ("en_GB.UTF-8"). locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory (Reading database ... 107817 files and directories currently installed.) Purging configuration files for tor (<IP_ADDRESS>-1~d10.buster+1) ... Processing triggers for systemd (241-7~deb10u4+rpi1) ...

Seems there's an error caused by OSX setting locale!
https://askubuntu.com/questions/599808/cannot-set-lc-ctype-to-default-locale-no-such-file-or-directory

I turned off OSX's "interference" with locale, installed Tor and rebooted.
With curl --socks5 localhost:9050 --socks5-hostname localhost:9050 -s https://check.torproject.org
...I got a bunch of html (including "Congratulations. This browser is configured to use Tor.")
Now my screen says: Public null:8333 10 peers for Tor. Not sure if that's working?
And LND isn't running ;(
*** LND SYSTEMD STATUS ***
● lnd.service - LND Lightning Daemon
   Loaded: loaded (/etc/systemd/system/lnd.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Sun 2020-11-29 13:45:38 CET; 47s ago
  Process: 21642 ExecStartPre=/home/admin/config.scripts/blitz.systemd.sh log lightning STARTED (code=exited, status=0/SUCCESS)
  Process: 21648 ExecStart=/usr/local/bin/lnd --tor.active --tor.streamisolation --tor.v3 --listen=<IP_ADDRESS>:9735 ${lndExtraParameter} (code=exited, status=1/FAILURE)
 Main PID: 21648 (code=exited, status=1/FAILURE)

Ok, so LND cannot connect to Tor. Suggestions on how to configure that?
*** LND SYSTEMD STATUS ***
● lnd.service - LND Lightning Daemon
   Loaded: loaded (/etc/systemd/system/lnd.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Sun 2020-11-29 13:58:45 CET; 45s ago
  Process: 15372 ExecStartPre=/home/admin/config.scripts/blitz.systemd.sh log lightning STARTED (code=exited, status=0/SUCCESS)
  Process: 15374 ExecStart=/usr/local/bin/lnd --tor.active --tor.streamisolation --tor.v3 --listen=<IP_ADDRESS>:9735 ${lndExtraParameter} (code=exited, status=1/FAILURE)
 Main PID: 15374 (code=exited, status=1/FAILURE)

Nov 29 13:58:45 zPi systemd[1]: lnd.service: Main process exited, code=exited, status=1/FAILURE
Nov 29 13:58:45 zPi systemd[1]: lnd.service: Failed with result 'exit-code'.

*** LAST LND ERROR LOGS ***
sudo journalctl -u lnd -b --no-pager -n12
-- Logs begin at Sun 2020-11-29 13:49:33 CET, end at Sun 2020-11-29 13:59:31 CET. --
Nov 29 13:57:12 zPi systemd[1]: Started LND Lightning Daemon.
Nov 29 13:57:28 zPi lnd[13842]: unable to initialize tor controller: unable to connect to Tor server: dial tcp <IP_ADDRESS>:9051: connect: connection refused
Nov 29 13:57:28 zPi systemd[1]: lnd.service: Main process exited, code=exited, status=1/FAILURE
Nov 29 13:57:28 zPi systemd[1]: lnd.service: Failed with result 'exit-code'.
Nov 29 13:58:28 zPi systemd[1]: lnd.service: Service RestartSec=1min expired, scheduling restart.
Nov 29 13:58:28 zPi systemd[1]: lnd.service: Scheduled restart job, restart counter is at 5.
Nov 29 13:58:28 zPi systemd[1]: Stopped LND Lightning Daemon.
Nov 29 13:58:29 zPi systemd[1]: Starting LND Lightning Daemon...
Nov 29 13:58:29 zPi systemd[1]: Started LND Lightning Daemon.
Nov 29 13:58:45 zPi lnd[15374]: unable to initialize tor controller: unable to connect to Tor server: dial tcp <IP_ADDRESS>:9051: connect: connection refused
Nov 29 13:58:45 zPi systemd[1]: lnd.service: Main process exited, code=exited, status=1/FAILURE
Nov 29 13:58:45 zPi systemd[1]: lnd.service: Failed with result 'exit-code'.

On 1.6.1 fresh install on vm and running build_sdscard.sh
dial tcp <IP_ADDRESS>:9050: connect: connection refused
err='Tor tcp connection refused'

Should I post here or create a new issue? Haven't tried things mentioned above yet.

@adevoss please make a new issue. thx.

@tweetytoo if you have updated with PATCH from 1.6.0 this wont work without deleting lines form the config files and reinstalling Tor. Changing the password_B from the menu might work to as it is synchronising the Tor password accross the services.
But honestly just get a 10EUR SDcard writer and flash a clean image, you will need it to update later anyway.

@tweetytoo if you have updated with PATCH from 1.6.0 this wont work without deleting lines form the config files and reinstalling Tor. Changing the password_B from the menu might work to as it is synchronising the Tor password accross the services.

I will try the password change.

But honestly just get a 10EUR SDcard writer and flash a clean image, you will need it to update later anyway.

Ordered. I've learned my lesson. I'm just trying to "find the bug" but I agree that it may be weird/waste of time. I still have a few days to bang my head on the wall ;)
Thanks for the help!

I ended up flashing and replacing the microSD card with a new version of 1.6.1. Everything is working again.
Now I need to figure out how to update various packages without causing a conflict.

Use the UPDATE menu, just not the PATCH.


Fabric API Key and Fabric Build Secret are useless now

Hi,
Now that Firebase have integrated Fabric, Fabric API key and Build secret are useless when you try to only upload DSYM if you want to use beta however it's still useful can you decoupled these two features and allow us to only upload DSYM to firebase ?
Thanks,

Hy @mackoj
Thank you for the heads up, I created a task for the tooling team to investigate the issue.

Hello @mackoj,
We made the change in the release: https://github.com/bitrise-steplib/steps-fabric-crashlytics-beta-deploy/releases/tag/2.3.0
"Now it is only required to provide one of Fabric: API Key (api_key) or GoogleService-Info.plist path (service_info_plist_path) to upload dSYMs to Crashlytics, Fabric: Build Secret is optional.
In case using Firebase Crashlytics: to keep your historic crash data, provide your Fabric API key if you have migrated this app to Firebase. If you onboarded this app via Firebase provide GoogleService-Info.plist path.
Same to the previous releases set IPA file path (ipa_path) to empty string to only upload dSYMs, and skip Fabric Crashlytics Beta deploy feature."


Is Risa/Asir supported as an alternative underlying CAS?

At present one of the dependencies of GaNRAC is ox-asir or SageMath; however, neither of them natively (in other words, without something like WSL/Cygwin/MSYS2) supports Windows OS where my PC runs. Since the OpenXM homepage notes that the Risa/Asir (Kobe distribution) being developed by OpenXM committers can be installed on Windows machines directly, will GaNRAC provide immediate support for Risa/Asia (or another state-of-the-art CAS available on latest Windows platform without WSL/Cygwin/MSYS2/…) in future releases if possible?
Besides, I notice that GaNRAC appears to be a port of your previous SyNRAC for Go. The “Iwane17” given in qe.md mentions that SyNRAC can be downloaded freely at "http://www.fujitsu.com/jp/group/labs/resources/tech/announced-tools/synrac/", but unfortunately, this link seems to have expired and now I cannot find anything related to SyNRAC on Fujitsu's official website. As I mainly work with Maple as well as Mma (so regretfully, I have little knowledge of either Risa/Asir or Golang), I was wondering if the most recent SyNRAC is still obtainable online?

Sorry for the late reply.
I don't have a Windows OS environment, so I cannot provide support for Windows.


SPARKC-191 Get columns from dataframe when save to table

Build against Scala 2.11 finished with failure

Build against Scala 2.10 finished with failure

Build against Scala 2.10 finished with success

Build against Scala 2.11 finished with success

+1 Looks good.

+1


[Webportal Plugin] Upgrade marketplace plugin

Close #2630.
Support user to go through protocol jobs in marketplace without submitting job.

Here're some snapshots:

List view:

Grid view:

Coverage remained the same at 53.063% when pulling 3f8b68b8dbad86c6279c2591ac50b329c4f8807d on xiongyf/marketplace into a01d6b2606d58b6b745aaf05fb1ca7856b52b60a on master.

Coverage remained the same at 53.063% when pulling 3f8b68b8dbad86c6279c2591ac50b329c4f8807d on xiongyf/marketplace into a01d6b2606d58b6b745aaf05fb1ca7856b52b60a on master.


one proguard rule missing

Not sure if it's dependent on my code (I doubt it), but I had to add a proguard rule to make @ParcelConstructor work:
-keep class * implements android.os.Parcelable {
  public static final android.os.Parcelable$Creator *;
  public <init>(***);
}

I haven't run into a problem with the parcel constructor annotation and proguard... can you give me some evidence, like a quick sample project, that the proguard rule is required?

Closing due to inactivity.

Following snippet will crash at runtime with parceler and default proguard:
@Parcel(
    parcelsIndex = false
)
public class HomeScreen {
  HomeContentScreen _subscreen_content;
  HomeDrawerScreen _subscreen_drawer;

  public HomeScreen() {
    init();
  }

  @ParcelConstructor
  HomeScreen(HomeContentScreen _subscreen_content, HomeDrawerScreen _subscreen_drawer) {
    this._subscreen_content = _subscreen_content;
    this._subscreen_drawer = _subscreen_drawer;
  }
}

Related to @ParcelConstructor because the only purpose of this constructor is to unwrap object from parceler. It has no other links in the code, so proguard removes it.
I don't see any relation to parcelIndex = false but you might know better. It's used here because this class is generated by some other annotation processor.

Ah, great, this will give me something to investigate.  Will get back to you asap.

These rules (instead of the ones I listed on the README / website) worked for me... do they fix the issue for you @lukaspili?:
# Parceler configuration
-keep class **$$Parcelable { *; }
-keep class org.parceler.Parceler$$Parcels

Yes this configuration works too (in addition to the one provided by @cartierjf).

I'm updating the website and README with the following configuration:
-keep class **$$Parcelable { *; }

Please reopen if this is not enough.


Choose/Create Team on Signup

It might be a good idea to allow users to create/join a team when they signup, rather than having them submit another form after signup. Might just make it simpler

I’ll take a look into this sometime later, thus I’m assigning myself for now, I’ll unassign myself if O decide not to.


fused pharyngeal arches MP:0020350

fused pharyngeal arches MP:0020350
CURRENT DEF: failure of two or more arches to fully separate
Amend textual definition to include "pharyngeal"

Textual definition has been changed to: "failure of two or more pharyngeal arches to fully separate"


Update dependency shelljs to 0.8.5 [SECURITY]

This PR contains the following updates:

Package
Type
Update
Change

shelljs
dependencies
patch
0.8.4 -> 0.8.5

GitHub Vulnerability Alerts
GHSA-64g7-mvw6-v9qj
Impact
Output from the synchronous version of shell.exec() may be visible to other users on the same system. You may be affected if you execute shell.exec() in multi-user Mac, Linux, or WSL environments, or if you execute shell.exec() as the root user.
Other shelljs functions (including the asynchronous version of shell.exec()) are not impacted.
Patches
Patched in shelljs 0.8.5
Workarounds
Recommended action is to upgrade to 0.8.5.
References
https://huntr.dev/bounties/50996581-c08e-4eed-a90e-c0bac082679c/
For more information
If you have any questions or comments about this advisory:

Ask at https://github.com/shelljs/shelljs/issues/1058
Open an issue at https://github.com/shelljs/shelljs/issues/new

CVE-2022-0144
shelljs is vulnerable to Improper Privilege Management

Release Notes

shelljs/shelljs
v0.8.5
Compare Source
This was a small security fix for #1058.

Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

@balena-ci I self-certify!


add FanTop address

Thank you always for your support.
Following the content here, I have created a PR to add our service. I'd be happy if you could check it.
https://docs.blocto.app/blocto-sdk/javascript-sdk/flow/verified-transaction
Our Service FanTop
https://fantop.jp/
We are currently in the final stages of preparing for the transition to v2.

Hi @sone-md, please add your all related transactions and messages to this project. You can refer to https://github.com/blocto/flow-transactions/pull/43/files

@scottphc
Thank you for your confirmation. I've added a transaction, so please check it.
Since there are multiple testnet environments, I've decided to exclude them.

@sone-md you also need to add the message https://github.com/blocto/flow-transactions/pull/43/files#diff-28752302d8186f6037fcf0d341602d6d5930f4465fd029b6f7b87eb5eed635eaR1-R9. It will show the localized message to users for better user experience.
For example, transactions/FanTop/transfer_token.json can be:
{
  "arguments": ["id", "to"],
  "messages": {
    "en": "Transfer FanTop NFT to {to}",
    "ja": "YOUR JAPANESE TRANSLATION"
  }
}

@scottphc
How is this "message" displayed? If there are any documents or samples, please teach me. I set it at the time of transaction execution, but I could not confirm the display.
fcl.mutate({
      message: "FanTopトークンを格納するための保管庫を作成します",
      cadence,
      proposer: fcl.currentUser,
      limit: 1000,
    });

@sone-md I mean you can update this file transactions/FanTop/transfer_token.json
{
  "arguments": ["id", "to"],
  "messages": {
    "en": "Transfer FanTop NFT to {to}",
    "ja": "YOUR JAPANESE TRANSLATION"
  }
}

And once we merge and update it, the message Transfer FanTop NFT to 0x1234567890 will show up in the Blocto wallet.

@scottphc I've added a message. How does it look with this kind of image?


fix css-builder in node 6 or higher when config.dir is undefined

In node 6 or higher if path.dirname not receipt a string, throw a exception.
https://nodejs.org/dist/latest-v6.x/docs/api/path.html#path_path_dirname_path

+1

Looks similar to #235. Will review more detailed this weekend.

I am no longer maintaining this project, but if anyone is interested in doing that I will gladly provide access.


Override migrations

Since https://github.com/jeremykenedy/laravel-roles/commit/d137fee4270a9b465b1509e3dfcdcc7d3b9f574c package migrations get properly loaded. Since this is not optional (conditional) this cannot be prevented.
After publishing migrations with php artisan vendor:publish --tag=laravelroles-migrations it is not possible to migrate since it leads to a "Cannot declare class CreateRolesTable, because the name is already in use" error. In my case I was modifying the name of the migration file.
A possible solution would be to make loading of migrations optional (configurable from env file). Also when publishing the migrations let the user know they should disable it after publishing the migrations.

If the migrations are present after you publish them they will override them. The name of the file is important so it shouldn’t be changed.

I've got to change the filename. The date of the roles migration has to be in 2019, cannot be 2016.


installation error: about vc++10.0

hi, i do not know it is proper put here my puzzle  or not! when i install seqlearn, it shows error: "Microsoft visual c++ 10.0 is required(unable to find vcvarsall.bat)". but i install vc++2013 and vc++2008  on my laptop! i have searched a lot of forums but i have no idea what they say about it! so how to solve it!!??
thanks!!!

@larsmans I agree. I can suggest to use AppVeyor as maintainer of hmmlearn does, so to have always ready-to-use code and also prepared versions for Windows: https://github.com/hmmlearn/hmmlearn/issues/30 .


Next dashboard not available

After the last release, the new dashboard is not available anymore. Are you going to reset it?

It has been moved to the saleor-storefront repo.

It is saleor-dashboard 😉

To the saleor-dashboard repository, yes 🎉

I was thinking it was in the saleor-storefront. By the way, many thanks!


Add an option to automatically screenshot new collection log items

Since there's an option to display new collection log items as a chat message in osrs, I thought that it would be neat if runelite was able to automatically take a screenshot when that happens.
I hope whoever is reading this has a nice day!

#13625

Sorry for creating a duplicate issue!


OrientGraph.begin() does not increment TX nesting counter (2.1.x)

Any additional call of OrientGraph.begin() is ignored when there is a currently running TX, instead of delegating a call to ODatabaseDocumentTx, to increment TX nesting counter, to support TX propagation.
However OrientGraph.rollback() and OrientGraph.commit() decrements the counter, making the behavior inconsistent.
Here is the problematic piece of code:
// OrientTransactionalGraph.begin()
public void begin() {
  makeActive();

  final boolean txBegun = database.getTransaction().isActive();
  if (!txBegun) {
    database.begin();
    database.getTransaction().setUsingLog(settings.isUseLog());
  }
}

I think a decision needs to be made whether OrientGraph supports TX propagation the same way as ODatabaseDocumentTx, then make behavior consistent and provide better documentation.

Duplication of https://github.com/orientechnologies/orientdb/issues/5693

Fixed


Restore node labels for kube state metrics

How to categorize this PR?

/area monitoring
/kind enhancement
What this PR does / why we need it:
In upgrading kube-state-metrics to 2.5.0 from 1.9.7 in https://github.com/gardener/gardener/pull/6224, kubernetes metrics
labels were made optional. They now need to be allow-listed in ksm's
launch arguments.
Now we allow-list all of kubernetes' node labels to achieve the same result
as before.
Which issue(s) this PR fixes:
Fix worker group dropdown in "Node/Worker Pool Overview" dashboard.
Special notes for your reviewer:
/cc @istvanballok
Release note:

Fix worker group dropdown in "Node/Worker Pool Overview" dashboard.

/cherry-pick release-v1.53

/cherry-pick release-v1.54


Gray Filter for SVGs (Eclipse Icons) Not Working for Some Icons

I attempted to introduce a gray filter to my SVGs (Eclipse Icons) at runtime to give them a "disabled look". While this worked well for most icons, some did not get rasterized as expected. To investigate, I rasterized the faulty icons using Chrome, and it had no issues.
Unfortunately, I couldn't determine which specific combination of SVG elements causes the problem. Perhaps you can help identify the cause. Below, I’ve provided links to both the icons that work and those that don’t.
The Introduced Filter
I added the following filter as a new child element within the existing <defs> tag:
<filter id="disabledLook">
    <!-- Grayscale conversion -->
    <feColorMatrix type="saturate" values="0"/>

    <!-- Additional desaturation -->
    <feComponentTransfer>
        <feFuncR type="linear" slope="0.8" />
        <feFuncG type="linear" slope="0.8" />
        <feFuncB type="linear" slope="0.8" />
    </feComponentTransfer>

    <!-- Brightness and contrast adjustment -->
    <feComponentTransfer>
        <feFuncR type="linear" slope="0.8" intercept="0.1" />
        <feFuncG type="linear" slope="0.8" intercept="0.1" />
        <feFuncB type="linear" slope="0.8" intercept="0.1" />
    </feComponentTransfer>
</filter>

To activate this filter, I added the following property to the <svg> element:
filter="url(#disabledLook)"

Icons That Were Rasterized Successfully

start.svg
external_tools.svg

Icons That Failed (Filter Not Applied)

package_obj.svg
newclass_wiz.svg

Minimal reproducing version:
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16">
    <defs>
        <filter id="disabledLook">
            <!-- Grayscale conversion -->
            <feColorMatrix type="saturate" values="0"/>

            <!-- Additional desaturation -->
            <feComponentTransfer>
                <feFuncR type="linear" slope="0.8"/>
                <feFuncG type="linear" slope="0.8"/>
                <feFuncB type="linear" slope="0.8"/>
            </feComponentTransfer>

            <!-- Brightness and contrast adjustment -->
            <feComponentTransfer>
                <feFuncR type="linear" slope="0.8" intercept="0.1"/>
                <feFuncG type="linear" slope="0.8" intercept="0.1"/>
                <feFuncB type="linear" slope="0.8" intercept="0.1"/>
            </feComponentTransfer>
        </filter>
    </defs>
    <g filter="url(#disabledLook)">
        <rect fill="red" x="0%" y="0%" width="100%" height="100%"/>
        <g transform=""/>
    </g>
</svg>

Issue is due to incorrect computation of bounds of empty groups with a transform. I have a fix for this, but releasing it will take a bit as I am currently working on getting animation support to a releasable state.
If you remove all of the empty groups then the filter will work fine.
PS: You can simplify the filter by combining both component transfers into a single transfer with slop 0.64 and intercept 0.1

Thats great! Thanks a lot for this quick response. No worries with the fix, I will clean up the SVGs that are not working.


Uncaught TypeError: Object(...) is not a function

When using a component:

Hey @Real001,
can you provide some sample code, and steps to reproduce this error?

i get the same error, most likely this will be some dependancy issue,
i just ran
yarn add react-scroll-to
in the terminal and then imported ScrollTo in the file
import { ScrollTo } from "react-scroll-to";

Odd.
I tried installing react-scroll-to as a dependency for create-react-app, and I'm not seeing any errors.
What browser is this being testing on?
Can you provide sample code/project? (https://codesandbox.io/s/o5v2y5mk9q)

@ganderzz hey, I added my dependencies to the package.json, and now you'll be able to see the error.
https://codesandbox.io/s/9qyljzwjkr

This seems to be a React version issue--which I'm guessing comes from that we're using React.createContext(). Upgrading React to the latest version (16.6) fixes the issue. (https://codesandbox.io/s/1y0zkzv88l)
If it's just the context cause the issue it seems like a trivial fix we can get in. I'll be away for a few days so I'm open for PR's--if not I'll try to get a fix out sometime this week!

This has been fixed and deployed in v2.0.2 !
(https://codesandbox.io/s/n0p4j286nj)


Fix "first letter should be capitalised" linting errors

Linters are now checking if comments start with capital letters. This updates all comments to start with a capital letter.

Closing this as I'm not totally sure a blanket application of the linter rule is actually useful. There seems to be a 50/50 split where many of the valid lower case instances are referencing variable names.


Write unit tests for plotting.py

@exook I have been working in this issue for some time and made progress. However, I wished to clarify if we need to use any specific testing suite or is there any specified testing framework me must use for testing?
I have been using unittest  and the pytest framework. Is that fine?