Serve_hostnames soak test gets unexpected errors

Running the serve_hostnames soak test on a 100 node cluster with 10 pods per node (i.e. a total of 1,000 pods) with at most 500 queries in flight at a time and an average of 10 queries per node per iteration has started to give an unexpected error (see below).
The expected response is the name of the pod that responds e.g. serve-hostname-34-9. However, quite often, the response is like:
I0413 22:29:11.378919   27358 serve_hostnames.go:294] Got response from {
  "kind": "Status",
  "apiVersion": "v1beta3",
  "metadata": {},
  "status": "Failure",
  "message": "dial tcp <IP_ADDRESS>:9376: no route to host",
  "code": 500
}

In the API server logs I notice:
I0413 22:31:46.938667    4456 handlers.go:138] GET /api/v1beta3/proxy/namespaces/serve-hostnames-9163/services/serv
e-hostnames: (33.195606ms) 0 [[serve_hostnames/v0.14.1 (linux/amd64) kubernetes/unknown] <IP_ADDRESS>:49972]
        E0413 22:31:46.966566    4456 errors.go:66] apiserver received an error that is not an api.Status: dial tcp
 <IP_ADDRESS>:9376: no route to host
        I0413 22:31:46.966762    4456 handlers.go:138] GET /api/v1beta3/proxy/namespaces/serve-hostnames-9163/servi
ces/serve-hostnames: (3.036067672s) 500
        goroutine 3147427 [running]:
        github.com/GoogleCloudPlatform/kubernetes/pkg/httplog.(*respLogger).WriteHeader(0xc20e391860, 0x1f4)
                /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudP
latform/kubernetes/pkg/httplog/log.go:188 +0x9a
        github.com/GoogleCloudPlatform/kubernetes/pkg/apiserver.writeJSON(0x1f4, 0x7fb715f405f0, 0xc20801d5e0, 0x7f
b715f407b8, 0xc211327400, 0x7fb715d95880, 0xc20e391860)
                /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudP
latform/kubernetes/pkg/apiserver/apiserver.go:249 +0x232
        github.com/GoogleCloudPlatform/kubernetes/pkg/apiserver.(*ProxyHandler).tryUpgrade(0xc208584480, 0x7fb715d9
5880, 0xc20e391860, 0xc22116d1e0, 0xc210af00d0, 0xc21e9881c0, 0x0, 0x0, 0x0)
                /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudP
latform/kubernetes/pkg/apiserver/proxy.go:229 +0x18e
        github.com/GoogleCloudPlatform/kubernetes/pkg/apiserver.(*ProxyHandler).ServeHTTP(0xc208584480, 0x7fb715d95
880, 0xc20e391860, 0xc22116d1e0)
                /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudP
latform/kubernetes/pkg/apiserver/proxy.go:190 +0x1605
        github.com/GoogleCloudPlatform/kubernetes/pkg/apiserver.func·002(0xc213ad6630, 0xc2089b14a0)
                /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudP
latform/kubernetes/pkg/apiserver/api_installer.go:706 +0x60
        github.com/emicklei/go-restful.func·005(0xc213ad6630, 0xc2089b14a0)
                /go/src/github.com/GoogleCloudPlatform/kubernetes/Godeps/_workspace/src/github.com/emicklei/go-rest
ful/container.go:214 +0x41
        github.com/emicklei/go-restful.(*FilterChain).ProcessFilter(0xc213ad6870, 0xc213ad6630, 0xc2089b14a0)
                /go/src/github.com/GoogleCloudPlatform/kubernetes/Godeps/_workspace/src/github.com/emicklei/go-rest
ful/filter.go:21 +0xa2
        github.com/GoogleCloudPlatform/kubernetes/pkg/apiserver.func·003(0xc213ad6630, 0xc2089b14a0, 0xc213ad6870)
                /go/src/github.com/GoogleCloudPlatf [[serve_hostnames/v0.14.1 (linux/amd64) kubernetes/unknown] 127
.0.0.1:49786]
I0413 22:31:47.023973    4456 handlers.go:138] GET /api/v1beta3/services: (3.420608ms) 200 [[kube-proxy/v0.14.1 (li
nux/amd64) kubernetes/1be6847] <IP_ADDRESS>:33033]

This is some of the log output of the soak test.
...
I0413 22:29:11.145102   27358 serve_hostnames.go:278] Proxy call in namespace serve-hostnames-9163 took 1m38.200217826s
I0413 22:29:11.145141   27358 serve_hostnames.go:294] Got response from serve-hostname-34-9
I0413 22:29:11.378839   27358 serve_hostnames.go:278] Proxy call in namespace serve-hostnames-9163 took 1m41.234674015s
I0413 22:29:11.378919   27358 serve_hostnames.go:294] Got response from {
  "kind": "Status",
  "apiVersion": "v1beta3",
  "metadata": {},
  "status": "Failure",
  "message": "dial tcp <IP_ADDRESS>:9376: no route to host",
  "code": 500
}
I0413 22:29:11.548075   27358 serve_hostnames.go:278] Proxy call in namespace serve-hostnames-9163 took 1m38.202100144s
I0413 22:29:11.548119   27358 serve_hostnames.go:294] Got response from serve-hostname-87-6
I0413 22:29:11.741882   27358 serve_hostnames.go:278] Proxy call in namespace serve-hostnames-9163 took 1m41.398092402s
I0413 22:29:11.741929   27358 serve_hostnames.go:294] Got response from {
  "kind": "Status",
  "apiVersion": "v1beta3",
  "metadata": {},
  "status": "Failure",
  "message": "dial tcp <IP_ADDRESS>:9376: no route to host",
  "code": 500
}
I0413 22:29:11.943367   27358 serve_hostnames.go:278] Proxy call in namespace serve-hostnames-9163 took 1m38.201145191s
I0413 22:29:11.943428   27358 serve_hostnames.go:294] Got response from serve-hostname-67-5
I0413 22:29:12.345609   27358 serve_hostnames.go:278] Proxy call in namespace serve-hostnames-9163 took 1m38.40038972s
I0413 22:29:12.345660   27358 serve_hostnames.go:294] Got response from serve-hostname-89-5
I0413 22:29:12.752724   27358 serve_hostnames.go:278] Proxy call in namespace serve-hostnames-9163 took 1m41.603265662s
I0413 22:29:12.752771   27358 serve_hostnames.go:294] Got response from {
  "kind": "Status",
  "apiVersion": "v1beta3",
  "metadata": {},
  "status": "Failure",
  "message": "dial tcp <IP_ADDRESS>:9376: no route to host",
  "code": 500
}
I0413 22:29:12.783879   27358 serve_hostnames.go:278] Proxy call in namespace serve-hostnames-9163 took 1m38.238766373s
I0413 22:29:12.783919   27358 serve_hostnames.go:294] Got response from serve-hostname-58-6
I0413 22:29:13.143044   27358 serve_hostnames.go:278] Proxy call in namespace serve-hostnames-9163 took 1m41.598008406s
I0413 22:29:13.143102   27358 serve_hostnames.go:294] Got response from {
  "kind": "Status",
  "apiVersion": "v1beta3",
  "metadata": {},
  "status": "Failure",
  "message": "dial tcp <IP_ADDRESS>:9376: no route to host",
  "code": 500
}
I0413 22:29:13.145557   27358 serve_hostnames.go:278] Proxy call in namespace serve-hostnames-9163 took 1m38.392609574s
I0413 22:29:13.145599   27358 serve_hostnames.go:294] Got response from serve-hostname-91-7
I0413 22:29:13.539806   27358 serve_hostnames.go:278] Proxy call in namespace serve-hostnames-9163 took 1m41.396829148s
I0413 22:29:13.539872   27358 serve_hostnames.go:294] Got response from {
  "kind": "Status",
  "apiVersion": "v1beta3",
  "metadata": {},
  "status": "Failure",
  "message": "dial tcp <IP_ADDRESS>:9376: no route to host",
  "code": 500
}
I0413 22:29:13.742147   27358 serve_hostnames.go:278] Proxy call in namespace serve-hostnames-9163 took 1m41.396210773s
I0413 22:29:13.742187   27358 serve_hostnames.go:294] Got response from {
  "kind": "Status",
  "apiVersion": "v1beta3",
  "metadata": {},
  "status": "Failure",
  "message": "dial tcp <IP_ADDRESS>:9376: no route to host",
  "code": 500
}
I0413 22:29:13.743846   27358 serve_hostnames.go:278] Proxy call in namespace serve-hostnames-9163 took 1m38.200853638s
I0413 22:29:13.743886   27358 serve_hostnames.go:294] Got response from serve-hostname-9-8
I0413 22:29:13.940004   27358 serve_hostnames.go:278] Proxy call in namespace serve-hostnames-9163 took 1m41.143346238s
I0413 22:29:13.940047   27358 serve_hostnames.go:294] Got response from {
  "kind": "Status",
  "apiVersion": "v1beta3",
  "metadata": {},
  "status": "Failure",
  "message": "dial tcp <IP_ADDRESS>:9376: no route to host",
  "code": 500
}
I0413 22:29:13.944366   27358 serve_hostnames.go:278] Proxy call in namespace serve-hostnames-9163 took 1m38.198924719s
I0413 22:29:13.944402   27358 serve_hostnames.go:294] Got response from serve-hostname-54-0
I0413 22:29:14.340538   27358 serve_hostnames.go:278] Proxy call in namespace serve-hostnames-9163 took 1m41.182768701s
I0413 22:29:14.340606   27358 serve_hostnames.go:294] Got response from {
  "kind": "Status",
  "apiVersion": "v1beta3",
  "metadata": {},
  "status": "Failure",
  "message": "dial tcp <IP_ADDRESS>:9376: no route to host",
  "code": 500
}
I0413 22:29:14.544639   27358 serve_hostnames.go:278] Proxy call in namespace serve-hostnames-9163 took 1m37.400984389s
I0413 22:29:14.544724   27358 serve_hostnames.go:294] Got response from serve-hostname-6-9
I0413 22:29:14.738817   27358 serve_hostnames.go:278] Proxy call in namespace serve-hostnames-9163 took 1m41.193959196s
I0413 22:29:14.738879   27358 serve_hostnames.go:294] Got response from {
  "kind": "Status",
  "apiVersion": "v1beta3",
  "metadata": {},
  "status": "Failure",
  "message": "dial tcp <IP_ADDRESS>:9376: no route to host",
  "code": 500
}
I0413 22:29:14.947287   27358 serve_hostnames.go:278] Proxy call in namespace serve-hostnames-9163 took 1m37.394815129s
I0413 22:29:14.947324   27358 serve_hostnames.go:294] Got response from serve-hostname-47-8
I0413 22:29:15.140596   27358 serve_hostnames.go:278] Proxy call in namespace serve-hostnames-9163 took 1m41.396136063s
I0413 22:29:15.140659   27358 serve_hostnames.go:294] Got response from {
  "kind": "Status",
  "apiVersion": "v1beta3",
  "metadata": {},
  "status": "Failure",
  "message": "dial tcp <IP_ADDRESS>:9376: no route to host",
  "code": 500
}
I0413 22:29:15.575149   27358 serve_hostnames.go:278] Proxy call in namespace serve-hostnames-9163 took 1m41.234715445s
I0413 22:29:15.575220   27358 serve_hostnames.go:294] Got response from {
  "kind": "Status",
  "apiVersion": "v1beta3",
  "metadata": {},
  "status": "Failure",
  "message": "dial tcp <IP_ADDRESS>:9376: no route to host",
  "code": 500
}
I0413 22:29:15.745343   27358 serve_hostnames.go:278] Proxy call in namespace serve-hostnames-9163 took 1m37.404747185s
I0413 22:29:15.745400   27358 serve_hostnames.go:294] Got response from serve-hostname-98-1
I0413 22:29:15.939728   27358 serve_hostnames.go:278] Proxy call in namespace serve-hostnames-9163 took 1m41.197106141s
I0413 22:29:15.939775   27358 serve_hostnames.go:294] Got response from {
  "kind": "Status",
  "apiVersion": "v1beta3",
  "metadata": {},
  "status": "Failure",
  "message": "dial tcp <IP_ADDRESS>:9376: no route to host",
  "code": 500
}
I0413 22:29:15.945360   27358 serve_hostnames.go:278] Proxy call in namespace serve-hostnames-9163 took 1m37.600336108s
I0413 22:29:15.945412   27358 serve_hostnames.go:294] Got response from serve-hostname-19-9
I0413 22:29:16.344389   27358 serve_hostnames.go:278] Proxy call in namespace serve-hostnames-9163 took 1m41.399187951s
I0413 22:29:16.344440   27358 serve_hostnames.go:294] Got response from {
  "kind": "Status",
  "apiVersion": "v1beta3",
  "metadata": {},
  "status": "Failure",
  "message": "dial tcp <IP_ADDRESS>:9376: no route to host",
  "code": 500
}
I0413 22:29:16.542738   27358 serve_hostnames.go:278] Proxy call in namespace serve-hostnames-9163 took 1m41.399372698s
I0413 22:29:16.542793   27358 serve_hostnames.go:294] Got response from {
  "kind": "Status",
  "apiVersion": "v1beta3",
  "metadata": {},
  "status": "Failure",
  "message": "dial tcp <IP_ADDRESS>:9376: no route to host",
  "code": 500
}
I0413 22:29:16.546302   27358 serve_hostnames.go:278] Proxy call in namespace serve-hostnames-9163 took 1m37.606040704s
I0413 22:29:16.546360   27358 serve_hostnames.go:294] Got response from serve-hostname-65-3

@lavalamp @smarterclayton @thockin

I'm still wondering if any of the /var/log/kube-proxy.log (on the nodes) say anything about too many open files...

Selected highlights from a kube-proxy file.
I0413 17:57:31.093767    5611 proxier.go:224] New UDP connection from <IP_ADDRESS>:34387
E0413 17:57:31.101432    5611 proxier.go:252] Read failed: read udp <IP_ADDRESS>:53: connection refused
I0413 17:57:31.109520    5611 proxier.go:224] New UDP connection from <IP_ADDRESS>:34387
E0413 17:57:31.110242    5611 proxier.go:252] Read failed: read udp <IP_ADDRESS>:53: connection refused
I0413 17:57:36.104871    5611 proxier.go:224] New UDP connection from <IP_ADDRESS>:55952
I0413 17:57:36.107803    5611 proxier.go:224] New UDP connection from <IP_ADDRESS>:47891
E0413 17:57:36.108641    5611 proxier.go:252] Read failed: read udp <IP_ADDRESS>:53: connection refused
I0413 17:57:41.112728    5611 proxier.go:224] New UDP connection from <IP_ADDRESS>:53457
I0413 17:57:41.116018    5611 proxier.go:224] New UDP connection from <IP_ADDRESS>:55403
I0413 17:57:41.121214    5611 proxier.go:224] New UDP connection from <IP_ADDRESS>:36016
E0413 17:57:41.122088    5611 proxier.go:252] Read failed: read udp <IP_ADDRESS>:53: connection refused
I0413 17:57:46.127639    5611 proxier.go:224] New UDP connection from <IP_ADDRESS>:40239
E0413 17:57:46.128907    5611 proxier.go:252] Read failed: read udp <IP_ADDRESS>:53: connection refused
I0413 17:57:51.137371    5611 proxier.go:224] New UDP connection from <IP_ADDRESS>:55421
I0413 17:57:51.141066    5611 proxier.go:224] New UDP connection from <IP_ADDRESS>:59602
E0413 17:57:51.141995    5611 proxier.go:252] Read failed: read udp <IP_ADDRESS>:53: connection refused
I0413 17:57:56.143601    5611 proxier.go:224] New UDP connection from <IP_ADDRESS>:32890
I0413 17:57:56.156743    5611 proxier.go:224] New UDP connection from <IP_ADDRESS>:57419
E0413 17:57:56.158036    5611 proxier.go:252] Read failed: read udp <IP_ADDRESS>:53: connection refused
I0413 17:58:01.161317    5611 proxier.go:224] New UDP connection from <IP_ADDRESS>:53080
...
W0413 18:14:27.289100    5611 api.go:153] Got error status on WatchServices channel: &{TypeMeta:{Kind: APIVersion:}
 ListMeta:{SelfLink: ResourceVersion:} Status:Failure Message:401: The event in requested index is outdated and cle
ared (the requested history has been cleared [16752/14370]) [17751] Reason: Details:<nil> Code:0}
...
I0413 18:29:57.875916    5611 iowatcher.go:102] Unexpected EOF during watch stream event decoding: unexpected EOF
...

This error comes up through a syscall, so it's not clear which one...
On Mon, Apr 13, 2015 at 3:57 PM, Satnam Singh<EMAIL_ADDRESS>wrote:

Selected highlights from a kube-proxy file.
I0413 17:57:31.093767    5611 proxier.go:224] New UDP connection from <IP_ADDRESS>:34387
E0413 17:57:31.101432    5611 proxier.go:252] Read failed: read udp <IP_ADDRESS>:53: connection refused
I0413 17:57:31.109520    5611 proxier.go:224] New UDP connection from <IP_ADDRESS>:34387
E0413 17:57:31.110242    5611 proxier.go:252] Read failed: read udp <IP_ADDRESS>:53: connection refused
I0413 17:57:36.104871    5611 proxier.go:224] New UDP connection from <IP_ADDRESS>:55952
I0413 17:57:36.107803    5611 proxier.go:224] New UDP connection from <IP_ADDRESS>:47891
E0413 17:57:36.108641    5611 proxier.go:252] Read failed: read udp <IP_ADDRESS>:53: connection refused
I0413 17:57:41.112728    5611 proxier.go:224] New UDP connection from <IP_ADDRESS>:53457
I0413 17:57:41.116018    5611 proxier.go:224] New UDP connection from <IP_ADDRESS>:55403
I0413 17:57:41.121214    5611 proxier.go:224] New UDP connection from <IP_ADDRESS>:36016
E0413 17:57:41.122088    5611 proxier.go:252] Read failed: read udp <IP_ADDRESS>:53: connection refused
I0413 17:57:46.127639    5611 proxier.go:224] New UDP connection from <IP_ADDRESS>:40239
E0413 17:57:46.128907    5611 proxier.go:252] Read failed: read udp <IP_ADDRESS>:53: connection refused
I0413 17:57:51.137371    5611 proxier.go:224] New UDP connection from <IP_ADDRESS>:55421
I0413 17:57:51.141066    5611 proxier.go:224] New UDP connection from <IP_ADDRESS>:59602
E0413 17:57:51.141995    5611 proxier.go:252] Read failed: read udp <IP_ADDRESS>:53: connection refused
I0413 17:57:56.143601    5611 proxier.go:224] New UDP connection from <IP_ADDRESS>:32890
I0413 17:57:56.156743    5611 proxier.go:224] New UDP connection from <IP_ADDRESS>:57419
E0413 17:57:56.158036    5611 proxier.go:252] Read failed: read udp <IP_ADDRESS>:53: connection refused
I0413 17:58:01.161317    5611 proxier.go:224] New UDP connection from <IP_ADDRESS>:53080
...
W0413 18:14:27.289100    5611 api.go:153] Got error status on WatchServices channel: &{TypeMeta:{Kind: APIVersion:}
ListMeta:{SelfLink: ResourceVersion:} Status:Failure Message:401: The event in requested index is outdated and cle
ared (the requested history has been cleared [16752/14370]) [17751] Reason: Details: Code:0}
...
I0413 18:29:57.875916    5611 iowatcher.go:102] Unexpected EOF during watch stream event decoding: unexpected EOF
...
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/6787#issuecomment-92525954
.


pack error on Windows 10 17746

🐛 Bug description
I just try the hello world on my computer.
Project structure is

wasm-pack init is success

but wasm-pack pack .  is faild

wasm-pack.log
Aug 31 10:21:31.981 INFO Running pack command...
Aug 31 10:21:31.982 INFO Path: Some(".")
Aug 31 10:21:31.982 INFO Packing up the npm package...
Aug 31 10:21:31.982 ERRO 系统找不到指定的文件。 (os error 2)

🤔 Expected Behavior
No error occurred
👟 Steps to reproduce

create new hello world project
wasm-pack init
wasm-pack pack .

🌍 Your environment
os: windows 10 x64 17746.1000
wasm-pack version: 0.4.2
rustc version: 1.30.0-nightly (02cb8f2a4 2018-08-29)

Thanks for the bug report!

could you provide your local npm meta info? I suspect that npm wasn't installed on your machine.

@WangZishi I suspect that npm wasn't installed on your machine, could you paste the npm meta info here?

@fitzgen
anyway, pack cmd invokes npm directly https://github.com/rustwasm/wasm-pack/blob/89be40df2f478a19b9fdd38dafdc7792967560f2/src/npm.rs#L10-L18
maybe better to add a binary exsit_or_not checking as you did in test PR here?

That sounds good to me! We should probably always do that, just to get good error messages to users

@csmoe

ah @WangZishi what happens when you run wasm-pack pack (without the dot?). the dot shouldn't cause an issue but it may be...

hrm. thanks so much for the response and sorry this is taking so long to figure out. @steveklabnik do you think you could try this locally?

I get
C:\Users\steve> wasm-pack pack
Unable to find the pkg directory at path ".", or in a child directory of "."

this bug can be reproduced with Chinese-ver Windows7 in my virtualbox, comparing to stevelabnik's comment, I suspect that system locale is the one to be blamed.

this might help: https://github.com/rust-lang/rust/issues/42791


Add target with delegation

Fixes #32

Adding a target only modifies a single metadata so making it a "edit" sub
command made sense... However, often user does not know which metadata
should be modified: this is especially the case with succinct
delegations.
Make add-target a top level action instead of a edit subaction:

role can still be optionally specified but it is a starting point for the search
delegation tree is followed from the starting role until the first leaf role (that does not delegate further) is found
command now also outputs which role it inserted the target file into

This means add-target is now a simple repository wide command which seems quite logical: user does not need to know the details, they just want to add a target file to the repository.
There is a edit()-refactor here that makes the edit-contextmanager handle AbortEdit silently: the users of edit() can raise AbortEdit to signal they want to exit the contextmanager without saving the edited metadata. This is a bit undiscoverable and not immediately obvious but works quite nicely in both snapshot and add-target in my opinion.

The obvious review comment here is that add-target and remove-target now look different... I have a commit for the latter as well, but would rather put that in another PR (it's not completely trivial as it makes sense to add a delegation search there as well).

@MVrachev care to take a look at this one?

Yes, I will.
I will try to find time these days.


MangaSee Filtering

Request to add filters for source mangasee
Filter like : recently updated, recommended, etc....could be extracted from homepage of the website
Thankyou

The reason it doesn't do this already is because it uses the json extracted from the search page (which contains every manga) and caches it to avoid repeated requests. Filtering the json could be added without scraping.


Cross-Origin Resource Sharing problem

Hello I commented  below writing at https://github.com/balderdashy/sails/issues/1206#issuecomment-48582352
Please check it!
thank you
Hello @mikermcneil
I launched server (version = v0.10.0-rc8 )
I have same error likes below.
(As casoetan says, I can emit this error after browser to localhost:1337)
error: Could not load session for socket #qjtt-C4ZSeotyh9Kexut
error: The socket's cookie could not be parsed into a sessionID.
error: Unless you're overriding the authorization function, make sure you pass in a valid sails.sidcookie
error: (or omit the cookie altogether to have a new session created and an encrypted cookie sent in the response header to your socket.io upgrade request)
error: TypeError: Cannot call method 'indexOf' of undefined
at exports.parseSignedCookie (/usr/src/nodejs/lib/node_modules/sails/node_modules/express/node_modules/connect/lib/utils.js:199:19)
at Object.Session.fromSocket (/usr/src/nodejs/lib/node_modules/sails/lib/hooks/session/index.js:339:38)
at SocketNamespace.onConnect (/usr/src/nodejs/lib/node_modules/sails/lib/hooks/sockets/lib/connection.js:45:18)
at SocketNamespace.emit as $emit
at connect (/usr/src/nodejs/lib/node_modules/sails/node_modules/socket.io/lib/namespace.js:292:10)
at /usr/src/nodejs/lib/node_modules/sails/node_modules/socket.io/lib/namespace.js:308:13
at SocketNamespace.authorize (/usr/src/nodejs/lib/node_modules/sails/node_modules/socket.io/lib/namespace.js:252:5)
at SocketNamespace.handlePacket (/usr/src/nodejs/lib/node_modules/sails/node_modules/socket.io/lib/namespace.js:302:14)
at Manager.handleClient (/usr/src/nodejs/lib/node_modules/sails/node_modules/socket.io/lib/manager.js:721:32)
at Manager.handleUpgrade (/usr/src/nodejs/lib/node_modules/sails/node_modules/socket.io/lib/manager.js:641:8) [TypeError: Cannot call method 'indexOf' of undefined]
error: Could not load session for socket #qjtt-C4ZSeotyh9Kexut
error: The socket's cookie could not be parsed into a sessionID.
error: Unless you're overriding the authorization function, make sure you pass in a valid sails.sidcookie
error: (or omit the cookie altogether to have a new session created and an encrypted cookie sent in the response header to your socket.io upgrade request)
error: TypeError: Cannot call method 'indexOf' of undefined
at exports.parseSignedCookie (/usr/src/nodejs/lib/node_modules/sails/node_modules/express/node_modules/connect/lib/utils.js:199:19)
at Object.Session.fromSocket (/usr/src/nodejs/lib/node_modules/sails/lib/hooks/session/index.js:339:38)
at interpretSocketReq (/usr/src/nodejs/lib/node_modules/sails/lib/hooks/sockets/lib/interpreter/interpret.js:542:19)
at Socket. (/usr/src/nodejs/lib/node_modules/sails/lib/hooks/sockets/lib/connection.js:95:5)
at Socket.emit as $emit
at SocketNamespace.handlePacket (/usr/src/nodejs/lib/node_modules/sails/node_modules/socket.io/lib/namespace.js:335:22)
at Manager.onClientMessage (/usr/src/nodejs/lib/node_modules/sails/node_modules/socket.io/lib/manager.js:518:38)
at WebSocket.Transport.onMessage (/usr/src/nodejs/lib/node_modules/sails/node_modules/socket.io/lib/transport.js:369:20)
at Parser. (/usr/src/nodejs/lib/node_modules/sails/node_modules/socket.io/lib/transports/websocket/hybi-16.js:39:10)
at Parser.emit (events.js:95:17) [TypeError: Cannot call method 'indexOf' of undefined]
I saw you say this error is fixed in sails beta version.
But it still exists.
Please comment!

@loicsaintroch @jyoungrok  Can you guys open this issue again? This hasn't been resolved.

Top, sorry for the delay.

It's a bit hard to comment on this without having more background.  If you don't have sockets and sessions pointed to a datastore like Redis, then this will absolutely happen whenever Sails is lowered / re-lifted while clients are connected, because sails.io.js automatically attempts to reconnect and either the socket, session or both are no longer accessible to the server.  Depending on your deployment scenario, your server could be cycling periodically (this would happen on a Heroku app scaled to a single dyno, for example), causing clients to become disconnected until they refresh their pages.

Without more info (and confirmation that this is still an issue in Sails v0.11.x), I'm closing this issue.  Happy to re-open if more info comes to light.

I have the same issue on sails v0.11. Trying to solve now.

NAVER - http://www.naver.com/
<EMAIL_ADDRESS>님께 보내신 메일 <Re: [sails] Cross-Origin Resource Sharing problem (#1952)> 이 다음과 같은 이유로 전송 실패했습니다.

받는 사람이 회원님의 메일을 수신차단 하였습니다.

I have the same problem when i make deploy on Heroku, I solved this by forcing transports for websocket:
http://stackoverflow.com/questions/32220349/sails-socket-io-websocket-blocked-how-to-fall-back/32260040#32260040


Bootstrap argocd installation with a helm chart

Summary
Argocd Autopilot users could benefit from optionally specifying a helm chart for ArgoCD installation rather than just the default installation.  For example, it would be nice to be able to control the bootstrap with things like initial RBAC configuration, controller replica count, or any other configuration available in the helm chart.
Proposal
The existing repo bootstrap should be able to install ArgoCD via a user-defined helm chart.
For example, I have a user-defined Values.yaml file with some configuration values for rbac.  I should be able to run something like argocd-autopilot repo bootstrap --helm-install=latest --values=Values.yaml
The --helm-install flag indicates that command should use install from the helm chart at either the latest or a specified version.
The --values flag is just a file location for any user defined values for the installation.

Hello @apresti12
This is currently under consideration/planning. I cannot commit to an ETA, but let's just say it is high up in the backlog...


Installing pyinterval on Windows with Python 3.6

Hi,
This might not be the right place for this question since it concerns pycrlibm. I asked the same question at https://github.com/taschini/pycrlibm/issues but there is more activity in this project so I am asking the same question here as well.
I tried installing pyinterval on Windows and Python 3.6. The complete output of the error I am getting is below.
(oe-3.6.2) C:\Users\ifisl\workspace>pip install pyinterval
Collecting pyinterval
  Using cached pyinterval-1.2.0.tar.gz
Collecting crlibm==1.*,>=1.0.3 (from pyinterval)
  Using cached crlibm-1.0.3.tar.gz
Requirement already satisfied: six>=1.10 in c:\users\ifisl\workspace\venvs\oe-3.
6.2\lib\site-packages (from pyinterval)
Installing collected packages: crlibm, pyinterval
  Running setup.py install for crlibm ... error
    Complete output from command c:\users\ifisl\workspace\venvs\oe-3.6.2\scripts\python.exe -u -c "import setuptools, tokenize;__file__='C:\\Users\\ifisl\\AppData\\Local\\Temp\\pip-build-24w2c8s7\\crlibm\\setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record C:\Users\ifisl\AppData\Local\Temp\pip-qajjsl7u-record\install-record.txt --single-version-externally-managed --compile --install-headers c:\users\ifisl\workspace\venvs\oe-3.6.2\include\site\python3.6\crlibm:
    running install
    running build
    running build_ext
    using msys2 compiler
    building 'crlibm' extension
    creating build
    creating build\temp.win-amd64-3.6
    creating build\temp.win-amd64-3.6\Release
    creating build\temp.win-amd64-3.6\Release\ext
    C:\msys64\mingw64\bin\gcc.exe -mdll -O2 -Wall -fno-strict-aliasing -fwrapv -DMS_WIN64 -Ibuild/crlibm/include -Ic:\users\ifisl\workspace\venvs\oe-3.6.2\include "-IC:\Program Files\Python362\include" "-IC:\Program Files\Python362\include" -c ext/crlibmmodule.c -o build\temp.win-amd64-3.6\Release\ext\crlibmmodule.o
    ext/crlibmmodule.c:7:10: fatal error: crlibm.h: No such file or directory
     #include "crlibm.h"
              ^~~~~~~~~~
    compilation terminated.
    invoking: ['make', 'msys2', 'PYTHON_DLL=c:\\users\\ifisl\\workspace\\venvs\\oe-3.6.2\\scripts\\python36.dll']
    error: [WinError 2] The system cannot find the file specified

    ----------------------------------------

I followed all instructions in http://stackoverflow.com/a/30071634 on installing/configuring MinGW-w64 under MSYS2 and am getting the error above. I tried to look for crlibm.h at http://lipforge.ens-lyon.fr/www/crlibm but that page does not exist any more.
Is there anything I can do to install pyinterval without pycrlibm? If not, how can I install pycrlibm on Windows with Python 3.6?
Thanks!
Igor

@jmmcd @ifisl have you fixed this issue?


Allow filtering of validators by top-level validator status

Right now, Lodestar does not support filtering response of getStateValidators by top-level validator statuses such as active as we only consider the more accurate sub statuses like active_ongoing, active_exiting and active_slashed.
As per beacon-api spec we should support active, pending, exited, and withdrawal (validators.yaml#L38).
Related code
https://github.com/ChainSafe/lodestar/blob/955f4569289d66e0a2ee171dfa7bd9984ce57ba7/packages/beacon-node/src/api/impl/beacon/state/utils.ts#L132

Hello!
I would like to contribute to this issue as part of Hacktoberfest. Could you please add the hacktoberfest label to the issue or repository so my contribution can count toward Hacktoberfest?
Thank you!


Run twindle-cli and share output below

Could everyone try to take the latest code and run twindle-cli. And please post your screenshots or any issues faced, or doubts :partying_face:
Here are couple instructions to get started,

Pull latest code
cd into twindle-cli
run npm install

then run the index.js file!!

Here is my output of a thread

Great @EYRAM565 next try to send to Kindle mobile app

okay.

@EYRAM565 can you please help @vasudeveloper001 in fixing his errors.

@vasu001 you have to node . -i then the tweet id -o instead, fetch any id at all no matter the date.

Done @EYRAM565

nice. can you try last months'?

Wait, let me check. Meanwhile, I recommend this 279 tweets long thread maintained since last 2 years for our use case scenario. We will figure out all the shortcomings with this thread.
https://twitter.com/ARanganathan72/status/924574125938503680

@vasudeveloper001 this is mind blowing thread. I suggest create a issue and we can collect these threads, it will be great for testing 😊

@vasudeveloper001 add
-p
At the end of your command and run

Worked this time.

Hello everyone, I am facing issue👇 Don't know how/what to fill in place of tweet Id. Do we need to get access of the twitter api access to see the result? If so, then I have yet to get my twitter api access.
@johnjacobkenny @EYRAM565 Do see & help me out in this.

Wait, let me check. Meanwhile, I recommend this 279 tweets long thread maintained since last 2 years for our use case scenario. We will figure out all the shortcomings with this thread.
https://twitter.com/ARanganathan72/status/924574125938503680

Does this run in current implementation

Hello everyone, I am facing issue👇 Don't know how/what to fill in place of tweet Id. Do we need to get access of the twitter api access to see the result? If so, then I have yet to get my twitter api access.
@johnjacobkenny @EYRAM565 Do see & help me out in this.

@Akshay2996 tweet id is the last set of numbers in the url when you open any tweet. But right now, yes you need to have the api key to be able to try it out

See My PDF file. Didn't expect the cli command to be simple & straight forward to use after getting twitter API access. Great work all around to the Twindle-cli Team & to everyone👏

I finally got the twitter api access!!
Here are my screenshots of twindle-cli:

I have some doubts as well.

How can I get my twitter api access?
What is that 'token'? How can I find?

@twindle-co/developer someone please help @RafaelBatman55

I have some doubts as well.

How can I get my twitter api access?
What is that 'token'? How can I find?

Applying for developer access wiki
Answering questions on Twitter access application
Please read these two wiki pages for getting access from Twitter.
To understand the Twitter API and how it works, read this: Developers documentation
If you still have questions after reading these, please message on discord board or on Twitter group someone will definitely help.

Thank you so much! I'll have a lot to study now!

This is the process step by step from the beginning.

First I copy the folder twindle-cli.

Then in a console typed npm install

Then node index.js -i<PHONE_NUMBER>039745026 and I got this message

I'm trying to solve this issue, as soon as I get it solve I will post the next step.

I have some doubts as well.

How can I get my twitter api access?
What is that 'token'? How can I find?

Applying for developer access wiki
Answering questions on Twitter access application
Please read these two wiki pages for getting access from Twitter.
To understand the Twitter API and how it works, read this: Developers documentation
If you still have questions after reading these, please message on discord board or on Twitter group someone will definitely help.

Thank you Mira!
One more question... If I don't misunderstood every member have to apply for developer access on twitter, right?

Currently, in order to run the cli the user needs to have the token

Currently, in order to run the cli the user needs to have the token

Thank you Kenny! I'm apply for dev-access it right now.


Overlapping content

Hi,
when i extent gridview column size to 7 than collapse some data, i dont know how to resolve?

Sorry for replying late. For your issue, I think the reason is that the GridView has not set background color.
The mechanism of the expand/split GridView is:

Get the drawing of the GridView, which will create a bitmap;
Split the bitmap into two part at the touch position;
Inject a new layout, which is a new GridView here, in the middle of the two bitmap;
Add the two bitmap and the middle layout to a new cover view, bring the cover view to front to cover the origin GridView;

By doing these steps, we create the expand/split effect.
The GridView's background color is transparent by default. So it would collapse at the bottom part.
The solution is set background color to the GridView.


Metaunit next links

Waiting on #2270
Makes the MetaUnit component use Next links.
It's going to be interesting to see when we get to cross referencing apps, how this might play out as it's a common lib.
https://github.com/wellcometrust/wellcomecollection.org/compare/complete-catalogue-jsx...metaunit_next_links?expand=1

@davidpmccormick updated with master so easier to read.

If you'd update the pre-existing Link to be a NextLink that'd be cool.

🏁


feat(aws-iot-s3): new construct implementation

Issue #, if available:
Description of changes:
New aws-iot-s3 solutions construct implementation
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 950bf82175e5721b315043717322b1221c3cf2a4
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 950bf82175e5721b315043717322b1221c3cf2a4
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 7a6cf09fa9c2aa1d37f4c9e44da1ef062052c45b
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 8bccbf48bcbc7764e549cc94cd2bc0e66b80b872
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: cb36649c47be07ff0efdd62f07fd37f86c7e2163
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 7a6cf09fa9c2aa1d37f4c9e44da1ef062052c45b
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 8bccbf48bcbc7764e549cc94cd2bc0e66b80b872
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: cb36649c47be07ff0efdd62f07fd37f86c7e2163
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 583471fa500794c7f53b8566a2391ba4fc373212
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 583471fa500794c7f53b8566a2391ba4fc373212
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: fe3313a296eee85750be25875af03aa1a72ee4ce
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: fe3313a296eee85750be25875af03aa1a72ee4ce
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 5d8ac6a60ec465a0a5b4207e06519137d9474a6c
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 5d8ac6a60ec465a0a5b4207e06519137d9474a6c
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 995cf8fee671d144f2304402eda705f915269802
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: f1cece2c5d2dfa8cd3667b24f18507709e2c7830
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: f1cece2c5d2dfa8cd3667b24f18507709e2c7830
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: b6891eba06ea91d312cc9360a7b103433a729e03
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: b6891eba06ea91d312cc9360a7b103433a729e03
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 7cb5a2aa42198d46709edaa96ac71850f03747cc
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 7cb5a2aa42198d46709edaa96ac71850f03747cc
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 80ccf45b6a915f62885052a41224c74e58e6207e
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 80ccf45b6a915f62885052a41224c74e58e6207e
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


New class of POB messages for validators

It appears that transcribers are daunted by all of the POB warning messages that are created for the benefit of validators.
It has been proposed that POB warning messages be placed in a category of their own.
Likely a size 8 .Would require a new class of messages; hence lots of donkey work where each message has to be looked at and a decision made as to which class to assign it and then a relay out of the pages to accommodate another class.
Geoff gives Priority Low then. I was hoping that it was just removal of some items from the existing report.
Afraid not. The system was built on 3 messages classes and an attempt to divide 1 into 2 after the fact is a kludge which would introduce maintainability issues for the next programmer. Hence one is far better off to say there are now 4 not 3 and a half

Summary
This is what I see as the situation:
There are three reports allowed.
Info: this is the least useful but there is a lot of information in it that is useful for specific situations such as new transcribers.
Warnings: This is essential for Validators
Errors: This is essential for Transcribers and Proofreaders as we cannot progress a transcription whilst it contains Errors.
In an ideal world we would have a fourth report which would be Essential Warnings. It would contain all the things that need to be looked at for quality purposes. It would not have the POB Warnings but would contain all the others. However this is not an ideal world.
The only solution that I can see is to expand the Errors report to contain these essential Warnings. This would then be similar, but not exactly the same, as a report from CSVCheck.
As Kirk idetifies this affects the download of a vld file and replacement in FC2. The current situation is that a downloaded vld file needs to be re-validated, which is a waste of time and effort as it has already been done once.
Geoff

In my opinion I agree with Geoff when he sums it up quite nicely as:
The only solution that I can see is to expand the Errors report to contain
these essential Warnings. This would then be similar, but not exactly the
same, as a report from CSVCheck.As Kirk idetifies this affects the download
of a vld file and replacement in FC2. The current situation is that a
downloaded vld file needs to be re-validated, which is a waste of time and
effort as it has already been done once.Geoff
Especially as it took 20 odd years to get it all online. It could  then
take as long again to redo them. Not an option as far as I can see.
Brenda
On Wed, 17 Feb 2021 at 11:03, geoffj-FUG<EMAIL_ADDRESS>wrote:

Summary
This is what I see as the situation:
There are three reports allowed.
Info: this is the least useful but there is a lot of information in it
that is useful for specific situations such as new transcribers.
Warnings: This is essential for Validators
Errors: This is essential for Transcribers and Proofreaders as we cannot
progress a transcription whilst it contains Errors.
In an ideal world we would have a fourth report which would be Essential
Warnings. It would contain all the things that need to be looked at for
quality purposes. It would not have the POB Warnings but would contain all
the others. However this is not an ideal world.

The only solution that I can see is to expand the Errors report to contain

these essential Warnings. This would then be similar, but not exactly the
same, as a report from CSVCheck.
As Kirk idetifies this affects the download of a vld file and replacement
in FC2. The current situation is that a downloaded vld file needs to be
re-validated, which is a waste of time and effort as it has already been
done once.
Geoff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/FreeUKGen/FreeCENMigration/issues/1147#issuecomment-780479178,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADIL3VRL6BRPAU5AWRZUZ3TS7OO67ANCNFSM4XW5ABWA
.

Brenda
It is not proposed to download every file. There is a need to download a vld file when we receive a query from a researcher and we need to amend the original transcription.
Geoff
From: Brenda<EMAIL_ADDRESS>Sent: Wednesday, February 17, 2021 10:04 PM
To: FreeUKGen/FreeCENMigration<EMAIL_ADDRESS>Cc: geoffj-FUG<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [FreeUKGen/FreeCENMigration] New class of POB messages for validators (#1147)
In my opinion I agree with Geoff when he sums it up quite nicely as:
The only solution that I can see is to expand the Errors report to contain
these essential Warnings. This would then be similar, but not exactly the
same, as a report from CSVCheck.As Kirk idetifies this affects the download
of a vld file and replacement in FC2. The current situation is that a
downloaded vld file needs to be re-validated, which is a waste of time and
effort as it has already been done once.Geoff
Especially as it took 20 odd years to get it all online. It could then
take as long again to redo them. Not an option as far as I can see.
Brenda
On Wed, 17 Feb 2021 at 11:03, geoffj-FUG<EMAIL_ADDRESS><EMAIL_ADDRESS>> wrote:

Summary
This is what I see as the situation:
There are three reports allowed.
Info: this is the least useful but there is a lot of information in it
that is useful for specific situations such as new transcribers.
Warnings: This is essential for Validators
Errors: This is essential for Transcribers and Proofreaders as we cannot
progress a transcription whilst it contains Errors.
In an ideal world we would have a fourth report which would be Essential
Warnings. It would contain all the things that need to be looked at for
quality purposes. It would not have the POB Warnings but would contain all
the others. However this is not an ideal world.

The only solution that I can see is to expand the Errors report to contain

these essential Warnings. This would then be similar, but not exactly the
same, as a report from CSVCheck.
As Kirk idetifies this affects the download of a vld file and replacement
in FC2. The current situation is that a downloaded vld file needs to be
re-validated, which is a waste of time and effort as it has already been
done once.
Geoff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/FreeUKGen/FreeCENMigration/issues/1147#issuecomment-780479178,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADIL3VRL6BRPAU5AWRZUZ3TS7OO67ANCNFSM4XW5ABWA
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/FreeUKGen/FreeCENMigration/issues/1147#issuecomment-780510971 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKCPIFPIPVUOWIOOLTDHQQTS7OWDLANCNFSM4XW5ABWA .  https://github.com/notifications/beacon/AKCPIFJI4MKQACF6EOJQ66LS7OWDLA5CNFSM4XW5ABWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOF2C2N6Y.gif

@geoffj-FUG Amount of effort to do as suggested is 90% of the effort required to add the new class

@geoffj-FUG
As I had to address the issue of the . in Rel or Dis fields in the processing of a traditional header; which is now deployed to test3 and permits with or without the . on those fields.
I decided to deal with this issue at the same time.
There are now four processing options

I have set the default to No POB Warnings and suggest this should be the standard option used by transcribers. Validators should use All Warnings to see the POB warnings as well as any others.
Running on test3

Tests well
This story can be closed
Geoff


fix(index): don't set to value (options)

ℹ  Describe the big picture of your changes here to communicate to the maintainers
why we should accept this pull request. If it fixes a bug or resolves a feature
request, be sure to link to that issue.

When passing to it truncates the output source map file path to just the path base name. By removing this value the paths are now correct.
The implementation of this logic is found here
Type

ℹ  What types of changes does your code introduce?

[x] Fix

SemVer

ℹ  What changes to the current semver range does your PR introduce?

[x] Bug (:label: Patch)

Issues

ℹ  What issue (if any) are closed by your PR?

None

Checklist

ℹ  You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. This is a reminder of what we are going to look for before merging your code.

[x] Lint and unit tests pass with my changes
[x] I have added tests that prove my fix is effective/works
[x] I have added necessary documentation (if appropriate)
[x] Any dependent changes are merged and published in downstream modules

Coverage remained the same at 87.975% when pulling aa52605c3b67d6001683f62ce9ebfd4cbae0278c on camshaft:patch-1 into 0a643de66a251e0539d0f385a87cddd8ec853ebc on postcss:master.

Without this fix:

With this fix:

Released in v2.1.1  🎉  Thx


Create unified set of plugin operations.

This makes asserting on specific event ordering much easier. Previously, the only thing we asserted on was that the commands all ran in the right order, and the logs were all in the right order, and the prompts were all in the right order. Now we will be able to assert that the commands, logs, and prompts are in the right order in relationship to each other.

CI is having issues with nodejs.org server timeouts, CI push jobs all finished though so I think we are fine.


Repository description field in database should allow more than 256 chars length

Gogs version (or commit ref):

<IP_ADDRESS>8

Git version:

2.17

Operating system:

Ubuntu Linux 18.04 x86 (LXC)

Database (use [x]):

[ ] PostgreSQL
[x] MySQL 5.7
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gogs.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Log gist (usually found in log/gogs.log):
2018/04/21 19:34:50 [ERROR] [...g/context/context.go:171 ServerError()] UpdateRepository: updateRepository: update: Error 1406: Data too long for column 'description' at row 1

Description
If you fill description field in edit repository form with UTF-8 long string (is russian as example) and try to save it - gogs fails with 500 error.
Suggestion:

do a migration that changes fields in DB like repository.description to TEXT type. Where it apropriate.
limit available length of characters in textarea form inputs (via javascript).

A new PR: #5219
Work in progress.


Git integration being removed in ADF when using PublishADFTask

We have an ADF with Git Integration enabled and would like to publish the changes in ADF every time a PR is merged to our Dev branch.
The publishing seems to work, but after the deployment stage, the Git Integration is gone.
Is this supposed to happen? We have a separate deployment POC using Git Enterprise and it does not happen in there.
This is the task we configured:

When I re-enable Git Integration, if I choose to save the current changes to a branch, it generates some differences with what we have in our repo:

Are those differences somehow making ADF to disable the Git Integration?

AFAIK these were optional, but sometimes are being added to the code by ADF backend when saving objects. Definitely not a culprit of switching off GIT integration.

Performing additional tests I'm having a scenario where if I add Global Parameters to the ADF instance, the publish removes the Git Integration and if I remove the Global Parameters, the publish does not remove the Git Integration.

Hopefully I will be able to check that this week.


wrong with tf.norm, it will produce nan

I use version 1.0.0 in server, in my code, the result will be nan if i use :
result = tf.square(tf.norm(penalize))

but if i change it to be:
result = tf.reduce_sum(tf.square(penalize))

everything will be ok, and result is some float between 0 and 1.

I was unable to reproduce the problem with v1.2.1. Could you please post a code snippet to reproduce the problem. BTW I would suggest that you use tf.reduce_sum(...) over tf.square(...) as it will likely be more efficient to compute.

my related code snipper is:
# softmax
# A.shape is [2, t]
A = tf.nn.softmax(A)

penalize = tf.matmul(A, tf.transpose(A)) - tf.diag(tf.ones(2))
penalize = tf.reduce_sum(tf.square(penalize))

# penalize = tf.square(tf.norm(penalize))

and what's the implement of your suggestion about use tf.reduce_sum(...) over tf.square(...)? Thx.

I tried this code snippet and it works perfectly fine on my machine with tf v1.2.1. Let me know if I'm missing something.
import tensorflow as tf

A = tf.constant([[0.1, 0.2, 0.5], [0.3, 0.1, 0.2]])
A = tf.nn.softmax(A)

penalize = tf.matmul(A, tf.transpose(A)) - tf.diag(tf.ones(2))
result1 = tf.reduce_sum(tf.square(penalize))
result2 = tf.square(tf.norm(penalize))

with tf.Session() as sess:
    print(sess.run(result1))
    print(sess.run(result2))

When I said that you should prefer tf.reduce_sum(...) over tf.square(...), I meant that you should prefer result = tf.reduce_sum(tf.square(penalize)) over result = tf.square(tf.norm(penalize))

this simple program works fine in my server, too. but my original program is quite big and it takes time to run and print related logs. So I hope I can find what exactly happens with the numbers some day ...

Thanks for helping our friend @lakshayg.


Add "GUI development with Rust and GTK 4"

Thanks. I'll look at this later this week.
On Sat, 28 Aug 2021, 19:05 Hofer-Julian, @.***> wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/lborb/book/pull/21
Commit Summary

Add "GUI development with Rust and GTK 4"

File Changes

M src/applications.md
https://github.com/lborb/book/pull/21/files#diff-50ab2ba7127b880f870a04d2300984d012603716d421fbe0a832f45870d2221f
(1)

Patch Links:

https://github.com/lborb/book/pull/21.patch
https://github.com/lborb/book/pull/21.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/lborb/book/pull/21, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAXF2PTGCNXZAHBXWIV7BLT7EQM5ANCNFSM5C7LBCQA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


[Snyk] Security upgrade python from 3.10-slim to 3.13.0rc2-slim

Snyk has created this PR to fix 5 vulnerabilities in the dockerfile dependencies of this project.
Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Snyk changed the following file(s):

model_training/s3/Dockerfile

We recommend upgrading to python:3.13.0rc2-slim, as this image has only 40 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Integer Overflow or Wraparound SNYK-DEBIAN12-ZLIB-6008963
  500

CVE-2024-26462 SNYK-DEBIAN12-KRB5-6277421
  150

Use of a Broken or Risky Cryptographic Algorithm SNYK-DEBIAN12-LIBGCRYPT20-1550206
  150

Information Exposure SNYK-DEBIAN12-LIBGCRYPT20-6405981
  150

CVE-2023-50495 SNYK-DEBIAN12-NCURSES-6123823
  150

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Use of a Broken or Risky Cryptographic Algorithm

@rootfs could you fix the DCO for this?


include html docs unzipped?

assuming this software would itself be compressed (eg using zip or gzip or bzip2 or xc) it does not make sense to ship the documentation inside it as a zip file. It would be better to shiip these unzipped.

It makes sense from the perspective of keeping all the HTML files together in a single bundle.  If someone wanted to install the HTML files somewhere, they would have to bundle them, move them to the new location, and unbundle them.
Keep in mind this is an early prototype project.  We're a long ways away from doing the first release.


Update extensions

Add igbinary extension. Fixes #387
Add ip2location extension. This also needs a shared library libip2location from source. Fixes #386
Add bitset extension.

We can hold off on the ip2location for now.


re-add bothell majors

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 76.573%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
657

Relevant Lines:
858

💛  - Coveralls


Add recepit error info for new permission system

为权限系统添加一个新的错误返回码

Codecov Report

Merging #41 into develop will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           develop     #41      +/-   ##
==========================================
- Coverage     47.3%   47.3%   -0.01%
==========================================
  Files          125     125
  Lines        19941   19942       +1
==========================================
  Hits          9433    9433
- Misses       10508   10509       +1

Impacted Files
Coverage Δ

libproto/src/protos/executor.rs
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


mongo integration autosetup not working

Description
When using curl -Ls https://raw.githubusercontent.com/newrelic/newrelic-cli/master/scripts/install.sh | bash && sudo NEW_RELIC_API_KEY=xxx NEW_RELIC_ACCOUNT_ID=xxx /usr/local/bin/newrelic install, presence of Mongo is detected and it starts the installation of the integration, however after providing the username / password / etc.., I receive a [Error]: cannot establish connection to mongodb.
When I write the same configuration in the /etc/newrelic/integrations.d/mongod.yml and restart it, the logs says it worked : newrelic-infra-service[3095967]: time="2021-08-18T15:02:51Z" level=info msg="Integration health check finished with success" instance=all integration=com.newrelic.mongodb prefix=config/mongodb working-dir=/var/db/newrelic-infra/newrelic-integrations
So I think something is broken in the setup.
Go Version
Command go not found
Current behavior
My mongo is running in Docker, with a 4.4 version, with a port forwarding on the standard port but on an internal address (i.e not <IP_ADDRESS> nor a public IP, but a third address):
$>docker ps
f233a7ff94c3   mongo:4.4                             "docker-entrypoint.s…"   3 months ago   Up 3 months   <IP_ADDRESS>:27017->27017/tcp                         mongo_mongo_1

It is set as a cluster, with two other machines.
The host mongo version is also a 4.4 (only used to have the cli, the server is not running)
From the host, executing mongo -u newrelic --password --host <IP_ADDRESS> works (after asking / providing the password)
From the newrelic autosetup, with the same parameters, the integration says it cannot connect to mongo.
Expected behavior
The mongo integration autosetup should be able to connect as expected to my docker instance.
Debug Output (if applicable)
sudo NEW_RELIC_API_KEY=xxx NEW_RELIC_ACCOUNT_ID=xxx /usr/local/bin/newrelic install

   _   _                 ____      _ _
  | \ | | _____      __ |  _ \ ___| (_) ___
  |  \| |/ _ \ \ /\ / / | |_) / _ | | |/ __|
  | |\  |  __/\ V  V /  |  _ |  __| | | (__
  |_| \_|\___| \_/\_/   |_| \_\___|_|_|\___|

  Welcome to New Relic. Let's install some instrumentation.

  Questions? Read more about our installation process at
  https://docs.newrelic.com/

INFO Validating connectivity to the New Relic platform...
    ✅ Checking for data in New Relic (this may take a few minutes)...success.
The guided installation will begin by installing the latest version of the New Relic Infrastructure agent, which is required for additional instrumentation.

? Please choose from the following instrumentation to be installed: MongoDB Open Source Integration

The following will be installed:
  Infrastructure Agent
  MongoDB Open Source Integration

==> Installing infrastructure-agent-installer...
Hit:1 http://ppa.launchpad.net/brightbox/ruby-ng/ubuntu focal InRelease
Hit:2 https://download.docker.com/linux/ubuntu focal InRelease
Hit:3 https://download.newrelic.com/infrastructure_agent/linux/apt focal InRelease
Ign:4 https://repo.mongodb.org/apt/ubuntu focal/mongodb-org/4.4 InRelease
Hit:5 https://repo.mongodb.org/apt/ubuntu focal/mongodb-org/4.4 Release
Get:6 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB]
Hit:7 http://nova.clouds.archive.ubuntu.com/ubuntu focal InRelease
Get:8 http://nova.clouds.archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB]
Get:10 http://nova.clouds.archive.ubuntu.com/ubuntu focal-backports InRelease [101 kB]
Fetched 328 kB in 1s (443 kB/s)
Reading package lists...
Warning: apt-key output should not be parsed (stdout is not a terminal)
OK
Hit:1 http://ppa.launchpad.net/brightbox/ruby-ng/ubuntu focal InRelease
Hit:2 http://nova.clouds.archive.ubuntu.com/ubuntu focal InRelease
Get:3 http://nova.clouds.archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB]
Get:4 http://nova.clouds.archive.ubuntu.com/ubuntu focal-backports InRelease [101 kB]
Hit:5 https://download.newrelic.com/infrastructure_agent/linux/apt focal InRelease
Hit:6 https://download.docker.com/linux/ubuntu focal InRelease
Ign:7 https://repo.mongodb.org/apt/ubuntu focal/mongodb-org/4.4 InRelease
Hit:8 https://repo.mongodb.org/apt/ubuntu focal/mongodb-org/4.4 Release
Get:9 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB]
Fetched 328 kB in 1s (447 kB/s)
Reading package lists...
Running agent status check attempt...
Agent status check ok.
    ✅ Checking for data in New Relic (this may take a few minutes)...success.
  ⚙  The Infrastructure Agent configuration file can be found in /etc/newrelic-infra.yml
  Edit this file to make changes or configure advanced features for the agent. See the docs for options:
  https://docs.newrelic.com/docs/infrastructure/install-infrastructure-agent/configuration/infrastructure-agent-configuration-settings

  Note: Process monitoring has been enabled by default - all other config options are left to the user.

==> Installing infrastructure-agent-installer...success.

==> Installing mongodb-open-source-integration...
  To capture data from the MongoDB integration, you'll first need to meet these prerequisites:
  - MongoDB version requirement (see https://docs.newrelic.com/docs/integrations/host-integrations/host-integrations-list/mongodb-monitoring-integration#comp-req)
  - User with clusterMonitor and listCollections roles

  In the MongoDB shell, execute the following commands to create a
  listCollections role and a new user, then assign clusterMonitor and
  listCollections roles to the new user.
  Note: username, password, and similar user-specific values must be replaced.

  In the MongoDB shell run the following command
  > rs.initiate()

  Switch to the admin database
  > use admin

  Use the following command to create the listCollections role:
  > db.createRole({role: "listCollections", privileges: [{ resource: {db:"",collection:""}, actions: ["listCollections"] }], roles: []})

  Use the following commands to create a new user, and assign clusterMonitor and listCollections roles to the user:
  > db.createUser({ user: "username", pwd: "password", roles: [ "clusterMonitor", "listCollections" ]})

? MongoDB Username newrelic
? MongoDB Password *************
? MongoDB Cluster Name Cluster4.4
? MongoDB Auth Source (default: admin) admin
? MongoDB Hostname (default: localhost) <IP_ADDRESS>
? MongoDB Port (default: 27017) 27017
? Use SSL to connect? (false/true) false
? Client Certificate file (if applicable)
? Certificate Authority file (if applicable)

[Error]: cannot establish connection to mongodb. See https://docs.newrelic.com/docs/integrations/host-integrations/host-integrations-list/mongodb-monitoring-integration#config for more info.
==> Installing mongodb-open-source-integration...failed.

WARNING exit status 2: [Error]: cannot establish connection to mongodb. See https://docs.newrelic.com/docs/integrations/host-integrations/host-integrations-list/mongodb-monitoring-integration#config for more info.
WARNING execution of MongoDB Open Source Integration failed, please see the following link for clues on how to resolve the issue: https://docs.newrelic.com/docs/using-new-relic/cross-product-functions/troubleshooting/not-seeing-data/
  One or more installations failed.  Check the install log for more details: /root/.newrelic/newrelic-cli.log
  New Relic installation complete!
  Your data is available at https://one.newrelic.com/redirect/entity/NzgwNjMxfElORlJBfE5BfDU1ODg0NDA3ODQwNDY5NjUyNTM
FATAL We encountered an error during the installation: exit status 2: [Error]: cannot establish connection to mongodb. See https://docs.newrelic.com/docs/integrations/host-integrations/host-integrations-list/mongodb-monitoring-integration#config for more info.. If this problem persists please visit the documentation and support page for additional help here: https://one.newrelic.com/-/06vjAeZLKjP

Also having this problem.


[BUG] Share manager pod would be recreated repeatedly until the pod is eventually scheduled

    There are at least two issues in this ticket.

The first one is that the share-manager pod is deleted and created repeatedly bacause of the ticket https://github.com/longhorn/longhorn-manager/commit/ed1f74273fb2d86d85d910ec7a08e2654f477536. Immediate checking pod.spec.nodeName (code) after creating a pod (code) would lead to an error that the pod is not scheduled by kubelet yet. For this issue, I added a verifyCreation logic in the share-manager controller, but I doubt there are some issues not resolved in the controller.
The second issue is I mentioned in https://github.com/longhorn/longhorn/issues/5224#issuecomment-1374431192. Actually, not sure if related to the first one or the NFS-ganesha issue. So, the customized images is to clarify if it is introduced by NFS-ganesha first.
cc @innobead
Originally posted by @derekbit in https://github.com/longhorn/longhorn/issues/5224#issuecomment-1374992517

cc @joshimoo

Sounds good to me.


Update README.md

Pull Request Etiquette

[x] I have checked the PRs for upcoming features/bug fixes.
[x] I have read the contributing guidelines.

Changes

[ ] Internal code
[ ] Library interface (affecting end-user code)
[x] Documentation
[ ] Other: _____

Closes Issue: NaN
Description
Remove unnecessary hyphens, change wording, etc

Closing for inactivity


Add support for adding a layer with raw geoJson data strings

Usage:
_map.AddLayer(new GeoJsonDataLayer() { GeoJsonData = @"geojson data string here" });

Thank you for this contribution!

Hi @RichardVogelij,
can I use customized markers with this? In JS, I would do something like:
                pointToLayer: function (feature, latlng) {
                    return Leaflet.marker(latlng, {
                        icon: myIcon,
                        rotationAngle: feature.properties.Direction,
                        title: feature.properties.Description
                    })
                }

myIcon, in turn, can be raw HTML, like so:
            var vesselIcon = Leaflet.divIcon({
                html: '<i class="fas fa-ship"></i>',
                className: 'leaflet-fontawesomeicon'
            });

For the above, I would need something like a layer.OnDrawFeature() event. But maybe there's a more elegant way?


Mention where the logs are located

The readme should mention that the Kong logs are located at /usr/local/kong/logs/

good idea think you could PR that?


Refactor llcp pdu length validation

Using a macro instead of repeated code for length validation

sits on-top of SCA PR, will rebase once merged

sits on-top of SCA PR, will rebase once merged

Can you please provide at link to the other PR? Also suggest to mark this as draft until the other PR has been merged

sits on-top of SCA PR, will rebase once merged

Can you please provide at link to the other PR? Also suggest to mark this as draft until the other PR has been merged

It is also possible to set the target branch of this PR to the branch of the other PR. Then the diff will show up correctly and once the other PR is merged the target branch of this PR will be changed to main.

Change is fine for non-test code, but for tests/bluetooth/controller/common/src/helper_pdu.c I'm a bit "worried" that this change uses PDU_DATA_LLCTRL_LEN for both the helper_pdu_encode_XXX functions and the helper_pdu_verify_XXX functions.
If an error was to be introduced in PDU_DATA_LLCTRL_LEN, these tests would no longer catch the length errors - as it's a fairly simple macro the chances are pretty low - I'm thinking in broader terms.
In my world test code is close to the metal and sometimes at bit cumbersome due to the fact that it cannot rely on the constructs it's trying to test and verify - otherwise there's no point in testing if both ends of the test has the same error and therefore self corrects.
Would like to hear other opinions.

If I am understanding you correct, you are arguing that using the same function/macro/whatever to calculate the value and to verify that the calculation is correct, may not catch any issues. I can fully agree to that, basically you don't want to have a test like
int foo()
{
    return val;
}

int test_foo()
{
    foo_val = foo();
    zassert_equal(foo_val, foo());
}

As any errors introduced in foo would not be caught.

I agree with @thoh-ot and @Thalley  - updated PR to keep the test code as is.

Added DNM as there is only one squashed commit in this PR. Please rebase.

If I am understanding you correct, you are arguing that using the same function/macro/whatever to calculate the value and to verify that the calculation is correct, may not catch any issues. I can fully agree to that, basically you don't want to have a test like...

@Thalley That was exactly what i was trying to say.


Unary operator& Fix

I'm merging it, though it's a bit more complicated with the changes to integer typedefs of util.h which I have to address myself.

I have replaced your commit on integer data types with my one. It was more complicated than a partial reverse could do.


Constant potential electrolysis

Dr. Burke,
I have one more question about applications of the Nanostat, then I promise to leave the issues board alone for a while.
Do you think the Nanostat hardware would be capable of constant potential electrolysis?  I haven't found other applications in some googling around of others using the LMP91000 for this process.
I recognize I would need to do some programming to achieve this.  If I do implement this successfully, I will fork the repo and share everything back.
Thank you for your thoughts!

Yes.
Use the DC tab. It is meant for noise test on the readings. But you can use it to DC bias.
The only question is the max current you would need to check that.


move vector_clock and sync into concurrency & make vector_clock private

Closes https://github.com/rust-lang/miri/issues/2199
The thread.rs didn't have to be moved to build.
If it makes more sense to move the thread.rs as well, please let me know. I can move it as well.

This looks good, thanks. :)
@bors r+

If it makes more sense to move the thread.rs as well, please let me know. I can move it as well.

Yes I think that would make sense. Would you like to submit a follow-up PR for that?

:pushpin: Commit 8ee68490122fba1849565e99804e8c78ee4d9e3a has been approved by RalfJung
It is now in the queue for this repository.

:hourglass: Testing commit 8ee68490122fba1849565e99804e8c78ee4d9e3a with merge 7b071620cb9f3120eade6f7a15c89024a7c17a59...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing 7b071620cb9f3120eade6f7a15c89024a7c17a59 to master...

Yes I think that would make sense. Would you like to submit a follow-up PR for that?
Yes, I will do that.


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 83 ms

Resolved: ClamAV performance has improved in 1a60fb7.


help?

File "c:\Users\User.vscode\extensions\ms-python.python-2019.9.34911\pythonFiles\ptvsd_launcher.py", line 21, in
import ptvsd
File "c:\Users\User.vscode\extensions\ms-python.python-2019.9.34911\pythonFiles\lib\python\ptvsd_init_.py", line 13, in
from .vendored import force_pydevd
File "c:\Users\User.vscode\extensions\ms-python.python-2019.9.34911\pythonFiles\lib\python\ptvsd_vendored\force_pydevd.py", line 37, in
'pydevd',
File "c:\Users\User.vscode\extensions\ms-python.python-2019.9.34911\pythonFiles\lib\python\ptvsd_vendored_init.py", line 123, in preimport
import_module(name)
File "C:\Python\Python37\lib\importlib_init_.py", line 127, in import_module
return _bootstrap.gcd_import(name[level:], package, level)
File "c:\Users\User.vscode\extensions\ms-python.python-2019.9.34911\pythonFiles\lib\python\ptvsd_vendored\pydevd\pydevd_plugins_init.py", line 2, in
import('pkg_resources').declare_namespace(name)
File "C:\Python\Python37\lib\site-packages\pkg_resources.py", line 1479, in
register_loader_type(importlib_bootstrap.SourceFileLoader, DefaultProvider)
AttributeError: module 'importlib._bootstrap' has no attribute 'SourceFileLoader'

Hi @PizzaRules668, please open a new issue following the issue template describing the error as well as steps to replicate the issue.


Local changes needed to run lobster-contribute.sh

Hi, I'm documenting two local changes I made in order to run the lobster-contribute.sh script. Hopefully this helps others! I'm using a Mac, so I'm not sure if other environments would have had similar issues.
Full script signature (run from scripts folder):
./lobster-contribute.sh <my_utxo> <lobster_script_utxo> <my_payment_address_path> <my_payment_signing_key_path> <old_counter> <new_counter> <old_votes>

Changes needed:
Ensure that the CARDANO_NODE_SOCKET_PATH is correct in the script files. Two options:

Set CARDANO_NODE_SOCKET_PATH to the correct location for your node.socket file.

This is needed in lobster-contribute.sh, lobster-deploy.sh, lobster-mint-nft.sh, mainnet-query-protocol-parameters.sh, and mainnet-utxo-at.sh

Or, make sure that node.socket is actually located in the scripts folder

Ensure you can run cardano-cli.

There may be multiple ways to ensure that cardano-cli is available in the scripts. I just removed ./ in front on cardano-cli in the following scripts (assuming cardano-cli is already available in your $PATH):

lobster-contribute.sh, lobster-deploy.sh, lobster-mint-nft.sh, mainnet-query-protocol-parameters.sh, mainnet-script-address.sh, mainnet-utxo-at.sh, and policyId.sh

what is these old counter, new counter old votes?

what is these old counter, new counter old votes?

Use the cli to query the utxos at the script address:
# Option 1 - script
./mainnet-utxo-at.sh addr1w8433zk2shufk42hn4x7zznjjuqwwyfmxffcjszw5l2ulesdt3jff

# Option 2 - run CLI directly (I had some issues running the script)
cardano-cli query utxo \
--address addr1w8433zk2shufk42hn4x7zznjjuqwwyfmxffcjszw5l2ulesdt3jff \
--mainnet

The output should look like:
                           TxHash                                 TxIx        Amount
--------------------------------------------------------------------------------------
319752b414804415988fb1165358e69f46095a9e9b1c01ef0830c182dc57f78b     0        1000000 lovelace + TxOutDatumHashNone
4c34feb07e32aa4855a494306aefcf16743356811914d680e112a6ec12214455     0        1000000 lovelace + TxOutDatumHashNone
63091c70aa6f8b402faffd24909d93c7721cbdced7094b62e52d157da8fb44e4     0        5000000 lovelace + TxOutDatumHashNone
67d318fabdd9905033bfe6156c6595716c952d496cabb9d98773c948974780ec     0        1000000 lovelace + TxOutDatumHashNone
85fef164485267ef2023bf3aee53036ef2b6c0ce4e8158913a5d759e7b7cda5b     1        2034438 lovelace + 1 cc7888851f0f5aa64c136e0c8fb251e9702f3f6c9efcf3a60a54f419.LobsterNFT + 13501 fda1b6b487bee2e7f64ecf24d24b1224342484c0195ee1b7b943db50.LobsterCounter + 318 fda1b6b487bee2e7f64ecf24d24b1224342484c0195ee1b7b943db50.LobsterVotes + TxOutDatumHash ScriptDataInAlonzoEra "45b0cfc220ceec5b7c1c62c4d4193d38e4eba48e8815729ce75f9c0ab0e4c1c0"
cb7b44500fc9145cf5b13a533bc7616eb219b7a080bc49d7ce6204c06b351733     0        1000000 lovelace + TxOutDatumHashNone
db250ed5eb4454843af19dea7ca84a8adda170fc88284e7e5e2381b41dab5f9b     1        30768137 lovelace + TxOutDatumHashNone

The utxo used for this vote is the one that has a really long entry in the table. Right now, it has the TxHash 85fef164485267ef2023bf3aee53036ef2b6c0ce4e8158913a5d759e7b7cda5b, but this will change over time.
From that entry, we can get the values:

Old counter: 13501
New counter: 13502
Old votes: 318


Amazon S3 perl module install for workunits, copied from rh-luminous

Signed-off-by: Tejas Chandramouli<EMAIL_ADDRESS>

@TejasC88 any logs for this?

There is a failure in the logs, debugging it slowly!


Show number of ServiceInstances on a ServicePlan in ServicePlan.Status

Depends on #1214; similar to #1215.
It would be useful to see the number of ServiceInstances using a ServicePlan in that plan's status.

No real opinion yet on this one, but I'm curious whether this goes against some "kube way" of doing things because as you add new instances we'd need to touch its parent plan each time. Kind of like how we don't point from the plan to each instance, we point from instances up to the plan.
And is there a risk of things getting out of sync since we don't have a transaction model and things can crash between the time we create/delete a new instance and the time we update the plan instance count?  Would we periodically need to count the # of instances for each plan to make sure the count in the plan is accurate?

@duglin this wouldn't be updated as part of reconciling an instance.  We'd add a control-loop for ServiceClass and ServicePlan that maintained this piece of status.
For example, as an analogy, the kubelet doesn't update replica counts for replica sets when it reconciles a pod - there is a controller that backs the replicaset resource that maintains the replica count.  The controller would periodically set the status fields correctly.
Does that make sense?

Note, we also will need field selection on ServiceInstance in order to implement this.


downgrade minimal python version requirments

attempt to use python >=3.8.10 (default on ubuntu 20.04) instead of 3.8.12
Ubuntu images come with python 3.8.10 (even after a distr-upgrade) relaxing the setup.py to check for a python version >=3.8.10 - will facilitate the installation process on ubuntu 20.04

@epifanio I am guessing that you can confirm the build worked with 3.8.10?

Yes, I confirm the User Interface starts without errors/warnings - However, I didn´t test its main functionalities. It is a minor version downgrade, it should be safe.


TypeError: Cannot read property 'id' of undefined

I am getting error on load-balancer when client try to call server using it.

Hey, this was an experimental repo, never thought it would see use 😄 I would recommend using this instead of this repo: https://github.com/senecajs/seneca-balance-client
If you prefer the API of this repo, I would be happy to actually finish it, if you want.


SMO Server Event Handling Issue

There appear to be some security considerations for subscribing to SQL Server events not addressed by the article titled "Handling SMO Events". Using the sample code provided, I encounter an error that states: "Cannot start an event subscription" and "The RPC server is unavailable". I am an administrator on the target server and have successfully used SMO to perform many tasks using the DataTransfer object, but encounter these errors after I attempt to start the events using db.Events.StartEvents(). Are there server or firewall settings that need to be enabled to subscribe to and start events on a remote server? Thank you!

@kidmusky -- thank you for your question regarding this article:
https://docs.microsoft.com/en-us/sql/relational-databases/server-management-objects-smo/create-program/handling-smo-events
Please consider these resources:

DBA Stack Exchange
Stack Overflow

You are welcome to add this issue here:

SQL Server Feedback

cc @markingmyname for awareness
I am closing this issue now.  You are welcome to @ mention me for any followup.
We hope to hear from you again.


https://us-python.pkg.dev/gce-ai-infra/maxtext-build-support-packages/simple/ not public

I don't think https://us-python.pkg.dev/gce-ai-infra/maxtext-build-support-packages/simple/ is public.

Does this cause issues for you during setup.sh?

Yes, here: https://github.com/google/maxtext/blob/ef9a6e9b96aef039797ecfcd20dd9ec554f8e387/setup.sh#L106-L108

It is a public facing repo. Could you share the exact error message you are seeing, please?

I'll try to do it if I find time but I am super busy these days and it's been some time since I used maxtext (and that was on a cluster I am not using any more)

But I think the error message to be expected is clear: We don't have access to that link, thus we need to just use pypi instead


Spg 1932 fix service override

Describe your changes
Comment Triggers

PR Check triggers

Build: trigger build
Sub Category Field Check: trigger subcategoryfieldcheck

Please generate the documentation, once since the schema was changed.


A couple CLI tweaks

Hi @lauraluebbert ,
I noticed with gget 0.2.0 that gget --help returns with an error code. Also, it appears that gget -v or gget --version aren't currently working as expected.
Best,
Mike

Hi Michael,
The cli bugs should be fixed in version 0.2.1 (pip install --upgrade gget). Thank you very much for bringing this to my attention!
Best,
Laura


Pass aggregator parent sources/args appropriately

The aggregator builder parent sources and cmdline args can be passed via

AggregateApplicationBuilder constructor
AggregateApplicationBuilder parent() builder method
and, the cmd line args can also be passed via
AggregateApplicationBuilder run() method

This PR supports passing all these options. The implementation sets parentSources and parentArgs by collecting the values from all the above options and use them when creating the parent context.

Add test case to verify these scenarios

This resolves #626

LGTM - rebased & merged.


Add HTTPS logging endpoint support

https://docs.fastly.com/en/guides/log-streaming-https is available via the API but has no client interface I can see.

HTTPS endpoint support was added with https://github.com/fastly/go-fastly/pull/155 and released in v1.9.0.

whoops. my bad. thanks!


[FEAT] Support ssm session stop with wildcard

clvm ssm session stop asher*
clvm ssm session stop - as with instance will stop all running sessions (or based of **kwargs filter)

closing as partially implemented.


PPPoS_client example esp_netif_new() returns NULL interface at second attempt of connection. (IDFGH-4791)

Hi everybody I am using esp-idf 4.2/release (last update) for this case.
Related with this example I am testing PPP reconnection when PPP_LOST_IP event is triggered at on_ip_changed event handler. Doing this what I want is to close PPP connection as esp_modem_stop_ppp() function does inside, including hang up command “ATH”. Here my problem is that when I retry the connection (At second attempt), after successfully ending the first connection attempt, I get these error related with esp_netif_new():
The interface created with esp_netif_new() is all NULL, so at the moment of using at "esp_netif_attach(esp_netif, modem_netif_adapter)" it raise me an error because the interface is NULL.
I will appreciate all your help with this issue I am having.

First attempt of connection:

Second attempt of connection:

Already solved, Thanks. I forgot to


Made address fields editable

Fixes #125

@littlestar642 Could you please provide the format for entering the GPS co-ordinates on the label? Also You do not validate the GPS entered, could you please validate it before accepting it?

@littlestar642 Do you require all the changes to  floodrelief/settings.py ?

Changes to  floodrelief/settings.py and .vscode/settings.json are not related to this PR, I think they should be removed. settings.py variables can be handled with env file.

#146 is a duplicate of this PR

@littlestar642 When the user now clicks Requesting for Others, the entire GPS CO-ordinates is hidden.

Cant merge until the this is fixed
"@littlestar642 When the user now clicks Requesting for Others, the entire GPS CO-ordinates is hidden."

@littlestar642 When you made the field editable, as I mentioned before, there is no validation. The user is at a loss to understand what values to give in that field, especially since the auto-filled value does not look like GPS co-ordinates. Could you at least change the label such that the user knows what format is expected on clicking -- requesting for others? (just give a sample -- e.g 49.25968926590981,7.051553546748877)?
Without validation, the user can enter pretty much any value, and the value may not even be useful for the volunteer.

Made the changes as requested. Also added a placeholder for coordinates values. @biswaz Please review.

@littlestar642 give me a few minutes; I will update soon.

@vrthra Can you please tell me the Django username and password?

@biswaz Can you please help me on this. I am not able to access django admin.

Closing this since #289 provides similar functionallity.


Fixed thread race condition when updating PartsPanel

Ensure that propertyChangeEvents are handled on the EventDispatchThread
Cleanup several trivial compiler warnings.

I got distracted from testing the ColorMapping persistence to a file. Now that this PartsPanel bug is fixed, I'll try to finish testing the ColorMapping stuff soon.

I just added a second commit which improves several minor issues on the PartsPanel. Specifically, the sorting, tool tips, displaying panels and totals... Details are in the commit description. The first commit is the bug fix for the thread race condition and should definitely be incorporated. The second commit that I added tonight is pretty much new features so take a look and see if you like it. BTW, I think it also makes it easier to modify the data we pass to the panel and how the PartsPanel orders and groups it in case we ever get around to adding to it down the road... Now back to testing the Color Mapping persistence...

I took a look at the fix for the race condition, and if I understand correctly, it involves SwingUtilities.invokelater().  While that is a useful and important tool, it is only necessary when running on some thread other than the event processing thread, or if one wants to use the event queue architecturally, to serialized cascading events or something.
So the question is, why is a property change being triggered on some other thread?  I’d prefer to solve the problem that way.
I’m also concerned about the addition of PartInfo, but possibly for the wrong reason.  Years ago, I intentionally made the UI code dependent only on the generic notion of a Controller.  This was a change designed to enable use of some UI technology other than Swing, even something non-Java-based.  The string-based event channel would be easy to bridge to any native libraries, or other languages like Javascript.  (At the time, I was looking at Cocoa, Apple’s native UI toolkit.)
That decoupling is less important to me know, I’ll admit, since I’m more interested in leaving Java behind entirely.  I’ll also admit that shoving data through the string-based channel is very limiting, as you’ve seen.
In the end, I think I’m OK with PartInfo, but I wanted to explain the context, so you have more info to go on the next time you see a similar need.

I figured that making the event handler thread-safe was a better design than being concerned with what threads might change the property and thus fire the event. In any case, it should be pretty easy to identify what thread(s) is/are calling it. I'll dig a little more in that area and let you know what I discover.

Looks like the ExclusiveAction class is specifically designed for running on the non-UI thread. If an ExclusiveAction ultimately fires a PropertyChangeEvent such as manifestationAdded, then that handler is not executed on the UI thread. Specifically, I discovered that creating a strut by dragging with the mouse works on the UI thread, but hiding a strut with Ctrl-H is not processed on the UI thread. Creating a strut with JoinBalls is not on the UI thread either. I suspect that most, if not all of the classes derived from ChangeManifestations may not be run on the UI thread and could potentially have similar considerations, but that's just speculation at this point  I ran out of time and didn't dig much deeper at this time. It looks like there are only a couple of places in DocumentFrame where the ExclusiveAction constructor is called so it should be easy to figure out what's happening.
I don't think I'll get to look at it much more until Monday or Tuesday, but I wanted to pass along what I found so far. Hopefully this much will stir up something that will help you determine which approach we should take to the multiple thread issue. Let me know if there's something else in particular you want me to look into.

Thanks for digging, David.  Yes, this was helpful.  Yes, most significant edits use ExclusiveAction, to block out other user edits while still freeing up the event handing thread (EHT).  I had forgotten this detail.  Your approach to making the PropertyChangeListener thread safe is correct, though I’ll come back to this question at the end of the email.
The issue does make me question my architecture.  It makes me want to segregate PropertyChangeEvents (PCEs) by source.  One kind of PCE represents the UI reacting to a UI gesture, with no round-trip to the controller and model layers.  For example, often a PCE will fire from the EHT, say, during a slider drag, checkbox click, or some other control gesture.  I was thinking about this pattern of PCE firing and handling when I reacted against using invokeLater; it feels like an anti-pattern when the PCE fires on the EHT in the first place.
Another source of PCEs is the model layer, in response to an UndoableEdit, as you’ve seen for the parts panel.  From memory, I'm not sure how many of these there are.
Finally, there is quite a bit of state in the controllers themselves, state that is not saved in the file.  Changes to controller state will trigger PCEs also.  Controller state is probably a bad thing in many (but not all) cases… it represents “models” that are not explicitly called out as such.
It would be very interesting to do a survey of all PCE firing points, and see if a classification emerges, and possibly some patterns for correct implementation.
Getting back to the original race condition: the race is between the ExclusiveAction thread firing a PCE and something else happening on the EHT.  What is the "something else"?  I'll review the original commit here to see if I can understand better.  I'm thinking along these lines: if we know we're firing a PCE from the ExclusiveAction background thread, perhaps we should use a Runnable to fire the event, then all PCLs can continue to assume that they are running on the EHT.  Perhaps another way to say it: any PCE fired from the model layer should use a Runnable to fire.
I look forward to your thoughts.

I see your excellent comment (again) in the code, explaining the race.  I think this confirms my conclusion above: any PCE known to emit from the background thread should be emitted via invokeLater somehow.  I'm still thinking about how to do that without putting a SwingUtilities dependency in the model layer.  I need to look at the details of how this particular PCE is fired.


Require an operation(Save or Show the results) when testing

It will waste a lot time to inference but do nothing if we didn't assign an operation
I did several times :joy:

Thanks! This check is necessary indeed.


Build(deps-dev): Bump @storybook/addon-essentials from 6.4.5 to 6.4.7 (#2099)

Pull request opened by the merge tool on behalf of #2099

Merged in f920c1e933bdf0d692a47c8be203dbca3dedc2c5


fix PHP 7.3 Warning: "continue" targeting switch is equivalent to "br…

…eak". Did you mean to use "continue 2"?
Found in Fedora QA, for various library using doctrine (not covered by doctrine test suite)
https://apps.fedoraproject.org/koschei/package/php-doctrine-doctrine-bundle?collection=f30
https://apps.fedoraproject.org/koschei/package/php-jms-serializer?collection=f30
etc

I encountered this issue too.
doctrine/orm: v2.6.2
php: 7.3.0RC3
In UnitOfWork.php line 2718:

  Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"?

@karser see https://github.com/doctrine/doctrine2/pull/7325


Fix for WFLY-13490, Galleon layer for web console

Issue: https://issues.redhat.com/browse/WFLY-13490
New layer in ee-galleon-pack, updated docs and layers test.

superseded by: https://github.com/wildfly/wildfly/pull/13343

Closing in favor of #13343


moved everything to design 5

Want to merge changes from Development to master
Chane log:
Switched from mutli-template to design 5

Merge approved

Merge approved


az policy assignment create and ---subscription

Would it be possible to allow az policy assignment create  to be used with --subscription, where the subscription is the name or id of the subscription?  If  --resource-group is used,  az policy assignment create cannot find the resource group if it is in another subscription.  The --role does not appear to work as expected and is less obvious than providing  --subscription.

policy

Hi, parameter --scope  can specify which subscription to apply to.
az policy assignment create --scope /subscriptions/<subscription-id>

The --scope flag has to be used with the subscription id, instead of the name.  For other commands, they allow --subscription, where the value can be the id or the name of the subscription.  The issue that one could execute a large number of commands using the name, but then find that the id has to be looked up for this one command.  While it is possible to lookup the id from the name using az account list, it adds another step for the user.
If the resource group is not in the default subscription:
$ az policy assignment create --name some_name --policy some_policy --scope "/subscriptions/some_subscription_id/resourceGroups/some_resource_group" ERROR: (MissingSubscription) The request did not have a subscription or a valid tenant level resource provider. Code: MissingSubscription Message: The request did not have a subscription or a valid tenant level resource provider.
The subscription id given was correct, but the command still reports an error.  Setting the default subscription to the subscription that contains the resource group
$ az policy assignment create --name some_name --policy some_policy --resource-group some_resource_group
works.  It seems a nasty hack to have to change the default subscription just for this command to work.  I am missing something?


Add tfc browserify shim instead of deeplearn.

This change is

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Upgrade base image to Debian 10 ("buster")

The current image is based on Debian 9 ("stretch") which has now been superseded by Debian 10 ("buster").
From https://www.debian.org/releases/stretch/

Debian 9 has been superseded by Debian 10 (buster). Security updates have been discontinued as of July 6th, 2020.

We should update to Debian 10 ("buster") to get security updates, and also to stay current with openjdk-11 which is no longer receiving updates on stretch.

Stretch Backports is still on openjdk 11.0.6 - https://packages.debian.org/stretch-backports/openjdk-11-jre-headless
Buster Stable is on openjdk 11.0.8 -  https://packages.debian.org/buster/openjdk-11-jdk-headless

@joakime Last I asked we were not allowed to upgrade jetty-runtime to jdk-11 as that needed to be coordinated with the wider jdk-11.
However, if "buster" also supports jdk-8, then upgrading now would be a good step to be ready.  @donmccasland Do you see any reason we can't do this?

The current image is based on FROM gcr.io/google-appengine/openjdk:8
It would be easy enough to base it FROM gcr.io/google-appengine/debian10:latest and just install openjdk-8-jdk-headless as the default.

Correction.  Debian 10 ("buster") has no openjdk-8 package available.
https://packages.debian.org/buster/java/
Seems to only support openjdk-11 or newer.
We could install the archive from adoptopenjdk easily enough though.

So we are now in the predicament.
We cannot continue to use Debian 9 ("stretch") due to lack of security updates, and no support for openjdk-11.
We cannot upgrade to Debian 10 ("buster") due lack of Java 8 JDK packages.
Can we create a new branch of the jetty-runtime images? perhaps with a new label like jetty-runtime-11:latest (or jetty-runtime:11-latest?) which is Debian 10 ("buster") and OpenJDK 11?

@joakime again I don't believe we can make an official jdk-11 image until all others are ready to go to jdk-11.  Surely there is a way to get a back port of jdk8 for debian 10?    jdk8 is going to live forever!