Unable to load URL: http://<IP_ADDRESS>:52548/fredrik

I have the following in my Gemfile:
gem 'capybara', '1.0.0'
gem 'capybara-webkit', '1.0.0.beta4'
and this in my spec_helper.rb:
Capybara.javascript_driver = :webkit
running in a Ruby 1.9.2/Rails 3.0.9 app and get this when I run my JS RSpec acceptance tests:
Unable to load URL: http://<IP_ADDRESS>:52548/fredrik
I don't see the webkit driver starting. I've installed the non debug Cocoa OSX dmg. Any ideas?

I'm running into a similar issue. It looks like it may be caused by a Browser#reset! call capybara is making at the end of each spec while a redirect or request is still being processed.
Backtrace
Capybara::Driver::Webkit::WebkitInvalidResponseError:
  Unable to load URL: http://<IP_ADDRESS>:59583/projects
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/capybara-webkit-0.7.2/lib/capybara/driver/webkit/browser.rb:176:in `check'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/capybara-webkit-0.7.2/lib/capybara/driver/webkit/browser.rb:72:in `command'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/capybara-webkit-0.7.2/lib/capybara/driver/webkit/browser.rb:32:in `reset!'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/capybara-webkit-0.7.2/lib/capybara/driver/webkit.rb:88:in `reset!'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/capybara-1.1.1/lib/capybara/session.rb:70:in `reset!'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/capybara-1.1.1/lib/capybara/dsl.rb:87:in `block in reset_sessions!'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/capybara-1.1.1/lib/capybara/dsl.rb:87:in `each'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/capybara-1.1.1/lib/capybara/dsl.rb:87:in `reset_sessions!'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/capybara-1.1.1/lib/capybara/rspec.rb:16:in `block (2 levels) in <top (required)>'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/rspec-core-2.6.4/lib/rspec/core/example_group.rb:324:in `instance_eval'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/rspec-core-2.6.4/lib/rspec/core/example_group.rb:324:in `instance_eval_with_rescue'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/rspec-core-2.6.4/lib/rspec/core/hooks.rb:45:in `run_in'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/rspec-core-2.6.4/lib/rspec/core/hooks.rb:80:in `block in run_all'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/rspec-core-2.6.4/lib/rspec/core/hooks.rb:80:in `each'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/rspec-core-2.6.4/lib/rspec/core/hooks.rb:80:in `run_all'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/rspec-core-2.6.4/lib/rspec/core/hooks.rb:126:in `run_hook_filtered'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/rspec-core-2.6.4/lib/rspec/core/example_group.rb:226:in `eval_after_eachs'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/rspec-core-2.6.4/lib/rspec/core/example.rb:149:in `run_after_each'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/rspec-core-2.6.4/lib/rspec/core/example.rb:54:in `block in run'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/rspec-core-2.6.4/lib/rspec/core/example.rb:107:in `with_around_hooks'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/rspec-core-2.6.4/lib/rspec/core/example.rb:45:in `run'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/rspec-core-2.6.4/lib/rspec/core/example_group.rb:294:in `block in run_examples'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/rspec-core-2.6.4/lib/rspec/core/example_group.rb:290:in `map'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/rspec-core-2.6.4/lib/rspec/core/example_group.rb:290:in `run_examples'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/rspec-core-2.6.4/lib/rspec/core/example_group.rb:262:in `run'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/rspec-core-2.6.4/lib/rspec/core/example_group.rb:263:in `block in run'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/rspec-core-2.6.4/lib/rspec/core/example_group.rb:263:in `map'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/rspec-core-2.6.4/lib/rspec/core/example_group.rb:263:in `run'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/rspec-core-2.6.4/lib/rspec/core/command_line.rb:24:in `block (2 levels) in run'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/rspec-core-2.6.4/lib/rspec/core/command_line.rb:24:in `map'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/rspec-core-2.6.4/lib/rspec/core/command_line.rb:24:in `block in run'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/rspec-core-2.6.4/lib/rspec/core/reporter.rb:12:in `report'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/rspec-core-2.6.4/lib/rspec/core/command_line.rb:21:in `run'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/rspec-core-2.6.4/lib/rspec/core/runner.rb:80:in `run_in_process'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/rspec-core-2.6.4/lib/rspec/core/runner.rb:69:in `run'
# /home/ci/work/7bccc6267d45de0b/vendor/bundler/ruby/1.9.1/gems/rspec-core-2.6.4/lib/rspec/core/runner.rb:11:in `block in autorun'

Debug driver output
>> Find
>> 1
>> 493
>> .//a[./@href][(((./@id = 'Upload' or normalize-space(string(.)) = 'Upload') or ./@title = 'Upload') or .//img[./@alt = 'Upload'])] | .//input[./@type = 'submit' or ./@type = 'image' or ./@type = 'button'][((./@id = 'Upload' or ./@value = 'Upload') or ./@title = 'Upload')] | .//input[./@type = 'image'][./@alt = 'Upload'] | .//button[(((./@id = 'Upload' or ./@value = 'Upload') or normalize-space(string(.)) = 'Upload') or ./@title = 'Upload')] | .//input[./@type = 'image'][./@alt = 'Upload']
<< ok
<< 1
<< 2
>> Node
>> 2
>> 7
>> visible
>> 1
>> 2
<< ok
<< 4
<< true
>> Node
>> 2
>> 7
>> visible
>> 1
>> 2
<< ok
<< 4
<< true
>> Node
>> 2
>> 5
>> click
>> 1
>> 2
<< ok
<< 0
<<
>> Reset
>> 0
<< failure
<< 51
<< Unable to load URL: http://<IP_ADDRESS>:59583/projects

We can issue a user "Stop" request before resetting to see if that solves
the issue.

Actually, I was just able to reproduce this behavior with a "Find" command as well. I even inserted a ~60 sleep between the "Node.click" and "Find" calls, and still received the same failure. It seemed like that failure response was queued / held up, and then being sent after the next command, regardless of what it was:
>> click
>> 1
>> 2
<< ok
<< 0
<<
>> Find
>> 1
>> 7
>> .//body
<< failure
<< 51
<< Unable to load URL: http://<IP_ADDRESS>:33271/projects
>> Reset
>> 0
<< ok
<< 0
<<

After further investigation I realized our http://<IP_ADDRESS>:59583/projects request was a redirect after a POST within an iframe to accomplish async file uploads with remotipart 1.0.0. Once I changed the action handling the POST to respond with a small JSON response instead of redirecting, our tests completed successfully.
Our team was only seeing this issue on our CI machine:
ubuntu 2.6.35-30-generic
Qt 4.7.0
single core

We did not encounter the problem on our multicore OS X laptops with Qt 4.7.4
I can revert our fix to reproduce the issue if you think of anything you'd like me to try.

Hi, I am getting the same "Unable to load URL" errors after posting a form to update a resource. Is there any update on this? Thanks

Same for me. It started after upgrading my bundle to:
rspec 2.8.0
capybara-webkit 0.8.0
capybara 1.1.2
This error does not shows up everytime I ran my specs, only sometimes.

Hi tvdeyen,
Weird, for me it happened each time.
I am not sure of what "fixed" the issue for me in the end as it kinda disappeared with the combination of gems and perhaps some changes in the code that I had made.
Sorry not to be of much help. I wish I knew for sure what caused that problem.
Cheers
Vito

Seeing this as well.  Also intermittent, and nothing interesting to report in the logs.

Same error :(
capybara-webkit 0.10.0

We're working on ways to improve the feedback here, but in the meantime, here are a couple of suggestions:

Try tailing your test.log for a Rails app; frequently there are exceptions that get swallowed by the background server but end up in the log.
Try switching your driver to :webkit_debug. It prints all the commands it's sending to the webkit_server, which sometimes provides insight into what went wrong.

I found why it was failing in my case. It's easy to reproduce, here is test-case: https://gist.github.com/1926473
If fails when i'm changing iframe src dynamically during test.
Hope it helps!

I found one of cases when it failing: https://gist.github.com/1926473
It shows this error if one of the iframes on page is failed to load.
Hope it helps!

@buger thanks, that should help us fix at least one of the issues here. We'll look into that.

Is this still an issue in the latest version of capybara-webkit?

Don't think so; I haven't seen this problem in years.

Great! I'll close this. If anyone is still having these issues, please re-open this issue.

Still having this issue w/ filepicker.
Error:
Unable to load URL: http://<IP_ADDRESS>:9887/ because of error loading https://www.filepicker.io/dialog/comm_iframe/: Unknown error (Capybara::Webkit::InvalidResponseError)

Manifestation:
Manifests every time when run on a local development machine OSX 10.10.5 (14F27) but does not manifest consistently on CI. Working on trying to diagnose differences in those machines.
The URL we navigate to does result in a 302, so we may have some version of the redirect issue mentioned above. I'll confirm whether this manifests if we navigate directly to the resulting URL.
Dependency Versions:
qt 5.4.2 (installed via brew)

Gem Versions:
capybara 2.4.4
capybara-webkit 1.6.0

Debug Logs
Wrote response true ""
Received "Visit(http://<IP_ADDRESS>:9887/)"
Started "Visit(http://<IP_ADDRESS>:9887/)"
Load started
"Visit(http://<IP_ADDRESS>:9887/)" started page load
Started request to "http://<IP_ADDRESS>:9887/"
Finished "Visit(http://<IP_ADDRESS>:9887/)" with response "Success()"
Started request to "http://<IP_ADDRESS>:9887/some/application/path"
Received 302 from "http://<IP_ADDRESS>:9887/"
Started request to "http://<IP_ADDRESS>:9887/assets/application.css"
Started request to "http://<IP_ADDRESS>:9887/some/other.css"
Started request to "http://<IP_ADDRESS>:9887/assets/application.js"
Started request to "https://fast.fonts.net/jsapi/projectId.js"
Received 200 from "http://<IP_ADDRESS>:9887/some/application/path"
Received 200 from "http://<IP_ADDRESS>:9887/assets/application.js"
Received 200 from "http://<IP_ADDRESS>:9887/assets/application.css"
Received 404 from "http://<IP_ADDRESS>:9887/some/other.css"
Received 200 from "https://fast.fonts.net/jsapi/projectId.js"
Started request to "http://<IP_ADDRESS>:9887/assets/image.png"
Started request to "https://www.filepicker.io/dialog/comm_iframe/"
Started request to "http://<IP_ADDRESS>:9887/user/generated/image.png"
Received 200 from "http://<IP_ADDRESS>:9887/assets/image.png"
Received 200 from "http://<IP_ADDRESS>:9887/user/generated/image.png"
Started request to "http://fast.fonts.net/t/1.css?apiType=js&projectid=projectId"
Received 200 from "http://fast.fonts.net/t/1.css?apiType=js&projectid=projectId"
Received 0 from "https://www.filepicker.io/dialog/comm_iframe/"
Page finished with false
Load finished
Page load from command finished
Wrote response false "{"class":"InvalidResponseError","message":"Unable to load URL: http://<IP_ADDRESS>:9887/ because of error loading https://www.filepicker.io/dialog/comm_iframe/: Unknown error"}"


Dockerize the server

For ease of deployment and better isolation it is better to dockerize the server.

Done


dropping support for GCM, bumping web drivers

GCM has been deprecated and support has now been removed. Had to bump chromedriver to 75, dropping support for the unstable branch. Not sure if this is the preferred way to go about it, but I'm not sure how to support multiple driver versions otherwise and this is a limitation of chromedriver 75 as far as I can tell.

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.
What to do if you already signed the CLA
Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ Googlers: Go here for more info.

I signed it!

Anything more needed from me to get this merged and functional I am all ears for! Please let me know!


Docker authentication to private registry fails since 1.3.4

I have upgraded to 1.3.4 to benefit from the flag googleContainerRegistryEnabled, but I encounter the following exception:
[ERROR] Failed to execute goal com.spotify:dockerfile-maven-plugin:1.3.4:push (push-docker-image) on project sample: Could not push image: no basic auth credentials -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.spotify:dockerfile-maven-plugin:1.3.4:push (push-docker-image) on project sample: Could not push image
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
	at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
	at org.jvnet.hudson.maven3.launcher.Maven33Launcher.main(Maven33Launcher.java:129)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238)
	at jenkins.maven3.agent.Maven33Main.launch(Maven33Main.java:176)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:139)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:70)
	at hudson.remoting.UserRequest.perform(UserRequest.java:153)
	at hudson.remoting.UserRequest.perform(UserRequest.java:50)
	at hudson.remoting.Request$2.run(Request.java:336)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.maven.plugin.MojoExecutionException: Could not push image
	at com.spotify.plugin.dockerfile.PushMojo.execute(PushMojo.java:90)
	at com.spotify.plugin.dockerfile.AbstractDockerMojo.tryExecute(AbstractDockerMojo.java:227)
	at com.spotify.plugin.dockerfile.AbstractDockerMojo.execute(AbstractDockerMojo.java:216)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
	... 31 more
Caused by: com.spotify.docker.client.exceptions.DockerException: no basic auth credentials
	at com.spotify.plugin.dockerfile.LoggingProgressHandler.handleError(LoggingProgressHandler.java:105)
	at com.spotify.plugin.dockerfile.LoggingProgressHandler.progress(LoggingProgressHandler.java:63)
	at com.spotify.docker.client.ProgressStream.tail(ProgressStream.java:74)
	at com.spotify.docker.client.DefaultDockerClient.push(DefaultDockerClient.java:1291)
	at com.spotify.docker.client.DefaultDockerClient.push(DefaultDockerClient.java:1271)
	at com.spotify.plugin.dockerfile.PushMojo.execute(PushMojo.java:88)
	... 35 more

I have a quite standard config.json:
{
	"auths": {
		"nexus-fabfonc.localdomain:5000": {
			"auth": "YWRtaW46YWRtaW4xMjM="
		},
		"nexus-fabfonc.localdomain:5001": {
			"auth": "YWRtaW46YWRtaW4xMjM="
		}
	}
}

I have also tested with a duplicated one like below with and without protocols as I stumbled on old issues linked to that problem, but with no more success, idem with only protocol suffixed ones:
{
	"auths": {
		"http://nexus-fabfonc.localdomain:5000": {
			"auth": "YWRtaW46YWRtaW4xMjM="
		},
		"http://nexus-fabfonc.localdomain:5001": {
			"auth": "YWRtaW46YWRtaW4xMjM="
		},
		"nexus-fabfonc.localdomain:5000": {
			"auth": "YWRtaW46YWRtaW4xMjM="
		},
		"nexus-fabfonc.localdomain:5001": {
			"auth": "YWRtaW46YWRtaW4xMjM="
		}
	}
}

I thinks that it is linked to the upgrade of the Docker client from 8.8.0 to 8.8.1 introduced by c295836810b9ad80c00361daf3bcf702d967e2d0 to resolve #23. I suspect more specifically the commit https://github.com/spotify/docker-client/commit/c29e44bc986d108b40862ee0b540b7a943f9c424.

Small problem, we haven't HTTPS on the target internal server :-/. I am hardly working to get it set up. Thanks for the hint though.

+1
Using an unsecured private Nexus 3 (http).
I had to go back to v1.3.3 (and ~/.docker/config.json without transfer protocol)

+1
Using an amazon container registry and auth failed with the above error for 1.3.5. Rolling back to 1.3.3 worked.

+1
I'm using Jenkins pipeline withDockerRegistry with Nexus3 private http repository. This issue is realling disturbing my builds.

Same issue here using Gitlab CI build pipelines as well.
I'll stick with version 1.3.3 for now otherwise my build will break...

1.3.6 with settings.xml server authentication works very well for me.
Em 23 de set de 2017 16:31, "Tim van Baarsen"<EMAIL_ADDRESS>escreveu:

Same issue here using Gitlab CI build pipelines as well.
I'll stick with version 1.3.3 for now otherwise my build will break...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/spotify/dockerfile-maven/issues/62#issuecomment-331664874,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABQuOOuPcJEGk8BLdWip0ah1UeSzHd-Rks5slVyHgaJpZM4O4_xL
.

+1
We're using AWS ECR, doing eval $(aws ecr get-login ...) prior to mvn deploy and get the same error with 1.3.6. Tried 1.3.3 as suggested by @bigtoast and this works.

so the thing looks really broken.
Requiring a dot in the hostname is something that should be documented.
Considering the spotify use cases this is understandable though.
But then it becomes impossible when using local insecure-registries.
Which I think makes totally sense in networks without an internet connection!
If I specify the protocol the ImageRef parser fails.
If I dont specify the protocl HTTPS get chosen....
so no way to get this going.
I try maven auth now.

So I found a super messy workaround:
I still can use the simple host insecure docker registry (our local nexus server).
BUT I need to add a fake authentication line to the .docker/config.json by copying the authentication line from the real server and replacing the host with the default docker repo like so:
"auths": {
		"my-local-nexus-host": {
			"auth": "XXXXXXXXXXXXXXXXXXX"
		},
		"https://index.docker.io/v1/": {
			"auth": "XXXXXXXXXXXXXXXXXXX"
		},
}

Same  problem for me, I stick to 1.3.3 until it is solved.

Note that while docker-client:8.10.0 fixes the problem, there are other classpath issues if you try to use docker-client:8.11.0 due to other refactoring between libraries.  So stick with 8.10.0.

I use gitlab-ci and sonatype nexus 3, dockerfile 1.3.6
Thanks to @mryan43 for the docker-client hint
secret variables are defined in gitlab: DOCKER_PUSH_USER and DOCKER_PUSH_PASS
I know the excerpt below is not MWE, but maybe it still helps someone to work around this issue
.gitlab-ci.yml:
build:
  image: openjdk:8-jdk
  stage: build
  script:
    - ./mvnw -B  -s .ci/settings.xml clean install deploy site-deploy

.ci/settings.xml
<servers>
    <server>
        <!-- for docker push -->
        <id>docker.nexus.somewhere</id>
        <username>${env.DOCKER_PUSH_USER}</username>
        <password>${env.DOCKER_PUSH_PASS}</password>
    </server>
</servers>

pom.xml
<project>
    <build>
        <plugins>
            <plugin>
                <groupId>com.spotify</groupId>
                <artifactId>dockerfile-maven-plugin</artifactId>
                <version>1.3.6</version>
                <executions>
                    <execution>
                        <id>default</id>
                        <goals>
                            <goal>build</goal>
                            <goal>push</goal>
                        </goals>
                        <configuration>
                            <tag>${project.version}</tag>
                        </configuration>
                    </execution>
                    <execution>
                        <id>push-as-latest</id>
                        <configuration>
                            <tag>latest</tag>
                        </configuration>
                        <goals>
                            <goal>build</goal>
                            <goal>push</goal>
                        </goals>
                    </execution>
                </executions>
                <configuration>
                    <repository>docker.nexus.somewhere/someone/something</repository>
                    <buildArgs>
                        <JAR_FILE>${project.build.finalName}.jar</JAR_FILE>
                    </buildArgs>
                    <useMavenSettingsForAuth>true</useMavenSettingsForAuth>
                </configuration>
                <dependencies>
<!-- from https://github.com/spotify/dockerfile-maven/issues/62#issuecomment-356368099 -->
                    <dependency>
                        <groupId>com.spotify</groupId>
                        <artifactId>docker-client</artifactId>
                        <classifier>shaded</classifier>
                        <version>8.11.1</version>
                    </dependency>
                </dependencies>
            </plugin>
        </plugins>
    </build>
</project>

The issue still exists at 1.3.7, even with the docker config without https/http. The aforementioned version (1.3.3) works as expected without any changes in Docker client.

Thanks @lazam for the workaround.
I confirm that works with 1.3.3 and do not work with 1.3.7

had to revert to 1.3.3 to use AWS again as well.

Forcing the plugin to use docker client latest release (8.11.2) fixed ecr login issues to me

@mmiglier Were you successful shading to the 8.11.2 docker client using plugin version 1.4.0 or an older version?

Using 1.4.0

Il giorno 09 apr 2018, alle ore 23:03, Terry Schutte<EMAIL_ADDRESS>ha scritto:
@mmiglier Were you successful shading to the 8.11.2 docker client using plugin version 1.4.0 or an older version?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks.  Seems none of these combinations are working for me on 1.4.0 and newer docker clients (on linux).  For now I've successfully reverted to 1.3.3 as well.

The solution suggested by @mmiglier  works for me using credentials into the pom.xml on the version 1.4.0

1.4.10 is still failing to push to ecr, and the above workaround is not working anymore. Rolling back to 1.4.0 + docker-client 8.11.2

Same problem with my configuration :
plugin version 1.4.10
docker-client:
Client:
Version:           18.09.7
API version:       1.39
Go version:        go1.10.8
Git commit:        2d0083d
Built:             Thu Jun 27 17:56:23 2019
OS/Arch:           linux/amd64
Experimental:      false


webots_ros2: 1.1.2-2 in 'galactic/distribution.yaml' [bloom]

Increasing version of package(s) in repository webots_ros2 to 1.1.2-2:

upstream repository: https://github.com/cyberbotics/webots_ros2.git
release repository: https://github.com/ros2-gbp/webots_ros2-release
distro file: galactic/distribution.yaml
bloom version: 0.10.7
previous version for package: 1.0.6-2

Missing a .git in the command.


Appendix Update/First Complete Draft

This PR is dependent upon the writing checklist PR, #14.  There aren't any changes to the main body of the document that aren't already in that PR, so you can skip them.
Thanks!

Hello @katyhuff and @munkm ! new draft

Great job with the updates you've made! I am still reviewing, but am giving you my suggestions so far so you can work on them Monday before our meeting. I will send the rest Monday sometime. first part of review

Ok here's my (full review)[https://drive.google.com/file/d/1r5wKkl6KM9nkspMxAaQ60mbxdOLO30Al/view?usp=sharing]

Hello @munkm and @katyhuff !  The new draft I just uploaded should answer most if not all of @munkm 's review!  Happy (late) Thanksgiving!

Hello @munkm and @katyhuff ! The most recent push fixes an error in a figure label that was preventing latex from referencing it properly.  I am also uploading this version for Kristie to see on box.

Thank you @ZoeRichter . I will try to reread this again over the weekend.

Can you post an updated PDF with these fixes?

New Draft It should have automatically updated in the appendix branch, but here is the direct link.

Hello @munkm!  The updated draft can be found in the appendix branch here

Hello @munkm !  I've just pushed the updated draft to the repo, and you can find it here.


Allow basic query param configuration

As an alternative to the config file, allow configuration of a "clean" exporter that will receive its configs from Prometheus itself (through URL query params), the same way blackbox exporter does it.
With this configuration, only a single exporter scrape_config will be supported, since Prometheus' scrape_config params section allows only strings or string arrays. There may be multiple endpoints but they all will be scraped with the same XPath query, for instance. Still, this should cover a couple of use cases and might make the exporter configuration easier.
Sample Prometheus config with this implementation:
scrape_configs:
  - job_name: 'wikipedia-exporter'
    metrics_path: /probe
    params:
      selector: "//div[@id='mw-content-text']//tr[@class='mw-statistics-articles']/td[@class='mw-statistics-numbers']/text()"
      decimal_point_separator: ","
      thousands_separator: " "
      metric_name: wikipedia_articles_total
      metric_type: gauge
      metric_help: "Total of articles available at Wikipedia"
    static_configs:
      - targets:
        - https://fr.wikipedia.org/wiki/Special:Statistics
        - https://pt.wikipedia.org/wiki/Especial:Estat%C3%ADsticas
    relabel_configs:
      - source_labels: [__address__]
        target_label: __param_target
      - source_labels: [__param_target]
        target_label: instance
      - target_label: __address__
        replacement: <IP_ADDRESS>:9883  # The html-exporter's real hostname:port.

Note that in this configuration we lose the ability to configure labels and individual decimal and thousands separators.

TODO:
[ ] Param validation
[ ] Use configs from query
[ ] ????
[ ] Profit


[FLINK-25398] Show complete stacktrace when requesting thread dump

What is the purpose of the change
Now the stacktrace is not complete when clicking the task executor's threaddump  in runtime webui. Hence it's hard to the initial calling according to the stacktrace.
Now the thread stacktrace is limited to 8, refer to openjdk:
https://github.com/openjdk/jdk/blob/master/src/java.management/share/classes/java/lang/management/ThreadInfo.java#L597
Solution
Using the custom stringify method to return stacktrace instead of using ThreadInfo.toString directly
Verifying this change
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@xintongsong
Hi, could you help recheck this feature? Do community need this feature? If yes, i will go ahead.

@tillrohrmann If you have time, could you help review it. Thanks

@tillrohrmann Thanks again for your kind and patience.
By the way, could you help review #18157 ?


Options to allow scoping during firearm action.

Description
Currently while the firearm action is playing during like a sniper/shotgun rechamber, you either cannot scope in, or you are locked in scoping until the firearm action is done.
It would be nice to have the option for guns to be able to scope in/out while the firearm action is playing, because it really hinders with snipers/shotguns right now.
Configuration
Firearm_Action:
  Allow_Scoping: <true/false>

Payment (optional)

[ ] I'm willing to pay for this feature

Logically you should be able to scope in & out even while performing firearm actions / reload


Updated run_forseti.sh

Issue: #1025

Thanks for improving this!
You can do a set -x early on in the script, then it will log the commands it's running to stdout (console in this case). That way you won't have to do the echo running command x -y=a.
I'd also switch to using logger instead of echo that way the messages get logged to syslog/messages and can be picked up by stackdriver (agent).


Astyx to Kitti Format

@kathy-lee Hello, I saw your discussion with wzan0001 on the project Astyx-radar-dataset-convert-to-kitti-format, and you seem to have a wonderful version with normalization and other encountered problems. Could you please send your improved version to me? My email address is<EMAIL_ADDRESS>Thanks a lot!

Hi @ZhuyunZhou ,
thanks for your interest. This project aims to visualize the sensor data of Astyx dataset and its annotations. The scripts can run on raw dataset without problem for me. Can you mention some detail about your issue?

@kathy-lee Hello, Thank you for your reply. In fact, I'm asking for your help with converting Astyx data to Kitti format. I just mentioned you on the page https://github.com/wzan0001/Astyx-radar-dataset-convert-to-kitti-format/issues/2, in case you may want to go through your discussion with wzan0001 in December 2019. After seeing your visualization work of Astyx and others, I believe you are really expert in this dataset and radar. And I'm even more interested in your improved version of the formatting issue. Thank you!

@kathy-lee Hello, i found your project and its been really helpfull so thank you for sharing. I was wondering if you have worked on point2 using this dataset i have trying to figure out a way to put it into that network and im not successful so is there any suggestion for me.

@kathy-lee Hello, i found your project and its been really helpfull so thank you for sharing. I was wondering if you have worked on pointnet++ using this dataset i have been trying to figure out a way to put it into that network and im not successful so is there any suggestion for me.

@manojpremsm Hello, what is your goal of using pointnet++ with this dataset, segmentation or classification or object detection? I have tried point segmentation with pointnet++ using this dataset, the lidar data could get reasonable performance.

@kathy-lee I wanted to classification and object detection first and then maybe segmentation.i will trying it on radar point cloud . Do u have a repo which I can check out??. Im have been stuck and unable to put this data set in the format so that it can fed into the pointnet++ network. It would be really helpful if u could share how you transformed this data set into the form where it can be used in point net ++

@kathy-lee  thank you for your response.
I wanted to do classification and object detection first and then maybe segmentation.i will be trying it on radar point cloud . Do you have a project repository which I can check out your implementation. It would be of great help because  I have been stuck and unable to put this data set in the format so that it can fed into the pointnet++ network. It would be really helpful if you could share how you transformed this data set into the form where it can be used in point net ++ or pointnet.

Hi @manojpremsm, I don't know which pointnet(++) code you're working on, so I cannot get which kind of problem you are stuck with, that's better if you can give some more detail info of your problem. Or you can check out my repo which implemented data interface(for this dataset) and pointnet segmentation: https://github.com/kathy-lee/astyx-pcdet. You don't need to do any data transform when you put it as input to pointnet(++), just feed it with point cloud: (x,y,z,other features...)*N.


bug fixes

Type

[X] Bug Fix: $servermfaLevel
[ ] Functions: <Function Name>
[ ] Callbacks: <Callback Name>
[ ] Handlers: <Handler Type>
[ ] Others: ______

Dependencies (Third Party Modules) needed: <Name | Github Link> (Maximum: 20MB~ size)
Want a credit? Discord tag or other social media link: <DiscordTag | OtherSocialMediaLink>
Referenced Issue: #393
Description
fixed $serverMfaLevel

There will be no more updates.


Trouble with Gradle

When i add you lib and build project - memory usage grows to up. In my project i have several libs
 compile 'com.android.support:design:22.2.0'
    compile 'com.android.support:appcompat-v7:22.2.0'
    compile 'com.android.support:recyclerview-v7:22.2.0'
    compile 'com.squareup.retrofit:retrofit:1.9.0'
    compile 'com.google.code.gson:gson:1.7.2'
    compile 'org.parceler:parceler-api:0.1.0'
    compile 'com.squareup.picasso:picasso:2.5.2'
    compile 'com.github.hotchemi:android-rate:0.4.3'
    compile 'com.hannesdorfmann:swipeback:1.0.0'
    compile 'com.makeramen:roundedimageview:2.1.0'

but when i add you lib its more time write - Building gradle....

This is simply because the lib depends on the AspectJ compiler to compile all the classes you have annotated;therefore it's injecting the code at compile time.So this will indeed take a bit more time.


Reproducing results Fig.5

Hello,
I am currently trying to reproduce the results given in Fig 5 (b) and (c), in "not finetuned" mode.
Here is my conf for the GFLOPs level of 3, Stage 3 not finetuned:
TRAIN:
  ENABLE: False

TEST:
  ENABLE: True
  DATASET: ImageNet
  BATCH_SIZE: 1024
  CHECKPOINT_FILE_PATH: "/root/workspace/projects/ATS/models/deit_small_patch16_224-cd65a155.pth"
  NUM_ENSEMBLE_VIEWS: 1
  NUM_SPATIAL_CROPS: 1
  SAVE_RESULTS_PATH: "/root/no_backup/preds_ats.pkl"

DATA:
  PATH_TO_DATA_DIR: "/datasets_local/ImageNet/"
  TEST_CROP_SIZE: 224
  TRAIN_CROP_SIZE: 224
  MEAN: [0.485, 0.456, 0.406]
  STD: [0.229, 0.224, 0.225]

DATA_LOADER:
  NUM_WORKERS: 2

VIT:
  IMG_SIZE: 224
  PATCH_SIZE: 16
  IN_CHANNELS: 3
  NUM_CLASSES: 1000
  EMBED_DIM: 384
  DEPTH: 12
  NUM_HEADS: 6
  MLP_RATIO: 4.0
  QKV_BIAS: True
  QK_SCALE: None
  REPRESENTATION_SIZE: None
  DROP_RATE: 0.0
  ATTN_DROP_RATE: 0.0
  DROP_PATH_RATE: 0.0
  HYBRID_BACKBONE: None
  NORM_LAYER: None
  ATS_BLOCKS: [3]
  NUM_TOKENS: [108, 108, 108, 108, 108, 108, 108, 108, 108, 108, 108, 108]
  DROP_TOKENS: True

NUM_GPUS: 1

And here is my conf for the GFLOPs level of 3, Multi-stage not finetuned:
TRAIN:
  ENABLE: False

TEST:
  ENABLE: True
  DATASET: ImageNet
  BATCH_SIZE: 1024
  CHECKPOINT_FILE_PATH: "/root/workspace/projects/ATS/models/deit_small_patch16_224-cd65a155.pth"
  NUM_ENSEMBLE_VIEWS: 1
  NUM_SPATIAL_CROPS: 1
  SAVE_RESULTS_PATH: "/root/no_backup/preds_ats.pkl"

DATA:
  PATH_TO_DATA_DIR: "/datasets_local/ImageNet/"
  TEST_CROP_SIZE: 224
  TRAIN_CROP_SIZE: 224
  MEAN: [0.485, 0.456, 0.406]
  STD: [0.229, 0.224, 0.225]

DATA_LOADER:
  NUM_WORKERS: 2

VIT:
  IMG_SIZE: 224
  PATCH_SIZE: 16
  IN_CHANNELS: 3
  NUM_CLASSES: 1000
  EMBED_DIM: 384
  DEPTH: 12
  NUM_HEADS: 6
  MLP_RATIO: 4.0
  QKV_BIAS: True
  QK_SCALE: None
  REPRESENTATION_SIZE: None
  DROP_RATE: 0.0
  ATTN_DROP_RATE: 0.0
  DROP_PATH_RATE: 0.0
  HYBRID_BACKBONE: None
  NORM_LAYER: None
  ATS_BLOCKS: [3, 4, 5, 6, 7, 8, 9, 10, 11]
  NUM_TOKENS: [108, 108, 108, 108, 108, 108, 108, 108, 108, 108, 108, 108]
  DROP_TOKENS: True

NUM_GPUS: 1

However I am not able to reach the Top1-Accuracy you indicate in these figures. Could you please provide the config files leading to the creation of Fig5 (b) and (c) please ?
Thank you in advance !

replace n_ref_tokens with n_tokens：
ys = self.create_ys(normalized_cdf, n_tokens).unsqueeze(
dim=2
)
replace N with n_tokens -1：
unique_indices = self.get_unique_indices(indices=tokens_to_pick_ind, max_value=n_tokens - 1)[:, : n_tokens - 1]

1 replace n_ref_tokens with n_tokens：
ys = self.create_ys(normalized_cdf, n_tokens).unsqueeze(
            dim=2
        )

2 replace N with n_tokens：
 unique_indices = self.get_unique_indices(indices=tokens_to_pick_ind, max_value=n_tokens - 1)[:, : n_tokens - 1]

Thanks for your answer !

Hi, i am interested in this project. I have a question. Why the number of tokens set a constant in the config file? Can the ATS module reduce it in such setting? Thanks!

Hi, @chloeskt . I replaced the code in ats_block.py as @cuguniang's comment. Though the code could run without any errors, I still could not reproduce the results given in Fig 5 (c).
I ran the testing with batchsize = 1, 1024, and NUM_TOKENS= 1.0, 0.87, 171 (for NUM_TOKENS <= 1.0, it would be view as ratio). And the results are:
batchsize=1,  NUM_TOKENS=1.0,   top1_acc = 77.05%
batchsize=1,  NUM_TOKENS=171, top1_acc =  74.52%
batchsize=1024,  NUM_TOKENS=1.0,   top1_acc =  78.34%
batchsize=1024,  NUM_TOKENS=0.87, top1_acc =  58.75%
Have you sucessfully reproduced the result?
Thank you.


[Vue warn]: Failed to resolve component: v-shell

Hi Salah, am trying to follow your example and use v-shell but am getting this error can you help


Added Full stops to comments

There were inconsistencies as some comments had full stops and some did not

Thanks for this patch, however there are hundreds of comments without dots and I don't think it's worth to create bulk updates for them.


[CT-1090] [Bug] dbt.type_timestamp() is not working using dbt 1.2.1

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
Using dbt.type_timestamp() I get,
dict object' has no attribute 'type_timestamp
but it works using type_timestamp(). dbt.<macro>() works for others though.
Expected Behavior
I expected dbt.type_timestamp() to work flawlessly :smi
Steps To Reproduce
Using 1.2.1, try
select
    cast(my_column as {{ dbt.type_timestamp() }})
from
    my_model

Relevant log output
'dict object' has no attribute 'type_timestamp'

Environment
- OS: Mac OS 12.51
- Python: 3.9
- dbt: 1.2.1

Which database adapter are you using with dbt?
postgres, snowflake, bigquery
Additional Context
No response

In order to reproduce this:

Custom generic test definition that references a dbt.* macro that was moved from dbt_utils
A version of the dbt_utils package installed with backwards compatibility (= same macro in the dbt_utils namespace, dispatching into the dbt namespace)

Why generic tests? For parsing speed, dbt constructs slimmer rendering contexts when parsing generic tests. It attempts to include just the macros that are called (depended on by) the generic test definition... and any macros those macros depend on, and so on. The dict object' has no attribute 'type_timestamp' error really means, for whatever reason, dbt isn't capturing that dependency, and including type_timestamp as a macro within the dbt namespace when parsing that generic test. (The dbt macro namespace is treating as a dictionary during macro resolution.)
If the package is installed, for whatever reason, dbt is resolving {{ type_timestamp() }} to point to dbt_utils.type_timestamp instead of dbt.type_timestamp. I'm not sure why—in general, only root project macros should get that kind of "global" priority; macros from packages should not—but in any case, dbt_utils.type_timestamp then redirects to dbt.type_timestamp, and all is well with the world.
In any case, it's possible to avoid this error by:

referencing it just as type_timestamp in the generic test definition (or removing the test / the macro call entirely)
uninstalling dbt_utils :)

In an ideal world, our macro dispatching/resolution order wouldn't yield this surprising outcome! I think the code involved here is pretty gnarly. IIRC it's around here:
https://github.com/dbt-labs/dbt-core/blob/5f59ff12549a035ce8be40bbb3b821db68a61870/core/dbt/context/macros.py#L128-L148
Workaround: Never use a dbt.* prefix ... for macros migrated from a package while also having a backwards-compatible of that package installed.
In a weird way, this issue (in its narrowest sense) will be fixed when dbt_utils removes that backwards compatibility. But we do risk running into this again in the future when we perform other package → core macro migrations.

Taking another look here, since we might want to consider recommending dbt.* as the go-forward standard, instead of calling utility macros out of the global namespace, and this bug is a big scary thing standing in our way.
Repro case
-- macros/some_test.sql
{% test some_test(model) %}
  select cast(current_timestamp as {{ dbt.type_timestamp() }})
  limit 0
{% endtest %}

-- models/some_model.sql
select 1 as id

# models/config.yml
version: 2
models:
  - name: my_model
    tests:
      - some_test

# packages.yml
packages:
  - package: dbt-labs/dbt_utils
    version: 0.9.2
# note that removing this, removes the bug!

$ dbt deps
$ dbt parse
...
dbt.exceptions.CompilationException: Compilation Error in test some_test_my_model_ (models/config.yml)
  'dict object' has no attribute 'type_timestamp'

  > in macro test_some_test (macros/custom_test.sql)
  > called by test some_test_my_model_ (models/config.yml)

Big idea, restated
We build a special context for generic test parsing that contains only the macros we think are necessary. That happens in these funky methods:
https://github.com/dbt-labs/dbt-core/blob/49ecd6a6a45c209857e23171f4c70d1c16a74304/core/dbt/context/providers.py#L1530-L1552
https://github.com/dbt-labs/dbt-core/blob/49ecd6a6a45c209857e23171f4c70d1c16a74304/core/dbt/context/macro_resolver.py#L130-L173
The problem: When dbt_utils is installed, dbt thinks that the generic test macro depends on dbt_utils.type_timestamp, instead of dbt.type_timestamp. So dbt_utils.type_timestamp shows up in the special test-parsing rendering context, whereas dbt.type_timestamp is missing, leading to the awkward error. (Yes, this error should also probably be better!)
This is the spot where we're saying that some_test depends on dbt_utils.type_timestamp, instead of dbt.type_timestamp:
https://github.com/dbt-labs/dbt-core/blob/49ecd6a6a45c209857e23171f4c70d1c16a74304/core/dbt/parser/manifest.py#L539
ipdb> possible_macro_calls
['dbt.type_timestamp']
ipdb> dep_macro_id
'macro.dbt_utils.type_timestamp'

Why? Because our macro resolution logic, which has special logic in case a specific package namespace has been specified, does not use said logic if the specified package namespace is an "internal" namespace (dbt):
https://github.com/dbt-labs/dbt-core/blob/49ecd6a6a45c209857e23171f4c70d1c16a74304/core/dbt/context/macro_resolver.py#L110-L120
Precise fix: Add logic to get_macro that prefers macros defined in the dbt namespace, if a macro has been called as dbt.some_macro. This... makes sense to me!
Blunt fix (risks a performance hit): Just always include all macros from the dbt namespace in namespace for generic test parsing
The precise fix could maybe be a breaking change for people who have been depending on funky/undocumented behavior around resolution order for global macros — namely, that my root project's create_table_as() will always "win" whenever create_table_as() or dbt.create_table_as() is called. For the latter case, dispatch makes it possible to do this more clearly and explicitly, and I'm inclined to say it's the direction we should head in.


Closing a whitelisting notification blacklists the project directory

Open a file which is not whitelisted and not yet blacklisted
The VSCode plugin will show a notification which has a Close button
A click on close blacklists the project dir ("C:\users\jansorg" in my case) but it should blacklist the current file only

I don't think that have been any different in the other plugins, we're blacklisting the directory returned by the projectdir endpoint, because otherwise a user would be bugged for every file of a project on which he doesn't care having kite running

@abe33 As far as I can tell this is different than the in the other editors.
As far as I see blacklisting with the file's path adds the parent directory to the list in Kite's settings.
I just tested with Atom, a click on the X button to close the notification blacklisted "c:\users\jansorg\pycharmprojects\testpython\blacklisted" and not "c:\users\jansorg".
PyCharm and Sublime work in the same way.
Could you update the "blacklist after user clicked on X" to blacklist the file?
Spec is at https://kite.quip.com/8xWpAmOqyh96/Behavioral-specification-Permissions#GZbACABGYBx.
We can discuss the best path to blackliste here, of course. But that will have to be done for all editors then. For now, VSCode should work the same way as the others do.


DRILL-8117: Upgrade unit tests to the cluster fixture framework

DRILL-8117: Upgrade unit tests to the cluster fixture framework
Description
Upgrades various unit tests to the cluster fixture framework and replaces other instances of deprecated code usage.
Methods client.alterSession() and client.alterSystem() run sql silently which would not throw exception, so it doesn't match the purpose for some test cases. And I still keep using run() here for consistence.
For TestInboundImpersonation
Because cluster fixture save client properties even client closed, use a dedicated cluster fixture for each test case to ensure the client fixture has clean properties.
For TestImpersonationMetadata
Only use one cluster from test start to the end will induce buffer overflow. So change BeforeClass to Before to start a new cluster for each test case.
Documentation
N/A
Testing
Existing unit tests.

@jnturton @kingswanwho Should we close the other PR?

One other question.  Should we document this in the developer documentation?

@jnturton @kingswanwho Should we close the other PR?

Yes, I closed another PR

One other question. Should we document this in the developer documentation?

I think we do have developer documentation describing cluster tests, or do you mean something else?

One other question. Should we document this in the developer documentation?

I think we do have developer documentation describing cluster fixture tests, or do you mean something else?

I was referring to the markdown files in the /docs folder.   With this PR do those need to be updated?  (It doesn't have to be a part of this PR.)

One other question. Should we document this in the developer documentation?

I think we do have developer documentation describing cluster fixture tests, or do you mean something else?

I was referring to the markdown files in the /docs folder. With this PR do those need to be updated? (It doesn't have to be a part of this PR.)

Hi Charles, I have checked /docs developer information, this PR transfer test framework from BaseTestQuery to ClusterTest, and doesn't change the test logic of ClusterTest. James helps to find a clean way to create new ClientFixture, and handle UserException. I can help to update those information in /docs in a new PR.

Okay, I think the penny's finally dropped. I was also thinking about the markdown in /docs but couldn't fathom what we'd add. But the new UserExceptionMatcher usage can be described and also the try-with-resources style of creating single-use client fixtures.

Message to whoever squashes and merges here, in case it's not me: when cleaning up the squashed commit detail message please retain the co-author footer so that the repo will reflect @kingswanwho's contribution.
---------

Co-authored-by: kingswanwho<EMAIL_ADDRESS>


Fix duration of slot conditions

Includes bonus Perish Song test

This is actually not correct...

...well it's good enough for 2 player formats, but I'll need to rework it for 4 player formats.

Ok now it should work with 4 players as well.


[5.6] Allow user-defined Sparkpost endpoint

Fixes #23864.
This allows the user to set an endpoint when using the Sparkpost transport by setting the 'services.sparkpost.options.endpoint' configuration key.
Currently, the options array is empty by default, and not actually used in the class, but the TransportManager still passes it into the constructor.
To use this, a user must add the sparkpost.options.endpoint key in config/services.php, for example:
'sparkpost' => [
        'secret' => env('SPARKPOST_SECRET'),
        'options' => [
                'endpoint' => env('SPARKPOST_ENDPOINT');
        ]
    ],

If the config option isn't set, or if it is null (default return from the env() helper), the default 'https://api.sparkpost.com/api/v1/transmissions' endpoint is used.
This approach allows a user to modify the endpoint of an existing SparkPostTransport through setOptions(). It also allows a user to have more complex endpoint logic by simply extending the class and overriding getOptions() rather than having to override send() or the constructor.

@dmcbrn PR submitted. Example was changed to match the style of every other example for services.


Cannot find package error

Hi,
I have a repository that I'm trying to convert to gradle based build by using gogradle plugin. I already defined all the dependencies in build.gradle file. But, when I run gradlew build I'm getting a lot of the following errors about package not found:
driver.go:17:2: cannot find package "github.com/Shopify/sarama" in any of:
        /Users/amimas/.gradle/go/binary/1.8.1/go/src/github.com/Shopify/sarama (from $GOROOT)
        /Users/amimas/gitProjects/POC/golang-project/.gogradle/project_gopath/src/github.com/Shopify/sarama (from $GOPATH)

driver.go:18:2: cannot find package "github.com/Sirupsen/logrus" in any of:
        /Users/amimas/.gradle/go/binary/1.8.1/go/src/github.com/Sirupsen/logrus (from $GOROOT)
        /Users/amimas/gitProjects/POC/golang-project/.gogradle/project_gopath/src/github.com/Sirupsen/logrus (from $GOPATH)

I know those dependencies are being pulled. I can see them in the vendor directory at the root of the repository, but the error messages above indicates it is not looking at the vendor directory. Did I miss any configurations?
Here's the snippet of the driver.go file.
package main

import (
	"context"
	"encoding/binary"
	"encoding/json"
	"fmt"
	"io"

	"github.com/Shopify/sarama"
	"github.com/Sirupsen/logrus"
)

Here's what the build.gradle looks like:
dependencies {
    golang {
        build<EMAIL_ADDRESS>        build<EMAIL_ADDRESS>    }
}
golang {
    packagePath = 'amimas/golang-project'
    goVersion = '1.8.1'
}

build {
    targetPlatform = ['linux-amd64']

    go 'build -o .gogradle/golang-project --ldflags "-extldflags -static" . amimas/golang-project'
}

I was able to get the build completed successfully by moving/copying the contents of vendor directory into .gogradle/project_gopath/src directory. So, I guess now my question is: is it supposed to be that way?
Currently the directory structure looks like this:
golang-project
-- | .gogradle
    -- | cache
    -- | project_gopath
          -- | src
               -- | my-package
-- | vendor
     -- | github.com
     -- | golang.org
-- build.gradle
-- a.go
-- a_test.go
-- b.go
-- b_test.go
-- main.go

I hope the this makes sense. The | denotes a directory. After I copied the contents of vendor directory into .gogradle/project-gopath/src, the build seemed to compile/complete successfully.
Am I doing something wrong or is this a new bug?

I don't understand why there's an extra dot in your command:
go 'build -o .gogradle/golang-project --ldflags "-extldflags -static" . amimas/golang-project'

I guess you should remove that dot before amimas/golang-project.

Good catch. Thanks. I removed the dot but I still have the same error when I run gradlew build

Interesting. Would you mind sharing a sample to let me reproduce this issue?

I'm working with a private repository. So, I can't share that directly, but it was probably forked from the following project. I'm simply trying to use gradle for the build process instead of the way it is here.
https://github.com/MickayG/moby-kafka-logdriver

But github.com/Shopify/sarama and github.com/Sirupsen/logrus are both public so I think you could construct a reproducible example with only these repos, a simple main.go and build.gradle.

okay. I'll see if I can reproduce it with a simpler repo

Here's a repo containing dependency only on Shopify/sarama. Dependency is being pulled fine, but can't seem to get the build going.
https://github.com/amimas/gogradle-test
Thanks for the quick responses.

Thank you very much.
Your go 'build -o .gogradle/golang-project --ldflags "-extldflags -static"' missed package name. It shoule be go 'build -o .gogradle/golang-project --ldflags "-extldflags -static" golang-project'. See https://golang.org/cmd/go/#hdr-Compile_packages_and_dependencies for documentation.

Can't believe it was as simple as that. I was trying to different options and didn't realize the package name had to be there.
This brings another question. To use the plugin, in addition to applying the plugin, I also need to specify the package name (packagePath) in the golang DSL in build.gradle file. Why is that the case? Now, as you can see, I need to specify the same package name in the go build command again, which I only need in order to specify the extra arguments for building static binary. What do you think of using the gradle project name as the default "package name" if customized go build command is not specified? I think that will make it more simpler to apply the gradle plugin
You can close the issue, if you want. Thanks again for your time.

Well, in go's world, everything must have a "package path", including the one you're developing. Default package is not a very good idea because it may lead to potential name collision.


Convert \n to actual line breaks after interpolating liquid

This allows entering new line characters via \nfor agents that do not use FormConfigurable and/or a text area to input the payload. I only tested it with the HipchatAgent, senarios to verify the patch is working are welcome.
/cc @drbig @virtadpt

Coverage decreased (-0.07%) to 88.29% when pulling 45948f22db6aa3d78670c8106060caa3800fb3c9 on dsander:liquid-line-breaks into<PHONE_NUMBER>c97b4cdc06077f1f6190eb44f64301 on cantino:master.

Coverage decreased (-0.07%) to 88.29% when pulling 45948f22db6aa3d78670c8106060caa3800fb3c9 on dsander:liquid-line-breaks into<PHONE_NUMBER>c97b4cdc06077f1f6190eb44f64301 on cantino:master.

Thanks @dsander! Do we understand at what stage in the process a \n isn't getting converted?  I'd expect that we want to convert \n in the JSON strings to a newline before performing interpolation.  Is that what this is doing?

From just reading the diff it seems to be doing conversion after interpolation of a template, which perhaps in some rare cases may result in something unexpected... Patch applied for testing anyway, I'll report back if I see any problems with this. Thanks @dsander!

@cantino When you enter "\n" in an input field (the characters not <enter>) it will never be interpreted as a line break, it's just two normal characters. At the moment the conversion is done after the interpolation.
@drbig I was thinking about that too, I tried adding a {{line_break}} liquid tag, but that was somehow swallowing the encoded \n


[feature] Add ServiceMonitor for operator

Is your feature request related to a problem? Please describe.

Describe the solution you'd like

reference:
https://github.com/radondb/radondb-mysql-kubernetes/blob/main/charts/helm/templates/servicemonitor.yaml
Describe alternatives you've considered

Additional context

The name of the monitoring service is -metrics, for example, if you create a cluster called sample-mysql, the monitoring service name is sample-metrics


Use upstream bufferization for TileFuseAndVectorizePassPipeline.

This is not used in default pipeline because the upstream comprehensive
bufferization does not support LinalgExt ops, see https://github.com/google/iree/issues/9004.

@bjacob this switches to use upstream bufferization for ARM matmul codegen. It's been used in x86 codegen for a while, and I verified that the behavior is aligned to IREE's old bufferization. I expect that it's an NFC.


freezing columns

HI.
I checked here: https://github.com/tabalinas/jsgrid/issues/105 and stephenlawuk 's function works. Just wonder if meanwhile anything changed in the framework.

@labregowski, no changes for the time being. The best way to go is to implement it. Some insights can be found in the original issue.


20160831 031700 polling motor driver

This PR moves the motor driver away from the OT forked firmware, and works as follows:

When a gcode command is sent, driver returns only when b"ok" or similar is received from motor controller
Current coordinates are polled using the M114 "show current position" gcode command

The response includes the motor controller's target coordinates and it's real-time coordinates

To detect when a series of move commands have completed, the wait_for_arrival() method compares the target coordinate to the real-time coordinate, and returns when they're equal

LGTM, but we need to test it IRL a lot to make sure.

Ready to be merged. This branch has passed thorough testing, running multiple hours on the tests/opentrons_sdk/drivers/random_move.py test. Ran over 24 hours, and all errors occurring have been either firmware or electrical errors.


Bump timeouts to 100 milliseconds for all tests in event loop

Current dependencies on/for this PR:

feature/proof-of-stake

PR #649

PR #722   👈

PR #705

PR #706

PR #707

PR #713

PR #714

PR #718


Added ml-commons.

Signed-off-by: dblock<EMAIL_ADDRESS>Description
Added ml-commons.
Check List

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@dblock , thanks a lot. Didn't know we should add new plugin to opensearch-plugins.

@ylwu-amzn We use meta to operate on sets of repos, not sure where/how we should document this.

@ylwu-amzn We use meta to operate on sets of repos, not sure where/how we should document this.

Not sure if we have an official doc for plugin development. If we have, we should add to there. If no and not so necessary to add it, I think it's also ok to add to OpenSearch contributing doc https://github.com/opensearch-project/OpenSearch/blob/main/CONTRIBUTING.md

@ylwu-amzn We use meta to operate on sets of repos, not sure where/how we should document this.

Not sure if we have an official doc for plugin development. If we have, we should add to there. If no and not so necessary to add a new doc for plugin development, I think it's also ok to add to OpenSearch contributing doc https://github.com/opensearch-project/OpenSearch/blob/main/CONTRIBUTING.md

This project is a good repository for anything plugin development, including a guide. See https://github.com/opensearch-project/opensearch-plugins#opensearch-plugins for a skeleton of plugin-related topics.


Add GCC 7.2

we're going to do this with the next template refresh

Looks like this one might be invalid now with the latest changes.  @uilianries , wdyt?

@solvingj I agree. This one is outdated after our last merge. This PR can be close now.


Issues with setData on certain images/crops

Using  Cropper v3.0.0-alpha.1
Testing on Windows 10 with IE and Chrome both latest versions
What I am trying to do is probably the simplest application of cropper - I just want to obtain crop coordinates for a 1:1 thumbnail portion of an image, and do all the processing server side.
What I need to do is to set up an initial thumbnail crop area when the page loads (this area is from a face detection algo on the server).   So in the Ready function of the Cropper, I'm performing a setData operation.    I determined that I needed autoCrop to be enabled in order to pre-set a crop boundary.
It has been problematic.  For certain images (but not all), if I set the x, y, width, height in a setData call,  what happens is that the current x, y remain where the autoCrop set them, and the width and height are changed.  It seems that setData has a problem with certain combinations of image/crop positions/dimensions.
After much testing I determined that a workaround was to always set the width and height first as one setData call,  and then set the x, y, in a separate setData call afterwards.
Here is a paste of the Cropper setup:
$('#photo').cropper({
  viewMode: 0,
  checkCrossOrigin: false,
  preview: '#thumbPreview',
  aspectRatio: 1,
  dragMode: 'none',
  background: false,
  guides: false,
  center: false,
  checkOrientation: false,
  minContainerWidth: 130,
  rotatable: false,
  scalable: false,
  autoCrop: true,
  movable: false,
  zoomable: false,
  toggleDragModeOnDblclick: false,
  minCropBoxWidth: minThumbPx,
  minCropBoxHeight: minThumbPx,

  ready: function(){
      // Set initial thumbnail boundaries

    // This would fail
    //var defaultCrop = { "x":355, "y":0, "width":(501-355)-1, "height":(501-355)-1};
    //$('#photo').cropper('setData',defaultCrop);

    // Width/height must be set prior to position , or else Cropper may get confused.
    $('#photo').cropper('setData',{"width":(501-355)-1, "height":(501-355)-1});
    $('#photo').cropper('setData', { "x":355, "y":0});
  }
});

Anyway there would appear to be an issue with the way that setData is processing the parameters, or the order it is doing it.
It would also be nice in general for setData or setCropBoxData to set a cropping region even when Cropper is in a Cleared state with no crop region active (not sure if this is a limitation of the way it needs to function?).

Try to round data values first:
$().cropper('setData', {
  x: Math.round(data.x),
  y: Math.round(data.y),
  width: Math.round(data.width),
  height: Math.round(data.height),
});

if i need to take input value as width and height how can i arrange them inside cropper method?this does not work
var width = $('#width').val();
var height = $('#height').val();
$(this).cropper('setCropBoxData', {width: width, height: height});

@ruhinacse14 If the width/height is the same as the current crop box's width/height, then them will be ignored.


dm-reverb-nightly == 0.5.0.dev20211104 can't be installed, no version found by pip

python 3.7, 3.8, all don't have it

Hi, just want to know if you have resolved this issue. I'm also facing the same problem.


[wil] Update to v1.0.230411.1

Fixes #30860
Update wil to latest version v1.0.230411.1.
No feature need to test.

[x] Changes comply with the maintainer guide
[x] SHA512s are updated for each updated download
[ ] The "supports" clause reflects platforms that may be fixed by this new version
[ ] Any fixed CI baseline entries are removed from that file.
[ ] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

Thanks for the update!


"Coroieni", "Baba", "Dealu Mare", "Drăghia" and "Vălenii Lăpușului" are listed in the drop-down menu

Description:
"Coroieni", "Baba", "Dealu Mare", "Drăghia" and "Vălenii Lăpușului" are listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Coroieni" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Coroieni, MARAMUREȘ (Coroieni)" and "Comuna Coroieni, MARAMUREȘ".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Type "Baba" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Baba, MARAMUREȘ (Coroieni)".

Step 5
Type "Dealu Mare" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Dealu Mare, MARAMUREȘ (Coroieni)".

Step 6
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 7
Type "Drăghia" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Drăghia, MARAMUREȘ (Coroieni)".

Step 9
Type "Vălenii Lăpușului" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Vălenii Lăpușului, MARAMUREȘ (Coroieni)".


[BUG] picamera2 doesn't work as a process.

I'm currently doing a project where I need the camera to take pictures when motion its detected amongst other stuff. So, I decided to run the motion part of the software as a process, and it get stuck at camera.start(). I'm using the multiprocessing package. No error codes.

Do you mind posting your code?
I've tested running multiple previews in subprocesses here -
https://github.com/raspberrypi/picamera2/blob/main/tests/close_test_multiple.py

I just wanted to add that you need to be very careful using the multiprocessing module with Picamera2. If you've started opening or using cameras and then try to use "multiprocessing", my understanding is that the original process gets forked. This duplicates the entire state, including file handles into all the kernel camera devices. If one process tries to use the camera now, it's not clear to me what happens to the other, but I expect it will start to get "unexpected" results. So my general advice is "multiprocessing + Picamera2 = be very careful". But as Chris said, please post some code - a simplified test case to demonstrate the problem would be helpful. Thanks!

Based on the internal event mechanics I wouldn't expect this to work properly in many cases. See also #387. At present, there isn't even python-thread safety, and multiprocessing adds a whole other can of worms.

@OmarLopez18 Hi again, I've been trying the following test case:
from multiprocessing import Process
from picamera2 import Picamera2
from threading import Thread

picam2 = Picamera2()
picam2.start()

def do_capture(picam2):
        picam2.capture_metadata()

#p1 = Thread(target=do_capture, args=(picam2,))  # this works
p1 = Process(target=do_capture, args=(picam2,))  # this locks up
p1.start()
p1.join()

I find that if I use a Thread then it works as expected, but with a Process it locks up immediately. My understanding is that libcamera does not allow you to use a single camera from multiple processes, so this kind of thing won't work. If you have code for us to look at, please let us know, otherwise I'll consider closing this in due course. Thank you!

@davidplowman hi, using Process didn’t work for me. Although I manage to use partial threads and that work in my case.


UI - fix a bug that shows error at unintended times on the application detail page

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

NONE

Thank you.
/approve


Translations of the guide in general.

Given that @bitemyapp has started a translations cycle, our dear overlord will have to use his iron grasp on how these are to be coordinated. Creating this issue for bundling up several opinions on what is necessary, when necessary.

I have started the greek translation effort here, on the learnhaskell-greek branch of the fork.

@irrequietus this is a good idea and it works for me.
/cc @doppioslash

I've started the german one here :)

Indeed :)
I've started the italian one here.

@jhedev @doppioslash excellent stuff people! Is there anybody working on a Japanese version? cc @bitemyapp

Starting the French translation here

Starting the Spanish translation [here] (https://github.com/davecaos/learnhaskell/blob/davecaos-En-Espanol/guide-es.md)

Starting the Turkish translation here.

@irrequietus nobody's working on the Japanese version TMK. I didn't ping Julie because I didn't want to distract her from the book.

@bitemyapp not a problem!

I'll start the Japanese translation. Actually I tried it in several months ago.

I've started working on the Traditional Chinese version here with common diction in Taiwan. The locale code for Chinese are zh_ in convention. For example, zh_TW, zh_HK, and zh_CN for Simplified Chinese, etc.
As there do exist some differences in commonly-used phrases, I named the file as guide-zh_tw.md to better clarify the purpose.

@fujimura :+1: , @southp :+1:

started Polish translation here

I'll start the Simplified Chinese translation.

I've finished russian translation here https://github.com/bitemyapp/learnhaskell/pull/76

Could I translate this guide in Korean?

@steelbear by all means, please do!


Add unittest to check for specific repo files

This repo should have the following list of files included:

./Docker or docker/Docker
./docker-compose.yml or ./docker/docker-compose.yml
./.env_sample
./.gitignore
./.travis.yml
./.codeclimate.yml
./CHANGELOG.md
./CODE_OF_CONDUCT.md
./CONTRIBUTING.md
./.github/ISSUE_TEMPLATE
./LICENSE.md
./.github/PULL_REQUEST_TEMPLATE
./README.md
./TROUBLESHOOTING.md
./USAGE.md
./USE_CASES.md

This PR is only asking for tests of the existence of these files, if the files do not exist when you run the tests - do not worry about the tests not passing. We will identify this and create a new PR for the issue.
Thank you!

I can take the task!

@thinkingserious are some of these files even needed ?
For example, we may not need a docker file as these all are just templates.


Add fallback functionality

Signed-off-by: misha<EMAIL_ADDRESS>
Changes as agreed per https://github.com/kedacore/keda/issues/1872
Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[x] Tests have been added
[x] A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified) N/A
[x] A PR is opened to update the documentation on (repo) (if applicable) https://github.com/kedacore/keda-docs/pull/474
[x] Changelog has been updated

Fixes #1872

@mishamo FYI the tests have failed

@mishamo thanks a lot for the contribution 🎉

Thank you, very nice feature!


Rejuvenate log levels

We appreciate your previous feedback! Here's a reissue of https://github.com/Netflix/hollow/pull/419 with a new version of our tool. The tool made fewer transformations. Again, we'd appreciate any feedback and are willing to make further changes if you wish to incorporate our PR into your project.
Settings
We have several analysis settings. We can vary these settings and rerun if you desire. The settings we are using in this pull request are:
Treat CONFIG levels as a category and not a traditional level, i.e., our tool ignores these log levels.
Never lower the logging level of logging statements within catch blocks.
Never lower the logging level of logging statements within if statements.
Never lower the logging level of logging statements containing certain (important) keywords.
Never raise the logging level of logging statements without particular keywords in their messages.
Avoid log wrapping by disregarding logging statements contained in if statements mentioning log levels.
The greatest number of commits from HEAD evaluated: 1000.
The head at the time of analysis was: ff635ee9e3d7e466796c2c25e4760b1a66cf3e1f

I'm curious to see how it plays out in other projects

We appreciate your previous feedback! Here's a reissue of #419 with a new version of our tool

Sorry, I was too obtuse in my original reply. We're not interested in your tool. Please don't send any more PRs from it. Thank you.


Add box-sizing to smacss

I hope this is the right place for it. I also thought about putting it near the top, between display and position?

Since we at @brigade don't subscribe to the SMACSS philosophy per se, I can't speak to whether this would be an appropriate place to order box-sizing.
Now that an implementation for #440 has landed on master, I'm hoping someone from the community can step forward and "own" any SMACSS related configuration, so we can remove this default ordering from scss-lint (and developers who want it can load the plugin separately).
Until #440 gets released, can anyone else who uses SMACSS vouch for this ordering?

Would it also be possible to add support for something like order: 'my-ordering.txt', so I don't need to have the whole CSS definition inside my yml?

I take that back.


Fix popup closing immediately after showing on some Linux WMs

When a popup is going to be closed, switch focus to the parent only if the closing popup is still being focused.
Fixes some cases with specific WMs where due to the order of events, a new popup could be immediately unfocused because a previously opened and closed popup is switching focus to the parent.
Also added a few more logs to help investigate this kind of issue.
Fixes #50367
Tested on ArchLinux with Gnome (no regression) and i3 (fixes the issue).
Kudos to @Houkime whose thorough investigation lead to finding this fix.

Yes, this seems to fix  #50367, thanks.

Thanks!


HNC: Update user guide on API conversion

See 3 corner cases of v1a1 propagated objects after API conversion.
We will suggest in the document:

No mode change before conversion;
No deletion before conversion;
For types with ignore mode, the previously propagated objects (if possible, when the mode was previously set at propagate) will be considered as source after API conversion.

Part of #868

Closing this since they are added in the release note https://github.com/kubernetes-sigs/multi-tenancy/releases/tag/hnc-v0.6.0-rc1


Why does JObject inherit from object instead of dict?

(paging @ejhumphrey )
Legit question, I'm curious if this was a conscious decision, and if so, what the reasons are/were.
Seems like inheriting from dict would let us ditch several one-liners which reimplement (most of) the dict interface?

This is a gardening issue... What started as an object evolved into a dict,
and it's totally sane / reasonable to consolidate now.
On 7 Mar 2015 20:47, "Brian McFee"<EMAIL_ADDRESS>wrote:

(paging @ejhumphrey https://github.com/ejhumphrey )
Legit question, I'm curious if this was a conscious decision, and if so,
what the reasons are/were.
Seems like inheriting from dict would let us ditch several one-liners
which reimplement (most of) the dict interface?
—
Reply to this email directly or view it on GitHub
https://github.com/marl/jams/issues/27.

Right.
I think, once #26 is settled, that I'll rewrite JObject to inherit from dict.  There should be no change in functionality, and it should allow us to cut down some redundant code and simplify tests.

This actually seems unnecessary in retrospect.  The dict-interface is really only helpful for serialization, and otherwise we really want an object/named tuple style interface.
Closing this one out.


--key Alice leads to error with recent updates

What is the proper way for inserting non-hex formatted key seeds?
./target/release/edgeware --chain=edgeware --key Alice
2019-03-21 16:58:10 Edgeware Node
2019-03-21 16:58:10   version 0.1.7-d807425-x86_64-macos
2019-03-21 16:58:10   by Parity Technologies, 2017-2019
2019-03-21 16:58:10 Chain specification: Edgeware V0.1.7
2019-03-21 16:58:10 Node name: annoying-paper-9982
2019-03-21 16:58:10 Roles: FULL
Error: Error(Keystore(InvalidSeed), State { next_error: None, backtrace: InternalBacktrace { backtrace: None } })

You can use --alice as shortcut. Or do --key //Alice.


Epic: Support Postgres event triggers

Add support for event triggers to capture DDL events:
https://www.postgresql.org/docs/current/event-triggers.html
We currently do not support event triggers due to the superuser requirement.
Related slack thread:
https://neondb.slack.com/archives/C03QLRH7PPD/p1710592909306899
User requests:
https://discord.com/channels/1176467419317940276/1216517379366846474/1216517382898454639
https://community.neon.tech/t/permission-denied-to-create-event-trigger/443

Supported by RDS https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/PostgreSQL.Concepts.General.FeatureSupport.html#PostgreSQL.Concepts.General.FeatureSupport.EventTriggers

Integration partners need to capture DDL events and use EVENT TRIGGERS to listen for them. Is it possible that, instead of trying to allow for event triggers completely, we offer a specific function to register for DDL events of a table. Partners need the DDL events, not necessarily the event triggers.

Use-case from Readyset
https://github.com/readysettech/readyset/blob/7bf77a8558908dab347ffa09130494a9c984c5d5/replicators/src/postgres_connector/ddl_replication.sql#L24-L50

Probably https://github.com/xataio/pgroll needs event triggers as well
Discussion https://neondb.slack.com/archives/C026T7K2YP9/p1717520052520779

Probably https://github.com/xataio/pgroll needs event triggers as well Discussion https://neondb.slack.com/archives/C026T7K2YP9/p1717520052520779

just fyi, issues tab on pgroll to me suggests that it's not advisable as a go-to

what's the expected timeline/priority of implementing this? i see #8808 was opened in august but it looks like there has been no movement since then.

This will be needed for Neon to be a fully supported target for zerosync.dev too. Without ability to receive correct DDL events transactionally, Neon can only ever be used with Zero (and other local first systems) for small deployments.
Happy to work with anyone on your team to define the minimal interface needed if full event triggers are too difficult.


Music recommendation from emotions

I would like to add a project.
Here, I would detect emotions of a human from facial expressions and then recommend musics accordingly

Ok
Add in face emotions recognition folder


CW-183: Duplicate ad banner content on kata search page

Sometimes the ad banners shows duplicate content. It's supposed to hide one of them if duplicate appears, but clearly it sometimes fails, as shown above.

@Voileexperiments thank you again for sharing this detail, this is a bug that we are aware of and are investigating the cause. We hope to have a fix very shortly.


Fix multiple NullPointerException's permit spark-submit functionality upgrade to elasticsearch-5.0.0

Hi @quintinali please merge this into your current cc_es_hadoop branch and add it to the open pull request over on https://github.com/mudrod/mudrod/pull/77 thank you. I will continue to work with you on fixing the bugs (of which there are many), and making the improvements.
Thank you

@lewismc Thanks for your help. These modifications are very helpful. I have merged your branch to quintinali:cc_es_hadoop branch. However, I don't know how to add branch modifications to the open pull request.
I find this link http://stackoverflow.com/questions/9790448/how-to-update-a-pull-request
Is it correct to run following command in quintinali:cc_es_hadoop branch to update the pull request?
git push -f origin mudrod:master
Could you please give me some hints when you have time?


Control Pod Mac Address

Component (Azure NPM or Azure CNI):
Azure CNI
Describe in detail the feature/behavior/change you'd like to see:
Have the ability to control the Mac Address assigned to containers in a pod based on a pod annotation
Orchestrator(e.g. Kubernetes, Docker):
Kubernetes
Operating System (Linux/Windows):
I specifically need Windows but don't see why it shouldn't be done for both
Anything else you would like to add:
The primary motivation for this kind of feature is to support running legacy software that is licensed based on mac address inside of a kubernetes cluster. Calico CNI supports this as documented here: https://projectcalico.docs.tigera.io/networking/pod-mac-address but deploying calico cni on aks with windows nodepools isn't fully working (at least I could not get volumes working)

@alennartz this is an interesting use case, but unlikely something that we will support.
First, Azure CNI is on the way out in favor of Cilium [1] [2] as the "core" CNI plugin for Kubernetes in Azure. Since Cilium CNI will be responsible for setting up the container network namespace (including assigning the MAC), and Azure IPAM is only responsible for IP address management, this kind of feature request would need to go to them.
(AzCNI will continue to be used on Windows for some time, but we don't want to add dramatically disparate features between supported OSes.)
However, I don't think it should because, fundamentally, the CNI does not (and should not) know how to talk to Kubernetes itself - it is used by Kubernetes through the CNI contracts and neither component should know any more about the other component than what is declared in that Spec. If the CNI tries to get Pod Metadata, it depends on Kubernetes, and then we have circular dependencies.

Thanks for the information Obviously we don't want to introduce circular dependencies. I also agree on principal in not going wider than the CNI spec (with which I am not familiar so please forgive any foolishness ideas caused by this ignorance).
I'm curious as to your thoughts on this alternative:
What if the concept of statefulness, as represented in k8s by stateful sets, were incorporated in to the CNI spec. In this scenario I would imagine that just as volumes are currently kept the same, MAC address & perhaps IPs could be preserved for pods controlled by a stateful set once initially provisioned. This would not allow us to control the mac address up front but at least keep it stable once set which would be sufficient to solve the initial use case.
Thanks.


DAG fails to render if operation (on-run-* hook) has parents

Describe the bug
If an operation (on-run-* project hook) depends on a model, it creates an entry for that operation in parent_map + child_map in manifest.json, which throws off the DAG rendering logic. It is possible to still use the DAG viz by adding --select criteria, i.e. by filtering out the operation node.
It's arguable whether operations should be included in parent_map + child_map, but isn't strictly wrong that they are. Changing that would require an artifact schema change. For now, it feels appropriate to handle this in the dbt-docs DAG rendering logic.
Steps To Reproduce
# dbt_project.yml
on-run-end:
  - "{{ reference_my_model() }}"

-- macros/reference_my_model.sql
{% macro reference_my_model() %}

    select 1 from {{ ref('my_model') }}

{% endmacro %}

-- models/my_model.sql
select 1 as id

$ dbt docs generate
$ dbt docs serve

I haven't been able to successfully run npm on this machine, so I can't generate source maps and get a more helpful pointer to a specific line of code. That's definitely the thing to do first.
The output of dbt --version:
This fails in v1.0.1 and v0.21.1, so at least this isn't a regression in v1.0. But it's pretty obnoxious, and I bet the fix is straightforward, so I'd like to include in dbt-core==1.0.2 if we can.

It's possible my theory for the cause of this bug is incomplete—folks are seeing it even without on-run-end hooks, or on-run-end hooks that reference other resources. See slack threads for more details


remove no-longer-needed extraneous subdirs

Thanks for the PR.
Can this wait? I have a huge patch in progress which touches a lot of files. It would be better to do the reorg when we do not have large patches in flight.

Was there an issue filed to do this cleanup? I'm not against deleting the
JS stuff if it's no longer in use, but moving almost every file doesn't
seem important right now
On Sat, Sep 9, 2017 at 2:21 PM Erik Arvidsson<EMAIL_ADDRESS>wrote:

Thanks for the PR.
Can this wait? I have a huge patch in progress which touches a lot of
files. It would be better to do the reorg when we do not have large patches
in flight.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/attic-labs/noms/pull/3687#issuecomment-328304240, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AMnImmfJR_X9voxhQItiWeGMNoOOhPnNks5sgwFngaJpZM4PRypi
.

@cmasone-attic yes there was, it me: #3668.
Thanks @wardn for the patch. I'm in favor of this. The useless /go subdir has been bugging me for awhile.

PS @wardn in order to accept any patch from you we'll need you to complete the contributor agreement first: https://github.com/attic-labs/noms/blob/master/CONTRIBUTING.md#contributing-code

fixed merge conflicts


Change to Property

Removes () from notes in the grpc_points and other Properties

Will include these changes as part of the formatting fixes


[Feature]: Autocomplete Prefix

What would you like to see added?
Bash's completion system will autoaccept completion up until common prefix. Should implement option for this as well.
Example
Given the files:

slide_01.md
slide_02.md
slide_12.md

Pressing tab will resolve to:
slide_

resolved by #227


[Run] Autosuggest not working

ℹ Computer information

PowerToys version: 0.23.0
PowerToy Utility: Run
Running PowerToys as Admin: No
Windows build number: [run "winver"]

Autosuggest is not working due to incorrect text from UpdateResultWithActionKeyword function when action keyword is not present.

does this fix the bug with the _  or is that a different bug?
Is this really hit the 'hot fix' bar?  I'm skeptical honestly.

@crutkas This is a different bug. Core autosuggest functionality is not working in version 0.23.0. In the screenshot below, autosuggest text should have been "Maps" but instead nothing is shown:

actually looks like we merged this into stable.

Fixed in https://github.com/microsoft/PowerToys/releases/tag/v0.23.2


serializing a map with numeric key's doesnt work

hi,
serializing a map with numeric keys does not work and ends in something like
TypeError: 21 key is not a string
import * as oo from 'json8';

const v = new Map();
v.set(4,5);

oo.serialize(v);
``

numbers aren't valid JSON keys


Question: How to track user data?

I want to track some user information, like UserId using opentelemetry. How I can do that? I would like to known if its a good approach use Span or Resource or other component to do so. I notice that is not possible to modify a resource after create a instance of openTelemetry. Example: to set UserId after login or remove UserId after logout. If I try to get another opentelemetry and set it on GlobalOpenTelemetry.set I get a exception. Because I instrumented the app (instrumentation.library.okhttp.v3_0) I also not able no modify any span with custom data created by OkHttp3Singletons

Hi, I just solved that creating a new SpanProcessor


Module installation error on node 4.2.3

I m using Node 4.2.3 When trying to install I m getting this error.
   [ERROR] gittio requires the global Titanium CLI: [sudo] npm install -g titanium

But I m aldready installed Titanium.
    titanium -v
    node) sys is deprecated. Use util instead.
    5.0.5

I look at gittio source code timodules.list function returns null

Mm, maybe because of that error timodules isn't able to read the JSON result from the Ti CLI. Let me check if we need to update the Ti CLI to work with 4.2.x still or if this has already been fixed.

Could you reinstall the Ti CLI? I run node 4.2.3 as well but I don't get that warning when I run ti -v

See https://jira.appcelerator.org/browse/TIMOB-19133

@FokkeZB   I reinstall Ti CLI and Gittio but  same result. :(

Could you try to delete your local npm cache (sudo rm -rf ~/.npm) and then install again?

I tried but same :(

Weird. Could you do a code search on the titanium dir (probably /usr/local/lib/node_modules) to see where sys is used? Search for both "sys" and 'sys'.

it cannot  find anything

I open Titanium npm modules on  text editor. and search
(node) sys is deprecated. Use util instead.
nothing found .its really weird .where is it come

its only found on test files
    /usr/local/lib/node_modules/titanium/node_modules/node-appc/node_modules/.bin/uglifyjs:
5
6  var UglifyJS = require("../tools/node");
7: var sys = require("util");
8  var yargs = require("yargs");
9  var fs = require("fs");

  /usr/local/lib/node_modules/titanium/node_modules/node-appc/node_modules/request/node_modules/http-signature/node_modules/asn1/tst/ber/writer.test.js:
2
3  var test = require('tap').test;
4: var sys = require('sys');
5
6  ///--- Globals

    /usr/local/lib/node_modules/titanium/node_modules/node-appc/node_modules/uglify-js/bin/uglifyjs:
5
6  var UglifyJS = require("../tools/node");
7: var sys = require("util");
8  var yargs = require("yargs");
9  var fs = require("fs");

      /usr/local/lib/node_modules/titanium/node_modules/node-appc/node_modules/uglify-js/node_modules/uglify-to-browserify/index.js:
  15    if (cache[file]) return makeStream(cache[file])
 16    var uglify = require(file)
  17:   var src = 'var sys = require("util");\nvar MOZ_SourceMap = require("source-map");\nvar UglifyJS = exports;\n' + uglify.FILES.map(function (path) { return fs.readFileSync(path, 'utf8') }).join('\n')
  18
    19    var ast = uglify.parse(src)

/usr/local/lib/node_modules/titanium/node_modules/request/node_modules/http-signature/node_modules/asn1/tst/ber/writer.test.js:
2
3  var test = require('tap').test;
4: var sys = require('sys');
5
6  ///--- Globals

5 matches across 5 files

Yeah, very strange. I've found that as well with another user and reported the issue:
https://jira.appcelerator.org/browse/CLI-907

•	sudo rm -rf ~/.appcelerator
•	sudo rm -rf ~/.titanium
•	sudo npm uninstall -g titanium
•	sudo npm uninstall -g alloy
•	sudo npm uninstall -g acs
•	sudo npm uninstall -g appcelerator
•	sudo npm install -g appcelerator
•	appc use latest
•	appc setup
•	sudo npm install -g alloy

  sudo npm install -g titanium

Now its solved my problem.

haha, but now we still don't know where sys was used ;)

yes :)  We cannot know anymore

Did you have TiShadow installed?

yes . its give me
(node) sys is deprecated. Use util instead.

If you uninstall it (or update to tishadow master) the sys / util warning will go away.

Now Titanium not giving util warning .But Tishadow gives. And they are different modules. How can it possible ?

TiShadow installs a hook into your ~/.titanium/config.json file that appc runs

Hmm now I understand ,thank guy :)


basic findQuery support

First draft at findQuery support.  I've simply mapped the underlying Firebase query methods.
Syntax:
// order by key
this.store.find('user', {
  orderBy: '_key', // default if omitted, also '_priority' is available
  limitToFirst: 10,
  startAt: '-JftjvGEXxoWX15S9l-t'
})

// order by child prop
this.store.find('user', {
  orderBy: 'lastName',
  limitToLast: 10,
  endAt: 'Wells'
})

[x] discuss query syntax (mainly the orderBy bit)
[x] tests (although similar to findAll, needs tests for the query object mapping)
[x] code cleanup (needs more DRY)
[ ] providing we're happy, write some docs

/cc @jayphelps @sararob

I started using this implementation in my App and it has been working for me perfectly.
Personally, I like the current usage of near native Firebase syntax as it makes the Firebase support docs easier to understand.
+1

Sorry for the delay on this. I had a change of job. We will be discussing this, testing and merging very soon.

Awesome!

@brendanoh @codepreneur any thoughts on the orderBy syntax?
Do you think it's okay with the _key and _priority settings? Or do you think a full passthrough of options would be clearer e.g.:
{
  orderByKey: true,
  limitToFirst: 10
}

{
  orderByChild: 'name',
  startAt: 'gamma'
}

My only problem with this more verbose syntax is that it becomes less apparent which order is chosen when you make a mistake and provide 2 order statements:
{
  orderByKey: true,
  orderByChild: 'name'
}

... you'd need to look in the code to see which one is applied last.

I would prefer the closest to firebase syntax. That allows a fallback to
the firebase documentation when anything isn't clear.
I will be at EmberConf if you want to discuss in person.
Brendan
On Feb 26, 2015 12:16 PM, "Tim Stirrat"<EMAIL_ADDRESS>wrote:

@brendanoh https://github.com/brendanoh @codepreneur
https://github.com/codepreneur any thoughts on the orderBy syntax?
Do you think it's okay with the _key and _priority settings? Or do you
think a full passthrough of options would be clearer e.g.:
{
orderByKey: true,
limitToFirst: 10
}
{
orderByChild: 'name',
startAt: 'gamma'
}
My only problem with this more verbose syntax is that it becomes less
apparent which order is chosen when you make a mistake and provide 2 order
statements:
{
orderByKey: true,
orderByChild: 'name'
}
... you'd need to look in the code to see which one is applied last.
—
Reply to this email directly or view it on GitHub
https://github.com/firebase/emberfire/pull/169#issuecomment-76221175.

@codepreneur how did you get it to work?

Hopefully the next release will have it but for now just get the FirebaseAdapter code from Master and paste it over the one in the EmberFire.js file your project. You need to be careful doing this but takes 5 minutes max. Of course if you bower install or update it will overwrite your change.

Awesome! I'll give that a try @brendanoh, but I managed to get it to work by adding the Git URL to my package.json thanks to @dstaley.

I did the git url way previously and it had some unintended issues with dependencies. But if its working for you then cool.

@b-e-r-t-o I added findQuery hook inside adapters/application.js with @tstirrat 's implementation, which then overrides original hook.


modify_perftest

1、change client latency  precision from ms to us
2、add function store perf metrics in mysql
3、change perf test method : perf  test according to time

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


[#143024853] Write cloud CI documentation

What
Users want to get going with their low-cost CI solutions, and we need them to do it well, so they don't get compromise themselves.
How to review
Proofreading please, make sure the docs are sane and info is clear.
You can test rendering with middleman locally:
bundle install
bundle exec middleman server

Who can review
Not @combor

We explicitly do this in the old Jenkins documentation but not in the new overview or Travis documentation. I think we should.

Shall we put it as general advice as it applies to any CI?

Shall we put it as general advice as it applies to any CI?

I think so. I wonder if we need to repeat it again in the Travis docs though, to make sure that people don't miss it.

Will renaming the pages break any existing links (internal or external)? Is that a problem?

I think it probably will. Having said that, there not much that can be done about this. This is a limitation of the single-page layout this currently uses (we can't do redirects for URL fragments as they're handled in the browser).

The advice about low-privileged users could still be clearer. It doesn't say that it's about your PaaS credentials. It's also easy to overlook if you jump straight to the Travis section. It might be good to have a linkable section in the overview about credentials, which can then be linked to from both the Jenkins and Travis sections.
Discussed with @tomskerous - we're going to merge this because it's required for user research, but will hold the story in review until we update it in a 2nd PR.


Fine-Grained control over the exposed values

Currently, the settings for enabling / disabling statistics are more or less bound to redfish endpoints. Maybe that should be more fine-grained.
In my case, I for example do not need the cpu information at all. But they are bound to the system settings.
Maybe instead of System, there would be separate entries for:

Bios
Machine
CPU
System
Health

And also for the sensors, maybe separate for

Temperature
Fan-Speed

Same for Power Supply, Usually I am inly interested in the effectively consumed watts.
And so on.
The background is:
If you have 10 servers, exporting the data every minute to VictoriaMetrics, every data you don't store helps keeping the space needed down. One could remove the data in the prometheus.yml but in my opinion, it is better to directly control this in the exporter itself.
Would you accept an MR that makes this much more configurable?

The metrics are bound to Redfish endpoints, because there is a cost to scraping each endpoint. Once the endpoint is scraped, we might as well export as much information as possible, since it's for free.
When looking at exporters in general, they do allow you to select specific subsets of metrics (like this one does), but usually not each metric individually.
I do understanding your reasoning, but I think this is a bit too niche, especially considering that Prometheus already has a way of filtering out specific metrics. Is the space needed really an issue? I am scraping ~150 machines, using several different exporters, and I never really had any concern about storage space for this.