Schlage Connect BE469ZP varying in reported metadata between devices in z-wave network

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
YES, BUT a Home Assistant developer has told me to come here
Is your problem within ZWaveJS2MQTT?
YES, BUT a ZWaveJS2MQTT developer has told me to come here
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?
Re-interviewing the device
What do you observe?
Every re-interview gives me a varying amount of metadata from the lock. The original entities that were added when I first enrolled the device in May 2021 are no longer available, even after attempting to refresh the metadata within the device configuration in Z-Wave JS. Sometimes
What did you expect to happen?
I expect a full set of metadata to be populated in each entry including, but not limited to, battery level, intrusion status, and low battery indication
Steps to reproduce the behavior:

Re-interview the device
Metadata will sometimes populate correctly, most of the data entries are "undefined"

Other notes:

Lock/unlock status is not affected, nor is sending commands and the UI updates correctly when the lock status is changed both remotely and manually.
I've attempted to add a 2000ms timeout to the config but this actually seemed to make the problem more consistent.

Device information
Manufacturer: Schlage Connect
Model name: BE469ZP
Node ID in your network: 9, 10, and 11
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: 2022.8.4
node-zwave-js branch: 9.6.2
zwavejs2mqtt branch: 6.15.2
Did you change anything?
no
If yes, what did you change?
No response
Did this work before?
Yes (please describe)
If yes, where did it work?
Worked without issue when first installing, I do not have an exact timeframe of when it no longer worked, but I noticed the lovelace UI not updating with lock status and the remote commands not working in August 2022. Re-interviewing the devices fixed those issues, but presented with missing metadata afterwards.
Attach Driver Logfile
zwavejs2mqtt_2022-08-15.log

[zwavejs_2022-08-15.log](https://github.com/zwave
zwavejs2mqtt_2022-08-15.log
-js/node-zwave-js/files/9338445/zwavejs_2022-08-15.log)
Uploaded correct files

This looks suspiciously like the other issue you commented in, at least to some degree. Node 9 has 27 timeouts during the interview alone. I don't know if you tried to up the response timeout but if you did, it didn't take.
What bothers me a bit is that the lock almost instantly requests a nonce which it needs to send an encrypted response, but the actual response never comes, not even delayed. When it does respond, the response comes within 100-200ms.
This could just be a connectivity issue, since the round-trip-times are fluctuating quite a bit.
Just to be sure: did you follow this guide?
Normally I'd recommend checking the network health but it doesn't seem like your controller supports reporting this information, so that won't be a lot of help.

I did try adding the timeout, but I didn't try upping it, I'll try maybe 5000 or 10000. Just to be sure, in my settings.json, I currently have this:
{"port":"/dev/ttyACM0","commandsTimeout":30,"logLevel":"info","logEnabled":true,"securityKeys":
I would then change it to the following:
{"port":"/dev/ttyACM0","options":{"timeouts":{"report":5000}},"commandsTimeout":30,"logLevel":"info","logEnabled":true,"securityKeys":
I would hesitate to put the blame on connectivity issues since my house is relatively small, and I've had no issues with the locks for the better part of a year. Like I said, I'm not exactly sure when the issue started, but IIRC there was some major change to Z-WaveJS a few months ago that maybe was when I started having issues? Not 100% sure.
Just to make sure, I did replace batteries in all locks.

I did change the default report timeout from 10000 ms to 1000 ms a while ago, to be in line with what the specs recommend. So far the only devices I've seen have issues with this are the Schlage locks, and they have contributed some straaange issues over the years.
Anyways, if you switch back to 10000ms, you should have exactly the same behavior as previously. If there are still timeouts, then it is not the driver change.

I had a similar issue with this lock (2 of them actually), and solved it by temporarily increasing the timeout to 10,000ms during the interview. I still had one time out during the interview, I think, but I think it was for a value of a config parameter, or something else that I could easily query after the interview finished. As best as I can tell, the lock sometimes just gets cranky and takes 5 seconds to respond, or decides not to respond at all.

Well, unless I'm not actually changing the timeout report to 10000 properly, that's still not solving my issues. The lock/unlock does work, but like I said, not much to no metadata is coming through during the interview process.

Well, unless I'm not actually changing the timeout report to 10000 properly, that's still not solving my issues. The lock/unlock does work, but like I said, not much to no metadata is coming through during the interview process.

I have a copy of the config that worked for me (minus security keys) here: https://github.com/zwave-js/node-zwave-js/issues/4746#issuecomment-1167360075

I'm seeing re-interviews of BE469ZPs fail to complete more often than not, even with the timeout bumped up. Here are 5 (out of 5) attempts failing with unsupported command errors, despite having the re-interview just prior to these 5 complete successfully.

does not support the command SupportedGet
2022-09-06T18:43:49.159Z DRIVER « [Node 093] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -68 dBm
                                  └─[SecurityCCCommandEncapsulation]
                                    │ sequenced: false
                                    └─[FirmwareUpdateMetaDataCCMetaDataReport]
                                        manufacturer id:         59
                                        firmware id:             18064
                                        checksum:                0
                                        firmware upgradable:     true
                                        max fragment size:       20
                                        additional firmware IDs: [18065]
                                        hardware version:        undefined
                                        continues to function:   unknown
                                        supports activation:     unknown
2022-09-06T18:43:49.164Z CNTRLR « [Node 093] Received firmware update capabilities:
                                    firmware targets:      0, 18065
                                    continues to function: unknown
                                    supports activation:   unknown
2022-09-06T18:43:49.165Z CNTRLR   [Node 093] [+] [Firmware Update Meta Data] interviewCo [Endpoint 0] [internal]
                                  mplete: true
2022-09-06T18:43:49.166Z CNTRLR   [Node 093] Root device interview: Device Reset Locally
2022-09-06T18:43:49.167Z CNTRLR   [Node 093] Root device interview: Powerlevel
2022-09-06T18:43:49.167Z CNTRLR   [Node 093] Root device interview: Indicator
2022-09-06T18:43:49.169Z CNTRLR   [Node 093] Interviewing Indicator...
2022-09-06T18:43:49.170Z CNTRLR » [Node 093] scanning supported indicator IDs...
2022-09-06T18:43:49.175Z CNTRLR   [Node 093] Error during node interview: Node #93 does not support the command
                                  SupportedGet! (ZW0302)

does not support the command HealthGet
2022-09-06T18:48:37.413Z DRIVER « [Node 093] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -67 dBm
                                  └─[SecurityCCCommandEncapsulation]
                                    │ sequenced: false
                                    └─[BatteryCCReport]
                                        level:  97
                                        is low: false
2022-09-06T18:48:37.418Z CNTRLR « [Node 093] received response for battery information:
                                  level:                           97
                                  status:                          undefined
                                  rechargeable:                    undefined
                                  is backup:                       undefined
                                  is overheating:                  undefined
                                  fluid is low:                    undefined
                                  needs to be replaced or charged: undefined
                                  is low temperature               undefined
                                  is disconnected:                 undefined
2022-09-06T18:48:37.419Z CNTRLR » [Node 093] querying battery health...
2022-09-06T18:48:37.422Z CNTRLR   [Node 093] Error during node interview: Node #93 does not support the command
                                  HealthGet! (ZW0302)

does not support the command SupportedGet

2022-09-06T18:52:11.895Z DRIVER « [Node 093] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -68 dBm
                                  └─[SecurityCCCommandEncapsulation]
                                    │ sequenced: false
                                    └─[FirmwareUpdateMetaDataCCMetaDataReport]
                                        manufacturer id:         59
                                        firmware id:             18064
                                        checksum:                0
                                        firmware upgradable:     true
                                        max fragment size:       20
                                        additional firmware IDs: [18065]
                                        hardware version:        undefined
                                        continues to function:   unknown
                                        supports activation:     unknown
2022-09-06T18:52:11.897Z CNTRLR « [Node 093] Received firmware update capabilities:
                                    firmware targets:      0, 18065
                                    continues to function: unknown
                                    supports activation:   unknown
2022-09-06T18:52:11.898Z CNTRLR   [Node 093] [+] [Firmware Update Meta Data] interviewCo [Endpoint 0] [internal]
                                  mplete: true
2022-09-06T18:52:11.898Z CNTRLR   [Node 093] Root device interview: Device Reset Locally
2022-09-06T18:52:11.899Z CNTRLR   [Node 093] Root device interview: Powerlevel
2022-09-06T18:52:11.899Z CNTRLR   [Node 093] Root device interview: Indicator
2022-09-06T18:52:11.901Z CNTRLR   [Node 093] Interviewing Indicator...
2022-09-06T18:52:11.901Z CNTRLR » [Node 093] scanning supported indicator IDs...
2022-09-06T18:52:11.906Z CNTRLR   [Node 093] Error during node interview: Node #93 does not support the command
                                  SupportedGet! (ZW0302)

does not support the command SupportedGet
2022-09-06T18:54:34.591Z DRIVER « [Node 093] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -68 dBm
                                  └─[SecurityCCCommandEncapsulation]
                                    │ sequenced: false
                                    └─[FirmwareUpdateMetaDataCCMetaDataReport]
                                        manufacturer id:         59
                                        firmware id:             18064
                                        checksum:                0
                                        firmware upgradable:     true
                                        max fragment size:       20
                                        additional firmware IDs: [18065]
                                        hardware version:        undefined
                                        continues to function:   unknown
                                        supports activation:     unknown
2022-09-06T18:54:34.596Z CNTRLR « [Node 093] Received firmware update capabilities:
                                    firmware targets:      0, 18065
                                    continues to function: unknown
                                    supports activation:   unknown
2022-09-06T18:54:34.597Z CNTRLR   [Node 093] [+] [Firmware Update Meta Data] interviewCo [Endpoint 0] [internal]
                                  mplete: true
2022-09-06T18:54:34.598Z CNTRLR   [Node 093] Root device interview: Device Reset Locally
2022-09-06T18:54:34.598Z CNTRLR   [Node 093] Root device interview: Powerlevel
2022-09-06T18:54:34.599Z CNTRLR   [Node 093] Root device interview: Indicator
2022-09-06T18:54:34.601Z CNTRLR   [Node 093] Interviewing Indicator...
2022-09-06T18:54:34.601Z CNTRLR » [Node 093] scanning supported indicator IDs...
2022-09-06T18:54:34.606Z CNTRLR   [Node 093] Error during node interview: Node #93 does not support the command
                                  SupportedGet! (ZW0302)

does not support the command HealthGet
2022-09-06T18:57:23.547Z DRIVER « [Node 093] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -68 dBm
                                  └─[SecurityCCCommandEncapsulation]
                                    │ sequenced: false
                                    └─[BatteryCCReport]
                                        level:  96
                                        is low: false
2022-09-06T18:57:23.562Z CNTRLR « [Node 093] received response for battery information:
                                  level:                           96
                                  status:                          undefined
                                  rechargeable:                    undefined
                                  is backup:                       undefined
                                  is overheating:                  undefined
                                  fluid is low:                    undefined
                                  needs to be replaced or charged: undefined
                                  is low temperature               undefined
                                  is disconnected:                 undefined
2022-09-06T18:57:23.562Z CNTRLR » [Node 093] querying battery health...
2022-09-06T18:57:23.565Z CNTRLR   [Node 093] Error during node interview: Node #93 does not support the command
                                  HealthGet! (ZW0302)

@doug-hoffman that was fixed today in https://github.com/zwave-js/node-zwave-js/pull/5015, version 10.0.4 (HA addon 0.1.70, z2m 7.1.0)

that was fixed today in #5015, version 10.0.4 (HA addon 0.1.70, z2m 7.1.0)

Excellent! Wasn't certain any of those fixes were related. I've already done a PR to bump the zwavejs2mqtt addon to 7.1.0. Just waiting for it to get released.

Is there any special configuration I'd need with this new version? I upgraded to 0.46.1 w/ 7.1.0 and 10.0.7 and my interviews are still failing to pick up any metadata even with a 10s timeout.

Still seeing issues on 7.1.0, as well. Downgraded to 6.15.2 and the situation is much better. Gotta take a few nights off from messing with z-wave stuff and give attention to other things. I'll collect logs once I have some time to spare.

So I've solved my issue. Since I had set these up quite a while ago, they were still using S0 legacy "security"
I unenrolled all the locks, generated S2 keys, restarted HA, and reenrolled everything (also replacing batteries in all locks) and everything is back up and running with all expected metadata in-tact.
One thing I also did was I use an Aeotec Gen5 stick, which reportedly has problems when connected to USB 3.0 ports (even though it's USB 2.0 itself) due to some funky signal probing it does on connect. I purchased a short USB 2.0 extension to force it always at USB 2.0.
Not sure which one of these things specifically solved my issues, but my locks are all back up and running again.
Thanks to all for the pointers.

Not sure which one of these things specifically solved my issues

The USB extension definitely played a big part in this


Fix zone_awareness_config config part

Hi there,
I have an issue with zone_awareness_config,
this parameter's nested availability_zone_count can either be set to 2 or 3 or omitted at all. I can't set it to one.
So if I set zone_awareness_enabled = false and availability_zone_count = 2
Every time I run terraform plan I get this
      ~ cluster_config {
            dedicated_master_count   = 0
            dedicated_master_enabled = false
            instance_count           = 1
            instance_type            = "t2.small.elasticsearch"
            zone_awareness_enabled   = false

          + zone_awareness_config {
              + availability_zone_count = 2
            }
        }

Expected behaviour - If availability_zone_count is set to 1, omit this config part at all.
I'm looking into what I can done to fix it and probably will send a pull-request later on.

Guys, any progress please with merging the PR^? This issue is really annoying. Thanks.

Issue occurs again in version 0.33.3


dyno does not live long

Hi, I'm using boarding on 2 free dynos. when i first deploy them they are fine for a few days. after that, they seem dead and i get this (attached image). I'm sure there is something I'm missing, as I'm not that familiar with heroku. Any suggestions what might cause this? Thanks.

Can you look at the look on your server? You'll find more information about the error there

I'm seeing an application error as well, and considering my lack of familiarity with heroku dynos, I imagine it's related.
My logs are:
2016-04-08T09:02:16.014169+00:00 heroku[worker.1]: Starting process with command bundle exec rake jobs:work
2016-04-08T09:02:16.591837+00:00 heroku[worker.1]: State changed from starting to up
2016-04-08T09:02:17.112456+00:00 app[web.1]: Successfully created tester<EMAIL_ADDRESS>2016-04-08T09:02:17.113168+00:00 app[web.1]: Addding tester to application
2016-04-08T09:02:17.986206+00:00 app[web.1]: Done
2016-04-08T09:02:19.609645+00:00 app[worker.1]: rake aborted!
2016-04-08T09:02:19.609672+00:00 app[worker.1]: Don't know how to build task 'jobs:work' (see --tasks)
2016-04-08T09:02:19.609911+00:00 app[worker.1]:
2016-04-08T09:02:19.609953+00:00 app[worker.1]: (See full trace by running task with --trace)
2016-04-08T09:02:20.383394+00:00 heroku[worker.1]: Process exited with status 1
2016-04-08T09:02:20.409419+00:00 heroku[worker.1]: State changed from up to crashed
2016-04-08T09:02:44.162415+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=POST path="/submit" host=XXXX request_id=d29c8fd4-1cfb-4a34-8674-af8e1522974c fwd="<IP_ADDRESS>" dyno=web.1 connect=1ms service=30001ms status=503 bytes=0

I just got this error as well. Apple locked my Apple ID saying someone from Virginia just signed in – I'm thinking that's the script signing in and Apple thinks it's a hacker. How do we resolve this? I know I resolved it on my end by typing in a 6 digit pin they gave me, but how do I resolve it on the script's end? I really hope I can get this working again.

@lghstim You didn't share any information about your setup, output or stack trace. Please do so, so we can help you. This is probably related to 2 step verification

@KrauseFx pretty much what I did was press the "Deploy to Heroku" button and typed in my iTunes Connect username and password and my App's bundle ID. Boarding worked for 2 days but then I got the same error as @rlimberger did. A few minutes later Apple locked me out of iTunes connect and told me someone from Virginia tried to login. I don't have 2-step verification enabled. Sorry, but I don't really know where to find my stack trace since this is my first time using Heroku.

Same issue. @lghstim Did you find the solution?  After my Apple ID locked, Apple ask me reset account password, then I shutdown the Boarding app on Heroku

For now, the only way to bypass this is to turn off Apple's Two-Factor Authentication...

Is there a workaround for this @KrauseFx ?  I do not have two factor authentication enabled on my Apple ID however I noticed this behavior after a few days (set up on Friday worked fine, see the error on Monday)
I am not a Heroku expert and simply deployed from the button on the GitHub readme.
I'd really like to use this service but this is a major issue.

I have the same issue as @owencarp from today with the same log.
I have tried to reset heroku db (with heroku pg:reset DATABASE) and restart all dynos, but it didn't help.

I just ran into this issue as well. I had luck for 2 weeks before I got this.

I'm seeing this issue as well.
 Spaceship::TunesClient::ITunesConnectError (there is no web session to update):
2016-12-08T17:34:09.649186+00:00 app[web.1]:   app/controllers/invite_controller.rb:164:in `login'
2016-12-08T17:34:09.649187+00:00 app[web.1]:   app/controllers/invite_controller.rb:143:in `app'
2016-12-08T17:34:09.649187+00:00 app[web.1]:   app/controllers/invite_controller.rb:155:in `block in app_metadata'
2016-12-08T17:34:09.649188+00:00 app[web.1]:   app/controllers/invite_controller.rb:153:in `app_metadata'
2016-12-08T17:34:09.649189+00:00 app[web.1]:   app/controllers/invite_controller.rb:168:in `set_app_details'

Please update to the latest version, this is not related to the original issue, but with a new version of spaceship

@KrauseFx killed and re-deployed my application through the link the Readme and it is working!  Thanks for the quick fix guys.

Hey Felix, I think I've run into a similar problem that I'm not able to currently understand. Since I'm running the latest version, are you able to shed some light on this for me? It was running since 22 days exactly, maybe it's connected with "3 weeks", but not sure how.
2017-05-23T05:50:36.313361+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/bin/puma:22:in `load'
2017-05-23T05:50:36.313361+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/bin/puma:22:in `<top (required)>'
2017-05-23T05:52:15.449818+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=mydictionaryapp.herokuapp.com request_id=b43d371f-2e31-4edd-991e-fcd0232a41a7 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2017-05-23T06:22:15.599683+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=mydictionaryapp.herokuapp.com request_id=5e6c87ab-a4da-4e22-8804-165da19ffa10 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2017-05-23T06:52:15.312907+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=mydictionaryapp.herokuapp.com request_id=bf9402a5-0bee-4935-b8fe-e8f7706b244d fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2017-05-23T07:15:28.975287+00:00 heroku[web.1]: State changed from crashed to starting
2017-05-23T07:15:32.722231+00:00 heroku[web.1]: Starting process with command `bundle exec puma -C config/puma.rb`
2017-05-23T07:15:34.713656+00:00 app[web.1]: [4] Puma starting in cluster mode...
2017-05-23T07:15:34.713677+00:00 app[web.1]: [4] * Version 3.8.2 (ruby 2.3.4-p301), codename: Sassy Salamander
2017-05-23T07:15:34.713678+00:00 app[web.1]: [4] * Min threads: 5, max threads: 5
2017-05-23T07:15:34.713679+00:00 app[web.1]: [4] * Environment: production
2017-05-23T07:15:34.713679+00:00 app[web.1]: [4] * Process workers: 2
2017-05-23T07:15:34.713680+00:00 app[web.1]: [4] * Preloading application
2017-05-23T07:15:38.506040+00:00 heroku[web.1]: Process exited with status 1
2017-05-23T07:15:38.515076+00:00 heroku[web.1]: State changed from starting to crashed
2017-05-23T07:15:38.400265+00:00 app[web.1]: Spaceship::TunesClient::ITunesConnectError: there is no web session to update
2017-05-23T07:15:38.400267+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/fastlane-2.28.4/spaceship/lib/spaceship/tunes/tunes_client.rb:222:in `handle_itc_response'
2017-05-23T07:15:38.400197+00:00 app[web.1]: bundler: failed to load command: puma (/app/vendor/bundle/ruby/2.3.0/bin/puma)
2017-05-23T07:15:38.400267+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/fastlane-2.28.4/spaceship/lib/spaceship/tunes/tunes_client.rb:94:in `team_id='
2017-05-23T07:15:38.400065+00:00 app[web.1]: [4] ! Unable to load application: Spaceship::TunesClient::ITunesConnectError: there is no web session to update
2017-05-23T07:15:38.400268+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/fastlane-2.28.4/spaceship/lib/spaceship/tunes/tunes_client.rb:121:in `select_team'
2017-05-23T07:15:38.400269+00:00 app[web.1]:   /app/app/services/boarding_service.rb:76:in `ensure_values'
2017-05-23T07:15:38.400270+00:00 app[web.1]:   /app/app/services/boarding_service.rb:32:in `initialize'
2017-05-23T07:15:38.400270+00:00 app[web.1]:   /app/config/initializers/services.rb:1:in `new'
2017-05-23T07:15:38.400271+00:00 app[web.1]:   /app/config/initializers/services.rb:1:in `<top (required)>'
2017-05-23T07:15:38.400272+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/dependencies.rb:268:in `load'
2017-05-23T07:15:38.400273+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/dependencies.rb:268:in `block in load'
2017-05-23T07:15:38.400273+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/dependencies.rb:240:in `load_dependency'
2017-05-23T07:15:38.400275+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/engine.rb:652:in `block in load_config_initializer'
2017-05-23T07:15:38.400274+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/dependencies.rb:268:in `load'
2017-05-23T07:15:38.400276+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/notifications.rb:166:in `instrument'
2017-05-23T07:15:38.400276+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/engine.rb:651:in `load_config_initializer'
2017-05-23T07:15:38.400277+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/engine.rb:616:in `block (2 levels) in <class:Engine>'
2017-05-23T07:15:38.400278+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/engine.rb:615:in `each'
2017-05-23T07:15:38.400279+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/engine.rb:615:in `block in <class:Engine>'
2017-05-23T07:15:38.400279+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:30:in `instance_exec'
2017-05-23T07:15:38.400280+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:30:in `run'
2017-05-23T07:15:38.400281+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:55:in `block in run_initializers'
2017-05-23T07:15:38.400281+00:00 app[web.1]:   /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/tsort.rb:228:in `block in tsort_each'
2017-05-23T07:15:38.400282+00:00 app[web.1]:   /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/tsort.rb:350:in `block (2 levels) in each_strongly_connected_component'
2017-05-23T07:15:38.400283+00:00 app[web.1]:   /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/tsort.rb:422:in `block (2 levels) in each_strongly_connected_component_from'
2017-05-23T07:15:38.400283+00:00 app[web.1]:   /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/tsort.rb:431:in `each_strongly_connected_component_from'
2017-05-23T07:15:38.400284+00:00 app[web.1]:   /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/tsort.rb:421:in `block in each_strongly_connected_component_from'
2017-05-23T07:15:38.400285+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:44:in `each'
2017-05-23T07:15:38.400285+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:44:in `tsort_each_child'
2017-05-23T07:15:38.400286+00:00 app[web.1]:   /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/tsort.rb:415:in `call'
2017-05-23T07:15:38.400287+00:00 app[web.1]:   /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/tsort.rb:415:in `each_strongly_connected_component_from'
2017-05-23T07:15:38.400287+00:00 app[web.1]:   /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/tsort.rb:349:in `block in each_strongly_connected_component'
2017-05-23T07:15:38.400288+00:00 app[web.1]:   /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/tsort.rb:347:in `each'
2017-05-23T07:15:38.400288+00:00 app[web.1]:   /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/tsort.rb:347:in `call'
2017-05-23T07:15:38.400289+00:00 app[web.1]:   /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/tsort.rb:347:in `each_strongly_connected_component'
2017-05-23T07:15:38.400290+00:00 app[web.1]:   /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/tsort.rb:226:in `tsort_each'
2017-05-23T07:15:38.400290+00:00 app[web.1]:   /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/tsort.rb:205:in `tsort_each'
2017-05-23T07:15:38.400291+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:54:in `run_initializers'
2017-05-23T07:15:38.400292+00:00 app[web.1]:   /app/config/environment.rb:5:in `<top (required)>'
2017-05-23T07:15:38.400292+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/application.rb:352:in `initialize!'
2017-05-23T07:15:38.400293+00:00 app[web.1]:   config.ru:3:in `require'
2017-05-23T07:15:38.400294+00:00 app[web.1]:   config.ru:3:in `block in <main>'
2017-05-23T07:15:38.400295+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/builder.rb:55:in `instance_eval'
2017-05-23T07:15:38.400296+00:00 app[web.1]:   config.ru:in `new'
2017-05-23T07:15:38.400295+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/builder.rb:55:in `initialize'
2017-05-23T07:15:38.400297+00:00 app[web.1]:   config.ru:in `<main>'
2017-05-23T07:15:38.400297+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/builder.rb:49:in `eval'
2017-05-23T07:15:38.400307+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/builder.rb:49:in `new_from_string'
2017-05-23T07:15:38.400308+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/builder.rb:40:in `parse_file'
2017-05-23T07:15:38.400308+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/puma-3.8.2/lib/puma/configuration.rb:313:in `load_rackup'
2017-05-23T07:15:38.400309+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/puma-3.8.2/lib/puma/configuration.rb:242:in `app'
2017-05-23T07:15:38.400310+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/puma-3.8.2/lib/puma/runner.rb:138:in `load_and_bind'
2017-05-23T07:15:38.400310+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/puma-3.8.2/lib/puma/cluster.rb:391:in `run'
2017-05-23T07:15:38.400311+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/puma-3.8.2/lib/puma/launcher.rb:172:in `run'
2017-05-23T07:15:38.400312+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/puma-3.8.2/lib/puma/cli.rb:77:in `run'
2017-05-23T07:15:38.400312+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/puma-3.8.2/bin/puma:10:in `<top (required)>'
2017-05-23T07:15:38.400313+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/bin/puma:22:in `load'
2017-05-23T07:15:38.400330+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/bin/puma:22:in `<top (required)>'
2017-05-23T07:22:15.596412+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=mydictionaryapp.herokuapp.com request_id=33de56e4-523f-4a47-b3fc-82495470d16d fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2017-05-23T07:40:19.742198+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=mydictionaryapp.herokuapp.com request_id=67c56961-04a0-4b6f-b24f-b7aaf32972af fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=http
2017-05-23T07:40:22.701507+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=mydictionaryapp.herokuapp.com request_id=d7f23ece-06bb-4c53-bfc7-cbc9e27cef40 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=http

thanks a bunch!

@s2imon thanks for letting me know, I just pushed a new commit, please update to the most recent version 👍


Clarify data layout for PaddlePaddle CPU kernels.

In doc part regarding design of NHWC support for MKLDNN, I've clarified what data layout is used for learnable parameters and what for operator input signals in PaddlePaddle CPU kernels.

 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.

@jczaja Please review.

@arogowie-intel Excellent! Much clearer now. LGTM

@jczaja I don't have permissions to ask any one for review, moreover don't know who to ask. Could you help?

@luotao1 Could you please review this one?


Port tests from Elixir's Inspect.Algebra

Since this package is so similar to Elixir's Inspect.Algebra I could add more tests taking as a reference the ones they use. The API is quite similar so it wouldn't be too hard to port those
Why is this a good first issue and how can you help?
Adding this shouldn't be too hard if you can read a bit of Elixir.
Basically, what one would need to do is:

look at Inspect.Algebra's tests
rewrite each test in Gleam

the tests can be added to the glam/doc_test module
most likely you'll need to have a look at Inspect.Algebra's documentation
mapping each of Inspect.Algebra's functions into the corresponding glam one. The API is quite similar but things may have different names

I think I'm quite happy with the current suite of tests and snapshot tests, there's no need to worry about this one now


test: fix jinja templates in conditionals

Fix the error reported by recent Ansible versions: Conditional statements should not include jinja2 templating delimiters. Conditional is marked as unsafe, and cannot be evaluated.

[citest]


solutions list as table

Signed-off-by: Ashraf Fouda<EMAIL_ADDRESS>Description
Describe the changes introduced by this PR and what does it affect
Changes
List of changes this PR includes
Related Issues
List of related issues
Checklist

[ ] Tests included
[ ] Build pass
[ ] Documentation
[ ] Code format and docstrings


Using rate() with VictoriaLogs and LogsQL in Grafana

Trying to understand is it possible to have something similar to the rate() function in Loki?
For example, I have the following query for Loki in Grafana to get a per-second traffic rate from VPC Flow Logs:
topk(5,
  sum by (pkt_src_addr) (
    rate(
      (
        {logtype="flow", logger_type="loki"}
        | pattern `<region> <vpc_id> <az_id> <subnet_id> <instance_id> <interface_id> <flow_direction> <src_addr> <dst_addr> <src_port> <dst_port> <pkt_src_addr> <pkt_dst_addr> <pkt_src_aws_service> <pkt_dst_aws_service> <traffic_path> <packets> <bytes> <action>`
        | interface_id="eni-0352f8c82da6aa229"
        | action="ACCEPT"
        | pkt_src_addr=ip("<IP_ADDRESS>/20")
        | pkt_src_addr=~"${kubernetes_pod_ip}"
        | pkt_dst_addr=~"${remote_svc_ip}"
        | unwrap bytes
        | __error__=""
      )[15m]
    )
  )
)

How can I achieve something similar with VMLogs and its LogsQL?

Hi @arseny-zinchenko ! This issue should be opened in the main repository of the VictoriaMetrics

Closing this issue as duplicate of https://github.com/VictoriaMetrics/VictoriaMetrics/issues/7646


Spatial::look_at() now preserves its scale values

It always normalized basis after look_at() computation.
Now it applies previous scale back, in order to avoid
distortions when global scale was different of (1,1,1).
fix #10003 and fix #19000

Please squash those commits together.

This should be done in Node, but not in Transform, since Transform one is a reference implementation of the function and it creates a new one, without keeping anything.

It would also fix #17924.

I originally coded on Node, but I thought it would be better to be on
Transform.
As I was wrong, I'll fix it later today
Em qui, 25 de abr de 2019 às 20:34, Tomek<EMAIL_ADDRESS>escreveu:

It would also fix #17924
https://github.com/godotengine/godot/issues/17924.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/pull/26897#issuecomment-486874021,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKDHU6ADLW4BL4MTFHJJP3PSI5YNANCNFSM4G47EROA
.

Thanks!

Thank you! I was affected by this too in my custom billboards. I hope this gets pushed to production ASAP.

Hi,
I might be wrong but shouldn't look_at_from_position be corrected also ?
I know it's not the same use case, but to me look_at_from_position can fire the same bug, no ?.
And in addition, it doesn't have the error checks that look_at has.

I found look_at_from_position does reset scale in 3.1, would be nice to be fixed if it still does in master.

You should definitely create a new issue, so it doesn't get lost, and it's easier to find for someone with the same problem

@malbach fixed and merged ;)


Fix icon consistency with the original javascript implementation

This PR fixes utilities.getNumber to generate the same output as the getHash function from the original. This way the icons created by this flutter implementation are similar to icons of the javascript-based original. This is useful in cases where both are used side-by-side in an ecosystem consisting of a flutter app and a website.
Since this PR produces different icons, it may be considered a major version change. Perhaps it is better to offer both options, defaulting to the old behavior. That would be a bigger change.
For reference and ease of reviewing, here's the original javascript has function:
https://github.com/boringdesigners/boring-avatars/blob/master/src/lib/utilities.js#L1C1-L9C2

Thank you. I apologize for the delayed response. The merged code will be released as version 1.1.0


Can I change the exiting listener Protocol

[Enter feedback here]
I have created a listener. Its Protocol is http. I want to change its Protocol from http to https. Can I do that? If I can do, how to implement it with python?

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

ID: 73282a20-be05-8b47-930c-3a9567014226
Version Independent ID: 9728db84-6176-c930-a99d-4193069d9fb0
Content: Create an application gateway with SSL termination - Azure PowerShell
Content Source: articles/application-gateway/tutorial-ssl-powershell.md
Service: application-gateway
GitHub Login: @vhorne
Microsoft Alias: victorh

@test123114 , Thank you for your feedback.
You can change the protocol from HTTP to HTTPS in the listener but you will need to upload SSL cert to the listener.
You can do that via Portal, ARM template, PowerShell, Azure CLI, REST API.
Any specific reason why you wanted to do it via Python?

Hi. I just create the resource with python SDK. So I want to know how to do that with python. You also can tell me how to do that with PowerShell.

@test123114 , i have uploaded the scrip to the gallery.
https://gallery.technet.microsoft.com/Convert-HTTP-listener-to-3981310b

Hi. I cannot visit the website.

@test123114 , are you able to create the listener? Can you provide more details?

Hi.
Now I can use the powershell script to update it. But now I cannot update it with python.
My code

    async_ag_creation = network_client.application_gateways.create_or_update(
        GROUP_NAME,
        APPLICATION_GATEWAY_NAME,
        {
            "location" : "southeastasia",
            "ssl_certificates": [{

                "data": "",
                "password": "",
                "name": appgateway_SSL_name
            }],
            "frontend_ports": [{
                "name": appgateway_frontport_name,
                "port": 443
            }],
            "http_listeners": [{
                "name": appgateway_http_listener_name,
                "frontend_ip_configuration": {
                    "id": appgateway_id + "/frontendIPConfigurations/" + appgateway_frontip_name
                },
                "frontend_port": {
                    "id": appgateway_id + '/frontendPorts/' + appgateway_frontport_name
                },
                "protocol": "Https",
                "ssl_certificate":{
                    "id": appgateway_id + '/sslCertificates/' + appgateway_SSL_name
                }
            }]
        }
    )

It does not work. Could can help me?

@test123114 , Unfortunately, I will not be able to help on that. You can look into the PowerShell commands and use the same logic to get it updated.


PopsicleError class no longer exposed in 3.0.x

Thanks for Popsicle! It's been a joy to use. :smile:
In 2.0.x, the PopsicleError class was exposed at require('popsicle').Error, which was handy for doing instanceof checks. As of 3.0.0, it's no longer exposed there. Was this intentional?
It looks like I can still get the error class with require('popsicle/dist/error'), but that feels a bit like I'm poking around in innards that might change. What would you recommend?

Not intentional to block access to this, I'll re-expose it.

https://github.com/blakeembrey/popsicle/releases/tag/v3.0.3 :+1:

Awesome. Thanks!


request for consistent tag formatting

Current Behaviour
When you publish new versions or create new tags for this repository, could you please adhere to a consistent format? something like vx.y.z is fine. This would help me a lot. Thank you.
Expected Behaviour
tag looks like vx.y.z, eg. v4.8.3
Data Description
none
Code that reproduces the bug
No response
pandas-profiling version
4.8.3
Dependencies
none

OS
No response
Checklist

[X] There is not yet another bug report for this issue in the issue tracker
[X] The problem is reproducible from this bug report. This guide can help to craft a minimal bug report.
[X] The issue has not been resolved by the entries listed under Common Issues.

@hubutui we do have a consistent tagging system, not sure what do you mean by that . We do keep the same format 4..
This last release there was an issue with the actions and that triggered some issues regarding the pre-release versions, but not the published version itself. This is something we can control.
But perhaps you could detail a bit more and be more specific? As we might be missing your point.

Yes, I found the release v4.8.3, https://github.com/ydataai/ydata-profiling/releases/tag/4.8.3,  but the tag is 4.8.3. So the source tarball url is https://github.com/ydataai/ydata-profiling/archive/refs/tags/4.8.3.tar.gz. But the previous release and git tags, they're something like v4.8.1, with source tarball https://github.com/ydataai/ydata-profiling/archive/refs/tags/v4.8.1.tar.gz. Note the prefix v in both the tag name and source tarball url. Just make it consistent, always with or without the v prefix. This is very helpful for me to automatically download the new source tarbal once a new release is available with a robot checking the new release with github api.

As mentioned previously, that release was an outlier as we had issues with the system and release process.
Rest assured we have and we have always had the tag formatting in place for the releases.


[Llama3] Refactor tests

After Llama3 feature complete PR gets merged we should dedicate some time refactoring our common Llama3 tests, as the golden standard for all our future LLM support.
This not only simplifies developers PRs by avoiding code duplication and complicated test tracking, but also greatly alleviates CI load and makes it easier to bringup new family of models.
There are other refactors we're planning, like the model config refactor, but those will be tracked in their own issues.
Draft Proposal
The new test infrastructure needs to comply with:

Cover the modules/tests we actually care about
Easily scalable
Easily understandable
Low CI load

Unit tests
Single template that supports every unit test. - Compares ttnn modules to their reference counterparts. No need to load model weights. Checks PCC and optionally e2e perf. 1 layer only.
Takes the following inputs:

input shape
ttnn module to test (e.g. attention, MLP, rmsnorm, etc.)
output shape(s) (e.g. compare both output and K and V caches)

The template then will be tasked with creating a ttnn tensor of input shape, sending that tensor to the ttnn module (e.g. MLP), getting it's output(s), sending them back to host and calculating the PCC against the reference output(s).
To avoid slow unit tests, we shall provide for all our Llama3 models (1B, 3B, 8B, 11B, 70B, etc) reference tensors. These tensors should be in a separate repository with git-lfs support, that we load through submodule. There will be many of these reference tensors, but each one of them will be small. See more in the issue: https://github.com/tenstorrent/tt-metal/issues/15114
The unit test template will include a list of all the expected PCC values and optionally e2e perf values for every combination of valid model, architecture and unit test.
This way, when a developer modifies a Llama module, they will then only need to run the unit test once and look out for it's output summary to see a list of what passed and what hasn't passed.
If a new model or module unit test is introduced, it's up to the developer to add a PCC check and provide the reference tensors.
CI
This methodology greatly simplifies CI integration from the model team side. CI would run all the unit tests (with respective safeguards to avoid running 70B tests on N150 machines for example), and developers wouldn't have to add new unit tests or models to CI, as it would automatically picked them all up.
Other tests (still thinking how to refactor these)
We are still defining which tests are mandatory for all models, but for Llama we would also have:

Demo: runs the latency/throughput/max-length tests and captures e2e perf
test accuracy: Demo, with teacher forcing but captures top1/top5. To simplify this one moving forward, we might just make it a symlink of demo and run it with a different accuracy parameter.
Device perf: Demo again, but with device profile. Requires a more stable tracy.

FIY @uaydonat


Screen shot not showing what is described

Page says, "For example, in the following screenshot, the values are in yellow for Average jitter, Max jitter, and Average packet loss rate."  However, the screenshot immediately below shows no data in yellow and no data about jitter or packet loss rate.

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

ID: ea52e6be-e0ae-4941-7bab-aeea5c5fc708
Version Independent ID: a38a6f0c-cb99-ea4d-e406-968fd07ec0c2
Content: Use Call Analytics to troubleshoot poor call quality
Content Source: Teams/use-call-analytics-to-troubleshoot-poor-call-quality.md
Service: msteams
GitHub Login: @LolaJacobsen
Microsoft Alias: lolaj

@Marshall-L-D it has the wrong image there for sure

@Marshall-L-D Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@Marshall-L-D thank you for pointing this out.  I'm working to have this issue fixed soonest.

Hi @LolaJacobsen. Please could you assist with the screenshot and I'll add it in a PR?

@LolaJacobsen Following up on this issue. Thanks.

We're preparing a complete overhaul of the CQD documentation over the upcoming weeks, so this artwork will get revised as part of that effort. Thanks for the heads up!


use ansible_processor fact in place of ansible_processor_vcpus

The ansible_processor_vcpus fact has been found to detect the incorrect number of available cpus.  Moving to ansible_processor instead.

retest

retest

retest

retest

retest

retest

retest

Still LGTM.

retest


Add an option to hide/show the errors.

That would be a good idea if it will be possible to hide/show the errors, because if the warning is not resolved, the space is always used by the linter.

I think this is already built-in to linter. You can click file/project at the bottom to show/hide the panel that displays all the errors.
If you meant something different comment here and we can re-open.

The cross icon doesent work, if i click on it, nothing happens, and there is nothing to show on the console if there was an error.
I use Atom 1.5.3

Click on where it says 'File' or 'Project' just to the left of the red X in your screenshot ot show/hide details on the error.
Otherwise, to have the linter ignore a a specific instance of error, you'll need to modify your code directly--see the pep8 docs... IIRC you add # noqa to the end of that specific line.

ah, thank you ^_^


[SPARK-36365][PYTHON] Remove old workarounds related to null ordering

What changes were proposed in this pull request?
Remove old workarounds related to null ordering.
Why are the changes needed?
In pandas-on-Spark, there are still some remaining places to call Column._jc.(asc|desc)_nulls_(first|last) as a workaround from Koalas to support Spark 2.3.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Modified a couple of tests and existing tests.

cc @HyukjinKwon @xinrong-databricks @itholic

Test build #141914 has started for PR 33597 at commit 15784ae.

Test build #141914 has finished for PR 33597 at commit 15784ae.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/141914/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46423/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46423/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/46423/

Merged to master and branch-3.2.


Add to awesome-raylib

There's a section for bindings and I noticed there wasn't a Raku lib on there yet.
https://github.com/Rabios/awesome-raylib

Do you mean this Bindings, which they link to?

The repo no longer exists.


Only download data if processing status is Ready

Internal issue - PV-1923

Since the tests and everything still point to staging.vandersat.com I do not have the time to fix all of this for this api client.
I tested this change manually on my computer and it works as expected. So I'm merging this without CI :cry:


Add Espree Parser

Let's do an updated version of this using espree:
http://esprima.org/demo/parse.html
We could borrow the style used here:
https://babeljs.io/repl/

This is super cool:
http://felix-kling.de/esprima_ast_explorer/

Very nice indeed! Looks like he's planning to add other parsers as well (Espree included): https://github.com/fkling/esprima_ast_explorer/issues/20

I'm almost there, will publish something in the next few days.
I was also thinking to support eslint plugin prototyping. Currently, when you click the transform button, you will get jscodeshift for generic AST-to-AST transform stuff. But if I generalize this a bit, then the "transform" could be interpreted as eslint plugin (and load and run eslint). It should be relatively easy then to add new tools. That's a bit further down the road though.

Added espree and got a shine new domain: http://astexplorer.net/.


New fields for boards

See API.  Missing these fields.

dateLastActivity
dateLastView
descData
invitations
invited
pinned
shortLink
shortUrl
starred

Looks like there are a lot more background settings in board prefs as well.
"prefs": {
"permissionLevel": "public",
"voting": "disabled",
"comments": "members",
"invitations": "members",
"selfJoin": true,
"cardCovers": true,
"calendarFeedEnabled": false,
"background": "grey",
"backgroundImage": null,
"backgroundImageScaled": null,
"backgroundTile": false,
"backgroundBrightness": "dark",
"backgroundBottomColor": "#838C91",
"backgroundTopColor": "#838C91",
"backgroundColor": "#838C91",
"canBePublic": true,
"canBeOrg": true,
"canBePrivate": true,
"canInvite": true
}

see branch feature/80-board-fields

Targeting v2.3.0


Quote argument to echo

The argument to echo contains newline characters, and so must be quoted to ensure the newlines are printed correctly when Vim is configured to use bash, fish, or zsh to run shell commands.
Thanks to @boxofrox for reporting this.

Confirming this works for me with zsh 5.3.1. :+1:


Add KGO0 to nowcast-extrapolate with metadata BATS test

After PR's #679 and #673 went in, the AT data associated with PR #633 was out of date.
I didn't notice this when merging (my bad), so I've updated the AT data and the test coverage.
Testing:

[x] Ran tests and they passed OK
[x] Added new tests for the new feature(s)

If you've tested it and it works, I'm happy


fix: build and tests on OpenBSD

Description of changes:
This PR repairs and tidies up the build and tests on OpenBSD. Testing performed on OpenBSD 7.2/amd64.
100% tests passed, 0 tests failed out of 424

Total Test time (real) =  54.68 sec

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report
Base: 80.79% // Head: 80.79% // No change to project coverage :thumbsup:

Coverage data is based on head (b999bc8) compared to base (951b70f).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #976   +/-   ##
=======================================
  Coverage   80.79%   80.79%
=======================================
  Files          53       53
  Lines        5665     5665
=======================================
  Hits         4577     4577
  Misses       1088     1088

Impacted Files
Coverage Δ

source/posix/thread.c
80.70% <ø> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Codecov Report
Base: 80.79% // Head: 80.79% // No change to project coverage :thumbsup:

Coverage data is based on head (255ed4b) compared to base (951b70f).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #976   +/-   ##
=======================================
  Coverage   80.79%   80.79%
=======================================
  Files          53       53
  Lines        5665     5665
=======================================
  Hits         4577     4577
  Misses       1088     1088

Impacted Files
Coverage Δ

source/posix/thread.c
80.70% <ø> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Create interactive mode

Especially for testing purposes, it would be good to have an interactive mode which stops at critical points to ask if it's ok to continue. This would be good for identifying any issues that might fly by unnoticed when reams of logging flies by on the screen.
Suggested option -i

b8e2756
Added interactive mode to get_moodle function as a trial. Will implement to rest of the code if it works as intended.

b8e2756
Added interactive mode to get_moodle function as a trial. Will implement to rest of the code if it works as intended.

658bf94bc031741e6e418878904d3db6bf4598d9
Introducing colour to interactive mode. Will add interactive mode to more functions.

658bf94bc031741e6e418878904d3db6bf4598d9
Introducing colour to interactive mode. Will add interactive mode to more functions.

64a9a2e3989c1595ac70a62d353189544c0e381e
New tag v0.2 introduces interactive mode.

64a9a2e3989c1595ac70a62d353189544c0e381e
New tag v0.2 introduces interactive mode.


[JS] Run the named actions before running the format when the file is open (issue #15818)

It's a follow-up of #14950: some format actions are ran when the document is open but we must be sure we've everything ready for that, hence we have to run some named actions before runnig the global format.
In playing with the form, I discovered that the blur event wasn't triggered when JS called setFocus (because in such a case the mouse was never down). So I removed the mouseState thing to just use the correct commitKey when blur is triggered by a TAB key.

/botio integrationtest

/botio unittest


Add ng-Print to bower repo

Hi Gil,
could you add ng-Print to bower repo for easier access/dependency management?
https://bower.io

Done.
You can use bower ngPrint to install the directive.


refactor: switch to custom html5 dialog implementation

Switch to homegrown modal implementation based on html5 dialog element (no need to add the whole @hope-ui library for a single component, moreover it adds its own custom theming infrastructure that I do not need)
Use motionone/solid for modal enter animation (only on larger screens where the modal is not fullscreen).

👍🏻


@conda-forge-admin, rerender

[ ] I read the conda-forge documentation and could not find the solution for my problem there.

Issue:

Environment (conda list):

$ conda list

Details about  conda and system ( conda info ):

$ conda info

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I rerendered the recipe in conda-forge/ctng-compiler-activation-feedstock#47.


Example for the use within a mobile app like ionic

Hi,
I really like your work. It is really nice to custom on a website. I would love to integrate the same form in a ionic app but I fail to do so.  When I enter the code with the  in the html file it just stays blank.  Could you provide an example please how to use this within an angular/ionic app?
that would be really great.
Thanks a lot

This is an Angular 1 directive and should work in any Angular 1 environment. You're probably missing something in your app. Maybe you're not including JSON Editor dependency files...


laravel 5.2 incompatability

Not to rush you on updating for laravel 5.2 but i thought i'd post this for your reference.
FatalErrorException in LaravelShopProvider.php line 91: Call to undefined method Illuminate\Foundation\Application::bindShared()
Thanks

Call to undefined method Illuminate\Foundation\Application::bindShared()

Thanks for your help. i did do that after i posted this but there seemed to be further changes needed with laravel-shop elsewhere so i pulled off temporarily. are you successfully using laravel-shop with 5.2?

no not in 5.2 are there more issues let me know?

sure! i'm doing this:
$cart = Cart::current();

$user = Auth::user();

in my controller like I do in L5.1 but laravel-shop acts as if user_id is null even though i can dump user_id just fine. maybe an incompatability with l5.2 auth changes?
error i get:
SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'user_id' cannot be null (SQL: insert into `cart` (`user_id`, `updated_at`, `created_at`) values (, 2016-01-05 19:11:35, 2016-01-05 19:11:35))

thanks

/vendor/amsgames/laravel-shop/src/LaravelShopProvider.php
change this
/*$this->app->bindShared('command.laravel-shop.migration', function ($app) {             return new MigrationCommand();         });*/
with
$this->app->singleton('command.laravel-shop.migration', function ($app) {             return new MigrationCommand();         });

This ain't gonna close better don't comment i am getting notification


Add a Media Player Component for Channels

Description:
This adds a media_player component for the app Channels (https://getchannels.com)
It supports:

playback state
what's currently playing
art of what is currently playing
pause
resume
skip commercials

I also offers 3 extra services:

channels_seek_forward - seeks forward the number of seconds currently set in the Channels app
channels_seek_backward - seeks backward the number of seconds currently set in the Channels app
channels_seek_by - seek the number of seconds inputted.

Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#4842
Example entry for configuration.yaml (if applicable):
- platform: channels
  name: Family Room Channels
  host: <IP_ADDRESS>

Checklist:

[x] The code change is tested and works locally.

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

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

Thanks for the feedback!! I've addressed all of the issues. This can have 👀s again.

🎉 🎉 🎉 🎉  🐬

Thanks for the review @MartinHjelmare. I addressed your comments on #12967.


slickGoTo breaks on non-infinite slick

When there is an item in the last group of slides that does not contain the number of slides specified in slidesToScroll, slick will navigate to the group before that slide, even if the slide is already in view.
Example:
Slick is initiated with slidesToScroll: 4, infinite: false.
There are 11 slides in the slider, numbered 1-11.
slickGoTo index 8, 9, or 10 will bring slides 5-8 in view instead of slides 8-11.
Here is a jsfiddle demonstrating this:
https://jsfiddle.net/6ubLpfwx/9/

Apologies for the lack of responsiveness. Looks like this got fixed as some point.
Updated fork
Thanks.


Replace pyjwkest

The pyjwkest package was abandoned upstream more than 3 years ago.  Let's replace it with something more actively maintained.  First check to see if the latest version of PyJWT (already used here) supports what we need from pyjwkest.  If not, I nominate Authlib as seeming to cover the same functionality with much more usage and active maintenance, but feel free to do a quick search on PyPI or elsewhere for a better replacement.

Maybe https://github.com/jpadilla/pyjwt/pull/723 added what we need?  Not sure without further digging into how this works.

Please see https://github.com/openedx/edx-drf-extensions/issues/333 for related discussion. I do not know if we have custom decoding code for asymmetric JWTs, or only for the symmetric JWTs.


invalidate path binding

https://github.com/libfuse/libfuse/blob/master/example/invalidate_path.c
Pretty straightforward:
static int invalidate(struct fuse *fuse, const char *path) {
	int status = fuse_invalidate_path(fuse, path);
	if (status == -ENOENT) {
		return 0;
	} else {
		return status;
	}

Can you do a pull-request for that?


Whistle but Chinese usage ?

Interested but why  ?
https://github.com/avwo/whistle

Do you mean why no English docs for whistle？
There is a issue for this https://github.com/avwo/whistle/issues/57, it would be nice if someone willing to help.

Ah thank you for info


Configurable Columns

Hi!,
very nice code. Thank you for that.
One suggestion: It may be beneficial to add configurable Columns, so that I can specificy whether a column should have a horizontal alignment right (e.G. if its a integer, like in excel) or in the middle or on the left.
Currently this is not possible as the settings are just on cell or row level.

Hey @MergimHo,
thanks for your request. Yes, you are right. A column does not support this as of now. I didn't really consider adding it until now but I can see at least one difficulty coming up. When having row spanning and column spanning the question is which setting (the row setting or the column setting) should get precedence? Or should it fall back to the setting from the table or the cell in this case? What if they are not set?
Still, I think you are right: It would add a bit of convenience if one could set different things already on the column level. But even then the question arises: If we set center alignment on column level and right alignment on row level what should happen?
Feel free to share your ideas on that issue! :)
Cheers,
Stefan

Hi Stefan,
actually this is quite easy.
Most of the tables work that way that their type is determined by the column. Row-level types and the data along the colums is very rare.
So it would be good to allow Column-Level configuration. And if the user needs, overwrite that with row level configs.

This is now part of the develop branch and will be released with the next release. The precedence for the settings is: cell level has highest precedence, then column, then row and finally table level.

Released with 0.8.4


Check Existences of Tables in Hastile Configuration File

Given a list of layer configurations check that the "table-name" property actually exists in the database (either a materialized view or a normal table).

Also add table checks to the script that generates the config.

Closed by 5d7dcae94777a50c5197aa3851fbb0ddf1e640fb


GSC Error tag amp-story

Bug Description
Google Search Console warns you that you can only have an amp-story derived tag in  as shown in the image.
Expected Behaviour

I sent the amp-story sitemap in Search Console and hours later this warning appeared that the content will not be indexed due to an amp-story tag error in . There should be no such error.

Screenshots

Additional Context

Plugin Version: Version 1.0.0-beta.1
Operating System: linux Ubuntu
Browser: Brave/Chrome

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief

Hi there
Running your story URL (https://nerdvision.com.br/stories/superman-the-movie-final-cut) through the AMP validator shows that there is 1 issue with AMP validation, which is the one that Search Console is reporting.
The issue is coming from this piece of code:

This is not allowed for Web Stories, at least not in this form. For Web Stories, <amp-analytics> needs to be used, see https://support.google.com/tagmanager/answer/9205783?hl=en.
Are you using a particular plugin to insert Google Tag Manager on your site? Or did you implement this yourself?

Hi friend. Thanks for the reply.
I use the wp plugin called Head, Footer and Post Injections. where I put the GTM tag.

Thanks for your info!
In the plugins settings, please try something like this for now:
<?php if ( ! is_singular( 'web-story' ) ) : ?>

<?php endif; ?>

Here's a screenshot of the settings page:

This will fix the error.
However, it means the GTM tag won't be printed for individual Web Stories.
To achieve that, you'd need to follow the instructions at https://support.google.com/tagmanager/answer/9205783?hl=en for creating an AMP container etc.
However, I would recommend you to use a plugin like Site Kit by Google to handle this automatically for you. Then it will work automatically and you don't even need the Head, Footer and Post Injections plugin for this.

Thank you for your help.
I did exactly as shown in your code, check the image, I deleted the WP cache and tested again on the AMP validator and the error continues.
Did I do something wrong.
ps: I installed the Google Site kit as indicated.
https://validator.ampproject.org/#url=https%3A%2F%2Fnerdvision.com.br%2Fstories%2Fsuperman-the-movie-final-cut

You need to delete lines 1-4. The only thing you should have in this box is this:
<?php if ( ! is_singular( 'web-story' ) ) : ?>

<?php endif; ?>

Nothing else.

Have you completed the Site Kit plugin's setup? If so, you should be able to deactivate the "Head, Footer and Post Injections" plugin and use GTM via Site Kit.

friend, thanks for the tips and your time.
I made the changes and now everything is ok!
thank you, you were very helpful.


snackbar duration

i guess there is a shorter or a better code :)

Besides, there is a very similar implementation called SnackbarOnAnyDeniedMultiplePermissionsListener we should update as well

I'm merging this PR in #141 and releasing a new version


tests/subsys/settings: build common code as zephyr_libraries

Stops leaking very long source paths in build directories; makes them
deterministic. Finishes what was started in commit b4282bf72db8, see
rationale and code reviews there.
See also CMake issue https://gitlab.kitware.com/cmake/cmake/issues/19475
for more details.
Use the opportunity to remove the most obvious duplication.
Test with: sanitycheck -T $ZEPHYR_BASE/tests/subsys/settings/
tests/subsys/settings/functional: de-duplicate zephyr_include_ and move it next to zephyr_library_sources()

@nvlsianpu could you take a look , since you're a code owner here?

@carlescufi Merge this one?

Thanks to all the reviewers!
I haven't explored this alternative out of fear of making some actual code change but I wonder if it would be possible (and much simpler) to have fewer src/ subdirectories and CMakeLists.txt files in tests/subsys/settings while keeping the same number of prj.conf and testcase.yml files... Any sanitycheck expert, @nashif , @galak , @andrewboie ?


Cannot install NativeBase due to dependencies

Description
i cannot install native-base in my expo app and it gives out the error mentioned below
CodeSandbox/Snack link

Steps to reproduce

type in terminal expo install native-base or npm install native-base
It gives out the error

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   peer react@"*" from<EMAIL_ADDRESS>npm ERR!   node_modules/native-base
npm ERR!     native-base@"*" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/react-dom
npm ERR!   peer react-dom@"*" from<EMAIL_ADDRESS>npm ERR!   node_modules/native-base
npm ERR!     native-base@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See C:\Users\user\AppData\Local\npm-cache\eresolve-report.txt for a full report.

npm ERR!      C:\Users\user\AppData\Local\npm-cache\_logs\2022-09-20T20_36_36_193Z-debug-0.log

NativeBase Version
3.4.16
Platform

[ ] Android
[ ] CRA
[X] Expo
[ ] iOS
[ ] Next

Other Platform
No response
Additional Information
eresolve-report.txt
# npm resolution error report

2022-09-20T20:37:52.850Z

While resolving<EMAIL_ADDRESS>Found<EMAIL_ADDRESS>node_modules/react
<EMAIL_ADDRESS>from the root project
  peer react@"*" from<EMAIL_ADDRESS>  node_modules/native-base
<EMAIL_ADDRESS>from the root project

Could not resolve dependency:
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-dom
  peer react-dom@"*" from<EMAIL_ADDRESS>  node_modules/native-base
<EMAIL_ADDRESS>from the root project

Fix the upstream dependency conflict, or retry
this command with --force, or --legacy-peer-deps
to accept an incorrect (and potentially broken) dependency resolution.

Raw JSON explanation object:

{
  "code": "ERESOLVE",
  "current": {
    "name": "react",
    "version": "18.0.0",
    "whileInstalling": {
      "name": "******",
      "version": "1.0.0",
      "path": "C:\\Users\\user\\******\\******\\******"
    },
    "location": "node_modules/react",
    "isWorkspace": false,
    "dependents": [
      {
        "type": "prod",
        "name": "react",
        "spec": "18.0.0",
        "from": {
          "location": "C:\\Users\\user\\******\\******\\******"
        }
      },
      {
        "type": "peer",
        "name": "react",
        "spec": "*",
        "from": {
          "name": "native-base",
          "version": "3.4.16",
          "whileInstalling": {
            "name": "******",
            "version": "1.0.0",
            "path": "C:\\Users\\user\\******\\******\\******"
          },
          "location": "node_modules/native-base",
          "isWorkspace": false,
          "dependents": [
            {
              "type": "prod",
              "name": "native-base",
              "spec": "3.4.16",
              "from": {
                "location": "C:\\Users\\user\\******\\******\\******"
              }
            }
          ]
        }
      }
    ]
  },
  "currentEdge": {
    "type": "prod",
    "name": "react",
    "spec": "18.0.0",
    "from": {
      "location": "C:\\Users\\user\\******\\******\\******"
    }
  },
  "edge": {
    "type": "peer",
    "name": "react",
    "spec": "^18.2.0",
    "error": "INVALID",
    "from": {
      "name": "react-dom",
      "version": "18.2.0",
      "whileInstalling": {
        "name": "******",
        "version": "1.0.0",
        "path": "C:\\Users\\user\\******\\******\\******"
      },
      "location": "node_modules/react-dom",
      "isWorkspace": false,
      "dependents": [
        {
          "type": "peer",
          "name": "react-dom",
          "spec": "*",
          "from": {
            "name": "native-base",
            "version": "3.4.16",
            "whileInstalling": {
              "name": "******",
              "version": "1.0.0",
              "path": "C:\\Users\\user\\******\\******\\******"
            },
            "location": "node_modules/native-base",
            "isWorkspace": false,
            "dependents": [
              {
                "type": "prod",
                "name": "native-base",
                "spec": "3.4.16",
                "from": {
                  "location": "C:\\Users\\user\\******\\******\\******"
                }
              }
            ]
          }
        }
      ]
    }
  },
  "strictPeerDeps": false,
  "force": false
}

i starred all locations to keep it a secret but it gives out basically the project's location

Hi @R4Y-repo, we currently don't support  react@18 and expo 46.

Happening to me too. Please put a lot of effort into releasing a version that works with Expo 46.

Hi @R4Y-repo, we currently don't support  react@18 and expo 46. we are working on the fix.

I appreciate that, looking forward to use it in these versions.

#5266

@Viraj-10
when running: npx react-native init TSProject --template react-native-template-typescript
<EMAIL_ADDRESS>is installed
"dependencies": {
    "react": "18.1.0",
    "react-native": "0.70.3"
  },

So then when running: npm install native-base<EMAIL_ADDRESS><EMAIL_ADDRESS>We get a similar error as described above.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   peer react@"*" from<EMAIL_ADDRESS>npm ERR!   node_modules/native-base
npm ERR!     native-base@"*" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/react-dom
npm ERR!   peer react-dom@"*" from<EMAIL_ADDRESS>npm ERR!   node_modules/native-base
npm ERR!     native-base@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

@Viraj-10 Your MR has not solved the issue. When installing NativeBase 3.4.19, still the same errors:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   peer react@"*" from<EMAIL_ADDRESS>npm ERR!   node_modules/native-base
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/react-dom
npm ERR!   peer react-dom@"*" from<EMAIL_ADDRESS>npm ERR!   node_modules/native-base
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution

Hi, @nicolinho22 @hayate
I tried installing native-base in the expo project and I was able to do it.
Please follow the steps:-

nvm use v16.13.0.
expo init my-project choose the template JS/TS
cd my-project
npm install native-base
npx expo install<EMAIL_ADDRESS>npx expo install<EMAIL_ADDRESS>expo install<EMAIL_ADDRESS>(for web support).
npm start

if you still face an error please run npx native-base-info and comment the log here.

Hi, @nicolinho22 @hayate I tried installing native-base in the expo project and I was able to do it.
Please follow the steps:-

nvm use v16.13.0.
expo init my-project choose the template JS/TS
cd my-project
npm install native-base
npx expo install<EMAIL_ADDRESS>npx expo install<EMAIL_ADDRESS>expo install<EMAIL_ADDRESS>(for web support).
npm start

if you still face an error please run npx native-base-info and comment the log here.

 It wont work with a newer one?

Hi @nicolinho22, It's not a native-base Issue. Node version v16.13.0 have npm v8.1.0. Node 17 and above have npm v8.11 and above. for some reason it is mandatory to use --legacy-peer-deps or --force to install peerDependancies which are not an exact match from npm v8.5 and above. For more details, you can check the issue on npm CLI here.
As you can see in the error itself native-base has a * as a dependency so having react@18 shouldn't cause any error.

I had to add "react-dom": "18.0.0" to my package.json and then install as described in the docs.

Hi @rosc0, we are making react-dom optional peerDep. @proohit just added this PR. which will fix this issue.

Hi @Foohx, Thanks for sharing the logs seems like the issue is coming from react-native-aria. we will fix this warning soon.

Will anything bad happen if just install NativeBase with --legacy-peer-deps? Like encountering some weird edge cases that shouldn't have happened, etc.

Will anything bad happen if just install NativeBase with --legacy-peer-deps? Like encountering some weird edge cases that shouldn't have happened, etc.

It could and that's what installing without the flag is warning about: If the version of a (peer)dependency mismatches, the underlying library (native base in this case) might use functionality that's been patched/removed/altered. Either you carefully inspect changes via changelogs or live unknowingly.

I am getting this issue kindly help!!
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   peer react@"*" from<EMAIL_ADDRESS>npm ERR!   node_modules/native-base
npm ERR!     native-base@"*" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/react-dom
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   peer react-dom@"*" from<EMAIL_ADDRESS>npm ERR!   node_modules/native-base
npm ERR!     native-base@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

@Kashyap-Singh03 should be fixed when #5507 gets merged.

I am having similar logs with react 18.1

Hi, @nicolinho22 @hayate I tried installing native-base in the expo project and I was able to do it.
Please follow the steps:-

nvm use v16.13.0.
expo init my-project choose the template JS/TS
cd my-project
npm install native-base
npx expo install<EMAIL_ADDRESS>npx expo install<EMAIL_ADDRESS>expo install<EMAIL_ADDRESS>(for web support).
npm start

if you still face an error please run npx native-base-info and comment the log here.

I am having similar logs with react 18.1

Add the follow lines in your package.json file:
"overrides": {
    "react": "18.0.0"
  },

0 verbose cli /usr/local/share/nvm/versions/node/v19.5.0/bin/node /usr/local/share/nvm/versions/node/v19.5.0/lib/node_modules/npm/bin/npm-cli.js
1 info using<EMAIL_ADDRESS>2 info using<EMAIL_ADDRESS>3 timing npm:load:whichnode Completed in 4ms
4 timing config:load:defaults Completed in 4ms
5 timing config:load:file:/usr/local/share/nvm/versions/node/v19.5.0/lib/node_modules/npm/npmrc Completed in 13ms
6 timing config:load:builtin Completed in 14ms
7 timing config:load:cli Completed in 1ms
8 timing config:load:env Completed in 0ms
9 timing config:load:file:/workspaces/Interface.beauty/my-interface/.npmrc Completed in 0ms
10 timing config:load:project Completed in 6ms
11 timing config:load:file:/home/codespace/.npmrc Completed in 0ms
12 timing config:load:user Completed in 0ms
13 timing config:load:file:/usr/local/share/nvm/versions/node/v19.5.0/etc/npmrc Completed in 0ms
14 timing config:load:global Completed in 0ms
15 timing config:load:setEnvs Completed in 2ms
16 timing config:load Completed in 28ms
17 timing npm:load:configload Completed in 28ms
18 timing npm:load:mkdirpcache Completed in 0ms
19 timing npm:load:mkdirplogs Completed in 0ms
20 verbose title npm exec native-base-info
21 verbose argv "exec" "--" "native-base-info"
22 timing npm:load:setTitle Completed in 2ms
23 timing config:load:flatten Completed in 3ms
24 timing npm:load:display Completed in 4ms
25 verbose logfile logs-max:10 dir:/home/codespace/.npm/_logs/2023-02-11T19_58_43_331Z-
26 verbose logfile /home/codespace/.npm/_logs/2023-02-11T19_58_43_331Z-debug-0.log
27 timing npm:load:logFile Completed in 4ms
28 timing npm:load:timers Completed in 0ms
29 timing npm:load:configScope Completed in 0ms
30 timing npm:load Completed in 42ms
31 silly logfile start cleaning logs, removing 1 files
32 silly logfile done cleaning log files
33 timing arborist:ctor Completed in 1ms
34 timing command:exec Completed in 22ms
35 verbose stack Error: Override for<EMAIL_ADDRESS>conflicts with direct dependency
35 verbose stack     at Node.assertRootOverrides (/usr/local/share/nvm/versions/node/v19.5.0/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/node.js:1344:29)
35 verbose stack     at [loadActual] (/usr/local/share/nvm/versions/node/v19.5.0/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/load-actual.js:147:25)
35 verbose stack     at async exec (/usr/local/share/nvm/versions/node/v19.5.0/lib/node_modules/npm/node_modules/libnpmexec/lib/index.js:160:21)
35 verbose stack     at async module.exports (/usr/local/share/nvm/versions/node/v19.5.0/lib/node_modules/npm/lib/cli.js:134:5)
36 verbose cwd /workspaces/Interface.beauty/my-interface
37 verbose Linux 5.4.0-1101-azure
38 verbose node v19.5.0
39 verbose npm  v9.3.1
40 error code EOVERRIDE
41 error Override for<EMAIL_ADDRESS>conflicts with direct dependency
42 verbose exit 1
43 timing npm Completed in 83ms
44 verbose code 1
45 error A complete log of this run can be found in:
45 error     /home/codespace/.npm/_logs/2023-02-11T19_58_43_331Z-debug-0.log

Add the follow lines in your package.json file:
"overrides": {
    "react": "18.0.0"
  },

This is working for me, but can you explain little bit, what it does?

@rassemdev https://docs.npmjs.com/cli/v9/configuring-npm/package-json#overrides


filter out apple ld warnings about out of sync files

Closes #150
Linking against any framework spews benign "out of sync"
warnings with the latest command line tools, see

https://forums.developer.apple.com/thread/97850
https://openradar.appspot.com/45171575

LGTM

I hate that this is the best way to get rid of Apple's dumb spew, but I'll merge it anyway.


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 207 ms

Resolved: ClamAV performance has improved in c2cb6c2 after 6 minutes.


does not work.

🐛 Bug Report
something

something
I have docs full of kbd tags from v1 that used to work and now none of them work in v2. Any migration steps for kbd tags?
This does not work with "@docusaurus/core": "^2.0.0-alpha.54" I've tried remark plugins https://www.npmjs.com/package/remark-kbd it does not seem to help either :/

What does "won't work" mean? Doesn't appear or no styling added?

See the kitty section.

The markdown for that part is:
## kitty
- Increase font size: Ctrl++
- Decrease font size: Ctrl+-
- Input unicode: Ctrl+U

So that's just a different styling, not that it doesn't work. If you see, the styling is still present. It's unlikely we're gonna add the styling in, so for now you can add it into your own website.

@yangshun the markdown is not rendered aswell. What could be causing this.
[Link to post](LINK HERE)

I'd expect this to work without any styling.
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/kbd
eg. <button> tag works, why not

I'd expect this to work without any styling.

 is styled, just not the way GitHub does it. It's using monospaced font.

the markdown is not rendered aswell. What could be causing this

You can't mix JSX and Markdown on the same line. You can do this instead:

[my link](...)

and it should work

Thanks for the help @yangshun , I applied these styles and it seem to work as expected now. :)

I think we can stylize this tag in Infima if @yangshun doesn't mind?

I had it last time but I removed it because I felt that it was quite a rare use case. Idm adding it back I guess.


"Istria", "Nuntași" are listed in the drop-down menu

Description:
When user writes "Istria", "Nuntași" the location appears in the drop-down menu next to the comune and the county which is a part according to the law
Precondition:
The website is up an running.

Step 1
Write in the search bar "Istria"

Expected results
The location appears in the drop-down menu as "Sat Istria, CONSTANȚA, (Istria)"

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Nuntași"

Expected results
The location appears in the drop-down menu as "Sat Nuntași, CONSTANȚA, (Istria)"


Add soci --version to get the CLI version

Issue #, if available:
Closes https://github.com/awslabs/soci-snapshotter/issues/477
Description of changes:
This change adds a soci --version flag to match soci-snapshotter-grpc --version.
Since urfave has a specific output format, soci-snapshotter-grpc was updated to match it. The new version format is:
$BINARY_NAME version $TAG $COMMIT
Testing performed:
$ ./out/soci --version
soci version 303d3db 303d3dbc7ea16376d77ba5279426b9139a147e0b
$ ./out/soci-snapshotter-grpc --version
soci-snapshotter-grpc version 303d3db 303d3dbc7ea16376d77ba5279426b9139a147e0b

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Can you test/confirm this works with a tag, such as a release version?

@sparr as an example:
$ git tag v0.1.1
$ make
$ ./out/soci --version
soci version v0.1.1 303d3dbc7ea16376d77ba5279426b9139a147e0b
$ ./out/soci-snapshotter-grpc --version
soci-snapshotter-grpc version v0.1.1 303d3dbc7ea16376d77ba5279426b9139a147e0b
$ git tag -d v0.1.1

maybe later we want to have separate server(daemon)/client(soci) versions, similar to containerd.

This could make sense, but you don't actually need to run the SOCI snapshotter in order to create SOCI indices and currently the CLI doesn't talk directly to the snapshotter. Maybe we can do that opportunistically if the snapshotter is available. I'll create an issue.

This could make sense, but you don't actually need to run the SOCI snapshotter in order to create SOCI indices and currently the CLI doesn't talk directly to the snapshotter. Maybe we can do that opportunistically if the snapshotter is available. I'll create an issue.

It's just for convenience and makes debug easier. Otherwise if a user has issue, we'll ask "can you provide output of soci --version AND soci-snapshotter-grpc --version.
We can make the cli to ignore snapshotter version if it's not running, and print if it's. An easy way might be just something like os.Exec("soci-snapshotter-grpc", "--version") (and ignore err if it doesn't exist).
As a smilar example, kubectl version just prints server: error .... when there isn't a k8s it can talk to. (I didn't try ctr)


Increase minimum password requirement

Solved with this commit:
https://github.com/rohsaurus/Cerberus/commit/5e9327e31471942c1d31ada49be79f4ab39ecc5b


Create and change organization icon

Create and change organization icon.

+1

:+1:

Nice, I will change project icon asap. :smiley:

Great work @gitarno. Done.


SAMP server can not load FCNPC for some unknown reason

Hi ! I get this error while loading FCNPC.dll :
I've installed MS VR C++ 2015 and older versions but not fixed!
---------------------------
samp-server.exe - Entry Point Not Found
---------------------------
The procedure entry point K32GetModuleInformation could not be located in the dynamic link library KERNEL32.dll.
---------------------------
OK
---------------------------

My server host OS is Windows Server 2008

It's loads without FCNPC (show logs)? Is main() {} exists in your code?
On Feb 9, 2018 14:13, "AmyrAhmady"<EMAIL_ADDRESS>wrote:

Hi ! I get this error while loading FCNPC.dll :
I've installed MS VR C++ 2015 and older versions but not fixed!

samp-server.exe - Entry Point Not Found
The procedure entry point K32GetModuleInformation could not be located in the dynamic link library KERNEL32.dll.
OK
My server host OS is Windows Server 2008
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ziggi/FCNPC/issues/129, or mute the thread
https://github.com/notifications/unsubscribe-auth/AA-QwyxQz1JO6W9GuCxEHmZst1yBb5H_ks5tTChogaJpZM4R_xRa
.

samp server won't crash just FCNPC get failed in loading..
and yes main() exist however it isn't related to script because it happens before loading gamemode , just a windows error like this :
http://i62.tinypic.com/k4xftv.jpg

Try to install VC++ Redistributable 2017 too.
On Feb 9, 2018 14:58, "AmyrAhmady"<EMAIL_ADDRESS>wrote:

samp server won't crash just FCNPC get failed in loading..
and yes main() exist however it isn't related to script because it happens
before loading gamemode , just a windows error like this :
http://i62.tinypic.com/k4xftv.jpg
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ziggi/FCNPC/issues/129#issuecomment-364414953, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA-QwxyN5UTpLbJJRH4HNb13fd9VVnqQks5tTDLmgaJpZM4R_xRa
.

Tried right now , still the same...

Can you try to install all updates for your server OS?

Nope , my server hosting provider doesn't let me to update , it is disabled by default

I even used FCNPC v1.0.0 , it doesn't work neigther

Maybe it's in Psapi.dll ?
Try that dll I sent to you.

Can you please specify OS, Build and architecture?

Out of date


Jump and slider functionality don't work.

# Environment:

Windows 10 Pro
Chrome 65.0.3325.146
Angular cli 1.7.2
ngrx/store: 5.2.0
ngrx/store-devtools: 5.2.0
Redux DevTools Chrome extension 2.15.2

# Problem:
When i fire actions, it is fine which shows the states but if i try to slide or jump to any state, it only shows the last state ( in my opinion ) or it does not work anymore.

this is the wrong repository. So i'm closing it.


nmdc-schema 7.6.0 -> 7.6.2

@turbomam is schema still on 7.6.2? I assume this is to migrate the submission schema to reference the correct schema version?

this is done. see https://github.com/microbiomedata/submission-schema/blob/main/sheets_and_friends/tsv_in/import_slots_regardless.tsv
10.2 is current


Allow in-game touchpad locomotion

Make it possible for the user to emulate movement based on HTC Vive touchpads.

Solved via VRTK/Touchpad in future. Closing.


[SMALLFIX][branch-1.5] Fix the write permission issue when formatting worker folder

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/16326/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/16327/
Test PASSed.


Update fails for entities with DatabaseGeneratedOption.Computed attribute

OrmConventions.cs:
Missing call to propertyMapping.ExcludeFromInserts().ExcludeFromUpdates();  for Computed option as well, otherwise the Update, Insert commands fail.
if (databaseGeneratedAttributes.Any(dbGenerated => dbGenerated.DatabaseGeneratedOption == DatabaseGeneratedOption.Computed))
{
     propertyMapping.SetDatabaseGenerated();
}
if (databaseGeneratedAttributes.Any(dbGenerated => dbGenerated.DatabaseGeneratedOption == DatabaseGeneratedOption.Identity))
{
      propertyMapping.SetDatabaseGenerated();
      propertyMapping.ExcludeFromInserts().ExcludeFromUpdates();
}

A bit confusing I agree, but if you go further deeper into the code you'll realize that database generated properties are going to be ignored from inserts by default.
        public bool IsDatabaseGenerated
        {
            get
            {
                return (_options & PropertyMappingOptions.DatabaseGeneratedProperty) == PropertyMappingOptions.DatabaseGeneratedProperty;
            }
            set
            {
                this.ValidateState();

                if (value)
                {
                    _options |= PropertyMappingOptions.DatabaseGeneratedProperty;
                    this.IsExcludedFromInserts = true;
                }
                else
                {
                    _options &= ~PropertyMappingOptions.DatabaseGeneratedProperty;
                }
            }
        }

        public PropertyMapping SetDatabaseGenerated(bool isDatabaseGenerated = true)
        {
            this.IsDatabaseGenerated = isDatabaseGenerated;
            return this;
        }

You'll notice that we've got a bunch of tests having a GUID having a default value generated by the DB on INSERT but updated on UPDATE.
At the moment, neither of the DatabaseGenerationOption enum values can be used to ignore a non-key property from an UPDATE. I suppose we should be following the MSDN docs. We'll need to update the T4 template as well.
Until then, you could override the default library conventions.

Hi MoonStorm, thank you for the reply.  Can you please check my code in this StackOverview question?  I am the developer having this problem:
http://stackoverflow.com/questions/34537729/databasegeneratedoption-doesnt-work-in-dapper-fastcrud

I MoonStorm.  We tried to debug locally and it turn out in "public bool IsDatabaseGenerated", there still isn't anything for update.   Here is 2 potential fix:
public bool IsDatabaseGenerated
    {
        get
        {
            return (_options & PropertyMappingOptions.DatabaseGeneratedProperty) == PropertyMappingOptions.DatabaseGeneratedProperty;
        }
        set
        {
            this.ValidateState();

            if (value)
            {
                _options |= PropertyMappingOptions.DatabaseGeneratedProperty;
                this.IsExcludedFromInserts = true;
                this.IsExcludedFromUpdates = true;  // Add This Line
            }
            else
            {
                _options &= ~PropertyMappingOptions.DatabaseGeneratedProperty;
            }
        }
    }

    public PropertyMapping SetDatabaseGenerated(bool isDatabaseGenerated = true)
    {
        this.IsDatabaseGenerated = isDatabaseGenerated;
        return this;
    }

Alternatively, we could also fix it here:
    public virtual void ConfigureEntityPropertyMapping(PropertyMapping propertyMapping)
    {
        ... ....
        if (databaseGeneratedAttributes.Any(dbGenerated => dbGenerated.DatabaseGeneratedOption == DatabaseGeneratedOption.Computed))
        {
            propertyMapping.SetDatabaseGenerated();
            propertyMapping.ExcludeFromInserts().ExcludeFromUpdates(); // Add This Line
        }

        if (databaseGeneratedAttributes.Any(dbGenerated => dbGenerated.DatabaseGeneratedOption == DatabaseGeneratedOption.Identity))
        {
            propertyMapping.SetDatabaseGenerated();
            propertyMapping.ExcludeFromInserts().ExcludeFromUpdates();
        }
        ... ....
   }

Fixed and released in 2.3.0. This version introduced breaking changes in order to align with the MSDN docs. Please check the updated wiki for more details.

Thank you so much for the quick fix, I will check it out next Monday ASAP.

I checked it out and it works well!  Thanks a lot!

Glad to hear that. Let me know if you encounter any more problems. Thanks.


Add OrderUpdates websocket subscription

Adds the implementation for the orderUpdate websocket
Tested against the testnet

@lmlmt I don't have write access, but this should be g2g


Middle click drag scroll function idea

Hi
Would it be possible to implement something like this: when you hold middle-click (on it's own or with a modifier key) and move around it scrolls the document in all directions.

It's possible but I haven't found a good reason to implement it, there are also some issues because it conflicts with other gestures. Here's a comment regarding that issue. I'll close this issue because it's duplicated, we can continue the conversation here. I'm open to discuss for a solution that's good enough for all the use cases.


Toggle completion menu

This pr gives the user the ablity to hide all the cmp, windows without closing cmp
by attaching an empty buffer to the windows and setting winblend to 100.
Making get_buffer return a back-buffer.
Views can write/highlight to the back-buffer while the empty buffer is being shown to the user
fixes:
https://github.com/hrsh7th/nvim-cmp/issues/1698
https://github.com/hrsh7th/nvim-cmp/issues/1013

Would love to see this merged.

This still needs documentation, but i am not sure if the current config interface is good, i added 2 options.
window = {
      auto_hide = false,
      show_on_cursor_update = false,
}

auto_hide hides the windows after they opened until require('cmp.utils.window').show_all() is called or when the cursor moves in the menu if show_on_cursor_update is true.
However show_on_cursor_update doesn't work well because the cursor doesn't move with a pre-selected item,

Thanks for the work on this branch, I've been using it for a couple of months and forgot to check if it got merged in but it looks like it hasn't. Would it be possible to get this reviewed and merged in? Might need more work since it looks like it has merge conflicts and not sure if the creator of the branch is still around but if they're not I can clean up any issues and resubmit. Thank you.

not sure if the creator of the branch is still around but if they're not I can clean up any issues

I am still here, but I don't plan to work on this pr anymore because I don't use cmp anymore. Sorry.