"Failed to write report" when "verbose" is set to true

When "verbose" is set to true, conventional-pr fails to write the report to the PR. Response is "422 Invalid request". The response from GitHub API says:
No subschema in "oneOf" matched.
"commit_id", "path", "position" weren't supplied.
"in_reply_to" wasn't supplied.
"commit_id", "line", "path" weren't supplied.
"commit_id", "path", "subject_type" weren't supplied. []

Thanks for filing an issue!
I can reproduce this, seems like the GQL migration isn't going on smoothly. I'll fix this ASAP

Apparently, this is caused by wrong API endpoint when creating a pull request report. Will be fixed in next patch version.

I've released v0.15.2 that fixes this issue as evidenced by this report. If you still have issues regarding verbose reporting, feel free to re-open this issue.
@all-contributors, please add @berkon for bug reporting

Thanks a lot Christopher for your very quick reaction! This really helps us a lot!
Regards,
Bernd


using ModernHttpClient as a replacement for standard HttpClient in Xamarin projects

Hi, thanks again for your work on simple odata..this is an invaluable client especially for mobile!
Wanted to see if its possible to use the Xamarin ModernHttpClient component in place of the standard   HttpClient inside of simple odata client
https://components.xamarin.com/view/modernhttpclient
it's  measurably faster on native platforms because it uses native network implementations
" brings the latest platform-specific networking libraries to Xamarin applications via a custom HttpClient handler. Write your app using System.Net.Http, but drop this library in and it will go drastically faster. This is made possible by two native libraries:
On iOS, via NSURLSession
On Android, via OkHttp 1.5 "

Hi,
Thank you for the suggestion. This might actually work already. ODataClientSettings class has OnCreateMessageHandler property that can be assigned to a NativeMessageHandler as suggested in ModernHttpClient docs. Can you check that this is what you need?

Thanks - I followed your advice and went ahead and created a simple test app that uses both ClientHandlers and tested performance -for refernce I uploaded my code here -it does appear to be faster (saved 5 seconds off an 800 count query) in Xamarin.iOS
see example code here:
https://github.com/ahmedkhan25/NativeODATAClientTester/blob/master/README.md

That's a huge save! Thanks for sharing the code.


Annotation control-plane.alpha.kubernetes.io/leader not registered / documented

This is a Bug Report

Problem:
Kubernetes defines an annotation, control-plane.alpha.kubernetes.io/leader. For example, this annotation is set on ConfigMaps that are being used for legacy leader election (the modern / GA way to do this is using a Lease).
That annotation is unregistered because it doesn't appear inside https://kubernetes.io/docs/reference/labels-annotations-taints/
Proposed Solution:
Register the annotation, by documenting it in
Page to Update:
https://kubernetes.io/docs/reference/labels-annotations-taints/

Additional Information:
/sig architecture
/language en

/assign

/triage accepted


Auto-enable

Do I need to toggle the coverage each time I open a new Atom window?
Maybe there should be a setting to enable it automatically?

Thank you for this feature request. I will think about how I can actualize that idea.

Any chance to have this feature?


Properly parse object types

The attribute is called "type" but we were previously looking for
"obj_type".

Cheers :+1:


Update hugo to version 0.50?

Upon installing hugo on ubuntu after running sudo apt-get update, hugo get's updated to v0.40
How do I run this theme on v0.40 since it is not running right now?
Is there any way to update hugo to V0.50? I can't really find any article on google about this.

The deb for the latest releases can be found at https://github.com/gohugoio/hugo/releases

got it.
Had to install homebrew for ubuntu.I guess there is no other way to update, maybe changing path to new version of hugo would help, that would be a headache. Thanks.

One more thing, how do I remove header ( Academic Install Now) from this theme?


Documentation missing for operators in typescript declaration files

This leads to hovers in vscode only including the type information, rather than the documentation additionally.
RxJS version: 5.5.2
Expected behavior: Documentation for operators in the respective .d.ts files.
Actual behavior: Most operators do not have documentation.
Additional information: I am importing operators like this import { switchMap } from 'rxjs/operators/switchMap'. I've noticed missing documentation on fromEvent, pipe, filter, subscribe, distinctUntilChanged, switchMap.

Hi @keegancsmith please close this issue as the operators:

fromEvent
filter
distinctUntilChanged
switchMap

as well as the pipe and subscribe functions are documented now.


Explain that Rancher's Helm implementation requires users to have permissions to manipulate K8s resources

This issue originated from a Slack conversation: https://rancher.slack.com/archives/C039Y2P93/p1564602941052900

Upstream Helm 2 will deploy the k8s resources with the permissions of the service account that tiller was launched with. So, its not multi-tenant.
Rancher launches an ephemeral instance of tiller with the permissions of the user deploying the catalog app, so that a user cannot gain more access to the cluster through helm than they would otherwise have.

The same is true for multi-cluster apps:

from the UI we allow creation of MCA only if user either has project-member role in the target (which gives CRUD privileges on workloads), or is the owner of the target project’s cluster

This needs to be explained in the catalog documentation https://rancher.com/docs/rancher/v2.x/en/catalog/

Closing this issue because it is addressed by https://github.com/rancher/docs/pull/2145


Don't run client build while starting server_run

We were doing this to create a file at build/index.html that the
milmove serve command needs to read in when it starts up. However,
this index file is not requested in local development as the index
is served by the create-react-app development server.
This commit puts an empty file in that location so that we don't need
to run client_build just to start up the server. In production we don't
invoke the server through make, so this will have no effect in those
environments.
Setup
Checkout this branch, rm -rf build within the project directory, and verify that you can start up the server for local development.
I'm not putting more specific instructions here in an attempt to get folks to test this out using their typical workflows (which vary a bit from person to person).

I think this breaks load testing. Let's please take a look at that first before merging.

@chrisgilmerproj Load testing can start the server with make server_run_standalone, which will run client_build and make the real index available.
We use server_run way more often than we load test, so optimizing for that use case (at the expense of making load testing setup slightly more complicated) seems like the right tradeoff.

@chrisgilmerproj PR here to update docs: https://github.com/transcom/milmove_load_testing/pull/3


Envelope encryption preserve batches within MemoryRecords

Type of change

Bugfix

Description
Closes #855
With these changes:

We preserve the batching of the input MemoryRecords in the encryption filter on the encrypt and decrypt path.
Each batch's metadata is preserved. The records within each batch should be identical.
Control batches are not encrypted, but passed through unmodified.
We introduce an integration test proving that a simple transactionally committed record can be read by a consumer (previously failing due to the control record being exposed to the client as a normal record)

Why?
The encryption filter was not preserving batches within the MemoryRecords it is transforming for a given topic-partition. Consequently we could have done things like:

Removing control batches. We created a single batch with metadata matching the first one in the input and then effectively flatmapped all the batches into it. Meaning that on a transaction commit the user would receive the original record and the control record, where the control record would normally be filtered out by the client and not exposed to poll().
If the control batch was the first batch, we could roll multiple records into a control batch when it's expected to have a single records.
The user may have some reason for compressing batches with different algorithms, we were discarding this and using a single compression scheme.

Generally we want to transparently behave the same as Kafka would, just with our bit of encrypting/decryption transform happening.
Checklist
Please go through this checklist and make sure all applicable tasks have been done

[ ] Write tests
[ ] Make sure all tests pass
[ ] Review performance test results. Ensure that any degradations to performance numbers are understood and justified.
[ ] Make sure all Sonar-Lint warnings are addressed or are justifiably ignored.
[ ] Update documentation
[ ] Reference relevant issue(s) and close them after merging
[ ] For user facing changes, update CHANGELOG.md (remember to include changes affecting the API of the test artefacts too).

Planning to make the tests more exhaustive to check that every one of the batch metadata properties is covered.


Support for React Router 7

Context
What's your version of nuqs?
2.2.2

What framework are you using?

✅ React Router

Which version of your framework are you using?

7.0.1

Description

React router v7 was now released. See: https://reactrouter.com/
It seems react-router-dom is no longer a thing, everything now lives inside react-router. With that said, the existing adapter is no longer compatible with react router 7.
Reproduction

Install react router 7
Attempt to use nuqs' react router adapter

I don't get it, their docs mention it's not a breaking change, but changing the package name is the breakiest of the changes..
I'd say the best way to handle this in nuqs is to have two adapters, one for v6 and one for v7:

nuqs/adapters/react-router: v6 to avoid a breaking change in nuqs
nuqs/adapters/react-router/v7: explicit support for v7
nuqs/adapters/react-router/v6: alias of nuqs/adapters/react-router to help with transition

In the next major update of nuqs, we can then swap what nuqs/adapters/react-router point to.

I don't get it, their docs mention it's not a breaking change, but changing the package name is the breakiest of the changes..
I'd say the best way to handle this in nuqs is to have two adapters, one for v6 and one for v7:

nuqs/adapters/react-router: v6 to avoid a breaking change in nuqs
nuqs/adapters/react-router/v7: explicit support for v7
nuqs/adapters/react-router/v6: alias of nuqs/adapters/react-router to help with transition

In the next major update of nuqs, we can then swap what nuqs/adapters/react-router point to.

Any updates when will this be implemented?

Would you like to open a PR?

Would you like to open a PR?

I have open a PR but this is my very first time opening a PR to an open source project. So feel free to add feedbacks cuz I know there will be a lot

Thanks and congrats for your first PR! ❤

@franky47, could you please share when you could ship this?

@omarkhatibco hopefully this week, now that tests have been merged in #807, they confirmed a few issues:

No support for shallow: true (the default) in react-router based adapters (v6, v7, and Remix)
We could sneak in HashRouter support as noted in #810 (the implementation might be simple, the testing not so much)


feat: Switch to yarn

Codecov Report

Merging #482 (4f0f40a) into master (d842292) will not change coverage.
The diff coverage is 33.33%.

@@           Coverage Diff           @@
##           master     #482   +/-   ##
=======================================
  Coverage   60.96%   60.96%
=======================================
  Files          16       16
  Lines         766      766
  Branches      160      160
=======================================
  Hits          467      467
  Misses        299      299

Impacted Files
Coverage Δ

src/extension.ts
25.35% <0.00%> (ø)

src/caStatusBarProvider.ts
37.50% <50.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 69ac2e8...4f0f40a. Read the comment docs.

Codecov Report

Merging #482 (4f0f40a) into master (d842292) will not change coverage.
The diff coverage is 33.33%.

@@           Coverage Diff           @@
##           master     #482   +/-   ##
=======================================
  Coverage   60.96%   60.96%
=======================================
  Files          16       16
  Lines         766      766
  Branches      160      160
=======================================
  Hits          467      467
  Misses        299      299

Impacted Files
Coverage Δ

src/extension.ts
25.35% <0.00%> (ø)

src/caStatusBarProvider.ts
37.50% <50.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 69ac2e8...4f0f40a. Read the comment docs.


about AttentionNet

Hi, could you share the AttentionNet with me? I want to learn how your net design~

Hi,
By AttentionNet, which part do you refer to? There's no "AttentionNet" in the paper.

Hi,
By AttentionNet, which part do you refer to? There's no "AttentionNet" in the paper.


update tartanhacks link

I went ahead and just added in the link, without the typo (66d93768f2c691bd05d2e95063570280b0d57286)


Merge master into live-based

Docs Build status updates of commit b4a358d:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-Prod/PowerShell-Docs, working directory: W:\vwmc-s, target branch: HEAD, target branch commit: a2d0003a8d3ee5d8b81d8b3c8d0eff048f499b9c, source commit: b4a358d0a65fbc76d2333d1b6f36878ecd68f955.

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.

Docs Build status updates of commit 1fde61b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

developer/format/tablecolumnitem-element-for-tablecolumnitems-for-tablecontrol-format.md
:white_check_mark:Succeeded
View

reference/7/Microsoft.PowerShell.Core/Start-Job.md
:white_check_mark:Succeeded
View (powershell-7)

reference/docs-conceptual/samples/Creating-Get-WinEvent-queries-with-FilterHashtable.md
:white_check_mark:Succeeded
View (powershell-3.0) View (powershell-4.0) View (powershell-5.0) View (powershell-5.1) View (powershell-6) View (powershell-7)

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.


vertices and faces from STL

Hi,
I'm wondering if it is already possible to do the opposite of this: stl from vertices and faces because I would need it for my project but I can't find a method to retrieve the unique points of an STL file and which of them belong to a face.
Thank you

That's part of the internal structure actually.
mesh.points will give you all unique points and mesh.vectors gives you the faces.
Additionally the x, y and z points can be fetched separately as well: https://numpy-stl.readthedocs.io/en/latest/stl.html#stl.base.BaseMesh

Hi,
thank you for the esplantation. I might be missing something. I generated the cube.stl file in the example above and if I read it back with
from stl import mesh
m1 = mesh.Mesh.from_file('cube.stl')

if I read
m1.points
m1.vectors

the first gives me back a 12x9 array of [p0, p1, p2] of all the triangles and not the unique points, while the second a 12x3x3 array with all the points coordinates. I am using the mesh module, you are linking the base module, can I read an existing stl file and retrieve unique points and "connectivity matrix"?
Thank you

Thank you for the clarification. This:
unique_points = np.unique(m.points.reshape((m.points.shape[0] * 3, 3)), axis=0)

did the trick for me. I have put it into a k-d tree so that it is relatively fast to rebuild the connectivity matrix of the faces.
Thank you


Missing separator error while building

When I'm trying to build a example I get the error attached to this issue.
missing.log
The only thing I could find about this is the following open issue:
https://github.com/openframeworks/openFrameworks/issues/5582
Any idea?

Hmmm interesting. Which operating system, IDE and oF version please?
I feel like somehow I have encountered this before.

I'm sorry I was in a rush.
I'm on bleeding edge 64 bit Arch Linux using the latest stable release of ofx. I don't use an IDE. All I did was executing make on the command line in the example directory.

I notice that there's a space on line 44 here : https://github.com/sebleedelisle/ofxLaser/blob/master/addon_config.mk#L44
Could you try deleting the space after the tab and let me know if that helps?

Nope, it has no effect. :neutral_face:

Hmm OK, it's a bit tricky for me to troubleshoot this as I don't use Linux
for oF...
Did you ever use this add-on before or is this the first time you looked at
it? My suspicion is that it may be a problem that is related to my adding
libusb for the LaserDock interfaces. Which interface are you using? Are you
able to remove the libusb dependency and try again? You'll also need to
remove the LaserDock classes from the build. If you need my help with that
let me know and I'll see what I can do.
Seb
On Mon, 9 Sep 2019 at 20:59, Noir<EMAIL_ADDRESS>wrote:

Nope, it has no effect. 😐
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/sebleedelisle/ofxLaser/issues/11?email_source=notifications&email_token=AAA3CEQH57SZG5XLR3IR7SDQI2TJXA5CNFSM4IUVC5T2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6I25OI#issuecomment-529641145,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAA3CEWZ2VFWV3KKAUBMEVDQI2TJXANCNFSM4IUVC5TQ
.

I'm just getting started with oF and I came to this lib because it was advertised on the LaserCube site. The LaserCube is the only device I can test so the libusb dependency is mandatory for me. But I'll still test the effect of removing libusb from the Makefile and the LaserDock classes this evening.

Great, thank you!
On Tue, 10 Sep 2019 at 12:02, Noir<EMAIL_ADDRESS>wrote:

I'm just getting started with oF and I came to this lib because it was
advertised on the LaserCube site. The LaserCube is the only device I can
test so the libusb dependency is mandatory for me. But I'll still test the
effect of removing libusb from the Makefile and the LaserDock classes this
evening.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/sebleedelisle/ofxLaser/issues/11?email_source=notifications&email_token=AAA3CEXCIESOALTETLMSXXTQI55CTA5CNFSM4IUVC5T2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6KWKGY#issuecomment-529884443,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAA3CEQLIK3MVINS3QDI2WTQI55CTANCNFSM4IUVC5TQ
.

I just tried to comment out line 44 of the Makefile and the error persists. I guess removing the LaserDock classes is not necessary to prove that this is not the cause of the problem.

Possibly a silly question but are the other openFrameworks
examples compiling OK? It's very difficult for me to troubleshoot as I have
zero experience using make on linux with this codebase. :(
On Tue, 10 Sep 2019 at 16:31, Noir<EMAIL_ADDRESS>wrote:

I just tried to comment out line 44 of the Makefile and the error
persists. I guess removing the LaserDock classes is not necessary to prove
that this is not the cause of the problem.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/sebleedelisle/ofxLaser/issues/11?email_source=notifications&email_token=AAA3CEWKKBNCOYSIGYPXSJ3QI64VVA5CNFSM4IUVC5T2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6LQUTQ#issuecomment-529992270,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAA3CEUWJSUMWLL7OLJFVODQI64VVANCNFSM4IUVC5TQ
.

Yup, the GUI Example worked just fine but that's the only one I tried until now.
Make is hard to debug and I can relate that supporting a non familiar platform is even harder.
Maybe I'll try the whole oF fuckery with cmake. There's already some work available.

Can you check to see if this is still an issue? I've made several changes recently to improve cross platform compatibility so fingers crossed it is fixed.

Closing due to inactivity and optimism that this is now fixed 😊

Can confirm that this is working now! Thanks a lot :)

Thanks @Noir- !


Metacontroller omitting updated status in subsequent sync

Had to crank up log verbosity to get to the bottom of this, but what I'm seeing is the following sequence of events:

Custom resource created
Metacontrolller adds finalizer to resource
Metacontroller calls sync hook for the firs time, a status field is returned.
Metacontroller PUTs the status to K8s, returns 200 OK

1 webhook.go:64] DEBUG: webhook url: http://stable-provisioning-controller.stable-provisioning-controller/kafka-topic/sync response body: {"status":{"state":"InProgress","message":"This topic was successfully submitted to the Kafka cluster, will check back to see if it was created.","failureType":null,"specId":"test","isCreated":false,"currentSpec":{"eventSource":null,"eventType":null,"privacy":"Non PI","schemas":[],"name":"example-topic-minimal-v4","description":"test4","partitions":1,"replicationFactor":2,"topicConfig":{"cleanup.policy":"delete","max.message.bytes":"1048588","retention.ms":"86400000","retention.bytes":"5000000000"},"producerConfig":{"compression.type":"gzip","retries":"2147483647","enable.idempotence":"true","acks":"all","max.in.flight.requests.per.connection":"2"},"specId":"test","terminationProtection":true,"importExternal":false},"topicDescription":{"activeOnCluster":false,"partitions":[],"activeConfig":{}}},"children":[],"finalized":false,"resyncAfterSeconds":5.0}
I0526 19:59:59.777998       1 round_trippers.go:405] GET https://<IP_ADDRESS>:443/apis/streamz.zillowgroup.com/v1/namespaces/zg-dev-streamz-flink-bootstrap-example/kafkatopics/example-topic-minimal-v4 200 OK in 5 milliseconds
I0526 19:59:59.785136       1 round_trippers.go:405] PUT https://<IP_ADDRESS>:443/apis/streamz.zillowgroup.com/v1/namespaces/zg-dev-streamz-flink-bootstrap-example/kafkatopics/example-topic-minimal-v4/status 200 OK in 6 milliseconds

Metacontroller immediately (20 ms later) calls sync hook again, but updated status is missing on parent

This causes a problem because the second sync call has no way of knowing that an external creation request was already submitted so it will try again and fail because of a duplication.
Note, the resourceVersion field isn't changing between the two syncs, nor is the generation. It simply looks like the exact same sync payload is being submitted without any update to the resource from the first sync.

I would add a follow up question to this. Is it ever ok for a sync hook to inspect the status of the parent resource to determine what to do within the sync?


Updated Nuget Packages

Update all projects to .NET 8
Update all micrososft packages to Latest Version
Update Quartz to 3.8
Update MudBlazor to 6.16

Closing it since no action and have another PR to upgrade to .NET 8


No return for 'eid'.

Hi, The command below doesn't work:
df_qced['FID'] = df_qced['IID']
I think there's a bug:
Bug:
fields = [fields_for_id(f)[0] for f in field_ids] + [participant.find_field(name='p20160_i0')]
Debugged:
 fields = [fields_for_id(f)[0] for f in field_ids] + [participant.find_field(name='p20160_i0')] +  [participant.find_field(name='eid')]

Thank you for catching this. Feel free to make PR.

Thanks @raminsalmas for your help. I had the same issue and your comment helped me to solve it!

@raminsalmas would you mind submitting a PR with this change or pointing me to the notebook where you found this bug so that I can update it please.

Fixed in https://github.com/dnanexus/UKB_RAP/pull/39


Cannot load lambda saved events in AWS Explorer - Test Function section

Describe the bug
AWS Explorer doesn't load lambda saved events in AWS Explorer -> AWS Lambda -> Test Function -> Example Requests section.
To Reproduce

Go to AWS Exlporer
Click on AWS Lambda
Click on a Lambda Function
Go on Test Function section
Open Example Requests

Expected behavior
You should find the request examples you created and saved on the AWS Console website. Instead, you only find the default examples.
Development System:

Windows Version: 11 Pro 23H2 build 22631.3527
Visual Studio Version: Pro 2022 version 17.9.6
AWS Toolkit for Visual Studio Version: <IP_ADDRESS>

Thanks for making this feature request. Did you have Private events or Shareable events in mind here? Private events are only available in the Lambda console, I don't believe there is a way to retrieve these elsewhere.

I mean Private Events. Otherwise, it could useful to create other local private events internally in AWS Toolkit itself.


Confirm your phone number is asked and “Matching can be done only once” error is shown  when the user taps on the “Connect” button from “Connect contacts” while signing with a verified phone number.

Frequency: 100%
Repro App version:  Test Flight build Valora app build  v1.0.0 (17) , Android Valora Mainnet build v1.0.0 (16)
Repro on device: iPhone 7+ (13.3.1), Google Pixel Xl (8.1)
Test Account: Backup Key:<PHONE_NUMBER>.
Pre-condition: Users should have an account key for which they have completed the phone number verification flow.
Repro Steps:

Launch the Application
Complete the walkthrough.
Tap on i have an account.
Enter Full name & test phone number.
Create PIN.
Observe Bug1 Confirm you phone number screen is shown.
Tap on the Start button.
User is redirected to the Connect contact screen.
Tap on “Connect” button.
10 Observe bug2 error message.

Current Behavior: Confirm your phone number is asked and “Matching can be done only once” error is shown
Expected Behavior:  Confirm your phone number should not ask for a verified phone number while signing.
Impact: Users may get frustrated that they have verified the phone number but still phone number verification is asking while sign in.
Attachment: ConfirmPhoneNumberIssue_Signin.mp4 (bug observed at Bug #1 18 sec, Bug #2 48 sec)

Bug 1 has been addressed and I have opened #5099 for Bug 2.

Thanks @tarikbellamine  yes bug 1 is fixed verified on latest build Test Flight build 1.2.0(25) and Android internal build 1.2.0(1004294313).
Now, Your number is already confirmed! is shown now on Confirm phone number screen.
Thanks for raising ticket for bug #2 #5099


Adding Athena OS test cases

What would you like to be added:
We would like to add Athena OS test cases:

test_boot_to_live_environment
test_install_athena_arch_entire_disk_with_defaults
test_install_athena_nix_entire_disk_with_defaults
test_post_install_clean_first_run

Why is this needed:
To implement quicktest for Athena OS in CI/CD workflows to keep the OS periodically monitored for successful installation.

I'll try to check how other checks are made and see if it is possible for me to implement these checks with a PR


Integrating the new proxy feature

API Gateway now has a new feature:
https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-set-up-simple-proxy.html
It is leaving the vast majority of lambada framework obsolete, like method creating logic etc.
Also it'll automatically resolve issues like https://github.com/lambadaframework/lambadaframework/issues/12 https://github.com/lambadaframework/lambadaframework/issues/11
It needs a big refactor but the business value is very big, so it should be implemented as soon as possible.

It removes a significant portion of the code base right?

That's correct. And it means we will be able to support more features with less code.

Any progress on this?

Can't figure out how to programmatically create the lambda proxy.

Of course they also did not add Cloudformation support for that.

So where does that leave us?

Actually my AWS SDK is old.. Checking .60

Got it.

I've been experimenting with this and got a working branch in https://github.com/atramos/serverless-jax-rs/commits/proxy-redux, unfortunately I found that it doesn't really help much and actually makes it harder to fix #57.


Clicking next step in wizard should move to the next page

Select one ...  (check one with "x")
[ ] bug
[ ] feature request
[x ] enhancement

Expected behavior
After completing a page, clicking on the next step (at the left) should move the user to the page for that step (assuming the current page is valid). It should do the same as the NEXT button.
After watching users trial our product, it's been noted they try to hit on the step (on the left of the wizard) to go to the next page, as well as to go backwards.
Actual behavior
Clicking on the next step does not take the user to the page for that step. They have to use the NEXT button. (However, users can click on steps to go backwards, so it seems sensible that they should be able to click steps to go forward too).
Reproduction of behavior
The examples on this page show the behavior: https://vmware.github.io/clarity/documentation/wizards
Environment details

Angular version: 2.4.9

Clarity version: 0.8.9

OS and version: Windows 8

Browser: all

I agree, if we are able to make this interaction available

I'll check to see if it is possible in the new wizard. If not, I'll assign this as an enhancement after the new wizard is out.

I've verified that the new wizard does not allow this. It follows the interaction/behavior of the pre-0.9 wizard.
I will add this to the backlog. I can see where it is confusing. But it will have to be an enhancement we add after the 0.9 wizard is final.


feat: Add possibility to use None as no proxy in tiered proxies.

Using None in input lists for tiered proxy configuration will be interpreted as no proxy. This allows to have for example lowest tier without proxy.
Add tests for it.
Update docs.

Closes: https://github.com/apify/crawlee-python/issues/687

Looking good to me 👏🏽  (I'm glad to see this really was as simple as in the JS version). Have you tested this locally with a crawler (i.e. won't other parts of Crawlee mind the None instead of a proxy URL?) Do we already support this case with new_url_function returning None?

Looking good to me 👏🏽 (I'm glad to see this really was as simple as in the JS version). Have you tested this locally with a crawler (i.e. won't other parts of Crawlee mind the None instead of a proxy URL?) Do we already support this case with new_url_function returning None?

I tested running
...
crawler = BeautifulSoupCrawler(
            proxy_configuration=ProxyConfiguration(tiered_proxy_urls=[[None, None], [None]]),
        )
await crawler.run(["https://crawlee.dev"])
...

I am not sure what you mean by this. Is there a usecase example?
"Do we already support this case with new_url_function returning None?"

Looking good to me 👏🏽 (I'm glad to see this really was as simple as in the JS version). Have you tested this locally with a crawler (i.e. won't other parts of Crawlee mind the None instead of a proxy URL?) Do we already support this case with new_url_function returning None?

I tested running
...
crawler = BeautifulSoupCrawler(
            proxy_configuration=ProxyConfiguration(tiered_proxy_urls=[[None, None], [None]]),
        )
await crawler.run(["https://crawlee.dev"])
...

I am not sure what you mean by "Do we already support this case with new_url_function returning None?". Is there a usecase example?

Ok I think I get it. I looked only at tiered proxies. Currently this will still not work:
crawler = BeautifulSoupCrawler( proxy_configuration=ProxyConfiguration(proxy_urls=[None, None]),)
await crawler.run(["https://crawlee.dev"])

I will make it work consistently for all possible ways of setting the proxies to None

Right, sorry, I might have been confusing - in JS version, we support the newUrlFunction (alternative of new_url) returning null to turn the proxy off. I'm actually not sure if you can pass null in proxyUrls (although it would make sense).

I will make it work consistently for all possible ways of setting the proxies to None

Sounds good! (and hopefully not too much work 🤞🏽 )


Merge and paginate direct delegators

V1: Merging & paginating direct delegations on the delegate profile page
Current solution

Advanced delegators are always on top
Only direct delegators are are paginated
The merge is done on the server side as opposed to the database side
Delegations are sorted by block number as opposed to the balance (delegation size)
Balances for each direct delegation are read from the contract once the delegators are pulled

The challenge
Calculating balances for each delegate on the database side is a very compute intensive operation as it involves aggregating transfer events
Such aggregation takes almost 30 min to run which makes it impractical even if it's to be materialized

PR-Codex overview
This PR enhances delegation functionality by adding pagination and optimization for delegator and delegatee lists.
Detailed summary

Added pagination for fetching delegators and delegatees
Optimized fetching delegators and delegatees
Updated delegation containers to handle paginated data efficiently

The following files were skipped due to too many changes: src/app/api/common/delegations/getDelegations.ts

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

I've been meaning to ask, what are "Advanced Delegates" and "Direct Delegates"?

I've been meaning to ask, what are "Advanced Delegates" and "Direct Delegates"?

Advanced delegatees / delegators are based on Alligator (partial delegation) delegations.
Direct delegatees / delegators are based on the token (direct delegation) delegations


On call of .py file function give Attempted “set” operation on ASN.1 schema object

Hi,
when we are calling .py file function throught Ironpython like c# code. It was working fine but in case of dynamically import module in pythob file like importlib.import_module("test_manager.py") then a system gives  No module found "pyasn1.type.univ".
After installing "pyasn1.type.univ" system gives "Attempted “set” operation on ASN.1 schema object".
This error is a bottleneck of us. Please share some thing on it if you have idea/info about that.
Thanks,
Sandeep
<EMAIL_ADDRESS>

I haven't been able to reproduce this over here. Do you have an simple example I can run to replicate the issue?


Goals for Hamburg

Hi @s-good @BecCowley et al - while we've still got some time, it would be good to set a goal for results to present in Hamburg. Finishing the outstanding tests (#54, #56 & #64) would be a good start, but also having something to present in terms of decision-making performance would be a great thing to be able to report. A machine learning strategy is described in #60, which I'm interested to execute on, but as I mention in #48, we need a larger dataset to train and test on (several thousand profiles).
Let me know what you'd like to show in Hamburg, and we'll try to make it happen.

Hi @BillMills , thanks for your message. I had a thought about the decision-making performance and implemented a simple algorithm that generates a subset of the full range of possibilities (#96). It runs quick but obviously is not so comprehensive. The machine learning strategy would still be interesting as there may be better combinations that the simple method does not find. I also put in a test for the EN background check.
I think that the first priorities for the Hamburg meeting is to get as many tests as possible finished and get some interesting results to show. I hope that we can really inspire the people there to contribute.
I will find the location of the larger dataset and send you in an email. We are concerned there may be some errors in it so don't want to distribute publicly yet.


Rule proposal - no-inline-styles

From https://github.com/Intellicode/eslint-plugin-react-native/blob/master/docs/rules/no-inline-styles.md
The plugin can be installed for a wb project, but it feels hacky...

If the rule would be added to eslint-plugin-react then I feel that it should be removed from eslint-plugin-react-native. Having the same rule existing two times within the ecosystem is just confusing.
That particular rule indeed doesn't seem exclusive to React-Native so it may belong better within this plugin. I assume RN developers do use this plugin for their React linting?
Mostly up to other contributors and the owner of eslint-plugin-react-native to make that decision though.

This would be useful while using styled-components. Would be great to see this in the react plugin rather than the react-native plugin.

Closing as a duplicate of #327

It seems strange to have closed this as a duplicate of #327. #327 has nothing to do with adding this rule to eslint-plugin-react.


Reducer type grammar - preview release

This version allows you to create type records with modifiers. Type aliases and type definitions can be created.
TODO:

Type aliases are not bound to their uses yet. Declarations that use aliases will not execute yet.
Type constructors are not interpreted. Declarations that use constructors will not execute yet.
An actual type checking function that uses a type definition and a value

Modifiers:
min, max, memberOf, opaque are  defined currently.  Each new type modifier is simply a function in the library. New modifiers does not require changes to the parser.
See the unit tests for syntax examples

Codecov Report

Merging #628 (9e4a70c) into develop (7f3caca) will increase coverage by 0.65%.
The diff coverage is 80.00%.

@@             Coverage Diff             @@
##           develop     #628      +/-   ##
===========================================
+ Coverage    52.08%   52.74%   +0.65%
===========================================
  Files           51       52       +1
  Lines         3231     3333     +102
===========================================
+ Hits          1683     1758      +75
- Misses        1548     1575      +27

Impacted Files
Coverage Δ

...ucerInterface/ReducerInterface_ExpressionValue.res
32.53% <25.00%> (-0.39%)
:arrow_down:

...Reducer_Expression/Reducer_Expression_Bindings.res
78.00% <55.55%> (-13.67%)
:arrow_down:

...educer/Reducer_Peggy/Reducer_Peggy_TestHelpers.res
63.15% <63.15%> (ø)

...ucer/Reducer_Dispatch/Reducer_Dispatch_BuiltIn.res
85.91% <85.71%> (-0.14%)
:arrow_down:

...educer_Dispatch/Reducer_Dispatch_BuiltInMacros.res
98.50% <96.77%> (-1.50%)
:arrow_down:

.../Reducer/Reducer_Expression/Reducer_Expression.res
85.36% <100.00%> (ø)

...xpression/Reducer_Expression_ExpressionBuilder.res
95.23% <100.00%> (+0.23%)
:arrow_up:

...ript/Reducer/Reducer_Peggy/Reducer_Peggy_Parse.res
95.34% <100.00%> (+0.22%)
:arrow_up:

...ducer/Reducer_Peggy/Reducer_Peggy_ToExpression.res
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

This looks neat, but I'm curious how it will be integrated in the next stories. Can you give 1-2 examples of how this will be used in practice?  (after the next story or two are done)
Like,
foo(a:number, b: number|string):number = {
  a + b
}

type newType = {a:number, b:number}
add(t:newType) {
  t.a + t.b
}

This looks neat, but I'm curious how it will be integrated in the next stories. Can you give 1-2 examples of how this will be used in practice? (after the next story or two are done)
Like,
foo(a:number, b: number|string):number = {
  a + b
}

type newType = {a:number, b:number}
add(t:newType) {
  t.a + t.b
}

Type declarations are not integrated into implementation syntax yet because it requires a serious reimplementation in the parser because of mutating the existing syntax. Separate declarations for now (time to create an issue for that; natural interleaved declarations) so that we can test typing without having to rewrite the parser yet.
Your examples with the current release would be:
foo:  number => number | string => string
foo(a,b) = a+b
type newType = {a:number, b:number}
add: newType => number
add(t)= t.a + t.b

Those declarations will be used  to build lambda functions and a jump table for internal functions. So everything will be available directly as a lambda function instead of using a huge switch statement.
Declarations in scripts will actually activate input type checking for user functions on call.
Type checking function will be available in FFI so that one can check if data fits the constraints outside rescript.

@OAGr Also note the feature you've wished. Squiggle expressions are legit as constraint parameters
odds1 = [1,3,5]; odds2 = [7, 9]; type odds = number<-memberOf(odds1 + odds2)

This PR doesn't seem to make changes now; the functionality will only come into effect with future stories. I'm going to merge, and do more testing in those future stories.


Exemp file-local types from SA1402 [resolves #3803]

I'm note sure why "Test C# 12 Release Test C# 12" is failing. It doesn't look like this can be fixed in the code.
Can someone please re-trigger the build step?

The quickest way is for yourself to amend the latest commit and force-push.


Don't check target architecture for builder crate to support cross-compiling

Fixes #173

Published together with #175 and #174 as v0.10.6.


sambamba error

I was testing the lcr-modules using a demo snakefile and demo samples. The workflow failed during running the sambamba markdup step. I looked on the log and found that this step failed because it was not able to open the new file:
sambamba-markdup: Cannot open file "/tmp/sambamba-pid2186658-markdup-lhow/PairedEndsInfoqbqa9" in mode "w+" (Too many open files)
For solution, I found that this is a common error and here https://github.com/biod/sambamba/issues/177 it was suggested to increase the number of temporary files by specifying the flag --overflow-list-size 600000 . I tried this and it helped to execute the workflow. I do not think that these many temporary files were needed, but this flag helped to proceed with workflow.
However, to add the flag, I went to the snakefile utils.smk in utils module.

Can you try increasing your ulimit? Specifically, ulimit -n should ideally be a higher number.
https://lcr-modules.readthedocs.io/en/latest/for_users.html#gsc-ulimit-setup

Sure! I'll try it today and will update here on how it worked out.
I was testing it by running on Thanos. The current ulimit -n says 1024. I will do ulimit -n 100000

@BrunoGrandePhD don't you find it concerning that it needs more than 1000 files open at once? My inclination is this points towards it not using memory optimally here and spawns more tempfiles than it theoretically needs but perhaps theres some other reason?

You have to test different ulimits until it works. Sometimes, the admin has set a hard limit that users can go above. For example, I found out that 50000 is the limit on n104 (numbers cluster head node):
# This works
$ ulimit -n 50000

# This doesn't work
$ ulimit -n 50001
-bash: ulimit: open files: cannot modify limit: Operation not permitted

Snakemake spawns many files on its own. It's not clear here whether most files are spawned by Snakemake or Sambamba. Nevertheless, I've asked @whelena to add --overflow-list-size 600000 as a default option for sambamba in the upcoming update to the utils module. See #57.

Sounds good. Thanks


Feature: Being able to compile files into "loaders" which require the actual project file from DU's Lua directory

Investigate the possibility of creating a "loader" during compile time, which is basically a small file that uses require to load the actual script from somewhere else.

I am using symbolic link to achieve that currently.
mklink /D "<DU's Lua directory>/sub-directory" "<src project directory>"

I am using symbolic link to achieve that currently.
mklink /D "<DU's Lua directory>/sub-directory" "<src project directory>"

From what I recall, the idea is to be able to achieve something similar to ArchHUD modular, where you have some files deployed in the DU install directory and loaded by the script.


PowerShell 7.3 sends arguments to native apps differently

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
Please use the attached script test.ps1 and satellite trivial Get-Arg.exe that prints all the arguments.
_221118_1846-ps730.zip
Or use/build from sources below:
test.ps1
& $PSScriptRoot\Get-Arg.exe 1 'a a' '"b"' '\"c\"'

Get-Arg.cs
using System;

internal class Program
{
    static void Main(string[] args)
    {
        foreach (var arg in args)
            Console.WriteLine(arg);
    }
}

Test 1 Invoke by powershell 5.1:
powershell .\test.ps1

Output (good):
1
a a
b
"c"

Test 2 Invoke by pwsh 7.2.7:
C:\Bin\pwsh.7.2.7\pwsh.exe .\test.ps1

Output (good, the same as above):
1
a a
b
"c"

Test 3 Invoke by pwsh 7.3.0:
pwsh .\test.ps1

Output (not good, different from test 1 and 2):
1
a a
"b"
\"c\"

The third and forth arguments are sent differently.
Expected behavior
see above

Actual behavior
see above

Error details
.

Environment data
Name                           Value
----                           -----
PSVersion                      7.3.0
PSEdition                      Core
GitCommitId                    7.3.0
OS                             Microsoft Windows 10.0.19045
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Visuals
No response

The release notes do not mention this change -- https://github.com/PowerShell/PowerShell/releases/tag/v7.3.0
So this might be a bug or unintended change. If this is the intended change then it's worth mentioning because it breaks the behavior existed for years.

See #18614
#18568
and #18554

@jhoneill Thank you. The suggested $PSNativeCommandArgumentPassing = 'Legacy' works as a workaround.
I agree that 7.3.0 works "better". But it clearly breaks things.
The change should be well documented and visible in release notes.
NB In the past, the PS team refused to fix some bugs for avoiding breaking effects like this.


Add script to launch fuzzing continuosly

Continuosly cycle over fuzz targets running each for 1 hour.
I use this script on a server of mine and maybe sharing the script incentives other doing the same

One thing that could have been interesting is "run until there is no coverage update in the last half an hour" to give more time to targets discovering new paths... But I didn't find an option for that in the fuzzer

I would suggest using chrt -i -p 0 $pid rather than nice to deprioritize.

Added chrt inline with the command so the script doesn't need to search for the pid.
I tested a running fuzz process with chrt -p $PID and it looks correct:
pid 2087371's current scheduling policy: SCHED_IDLE
pid 2087371's current scheduling priority: 0


fix: Wallpaper Path on Windows

This is more of a work around:

Paths generated by pywal on Windows aren't properly escaped

This causes JSON.parse to fail since there are unsupported escape sequences.

This change removes the "wallpaper" entry from colors.json if there is a failure.
If there is another failure, it checks to see if any colors are available from the colors cache file, if so it proceeds even though we couldn't get better values from colors.json (with a warning), if not we hard fail.

I've submitted a pull request to pywal as well to attempt fixing upstream.

Thank you very much, I wasn't aware of this issue.
I've already checked your PR and I should be able to push the update by tomorrow.

Sorry for taking more time than what I said, but I finally released the update on the vscode marketplace.


Type agnostic input pointer behavior for spent flagging&double-spend detection

Issue Type
design discussion
Description
This is a proposition of an improvement to the design and abstractions used in ExitGame. Discussed during the workshop with @kevsul @boolafish @pik694 (cc/ @paulperegud).
It could potentially simplify to have bytes32 bitwise-comparison drive both:

output flagging as spent
double spend detection

Then the only place where you're concerned about the contents and semantics of the input pointer (the bytes32) is when you're starting standard exits. You then "remember" the input pointer type. Anyone that signs a tx spending that input pointer type is a double spend to challenge with.
:point_up:  that's type agnostic input pointer type
Right now we're calculating the outputId to do "flagging" part 1., whereas we're using utxoPos as "double spend detection" part. 2. This looks like complexity that can be avoided.
We don't have time to refactor this into an input pointer type agnostic behavior to just compare bytes32 bitwise in both 1. and 2.
It seems like we can upgrade to it though, because the calculation of the "output flagging as spent" bytes32 is up to the ExitGame.

This has been spotted during the discussion the addition of tx inputs into the input challenging APIs (SE challenges, IFE canonicity challenges, IFE input challenges). IIRC, doing this modification could also relieve us of the necessity to deliver those additional inputs.

just leaving some thoughts here:
For next round when we have some breaking changes that need an re-write/refactor to existing ExitGame contract, I think we should evaluate do we still want multiple input pointer type?:

If no, things would be simpler as it would be just outputId. Then the only refactor is we can compare the outputId (or whatever single id schema we decide to keep) with input.
If yes, assuming 1 output type <> 1 input pointer type, we can do the above. We add some complexity on startXXExit part as it needs to dispatch by output type to decide what schema it should be using. However, we would store the id according to input type to storage after it starts. (replacing our current outputId in storage).

One caveat is that currently we rely on WireTransaction.sol  to do that for arbitrary transaction. This means we embed some data (structure) dependency into code. Hopefully we might come up with some cleaner design that decouples the dependency but keeps the abstraction and flexibility.

Closing this as I think there is no action item on this further more. We use this issue to note our discussion down. If there is any, feel free to re-open.


Unable to use scoped packages from a npm or a private registry

Hey, first of thanks for creating this! It solves almost all the use cases i have for scaffolding.
One Problem however is that i am unable to use my generator which is published in th private package registry of github requiring me to use a scoped package name. When trying to use the generator with:
sao --registry=https://npm.pkg.github.com @pixolith/sao-project-generator test
Sao will try to resolve this as a github repository. How can i circumvent this in order to use the package registry provided here? I suppose it also wouldn't work with npm scoped packages.
error Response code 404 (Not Found)
<EMAIL_ADDRESS>
Thanks in advance!

sao --registry=https://npm.pkg.github.com npm:@pixolith/sao-project-generator test

@MDSLKTR
You need to set npm registry global https://npm.pkg.github.com, this way npm knows where find package
 npm config set @pixolith:registry=https://npm.pkg.github.com

This way, when npm search for scope @pixolith package, will try to find in https://npm.pkg.github.com


⚠ Homepage (omg.lol) has degraded performance

In 35d5066, Homepage (omg.lol) (https://8bit.lol/) experienced degraded performance:

HTTP code: 503
Response time: 914 ms

Resolved: Homepage (omg.lol) performance has improved in a2eb3d2 after 12 minutes.


[Question] AWS SecretsManager Push Whole Secret

Is pushing an entire secret to AWS Secrets Manager supported? I'm currently on version 0.9.17 and using the following configuration:
kind: PushSecret
metadata:
  name: aws-sync
  namespace: my-namespace
spec:
  deletionPolicy: Delete
  secretStoreRefs:
    - name: aws
      kind: ClusterSecretStore
  selector:
    secret:
      name: foo
  data:
    - match:
        remoteRef:
          remoteKey: foo

I'm getting this error:
set secret failed: could not write remote ref to target secretstore aws: pushing the whole secret is not yet implemented
Is there a version where this has been implemented?

Hello!
Yes, currently, it's not implemented.
func (sm *SecretsManager) PushSecret(ctx context.Context, secret *corev1.Secret, psd esv1beta1.PushSecretData) error {
	if psd.GetSecretKey() == "" {
		return errors.New("pushing the whole secret is not yet implemented")
	}

Provider features are community driven. If there is a need for it, anyone can take a stab at trying to implement it.
If you don't want to, or can't for some reason, the maintainers will maybe eventually get to it, but there is no guarantee. The priority is based on user engagement.

Ok, I'll open a feature request for this. Appreciate the quick response and code snippet.

@eternalyperplxed please reference the feature request, I have some capacity to work on this.


Implement export with no options

Implemented ft_export(char *str, t_ms *ms), it create the env variable or change it's value if it exist.


Respository Creation

I completed my task which is creation of Respository Creation.

Good Job Jeeva Keep it up ...


CAN'T LOGIN!!

Guys, I joined a room and when I raise my hand to speak they couldn'tgive me the microphoneor be on stage! They asked me to go out n rejoin, I did but I couldn'tspeak, so I thought if I uninstalled the app and re install it will be able to speak, but when I did I couldn'teven log in with my number!!!
I tried many times!

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):

Device: [e.g. Google Pixel]
OS: [e.g. Android 11]
Version [e.g. 1.0.7]

Additional context
Add any other context about the problem here.

Use vpn

You have blocked access. The application is missing an error: We are unable to sign you in. Please try again later.


Opt-in for F# records/unions to have prototype in JS

Add a new attribute [<Prototype(?bool)>] (name discussable).

Default behavior:
A record type has a prototype iff one of the following is true:

It has instance members.
It implements an interface.

With [<Prototype>] (or equivalently [<Prototype(true)>]):
A record type always has a prototype.
With [<Prototype(false)>]:
A record type never has a prototype.

Instance members are compiled into static members with 1 extra first arg.
If it tries to implement an interface, compile error.

Note: if a record type doesn't have a prototype (for any of the above
reasons), then trying to type-test against it throws a compile error.

A tricky part was to uncover and fix an issue with the JSON serializer:
De/serializing records was optimized to use identity function when all fields are the same name, there are no optional fields and no prototype for the record. But on inlined records in union cases when simplified this way, the tag field remained incorrectly on the result (not breaking match/union case get, but breaking JS structural equality). Extra care is needed to remove the tag field in this (and only this) case when deserializing the union.

Implemented and released in Zafir.<IP_ADDRESS>-beta6


Remove smart-file-system from packages/ as moving

Ref https://github.com/symplify/smart-file-system/pull/2

All checks have passed 🎉 @TomasVotruba let's merge ;)
For splitted package, Github action is not running, please activate github action there https://github.com/symplify/smart-file-system/pull/2


partially fix rabbitmq-diagnostics cipher_suites

I'm confident in the fix at line 1344, 1347 ad 1355..
But I don't know what would be the correct fix at line 1373.
Pls advise

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

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

@metas-ts Thank you for signing the Contributor License Agreement!

@metas-ts Thank you for signing the Contributor License Agreement!

The example on line 1373 is now redundant: --format erlang does the same thing in 3.8.

The example on line 1373 is now redundant: --format erlang does the same thing in 3.8.

Thank you!

Thank you!

I've removed the duplicate example in live.

I've removed the duplicate example in live.


An example of RTL support

Hi,
Since Dogfalo hesitates to support RTL (right to left writing such as Arabic), Materialize and AMB do not support RTL.
Here is a very simple example that illustrates how to change directions of writing using materialize_rtl.css.
https://gist.run/?id=3526eacc3ed1e5a7f6b4388099ee177e
Toggle direction button should change the direction of writing. Unfortunately it does not run because of "require is not a function" on Gist.run, though it works in my app. (Does anyone fix it?)
Here is the core part of the example.
    @observable direction;   // rtl or ltr
    directionChanged() {
        if (this.direction === 'rtl') {
            require('./materialize_rtl.css');
        } else {
            require('materialize-css/bin/materialize.css');
        }
        document.getElementsByTagName('body')[0].setAttribute('dir', this.direction);
    }

Get materialize_rtl.css from this repository by @vahid-almasi.
Comment out direction for body, since we use dir attribute of body.
/*body {
	direction: rtl;
}*/

.input-field label {
	right: 0.75rem;
...

The example also illustrates how to combine with aurelia-i18n. Remove comments in locale-manager.js and do this.localeManager.locale = 'ar' for Arabic.  (You need to setup aurelia-i18n in main.js and prepare locale files)
I hope this helps somebody who needs RTL support.

Note that SideNav fails with this approach. The following example does not work, because md-edge is not dynamic.
  <md-sidenav view-model.ref="sideNav"
         md-edge = ${localeManager.direction === 'rtl' ? 'right' : 'left'}"
         md-close-on-click="true">

@HIRANO-Satoshi Cool, thanks! 😃
In theory it should work with Aurelia loader. I can't demonstrate it in the gist right now because aurelia-pal is missing in the bundles.
Like this:
import { bindable, computedFrom, inject, observable, Aurelia, Loader } from 'aurelia-framework';
import { DOM } from 'aurelia-pal';

@inject('Loader')
export class LocaleManager {
  constructor(loader) {
    this.loader = loader;
  }

    @observable direction;   // rtl or ltr
    directionChanged() {
        if (this.direction === 'rtl') {
            this.loadStyle('./materialize_rtl.css');
        } else {
            this.loadStyle('materialize-css/bin/materialize.css');
        }
        document.getElementsByTagName('body')[0].setAttribute('dir', this.direction);
    }

    loadStyle(path) {
      this.loader.loadText(path).then(css => {
        DOM.injectStyles(css);
      });
    }
}

I can add ths to the bridge's contribution/recipes section if you like.

Thanks, but there must be other problems.
row col seems incorrect.
materialize_rtl.css has
.row .col {
	float: right;
}

while materialize.css has
.row .col {
	float: left;
        ...
}

After switching from rtl to ltr, float: right remains.  (I'm not an expert of CSS and HTML.)

It's switching correctly for me in the gist. I've used <require from="./materialize_rtl.css"></require> instead of clicking the button to try that.

Please reopen if still needed


[Falco] Add the option to disable async CRI metadata fetching

/kind feature
/kind chart-release
Any specific area of the project related to this PR?
/area falco-chart
What this PR does / why we need it:
Enables us to use the --disable-cri-async.
Which issue(s) this PR fixes:
None
Fixes #
Special notes for your reviewer:
Checklist

[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] CHANGELOG.md updated

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

d761689 Merge branch 'master' into falco-disable-cri-async

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Annegies: Adding label do-not-merge/contains-merge-commits because PR contains merge commits, which are not allowed in this repository.
Use git rebase to reapply your commits on top of the target branch. Detailed instructions for doing so can be found here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign bencer after the PR has been reviewed.
You can assign the PR to them by writing /assign @bencer in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

falco/OWNERS

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

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

c44d9dd bump chart version

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/approve

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Annegies
To complete the pull request process, please assign bencer after the PR has been reviewed.
You can assign the PR to them by writing /assign @bencer in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

falco/OWNERS

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

/assign @bencer

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

c44d9dd bump chart version
8ede602 Merge branch 'master' into falco-disable-cri-async

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Annegies: Adding label do-not-merge/contains-merge-commits because PR contains merge commits, which are not allowed in this repository.
Use git rebase to reapply your commits on top of the target branch. Detailed instructions for doing so can be found here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

c44d9dd bump chart version

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Annegies
To complete the pull request process, please assign leodido after the PR has been reviewed.
You can assign the PR to them by writing /assign @leodido in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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


Some messengers can't cope with long links

This is slack, for instance. See those [...] - some users are crazy enough to copy that.
This is more of a messenger issue, but if it can be changed on cryptgeon side, that would be nice.

This is def. a usability issue and should be fixed, without sacrifying security

I my opinion we have a few options:

Decrease note id size from 256 to 128bit (or 64bit). This does not affect security in any way.
Decrease both note id and encryption key to 128bit. This is still absolutely safe still but if decreasing the note id is enough this might be the way to go.

Also I would put this behind a flag? Maybe something line NOTE_ID_SIZE. Thoughts?


fix: regression with options.plugins {Function} (webpack.config.js)

https://github.com/postcss/postcss-loader/releases/tag/v2.0.5


Crash upon connecting to game.eoserv.net

System.NullReferenceException: Object reference not set to an instance of an object.
at EndlessClient.World.ApplyWelcomeMessage(WelcomeMessageData data)
at EndlessClient.EOGame.<>c__DisplayClass33.b__2b(Object dlgS, CloseDialogEventArgs dlgE)
at XNAControls.XNADialog.Close(XNAButton whichButton, XNADialogResult result)
at EndlessClient.EOConnectingDialog.d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c__DisplayClass2.b__3(Object state)

This is a known issue due to a race condition when logging in. Usually works after a couple login attempts. Currently I'm unsure the best way to solve it without some complex, convoluted locking mechanism to ensure the welcome packets are never handled out of order.

Confirmed with MonoGame too:
at XNAControls.XNAControl.Update(GameTime gameTime)
at XNAControls.XNAButton.Update(GameTime gt)
at Microsoft.Xna.Framework.Game.<.cctor>b__19(IUpdateable updateable, GameTime gameTime)
at Microsoft.Xna.Framework.Game.SortingFilteringCollection1.ForEachFilteredItem[TUserData](Action2 action, TUserData userData)
at Microsoft.Xna.Framework.Game.Update(GameTime gameTime)
at Microsoft.Xna.Framework.Game.DoUpdate(GameTime gameTime)
at Microsoft.Xna.Framework.Game.Tick()
at MonoGame.Framework.WinFormsGameWindow.RunLoop()
at MonoGame.Framework.WinFormsGamePlatform.RunLoop()
at Microsoft.Xna.Framework.Game.Run(GameRunBehavior runBehavior)
at EndlessClient.Program.Main() on Z:\github.com\ethanmoffat\EndlessClient\EndlessClient\EndlessClient\Program.cs:line 22

Closing due to client rewrite


[gardening] Could not find a command named <...>.out.jitsnapshot

Unexpected exit code 64
DART_CONFIGURATION=DebugX64 out/DebugX64/dart --ignore-unrecognized-flags --packages=/b/s/w/ir/.packages /b/s/w/ir/out/DebugX64/generated_compilations/app_jitk-linux-debug-x64/multitest_ffi_2_vmspecific_leaf_call_test_02/out.jitsnapshot

Could not find a command named "/b/s/w/ir/out/DebugX64/generated_compilations/app_jitk-linux-debug-x64/multitest_ffi_2_vmspecific_leaf_call_test_02/out.jitsnapshot".

https://logs.chromium.org/logs/dart/buildbucket/cr-buildbucket.appspot.com/8846304289428256448/+/u/vm_tests_shard_5/task_stdout_stderr:_vm_tests_shard_5
This is surfacing as an infra failure on the app-kernel-linux-debug-x64  bot, hiding any further status changes.
Test added in https://github.com/dart-lang/sdk/commit/4d5055805fe7b8bf9bc2c0fb5b2cf23f4272e984
We might want to skip the test on the configuration until we figure out what is going on, so that we don't hide further failures under an infra failure.
cc @cskau-g

This is indeed failing for app_jitk-*-debug-*:
$ tools/test.py --build -n app_jitk-linux-debug-x64 ffi_2/vmspecific_leaf_call_test

--- Command "app_jit" (took 03.000033s):
DART_CONFIGURATION=DebugX64 out/DebugX64/dart --snapshot=/.../out/DebugX64/generated_compilations/app_jitk-linux-debug-x64/multitest_ffi_2_vmspecific_leaf_call_test_02/out.jitsnapshot --snapshot-kind=app-jit [...] /.../out/DebugX64/generated_tests/ffi_2/vmspecific_leaf_call_test_02.dart

exit code:
0

stderr:
Could not find a command named "/.../out/DebugX64/generated_compilations/app_jitk-linux-debug-x64/multitest_ffi_2_vmspecific_leaf_call_test_02/out.jitsnapshot".

The test is expected to crash during runtime, and we set up a special handler to catch this during testing.
Though during app_jit this appears to disrupt the snapshot generation (though the command itself exits with code 0), which means the next run step will fail due to the expected snapshot file missing.
I don't immediately know what we can do about this situation, so for now I suggest we approve ffi{,_2}/vmspecific_leaf_call_test/{02,03} on app_jitk-*-debug-*.

201185 adds a Skip for the affected tests.


Additional safeguards needed for "null" values in SCA result type.

Attempted to import a Checkmarx Detailed file with the "sca" result type, but it threw an error when it reached line 447 of the Checkmarx parser. Here is the link to the file.
I was able to get around the issue by adding results[result_type].get("packages", []) or []. I also added the same correction to other areas of the code that were attempting to loop over a list.
Posting example of the SCA result type below.
"sca": {
   "packagesCount": 0,
   "packages": null,
   "containersCount": 0,
   "containers": null,
   "vulnerabilities": {
    "total": 0,
    "critical": 0,
    "high": 0,
    "medium": 0,
    "low": 0,
    "info": 0
   }

Steps to reproduce
Steps to reproduce the behavior:

Upload file with example SCA result type posted above.
See error

@KK7NZY  I was not able to reproduce this. Could you please add an output file to reproduce this? This will also serve as a unittest scan file to stabalize the parser.

@KK7NZY ,
could you please post a valid sample file to reproduce this. Yours is not valid, it is a deformed JSON file. I would help you with a PR if you can post a sample file here.

No feedback for multiple weeks. can we close this @mtesauro ?


chore(ci): report memory usage in bb-native-tests

It was hard to see why Mara's PR took down memory, should make it more clear.

Benchmark results
Metrics with a significant change:

avm_simulation_time_ms (Token:assert_minter_and_mint): 59.8 (-40%)
avm_simulation_time_ms (Token:transfer_public): 48.2 (+62%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Proof generation
Each column represents the number of threads used in proof generation.

Metric
1 threads
4 threads
16 threads
32 threads
64 threads

proof_construction_time_sha256_ms
5,759 (+1%)
1,554 (+1%)
708
752 (-1%)
771 (+1%)

proof_construction_time_sha256_30_ms
11,809 (+1%)
3,181 (+1%)
1,406
1,445 (+1%)
1,469 (-1%)

proof_construction_time_sha256_100_ms
44,096
12,424
5,655 (-1%)
5,542 (-1%)
5,495 (-1%)

proof_construction_time_poseidon_hash_ms
78.0
34.0
34.0
59.0
88.0 (-1%)

proof_construction_time_poseidon_hash_30_ms
1,528 (+1%)
418
200
222 (-1%)
271 (+2%)

proof_construction_time_poseidon_hash_100_ms
5,656 (+1%)
1,521
680 (+1%)
743
754 (+1%)

L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
4 txs
8 txs
16 txs

l1_rollup_calldata_size_in_bytes
708
708
708

l1_rollup_calldata_gas
6,600
6,594
6,600

l1_rollup_execution_gas
611,442
611,587
611,744

l2_block_processing_time_in_ms
759
1,442 (+4%)
2,718

l2_block_building_time_in_ms
10,641 (-1%)
20,777 (+2%)
40,967 (-1%)

l2_block_rollup_simulation_time_in_ms
10,641 (-1%)
20,777 (+2%)
40,967 (-1%)

l2_block_public_tx_process_time_in_ms
8,873 (-1%)
18,806 (+2%)
38,926 (-1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 8 txs.

Metric
3 blocks
5 blocks

node_history_sync_time_in_ms
7,133 (+5%)
10,096 (+5%)

node_database_size_in_bytes
12,746,832
16,908,368

pxe_database_size_in_bytes
16,254
26,813

Circuits stats
Stats on running time and I/O sizes collected for every kernel circuit run across all benchmarks.

Function
time_ms
bytecode_size_in_bytes

GasToken:_increase_public_balance
97.2
8,139

GasToken:set_portal
12.8 (+3%)
2,362

Token:constructor
121 (-1%)
16,400

FPC:constructor
101 (+9%)
9,304

GasToken:mint_public
81.7 (-2%)
6,150

Token:mint_public
60.0 (-1%)
11,720

Token:assert_minter_and_mint
:warning: 59.8 (-40%)
8,028

AuthRegistry:set_authorized
45.2 (+2%)
4,537

FPC:prepare_fee
250 (+8%)
8,812

Token:transfer_public
:warning: 48.2 (+62%)
32,641

FPC:pay_refund
70.5 (-3%)
12,114

Benchmarking:increment_balance
1,041 (+1%)
7,450

Token:_increase_public_balance
12.1 (-4%)
8,960

FPC:pay_refund_with_shielded_rebate
145 (-1%)
12,663

Public DB Access
Time to access various public DBs.

Function
time_ms

get-nullifier-index
0.159 (+2%)

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
256 leaves
512 leaves
1024 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.4 (+1%)
16.7 (+1%)
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.8
31.7
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.600 (+1%)
0.513 (+1%)
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
48.0 (+1%)
76.2 (+1%)
131 (-2%)
248 (+4%)
469

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
159
287
543
1,055

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.491 (+1%)
0.468 (+1%)
0.450 (-1%)
0.448 (+4%)
0.438

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
59.6 (+1%)
112 (+3%)
183 (+1%)
356 (+4%)
693

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
109
207
355
691
1,363

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.503 (+1%)
0.501 (+2%)
0.485 (+1%)
0.481 (+4%)
0.477

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
73.2 (+2%)
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
133
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
0.520 (+2%)
N/A
N/A
N/A
N/A

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
72,017
666,910

Transaction size based on fee payment method
| Metric |  |
| - |  |


ssh password can't be set

Hello there,
I just insalled the latest RasberryMatic downloaded today. Enabling SSH an saving was possible.
Enabling SSH and set a new password leads to a timeout after about 10 min "Die Einstellungen werden gespeichert!"-Message.
Trying to login via Putty (V0.7) gives me an acces denied response even if I'm using the user: root without password after enabling ssh without password.
Is this an issue or just an user mistake?
Thanks in advance for helping.

User problem!

any advice?

Please ask in the homematic fora this is a big/issue tracker! Thanks

thank you.


update kpanda download page

Fix typo
Remove 0.20 link to download since its checksum is incorrect and the suffix -dev is only for test

cc @Douglas235 and @qiupingdai

cc @justedennnnn


Add functionality for creating new journals from cmd

See issue #330.

This is great! I have three requests:

Can you rebase this against 2.0.0-rc1?
can we change the parameters to only take the name (we'll then ask for the path)
Can we unify the creation process with jrnl.install.install?

Afterwards happy to merge this in for the 2.0 release!

Sure:

I will close this PR and open a new one to 2.0-rc1.
OK, that's easy.
What do you mean by unify? Do you mean change a bit the interface of jrnl.install.install, so it can take an additional argument (the journal name), and then call it from run if -create argument is provided?


wordpress: need the ability to edit stuff

i have updated my wordpress profile. now i need the ability to edit stuff.

Okay, copied over all your old posts and you can now add and edit stuff.


Replace jQuery .delegate() with .on()

jQuery has discouraged the use of .delegate()
in favor of .on() since the release of jQuery 1.7 in 2011.
In jQuery 3, .delegate() has been deprecated and
is up for removal. So jquery-migrate complains
about the usage of .delegate().
This change will replace delegate() with on(). That
also means jQuery versions < 1.7 will not be
supported, but supposedly it should be more
important to support the current version of jQuery
than to support the 6 year old version.
(At least in future releases?)

This would be nice to have. I was about to do the same...

Can someone please review and merge this PR as it becomes somewhat of a nuisances #824.

@Craga89 - How would you feel about merging this? It has quite a few upvotes 😉?


Make "Body" part of the question optional?

via questions/D1xK2
Is your enhancement request related to a problem? Please describe

I run a community Q&A site where the questions are often very simple such as "Where do I get my dog groomed?". They fit into the Title of the question and there is no need to elaborate on it further in the body. However because the Body is a required field, people are often struggling as to what to put there.

Describe the solution you'd like

Can we introduce a feature where the Body field is optional and people can ignore it if they feel the Title captures the question sufficiently?

@fenbox check this. A hack / workaround for this. Better than suggested solution.

Check this. A hack / workaround for this. This has a design advantage. Works same as how feed works in any social media apps

@surapuramakhil This workaround misses question level features such as bookmark and gamification (losing its nature).
@fenbox Should it be made configurable for admins? Like
Allow "Short questions"?
Description: Question content is not a required field for a short question.

And I'd like to fix this issue after the solution is settled.

@Octobug I agree what you mean. But users can do bookmark of a topic as such. As i this hack would work great if there would only up to 50 questions.
@fenbox @Octobug just my suggestion is if Q&A are too small then overhead of switching will be too much (1 page for each question). Having something like feed would be quite useful.

@Octobug I prefer the second one.
Add "Min question body length" in Settings->Write. Default value is 6, and 0 means optional.


Fix condition filtering bug in elbv2.create_rule()

Fixes https://github.com/spulec/moto/issues/3090, I wasn't able to get tests running locally, but I verified it fixes the repro script from the linked issue. The problem is that the values returned from _condition.items() are ('field', 'path-pattern'), ('path_pattern_config._values.member.1', '/test_repo/test_branch/*'), so the key doesn't actually start with "values.member"

Coverage remained the same at 94.393% when pulling 757fc0f1f3de94d619f36331daac759866ad57b5 on adriank-convoy:create_rule_bug_fix2 into e033d6cd68bdabba7710ebea62822ca2f1b4dd5d on spulec:master.

Yeah, sorry was just being lazy... I got tests running locally, and modified the existing test_handle_listener_rules unit test to add in a condition using PathPatternConfig (which also caught the same bug when updating a rule).

This is now available as of moto >= 1.3.15.dev917


when the first menu is clicked, I want to startActivity

when the first menu is clicked, it becomes infinite loop. how can I fix this problem
@Override
public void onNavigationDrawerItemSelected(int position) {
        switch (position) {
            case 0: // giriş ekranını göster
                this.startActivity(new Intent(this, Arama.class));
                break;
            case 1: //detaylı arama
                this.startActivity(new Intent(this, DetayliArama.class));
                break;

...

Remove the selectItem call from the onCreate method on the fragment

it's works. thank you.


See Ghost characters when fixing Hebrew alignments

Reported by users - See Ghost characters when fixing Hebrew alignments. Could to be due to issue when word is changed in original language after alignment. See comments below.
This will need the steps to reproduce
This will need testing notes
Example:

Note that in the example יְנֻגָּֽעוּ is duplicated and some letters are replace with ? symbol

Notes from user:
Has anyone seen this happen before? Notice in the aligning window the Hebrew word with 2 question marks in it instead of Hebrew letters and also notice that it is effecting the highlighting in gE since the phrase "they do" should be highlighted in the UST but is not. What is strange is that a few minutes ago it was a different Hebrew word in this verse that had two question marks in it but the question marks switched words after refreshing. I just refreshed again and now the question marks are staying in the same Hebrew word and effecting the highlighting. I’m stumped.

Developer Note:

it looks like this will have to be fixed in word-aligner-rcl

@birchamp @elsylambert - In tCore we do alignment validation each time the repo is opened.  So at a minimum It looks like we need to improve the alignment validation in GWE.  Words that are not in the original language should not appear in the alignment tool.

@birchamp @elsylambert - In tCore we do alignment validation each time the repo is opened.  So at a minimum It looks like we need to improve the alignment validation in GWE.  Words that are not in the original language should not appear in the alignment tool.

Moved the validation and migration work into a separate issue https://github.com/unfoldingWord/gateway-edit/issues/565 .  Will leave this open until we can reproduce the corruption of the alignments seen.

@elsylambert @danielklapp - Maybe move this to QA watch.  This should not happen again.  But since we haven't been able to come up with a way to reproduce, it could reappear.


Add update circleci config script

Short description
#
Add script to update circleci config.
Proposed changes

Add command to package.json.
Side effects

None.
Resolved issues

Fixes: None.

@steffenkleinle please add not testable label the the pr if there is no issue with this label

Sorry if I am missing something, but we also have this script in ./scripts/circleci-update-config.sh What is the difference to run it here or there? Or it's triggered automatically from package.json somewhere?

Ahh, good to know, I did not now about that one. I personally like to run it like this because I use the command in Integreat too, but we can also just close and reject this if you feel like this is too much of a duplicate.


SegmentedButtonGroup background is being ignored

When creating rounded buttons the background of the left-overs is from the parent and not the SegmentedButtonGroup!
setting android:background="COLOR" on SegmentedButtonGroup doesnt change this fact

I somewhat understand the problem you're describing, but do you mind giving me a simple example I can rerun. (Sounds like we should only need the layout XML for the example)
Thanks!

Thanks for responding so quickly!
`
<com.addisonelliott.segmentedbutton.SegmentedButtonGroup
android:id="@+id/buttonGroup_lordOfTheRings"
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:layout_gravity="center_horizontal"
android:layout_marginTop="32dp"
android:layout_marginBottom="8dp"
android:background="@color/whiteOriginal"
android:elevation="4dp"
app:borderColor="@color/whiteOriginal"
app:borderWidth="6dp"
app:divider="@color/transparent"
app:dividerPadding="10dp"
app:dividerWidth="1dp"
app:layout_constraintBottom_toTopOf="@+id/bankIbanNextButton"
app:layout_constraintEnd_toEndOf="parent"
app:layout_constraintStart_toStartOf="parent"
app:layout_constraintTop_toBottomOf="@+id/bankIbanNameEditText"
app:layout_constraintVertical_bias="0.0"
app:radius="360dp"
app:selectedBackground="@color/orangeOriginal">
            <com.addisonelliott.segmentedbutton.SegmentedButton
                android:layout_width="0dp"
                android:layout_height="match_parent"
                android:layout_weight="1"
                android:fontFamily="@font/grotesque_regular"
                android:padding="18dp"
                app:selectedTextColor="@color/whiteOriginal"
                android:background="@color/whiteOriginal"
                app:text="Betaalrekening"
                app:textColor="@color/grey"
                app:rounded="true"
                app:textSize="18sp" />

            <com.addisonelliott.segmentedbutton.SegmentedButton
                android:layout_width="0dp"
                android:layout_height="match_parent"
                android:layout_weight="1"
                android:background="@color/whiteOriginal"
                android:fontFamily="@font/grotesque_regular"
                android:padding="18dp"
                app:rounded="true"
                app:selectedTextColor="@color/whiteOriginal"
                app:text="Spaarrekening"
                app:textColor="@color/grey"
                app:textSize="18sp" />

        </com.addisonelliott.segmentedbutton.SegmentedButtonGroup>`

No problem. So at first glance, I don't see anything wrong with the code, so it seems like a valid bug.
I'm a bit confused that I have a similar test case as shown here:

The interesting thing is that it is showing the white background and not the gray one.
Anyway, I'll play around with this within the next few days to see if I can reproduce. There's a possibility that maybe the device you're using is having problems. I'll keep you up to date with my findings.

Alright, I figured it out. Took me a little while to understand what was going on.
The issue is that you have app:rounded="true" in the SegmentedButton's. This does not do what you think it does and it is what is causing the problem.
Here is the PR for the rounded attribute, added in April: https://github.com/addisonElliott/SegmentedButton/pull/12
Here's the relevant line of code to explain what rounded is doing: https://github.com/addisonElliott/SegmentedButton/blob/master/library/src/main/java/com/addisonelliott/segmentedbutton/SegmentedButton.java#L971
So, the rounded attribute will round both sides of the button regardless of it's position. So the buttons were being rounded and that's why the background was bleeding through, so to speak. The purpose of the rounded attribute is for buttons with a transparent background. Look at this example in the sample code:

This is the use case for the rounded attribute.
So, with that in mind, I think there are some improvements that could be made to the documentation, such as:

[ ] Add another animated image on README showing this new test
[ ] Maybe link to example layout XML in README for animated preview images
[ ] Update README, particularly the rounded attribute row with better detail of what this parameter is for.

I'll be leaving this issue open for others to reference until PRs are submitted for the following changes. I won't have time to do this so I'll leave it for anyone that is interested.

Thanks for replying and sorry for my late response. I have some deadlines, if I have time left I will look at fixing this problem in the code. For now a work-a-round is to have a viewgroup container with the background color as desired. That way I can still have rounded buttons!

No problem. I'm a bit confused by your message. In terms of code/functionality, what you are wanting can be done, the primary issue is the confusion in documentation.
So there should be no need for a workaround to get your code working. Does that make sense?
The functionality you want is shown in the examples with Yes/No/maybe just with different styling and such.

ah, you are right using "app:selectedButtonRadius" fixed this issue for me! Thanks for responding man !

Added additional documentation in 3.1.5


S3 Compression

Is your feature request related to a problem? Please describe.
No.
Describe the feature you'd like
We want to support what RedShift Spectrum supports. (usually Snappy).
https://docs.aws.amazon.com/redshift/latest/dg/c-spectrum-data-files.html
Additional context
Add any other context or screenshots about the feature request here.

Compressed files in S3 are supported. File formats and supported compression algorithms are shown in the following table.
https://docs.aws.amazon.com/databrew/latest/dg/supported-data-file-sources.html


bazel-remote: 2019-01-12 -> 2020-01-29

Motivation for this change
Update it and fix it.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[x] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Notify maintainers
cc @Profpatsch @abbradar

@GrahamcOfBorg build bazel-remote

fails:
ERROR: An error occurred during the fetch of repository 'in_gopkg_yaml_v2':
   failed to fetch in_gopkg_yaml_v2: 2019/09/16 04:23:06 unrecognized import path "gopkg.in/yaml.v2"
Loading: 15 packages loaded
Loading: 21 packages loaded
ERROR: /private/tmp/nix-build-bazel-remote-2019-08-21-deps.drv-0/source/config/BUILD.bazel:3:1: no such package '@in_gopkg_yaml_v2//': failed to fetch in_gopkg_yaml_v2: 2019/09/16 04:23:06 unrecognized import path "gopkg.in/yaml.v2"
 and referenced by '//config:go_default_library'
INFO: Call stack for the definition of repository 'com_google_cloud_go' which is a go_repository (rule definition at /private/tmp/nix-build-bazel-remote-2019-08-21-deps.drv-0/output/external/bazel_gazelle/internal/go_repository.bzl:122:17):
 - /private/tmp/nix-build-bazel-remote-2019-08-21-deps.drv-0/source/WORKSPACE:76:1
ERROR: An error occurred during the fetch of repository 'com_google_cloud_go':
   failed to fetch com_google_cloud_go: 2019/09/16 04:23:28 unrecognized import path "cloud.google.com/go"
ERROR: /private/tmp/nix-build-bazel-remote-2019-08-21-deps.drv-0/output/external/org_golang_x_oauth2/google/BUILD.bazel:3:1: no such package '@com_google_cloud_go//compute/metadata': failed to fetch com_google_cloud_go: 2019/09/16 04:23:28 unrecognized import path "cloud.google.com/go"
 and referenced by '@org_golang_x_oauth2//google:go_default_library'
ERROR: Evaluation of query "deps(//:bazel-remote)" failed: errors were encountered while computing transitive closure
Loading: 33 packages loaded
Loading: 33 packages loaded
builder for '/nix/store/3awlmls2m253bhlnj251p40qfqsprvr9-bazel-remote-2019-08-21-deps.drv' failed with exit code 2
error: build of '/nix/store/3awlmls2m253bhlnj251p40qfqsprvr9-bazel-remote-2019-08-21-deps.drv' on 'ssh://builder@sarov-mac' failed: builder for '/nix/store/3awlmls2m253bhlnj251p40qfqsprvr9-bazel-remote-2019-08-21-deps.drv' failed with exit code 2
builder for '/nix/store/3awlmls2m253bhlnj251p40qfqsprvr9-bazel-remote-2019-08-21-deps.drv' failed with exit code 1
cannot build derivation '/nix/store/1avgb7fkpg46sir5kq7fc1r6cx131kr0-bazel-remote-2019-08-21.drv': 1 dependencies couldn't be built
error: build of '/nix/store/1avgb7fkpg46sir5kq7fc1r6cx131kr0-bazel-remote-2019-08-21.drv' failed

@GrahamcOfBorg build bazel-remote

ping @Profpatsch

@GrahamcOfBorg build bazel-remote

Great!


fix: search all configs regardless of staged files

This PR searches for all configurations inside the git repo, instead of only those matching the staged files. It's currently only used for the hasMultipleConfigs check, but in the future it will also be used to fix "parent directory" globs, which are currently not working.
Without this fix, hasMultipleConfigs would be false if you only staged files matching a single config, and thus the CWD would be wrong.

Need to add some more tests:
--------------------|---------|----------|---------|---------|-------------------
File                | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
--------------------|---------|----------|---------|---------|-------------------
All files           |     100 |    99.68 |     100 |     100 |
 searchConfigs.js   |     100 |       80 |     100 |     100 | 26

What do you think about this, @okonet ?

Ping @okonet, do you think you'd have time for checking this out? I haven't really had time to take it further either, but merging this would fix the most clear issue we have currently in monorepo setups.

I hope you are well @okonet.
In the meantime, if someone from the community wants to open this exact same pull request, I am able to approve and release it. Unfortunately with the current repo settings, I'm not able to self-approve my own changes.

Thanks, @okonet! I'll try to migrate the config grouping to the new logic next.


Update links and reorder logos

Moved FAR logo first to reflect majority of authors now have FAR not CHAI affiliation.
Link directly to arXiv paper, remove our local PDF copy (be more DRY).

src/content.ts also links to /pdfs/go_attack_paper.pdf in a few places. It links to some specific sections of the paper (e.g., it links to appendix E.2) whose numberings have changed between the current arXiv version vs. the more up-to-date /pdfs/go_attack_paper.pdf, so we'll want to update the arXiv version before deleting /pdfs/go_attack_paper.pdf

Ah thanks for catching the arXiv vs PDF discrepancy, I didn't realize the PDF was more up to date. Yeah, let's aim to update arXiv release soon and put this PR on hold until then.

Went ahead and just made some changes myself. Links are now updated and logos are smaller.

Thanks for pushing this over the finish line, sorry I went AWOL on this PR.


Passing props to root instance

Version
2.4.2
Reproduction link
https://jsfiddle.net/1madr5ze/
Although putting it into data works: https://jsfiddle.net/t1t4teeo/
Steps to reproduce
Declare a prop for the root application instance.
Pass the prop to the <div> that represents the root of the app.
What is expected?
The root app should have the props data.
What is actually happening?
The props data isn't showing up.

That's expected behaviour, it's simply not supported.

You may be interested in https://vuejs.org/v2/api/#propsData

@posva https://jsfiddle.net/jmf5f70k/
I have tried it but not sure anything changed after changing it from props to propsData. :/
Although from the docs it seems that propsData is pretty much data but without using the function. :)
It seems that a popular workaround for this is either using this.$root.$data which people say works but isn't the best practice and the other one is creating a child component which you treat as your root component and then throwing all the children there, so that it's sort of looks like:
<div id='#app'>
	<app :all-the-root-props-go-here="">
		<component1 :some-of-the-root-props=""></component1>
		<component2 :some-of-the-root-props=""></component2>
		<component3 :some-of-the-root-props=""></component3>
		<component4></component4>
	</app>
</div>

So then after looking at that I'm thinking ... why is the root instance different from the component instances when it's essentially just a component itself? :)
I guess that main use I see in this is ... avoiding duplication of my PHP code where I declare the same prop in multiple places (components), and only putting the actual value once for the root and for the children to use the root's prop value and not having it declared again (so say I want to change the code for setting that prop value, currently I need to change all my components to the new code, whereas if I only pass the prop once to the root then there's just one place to change it).

So then after looking at that I'm thinking ... why is the root instance different from the component instances when it's essentially just a component itself? :)

Props are for passing data form a parent component to a child component.
The main instance is the root component, it has no parent component.
HTML Attributes on the element you mount to are not props.
Hence, making this work as you want it to would require extra code to act as if the mount element was some kind of parent component.

I would advise you to just go with the main child component. It really is an established pattern.


Enable interactive brush and drop down selection

This PR enable an interactive brush and add a drop down menu
to allow selections between all pushes and complete ones.

Running version here: https://pr32-c36ca11-dot-step189-2020.uc.r.appspot.com/