Quick start with EM stuck at 87%; can't complete write-netplan step

Following the guide for Equinix Metal, the workflow is stuck at 87% and it seems to have issues with write-netplan step
+----------------------+--------------------------------------+
| FIELD NAME           | VALUES                               |
+----------------------+--------------------------------------+
| Workflow ID          | e193da91-f82a-11ec-986a-0242ac120003 |
| Workflow Progress    | 87%                                  |
| Current Task         | os-installation                      |
| Current Action       | disable-apparmor                     |
| Current Worker       | 0eba0bf8-3772-4b4a-ab9f-6ebe93b90a94 |
| Current Action State | STATE_SUCCESS                        |
+----------------------+--------------------------------------+

Expected Behaviour
The workflow should complete at 100%
Current Behaviour
+----------------------+--------------------------------------+
| FIELD NAME           | VALUES                               |
+----------------------+--------------------------------------+
| Workflow ID          | e193da91-f82a-11ec-986a-0242ac120003 |
| Workflow Progress    | 87%                                  |
| Current Task         | os-installation                      |
| Current Action       | disable-apparmor                     |
| Current Worker       | 0eba0bf8-3772-4b4a-ab9f-6ebe93b90a94 |
| Current Action State | STATE_SUCCESS                        |
+----------------------+--------------------------------------+

Here's relevant logs (I think)
tink-server_1                    | {"level":"info","ts":1656563265.5266938,"caller":"server/dbserver_workflow.go:234","msg":"done getting a workflow context","service":"github.com/tinkerbell/tink","workflowID":"e193da91-f82a-11ec-986a-0242ac120003","currentWorker":"0eba0bf8-3772-4b4a-ab9f-6ebe93b90a94","currentTask":"os-installation","currentAction":"disable-apparmor","currentActionIndex":"6","currentActionState":"STATE_SUCCESS","totalNumberOfActions":8}
tink-server_1                    | {"level":"info","ts":1656563266.8126962,"caller":"server/dbserver_worker_workflow.go:82","msg":"received action status: STATE_RUNNING","service":"github.com/tinkerbell/tink","actionName":"write-netplan","workflowID":"e193da91-f82a-11ec-986a-0242ac120003","taskName":"os-installation"}
boots_1                          | {"level":"info","ts":1656563266.8126342,"caller":"syslog/receiver.go:107","msg":"host=<IP_ADDRESS> facility=daemon severity=ERR app-name=eafa7d318d9c procid=1198 msg=\"{\\\"level\\\":\\\"info\\\",\\\"ts\\\":1656563265.1012092,\\\"caller\\\":\\\"worker/worker.go:442\\\",\\\"msg\\\":\\\"reporting Action Status\\\",\\\"service\\\":\\\"github.com/tinkerbell/tink\\\",\\\"workerID\\\":\\\"0eba0bf8-3772-4b4a-ab9f-6ebe93b90a94\\\",\\\"workflowID\\\":\\\"e193da91-f82a-11ec-986a-0242ac120003\\\",\\\"actionName\\\":\\\"write-netplan\\\",\\\"taskName\\\":\\\"os-installation\\\",\\\"workflowID\\\":\\\"e193da91-f82a-11ec-986a-0242ac120003\\\",\\\"workerID\\\":\\\"0eba0bf8-3772-4b4a-ab9f-6ebe93b90a94\\\",\\\"actionName\\\":\\\"write-netplan\\\",\\\"taskName\\\":\\\"os-installation\\\",\\\"status\\\":\\\"STATE_RUNNING\\\"}\\n\"","service":"github.com/tinkerbell/boots","pkg":"syslog"}
boots_1                          | {"level":"info","ts":1656563266.8141456,"caller":"syslog/receiver.go:107","msg":"host=<IP_ADDRESS> facility=daemon severity=ERR app-name=eafa7d318d9c procid=1198 msg=\"{\\\"level\\\":\\\"error\\\",\\\"ts\\\":1656563265.1027963,\\\"caller\\\":\\\"worker/worker.go:445\\\",\\\"msg\\\":\\\"failed to report action status: rpc error: code = FailedPrecondition desc = invalid action index for workflow\\\",\\\"service\\\":\\\"github.com/tinkerbell/tink\\\",\\\"workerID\\\":\\\"0eba0bf8-3772-4b4a-ab9f-6ebe93b90a94\\\",\\\"workflowID\\\":\\\"e193da91-f82a-11ec-986a-0242ac120003\\\",\\\"actionName\\\":\\\"write-netplan\\\",\\\"taskName\\\":\\\"os-installation\\\",\\\"workflowID\\\":\\\"e193da91-f82a-11ec-986a-0242ac120003\\\",\\\"workerID\\\":\\\"0eba0bf8-3772-4b4a-ab9f-6ebe93b90a94\\\",\\\"actionName\\\":\\\"write-netplan\\\",\\\"taskName\\\":\\\"os-installation\\\",\\\"status\\\":\\\"STATE_RUNNING\\\",\\\"error\\\":\\\"failed to report action status: rpc error: code = FailedPrecondition desc = invalid action index for workflow\\\",\\\"errorVerbose\\\":\\\"rpc error: code = FailedPrecondition desc = invalid action index for workflow\\\\nfailed to report action status\\\\ngithub.com/tinkerbell/tink/cmd/tink-worker/worker.(*Worker).reportActionStatus\\\\n\\\\t/home/runner/work/tink/tink/cmd/tink-worker/worker/worker.go:445\\\\ngithub.com/tin\"","service":"github.com/tinkerbell/boots","pkg":"syslog"}

Possible Solution

Steps to Reproduce (for bugs)

Follow the quick start guide for Equinix Metal

Context

Your Environment

Operating System and version (e.g. Linux, Windows, MacOS):
MacoS
How are you running Tinkerbell? Using Vagrant & VirtualBox, Vagrant & Libvirt, on Packet using Terraform, or give details:
Metal with terraform
Link to your project or a code example to reproduce issue:

Hey @jpablo-eqx, thanks for reporting this. I believe that this PR: https://github.com/tinkerbell/tink/pull/632 should fix the issue.


Fixed install script that was not working for RHEL7 host

Looks like a recent change to the install script in this PR: #23124 caused a regression that prevented docker from getting installed on RHEL7
This PR should fix this issue #23787
Signed-off-by: Ken Cochrane<EMAIL_ADDRESS>/cc @thaJeztah

LGTM (IANAM)

lgtm

LGTM

Can this be fixed for docker test?
https://test.docker.com/


Importer: import audiobooks

An Audiobook can be of Document Type Book. Audiobook are added to existing Book record as additional e-item with description 'Audiobook'. If there is no record, a Book record is created with an e-item with description 'Audiobook'. ISBNs identified as '(electronic audio bk.)' (020 subfield q) should refer to Material 'Audiobook'. The other ISBNs should be treated as usual. Important: <leader> field should include value im to identify as audiobook
Display Audiobook  in the Formats in the facets (based on the description in the e-items): e-book/ebook (to be standardized - please bulk update to 'e-book') -> Facet 'E-book'; Audiobook -> Facet 'Audiobook';  in the Filter by Format.
For Deletions, distinguish Ebook/Audiobook with the LDR field (am (Book)/im (Audiobook)) to remove only the corresponding e-item. The rest of deletion process would as usual.

I tested with 2 files and got the following results:

'videos' are well imported as such: example: https://sandbox-cds-ils.web.cern.ch/literature/08j5p-vsf95 Works!
'audiobook' that matched with an 'e-book': https://sandbox-cds-ils.web.cern.ch/backoffice/documents/y32s1-qzf62 it looks the audiobook item replaced the e-book (it should have been added - there should be 2 e-items (the 'e-book and the 'audiobook').
'audiobook' (without already existing record - new record): example: https://sandbox-cds-ils.web.cern.ch/backoffice/documents/e4k6y-c1235 Works!

You can ignore the following fields in the matching rules: {'758__4', '758__a', '758__i', '758__1'} in the importer.

Please let us know when point 2 in the above comment is solved, and we will also test if the importer is behaving as it should for deletions (should delete the corresponding e-item (either e-book or audiobook) if both are present).

Perfect, it is working with the importer for audiobooks! it has added the audiobook without deleting the e-book.

Ok!


chore(deps): install missing @types/js-yaml

Signed-off-by: Lukas Mertens<EMAIL_ADDRESS>

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#200  👈
#199
#198
#177
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @lukas-mertens and the rest of your teammates on  Graphite

Merge activity

Oct 14, 9:24 AM EDT: A user merged this pull request with Graphite.


Fixes for Heroku example

Current coverage is 95.07%

Merging #282 into master will not affect coverage as of 84cbf0b

@@            master    #282   diff @@
======================================
  Files          179     179
  Stmts         2516    2516
  Branches       307     307
  Methods          0       0
======================================
  Hit           2392    2392
  Partial          0       0
  Missed         124     124

Review entire Coverage Diff as of 84cbf0b

Powered by Codecov. Updated on successful CI builds.

Hi @jkutner, thanks for contributing. I'll add review comments to pull request.

I verified that your changes fix the heroku deployment, thank you. One additional thing I noticed is that in the README.md, that the copy command
$ cp -R finatra-hello-world-heroku ~/finatra-hello-world
should be
$ cp -R hello-world-heroku ~/finatra-hello-world
Would you mind adding that change? Thanks.

Done. Thanks.

Great, appreciate it. I'll get this pulled into our internal codebase today. It'll get pushed back to GitHub in a few days. I'll close out the pull request when it's made its way back to GitHub. Thanks again.

This has been pushed back out to GitHub in this commit - https://github.com/twitter/finatra/commit/d356d75b3ee94be0af81f26e7bf76e958075ce29
Thank you.


redesigned the joinus page

Description
Fixed the styling and layout of the whole page
Fixes #1074
Screenshots

Checklist

[x] Tests have been added or updated to cover the changes
[ ] Documentation has been updated to reflect the changes
[x] Code follows the established coding style guidelines
[x] All tests are passing

@thestarsahil please check

Work on same Color pattern of this website

Work on same Color pattern of this website

Can you explain ???

See the color in boxes , its not that color

See the color in boxes , its not that color

Oh yes,
Should give them a bluish colour??

@ayush-848 Yes

@ayush-848 Yes

@thestarsahil now check

Fix this

Fix this

I changed the file name which was 'Joinus.cc' to 'JoinUs.css'

@thestarsahil understood. The filename is not case-sensitive

Due to this ,
1.login page effected
2. Make a same navbar , don't implement extra changes
3. Same font will gonna used

Due to this , 1.login page effected 2. Make a same navbar , don't implement extra changes 3. Same font will gonna used

Ok

@thestarsahil you can check it now. I have reverted the file name

@thestarsahil please check it


[Integrated driver] Adopt new driver APIs for descriptions.

The Swift driver added some APIs to provide descriptions and
whether a particular job invokes the Swift frontend. Use those
APIs rather than switching on the "kind" of a Swift driver job.

@swift-ci smoke test


I think robohash is down. Everything ok?

Looks like there were no commits for a couple years until this past day. I'm guessing the author tried to deploy the new code with disastrous results?
@e1ven need any help?

The nodes were getting overloaded, which was causing the site to go slow and stop responding.. I added some additional digital ocean nodes. When I did, it wasn't generating the hashes with the same order as it had traditionally. I didn't want the hash to depend on what server you were hitting, so I added code to re-force the hash order.
Coming back to RH after a few years, I realize I should have spent more time originally ensuring that the order for the images was always consistent, rather than implicitly relying on inode order.
I also should have had test coverage, but that's another show.
Once I fixed the code, I was able to bring the new nodes online.
When nodes start becoming overloaded, image requests that don't hit cache start building up, until it's not keeping up with demand, building a bigger and bigger backlog. This causes the machine to eventually go out of rotation, and the other nodes get hit even harder, until you're in runaway.
At that point, if you add new nodes to the rotation, they'll get 100% of the traffic, and go down too - You need to take the Load balancer down entirely, drain the connections to each node, then bring it back up.
If it were a real app, I'd probably set up an auto-scale group at EC2, but that would cost me real money :)
Sorry about the downtime - Hopefully it should be fixed now.


[BUG] TypeError: asdict() should be called on dataclass instances

Required prerequisites

[X] I have read the documentation https://camel-ai.github.io/camel/camel.html.
[X] I have searched the Issue Tracker and Discussions that this hasn't already been reported. (+1 or comment there if it has.)
[X] Consider asking first in a Discussion.

What version of camel are you using?
0.1.1
System information
python: 3.10.14
camel :0.1.1
Problem description
Traceback (most recent call last):
File ".\camel-master\examples\ai_society\role_playing.py", line 75, in
main()
File ".\camel-master\examples\ai_society\role_playing.py", line 50, in main
assistant_response, user_response = role_play_session.step(input_msg)
File "C:\Users\Carlos\miniconda3\envs\LLM\lib\site-packages\camel\societies\role_playing.py", line 435, in step
user_response = self.user_agent.step(assistant_msg)
File "C:\Users\Carlos\miniconda3\envs\LLM\lib\site-packages\camel\agents\chat_agent.py", line 278, in step
self.update_memory(input_message, OpenAIBackendRole.USER)
File "C:\Users\Carlos\miniconda3\envs\LLM\lib\site-packages\camel\agents\chat_agent.py", line 192, in update_memory
self.memory.write_record(MemoryRecord(message, role))
File "C:\Users\Carlos\miniconda3\envs\LLM\lib\site-packages\camel\memories\base.py", line 69, in write_record
self.write_records([record])
File "C:\Users\Carlos\miniconda3\envs\LLM\lib\site-packages\camel\memories\chat_history_memory.py", line 105, in write_records
stored_records.append(record.to_dict())
File "C:\Users\Carlos\miniconda3\envs\LLM\lib\site-packages\camel\memories\records.py", line 76, in to_dict
**asdict(self.message)
File "C:\Users\Carlos\miniconda3\envs\LLM\lib\dataclasses.py", line 1237, in asdict
raise TypeError("asdict() should be called on dataclass instances")
TypeError: asdict() should be called on dataclass instances
Reproducible example code
The Python snippets:

Command lines:

Extra dependencies:

Steps to reproduce:

Traceback
Traceback (most recent call last):
  File "LLM\camel-master\examples\ai_society\role_playing.py", line 75, in <module>
    main()
  File "LLM\camel-master\examples\ai_society\role_playing.py", line 50, in main
    assistant_response, user_response = role_play_session.step(input_msg)
  File "C:\Users\Carlos\miniconda3\envs\LLM\lib\site-packages\camel\societies\role_playing.py", line 435, in step
    user_response = self.user_agent.step(assistant_msg)
  File "C:\Users\Carlos\miniconda3\envs\LLM\lib\site-packages\camel\agents\chat_agent.py", line 278, in step
    self.update_memory(input_message, OpenAIBackendRole.USER)
  File "C:\Users\Carlos\miniconda3\envs\LLM\lib\site-packages\camel\agents\chat_agent.py", line 192, in update_memory
    self.memory.write_record(MemoryRecord(message, role))
  File "C:\Users\Carlos\miniconda3\envs\LLM\lib\site-packages\camel\memories\base.py", line 69, in write_record
    self.write_records([record])
  File "C:\Users\Carlos\miniconda3\envs\LLM\lib\site-packages\camel\memories\chat_history_memory.py", line 105, in write_records
    stored_records.append(record.to_dict())
  File "C:\Users\Carlos\miniconda3\envs\LLM\lib\site-packages\camel\memories\records.py", line 76, in to_dict
    **asdict(self.message)
  File "C:\Users\Carlos\miniconda3\envs\LLM\lib\dataclasses.py", line 1237, in asdict
    raise TypeError("asdict() should be called on dataclass instances")
TypeError: asdict() should be called on dataclass instances

Expected behavior
No response
Additional context
No response

reason:
the error is occurred since your 'input_msg' is created by 'role_play_session.init_chat()', which is a (assistant msg, user msg) set with type (BaseMessage, List[BaseMessage]). But 'role_play_session.step' only accepts one assistant msg with type BaseMessage.
solution:
In role_playing.py, try replacing the line of code "input_msg = role_play_session.init_chat()" to "input_msg, _ = role_play_session.init_chat()"

Thanks @WuJunde help to answer this!


🌐 Add Chinese translation for Tutorial - Bigger Applications - Multiple Files

@RunningIkkyu @maoyibo @yanever Please take a look.

Thanks @waynerv! :clap: :clap: :rocket:
And thanks for the reviews @yanever , @blt232018 , and @Laineyzhang55 :coffee: :cake:


Brick should not depend on GToolkit-Debugger

Due to BrDebugglableElementStencil, which we probably should move to the debugger package?


How to eval

I call mmcls.model from the outside, but it can only be trained, not verified, how can I verify it?
This is my code:
model = dict(
type='ImageClassifier',
backbone=dict(
type='SwinTransformer', arch='base', img_size=224, drop_path_rate=0.5),
neck=dict(type='GlobalAveragePooling'),
head=dict(
type='LinearClsHead',
num_classes=8,
in_channels=1024,
init_cfg=None,  # suppress the default init_cfg of LinearClsHead.
loss=dict(
type='LabelSmoothLoss', label_smooth_val=0.1, mode='original'),
cal_acc=False),
init_cfg=[
dict(type='TruncNormal', layer='Linear', std=0.02, bias=0.),
dict(type='Constant', layer='LayerNorm', val=1., bias=0.),
dict(type='Pretrained', checkpoint='https://download.openmmlab.com/mmclassification/v0/swin-transformer/swin_tiny_224_b16x64_300e_imagenet_20210616_090925-66df6be6.pth')
])
net = build_classifier(model)

you can refer to the get_started docs to learn about the test.py tools.
If you want to learn about the mmcls python test\eval API, you can refer to notebook.


Permissions for specific druid datasources.

We are using the recommended steps to permission a user with gamma + specific druid datasource role, to limit the user to that specific druid datasource.
The /druiddatasourcemodelview/list/ route will still show the other available datasources. Upon clicking a datasource, access denied message is correctly shown.
However, the user should not be able to see other available datasources that he/she does not have permission to access.

To anyone willing to tackle this, it should be something similar to what has been done for SQLAlchemy tables:
https://github.com/airbnb/caravel/commit/061d4f1ac7088de7b39c8eea4f901ee9e006ce66


Add Obj-C support to PillButton color constants

Platforms Impacted

[x] iOS
[ ] macOS

Description of changes

Add Obj-C support to PillButton color constants
Add Obj-C support to PillButton corner radius

Verification
-Verified that PillButton colors and corner radius are included in the generated Obj-C header FluentUI-Swift.h

Before
After

Screenshot or description before this change
Screenshot or description with this change

Pull request checklist
This PR has considered:

[ ] Light and Dark appearances
[ ] VoiceOver and Keyboard Accessibility
[ ] Internationalization and Right to Left layouts
[ ] Different resolutions (1x, 2x, 3x)
[ ] Size classes and window sizes (iPhone vs iPad, notched devices, multitasking, different window sizes, etc)

Microsoft Reviewers: Open in CodeFlow

can you update your PR description with compared screenshots please?

what's the intended use here? if it is PillButtonBar, there is a way to customize PillButtonBar background color via "pillbuttonbackgroundcolor." also, changing the outlinestyle color itself seems not following the fluent guideline

what's the intended use here? if it is PillButtonBar, there is a way to customize PillButtonBar background color via "pillbuttonbackgroundcolor." also, changing the outlinestyle color itself seems not following the fluent guideline
@harrieshin
For some reason I can't reply to the comment directly, so answering here: in certain scenarios, PillButtonBar is not being used to contain the PillButtons (for example in the case of multiple sections of grouped PillButtons), so some other custom view is used. In order for those custom views (in Obj-C) to adopt similar appearances (e.g. background color, corner radius) these constants need to be publicly accessible to Obj-C.


maxOptions not working for mobile

Not sure if this a known issue, I could not find anything related anywhere.
I cant get the maxOptions option to work when I enable mobile menus.
Also cant get
$('#mySelect').on('changed.bs.select', function (e)
to work on mobile.
For desktop it is all working fine, not sure if there is any option I should be using?
Thanks,

I also have the same issue for maxOptions where when I enable mobile scrolling for mobile views, it completely ignores the data options like maxOptions and header but it works when I'm on desktop view (where data-mobile="false").
Did you ever figure out a solution?

Did you ever figure out a solution?

We will never know!


Client Allocation Request for: FileDrive

Client Allocation Questions
Core Information

Name: FileDrive
Website / Social Media: https://twitter.com/FileDrive1
DataCap Requested: 5TiB
Addresses to be Notarized: f3wgfwtrs5p6jrkwfl2mksqa2ivgbgdjjrhjbefy3n7qzvotc3y6sazmp5gfyj7um6jlgdvlbiepzawnc6wxtq
Notary Requested: steven004

Hey @laurarenpanda , thanks for your request. Can you kindly add more information / context here on:

yourself/ your organization (with links to official website/social media/news mentions etc)
Your history working on IPFS/Filecoin (notable contributions to the community, type of engagement shown over time etc)
Use case: type/source/quantity/diversity/scarcity of the data you plan to store on Filecoin
Miners you intend to allocate DataCap with allocation proportion(with redundancy/location/specific requirement of storage miners)
What's your next plan for the data you plan to store in Filecoin Network? For-profit or not?
Would you be OK in posting deal transactions here?

Thanks

Hey @laurarenpanda , thanks for your request. Can you kindly add more information / context here on:

yourself/ your organization (with links to official website/social media/news mentions etc)
Your history working on IPFS/Filecoin (notable contributions to the community, type of engagement shown over time etc)
Use case: type/source/quantity/diversity/scarcity of the data you plan to store on Filecoin
Miners you intend to allocate DataCap with allocation proportion(with redundancy/location/specific requirement of storage miners)
What's your next plan for the data you plan to store in Filecoin Network? For-profit or not?
Would you be OK in posting deal transactions here?

Thanks

Hi @steven004 , thanks for replying, here are my answers.

yourself/ your organization (with links to official website/social media/news mentions etc)

FileDrive team has been in Filecoin ecosystem from 2019, and conscientiously concentrate on development distributed storage solution. Our vision is to build a data transaction platform on Filecoin Network. Our team is composed of talents with years development experience. We have self-developed underlying codes, and technical architecture and solutions of distributed storage.
In 2019, we independently developed DriveUp, which is a beta version cloud storage application based on IPFS. Over hundreds of users participated in testing phase.
In 2020, we established Shanghai Xuanling Technology Co., Ltd, and began to work as start-up company.
Since September 2020, we participated in Slingshot competition by Protocol Labs and developed an application named FileDrive.
FileDrive is a open source databank powered by IPFS/Filecoin, users can retrieve any data by file-name or content hash. Now, there are over 2.9k files from global public datasets stored on it with capacity of more than 57TiB storage space.

Project website: http://filedrive.io
Team website: https://honghupro.com
Twitter: https://twitter.com/FileDrive1
WeChat Official Account: FileDrive
https://mp.weixin.qq.com/mp/profile_ext?action=home&__biz=MzkzMDE4ODg0MQ==&scene=124#wechat_redirect
Github: https://github.com/beeleelee
Slack: Laura Panda/ flytosky

Participated in Filecoin Virtual Community Meetup - January 2021: https://www.youtube.com/watch?v=0aVghq-syoo

Your history working on IPFS/Filecoin (notable contributions to the community, type of engagement shown over time etc)

Participating in Slingshot 2.2 with over 300 TiB data
Participated in Slingshot 2.1
Eligible Data: over 300TiB
Storage Awards: 1st Place
Booster Award
Participated in Slingshot Phase 1: totally earned 6,885FIL
Storage Awards: 3rd Place
Community Choice Awards: Personal User Storage(Third Place)
Booster Award
 Start-up project: DriveUp
 Cloud storage application based on IPFS
 Self-developed by FileDrive team

Use case: type/source/quantity/diversity/scarcity of the data you plan to store on Filecoin

All of the data on FileDrive are useful and valid, and from public datasets, which are on the list of Filecoin Slingshot curated datasets. On filedrive.io, there are over 57TiB data from more than 15 global public datasets. We'll choose scarce and valuable data and store no more than 10 copies.
All data are from public open datasets, as a result, there is no copyright issue involved.

List of Slingshot curated datasets: https://github.com/filecoin-project/slingshot/blob/master/datasets.md

Miners you intend to allocate DataCap with allocation proportion(with redundancy/location/specific requirement of storage miners)

Redundancy: at least 3 copies
Proportion: at least 3 miners
Location: intend to store data in Asia
Miners: have great reputation and contribution in Filecoin Community, accept real data deals during Slingshot Competition, or are willing to store real data on Filecoin Network.

What's your next plan for the data you plan to store in Filecoin Network? For-profit or not?

All data on filedrive.io are non-profit. Everyone can search, browse and download these data by using FileDrive.

Would you be OK in posting deal transactions here?

Yes, of course.

Hi @steven004 , thanks for replying, here are my answers.

yourself/ your organization (with links to official website/social media/news mentions etc)

FileDrive team has been in Filecoin ecosystem from 2019, and conscientiously concentrate on development distributed storage solution. Our vision is to build a data transaction platform on Filecoin Network. Our team is composed of talents with years development experience. We have self-developed underlying codes, and technical architecture and solutions of distributed storage.
In 2019, we independently developed DriveUp, which is a beta version cloud storage application based on IPFS. Over hundreds of users participated in testing phase.
In 2020, we established Shanghai Xuanling Technology Co., Ltd, and began to work as start-up company.
Since September 2020, we participated in Slingshot competition by Protocol Labs and developed an application named FileDrive.
FileDrive is a open source databank powered by IPFS/Filecoin, users can retrieve any data by file-name or content hash. Now, there are over 2.9k files from global public datasets stored on it with capacity of more than 57TiB storage space.

Project website: http://filedrive.io
Team website: https://honghupro.com
Twitter: https://twitter.com/FileDrive1
WeChat Official Account: FileDrive
https://mp.weixin.qq.com/mp/profile_ext?action=home&__biz=MzkzMDE4ODg0MQ==&scene=124#wechat_redirect
Github: https://github.com/beeleelee
Slack: Laura Panda/ flytosky

Participated in Filecoin Virtual Community Meetup - January 2021: https://www.youtube.com/watch?v=0aVghq-syoo

Your history working on IPFS/Filecoin (notable contributions to the community, type of engagement shown over time etc)

Participating in Slingshot 2.2 with over 300 TiB data
Participated in Slingshot 2.1
Eligible Data: over 300TiB
Storage Awards: 1st Place
Booster Award
Participated in Slingshot Phase 1: totally earned 6,885FIL
Storage Awards: 3rd Place
Community Choice Awards: Personal User Storage(Third Place)
Booster Award
 Start-up project: DriveUp
 Cloud storage application based on IPFS
 Self-developed by FileDrive team

Use case: type/source/quantity/diversity/scarcity of the data you plan to store on Filecoin

All of the data on FileDrive are useful and valid, and from public datasets, which are on the list of Filecoin Slingshot curated datasets. On filedrive.io, there are over 57TiB data from more than 15 global public datasets. We'll choose scarce and valuable data and store no more than 10 copies.
All data are from public open datasets, as a result, there is no copyright issue involved.

List of Slingshot curated datasets: https://github.com/filecoin-project/slingshot/blob/master/datasets.md

Miners you intend to allocate DataCap with allocation proportion(with redundancy/location/specific requirement of storage miners)

Redundancy: at least 3 copies
Proportion: at least 3 miners
Location: intend to store data in Asia
Miners: have great reputation and contribution in Filecoin Community, accept real data deals during Slingshot Competition, or are willing to store real data on Filecoin Network.

What's your next plan for the data you plan to store in Filecoin Network? For-profit or not?

All data on filedrive.io are non-profit. Everyone can search, browse and download these data by using FileDrive.

Would you be OK in posting deal transactions here?

Yes, of course.

Hey @laurarenpanda , thanks for the clarification. Can you kindly specify what part of data will be saved using the particular datacap if you are granted with this request? You know, the Slingshot curated datasets is a long list.

Hi @steven004 , thanks so much.

Using 5 TiB Datacap, We will storage data from Landsat8, which is a public dataset with multispectral time series satellite imagery of all land on Earth since 2013.
Landsat 8: https://registry.opendata.aws/landsat-8/#usageexamples

Hey @laurarenpanda , Your Datacap Allocation Request has been approved
Message sent to Filecoin Network

bafy2bzacedrfkzv6ymicfkfy6jl2ofuo7tdhsfht6nl3dgmwt7wndu6wjpsxa

Address

f3wgfwtrs5p6jrkwfl2mksqa2ivgbgdjjrhjbefy3n7qzvotc3y6sazmp5gfyj7um6jlgdvlbiepzawnc6wxtq

Datacap Allocated

5 TiB

Please check.

Hi @steven004 , here is the dos for this 5 TiB datacap deal transactions, please check it.

https://docs.google.com/spreadsheets/d/1NQUW2vQboFkYTlqiRZTCUNpLehGbJ_ojrkd2mFAeeqI/edit?usp=sharing

This user’s identity has been verified through filplus.storage


Angular Motor of 6DOF Joint isn't working predictably in Godot 4.0

Godot version
4.0 Beta 5
System information
Windows 10, Windows 11, irrelevant to the issue
Issue description
Angular motor setup that worked in Godot 3.5 no longer works (recreated) in Godot 4 Beta 5.

I make custom vehicle setup (instead of vehicle node for customization purpose)
Each wheel is connected to the main body via a 6DOF joint
I disable the X-axis rotation lock
I enable X-axis angular motor
It works in Godot 3.x, but do nothing in Godot 4
In general, Godot 4 joints work (for example, if I rotate the ground, the car rolls on it)
If we apply force to the car, it also gonna roll

Here is how it looks (meshes are just placeholders)

Steps to reproduce
Described above
Minimal reproduction project
GODOT_01.zip

Can you test this on 3.5 with the 3D physics engine set to GodotPhysics instead of the default Bullet?

Can you test this on 3.5 with the 3D physics engine set to GodotPhysics instead of the default Bullet? 4.0 uses GodotPhysics by default.

Yep, it isn't working if I switch to Godot Physics in 3.5, only works in Default

I left it for 3 minutes and after that one wheel (of two with motors) started to rotate oddly (Gofot Physics, 3.5)
https://user-images.githubusercontent.com/19660324/202806083-5a42732c-bedf-4e82-8d93-47e5ece9b124.mp4

@Calinou another interesting point is that I switched to Hinge 3D instead and angular limits are not actually limiting anything if the motor is enabled (and if they crossed the original value)

Duplicate of #66335.


Query servers by topology

What does this PR (Pull Request) do?

[x] This PR is not related to any Issue
This PR lets you query servers by topology, meaning querying servers whose cachegroups belong to a given topology.

Which Traffic Control components are affected by this PR?

Documentation
Traffic Ops
Traffic Portal

What is the best way to verify this PR?

Run the Traffic Ops API tests, which includes a test for the topology query parameter on GET /api/3.0/servers
In TP, create a topology, add cache groups, save. Then on the topology page under More you'll see View Servers. This will show you all the servers associated with the topology.
The following criteria are ALL met by this PR

[x] This PR includes tests
[x] This PR includes documentation
[x] This PR includes an update to CHANGELOG.md
[x] This PR includes any and all required license headers
[x] This PR does not include a database migration
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

Additional Information

@zrhoffman this PR has merge conflicts

Conflict is in traffic_portal/app/src/common/modules/form/topology/form.topology.tpl.html, @mitchell852 has been working on rebasing I believe

Merge conflicts fixed. Thanks @mitchell852!


Add find() variants and Travis build file.

Lemme know if you want me to drop the .travis.yml bit.  If you like the idea of CI for Boost.Algorithm, I'll add an Appveyor script for MSVC support.

BidiIter find_backward(BidiIter first, BidiIter last, T const & x)
East const, Zach?

I think I'd rather you proposed the CI stuff as a separate commit. That will keep the change log cleaner. I don't have a problem with the CI stuff, I'd just rather it was separated.

There, how's that?  I'll prepare an Appveyor script too before submitting the CI piece.

Thanks. Please watch the test bots; and ping me in a week or so to merge to master.


Adding missing method to mock driver

Hi
I added this method to the mock driver so it implements the interface HardwareDriver

doh! sorry for the delay, I completely missed this PR.
Cheers


Enrolling in a course does not necessary means i'm interested in a program

Steps to Reproduce
Enroll in a DEDP course (e.g. Political Economy and Economic Development)
Expected Behavior
See the course listed in my dashboard
Actual Behavior
The course is not listed.  Its listed only in the list of courses for the program that particular course belongs to.
I think we should list it as a course in the list of courses (because that's what my intention was as a user) and in the drawer (to say that "btw, this course is part of this program, in case you were interested")
Screenshot or Screencast

Related to this, making this change will also impact our need to address #703, which we'd pushed out a bit because the current behavior addressed that well enough for the short term.

Also related, in #915 we want to put the program card and drawer behind a feature flag.

We redesigned this with one dashboard for course enrollments and another dashboard for program enrollments.


Flaky "invalid memory address or nil pointer" error in rules package's tests

Spotted in https://travis-ci.org/prometheus/prometheus/builds/413101424
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xa684b0]
goroutine 111 [running]:
github.com/prometheus/prometheus/rules.(*RecordingRule).Eval(0xc420185880, 0xc17a20, 0xc4203e0000, 0x270c56ef, 0xed2fb8ea0, 0xee04e0, 0x0, 0x0, 0xee04e0, 0xc17a20, ...)
	/home/travis/gopath/src/github.com/prometheus/prometheus/rules/recording.go:73 +0xf0
github.com/prometheus/prometheus/rules.(*Group).Eval.func1(0xc179a0, 0xc4200a6050, 0x270c56ef, 0xed2fb8ea0, 0xee04e0, 0xc4200e2500, 0x0, 0xc1b4e0, 0xc420185880)
	/home/travis/gopath/src/github.com/prometheus/prometheus/rules/manager.go:384 +0x2ec
github.com/prometheus/prometheus/rules.(*Group).Eval(0xc4200e2500, 0xc179a0, 0xc4200a6050, 0x270c56ef, 0xed2fb8ea0, 0xee04e0)
	/home/travis/gopath/src/github.com/prometheus/prometheus/rules/manager.go:452 +0xd0
github.com/prometheus/prometheus/rules.(*Group).run.func1()
	/home/travis/gopath/src/github.com/prometheus/prometheus/rules/manager.go:230 +0x105
github.com/prometheus/prometheus/rules.(*Group).run(0xc4200e2500, 0xc179a0, 0xc4200a6050)
	/home/travis/gopath/src/github.com/prometheus/prometheus/rules/manager.go:243 +0x38f
github.com/prometheus/prometheus/rules.(*Manager).Update.func1.1(0xc4201c4140, 0xc4200e2500)
	/home/travis/gopath/src/github.com/prometheus/prometheus/rules/manager.go:679 +0xa7
created by github.com/prometheus/prometheus/rules.(*Manager).Update.func1
	/home/travis/gopath/src/github.com/prometheus/prometheus/rules/manager.go:674 +0x64
FAIL	github.com/prometheus/prometheus/rules	0.430s

I can not reproduce this test failed and the link seems to be passed. I would love to fix this bug.

@jojohappy right the failed build log has been overwritten. I don't know how to reproduce it unfortunately.

To reproduce, run it enough times and grab popcorn :)
➜  prometheus git:(master) for i in {1..5000}
do
   go test ./rules -count=1
done

ok  	github.com/prometheus/prometheus/rules	0.130s
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1426c3a]

goroutine 189 [running]:
github.com/prometheus/prometheus/rules.(*RecordingRule).Eval(0xc4201a64d0, 0x15ab2e0, 0xc420a667b0, 0x270c56ef, 0xed308ca2a, 0x1814b20, 0x0, 0x0, 0x1814b20, 0x15ab2e0, ...)
	/Users/goutham/go/src/github.com/prometheus/prometheus/rules/recording.go:73 +0xca
github.com/prometheus/prometheus/rules.(*Group).Eval.func1(0x15ab260, 0xc4200ac048, 0x270c56ef, 0xed308ca2a, 0x1814b20, 0xc4200eeb40, 0x0, 0x15aebe0, 0xc4201a64d0)
	/Users/goutham/go/src/github.com/prometheus/prometheus/rules/manager.go:384 +0x26f
github.com/prometheus/prometheus/rules.(*Group).Eval(0xc4200eeb40, 0x15ab260, 0xc4200ac048, 0x270c56ef, 0xed308ca2a, 0x1814b20)
	/Users/goutham/go/src/github.com/prometheus/prometheus/rules/manager.go:452 +0xad
github.com/prometheus/prometheus/rules.(*Group).run.func1()
	/Users/goutham/go/src/github.com/prometheus/prometheus/rules/manager.go:230 +0xc0
github.com/prometheus/prometheus/rules.(*Group).run(0xc4200eeb40, 0x15ab260, 0xc4200ac048)
	/Users/goutham/go/src/github.com/prometheus/prometheus/rules/manager.go:243 +0x288
github.com/prometheus/prometheus/rules.(*Manager).Update.func1.1(0xc4200baeb0, 0xc4200eeb40)
	/Users/goutham/go/src/github.com/prometheus/prometheus/rules/manager.go:679 +0x60
created by github.com/prometheus/prometheus/rules.(*Manager).Update.func1
	/Users/goutham/go/src/github.com/prometheus/prometheus/rules/manager.go:674 +0x56
FAIL	github.com/prometheus/prometheus/rules	0.115s


UI: Adjustable column widths in drill-down tables

UI Details

Allow users to adjust column widths in drill-down tables (or all tables) for improved readability of columns with text in cells.
Additional Comments

yeah, i'll remove this issue from 2.0.

This comes for ~free when we finish switching everything to {gt} (#289) 🎉


fix #204 improve memory for haxecpp target

https://github.com/jtransc/jtransc/blob/master/jtransc-rt-core/src/com/jtransc/JTranscSystem.java

JTranscSystem for example provides gcEnable and gcDisable features not available in java.lang.System with a fallback so you can use in plain jvm or using jtransc. If there is a feature about memory that jvm doesnt support: useMemory you can put it there and move all other implementations there to make it consistent

@soywiz I am rewrite backend, and not use it, maybe make private this function without move to JTransc? Use for calculate freeMemory, because haxe have not function for get free.

https://github.com/jtransc/gdx-backend-jtransc/commit/e072a634b5c854ca1fabad8960253a7a42e8cc5d
sorry for commit without review, i am mistake with branch =)


Add donation reminder

For non-GooglePlay versions:

[x] On N-th use (lets say 10th)
[x] And when app is updated

Show the popup with request for donation with BTC address to be donated to.

every 14 days


Documentation: Clarify mapping from high-level agent properties to experiments and environments

Hello Ian and others!
I'm having a look at bsuite after Ian Osband's talk at the Simons Institute Deep RL workshop. After spending a few minutes browsing the documentation and source code here on GitHub I had a suggestion for improving the documentation.
My first question when browsing this project is "The radar plot on the readme is lovely, I wonder what experiments contribute to a good ____________ score". Where the blank is e.g. 'generalization'.
After browsing the source code for a few minutes this isn't immediately obvious. I can see a little bit of information regarding this at the example colab notebook. It would be nice to promote this mapping to a 'first class' member of the documentation somewhere :)

Hi Aaron!
Apologies for the delay in getting back here... we can try and add some more documentation about where this comes from.
In each experiment/sweep.py there is a list of TAGS that define which radar spokes each experiment contribute to:
e.g. https://source.corp.google.com/piper///depot/google3/third_party/py/bsuite/experiments/cartpole_noise/sweep.py
Has TAGS = ('noise', 'generalization')
If we add too much documentation separate to the code, then we run a significant risk of getting things out-of-sync.
Also, I think we hope that the "colab notebook" is really meant to be a first class part of bsuite.
Probably the solution is to explain where these TAGS are located and what they mean?
Would that work for you?

Hi Ian :) Loved your talk by the way.
Yes, I think the TAGS variable(s) is/are exactly what I was looking for when browsing the documentation.

Probably the solution is to explain where these TAGS are located and what they mean?

Exactly :) This could be as simple as a heading on the readme explaining that this is how the mapping from environments to algorithm attributes is defined, with a link to one of the source files?


HTTPClient Basic authentication header handling is weird since v1.24.1

This block didn't raise any error before, but it raises WebMock::NetConnectNotAllowedError since 1.24.1.
It seems userinfo is set in the stub request wrong way.
require 'webmock'
include WebMock::API

WebMock.disable_net_connect!

endpoint = 'http://auth.example.com/'
headers = {
  'Authorization': 'Basic Y2xpZW50X2lkOmNsaWVudF9zZWNyZXQ'
}

stub_request(:post, endpoint).with(
  headers: headers
)

HTTPClient.post(endpoint, nil, headers)

@nov thank you for reporting this.
@mkarnebeek any thoughts?

It depends what the idea is behind handling basic auth.

When supplying credentials in the URI,  it is clear the mock should also have it in the URI.
When supplying credentials via de http client's api (for example HTTPClients's basic_auth method on a client), it's unclear if the mock should have the credentials in the URI. Judging from existing WebMock implementation of other http clients, it should be in de URI. (i think it is even in the specs)
When supplying headers, it's probably up for discussion. My previous PR changed this behavior to be consistent with the above two, but there is also something to be said to have the mock "as close to the original call", in which case the credentials should not be in the URI.

I'm currently on vacation and will be back the 16th this month (a week from now). Let me known if i can be of any help then.

As for the third case, we should also look how WebMock implements this for other http client libraries.

With the fact that basic authentication can be specified in 2 different ways (url or header) it's tricky indeed.
Perhaps WebMock could treat Authorization header and credentials in the url as equal (both ways, currently it's only one way). In case it's important that the request has authorization header, the behaviour would be wrong.

endpoint = 'http://auth.example.com/'
headers = {
  'Authorization': 'Basic Y2xpZW50X2lkOmNsaWVudF9zZWNyZXQ'
}

stub_request(:post, endpoint).with(
  headers: headers
)

HTTPClient.post(endpoint, nil, headers)

@nov I have been thinking about it and I agree that the current solution is confusing.
The simplest solution would be to not remove the Authorization headers from the request signature.
This will allow making expectations on request headers in stubs.
Unfortunately, WebMock will still extract the header, decode it and add the userinfo to the url.
That's the current behaviour and removing it would break backward compatibility.
This has additional side effect that the stub without userinfo specified, is not going
to match a request signature with userinfo present (and it will be added to request signature, as mentioned above).
To have a matching stub, one will have to add userinfo to the url anyway,
despite declaring expected authorization header in the stub headers already.
This will make things complex.
I'm considering removing this whole mess. Keeping userinfo in url completely separate to authorization headers, breaking backward compatibility and upgrading WebMock to version 2.0.0.
This will require programmes to create stubs with base64 encoded version of the username and password, which won't be as readable, but perhaps that's the way right way to do it.
Any thoughts?
//cc @upuls @sirn

For reference https://github.com/bblimke/webmock/issues/593

Fixing in next major version is fine for me :)
I'm not understanding why things were OK before 1.24.1 yet though.

It worked because Authorization header was ignored by WebMock's HTTPClient adapter, unless credentials were set with set_basic_auth

Having 2.0.0 leave authorization header as-is separate from userinfo sounds good to me.
One of the pattern I did quite often is when I need to stub a request that happen to contain authorization header that I'm not actually cared (since authorization is done by other components), I found myself to do a lot of stubbing using Regex URL to get around the userinfo.
In either case, I'm very much prefer if WebMock do not transform the request and treat userinfo and authorization header separately (userinfo only if it is in the URL, leave it in header if it is in the header).

@nov Could you please check if version 2.0.0.beta1 resolves this issue? Please see the changes here https://github.com/bblimke/webmock/blob/2.0/CHANGELOG.md#200
@nov @sirn @uplus Version 2.0 is backwards incompatible with version 1.x. Do you find the information in the CHANGELOG sufficient?

cool, 2.0.0.beta1 works perfect for my gem ;-)

Yes, the change log details are sufficient to go by. Will give it a try and
report back if we hit a snag
Thanks!
On Tue, Apr 19, 2016 at 7:16 AM, Nov Matake<EMAIL_ADDRESS>wrote:

cool, 2.0.0.beta1 works perfect for my gem ;-)
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/bblimke/webmock/issues/591#issuecomment-211940098

The changelog is clear enough to me, but I think it would be nice if "Important! Since version 2.0.0…" in 2.0.0 README is moved to the "Upgrading…" section (since now it's kinda buried inside the examples.)


Ortho 7: group page, new  proteins section:  UI improvements

https://feature.orthomcl.org/orthomcl.feature/app/record/group/OG7_0000696
I know a few updates have been proposed but here some easy options  to improve the usability

smaller pfam table with max height
---- located in middle or left
----  ideally header stays as you scroll
---- add search to reduce the domains
---- add sort

I'd say this has all been superseded by @dmfalke's work on the filter drop-down buttons.
The request for a sticky table header was presumably just for the Pfam table that is no more. However, I had a think about adding this feature for the main table, but it's tricky to implement because of the tree. The tree isn't in a table cell/column. It's just next to the table. So I don't think that's going to happen unless we go back to the drawing board.
Closing this ticket.


Allow loading of artifacts without needing to activate the artifact store (again)

Describe changes
I fixed the logic of reading artifacts from ZenML to achieve the following snippet to work as usual, without the need to activate the stack before that:
from zenml.client import Client

artifact = Client().get_artifact_version('some-uuid')
loaded_artifact = artifact.load()

Pre-requisites
Please ensure you have done the following:

[ ] I have read the CONTRIBUTING.md document.
[ ] If my change requires a change to docs, I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] I have based my new branch on develop and the open PR is targeting develop. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.
[ ] If my changes require changes to the dashboard, these changes are communicated/requested.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Other (add details above)

Haven't looked at it in detail yet, just a more general question: What's the technical reason why this is not possible with fileio anymore and we have to use the artifact store methods in the materializers?

There is one main reason behind it: fileio works smoothly (meaning in a protected fashion, according to previous PRs) for all FS types, except local, while local is used in many other places outside of materializers' story, so to keep writing of artifacts and logs in scope-aware mode without the need to care about the underlying FS - I moved them to go via Artifact Stores. This PR is not changing that (it was already done and released) it just adds the possibility to set an artifact store explicitly in the materializer class, so we can pull smoothly without the need to switch stacks.

I see, with that in mind the changes in this PR look good to me.
However I still don't really get why we made those changes to use the artifact stores in the first place, doesn't fileio contains some useful methods built on top of the artifact store interface (e.g. copying from one store to another) that are very useful inside the materializers?

I see, with that in mind the changes in this PR look good to me. However I still don't really get why we made those changes to use the artifact stores in the first place, doesn't fileio contains some useful methods built on top of the artifact store interface (e.g. copying from one store to another) that are very useful inside the materializers?

This might be indeed the case, that usage of some fileio methods might come in handy on top of the artifact store methods, but the PR merged previously was aiming to close the gap with the usage of unsafe paths (e.g. outside of artifact store bounds) since it was reported as a bug.
I cannot think of a scenario, where a materializer has to work with some data from outside of the configured artifact store. My reasoning: materializer is used only in steps (using them directly is possible, but is not what is officially supported) and inside a step, we always have a stack set, so we never face multi-artifact store use-case, as of now. If going forward, we will support different artifact stores for different steps inside one pipeline, my assumption still stands, since in one step we only deal with one AS. Does it make any sense or I missed something important? @schustmi

The scenario I was thinking of was actually copying local directories <-> artifact store.

I see, so fileio.copy still covers this case, but the previous PR I mentioned is protecting a bit of our standard materialized from malicious use. I understand that cannot fully get rid of the cases when we go beyond artifact store bounds and this can be kept as is in other materialized with more complex logic.
I will merge this one now and we can create a follow-up for that if you find this needed.
What can be actually done for the use case you described is also achievable with the artifact store interface, but with a bit more sugar around:
with self.artifact_store.open("s3://some_path/05b56688-931a-44f8-8777-035b046e191f.log","rb") as src:
     with open("local-file.log","wb") as tgt:
         tgt.write(src.read())


Add reusable workflow for build-push

Description

https://github.com/aica-technology/.github/issues/3

This PR adds a workflow that wraps the two workflows (multi arch build-push and write file) from our .github repository for the particular case of our docker-images. In other words, this translates - with minor differences - the build-push action into a workflow, such that we are able to reuse other workflows from other places.
While we still have that special parsing of inputs that can get the Dockerfile path and workspace directory from the image names (ros2_control_libraries with branch develop if you want to build ros2-control-libraries:humble-devel etc.) we have the special case of the ros2_ws where we need to copy the sshd_entrypoint.sh script. For that, we need to upload the file as an artifact and pass the artifact name and path to the build-push workflow from the .github repo.
I want to show you the new workflow before I delete the existing actions and refactor the current workflows. This has been tested on my fork already.

Review guidelines

Estimated Time of Review: x minutes

Needed to rename the architecture argument to `platforms


Invalid call to git-mkver

Bug report
What is the current behavior?
I've updated the release, because I needed to use a version of poetry compatible with the latest pyproject.toml standard.
I made the release (1.0.1) and am now getting the following error when running:
/usr/bin/docker run --name octuechecksemanticversion101_077300 --label 1af1a0 --workdir /github/workspace --rm -e "INPUT_PATH" -e "INPUT_BREAKING_CHANGE_INDICATED_BY" -e "HOME" -e "GITHUB_JOB" -e "GITHUB_REF" -e "GITHUB_SHA" -e "GITHUB_REPOSITORY" -e "GITHUB_REPOSITORY_OWNER" -e "GITHUB_REPOSITORY_OWNER_ID" -e "GITHUB_RUN_ID" -e "GITHUB_RUN_NUMBER" -e "GITHUB_RETENTION_DAYS" -e "GITHUB_RUN_ATTEMPT" -e "GITHUB_REPOSITORY_ID" -e "GITHUB_ACTOR_ID" -e "GITHUB_ACTOR" -e "GITHUB_TRIGGERING_ACTOR" -e "GITHUB_WORKFLOW" -e "GITHUB_HEAD_REF" -e "GITHUB_BASE_REF" -e "GITHUB_EVENT_NAME" -e "GITHUB_SERVER_URL" -e "GITHUB_API_URL" -e "GITHUB_GRAPHQL_URL" -e "GITHUB_REF_NAME" -e "GITHUB_REF_PROTECTED" -e "GITHUB_REF_TYPE" -e "GITHUB_WORKFLOW_REF" -e "GITHUB_WORKFLOW_SHA" -e "GITHUB_WORKSPACE" -e "GITHUB_ACTION" -e "GITHUB_EVENT_PATH" -e "GITHUB_ACTION_REPOSITORY" -e "GITHUB_ACTION_REF" -e "GITHUB_PATH" -e "GITHUB_ENV" -e "GITHUB_STEP_SUMMARY" -e "GITHUB_STATE" -e "GITHUB_OUTPUT" -e "RUNNER_OS" -e "RUNNER_ARCH" -e
[2024-07-25 11:23:5[6](https://github.com/octue/amy/actions/runs/10092701070/job/27908459394#step:4:7),040 | INFO | check_semantic_version.check_semantic_version] Getting current version from '/github/workspace/pyproject.toml'.
[2024-07-25 11:23:56,[7](https://github.com/octue/amy/actions/runs/10092701070/job/27908459394#step:4:8)32 | WARNING | check_semantic_version.check_semantic_version] No `mkver.conf` file found. Generating one instead.
Traceback (most recent call last):
  File "/usr/local/bin/check-semantic-version", line [8](https://github.com/octue/amy/actions/runs/10092701070/job/27908459394#step:4:9), in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.10/site-packages/check_semantic_version/cli.py", line 30, in main
    match = check_versions_match(args.path, args.breaking_change_indicated_by)
  File "/usr/local/lib/python3.[10](https://github.com/octue/amy/actions/runs/10092701070/job/27908459394#step:4:11)/site-packages/check_semantic_version/check_semantic_version.py", line 57, in check_versions_match
    expected_semantic_version = _get_expected_semantic_version(
  File "/usr/local/lib/python3.10/site-packages/check_semantic_version/check_semantic_version.py", line 141, in _get_expected_semantic_version
    raise CalledProcessError(returncode=e.returncode, cmd=e.cmd, output=e.output, stderr=e.stderr) from None
check_semantic_version.check_semantic_version.CalledProcessError: Command '['git-mkver', '-c', '/tmp/tmpkh_32qvh', 'next']' returned non-zero exit status 1. Stderr: b''

What is the expected behavior?
Should work as normal
Other information
https://github.com/octue/amy/actions/runs/10092701070

I can reproduce this error by running this in a repository on my local:
docker run -v $(pwd):/code -it octue/check-semantic-version:1.0.3 /code/pyproject.toml

WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
[2024-10-08 16:37:58,448 | INFO | check_semantic_version.check_semantic_version] Getting current version from '/code/pyproject.toml'.
[2024-10-08 16:37:59,039 | WARNING | check_semantic_version.check_semantic_version] No `mkver.conf` file found. Generating one instead.
[2024-10-08 16:37:59,040 | INFO | check_semantic_version.check_semantic_version] `mkver.conf` file created at '/tmp/tmpsy3s4zw5'.
Traceback (most recent call last):
  File "/usr/local/bin/check-semantic-version", line 8, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.10/site-packages/check_semantic_version/cli.py", line 30, in main
    match = check_versions_match(args.path, args.breaking_change_indicated_by)
  File "/usr/local/lib/python3.10/site-packages/check_semantic_version/check_semantic_version.py", line 57, in check_versions_match
    expected_semantic_version = _get_expected_semantic_version(
  File "/usr/local/lib/python3.10/site-packages/check_semantic_version/check_semantic_version.py", line 143, in _get_expected_semantic_version
    raise CalledProcessError(returncode=e.returncode, cmd=e.cmd, output=e.output, stderr=e.stderr) from None
check_semantic_version.check_semantic_version.CalledProcessError: Command '['git-mkver', '-c', '/tmp/tmpsy3s4zw5', 'next']' returned non-zero exit status 1. Stderr: b''

However, if I shell into the container and call the CLI in there, it works:
docker run -v $(pwd):/code -it --entrypoint=/bin/bash octue/check-semantic-version:1.0.3

check-semantic-version pyproject.toml
[2024-10-08 16:41:37,622 | INFO | check_semantic_version.check_semantic_version] Getting current version from '/code/pyproject.toml'.
[2024-10-08 16:41:38,203 | WARNING | check_semantic_version.check_semantic_version] No `mkver.conf` file found. Generating one instead.
[2024-10-08 16:41:38,204 | INFO | check_semantic_version.check_semantic_version] `mkver.conf` file created at '/tmp/tmpashc30yv'.
VERSION PASSED CHECKS: The current version is the same as the expected semantic version: 0.4.1.

Curiously, I can run git-mkver next from my local:
docker run -v $(pwd):/code --workdir=/code \
  --entrypoint=git-mkver \
  octue/check-semantic-version:1.0.3 next

WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
0.1.0+improve-shell-workflow.967ee40

The newly-released version 1.0.4 seems to fix the issue.
docker run -v $(pwd):/code octue/check-semantic-version:1.0.4 /code/pyproject.toml

WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
[2024-10-09 15:39:53,537 | INFO | check_semantic_version.check_semantic_version] Getting current version from '/code/pyproject.toml'.
[2024-10-09 15:39:54,126 | INFO | check_semantic_version.check_semantic_version] Current version: 0.4.1
[2024-10-09 15:39:54,127 | WARNING | check_semantic_version.check_semantic_version] No `mkver.conf` file found. Generating one instead.
[2024-10-09 15:39:54,128 | INFO | check_semantic_version.check_semantic_version] `mkver.conf` file created at '/tmp/tmplcqjcadd'.
VERSION FAILED CHECKS: The current version (0.4.1) is different from the expected semantic version (0.1.0).

The above runs locally but the action still fails with the same error:
[2024-10-09 15:57:01,391 | INFO | check_semantic_version.check_semantic_version] Getting current version from '/github/workspace/pyproject.toml'.
[2024-10-09 15:5[7](https://github.com/octue/octue-sdk-python/actions/runs/11258547471/job/31305752555#step:4:8):02,140 | INFO | check_semantic_version.check_semantic_version] Current version: 0.60.1
[2024-10-09 15:57:02,141 | WARNING | check_semantic_version.check_semantic_version] No `mkver.conf` file found. Generating one instead.
[2024-10-09 15:57:02,143 | INFO | check_semantic_version.check_semantic_version] `mkver.conf` file created at '/tmp/tmp2y4fi[8](https://github.com/octue/octue-sdk-python/actions/runs/11258547471/job/31305752555#step:4:9)ct'.
Traceback (most recent call last):
  File "/check_semantic_version/check_semantic_version.py", line 142, in _get_expected_semantic_version
    process = subprocess.run(["git-mkver", "-c", config_path, "next"], capture_output=True, check=True)
  File "/usr/local/lib/python3.10/subprocess.py", line 526, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['git-mkver', '-c', '/tmp/tmp2y4fi8ct', 'next']' returned non-zero exit status 1.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/bin/check-semantic-version", line 8, in <module>
    sys.exit(main())
  File "/check_semantic_version/cli.py", line 3[9](https://github.com/octue/octue-sdk-python/actions/runs/11258547471/job/31305752555#step:4:10), in main
    match = check_versions_match(args.path, args.breaking_change_indicated_by)
  File "/check_semantic_version/check_semantic_version.py", line 56, in check_versions_match
    expected_semantic_version = _get_expected_semantic_version(
  File "/check_semantic_version/check_semantic_version.py", line 144, in _get_expected_semantic_version
    raise CalledProcessError(returncode=e.returncode, cmd=e.cmd, output=e.output, stderr=e.stderr)
check_semantic_version.check_semantic_version.CalledProcessError: Command '['git-mkver', '-c', '/tmp/tmp2y4fi8ct', 'next']' returned non-zero exit status 1. Stderr: b''

I've just checked that version 1.0.0.beta-9 of the action still works. I'll look into the diff between the latest version and that version


HPI-PPI not working

In HPI-PPI tool, no matter what organism or option I select, "View N interactions" button keeps showing spinning wheel. Also, interaction tab at the genome level also shows only spinning wheels.
-Maulik

This is due to the facet that old data api path changed in recent release. Need to change source code (base url for the api). will work on it

this is fixed and available on production.


Makefile.inc: Add support for building AMD Onyx coreboot.

This change uses an AMD coreboot defined variable from their projects Makefile, to avoid using the Intel specific coreboot config changes implemented in the osf-builder Makefile.inc
Signed-off-by: Eddie Vas<EMAIL_ADDRESS>

The changes look good, but I think the commit message needs to be updated. It appears that we're really just telling the Makefile not to worry about Intel blobs. That doesn't necessarily have anything to do with AMD.
(fwiw, I'm also looking at builds for other chips: #5

LGTM. @dhendrix @ArthurHeymans I will merge this PR if no additional comment till Friday.

Looks good now. LGTM


FEATURE -

As a developer,
I want to modify the mock server on the fly during my Opa5 tests,
so that I can perform actions such as reverting data or mock error responses
Description
What is the high level purpose and value of the feature?  The description should ensure that anyone reading understands what it is doing (at a high level) and most importantly why.
I have a UI5 application (developed in TypeScript) that uses Opa5 for integration testing. As I wrote my tests, I realised that

the test order sometimes affects whether all the journeys can pass. For example, say I have a list report page and an object page. I can change the status of the entities (e.g. from NEW -> APPROVED) in both the list page and object page.

In the list page, I have a test to make sure filtering by NEW works by checking the correct number of results.
If the detail page journey, which includes testing if the entity can be APPROVED, runs first, then the list page journey fails as the expected number of entities with the NEW status is now wrong.

I have tests to check if error handling is implemented correctly, that is if an error occurred, it should display a MessageBox. I am able to mock an error response using the mock server API for PATCH requests, but not for DELETE requests.

Technical Design
What modules need to be created or enhanced?
How would the functionality be exposed and how can it be consumed?
Acceptance Criteria
GivenWhenThen format (https://martinfowler.com/bliki/GivenWhenThen.html)
Given I have 2 Opa5 tests whose successful execution depends on which is ran first
when I execute a function that lets me change the mock data inside the tests
then my tests will pass regardless of the order it is ran first.
Given I have an Opa5 test that needs to mock an error response from the server
when I execute a function that lets me mock an error response
then my tests will run with the error response and check that it is handled properly.
Notes
Tasks

[ ]
[ ] Unit Tests added
[ ] Test Cases defined

Modifying mockserver on the fly to accomodate for test is not the recommended way to achieve what you want.
Intead we recommend that you define different set of mockdata using the contextBasedIsolation option.
Once this is enabled by passing the sap-client=xxx parameter, all request going into the mockserver will have this tenantId parameter available and each tenant will have it's own independent set of data (can be either the same or different)
You can see how this is used in practice here https://github.com/SAP/open-ux-odata/blob/15a26c5e3869067c90c5bc99afe4069223f74c6c/packages/fe-mockserver-core/test/unit/data/mockdata/MyRootEntity.js#L4
Regards
Nicolas

Hi Nicolas, thanks for pointing out the use of contextBasedIsolation. It does seem useful for separating mock data for different test scenarios.
Currently, I am also facing another issue where I have to restart the mock server every time I re-run the integration tests, which I don't think contextBasedIsolation helps in this case. For example, I am testing if I can approve an entity, but I realised in my test I have written the assertion wrongly causing the test to fail (however the approve action works). Now, my entity has the status APPROVED, and to re-test this test case I have to restart the mock server again to change the status of my entity back to NEW. May I ask if you know of a way to work around this? Thank you!

If you POST to $metadata/reload the mockdata will be reloaded, it is what is usually done in FioriElements based OPA test.
It's also part of the BaseArrangements class from sap.fe.test

Thank you so much! I managed to get the reloading to work :)
Will be closing this issue now since the feature requests were solved with existing features


Docs missing for new white handling option

With https://github.com/Aircoookie/WLED/pull/3073 a new option is added to the Auto-calculate white channel from RGB option called Max.
The Explanation seems to be missing in  https://kno.wled.ge/features/cct/
https://github.com/Aircoookie/WLED-Docs/blob/51b81e2c45548e13e477e084833f4d560c9bd0de/docs/features/cct.md#L18-L23

You are welcome to add that information.


ssl handshake without hostname

Flutter Version：Flutter 2.8.1 • channel stable
Dart SDK version: 2.15.1 (stable)
I need to use the SNI method to make SNI requests, but I get an error when I use Flutter's httpClient/dio and other libraries for SNI requests: HandshakeException: Connection terminated during handshake
I am very sure that my server is normal, because I can access it using the URLConnection provided by Android or the third-party library Okhttp.
It is currently suspected that this error is caused by not carrying the hostname during the SSL handshake process, I hope it can be fixed

@rayku-chans
Can you provide a minimal reproducible code sample using http package along with entire error log ? dio is a third party.


Pandera integration using new plugin system

Pandera integration using new plugin system
This PR implements a pandera plugin to support pandera.SchemaModels as an alternative way of expressing dataframe types in flyte tasks and workflows.
import flytekitplugins.pandera

import pandera as pa
from pandera.typing import DataFrame, Series

class Schema(pa.SchemaModel):
    col1: Series[int]
    col2: Series[float]

@task
def my_task(df: DataFrame[Schema]):
    ...

Type

[ ] Bug Fix
[ ] Feature
[X] Plugin

Are all requirements met?

[ ] Code completed
[ ] Smoke tested
[ ] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
How did you fix the bug, make the feature etc. Link to any design docs etc
Tracking Issue
https://github.com/lyft/flyte/issues/
Follow-up issue
NA
OR
https://github.com/lyft/flyte/issues/

Codecov Report

Merging #354 (729364d) into master (9842493) will decrease coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #354      +/-   ##
==========================================
- Coverage   96.00%   95.94%   -0.06%
==========================================
  Files           2        2
  Lines          75       74       -1
  Branches        8        8
==========================================
- Hits           72       71       -1
  Misses          1        1
  Partials        2        2

Impacted Files
Coverage Δ

tests/scripts/test_flytekit_sagemaker_runner.py
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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

Codecov Report

Merging #354 (729364d) into master (9842493) will decrease coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #354      +/-   ##
==========================================
- Coverage   96.00%   95.94%   -0.06%
==========================================
  Files           2        2
  Lines          75       74       -1
  Branches        8        8
==========================================
- Hits           72       71       -1
  Misses          1        1
  Partials        2        2

Impacted Files
Coverage Δ

tests/scripts/test_flytekit_sagemaker_runner.py
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9842493...729364d.

Thanks.  let me know what you think. https://github.com/cosmicBboy/flytekit/pull/1


Docs: Build Janus example on OSX

Documented how to build the janus-gateway example on OSX.

Thanks for the contribution @feixiao!

Pull Request Test Coverage Report for Build 2253

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.1%) to 80.335%

Files with Coverage Reduction
New Missed Lines
%

internal/mux/mux.go
2
95.0%

Totals

Change from base Build 2245:
0.1%

Covered Lines:
3881

Relevant Lines:
4831

💛  - Coveralls


overscroll gets stuck when you move your cursor quickly (touchpad)

Describe the bug

overscroll can get stuck when you move your cursor quickly (touchpad)
Steps to reproduce the bug

Steps to reproduce the behavior:

Open something you can scroll. Let's go with the start menu
Scroll down a little bit using your touchpad (by moving your fingers up w/ default settings)
Scroll up (by moving your fingers down w/ default settings) and let go then quickly move your cursor

Expected behavior

it would go back down, just like it does when you do not quickly move your cursor. Note that scrolling usually stops when you move the cursor and that it should stay like that. I'm only talking about overscroll. I think that WinUI handles this now but I honestly have no idea.
Screenshots

Normal:

Bug:

Version Info

NuGet package version:

Microsoft.UI.Xaml 2.4.0

Windows 10 version
Saw the problem?

Insider Build (xxxxx)

May 2020 Update
Yes

November 2019 Update (18363)
Yes

May 2019 Update (18362)

October 2018 Update (17763)

April 2018 Update (17134)

Fall Creators Update (16299)

Creators Update (15063)

Device form factor
Saw the problem?

Desktop
Yes

Mobile

Xbox

Surface Hub

IoT

Additional context

@Poopooracoocoo We are having trouble reproducing this issue, if you could provide a recording of your repro that might be helpful for us. You can record your screen using Gamebar (invoked by windows key + G) or powerpoint.  Also, what version of Windows are you running on?

@StephenLPeters idk if a screen recording will be very useful but ok. and wow. gamebar and powerpoint are what y'all recommend? i used sharex for this one:

I usually encounter this in the start menu but it happens in any UWP/XAML/WinUI (I don't really know the difference) app.

@RBrid any thoughts ?

@ranjeshj, no idea unfortunately. I think this would require a lengthy investigation.

I'm pretty sure this has to do with scrolling stopping once you move your cursor (as I mentioned in the issue)

Any updates on this issue now that WinUI 3.0 is headed for release?

@ojhad , @ranjeshj , @Poopooracoocoo , I just tried to repro in Windows 11's Settings app, and yes I can easily run into this situation:

using two fingers overpan the ScrollViewer content down with the trackpad.
release the fingers and while the content moves back up quickly click on it with the trackpad.

Result: the content stops instead of animating back all the way!

release the fingers and while the content moves back up quickly click on it with the trackpad.

For me I don't need to click on it. You just need to move your cursor.

Do not close

@Poopooracoocoo, thank you for reporting this. Unfortunately we are not currently investigating WinUI2 issues that are not business or security critical (more on the policy here).
We tried this on WinAppSDK 1.5 / WinUI3 Gallery and the issue does not appear to repro. If you find that it does still repro in WinAppSDK, please comment here and we will revisit.


Refactor brew cask style not to require .rubocop.yml.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[x] Have you successfully run brew tests with your changes locally?

Since rubocop-cask already includes a default.yml, we don't need to have a separate YAML file inside caskroom/cask. This also fixes the rare case that brew cask style fails when caskroom/cask is untapped, this is useful so we can have tests for brew cask style without having caskroom/cask tapped.
--
@Homebrew/cask

Had to add --config /dev/null to make sure that only rubocop-cask's default.yml is used. Not sure if there is a better/official way to force using the default configuration.

@reitermarkus Went ahead and asked for you: https://github.com/bbatsov/rubocop/issues/3647

Merging for now since this works as-is, but will follow up in a separate PR if necessary once we hear back on bbatsov/rubocop#3647.


More build improvements

PR summary
Tweak the .travis.yml file to remove the duplicate "bintray sync" step.
PR Checklist
Please make sure that your PR fulfills the following requirements:

[ ] The commit message follows the Angular Commit Message Guidelines.
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[ ] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Other information

:tada: This PR is included in version 0.15.7 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Added support for SSL connection encryption through secured URL option

Added support to SSL encrypted connections to iSeries systems.
The jt400 library provide a connection pool with 2 different methods:

getConnection()
getSecureConnection()

Using a camel uri option (secured=true or secured=false; default to false) is possible to toggle between the two type of connections. Jt400 library relay on underlying JVM trust cert store to establish the secure connection.

Thanks for this PR. It has been merged. Do you mind closing this?

Closed.


How I can edit file in Alluxio?

Hi collegues!
You develop nice product .... But I faced with litte problem ...
How I can edit file?
By recreating only?  Can I send push request with the function?
A lot of thanks?

Please post questions here: https://groups.google.com/forum/?fromgroups#!forum/alluxio-users


refactor(es6): Upgrade AutomaticPrefetchPlugin to es6

What kind of change does this PR introduce?
Refactor
Did you add tests for your changes?
Existing Tests are passing
If relevant, link to documentation update:
N/A
Summary
update AutomaticPrefetchPlugin to ES6
Does this PR introduce a breaking change?
No

Not sure why Appveyor failed ¯_(ツ)_/¯

Also not sure why it passes now O_o

I restarted the appveyor build. Seems like that one test case is flanky.

@chicoxyzzy Would you be willing to write tests for it in this PR or a merge-dependent separate PR? Otherwise, if not I'll create an issue and someone can pick it up if they want.

@TheLarkInn from what I read in https://github.com/webpack/webpack/issues/1566 and https://github.com/webpack/webpack.js.org/issues/126 I don't understand how to test this plugin :(

@chicoxyzzy Okay so I can help with that I believe. So on Compilation.js there is a .prefetch function which adds a dependency to the moduleChain.
Typically it goes in dependency order but I believe let's you jump the order on certain deps. that may take longer.
This used to be done by using PrefetchPlugin() and manually specifying the dependencies. It looks like in this logics case its finds the lastModules and then calls prefect async.
So in this case, you could add tests to Compiler.test.js (@sokra correct me if I'm wrong).

As the AutomaticPrefetchPlugin depends on being in watch mode I would go with writing a test/watchCases test.

The above feel suggestions feel like integration tests (ie. does the plugin work when called as part of a larger use case). As well as those, it might be nice to have unit tests too - there's an applyPluginWithOptions helper that's just been merged in #3684 (that PR has a test added too as an example of how to use it, or see #3685).
With that helper, you can assert a) does the plugin listen for the expected events and b) do the corresponding event handlers work as expected.

Going to merge and then create an issue for adding test coverage for this plugin.

@chicoxyzzy Thank you!


Add support for dxgkrnl on WSL 2

This is a wishlist request to support GPU compute on WSL 2, in particular CUDA.
Basically I would like support for this https://stgraber.org/2017/03/21/cuda-in-lxd/ with CUDA on WSL 2 with the systemd workarounds to get LXD running https://blog.simos.info/how-to-run-lxd-containers-in-wsl2/ and https://wsl.dev/wsl2-lxd-funtoo/.
I am particularly interested in combining GPU support with the new VM and SPICE features coming in LXD.
CUDA on WSL 2 doesn't use Nvidia drivers on Linux, tools need to detect dxgkrnl for pass-through GPU https://devblogs.nvidia.com/announcing-cuda-on-windows-subsystem-for-linux-2/.
More info on dxgkrnl https://devblogs.microsoft.com/directx/directx-heart-linux/ and<EMAIL_ADDRESS>What can I do to help?

LXD doesn't really do much there. You need to have the GPU show up in /sys/class/drm, if it does, things should just work already. If not, then you need a better kernel :)
For the rest of the story about passing through the libraries and the rest, that's all done through nvidia-container, so if something's broken there, then you'd need to file a bug against that project. Though the logic should be pretty similar in nvidia-docker, so assuming this works, there's a good chance that it would work here too.

lxc query /1.0/resources
And 'find /dev' would be useful

Looking at the kernel doc, this isn't a true GPU so won't work with our normal GPU support or with the Nvidia integration bits nor can it really be made to work with any if it as there is no hardware data showing up.

lxc config device add NAME dxg  unix-char path=/dev/dxg
This should work fine assuming the kernel doc is correct.

Closing as there doesn't appear to be an actual issue for us to fix.
If this does work with /dev/dxg, a tutorial for it would be great to see though. Feel free to post any such content on our forum at https://discuss.linuxcontainers.org

Thank you for looking into this.
I am going to do more research.
Here are the log files previously requested.
find_dev.txt
lxd_query_resources.txt

Interesting, so unix-char for /dev/dxg should definitely work fine for what you're trying to do.
What's interesting is that there's also some kind of GPU visible on the PCI bus though without any usable DRI/DRM entries associated with it and it doesn't appear that /dev/dxg is clearly tied to it either otherwise we could do some more magic in the gpu device type to make it work without unix-char.


Refactor rover apply to reuse an existing terraform plan

At the moment the rover apply is running a terraform plan and apply behind the scene. This issue fix that and propose the following:

if no plan is provided then rover apply will execute rover plan and apply
If a plan is provided as a parameter rover apply will use that plan instead of creating a new one

The scenario we want to cover are

Run rover plan in cd pipelines and store the plan in an artifact repo
Perform a review
Execute the apply based on the plan stored in the artifact

Commands to separate plan from apply and destroy.
 Note -var-folder, -var-file or -var must be removed from the command line.


Verify reddit's smart contracts for Community Points

Reddit uses ERC20 for their subbreddits. It's currently deployed on Rinkeby and they have two distinct ERC20 tokens.
https://www.reddit.com/r/CryptoCurrency has Moon tokens (https://rinkeby.etherscan.io/address/0xdf82c9014f127243ce1305dfe54151647d74b27a)
and
https://www.reddit.com/r/FortNiteBR/ has Brick tokens (no detail where they are).

The deployer created multiple contracts roughly at the same time: https://rinkeby.etherscan.io/address/0x0e95c00dbaa7f7107bb7658d45d53a600547f5c7

I have contacted reddit user that has announced release of Moon tokens when they came out so I am waiting for his response on verifying sources. I could not find sources by googling so maybe they are not open source.


Fix for ObjectUtilities in 5.3.2

Fixes a build error when trying to compile the ObjectUtilities class under UE5.3.2. Should be checked for review before being merged onto main.

Does this issue occur in 5.3 generally? Or just in 5.3.2?

Unsure, haven't tested on builds other than 5.3.2

Manually merged by prior commit


JobDeleter::remove gets stuck when called from tokio::spawn

JobDeleter::remove works fine when called from tokio::main but if I call it in a new thread (tokio::spawn) it gets stuck.
It gets stuck on the first JobDeleter::remove tokio::spawn
Tokio just doesn't want to spawn a new thread or is somehow blocked. I am running everything in multi_thread environment.
I managed to fix it by removing one tokio::spawn and making the function async
pub async fn remove(context: &Context, job_id: &Uuid) -> Result<(), JobSchedulerError> {
        let delete = context.job_delete_tx.clone();
        let mut deleted = context.job_deleted_tx.subscribe();
        let (tx, rx) = std::sync::mpsc::channel();

        let job_id = *job_id;
        tokio::spawn(async move {
            if let Err(e) = delete.send(job_id) {
                error!("Error sending delete id {:?}", e);
            }
        });
        while let Ok(deleted) = deleted.recv().await {
            let ret = match deleted {
                Ok(uuid) => {
                    if uuid == job_id {
                        Ok(())
                    } else {
                        continue;
                    }
                }
                Err((e, Some(uuid))) => {
                    if uuid == job_id {
                        Err(e)
                    } else {
                        continue;
                    }
                }
                _ => continue,
            };
            if let Err(e) = tx.send(ret) {
                error!("Error sending removal result {:?}", e);
            }
            else {
                break;
            }
        }

        let ret = rx.recv();
        match ret {
            Ok(ret) => ret,
            Err(e) => {
                error!("Error receiving result from job deletion {:?}", e);
                Err(JobSchedulerError::CantRemove)
            }
        }
    }

Note: this isn't a proper fix, is hacky and isn't properly tested but it works in my case

Hi @skrcka
Thank you for the report. Lots of these little bugs are due to me trying to mix async with sync.
I'll have a look on the above what you've suggested, and report back here.

v0.9.2 released, have a look.

Thanks @mvniekerk  v0.9.3 did the trick


Update threading

Do NOT merge at this time | discuss
My initial attempts at updating threading apparently missed something (boost thread implementation), which caused compat for windows to fail. This resolves building for windows and appears to work properly in Linux.
This brings us slightly more in-line with Bitcoin not to mention it is a code cleanup because it removes the pthread_t typedef for windows.
This needs significantly more testing before it should be merged.

Has anyone messed with this (@mitchellcash or @PaycoinMaster)

Not yet sorry. Let me get something up and running maybe today, if not weekend

@IngCr3at1on I can't test building for windows but a test build on Ubuntu 14.04 server was fine. Will let it run for a few days.

Have been running this for the past two days and have encountered no issues.
LGTM

I will try to build it for windows and see how it fairs my self.

Rebased and confirmed this does build in gitian.
@PaycoinMaster have you looked into this one at all on Windows?


CursorLine highlighting is sometimes duplicated

Disabling and enabling 'cursorline' while moving the cursor leaves ghost CursorLine highlighting.
Reproduction: echo "test\ntest\n" | vim --clean --not-a-term -c 'exe "nn q :se cul!<CR>" | au VimEnter * cal timer_start(100, {id -> feedkeys("qjqkqj")})' -.

Hi,
I can reproduce this.
This issue occurred in 8.1.0373 or later.
Not occurred in 8.1.0372.
$ git log -1 v8.1.0373
commit 1b7fefcbce5dd2fd337e217d4857b941da3f8bed (tag: v8.1.0373)
Author: Bram Moolenaar<EMAIL_ADDRESS>Date:   Wed Sep 12 22:27:15 2018 +0200

    patch 8.1.0373: screen updating still slow when 'cursorline' is set

    Problem:    Screen updating still slow when 'cursorline' is set.
    Solution:   Fix setting last_cursorline.

--
Best regards,
Hirohito Higashi (h_east)


⚠ Turnos 24x7 has degraded performance

In 2dd6250, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 957 ms

Resolved: Turnos 24x7 performance has improved in f675c65.


Are we still musing CryoNet as a concept

Are we still using cryonet as a concept in our documentation? Check chapter 2 and in particular 2.3.1.

yes, we should continue using CryoNet as a concept, since it's already documented


ADD PROPER IMAGE AND DESCRIPTION FOR THE CARDS IN EVENTS SECTION

Description
I will add proper photos and names for the events section. Please assign me this issue :))
Screenshots

Browser 🥦
Google Chrome
Checklist ✅

[X] I checked and didn't find similar issue
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (blank for no)

These were dynamically created events. We cannot add stuffs to it manually.