Include full URLs in search results

URLs are typically what will ultimately be resolved or used by a service or application utilizing the search API. So it'd probably make sense to just return these.

@kauffj I wanted to just get this one done, however, there could be dependencies, and there may be alternative uses of getting claim value details based on a search result. Either way it returns all that it does because the data is stored in elastic search as an elastic document that can be summed up as a json object of information. The results are for these documents. If we wanted to return the URLs it would just be some minor post processing.
Since there are external dependencies on this API it is probably best to create a new API:
current http://localhost:50005/search?s=
new http://localhost:50005/url/search?s=
This way we can have the service live before it is used live by the app and the current one can still be used unhindered until the adjustment in the app is ready. Also it reduces golive dependencies. The drawback is now we have 2 apis.

I was going through tickets assigned to me and realized I never saw above until now. Good catch of a real issue, but I'd propose the proper fix for this is likely to add a version parameter the endpoint to allow graceful migration, not diverge endpoints.

Yeah that makes sense! Will do

@seanyesmunt we have the PR ready, but I just wanted to double check with you that we are not using the search APIs anywhere else.

They are used in the android app. It would definitely be a smoother transition to include versioning in the api

I'm not 100% on what I meant by this, but I think I just meant to actually include the URL so it doesn't have to be reconstructed, not to actually strip out the metadata (though that may be fine).
Ideally, it's return the canonical url.

It's still not performant to display/determine the shortest possible canonical URL, but I'm fine waiting on the daemon to fix that.
That said, even without proper canonical URLs, I do think it makes sense to return the full URL. It'd be like if a search engine returned the host and TLD separately (technically host includes TLD but you get what I mean).

@tiger5226 Whoops. You are right. I thought we were handling that data differently.

All clear. I will leave the current fields alone and add one for the canonical url which should be:
<claim_name>#<claim_id> is this correct @kauffj ?
I reviewed the issue linked, but I don't see what exactly we want the canonical url to be. Sorry if I missed something.

@tiger5226 no, the canonical URL is more complex than that. Given full access to chainquery however, it should be possible to compute it in a single query/pass.
I updated https://github.com/lbryio/lbry/issues/958 to (hopefully) be significantly more clear

@kauffj This seems very complex. In a given query each row would have to compare against all other rows with a similar set of fields. Do you think this is something I should adjust Chainquery to calculate when a new claim comes in? Also what is the impact if a claim is abandoned? I presume that doesn't matter. If it existed in the blockchain at some point it impacts the canonical url. Is this correct? Adjusting Chainquery seems like a good idea. I could see someone using the API to gain quick access to the canonical URL or getting the claimid from a canonical url. If chainquery has already done these calculations it will be much faster. Also the adjustment to the lighthouse query becomes super simple as well. We just add a field to grab and push to elastic search.

@tiger5226 canonical URLs cannot (and won't) change even if a claim is abandoned.
We can probably wait to handle this in lighthouse until it's been added at lower levels.

ok I will put this in the icebox.

@tiger5226 Is this ready for review or going to the icebox?

icebox, corrected the pipeline to triaged.

closing until it's been added at a lower level


Elfie TsvWriter, Arriba AddOrUpdate options

Elfie: Adding TsvWriter to allow writing out TSV. Pattern for converting integers without allocation.
Arriba: Adding "AddOrUpdateOptions" to AddOrUpdate to allow controlling whether columns or rows are added per AddOrUpdate. This makes it easier to "decorate" tables with additional data only for items which exist and provides clean overrides for the "ShouldAddColumnsDynamically" heuristics.

@michaelcfanning @rtaket @jinujoseph @dannychmsft

PR Feedback fixed. [Jinu, the Elfie changes are additive only, so I'm submitting. Let me know if you have any concerns.]


Split --whitelisted-ips for SSH/TCP/HTTP

I'd like to have the sish available from everywhere for tunnel creation, but restricts usage of the tunnels created to a few IP addresses.
Currently it's not possible because the whitelisted IP list is the same for SSH, TCP and HTTP.
I suggest this gets split into 3 different configuration option.

I do see the value here, but I'm a bit averse of adding more functionality to sish where it is probably better done using something else (iptables or ufw or nftables) to handle this.

That being said, if someone wants to add this functionality I am more than happy to get it merged in :)

Uhm. What the purpose of the existing --whitelisted-ips then ? Because we can do it also with iptables ;-)

The main benefit is a "quick and easy" geoip filter. (i.e. if there is a problem locale that is just spamming you with logins, you can easily just tell sish to ignore that). What you're trying to do (limit ssh logins to just a few ips) sounds like something a iptables rule will fix!
Again, I'm more than happy if someone wants to pull this in and we can get it into a sish release :)
I just sadly don't have too much time on my hands (work, school, life) to do it myself! If sish was able to pay the bills, I would do it in a heartbeat!


Launch MLIR code on VCK5000?

On the MLIR-AIE side, everything seems to be clear as long as it is to be run on VCK190. I understood that to make it on VCK5000, MLIR-AIR is needed. I installed it as detailed here with the most recent ROCm-runtime.
Following aircc doc, there seems not to be in any way a clear path to get an MLIR code up and running on VCK5000. I tried to play with the tests and a few examples, such as SPARTA but I am not seeing that going anywhere.
Perhaps there is an indication or a tutorial like the one for MLIR-AIE here where from an MLIR code written in AIE/R dialects, I can get it running on VCK5000?

Hi @medbzkst ! Do you have any update / workaround on this issue?

Nothing much except what is given in SPARTA example in ROCm (not the one in this repo!).

Hi again @medbzkst :) It seems that we have common interest in running some MLIR code on VCK5000 while interfacing with the PL as your issue here https://github.com/Xilinx/mlir-aie/issues/1105 suggests.
I'm curious to know if you managed to do it even on a small project, and if so, how?

Hi @jbelot, nothing really seemed to work out ...


Node JS: crypto import polyfill not taken into account?

Hi there 👋 !
I see that there is now a polyfill to automatically import and declare crypto in the global scope.
Unfortunately, I'm getting the following error when using WARCRecord.create() after removing my own global import of crypto :
ReferenceError: crypto is not defined

For reference, I'm importing crypto as such to compensate for its absence:
import crypto from 'crypto'
global.crypto = crypto

I'm using warcio.js 2.0.1 with Node 18+.
Thanks in advance,

Yes, the current polyfill applies only to the test suite. I was having trouble setting up a proper polyfill for the node build.
Though, Node 18 does have --experimental-global-webcrypto for making crypto global and I guess in node 19, this is the default..

Finally found a way to have automatic polyfills:
Use inject with a separate polyfills file


Rule for org.eclipse.angus:angus-activation

It conflicts with com.sun.activation:jakarta.activation:2.0.1.

Note:

conflicts only with the 1.x version of angus-activation (com.sun package)
Version 2.x has org.eclipse package


Ice connection state change delegate method is not triggering

The following method is not at all triggered for any of the state like below one.
RTCIceConnectionStateNew,
RTCIceConnectionStateChecking,
RTCIceConnectionStateConnected,
RTCIceConnectionStateCompleted,
RTCIceConnectionStateFailed,
RTCIceConnectionStateDisconnected,
RTCIceConnectionStateClosed,
RTCIceConnectionStateCount,
public func peerConnection(_ peerConnection: RTCPeerConnection, didChange newState: RTCIceConnectionState) {
    self.delegate?.rtcClient(client: self, didChangeConnectionState: newState)

}

But at the same time the below delegate is triggering and i am getting ice candidates.
public func peerConnection(_ peerConnection: RTCPeerConnection, didGenerate candidate: RTCIceCandidate) {
    self.delegate?.webrtcClient(client: self, didGenerateIceCandidate: candidate)

}

The peer connection is not established in this case. Kindly do the needful on this.

Kindly do the needful. i am not able to proceed further

@sudhamoorthi  are you able to make connections in different networks from device to device ?

yes. connection is established between different device in different networks.

@sudhamoorthi  without triggering  RTCIceConnectionStateChecking,
RTCIceConnectionStateConnected,
RTCIceConnectionStateCompleted,
RTCIceConnectionStateFailed,
RTCIceConnectionStateDisconnected,
RTCIceConnectionStateClosed,
RTCIceConnectionStateCount,
the above method
how are you able to connect (make a connection video call) can you please ping me to mail<EMAIL_ADDRESS>I have some query


PHP 8.1 support in MySQLiConnector::query errors

Parent issue for https://github.com/silverstripe/silverstripe-framework/pull/10570

The default error reporting mode in PHP 8.1 has changed from using errors reported on the connection handle to throwing mysqli_sql_exception. query() makes no allowance for this, and functions up the call stack expect to catch
Silverstripe\ORM\Connect\DatabaseException instead - resulting in the MySQLi exception going all the way up to halt the system.

Linked PR has been merged


revise term WebLogic operator

Where needed, I changed "WebLogic operator" to "WebLogic Kubernetes Operator," elsewhere, I changed it to "operator."

also merged to develop in 35905b5c1


feat: add webhooks for crossplane resources to zarf-agent

Description
This Implements the Crossplane resources

Configuration
Provider
Function
to rewrite the spec.package and spec.packagePullSecrets field in a similar way as for Pod.

This allows the Crossplane Pod to pull the images from the local registry.
Well... not quite yet. This also implements an extension of the private-registry secret, which is created for namespaces managed by zarf. additionally to the localhost reference to the registry this also adds the same credentials for the route over the kubernetes service.
This implementation rewrites
apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: provider-terraform
spec:
  package: xpkg.upbound.io/upbound/provider-terraform:v0.16.0

into
apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  # Removed for brevity
  labels:
    app.kubernetes.io/managed-by: Helm
    zarf-agent: patched
  name: provider-terraform
spec:
  ignoreCrossplaneConstraints: false
  package: zarf-docker-registry.zarf.svc.cluster.local:5000/upbound/provider-terraform:v0.16.0-zarf-255403924 # patched by zarf-agent
  packagePullPolicy: IfNotPresent
  packagePullSecrets:
  - name: private-registry # added by zarf-agent
  revisionActivationPolicy: Automatic
  revisionHistoryLimit: 1
  runtimeConfigRef:
    apiVersion: pkg.crossplane.io/v1beta1
    kind: DeploymentRuntimeConfig
    name: default
  skipDependencyResolution: false

which will by default create a pod like this:
apiVersion: v1
kind: Pod
metadata:
  # Removed for brevity
spec:
  containers:
    - image: <IP_ADDRESS>:31999/upbound/provider-terraform:v0.16.0-zarf-255403924-zarf-928246402
       name: package-runtime
  # Removed for brevity

The resulting Pod is a bit of a problem. Since when
https://github.com/defenseunicorns/zarf/blob/0c02643b9f5631a7bdd98650cc87c74901190771/src/internal/agent/hooks/pods.go#L76
is called the function does just replace the hostname.
I could not yet find a nice way to implement this, as the const i would need is in
https://github.com/Avarei/zarf/blob/13a7957b46a0dcacb9baa63d7826f42ea44915d7/src/types/k8s.go#L51
and the package surrounding
https://github.com/defenseunicorns/zarf/blob/0c02643b9f5631a7bdd98650cc87c74901190771/src/pkg/transform/image.go#L27
seems to avoid this kind of external dependency. and i would like to avoid negatively impacting your code quality.
Currently I sidestep this issue by creating a DeploymentRuntimeConfig in Crossplane which lets me overwrite the used image back to the internet version, which will be replaced back to the localhost version when the Pod is created.
Related Issue
Fixes  #2572
Checklist before merging

[ ] Test, docs, adr added or updated as needed
[ ] Contributor Guide Steps followed

I reconsidered and implemented the additional logic to the function in the hope that it makes review easier, than thinking about hypotheticals.
The resulting pod now looks like it should. I also added a test to assert this.

I am closing this PR because the Zarf team has decided to not support mutating Crossplane resources at this time
https://github.com/defenseunicorns/zarf/pull/2628#issuecomment-2186990599


Clippy warnings in some components with rust 1.78

Describe the bug
There's a new clippy warning that shipped with Rust 1.78 and is turned on by default, which warns about empty rustdoc comments. See https://rust-lang.github.io/rust-clippy/master/index.html#/empty_docs.
It appears that the #[component] macro generates such empty rustdoc comments in the case where you don't specify your own rustdoc comment and the component has no properties, which now triggers the new clippy lint.
It's more of an annoyance than a bug as you can silence the warning by either adding a rustdoc to your component (probably good practice anyway...) or disabling the lint, but the component macro can probably be fixed to not output any empty rustdoc comment in that particular case.
Leptos Dependencies
leptos = { workspace = true, features = ["csr"] }
leptos-use = "0.10"
leptos_query = { version = "0.5", features = ["csr"] }
leptos_query_devtools = { version = "0.1", features = ["csr"] }
leptos_router = { version = "0.6", features = ["csr"] }

To Reproduce
Steps to reproduce the behavior:

Add a component like the following:

#[component]
pub fn Foo() -> impl IntoView {
    view! { "test" }
}

run cargo clippy

Expected behavior
There shouldn't be any clippy::empty_docs warning.

Disable clippy::empty_docs in Cargo.toml:
[lints.clippy]
empty_docs = "ignore"


Generate a random incomplete Deal (e.g. a random 4-card ending)

I want a random Deal, but not 13-card but with some lower number of cards.
Is there a clean way to do this?
If not, do you think this feature makes sense (and are you interested in a PR)?
(I don't need help with "ugly" solutions :) )

Hiya,
Apologies for the late reply.
There's no inbuilt way of doing this at the moment, but I agree it is a potentially useful feature. The generate_deal function is a bit messy, but if you have an algorithm in mind then I would definitely be interested in a PR :)
Thanks,
Dom


does not compile with rust 1.52.1

https://tfb-status.techempower.com/unzip/results.2021-06-06-03-33-04-151.zip/results/20210601100659/ntex/build/ntex.log

Sorry, my bad. Now I release a new version.

The new version is now available. In techempower you don't have to do anything since the version is 0.15. Sorry.


Penalty Improvement - Traceback

Dependencies

settlementIds as we currently do not have a table for those. https://github.com/ubiquity/ubiquibot/issues/787

Overview
Let's name this table Penalties to represent instances where a contributor is penalized. This table keeps a record of the exact comment or incident due to which a penalty was applied.
Penalties
A ledger of penalties applied to contributors. This table provides a link to the exact comment or reason for the penalty, making the process transparent and traceable.
Schema

Field
Type
Description
Example Value

id
Integer
Unique identifier for the penalty log entry.
1

created
DateTime
Timestamp when the penalty was logged.
2023-09-14T19:20:23.004Z

updated
DateTime
Timestamp when the penalty log was last updated.
2023-09-14T19:20:23.004Z

userId
Integer
GitHub id of the user penalized.
139262667

settlementId
Integer
Reference to the Settlements table.
512

orgId
Integer
GitHub id of the organization.
76412717

repoId
Integer
GitHub id of the repository where the issue is located.
534616569

issueId
Integer
GitHub id of the issue related to the penalty.
1868425596

commentURL
String
URL of the comment or incident leading to the penalty.
https://github.com/ubiquity/ubiquibot/issues/680#issuecomment-1718491622

Notes:

The commentURL field allows quick access to the exact comment or reason for the penalty.
I also made up the settlementIds as we currently do not have a table for those. However its spec is here https://github.com/ubiquity/ubiquibot/issues/787
Ensure foreign key constraints are set up properly to maintain data integrity.
We should rely on GitHub API's id properties instead of node_id Source.

Source

https://github.com/ubiquity/ubiquibot/issues/680#issuecomment-1718488900

/start

/start

We'll probably need to change the schema to support a new table that has all the debt information. Basically a ledger of credits and debits which also associates the issue with each credit or debit. Example:

Maybe we can have another table called offset that is an array of repo that offsets a particular penalty

created
updated
user
credit
org
repo
task
offset

2023-09-14T19:20:23.004Z
2023-09-14T19:20:23.004Z
whilefoo
-100
ubiquity
ubiquibot
680
566, 447

2023-09-14T19:20:32.554Z
2023-09-14T19:20:32.554Z
whilefoo
150
ubiquity
ubiquity-dollar
733
234, 444, 560

We'll probably need to change the schema to support a new table that has all the debt information. Basically a ledger of credits and debits which also associates the issue with each credit or debit. Example:

@pavlovcik  Maybe we can have another table called offset that is an array of repo that offsets a particular penalty

created
updated
user
credit
org
repo
task
offset

2023-09-14T19:20:23.004Z
2023-09-14T19:20:23.004Z
whilefoo
-100
ubiquity
ubiquibot
680
566, 447

2023-09-14T19:20:32.554Z
2023-09-14T19:20:32.554Z
whilefoo
150
ubiquity
ubiquity-dollar
733
234, 444, 560

@seprintour

Storing multidimensional data in a SQL database should be avoided
Also I updated the spec.

I think penalty_amount field should be added. @pavlovcik

/stop

Rolled into https://github.com/ubiquity/ubiquibot/issues/787


add whitespaces between z. and B. as it ist in many other occurences in german faq

@DerVogel2020
You might need to put in   if you do that. I'm not sure about the convention for this, but maybe you have some references? Is it OK for z. and B. to be split at the end of a line?

You might need to put in   if you do that. I'm not sure about the convention for this, but maybe you have some references? Is it OK for z. and B. to be split at the end of a line?

Sure, you're right. Reference is https://www.duden.de/node/212250/revision/212286 and https://www.duden.de/node/208327/revision/243442 , there always with whitespace.

Thanks, @DerVogel2020 , I have merged your changes.
Cheers!

Thanks.


Skyline: automatically add small molecule detail columns for datagrid…

…s that use TargetColumn

Here's an example of how a TargetResolver equipped grid looks currently:

and with the new work - more detail, which is nice:

but the big difference is that if you wanted to add a new entry to that list that wasn't already in the document, you'd have to understand our crazy string encoding. Now you just give it a name, formula etc and it all works.

I guess I see this as more informational than a useful feature that anyone would use. Certainly, I doubt anyone will ever enter a single row into these grids manually. I have used pasting in lists of peptides, but here I think it is not as clear what columns you need, and there does not seem to be a way to turn off unused columns and rearrange them, as in Edit > Insert > Transitions. So, to me it looks more like you get the information rather than this makes it possible to enter the information. The Inche and SMILES columns seem very long, possibly less useful in this context. If the KEGG column is another ID and much shorter, maybe it should go next to CAS and IncheKey instead of at the end.

It presents columns for any information that it has, leaving out any columns that it hasn't got values for. If there isn't any initial information available, it presents all possible fields so you can paste in, as in populating an ion mobility database (which is what drove this work in the first place). It's true that there's no way to hide or rearrange columns at this point, that would be a nice enhancement but it's not a big deal to do it in Excel first. The current order of all those ID columns reflects our priority of IDs in the event that more than one are available, but that's not terribly important from a UI point of view and they could certainly be ordered for decreasing brevity if that's what we want.

A picture of friendlier UI for small molecule users

Masses seem a bit high precision for UI. Let's limit them to the same 4 decimal places used in the Targets tree.

It's a round trip thing, but I'll see what I can do about it.
On Tue, Sep 1, 2020 at 4:38 PM Brendan MacLean<EMAIL_ADDRESS>wrote:

Masses seem a bit high precision for UI. Let's limit them to the same 4
decimal places used in the Targets tree.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ProteoWizard/pwiz/pull/1087#issuecomment-685189172,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJFE6L6B4GRDAYCT4QOQADSDWAYPANCNFSM4NHCEVLA
.

You need the full value for the round trip, but you can display whatever precision you want.

Certainly - you just have to make sure you don't pull it back in again and
decide that the molecule description has changed.
On Wed, Sep 2, 2020 at 10:28 AM Brendan MacLean<EMAIL_ADDRESS>wrote:

You need the full value for the round trip, but you can display whatever
precision you want.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ProteoWizard/pwiz/pull/1087#issuecomment-685885670,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJFE6MAAOVEOH2Z4LTJRZ3SDZ6DDANCNFSM4NHCEVLA
.

Excellent, thanks!
On Wed, Sep 2, 2020 at 11:48 AM nickshulman<EMAIL_ADDRESS>wrote:

@nickshulman commented on this pull request.
Certainly - you just have to make sure you don't pull it back in again and
decide that the molecule description has changed.
Microsoft Access has logic in it to decide whether a the format string
loss data for a particular value. When you go into edit mode on a cell in
Microsoft Access, it checks whether parsing currently formatted value is
equal to the cell value. If the parsed formatted value and the real value
are not equal, then the value that gets put in the edit box is the
unformatted real value.
You would think that this logic would have been duplicated somewhere in
the current DataGridView, but I do not see anything like that. There might
be some way to make it work where you change the formatting if necessary on
a DataGridViewCell right before it goes into edit mode, but I do not know
whether that is feasible.
In pwiz_tools/Skyline/Controls/SmallMoleculeColumnsManager.cs
https://github.com/ProteoWizard/pwiz/pull/1087#discussion_r481417100:

+using System.Linq;
+using System.Windows.Forms;
+using pwiz.Skyline.Model;
+using pwiz.Skyline.Model.Lib;
+using pwiz.Skyline.Properties;
+using pwiz.Skyline.Util;

+namespace pwiz.Skyline.Controls
+{
+

///
/// Handles updating small molecule detail columns when target is set
///
public class SmallMoleculeColumnsManager
{

   public const string DATA_PROPERTY_NAME_FORMULA = @"Formula"; // This must agree with the member name in DbAbstractPeptide

You should do:
public const string DATA_PROPERTY_NAME_FORMULA =
nameof(DbAbstractPeptide.Formula);
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ProteoWizard/pwiz/pull/1087#pullrequestreview-480097872,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJFE6PXLIBOA7JEWGWVEODSD2HPTANCNFSM4NHCEVLA
.

Closing this until I can return to it


fix: proxy_read_timeout updated in nginx conf

Fixes https://github.com/SigNoz/signoz/issues/1881

@prashant-shahi , please have a look at this, not able to assign you as reviewer.


Consider app crash tests as non-fatal if they pass on retry

Introducing a flag retry-app-crash-tests to retry tests that. might have caused app crashes. When this flag is turned on, the execution will not fail if all app crash tests pass on retry.
The retries will honor the error-retries count, restarts the sim before retrying the crashed test and makes the crash logs available, like before.
Ref: https://github.com/linkedin/bluepill/issues/455
\cc @ob  @chenxiao0228

Code looks good but I wonder if we really need another flag. Our flag set is already too complicated so if we can find a way to roll this under an existing flag (or simplify the flag set somehow) that'd be much better.

Oscar, I agree a few flags might have gotten complicated over time and may even have deviated from the original purpose. So, I am going to take the latter route to simplify the flag set and deprecate some of them. Created issue https://github.com/linkedin/bluepill/issues/457 for further discussion and follow-up on this.

let's clean up the flags after this...

Sure. Merging this now.


[VEN-2315]: Liquid Staked ETH Pool deployments

Description

Resolves #
Checklist

[ ] I have updated the documentation to account for the changes in the code.
[ ] If I added new functionality, I added tests covering it.
[ ] If I fixed a bug, I added a test preventing this bug from silently reappearing again.
[ ] My contribution follows Venus contribution guidelines.

We should change the base branch to develop because we have already merged https://github.com/VenusProtocol/isolated-pools/pull/344


[Process] don't populate internal buffer if user closure is supplied

This fixes Issue 17390

Can you please reopen the PR at the symfony/symfony repository? The component repository are read-only splits of the main repo.

Done.


useMemo vs useContextSelector

Hi,
May you please let me know , why to prefer this library over useMemo?

As of now, you can't stop triggering rerenders when context updates, even with useMemo.
See some old discussions:

https://github.com/facebook/react/issues/14110
https://blog.axlight.com/posts/4-options-to-prevent-extra-rerenders-with-react-context/


Refactor to work with the proposed Ghidra WildcardAssembler.

This branch refactors the pattern compiler portion of Pickled Canary to use the new WildcardAssembler proposed in NationalSecurityAgency/ghidra#6118

This the CI for Pickled Canary will be broken on this pull request until there's a Ghidra release with the WildcardAssembler in it. Manual testing against a DEV version of Ghidra with the WildcardAssembler shows all tests passing.


Enable case-sensitive assertion action/resource value storage

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.

this change allows if there is an application that it does the authorization based on case sensitive values, the user can store them as such in Athen ZMS without automatically being converted to lowercase.
however, for authz checks within ZMS and ZTS, it will still only support case-insensitive matches.


Website Linux download links are broken.

Been trying to install the Debian version of the app for days but clicking the download button does not yield any result. Windows button works fine...

Do people not read the issue template?
#2118 #2117 #2103


Update the ESP-IDF tooling to master (or v5.4 when released) to fix Embedded Swift Crashes

Fixes Embedded Swift issues. Random numbers do not work on 5.1.2 - 5.3.1 in addition to several issues.
Note: The fix is on master, but we don't have a 5.4 release yet. Since Embedded Swift is experimental, it makes sense to be recommending tooling that solves current problems. There is some risk in not having a stable ESP-IDF release.

Please stay in the master (v5.4) branch. Don't checkout to the release v5.2 or v5.3
As a summary;
We have fixed the The gap between ...  errors in this repo with the 2eb2975 . No change in the IDF releases.
We don't have getentropy error in IDF master (v5.4) branch. No need to apply a patch.
For the previous idf releases (v5.3.x and v5.2.x), apply the patch I prepared. https://github.com/user-attachments/files/15877608/0001-newlib-getentropy-implementation.patch

https://github.com/apple/swift-embedded-examples/issues/17#issuecomment-2348454444

I'd like to hold off on this until 5.4 is released

@erhankur do we have a rough idea of when 5.4.0 will be released?

@rauhul We plan to make the final release in February next year.

Oh ok thats a while away, we can use the master branch until then.


forgot password works sometimes and doesn't work the other times

If some feature is not working at only some time, It doesn't mean that there is an bug in the code. It can also happen due to some other factors like, bad network connection.
When there is a bug in the code, the bug arrives after certain steps taken by the user. So please provide those steps otherwise we will force to assume that issue was due to other factors and close the issue.

Done


Add procedure for repurposing compute as uan

Summary and Scope
This PR adds a procedure for repurposing compute nodes as UANs.
Issues and Related PRs

Resolves CASMUSER-3053

Testing
Tested on:

hela

Test description:
This procedure was tested on hela repurposing one compute node as a UAN.
Risks and Mitigations
Low risk
Pull Request Checklist

[X] Version number(s) incremented, if applicable
[X] Copyrights updated
[X] License file intact
[X] Target branch correct
[X] CHANGELOG.md updated
[X] Testing is appropriate and complete, if applicable
[NA] HPC Product Announcement prepared, if applicable

I think the guide should add to prerequisites and the steps to complete, a check that cray_uan_setup: true is set. This guide could be referenced if you feel it would be useful:
https://github.com/Cray-HPE/uan-product-stream/blob/main/docs/portal/developer-portal/advanced/Enabling_CAN_CHN.md

I think the guide should add to prerequisites and the steps to complete, a check that cray_uan_setup: true is set. This guide could be referenced if you feel it would be useful:
https://github.com/Cray-HPE/uan-product-stream/blob/main/docs/portal/developer-portal/advanced/Enabling_CAN_CHN.md

@alanm-hpe The Enabling_CAN_CHN file does not appear in either ditamap. Do we want that procedure to appear in both guides?


Breaks with MineAddons 1.3

[x] I am using a release version of the mod
[x] I have mods that integrate with this installed:

[x] Tinker's Construct
[x] Mine Factory Reloaded
[x] Mine Addons
[ ] Moo Fluids
[x] Waila
[x] Avaritia

[x] I also have other mods installed
[x] I have searched for this issue previously and it was either (1) not previously reported, or (2) previously fixed and I'm having the same problem.
[x] I am crashing and can provide my crash report(s)

Additional Information

[x] Java Version:

[ ] Java 6
[ ] Java 7
[x] Java 8

[x] Minecraft Version:

[x] 1.10.2

Issue Description
MineAddons recently released v1.3, which changes the mod namespace layout, causing a crash.

Reproduce Steps
Use MiniMoos with MineAddons 1.3

Additional Information
Crash Log

@BrisingrAerowing Thanks for pointing this out, I'm going to fix it as soon as possible.

@BrisingrAerowing Should be fixed in the new version (1.4.2)


Fix log output for "daprd --version" call

In what area(s)?

/area runtime

/area operator

/area placement

/area docs

/area test-and-release

What version of Dapr?
1.5.0
Expected Behavior
$ ~/.dapr/bin/daprd --version
1.5.0

Actual Behavior
~/.dapr/bin/daprd --version
2021/11/13 01:27:27 maxprocs: Leaving GOMAXPROCS=12: CPU quota undefined
1.5.0

Steps to Reproduce the Problem
run daprd --version directly
Release Note

RELEASE NOTE:

@CrazyHZM can you please comment here with /assign so the issue get assigned to you? Thanks for the PR.

/assign

@CrazyHZM can you please comment here with /assign so the issue get assigned to you? Thanks for the PR.

This bot is very easy to use. ： ）


changed Show.py such that pdf is rendered instead of png

Hi all,
Apologies for the sudden pull request without any prior discussion.
This is a temporary fix to #6 and https://github.com/Abjad/abjad/issues/1132
The issue to the underlying problem might be as described in https://github.com/Abjad/abjad/issues/1173 or somewhere else.
Anyway, this is my work-around of the problem.
Instead of rendering the score as a .png file, here I am rendering it as a .pdf file first before converting it to a .png file.
Due to the changes that I have made, the Wand Python package and pdfcrop are now required.
Apologies in advance if this pull request does not align with the contributing guidelines of this repository.

Hi! Thanks for the PR.
I'm aware of pdfcrop, but I'd prefer to fix this extension without requiring additional dependencies.
LilyPond 2.20+ now support a -Dcrop directive which crops output. That can be combined with -Dbackend=svg to create cropped SVGs, one per system.
See https://github.com/Abjad/abjad/blob/master/abjad/ext/sphinx.py#L306-L317 and https://github.com/Abjad/abjad/blob/master/abjad/iox.py for how this technique is now used to generate the SVGs shown in Abjad's documentation, e.g. https://abjad.github.io/api/abjad/core/LeafMaker.html#abjad.core.LeafMaker.LeafMaker. To start, abjad-ext-ipython needs to be rewritten to use the LilyPondIO class instead of IOManager.
I know it's a large ask to completely rewrite this to use the new technique, but that's the direction I  want this extension module to take.

I have a simpler implementation that embeds SVGs without additional dependencies here: https://github.com/Abjad/abjad-ext-ipython/pull/8

Note that #8 is failing its Travis-CI tests. I have some additional work to do in Abjad's https://travis-ci.org/github/josiah-wolf-oberholtzer/uqbar dependency before the test suite will pass, and still have to port play() forward to use some of the simpler techniques employed in #8.

@nivlekp OK, take a look at #8. Let me know if that code works for you.

Thank you @josiah-wolf-oberholtzer very much for the fix.
Please take a look at my comment at #8.
Anyhow, I am happy to close this pull request.


Install from live cd media

Issue description
I'm trying to install in a place with inconsistent/no internet. I would like to be able to read the packages from the live cd medium—I downloaded the "plasma" live cd because I thought it came with the packages to install KDE.
Steps to reproduce
Unplug modem & attempt to install nixos from the "plasma" live cd.

On an additional note, there are many good reasons to be able to point the package resolver at a local resource rather than a hard-coded remote one, notably caching of packages for local distribution.

Actually, NixOS does use the Live media as a substituter when installing. If the install cannot be performed with a Live image, this means that the image lacks a component in /nix/store needed for your system to be realised.
I would actually expect that a basic NixOS configuration as generated by nixos-generate-config on a graphical ISO would be able to be built without relying on cache.nixos.org. Can you provide your configuration.nix here? I'd like to take a look at what you expected to install on your system.
By the way, did you know that while building the ISO with Nix you can declare an option system.extraDependencies to include additional packages in the image? They would get used if they're needed while installing your shiny new system :sparkles:

Another issue could be different version of Nixpkgs - to increase your chances of successfully substituting all packages from the Live media, you need to use the same Nixpkgs version that was used to build the media (hint: nixos-version --revision will show you the Git revision that was used in producing the system you're running, this should work on a Live ISO too)

Likely what's happening is there's a few packages being added to your configuration unintentionally. And thus nix will try to fetch them.
There's also the isoImage.includeSystemBuildDependencies option if you want to make your own iso, it will dramatically inflate the size of the iso as you're downloading all of the build dependencies as well.

I would create your own iso, following https://nixos.wiki/wiki/Creating_a_NixOS_live_CD:
iso-config.nix:
{config, pkgs, ...}:
{
  import = [
    <nixos/modules/installer/cd-dvd/installation-cd-graphical-plasma5.nix>
  ];

  # Rest of your final configuration
  ....
}

then build the image with:
nix-build '<nixpkgs/nixos>' -A config.system.build.isoImage -I nixos-config=iso-config.nix

that should create an iso image with all of your desired packages already on it

Alright, this certainly doesn't need to be an open issue. However, I would have definitely downloaded a no-network install iso had it been available, so I'm just registering interest in this use case.


Request: concurrent network requests

I'm trying to upload a large file in multiple parts, and making those requests run in parallel would make that task faster. But with the current implementation all requests are bottlenecked by a single V8 thread.
Is there any easier solution than having multiple Blockstack sessions, if that's even possible and not consume too many resources? Or is this a shortcoming of the current library?

There are limitations due to the j2v8. For multiple Blockstack sessions/threads to work you need to attach and detach the engine (there are methods for that), not sure what will happen with the running upload calls or the return results. It looks like difficult to manage.
I think it would make more sense to implement putFile in Android directly.

@friedger a native Android library, or even just the putFile call, sounds like a dream. I haven't look much inside the blockstack.js, but I imagine it's no small task.

Gaia protocol is not that difficult...
On Fri, 12 Jul 2019, 17:39 Sérgio Santos<EMAIL_ADDRESS>wrote:

@friedger https://github.com/friedger a native Android library, or even
just the putFile call, sounds like a dream. I haven't look much inside
the blockstack.js, but I imagine it's no small task.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/blockstack/blockstack-android/issues/154?email_source=notifications&email_token=AALBYWMWK2I2ZKQ3PLC7KLTP7CQU5A5CNFSM4IBOOZT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ2DUSY#issuecomment-510933579,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALBYWP2QRNVZ6GT4LLLYD3P7CQU5ANCNFSM4IBOOZTQ
.

Work is done in feature branch native_gaia

Version 0.5.0 introduces a native implementation of the gaia protocol, giving much more control over concurrent requests.


Swipes do not register in top half of portrait-oriented Carousel Card ('stack', and 'tinder')

@bd-arc,
Didn't follow the Template this time around due to time constraints, but I want to put this potential issue on your radar. It's a really weird one..
To reproduce:

I set up a Carousel with tall (portrait-oriented) cards.
I found that once the card exceeded a rectangular shape, the hitbox for swipes diminished.
Did not do much else by way of customization. Occurs with layouts 'stack', and 'tinder'

Works:

Seeing Issue:

Thanks for taking a look.
Reproduced on iOS device / simulator. Tested in Dev mode.

Hi @jordangrant,
Damn! I've encountered this issue before, but I was secretly hoping that this was a problem with something very specific in the provided example... Apparently not.
So far, this behavior seems linked to the carousel position in the viewport rather than having to do with the height of the item. It looks like approximately the top quarter of the screen is deaf to swipe events on the carousel. You can take a look at this screencast to see what I mean: https://giphy.com/gifs/xThtasOLFCD4A6pW6c
Note that I didn't have any issue on Android.
To be honest, I don't have the slightest clue so far about what's at stake :( I'm going to run a few tests based on the iOS/Android difference and see if I can get a better understanding of the issue.
Any idea on your end?

If I remove the following style rule, it works properly:
zIndex: carouselProps.data.length - index

But then, of course, the layout is completely messed up:

A quick fix would be to use props scrollInterpolator and slideInterpolatedStyle to pass the Android 'stack' custom interpolation. The effect is going to be inverted, but at least there will be no need to specify a zIndex.

Regarding the issue, I am left clueless. I don't understand why:

the zIndex rule randomly messes with the swipe events (sometimes you can swipe the 2-3 first items and then you need to swipe from a lower portion of the screen)
only the top part of the screen is affected
the default effect doesn't have any swipe issue even if we add the zIndex rule.

=> Any insight will be greatly appreciated!

Here is the relevant code in case you want a quick fix for the 'stack' effect:
import Carousel, { getInputRangeFromIndexes } from 'react-native-snap-carousel';

function stackScrollInterpolator (index, carouselProps) {
    const range = [1, 0, -1, -2, -3];
    const inputRange = getInputRangeFromIndexes(range, index, carouselProps);
    const outputRange = range;

    return {
        inputRange,
        outputRange
    };
}
function stackAnimatedStyles (index, animatedValue, carouselProps) {
    const sizeRef = carouselProps.vertical ? carouselProps.itemHeight : carouselProps.itemWidth;
    const translateProp = carouselProps.vertical ? 'translateY' : 'translateX';

    const cardOffset = 18;
    const card1Scale = 0.9;
    const card2Scale = 0.8;

    const getTranslateFromScale = (index, scale) => {
        const centerFactor = 1 / scale * index;
        const centeredPosition = -Math.round(sizeRef * centerFactor);
        const edgeAlignment = Math.round((sizeRef - (sizeRef * scale)) / 2);
        const offset = Math.round(cardOffset * Math.abs(index) / scale);

        return centeredPosition - edgeAlignment - offset;
    };

    return {
        opacity: animatedValue.interpolate({
            inputRange: [-3, -2, -1, 0],
            outputRange: [0, 0.5, 0.75, 1],
            extrapolate: 'clamp'
        }),
        transform: [{
            scale: animatedValue.interpolate({
                inputRange: [-2, -1, 0, 1],
                outputRange: [card2Scale, card1Scale, 1, card1Scale],
                extrapolate: 'clamp'
            })
        }, {
            [translateProp]: animatedValue.interpolate({
                inputRange: [-3, -2, -1, 0, 1],
                outputRange: [
                    getTranslateFromScale(-3, card2Scale),
                    getTranslateFromScale(-2, card2Scale),
                    getTranslateFromScale(-1, card1Scale),
                    0,
                    sizeRef * 0.5
                ],
                extrapolate: 'clamp'
            })
        }]
    };
}

const myCarousel = (
    <Carousel
      scrollInterpolator={stackScrollInterpolator}
      slideInterpolatedStyle={stackAnimatedStyles}
      useScrollView={true}
    />
);

@bd-arc Thanks for the  quick fix! No idea why the issue occurs, but this definitely helps me for the time being.

@bd-arc How I implement the same fix but for the "Tinder" style?

Hi @donnes,
Here is the code in case you're facing the issue and need to fix the "Tinder" layout. I've just adapted the code you can find in /src/utils/animations.js.
import { Platform } from 'react-native';
import Carousel, { getInputRangeFromIndexes } from 'react-native-snap-carousel';

function stackScrollInterpolator (index, carouselProps) {
    const range = [1, 0, -1, -2, -3];
    const inputRange = getInputRangeFromIndexes(range, index, carouselProps);
    const outputRange = range;
    return { inputRange, outputRange };
}

function stackAnimatedStyles (index, animatedValue, carouselProps) {
    const sizeRef = carouselProps.vertical ? carouselProps.itemHeight : carouselProps.itemWidth;
    const mainTranslateProp = carouselProps.vertical ? 'translateY' : 'translateX';
    const secondaryTranslateProp = carouselProps.vertical ? 'translateX' : 'translateY';

    const cardOffset = 9;
    const card1Scale = 0.96;
    const card2Scale = 0.92;
    const card3Scale = 0.88;
    const peekingCardsOpacity = Platform.OS === 'android' ? 0.92 : 1;

    const getMainTranslateFromScale = (cardIndex, scale) => {
        const centerFactor = 1 / scale * cardIndex;
        return -Math.round(sizeRef * centerFactor);
    };

    const getSecondaryTranslateFromScale = (cardIndex, scale) => {
        return Math.round(cardOffset * Math.abs(cardIndex) / scale);
    };

    return {
        opacity: animatedValue.interpolate({
            inputRange: [-3, -2, -1, 0, 1],
            outputRange: [0, peekingCardsOpacity, peekingCardsOpacity, 1, 0],
            extrapolate: 'clamp'
        }),
        transform: [{
            scale: animatedValue.interpolate({
                inputRange: [-3, -2, -1, 0],
                outputRange: [card3Scale, card2Scale, card1Scale, 1],
                extrapolate: 'clamp'
            })
        }, {
            rotate: animatedValue.interpolate({
                inputRange: [0, 1],
                outputRange: ['0deg', '22deg'],
                extrapolate: 'clamp'
            })
        }, {
            [mainTranslateProp]: animatedValue.interpolate({
                inputRange: [-3, -2, -1, 0, 1],
                outputRange: [
                    getMainTranslateFromScale(-3, card3Scale),
                    getMainTranslateFromScale(-2, card2Scale),
                    getMainTranslateFromScale(-1, card1Scale),
                    0,
                    sizeRef * 1.1
                ],
                extrapolate: 'clamp'
            })
        }, {
            [secondaryTranslateProp]: animatedValue.interpolate({
                inputRange: [-3, -2, -1, 0],
                outputRange: [
                    getSecondaryTranslateFromScale(-3, card3Scale),
                    getSecondaryTranslateFromScale(-2, card2Scale),
                    getSecondaryTranslateFromScale(-1, card1Scale),
                    0
                ],
                extrapolate: 'clamp'
            })
        }]
    };
}

const myCarousel = (
    <Carousel
      scrollInterpolator={stackScrollInterpolator}
      slideInterpolatedStyle={stackAnimatedStyles}
    />
);

Note that, as for the stack layout, you'll get the Android effect (inverted compared to the original iOS one).

Hope this helps!

Hello,
I'm facing the same problem, i can't swipe with the entire area of my cards because of zIndex issue on stack layout. I tried your solution but that revert my cards display and into vertical mode it's very not a good display and other think i can't use looping options. Is there another solution to swipe normaly and keep the all the functionalities??

@soulso Unfortunately, I haven't been able to pinned down the root of the issue yet. Even though I fear a React Native bug, any insight that could point me in the relevant direction would be of great help!
I'm currently considering horrible workarounds like setting pointerEvents={'none'} for non-visible elements for example... I'll let you know if I find anything that works.
For now, unless you create a custom interpolation that doesn't require the zIndex trick (like this one), you may encounter the issue.

Hello thanks for the answer, i hope you will found a solution.
How i can know that an element is non-visible?

@soulso You can use the measure() method in conjunction with prop onSnapToItem(index). For example, you could check if index - 1, index and index + 1 are located in the viewport and then set pointerEvents to none for every item but those three, given that they are currently visible.
Or, you can simply set pointerEvents to auto for those three items, without relying on measure().
Be aware that:

it's a hack
measure() is asynchronous and its execution usually takes about 500 ms
there will almost certainly be side effects
I'm guessing that it can solve the issue, but I'm not sure yet.

Anyway, if you decide to give it a try, I'll be interested in your findings ;-)

@bd-arc Thank you very much! It's fixed the problem on iOS using the Android style.

Not sure if this has been already reported, but I noticed that the area where swipe actions are not detected is actually occupied by one or more "ghost" cards.
If you inspect the layout (CMD+I) and tap in those areas, you can see that there is an invisible card partially overlapping the active one.
That said, given that the first two or three cards in the carousel seem to work well, I suppose that old cards that should be way off the screen are instead rendered in that area, messing with the click events.
Hope this could help in fixing or finding a workaround!

I'm also experiencing the same issues. I thought I was going mad (hence the awes-inspiring background colors).
So if this helps at all: In the image below I'm on the 6th slide, and the ghost image is from the 2nd slide.

Very interesting! However I confirm that the problem goes away if you use
removeClippedSubviews={true}

If you don't have too many cards it shouldn't be a big deal.

@brunoci doesn't help me 😢

I encountered an issue on iOS where I am displaying 3 carousels on 1 view and the third one is not showing up, removeClippedSubviews={true} fixed it.

In version 3.8.0 I've set removeClippedSubviews to false by default when using the 'stack' or 'tinder' layouts.
This should help!

If I remove the following style rule, it works properly:
zIndex: carouselProps.data.length - index

But then, of course, the layout is completely messed up:

A quick fix would be to use props scrollInterpolator and slideInterpolatedStyle to pass the Android 'stack' custom interpolation. The effect is going to be inverted, but at least there will be no need to specify a zIndex.
Here is the relevant code in case you want a quick fix for the 'stack' effect:
import Carousel, { getInputRangeFromIndexes } from 'react-native-snap-carousel';

function stackScrollInterpolator (index, carouselProps) {
    const range = [1, 0, -1, -2, -3];
    const inputRange = getInputRangeFromIndexes(range, index, carouselProps);
    const outputRange = range;
    return { inputRange, outputRange };
}

function stackAnimatedStyles (index, animatedValue, carouselProps) {
    const sizeRef = carouselProps.vertical ? carouselProps.itemHeight : carouselProps.itemWidth;
    const translateProp = carouselProps.vertical ? 'translateY' : 'translateX';

    const cardOffset = 18;
    const card1Scale = 0.9;
    const card2Scale = 0.8;

    const getTranslateFromScale = (index, scale) => {
        const centerFactor = 1 / scale * index;
        const centeredPosition = -Math.round(sizeRef * centerFactor);
        const edgeAlignment = Math.round((sizeRef - (sizeRef * scale)) / 2);
        const offset = Math.round(cardOffset * Math.abs(index) / scale);

        return centeredPosition - edgeAlignment - offset;
    };

    return {
        opacity: animatedValue.interpolate({
            inputRange: [-3, -2, -1, 0],
            outputRange: [0, 0.5, 0.75, 1],
            extrapolate: 'clamp'
        }),
        transform: [{
            scale: animatedValue.interpolate({
                inputRange: [-2, -1, 0, 1],
                outputRange: [card2Scale, card1Scale, 1, card1Scale],
                extrapolate: 'clamp'
            })
        }, {
            [translateProp]: animatedValue.interpolate({
                inputRange: [-3, -2, -1, 0, 1],
                outputRange: [
                    getTranslateFromScale(-3, card2Scale),
                    getTranslateFromScale(-2, card2Scale),
                    getTranslateFromScale(-1, card1Scale),
                    0,
                    sizeRef * 0.5
                ],
                extrapolate: 'clamp'
            })
        }]
    };
}

const myCarousel = (
    <Carousel
      scrollInterpolator={stackScrollInterpolator}
      slideInterpolatedStyle={stackAnimatedStyles}
      useScrollView={true} // <--- Use this for a better effect or disable it to get performance optimizations
    />
);

=> Note that you're going to get the Android effect on both platforms (inverted compared to the original iOS one).

Regarding the issue, I am left clueless. I don't understand why:

the zIndex rule randomly messes with the swipe events (sometimes you can swipe the 2-3 first items and then you need to swipe from a lower portion of the screen)
only the top part of the screen is affected
the default effect doesn't have any swipe issue even if we add the zIndex rule.

=> Any insight will be greatly appreciated!

@bd-arc  can i make the inverted version from this effect on "tinder" layout on both android & ios?

If I remove the following style rule, it works properly:
zIndex: carouselProps.data.length - index

But then, of course, the layout is completely messed up:
A quick fix would be to use props scrollInterpolator and slideInterpolatedStyle to pass the Android 'stack' custom interpolation. The effect is going to be inverted, but at least there will be no need to specify a zIndex.
Here is the relevant code in case you want a quick fix for the 'stack' effect:
import Carousel, { getInputRangeFromIndexes } from 'react-native-snap-carousel';

function stackScrollInterpolator (index, carouselProps) {
    const range = [1, 0, -1, -2, -3];
    const inputRange = getInputRangeFromIndexes(range, index, carouselProps);
    const outputRange = range;
    return { inputRange, outputRange };
}

function stackAnimatedStyles (index, animatedValue, carouselProps) {
    const sizeRef = carouselProps.vertical ? carouselProps.itemHeight : carouselProps.itemWidth;
    const translateProp = carouselProps.vertical ? 'translateY' : 'translateX';

    const cardOffset = 18;
    const card1Scale = 0.9;
    const card2Scale = 0.8;

    const getTranslateFromScale = (index, scale) => {
        const centerFactor = 1 / scale * index;
        const centeredPosition = -Math.round(sizeRef * centerFactor);
        const edgeAlignment = Math.round((sizeRef - (sizeRef * scale)) / 2);
        const offset = Math.round(cardOffset * Math.abs(index) / scale);

        return centeredPosition - edgeAlignment - offset;
    };

    return {
        opacity: animatedValue.interpolate({
            inputRange: [-3, -2, -1, 0],
            outputRange: [0, 0.5, 0.75, 1],
            extrapolate: 'clamp'
        }),
        transform: [{
            scale: animatedValue.interpolate({
                inputRange: [-2, -1, 0, 1],
                outputRange: [card2Scale, card1Scale, 1, card1Scale],
                extrapolate: 'clamp'
            })
        }, {
            [translateProp]: animatedValue.interpolate({
                inputRange: [-3, -2, -1, 0, 1],
                outputRange: [
                    getTranslateFromScale(-3, card2Scale),
                    getTranslateFromScale(-2, card2Scale),
                    getTranslateFromScale(-1, card1Scale),
                    0,
                    sizeRef * 0.5
                ],
                extrapolate: 'clamp'
            })
        }]
    };
}

const myCarousel = (
    <Carousel
      scrollInterpolator={stackScrollInterpolator}
      slideInterpolatedStyle={stackAnimatedStyles}
      useScrollView={true} // <--- Use this for a better effect or disable it to get performance optimizations
    />
);

=> Note that you're going to get the Android effect on both platforms (inverted compared to the original iOS one).

Regarding the issue, I am left clueless. I don't understand why:

the zIndex rule randomly messes with the swipe events (sometimes you can swipe the 2-3 first items and then you need to swipe from a lower portion of the screen)
only the top part of the screen is affected
the default effect doesn't have any swipe issue even if we add the zIndex rule.

=> Any insight will be greatly appreciated!

I want right stack swipe direction, what should I need to change in animation file?


Shared logging for inference system

The inference system currently runs in Azure Container Instances. It restarts every once in a while, which is expected. However, logs are printed to stdout and lost when the container restarts.
We would like to save logs externally so they are available beyond container restarts.

No longer relevant since inference system has been moved to AKS


fix #565 : cursor motion in insert mode should affect .

Fixes most of #565 except when I click in the editor, vim-mode doesn't notice. I don't know yet how to fix that, but this PR is better than nothing I guess. 8-)

Because my fix generates an InsertCancellable operation with every arrow key motion, the history was growing quite quickly; if InsertCancellable removes itself, it's better after all.

This PR doesn't fix one part of #565: when I click in the editor, vim-mode doesn't notice. I don't know yet how to fix that, but this PR is better than nothing I guess. 8-)

I've added two tests for the new behaviour. Now the PR should be good I hope. 8-)

Rebased to current state of the art, cleaned up.

There's a bug with this PR: https://github.com/bronson/vim-mode-next/issues/4
Also, even though it's more Vim-ish, I don't like that right-arrow in insert mode no longer wraps to the next line.

Quite right, sorry about that. Working on a fix.
About the wrapping, @bronson, do I understand correctly that you have wrapLeftRightMotion off, and yet want that motion to wrap in insert mode?

Yes, I said that, but I take it back.  Sorry.  :)
That's how my workstation's Vim works -- normal mode doesn't wrap, insert mode does.  But I'm on my laptop now, and neither mode wraps.  Since I haven't noticed the difference until now (we're talking years probably...), I guess I don't care much after all.
I'll get used to whichever way vim-mode settles on.  And I definitely vote to NOT implement whichwrap!

Fixed bronson/vim-mode-next#4 , but need to postpone rebasing to master for now. This PR is related to #609 and should be considered together, and that one needs maintainer guidance.

Fix looks great!  Added this PR back to latest vim-mode-next, 0.54.15.

This PR breaks autocomplete-plus.
When the completions are shown, I hit down arrow to move to the next completion.  Instead, vim-mode:move-down-insert fires, turns off the autocompletions, and moves one line down in the buffer.

Thank you, good catch. If we find other similar interactions, we can start thinking about how to address this in a less case-by-case way.

Forgot to say explicitly: I added a fix for the autocomplete issue. 8-)

Yeah, the not(.autocomplete-active) clause might turn into not(.autocomplete-active|.doc-hints-active|.weatherbug-active|.j-random-plugin|.etc).
That said, hopefully there won't be a lot of plugins popping up distractions as I type.  Maybe this is good enough.

Yes @bronson, that's exactly the issue that one immediately imagines. I suspect, though, that due to life being how it is, interactions with j-random-plugin would need some other workaround. Notice how only up/down is in not(.autocomplete-active) and not left/right; I'm sure j-random-plugin will have a different conflicting set. As they say - one is an incident, two is a coincidence, and three's a pattern. I'd like to postpone trying to generalize until I see a pattern. If Atom provides one, I'd love to know about it.

I just realized this approach to fixing #565 isn't right - I've only taken into account arrow-key motions but not any other motions than can happen in insert mode (pgdn, end etc.). I'll redo this PR with onDidChangeCursorPosition.

Does it make sense to just fix #565 here and do the cursor motion fixes in another PR?
Also, mouse doesn't seem to interrupt insert mode either...  Just wondering if you thought about it and found the fix was too ugly.

@bronson fixing it with onDidChangeCursorPosition will be one fix for any motion, including mouse clicks. I have 30e4073c (a biggie) and #767 (a small one) in the queue before I can get to this one.

I hear that, first things first.  I was just wondering if that would be an easy way to make this PR smaller / easier to merge?
My random thinking...   I care a lot about fixing giant undos, but not much about forcing the insert cursor to stay on the same line.  (Actually, once that lands, I'm going to figure out a way to turn it off.  :)  Turns out I really do like insert mode feeling just like Atom.  I know, I'm waffling like crazy on this one!)

@bronson I'm not sure what you mean about cursor positioning there

Sorry, let me back up...   This PR does two things, right?

ensures arrow key motion (and hopefully mouse clicks) interrupt insert mode keeping undos small
restricts the cursor to the current line using keymaps now, and hopefully onDidChangeCursor position in the future

Just curious if it would help mergeability to split these two behaviors into separate PRs.  (ordered of course -- one would have to be applied before the other)

Ah I see, I'd forgotten about restricting left/right motions in case wrapLeftRightMotion is off.
I've been trying to do the interrupting of undo with onDidChangeCursorPosition but it's a huge pain - of course Atom will report a cursor position change on every input (at least it says the cursor motion was caused by text change, except backspace doesn't report the motion was caused by text change); and bracket-matcher's insertion of () when the user types ( also causes a cursor motion.
At the moment I'm thinking that some departure from VIM is warranted here - perhaps insert undo should work like normal, non-vim-mode, typing undo?
My littlest one has been keeping me busy these days but soon I should be able to make an alternate PR to show what I mean.

Sure, vim-mode undo working just like Atom undo sounds fine to me.  Atom's undo grouping used to be atrocious but seems pretty good now.  As long as the entire insert session doesn't get grouped into a single undo, I'd probably be happy with just about anything.

As stated in the README, this package is no longer maintained and is deprecated. We recommend that people use the vim-mode-plus package instead. Because of this, we are archiving this repository and closing all issues and pull requests. Thanks very much for your support and contributions!


WIP: Added directive wiring

Requires  https://github.com/graphql-java-kickstart/graphql-java-tools/pull/312

Thanks, it's part of 5.11.0.

Thanks a lot

Any example usage? To be precise, I'm trying to use that to wire graphql-java-extended-validation into my spring boot application.

@vinterdo  did it work for you? i need help with the same please.


fix(editor/#816): Implement vertical scroll bar for editor

Fix for #816 for the vertical scroll bar - leverage the mouse capture API, create a common scroll component for the editor, and hook up a Feature_Editor.msg and Feature_Editor.update for the scroll messages.

/azp run

Need to bring over to the horizontal scrollbar to call #816 fixed


504 gateway time-out error

Problem description
504 gateway time-out error received when sending notes to running phi-annotator-neuroner. Encountered the same error in both UI and using nlpsandbox python client for note annotation.
Reason: Gateway Time-out
HTTP response headers: HTTPHeaderDict({'Server': 'nginx/1.19.6', 'Date': 'Fri, 18 Feb 2022 05:12:20 GMT', 'Content-Type': 'text/html', 'Content-Length': '167', 'Connection': 'keep-alive'})
HTTP response body:
<title>504 Gateway Time-out</title>

504 Gateway Time-out

nginx/1.19.6


Suggestion

Can it be done using the gpt neo, it is better than gpt 2  and also open source?
Btw great work

The big issue as it stands right now, is that I struggle to get GPT-Neo to do what I want it to do on the experimental branch. I am also currently developing a GPT-2 345M based model called GPT-R, and it will have a sibling named GPT-X for less polite and more hardcore company.


Update bats tests to add the "release" tag

Since https://github.com/ddev/github-action-add-on-test/releases/tag/v2.1.0, user can exclude "release" tagged tests from pull request workflow.
As it is the default expected behavior, we should update the bats tests accordingly (here):
# bats test_tags=release
@test "install from release" {
...
...
}

Fixed in #58

#58 was merged so this can be closed now.

Thank you. I didn't have permission to close this otherwise I would have do it myself. :)


How to add more details on particular appointment view ?

provide a custom event view - works just like providing a custom tableviewCELL.

add subviews to the event view you provide to give all infos you want. See the swift event kit demo


Generalized interface for multivariate multiscale methods.

Describe the feature you'd like to have
With #132, we'll have a nice interface for computing any multiscale entropy or complexity measure of a timeseries x, as long as a relevant MultiScaleAlgorithm and corresponding downsample method is defined.
However, we haven't yet implemented methods for multivariate input. This is used for example in Morabito et al. (2012), where the compute the multivariate multiscale permutation entropy.
If possible, sketch out an implementation strategy
Implementing this is probably straight-forward. We just need to define downsample(::MultiScaleAlgorithm, x::AbstractDataset).
I'm just submitting this issue to remember actually doing so.
Cite scientific papers related to the feature/algorithm
Morabito, F. C., Labate, D., Foresta, F. L., Bramanti, A., Morabito, G., & Palamara, I. (2012). Multivariate multi-scale permutation entropy for complexity analysis of Alzheimer’s disease EEG. Entropy, 14(7), 1186-1202.

downsample(a::MultiScaleAlgorithm, x::AbstractDataset) = Dataset(map(t -> downsample(a, t), columns(x))...) ?

downsample(a::MultiScaleAlgorithm, x::AbstractDataset) = Dataset(map(t -> downsample(a, t), columns(x))...) ?

Excellent. This will work generically. I'll add this to #132 straight away.

Reminder: we have two existing signature for probabilities(x::AbstractVector, est::SymbolicPermutation) and probabilities(x::AbstractDataset, est::SymbolicPermutation). The multivariate approach conflicts with the latter. We need to decide on what to do about that. Perhaps it is best to replace the latter method with one that interprets each column of x as a timeseries, rather than interpreting the rows of x as pre-embedded state vectors to be symbolized.


passt: 2024_05_23.765eb0b -> 2024_06_24.1ee2eca

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for passt is: Plug A Simple Socket Transport
meta.homepage for passt is: https://passt.top/passt/about/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2024_06_07.8a83b53 with grep in /nix/store/5n2lcqn9j01kgvhrc7g26r7aiqgziyqp-passt-2024_06_07.8a83b53
found 2024_06_07.8a83b53 in filename of file in /nix/store/5n2lcqn9j01kgvhrc7g26r7aiqgziyqp-passt-2024_06_07.8a83b53

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

8 total rebuild path(s)

8 package rebuild(s)

First fifty rebuilds by attrpath

apx
apx-gui
buildah
krunvm
out-of-tree
passt
podman

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/5n2lcqn9j01kgvhrc7g26r7aiqgziyqp-passt-2024_06_07.8a83b53 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/c8a248f1de1eb64f2aac85e6e2954c2c52676606#passt

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/5n2lcqn9j01kgvhrc7g26r7aiqgziyqp-passt-2024_06_07.8a83b53
ls -la /nix/store/5n2lcqn9j01kgvhrc7g26r7aiqgziyqp-passt-2024_06_07.8a83b53/bin

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

9 packages built:

apx
apx-gui
buildah
buildah.man
krunvm
out-of-tree
passt
podman
podman.man

Maintainer pings
cc @8aed for testing.

Result of nixpkgs-review pr 318598 run on x86_64-linux 1

9 packages built:

apx
apx-gui
buildah
buildah.man
krunvm
out-of-tree
passt
podman
podman.man

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for passt is: Plug A Simple Socket Transport
meta.homepage for passt is: https://passt.top/passt/about/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2024_06_24.1ee2eca with grep in /nix/store/g9hi7aglwlclnxf2z41swvj7y9ja9239-passt-2024_06_24.1ee2eca
found 2024_06_24.1ee2eca in filename of file in /nix/store/g9hi7aglwlclnxf2z41swvj7y9ja9239-passt-2024_06_24.1ee2eca

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

8 total rebuild path(s)

8 package rebuild(s)

First fifty rebuilds by attrpath

apx
apx-gui
buildah
krunvm
out-of-tree
passt
podman

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/g9hi7aglwlclnxf2z41swvj7y9ja9239-passt-2024_06_24.1ee2eca \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/8a21839c711e70f2eef346bd284eb2c76b692a98#passt

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/g9hi7aglwlclnxf2z41swvj7y9ja9239-passt-2024_06_24.1ee2eca
ls -la /nix/store/g9hi7aglwlclnxf2z41swvj7y9ja9239-passt-2024_06_24.1ee2eca/bin

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

9 packages built:

apx
apx-gui
buildah
buildah.man
krunvm
out-of-tree
passt
podman
podman.man

Maintainer pings
cc @8aed for testing.

Result of nixpkgs-review pr 318598 run on x86_64-linux 1

9 packages built:

apx
apx-gui
buildah
buildah.man
krunvm
out-of-tree
passt
podman
podman.man


Rebuild benchmarks

This is dependent on https://github.com/JuliaGPU/gitlab-ci/pull/22
Basically the same thing as the tutorials.
TODO:

Figure out which runner tag should be used for benchmark jobs
Change a path from cdg/rebuilds to master in .gitlab-ci.yml when the JuliaGPU/gitlab-ci PR is merged

Here's a commit it made: https://github.com/SciML/DiffEqBenchmarks.jl/commit/c211b96ea685bc122e865eb45458f0d63fd4af87

Figure out which runner tag should be used for benchmark jobs

nvidia-benchmark


Added information about Haddock and LH with VSCode extension

Added settings for VSCode to disable haddock.
Added information in the readme about this need, and instructions to replicate in other repos.

Impact:

Closes Issue #1

I've merged with main. Is there anything blocking this from being merged?

Nope let’s merge!
On Tue, Oct 25, 2022 at 5:51 AM Alcides Fonseca @.***>
wrote:

I've merged with main. Is there anything blocking this from being merged?
—
Reply to this email directly, view it on GitHub
https://urldefense.com/v3/__https://github.com/ucsd-progsys/lh-plugin-demo/pull/2*issuecomment-1290505344__;Iw!!Mih3wA!GGjCpDUeU82jMUFu2DfOCdGRsdbDvUja4i7O0p-WDL_qfYx3bZS0QZXQd7tSPYlUCW229SgxsdBeCHwu7dolqvsL$,
or unsubscribe
https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AAMS4OATTXOQAGBTG7XKML3WE7JV3ANCNFSM5NZ3ZTXQ__;!!Mih3wA!GGjCpDUeU82jMUFu2DfOCdGRsdbDvUja4i7O0p-WDL_qfYx3bZS0QZXQd7tSPYlUCW229SgxsdBeCHwu7bnXScqz$
.
You are receiving this because you commented.Message ID:
@.***>

I’ll merge as soon as this finishes! LMK if you want merge access - and thanks a million !!


CUDA testing support in proj

From slack:

proj should be updated so that when someone runs proj test it checks for a GPU, and if a GPU is found it runs the GPU tests, and if the GPU is not found then it throws an error/prints an error message. An additional flag --skip-gpu-tests should be added to proj test that users without a GPU should run in order to not get that error

Also, while Dylan's command is correct, kernels currently does GPU tests in a somewhat outdated way. We're planning to move over to the model @reyna-abhyankar introduced in local-execution, where there are two doctest TEST_SUITEs, one for cuda tests and one for non-cuda tests

Eventually kernels should also be moved over to use this model

Example: https://github.com/reyna-abhyankar/FlexFlow/blob/79ef4c964fa4abebf9813166353ecce230b83c75/lib/local-execution/test/src/test_update_e2e.cc#L13

Kernels tests was added to proj. You could check here.


Option to disable healthcheck logging

With wopiserver v10 a new healthcheck was introduced in https://github.com/cs3org/wopiserver/pull/122 which causes a lot of noise. Can we have an option to disable logging for the healthcheck or move it to the debug level? IMO, creating a log entry for every single successful healthcheck call is not very helpful.

Thanks!

No problem! You're welcome to contribute a patch in such cases ;-)

Happy to do :) This issue was meant to be for discussion as it happens too often that people investigate into a PR which is getting rejected because the maintainers disagree on implementing it.

Fair enough, though this one is not an architectural change so not much contentious.
As I'm at it, I introduced this health check for the ScienceMesh deployments, as having the wopiserver "up and running" but unable to talk to Reva is basically a broken deployment.


(cygwin) Add parameter /Packages

In package Cygwin
Description
Add a param /Packages to specify packages to install
Motivation and Context
Currently this choco-package installs with '--packages default' (see chocolateyInstall.ps1#L34)
The param /Packages allows to specify additional/alternative packages.
Example of use:
choco install cygwin --params "/InstallDir:C:\your\install\path /NoStartMenu /Packages:default,curl,git,jq,lynx,patch,python39,rsync,unzip,vim,wget"

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Migrated package (a package has been migrated from another repository)

Checklist:

[x] My code follows the code style of this repository.
[ ] My change requires a change to documentation (this usually means the notes in the description of a package).
[x] I have updated the documentation accordingly (this usually means the notes in the description of a package).
[ ] I have updated the package description and it is less than 4000 characters.
[x] All files are up to date with the latest Contributing Guidelines
[x] The added/modified package passed install/uninstall in the chocolatey test environment.
[x] The changes only affect a single package (not including meta package).

:white_check_mark: Package verification completed without issues. PR is now pending human review

@me-kell We can't accept this PR while it's from your master branch. Can you move to a branch and PR from there?


Update to support Xcode 8 GM

just copied changes from Swinject

Thank you for your help to support Xcode 8 GM👍👍👍


boards: mimxrt1020_evk: Add jlinkscript init file

The mimxrt1020_evk relies on the boot ROM to configure the SRAM but when using the debugger the SRAM is not initialized. J-Link uses an init script to initialize the platform before starting the debug  session.

Codecov Report

Merging #13814 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #13814      +/-   ##
==========================================
+ Coverage   52.26%   52.26%   +<.01%
==========================================
  Files         307      307
  Lines       45410    45410
  Branches    10504    10504
==========================================
+ Hits        23733    23734       +1
  Misses      16887    16887
+ Partials     4790     4789       -1

Impacted Files
Coverage Δ

arch/posix/core/posix_core.c
91.91% <0%> (+1.01%)
:arrow_up:

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 4c77c91...2a896b3. Read the comment docs.

@dleach02 plans to update this?

Syncing with Maureen. There is probably some value in having support for scripts but it was confusing on how the rt1020 actually functioned.


setup virtual testing env

good to have a test infra which can be executed on PC/server instead of real networking hardware for development and testing.
We can use the following mechanism to emulate the hardware

TAI : stub library
SAI : vslib
ONLP : kvm driver

done


Receive heartbeat from frontend and log name

https://github.com/mdn/samples-server/tree/master/s/websocket-chat
might be helpful

https://medium.com/factory-mind/websocket-node-js-express-step-by-step-using-typescript-725114ad5fe4 could also be helpful with a step by step


grpc_php_plugin cannot be built as in quick start/tutorial for PHP

Tried following the tutorial for PHP: https://grpc.io/docs/languages/php/basics/
$ cd grpc && git submodule update --init
$ make grpc_php_plugin
make: *** No rule to make target 'grpc_php_plugin'.  Stop.
I am ultimately trying to compile my own prototype file. I tried this:
protoc --php_out=. --grpc_out=. test.proto
But this does not generate the client stub classes that I need. So I clearly need the grpc php plugin but I cannot compile it.
If I try to use the included route_guide_proto_gen.sh:
./../../../bins/opt/grpc_php_plugin: program not found or is not executable
Please specify a program using absolute path or make sure the program is available in your PATH system variable
--grpc_out: protoc-gen-grpc: Plugin failed with status code 1.

I tried using the master branch as suggested in a previous issue about this exact problem, but for me it did not work. #22108
What version of gRPC and what language are you using?
grpc 1.7.0
protobuf 3.12.4
What operating system (Linux, Windows,...) and version?
Linux

Just had the same issue. Using an older version works for me:
RUN cd /tmp && git clone -b v1.34.1 --depth 1 https://github.com/grpc/grpc && cd grpc && git submodule update --init && make grpc_php_plugin

Just had the same issue. Using an older version works for me:
RUN cd /tmp && git clone -b v1.34.1 --depth 1 https://github.com/grpc/grpc && cd grpc && git submodule update --init && make grpc_php_plugin

Thank you! That version worked for me too

We probably should update the docs. You can build it with bazel now:
./tools/bazel build @com_google_protobuf//:protoc
./tools/bazel build src/compiler:grpc_php_plugin

It could be nice if it was added to the compiled releases of protoc as well :)

Note that https://github.com/grpc/grpc/tree/master/src/php#grpc_php_plugin-protoc-plugin also need updating.

This is reporting a problem with grpc.io docs, for which there is the following issue: https://github.com/grpc/grpc.io/issues/664.
@jtattermusch @stanley-cheung - can you close this issue? We'll track it's resolution at https://github.com/grpc/grpc.io/issues/664.

Fixed by #25544 and https://github.com/grpc/grpc.io/pull/684.


pwa with angular 6 does not work

Bug Report or Feature Request (mark with an x)
- [ x] bug report -> please search issues before submitting
- [ ] feature request

Area
- [ x] devkit
- [ ] schematics

Versions

Repro steps

The log given by the failure

Desired functionality

Mention any other details that might be useful

complete details: https://stackoverflow.com/questions/50361196/angular-6-pwa-does-not-work?noredirect=1#comment87741844_50361196

This issue was moved to angular/angular-cli#12099


Fix OOM when receiving too many snapshots.

Fix the bug by limit concurrent receiving snapshot count. And some other improve:

let receiving use same CpuPool with sending.
build and consume SnapshotChunk one by one instead of keeping many chunks in channel.

Based on #2850 . Please review that first.

PTAL @overvenus @BusyJay

Now we use the same pool for send and recv, but still use DEFAULT_SENDER_POOL_SIZE to create the pool, maybe you should rename the const var name.

please rename name https://github.com/hicqu/tikv/blob/98eab7017317bf5c776492f75fd647969c27d73d/src/server/snap.rs#L314

LGTM


Create Atomic Queue

The Atomic Queue is extremely similar to the original Withdraw Queue, except for it allows users to specify a want asset as opposed to only being able to get the Cellars cellar.asset() from withdraws.
A neat side effect of doing this is that the atomic queue can be used for user deposits as well. Which means we can effectively support an ERC4626 deposit with ANY asset, evens ones outside of the ones normally supported by a multi asset deposit cellar.

Looking good, and hopefully will be straight forward for audit since it builds off of the design of the WithdrawQueue.sol.
Just some small changes in terms of spelling, and possible some regarding design.
Also, are we not going to give a new "example" solver, similar to the SimpleSolver.sol?

Thanks for the review! We will not be providing an example solver, as this solver will need to be much more complicated than what can be captured in a "simple solver" contract. It really starts creeping into the realm of MEV bot contracts.


Create CODE_OF_CONDUCT.md

Type of change

[ ] Refactor
[ ] New feature
[ ] Bug fix
[ ] Optimization
[ X] Documentation Update

Add a code of conduct from a GitHub provided template. Please make any suggestions for improvement.

https://github.com/cloud-bulldozer/.github
This is actually inherited already..

Perhaps, but I am trying to satisfy a list of requirements to get CNCF sandbox status, and we need a code of conduct within the repo.

Maybe consider using :  https://github.com/cncf/foundation/blob/main/code-of-conduct.md If this is specific to the CNCF.

Maybe consider using : https://github.com/cncf/foundation/blob/main/code-of-conduct.md If this is specific to the CNCF.

Yeh I considered using that. However reading the text of it, it doesn't seem like it is something that could be referenced by a non CNCF project. I can see a scenario where once we are accepted, we move over and just point to the CNCF guide.

Maybe consider using : https://github.com/cncf/foundation/blob/main/code-of-conduct.md If this is specific to the CNCF.

Yeh I considered using that. However reading the text of it, it doesn't seem like it is something that could be referenced by a non CNCF project. I can see a scenario where once we are accepted, we move over and just point to the CNCF guide.

ack -
No issues here... Thanks for the additional context.

@rook is this good to go?


New package: JustRelax v0.1.1

Registering package: JustRelax
Repository: https://github.com/PTsolvers/JustRelax.jl
Created by: @albert-de-montserrat
Version: v0.1.1
Commit: 6cde5ee549b301e6decbed1d3f700aa348898e97
Reviewed by: @albert-de-montserrat
Reference: https://github.com/PTsolvers/JustRelax.jl/issues/57#issuecomment-1865897793
Description: Pseudo-transient accelerated iterative solvers

Name is okay,  previous PR https://github.com/JuliaRegistries/General/pull/93491


chore: code style 2nd part

Which issues of this PR fixes ：

This PR try to fix #26
Change log

fix some TODO
add some log
othe issues about code style

please resolve conflict


Why only .jsx extension works with Vite not .js extension in React?

Describe the bug
I am trying to use Vite + React for performance optimization and faster development.  I am not too much familiar with Vite at all, but as much with React with the extension .js.
So, the problem I am facing is that when I use .jsx ext. with vite it works well, and doesn't throw any errors, but when I use .js ext. to my files in react then it throws a lot of errors can't seem to understand anything what is the reason :(
I am still facing this error:
VITE v4.3.9  ready in 8005 ms

  ➜  Local:   http://localhost:5173/
  ➜  Network: use --host to expose
  ➜  press h to show help
10:34:47 AM [vite] Internal server error: Failed to parse source for import analysis because the content contains invalid JS syntax. If you are using JSX, make sure to name the file with the .jsx or .tsx extension.
  Plugin: vite:import-analysis
  File: /home/projects/vitejs-vite-znkzfw/src/index.js:10:1
  5  |  ReactDOM.createRoot(document.getElementById('root')).render(<React.StrictMode>
  6  |      <App />
  7  |    </React.StrictMode>);
     |                         ^
      at formatError (file:///home/projects/vitejs-vite-znkzfw/node_modules/vite/dist/node/chunks/dep-e8f070e8.js:42697:46)
      at TransformContext.error (file:///home/projects/vitejs-vite-znkzfw/node_modules/vite/dist/node/chunks/dep-e8f070e8.js:42693:19)
      at TransformContext.transform (file:///home/projects/vitejs-vite-znkzfw/node_modules/vite/dist/node/chunks/dep-e8f070e8.js:40499:22)
      at async Object.transform (file:///home/projects/vitejs-vite-znkzfw/node_modules/vite/dist/node/chunks/dep-e8f070e8.js:42971:30)
      at async loadAndTransform (file:///home/projects/vitejs-vite-znkzfw/node_modules/vite/dist/node/chunks/dep-e8f070e8.js:53437:29)

If stackblitz link is not working
then you can find some snippets for this.
index.js
import React from 'react';
import ReactDOM from 'react-dom/client';
import App from './App.js'; // here extension is `.js`
import './index.css';

ReactDOM.createRoot(document.getElementById('root')).render(
  <React.StrictMode>
    <App />
  </React.StrictMode>
);

index.html
<!DOCTYPE html>

    <meta charset="UTF-8" />
    <link rel="icon" type="image/svg+xml" href="/vite.svg" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>Vite + React</title>

vite.config.js
import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'

// https://vitejs.dev/config/
export default defineConfig({
  plugins: [react()],
})

package.json
{
  //...
  "scripts": {
    "dev": "vite",
    "build": "vite build",
    "lint": "eslint src --ext js,jsx --report-unused-disable-directives --max-warnings 0",
    "preview": "vite preview"
  },
  "dependencies": {
    "react": "^18.2.0",
    "react-dom": "^18.2.0"
  },
  "devDependencies": {
    //...
    "vite": "^4.3.9"
  }
}

PS: I think it should have the possibility to get to work with all extensions (.js, .ts, etc.) means no difficulties while using it, like many people are mostly used to with it.
Reproduction
https://stackblitz.com/edit/vitejs-vite-znkzfw?file=src%2Fmain.js
Steps to reproduce
Run npm install && npm run dev
System Info
-

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I believe this is how it is suppose to work. You can only use JSX in .jsx file.

To keep it simple, https://github.com/vitejs/vite/discussions/3448#discussioncomment-5288419 will resolve your issue.
Why? vite.js does not support jsx format in .js file by default since vite covers not only jsx format but js | ts modules and is wasting time when trying to read jsx in js when you could respectively transit to jsx extension.

Hi @chaejunlee @devjiwonchoi, Thanks for your reply!

I believe this is how it is supposed to work. You can only use JSX in .jsx file.

I think you will find the answer faster by searching it up on Google.

I almost tried all the way to find answers everywhere on the internet. It should have to make some real changes in its own library by maintainers. So, it'd be better to use it easily with all extensions.

To keep it simple, https://github.com/vitejs/vite/discussions/3448#discussioncomment-5288419 will resolve your issue.

I will check it out soon! :)

Quoting Evan

The reason Vite requires .jsx extension for JSX processing is because in most cases plain .js files shouldn't need full AST transforms to work in the browser. Allowing JSX in .js files means every served file must be full-AST-processed just in case it contains JSX.


fix spelling in docs

Signed-off-by: samuel.elias<EMAIL_ADDRESS>

Coverage decreased (-0.1%) to 72.785% when pulling e16dd27de5da78c522020ebf4fe9fa5cef4fa22a on samelias:dev into a258bf5101bc9e15a24954eaca1a8bb9cb5f0494 on contiv:dev.


Maximize/minimize/fullscreen

Events:

EventWindowMaximize
EventWindowMinimize
EvenWindowFullscreen
EventWindowRestore (better name?)
EventWindowVisible(boolean)

Methods:

Window::minimize
Window::maximize
Window::requestFullscreen(boolean)
Window::restore (possible?)
Rename show -> Window::setVisible(boolean)

Window:

[ ] Windows
[ ] Linux
[ ] macOS

Windows SIZE event:

Docs link

So I guess:
EventWindowMaximize
EventWindowMinimize
EventWindowRestore
Is there a separate show/hide on Windows? Is it different from minimize?

Linux: schedule minimize/maximize events after resize