docker-api doesn't get image id properly for Docker 1.9 if image already exists

It looks like (with docker 1.9), if an image already exists and you try to create it, it returns the tag as the id instead of the actual id.
2.2.1 :001 > require 'docker'
 => true
2.2.1 :002 > Docker::Image.create('fromImage' => 'redis', 'tag' => '2.8')
 => #<Docker::Image:0x007fe90e009e30 @id="ca6553f7ffad", @info={"id"=>"ca6553f7ffad", :headers=>{}}, @connection=#<Docker::Connection:0x007fe90a844478 @url="tcp://<IP_ADDRESS>:2376", @options={:client_cert=>"/Users/fish/.docker/machine/machines/default/cert.pem", :client_key=>"/Users/fish/.docker/machine/machines/default/key.pem", :ssl_ca_file=>"/Users/fish/.docker/machine/machines/default/ca.pem", :scheme=>"https"}>>
2.2.1 :003 > Docker::Image.create('fromImage' => 'redis', 'tag' => '2.8')
 => #<Docker::Image:0x007fe90a868bc0 @id="2.8", @info={"id"=>"2.8", :headers=>{}}, @connection=#<Docker::Connection:0x007fe90a844478 @url="tcp://<IP_ADDRESS>:2376", @options={:client_cert=>"/Users/fish/.docker/machine/machines/default/cert.pem", :client_key=>"/Users/fish/.docker/machine/machines/default/key.pem", :ssl_ca_file=>"/Users/fish/.docker/machine/machines/default/ca.pem", :scheme=>"https"}>>

$ gem list docker-api

*** LOCAL GEMS ***

docker-api (1.22.4)

2.2.1 :001 > require 'docker'
 => true
2.2.1 :002 > Docker.version
 => {"Version"=>"1.9.0", "ApiVersion"=>"1.21", "GitCommit"=>"76d6bc9", "GoVersion"=>"go1.4.3", "Os"=>"linux", "Arch"=>"amd64", "KernelVersion"=>"4.1.12-boot2docker", "BuildTime"=>"Tue Nov  3 19:20:09 UTC 2015"}
2.2.1 :003 > Docker.info
 => {"ID"=>"EDRV:EO4U:UB2T:TFDZ:UWAU:C4DR:GW2Z:SHWK:A5CA:7PUW:IEHY:E2UN", "Containers"=>0, "Images"=>17, "Driver"=>"aufs", "DriverStatus"=>[["Root Dir", "/mnt/sda1/var/lib/docker/aufs"], ["Backing Filesystem", "tmpfs"], ["Dirs", "17"], ["Dirperm1 Supported", "true"]], "MemoryLimit"=>true, "SwapLimit"=>true, "CpuCfsPeriod"=>true, "CpuCfsQuota"=>true, "IPv4Forwarding"=>true, "BridgeNfIptables"=>true, "BridgeNfIp6tables"=>true, "Debug"=>true, "NFd"=>11, "OomKillDisable"=>true, "NGoroutines"=>19, "SystemTime"=>"2015-11-05T23:22:10.446475356Z", "ExecutionDriver"=>"native-0.2", "LoggingDriver"=>"json-file", "NEventsListener"=>0, "KernelVersion"=>"4.1.12-boot2docker", "OperatingSystem"=>"Boot2Docker 1.9.0 (TCL 6.4); master : 16e4a2a - Tue Nov  3 19:49:22 UTC 2015", "IndexServerAddress"=>"https://index.docker.io/v1/", "RegistryConfig"=>{"InsecureRegistryCIDRs"=>["<IP_ADDRESS>/8"], "IndexConfigs"=>{"docker.io"=>{"Name"=>"docker.io", "Mirrors"=>nil, "Secure"=>true, "Official"=>true}}, "Mirrors"=>nil}, "InitSha1"=>"", "InitPath"=>"/usr/local/bin/docker", "NCPU"=>1, "MemTotal"=>1044578304, "DockerRootDir"=>"/mnt/sda1/var/lib/docker", "HttpProxy"=>"", "HttpsProxy"=>"", "NoProxy"=>"", "Name"=>"default", "Labels"=>["provider=virtualbox"], "ExperimentalBuild"=>false, "ServerVersion"=>"1.9.0", "ClusterStore"=>"", "ClusterAdvertise"=>""}

Oh boy, sounds like an API change.  Will need to install the latest and see what the returned JSON looks like now.  If you could run that method twice with the environment variable EXCON_DEBUG=true on, this'll be quick to diagnose!

Sure!
2.2.1 :001 > ENV['EXCON_DEBUG']='true'
 => "true"
2.2.1 :002 > require 'docker'
 => true
2.2.1 :003 > Docker::Image.create('fromImage' => 'redis', 'tag' => '2.8')
excon.request
  :chunk_size          => 1048576
  :ciphers             => "HIGH:!SSLv2:!aNULL:!eNULL:!3DES"
  :client_cert         => "/Users/fish/.docker/machine/machines/default/cert.pem"
  :client_key          => "/Users/fish/.docker/machine/machines/default/key.pem"
  :connect_timeout     => 60
  :debug_request       => true
  :debug_response      => true
  :expects             => [
    200
    201
    202
    203
    204
    304
  ]
  :headers             => {
    "Content-Type" => "text/plain"
    "Host"         => "<IP_ADDRESS>:2376"
    "User-Agent"   => "Swipely/Docker-API 1.22.4"
  }
  :host                => "<IP_ADDRESS>"
  :hostname            => "<IP_ADDRESS>"
  :idempotent          => false
  :instrumentor        => Excon::StandardInstrumentor
  :instrumentor_name   => "excon"
  :method              => :post
  :middlewares         => [
    Excon::Middleware::Hijack
    Excon::Middleware::ResponseParser
    Excon::Middleware::Expects
    Excon::Middleware::Idempotent
    Excon::Middleware::Instrumentor
    Excon::Middleware::Mock
  ]
  :mock                => false
  :nonblock            => true
  :omit_default_port   => false
  :path                => "/v1.16/images/create"
  :persistent          => false
  :port                => 2376
  :query               => {
    "fromImage" => "redis"
    "tag"       => "2.8"
  }
  :read_timeout        => 60
  :response_block      => #<Proc:0x007fa83b9cb0b8@/Users/fish/.rvm/gems/ruby-2.2.1@preview/gems/docker-api-1.22.4/lib/docker/image.rb:296 (lambda)>
  :retries_remaining   => 4
  :retry_limit         => 4
  :scheme              => "https"
  :ssl_ca_file         => "/Users/fish/.docker/machine/machines/default/ca.pem"
  :ssl_verify_peer     => true
  :tcp_nodelay         => false
  :thread_safe_sockets => true
  :uri_parser          => URI
  :versions            => "excon/0.45.4 (x86_64-darwin14) ruby/2.2.1"
  :write_timeout       => 60
excon.response
  :body          => ""
  :headers       => {
    "Content-Type" => "application/json"
    "Date"         => "Fri, 06 Nov 2015 15:57:25 GMT"
    "Server"       => "Docker/1.9.0 (linux)"
  }
  :local_address => "<IP_ADDRESS>"
  :local_port    => 63381
  :reason_phrase => "OK"
  :remote_ip     => "<IP_ADDRESS>"
  :status        => 200
  :status_line   => "HTTP/1.1 200 OK\r\n"
 => #<Docker::Image:0x007fa83aadd808 @id="ca6553f7ffad", @info={"id"=>"ca6553f7ffad", :headers=>{}}, @connection=#<Docker::Connection:0x007fa83b9cb428 @url="tcp://<IP_ADDRESS>:2376", @options={:client_cert=>"/Users/fish/.docker/machine/machines/default/cert.pem", :client_key=>"/Users/fish/.docker/machine/machines/default/key.pem", :ssl_ca_file=>"/Users/fish/.docker/machine/machines/default/ca.pem", :scheme=>"https"}>>
2.2.1 :004 > Docker::Image.create('fromImage' => 'redis', 'tag' => '2.8')
excon.request
  :chunk_size          => 1048576
  :ciphers             => "HIGH:!SSLv2:!aNULL:!eNULL:!3DES"
  :client_cert         => "/Users/fish/.docker/machine/machines/default/cert.pem"
  :client_key          => "/Users/fish/.docker/machine/machines/default/key.pem"
  :connect_timeout     => 60
  :debug_request       => true
  :debug_response      => true
  :expects             => [
    200
    201
    202
    203
    204
    304
  ]
  :headers             => {
    "Content-Type" => "text/plain"
    "Host"         => "<IP_ADDRESS>:2376"
    "User-Agent"   => "Swipely/Docker-API 1.22.4"
  }
  :host                => "<IP_ADDRESS>"
  :hostname            => "<IP_ADDRESS>"
  :idempotent          => false
  :instrumentor        => Excon::StandardInstrumentor
  :instrumentor_name   => "excon"
  :method              => :post
  :middlewares         => [
    Excon::Middleware::Hijack
    Excon::Middleware::ResponseParser
    Excon::Middleware::Expects
    Excon::Middleware::Idempotent
    Excon::Middleware::Instrumentor
    Excon::Middleware::Mock
  ]
  :mock                => false
  :nonblock            => true
  :omit_default_port   => false
  :path                => "/v1.16/images/create"
  :persistent          => false
  :port                => 2376
  :query               => {
    "fromImage" => "redis"
    "tag"       => "2.8"
  }
  :read_timeout        => 60
  :response_block      => #<Proc:0x007fa83b071af8@/Users/fish/.rvm/gems/ruby-2.2.1@preview/gems/docker-api-1.22.4/lib/docker/image.rb:296 (lambda)>
  :retries_remaining   => 4
  :retry_limit         => 4
  :scheme              => "https"
  :ssl_ca_file         => "/Users/fish/.docker/machine/machines/default/ca.pem"
  :ssl_verify_peer     => true
  :tcp_nodelay         => false
  :thread_safe_sockets => true
  :uri_parser          => URI
  :versions            => "excon/0.45.4 (x86_64-darwin14) ruby/2.2.1"
  :write_timeout       => 60
excon.response
  :body          => ""
  :headers       => {
    "Content-Type" => "application/json"
    "Date"         => "Fri, 06 Nov 2015 15:57:56 GMT"
    "Server"       => "Docker/1.9.0 (linux)"
  }
  :local_address => "<IP_ADDRESS>"
  :local_port    => 63456
  :reason_phrase => "OK"
  :remote_ip     => "<IP_ADDRESS>"
  :status        => 200
  :status_line   => "HTTP/1.1 200 OK\r\n"
 => #<Docker::Image:0x007fa83b9c0988 @id="2.8", @info={"id"=>"2.8", :headers=>{}}, @connection=#<Docker::Connection:0x007fa83b9cb428 @url="tcp://<IP_ADDRESS>:2376", @options={:client_cert=>"/Users/fish/.docker/machine/machines/default/cert.pem", :client_key=>"/Users/fish/.docker/machine/machines/default/key.pem", :ssl_ca_file=>"/Users/fish/.docker/machine/machines/default/ca.pem", :scheme=>"https"}>>

Let me know if I can provide any more information.  Thanks!

Darn, looks like we're stealing the response body out from under Excon.
Docker::Image.create('fromImage' => 'redis', 'tag' => '2.8') { |chunk| puts chunk }

This'll print out the JSON we need.

  Will need to start thinking of other ways to get the ID then.

We solved this by simply doing Docker::Image.get(image_name) after the create... Not sexy, but it works ;)

@foeken I changed the gem to do just that itself.  Should be working in v1.25.0 without the additional .get now.


Not compatible with this.props.history.push?

When going to another page using this.props.history.push, I can't seem to use this with a protected route stateless component which restricts the access of a page to a view when no user is logged in.

Here's my code. When I go to another page(using this.state.push), it won't display unless I refresh it.

It also doesn't seem to work with the <Link to='/home'> tag.

Interesting, do you have an error in the developer console?
Do you mind creating a small repository showing this issue? Thanks. Could you reproduce it using the examples?

i'll send it on a zip.

myproject.zip
Steps to run:

npm install
npm run build:all
to start: npm run dev:unix (if you're in linux)

I didn't receive an error in the console. Oopps. my bad. It's an outdated project that I sent you .. wait..
myproject.zip
Here.
After the 3 steps,
You have to register an account so that you could go to /home. then create a farm. farmlist is a protected route, the same is true with the farm/farmId. They change links but don't render.

Thanks, I'll look at it tomorrow (too late here).

Ok. thanks

Your app doesn't build on my side:
SyntaxError: src/views/dumb/activityForm.jsx: Unexpected token (15:2)
  13 |
  14 | const ActivityForm = ({ onInputChange, formErrors }) => (
> 15 |   <Grid fluid style={styles.root}>
     |   ^
  16 |     <Row center="xs">
  17 |       <Col xs={12}>
  18 |         <Paper zDepth={0}>

I'll try to isolate the problem in one of my example.

I wasn't able to reproduce the issue, I did the following test:
diff --git a/examples/React-router/src/Components/Home.js b/examples/React-router/src/Components/Home.js
index ea57d48..57692f0 100644
--- a/examples/React-router/src/Components/Home.js
+++ b/examples/React-router/src/Components/Home.js
@@ -6,11 +6,13 @@ import Navigation from './Navigation';

 const sleep = ms => new Promise(r => setTimeout(r, ms));

-async function Home() {
+async function Home(props) {
   await sleep(1000);

   const style = {backgroundColor: '#2196F3'};

+  props.history.push("/routeA")
+
   return (

I was redirected to /routeA and saw the routeA component.
Could you maybe try to reproduce it in the React-router example?

do you have a gitlab account? I'll invite you. I seem to mess it up. Some hidden files with the prefix . haven't been copied.

https://gitlab.com/sekiryuutei47/testproj/
Here it is.
Steps:

npm i
npm run build:all
npm run dev:unix
After the 3 steps,
You have to register an account so that you could go to /farmlist. then create a farm. farmlist is a protected route, the same is true with the farm/farmId. They change links but don't render.

p.s. A protected route is a route that only logged in user could access.

Ow, it rendered probably because /routeA isn't a protectectedRoute.

Here's the list of protected routes.

I would like to help you really but I need a way to reproduce easily your issue in order to fix quickly.
Could you please reproduce the issue in my minimal React-router example available in this repo?

I found this article, https://github.com/ReactTraining/react-router/issues/4975
We have the same problem, but the problem occurs only when I use async-reactor which is actually strange. I tried the React-router example link that you've sent but I can't seem to reproduce the error.

Are you using this one?

No, async-reactor is not using shouldComponentUpdate.


Codegen

Take over from Roman's nice patch https://github.com/google/souper/pull/504 :)
Some test cases are not passing. I'll reply here once the PR is good for review.

@googlebot I consent.

@googlebot does not work on PR's with commits by more than one author.

This patch is ready for review. @regehr

what happens to the old souper2llvm in this patch? shouldn't you rename it as old-souper2llvm or something? otherwise we end up with two programs of the same name and this is likely very confusing

what happens to the old souper2llvm in this patch? shouldn't you rename it as old-souper2llvm or something? otherwise we end up with two programs of the same name and this is likely very confusing

@regehr fixed :)

thanks!


Sends the right templateStrategy to the padding calculation to use th…

…e right constraints
This was fixing error it setting the padding for a container.

Will close this PR, as a new PR #467 was created to fix the conflicts in this branch. The mentioned PR is a copy of this one.


metadata.xml does not support property name "results"

OpenUI5 version: 1.67.1
Browser/version: Newest Chrome
Steps to reproduce the problem:

Inside webide create a new application from template (Master/Detail)
Use local metadata.xml with only one EntityType + EntitySet:

EntityType:
<EntityType Name="ResultEntity"> 	<Key> 		<PropertyRef Name="results"/> 	</Key> 	<Property Name="results" Type="Edm.String" Nullable="false"/> </EntityType>
EntitySet:
<EntitySet EntityType="Model.ResultEntity" Name="ResultEntitySet"/>

Bind results property to some control
Start app with mockserver

What is the expected result?
It shows auto generated values from property results
What happens instead?
It shows a error because of the property name "results".
Does not happen with other property names like "result".
Any other information? (attach screenshot if possible)

Hello @marc4F ,
Thank you for sharing this finding. I've created an internal incident. The status of the issue will be updated here in GitHub.
Regards,
Petya Bogdanova
(UI5 Dispatcher)


⚠ Bofrost.fr has degraded performance

In f903335, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 853 ms

Resolved: Bofrost.fr performance has improved in 69df390 after 8 minutes.


Fixed crash in fused location provider in stopSensing

Card [N.11]
Fixed:

crash of the fused location provider when it is stopped

@tedschmidt shouldn't this go to master also?

@orhan89 it could but since no apps of ours use the fused location provider I chose to use the develop branch. But if you think we should use the master because third party developers could have this issue, then we should indeed create a hotfix.


Presto's tests are very flaky

Some of the tests in Presto are flaky and fail randomly.  It's difficult to contribute code because I have to manually switch off all tests except for the module I'm working on (presto-client, for example, fails 100% of the time on my machine).
If you look at the build history in travis, you can also see a long continuous streak of failure on master: https://travis-ci.org/facebook/presto/builds
From the travis log, it looks like one frequent failures is tests being OOM killed.  Travis provides 3GB of memory for building, which should be sufficient.  However, the heap size + perm gen for maven and the tests exceeds the total available memory.
For now, I propose doing this to make the build succeed: https://github.com/facebook/presto/pull/1712

I spent a while fixing our tests, and tracked down several race conditions. If you're still having problems try setting the surefire thread count to 1

Good work!


[STEP-1998] Deprecate bitrise-add-trace-sdk Step

Description
This PR is deprecates the bitrise-add-trace-sdk as it is not supported anymore

 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.


camera zoom not not working

camera zoom outer limit resets every time an interface is opened, i play mostly always zoomed all the way out but when i log in i either cant zoom out at all or it resets when i  open any interface

Fixed, wait for update


Calculate profit

[ ] New property for desired fiat currency
[ ] Get BTC exchange rate for the selected currency
[ ] Check if currency is supported at all
[ ] Modify electricity cost to be in this native currency
[ ] Convert mBTC to fiat
[ ] Deduct electricity costs from fiat
[ ] Print as profit, but only if power usage is > 0, otherwise it's pointless

https://blockchain.info/ticker
Is there a better one with more currencies?

https://www.coindesk.com/api/
Requires credit.


API migration, direct client side calls to new API, fixes

Coverage decreased (-11.0002%) to 45.995% when pulling ecbd513689db15164d9d5e904a11af87f3356c37 on maxhq:api-migration into 9910eb9bab4d85273802497e3f580702f21f49f0 on openxpki:develop.


feat: add support for ingress e2e test framework

Signed-off-by: bitliu<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
Fixes: https://github.com/alibaba/higress/issues/134
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #133 (62b2d15) into main (b410fc9) will increase coverage by 0.44%.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #133      +/-   ##
==========================================
+ Coverage   25.88%   26.32%   +0.44%
==========================================
  Files          26       26
  Lines        4524     4524
==========================================
+ Hits         1171     1191      +20
+ Misses       3277     3257      -20
  Partials       76       76

Impacted Files
Coverage Δ

pkg/bootstrap/server.go
62.97% <0.00%> (+7.63%)
:arrow_up:


Add csi-driver base image flavor

Adds the CSI base fravor.
The base image is automatically build by the GH workflow here: https://github.com/cert-manager/base-images.

Adding lgtm based on @ThatsMrTalbot' review.
@ThatsMrTalbot feel free to add yourself to the OWNERS file.

/approve


multiple manifest ibmcloud fn deploy

I'm can multiple manifest to organaze my functions:
package.yml
packages:
  procjet-production:
    version: 1.0
    license: Apache-2.0

function-production.yml
actions:
  function-production:
    function: dist/function.bundle.js
    runtime: nodejs
    limits:
      memorySize: 192

manifest.yml
include:
  - manifests/package.yml
  - manifests/function-production.yml

and run:
ibmcloud fn deploy -m manifest.yml
I got the follow error:
==> yaml: unmarshal errors:
==> line 1: field include not found in type parsers.YAML

Github Copilot give me a awser:
package main

import (
    "fmt"
    "io/ioutil"

    "gopkg.in/yaml.v2"
)

type Manifest struct {
    Include []string `yaml:"include"`
}

func main() {
    data, err := ioutil.ReadFile("manifest-beta.yml")
    if err != nil {
        panic(err)
    }

    var manifest Manifest
    err = yaml.Unmarshal(data, &manifest)
    if err != nil {
        panic(err)
    }

    fmt.Println(manifest.Include)
}

It looks like you have found your answer. Terrific. I will therefore close this issue.

But this not be include em source code?


Gzip compressor level?

In your benchmarks, which gzip implementation did you use + what compressor settings?

It's zlib with default compression

Thanks, that's what I would have guessed. FWIW, it's worth being explicit about this in the readme.


Add Mockingbird

Project URL
https://github.com/Farfetch/mockingbird
Category
Other Testing
Description
Simplify software testing, by easily mocking any system using HTTP/HTTPS, allowing a team to test and develop against a service that is not complete, unstable or just to reproduce planned cases.
Why it should be included to awesome-ios (mandatory)
Will help developers to find out a great tool to improve tests and development.
Checklist

[ ] Has 50 GitHub stargazers or more
[x] Only one project/change is in this pull request
[x] Isn't an archived project
[ ] Has more than one contributor
[x] Has unit tests, integration tests or UI tests
[x] Addition in chronological order (bottom of category)
[ ] Supports iOS 9 / tvOS 10 or later
[x] Supports Swift 4 or later
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

@erickjung Can you fix the conflicts?

@erickjung Thanks for contributing!


Add Imail High School

Note: This is not imail.sunway.edu.my, this is a high school from Vietnam.

@lengoc-quang The domain registrant for imail.edu.vn is Nguyễn Quốc Thái (Nguyen Quoc Thai). This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.


Separate Sinatra::Streaming (or lazy depend on eventmachine)

Hello,
This request might sound weird, but sinatra-contrib gem dependency on eventmachine causes issues with Ruby 1.9.x (1.9.2 and 1.9.3) under Windows.
Users trying to use Sinatra::Reloader during development add sinatra-contrib gem, which depends on eventmachine >= 0
This results in attempt to install latest stable gem (0.12.10) which has known issues under Windows (ala: does not compile).
After lurking on the internet for answers, end installing eventmachine 1.0.0.beta.4.1 (using --pre during gem install) but for some, under some weird circumstances with Bundler, dependencies are not met and it attempts to install eventmachine 0.12.10, again resulting in failure.
I believe is caused by installation on different GEM_PATH than GEM_HOME, but need more investigation.
May I suggest change sinatra/streaming.rb requires and remove runtime dependency on eventmachine?
require 'sinatra/base'
begin
  require 'eventmachine'
rescue LoadError
  abort 'EventMachine is required to use Sinatra::Streaming. Please `gem install eventmachine` first.'
end
require 'backports'

Thank you

I will be removing the eventmachine dependency from sinatra/streaming as soon as I find time.

@rkh wow that was fast!, thank you! ::love::


Automate publishing of the dedicated kube-aws documentation site

Print node.js version to debug when the script failed due to an incompatible node.js version

nvm for version-locking node.js isn't available in Travis CI's golang image

Read the repo slug(user/reponame) from env vars so that we do not need to hard-code it

Improve make publish-docs to support various cases

travis builds and local runs against a forked repo

This is already verified to work on my fork of kube-aws.
Let's see it works here, too.


ECDSA, phpseclib and PHP7: what is the current status?

Hi
I tried using ES512 but got the following error:
Fatal error: Uncaught InvalidArgumentException: phpseclib 1.0.0(LTS), even the latest 2.0.0, doesn't support PHP7 yet in /.../vendor/namshi/jose/src/Namshi/JOSE/Signer/OpenSSL/ECDSA.php:15
But phpseclib seems to be alright these days with PHP 7 (their builds pass on PHP 7 and 7.1, see https://travis-ci.org/phpseclib/phpseclib)
If I comment out the 2 version check blocks in Signer/OpenSSL/ECDSA.php then it seems to be working OK.
Is the block for PHP 7 still justified? If yes, could it at least be made more explicit in the README of this project? Also, would it be possible to emphasize the need to require phpseclib for ECSDA support in the same README?
Thanks

I'm having the same issue on PHP 7 and agree with @matrey that it seems to make sense to remove this block.

I use phpseclib on PHP 7.1 without issues.

This is still an issue for me

phpseclib 2.0.21
jose 7.2.3

https://github.com/namshi/jose#deprecation-notice


Cilium Operator leases have a default TTL of 60 seconds

Contrary to the cilium-agent, the cilium-operator does not have a kvstore TTL flag. We should add one because right now it is using the default value of etcd's library which is 60 seconds.

@aanm Please inform me if this is reasonable
So we have to define a new flag in operator/cmd/flags.go for specifying the value Time-to-live for the KVstore lease and use them instead of defaults.LockLeaseTTL in the places like https://github.com/cilium/cilium/blob/master/operator/cmd/kvstore_watchdog.go#L61

@aanm Please inform me if this is reasonable
So, we have to define a new flag in operator/cmd/flags.go for specifying the value Time-to-live for the KVstore lease and use them instead of defaults.LockLeaseTTL in the places like https://github.com/cilium/cilium/blob/master/operator/cmd/kvstore_watchdog.go#L61

@NikhilSharmaWe I think it just as simple as adding this code https://github.com/cilium/cilium/blob/d7af9ef37fa772ac8379d82460ff78cdfc12386e/daemon/cmd/daemon_main.go#L538-L540
in the operator's flags.go


[Swift-2.0][Examples] update Swift 2 examples to do/catch instead of try!

In Swift 2, try! ... removeItemAtPath will assert if the file doesn't already exist and try? shows a warning in Xcode, so I'm using empty catch blocks instead. /cc @segiddins @tgoyne

:+1:


Async execution causes errors in distributed computation.

bind_exec() method in python/module/executor_group.py may cause libzmq communication errors in distributed computation since output arrays of executors are tried to be read before they are filled completely. To my findings, the related code part may be fixed as below.

        if self.for_training:
            self.grad_arrays = [[exec_.grad_arrays[i] for exec_ in self.execs]
                                for i, name in enumerate(self.arg_names)
                                if  exec_.grad_arrays[i].wait_to_read() or name in self.param_names]
        else:
            self.grad_arrays = None

        data_names = [x[0] for x in data_shapes]
        if self.inputs_need_grad:
            self.input_grad_arrays = [[exec_.grad_arrays[i] for exec_ in self.execs]
                                      for i, name in enumerate(self.arg_names)
                                      if exec_.grad_arrays[i].wait_to_read() or name in data_names]

Not sure anymore :) Depending on -n parameter of launch.py, different errors are raised. Examining.

I'm much more sure now :) The second sentence in my previous comment was due to MxNet version conflict. Please forget it. However, my first comment seems true but my solution is syntactically incorrect, semantically correct :) The correct solution, to me of course, is as below:

        if self.for_training:
            self.grad_arrays = [[exec_.grad_arrays[i] for exec_ in self.execs if exec_.grad_arrays[i].wait_to_read() or True]
                                for i, name in enumerate(self.arg_names)
                                if name in self.param_names]
        else:
            self.grad_arrays = None

        data_names = [x[0] for x in data_shapes]
        if self.inputs_need_grad:
            self.input_grad_arrays = [[exec_.grad_arrays[i] for exec_ in self.execs if exec_.grad_arrays[i].wait_to_read() or True]
                                      for i, name in enumerate(self.arg_names)
                                      if name in data_names]

This issue is closed due to lack of activity in the last 90 days. Feel free to reopen if this is still an active issue. Thanks!


is codislab/codis still be able to use on latest or 3.3.6 pika?

is codislab/codis still be able to use on latest or 3.3.6 pika?
i saw sharding should be disabled in 3.3.6 so was wondering if codis can still be used with this.

shading is still able in 3.3.6 but not in unstable

@chejinge having this problem: can you pls help how to resolve?
i've tried pika 3.3.6 and works with codis-server BUT pika will get this error, i've already set the mode to sharding and slots at 1024
but...
<IP_ADDRESS>:19000> set a b
(error) ERR Partition not found
any instructions on setting up pika to use with codis?
do i have to use pika_codis branch or pika_support_codis branch or this version of codis?
https://github.com/kernelai/codis/blob/release3.2-dev/doc/tutorial_zh.md#6-codis-多表版本使用说明
with reference to this question:
https://github.com/OpenAtomFoundation/pika/issues/1562
pls help provide a definite guide to using pika with codis. thx!

@chejinge having this problem: can you pls help how to resolve?
i've tried pika 3.3.6 and works with codis-server BUT pika will get this error, i've already set the mode to sharding and slots at 1024
but...
<IP_ADDRESS>:19000> set a b
(error) ERR Partition not found
any instructions on setting up pika to use with codis?

do i have to use pika_codis branch or pika_support_codis branch or this version of codis? https://github.com/kernelai/codis/blob/release3.2-dev/doc/tutorial_zh.md#6-codis-多表版本使用说明 with reference to this question: #1562
pls help provide a definite guide to using pika with codis. thx!

pika3.3.6 support codis but it has rewrited, you can use pika_codis branch or pika_support_codis branch

@chejinge which do you suggest? pika_codis or pika_support_codis branch?

@chejinge which do you suggest? pika_codis or pika_support_codis branch?

pika_codis 我们内部是使用的pika 3.3.6+自己实现的codis  没有使用过其他分支，您用pika_codis吧，这个是比较符合的代码

pika_codis 我们内部是使用的pika 3.3.6+自己实现的codis 没有使用过其他分支，您用pika_codis吧，这个是比较符合的代码

pika_codis 我们内部是使用的pika 3.3.6+自己实现的codis 没有使用过其他分支，您用pika_codis吧，这个是比较符合的代码

@chejinge having this problem: can you pls help how to resolve?
i've tried pika 3.3.6 and works with codis-server BUT pika will get this error, i've already set the mode to sharding and slots at 1024
but...
<IP_ADDRESS>:19000> set a b
(error) ERR Partition not found
any instructions on setting up pika to use with codis?

do i have to use pika_codis branch or pika_support_codis branch or this version of codis? https://github.com/kernelai/codis/blob/release3.2-dev/doc/tutorial_zh.md#6-codis-多表版本使用说明 with reference to this question: #1562
pls help provide a definite guide to using pika with codis. thx!

pika3.3.6 support codis but it has rewrited, you can use pika_codis branch or pika_support_codis branch

pika_codis 我们内部是使用的pika 3.3.6+自己实现的codis 没有使用过其他分支，您用pika_codis吧，这个是比较符合的代码

@chejinge thank you!

@chejinge thank you!

nothing


Bug: Lint a file takes the create date and uses that as filename.

When I lint a file the create date is taken and used as filename.
This happens for:
title
alias
linter-yaml-title-alias
see before:

and after:

Thanks for reporting this!
This looks like it is a bug with the links present in the heading since the text is often ignored. Could you provide a minimum reproducible example? I see the images, but that is not enough to know how this is happening without some text to pull in that causes the issue.

the problem is the # [[test]] changing that to # test fixes it.
`---
UUID:<PHONE_NUMBER>5858
DateStamp: 2022-10-10
Updated:
publish: false
language: de
Vault: Privat
title: "test"
tags:
aliases: []

[!METADATA]-

Created:: [[2022-10-10]]
Related::
Summary::
Content::
up::
Topics::
Type:: #type/note/normal
Status:: #status/seed
Related::
Reference::

[[test]]
Daily Log
Dies ist ein Test

mal schauen
wie das aussieht
CSS Styling ist doof.

Und der Rest
das ist der Rest
#test
`

Ok. I am pretty sure I see the problem. If I no longer ignore linka for thia rule it should start working again.

cool, looking forward to it.

This change should now be on master. Please let us know if the issue is not fixed on master or in the next release.

thanks will take a look.
The metadata block is an idea I grabbed from somewhere.. I want to put data in there which I need, but don't want to see (looking forward to a way to hide the yaml in edit / preview mode).
Some people put the data at the end, but I like it at the top so that I can easily access it in larger notes and my notes have the correct data. (you don't want to see my templater files 😀 ).
Having H1 as a link is also coming from a lot of templates.


Keptn test task successful when test duration is few seconds but fails to poll when duration is few minutes

jes version: 0.3.0, keptn v 1.2.0
I'm running a jmeter test from Keptn. When I try test duration 30 seconds, I get jmeter summary in keptn job sequence log. But when I try 300s I don't see the test summary. The job fails with error:
"Error while creating job: polling for job job-executor-service-job-0c6ae285-0aca-472d-a237--000-001 timing out after 5m0.403875056s: max poll count reached for job"
But when I check the pod logs I see the test is running fine.
jes pod logs:

jes task logs:

Found the knowledge gap. Default max poll is 5 min and my test was also 5 min, hence polling period finished before test and error happened. Increased maxPollDuration in the job config yaml and now its fine


Remove isolate script when running unittest

For #11264
Looks like this fix #11353 is incomplete. we need to remove isolation for this as well with unittest.

Codecov Report

Merging #11378 into master will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master   #11378      +/-   ##
==========================================
- Coverage   60.98%   60.96%   -0.02%
==========================================
  Files         609      609
  Lines       33531    33531
  Branches     4741     4741
==========================================
- Hits        20448    20442       -6
+ Misses      12637    12059     -578
- Partials      446     1030     +584

Impacted Files
Coverage Δ

...rc/client/common/process/internal/scripts/index.ts
70.12% <100.00%> (ø)

src/datascience-ui/react-common/arePathsSame.ts
75.00% <0.00%> (-12.50%)
:arrow_down:

src/client/common/utils/platform.ts
64.70% <0.00%> (-11.77%)
:arrow_down:

src/client/linters/pydocstyle.ts
86.66% <0.00%> (-2.23%)
:arrow_down:

src/client/datascience/debugLocationTracker.ts
76.56% <0.00%> (-1.57%)
:arrow_down:

src/client/common/process/proc.ts
14.49% <0.00%> (-0.73%)
:arrow_down:

src/client/testing/main.ts
14.38% <0.00%> (ø)

src/client/common/editor.ts
8.25% <0.00%> (ø)

src/client/linters/flake8.ts
85.71% <0.00%> (ø)

src/client/linters/pylint.ts
98.27% <0.00%> (ø)

... and 139 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f96e762...325b763. Read the comment docs.


editor error for array parameters.

Problem statement
When trying to generate swagger.json for parameters having array values, its generating in the below-mentioned structure which is giving an error in http://editor.swagger.io/.
Steps to reproduce
type Ele struct {
        SomeId  int    `json:"someId,required"`
	SomeName string `json:"someName,required"`
}

// swagger:parameters Request
type Request struct {
  Arr []Ele `json:"arr,omitempty"`
}

Generates a swagger.json of the format
"parameters": [
...
{
            "type": "array",
            "items": {
              "$ref": "#/definitions/Ele"
            },
            "name": "Arr",
            "in": "query"
          }
...
]

"definitions": {
...
   "Ele": {
      "type": "object",
      "properties": {
        "SomeName": {
          "type": "string",
        },
        "propId": {
          "type": "integer",
          "format": "int64",
        }
      },
    },
...
}

Error from Editor says:
items $refs cannot match any of the following: "*#/definitions*"
When editing the generated structure to the following structure for array its getting accepted.
name: Arr
in: body
schema:
	type: array
	items:
	$ref: '#/definitions/Prop'

Is there any thing I'm missing?
Environment
swagger version: 2.0
go version: 1.8.3
OS:  OSX

query arguments don's support complex objects, just simple types

@casualjim thanks for the reply.
Added in: body
// swagger:parameters Request
type Request struct {
  //in:body
  Arr []Ele `json:"arr,omitempty"`
}

It's generating correctly, but when I have two array parameters
// swagger:parameters Request
type Request struct {
  //in:body
  Arr []Ele1 `json:"arr,omitempty"`

   //in:body
  Arr []Ele2 `json:"arr,omitempty"`

}

Now i'm getting an error:
Operations must have no more than one body parameter
Can you refer me to the documentation that would be of help?

there can be only 1 body, this is described in the swagger specification: https://swagger.io/specification/
information about the annotations can be found here: https://goswagger.io/generate/spec.html
And examples you can find by either generating code for a swagger spec
or by looking here which is used in our unit tests: https://github.com/go-swagger/go-swagger/tree/master/fixtures/goparsing/classification
Every example also has annotation: https://github.com/go-swagger/go-swagger/tree/master/examples


examples.remote-fib

I executed the examples.remote-fib action using the UI, and noticed the following error:
ImportError: No module named six.moves
I don't think this is "user error" on my part.. so creating this issue to track.

Just tested with st2vagrant, version 2.8.1, seems to work with no problems.


chore(helm): default image tag to AppVersion

Description
This adds a new helm "function" that defaults the image tag to the AppVersion if it is not provided.
The removes one spot where the app version needed to be copied at releases.
This is already in place on the frontend, I'd been meaning to port this to the other repos -- also see https://github.com/Substra/orchestrator/pull/159 which is this but for the orchestrator.
How has this been tested?
Check it works the same way:
git switch main
helm template charts/substra-backend > old-render.yaml
git switch chore-helm/default-appversion
helm template charts/substra-backend > new-render.yaml
diff old-render.yaml new-render.yaml

I also tried helm template charts/substra-backend --set server.image.tag=woop to check it (and only it) was set the given value.
Checklist

[x] changelog was updated with notable changes
[x] documentation was updated

Checks aren't passing:

pylint is failing but that's from main, this PR doesn't touch python code
There already is a backend chart 22.3.3 due to patch shenanigans, I'll make sure this is OK with Guilhem before resolving and merging this.

Can you try to rebase ?  It should fix the issues you got with the CI

LGTM!


Advice session on 3nd May

Routing

Configure routing rules to ensure each site can only access the correct server
Ensure correct source and destination addresses are used in IPsec tunnels

Certificate Management Issues

Design a certificate distribution mechanism to replace the current Vagrant method
Consider using pre-shared key (PSK) authentication as an alternative to PKI certificates

Scalability Issues

Evaluate using containerized solutions to reduce costs per client
Consider developing the service as a scalable web service for multi-client support
Ensure persistent storage is correctly mapped from containers to corresponding devices

Must do
Configure routing rules that the cloud gateway decides where the packet should go by source address (currently the server to go is hardcoded in the client site gateways)
Full mark if we also do this
Containerize servers on the cloud
Bonux points
A realistic and feasible way to distribute certificates (currently it's vagrant cp)


feat: try impl type aliases

Related issue(s)

Resolves https://github.com/noir-lang/noir/issues/735
Description
Summary of changes

Dependency additions / changes

Test additions / changes

Checklist

[ ] I have tested the changes locally.
[ ] I have formatted the changes with Prettier and/or cargo fmt with default settings.
[ ] I have linked this PR to the issue(s) that it resolves.
[ ] I have reviewed the changes on GitHub, line by line.
[ ] I have ensured all changes are covered in the description.
[ ] This PR requires documentation updates when merged.

Additional context

Ah, I had forgotten about this PR, apologies.
My current thinking is we should get it to a state where we can merge it easily (ie without generics) and work on adding the rest later. I'll review this again soon and let you know any comments I have.


where is linux_musl-x64-67_binding.node ?

error when building docker
><EMAIL_ADDRESS>install /web/node_modules/node-sass
> node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v4.9.0/linux_musl-x64-67_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v4.9.0/linux_musl-x64-67_binding.node":

HTTP error 404 Not Found

all info that I can provide is version of node inside container

node -v v11.0.0:

Why it tries to download that version?

Are you using node:alpine as your starter image? If so, try changing your Dockerfile's FROM to a different version of node:alpine. node:10-alpine worked for me after I cleared all images, npm cache, rebuilt sass, etc.
Seems like an issue with the newest version of node:alpine (11). They pushed a small update ~6 hours ago.

yeah, it worked 10-alpine. required couple of hours to figure out why it stopped working today :)

I opened an issue on the official docker-node repo (the one that makes updates to node:alpine and such) https://github.com/nodejs/docker-node/issues/895

Duplicate of #2521 please subscribe to that issue to be notified when it is resolved


Keep track of already-verified .chd files to avoid having to re-convert them every time

This idea was described by ZeroBANG on Reddit.

I think a nice way of implementing this would be to keep a cache file (perhaps in the folder with the .chd files or perhaps just in ~/.cache or something). It would record successful validations with the name of the .chd, the SHA-1 of the .chd, and a reference to the game in the Datfile.

The reference to the game in the Datfile would need to store enough information so that we could tell if the game has changed in a new version of the Datfile. A simple way of doing that would just be to copy the information about the individual files from the Datfile into the cache file and compare that with the current Datfile when running.

There could be an option to skip verifying the SHA-1 of previously verified .chd files, since that would just be checking for bitrot/accidental modification. Maaaybe that option should be on by default.

In linux, i use extended attributes for this. Unfortunately, this wouldn't work in windows (windows does have a similar kind of metadata for ntfs, but it requires administrative rights). The advantage is that you can move the files. A disadvantage is that copying the files, or hardlinking them, nukes the information instead of copying it unless you pass a uncommon switch (which isn't in normal copy paste iirc).

I thought about writing a standard sha1sum file next to the verified files, with a comment that includes an additional hash of all the game details from the Datfile. So that way verifydump could recompute that hash of the game details and see that it has already been verified, and you could also use the standard sha1sum to verify against bitrot if you wanted.
But I dunno if people would appreciate having a hash file in the folder with their .chds and having to learn what that's for, so it might just be simpler to write a custom file to ~/.cache or similar 🤔

People will totally delete files they think are 'meaningless'. The only reason to have those files is the hope that as people move and rename the originals they also move and rename those files, and that's kind of a high expectation from lusers.
A .cache file is best if you want 'cross platform'. Problem is that these things are very very fragile if the user modifies/moves/renames the file. Having to repeat a bit of work is not the worst possibility - the worst possibility is the luser replacing a file with a different file with the same name and the cache saying 'this is the checksum' when the file is now completely different.
I prefer to use the extended attribute method so i don't track all that noise.

Yeah, really good points. I think it's best then if verifydump just does the caching of results behind the scenes to keep things simple for the users. If it can use that cache to speed things up then great, and if not because things have moved around then it'll just slow things down somewhat for the that first verification after the move.

Maybe you can store the 'date of verification' and compare it to the 'date changed' to invalidate cache entries. Complexity, but from what i've seen of your program, you handle that well.

Oh that's a nice idea. I think if the file path, size and modification date match what we verified already then that's a pretty strong signal that it's the same file. So it would be sensible to skip verifying the .chd SHA-1 in those cases, with an option to override and do the check anyway if the user wants. I'll give that a try. Thanks!

Speaking of chd, i'm tempted to do a zerg rush of opening bug reports in the emulators that say they support the format, because they aren't supporting 'delta chds' because those require loading the original to get them working.
MAME does this with software lists, but other emulators that aren't so obsessive compulsive about verifying every last dump they load, should have at least the option to make loading a delta chd activate a scan of the directory where they are (at least) to find the parent. Without this delta chd is rather pointless in emulators because you'd need to have the users specifying the parent (no one would use delta chds).
Although i think this is not a problem just for verifying delta chds, because i think their data sha1 is the correct even if they don't have the data, you have the problem that you're not using the data sha1 but calculating the track manually... so you probably should do this when you have the possibility.
Maybe it's best to wait for the fabled python api for chd though (or make sure than when you write it, you consider this case).

For for the slow reply. I have to admit I haven't looked into delta chds yet. Are they useful in the context in managing Redump collections? Can you do something fancy like have the different regions of the same title using smaller delta files?

They're more useful for older games, because modern virtual filesystems compress their data, and slight changes earlier in the stream, affect the compressed bytes later in the stream.
In effect, delta chds function as a form of softpach for cds, and yes, they can be used to reduce chd size if that problem in the first paragraph doesn't occur. For instance, imagine a game with two cds that only has two cds because the devs tried, but couldn't manage to fit it all in one.
Most of the data is similar, so making the second cd image a delta chd of the first, could be effective.
It would also be useful for user deltas for romhacks, if it had a way to directly apply a romhack to a chd and produce a delta - but it doesn't, that'll have to be us peons doing that when a libchd like library, but for writing happens.
Also note, that libchdr (the library) has a extension for a theoretical 'more than 1 level' of delta-chd(s) for the cases were for example, you want to do that cd1-2 trick but also want a romhack, the romhack of cd2 could have to fetch bytes from romhack->cd2->cd1. MAME didn't adopt this afaik, so it's dead in the water, because MAME is the only chd writer for now.

I've implemented this locally since I really wanted to speed up re-scans and don't mind sharing what I wrote.
What I did:
Added new optional arg cache_file that is a path to a file that will hold cached verified file details in a sqlite db (lets user put it wheverver they want--I have a .meta dir per system that holds the dat, cuefiles if available, script for running verifydump, and now the cache db). If arg is not supplied then program runs as it does now; if supplied see below.
For CHDs:
If a chd is successfully verified, store the file name, file size, and file modified time along with the cue_verification_result, game name from the dat, and for each rom in that game in the dat the rom name, rom size, and rom hash.
For re-scans, check if the chd file name exists in the cache and if the file size and modification time match. If so, check if the new parsed dat has a game name that matches the cached one and check this game's rom list for the correct number of roms, rom names, rom sizes, and rom sha1s. If they all match up, use the cached cue_verification_result and game from the parsed dat and skip the actual file analysis. If anything does not match then fully analyze the file as before.
For RVZs:
If a rvz is successfully verified, store the file name, file size, and file modified time along with the matching sha1 of the uncompressed file.
For re-scans, check if the rvz file name exists in the cache and if the file size and modification time match. If so, use the cached sha1 of the uncompressed file and skip the file analysis.  If anything does not match then fully analyze the file as before.
I can put this in a PR if you want--not saying you have to implement it exactly the same as I just hit the use cases I could think of that I needed but it could give you some ideas. For instance, I didn't add a mode to do a full verification with caching on since you can just delete the cache db and get the same results.

Thank you for doing that work @Z-95. I'm not sure if I'll implement it the exact same way (mainly I think I'd have the cache files in ~/.cache or similar so that users won't have to be aware of the cache files to benefit from them), but it would be great to be able to refer to your work and use parts of it so if you'd like to fork the project on GitHub and publish your changes there then that would be very welcome. Thanks again!

Sounds good! I'll actually submit a PR from my fork as well so you or others can easily reference. I'll also set it so you have modification access so you can change it if you want or you can delete the PR if it rots or is no longer needed.

Perfect, thank you!


Add release notes for 0.123

@electrum Can you review it please? I don't really know how to review release notes.

Looks good

Will merge


[SVCS-542] Add PR Template for WB

Ticket
https://openscience.atlassian.net/browse/SVCS-542
MFR Counterpart
https://github.com/CenterForOpenScience/modular-file-renderer/pull/287
Purpose
Add PR Template to help the reviewing progress.
Changes
Add PULL_REQUEST_TEMPLATE.md to the root directory.
Side Effects
No
QA Notes
No
Deployment Notes
No

Coverage remained the same at 89.015% when pulling 831a4937a620616fd4a47562924006b9ab97894d on cslzchen:feature/pr-templates into 1dcc38940eeeb60caf4e0cbbd10338c131c0d965 on CenterForOpenScience:develop.

🍤 🍤 🍤


cnspec: 10.0.3 -> 10.1.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/mondoohq/cnspec/releases.
meta.description for cnspec is: An open source, cloud-native security and policy project
meta.homepage for cnspec is: https://github.com/mondoohq/cnspec
meta.changelog for cnspec is: https://github.com/mondoohq/cnspec/releases/tag/v10.1.3
Updates performed

Golang update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 10.1.3 with grep in /nix/store/pyvl518nz5xqar8sc329al0s5x0pahq1-cnspec-10.1.3
found 10.1.3 in filename of file in /nix/store/pyvl518nz5xqar8sc329al0s5x0pahq1-cnspec-10.1.3

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
cnspec

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/pyvl518nz5xqar8sc329al0s5x0pahq1-cnspec-10.1.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cnspec https://github.com/r-ryantm/nixpkgs/archive/b48e4543afa6e0967c6ec7a5b5d8e0feed3ab3d2.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/b48e4543afa6e0967c6ec7a5b5d8e0feed3ab3d2#cnspec

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/pyvl518nz5xqar8sc329al0s5x0pahq1-cnspec-10.1.3
ls -la /nix/store/pyvl518nz5xqar8sc329al0s5x0pahq1-cnspec-10.1.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

cnspec

Maintainer pings
cc @fabaff @mariuskimmina for testing.

Superseded by #285713


Fix two minor typos in README

Because I couldn't help myself.
@kris-nova please review

lol I suck at spelling - thank you so much for helping! Also you are the first woman besides me to contribute - and I freaking love that so much

Ok, now I feel like I need to contribute to some code. (Working in mostly Scala for the last year and I miss go and k8s so muuuuuuch!)


ability to test commands with generated/variable arguments

i have a script that writes to a logfile and it includes the date, so right now i'm not able to write a protocol that passes. here is an example of the error i get:
error:
  expected: /bin/sh -c "echo \"2019-03-06T22:15:12+00:00 - start: /directory - filename - test\" >> /Users/testuser/tmp/unrar.log"
  received: /bin/sh -c "echo \"2019-03-06T22:16:05+00:00 - start: /directory - filename - test\" >> /Users/testuser/tmp/unrar.log"

i imagine the ability to place a regex in my command is a straightforward way to solve this, any other ideas?

@soenkehahn some open questions before this can be tackled:

how should users indicate a regular expression in their protocol? what characters should signify to our parser/tokenizer that the following string should be taken as a regex? since $(...) and `...` will usually be interpreted by bash before arguments are passed to the syscall, maybe those are viable options?
i think we'll have to rethink how commands are parsed and matched, since argument for argument equality would no longer work. for example:- command: echo $(\d\s*\d)

should match echo 1 2 and echo 12, but currently the representation of those two commands coming from the script are not structured well to test the match. i'm curious if people have thoughts on how to adjust the way arguments are stored and matched.
can a regex be adjacent to text or should it be surrounded by whitespace/its own token? for example:- command: echo a$(\d)

should this be allowed, and match echo a1? or should users have to do- command: echo $(a\d)

@soenkehahn bump for opinion on the above questions

First I thought we could mark regexes by putting them into slashes, like in javascript. But then I realized that there's actually a good chance that normal commands will start and end with a slash, for example /usr/local/bin/ruby ./showDirectory.rb ./myDir/. So what about this:
protocols:
  - protocol:
      - regex: /bin/cp .*.txt .*.md

Re: how the arguments are matched: Could we match the regex against our canonical rendering of the whole command that is executed? (That would be Command::format, i think.) E.g. like this:
#!/usr/bin/env bash
/bin/cp foo.txt bar.md

protocols:
  - protocol:
      - regex: \/bin\/cp .*.txt .*.md

So then - regex: echo $(\d\s*\d) would match both echo 1 2 and echo 12. @matthandlersux: What do you think about that?
#124, which is about to be merged, is also somewhat relevant, since it changes the canonical representation from /bin/cp foo bar to cp foo bar. CC: @hallettj

sounds good... i spiked this out by initially trying to embed regexes into the command (using backticks as a delimiter), and while that isn't too complicated, it does not allow matching on different variants of spacing. i like your suggestion of just having the whole line be a regex... makes the parsing simpler and avoids complicated escaping logic.
new questions:

i would assume that with a format like you suggest, you could only have either a command or regex but not both, does that make sense?
should the regex assume that it is anchored on either end? ie. is - regex: /bin/cp .*.txt .*.md interpreted as - regex: ^/bin/cp .*.txt .*.md$?

i would assume that with a format like you suggest, you could only have either a command or regex but not both, does that make sense?

Yes, exactly. So a Step is either a yaml string, or an object, and that object has to have either command or regex, but not both.

should the regex assume that it is anchored on either end? ie. is - regex: /bin/cp ..txt ..md interpreted as - regex: ^/bin/cp ..txt ..md$?

Good question and I'm not sure. Maybe not, since that's what other tools do, e.g. grep. Maybe @astampoulis has an opinion?

I'm not sure! I would probably go for avoiding the anchoring-by-default, since that's more general, but I'm not sure if I can find a good use case.
One not very convincing case I came up with is -- let's say I want to say that some git command will run but don't care about which one, we could just do regex: ^/usr/bin/git, but something similar is doable  in the anchored case too.

my vote would be yes for automatic anchoring, only because it forces people to be explicit. ie, they need to put in .* if they actually want that. without anchoring, regex: /usr/bin/git matches something like chmod 700 /usr/bin/git, which would be confusing to debug. if you did want to match that, with anchoring, you'd have to specify .*/usr/bin/git before the test would pass, and the explanation of the failure would make that clear.

@matthandlersux: Sounds good to me.


Fatal error: "value" argument must not be a number

I'm getting this error message when trying to run this task:
Files: dist/xstyle/shim/pseudo.js.map -> xstyle/shim/pseudo.js.map
Files: dist/xstyle/shim/transition.js -> xstyle/shim/transition.js
Files: dist/xstyle/shim/transition.js.map -> xstyle/shim/transition.js.map
Files: dist/xstyle/shims.css -> xstyle/shims.css
Files: dist/xstyle/util -> xstyle/util
Files: dist/xstyle/util/getComputedStyle.js -> xstyle/util/getComputedStyle.js
Files: dist/xstyle/util/getComputedStyle.js.map -> xstyle/util/getComputedStyle.js.map
Files: dist/xstyle/xstyle.js -> xstyle/xstyle.js
Options: archive="deploy/deploy.zip", mode=null, level=1
>> Compressed 16974 files.
Archived dist/agrc/ -> deploy/deploy.zip/agrc/
Fatal error: "value" argument must not be a number

Here's my task config:
compress: {
    main: {
        options: {
            archive: 'deploy/deploy.zip'
        },
        files: [{
            src: deployFiles,
            dest: './',
            cwd: 'dist/',
            expand: true
        }]
    }
},

Thanks, in advance, for any ideas on how to solve this.
node: v6.9.1
grunt: v1.0.1

Does this still happen?

I don't think so. Thanks for the bump.


Cannot read property 'map' of undefined

More of a question than a bug report I think. Does this plugin support V2?
I'm trying to access this api
{
    resolve: 'gatsby-source-yodorada-webservice',
    options: {
      host: `https://api.iextrading.com/1.0/ref-data/`, // the absolute path to your RESTful API
      endpoints: [`symbols`], // the endpoints from where you want to fetch
      user: ``, // the login username
      password: ``, // the login password
      apiKey: ``, // the unique api key
      conflictPrefix: `yoId`, // rename conflicting fields, will be camelCased (eg: yoId)
      options: {} // additional options (not yet implemented)
    }

There is no api key or userid required. at Gatsby Develop I'm getting this error:
-source and transform nodesYodorada Webservice Error: TypeError: Cannot read property 'map' of undefined
Any suggestions would be appreciated.
UPDATE
It's no an authentication issue.
Looks like there may be an issue here
https://github.com/yodorada/gatsby-source-yodorada-webservice/blob/ff0ffd93d36da9501b176bd0b01280fb6fe1dfff/gatsby-node.js#L35
as res.data is undefined. If I change it to res.map I can see the nodes that are to be created but it fails with different error.
 Error: Could not find function loadNodeContent for plugin gatsby-source-yodora  da-webservice

In the end I used another plugin as the loadNodeContent error was a bridge too far for me today.
https://github.com/abonventre/gatsby-source-thirdparty

Hi, I am glad you found a solution.
I created this plugin to use exclusively with the RESTful API, that I once coded, see: PHP-Webservice-REST-API.
So it is not a surprise, it did not work out as you wanted.

All best and sending good coding vibes!


Backbone not attached to global in node environment

backbone.js:27 has:
factory(root, exports, _, $);
Should it be:
var root.Backbone = factory(root, exports, _, $);
Couldn't get it work otherwise.

Have you tried: global.Backbone = requiere('backbone'); yet?
On Tue, Sep 6, 2016, 07:10 Vesa Nikkilä<EMAIL_ADDRESS>wrote:

backbone.js:27 has:
factory(root, exports, _, $);
Should it be:
var root.Backbone = factory(root, exports, _, $);
Couldn't get it work otherwise.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jashkenas/backbone/issues/4072, or mute the thread
https://github.com/notifications/unsubscribe-auth/AHG61AIBGj5LPvwgf9-aoYeUcBc9A66tks5qnVhFgaJpZM4J1xHt
.

I meant require, cannot edit on mobile, sorry.

Yes, but it backbone.js doesn't return anything:
This is the function that gets executed on module require. There is no module.exports or anything on case of node. But I guess quick fix would be just to assign backbone to global (root.Backbone = ) because some extensions assume Backbone global variable?

8 function(factory) {
9
10   // Establish the root object, window (self) in the browser, or global on the server.
11   // We use self instead of window for WebWorker support.
12   var root = (typeof self == 'object' && self.self === self && self) ||
13             (typeof global == 'object' && global.global === global && global);
14
15   // Set up Backbone appropriately for the environment. Start with AMD.
16   if (typeof define === 'function' && define.amd) {
17     define(['underscore', 'jquery', 'exports'], function(_, $, exports) {
18       // Export global even in AMD case in case this script is loaded with
19       // others that may still expect a global Backbone.
20       root.Backbone = factory(root, exports, _, $);
21     });
22
23   // Next for Node.js or CommonJS. jQuery may not be needed as a module.
24   } else if (typeof exports !== 'undefined') {
25     var _ = require('underscore'), $;
26     try { $ = require('jquery'); } catch (e) {}
27     factory(root, exports, , $);
28
29   // Finally, as a browser global.
30   } else {
31     root.Backbone = factory(root, {}, root., (root.jQuery || root.Zepto || root.ender || root.$));
32   }
33
34 })

Backbone works fine in commonJS (node require). The typeof exports !== 'undefined' path is specifically for CommonJS.
Please try StackOverflow for help debugging.


Only set sentinel value for soft-deleteable tables

Commit cc098ad461e35a360b5a2b33591eca06f0d20772 added support for
sentinel columns, which allow unique active row constraints to be
implemented using any SQL database. However, it attempted to set the
sentinel value even for tables which were not explicitly marked as
soft-deleteable (via softDelete: true in the model config). Check for
that flag before enabling sentinels.

@bsiddiqui sorry, I found a bug in my previous PR when only some tables had softDelete: true. This should probably be a 0.10.1 bugfix release.

Nice catch!


fetch error: Error: response code 0

Hello, I have issue when i'm trying to fetch  metadata of external data
I got this error.

Here is my code.
"use client";
import React, { useState, useEffect } from "react";

function ToolsPage() {
  const [metadataImage, setMetadataImage] = useState<string | undefined>(
    undefined
  );

  const urlMetadata = require("url-metadata");

  useEffect(() => {
    const fetchData = async () => {
      try {
        const options = {
          mode: "no-cors",
          includeResponseBody: false,
        };

        const metadata = await urlMetadata(
          "https://youtube.com/",
          options
        );

        const ogImage = metadata["og:image"] || undefined;
        setMetadataImage(ogImage);

        console.log("fetched metadata:", metadata);
        console.log("inside fetchMetadata, ogImage:", ogImage);
      } catch (err) {
        console.log("fetch error:", err);
      }
    };

    fetchData();
  }, []);

  console.log("outside fetchMetadata, metadataImage:", metadataImage);

  return (
    <>
      <img
        src={`${metadataImage}`}
        className="object-cover h-52 w-96 object-center pb-3 rounded-t-lg"
        alt=""
      />
    </>
  );
}

export default ToolsPage;

Response status code 0 is coming directly from javascript native fetch api inside the package. The request failed at either the network or protocol level.
Here are some possible causes of a status code 0:

CORS errors. Try changing the mode option ((ex: cors, no-cors, same-origin, etc)
A browser plugin such as an ad blocker or privacy protector, blocking the request. It could also be caused by trying to access an https resource that has an invalid certificate, or trying to access an http resource from a page with an https origin.


MTA-3625: Dummy attributes for MTA sync and merge test

JIRA

MTA-3625: Values to test the build of MTA 7.1.0. Changing the main attributes to 7.1 as required by Pantheon

FYI - @raoradhika for tomorrow's session. Please do not merge until we are ready

Confirming merge , done!


IllustratedMessage: graphic is always grey in HCM

🐛 Bug Report
The graphic in illustratedMessage is hardcoded to --spectrum-global-color-gray-500
🤔 Expected Behavior
It should be the same as the text color in High Contrast mode
😯 Current Behavior
https://react-spectrum.adobe.com/react-spectrum/IllustratedMessage.html
Run in High Contrast mode - note that the graphics are always grey

💁 Possible Solution

provide an override for https://github.com/adobe/react-spectrum/blob/cb1fc23c8f9efce828f774858aaf3a06a19b49a2/packages/%40adobe/spectrum-css-temp/components/illustratedmessage/skin.css#L14 in High Contrast mode so color is CanvasText
🔦 Context

💻 Code Sample

🌍 Your Environment

Software
Version(s)

react-spectrum
3

Browser
Edge

Operating System
Windows High Contast mode

🧢 Your Company/Team

🕷 Tracking Issue (optional)

FYI, many of the WHCM issues that have been raised in your audit (including this one) were found as part of our initial testing after it was first merged: https://github.com/adobe/react-spectrum/issues/2949. Might be worth going through those and deduping.


Proposed Topic: An accelerated AI platform for heart disease diagnosis

Topic Title
An accelerated AI platform for heart disease diagnosis
Abstract
Recently, deep learning technologies offer ways to diagnose heart diseases automatically which may benefit millions of people in rural areas.
In this talk, we will first introduce the medical background of heart disease diagnosis and what's the challenges using the AI platform for remote healthcare. Then, we will elaborate on our heart diseases diagnosis platform in details. This section includes the infrastructure design, the introduction of the diagnosis process and the dynamic training process. Next, we will present the preliminary screening models at the edge side and classification models in the cloud. The whole talk will elaborate on how to accelerate the infrastructure as well as the models both at the edge and in the cloud. (GPU + Movidius)
Related Upstream Open Source Projects
OpenStack Nova, OpenStack Cyborg, Kubernetes
Category

Accelerator Hardware
Cloud Platform Management Support For Accelerators
Applications With Accelerator Support (AI, 5G, Edge/IoT, HPC, Quantum Computing, Neuromorphic Computing, etc)

Speaker Bio (no more than 2 people)
Jinghua Gao, Staff Researcher, Lenovo Research
Got involved in OpenStack for 5+ years and Kubernetes for 2+ years. Mainly focus on network management. Interests include DPDK technology, user-space TCP/IP stack, load-balance and so on. Recent work is related to intelligent traffic analysis and hardware acceleration.
Speaker email
Jinghua<EMAIL_ADDRESS><EMAIL_ADDRESS>

Move to part of the unconference discussion


[BUG] Confusion caused by 'prompt-text/tokens' in inference stage

Thank you so much for your open-source initiative. The transition from a VITS structure to a transformer-based structure is exciting.
Describe the bug
It could be a mistake in the description of the introduction/inference, or it could be something else.
Details
I noticed that in the introduction stage, the inference part of the model was described as requiring only textual input. But under inference, the user is asked to enter 'prompt-text/tokens''.
Perhaps you can consider adding a simple inference code that requires only --text or explain why prompt input is still required during the inference phase.
Thank you for your contributions.

Prompt text / tokens are used for zeroshot TTS speaker following (conditioned on specific speaker), otherwise, it will use random speaker.


Snooze or skip alarm, with a reason

Do this one after #47, #45 and #44.
Some snooze reasons:

[ ] I don't want to do it now
[ ] I can't do it now
[ ] I'm working now

Skip reasons:

[ ] There is no need to do this now

Reasons:

[ ] Create a Reason model with columns: id, title, can_snooze (bool), can_skip (bool)
[ ] A reason can be used on snooze, on skip, or on both; at least of the flags must be set

Telegram bot:

[ ] Show buttons with reasons to skip or snooze the chore
[ ] Accept new text as a different reason
[ ] Examples of reasons: busy, working, don't want to, not needed now, not in the mood

This issue has become obsolete. See #135.


Line height

If Text style has lineHeight, The English, chinese, japanese, number is not on a same baseline.

Test Plan

Related PRs

Related Notes
[GENERAL] [BUGFIX] [Libraries/Text/RCTTextShadowView.m] - Fix Text background has alpha

This should be superseded by #19653.

Thanks for your PR. This should already be fixed on master, yay!


Legs' state cannot be reset

Hi @tarasborov
Still playing with Spot teleop, and noticed that any changes that affect Spot's legs pose can't be reset via Gazebo.
Specifically, I tried to move the body up, until Spot reached the state it can't control the balance anymore.

Then I tried to reset model poses (even the world) via native Gazebo functionality. Spot has appeared in the initial point, but the legs' state hasn't been reset:

Gazebo can not reset robot pose because a ros_controller is running that set poses for joints.

@tarasborov can we reset the controller's state to defaults? Maybe via publishing to some topic? Or it's not manageable?

To reset the controller, you should rerun it.


Failed to install VS Code update

VSCode Version: Insaider
OS Version: Windows 10 Pro x64 ; build: 17134.112

This is e attach of the following log file with error from update
Jun 18 09:50:13.479 INFO Starting: C:\Program Files\Microsoft\VS Code Insiders\Code - Insiders.exe, false
Jun 18 09:50:13.487 INFO Checking for running Code - Insiders.exe processes... (attempt 1)
Jun 18 09:50:13.508 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:14.040 INFO Checking for running Code - Insiders.exe processes... (attempt 2)
Jun 18 09:50:14.116 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:14.627 INFO Checking for running Code - Insiders.exe processes... (attempt 3)
Jun 18 09:50:14.665 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:15.173 INFO Checking for running Code - Insiders.exe processes... (attempt 4)
Jun 18 09:50:15.207 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:15.708 INFO Checking for running Code - Insiders.exe processes... (attempt 5)
Jun 18 09:50:15.738 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:16.244 INFO Checking for running Code - Insiders.exe processes... (attempt 6)
Jun 18 09:50:16.279 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:16.781 INFO Checking for running Code - Insiders.exe processes... (attempt 7)
Jun 18 09:50:16.815 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:17.316 INFO Checking for running Code - Insiders.exe processes... (attempt 8)
Jun 18 09:50:17.346 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:17.848 INFO Checking for running Code - Insiders.exe processes... (attempt 9)
Jun 18 09:50:17.879 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:18.384 INFO Checking for running Code - Insiders.exe processes... (attempt 10)
Jun 18 09:50:18.418 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:18.919 INFO Checking for running Code - Insiders.exe processes... (attempt 11)
Jun 18 09:50:18.949 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:19.473 INFO Checking for running Code - Insiders.exe processes... (attempt 12)
Jun 18 09:50:19.513 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:20.095 INFO Checking for running Code - Insiders.exe processes... (attempt 13)
Jun 18 09:50:20.228 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:20.756 INFO Checking for running Code - Insiders.exe processes... (attempt 14)
Jun 18 09:50:20.843 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:21.383 INFO Checking for running Code - Insiders.exe processes... (attempt 15)
Jun 18 09:50:21.429 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:22.056 INFO Checking for running Code - Insiders.exe processes... (attempt 16)
Jun 18 09:50:22.190 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:22.719 INFO Checking for running Code - Insiders.exe processes... (attempt 17)
Jun 18 09:50:22.771 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:23.308 INFO Checking for running Code - Insiders.exe processes... (attempt 18)
Jun 18 09:50:23.357 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:23.863 INFO Checking for running Code - Insiders.exe processes... (attempt 19)
Jun 18 09:50:23.911 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:24.441 INFO Checking for running Code - Insiders.exe processes... (attempt 20)
Jun 18 09:50:24.511 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:25.014 INFO Checking for running Code - Insiders.exe processes... (attempt 21)
Jun 18 09:50:25.063 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:25.565 INFO Checking for running Code - Insiders.exe processes... (attempt 22)
Jun 18 09:50:25.603 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:26.104 INFO Checking for running Code - Insiders.exe processes... (attempt 23)
Jun 18 09:50:26.162 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:26.664 INFO Checking for running Code - Insiders.exe processes... (attempt 24)
Jun 18 09:50:26.710 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:27.213 INFO Checking for running Code - Insiders.exe processes... (attempt 25)
Jun 18 09:50:27.255 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:27.756 INFO Checking for running Code - Insiders.exe processes... (attempt 26)
Jun 18 09:50:27.794 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:28.296 INFO Checking for running Code - Insiders.exe processes... (attempt 27)
Jun 18 09:50:28.335 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:28.836 INFO Checking for running Code - Insiders.exe processes... (attempt 28)
Jun 18 09:50:28.872 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:29.374 INFO Checking for running Code - Insiders.exe processes... (attempt 29)
Jun 18 09:50:29.426 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:29.959 INFO Checking for running Code - Insiders.exe processes... (attempt 30)
Jun 18 09:50:29.990 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:30.493 INFO Checking for running Code - Insiders.exe processes... (attempt 31)
Jun 18 09:50:30.532 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:31.033 INFO Checking for running Code - Insiders.exe processes... (attempt 32)
Jun 18 09:50:31.077 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:31.578 INFO Checking for running Code - Insiders.exe processes... (attempt 33)
Jun 18 09:50:31.613 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:32.114 INFO Checking for running Code - Insiders.exe processes... (attempt 34)
Jun 18 09:50:32.156 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:32.672 INFO Checking for running Code - Insiders.exe processes... (attempt 35)
Jun 18 09:50:32.723 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:33.225 INFO Checking for running Code - Insiders.exe processes... (attempt 36)
Jun 18 09:50:33.294 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:33.803 INFO Checking for running Code - Insiders.exe processes... (attempt 37)
Jun 18 09:50:33.846 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:34.348 INFO Checking for running Code - Insiders.exe processes... (attempt 38)
Jun 18 09:50:34.403 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:34.904 INFO Checking for running Code - Insiders.exe processes... (attempt 39)
Jun 18 09:50:34.957 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:35.458 INFO Checking for running Code - Insiders.exe processes... (attempt 40)
Jun 18 09:50:35.493 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:35.997 INFO Checking for running Code - Insiders.exe processes... (attempt 41)
Jun 18 09:50:36.039 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:36.544 INFO Checking for running Code - Insiders.exe processes... (attempt 42)
Jun 18 09:50:36.590 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:37.092 INFO Checking for running Code - Insiders.exe processes... (attempt 43)
Jun 18 09:50:37.144 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:37.668 INFO Checking for running Code - Insiders.exe processes... (attempt 44)
Jun 18 09:50:37.703 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:38.239 INFO Checking for running Code - Insiders.exe processes... (attempt 45)
Jun 18 09:50:38.277 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:38.787 INFO Checking for running Code - Insiders.exe processes... (attempt 46)
Jun 18 09:50:38.846 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:39.349 INFO Checking for running Code - Insiders.exe processes... (attempt 47)
Jun 18 09:50:39.397 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:39.903 INFO Checking for running Code - Insiders.exe processes... (attempt 48)
Jun 18 09:50:39.953 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:40.458 INFO Checking for running Code - Insiders.exe processes... (attempt 49)
Jun 18 09:50:40.501 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:41.004 INFO Checking for running Code - Insiders.exe processes... (attempt 50)
Jun 18 09:50:41.058 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:41.559 INFO Checking for running Code - Insiders.exe processes... (attempt 51)
Jun 18 09:50:41.608 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:42.112 INFO Checking for running Code - Insiders.exe processes... (attempt 52)
Jun 18 09:50:42.158 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:42.661 INFO Checking for running Code - Insiders.exe processes... (attempt 53)
Jun 18 09:50:42.704 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:43.205 INFO Checking for running Code - Insiders.exe processes... (attempt 54)
Jun 18 09:50:43.248 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:43.749 INFO Checking for running Code - Insiders.exe processes... (attempt 55)
Jun 18 09:50:43.793 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:44.294 INFO Checking for running Code - Insiders.exe processes... (attempt 56)
Jun 18 09:50:44.336 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:44.838 INFO Checking for running Code - Insiders.exe processes... (attempt 57)
Jun 18 09:50:44.874 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:45.376 INFO Checking for running Code - Insiders.exe processes... (attempt 58)
Jun 18 09:50:45.424 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:45.927 INFO Checking for running Code - Insiders.exe processes... (attempt 59)
Jun 18 09:50:45.972 INFO Code - Insiders.exe is running, wait a bit
Jun 18 09:50:46.474 INFO Checking for running Code - Insiders.exe processes... (attempt 60)
Jun 18 09:50:46.514 INFO Gave up waiting for Code - Insiders.exe to exit
Jun 18 09:50:46.515 INFO Checking for possible conflicting running processes... (attempt 1)
Jun 18 09:50:46.554 INFO Kill process if found: 12244, Code - Insiders.exe
Jun 18 09:50:46.554 INFO Found Code - Insiders.exe running, pid 12244, attempting to kill...
Jun 18 09:50:46.554 INFO Kill process if found: 11328, Code - Insiders.exe
Jun 18 09:50:46.556 INFO Found Code - Insiders.exe running, pid 11328, attempting to kill...
Jun 18 09:50:46.556 INFO Kill process if found: 8012, Code - Insiders.exe
Jun 18 09:50:46.556 INFO Found Code - Insiders.exe running, pid 8012, attempting to kill...
Jun 18 09:50:46.556 INFO Kill process if found: 9624, Code - Insiders.exe
Jun 18 09:50:46.557 INFO Found Code - Insiders.exe running, pid 9624, attempting to kill...
Jun 18 09:50:46.557 INFO Kill process if found: 8748, Code - Insiders.exe
Jun 18 09:50:46.558 INFO Found Code - Insiders.exe running, pid 8748, attempting to kill...
Jun 18 09:50:46.558 INFO Successfully killed Code - Insiders.exe, pid 8748
Jun 18 09:50:46.559 INFO Kill process if found: 12924, Code - Insiders.exe
Jun 18 09:50:46.561 INFO Kill process if found: 9772, Code - Insiders.exe
Jun 18 09:50:46.561 INFO Found Code - Insiders.exe running, pid 9772, attempting to kill...
Jun 18 09:50:46.562 INFO Kill process if found: 12060, Code - Insiders.exe
Jun 18 09:50:46.562 INFO Found Code - Insiders.exe running, pid 12060, attempting to kill...
Jun 18 09:50:46.562 INFO Kill process if found: 28180, Code - Insiders.exe
Jun 18 09:50:46.562 INFO Found Code - Insiders.exe running, pid 28180, attempting to kill...

Jun 18 09:50:46.653 INFO Kill process if found: 11328, Code - Insiders.exe
Jun 18 09:50:46.653 INFO Found Code - Insiders.exe running, pid 11328, attempting to kill...
Jun 18 09:50:46.654 INFO Kill process if found: 8012, Code - Insiders.exe
Jun 18 09:50:46.654 INFO Found Code - Insiders.exe running, pid 8012, attempting to kill...
Jun 18 09:50:46.655 INFO Kill process if found: 9624, Code - Insiders.exe
Jun 18 09:50:46.655 INFO Found Code - Insiders.exe running, pid 9624, attempting to kill...
Jun 18 09:50:46.656 INFO Kill process if found: 12924, Code - Insiders.exe
Jun 18 09:50:46.656 INFO Kill process if found: 9772, Code - Insiders.exe
Jun 18 09:50:46.657 INFO Found Code - Insiders.exe running, pid 9772, attempting to kill...
Jun 18 09:50:46.658 INFO Kill process if found: 12060, Code - Insiders.exe
Jun 18 09:50:46.658 INFO Found Code - Insiders.exe running, pid 12060, attempting to kill...
Jun 18 09:50:46.658 INFO Kill process if found: 28180, Code - Insiders.exe
Jun 18 09:50:46.659 INFO Found Code - Insiders.exe running, pid 28180, attempting to kill...

Jun 18 09:50:46.902 INFO Kill process if found: 11328, Code - Insiders.exe
Jun 18 09:50:46.903 INFO Found Code - Insiders.exe running, pid 11328, attempting to kill...
Jun 18 09:50:46.904 INFO Kill process if found: 8012, Code - Insiders.exe
Jun 18 09:50:46.904 INFO Found Code - Insiders.exe running, pid 8012, attempting to kill...
Jun 18 09:50:46.905 INFO Kill process if found: 9624, Code - Insiders.exe
Jun 18 09:50:46.905 INFO Found Code - Insiders.exe running, pid 9624, attempting to kill...
Jun 18 09:50:46.906 INFO Kill process if found: 12924, Code - Insiders.exe
Jun 18 09:50:46.906 INFO Kill process if found: 9772, Code - Insiders.exe
Jun 18 09:50:46.907 INFO Found Code - Insiders.exe running, pid 9772, attempting to kill...
Jun 18 09:50:46.907 INFO Kill process if found: 12060, Code - Insiders.exe
Jun 18 09:50:46.908 INFO Found Code - Insiders.exe running, pid 12060, attempting to kill...
Jun 18 09:50:46.908 INFO Kill process if found: 28180, Code - Insiders.exe
Jun 18 09:50:46.909 INFO Found Code - Insiders.exe running, pid 28180, attempting to kill...

Jun 18 09:50:47.397 INFO Kill process if found: 11328, Code - Insiders.exe
Jun 18 09:50:47.398 INFO Found Code - Insiders.exe running, pid 11328, attempting to kill...
Jun 18 09:50:47.398 INFO Kill process if found: 8012, Code - Insiders.exe
Jun 18 09:50:47.398 INFO Found Code - Insiders.exe running, pid 8012, attempting to kill...
Jun 18 09:50:47.399 INFO Kill process if found: 9624, Code - Insiders.exe
Jun 18 09:50:47.400 INFO Found Code - Insiders.exe running, pid 9624, attempting to kill...
Jun 18 09:50:47.400 INFO Kill process if found: 12924, Code - Insiders.exe
Jun 18 09:50:47.401 INFO Kill process if found: 9772, Code - Insiders.exe
Jun 18 09:50:47.401 INFO Found Code - Insiders.exe running, pid 9772, attempting to kill...
Jun 18 09:50:47.402 INFO Kill process if found: 12060, Code - Insiders.exe
Jun 18 09:50:47.403 INFO Found Code - Insiders.exe running, pid 12060, attempting to kill...
Jun 18 09:50:47.403 INFO Kill process if found: 28180, Code - Insiders.exe
Jun 18 09:50:47.404 INFO Found Code - Insiders.exe running, pid 28180, attempting to kill...

Jun 18 09:50:48.243 INFO Kill process if found: 11328, Code - Insiders.exe
Jun 18 09:50:48.244 INFO Found Code - Insiders.exe running, pid 11328, attempting to kill...
Jun 18 09:50:48.244 INFO Kill process if found: 8012, Code - Insiders.exe
Jun 18 09:50:48.245 INFO Found Code - Insiders.exe running, pid 8012, attempting to kill...
Jun 18 09:50:48.245 INFO Kill process if found: 9624, Code - Insiders.exe
Jun 18 09:50:48.246 INFO Found Code - Insiders.exe running, pid 9624, attempting to kill...
Jun 18 09:50:48.246 INFO Kill process if found: 12924, Code - Insiders.exe
Jun 18 09:50:48.247 INFO Kill process if found: 9772, Code - Insiders.exe
Jun 18 09:50:48.247 INFO Found Code - Insiders.exe running, pid 9772, attempting to kill...
Jun 18 09:50:48.248 INFO Kill process if found: 12060, Code - Insiders.exe
Jun 18 09:50:48.248 INFO Found Code - Insiders.exe running, pid 12060, attempting to kill...
Jun 18 09:50:48.249 INFO Kill process if found: 28180, Code - Insiders.exe
Jun 18 09:50:48.250 INFO Found Code - Insiders.exe running, pid 28180, attempting to kill...

Jun 18 09:50:49.546 INFO Kill process if found: 11328, Code - Insiders.exe
Jun 18 09:50:49.546 INFO Found Code - Insiders.exe running, pid 11328, attempting to kill...
Jun 18 09:50:49.547 INFO Kill process if found: 8012, Code - Insiders.exe
Jun 18 09:50:49.547 INFO Found Code - Insiders.exe running, pid 8012, attempting to kill...
Jun 18 09:50:49.548 INFO Kill process if found: 9624, Code - Insiders.exe
Jun 18 09:50:49.548 INFO Found Code - Insiders.exe running, pid 9624, attempting to kill...
Jun 18 09:50:49.548 INFO Kill process if found: 12924, Code - Insiders.exe
Jun 18 09:50:49.549 INFO Kill process if found: 9772, Code - Insiders.exe
Jun 18 09:50:49.549 INFO Found Code - Insiders.exe running, pid 9772, attempting to kill...
Jun 18 09:50:49.550 INFO Kill process if found: 12060, Code - Insiders.exe
Jun 18 09:50:49.550 INFO Found Code - Insiders.exe running, pid 12060, attempting to kill...
Jun 18 09:50:49.551 INFO Kill process if found: 28180, Code - Insiders.exe
Jun 18 09:50:49.551 INFO Found Code - Insiders.exe running, pid 28180, attempting to kill...

Jun 18 09:50:51.395 INFO Kill process if found: 8012, Code - Insiders.exe
Jun 18 09:50:51.395 INFO Found Code - Insiders.exe running, pid 8012, attempting to kill...
Jun 18 09:50:51.396 INFO Kill process if found: 9624, Code - Insiders.exe
Jun 18 09:50:51.396 INFO Found Code - Insiders.exe running, pid 9624, attempting to kill...
Jun 18 09:50:51.397 INFO Kill process if found: 12924, Code - Insiders.exe
Jun 18 09:50:51.397 INFO Kill process if found: 9772, Code - Insiders.exe
Jun 18 09:50:51.398 INFO Found Code - Insiders.exe running, pid 9772, attempting to kill...
Jun 18 09:50:51.399 INFO Kill process if found: 12060, Code - Insiders.exe
Jun 18 09:50:51.400 INFO Found Code - Insiders.exe running, pid 12060, attempting to kill...
Jun 18 09:50:51.400 INFO Kill process if found: 28180, Code - Insiders.exe
Jun 18 09:50:51.401 INFO Found Code - Insiders.exe running, pid 28180, attempting to kill...
Jun 18 09:50:51.401 WARN Kill error Failed to get process file name: Odmowa dostępu.

Jun 18 09:50:53.897 INFO Kill process if found: 8012, Code - Insiders.exe
Jun 18 09:50:53.898 INFO Found Code - Insiders.exe running, pid 8012, attempting to kill...
Jun 18 09:50:53.899 INFO Kill process if found: 9624, Code - Insiders.exe
Jun 18 09:50:53.899 INFO Found Code - Insiders.exe running, pid 9624, attempting to kill...
Jun 18 09:50:53.900 INFO Kill process if found: 12924, Code - Insiders.exe
Jun 18 09:50:53.900 INFO Kill process if found: 9772, Code - Insiders.exe
Jun 18 09:50:53.901 INFO Found Code - Insiders.exe running, pid 9772, attempting to kill...
Jun 18 09:50:53.901 INFO Kill process if found: 12060, Code - Insiders.exe
Jun 18 09:50:53.902 INFO Found Code - Insiders.exe running, pid 12060, attempting to kill...
Jun 18 09:50:53.902 INFO Kill process if found: 28180, Code - Insiders.exe
Jun 18 09:50:53.903 INFO Found Code - Insiders.exe running, pid 28180, attempting to kill...
Jun 18 09:50:53.903 WARN Kill error Failed to get process file name: Odmowa dostępu.

Jun 18 09:50:57.224 INFO Kill process if found: 8012, Code - Insiders.exe
Jun 18 09:50:57.225 INFO Found Code - Insiders.exe running, pid 8012, attempting to kill...
Jun 18 09:50:57.226 INFO Kill process if found: 9624, Code - Insiders.exe
Jun 18 09:50:57.226 INFO Found Code - Insiders.exe running, pid 9624, attempting to kill...
Jun 18 09:50:57.227 INFO Kill process if found: 12924, Code - Insiders.exe
Jun 18 09:50:57.227 INFO Kill process if found: 9772, Code - Insiders.exe
Jun 18 09:50:57.228 INFO Found Code - Insiders.exe running, pid 9772, attempting to kill...
Jun 18 09:50:57.228 INFO Kill process if found: 12060, Code - Insiders.exe
Jun 18 09:50:57.229 INFO Found Code - Insiders.exe running, pid 12060, attempting to kill...
Jun 18 09:50:57.229 INFO Kill process if found: 28180, Code - Insiders.exe
Jun 18 09:50:57.230 INFO Found Code - Insiders.exe running, pid 28180, attempting to kill...
Jun 18 09:50:57.230 WARN Kill error Failed to get process file name: Odmowa dostępu.

Jun 18 09:51:01.324 INFO Kill process if found: 8012, Code - Insiders.exe
Jun 18 09:51:01.325 INFO Kill process if found: 9624, Code - Insiders.exe
Jun 18 09:51:01.326 INFO Found Code - Insiders.exe running, pid 9624, attempting to kill...
Jun 18 09:51:01.326 INFO Kill process if found: 12924, Code - Insiders.exe
Jun 18 09:51:01.326 INFO Kill process if found: 9772, Code - Insiders.exe
Jun 18 09:51:01.327 INFO Found Code - Insiders.exe running, pid 9772, attempting to kill...
Jun 18 09:51:01.327 INFO Kill process if found: 12060, Code - Insiders.exe
Jun 18 09:51:01.328 INFO Kill process if found: 28180, Code - Insiders.exe
Jun 18 09:51:01.328 INFO Found Code - Insiders.exe running, pid 28180, attempting to kill...
Jun 18 09:51:01.329 WARN Kill error Failed to get process file name: Odmowa dostępu.

Jun 18 09:51:01.333 WARN Kill error Failed to kill process
Jun 18 09:51:06.328 INFO Checking for possible conflicting running processes... (attempt 11)
Jun 18 09:51:06.372 INFO Kill process if found: 12244, Code - Insiders.exe
Jun 18 09:51:06.373 INFO Kill process if found: 11328, Code - Insiders.exe
Jun 18 09:51:06.373 INFO Found Code - Insiders.exe running, pid 11328, attempting to kill...
Jun 18 09:51:06.374 INFO Kill process if found: 8012, Code - Insiders.exe
Jun 18 09:51:06.374 INFO Kill process if found: 9624, Code - Insiders.exe
Jun 18 09:51:06.375 INFO Found Code - Insiders.exe running, pid 9624, attempting to kill...
Jun 18 09:51:06.375 INFO Kill process if found: 12924, Code - Insiders.exe
Jun 18 09:51:06.376 INFO Kill process if found: 9772, Code - Insiders.exe
Jun 18 09:51:06.376 INFO Found Code - Insiders.exe running, pid 9772, attempting to kill...
Jun 18 09:51:06.377 INFO Kill process if found: 12060, Code - Insiders.exe
Jun 18 09:51:06.377 INFO Kill process if found: 28180, Code - Insiders.exe
Jun 18 09:51:06.378 INFO Found Code - Insiders.exe running, pid 28180, attempting to kill...
Jun 18 09:51:06.378 WARN Kill error Failed to get process file name: Odmowa dostępu.

Please read this comment if you can provide more detail: https://github.com/Microsoft/vscode/issues/47841#issuecomment-393101777
Please read this one to disable background updates: https://github.com/Microsoft/vscode/issues/47841#issuecomment-395017687


ci: fix syntax error in pull-request-commenter GitHub Workflow

The ok-to-test label does not work anymore, and the GitHub Workflow contains the following error:
The workflow is not valid.
.github/workflows/pull-request-commentor.yaml (Line: 15, Col: 9):
Unrecognized named-value: 'ok-to-test'.

Show available bot commands
These commands are normally not required, but in case of issues, leave any of
the following bot commands in an otherwise empty comment in this PR:

/retest ci/centos/<job-name>: retest the <job-name> after unrelated
failure (please report the failure too!)
/retest all: run this in case the CentOS CI failed to start/report any test
progress or results

/test all

/retest all

/test ci/centos/upgrade-tests-rbd

/test all


Compare 2 iterators

Provide assertion for the equality of 2 iterators.
It makes a bit difference for readability of a test of both actual and expected need ".collect::<Vec<_>>()" on the end.

Hey, thanks for raising this! I think that sounds like an excellent idea.
If you want, you can submit a pull request to add this in. If you decide to do that, and have any questions, I'd be more than happy to answer them.
Otherwise, I'll try to look into this as soon as I can.