Why has iikira/BaiduPCS-Go been totally eliminated?

Shocked to realize that iikira/BaiduPCS-Go has been eliminated. Visited the project just one month or so ago, still active then.
So has the appveyor link where latest builds were regularly issued.
So has the QQ group, which cannot be searched for now.
What happened? And when did that happen? Will there be further updates on the project here or somewhere else?
Thx for any info.

iikira might deleted the repo because of the breaking change of baidu-api (As of this comment was made, all the download method has just broken except pcs), or because of the tea from Baidu legal department 😂.
The repo still exists when I download the new version of Baidupcs-go yesterday.
So, just stop using baidu pan anymore, it's not worth it...
By the way, when I try to download 美少女万華鏡 -理と迷宮の少女 yesterday with baidu svip used. The download speed is just 300k/s, WTF...

not allow to login with cookies

So sad about the deletion of the original repo. Hope that this reloaded one will survive...
And hope the author of the repo have not be threatened by Baidu corp..
PS: Well, 2L reminds me that I still have 100GB+ games and 300GB+ image sets in BaiduNetdisk... ( ๑ŏ ﹏ ŏ๑ ) I may just heard my small cloud server crying (-̩̩̩-̩̩̩-̩̩̩-̩̩̩-̩̩̩___-̩̩̩-̩̩̩-̩̩̩-̩̩̩-̩̩̩) cuz it must hold BaiduPCS-Go process and download from BaiduNetdisk day and night for a very long time and I do not have a SVIP...˚‧º·(˚ ˃̣̣̥᷄⌓˂̣̣̥᷅ )‧º·˚

iikira might deleted the repo because of the breaking change of baidu-api (As of this comment was made, all the download method has just broken except pcs), or because of the tea from Baidu legal department 😂.
The repo still exists when I download the new version of Baidupcs-go yesterday.
So, just stop using baidu pan anymore, it's not worth it...
By the way, when I try to download 美少女万華鏡 -理と迷宮の少女 yesterday with baidu svip used. The download speed is just 300k/s, WTF...

Guess iikira has been threatened by 'Certain Authorities'. Had thought a command-line tool would somehow survive. Things are getting out of control lately. WTF...
So, as of when your comment is made, does BaiduPCS-Go work? Is the 300K/s speed achieved with BaiduPCS-Go or with the 'Official' BaiduNetDisk program?
And, is it possible to share the latest build of PCS-GO? I only have v3.6.2 (amd64 exe) whose MD5 ends with A520...thx very much!

iikira might deleted the repo because of the breaking change of baidu-api (As of this comment was made, all the download method has just broken except pcs), or because of the tea from Baidu legal department 😂.
The repo still exists when I download the new version of Baidupcs-go yesterday.
So, just stop using baidu pan anymore, it's not worth it...
By the way, when I try to download 美少女万華鏡 -理と迷宮の少女 yesterday with baidu svip used. The download speed is just 300k/s, WTF...

Guess iikira has been threatened by 'Certain Authorities'. Had thought a command-line tool would somehow survive. Things are getting out of control lately. WTF...
So, as of when your comment is made, does BaiduPCS-Go work? Is the 300K/s speed achieved with BaiduPCS-Go or with the 'Official' BaiduNetDisk program?
And, is it possible to share the latest build of PCS-GO? I only have v3.6.2 (windows-amd64, BaiduPCS-Go.exe) whose MD5 ends with A520...thx very much!

works!(version v3.6.2-devel)

iikira might deleted the repo because of the breaking change of baidu-api (As of this comment was made, all the download method has just broken except pcs), or because of the tea from Baidu legal department 😂.
The repo still exists when I download the new version of Baidupcs-go yesterday.
So, just stop using baidu pan anymore, it's not worth it...
By the way, when I try to download 美少女万華鏡 -理と迷宮の少女 yesterday with baidu svip used. The download speed is just 300k/s, WTF...

Guess iikira has been threatened by 'Certain Authorities'. Had thought a command-line tool would somehow survive. Things are getting out of control lately. WTF...
So, as of when your comment is made, does BaiduPCS-Go work? Is the 300K/s speed achieved with BaiduPCS-Go or with the 'Official' BaiduNetDisk program?
And, is it possible to share the latest build of PCS-GO? I only have v3.6.2 (windows-amd64, BaiduPCS-Go.exe) whose MD5 ends with A520...thx very much!

works!(version v3.6.2-devel)

What's your version? I mean, what's the MD5 of your baidupcs-go.exe file?

v3.6.2 is the latest version, I believe. I pulled a request one month ago and I'm sure there is no code change since then.
All functions works well as usual, baidu-api change is not the reason, I think.
I also had a copy here, it's based on the latest version and a new function (transfer share link) was added, compiled file can be downloaded here (code: 4pix)
3.6.2应该是最新版本了，我这几天一直在关注这个项目，近期没什么变化。
今天测试一切工作正常，应该不是百度API更换导致的（实际上项目的下载API跟mac版、Linux版客户端用的是一个，所以不太可能突然就失效）
我上个月提交过一个增加了转存功能的版本，在这里，readme里有新功能的使用说明，其他与原作者提交的最新版本一致。已编译文件可在蓝奏云下载
https://ww.lanzous.com/b01berebe
密码:4pix

v3.6.2 is the latest version, I believe. I pulled a request one month ago and I'm sure there is no code change since then.
All functions works well as usual, baidu-api change is not the reason, I think.
I also had a copy here, it's based on the latest version and a new function (transfer share link) was added, compiled file can be downloaded here (code: 4pix)
3.6.2应该是最新版本了，我这几天一直在关注这个项目，近期没什么变化。
今天测试一切工作正常，应该不是百度API更换导致的（实际上项目的下载API跟mac版、Linux版客户端用的是一个，所以不太可能突然就失效）
我上个月提交过一个增加了转存功能的版本，在这里，readme里有新功能的使用说明，其他与原作者提交的最新版本一致。已编译文件可在蓝奏云下载
https://ww.lanzous.com/b01berebe
密码:4pix

感谢！我运行了你的已编译版本（win-x64），提示“注：分享链接转存功能无法使用，可使用-cookies参数重新登录以启用”。是说要使用分享链接转存功能，必须以-cookies="blabla"形式登陆，而不能用login分次输入用户名密码的方式登陆？

v3.6.2 is the latest version, I believe. I pulled a request one month ago and I'm sure there is no code change since then.
All functions works well as usual, baidu-api change is not the reason, I think.
I also had a copy here, it's based on the latest version and a new function (transfer share link) was added, compiled file can be downloaded here (code: 4pix)
3.6.2应该是最新版本了，我这几天一直在关注这个项目，近期没什么变化。
今天测试一切工作正常，应该不是百度API更换导致的（实际上项目的下载API跟mac版、Linux版客户端用的是一个，所以不太可能突然就失效）
我上个月提交过一个增加了转存功能的版本，在这里，readme里有新功能的使用说明，其他与原作者提交的最新版本一致。已编译文件可在蓝奏云下载
https://ww.lanzous.com/b01berebe
密码:4pix

感谢！我运行了你的已编译版本（win-x64），提示“注：分享链接转存功能无法使用，可使用-cookies参数重新登录以启用”。是说要使用分享链接转存功能，必须以-cookies="blabla"形式登陆，而不能用login分次输入用户名密码的方式登陆？
另，有个小问题，这个repo是从iikira的repo fork出来的吧，现在iikira的repo删了，所有readme里的指向iikira原始repo的链接全部作废了。这些dead link有办法恢复吗？比如我想知道如何找到BDUSS，但readme那个链接显然挂了。。

1.是的，因为转存功能需要用到的cookies字段比原版本设计的多几个
2.虽然原教程没了，但获取BDUSS的方法还是很容易搜到的，直接百度就行。另外获取cookies字段的方法，在新编译版本的login --help里也有提及。

iikira might deleted the repo because of the breaking change of baidu-api (As of this comment was made, all the download method has just broken except pcs), or because of the tea from Baidu legal department 😂.
The repo still exists when I download the new version of Baidupcs-go yesterday.
So, just stop using baidu pan anymore, it's not worth it...
By the way, when I try to download 美少女万華鏡 -理と迷宮の少女 yesterday with baidu svip used. The download speed is just 300k/s, WTF...

Guess iikira has been threatened by 'Certain Authorities'. Had thought a command-line tool would somehow survive. Things are getting out of control lately. WTF...
So, as of when your comment is made, does BaiduPCS-Go work? Is the 300K/s speed achieved with BaiduPCS-Go or with the 'Official' BaiduNetDisk program?
And, is it possible to share the latest build of PCS-GO? I only have v3.6.2 (windows-amd64, BaiduPCS-Go.exe) whose MD5 ends with A520...thx very much!

works!(version v3.6.2-devel)

@chendijun527 Hi, could you please share your baidupcs-go version and configure of your Baidupcs-go including download mode, max_parallel (which can be shown by using config command). And I wonder if you are a svip user. I'm afraid that using a too large parallel count will cause baidu banning my account.

@felixonmars @qjfoidnh
可以和这个比较下: https://gitee.com/mirrors/BaiduPCS-Go

v3.6.2 is the latest version, I believe. I pulled a request one month ago and I'm sure there is no code change since then.
All functions works well as usual, baidu-api change is not the reason, I think.
I also had a copy here, it's based on the latest version and a new function (transfer share link) was added, compiled file can be downloaded here (code: 4pix)
3.6.2应该是最新版本了，我这几天一直在关注这个项目，近期没什么变化。
今天测试一切工作正常，应该不是百度API更换导致的（实际上项目的下载API跟mac版、Linux版客户端用的是一个，所以不太可能突然就失效）
我上个月提交过一个增加了转存功能的版本，在这里，readme里有新功能的使用说明，其他与原作者提交的最新版本一致。已编译文件可在蓝奏云下载
https://ww.lanzous.com/b01berebe
密码:4pix

下载地址已失效了，请问有没有编译好的linux版本？多谢

v3.6.2 is the latest version, I believe. I pulled a request one month ago and I'm sure there is no code change since then.
All functions works well as usual, baidu-api change is not the reason, I think.
I also had a copy here, it's based on the latest version and a new function (transfer share link) was added, compiled file can be downloaded here (code: 4pix)
3.6.2应该是最新版本了，我这几天一直在关注这个项目，近期没什么变化。
今天测试一切工作正常，应该不是百度API更换导致的（实际上项目的下载API跟mac版、Linux版客户端用的是一个，所以不太可能突然就失效）
我上个月提交过一个增加了转存功能的版本，在这里，readme里有新功能的使用说明，其他与原作者提交的最新版本一致。已编译文件可在蓝奏云下载
https://ww.lanzous.com/b01berebe
密码:4pix

下载地址已失效了，请问有没有编译好的linux版本？多谢

https://gitee.com/littleye233/BaiduPCS-Go-reuploaded/attach_files/409715/download
我这边蓝奏似乎挂了，只能用gitee凑合，似乎有点慢，但是应该可用

v3.6.2 is the latest version, I believe. I pulled a request one month ago and I'm sure there is no code change since then.
All functions works well as usual, baidu-api change is not the reason, I think.
I also had a copy here, it's based on the latest version and a new function (transfer share link) was added, compiled file can be downloaded here (code: 4pix)
3.6.2应该是最新版本了，我这几天一直在关注这个项目，近期没什么变化。
今天测试一切工作正常，应该不是百度API更换导致的（实际上项目的下载API跟mac版、Linux版客户端用的是一个，所以不太可能突然就失效）
我上个月提交过一个增加了转存功能的版本，在这里，readme里有新功能的使用说明，其他与原作者提交的最新版本一致。已编译文件可在蓝奏云下载
https://ww.lanzous.com/b01berebe
密码:4pix

下载地址已失效了，请问有没有编译好的linux版本？多谢

https://gitee.com/littleye233/BaiduPCS-Go-reuploaded/attach_files/409715/download
我这边蓝奏似乎挂了，只能用gitee凑合，似乎有点慢，但是应该可用

蓝奏云我测试是OK的，不清楚是否在某些地区有访问限制。
gitee的地址我这里无法访问，登录后依旧提示受限，不知是不是个例。

v3.6.2 is the latest version, I believe. I pulled a request one month ago and I'm sure there is no code change since then.
All functions works well as usual, baidu-api change is not the reason, I think.
I also had a copy here, it's based on the latest version and a new function (transfer share link) was added, compiled file can be downloaded here (code: 4pix)
3.6.2应该是最新版本了，我这几天一直在关注这个项目，近期没什么变化。
今天测试一切工作正常，应该不是百度API更换导致的（实际上项目的下载API跟mac版、Linux版客户端用的是一个，所以不太可能突然就失效）
我上个月提交过一个增加了转存功能的版本，在这里，readme里有新功能的使用说明，其他与原作者提交的最新版本一致。已编译文件可在蓝奏云下载
https://ww.lanzous.com/b01berebe
密码:4pix

下载地址已失效了，请问有没有编译好的linux版本？多谢

https://gitee.com/littleye233/BaiduPCS-Go-reuploaded/attach_files/409715/download
我这边蓝奏似乎挂了，只能用gitee凑合，似乎有点慢，但是应该可用

蓝奏云我测试是OK的，不清楚是否在某些地区有访问限制。
gitee的地址我这里无法访问，登录后依旧提示受限，不知是不是个例。

抱歉！我sb了...我这gitee仓库是私有的，忘记公开了...现在应该可以了：https://gitee.com/littleye233/BaiduPCS-Go-reuploaded/attach_files/409715/download
ps：我一时半会儿拿不到pc，所以用手机上的蓝奏wap，上传莫名奇妙一直失败，但是其他的服务应该是可以的

v3.6.2 is the latest version, I believe. I pulled a request one month ago and I'm sure there is no code change since then.
All functions works well as usual, baidu-api change is not the reason, I think.
I also had a copy here, it's based on the latest version and a new function (transfer share link) was added, compiled file can be downloaded here (code: 4pix)
3.6.2应该是最新版本了，我这几天一直在关注这个项目，近期没什么变化。
今天测试一切工作正常，应该不是百度API更换导致的（实际上项目的下载API跟mac版、Linux版客户端用的是一个，所以不太可能突然就失效）
我上个月提交过一个增加了转存功能的版本，在这里，readme里有新功能的使用说明，其他与原作者提交的最新版本一致。已编译文件可在蓝奏云下载
https://ww.lanzous.com/b01berebe
密码:4pix

下载地址已失效了，请问有没有编译好的linux版本？多谢

https://gitee.com/littleye233/BaiduPCS-Go-reuploaded/attach_files/409715/download
我这边蓝奏似乎挂了，只能用gitee凑合，似乎有点慢，但是应该可用

蓝奏云我测试是OK的，不清楚是否在某些地区有访问限制。
gitee的地址我这里无法访问，登录后依旧提示受限，不知是不是个例。

抱歉，我sb了！我那个gitee是私有库，忘记公开了....现在那个地址应该能用了（逃
之前我以为蓝奏对手机wap端不友好，后来才发现上传文件类型有限制，改了个后缀名就好了（下载下来要把扩展名去掉）：https://littleye233.lanzous.com/iWLnWder7pg

偶然发现3.6.1还能用，无会员下载速度2M左右。

Because of the tea from Baidu legal department.

Erope的V3.7.1修复无法登录的版本，在6月14日晚，作者也删库了，吐了，两个t的文件，怎么办啊https://github.com/Erope/baidupcs-web

v3.6.2 is the latest version, I believe. I pulled a request one month ago and I'm sure there is no code change since then.
All functions works well as usual, baidu-api change is not the reason, I think.
I also had a copy here, it's based on the latest version and a new function (transfer share link) was added, compiled file can be downloaded here (code: 4pix)
3.6.2应该是最新版本了，我这几天一直在关注这个项目，近期没什么变化。
今天测试一切工作正常，应该不是百度API更换导致的（实际上项目的下载API跟mac版、Linux版客户端用的是一个，所以不太可能突然就失效）
我上个月提交过一个增加了转存功能的版本，在这里，readme里有新功能的使用说明，其他与原作者提交的最新版本一致。已编译文件可在蓝奏云下载
https://ww.lanzous.com/b01berebe
密码:4pix

这个转存功能过一会就失效了，然后提示分享页面解析失败，需要重新获取cookies才可以

baidupcs-go这个项目的现状如何？
本人因为很长一段时间用着v3.6.1不亦乐乎，所以一直都没有关注过这个项目的发展状况。
结果突然间发现，又是iikira删库，又是什么“不能用”“登录不上”“没有速度”之类的言论，我有些黑人问号。
手头的v3.6.1在开了SVIP的情况下能把家里宽带跑满，所以一直以为可以“永远高枕无忧”的说……


Transfer WitnessVersion to rust-bitcoin

Pending https://github.com/rust-bitcoin/rust-bitcoin/pull/617

Closed in upstream, removed from this library


Article about change requests

[ ] Describe the needs
[ ] Describe the feature
[ ] Screenshot
[ ] Next improvements
[ ] Upcoming features
[ ] Ask for feedback

Just some ideas:

Easy collaboration workflow for all!
Change requests are out, and they will make easy for teams to collaborate in an organized way on their documents. GitBook now allows to group your contributions in cohesive wholes, called change requests. They are easy to use, they work great with large teams, they facilitate reviews.
[Screenshot]
Start using change requests now from the new editor interface, or learn more about them
.
We can't wait to hear from you, or to read your feedback!


Kimde intraň kody ba bolsa haýyş beräýiň!!!

kim täze kod tapsa kyn görmän şu taýyk ýazaýyň

Ok

Https://Dns.bentasker.co.Uk/dns-query barlap gorun isleya su

Mende
вт, 10 нояб. 2020 г., 22:32 Ayna147<EMAIL_ADDRESS>
Https://Dns.bentasker.co.Uk/dns-query barlap gorun isleya su
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Jigsaw-Code/Intra/issues/343#issuecomment-724853410,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARDX4WS5ZHZOCXXRV4FAR4TSPF2MRANCNFSM4TQXYL3A
.

Https://Dns.bentasker.co.Uk/dns-query barlap gorun isleya su
Ayna147 spasibo köp köp işleýä


drivers/serial: fix Rx interrupt enable for cdcacm

The debugging and work leading to this pull request was done together with @davids5.
Summary
This is addressing an issue where Rx interrupts were not restored for cdcacm after the buffer had been filled (in a burst).
The Rx interrupts were only restored after the watchdog timeout of 200ms fired.
This happened because CONFIG_SERIAL_RXDMA was set, however, for the cdcacm driver this does not actually matter as it is relying on uart_enablerxint to be called via the ops table.
This patch makes sure that uart_enablerxint and uart_disablerxint are always called, independent of CONFIG_SERIAL_RXDMA, relying on the ops table to be correct for the case where it should be only a no-op.
Also note: This is without CONFIG_CDCACM_IFLOWCONTROL.
Impact

Before applying this patch we need to check all archs/platforms whether they have the uart_enablerxint and uart_disablerxint correctly set (or not set) in the ops table.
Also, the location of enter_critical_section and leave_critical_section need to be reviewed as I'm not quite sure of how it should exactly be, for the "normal" and DMA case.

Testing
Testing so far was done on a stm32f4 and stm32f7 running PX4 by sending a burst of serial data and basically disabling the cdcacm watchdog by making the timeout very big.

@xiaoxiang781216 - would you please have a look at the changes here. The issues is that DMA is per port by TX or RX. So all 4 permutations (NO DMA, RX & TX DMA, RX Only DMA or TX Only DMA) can be enabled on different ports in the low level drivers by port.
So U[S]ART1 may have RX & TX DMA and U[S]ARTmay have NO DMA. and CONFIG_SERIAL_RXDMA will be lit and then the proper functions are not called on the ports not using DMA.

@xiaoxiang781216 - Thank you - please merge.

Thank you @davids5 and @xiaoxiang781216 for your help.


Japanese (medical 3 of 3): further identification of date/time expressions

NOTE: This is the last of the three items reported by @Rei-hub in issue #137, to enable analysis of EMR's daily progress notes that are less formal than discharge summaries..
Detect time expression
In medical progress notes, there are many time expressions, so that it’s very useful that they could be identified by something like markers.
Some examples:
2015-06-16 12:47:42 -> 2015-06-16 (Date) + 12:47:42 (Time) or 2015-06-16 12:47:42 (Datetime)
「12月ごろ花粉症の内服処方」 (extracted as a single entity) -> 12月ごろ花粉症の内服処方 (Month)
(in English: Around December prescription of medication for hay fever)

Improvements on DateTime attributes are being worked on concurrently with the upcoming Measurement attributes. We'll make sure that the suggested expressions get DateTime attributes when Measurement attributes are introduced.

@Rei-hub - the DateTime attribute detection has been improved with today's merge, for various examples including the ones mentioned in this issue. We would appreciate your feedback as always.


received wrong response (wrong parameter) for access_token (request)

did the following steps (grant_type=authorization_code)
step1) requested for authorization_code -> received successfully
step2) using the code(from step1) requesting for access_token -> receives the access_token successfully with other parameters
***the json format received was not as been mention in the github page(https://github.com/OneDrive/onedrive-api-docs/blob/master/auth/msa_oauth.md)
eg
{
"token_type":"bearer",
"expires_in": 3600,
"scope":"wl.basic onedrive.readwrite",
"access_token":"EwCo...AA==",
"authentication_token":"eyJh...93G4",
"refresh_token":"eyJh...9323"
}
the problem is with parameter "authentication_user", never received this parameter in response

we are receiving parameter "user_id" which is not mention on github page

The JSON response has been updated to remove the authentication_token and add a user_id. Neither of these values are used in the OneDrive API, so it's safe to ignore them. As a best practice with all JSON responses, you should expect/allow additional properties to be included in the response and ignore them.
In the OAuth response, the important values are access_token and refresh_token, since those are the values you'll need in the future to pass into the API. The other properties in this response are informational and can/should be ignored.

ty for response...
if im a new to your API's, and integrating onedrive using this APIs,  i wouldnt be cming to know which are important or which are not...

I'll update the documentation to be more clear about the required properties.

@rgregg update the docs for above scenario also
thank u for ur response


Screenshot location

You have the screenshot filepath set to /media/ramdisk
I think that /tmp is a better location, as its a standard ramdisk.
Alternatively, the creation of /media/ramdisk should be included in the installation guide.
Cheers!
config.lua:
-- filepath where current game's last screenshot will be saved
-- ideally on a ramdisk (for speed and less stress on the hard drive)
SCREENSHOT_FILEPATH = "/media/ramdisk/mario-ai-screenshots/current-screen.png"

Do you mean something like /tmp/ramdisk or just /tmp? I think /tmp itself is usually not a ramdisk. Might make sense to use /tmp/ramdisk - I don't know what the convention there is.
Btw, the readme contains under "installation procedure" a small chapter about the ramdisk stuff.

/tmp is mounted as tmpfs on Ubuntu.
To see if it is mounted that way, you can run mount | grep tmpfs,
which will list all of the tmpfs mountpoints on your system.
Thanks, I see the section now.


[FLOC-2928] Don't spellcheck the authors

Fixes https://clusterhq.atlassian.net/browse/FLOC-2928

:+1: LGTM
Please wait until tests pass before merging.


Timing file change events

Scenario: I'm watching 1000s of files.  For each add, change or delete an  emit gets triggered and the client (browser) will sometimes get slammed with 100's of requests in a short amount of time.  And some will come in bursts.  Many heavy duty visual aspects of the client can change.  I see the CPU get very high during these spurts.  I want to be able to control the speed and number that come down at any given time so browser is not overloaded.
My question is - does anyone have a recommendation for queuing the events that  chokiar (correctly) fires off and store them.  Then release events out the clients in a controlled, timed manner, say every 30 seconds.  Has anyone used or seen such an implementation
Thanks.
Rob

You could collect the events to an array yourself and/or use async.queue (https://github.com/caolan/async#queue) to process them in a controlled manner.
var async    = require('async')
,   chokidar = require('chokidar')

function parse(path, cb){
    // do your stuff. Make sure to call the cb() at some point.
}

// the second argument will allow you to control how many files will be processed at the same time
var parsequeue = async.queue(parse, 50);

function onAdd(path){
    parsequeue.push(path, null);
}

var watcher = chokidar('c:\test', {});
watcher.on('add', onAdd);

You might be looking for a debounce or throttle sort of implementation, both of which are provided by lodash and elsewhere.
This is out of scope for chokidar to provide itself, so closing the issue, but feel free to continue to discuss.


Send WebExtensions off to manual review

Because we aren't quite sure what we need to validate or look at in WebExtensions, it was suggested that instead we just WebExtensions off for manual review on AMO.

Since #1005 we automatically review and sign unlisted extensions.
Do we want unlisted WebExtensions to also go to the manual review?

Unlisted WebExtensions can't be any riskier than regular ones, so I think they should be auto-approved like the others.

Since all listed add-ons are reviewed, I think we can just close this?


Redisnode stopped working

docker run -it --entrypoint /bin/sh  redisoperator/redisnode:latest
/data # /redisnode
/bin/sh: /redisnode: not found

After linking musl library everything works fine
/data # mkdir /lib64 && ln -s /lib/libc.musl-x86_64.so.1 /lib64/ld-linux-x86-64.so.2
/data # /redisnode
Program started at: 2018-10-01 16:51:49.758428273 +0000 UTC m=+0.221624727

Haven't found anything suspicious in recent commits.

BTW
It would be nice to have a docker image with version tag. For version locking

@killmeplz thanks for reporting this issue,
today, I tried to release the version 0.1.1 (docker images and helm chart) https://github.com/AmadeusITGroup/Redis-Operator/releases/tag/0.1.1  in order to have like you say a docker image version locking. during the release process, the docker images were built with goreleaser, this introduces the bug... I rebuilt locally the docker image redisoperator/redisnode:0.1.1 and latest.
It should again.
I keep open this issue, in order to track a proper fix for the release process.


Swagger 2.0

So. I know there is API blueprint but I am a lot more leaned towards Swagger 2.0 which is a huge improvement over 1.0.
Any thoughts on implementing?

It really depends how similar they are as the way the annotations are named and work are pretty much how the API Blueprint spec describes them. Unless we go with an entirely new set of annotations for a Swagger implementation.
While it would be cool it's certainly not high on my todo. If you can get a working implementation or know of an existing implementation that uses annotations I'd love to see it though.

Well, I actually tried the Swagger with swaggarel package and I was not entirely happy with it. The annotation is more complex than the one provided by dingo/api right now.
More over, it doesn't support multiple api versions (Let's say you have 2 api versions but for some endpoints nothing changed - how you would document that?).
I am not against the Swagger, but the Blueprint is quite nice. And you could generate documentation easy with laravel-elixir-aglio. An in-dept look to this package will show even how to setup different routes for different documentation versions to be browse-able from your server.
@jasonlewis Still will be fine to have in config some sensible defaults to generate documentation without the need to specify any parameters.

@lightvision you can do that now, there's the version and name config keys that will be used if the command is run without any arguments.

:+1:
Thanks, I didn't check it. I am writing some tests for my app and I leave the docs after that.

Another great thing with Swagger is the API explorer, demo: http://petstore.swagger.io ... does API blueprint provide something similar which you can self host?
The Symfony package NelmioApiDoc generates an interface for this automatically for your API when you visit something like /api/docs/. Something similar for Dingo would be nice.
This package uses Doctrine annotations: https://github.com/zircote/swagger-php

Yeah, API Blueprint has a bunch of tools.
Aglio generates a static HTML explorable API

There's this conversion tool, I haven't tried it but if it works maybe it might be a good solution. It would be nice to be able to generate doc not only in api blueprint and swagger but also RAML. If you ask me it would make more sense to stick to just one.

Yeah for now I'm just going to be sticking to API Blueprint.

I would really +1 Swagger here. My first experience with it was while building a standalone API using Restler, and the Swagger-based docs just blew my mind. It's certainly the best way to provide developers with a comprehensive and interactive documentation.
The only tool available in the Blueprint website that seems to do similar job is paid
Also, I'm not sure if this would help in any way, but I find the Restler annotations much, much more leaner and easier to be used. Not sure if this is related to the conversor it uses or if it's just "proprietary tech".

I personally like the idea of this (use Swagger 2.0 at work), but at the moment the main focus is going to be tagging a stable 1.0. Once that's done, might be able to revisit this. And of course, PR's are welcome

Closing, this is unlikely to be done largely due to lack of resources and many other priorities. If anyone wants to take it up, please feel free !


PHOENIX-7001: Addendum to initial CDC feature

Addendum to PR #1866

Revert a change that broke GlobalImmutableTxIndexIT#testLastDDLTimestampOnAsyncIndexes
Remove ALTER CDC support as it is no longer needed.

Pending build results https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1899/2/

Looks like tests are still failing
e.g.
java.lang.AssertionError: Ran out of time waiting for index state to become BUILDING last seen actual state is ACTIVE
	at org.junit.Assert.fail(Assert.java:89)
	at org.apache.phoenix.util.TestUtil.waitForIndexState(TestUtil.java:1104)
	at org.apache.phoenix.end2end.index.BaseIndexWithRegionMovesIT.testLastDDLTimestampOnAsyncIndexes(BaseIndexWithRegionMovesIT.java:1712)

FYI @tkhurana @palashc could you please also review? Something missing in the tests after the current PR state?

Now it's failing with NPE, though I am not sure if it is flaky test or it's consistently failing:
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1899/3/testReport/junit/org.apache.phoenix.end2end.index/GlobalMutableTxIndexIT/testLastDDLTimestampOnAsyncIndexes_GlobalMutableTxIndexIT_transactionProvider_OMID_columnEncoded_false_/

java.lang.NullPointerException
	at org.apache.phoenix.end2end.IndexToolIT.verifyMapper(IndexToolIT.java:979)
	at org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:1021)
	at org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:1001)
	at org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:992)
	at org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:986)
	at org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:958)
	at org.apache.phoenix.end2end.index.BaseIndexIT.testLastDDLTimestampOnAsyncIndexes(BaseIndexIT.java:1516)

It has to be a flapper as it is working fine on my box (tried 3 times).


chore: add demo toolings

Broke the other PR (by deleting my fork due a problem).
I tried the

I deleted the extra vendor bundle. Now you have to require vendor.ts on the demo.ts.

Review please.

Left some comments. Good stuff!

I addressed all of them (except the dist thing).

LGTM!


chore: setup jest testing

Jest can be setup with TypeScript with either babel or ts-jest
Fireship (in one of the Pro courses) uses ts-jest instead of babel, while MobX seems to use babel according to the repo.
ts-jest has a comparison here, where it implies that the TypeScript preset for babel is mainly for those who are already using babel.
Since we are not using create-react-app or expo, which uses the babel compiler, we can just use ts-jest as we are not using the babel compiler in the first place. Seems less hassle and setup anyways, babel had always gave me headaches in the past.
References

https://www.youtube.com/watch?v=Jv2uxzhPFl4&t=680s&ab_channel=Fireship
https://jestjs.io/docs/getting-started#via-ts-jest
https://github.com/kulshekhar/ts-jest
https://kulshekhar.github.io/ts-jest/docs/getting-started/installation/#jest-config-file

Correction: MobX according to package.json uses ts-jest too

Update: upon further inspection MobX uses tsdx, which bootstraps a typescript project automatically!

refer to #6


BUG: snakecase('_id') => id

This is a bug for sure, this is not the expected output for snake casing.

I'm unable to replicate with the latest version: https://runkit.com/blakeembrey/5e0677c07d4082001a02850f.

Closing since id is expected behavior based on the title change. This is how it's always worked: https://github.com/blakeembrey/change-case/issues/50.

My point of renaming the title: It is a bug that always existed, but I had a workaround for it.
The correct implementation of snake case for _<something> is:
Python 3.8.0 (default, Dec 29 2019, 20:15:26)
[Clang 10.0.1 (clang-1<IP_ADDRESS>)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import stringcase
>>> stringcase.snakecase('_')
'_'
>>> stringcase.snakecase('_foo')
'_foo'
>>>

It's a reasonable request. I'd always suggest searching and commenting on an existing open issue though. As a maintainer, I'll usually close out duplicate issues. As for implementing this feature, I think it should be fairly easy to do - but should camelCase and PascalCase also follow the convention? It's pretty standard to do underscore prefix on them too.

One idea is to support a prefix: '_' option globally, and use the prefix when this code executes: https://github.com/blakeembrey/change-case/blob/1c1377a692d328ae01221b2a1532bade38e1eaa3/packages/no-case/src/index.ts#L36-L37. Would that suit your needs, or do you expect this to be the default behavior?

Yes an optional override is probably the way to go to avoid breaking changes for any existing projects.
I did some experiments with similar libraries in various languages and noticed there seems to be a common inconsistency, e.g. in most popular Ruby (activesupport) and Python (stringcase) libraries _<something> keeps the prefix, but in Sublime Text package Case Conversion it is stripped.


Adding netlify for previewing docs

It took me a little time to figure out where to click, but nice to see that we can get a preview. Is there a way we can use one of our existing CI runners (maybe zuul) to run and produce the same?

recheck

recheck

recheck

/test dataplane-operator-build-deploy-kuttl

/test dataplane-operator-build-deploy-kuttl

recheck

recheck

closing in favor of https://github.com/openstack-k8s-operators/dataplane-operator/pull/282


Content Creation Screen is blank when a custom link is present

Hello,
I am running into an issue - I have created a custom LinkData property and I am using it on our models. There is an issue at the moment that if there is a custom LinkData present then no properties will show on the content creation screen in the CMS.
public class GeneralLinkData : LinkData
    {
        [ScaffoldColumn(false)]
        public override string? Target => OpenInNewTab ? "_blank" : "_self";

        [ScaffoldColumn(false)]
        public override string? Title => base.Text;

        [Ignore]
        public Url? Url => !string.IsNullOrWhiteSpace(base.Href) ? new Url(base.Href) : null;

        [Display(Name = "Open In New Tab")]
        public virtual bool OpenInNewTab
        {
            get => GetAttribute((v) => bool.Parse(v));
            set => SetAttribute(value, (v) => v.ToString());
        }

        [Required]
        public override string? Href
        {
            get => base.Href;
            set => base.Href = value;
        }
    }

[PropertyDefinitionTypePlugIn(
        DisplayName = "General link",
        GUID = "41589b68-f826-459e-bc11-e4db2c8f51cc")]
    public class PropertyGeneralLink : PropertyLinkData<GeneralLinkData>
    {
    }

[ContentType(
        DisplayName = "Static Three Up Item",
        Description = "An item to be used in a Static Three Up block.",
        GUID = "eec5gfea-f570-4384-8916-ec2279a0cc80")]
    [ImageUrl("~/assets/images/episerver/thumbnails/staticthreeupitemblock.png")]
    public class StaticThreeUpItemBlock : BlockData
    {
        [Required]
        public virtual string? Heading { get; set; }

        [Required]
        public virtual GeneralLinkData? Link { get; set; }

        [UIHint(UIHint.Image)]
        public virtual ContentReference? Image { get; set; }

        public virtual string? Text { get; set; }
    }

As you can see from the screenshot, when I have the custom LinkData property on the model, the creation screen is completely blank. If I set it to [ScaffoldColumn(false)] the properties will show again.
This is a showstopper as when you create block directly from a ContentArea, it will not let you create it without required fields being populated, so the item cannot be added this way.

@valdisiljuconoks @svenrog any info on this?

Hi,
We will look into this next week.

Awesome, thank you both. I will let you know once I get the package updated.
Do you know roughly when Optimizely might approve the change? No worries if not

1.4.3 is out on feed.


Add breaks around conditions of while-stmt.

This aligns the behavior of while-stmt and guard-stmt conditions. The while-stmt conditions didn't have open-breaks, which meant there was no additional indentation nor would continuation breaks be able to stack.
This means there's always a break before the first token of the condition element list when the while-stmt's condition is multiple lines. That is likely to cause some churn in existing code. An alternative would be to treat this like if-stmt, where there is no break after the while token.
Issues

This is likely to cause churn. I think we could minimize that by aligning with the if-stmt behavior, but I think it makes more sense to allow a break after while, like guard.

To avoid churn, can we align with if for now, then once we have region-restricted formatting in the future, change it to have the break after the while?

To avoid churn, can we align with if for now, then once we have region-restricted formatting in the future, change it to have the break after the while?

I think that's fair. Made the change.


default('test') don't work!

Text::make('Name') ->sortable()->rules('required', 'max:255')->default('test'),

Hi! You can set default values by inserting them into the nova_settings database table directly. It would be misleading to show a default value for a setting in the UI while it's not actually in the database.


Img tag is now able to be converted in JSX

"img" tags can now convert into JSX but the other requirements are not working.
You can reproduce it with:
input:
output:
expected output:

ohh wait I'll look into it

@pythonpioneer hey man i fixed the code just have a look


sdssplitargs should lazily create the string instead of pushing 1 by 1 into the new one.

https://github.com/JohnSully/KeyDB/blob/69a74a567bd381a84e71f954d4cb35eb878f6d3c/src/sds.c#L998
Was just browsing the codebase and noticed that this string arguments splitting function is eagerly creating the vector of argument substrings by calling sdscatlen at pretty much every non-whitespace character. This could potentially allocate multiple times for long arguments.
I think it should just iterate through the arguments, remember when it started and just allocate as required.
According to this: https://github.com/JohnSully/KeyDB/blob/69a74a567bd381a84e71f954d4cb35eb878f6d3c/src/sds.c#L236
The allocated buffer is multiplied by 2 each time, which assumes that strings are usually around the power of 2; which is not true I think.
I don't think Redis made any changes to this.
https://github.com/redis/redis/blob/8b497881f2eda5b028cc2ba0aa17ef204f6a083b/src/sds.c#L979

I spent some time looking into this, and I don't think there's a valuable change to be made. It parses one character at a time so it can add escape characters, quoted sections, etc. While the logic could of course be rewritten I don't think there's sufficient reason to do so. As for the allocation, the fact that it doubles every time doesn't mean it assumes strings are around the power of 2, it simply assumes that the string doubling in length is an approximately reasonable ceiling. Common implementations of C++'s std::vector<T>::resize use this same paradigm. In any case, performance is negligibly affected by the handful of reallocations that happen while reading each token.
Closing since there's no user-affecting improvement to be made.


cannot install... help

I have used your product in the past without any issues
sorry for this but its bizarre
just started happening
cannot install your product
everything else works except your package
and its suppose to work self contained independent of anything correct?
I have nothing on my machine
% yarn global add json-graphql-server
yarn global v1.22.22
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
warning "json-graphql-server ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>[4/4] 🔨  Building fresh packages...
success Installed<EMAIL_ADDRESS>with binaries:
      - json-graphql-server
✨  Done in 1.92s.

% which json-graphql-server
json-graphql-server not found

can anyone help?
is the incorrect peer dependency causing this?
I installed node.js perfectly and altered the permissions of the cache for $USER as appropriate
everything else appears working but this is holding me up
very bizarre
any help is apprevciated
THANKS

same thing with NPM
% npm install -global json-graphql-server
npm warn ERESOLVE overriding peer dependency
npm warn While resolving<EMAIL_ADDRESS>npm warn Found<EMAIL_ADDRESS>npm warn node_modules/json-graphql-server/node_modules/graphql
npm warn<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm warn   node_modules/json-graphql-server
npm warn     json-graphql-server@"*" from the root project
npm warn   7 more (@apollo/client, @graphql-tools/schema, graphql-tag, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm warn node_modules/json-graphql-server/node_modules/express-graphql
npm warn<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm warn   node_modules/json-graphql-server
npm warn
npm warn Conflicting peer dependency<EMAIL_ADDRESS>npm warn node_modules/graphql
npm warn   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm warn   node_modules/json-graphql-server/node_modules/express-graphql
npm warn<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm warn     node_modules/json-graphql-server
npm warn deprecated<EMAIL_ADDRESS>Please use @jridgewell/sourcemap-codec instead
npm warn deprecated<EMAIL_ADDRESS>This is probably built in to whatever tool you're using. If you still need it... idk
npm warn deprecated<EMAIL_ADDRESS>This package is no longer maintained. We recommend using `graphql-http` instead. Please consult the migration document https://github.com/graphql/graphql-http#migrating-express-grpahql.

changed 116 packages in 6s

13 packages are looking for funding
  run `npm fund` for details
% which json-graphql-server
json-graphql-server not found

I have pnpm setup had been using that prior and same thing with that as well

okay someone or something botched up my machine
with an added point of FAILURE
.npmrc
the prefix attribute
wiped me out
it was set to the home directory of my apps project
you know if they dont stop introducing fifty million points of failure no one is going to ever dig themselves out of this mess
as to why
I LEAD
I DO NOT FOLLOW

fixed... nuke .npmrc and all works fine

alright Im hoping soneonemay see this since it sclosed
I could goto the npm, yarn or pnpm folks
but maybe I can muster some help here for fast solution
the design of the package managers is off the charts GONE
and its haunting to this day
they should have ditched brew, nvm and anything else in between that puts its fingers all over the OS and its PATH for the package manager to appropriately install things and have the OS subsequently FIND IT
well mine still cant
and Im hesitant to continue mucking because I know its only going to get worse
I deleted ~/.npmrc
I do not have any global fabricated directory to hyold and store global packages producs like this one json-graphql-server
but when I install they go somewhere hopefully supposedly STANDARD supposedly the way the package mgr is suppose to behave so the OS can find it thereafter during execution/launch
but my OS still cannot find json-graphql-server
its installed at
% ls /usr/local/lib/node_modules
corepack		json-graphql-server	npm


fix: fix accessibility on storybook

Signed-off-by: Arthur Andrade<EMAIL_ADDRESS>What's the purpose of this pull request?
This PR fix some accessibility issues in sotrybook.
How it works?
Some storybook’ components have accessibility issues. The goal is to fix that.

[x] Badge: Elements must have sufficient color contrast
[x] Form elements must have labels
[x] Price: Elements must have sufficient color contrast
[x] Radio: Form elements must have labels
[x] Select: Select element must have an accessible name
[x] Textarea: Form elements must have labels
[x] Carousel: aria-roledescription must be on elements with a semantic role
[x] IconButton: Buttons must have discernible text
[x] PriceRange: Elements must have sufficient color contrast
[x] Table: Elements must have sufficient color contrast

Not sure it's in the scope of this task, but since I believe it's related, can you also add the assertion toHaveNoIncompletes from https://github.com/vtex/faststore/pull/1054 in the existing accessibility component tests? Maybe right after the ones that only have toHaveNoViolations.


🚀 [Feature Request]  : Bookmark the blog

Is your feature request related to a problem ? Please describe. ✍

If the blog/ page click the bookmark icon there is no action.
If i want to implemment the new feature to the bookmark added & Remove.

Describe briefly how you would implement this enhancement.
Some steps to implement this enhancement-
1. Step 1 : Navigate to the `blog` page
2. Step 2 : Click the any one of the blog
3. Step 3 : see the site `bookmark` icon there is no something action not information showing.

Additional context or screenshots

please assign me ...
i will ready for work in this project.

Are you contributing for a program?
GSSoC2024
Code of Conduct

[X] I have read and agree to the Contributing Guidelines of this project.

hey please assign me this issue under gssoc24


Not able to avoid formula

I don't want to allow people to type formulas on the cell. It has to be numbers only. However if the person type =, formula is invoked automatically and there is no way I could find to avoid it.
Also the formula function has 2 console.log() logging the values of each cell

Yes, if = is typed they are trying to invoke that. But you could try to remove than with the updateSettings that happens every time a column is changed.
https://bossanova.uk/jexcel/examples/currency-and-masking-numbers
About the console.log this was updated in the master repository and you can get the new version without it.

yes I can use the updateSettings, however it is called after the cell has invoked the formula, so I will have the value changed to the one I want, but I'll have and error on my console too.
I think best place to handle this type of validation would be on onbeforechange(), so I could take care of making any value validation and replacement before it take place.
However, even tho I could validate it on onbeforechange(), I have not found a way to replace the value on the cell. My idea is, if the value is valid, keep the value, if not valid then replace the new value with the old value.


Typo in sec 36.8.2

Edition: 2023-04-01, Advanced Topics

The z's should be x's

Side note: despite the occasional typo, this chapter on causality is incredible. I've read several books on causality and I've never come across a description so principled, unified, reconciled and comprehensive. And then there are 35 other chapters. This book is a ridiculous gift.

I fixed the typos.
Thanks for the praise. However, it was actually @vveitch and @alexdamour who wrote this chapter :)


Are we going to distribute a PyPI package? What should be included?

[ ] restore the src/mixs/datamodel/__init__.py as described below
[ ] Are we going to distribute a PyPI package? https://pypi.org/project/mixs-linkml/ ?
[ ] What extras should be included, like the schema YAML file?
[ ] We will need to set up PyPI authentication

The Python representation of the MIxS standard is in src/mixs/datamodel/mixs.py
@sujaypatil96 has added some doc-generating utilities to  src/scripts

Neither of those paths have an __init__.py file at this time

PyPI pachage build and publishing are included in the default GH actions, but we need to decide whose PyPI account to use and save the credential as a password
Or we can use a project-specific credential
otherwise:

ERROR    HTTPError: 403 Forbidden from https://upload.pypi.org/legacy/
Invalid or non-existent authentication information. See
https://pypi.org/help/#invalid-auth for more information.

Should we make this a priority for the next release, perhaps v7.0?

see also this, and more

https://github.com/GenomicsStandardsConsortium/mixs/issues/245

The release of a PyPI artifact (which will make it easier for people to interact with MIxS programmatically) could be considered orthogonal to MIxS 7, which I mainly think of a s new content.
But maybe it is advantageous to time the PyPI package with MIxS, 7, so that it gets a lot of visibility?


Skip blockpc(s) where the block's phis are not relevant

When we generate relevant blockpc(s), we have to filter out
those where the block's phi instructions are not relevant to
the replacement candicate. Let's look at the following (simplified)
example:
; :10                                      ; preds = %3, %7
%11 = phi i32 [ %9, %7 ], [ %6, %3 ]
store i32 %11, i32* @x5, align 4, !tbaa !1
br i1 false, label %13, label %12
; :12                                      ; preds = %10
store i32 0, i32* @x3, align 4, !tbaa !1
br label %13
; :13                                      ; preds = %._crit_edge, %10, %12
%14 = phi i32 [ %11, %10 ], [ %.pre, %._crit_edge ], [ %11, %12 ]
store i32 %14, i32* @x4, align 4, !tbaa !1
%16 = icmp eq i32 %1, 0
Previously, when we generate replacement candidate for instruction %16,
we will generate blockpc coming from [%11, %12], e.g.,
...
%10:i1 = slt %1, %9
blockpc %3 2 %10 0:i1
%11:i1 = eq 0:i32, %1
cand %11 0:i1
because %10 relates to %11 (they have %1 in common). However, it's bad
because the phi node is missing. Consequently, when we generate KLEE expressions,
blockpc %3 won't be touched because it can't be reached from any phi instruction,
and hence we will generate insufficient queries and mis-optimize the given code.
This patch fixed this issue (#166).

Google » souper #448 SUCCESS
This pull request looks good
(what's this?)

It's now not generating a candidate for the icmp eq i32 %0, 0 instruction in the test case from #166, i.e. the instruction that triggered the incorrect optimisation. Is that intended?

@jeroenk I think Souper still generates candidates for icmp eq i32 %0, 0. Note that Souper prints Souper IR only for valid candidates. For example, on my machine, I got:
$ /home/chenyang/work/souper_fork/souper/build/souper -keep-solver-inputs -dump-klee-exprs -z3-path=/home/chenyang/other_programs/z3/build/z3 test.bc
; Listing valid replacements.
; Using solver: Z3 + internal cache
Solver input saved to /tmp/input-521a0a.smt2
Solver input saved to /tmp/input-9879f1.smt2
Solver input saved to /tmp/input-4e5d09.smt2
Solver input saved to /tmp/input-a1a01d.smt2
Solver input saved to /tmp/input-2fe28c.smt2
Solver input saved to /tmp/input-990490.smt2
Solver input saved to /tmp/input-8cedd1.smt2
Solver input saved to /tmp/input-cb57bf.smt2

; Static profile 1
; Function: main
%0 = block 2
%1:i32 = var
%2:i1 = slt %1, 1:i32
blockpc %0 0 %2 0:i1
%3:i32 = var
%4:i1 = slt 1:i32, %3
blockpc %0 0 %4 0:i1
blockpc %0 1 %2 0:i1
%5:i1 = slt 0:i32, %3
%6:i32 = zext %5
%7:i32 = zext %4
%8:i32 = phi %0, %6, %7
%9:i1 = slt %1, %8
cand %9 0:i1
Solver input saved to /tmp/input-394537.smt2
Solver input saved to /tmp/input-8b08b1.smt2

We have ten smt queries, which correspond to five icmp instructions in John's example. However, out of those ten candidates, only one got optimized by Souper.

Yang, do you know if this issue is tied to #157? It seems like you are saying here that they two issues should be fixed separately.
Raimondas, can you look at this code?
Overall I think we are due for some cleanup and refactoring in this part of Souper, I find it quite difficult.

I'll start running some Csmith tests on this branch.

John, Yes, #157 and #166 are separate issues.

LGTM, but I second John, we need refactoring in this part of Souper including UB/Phi pred code.

In light of other discussions, should we close this?

Yes, we should close it.


I want to translate

I have seen that the app has to be translatable, but in German, for example, a lot is not translated.
Is there a link somewhere on github so that I know what I can translate?

Hi @mondlicht-und-sterne the app is not translatable. When you select a language it uses ISO code to fetch TMDB movies with that language. You can add a translation for your favorite movie on the TMDB website.


Send email to users without any activity

In order to promote users to start using the platforms, we should send an email - periodically or at least manually - to all users that have no submission and have being registered, say, more than one month ago.

What are you using for this?
I like this small option:
https://github.com/jmettraux/rufus-scheduler
If not you can use this fatty boy
https://github.com/resque/resque-scheduler

Actually we have not starting using it yet. There is an implementation by @iluetich but I had no time to configure mailing nor to schedule mailing.
We should respawn this issue

Ok, by now I went to a less scalable but quicker solution: I just added some filters to the admin user interface for getting users without recent activity. Then you can export that list as CSV from ActiveAdmin and import in Mailchimp or any service like that.


[432]fixed nullable mismatch in coalesce

Changelog category (leave one):

Bug Fix

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
...
Documentation entry for user-facing changes

[ ] Documentation is written (mandatory for new features)

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

closed #432

Can one of the admins verify this patch?

test this please with 1353


Update documentation url and add badges to README

Now that webmock-fixtures is published to RubyGems we can update the documentation link to point to http://www.rubydoc.info/gems/webmock-fixtures
As well, I added in ruby gem version badge and travis build status badges to the README.
Fixes #5
/cc @twolfson

Now that the documenation is up, I have some questions/feedback:

The backticks don't seem to be respected here

http://www.rubydoc.info/gems/webmock-fixtures/WebMock/Fixtures/Manager#fixtures-class_method

Can we wrap the e.g. to another line somehow? It feels lengthy

http://www.rubydoc.info/gems/webmock-fixtures/WebMock/Fixtures/Manager#fixtures-class_method

This seems to say it returns Object when it actually returns nothing (or nil). Any idea if we can correct that in Yard?

http://www.rubydoc.info/gems/webmock-fixtures/WebMock/Fixtures/Manager#register_fixture-class_method

Looks good except for the missing branch fixation

I updated to try and address the comments you had about the documentation.
As well, I noticed that YARD did a pretty bad job of rendering our README. So I added in .yardopts to make sure that we use markdown formatting and included LICENSE-MIT and CHANGELOG.md in our documentation as well.

For my knowledge, are you able to preview this locally to make sure the updates will work?

Changes look good :+1:

I was just running YARD locally. Decided not to add it in here, probably not going to be a normal part of our dev process, just needed to get .yardopts right without merging to master (for rubydoc.info).
But for verbosity.

Add gem "yard" to Gemfile
Run bundle exec yard doc
cd ./doc && python -m SimpleHTTPServer
Visit http://localhost:8000/

Ah, k. Not sure how applicable it is to this repo but it would be sweet if we could do something similar as with the Engineering blog for previewing documentation changes.
Or maybe skip using YARD and always document in README.md ;)


Due Oct 1, 2023: Update GA scripts to GA4

DAP Users:
Over the last few months, we’ve gotten a BUNCH of questions from you all about our plans for launching a DAP GA4 property.
The good news is: Our goal is to launch a dual Universal Analytics (the current version you use) and GA4 DAP code on May 26, 2022!
Here’s what you need to know to prepare:
Will I need to do anything to initiate data flowing into the DAP GA4 Property?
If your site calls the DAP code from the location we host, https://dap.digitalgov.gov/Universal-Federated-Analytics-Min.js, there will be no action needed. When we launch the code, we’ll push it to that location and it will automatically collect and send data to both the existing Universal Analytics property AND our new GA4 Property.
If you choose to host the code on your own servers, you’ll need to replace your existing DAP version with v6.4, which will be the production dual tracking code. On launch day, I’ll send an email with a link to that code version for you to replace your current code.
Will this change anything in the DAP Universal Analytics property we currently use?
No. You should be able to use the current DAP Universal Analytics Property and Views as you have been. We spent a lot of time configuring this solution so that we could implement it with no effect on the current data collection. If you happen to see something very out of the ordinary going on in your DAP Universal Analytics data after launch, please reach out to us so we can troubleshoot.
Should I start using GA4 for my reporting needs?
At this point, no. Google is still pushing changes to GA4 regularly, and there’s a very good chance the DAP team will be making tweaks as well. The goal of getting this GA4 code in production is to make sure we have a full year of data overlap before Google discontinues Universal Analytics in late 2023. So, our advice for now is: play in the user interface and get acquainted! As you’ll see, it’s very different from what we’re used to. But, continue to use the existing Universal Analytics property and views for your regular reporting and analysis for now.
What’s next after launch?
Prior to launch, I will be sending updates to talk about how we have put this solution together and with new documentation so you know which features are available. After that, the DAP team will start working on resources to help you understand GA4.
You are going to have a lot of questions.  This is a completely new tool and data structure. It has a new UI, new metrics, new terminology, etc. We’re all going to go through the learning curve together.
In the first few weeks after launch, I would ask you to hold off on asking us questions about how to use the interface (to be honest, we’re still figuring it out ourselves!). Before we dive into training and resources, we want to focus on making adjustments so that the GA4 data is coming in how we need it to. We promise we’ll be working on materials to help you with reporting in the coming months.
With that said, keep an eye on this listserve, because there is more information on the way.


No mention of SharePoint 2019

It would be nice is there is some guidance for customers that want to migrate SharePoint 2019 to SharePoint Online.  My understanding that the SPMT doesn't support SP 2019, but an estimated release date or some type of recommendations on 3rd party tools would be useful.

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

ID: 85a08784-543a-32b7-1e83-4f3ebf5bc6d4
Version Independent ID: 7234f9f2-a3a1-b37b-4153-f86ec483993c
Content: Migrate to Microsoft 365 - Migrate to Microsoft 365
Content Source: migration/migrate-to-sharepoint-online.md
Service: sharepoint-online
Sub-service: sharepoint-migration
GitHub Login: @JoanneHendrickson
Microsoft Alias: jhendr

Hello @will73
I am looking into this

Hello @will73
I am looking into this

@will73
This roadmap item has just showed up about SPMT & 2019 with the expected availability
https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=&searchterms=93408

@scanum


Use pikepdf instead of PyPDF2

I'd like to submit this PR to suggest the use of pikepdf instead of PyPDF2.
Reason: PyPDF2 isn't maintained & outdated
Benefits: pikepdf has newer PDF & encryption standards and supports Python 3.5 to 3.8
PyPDF2 isn't maintained anymore since 2016 and only supports Python 2.6 to 3.5 (all outdated by now).
Right now we were only using PyPDF2 for testing, so there isn't really a need to change at the moment. BUT if we want to implement new features (such as encrypted PDFs suggested by #454) it would definitely be better to use pikepdf as it uses newer PDF and encryption standards than PyPDF2). More advantages can be found here: https://github.com/pikepdf/pikepdf

pikepdf depends on qpdf and needs at least qpdf version 8.4.2. Travis is using Ubuntu Xenial (16.04 LTS) by default, which only supports up to qpdf 8.0.2-3. That's why it's failing! :(
So if we don't use Ubuntu Focal (20.04 LTS) instead on Travis, I think we can't use pikepdf at the moment. In case someone knows: Ate there be any downside to use Focal instead of Xenial for Travis?
I also check if I can find other, similar, libraries to pikepdf, but I haven't found any that is up to date and well maintained. "pdfminer.six" might me an alternative, but it really seems to be poorly documented.
Therefore I'm closing this PR now. We'll probably have to stick to PyPDF2 for now.

Hi, I am interested in this change, maybe you can downgrade the pikepdf version and his qpdf to work with Ubuntu Xenial.

Try using pikepdf>=0.3.7

@luisza Wouldn't this install just the latest version (1.19.3) of pikepdf? Shouldn't it be pikepdf<=0.3.7? Or am I missing something?
According to the release notes of pikepdf: We would need to downgrade to version 0.3.0, because 0.3.1 already needs qpdf 8.1.0 as minimum. --> https://pikepdf.readthedocs.io/en/latest/release_notes.html
So pikepdf version 0.3.0 (released July 2018) seems to be the last version that could be run on Xenial. And at this point I don't know if it's worth it - changing from the outdated PyPDF2 to an outdated version of pikepdf. What do you think?
Apart from downgrading to pikepdf 0.3.0, I don't see any other solution right now. Bionic also only supports qpdf 8.0.2. And Bionic will be end-of-life in 2023. (Focal is using qpdf 9.1.1-1.)

This app is installed in servers where the stability is very important so it's easy to found installation of Ubuntu 16.04 or Debian Stable or Rethat so we need to provide a easy way to have this app in this environments, but 0.3.0 is too old so I propose to reach an intermediate point using as less version of pikepdf 1.2.0 with libqpdf 8.4.0.
We can change de tavis base installation to Debian 10 (or updated Ubuntu image), and work in better support of pikepdf like Metadata management, password and encryption documents, for a future milestone.

Here is a short overview:

"possible pikepdf versions" --> "needed qpdf version" --> "running on this OS"

pikepdf 0.3.0                              --> qpdf 8.0.2    --> Ubuntu Xenial/Bionic/Focal/Groovy; Debian 10

pikepdf 0.3.1 - 0.3.2                   --> qpdf 8.1.0    --> Ubuntu Focal/Groovy; Debian 10

pikepdf 0.3.3 - 1.1.0                   --> qpdf 8.2.1    --> Ubuntu Focal/Groovy; Debian 10

pikepdf 1.2.0 - 1.5.0                   --> qpdf 8.4.0    --> Ubuntu Focal/Groovy; Debian 10

pikepdf 1.6.0 - 1.19.3 (newest)   --> qpdf 8.4.2   --> Ubuntu Focal/Groovy

pikepdf 2.0.0 (dev)                     --> qpdf 10.0.1  --> Ubuntu Groovy

So which one would you prefer? If we change from Xenial to Focal: What are the consequences? Are we dropping more or less support for Xenial and Bionic then? I don't know if that's a good idea.
And is it even possible to use Debian with Travis? I could only read about Ubuntu in the documentation.

using as less version of pikepdf 1.2.0 with libqpdf 8.4.0
With qpdf 8.4.0 we could also use pikepdf 1.5.0. And if we use Focal, we could even use the newest version (1.19.3).


Create correct outputs from Falcon by changing the generation configuration

Falcon 7b and 40b generate outputs that are either cutoff in the middle or do not stop after the Eos token. We could solve this with the generation configuration. I will experiment with different settings to see if this resolves the issue.

I am facing the same problem. Did you finally find the best generation configuration for solving this ?


Correct format string error in answer 3.12

Tested with sbcl. ~{ and ~} starts and ends a loop.

Tested with sbcl. ~{ and ~} starts and ends a loop.


Separate Job spec from system state

At present the system representation of a job and user submitted data are combined together into a single structure, the Job type.
Problem
It feels like we are making this easy for ourselves, instead of ours users. Or what's more likely - making this hard for BOTH ourselves and users. At present we are munging together user submitted data and system data into multiple structures - the job and its tasks. Further we are making modifications to the data submitted by users depending on various edge cases. Lastly, we are inefficiently storing job state when persisting to disk in the jobstore.
Ways we are making it harder for ourselves:

There are several different methods on the job type that must be called to validate and sanitize it. Some of these methods must only be called on the client side, while others must only be called on the server side. This is poor DevEx.

Some of these methods are only needed in the first place because we are munging together system representation and user data. e.g. SanitizeSubmission only exists because we allow users to submit system fields in the first place.

The meta field of a job has various "reserved" keys that cannot be set by users, if they are we delete them: https://github.com/bacalhau-project/bacalhau/blob/main/pkg/models/job.go#L307. This is both poor DevEx and UX.
We only disallow user submissions with the JobID set if the job type is batch or ops. system and daemon jobs may provide their own jobID on submission: https://github.com/bacalhau-project/bacalhau/blob/main/pkg/models/job.go#L295-L300.

If this is the intended behavior, and I bet its not, that's really confusing UX. If it's not the intended behavior, its a bug serving as evidence we are making this hard for ourselves: We should prevent this field from even being an option for users to provide.

We inefficiency store the entire job structure, and its tasks(!!), repeatedly to disk when only modifying a small portion of the structure: https://github.com/bacalhau-project/bacalhau/blob/main/pkg/jobstore/boltdb/store.go#L848-L852. The State of a job doesn't need to be in the same structure as the users submission. It would be significantly more efficient to store the user submission once and make updates to system state representation separately.
Whenever the time comes to make changes to the system state representation of the job or task (e.g. add a new field, remove a field, modify a fields type, etc.) we will need to modify everything from the client to the server to accommodate it. Ohh and let's not forget the various SDKs!

Ways we are making it hard for our users

Running bacalhau job describe may return a job spec that is different from what the users actually submitted. For example, we modify the count field depending on the job type a user submitted: https://github.com/bacalhau-project/bacalhau/blob/main/pkg/models/job.go#L166
Running bacalhau job describe --output yaml | bacalhau job run and getting several warning messages back about fields being ignored is confusing. As a user I would expect this to "just work" with out warning.
Users must carry the cognitive overhead of knowing which fields they can set and which they can't when submitting jobs. This is called out plainly in our documentation: https://expanso.gitbook.io/bacalhau-docs/setting-up/jobs/job#server-generated-parameters.

At per my point above on the reserved Meta field keys, they must also know, there are certain keys that cannot be used. I think this case is unlikely, but we could remove it from the set of possibilities entirely by tracking system and user fields separately.

Proposal
Separate the system representation of a job and the data expected from users into two different types. As an example, the JobState is used by bacalhau to monitor and track various system attributes of a job. The JobSpec is the schema/type users are expected to submit.
type JobState struct {
	// ID is a unique identifier assigned to this job.
	// It helps to distinguish jobs with the same name after they have been deleted and re-created.
	// The ID is generated by the server and should not be set directly by the client.
	ID string `json:"ID"`

	// SystemMeta is used to associate arbitrary metadata with this job.
	SystemMeta map[string]string `json:"Meta"`

	// State is the current state of the job.
	State State[JobStateType] `json:"State"`

	// Version is a per-job monotonically increasing version number that is incremented
	// on each job specification update.
	Version uint64 `json:"Version"`

	// Revision is a per-job monotonically increasing revision number that is incremented
	// on each update to the job's state or specification
	Revision uint64 `json:"Revision"`

	CreateTime int64 `json:"CreateTime"`
	ModifyTime int64 `json:"ModifyTime"`

	// Spec is the normalized submission provided by the user. It may contain transformations made to the
	// original Source submitted by the user.
	Spec JobSpec

	// Source is the original submission provided by the user. It is json bytes
	Source []byte
}

type JobSpec struct {
	// Name is the logical name of the job used to refer to it.
	// Submitting a job with the same name as an existing job will result in an
	// update to the existing job.
	Name string `json:"Name"`

	// Namespace is the namespace this job is running in.
	Namespace string `json:"Namespace"`

	// Type is the type of job this is, e.g. "daemon" or "batch".
	Type string `json:"Type"`

	// Priority defines the scheduling priority of this job.
	Priority int `json:"Priority"`

	// Count is the number of replicas that should be scheduled.
	Count int `json:"Count"`

	// Constraints is a selector which must be true for the compute node to run this job.
	Constraints []*LabelSelectorRequirement `json:"Constraints"`

	// Meta is used to associate arbitrary metadata with this job.
	Meta map[string]string `json:"Meta"`

	// Labels is used to associate arbitrary labels with this job, which can be used
	// for filtering.
	Labels map[string]string `json:"Labels"`

	Tasks []*Task `json:"Tasks"`
}

Thanks Forrest for your deep dive. Though I am not in agreement with most of the issues and concerns you've raised
First, there is a precedence to what we are doing and how we are handling and filtering out system defined fields from the job submissions. Nomad's job spec is very close to what we are doing where they interleave system defined fields in the job spec. Similarly, Kubernetes allow users to define metadata and spec fields when submitting a job, but also return status field when querying about the job and they do add their own metadata and it is a standard practice for CRDs to inject additional metadata in the same top level metadata field. While not recommended, users can submit jobs with status field, and kubernetes will just ignore them.
Second, we need to think about our API design. Nomad, Kubernets and our V2 APIs are restful APIs with a unified endpoint for interacting with jobs/pods, where users can submit jobs using PUT method and query using GET. Based on your proposal, there will be separate endpoints to submit and others to query
As for your specific concerns:

There are several different methods on the job type that must be called to validate and sanitize it. Some of these methods must only be called on the client side, while others must only be called on the server side. This is poor DevEx.

I don't understand why this is poor DevEx? Again this is what both Kubernetes and Nomad do, and I don't see the problem. Besides, we allow the requester to set default fields if they are missing in the job, and we will benefit from different validation at the submission layer where things can be more relaxed, and later validation after populating defaults.

The meta field of a job has various "reserved" keys that cannot be set by users, if they are we delete them: https://github.com/bacalhau-project/bacalhau/blob/main/pkg/models/job.go#L307. This is both poor DevEx and UX.

Again there is a precedence in Kubernetes with this, and it is the main way for CRDs to inject their own state and metadata. I would prefer this than having multiple places to define metadata for the same job

We only disallow user submissions with the JobID set if the job type is batch or ops. system and daemon jobs may provide their own jobID on submission: https://github.com/bacalhau-project/bacalhau/blob/main/pkg/models/job.go#L295-L300.

Yeah we can remove this logic as it can be confusing. The original intention was to allow users to provide their own job names and be able to update long running jobs, but not update batch and ops jobs. Job updates is a bigger discussion and we have other issues to track this including https://github.com/bacalhau-project/bacalhau/issues/3871 and https://github.com/bacalhau-project/bacalhau/issues/3864. Most likely we will allow users to update batch and ops jobs as well.

We inefficiency store the entire job structure, and its tasks(!!), repeatedly to disk when only modifying a small portion of the structure: https://github.com/bacalhau-project/bacalhau/blob/main/pkg/jobstore/boltdb/store.go#L848-L852. The State of a job doesn't need to be in the same structure as the users submission. It would be significantly more efficient to store the user submission once and make updates to system state representation separately.

You need to understand the access pattern of our jobs and APIs before concluding if we are doing things inefficiently or not. We almost never retrieve the job spec without its state. Previously when we had job spec and state as separate objects, we always had to do two queries to the database to fetch both. It is true that we are doing heavier writes, but our access pattern is heavier on the read side. Still, we can benefit from a model that is closer to Kubernetes where we have top level fields for metadata, spec and state. This allows job store implementations to optimize their storage for partial updates.

Whenever the time comes to make changes to the system state representation of the job or task (e.g. add a new field, remove a field, modify a fields type, etc.) we will need to modify everything from the client to the server to accommodate it. Ohh and let's not forget the various SDKs!

I don't understand this. If we add a new system state representation, we will need to update the SDKs regardless to be able to display this field. This is regardless if those system fields are interleaved in the job model, or if they are under a top level state field

Running bacalhau job describe may return a job spec that is different from what the users actually submitted. For example, we modify the count field depending on the job type a user submitted: https://github.com/bacalhau-project/bacalhau/blob/main/pkg/models/job.go#L166

We allow requester nodes to set job defaults if they are missing, such as timeout, job resources and publisher. I don't see this is a problem. I am more concerned in understanding how the system handled my job and what fields it assumed when running the job, rather than making sure bacalhau describe to return exactly what I submitted. Also, Kubernetes and Nomad do inject system information in the submitted job that you will see when you try to get the job

Running bacalhau job describe --output yaml | bacalhau job run and getting several warning messages back about fields being ignored is confusing. As a user I would expect this to "just work" with out warning.

First, Kubernetes ignore those fields without a warning. We can remove the warnings in the future if they are painful. Second, this model of re-submitting jobs may not be useful anyways and not common. Third, users are different and we need to collect more feedback from users before making drastic changes to our APIs. Saying that As a user I would expect this to "just work" with out warning. is a big assumption

Users must carry the cognitive overhead of knowing which fields they can set and which they can't when submitting jobs. This is called out plainly in our documentation: https://expanso.gitbook.io/bacalhau-docs/setting-up/jobs/job#server-generated-parameters.

I think you are over complicating this. Having reserved prefixes for metadata doesn't sound like something painful for users to work with, specially as we are following a pattern where we prefix all those reserved metadata with bacalhau.org/

My overall feedback is that I am sure our APIs will go through another iteration at some point, but lets do that after we have more users and collect more feedback to make informed decisions. The current APIs are functional, have precedence in Nomad, and I don't see will cause us problems for at least 2 years.
We have already opted for fixing a lot of technical debt this quarter, and we need to move forward and deliver new features rather than getting stuck in this phase. When we have more capacity and more users, we will not only explore the structure of our API models, but also the need for separate APIs and CLIs for the different job types as we've discussed before.

Closing due to the controversial nature of this change in discussions here and synchronously.


Delete support/azure/app-service/web-apps-performance-faqs.md

Pull request guidance
Thank you for submitting your contribution to our support content! Our team works closely with subject matter experts in CSS and PMs in the product group to review all content requests to ensure technical accuracy and the best customer experience. This process can sometimes take one or more days, so we greatly appreciate your patience.
We also need your help in order to process your request as soon as possible:

We won't act on your pull request (PR) until you type "#sign-off" in a new comment in your pull request (PR) to indicate that your changes are complete.

After you sign off in your PR, the article will be tech reviewed by the PM or SME if it has more than minor changes. Once the article is approved, it will undergo a final editing pass before being merged.

@backforwards Could you please explain the reason for deleting the file web-apps-performance-faqs.md? It seems the article is still valid.


Enhancement: Normalize composer.json

Q
A

Bug fix?
no

New feature?
no

BC breaks?
no

Deprecations?
no

Related tickets
n/a

Documentation
n/a

License
MIT

What's in this PR?
This PR

[x] normalizes composer.json

💁♂ I ran
$ composer global require localheinz/composer-normalize

followed by
$ composer normalize

Why?
A follow-up to #39.
Also see https://github.com/localheinz/composer-normalize.
Example Usage
n/a
Checklist
n/a
To Do
n/a

Build failure is fixed in #336.

can you please rebase this on master?

@dbu
Done!

thanks!

Thank you, @dbu!


🚀Perf/utils：add goruntine

🚀Perf/utils：add goruntine

util (grpc goroutine model ): now move in github.com/Go-To-Byte/grpc-goroutine


OSC_PARAM changes all parameters to zero before first OSC_CYCLE call

Describe the bug
(It may not be a bug but an issue of API specification. Anyway, I report this because someone might come into the same issue or have some solution for this issue.
I set a global variable to a non-zero value in OSC_INIT(). The variable also can be modified from OSC_PARAM(). At the first OSC_CYCLE() call, the variable is always zero. If I remove the lines modifying the variable from OSC_PARAM(), the issue would disappear. I think this is because OSC_PARAM() is invoked with all parameters are zero' ed, after OSC_INIT() and before the first OSC_CYCLE() call,
So, how can I initialize parameters in OSC_INIT() with keeping it modifiable from OSC_PARAM()?
To Reproduce
#include "userosc.h"

#define SINE   0
#define SQUARE 1

typedef struct State {
  float phase;
  uint8_t wave;
} State;

static State s_state;

void OSC_INIT(uint32_t platform, uint32_t api)
{
  s_state.phase = 0.f;
  s_state.wave = SQUARE;          /* wave is set to SQUARE, but... */
}

void OSC_CYCLE(const user_osc_param_t * const params,
               int32_t *yn,
               const uint32_t frames)
{
  const float w0 = osc_w0f_for_note((params->pitch)>>8, params->pitch & 0xFF);
  float phase = s_state.phase;

  q31_t * __restrict y = (q31_t *)yn;
  const q31_t * y_e = y + frames;

  for (; y != y_e; ) {
    float sig;
    switch (s_state.wave) {        /* wave is ALWAYS SINE ! */
    case SINE:
      sig = osc_sinf(phase);
      break;
    case SQUARE:
      sig = osc_sqrf(phase);
      break;
    }

    *(y++) = f32_to_q31(sig);

    phase += w0; phase -= (uint32_t)phase;
  }
  s_state.phase = phase;
}

void OSC_NOTEON(const user_osc_param_t * const params){}
void OSC_NOTEOFF(const user_osc_param_t * const params){}

void OSC_PARAM(uint16_t index, uint16_t value) {
  switch (index) {
  case k_user_osc_param_id1:
    s_state.wave = value;          /* removing this line solves the problem */
    break;
  default:
    break;
  }
}

Expected behavior
OSC_PARAM() initializes all parameters to "initial values," which should be specified in the manifest file.
Desktop (please complete the following information):

OS: [NTS1]
Version [1.1-0]

@boochow -- I think it's reasonable that OSC_PARAM is being called upon initialization of the oscillator program. If your oscillator program is used as part of a preset on the prologue or minilogue xd, OSC_PARAM is likely the way that the correct parameter values get set when that preset is recalled.
There are bugs related to this behavior though, particularly with bipolar parameters. Please see my bug #36 .

@h2g2guy  thank you for your comment! I agree with you that OSC_PARAM should set the parameters to the appropriate value when a preset program is loaded. It is a completely reasonable behavior.
My point is that I want to define initial values of parameters for NTS1, which is not able to have any preset programs. Currently, the SDK always sets all parameters for their minimum values. I also think that maybe the initial-value feature would be useful for Prologue/Minilouge xd because it could give default parameter values for a new patch.


Argument #2 ($record) - null given

Filament\Actions\ViewAction::Filament\Actions{closure}(): Argument #2 ($record) must be of type Illuminate\Database\Eloquent\Model, null given, called in /app/vendor/filament/support/src/Concerns/EvaluatesClosures.php on line 35
I'm getting this when I click an event and it's trying to open an edit modal.
This is just using current filament and plugin versions, just walking through the example code - no major integration with anything else.
Has something recently changed that might trigger this?

Hey! Can you share some related code? Just tested here and it seems to work properly.
https://github.com/saade/filament-fullcalendar/assets/14329460/0703ba90-34dc-4c71-9e37-843628e2563d

@saade  - apologies!  I got pulled away to other aspects of the project.  I will be looking back at this later this week!

Going to close this - I rebuilt some of the code and it's working.


read me description for routing is misleading

"mavlink-router mainly routes mavlink packets from one endpoint to the other endpoints without differentiating what they are."

Messages will be processed based on the mavlink routing standard. https://mavlink.io/en/guide/routing.html#routing-detail
There is a vector for each endpoint instance that adds new sender sysid/compid pairs that it sees. If a message with sender sys_id and compid is received that is listed in the endpoint vector, it will be rejected.

can you point can you detail what exactly is misleading or maybe propose a change to the README.md through  a patch?

"mavlink-router mainly routes mavlink packets from one endpoint to the other endpoints without differentiating what they are."
without differentiating what they [mavlink packets] are.
If I'm not mistaken, this is not the case. There is some filtering happening which will appear as dropped packets if you assume that the ports are just copies of one another.

My understanding of that sentence is, that packets are routed between endpoint without differentiating between the endpoints. So the "they" is referencing to the last noun.

yea that makes sense. Okay, maybe still add something about the filtering?


grafana-agent: 0.41.1 -> 0.42.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for grafana-agent is: Lightweight subset of Prometheus and more, optimized for Grafana Cloud
meta.homepage for grafana-agent is: https://grafana.com/products/cloud
meta.changelog for grafana-agent is: https://github.com/grafana/agent/blob/v0.42.0/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.42.0 with grep in /nix/store/fxq3vhnrk1l7k5ac69hclbcwwqmgh3s8-grafana-agent-0.42.0
found 0.42.0 in filename of file in /nix/store/fxq3vhnrk1l7k5ac69hclbcwwqmgh3s8-grafana-agent-0.42.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

grafana-agent

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/fxq3vhnrk1l7k5ac69hclbcwwqmgh3s8-grafana-agent-0.42.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A grafana-agent https://github.com/r-ryantm/nixpkgs/archive/e787df99a3d80c4efd3dd162b23cb760bc492378.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/e787df99a3d80c4efd3dd162b23cb760bc492378#grafana-agent

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/fxq3vhnrk1l7k5ac69hclbcwwqmgh3s8-grafana-agent-0.42.0
ls -la /nix/store/fxq3vhnrk1l7k5ac69hclbcwwqmgh3s8-grafana-agent-0.42.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

grafana-agent

Maintainer pings
cc @flokli @emilylange for testing.

is there no backport?

is there no backport?

24.05 is still on 0.40.5 because both 0.41.0 and 0.41.1 had minor breaking changes.
I personally would argue the security fixes 0.42.0 aren't of particular severity considering grafana-agent usually runs in somewhat trusted environments.
But I suppose we could ignore the breaking changes and backport is anyway.
@tamara-schmitz can you comment on why you would like to see a backport of this? Just so we are on the same page. Thanks.

@tamara-schmitz can you comment on why you would like to see a backport of this? Just so we are on the same page. Thanks.

I am mostly concerned about CVE-2024-24790 for network environments where IPv4 addresses are mapped to IPv6 addresses.

Backport in #333036


Change predicate to not m_attachingSource

Summary: NeedData does not wait for attach source because the m_attachingSource is true, fix this by checking !m_attachingSource in the wait.
Type: Fix
Test Plan: Unittests, Component Tests, Aamp DASH video test stream.
Jira: RIALTO-431

https://jenkins.code.rdkcentral.com/job/github-triggered/46987/ started

https://jenkins.code.rdkcentral.com/job/build-component/86341/ started.

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/github-triggered/12488/ started

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/build-component-platform/18608/ started.

Sanity tests for ['RPI4 Hybrid'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/36568/

Job for AI/job/AI_BUILDS/job/AI-Trigger-PullRequests started: https://pv-jen015.uk2.scp.bskyb.com/job/AI/job/AI_BUILDS/job/AI-Trigger-PullRequests/136/


Staged CI for core and vmdb plugins

Staged CI
As we split out providers, UI and other vmdb plugins we are seeing interdependencies of those repos.
Now, I think this is good and intended. Pain is weakness leaving the body. Because we have to remove those interdependencies.
People will create PRs that are green on the respective repo, but once merged turn other repos unintentionally red.
We might consider a staged CI approach where

CI runs repos specs on PR
miq-bot is told to merge
CI runs all vmdb plugin specs and only merges if green

Links

Gitter discussion around this: https://gitter.im/ManageIQ/manageiq?at=587f7f3b11e7a7f61db10f50
Comment on keeping the specs exposed: https://github.com/ManageIQ/manageiq-providers-amazon/pull/92#issuecomment-268356230
A similar issue and proposal - but with our external dependencies as a problem source: https://github.com/ManageIQ/miq_bot/issues/165

cc @Fryguy @bdunne @jrafanie @martinpovolny @blomquisg @chessbyte @chrisarcand

@Fryguy what is the status of this? would love to hear your thoughts/plans - thanks!

@Fryguy any updates?

Closing since this is partly covered bt ManageIQ cross repo tests


'repo_overview' not working

clicking ''repo_overview''  -- no response

I don't know which page to redirect?


docs(aws-lambda): add name format description for aws lambda plugin

Summary
This PR adds a detailed description for the function_name format of the aws-lambda plugin.

Checklist

[na] The Pull Request has tests
[na] A changelog file has been created under changelog/unreleased/kong or skip-changelog label added on PR if changelog is unnecessary. README.md
[ ] There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

@nowNick All correct except the APi we're using is actually InvokeFunction which invokes a Lambda function. But the function name format is the same, it is the same for all these APIs related to Lambda function. As long as AWS API supports that format we'll support that too


Traceback Error

mdankideck --help
Traceback (most recent call last):
  File "/usr/local/bin/mdankideck", line 5, in <module>
    from markdown_anki_decks.cli import main
  File "/usr/local/lib/python3.9/site-packages/markdown_anki_decks/cli.py", line 8, in <module>
    import genanki
  File "/usr/local/lib/python3.9/site-packages/genanki/__init__.py", line 6, in <module>
    from .model import Model
  File "/usr/local/lib/python3.9/site-packages/genanki/model.py", line 3, in <module>
    import pystache
  File "/usr/local/lib/python3.9/site-packages/pystache/__init__.py", line 2, in <module>
    from init import *
ModuleNotFoundError: No module named 'init'

mdankideck /Users/xxx/Desktop/inout /Users/xxx/Desktop/output
Traceback (most recent call last):
  File "/usr/local/bin/mdankideck", line 5, in <module>
    from markdown_anki_decks.cli import main
  File "/usr/local/lib/python3.9/site-packages/markdown_anki_decks/cli.py", line 8, in <module>
    import genanki
  File "/usr/local/lib/python3.9/site-packages/genanki/__init__.py", line 6, in <module>
    from .model import Model
  File "/usr/local/lib/python3.9/site-packages/genanki/model.py", line 3, in <module>
    import pystache
  File "/usr/local/lib/python3.9/site-packages/pystache/__init__.py", line 2, in <module>
    from init import *
ModuleNotFoundError: No module named 'init'

Closing for now since I was unable to reproduce and I need more info to debug. If anyone else experiences something similar please let me know and I will reopen!


Dismiss Modal Barrier on handleTapCancel

Fixes https://github.com/flutter/flutter/issues/90223
This PR adds dismiss callback to onTapCancel modal barrier.
Native
https://user-images.githubusercontent.com/48603081/153480378-b26ef604-555c-485e-97c4-389b7b1f20dd.mp4
Flutter (with this PR)
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

This change does not causes a regression.
repro:
https://gist.github.com/chunhtai/db68a074f63f96fe2b997597599ebbbb

tap show dialog
tap and hold one finger on modal barrier without lifting it.
use other finger to tap ok

expect: alert dialog is dismissed and page stays at /abc
actual: alert dialog is dismissed, page /abc is popped
Preparing for revert.

Since the original issue #90233 is locked, I'm adding a few things.
If I'm not mistaken, the last time I saw the code for the popup it's using a ModalBarrier which is used on other types of popups (like dialogues). I believe it should have its own barrier, one that closes as soon as an interaction outside the popu menu is done.
Take for example the Gmail App on Android.
Here is an example of the drawer menu:

If you hold the barrier or drag up/down it stays open. It closes by a right to left gesture (even initiated from the barrier) or a single tap on the barrier.

This pop up to switch accounts. Stats open with hold or drags on the barrier but a single tap closes it.

Finally this pop-up menu that opens when tapping the meatballs menu on the top right of the email. Any gesture outside of it closes it, as soon as the screen is touched (tap down) it closes immediately. There's no way to keep it open when interacting with anything outside of the menu.
Now, the main reason I opened this issue is because I have had users complain that the app is frozen on a screen and sent me screenshots of a screen very similar to the last screenshot, where they open a pop-up menu that allows them to have multiple selections while open and then they try to scroll the screen behind it, the popup doesn't close and the screen behind doesn't scroll, which gives them the feeling that the app is frozen. Also, it's unbelievable the amount of people that think that to close a popup menu like the one in the third screenshot they have to "swipe up" instead of just a tap.
I have had reports of people trying to get back to the screen for several minutes before filing the support ticket and even sent recorded videos of them picking options from the menu (which doesn't close since it's just picking on/off options) and then swiping outside the menu several times, fast and slow, in every direction but never tapping the screen with a single tap, believing somehow that the app is frozen and only the menu is interactive until they have to force close the app and reopen.
My issue is temporarily resolved because I implemented a custom popup menu that closes as soon as a gesture is detected on the custom barrier, but it's a mess of a code, only works with my data.
Then I tried the same thing on web and it's even worse.
You'd expect that when you have a popup menu open and scroll with the mousewheel, that at least the content behind scrolls freely, but no. (Like it does here in GitHub if you click the meatballs menu on the top right of this comment and then scroll up/down). On some pages, this behaves differently. Some retain the menu in place relative to the initial position where it opened, others keep it attached to the button that originated the menu and others close it immediately. O have a couple of examples, like using Google docs and opening one of the context menu options (file, edit) then scrolling the page below, or clicking the options menu in chrome and scrolling the page while open (it closes).
I believe that the Material Design guidelines states that a popup menu should close with any gesture, but dialogs can remain open unless dismissable with a tap on the barrier, but I'm not sure about this, it's just the behaviour I've see on apps like Google Play Store and Gmail, while other apps have alight modifications (like the steam app, where some popup menus on the screen remain open and attached to the button that originated it while allowing for scrolling of the whole content).
In any case, the current implementation doesn't allow anything but the same behavior than dialogs, which is dismiss with a tap where it should, at least, provide a few options (like close any gesture or passthrough, maybe with options to remain open relative to screen or attached to the button that opened it).

I didn't mean the current behavior is correct. The reason the change is reverted is that it introduced a different issue. We should find a find a fix that does not cause other regression.


Rename SCSS files, so no unnecessary stylesheets are generated.

Great catch. :smile: Thanks again!


will support custom errors?

what is custom errors?

https://soliditylang.org/blog/2021/04/21/custom-errors/

completion and goto definition not support yet


Fresnel - Propagation Bug

In implementing a validation coronagraph (based on the TDEM report 1, https://github.com/kuravih/poppy_example_notebooks/blob/TDEM_coronagraph/Fresnel/Coronagraph/TDEM_Coronagraph.ipynb) and the microscope prescription from the PROPER manual (https://github.com/douglase/poppy_example_notebooks/blob/master/Fresnel/Microscope_Example.ipynb), we found a significant error that crops up dramatically for small apertures and that shows this code is not quite ready for release.
for example, for a simple 1 lens system:
beam_diameter =  .025*u.m
fl = 0.7*u.m
wavefront = fresnel.FresnelWavefront(beam_radius=beam_diameter/2., wavelength=500.0e-9, npix=256, oversample=2)
diam = beam_diameter
wavefront.apply_lens_power(fresnel.GaussianLens(fl, name='M1'))
wavefront *= poppy.CircularAperture(radius=diam.value/2)
wavefront.display("both")
wavefront.propagate_fresnel(fl*2,display_intermed=True)
wavefront.display("both")

we see a non-circularly symmetric diffraction pattern at the ROC, independent of the oversampling:

This is a dramatic case of slighter asymmetries that have been visible in other tests, which I have not worried too much about, partly thinking they came from the hard edges of the apertures. But I've tried using a ant-aliased PROPER generated entrance aperture as the input, and while the higher-order effects go away, the quadrant pattern does not.
This seems to only effect the to and from spherical functions, since the plane-to-plane comparisons to PROPER show no such asymmetries. (#106).
I have implemented the test system above in PROPER and Zemax and both are circularly symmetric as expected.
I have limited time to debug this now but will look into it more when time allows.

Huh, that's definitely weird. Thanks for looking into this. I don't have any time now either so we'll have to await whenever time permits you to dig into it more...

Tracked it down, the quadratic phase operator needs to be shifted to match the FFT origin, we can't re-use the same operator as the lens which has it's origin on the center:

We can close this bug now that I merged your #115, correct?

Yep, thanks.

On Oct 1, 2015, at 8:19 PM, Marshall Perrin<EMAIL_ADDRESS>wrote:
We can close this bug now that I merged your #115, correct?
—
Reply to this email directly or view it on GitHub.

closed!