Add support for model(s): DR-HSH006S

Include all of the following:

Model - in the format used in the README.MD: DR-HSH006S
Number of speeds the fan supports (not including "off"):

1 in FAN mode (not modifiable)
3 heating level H1/H2/H3 in HEAT mode
1 in ECO mode (not modifiable)

Does the fan support oscillating? No
What preset modes are supported? I don't know. See speeds of fan for detailed modes.
Is temperature supported? Yes in ECO mode (°C in France)

Make sure you've installed this integration, then from the integration settings page, select Download Diagnostics and attach that file.
home-assistant_dreo_2024-10-08T17-04-11.722Z.log

@JeffSteinbok, the pull request #215 is available for review.
It contains:

management of DR-HSH006S device model
Fixes for setting preset and target temperature (ranges not correctly controlled)

It remains some behaviors to fix for me with the Celsius mode, because the current temperature value in climate is not correct (Fahrenheit value instead of Celsius) even if the unit is OK. I don't know how to fix it.


modifications to fix problems with latest numpy version

Dear Claudio,
I found your description of word2vec and your implementation of it very useful.  I have made some small changes to the code so that it runs under numpy v 1.14.  I think/hope I've done it correctly, and my version passes your unittests.
The problems all revolved around the intepretation of 1-dimensional arrays in numpy, which are always confusing to me.
I hope you find this useful.

Hi Jeremy, I did a couple more checks. Running python test_word2veclite.py results in the tests passing, however when I run nosetests the skipgram test fails (not sure why yet, didn't have time to investigate further). In any case, as I mentioned before the results of the skipgram model as they are now are not consistent with the previous ones.

I naively accepted the fact that (at least for me) the skipgram test passed, so didn't study it as much as I should have.  I will look more closely at it today.

I made another pass at this and hopefully things are OK now with some caveats:
Good News:
both skipgram and cbow run and the loss function seems to behave correctly -- you get convergence.
Bad News:
They fail the test code; the results don't match tensorflow to 5 digits.  I'm not sure if this is a real problem; there could be a bug or it could just be that my particular installation of tensorflow doesn't quite give the same numerical results.  If you believe they should match, I can look again.

By the say, the jupyter notebook shows the loss function graphs.

OK, I made those changes, and now the tests pass.

Incidentally I haven't tested the "predict" function nor used a larger corpus or other parameters like a wider window.

woodmont:~/GitHub/word2veclite/word2veclite/test$ nosetests
Using TensorFlow backend.
2018-07-09 17:12:26.126068: I tensorflow/core/platform/cpu_feature_guard.cc:140] Your CPU supports instructions that th\
is TensorFlow binary was not compiled to use: AVX2 FMA
..
----------------------------------------------------------------------
Ran 2 tests in 0.233s

OK

Great, I will test this and merge your branch later tonight.

Cool! Thanks, and thanks again for putting this all together in the first place, I learned a lot.


Extracting x-cache-proxyname from the header doesn't work all the time

So I've been scraping through Python Requests. NOT Scrapy, and I basically extract the name of the said proxy like this:
name= horsereq.history[0].headers['x-cache-proxyname']
Now this often works, but I also often get this error:
`File "exampleuk.py", line 161, in func

name= horsereq.history[0].headers['x-cache-proxyname']
  IndexError: list index out of range`

[x-cache-proxyname] is just not in the original headers.
How do I fix this? Is there another way to find the name of the proxy?

Hello @Bayoslav ,
2 questions:
1/ Is the request on HTTP ? (not HTTPS)
2/ can you dump the full header response ?
Thx,
Fabien

Hey @fabienvauchelles
Tried both HTTP and HTTPS, still throws the same error from time to time.
HTTP Header:
{'content-type': 'text/html; charset=UTF-8', 'server': 'Microsoft-IIS/7.5', 'set-cookie': 'CFID=40348307; HttpOnly;domain=.www.equineline.com;path=/, CFTOKEN=41a5aec994f745e7%2D0DBB780A%2D5056%2DBE0C%2D978C6E5B474B5D37; HttpOnly;domain=.www.equineline.com;path=/', 'x-powered-by': 'ASP.NET', 'date': 'Sun, 25 Feb 2018 18:14:28 GMT', 'content-length': '22714', 'x-cache-proxyname': 'i-09df019527f7b1768', 'Connection': 'keep-alive'}
HTTPS Header:
{'Content-Type': 'text/html; charset=UTF-8', 'Server': 'Microsoft-IIS/7.5', 'Set-Cookie': 'CFID=38979868; HttpOnly;domain=.www.equineline.com;path=/, CFTOKEN=e138576cbb60bff3%2D0DC6BCB5%2D5056%2DBE2F%2D782FE7D35A5F028F; HttpOnly;domain=.www.equineline.com;path=/', 'X-Powered-By': 'ASP.NET', 'Date': 'Sun, 25 Feb 2018 18:15:42 GMT', 'Content-Length': '22714'}
This might be an issue with Python Requests library, but I am not sure.

Hey so I've just noticed in the usual HTTP Headers, I have no idea how I didn't see it before. Anyway, thank you for your time.


services seems to be ignoring baseUrl in getKernelSpecs

I have a webserver hosting my content on port 8080 and a notebook server running on 8888.
Running the following code:
// Connect to the notebook webserver.
    getKernelSpecs('http://localhost:8888').then(kernelSpecs => {
        return startNewKernel({
            baseUrl: 'http://localhost:8888',
            wsUrl: 'ws://localhost:8888',
            name: kernelSpecs.default,
        });
    }).then(kernel => {});

yields
GET http://localhost:8080/api/kernelspecs?1453312304541 404 (Not Found)

Correct me if I'm wrong, but it looks like jupyter-js-services is ignoring the base url I pass in to getKernelSpecs.  Instead it's using the window's current URL as a base.
See https://github.com/ipython/ipywidgets/pull/328

Aha, the API changed- why not release as a new major version?

For ref:
// Connect to the notebook webserver.
    getKernelSpecs({baseUrl: 'http://localhost:8888'}).then(kernelSpecs => {
        return startNewKernel({
            baseUrl: 'http://localhost:8888',
            wsUrl: 'ws://localhost:8888',
            name: kernelSpecs.default,
        });
    }).then(kernel => {});

Works

There is no major version yet, it is still considered alpha.  I did bump from 0.2 -> 0.3 for this change.

Sorry for the noise!  I should pay more attn to changes here


Temporary workaround for flaky metadata server on GCE

ref https://github.com/kubernetes/kubernetes/issues/22176

LGTM


Date range restriction for Statistics API breaks on empty/invalid date passed

If an empty date is passed, this should handle the error and default to open-ended search.
If an invalid date is passed, this should inform the user.

This is specifically affecting the new-plans org-admin usage dashboard

works well


Existed courses on table will disappear when select new courses

Scenario

When there are course(s) already exists in the time box, added a course in the same box can reproduce this bug.

Cause
Undetermined

Speculation: The hover state and courseTime state have some kind of conflict with each other.

Fix
TBD

Cannot reproduce this bug in the new framework and new state design.


[BanyanDBJavaClient] Support "version" field

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
This is based upon #9990
The java client should support this new field.
Use case
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I'm interested in this task. But is this task should wait for issue #9990 to be done?

I'm interested in this task. But is this task should wait for issue #9990 to be done?

That's right. This is a follow-up task of #9990.


K8SPXC-1060: validate cr version

https://jira.percona.com/browse/K8SPXC-1060

Test name
Status

haproxy
passed

upgrade-haproxy
passed

scheduled-backup
failed

scaling
passed

storage
passed

recreate
passed

big-data
passed

cross-site
passed

scaling-proxysql
passed

self-healing
passed

self-healing-chaos
passed

restore-to-encrypted-cluster
passed

security-context
passed

upgrade-proxysql
passed

self-healing-advanced
passed

self-healing-advanced-chaos
passed

init-deploy
passed

demand-backup
passed

limits
failed

operator-self-healing
passed

operator-self-healing-chaos
passed

smart-update
passed

pitr
failed

monitoring-2-0
failed

We run 24 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1192/commits/38b485665d278a403ce1343acfdc731593bcb742
image: perconalab/percona-xtradb-cluster-operator:PR-1192-38b48566

Test name
Status

big-data
passed

upgrade-haproxy
passed

storage
passed

haproxy
failed

cross-site
passed

scheduled-backup
failed

scaling
passed

recreate
passed

scaling-proxysql
passed

self-healing
passed

self-healing-chaos
passed

restore-to-encrypted-cluster
passed

upgrade-proxysql
passed

security-context
passed

init-deploy
passed

self-healing-advanced
passed

self-healing-advanced-chaos
passed

demand-backup
passed

limits
failed

smart-update
passed

operator-self-healing
passed

operator-self-healing-chaos
passed

pitr
failed

upgrade-consistency
failed

monitoring-2-0
failed

demand-backup-encrypted-with-tls
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
failed

proxy-protocol
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1192/commits/7a07df2d38902d392c20429004cd4aff5e418750
image: perconalab/percona-xtradb-cluster-operator:PR-1192-7a07df2d

Do we add/update tests for changes like this?

Test name
Status

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

haproxy
passed

big-data
passed

scheduled-backup
failed

upgrade-haproxy
passed

storage
passed

pitr
failed

cross-site
passed

self-healing
passed

scaling
passed

self-healing-chaos
passed

scaling-proxysql
passed

self-healing-advanced
passed

security-context
passed

self-healing-advanced-chaos
passed

operator-self-healing
passed

operator-self-healing-chaos
passed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed

init-deploy
passed

limits
passed

monitoring-2-0
failed

demand-backup-encrypted-with-tls
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
failed

proxy-protocol
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1192/commits/7a07df2d38902d392c20429004cd4aff5e418750
image: perconalab/percona-xtradb-cluster-operator:PR-1192-7a07df2d

Test name
Status

scaling
passed

scaling-proxysql
passed

security-context
passed

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

haproxy
passed

scheduled-backup
failed

cross-site
passed

upgrade-haproxy
passed

big-data
passed

storage
passed

pitr
failed

init-deploy
passed

self-healing
passed

limits
passed

self-healing-chaos
passed

monitoring-2-0
failed

self-healing-advanced
passed

self-healing-advanced-chaos
passed

operator-self-healing
passed

operator-self-healing-chaos
passed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
failed

proxy-protocol
passed

demand-backup-encrypted-with-tls
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1192/commits/7a07df2d38902d392c20429004cd4aff5e418750
image: perconalab/percona-xtradb-cluster-operator:PR-1192-7a07df2d

Do we add/update tests for changes like this?

we need to test it

Test name
Status

haproxy
failed

storage
passed

upgrade-haproxy
passed

scaling
passed

recreate
passed

scheduled-backup
failed

cross-site
passed

big-data
passed

scaling-proxysql
passed

self-healing
passed

self-healing-chaos
failed

restore-to-encrypted-cluster
passed

security-context
passed

upgrade-proxysql
passed

init-deploy
passed

self-healing-advanced
passed

self-healing-advanced-chaos
failed

demand-backup
passed

limits
passed

smart-update
passed

operator-self-healing
passed

operator-self-healing-chaos
failed

monitoring-2-0
passed

pitr
failed

affinity
passed

one-pod
passed

auto-tuning
passed

upgrade-consistency
failed

proxysql-sidecar-res-limits
failed

demand-backup-encrypted-with-tls
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
failed

proxy-protocol
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1192/commits/2aea0001e476595aac2233cbc8b8de8d2cc37c4e
image: perconalab/percona-xtradb-cluster-operator:PR-1192-2aea0001

Test name
Status

cross-site
passed

scaling
passed

storage
passed

scheduled-backup
failed

big-data
passed

haproxy
failed

upgrade-haproxy
passed

recreate
passed

scaling-proxysql
passed

self-healing
passed

self-healing-chaos
failed

restore-to-encrypted-cluster
passed

security-context
passed

upgrade-proxysql
passed

init-deploy
passed

self-healing-advanced
passed

self-healing-advanced-chaos
failed

demand-backup
passed

operator-self-healing
passed

operator-self-healing-chaos
failed

smart-update
passed

pitr
failed

limits
passed

monitoring-2-0
passed

affinity
failed

upgrade-consistency
passed

demand-backup-encrypted-with-tls
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
failed

proxy-protocol
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1192/commits/b6eee1a3034b5cb343d852814e9f82330af44218
image: perconalab/percona-xtradb-cluster-operator:PR-1192-b6eee1a3

Test name
Status

recreate
passed

scaling
passed

haproxy
passed

scheduled-backup
failed

upgrade-haproxy
passed

big-data
passed

cross-site
passed

storage
passed

scaling-proxysql
passed

self-healing
passed

self-healing-chaos
failed

restore-to-encrypted-cluster
passed

security-context
passed

upgrade-proxysql
passed

init-deploy
passed

self-healing-advanced
passed

self-healing-advanced-chaos
failed

demand-backup
passed

smart-update
passed

limits
passed

operator-self-healing
passed

operator-self-healing-chaos
failed

monitoring-2-0
passed

pitr
failed

affinity
passed

one-pod
passed

upgrade-consistency
failed

auto-tuning
failed

demand-backup-encrypted-with-tls
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

proxy-protocol
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1192/commits/20e15ef813901a978febbf6b67d64952a2410408
image: perconalab/percona-xtradb-cluster-operator:PR-1192-20e15ef8

Test name
Status

recreate
passed

storage
passed

scaling
passed

upgrade-haproxy
passed

cross-site
passed

big-data
passed

scheduled-backup
failed

haproxy
passed

scaling-proxysql
passed

self-healing
passed

self-healing-chaos
failed

restore-to-encrypted-cluster
passed

security-context
passed

init-deploy
passed

upgrade-proxysql
passed

demand-backup
passed

self-healing-advanced
passed

self-healing-advanced-chaos
failed

limits
passed

smart-update
passed

operator-self-healing
passed

operator-self-healing-chaos
failed

monitoring-2-0
passed

pitr
failed

affinity
passed

one-pod
passed

auto-tuning
passed

upgrade-consistency
passed

proxysql-sidecar-res-limits
passed

demand-backup-encrypted-with-tls
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

proxy-protocol
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1192/commits/ce65491884e7ec74f53889cfbafa50596ff516eb
image: perconalab/percona-xtradb-cluster-operator:PR-1192-ce654918

Test name
Status

upgrade-haproxy
passed

recreate
passed

big-data
passed

cross-site
passed

scheduled-backup
failed

scaling
passed

storage
passed

restore-to-encrypted-cluster
passed

haproxy
passed

scaling-proxysql
passed

self-healing
passed

demand-backup
passed

init-deploy
passed

security-context
passed

self-healing-chaos
failed

limits
passed

pitr
failed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

proxy-protocol
passed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed

self-healing-advanced
passed

self-healing-advanced-chaos
failed

operator-self-healing
passed

operator-self-healing-chaos
failed

demand-backup-encrypted-with-tls
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1192/commits/ce65491884e7ec74f53889cfbafa50596ff516eb
image: perconalab/percona-xtradb-cluster-operator:PR-1192-ce654918

Test name
Status

We run 0 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1192/commits/5ace3ab1735e947c8afc3300a7a56dcf7e9f6e97
image: perconalab/percona-xtradb-cluster-operator:PR-1192-5ace3ab1

Test name
Status

storage
passed

recreate
passed

upgrade-haproxy
passed

cross-site
passed

big-data
passed

scheduled-backup
failed

haproxy
failed

scaling
passed

self-healing
passed

self-healing-chaos
passed

scaling-proxysql
passed

restore-to-encrypted-cluster
passed

security-context
passed

upgrade-proxysql
passed

self-healing-advanced
passed

init-deploy
passed

self-healing-advanced-chaos
passed

demand-backup
passed

limits
passed

operator-self-healing
passed

operator-self-healing-chaos
passed

monitoring-2-0
passed

smart-update
passed

affinity
passed

one-pod
passed

pitr
failed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

upgrade-consistency
failed

users
failed

demand-backup-encrypted-with-tls
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

proxy-protocol
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1192/commits/5c47d44a3dba12c2060eee46c5c5b8203a9f30ce
image: perconalab/percona-xtradb-cluster-operator:PR-1192-5c47d44a

Test name
Status

We run 0 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1192/commits/c067ffe349b476830ead19ba548c3628b0ed4ac3
image: perconalab/percona-xtradb-cluster-operator:PR-1192-c067ffe3

Test name
Status

upgrade-haproxy-8-0
passed

scaling-8-0
passed

scheduled-backup-8-0
passed

haproxy-8-0
passed

users-5-7
passed

big-data-8-0
passed

cross-site-8-0
passed

storage-8-0
passed

recreate-8-0
passed

scaling-proxysql-8-0
passed

self-healing-8-0
passed

self-healing-chaos-8-0
passed

init-deploy-8-0
passed

restore-to-encrypted-cluster-8-0
passed

security-context-8-0
passed

upgrade-proxysql-8-0
passed

self-healing-advanced-8-0
passed

self-healing-advanced-chaos-8-0
passed

limits-8-0
passed

one-pod-5-7
passed

demand-backup-8-0
passed

scheduled-backup-5-7
failed

monitoring-2-0-8-0
passed

operator-self-healing-8-0
passed

smart-update-8-0
passed

operator-self-healing-chaos-8-0
passed

affinity-8-0
passed

one-pod-8-0
passed

auto-tuning-8-0
passed

pitr-8-0
failed

proxysql-sidecar-res-limits-8-0
passed

users-8-0
failed

upgrade-consistency-8-0
failed

demand-backup-encrypted-with-tls-8-0
failed

init-deploy-5-7
passed

tls-issue-self-8-0
passed

tls-issue-cert-manager-8-0
passed

haproxy-5-7
passed

tls-issue-cert-manager-ref-8-0
passed

validation-hook-8-0
passed

proxy-protocol-8-0
passed

We run 41 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1192/commits/c067ffe349b476830ead19ba548c3628b0ed4ac3
image: perconalab/percona-xtradb-cluster-operator:PR-1192-c067ffe3

Test name
Status

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

demand-backup-8-0
passed

pitr-8-0
passed

big-data-8-0
passed

storage-8-0
passed

scaling-8-0
passed

upgrade-haproxy-8-0
passed

self-healing-8-0
passed

scaling-proxysql-8-0
passed

self-healing-chaos-8-0
passed

security-context-8-0
passed

self-healing-advanced-8-0
passed

users-5-7
passed

haproxy-8-0
passed

scheduled-backup-8-0
passed

self-healing-advanced-chaos-8-0
passed

cross-site-8-0
passed

one-pod-5-7
passed

init-deploy-8-0
passed

operator-self-healing-8-0
passed

scheduled-backup-5-7
passed

limits-8-0
passed

operator-self-healing-chaos-8-0
passed

monitoring-2-0-8-0
passed

affinity-8-0
passed

one-pod-8-0
passed

auto-tuning-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

users-8-0
passed

upgrade-proxysql-8-0
passed

smart-update-8-0
passed

upgrade-consistency-8-0
passed

tls-issue-self-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

validation-hook-8-0
passed

proxy-protocol-8-0
passed

init-deploy-5-7
passed

haproxy-5-7
passed

demand-backup-encrypted-with-tls-8-0
passed

We run 41 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1192/commits/c067ffe349b476830ead19ba548c3628b0ed4ac3
image: perconalab/percona-xtradb-cluster-operator:PR-1192-c067ffe3

Test name
Status

affinity-8-0
failed

auto-tuning-8-0
failed

cross-site-8-0
failed

demand-backup-8-0
failed

demand-backup-cloud-8-0
failed

demand-backup-encrypted-with-tls-8-0
failed

haproxy-5-7
failed

haproxy-8-0
failed

init-deploy-5-7
failed

init-deploy-8-0
failed

limits-8-0
failed

monitoring-2-0-8-0
failed

one-pod-5-7
failed

one-pod-8-0
failed

pitr-8-0
failed

proxy-protocol-8-0
failed

proxysql-sidecar-res-limits-8-0
failed

recreate-8-0
failed

restore-to-encrypted-cluster-8-0
failed

scaling-8-0
failed

scaling-proxysql-8-0
failed

scheduled-backup-5-7
failed

scheduled-backup-8-0
failed

security-context-8-0
failed

smart-update1-8-0
failed

smart-update2-8-0
failed

storage-8-0
failed

tls-issue-cert-manager-8-0
failed

tls-issue-cert-manager-ref-8-0
failed

tls-issue-self-8-0
failed

upgrade-consistency-8-0
failed

upgrade-haproxy-8-0
failed

upgrade-proxysql-8-0
failed

users-5-7
failed

users-8-0
failed

validation-hook-8-0
failed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1192/commits/28c9ed842574cfd7d14f4f92be572b8555d7e265
image: perconalab/percona-xtradb-cluster-operator:PR-1192-28c9ed84

Test name
Status

affinity-8-0
failed

auto-tuning-8-0
failed

cross-site-8-0
failed

demand-backup-8-0
failed

demand-backup-cloud-8-0
failed

demand-backup-encrypted-with-tls-8-0
failed

haproxy-5-7
failed

haproxy-8-0
failed

init-deploy-5-7
failed

init-deploy-8-0
failed

limits-8-0
failed

monitoring-2-0-8-0
failed

one-pod-5-7
failed

one-pod-8-0
failed

pitr-8-0
failed

proxy-protocol-8-0
failed

proxysql-sidecar-res-limits-8-0
failed

recreate-8-0
failed

restore-to-encrypted-cluster-8-0
failed

scaling-8-0
failed

scaling-proxysql-8-0
failed

scheduled-backup-5-7
failed

scheduled-backup-8-0
failed

security-context-8-0
failed

smart-update1-8-0
failed

smart-update2-8-0
failed

storage-8-0
failed

tls-issue-cert-manager-8-0
failed

tls-issue-cert-manager-ref-8-0
failed

tls-issue-self-8-0
failed

upgrade-consistency-8-0
failed

upgrade-haproxy-8-0
failed

upgrade-proxysql-8-0
failed

users-5-7
failed

users-8-0
failed

validation-hook-8-0
failed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1192/commits/28c9ed842574cfd7d14f4f92be572b8555d7e265
image: perconalab/percona-xtradb-cluster-operator:PR-1192-28c9ed84

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

haproxy-5-7
failed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
failed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-8-0
passed

scaling-proxysql-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1192/commits/80ec338f2ad4618ca18dc36276a6ac5d68577b96
image: perconalab/percona-xtradb-cluster-operator:PR-1192-80ec338f

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-8-0
passed

scaling-proxysql-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1192/commits/80ec338f2ad4618ca18dc36276a6ac5d68577b96
image: perconalab/percona-xtradb-cluster-operator:PR-1192-80ec338f


Call for Proposals - Solidity to Ink! Converter

Proposal
Web3 Grants is looking to fund the development of a Solidity to Ink!  conversion tool and is issuing a call for grant proposals for this work. Please apply through the normal process outlined here.
Motivation
If a blockchain solution built on Ethereum needs to be migrated or rebuilt on Substrate it requires a lot of effort to redesign and rewrite the business logic from Solidity smart contracts to either Substrate runtime modules or smart contracts written in Ink!, a Rust-based eDSL for smart contracts on Substrate.
In cases where a direct rewrite of a Solidity smart contract into an Ink! smart contract makes sense, it would be good to have some tooling to reduce this effort.
For example, if a smart contract developer takes x amount of effort to rewrite a Solidity smart contract in Ink!, can we try to reduce this effort by providing a tool? This could help with fast-paced Substrate adoption in use-cases where primary logic should stay in smart contracts when ported to Substrate.
Solidity to Ink! Converter
While it is fairly complex to create a language conversion tool which emits fully compilable and functional code, we can start with a simpler tool that “translates” Solidity to Ink! by doing keyword and grammar replacement. This will not produce compilable code but should significantly reduce migration efforts for a developer. Instead of spending x amount of effort to rewrite the contract in Ink! the developer would now spend only x - y effort to make the converted code compile and run. The reduction of effort y will increase with the maturity of the conversion tool.
References
Java to C# converter
Java to Typescript

How come you closed this already?
JBP

On Sep 20, 2019, at 8:39 AM, Dieter Fishbein<EMAIL_ADDRESS>wrote:
Closed #179.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Pagination emit unnecessary nzPageIndexChange event

Version
0.6.14
Environment
mac chrome latest
Reproduction link
https://stackblitz.com/edit/ng-zorro-antd-setup-hzm6ar?file=app%2Fapp.component.ts
Steps to reproduce
https://stackblitz.com/edit/ng-zorro-antd-setup-hzm6ar?file=app%2Fapp.component.ts
What is expected?
nzPageIndexChange 不应该 被 回调
What is actually happening?
nzPageIndexChange 被 回调
Other?
https://github.com/NG-ZORRO/ng-zorro-antd/issues/280  之前 修过，怎么又 复现了

ref #1016


Footer - Twitter Logo update

Hi Team,
As we all know the Twitter logo has been updated from a bird called Larry to an X. So, please make the changes accordingly in the footer.

@Kummu007 - please validate

Hi @Vinaykumargujja thanks for the quick response, This issue is fixed hence closing the ticket.


Tech Community Call

Tech Community Call Update Tue 26th, 2024
A total of 6 People joined this call from the community side from FIDE. A total of 3 people joined to answer all the Questions that the community people had.


Possibility to limit months

Great tool, thank you for making this.
I'm visualising extreme cold temperatures, and these only happen from December through March. It would be nice to be able to limit months in the plot and rearrange them to overlap years.

Hi, if this problem still exists and you'd like to create a PR to fix it please direct it to https://github.com/MarvinT/calmap/
That is the version that gets published to pypi and has received several updates to fix some existing issues.

Thank you for creating the issue. Unfortunately I don't have the time to maintain this project. As per @MarvinT 's comment, please see https://github.com/MarvinT/calmap/ instead.


L code

Traceback (most recent call last):
File "Samarium_GUI.py", line 144, in
File "pypresence\presence.py", line 13, in init
File "pypresence\baseclient.py", line 28, in init
pypresence.exceptions.DiscordNotFound: Could not find Discord installed and running on this machine.
LMAO nice logger

It says in the moduel pypresence, thats for the Discord RPC, it's not a logger.


An equivalent to force_sort_within_sections from isort

I personally prefer to sort imports like this (which used to be the standard sorting for the Python extension on VS Code):
import numpy as np
import torch
import torch.nn.functional as F
from torch.utils.data import DataLoader
from torchvision import datasets
from torchvision.transforms import ToTensor
import tqdm

from .my_module import my_func

as opposed to this sorting, which is how isort (and ruff) sorts by default:
import numpy as np
import torch
import torch.nn.functional as F
import tqdm
from torch.utils.data import DataLoader
from torchvision import datasets
from torchvision.transforms import ToTensor

from .my_module import my_func

(Notice how tqdm is sandwiched there in the torch imports.)
With isort, I can achieve the desired sorting with the force_sort_within_sections option. Would you be interested in supporting this as well?

Yeah we can probably support this (and I don't mind doing so), though it requires a bit of refactoring to the import model.

Added in #1635.


Create bash auto-complete for tomee-cli.sh

how about creating an Ubuntu upstart script/conf similar to Tomcat service?

@rponte
TomEE CLI helps you to configure your Application Server.
Some features is useful for tomcat too, like: Configure security, Configure clusters, hosts, WAR deploy e etc. (Some in development)
This case, we want to have a bash autocomplete.
Eg:.
I want to install TomEE:
tomee-cli install --[TAB]

The shell will show options for this command:
--version --dist --path

If you want a functions to create and configure scripts on initialization's OS like:
Create a service for Windows;
Create a rc.Initi script for *nix
Create a plist for launchd for OS X.
Please, open a issue for that and we'll discuss about.


Remodeled the Speech Recognition System

Speech Recognition System
-> Bug: Amy shut down doesn't work #362
-> Possible Enhancement: SR-Config loading some predefines
-> remote SR deadlock exists again
References PR : Closes #328
Pull request status:

[x] Tests added/updated
[x] Code conventions
[x] Ready for review

Codecov Report

Merging #322 into dev will increase coverage by 0.27%.
The diff coverage is 0%.

@@             Coverage Diff              @@
##                dev     #322      +/-   ##
============================================
+ Coverage     51.59%   51.86%   +0.27%
+ Complexity     1146     1142       -4
============================================
  Files           195      187       -8
  Lines          4968     4903      -65
  Branches        639      626      -13
============================================
- Hits           2563     2543      -20
+ Misses         2253     2208      -45
  Partials        152      152

Impacted Files
Coverage Δ
Complexity Δ

...rt/iaas/amyassist/amy/core/speech/data/Sounds.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

.../iaas/amyassist/amy/core/speech/SpeechManager.java
0% <0%> (ø)
0 <0> (?)

.../amyassist/amy/core/CoreServiceProviderLoader.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...t/amy/core/speech/sphinx/SphinxGrammarCreator.java
0% <0%> (ø)
0 <0> (?)

...ssist/amy/core/speech/sphinx/SphinxRecognizer.java
0% <0%> (ø)
0 <0> (?)

...myassist/amy/plugin/calendar/CalendarResource.java
100% <0%> (ø)
18% <0%> (+4%)
: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 345c0ed...af81bc3. Read the comment docs.

Bug: Amy shut down doesn't work #362

Isn't this issue fixed by now? I can't reproduce it on my system, but I don't want to close the issue without confirmation from someone else

make it possible to change the wake up command #63

@Legion2 I think customising the wake-up command should be a separate task and PR


centralcatholic

centralcatholichs.com

@wilson20cc Please rename lib/domains/com/centralcatholic to lib/domains/com/centralcatholic.txt
Thank you!

@wilson20cc You might miss my previous comment. Please react.

@wilson20cc Pull request merged. Thank you!


[WIP] Setup Danger.systems

What?
Setup Danger.

CC @pusher/sigsdk

          1 Warning

:warning:
PR is classed as Work in Progress

  Generated by :no_entry_sign: Danger

🚢


Fixing publish action

Fixing publish action due to having two identical identifiers

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 80.269%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2161

Relevant Lines:
2663

💛  - Coveralls


variable name instead of the value in dashboard

Not sure if this is an issue in this project or the dashboard code but on
https://storage.googleapis.com/java-cloud-bom-dashboard/com.google.cloud/google-cloud-bom/0.141.0/index.html
I saw this:

note how we get the variable name instead of the value

Thanks for reporting the bug @elharo -- an existing issue captures this https://github.com/googleapis/java-bigquery/issues/881.
We will keep track of the work in the exiting ticket.


QuickSort Algorithm

Review File name guidelines in CONTRIBUTING.md
Rename the file.
Then Commit -> Push
It'll update here automatically
Let me know if facing any issues

And only one file per PR 😅
Utilize branches for simultaneous PRs

Review File name guidelines in CONTRIBUTING.md
Rename the file. Then Commit -> Push It'll update here automatically
Let me know if facing any issues

Do I need to do PR again after changing name?

Review File name guidelines in CONTRIBUTING.md
Rename the file. Then Commit -> Push It'll update here automatically
Let me know if facing any issues

Do I need to do PR again after changing name?

No you don't

Just create another request for the second file


What is the maximum payload size that CFU can support? - From Cypress Semi

In CFU Protocol Specification, Table 5.5 3 (FIRMWARE_UPDATE_CONTENT Header Bits) Data length field is limited to 8 bits in size.
It is also mentioned that "maximum allowed value for the length is 52 bytes".

Does this mean that the maximum allowed size in one payload transaction is 52 bytes?

Sorry for delay in answering this question.
The 52-byte limitation is to allow compatibility with usb full-speed protocol. Transfer size is 60 minus 8 bytes overhead which equals 52 bytes.
Since the transfer occurs in the background, it is ok if the transfer takes a long time. There is no limit to the number of transfers.


Not able to install Power Platform CLI on Linux (Ubuntu 22.04)

Hi Team,
We want to configure a Jenkins CICD for our power platform. Jenkins is installed on Linux Server (Ubunto 22.04).
We referred this article for installing the power platform cli -  (https://powerusers.microsoft.com/t5/Power-Apps-Pro-Dev-ISV/Pac-linux/m-p/1744332#M6738)
We tried this approach for macOS and Windows it worked.
However we have run into issue for Linux.
we run the commands as below
chmod +x pac
./pac
and then we get following error
A fatal error occurred. The required library libhostfxr.so could not be found.
If this is a self-contained application, that library should exist in [/home/[username]/TEMP/].
If this is a framework-dependent application, install the runtime in the global location [/usr/share/dotnet] or use the DOTNET_ROOT environment variable to specify the runtime location or register the runtime location in [/etc/dotnet].
The .NET runtime can be found at:

https://aka.ms/dotnet-core-applaunch?missing_runtime=true&arch=x64&rid=ubuntu.22.04-x64&apphost_version=6.0.6

Following are the steps we did on linux server.

installed the .Net 6.0
installed vscode
installed the Power Platform Tools extension
extracted the nupkg file
Tried to run with chmod +x pac
We get error message as shown above.

Please help us resolve this issue as its critical for us have this installation done for Jenkins to run pac commands.
Thanks.

@sunilbsharma
I'm sorry to hear you are experiencing this issue.
This repository is for the PAC CLI documentation. We accept issues where people have feedback for the documentation. I don't see any comments about the documentation in this issue. This looks like a request for technical support. We don't have the resources to respond to technical support requests.
I see you have also raised this in the forum. That is also a good idea. But if this is critical, I recommend you contact Microsoft Support to get a resolution for this issue.
I'm going to close this issue.


Multi Language Tokenization Support

I'm hoping that we can get to the point where we fully support the following languages.

English
Spanish
German
French
Russian
Japanese
Hindi
Farsi
Chinese
Arabic

I started adding unit tests for these languages for a few tokenizers here https://github.com/RubixML/ML/tree/master/tests/Tokenizers - however, it doesn't look like we support all the langugaes. I only speak English so it's hard for me to tell. Could we get some help from the community to verify that our Tokenizers support all of these languages and, if not, contribute a fix?
https://github.com/RubixML/ML/tree/master/src/Tokenizers
Thank you!

How to join the development of multiple languages? I am good at Chinese and English.

Hi @taotecode, thanks for your interest in contributing to the project! Here are the unit tests for the Tokenizers implemented in the library.
https://github.com/RubixML/ML/tree/master/tests/Tokenizers
We need help from native language speakers to ensure that we have test coverage for different languages and that the current tests are correct.

@andrewdalpino I can help with Hindi. I am not sure how it is going to work with though.
Here is the problem:
$text = "यदि कोई चीज़ काफ़ी महत्वपूर्ण है, तो आपको उसे आज़माना चाहिए। भले ही - संभावित परिणाम विफलता हो।";
$tokens = \Rubix\ML\Tokenizers\Word::tokenize($text);

Expected array:
[
  'यदि', 'कोई', 'चीज़', 'महत्वपूर्ण', 'है', 'तो', 'आपको', 'उसे', 'आज़माना',
  'चाहिए', 'भले', 'ही', '-', 'संभावित', 'परिणाम', 'विफलता', 'हो',
]

Actual array:
[
'यद', 'क', 'ई', 'च', 'ज', 'क', 'फ', 'महत', 'वप', 'र', 'ण', 'ह', 'त', 'आपक',
'उस', 'आज', 'म', 'न', 'च', 'ह', 'ए', 'भल', 'ह', '-', 'स', 'भ', 'व', 'त',
'पर', 'ण', 'म', 'व', 'फलत', 'ह',
]
I only tested for `\Rubix\ML\Tokenizers\Word` yet.

@andrewdalpino I can help with Hindi. I am not sure how it is going to work with though.
Here is the problem:
$text = "यदि कोई चीज़ काफ़ी महत्वपूर्ण है, तो आपको उसे आज़माना चाहिए। भले ही - संभावित परिणाम विफलता हो।";
$tokens = \Rubix\ML\Tokenizers\Word::tokenize($text);

Expected array:
[
  'यदि', 'कोई', 'चीज़', 'महत्वपूर्ण', 'है', 'तो', 'आपको', 'उसे', 'आज़माना',
  'चाहिए', 'भले', 'ही', '-', 'संभावित', 'परिणाम', 'विफलता', 'हो',
]

Actual array:
[
  'यद', 'क', 'ई', 'च', 'ज', 'क', 'फ', 'महत', 'वप', 'र', 'ण', 'ह', 'त', 'आपक',
  'उस', 'आज', 'म', 'न', 'च', 'ह', 'ए', 'भल', 'ह', '-', 'स', 'भ', 'व', 'त',
  'पर', 'ण', 'म', 'व', 'फलत', 'ह',
]

I only tested for \Rubix\ML\Tokenizers\Word yet.

This is because Hindi and many other languages are based on Complex Text Layout (CTL) - so you will need to account for partial words that becomes full words at the end. In general terms, they fall under complex script languages. I'm pretty sure there are many works in python for tokenizing these languages, PHP also needs one of those implementations such as hindi-tokenizer but for other languages as well to support further development.
AFAIK the tokenizers comes from NLTK and it's derivative works, there needs to be equivalent implementation in php or FFI wrapper in order to make this work.


How to get confidence values?

Hi @tmbdev , I did some experiments about offline handwriting recognition with clstm. The network can produce one sequential result by given image.
Is it possible to get confidence values of the result? For example, as shown in the image given by https://github.com/tmbdev/clstm/issues/18 , every position of the sequence has different colors for different predictions.
Are there any interfaces in clstm to get such confidence values?
Thanks.

I've added another overloading for CLSTM::predict that gives you confidence values. You can also get them from the clstmocr command line by setting conf=1

Thanks, @tmbdev
I have another question.
Can the predict interface provide top-N results?
That will be helpful for better results and finding weakness of datasets.
Thanks.

if you want to buy these(ocropy.com/ocropy.net/ocropy.org) domains. contact us
mail<EMAIL_ADDRESS>


Options menu

A new tab to collect options.
Options should be saved off somewhere, probably UserDefaults.

[x] Color configurations
[x] Units
[x] Render options

Color configurations
ColorPicker is finally out of beta with iOS 14!
Choice of mesh and lighting colors.
Ability to enable random-quilt mesh coloring.
Any other colors??
Units
metric/customary switch affecting

SurveyLine labels
cutoff height on projected render
maybe the order of projected-render scale bars?
extents?

Customary units will still be decimal feet for sanity.
Render options
Camera configuration / interactionMode.

Enumerated all the currently-defined options as SettingsKey enum and created SettingsStore in 6f2fcb2.

PR #13 completes the integration of the display-unit options and rendering around the app

PR #13 completes the integration of the display-unit options and rendering around the app


[FLINK-32158] Unify the getMultiInputOperatorDefaultMeta and getOneInputOperatorDefaultMeta methods into the same getInputOperatorDefaultMeta method

What is the purpose of the change
Unify the getMultiInputOperatorDefaultMeta and getOneInputOperatorDefaultMeta methods into the same getInputOperatorDefaultMeta method. Because 1 is a special case of Multi, there is no need to repeat the definition.Same applies to getStateTtlForMultiInputOperator and getStateTtlForOneInputOperator methods
Brief change log
Unify the getMultiInputOperatorDefaultMeta and getOneInputOperatorDefaultMeta methods into the same getInputOperatorDefaultMeta method
Unify the getStateTtlForMultiInputOperator and getStateTtlForOneInputOperator methods into the same getStateTtlForInputOperator method
Verifying this change
This change is already covered by existing tests
Does this pull request potentially affect one of the following parts:

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

Documentation

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

@LadyForest  @godfreyhe could you help take a look when you have time? Thanks.

@flinkbot run azure

@flinkbot run azure

Hi @jiaoqingbo, Thanks for the contribution!
IMO, getOneInputOperatorDefaultMeta is heavily used since almost all stateful operators (except for Join) are OneInputStreamOperator, so it might be tedious to invoke getInputOperatorDefaultMeta().get(0). You might want to rebase the master to see the change FLINK-32053.


Cloud Native should NOT be a category

Cloud native is a characteristic/trait. It doesn't make sense to have a category, because then 90% of the other cards should also be here.
It also gives the false impression that tools that are not there are "not" cloud native.
Isn't Tekton cloud native?
Isn't ArgoCD cloud native?
Isn't Shipwright cloud native?
The current contents of this "category" are unrelated. Terraform is a CLI that implements infrastructure as code, Rancher is a cluster orchestration/management platform, Alibaba is a whole cloud provider, while Ketch is an application for Kubernetes deployments.
Related to https://github.com/cdfoundation/cdf-landscape/issues/175

Point to the CNCF landscape as a embedded landscape link. This will enable us to have the CNCF maintain the landscape for this category.

Make all one Infrastructure Deployments -- remove subcategories.

Closing as remaining work to be done is surfaced in #208.


Adds vm.network

@joechainz Hi Joe, is it possible to help merge this PR? I'm not good with pytest and currently dont have an environment to write integration tests.


How can I render QR Code on a PDF?

I need to render a QR code on a PDF which my end-user can download. FOr creating the pdf I am using react-pdf/renderer.
Here is my code -
import React from "react";
import {Page, Text, View, Document, StyleSheet, Image} from "@react-pdf/renderer";
import { QRCode } from "react-qr-svg";

export function PdfDocument(props) {
    return (
        <Document>
        <Page size="A4">
          <View>
            <Text>Section #1</Text>
          </View>
          <View>
            <Text>Section #2</Text>
            <QRCode
                bgColor="#FFFFFF"
                fgColor="#000000"
                level="Q"
                style={{ width: 256 }}
                value="some text"
            />
          </View>
        </Page>
      </Document>
    );
}

The above gives me the following error -
Error: Invalid element of type rect passed to PDF renderer
What I am doing wrong? How can I render a QR code on the fly onto a PDF?

Hi, from the error message it seems as if the PDF renderer you use does not support rendering of SVG (because rect is a valid SVG element type). You will probably have to use some other PDF renderer or ask for support for your current one.

I see. Thanks for your response @no23reason


Add private github repo e2e test

Changes

This PR made the following changes:

Updated workflow ci.yml file to export secret as an environment variable, which is passed in e2e test
Added build/buildrun yml for testing private github repo
Only keep one set of build/buildrun yml for testing private github repo and deleted others
Added createGithubSSHKeySecret in e2e utils

Submitter Checklist

[ ] Includes tests if functionality changed/was added
[ ] Includes docs if changes are user-facing
[ ] Set a kind label on this PR
[ ] Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.
Release Notes

/retest


Reduce public API before release.

There are many utility methods in core that were written in prep for a
refactor of databroker_to_xarray, some of which are not actually used yet,
and maybe all of which could be moved to event-model because they are
generically useful for manipulating Documents. In prepartion for possibly
moving and/or re-tooling them, I have made them private expect for those
that are imported to drivers.
I also moved tail, which a text-parsing utility only used by the JSONL driver,
into the JSONL driver.

Closes #510

One build passed, two failed on random failures. Re-running those just to be sure.

Looks good to me


Redirect loop

I have this code.Here is the plnkr . http://plnkr.co/edit/FtWBfKaZ9VsCN1tT6nef?p=preview
on the
App.run(function ($rootScope, currentUser, $state, $location) {
$rootScope.$on('$stateChangeStart',
       function (event, toState, toParams, fromState, fromParams) {

           if (localStorage.getItem("Token") == null && toState.name != "loginPage") {
               event.preventDefault();
               $state.go('loginPage', { redirectUrl: toState.name });
               return;
           }

       });

});
The problem is that it goes around and around in a loop, until i get max 10 digest error.My javascript knowledge is rather limited.Can somebody please help me?

well i found the answer.I had to do this, perhaps somebody explain what is going on? and maybhe fix this bug?
$urlRouterProvider.otherwise(function ($injector, $location) { // nasty bug.
var $state = $injector.get("$state");
$state.go("home");
});

Can you post a plnkr example please?

http://plnkr.co/edit/FtWBfKaZ9VsCN1tT6nef?p=preview
here you go.
Open up the console and you can clearly see 10 digest cycles reached.

Duplicate of #2238


separate docs:build

Per your suggestion, and to fix the examples build, which needs both yarn docs:build to build the docs, and yarn build so that the examples can run build/bin/observable.js.

(Maybe we should have generated to docs/.observablehq/dist by default like VitePress does but changing that would be disruptive now.)


Using multiple proxies in one instance does not work

There's some problem when you try load more than one proxy.
I have tried all the proxy one by one and works fine, then try the whole list and...
Failed to request server (error=REQUEST_ERROR, error_source=Error: connect EHOSTUNREACH)
I assume that the format of the proxy list is IP:PORT line break IP:PORT...

yes thats true - did not figgured out the reason behind this - maybe a bug in @camilleeyries 's lib I am using ... others reported the same issue aswell... you can run multiple instances like this:
node feeder.js abc123 0
node feeder.js abc123 1
node feeder.js abc123 2
node feeder.js abc123 3
we need to fix this - if you found a solution please make a pull request

you also can put a NOPROXY line into your socks.txt to use your local ip

fixed in newest version


Occasionally meet exceptions that unable to catch

Verify latest release

[X] I verified that the issue exists in the latest chatgpt release

Verify webapp is working

[X] I verify that the ChatGPT webapp is working properly for this account.

Environment details
  System:
    OS: macOS 13.2
    CPU: (10) arm64 Apple M1 Max
    Memory: 13.99 GB / 64.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.12.0 - ~/Library/Caches/fnm_multishells/32653_1675674566329/bin/node
    Yarn: 3.2.1 - ~/Library/Caches/fnm_multishells/32653_1675674566329/bin/yarn
    npm: 8.19.2 - ~/Library/Caches/fnm_multishells/32653_1675674566329/bin/npm
  Browsers:
    Chrome: 109.0.5414.119
    Safari: 16.3

Describe the Bug
We're using onMessage to display message by chunk, we use a very simple code snippet like:
try {
    const response = await api.sendMessage(
        body.content,
        {
            conversationId: body.conversationId,
            parentMessageId: body.parentMessageId,
            onProgress: response => {
                this.logger.verbose(`[${id}] Partial reply ${JSON.stringify(response.text)}`);
                socket.send(JSON.stringify({event: 'progress', payload: response}));
            },
        }
    );
    this.logger.debug(`[${id}] Reply ${JSON.stringify(response.text)}`);
    socket.send(JSON.stringify({event: 'finish', payload: response}));
}
catch (ex) {
    const payload = ex instanceof ChatGPTError
        ? {statusCode: ex.statusCode, message: ex.message}
        : {statusCode: 500, message: ex instanceof Error ? ex.message : `${ex}`};
    this.logger.warn(`[${id}] Caught HTTP ${payload.statusCode}: ${JSON.stringify(payload.message)}`);
    socket.send(JSON.stringify({event: 'error', payload}));
}

Ocasionally we see errors in our log saying fetch is terminated, this error is not caught by catch clause so our server may crash on unhandled rejections.

We expect all errors be caught, but wondering if SSE fetch or the abort signal stuff can create uncatcheable rejected promises reading response stream

Interesting.
I think I know what might be going on. Just pushed a fix; can you upgrade to https://github.com/transitive-bullshit/chatgpt-api/releases/tag/v4.1.3 and see if that resolve the issue for you?
The other possibility is that the socket is being forcibly closed after the initial HTTP request responds and during the message exchange. There's definitely room to add additional error handling logic here that may not be caught by the wrapping Promise.

Have run the new version for 2 hours, didn't see any crash any more 👍


⚠ Bofrost.de has degraded performance

In 3636307, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 943 ms

Resolved: Bofrost.de performance has improved in e9372a7.


Add predicates to ARAX results summary table

Ask from Chris B -  it would be nice to add predicates to the results summary table (currently Chris has to write code to get that information out of the results, time consuming process.)
Create a ticket for Eric to build that into the ARAX UI.

Being tested in DEV, not quite complete yet. Revisit at the next mini-hack

Predicates per result appear not really feasible in the result table (due to variable length queries) and are better viewed per result. However, @isbluis has now implemented a provenance feature where the union of all predicates (per component) are displayed along with the underlying knowledge sources/providers/aggregators from where they are derived. Eg. hover your mouse on the new "sources" column on this result: https://arax.ncats.io/test/?source=ARS&id=a91b6205-c88a-434e-acb2-a397f4d8dbda or the "Provenance" tab after you've clicked one of the results. Let us know if this is ok to close

Resolved.


Add help option to bot.

A help option would be recommended

What would a help option entail? Are you asking for a command that tells users how to use the bot or>


Harrison, MO

County Assessor Lily Craig charges $200 for the record.
Contact Lila Craig, City Assessor<EMAIL_ADDRESS>

For GIS shapefile Data?

On Mar 19, 2017, at 15:53, ltuff<EMAIL_ADDRESS>wrote:
County Assessor Lily Craig charges $200 for the record.
Contact Lila Craig, City Assessor<EMAIL_ADDRESS>―
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Yes, that is correct and can not be used for resale. For future reference, unless otherwise noted, it is for GIS shapefile or CSV data.

8,000 pop small sized county

no data


fix bpftrace_fuzz error for call to 'get_kernel…_cflags'

When compiling bpftrace_fuzz we run into the following issue where 1 argument is missing, adding the required argument
src/fuzz_main.cpp:140:21: error: no matching function for call to 'get_kernel_cflags'
      extra_flags = get_kernel_cflags(utsname.machine, ksrc, kobj);
                    ^~~~~~~~~~~~~~~~~
src/utils.h:180:26: note: candidate function not viable: requires 4 arguments, but 3 were provided std::vector<std::string> get_kernel_cflags(const char *uname_machine,
                         ^

Seems fourth argument was added via 4bcee640636e268de4b938a1007fb29a8836f049

Checklist

[ ] Language changes are updated in man/adoc/bpftrace.adoc and if needed in docs/reference_guide.md
[ ] User-visible and non-trivial changes updated in CHANGELOG.md
[ ] The new behaviour is covered by tests

Good catch and thanks for the fix. I guess we don't compile bpftrace_fuzz in any CI runs, which is sad.
Mind just fixing the formatting issue? git clang-format upstream/master

Mind just fixing the formatting issue? git clang-format upstream/master

Will do

@jordalgo I have made the required changes, could you please merge, thank you


[Feature Request] Priority order

Is your feature request related to a problem? Please describe.
The software have alot of download options but they do not work well together. The issue is that if you use HD Download then it doesn't download any Images, and both HD and SD Download will skip everything that is Watermarked Only. So if you want to download a full profile and want HD then you may have to run the same text files three times and filter out anything already downloaded. 1. First to get all videos that have HD 2. To get all images Or SD only videos 3. to get any remaining Watermark only files.
Describe the solution you'd like
I would like to see solution that can download everything in one go. Something like a priority order

HD
SD
Watermarked

So IF user wants HD and that does not exist then try to download SD and then watermark as last resort.
And IF user wants SD or ´With watermark` is checked then it would have a higher priority.

I’ll take a closer look at this feature and think about how it can be implemented. Introducing a priority order seems like a good solution to simplify the download process.


Add possibility to disable destination value retrieval on mapping #301

This PR adds possibility to disable destination property value retrieval. Default behaviour isn't changed, so this PR doesn't add any breaking changes.
Possible use cases:

Destination object getters are expensive to be executed.
Destination object getters throws exceptions when the value isn't set yet.

Fixes #301

For some reason the test MultiOccurrenceToMultiOccurrenceTestCase#mappingContext is now failing. I cannot find the root problem because getDestinationOnMapping is always true in this test.
@elaatifi Do you know what could cause it? For some reason assertion on line 227 (Assert.assertNotNull(dest);) is failing.

@elaatifi found a problem with variables and fixed it. TraviCI passes for oraclejdk11.
Failures for oraclejdk8 and oraclejdk9 isn't caused by this PR. It is currently fails in master branch.
mvn clean install with oraclejdk8 passes on my laptop.

No problem, will check them I think it's related to travis jdk's installers

@elaatifi I see you changed oraclejdk to openjdk in master but Travis still fails for openjdk 9. Should I rebase my PR from master branch / wait till Travis passes in master branch or this PR isn't necessary to be rebased?

The command "~/bin/install-jdk.sh ..... failed"
This error is random and on Travis side,  because of jdk.java.net is less reliable nowadays


HTML

HTML
User story
As a bootcamp student
I want the prework notes to be structured on a webpage
Acceptance criteria
GIVEN a prework study guide website
WHEN i vist the website in my browser
THEN I see four boxes titled HTML, CSS, Git, Javascript with associated notes listed

closed


Fix tests for cropped data

Remove hardcoded cell number assertion in NETCDF/GRIB tests.

launch jenkins

launch jenkins

launch jenkins

launch jenkins

launch jenkins


Bootstrap implementation

Incorporating bootstrap of Login page only. The plan is to scratch the main page since it is not as high a priority as something like getting a game to work.

This merge was done in order to complete the branch before implementation of AngularJS and Tornado. From here on out, php will no longer be used.


Double action in fullscreen intent

Discussed in https://github.com/rafaelsetragni/awesome_notifications/discussions/670

Originally posted by Kevinpahlevi November 29, 2022
i am facing this problem when using fullscreen intent, from awesome notifications debug i see there is 2 times action has been triggered
D/Android: [Awesome Notifications]( 7811): New notification creation event (AwesomeEventsReceiver:209)
D/Android: [Awesome Notifications]( 7811): New notification display event (AwesomeEventsReceiver:229)
D/Android: [Awesome Notifications]( 7811): Notification created and displayed in 18ms (NotificationSender:198)
D/Android: [Awesome Notifications]( 7811): New action received (NotificationActionReceiver:36)
D/Android: [Awesome Notifications]( 7811): New notification action event (AwesomeEventsReceiver:249)
D/Android: [Awesome Notifications]( 7811): App is now Foreground (LifeCycleManager:94)
D/Android: [Awesome Notifications]( 7811): New action received (NotificationActionReceiver:36)
D/Android: [Awesome Notifications]( 7811): New notification action event (AwesomeEventsReceiver:249)

and this give different id from notification, because i use random number between 1 - 100 for notification id but i get another action with id more than 100, and this problem so inconsistent
I/flutter ( 7811): NOTIF CLICKED !!!
I/flutter ( 7811): basic_channel
I/flutter ( 7811):<PHONE_NUMBER>
I/flutter ( 7811): gggg
I/flutter ( 7811): NOTIF CLICKED !!!
I/flutter ( 7811): basic_channel
I/flutter ( 7811): 13
I/flutter ( 7811): gggg

i am get  this problem when fullscreen intent only, all work well in foreground and background
AndroidManifest.xml
<uses-permission android:name="android.permission.USE_FULL_SCREEN_INTENT" />
    <uses-permission android:name="android.permission.WAKE_LOCK" />

   <application
        android:label="MyApp"
        android:name="${applicationName}"
        android:usesCleartextTraffic="true"
        android:icon="@mipmap/ic_launcher">
        <activity
            android:name=".MainActivity"
            android:exported="true"
            android:launchMode="singleTop"
            android:theme="@style/LaunchTheme"
            android:configChanges="orientation|keyboardHidden|keyboard|screenSize|smallestScreenSize|locale|layoutDirection|fontScale|screenLayout|density|uiMode"
            android:hardwareAccelerated="true"
            android:windowSoftInputMode="adjustResize"
            android:showWhenLocked="true"
            android:turnScreenOn="true">

Awesome Client
 client.initialize(
        // set the icon to null if you want to use the default app icon
        null,
        [
          NotificationChannel(
            channelGroupKey: 'basic_channel_group',
            channelKey: 'basic_channel',
            channelName: 'Basic notifications',
            criticalAlerts: true,
            channelDescription: 'Notification channel for basic notificaton',
            defaultColor: Color(0xFFD10000),
            ledColor: Colors.white,
            defaultRingtoneType: DefaultRingtoneType.Notification,
            importance: NotificationImportance.Max,
          ),
          NotificationChannel(
            channelGroupKey: 'call_channel_group',
            channelKey: 'call_channel',
            channelName: 'call notifications',
            criticalAlerts: true,
            channelDescription: 'Notification channel for call',
            defaultColor: Color(0xFFD10000),
            ledColor: Colors.white,
            defaultRingtoneType: DefaultRingtoneType.Ringtone,
            importance: NotificationImportance.Max,
          )
        ],
        // Channel groups are only visual and are not required
        channelGroups: [
          NotificationChannelGroup(
              channelGroupKey: 'basic_channel_group',
              channelGroupName: 'Basic group'),
          NotificationChannelGroup(
              channelGroupKey: 'call_channel_group',
              channelGroupName: 'call group')
        ],
        debug: true);

How i use it to show notification
client.createNotification(
        content: NotificationContent(
            id: id,
            channelKey: 'basic_channel',
            title: "$iconNotif $title",
            body: body,
            groupKey: payload,
            fullScreenIntent: true,
            actionType: ActionType.Default));

My awesome and flutter version
  awesome_notifications: ^0.7.4+1

Flutter 3.3.9 • channel stable • https://github.com/flutter/flutter.git
Framework • revision b8f7f1f986 (6 days ago) • 2022-11-23 06:43:51 +0900
Engine • revision 8f2221fbef
Tools • Dart 2.18.5 • DevTools 2.15.0

Can you create a simple example with this issue replicated?

i will try to replicated with example from awesome notification first, maybe i forgot something for config and i see when id < 0 , awesome notification will replace with random number, my current apps already using fcm so maybe i will try using schedule notification to see if apps still get double action in locked device
and for another issue, wakeup and wakelock doesn't work in real device in debug mode or release , but work well in emulator

okay i already found solution for my problem , just need using AndroidForegroundService.startAndroidForegroundService for create notification because my notification using fullScreenIntent and i got one action with normal id notification
  await AndroidForegroundService.startAndroidForegroundService(
        foregroundStartMode: ForegroundStartMode.stick,
        foregroundServiceType: ForegroundServiceType.phoneCall,
        content: NotificationContent(
            id: id,
            channelKey: 'call_channel',
            title: "${Emojis.phone_telephone_receiver} ${title!}",
            body: body,
            groupKey: payloadFirst[0],
            category: NotificationCategory.Call,
            actionType: ActionType.Default,
            fullScreenIntent: true,
            wakeUpScreen: true,
            summary: "$refFirebase||$jwt",
            autoDismissible: false),

and for wakeup i just forget to add wakeUpScreen: true in NotificationContent , i need read again that example 🙂 thank you for awesome package 👍


Swift Package Manager and CLLocationManager extension

I try to use the Swift Package Manager. I have no problem using with the promises classes and functions. But I can't use the CLLocationManager extension. I imported the PromiseKit, but the extensions folder is outside the Sources folder of Swift Package Manager. I think this is the problem. Any suggestion? # #

As per our copious documentation, SwiftPM is not currently supported for the CoreLocation extensions. Feel free to add it here:
https://github.com/PromiseKit/CoreLocation

I guess this is done already in CoreLocation library

Hello @anestis1000
SPM is supported for https://github.com/PromiseKit/CoreLocation, please close the issue.


Replace Concept selector with topic selector in CourseUnit & TextBook unit

Description:
Replace Concept selector with topic selector in CourseUnit & TextBook Unit.
Test Cases and Scenarios:
https://project-sunbird.atlassian.net/browse/SB-6822

Rejected.
Scenarios are not updated in JIRA.
There is no unit-test cases.


Update to FAME-Io v3.0

Request Summary
Update to new FAME-Io which

updates CLI on time-merging
updates FAME-Protobuf dependency
addresses access on formerly private keys in contracts, see _create_contracts()

Use case
Being up-to-date with latest FAME framework.

currently blocked until FAME-Io v3.0 is released, see https://pypi.org/project/fameio/


fix(shared-data): update flex fixed-trash for dvt

This fixed trash bin has changed shapes.
Review requests

is it, like, ok that the position is negative? The depth really does extend below the deck

testing

should drop stuff a lot closer to the trash now

is it, like, ok that the position is negative? The depth really does extend below the deck

We should keep an eye out for motion-planning accidentally clamping positions to 0.
We should also probably figure out a number for the lowest possible z that a pipette can move to, the same way we already have that for the highest possible z.

The negative positions fail protocols in simulation unfortunately. I'll rework this to just have the "above-ground" geometry.

That makes sense, thank you! I think though that we need changes like you mentioned @SyntaxColoring about minimum z positions before we allow a negative position that large, just in case someone tries to go to .bottom() or .center() or whatever. I think we should merge this with above-deck-geometry only for now.


Difference between v0.5.0 and v0.5.1

Depends on connectivity funcs
Requires >1 pop to reproduce (so likely to be related to order of pops for conn?)

Fixed - was 1) differences in param definitons, 2) small bug that created 2 conns to netstims instead of 1


fix: [Auto Routing Improved] one controller method has more than one URI when $translateURIDashes is true

Needs #7406
Description
When $translateURIDashes is true, two URIs correspond to a single controller method,
one URI for dashes (foo-bar) and one URI for underscores (foo_bar).
This is incorrect behavior, contrary to the design philosophy.
This PR prohibits the URI for underscores (foo_bar) when $translateURIDashes is true.
Checklist:

[x] Securely signed commits
[x] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[x] User guide updated
[x] Conforms to style guide

Rebased to resolve conflicts.


cv2.error: /home/pi/opencv-3.1.0/modules/imgproc/src/imgwarp.cpp:3229: error: (-215) ssize.area() > 0 in function resize

face_recognition version:
Python version: 3.4
Operating System: Jesse Raspbian

Description
Whenever I try to run facerec_from_webcam_faster.py, I get the error below. Note that I have checked my local files, the image to be recognized is place appropriately.

OpenCV Error: Assertion failed (ssize.area() > 0) in resize, file /home/pi/opencv-3.1.0/modules/imgproc/src/imgwarp.cpp, line 3229
Traceback (most recent call last):
  File "pj_webcam.py", line 31, in <module>
    small_frame = cv2.resize(frame, (1, 1), fx=0.01, fy=0.01)
cv2.error: /home/pi/opencv-3.1.0/modules/imgproc/src/imgwarp.cpp:3229: error: (-215) ssize.area() > 0 in function resize

This probably means OpenCV wasn't able to grab an image from your webcam. Can you try rebooting your computer and running it again?

Hi,
Rebooted my Raspberry Pi. I am still get the same error.

Oh, this is a raspberry pi. You put macOS in the issue description..
The RPi camera doesn't work with OpenCV like that. There's a separate code example for raspberry pis that uses the picamera module.

Is there any separate code module that can do live video processing on Raspberry Pi similar to this? https://github.com/ageitgey/face_recognition/blob/master/examples/facerec_from_webcam_faster.py

The examples do almost the same thing. The only difference is the opencv example shows the video in a window while it processes it.
If you want to use the OpenCV example on an RPi, you could modify the OpenCV example to replace the part that captures the image:
# Get a reference to webcam #0 (the default one)
video_capture = cv2.VideoCapture(0)

# .. etc ..

while True:
    # Grab a single frame of video
    ret, frame = video_capture.read()

    # Resize frame of video to 1/4 size for faster face recognition processing
    small_frame = cv2.resize(frame, (0, 0), fx=0.25, fy=0.25)

with the equivalent code using picamera:
camera = picamera.PiCamera()
camera.resolution = (320, 240)
small_frame = np.empty((240, 320, 3), dtype=np.uint8)

# ... etc ...

while True:
    print("Capturing image.")
    # Grab a single frame of video from the RPi camera as a numpy array
    camera.capture(small_frame, format="bgr")

And something like that should work.

@ageitgey Thanks for your help. Will definitely try this out.

Cool! 👍


Common string matching patterns to avoid.

@lekoenig has a nice list of string matching omissions that could get added to the disambiguate names function.

Maybe we could just put the example that's a good starting point in an example or vignette?


error handling for store.get

I'm using express-brute with express-brute-mongo. I see occasions when the mongoDB call returns an error (possibly a timeout). This then doesn't get handled smoothly in express-brute/index.js L83-85 and crashes my node instance. I think this should at least pass on the actual error for debugging purposes
this.store.get(key, _.bind(function (err, value) {
  if (err) {
    throw "Cannot get request count";
  }

Yeah, that's a good point. I'm working on a fix that would:

Include the original error in the error object that gets thrown
Allow you to pass your own function to handle store errors if one occurs (and you don't want the error just thrown).

I think for most users having the error thrown is probably the correct answer because a server restart will probably fix the problem, and there is nothing we can do to recover from the error. That said, this is absolutely be a behavior that people should have more control over.
I'm committing it to master now, but I'm still working on tests and such.
Let me know if that sounds like it would solve your issue,

Adam

Yes, that sounds exactly like what I would need.
Thank you!

This should be resolved in v0.5.3 - let me know if you have any issues!

Adam

@AdamPflug thank you for this, very nice!


driver / Update cryogenic magnet driver

Fixes feature request for operation at ScapucciLab (Leiden).
Changes proposed in this pull request:

Add function to go to field specified by positive and negative numbers (bidirectional) instead of setting absolute value and sign (direction) separately
Add convenience function to block until requested field is reached
Change driver to use RAMP ZERO when requesting a to go to exactly 0 Tesla
Extra safety check for switch heater

@WilliamHPNielsen

@WilliamHPNielsen @peendebak
Codacy passes cleanly, but CI gives warnings on parts of the code that I haven't touched.

@mwilmer I think that was fixed by #1081


(waterfox) Get-GitHubRelease require switches

Description
The Get-GithubRelease needs the -owner... switches
Motivation and Context
fixes https://github.com/chocolatey-community/chocolatey-packages/issues/2584
How Has this Been Tested?
On my computer
Screenshot (if appropriate, usually isn't needed):
Types of changes

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Migrated package (a package has been migrated from another repository)

Checklist:

[X] My code follows the code style of this repository.
[ ] My change requires a change to documentation (this usually means the notes in the description of a package).
[ ] I have updated the documentation accordingly (this usually means the notes in the description of a package).
[ ] I have updated the package description and it is less than 4000 characters.
[X] All files are up to date with the latest Contributing Guidelines
[X] The added/modified package passed install/uninstall in the Chocolatey Test Environment(https://github.com/chocolatey-community/chocolatey-test-environment/). Note that we don't support the use of any other environment.
[X] The changes only affect a single package (not including meta package).

:x: Package verification failed, please review the Appveyor Logs and the provided Artifacts before requesting a human reviewer to take a look.


Publish .ipa release?

Hello!
It would be great if the .ipa is available so iOS users can sideload this app using Altstore(iOS 12.2+) or Sideloadly(iOS 7+).
Unfortunately, I can't build it because I don't have a mac or know others who have one.
If it is released, I also hope it can be installed on arm7v 32-bit iOS 9.3 because it's the last OS version available for my device.
Thank you!
Edit: It looks like Flutter SDK versions 2.10.5(Stable), April 2022 and 2.13.0-0.4.pre(Beta), May 2022 were the last releases to support arm7v 32-bit iOS such as my version of iOS 9 based from this document.

.apk release too @tejas-xd

i dont have a mac either


Set a spatial_ref value to 0 instead of EPSG code for better compatibility with rioxarray

Short description
I use odc-geo to reproject and match Landsat 8 QA mask raster to the resolution of the panchromatic band. All the other operations with data are performed using rioxarray.
The issue is that rioxarray sets spatial_ref value to 0 by default, but then odc-geo re-sets that value to the EPSG code of the projection, and, when I mask the original panchromatic band (that was loaded by rioxarray) with QA band (that was reprojected by odc-geo) using xarray.where, spatial_ref coordinate is being dropped.
Libraries import
import xarray
import rioxarray
import odc.geo.xr

Loading the panchromatic band with rioxarray
pan = r"path/to/file/LC09_L1TP_142020_20230825_20230825_02_T1/LC09_L1TP_142020_20230825_20230825_02_T1_B8.TIF"
with rioxarray.open_rasterio(pan, chunks=True, lock=True) as img:
    pan = img

Loading the QA raster with rioxarray
mask = r"path/to/file/LC09_L1TP_142020_20230825_20230825_02_T1/LC09_L1TP_142020_20230825_20230825_02_T1_QA_PIXEL.TIF"
with rioxarray.open_rasterio(mask, chunks=True, lock=True) as img:
    mask = img

Checking the coordinates of the panchromatic band
pan.coords

Coordinates:

band         (band) int32 4B 1
x            (x) float64 128kB 4.689e+05 4.689e+05 ... 7.08e+05 7.08e+05
y            (y) float64 129kB 6.473e+06 6.473e+06 ... 6.232e+06 6.232e+06
spatial_ref  int32 4B 0

More detailed look into spatial_ref
The value is 0, and all the data is stored in the attrs.
pan.spatial_ref

array(0)
Coordinates:
spatial_ref () int32 0
Indexes: (0)
Attributes: (18)
Checking the coordinates of the QA band
mask.coords

Coordinates:

band         (band) int32 4B 1
x            (x) float64 64kB 4.689e+05 4.689e+05 ... 7.08e+05 7.08e+05
y            (y) float64 64kB 6.473e+06 6.473e+06 ... 6.232e+06 6.232e+06
spatial_ref  int32 4B 0

More detailed look into spatial_ref
The value is also 0, and all the data is stored in the attrs.
mask.spatial_ref

array(0)
Coordinates:
spatial_ref () int32 0
Indexes: (0)
Attributes: (18)
Reprojecting the QA band
We reproject the QA band to match the geobox of the panchromatic band.
mask_rep = mask.odc.reproject(pan.odc.geobox)

Checking the coordinates of the reprojected QA band
mask_rep.coords

Coordinates:

band         (band) int32 4B 1
y            (y) float64 129kB 6.473e+06 6.473e+06 ... 6.232e+06 6.232e+06
x            (x) float64 128kB 4.689e+05 4.689e+05 ... 7.08e+05 7.08e+05
spatial_ref  int32 4B 32646

More detailed look into spatial_ref
The value is 32646 - the EPSG code of the projection. More detailed data is still stored in the attrs.
mask_rep.spatial_ref

array(32646)
Coordinates:
spatial_ref () int32 32646
Indexes: (0)
Attributes: (18)
Masking the panchromatic band
Then we use our reprojected mask (mask_rep) to mask the panchromatic band. IRL the function is more complicated, but this minimum example still shows the problem.
pan_masked = pan.where(mask_rep == 0, 0)

Checking the coordinates
The spatial_ref is gone. It must be because the coordinates from two arrays had different values.
pan_masked.coords

Coordinates:

band     (band) int32 4B 1
x        (x) float64 128kB 4.689e+05 4.689e+05 ... 7.08e+05 7.08e+05
y        (y) float64 129kB 6.473e+06 6.473e+06 ... 6.232e+06 6.232e+06

If we use two xarrays loaded with rioxarray, the problem does not appear. If we just simply reassign the coord to 0, (pan_w = pan.where(mask_rep.assign_coords(spatial_ref=0) == 0, 0)) the problem does not appear.
To sum up
Is it really necessary to have a EPSG code of a CRS as a default value for spatial_ref? Maybe just use 0 as a default value like rioxarray does, as the actual CRS data anyway is mostly stored in the attributes, not in the coordinate value itself? Or convince rioxarray devs to also use EPSG code as a default value? I think there should be a common convention for both libraries.

Env

Windows 11 22631.3737
Conda==24.5.0
python==3.11.9
odc-geo==0.4.6
rioxarray==0.15.5
xarray==2024.6.0
rasterio== 1.3.9

@simonreise When using xr.where with mask data computed from pixel values of the original image one should prefer to use "raw numpy arrays" and avoid all the coordinate mismatch nonsense, it's not only spatial_ref issue it can also be slight variations in coordinate locations (+/- 1e-14 difference kinda thing).
In your case just change:
- pan_masked = pan.where(mask_rep == 0, 0)
+ pan_masked = pan.where(mask_rep.data == 0, 0)

But sure, the value stored in the spatial_ref can be changed to always be 0 to match what rioxarray does, we don't really check for that, and in fact rioxarray loaded sources still support .odc.geobox. Not sure this would fix that issue though. xrarray.where()  works best when you provide raw numpy/dask array of the same shape as the xarray data as a mask and not an xarray array.
When mask is an xarray array all the extra work of figuring out "valid overlap", common coords, common dims, common attributes needs to be done by xarray often causing not only slow downs but "unexpected behaviours" like the one you are reporting.

@simonreise can you please check if forcing 0 into spatial_ref fixes the issue in your case or not:
https://github.com/opendatacube/odc-geo/blob/78577dc15f6791e17f18706c5a6bb6ba7a302b77/odc/geo/_xr_interop.py#L216-L221
replace epsg with 0 on line 217 referenced above

Both of your suggestions worked: adding .data to xarray.where and forcing 0 into spatial_ref. Thank you.


docker-multinode allow to change cluster ip range

FLANNEL_NETWORK is config-able, but that's not enough, No way to change dns ip(hard coded) and cluster ip range. So I suggest

Put config outside the container.
Allow use env var to change ip range.

My cloud provider (AliYun) use 10 ip range as internal network, so the default docker-multinode doesn't works with this ip(dns problem, networking communication problem), I have to change the ip range used by docker-multinode(default is 10/8).This took my days to find out the problem.
This is what I do:

Copy /etc/kubernetes outside the container
Replace <IP_ADDRESS> to <IP_ADDRESS> in /etc/kubernetes/master-multi/master-multi.json
Change addon volume in /etc/kubernetes/master-multi/addon-manager.json to

{
        "name": "addons",
        "hostPath": {"path":"/path/to/you/own/etc/kubernetes/"}
}

Change clusterIP in /etc/kubernetes/addon/skydns-svc.yaml to <IP_ADDRESS>
Change all --cluster-dns=<IP_ADDRESS> in common.sh to --cluster-dns=<IP_ADDRESS>
Add -v /path/to/you/own/etc/kubernetes/:/etc/kubernetes/ \ to KUBECTL_MOUNT in common.sh
Then FLANNEL_IPMASQ=false FLANNEL_NETWORK=<IP_ADDRESS>/16 ./master.sh
Done

I assume you provider uses <IP_ADDRESS>/16, right ? I think we should replace the defaults to something less common e.g. <IP_ADDRESS>/16
Making everything configurable that is acceptable to everyone is a bit more complicated. But it will be addressed rather soon

My provider use <IP_ADDRESS>/22(HuaDong2 region),<IP_ADDRESS>/21(HK region),<IP_ADDRESS>/23(Another HuaDong2 region),I am not sure we will never overlap(<IP_ADDRESS>/16),quite uncommon ha 😂.AliYun is the main provider in China.
Making everything(dns,proxy,dashboard,api,kubectl... and more in future) configurable(move .yaml/.json *.sh out of container) and have a good default value will let docker-multinode go farther.

Feel free to make a PR of what you're planning and we'll see :)

I don't see an overlap in the IP ranges.....
(btw I am on holidays)

I setup a multi-node cluster , and I can see some info using curl http://ip:8080,
but  kubectl returns nothing ,  what's wrong with this ?

@cheld Cluster use 10/8, server use 10/22, flannel use <IP_ADDRESS>/16, they do overlap.

Hi, are there instructions on what changes need to be made in order to switch to another ip range? When executing the master.sh it freezes at

+++ [0905 21:05:02] Launching docker bootstrap...
+++ [0905 21:05:04] Launching etcd...
8213a56270bc10251aaa7a6e0a0f5f46d605985d113fa9468066a9ab80f6cd0a
+++ [0905 21:05:07] Launching flannel...
{"action":"set","node":{"key":"/coreos.com/network/config","value":"{ "Network": "<IP_ADDRESS>/16", "Backend": {"Type": "udp"}}","modifiedIndex":4,"createdIndex":4}}
9328aa0ccdfbca13b2b209fae9c1545803dd0c1971398a2bfc6554ef6ac02e07
+++ [0905 21:05:07] FLANNEL_SUBNET is set to: <IP_ADDRESS>/24
+++ [0905 21:05:07] FLANNEL_MTU is set to: 1472
+++ [0905 21:05:07] Restarting main docker daemon...
+++ [0905 21:05:09] Restarted docker with the new flannel settings
+++ [0905 21:05:09] Launching Kubernetes master components...

Unfortunately repeating the steps of the original post does not work for me. My servers are using 10/8 range for internal IPs.
Changing the FLANNEL_NETWORK to 192.168/17 AND --cluster-dns=<IP_ADDRESS> in common.sh to e.g. --cluster-dns=<IP_ADDRESS> (outside FLANNEL_NETWORK!) makes master.sh run. But the dns service is not working (tested with https://github.com/kubernetes/kubernetes/tree/release-1.2/cluster/addons/dns#how-do-i-test-if-it-is-working )

docker-multinode was removed in https://github.com/kubernetes/kube-deploy/pull/283 so I'm closing this issue as obsolete.