问题：上传文件遇到内存错误

[7819] 2022-09-05 11:42:22 已经禁用秒传检测，直接上传
[7685] ↑ 6.73GB/6.95GB 5.48MB/s(73.83MB/s) in 16m39.4s ............[7821] 2022-09-05 11:42:22 文件上传结果：  耗时 1秒
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0xabe5a3]
goroutine 541374 [running]:
github.com/tickstep/aliyunpan/internal/functions/panupload.(*UploadTaskUnit).Run(0xc000f9ce70, 0xc0298e4480)
/Users/tickstep/Documents/Workspace/go/projects/aliyunpan/internal/functions/panupload/upload_task_unit.go:354 +0xa83
github.com/tickstep/aliyunpan/internal/taskframework.(*TaskExecutor).Execute.func1(0xc0015644b0, 0xc000286630, 0xc0009f4ac8)
/Users/tickstep/Documents/Workspace/go/projects/aliyunpan/internal/taskframework/executor.go:111 +0x62
created by github.com/tickstep/aliyunpan/internal/taskframework.(*TaskExecutor).Execute
/Users/tickstep/Documents/Workspace/go/projects/aliyunpan/internal/taskframework/executor.go:108 `+0x7c
在上传文件夹占用空间大概在1T以上时，必然会遇到这个报错，我是用的命令是 aliyunpan u ./ok /U2 --norapid --ow -pp
报错后再次使用该命令尝试继续上传会报错：
[0] 当前文件上传最大并发量为: 15, 上传分片大小为: 10.00MB
打开上传未完成数据库错误: panupload.UploadingDatabase.UploadingList: []*panupload.Uploading: panupload.Uploading.LocalFileMeta: Path: localfile.SymlinkFile.LogicPath: readStringSlowPath: unexpected end of input, error found in #10 byte of ...|icPath":"/|..., bigger context ...|12},"upload_done":true}]}},{"path":{"logicPath":"/|...

我把上传缓存增加到10MB后，目前还没有报错。已经上传到第23000个文件了。

今天在上传到18000文件时遇到同样问题

帮忙收集一些debug日志。
你单个文件的最大大小是多少，我有点怀疑过大文件不允许这样传。

帮忙收集一些debug日志。 你单个文件的最大大小是多少，我有点怀疑过大文件不允许这样传。

有日志文件可以方便查看吗？单个文件最大不会超过100G

帮忙收集一些debug日志。 你单个文件的最大大小是多少，我有点怀疑过大文件不允许这样传。

有日志文件可以方便查看吗？单个文件最大不会超过100G

debug日志你看readme文档，有教程怎么开。

好的，我开启了debug日志，我在复现问题后上传

我使用aliyunpan u ./ok /U2/ --ow 2>&1 > ./debuglog.log命令没能成功将debug日志保存到文件中。我主要有几个文件上传失败。文件中最后一段log是
[6426] 2022-09-07 06:57:22 准备上传: /root/Downloads/ok/HUNTER X HUNTER 2011 BLURAY COFFRET FRANCAIS 2xBLURAYBOX ^~^DragonMax^~^/HUNTER_X_HUNTER_DISC_17-DragonMax/BDMV/STREAM/00043.m2ts => /U2/ok/HUNTER X HUNTER 2011 BLURAY COFFRET FRANCAIS 2xBLURAYBOX ^~^DragonMax^~^/HUNTER_X_HUNTER_DISC_17-DragonMax/BDMV/STREAM/00043.m2ts
[6426] 2022-09-07 06:57:22 检测秒传中, 请稍候...
[6426] 2022-09-07 06:57:22 秒传失败，开始正常上传文件
[6412] 2022-09-07 06:57:22 文件上传结果： 失败！上传文件失败,The resource upload_id cannot be found. upload is not exist or has been completed 耗时 0秒
[6478] 2022-09-07 06:57:22 准备上传: /root/Downloads/ok/HUNTER X HUNTER 2011 BLURAY COFFRET FRANCAIS 2xBLURAYBOX ^~^DragonMax^~^/HUNTER_X_HUNTER_DISC_18-DragonMax/BDMV/BACKUP/index.bdmv => /U2/ok/HUNTER X HUNTER 2011 BLURAY COFFRET FRANCAIS 2xBLURAYBOX ^~^DragonMax^~^/HUNTER_X_HUNTER_DISC_18-DragonMax/BDMV/BACKUP/index.bdmv
[6478] 2022-09-07 06:57:22 检测秒传中, 请稍候...
[6478] 2022-09-07 06:57:22 秒传失败，开始正常上传文件
[6183] 2022-09-07 06:57:22 文件上传结果： 失败！上传文件失败,The resource upload_id cannot be found. upload is not exist or has been completed 耗时 0秒
[6531] 2022-09-07 06:57:22 准备上传: /root/Downloads/ok/HUNTER X HUNTER 2011 BLURAY COFFRET FRANCAIS 2xBLURAYBOX ^~^DragonMax^~^/HUNTER_X_HUNTER_DISC_18-DragonMax/BDMV/STREAM/00004.m2ts => /U2/ok/HUNTER X HUNTER 2011 BLURAY COFFRET FRANCAIS 2xBLURAYBOX ^~^DragonMax^~^/HUNTER_X_HUNTER_DISC_18-DragonMax/BDMV/STREAM/00004.m2ts
[6531] 2022-09-07 06:57:22 检测秒传中, 请稍候...
[6531] 2022-09-07 06:57:22 秒传失败，开始正常上传文件
[6296] 2022-09-07 06:57:22 文件上传结果： 失败！上传文件失败,The resource upload_id cannot be found. upload is not exist or has been completed 耗时 0秒
[6414] 2022-09-07 06:57:22 文件上传结果： 失败！上传文件失败,The resource upload_id cannot be found. upload is not exist or has been completed 耗时 0秒
[9198] ↑ 1.32GB/7.08GB 6.07MB/s(29.26MB/s) in 3m26s ............[6422] 2022-09-07 06:57:22 文件上传结果： 失败！上传文件失败,The resource upload_id cannot be found. upload is not exist or has been completed 耗时 0秒
[6419] ↑ 4.94GB/5.09GB 4.63MB/s(28.59MB/s) in 1m34s ............[6426] 2022-09-07 06:57:22 文件上传结果： 失败！上传文件失败,The resource upload_id cannot be found. upload is not exist or has been completed 耗时 0秒
[6478] 2022-09-07 06:57:22 文件上传结果： 失败！上传文件失败,The resource upload_id cannot be found. upload is not exist or has been completed 耗时 0秒
[6531] 2022-09-07 06:57:22 文件上传结果： 失败！上传文件失败,The resource upload_id cannot be found. upload is not exist or has been completed 耗时 0秒
[9198] ↑ 1.47GB/7.08GB 4.38MB/s(38.55MB/s) in 3m51s ...............
[6419] 2022-09-07 06:57:22 上传文件成功, 保存到网盘路径: /U2/ok/HUNTER X HUNTER 2011 BLURAY COFFRET FRANCAIS 2xBLURAYBOX ^~^DragonMax^~^/HUNTER_X_HUNTER_DISC_17-DragonMax/BDMV/STREAM/00032.m2ts
[9051] ↑ 4.64GB/7.09GB 8.19MB/s(15.53MB/s) in 11m16s ............[6419] 2022-09-07 06:57:22 文件上传结果： 成功！ 耗时 1分59秒
[9051] ↑ 4.93GB/7.09GB 7.87MB/s(39.96MB/s) in 11m59s ............[9286] 2022-09-07 06:58:22 文件上传结果： 失败！创建上传任务失败：context deadline exceeded (Client.Timeout or context cancellation while reading body),context deadline exceeded (Client.Timeout or context cancellation while reading body) 耗时 3分29秒
[6077] ↑ 0B/1.20MB 0B/s(28.57MB/s) in 6m54s ............[8463] 2022-09-07 07:02:22 文件上传结果： 失败！上传文件失败,context canceled 耗时 6分42秒
[8463] 上传文件失败, context canceled, 重试 2/3
[9198] ↑ 3.86GB/7.08GB 6.37MB/s(0B/s) in 9m47s ............[9150] 2022-09-07 07:03:22 文件上传结果： 失败！上传文件失败,context canceled 耗时 13分46秒
[9150] 上传文件失败, context canceled, 重试 1/3
[9199] ↑ 3.87GB/7.07GB 6.00MB/s(16.65MB/s) in 9m49s .............
[9051] 2022-09-07 07:03:22 上传文件成功, 保存到网盘路径: /U2/ok/めぞん一刻/MAISON_IKKOKU_13/BDMV/STREAM/00000.m2ts
[9051] ↑ 7.09GB/7.09GB 2.90MB/s(68.83MB/s) in 17m18s ............[9051] 2022-09-07 07:03:22 文件上传结果： 成功！ 耗时 19分20秒
[5713] ↑ 0B/1.15MB 0B/s(1.88MB/s) in 10m0s ............[9199] 2022-09-07 07:05:22 文件上传结果： 失败！上传文件失败,context canceled 耗时 13分23秒
[9199] 上传文件失败, context canceled, 重试 1/3
[5713] ↑ 0B/1.15MB 0B/s(0B/s) in 16m10s ............................
[9198] 2022-09-07 07:11:22 上传文件成功, 保存到网盘路径: /U2/ok/めぞん一刻/MAISON_IKKOKU_16/BDMV/STREAM/00000.m2ts
[9198] 2022-09-07 07:11:22 文件上传结果： 成功！ 耗时 19分35秒
[5713] ↑ 0B/1.15MB 0B/s(0B/s) in 3h4m19s ............
DEBUG日志一直在循环打印这一段log,已经持续好几个小时
[2022-9-7 15:56:54.085] do request url: https://api.aliyundrive.com/v2/file/get_upload_url
[2022-9-7 15:56:54.181] DEBUG: UPLOADER INFO: multiUpload worker upload file done
[2022-9-7 15:56:54.181] DEBUG: UPLOADER WARN: upload err: UrlExpired, id: 0
[2022-9-7 15:56:54.181] DEBUG: UPLOADER INFO: begin to upload part: 0
[2022-9-7 15:56:54.181] do request url: https://api.aliyundrive.com/v2/file/get_upload_url
[2022-9-7 15:56:54.378] DEBUG: UPLOADER INFO: multiUpload worker upload file done
[2022-9-7 15:56:54.378] DEBUG: UPLOADER WARN: upload err: UrlExpired, id: 0
[2022-9-7 15:56:54.378] DEBUG: UPLOADER INFO: begin to upload part: 0
[2022-9-7 15:56:54.378] do request url: https://api.aliyundrive.com/v2/file/get_upload_url
[2022-9-7 15:56:54.469] DEBUG: UPLOADER INFO: multiUpload worker upload file done
[2022-9-7 15:56:54.469] DEBUG: UPLOADER WARN: upload err: UrlExpired, id: 0
[2022-9-7 15:56:54.469] DEBUG: UPLOADER INFO: begin to upload part: 0

我使用aliyunpan u ./ok /U2/ --ow 2>&1 > ./debuglog.log命令没能成功将debug日志保存到文件中。我主要有几个文件上传失败。文件中最后一段log是 [6426] 2022-09-07 06:57:22 准备上传: /root/Downloads/ok/HUNTER X HUNTER 2011 BLURAY COFFRET FRANCAIS 2xBLURAYBOX ^~^DragonMax^~^/HUNTER_X_HUNTER_DISC_17-DragonMax/BDMV/STREAM/00043.m2ts => /U2/ok/HUNTER X HUNTER 2011 BLURAY COFFRET FRANCAIS 2xBLURAYBOX ^~^DragonMax^~^/HUNTER_X_HUNTER_DISC_17-DragonMax/BDMV/STREAM/00043.m2ts [6426] 2022-09-07 06:57:22 检测秒传中, 请稍候... [6426] 2022-09-07 06:57:22 秒传失败，开始正常上传文件 [6412] 2022-09-07 06:57:22 文件上传结果： 失败！上传文件失败,The resource upload_id cannot be found. upload is not exist or has been completed 耗时 0秒 [6478] 2022-09-07 06:57:22 准备上传: /root/Downloads/ok/HUNTER X HUNTER 2011 BLURAY COFFRET FRANCAIS 2xBLURAYBOX ^~^DragonMax^~^/HUNTER_X_HUNTER_DISC_18-DragonMax/BDMV/BACKUP/index.bdmv => /U2/ok/HUNTER X HUNTER 2011 BLURAY COFFRET FRANCAIS 2xBLURAYBOX ^~^DragonMax^~^/HUNTER_X_HUNTER_DISC_18-DragonMax/BDMV/BACKUP/index.bdmv [6478] 2022-09-07 06:57:22 检测秒传中, 请稍候... [6478] 2022-09-07 06:57:22 秒传失败，开始正常上传文件 [6183] 2022-09-07 06:57:22 文件上传结果： 失败！上传文件失败,The resource upload_id cannot be found. upload is not exist or has been completed 耗时 0秒 [6531] 2022-09-07 06:57:22 准备上传: /root/Downloads/ok/HUNTER X HUNTER 2011 BLURAY COFFRET FRANCAIS 2xBLURAYBOX ^~^DragonMax^~^/HUNTER_X_HUNTER_DISC_18-DragonMax/BDMV/STREAM/00004.m2ts => /U2/ok/HUNTER X HUNTER 2011 BLURAY COFFRET FRANCAIS 2xBLURAYBOX ^~^DragonMax^~^/HUNTER_X_HUNTER_DISC_18-DragonMax/BDMV/STREAM/00004.m2ts [6531] 2022-09-07 06:57:22 检测秒传中, 请稍候... [6531] 2022-09-07 06:57:22 秒传失败，开始正常上传文件 [6296] 2022-09-07 06:57:22 文件上传结果： 失败！上传文件失败,The resource upload_id cannot be found. upload is not exist or has been completed 耗时 0秒 [6414] 2022-09-07 06:57:22 文件上传结果： 失败！上传文件失败,The resource upload_id cannot be found. upload is not exist or has been completed 耗时 0秒 [9198] ↑ 1.32GB/7.08GB 6.07MB/s(29.26MB/s) in 3m26s ............[6422] 2022-09-07 06:57:22 文件上传结果： 失败！上传文件失败,The resource upload_id cannot be found. upload is not exist or has been completed 耗时 0秒 [6419] ↑ 4.94GB/5.09GB 4.63MB/s(28.59MB/s) in 1m34s ............[6426] 2022-09-07 06:57:22 文件上传结果： 失败！上传文件失败,The resource upload_id cannot be found. upload is not exist or has been completed 耗时 0秒 [6478] 2022-09-07 06:57:22 文件上传结果： 失败！上传文件失败,The resource upload_id cannot be found. upload is not exist or has been completed 耗时 0秒 [6531] 2022-09-07 06:57:22 文件上传结果： 失败！上传文件失败,The resource upload_id cannot be found. upload is not exist or has been completed 耗时 0秒 [9198] ↑ 1.47GB/7.08GB 4.38MB/s(38.55MB/s) in 3m51s ............... [6419] 2022-09-07 06:57:22 上传文件成功, 保存到网盘路径: /U2/ok/HUNTER X HUNTER 2011 BLURAY COFFRET FRANCAIS 2xBLURAYBOX ^~^DragonMax^~^/HUNTER_X_HUNTER_DISC_17-DragonMax/BDMV/STREAM/00032.m2ts [9051] ↑ 4.64GB/7.09GB 8.19MB/s(15.53MB/s) in 11m16s ............[6419] 2022-09-07 06:57:22 文件上传结果： 成功！ 耗时 1分59秒 [9051] ↑ 4.93GB/7.09GB 7.87MB/s(39.96MB/s) in 11m59s ............[9286] 2022-09-07 06:58:22 文件上传结果： 失败！创建上传任务失败：context deadline exceeded (Client.Timeout or context cancellation while reading body),context deadline exceeded (Client.Timeout or context cancellation while reading body) 耗时 3分29秒 [6077] ↑ 0B/1.20MB 0B/s(28.57MB/s) in 6m54s ............[8463] 2022-09-07 07:02:22 文件上传结果： 失败！上传文件失败,context canceled 耗时 6分42秒 [8463] 上传文件失败, context canceled, 重试 2/3 [9198] ↑ 3.86GB/7.08GB 6.37MB/s(0B/s) in 9m47s ............[9150] 2022-09-07 07:03:22 文件上传结果： 失败！上传文件失败,context canceled 耗时 13分46秒 [9150] 上传文件失败, context canceled, 重试 1/3 [9199] ↑ 3.87GB/7.07GB 6.00MB/s(16.65MB/s) in 9m49s ............. [9051] 2022-09-07 07:03:22 上传文件成功, 保存到网盘路径: /U2/ok/めぞん一刻/MAISON_IKKOKU_13/BDMV/STREAM/00000.m2ts [9051] ↑ 7.09GB/7.09GB 2.90MB/s(68.83MB/s) in 17m18s ............[9051] 2022-09-07 07:03:22 文件上传结果： 成功！ 耗时 19分20秒 [5713] ↑ 0B/1.15MB 0B/s(1.88MB/s) in 10m0s ............[9199] 2022-09-07 07:05:22 文件上传结果： 失败！上传文件失败,context canceled 耗时 13分23秒 [9199] 上传文件失败, context canceled, 重试 1/3 [5713] ↑ 0B/1.15MB 0B/s(0B/s) in 16m10s ............................ [9198] 2022-09-07 07:11:22 上传文件成功, 保存到网盘路径: /U2/ok/めぞん一刻/MAISON_IKKOKU_16/BDMV/STREAM/00000.m2ts [9198] 2022-09-07 07:11:22 文件上传结果： 成功！ 耗时 19分35秒 [5713] ↑ 0B/1.15MB 0B/s(0B/s) in 3h4m19s ............
DEBUG日志一直在循环打印这一段log,已经持续好几个小时 [2022-9-7 15:56:54.085] do request url: https://api.aliyundrive.com/v2/file/get_upload_url [2022-9-7 15:56:54.181] DEBUG: UPLOADER INFO: multiUpload worker upload file done [2022-9-7 15:56:54.181] DEBUG: UPLOADER WARN: upload err: UrlExpired, id: 0 [2022-9-7 15:56:54.181] DEBUG: UPLOADER INFO: begin to upload part: 0 [2022-9-7 15:56:54.181] do request url: https://api.aliyundrive.com/v2/file/get_upload_url [2022-9-7 15:56:54.378] DEBUG: UPLOADER INFO: multiUpload worker upload file done [2022-9-7 15:56:54.378] DEBUG: UPLOADER WARN: upload err: UrlExpired, id: 0 [2022-9-7 15:56:54.378] DEBUG: UPLOADER INFO: begin to upload part: 0 [2022-9-7 15:56:54.378] do request url: https://api.aliyundrive.com/v2/file/get_upload_url [2022-9-7 15:56:54.469] DEBUG: UPLOADER INFO: multiUpload worker upload file done [2022-9-7 15:56:54.469] DEBUG: UPLOADER WARN: upload err: UrlExpired, id: 0 [2022-9-7 15:56:54.469] DEBUG: UPLOADER INFO: begin to upload part: 0

看着是上传链接过期了导致不断重试。
你把aliyunpan_uploading.json的文件删除，再上传应该就能上传成功了。我看看怎么改善下这个问题


Stack Club Spring Course

We have been talking about starting a new phase of stack club where we teach a "course" targeting new users. This would probably mean something like six weeks where we hold one 2-hour session per week, followed by two weeks where participants work on "final projects" (i.e., their own notebooks).
The six-week course would be taught by current stack club members and would focus around the notebooks that we have already created.
The target start date would be somewhere around April 2020.
@Madejski @drphilmarshall what do you think? Would you be able to help me organize and advertise?

I'm not sure whether or not this is relevant.
We're running an intro to LSST stack things in Princeton in early December.  I think it'll be on blue jeans;  I think anyone will be welcome to attend remotely (but possibly muted)
				R

We have been talking about starting a new phase of stack club where we teach a "course" targeting new users. This would probably mean something like six weeks where we hold one 2-hour session per week, followed by two weeks where participants work on "final projects" (i.e., their own notebooks).
The six-week course would be taught by current stack club members and would focus around the notebooks that we have already created.
The target start date would be somewhere around April 2020.


[[Power-Fx]] Localization hand-back [CTAS - RunID=20230628-152706-py22mbkq87]

Translation handback check-in (PR Created by automation).

✅ No public API change.

Closing as this PR is 2-week-old and changes from dev on strings are now in place.


chore: refactor metaverse service

There was a component called deployer implementing this interface:
interface MetaverseContentService {
  deployEntity
  isContentAvailable
  getContent
  getDeployments
}

As we may see, all of these methods are related to deployments but only deployEntity is something that you would expect from a "deployer". So we can split the operations into two groups:

Read operations:   isContentAvailable, getContent , getDeployments, getDeploymentsForActiveEntities
Write operation: deployEntity.

In addition, we can see in the code that the read operations don't use the logic in the deployEntity logic. For the sake of simplicity and separation of responsibility, the logic between the two groups was separated in two different files.
To summarize the changes proposed in this PR are:

The read operations logic was moved to the already existing file src/logic/deployments.ts.
The write operation logic was moved to a new component called Deployer in src/ports/deployer.ts.
All types associated with both operations that were defined in multiple files all across the code were condensed and moved to a new file src/deployment-types.ts.

THANK YOU SO MUCH FOR REMOVING THAT NAME


Fixed #26834 -- Included min/max values in IntegerField formfield

Rebased from #6964.
https://code.djangoproject.com/ticket/26834
Edit: Tests are breaking, I'll look into it.

@rixx Thanks! Some test are falling there is also an issue with multiple validators (see comment), and mysterious "issue related to the validators property" (see comment).

Ah, I had unfairly ignored the issues with multiple validators. I added handling and tests for this case.
As for the validators property, I believe it's suitable for this feature, so I don't see any issue with it at this point.

Tests are breaking, and this is why: On databases with proper limits on their integer fields (so all supported ones apart from sqlite3), there are Min/Max validators on IntegerFields to prevent overflows and keep IntegerFields to the values they are rated for.
This would now result in these min/max values to be added to form fields, e.g. -2147483648 as a typical min value on a form with no further min value validation.
I'd argue that this is actually well-behaved form generation, as the form should prevent values from reaching the database that we know will now be acceptable. But it makes this change more frontend facing. Is this acceptable? If it is, I'll need some minor help in building better tests and how to phrase the release notes.

Also note that limit_value can be callable as of 2.2 which required a fix released in 2.2.1 - see https://github.com/django/django/pull/11180.
I would recommend revisiting my suggestion in that PR to make limit_value a settable property to hide away the callable stuff so that we can avoid the potential for crashes in all new places that attempt to use limit_value.
Note that my suggestion was rejected at the time as too invasive for a regression fix, but this highlights the exact situation my proposal was aiming to prevent.

Hmm, so either we wait for your suggestion to be implemented, or we add another piece of code and tests for callable values here. For the little it's worth, I fully agree with your suggested property based API – having all places that interact with Min/Max validators check for callable(my_validator.limit_value) seems unwieldy.

...having all places that interact with Min/Max validators check for callable(my_validator.limit_value) seems unwieldy.

Especially when the result of forgetting to do so is a crash.
I have prepared some code to refactor limit_value to handle callables transparently and will try to get a PR together later today if possible.

Yes, I think we should figure out first if

we are comfortable changing pretty much all forms with IntegerFields, potentially breaking many tests out there, and
potentially leaking the database in use by providing database-related min/max values

before I continue working on this.

@rixx Sorry for a late response :disappointed: . I missed your comment.
We should reach a wider audience and consensus on the mailing list before moving this forward.
Closing for now.


Add support for cron jobs in ARQ integration

This adds support for logging exceptions that occurs in ARQ cron jobs to Sentry.
Previously, only the tasks defined in the functions argument of the ARQ Worker Settings class were supported. Cron jobs were being ignored.
Since Cron Jobs run automatically by the worker object, we need to patch the worker instead of the func function that was previously patched.

Hey @lewazo !
Thanks for the PR!
It will take some time until we have the capacity to review this, please be patient.

ping

Btw @lewazo  and @iam-abbas Sentry has now a "Crons" feature, where cron jobs can submit their config (when it should run) on creation of a cron job and then can have check ins on each run (and on each success and failure) and then one has a nice UI in Sentry to see if the crons are running on time and if there are errors. Here is part of the implementation in Celery<EMAIL_ADDRESS>Maybe you want to add this too for ARQ?

Thanks @antonpirker that looks like a nice feature indeed and sounds perfect for this integration.
I'll reserve some time to take a look at implementing it for ARQ


Add get_true_posterior functions

This PR aims to add the functions to get the true posterior from both the power spectrum and full field.

Now everything is tested and working :)


Remove BC Layer for Symfony Translator versions 3 and lower

This PR partially resolves https://github.com/Behat/Behat/issues/1305

Anything needed from me here to push this forward?

Thanks!


How to automatically scall the workload to match demand?

Hello,
I successfully deployed Besu.  However, "member-1" is chashing because it cannot autoscale to match demand.
Thus, I'd like to know if using the Horizontal Pod Autoscaler is the appropiate way to automatically scall the workload to match demand.
If yes, how can I implement it in this repo?
Regards,

Hello @andyafene this has been answered here https://discord.com/channels/905194001349627914/938504958909747250/965563388476403742
You need to enable the autoscaler on the cluster you created and isn't part of the charts in this repo. Please see the Azure docs on how to enable the autoscaler https://docs.microsoft.com/en-us/azure/aks/cluster-autoscaler


VanillaNet use 4*4 kernel

Many chips are optimized for 3×3 kernel, will it be slow to use 4×4 kernel on the mobile ? For example, on the MTK chip.

Thanks for the nice suggestion. Since we use a stride 4 convolution, a 3*3 kernel will miss the information in the input features. Therefore, we use 4x4 kernel for the stem.


3.0.222 release did not get completed

👋 looks like 3.0.222 release did not get completed, raise this issue for some awareness. Thanks!
relates to https://github.com/Homebrew/homebrew-core/pull/183412

Thanks for your feedback, The issue was caused by package certs. It has been fixed.


The module 'hooks' could not be loaded.

Hi,
When running ask deploy I'm getting the below error:
PS D:\My Documents\Alexa\dublin-stream> ask deploy
& : The module 'hooks' could not be loaded. For more information, run 'Import-Module hooks'.
At line:1 char:6
+ & {& 'hooks\pre_deploy_hook.ps1' Dublin_Stream $False all}
+      ~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (hooks\pre_deploy_hook.ps1:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CouldNotAutoLoadModule

[Error]: Hook Scripts failed
PS D:\My Documents\Alexa\dublin-stream> Import-Module hooks
Import-Module : The specified module 'hooks' was not loaded because no valid module file was found in any module directory.
At line:1 char:1
+ Import-Module hooks
+ ~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ResourceUnavailable: (hooks:String) [Import-Module], FileNotFoundException
    + FullyQualifiedErrorId : Modules_ModuleNotFound,Microsoft.PowerShell.Commands.ImportModuleCommand

This has been resolved.


Open Script on Line number with EditorPlugin

Operating system or device - Godot version:
2.1.3 Steam Stable
Using EditorPlugin;
May I suggest we add the option to open a script on a specific line?
This would be useful in the case of Jahn's TODO plugin  - Instead of just opening the script, we could open it and navigate to a specific line number. :)

There's Go to Line already, shouldn't be hard to do.

@vnen yes, but I guess @Tybobobo meant that there is no way to get script editor reference.

Can the script editor be exposed to editor plugins instead of adding more functions to EditorPlugin?

Is this a problem any more? I see that EditorInterface has a public get_script_editor() method that returns the ScriptEditor singleton.

@kareed44 no, because although there is an API for the script editor, it still does not expose a way to open a script at a given line, or even just scroll the current TextEdit to that line.


brew search xxx: curl: (35) SSL certificate problem: Couldn't understand the server certificate format

Please follow the general troubleshooting steps first:

[x] Ran brew update and retried your prior step?
[x] Ran brew doctor, fixed as many issues as possible and retried your prior step?
[x] If you're seeing permission errors tried running sudo chown -R $(whoami) $(brew --prefix)?
[x] Confirmed this is problem with Homebrew/brew and not specific formulae? If it's a formulae-specific problem please file this issue at https://github.com/Homebrew/homebrew-core/issues/new

Bug reports:
I'm seeing the following error on one machine, but not another. Would really appreciate a tip on what specific curl command brew search is running that might be failing so I can run that curl command manually and troubleshoot further.
$ brew search pip --verbose
aespipe                    pipebench                  pipeviewer
brew-pip                   pipemeter                  pyenv-pip-migrate
lesspipe                   pipes-sh                   spiped
homebrew/completions/pip-completion      homebrew/science/methpipe
homebrew/science/bpipe

If you meant "pip" precisely:

Homebrew provides pip via: `brew install python`. However you will then
have two Pythons installed on your Mac, so alternatively you can install
pip via the instructions at:
  https://pip.readthedocs.io/en/stable/installing/
Error: curl failed!   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (35) SSL certificate problem: Couldn't understand the server certificate format
curl: (3) <url> malformed

I've already looked at this similar closed issue: https://github.com/Homebrew/brew/issues/1324
The root cause in that issue appeared to be a corporate network using man-in-the-middle certificate(s), but I'm not on a network currently and not using any custom certificates (that I know of :).

Strange - just tried the same command now on the same machine that had the problem and now NO ERROR. Some kind of intermittent GitHub issue? Would still be good to know what the curl command brew search is running that was failing.

The problem is back. No idea.

It seems I have the same issue
$ brew update
fatal: unable to access 'https://github.com/Homebrew/brew.git/': SSL certificate problem: Couldn't understand the server certificate format
fatal: unable to access 'https://github.com/d12frosted/homebrew-emacs-plus/': SSL certificate problem: Couldn't understand the server certificate format
fatal: unable to access 'https://github.com/Homebrew/homebrew-binary/': SSL certificate problem: Couldn't understand the server certificate format
fatal: unable to access 'https://github.com/Homebrew/homebrew-core/': SSL certificate problem: Couldn't understand the server certificate format
fatal: unable to access 'https://github.com/Homebrew/homebrew-games/': SSL certificate problem: Couldn't understand the server certificate format
fatal: unable to access 'https://github.com/neovim/homebrew-neovim/': SSL certificate problem: Couldn't understand the server certificate format
fatal: unable to access 'https://github.com/railwaycat/homebrew-emacsmacport/': SSL certificate problem: Couldn't understand the server certificate format
fatal: unable to access 'https://github.com/thoughtbot/homebrew-formulae/': SSL certificate problem: Couldn't understand the server certificate format
Error: Fetching /usr/local/Homebrew failed!
Fetching /usr/local/Homebrew/Library/Taps/d12frosted/homebrew-emacs-plus failed!
Fetching /usr/local/Homebrew/Library/Taps/homebrew/homebrew-binary failed!
Fetching /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core failed!
Fetching /usr/local/Homebrew/Library/Taps/homebrew/homebrew-games failed!
Fetching /usr/local/Homebrew/Library/Taps/neovim/homebrew-neovim failed!
Fetching /usr/local/Homebrew/Library/Taps/railwaycat/homebrew-emacsmacport failed!
Fetching /usr/local/Homebrew/Library/Taps/thoughtbot/homebrew-formulae failed!

Same thing with brew search
$ brew search pip --verbose
aespipe                     lesspipe                    pipemeter                   pipeviewer                  spiped
brew-pip                    pipebench                   pipes-sh                    pyenv-pip-migrate

If you meant "pip" precisely:

Homebrew provides pip via: `brew install python`. However you will then
have two Pythons installed on your Mac, so alternatively you can install
pip via the instructions at:
  https://pip.readthedocs.io/en/stable/installing/
Error: curl failed!   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (35) SSL certificate problem: Couldn't understand the server certificate format
curl: (3) <url> malformed

Sorry but you have not followed the requested steps on the Troubleshooting page
Please follow (all of) these steps and post the information here so we can help you with your problem.
Thanks!

Thanks, I think this is the only thing I haven't submitted yet.
doctor is clean no problems.
Not seeing the curl problem today.
$ brew config
HOMEBREW_VERSION: 1.1.2
ORIGIN: https://github.com/Homebrew/brew
HEAD: 0f529dae1043639058130092cf35e68d18907cb8
Last commit: 8 days ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 88cfb1560bf02d5c10077a243f95652e95a7806b
Core tap last commit: 19 hours ago
HOMEBREW_PREFIX: /usr/local
HOMEBREW_REPOSITORY: /usr/local/Homebrew
HOMEBREW_CELLAR: /usr/local/Cellar
HOMEBREW_BOTTLE_DOMAIN: https://homebrew.bintray.com
CPU: octa-core 64-bit ivybridge
Homebrew Ruby: 2.0.0-p648
Clang: 8.0 build 800
Git: 2.11.0 => /usr/local/bin/git
Perl: /usr/bin/perl
Python: /usr/local/bin/python => /usr/local/Cellar/python/2.7.12_2/Frameworks/Python.framework/Versions/2.7/bin/python2.7
Ruby: /usr/local/bin/ruby => /usr/local/Cellar/ruby/2.3.3/bin/ruby
Java: 1.8.0_112
macOS: 10.12.1-x86_64
Xcode: 8.1
CLT: <IP_ADDRESS>.1.1476494586
X11: N/A

I'm afraid there's nothing Homebrew can do if you can't connect to GitHub. It's performing a normal curl query to https://api.github.com.

Thanks, might be some kind of MacOS issue. Had SSL CERT errors at one point in Google Chrome trying to open google.com, and running brew search pip at that time gave the curl (35) ssl error also. Logging out and back in fixed the issue.

Documenting here for anyone else coming by. Similar-sounding problems also reported by John Siracusa of ATP Podcast on the Dec 7 podcast.
Most likely trigger for the problem: enabling iCloud Keychain in iCloud settings
One or more observable symptoms when issue is happening:

A pop-up MacOS message that keychain has to be repaired/reset
When looking at Keychain Access tool, keychains appear to be empty and set to Read-Only mode
When looking at Keychain Access tool, keychain icons on sidebar are missing (dotted borders)
Trying to navigate to https://google.com in Google Chrome fails with an SSL CERT error
Running brew search pip for example, shows the curl (35) certificate error message

The problem can be temporarily resolved by logging out and back in, and/or rebooting. After it is resolved, the Keychain Access tool will show all the keychains and their contents as it should. The problem is likely to recur at a later time.
Hoping (fingers X) that a Mac OS patch (maybe 10.12.2?) will resolve the root cause.
Otherwise one idea is to disable the iCloud Keychain option in iCloud prefs (have not yet tried).


Export to PDF utilities for selfhosting

Hi, Thanks for developing stackedit. I like its expressiveness. I want to self-host it. I also need the utility that converts the markdown to PDF.
If you don't mind, can you please share with us which technology you use for the conversion? And if possible, also open source your solution?
Many thanks in advance.

Hi, please send an email to<EMAIL_ADDRESS>if you need some (not-free) support.


Update lifecycle to 0.10.2 & provide support for platform apis 0.5,0.4,0.3

Drop support for platform api 0.2
If using 0.4+ default the process type to web (identical to pack behavior)
Prevent notary/windows on platform api 0.3

Perhaps we should validate that there is a supported platform api on builder creation. cc' @tylerphelan

Perhaps we should validate that there is a supported platform api on builder creation. cc' @tylerphelan

When this rfc is implemented (likely in platform api 0.6) we can remove the default process type to web flag.

When this rfc is implemented (likely in platform api 0.6) we can remove the default process type to web flag.


Dalli Cache Store should allow users to opt out of ActiveSupport::Cache::Entry

Rails 3.x unified the implementation and feature set of the various different cache stores.  It did this by introducing ActiveSupport::Cache::Entry which it stores in the various stores.  Those entries provide information on the ttl etc allowing things like the memory store to support memcached style features.
However for memcached stores this is pretty wasteful.  The serialized Entry classes add about 108 bytes to every single item stored, causing increased cache usage,  especially with small values being cached. When multiplied over 10,000s of items, that's a big number.
Ideally dalli would allow users to 'opt out' of this functionality to save the ram / cpu cycles.

I'd love to see dalli_store drop the Cache base class and remove the Entry wrapper since you're right: dalli/memcached already implement 90% of the functionality, e.g. compression, marshalling, namespacing, expiration.

Strictly speaking you can't do the compression functionality the same way that Entry can, compressing some values and not others but transparently reading them all.  However no one actually wants to do that ;)

Dalli already does that so I guess I can code the impossible. Hint: memcached allows you to attach flags to each value.
On Feb 23, 2012, at 10:45 PM, Michael<EMAIL_ADDRESS>wrote:

Strictly speaking you can't do the compression functionality the same way that Entry can, compressing some values and not others but transparently reading them all.  However no one actually wants to do that ;)

Reply to this email directly or view it on GitHub:
https://github.com/mperham/dalli/issues/173#issuecomment-4152385

Ha, awesome.

I stand corrected, but still maintain no one wants to do that :-P

See the rework_store branch.  Initial benchmarking shows a definite speed increase from 4.0 sec to 3.0 sec.

Commit here: c23810882c747e6aa677e35931942b83537704fc

Looking good, I'd suggest adding two additional options, off by default, or doing it with an alternative store.
If you added :unwrap=>true then the read value could still have some code like
  if entry.is_a?(ActiveSupport::Cache::Entry)
   entry = entry.value
  end

this would let new versions read values written by the old version
Similarly you could add :return_wrapped=>true
  return ActiveSupport::Cache::Entry.new(entry)

Which would let the store return values in a manner consistent with what other libraries may be expecting, without actually incurring the overhead of additional storage costs?

I don't understand the point of return_wrapped.  Entry is an internal class just used by Cache::Store.  I'll add auto unwrap support to minimize migration pain.

Does Cache::Store properly handle feeding a value back to a client if it's not wrapped in an Entry?

@timhaines The dalli_store 1.x will auto-wrap bare values set by dalli_store 2.x in an Entry so it should work fine.  dalli_store 2.x doesn't use Cache::Store or Entry at all but it will unwrap Entries set by dalli_store 1.x with this next commit.


[Feature Request] CLI or ARM template provisioning

Is your feature request related to a problem? Please describe.
My customer wants to be able to automate the process of test creation and running so that a "standard set" of tests can be provisioned and run later.
Describe the solution you'd like
Test creation by an ARM template or through CLI calls.
Describe alternatives you've considered
I can see that there is a VS Code extension and also there are actions for pipelines. But the customer really wants to be able to deploy a library of tests and for others to later execute these. The execute element could be done in the portal, but I can't see how you can lodge a set of test scripts to be used later.
Additional context
This is in no sense a blocker for the customer, but it would be good to understand more on what automation is planned for load testing.
AB#1458968

@jometzg Thanks for reaching out. CLI support is planned for Azure Load Testing. Currently we support ARM template for resource creation and Azure Pipelines / GitHub actions for test creation. If you are using any of these tools, we recommend you to commit your test scripts to your repo so that they are version controlled. These can be run from the pipeline when required. Does this help with the customer's scenario?

@ninallam Can you provide an example ARM resource template? When I create an Azure Load Test resource via the portal and try to export the template I get the message
"{   "code": "ExportTemplateCompletedWithErrors",   "message": "Export template operation completed with errors. Some resources were not exported. Please see details for more information.",   "details": [     {       "code": "ResourceTypeSchemaNotFound",       "target": "Microsoft.LoadTestService/loadtests",       "message": "The schema of resource type 'Microsoft.LoadTestService/loadtests' is not available. Resources of this type will not be exported to the template."     }   ] }
When do you expect CLI support to be available?

Hi @dewolfs you can get the ARM template from the repository https://github.com/Azure-Samples/nodejs-appsvc-cosmosdb-bottleneck/tree/main/ARMTemplate

Azure Load Testing now supports creating tests from Az CLI https://learn.microsoft.com/cli/azure/load. Please try it out and let us know your feedback here.


Datetime retrieved from ModifiedField always returns datetime.utcnow()

Retrieving document's modified field always returns datetime.utcnow()

I'm looking into this. Fixing this is easy, but it revealed a few other issues with this field which I also want to try to fix

this was released earlier this year. closing


Removed the submit bing (Components\SubmitAudioComponent.razor and as…

Removed the submit bing (Components\SubmitAudioComponent.razor and associated JavaScript call in wwwroot\js\ai-for-orcas.js) from Pages\Detections\Candidates.razor (and code behind),
Pages\Detections\SingleDetection.razor (and code behind), and Pages\Detections\Unknown.razor (and code behind).
Replaced it with a call to pop up a Toast message indicating the detection submit was successful.

Hi, @micowan could you add a screenshot of what the toast looks like? Also, if you could follow-up with Dave about whether this feature would be desirable to him as well, that would be great.


Update OVS pipeline document

Resolves #5200

[x] PipelineRootClassifierTable
[x] ARPSpoofGuardTable
[x] ARPResponderTable
[x] ClassifierTable
[x] SpoofGuardTable
[x] UnSNATTable
[x] ConntrackTable
[x] ConntrackStateTable
[x] PreRoutingClassifierTable
[x] SessionAffinityTable
[x] ServiceLBTable
[x] EndpointDNATTable
[x] AntreaPolicyEgressRuleTable
[x] EgressRuleTable
[x] EgressDefaultTable
[x] EgressMetricTable
[x] L3ForwardingTable
[x] EgressMarkTable
[x] L3DecTTLTable
[x] SNATMarkTable
[x] SNATTable
[x] L2ForwardingCalcTable
[x] TrafficControlTable
[x] IngressSecurityClassifierTable
[x] AntreaPolicyIngressRuleTable
[x] IngressRuleTable
[x] IngressDefaultTable
[x] IngressMetricTable
[x] ConntrackCommitTable
[x] OutputTable

Not finished all tables yet.

@hongliangl please add Resolves #5200 to the PR summary to help closing the issue when the PR is merged.

Hi maintainers, we are close to v2.0 release date, @antoninbas @jianjuns @tnqn  could you help to prioritize this PR to review? Thanks.

@antoninbas Not addressed all review comments. Will continue that several hours later.

Thanks you guys for reviewing this big PR!

Thanks you guys for reviewing this big PR!

Thanks @hongliangl for working on this massive documentation PR!

echo @antoninbas
Thanks @hongliangl for working on this!


NIFI-4143 - externalize MAX_CONCURRENT_REQUESTS

Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit?

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[x] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

@pvillard31 Just started reviewing this PR. I'm wondering if the property should be associated with the cluster section instead of the web properties. This property is only relevant when clustered and am concerned it may be confusing being colocated with the jetty thread configuration. Since that thread pool drives the size of the thread pool that Jetty uses it could be confused with the maximum number of concurrent requests. It might make sense to associate this property with other request replication properties.
For instance the replication thread pool size:
nifi.cluster.node.protocol.threads=${nifi.cluster.node.protocol.threads}
nifi.cluster.node.protocol.max.threads=${nifi.cluster.node.protocol.max.threads}

Or the replication timeouts:
nifi.cluster.node.connection.timeout=${nifi.cluster.node.connection.timeout}
nifi.cluster.node.read.timeout=${nifi.cluster.node.read.timeout}

Thoughts?

Thanks for your feedback @mcgilman. You're right, let me know if this new naming is better.

Thanks @pvillard31! Most recent update looks great. This has been merged to master.


Unable to create default retention policy

Bug report
System info:
InfluxDB 1.0beta1
CentOS/7
Steps to reproduce:

CREATE DATABASE test
CREATE RETENTION POLICY default ON test DURATION INF REPLICATION 1 DEFAULT

Expected behavior: success
Actual behavior: ERR: error parsing query: found DEFAULT, expected identifier at line 1, char 25
Additional info:
This was encountered trying to fix issue #6825.
It appears to be an issue with naming the retention policy as default, even though no such retention policy exists:
> show retention policies on test
name	duration	shardGroupDuration	replicaN	default
autogen	0		168h0m0s		1		true

>
> CREATE RETENTION POLICY foo ON test DURATION INF REPLICATION 1 DEFAULT
>

Also, it would be grand if the error message didn't capitalize the input text when displaying the error. It's rather confusing to be told the error is with DEFAULT when I typed default, as the text DEFAULT occurs elsewhere on the line.

Ah, needs to be quoted. Perhaps this should be in the documentation.


New Experiment: disable timeline

See #34
But why?
https://world.hey.com/brecht/free-range-tweet-farming-9399f6e5

Released in v2.5


Unexpected Error from fuse mount

What happened?:
$ pachctl create-repo testrepo
$ echo "test" | pachctl put-file testrepo master /a/b/c/d.txt
Reading from stdin.
$ pachctl list-file testrepo master a
NAME TYPE SIZE
/a/b      dir      5B
$ mkdir pfs
$ pachctl mount pfs &
$ ls pfs/testrepo
a
$ ls pfs/testrepo/a
ls: reading directory 'pfs/testrepo/a: Input/output error

In addition, this error was reported in the pachd logs (retrieved with kubectl logs)
2018-10-25T20:20:07Z ERROR pfs.API.InspectFile {"duration":0.00161529,"error":"file a/a/b not found in repo testrepo at commit e6f08727e88341a4bb83ea0b09b75e28","request":{"file":{"commit":{"repo":{"name":"testrepo"},"id":"e6f08727e88341a4bb83ea0b09b75e28"},"path":"a/a/b"}},"response":null} []

What you expected to happen?:
$ ls pfs/testrepo/a
b

How to reproduce it (as minimally and precisely as possible)?:
(see above)
Anything else we need to know?:
Environment?:

Kubernetes version (use kubectl version):
  $ kubectl version
  Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.1", GitCommit:"4ed3216f3ec431b140b1d899130a69fc671678f4", GitTreeState:"clean", BuildDate:"2018-10-05T16:46:06Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
  Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.5", GitCommit:"32ac1c9073b132b8ba18aa830f46b77dcceb0723", GitTreeState:"clean", BuildDate:"2018-06-21T11:34:22Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

Pachyderm CLI version (use pachctl version):
  $ pachctl version
  COMPONENT           VERSION
  pachctl             1.7.10
  pachd               1.7.10

Cloud provider (e.g. aws, azure, gke) or local deployment (e.g. minikube vs dockerized k8s):
Deployed on AWS with kops.

OS (e.g. from /etc/os-release):
  $ cat /etc/os-release | head -n 2
  NAME="Ubuntu"
  VERSION="16.04.5 LTS (Xenial Xerus)"

Others:

This is fixed in 1.8.1, the output is as expected.


Remove option "--manager" description for swarm_join.md

Option "--manager" has been removed in the usage of the same md doc, so the description can be removed:
Usage:  docker swarm join [OPTIONS] HOST:PORT

Join a swarm as a node and/or manager

Options:
  --advertise-addr value   Advertised address (format: <ip|interface>[:port])
  --help                   Print usage
  --listen-addr value      Listen address (format: <ip|interface>[:port)
  --token string           Token for entry into the swarm

LGTM

LGTM (IANAM)

LGTM


[GHSA-4653-xjcv-7jcm] An arbitrary file upload vulnerability in the file upload...

Updates

Affected products
Summary

Comments
Add reference to npm module

Hi @elliottg-zi, I'm closing the pull request and not accepting the contribution because, per https://github.com/jaydenseric/graphql-upload/issues/304, CVE-2022-29353 is not a valid vulnerability. Thank you for your interest in GHSA-4653-xjcv-7jcm and have a good day.


new(docs): add regex and basename documentation

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind content

/kind event

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area documentation
What this PR does / why we need it:
As per title.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

content/OWNERS [LucaGuerra]

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

/hold
until 0.39.0 release

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leogr, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

content/OWNERS [LucaGuerra,leogr]

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

LGTM label has been added.  Git tree hash: cd98b65b269d92547f5463aa5705806f92f8c72f

/unhold


Fixed compilation on Mac Catalyst

Fix compilation on macCatalyst platform.
Motivation:
Support compilation on macCatalyst platform.
Modifications:
Updated availability guards in TLSConfiguration.
Result:
Fixes compilation on macCatalyst platform.
Closes #304

note that SSLProtocol is depreciated
/**
 * @enum SSLProtocol enumeration
 * @abstract Enumerations for the set of supported TLS and DTLS protocol versions.
 *
 * @note This enumeration is deprecated. Use `tls_protocol_version_t` instead.
 */
public enum SSLProtocol : Int32 {

    @available(iOS, introduced: 5.0, deprecated: 13.0)
    @available(macCatalyst, introduced: 13.0, deprecated: 13.0)
   // ...
}

CC @Lukasa

Hmm, given your notes above I went back and checked: I have no trouble building the package for macCatalyst. The fact that the macCatalyst guards are redundant suggests that you shouldn't be either. Are you confident that your Xcode build is using the Xcode toolchain and not an OSS one?

I'm increasingly wondering if some of the platform checking for macCatalyst is not working right, as I'm seeing build warnings about redundant checking which don't make any sense either. Let's see if we can drill down to why this is happening.

For now we can address the warning about SSLProtocol. If you add @available(iOS, introduced: 5.0, deprecated: 13.0) to TLSVersion.sslProtocol then that will nicely resolve the build warnings for that.

Hmm, given your notes above I went back and checked: I have no trouble building the package for macCatalyst. The fact that the macCatalyst guards are redundant suggests that you shouldn't be either. Are you confident that your Xcode build is using the Xcode toolchain and not an OSS one?

How do you build it?
I have only Xcode installed, OSS Swift running typically in Docker;
I tested compilation using Xcode 11 and 12beta.
I have not generated XCode project opening the package manifest file Package.swift in Xcode.
The problem came up after importing AHC as Swift package to another iOS Xcode project (supporting macCatalyst platform).

I've been building directly by opening the Package.swift in Xcode using Xcode 12 beta.

I've been building directly by opening the Package.swift in Xcode using Xcode 12 beta.

Fails 100% time for me...

This is when opening async-http-client directly, not when using it as a dependency?

This is when opening async-http-client directly, not when using it as a dependency?

yes

Hmm, let me get hold of a machine that matches your setup and I'll try to replicate it.

Hmm, let me get hold of a machine that matches your setup and I'll try to replicate it.

Thank you, please let me know if/what to check/change on my end.
Not sure how our environments could be different.

Ok, I have validated this definitely occurs. I'm going to reach out to some colleagues to see if I can understand this better. So far as I know the macCatalyst availability is strictly the same as the iOS availability, so I think this is just a bug in Xcode.

Ok, after some chatting with my colleagues this appears to be due to the awkward combination of the following: @available(macCatalyst 13) on the replacement declaration, with @unavailable on the fallback. Strictly macCatalyst version guards are redundant with iOS version guards (the macCatalyst version is assumed from the iOS version). However, the difference is that there is no macCatalyst version before 13. This has some weird effects: we see warnings about redundant version guards in this code, and we get that weird issue where we still have to sort out an else block that has no real fallback.
I propose we change the block to this:
            if #available(macOS 10.15, iOS 13.0, tvOS 13.0, watchOS 6.0, *) {
                sec_protocol_options_set_min_tls_protocol_version(options.securityProtocolOptions, self.minimumTLSVersion.nwTLSProtocolVersion)
            } else {
                #if !targetEnvironment(macCatalyst)
                sec_protocol_options_set_tls_min_version(options.securityProtocolOptions, self.minimumTLSVersion.sslProtocol)
                #else
                preconditionFailure("macCatalyst 13 is the first version of macCatalyst")
                #endif
            }

This code is pretty hideous, but it avoids the concern I have about that block scaling up to being too big. We can do the same in the other block. Want to update to that?

@Lukasa thank you for following up on that,
updated PR as suggested, let me know if you have more comments
feel free to close this PR and submit a patch on your own if its faster that way;
BTW when compiling for Mac Catalyst there is still warning:

Unnecessary check for 'iOS'; enclosing scope ensures guard will always be true

Not sure if it makes sense to try to fix it (for example by putting the availability inside of targetEnvironment condition),
IMO it would make the logic even less clear

BTW when compiling for Mac Catalyst there is still warning:

Unnecessary check for 'iOS'; enclosing scope ensures guard will always be true
Not sure if it makes sense to try to fix it (for example by putting the availability inside of targetEnvironment condition),
IMO it would make the logic even less clear

@swift-server-bot test this please

Just some minor formatting issues to cleanup there.

@swift-server-bot test this please

@swift-server-bot test this please

Aaand now we bump into SR-11560.

There are probably no good routes out of this. Linux doesn't believe macCatalyst exists, so any reference to it will warn, but we have to refer to it in order to get a safe macCatalyst build because it has an explicit unavailable marker for the nonexistent macCatalyst 12-and-earlier version.

There are probably no good routes out of this. Linux doesn't believe macCatalyst exists, so any reference to it will warn, but we have to refer to it in order to get a safe macCatalyst build because it has an explicit unavailable marker for the nonexistent macCatalyst 12-and-earlier version.

how to define macCatalyst without using its name lol
a way to solve this would be to drop support for iOS12.
is it feasible once iOS14 is officially released (which is days)?
that way AHC would support 2 stable iOS versions and Mac Catalyst

Ok, after some digging I've come up with a proposal.
If we wrap the #if targetEnvironment block in #if swift(>=5.3) this should not emit warnings: Swift 5.3 understands that macCatalyst is a real environment. So I think what we're going to do is say that macCatalyst is only supported on Swift 5.3, and wrap this in #if swift(>=5.3).
Does that sound acceptable to you @pokryfka?

@Lukasa
Thank you for following on that.
Amazing weather here and trying to stay away from computer, I am sorry for late response.

So I think what we're going to do is say that macCatalyst is only supported on Swift 5.3,

To be honest supporting only iOS14/Sift5.3 is not ideal but an improvement nevertheless.

If we wrap the #if targetEnvironment block in #if swift(>=5.3) this should not emit warning

I am not sure I understood it correctly, just tried (ugly!):
            if #available(macOS 10.15, iOS 13.0, tvOS 13.0, watchOS 6.0, *) {
                sec_protocol_options_set_min_tls_protocol_version(options.securityProtocolOptions, self.minimumTLSVersion.nwTLSProtocolVersion)
            } else {
                #if swift(>=5.3)
                    #if !targetEnvironment(macCatalyst)
                        sec_protocol_options_set_tls_min_version(options.securityProtocolOptions, self.minimumTLSVersion.sslProtocol)
                    #else
                        preconditionFailure("macCatalyst 13 is the first version of macCatalyst")
                    #endif
                #endif
            }

but it still fails on Linux with Swift 5.2:
docker-compose -f docker/docker-compose.yaml -f docker/docker-compose.1804.52.yaml -p async-http-client-swift52-prb run --rm test

/code/Sources/AsyncHTTPClient/NIOTransportServices/TLSConfiguration.swift:72:44: error: unknown target environment for build configuration 'targetEnvironment'
                    #if !targetEnvironment(macCatalyst)
                                           ^
/code/Sources/AsyncHTTPClient/NIOTransportServices/TLSConfiguration.swift:72:44: note: did you mean 'simulator'?
                    #if !targetEnvironment(macCatalyst)
                                           ^~~~~~~~~~~
                                           simulator

Try #if compiler instead of #if swift

Try #if compiler instead of #if swift

                #if compiler(>=5.3)
                    #if !targetEnvironment(macCatalyst)
                        sec_protocol_options_set_tls_min_version(options.securityProtocolOptions, self.minimumTLSVersion.sslProtocol)
                    #else
                        preconditionFailure("macCatalyst 13 is the first version of macCatalyst")
                    #endif
                #endif

Same, does not compile on Linux and Swift5.2 tested using the docker compose file in the repo:
docker-compose -f docker/docker-compose.yaml -f docker/docker-compose.1804.52.yaml -p async-http-client-swift52-prb run --rm test

@swift-server-bot test this please

@swift-server-bot test this please

Try #if compiler instead of #if swift

                #if compiler(>=5.3)
                    #if !targetEnvironment(macCatalyst)
                        sec_protocol_options_set_tls_min_version(options.securityProtocolOptions, self.minimumTLSVersion.sslProtocol)
                    #else
                        preconditionFailure("macCatalyst 13 is the first version of macCatalyst")
                    #endif
                #endif

Same, does not compile on Linux and Swift5.2 tested using the docker compose file in the repo:
docker-compose -f docker/docker-compose.yaml -f docker/docker-compose.1804.52.yaml -p async-http-client-swift52-prb run --rm test

@weissi actually, I did not push the change back then but I did try #if compiler(>=5.3) locally,
re-tested and pushed the change now, failing with:
/code/Sources/AsyncHTTPClient/NIOTransportServices/TLSConfiguration.swift:88:48: note: did you mean 'simulator'?
                        #if !targetEnvironment(macCatalyst)

@swift-server-bot test this please


Mount points are incorrectly written to console.

When using local start-api, there's something in the template that will cause it to display the wrong functions to mount for the endpoints.  It will display the same mount point (randomly chosen, it seems) for all paths.
e.g.
Mounting index.deactivateBaz (nodejs6.10) at http://<IP_ADDRESS>:3000/foo/bar [GET]
Mounting index.deactivateBaz (nodejs6.10) at http://<IP_ADDRESS>:3000/foo/bar/{barId}/baz [POST]
Mounting index.deactivateBaz (nodejs6.10) at http://<IP_ADDRESS>:3000/foo/baz [GET]
Mounting index.deactivateBaz (nodejs6.10) at http://<IP_ADDRESS>:3000/foo/fizz [POST]
Mounting index.deactivateBaz (nodejs6.10) at http://<IP_ADDRESS>:3000/foo/baz/{bazId} [DELETE]
Mounting static files from public at /

I'm using an inline swagger definition in my template.  In the above example each method has a unique method.

The same occurs with java 8

Can you try the latest release - https://github.com/awslabs/aws-sam-cli/releases/tag/v0.3.0? I believe this is fixed. Feel free to re-open Issue if not.


Update MD file on new branch 2017-11-10_16-42-26

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/content1.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Which license? MIT?

Hello,
It seems a good base to start messing with PB and SK :) Thank you @jkdoshi !
Which license is it? MIT?

Yes, MIT. I've now added LICENCE.md to the repo.

Thanks @jkdoshi
Have a great week-end! (7pm here)


Aruha 759 per event authz

ARUHA 759
This PR adds an API for per-resource authorization. It also improves the repository by providing a README, a list of MAINTAINERS, and a zappr configuration

I think in order to be able to call your plugin from Nakadi you have to implement existing plugin api, which I do not see here.

Discussed this offline with @adyach. Plugins are implemented in separate repos, and a dummy is in the Nakadi repo.

👍

👍


Instance store AMI support

This PR adds support for creating instance store AMIs (coreos/bugs#177).
oem/ami/import.sh has a lot going on, but ultimately it:

Builds lots of state
Downloads an image (probably)
Produces an uncompressed, authenticated coreos_production_ami_image.bin file
Uses ec2-import-volume to turn the image file into an EBS volume
Uses ec2-create-snapshot to turn that EBS volume into an EBS snapshot
Registers an HVM AMI based on that snapshot
Registers a PV AMI based on that snapshot

oem/ami/import-instance-store.sh is based on oem/ami/import.sh since it shares much of this process. This new script:

Builds lots of state
Downloads an image (probably)
Produces an uncompressed, authenticated coreos_production_ami_image.bin file
Uses ec2-bundle-image to turn the image into a bunch of smaller files and a corresponding manifest
Uses ec2-upload-bundle to copy the bundle files to S3
Registers an HVM AMI based on that bundle
Registers a PV AMI based on that bundle

I think it makes sense to produce instance store AMIs alongside the EBS AMIs, in which case the ec2-bundle-image + ec2-upload-bundle steps should be merged into oem/ami/import.sh such that it produces 4 AMIs instead of 2. This PR keeps them separate so the instance store AMI generation process can be discussed and executed in isolation.
coreos_production_ami_image.bin appears to work as an instance store AMI without modification. My setup process was:

Launch an Amazon Linux instance.
Copy scripts
Copy EC2 X.509 certificate + key, since instance store AMI creation additionally requires these credentials

Then, to create the AMIs:
$ export AWS_ACCESS_KEY_ID=AKI…
$ export AWS_SECRET_ACCESS_KEY=…
$ export AWS_ACCESS_KEY=$AWS_ACCESS_KEY_ID
$ export AWS_SECRET_KEY=$AWS_SECRET_ACCESS_KEY
$ VERSION=1068.8.0
$ oem/ami/import-instance-store.sh -V $VERSION -g stable -u http://stable.release.core-os.net/amd64-usr/$VERSION/coreos_production_ami_image.bin.bz2 -B totally-not-official-ami -c /home/ec2-user/secrets/cert.pem -k /home/ec2-user/secrets/pk.pem -a <123456789012> -X
Building AMI in zone us-east-1e
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  255M  100  255M    0     0   122M      0  0:00:02  0:00:02 --:--:--  122M
Bunzipping....
Bundling image file...
…
Manifest uploaded to: totally-not-official-ami/CoreOS-stable-1068.8.0/CoreOS-stable-1068.8.0.manifest.xml
Bundle upload completed.
Registering hvm AMI
Registering paravirtual AMI
CoreOS stable 1068.8.0
architecture: x86_64
region:       us-east-1 (us-east-1e)
aki id:       aki-919dcaf8
name:         CoreOS-stable-1068.8.0
description:  CoreOS stable 1068.8.0
PV AMI id:    ami-2881143f
HVM AMI id:   ami-f58613e2

Full output is recorded for posterity in this gist.
The AMIs ami-2881143f and ami-f58613e2 are public for the purposes of this PR. (In other words, don't use them in production because I will delete them at some point.) Both AMIs appear to work:
$ aws ec2 run-instances --image-id ami-2881143f --key-name … --subnet-id … --security-group-ids … --instance-type m3.large
$ aws ec2 run-instances --image-id ami-f58613e2 --key-name … --subnet-id … --security-group-ids … --instance-type m3.large

My goal is to get official CoreOS instance store AMIs, created and published by the usual official process. How do we get there from here?

This is pretty awesome. Thank you! We probably aren't going to have time to review this until next week, so if you don't see any activity for a while, that's why. We aren't ignoring you ;)

Sounds great, thanks!
I've also been tinkering with getting the CoreOS AMI build process working in a Docker container which could run anywhere, i.e. even outside EC2. Is that something you'd want to see in a different PR?
Relatedly, how attached are you to these shell scripts? 😃

@willglynn soon we will be moving AMI code into https://github.com/coreos/mantle.

@mischief Cool! That answers my question. I'll stop at tinkering 👍

I discussed with (pestered) @mischief on IRC. I understand that the CoreOS distribution process is heading towards a pure-Go solution, so I set out to ensure that instance store AMIs could be a part of this.
I wrote a pure-Go aws_bundle package capable of replacing ec2-bundle-image. It produced its first bootable AMI this morning. With some glue from that to the Go AWS SDK, I can get instance store AMI bundling, uploading, and registration all together into a single tool with no external dependencies, and – I hope – from there into mantle.

I wrote some glue. There's now a pure-Go ec2-bundle-and-upload-image CLI tool living on top of my aws_bundle package.
One can say ec2-bundle-and-upload-image -image coreos_production_ami_image.bin.bz2 -s3-bucket whatevs with literally no other parameters. It'll write a machine bundle to s3://whatevs and return the manifest location. Then, pass that into aws ec2 register-image --image-location and you'll have an instance store AMI.
(Oh, and in the CoreOS case, you'd pass that location into register-image a second time with --virtualization-type=hvm to get the second instance store AMI.)
Options I see from here, which may not be an exhaustive list:

I can leave this PR as-is
I can update this PR to use my tool
I can close this PR, wait until EBS AMI generation lands in mantle (coreos/mantle#121?), then open a PR over there to add instance store AMI generation leveraging aws_bundle
Some combination of these things

Please let me know how you'd like to proceed.

At this point we've completely switched to mantle for AMI creation/release. The relevant code is called from the cmd/plume/{release,prerelease}.go files.
I'll close this PR as it's stale.
Instance Store backed AMIs in mantle does sound like a good feature to have.


Bugs

Describe your bug here.
PsychEngine_2024-07-16_15'26'12.txt
Command Prompt/Terminal logs (if existing)
objects/Note.hx (line 464)
states/PlayState.hx (line 1758)
flixel/group/FlxGroup.hx (line 787)
states/PlayState.hx (line 1752)
flixel/FlxState.hx (line 222)
flixel/FlxGame.hx (line 752)
flixel/FlxGame.hx (line 682)
flixel/FlxGame.hx (line 556)
openfl/events/EventDispatcher.hx (line 444)
openfl/display/DisplayObject.hx (line 1400)

Uncaught Error: Null Object Reference
Please report this error to the GitHub page: https://github.com/ShadowMario/FNF-PsychEngine

> Crash Handler written by: sqirra-rng

Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
When I tried to edit the chart and open it, this happened.

are you using any custom noteskins


new data pull in & validate

Edited the data folder so that make data will pull in the raw ds005 the new func ds005, and the mni templates folder.
make validate should validate all of that with the new mni_hashlist i put in.
Also renamed mni_icbm152... folder itself to 'templates' and the mni_icbm152_t1... file we'll be using into 'mni_standard.nii' for convenience and clarity. mni_standard.nii is the one matthew mentioned as most useful for displaying the patterns on
This will prbly screw up travis ci somewhere but we'll see

yeah...the coverage dropped like crazy, not sure how to fix... can you play around with the coverage in makefile of project directory and/or add coverage of makefile of data directory and see how travis responds? If nothing works raise an issue and ask jarrod/ross

Are you generating a hash list every time you run data.py?
You should generate the hash list yourself and everybody should just compare their hash to the txt file you uploaded.
I don't see why you need the make_hash_list function.

The make_hash_list function I just left in, in case I wanted to make another hash list, so it's not actually being called. I git added a prior hash list that I had generated before to compare to, yeah. I'll mess with it around some more and see with the travis ci.

But it seems like that's messing up travis. I had to put the generate hash script in the tools folder to avoid travis problems, if you recall.

Commented that out just now, should improve at least a little now

What is the new_hashList.txt, what data is that for?

new_hashList.txt is the hashlist for ds005 that includes the mni_func data, so it actually makes the original hashlist redundant for now. but should keep the old hashlist in until we finalize things more

and mni_hashlist is for the templates?
Also, what does the templates do? I'm kinda confused.

Yup, mni_hashlist is for the templates.
Templates is just the folder:
http://nipy.bic.berkeley.edu/rcsds/mni_icbm152_nlin_asym_09c_2mm/
I renamed mni_icbm152_nlin_asym_09c_2mm to templates for clarity and convenience so we don't have to bother with that complicated name.
That's also why I renamed mni_icbm152_t1_tal_nlin_asym_09c_2mm.nii inside that folder to mni_standard.nii. This nii file is the standard brain template we should use to display functional patterns on, according to the Readme updated by Matthew.
Also we'll probably end up using the mask template in there, but haven't renamed that yet.
As for the travis ci, i think combining all the hashlists and doing only one check_hashes might help with the remaining -2.4%

Travis won't cover the main function, last time, we also ignored the non-coverage of the last few lines. So I suppose if we combine everything into 1 check hashes, it's going to help, but it might also be confusing to people reading our codes. I'm not so sure about if we should combine all the hash lists...

To avoid coverage on data.py entirely:

You can let coverage check only the functions inside by creating a new python script with only functions
Then go to the main project directory and change the make coverage line:
--cover-package=data/thenewfunction.py

How did this go?

Is there any other reason not to combine the hashlists? I'm not sure why it'd be confusing since the idea of the is to check if all the data pulled in matches our hashlist, and it shouldn't matter if there's three hashlists or one?
I combined mni_hash.txt and newhashlist.txt into total_hash.txt, so it checks for everything in ds005 and the mni templates folders. It looks like it'll pass the travis so is it okay if we go with this?
If so I'll remove all the extraneous hashlists and code and then merge the pull request

I think the main thing is to make sure the hashes are checked in the right order as they are generated, did you try downloading the data and validating it? if it works then this should be fine

Wait are you sure they need to be checked in a certain order? I did the make validate and that was fine.

well, i assumed the for loop in check_hashes requires a certain order, if download and validate work fine then we can go ahead and merge

Added a readme

lol next time probably should wait for travis


Question about hood

Hello valter, your app is so great I’ve bought you a coffee ;) and thanks for your support in last two questions ;)
I’m trying to provide edge remote support (I know isn’t in your roadmap); I think I can achieve with your work in ji2, but if you guide me how can map de buttons/hood with the buttons in Karoo this wil be very helpful
I know the Karoo SDK is very limited and it’s not possible to send key commands and this will be possible in ride app, but if you can provide me where is done or some kind of guide howto do in ride app, it’ll be enough and very useful for me.
I give you my email<EMAIL_ADDRESS>if you want to write there and no dirt these comments. ;) thanks a lot

Or if you want I can write you to your donation email ;) regards

Thanks! :)
The buttons in Karoo are actually simulating Keyboard Key Events, I have a mapping in file https://github.com/valterc/ki2/blob/main/app/src/main/java/com/valterc/ki2/data/input/KarooKey.java
    /**
     * Left top key.
     */
    LEFT(KeyEvent.KEYCODE_NAVIGATE_PREVIOUS),

    /**
     * Right top key.
     */
    RIGHT(KeyEvent.KEYCODE_NAVIGATE_NEXT),

    /**
     * Right bottom key.
     */
    CONFIRM(KeyEvent.KEYCODE_NAVIGATE_IN),

    /**
     * Left bottom key.
     */
    BACK(KeyEvent.KEYCODE_BACK),

So you need to send these android physical keys to the Ride app. You can use some input systems like the InputManager (this is what I do in Ki2) from Android or grab the activity and use dispatchKeyEvent, etc.
These keys can also do several actions, depends if it's single press, double press or hold.

Thanks for your support. I’ll try to follow your examples ;)
Regards

Thanks! :)
The buttons in Karoo are actually simulating Keyboard Key Events, I have a
mapping in file
https://github.com/valterc/ki2/blob/main/app/src/main/java/com/valterc/ki2/data/input/KarooKey.java
/**     * Left top key.     */
LEFT(KeyEvent.KEYCODE_NAVIGATE_PREVIOUS),

/**     * Right top key.     */
RIGHT(KeyEvent.KEYCODE_NAVIGATE_NEXT),

/**     * Right bottom key.     */
CONFIRM(KeyEvent.KEYCODE_NAVIGATE_IN),

/**     * Left bottom key.     */
BACK(KeyEvent.KEYCODE_BACK),

So you need to send these android physical keys to the Ride app. You can
use some input systems like the InputManager (this is what I do in Ki2
https://github.com/valterc/ki2/blob/main/app/src/main/java/com/valterc/ki2/input/InputAdapter.java)
from Android or grab the activity and use dispatchKeyEvent, etc.
These keys can also do several actions, depends if it's single press,
double press or hold.
—
Reply to this email directly, view it on GitHub
https://github.com/valterc/ki2/issues/132#issuecomment-1455050707, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AN5QCYCCZ5Z2LRGSVDFUR5TW2RTMBANCNFSM6AAAAAAVQBAHDU
.
You are receiving this because you authored the thread.Message ID:
@.***>


getting started

Hi I'm quite new to coding and would appreciate some basic help.
I've downloaded all the files and placed them in my 'python folder of "installed packages"
What do I need to do next to use it?
thanks

Thanks got it working
-but now it tells me I can't save the file

got it

:+1:


Action support of agv operation and maintenance

The master control system should be able to control the shutdown or restart of the agv,so it may need "shutdown" and "restart" two  instantActions
In some special cases, the status of the agv is abnormal,such as  losting location,or a module exception,so maybe we need to reset agv,how about add a standard instantAction ,just like "reset",get it to self-check and go back to a working state as much as possible,it may like this issue:https://github.com/VDA5050/VDA5050/issues/296

-> I support this request to standardize this actionTypes, until then AGV supplier can define their own customized actions to support this, which leads to the requirement in master control system to support the configuration of customized instant actions.


Specify that VM-level commands apply to instances

Specify that commands to get "VM-level" (not scale-set level) model/instance views, target a specific VM instance, not the whole scale set.

@alexvy86 : Thanks for your contribution! The author, @gatneil, has been notified to review your proposed change.

@cynthn @jpconnock - Can you follow up on this?

@zr-msft adding Zach, who is taking over VMSS doc and @rajsqr who is the new PM.

@alexvy86 Thank you for the contribution!
We typically refer to "VMs" as "VM instances" in the context of scale sets.
For example:

... To query the model view for a particular VM in a scale set, you can use:

Would be:

... To query the model view for a particular VM instance in a scale set, you can use:

Do you mind amending your PR with the above updates? Once thats done, we can merge and publish this update.

@alexvy86 : Thanks for your contribution! The author, @gatneil, has been notified to review your proposed change.

@zr-msft I made the changes... it feels kind of weird to talk about the "VM instance instance view"  or the "instance view of the VM instance" though. Would it make sense to talk about "runtime" views instead of "instance" views? Or maybe "current" views?

@alexvy86 Thank you for the quick follow up and updates to the PR. I agree there are a couple of examples where we could reword something for clarity.
We can merge this for now and I'll file a follow up PR shortly after to clean up the terminology.
#sign-off

@zr-msft: I'm sorry - only the author of this article, @gatneil, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

#sign-off

@rajsqr: I'm sorry - only the author of this article, @gatneil, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

#sign-off

also, please modify the author to be @rajsqr, since I no longer own this article; Raj is the right person to own it :)


Issue 1933 - Cutadapt JSON file

Test data (sample JSON file from current version of cutadapt), see #1933

Thank you!

For the reference, it's for this issue: https://github.com/ewels/MultiQC/issues/1933


Move release process docs to handbook

Moving legacy handbook to handbook.mattermost.com is tracked as part of https://docs.google.com/spreadsheets/d/1Yz93lett6y-vPqyxqBFZhL_43xBQ2eYRUwcVyEat-lo/edit#gid=0
Accompanying handbook PR: https://github.com/mattermost/mattermost-handbook/pull/159

Ready to review, but adding Do Not Merge label until the accompanying handbook PR has been merged.

@amyblais great catch :+1:


Additional instructions

It seems that aws cli is using instance metadata the gh executor is running on and causing issues with auth against aws backend. Adding this variable to env solves the issue.

Thank you @mickutz
Could you please at as a TIP? Like:

TIP: For EC2 instances make you add the environment  variable ... in order to ...

Thank you @mickutz
Just to be on the safe side - do you mean running this action in GitHub Actions with a self-hosted EC2 runner?
According to the TIP, it sounds like this action doesn't work in GitHub Actions without those env vars. Am missing something? 🤔

Hi @unfor19 .
Sorry for the alte reply. No, I had this issue on github's own runners.

@mickutz Then I'm not sure about this change at all, may you please share what you did and how it solved your problem?

@mickutz I'm closing this issue as EC2 issues are not quite related to the action itself.
You're more than welcome to share logs/details of your issue here and I'll do my best to assist


Multi-GPU training?

Hi, cool work!
I was wondering if the toolkit supported multi-GPU training as-is, and, if not, if there are any plans to support it.
Thanks!

As of last week, looks like AllenNLP now has support for distributed training on multiple GPUs. You'll have to install the package from the AllenNLP repo (see the README). I don't have much time to look into it to explain how to set it up, but you can refer here for info on progress with the new multi GPU features and here for the new changes.

Sounds good, I'll take a look!


Fix deprecation warning

Ruby 2.3?

Yep

Seems like a good change.  I wanted to reproduce the warning, but somehow I don't see it with 2.3.0  How do you trigger this warning?

Add to ~/Rakefile:
Rake::TestTask.new(:test) do |t|
[...]
  t.warning = true
end

I've enabled warnings for assert_value builds too.  Any idea how t.warning = true got into your Rakefile?  Is this a new standard thing that Rails does, or your/company thing?

Don't remember how I came to know that flag, but it happened in the past 3 days :)
http://rake.rubyforge.org/classes/Rake/TestTask.html :
[RW] 	warning 	Request that the tests be run with the warning flag set. E.g. warning=true implies "ruby -w" used to run the tests.

Released in 1.5.3, thanks.


Solved issue 1007

Related Issue
Fixes:  #1007
Description
The content in the hero section are currently not aligned properly. This misalignment affects the overall visual appeal and user experience of the page.

Type of PR

[x] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
Before

After

Checklist:

[x] I have made this change from my own.
[ ] I have taken help from some online resources.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers and screenshots after making the changes.

Great contribution to GSSOC'24! 🎉


fix #5079 SQLServer socketTimeout support

fix #5079, in SQLServer,  loginTimeout in second, socketTimeout in millisecond

also, do some fix about #5096 modify the Postgres timeout values unit from milliseconds to seconds,
and fix one wrong field assignment

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

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

@Wincher  please fix the ci first.

@Wincher please fix the ci first.

@kimmking  Solved, please approve the ci job.


feat(trace-otlp-grpc): configure security with env vars

Which problem is this PR solving?
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Partially Fixes https://github.com/open-telemetry/opentelemetry-js/issues/2706 (issue)
Currently the transport security for the gRPC exporter can be set either programmatically or the default insecure transport is used. This PR adds insecure environment variables and certificate file environment variables that related to security configuration.
Note: this PR is not ready to be merged yet. Need to get feedback from others on a few items first. See comments.
Short description of the changes

Added "insecure" and "certificate file" configuration env vars.
Added configureSecurity function that sets up the transport security configuration.
Updated default url from localhost:4317 to http://localhost:4317 as discussed during the SIG.

Type of change
Please delete options that are not relevant.

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

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Unit Tests

Checklist:

[x] Followed the style guidelines of this project
[x] Unit tests have been added
[ ] Documentation has been updated

TODO:

[x] Clarify how security should be configured in certain cases (scheme in endpoint, default security)
[x] Clarify using OTEL_EXPORTER_OTLP_SPAN_INSECURE as part of configureSecurity function.

This PR doesn't break anything when it comes to setting up transport security.
I would like some feedback on the following items:

Spec says that the default "insecure" should be "false" which means a secure transport channel. The current default implementation (before this pr) is "insecure". Should we leave this as it or change it to match the spec that it should be secure as the default (which means it'll be a breaking change)?
Spec says that a scheme of https indicates a secure connection and takes precedence over the "insecure" config settings. The current implementation (before this pr) doesn't take the scheme in the endpoint into consideration at all. Should we add logic that takes scheme in endpoint into consideration in order to determine security. Here are some current use cases with the scheme endpoint of the current implementation (before this pr and continued with this pr):

A. using all defaults - no endpoint specified, no channel credentials specified => returns insecure channel
Note: spec says we should create secure channel but current implementation creates insecure

B. endpoint = localhost:4317, no channel credentials specified => returns insecure channel
Note: follows spec (no scheme means insecure channel)

C. endpoint = http://localhost:4317, no channel credentials specified => returns insecure channel
Note: follows spec (http scheme means insecure channel)

D. endpoint = https://localhost:4317, no channel credentials specified => returns insecure channel
Note: spec says this should be a secure channel but current implementation creates insecure

E. endpoint = grpc://localhost:4317, no channel credentials specified => returns insecure channel
Note: follows spec (http scheme means insecure channel)

F. endpoint = grpcs://localhost:4317, no channel credentials specified => returns insecure channel
Note: spec says this should be a secure channel but current implementation creates insecure

G. endpoint = https://localhost:4317, channel credentials (either secure or insecure) specified => return
same `channelCredentials`
Note: there's no details from the spec on what to do in this case but I think that if a user specifically
created channel credentials programmatically (either insecure or secure) that we should use those
exact credentials no matter what scheme the endpoint contains. Also this is what is happening with
the current implementation (before this pr and continued with this pr) - we use the security credentials
set by the user.

Spec mentions that OTEL_EXPORTER_OTLP_SPAN_INSECURE is obsolete but they are still supported because of a stable release of the spec. Should we read this OTEL_EXPORTER_OTLP_SPAN_INSECURE env var in my configureSecurity function?

Discussed in SIG yesterday and spent a little more time reading the spec today. The spec states "The endpoint SHOULD accept any form allowed by the underlying gRPC client implementation" and also only specifies https scheme as overriding the secure config. Given that, I think we should respect the insecure config in all cases (including secure by default) except when the scheme is https where the spec specifically says we should be secure. The only thing I'm not sure about is default behavior if nothing is configured because a secure connection to localhost is likely to fail certificate validation. I have opened https://github.com/open-telemetry/opentelemetry-specification/issues/2420 for this question.

@svetlanabrennan what's the current status here?

@svetlanabrennan what's the current status here?

I just need confirmations on these use cases before I push up my changes to this pr:

if user wants to use all defaults, return secure channel
anytime user provides their own credentials, use those same credentials (no matter the scheme or env insecure settings)
if user sets https scheme return secure channel (ignoring insecure env settings)
if user sets http scheme and no other items (like providing credentials or env insecure settings) return insecure channel
if user sets no scheme and no other items (like providing credentials or env insecure settings) return secure channel
if user sets http scheme and env insecure = false, return secure channel
if user sets http scheme and env insecure = true, return insecure channel
if user sets no scheme and env insecure = false, return secure channel
if user sets no scheme and env insecure = true, return insecure channel

Do you (and anyone else) agree with this configuration?

Thank you for that feedback @dyladan. I'll wait for clarification on use case 4 and 6.
Note: this pr is also held up by the two lerna configurations issue.

if user wants to use all defaults, return secure channel

According to @tigrannajaryan open-telemetry/opentelemetry-specification#2420 it should be insecure to localhost. Tigran agrees spec should be clarified.

Tigran has clarified that the intention of the spec was for the default to be an insecure localhost connection.

if user sets http scheme and no other items (like providing credentials or env insecure settings) return insecure channel

This is not as clear. I'll ask Tigran. The spec says insecure is false by default, but http implies insecure.

Tigran's comment here clarifies that endpoint with http scheme overrides insecure setting. Insecure setting is only used if no scheme is provided.

if user sets http scheme and env insecure = false, return secure channel

Yes. I think this will also be the answer for "user sets http scheme and no other items" but we'll wait for Tigran.

The same clarification above also applies to this. The insecure config is only used if a scheme is not provided.

The same clarification above also applies to this. The insecure config is only used if a scheme is not provided.

Perfect. Thanks for the clarification.

Just to be clear: it was just my opinion, I may be wrong :-)
It would be great to submit a spec PR that fixes this and get it merged to be sure.

A few questions:

Should we accept/allow grpc(s) scheme? I recall chatting about this during our SIG meeting a few weeks ago - that we should just remove it. Am I remembering that correctly?

If a user provides a key but that not a chain, grpc will throw an error such as Private key must be given with accompanying certificate chain and if a chain is provided but not a key, grpc will throw a similar error.  I have it configured to catch that error, pass it to diag.warn and then create a secure channel using the default root certificates as shown here.  I just want to confirm if that's what we should in that case where key or chain isn't provided or should we do something else in that case?

A few questions:

Should we accept/allow grpc(s) scheme? I recall chatting about this during our SIG meeting a few weeks ago - that we should just remove it. Am I remembering that correctly?

Spec states we should accept whatever the underlying implementation accepts. If we are passed a string, we should pass it directly to the underlying implementation. If it fails then fine. If it works then fine.

If a user provides a key but that not a chain, grpc will throw an error such as Private key must be given with accompanying certificate chain and if a chain is provided but not a key, grpc will throw a similar error.  I have it configured to catch that error, pass it to diag.warn and then create a secure channel using the default root certificates as shown here.  I just want to confirm if that's what we should in that case where key or chain isn't provided or should we do something else in that case?

I think we should allow the failure to be thrown to the user. This isn't a failure which will happen only sometimes or late during runtime, but at setup so should fail early and in a way that makes it obvious what happened. If we log to diag, many users won't see that and changing the behavior may be confusing to them.

Ready for review

Sorry for the delay on review here. i've got this on my list for the morning


How can I send custom commands? (Logitech G920 Steering Wheel)

Hi, I've been using this repository to try and translate Xbox inputs from a Logitech steering wheel to work on Nintendo Switch as a wired controller, and so far I've managed to print out the inputs using your example in the readme. The one problem I'm having is that the steering wheel I'm using has autocenter enabled by default, meaning the wheel will always try to move towards the center position. This makes turning the wheel really really hard in gameplay. I've looked into some open source programs that support this wheel and a couple of them seem to send the command 0xf5, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 to disable the autocenter. I tried this with your code and it didn't seem to do anything. Is there any special format I need to use to get custom Xinput/Xbox commands to work in this library?
Here's how I've been sending commands to the wheel:
static const uint8_t data[] = { 0xf5, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 };

tuh_xinput_send_report(dev_addr, instance, data, sizeof(data));
while (usbh_edpt_busy(dev_addr, xid_itf->ep_out))
{
  tuh_task();
}

That looks about right to me. Perhaps it's not right for that wheel?
You'd need to use Wireshark or similar to monitor USB traffic assuming you can trigger in on a PC to find the command.

Yeah, I monitored the USB traffic on my Raspberry Pi and later found out the wheel is actually sent a command to remount as an HID device, and that device is used for force feedback. The command is likely unrelated to the Xinput mode and instead the HID mode, so I'll have to figure out the correct way to send the command through HID.