Fix for unit test: check for different error message in INTEL MKL enabled Tensorflow

In INTEL MKL enabled flow, the error shown is different from XLA/Eigen flow. This causes one of the unit tests to fail in INTEL MKL enabled flow. The fix addresses this case.
Failing test :/tensorflow/python/kernel_tests/conv_ops_test.py (testOpEdgeCases)

Please close this PR, as it is replaced by a more recent one
https://github.com/tensorflow/tensorflow/pull/43590

@jojivk73 Can you please check the above comment from @gzmkl and give confirmation to close this PR?

@gbaned  Please close this PR, as it is replaced by a more recent one
#43590

@jojivk73 Can you please check the above comment from @gzmkl and give confirmation to close this PR? Thanks!

No response from @jojivk73, hence closing the PR. Thanks!


Ldaps wit ca self signed

Environment

OS: Ubuntu 20.04.4 LTS.
Kubernetes/K3s: k3s version v1.22.7+k3s1
AWX Operator: 0.22.0

Description
Cannot use ldaps with ca self signed.
i've always same error on awx-web container :
2022-06-14 09:49:59,087 WARNING  [7364d930a2694d95b811887768349fc0] django_auth_ldap Caught LDAPError while authenticating fferraro87: SERVER_DOWN({'result': -1, 'desc': "Can't contact LDAP server", 'errno': 107, 'ctrls': [], 'info': 'Transport endpoint is not connected'})

Step to Reproduce

i've added to kustomization.yaml :  - name: awx-custom-certs
 type: Opaque
 files:
   - ldap-ca.crt=/root/francesco/awx-on-k3s/base/ca1.ad.francesco.it.pem
   - bundle-ca.crt=/root/francesco/awx-on-k3s/base/ca1.ad.francesco.it.pem

and on awx.yaml

   ldap_cacert_secret: awx-custom-certs
  bundle_cacert_secret: awx-custom-certs

kubectl apply -k base

On secrets, there are
awx-custom-certs                              Opaque                                2      10d
root@automation:~/francesco/awx-on-k3s# kubectl describe secret awx-custom-certs -n awx
Name:         awx-custom-certs
Namespace:    awx
Labels:       <none>
Annotations:  <none>

Type:  Opaque

Data
====
ldap-ca.crt:    2390 bytes
bundle-ca.crt:  2390 bytes

but i've always same error.
i've try also to disable on awx.yaml LDAPTLS_REQCERT with this :
spec:
 .
 .
 .
  web_extra_env: |
    - name: LDAPTLS_REQCERT
      value: never

but still nothing, do you've an idea on how can i use ldaps?
thanks

@fferraro87
Hi, thanks for filling the issue.
Does your CA cert file have PEM format correctly? I mean, not just the extension *.pem, but the content of the file has to be in PEM format. Ensure your file starts and end up with:
$ cat /root/francesco/awx-on-k3s/base/ca1.ad.francesco.it.pem
-----BEGIN CERTIFICATE-----
...
-----END CERTIFICATE-----

And ensure you've specify ldaps:// in AWX correctly.
If possible, can we try the connection with LDAP instead of LDAPS to see if it is a certificate issue in the first place? Since the error message around LDAP is unfriendly, it's difficult to determine the cause is certainly certificate related one by only the message you provided.

Hi,
thanks for you reply, yes pem file is like you said.
i've check also inside
kubectl get secrets awx-custom-certs -o jsonpath="{.data}" -n awx
i've decoded both bundle-ca.crt and ldap-ca.crt and it start with
-----BEGIN CERTIFICATE-----
...
-----END CERTIFICATE-----

and on AWX i've set LDAP Server URI ldaps://dc1.ad.francesco.it:636
and with 389 ldap everything works (i attach log from awx-web container)
022-06-15 07:04:08,627 DEBUG    [f7aa897273aa47e59d1aeb707c33d218] django_auth_ldap search_s('ou=staff,dc=ad,dc=francesco,dc=it', 2, '(sAMAccountName=%(user)s)') returned 1 objects: cn=fferraro87,ou=staff,dc=ad,dc=francesco,dc=it

Hi, thanks for updating.
Okay, so if the port 636 is opened for external access on your LDAP server, it seems certainly SSL related issue. I guess the certificate chain for your LDAP server can't be determined.
You can verify the certs invoking openssl command inside the pod.
# Get Bash shell of the `awx-web` container
$ kubectl -n awx exec -it deployment/awx -c awx-web -- bash
bash-5.1$      👈 Now you are in the container

# Ensure CA cert is mounted.
# The secret ldap_cacert_secret is mounted as /etc/openldap/certs/ldap-ca.crt
# and the secret bundle_cacert_secret is mounted as /etc/pki/ca-trust/source/anchors/bundle-ca.crt
bash-5.1$ cat /etc/openldap/certs/ldap-ca.crt
bash-5.1$ cat /etc/pki/ca-trust/source/anchors/bundle-ca.crt

# Test SSL connection to your LDAPS server using /etc/openldap/certs/ldap-ca.crt
bash-5.1$ openssl s_client -connect dc1.ad.francesco.it:636 -no-CAfile -CAfile /etc/openldap/certs/ldap-ca.crt

If your cerificate chain is correctly built, the output should look like:
bash-5.1$ openssl s_client -connect dc1.ad.francesco.it:636 -no-CAfile -CAfile /etc/openldap/certs/ldap-ca.crt
depth=1 DC = ****, DC = ****, CN = ****
verify return:1
depth=0 CN = ****
verify return:1
---
Certificate chain
 0 s:CN = ****
   i:DC = ****, DC = ****, CN = ****
   a:PKEY: rsaEncryption, 2048 (bit); sigalg: RSA-SHA256
   v:NotBefore: Jun 15 11:56:01 2022 GMT; NotAfter: Jun 15 11:56:01 2023 GMT
---
...omit...
...omit...
...omit...
---
SSL handshake has read 2066 bytes and written 502 bytes
Verification: OK      👈👈👈 No verification error
---
New, TLSv1.2, Cipher is ECDHE-RSA-AES256-GCM-SHA384
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
    Protocol  : TLSv1.2
    Cipher    : ECDHE-RSA-AES256-GCM-SHA384
    Session-ID: A4220000D3234AFDA571A5C59648A727886D28FF837ABCD83BB03AB9FE1A8066
    Session-ID-ctx:
    Master-Key: 1FDAC63FD4A71AD80C9CED369E562DA0554885EE40A8E2316A8FC8F5D743E05D385CEE21BB7A545838A1FD23316A05F5
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    Start Time:<PHONE_NUMBER>
    Timeout   : 7200 (sec)
    Verify return code: 0 (ok)      👈👈👈 No verification error
    Extended master secret: yes

If the chain can't be built, you get:
bash-5.1$ openssl s_client -connect dc1.ad.francesco.it:636 -no-CAfile -CAfile /etc/openldap/certs/ldap-ca.crt
CONNECTED(00000003)
depth=0 CN = ****
verify error:num=20:unable to get local issuer certificate      👈👈👈 Chaining error
verify return:1
depth=0 CN = ****
verify error:num=21:unable to verify the first certificate      👈👈👈 Chaining error
verify return:1
depth=0 CN = ****
verify return:1
---
...omit...
...omit...
...omit...
---
SSL handshake has read 2066 bytes and written 502 bytes
Verification error: unable to verify the first certificate      👈👈👈 Chaining error
---
New, TLSv1.2, Cipher is ECDHE-RSA-AES256-GCM-SHA384
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
    Protocol  : TLSv1.2
    Cipher    : ECDHE-RSA-AES256-GCM-SHA384
    Session-ID: 1E060000C3EDF2626E47CC7798816C63BF82C08F41BD64D94A4A781E736240BC
    Session-ID-ctx:
    Master-Key: 16C5557C601DAC9263A27408041EDA4A00363B34258D585771BDBE8E6378AA37DDF688CBAC8E4F3D5B0BC8924C83C5A3
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    Start Time:<PHONE_NUMBER>
    Timeout   : 7200 (sec)
    Verify return code: 21 (unable to verify the first certificate)      👈👈👈 Chaining error
    Extended master secret: yes

i've this output
bash-5.1$ openssl s_client -connect dc1.ad.francesco.it:636 -no-CAfile -CAfile /etc/openldap/certs/ldap-ca.crt
CONNECTED(00000003)
write:errno=104
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 0 bytes and written 319 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
---

So verification is ok but it seems miss all other parameters

Ah I see, so, um, the output means that your LDAP server does not listen LDAPS... It's not over SSL but just plain LDAP.
Maybe you can get completely same output when you test connection to dc1.ad.francesco.it:389 that is plain LDAP port.
bash-5.1$ openssl s_client -connect dc1.ad.francesco.it:389 -no-CAfile -CAfile /etc/openldap/certs/ldap-ca.crt

I think your LDAP server is Active Directory, right? If so, the default LDAP service on Active directory is listening plain LDAP on  LDAPS port (636). So you (or your team) have to configure AD as truly LDAPS server by adding certificate for AD DS service.

but it's a strange thing because if i test from another vm (centos 7) openssl i receive this output:
[root@vmtest01 ~]# openssl s_client -connect dc1.ad.francesco.it:636 -CAfile ca1.ad.francesco.it.pem  -state -nbio
CONNECTED(00000003)
turning on non blocking io
SSL_connect:before/connect initialization
SSL_connect:SSLv2/v3 write client hello A
SSL_connect:error in SSLv2/v3 read server hello A
write R BLOCK
SSL_connect:SSLv3 read server hello A
depth=1 DC = it, DC = francesco, DC = ad, CN = francesco CA
verify return:1
depth=0
verify return:1
SSL_connect:SSLv3 read server certificate A
SSL_connect:SSLv3 read server key exchange A
SSL_connect:SSLv3 read server certificate request A
SSL_connect:SSLv3 read server done A
SSL_connect:SSLv3 write client certificate A
SSL_connect:SSLv3 write client key exchange A
SSL_connect:SSLv3 write change cipher spec A
SSL_connect:SSLv3 write finished A
SSL_connect:SSLv3 flush data
SSL_connect:error in SSLv3 read finished A
SSL_connect:error in SSLv3 read finished A
read R BLOCK
SSL_connect:SSLv3 read finished A
read R BLOCK
---
Certificate chain
 0 s:
   i:/DC=it/DC=francesco/DC=ad/CN=francesco CA
---
Server certificate
-----BEGIN CERTIFICATE-----
...
-----END CERTIFICATE-----
subject=
issuer=/DC=it/DC=francesco/DC=ad/CN=francesco CA
---
Acceptable client certificate CA names

/C=IT/ST=Perugia/L=Perugia/O=francesco S.p.A./CN=*.ad.francesco.it
/CN=newdc1.ad.francesco.it
/DC=it/DC=francesco/DC=ad/CN=francescoCA2
/DC=it/DC=francesco/DC=ad/CN=francesco CA
/C=SE/O=AddTrust AB/OU=AddTrust External TTP Network/CN=AddTrust External CA Root
/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert Assured ID Root CA
/C=US/O=The Go Daddy Group, Inc./OU=Go Daddy Class 2 Certification Authority
/C=US/ST=New Jersey/L=Jersey City/O=The USERTRUST Network/CN=USERTrust RSA Certification Authority
/C=US/O=VeriSign, Inc./OU=VeriSign Trust Network/OU=(c) 2008 VeriSign, Inc. - For authorized use only/CN=VeriSign Universal Root Certification Authority
/C=US/O=VeriSign, Inc./OU=VeriSign Trust Network/OU=(c) 2006 VeriSign, Inc. - For authorized use only/CN=VeriSign Class 3 Public Primary Certification Authority - G5
/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert High Assurance EV Root CA
/C=US/O=VeriSign, Inc./OU=Class 3 Public Primary Certification Authority
/OU=GlobalSign Root CA - R2/O=GlobalSign/CN=GlobalSign
/C=US/O=GTE Corporation/OU=GTE CyberTrust Solutions, Inc./CN=GTE CyberTrust Global Root
/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert Global Root CA
/C=US/O=Starfield Technologies, Inc./OU=Starfield Class 2 Certification Authority
/C=BE/O=GlobalSign nv-sa/OU=Root CA/CN=GlobalSign Root CA
/C=IE/O=Baltimore/OU=CyberTrust/CN=Baltimore CyberTrust Root
/OU=GlobalSign Root CA - R3/O=GlobalSign/CN=GlobalSign
/C=US/O=GeoTrust Inc./CN=GeoTrust Global CA
/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert Global Root G2
/C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft Root Certificate Authority 2010
/C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft Root Certificate Authority 2011
/OU=Copyright (c) 1997 Microsoft Corp./OU=Microsoft Corporation/CN=Microsoft Root Authority
/DC=com/DC=microsoft/CN=Microsoft Root Certificate Authority
/CN=NT AUTHORITY
Client Certificate Types: RSA sign, DSA sign, ECDSA sign
Requested Signature Algorithms: RSA+SHA512:ECDSA+SHA512:RSA+SHA256:RSA+SHA384:RSA+SHA1:ECDSA+SHA256:ECDSA+SHA384:ECDSA+SHA1:DSA+SHA1
Shared Requested Signature Algorithms: RSA+SHA512:ECDSA+SHA512:RSA+SHA256:RSA+SHA384:RSA+SHA1:ECDSA+SHA256:ECDSA+SHA384:ECDSA+SHA1:DSA+SHA1
Peer signing digest: SHA1
Server Temp Key: ECDH, P-256, 256 bits
---
SSL handshake has read 5106 bytes and written 483 bytes
---
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES256-SHA384
Server public key is 1024 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
    Protocol  : TLSv1.2
    Cipher    : ECDHE-RSA-AES256-SHA384
    Session-ID: ...
    Session-ID-ctx:
    Master-Key: ...
    Key-Arg   : None
    Krb5 Principal: None
    PSK identity: None
    PSK identity hint: None
    Start Time:<PHONE_NUMBER>
    Timeout   : 300 (sec)
    Verify return code: 0 (ok)
---

yes we've active directory.
But how can i add
TLS_REQCERT     never
on ldap.conf inside container?

Hmm, strange... Then check same connectivity not from awx-web container, but from your K3s host, please?
If openssl on your K3s host can't be established, your issue is not related to AWX. Seems your AD validates client-side certificate?

But how can i add
TLS_REQCERT never
on ldap.conf inside container?

You can create Config Map and add it to the Pod as a volume to override default ldap.cert, but for the time being, I would like you to try to see if you can communicate with your AD properly from the K3s host.

Hi,
nope also from k3s host i've same output...but i see that from all ubuntu 20.04 vm i've same output with a wrong connection like i said before but from centos or redhat i've correct output like i say on post before.
so i think maybe that's a cipher used by openssl command on ubuntu, that's maybe different from openssl on centos or redhat

Thanks for your support i know that's out of scope of this repo so thanks again!
yes i'll ask to my colleagues to check on ad server about this problem.
Thanks again

@fferraro87
Thanks for updating, I hope my minimal code could help you...
If you have solved the issue and if you have time, please let me know the root cause of this and how to solve this. I'm interested in technical details of this. Thanks, enjoy your automation 😃

This post help me a lot today!!!
Very thx guys!!


Create dataset/partition COPY operation

In order to build proto GSDs and for further yet unknown use it would be really useful to be able to copy an entire dataset partition with all its data into a new dataset with a new key.
For catalogues this should optionally include to duplicate all global entities (sectors, decisions, estimates) or remove them. This is very much what a catalogue release already does, but probably without the issuing of new, stable keys

done and available at /dataset/copy


Update effective-level to v1.1

Adds invisible non-combat boosts such as celestial ring/signet (+4 mining), crystal saw (+3 construction) and skilling guilds (+7 fishing, mining, woodcutting).

It looks like you have done this change wrong, unless you meant to create an additional config and plugin file at the root of your project.

Thank you for pointing that out. This has now been fixed and tested


Add editors from the edit crate

The edit crate has excellent support for various platform-specific editors, both TUI and GUI. It would be great if we could bring this to dialoguer::Editor.

Maybe we can remove edit feature from this crate instead and point towards that one?

That works too.


Master

Description:
Related issue (if applicable): fixes #
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Example entry for configuration.yaml (if applicable):

Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[x] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

Suggest you close this PR and open a new one with the changes you have in mind.
Also fill out the the description field with the requested information.

e


Check whether all the endpoints still working correctly.

Done with this. All issues regarding this is registered in Github.


dockerswarm_sd_configs - is it possible to remove targets that no longer satisfy filtering rules?

What did you do?
I have a dockerswarm_sd_configs set keep only targets with __meta_dockerswarm_task_desired_state set to running, and it works fine, but when I surf the prometheus GUI I see

and the presence of those 33.200 targets (no longer running, but in shutdown) generate a lot of noise (the service discovery web page is 240Megabytes!)
What did you expect to see?
No response
What did you see instead? Under which circumstances?
I would like a way to remove that noise
System information
docker swarm with Ubuntu 22.04.4 LTS nodes
Prometheus version
image: quay.io/prometheus/prometheus:v2.32.1

Prometheus configuration file
- job_name: 'docker_tasks'
    dockerswarm_sd_configs:
      - host: http://dockersocket.backplane:2375
        role: tasks
    relabel_configs:
      #
      # Make sure that the running state filter is applied first. This is crucial because Prometheus processes relabel_configs sequentially.
      #
      # Only keep containers that should be running.
      # filtering out any stopped or inactive tasks.
      - source_labels: [__meta_dockerswarm_task_desired_state]
        regex: running
        action: keep
      # Only keep containers that have a `prometheus.enable` label.
      - source_labels: [__meta_dockerswarm_service_label_prometheus_enable]
        regex: true
        action: keep
      # Use the swarm service name as Prometheus job label.
      - source_labels: [__meta_dockerswarm_service_name]
        target_label: job
      # constructs the instance label by combining the service name and the task slot, which helps in identifying individual tasks within a service.
      - source_labels: [__meta_dockerswarm_service_name, __meta_dockerswarm_task_slot]
        regex: "([^;]+);(.*)"
        replacement: $1.$2
        target_label: instance
      # Scraping metrics via a certain network only
      - source_labels: [__meta_dockerswarm_network_name]
        regex: backplane.*
        action: keep
      # Adding a docker_node label to the targets
      - source_labels: [__meta_dockerswarm_node_hostname]
        target_label: docker_node
      # modifies the target address for scraping by replacing the default address with the service's specified Prometheus
      # port, ensuring that Prometheus scrapes metrics from the correct endpoint
      - source_labels: [__address__, __meta_dockerswarm_service_label_prometheus_port]
        regex: "([^:]+):[^;]+;(.*)"
        replacement: $1:$2
        target_label: __address__

### Alertmanager version

_No response_

### Alertmanager configuration file

_No response_

### Logs

_No response_

Hi,
I've just update to v2.54
<     image: quay.io/prometheus/prometheus:v2.54.1
---
>     image: quay.io/prometheus/prometheus:v2.32.1

but my service discovery gui still shows

am I suppose to trigger somehow the new fix?

ah, ... :(
I still have over 33K, oh, well, even more today

today
any suggestion on how to  reduce it?

I've added it and it's visible in my config in GUI

but I still see
docker_tasks (98 / 33473 active targets)

Ah, yes, you are super right!
I still see

but if I click on

I only see 100 jobs
Thank you!


Move repositories to organization?

What do you guys think about moving all repositories (behavior3editor|behavior3js|behavior3py) to behavior3 organization? I already created the organization but I want to hear your opinions before migrating. (this would happen before the next release, +- 2/3 weeks)
IMO, this makes the project looking more "professional" and less like a personal tool.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/20470847-move-repositories-to-organization?utm_campaign=plugin&utm_content=tracker%2F11194799&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F11194799&utm_medium=issues&utm_source=github).

It wouldn't bother me, so long as it's well organized and you're really planning on making this a permanent thing outside of your current research. Otherwise, you might as well keep it personal, in my opinion.
You've done a good job with the rest of the support materials on http://behavior3js.guineashots.com/ site. Maybe a point of confusion is that your new organization doesn't match the website domain, unless you are planning on changing the domain as well?
On a side note, if you're moving to a new organization, perhaps this is a chance to add it to Bower as a modular library. I had half-decided to implement my own version for modularity, code style, and personal educational reasons, but it was the lack of bower support that tipped me toward the decision to write my own code.
Thanks for making the library and backing resources available. It's been really helpful to me!

@daveseah Thanks for the feedback Dave,
Yes, I using this project for my research but it's bounded to it. So, I hope to keep working even after my PhD.
and Yes, I will redirect everything to http://behavior3.com/ (site under development).
Do you mean, add the editor to bower? How would this work? Bower always seemed to me for libraries (like beahvior3js). If you mean the behavior3js, it is already on bower.

@renatopp Regarding Bower...my mistake! You're right...behavior3js, not the editor, belongs on bower.  Now I can't remember why I didn't use it...will have to check my journal!

That's ok. If I hear no arguments against it, I'm going to move the repositories next week.

All projects have been moved to:
https://github.com/behavior3

I'm closing all issues here.


Adds administrative region terms

Closes #243. This adds the new administrative region terms and restores part of the ENVO import hiearchy to match ENVO, i.e.
'site' > 'administrative region'
instead of
'site' > 'geographic location' > 'administrative region'.

May send request to ENVO for 'fifth-order administrative region'.


(Kia EU) Push notification integration

It looks like an integration of Google Cloud Messaging was attempted at some point by @fuatakgun :
        try:
            credentials = push_receiver.register(sender_id=self.GCM_SENDER_ID)
            registration_id = credentials["gcm"]["token"]
        except:
            pass

push_register is a Google Cloud Messaging (GCM) / FIrebase Cloud Messaging (FCM) client library.
I assume the intended application was to retrieve push notifications the way the native app does it.
This was removed in new releases. Why?

Orignally this code came from here https://github.com/fuatakgun/kia_uvo/blob/master/custom_components/kia_uvo/KiaUvoApiEU.py
I believe it was removed because push_receiver as a library is no longer supported and has deprecated libraries so was a ticking time bomb on some of our users systems.
https://github.com/fuatakgun/kia_uvo/issues/345

In theory a new fork of push_receiver could be created with updated dependencies to continue that approach.

OK. I looked around and found other similar libraries.
In theory there could be useful use cases for a notification client.
We'd need to check how it works in practice. I believe each client (mobile app) or user has a unique ID/token, and it may not be easy to obtain.


cmd/cue: revisit get go embedding logic

What version of CUE are you using (cue version)?

$ cue version
cue version +aa61ee7f linux/amd64

Does this issue reproduce with the latest release?
Yes
What did you do?
https://github.com/cuelang/cue/issues/848 raises a question about whether the CUE generated by cue get go (which will become cue import go under #646) is in fact valid. #848 has been closed as "working as intended" but per https://github.com/cuelang/cue/issues/848#issuecomment-805006596 it does appear to raise a couple of issues/questions.
The cue help get go text talks about the JSON inline tag:
        - embedded structs marked with a json inline tag unify with struct
          definition. For instance, the Go struct

However, this tag does not exist as part of encoding/json, it only exists as a proposal: https://github.com/golang/go/issues/6213. This tag does however exist as part of gopkg.in/yaml.v1 and later major versions.
My suggestion would therefore be that we drop this rule for the inline tag and instead, by default, adopt the semantics implied by JSON marshalling. Consider this example:
https://gist.github.com/myitcv/fbf930c45892bbbc22cced812bfbe346
This demonstrates how:

encoding/json marshals values of types S1 and S2 identically, regardless of the presence of the inline tag
encoding/json respects the embedding of T1 and T2 in both S1 and S2, hence values s1 and s2 marshal to the same value (see stdout.golden)
cue get go does behave differently depending on the inline tag: see how #S1 and #S2 differ in main_go_gen.cue.golden

But this raises one further question. The sigs.k8s.io types referenced in #848 have lots of Yaml tags, which implies these values of these types are fairly regularly marshalled to/from Yaml. Given the proposed change in struct rules above, this might well imply a number of users would be discontent with the default:

The rules for Yaml marshalling differ from JSON
There is not a Yaml package in the standard library (https://pkg.go.dev/gopkg.in/yaml.v3 perhaps comes closest)

This seems to point to another requirement: that the caller of cue get go should be able to specify the "rules" applied during the conversion. By default, encoding/json semantics would be applied, with further options available (perhaps in future we could define what it would mean for a Go package to implement and "interface"/API for such conversions?) behind a flag.
cc @nyarly and @verdverm from #848

Some thoughts

Go struct tags are much like CUE attributes, in that they are purely string based metadata for tools build to read the languages code. There are many Go tools & libraries which make use of these in interesting ways. A JSON inline tag is an interesting grey area case...
Marshalling and Import (get go) are quite different processes. I would think that we want an import to make use of as much information as possible, including any extra struct tags, anti-unification, user driven edge cases, patterns, and overrides through a to-be flag... and also the cue.mod/usr dir
What happens in your example if T1 and T2 share a field name and have the inline tag? This would seem problematic... but what is the user intention here? Could it be to merge some schemas which have some overlap, or unmarshal the same field into multiple structs? I'll have to think on this more in the import vs marshal comparison...
Sane, consistent, and workable default behavior is always a win. Definitely like the idea of users configuration on the import process. Might tie in well if we consider it with a --out go for structs (and/or) import/export for other languages?
If we drop inline, are there cases where a breakage occurs? Do we already have a test that might show this?

This issue has been migrated to https://github.com/cue-lang/cue/issues/1026.
For more details about CUE's migration to a new home, please see https://github.com/cue-lang/cue/issues/1078.


I can confirm that the CyberChef versions after 8.8.1 are not loading after saved to the local drive

Summary
CyberChef versions after 8.8.1 version which is stable, will not load after being downloaded on the local drive. Browsers used Chrome 70 and Edge
Unable to set property 'cptable' of undefined or null reference
Filename: blob:null/b2e7a418-53a6-4ebf-9505-eac8f093f0a5
Line: 1828
Column: 785599
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Edge/17.17134
CyberChef version: 8.8.5s
Example

Seeing the same behavior here

Same here with Firefox 62.0:
TypeError: e is undefined
Filename: blob:null/018fe1d6-b1f4-4be4-b313-80f76cca07f2
Line: 1828
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:62.0) Gecko/20100101 Firefox/62.0
CyberChef version: 8.8.5s

This appears to be related to #388

Fixed in #403. Thanks to @bwhitn.


Disable package-lock.json

@gurgunday thanks! This looks good.

Well, it should be fine if SemVer is respected by the dependencies
You mean reproducibility after cloning right? Cause package-lock isn't included in the NPM registry anyway

Right now, do you have any issues when you clone the repository and do an npm i?
Look, this is one of those subjects where there isn't a single right way to go about things — it's subjective!
If maintainers don't regularly update the lock file, you end up with vulnerable packages. Also, when you say typically, you need to provide some examples, because from what I see, typically, it's kinda the norm to remove it for libraries.
In any case, I don't have a strong opinion on this matter, so you can ask @nebrelbug to get a definitive answer.

@gurgunday @legobeat I appreciate the discussion about this issue.
I think a lot of the benefits of having a package-lock.json don't necessarily apply in this case, since Eta has no direct dependencies -- just development dependencies. This means that users won't get notified about security vulnerabilities when installing Eta which aren't necessarily relevant.
I do think it's worth considering adding back package-lock.json just because -- depending on how we set up CI -- it could speed up builds. Let's add this to the list of todo items for v3. We can evaluate further after we design the v3 CI build process, which I want to migrate entirely to GitHub Actions.


[UnitaryHack] Implementation of Nelder Mead Optimizer

Purpose
Implemented the Nelder Mead Optimizer.
Details
The optimizer along with tests. Also added the jupyter notebook used to test the optimizer. I have used 200 epochs instead of 100 as the optimizer required more epochs for convergence. This PR resolves #85.
Results
I ran two tests with adaptive equal to True and False for 200 epochs.

adaptive=False, final output is 0.98555, 0.01445

adaptive=True, final output is 0.96625, 0.03375

@Gopal-Dahale Hi and thanks for this. There are some linting errors, could you fix them?

Hi @dimkart, I have formatted the code and ran the two commands locally and both of them now give 0:

flake8 lambeq --max-doc-length=74
flake8 lambeq --count --isolated --select=E9,F63,F7,F82 --show-source --statistics

Hi @dimkart, I see type check with mypy has failed. I'll fix it. Meanwhile, is there documentation on how to build and test lambeq locally so that I don't have to rely on GitHub actions until I fix them all locally?

Thanks. I have fixed the mypy issue and now it gives Success: no issues found in 58 source files.

Hi, @Thommy257 @ianyfan can you resolve the conversations?

@Gopal-Dahale Hi, thanks for taking the time to respond to all comments -- the conversations will be resolved tomorrow by Ian and Thomas.

Hi @ianyfan, I had updated the code as per your comments. Can you resolve the conversations?


Can't confirm Netlify CMS account

Describe the bug
When we click in the invitation email (from Netlify) to register our account, we arrive on our homepage and that's all. The invitation link is not working.
To Reproduce
Steps to reproduce the behavior:

Go to Netlify CMS > Identity > Invite user > Type my email
Click on the Accept the invite link
Arrive in my homepage : https://website.com/#invite_token=blablablabla
Nothing happen

Expected behavior

Go to Netlify CMS > Identity > Invite user > Type my email
Click on the Accept the invite link
Arrive in my homepage : https://website.com/#invite_token=blablablabla
A form should appear to ask our password. I know it because if I manually change the link to https://website.com/admin/#invite_token=blablablabla, it ask me to type in my (future) password

Our index page does not contain the widget and it should be (cf https://www.netlifycms.org/docs/hugo/#authenticating-with-netlify-identity)
Technical details:

Academic Version: v4.8 upgraded from 4.3 (by doing cd themes/academic && git checkout v4.8.0)
Hugo Version: 0.68.3 (via Netlify)
Browser/OS: Chrome 80.0.3987.163
website : flolaco.ovh

it seems that there is an "issue" with the tagged version v4.8.
commit https://github.com/gcushen/hugo-academic/commit/5738cdd41e547d6527c1d30816ee82b55d57dedd (and https://github.com/gcushen/hugo-academic/commit/42d0e5f8cd130e52e2dfa496c199229a9f12d8cb) is adding the support of netlify CMS but this commit is not part of the v4.8

Yes, there is an option in the master branch to enable Netlify Identity without adding it separately in the custom head/js hooks.

@gcushen yes but the bigger problem is that the site_head.html (which contains netlify widget) is also on master branch and not on tag v4.8.0


Feed Management Enhancements : READ and UPDATE lifecycleEvent

Feed Management Enhancements for Kafka feed
This issue is an Epic to collect all the related tasks to implement the final solution for kafka
For some background on feeds and lifecycles refer to https://github.com/apache/incubator-openwhisk/blob/master/docs/feeds.md
This features are based on user feedback
Feature Requests

Allow the user retrieve trigger information from the feed provider

This allows the user to get back the original config
This allows the user to get the current status of the trigger

Allow the user to update the trigger configuration on the feed provider without the need to delete and re-create the trigger with a new configuration

Lifecycle Events
Today this feed implements the lifecycle events CREATE and DETELETE
To implement the features requested above the this feed would need to implement the lifecycle events READ, UPDATE
READ lifecycle
The feed action should accept the parameter lifecycleEvent with the value of READ.
It should return the configuration and status for the trigger, for example:
{
  "config":{
    "triggerName": "_/myKafkaTrigger",
    "isMessageHub": true,
    "topic": "mytopic",
    "isJSONData": true,
    "isBinaryValue": false,
    "isBinaryKey": false,
    "brokers": [
      "kafka01-prod01.messagehub.services.us-south.bluemix.net:9093",
      "kafka02-prod01.messagehub.services.us-south.bluemix.net:9093",
      "kafka03-prod01.messagehub.services.us-south.bluemix.net:9093",
      "kafka04-prod01.messagehub.services.us-south.bluemix.net:9093",
      "kafka05-prod01.messagehub.services.us-south.bluemix.net:9093"
    ],
    "username": "admin",
    "password": "123",
    "kafka_admin_url": "https://kafka-admin-prod01.messagehub.services.us-south.bluemix.net:443"
  },
  "status":{
    "active": false,
    "dateChanged":1509321736699,
    "dateChangedISO":"2017-10-30T00:02:16.699Z",
    "reason":{
      "kind": "AUTO",
      "statusCode": 403,
      "message": "Automatically disabled after receiving a 403 status code when firing the trigger."
    }
  }
}

Notes:
The field status.reason not present when status.active is true
The clients would be able to invoke the feed action with this lifecycleEvent
For example using the CLI directly invoking the feed action.
wsk action invoke /whisk.system/messaging/messageHubFeed -p triggerName _/myKafkaTrigger -p authKey guest:123 -p lifecycleEvent READ -r

The go-CLI would be able to call the feed action automatically on a trigger get.
For example:
wsk trigger get myKafkaTrigger

ok: got trigger myCloudantTrigger
{
    "namespace": "guest",
    "name": "myKafkaTrigger",
    "version": "0.0.1",
    "annotations": [
        {
            "key": "feed",
            "value": "/whisk.system/messaging/messageHubFeed"
        }
    ]
}
ok: invoked feed action /whisk.system/messaging/messageHubFeed
{
  config:{
    triggerName: "_/myKafkaTrigger",
    isMessageHub: true,
    topic: "mytopic",
    isJSONData: true,
    isBinaryValue: false,
    isBinaryKey: false,
    brokers: [
      "kafka01-prod01.messagehub.services.us-south.bluemix.net:9093",
      "kafka02-prod01.messagehub.services.us-south.bluemix.net:9093",
      "kafka03-prod01.messagehub.services.us-south.bluemix.net:9093",
      "kafka04-prod01.messagehub.services.us-south.bluemix.net:9093",
      "kafka05-prod01.messagehub.services.us-south.bluemix.net:9093"
    ],
    username: "admin",
    password: "123",
    "kafka_admin_url": "https://kafka-admin-prod01.messagehub.services.us-south.bluemix.net:443"
  },
  status:{
    active: true
    }
  }
}

UPDATE lifecycle
The UPDATE lifecycle will allow users to update their feed without the need to delete and re-create their trigger.
The feed action should accept the parameter lifecycleEvent with the value of UPDATE.
The user should be able to pass a partial set of the configuration values, allowing them to update their trigger feed.
The feed will be paused while it's being updated.
For example if user wants to update the topic name, it will invoke the feed action with the topic parameter for the existing trigger.
For example invoking directly the feed action:
wsk action invoke /whisk.system/messaging/messageHubFeed -p topic newtopic -p triggerName _/myKafkaTrigger -p authKey guest:123 -p lifecycleEvent UPDATE -r

Using the cli using the integration embedded into the CLI
wsk trigger update myKafkaTrigger -p topic newtopic

One wrinkle here is that, for Message Hub triggers, the properties recorded in the DB can have different names than the properties specified when creating the trigger. For example, I specify my brokers using the kafka_brokers_sasl property, but this gets recorded as brokers in the DB.
I would argue that when retrieving the trigger details, the user should always see the property names the same as what they set when creating the trigger. This may mean massaging the property name back to what the user expects to see (e.g. brokers -> kafka_brokers_sasl)

Agree we should not expose the implementation details and keep the abstraction of the interface to the user the same so massaging the keys is a good thing.

@abaruni Could you change READ config object to match the input parameters by user based on feedback from @jberstler above ^^ https://github.com/apache/incubator-openwhisk-package-kafka/issues/220#issuecomment-343330248

I would argue that when retrieving the trigger details, the user should always see the property names the same as what they set when creating the trigger. This may mean massaging the property name back to what the user expects to see (e.g. brokers -> kafka_brokers_sasl)

cc @jasonpet

I did a quick look it looks like there are 2 fields to change
username -> user
brokers -> kafka_brokers_sasl
{
"kafka_brokers_sasl": [
      "kafka01-prod01.messagehub.services.us-south.bluemix.net:9093",
      "kafka02-prod01.messagehub.services.us-south.bluemix.net:9093",
      "kafka03-prod01.messagehub.services.us-south.bluemix.net:9093",
      "kafka04-prod01.messagehub.services.us-south.bluemix.net:9093",
      "kafka05-prod01.messagehub.services.us-south.bluemix.net:9093"
    ],
"user": "admin"
}

@abaruni I will update description above, can you double check?

Hum I think it's username and the doc is wrong using user

It's definitely user here in produce action https://github.com/apache/incubator-openwhisk-package-kafka/blob/master/action/messageHubProduce.py#L124

It's definitely user here in MessageHubFeedWeb Action https://github.com/apache/incubator-openwhisk-package-kafka/blob/master/action/messageHubFeedWeb.js#L145
But stored as username in db, so we need the get to change to user in the way out
https://github.com/apache/incubator-openwhisk-package-kafka/blob/master/action/messageHubFeedWeb.js#L84-L86
it is
                            kafka_brokers_sasl: triggerDoc.brokers,
                            user: triggerDoc.username,

it should be
                            brokers: triggerDoc.brokers,
                            username: triggerDoc.username,


Unable to find podcast player in Obsidian in iOS

I have Obsidian on iOS. I cannot find a way to load the Podcast player. I see the docco says this plugin is mobile-friendly. How do we use it in iOS?

Update: I found it by swiping from the right and tapping the backlinks heading to bring up a list of plugins. However, "Podcast Player" is in that list 8 times now, even after removal and reinstallation of the plugin within Obsidian Settings. Why would it show up 8 times?

It appeared so many times due to code loading it but not removing it - should be fixed now!


Unable to find in obsidian community plugins

I can find the original plugin from @pacokwon but I can't find yours. I've tried installing your version using the VARE plugin, but I'm still having issues even tho it's installed. When I try to insert a conference talk it doesn't do the formatting. Any ideas?

I'm sorry for the late reply @lbacigal. The plug-in moderators were taking some time to approve the plug-in. It was finally accepted just this last week! Please check the community plug-ins for it. As for the formatting, I'm not sure.
This is the result I get:

If the internet connection is a little unstable it seems to have a more difficult time. I've found that sometimes deleting the last character, and then typing it again reinitiates the search.

Additionally, when you load a plug-in either manually or from Obsidian, you need to make sure you've turned it on under Settings->Community plugins. Once there scroll down until you see "LDS Library Reference." On the right are buttons for plugin settings, delete, and to toggle it on or off.


custom model created based on your tutorial doesn't work files

I am an absolute beginner,  follow your tutorial (https://www.youtube.com/watch?v=cvyDYdI2nEI&ab_channel=GilbertTanner) and successfully create a custom model but when trying the model with this TensorFlow-2-Object-Counting its doesn't work.
can please help on how to link your object detection tutorial to the abject counting tutorial.

What do you mean with it doesn't work? What error are you getting?


add Helijia

Please review our Contribution Guidelines to ensure your changes abides by it.
Changes should be made to the end of the file.
Review your changes and complete the checklist below.

[x] Company name
[x] Industry
[x] Company location
[x] Company description
[x] How Elixir is used
[x] GitHub / blog links
[x] Job listings

Thank you for the addition @qhwa!

Thank you @doomspork ! 🥂


How to change the directory where the model will get loaded to in SageMaker

Hey my root directory only has 30 Gb of free storage, while the EBS volume that I added has 500 Gb of free storage.
I want that the model should be stored in the EBS volume added NOT in root directory.
But, I am unable to figure out how to change the storage location in vLLM

You can use the --download-dir option to specify your model cache path.


spacing  and sizing changes

🐛 Bug Report

A relatively narrow navbar would look more  elegant .
The spacing between the section end and topic is to wide.

Add relevant screenshot or video (if any)

/assign

Hey mentors and project admin . I think there is nothing much to be done in the  issue as the problems mentioned are already solved in another pr . So I am closing this issue.


Add PyPI trove classifiers for Python 3

Fixes #53.

Coverage remained the same at 75.966% when pulling d7044c58a5eea7d597a472fe242d6b8a5517501e on edmorley:python3-trove into 0ceca24d12494efa1552f29be18e72c85d064724 on GaretJax:develop.

Thanks Ed, good catch. Before merging I wonder if I want to have Py 2.6 in there.
It might work, but don't want to support it explicitly.

Hi! I used the version list from .travis.yml - I can either just drop it from this PR, or also remove it from the Travis run?

Let's do both then, thank you!
I'll try to get other issues fixed as well and a release uploaded to pypi

Thank you for doing that in c5a984b6ca2bc56bf3f44e2e4542f1f0751769d8 :-)


Add feature: gnu_legacy mode for ansi styles

Hi,
gnu coreutils are still using double digit styles instead of single digit styles.
To make this available in uucoreutils (the rust drop in replacement for gnu core utils) I added a feature called gnu_legacy.
Related PR
By turning it on it will generate styles double digit. If not turned on it will behave as before. Tests have been added.
// without feature flag gnu_legacy
    test!(bunderline:            Style::new().bold().underline();   "hi" => ,"\x1B[1;4mhi\x1B[0m");
// with feature flag gnu_legacy
    test!(bunderline:            Style::new().bold().underline();   "hi" => "\x1B[01;04mhi\x1B[0m");

Please see the code and I hope this feature can make it.
The second missing feature would be to have the option to reset a style before applying. I would open another PR for this.

looks like some tests are failing

Thanks


python3Packages.restfly: 1.4.0 -> 1.4.1

Motivation for this change
Update to latest upstream release 1.4.1
Things done

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

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 132816 run on x86_64-linux 1

4 packages built:

python38Packages.pytenable
python38Packages.restfly
python39Packages.pytenable
python39Packages.restfly

Result of nixpkgs-review pr 132816 at 26b50ee7 run on aarch64-linux 1

4 packages built successfully:

python38Packages.pytenable
python38Packages.restfly
python39Packages.pytenable
python39Packages.restfly


Accumulate dynamic tensor in LoopOp

Tensors computed in loop body may be accumulated in a tensor with an extra dimension. For example, a loop body may return a tensor<d1,...,dnXT> and the loop will generate a tensor<IC, d1, ...,dn XT> to accumulate the result of every iteration. IC will be equal to the iteration count, either statically or dynamically. In current implementation, it is assumed that IC is known, at least dynamically, before the loop. The straightforward implementation is to allocate the tensor for accumulation before the loop body. However, this allocation can not be done when any d1, ..., dn is not statically known. The local tensor has not been computed yet and dimOf can not be used to get the dynamic size.
Current solution details:

use memref<ICxmemref<d1, ...dnxT>> to represent the accumulate tensor.
allocate it before the loop with IC
In loop, the accumulation is to store the memref computed in the loop body as a whole.
After the loop, the memref<ICxmemref<d1, ..., dn xT>> to memref<IC, d1, ..., dnxT>. For the unknown di (di == -1), we can use DimOf on any memref element loaded for the accumulated memref. The LoopOp semantics guarantees that all the local tensor should have the same shape.

Due to issue#1236, I can not test this PR with a model yet.
Future work:

A generic solution is use SeqType if the trip count is unknown. The current solution is an optimization to avoid adding loop-carried dependence by sequence and extra copying of data.
Another possible solution is to allocate an empty memref before loop and then re-allocate the memref at the end of first iteration. This solution will also introduce a loop-carried dependence.

@tungld Thanks for the suggestions. I fixed them.

Jenkins Linux ppc64le Build #3521 [push] Accumulate dynamic tenso... started at 17:45

Jenkins Linux s390x Build #4405 [push] Accumulate dynamic tenso... started at 17:42

Jenkins Linux amd64 Build #4393 [push] Accumulate dynamic tenso... started at 16:42

Jenkins Linux s390x Build #4405 [push] Accumulate dynamic tenso... passed after 46 min

Jenkins Linux ppc64le Build #3521 [push] Accumulate dynamic tenso... passed after 55 min

Jenkins Linux amd64 Build #4393 [push] Accumulate dynamic tenso... passed after 1 hr 0 min


Loosen Python 3.8 requirement for ripsaw-cli

Describe the bug
For a loaded upgrade test the Perf/Scale QE team performs we use cluster-density and other kube-burner tests to load the cluster before an upgrade.
Previously these tests worked with using Jenkins on 3.6.8 python version.
Is it possible to push back the needed python version for ripsaw cli. I can do some testing using python: 3.6.8
ERROR: Package 'ripsaw-cli' requires a different Python: 3.6.8 not in '>=3.8'
11-01 16:39:25.335  ../../utils/benchmark-operator.sh: line 32: ripsaw: command not found

To Reproduce
Steps to reproduce the behavior:

Run Cluster-density

Expected behavior
Cluster density test (other scale-ci jobs) run properly
Additional context
https://mastern-jenkins-csb-openshift-qe.apps.ocp-c1.prod.psi.redhat.com/job/scale-ci/job/paige-e2e-multibranch/job/cluster-density/94/console
11-01 16:26:44.688  Python 3.6.8
11-01 16:26:52.953  Collecting pip
11-01 16:26:52.953    Downloading https://files.pythonhosted.org/packages/a4/6d/6463d49a933f547439d6b5b98b46af8742cc03ae83543e4d7688c2420f8b/pip-21.3.1-py3-none-any.whl (1.7MB)
11-01 16:26:52.953  Installing collected packages: pip
11-01 16:26:52.953    Found existing installation: pip 9.0.3
11-01 16:26:52.953      Uninstalling pip-9.0.3:
11-01 16:26:52.953        Successfully uninstalled pip-9.0.3
11-01 16:26:53.533  Successfully installed pip-21.3.1
11-01 16:26:54.478  Collecting ripsaw-cli
11-01 16:26:54.478    Cloning https://github.com/cloud-bulldozer/benchmark-operator.git/ to /tmp/pip-install-3_x89a0e/ripsaw-cli_3b7f64d1b3ea447bbbfc4ae80a9320eb
11-01 16:26:54.478    Running command git clone --filter=blob:none -q https://github.com/cloud-bulldozer/benchmark-operator.git/ /tmp/pip-install-3_x89a0e/ripsaw-cli_3b7f64d1b3ea447bbbfc4ae80a9320eb
11-01 16:26:55.874    Resolved https://github.com/cloud-bulldozer/benchmark-operator.git/ to commit c8e5ca99ce8f6db5e0a861726f846a07e4d00149
11-01 16:26:55.874    Preparing metadata (setup.py): started
11-01 16:26:55.874    Preparing metadata (setup.py): finished with status 'done'
11-01 16:26:56.132  Collecting python-benedict==0.24.0
11-01 16:26:56.132    Downloading python_benedict-0.24.0-py3-none-any.whl (40 kB)
11-01 16:26:56.132  Collecting click==8.0.1
11-01 16:26:56.412    Downloading click-8.0.1-py3-none-any.whl (97 kB)
11-01 16:26:56.412  Collecting kubernetes==17.17.0
11-01 16:26:56.412    Downloading kubernetes-17.17.0-py3-none-any.whl (1.8 MB)
11-01 16:26:56.670  Collecting urllib3==1.25.7
11-01 16:26:56.670    Downloading urllib3-1.25.7-py2.py3-none-any.whl (125 kB)
11-01 16:26:56.670  Collecting PyYAML==5.4.1
11-01 16:26:56.670    Downloading PyYAML-5.4.1-cp36-cp36m-manylinux1_x86_64.whl (640 kB)
11-01 16:26:56.931  Collecting elasticsearch==7.13.4
11-01 16:26:56.931    Downloading elasticsearch-7.13.4-py2.py3-none-any.whl (356 kB)
11-01 16:26:57.188  Collecting GitPython==3.1.18
11-01 16:26:57.188    Downloading GitPython-3.1.18-py3-none-any.whl (170 kB)
11-01 16:26:57.188  ERROR: Package 'ripsaw-cli' requires a different Python: 3.6.8 not in '>=3.8'
11-01 16:26:57.447  ../../utils/benchmark-operator.sh: line 32: ripsaw: command not found

Hey @paigerube14 - Could you get by without using the ripsaw-cli?
Alternatively you could run in a venv?

Previously these tests worked with using Jenkins on 3.6.8 python version.

Just as a heads up, there will be some other tools that eventually require you to update to python 3.8, like Ansible - eventually...

Hey @jtaleric,
I was trying to stay up to date with changes going into e2e-benchmark and benchmark operator. I think ripsaw-cli is used by default in all e2e-benchmark/workloads/kube-burner/*.sh files, correct?  Will try not using the ripsaw-cli. Think I just need someone on the jenkins side to set up python 3.8. Thanks!

@jtaleric would we be able to install python3.8 if it isn't already on the system so we can get around this issue on systems we don't know the setup?


Docs Search: Search result also shows all the includes md-files - and it looks odd when clicking

Some of the search result comes up with no titel only " | SuperOffice Docs"
Clicking that link will open a page with no content other that the include md file.
Expected that the include files should not be indexed and shown in the search result.

All includes folders must be excluded in the configuration file.

@SuperOfficeDevNet, I implemented the requested changes on superoffice-docs main branch.
However, docfx-learn.json in build-docs must also be updated and I lack access.
Add general exclude at the top (becomes lines 9-11):
    "content": [
      {
        "src":"docs",
        "files": [ "*.{md,yml}" ]
      },
      {
        "exclude": ["**/includes/**"]
      },

Add exclude (1 line) to existing release-notes entry, ca line 100:
{
        "src":"superoffice-docs/release-notes",
        "dest":"en/release-notes",
        "files": [ "**/**.{md,yml}", "*.{md,yml}" ],
        "exclude": ["**/includes/**"]
}


add fetch-providers pagination and rancher2 schema

This also fixes missing providers rancher2 to point one.
Github api limits returned repositories to 100 (not 200) so it was missing some of entries.

Thanks. I've merged manually first commit.


@Parameters arity exception could be more verbose

Deleted incorrect bug source assumptions from original issue.
When @Parameters exist, and initial parameters (index = 0 or 1 or so) are removed during coding, runtime throws an exception
Exception in thread "main" picocli.CommandLine$ParameterIndexGapException: Missing field annotated with @Parameter(index=0). Nearest field 'file' has index=2
at picocli.CommandLine.validatePositionalParameters(CommandLine.java:2066)
Maybe the message could, instead of (or in addition to) saying "missing field", say "not a valid index". I read the "missing" message as a missing command line parameter and thought it was saying "field X annotated with Y was not supplied to the Command" or something and being overly verbose about just where in the code that option/parameter being asked for was.
Regardless, the message should use the correct annotation @Parameters, not @Parameter.

Thanks for pointing that out! I’ll improve the error message.

Do you think you’ll be able to provide a pull request for this?

I improved the error message. It now looks like this:
throw new ParameterIndexGapException(
    "Command definition should have a positional parameter with index="
     + min +
    ". Nearest positional parameter '"
     + positional.paramLabel() + "' has index=" + index.min);

Thanks for the suggestion!


diff: alter foreground color as well

to keep readable contrast between bg and fg
example:
viddy -d --no-title date

before

after

@sachaos just discovered viddy today. I find it succint and elegant, and it solves very real problem. For me it's being able to scroll.
Than you for your work!

@sachaos hi, how are you :)
Do you remember that loop, which highlights each individual character in the diff.
There is an issue with that, if there are already colors in the text, before coloring diff,
then for example '[\x1b40m' gets converted to green('[') + green('\x1b') + green('4') + ..., which visually looks like this:

so invisible '[\x1b40m' becomes visible and green, which is not supposed to happen.
Maybe we should remove such things from the string before applying green?

@NikolayXHD Hi, thank you for your bug report.
Is this new bug of this PR or not?
I think we should dicuss on a new issue.


⚠ Bofrost.at has degraded performance

In 30b6057, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 4417 ms

Resolved: Bofrost.at performance has improved in 8ebedaf.


Update global.scss

Fix some low-contrast accessibility issues for mobile menu.

Oh, good thinking. Created ticket #128


Add locale variable to loadLanguageAsync promise

A lazy-loaded promise js doesn't get the "locale" value just the ctx
await Promise.resolve(messages(context))
Please add the value to the Promise
await Promise.resolve(messages(context, locale))
Reason
I made a common i18n loader with fallback handling and my handler doesn't get the desired language without a workaround.
Workaround
en.js
 import loader from './i18nLoader'
export default (ctx) => {
  return loader(ctx, 'en')
}
i18nLoader
export default async (ctx, locale) => {
  return new Promise(async (resolve) => {
...
}}

Implemented and will release in the next version (6.13).


multiple connection

this all works just fine when connection is created like
mongoose.connect(config.mongo.url, config.mongo.options, () => {
	console.log("connected :)")
});

but silently fails when connection is created like
mongoose.createConnection(configs.migration.mongo.url, configs.migration.mongo.options, () => {
	console.log("connected :)");
})

which is actually correct because mongoose.connection is not set
so can you please add some possibility to pass connection to where models are registered
https://github.com/saintedlama/mongoose-version/blob/master/lib/strategies/collection.js#L20

You can try out https://www.npmjs.com/package/lackey-mongoose-version
It's pretty much still just @saintedlama code. We just added the multiple connection support.
We also decided to remove the array option. Mongo has a fairly low size limit per document. We have already hit it a couple of times and given the fact we don't actually use that we just stripped it out.
We would be more than happy to move back to using this plugin if it supports multiple connections, but for the time being this quick fork solved our problem.

Do you have a pull request for the multiple connection feature @relvao? Will merge ASAP

I had this one https://github.com/saintedlama/mongoose-version/pull/18
Can you merge it or would I have to do a new pull request?

I'd need a new pull request since the repository containing the pull request has been deleted

@saintedlama  OK. Let me re-build it this weekend and do another pull request.
The connection should make little difference in the tests. I had replicated all the tests in another folder just to verify/proove if it made no difference, but I guess a basic test checking if the basic features still work with multiple connections should be enough. I don't see any point in duplicating everything. What do you think?

Duplicating all the tests does not make sense. If the multiple connection feature works in a basic scenario it will (most likely) work in other scenarios as well. Code coverage generated by istanbul is a good measurement for adding new tests.

@relvao have you had a chance to work on this or do you need a help?

Not yet, sorry. I'll try and do it soon.


strawman: sketch of agent bits of SDK

DO NOT SUBMIT
This PR exists solely for trying to facilitate SDK design. It is not meant NOR intended to be a finalized approach that is consumed by python SDK users.
Questions for reviewers:

is this "style" the one we want to pursue?
do we need fuller worked examples here?
is this approximately the right level of opinionated for the SDK?  Should it be heavier?  Lighter?
do we think something like AgentContext is valuable?  What role should it play?
Is it useful to separate Action from Tool?  Is there a better concept there (ToolExecution? other?)
Do we believe Block + Tag is the right way to pass information between Tools and between Tool and Agent ?

DO NOT SUBMIT

Looking at HF Agents/Tools, another very neat design property they seem to have, that I think we could replicate, is the following:
An Agent/Tool in copy-pasted Python works...
But if you were to ship deploy agent.py or tool.py, we could just "do the right thing" even without steamship.json (since most of that is inferred from the python file anyway) and now it's a remoted Agent/Tool.
And if you wanted, you could then just have a RemoteAgent("handle") or RemoteTool("handle") that you used instead.
It probably makes sense for each instance to always pin itself to the latest version unless you specifically mention the version. Which is slightly different than current semantics of it pinning itself to the latest version upon first invocation, and then not auto-rolling-forward unless you update the version & your code. That way we still support versioning, but default to $LATEST at all times.
That also makes us compatible with HF agents -- you could have SteamshipTool("handle") and SteamshipAgent("handle") that were wrapped in a way that lets us help the HF community by providing agents with memory attached

@douglas-reid  OK if we close this one to clean up the open PRs view?


Add detected object with feature (#54) (#59)

Related Links

add following msgs
DetectedObjectWithFeature
DetectedObjectsWithFeature

Description

Remarks

Pre-Review Checklist for the PR Author
PR Author should check the checkboxes below when creating the PR.

[x] Code is properly formatted
[x] Assign PR to reviewer

Checklist for the PR Reviewer
Reviewers should check the checkboxes below before approval.

[ ] Commits are properly organized and messages are according to the guideline
[ ] Code is properly formatted
[ ] PR title describes the changes

Post-Review Checklist for the PR Author
PR Author should check the checkboxes below before merging.

[ ] All open points are addressed and tracked via issues or tickets
[ ] Write release notes

CI Checks

Build and test for PR: Required to pass before the merge.
Check spelling: NOT required to pass before the merge. It is up to the reviewer(s). See here if you want to add some words to the spell check dictionary.

@isamu-takagi @kenji-miyake
Do we need to pick up the following PR to resolve the CI/CD error ? :thinking:

https://github.com/tier4/AutowareArchitectureProposal_msgs/pull/2

@isamu-takagi @kenji-miyake
Do we need to pick up the following PR to resolve the CI/CD error ? thinking

Fix build_depends.repos #2

fix in https://github.com/tier4/AutowareArchitectureProposal_msgs/pull/4/commits/9fe5f15b722a90d691152b33f526ab208165bcb7
pass all CI/CD :smile:

@satoshi-ota Nice work! But I think you should change the target branch.

@kenji-miyake Ok, witch branch would be appropriate? Do I have to make use-autoware-auto-msgs in this repo, too?

@satoshi-ota Yes, it's fine. FYI the reason is main is reserved for syncing with the internal repository.

@kenji-miyake I see :+1:
I'll create use-autoware-auto-msgs branch in this repo, and update the build depends in AutowareArchitectureProposal.iv.
https://github.com/tier4/AutowareArchitectureProposal.iv/blob/449209219cb3b1d3fbf153c8bc639f6d9b65e985/build_depends.repos#L2-L5

@satoshi-ota Perfect!

update target branch :+1:


fail pytest

Task <Task pending name='Task-13' coro=<ASGIHTTPConnection.handle_request() running at /home/artem/PycharmProjects/mm-yc-notify/venv/lib/python3.12/site-packages/quart/asgi.py:98> cb=[_wait.._on_completion() at /usr/lib/python3.12/asyncio/tasks.py:524]> got Future  attached to a different loop
Environment:

Python version: 3.12
Quart version: 0.19.3

Not sure how you expect any help if you do not even post code to reproduce this...


perf(consensus): align calls to ValidateBlock to ProcessProposal

Closes #2854
This changes is an implementation of the alignment of ValidateBlock to ProcessProposal explained here.
We need to:

Check if that helps, perf-wise
Carefully make we're not compromising algorithm's correctness

PR checklist

[ ] Tests written/updated
[ ] Changelog entry added in .changelog (we use unclog to manage our changelog)
[ ] Updated relevant documentation (docs/ or spec/) and code comments
[x] Title follows the Conventional Commits spec

Removed from project board & Milestone b/c it's tracked already under https://github.com/cometbft/cometbft/issues/2854

See this comment for an explanation of the latest commits


Upgrading to HBase 2.1.0

The HBase mini cluster tests still seem to be broken.  That needs to still be investigated as per issue #1843

@igorbernstein2, ping.


cli: fix transfer print psbt version

Description:
The display implementation of Psbt does not use {:#}(formatter.alternate()) to determine the psbt version. All printing here is the V2 version of psbt.

Sorry, this doesn't make any sense: neither description nor code changes. Please update or this will be closed.
Use google translate if necessary and read documentation on how rust Display work

In the transfer code, the psbt version returned by Runtime.pay is V2.
If I do not specify the psbt_file parameter in the parameter, then psbt will be displayed and printed to the terminal. But in the impl Display for Psbt code, println("{psbt}"), f.width() == None, f.sign_aware_zero_pad() == false, so it will match the _ branch and the returned ver is 2.

Sorry, my English writing is terrible. I tried my best to explain this matter. If there are errors in my ideas or code implementation, you can close this pull request. Sorry to take up your time.

Thank you very much for reporting the issue, you are right!
But this PR doesn't fixes it and do not make any sense - it is simply wrong, so I close it and open an issue to address the bug you have discovered.

Thank you very much for your reply. It seems that I don't have to learn rust again😄. But I have some doubts about the point where you say the fixed code do not make any sense. Because I only made changes based on the corresponding documentation, and I have tested it locally and it is runnable. Maybe your solution is that the Runtime::pay method should have a parameter to control the version of psbt returned? Or some other plan? @dr-orlovsky


Switching forecast model can result in delay

When the select "Solcast PV Forecast Use Forecast Field" is configured on a dashboard, changing the forecast model between 10/avg/90 can result in a significant delay.
This is because the integration reloads, and a check for rooftop sites and API use is re-performed.
The proposal is that on receiving an initial 429/too busy for each of roofop sites/API usage that the retry mechanism instead immediately use the cache should it exist. This will result in a near instant reload.

The code is done and based on proposed future v4.0.33, currently running on my 'prod' instance for thorough testing. It will likely be included in a post v4.0.33 release.
This will also include a bunch of logging refinements, and a fix for get usage allowance, which is presently not retrying on failure.

This is working brilliantly so far. Just hit a 429 on selection of a forecast prediction for rooftop sites, and the integration moved on with cache instantly.
2024-06-25 21:37:29.331 DEBUG (MainThread) [custom_components.solcast_solar.solcastapi] SOLCAST - connecting to - https://api.solcast.com.au/rooftop_sites?format=json&api_key=******NV8ggJ
2024-06-25 21:37:29.554 DEBUG (MainThread) [custom_components.solcast_solar.solcastapi] SOLCAST - sites_data http session returned status 429/Solcast too busy
2024-06-25 21:37:29.554 DEBUG (MainThread) [custom_components.solcast_solar.solcastapi] SOLCAST - loading cached sites data
2024-06-25 21:37:29.558 DEBUG (MainThread) [custom_components.solcast_solar.solcastapi] SOLCAST - sites_data: {'sites': [{'name': 'Iris North-East', 'resource_id': 'b68d-c05a-c2b3-2cf9', 'capacity': 6.857, 'capacity_dc': 7.92, 'longitude': xx.xxxxxx, 'latitude': xx.xxxxxx, 'azimuth': -67, 'tilt': 26, 'loss_factor': 0.95, 'tags': []}, {'name': 'Iris North-West', 'resource_id': '83d5-ab72-2a9a-2397', 'capacity': 5.243, 'capacity_dc': 5.72, 'longitude': xx.xxxxxx, 'latitude': xx.xxxxxx, 'azimuth': 27, 'tilt': 17, 'loss_factor': 0.95, 'tags': []}], 'page_count': 1, 'current_page': 1, 'total_records': 2}
2024-06-25 21:37:29.558 DEBUG (MainThread) [custom_components.solcast_solar.solcastapi] SOLCAST - getting API limit and usage from solcast for ******NV8ggJ
2024-06-25 21:37:29.615 DEBUG (MainThread) [custom_components.solcast_solar.solcastapi] SOLCAST - sites_usage http session returned status 200/Success
2024-06-25 21:37:29.615 DEBUG (MainThread) [custom_components.solcast_solar.solcastapi] SOLCAST - writing API usage cache file: /config/solcast-usage.json
2024-06-25 21:37:29.621 DEBUG (MainThread) [custom_components.solcast_solar.solcastapi] SOLCAST - API counter for ******NV8ggJ is 8/10
2024-06-25 21:37:29.639 DEBUG (MainThread) [custom_components.solcast_solar.solcastapi] SOLCAST - load_saved_data file exists: file type is <class 'dict'>
2024-06-25 21:37:29.669 DEBUG (MainThread) [custom_components.solcast_solar.solcastapi] SOLCAST - removePastForecastData forecasts len in 1055
2024-06-25 21:37:29.670 DEBUG (MainThread) [custom_components.solcast_solar.solcastapi] SOLCAST - removePastForecastData midnight_utc 2024-06-24 14:00:00+00:00, forecasts len out 384
2024-06-25 21:37:29.671 DEBUG (MainThread) [custom_components.solcast_solar.solcastapi] SOLCAST - Data for 2024-06-25 contains all 48 records

Automated redaction of API key and latitude/longitude, and HTTP status codes translation as seen here coming soon... Spoiler.

v4.0.34 pre-release is published to address this.


fix memoryview compare

@qingshi163 I think you are one of the pro of memoryview. Could you review this PR please?

Thank you for your review. I'm not sure if I edited it as you said.

I don't know any reason CPython has a back door for ord compare between memoryview and bytearray(not bytes). Should we follow? @coolreader18
Otherwise this code fix at lease some of the case.

Huh, that's really weird behavior. I think if there's no test cases that test for that (or even if there are, honestly) it's fine to ignore that.


Update some "dependencies" (builds tools) and increase target/compile version

Title says everything..
I haven't it tested yet :D

Just have tested it.
Sample works fine. Uploading to bintray also (see https://bintray.com/stefma/maven/Tray).
Seems to be working 😄
Additional tests needed? @passsy

Codecov Report

Merging #107 into master will not change coverage.
The diff coverage is n/a.

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


dbctl for dqlite backup and restore

A dbctl command is added to take backups and restore the dqlite db.
$ microk8s.dbctl --help
usage: microk8s dbctl [-h] [--debug] {restore,backup} ...

backup and restore the Kubernetes datastore

optional arguments:
  -h, --help        show this help message and exit
  --debug           print debug output

commands:
  {restore,backup}  backup and restore operations

@sstubbs here is the PR with a command to handle dqlite backups.

Oh brilliant! thanks a lot. This is such a great feature to have.


fix: no-unlocalized-strings rule to correctly handle as const assertions in property values with ignoreNames

Description:
This PR fixes an issue in the no-unlocalized-strings ESLint rule where string literals assigned to object properties are incorrectly reported as unlocalized strings when using TypeScript's as const assertions, even if the property names are specified in the ignoreNames option.
Background:
When using the ignoreNames option with a regex pattern to ignore certain property names, the rule should not report string literals assigned to those properties. However, if the property value includes an as const assertion, the rule fails to recognize it due to the TSAsExpression node introduced by the TypeScript assertion.
Example:
Given the ESLint configuration:
{
  "rules": {
    "no-unlocalized-strings": [
      "error",
      { "ignoreNames": [{ "regex": { "pattern": "^[A-Z0-9_-]+$" } }] }
    ]
  }
}

The following code incorrectly reports errors for the string literals "circle" and "rectangle":
export const Shape = {
  CIRCLE: "circle" as const,
  RECTANGLE: "rectangle" as const,
};

Cause of the Issue:
The as const assertion wraps the string literal in a TSAsExpression node in the Abstract Syntax Tree (AST). The existing rule does not handle TSAsExpression nodes when processing property values, so it fails to apply the ignoreNames logic to the unwrapped string literals.
Solution:
The fix involves updating the rule to handle TSAsExpression nodes by unwrapping them to access the underlying string literals. Specifically:

Implemented an Unwrapping Helper Function:
Added a helper function unwrapTSAsExpression to recursively unwrap TSAsExpression nodes:
function unwrapTSAsExpression(
  node: TSESTree.Expression,
): TSESTree.Literal | TSESTree.TemplateLiteral | TSESTree.Expression {
  while (node.type === TSESTree.AST_NODE_TYPES.TSAsExpression) {
    node = node.expression;
  }
  return node;
}

Updated the isStringLiteral Function:
Modified isStringLiteral to handle TSAsExpression nodes:
function isStringLiteral(node: TSESTree.Node | null | undefined): boolean {
  if (!node) return false;

  if (node.type === TSESTree.AST_NODE_TYPES.TSAsExpression) {
    return isStringLiteral(node.expression);
  }

  switch (node.type) {
    case TSESTree.AST_NODE_TYPES.Literal:
      return typeof node.value === 'string';
    case TSESTree.AST_NODE_TYPES.TemplateLiteral:
      return true;
    case TSESTree.AST_NODE_TYPES.JSXText:
      return true;
    default:
      return false;
  }
}

Modified the Visitor to Handle TSAsExpression Nodes:
Updated the visitor function for Property nodes to unwrap TSAsExpression nodes when processing property values:
'Property > :matches(Literal, TemplateLiteral, TSAsExpression)'(
  node: TSESTree.Literal | TSESTree.TemplateLiteral | TSESTree.TSAsExpression,
) {
  const parent = node.parent as TSESTree.Property;

  if (
    (isIdentifier(parent.key) && isIgnoredName(parent.key.name)) ||
    ((isLiteral(parent.key) || isTemplateLiteral(parent.key)) &&
      isIgnoredName(getText(parent.key)))
  ) {
    const unwrappedNode = unwrapTSAsExpression(node);

    if (isLiteral(unwrappedNode) || isTemplateLiteral(unwrappedNode)) {
      visited.add(unwrappedNode);
    }
  }
},

Testing:

Manual Testing:

Verified that with the ignoreNames option configured, the linter no longer reports errors for string literals assigned to property names matching the regex pattern, even when using as const assertions.

Automated Testing:

Ran the existing test suite to ensure no regressions were introduced.
Added new test cases to cover scenarios involving as const assertions in property values.

Notes:

Minimal Changes: The fix is minimal and specifically targets the handling of TSAsExpression nodes in property values, avoiding changes that could affect other parts of the rule.
TypeScript Compatibility: The solution ensures compatibility with TypeScript features, making the rule more robust when analyzing TypeScript code.
No Regressions: Care was taken to ensure that existing functionality remains unaffected, and that the fix does not introduce any new issues.

Conclusion:
This PR improves the no-unlocalized-strings rule by correctly handling as const assertions in property values when using the ignoreNames option. It ensures that string literals assigned to ignored property names are not incorrectly reported as unlocalized strings.

LGTM, thanks for the contribution!

@swernerx thanks for the contribution! Could you please rebase the current branch and resolve conflicts?

Rebase done!


CurveNet performs the best under corruptions!

Dear Authors,
We find that CurveNet performs the best under on ModelNet40-C architecture benchmark: https://github.com/jiachens/ModelNet40-C#modelnet40-c-leaderboard
I will update our arXiv paper recently to highlight this result, and could you please also highlight this in your repo, so that also advertise our benchmark?
Thank you so much!

Hi,
Thanks for your efforts on this! Glad to see CurveNet performs the best on your benchmark. I will make an update in the README to highlight such result and make a rediretcion to your repo.
Thanks!

Thank you~


number tooltips are hard to copy/paste from (they disappear as you try to get the mouse over them)

It's possible to get the mouse over the popup number tooltips to copy/paste the hex representation of a number.  But it's not easy: you have to move the mouse fast and accurately to go from hovering over the number to hovering over the tooltip itself, so you can double-click the number and CTRL-C.
Is it possible to make them less finicky?  Sometimes you want to copy the hex representation instead of the original decimal (or I guess vice versa for binary objdump mode), especially for negative numbers if you're pasting into an arbitrary-precision calculator that doesn't do 32-bit 2's complement.
I'm using chromium on Linux, in case that matters.

@pcordes I just pushed a commit that might adress this. I can let you know once this hits the live site so you can tell me if it helps? :smile:

@RabsRincon:  Sure, I can test.  Let me know when.  (And where, if it's only on the alpha site, if that's still a thing.)

The beta site is currently away on holiday...but I have pushed the latest code to the live site.

Ey! Sorry to bug you with this, but have you been able to test it?

@RabsRincon: Sorry for the delay.  Just re-tested and it's very easy to mouse from the number to the tooltip now.
I just noticed that the binary-mode machine-code hexdump isn't selectable, and neither are the tooltips (useful for instructions longer than 5 bytes).  I don't think I've ever wanted to copy/paste hex machine code from godbolt, but maybe someone has.  I assume those tooltips are totally separate from the number tooltips, but if it's easy to do something about it without making the page run slower in people's browsers, that might be cool.


Add ispi4038.edu.ar

Hi guys, we have recently acquired the .edu.ar domain for our institute and we'll start deploying email addresses under it soon.
We already have a JetBrains verified domain here -> https://github.com/JetBrains/swot/blob/master/lib/domains/ar/com/ispi4038.txt
You can check both domains are pointing to the same server.
Do you need something else?
Could we keep both at least temporary? Or you need me to remove the .com.ar?. In that case, what happen with those students (if any) who already have created a JetBrains account using the .com.ar domain.
Cheers!
Edit:
ispi4038.com.ar PR -> https://github.com/JetBrains/swot/pull/4596

@cperezabo No problem, you can continue to use both email domains as long as they exist. Thank you for the update! Pull request merged.


Fix superglobal-access not to cause warnings, since they are initialized

Fix these annoying branch warnings that a variable was initialized in a
conditional branch, which occured when using super globals
in if-statements.

Can you add a test case for it? (use super global) to see warning
Thanks

You just need to use something really basic like:
if unlikely isset _GET["id"] {
    let _POST["id"] = _GET["id"];
}
if isset _POST["id"] {
    echo "g";
}

@andresgutierrez
Does "not tested" in that context mean that the solution hasn't been tested yet,
or that tests are missing?
If tests are missing, how do you test this specific issue, because
you would basically have to ensure that specific warnings do not appear.


[Draft] Attribute extraction

Adds a new task called attribute_extraction to the supported tasks. This task aims to extract multiple attributes from text and return it as a dictionary. It requires a new section in the config called output_attributes which details the name and options for each attribute. This could be expanded further to support more than just classification style labels such as multilabel classification or question answering.
Currently the accuracy and f1 metrics are calculated individually for every attribute. This could be expanded by specifying what type each attribute is in the output_attributes dictionary and deciding which evals to compute for each attribute based on that.
Here's an example of an eval table for the supreme court dataset:

With the most recent commit, the user can now specify what type the attribute is (currently supports classification, multilabel, and question answering) which allows autolabel to compute the correct labels for the correct attributes.

Working on top of this PR. Thanks a lot @Tyrest!


feat: 🎸 Add an endpoint to get an Asset's operation history

JIRA Link
DA-60
Changelog / Description
Add endpoint GET /assets/:ticker/operations to get an Asset's operation history
Checklist -

[x] New Feature ?
[x] Updated swagger annotation (if API structure is changed) ?
[x] Unit Test (if possible) ?
[ ] Updated the Readme.md (if required) ?

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


Replace link on Project page

Link on Project page in section Phase 1 doesn't work.  The correct one is  probably https://raw.githubusercontent.com/LouisvilleMetro/WazeCCPProcessor/master/docs/Current Architecture.png

Numbers on cards come from our Architecture Diagram. https://github.com/LouisvilleMetro/WazeCCPProcessor/blob/master/docs/Metro Waze Proposed Architecture.pdf

Thank you, it's updated now!


Provide a packaged way to setup selenium

Including browser specific settings (opera)
Also document instructions to install & cofigure

As per this issue a website will be created.
Accessible through grunt serve, a specific page will be created.

Done


Error message presented to the user when invalid acorn arguments are set in auto upgrade run command is misleading.

acorn version v0.5.0-rc2-2-g6cee142+6cee1422
While trying to run an app in auto upgrade mode with invalid acorn arguments , parsing error is presented to the user which does not provide any useful information.
% acorn run index.docker.io/xxx/xxx:v#.#.# --interval 3
  ✗  ERROR:  could not parse reference: index.docker.io/sangeetha/myfirstacorn:v#.#.#

The same scenario is handled with better error message when not using auto upgrade mode .
 % acorn run index.docker.io/xx/xxx:v2.0.0 --interval 3
  ✗  ERROR:  unknown flag: --interval

This is actually not an error message problem.
The args passed after the image are "acorn args." In order to determine if the passed args are valid for an Acorn, the CLI will look at the Acorn image and parse its args.
In the case where you are providing an auto-upgrade image format, Acorn doesn't know which Acorn image to pull which causes the error. You get a different error when you pass a real image name because Acorn pulls the image and sees that the Acorn doesn't have an --interval option.
@cjellick Is this something we want to support?

This problem happens even when valid acorn arguments are passed. I am changing the bug description to reflect this.

Tested with acorn version v0.5.1-28-g099c492+099c492f
We are now able to set acorn arguments when launching apps in auto upgrade format.
When invalid acorn arguments are passed , user is presented with an error message.
% acorn run --interval=1m -n myt2 mynew:#.#.# --xx=false
  ✗  ERROR:  unknown flag: --xx
% acorn run --interval=1m -n myt2 mynew:#.#.# --new=false --xx=false
  ✗  ERROR:  unknown flag: --xx
 % acorn run --interval=1m -n myt2 mynew:#.#.# --new=false
myt2
STATUS: ENDPOINTS[] HEALTHY[] UPTODATE[]
STATUS: ENDPOINTS[] HEALTHY[0] UPTODATE[0] pending
STATUS: ENDPOINTS[] HEALTHY[0/1] UPTODATE[1] [containers: nginx1 ContainerCreating]
...


Add compliant message for history

Cert-policy-controller doesn't write a message when it is compliant and has a namespace. Therefore it doesn't send compliance history. This PR will correct this issue.
Ref: https://issues.redhat.com/browse/ACM-10146

All Framework / KinD / Tests  should be changed

/override  "Framework / KinD / Tests (latest, true) (pull_request)" " Framework / KinD / Tests (latest, false) (pull_request)" "Framework / KinD / Tests (minimum, true) (pull_request)" "framework / KinD / Tests (minimum, false) (pull_request)" "Framework / KinD / Tests (latest, false, hosted) (pull_request)"

/override "KinD / Tests (latest, false)" "KinD / Tests (latest, false, hosted)" "KinD / Tests (latest, true)" "KinD / Tests (minimum, false)" "KinD / Tests (minimum, true)"

/override "KinD / Tests (latest, false)" "KinD / Tests (latest, false, hosted)" "KinD / Tests (latest, true)" "KinD / Tests (minimum, false)" "KinD / Tests (minimum, true)"

/override "KinD / Tests (latest, false)" "KinD / Tests (latest, false, hosted)" "KinD / Tests (latest, true)" "KinD / Tests (minimum, true)"


Problem with css at installation

Hey,
i ran into another problem while installing shopware6.
https://imgur.com/DLDT3KA
Thanks,
Florian

Also /admin after the Url isn't working either.

did you install shopware via ./psh.phar install?

Where can i find the file psh.phar?

I want to install it normally not to build plugins or anything else. I want to use it.

Did you download our package from our website or did you clone this repo from git?
Maybe having a look at our doku here will help you understand the installation process a litte better

Closing this due to inactivity. Hope you could fix your problem :)


gradle: merge engine-tests back in to engine directory

The directory (and gradle) layout for engine and its tests is like this:

/engine/src/main
/engine-tests/src/main
/engine-tests/src/test

instead of the standard

/engine/src/main
/engine/src/test

Using the standard layout would simplify the build configuration.
Dumping some thoughts from Cervator here:

does there need to be an engine-tests anymore - many moons ago we needed that hack, but i think Gradle (and IntelliJ?) both got more advanced about how you could link together sourceSets / code modules / compile vs test
i don't remember the details anymore but it was definitely something about being unable to have it unified because modules (maybe specifically module tests?) would get confused and things wouldn't compile / test in the right order
maybe particularly about tests that needed the environment base classes, like HeadlessEnvironment
worth noting is that class (and its friends IIRC) all live in the regular sourceSet inside engine-tests

On a related note the dev sourceSet inside engine can be simplified as well. It was kept separate for ... I dunno :) Probably just didn't seem right to have that code in the engine (it doesn't do anything for the engine) nor in tests since it isn't junit based or anything, although it feels kinda close to the tests, and benchmarking is sort of a test category
I propose (and have just validated that it'll work - look for and run EntitySystemBenchmark) moving the org.terasology.benchmarks package into the main sourceSet in engine-tests + remove the special handling for the dev sourceSet in the engine, although maybe that'll then be weird after re-unifying it since it does still not fit as engine code, nor regular test code 🤔
Once upon a time I was thinking we should have a test sourceSet per type of test - unit, integration, benchmark, acceptance (MTE) but maybe that'd just re-complicate things. It would really organize what kind of test something is though.

I have found one reason for making a -tests project that builds an independent thing from the main library: code you want to be re-used by other tests.
If you make something like ModuleTestingEnvironment, it has dependencies that aren't otherwise part of your library's implementation dependencies. Your users don't want this stuff on their implementation classpath either, they want something they can use as a test dependency.
I think you can do that and still keep the tests for the engine under src/test in the main project. The dependencies get a little bit twisty, but I think this works:

(Engine) - [:testImplementation] -> (MTE)  // allows project's tests to use MTE
(MTE) - [:implementation] -> (Engine)    // allows MTE to use engine APIs

A gradle project's test source set depends on its main source set anyway, it should work out.
tl;dr: do move engine-tests/src/test/ to engine/src/test, move MTE to engine-tests/src/main.

tl;dr: do move engine-tests/src/test/ to engine/src/test, move MTE to engine-tests/src/main

@keturn If we move MTE to engine-tests/src/main, would it make sense to rename it while we're at it? If not, why? And if so, to what? integrationTestEnvironment or something?

Sure, it'd be a convenient time to rename it.
Relevant terms include:

Integration: it sets up a complex environment in which we test the integration of various different things
Extension: the primary use case for it is as a JUnit Jupiter Extension
Engine: it provides a TerasologyEngine instance

ModuleEnvironment: most of the time it will be configured with a particular ModuleEnvironment (unless/until we have integration tests that involve something like going through Advanced Game Setup)

Headless: it runs things without rendering, as a headless server would. (But it would be handy to be able to switch on visible-mode sometimes.)


test: add more scheduler integration tests (4/)

Description of your changes
This PR adds more scheduler integration tests.
Note that it also features two fixes sent earlier, which will be rebased after they are merged.
I have:

[x] Run make reviewable to ensure this PR is ready for review.

How has this code been tested
N/A
Special notes for your reviewer
N/A

Merged to unblock progress; approval acquired previously -> no major changes afterwards.
If there's any concern, please let me know.


Avoid timeouts and race conditions esp. on slow machines

Resolves #180  Increase the timeout in two places that I've seen cause failures in thethe daemonset test.  Also add waits so that elasticsearch and cassandra tests don't start until es or cassandra are ready.

This change is

@objectiser @pavolloffay @jpkrohling Please review


ISPN-9334 Expose the metrics for memory utilization when BINARY storage

is used

Add data memory used stats to various classes
Works with off heap and binary when memory eviction is used

https://issues.jboss.org/browse/ISPN-9334

Fixed failing tests due to resource descriptor resolver missing changes.

Should be rebased now.

@wburns it looks good to me, but CI has a bunch of failures. they seem unrelated. could you double check? (integration.as.*)

yeah those errors make no sense for the changes I have here. I can try to run it again to see.

Now with all the lucene junk failures CI passed fine.


Create tr_tr.json

Turkish Localization

Hey, thanks for helping to localize the project!
The translation for ping-wheel.settings.nameLabelForced seems to be a bit long to fit into the UI.
This is not an issue in newer version of Minecraft, where the text scrolls back and forth, but for the older versions it overflows the button.

If you find a shorter translation for it, that would be appreciated to keep things nicely integrated in the UI.

I think it should be good now

Looks good!


The link on the page is broken

https://docs.microsoft.com/en-us/security/defender-endpoint/non-windows
the above link in the below section on the page is broken, gets a 404 error.

Important
The capabilities on non-Windows platforms may be different from the ones for Windows. For more information on what capabilities are available for non-Windows platforms, see Microsoft Defender for Endpoint for non-Windows platforms.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 8690a332-f672-8db8-1552-5ee16e78746f
Version Independent ID: 3df5b553-4e29-da25-c0e4-10686c5fed20
Content: Microsoft Defender for Endpoint
Content Source: microsoft-365/security/defender-endpoint/microsoft-defender-endpoint.md
Product: m365-security
Technology: mde
GitHub Login: @mjcaparas
Microsoft Alias: macapara

@RAJU2529 Thank you very much for the contribution and updating the documentation with PR. @v-sashig Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also


merge from template-arlac77-github

package.json

chore(deps): add ^5.1.5 remove ^5.1.3 (devDependencies.typescript)

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 95.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
167

Relevant Lines:
174

💛  - Coveralls


Android,Cannot read property 'showImagePicker' of undefined

Make sure you folow all the installation
You can instanciate the module in RN like this :
var UIImagePickerManager = require('NativeModules').UIImagePickerManager;

same here, are you sure about the require statement ? NativeModules ?

you can try like this too
var { NativeModules } = require('react-native');
var UIImagePickerManager = NativeModules.UIImagePickerManager;

it's maybe cause you don't require('react-native') at the beginning of the file
var React = require('react-native');
var UIImagePickerManager = require('NativeModules').UIImagePickerManager;

no response i close

In case anyone else runs into this, running react-native run-android (not included in the installation steps) fixed this for me.

You need to rebuild you project

thank you @callcter
ı made cd android
after than
gradlew clean
and runing


Creating a workspace item from an external source

This is the REST API development for https://github.com/DSpace/Rest7Contract/pull/83, the changes to workspaceitems.md only
It ensures submitters can create a new entity based on an external source as a workspace item.
This uses a POST on the /api/submission/workspaceitems, but using a URI-list (with the external source)
The item is created as a workspace item, the submitter can further edit the item hereafter.
For code reuse purposes, the ExternalSourceEntryUriListHandler class has been renamed to ExternalSourceEntryItemUriListHandler and made abstract, with the ExternalSourceEntryArchivedItemUriListHandler being used for https://github.com/DSpace/DSpace/pull/2590 and ExternalSourceEntryWorkspaceItemUriListHandler being used for this task

Thanks @tdonohue for your review, Raf has adjusted everything you requested

Thanks @paulo-graca for your review.
It's a known issue that MyDSpace UI doesn't use the item list component yet for rendering the list of items. Once that's solved, this complexity will be solved automatically.

Merging, as this is now at +2


No more HTML?

In the changelog it says:
"With the next major release of Homebrewery, v3.0.0, this tool will no longer support raw HTML input for brew code. Most issues and errors users are having are because of this feature and it's become too taxing to help and fix these issues."
I use a ton of HTML in my brews. SPANS and DIVS (with various classes), all my images are IMG tags, etc. How will these be handled going forward?

Good question. Most elements will just be done in Markdown syntax rather than the HTML syntax. For things like divs I am creating a new syntax to create a classnamed div. For example to create a background image,
{{titlePageBackground
  ![](http://linktomyimage.biz/cool.png)
}}

this would create the following rendered HTML

Defining styles will be broken out into it's own editor,
.titlePageBackground img{
  position : absolute;
  top : 40px;
  left : 60px
}

I use a lot of HTML /CSS as well to get things to look how I want. It looks like youre planning to still allow custom css and classes then. Maybe that will work. Does a separate style editor mean we have a separate window open or something? Would a style editor support LESS?

My goal with this change is to make easy things easier, and harder things harder. Right now the UI to access the style editor is to hit a toggle button in the snippet bar to toggle the editor to show the style code and back to the brew code.
Having precise control over the look of your brew will probably get trickier or more verbose, but honestly that's not the goal of this tool. If you want that precise control, Photoshop and templates will provide a much better experience.
And no support for less right now. The style overrides should be relatively simple.

Also, @dmmagic you asked your question is such a great way, thanks! I've been really apprehensive/worried about this big change for the last 2 months, but I think it's going to be for the best for the future of the tool. I don't take removing features lightly.
This will let me refocus my time on new features, tools, and compatibility, rather than trying to squash obscure HTML bugs.

No problem at all! You've created a magnificent tool!

I'll have more details when v3 gets closer to deploy.


The bot presence is not set.

I write everything as in the documentation. As a result, it returns a fattal error:

Can you install the develop branch by running composer require team-reflex/discord-php dev-develop? Then try:
$activity = $discord->factory(\Discord\Parts\User\Activity::class, ['name' => 'i am playing a game!']);
$discord->updatePresence($activity);

A token is used to install dev-development. What's it?

Not sure what you mean? I had no issues installing it to a test project. Are you typing it in correctly?
composer require team-reflex/discord-php dev-develop

Any ETA when develop changes will be released?

Any ETA when develop changes will be released?

Not sure yet sorry, I would still consider develop the most stable branch at the moment.

I'm really struggling to get this working. Do you perhaps have any pointers for me?
$this->setup();

$this->discord->on('ready', function($discord) {
   var_dump('update presence');
   $activity = $discord->factory(\Discord\Parts\User\Activity::class, ['name' => 'i am playing a game!']);
   $discord->updatePresence($activity);
});

The setup initiates an extended Discord instance. Responds to messages and all, so that seems to work fine and initiate at the right moment. However, the updatePresence bit doesn't seem to do anything.
After ready was triggered I can see update presence popping up, but nothing changes on the bot.
Are you aware of any limitations to test-bots? Or is there something else going on.
Thanks!

Try providing a type in addition to the name.

Awesome, thanks!
For people who come across this in the future:
When running the latest develop branch, use:
$discord->on('ready', function($discord) {
   $activity = $discord->factory(\Discord\Parts\User\Activity::class, [
       'name' => '!help',
       'type' => Activity::TYPE_LISTENING
   ]);
   $discord->updatePresence($activity);
});