Unexpected EOF while installing/downloading large packages

My reason:
Installing larger packages (this one in this scenario) fails consistently from verdaccio with an unexpected EOF. The package is published to the local verdaccio server, not a redirection to the public registry. It installs fine from the public registry at https://registry.npmjs.org.
Even a simple wget ends abruptly
HTTP request sent, awaiting response...
  HTTP/1.1 200 OK
  X-Powered-By: verdaccio/2.3.4
  Access-Control-Allow-Origin: *
  Content-Type: application/octet-stream
  Content-Length: 137211454
  X-Status-Cat: http://flic.kr/p/aVuVsF
  Date: Mon, 21 Aug 2017 11:43:35 GMT
  Connection: keep-alive
Length: 137211454 (131M) [application/octet-stream]
Saving to: ‘react-native-awesome-card-io-0.6.6.tgz.2’

react-native-awesome-card-io-0.6.6.tgz.2        65%[======================================================================>                                      ]  85.73M  13.6MB/s    in 6.1s

2017-08-21 17:15:23 (14.1 MB/s) - Connection closed at byte 89897191. Retrying.

Steps to reproduce:

Publish the package to Verdaccio
Try installing it with yarn or npm

Issue is occurring when running the latest docker image, or on the host system with verdaccio installed through npm. Issue has persisted on both a Linux host and a macOS host.
It seems to occur on an erratic timeout basis (~7-10 seconds) because the download completes successfully if the download speed is high enough. The byte at which the connection closes is also not constant.
App Version:
2.3.4
Config file:
Default config file with only max_body_size increased to 300mb allow publishing packages of this size.

I will take a look it along the week.

Sorry, but I couldn't reproduce it. I doubt is an issue with verdaccio itself.
➜ npm install react-native-awesome-card-io
npm WARN saveError ENOENT: no such file or directory, open '/Users/jpicado/projects/hello_world_npm/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/Users/jpicado/projects/hello_world_npm/package.json'
npm WARN hello_world_npm No description
npm WARN hello_world_npm No repository field.
npm WARN hello_world_npm No README data
npm WARN hello_world_npm No license field.

+<EMAIL_ADDRESS>updated 1 package in 16.797s

I tried multiple ways to simulate network latency, packages drop, uplink delays etc. I would you suggest clean your cache or review your local environment. My tests were from a local Docker container and v2.3.6.
I'll close this, feel free to reopen if the issue persists and try to provide more verbose output.

Alright, thanks for your time! Already tried cleaning cache and fresh installs and there's nothing obvious that stands out in the local environment, but will dig deeper to try and identify the issue.

I've reproduced the same issue in this case with geoip-lite which is a fairly large package (~30MiB). It doesn't work no matter what I try, even after npm cache clean --force. I have verdaccio 2.3 running in an aws hosted Docker container.
It works perfectly with the standard npm registry.
This is the npm log:
1777 http fetch GET 200 https://npm.foo.bar/geoip-lite/-/geoip-lite-1.2.1.tgz 12714ms
1778 silly fetchPackageMetaData error for<EMAIL_ADDRESS>unexpected end of file
1779 verbose stack Error: unexpected end of file
1779 verbose stack     at Gunzip.zlibOnError (zlib.js:152:15)
1780 verbose cwd /Users/me/work/my-project
1781 verbose Darwin 16.7.0
1782 verbose argv "/Users/me/.nvm/versions/node/v8.5.0/bin/node" "/Users/me/.nvm/versions/node/v8.5.0/bin/npm" "i"
1783 verbose node v8.5.0
1784 verbose npm  v5.3.0
1785 error code Z_BUF_ERROR
1786 error errno -5
1787 error unexpected end of file
1788 verbose exit [ -5, true ]

geoip-lite-1.2.1.tgz is consistently well downloaded in verdaccio, though.

Fwiw we weren't able to identify the actual cause, we were able to work around it however by setting up an nginx reverse proxy to verdaccio on the same host machine and accessing the registry through the proxy.

Thanks for the help, @yogeshwar-20 . Did you use any specific setting? Timeouts or anything like that? I tried with a squid proxy with no luck.

Only keepalive and proxypass.

Running into the same issue when trying to pull ares-webos-sdk (> 42mb)

We need to find a perfect way to reproduce this properly. I didn't have success in my last try.

Putting it behind an nginx proxy did fix the problem for me

We're having the exact same issue. Our local (in Docker) Verdaccio currently hosts only one private package, and it fails both with npm install / yarn install and even simply curl for downloading the package's .tgz file.
@juanpicado Can you please re-open this issue? It really blocks us from using Verdaccio at the moment. :(

Sure, no problem

@alonl It doesn't work with @pward123 workaround?

@alonl It doesn't work with @pward123 workaround?
Haven't tried yet.

@juanpicado one interesting verdict I've just found:

Every time, the connection terminates after exactly 6.0 - 6.6 seconds. Maybe there is some session timeout configured somewhere? Maybe in the Docker configuration? See these attempts of wget (until it finally succeeded in less than 6.2 seconds) below:

> wget http://verdaccio.infra.svc.cluster.local/some-package/-/some-package-5.0.0.tgz

--2017-10-03 21:16:38--  http://verdaccio.infra.svc.cluster.local/some-package/-/some-package-5.0.0.tgz
Resolving verdaccio.infra.svc.cluster.local (verdaccio.infra.svc.cluster.local)... <IP_ADDRESS>
Connecting to verdaccio.infra.svc.cluster.local (verdaccio.infra.svc.cluster.local)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2522568 (2.4M) [application/octet-stream]
Saving to: ‘some-package-5.0.0.tgz’

some-package-5.0.0.tgz                                   39%[==============================================>                                                                        ] 974.39K   191KB/s    in 6.2s

2017-10-03 21:16:45 (158 KB/s) - Connection closed at byte 997776. Retrying.

--2017-10-03 21:16:46--  (try: 2)  http://verdaccio.infra.svc.cluster.local/some-package/-/some-package-5.0.0.tgz
Connecting to verdaccio.infra.svc.cluster.local (verdaccio.infra.svc.cluster.local)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2522568 (2.4M) [application/octet-stream]
Saving to: ‘some-package-5.0.0.tgz’

some-package-5.0.0.tgz                                   35%[=========================================>                                                                             ] 872.50K   149KB/s    in 6.2s

2017-10-03 21:16:53 (141 KB/s) - Connection closed at byte 997776. Retrying.

--2017-10-03 21:16:55--  (try: 3)  http://verdaccio.infra.svc.cluster.local/some-package/-/some-package-5.0.0.tgz
Connecting to verdaccio.infra.svc.cluster.local (verdaccio.infra.svc.cluster.local)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2522568 (2.4M) [application/octet-stream]
Saving to: ‘some-package-5.0.0.tgz’

some-package-5.0.0.tgz                                   38%[============================================>                                                                          ] 942.63K   178KB/s    in 6.2s

2017-10-03 21:17:02 (153 KB/s) - Connection closed at byte 997776. Retrying.

--2017-10-03 21:17:05--  (try: 4)  http://verdaccio.infra.svc.cluster.local/some-package/-/some-package-5.0.0.tgz
Connecting to verdaccio.infra.svc.cluster.local (verdaccio.infra.svc.cluster.local)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2522568 (2.4M) [application/octet-stream]
Saving to: ‘some-package-5.0.0.tgz’

some-package-5.0.0.tgz                                   99%[=====================================================================================================================> ]   2.39M   460KB/s    in 6.1s

2017-10-03 21:17:12 (398 KB/s) - Connection closed at byte 2505891. Retrying.

--2017-10-03 21:17:16--  (try: 5)  http://verdaccio.infra.svc.cluster.local/some-package/-/some-package-5.0.0.tgz
Connecting to verdaccio.infra.svc.cluster.local (verdaccio.infra.svc.cluster.local)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2522568 (2.4M) [application/octet-stream]
Saving to: ‘some-package-5.0.0.tgz’

some-package-5.0.0.tgz                                   67%[===============================================================================>                                       ]   1.63M   284KB/s    in 6.6s

2017-10-03 21:17:24 (251 KB/s) - Connection closed at byte 2505891. Retrying.

--2017-10-03 21:17:29--  (try: 6)  http://verdaccio.infra.svc.cluster.local/some-package/-/some-package-5.0.0.tgz
Connecting to verdaccio.infra.svc.cluster.local (verdaccio.infra.svc.cluster.local)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2522568 (2.4M) [application/octet-stream]
Saving to: ‘some-package-5.0.0.tgz’

some-package-5.0.0.tgz                                   74%[=======================================================================================>                               ]   1.80M   317KB/s    in 6.8s

2017-10-03 21:17:37 (269 KB/s) - Connection closed at byte 2505891. Retrying.

--2017-10-03 21:17:43--  (try: 7)  http://verdaccio.infra.svc.cluster.local/some-package/-/some-package-5.0.0.tgz
Connecting to verdaccio.infra.svc.cluster.local (verdaccio.infra.svc.cluster.local)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2522568 (2.4M) [application/octet-stream]
Saving to: ‘some-package-5.0.0.tgz’

some-package-5.0.0.tgz                                   33%[=======================================>                                                                               ] 832.80K   144KB/s    in 6.5s

2017-10-03 21:17:50 (128 KB/s) - Connection closed at byte 2505891. Retrying.

--2017-10-03 21:17:57--  (try: 8)  http://verdaccio.infra.svc.cluster.local/some-package/-/some-package-5.0.0.tgz
Connecting to verdaccio.infra.svc.cluster.local (verdaccio.infra.svc.cluster.local)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2522568 (2.4M) [application/octet-stream]
Saving to: ‘some-package-5.0.0.tgz’

some-package-5.0.0.tgz                                   32%[=====================================>                                                                                ] 789.14K   128KB/s    in 6.6s

2017-10-03 21:18:05 (120 KB/s) - Connection closed at byte 2505891. Retrying.

--2017-10-03 21:18:13--  (try: 9)  http://verdaccio.infra.svc.cluster.local/some-package/-/some-package-5.0.0.tgz
Connecting to verdaccio.infra.svc.cluster.local (verdaccio.infra.svc.cluster.local)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2522568 (2.4M) [application/octet-stream]
Saving to: ‘some-package-5.0.0.tgz’

some-package-5.0.0.tgz                                   42%[=================================================>                                                                     ]   1.03M   177KB/s    in 6.3s

2017-10-03 21:18:20 (167 KB/s) - Connection closed at byte 2505891. Retrying.

--2017-10-03 21:18:29--  (try:10)  http://verdaccio.infra.svc.cluster.local/some-package/-/some-package-5.0.0.tgz
Connecting to verdaccio.infra.svc.cluster.local (verdaccio.infra.svc.cluster.local)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2522568 (2.4M) [application/octet-stream]
Saving to: ‘some-package-5.0.0.tgz’

some-package-5.0.0.tgz                                   45%[=====================================================>                                                                 ]   1.10M   231KB/s    in 6.0s

2017-10-03 21:18:36 (186 KB/s) - Connection closed at byte 2505891. Retrying.

--2017-10-03 21:18:46--  (try:11)  http://verdaccio.infra.svc.cluster.local/some-package/-/some-package-5.0.0.tgz
Connecting to verdaccio.infra.svc.cluster.local (verdaccio.infra.svc.cluster.local)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2522568 (2.4M) [application/octet-stream]
Saving to: ‘some-package-5.0.0.tgz’

some-package-5.0.0.tgz                                  100%[======================================================================================================================>]   2.41M   446KB/s    in 6.1s

2017-10-03 21:18:53 (404 KB/s) - ‘some-package-5.0.0.tgz’ saved [2522568/2522568]

I'm not aware of any timeout, but I'll try to dig a bit and see what I find out. Since I'm not a Docker expert 😥  would be great anyone else dig as well in order to fix this issue.

For now I couldn't reproduce locally, even when running in Docker :(

Yes, locally works perfectly. I wonder if any factor might be causing this issue.

Nginx seems so solve the problem for me as well. Thanks @pward123.

@juanpicado I have a belief that this issue is somehow related to the stream buffering, since the difference (that I see) between with/without nginx is that nginx buffers the response.
From my nginx logs:
23:46:09 [warn] 7#7: *90 an upstream response is buffered to a temporary file /var/cache/nginx/proxy_temp/1/01/0000000011 while reading upstream, client: <IP_ADDRESS>, server: , request: "GET /some-package/-/some-package-5.3.0.tgz HTTP/1.1", upstream: "http://<IP_ADDRESS>:4873/some-package/-/some-package-5.3.0.tgz", host: "verdaccio.infra.svc.cluster.local"

@alonl I don't get it

We are also using Verdaccio to maintain the private registry.  I tried to figure out this issue but unable to reproduce it.
Sharing conf files. Hope this help.
** We are not using verdaccio with docker.   **
Verdaccio version: 2.3.6
Verdaccio config:
# path to a directory with all packages
storage: ./storage

# a list of users
#
# This is deprecated, use auth plugins instead (see htpasswd below).
# users:
  # admin:
    # crypto.createHash('sha1').update(pass).digest('hex')
    # password: a94a8fe5ccb19ba61c4c0873d391e987982fbbd3

web:
  # WebUI is enabled as default, if you want disable it, just uncomment this line
  #enable: false

  title: Registry

  #logo: logo.png

auth:
  htpasswd:
    file: ./htpasswd
    # Maximum amount of users allowed to register, defaults to "+infinity".
    # You can set this to -1 to disable registration.
    max_users: -1

# a list of other known repositories we can talk to
uplinks:
  npmjs:
    #url: http://localhost:5984/registry
    url: https://registry.npmjs.org/

    # amount of time to wait for repository to respond
    # before giving up and use the local cached copy
    #timeout: 30s

    # maximum time in which data is considered up to date
    #
    # default is 2 minutes, so server won't request the same data from
    # uplink if a similar request was made less than 2 minutes ago
    #maxage: 2m

    # if two subsequent requests fail, no further requests will be sent to
    # this uplink for five minutes
    #max_fails: 2
    #fail_timeout: 5m

    # timeouts are defined in the same way as nginx, see:
    # http://wiki.nginx.org/ConfigNotation

    # add/override HTTP headers sent to the uplink server
    # this allows for HTTP Basic auth for example:
    #headers:
    #  authorization: "Basic YourBase64EncodedCredentials=="

    # set this to false to prevent tarballs from this upstream
    # to be stored in the local storage (defaults to true)
    #cache: false

packages:
  '@*/*':
    # scoped packages
    access: $authenticated
    publish: $authenticated
    proxy: npmjs
  # uncomment this for packages with "local-" prefix to be available
  # for admin only, it's a recommended way of handling private packages
  #'local-*':
  #  access: admin
  #  publish: admin
  #  # you can override storage directory for a group of packages this way:
  #  storage: 'local_storage'

  '**':
    # allow all users to read packages (including non-authenticated users)
    #
    # you can specify usernames/groupnames (depending on your auth plugin)
    # and three keywords: "$all", "$anonymous", "$authenticated"
    access: $authenticated

    # allow 'admin' to publish packages
    publish: $authenticated

    # if package is not available locally, proxy requests to 'npmjs' registry
    proxy: npmjs

#####################################################################
# Advanced settings
#####################################################################

## Special packages publish configurations
#publish:
## This will allow the publisher to publish packages even if any uplink is down.
#  allow_offline: true

# if you use nginx with custom path, use this to override links
#url_prefix: https://dev.company.local/verdaccio/

# You can specify listen address (or simply a port).
# If you add multiple values, verdaccio will listen on all of them.
#
# Examples:
#
#listen:
# - localhost:4873            # default value
# - http://localhost:4873     # same thing
# - <IP_ADDRESS>:4873              # listen on all addresses (INADDR_ANY)
# - https://example.org:4873  # if you want to use https
# - [::1]:4873                # ipv6
# - unix:/tmp/verdaccio.sock    # unix socket

# Configure HTTPS, it is required if you use "https" protocol above.
#https:
#  key: path/to/server.key
#  cert: path/to/server.crt
#  ca: path/to/server.pem

# type: file | stdout | stderr
# level: trace | debug | info | http (default) | warn | error | fatal
#
# parameters for file: name is filename
#  {type: 'file', path: 'verdaccio.log', level: 'debug'},
#
# parameters for stdout and stderr: format: json | pretty | pretty-timestamped
#  {type: 'stdout', format: 'pretty', level: 'debug'},
logs:
  - {type: stdout, format: pretty, level: http}
  #- {type: file, path: verdaccio.log, level: info}

# you can specify proxy used with all requests in wget-like manner here
# (or set up ENV variables with the same name)
#http_proxy: http://something.local/
#https_proxy: https://something.local/
#no_proxy: localhost,<IP_ADDRESS>

# maximum size of uploaded json document
# increase it if you have "request entity too large" errors
#max_body_size: 1mb

# Notify Settings
# Notify was built primarily to use with Slack's Incoming
# webhooks, but will also deliver a simple payload to
# any endpoint. Currently only active for publish / create
# commands.
notify:
  # Choose a method. Technically this will accept any HTTP
  # request method, but probably stick to GET or POST
  method: POST
  # Only run this notification if the package name matches the regular
  # expression
  packagePattern: ^(.*)$
  # Any flags to be used with the regular expression
  packagePatternFlags: i
  # If this endpoint requires specific headers, set them here
  # as an array of key: value objects.
  headers: [{'Content-type': 'application/x-www-form-urlencoded'}]
  # set the URL endpoint for this call
  endpoint: https://hooks.slack.com/services/XXXXXXXXX/XXXXXXXXX/XXXXXXXXXXXXXX
  # Finally, the content you will be sending in the body.
  # This data will first be run through Handlebars to parse
  # any Handlebar expressions. All data housed in the metadata object
  # is available for use within the expressions.
  # content: ' {{ handlebar-expression }}'
  # For Slack, follow the following format:
  content: '{ "text": "Package *{{ name }}* published to version *{{ dist-tags.latest }}*", "username": "Verdaccio", "icon_emoji": ":package:" }'

  # Multiple notification endpoints can be created by specifying a collection
  'example-package-1':
    method: POST
    # Only run this notification if the package name matches the regular
    # expression
    packagePattern: ^example-package-regex$
    # Any flags to be used with the regular expression
    # since verdaccio 2.2.2 this property has been disabled read #108
    # it will be re-enabled after 2.5.0
    # packagePatternFlags: i
    # If this endpoint requires specific headers, set them here
    # as an array of key: value objects.
    # headers supports as well a literal object
    headers: {'Content-type': 'application/x-www-form-urlencoded'}
    # set the URL endpoint for this call
    endpoint: https://hooks.slack.com/...
    # Finally, the content you will be sending in the body.
    # This data will first be run through Handlebars to parse
    # any Handlebar expressions. All data housed in the metadata object
    # is available for use within the expressions.
    content: ' {{ handlebar-expression }}'
    # For Slack, follow the following format:
    # content: '{ "text": "Package *{{ name }}* published to version *{{ dist-tags.latest }}*", "username": "Verdaccio", "icon_emoji": ":package:" }'

Our nginx conf as follows:
# For more information on configuration, see:
#   * Official English Documentation: http://nginx.org/en/docs/
#   * Official Russian Documentation: http://nginx.org/ru/docs/

user nginx;
worker_processes auto;
error_log /var/log/nginx/error.log;
pid /run/nginx.pid;

# Load dynamic modules. See /usr/share/nginx/README.dynamic.
include /usr/share/nginx/modules/*.conf;

events {
    worker_connections 1024;
}

http {
    log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for"';

    access_log  /var/log/nginx/access.log  main;

    sendfile            on;
    tcp_nopush          on;
    tcp_nodelay         on;
    keepalive_timeout   65;
    types_hash_max_size 2048;
    client_max_body_size 20M;

    include             /etc/nginx/mime.types;
    default_type        application/octet-stream;

    # Load modular configuration files from the /etc/nginx/conf.d directory.

Using verdaccio without docker.
I tried to configure the nginx, the way @ayusharma did but could not install react-mdl as well geoip-lite, where as I am able to install each-async package. Size of the package seems to be the issue.

happens to me also with current verdaccio docker

it doesnt happen if i do wget package from localhost but does if i use a non loop ip address.
i've installed sinopia docker and it doesnt happen

Had this issue once when the filesystem was full. Did you check this?

I am also experiencing this issue. I've found that I am able to reproduce it consistently from a clean install on local by rate-limiting curl and attempting to download a relatively large package's tgz file:
$ git clone git@github.com:verdaccio/verdaccio.git
$ cd verdaccio
$ npm i
$ npx verdaccio

Then in another terminal:
$ while true; do curl 'http://<IP_ADDRESS>:4873/picturefill/-/picturefill-3.0.2.tgz' --limit-rate 1M | md5sum; sleep 1; done

Output from curl:
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
 96 14.5M   96 14.0M    0     0  1023k      0  0:00:14  0:00:14 --:--:-- 1022k
curl: (18) transfer closed with 546327 bytes remaining to read
27104771a7a00310e993bbace951a332  -
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
 96 14.5M   96 14.0M    0     0  1023k      0  0:00:14  0:00:14 --:--:-- 1025k
curl: (18) transfer closed with 546327 bytes remaining to read
27104771a7a00310e993bbace951a332  -
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
 96 14.5M   96 14.0M    0     0  1023k      0  0:00:14  0:00:14 --:--:-- 1022k
curl: (18) transfer closed with 546327 bytes remaining to read
27104771a7a00310e993bbace951a332  -
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 14.5M  100 14.5M    0     0  1023k      0  0:00:14  0:00:14 --:--:-- 1023k
2d634f05cb3f0f0ad5143be7ddf66924  -
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 14.5M  100 14.5M    0     0  1024k      0  0:00:14  0:00:14 --:--:-- 1025k
2d634f05cb3f0f0ad5143be7ddf66924  -
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 14.5M  100 14.5M    0     0  1023k      0  0:00:14  0:00:14 --:--:-- 1026k
2d634f05cb3f0f0ad5143be7ddf66924  -
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
 95 14.5M   95 13.8M    0     0  1023k      0  0:00:14  0:00:13  0:00:01 1027k
curl: (18) transfer closed with 742776 bytes remaining to read
465ef6504058ffa825c8210d60651f2b  -
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
 92 14.5M   92 13.4M    0     0  1023k      0  0:00:14  0:00:13  0:00:01 1026k
curl: (18) transfer closed with 1201157 bytes remaining to read
90c60889c22766003927b0f54903ab68  -
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 14.5M  100 14.5M    0     0  1023k      0  0:00:14  0:00:14 --:--:-- 1026k
2d634f05cb3f0f0ad5143be7ddf66924  -
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
 97 14.5M   97 14.2M    0     0  1023k      0  0:00:14  0:00:14 --:--:-- 1027k
curl: (18) transfer closed with 349878 bytes remaining to read
611379484ebffff06668801af5aa1c3d  -
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
 93 14.5M   93 13.6M    0     0  1023k      0  0:00:14  0:00:13  0:00:01 1025k
curl: (18) transfer closed with 1004708 bytes remaining to read
bb6050f5780259b0ca3e0dd352d83e00  -

That file should is 15MB and should have an MD5 of 2d634f05cb3f0f0ad5143be7ddf66924. Without the --rate-limit option, it works perfectly fine.
For context, we have this behind a reverse proxy (tried both nginx and apache) and the same behavior occurs consistently as the proxy runs out of allowed buffer space while streaming over a slow connection.

Did this get resolved? Someone said this wasn't an issue on sinopia, comparing the docker files they both use different versions of node, maybe going to node 6.x might help, anyone tried?

Put in the workaround and it seems like a stable fix although there's probably a performance cost. Looks like this might be a legit node issue
https://github.com/nodejs/node/issues/13391

Thanks @dbroadhurst for fixing this. Shipped on v2.6.5

Thanks for the fix. For anyone not using the official docker images, upgrading to Node 8.9.0+ (or 9.0.0+) will fix the issue.

Having this issue with the latest docker image (sha256: 122111476bf8e6f397de4babb3cd45390b3d3ecc8bd60ec385d01bafd4ce358f).
Any ideas?

@binarious I'm thinking this is a slow network connection issue. The default timeout of 30s might be too short: http://www.verdaccio.org/docs/en/uplinks.html
Although, if I set it to 1s, I see "error: ESOCKETTIMEDOUT"  in the logs, whereas for this intermittent issue, I don't get anything in the logs. Almost seems like a client issue.

i have to agree with @actraiser - i am having the same problem here with 2.7.4 :(

I am new to node and i am trying to set up local repo on windows server, and it worked perfectly until i published larger package >2,5mb and i cant install it from another machine, currently it is node 10 and i don't know where i should put keepAliveTimeout can i get a little help. Tnx

In my case @rostislav-simonik solution solved the problem.
@crowz4k you can find the file in node_modules\verdaccio\build\lib\bootstrap.js

npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha1-WR2E02U6awtKO5343lqoEI5y5eA=) seems to be corrupted. Trying one more time. npm ERR! code EINTEGRITY npm ERR! sha1-WR2E02U6awtKO5343lqoEI5y5eA= integrity checksum failed when using sha1: wanted sha1-WR2E02U6awtKO5343lqoEI5y5eA= but got sha512-KI1+qOZu5DcW6wayYHSzR/tXKCDC5Om4s1z2QJjDULzLcmf3DvzS7oluY4HCTrc+9FiKmWUgeNLg7W3uIQvxtQ== sha1-Eh+evEnjdm8xGnbh+hyAA8SwOqY=. (12807 bytes)
I've been having this issue for a very long time now....help anyone? I've tried doing npm install &/or npm ci and neither make a difference I still recieve the same error.

Node v8.9.3
NPM v6.4.1
Verdaccio v3.10.0
still facing this problem. It will comeout with
ZlibError: zlib: unexpected end of file

WARN tarball tarball data for<EMAIL_ADDRESS>(sha1-WR2E02U6awtKO5343lqoEI5y5eA=) seems to be corrupted

and  fix from @rostislav-simonik
// node_modules\verdaccio\build\lib\bootstrap.js
// line 141
} else {
        // http
        webServer = _http2.default.createServer(app);

      }
      webServer.keepAliveTimeout=0 // <<< WORK AROUND

did fix the bug


Dockerhub image link is missing

This tool is super awesome! I just wanted to mention that the README should link to the full Dockerhub image:
wasserth/totalsegmentator_container:master

Thank you for this hint. I updated the readme.


Uninstall Service

I need a command to Uninstall an existing WinService.

When I have the time I can look into that. Shouldnt be that much different.


Protos with messages containing oneof don't compile with option generate_accessors to Some(false)

Describe the bug
When you generate code programmatically for protobufs containing messages with oneof and option generate_accessors: Some(false) the generated code doesn't compile.
I get this error:
error[E0599]: no function or associated item named `has_field1` found for type `oneof::MessageWithOneof` in the current scope
   --> src/oneof.rs:187:39
    |
30  | pub struct MessageWithOneof {
    | --------------------------- function or associated item `has_field1` not found for this
...
187 |                     MessageWithOneof::has_field1,
    |                                       ^^^^^^^^^^
    |                                       |
    |                                       function or associated item not found in `oneof::MessageWithOneof`
    |                                       help: there is a method with a similar name: `get_field1`

error[E0599]: no function or associated item named `has_case2` found for type `oneof::MessageWithOneof` in the current scope
   --> src/oneof.rs:192:39
    |
30  | pub struct MessageWithOneof {
    | --------------------------- function or associated item `has_case2` not found for this
...
192 |                     MessageWithOneof::has_case2,
    |                                       ^^^^^^^^^
    |                                       |
    |                                       function or associated item not found in `oneof::MessageWithOneof`
    |                                       help: there is a method with a similar name: `get_case2`

To Reproduce
Steps to reproduce the behavior:

Clone the repro repo by running  git clone git@github.com:Elrendio/OneofGrpcError.git
Try to compile: cd OneofGrpcError && cargo check
See error

Expected behavior
Code should compile.
System information
I'm on MacOS High Sierra version 10.13.3, with an 2.8 GHz Intel Core i7 processor.
Additional context
I'm using rustc 1.37.0 (eae3437df 2019-08-13) and cargo 1.37.0 (9edd08916 2019-08-02). Other dependencies are in the Cargo.toml of the repro repo.
You can find the build script in the build.rs file.

@nrc PTAL


Fixed issue where containerapp up would not honor --registry-server.

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

Task: https://msazure.visualstudio.com/Antares/_backlogs/backlog/Antares CLI and PS/Epics/?workitem=14664549

#127


Make the H3 build script work properly on Debian platforms

Cherry-picked to v9.1.x branch.
(This file is not in 9.0.x, so can't back port there unless we want to copy it over as well).


[Python] Error while creating a ParquetDataset on a path without '_common_dataset' but with an empty '_tempfile'

I suspect that there's an error in this line of code:
https://github.com/apache/arrow/blob/master/python/pyarrow/parquet.py#L926
While validating schema in the initialisation of a ParquetDataset, we assume that if _common_metadata file does not exist, the schema should be inferred from the first piece of that dataset. The first piece, in my experience, could refer to a file named with an underscore, that does not necessarily have to contain the schema, and could be an empty file, e.g. _tempfile.
/tmp/pq/
├── part1.parquet
└── _tempfile

This behavior is allowed by the parquet specification, and we should probably ignore such pieces.
On a cursory look, we could do either of the following.

Choose the first piece with path that does not start with "_"
Sort pieces by name, but put all the "_" pieces later while making the manifest. https://github.com/apache/arrow/blob/master/python/pyarrow/parquet.py#L729
Silently exclude all the files starting with "_" here, but this will need to be tested: https://github.com/apache/arrow/blob/master/python/pyarrow/parquet.py#L770

Can you open a JIRA issue?

Let's track this on Jira: https://issues.apache.org/jira/browse/ARROW-4516


Upgrade calibre.app to v2.45.0

Thank you for the contribution. It was merged directly as 3b9d5f417fd2cb07d5fbd7901ce1718c30d31238 to keep commit history cleaner. Your contribution is still credited to you.

Thank you.


[CARBONDATA-1920] [PrestoIntegration] Sparksql query result is not same as presto on same sql

Sparksql query result is not same as presto on same sql
https://issues.apache.org/jira/browse/CARBONDATA-1920
Problem: In Stream Readers we are only decoding dictionary value in case our javatype is slice and it is not decimal type
Solution: To solve this problem we need to do dictionary decoding in case of everydatatype if its dictionary exists because user can put any data type in dictionary_include when creating carbontable
This Pr Include Following Changes
1.In  stream readers functionality of dictionary decoding is provided
2.Removed duplicate variables
3.In presto filter util case of smallint was missing in ConvertDataByType method,it is added
4.Refactor the code of carbondatastorecreator to include dictionary encoding
5.In CarbonDictionaryDecodeReadSupport create sliceArrayBlock Only If data type is string in case of any other datatype do not create sliceArrayBlock we can decode the dictionary values using dictionary
array the same way orc is doing on presto
6.test cases are same but with dictionary encoding
How Testing Is Done
1.mvn -Pspark-2.1 clean install is passing
2.Manually checked for all the tpch presto queries
3.check all the possible queries with both dictionary_include and dictionary_exclude

@chenliang can you please review this pr

sure, i will review it. thanks for your contribution.

Have you used carbondata 1.3.0-master code and spark 2.1 to test ?
Same issues ?

@chenliang613 yes same issues are getting replicated for both 1.2.0 and 1.3.0

this pr verified , looks good to me.


chore: upgrade lib dependencies

Description
This package upgrade downgrades the yearn sdk version to stabilize security access errors as shown here: https://github.com/shapeshift/lib/pull/1076
Notice

[x] Have you followed the guidelines in our Contributing guide?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[x] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #
Risk
Low
Testing

yearn network errors should no longer be spewing in the console

Engineering
:point_up:
Operations
:point_up:
Screenshots (if applicable)

This doesn't have the effect that we thought it would, but we should probably merge as it technically does contain the most recent lib package versions, and makes web no worse.

Merging to keep packages up-to-date, but noting it has no effect on any of the issues.
I've updated this branch inline with the current develop branch and run it locally to confirm it doesn't break anything/make it worse.


fix policy framework deployment step

Signed-off-by: Mike Ng<EMAIL_ADDRESS>to address the comments in https://github.com/open-cluster-management-io/open-cluster-management-io.github.io/pull/108#pullrequestreview-698554404

/lgtm

Thanks for fixing these, @mikeshng!


Remove supports for float

Because they don't belong to here anyway

Ints are important for a real calculator


set backupdir does not support double trailing slashes to include path info in filename

What steps will reproduce the problem?
1. add to your vimrc:  set backupdir=~/tmp/vimbackupdir//
2. cd /some/dir
3. vim somefile
4. :w

What is the expected output?
~/tmp/vimbackupdir/ should have a filename with embedded path info so that you
can edit the same filename in different directories without overwriting. The
same way that "set directory" handles it for swap files.

What do you see instead?
Files in backupdir have only the filename.

What version of the product are you using? On what operating system?
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Aug 12 2013 08:50:31)
Ubuntu 12.04.2 LTS

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 13 Nov 2013 at 11:44

Any news on this ?

Any news on this ?

It is still in the todo list.
Best,
Christian
Eingebildete Leute haben mir Leid getan, denn sie tragen ja ihren
Trost mit sich.
-- George Eliot (eigentlich Mary Ann Evans)

On 2015-11-18, Christian Brabandt wrote:

Any news on this ?

It is still in the todo list.

Do you have an updated patch for this?  I tried applying the one
I have from December, 2013, and unsurprisingly, it failed.
Regards,
Gary

On Do, 29 Jun 2017, Gary Johnson wrote:

On 2015-11-18, Christian Brabandt wrote:

Any news on this ?

It is still in the todo list.

Do you have an updated patch for this?  I tried applying the one
I have from December, 2013, and unsurprisingly, it failed.

Oh thanks for noticing me. I'll look into it.
Best,
Christian
Schließlich erreicht jeder Mensch jedes Ziel. Er muß es nur genügend
weit zurückstecken.
-- Hans Söhnker

Updated patch, including a test can be found here

On Do, 29 Jun 2017, Gary Johnson wrote:

On 2015-11-18, Christian Brabandt wrote:

Any news on this ?

It is still in the todo list.

Do you have an updated patch for this?  I tried applying the one
I have from December, 2013, and unsurprisingly, it failed.

I have updated the patch and included a test. It is available here:
https://github.com/chrisbra/vim-mq-patches/blob/master/backupdir
and I attach it for reference here as well.
Best,
Christian
Alles wahre Aperçu kommt aus einer Folge und bringt Folge. Es ist
ein Mittelglied einer großen, produktiv aufsteigenden Kette.
-- Goethe, Maximen und Reflektionen, Nr. 26

On 2017-06-30, Christian Brabandt wrote:

On Do, 29 Jun 2017, Gary Johnson wrote:

On 2015-11-18, Christian Brabandt wrote:

Any news on this ?

It is still in the todo list.

Do you have an updated patch for this?  I tried applying the one
I have from December, 2013, and unsurprisingly, it failed.

I have updated the patch and included a test. It is available here:
https://github.com/chrisbra/vim-mq-patches/blob/master/backupdir
and I attach it for reference here as well.

Thank you.  It doesn't seem to be working, though.  I updated to Vim
8.0.691, applied the patch, built and installed on a system running
Red Hat Enterprise Linux Server release 7.2.
$ vim
:set backup? backupdir?
  backup
  backupdir=~/tmp/vimbackup//

:e ~/hello.txt
" Make some changes.
:wq
$ ls ~/tmp/vimbackup
hello.txt~

Regards,
Gary

On Fr, 30 Jun 2017, Gary Johnson wrote:

Thank you.  It doesn't seem to be working, though.  I updated to Vim
8.0.691, applied the patch, built and installed on a system running
Red Hat Enterprise Linux Server release 7.2.
$ vim
:set backup? backupdir?
  backup
  backupdir=~/tmp/vimbackup//

:e ~/hello.txt
" Make some changes.
:wq
$ ls ~/tmp/vimbackup
hello.txt~

Hm, I tested it and even included a test. Are you sure, you included the
patch in the vim you have been running?
Best,
Christian
Wer sich zu groß fühlt, um kleine Aufgaben zu erfüllen, ist zu klein,
um mit großen Aufgaben betraut zu werden.
-- Jacques Tati

On 2017-06-30, Christian Brabandt wrote:

On Fr, 30 Jun 2017, Gary Johnson wrote:

Thank you.  It doesn't seem to be working, though.  I updated to Vim
8.0.691, applied the patch, built and installed on a system running
Red Hat Enterprise Linux Server release 7.2.
$ vim
:set backup? backupdir?
  backup
  backupdir=~/tmp/vimbackup//

:e ~/hello.txt
" Make some changes.
:wq
$ ls ~/tmp/vimbackup
hello.txt~

Hm, I tested it and even included a test. Are you sure, you included the
patch in the vim you have been running?

As sure as I know how to be.  I applied the patch to a system at
home and to one at work.  Both fail the same way.  I ran "patch
--dry-run -p1 < ~/.vim/backupdir.patch" again on the second system
to check and it reported that the patches were already there.
Running the test gives me just this and an empty test_backup.res
file.
$ make test_backup.res
VIMRUNTIME=../../runtime; export VIMRUNTIME;  ../vim -f  -u unix.vim -U NONE --noplugin --not-a-term -S runtest.vim test_backup.vim

Regards,
Gary

This bug still exists.
I tested this using Vim 8.1.239 x64 on Windows 10 x64.
Vim 8.1.239 x64 for Windows was downloaded from
https://github.com/vim/vim-win32-installer/releases
Is there any plan to fix this bug?
Regards~

On 2018-08-07, Bram Moolenaar wrote:

Closed #179 via b782ba4.

Thank you!
Regards,
Gary


docs(zh-cn): Reviewed 40_uploading-a-dataset-to-the-hub.srt

docs(zh-cn): Reviewed 40_uploading-a-dataset-to-the-hub.srt #390

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


vscode-extensions.Gleam.gleam: init at 1.3.0

Two minor points I'm uncertain about:

"Gleam.gleam" is capitalized in the VSCode Marketplace unique ID, but most (all?) other nix vscode-extensions seem to be lowercase.
Version discrepancy: v1.2.0 vs v1.3.0 - see https://github.com/gleam-lang/vscode-gleam/issues/13

Motivation for this change
Gleam support for VSCode
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 126329 run on x86_64-darwin 1

This is only my opinion, but I would say, leave the package name lowercase and inside the publisher and name, you can use the right casing. I don't think it brings anything to have a package name having some uppercase and some lowercase.
Other than that, interesting version issue, let's wait to see what happened there.

@OliverEvans96
Do you have time to address the reviews to finish this PR?
Or shall I fork your repo and pick it up?

@sharno I would finish it myself, but I'm a bit preoccupied right now with family things, and don't have much spare attention. If you  have some free cycles to knock it out, I would definitely appreciate it! Otherwise, I'll come back to it when I get a chance.

Please fix merge conflict.

Closing due to being stale


New release

May I kindly ask for a new release including the fix from my pull request and the other changes? I want to have it in Foreman and a new release would be preferred over a snapshot version. Thanks in advance!

@ohadlevy @dmitri-d I know y'all are a bit removed these days from the project, but if you were able to do address this release request @theforeman would appreciate it!

I just checked and it seems I have the permissions to do such a release. I will try to do that in the coming days.

I am sorry that I took so long, life and all...
I present you: safemode 1.3.6, which is essentially current master, since that included the change you wanted. I also updated the travis.yml to result in a green build:

https://rubygems.org/gems/safemode/versions/1.3.6
https://travis-ci.org/github/svenfuchs/safemode/builds/722711041

One question pops into my mind, @ekohl @dgoetz : Which ruby-version(s) does foreman install/use/support? Since foreman/satellite is a major user of safemode, I see this information as a important datapoint. Also, something I want to know before trimming away older and unsupported rubies from the build-matrix. If there is OTOH an installation base that still uses older Ruby-Version with SCL-Securitypatches, I would need to tweak the tests and implementation to also run on that, right?

At this moment we use 2.5 or later everywhere. From a Foreman point of view, we no longer care about Ruby 2.4 and older. I think the SCLs don't really carry patches and we don't do any special testing. AFAIK our CI uses RVM to install a Ruby 2.5. Debian 10 and Ubuntu 18.04 also ship Ruby 2.5.


Workaround for TransactionTrace serialization issue

#377

Closing this because a better solution in #380 is done.


feat: make analysis buttons open workflow landing pages (#137)

No error handling for the API request
Only regulation is set up

@mvdbeek Thanks for the feedback! I've:

Updated the types to make more room for alternative keys (though in a different way than suggested -- I wanted to make it explicit what the keys can be)
Added public: true to the API request body
Added ?public=true to the constructed landing page URL (but left the URL encoding in -- although it's not necessary in theory, I'm inclined to be cautious and default to encoding things when constructing URLs)

@hunterckx, can you rebase this, please? Thanks!

For right now this is working well. I have a few things to build on here, could we get this merged ?


scroll wheel input translated to horizontal scrolling

It would be really useful to have an option that translates scrolling from a scroll wheel (vertical scroll input) into horizontal scrolling for areas that scroll horizontally. Perhaps this is an easy implementation, but I've spent some time trying to get it to work and I have been unsuccessful.

That would be fantastic. Thanks!


DataHub CLI Import Error

Describe the bug
An error when run datahub version after went through the steps for using DataHub CLI
from avro.schema import make_avsc_object
ImportError: cannot import name 'make_avsc_object' from 'avro.schema' (/Users/username/opt/anaconda3/envs/py37/lib/python3.7/site-packages/avro/schema.py)

To Reproduce
Steps to reproduce the behavior:

Go to 'https://datahubproject.io/docs/cli'
Install DataHub CLI by following the online instruction
Run 'datahub version'
See error

Expected behavior
the correct version of datahub
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: MacOS
Browser: n/a
Version: latest
Python version: 3.7

seems most likely it is my local py37 environment. A fresh py36 env seems working.

It worked this way:
pip install avro==1.11.0
pip install confluent-kafka
pip uninstall avro
pip install acryl-datahub

It seems that there's some conflicting versions of dependencies for avro and acryl-datahub.
I hope this problem would be fixed - it causes so much pain to create correct env.

I know this is an old issue, but leaving this for posterity:
The actual issue is an incompatibility between avro and avro-python3 - they end up overwriting each others files when both are installed. The workaround is to uninstall avro-python3 and then reinstall avro.


starting to implement truncation in the distributions wip #11

need to address inverse cdf, pdf, and cdf to use the truncated probability range still, but the probability ranges are now properly being set (i think)

still need to fix cdf and pdf.

I am concerned our truncation approach is not quite right, we may need to rethink some of the details here.

@HenryGeorgist I am sorry I lost track of this PR. Are there details in specific I can investigate, or would you rather put that off?


feat(useQueryParameters): Add useQueryParameters hook

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Error occurs when create ndarray on GPU

When I run the command c = mx.nd.empty((2, 3), mx.gpu(1)), it works well.
But when I run b = mx.nd.zeros((2, 3), mx.gpu(1)), error occurs:
"/usr/local/lib/python2.7/dist-packages/mxnet-0.5.0-py2.7.egg/mxnet/ndarray.pyc in zeros(shape, ctx, dtype)
676     """
677     arr = empty(shape, ctx, dtype)
--> 678     arr[:] = 0.0
679     return arr
680
/usr/local/lib/python2.7/dist-packages/mxnet-0.5.0-py2.7.egg/mxnet/ndarray.pyc in setitem(self, in_slice, value)
201                 value.copyto(self)
202         elif isinstance(value, numeric_types):
--> 203             NDArray._set_value(float(value), out=self)
204         elif isinstance(value, (np.ndarray, np.generic)):
205             self._sync_copyfrom(value)
/usr/local/lib/python2.7/dist-packages/mxnet-0.5.0-py2.7.egg/mxnet/ndarray.pyc in generic_ndarray_function(*args, **kwargs)
1117                 ctypes.c_int(len(kwargs)),
1118                 c_array(ctypes.c_char_p, kwargs.keys()),
-> 1119                 c_array(ctypes.c_char_p, [str(i) for i in kwargs.values()])))
1120         if n_mutate_vars == 1:
1121             return mutate_vars[0]
/usr/local/lib/python2.7/dist-packages/mxnet-0.5.0-py2.7.egg/mxnet/base.pyc in check_call(ret)
75     """
76     if ret != 0:
---> 77         raise MXNetError(py_str(_LIB.MXGetLastError()))
78
79 def c_str(string):
MXNetError: [14:27:07] src/ndarray/ndarray.cc:173: GPU is not enabled
"
I don't know what's the problem....So SOS!!!

turn on CUDA in config.mk. The installation guide discribes how

My config.mk is like this:
#---------------------
choice of compiler
#--------------------
export CC = gcc
export CXX = g++
export NVCC = nvcc
whether compile with debug
DEBUG = 0
the additional link flags you want to add
ADD_LDFLAGS = -L/opt/openblas/lib -lopenblas
the additional compile flags you want to add
ADD_CFLAGS = -I/opt/openblas/include
#---------------------------------------------
matrix computation libraries for CPU/GPU
#---------------------------------------------
whether use CUDA during compile
USE_CUDA = 1
add the path to CUDA library to link and compile flag
if you have already add them to environment variable, leave it as NONE
USE_CUDA_PATH = /usr/local/cuda
USE_CUDA_PATH = /usr/local/cuda-7.5
whether use CuDNN R3 library
USE_CUDNN = 1
whether use cuda runtime compiling for writing kernels in native language (i.e. Python)
USE_NVRTC = 1
whether use opencv during compilation
you can disable it, however, you will not able to use
imbin iterator
USE_OPENCV = 1
use openmp for parallelization
USE_OPENMP = 1
choose the version of blas you want to use
can be: mkl, blas, atlas, openblas
in default use atlas for linux while apple for osx
UNAME_S := $(shell uname -s)
ifeq ($(UNAME_S), Darwin)
USE_BLAS = apple
else
USE_BLAS = openblas
endif
add path to intel library, you may need it for MKL, if you did not add the path
to environment variable
USE_INTEL_PATH = NONE
If use MKL, choose static link automatically to allow python wrapper
ifeq ($(USE_BLAS), mkl)
USE_STATIC_MKL = 1
else
USE_STATIC_MKL = NONE
endif
#----------------------------
distributed computing
#----------------------------
whether or not to enable multi-machine supporting
USE_DIST_KVSTORE = 1
whether or not allow to read and write HDFS directly. If yes, then hadoop is
required
USE_HDFS = 0
path to libjvm.so. required if USE_HDFS=1
LIBJVM=$(JAVA_HOME)/jre/lib/amd64/server
whether or not allow to read and write AWS S3 directly. If yes, then
libcurl4-openssl-dev is required, it can be installed on Ubuntu by
sudo apt-get install -y libcurl4-openssl-dev
USE_S3 = 0
#----------------------------
additional operators
#----------------------------
path to folders containing projects specific operators that you don't want to put in src/operators
EXTRA_OPERATORS =
#----------------------------
plugins
#----------------------------
whether to use torch integration. This requires installing torch.
TORCH_PATH = $(HOME)/torch
MXNET_PLUGINS += plugin/torch/torch.mk
whether to use sframe integration. This requires build sframe
git@github.com:dato-code/SFrame.git
SFRAME_PATH = $(HOME)/SFrame
MXNET_PLUGINS += plugin/sframe/plugin.mk
I have turned on CUDA and passed the compilation, but it still doesn't work....

I have set USE_CUDA=1 in config.mk and passed the compilation, but it still doesn't work...


add option to select/change the CSV delimiter

Default ist currently a semicolon ';'  ... but maybe its not so importan. must Tools can import either

Since most post processing tools can detect/change the delimiter this feature will not be implemented to Keep the Addon as simple as possible.


Help prevent block form and file manager modals from blending in with background page content

Current:
block form modal

file manager modal

Changes:
block form modal

file manager modal

I'd really love to see the file manager dialog popup improved like this, the transparency in the currently blue bar makes it feel like the page hasn't loaded properly.

This is really nice. As we mentioned a day or so ago we're planning on doing additional work on usability and accessibility, but this looks simple and targeted enough to include in 8.4.1


Version 2.1.1 - ElasticSearch Backend Listener

Added use of assertionArray
getElapsedTime now returns a generic date for comparison in Jenkins AND the elapsed time according to today.
Added "sentBytes" metric
ResponseTime uses the getTime() method
Added timeout to avoid hanging requests
Corrected formatting of dates
Added logging in case of failures

Yes, there was an issue with deploy process, it is fixed now. Your plugin should be available.


Add UOps pattern matcher regression tests

Standalone PR to add simple tests for each of the important fields that gets matched on.

I still 2+ wrong UOps.

@Qazalin feel free to merge if this is correct and useful

test_dup_name is testing an invalid graph since y1 and y2 cannot exist in the same UOpGraph, I'd keep it though it's a useful behavior test.


Not working with entity Frame work .

hi i am trying to test a logic that is not working with entity framework and that is throwing an error : No connection string Name 'my connection string name' could be found in the application config file but i ran a test case without smoke and that is working fine.do i need  to add any additional config file.
Please check this issue i am sucked  in the middle .

Thanks for reporting this. Could you add some instructions and/or sample code that can be used to reproduce the problem?


⚠ ClamAV has degraded performance

In d50bbaa, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 441 ms

Resolved: ClamAV performance has improved in 34174a6 after 11 minutes.


enable updating custom version files with changeset version

Affected Packages
changesets/cli , version command
Problem
sometimes a package wants to export it's version. To do that, it needs to include something like
// version.js , autogenerated, do not modify
export const VERSION = '1.2.3';

// index.js
export VERSION from './version.js'

in it's output.
But version.js can only be updated after changeset version has bumped package.json. Leading to a situation where the version value in package.json and version.js is different until a separate generate-version-js script has been run.
If for whatever reason these two go out of sync, there could be a release where the VERSION export does not correctly reflect the version of package.json, which would be very confusing at best and lead to hard to track errors at worst.
Proposed solution
improve the version command allow updating other files with the bumped verison. This could be other files like documentation too.
One workaround could be to use a custom version arg with the @changeset/action, but this ties it to github actions.

Background: we are moving svelte to a pnpm monorepo with changesets and need to export the version in unbundled esm.

Looks like with commit: false option which is the default, it is possible to do this after changeset version and before commiting. The changeset action allows to pass a custom version script so with a bit of scripting effort this is achievable today.
Still would be nice to have something builtin.

Perhaps related to https://github.com/changesets/changesets/issues/982 requesting "postversion" script hook support

ok


GKE WLI to authenticate as another service account

TL;DR
Pod in GKE has a SA, I would like to authenticate as another service account dynamically via utilizing WLI to impersonate the other account.
Detailed design
in the examples,
https://github.com/google-github-actions/auth/blob/main/docs/EXAMPLES.md#workload-identity-federation-through-a-service-account
You can use WLF to authenticate as a service account, I would like to have the same ability to change the pod's identity using its identity which is obtained from WLI, at least for the GitHub action execution.
Using SA impersonation, the KSA/GSA with WLI will have the ability (previously granted with required permission) to impersonate a target SA to dynamically change the identity of the execution.
Additional information
No response

Hi @halradaideh thank you for opening an issue. I'm not sure I understand what you mean by:

I would like to have the same ability to change the pod's identity using its identity which is obtained from WLI, at least for the GitHub action execution.

Can you provide an example? What problem are you trying to solve?

i have a case with GitHub Actions
the runner is a pod with a KSA bound to a GSA
I am trying to dynamically change who is accessing GCP resources at execution time
so, I am aiming to use SA impersonation in order to allow the pod's KSA/GSA to impersonate another GSA based on the source of the execution
in this way, I need to grant the pod's SA the ability to impersonate others and manage IAM access per team per the team's SA and thus providing the execution access to the team's resources only

How is that different from Workload Identity Federation, which does this natively (and auth already supports)?
If you really want an impersonation chain, you can use the delegates option.

Sorry but I may be a bit confused
All examples requires workload_identity_provider, I thought there is a default one, but when I checked there is no workloadIdentityPools by default
If the federation example supports what I want, what should I fill workload_identity_provider then?

Can you give some concrete examples of what you're trying to do? You have a GKE cluster that is running some pods. Those pods have an identity, and you want to exchange that pod identity for another identity? Why - what are you trying to do? What workload is running on the pod?

The workload is a GitHub runner part of GitHub arc
I want the execution to have a unique identity at execution time since the runners are shared between teams
Then, based on the calculated identity, the execution will exchange the current pod identity to the proper one to limit access to other resources/secrets or stay with the default identity if not needed
regradless of my usecase, if WIF is the way to go, how can I use it without defining new pools/provider in GCP, I want to do the same gcloud do when it applies the impersonation
is there a default workload_identity_provider for GCP?

It look like your use case is the basic use case for this this action.
GitHub job got a unique id from id_token and you exchange it to a GCP id  (can be a SA, or can just be a principalSet).
In both case you have to create your own workload identity provider / pool.
At this point, you don't need any (gcp) service account linked to your pod.  You only want one if you want to give a base access (read only access to standard service ...)
Impersonation cannot be limited by a policy, if a policy give the permission on 2 services account to be impersonated by your server service account, then everybody executing things on this server will be able to impersonate the 2 service accounts.  To limit what people can do, you have to get an external data(here the id_token), and doing so, setup something on GCP (pool / provider).
Now in theory GCP could provide a defaut GitHub pool (it is not done), but it would be a contradiction to the federated service as nobody would be able to put their own additional provider on the pool, nor do any small configuration change on the GitHub provider would be possible.

I think multiple ideas are being conflated here. This action (google-github-actions/auth) is for taking GitHub-issued OIDC tokens and exchanging them for Google Cloud identities. Those tokens are signed by GitHub when a job is given id-token: 'write' permissions. With a properly-configured Google Cloud Workload Identity Pool/Provider, that OIDC token can be presented to Google Cloud (via sts.googleapis.com) to get a Google Cloud identity based on attributes in the given token.
If you're already on Google Cloud and you already have the desired identity, you can use Application Default Credentials to get the underlying instance identity credentials; this works on GKE too for KSA identities.
Neither GitHub-managed runners (on github.com) nor self-hosted runners have a specific "identity"; they have a series of claims for which you can map to identities. Those claims include things like the workflow name, caller, repo, and org, for example:
{
  // ...
  "ref": "refs/heads/main",
  "sha": "example-sha",
  "repository": "octo-org/octo-repo",
  "repository_owner": "octo-org",
  "actor_id": "12",
  "repository_visibility": "private",
  "repository_id": "74",
  "repository_owner_id": "65",
  "run_id": "example-run-id",
  "run_number": "10",
  "run_attempt": "2",
  "runner_environment": "github-hosted"
  "actor": "octocat",
  "workflow": "example-workflow",
  //...
}

If you want to map those claims to specific identities, you can use Workload Identity Federation (WIF) to establish those rules. For example, if you wanted a rule like:

Any workflow started by "sethvargo" can deploy Cloud Run services

You can create a WIF Pool and Provider that grants the corresponding principalSet:// permissions on the target Google Cloud project:
gcloud projects add-iam-policy-binding "my-project" \
  --role "roles/cloudrun.developer" \
  --member "principalSet://iam.googleapis.com/projects/416438230019/locations/global/workloadIdentityPools/github/attribute.actor/sethvargo"

Then using google-github-actions/auth, you could exchange the GitHub-provided OIDC token with a Google Cloud Federated Identity Token that can be used as a Bearer Token to deploy to Cloud Run
If you go that route, you should ensure that the KSA/GSA has no permissions on Google Cloud, since that identity is not actually used to interact with Google Cloud resources.

I think you might be confusing the Workload Identity for Kubernetes with the per-invocation workflow identity provided by GitHub Actions.

Thank you both for the clarification.
@GregoireW  I understand that if there were an identity on the Pod it would be able to access any other service account.

@sethvargo
Thank you for explaining the WIF, and yes multiple ideas are being conflated here.
What I initially wanted is not related to GitHub-issued OIDC tokens nor the WIF, I simply wanted to exchange the active service account on the pod dynamically based on a mapping I have in mind (map repos to teams), and to achieve that I wanted to use Service Account Impersonation.
Clearly, this Auth action is not the action to do what I am thinking of, although it would be nice to add another "auth" method to be the impersonation alongside the WIF and Service Account key this action already provides.
I managed somehow to do what I had in mind, but still, it is a hack (Poor's man impersonation 😆 )
      - name: get SA token for GCP auth
        id: token
        run: |
          #!/bin/bash
          set -x

<EMAIL_ADDRESS>
          TOKEN_URL="https://iamcredentials.googleapis.com/v1/projects/-/serviceAccounts/${TARGET}:generateAccessToken"
          SCOPE_URL="https://www.googleapis.com/auth/cloud-platform"

          SOURCE=$(curl -s -H  "Metadata-Flavor: Google"   "http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/email")

          TOKEN_REQUEST='{
            "delegates": ["'$SOURCE'"],
            "scope": "'$SCOPE_URL'"
          }'

          ACCESS_TOKEN=$(curl -s -H  "Metadata-Flavor: Google"   "http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/token"   | jq -r .access_token)
          curl -s -X POST -H "Content-Type: application/json" \
               -H "Authorization: Bearer $ACCESS_TOKEN" \
               -d "$TOKEN_REQUEST" \
               "$TOKEN_URL" > /tmp/token.json

          file=$(find * | grep gha-kubeconfig)
          DATA=$(cat /tmp/token.json | jq .accessToken)
          sed -i "s/token: .*/token: $DATA/g" $file

so at the end, if the impersonation logic is not considered part of the "auth" action, I think it should be a separated action.
anyway, in the WIF you provided, you mapped the principalSet as the user to a role, is it possible to grant it what another SA have (impersonate a GCP SA)?
I know I can make my mapping to map to a custom role to include what the SA have, but the idea I am trying to achieve is to make the workflow execution impersonate/impose a service account with what that service account has access to, thus have dynamic identity for the execution and manage access on service account level rather than doing it on the WIF

Hi @halradaideh I still think you're misunderstanding how WIF works. The underlying configuration for the code snippet you provided indicates that the KSA has permissions to impersonate the superset of all service accounts jobs might need; that means an insider or an attacker can get access to arbitrary identities, regardless of the source job or attributes.

If you already have a mechanism that is completely outside the end-user's control for running a GitHub Actions workflow on a specific pod with a specific identity, then you should grant that underlying KSA access to the GCP resources instead of relying on impersonation. You do not need auth at all in this case.

If you're relying on end-user's to chose the Service Account to impersonate in their workflow, that is a security misconfiguration as noted above. Please do not do this.

If you're trying to map metadata/attributes from the GitHub Actions workflow (such as the workflow name or GitHub repository) to specific permissions on Google Cloud, then use WIF + Attribute Conditions + Attribute Mappings to associate those permissions. principal:// and principalSet:// are identities just like a Service Account, User, or Group.

I simply wanted to exchange the active service account on the pod dynamically based on a mapping I have in mind (map repos to teams), and to achieve that I wanted to use Service Account Impersonation.

This certainly sounds like you're trying to use GitHub Actions + OIDC as it's intended to be used...

...is it possible to grant it what another SA have (impersonate a GCP SA)?

Yes, that's Workload Identity Federation through a Service Account as documented the README. The auth action will take care of the impersonation when it generates an access token, but it cannot configure downstream things to use impersonation.
In general, we recommend using Direct Workload Identity Federation instead of relying on impersonation, since impersonation introduces multiple layers of indirection.

Yes, I am aware of the security risk as mentioned in the previous comment, it is not managed by the user another step generates the mapping, but yes anyone can get access if they know what is being made underneath.
WIF seems the logical way to go.
Thank you all for your time and explanation.


Bump promscale helm chart to 13.0.0

What this PR does / why we need it
Update Promscale Helm chart to the latest version 13.0.0 and update relevant documentation
Which issue this PR fixes

fixes #509

Checklist

[x] Chart Version bumped
[x] CLA signed

Do not merge this until after #546


[1.8] Add validation for workload group (#29355)

Primary motivation is to allow testing of k8s 1.20 in 1.8

Add validation for workload group

Kubernetes 1.20 tests are currently broken, since our old invalid config
is now considered valid (see
https://github.com/kubernetes/kubernetes/pull/95423). In fixing this, I
realized we don't have any validation for WorkloadGroup! This adds
validation, by applying the same validation WorkloadEntry has to the
template of workload group. However, workload entry validation is pretty
much nil, so this change isn't very beneficial beyond getting tests
passing.

gen

fixes

Update

fmt

(cherry picked from commit 6e649ab3d40d195e9f314bc94500ee6b41456bd0)
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test unit-tests_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test unit-tests_istio_release-1.8

integ-security-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-security-k8s-tests_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test unit-tests_istio_release-1.8

integ-security-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-security-k8s-tests_istio_release-1.8

release-test_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test release-test_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test unit-tests_istio_release-1.8

integ-security-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-security-k8s-tests_istio_release-1.8

release-test_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test release-test_istio_release-1.8

integ-distroless-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-distroless-k8s-tests_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test unit-tests_istio_release-1.8

integ-security-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-security-k8s-tests_istio_release-1.8

release-test_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test release-test_istio_release-1.8

integ-distroless-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-distroless-k8s-tests_istio_release-1.8

integ-pilot-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-pilot-k8s-tests_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test unit-tests_istio_release-1.8

integ-security-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-security-k8s-tests_istio_release-1.8

release-test_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test release-test_istio_release-1.8

integ-distroless-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-distroless-k8s-tests_istio_release-1.8

integ-pilot-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-pilot-k8s-tests_istio_release-1.8

integ-telemetry-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-telemetry-k8s-tests_istio_release-1.8

integ-telemetry-mc-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-telemetry-mc-k8s-tests_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test unit-tests_istio_release-1.8

integ-security-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-security-k8s-tests_istio_release-1.8

release-test_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test release-test_istio_release-1.8

integ-distroless-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-distroless-k8s-tests_istio_release-1.8

integ-pilot-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-pilot-k8s-tests_istio_release-1.8

integ-telemetry-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-telemetry-k8s-tests_istio_release-1.8

integ-telemetry-mc-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-telemetry-mc-k8s-tests_istio_release-1.8

integ-ipv6-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-ipv6-k8s-tests_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test unit-tests_istio_release-1.8

integ-security-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-security-k8s-tests_istio_release-1.8

release-test_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test release-test_istio_release-1.8

integ-distroless-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-distroless-k8s-tests_istio_release-1.8

integ-pilot-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-pilot-k8s-tests_istio_release-1.8

integ-telemetry-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-telemetry-k8s-tests_istio_release-1.8

integ-telemetry-mc-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-telemetry-mc-k8s-tests_istio_release-1.8

integ-ipv6-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-ipv6-k8s-tests_istio_release-1.8

integ-operator-controller-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-operator-controller-tests_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test unit-tests_istio_release-1.8

integ-security-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-security-k8s-tests_istio_release-1.8

release-test_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test release-test_istio_release-1.8

integ-distroless-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-distroless-k8s-tests_istio_release-1.8

integ-pilot-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-pilot-k8s-tests_istio_release-1.8

integ-telemetry-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-telemetry-k8s-tests_istio_release-1.8

integ-telemetry-mc-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-telemetry-mc-k8s-tests_istio_release-1.8

integ-ipv6-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-ipv6-k8s-tests_istio_release-1.8

integ-operator-controller-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-operator-controller-tests_istio_release-1.8

integ-pilot-multicluster-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-pilot-multicluster-tests_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test unit-tests_istio_release-1.8

integ-security-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-security-k8s-tests_istio_release-1.8

release-test_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test release-test_istio_release-1.8

integ-distroless-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-distroless-k8s-tests_istio_release-1.8

integ-pilot-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-pilot-k8s-tests_istio_release-1.8

integ-telemetry-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-telemetry-k8s-tests_istio_release-1.8

integ-telemetry-mc-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-telemetry-mc-k8s-tests_istio_release-1.8

integ-ipv6-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-ipv6-k8s-tests_istio_release-1.8

integ-operator-controller-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-operator-controller-tests_istio_release-1.8

integ-pilot-multicluster-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-pilot-multicluster-tests_istio_release-1.8

integ-helm-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-helm-tests_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test unit-tests_istio_release-1.8

integ-security-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-security-k8s-tests_istio_release-1.8

release-test_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test release-test_istio_release-1.8

integ-distroless-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-distroless-k8s-tests_istio_release-1.8

integ-pilot-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-pilot-k8s-tests_istio_release-1.8

integ-telemetry-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-telemetry-k8s-tests_istio_release-1.8

integ-telemetry-mc-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-telemetry-mc-k8s-tests_istio_release-1.8

integ-ipv6-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-ipv6-k8s-tests_istio_release-1.8

integ-operator-controller-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-operator-controller-tests_istio_release-1.8

integ-pilot-multicluster-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-pilot-multicluster-tests_istio_release-1.8

integ-helm-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-helm-tests_istio_release-1.8

integ-security-multicluster-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-security-multicluster-tests_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test unit-tests_istio_release-1.8

integ-security-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-security-k8s-tests_istio_release-1.8

release-test_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test release-test_istio_release-1.8

integ-distroless-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-distroless-k8s-tests_istio_release-1.8

integ-pilot-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-pilot-k8s-tests_istio_release-1.8

integ-telemetry-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-telemetry-k8s-tests_istio_release-1.8

integ-telemetry-mc-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-telemetry-mc-k8s-tests_istio_release-1.8

integ-ipv6-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-ipv6-k8s-tests_istio_release-1.8

integ-operator-controller-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-operator-controller-tests_istio_release-1.8

integ-pilot-multicluster-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-pilot-multicluster-tests_istio_release-1.8

integ-helm-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-helm-tests_istio_release-1.8

integ-security-multicluster-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-security-multicluster-tests_istio_release-1.8

integ-multicluster-k8s-tests_istio_release-1.8
4c6884307168cccc3035277bd7fae980aceaf9fc
link
/test integ-multicluster-k8s-tests_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


[NWC frontend] update disconnect verbiage

#199  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @shreyav and the rest of your teammates on  Graphite


Fix typo in<EMAIL_ADDRESS>

'matter how' is repeated in 'Observing a Store’s values'

Hey @Qusea, thank you so much for the help! I truly appreciate the effort, but I believe you've modified the wrong file to make this change.
The file you updated is one of the files Apple's docc processor automatically generates, if we fix it here then the problem will re-emerge next time the documentation is regenerated. Instead the right file to update is in the Boutique/Sources/Boutique/Documentation.docc/Articles folder, the The @Stored Family Of Property Wrappers.md located in that folder.
Would it be too much trouble to ask you to update the pull request to revert this change and update that file instead? Then I'll be able to re-run the job to regenerate the documentation.
Thank you so much!

No worries, I'll get right on it

I tried to revert the change, but I'm not sure if it worked. I did update the correct file though.

That looks great, thanks again!


[Question]: Gemini Blocking Answer Generation

What is your question?
I have successfully installed and tested fabric.  I am trying to run the following command to extract wisdom from a youtube podcast.
fabric -y "https://youtube.com/watch?v=ajneRM-ET1Q" | fabric --stream -p extract_wisdom
This command executes perfectly, the youtube transcript is pulled fine, and the stream is started.  However at random points during the stream (different every run), the full output will be blocked with the following message ...

blocked: candidate: FinishReasonSafety

I asked Gemini personally what this nonsense was all about .. to which it replied

You're getting the "blocked: candidate: FinishReasonSafety" error when accessing me through an API because the system has identified a potential safety risk in your request. This is a common safety measure implemented to prevent harmful or inappropriate content from being generated.

Is this a Gemini preventing the answer issue?  Everything seems to be working fine with fabric.

That exact command is working for other youtube videos ... could this be because of the content of the video that Gemini is preventing the answer from being generated?

Followup question ... are other models less prone to censorship?  Working on getting other free versions up and running now.

btw. you could simplify the call
fabric -y "https://youtube.com/watch?v=ajneRM-ET1Q" --stream -p extract_wisdom

fabric -y "https://youtube.com/watch?v=ajneRM-ET1Q" --stream -p extract_wisdom
This one prints the whole youtube transcript for me tho

And then nothing happening?

Ya the output is partially streamed then completely stopped with the error message below ...

blocked: candidate: FinishReasonSafety

I think it is because of the content of the video. We can't do anything here.


Improve some docstrings. Accepts major flake8 checks of api base-code.

Some minor renaming of variables within functions.
Major additions of doc strings to base api code.
flake8 comparability corrections. A few violating lines to change later as functionality improves.

[x] Tests added / passed
[x] Associated doc strings if new function
[x] Passes flake8

Variables with net in name changed to use model keyword instead. This naming convention is intended to make documentation write up easier.


"Receive channel has not been made available" when I get request data at global exception

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the FastAPI documentation, with the integrated search.
[X] I already searched in Google "How to X in FastAPI" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to FastAPI but to Pydantic.
[X] I already checked if it is not related to FastAPI but to Swagger UI.
[X] I already checked if it is not related to FastAPI but to ReDoc.

Commit to Help

[X] I commit to help with one of those options 👆

Example Code
@app.exception_handler(Exception)
async def unexpected_exception_error(request: Request, exc: Exception):
    body = await request.body()
    return JSONResponse(
        status_code=status.HTTP_200_OK,
        content=jsonable_encoder({
            "code": 110,
            "request_data": body,
            "msg": str(exc)
        })
    )

Description
Hi guys~I wanna catch global exceptions in my app and return the body of request. But now when I write this code above, I got an error:
RuntimeError: Receive channel has not been made available
And I checked the error, because request object in site-packages\starlette\middleware\errors.py doesn't have receive property.
Can you help me ? I have created middleware and diy my Exception, But I can't get exception info any more.(I can get request body)
Operating System
Windows
Operating System Details
No response
FastAPI Version
0.63.0
Python Version
3.9.5
Additional Context
No response

Maybe this issue can help you.

Maybe this issue can help you.

Thanks~ I have solved it by middleware.😂
pity = FastAPI()

async def set_body(request: Request, body: bytes):
    async def receive() -> Message:
        return {"type": "http.request", "body": body}

    request._receive = receive

async def get_body(request: Request) -> bytes:
    body = await request.body()
    await set_body(request, body)
    return body

@pity.middleware("http")
async def errors_handling(request: Request, call_next):
    body = await request.body()
    try:
        await set_body(request, await request.body())
        return await call_next(request)
    except Exception as exc:
        return JSONResponse(
            status_code=status.HTTP_200_OK,
            content=jsonable_encoder({
                "code": 110,
                "msg": str(exc),
                "request_data": body,
            })
        )

Nice workaround, but how do you use get_body?


Cannot set RGB observation shape

I would like to manually set it from my own script rather than by using a YAML file.
I try
        env = iGibsonEnv(config_file=config_file, mode='headless')

        config = parse_config(config_file)
        config['max_step'] = horizon
        config['image_width'] = w
        config['image_height'] = h

        env.config = config
        env.simulator.reload()
        env.load()

max_step is set correctly, but image_width and image_height are not.
Strangely, env.observation_space.shape['rgb'].shape changes correctly to (w, h, 3), but whenever I call reset() or step() the observation returned is still of the original size.

Once env = iGibsonEnv(config_file=config_file, mode='headless') is called, the image size will already be set. Is there a particular reason why you don't want to set the image width and height in the YAML file?

To have the same structure of other environments. I can do the same with Habitat, DM control, Mujoco, ... So for instance if I need to I can use the same network (same input size) on all environments. It would be more convenient to do it from my python code rather than having to edit the YAML all the time, but it is not crucial. Is there a way to edit the config read by the YAML file before passing its parameter to the simulator?
At the moment I can only pass the path to the YAML to the simulator (not the config itself).
Thanks for your help!

I think you can actually pass the config itself, rather than the config file path. Could you try it out?
Ref: https://github.com/StanfordVL/iGibson/blob/5f8d253694b23b41c53959774203ba5787578b74/igibson/utils/utils.py#L17-L37


Slider Scroll

Hello
Thank for the great slider
I added the slider and all ok but not scrolling like the rest of the page , sort of fixed at the top of the screen like top bar

Then put it in a ScrollView.


TypeScript Do's and Don'ts

Adhere to the TypeScript recommendations published at Do's and Don'ts.
TODO:

[x] Don’t ever use the types Number, String, Boolean, or Object. These types refer to non-primitive boxed objects that are almost never used appropriately in JavaScript code.

[x] Instead of Object, use the non-primitive object type (added in TypeScript 2.2).

[X] Identify other rules being broken and correct them.

The pull request #26 implements a more strict type checking approach related to primitive types.
As a improvement, a more strict type checking for handlers and call backs functions is added as a TODO item for a future release.


*: fix build with panic engines

Signed-off-by: tabokie<EMAIL_ADDRESS>What is changed and how it works?
Issue Number: Ref #13131
What's Changed:
Make it build with panic engines:
cargo test --package tikv --features test-engines-panic --no-default-features
None

Related changes
Check List
Tests

Unit test

Release note
None

/cc @BornChanger @SpadeA-Tang

/run-test

Would you mind telling me what's the purpose or benefit of build with panic engines here?

@SpadeA-Tang We don't actually use panic engines, but building against it makes sure the code can work with arbitrary engines that adhere to engine traits. For the purpose of engine traits, please read the documentation in "components/engine_traits".

@BornChanger I'll add a new clippy pipeline later.

/merge

/run-test retry=5

/run-test retry=5


Request for SCIPgetNIntVars() and SCIPgetNBinVars() functions

Is it possible to add these two SCIP functions existing in C-API (SCIPgetNIntVars() and SCIPgetNBinVars()) as in the following documentation https://www.scipopt.org/doc/html/group__GlobalProblemMethods.php  also into the PySCIPOpt if it is not too complicated?
Thanks in advance.

it is and it shouldn't be complicated. You can do it yourself and open a PR: https://github.com/SCIP-Interfaces/PySCIPOpt#extending-the-interface
Examples: https://github.com/SCIP-Interfaces/PySCIPOpt/pull/388/files
https://github.com/SCIP-Interfaces/PySCIPOpt/pull/410/files


Increase interface frequency to 500 Hz for iRonCub experiments

cc @GiulioRomualdi @HosameldinMohamed @isorrentino @antonellopaolino @DanielePucci @traversaro

I have noted two things:

there is a huge number of  deprecated - unused files. See e.g.
https://github.com/ami-iit/robots-configuration/tree/devel_iCubGenova04_higherFreq/iRonCub-Mk1/estimators
https://github.com/ami-iit/robots-configuration/tree/devel_iCubGenova04_higherFreq/iRonCub-Mk1/wrappers/inertials (deprecated files)

the waist-IMU interface is not very clear. we don't us the wrapper because it is not called in iRonCub_wbd_noFeetFTs.xml. Instead we open a port directly from  https://github.com/ami-iit/robots-configuration/blob/devel_iCubGenova04_higherFreq/iRonCub-Mk1/hardware/inertials/waist-inertial.xml. I've added here the period https://github.com/ami-iit/robots-configuration/blob/devel_iCubGenova04_higherFreq/iRonCub-Mk1/hardware/inertials/waist-inertial.xml#L7as per YARP documentation https://www.yarp.it//git-master/classServerInertial.html#details

there was a reference to a deprecated file in iRonCub_wbd_noFeetFTs.xml, see  https://github.com/ami-iit/robots-configuration/pull/16/files#diff-0d2b3ba6a3a68c4f07304938f668db371cc19b50cdae7cd15328fe387c1193dcL47

decrease this parameter https://github.com/ami-iit/robots-configuration/blob/devel_iCubGenova04_higherFreq/iCubGenova09/hardware/electronics/left_arm-eb1-j0_1-eln.xml#L32
to set the frequency at which the debugger verifies if the packages are not processed in time by the icub-head pc

I think we can proceed with this PR now @gabrielenava!

Super cool