feat: enable FIPS compliance by switching to ubi9 minimal and installing openssl; add Infrastructure Feature Test annotations (RHIDP-294)

What does this PR do?
feat: enable FIPS compliance by switching to ubi9 minimal and installing openssl; add Infrastructure Feature Test annotations (RHIDP-294)
Signed-off-by: RHDH Build (rhdh-bot<EMAIL_ADDRESS>Screenshot/screencast of this PR
N/A
What issues does this PR fix or reference?
N/A (or see commit message above for issue number)
How to test this PR?
N/A
PR Checklist
As the author of this Pull Request I made sure that:

[x] The Eclipse Contributor Agreement is valid
[x] Code produced is complete
[x] Code builds without errors
[ ] Tests are covering the bugfix
[x] The repository devfile is up to date and works, if one exists
[x] Sections What issues does this PR fix or reference and How to test this PR completed
[x] Relevant user documentation updated
[x] Relevant contributing documentation updated
[x] CI/CD changes implemented, documented and communicated

Reviewers
Reviewers, please comment how you tested the PR when approving it.

FIPS compliance checked with build https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=58051064
#➔ ~/4/check-payload/check-payload scan image --spec  registry-proxy.engineering.redhat.com/rh-osbs/rhdh-rhdh-rhel9-operator:rhdh-1-rhel-9-containers-candidate-69291-20240112183533
I0112 15:13:12.322240   43446 main.go:100] "scan" version="0.3.0-4-g362bde27"
---- Warning Report
+-------------------------+-----------------+-----------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------+
| OPERATOR NAME           | EXECUTABLE NAME | STATUS                                                          | IMAGE                                                                                |
+-------------------------+-----------------+-----------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------+
| rhdh-operator-container | /manager        | go binary has no build tags set (should have strictfipsruntime) | registry-proxy.engineering.redhat.com/rh-osbs/rhdh-rhdh-rhel9-operator:rhdh-1-rhel-9-containers-candidate-69291-20240112183533 |
+-------------------------+-----------------+-----------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------+
---- Successful run with warnings

By my math it's only 2x bigger https://quay.io/repository/janus-idp/operator?tab=tags ... adding only 32M to the compressed container image.

Yes, it somehow fits the data that image size grown from 6.9M to 36M (operator is like 22-25M).
Curious, if we need support FIPS upstream.

Counter argument: Why do we want the upstream operator code to be different from the downstream one? Do we want 2x the testing and support burden?


chore: bdd-spring-1576193938 to 0.0.1

chore: Promote bdd-spring-1576193938 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


BLE advertising broken in master branch? (IDFGH-5353)

I have code that worked few days ago and today i pulled esp-idf from master branch and here is error:
E (1085) BT_BTC: Invalid advertisting interval parameters.

Advertising parameters seems to be ok:
	esp_ble_adv_params_t m_advParams;
	m_advParams.adv_int_min       = 0x20;
	m_advParams.adv_int_max       = 0x40;
	m_advParams.adv_type          = ADV_TYPE_IND;
	m_advParams.own_addr_type     = BLE_ADDR_TYPE_PUBLIC;
	m_advParams.channel_map       = ADV_CHNL_ALL;
	m_advParams.adv_filter_policy = ADV_FILTER_ALLOW_SCAN_ANY_CON_ANY;
	m_advParams.peer_addr_type    = BLE_ADDR_TYPE_PUBLIC;

       err = esp_ble_gap_start_advertising(&m_advParams);

and return code is also ESP_OK, so why this error?
Full logs:
I (29) boot: ESP-IDF v4.4-dev-1404-gc13afea63-dirty 2nd stage bootloader
I (29) boot: compile time 21:50:18
I (30) boot: chip revision: 3
I (34) boot_comm: chip revision: 3, min. bootloader chip revision: 0
I (41) boot.esp32: SPI Speed      : 40MHz
I (46) boot.esp32: SPI Mode       : DIO
I (50) boot.esp32: SPI Flash Size : 4MB
I (55) boot: Enabling RNG early entropy source...
I (60) boot: Partition Table:
I (64) boot: ## Label            Usage          Type ST Offset   Length
I (71) boot:  0 otadata          OTA data         01 00 00009000 00002000
I (79) boot:  1 phy_init         RF data          01 01 0000b000 00001000
I (86) boot:  2 factory          factory app      00 00 00010000 00100000
I (93) boot:  3 ota_0            OTA app          00 10 00110000 0027a000
I (101) boot:  4 nvs              WiFi data        01 02 0038a000 00006000
I (109) boot: End of partition table
I (113) boot: Defaulting to factory image
I (117) boot_comm: chip revision: 3, min. application chip revision: 0
I (125) esp_image: segment 0: paddr=00010020 vaddr=3f400020 size=19e9ch (106140) map
I (172) esp_image: segment 1: paddr=00029ec4 vaddr=3ffbdb60 size=03598h ( 13720) load
I (177) esp_image: segment 2: paddr=0002d464 vaddr=40080000 size=02bb4h ( 11188) load
I (182) esp_image: segment 3: paddr=00030020 vaddr=400d0020 size=64f78h (413560) map
I (336) esp_image: segment 4: paddr=00094fa0 vaddr=40082bb4 size=13c34h ( 80948) load
I (369) esp_image: segment 5: paddr=000a8bdc vaddr=50000000 size=00010h (    16) load
I (380) boot: Loaded app from partition at offset 0x10000
I (380) boot: Disabling RNG early entropy source...
I (392) cpu_start: Pro cpu up.
I (392) cpu_start: Starting app cpu, entry point is 0x4008116c
0x4008116c: call_start_cpu1 at /home/chegewara/esp/master/components/esp_system/port/cpu_start.c:150

I (0) cpu_start: App cpu up.
I (406) cpu_start: Pro cpu start user code
I (406) cpu_start: cpu freq: 240000000
I (406) cpu_start: Application information:
I (411) cpu_start: Project name:     syrp-factory-app
I (416) cpu_start: App version:      1.0.0
I (421) cpu_start: Compile time:     Jun  3 2021 21:50:13
I (427) cpu_start: ELF file SHA256:  e8a496408e382826...
I (433) cpu_start: ESP-IDF:          v4.4-dev-1404-gc13afea63-dirty
I (440) heap_init: Initializing. RAM available for dynamic allocation:
I (447) heap_init: At 3FFAFF10 len 000000F0 (0 KiB): DRAM
I (454) heap_init: At 3FFB6388 len 00001C78 (7 KiB): DRAM
I (460) heap_init: At 3FFB9A20 len 00004108 (16 KiB): DRAM
I (466) heap_init: At 3FFC28D8 len 0001D728 (117 KiB): DRAM
I (472) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (478) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (485) heap_init: At 400967E8 len 00009818 (38 KiB): IRAM
I (492) spi_flash: detected chip: generic
I (496) spi_flash: flash io: dio
I (501) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
I (18) BTDM_INIT: BT controller compile version [d03a5d3]
I (544) system_api: Base MAC address is not set
I (545) system_api: read default base MAC address from EFUSE
I (553) phy_init: phy_version 4670,719f9f6,Feb 18 2021,17:07:07
E (1085) BT_BTC: Invalid advertisting interval parameters.

Untracked files:
  (use "git add <file>..." to include in what will be committed)
	components/bt/controller/lib/

nothing added to commit but untracked files present (use "git add" to track)
chegewara@ubuntu:~/esp/master$ git submodule update --init --recursive
chegewara@ubuntu:~/esp/master$

Why bt/controller lib is untracked, and all modules seem to be up to date.
Thanks

Never mind.


Network related metrics don't have container_name tag

Hello,
I'm running a dedicated heapster pod in a GKE (1.1) cluster with a dedicated influxdb sink:
      containers:
      - name: heapster
        image: gcr.io/google_containers/heapster:v1.0.0
        resources:
          limits:
            memory: 550Mi
        command:
          - /heapster
          - --source=kubernetes:''
          - --sink=influxdb:http://influxdb:8086

It seems that network related metrics don't have any container_name tag. All other metrics seems good.
Am'I missing something ? Is it intended ?
Regards,

No, you are not missing anything. Due to the way pods work and some current technical limitations the network stats are gathered at the pod level.

@mwielgus thank you for the clarification. It wasn't clear for me in documentation. Closing this one


[CH-215] Support shift left and shift right function.

Changelog category (leave one):

New Feature

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Support shift left and shift right function.

Information about CI checks: https://clickhouse.tech/docs/en/development/continuous-integration/

Can one of the admins verify this patch?

Attention: it must be merge after https://github.com/oap-project/gluten/pull/606

test this please


Extend Impulse.of with init: (scope: Scope) => T

It might be useful to be able to get another impulse value when creating a new one

Resolved in #586


Save datetime fractions of second

I'm using the datetime attribute in my model and would like to save accurate timestamps for my records. I'm using the sails-mysql adapter, and even after modifying the field into datetime(3) after initializing the model, it doesn't seem to save the fractions of second, but rather sets them to hh:mm:ss.000. Is this a waterline-related issue or sails-mysql related?

Hi @murhum1, this is not a waterline core issue but a sails-mysql adapter issue, namely in its helper library waterline-sequel. There is an open pull request to support milliseconds, check PR balderdashy/waterline-sequel#24.

Good call @dmarcelino!  Should we move this conversation over there?

Yes, I think that's better.

See you all over at balderdashy/waterline-sequel#24!  Is that okay, @murhum1?


Google "Cannot Connect to Homebridge" Error

Issue Description
While attempting to get the access token, I was stopped at the step involving the following URL:
```
https://nestservices.google.com/partnerconnections/project-id/auth?redirect_uri=https://www.google.com&access_type=offline&prompt=consent&client_id=oauth2-client-id&response_type=code&scope=https://www.googleapis.com/auth/sdm.service
```
An error occurred that prevented me from proceeding. Screenshot attached, but basically Google saying they can't talk to Homebridge. Not an issue with your setup (I don't think?), but figured others will run into it as well.
Environment

Plugin Version: v1.0.3
Homebridge Version: v1.6.1
Node.js Version: 20.8.0
NPM Version: 10.1.0
Operating System: macOS Sonoma (M2 silicon chip)

Steps to Reproduce

Navigate to the Nest Services Google authentication URL.
Follow the prompts for authentication.
Reached the step right before attempting to get the access token.

Expected Behavior
The authentication process should complete successfully, allowing me to proceed to next step, where I could curl to get the access token.
Actual Behavior
(Authentication fails/Error message appears/etc.)

I have the same issue

Closing due to lack of activity.


Merge master-qa

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: LucasBrazi06:white_check_mark: YassineCH96:x: melvynduboisYou have signed the CLA already but the status is still pending? Let us recheck it.


Rancher UI freezes when posting any edit to cluster through v3 api

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):

deploy rancher v2.5-head (8b65a6abb)
add any cluster (tested on node provisioned fully active, imported without running on downstream cluster, custom without running on downstream node)
edit any field through v3 api
post request

Result:

rancher is unresponsive. logging in to the node running rancher has the following errors:

[mgmt-cluster-rbac-delete] Updating cluster c-qqw4n
I0211 00:10:01.219099      26 controller.go:606] quota admission added evaluator for: clusterregistrationtokens.management.cattle.io
I0211 00:10:24.897927      26 topology_manager.go:219] [topologymanager] RemoveContainer - Container ID: 0f22e51bec819b435d05c8e2f6376418c3536820a1a3d2b097ae798cbd9ce54f
2021/02/11 00:10:28 [ERROR] could not convert gke config to map
2021/02/11 00:10:28 [ERROR] could not convert gke config to map
2021/02/11 00:10:33 [ERROR] could not convert gke config to map
I0211 00:10:34.897780      26 topology_manager.go:219] [topologymanager] RemoveContainer - Container ID: c84c34a4b454fd206c223ab1ca3557b49894bb2e84024f8286a01a70a1ddabd2
I0211 00:10:34.898016      26 topology_manager.go:219] [topologymanager] RemoveContainer - Container ID: beabb2276b12dc9492669af25dce777f622d85cbcb18fc212de8f6878d40dbf5
I0211 00:10:35.898304      26 topology_manager.go:219] [topologymanager] RemoveContainer - Container ID: ba77afcf6a1abffdeee4638752b677120900688df0f2cf98b749a0fda0af194f
2021/02/11 00:10:38 [ERROR] could not convert gke config to map
I0211 00:10:39.899868      26 topology_manager.go:219] [topologymanager] RemoveContainer - Container ID: 6c2f0916914845ad6917151eae9e5a29010dbe90325c18608f46988da13187cc
I0211 00:11:05.909405      26 topology_manager.go:219] [topologymanager] RemoveContainer - Container ID: c3936ce54b97347c9490fa98f7a336c0387d141dd04579d5a819c3bd98cdabbf
I0211 00:11:31.900533      26 topology_manager.go:219] [topologymanager] RemoveContainer - Container ID: 0f22e51bec819b435d05c8e2f6376418c3536820a1a3d2b097ae798cbd9ce54f
I0211 00:11:50.897939      26 topology_manager.go:219] [topologymanager] RemoveContainer - Container ID: ba77afcf6a1abffdeee4638752b677120900688df0f2cf98b749a0fda0af194f
I0211 00:12:00.897669      26 topology_manager.go:219] [topologymanager] RemoveContainer - Container ID: 6c2f0916914845ad6917151eae9e5a29010dbe90325c18608f46988da13187cc
I0211 00:12:04.897840      26 topology_manager.go:219] [topologymanager] RemoveContainer - Container ID: beabb2276b12dc9492669af25dce777f622d85cbcb18fc212de8f6878d40dbf5
I0211 00:12:04.898099      26 topology_manager.go:219] [topologymanager] RemoveContainer - Container ID: c84c34a4b454fd206c223ab1ca3557b49894bb2e84024f8286a01a70a1ddabd2
I0211 00:12:21.900210      26 topology_manager.go:219] [topologymanager] RemoveContainer - Container ID: c3936ce54b97347c9490fa98f7a336c0387d141dd04579d5a819c3bd98cdabbf
I0211 00:12:40.897566      26 topology_manager.go:219] [topologymanager] RemoveContainer - Container ID: 0f22e51bec819b435d05c8e2f6376418c3536820a1a3d2b097ae798cbd9ce54f
I0211 00:13:07.902937      26 topology_manager.go:219] [topologymanager] RemoveContainer - Container ID: ba77afcf6a1abffdeee4638752b677120900688df0f2cf98b749a0fda0af194f
I0211 00:13:10.897828      26 topology_manager.go:219] [topologymanager] RemoveContainer - Container ID: c84c34a4b454fd206c223ab1ca3557b49894bb2e84024f8286a01a70a1ddabd2
I0211 00:13:19.898642      26 topology_manager.go:219] [topologymanager] RemoveContainer - Container ID: beabb2276b12dc9492669af25dce777f622d85cbcb18fc212de8f6878d40dbf5
I0211 00:13:23.897628      26 topology_manager.go:219] [topologymanager] RemoveContainer - Container ID: 6c2f0916914845ad6917151eae9e5a29010dbe90325c18608f46988da13187cc
I0211 00:13:45.901385      26 topology_manager.go:219] [topologymanager] RemoveContainer - Container ID: c3936ce54b97347c9490fa98f7a336c0387d141dd04579d5a819c3bd98cdabbf

Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.5-head (8b65a6abb)
Installation option (single install/HA): single install/HA

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): imported (did not add any nodes)
Machine type (cloud/VM/metal) and specifications (CPU/memory):

Seeing the same behavior when I create a custom cluster with aciNetworkProvider.

Create a custom cluster in UI.
Edit in API to set aci network plugin,

	"network": {
		"aciNetworkProvider": {
			"apicHosts": ["<IP_ADDRESS>"],
			"kubeAPIVlan": "hello",
			"apicRefreshTime": "1200",
			"systemId": "rancher",
			"type": "/v3/schemas/aciNetworkProvider"
		},
		"mtu": 0,
		"plugin": "aci",
		"type": "/v3/schemas/networkConfig"
	},

Fields show up in API correctly,

Same error in UI as original issue.

index.js:1412 Uncaught (in promise) TypeError: Cannot read property 'publicAccess' of null
    at ye (index.js:1412)
    at Object.ve [as get] (index.js:1396)
    at n.<anonymous> (cluster.js:191)
    at index.js:1977
    at e.untrack (validator.js:835)
    at i.a.get (index.js:1976)
    at n.eksDisplayEksImport (index.js:1047)
    at n.<anonymous> (cluster.js:483)
    at index.js:1977
    at e.untrack (validator.js:835)

I can now make edits through v3 on v2.5-3e96d7fb1c0478b14fb82092410a5ac9926e0ac0-head and master-9ef8e69d2dcd87e8623eb7a1aa5da8b2b27a5b7b-head


test_suite/test_sequence_success.py assumes content-length will be sequence length

test_suite/test_sequence_success.py currently tests content length. However if a server had compression enabled using Accept-Encoding (whilst not part of the spec a server may decide it wants to support this) requests will make a request with the appropriate headers set. If this happens then the response Content-Length header refers to the length of the gzipped content not the underlying sequence. We can only check this test if we did not have gzip encoding like so.
if all (k not in response.headers for k in ('transfer-encoding', 'content-encoding')):
    assert int(response.headers['content-length']) == seq.size

Perfect Somesh. Please don't worry about fixing these as they won't affect your GSOC grading


Avoid "eRouska is paused" notification if other ENS app is active

I understand that may be part of a minority of users, but especially until the data sharing problem is resolved I expect there will be more people like me, who have more than one ENS app installed.
I use the UK's NHS Covid-19 app where I have tracing enabled and I'm getting the following notification repeatedly from eRouska:

I think the notification is helpful and I would want to keep getting it, but obviously not in this context.
The only option I realistically have now is to either uninstall it until I travel back to 🇨🇿   or suppress that notification category, which does not seem ideal to me.
Is there any API that would allow you to check whether there is any other active ENS app and avoid sending that notification in such case?

I'm not aware about an API for checking other ENS apps. This will be solved with data sharing, we are already working on it in branch feature/efgs.

We are working of integration of EFGS: https://github.com/eu-federation-gateway-service/efgs-federation-gateway
This is an EU initiative, led by the German team. Because of Brexit, not sure about the UK.

Gotcha, I suppose there isn't much you can do then, if there isn't any API available.
I assume that uninstalling eRouska or suppressing notification is the only solution until/unless EFG or similar project allows data sharing, which is understandable.
Thank you for all the work you do btw.!


add tooltip prototype

Example for #22 for further discussion.

Looks great, @eum2o ! 😍
I would expect tooltips only on the non-int cards because whether some int card requires low effort or not is imho up to the team and the work they estimate. The only common thing is that the estimation correlates w/ the numbers - so the tooltips on those int cards might be misleading. e.g. what card would mach: "It should be rather low effort, but the task has a high risk"...
On the others I would like:
🤷♂ "Don't know" or "Can't tell"
☕ "Need a break"
✂ "Too big for one ticket"

Looks good 2 me now. ^^

How about

"Cut into estimatable parts" or
"Cut into manageable parts"
?

"Too big to handle"?

Cut smaller

Mmmmeh-ish. Sounds kinda denglish to me. 😉


Load private key from file system

As far as I know Web Crypto API allows usage of local private keys (.p12 of pkcs#12-formatted files). But in the examples page I found only generate-key-on-the-fly or read-binary-.cer methods. Does PKI.js support loading local .p12 file?
Thanks!

In Web Cryptography API there are functions for importing/exporting keys from "spki" (public keys) and "pkcs8" (private keys) format. PKCS#12 format is a special format to convey encrypted data about certificate and private key. There is no support for PKCS#12 in Web Crypto. But it is possible to create special "helper" to work with PKCS#12 files. It would be implemented in PKIjs but this task not not so important for PKIjs library development at the moment. Meanwhile you can use importing/exporting private keys into "pkcs8" format. How to use it was shown in this example.

Thank you for the fast response!
If I got you properly, I can implement pkcs#12 "helper" in pure JS, am I right? Do you mean by implementing "helper" a lot of boilerplate .p12-file parsing JS-code or you mean using special "native" tool like openssl and calling executable from JS via ActiveX and further handle converted file with JS?

I mean "a lot of boilerplate .p12-file parsing JS-code". Inside PKIjs such "helpers" are inside "*_simpl.js" files, take a look. As I said support for PKCS#12 would be allso a part of PKIjs, but its not in our nearest plans.

Thanks!

I'm also very interested also in parsing pkcs#12!

I believe I will find a time to implement the PKCS#12 soon.

Nice ;)

Now we have PKCS#12 in latest release. Unfortunally PKIjs uses modern crypto algorithms and Windows uses very old algorithms. That is why our version of PKCS#12 data could not be read via standard Windows GUI. But OpenSSL is able to work with some of our output formats with option "-nomacver".


Add PodPreset basic usage instructions

This change is

@surajssd can you help uncheck and check the allow editor to edit button in your PR page? I'd like to do an edit on your change.

@tengqm done :-)


Can't verify CSRF token authenticity with Fetch API

Hi, so I get this error in the server when I try to do a fetch request in React
 Can't verify CSRF token authenticity.
 ActionController::InvalidAuthenticityToken (ActionController::InvalidAuthenticityToken)
 ActionController::InvalidAuthenticityToken - ActionController::InvalidAuthenticityToken

Here is my fetch request
  onConfirm = () => {
    let headers = {
        'Content-Type':'application/json',
        'Accept': 'application/json',
      }
    fetch('/parcel/booking', {
      method: 'post',
      header: ReactOnRails.authenticityHeaders(headers),
      body: {
        "booking[amount]": this.props.amount,
        "booking[agent_id]": this.props.agent.id
      }
    }).then(function(response) {
      console.log(response)
    })
  }

I tried doing ReactOnRails.authenticityHeaders(headers) in the console and I got this
{Content-Type: "application/json", Accept: "application/json", X-CSRF-Token: "vtlbcJKc9RLJt5GvrTYggItU0RfsfU9vSNGUdmCA3y1pA9MGEC863dz2WyH2K2G9nlGqvvDfR4CsVTAp/AoGBQ==", X-Requested-With: "XMLHttpRequest"}

So it seems thats working.
Am I missing something?

Take a look at

https://github.com/shakacode/react_on_rails/blob/master/node_package/src/ReactOnRails.js#L102
https://github.com/shakacode/react_on_rails/blob/d5d579e7c1a24667eb5ccfbb34c17c0e898d6bf9/docs/api/javascript-api.md
https://github.com/shakacode/react_on_rails/blob/57fdc402a67155d3f93bc4f89c5aec064092f26f/README.md#L634

Would you be interested in our ShakaCode Pro Support plan?
http://www.shakacode.com/work/shakacode-pro-support.pdf
If so, please schedule a complimentary 30-minute consultation:
https://calendly.com/justingordon
Thanks,
Justin
<EMAIL_ADDRESS>

@hewrin My firm has built https://www.hawaiichee.com and we've got lots of experience on the nuances of the CSRF issues.

@foo4foo I invited you to our Slack Room. You can ask the group there.

@justin808 Can i also join your slack room? I wanna learn more about react_on_rails

@ivanraybuglosa @acherukuri I believe I faced this problem using FETCH API only. Sending requests using axios did the trick.


[master] Upgrade to latest dependencies

Cron. -knative-prow-robot
/cc knative/serving-writers knative/eventing-writers
/assign knative/serving-writers knative/eventing-writers
Produced via:
./hack/update-deps.sh --upgrade --release v0.21
./hack/update-codegen.sh

Details:
bumping knative.dev/hack 8d623a0...8368e1f:
  > 8368e1f guard against set -o unset (# 49)
  > 2b4f6fc disable go's proxy and sumdb only for knative deps (# 47)

/lgtm
/approve
/retest


Panic on graph creation

It is impossible to create graph via admin interface - output is attached
facette.txt

Strace output is attached too
facette-strace.txt

Hi
Looking at your error log it's more like your Facette instance process got a "segmentation fault" signal following the opening of a RRDtoo file:
[pid  3811] open("/var/lib/collectd/eye/cpu/percent-system.rrd", O_RDONLY) = 12
[pid  3811] fstat(12, {st_mode=S_IFREG|0644, st_size=148648, ...}) = 0
[pid  3811] mmap(NULL, 148648, PROT_READ, MAP_PRIVATE|MAP_NORESERVE, 12, 0) = 0x7f3906851000
[pid  3811] madvise(0x7f3906851000, 148648, MADV_RANDOM) = 0
[pid  3811] munmap(0x7f3906851000, 148648) = 0
[pid  3811] close(12)                   = 0
[pid  3811] --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0} ---
[pid  3811] rt_sigreturn({mask=[]})     =<PHONE_NUMBER>01392

Is it coincidental? Could you try to start Facette excluding the file /var/lib/collectd/eye/cpu/percent-system.rrd?

It works on system with kernel 3.14.22 and did not work on system with kernel 4.1.13 (on host system and inside systemd-nspawn container). Both facette instances are extracted from deb into /opt as described in https://github.com/facette/facette/issues/284

Problem is reproducing on all rrd files created by local installed collectd.

Problem is even reproducing on copied rrd files from system with 3.14.22 on which facette works correctly with the same files

Maybe some libraries are missing? I can give ssh access tomorrow into container with panic if it may help.

Is it possible there is a mismatch between 32 and 64-bit architectures? RRDtool is sensitive to that, although I don't think it would crash the entire program.

All systems are x86_64

Which versions of Facette and librrd are you using?

Build Information
Version: 	0.3.0
Build Date: 	2015-07-08
Compiler: 	gc (go1.4.2)
Built-in Connectors: 	facette
graphite
influxdb
kairosdb
rrd

librrd4-1.4.7-alt3.1 on working system and librrd4-1.5.4-alt1.1 on panic

Looks like the RRDtool binding we rely on (https://github.com/ziutek/rrd) only supports librrd 1.4.x and crashes on 1.5.x, see this issue: https://github.com/ziutek/rrd/issues/24
Unfortunately there is nothing we can do for this particular problem, sorry. Could it be possible to downgrade your librrd to 1.4.x?

This possible a duplicate of #207

@enp, have you tried to compile Facette from the sources linking it on the rrd 1.5 library?

Tried now. Version 0.4.0dev (last trunk) allows to create graphs, version 0.3.0 fails with the same output as above. Go version is 1.5.1 in both cases.


chore: Upgrade to Spring Boot 3.0.6

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


A new DROP benchmark is needed

@clefourrier has been investigating the DROP benchmark and has discovered that it has some serious problems, as are detailed in our recent blog post together and her previous this issue https://github.com/EleutherAI/lm-evaluation-harness/issues/978. We've established that:

The current implementation matches the official one.
The official implementation makes systematic errors in how it handles preprocessing and grading that make it hihgly non-desirable to use.

The purpose of this issue is to solicit input from the community on whether you use DROP to evaluate language models, how you use it, and if you have any input on how we should evaluate it going forward. We will definitely continue to support the official implementation, but this is a case where it seems like we should change the default implementation to something more reasonable.
In general, we following the following priority list for addressing concerns about prompting and other eval details:

If there is widespread agreement among people who train LLMs, use the agreed upon procedure.
If there is a clear and unambiguous official implementation, use that procedure.
If there is widespread agreement among people who evaluate LLMs, use the agreed upon procedure.
If there are multiple common implementations but not universal or widespread agreement, use our preferred option among the common implementations. As before, prioritize choosing from among the implementations found in LLM training papers.

These are guidelines and not rules, and can be overruled in special circumstances.
We try to prioritize agreement with the procedures used by other groups to decrease the harm when people inevitably compare runs across different papers despite our discouragement of the practice. Historically, we also prioritized the implementation from "Language Models are Few Shot Learners" as our original goal was specifically to compare results with that paper.

@clefourrier has been investigating the DROP benchmark and has discovered that it has some serious problems, as are detailed in our recent blog post together and her previous this issue https://github.com/EleutherAI/lm-evaluation-harness/issues/978. We've established that:

Would you mind pointing a link towards the said blog post?

@clefourrier has been investigating the DROP benchmark and has discovered that it has some serious problems, as are detailed in our recent blog post together and her previous this issue #978. We've established that:

Would you mind pointing a link towards the said blog post?

I jumped the gun a little bit... the blog post needs to reference this issue and this issue needs to reference the blog post and I figured nobody would notice if I pushed the issue a little early 😅
As soon as the blog post goes live I'll edit the link in!

Blog is up here

The official implementation makes systematic errors in how it handles preprocessing and grading that make it hihgly non-desirable to use.

Can you say more about this?  What official implementation are you talking about, and what specifically is wrong with it?  From the blog post, most of the errors mentioned looked like they were not related to the official scoring, they were related to the generation procedure.
And for the record, if there are problems with the "official" scoring, they should absolutely be fixed.

I may have traced through the various github comments enough to answer my question (this comment gave me confidence I was understanding the issue correctly).
I can tell you that the DROP metric was intended to be as close as possible to the SQuAD metric, but with better handling of numbers, and with an attempt to deal with sets of answers.  The particular tokenization issue that's at the heart of the 10\n\nPassage problem is just a carryover from using the original SQuAD implementation.  At the time these datasets were made, we didn't really conceive of models that would return things involving newlines, and so the metrics didn't account for them.  The tokenization should be fixed.

Well, actually, I take back the assertion that the tokenization came from SQuAD.  I looked more closely at the SQuAD script and didn't find that tokenization in there.  I also don't see that tokenization in the original evaluation code for DROP.  I'm not sure at what point it got added to the computation in allennlp-models, nor what code is actually backing the official AllenAI leaderboard (I don't have access to that code at this point, if it even matters anymore).  But regardless, that tokenize method is clearly just wrong.

Can you say more about this? What official implementation are you talking about, and what specifically is wrong with it? From the blog post, most of the errors mentioned looked like they were not related to the official scoring, they were related to the generation procedure.
And for the record, if there are problems with the "official" scoring, they should absolutely be fixed.

Perhaps I'm using the word "scoring" here a little loosely, but I'm talking about the generation termination criteria and the answer extraction procedure.

I also don't see that tokenization in the original evaluation code for DROP. I'm not sure at what point it got added to the computation in allennlp-models, nor what code is actually backing the official AllenAI leaderboard (I don't have access to that code at this point, if it even matters anymore). But regardless, that tokenize method is clearly just wrong.

Your link to the "original DROP code" 404s for me. Is it a private repo?
Unfortunately the paper contains almost no algorithmic detail about the implementation so we were forced to rely heavily on the codebase. I had been assuming that the backend for the leaderboard would be using the same code that the leaderboard links to... do you think we should take seriously the idea that they might differ?

Yeah, no worries, I didn't take it as criticism of the paper, just making sure I understand the issue.
I looked even more deeply through the history, and I found that this is the first commit where I added the official DROP eval script to allennlp.  The tokenization issue is in that commit also.  So somewhere between Dheeru's original implementation (in an apparently private repo) (which I thought was what backed the metrics in the original paper, but now I'm questioning that given what I see in the allennlp repo...) and the commit that I added, someone introduced that tokenization bug.  There are several candidates for who did it, including me, and I won't try to throw anyone under the bus :).  But I think it's pretty clearly a bug that should be fixed, owing to us not testing cases that we didn't expect to see at the time.  And given what I see now in the history, I'm confident that it's that script that is behind the leaderboard.  I looked too quickly earlier today.
As far as what you should do - my vote would be to fix the bug in the eval script, doing whatever is needed to have a sane evaluation.  "Fairness" with prior work doesn't really matter if the evaluation is nonsensical in the first place.  If I were still in control of the DROP leaderboard I would fix it there, too (well, really, I might declare that the leaderboard has served its purpose and make the test set public, but that's a separate issue...).

Hi, I want to loop in to see if I can help from AI2 internally.
From a quick skim, it seems there are two issues:

Our original eval tokenization didn't consider the newline token, which was not a big deal in the reading comprehension context but became very common in evaluating LLMs.
The using . as a stopword token in the OpenLLM leaderboard generation. Based on the nice analysis in the blog post, it seems using \n is clearly a better choice.

I could help fix 1 if @matt-gardner and @dDua think it's a good idea. But I think 2 needs to be fixed anyway from the OpenLLM leaderboard side, and if you use \n as the stop token, fixing 1 won't make any difference.

Btw, the reference implementation we assumed was the original is this one

The official code for GSM8k samples 100 tokens
It looks like TriviaQA doesn't define an official sampling procedure, as their code assumes you have the generations already and just does the evaluation.
I'm finding the official SCROLLS code a bit confusing but there isn't anything that is obviously a condition for stopping generation.

Sorry, a bit late to the party (EMNLP etc.)
As I understand it there are tokenization\generation problems in some examples, but we can find which quite easily (or a superset at least).
As we

only care about evaluation
have sunk cost of (2k models?) that already ran this
think this evaluation is already costly
Why bother fixing in LM eval anything? The solution of just ignoring those examples solves it all (also follows our recent efficient benchmarking). It is quite unlikely that we need 9K examples for any evaluation, one this is only a number in a list is even less so. We can happily live with say 1K. This saves a lot of compute forward. This can use the results we already ran, just need to compute the average again, with little fear that the new implementation requires rerunning everything.

Imo, the answer to both is simple and the following.
There is a big difference between:

the Eleuther LM Eval Harness, an evaluation suite which aims at providing a reference implementation for as many evaluations as possible (and therefore needs to have correct implementations of said evaluations)
and the HuggingFace OpenLLMLeaderboard, a leaderboard, which aims to provide a ranking of LLMs at a given time on a given number of evaluations.

Whether we chose to keep or not DROP in the leaderboard, it would still need to be fixed in the harness - and as we want the leaderboard to follow the harness implementation, we removed it from the leaderboard.

This also answers the tweet you pointed, where my phrasing was not very good (I should have used reference, instead of original implementaiton): we want people using the leaderboard to be able to compare their results to the reference implementation in the harness - if people publish papers with the harness evaluations, their results should be comparable to the leaderboard's.

I see the difference. If it is only for evaluation purposes 9K is excessive also for the harness, the fact that Matt happened to get this number of examples doesn't mean we need to use all of it, it is an arbitrary sample from the unlimited amount of examples he could have created. The evaluation would be correct in that way (for any example given).
The other option is to work much harder and get the evaluation metric to work on every example, I don't see why the effort is worth it unless the metric is also used on other datsets or the fix is very easy (and we don't count the leaderboard in this decision that loses) or we assume the deletion systematically deletes something of special importance (e.g. floats are especially critical).


Update for PureScript 0.11.5

https://github.com/purescript/purescript/releases/tag/v0.11.5

Coverage remained the same at 100.0% when pulling a4feaf0326196df6f72aa1f00a1b1e9d0462ab1f on damncabbage:topic/bump-0.11.5 into 68f41d82c91b52726bb27a34e5e61eb82e51dfce on purescript-contrib:master.

Published to npm.
$ npm view purescript version
> 0.11.5


Still no way to programatically screenshot?

Is there no way to programmatically access the underlying buffer and take a screenshot? It looks like headless is the easiest way to do it but a lot of my data is resident elsewhere and I can't really proxy things correctly to make it work. All my calls to screenshot are failing. I'd be fine even if i could just trigger the javascript that downloads the file. Has anyone hacked this together to make a short movie without being in headless mode?

Dear Matt,
It should be working, if the ipv.screenshot() and friends are not working, please open an issue for that. The other option is to hit the 'image' icon in the toolbar.
cheers,
Maarten

Could you write me a quick code snippet for how to save a movie without running in headless mode?

And movie works using ipv.movie(..), which makes a series of screenshots and encodes them as gif or encodes them using ffmpeg.

Let me know if this works btw!

Sorry, maybe I was unclear. I'd like to make a rotating clip of an object, so say I load an object like so:
p3.plot_trisurf(x, z, y, triangles=faces, color='white')
how do I rotate it and make a movie? I'm happy to just screenshot each frame, but will something like that work? Because I keep getting timeout, no data errors


adding is_unlocked column to report_history table

Description
Added is_unlocked column to the report_history table to allow reports to be copied
Checklist

[ ] I have read the CONTRIBUTING doc
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have already been accepted and merged

Further comments

Thanks for the PR!
Deployments, as required, will be available below:

Frontend

After changing the database, you have to run "npm run pull" in the backend folder.


Testnet contract search returning error

I tried to inspect a contract on Goerli testnet, but both testnet and testnet2 options were returning errors "Error No result found". The same contract address returned result details on Starkscan.co

Hi! Thanks for filing the issue, unfortunately we don't yet support contracts on the explorer, it is one of the Remaining Tasks listed on the README.

Hi! Thanks for filing the issue, unfortunately we don't yet support contracts on the explorer, it is one of the Remaining Tasks listed on the README.

Oh, Okay... Fede's Intern directed me to open the issue here  though.


Python file that generates corresponding header file for Cifar10

Hello Brad,
Can you please add the python file that trains a binary network based on cifar10?
Regards
Hassan

Yes -- I will do sometime in the next day or so. Thanks.

Look forward to it.
in examples, only filter size is given, is the default number of layers is 1?
Thanks

Sorry for the delay. I think the current codebase can already generate the header file. Please try running:
python simple.py --dataset cifar10. Note that the model would need to be improved (made larger) in order to get good results for cifar. This will generate the header file after completing training.


Implement threadgroup memory

Migrated from https://bugs.webkit.org/show_bug.cgi?id=189884:
At 2018-09-22T11:03:57Z<EMAIL_ADDRESS>wrote:
Implement threadgroup memory

Duplicate of https://github.com/gpuweb/WHLSL/issues/63


Stricter access control

:koala:
/cc @zendesk/quokka
Risks

None

@zendesk/quokka :haircut:

:+1:

setting it to the origin (instead of *) will send the session over, do you care? Shouldn't matter since its the local machine but also should be useless since it is encrypted.

@adammw any security concerns with leaving it '*'?

:+1:

@danielbreves only thing I can think of is that the browser might cache the "*" value and use it to allow future requests when served from cache. But mostly it just seems a bit improper.


Enable bench unittests for CI performance testing

Refactor of SQLite initialization to make integration with unittests easier

Add bench step to GitHub "makecheck" workflow

Disable prevector bench test

Port nano test bench framework from BitcoinCore

Standards checklist:

[x] The PR title is descriptive.
[x] The PR doesn't replicate another PR which is already open.
[x] The PR has self-explained commits history.

[x] The code is mine or it's from somewhere with an Apache-2.0 compatible license.
[x] The code is efficient, to the best of my ability, and does not waste computer resources.
[x] The code is stable and I have tested it myself, to the best of my abilities.
[x] If the code introduces new classes, methods, I provide a valid use case for all of them.

Changes:

[...]

Other comments:
...

@Budbury Thank you for your contribution. Could you update the SQLiteDatabase class, because checkpoints are no longer supplied via separate files - we have sewn them into the code.


ungoogled-chromium: 110.0.5481.177 -> 111.0.5563.65

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

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

[ ] Fits CONTRIBUTING.md.

I manually backported the update in #220710 - forgot to consider the LLVM changes... (luckily M111 should still build fine with LLVM 14).


Numpy bug/warning when calling MapieRegressor predict()

When calling predict on test set, this warning appears. This might be related to your aggregate_with_mask function
since it used np.median. Related issue see here: https://stackoverflow.com/questions/45786763/median-filter-produces-unexpected-result-on-fits-file
Error message on Linux:
anaconda3/envs/MASTER/lib/python3.10/site-packages/numpy/lib/function_base.py:4638: UserWarning: Warning: 'partition' will ignore the 'mask' of the MaskedArray.
  arr.partition(concatenate((virtual_indexes.ravel(), [-1])), axis=0)

i have two solution for this problem:
1. just ignore it :)
import warnings
warnings.filterwarnings('ignore')
2. delete the mask
the mask come from this:
ma.masked_invalid(lower_bounds)
change it:
lower_bounds
may help~

I ignored it but this seems to lead to other significant problems. I had a big dataset, where I had to split the prediction on many data folds, which worked fine. However for cv=10 my prediction looks like this:

I assume 0 is the single_estimator attribute and 1-10 are the folds. Column 0 is the prediction and column 1 the interval. But why are they not aggregated, from my understanding the result should be a prediction on the dataset as a whole.
I think this is related to the aggregate_with_mask function but I do not know how to get the right prediction arrays here.

Fixed by PR #135


Implement multi-line progress message support

This PR adds support for multi-line progress messages, following #442.
The changes mostly update the drawing functions to split progress messages before counting them, so that the correct number of lines are cleared when they are redrawn. I'm not sure I 100% understood how orphan lines work, so I'd appreciate if someone could take a closer look at how I handle them.
The existing examples all run as they did previously, and I've added a new example (multi-log) showing the style I was trying to implement when I opened the issue.
One thing I noticed is that calling clear on a multiline progress doesn't always seem to clear all progress messages, a random amount stays on the screen even when a message is printed afterwards. I first thought that I introduced that bug, but switching back to main it still appeared in the examples I tried (yarnish and multi). Is this a known bug?

If lines does not contain one element per line, that seems like a problem to me. Should we split up multi-line messages earlier in the process to deal with this?

Could you provide an example of this happening? It would probably be possible to render completely on a line-by-line basis, since the render target is not really aware of the content of the lines and just redraws everything every time. I'm not sure I understand the issue you're referring to here though.

I'm honestly not sure I 100% understand them, myself. chris-laplante do you? I think they're used to keep track of how many lines we drew in the previous iteration, so that we can correct if we're drawing fewer lines in the current iteration.

From what I could glean from the code, it's about cleaning up old lines when the progress is dropped, as well as when lines are printed manually by the user and lines that were moved up as a result need to be forgotten. So I defaulted to counting multiline strings in there as well, since they could potentially contain multiline messages set by the user. Not sure if this is necessary though.

Would you mind filing a separate issue about this?

Sure, will do!

The code is a little hard to follow, but what I understand is that orphan_lines are only used to implement println. I'll try to go through and add some comments and/or clean up the code to make it easier to understand.

Cool, feel free to make changes or add suggestions on my PR.

Cool, feel free to make changes or add suggestions on my PR.

Will do, but BTW I meant that the code in indicatif currently is a little hard to follow, not your code :)

Haha, don't worry about it, that's not how I took it. I didn't add enough code for it to be too complicated anyways :-P

Is there anything I can help with to move this along? I'm depending on my fork with my own projects for now, but of course I'd prefer if I can go back to upstream. I don't mind this taking longer, but I'd be happy to help if I can speed up the process :-)

I'm still wondering if there's a good reason not to have one element per line in DrawState::lines, rather than potentially multiple lines per element due to nested \n. IMO we should deal with that in a different way, by splitting up the message in set_message().

Just had a more thorough look at this. From what I can see, the different parts of the status (msg, prefix and so on) are set separately, and then they are appended to DrawState::lines in ProgressStyle::format_state. This means that if we want to already split multiline messages in set_message, we would need to have Vecs for all of the parts of the status, since both prefix and message (and maybe even the bar?) might have multiple lines.
This already introduces overhead (Vec instead of String for every part that can contain multiple lines), but also gets very complicated since the last line of each part needs to be joined together with the first line of the next part. Also, having newlines in the template is not even possible like this.
I think my approach is not optimal, but it makes the rendering of newlines in any part of the progress state a part of the rendering process, which allows any amount of newlines in any part of the template or message.
Maybe I misunderstood you and I'm missing an easier solution here... What do you think?

Hmm, maybe it would be better to split stuff inside ProgressStyle::format_state()?

Alright, that turned out to be a great idea! I'm now splitting the buffer right before any new lines are appended, and running the same code as before if no newlines are contained. This should handle all cases, even when the newlines are split over different parts of the template.
This also enabled me to add some tests for the cases I added. Have a look and tell me if there's anything else I can add.

Alright, all done. Please let me know if there's anything else I can do.

This looks good to me! I think there is some potential for optimization, but this will do as a first take. @chris-laplante any thoughts?

It looks good to me too and some light testing on my own code gives correct results :). The only thing I'm wondering is whether we've tested what happens when you change the number of newlines in messages using ProgressBar::set_message. Especially when part of MultiProgress. I want to make sure it doesn't under/over-erase lines.

You could submit some tests for the case Chris mentioned in his last comment, I think?

Alright, I've added additional tests that render a MultiProgress, set multiline messages and then single line messages again using set_message, increase the progress and then finish the progress using finish_with_message.
Please tell me if these tests cover the cases you were thinking about.

Thanks for adding the tests! This looks good to me. @djc alright to merge?

Great, thanks!


401 error when deploying http function

Does this occur consistently?
Repro steps:

Followed steps here https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-first-function-vs-code?pivots=programming-language-python

Action: azureFunctions.deploy
Error type: 401
Error Message: Failed with code "401".
Version: 0.21.0
OS: win32
OS Release: 10.0.18362
Product: Visual Studio Code
Product Version: 1.43.0
Language: en

Call Stack
extension.bundle.js:496:399875extension.bundle.js:496:399875
retryCallback extension.bundle.js:338:114595
retryCallback extension.bundle.js:127:31063
extension.bundle.js:127:32676extension.bundle.js:127:32676
handleRedirect extension.bundle.js:254:7752
extension.bundle.js:127:29848extension.bundle.js:127:29848
Request._callback extension.bundle.js:1:686346
Request.n._callback.n.callback.n.callback extension.bundle.js:314:6016
Request.emit events.js:203:13
Request.<anonymous> extension.bundle.js:314:19288
Request.emit events.js:208:15
IncomingMessage.<anonymous> extension.bundle.js:314:18078
Object.onceWrapper events.js:291:20
IncomingMessage.emit events.js:208:15
endReadableNT _stream_readable.js:1168:12
processTicksAndRejections task_queues.js:77:11

@preachermaan please add more detailed repro steps. This doesn't repro for us with just that tutorial. It could be something related to your subscription or even a temporary error that goes away if you try again

Fixed by creating the function app manually in the console first.
On Wed, Mar 11, 2020, 5:48 PM Eric Jizba<EMAIL_ADDRESS>wrote:

@preachermaan https://github.com/preachermaan please add more detailed
repro steps. This doesn't repro for us with just that tutorial. It could be
something related to your subscription or even a temporary error that goes
away if you try again
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode-azurefunctions/issues/1965#issuecomment-597775918,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFIKCQN76FF3JPVJIENBLGDRG7FHJANCNFSM4LE4QEOA
.


Remove RedisInsight AcceptEula API

We don't want to have a custom license or agreement on our nuget packages. And this API is not ergonomic, so let's not ship this public API until we can ensure this is the way we want to go forever.
Contributes to #5727
Microsoft Reviewers: Open in CodeFlow

/backport to release/9.0-rc1

FYI @Alirexaa

/apz run

/azp run


Fix 'Cannot read property 'create' of undefined'

This exception is being thrown when attempting to call the build() function of the adapter because it's taking in the model rather than the modelName attribute.

I've tried forking my own repo from this and implementing my fix but for whatever reason it just throws this error:
.../node_modules/factory-girl/src/index.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){import FactoryGirl from './FactoryGirl';

I don't have a clue why this would happen when I'm literally only changing six characters and rebuilding. I'm hoping that you can merge this fix in soon so I can use this library.


Workplan Page - List all tasks/milestones under a phase

As a user
I want to see all legislated milestones
so that I can plan what tasks to add to reach those milestones
Acceptance Criteria
Scenario 1:
GIVEN I am in a workplan page
WHEN I open any phase accordion
THEN I see a grid view of all the legislated milestones with following titles:

Task/Milestone
type
start date
end date
days
assigned
responsibility
notes
progress

Scenario 2:
GIVEN I am in a workplan page
WHEN I open any phase accordion
THEN I see a checkbox to the left of search/filters
SO THAT I can do multiselect actions on non-milestone events
Validation Rules?
(If yes, list here)
Screenshot
(Link above will always be the most up-to-date version.)

Link to the design library
https://www.figma.com/file/8mmxxkkj2jGsBZLNA2dbn9/Design-System?type=design&node-id=1163-2228&mode=design
https://www.figma.com/file/8mmxxkkj2jGsBZLNA2dbn9/Design-System?type=design&node-id=1174-2337&mode=design


Cannot Rename Items In File System

Godot version
v4.1.dev3.official [a67d37f7c]
System information
Windows 10 64-bit
Issue description
When trying to rename anything (a scene, script, folder, etc) instead of selecting the item itself, it highlights the current folder in the FileSystem tab instead.
Upon pressing enter or confirm the name change a Warning dialogue appears with the following text:

This file extension is not recognized by the editor.
If you want to rename it anyway, use your operating system's file manager.
After renaming to an unknown extension, the file won't be shown in the editor anymore.

If no new text is entered, the warning box instead states

Name contains invalid characters.

Upon pressing Ok, the folder name in the FileSystem tab is visually changed to match the name of the item you attempted to rename (regardless of the entered text) including the extension if any. The folder name remains the same in the file system, but visually in the editor it is the name of the item.
In the output log, there is a message

scene/main/viewport.cpp:3005 - Condition "!is_inside_tree()" is true.

Steps to reproduce

Create or open a project
Rename any item (scene, script, folder, etc) by right clicking or pressing F2 (or corresponding shortcut for rename)

Minimal reproduction project
N/A

It didn't occur to me to test this on other things instead of just scenes when I created the issue. The original issue was specifically about being unable to rename scenes. I have edited the issue and title accordingly since the bug appears to affect everything else in the file system.

You CAN rename scenes. The warning appears, because it tries to use the name you provided for the wrongly selected folder. Once you accept, it will rename the file you wanted to rename, not the edited folder.
The bug here is that the wrong file is being edited when renaming.

You CAN rename scenes.
Once you accept, it will rename the file you wanted to rename, not the edited folder.

Can you elaborate? I am unable to rename scenes at all. When I go to windows file explorer, the file has the same name. When I restart the editor, the file still has the same name.
I can only rename things if I disable split mode (which I had forgotten to mention in the issue but is mentioned in the pull request)


Fix: Clippy warnings

Codecov Report

Merging #8 (152a78f) into main (3e35632) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@           Coverage Diff            @@
##            main      #8      +/-   ##
========================================
- Coverage   2.19%   2.18%   -0.02%
========================================
  Files          8       8
  Lines        182     183       +1
========================================
  Hits           4       4
- Misses       178     179       +1

Impacted Files
Coverage Δ

src/bar.rs
0.00% <0.00%> (ø)

src/colorizer.rs
0.00% <0.00%> (ø)

src/filesystem.rs
0.00% <0.00%> (ø)

src/stats.rs
0.00% <0.00%> (ø)

src/writer.rs
6.89% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Touchup tracing output.

This adds some tracing output to the syncer code, and fixes the Connection state machine to correctly propagate tracing spans.

Rebased to squash the fixup commits and keep a clean history.


Fix sky ViewportTexture path

I have problem instancing this environment into my scene, so this change picks absolute path regardless where's addon located
On a side note, I don't know where this comes from, which gives error on fresh install
	EnvironmentBlender.register_main_env(self)

Seems to work OK


Remove watchOptions prop

And just always watch options instead.

The API is unintuitive, and unnecessary. Users can just create a non-reactive options object by themselves.
This prop also almost doubles the size of the package (if we don't count perfect-scrollbar itself

Hi, thank you for proposition. I'm wondering what gives you reactive options when you have to reinitialize perfect scrollbar instance again ? PS instance is not reactive itself, so I have to destroy and create new one. What do you think ?

I'm wondering what gives you reactive options when you have to reinitialize perfect scrollbar instance again ?

Sorry, could you rephrase?

Ok never mind, I did not understand you the first time -)  So you want it to watch options by default ?

Yes.

I will take into account, because it will be breaking change


Make constants final

Currently there are constants used in autotune which are not final and they can be changed at any part of the code which may lead into problems as the defaults or fixed attributes are changed. All the constants added should be marked final

@dinogun Closing this issue as #504 is merged


update the news feed with the latest online news

Thank you Adam!
This is no going to be necessary. At the moment, since im using gh-pages, I cannot read the XML in the server, but once we deploy on the server we wont be reading the static XML but the one generated by wordpress :+1:

@cyntss I understand that, but it is still nice to have the latest news in the gh-pages mockup, so we can see how it will really look when you switch to the dynamic XML feed.  So please can you merge anyway?


Readme invalid link

the link provided for live data link for google is not  view only link or shareable. pleas update it if possible

that should be read-only to the public tho right?
There is form where users can submit cases -->  https://forms.gle/7NRSrbspW2a6pbm58

I asking for the dataset read access so it can be used other dashboard developments not using programming like react js . I am asking read access(view only not edit) for using in powerbi and tableau dashboard and i havent found any reliable datasource anywhere else

moreover it was given as public dataset to used to anything else at https://www.mohfw.gov.in/ in resources section

It was written as dataset source at

It's was written as dataset source at https://innovate.mygov.in/covid19/
That why's I was asking for read access

Not a bug


Change recipe overrides to check if endergetic/campful is installed

Right now it causes a bit of spam in the error log, was able to circumvent it by just replacing the recipes. But it would be a nice QoL for it to check if the mods are loaded before changing recipes that... well aren't there.

I would like to add this, but couldn't find a way for now. I will put it on a TO-DO list, but for now the manual deleting is the only way.


Remove votes props from plugins

Closes: https://github.com/snapshot-labs/snapshot/issues/3624
Changes

removed votes ref from SpaceProposalPage
removed unused votes props from plugins

How to test

make sure all plugins works good

@j0hnfl0w we use "Fixes" not "Closes" to close issues automatically

ah in sx-ui we use closes

Okay, "FIxes" should show as default when you open a new PR


If the NavigationView's SelectedItem is set after having set the ItemsSource the NavigationViewItem is not selected.

Describe the bug
When setting the SelectedItem of a NavigationView after having set the ItemsSource, the NavigationViewItem which has to be selected doesn't select.
Steps to reproduce the bug
1 - Open the attached sample and compile it.
2 - Execute the NavigationViewSelectionDisappears.Windows project as Package.
3 - You'll see that the NavigationViewItem is not selected.
Expected behavior
The NavigationViewItem has to be selected.
Screenshots
No response
NuGet package version
None
Windows version
No response
Additional context

NavigationViewItemIsSelectedValue.zip

IMO, you should provide a minimal repro sample rather than a large market-platform project with many extraneous references.
~I couldn't run it unless I installed things I'd prefer not to.

I attach the solution with the Windows target framework only.
NavigationViewItemIsSelectedValueWindowsOnly.zip

This is not a minimal repro:
    <PackageReference Include="Uno.Resizetizer" Version="1.2.1" />
    <PackageReference Include="Uno.WinUI" Version="5.0.48" />
    <PackageReference Include="Microsoft.WindowsAppSDK" Version="1.4.231008000" />
    <PackageReference Include="Microsoft.Windows.SDK.BuildTools" Version="10.0.22621.756" />
    <PackageReference Include="CommunityToolkit.Mvvm" Version="8.2.1" />
    <PackageReference Include="Uno.Material.WinUI" Version="4.0.6" />
    <PackageReference Include="Microsoft.Extensions.Logging.Console" Version="7.0.0" />
    <PackageReference Include="Uno.Core.Extensions.Logging.Singleton" Version="4.0.1" />
    <PackageReference Include="Uno.UI.Adapter.Microsoft.Extensions.Logging" Version="5.0.48" />
    <PackageReference Include ="Prism.Core" Version="8.1.97"/>

This is a minimal repro from making a new app from the standard template and copying over bits of your code:
https://github.com/kmgallahan/NavSelectedItemSample
and it shows the NavigationView working as expected.
You should start eliminating or adding dependencies and complications in a test project until you find what is causing your problem.

Thanks for reporting this @Suriman, and thanks @kmgallahan for investigating. I'm closing this for now since it seems to be an external issue. Please reopen if you've identified the problem to be something on WinUI 3.


Owner or admin access can be easily gained

If someone knows the nick of the owner, then that person can easily /nick Foobar to change his/her nick to the owner's nick. Then the person has full access to the bot for 60 seconds (until automatic kick by server) and can promote their own account in that time period.

Currently, a proposed fix has been pushed to rights_checks branch. As these are pretty extensive changes, they are on hold until approval or any other comments from the project leader.


Progress displayed wrong of no packaged checked for downloading

If you do not check any packages but still click the "Install checked" button the progress window claims that 0 of 2 packages are installed. The 2 seems a bit odd there... ;-)
...other than that: that tool's a good idea!

Oops!  The "0 of 2" is what is set at design-time; in the case of no packages selected, the form is never updated because it finishes before it starts!  Thanks for pointing this out--it'll be fixed in the next commit.


FAQ: How does search work - does not mention search by IDs

In http://beta.pathwaycommons.org/pathways/#/faq, "How does search work" should probably begin with (item 0) about what if a user query/phrase contains a valid identifier (- then, a.f.a.i.k, only ID(s) is used to query in 'xrefid' index field, and all other words in the input are ignored)

I think we briefly talked about this: There was no prefixing with  xrefid when I picked up the app.

It's not about prefixing at all. It's about auto-detecting IDs in a query phrase first and then internally forcing search in xrefid. Remember? It works that way right now, no? It should.

On May 31, 2017, at 3:09 PM, Jeffrey<EMAIL_ADDRESS>wrote:
I think we briefly talked about this: There was no prefixing with xrefid when I picked up the app.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

What's the operational difference between prefixing with xrefid and internally forcing search in xrefid?

Well, you're right that there was no use of 'xrefid:' prefix since we've designed with Manfred (he found a workaround).  And, more important, everything seems to work very well, and it's hard to prove otherwise (partially due to a side effect of PathwayCommons/cpath2-client#3 bug)...
FYI (optional but interesting reading).
Initially, the whole idea of detecting IDs from user's input was to use 'xrefid:' search internally or at least to query those words without using any prefix or order. Now I see that much of code has changed since after Manfred's done, and after we first added wildcards (*) there.
But, my point is that all words (user query tokens) must participate in a search query and have a chance to match. Currently we allow only auto-detected IDs (8 types, and where the 'hgnc' pattern captures almost everything) to match without any field name prefix, while all other words are prefixed with 'name:' (wrapped as 'name:" + "" + word + ""' always), and entire input phrase is prefixed with 'name:' as well. I think, we should simply add one more sub-query like "(" + escapeSpaces( words ) + ") OR (" in addition to what's already there (note: here I am suggesting 'words' - original tokens - array, not 'result', to be used, and - no 'name:' prefix).
Finally (having suggested sub-query), we do not have to detect bio IDs with regexp (it does not improve the search).
For example, one can find Reactome "Meiotic recombination" using not only Q06609 or RAD51 or NP_002866, but also - gene ID: 5888 - via PC API:
http://beta.pathwaycommons.org/pc2/search?type=pathway&datasource=reactome&q=5888
http://beta.pathwaycommons.org/pc2/search?type=pathway&datasource=reactome&q=xrefid:5888
If not this issue, pathways-search would not probably find that pathway using the gene ID 5888:
http://beta.pathwaycommons.org/pathways/#/search?datasource=Reactome&gt=3&lt=250&q=5888&type=Pathway (magically works thanks to bugs...)

For aeaa631c6df189f432d5113c08a7228979a57e8c:

Added refseq to checkList of identifiers it would compare tokens against
Refactored if statements to be more explicit about each stage (failureCount)

Theres a looootttttt of room to improve ( #75 #82 ) but it kinda works OK for now.
If I search Jeffrey Wong:
Inhibition of Signaling by Overexpressed EGFR
Reactome
15 Participants


Prepare for release 0.3.0

🎉 New feature
Prepare for release 0.3.0
Summary
Depends on:

#279
https://github.com/maliput/maliput/pull/630 and the posterior bazel release.

Test it
N/A
Checklist

[x] Signed all commits for DCO
[ ] Added tests
[ ] Added example and/or tutorial
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if it affects the public API)

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

TSAN Errors point to drake's code.


Update dependency docker.io/rook/ceph to v1.9.4

This PR contains the following updates:

Package
Update
Change

docker.io/rook/ceph
minor
v1.8.9 -> v1.9.4

Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

Old alerts

[] SYN_CephClusterCriticallyFull	Storage cluster utilization has crossed 80% and will become read-only at 85%. Free up some space or expand the storage cluster immediately.
[] SYN_CephClusterErrorState	Storage cluster is in error state for more than 10m.
[] SYN_CephClusterNearFull	Storage cluster utilization has crossed 75% and will become read-only at 85%. Free up some space or expand the storage cluster.
[] SYN_CephClusterReadOnly	Storage cluster utilization has crossed 85% and will become read-only now. Free up some space or expand the storage cluster immediately.
[] SYN_CephClusterWarningState	Storage cluster is in warning state for more than 15m.
[] SYN_CephDataRecoveryTakingTooLong	Data recovery has been active for too long. Contact Support.
[] SYN_CephMdsMissingReplicas	Minimum required replicas for storage metadata service not available. Might affect the working of storage cluster.
[] SYN_CephMgrIsAbsent	Ceph Manager has disappeared from Prometheus target discovery.
[] SYN_CephMonHighNumberOfLeaderChanges	Ceph Monitor {{ $labels.ceph_daemon }} on host {{ $labels.hostname }} has seen {{ $value | printf "%.2f" }} leader changes per minute recently.
[] SYN_CephMonQuorumAtRisk	Storage cluster quorum is low. Contact Support.
[] SYN_CephMonQuorumLost	Storage cluster quorum is lost. Contact Support.
[] SYN_CephMonVersionMismatch	There are {{ $value }} different versions of Ceph Mon components running.
[] SYN_CephOSDCriticallyFull	Utilization of storage device {{ $labels.ceph_daemon }} of device_class type {{$labels.device_class}} has crossed 80% on host {{ $labels.hostname }}. Immediately free up some space or add capacity of type {{$labels.device_class}}.
[] SYN_CephOSDDiskNotResponding	Disk device {{ $labels.device }} not responding, on host {{ $labels.host }}.
[] SYN_CephOSDDiskUnavailable	Disk device {{ $labels.device }} not accessible on host {{ $labels.host }}.
[] SYN_CephOSDFlapping	Storage daemon {{ $labels.ceph_daemon }} has restarted 5 times in last 5 minutes. Please check the pod events or ceph status to find out the cause.
[] SYN_CephOSDNearFull	Utilization of storage device {{ $labels.ceph_daemon }} of device_class type {{$labels.device_class}} has crossed 75% on host {{ $labels.hostname }}. Immediately free up some space or add capacity of type {{$labels.device_class}}.
[] SYN_CephOSDSlowOps	{{ $value }} Ceph OSD requests are taking too long to process. Please check ceph status to find out the cause.
[] SYN_CephOSDVersionMismatch	There are {{ $value }} different versions of Ceph OSD components running.
[] SYN_CephPGRepairTakingTooLong	Self heal operations taking too long. Contact Support.
[] SYN_RookCephOperatorScaledDown	TODO

New alerts

[] SYN_CephDaemonCrash	One or more Ceph daemons have crashed, and are pending acknowledgement
[] SYN_CephDeviceFailurePredicted	Device(s) have been predicted to fail soon
[] SYN_CephDeviceFailurePredictionTooHigh	Too many devices have been predicted to fail, unable to resolve
[] SYN_CephDeviceFailureRelocationIncomplete	A device failure is predicted, but unable to relocate data
[] SYN_CephFilesystemDamaged	Ceph filesystem is damaged.
[] SYN_CephFilesystemDegraded	Ceph filesystem is degraded
[] SYN_CephFilesystemFailureNoStandby	Ceph MDS daemon failed, no further standby available
[] SYN_CephFilesystemInsufficientStandby	Ceph filesystem standby daemons too low
[] SYN_CephFilesystemMDSRanksLow	Ceph MDS daemon count is lower than configured
[] SYN_CephFilesystemOffline	Ceph filesystem is offline
[] SYN_CephFilesystemReadOnly	Ceph filesystem in read only mode, due to write error(s)
[] SYN_CephHealthError	Cluster is in an ERROR state
[] SYN_CephHealthWarning	Cluster is in a WARNING state
[] SYN_CephMgrModuleCrash	A mgr module has recently crashed
[] SYN_CephMgrPrometheusModuleInactive	Ceph's mgr/prometheus module is not available
[] SYN_CephMonClockSkew	Clock skew across the Monitor hosts detected
[] SYN_CephMonDiskspaceCritical	Disk space on at least one monitor is critically low
[] SYN_CephMonDiskspaceLow	Disk space on at least one monitor is approaching full
[] SYN_CephMonDown	One of more ceph monitors are down
[] SYN_CephMonDownQuorumAtRisk	Monitor quorum is at risk
[] SYN_CephNodeDiskspaceWarning	Host filesystem freespace is getting low
[] SYN_CephNodeInconsistentMTU	MTU settings across Ceph hosts are inconsistent
[] SYN_CephNodeNetworkPacketDrops	One or more Nics is seeing packet drops
[] SYN_CephNodeNetworkPacketErrors	One or more Nics is seeing packet errors
[] SYN_CephNodeRootFilesystemFull	Root filesystem is dangerously full
[] SYN_CephObjectMissing	Object(s) has been marked UNFOUND
[] SYN_CephOSDBackfillFull	OSD(s) too full for backfill operations
[] SYN_CephOSDDown	An OSD has been marked down/unavailable
[] SYN_CephOSDDownHigh	More than 10% of OSDs are down
[] SYN_CephOSDFlapping	Network issues are causing OSD's to flap (mark each other out)
[] SYN_CephOSDFull	OSD(s) is full, writes blocked
[] SYN_CephOSDHostDown	An OSD host is offline
[] SYN_CephOSDInternalDiskSizeMismatch	OSD size inconsistency error
[] SYN_CephOSDNearFull	OSD(s) running low on free space (NEARFULL)
[] SYN_CephOSDReadErrors	Device read errors detected
[] SYN_CephOSDTimeoutsClusterNetwork	Network issues delaying OSD heartbeats (cluster network)
[] SYN_CephOSDTimeoutsPublicNetwork	Network issues delaying OSD heartbeats (public network)
[] SYN_CephOSDTooManyRepairs	OSD has hit a high number of read errors
[] SYN_CephPGBackfillAtRisk	Backfill operations are blocked, due to lack of freespace
[] SYN_CephPGImbalance	PG allocations are not balanced across devices
[] SYN_CephPGNotDeepScrubbed	Placement group(s) have not been deep scrubbed
[] SYN_CephPGNotScrubbed	Placement group(s) have not been scrubbed
[] SYN_CephPGRecoveryAtRisk	OSDs are too full for automatic recovery
[] SYN_CephPGsDamaged	Placement group damaged, manual intervention needed
[] SYN_CephPGsHighPerOSD	Placement groups per OSD is too high
[] SYN_CephPGsInactive	One or more Placement Groups are inactive
[] SYN_CephPGsUnclean	One or more platcment groups are marked unclean
[] SYN_CephPGUnavilableBlockingIO	Placement group is unavailable, blocking some I/O
[] SYN_CephPoolBackfillFull	Freespace in a pool is too low for recovery/rebalance
[] SYN_CephPoolFull	Pool is full - writes are blocked
[] SYN_CephPoolNearFull	One or more Ceph pools are getting full
[] SYN_CephSlowOps	MON/OSD operations are slow to complete
[] SYN_RookCephOperatorScaledDown	rook-ceph operator scaled to 0 for more than 1 hour.


fix issue #677

Hi,
I've encountered this error several times when developing an expo application. I used the create-t3-turbo boilerplate as a starting boilerplate and made some modifications to it, but not enough to break nativewind.

This breaks all functionality around specificity

This breaks all functionality around specificity

Oh yes sorry, as I'm a novice, I had a hard time testing my fix to see if it was any good! But it should be good!


wont install in any way i try

i tried uninstalling bbd, reinstalling bbd, repairing bbd, using it in a different folder, running as administrator, installing on canary, reinstalling discord, literally everything you can think of and it just wont install

BBD installs for me, but won't complete loading. The installer didn't bring up any errors that caught my eye. I'm not particularly sure if this was the right area for me to check for errors in the console, but here's the errors I got.

sorry im late heres the installer log:
Downloading BandagedBD package
Using channel: https://github.com/rauenzi/BetterDiscordApp/archive/injector.zip
Downloading to: C:\ProgramData\Flashlight Bulbton\Discord\app-0.0.300\\resources\BetterDiscord.zip
Finished downloading BandagedBD package
Deleting old BetterDiscord
Extracting BandagedBD package
Renaming package dir
Deleting temp file C:\ProgramData\Flashlight Bulbton\Discord\app-0.0.300\\resources\BetterDiscord.zip
Verifying installation
Checking for old style injection
Checking for old injection C:\Users\Flashlight Bulbton\AppData\Roaming\discord\0.0.305\
Verifying C:\ProgramData\Flashlight Bulbton\Discord\app-0.0.300\\resources\app\index.js
Verifying C:\ProgramData\Flashlight Bulbton\Discord\app-0.0.300\\resources\app\config.json
Verifying C:\ProgramData\Flashlight Bulbton\Discord\app-0.0.300\\resources\app\package.json
Verifying C:\ProgramData\Flashlight Bulbton\Discord\app-0.0.300\\resources\app\betterdiscord\index.js
Verifying C:\ProgramData\Flashlight Bulbton\Discord\app-0.0.300\\resources\app\betterdiscord\config.json
Verifying C:\ProgramData\Flashlight Bulbton\Discord\app-0.0.300\\resources\app\betterdiscord\utils.js
Verification successful
Finished installing BandagedBD for Discord!
---------------------------------------------------------------------------------

it takes a split second and nothing happens do my actual client
the ctrl shift i seems to have nothing BD related

Fixed: I opened the discord directory from task manager and used that in the betterdiscord installer.


HS-FLS100-G2 v1.0 not identified

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
NO, my problem is NOT within Home Assistant or the ZWave JS integration
Is your problem within ZWaveJS2MQTT?
NO, my problem is NOT within ZWaveJS2MQTT
Checklist

[X] I have checked the troubleshooting section and my problem is not described there.

[X] I have read the changelog and my problem was not mentioned there.

Describe the bug
What causes the bug? Include v1.0 unit using the DSK QR code
What do you observe?
I have two units: one is a v1.1 and the other is v1.0. The v1.1 unit is included properly and appears in the control panel with the proper deviceID: 0x000c-0x0201-0x000c. The v1.0 unit shows up in the control panel with an unknown device ID: "hexId": "0xXXXX-0xXXXX-0xXXXX",
What did you expect to happen?
The v1.0 unit recognized with the proper device ID
Steps to reproduce the behavior:

settings->z-wavejs-> add device
enter q=QR coded scanned from the device
Restart HA
Both appear in the provisioned entity list
The v1.1 unit appears in the control panel with the correct deviceID
The v1.0 unit appears in the control panel as unknown
The switches and sensors work as expected for the v1.1 unit
The switches and sensors do not appear for the v1.0 unit

Device information
Manufacturer: HomeSeer
Model name: HS-FLS100-G2
Node ID in your network: 93
How are you using node-zwave-js?

[ ] zwavejs2mqtt Docker image (latest)
[ ] zwavejs2mqtt Docker image (dev)
[ ] zwavejs2mqtt Docker manually built (please specify branches)
[ ] ioBroker.zwave2 adapter (please specify version)
[X] HomeAssistant zwave_js integration  (please specify version)
[ ] pkg
[ ] node-red-contrib-zwave-js (please specify version, double click node to find out)
[ ] Manually built from GitHub (please specify branch)
[ ] Other (please describe)

Which branches or versions?
version:
node-zwave-js branch:
zwavejs2mqtt branch:
github haos_rpi4-64-8.5.img.xz running on an RPI4.
My z-wave radio is the Aeotec Z-Stick Gen5+
Z-Wave JS  10.0.3
Did you change anything?
no
If yes, what did you change?
No response
Did this work before?
No, it never worked anywhere
If yes, where did it work?
No response
Attach Driver Logfile
zwave_js(2).log

zwavejs_2022-09-03.log

Issue resolved or why did you close?

Thank you for the prompt! I'm new to the git hub bug tracker. In my haste to add the proper log file I pushed the wrong send button! The issue is still open. :)
I'm concerned that this last log will not be helpful because it shows a re-interview operation that completed successfully. The log shows some route failures during route discovery, but I did not see a sequence that reads the deviceID in this re-interview log. I fear that I may need to first exclude the device then capture the log through the include sequence. The exclude procedure requires that I have physical access to the node to press a button. There are three V1.0 units installed already and with all of the construction around the house they are difficult to get a ladder to. Of course, the v1.1 units have not been installed yet! They are working perfectly on my bench right now. Please have a look at the re-interview log to see it it is helpful. I may need to arrange to take one of the v1.0 units off the house and put it on the bench for easier access.

Unfortunately the interview log is truncated. You need to keep the log window open at all times while performing the re-interview. Please try again (I only need the non-working one).

Please re-test with v10.0.4. This version is included in:
zwave_js addon: 0.1.70
or
zwavejs2mqtt: 7.1.0

v10.0.4 is installed and has been there since the first test on 9/3.
A major change has occurred to node 93 since I last reported. The control panel shows node 93 with the correct device ID and the switches and sensors how show up for it in the control panel and appear to function properly.
Node 93 does not show up in the z-wave device list. settings->Devices & Services->Z-wave JS devices
Not sure what happened to stimulate this result. There were lots of probes and actions but it was not recognized before I gave up on 9/3.
This unit is acting strangely since it was recognized. The flood light turns on and off momentarily in the evening. It is annoying so right now it is turned off with the control panel.
Nodes 94 and 88 are not recognized and are the same device type and version number. The behavior of these is the same as previously reported for node 93. No controls appear in the node display in control panel and switches for them in the device list are inoperative (grey). A single switch appears for Nodes 94 and 88 in the overview dashboard  but these are grey too. (Node 93 does not appear in the dashboard)
The logs have been running since 9/3 and the entire set is in the attached zip file. I'm hoping that the recognition sequence for node 93 is present in the logs. The last action in the log for 9/8 is a re-interview sequence for node 94.
You may see in the logs that the Nodes 93, 94 & 88 are dead during the day. All three are attached to a z-wave wall switch with an automation to turn them on after dark. For the last test, I manually turned on the switch first and verified the device with a successful ping.
zwavejs2mqtt-store.zip

There's no interview at all in any of these logs. Did you have filters configured for the logging? If so, remove them.

I have not configured filters intentionally. How to I tell if any are active?
I can see the interview progress in the debug window.

Thank you for the information and patience. I've finally sorted out the logs and have captured the interview sequence in the log.
zwavejs2mqtt_2022-09-17.log
(My settings->general screen looks different than the user document link. It is now a devices value configuration list ... I think it changed after the last upgrade.)
The log is confirming what we already know:
2022-09-17 15:48:26.945 INFO ZWAVE: Node 94 ready: Unknown manufacturer 0xXXXX - Unknown product 0xXXXX (0xXXXX)
I'm wondering if this is an equipment failure? However this thought is muted somewhat because Node 93 has magically started to work on its own. (Node 94 & 88 are the other v1.0 firmware devices and are both reporting unknown manufacturer.)
Are the strings presented in the log "0xXXXX" what the equipment is returning or is it a log replacement pattern for unknown values?
I'm wondering if I should take this question to HomeSeer support but with the values that are returned from the equipment.

You're looking at the wrong logfile. Note how my link goes to "Driver logs" not "Application logs".

I'm now just getting back to home base and can work on this issue.
I think I have the driver log.
zwavejs_2022-09-28.log
The log should capture the interview for node 94

The driver thinks the node was included using S2 unauthenticated:
2022-09-29T01:56:23.419Z CNTRLR » [Node 094] Querying securely supported commands (S2_Unauthenticated)...

but the node responds with an empty list of commands
2022-09-29T01:56:30.276Z DRIVER « [Node 094] [REQ] [ApplicationCommand]
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 206
                                    └─[Security2CCCommandsSupportedReport]
                                        supportedCCs:

which means it was included with S2_Authenticated or S2_AccessControl.
Make sure you have those keys configured and if you do, re-interview the node again, this time enable the checkbox "reset security classes" in the re-interview dialog. This will cause the driver to query all S2 keys instead of just one.
If that also doesn't help, then exclude, factory reset to delete all keys on the device, then include again.

I re-interviewed the faulty nodes and reset the security classes. Once complete the nodes are now recognized. Thank you for your help.

Thank you again for your support on this issue. :)
Considering the following comment in more detail:

The driver thinks the node was included using S2 unauthenticated

Is there a deeper trouble to investigate when a new device is added using a QR code?
All of the HS-FLS100-G2 devices were added using: settings->devices & services->z-wave js devices->+add device
In each case, the QR code scanned from the device was entered. No other information was requested or entered. The script just added the device with the S2 unauthenticated result. Other than the "unrecognized manufacturer response" there was no indication that an invalid security class was automatically chosen.
Recovery required "reset security classes" from the control panel device interview advanced setting. The second pass appears to have selected the proper security class and the device is now properly recognized and operating normally.
Is there a problem with the initial add device function that somehow did not apply the correct security class as the device was added in the first place?
Additional information about the initial device add:

Two devices with v1.1 firmware were properly recognized with their QR code on the first try and operate properly
Three devices with v1.0 all failed with similar results described above requiring a reset security class action to recover.
All devices now have a green check in the control panel security column. I did not record this status indication when the invalid S2 status was standing.

Is there a problem with the initial add device function that somehow did not apply the correct security class as the device was added in the first place?

Can't tell without driver logs of the inclusion process.


The main example doesn't work

Doing everything using documentation I have this error:
Ξ ~/evscript git:(master) ▶ evscript -f ev.dyon -d /dev/input/event19
--- ERROR ---
In ev.dyon:
Type mismatch (#200):
Expected [], found {}
9,19:         for i len(evts) {
9,19:                   ^

I had the same problem. You can fix it by changing for i len(evts) { ... } to for i { ... } as explained in Inferring range by indexing . I know it looks
weird to write a for loop without declaring the range to iterate over. It
seems that Dyon can see that i is used as an index into evts, and
infers that it should iterate over every index of evts.
On Sat, Feb 22, 2020, 12:12 paranormal<EMAIL_ADDRESS>wrote:

Doing everything using documentation I have this error:
Ξ ~/evscript git:(master) ▶ evscript -f ev.dyon -d /dev/input/event19
--- ERROR ---
In ev.dyon:
Type mismatch (#200):
Expected [], found {}
9,19: for i len(evts) {
9,19: ^
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/myfreeweb/evscript/issues/9?email_source=notifications&email_token=AAACLFUQIJIBNDSE3KADPXTREFMGFA5CNFSM4KZTBOX2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IPPZQAQ,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAACLFW4SUVI5WUXXGSTL4LREFMGFANCNFSM4KZTBOXQ
.

It works. Thank you.
Unfortunately I can't figure out if it is possible to remap . I need my ENTER to work as RIGHTCTRL when hold, and as ENTER when just pressed.
xcape(mut should_enter, evt, KEY_ENTER(), [KEY_RIGHTCTRL()]) doesn't do the trick

@paranormal I think you need to do it the other way around: remap your enter key to be right control (using xkb or some other means), and configure it to send enter on tap:
xcape(mut should_enter, evt, KEY_RIGHTCTRL(), [KEY_ENTER()])

Thank you for the tip. Just as I did with the xcape.
However

@paranormal I think you need to do it the other way around: remap your enter key to be right control (using xkb or some other means), and configure it to send enter on tap:
xcape(mut should_enter, evt, KEY_RIGHTCTRL(), [KEY_ENTER()])

Thank you for the tip. This is how it worked with an xcape.
But it doesn't work the same with evscript. Somehow when run evscript, it restores the old RETURN map and on press it acts as RETURN, when ^C the evscript: the RETURN behaviour is preserved and acts as RETURN.
xmodmap -e "keycode 0x24 = Control_R"
xmodmap -e "add Control = Control_R"

fn main() ~ evdevs, uinput {
    should_enter := false
    loop {
        evts := next_events(evdevs)
        for i {
            evt := evts[i]
            xcape(mut should_enter, evt, KEY_RIGHTCTRL(), [KEY_ENTER()])
        }
    }
}

It feels like evscript restores ENTER and it stops acting like CTRL, even after evscript is stopped remap no longer works, ENTER is an ENTER again.

@paranormal are you still trying all that under xorg? you're not trying to xmodmap under wayland?

@myfreeweb yes, I experimented under xorg, xcape is what I currently using and the reason I couldn't switch to sway.
Shall running the same recipe with remap and evscript work differently under wayland?

I'll try, thank you.

@paranormal are you still trying all that under xorg? you're not trying to xmodmap under wayland?

I've just tried it under sway, it doesn't remap ENTER back. But it doesn't work either.

In /usr/share/X11/xkb/keycodes/evdev I changed RTRN to RCTRL after that my enter started working as CTRL. running evscript -f ev.dyon -d /dev/input/event19 where my HHKB sets changes nothing.

    should_enter := false
    loop {
        evts := next_events(evdevs)
        for i {
            evt := evts[i]
            xcape(mut should_enter, evt, KEY_RIGHTCTRL(), [KEY_ENTER()])
        }
    }
}

Just rechecked everything again. Things from the main example works, it prints numbers on pressed shift keys. Enter key doesn't work at all, it behaves as a control.

Just rechecked everything again. Things from the main example works, it prints numbers on pressed shift keys. Enter key doesn't work at all, it behaves as a control.
Just did another test with default /usr/share/X11/xkb/keycodes/evdev and trying to map LCTL to ENTER. Doesn't work, all other keys works, ENTER doesn't ((

@paranormal I think what's happening is.. you remapped enter to something in xkb keycodes, and evscript is pressing enter again - it's getting the same remapping :D
I guess you could instead have evscript press something else that would be equivalent (numpad enter) or remapped differently (via xkb options in the compositor)??

@myfreeweb I excluded this possibility. I returned everything back (default xkb keycodes) and applied the scenario to LCTL, it didn't triggered ENTER.
To reproduce this you just need this (don't do any remapings):
xcape(mut should_enter, evt, KEY_LEFTCTRL(), [KEY_ENTER()])

it doesn't work for me.

I've given it another shoot and found that I have to put //! keys = ['ESC', 'LEFTSHIFT', '9', '0'] in config, this wasn't mentioned in documentation.
After inserting line with //! keys = ['LEFTCTRL', 'RIGHTCTRL', 'ENTER'] it started working.


There is a typo mistake in (Configure dependencies for Android) section

Hello,
I found there is a typo mistake in (Configure dependencies for Android) section, while i going through the tutorial i found this problem.
https://docs.microsoft.com/en-us/graph/tutorials/react-native?tutorial-step=1
MIstake
defaultConfig {     manifestPlaceholders = [         appAuthRedirectScheme: 'graphtutorial'     ] }
Correction
defaultConfig {     manifestPlaceholders = [         appAuthRedirectScheme: 'graph-tutorial'     ] }
Please make the correction as soon as possible.
Thanks

Thanks for catching this.


Why no haiku support?

Why no haiku support? I need claude haiku for some quick data estraction (names, job title, address) from documents. Haiku is the only one not too expensive and fast enough for the job (can process hundreds of paragraphs per minute). Your pyaskit is ideal for integrating such quick text processing tasks in a python script. Being the model more convenient on the market, I expected it to be your first choice.

Thank you for your feedback on adding Haiku support to pyaskit. We're pleased to announce that we have updated pyaskit to include Haiku integration.
To help you get started, we've added the example/information_extraction.py script that demonstrates how to use Haiku with pyaskit for information extraction tasks. We encourage you to give it a try and let us know about your experience.
Your feedback is valuable to us as we continue to improve pyaskit. Please don't hesitate to share any further suggestions or report any issues you may encounter while using Haiku with pyaskit.
We appreciate your contribution and hope you find the Haiku support beneficial for your projects.

You solved it all, even adding examples! You are really amazing! Thank you!🙏 😲
I will do my best to give you some feedback!🫡
I truly believe in pyaskit potential!
AI integration in python needs to be as easy and pythonic as possible.
I also wanted to suggest you a decorator, but this is for later, now I need to test it out.😉