no route to host

WARN[0001] Error creating connection dial tcp <IP_ADDRESS>:28015: getsockopt: no route to host
FATA[0001] no connections were made when creating the session
This is what causes??

Too hard to say, How did you install shipyard?

curl -s https://shipyard-project.com/deploy | bash -s
This is a relationship with the docker version?

Show me your docker ps -a docker version

I have similar problems

@johnny-wang86  show me inspect output of rethinkdb container. docker inspect 18e

Can you also post the Docker version you are using?
On Tue, Oct 20, 2015 at 7:16 AM, Jason Young<EMAIL_ADDRESS>wrote:

@johnny-wang86 https://github.com/johnny-wang86 show me inspect output
of rethinkdb container. docker inspect 18e
—
Reply to this email directly or view it on GitHub
https://github.com/shipyard/shipyard/issues/640#issuecomment-149530846.

INFO[0000] shipyard version 3.0.1
WARN[0001] Error creating connection dial tcp <IP_ADDRESS>:28015: getsockopt: no route to host
FATA[0001] no connections were made when creating the session
INFO[0000] shipyard version 3.0.1
WARN[0001] Error creating connection dial tcp <IP_ADDRESS>:28015: getsockopt: no route to host
FATA[0001] no connections were made when creating the session
INFO[0000] shipyard version 3.0.1
WARN[0001] Error creating connection dial tcp <IP_ADDRESS>:28015: getsockopt: no route to host
FATA[0001] no connections were made when creating the session
INFO[0000] shipyard version 3.0.1
WARN[0001] Error creating connection dial tcp <IP_ADDRESS>:28015: getsockopt: no route to host
FATA[0001] no connections were made when creating the session
[
{
"Id": "e085c4c2a5aa1e13bdeecb61f78bd40e58ca5758907f8977f07447e56a032875",
"Created": "2015-10-20T11:59:38.001912365Z",
"Path": "rethinkdb",
"Args": [
"--bind",
"all"
],
"State": {
"Running": true,
"Paused": false,
"Restarting": false,
"OOMKilled": false,
"Dead": false,
"Pid": 20280,
"ExitCode": 0,
"Error": "",
"StartedAt": "2015-10-20T11:59:38.860081585Z",
"FinishedAt": "0001-01-01T00:00:00Z"
},
"Image": "84afe2b8ffc117382da1b23db65778cb57cf33584ef1550a72a72de1de37aa97",
"NetworkSettings": {
"Bridge": "",
"EndpointID": "4dca9d870a45815c8562f786b007007bd3cdc44af3a840b39bb780080a37fd0a",
"Gateway": "<IP_ADDRESS>",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"HairpinMode": false,
"IPAddress": "<IP_ADDRESS>",
"IPPrefixLen": 16,
"IPv6Gateway": "",
"LinkLocalIPv6Address": "",
"LinkLocalIPv6PrefixLen": 0,
"MacAddress": "02:42:ac:11:00:5b",
"NetworkID": "eda181dfc75f632540ac7bbbd24bddd00b6be9430fff0a0358d764f28194c391",
"PortMapping": null,
"Ports": {
"28015/tcp": null,
"29015/tcp": null,
"8080/tcp": null
},
"SandboxKey": "/var/run/docker/netns/e085c4c2a5aa",
"SecondaryIPAddresses": null,
"SecondaryIPv6Addresses": null
},
"ResolvConfPath": "/var/lib/docker/containers/e085c4c2a5aa1e13bdeecb61f78bd40e58ca5758907f8977f07447e56a032875/resolv.conf",
"HostnamePath": "/var/lib/docker/containers/e085c4c2a5aa1e13bdeecb61f78bd40e58ca5758907f8977f07447e56a032875/hostname",
"HostsPath": "/var/lib/docker/containers/e085c4c2a5aa1e13bdeecb61f78bd40e58ca5758907f8977f07447e56a032875/hosts",
"LogPath": "/var/lib/docker/containers/e085c4c2a5aa1e13bdeecb61f78bd40e58ca5758907f8977f07447e56a032875/e085c4c2a5aa1e13bdeecb61f78bd40e58ca5758907f8977f07447e56a032875-json.log",
"Name": "/shipyard-rethinkdb",
"RestartCount": 0,
"Driver": "devicemapper",
"ExecDriver": "native-0.2",
"MountLabel": "",
"ProcessLabel": "",
"Volumes": {
"/data": "/var/lib/docker/volumes/c1571b1ea07c19606cba8d70fdb1721d85ff5bae567f92b8bb509fa7ac70f401/_data"
},
"VolumesRW": {
"/data": true
},
"AppArmorProfile": "",
"ExecIDs": null,
"HostConfig": {
"Binds": null,
"ContainerIDFile": "",
"LxcConf": [],
"Memory": 0,
"MemorySwap": 0,
"CpuShares": 0,
"CpuPeriod": 0,
"CpusetCpus": "",
"CpusetMems": "",
"CpuQuota": 0,
"BlkioWeight": 0,
"OomKillDisable": false,
"Privileged": false,
"PortBindings": {},
"Links": null,
"PublishAllPorts": false,
"Dns": null,
"DnsSearch": null,
"ExtraHosts": null,
"VolumesFrom": null,
"Devices": [],
"NetworkMode": "bridge",
"IpcMode": "",
"PidMode": "",
"UTSMode": "",
"CapAdd": null,
"CapDrop": null,
"RestartPolicy": {
"Name": "always",
"MaximumRetryCount": 0
},
"SecurityOpt": null,
"ReadonlyRootfs": false,
"Ulimits": null,
"LogConfig": {
"Type": "json-file",
"Config": {}
},
"CgroupParent": ""
},
"Config": {
"Hostname": "e085c4c2a5aa",
"Domainname": "",
"User": "",
"AttachStdin": false,
"AttachStdout": false,
"AttachStderr": false,
"PortSpecs": null,
"ExposedPorts": {
"28015/tcp": {},
"29015/tcp": {},
"8080/tcp": {}
},
"Tty": true,
"OpenStdin": true,
"StdinOnce": false,
"Env": [
"PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
"RETHINKDB_PACKAGE_VERSION=2.1.5+2~0jessie"
],
"Cmd": [
"rethinkdb",
"--bind",
"all"
],
"Image": "rethinkdb",
"Volumes": {
"/data": {}
},
"VolumeDriver": "",
"WorkingDir": "/data",
"Entrypoint": null,
"NetworkDisabled": false,
"MacAddress": "",
"OnBuild": null,
"Labels": {}
}
}
]

@RustJason
docker inspect 18e
[
{
"Id": "18e34ceb83390f37f0e6e0a0607f57f5daa10e160f828368be19d13dc0942a27",
"Created": "2015-10-20T10:06:32.91621657Z",
"Path": "rethinkdb",
"Args": [
"--bind",
"all"
],
"State": {
"Running": true,
"Paused": false,
"Restarting": false,
"OOMKilled": false,
"Dead": false,
"Pid": 6659,
"ExitCode": 0,
"Error": "",
"StartedAt": "2015-10-20T10:06:33.202820075Z",
"FinishedAt": "0001-01-01T00:00:00Z"
},
"Image": "84afe2b8ffc117382da1b23db65778cb57cf33584ef1550a72a72de1de37aa97",
"NetworkSettings": {
"Bridge": "",
"EndpointID": "0d793d97b801046e8ec928a0a555677d9608d1d8a060f9b6ca46c2767c0cc048",
"Gateway": "<IP_ADDRESS>",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"HairpinMode": false,
"IPAddress": "<IP_ADDRESS>",
"IPPrefixLen": 16,
"IPv6Gateway": "",
"LinkLocalIPv6Address": "",
"LinkLocalIPv6PrefixLen": 0,
"MacAddress": "02:42:ac:11:00:05",
"NetworkID": "581f3a76b3282e7cf76ceaf2cdc9b0b7a7b4b63a6ee78b1aa64a7ffc68a5c920",
"PortMapping": null,
"Ports": {
"28015/tcp": null,
"29015/tcp": null,
"8080/tcp": null
},
"SandboxKey": "/var/run/docker/netns/18e34ceb8339",
"SecondaryIPAddresses": null,
"SecondaryIPv6Addresses": null
},
"ResolvConfPath": "/var/lib/docker/containers/18e34ceb83390f37f0e6e0a0607f57f5daa10e160f828368be19d13dc0942a27/resolv.conf",
"HostnamePath": "/var/lib/docker/containers/18e34ceb83390f37f0e6e0a0607f57f5daa10e160f828368be19d13dc0942a27/hostname",
"HostsPath": "/var/lib/docker/containers/18e34ceb83390f37f0e6e0a0607f57f5daa10e160f828368be19d13dc0942a27/hosts",
"LogPath": "/var/lib/docker/containers/18e34ceb83390f37f0e6e0a0607f57f5daa10e160f828368be19d13dc0942a27/18e34ceb83390f37f0e6e0a0607f57f5daa10e160f828368be19d13dc0942a27-json.log",
"Name": "/shipyard-rethinkdb",
"RestartCount": 0,
"Driver": "devicemapper",
"ExecDriver": "native-0.2",
"MountLabel": "",
"ProcessLabel": "",
"Volumes": {
"/data": "/var/lib/docker/volumes/4449cdaba9593b26cedd12196cd56ae4ef7135ede09ac8545f7aa5fa2faee006/_data"
},
"VolumesRW": {
"/data": true
},
"AppArmorProfile": "",
"ExecIDs": null,
"HostConfig": {
"Binds": null,
"ContainerIDFile": "",
"LxcConf": [],
"Memory": 0,
"MemorySwap": 0,
"CpuShares": 0,
"CpuPeriod": 0,
"CpusetCpus": "",
"CpusetMems": "",
"CpuQuota": 0,
"BlkioWeight": 0,
"OomKillDisable": false,
"Privileged": false,
"PortBindings": {},
"Links": null,
"PublishAllPorts": false,
"Dns": null,
"DnsSearch": null,
"ExtraHosts": null,
"VolumesFrom": null,
"Devices": [],
"NetworkMode": "bridge",
"IpcMode": "",
"PidMode": "",
"UTSMode": "",
"CapAdd": null,
"CapDrop": null,
"RestartPolicy": {
"Name": "always",
"MaximumRetryCount": 0
},
"SecurityOpt": null,
"ReadonlyRootfs": false,
"Ulimits": null,
"LogConfig": {
"Type": "json-file",
"Config": {}
},
"CgroupParent": ""
},
"Config": {
"Hostname": "18e34ceb8339",
"Domainname": "",
"User": "",
"AttachStdin": false,
"AttachStdout": false,
"AttachStderr": false,
"PortSpecs": null,
"ExposedPorts": {
"28015/tcp": {},
"29015/tcp": {},
"8080/tcp": {}
},
"Tty": true,
"OpenStdin": true,
"StdinOnce": false,
"Env": [
"PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
"RETHINKDB_PACKAGE_VERSION=2.1.5+2~0jessie"
],
"Cmd": [
"rethinkdb",
"--bind",
"all"
],
"Image": "rethinkdb",
"Volumes": {
"/data": {}
},
"VolumeDriver": "",
"WorkingDir": "/data",
"Entrypoint": null,
"NetworkDisabled": false,
"MacAddress": "",
"OnBuild": null,
"Labels": {}
}
}
]

@ehazlett
Docker version 1.7.1 ,kernel version 3.10.90-1 or  3.10.5-3

@bing6 @johnny-wang86 下次贴代码的时候用三个```扩起来。
Test

@ehazlett Is this cause by different version?

Hmm it shouldn't. It looks like a networking issue. Do you have any custom
networking you are doing on the engine?
On Tuesday, October 20, 2015, Jason Young<EMAIL_ADDRESS>wrote:

@ehazlett https://github.com/ehazlett Is this cause by different
version?
—
Reply to this email directly or view it on GitHub
https://github.com/shipyard/shipyard/issues/640#issuecomment-149768359.

@bing6 @johnny-wang86 Try to curl {rethinkdbip}:28015 and see what happens

@RustJason
8080/tcp, 28015/tcp, 29015/tcp
rethinkdb Port not open up.
I deployed successfully docker 1.8.
docker 1.7 will have this problem.

@bing6 But your inspect shows 28015/tcp are exposed, did you try to see the log of rethinkdb to see if it start correctly? And also, you can try to ```docker exec -it ${rethinkdb} bash``  in your controller and ping rethinkdb to see if this error reproduce again

@RustJason @ehazlett
This is indeed a network issue.
I found my container within the network can not visit each other.

@bing6 ah ok thanks for the update!  closing,


[BUG] POST request not working with Fetch::Request

Is there an existing issue for this?

[X] I have searched the existing issues

What version of workers-rs are you using?
0.3.0
What version of wrangler are you using?
3.63.1
Describe the bug
POST requests sent using Fetch::Request are never sent, and no error is emitted
Steps To Reproduce

Use this example code:

    let request = Request::new_with_init(
        &webhook_url,
        RequestInit::new()
            .with_body(Some(serde_wasm_bindgen::to_value(
                &json!({ "text": "hi"}),
            )?))
            .with_method(Method::Post),
    )?;
    Fetch::Request(request).send().await?;

Observe how the request is never sent, and code execution continues after the request is "sent" and awaited

The temporary workaround for this is to use a library like reqwest


Support overriding state options when creating state movements

So that https://github.com/indeedeng/iwf-java-sdk/issues/179 will be useful

in #193


Fetch next salts when there is one left and is about to expire

See https://github.com/Lonami/grammers/pull/172#pullrequestreview-1376269664 for context.
Because Telegram may return less salts than expected, there may be no "next salt that may be used" to check for. So instead, we should check if there's only one salt left and it will expire soon.

Should be good now after a6025a477505362853304dcc783234a195d7d89f.


Port forwarding rtsp cameras (port 554)

I am trying to access my cameras remotely by port forwarding port 554 to port 554 with the following command
ssh -R cameras:554:<IP_ADDRESS>:554 domain.com
the output is:
Starting SSH Forwarding service for tcp:554. Forwarded connections can be accessed via the following methods:
TCP Alias: cameras:554

how do I access the cameras

You should be able to access domain.com:554 for your cameras. As long as there is a service listening on <IP_ADDRESS>:554

Hey @riazbapoo,
You need to drop the cameras: from your ssh command. When you provide a parameter to a TCP connection, that creates a TCP alias within sish (an unexposed connection). If that is intentional, you can use a local forward ssh -L 8080:cameras:554 domain.com and point your rtsp client to localhost:8080. If it supports using a command as a pipe (like ffmpeg) you could even do this with ssh by doing ssh -W cameras:554 domain.com.


[doc] proofread documentation and fixed some typos.

Thumbs up!

In English, the 's possessives also work for objects. For example, "the school's mascot is a tiger".
In the case above, if the get method belongs to the request object, the possessive 's is valid. That is, if you could say "the get method of request", then you can also say, "request's get method."
Here's one of many sites detailing this: http://www.englishclub.com/grammar/nouns-possessive.htm


merge from arlac77/npm-package-template-esm-only

package.json

chore(package<EMAIL_ADDRESS>chore(scripts): cover@#overwrite c8 -x 'tests/**/*' --temp-directory build/tmp ava && c8 report -r lcov -o build/coverage --temp-directory build/tmp

Coverage remained the same at 88.375% when pulling dc3a5273d76b3abefe870f0cc023e357925e44f7 on npm-template-sync/1 into c047cee9aca3aff2ec90a63e435b343f5e2cf662 on master.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Crash while viewing utilization of K8s cluster

Describe the bug
A clear and concise description of what the bug is.
Application crashed while viewing utilization of K8s cluster
To Reproduce
Steps to reproduce the behavior or a screencast

Open application
Go to utilization tab
Play a bit with the grouping <g>
???
Crash

Expected behavior
A clear and concise description of what you expected to happen.
The application does not crash
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS and OS version: [e.g. macOS 10.1 / Fedora 34 / WIndows 10]

Ubuntu 20.04 LTS
Linux artemis 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Terminal name and version [e.g. Tilix, Yakuake, Gnome Terminal, Konsole, iTerm, Windows CMD]

Windows terminal using WSL2, though accessing a remote server over SSH

Shell name and version [e.g. bash, zsh, fish, powershell]

GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu)

Kubectl Client Version [e.g. 1.19]

Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.5", GitCommit:"6b1d87acf3c8253c123756b9e61dac642678305f", GitTreeState:"clean", BuildDate:"2021-03-18T01:10:43Z", GoVersion:"go1.15.8", Compiler:"gc", Platform:"linux/amd64"}

Kubectl Server Version [e.g. 1.19]

Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.5", GitCommit:"6b1d87acf3c8253c123756b9e61dac642678305f", GitTreeState:"clean", BuildDate:"2021-03-18T01:02:01Z", GoVersion:"go1.15.8", Compiler:"gc", Platform:"linux/amd64"}

KDash version [e.g. 0.0.8] 0.1.2

Additional context
Add any other context about the problem here.
Produced logs file:
tobias@artemis:~/kubernetes/manifests/system$ cat /tmp/report-310a52bb-fffa-45d3-bbfa-c68aa9d110aa.toml
name = 'kdash'
operating_system = 'unix:Ubuntu'
crate_version = '0.1.2'
explanation = '''
Panic occurred in file '/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tui-0.15.0/src/widgets/table.rs' at line 359
'''
cause = 'index out of bounds: the len is 171 but the index is 171'
method = 'Panic'
backtrace = '''

   0: 0x7f29ada79c82 - <unresolved>
   1: 0x7f29add1dcae - <unresolved>
   2: 0x7f29adbeae03 - <unresolved>
   3: 0x7f29adccf1d2 - <unresolved>
   4: 0x7f29adbcc548 - <unresolved>
   5: 0x7f29adb6e092 - <unresolved>
   6: 0x7f29adbdf629 - <unresolved>
   7: 0x7f29adcc1a14 - <unresolved>
   8: 0x7f29adc509ea - <unresolved>
   9: 0x7f29adb2f8c3 - <unresolved>
  10: 0x7f29adc31f0d - <unresolved>
  11: 0x7f29ae16cfa9 - <unresolved>
  12: 0x7f29adc510e2 - <unresolved>

Hi thanks for the report. Does it happen all the time or was a once off
error. There is an open issue in table widget library that I'm aware of.
Just need to make sure if this is the same
On Sat, 10 Jul 2021, 11:44 am Tobias de Bruijn, @.***>
wrote:

Describe the bug
A clear and concise description of what the bug is.
Application crashed while viewing utilization of K8s cluster
To Reproduce
Steps to reproduce the behavior or a screencast

Open application
Go to utilization tab
Play a bit with the grouping
???
Crash

Expected behavior
A clear and concise description of what you expected to happen.
The application does not crash
Screenshots
If applicable, add screenshots to help explain your problem.
[image: image]
https://user-images.githubusercontent.com/28569170/125158785-9d364400-e173-11eb-9855-001651a9b8b0.png
Desktop (please complete the following information):

OS and OS version: [e.g. macOS 10.1 / Fedora 34 / WIndows 10]

Ubuntu 20.04 LTS
Linux artemis 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Terminal name and version [e.g. Tilix, Yakuake, Gnome Terminal,
Konsole, iTerm, Windows CMD]

Windows terminal using WSL2, though accessing a remote server over SSH

Shell name and version [e.g. bash, zsh, fish, powershell]

GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu)

Kubectl Client Version [e.g. 1.19]

Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.5", GitCommit:"6b1d87acf3c8253c123756b9e61dac642678305f", GitTreeState:"clean", BuildDate:"2021-03-18T01:10:43Z", GoVersion:"go1.15.8", Compiler:"gc", Platform:"linux/amd64"}

Kubectl Server Version [e.g. 1.19]

Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.5", GitCommit:"6b1d87acf3c8253c123756b9e61dac642678305f", GitTreeState:"clean", BuildDate:"2021-03-18T01:02:01Z", GoVersion:"go1.15.8", Compiler:"gc", Platform:"linux/amd64"}

KDash version [e.g. 0.0.8] 0.1.2

Additional context
Add any other context about the problem here.
Produced logs file:
@.***:~/kubernetes/manifests/system$ cat /tmp/report-310a52bb-fffa-45d3-bbfa-c68aa9d110aa.toml
name = 'kdash'
operating_system = 'unix:Ubuntu'
crate_version = '0.1.2'
explanation = '''
Panic occurred in file '/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tui-0.15.0/src/widgets/table.rs' at line 359
'''
cause = 'index out of bounds: the len is 171 but the index is 171'
method = 'Panic'
backtrace = '''
0: 0x7f29ada79c82 -
1: 0x7f29add1dcae -
2: 0x7f29adbeae03 -
3: 0x7f29adccf1d2 -
4: 0x7f29adbcc548 -
5: 0x7f29adb6e092 -
6: 0x7f29adbdf629 -
7: 0x7f29adcc1a14 -
8: 0x7f29adc509ea -
9: 0x7f29adb2f8c3 -
10: 0x7f29adc31f0d -
11: 0x7f29ae16cfa9 -
12: 0x7f29adc510e2 -
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kdash-rs/kdash/issues/77, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIOKF4RJTFXEVPHO56S2ATTXAJBRANCNFSM5AECIFCQ
.

I haven't noticed it again yet, so I think it might have been a one-off

Ok that sounds like https://github.com/fdehau/tui-rs/issues/470

Experienced a (similar?) crash once more, this time just after selecting a namespace. Screen size did not change while doing so (2569x1080):
tobias@artemis:~$ kdash
Well, this is embarrassing.

kdash had a problem and crashed. To help us diagnose the problem you can send us a crash report.

We have generated a report file at "/tmp/report-49fb2d66-62fc-4bed-8302-1a3e9c621a50.toml". Submit an issue or email with the subject of "kdash Crash Report" and include the report as an attachment.

- Homepage: https://github.com/kdash-rs/kdash
- Authors: Deepu K Sasidharan<EMAIL_ADDRESS>
We take privacy seriously, and do not perform any automated error collection. In order to improve the software, we rely on people to submit reports.

Thank you kindly!
tobias@artemis:~$ cat /tmp/report-49fb2d66-62fc-4bed-8302-1a3e9c621a50.toml
name = 'kdash'
operating_system = 'unix:Ubuntu'
crate_version = '0.1.2'
explanation = '''
Panic occurred in file '/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tui-0.15.0/src/widgets/table.rs' at line 359
'''
cause = 'index out of bounds: the len is 28 but the index is 47'
method = 'Panic'
backtrace = '''

   0: 0x7f5bbe150c82 - <unresolved>
   1: 0x7f5bbe3f4cae - <unresolved>
   2: 0x7f5bbe2bdfb3 - <unresolved>
   3: 0x7f5bbe2bbf00 - <unresolved>
   4: 0x7f5bbe2bb5c0 - <unresolved>
   5: 0x7f5bbe3a61fc - <unresolved>
   6: 0x7f5bbe2a3548 - <unresolved>
   7: 0x7f5bbe245092 - <unresolved>
   8: 0x7f5bbe2b6629 - <unresolved>
   9: 0x7f5bbe398a14 - <unresolved>
  10: 0x7f5bbe3279ea - <unresolved>
  11: 0x7f5bbe2068c3 - <unresolved>
  12: 0x7f5bbe308f0d - <unresolved>
  13: 0x7f5bbe843fa9 - <unresolved>
  14: 0x7f5bbe3280e2 - <unresolved>'''

Unfortunately I have to rely on tui-rs to fix it. In the meanwhile, I'll
try to find some workaround
On Tue, 13 Jul 2021, 2:47 pm Tobias de Bruijn, @.***>
wrote:

Experienced a (similar?) crash once more, this time just after selecting a
namespace. Screen size did not change while doing so (2569x1080):
@.***:~$ kdash
Well, this is embarrassing.
kdash had a problem and crashed. To help us diagnose the problem you can send us a crash report.
We have generated a report file at "/tmp/report-49fb2d66-62fc-4bed-8302-1a3e9c621a50.toml". Submit an issue or email with the subject of "kdash Crash Report" and include the report as an attachment.

Homepage: https://github.com/kdash-rs/kdash
Authors: Deepu K Sasidharan @.***>

We take privacy seriously, and do not perform any automated error collection. In order to improve the software, we rely on people to submit reports.
Thank you kindly!
@.***:~$ cat /tmp/report-49fb2d66-62fc-4bed-8302-1a3e9c621a50.toml
name = 'kdash'
operating_system = 'unix:Ubuntu'
crate_version = '0.1.2'
explanation = '''
Panic occurred in file '/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tui-0.15.0/src/widgets/table.rs' at line 359
'''
cause = 'index out of bounds: the len is 28 but the index is 47'
method = 'Panic'
backtrace = '''
0: 0x7f5bbe150c82 -
1: 0x7f5bbe3f4cae -
2: 0x7f5bbe2bdfb3 -
3: 0x7f5bbe2bbf00 -
4: 0x7f5bbe2bb5c0 -
5: 0x7f5bbe3a61fc -
6: 0x7f5bbe2a3548 -
7: 0x7f5bbe245092 -
8: 0x7f5bbe2b6629 -
9: 0x7f5bbe398a14 -
10: 0x7f5bbe3279ea -
11: 0x7f5bbe2068c3 -
12: 0x7f5bbe308f0d -
13: 0x7f5bbe843fa9 -
14: 0x7f5bbe3280e2 - '''
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kdash-rs/kdash/issues/77#issuecomment-879056718, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIOKF7AIMQRHSAMRNKUOKDTXQYUTANCNFSM5AECIFCQ
.

This is fixed upstream and lib is updated here

@TheDutchMC hey let me know if you see any similar issue in v0.2.3

I haven't noticed any yet!


subcommands vs. "required"

Can you change the parser to fill in both parent and child command's parameters if they have the same name?
Currently, a subcommand with a required param of same name as parent command will issue an error like "the required flag `--master-host' was not specified"
Here is a sample command parent/child:
type VersionCommand struct {
	Master_host   string `long:"master-host" required:"yes" description:"Domain name or IP of host"`
}

type CheckCommand struct {
	Version VersionCommand     `command:"version" alias:"ver" description:"stuff happened here"`
	Master_host string `long:"master-host" required:"yes" description:"Domain name or IP of host"`

Can you explain why your version command needs the same flag as its parent? Can you not just use the parents flag? I think what you're trying to do is just not the way go-flags works.

Thanks for the feedback. My requirement was that the subcommand have the same flag, but I'll ask the PM about changing that requirement.


Fix for #226.

Currently the client init uses only the first address info tuple returned from socket.getaddrinfo() to create the socket (see line 97). Unfortunately sometimes this isn't the right address. Best practice is to iterate through the address info tuples until we find one that we can connect to successfully. See this stack overflow question. This change necessitated moving the call to socket.connect out of the WebSocketBaseClient.connect method and into the WebSocketBaseClient.init method. If that is not desirable, we could instead pass the list of address information into the connect method and let the initialization of the socket happen there.

The unit tests don't seem to be set up to allow connecting to the socket in the init. Need to investigate further.


[GSsoc'23] React Project (pomodoro timer)

Pomodoro timer by Reactjs

@pranjay-poddar
Please assign me this issue under GSSOC'23.

please assign me this issue


use MatchJSON in tests wherever needed

What type of PR is this?

Uncomment only one  /kind line, and delete the rest.
For example, > /kind bug would simply become: /kind bug

/kind failing-test
/kind area/Windows
What does does this PR do / why we need it:
Which issue(s) this PR fixes:
Fixes https://github.com/openshift/odo/issues/3499
How to test changes / Special notes to the reviewer:
Failing tests should pass

/retest

@girishramnani IMO issue #3499 is not because of different json struct order, there is some missing attribute which I verified using FIt to a particular spec that is being changed in your pr and still facing the same error.
 ginkgo .\tests\integration\
Running Suite: Integration Suite
================================
Random Seed:<PHONE_NUMBER>
Will run 2 of 177 specs

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSCreated dir: C:\Users\Admin\AppData\Local\Temp\831810071
Creating a new project: mjmbuxbujz
Running odo.exe with args [odo project create mjmbuxbujz -w -v4]
[odo]  -  Waiting for project to come up  ...
[odo] I0709 06:08:24.188171    9444 occlient.go:543] Status of creation of project mjmbuxbujz is Active
[odo] I0709 06:08:24.269209    9444 occlient.go:548] Project mjmbuxbujz now exists
[odo] I0709 06:08:24.274117    9444 occlient.go:583] Status of creation of service account &ServiceAccount{ObjectMeta:{default  mjmbuxbujz /api/v1/namespaces/mjmbuxbujz/serviceaccounts/default cf43b679-c1a9-11ea-a594-fa163e9b6334 19192482 0 2020-07-09 06:02:45 +0000 GMT <nil> <nil> map[] map[] [] []  []},Secrets:[]ObjectReference{ObjectReference{Kind:,Namespace:,Name:default-token-nnqlx,UID:,APIVersion:,ResourceVersion:,FieldPath:,},ObjectReference{Kind:,Namespace:,Name:default-dockercfg-ddnms,UID:,APIVersion:,ResourceVersion:,FieldPath:,},},ImagePullSecrets:[]LocalObjectReference{LocalObjectReference{Name:default-dockercfg-ddnms,},},AutomountServiceAccountToken:nil,} is ready
 V  Waiting for project to come up [933ms]
[odo]  V  Project 'mjmbuxbujz' is ready for use
[odo]  V  New project created and now using project: mjmbuxbujz
[odo] I0709 06:08:24.311216    9444 odo.go:72] Could not get the latest release information in time. Never mind, exiting gracefully :)
Current working dir: C:\Users\Admin\go\src\github.com\openshift\odo\tests\integration
Setting current dir to: C:\Users\Admin\AppData\Local\Temp\831810071
Running odo.exe with args [odo create nodejs cmp-git --project mjmbuxbujz --git https://github.com/openshift/nodejs-ex --context C:\Users\Admin\AppData\Local\Temp\831810071 --app testing]
[odo] Validation
 V  Validating component [11ms]
[odo]
[odo] Please use `odo push` command to create the component with source deployed
Running odo.exe with args [odo url create url-1 --context C:\Users\Admin\AppData\Local\Temp\831810071]
[odo]  V  URL url-1 created for component: cmp-git
[odo]
[odo] To apply the URL configuration changes, please use `odo push`
Running odo.exe with args [odo url create url-2 --context C:\Users\Admin\AppData\Local\Temp\831810071]
[odo]  V  URL url-2 created for component: cmp-git
[odo]
[odo] To apply the URL configuration changes, please use `odo push`
Running odo.exe with args [odo storage create storage-1 --size 1Gi --path /data1 --context C:\Users\Admin\AppData\Local\Temp\831810071]
[odo]  V  Added storage storage-1 to cmp-git
[odo]
[odo] Please use `odo push` command to make the storage accessible to the component
Running odo.exe with args [odo describe --context C:\Users\Admin\AppData\Local\Temp\831810071]
[odo] Component Name: cmp-git
[odo] Type: nodejs
[odo] Source: https://github.com/openshift/nodejs-ex
[odo] Storage:
[odo]  · storage-1 of size 1Gi mounted to /data1
[odo] URLs:
[odo]  · URL named url-1 will be exposed via 8080/TCP
[odo]  · URL named url-2 will be exposed via 8080/TCP
Running odo.exe with args [odo describe -o json --context C:\Users\Admin\AppData\Local\Temp\831810071]
[odo] {
[odo]     "kind": "Component",
[odo]     "apiVersion": "odo.dev/v1alpha1",
[odo]     "metadata": {
[odo]         "name": "cmp-git",
[odo]         "namespace": "mjmbuxbujz",
[odo]         "creationTimestamp": null
[odo]     },
[odo]     "spec": {
[odo]         "app": "testing",
[odo]         "type": "nodejs",
[odo]         "source": "https://github.com/openshift/nodejs-ex",
[odo]         "sourceType": "git",
[odo]         "urls": {
[odo]             "kind": "List",
[odo]             "apiVersion": "odo.dev/v1alpha1",
[odo]             "metadata": {},
[odo]             "items": [
[odo]                 {
[odo]                     "kind": "url",
[odo]                     "apiVersion": "odo.dev/v1alpha1",
[odo]                     "metadata": {
[odo]                         "name": "url-1",
[odo]                         "creationTimestamp": null
[odo]                     },
[odo]                     "spec": {
[odo]                         "port": 8080,
[odo]                         "secure": false
[odo]                     },
[odo]                     "status": {
[odo]                         "state": "Not Pushed"
[odo]                     }
[odo]                 },
[odo]                 {
[odo]                     "kind": "url",
[odo]                     "apiVersion": "odo.dev/v1alpha1",
[odo]                     "metadata": {
[odo]                         "name": "url-2",
[odo]                         "creationTimestamp": null
[odo]                     },
[odo]                     "spec": {
[odo]                         "port": 8080,
[odo]                         "secure": false
[odo]                     },
[odo]                     "status": {
[odo]                         "state": "Not Pushed"
[odo]                     }
[odo]                 }
[odo]             ]
[odo]         },
[odo]         "storages": {
[odo]             "kind": "List",
[odo]             "apiVersion": "odo.dev/v1alpha1",
[odo]             "metadata": {},
[odo]             "items": [
[odo]                 {
[odo]                     "kind": "storage",
[odo]                     "apiVersion": "odo.dev/v1alpha1",
[odo]                     "metadata": {
[odo]                         "name": "storage-1",
[odo]                         "creationTimestamp": null
[odo]                     },
[odo]                     "spec": {
[odo]                         "size": "1Gi",
[odo]                         "path": "/data1"
[odo]                     }
[odo]                 }
[odo]             ]
[odo]         },
[odo]         "ports": [
[odo]             "8080/TCP"
[odo]         ]
[odo]     },
[odo]     "status": {
[odo]         "state": "Not Pushed"
[odo]     }
[odo] }
Deleting project: mjmbuxbujz
Running odo.exe with args [odo project delete mjmbuxbujz -f]
[odo]  V  Deleted project : mjmbuxbujz
[odo]  !  Warning! Projects are deleted from the cluster asynchronously. Odo does its best to delete the project. Due to multi-tenant clusters, the project
may still exist on a different node.
Setting current dir to: C:\Users\Admin\go\src\github.com\openshift\odo\tests\integration
Deleting dir: C:\Users\Admin\AppData\Local\Temp\831810071

------------------------------
+ Failure [3.781 seconds]
odo component command tests
C:/Users/Admin/go/src/github.com/openshift/odo/tests/integration/cmd_cmp_test.go:13
  Creating component
  C:/Users/Admin/go/src/github.com/openshift/odo/tests/integration/component.go:52
    should describe the component when it is not pushed [It]
    C:/Users/Admin/go/src/github.com/openshift/odo/tests/integration/component.go:233

    Expected
        <string>: {
          "apiVersion": "odo.dev/v1alpha1",
          "kind": "Component",
          "metadata": {
            "creationTimestamp": null,
            "name": "cmp-git",
            "namespace": "mjmbuxbujz"
          },
          "spec": {
            "app": "testing",
            "ports": [
              "8080/TCP"
            ],
            "source": "https://github.com/openshift/nodejs-ex",
            "sourceType": "git",
            "storages": {
              "apiVersion": "odo.dev/v1alpha1",
              "items": [
                {
                  "apiVersion": "odo.dev/v1alpha1",
                  "kind": "storage",
                  "metadata": {
                    "creationTimestamp": null,
                    "name": "storage-1"
                  },
                  "spec": {
                    "path": "/data1",
                    "size": "1Gi"
                  }
                }
              ],
              "kind": "List",
              "metadata": {}
            },
            "type": "nodejs",
            "urls": {
              "apiVersion": "odo.dev/v1alpha1",
              "items": [
                {
                  "apiVersion": "odo.dev/v1alpha1",
                  "kind": "url",
                  "metadata": {
                    "creationTimestamp": null,
                    "name": "url-1"
                  },
                  "spec": {
                    "port": 8080,
                    "secure": false
                  },
                  "status": {
                    "state": "Not Pushed"
                  }
                },
                {
                  "apiVersion": "odo.dev/v1alpha1",
                  "kind": "url",
                  "metadata": {
                    "creationTimestamp": null,
                    "name": "url-2"
                  },
                  "spec": {
                    "port": 8080,
                    "secure": false
                  },
                  "status": {
                    "state": "Not Pushed"
                  }
                }
              ],
              "kind": "List",
              "metadata": {}
            }
          },
          "status": {
            "state": "Not Pushed"
          }
        }
    to match JSON of
        <string>: {
          "apiVersion": "odo.dev/v1alpha1",
          "kind": "Component",
          "metadata": {
            "creationTimestamp": null,
            "name": "cmp-git",
            "namespace": "mjmbuxbujz"
          },
          "spec": {
            "app": "testing",
            "ports": [
              "8080/TCP"
            ],
            "source": "https://github.com/openshift/nodejs-ex",
            "sourceType": "git",
            "storages": {
              "apiVersion": "odo.dev/v1alpha1",
              "items": [
                {
                  "apiVersion": "odo.dev/v1alpha1",
                  "kind": "storage",
                  "metadata": {
                    "creationTimestamp": null,
                    "name": "storage-1"
                  },
                  "spec": {
                    "path": "/data1",
                    "size": "1Gi"
                  }
                }
              ],
              "kind": "List",
              "metadata": {}
            },
            "type": "nodejs",
            "urls": {
              "apiVersion": "odo.dev/v1alpha1",
              "items": [
                {
                  "apiVersion": "odo.dev/v1alpha1",
                  "kind": "url",
                  "metadata": {
                    "creationTimestamp": null,
                    "name": "url-1"
                  },
                  "spec": {
                    "kind": "route",
                    "port": 8080,
                    "secure": false
                  },
                  "status": {
                    "state": "Not Pushed"
                  }
                },
                {
                  "apiVersion": "odo.dev/v1alpha1",
                  "kind": "url",
                  "metadata": {
                    "creationTimestamp": null,
                    "name": "url-2"
                  },
                  "spec": {
                    "kind": "route",
                    "port": 8080,
                    "secure": false
                  },
                  "status": {
                    "state": "Not Pushed"
                  }
                }
              ],
              "kind": "List",
              "metadata": {}
            }
          },
          "status": {
            "state": "Not Pushed"
          }
        }

    first mismatched key: "spec"."urls"."items"[0]."spec"

    C:/Users/Admin/go/src/github.com/openshift/odo/tests/integration/component.go:254

[Fail] odo component command tests Creating component [It] should describe the component when it is not pushed
C:/Users/Admin/go/src/github.com/openshift/odo/tests/integration/component.go:254

Running on windows 3.11 cluster PSI.

Even if this doesn't fix  #3499 using jsonmarch it is still the right thing to do.
/approve

Even if this doesn't fix #3499 using jsonmarch it is still the right thing to do.
/approve

Ok, then its better to change all the occurence in our test suite. @girishramnani Can you please update the description field accordingly so that it won't close the actual issue.

@prietyc123 yes I have changed all the necessary occurrences

/hold cancel

/kind failing-test
/kind area/Windows

@girishramnani It seems a code refactoring pr. Can you please update this also.

Done

/lgtm

/retest

/retest


Unable to select dates before today in Ionic 6

Ionic version:  (check one with "x")
[ ] 2.x
[ ] 3.x
[ ] 4.x
Ion2-calendar mode:  (check one with "x")
[ ] components mode
[ ] modal mode
I'm submitting a ...  (check one with "x")
[ ] bug report
[ ] feature request
[ ] help me
Current behavior:

Expected behavior:
Allow user select days starting from defined date in options value
Steps to reproduce:
I added ion2-calendar to an Ionic 6 project, but cannot make it select a date before the current date. Setting from to new Date('01/01/1970') does nothing, and just disables selecting any day at all. Is this library compatible with Ionic 6?
Related code:
options: CalendarComponentOptions = {
    from: new Date('01/01/1970'),
};

ngOnInit() {
    if(this.rangeType !== 'day') {
      this.options.pickMode = 'range';
    }
  }

``

**Other information:**

**Ionic info:** (run `ionic info` from a terminal/cmd prompt and paste output below):

Ionic:
Ionic CLI                     : 6.19.1 (C:\Users\robot\AppData\Roaming\npm\node_modules@ionic\cli)
Ionic Framework               : @ionic/angular 6.1.8
@angular-devkit/build-angular : 13.2.6
@angular-devkit/schematics    : 13.2.6
@angular/cli                  : 13.2.6
@ionic/angular-toolkit        : 6.1.0
Capacitor:
Capacitor CLI      : 3.5.1
@capacitor/android : 3.5.1
@capacitor/core    : 3.5.1
@capacitor/ios     : not installed
Utility:
cordova-res : not installed globally
native-run  : 1.6.0
System:
NodeJS : v16.15.0 (C:\Program Files\nodejs\node.exe)
npm    : 8.5.5
OS     : Windows 10```
Screenshot:

Hello, I have the same problem, were you able to solve it?

I found it is working for Ionic 6. You just need to set the to: date to be a future date. For example:
this.options = {
color: 'secondary',
from: new Date(2021, 0, 1),   // days click enabled from;
to: new Date(2024, 8, 15),    // days click enabled to;
showMonthPicker: false,
daysConfig: _daysConfig,
};

I took this approach to get it working:
options: CalendarModalOptions = {
    pickMode: 'multi',
    showMonthPicker: true,
    from: moment().add(-1,'year').toDate(),
    to: moment().add(1,'year').toDate()
};

I found that the "minimum" from date is 1971
  const options: CalendarModalOptions = {
      title: '',
      from: new Date(1971, 0, 1),
      to: 0,
      defaultDate: new Date(),
   };

If you set before 1971 it will show all elements as a disabled
  const options: CalendarModalOptions = {
      title: '',
      from: new Date(1970, 0, 1),
      to: 0,
      defaultDate: new Date(),
   };

Unfortunately this repository was abandoned, to solve my problems with dates before 1970 and updates, I released a new version with corrections and new features.
https://www.npmjs.com/package/@heliomarpm/ion-calendar


Stub in a place for documents related to Spiritual Nurture groups on the M&C section

Jessica's message:

Dear Morningsiders,

Pam Wood asked if I’d send an email to you about forming a spiritual nurturance group. I wonder if we can figure out a time to meet virtually in the next week or two to discuss how we’d like to gather and when?

If you’d each send me some days/times that work generally, and any blackout dates/times, I’ll follow up with a calendar doodle to everyone with some suggestions.

Pam also said that gathering these spiritual nurturance groups, like most things Morningside, is collectively driven and self-organized. In that spirit, I’d like to share with you materials that she sent to me. If we all understand the scaffolding, we can all better decide how we’d like to proceed.

Here is the folder with the documents Pam shared. She may have some more coming:  http://bit.ly/spiritualnurturance

I’ll gather this first meeting and let’s see what happens next. I’m excited to meet you all, if virtually for the time being.


Add RIB_STROKE constant (default salmon) for VWS rib color

Makes the color of ribs salmon

Actually, I decided it would be better to have it have an alpha, so overlapping ones are obvious, and also I changed the render order.

Please review/rebase+merge if happy @MatthewBlanchard
This isn't totally kosher Git-wise, technically I should've made a new PR, but I also added a Makefile change lol
You can now
make testrun TESTFILE=imlym2.glif


AnrPlugin.kt:-2 - com.bugsnag.android.AnrPlugin.enableAnrReporting

Describe the bug
enableAnrReporting(true) triggers the following Error in Production at the following line.
java.lang.UnsatisfiedLinkError: No implementation found for void com.bugsnag.android.AnrPlugin.enableAnrReporting(boolean) (tried Java_com_bugsnag_android_AnrPlugin_enableAnrReporting and Java_com_bugsnag_android_AnrPlugin_enableAnrReporting__Z)

Environment
The error was experienced on the following environment, we are upgrading the denpency and we will update this issue:

Bugsnag version<EMAIL_ADDRESS>Browser framework version (if any):

React<EMAIL_ADDRESS><EMAIL_ADDRESS>

Device (e.g. iphonex): Pixel 3a API 28

Example Repo

[ ] Create a minimal repository that can reproduce the issue
[ ] Link to it here:

Error messages:

Hi @fabriziobertoglio1987.
I believe this this error will be thrown due to the android native library loader being somewhat unreliable in certain conditions. You can try using Relinker to manually load the library before calling Bugsnag.start(). Instructions on how to do that can be found here:  https://docs.bugsnag.com/platforms/android/faq/#what-are-anrlinkerror-and-ndklinkerrors

Hi @fabriziobertoglio1987.
I believe this this error will be thrown due to the android native library loader being somewhat unreliable in certain conditions. You can try using Relinker to manually load the library before calling Bugsnag.start(). Instructions on how to do that can be found here:  https://docs.bugsnag.com/platforms/android/faq/#what-are-anrlinkerror-and-ndklinkerrors


Bug: issues on brave (in Linux)

Paul Johnson
I would use it over Seven JSON Viewer, but it is currently broken (I am using Brave on Linux)
Quick fix for me was to add .line { line-height: 18px; }.

seems to work fine on my brave in kali linux


[paymentservice] [checkoutservice] introduce new featureflags

Changes
This PR is an updated version of #1383 to conform to the updated feature flags. Also a comment regarding the paymentServiceUnreachable feature flag was addressed by moving the feature flag to the checkout-service.
Merge Requirements
For new features contributions please make sure you have completed the following
essential items:

[x] CHANGELOG.md updated to document new feature additions
[x] Appropriate documentation updates in the docs
[ ] Appropriate Helm chart updates in the helm-charts

Maintainers will not merge until the above have been completed. If you're unsure
which docs need to be changed ping the
@open-telemetry/demo-approvers.

Hello, as stated above this PR is the updated version of #1383. Sadly it seems like the helm chart is still outdated and I do not see any open PRs addressing that. Can you tell me what the status is there?

Hello, as stated above this PR is the updated version of #1383. Sadly it seems like the helm chart is still outdated and I do not see any open PRs addressing that. Can you tell me what the status is there?

Excelent question!
I'll take a look into it.

Hello, as stated above this PR is the updated version of #1383. Sadly it seems like the helm chart is still outdated and I do not see any open PRs addressing that. Can you tell me what the status is there?

There you go: https://github.com/open-telemetry/opentelemetry-helm-charts/pull/1082

There you go: open-telemetry/opentelemetry-helm-charts#1082

@julianocosta89, thanks a lot for the info, as soon as this PR is merged I will make the changes to the helm chart.
Also, do you perchance know why the tracetesting check is failing? I am asking because I made sure to check that it passes locally (see image). Would appreciate your insights.

Also, do you perchance know why the tracetesting check is failing? I am asking because I made sure to check that it passes locally (see image). Would appreciate your insights.

Testing out your PR, I did see the failing test.
It seems that the folks from TraceTest changed the name of the trigger and the test wasn't found.
Not related to your PR, but since the update of traceTest you are the first one to touch checkoutService.
I added the fix to your PR, hope you don't mind.


panel reparent error and blank container

Found 2 minor issues, I think they were not reported yet.
When performing a reparent of the FileSystem panel the terminal shows some errors. Also there is a empty container when opening "old" projects.
Screen-shoot attached for better clarification.

See #2349 for the second bug.
Is the first bug still valid in the current master branch? Please also make sure to open one issue per bug next time, it makes tracking each bug easier :)

Yes, it does happen on current master. The empty container also appear after the reparent.

The second issue has been fixed in #2349.

@akien-mga sry, next time I will create one issue per bug.

No problem, in the end it looks like some contributors found how to address both bugs :)

i can't reproduce either of them, so it seems like it's closed


Dot Indicator using Snap Helper

Hi,
Can I create UI like this using Snap Helper?

That should be a custom view instead.


failing test: chain-method-continuation fail for fully qualified call

Just found an issue with chain-method-continuation, raising a PR with the repro only for now.
Happy to work on the fix if someone points me in the right direction.
Repro for https://github.com/pinterest/ktlint/issues/2797

Please see docs for configuration of the rule. Expression will be wrapped when the configured number of operators is reached. In case you do not want that, please set it to some high number (Integer.MAX for example).
So there is no need for fixing this.

https://github.com/pinterest/ktlint/commit/9a10ec09f1cf6d58d5c70b03e57a1b69cd75191f supersedes this.


Custom resources do not support StrategicMerge patch type

In these commits:
https://github.com/kbst/terraform-provider-kustomize/commit/212c7834bbc091dcfedb73f26cb388cc4bbc9e62
https://github.com/kbst/terraform-provider-kustomize/commit/5a22486341544fb966693a49ddcb71121efaaf50
the patch type was changed to StrategicMergePatchType, however this patch type is not supported for custom resources:
https://github.com/kubernetes/kubernetes/issues/71024
Despite the above comment being from 2018 I am getting similar errors on stable GKE:
Error: ResourceDiff: ServiceMonitor prometheus-operator prometheus-op-kube-dns the body of the request was in an unknown format - accepted media types include: application/json-patch+json, application/merge-patch+json, application/apply-patch+yaml

I suppose an option could be to try a StrategicMerge and if that is denied fall back to the behavior before the mentioned commit.


[SPARK-47862][PYTHON][CONNECT]Fix generation of proto files

What changes were proposed in this pull request?
When Spark Connect generates the protobuf files, we move them to the correct folder and adjust the package imports. However, we did not properly adjust the module name of the serialized descriptor. This in turn breaks serialization of the descriptors using Cloudpickle.
The default __reduce__ method of the generated proto message uses the descriptor module and the serialize to string method to generate a proper binary representation. However, since the module was previously wrongly encoded, serialization would fail
Why are the changes needed?
Compatibility
Does this PR introduce any user-facing change?
No
How was this patch tested?
Manual
Was this patch authored or co-authored using generative AI tooling?
No

Merged to master.


Added speech to text capability

Verify your system default microphone is the one you're testing with, as that's the primary limitation of this initial text to speech implementation for voice prompting.

Awesome! Once we settle in on some provider work this is on my radar for when we've got room for feature adds. 👍

I actually pulled it and merged with provider work.
There are conflicts but minimal ones, it can go in parallel.
Tested here and seems to work.
There is one thing I would fix before merging
https://www.youtube.com/watch?v=3Gc0yOgx-EQ
When user submits we should clean out ongoing text so that when he speaks next time its new text.
There are some other potential UX changes.
I would love to play with allowing it to do commands.
Aka "stop/start/submit" so I can control it with my voice only.
Use "Hello Google/Alexa" style wake up and go to sleep commands?
Ugh so exciting, thanks for your great work @navyseal4000

Ooh, I started working on #281 before this was created.

@wonderwhy-er  Can we combine the two so it's not time wasted?
Maybe use your when available and mine when the browser doesn't support this.

Oof, I started working on #281 before this was created.

that is why I am for posting PRs early in draft mode for early feedback.
I shared in the group that my policy is to review ones who added PR earlier first.

Won't have time this morning to get the enhancements done, I'll try to get to them later tonight

In fact if you'd like, feel free to finish this @milutinke and if you can, feel free to take the author role. Just lmk if you do so we don't both work on it tonight

In fact if you'd like, feel free to finish this @milutinke and if you can, feel free to take the author role. Just lmk if you do so we don't both work on it tonight

I had quite a busy day, sorry for the late reply, I won't have the time to do anything at least up to 22. of November.
Wrote a proposal to Eduard in my PR, waiting for his reply, but I'd say you can finish this, and if he agrees, I would pull your changes and then add my option as the fallback. Great job btw.

Voice support is an awesome feature to support, I’m really biased toward it from a human computer interface perspective so just full disclosure.
If we can all work together towards integration of this and #281 I am more than happy to help out where I can. Cheers!

I am pretty excited for this feature and already tested @milutinke solution that it works pretty well with one exception.
I am honestly willing to merge this and then add those improvements as separate PRs so that ball is rolling.
May be will get to this in the evening

@wonderwhy-er Ready for retesting. I got the fix working, but not the additional features with voice mode yet. Adding "enhance voice mode" as a goal in the readme might be a good idea, but I'll leave that determination up to you.

@wonderwhy-er Regarding the discussion in the #281, we can get this merged first, since @navyseal4000 continued working on it.
Then I would add the https://huggingface.co/spaces/Xenova/whisper-web as the fallback.

Looking at it :)

Just took a look, I see you are stopping microphone on submit now.
I guess that is fine too, I do want to add "non stop audio mode" later :)
I was away from computer for this weekend.
So could not test.
I am ready to merge, but we need to resolve conflict first.


Add Putra Project portfolio draft 1 and test cases

Also annotated @@author relevantly

Codecov Report

Merging #141 into master will increase coverage by 1.22%.
The diff coverage is 40%.

@@             Coverage Diff             @@
##             master    #141      +/-   ##
===========================================
+ Coverage     35.48%   36.7%   +1.22%
- Complexity      233     249      +16
===========================================
  Files            62      62
  Lines          1657    1659       +2
  Branches        183     183
===========================================
+ Hits            588     609      +21
+ Misses         1028    1012      -16
+ Partials         41      38       -3

Impacted Files
Coverage Δ
Complexity Δ

...du/addressbook/commands/UpdatePasswordCommand.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

src/seedu/addressbook/commands/HelpCommand.java
100% <ø> (ø)
3 <0> (ø)
:arrow_down:

...eedu/addressbook/readandwrite/ReaderAndWriter.java
55.55% <ø> (ø)
3 <0> (ø)
:arrow_down:

src/seedu/addressbook/timeanddate/TimeAndDate.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

src/seedu/addressbook/commands/LockCommand.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

src/seedu/addressbook/ui/MainWindow.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

src/seedu/addressbook/password/Password.java
27.93% <50%> (+7.09%)
39 <2> (+16)
: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 13fb183...d6ba1b3. Read the comment docs.


Provide an updated release

There's been a lot of changes to the SDK since the last release, v0.4.6, in April.
If there was a more recent release available, developers could import the latest SDK using Maven/Gradle the way this documentation currently describes: https://docs.hedera.com/reference#import-sdk

Thank you for the ping. The new release will be out today or tomorrow.

This is now done - https://github.com/hashgraph/hedera-sdk-java#maven


Lint option: Highlighting copies

It would be nice to have a lint feature that, when enabled, will highlight all instances where a variable is copied. This would be useful because it's not always clear when a copy would occur, and highlighting copies could point out areas where code compiles correctly, but could be written better.
For example:
#[derive(Debug, Clone, Copy)]
struct Test {
    num: [u8; 20],
}

fn func(_: Test) {
    // ...
}

fn main() {
    let t = Test{
        num:[0;20],
    };
    let t2 = t.clone();
    func(t);
    println!("{:?}", t2);
}

In this case, the author of the code is unaware that Test implements Copy, so they clone t to pass to func() in order to keep using t after they assume it was moved. When highlighting is enabled, the t in func(t) would be highlighted which would provide a visual indicator that the clone is unnecessary, as t will be copied instead of moved when passed to func.

Note that clippy gives you a lint for this as well
https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=95f05e8d9bf217e265f51094e192110b
warning: using `clone` on type `Test` which implements the `Copy` trait

Note that clippy gives you a lint for this as well
https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=95f05e8d9bf217e265f51094e192110b
warning: using `clone` on type `Test` which implements the `Copy` trait

Depending on how it's implemented, it might also be worth adding a sub-option to disable highlighting for primitive types, since most people would already reason that primitive types implement Copy and would find the extra highlighting for them to be unneeded noise.

Depending on how it's implemented, it might also be worth adding a sub-option to disable highlighting for primitive types, since most people would already reason that primitive types implement Copy and would find the extra highlighting for them to be unneeded noise.

I don't think this is currently really actionable, since it requires move analysis to do properly.

I don't think this is currently really actionable, since it requires move analysis to do properly.


An error occurred while using the Python magic library at Docker & Github Action. "E ModuleNotFoundError: No module named 'magic'"

🐛 Issue Description:
Running a Python project using the python-magic library within a Docker container on Windows 10 OS results in the error "Module magic not found."
🔧 Proposed Fix:
Initially, changing the dependency from python-magic to python-magic-bin resolved the issue in the local environment. However, when running the project in a Docker container, the same error resurfaced unexpectedly.
🐋 Dockerfile Content:
# Dockerfile for API service
FROM python:3.11.0 as base

# Dependencies installations
RUN apt-get update && apt-get install -y \
    poppler-utils \
    tesseract-ocr \
    libgl1-mesa-glx \
    libmagic1 \
    python3-magic

# Non-root user setup
RUN groupadd --gid 1000 user && adduser --disabled-password --gecos '' --uid 1000 --gid 1000 user
WORKDIR /home/user
USER user

# Development stage setup
FROM base as dev
USER root
COPY --chown=user:user ./requirements.txt ./
RUN pip install --no-cache-dir -r requirements.txt
COPY --chown=user:user ./src /home/user/src
COPY --chown=user:user ./test /home/user/test
COPY --chown=user:user .env /home/user/.env
USER user
CMD ["python", "-m", "uvicorn", "src.main:app", "--host", "<IP_ADDRESS>", "--port", "5000", "--reload", "--env-file", "/home/user/.env"]

# Test stage setup
FROM base as test
COPY --chown=user:user ./requirements.txt ./
RUN pip install --no-cache-dir -r requirements.txt
USER root
COPY --chown=user:user ./src /home/user/src
COPY --chown=user:user ./test /home/user/test
RUN mkdir /home/user/.mypy_cache && chown user:user -R /home/user/.mypy_cache
RUN pip install pytest
CMD ["pytest"]
USER user

# Default target stage
FROM dev

🤔 Current Challenge:
The error "Module magic not found" persists when running the project in a Docker container despite changing the library dependency. Seeking insights or suggestions to overcome this issue. Your thoughts? 👀
Regards 🚀

If you apt-get install any Python program in this image, you will get a second copy of Python installed from the distribution.  If you want to use our image and need modules like magic, you'll need to pip install, etc them instead.

Solution Implemented:
After encountering the "Module magic not found" error in the Docker container, I devised a solution by creating separate requirements.txt files for Windows and Linux versions of the project. The Linux version requires python-magic, while the Windows version necessitates python-magic-bin.
🐳 Dockerfile With Updated Configuration:
# Dockerfile for API service
FROM python:3.11.0 as base

# Define build arguments
ARG PROJECT=src
ARG TEST=test

# Install dependencies
RUN apt-get update && apt-get install -y \
    poppler-utils \
    tesseract-ocr \
    libgl1-mesa-glx \
    libmagic1 \
    python3-magic

# Create a non-root user
RUN groupadd --gid 1000 user && adduser --disabled-password --gecos '' --uid 1000 --gid 1000 user

WORKDIR /home/user
USER user

# Development stage setup
FROM base as dev

USER root
COPY --chown=user:user ./requirements-linux.txt ./
RUN pip install --no-cache-dir -r requirements-linux.txt
COPY --chown=user:user ./$PROJECT /home/user/$PROJECT
COPY --chown=user:user ./$TEST /home/user/$TEST
COPY --chown=user:user .env /home/user/.env
USER user
CMD ["python", "-m", "uvicorn", "src.main:app", "--host", "<IP_ADDRESS>", "--port", "5000", "--reload", "--env-file", "/home/user/.env"]

# Test stage setup
FROM base as test

COPY --chown=user:user ./requirements-linux.txt ./
RUN pip install --no-cache-dir -r requirements-linux.txt
COPY --chown=user:user ./$PROJECT /home/user/$PROJECT
COPY --chown=user:user ./$TEST /home/user/$TEST
RUN mkdir /home/user/.mypy_cache && chown user:user -R /home/user/.mypy_cache
RUN pip install pytest
CMD ["pytest"]
USER user

# Set the default target stage to 'dev'
FROM dev

🚀 Outcome:
By segregating the requirements between Windows and Linux versions and updating the Dockerfile correspondingly, the project now runs smoothly without the "Module magic not found" error in the Docker container.

I will reiterate again that you do not want to apt-get install any python* APT packages with this Docker image.  You either want to switch to using Debian directly (FROM debian:bookworm) and installing those from Debian, or switch to using "upstream" methods like pip for installing Python dependencies to keep using this image.


Victor VosMottor: Watch ketorpoavis

Victor VosMottor requests the watch of the watch_keyword ketorpoavis. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

ketorpoavis has been seen in 0 true positives, 0 false positives, and 0 NAAs.

This appears to be a typo.


Fresh Windows 11 x64 install MSVCR100.DLL missing program will not load

yt-dlp works as expected
yt-dlp --version
2022.11.11
youtube-dl --version  reports MSVCR100.DLL missing
tried 2012 and 2015 vcredist,exe without success
app runs on windows 10
youtube-dl --version
2021.12.17
WRITE DESCRIPTION HERE
I can't post a log as it doesn't execute

Read the manual, and also https://github.com/ytdl-org/youtube-dl/issues/30143#issuecomment-1022686470.
Duplicate of #10874.


How to work with chrono? migrate 18.2 -> 22.2

Hey there,
sorry for the probably dump question. I want to update my dependencies and don't know how to use the library with chrono anymore. The examples and docs is quite limited here.
My code looks like this
let query = r#"
    SELECT id, activationCode, createdAt
    FROM user
    WHERE id = ?
"#;

get_connection()
    .exec_first::<(i64, Option<String>, Option<NaiveDateTime>), _, _>(query, (user_id,))
    .map_err(server_error!("Sql query failed to get user"))
    .unwrap_or(None)
    .map(|(id, activation_code, created_at)| User {
        id,
        activated: activation_code.unwrap_or("0".to_owned()) == "0",
        created_at: premium_until.map(|date| DateTime::from_utc(date, Utc)),
    })

In version 18.2 chrono feature were still part of the mysql crate and this code worked. With the new version I added mysql_common and enabled chrono feature but the NaiveDateTime doesn't seem to implement anymore the FromRow trait.
error[E0277]: the trait bound `(i64, std::option::Option<std::string::String>, std::option::Option<NaiveDateTime>): mysql::prelude::FromRow` is not satisfied
   --> db/src/model/user.rs:24:14
    |
24  |             .exec_first::<(i64, Option<String>, Option<NaiveDateTime>), _, _>(query, (user_id,))
    |              ^^^^^^^^^^ the trait `mysql::prelude::FromRow` is not implemented for `(i64, std::option::Option<std::string::String>, std::option::Option<NaiveDateTime>)`

mysql = "22.2.0"
mysql_common = { version = "0.29.0", features = ["chrono"] }

Is there a new way to query data? I'm missing a bit of examples here. Thanks for your work and your help :)

Hi.

Is there a new way to query data? I'm missing a bit of examples here.

Please note, that mysql v22.2.0 is not yet updated to mysql_common v0.29.0. This means that you need to change your Cargo.toml to this:
mysql = "22.2.0"
mysql_common = { version = "0.28.2", features = ["chrono"] }

seem to have solved it, dump me. May you could add to the documentation / readme that mysql_common has to be used and which version it should be :)


Broken Sveltekit on master

Describe the bug
The SvelteKit build and tests on master are failing.
Your Example Website or App
https://github.com/dotansimha/graphql-yoga
Steps to Reproduce the Bug or Issue
Run tests on https://github.com/dotansimha/graphql-yoga
Expected behavior
Tests should pass :)
Screenshots or Videos
No response
Platform

GitHub Actions

Additional context
When I run yarn test locally SvelteKit tests always fail, because I have to run some manual steps. Instead the test file/suite should spawn the SvelteKit process.
The svelte command fails locally with the following command:

  SvelteKit v1.0.0-next.348

  local:   http://localhost:3007
  network: not exposed

  Use --host to expose server to other devices on this network

TypeError: handler is not a function
    at render_endpoint (file:///Users/laurinquast/Projects/graphql-yoga/examples/sveltekit/.svelte-kit/output/server/index.js:179:26)
    at resolve (file:///Users/laurinquast/Projects/graphql-yoga/examples/sveltekit/.svelte-kit/output/server/index.js:2155:59)
    at async respond (file:///Users/laurinquast/Projects/graphql-yoga/examples/sveltekit/.svelte-kit/output/server/index.js:2111:22)
    at async file:///Users/laurinquast/Projects/graphql-yoga/node_modules/@sveltejs/kit/dist/chunks/index4.js:166:5

I think this has been fixed, no?


[WIP] 2nd batch of require work: require_relative all the things

Part 2 of #11244
In this episode we:

Fixed up supply
Wrote a helper that, for each tool, gives a helper from_tool that returns the relative path from the file it is being called from to that tool
Wrote a custom cop for fastlane that does require 'tool/module' -> require_relative from_tool/'module'
Ran that thing on all of fastlane

TODO:

[ ] Appease the Style/SpacesAroundOperators cop because require_relative from_fastlane/'runner' looks better than require_relative from_fastlane / 'runner'
[ ] Reenable Require/MissingRequireStatement once I figure out how to make this work with that

I have no idea what happened here... I'll just close and reopen this one.

Uh @milch, was this ever reopened or completely abandoned?

Hmm, I remember reopening at some point, but never merging it due to ... issues ...
In any case, I'm now clear to pick this up again. I'll take a look this weekend!

As I'm experimenting with performance optimization stuff right now I rebased your branch onto master, went through the merge conflicts and created a new PR to see if it actually succeeds in tests: https://github.com/fastlane/fastlane/pull/13458 It does not, and I also left several comment of missing or additional requires.


Change build environment to JDK8

Use JDK8 for build but still support Java 6 and 7. Depends on JavaDoc compatibility with Java 8 #39 and requires to have a test project in order to ensure lettuce usage on JDK6/7/8

Created test container project (https://github.com/mp911de/lettuce-testcontainer) for lettuce in order to verify compatibility with java 6/7/8


Email post script text

Find out if and how this text needs to change at the end of the email

This will not be included in the email.


Causeable Interface

It would be nice if there was a Causable interface, or something of a similar name, that contained a default asCause() method that wrapped the current object in a Cause. Classes such as Entity could implement it and plugin authors could use it on their main plugin classes, or any other class they use as a cause. It would improve clarity as classes marked as Causable are clearly intended to be used as a Cause, and would also make current code more concise.
Cause.of(NamedCause.source(getPlugin()));
vs.
getPlugin().asCause();

If it sounds like a good idea I'd be happy to submit a PR.

Doing this as per your example you lose the "names" part of the cause.

@ryantheleach It would be easy to provide overloaded methods to support more functionality.
	default Cause asCause() {
		return asCause(NamedCause.SOURCE);
	}

	default Cause asCause(String name) {
		return Cause.of(NamedCause.of(name, this));
	}

Could you clarify what the point of it is? None of the methods that currently use Causes are meant to have single objects within the Cause...

Originally I thought this would be useful as just the root of the cause, but with more causes its impact becomes less significant.
Cause.of(NamedCause.of("root", getPlugin()), NamedCause.of("second", second), NamedCause.of("third", third));
vs.
getPlugin().asCause(NamedCause.of("second", second), NamedCause.of("third", third));

So I'm not really sure its worth it anymore. as the relative amount of code saved decreases the longer the cause chain is.

I feel like people also forget that the Cause.Builder literally provides easier methods to avoid having to make NamedCauses every time:
Cause.source(getPlugin()).named("second", second).named("third", third).build();

Did not realize that sorry, closing the issue.


Node red crashes when not selecting a meter in the "Meter" and "Production Meter" section of the "DiscovergyMeter" node

Thank you for updating the module and fixing the "node red crashes when configuration is not complete" issue. However, I'm experiencing also "node red crashing" issues with the DiscovergyMeter node when not selecting a meter in the "Meter" and "Production Meter" node.
When I add the node and select only one combobox entry (i.e. "Meter") and deploy the node, node red crashes. It looks like there should be some additional checks to prevent this. The same happens when I have not yet configured the discovergy account though I can live with that.
Keep up the great work and sorry for not answering your last question but I'm really busy.

solved after #73


ASB lock renewal per topic

Description
This PR does the following:

Handles best effort lock renewal on a per subscription basis
Updates ASB sdk version
Refactors subscription logic out of ASB namespace and entity management
Demotes lock renewal error to warning (this will happen but is expected)
Tracks async handler cancelFunc to invoke on close
Handle connection recovery

Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #364
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[ ] Created/updated tests
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

@yaron2 few things I'm unsure on here:

We currently don't propagate a context in the publish func. Should we do this so we can properly timeout the app handler and do graceful cleanup of async calls.
We also don't currently have a pattern for restarting a subscription to a topic in the case of fatal errors i.e. server kills the connection due to a property update or topic/subscription being deleted for instance. In this current build, the subscription is cleaned up and then stops. How do you think we should handle this?

@youngbupark any thoughts on the above questions?

@yaron2 few things I'm unsure on here:

We currently don't propagate a context in the publish func. Should we do this so we can properly timeout the app handler and do graceful cleanup of async calls.

You can find many parts which we are not populating context. While working on service invocation, we populated context in the service invocation call flow, but not the others. I would create the separate work item to populate context.

We also don't currently have a pattern for restarting a subscription to a topic in the case of fatal errors i.e. server kills the connection due to a property update or topic/subscription being deleted for instance. In this current build, the error is logged, the subscription is cleaned up (although async calls currently can't be cancelled, see issue 1.) and then dapr continues but since the connection is closed no more messages will be received. How do you think we should actually handle this?

Good points. One of users filed the issue to reconnect dependency if it is disconnected or reconnected. not all client supports reconnection. So we need to consider to review each component behavior for this cases and improve it. I think conformance tests should test this negative scenario. (cc/ @mukundansundar)
I would track this problem as a separate issue.
cc/ @orizohar @amanbha @msfussell @yolember

@yaron2 please review and test. https://github.com/dapr/docs/pull/642 is the associated docs update.

Found an edge case that stops the message processing from functioning correctly once recovering from multiple connection errors. Investigating at the moment.

I've raised an issue on the underlying SDK for the above: https://github.com/Azure/azure-service-bus-go/issues/173
I'll try to see if I can fix this later this week.

@yaron2 looks like the change downstream in azure-service-bus-go requires a change in go-amqp which could have a fairly big impact on existing users so might be slow to integrate. I'll back out my hack for now and leave the original issue in. We can merge this PR and open a new issue for the specific edge case. Seem reasonable?

Yes


Proposal Date
2023-12-19
Target Ticket Acceptance Date
2023-01-10
Earliest Open edX Named Release Without This Functionality
Redwood 2023-04
Rationale
Codecov does not work OOTB for most repositories created using this cookiecutter and most people remove it once their repository has been created. There are known alternatives that do not require additional steps for setup.
Removal
https://github.com/openedx/edx-cookiecutters/blob/8180c89864d9d596e57c0bec8fe4ac8daedd7081/cookiecutter-xblock/{{cookiecutter.repo_name}}/.github/workflows/ci.yml#L39
https://github.com/openedx/edx-cookiecutters/blob/8180c89864d9d596e57c0bec8fe4ac8daedd7081/cookiecutter-django-app/{{cookiecutter.repo_name}}/.github/workflows/ci.yml#L39
Replacement
TBD
Deprecation
Should not be needed
Migration
Should not be needed
Additional Info
No response

I'm fully in favor of removing a dependency on a 3rd party service that doesn't work (and manages to break our builds , too), but enforcing code coverage still strikes me as being as important as it's always been. Rather than totally ripping out the coverage check, could we set it up to enforce some generally-reasonable threshhold by checking the output of the coverage.py? Teams could still lower the threshhold or rip it out, but at least they'd be start out with a reasonable default coverage check.

Updated description with a possible alternative: https://github.com/py-cov-action/python-coverage-comment-action

I'd really like this to get someone's attention, because the failing uploads that breaks PRs is a frustration that many people are probably feeling. I guess we have scripts where we might be able to quantify. I think this issue deserves a shorter term solution, which either means someone [Axim? Community? Arch-BOM?] picking up this work so the long term is now, or implementing a retry or some other purely short term solution. Thoughts?

As I understand it:

This is an issue for people creating new repos. Existing repo are already working around it, either by using something else or by disabling coverage-checking altogether.
The short-term solution would be to simply remove codecov from the cookiecutter.
The medium-term solution would be to either:

make codecov work OOTB in the cookiecutter,
replace it with something else in the cookiecutter.

The long-term solution would be to go back through the existing repos and apply the medium-term solution, with the end-goal of having the same coverage tool running on all Python repos.

Given that this only affects new repositories, my inclination is that it's not high-priority for Axim. Right now, our most acute challenge is ensuring a state of good maintenance for all Core Product repositories, which is already an overwhelming list.

@kdmccormick: I see. I didn't realize this issue was in edx-cookiecutters, and I was really asking about existing repos, like openedx-events where I saw a recent codecov upload failure.

Existing repo are already working around it, either by using something else or by disabling coverage-checking altogether.

So I guess for openedx-events, the options is to disable the check altogether, or use something else? Is there an example of the something else? This ticket lists a hackathon project as a potential replacement, but I'm not sure how far that got. Ideally we would not disable altogether without a replacement. I imagine there must be more repos with this problem.

We actually added documentation to the developer docs on how to set up and use a CodeCov alternative: https://docs.openedx.org/en/latest/developers/how-tos/use-python-coverage-comment.html
2U uses it in one of our private repos and it seems to be working acceptably.

@robrap Ah, I was confused too. I didn't realize that this was an active issue for existing repos.
Those docs look great @dianakhuang ! Would you both agree that:

As a short-term unblocker for affected repos, let's circulate that document around.
For the medium-term fix, the cookiecutter should be updated to use python-coverage-comment instead of codecov.
For the long-term fix, we should ticket up the work of moving all Python repos off of codecov.

This has passed the acceptance date, and I think we're all in agreement that we should move off CodeCov at least by default.

Note that the ticket https://github.com/edx/edx-arch-experiments/issues/528 got blocked/abandoned due 2U issues.

openedx-events is attempting to use the replacement here: https://github.com/openedx/openedx-events/pull/323

We don't yet have a good plan for replacing JS coverage, and we need to figure out if we'll use codecov's bundle asset size tooling or if we need a different alternative.


Literature Review

Articles, books, etc.

http://www.sciencedirect.com/science/article/pii/S2212827115004692
My notes:
This is a study conducted from 2011 bike sharing data in Lyon, France, which aims to quantify how the built environment impacts demand at bike sharing docks. The researchers defined built environment through public transportation, socioeconomic, topographic and bike sharing network metrics. I would say most of our variables fall under the ‘topographic’ built environment type that they’ve created.
“The main objective of the current paper is to quantify the influence of built environment factors on arrival and departure flows at bike sharing station level using a statistical linear regression method.”
“The trips data is combined with built environment attributes around station allowing us to examine the influence of these factors on bicycle sharing demand.”
Research has already tried to predict bike sharing flow “using different urban factors such as: population, job, bicycle lanes, proximity to public transport, bike sharing station density, altitude, retail shops, etc.”
“Contributes to the literature by determining the effect of type of subscribers and built environment attributes on bicycle arrival and departure flows at the station level using hourly bike sharing data. The estimated models will allow us to predict not only the demand of bike sharing but also to better understand the influence of built environment to the bike sharing system.”
“The hypothesis we use in this study is that the bike sharing usage of each station depends on the built environment around the station.”
“We decided to keep a 300m buffer zone because the built environment variables are the most significant in the models and a 300 meter buffer zone is an appropriate walking distance between Velo’v stations.”
“The explicative variables used in our analysis can be categorized into five groups: public transport variable, socioeconomic variable, topographic variable, bike sharing network variable, and topographic variable.”
“The number of metro, tramway and railway stations near a Velo’v station were generated to examine the influence of public transit on bike sharing flows.”
“The socio-economic variables included four factors: 1) population, 2) number of jobs, 3) number of students in campus, and 4) number of student residences near a bike sharing station.” There were a lot of students in Lyon during this study, which is why two student variables were selected here.
They considered three types of leisure variables, “1) number of restaurants, 2) number of cinema, and 3) presence of embankment road of Rhone River – the main sportive and leisure zone near a bike sharing station.”
“Railway station is the only public transport variable that is significant in all the models of regression… metro and tramway stations are not significant in all the models.”
“The results show also that student is an important bike sharing user. We have used two variables: the number of students on campus and the number of student residences… Bike sharing seems to be a mode of transportation well adopted by student thanks to the cheap price of subscription.”
“The variables of bike sharing network such as: bike sharing network density and capacity of station play important role in the generation of bike sharing flows. The variables are positively significant in all models. It means that the increase of number of stations and the increase of station capacity have positive impact on the bike sharing flows.”
“We observe that the bike sharing usage of long term subscribers seem not to be influenced by the leisure variables. The number of restaurants, the number of cinemas and the embankment road are not significant in any models of long term bike sharing usage. On the other hand, the bike sharing usage of short term subscribers can be described by two words: occasional and leisure.”


Add QA-related scripts into separate subdirectory

Currently all QA-related scripts (check-bashscripts.sh, check-docstyle.sh) are stored in the repo's root directory. It might be worth to move it into separate subdirectory to cleanup the content a bit.

Implemented in https://github.com/fabric8-analytics/fabric8-analytics-jenkins-plugin/pull/35


UNABLE to add Let's Encrypt Certificate for my domain website

Below is the error when want to add in
error: subprocess-exited-with-error
× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> [122 lines of output]
Collecting setuptools!=60.9.0,>=40.6.0
Using cached setuptools-63.4.2-py3-none-any.whl (1.2 MB)
Collecting wheel
Using cached wheel-0.37.1-py2.py3-none-any.whl (35 kB)
Collecting cffi>=1.12
Using cached cffi-1.15.1.tar.gz (508 kB)
Preparing metadata (setup.py): started
Preparing metadata (setup.py): finished with status 'done'
Collecting setuptools-rust>=0.11.4
Using cached setuptools_rust-1.4.1-py3-none-any.whl (23 kB)
Collecting pycparser
Using cached pycparser-2.21-py2.py3-none-any.whl (118 kB)
Collecting typing-extensions>=<IP_ADDRESS>
Using cached typing_extensions-4.3.0-py3-none-any.whl (25 kB)
Collecting semantic-version<3,>=2.8.2
Using cached semantic_version-2.10.0-py2.py3-none-any.whl (15 kB)
Building wheels for collected packages: cffi
Building wheel for cffi (setup.py): started
Building wheel for cffi (setup.py): finished with status 'error'
error: subprocess-exited-with-error
    × python setup.py bdist_wheel did not run successfully.
    │ exit code: 1
    ╰─> [36 lines of output]
        running bdist_wheel
        running build
        running build_py
        creating build
        creating build/lib.linux-armv7l-3.7
        creating build/lib.linux-armv7l-3.7/cffi
        copying cffi/model.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/recompiler.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/verifier.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/vengine_gen.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/__init__.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/cffi_opcode.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/error.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/lock.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/pkgconfig.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/ffiplatform.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/setuptools_ext.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/commontypes.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/vengine_cpy.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/cparser.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/api.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/backend_ctypes.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/_cffi_include.h -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/parse_c_type.h -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/_embedding.h -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/_cffi_errors.h -> build/lib.linux-armv7l-3.7/cffi
        running build_ext
        building '_cffi_backend' extension
        creating build/temp.linux-armv7l-3.7
        creating build/temp.linux-armv7l-3.7/c
        arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -DFFI_BUILDING=1 -DUSE__THREAD -DHAVE_SYNC_SYNCHRONIZE -I/usr/include/ffi -I/usr/include/libffi -I/usr/include/python3.7m -c c/_cffi_backend.c -o build/temp.linux-armv7l-3.7/c/_cffi_backend.o
        c/_cffi_backend.c:2:10: fatal error: Python.h: No such file or directory
         #include
                  ^~~~~~~~~~
        compilation terminated.
        error: command 'arm-linux-gnueabihf-gcc' failed with exit status 1
        [end of output]

    note: This error originates from a subprocess, and is likely not a problem with pip.
    ERROR: Failed building wheel for cffi
    Running setup.py clean for cffi
  Failed to build cffi
  Installing collected packages: wheel, typing-extensions, setuptools, semantic-version, pycparser, setuptools-rust, cffi
    Running setup.py install for cffi: started
    Running setup.py install for cffi: finished with status 'error'
    error: subprocess-exited-with-error

    × Running setup.py install for cffi did not run successfully.
    │ exit code: 1
    ╰─> [36 lines of output]
        running install
        running build
        running build_py
        creating build
        creating build/lib.linux-armv7l-3.7
        creating build/lib.linux-armv7l-3.7/cffi
        copying cffi/model.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/recompiler.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/verifier.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/vengine_gen.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/__init__.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/cffi_opcode.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/error.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/lock.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/pkgconfig.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/ffiplatform.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/setuptools_ext.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/commontypes.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/vengine_cpy.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/cparser.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/api.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/backend_ctypes.py -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/_cffi_include.h -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/parse_c_type.h -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/_embedding.h -> build/lib.linux-armv7l-3.7/cffi
        copying cffi/_cffi_errors.h -> build/lib.linux-armv7l-3.7/cffi
        running build_ext
        building '_cffi_backend' extension
        creating build/temp.linux-armv7l-3.7
        creating build/temp.linux-armv7l-3.7/c
        arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -DFFI_BUILDING=1 -DUSE__THREAD -DHAVE_SYNC_SYNCHRONIZE -I/usr/include/ffi -I/usr/include/libffi -I/usr/include/python3.7m -c c/_cffi_backend.c -o build/temp.linux-armv7l-3.7/c/_cffi_backend.o
        c/_cffi_backend.c:2:10: fatal error: Python.h: No such file or directory
         #include
                  ^~~~~~~~~~
        compilation terminated.
        error: command 'arm-linux-gnueabihf-gcc' failed with exit status 1
        [end of output]

    note: This error originates from a subprocess, and is likely not a problem with pip.
  error: legacy-install-failure

  × Encountered error while trying to install package.
  ╰─> cffi

  note: This is an issue with the package mentioned above, not pip.
  hint: See above for output from the failure.
  WARNING: You are using pip version 22.0.4; however, version 22.2.2 is available.
  You should consider upgrading via the '/usr/bin/python3 -m pip install --upgrade pip' command.
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error
× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
WARNING: You are using pip version 22.0.4; however, version 22.2.2 is available.
You should consider upgrading via the '/usr/bin/python3 -m pip install --upgrade pip' command.
at ChildProcess.exithandler (node:child_process:399:12)
at ChildProcess.emit (node:events:526:28)
at maybeClose (node:internal/child_process:1092:16)
at Socket. (node:internal/child_process:451:11)
at Socket.emit (node:events:526:28)
at Pipe. (node:net:687:12)

this part : WARNING: You are using pip version 22.0.4; however, version 22.2.2 is available. <= my pi server is already installed pip version 22.2.2, i tried to reboot my pi many times still same errors  & i am using latest python 3.10 version

Would like to have a good solution to above errors

Sorry, but are you posting in the right repository?
NginxProxyManager has a webinterface to request and assign SSL certificates.
Which NginxProxyManager version are you running? v2.9.18?
Have you tried adding a certificate via webinterface?
Which option did you try? http-challenge? dns-challenge?

I am using the latest version of nginx proxy manager from jc21 n tried both http challenge n dns challenge also give errors

Sorry, your error reporting here seems off... all dependencies are within the container.
So you shouldnt have issues with the pip on your system itself...
Can you please give all the following info:
Checklist
Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
    Yes / No
Are you sure you're not using someone else's docker image?
    Yes / No
Have you searched for similar issues (both open and closed)?
    Yes / No

Describe the bug
Nginx Proxy Manager Version
To Reproduce Steps to reproduce the behavior:
Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
Screenshots
Operating System
Additional context

Hello, I have the same issue.
Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
    Yes
Are you sure you're not using someone else's docker image?
    Yes
Have you searched for similar issues (both open and closed)?
    Yes

To Reproduce Steps to reproduce the behavior:
Go to 'SSL Certificates'
Click on 'Add SSL Certificate'
Scroll down to 'Let's Encrypt'
Fill necesary data
Select 'Use a DNS Challenge'
See error described in the fitst post

When I do not select 'DNS Challenge' certificates are generated correctly
For a wildcard certificate you need DNS.

I am running latest v2.9.18 without any issues.
Neither DNS challenge for wildcards nor http challenge.
Most likely the DNS challenge settings are wrongly entered, it needs to be ensured that correct api keys etc or whatever is required are used.

Renewing certs on existing domains is currently broken if force SSL is ticked, untick force SSL, save and then update the cert, before tuning force SSL back on, at least until PR #2038 is merged and made live.

I have the exact same problem. is there any update on this?

@rezzorix

Sorry, your error reporting here seems off... all dependencies are within the container.
So you shouldnt have issues with the pip on your system itself...

Sorry, I don't think you should be commenting on this issue.
NPM runs in a container, yes. That container is filled with processes and calls which depend on interlocking dependencies.
That is a very valid error and report. You see the exact same error in a HTML tag, but that doesn't mean it has any less value than a screenshot of the front-end.
I've also seen this error on a Pi 4 and if you care to look at the other issues returning errors for cffi in the Issue tracker you will see similar reporting and errors.

Most likely the DNS challenge settings are wrongly entered

Yes. The single box that says "ENV_VAR=API_KEY" was entered wrong. User error. Of course! /s

For everyone else, you can try this comment after entering the container with docker exec
https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1955#issuecomment-1085817627
apt update
apt-get install build-essential libssl-dev libffi-dev python3-dev cargo
pip install certbot-dns-duckdns~=0.6

@rezzorix

Sorry, your error reporting here seems off... all dependencies are within the container.
So you shouldnt have issues with the pip on your system itself...

Sorry, I don't think you should be commenting on this issue.
NPM runs in a container, yes. That container is filled with processes and calls which depend on interlocking dependencies.
That is a very valid error and report. You see the exact same error in a HTML tag, but that doesn't mean it has any less value than a screenshot of the front-end.
I've also seen this error on a Pi 4 and if you care to look at the other issues returning errors for cffi in the Issue tracker you will see similar reporting and errors.

Most likely the DNS challenge settings are wrongly entered

Yes. The single box that says "ENV_VAR=API_KEY" was entered wrong. User error. Of course! /s
For everyone else, you can try this comment after entering the container with docker exec
#1955 (comment)
apt update
apt-get install build-essential libssl-dev libffi-dev python3-dev cargo
pip install certbot-dns-duckdns~=0.6

Those commands just nuked my instance
note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
[9/22/2022] [12:52:09 PM] [Global   ] › ℹ  info      No valid environment variables for database provided, using default SQLite file '/data/database.sqlite'
[9/22/2022] [12:52:09 PM] [Migrate  ] › ℹ  info      Current database version: none

I'm having this issue as well. I'll wait until I hear back on a solution. But for now, I have to create the certificate on my UDM Pro, and pull them over. At least for now, I'm good until December. :)

Same here, just getting an Internal Error when trying to request a cert from LE.


Update app version to 1.0-alpha01 and refresh app icon

Update app branding and prepare for v1.0 release

Redesign app launcher icon with new background and foreground colors
Add gradient background for improved visual appeal
Implement day/night theme support for launcher icons
Update app version to 1.0-alpha01
Switch to AppCompat theme with proper window background colors

#329  👈
main

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

Join @ksharma-xyz and the rest of your teammates on  Graphite

Merge activity

Nov 9, 1:20 PM EST: A user merged this pull request with Graphite.


Update whole Subutai instead of Subutai P2P on desktop peers.

Expected Behavior

Updating P2P must work correctly on desktop peers
Current Behavior

Updating P2P via CC on desktop peers leads to removal of Subutai which kills this peer.
Possible Solution

Update whole Subutai instead of Subutai P2P on desktop peers. Use subutai update rh.
Steps to Reproduce

Create desktop peer.
Try to update or uninstall P2P via CC
You will end up with broken peer.

The p2p update fixed on the desktop peer.


ext vol feature flag warning not visible in UI if app instances > 1

I tried creating this JSON spec in the UI and received the following error message that doesn't mention the feature flag:
{
  "id": "hello2",
  "cmd": "/usr/bin/tail -f /dev/null",
  "cpus": 0.1,
  "mem": 32,
  "disk": 0,
  "instances": 2,
  "container": {
    "type": "MESOS",
    "volumes": [
      {
        "containerPath": "/tmp/test-rexray-volumehjskdhfksjhfksjhdfskjshdf",
        "external": {
          "name": "jdef-test-vol",
          "provider": "dvdi",
          "options": {
            "dvdi/driver": "rexray"
          }
        },
        "mode": "RW"
      }
    ]
  },
  "upgradeStrategy": {
    "maximumOverCapacity": 0,
    "minimumHealthCapacity": 0
  }
}

error message:
There was a problem with your configuration
general: Number of instances is limited to 1 when declaring DVDI volumes in app [AppDefinition(/hello2,Some(/usr/bin/tail -f /dev/null),None,None,Map(),2,0.1,32.0,0.0,,Set(),List(),List(),List(PortDefinition(0,tcp,None,Map())),false,1 second,1.15,3600 seconds,Some(Container(MESOS,List(ExternalVolume(/tmp/test-rexray-volumehjskdhfksjhfksjhdfskjshdf,ExternalVolumeInfo(None,jdef-test-vol,dvdi,Map(dvdi/driver -> rexray)),RW)),None)),Set(),List(),Set(),UpgradeStrategy(0.0,0.0),Map(),None,None,OnlyVersion(2016-04-13T18:38:26.343Z),None).id]

similarly, if I specify a bogus provider name, I get an error message that doesn't reference the feature flag (and apparently doesn't mention the provider name either):
{
  "id": "hello2",
  "cmd": "/usr/bin/tail -f /dev/null",
  "cpus": 0.1,
  "mem": 32,
  "disk": 0,
  "instances": 1,
  "container": {
    "type": "MESOS",
    "volumes": [
      {
        "containerPath": "/tmp/test-rexray-volumehjskdhfksjhfksjhdfskjshdf",
        "external": {
          "name": "jdef-test-vol",
          "provider": "dvdisdf",
          "options": {
            "dvdi/driver": "rexray"
          }
        },
        "mode": "RW"
      }
    ]
  },
  "upgradeStrategy": {
    "maximumOverCapacity": 0,
    "minimumHealthCapacity": 0
  }
}

error:
There was a problem with your configuration
general: is unknown provider

FWIW, when I perform the same "attempted create" operation via the API using cURL I get multiple error messages, for example:
$ curl -H "Content-type: application/json" -X POST<EMAIL_ADDRESS>http://localhost:8080/v2/apps
{"message":"Object is not valid","details":[{"path":"/container/volumes(0)","errors":["Feature external_volumes is not enabled. Enable with --enable_features external_volumes)"]},{"path":"/","errors":["Number of instances is limited to 1 when declaring DVDI volumes in app [AppDefinition(/hello2,Some(/usr/bin/tail -f /dev/null),None,None,Map(),2,0.1,32.0,0.0,,Set(),List(),List(),List(PortDefinition(0,tcp,None,Map())),false,1 second,1.15,3600 seconds,Some(Container(MESOS,List(ExternalVolume(/tmp/test-rexray-volumehjskdhfksjhfksjhdfskjshdf,ExternalVolumeInfo(None,jdef-test-vol,dvdi,Map(dvdi/driver -> rexray)),RW)),None)),Set(),List(),Set(),UpgradeStrategy(0.0,0.0),Map(),None,None,OnlyVersion(2016-04-13T19:08:15.953Z),None).id]"]}]}