`SampleApp': double free or corruption

2017-08-29 07:52:34.602 [ 17] 9 MediaPlayer:setSourceForUrlCalled
2017-08-29 07:52:34.618 [ 18] 0 MediaPlayer:handleSetSourceForUrlCalled
2017-08-29 07:52:34.629 [ 18] 9 MediaPlayer:tearDownPipeline
2017-08-29 07:52:34.630 [  7] E HTTP2Transport:networkLoopCleanupFailed:reason=curlFailure,method=curl_multi_remove_handle,error=Er
*** Error in `SampleApp': double free or corruption (!prev)Sync time from web server now!
: 0x000cbf00 ***
[  590.480444] Dequeue

Hi @NyxRockchip2017,
Can you provide more detail on how to reproduce this issue?  Specifically:

What SDK version are you using?
Have you modified anything in the source code, or is this the standard SampleApp?
What hardware platform and operating system release are you running this on?
What specific steps do you take to trigger this error?
Is the problem consistent or intermittent?
If intermittent, about how often does it occur?

Thanks,
Ken

The SDK version is v1.0.2 and I don't modify the source code.
I integrated customize board (linux-buildroot-arm32).
I don't trigger the device and place it for some hours,the SampleApp is crash.

Hi @NyxRockchip2017,
I will leave a raspberry pi board running SampleApp sitting idle overnight and will watch for crashes.
  There are calls to MediaPlayer::setSourceForUrl immediately prior to the crash.  Do you have a log from the crash when it is sitting idle?  What steps lead to the crash in the log you pated above?
Ken

The crash happened when we set the network.
[ 4458.891045] CFG80211-ERROR) wl_cfg80211_event : ignore event 4, not interested

[ 4458.893486] CFG80211-ERROR) wl_cfg80211_event : ignore event 4, not interested

[ 4458.897556] CFG80211-ERROR) wl_cfg80211_event : ignore event 8, not interested

[ 4458.994225] CFG80211-ERROR) wl_cfg80211_event : ignore event 12, not interested

[ 4459.086955] CFG80211-ERROR) wl_cfg80211_event : ignore event 4, not interested

[ 4459.087454] CFG80211-ERROR) wl_cfg80211_event : ignore event 4, not interested

[ 4459.094535] CFG80211-ERROR) wl_cfg80211_event : ignore event 4, not interested

[ 4459.098546] CFG80211-ERROR) wl_cfg80211_event : ignore event 4, not interested

[ 4459.101851] CFG80211-ERROR) wl_cfg80211_event : ignore event 8, not interested

[configServer]: accept a new client, ip:<IP_ADDRESS>, port:40176

[configServer]: Come wifi list requeset from client.

[configServer]: scan useable: OK

[configServer]: list size: 1

[configServer]: Close client sockfd.

[configServer]: accept a new client, ip:<IP_ADDRESS>, port:46745

[configServer]: Come wifi list requeset from client.

[configServer]: scan useable: OK

[configServer]: list size: 24

[configServer]: Close client sockfd.

[configServer]: accept a new client, ip:<IP_ADDRESS>, port:41520

[configServer]: Come companion info requeset from client.

[configServer]: parse companionInfo json into member value success.

[configServer]: m_sessionId = db628128-c3e9-4496-86f3-de962e37787f.

[configServer]: m_clientId = amzn1.application-oa2-client.fd7d2150df1340189d647e782c78d205.

[configServer]: m_redirectUri = amzn://com.rockchip.alexa.jacky.

[configServer]: m_authCode = ANiTehFJhbJYizqSUocH.

[configServer]: m_codeVerifier = OPN5DYgKK8KNSoaGHHYBK6qzg3elqPqCAG7dOnVQ5Yo.

[configServer]: Close client sockfd.

[configServer]: accept a new client, ip:<IP_ADDRESS>, port:38914

[configServer]: Come wifi setUp requeset from client.

staring connect to:TP-LINK_7E3A:pzb123456

execute:wpa_cli -iwlan0 set_network 1 ssid \"TP-LINK_7E3A\"

execute:wpa_cli -iwlan0 set_network 1 psk \"pzb123456\"

execute:wpa_cli -iwlan0 select_network 1

[ 4466.469328] CFG80211-ERROR) wl_cfg80211_disconnect : Reason 3

[ 4466.471996] wl_iw_event: Link Down with BSSID=34:96:00:00:7E:3A

[ 4466.472647] CFG80211-ERROR) wl_is_linkdown [configServer]: Wpa connected success, start thread to do udhcpc and check.

[configServer]: Close client sock: Link down Reason : WLC_E_LINK

[ 4466.472690] link down if wlan0 may call cfg80211_disconnected. event : 16, reason=2 from 34:9fd.

6:72:c6:7e:3a

[ 4466.484736] cfg80211: Calling CRDA to update world regulatory domain

[ 4466.518718] Connectting with 34:96:72:c6:7e:3a channel (11) ssid "TP-LINK_7E3A", len (12)

[ 4466.518718]

[ 4466.555425] wl_iw_event: Link UP with BSSID=34:96:00:00:7E:3A

[ 4466.559995] wl_bss_connect_done succeeded with 34:96:72:c6:7e:3a

udhcpc: started, v1.25.0

/usr/share/udhcpc/default.script: line 74: can't create /etc/resolv.conf: Read-only file system

[ 4466.748517] CFG80211-ERROR) wl_cfg80211_event : ignore event 16, not interested

[ 4466.749790] wl_bss_connect_done succeeded with 34:96:72:c6:7e:3a

udhcpc: sending discover

udhcpc: sending select for <IP_ADDRESS>

udhcpc: lease of <IP_ADDRESS> obtained, lease time 7200

/usr/share/udhcpc/default.script: line 74: can't create /etc/resolv.conf: Read-only file system

/usr/share/udhcpc/default.script: line 74: can't create /etc/resolv.conf: Read-only file system

[configServer]: Congratulation: wifi connected.

postData:grant_type=authorization_code&code=ANiTehFJhbJYizqSUocH&redirect_uri=amzn://com.rockchip.alexa.jacky&client_id=amzn1.application-oa2-client.fd7d2150df1340189d647e782c78d205&code_verifier=OPN5DYgKK8KNSoaGHHYBK6qzg3elqPqCAG7dOnVQ5Yo

2017-08-29 03:52:35.223 [ 1f] 0 HttpPost:doPostSucceeded:code=200

body: {"access_token":"Atza|IwEBIMGvJL-Lkc3nGR4GAxmg-lUs3REG1drgLa37wL5uO4yWvQKkBH51nDlisCyQrl5K-fHVPhkKj9fjQ12FvzX2_C2mpmvMwN_wMFkBLGFQvxUzgjQH9FJd-Ky4NuDuIOtwNsd0_GoifYZJfBXu-7PMABxJULJfxpjAAyFhvK9RsGr5ouQgi1elL8REEeEeM5nFyEndzppVPfMLNITsq8FPPmDCbVFLAue1Af8kCsRxknHDLFrp97K4RtRlvbPIWrD5AO42ZzHXw7BUFkqAvI650-TI6Aj0CIpbj-w8jgO8g5Er0kgsJ7iJrfOyI7KTJ1am-R-LDBqfm1K9a1fmSfg3qLIdL8dp3jnWsoBIzlT2ese55K1ggIW7u7vbom6r9sVMFBa2nc5tQAaOG4FiR1MQzmt4CC-l2jEEc8d7AUJAjk72gS9QmTLFCgOP-0SiTAdCkntQR33npdb2z9VAkXZzpO23PRvSzg47VvVv754PnlZa7fG1_8AHwfyuIE0Ah6GZKFer_5s6n017exiAaiMyPk6OnxEGKoW85RYZbp8md3Wq3Q","refresh_token":"Atzr|IwEBIDN7oDacTiYuUsn4T1eY-j5QPTZ7PRMbrLBNohdQNy9AWSeRu-dSYT8fBqiaI6NLqyWSsrolCUlnvMUhVQnTBoNCGWavSrHr7WRRsWshD8WULJ011AqtebKtlbpyeVPIAjUNEMLWtK8umRuN--M-wKXjMrGBGwvJAe2NZ2jFLtu3T8xCKZs3MegjLCpUPTk1Bx1ZWXoabH9PmLwqSX_LVRZWsOav-gktSlM1L04oqOTAmw8oWtC1p7Of4h_g0jomWmcdPqZDn-anHTPgkOW1T7WB8P9jJGuqkEeYPf0lJfeXXQvZok7q4V5eo4g5HIMyOjwu8Oeq6g1dlyz4q0EvetTtlj6CPl6v_QeXGZDLA5ii0jOirEezUNfYiwICAPwk85i9GOGLiA9-YJ9HuM5l5YTUGi7QXD0WVFWRmdqVSNl69Od6rfIIqR1nuVmXJCMMWJ2YMjjMktmTQyhRNg-Qp5tI3SjqUlNxNk3MSvptRF2OYVCn5CzYO4D1DhJsC09JBGQE1uqsRoyMjC3wsBk01tgC3NiVXBGiK9ckA7z8ZUVjzQ","token_type":"bearer","expires_in":3600}

[configServer]: httpPost success.

[configServer]: m_accessToken = Atza|IwEBIMGvJL-Lkc3nGR4GAxmg-lUs3REG1drgLa37wL5uO4yWvQKkBH51nDlisCyQrl5K-fHVPhkKj9fjQ12FvzX2_C2mpmvMwN_wMFkBLGFQvxUzgjQH9FJd-Ky4NuDuIOtwNsd0_GoifYZJfBXu-7PMABxJULJfxpjAAyFhvK9RsGr5ouQgi1elL8REEeEeM5nFyEndzppVPfMLNITsq8FPPmDCbVFLAue1Af8kCsRxknHDLFrp97K4RtRlvbPIWrD5AO42ZzHXw7BUFkqAvI650-TI6Aj0CIpbj-w8jgO8g5Er0kgsJ7iJrfOyI7KTJ1am-R-LDBqfm1K9a1fmSfg3qLIdL8dp3jnWsoBIzlT2ese55K1ggIW7u7vbom6r9sVMFBa2nc5tQAaOG4FiR1MQzmt4CC-l2jEEc8d7AUJAjk72gS9QmTLFCgOP-0SiTAdCkntQR33npdb2z9VAkXZzpO23PRvSzg47VvVv754PnlZa7fG1_8AHwfyuIE0Ah6GZKFer_5s6n017exiAaiMyPk6OnxEGKoW85RYZbp8md3Wq3Q.

[configServer]: m_refreshToken = Atzr|IwEBIDN7oDacTiYuUsn4T1eY-j5QPTZ7PRMbrLBNohdQNy9AWSeRu-dSYT8fBqiaI6NLqyWSsrolCUlnvMUhVQnTBoNCGWavSrHr7WRRsWshD8WULJ011AqtebKtlbpyeVPIAjUNEMLWtK8umRuN--M-wKXjMrGBGwvJAe2NZ2jFLtu3T8xCKZs3MegjLCpUPTk1Bx1ZWXoabH9PmLwqSX_LVRZWsOav-gktSlM1L04oqOTAmw8oWtC1p7Of4h_g0jomWmcdPqZDn-anHTPgkOW1T7WB8P9jJGuqkEeYPf0lJfeXXQvZok7q4V5eo4g5HIMyOjwu8Oeq6g1dlyz4q0EvetTtlj6CPl6v_QeXGZDLA5ii0jOirEezUNfYiwICAPwk85i9GOGLiA9-YJ9HuM5l5YTUGi7QXD0WVFWRmdqVSNl69Od6rfIIqR1nuVmXJCMMWJ2YMjjMktmTQyhRNg-Qp5tI3SjqUlNxNk3MSvptRF2OYVCn5CzYO4D1DhJsC09JBGQE1uqsRoyMjC3wsBk01tgC3NiVXBGiK9ckA7z8ZUVjzQ.

[configServer]: m_expiresInSeconds = 3600.

2017-08-29 03:52:35.476 [ 1f] I ConfigurationNode:initializeSuccess

2017-08-29 03:52:35.491 [ 1f] 0 MessageRouter:connectionStatusChanged:reason=ACL_CLIENT_REQUEST,newStatus=DISCONNECTED

################################################

#       May AuthDelegate recreated just!       #

################################################

-----mode OFF-------

2017-08-29 03:52:35.523 [ 1f] 9 MediaPlayer:setSourceForUrlCalled

2017-08-29 03:52:35.537 [ 20] 0 MediaPlayer:handleSetSourceForUrlCalled

2017-08-29 03:52:35.552 [ 20] 9 MediaPlayer:tearDownPipeline

2017-08-29 03:52:35.576 [  2] 0 MediaPlayer:callingOnPlaybackPaused

2017-08-29 03:52:35.603 [ 1a] E HTTP2Transport:networkLoopCleanupFailed:reason=curlFailure,method=curl_multi_remove_handle,error=Error

*** Error in `SampleApp': double free or corruption (!prev): 0x0016b830 ***

[ 4470.521187] Dequeue

[ 4470.521282] Dequeue

[ 4470.521300] Dequeue

[ 4470.521314] Dequeue

[ 4470.521328] Dequeue

[ 4470.521343] Dequeue

[ 4470.521354] Dequeue

[ 4470.521371] dwc_otg_hc_halt: hcchar.b.chen 1, ep_type 1

[ 4470.521390] Dequeue

[ 4470.521421] dwc_otg_hc_halt: hcchar.b.chen 1, ep_type 1

[ 4470.523509] snd_usb_pcm_close: line 1139

[ 4470.523537] usb_set_interface: alternate 0

[ 4470.523843] dwc_otg_hcd_endpoint_disable: line 658!!!!!!!!!!!!!!!!

Hi @NyxRockchip2017,
Can you clarify what you mean by "set the network"?  I am able to connect/disconnect the network repeatedly while the sample app is running, without crashes.  I do see an issue with leaving the SampleApp running while the network is disconnected; after several minutes I see a crash.  We have a ticket filed to address that, but I'm not clear if it's the same issue you are encountering here.
Ken

Hi Ken，
thks，this issue mayb produce by the code that we add to receive the wifi ap infomation from the phone app.

Hi @NyxRockchip2017 , any updates on the issue? Is it resolved?

Yeah,it was resolved，thks

can you close the issue? Thanks!


Use default number of attempts (3) for get_work rpc method.

Our workers die from time to time because of:
luigi.rpc.RPCError: Errors (1 attempts) when connecting to remote scheduler 'localhost'

This happens a lot more often when calling the get_work method than other RPC methods. Unlike all other RPC methods, get_work uses only one retry attempt and I don't really understand if there's a reason for it. I suspect additional two attempts were unintentionally cut off in 725172e3d8d970a505931a2556cda9a235dd2373

Wait, what?
This looks great and all and I would like to merge. But can you add a test case as well @jkukul?

@Tarrasch I pushed again, with a test case this time.

Thanks. I'll wais for @erikbern to review this though. He might remember why he did 725172e back in the days. :)

There's a flake8 error @jkukul

@Tarrasch fixed, sorry about that

did you try this in production yet?

Not yet. I'll deploy it to production and get back to you after it will have been working smoothly for a while.

Thanks @jkukul. This change makes sense to me. But it doesn't hurt to be on the safe side.
The bad thing I think can happen is that you keep asking for get_work but the client doesn't get the replies, so it keeps asking for it. Doing two add_task isn't harmful, but two get_work will alter state more than just one get_work would.

Haha, there's so many ex-spotifiers in #174 :)

@jkukul , I have a worry about log_exceptions=False. Why did you drop it?

@toidi, The reason log_exceptions=False was true initially was that it was =False for the initial call, and then retried 2 times with =True. See the commits and surrounding history that @jkukul linked to.

So this has been running for us in production for more than a week now, without any side effects.


add: MAYUR AJIT SAHARE

Description

Related Issues

Changes Proposed

Checklist

[x] I have read and followed the Contribution Guidelines.
[x] All new and existing tests passed.
[x] I have updated the documentation to reflect the changes I've made.
[x] My code follows the code style of this project.
[x] The title of my pull request is a short description of the requested changes.

Screenshots
Note to reviewers

Hi @sahare-mayur-0071 , thanks for your interest in contributing to DevDisplay!
We noticed you adding your profile on #DevDisplay but forgot to star the repo. It's like making an amazing sandwich and forgetting to take a bite! -- I think our repo's feeling a little lonely without your 🤗 So, be sure to star the DevDisplay GitHub Repository. 🌟
💌 This is a mandatory step for all contributors. & It's is the first priority of contribution in DevDisplay 💌
Thanks 👍🏻


use embedded-hal::digital::v2

Hello.
I try use last stm32f1xx-hal (along as onewire) in my project and found errors:
error[E0277]: the trait bound `heat_control_f103::gpiob::PBx<heat_control_f103::Output<heat_control_f103::stm32f1xx_hal::gpio::OpenDrain>>: heat_control_f103::_embedded_hal_digital_OutputPin` is not satisfied
   --> src/main.rs:249:33
    |
249 |     let mut wire = OneWire::new(&mut one, false);
    |                                 ^^^^^^^^ the trait `heat_control_f103::_embedded_hal_digital_OutputPin` is not implemented for `heat_control_f103::gpiob::PBx<heat_control_f103::Output<heat_control_f103::stm32f1xx_hal::gpio::OpenDrain>>`
    |
    = note: required because of the requirements on the impl of `onewire::OpenDrainOutput` for `heat_control_f103::gpiob::PBx<heat_control_f103::Output<heat_control_f103::stm32f1xx_hal::gpio::OpenDrain>>`
    = note: required for the cast to the object type `dyn onewire::OpenDrainOutput`

error[E0277]: the trait bound `heat_control_f103::gpiob::PBx<heat_control_f103::Output<heat_control_f103::stm32f1xx_hal::gpio::OpenDrain>>: heat_control_f103::_embedded_hal_digital_InputPin` is not satisfied
   --> src/main.rs:249:33
    |
249 |     let mut wire = OneWire::new(&mut one, false);
    |                                 ^^^^^^^^ the trait `heat_control_f103::_embedded_hal_digital_InputPin` is not implemented for `heat_control_f103::gpiob::PBx<heat_control_f103::Output<heat_control_f103::stm32f1xx_hal::gpio::OpenDrain>>`
    |
    = note: required because of the requirements on the impl of `onewire::OpenDrainOutput` for `heat_control_f103::gpiob::PBx<heat_control_f103::Output<heat_control_f103::stm32f1xx_hal::gpio::OpenDrain>>`
    = note: required for the cast to the object type `dyn onewire::OpenDrainOutput`

Using  embedded_hal::digital::v2 solves this problem, so what you say about this PR?
unwrap() in method read() at line 458 looks ugly, but I don't found better solution.. Any ideas?

Hmm, it seems Void would be replaced with Infallible in future:
https://github.com/rust-embedded/embedded-hal/pull/150

I second this PR. Thanks for the work!

Dang it. I totally missed this PR.
Will look into it after work today in the evening!

The current version 0.3.13 generifies over the actual pin-error-type.
This should mean that Void, Infallible and even legacy () should work.
Feel free to comment on that change and / or open a new issue for discussion (having a discussion in a merged/closed ticket gets lost so fast...)


chore(chip): reflect filter chip selected value

In a chip set context, there are currently no way to query selected chips from the outside
(e.g. queryAll('md-filter-chip[selected]')).
This PR solves that problem.

I'm curious, what's the context where you need to querySelector the chips instead of using the chip-set's chips property?
const chipSet = document.querySelector('md-chip-set');
const selectedChips = chipSet.chips.filter(chip => (chip as MdFilterChip).selected);

I'm curious, what's the context where you need to querySelector the chips instead of using the chip-set's chips property?
const chipSet = document.querySelector('md-chip-set');
const selectedChips = chipSet.chips.filter(chip => (chip as MdFilterChip).selected);

Sorry I didn't know about that one.
But don't you think it's an interesting improvement? It supports declarative querying.

Yes, though when will a client need that? The only place I can think of is CSS, but we have dedicated "selected" tokens for different selection styling.
I'm not strongly opposed to it right now, but I know we've had to adjust reflecting the attributes of some components to mimic native behavior. Notably, <select>'s <option> does not reflect its selected property to an attribute.

Side note: I want to adopt the element internals states api for state querying as a future feature.
const selectedChips = document.querySelectorAll('md-filter-chip:--selected');
const removableChips = document.querySelectorAll('md-filter-chip:--removable');

I don't really see a case where one would want to style a chip using CSS, maybe for changing the opacity of unselected chips??
Anyway I just thought it was more intuitive, the solution you provided doesn't bother me that much, it's just the query selector solution was the first I tried without jumping into the doc or into the source code.
We can use selected attribute to initially select chips, I just thought clients would naturally think it's reflected?
Another thing, let's imagine there are many chipsets for different subjects, you can query all selected chips using the selector version, whereas the JS solution would require to concat all filtered chips from all queried chipset...


Maxx Redwine

Maxx had a lifelong struggle with diabetes and passed in early 2011.
June 24, 1964 - January 31, 2011

https://www.dignitymemorial.com/obituaries/kennesaw-ga/maxx-redwine-4544321


add sign_in_second_factor claim to FirebaseInfo

Fixes https://github.com/firebase/firebase-admin-go/issues/619. These fields are available in the node SDK.

I see @Xiaoshouzi-gh was assigned, could you PTAL?

@Xiaoshouzi-gh friendly ping


Add suspense boundary

fixes https://nextjs.org/docs/messages/missing-suspense-with-csr-bailout
▲ Next.js 14.1.0

⨯ useSearchParams() should be wrapped in a suspense boundary at page "/authenticate". Read more: https://nextjs.org/docs/messages/missing-suspense-with-csr-bailout

Error occurred prerendering page "/authenticate". Read more: https://nextjs.org/docs/messages/prerender-error

@peckjon thanks for opening up! This repo is still on Next.js 13.x, looks like you're using 14.x here.
Was this the only error you encountered while running this example app on Next.js 14?

Thanks @chris-stytch! Yes that's correct. Not sure if this futureprofing patch is backward compatible?
That's my only trouble so far, I think the rest are related to my domain config. Am working with support to resolve. Thanks!


Add the channel gains of beads to the output excel file within the beads tab

Quickly identifying the gain of bead files allows the user to double check that the beads were measured at the gains which the samples were measured at. This feature in past versions of FC has been very helpful in diagnosing data irregularities.

Commit a77a8c6da7dc0ef047b13fd5cdefdd318932dba1 implements this. In addition to printing the detector voltage (gain) to the beads sheet, the program now also prints the acquisition time and the number of (gated) events. Running it against the example files gives the correct results as far as I can tell.
@felixekn please test it if you can. @taborlab/flowcal-developers, if there is no proposed change or complain within the next 24 hours, I'll merge into develop.
I think #38 would not be hard to implement after this.


PHP Fatal error:  Class 'CValidator' not found in /opt/lampp/htdocs/magento2/app/code/Ubertheme/Ubdatamigration/lib/yii/validators/CCompareValidator.php on line 39

I installed and upgrade the module successfully. When I run the "setup:di:compile" it throw the error
PHP Fatal error:  Class 'CValidator' not found in /opt/lampp/htdocs/magento2/app/code/Ubertheme/Ubdatamigration/lib/yii/validators/CCompareValidator.php on line 39

@satyapackirisamy,
If you can access to the back-end of our migration tool, you can run this command to solve the issue you mentioned.
rm -rf /opt/lampp/htdocs/magento2/app/code/Ubertheme/Ubdatamigration/lib/
However, our script here uses an outdated codebase, thus we no longer maintain and replace with a newer Pro version here.
We highly recommend you consider our Pro version, it definitely saves you pretty much time.
Regards,
Ubertheme team

Thank you for your valuable Reply.

Glad we can help.
As mentioned above, the current script you're using might have unexpected issues due to the outdated codebase. Anyway, you can proceed a testing migration if you choose to.
Regards,
Ubertheme team


Providing the context menu on mouseover instead of right mouse click

Hi,
Thanks for OS this cool utility. I integrated it and it works quite nicely.
On the project I integrated this in, they would love to have a way of making the context menu show on any mouseover event. As I saw in the source code, this is currently not supported. Do you think this could be added as an option or do you have a practical reason not to add this?
If you want to, I could provide a PR with the necessary changes to do so.
Kind regards

You should be able to do it without a PR.  See here.  Just use (mouseover) to trigger the context menu.

My bad! Thanks for the swift response!


image/png handling

Hello, thanks a lot for this great tool.
Is this possible to handle image mime type ?
If I do a screenshot and put it in the clipboard, it appear in the history.
For example:
maim --select --hidecursor --highlight --color=0.3,0.4,0.6,0.3 --bordersize=3 --format=png --quality=10 | xclip -selection clipboard -t image/png
But if I select it in rofi, I have just the following in the clipboard
�PNG

Hello,
Sadly I will not implement the feature as due to how rofi and greenclip interact with each other, the end result will be flaky.

Hello,
Sadly, I will not implement the feature as due to how rofi and greenclip interact with each other, the end result will suck without a lot of rework.
Rofi doesn't know about greenclip and greenclip does not know about Rofi.
Rofi responsibility is to display a list of lines and greenclip responsibility is to provide this list and advertise the selected one.
In order to support image handling, I should convert them to their hash each time you want to display the history which will be quite expansive and slow for big images or if you have a lot of images in your history.
So I will have to change the backend format from a flat file to something smarter to avoid doing this.
Once the new backend is ready, I will have to implement mime support in greenclip, which seems to be full of legacy tricks from what I can see from other clipboard-managers.
While this is technically feasible, I doubt I will implement it as it require a lot of rework (and debugging sessions) for it to be viable. Maybe in a 3.0 version but for now I don't have a lot of free time.

I released a 3.0-beta with mime support (images at least) https://github.com/erebe/greenclip/releases/tag/3.0
You can give it a shot if you want.
Be aware that it only handle small images < 500ko as beyond it use an incremental protocol to transfer data and as due to how greenclip interact with other clipboard app (it does not steal it in order to not break other apps features) it consume to much CPU.

just tested it, it works really well.
I had to remove ~/.cache/greenclip.history before starting the daemon because of an error:
~ ❯ greenclip print
greenclip: Data.Binary.Get.runGet at position 104: not enough bytes
CallStack (from HasCallStack):
  error, called at libraries/binary/src/Data/Binary/Get.hs:342:5 in binary-<IP_ADDRESS>:Data.Binary.Get

Thanks for reporting it, I should put a warning somewhere for the migration.


Sample Videos Not Working

When I try to run the command
./kvs_gstreamer_file_uploader_sample Demonstrate /sample-video/package.mp4 date +%s
It generates an error as
[ERROR] kvs_gstreamer_file_uploader_sample : File start time is not a valid number.

When I try to run the command ./kvs_gstreamer_file_uploader_sample Demonstrate /sample-video/package.mp4 date +%s
It generates an error as [ERROR] kvs_gstreamer_file_uploader_sample : File start time is not a valid number.

So I copied the videos from sample-video folder to amazon-kinesis-video-streams-producer-sdk-cpp/build folder and then tried to execute the same command as mentioned earlier. But, I got same error.
Then, I made changes in nano file as:

sudo nano ~/.bashrc
Once the file opens, scroll to the end of file and add below entries
export GST_PLUGIN_PATH=:$GST_PLUGIN_PATH
export AWS_ACCESS_KEY_ID=
export AWS_SECRET_ACCESS_KEY=
export AWS_DEFAULT_REGION=
Save the file changes.
Then try to run video upload command again

But, again I got the same error


no instructions on how to enable pgaadauth_* functions

This page suggests using several functions whose names begin with pgaadauth_. When I try to use them, I get errors like
ERROR:  function pgaadauth_list_principals(boolean) does not exist

When I type \df in psql, the list of functions doesn't show any like this. I thought perhaps there was a server extension I needed to enable, but in the list of available extensions (az postgres flexible-server parameter show -n azure.extensions -o tsv --query allowedValues), none have a name containing ad, active, or dir. I'm not sure what else to try from here.

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

ID: c454ed0e-944b-2933-ff30-5969ff0de1c9
Version Independent ID: 6f69997e-b534-e573-154d-7116e189d3c9
Content: Manage Azure Active Directory Users - Azure Database for PostgreSQL - Flexible Server
Content Source: articles/postgresql/flexible-server/how-to-manage-azure-ad-users.md
Service: postgresql
Sub-service: flexible-server
GitHub Login: @achudnovskij
Microsoft Alias: anchudno

@dhduvall
Thanks for your feedback! We will investigate and update as appropriate.

Hi @achudnovskij,
Could you please look into this document request. Thanks

Hi @dhduvall .
Those functions are part of "pgaadauth" extension installed on "postgres" database once you enable Azure AD authentication on a Flexible Server.
If you enabled the Azure AD authentication and still don't see the functions, please open a support ticket.

Thank you; I've done just that.

@dhduvall - can we close this?

Not yet; we're making progress in the support ticket, but there are still a couple of unanswered questions, and I think changes will need to be made to this page as a result. If you'd rather have that as a separate ticket, though, that's up to you.

The support ticket ID is<PHONE_NUMBER>002257. I have everything I need, so I'll let you work it out on your end what needs to be closed and how.

Closing this PR as support ticket<PHONE_NUMBER>002257 to track the issue. Please feel free to reopen the PR if you need any other info.

@please-close

Hi @dhduvall . Those functions are part of "pgaadauth" extension installed on "postgres" database once you enable Azure AD authentication on a Flexible Server. If you enabled the Azure AD authentication and still don't see the functions, please open a support ticket.

Hi,
I have provisioned a postgres DB through terraform with:
authentication {     active_directory_auth_enabled = true     ...     }
But I don't see the extension installed on the database.
Does the installation happen only when enabling through the Azure Portal?
Where can I open a support ticket for this?

Hi All, is there a resolution to this? I am also having this problem.

facing same, any update on this


Setting minute to a value from 00-09 causes leading zero to be cut off

What it looks like:

What it should look like:

Thanks
Fixed in: 68f1a53


[Port] Event tracing in the runtime

rheventtrace.cpp, eventtrace.cpp only exist on the TFS side.
This is used to e.g. implement RhpEtwExceptionThrown that is used to generate tracing events when managed exceptions are thrown.
For now, this issue tracks both porting the files to git, and also making them crossplat. We can split the crossplat part off later.
When this is fixed, remove CORERT-TODO: RhpEtwExceptionThrown in Exception.cs.

#7293.


WIP: fast track critical pending outtx by reducing re-try interval

Description
Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
Closes:
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Include instructions and any relevant details so others can reproduce.

[ ] Tested CCTX in localnet
[ ] Tested in development environment
[ ] Go unit tests
[ ] Go integration tests
[ ] Tested via GitHub Actions

Checklist:

[ ] I have added unit tests that prove my fix feature works

this was already merged in another PR.


⚠ Bofrost.de has degraded performance

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

HTTP code: 200
Response time: 1244 ms

Resolved: Bofrost.de performance has improved in 2c8842f after 13 minutes.


renaming node, renaming topics does not work as expected

I have a distributed ROS system with three computers. I would like to start on every computer the cpu_monitor under a different name. In the launch files on the different machines I set up the following:

<node pkg="cpu_monitor" name="computer1_cpu_monitor" type="monitor.py" output="screen">
<node pkg="cpu_monitor" name="computer2_cpu_monitor" type="monitor.py" output="screen">
<node pkg="cpu_monitor" name="computer3_cpu_monitor" type="monitor.py" output="screen">

Unfortunately on all three computers still the same topic "namespace" is used and brings the same topic names like:
/cpu_monitor/total_cpu
instead of
/computer1_cpu_monitor/total_cpu
/computer2_cpu_monitor/total_cpu
/computer3_cpu_monitor/total_cpu
Looking in the script I found that topic prefix is hard coded. In order solve this I applied the following patch:
index 4671a9c..f7bccb7 100755
--- a/monitor.py
+++ b/monitor.py
@@ -24,8 +24,8 @@ class Node:
   def __init__(self, name, pid):
     self.name = name
     self.proc = psutil.Process(pid)
-    self.cpu_publisher = rospy.Publisher(ns_join("cpu_monitor", name[1:], "cpu"), Float32, queue_size=20)
-    self.mem_publisher = rospy.Publisher(ns_join("cpu_monitor", name[1:], "mem"), UInt64, queue_size=20)
+    self.cpu_publisher = rospy.Publisher(ns_join(rospy.get_name(), name[1:], "cpu"), Float32, queue_size=20)
+    self.mem_publisher = rospy.Publisher(ns_join(rospy.get_name(), name[1:], "mem"), UInt64, queue_size=20)

   def publish(self):
     self.cpu_publisher.publish(Float32(self.proc.cpu_percent()))
@@ -45,7 +45,7 @@ if __name__ == "__main__":
   node_map = {}
   ignored_nodes = set()

-  cpu_publish = rospy.Publisher("cpu_monitor/total_cpu", Float32, queue_size=20)
+  cpu_publish = rospy.Publisher("%s/total_cpu" % rospy.get_name() ,Float32, queue_size=20)

   mem_topics = ["available", "used", "free", "active", "inactive", "buffers", "cached", "shared", "slab"]

@@ -54,7 +54,7 @@ if __name__ == "__main__":

   mem_publishers = []
   for mem_topic in mem_topics:
-    mem_publishers.append(rospy.Publisher("cpu_monitor/total_%s_mem" % mem_topic,
+    mem_publishers.append(rospy.Publisher("%s/total_%s_mem" % (rospy.get_name(),  mem_topic),
                                           UInt64, queue_size=20))

   while not rospy.is_shutdown():

Thanks for bringing this up. I've pushed commit https://github.com/alspitz/cpu_monitor/commit/e14953bc108b943fed556fbd6344cd61a9291551 which uses the private name space, and will cause all topic names to fall under the node name. I believe that's simplest unless there is some benefit to calling get_name directly?


Added cronjobs.

Fixes #207.

Coverage decreased (-0.33%) to 59.62% when pulling 7b14ab210b7d9be47833cc60c05479549d6e6c9e on rhyolight:cron into 11fbecc65a9e95e7bafc2b27611cf26cadd192da on numenta:master.


Next

Hello! Sorry, was away for a few days. I don't have access to a computer right now (mine broke) so I'll check back when my new laptop arrives in the mail.

Okay, thanks!
On Sat, 7 Sept 2024, 09:57 lain ping tool, @.***> wrote:

Hello! Sorry, was away for a few days. I don't have access to a computer
right now (mine broke) so I'll check back when my new laptop arrives in the
mail.
—
Reply to this email directly, view it on GitHub
https://github.com/AlexHayton/jaenokhwa/pull/3#issuecomment-2335123561,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAPM7Q32AIL3MDCG4P6A6TZVK5YVAVCNFSM6AAAAABNOT5AX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZVGEZDGNJWGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

I'm ready to start working, I just want to ask, why is this being merged into itself?

I kept it separate from the main branch because the convert-to-rgb example
isn't working on this branch, yet.
I'm planning to dig into it soon (next week or so) but got a bit sidelined
by other work.
I am guessing the next big thing to do is to work more on the
cross-platform colour conversion?
I think in most cases the desired output will be RGB or RGBA... But I like
that if you just want to know what the FourCC was and to handle it yourself
you can do that. We could create a separate helper lib that goes from
fourCC -> enum value to help people out there?
On Sat, 14 Sept 2024 at 09:33, lain ping tool @.***>
wrote:

I'm ready to start working, I just want to ask, why is this being merged
into itself?
—
Reply to this email directly, view it on GitHub
https://github.com/AlexHayton/jaenokhwa/pull/3#issuecomment-2350913432,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAPM7S5C3LXJBDYF4RSOODZWPYF5AVCNFSM6AAAAABNOT5AX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJQHEYTGNBTGI
.
You are receiving this because you authored the thread.Message ID:
@.***>

I kept it separate from the main branch because the convert-to-rgb example
isn't working on this branch, yet.
I'm planning to dig into it soon (next week or so) but got a bit sidelined
by other work.

Makes sense, but honestly if we merge this into main the example would have to be redone anyway... so many changes made to main that at least a quarter to half of it has been changed. Being honest, other than that there isn't much for me to do here - I would need to see the diffs in the main repo.

I am guessing the next big thing to do is to work more on the
cross-platform colour conversion?

I suppose we could just wrap dcv-color-primitives or fork it to add our own stuff.

I was hoping to move it all to the GPU layer, if possible. Ideally we could
do the processing far faster that way
On Sat, 14 Sept 2024, 14:34 lain ping tool, @.***>
wrote:

I kept it separate from the main branch because the convert-to-rgb example
isn't working on this branch, yet.
I'm planning to dig into it soon (next week or so) but got a bit sidelined
by other work.
Makes sense, but honestly if we merge this into main the example would
have to be redone anyway... so many changes made to main that at least a
quarter to half of it has been changed. Being honest, other than that there
isn't much for me to do here - I would need to see the diffs in the main
repo.
I am guessing the next big thing to do is to work more on the
cross-platform colour conversion?
I suppose we could just wrap dcv-color-primitives or fork it to add our
own stuff.
—
Reply to this email directly, view it on GitHub
https://github.com/AlexHayton/jaenokhwa/pull/3#issuecomment-2350993651,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAPM7VUQZPJUWVMRJC4QWLZWQ3OPAVCNFSM6AAAAABNOT5AX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJQHE4TGNRVGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

We could probably provide just a "Converter" trait then implement it later, like what Ive been trying to do in main.


remove Kubernetes as the group seems to have been dissolved

https://groups.google.com/g/kubernetes-wg-naming/c/e_F2r4y9xls

Thank you for your suggestion and for following through with making a pull request. Just documenting my clarification and understanding here before I make the approval step:

https://groups.google.com/g/kubernetes-wg-naming/c/e_F2r4y9xls

Just to make sure I understand this change, this question is for anyone — is the following accurate?

There was once an active working group in Kubernetes.
Soon after it formed, some of the WG members realized an ecosystem-wide approach would be helpful, and the Inclusive Naming Initiative (INI) was born.
Once INI was formed and active, the WG decided to fold, with presumably many of the activities having moved to the INI.

Since that seems to be the case — and also since the referenced mailing list/group has been formally closed for almost 18 months — this makes sense to me. Thanks again for making the pull request.
/lgtm
/approve


Remove yaml files that are no longer used.

This PR is part of an effort to move or remove everything in the /docs/admin folder.

/approve


chore(main): release 1.1.0

:robot: I have created a release beep boop
1.1.0 (2024-01-02)
Features

project created (5bf4964)

Bug Fixes

fixes types; fixes reactivity (c9b438f)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/oqx/qwik-table/releases/tag/v1.1.0 :sunflower:


Merge 'ThreeMammals:master' into 'master'

Let's update your repo with latest top-commits from head repository.
That will allow to perform rebase-operation for feature branches without merge-commits.
⚠ Warning!
Use fast-forwarding, rebase option to merge please!

Alternatively,
Could you Sync fork please? This is preferred option!
After repo synchronization, close this PR please!


Deadline Exceeded 504 On Mass Edit

Operating System version: Linux Mint 19
Firebase SDK version: 4.3.0
Library version: Unsure (Latest?)
Firebase Product: firestore

Step 3: Describe the problem
I have a large set of users with a given set of data. I download the user data, repackage it and repost it. Pretty straight forward. However, I can only run about 600 users at a time before I get the following:
Traceback (most recent call last):
  File "/home/clive/repositories/refquest-pro/plus/python_files/PermissionsTranslator/venv/lib/python3.6/site-packages/google/api_core/grpc_helpers.py", line 96, in next
    return six.next(self._wrapped)
  File "/home/clive/repositories/refquest-pro/plus/python_files/PermissionsTranslator/venv/lib/python3.6/site-packages/grpc/_channel.py", line 416, in __next__
    return self._next()
  File "/home/clive/repositories/refquest-pro/plus/python_files/PermissionsTranslator/venv/lib/python3.6/site-packages/grpc/_channel.py", line 689, in _next
    raise self
grpc._channel._MultiThreadedRendezvous: <_MultiThreadedRendezvous of RPC that terminated with:
	status = StatusCode.DEADLINE_EXCEEDED
	details = "Deadline Exceeded"
	debug_error_string = "{"created":"@1590900128.216480777","description":"Error received from peer ipv4:<IP_ADDRESS>:443","file":"src/core/lib/surface/call.cc","file_line":1056,"grpc_message":"Deadline Exceeded","grpc_status":4}"
>

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "translate.py", line 49, in <module>
    for user in usersList:
  File "/home/clive/repositories/refquest-pro/plus/python_files/PermissionsTranslator/venv/lib/python3.6/site-packages/google/cloud/firestore_v1/query.py", line 775, in stream
    for response in response_iterator:
  File "/home/clive/repositories/refquest-pro/plus/python_files/PermissionsTranslator/venv/lib/python3.6/site-packages/google/api_core/grpc_helpers.py", line 99, in next
    six.raise_from(exceptions.from_grpc_error(exc), exc)
  File "<string>", line 3, in raise_from
google.api_core.exceptions.DeadlineExceeded: 504 Deadline Exceeded

Steps to reproduce:
What happened? How can we make the problem occur?
This could be a description, log/console output, etc.
Relevant Code:

import json

import firebase_admin
from firebase_admin import credentials, firestore

cred = credentials.Certificate('../serviceKey.json')
firebase_admin.initialize_app(cred)

db = firestore.client()

# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
# Build a dictionary object of all master data

# Process through every account
accountsRef = db.collection(u'accounts').stream()

# Create the final account object
accountObject = {}

# For every account in the portfolio
for account in accountsRef:

    # Get a reference for all of the conferences in the account
    conferenceRef = db.collection(u'accounts').document(account.id).collection(u'conferences').stream()

    # The array of conferences
    conferenceList = []

    # For every conference in the list
    for conference in conferenceRef:

        # add it to the array
        conferenceList.append(conference.id)

    # next add the compiled array to the account Object
    accountObject[account.id] = conferenceList

# # # # # # # # Error In here somewhere # # # # #
# Using an order_by and start_after here to restart after the timeout error kills the job
usersList = db.collection(u'users').order_by(u'email_address').start_after({u'email_address': u'email@email.com'}).stream()

i=1
for user in usersList:

    # For a given user
    userRef = db.collection(u'users').document(user.id)
    userData = userRef.get().to_dict()
    # userData = user.to_dict()

    # Check they have a membership
    if ('membership' in userData):

        accountsList = userData ['membership']

        permV2 = {}

        for refAccount in accountsList:

            flatConsortium = {}

            for confKey in userData['permissions']:

                # Block tthis consortium because its exempt
                if (refAccount != 'kIM78AbSsscMHVgzGosk'):

                    if confKey in accountObject[refAccount]:

                        flatConsortium[confKey] = True

            permV2[refAccount] = flatConsortium

        userRef.update({u'permissionsV2': permV2})

    # print('{}'.format(permV2))
    print(str(i) + ': ' + userData['email_address'])
    i = i + 1

Note that Firestore client is actually in the repo https://github.com/googleapis/python-firestore
You're likely to get a faster response if you report this there.

@crwilcox @BenWhitehead fya

@hiranya911  Thanks for your comment. I guess I thought this was the best place to put the comment but if there is somewhere I should move it to, please let me know!

Since you're updating users individually it seems unlikely that the individual updates are hitting a deadline exceeded. More likely is that streaming the usersList is what's timing out.
In streaming Google APIs, including Firestore, the RPC deadline applies to the entire stream, not the next result. This means with the default deadline of 60 seconds, you must process the all the stream results within that span.
There are a few things you can do to address this:

Process results faster, e.g. by collecting all the results usersList into a list separately from processing them. I wouldn't recommended this simple strategy if your list is large though.
You could also extend the deadline with a configuration similar to the one described in another issue, though in this case you'd use RunQuery as the RPC you're configuring, not Listen. You can't make the RPC deadline infinite though (I believe the max is less than 10 minutes) so this strategy will only buy you ~5-10x the results you're handling now.
Read results in a loop with a limited number of documents per query.

This last strategy will extend indefinitely (though you can combine it with the others). The idea is that you run the query with a limit and use the last document in the query to construct the start_after for the next query. This strategy will let you read all documents in a collection, no matter the collection size.


Define TransactionWatcher (similar to what we have in sdk-js)

Added in https://github.com/multiversx/mx-sdk-specs/pull/64.


[FR] - build transactions without outputs in cardano-cli

External
Area
Other   cardano-cli
Describe the feature you'd like
Currently, there seems to be no way to serialize raw transactions that would not have an output, which may indeed be convenient when signing certificates where the inputs cover the fees exactly.
Example of a valid command (tx with one output):
cardano-cli shelley transaction build-raw --tx-in 89ba28b30e5eebc7d37c0123713b9e6089b90e07b3fb7d33979dc8d443df646e#1 --tx-out addr_test1qrwzf2dkeseu6mcv3jtw8muvseqz55np5529269lgg6fvap60uya8h6v7e488xwzkpdl5g6dtg54vrp3rlzaknzfqugse3ujve+50 --ttl 42 --fee 42 --out-file tx_example.raw

But this one (the same except missing output) fails with Missing: --tx-out TX-OUT error even though a tx with no outputs should technically be a valid tx, if I understand correctly:
cardano-cli shelley transaction build-raw --tx-in 89ba28b30e5eebc7d37c0123713b9e6089b90e07b3fb7d33979dc8d443df646e#1 --ttl 42 --fee 42 --out-file tx_no_out.raw

diff --git a/cardano-cli/src/Cardano/CLI/Shelley/Parsers.hs b/cardano-cli/src/Cardano/CLI/Shelley/Parsers.hs
index e09e6a3f..08796631 100644
--- a/cardano-cli/src/Cardano/CLI/Shelley/Parsers.hs
+++ b/cardano-cli/src/Cardano/CLI/Shelley/Parsers.hs
@@ -501,7 +501,7 @@ pTransaction =
   pTransactionBuild :: Parser TransactionCmd
   pTransactionBuild = TxBuildRaw <$> pCardanoEra
                                  <*> some pTxIn
-                                 <*> some pTxOut
+                                 <*> many pTxOut
                                  <*> optional pMintMultiAsset
                                  <*> optional pInvalidBefore
                                  <*> optional pInvalidHereafter


Requesting a direct URL for private Objects should generate a 403 response

Example code of a failing test:
  @mock_s3
  def test_s3_private_object(self):
      s3 = boto3.resource('s3')
      bucket = s3.Bucket('test-bucket')
      bucket.create(ACL='private')
      bucket.put_object(ACL='private', Body=b'ABCD', Key='file.txt')
      direct_url = 'https://test-bucket.s3.amazonaws.com/file.txt'
      response = requests.get(direct_url)
      self.assertEqual(response.status_code, 403)  # Fails with a 200 status code

The ACL is set to private for the Bucket and the Object but then it's not being checked during the GET request.

@dablak Thanks for pointing this out (and for writing a failing test case!). I've implemented a portion of S3 ACL checking here: #1151
It's just a start so please extend it to fit your needs.

This is now fixed on master


Upgrade go-grpc-middleware to v2.1.0

This PR addresses https://github.com/openfga/openfga/issues/893.
It removes dependencies to go-grpc-middleware v1.4.0 existed in logging and recovery middlewares.
Description

Cloned grpc_ctxtags middleware to the project repository because it was deleted from go-grpc-middleware v2.0.0. It was required either get rid of grpc tags middleware or copy it to the openfga project to delete dependency on go-grpc-middleware without v1.4.0.

Firstly, I tried to migrate the logging middleware to logging.InjectField API  introduced in v2.0.0.
I couldn't complete this migration because I didn't find a way to pass Authorization Model ID from a handler to the logging middleware. Before, it was achieved by setting a key-value to the tag map and then reading all key-value pairs on the logging layer.
New API doesn't use the embedded map (as grpc_ctxtags does). Instead, it returns a context with the injected field. I didn't find a way to deliver this new context from the handler layer to PostCall function of the logging middleware.
Therefore, I decided to clone part of grpc_ctxtags middleware to the project and keep logging data propagation the same.

Upgraded grpc recovery middleware to v2. There were no breaking changes.

Metrics and traces were not affected by the upgrade.

References

Review Checklist

[x] I have clicked on "allow edits by maintainers".
[x] I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
[x] The correct base branch is being used, if not main
[x] I have added tests to validate that the change in functionality is working as expected

What is the standard around the go-grpc-middleware for this deprecation? What are other people doing? Do you have some examples you can share from other Go projects so that can help us make a more informed decision here.

@jon-whit,  the standard way is:

implementing package-specific logic on the project side (example for zap). These lib implementations were a part of the grpc-midleware v1 package but they are removed in v2.
2 change ctxtags functions to logging.Extract/Inject.

I've searched similar PRs on github but I've found only some basic scenarios where neither reporting interface was used nor logging was used on the handler layer (we use it to pass type system id into the middleware)
I didn't find a way to pass a new ctx from a handler back to logging.PostCall function without huge code changes.
Eventually, I decided to make small amount of changes in the existing code base and just add a part of the ctxtags middleware to keep the same logic where a map object is used.
Initially, I tried to migrate the logging middleware to logging.InjectField API  introduced in v2.0.0.


Illegal instruction

Migrated from Slack
People involved: @earosenberg

Erik Rosenberg
3:57 PM
Hi Kolen, new question: I am trying to run toast_ground_schedule on Blackett. I have a script to do this that seems to run fine on the interactive node but fails when I submit it as a job to the worker node. The error is on the toast_ground_schedule line with the error message "Illegal instruction". Is this something you've seen before? This is with your anaconda tarball btw
Kolen Cheung
8:34 PM
Oh, wow. I need a reproducible working example for this. I bet if you rerun it you might not be able to get the same error right away. My bet is that it lands on a node with very old processors that lacks some newer instructions? Probably related to AVX512.
8:35
If you still have the log, could you please send me the log? Specifically I want to have the address of the node. I want to see what that node is capable of.
New
Erik Rosenberg
8:47 PM
I did submit it a couple times with the same result. Here is the address line (I think) 	Transferring to host: <<IP_ADDRESS>:9618?addrs=<IP_ADDRESS>-9618+[2001-630-22-d0ff-5054-ff-fee9-c3d]-9618&alias=vm75.in.tier2.hep.manchester.ac.uk&noUDP&sock=slot1_4_1883_7e66_92777>
8:48
(the full log file and a bit more info here if helpful)
Gzip
preprocess_schedule_info.tar.gz

Hi, @earosenberg, I also need other files involved in that job including get_schedule.sh

Sure, here are all the files; apologies for not providing them earlier.
preprocess_schedule_full.tar.gz
I actually ran it again and it seemed to work this time but hopefully you can reproduce the error -- the new log file for the run that worked is in this tarball

As @ickc suspected, this appears to be an AVX problem. vm75 only has AVX, but your packaged conda environment seems to require at least AVX2. All other standard nodes in the testbed have at least AVX2, but not necessarily AVX512.
I've disabled vm75 for now and will remove it from the testbed later (this was planned anyway).

The current software environment I provided are compiled with AVX512, where at the time I prepared them, all available nodes to us are AVX512 capable. But that has recently changed as more nodes is made available to us.
There's 2 ways to tackle this in my mind but I haven't got time to reach this stage yet:

Use has_avx512f from Machine ClassAd Attributes — HTCondor Manual 23.1.0 documentation to request only AVX-512 capable nodes.
Prepare both AVX2 and AVX512 software environments and dispatch in runtime which one to load.

(1) can be used in the interim, and I plan to do (2) in the future upon testing. We will have more concrete plans when our machines arrive.
I will try to document (1) soon.

Please be aware that the majority of cores (~80%) of the current production cluster are AMD nodes (Zen 2 and Zen 3) which only support avx2 and will be unavailable if you use (1). This percentage will go up when we remove more nodes with Intel CPUs that are going out of warranty.

While I don't know the percentage before, I'm aware it probably won't be the majority of the nodes. My plan in the long run is to auto-dispatch it at run-time so that optimal compilation is selected automatically. Our procurement is still in process and this would depends also on what kind of machines we will buy. There's more incentive to do this if we are buying Intel nodes. It also will depends on benchmarks after our nodes arrived, but I anticipated AVX-512 would give significant performance boost in our stack from prior experience.
In a sense it also depends on how the fair-share system works in practice. If I have access to a smaller portion of the machine with longer queue time, but trading off with better performance hence smaller compute hours meaning that I can get more jobs done with the same fair-share, then it would be worth it. At NERSC there's something called NERSC hours and allocation year, so the concept of minimizing cost per job is very objective and easy to understand. But at Blackett it is not clear how that cost model would work out in practice, making optimization (more job given same fair-share) more difficult to reason with.

Closing, remaining items tracked in #7


Feature/add typescript type definitions

Why:
(Hi!) We've been using your wonderful module in a Front-End project that uses Typescript and to make things clearer for the devs (IDE intellisense) we wrote custom declaration files for it and included in the project itself. Although that works perfectly for us, we thought it might benefit others too, hence this PR.
How:
Given the fact that the module itself is written in JavaScript, we cannot automatically generate the declaration file. This means we wrote it manually by cross-referencing documentation and source code. Any updates to the module should be reflected in the declaration files as well to keep them up to date.
Need help:
Although I am comfortable writing Typescript, I'm by no means an expert at it, so I invite the community to improve my work.
One idea for the future would be to extend the Config interface by making it a generic interface, therefore Typescript could infer the return type of the fixtures method based on the request method.
Screenshots:

@Slashgear @DevSide any chance to get this merged and released?


Update React 16.12 & utilize hooks

covers PR 140
covers PR 142
covers PR 95
covers PR 68
will use this as a basis to update the rest of the package versions (react-router, redux etc).
will also update redux to use hooks

Hi @bahtou It looks like there is an error when i sign in:

and in the console:

Do you have any solution for this error? I am using django backend

Are you sure you:

checked out branch ver-class-updates of Bahtou's fork?
removed node_modules/ and package-lock.json and ran npm install again for a clean install of dependencies
cleared you browser's localStorage (where it saves a jwt token)

Doing these 3 things should fix your issue :)


Downloader Kotlin conversion.

Kotlin conversion completed.
Sample app using compose added.

Merging this PR to test Jitpack.


Process finished with exit code -1073740791 (0xC0000409)

after running the labelImg.py after 5 sec window automatically closed and giving me Process finished with exit code -1073740791 (0xC0000409) this kind of error

Maybe I can say something about this issue. This error occurs when trying to open txt file that you have already labeled. In other words, this error occurs when a labeled photo and the txt file belonging to this process are in the same directory.
I hope it will help you.


Remove version: ChrisBagwell.SoX version 14.4.2

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

Close with reason: URL works;


health-ep: provide netmask to spawn_netns

spawn_netns expects IP address with mask.
IP removal without mask using iputils might cause below error:
RTNETLINK answers: Cannot assign requested address
Warning: Executing wildcard deletion to stay compatible with old scripts.
Explicitly specify the prefix length (<IP_ADDRESS>/32) to avoid this warning.
This special behaviour is likely to disappear in further releases,
fix your scripts!

This change is

I wonder if there is any other way to retrieve max for IP provided by ipam.

Coverage increased (+0.09%) to 43.448% when pulling e9b76e70c98b5a4e88821320b15b86f63d39d48f on nirmoy:health_ip_fix into f0fdb07725f771be28f330519503f4818a251492 on cilium:master.

test-me-please

test-me-please

test-me-please

Seems unrelated
11:54:03 • Failure [481.132 seconds]
11:54:03 K8sUpdates
11:54:03 /home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:351
11:54:03   Tests upgrade and downgrade from a Cilium stable image to master [It]
11:54:03   /home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:383
11:54:03
11:54:03   Cannot curl app1-service
11:54:03   Expected command: kubectl exec -n default app2-75f77ffdbf-jcrtn -- curl -s -D /dev/stderr --fail --connect-timeout 3 --max-time 8 http://app1-service/public -w "time-> DNS: '%{time_namelookup}(%{remote_ip})', Connect: '%{time_connect}',Transfer '%{time_starttransfer}', total '%{time_total}'"
11:54:03   To succeed, but it failed:
11:54:03   Exitcode: 28
11:54:03   Stdout:
11:54:03    	 time-> DNS: '0.000000()', Connect: '0.000000',Transfer '0.000000', total '3.521539'
11:54:03   Stderr:
11:54:03    	 command terminated with exit code 28
11:54:03
11:54:03
11:54:03
11:54:03   /home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/k8sT/Updates.go:216

11:41:30 • Failure [383.577 seconds]
11:41:30 K8sChaosTest
11:41:30 /home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:351
11:41:30   Restart with long lived connections
11:41:30   /home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:351
11:41:30     L3/L4 policies still work while Cilium is restarted [It]
11:41:30     /home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:383
11:41:30
11:41:30     Failed while cilium was restarting
11:41:30     Expected command: kubectl exec -n default netperf-client -- netperf -l 300 -t TCP_STREAM -H <IP_ADDRESS>
11:41:30     To succeed, but it failed:
11:41:30     Exitcode: 1
11:41:30     Stdout:
11:41:30      	 MIGRATED TCP STREAM TEST from <IP_ADDRESS> (<IP_ADDRESS>) port 0 AF_INET to <IP_ADDRESS> (10.10.1) port 0 AF_INET
11:41:30     	 recv_response_timed_n: no response received. errno 104 counter 0
11:41:30     	 command terminated with exit code 1
11:41:30
11:41:30     Stderr:
11:41:30
11:41:30
11:41:30
11:41:30     /home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/k8sT/Chaos.go:260

test-me-please

test-me-please


Txgh sprint

Hi @szum !
It looks like you might've committed specific information about your environment.  Please be aware that any specific config (API keys, etc) can be put into environment variables that way you can avoid pushing them to GitHub.  If you need more details on how Txgh supports this, feel free to raise an issue!
Thanks


Add label-wrap feature

Codecov Report

Merging #16 (df9aa2e) into master (e5e49f9) will increase coverage by 0.09%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #16      +/-   ##
==========================================
+ Coverage   96.27%   96.37%   +0.09%
==========================================
  Files           6        6
  Lines         188      193       +5
==========================================
+ Hits          181      186       +5
  Misses          7        7

Impacted Files
Coverage Δ

airflow_diagrams/cli.py
97.91% <ø> (ø)

airflow_diagrams/utils.py
100.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 e5e49f9...df9aa2e. Read the comment docs.

@nathadfield this feature could be interesting for you. You could set --label-wrap to either a number or a separator to wrap the labels to new lines.

@feluelle Definitely!  Happy to give it a try when it's a available.

It is now available in 1.1.0rc1. I would really appreciate if you could test it. :)

Much better!


App router migration new relic configuration

Children PR for the progressive migration of _app.tsx and _document.tsx within the Root Layout
Issue link / number:
#1083
What changes did you make?
Created new relic configuration
Added new relic configuration to root layout
Why did you make the changes?
In order to be able to have new relic within app router
Did you run tests?
Yes
Navigate to http://localhost:3000/public-route-test to check that the head nr-browser-agent and body scripts are added properly

@annarhughes This PR needs to point to app-router-migration branch once #1085 is merged

@eleanorreem, @annarhughes I have just changed the base branch, have a look when possible. Thanks

Merged @boodland sorry for the delay.

Merged @boodland sorry for the delay.

No worries at all, very happy to help


Array allocation for dt64

Feature request

The usual ways of allocation for dt64 such as np.empty(n, dtype=np.dtype('datetime64[ns]')) and np.empty(10, dtype='datetime64[ns]') are required for parallel support.

You can implement np.dtype('datetime64[ns]') with intrinsic and overload.
See example in https://gist.github.com/sklam/c75538f86bb5899d41526ba97af2199b

Closing since this seems to be working in latest Numba.


Use acorn instead of esprima

According to esprima's benchmarks acorn is 2 times faster than esprima: http://esprima.org/test/compare.html
According to acorn benchmarks its 5 times faster in FF (10 times in Chrome) (open /test/bench.html from the acorn package).
Would be nice to use acorn instead of esprima, or at least provide an option which one to use for user. Both parsers produce the mostly the same AST conforming to Mozilla format, but esprima adds some extensions to it and instanbul relies on them.
For example, the Mozilla's AST definition for "ObjectExpression" does not define the "type" property for the items of the "properties" array:
interface ObjectExpression <: Expression {
    type: "ObjectExpression";
    properties: [ { key: Literal | Identifier,
                    value: Expression,
                    kind: "init" | "get" | "set" } ];
}

meanwhile esprima emits "type : "Property"" for such nodes (and istanbul relies on its presence). Shouldn't be hard either not rely on it, or add a feature request to "acorn" to add the same property.

@gotwarlost Do you have any plans for merging the now-removed acorn branch?

Why was Acorn removed?  Is it out of consideration now?
I just stumbled onto this thread from a web search.  I'm trying to choose between esprima and acorn in my new project.  Any thoughts would be appreciated.

@gotwarlost very old, close for good to inspire more people to use this very good solution?


About EffectNet Datasets

How much data did you use on the AffectNet7 and AffectNet8 datasets to train the model

We train and test according to the officially provided AffectNet-7cls and AffectNet-8cls. We will soon make the dataset link public.


Add Contact Form

This is my first time using PHP, so please let me know if there's anything that should be done differently or changed about this PR. Thank you!
Features

Adds contact form that sends slack message to a configured channel
Contact form uses hcaptcha with Scyllaly/hcaptcha to avoid spam
Adds laravelcollective/html to generate form fields
Also adds laravel/slack-notification-channel

Configuration

Generate a new Slack webhook URL for the specified channel and set the SLACK_CONTACT_WEBHOOK environment variable
Register a new HCaptcha account and add the sitekey and secret to the HCAPTCHA_SITEKEY and HCAPTCHA_SECRET environment variables.
Try out the new contact form!

I should also mention that I'm planning on making a separate bot to automatically post events from the OpenEvents API, and since that will hopefully go into HackGreenville eventually, the webhook URLs can just be generated from that to save integration slots.
Issues
Closes #46
Preview

Message preview:

My meta description changes from #111 have been merged in, so you should be able to sync up with develop and add a custom meta description to the new page / view
@section('title', 'Contact HackGreenville')
@section('description', 'Send non-spammy questions or comments to the HackGreenville community.')

Thank you for suggesting laravelcollective/html! I figured there was probably a better way to do the inputs but wasn't sure if there was something that I should add.
I also added form-groups to the inputs, so hopefully they should take more advantage of Bootstrap.
I also originally created a custom request, but wasn't sure if it was too verbose and then turned it into the facade :sweat_smile:. It's back to a full request now though :smile:
Unfortunately, it seemed that laravel collective's form builder possibly defaults to an http url, so I used the workaround in this issue: https://github.com/LaravelCollective/html/issues/447#issuecomment-576193331

Whoops, I approved it already. But, would you be able to remove the text-center class from the form? You can remove most of the classes from the form it'll continue to look good.

Removed some more classes, and this is what it looks like now

This may come in handy as the Typeform has hit it's monthly submission limit, as seen in #114
@Soulfire86 has been moderating the invites, so pinging him here too.

@Soulfire86 it sounds like there are options to have a contact form Slack integration go to an email, to a channel, and possibly even a private chat (assuming our free tier allows such things).  Thoughts for a direction for @oliviasculley  ?

This came up in today's Code For Greenville meeting.
I was initially figuring this contact form would dump into some channel in the HG Slack where anybody subscribed to the channel would see it and help co-moderate.
That sounds nice in the ideal case, but then edge cases cross the mind, like a disgruntled member posts to the contact form to report another member.  You might have someone venting and not realizing it goes straight to a public channel.
Perhaps a "Warning Label" on the form would make it clear the contents are for public moderation, but maybe this goes to a moderator. IDK.

This has been reviewed at length I'm merging this :100:


[Feat]: Create ISSUE_TEMPLATE, so others are can use to report bugs, pull requests and feature requests

Is your feature request related to a problem? Please describe.
When I am trying to create the issue, need to open multiple blogs to write well-mannered issue.
Describe the solution you'd like
Can create the ISSUE_TEMPLATES on github folder, so that others can create report bugs, features in a well-mannered.
Additional context
Can follow  this blog -> How can add templates in github projects

Hey @Nik4Furi thank you for bringing this up
I'm closing this issue as I just fixed it in the bellow commits
https://github.com/Abhishek-Mallick/universal-box/commit/37741435b8c8848c11fe530357c6db301fe8cb1c
https://github.com/Abhishek-Mallick/universal-box/commit/8798310b3c91087454539653884e48b0642e1502
https://github.com/Abhishek-Mallick/universal-box/commit/41bc100a1e1f56f797afd2bc907827bdd5df990a


QAT in docker container

Hi :
I ran into issue when QAT is in linux docker.
the application crash after it allocated memory via qat_contig_mem interface.
here is the trace . I have added few printk in qat_contig_mem driver.
Initially, I did my dev in a non-docker environment, and it works great. Now, because the way our product is implemented, I need to run similar things in docker.
[ 1198.973933] Started AE 0
[ 1198.973938] Started AE 1
[ 1198.973942] Started AE 2
[ 1198.973946] Started AE 3
[ 1198.973950] Started AE 4
[ 1198.973954] Started AE 5
[ 1198.973958] Started AE 6
[ 1198.973962] Started AE 7
[ 1198.973966] Started AE 8
[ 1198.973970] Started AE 9
[ 1198.973974] Started AE 10
[ 1198.973978] Started AE 11
[ 1257.223597]  qat_contig_mem: mem_open :  qat_contig_mem: do_ictl :  qat_contig_mem: do_ictl : memalloc virt 0000001fb4320000 phy ffff881fb4320000 len 20000
[ 1257.223623]  qat_contig_mem: do_mmap:  vm_start 00007ff1e0d42000 vm_end 00007ff1e0d82000 pfn 1fb4320 size 40000 page_Size 1000
[ 1257.223627]  qat_contig_mem: do_mmap 1 :  vm_start 00007ff1e0d60000 vm_end 00007ff1e0d80000 pfn 1fb4320 size 40000
[ 1257.223635] ------------[ cut here ]------------
[ 1257.223647] WARNING: CPU: 10 PID: 9888 at /build/linux-FyIZxz/linux-4.4.0/mm/mmap.c:1640 mmap_region+0x55b/0x650()
[ 1257.223649] Modules linked in: qat_contig_mem(OE) icp_qa_al(OE) xt_nat xt_tcpudp veth ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack br_netfilter bridge stp llc aufs iptable_mangle ip_tables x_tables intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp ipmi_ssif kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd joydev input_leds sb_edac edac_core mei_me mei shpchp ioatdma lpc_ich 8250_fintek ipmi_si ipmi_msghandler acpi_pad acpi_power_meter mac_hid sunrpc autofs4 hid_generic usbhid hid mxm_wmi ixgbe igb vxlan ip6_udp_tunnel dca udp_tunnel ahci ptp libahci pps_core megaraid_sas mdio i2c_algo_bit
[ 1257.223721]  fjes wmi [last unloaded: icp_qa_al]
[ 1257.223728] CPU: 10 PID: 9888 Comm: nsproxy Tainted: G           OE   4.4.0-77-generic #98-Ubuntu
[ 1257.223730] Hardware name: Netskope N1000/S2600WTTR, BIOS SE5C610.86B.01.01.0020.122820161512 12/28/2016
[ 1257.223733]<PHONE_NUMBER>000286 000000000c9af1d9 ffff881fb4353d48 ffffffff813f8493
[ 1257.223738]<PHONE_NUMBER>000000 ffffffff81cd3808 ffff881fb4353d80 ffffffff81081302
[ 1257.223741]  ffff880c825a81c0 00007ff1e0d60000<PHONE_NUMBER>000000 ffff88203203e320
[ 1257.223745] Call Trace:
[ 1257.223755]  [] dump_stack+0x63/0x90
[ 1257.223764]  [] warn_slowpath_common+0x82/0xc0
[ 1257.223768]  [] warn_slowpath_null+0x1a/0x20
[ 1257.223771]  [] mmap_region+0x55b/0x650
[ 1257.223775]  [] do_mmap+0x333/0x420
[ 1257.223785]  [] vm_mmap_pgoff+0xaf/0xe0
[ 1257.223790]  [] SyS_mmap_pgoff+0x1c1/0x290
[ 1257.223800]  [] SyS_mmap+0x1b/0x30
[ 1257.223810]  [] entry_SYSCALL_64_fastpath+0x16/0x71
[ 1257.223813] ---[ end trace d4a34ce431bc2e7d ]---
[ 1257.223939]  qat_contig_mem: do_ictl :  qat_contig_mem: do_ictl : memalloc virt 0000001fb42a0000 phy ffff881fb42a0000 len 20000
[ 1257.223947]  qat_contig_mem: do_mmap:  vm_start 00007ff1e0d20000 vm_end 00007ff1e0d60000 pfn 1fb42a0 size 40000 page_Size 1000
[ 1257.223949]  qat_contig_mem: do_mmap 1 :  vm_start 00007ff1e0d40000 vm_end 00007ff1e0d60000 pfn 1fb42a0 size 40000
Please advice
tseng

Hi Tseng,
The issue you are seeing above is just a warning rather than an actual crash of any kind.
Have a look at the following issue: https://github.com/01org/QAT_Engine/issues/18 especially the last comment I added.
You'll only see this warning on the very first memory allocation with the qat_contig_mem driver, you should not see it after that unless the qat_contig_mem driver is reloaded. The kernel is just making you aware that the driver is doing something that could be considered unusual and changing the start address of the region that is being memory mapped.
Apart from the warning in the trace are you seeing any other functional issues after?
Kind Regards,
Steve.

Thank you for your quick response.
It is probably related to permission.
Since I have never seen this before , I assume it is related to docker.
In the past, I always ran as standalone not in docker container.
Tseng
From: stevelinsell<EMAIL_ADDRESS>Sent: Wednesday, May 10, 2017 3:06 AM
To: 01org/QAT_Engine
Cc: tsenghu; Author
Subject: Re: [01org/QAT_Engine] QAT in docker container (#23)
Hi Tseng,
The issue you are seeing above is just a warning rather than an actual crash of any kind.
Have a look at the following issue: #18 https://github.com/01org/QAT_Engine/issues/18  especially the last comment I added.
You'll only see this warning on the very first memory allocation with the qat_contig_mem driver, you should not see it after that unless the qat_contig_mem driver is reloaded. The kernel is just making you aware that the driver is doing something that could be considered unusual and changing the start address of the region that is being memory mapped.
Apart from the warning in the trace are you seeing any other functional issues after?
Kind Regards,
Steve.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/01org/QAT_Engine/issues/23#issuecomment-300436788 , or mute the thread https://github.com/notifications/unsubscribe-auth/APaHlwDGyf92RHZt8xp_n06v96Pm1SQtks5r4Yv6gaJpZM4NVtNg .  https://github.com/notifications/beacon/APaHl1g9z3lrpWHNxVY0wtYfIwDHd7lPks5r4Yv6gaJpZM4NVtNg.gif

Hi, I wanted to try QAT in docker container, but I did not find docs on how to enable it in docker containers. Could you tell me where I can found the related documents? Thanks a lot.

Hi kchen-sh
As far as I'm aware, QAT has not been packaged in a docker container and therefore no documentation yet exists regarding this.
Regards,
Paul Turner


Unable to flash

I have just got one of these to fiddle with - was hoping to install the yi-hack-v4 firmware, but realised on arrival that it was the new 9FUS version.  For some reason, despite the version and firmware matching those described in the readme, I cannot get to to flash.  Probably something I am doing wrong, but thought I would post here in case it is an issue.
Details
Camera: YI 1080p home camera, model 9FUSY31ZWT
Firmware: <IP_ADDRESS>A_201912270941
SD card: 16GB Sandisk ultra
Steps taken

Camera powered on, intial set-up completed with the Yi app to connect to WiFi
SD card inserted and formatted using the camera itself (FAT32)
Camera powered off, SD card inserted in PC, contents of archive copied to root of SD card (home_y20gam.stage and "Factory" and "newhome" folders.
SD card inserted to camera, camera powered on.

I have tried this a few times.  The camera comes on, yellow light shows for around 30 secs, then reboots again.  At that point the camera seems to boot normally, blue light flashes then steady and the camera is accessible through the Yi app.  The firmware upload does not appear to work.
Happy to troubleshoot further if you let me know what info you need.

OK - so it was probably just me.  I flashed with 0.1.3 and it seemed to work.  Then upgraded to 0.1.4 from within the web console and all running fine.
Thanks!


Expose setting to utilize dns.resolve automatically instead of falling back to dns.lookup

In a normal scenario if you do a request.get("http://www.foo.com") Node will perform a dns.lookup on www.foo.com. This is an asynchronous task in the Node event loop, but it utilizes a synchronous libuv thread. This is called out in the DNS docs, https://nodejs.org/api/dns.html#dns_dns_lookup.
You can see why this matters by looking at the following Node github issue (https://github.com/nodejs/node/issues/8436) and my comment on that issue at (https://github.com/nodejs/node/issues/8436#issuecomment-268322327).
Unless you utilize a custom flag, the libuv thread pool is only 4 deep. This means if you do 4 dns.lookups which are delayed for some reason, the entirety of anything governed by libuv is blocked until those returned. This means any IO is blocked until those dns requests resolve, which is really hard to debug since the Node event loop will be healthy, but IO requests will never complete.
Now, this entire operation is avoidable if dns.resolve() is used instead of dns.lookup(). From my tests dns.resolve() ignores /etc/hosts but still utilizes /etc/resolv.conf. So my suggestion would be expose a setting, which when passed dnsResolve : true then it will take the URL passed, extract the hostname, execute a dns.resolve on it, then alter the url to be by IP and pass a host header with the original value. In example request.get("http://www.google.com/test/") would be converted under the hood to request.get("http://<IP_ADDRESS>/test/", { headers : { host : "www.google.com" } }). All in all it's a fairly easy operation to make, and is essential for our use case. We would be willing to submit a pull request to get it into request if you believe it could be of value.

I think this is happening in my system too. Just jumping on board!
@owenallenaz Thanks for explaining it so well above.

If it was to use dns.resolve, we'd probably also want to consider IPv4 vs IPv6 and the case where mutliple IP's are returned. I was reading this issue regarding multiple IP's https://github.com/nodejs/node/issues/708

Out of the box dns.resolve only returns ipv4 results. dns.lookup will return the fastest ip that your getaddrinfo call returns, so it may be ipv4 or ipv6. If we exposed the setting I propose { dnsResolve : true }, it is possible that we could pass an argument similar to the family argument that is exposed on http.request where you can specify 4 or 6 to tell it whether to utilize dns.resolve4 or dns.resolve6.
The implementation for my idea is pretty basic, this is a rough example that I was able to get working by passing my own new Agent(). It just feels common enough that other people may want it, and thus should possibly be part of request core.
// in request.js where we create the agent
agent.createConnection = function(args, cb) {
	return net.createConnection({
		port : args.port,
		host : args.host,
		lookup : function(ip, args, cb) {
			return dns.resolve(ip, function(err, ips) {
				if (err) { return cb(err); }

				return cb(null, ips[0], 4);
			});
		}
	}, cb);
}

TLS should not be affected as this TLS, to my knowledge, has nothing to do with DNS and IP resolution. TLS is happening in the http layer which is after dns resolution has occurred.  Regarding the retrying that's mentioned in those github comments. I agree 100% with the Node authors that auto-retrying the same connection (or even in parallel as the commentors want) is not a good idea. We have to trust dns to return a functional IP. If it doesn't, the application shouldn't be blindly retrying all other possible IPs, that sort of "finding the right IP" should be done in the dns universe. There are numerous dns caching systems which can do a much better job at a much lower level than doing some awful parallel connection scheme which is what they were proposing.

I had similar issue with some library, turns out you can override default lookup function via agentOptions.lookup.
import dns from 'dns'

const customLookup = (hostname, options, callback) => {
  dns.lookup(hostname, { ...options, family: 4 }, callback)
}

const options  = {
  agentOptions: {
    lookup: customLookup
  }
}

// request.get(options)


Signer Offering Metadata Key Names

The names of the keys for the signer offering metadata event should be:

temperature (possible values: warm, cold, air-gapped)
response_time (time in minutes?)
device_type (the brand of the cold card)
cost_per_signature
monthly_cost_basis_points(percentage of the vault balance that should be charged)
monthly_cost

Valid values for Device type could be any string, but we should offer the below in the UI:

Coldcard
BitBox02
Ledger
Mobile device
Desktop/laptop device
Cloud-based
Other:
Undisclosed

@sebastianmontero I think the costs should be annual instead of monthly, even though fees may be charged monthly. It makes it easier to calculate the cost in days. Most recurring fees I've seen have been yearly basis points (100, or 1% per year).


expression matrix

Hello!
Thanks for your tools : ) But I am confused about the format of expression matrix.
Should it be raw counts or normalized (eg, TMMCPM) ones?Thx!

In case this package is still maintained by somebody, I would like to ask the same question. From the example, it looks like the counts are in TPM or something like that. Would it be possible to have some clarification about this?
The original GSVA package in R didn't offer much information about it either...


Serialize trap manifest and tables in lucet-module-data

Support for these is not landing in #16, but we would eventually like all of the module metadata to live in that structure.
The main challenge here will be keeping the amount of copying down, since the trap metadata is potentially quite large. To that end, we'll probably want to keep at least the tables, but potentially also the manifest as a byte slice to allow zero-copy deserialization. We'll want to be very careful with alignment when we do that.

This has been moved to ModuleData, and both are deserialized in a zero-copy manner. We still need to be very careful with alignment and layout if we change FunctionSpec or trap site layout in the future.


feat: patch-based requiresRestart

adds requires restart property to BasePatcher
prompt restarts based on that property when toggling patch
prompt restart when toggling plugin if any patches requiring restarts are enabled

Oof, I was actually working on that right now. Saw the PR a bit too late. Such a shame


Suggestion: Adding binder/binding information when throwing a BinderException

Version of the framework
spring-cloud-stream:3.1.3
spring-cloud-stream-binder-kafka:3.1.3
When starting an application with Spring Cloud Stream for the Kafka binder and the configuration of a binding is not correct, either because the target topic is not reachable or another reason, the exception and ERROR traces indicate neither the binding name, nor the binder (in case it is a multi-binder scenario) nor exception topic information in case the cause is UnknownTopicOrPartitionException.
We show an example of error trace when configuring a binding against a non-existent topic:
2021-07-28 13:40:52,029 [main] ERROR org.springframework.boot.SpringApplication - Application run failed
org.springframework.context.ApplicationContextException: Failed to start bean 'inputBindingLifecycle'; nested exception is org.springframework.cloud.stream.binder.BinderException: Cannot initialize binder:
	at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:181)
	at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:54)
	at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:356)
	at java.base/java.lang.Iterable.forEach(Iterable.java:75)
	at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:155)
	at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:123)
	at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:935)
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:586)
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:145)
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:754)
	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:434)
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:338)
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1343)
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1332)
	at com.inditex.ot.openfwkt.Application.main(Application.java:11)
Caused by: org.springframework.cloud.stream.binder.BinderException: Cannot initialize binder:
	at org.springframework.cloud.stream.binder.kafka.provisioning.KafkaTopicProvisioner.getPartitionsForTopic(KafkaTopicProvisioner.java:591)
	at org.springframework.cloud.stream.binder.kafka.KafkaMessageChannelBinder.getPartitionInfo(KafkaMessageChannelBinder.java:1120)
	at org.springframework.cloud.stream.binder.kafka.KafkaMessageChannelBinder.processTopic(KafkaMessageChannelBinder.java:869)
	at org.springframework.cloud.stream.binder.kafka.KafkaMessageChannelBinder.createConsumerEndpoint(KafkaMessageChannelBinder.java:625)
	at org.springframework.cloud.stream.binder.kafka.KafkaMessageChannelBinder.createConsumerEndpoint(KafkaMessageChannelBinder.java:158)
	at org.springframework.cloud.stream.binder.AbstractMessageChannelBinder.doBindConsumer(AbstractMessageChannelBinder.java:408)
	at org.springframework.cloud.stream.binder.AbstractMessageChannelBinder.doBindConsumer(AbstractMessageChannelBinder.java:91)
	at org.springframework.cloud.stream.binder.AbstractBinder.bindConsumer(AbstractBinder.java:143)
	at org.springframework.cloud.stream.binding.BindingService.doBindConsumer(BindingService.java:171)
	at org.springframework.cloud.stream.binding.BindingService.bindConsumer(BindingService.java:134)
	at org.springframework.cloud.stream.binding.AbstractBindableProxyFactory.createAndBindInputs(AbstractBindableProxyFactory.java:118)
	at org.springframework.cloud.stream.binding.InputBindingLifecycle.doStartWithBindable(InputBindingLifecycle.java:58)
	at java.base/java.util.LinkedHashMap$LinkedValues.forEach(LinkedHashMap.java:608)
	at org.springframework.cloud.stream.binding.AbstractBindingLifecycle.start(AbstractBindingLifecycle.java:57)
	at org.springframework.cloud.stream.binding.InputBindingLifecycle.start(InputBindingLifecycle.java:34)
	at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:178)
	... 14 common frames omitted
Caused by: org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server does not host this topic-partition.

It would be very useful that in the exception, at least the name of the binding that is causing it is indicated.

On the other hand, regarding the information of the cause of the BinderException(UnknownTopicOrPartitionException), whose message does not show the information of the name of the topic in question that has originated the error when trying to consult its metadata, there is an issue for this in Apache: https://issues.apache.org/jira/browse/KAFKA-13144

@garyrussell   any thoughts on this? If you think the addition proposed by @ferblaca is valuable we can try to contribute the change to Spring Cloud Stream.
In our projects a lot of teams access different topics  with different names by environment and is frequent to mistype a character or use one topic name in an environment where it is not valid. If the log showed this the troubleshooting will be instantaneous. Without this that have to increase the log level of Apache Kafka client to debug in every environment they have the problem.
What do you think?
P.D. We are aware that the complete solution would be having this change in SCS but also in the kafka client, but we have to begin with sth. 😄

@juliojgd A quick look at the code tells me it would be easy to add the topic name; adding the binding name would require more work because it is not currently available in the method that throws the exception.
A contribution would indeed be welcome; thanks.


w - Wrap the stack at the end of any function if the stack has more than one item

Ykw I've decided this  is kinda useless, it was suggested before builtins that make this obsolete.


Compile 'SSLService' problem: bn.h:187:19: error: integer literal is too large to be represented in any integer type

The following problem blocked our pushing swift application to Bluemix:
STG/0
Compile Swift Module 'SSLService' (1 sources)
Mar 7, 2017 11:41:08 AM
STG/0
/tmp/app/.apt/usr/include/openssl/bn.h:187:19: error: integer literal is too large to be represented in any integer type
Mar 7, 2017 11:41:11 AM
STG/0
^
Mar 7, 2017 11:41:11 AM
STG/0
^~~~~~~~~~~~~~~~~~~~~~
Mar 7, 2017 11:41:11 AM
STG/0
SSL_CTX_ctrl(context, SSL_CTRL_SET_ECDH_AUTO, 1, nil)
Mar 7, 2017 11:41:11 AM
STG/0
#define BN_MASK (0xffffffffffffffffffffffffffffffffLL)
Mar 7, 2017 11:41:11 AM
STG/0
OpenSSL.SSL_CTRL_SET_READ_AHEAD:1:12: note: did you mean 'SSL_CTRL_SET_READ_AHEAD'?
Mar 7, 2017 11:41:11 AM
STG/0
public var SSL_CTRL_SET_READ_AHEAD: Int32 { get }
Mar 7, 2017 11:41:11 AM
STG/0
^
Mar 7, 2017 11:41:11 AM
STG/0
^
Mar 7, 2017 11:41:11 AM
STG/0
public var SSL_CTRL_SET_SRP_ARG: Int32 { get }
Mar 7, 2017 11:41:11 AM
STG/0
/tmp/app/Packages/SSLService-0.12.25/Sources/SSLService.swift:817:31: error: use of unresolved identifier 'SSL_CTRL_SET_ECDH_AUTO'
Mar 7, 2017 11:41:11 AM
STG/0
OpenSSL.SSL_CTRL_SET_SRP_ARG:1:12: note: did you mean 'SSL_CTRL_SET_SRP_ARG'?
Mar 7, 2017 11:41:11 AM
STG/0
:0: error: build had 1 command failures
Mar 7, 2017 11:41:21 AM
STG/0
Failed to compile droplet
Mar 7, 2017 11:41:21 AM
STG/0
Exit status 223
Mar 7, 2017 11:41:21 AM
STG/0
Staging failed: Exited with status 223
Mar 7, 2017 11:41:21 AM
STG/0
Destroying container
Mar 7, 2017 11:41:21 AM
API/0
Failed to stage application: staging failed
Mar 7, 2017 11:41:21 AM
STG/0
swift-build: error: exit(1): /tmp/cache/swift-3.0.2/swift-3.0.2-RELEASE-ubuntu14.04/usr/bin/swift-build-tool -f /tmp/app/.build/release.yaml
Mar 7, 2017 11:41:21 AM
STG/0
Successfully destroyed container

We are also seeing this problem hitting in our Travis tests on Linux. There are two errors, one to do with the literal and one to do with an unresolved identifier.
/usr/include/openssl/bn.h:187:19: error: integer literal is too large to be represented in any integer type

#define BN_MASK         (0xffffffffffffffffffffffffffffffffLL)

                         ^

/tmp/87c06c14666f7ad8d15dbe70e37233d0b50cc764/notes/Packages/SSLService-0.12.25/Sources/SSLService.swift:817:31: error: use of unresolved identifier 'SSL_CTRL_SET_ECDH_AUTO'

                                SSL_CTX_ctrl(context, SSL_CTRL_SET_ECDH_AUTO, 1, nil)

                                                      ^~~~~~~~~~~~~~~~~~~~~~

OpenSSL.SSL_CTRL_SET_READ_AHEAD:1:12: note: did you mean 'SSL_CTRL_SET_READ_AHEAD'?

public var SSL_CTRL_SET_READ_AHEAD: Int32 { get }

           ^

OpenSSL.SSL_CTRL_SET_SRP_ARG:1:12: note: did you mean 'SSL_CTRL_SET_SRP_ARG'?

public var SSL_CTRL_SET_SRP_ARG: Int32 { get }

           ^

<unknown>:0: error: build had 1 command failures

error: exit(1): /home/travis/build/IBM-Swift/generator-swiftserver/swift-3.0-RELEASE-ubuntu14.04/usr/bin/swift-build-tool -f /tmp/87c06c14666f7ad8d15dbe70e37233d0b50cc764/notes/.build/debug.yaml

      1) "before all" hook

I see that this file has been added .swift-build-linux:
swift build -Xswiftc -DOPENSSL_TOO_OLD

If adding that option to swift build resolves the problem, then it looks like we have added a requirement to pass an option to any project that uses Kitura. :(

I agree with @tunniclm that adding a compile flag is not the way to fix this.

Removed the compile flag for the default.  The compile flag still exists in a different form.  It needs to be explicitly set to enable the functionality and this is documented in the README.md.  The functionality is provided by OpenSSL 1.0.2 or higher, this rules out use of it on Ubuntu 14.04.


Implement unsubscribe

Implemented in my fork: https://github.com/davidchappelle/AutobahnCpp

This can now be closed as this came in with the last merge of my fork.


Add veo_cv19_analyses_share.py

published version of script used to provide Covid-19 data updates to ELTE as part of the VEO project

I am out of office on jury service on a long trial until early
  March 2024.
I am unavailable for calls during the week but if there are any
  matters of priority I will be able to help with this.
Kind Regards, Jasmine

--

Jasmine McKinnon
User-Support Bioinformatician
ENA - European Nucleotide Archive
European Bioinformatics Institute (EMBL-EBI)

Hi Colman,
The specified information has been removed, and instead the named variables for this information are named at the start of the script as part of the script set up


ORC-1263: Doc: add decimal type to ORC Website

What changes were proposed in this pull request?

Add decimal type to ORC Website.
At present, there is no decimal type description in https://orc.apache.org/docs/types.html.
Why are the changes needed?

How was this patch tested?

Welcome to the Apache ORC community. I added you to the Apache ORC contributor group and assigned ORC-1263 to you.

cc @williamhyun since he is a release manager of Apache ORC 1.8.0.


Langgraph AGI

Is your feature request related to a problem? Please describe:
After closely observing agentic developers like opendevin and recent swebench score of sonnet3.5+tools(no agent), it's clear that agents sometimes over complicate the task resulting worse performance (Sonnets scores highest on verified list beating all agents)
Describe the solution you'd like:
Instead of having multiple agents running in the background, there should be only 1 agent(with possible subagents) working as the intermediary between bolt and the llm using langchain-openai-api-bridge. This way, the agent will serve only one purpose, which is to increase the general performance of the llm. This will also improve the quality of small llms.
Describe alternatives you've considered:
There could be multiple sets of intermediate agents that users can choose, i.e., COT, reflection, etc. Different mindmaps could be more effective for different models.
Additional context:
https://www.swebench.com/

Without me stumbling out of my comfort zone about LLM interactions, I'm not sure if a single agent serving as a bridge to Bolt is a valid constraint when multiple agents in a voting circle could potentially be used/necessary for things like useful code reviews inline, etc. - This is a good conversation worth having though and I'd love to get more context.


add all supported k8s versions to golden image

What this PR does / why we need it: install all k8s versions on the image
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
If applicable:

[ ] documentation
[ ] unit tests
[ ] tested backward compatibility (ie. deploy with previous version, upgrade with this branch)

Release note:

/lgtm