How to monitor File Share capacity?

Hi,
When you use Azure File Shares it would be pretty nice to be able to get an alert before a share is completely full. As far as I can figure out this is not really possible at the moment. The nearest solution I can see is to only have one Share per Storage account and then create an Azure Monitor alert using "Whenever the average file capacity is greater than XYZ bytes". I have not been able to figure out what average means though...
Anyway, is it correct that there is no way to monitor a file shares capacity?
Regards Peter

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

ID: 63c3effd-7cc3-f021-358a-adeaf59a0a69
Version Independent ID: 36381f6b-f57b-95a2-67cd-80bffcee238c
Content: Monitoring Azure Storage
Content Source: articles/storage/common/monitor-storage.md
Service: storage
GitHub Login: @normesta
Microsoft Alias: normesta

@theheatDK Thanks for the question. We are looking into this and will get back to you shortly.

@theheatDK  Firstly Apologies for delay in responding here!
Based on your scenario you may refer to the suggestion mentioned in this SO thread
This MSDN thread will provide different ways to check Azure file share capacity
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Model, hook bug fixed #208

add model hooks will has to append current classname as prefix now.
previous
$this->di->hook("model.after.update", function(){ });

now
$this->di->hook("model.after.update." . static::class, function(){ });

this pr is not a thoroughly solution. closed


neon/mla_lane: initial implementation using mla+dup

Thank you @ngzhian !
MSVC doesn't like it when we combine CONSTIFY and macro defined functions, so I added a workaround and queued this up for merge in 0b593ce


[Task]: replace findDatabase in Transform vertica bulk loader

What needs to happen?
replace findDatabase in Transform vertica bulk loader
Issue Priority
Priority: 3
Issue Component
Component: Database, Component: Transforms

Merge pull request https://github.com/apache/hop/pull/2864


My tests only pass when I enable "debug with chrome"

What happened?
I have a very small test suite which used to run and pass. However, recently the tests have stopped passing. After considerable investigation I figured out that if I run the tests, wait for the app to load, trigger the shake gesture (open dev menu), and then tap "debug with chrome" the individual test will suddenly pass. I've disabled flipper, however that hasn't changed anything.
Before I tap "debug with chrome", I see messages over and over about a timer:
12:59:19.717 detox[76569] INFO:  [APP_STATUS] The app is busy with the following tasks:
• There are 1 work items pending on the dispatch queue: "Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)".
• 1 enqueued JavaScript timers:
  - Timer #1:
    + JS timer ID: 786.
    + Duration: 0.05.
    + Is recurring: NO.
• Run loop "Main Run Loop" is awake.

I'm not sure how to figure out what is setting this timer, and I am further confused by the fact that connecting the chrome debugger suddenly allows the test to complete.
What was the expected behaviour?
The tests to pass without manually tapping "debug with chrome" for each test.
Was it tested on latest Detox?

[X] I have tested this issue on the latest Detox release and it still reproduces.

Did your test throw out a timeout?

[X] I have followed the instructions under Identifying which synchronization mechanism causes us to wait too much.

Help us reproduce this issue!
No response
In what environment did this happen?
Detox version: 19.4.5
React Native version: 0.64.2
Node version: 14.18.0
Device model: iPhone 13
iOS version: 15.2
macOS version: 12.2.1
Xcode version: 13.2.1
Test-runner (select one): jest-circus
Detox logs
Detox logs
13:15:11.650 detox[77975] INFO:  [AppleSimUtils.js] com.joinpapa.papapal launched.
• There are 1 work items pending on the dispatch queue: "Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)".
• 1 enqueued JavaScript timers:
  - Timer #1:
    + JS timer ID: 774.
    + Duration: 0.05.
    + Is recurring: NO.
13:15:32.920 detox[77975] TRACE: [WS_SEND] {"type":"currentStatus","params":{},"messageId":2}
13:15:32.920 detox[77975] TRACE: [WSS_GET_FROM, #tester] {"type":"currentStatus","params":{},"messageId":2}
13:15:32.920 detox[77975] TRACE: [WSS_SEND_TO, #app] {"type":"currentStatus","params":{},"messageId":2}
13:15:32.922 detox[77975] TRACE: [WSS_GET_FROM, #app] {"type":"currentStatusResult","messageId":2,"params":{"messageId":2,"status":{"busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":936,"duration":0.050000000000000003}]}}],"app_status":"busy"}}}
13:15:32.922 detox[77975] TRACE: [WSS_SEND_TO, #tester] {"type":"currentStatusResult","messageId":2,"params":{"messageId":2,"status":{"busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":936,"duration":0.05}]}}],"app_status":"busy"}}}
13:15:32.922 detox[77975] TRACE: [WS_MESSAGE] {"type":"currentStatusResult","messageId":2,"params":{"messageId":2,"status":{"busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":936,"duration":0.05}]}}],"app_status":"busy"}}}

13:15:32.922 detox[77975] INFO:  [APP_STATUS] The app is busy with the following tasks:
• Run loop "Main Run Loop" is awake.
• There are 1 work items pending on the dispatch queue: "Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)".
• 1 enqueued JavaScript timers:
  - Timer #1:
    + JS timer ID: 936.
    + Duration: 0.05.
    + Is recurring: NO.
13:15:42.923 detox[77975] TRACE: [WS_SEND] {"type":"currentStatus","params":{},"messageId":3}
13:15:42.923 detox[77975] TRACE: [WSS_GET_FROM, #tester] {"type":"currentStatus","params":{},"messageId":3}
13:15:42.924 detox[77975] TRACE: [WSS_SEND_TO, #app] {"type":"currentStatus","params":{},"messageId":3}
13:15:42.925 detox[77975] TRACE: [WSS_GET_FROM, #app] {"type":"currentStatusResult","params":{"status":{"busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":1114,"duration":0.050000000000000003}]}}],"app_status":"busy"},"messageId":3},"messageId":3}
13:15:42.925 detox[77975] TRACE: [WSS_SEND_TO, #tester] {"type":"currentStatusResult","params":{"status":{"busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":1114,"duration":0.05}]}}],"app_status":"busy"},"messageId":3},"messageId":3}
13:15:42.925 detox[77975] TRACE: [WS_MESSAGE] {"type":"currentStatusResult","params":{"status":{"busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":1114,"duration":0.05}]}}],"app_status":"busy"},"messageId":3},"messageId":3}

13:15:42.925 detox[77975] INFO:  [APP_STATUS] The app is busy with the following tasks:
• Run loop "Main Run Loop" is awake.
• There are 1 work items pending on the dispatch queue: "Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)".
• 1 enqueued JavaScript timers:
  - Timer #1:
    + JS timer ID: 1114.
    + Duration: 0.05.
    + Is recurring: NO.
13:15:52.927 detox[77975] TRACE: [WS_SEND] {"type":"currentStatus","params":{},"messageId":4}
13:15:52.927 detox[77975] TRACE: [WSS_GET_FROM, #tester] {"type":"currentStatus","params":{},"messageId":4}
13:15:52.928 detox[77975] TRACE: [WSS_SEND_TO, #app] {"type":"currentStatus","params":{},"messageId":4}
13:15:52.929 detox[77975] TRACE: [WSS_GET_FROM, #app] {"type":"currentStatusResult","params":{"status":{"busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":1293,"duration":0.050000000000000003}]}}],"app_status":"busy"},"messageId":4},"messageId":4}
13:15:52.929 detox[77975] TRACE: [WSS_SEND_TO, #tester] {"type":"currentStatusResult","params":{"status":{"busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":1293,"duration":0.05}]}}],"app_status":"busy"},"messageId":4},"messageId":4}
13:15:52.929 detox[77975] TRACE: [WS_MESSAGE] {"type":"currentStatusResult","params":{"status":{"busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":1293,"duration":0.05}]}}],"app_status":"busy"},"messageId":4},"messageId":4}

13:15:52.930 detox[77975] INFO:  [APP_STATUS] The app is busy with the following tasks:
• Run loop "Main Run Loop" is awake.
• There are 1 work items pending on the dispatch queue: "Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)".
• 1 enqueued JavaScript timers:
  - Timer #1:
    + JS timer ID: 1293.
    + Duration: 0.05.
    + Is recurring: NO.

Device logs
Device logs
Mar 2 13:27:37 detox[79085] TRACE: [WS_SEND] {"type":"currentStatus","params":{},"messageId":25}
Mar 2 13:27:37 detox[79085] TRACE: [WSS_GET_FROM, #tester] {"type":"currentStatus","params":{},"messageId":25}
Mar 2 13:27:37 detox[79085] TRACE: [WSS_SEND_TO, #app] {"type":"currentStatus","params":{},"messageId":25}
Mar 2 13:27:37 detox[79085] TRACE: [WSS_GET_FROM, #app] {"params":{"status":{"busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":4791,"duration":0.050000000000000003}]}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}}],"app_status":"busy"},"messageId":25},"messageId":25,"type":"currentStatusResult"}
Mar 2 13:27:37 detox[79085] TRACE: [WSS_SEND_TO, #tester] {"params":{"status":{"busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":4791,"duration":0.05}]}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}}],"app_status":"busy"},"messageId":25},"messageId":25,"type":"currentStatusResult"}
Mar 2 13:27:37 detox[79085] TRACE: [WS_MESSAGE] {"params":{"status":{"busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":4791,"duration":0.05}]}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}}],"app_status":"busy"},"messageId":25},"messageId":25,"type":"currentStatusResult"}

Mar 2 13:27:37 detox[79085] INFO:  [APP_STATUS] The app is busy with the following tasks:
• Run loop "Main Run Loop" is awake.
• 1 enqueued JavaScript timers:
  - Timer #1:
    + JS timer ID: 4791.
    + Duration: 0.05.
    + Is recurring: NO.
• There are 1 work items pending on the dispatch queue: "Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)".
Mar 2 13:27:47 detox[79085] TRACE: [WS_SEND] {"type":"currentStatus","params":{},"messageId":26}
Mar 2 13:27:47 detox[79085] TRACE: [WSS_GET_FROM, #tester] {"type":"currentStatus","params":{},"messageId":26}
Mar 2 13:27:47 detox[79085] TRACE: [WSS_SEND_TO, #app] {"type":"currentStatus","params":{},"messageId":26}
Mar 2 13:27:47 detox[79085] TRACE: [WSS_GET_FROM, #app] {"type":"currentStatusResult","params":{"status":{"busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":4955,"duration":0.050000000000000003}]}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}}],"app_status":"busy"},"messageId":26},"messageId":26}
Mar 2 13:27:47 detox[79085] TRACE: [WSS_SEND_TO, #tester] {"type":"currentStatusResult","params":{"status":{"busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":4955,"duration":0.05}]}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}}],"app_status":"busy"},"messageId":26},"messageId":26}
Mar 2 13:27:47 detox[79085] TRACE: [WS_MESSAGE] {"type":"currentStatusResult","params":{"status":{"busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":4955,"duration":0.05}]}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}}],"app_status":"busy"},"messageId":26},"messageId":26}

Mar 2 13:27:47 detox[79085] INFO:  [APP_STATUS] The app is busy with the following tasks:
• Run loop "Main Run Loop" is awake.
• 1 enqueued JavaScript timers:
  - Timer #1:
    + JS timer ID: 4955.
    + Duration: 0.05.
    + Is recurring: NO.
• There are 1 work items pending on the dispatch queue: "Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)".
Mar 2 13:27:57 detox[79085] TRACE: [WS_SEND] {"type":"currentStatus","params":{},"messageId":27}
Mar 2 13:27:57 detox[79085] TRACE: [WSS_GET_FROM, #tester] {"type":"currentStatus","params":{},"messageId":27}
Mar 2 13:27:57 detox[79085] TRACE: [WSS_SEND_TO, #app] {"type":"currentStatus","params":{},"messageId":27}
Mar 2 13:27:57 detox[79085] TRACE: [WSS_GET_FROM, #app] {"messageId":27,"params":{"messageId":27,"status":{"busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":5119,"duration":0.050000000000000003}]}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}}],"app_status":"busy"}},"type":"currentStatusResult"}
Mar 2 13:27:57 detox[79085] TRACE: [WSS_SEND_TO, #tester] {"messageId":27,"params":{"messageId":27,"status":{"busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":5119,"duration":0.05}]}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}}],"app_status":"busy"}},"type":"currentStatusResult"}
Mar 2 13:27:57 detox[79085] TRACE: [WS_MESSAGE] {"messageId":27,"params":{"messageId":27,"status":{"busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":5119,"duration":0.05}]}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}}],"app_status":"busy"}},"type":"currentStatusResult"}

Mar 2 13:27:57 detox[79085] INFO:  [APP_STATUS] The app is busy with the following tasks:
• Run loop "Main Run Loop" is awake.
• 1 enqueued JavaScript timers:
  - Timer #1:
    + JS timer ID: 5119.
    + Duration: 0.05.
    + Is recurring: NO.
• There are 1 work items pending on the dispatch queue: "Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)".
Mar 2 13:28:07 detox[79085] TRACE: [WS_SEND] {"type":"currentStatus","params":{},"messageId":28}
Mar 2 13:28:07 detox[79085] TRACE: [WSS_GET_FROM, #tester] {"type":"currentStatus","params":{},"messageId":28}
Mar 2 13:28:07 detox[79085] TRACE: [WSS_SEND_TO, #app] {"type":"currentStatus","params":{},"messageId":28}
Mar 2 13:28:07 detox[79085] TRACE: [WSS_GET_FROM, #app] {"params":{"status":{"busy_resources":[{"name":"run_loop","description":{"name":"JS Run Loop"}},{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":5279,"duration":0.050000000000000003}]}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}}],"app_status":"busy"},"messageId":28},"messageId":28,"type":"currentStatusResult"}
Mar 2 13:28:07 detox[79085] TRACE: [WSS_SEND_TO, #tester] {"params":{"status":{"busy_resources":[{"name":"run_loop","description":{"name":"JS Run Loop"}},{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":5279,"duration":0.05}]}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}}],"app_status":"busy"},"messageId":28},"messageId":28,"type":"currentStatusResult"}
Mar 2 13:28:07 detox[79085] TRACE: [WS_MESSAGE] {"params":{"status":{"busy_resources":[{"name":"run_loop","description":{"name":"JS Run Loop"}},{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":5279,"duration":0.05}]}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}}],"app_status":"busy"},"messageId":28},"messageId":28,"type":"currentStatusResult"}

Mar 2 13:28:07 detox[79085] INFO:  [APP_STATUS] The app is busy with the following tasks:
• Run loop "JS Run Loop" is awake.
• Run loop "Main Run Loop" is awake.
• 1 enqueued JavaScript timers:
  - Timer #1:
    + JS timer ID: 5279.
    + Duration: 0.05.
    + Is recurring: NO.
• There are 1 work items pending on the dispatch queue: "Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)".
Mar 2 13:28:17 detox[79085] TRACE: [WS_SEND] {"type":"currentStatus","params":{},"messageId":29}
Mar 2 13:28:17 detox[79085] TRACE: [WSS_GET_FROM, #tester] {"type":"currentStatus","params":{},"messageId":29}
Mar 2 13:28:17 detox[79085] TRACE: [WSS_SEND_TO, #app] {"type":"currentStatus","params":{},"messageId":29}
Mar 2 13:28:17 detox[79085] TRACE: [WSS_GET_FROM, #app] {"messageId":29,"type":"currentStatusResult","params":{"messageId":29,"status":{"busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":5447,"duration":0.050000000000000003}]}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}}],"app_status":"busy"}}}
Mar 2 13:28:17 detox[79085] TRACE: [WSS_SEND_TO, #tester] {"messageId":29,"type":"currentStatusResult","params":{"messageId":29,"status":{"busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":5447,"duration":0.05}]}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}}],"app_status":"busy"}}}
Mar 2 13:28:17 detox[79085] TRACE: [WS_MESSAGE] {"messageId":29,"type":"currentStatusResult","params":{"messageId":29,"status":{"busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":5447,"duration":0.05}]}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}}],"app_status":"busy"}}}

Mar 2 13:28:17 detox[79085] INFO:  [APP_STATUS] The app is busy with the following tasks:
• Run loop "Main Run Loop" is awake.
• 1 enqueued JavaScript timers:
  - Timer #1:
    + JS timer ID: 5447.
    + Duration: 0.05.
    + Is recurring: NO.
• There are 1 work items pending on the dispatch queue: "Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)".
Mar 2 13:28:27 detox[79085] TRACE: [WS_SEND] {"type":"currentStatus","params":{},"messageId":30}
Mar 2 13:28:27 detox[79085] TRACE: [WSS_GET_FROM, #tester] {"type":"currentStatus","params":{},"messageId":30}
Mar 2 13:28:27 detox[79085] TRACE: [WSS_SEND_TO, #app] {"type":"currentStatus","params":{},"messageId":30}
Mar 2 13:28:27 detox[79085] TRACE: [WSS_GET_FROM, #app] {"messageId":30,"type":"currentStatusResult","params":{"messageId":30,"status":{"busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":5611,"duration":0.050000000000000003}]}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}}],"app_status":"busy"}}}
Mar 2 13:28:27 detox[79085] TRACE: [WSS_SEND_TO, #tester] {"messageId":30,"type":"currentStatusResult","params":{"messageId":30,"status":{"busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":5611,"duration":0.05}]}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}}],"app_status":"busy"}}}
Mar 2 13:28:27 detox[79085] TRACE: [WS_MESSAGE] {"messageId":30,"type":"currentStatusResult","params":{"messageId":30,"status":{"busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":5611,"duration":0.05}]}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}}],"app_status":"busy"}}}

Mar 2 13:28:27 detox[79085] INFO:  [APP_STATUS] The app is busy with the following tasks:
• Run loop "Main Run Loop" is awake.
• 1 enqueued JavaScript timers:
  - Timer #1:
    + JS timer ID: 5611.
    + Duration: 0.05.
    + Is recurring: NO.
• There are 1 work items pending on the dispatch queue: "Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)".
Mar 2 13:28:37 detox[79085] TRACE: [WS_SEND] {"type":"currentStatus","params":{},"messageId":31}
Mar 2 13:28:37 detox[79085] TRACE: [WSS_GET_FROM, #tester] {"type":"currentStatus","params":{},"messageId":31}
Mar 2 13:28:37 detox[79085] TRACE: [WSS_SEND_TO, #app] {"type":"currentStatus","params":{},"messageId":31}
Mar 2 13:28:37 detox[79085] TRACE: [WSS_GET_FROM, #app] {"messageId":31,"type":"currentStatusResult","params":{"status":{"app_status":"busy","busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":5787,"duration":0.050000000000000003}]}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}}]},"messageId":31}}
Mar 2 13:28:37 detox[79085] TRACE: [WSS_SEND_TO, #tester] {"messageId":31,"type":"currentStatusResult","params":{"status":{"app_status":"busy","busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":5787,"duration":0.05}]}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}}]},"messageId":31}}
Mar 2 13:28:37 detox[79085] TRACE: [WS_MESSAGE] {"messageId":31,"type":"currentStatusResult","params":{"status":{"app_status":"busy","busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":5787,"duration":0.05}]}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}}]},"messageId":31}}

Mar 2 13:28:37 detox[79085] INFO:  [APP_STATUS] The app is busy with the following tasks:
• Run loop "Main Run Loop" is awake.
• 1 enqueued JavaScript timers:
  - Timer #1:
    + JS timer ID: 5787.
    + Duration: 0.05.
    + Is recurring: NO.
• There are 1 work items pending on the dispatch queue: "Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)".
Mar 2 13:28:47 detox[79085] TRACE: [WS_SEND] {"type":"currentStatus","params":{},"messageId":32}
Mar 2 13:28:47 detox[79085] TRACE: [WSS_GET_FROM, #tester] {"type":"currentStatus","params":{},"messageId":32}
Mar 2 13:28:47 detox[79085] TRACE: [WSS_SEND_TO, #app] {"type":"currentStatus","params":{},"messageId":32}
Mar 2 13:28:47 detox[79085] TRACE: [WSS_GET_FROM, #app] {"params":{"messageId":32,"status":{"busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":5953,"duration":0.050000000000000003}]}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}}],"app_status":"busy"}},"type":"currentStatusResult","messageId":32}
Mar 2 13:28:47 detox[79085] TRACE: [WSS_SEND_TO, #tester] {"params":{"messageId":32,"status":{"busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":5953,"duration":0.05}]}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}}],"app_status":"busy"}},"type":"currentStatusResult","messageId":32}
Mar 2 13:28:47 detox[79085] TRACE: [WS_MESSAGE] {"params":{"messageId":32,"status":{"busy_resources":[{"name":"run_loop","description":{"name":"Main Run Loop"}},{"name":"js_timers","description":{"timers":[{"is_recurring":false,"timer_id":5953,"duration":0.05}]}},{"name":"dispatch_queue","description":{"queue":"Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)","works_count":1}}],"app_status":"busy"}},"type":"currentStatusResult","messageId":32}

Mar 2 13:28:47 detox[79085] INFO:  [APP_STATUS] The app is busy with the following tasks:
• Run loop "Main Run Loop" is awake.
• 1 enqueued JavaScript timers:
  - Timer #1:
    + JS timer ID: 5953.
    + Duration: 0.05.
    + Is recurring: NO.
• There are 1 work items pending on the dispatch queue: "Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)".

More data, please!
No response

Hey there, thanks for reaching out. I think the chrome debugging thing sort out distracts you from the real issue.
Could you rerun your tests in release mode (i.e. JS code bundled into the app + no metro-server running in the backgroun)?

Thanks for the reply. I've tried running the app with the release configuration, and unfortunately the problem still exists. I was mostly hoping someone here might have some insight into how best to track down what might be creating the timer. We don't have any of this type of timer being created by our own code, so I'd suspect some dependency of ours. Unfortunately a lot has changed since the last time we worked on these tests. We have the bandwidth now to work on our end-to-end testing efforts, however I'm unable to move forward because of this issue.
I know this isn't an issue in Detox, but any advice here would be greatly appreciated.
btw, the tests pass when attaching to any debugger (not just the chrome one). I was hoping this might be a clue that would point to some known issue with some library or something. Anyway, I'll keep digging. Thanks for your reply and for all the hard work :)

@papa-jake
thanks for pasting this here!
I am indeed experiencing the same problem, but cant fix it.
In the above snippet you wrote GLOBAL ... is this a typo? should this be global? Because uppercase global will be undefined.. but lowercase does not seem to work.
Thanks!

For reference, here's the related issue on the Sentry side: https://github.com/getsentry/sentry-react-native/issues/1921


Bypass invalid SSL-checks for Nswag CLI / MsBuild

We're using  NSwag.MSBuild as part of our build process to update and generate clients from OpenAPI specs before building new versions.
Some of these OAPI specs are published on servers using self signed SSL-certs (test/dev servers). This breaks our build process as Nswag CLI currently cant bypass SSL checks and fails with:

Executing file 'generation/dto.nswag' with variables 'Configuration=Debug'...
System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception.
---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.

This was fixed for Nswag studio here https://github.com/RicoSuter/NJsonSchema/issues/908 - any chance of enabling an optional SSL bypass for CLI aswell?

I'm not very keen on disabling security... as a workaround you can download the file outside of the CLI for now (e.g. via powershell) and pass it in via relative path.
What do you think @jeremyVignelles?

I'm not in favor of an "disable SSL checks" option, but open for a "select certificate" option.
Advanced scenarios might want to download the file as you suggested, but I don't know if there is any difference between a local json file and a file downloaded by NSwag directly

I'm not in favor of an "disable SSL checks" option, but open for a "select certificate" option.

If this was an optional parameter (disabled by default) would this still be a security problem? Similar to @RasmusWesterlundh we have multiple test/dev systems that use self-signed certificates, and being able to just bypass certificate validation would be easier than having to select certificates for each

I'm not in favor of...

Sure, whatever. Unfortunately it is not yet that straightforward to make everyone "trust" dotnet certificates on local environment on Linux. I went with one of the solutions and put necessary files in ~/.pki/nssdb. So my browser is not making problems.
How do I force NSwag CLI to use the same information and trust my self-signed certificate?

@RasmusWesterlundh @J-Sek did either of you find a solution/workaround to this.
We've just changed our app to use WebApplication.CreateBuilder and now experiencing this

did either of you find a solution/workaround to this.

chrome://flags » Allow invalid certificates for resources loaded from localhost.
...and you only need to ignore red "Not secure" in the address bar

Chrome flags aren't going to help in the nswag CLI

Chrome flags aren't going to help in the nswag CLI

Oh.. yeah, sorry. It's been a while and I forgot that this problem has 2 layers.
You can check my [notes](](https://gist.github.com/J-Sek/96f432ea5d7e2222b5f270b81cd9cadf) I follow every time I setup new environment.


docs: add CLI docs under tools content bucket

This Pull Request creates the AsyncAPI CLI content under the Tools content bucket by re-writing and editing what is currently in the CLI readME docs. This resolves issue #1078

Alrighty, review is done and you can work on Draft 2 now ✨✨

Thanks for the review @alequetzalli. I will work on the recommendations.

@derberg @alequetzalli all reviews have been implemented and all feedback comments resolved.

yay! nice job so far! thank you for taking care of that so quickly 🙌🏽🙌🏽🙌🏽
We need to have another technical feedback review by @derberg before we can merge tho, so now we wait for him 😄✌🏽

@alequetzalli thank you for your compliments. I was only able to complete the task so quickly because of your well detailed and timely feedbacks. It's been a pleasure working with you on this, and I'm looking forward to working with you on a new task once this current one is completed.

It looks good. My only concern is that it is CLI  docs authored in website repo, and it should be authored in cli repo, like we do with generator.

@alequetzalli I mean we need docs under cli repo (but 3 markdown files, one for intro, one for installation and one for usage, and later we can add a nice one about context concept explanation), and then add automation to cli repo that will push any updates done to docs, to the website repo.

Hey @activus-d, kindly update the GoBack button on /docs/guides page to point it to the new AsyncAPI CLI page created by you.

@akshatnema Thanks for the Observation. The branch has been updated.

Hey @activus-d here is what you need to do:

We are not going to merge this PR; as Lukasz observed, we want to host docs in their main repo and have them copied to the website repo where we can maintain them in the official website.
You must create a NEW PR in the CLI repo with this same exact content. Make sure this new PR in the CLI repo is only the written docs' content. (You don't need to add the prev/next buttons here since those only work on the /website repo.)
@derberg needs to code an automation that copies new docs added in CLI repo to the /website repo. Once that functionality is complete, it will be automatic to open a PR in both  CLI and /website repoes. (Lukasz needs to sync with us on what he thinks his next steps here are and timeline)
After the new automation copies the docs over to a new PR in the /websiterepo, you must ensure to add the prev/next buttons just like akshat showed you here.

I realize this is a lot of extra steps to think about, so please let us know if you understand and if you're able to do next steps. 😄✌🏽

later we can add a nice one about context concept explanation

Not quite, that is not what the Concepts sections is for and you should not duplicate content buckets into sub-sections.
Instead, the CLI tool will be introduced in the first file of introduction.md and any background context needed to introduce the tool shall be inside the Introduction section.
@derberg

Not quite, that is not what the Concepts sections is for and you should not duplicate content buckets into sub-sections.

oh, sorry, by concept I meant concept in general, not Concept bucket. So like in generator, where we have docs that explain different generator concepts, but these are just on the list of docs for generator. Same I mean for CLI, we just need to have later a document that explains "context" functionality/concept in the CLI.

You must create a NEW PR in the CLI repo with this same exact content. Make sure this new PR in the CLI repo is only the written docs' content. (You don't need to add the prev/next buttons here since those only work on the /website repo.)
For this NEW PR, let's actually make a tiny change. We want to have this CLI docs have subsections in the left-hand navigation. To accomplish that, you must separate your current CLI docs into separate files instead of only 1 file like you currently have in this PR. Let's separate your content based on the outline into 3 tiny sub-sections: introduction.md, installation.md, and usage.md.

@alequetzalli ALright. However, you are yet to tell me which of the directories in the CLI repository would host the document. Is it that I will create a new folder at the root of the repository and name it (let's say docs)? I need a specific direction in this regard.

@activus-d yes, new docs directory like https://github.com/asyncapi/generator/tree/master/docs

@derberg @alequetzalli I will work on it and make a pull request soon.

@alequetzalli @derberg the pull request has been made as instructed. Kindly review.

CLOSING in favor of resolving via https://github.com/asyncapi/cli/pull/414


How to ignore patterns?

Hey!
Trying to love the tool, but searching from ~ is long ; I'd like to exclude patterns like "any .git" directory or "any .cache" directory or "any node_modules" directory etc. you get it :)
Any idea how to do that?
I tried to put the following in my ~/.zshrc but it's not helping much, ~/.cache/ is still listed by fzf-dir-navigator
_fzf_compgen_path() {
  fd --follow --exclude ".git" --exclude "node_modules" --exclude ".venv" --exclude ".rvm" --exclude ".cache" --exclude ".virtualenvs" . "$1"
}

Thanks

Hey @vict0rsch,
The latest release should be a convenient way to exclude directories from your search results. Please take a look.
Thanks for the issue, and if it helps solve your problem, do close the issue too! Cheers!

That's great thanks!
Do we have to modify the conf file in ~/.oh-my-zsh/custom/plugins/fzf-dir-navigator?

I did not think of that initially. I have now updated instructions in the README file as well as the configuration file. The essential design remains the same (mainly because I am not able to come up with a better idea to handle the configurable options), in that a conf file within the repository itself will have to be edited.
The default config file fzf-dir-navigator.conf will receive updates, and what is expected from the user is to copy this default config file and name it fzf-dir-navigator-custom.conf, so that any pushes to the default config file will not affect the user (as you mentioned). So, in your case, you will have to do the following:
$ cp ~/.oh-my-zsh/custom/plugins/fzf-dir-navigator.conf ~/.oh-my-zsh/custom/plugins/fzf-dir-navigator-custom.conf
$ <editor command> ~/.oh-my-zsh/custom/plugins/fzf-dir-navigator-custom.conf

And then proceed to edit your custom configuration file.
Thanks for the valuable feedback, much appreciated!

That's working thanks!


Broken on windows

ping @sdondley -- https://ci.appveyor.com/project/azawawi/raku-file-homedir-kveko/builds/44860869#L1305

Fixed in https://github.com/azawawi/raku-file-homedir/commit/9ff6b6eeca2af585dfc2d56a8801b14100ceca25. Also GitHub test workflow is now working.
@ugexe  Thanks. I am warming up 👍


story: alert should have same fade out animation on close as notification

I have a couple of questions/topics to discuss:

In the current implementation, the alert has no close API. When clicking the closing button, it just emits a requestDismissal. Proposal:

remove the requestDismissal event
Add a cancellable willClose and a didOpen event
Expose a close method that will be called automatically when clicking the closing button

The animation property type default change from open to all (as the sbb-notification)

These changes would both generate a breaking change


nomacs: fix build with CUDA support

Description of changes
nomacs failed to be built at configure phase, if CUDA is enabled in nixOS (config.nixpkgs.config.cudaSupport = true;).
nomacs> CMake Error at /nix/store/bi9wn96vwxshzix8y4xwrqij91m06ppp-cmake-3.29.2/share/cmake-3.29/Modules/FindCUDA.cmake:883 (message):
nomacs>   Specify CUDA_TOOLKIT_ROOT_DIR
nomacs> Call Stack (most recent call first):
nomacs>   /nix/store/p1rp77lyvpsczzi7xpksf46ms0nrf2zj-opencv-4.9.0/lib/cmake/opencv4/OpenCVConfig.cmake:86 (find_package)
nomacs>   /nix/store/p1rp77lyvpsczzi7xpksf46ms0nrf2zj-opencv-4.9.0/lib/cmake/opencv4/OpenCVConfig.cmake:108 (find_host_package)
nomacs>   cmake/Unix.cmake:41 (find_package)
nomacs>   CMakeLists.txt:121 (include)

This PR fixed it.
I only tested this PR on my machine (x86-64). It was built successfully, and the binary works properly. Sorry if I lost some other test steps.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This builds, and loads e.g. libcudart at startup, but how do I test any actual cuda-dependent functionality?

It's an image viewer. I doubt whether it truly uses CUDA.  It seems like that CUDA is required by opencv4 instead of nomacs.

opencv> shrinking /nix/store/kbc392n8w8cpls0qh0l7v8gfcji3ay0v-opencv-4.9.0-package_tests/opencv_test_xphoto
opencv> checking for references to /build/ in /nix/store/kbc392n8w8cpls0qh0l7v8gfcji3ay0v-opencv-4.9.0-package_tests...
opencv> patching script interpreter paths in /nix/store/kbc392n8w8cpls0qh0l7v8gfcji3ay0v-opencv-4.9.0-package_tests
opencv> /nix/store/kbc392n8w8cpls0qh0l7v8gfcji3ay0v-opencv-4.9.0-package_tests/samples/install/linux_verify.sh: interpreter directive changed from "#!/bin/bash" to "/nix/store/306znyj77fv49kwnkpxmb0j2znqpa8bj-bash-5.2p26/bin/bash"
nomacs> building '/nix/store/90pgcnhpfk9cgcpgfq7nfviy2rzsngp0-nomacs-3.17.2295.drv'
nomacs> Running phase: qtPreHook
nomacs> Running phase: unpackPhase
nomacs> unpacking source archive /nix/store/cvahscwvbn4q0an1mar9y3w95ai9iqh8-source
nomacs> source root is source/ImageLounge
nomacs> Running phase: patchPhase
nomacs> Running phase: updateAutotoolsGnuConfigScriptsPhase
nomacs> Running phase: configurePhase
nomacs> fixing cmake files...
nomacs> cmake flags: -DCMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTING=OFF -DCMAKE_INSTALL_LOCALEDIR=/nix/store/nsvyc4vg8wlw9j093ikmys3gr4jsl11j-nomacs-3.17.2295/share/locale -DCMAKE_INSTALL_LIBEXECDIR=/nix/store/nsvyc4vg8wlw9j093ikmys3gr4jsl11j-nomacs-3.17.2295/libexec -DCMAKE_INSTALL_LIBDIR=/nix/store/nsvyc4vg8wlw9j093ikmys3gr4jsl11j-nomacs-3.17.2295/lib -DCMAKE_INSTALL_DOCDIR=/nix/store/nsvyc4vg8wlw9j093ikmys3gr4jsl11j-nomacs-3.17.2295/share/doc/nomacs -DCMAKE_INSTALL_INFODIR=/nix/store/nsvyc4vg8wlw9j093ikmys3gr4jsl11j-nomacs-3.17.2295/share/info -DCMAKE_INSTALL_MANDIR=/nix/store/w1yhmx36vy6l2vz7y7w03iaaplwffd0n-nomacs-3.17.2295-man/share/man -DCMAKE_INSTALL_OLDINCLUDEDIR=/nix/store/nsvyc4vg8wlw9j093ikmys3gr4jsl11j-nomacs-3.17.2295/include -DCMAKE_INSTALL_INCLUDEDIR=/nix/store/nsvyc4vg8wlw9j093ikmys3gr4jsl11j-nomacs-3.17.2295/include -DCMAKE_INSTALL_SBINDIR=/nix/store/nsvyc4vg8wlw9j093ikmys3gr4jsl11j-nomacs-3.17.2295/sbin -DCMAKE_INSTALL_BINDIR=/nix/store/nsvyc4vg8wlw9j093ikmys3gr4jsl11j-nomacs-3.17.2295/bin -DCMAKE_INSTALL_NAME_DIR=/nix/store/nsvyc4vg8wlw9j093ikmys3gr4jsl11j-nomacs-3.17.2295/lib -DCMAKE_POLICY_DEFAULT_CMP0025=NEW -DCMAKE_OSX_SYSROOT= -DCMAKE_FIND_FRAMEWORK=LAST -DCMAKE_STRIP=/nix/store/9bv7dcvmfcjnmg5mnqwqlq2wxfn8d7yi-gcc-wrapper-13.2.0/bin/strip -DCMAKE_RANLIB=/nix/store/9bv7dcvmfcjnmg5mnqwqlq2wxfn8d7yi-gcc-wrapper-13.2.0/bin/ranlib -DCMAKE_AR=/nix/store/9bv7dcvmfcjnmg5mnqwqlq2wxfn8d7yi-gcc-wrapper-13.2.0/bin/ar -DCMAKE_C_COMPILER=gcc -DCMAKE_CXX_COMPILER=g++ -DCMAKE_INSTALL_PREFIX=/nix/store/nsvyc4vg8wlw9j093ikmys3gr4jsl11j-nomacs-3.17.2295 -DENABLE_OPENCV:BOOL=TRUE -DENABLE_QUAZIP:BOOL=TRUE -DENABLE_RAW:BOOL=TRUE -DENABLE_TIFF:BOOL=TRUE -DENABLE_TRANSLATIONS:BOOL=TRUE -DUSE_SYSTEM_QUAZIP:BOOL=TRUE
nomacs> CMake Deprecation Warning at CMakeLists.txt:3 (cmake_minimum_required):
nomacs>   Compatibility with CMake < 3.5 will be removed from a future version of
nomacs>   CMake.
nomacs>
nomacs>   Update the VERSION argument <min> value or use a ...<max> suffix to tell
nomacs>   CMake that the project does not need compatibility with older versions.
nomacs>
nomacs>
nomacs> -- The C compiler identification is GNU 13.2.0
nomacs> -- The CXX compiler identification is GNU 13.2.0
nomacs> -- Detecting C compiler ABI info
nomacs> -- Detecting C compiler ABI info - done
nomacs> -- Check for working C compiler: /nix/store/9bv7dcvmfcjnmg5mnqwqlq2wxfn8d7yi-gcc-wrapper-13.2.0/bin/gcc - skipped
nomacs> -- Detecting C compile features
nomacs> -- Detecting C compile features - done
nomacs> -- Detecting CXX compiler ABI info
nomacs> -- Detecting CXX compiler ABI info - done
nomacs> -- Check for working CXX compiler: /nix/store/9bv7dcvmfcjnmg5mnqwqlq2wxfn8d7yi-gcc-wrapper-13.2.0/bin/g++ - skipped
nomacs> -- Detecting CXX compile features
nomacs> -- Detecting CXX compile features - done
nomacs> -- Performing Test COMPILER_SUPPORTS_CXX11
nomacs> -- Performing Test COMPILER_SUPPORTS_CXX11 - Success
nomacs> -- Performing Test COMPILER_SUPPORTS_CXX0X
nomacs> -- Performing Test COMPILER_SUPPORTS_CXX0X - Success
nomacs> -- A release build (non-debug). Debugging outputs are silently ignored.
nomacs> -- Found PkgConfig: /nix/store/zdvrzlvzbn9ymb0z8na50w995j8np16z-pkg-config-wrapper-0.29.2/bin/pkg-config (found version "0.29.2")
nomacs> -- Checking for module 'exiv2>=0.27'
nomacs> --   Found exiv2, version 0.28.2
nomacs> -- exiv2 version by pkg-config: 0.28.2
nomacs> -- exiv2 contains exiv2.hpp, using it
nomacs> CMake Warning (dev) at /nix/store/jsbvb4gmfncj9ahfsr1qgjd26hwk75w3-opencv-4.9.0/lib/cmake/opencv4/OpenCVConfig.cmake:86 (find_package):
nomacs>   Policy CMP0146 is not set: The FindCUDA module is removed.  Run "cmake
nomacs>   --help-policy CMP0146" for policy details.  Use the cmake_policy command to
nomacs>   set the policy and suppress this warning.
nomacs>
nomacs> Call Stack (most recent call first):
nomacs>   /nix/store/jsbvb4gmfncj9ahfsr1qgjd26hwk75w3-opencv-4.9.0/lib/cmake/opencv4/OpenCVConfig.cmake:108 (find_host_package)
nomacs>   cmake/Unix.cmake:41 (find_package)
nomacs>   CMakeLists.txt:121 (include)
nomacs> This warning is for project developers.  Use -Wno-dev to suppress it.
nomacs>
nomacs> CMake Error at /nix/store/q1nssraba326p2kp6627hldd2bhg254c-cmake-3.29.2/share/cmake-3.29/Modules/FindCUDA.cmake:883 (message):
nomacs>   Specify CUDA_TOOLKIT_ROOT_DIR
nomacs> Call Stack (most recent call first):
nomacs>   /nix/store/jsbvb4gmfncj9ahfsr1qgjd26hwk75w3-opencv-4.9.0/lib/cmake/opencv4/OpenCVConfig.cmake:86 (find_package)
nomacs>   /nix/store/jsbvb4gmfncj9ahfsr1qgjd26hwk75w3-opencv-4.9.0/lib/cmake/opencv4/OpenCVConfig.cmake:108 (find_host_package)
nomacs>   cmake/Unix.cmake:41 (find_package)
nomacs>   CMakeLists.txt:121 (include)
nomacs>
nomacs>
nomacs> -- Configuring incomplete, errors occurred!

It seems that the nomacs hasn't detected the opencv4 correctly, and tried to compile it again.

CC maintainer: @AndersonTorres @Mindavi

At least is not a good idea need to add CUDA to all packages that depend on opencv, no matter whether it truly needs CUDA.

This is why there currently exists the opencv.cxxdev output with the extra propagated-build-inputs. This should really be moved to dev, except that this inflates the python package's closure

@Cryolitia is correct, it doesn't seem like nomacs is even aware it (transitively) depends on cuda, so manually extending the build inputs isn't the correct solution.
For the time being, I'd suggest we replace opencv4 in buildInputs with (lib.getOutput "cxxdev" opencv4).
Once the python situation improves we can revert this change and let mkDerivation choose dev "by default"

@SomeoneSerge I confirmed the fix (lib.getOutput "cxxdev" opencv4) works. I have force pushed the change.


Still active, or use a fork?

Hi, I see that his project is not very active but has active forks. Do you intend to merge them or should I start using a fork? Do the forks want to be used at all?
Pinging fork owners: @seanlth @arcturu @snuk182

I check in on this every week or so. I'd love to use libui in Rust, but I want to feel confident about maintenance.

At this point I'm more than happy to hand off official maintainership to one of those forks, for what it's worth. :)

https://www.reddit.com/r/rust/comments/85j62r/libuirs_revival/dvxxyj4/

https://github.com/LeoTindall/libui-rs is the most active one one. The other two have since gone inactive or gone entirely


Fixed a bug in makeMarkovApproxToNormal in HARKutilities.py.  Before,…

Came across a bug in makeMarkovApproxToNormal, so (I think) I fixed it.  Before, the weights in alpha could go below 0 or above 1, which obviously caused issues.
I also created another function, makeMarkovApproxToNormalByMonteCarlo, largely as a way to check makeMarkovApproxToNormal.  Now, the two functions seem to give very comparable output, but I will let you verify this, and check this code any other way you want.
makeMarkovApproxToNormalByMonteCarlo was really just intended to check makeMarkovApproxToNormal; I'm not sure it needs to stay in HARK once we are sure makeMarkovApproxToNormal works.  I leave that decision up to you.

Yes, you are correct in finding this bug.  I'm not a huge fan of this function, as it was just sort of thrown together when I needed to make a Markov approximation to an AR1.
Edmund Crawley has added the function TauchenAR1 (which should be renamed makeTauchenAR1) to a branch on his fork that we're currently working on.  For most purposes for which I intended to use makeMarkovApproxToNormal, makeTauchenAR1 is better suited.  The only advantage to my function is that you can pick a weird grid of values if you want (and it does one row at a time), but that can easily be added as an option to makeTauchenAR1

You misplaced the comma or parentheses in the third part of the assertion.  Method crashes.
(np.isclose(np.sum(p_vec)),1.) should be (np.isclose(np.sum(p_vec),1.))

Should be fixed now


Typo in the documentation

readme.md file has a typo at  legacyDecorators word.
If you want use @babel/plugin-proposal-decorators with EsLint, you can enable useEslintRc, described below, with the follow configuration in your .eslintrc or package.json:
{
  "extends": "react-app",
  "parserOptions": {
    "ecmaFeatures": {
      "legacyDecotators": true // this is an error
    }
  }
}

You need to use
{
  "extends": "react-app",
  "parserOptions": {
    "ecmaFeatures": {
      "legacyDecorators": true
    }
  }
}

It was fixed in f61b8524671756c17abb27c762e316572b40f06e.

Sweet - glad it was fixed. Thanks!


Dropping support for node v6 and using async/await

With v6 out of LTS and v12 introducing async stacktraces, would you at all be interested in refactoring the codebase by replacing all .then/.catch with async/await and try/catch for the performance & debugging improvements? If you are, I'll be happy to help out with a few PRs

Async/await is definitely something that we want to do, although I'm not sure about performance benefits; isn't it still at least slightly slower than promises? That said, I want async/await for tests badly, so we are most likely dropping support for Node 6 in next major version anyway. So please do send these PRs in!

Good point - regarding performance, native async/await has caught up in v12:
/bluebird $ ./bench doxbee

results for 10000 parallel executions, 1 ms per I/O op

file                                       time(ms)  memory(MB)
callbacks-baseline.js                           167       25.14
callbacks-suguru03-neo-async-waterfall.js       215       40.11
callbacks-caolan-async-waterfall.js             225       46.23
promises-bluebird-generator.js                  229       32.55
promises-bluebird.js                            263       49.07
promises-native-async-await.js                  269       54.89
promises-lvivski-davy.js                        280       89.95
promises-ecmascript6-native.js                  295       64.70
promises-cujojs-when.js                         303       59.53
promises-then-promise.js                        347       72.50
promises-tildeio-rsvp.js                        412       86.03
generators-tj-co.js                             491       62.53
promises-calvinmetcalf-lie.js                   499      139.76
promises-dfilatov-vow.js                        589      133.29
promises-obvious-kew.js                         635      114.16
streamline-generators.js                        687       90.89
promises-medikoo-deferred.js                    737      127.87
observables-pozadi-kefir.js                     799      153.48
streamline-callbacks.js                         945      118.20
observables-Reactive-Extensions-RxJS.js        1235      228.34
promises-kriskowal-q.js                        2762      484.91
observables-caolan-highland.js                 3158      455.48
observables-baconjs-bacon.js.js                4611      815.02

Platform info:
Darwin 18.5.0 x64
Node.JS 12.0.0
V8 7.4.288.21-node.16
Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz × 4

Also here's more detail about the improved debugging: https://v8.dev/blog/fast-async

After https://github.com/tgriesser/knex/pull/3227 is merged, we can finally get started!

Node 6 support was dropped in master. PRs with refactorings for async/await usage are most welcome now.

@alubbe Bluebird was being removed bit by bit lately. Additional PR for replacement of .then() blocks would be most welcome.


Fix an issue with CuratedPackage.toUncuratedPackage()

Get rid of the "not always correctly working" [1] toUncuratedPackage() by utilizing the original uncurated packages from the OrtResult. While at it, do a couple of clean-ups for related OrtResult getters and their callers.
[1] https://github.com/oss-review-toolkit/ort/issues/5637.
BREAKING CHANGE: Only for programmatic use of ORT:

uncurated packages should be obtained now from the OrtResult instead of from the removed toUncuratedPackage().
Some API functions get renamed, so the name change must be reflected.

Could it be commit-lint is running into this bug? https://github.com/conventional-changelog/commitlint/issues/896

Could it be commit-lint is running into this bug? conventional-changelog/commitlint#896

Looks like it, maybe the #5637 in the body triggers the line to be read as footer because the commitlint output shows an empty line before the second line of the body. Maybe you can find a workaround, FYI you can commitlint locally like this npx commitlint --from HEAD~2.


Visibility

hi, again
i know, that this should be a smooth (artless) Design.
For bigger Screens or bigger Distances the visibility is very small.
Could there be more Values in the "Line width" setting?

For linear layout it just runs out of space. To make it support more than 1 unit in height seems quite of challenge.
For radial layout it may be possible to go let's say up to 15px line width. It then creates another possible issue with tickmark positions and can possibly overlap. And it definitely will make mess for smaller sizes.

So the configuration options should dynamically change according to configured size. Such things are annoying for user and should be avoided.
So it is a bit more work than just add bigger figures to options...
(slight remark - to improve readability, playing with color combinations may help.)

@hotNipi  I hope you did not understand my wish as a just do it is so simple.
You are the Designer and know exactly what is possible under which circumstances. Im only a User who is searching for a Solution which fits my needs. Off coarse you have to consider for all scenarios.
I hope you find a "dynamic" Solution for future Versions 👍

No problems :) And I did what was possible and reasonable.
With version 0.1.46 the radial layout gives more options for line thickness but only if the layout size is at least 4x4 units. No change for linear layout as there is no space for that.

@hotNipi
Fantastic 👍👌👏 work fine.
Maybe you could think about the Linear Version, stretched to the hight of 2?
For the Moment thanks for the fantastic Support and the creating of the new Version 🎁

With version 0.1.47 (already published and will be available shortly) the linear layout has support for 2 units height and up to 25px line thickness. (slightly bigger texts and icon to preserve graphical balance)

@hotNipi
you are suuuper 👌👍

Oh not that much, made mistake so 0.1.48 will be a bit better version (shortly available)


refactor(nodebuilder/share/cmd)!: Take block height instead of ExtendedHeader as argument for share cmds

Description
Replace extended headers with block height as an argument in shares cmd
Issues close
Close #2848
Changes made

Replace all uses of extended header as an argument with block height in nodebuilder/share/cmd/share.go.
Add logic to fetch header first with block height for

hey @Wondertan, i added both usage of block hash and height in

Approving. Did you test it out manually? Please do if not and then we can merge

yes i've tested it and everything work great


Update stable.txt url

It looks like we need to update the URL for stable.txt file, the one on the googleapis is supposed to be gone (or not updated automatically any more).
The new URL is: https://dl.k8s.io/release/stable.txt
PS: I will create another PR to update it on kubernetes-sigs/verify-conformance repo as well.
/cc @BobyMCbobs

Oh good catch! Thank you!
/lgtm
/approve


Merge branchunless test suite files

There were two branchunless test suites:

branch_unless_test.rb: had UTs inside, but the (seemingly) wrong file and suite naming
branchunless_test.rb: no UTs, but (seemingly) correct file and suite naming

I've moved the content of the first suite into the second, and removed the first file, so now both file and suite naming are (seemingly) correct.
Regarding the test suites naming, there are a few other inconsistently named suites (search (?<!Test )< JITTest), but I'm not sure if this is just pedantic, so I'm only reporting this :)

Sorry, there's a force push, as I had erroneously pushed Gemfile.lock (it's not in the git ignore list). I'm opening an issue for this.


Fix toolbars in dsp sample app

Fix toolbars implementation in dsp sample app (currently it's commented out becuase of some strange databinding issues)

Fixed with PR: https://github.com/kotoMJ/kotox-android/pull/14

https://github.com/kotoMJ/kotox-android/pull/14


feat: add support to use existing SM instance for DA

Description
Issue: https://github.com/terraform-ibm-modules/terraform-ibm-secrets-manager/issues/107

Release required?

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

 2024/04/26 15:02:49 Terraform apply | Error: [ERROR] Error when creating resource instance: Please contact the Service Provider for this error. [422, Unprocessable Entity] This account reached the number of Trial plan instances that are allowed. To proceed, you must select the Standard plan or delete an existing Trial instance. If you delete the Trial plan instance, you must also delete its reclamation by using the IBM Cloud CLI. Learn more: https://ibm.biz/BdPa49 with resp code: {

region: eu-de

/run pipeline

/run pipeline

@ocofaigh - is there a need to clean up trial instances?

/run pipeline

/run pipeline


MB-5862 | Making scripts/scan-alb-logs support GovCloud

Paired with @kilbergr and verified this works.

Messages

:book:
:link: MB-5862

  Generated by :no_entry_sign: dangerJS against 1e38d76a247c85d5d2b1cafec79bdc774141a51c


Switch to using JSPM instead?

nah, provide a link to the JSPM version as a branch

we have a jspm branch
https://github.com/angular-class/NG6-starter/tree/jspm


Bugfix for the use of metric

Our code for how to use the metric (aka M_inverse) was based on Stan's. For a long time, we found our diag and dense preconditioning behaves weridly. This is still true for the current master and I meet this issue when running integrated test on Turing.jl again today, even in gdemo.
After checking Section 4.2.1 of Michael's paper again, I don't see any clue how would Stan's way to use M_inverse would work (at least in our current setting). So I changed it based on my current understanding and at least it works normally on gdemo now.
Below is what I did:

When sample momentum, I return the momentum variable in the transformed space.

The transformation is the one in Michael's paper instead of the previous one. The difference is whether we multiply or divide r by M_inverse.
I think @yebai was trying to do the same thing before but we ended up following Stan's code.

When compute grad_r that is needed to update q, I transform grad_r back to its original space.

By doing so, the update of q is just as normal.

Nowhere else need to use M_inverse.

The changes in energy are cancelled and we only use Hamiltonian as a sum of two energy.

End of page 30 of https://arxiv.org/pdf/1701.02434.pdf is the one for knetic energy, and for potential energy it's just the origional - log(abs(det(jacob)), the latter of which is cancelled.

The logabsdetjacob in potential space doesn't matter as it's a constant w.r.t potential variable thus will be 0 when we take the gradient.

@yebai Any comments?

Emmm. I asked Michale about why they are different between the code and the paper and he explained to me what happens. The r.v. we sample from N(0, 1) is in fact q' but not q, thus all the multiplication and division are "reversed".
I'm not more confused about this :(

This might be related to the U-Turn criteria. Ref: https://github.com/stan-dev/stan/blob/1bb054027b01326e66ec610e95ef9b2a60aa6bec/src/stan/mcmc/hmc/nuts_classic/diag_e_nuts_classic.hpp#L24 is different.

I don't think this fix is quite right now. I will reopen it or create a new one when I feel more confident on it.


Ignore case while sorting imports

Codecov Report

Merging #106 (865dba4) into master (e461613) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #106   +/-   ##
=======================================
  Coverage   37.43%   37.43%
=======================================
  Files          67       67
  Lines        4304     4304
=======================================
  Hits         1611     1611
  Misses       2693     2693

Impacted Files
Coverage Δ

lona/__init__.py
80.00% <100.00%> (ø)

lona/command_line/run_server.py
25.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

@maratori why do we want this exact configuration and not the default one?

@fscherf I've discovered that current config is not always use length to sort. Example: https://github.com/lona-web-org/lona/pull/106/files#diff-220e4fd05c64a365ba3a559a3d4113b7382152a54f5902fed428c0ce1603adfaR7

@maratori and why? Is there a good reason why isort is doing it this way by default? Why do we want it differently?

@fscherf I've rebased branch and removed configs that don't change defaults.
By default it sorts first by type and then alphabetically (order_by_type = True and length_sort = False).
When we sort by length, but keep sorting by type, we get following.
from lona.html import (
    TextInput,
    Button,
    Node,
    Div,
    Br,
    A,
    CHANGE,
    CLICK,
    HTML,
)

I think it's better to not sort by type.
from lona.html import (
    TextInput,
    CHANGE,
    Button,
    CLICK,
    Node,
    HTML,
    Div,
    Br,
    A,
)

@maratori I totally agree! Thanks! :)


[BEAM-9431] Remove ReadFromPubSub/Read-out0-ElementCount from the met…

…rics validation
Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

R: @Ardagan @ananvay @acrites

LGTM. Thanks Ankur!

Can you elaborate a bit more on why we remove counter validation?

I think the counters are not available on streaming engine and only published with streaming appliance so it will not be a valid test to have them.
cc/ @ananvay

@Ardagan Friendly ping. Do the change look good?


Use case for sharing memory-cached dataset across processes.

Hi Mihej,
Thank you for your contributions to creating this repo, I'm trying to make use of it in the following scenario, which I think may help others as well so I'm creating an issue here:
I'm writing a PyTorch program that involves training on a large dataset, and I want to cache the whole dataset to memory to speed up training. However, since the dataset is large and I want to run multiple hyperparameter settings at the same time and the same dataset, I want to share the cached dataset across different runs. Could you give a simple example of how I can achieve this?
I think a SharedMemory class and the put_message(dataset), take_message(dataset) methods should work, but I'm not sure if I can call the take_message multiple times across different runs once I've put it.
The dataset I want to cache has the following form:
cached_dataset = [
data_1, # dictionary of several numpy arrays like images, etc
data_2,
...,
]

Do you have any advice on how I can improve the reading performance of the shared dataset? And after I've put the cached dataset into the shared memory, is it safe for me to delete the original cached dataset so that it won't take up twice of the memory?
Thank you for the help!

Hi @hukz18, thank you for your interest!
First of all, feel free to use read_message instead of take_message. It will read an object from the message but will not delete the message from the queue. That means you can safely take the same shared object multiple times.
The overall architecture can vary depending on your situation. Here are two possibilities:
1. Single Process at Each Moment in Time
If you are trying to run your training script multiple times in a row in a sequenced manner (such that there is either no instance or no more than one instance of your training process in memory at a time) and just want to preload data for those runs, follow these steps:

Spawn a Creator process that will put_message with your shared data and then persist permanently.
In the main loop of your working process:
a. Spawn a Consumer that will read_message and work on your preloaded data.
b. Finish your Consumer instance.
c. Spawn another instance of your Consumer that will read_message and work on your preloaded data.
d. Finish another instance of your Consumer.
e. ... (Repeat as necessary)

2. Multiple Processes at Each Moment in Time
If you need to share data between multiple instances (processes) of your training scripts at the same time (in parallel):
In this situation, you'll need to wait for my next release (probably by next Monday). I've added support for symmetric multiprocessing (SMP).
If you have any additional questions, please feel free to use either Discussions or Cengal Discord.

Thanks for your reply! I'm waiting for the SMP features, I'm glad to try it out :-)


Fixes #780 Some Python tutorials use queue_declare() without ...

…the required queue argument

@glexey Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@glexey Thank you for signing the Contributor License Agreement!

https://github.com/rabbitmq/rabbitmq-tutorials/pull/225


Add phylotree.js as an NPM package

This PR replaces an old version of phylotree.js that we included with Klados with phylotree v1.4.0 installed from NPM.js.
Closes #258.
WIP:

[x] Need to get the old code for highlighting the resolved clade edges to work.
[x] Need to get the old code for using a larger font size for text in the phylogeny.
[x] Need to get the old code for stretching the phylogeny to fill the available width to work.
[x] Need to get the old code for changing the label of a node to work.
[ ] #228
[ ] #226

Current status:


Auth support for SameSite Changes coming to Browsers and Loading CCP widget on a 3rd Party Domain

As of Chrome v80 – to be released Feb 4 -  (and soon to be Firefox and the latest IE) the browsers will be enforcing SameSite cookies by default.  Meaning that if SameSite policy is not set on cookies they will by default not be available across third party domains. This is problematic for any developers trying to embed AWS connect widget's on one of their 3rd party domains.
Better explanation: https://web.dev/samesite-cookies-explained/#explicitly-state-cookie-usage-with-the-samesite-attribute
The SAML auth flow with AWS connect currently obtains the following auth cookies after SAML auth flow with a API call to
POST https://${ConnectInstance}.awsapps.com/connect/auth/sign-in
This API call set the 2 following cookies on Response used for authentication on subsequent AWS Connect Calls
lily-auth-prod-iad
&&
lily-auth-refresh-prod-iad

As you can see these cookies are being set with SameSite as empty. This causes Chrome in new version to default cookies SameSite policy to SameSite=Lax which then will cause these auth cookies to not be sent to the subsequent AWS call to authorize with how the CCP widget is loaded into an IFRAME on a 3rd party domain.
GET https://${ConnnectInstance}.awsapps.com/connect/auth/authorize
By downloading chrome canary version you can validate this breaks as well as get the following warning saying cookies are being filtered so they will not be sent along with the call to /connect/auth/authorize and thus we get a 401 consistently.

To Test:

Download Chrome Canary ( https://www.google.com/chrome/canary/ )
In your current Chrome type in chrome://flags, and enable SameSite cookies

Is there any recommendation for developers to work around this or for how to proceed if they are embedding the CCP widget on a custom domain name. This would be a change Amazon would need to make with how they are defaulting cookies on the call to /connect/auth/sign-in and set connect auth cookies to SameSite=None if they intend to allow end users to embed the aws connect CCP widget on their domains.

Thanks for the detailed post!
We are aware of this issue and are working on a solution, stay tuned for an update.

Closing this issue, as the samesite changes have been made and are functioning properly.


Configuring for "TTGO T-Display" results in build error

IMPORTANT
Issues that don't use this template will be ignored and closed.
Perform all steps below and tick them with [x]

[x] Check the related part of the Documentation
[x] Update lvgl to the latest version
[NA] Reproduce the issue in a Simulator

Describe the bug
Build Error when lv_port_esp32 configured to TTGO T-Display - TFT_SPI_HOST not defined.
./components/lvgl_esp32_drivers/lvgl_helpers.c: In function 'lvgl_driver_init': ../components/lvgl_esp32_drivers/lvgl_helpers.c:111:26: error: 'TFT_SPI_HOST' undeclared (first use in this function); did you mean 'VSPI_HOST'? lvgl_spi_driver_init(TFT_SPI_HOST,
To Reproduce

git clone --recurse-submodules https://github.com/lvgl/lv_port_esp32.git
Run the menuconfig, and for the lvl tft display controller, pick "TTGO T-display"
Save the configuration and build.

The Kconfig seems to be at fault: the conditional on prompt "TFT SPI Bus." in lv_port_esp32\components\lvgl_esp32_drivers\lvgl_tft\Kconfig
appears to prevent LV_TFT_DISPLAY_SPI_* from being set. At least, commenting out the conditional lets it build.
Environment: vscode-esp-idf-extension, Win10.
Expected behavior
Build without errors
Screenshots or video

As this is issue is related to lv_port_esp32 I transfer it there.


Context is lost when using Webpack

If you compile the webpack module with cls-hooked and run bundle in NodeJS, the context will be lost. Why is this happening?

@zkulbeda  could you please share an example about your issue, how do you use it with webpack


Failure in external plugin list command is ignored

If an external plugin fails when called with list, the error is logged but the ls call still succeeds (exits 0) and reports the directory as empty. It should fail and return the error.

A little more context on this: we swallow the error because we may get useful output even if find or whatever command you use to list things exits non-zero due to lack of permissions on some targets. However, we also ignore stderr. Some possibilities improvements here are

warn instead of info for errors when we get some entries back
error if we get non-zero exit and no entries
capture stderr; on failure, stdout probably doesn't contain the cause

Specific test was ls on the filesystem for a Bolt target that doesn't exist.


MQTT Client stuck at mqttClient.connect("id", "user", "pass"). No runtime error, no error code, no timeout.

The client seems to freeze when executing mqttClient.connect(). I find it strange considering how it manages a few complete transmissions before this happens. I'm using GSM - I make sure the arduino is connected before each transmission by reconnecting and checking whether there's a valid IP-address present. This doesn't seem to be a common issue so I figured I'd try my luck here.
Here's the mqtt function:
  if (!mqttClient.connected()) {
    Serial.print("MQTT - Attempting to connect to MQTT broker: ");
    Serial.println(broker);

    if (!mqttClient.connect("id", "user", "pass")) {
      Serial.print("MQTT - connection failed! Error code = ");
      Serial.println(mqttClient.state());
    } else {
      Serial.println("MQTT - connected");
      send_to_mqtt();
      Serial.println("MQTT - message sent.");
      mqttClient.disconnect();  // disconnects mqtt
      gsmClient.stop();   // disconnects network
      isClientConnected = false;
      Serial.println("MQTT - mqttClient and gsmClient disconnected.");
    }
  } else {
    Serial.println("MQTT - already connected");
  }

There's a reconnect function executed before each MQTT transmission looking like this:
  checkNetwork();
  Serial.println("Reconnecting GSM...");
  GSM.getNetwork()->disconnect();
  delay(500);
  Serial.println(GSM.localIP());
  int thresh = 3;
  while(GSM.localIP() == IPAddress(0,0,0,0) && thresh > 0)
  {
    Serial.println("No Ip - Connecting...");

    switch(GSM.getNetwork()->connect())
    {
      case 0:  //NSAPI_ERROR_OK
      Serial.println("Connection established.");
      break;

      case -3020:    //NSAPI_ERROR_BUSY
      Serial.println("Asynchronous operation cannot be started. ");
      break;

      case -3015:    //NSAPI_ERROR_IS_CONNECTED
      Serial.println("Already connected.");
      break;

      default:
      Serial.println("Connection failed");
      break;
    }
    delay(1000);
    thresh--;
  }
  if (!thresh)
  {
    Serial.println("Failed to establish GSM connection.");
    physReset(RESETpin);
  }
  else
  {
    Serial.print("GSM connected at IP adress: ");
    Serial.println(GSM.localIP());
  }

Here's a screenshot of the output:

After looking through the source code I'm guessing this is the part where I'm getting stuck (in boolean PubSubClient::connect(const char *id, const char *user, const char *pass, const char* willTopic, uint8_t willQos, boolean willRetain, const char* willMessage, boolean cleanSession)), but I can't seem to figure a way to solve it
            while (!_client->available()) {
                unsigned long t = millis();
                if (t-lastInActivity >= ((int32_t) this->socketTimeout*1000UL)) {
                    _state = MQTT_CONNECTION_TIMEOUT;
                    _client->stop();
                    return false;
                }
            }

Edit:
I tried rewriting the function to use a unique pointer instead to ensure a fresh client, but the problem persists
First declaring the object:
std::unique_ptr<PubSubClient> mqttClient;
And defining the function:
  mqttClient.reset(new PubSubClient);
  mqttClient->setClient(gsmClient);
  mqttClient->setServer(broker, port);
  if (!mqttClient->connected()) {
    Serial.print("MQTT - Attempting to connect to MQTT broker: ");
    Serial.println(broker);

    if (!mqttClient->connect("id", "user", "pass")) {
      Serial.print("MQTT - connection failed! Error code = ");
      Serial.println(mqttClient->state());
    } else {
      Serial.println("MQTT - connected");
      send_to_mqtt();
      Serial.println("MQTT - message sent.");
      mqttClient->disconnect();  // disconnects mqtt
      gsmClient.stop();   // disconnects network
      isClientConnected = false;
      Serial.println("MQTT - mqttClient->and gsmClient disconnected.");
    }
  } else {
    Serial.println("MQTT - already connected");
  }

Edit 2:
After some further testing I seem to have located the part causing issues. I placed print statements before and after each function call in the connect() method, and the only part where it seems to struggle is here:
write(MQTTCONNECT,this->buffer,length-MQTT_MAX_HEADER_SIZE);
Is it possible to add some sort of either timeout or complete reset of the buffer before executing this command?

Hi,
I'm in a similar situation, when I try to connect an MQTT broker over internet (eg. test.mosquitto.org) or in my LAN (Raspberry Pi) and there isn't any internet or network connection (I haven't possibility to check it before) calling PubSubClient::connect(const char* ) the ESP32 hangs in that row

I believe this may help: https://github.com/knolleary/pubsubclient/issues/403#issuecomment-1432869562
I answered thinking this is my problem, but I found your issue.


Don't include example off docs.rs

This uses docs.rs metadata to specify the inclusion of the example, meaning that it doesn't have to be included by default.
Technically a [breaking-change], though... (though the module is specified as not public API)

Published in 1.0.2. This drops compile time of the bitflags crate by itself from 0.41 seconds to 0.29 seconds on my machine, a 30% improvement. :grinning:


CVSS 2 editor

The title and description are missing for all fields in the CVSS2 editor since these are not given in the cvss-v2.0.json.

In https://github.com/secvisogram/secvisogram/pull/356 I tried to solve that by getting title and description from additional metadata https://github.com/secvisogram/secvisogram/pull/356/commits/9ea2a97e9bd44490774830cb543ffa3aaa89d1c3

The title and description are missing for all fields in the CVSS2 editor since these are not given in the cvss-v2.0.json.

In #356 I tried to solve that by getting title and description from additional metadata 9ea2a97

I guess this problem will be solved, once we have the translation setup.

The title and description are missing for all fields in the CVSS2 editor since these are not given in the cvss-v2.0.json.

In #356 I tried to solve that by getting title and description from additional metadata 9ea2a97

I guess this problem will be solved, once we have the translation setup.

Alright, that's fine for me.


json-read: Fix output to be valid JSON for hash values

We were outputting ruby representation for attributes, which is not
valid JSON when the value is not a string / integer / boolean / etc.

+1

:+1:

Why are we anyway writing json on our own? Ruby got methods to dump valid JSON

Why are we anyway writing json on our own? Ruby got methods to dump valid JSON

I'm confused :-) Do you want to ask "why do we have this tool", or "why this change", or something else?

I'm confused :-) Do you want to ask "why do we have this tool", or "why this change", or something else?

I'm asking why we are doing it so fragile and complicated :D

@tboerger PRs very welcome (and no, I don't mean this ;-) )


Fix support for display hints being applied

This change restores support in pysmi for applying display hints, as was broken by lextudio/pysmi@84be3ff. This is the pysmi issue I mentioned in lextudio/pysnmp#139. Of course, the display hint related issues in pysnmp itself still remain.
As before, this change has been tested with the script from PR #3, now with the updated mibs.pysnmp.com collection. The results are exactly the same before and after this change. From pysmi's perspective, the main observable difference of this change is that the newly added "PrettyValue" test cases failed before, and pass after this change.
Please note that when using the latest pysnmp HEAD, the pysmi test set already started to fail for other reasons (namely, the rename of namedValues). I don't know whether that will be an issue for automatic verification here.
Also, a heads-up FWIW: I intend to submit a few more pysmi changes later this week, with as ultimate goal the ability to regenerate the code of the base MIBs in pysnmp.

But now no test cases cover Unsigned32 related display hints, right? @dcvmoole Do you plan to work on that in another pull request?

Not for pysmi. The reason I changed Unsigned32 to INTEGER in the existing test here, is that in order to process a DEFVAL value for an Unsigned32 syntax, pysmi requires actual symbol information from SNMPv2-SMI (i.e., it needs to do a symbol table pass on that entire MIB first), and SNMPv2-SMI is not available to the test set. However, Unsigned32 was an arbitrary choice for that test in the first place: for pysmi, handling of DISPLAY-HINT clauses is fully independent of the specific syntax, so for the purpose of this test, any base type will do. It would of course be possible to make a copy of the previous test and change/add the INTEGER/DEFVAL parts in the copy only, but that would just be redundant and add no value for pysmi.
On the other hand, it would definitely be useful to have a full sweep of display hint processing against each base type, especially in the light of the issues that came up in lextudio/pysnmp#139. However, that is conceptually outside of the scope of pysmi and its test set, and would practically run into the above symbol table issue anyway. I think it would make much more sense to add such a test to pysnmp, as it involves mostly functionality on the pysnmp side. Given that I currently do not foresee having any use for the pysnmp display hint functionality myself, I have no plans for working on that at this time.

Thanks. Shipped in release 1.5.6.


Add component governance task to Azure pipeline

Is your feature request related to a problem? Please describe.
This is a security requirement that we run the Component Governance task in a release pipeline. azure-pipelines.yml performs a release so we must add this task.
Describe the solution you'd like

[x] Move the GEv4 pipeline to the microsoftgraph ADO organization under our Microsft Graph Dev Experiences project. This will require us to reconfigure some service connections.
[ ] Setup a Component Governance page for the results of CG task.
[ ] Add a the ComponentGovernanceComponentDetection task to the pipeline. I think we will want to make a second pipeline that triggers on azure-pipelines.yml successful completion to run CG. This way, we don't block deployment. The reason being the we will need to evaluate whether the issue can be fixed (some dependencies chains my not accept a later version, and we may need to press the owners to update their dependency tree). We will want to create bugs to address this on fail.

- task: ComponentGovernanceComponentDetection@0
  inputs:
    scanType: 'LogOnly'
    verbosity: 'Verbose'
    alertWarningLevel: 'High'
    failOnAlert: true

AB#7495

I think we just need to fail on alert.
https://github.com/microsoftgraph/microsoft-graph-explorer-v4/blob/dev/azure-pipelines.yml#L65

Closing this as fail on alert is not supported yet.
https://github.com/Azure/azure-sdk/issues/40#issuecomment-467182808
Other parameters of the task have been met


Feature/transition frontier diff

Created tests that make sure that the writes are successful to the database. Need to refine the tests such that they are able to query from these databases.
Checklist:

[ ] Tests were added for the new behavior
[ ] All tests pass (CI will check this if you didn't)
[ ] Serialized types are in stable-versioned modules
[ ] Does this close issues? List them:

should be put it in gitattributes?

this is how you skip diffs on it right? I think we should

Should you add yourself as the code owner for the newly added files?


Allow hiding and colour change of individual needles

Add unique class names to needles so they can be hidden, or colour changed etc by CSS

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download

Why?

Feature added in v1.3.0


update rotary-mouse-wheel project to remove HID module

The project
https://microsoft.github.io/jacdac-docs/clients/makecode/projects/rotary-mouse-wheel/
requires a HID module which won't be available this summer.

never mind, I see you have another project for rotary encoder.


Fix error with big message for translation.

Google added the maximum length to the text for translation. Max size of text = 5000.

Coverage increased (+0.02%) to 98.765% when pulling 60fbed6b406fd81e46d11e20e2d6da27db34a264 on Andru1999:patch-1 into 48653332effe76d0a034a730abdba1e96cd56d8a on ssut:master.

I am not sure if this idea will solve the issue properly because in this way the translation context should be lost unless splitting text by punctuation or something, which separates text by contexts.


how get bearing?

how can get bearing in direction to second latlng?
thanks

You have to write the code to calculate the bearing in the each step with lat/lng (Search for quadrant in mathematic)


Restore 100% test coverage

This is mostly annotational, but there were a few minor tests missing from however long the coverage-check was busted.
The larger items:

Add :nocov: annotations to some version-specific code
Mark all SecurityError-related code as :nocov:, and conditionalize a few of the specs related to it based on RSpec::Support::RubyFeatures.supports_taint?. They were passing anyway, since they were just checking for "doesn't raise an error", but they weren't actually testing what they said they were testing, when run against anything after ruby-2.6
Mark the ForkRunner#run_specs method as :nocov: - it actually is fully covered, but it only executes in a forked process, when run by the integration/bisect_spec.rb, and the Coverage run in the main process doesn't hear about it. But I manually checked, and both conditional branches are getting exercised.
Mark the DidYouMean wrapper as :nocov:, since the gem isn't installed on CI - none of the code inside this file can be exercised there (though it is covered anywhere it can run)
Add a few obvious specs, based on existing adjacent specs
Add a silly spec for Bisect::ShellRunner.name which maybe should just be deleted instead? It's not clear that this method is necessary - if anyone can be confident that it's not, I'd be just as happy to remove it. (But probably in another PR - I like keeping these kinds of things comment/test-only)
Start requiring 100% coverage again, now that it's true.
If the tests fail, store the coverage output as an artifact. This was because tracking down what lines were uncovered on CI turned out to be fairly annoying; this will make it easy next time.

(Moving back to draft while I figure out what else is covered locally but not in CI)

My apologies for another round of comments. Now when we have a check for >= 3.1, would it work to run coverage on those versions? That way we would get rid of a necessity having this coverage_only_on. At a (quite low) cost of running coverage on 3.1 and 3.2. What do you think?

Ah! Yes, it shouldn't be necessary anymore. But that does call to mind the reason I had it as an environment variable in the first place, which was that controlling which rubies we want to enforce coverage against should ideally be specified near the matrix, instead of in the script - I should have used that variable for this purpose instead! One moment.

3.1 coverage seems to be 99.9. I’m ok to enforce on 3.2+

3.1 coverage seems to be 99.9. I’m ok to enforce on 3.2+

Oh, it looks like if SyntaxError.instance_methods.include?(:detailed_message) amounts to 3.2+ - I'll update the boundary :-)

Thank you!

Thank you!


move static route to unit

If a node reboots, the routes aren't installed as it happens in kubeadm.
It should be a unit in ignition. Context: https://gigantic.slack.com/archives/C02EVLE9W/p1714374192860579
I had a race condition issue when using a dedicated networkd unit so I moved the ip route add commands to the script that sets up networking.
(Rework of https://github.com/giantswarm/cluster-cloud-director/pull/293)

/run cluster-test-suites

I kinda want the green check though
/run cluster-test-suites

/run cluster-test-suites

this PR seems to repeatably fail on the upgrade test:
  {"level":"info","ts":"2024-05-14T16:26:56Z","msg":"Found KubeadmControlPlane condition MachinesSpecUpToDate with Status='False' and Reason='RollingUpdateInProgress', expected condition with Status='True' and Reason=''"}
  [FAILED] in [It] - /app/internal/upgrade/upgrade.go:146 @ 05/14/24 16:27:17.439
• [FAILED] [1200.070 seconds]
Basic upgrade test upgrade [It] successfully finishes control plane nodes rolling update if it is needed
/app/internal/upgrade/upgrade.go:106

  [FAILED] Timed out after 1200.001s.
  Expected
      <bool>: false
  to be true
  In [It] at: /app/internal/upgrade/upgrade.go:146 @ 05/14/24 16:27:17.439

In the past I've encountered a CP nodes isn't draining because of cert-manager, I bet it'll be that. I'll try again manually with 3 CP nodes (worked with 1)

I tested manually

Create WC on 0.51.0
Upgrade to this PR
worked fine

Last one and then I'll give up on E2E passing for this PR
/run cluster-test-suites

I was babysitting this run. It was working but slow and timed out during the rolling of the CP nodes.


Detect interpolation issues (followup)

Followup to PR #3931 by @simoncozens
This pull request addresses the problems described at issue #3930.

@simoncozens, why did you add the Munkres dependency (at https://github.com/googlefonts/fontbakery/pull/3931/commits/9555dddd9ceeb7a20b9f38c9576c80367dbdf273 included in PR #3931)?
I'm not seeing the dependency being actually used in the code-changes introduced in that PR.

@simoncozens, why did you add the Munkres dependency

It's needed for fontTools.varlib.interpolatable to work:
    try:
        from scipy.optimize import linear_sum_assignment

        rows, cols = linear_sum_assignment(G)
        assert (rows == list(range(n))).all()
        return list(cols), _matching_cost(G, cols)
    except ImportError:
        pass

    try:
        from munkres import Munkres

        cols = [None] * n
        for row, col in Munkres().compute(G):
            cols[row] = col
        return cols, _matching_cost(G, cols)
    except ImportError:
        pass

    if n > 6:
        raise Exception("Install Python module 'munkres' or 'scipy >= 0.17.0'")

@simoncozens, why did you add the Munkres dependency

It's needed for fontTools.varlib.interpolatable to work:

I believe munkres should then be explicitly declared as a dependency of fonttools

It's an option, so we should use fontTools[interpolatable].

using the fonttools[interpolatable] extras is going to install scipy which is much faster than the pure python munkres (the latter is used for pypy as scipy had issues with it IIRC)

latest scipy already dropped support for 3.7, only support 3.8+.
In fonttools requirements.txt (used to set up testing environment) we do this:
https://github.com/fonttools/fonttools/blob/155c32c2d0500247e599d7bad5fc9dedc7349c1a/requirements.txt#L6-L7
scipy==1.7.3; platform_python_implementation != "PyPy" and python_version <= '3.7'  # pyup: ignore
scipy==1.9.3; platform_python_implementation != "PyPy" and python_version > '3.7'

Maybe fonttools's setup.py should do the right thing and pin scipy to 1.7.3 for cpython <= 3.7..

munkres should then be explicitly declared as a dependency of fonttools

it wouldn't be too bad if you were to require it directly in fontbakery's own setup.py

it wouldn't be too bad if you were to require it directly in fontbakery's own setup.py

yes, that's what I am doing on the 0.8.11a3 release, but it feels like manually taking care of dependencies of an upstream dependency.

That’s how optional dependencies work.

If I add fonttools[interpolatable] will I still need to explicitly add munkres as well? If that's the case, then it is broken.

you would't need to add munkres in that case; if you think this interpolation check is a core fontbakery feature and you want it to run as fast as possible, then you you can let fonttools[interpolatable] in turn pull in the relatively heavier scipy dependency (it in turn requires numpy, but there are wheels nowadays); if you don't want to burden fontbakery users with those indirect deps and are happy with running the interpolation checks a bit slower and in pure-python, then require munkres explicitly and don't specify fonttools[interpolatable] extra. This is also fine and by design, it is not broken.

let fonttools[interpolatable] in turn pull in the relatively heavier scipy dependency (it in turn requires numpy

@felipesanches please be mindful of the bloat impact. FontBakery already has a very large footprint #3874

Yeah. If one is interested in a faster interpolation check they can always install scipy alongside fontbakery and fonttools will prefer to pick that one when available.

This is why I went for munkres instead of scipy.

Thanks for the clarification, @simoncozens
I think we're already with the good setup on requirements.txt and setup.py right now. So no further changes are needed.


preheater return error 2

Describe the bug
First of all, thx for this repository and hard work, rly appreciate it!
I have truble to start setPreHeater function. When I start this function, API return me error 2.
Is this working in MySkoda app?*
Yes, but this functionality is called Auxiliary Heater and I'm little confuse about that.
Latest working release
Debug logs
paste service
Installation:

Home Assistant variant: Hass OS
Python version 3.11
Python library versions 1.2.7

Additional context
I'm not sure if I get this functionally get right, coz all I want is to start car heater from HA and straight through was to call *_parking_heater_heating  switch to ON, but error 2 occur appears.

https://github.com/skodaconnect/homeassistant-skodaconnect/issues/188

Related to this? #188

Thx for replay, but I don't know, because even if I send "new" heat time duration and then send switch on at *_parking_heater_heating nothing change. Or mby I'm doing it all wrong and I should send *_parking_heater_ventilation instead of *_parking_heater_heating?

@sodd
I think you need to have the payed for version of "Care Connect"
I have setup as mentioned in #188.
Working fine, as long as Skoda servers are "online".

@sodd did you get this working? I don't have a car with parking heater so I can't test this. I'm not seeing either *_parking_heater_ventilation or *_parking_heater_heating in the example updated in #205 . Where does that come from? If this isn't working for you we'll need debug logs from the integration.


Breaks app.import styles

I have 2 CSS files I'm importing in my ember-cli build file. As soon as this addon is installed they no longer get brought into vendor.css

@optikalefx did you try the latest beta..?

I haven't I'll give it a shot

yea that works. Great.

Same issue here.

@webark when is this landing in a stable version?

Ya, the primary thing that needs to be fleshed out is the plain CSS support. Right now you have to add something to import the file in manually, which is a breaking change from the previous version (it would automatically tack it on to the vendor CSS). Want to find a better solution. And cool. If anyone come across this, please upgrade to the beta, and if you are still experiencing issues, open a new ticket. Thanks!


Issues using gt parameter on date search for AllergyIntolerance

When running the searches date=gt2017-10 or date=gt2017-10-19, a bundle with 0 results is returned.
date=gt2017-10: 10001, 10003, 10004, 10005, 10006... is expected
date=gt2017-10-19:  100007, 100018, 100032 is expected
date=gt2016 does seem to work correctly.

Entered in Error. Retested and works correctly.