Flip transition

Related to #155
Last transition from VCTransitionsLibrary Flip:

Take a direction (only Left / Right are working right now, Top / Bottom are broken, but didn't find why yet)
Default gesture is the Pan
No custom parameters

I'm gonna take another look later for the Top / Bottom, but I think we can already merged this for the next release (since the main directions are working)

👍  thank you very much, please merge it.
BTW: I am working on the Pinch gesture, there maybe a small bug in Portal animator when uses with gesture interaction, I am looking at it. Once it is done, will submit a PR and release 2.3. It will be a big release since all VCTransitionsLibrary are in IBAnimatable now. 👯

Awesome. Let me know if you need any helps before the next release, that one is a huge one 🎉

@tbaranes thanks, I am still working on the PortalAnimator, once it is done, we will have a big release 🎊

BTW, I was just thinking that I didn't update the README for each new animator 😢
Another though, shouldn't we divide the README in subREADME, with (or not) a summary in the main README? Right now, the main one is getting really big and harder to navigate in.

Yes, may move API section out of README.md thoughts? @tbaranes


Encoding in setup.py file

Hi
When installing from source it throws the following error:
File "setup.py", line 12
SyntaxError: Non-ASCII character '\xc5' in file setup.py on line 12, but no encoding declared; see http://python.org/dev/peps/pep-0263/ for details
I'm using UTF-8 encoding.
According to docs, adding # coding=latin-1 fixes it.

Merged

And i double checked, the encoding of the file is definitely utf-8. Since I am Czech the latin encoding messed up my name in PyPi repository.


Add serde support

Closes #14

Yes, please merge. We need it too.

This PR implies you're transmitting Incoming<Msg> and Outgoing<Msg> over a wire, I'm not sure it's a right thing to do. Incoming and outgoing structs contain information such as sender/recipient and whether it's p2p or broadcast message. However, this information should rather be implied from specific delivery implementation.
For instance, if delivery is implemented as p2p network, sender ID would be implied from IP address of sender (or rather, from which specific channel this message came from).
Also, while parties send Outgoing<Msg>, they expect to receive Incoming<Msg> which just simply have different set of fields, so you can't just serialize and send Outgoing and then receive and deserialize Incoming, it just won't work.
Would you elaborate on why you need serde traits on incoming and outgoing?

This PR implies you're transmitting Incoming<Msg> and Outgoing<Msg> over a wire, I'm not sure it's a right thing to do. Incoming and outgoing structs contain information such as sender/recipient and whether it's p2p or broadcast message. However, this information should rather be implied from specific delivery implementation.
For instance, if delivery is implemented as p2p network, sender ID would be implied from IP address of sender (or rather, from which specific channel this message came from).
Also, while parties send Outgoing<Msg>, they expect to receive Incoming<Msg> which just simply have different set of fields, so you can't just serialize and send Outgoing and then receive and deserialize Incoming, it just won't work.
Would you elaborate on why you need serde traits on incoming and outgoing?

The use of IP address won't work in our use case, because, we have generalized a Network trait that does not care about the underlying method of data transmission (e.g., we might use in-memory channels for tests). Thus, IP addresses are not guaranteed.
To this effect, since we have generalized the underlying method of transmission and have forwarding to/from the network source and the channels in memory that receive/transmit these payloads, we do need to be able to serialize these incoming/outgoing structs otherwise our codebase will get ugly in a hurry and we'd be forced to maintain our own fork going forward.

This PR implies you're transmitting Incoming<Msg> and Outgoing<Msg> over a wire. I'm not sure it's the right thing to do.

It doesn't have to be sent over a networking wire; we have a wrapper over that already that handles the inner message $M$.

Would you elaborate on why you need serde traits on Incoming and Outgoing?

Currently, we have one channel for outgoing and incoming messages. We split this single channel into different channels with different kinds of message types. They all share the single channel under the hood (did I just explain multiplexing?). We use an enum to unify all these kinds of channels, which requires all messages to be serializable.
From your explanation, if you're saying we shouldn't send these messages as-is and instead send the inner message $M$, that's fine, but we'd still need $M$ to be serializable, right?
Thank you!

The use of IP address won't work in our use case

IP addresses was an oversimplified example. Delivery implementation shouldn't rely on them. Instead, in case of p2p network, it should establish secure p2p channels by performing a cryptographic handshake. Then, identifying the channel from which message is received should give information about the sender.

To this effect, since we have generalized the underlying method of transmission and have forwarding to/from the network source and the channels in memory that receive/transmit these payloads

I'd say that generalized network framework should leave a functionality of identifying sender (and figuring out other metadata) up to the implementation. Having an option of sending Incoming<M> and Outgoing<M> over the wire means that, for instance, sender field has to be trusted. That's not a secure implementation of delivery, if malicious party can pretend being any other party by changing sender field of transmitted message.

As such, this PR does not necessarily imply that these structs will literally be transferred over the wire, but they may be depending on our chosen network implementation.

Yes, it doesn't force anyone to use serde, but having it in public API could suggest one that it's fine to send incomings/outgoings as is. If we're merging this PR, I need to identify a legit use-case for serialization, and update documentation to be clear when serialization should and should not be used.

From your explanation, if you're saying we shouldn't send these messages as-is and instead send the inner message $M$, that's fine, but we'd still need $M$ to be serializable, right?

Yes, M certainly need to be serializable.

If it helps, I can give you an example of how we implemented delivery (it's not opensourced tho). We have a relay server that relays messages between parties. Parties know each other (signing) public keys in advance. In order to do any communications, they first connect to delivery server and perform cryptographic handshakes and establish per-protocol encryption keys. Then, when they send a p2p message, they send encrypted M, own public key, and a signature. When other party receives p2p message, it verifies the signature, then it looks up sender public key and determines which signer index is associated with the sender. Then it just decrypts M and reassembles Incoming<M> from the information it already knows.
Any other secure implementation of delivery I can think of (no matter if it uses p2p network/relay server/blockchain/..) should be using similar approach, it would likely replace signer index by signer identity (public key) and transmit the signature as well. Or other valid approach I can imagine would be implying sender ID from the secure channel which produced the message. Either approach doesn't need incoming/outgoing to be serializable.

Closing for now as not needed.


remove pushlogs

Since we have the public pipeline, this is no longer needed

This can delete the checkstatus.sh and the continue on failure of the earlier wait, because all that only exists for this log pushing step.


chore: add arcus issue templates

Adds common Arcus issue templates to repo.
Closes #97

@ALaks96 , I'll merge this, as @SamVanhoutte is still code-owner till the end of this month. 😉 .


Docs

Adds an example which would close #168. Any edits or suggestions welcome!

@geoffrey-eisenbarth, I have to apologize. I overlooked this pull request. Are you still interested in working on it?

@palewire Sure, but if I recall correctly, this is really a companion PR to PR #156.
I've been using my Upsert fork in production for the past 10 months and it's been good to me. I can't tell if you're interested in the PR or not: I'd love to have it merged in, and would be willing to do any work necessary to get it there. I believe my PR was failing some relatively minor GitHub Actions validations and I didn't know how to re-trigger them in order to make sure all is good.
Would you be willing to review it? Thanks!


Toaster incorrectly calculates its height in promise variant when a long title is passed to it

https://github.com/emilkowalski/sonner/assets/134369911/5025608d-3605-4739-b9d6-35acafba1852

What version are you using?

Which version are you using?

0.4.0

This was fixed in #75 but it looks like it's not in npm. Locally everything seems to work
https://github.com/emilkowalski/sonner/assets/48808846/e8db72f8-d085-4194-9728-a1aa67dc95fd

This should be fixed in the newest release!


Improve issue templates

Closes #170
Drops the following in favor to labels:

Tags from the title
Checkboxes list of libs

Can be further improved with additional automation by someone willing to take the effort. (IMHO I think it's too early to do that now)

One thing is that this doesn't nudge toward selecting the initial labels (the previous way was annoying because it created tasks which didn't fit in, but having the "nudge" to select initially was nice).
I think https://github.com/marketplace/actions/advanced-issue-labeler could fit the bill to do both...


HOTT-2297: Adds presentation of quota closed and transferred event

Jira link
https://transformuk.atlassian.net/browse/HOTT-2297
What?
I have added/removed/altered:

[x] Added view for quota closed and transferred events
[x] Removed 20 day requirement for fetching pending safeguard quota events
[x] Adds specs for new transfer events

Why?
I am doing this because:

This is required to enable transfer events to present in the quota modal UI
The requirement of showing pending balance events only within 20 days of the definition period no longer applies

Pending balances still show regardless of the current date of the safeguard quota:

Transferred balances show when there is an event and we're past the closing date

Transferred balances on the closing date


Feature/sync with gfdl

Description
At long last, we are synchronized with GFDL's latest and greatest ...
This PR is using a the main branch of mom6, with a manual merge of the ecbuild/cmake work from our old branch dev/master-ecbuild to feature/main-ecbuild. My current plan is to rename the mom6 feature/main-ecbuild branch to main-ecbuild and make it the new mom6 default branch. Open to suggestions if you have a better idea, but merging into dev/master-ecbuild is full of conflict that I don't really want to resolve (we're ~7000 commits behind!). The power of procrastination.
Many thanks to @liuxiao37k for sorting out the problems on the BGC side.
Despite the many mom6 commits, there were few issues:

Minor adjustment in Geometry
A restart checksum that we need to by-pass
Using ustar in the model test fails in the forecast of length 0. This will be addressed in a different PR, ustar has been removed from the list of model variables that the model is tested with
All the test output that have a dependency on the model advance step have been adjusted

Issue(s) addressed
closes #480
Testing
What compilers / HPCs was it tested with? gnu/container
Dependencies
Requires the use of the  mom6 feature/main-ecbuild branch.

@guillaumevernieres Successfully built on Hera with -DENABLE_OCEAN_BGC=ON and -DENABLE_OCEAN_BGC=OFF, failed when -DENABLE_OCEAN_BGC if not specified in the ecbuild command line.
My bad. I think we just need a simple fix here, replacing
if ( NOT ${ENABLE_OCEAN_BGC})
with:
if ( NOT ENABLE_OCEAN_BGC)
which should solve the problem.

@guillaumevernieres Successfully built on Hera with -DENABLE_OCEAN_BGC=ON and -DENABLE_OCEAN_BGC=OFF, failed when -DENABLE_OCEAN_BGC if not specified in the ecbuild command line.
My bad. I think we just need a simple fix here, replacing
if ( NOT ${ENABLE_OCEAN_BGC})
with:
if ( NOT ENABLE_OCEAN_BGC)
which should solve the problem.

@liuxiao37k , you can submit a simple bugfix PR online and take credit for it!

Dependencies:
Require a simple bugfix in this JCSDA-internal/MOM6 PR.

Dependencies:
Require a simple bugfix in this JCSDA-internal/MOM6 PR.

Tested with the bugfix PR on Orion using INTEL compiler. Passed.

@travissluka , I wouldn't mind getting rid of that work soon ...

@guillaumevernieres update the bundle in soca-science as well to point to that mom branch ?

@guillaumevernieres update the bundle in soca-science as well to point to that mom branch ?

Yes, that too. There's also that MOM6 PR that needs a review.


Alumni Tracking System

Project Description
a system that brings college graduate together and connected
dynamic with various features
this template was originally created for mits gwallior hackathon
now i would like to contribute it to open source
implies backend + user friendly UI and dashboard
Stack:
And in order to tick the check box just but x inside them for example - [x] like this. Please delete options that are not relevant.

[] Html
[] CSS
[] JavaScript
[x] ReactJS
[x] NodeJS

/assign


Configurable kubernetes version when creating alibaba ACK

Add support to configure kubernetes version when using the Alibaba ACK driver. Currently, we always create clusters in default kubernetes version.

driver pr merged. need a pr to update rancher/rancher

@loganhz you are validating this one?

Fixed in rancher/rancher:master 02/20
steps to validate:

Select a k8s version in UI
Create the cluster
Now the version is populated in the API
The correct k8s version is created in aliyun console


Communication: Improve performance when loading messages

Checklist
General

[x] I tested all changes and their related features with all corresponding user types on a test server.
[x] I chose a title conforming to the naming conventions for pull requests.

Server

[x] Important: I implemented the changes with a very good performance and prevented too many (unnecessary) database calls.
[x] I strictly followed the server coding and design guidelines.
[x] I added pre-authorization annotations according to the guidelines and checked the course groups for all new REST Calls (security).
[x] I documented the Java code using JavaDoc style.

Motivation and Context
Loading messages was slow due to too many database queries. This PR significantly improves performance without changing any functionality.
Steps for Testing

Prerequisites:

2-5 Students

Write a couple of messages (with replies) by different students in a course in one or multiple channels
Make sure that loading the messages in the communication (select the corresponding channels in the filter) and messages tabs works correctly (there should be no difference to the previous state)
If you test locally: Have a look at the logs and notice the performance difference

Testserver States

[!NOTE]
These badges show the state of the test servers.
Green = Currently available, Red = Currently locked

Review Progress

Performance Review

[ ] I (as a reviewer) confirm that the client changes (in particular related to REST calls and UI responsiveness) are implemented with a very good performance
[ ] I (as a reviewer) confirm that the server changes (in particular related to database calls) are implemented with a very good performance

Code Review

[ ] Code Review 1
[ ] Code Review 2

Manual Tests

[ ] Test 1
[ ] Test 2

I think I tested different scenarios 😊 having 50 messages from different authors.
Good that you did a test with 1000 messages. Thank you!
I guess I know where the issue comes from. There is a limitation when it comes to pagination and fetching one to many relationships. Hibernate cannot do this in the database and then needs to fetch all messages which fulfill the filter, potentially 1000, now with additional data due to the left joins. Then, pagination is done in Java.
This is also shown in the logs with a corresponding warning.
What we can do is the following: only load the ids of the posts within the paginated query and then fetch all left joins for those ids in a second query and add it into the corresponding page. This should do the trick. I'll try this approach and also look for other cases where we do pagination with left joins because this is then something that we should mark as bad practice in the coding guidelines.

@bassner @az108 thanks for testing. I could fix the issue. Now, it should also be faster in the scenario: thousands of messages by the same user. I tested it in the same course on TS6 and it is faster or has at least the same timing with significantly less database requests.

To make the testing more realistic, we should consider to have the following in the channel:

Messages by different users
Answers to messages in threads (notice, there is no paging here, so having a really really long answer thread can potentially be a performance drain, but this is out of scope for this PR)
Reactions by different users

Can we directly remove the unused endpoints and methods?

I wanted to do that in a follow-up, because it's out of scope. I just wanted to mark them here, so we don't forget it

Tested locally performence I recorded the average performences in the log:
createMessage took in average 45ms with 100 messages in a channel
createAnswerMessage took in average 35ms with 100 replies in a channel
Filtering, searching and channel tabs seems to be working fine


pay later option redirects back to checkout start

Hi,  thanks for this.  I am having an issue with checking out wholesaler and using pay later.  When continuing should bring you to the summary page but will go back to the cart.  The order does actually  go through.  What I am finding that at this point of failure the customer needs to log out and then back in to process or even checkout again.  so maybe has to do with session not getting closed.  i am using 0.60.1 version.
Thanks

#15 resolves this issue and should be closed although it only applies to 0.70.x.  I believe the code should work with 0.60.x as well.
The issue was that the state_machine states were not stepped through with the appropriate callbacks and therefore the orders were not cleanly completed.

Awesome thanks for checking this out @tavon

great i will try on 0.60.4


Foundation: avoid temporary file leaks on Windows

Correct the implementation of _NSCleanupTemporaryFile to use MoveFileExW with MOVEFILE_COPY_ALLOWED to prefer to use file renames rather than copy and delete.  This should improve performance in the general single volume case and still allow the correct behaviour in the multi-volume scenarios using CopyFile and DeleteFile.
Thanks to @darinf for identifying the test case with 65535 temporary files!

@swift-ci please test

@swift-ci please test

@swift-ci please test Windows platform

@swift-ci please test Windows platform

@swift-ci please test Windows platform

@swift-ci please test Windows platform

@swift-ci please test Windows platform

@swift-ci please test

@swift-ci please test Windows platform

woo!


Pass context to the title, url and check.

It would be useful to pass context to the functions such as title, url and check so that we can extract information from the context as well as the request.
Something like:
check(request, context)

Hi.
Sorry, but this is a non-trivial change and I'm not going to attempt it.  If you feel it's something you think you can do cleanly I would consider a PR -- but it would require that no backwards compatible changes get introduced.
If you really need access to the context you can also always just reconstruct it in your callable:
from django.template import RequestContext
def my_check(request):
    context = RequestContext(request)

Yeah, I was probably going to look at attempting this in the not too distant future. I was going to check to see if the callable supports more than one argument as pass context as a secondary argument (to preserve backwards compatibility).

You'd probably need to do something like use inspect.getargspec to see if the callable supports a parameter named context and then supply it.


[SPARK-32540][SQL] Eliminate the filter clause in aggregate

What changes were proposed in this pull request?
Spark SQL supported filter clause in aggregate, for example:
select sum(distinct id) filter (where sex = 'man') from student;
But sometimes we can eliminate the filter clause in aggregate.
SELECT COUNT(DISTINCT 1) FILTER (WHERE true) FROM testData;
could be transformed to
SELECT COUNT(DISTINCT 1) FROM testData;
SELECT COUNT(DISTINCT 1) FILTER (WHERE false) FROM testData;
could be transformed to
SELECT 0 FROM testData;
Why are the changes needed?
Optimize the filter clause in aggregation
Does this PR introduce any user-facing change?
'No'.
How was this patch tested?
New test.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31747/
Test PASSed.

Test build #127125 has started for PR 29369 at commit 3db6f32.

Test build #127125 has finished for PR 29369 at commit 3db6f32.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/127125/
Test FAILed.

Test build #127130 has started for PR 29369 at commit 2596448.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31752/
Test PASSed.

Test build #127130 has finished for PR 29369 at commit 2596448.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/127130/
Test FAILed.

retest this please

Test build #127133 has started for PR 29369 at commit 2596448.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31755/
Test PASSed.

Test build #127133 has finished for PR 29369 at commit 2596448.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/127133/
Test FAILed.

retest this please

Test build #127140 has started for PR 29369 at commit 2596448.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31762/
Test PASSed.

Test build #127140 has finished for PR 29369 at commit 2596448.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/127140/
Test FAILed.

Test build #127181 has started for PR 29369 at commit d97bcfb.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31803/
Test PASSed.

Test build #127181 has finished for PR 29369 at commit d97bcfb.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/127181/
Test FAILed.

Test build #127184 has started for PR 29369 at commit 6d02c8f.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31806/
Test PASSed.

Merged build finished. Test PASSed.

Test build #127184 has finished for PR 29369 at commit 6d02c8f.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/127184/
Test FAILed.

retest this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31807/
Test PASSed.

Test build #127186 has started for PR 29369 at commit 6d02c8f.

Test build #127191 has started for PR 29369 at commit 45c7205.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31813/
Test PASSed.

Test build #127193 has started for PR 29369 at commit 87ec2ee.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31814/
Test PASSed.

Test build #127186 has finished for PR 29369 at commit 6d02c8f.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/127186/
Test FAILed.

Test build #127191 has finished for PR 29369 at commit 45c7205.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/127191/
Test PASSed.

Test build #127193 has finished for PR 29369 at commit 87ec2ee.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/127193/
Test PASSed.

Test build #127262 has started for PR 29369 at commit f81da69.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31882/
Test PASSed.

Test build #127262 has finished for PR 29369 at commit f81da69.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/127262/
Test FAILed.

retest this please

Test build #127278 has started for PR 29369 at commit f81da69.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31898/
Test PASSed.

Test build #127278 has finished for PR 29369 at commit f81da69.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/127278/
Test PASSed.

Test build #127302 has started for PR 29369 at commit e4b4c5a.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31921/
Test PASSed.

Test build #127302 has finished for PR 29369 at commit e4b4c5a.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

retest this please

Test build #127312 has started for PR 29369 at commit e4b4c5a.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/127302/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31931/
Test PASSed.

Test build #127318 has started for PR 29369 at commit a9d5042.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31937/
Test PASSed.

Test build #127320 has started for PR 29369 at commit 690e326.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31939/
Test PASSed.

Test build #127312 has finished for PR 29369 at commit e4b4c5a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/127312/
Test PASSed.

Test build #127318 has finished for PR 29369 at commit a9d5042.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/127318/
Test PASSed.

Test build #127320 has finished for PR 29369 at commit 690e326.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/127320/
Test PASSed.

thanks, merging to master/3.0!

@cloud-fan Thanks for your help!


AttributeError: 'function' object has no attribute 'setter'

Getting the following issue when running the latest commit
Traceback (most recent call last):   File "main.py", line 22, in <module>     from coapthon.server.coap import CoAP   File "/home/pi/dev/captivate_server/dataViz/CoAPthon3/coapthon/server/coap.py", line 9, in <module>     from coapthon.layers.blocklayer import BlockLayer   File "/home/pi/dev/captivate_server/dataViz/CoAPthon3/coapthon/layers/blocklayer.py", line 5, in <module>     from coapthon.messages.request import Request   File "/home/pi/dev/captivate_server/dataViz/CoAPthon3/coapthon/messages/request.py", line 2, in <module>     from coapthon.messages.message import Message   File "/home/pi/dev/captivate_server/dataViz/CoAPthon3/coapthon/messages/message.py", line 12, in <module>     class Message(object):   File "/home/pi/dev/captivate_server/dataViz/CoAPthon3/coapthon/messages/message.py", line 656, in Message     @size1.setter AttributeError: 'function' object has no attribute 'setter'

This issue is solved by the following request: https://github.com/Tanganelli/CoAPthon3/pull/39/commits/9be6559133ba7ba07f23fdaa3ffccf37b3fc8f36


We can't detect porn link by title or etc
And as i say, this is just library for extract & search file, so I'm not responsible for the link she/he inputs
Im waiting for another issue💪, Happy hacktoberfest!


signalSorter new feature + normalizeMovie, loadMovieList, Miji loading, etc. improvements

signalSorter now has a new feature to allow users to use a frame slider to select specific frames to investigate with movie aligned images. Additional improvements to UI, back-end.
Change Miji to not load GUI or interactive interface in loadBatchFxns or other parts of the package. Reduce it popping-up and causing user issues.
normalizeMovie now has a crop function so FFT can be run on movies with NaN borders more easily.
runCvxSetup added to centralize CVX loading.
caxisChange added to allow changing of colorbar when changing caxis.
playMovie now has a slider
Added h5info support and support for 16-bit float types.
Change dataset reading to handle HDF5 where main dataset is not a top-level directory OR it is a sub-directory that is not the only dataset in the HDF5.
readHDF5Subset - Add correction for frame order. Select hyperslab in HDF5 makes blocks in sorted order, so after reading the explicit offset ordering is not the original unsorted order.
Improved input dialog boxes in several class methods, more user friendly.
signalSorter legend is now a figure, no more pop-ups!
Fix for downloading/installing/loading Fiji on OSX/Unix systems.
Misc. other changes.

Merging.


Updated pc.AnimationComponent#_stopCurrentAnimation to stop all the c…

…lips and reset pose
I confirm I have signed the Contributor License Agreement.

Can we get a bit more description around what this fixes and why it was a problem?

Can we get a bit more description around what this fixes and why it was a problem?

_stopCurrentAnimation did not reset the pose of the glb animation which can be seen when deselecting a glb animated entity in the Editor.


RVV 1.0 integration

This PR contains a riscv64-cross.txt file for cross compiling for riscv64 architecture on meson, a cloud-v-pipeline file for CI flow and a Makefile for running tests on RISC-V architecture (since meson fails when binaries are transferred from one platform to the other).
The Makefile contains a very simple bash script in it which executes are the executables in the build/test directory recursively and prints out the passed and failed tests' count along with the total number of counts.
Currently the passing criteria is that all the binaries should be executed with a return code of zero. Else the test will fail.
A complete CI build of this is present at: https://dash.cloud-v.co/blue/organizations/jenkins/simde-fork/detail/simde-fork/48/pipeline/51/

@mr-c I made all the changes you requested. Also, previously, the compile was for riscv64 default target (which was rv64gc). Now I have added -march=rv64gcv to compile for vector extension. For rv64gc, all 2002 tests pass but for rv64gcv, tests are failing. I think it is because of some porting issue in the source code macros.

Thank you @alitariq4589 ; this is exactly the sort of issue we want to catch using CI!
@zengdage @howjmay @eric900115 Can you look into this compile errors when using -march=rv64gcv and also why they weren't caught with our existing testing?
Details

../test/arm/neon/../../../simde/arm/neon/types.h:54:5: error: unknown type name 'fixed_vint8m1_t'
   54 |     fixed_vint8m1_t sv64;
      |     ^~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:67:5: error: unknown type name 'fixed_vint16m1_t'
   67 |     fixed_vint16m1_t sv64;
      |     ^~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:80:5: error: unknown type name 'fixed_vint32m1_t'
   80 |     fixed_vint32m1_t sv64;
      |     ^~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:93:5: error: unknown type name 'fixed_vint64m1_t'
   93 |     fixed_vint64m1_t sv64;
      |     ^~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:106:5: error: unknown type name 'fixed_vuint8m1_t'
  106 |     fixed_vuint8m1_t sv64;
      |     ^~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:119:5: error: unknown type name 'fixed_vuint16m1_t'
  119 |     fixed_vuint16m1_t sv64;
      |     ^~~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:132:5: error: unknown type name 'fixed_vuint32m1_t'
  132 |     fixed_vuint32m1_t sv64;
      |     ^~~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:145:5: error: unknown type name 'fixed_vuint64m1_t'
  145 |     fixed_vuint64m1_t sv64;
      |     ^~~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:175:5: error: unknown type name 'fixed_vfloat32m1_t'
  175 |     fixed_vfloat32m1_t sv64;
      |     ^~~~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:188:5: error: unknown type name 'fixed_vfloat64m1_t'
  188 |     fixed_vfloat64m1_t sv64;
      |     ^~~~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:196:5: error: unknown type name 'fixed_vuint8m1_t'
  196 |     fixed_vuint8m1_t sv64;
      |     ^~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:203:5: error: unknown type name 'fixed_vuint16m1_t'
  203 |     fixed_vuint16m1_t sv64;
      |     ^~~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:210:5: error: unknown type name 'fixed_vuint64m1_t'
  210 |     fixed_vuint64m1_t sv64;
      |     ^~~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:230:5: error: unknown type name 'fixed_vint8m1_t'
  230 |     fixed_vint8m1_t sv128;
      |     ^~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:251:5: error: unknown type name 'fixed_vint16m1_t'
  251 |     fixed_vint16m1_t sv128;
      |     ^~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:276:5: error: unknown type name 'fixed_vint32m1_t'
  276 |     fixed_vint32m1_t sv128;
      |     ^~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:297:5: error: unknown type name 'fixed_vint64m1_t'
  297 |     fixed_vint64m1_t sv128;
      |     ^~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:318:5: error: unknown type name 'fixed_vuint8m1_t'
  318 |     fixed_vuint8m1_t sv128;
      |     ^~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:339:5: error: unknown type name 'fixed_vuint16m1_t'
  339 |     fixed_vuint16m1_t sv128;
      |     ^~~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:360:5: error: unknown type name 'fixed_vuint32m1_t'
  360 |     fixed_vuint32m1_t sv128;
      |     ^~~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:381:5: error: unknown type name 'fixed_vuint64m1_t'
  381 |     fixed_vuint64m1_t sv128;
      |     ^~~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:427:5: error: unknown type name 'fixed_vfloat32m1_t'
  427 |     fixed_vfloat32m1_t sv128;
      |     ^~~~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:448:5: error: unknown type name 'fixed_vfloat64m1_t'
  448 |     fixed_vfloat64m1_t sv128;
      |     ^~~~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:456:5: error: unknown type name 'fixed_vuint8m1_t'
  456 |     fixed_vuint8m1_t sv128;
      |     ^~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:463:5: error: unknown type name 'fixed_vuint16m1_t'
  463 |     fixed_vuint16m1_t sv128;
      |     ^~~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:470:5: error: unknown type name 'fixed_vuint64m1_t'
  470 |     fixed_vuint64m1_t sv128;
      |     ^~~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:781:11: error: unknown type name 'fixed_vint8m1_t'
  781 |   typedef fixed_vint8m1_t    simde_int8x8_t;
      |           ^~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:782:11: error: unknown type name 'fixed_vint16m1_t'
  782 |   typedef fixed_vint16m1_t   simde_int16x4_t;
      |           ^~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:783:11: error: unknown type name 'fixed_vint32m1_t'
  783 |   typedef fixed_vint32m1_t   simde_int32x2_t;
      |           ^~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:784:11: error: unknown type name 'fixed_vint64m1_t'
  784 |   typedef fixed_vint64m1_t   simde_int64x1_t;
      |           ^~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:785:11: error: unknown type name 'fixed_vuint8m1_t'
  785 |   typedef fixed_vuint8m1_t   simde_uint8x8_t;
      |           ^~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:786:11: error: unknown type name 'fixed_vuint16m1_t'
  786 |   typedef fixed_vuint16m1_t  simde_uint16x4_t;
      |           ^~~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:787:11: error: unknown type name 'fixed_vuint32m1_t'
  787 |   typedef fixed_vuint32m1_t  simde_uint32x2_t;
      |           ^~~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:788:11: error: unknown type name 'fixed_vuint64m1_t'
  788 |   typedef fixed_vuint64m1_t  simde_uint64x1_t;
      |           ^~~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:789:11: error: unknown type name 'fixed_vfloat32m1_t'
  789 |   typedef fixed_vfloat32m1_t simde_float32x2_t;
      |           ^~~~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:790:11: error: unknown type name 'fixed_vfloat64m1_t'
  790 |   typedef fixed_vfloat64m1_t simde_float64x1_t;
      |           ^~~~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:792:11: error: unknown type name 'fixed_vint8m1_t'
  792 |   typedef fixed_vint8m1_t    simde_int8x16_t;
      |           ^~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:793:11: error: unknown type name 'fixed_vint16m1_t'
  793 |   typedef fixed_vint16m1_t   simde_int16x8_t;
      |           ^~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:794:11: error: unknown type name 'fixed_vint32m1_t'
  794 |   typedef fixed_vint32m1_t   simde_int32x4_t;
      |           ^~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:795:11: error: unknown type name 'fixed_vint64m1_t'
  795 |   typedef fixed_vint64m1_t   simde_int64x2_t;
      |           ^~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:796:11: error: unknown type name 'fixed_vuint8m1_t'
  796 |   typedef fixed_vuint8m1_t   simde_uint8x16_t;
      |           ^~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:797:11: error: unknown type name 'fixed_vuint16m1_t'
  797 |   typedef fixed_vuint16m1_t  simde_uint16x8_t;
      |           ^~~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:798:11: error: unknown type name 'fixed_vuint32m1_t'
  798 |   typedef fixed_vuint32m1_t  simde_uint32x4_t;
      |           ^~~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:799:11: error: unknown type name 'fixed_vuint64m1_t'
  799 |   typedef fixed_vuint64m1_t  simde_uint64x2_t;
      |           ^~~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:800:11: error: unknown type name 'fixed_vfloat32m1_t'
  800 |   typedef fixed_vfloat32m1_t simde_float32x4_t;
      |           ^~~~~~~~~~~~~~~~~~
../test/arm/neon/../../../simde/arm/neon/types.h:801:11: error: unknown type name 'fixed_vfloat64m1_t'
  801 |   typedef fixed_vfloat64m1_t simde_float64x2_t;
      |           ^~~~~~~~~~~~~~~~~~

Full log: https://dash.cloud-v.co/job/simde/15/consoleFull

@zengdage Thanks for providing me the link to the patch changelog. I added the compilation flag which you requested. However, it is unrecognized in the RISC-V 64 GNU GCC cross-compiler. Also, I am using RISC-V 64-bit GNU cross compiler (nightly build pre-release version April 12, 2024 which is the latest version in pre-release list) on x86 because compiling the source code on K230 kendryte is very time-consuming because of the lack of compute resources on it.
Also, I have tried searching for fixed_vint8m1_t string but could not find it in the https://gcc.gnu.org/pipermail/gcc-patches/2024-March/648204.html link. Maybe they did not add it yet?

@alitariq4589 please look at that, https://godbolt.org/z/r7Ksbo1oP , I think it's the usage of fixed_vint8m1_t in the latest gcc.

@zengdage Thanks for referring me to the link. The compiler version in the environment is 13.2.0. I will update the compiler to 14.1.0 and will try to compile again.

I have updated the riscv gnu toolchain version to 14.1.1 and also updated the CI files. Previous errors are resolved but there are some new errors in the log (full log available at: https://dash.cloud-v.co/view/SIMDe/job/simde/25/console).

@mr-c @zengdage bumping this PR.

@zengdage Any thoughts?
riscv64-unknown-linux-gnu-gcc -march=rv64gcv_zvl256b -mrvv-vector-bits=zvl -mabi=lp64d -Ofast -Itest/arm/neon/addv-emul-c.p -Itest/arm/neon -I../test/arm/neon -I.  I try to use the gcc 14.1 in Compiler Explorer, https://godbolt.org/z/4qzrdPs7v , and it can compile addv.c successfully.
According to the google result,
<EMAIL_ADDRESS>https://github.com/riscv-software-src/riscv-tests/issues/9
I think the issue have been fixed in gcc 14.1,  so may you check that is something mismatched in your configurations.

@mr-c @zengdage I have run the build with -O3 and without any optimization at all.

The build with -O3 failed during compile stage. The complete log is available at this link

The build without any optimization flags passed at the compile stage but the tests failed during execution in the kendryte k230 RISC-V compute instance. The complete list of failed tests are available in test.mak.log. The complete log is available at this link

I have not yet configured the pipeline to publish the test.mak.log file so following is the test.mak.log file.
test.mak.log

Update: I have updated the pipeline file to archive artifacts of builds.
The latest build is #39 where you can check the test.mak.log file in the Build Artifacts section.

Update: I have updated the pipeline file to archive artifacts of builds.
The latest build is #39 where you can check the test.mak.log file in the Build Artifacts section.

Huh, that is a lot of errors. I guess they need reporting upstream. Do you get the same errors without  -march=rv64gcv_zvl256b -mrvv-vector-bits=zvl -mabi=lp64d ?

Update: I have updated the pipeline file to archive artifacts of builds.
The latest build is #39 where you can check the test.mak.log file in the Build Artifacts section.

Huh, that is a lot of errors. I guess they need reporting upstream. Do you get the same errors without  -march=rv64gcv_zvl256b -mrvv-vector-bits=zvl -mabi=lp64d ?

@mr-c I tried building and running this just for RV64GC in the past (i.e. without vector extension flags) and it ran successfully. The build log is available at private CI pipeline here


Remove more AWT related code

The rememberCursorPositionProvider only uses a few awt related things but breaks a lot of compatibility.
val component = LocalLayerContainer.current
val cursorPoint = remember {
    val awtMousePosition = MouseInfo.getPointerInfo().location
    convertPointFromScreen(awtMousePosition, component)
    IntOffset(
        (awtMousePosition.x * component.density.density).toInt(),
        (awtMousePosition.y * component.density.density).toInt()
    )
}

It will break the tooltip, cursor position popup.
It breaks when using OpenGL or another non awt environment with ComposeSence.
https://github.com/HumbleUI/JWM/issues/172
Can we have a LocalMouseLocationProvider with CompositionLocal and set defaults to the code above in rememberCursorPositionProvider?
related to: https://github.com/JetBrains/compose-jb/issues/652

In 1.4.0 rememberCursorPositionProvider doesn't rely on AWT anymore, so it should fine with non-awt environment

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


The dependency AFNetworking (~> 3.0) is not used in any concrete target

I am on mac OS X EI Capitan, version 10.11.3 and using Xcode version 7.2.1,
I created a pod file in my project directory & write following lines in pod file as mentioned in AFNetworking pod file installation
source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '8.0'
pod 'AFNetworking', '~> 3.0'
after writing those above lines in podfile I tried to install pod with this command line.
pod install
and getting following error each & every-time
"The dependency AFNetworking (~> 3.0) is not used in any concrete target"
I also tried using cocoaPods software available with 1.0.0 but same error again & again.
could anyone help me to sort out this issue???
Thanks

As of CocoaPods 1.0 you have to have a 'target' section in your PodFile.
So your example would become:
source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '8.0'
target '' do
pod 'AFNetworking', '~> 3.0'
end
Your problem has nothing to do with AFNetworking - it is the breaking
changes in CocoaPods 1.0 - see
http://blog.cocoapods.org/CocoaPods-1.0-Migration-Guide/ for details.
Using the new CocoaPods app - https://cocoapods.org/app - I got it to
update my PodFiles for me to the new spec.
On Sat, May 21, 2016 at 4:50 PM, infinZero<EMAIL_ADDRESS>wrote:

I am on mac OS X EI Capitan, version 10.11.3 and using Xcode version
7.2.1,
I created a pod file in my project directory & write following lines in
pod file as mentioned in AFNetworking pod file installation
source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '8.0'
pod 'AFNetworking', '~> 3.0'
after writing those above lines in podfile I tried to install pod with
this command line.
pod install
and getting following error each & every-time
"The dependency AFNetworking (~> 3.0) is not used in any concrete target"
I also tried using cocoaPods software available with 1.0.0 but same error
again & again.
could anyone help me to sort out this issue???
Thanks
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/AFNetworking/AFNetworking/issues/3531

--
Richard Groves
Technical Director | NoodlFroot
M: +44 (0)7962 054 163
www.noodlfroot.com
NoodlFroot Limited is a company registered in England and Wales with
registration number 07245048.
Registered office: 20-22 Wenlock Road, London, N1 7GU.

Thanks!


How to configure Max pods per node

[Enter feedback here]
For AKS, there are ways to specify Max pods per node, but I can not find how to configure max pods in AML python SDK or Studio.

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

ID: d9132512-d322-6455-b458-f629337e15f6
Version Independent ID: 2d9e6319-8c7e-113d-a241-2d093b73897f
Content: Create and attach Azure Kubernetes Service - Azure Machine Learning
Content Source: articles/machine-learning/how-to-create-attach-kubernetes.md
Service: machine-learning
Sub-service: core
GitHub Login: @jpe316
Microsoft Alias: jordane

@chengyu-liu-cs Thanks for the question. I am checking with our team internally on this to check if there is a way to set this option with the AKS compute. Thanks!

@chengyu-liu-cs At this moment we don’t support advanced aks configurations in the Azure ML SDK or Studio. For advanced cases, we recommend to create AKS with AKS API's and attach to the AML workspace. Thanks.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag @RohitMungi-MSFT in your reply.


Adds back NumberFormatPartType to the global types from intl

We switched to do:
    type ES2018NumberFormatPartType = "literal" | "nan" | "infinity" | "percent" | "integer" | "group" | "decimal" | "fraction" | "plusSign" | "minusSign" | "percentSign" | "currency" | "code" | "symbol" | "name";
    type ES2020NumberFormatPartType = "compact" | "exponentInteger" | "exponentMinusSign" | "exponentSeparator" | "unit" | "unknown";

So it was documented what options version are available, but in the process broke CI on DT because a module relied on NumberFormatPartType being available globally.

Thanks


Fix formatting of rendered enums

Enums are marked up using a dcc feature that is intended for long quotes. (See below.) We need to find another way to render this.

Duplicate of #41


fix: add button labels

Fix RM-XYZ

🧰 Changes
adds button labels to Lightbox
🧬 QA & Testing

Broken on production.
Working in this PR app.

This PR was released!
🚀 Changes included in v7.10.2


Under concurrent load, child process exit event fires before IO is complete, causing errors

Under heavy load (in the context of web application, for example using nestjs) some of the requests fail:

According to child process documentation (https://nodejs.org/docs/latest-v14.x/api/child_process.html#child_process_event_exit), exit event can fire before stdio is closed.
In such cases respond() is being called with code 0 (success), no error and no data. This results in an error in the calling code, because filename is expected but is not returned.
I added additional error checking to respond() to handle this case.

Given the above, it's probably not a good idea to subscribe to exit event at all. I commented out the on('exit'..) code. on('close') should be sufficient.

Tested it under some load (30 concurrent connections for 2 minutes) - no errors, 5000+ PDFs rendered.

I should add that without this change, under a concurrent load, somewhere in the range of 10-20% of requests for PDF are failing.

@kvasserman we have also been noticing failures to get the file supposedly made by phantomjs under concurrent load. I have a suspicion that the issue fixed by this PR might be the same bug causing #643 . @marcbachmann would it be possible to merge both #644 and #643 and to create a release (even if beta)?

I used patch-package to patch<EMAIL_ADDRESS>for the project I'm working on.
This patch is meant to let others use the fix in #644 until it is merged and a new version released. This patch will probably solve #643 as well.
To install it, follow the installation instructions at https://github.com/ds300/patch-package and copy the diff below to your patches/ folder
Here is the diff that solved my problem (all credit to @kvasserman ) :
diff --git a/node_modules/html-pdf/lib/pdf.js b/node_modules/html-pdf/lib/pdf.js
index 46f2ce4..764bf80 100644
--- a/node_modules/html-pdf/lib/pdf.js
+++ b/node_modules/html-pdf/lib/pdf.js
@@ -123,12 +123,15 @@ PDF.prototype.exec = function PdfExec (callback) {
     // Ignore if code has a value of 0 since that means PhantomJS has executed and exited successfully.
     // Also, as per your script and standards, having a code value of 1 means one can always assume that
     // an error occurred.
-    if (((typeof code !== 'undefined' && code !== null) && code !== 0) || err) {
+    if (((typeof code !== 'undefined' && code !== null) && code !== 0) || err || (code === 0 && !data)) {
       var error = null

       if (err) {
         // Rudimentary checking if err is an instance of the Error class
         error = err instanceof Error ? err : new Error(err)
+      } else if (code === 0 && !data) {
+        // This is to catch the edge case of having a exit code value of 0 but having no data (exit can be called before io pipes are closed)
+        error = new Error('html-pdf: Process exited successfully, but no data received')
       } else {
         // This is to catch the edge case of having a exit code value of 1 but having no error
         error = new Error('html-pdf: Unknown Error')
@@ -150,7 +153,7 @@ PDF.prototype.exec = function PdfExec (callback) {

   // An exit event is most likely an error because we didn't get any data at this point
   child.on('close', respond)
-  child.on('exit', respond)
+  // child.on('exit', respond)

   var config = JSON.stringify({html: this.html, options: this.options})
   child.stdin.write(config + '\n', 'utf8')

This issue body was partially generated by patch-package.

@kvasserman I added a test for your PR branch change here https://github.com/kvasserman/node-html-pdf/pull/1
If that test is run on the master branch of this repo, you can recreate the failure

@barakplasma awesome patch, helped me to reduce the error rate on Heroku + html-pdf to almost 0%!


Add integration testing data for all uncovered meta examples

Some meta examples do not have testing data, e.g. the nystrom regression one.
This (super easy) entrance task is to add such integration testing data. See the wiki develop readme for details how to do this.
Workflow
1.) Send PR and merge to data repo
2.) Update data submodule commit hash in develop branch and send a second PR
Potentially, this can be done for more than a single example at a time.
#3402 #3555

Hi @karlnapf ,
I am new to Shogun and I would like to take up this task.

Added a PR with integration testing data for KRR Nyström in shogun-data

Sorry didn't see you did it already


Little explanation for function fmt at Document

Hi, could you please provide me some information about what this function functionality is ?
https://github.com/weso/utils/blob/9cbf59aff2f34fbaa9bcd6abf7b7db5bb43c1767/modules/utils/src/main/scala/es/weso/document/Document.scala#L66-L93

As it says at the beginning of the file, that code was originally part of Scala's standard library.
However, at scala 2.11 (I think) it was separated from the standard library and marked as deprecated.
Nevertheless, the code is useful when one wants to pretty print some language and that's why several projects embed the code directly in their code base.
It would probably be better to have a standalone repository and library for the code, but as it is so simple, no one is doing it AFAIK.
At this moment, I am not sure iff that particular function is being invoked and could probably be removed.
For some background about that code, I think this paper by C. Lindig contains an explanation of pretty printing in general.

API moved to https://github.com/weso/document


Bug fixes

@robons The bugs you have raised are now fixed. The latest pre-release version is v0.0.25-alpha (https://github.com/marketplace/actions/csv-to-csvw-action).
The example repo is at: https://github.com/GSS-Cogs/csv-to-csvw-action-example

So long as you remove all of the extraneous testing files, I'm happy for you to merge.
But don't forget to consider whether we need to delete the old renamed files too.

@robons It looks the library I am using to detect files changed in a commit do not provide me with the previous name of the renamed file. I was expecting this to be presented in the deleted list of files, but this is not the case. I will need the previous name of the file with its path to detect which files I should be deleted from the out/ folder.

Can you instead look for all CSV files currently in the git repo and remove any folders from the output folder/githubpages which no longer have inputs?


Error for TokenRefreshView, 403 Forbidden

Platforms:

Python: 3.6.5
Django: 2.0.3
djangorestframework: 3.8.2
djangorestframework-simplejwt: 3.2.3
React

Description:

When it is required to refresh the access token with the TokenRefreshView view through the frontend functionality in ReactJs fetch () (general functionality in Javascript for request), it happens that it responds with 403 Forbidden: CSRF cookie not set.
With the obtaining of the token I do not have any problem, it is only with the refreshing; The headers that are sent to you are the following:

And the configuration of the headers for the fetch is the following:
export const refreshAccessToken = (token) => ({
  [RSAA]: {
    endpoint: 'api-auth/token/refresh/',
    method: 'POST',
    body: JSON.stringify({refresh: token}),
    headers: {
      'Accept':  'application/json',
      'Content-Type': 'application/json',
      'Cache': 'no-cache'
      // 'Cookie': document.cookie,
      // 'X-CSRFTOKEN': document.cookie.split('=')[1].split(';')[0]
    },
    'credentials': 'include',
    types: [
      TOKEN_REQUEST, TOKEN_RECEIVED, TOKEN_FAILURE
    ]
  }
})

I have tried to configure in different ways, from the simplest, only with the Content-type, to add those that are commented; I found a different answer when adding the X-CSRFTOKEN, I answer with error 405 Method Not Allowed.
PS: The method discussed in the code is equivalent to the fetch () but it really is of redux-api-middleware, I will be attentive to the updates of this error.

Hey! Did you find out what the problem was? I am stuck with this problem right now. Issuing a new token request with TokenObtainPairView works just fine but TokenRefreshView and TokenVerifyView throws out 401, Unauthorized for me.


docs: updated usage section in readme for all the modules

Description
Updated usage section in readme for all the modules
Release required?

[ ] No release
[x] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

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


Default initializers doesn't work for defaultProps

default initializers defaultProps
Code
interface Props {
  name: string
}

function Greet({ name = "world" }: Props) {
    return
Hello {name.toUpperCase()}!
;
}
<Greet />

Expected behavior:
According to https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-0.html#caveats
it shouldn't have error
Actual behavior:
Has error
TS2741: Property 'name' is missing in type '{}' but required in type 'Props'.

Playground Link:
http://www.typescriptlang.org/play/?jsx=2#code/PTAEGcFMBdQKQMoA1TQPagEQCVIEMBjaTUNAJywAUzIoyA3STAWACg2RQAzPAa0lAAjAJYA7ACZiA5uDbjIBADZ4aoUXgC2tAA6EBuQrADebUNwCuoosLSjQBGnmiQAooshbR0ABQBKAFygeKIAngDcbAC+bGxizmQ8BALUaNrgoCasZupageDQZNJRMaxclta2oADiNDDeRmqaAgC8WADu5IriJJGBKWm+GaZmoDTQ5mR2AOQAEpCKimhTZgDUjVoAdOgAqtrakGQAwnhQfgCEEazR7KwEtvmg4mgaoK0APDWQMKDAAHxAA
There is a workaround
Greet.defaultProps = {name = "world"}

But I would prefer to use default initializers

The documentation you linked refers to a static defaultProps property. You don't have anything like that in your example code. But when you add it, then it will work as expected.
interface Props { name: string }

function Greet({ name }: Props) {
  return
Hello {name.toUpperCase()}!
;
}

Greet.defaultProps = { name: 'World' };

<Greet />

Stackblitz example: https://stackblitz.com/edit/react-ts-bsvjqe?file=index.tsx (ignore the errors, the used TypeScript version is old)

@MartinJohns

The documentation you linked refers to a static defaultProps property.

It has this section

For function components (formerly known as SFCs) use ES2015 default initializers:

function Greet({ name = "world" }: Props) {
    return
Hello {name.toUpperCase()}!
;
}

@RyanCavanaugh Could you elaborate what is working as Intended?

Your function has two conflicting pieces of information:

name is optional because it has an initializer
name is required because it's required in Props as specified by the parameter type annotation

TypeScript says that parameter type annotations always win in this situation.

@RyanCavanaugh Thank. So for functional component I need to use defaultProps.
interface Props {
  name: string
}
const Greet = ({name}: Props) => {
    return
Hello {name.toUpperCase()}!
;
}
Greet.defaultProps = { name: "world" }

and I can use <Greet/> without name property.
But I don't understand what is the point of this example from release notes
function Greet({ name = "world" }: Props) {
    return
Hello {name.toUpperCase()}!
;
}

It doesn't do anything useful.

@RyanCavanaugh any thoughts?


Use of ORecordAbstract.getDatabaseIfDefined() lead to unpredictable errors

Guys,
There are several places where getDatabaseIfDefined() has been used and some of them might lead to unpredictable errors. For example:

Why ODocument.getSchemaClass() returns null if database was previously closed and not yet initialized?
Why OrientEdgeIterator.createGraphElement() creates nothing if db was not recieved from ODatabaseRecordThreadLocal.INSTANCE previously?

I understand that there might be some places where initialization of DB will be so heavy and quite redundant. But even in these cases some workaround might be used.

ODocument.toString() is trying to get immutableSchemaClass just to print schemaClass, but there is already String _className: so no need explicitly get ImmutableSchemaClass

Can you please review usage of getDatabaseIfDefined() and consider switching to getDatabase() in cases when "some DB entity where requested and DB is required to provide proper response"

@PhantomYdn About 2) you're right, I'm fixing it. About 1) ODocument could be used even without a database. That's the reason.

@lvca, but 1 without db doesn't make sense: it will return null and that null can lead to subsequent problems... so users have to call getDatabase() prior to this method to be sure, that NPE will not happen in their code.

We use ODocument for many purposes. For example we manage the distributed cfg between servers, but it's just JSON and it doesn't need db/class.

I see. If case when return null instead of class is OK for some conditions - I'm good. Thanks!

@PhantomYdn Thanks anyway for pointing on such things. Some OrientDB pieces are quite old and a rework could be needed ;-)


SubStatus codes for 401, 403, 404, and 500

Could these HTTP Status codes fit in http crate?

HTTP Status
HTTP SubStatus
Definition

401.x

Unauthorized.

401
1
Access is denied due to invalid credentials.

401
2
Access is denied due to server configuration favoring an alternate authentication method.

401
3
Access is denied due to an ACL set on the requested resource.

401
4
Authorization failed by a filter installed on the Web server.

401
5
Authorization failed by an ISAPI/CGI application.

401
7
Access denied by URL authorization policy on the Web server.

403.x

Access is denied.

403
1
Execute access is denied.

403
2
Read access is denied.

403
3
Write access is denied.

403
4
SSL is required to view this resource.

403
5
SSL 128 is required to view this resource.

403
6
IP address of the client has been rejected.

403
7
SSL client certificate is required.

403
8
DNS name of the client is rejected.

403
9
Too many clients are trying to connect to the Web server.

403
10
Web server is configured to deny Execute access.

403
11
Password has been changed.

403
12
Client certificate is denied access by the server certificate mapper.

403
13
Client certificate has been revoked on the Web server.

403
14
Directory listing is denied on the Web server.

403
15
Client access licenses have exceeded limits on the Web server.

403
16
Client certificate is ill-formed or is not trusted by the Web server.

403
17
Client certificate has expired or is not yet valid.

403
18
Cannot execute requested URL in the current application pool.

403
19
Cannot execute CGIs for the client in this application pool.

403
20
Passport logon failed.

404.x

File or directory not found.

404
1
Web site not accessible on the requested port.

404
2
Web service extension lockdown policy prevents this request.

404
3
MIME map policy prevents this request.

500.x

Internal server error.

500
11
Application is shutting down on the Web server.

500
12
Application is busy restarting on the Web server.

500
13
Web server is too busy.

500
14
Invalid application configuration on the server.

500
15
Direct requests for Global.asa are not allowed.

500
16
UNC authorization credentials are incorrect.

500
17
URL authorization store cannot be found.

500
18
URL authorization store cannot be opened.

500
100
Internal ASP error.

I don't quite understand what this is asking for. Could expand on the feature request?

These are nonstandard codes, which come from Microsoft IIS Status and Substatus codes.  They would greatly help my Rust based web framework.
The only alternative I see is to modify the reason-phrase in the response header, similarly to tornado, which sorta matches what rfc2616 says to do for 403:

If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity.

Yet, it also says in rfc7230 about providing that reason:

The reason-phrase element exists for the sole purpose of providing a textual description associated with the numeric status code, mostly out of deference to earlier Internet application protocols that were more frequently used with interactive text clients. A client SHOULD ignore the reason-phrase content."

So, it seems a machine code for each status message matches the spirit of the standards better than putting human readable text, which is meant to be ignored.  afaict, this means StatusCode would change from a 3 digit integer, as defined by ietf, to a decimal value which encompasses some new codes, as implied by ietf.

When the HTTP specs refer to an entity, that usually always means the body of a message.
What does the substatus mean for the protocol? How is rendered and parsed? Why can't they be implemented as a header or in the body?

When the HTTP specs refer to an entity, that usually always means the body of a message.

Why can't they be implemented as a header or in the body?

Yea.  I think for 401, the WWW-Authenticate field has space for that info, for 403, the Permission-Denial is either implied or can go in the header or body, and for 500, the Error can go in the header or body too.  About 500, here's some named errors: error: 121 and system error codes
Thanks


ScopedCssBaseline doesn't work

Hello,
When trying to use the ScopedCssBaseline module, I get runtime error:

Attempted import error: 'ScopedCssBaseline' is not exported from '@material-ui/core' (imported as 'Core').

This seemed to help:
@react.component @module("@material-ui/core/ScopedCssBaseline")
external make: (
  ~children: React.element=?,
  ~classes: Mui.ScopedCssBaseline.Classes.t=?,
  ~className: string=?,
  ~id: string=?,
  ~style: ReactDOM.Style.t=?,
  ~key: string=?,
  ~ref: ReactDOM.domRef=?,
) => React.element = "default"

The problem here is, that it is not re-exported in this file.
They only fixed that in v5, unfortunately: https://github.com/mui-org/material-ui/pull/21869/files

Maybe we can patch the MUI sources before the code generation step?

This is fixed in version 5. Closing...


bad tag name and/or "\r" error

Hi,
I have installed version 3.1.0 of the docker-iobroker on a Synology DiskStation DS718+ using MACVLAN with IP adresses <IP_ADDRESS> and <IP_ADDRESS>. The ioBroker admin webUI is reachable under <IP_ADDRESS>. Everything works fine so far.
However, a simple update by using the command "iobroker update" leads to an "node \r" error. If I try the alternative by using "npm install iobroker.js-controller --production", npm shows an "EINVALIDTAGNAME" message.
Respective screenshots and further infos in German language can be found here and here.
When I switch to version 2 of docker-iobroker using exact the same mounted directories (/volume1/docker/ioBroker) there is no such error message.

Hi,
at the forum thread (link) I read that this issue is gone after modifying and running "reinstall.sh". Can you confirm?
Can this be closed? Thx.
Regards,
André

Hi André,
yes. Thanks for your support.
Best regards,
Thorsten
Von: Andre<EMAIL_ADDRESS>Gesendet: Montag, 28. Oktober 2019 22:43
An: buanet/docker-iobroker<EMAIL_ADDRESS>Cc: drtp<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Betreff: Re: [buanet/docker-iobroker] bad tag name and/or "\r" error (#34)
Hi,
at the forum thread (link https://forum.iobroker.net/post/317162 ) I read that this issue is gone after modifying and running "reinstall.sh". Can you confirm?
Can this be closed? Thx.
Regards,
André
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/buanet/docker-iobroker/issues/34?email_source=notifications&email_token=AEHPR3MYYPXZIW7BRJ52OATQQ5MGNA5CNFSM4IP6A6K2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECOPWCY#issuecomment-547158795 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AEHPR3OTA32R4M4QHSAYI6DQQ5MGNANCNFSM4IP6A6KQ .  https://github.com/notifications/beacon/AEHPR3N3YCERGZ4MZKVUHSTQQ5MGNA5CNFSM4IP6A6K2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECOPWCY.gif


Sample build strategies should be secure by default

The sample build strategies in this project define to skip certificate validation when pushing to the target registry. This is done by default and not configurable. See:

Buildah: https://github.com/redhat-developer/build/blob/2e19beaca342a85570410adc9845a26226879dc7/samples/buildstrategy/buildah/buildstrategy_buildah_cr.yaml#L31
Kaniko: https://github.com/redhat-developer/build/blob/2e19beaca342a85570410adc9845a26226879dc7/samples/buildstrategy/kaniko/buildstrategy_kaniko_cr.yaml#L26
Source2Image: https://github.com/redhat-developer/build/blob/2e19beaca342a85570410adc9845a26226879dc7/samples/buildstrategy/source-to-image/buildstrategy_source-to-image_cr.yaml#L45

We should ship samples that are secure by default. This means that certificate validation should NOT be disabled by default. Instead, it should be enabled. We could introduce a flag on the build cr to skip it.

Yes the yet-to-be used parameters section is for such not-so-common parameters that don't make sense to be strongly typed in the API but nice-to-have.
A bit of history around why the SSL verification has been turned off : pushes to the registry was failing in case of internal registries because the service account didn't have th CA certificates mounted.
We need to define a contract so that the build controller can always look for CA certificates in a specific object. That way, we can actually hardcode SSL verify to true ( because that's the good practice!).

I also agree we should be export this parameter to end-user. If I am the end-user, I want the SSL is always enabled to make sure the security.
And I have a question. about the history, Shoubhik.
When you talking about the internal registries, do you mean you faced some problem when you try to enable SSL for openshift internal registry?
And when you talking about the contract, do you mean it is a CA cert which is stored in SA? Or is there any document or link to introduce the background?
Thanks a lot! :)

I dont think this is high prio for now, if you folks allow me, I would like to add the icebox label.

So this means, there currently is no possibility to use a custom CA for my private container registry, or did I get that wrong?

So this means, there currently is no possibility to use a custom CA for my private container registry, or did I get that wrong?

Nothing out of the box, but you can try to customize the build strategy, see https://kubernetes.slack.com/archives/C019ZRGUEJC/p1645000201441049?thread_ts=1644959006.747239&cid=C019ZRGUEJC for the idea.

So this means, there currently is no possibility to use a custom CA for my private container registry, or did I get that wrong?

Nothing out of the box, but you can try to customize the build strategy, see https://kubernetes.slack.com/archives/C019ZRGUEJC/p1645000201441049?thread_ts=1644959006.747239&cid=C019ZRGUEJC for the idea.

Could you post the article here plz?I can not enter this slack workspace...

Hi @xiaocode, you can join that Slack workspace here: https://slack.k8s.io/
The referenced post is:

Okay, we are currently discussing a change where the push operation is not anymore performed by the build strategy step but instead by shipwright logic. This will enable us to offer capability like what you mention in a strategy-independent way. Your scenario fits very well. But, this will take some more time until this lands.
For the time being, you will need to extend the Kaniko build strategy. Basically you'll need a step before build-and-push which takes the certificate from an environment variable coming from a secret, and stores it in a file in a shared volumeMount also used by the build-and-push step. And then use the corresponding Kaniko argument. I don't have the time now to try that out.


Firefox print (and preview) problem with card and table (flex problem)

Hello,
I am not sure if the problem is on the Bootstrap 4.3.1 or in Firefox but the printing and preview printing is truncated (only one page in printed or previewed) if a long table is contained in a Card component.
You can see a simple example on jsbin here: link to example
For information, it works well on Chrome and Edge.
The problem seems to be due to display:flex on div element.
The way to avoid this problem is to add in your stylesheet:
@media print {
	div.card {
	  display: block !important;
	}
}

Operating system and version:
Windows 10 (version 1809)
Firefox 66 : not working
Google 73.0.3683.86 : Work well
Microsoft Edge 11 : Work well

Closing as a stale won't fix—v5 drops the bulk of our print styles.

Closing as a stale won't fix—v5 drops the bulk of our print styles.


test-memory-reap breaks on -O0

So does test-memory, because it doesn't link.

I think this bug is invalid. It's slow, but finishes in about 10 seconds on my machine.

test-memory breaks when the userland is at -O0.  test-memory-reap breaks when the kernel is at -O0

Ah, that makes sense.
Turns out test-float-fib also doesn't work if the kernel is -O0

Actually, with the kernel -O0 (and userland -O2) the following tests fail:

test-memory-reap
test-memory
test-float-fib
test-fork

this is likely a bug in the fork syscall, which all of these share.

This was broken by fc05b705dee6a1bbc5b047578e15ea21873e5887


Restoring to a completely new server

This is not issue or bug. Just asking if this feature available or not.
Let's say following situation happened:
Server that is getting backed up by restic is under attack or attacked. And local repo is unreachable.
Is it possible to restore from remote (origin) into a completely new server?

Restic isn't bootable in itself, so you need to boot something that can run restic, and then run restic from that. Since restic works on OS X, Linux, Windows, etc, this should be fairly straight forward. You can use any Live OS or similar, for example. You just need the restic binary, which you can either download from https://beta.restic.net/ or cross-compile yourself using Go (let us know if you need pointers for that).

PS: This type of question is a better fit for the forum at https://forum.restic.net/ 👍

@rawtaz  I never mentioned booting it. All I want to know it, how to initialize local repo and pull last backup from remote repo in a new server?

@turalus No, I did.
I'm not sure I understand what you're trying to say. What local repo are you talking about? When you use restic to back something up, you initialize one repo(sitory). That repo may be remote (e.g. SFTP, Minio, S3, etc), or it can indeed be a local one (e.g. on local disk). Either way, there's just one repo for your backup (in the normal case, you can of course do multiple backups each to their own repo, but that's probably outside of this discussion).
So, that repo, what do you mean by it being "local"?
The only way I can interpret what you are asking and saying is that you have a completely clean, not in any way installed, server, and you want to restore the data you have in a restic repo to it.
You can either mount the disks in that server on some other system, and on that system use restic to restore the data from your restic repository into the disks, and then put the disks back into the server. You will probably have to do some additional commands in order to make those disks bootable, since that's outside of what restic does (it doesn't manage boot flags, nor does it manage your partitions). So while you can restore "all your files", you still need to manage the operating system aspects of what you restore to.
Here's a thread in the forum, discussing full system restore: https://forum.restic.net/t/full-system-restore/126 - As you can see there's a bunch of special directories and other parts of the filesystem that you need to handle explicitly, as they're not just plain files/directories.
If I'm misunderstanding what you're asking, please let me know. While it's seemingly a bit unclear, I believe the answer to your question is in short a "yes, but you need to be aware of a few complementing things that you need to attend".

This still doesn't explain to me how restic can restore from a completely offline repo! I backup to a NAS and if I attempt to list that repo's snapshot or mount it on the NAS, it always fails because I can't access the cache. This seems to be a major flaw with the program! Am I missing something really basic?

This still doesn't explain to me how restic can restore from a completely offline repo!

I don't understand what you mean. Just to be clear: restic is not a complete disaster recovery system. In order to restore to a machine, you will need to boot an operating system and run restic so that it can access the repository to which the data has been saved.

it always fails because I can't access the cache.

We will need to see the error output in order to diagnose what's going on. Restic does not need a cache for its operation, it's just an optimization and the cache will just be recreated if it is missing. You can even disable the cache with --no-cache.
So, this becomes way too long and other people won't find it. If you need more support, please create a new post in the forum and we'll start from scratch there.
Thanks!


Exclude package.json in vscode dir

when looking for package.json we could end up picking up vscodes package.json which is wrong (at which point we don't know the calling extension).

Codecov Report

Merging #10035 (194a28c) into main (f35e44a) will increase coverage by 0%.
The diff coverage is 100%.

@@          Coverage Diff           @@
##            main   #10035   +/-   ##
======================================
  Coverage     63%      63%
======================================
  Files        211      215    +4
  Lines      10097    10123   +26
  Branches    1611     1612    +1
======================================
+ Hits        6456     6474   +18
- Misses      3125     3131    +6
- Partials     516      518    +2

Impacted Files
Coverage Δ

src/platform/common/application/extensions.node.ts
86% <100%> (+<1%)
:arrow_up:

...rc/platform/common/dataScienceSurveyBanner.node.ts
65% <0%> (-6%)
:arrow_down:

src/platform/common/platform/fileUtils.node.ts
50% <0%> (-2%)
:arrow_down:

src/platform/serviceRegistry.node.ts
97% <0%> (-1%)
:arrow_down:

src/platform/export/types.ts
100% <0%> (ø)

src/platform/common/platform/types.ts
100% <0%> (ø)

src/platform/common/platform/types.node.ts
100% <0%> (ø)

src/platform/export/exportFileOpener.node.ts

src/platform/export/exportDialog.node.ts

src/platform/export/export.index.node.ts
100% <0%> (ø)

... and 7 more


Double quotes are not properly escaped when passed to ant

When we submit a PR containing double quotes in their description, for example:

Some commit message with "double quotes"

It results in ant build erroring out, because of invalid escaping of command line arguments. The issue lies within following fragment:

[workspace] $ ant '-DghprbPullTitle=Some commit message with "double quotes"' -DghprbPullAuthorLoginMention=@kip9 " build-without-tests
Buildfile: /vol/lib/jenkins/jobs/pull-request/workspace/build.xml
BUILD FAILED
Target "quotes" does not exist in the project "XXX".

Ant should fire target called build-without-tests, but due to wrong escaping it goes wild.
I've found another report of the same issue on Jenkins JIRA tracker:
https://issues.jenkins-ci.org/browse/JENKINS-29919
Note: I've removed other ant parameters passed by your plugin from the output, as they aren't important for this particular case, and contain sensitive information.

Looks like a duplicate of #327

I'll double check, but I'm 90% sure it's not the case. It's not related to "displaying" things on Jenkins side, but to passing arguments to the jobs invoked. Will post if that workaround helps or not as soon as I manage to prepare test case.

I had exactly the same problem with Jenkins and ant! When quotes are in the PR name, it tries to call ant with that.

We have faced a similar issue to this.
We have double quotes in the pull request description and it was causing the same issue (quotes not escaped properly) in ant command parameters.
The injected parameters were like the following:
[entrypoints] $ cmd.exe /C "...\ant.bat
-file module.ant

'"-DghprbPullLongDescription=This PR fix bug XXX \""bug description\""\r\n\r\nmore details\r\nname=xxx\r\nversion=1.0.0\r\nprovider=xxx\r\nbuildLabel=20220224-1555"'

The pull request description is like the following:
This PR fix bug XXX "bug description"

more details
name=xxx
version=1.0.0
provider=xxx
buildLabel=20220224-1555

plugin version 1.42.0


Tap: true firing multiple events, iscroll-5.1.3

I have an issue with the click event for the scroller.
I have a header list, when the iscroll options for click and tap are set to true, there are multiple events are firing and when I change them to false, it is working good in desktop and IOS but not in android, in android it is not even getting clicked, I tried to use the custom tap event as well like, tap: "myTap" and listened to that event, then it again firing multiple times.
Please let me know if there is any workaround for this or I have to change the version.

check this comment.
https://github.com/cubiq/iscroll/issues/361#issuecomment-194189473

I forked iscroll 5.1.3
https://github.com/naver/egscroll
egscroll fix this issue.
you can download from bower
bower install egscroll#master

I merged


'Video unavailable' when trying to load certain youtube videos

Be sure to search for your issue before opening a new one.
Current Behavior
Once deployed to heroku, I try and load a youtube video using react-player but it comes back with 'video unavailable - watch on youtube'.  On localhost it worked fine.

It works OK for some videos, i.e. https://www.youtube.com/watch?v=15Nqbic6HZs&t=1176s&ab_channel=AlfaMist
But for most videos, I get the aforementioned error.  i.e. https://www.youtube.com/watch?v=Beld090NIoo&t=376s&ab_channel=MyAnalogJournal
Is this something related to copyright for embedded videos?
Expected Behavior
It should load all videos without issue.
Steps to Reproduce

Try and load a video that does not work, i.e. https://www.youtube.com/watch?v=Beld090NIoo&t=376s&ab_channel=MyAnalogJournal - it comes back with 'video unavailable - watch on youtube'
Try and load a video that does work, i.e. https://www.youtube.com/watch?v=15Nqbic6HZs&t=1176s&ab_channel=AlfaMist - it works fine and no error message.

Environment

URL attempting to play:
An example of a youtube video that does load: https://www.youtube.com/watch?v=15Nqbic6HZs&t=1176s&ab_channel=AlfaMist
An example of a youtube video that doesnt load: https://www.youtube.com/watch?v=Beld090NIoo&t=376s&ab_channel=MyAnalogJournal
Browser: Chrome latest
Operating system: Mac OS Monterey
jsFiddle example: https://jsfiddle.net/sv5x3ug1

Other Information
In the console, I do also get the following errors, although not entirely sure if relevant:

Did you find a solution?

Did you find a solution?

yes, I did.  Found it here: https://stackoverflow.com/questions/51424578/embed-youtube-code-is-not-working-in-html
By adding SECURE_REFERRER_POLICY = "no-referrer-when-downgrade" it worked after then.

Just add somewhere in the <head> this
<meta name="referrer" content="no-referrer-when-downgrade">


Explicit declaration of mounted engines

This is an official issue regarding https://github.com/nanobox-io/nanobox/issues/95
When nanobox detects a local engine is mounted (even a clone of a generic engine). We want to show the path to the engine. So rather than:
--------------------------------
   [√] LANGUAGE : python
   [√] ENGINE   : python (generic)
--------------------------------

maybe something like:
--------------------------------
   [√] LANGUAGE : python
   [√] ENGINE   : path/to/mounted/engine
--------------------------------

+1 :)

@harobed Thanks for your vote! Nanobox has been completely re-written from the ground up, and we just released the v1 into beta this week. We would love to get your feedback on the new version. The new guides are still a WIP but should be usable within the next week. If you're interested, we'd love to talk with you on irc #nanobox or we can bring you into our slack channel as well.
Additionally, Nanobox and Nanobox Cloud have been merged into a unified process. If you would be interested in early access to the private beta please let me know and I can get you an access token.
Just reach out to<EMAIL_ADDRESS>and we can get you going.
I really appreciate your help on this. I'll go ahead and close this ticket and hope to hear from you directly.


installation fails

i cannot follow the installation instructions
it gives me the following error when i run develop
Installed /home/user/pyethapp
Processing dependencies for pyethapp==1.5.0
error: rlp 0.4.7 is installed but rlp<=0.4.6,>=0.4.4 is required by set(['devp2p'])

Here's the devp2p commit where they pinned rlp to <=0.4.6: https://github.com/ethereum/pydevp2p/commit/1b4647f500bdb495c77518e55b94b97a1125739c
Maybe that needs to be done in pyethapp as well, until ethereum/pyethereum#412 is fixed?

Maybe just swapping the order of the devp2p and rlp lines in requirements.txt would fix this, as rlp<=0.4.6 would be installed as a requirement of devp2p and when pip gets to the rlp>=0.4.4 line it will already be satisfied and won't end up installing 0.4.7 (latest)

+1 have same error. it seems that swapping the order does not work. @gsalgado

I couldnt reproduce this error. But, after installing a new system and trying to bring this back to life, pip install devp2p was failing. It was a simple solution as I was just missing python-dev, perhaps try sudo apt-get install python-dev and try again (assuming you're on ubuntu/debian)?

Hi, did anyone figure this out? I had the same issue while building docker for hydrachain.

Having this issue as well.

Remove the following code from hydrachain/docker/dev/hydrachain/node:
line 26
RUN python setup.py install
hydrachain/makefile line 60
release: clean
python setup.py sdist upload
python setup.py bdist_wheel upload
dist: clean
python setup.py sdist
python setup.py bdist_wheel
ls -l dist
install: clean
python setup.py install

This is great; thanks very much to everyone involved!


Remove direct dependency on FSharp.Core

We have a transitive dependency on this, and the current setup causes a package downgrade error in all downstream packages, requiring them all to pick a version of FSharp.Core, which isn't great, especially as most downstream packages aren't written in F#.
The error happens because FsToolkit.ErrorHandling depends on FSharp.Core 7.
This also needs to be changed in the SDK.
The alternative is to keep the dependency, but update it to 7.

Maybe we pin it to nuget FSharp.Core >= 7.0.0 in that case?


Miscellaneous Updates and Test Improvements

Coverage remained the same at 100.0% when pulling 5ea241be51339365a844b5abfb77be2c6b74f81f on jeffgbutler:master into 158079071c13cc277c67df884d1bdcc7d2862ea9 on mybatis:master.


Update Connatix Docs With Video Media Type Support

🏷 Type of documentation

[ ] new bid adapter
[x] update bid adapter
[x] new feature
[ ] text edit only (wording, typos)
[ ] bugfix (code examples)
[x] new examples

📋 Checklist

[x] Related pull requests in prebid.js or server are linked https://github.com/prebid/Prebid.js/pull/11933
[ ] For new adapters check submitting your adapter docs

released with PBJS 9.5


Tree status is not refreshed on old PRs

For example: https://github.com/flutter/flutter/pull/101834
Tree has been green since yesterday, but the luci-flutter status is still red.

Culprit: pull list api returns 30 PRs by default. We should extend the number to cover relatively old PRs.

Does this mean only 30 of our 199 open PRs are getting luci-flutter updates?

Does this mean only 30 of our 199 open PRs are getting luci-flutter updates?

Right. The top 30 PRs based on created. To avoid creating new PRs, one workaround to to switch to updated. I guess we switched to a smaller number instead of all PRs due to API quote issue.


Make migration script the same as in the lsm module

Description
Related to https://github.com/inmanta/lsm/pull/793
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[ ] Attached issue to pull request
[x] Changelog entry
[ ] Type annotations are present
[ ] Code is clear and sufficiently documented
[ ] No (preventable) type errors (check using make mypy or make mypy-diff)
[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )
[ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)

Processing this pull request

Merged into branches master in 2f4555dde1748d28b2bebc0f08a314ab050bddc8

Processing #8044.


[email] display cc and bcc fields

Code changes

[x] showing CC and BCC fields for expanded email

Screenshots:
When I send an email to others including CC and BCC:

When I send an email to others more than PARTICIPANTS_TO_TRUNCATE including CC and BCC:

When I receive an email from someone including 3 CC and 4 BCC:

Readiness checklist

[x] Added changes to component CHANGELOG.md

License
I confirm that this contribution is made under the terms of the MIT license and that I have the authority necessary to make this contribution on behalf of its copyright owner.

@pooja169usp yeah they are cropped but will be scrollable on x axis. Should the tooltip show all of it?

@pooja169usp yeah they are cropped but will be scrollable on x axis. Should the tooltip show all of it?

@krisgardiner I think it should have the same flexibility as what gmail currently does. So the width/height auto adjusts to a point. All text wraps.

@pooja169usp @AaronDDM updated


Repo should have a CONTRIBUTING.md

to encourage participation, the repo should have a contributing page (and reference it in readme) on how to contribute.
Does the group use a fork&pull approach or rebase?
The contributing page should either directly contain governance info or it should reference a GOVERNANCE.md page. How are contributions reviewed (ie explain OCA wg meetings open to all)? Who are project maintainers? etc

Excellent request. Would anyone on the ontology project like to spend some time developing these artifacts?


Update scalatest to 3.1.2

Updates org.scalatest:scalatest from 3.1.1 to 3.1.2.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalatest", artifactId = "scalatest" } ]

labels: test-library-update, semver-patch

Codecov Report

Merging #106 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #106   +/-   ##
=======================================
  Coverage   13.05%   13.05%
=======================================
  Files          53       53
  Lines        2152     2152
  Branches       27       27
=======================================
  Hits          281      281
  Misses       1871     1871

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 43d077c...2401a32. Read the comment docs.


Increase length of area stats name

Update area and geofence names with varchar(255) to match koji

done in #194


Move system test runner from bash to Python

Also re-tooling the run_module_tests method to be more useful from other directories (so that we could call it from the scripts/ subdirectory).

Towards #1123

@tseaver PTAL I added another commit to have all 4 system tests use Config.

LGTM


color calibration crash in glasgow

Has to do with the gamma grid?
Double-check that the existing gamma grid works on the machine in Toronto. If so, this might be an issue with different versions of Numpy (it's a numpy array) or PsychoPy (maybe the way to define gamma grids has changed?). Or even different versions of Python (would be strange). If it doesn't work in Toronto, the gamma grid itself may have an error.

This is an issue with the EyeTracker repository... moved to that repository.