Use CommandExt::exec for cargo run on Unix (#2343)

Before, we would spawn a child process for the program. One of the
problems with that is when killing the cargo process, the program
continues running.
With this change, the cargo process is replaced by the program, and
killing it works.
Before (cargo run is the parent):

502  7615  7614   0  2:26PM ttys012    0:00.12 /Users/rstocker/.multirust/toolchains/stable-x86_64-apple-darwin/bin/cargo run
502  7620  7615   0  2:26PM ttys012    0:00.01 target/debug/program

After (the shell is the parent):

502 81649 81648   0  5:27PM ttys012    0:00.69 -zsh
502  7739 81649   0  2:26PM ttys012    0:01.27 target/debug/program

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

Thanks for the PR @robinst! The implementation looks good to me.
cc @brson, do you have thoughts on this? This causes the behavior on Windows and Unix to diverge, but in a way that makes sense to me because this is arguably the "more correct" thing to do and allows native tools like gdb and such to work if you want to debug the target process. I also suspect that we may want rustup to start taking a similar tactic where it uses exec on Unix and the same behavior as today on Windows.

@alexcrichton I recall that at least in the rustup case we decided to move back to fork/exec for a reason more than consistency with windows ... telemetry. Can't report anything if your process doesn't exist.
The problem of killing cargo transitively killing rustc can be solved in some other way too right?

Ah right, forgot about the telemetry. In Cargo's case it can't report things like termination-via-signal on Unix where it can do more fancy reporting on Windows if we implement this.
It's true that transitively killing rustc is possible on Unix with process groups (you kill the entire process group, not just the Cargo process). It's somewhat of a pain to set up though and it also doesn't allow things like debuggers/profilers to work nicely, so I don't necessarily see process killing as the only motivation here.
I'm somewhat inclined to do this as this seems a little more low level than what rustup is doing, but it also would likely have far less utility unless rustup mirrored this strategy (as cargo run by default wouldn't exec to the final process if using rustup).
I guess there's no other way to collect telemetry in rustup?

ping @brson, although this is deviating Cargo and rustup, I feel like for Cargo this is still the right choice, how do you feel about that?

I'm kinda confused on the issues here.  I thought that was standard behavior - on windows isn't that why we have the explicit group setup - so that killing cargo kills rustc?

In Cargo's case it can't report things like termination-via-signal on Unix where it can do more fancy reporting on Windows if we implement this.

Why does this patch affect the reporting on Windows?  My main desire for this is to assist debuggers where you can just run gdb --args cargo run ... and it'll fall into the relevant program eventually.

Why does this patch affect the reporting on Windows? It's a Unix-specific patch.

 This happens for Windows as well. If, however, Cargo were to exec, then it wouldn't have a chance to print that out. This means that cargo run which ran a program which printed no output and segfaulted would be up to the programmer to figure out that the segfault happened.

 This happens for Windows as well. If, however, Cargo were to exec, then it wouldn't have a chance to print that out. This means that cargo run which ran a program which printed no output and segfaulted would be up to the programmer to figure out that the segfault happened.

On Unix. Are you just suggesting that if we made this change on Unix we would also remove the reporting behavior on Windows so they have feature-parity?

Oh sorry nah I was actually just pointing out how this will introduce an inconsistency between Unix/Windows. It's probably not worth it to actively avoid printing such information on Windows when we otherwise could.

:umbrella: The latest upstream changes (presumably #3091) made this pull request unmergeable. Please resolve the merge conflicts.

Should I look into fixing the conflicts for this PR?
I probably should have explained why I created this PR: I was looking for nice way to have auto-reloading when developing server programs (e.g. an iron server). cargo watch run looks perfect for this, but it has a problem (see this issue). Without this PR, the following happens:
% cargo watch run
Waiting for changes... Hit Ctrl-C to stop.

$ cargo run
   Compiling foo-service v0.1.0
     Running `target/debug/foo-service`

# made changes to the code here, which are detected by cargo-watch

$ cargo run
   Compiling foo-service v0.1.0
     Running `target/debug/foo-service`
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Io(Error { repr: Os { code: 48, message: "Address already in use" } })', ../src/libcore/result.rs:788
note: Run with `RUST_BACKTRACE=1` for a backtrace.
error: Process didn't exit successfully: `target/debug/foo-service` (exit code: 101)
-> exit code: 101

What happens is that cargo-watch calls cargo run. It detects that files were changes, so it kills cargo run. But because cargo run uses a child process, the program still continues running. Then it invokes another cargo run, which fails because the port is already in use.
With this PR, it works nicely as expected.
So, what I currently use to get the auto reloading is entr (it manages to kill both cargo and the child process): find src Cargo.toml | entr -r cargo run

@robinst thanks for the ping! Sorry this PR has been a bit slow :(
In that specific case cargo-watch wouldn't actually want to benefit from a feature like this because it wouldn't be as robust as it could be. For example this still wouldn't work on Windows (e.g. cargo-watch would exhibit the same bad behavior there). Additionally, if the process itself spawned more children they also wouldn't be killed.
For a tool like cargo watch the processes it spawns on Unix want to be part of their own process group (e.g. setsid) and then when it kills a child it kills the process group to ensure that everything dies. For Windows it'd want to use job objects which have similar semantics to killing entire process trees.
Basically the tl;dr; is that I don't think this feature is appropriate for solving the cargo-watch problem, but I believe that this is still useful independently of that. For example it allows cargo run to work better by proxying signals to the main process. If you're developing a shell, this means that cargo run followed by ctrl-c would "do the right thing". I think this also helps debuggers by avoiding process spawns and instead sticking with the same pid.
The drawback is that while this functionality would work on Unix, none of it would work on Windows (due to the lack of exec). This means that you could have an inconsistent development experience across platforms, which is generally something we try to avoid where possible.
I'm still a bit on the fence about whether or not it's worth it here. I believe @brson felt that it may have not been, but I'm not sure whether I agree yet. So I guess to answer your question about whether this should be rebased or not, first off do you agree with what I mentioned about cargo-watch? Next, would you still be interested in rebasing for the other features this earns?

Apparently cargo watch already works as expected on Windows (haven't checked myself though): https://github.com/passcod/cargo-watch/issues/25#issuecomment-225715223
I'll rebase this PR, and maybe look into doing the process group thing in cargo watch.
Also note that just recently the watchexec tool was released, and it has the same problem: https://github.com/mattgreen/watchexec/issues/16

@bors: r+

:pushpin: Commit ed5cea5 has been approved by alexcrichton

:hourglass: Testing commit ed5cea5 with merge 9a0801d...

Ok, I think this is worth it for the debugging and "least surprise" case, so r+'ing. Thanks again!

:sunny: Test successful - cargo-cross-linux, cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64
Approved by: alexcrichton
Pushing 9a0801da0caa81653950baffabd8705d41d24d40 to master...

Thanks for merging this! Saw that the 2017 roadmap includes "Rust should have a pleasant edit-compile-debug cycle", and that is exactly what motivated this PR.
I now use watchexec like so for server development:
$ watchexec --run-initially --restart "cargo run"

It still takes 7 seconds to compile after I've made changes, but it's already better than manually restarting (and here's hoping that incremental compilation will bring down those 7 seconds in the future) :). Ideally I'd want cargo to provide the "automatically rerun after changes" functionality, but I'm not sure how that fits in with cargo's vision.


DynamoDBContext SaveAsync doesn't update empty lists

Description
When using SaveAsync from DynamoDBContext, fields that are an empty list (eg List<string>) are not included in the PUT request to DynamoDB and hence are not correctly updated.
Reproduction Steps
using System.Collections.Generic;
using System.Threading.Tasks;
using Amazon.DynamoDBv2;
using Amazon.DynamoDBv2.DataModel;
using Xunit;

namespace AntMeehan.DynamoDbSaveEmptyList;

public class SaveEmptyListTests
{
    [Fact]
    public async Task EmptyListShouldBeSaved()
    {
        // Arrange
        //  aws dynamodb create-table --endpoint-url http://localhost:8000 --table-name TestModel --attribute-definitions AttributeName=HashKey,AttributeType=S --key-schema AttributeName=HashKey,KeyType=HASH --provisioned-throughput ReadCapacityUnits=5,WriteCapacityUnits=5

        var context = new DynamoDBContext(new AmazonDynamoDBClient(new AmazonDynamoDBConfig() {ServiceURL = "http://localhost:8000"}));

        var model = new TestModel()
        {
            HashKey = "MyKey",
            MyList = new List<string>() {"Value1", "Value2"}
        };

        await context.SaveAsync(model);

        // Act
        model.MyList.RemoveAll(_ => true);

        await context.SaveAsync(model);

        // Assert
        var updatedModel = await context.LoadAsync<TestModel>("MyKey");

        Assert.Empty(updatedModel.MyList);
    }

    public class TestModel
    {
        [DynamoDBHashKey]
        public string HashKey { get; set; }

        public List<string> MyList { get; set; }
    }
}

Environment
See .csproj file:
<Project Sdk="Microsoft.NET.Sdk">
    <PropertyGroup>
        <TargetFramework>net6.0</TargetFramework>
        <Nullable>enable</Nullable>
        <IsPackable>false</IsPackable>
    </PropertyGroup>

    <ItemGroup>
        <PackageReference Include="Microsoft.NET.Test.Sdk" Version="16.11.0"/>
        <PackageReference Include="xunit" Version="2.4.1"/>
        <PackageReference Include="AWSSDK.DynamoDBv2" Version="<IP_ADDRESS>" />
    </ItemGroup>
</Project>

Resolution

[x] :wave: I can/would-like-to implement a fix for this problem myself

https://github.com/aws/aws-sdk-net/blob/master/sdk/src/Services/DynamoDBv2/Custom/DataModel/ContextInternal.cs#L228 Needs to change so it doesn't consider the length of the list.
Note this would be a breaking change in behaviour, but I can't imagine why you wouldn't want to persist an empty list (rather than a null one).

This is a :bug: bug-report

Created PR - https://github.com/aws/aws-sdk-net/pull/1997

Needs review with the team.

@antmeehan Hello, there is a special parameter you can specify in the Config called Conversion. If you set this to V2, you will be able to send empty lists. This is because by default V1 uses sets, which can't be empty while V2 uses lists which can be empty.So if you want to be able to save empty lists and send empty lists,
you need to specify V2 in your config like so:
            var config = new DynamoDBContextConfig
            {
                Conversion = DynamoDBEntryConversion.V2
            };

I'm going to close this issue out since this is not a bug, but if there's anything you'd like to add I'd be happy to reopen it :)


create a temporary home for examples in the demo app

removing merge ready label since i'm adding some more examples

Could you also restructure the directory so that it looks like
examples
   button-overview
   button-types
   checkbox-overview
   checkbox-configurable
   etc

?
That should make them easier to load by string key

Another thought- could you change the .scss styles to just .css? I want to make sure we highlight that sass isn't required to use material.

wound up adding this directly to material.angular.io instead


Check cartoview version compatibility with backward version

Check cartoview version compatibility with backward version
to be able to check apps compatibility with cartoview version

https://github.com/cartologic/cartoview/pull/120


Failed to install QLite library

I'm on MacOS High Sierra with Java 10.0.1 and Maven 3.5.4 installed. I followed the instructions, and everything worked fine until I attempted to install the QLite library:

mvn install

Here's the error I got:

Reactor Summary:
QLite 0.1 .......................................... SUCCESS [  0.879 s]
QLite : Library 0.1 ................................ FAILURE [  4.840 s]
...
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.13:test (default-test) on project qlite: groups/excludedGroups require TestNG or JUnit48+ on project test classpath -> [Help 1]

Here's a screenshot of my terminal

Thank you for reporting. "groups/excludedGroups require TestNG or JUnit48+ on project test classpath" seems to be the cause. i hope https://github.com/qubiclite/qlite.lib.java/commit/cd14753247d56b9b0a0bcf74d3bb716b79747b97 fixes that. Please retry with the modified pom.xml and report back.

It works fine after cd14753. Thanks!

I will close this issue then.


Initial prototype of Machine Learning service deployment

Depoly trained ML model to improve TRSS possible issue function
TRSS will run normally even ML server is down
ML training process is also adjusted to suit this deployment
ReadMe will be added after completing sever setup later
Related Issue: https://github.com/adoptium/aqa-test-tools/issues/355

Signed-off-by: Longyu Zhang<EMAIL_ADDRESS>

Possible Issue page with Related Degree "High" for most related issue "AssertionError with testOSMXBeanLocal":

@llxia @smlambert Could you review it? Thanks.


RemoveDuplicates: take taints and node selector into account when computing the number of duplicates

Is your feature request related to a problem? Please describe.
In case there's a cluster with 3 master nodes and 3 workers and a workload (owned by an RC) is uniformly distributed among worker nodes (the expected distribution), the strategy still evicts pods of the workload since it takes master nodes into account as well. E.g. 12 pods, 4 pods bound to each worker node, 6 pods are evicted (6 nodes, 12 pods, 2 per node) which always end up on the same worker nodes again.
Describe the solution you'd like
Take at least node taints (e.g. taints repealing pods from master nodes) into account when selecting pods for eviction. If possible, take node selector into account as well.
Describe alternatives you've considered
Not considered
What version of descheduler are you using?
The latest master HEAD
descheduler version:
Assume 0.20
Additional context

We could probably open an umbrella issue to get all strategies in line with this. I also have https://github.com/kubernetes-sigs/descheduler/issues/529 for LNU and @RyanDevlin pointed out the same with Affinity and PTS https://github.com/kubernetes-sigs/descheduler/issues/529#issuecomment-820393845

It seems like this could be implemented as a global feature in evictions.go. Maybe there could be a modification to the Evictable function to take the context of cluster nodes into account. So instead of:
func (pe *PodEvictor) Evictable(opts ...func(opts *Options)) *evictable {}

We have:
func (pe *PodEvictor) Evictable(nodes []*v1.Node, opts ...func(opts *Options)) *evictable {}

Inside this function (possibly with a call to a utility function), the node taints and pod tolerations, RequiredDuringSchedulingIgnoredDuringExecution affinity rules, and node selectors could be checked. All the strategies would most likely need to be modified after this addition to not check affinity rules or taints if they already do.
This way, the optimization is globally implemented. Thoughts on this approach?

The PodEvictor already has the list of nodes, so we shouldn't need to pass it to Evictable. So we could just enable the check using the WithOption... pattern (like in NodeAffinity)
I don't think this should be enabled by default, because we do allow evicting pods without Owners (ie, pods that won't get recreated), so in those cases whether or not a pod fits on another node is irrelevant. That means this will probably have to be exposed as a policy option

Good point, I didn't notice the PodEvictor already had that. I'm a bit confused about the second part of your comment though. As I understand we've hardcoded the IsEvictable() function in evictions.go to never evict pods without ownerRefs, no?

Any pod with the descheduler.alpha.kubernetes.io/evict annotation can be evicted, regardless of ownerRefs (checked in evictions.go

Oh right! Okay in that case, I'm happy to work on this one. Should I open another issue as a catch-all referencing this one and #529?

@ingvagabund @damemi I'm assuming this is out of scope for the issue, but I thought I'd still bring it up. Should considerations be made to the various other scheduling predicates that are used by the scheduler in filtering? For instance, with predicates like PodFitsResources or NoDiskConflict, the scheduler is able to filter out nodes that will not be able to run this pod. If we don't take that into account when evicting, there's a probability that the pod will just be rescheduled onto the same node, and we will have disrupted a workload for no reason.
On the flip side of this, maybe the descheduler is meant to be run at times when disrupting workloads is acceptable (eg. overnight), and therefore this consideration is not needed. Is this a valid concern?

Until the scheduling framework (or its key part) is completely moved under a staging repo, it will be an overkill to take into account every plugin with Filter method. We are aware of this limitation. For the moment we can only improve the estimation on how many nodes are "free" for scheduling. Eventually, the Descheduler will run a subset of the scheduler through various plugins (which will be probably configured at the startup). Though, there's still gonna be chance a pod gets re-scheduled to the same node no matter how good estimate we will make.

On the flip side of this, maybe the descheduler is meant to be run at times when disrupting workloads is acceptable (eg. overnight), and therefore this consideration is not needed. Is this a valid concern?

I like to keep this decision for consumers :)

/assign

@ingvagabund @damemi In terms of how this feature may be extended in the future, do we want the ability to selectively include some, but not all, of the filtering methods? For instance, right now I have checks for NodeAffinity, NodeSelector, and Taints. I can design the feature such that the descheduler can be configured to check for all of these, or check for a subset, like NodeSelector and Taints.
To enable all filters, this would look like:
apiVersion: "descheduler/v1alpha1"
kind: "DeschedulerPolicy"
strategies:
  "RemoveDuplicates":
     enabled: true
     params:
       removeDuplicates:
         excludeOwnerKinds:
         - "ReplicaSet"
         predicates:            <========= Here
         - "All"

To enable a subset, it would look like:
apiVersion: "descheduler/v1alpha1"
kind: "DeschedulerPolicy"
strategies:
  "RemoveDuplicates":
     enabled: true
     params:
       removeDuplicates:
         excludeOwnerKinds:
         - "ReplicaSet"
         predicates:            <========= Here
         - "MatchNodeSelector"
         - "PodToleratesNodeTaints"

I'm uncertain whether we wanted this to be an "all or nothing" parameter?

That's an interesting idea, but I would start with all or nothing for now, before going to that level of granularity (since we don't currently have any reported use cases for being that much detail)
In the future, I think at most that level of detail could simply be a top-level setting that applies to all strategies

@damemi Okay good point. For now I'll just build it as a boolean parameter for all strategies.

/assign

/unassign

/unassign


[Operator] Add cov op

PR Category
Operator
Type of Change
New Feature
Description
Add cov op
Issue
#256
Performance
Tested on NV-A100-80G

PR Category
Operator
Type of Change
New Feature
Description
Add cov op
Issue
#256
Performance
Tested on NV-A100-80G

What's the performance metric?

What's the performance metric?

I've added a benchmark to test the accuracy and performance of the covariance operation compared to Torch’s implementation:
@triton.testing.perf_report(
    triton.testing.Benchmark(
        x_names=['N'],
        x_vals=[2**i for i in range(4, 16)],
        x_log=True,
        line_arg='provider',
        line_vals=['torch', 'triton'],
        line_names=['Torch', 'Triton'],
        styles=[('blue', '-'), ('green', '-')],
        ylabel='GB/s',
        plot_name='covariance-benchmark',   # Name for the plot.
        args={'M': 1024, 'correction': 1},  # Default values for parameters other than N.
    )
)
def benchmark_cov(M, N, correction, provider):
    X = torch.randn(M, N, device='cuda', dtype=torch.float32)
    fweights = torch.randint(1, 5, (N,), dtype=torch.int32, device=X.device)
    aweights = torch.rand(N, device='cuda') + 0.1  # Avoid zeros in weights

    quantiles = [0.5, 0.2, 0.8]

    if provider == 'torch':
        ms, min_ms, max_ms = triton.testing.do_bench(
            lambda: torch.cov(X, correction=correction, fweights=fweights, aweights=aweights),
            quantiles=quantiles
        )
        result = torch.cov(X, correction=correction, fweights=fweights, aweights=aweights).cpu()
    elif provider == 'triton':
        ms, min_ms, max_ms = triton.testing.do_bench(
            lambda: cov(X, correction=correction, fweights=fweights, aweights=aweights),
            quantiles=quantiles
        )
        result = cov(X, correction=correction, fweights=fweights, aweights=aweights).cpu()

    gbps = lambda ms: 3 * X.numel() * X.element_size() * 1e-9 / (ms * 1e-3)

    if provider == 'triton':
        torch_result = torch.cov(X, correction=correction, fweights=fweights, aweights=aweights).cpu()
        precision_diff = torch.max(torch.abs(torch_result - result))
        print(f'The maximum difference between Torch and Triton is {precision_diff.item()}')
    else:
        precision_diff = torch.tensor(0.0)  # No difference for Torch itself

    return gbps(ms), gbps(max_ms), gbps(min_ms)

benchmark_cov.run(print_data=True, show_plots=True, save_path=".")

I’ve attached the results as a picture for reference. Let me know if additional details are needed!

Hello @RubiaCx , are you planning on further revise?
@tongxin Yes, I am in the process of fixing bugs, but I've been quite busy recently.

This update commit addresses the issue where the COV calculation would fail if N < 256 and N is not a power of 2. The code now ensures that BLOCK_SIZE is a power of 2, which resolves this problem.
However, I encountered an "illegal memory access was encountered" error when M exceeds MAX_GRID_NUM.

Could you please try resolve conflicts and we're able to merge this PR?


Switch from TSLint to ESLint

When running yarn install, I got a message about TSLint being deprecated in favor of ESLint (and a link to this issue).
We may be able to just use this project!

Another lib, leaflet-d3, uses eslint I think. We can mimic how it is set up.


Very strange network connection problem with bind network

Prerequisites

[x] Can you reproduce?
[x] Are you running the latest version of SoftEtherVPN?

Server with vpn server, version SoftEther VPN 4.34 Build 9745 RTM x64, on Windows Server 2012 R2.
A1 and A2 are Raspberry Pi 4 (4G mem), SoftEther is pulled here yesterday and built by the same device, on Ubuntu Server ARM64 20.04 and latest patches. Both A1 and A2 have a USB NIC.
Hub is created on server.
Both A1 and A2 have a local hub, and connect the hub to the server using cascade connection.
Both A1 and A2 bind the local hub to the eth0 (the physical nic built in Raspberry Pi 4).
Computer B1 is connected to A1 through the eth0. Computer B2 is connected to the A2 through the eth0.
IP are set static in B1 and B2.
Now, in the vpn server, I can see both B1 and B2 ip address listed in manager.
In B1 and B2 (Windows 10), the other one is visible through arp -a.
BUT: B1 and B2 cannot ping to each other.
The workaround is: Add a loopback device on the server, bind it to the hub, assign an IP address in the same subnet on the loopback device, and ping to one IP (B1 or B2) from the server. After that, B1 and B2 can ping to each other.
If B1 and B2 changed to another IP subnet, the server need to assign a new IP in the same subnet and ping once again, or it still fails in ping test.

happened again on another solution with one client in raspberry pi and another in windows.

I have read multiple times and I still don't understand your issue. Please describe it clearly, with screenshots and illustrations.

Too late. Problem solved by changing server to linux.


CDH: add en/decrypt support for eHSM-KMS

Add eHSM-KMS client to support en/decrypt operation.
eHSM-KMS related tasks mentioned in #353 will be further developed based on it.

Cool, I will check this out once we are done with the release.

Modifications to the Aliyun KMS client have been removed.

@fitzthum I have fixed these issues, thanks for your review!


Is there a way to track page index?

Each time swup makes a transition it counts as a new page. Is there a way to have the same functionality as a regular website?
Can I keep track of where the user is through an index?

Swup preserves the browser history functionality, so when the user goes back/forward, it will work the same way as browser normally does.
If you'd like to track users and their navigation through your site, I would suggest using Google Analytics together with GA plugin or GTM plugin. GA offers lots of information you could find useful.
If you like to save your data elsewhere and track users manually, you can use swup events to read window.location.href or any other information accessible in the browser at the right moment and further use it (run some code based on page / save current location to DB, etc.).
Do you have some particular use case?


[WFCORE-5121] Add ability to ignore excluded extensions to FetchMissi…

JIRA: https://issues.redhat.com/browse/WFCORE-5121
Attempts to solve the issue by passing the domain exclude info used to generate initial sync to handler doing missing config sync. This requires changing visibility of some methods, I'm not sure if there's a better way.
@jmesnil could you review please?

@yersan could you please review?

@yersan, thanks I like your idea, it makes this much cleaner :)
I made the changes in separate commit for now, let me know if it looks good and I'll squash them.

Done, thanks :)

@spyrkob thanks


Update Composer dependencies (2023-01-25-00-09)

Visual regression test passed!
View the visual regression test report


The "Files and lists service limits" section does not show any limits

The Files and lists service limits section states:
"The preceding information applies to the following resources"
but there is no limit information shown

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

ID: ce39639f-5e2c-06d6-5775-ac16a6a4828e
Version Independent ID: ce39639f-5e2c-06d6-5775-ac16a6a4828e
Content: Microsoft Graph service-specific throttling limits - Microsoft Graph
Content Source: concepts/throttling-limits.md
Product: non-product-specific
Technology: microsoft-graph
GitHub Login: @MSGraphDocsvTeam
Microsoft Alias: MSGraphDocsVteam

Thank you @diegodru for raising this issue. The limits info is defined in the linked documentation https://learn.microsoft.com/en-us/sharepoint/dev/general-development/how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online.
Hope this helps.


Draft: Native workalike to compute_tree_root in plonk::stlib::merkle_tree

NOT READY TO MERGE
This diff looks large because it is a commit before the recent rebase happening in aztec3 branch. The changes should be reapplied on top of that branch once rebase is complete.
Description
Native workalike to compute_tree_root in plonk::stlib::merkle_tree
Relevant edits here: https://github.com/AztecProtocol/barretenberg/pull/247/files#diff-0e6310ff28b85164b08ecf2373082c121d8d6e90ed942cb8a086ea83734a382bR32
Checklist:

[ ] I have reviewed my diff in github, line by line.
[ ] Every change is related to the PR description.
[ ] I have linked this pull request to the issue(s) that it resolves.
[ ] There are no unexpected formatting changes, superfluous debug logs, or commented-out code.
[ ] There are no circuit changes, OR specifications in /markdown/specs have been updated.
[ ] There are no circuit changes, OR a cryptographer has been assigned for review.
[ ] I've updated any terraform that needs updating (e.g. environment variables) for deployment.
[ ] The branch has been rebased against the head of its merge target.
[ ] I'm happy for the PR to be merged at the reviewer's next convenience.
[ ] New functions, classes, etc. have been documented according to the doxygen comment format. Classes and structs must have @brief describing the intended functionality.
[ ] If existing code has been modified, such documentation has been added or updated.

We need to call another function if we're using UltraPlonk. So you'll have to add conditional logic like:
if (plonk::SYSTEM_COMPOSER == plonk::PLOOKUP) {
    return crypto::pedersen_hash::lookup::hash_multiple({ lhs, rhs });
} else {
    return crypto::pedersen_hash::hash_multiple({ lhs, rhs });
}

if (plonk::SYSTEM_COMPOSER == plonk::PLOOKUP) {
    return crypto::pedersen_hash::lookup::hash_multiple({ lhs, rhs });
} else {
    return crypto::pedersen_hash::hash_multiple({ lhs, rhs });
}

Thanks for the feedback @suyash67! Why do we need to use different pedersen implementations here when these are native functions? What makes a native pedersen hash different when done in via ultraplonk?

Fixed here: https://github.com/AztecProtocol/barretenberg/pull/247/commits/c379a74ad0d80ea36b3738ecb1a76b5d78b61bdd

We need to call another function if we're using UltraPlonk. So you'll have to add conditional logic like:

Thanks for the feedback @suyash67! Why do we need to use different pedersen implementations here when these are native functions? What makes a native pedersen hash different when done in via ultraplonk?

Sorry for a late reply, I missed this comment. Basically, ultraplonk uses a very efficient lookup based Pedersen hash for merkle tree hashing. On the other hand, Pedersen hash using turbo plonk uses a custom fixed base gate. The output of the Pedersen when using turbo and ultra are different (because the underlying designs are totally different). That's the reason we want the conditional logic.


Get views working for creating new conversation & viewing

This is ready for review. I have a larger PR that I'm breaking into pieces for easier review. After I merge this PR in, the sidebar is in a little bit of a messed up state, but I'm going to do a separate PR that makes a few more changes to the sidebar. I restricted this PR mostly to moving files around, renaming them, and changing routes. What's included is:

[x] The root_url is now assistants#index which is a smart route that grabs your first assistant and starts a new conversation with it (later we can tweak the logic for which is your "primary" assistant)
[x] After login, you area redirected to this root_url
[x] /register is phased out in favor of /users/new (reducing the non-restful routes)
[x] Starting a new conversation for an assistant lives here: /assistants/123/messages/new. This view now works and submits to messages#create which creates a new message & and new conversation
[x] After the conversation is started, continuing the conversation lives here: /conversations/123/messages. The core functionality of this view works.
[x] These two views share a layout for messages_controller which lives in layouts/messages and inherits from the application layout

I see I have some broken tests I need to fix still.


feat: Reimplement webhooks for Voice API

The current implementation of webhooks for Voice in the com.vonage.client.incoming.* package is incomplete as described in #475. Furthermore, it requires a priori knowledge of the event type, which further devalues the classes since some form of parsing is needed to determine the correct class to map the JSON payload to. This PR aims to follow the same approach as the implementations for Messages and Verify v2: use a single class for each inbound URL. That way, the user can simply call the fromJson method on a single class based on which URL is hit, and obtain the relevant fields based on the event type.

Codecov Report

Merging #506 (f96acc7) into main (8b34038) will decrease coverage by 0.08%.
The diff coverage is 62.50%.

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #506      +/-   ##
============================================
- Coverage     94.22%   94.14%   -0.08%
- Complexity     2797     2808      +11
============================================
  Files           405      406       +1
  Lines          6748     6761      +13
  Branches        444      443       -1
============================================
+ Hits           6358     6365       +7
  Misses          203      203
- Partials        187      193       +6

Files
Coverage Δ

...in/java/com/vonage/client/voice/AnswerWebhook.java
62.50% <62.50%> (ø)

... and 2 files with indirect coverage changes


New NIFSTD curie file location and NIFMOL curie not working

Here is the new location for the NIFSTD curie yaml file:
https://raw.githubusercontent.com/SciCrunch/NIF-Ontology/master/scigraph/nifstd_curie_map.yaml
(will be made public shortly)
Bug:
curie is defined as
'NIFMOL': 'http://ontology.neuinfo.org/NIF/BiomaterialEntities/NIF-Molecule.owl#'
but for some reason it is appearing as null in scigraph
http://matrix.neuinfo.org:9000/scigraph/vocabulary/id/nlx_mol_1012006
http://matrix.neuinfo.org:9000/scigraph/vocabulary/id/nlx_mol_20090405
For comparison:
'NIFORG': 'http://ontology.neuinfo.org/NIF/BiomaterialEntities/NIF-Organism.owl#'
http://matrix.neuinfo.org:9000/scigraph/vocabulary/id/nlx_organ_110506
works with no issues.

CURIES should be unique. That CURIE map has two entries for NIFMOL:
'NIFMOL': 'http://ontology.neuinfo.org/NIF/BiomaterialEntities/NIF-Molecule.owl#'
and
'NIFMOL': 'http://ontology.neuinfo.org/NIF/BiomaterialEntities/NIF-Molecule-Role-Bridge.owl#'
Only the last one gets used.


Is there a way to force the Sections Layout to stack vertically rather than horizontally?

I am using the "Section" Layout and I am wondering if there is a way to force a vertical layout for the Sections rather then horizontal.
Thanks,
-Ray

@rantinray I will add the option in the upcoming release.

@mikhail-vl Thank you.  This plugin has been very helpful.  I really appreciate the quick feedback.
-Ray


Update all the grant handlers to support the property "EXPIRY_TIME_JWT"

"EXPIRY_TIME_JWT" property is introduced to support handling the expiry time of generated self contained access token based on incoming assertions.
If "EXPIRY_TIME_JWT" is set, when setting the expiry time for JWT token, minimum of (configuration based expiry time, value of "EXPIRY_TIME_JWT") will be set as expiry time of JWT token.
Relevant grant handlers are expected to set this property

Thank you for your contribution!
We are closing this issue since it has not been prioritized for a long time. Chances are that it has already been solved in more recent versions. If not, we will be re-evaluating this when it becomes a priority.


add sindhu.live to webring index

Hi, hoping to have my digital garden added to the webring index!
The webring icon can be found at the bottom of the about page: https://www.sindhu.live/about

Nice digital garden Sindhu, welcome to the webring :)


Improve peerDependency bumping messaging

Problem
When a package inherits a major bump from an upgraded peerDependency it's not clear what triggered the SemVer jump. For example:
"peerDependencies": {
    "bar": "^4.0.0",
  },

## 8.0.0

### Patch Changes

- [patch] abc1234: Example description of bug fix.

- Updated dependencies def1234:

  -<EMAIL_ADDRESS>  -<EMAIL_ADDRESS>  -<EMAIL_ADDRESS>
The problem at the moment is that the "updated dependencies" message is included as part of the patch notes, and there's no way to know that bar was bumped from ^3.2.0 to ^4.0.0 which is the reason why an inherited major bump occurred to make 8.0.0 of the example package above.
Proposed solution
Enhance the messaging when a peerDependency bump adjusts the version.
Something like:

## 8.0.0

### Major Changes

Updated dependencies def1234:

<EMAIL_ADDRESS>=><EMAIL_ADDRESS><EMAIL_ADDRESS>=><EMAIL_ADDRESS><EMAIL_ADDRESS>=><EMAIL_ADDRESS>
### Patch Changes

- [patch] abc1234: Example description of bug fix.

For anyone looking at this, the logic for this currently lives in the cli package.


High reindexing CPU cost while editing -e installed libraries in multi-root workspace

I am working in a multi-root workspace project with 10+ workspaces, each with its own venv and instance of pylance. Most workspaces are web applications, and consumes a common library via -e install (a poetry dependency with develop = true),  which itself is a workspace.
When editing and saving files within the common library, I have noticed that it causes all the consuming application's workspace pylance to invalidateAndForceReanalysis, even if I have none of the application's source files open. The subsequent reindexing of all the workspaces spikes CPU and freezes up my computer for up to a minute or two.
Environment data

Language Server version: 2022.1.5
OS and version: MacOS
Python version (& distribution if applicable, e.g. Anaconda): Python 3.9, using poetry

Expected behaviour
Ideally, the indexer wouldn't run for applications where I haven't open the files for. A simple change save causing a full reindexing also seems unnecessary.
Actual behaviour
Full re-indexing from every workspace's instance of pyright (10+).
Logs
[Info  - 10:09:43 AM] (35572) LibraryFile: Received fs event 'add' for path '<....>.py.5577df4034c34679659b7356775fc122.tmp'}'
[Info  - 10:09:43 AM] (35572) LibraryFile: Received fs event 'add' for path '<....>.py.5577df4034c34679659b7356775fc122.tmp'}'
[Info  - 10:09:43 AM] (35572) LibraryFile: Received fs event 'add' for path '<....>.py.5577df4034c34679659b7356775fc122.tmp'}'
[Info  - 10:09:43 AM] (35572) LibraryFile: Received fs event 'add' for path '<....>.py.5577df4034c34679659b7356775fc122.tmp'}'
# .... one for each consuming app, tmp files created when saving within vscode.

[Info  - 10:09:43 AM] (35572) LibraryFile: Received fs event 'change' for path '<...>.py'}'
# .... one for each consuming app, probably from the actual change of the library file

[Info  - 10:09:43 AM] (35572) LibraryFile: Received fs event 'change' for path '<....>.py.5577df4034c34679659b7356775fc122.tmp'}'
# ... one for each consuming app, probably from the deletion of the .tmp files

(35572) Background analysis message: markFilesDirty
(35572) Background analysis message: analyze
(35572) Background analysis message: invalidateAndForceReanalysis
(35572) Background analysis message: invalidateAndForceReanalysis
(35572) Background analysis message: invalidateAndForceReanalysis
(35572) Background analysis message: invalidateAndForceReanalysis
(35572) Background analysis message: invalidateAndForceReanalysis
(35572) Background analysis message: invalidateAndForceReanalysis
(35572) Background analysis message: analyze
(35572) Background analysis message: analyze
(35572) Background analysis message: analyze
(35572) Background analysis message: analyze
(35572) Background analysis message: analyze
(35572) Background analysis message: invalidateAndForceReanalysis
(35572) Background analysis message: invalidateAndForceReanalysis
(35572) Background analysis message: analyze
(35572) Background analysis message: invalidateAndForceReanalysis
(35572) Background analysis message: analyze
(35572) Background analysis message: invalidateAndForceReanalysis
... long indexing trace logs

Code Snippet / Additional information
I have tried adding **/*.tmp to files.watcherExclude but that doesn't seem to help. The created .tmp file still triggers the fs event

@justinttl unfortunately, currently there is no easy way to support this since each pylance servers are independent each other (one per root) and can't share indices for the changed libraries.
for now, only option you have is turning off indexing. "python.analysis.indexing": false in your setting.json file (or workspace setting file)

Hey @heejaechang, thanks for the quick response! I have taken a look at #2270 and will experiment with removing the root workspace. (for context, it was useful to have that around since we run a monorepo and a lot of the configuration and monorepo tooling is on the root workspace)
I have a question though:
Is it expected behavior that file change in a library will cause a full reindex? I have known that new file tends to cause pylance to reindex, but I am surprised to see that a save causes the same reindexing behavior.
Perhaps it is from the .tmp or .swp files created when an editor (vscode, vim) saves?

INFO level language server logs when I save a change in a common library workspace
[Info  - 10:18:42 AM] (68738) Indexer background runner(88) root directory: /Users/justinlee/.vscode/extensions/ms-python.vscode-pylance-2022.1.5/dist (refresh)
[Info  - 10:18:42 AM] (68738) Indexing(88) started
[Info  - 10:18:42 AM] (68738) Indexer background runner(81) root directory: /Users/justinlee/.vscode/extensions/ms-python.vscode-pylance-2022.1.5/dist (refresh)
[Info  - 10:18:42 AM] (68738) Indexing(81) started
[Info  - 10:18:42 AM] (68738) Indexer background runner(82) root directory: /Users/justinlee/.vscode/extensions/ms-python.vscode-pylance-2022.1.5/dist (refresh)
[Info  - 10:18:42 AM] (68738) Indexing(82) started
[Info  - 10:18:42 AM] (68738) Indexer background runner(85) root directory: /Users/justinlee/.vscode/extensions/ms-python.vscode-pylance-2022.1.5/dist (refresh)
[Info  - 10:18:42 AM] (68738) Indexing(85) started
[Info  - 10:18:42 AM] (68738) Indexer background runner(83) root directory: /Users/justinlee/.vscode/extensions/ms-python.vscode-pylance-2022.1.5/dist (refresh)
[Info  - 10:18:42 AM] (68738) Indexing(83) started
[Info  - 10:18:42 AM] (68738) Indexer background runner(84) root directory: /Users/justinlee/.vscode/extensions/ms-python.vscode-pylance-2022.1.5/dist (refresh)
[Info  - 10:18:42 AM] (68738) Indexing(84) started
[Info  - 10:18:42 AM] (68738) Indexer background runner(89) root directory: /Users/justinlee/.vscode/extensions/ms-python.vscode-pylance-2022.1.5/dist (refresh)
[Info  - 10:18:42 AM] (68738) Indexing(89) started
[Info  - 10:18:42 AM] (68738) Indexer background runner(90) root directory: /Users/justinlee/.vscode/extensions/ms-python.vscode-pylance-2022.1.5/dist (refresh)
[Info  - 10:18:42 AM] (68738) Indexing(90) started
[Info  - 10:18:42 AM] (68738) Indexer background runner(86) root directory: /Users/justinlee/.vscode/extensions/ms-python.vscode-pylance-2022.1.5/dist (refresh)
[Info  - 10:18:42 AM] (68738) Indexing(86) started
[Info  - 10:18:42 AM] (68738) Indexer background runner(87) root directory: /Users/justinlee/.vscode/extensions/ms-python.vscode-pylance-2022.1.5/dist (refresh)
[Info  - 10:18:42 AM] (68738) Indexing(87) started
[Info  - 10:18:45 AM] (68738) [IDX(90)] Long operation: scan packages (2231ms)
[Info  - 10:18:45 AM] (68738) [IDX(81)] Long operation: scan packages (2816ms)
[Info  - 10:18:45 AM] (68738) [IDX(88)] Long operation: scan packages (2424ms)
[Info  - 10:18:45 AM] (68738) [IDX(85)] Long operation: scan packages (2327ms)
[Info  - 10:18:46 AM] (68738) [IDX(87)] Long operation: scan packages (2596ms)
[Info  - 10:18:46 AM] (68738) [IDX(84)] Long operation: scan packages (2633ms)
[Info  - 10:18:46 AM] (68738) [IDX(89)] Long operation: scan packages (2853ms)
[Info  - 10:18:46 AM] (68738) [IDX(83)] Long operation: scan packages (2825ms)
[Info  - 10:18:46 AM] (68738) [IDX(86)] Long operation: scan packages (3070ms)
[Info  - 10:18:46 AM] (68738) [IDX(82)] Long operation: scan packages (3122ms)
[Info  - 10:18:55 AM] (68738) [IDX(85)] Long operation: index execution environment /Users/justinlee/Development/<...> (10158ms)
[Info  - 10:18:55 AM] (68738) [IDX(85)] Long operation: index libraries /Users/justinlee/Development/<....> (13271ms)
[Info  - 10:18:55 AM] (68738) Indexer done(85). indexed 473 files
[Info  - 10:18:56 AM] (68738) [IDX(90)] Long operation: index execution environment /Users/justinlee/Development/<.....> (10453ms)
[Info  - 10:18:56 AM] (68738) [IDX(90)] Long operation: index libraries /Users/justinlee/Development/<.....> (13402ms)
[Info  - 10:18:56 AM] (68738) Indexer done(90). indexed 473 files
[Info  - 10:18:58 AM] (68738) [IDX(88)] Long operation: index execution environment /Users/justinlee/Development/<.....>  (12319ms)
[Info  - 10:18:58 AM] (68738) [IDX(88)] Long operation: index libraries /Users/justinlee/Development/<.....> (15499ms)
[Info  - 10:18:58 AM] (68738) Indexer done(88). indexed 503 files
[Info  - 10:18:59 AM] (68738) [IDX(81)] Long operation: index execution environment /Users/justinlee/Development/<.....>  (13333ms)
[Info  - 10:18:59 AM] (68738) [IDX(81)] Long operation: index libraries /Users/justinlee/Development/<.....> (16428ms)
[Info  - 10:18:59 AM] (68738) Indexer done(81). indexed 506 files
[Info  - 10:18:59 AM] (68738) [IDX(83)] Long operation: index execution environment /Users/justinlee/Development/<.....>  (13342ms)
[Info  - 10:18:59 AM] (68738) [IDX(83)] Long operation: index libraries /Users/justinlee/Development/<.....> (16992ms)
[Info  - 10:18:59 AM] (68738) Indexer done(83). indexed 516 files
[Info  - 10:18:59 AM] (68738) [IDX(82)] Long operation: index execution environment /Users/justinlee/Development/<.....>
 (13192ms)
[Info  - 10:18:59 AM] (68738) [IDX(82)] Long operation: index libraries /Users/justinlee/Development/<.....> (17080ms)
[Info  - 10:18:59 AM] (68738) Indexer done(82). indexed 517 files
[Info  - 10:18:59 AM] (68738) [IDX(84)] Long operation: index execution environment /Users/justinlee/Development/<.....> (13579ms)
[Info  - 10:18:59 AM] (68738) [IDX(84)] Long operation: index libraries /Users/justinlee/Development/<.....>  (16988ms)
[Info  - 10:18:59 AM] (68738) Indexer done(84). indexed 516 files
[Info  - 10:18:59 AM] (68738) [IDX(87)] Long operation: index execution environment /Users/justinlee/Development/<.....>  (13906ms)
[Info  - 10:18:59 AM] (68738) [IDX(87)] Long operation: index libraries /Users/justinlee/Development/<.....> (16998ms)
[Info  - 10:18:59 AM] (68738) Indexer done(87). indexed 512 files
[Info  - 10:19:00 AM] (68738) [IDX(86)] Long operation: index execution environment /Users/justinlee/Development/<.....>  (13675ms)
[Info  - 10:19:00 AM] (68738) [IDX(86)] Long operation: index libraries /Users/justinlee/Development/<.....> (17347ms)
[Info  - 10:19:00 AM] (68738) Indexer done(86). indexed 516 files
[Info  - 10:19:00 AM] (68738) [IDX(89)] Long operation: index execution environment /Users/justinlee/Development/<.....>  (13865ms)
[Info  - 10:19:00 AM] (68738) [IDX(89)] Long operation: index libraries /Users/justinlee/Development/<.....>  (17244ms)
[Info  - 10:19:00 AM] (68738) Indexer done(89). indexed 518 files

@justinttl problem is you have multiple roots (multiple pylance servers) and each root is editable install to other roots, in other word, a library to other roots. so, when you change a file (save) in other root, other roots think there is a change in library installed, and each roots re-index libraries.
right now, we assume library changes rarely, so when a library change, each root re-index all libraries. and I believe that is what is happening here.
this won't happen if there is only 1 root (one workspace) since all packages (install -e packages) are under 1 server. but in multi root workspace case, each root has its own isolated pylance server. so it has no idea on other roots (basically other pylance servers). so when file is changed on one of root, other roots (server) will wake up and say "library change detected!" and re-index their libraries.
..
and yes, fs event below probably is the cause of making us to re-index.
[Info  - 10:09:43 AM] (35572) LibraryFile: Received fs event 'add' for path '<....>.py.5577df4034c34679659b7356775fc122.tmp'}'

..
if you change your multiroot workpace to single root workspace, these issue will probably go away.

right now, we assume library changes rarely, so when a library change, each root re-index all libraries. and I believe that is what is happening here.

I was afraid that is the case... Is there room for optimization there? Multi-root workspace lends very nicely to working on application and libraries concurrently...

if you change your multiroot workpace to single root workspace, these issue will probably go away.
We lose out a lot by not being in a multi-root workspace. The monorepo we have defines 10 microservices and shared libraries. The multi-root setup have been amazing for us in getting 100% intellisense coverage across all app's diverging dependencies in separate virtualenvs. It also makes tools like isort and pylint work well in the IDE since they are dependent on being within the venv the code is running on.

Anyhow, thank you for clarifying the behavior.
Few more question:

If I turn off indexing, do I loose intenseness and type hints?
Is there a way to configure not running pylance on certain workspaces while under a multi-root setup? (like adding .vscode/settings under a particular workspace and setting the language server to None?)

@justinttl

If I turn off indexing, do I loose intenseness and type hints?
turning off indexing won't affect intelliSense and type hints. they will still work. main thing you will lose is auto-import for third party libraries (ones you never used before) but you will still get auto-import for stdlib.

Is there a way to configure not running pylance on certain workspaces while under a multi-root setup? (like adding .vscode/settings under a particular workspace and setting the language server to None?)
you can, but turning off indexing should be sufficient for your issue.

that being said, I think we have some idea on improving this case. I will let you know once we have something working.

@heejaechang
Turning off indexing worked wonders! Thank you for the suggestion.
Feel free to close the issue, I will keep any eye out for any updates on the improvements you mentioned.

closing it as dup of https://github.com/microsoft/pylance-release/issues/2270 since new change addresses both issue.


Make strut cache global

Thanks! Please have a look at https://github.com/liskin/xmonad-contrib/commits/managedocks-global-cache, I made some additional changes, improved your commit message and added another commit.

@liskin I agree with almost all of your improvements except using refresh instead of sending messages. The point is that sending messages to inactive layouts, it's just useless(sorry, my fault), that's why I think the most right way is to use only sendMessage.

Well, I did some research and found no modules in xmonad-contrib that use messages solely for the purpose of refreshing the layout without carrying a specific change to its configuration, while there are some that use refresh. That's why I used refresh, since it's clearly simpler (by lines of code, at least).
Regarding #76, I have no idea. Does PerWorkspaceactively prevent messages being sent to the layout when it's active? Then it's a PerWorkspace bug. But it seems strange.

I think code is cleaner when something is run only when it needs to be run.

Does PerWorkspace eactively prevent messages being sent to the layout when it's active?

It prevents messages being sent to the layout when it has never been active because it retranslates message to its first sub-layout when it hasn't been run initially while it should retranslate it to the second one.

I think code is cleaner when something is run only when it needs to be run.

Okay, whatever. :-)

It prevents messages being sent to the layout when it has never been active because it retranslates message to its first sub-layout when it hasn't been run initially while it should retranslate it to the second one.

Oh. Well, I never claimed that #76 was fixed by this, anyway. Point c) in https://github.com/liskin/xmonad-contrib/commit/fab2c2ad0e1720cd97d27a41c14b30ef9464b4d8 is a different issue, one that is now fixed indeed.

@f1u77y , @liskin - Thank you, both.  I just applied the patches (from @liskin's branch) and everything is awesome again :+1:

Any chance this could be merged?
Thanks

I don't really understand the issues or changes here, but if everyone involved is happy with it and you just need someone with a commit bit to click "merge" I would be happy to.  I'll merge in a few days unless I hear any objections before then.

@byorgey c48d81e37845184b62623aa08545e23859828f86 is just an enchancement that keeps docks state in StateExtension instead of per-layout state. It should not fix any issues(but it fixes one caused by X.L.Perworkspace bug(#76); will create a ticket with more information ASAP).
Another(e38fb3bdb8bba7e09cc598fd37a06545ce18229f) enchancement is described well enough in commit message, I think.
(oh, and how did I not notice that this StateExtension should be persistent; will fix)

OK, thanks, makes sense.  I'll wait for the StateExtension fix then, ping me when you think it's ready to be merged.

Oh no, no no no.
c48d81e is everything but just an enhancement. That's the whole fix. And it too has a commit message that explains what is fixed and how.
And no, it should definitely not be persistent. If the strut cache somehow gets out of sync, an xmonad restart is all that needed to reset it. If you make it persistent, that won't be possible. Also, there's really no point in making a cache persistent, is it?

(So just to avoid any misunderstandings, I do think that it is currently ready to be merged and any additional changes may make it not ready. I did express this opinion by https://github.com/xmonad/xmonad-contrib/pull/80#pullrequestreview-120363)

@liskin
Ok got it, and I've forgot about docksStartupHook that makes PersistentExtension completely useless.
I also think that modifyXS should be moved to X.U.ExtensibleState because it's more common then just for internal usage in this module(I used exatly that function for fixing X.L.Minimize at least)

@byorgey it's ready to be merged

On Mon, Oct 24, 2016 at 6:29 PM, Bogdan Sinitsyn<EMAIL_ADDRESS>wrote:

@byorgey https://github.com/byorgey
c48d81e
https://github.com/xmonad/xmonad-contrib/commit/c48d81e37845184b62623aa08545e23859828f86
is just an enchancement that keeps docks state in StateExtension instead
of per-layout state.

This actually trades one bug for another: currently you lose the strut
cache, and therefore existing struts, on mod-shift-space.
This would stop that, but also break the workaround that replaces the
binding with one that rebuilds the cache afterward: IIRC it would keep the
old struts because it can't be cleared from the outside, and then merge a
fixed one, leaving you with a semi-broken mixture.
--
brandon s allbery kf8nh                               sine nomine associates
<EMAIL_ADDRESS><EMAIL_ADDRESS>unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net

@geekosaur as liskin mentioned, rebuilding of the cache now can be achieved by restarting xmonad

As liskin mentioned, rebuilding of the cache now can be achieved by
restarting xmonad
On 10/25/2016 09:12 PM, geekosaur wrote:

On Mon, Oct 24, 2016 at 6:29 PM, Bogdan Sinitsyn
<EMAIL_ADDRESS>wrote:

@byorgey https://github.com/byorgey
c48d81e

https://github.com/xmonad/xmonad-contrib/commit/c48d81e37845184b62623aa08545e23859828f86

is just an enchancement that keeps docks state in StateExtension instead
of per-layout state.

This actually trades one bug for another: currently you lose the strut
cache, and therefore existing struts, on mod-shift-space.
This would stop that, but also break the workaround that replaces the
binding with one that rebuilds the cache afterward: IIRC it would keep the
old struts because it can't be cleared from the outside, and then merge a
fixed one, leaving you with a semi-broken mixture.
--
brandon s allbery kf8nh sine nomine associates
<EMAIL_ADDRESS><EMAIL_ADDRESS>unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/xmonad/xmonad-contrib/pull/80#issuecomment-256115792,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKyf5bxp0hB3lf16aBO9vtBPOG3s6Fnfks5q3kaZgaJpZM4J0DFA.


Fix ExecutionConfig.dbt_executable_path to use default_factory

Description
I was seeing unit tests failing locally for dbt.test_graph.test_load_via_dbt_ls_with_invalid_dbt_path because I have dbt installed on my system and after the fix in #666 this test will fail since it fallbacks to the system dbt if it exists instead of "dbt" which the test is expecting.
This PR changes ExecutionConfig.dbt_executable_path to use a dataclass default factory for get_system_dbt so it is not called when ExecutionConfig is defined and allows us to more easily patch the shutil.which in the test so it won't fail if there is a system dbt installation.
Related Issue(s)
None
Breaking Change?
None

@jbandoro  This was released in 1.2.5 🎉

https://pypi.org/project/astronomer-cosmos/1.2.5
https://github.com/astronomer/astronomer-cosmos/releases/tag/astronomer-cosmos-v1.2.5


Enable bumping devtools versions using Dependabot

Our current way of tagging Docker images is not compatible with Dependabot when
combined with a digest. Using the latest tag until we have a better versioning
scheme.
Ref:

https://github.com/coopnorge/engineering-docker-images/issues/1253

:+1:


Fixes #71

Ensure no sub-conditions underflow (towards threshold) in the THRESHOLD-SHA-256 condition class

Signed-off-by: Pascal Avondes<EMAIL_ADDRESS>

Closing this in favor of #81, which has been merged. Please re-open or create a new ticket if you see anything amiss.


[Component] Datalist

Autocomplete text input
https://stackoverflow.com/questions/13568609/autocomplete-text-input/19779010#19779010
https://demo.agektmr.com/datalist/

Need to investigate browser support


merge_cubes fails if some attrs are different

I'm doing some tests with the client side processing and I found this bug. I am using two netCDFs with a common property, but different values (due to a recent update of the VITO back-end):
institution :
    openEO platform - Geotrellis backend: 0.9.5a1

institution :
    openEO platform - Geotrellis backend: 0.11.0a1

The error is:
MergeError: combine_attrs='no_conflicts', but some values are not the same.
The solution is easy, we just have to set the combine_attrs="drop_conflicts" (default is "no_conflicts") in the following lines:
https://github.com/Open-EO/openeo-processes-dask/blob/b037b0a3e7981c974926c4ac8fc8c552ea6fe04f/openeo_processes_dask/process_implementations/cubes/merge.py#L112
https://github.com/Open-EO/openeo-processes-dask/blob/b037b0a3e7981c974926c4ac8fc8c552ea6fe04f/openeo_processes_dask/process_implementations/cubes/merge.py#L193
@LukeWeidenwalker could you include this in the next release along with the other merge_cubes fixes?

Ah, thanks for raising this, will do!


UND_ERR_REQUEST_TIMEOUT

Bug description
We are seeing this bug after upgrading to Prisma 2.9.0 from 2.7.1
{
   clientVersion: "2.9.0"
   code: "UND_ERR_REQUEST_TIMEOUT"
  }

I can not find any information about this code or how to handle it.
Prisma is connected to a Google Cloud Postgres that is only at 20% CPU.
How to reproduce
Do not know how to reproduce it yet
It happens with a prisma.xxx.upsert
Expected behavior
That it did not supposedly timeout.
Prisma information
"@prisma/client": "^2.9.0",
Environment & setup

OS:
Database:
Node.js version:
Prisma version:

Hey @kevinsimper
Can you please try 2.10 once? If you can still reproduce this, please provide a verbose logging my enabling debug output. You can enable debug output using export DEBUG=* on unix based system

Possibly related: https://github.com/prisma/prisma/issues/3892

Closing due to inactivity.


Library name change request

Library repository URL
https://github.com/locple/LiquidCrystal_I2C_UTF8

Hi @locple. I am confirming your request.
Unlike submissions, this type of request is still handled manually. The Library Manager index maintainer occasionally comes through to clear all the outstanding requests. They will close this issue when it is done. You will get a notification from GitHub at that time.
After that, you can monitor the indexing of the library via its dedicated logs web page.
Information about that here:
https://github.com/arduino/library-registry/blob/main/FAQ.md#can-i-check-on-library-releases-being-added-to-library-manager

Done:
2024/03/21 16:48:49 Loaded 6770 libraries from DB
Removing LiquidCrystal I2C UTF8
Success!


The avatar of the user doesn't show on MainTabs of iphone

Unexpected behavior
The avatar of the user doesn't show up in the MainTabs of the Zulip mobile. This is a serious bug that needs to be fixed.
Screenshot of the app on iPhone 12

@Gautam-Arora24 I think this issue is only in ios as I have tried it in my android emulator its working fine

@Gautam-Arora24 I think this issue is only in ios as I have tried it in my android emulator its working fine

Yes @abhi0504 This issue is only popping up on iOS devices. I have also checked on android simulator and it works fine there

Yes @abhi0504 This issue is only popping up on iOS devices. I have also checked on android simulator and it works fine there

Hello! Thanks for the report.
So far, the bug seems consistent with #4365, which we believe was fixed just last Thursday in bcc135691, from #4420. Could you please pull the latest master (if you haven't already) and see if the problem persists there?
If it does, here are some questions that should help us further debug:

What version of iOS is running in the simulator?
Can you see any avatars in the app?

If so, where do you see them? Do you see them for some users and not others? Do you see them in the message list but not outside it?

Hello! Thanks for the report.
So far, the bug seems consistent with #4365, which we believe was fixed just last Thursday in bcc135691, from #4420. Could you please pull the latest master (if you haven't already) and see if the problem persists there?
If it does, here are some questions that should help us further debug:

What version of iOS is running in the simulator?
Can you see any avatars in the app?

If so, where do you see them? Do you see them for some users and not others? Do you see them in the message list but not outside it?

The bug still persists with the latest code.
Device -> iPhone 12
iOS Version -> 14.3

The bug still persists with the latest code.
Device -> iPhone 12
iOS Version -> 14.3

Hmm, fascinating. Thanks for the report!
Over on #4365, we found that this didn't appear when using Xcode 11. I currently use Xcode 11 for making releases, which means this doesn't yet affect most users. But... I only have the one Mac, so I can't upgrade to Xcode 12 without making this bug live for the next release, which makes this trickier because I can't reproduce the bug myself.
@Gautam-Arora24 Can you try the further debugging questions Chris mentioned above? That'll help us narrow this down.

Hmm, fascinating. Thanks for the report!
Over on #4365, we found that this didn't appear when using Xcode 11. I currently use Xcode 11 for making releases, which means this doesn't yet affect most users. But... I only have the one Mac, so I can't upgrade to Xcode 12 without making this bug live for the next release, which makes this trickier because I can't reproduce the bug myself.
@Gautam-Arora24 Can you try the further debugging questions Chris mentioned above? That'll help us narrow this down.

Thank you @gnprice. One piece of feedback from my side is that I can see the avatars of the user only in the message list and nowhere else.

Thank you @gnprice. One piece of feedback from my side is that I can see the avatars of the user only in the message list and nowhere else.

Linking to discussion on CZO; probably best to continue debugging in one place (there). 🙂

Linking to discussion on CZO; probably best to continue debugging in one place (there). 🙂

I think building the app from scratch on iPhone solved my problem.


Most pseudogenes have no read alignment from Paraphase output

Hello,
Thank you for developing the tool. :)
It is stated that:

Paraphase takes all reads from a gene family, realigns to one representative gene of the family and then phases them into haplotypes.

Although long reads have trouble aligning to PMS2 pseudogenes other than PMS2CL, in the paraphrase outputs, no reads align to most PMS2 pseudogenes, except PMS2CL.
Is this because paraphase was designed to consider PMS2 and PMS2CL jointly, but not jointly with the other pseudogenes?
Many thanks,
Min

Hi Min,
Paraphase is designed to consider PMS2 and PMS2CL jointly, because there is no misalignment between PMS2 and other pseudogenes. If you see misalignments to other pseudogenes, could you give an example?
Thanks,
Xiao

Hi Xiao,
Thank you for responding to me.
May I ask how you identify misalignments please?
Shown below are read alignments to the PMS2P2 and PMS2P5 genes. The alignments were sorted by mapping quality and shade by mapping quality high. In each figure, the top panel is the pbmm2 alignment, and the bottom panel is the paraphase alignment.
We can see that reads with low mapping qualities were mapped to the PMS2P2 and PMS2P5 genes by pbmm2. Reads mapping to the PMS2P2 gene have a lower mapping quality than those mapping to the PMS2P5 gene. Reads mapping to the downstream of the PMS2P5 gene, especially those spanning across the deletion, have a mapping quality of 60.
Would you consider reads with lower mapping qualities as misalignment? Perhaps those reads could have been realigned to other PMS2 pseudogenes?

Many thanks,
Min

Hi Min,
Yes the low MAPQs reflect that there are mapping issues. This is because those pseudogenes (those named PMS2P#) have high sequence similarity between each other. This is a separate problem from PMS2-PMS2CL, as PMS2-PMS2CL and PMS2P# are very different in sequence.
Paraphase is centered on genes so far, so we haven't included those pseudogene-only families. Are you interested in studying these psuedogenes even when they are not homologous to PMS2?
Thanks,
Xiao

Hi Xiao,
Could you take a look at Table 2 in this publication please? https://www.mdpi.com/1422-0067/24/2/1398
Many thanks,
Min

Hi Min,
A HiFi read is 100 times longer than a short read, so it provides much more information in alignment. Therefore, a region that has alignment problems due to sequence homology in short read data may not have any alignment problem in long read data. If you align PMS2 to the entire genome, aside from matches to PMS2CL, the remaining matches are all shorter than 4kb at a sequence similarity of 91% or lower- these are different enough and short enough, and would not create any alignment issues for HiFi reads.
If you do see any misalignment between PMS2 and PMS2P# genes, please share them here and I'd be look into it.
Thanks,
Xiao

Hi Xiao,
Thank you for developing the tool paraphase. It is a great tool, and I would love to see HiFi reads being applied to more applications. Texts are all we have now, although texts might not be the best way to communicate as all the tones and non-verbal communication are neglected. If my words came across as picky and harsh, I apologise in advance. I did not mean to.
The IGV screenshots that I showed 5 days ago are HiFi reads aligning to the PMS2P2 and PMS2P5 genes, using the default settings of pbmm2. PMS2 and its pseudogenes are called challenging medically relevant genes due to their high sequence similarities to each other. In this case, HiFi reads also had difficulty finding their unique mapping location.
I think it would be really helpful if paraphrase could expand its joint consideration from PMS2 and PMS2CL to PMS2 and all its pseudogenes. That's the only reason why I submitted this ticket in the first place.
Many thanks,
Min

Hi Min,
If your goal is to call variants in PMS2, you can use the current setup in Paraphase, It’s only necessary to consider PMS2 and PMS2CL. Other pseudogenes (PMS2P#) will not cause alignment problems in PMS2, i.e. no PMS2P# reads will align to PMS2 and no PMS2 reads will align to PMS2P#. This is because the sequence similarity between PMS2 and PMS2P# genes is low enough for HiFi reads to align correctly.
If your goal is to instead call variants in those PMS2P# genes, then we would need to add a new region definition in Paraphase so that PMS2P# genes can be considered together as a group (this group does not include PMS2/PMS2CL). This is because PMS2P# genes are highly similar in sequence to each other and there can be misalignments among PMS2P# genes, as seen in the examples you shared. Again, we do not expect misalignments between PMS2 and PMS2P# genes.
Please note that all my statements above are based on HiFi data. It’s a different story for short reads.
Thanks,
Xiao


Fix MCR Build Issues

Summary

RFCs: Link to RFC, Link to RFC, or $\emptyset$.
Categories: any of protocol-units, networks, scripts, util, cicd, or misc.

Changelog

Testing

Outstanding issues

Sadly this is failing with a new error (that fixed the old one). I am going to see if I can discover what commit of safe-smart-account was being used prior to these failures and autoupdates.
cc. @0xPrimata incase you already know


IndexError: tuple index out of range

Hi
I'm trying to do some imputation checks by masking the genotype data and it worked well with the original file but always get errors when I use the file that I added random 9(missing value) into the genotype file:
File "/home1/p314480/.local/lib/python3.10/site-packages/alphaimpute2/Imputation/BurrowsWheelerLibrary.py", line 65, in setup_library
bw_loci = np.array(range(self.haplotypes.shape[1]), dtype = np.int64)
IndexError: tuple index out of range
How could I solve this problem? Thank you!

@Sendong98 this is odd. Can you provide a reproducible example?

Of course, here's an example for the Alphaimpute example genotype file: I added random 9 and got the error during imputation.
original file (genotype and pedigree data )downloaded from https://github.com/AlphaGenes/AlphaImpute2/tree/main/example masked 10% genotype data generated by adding random missing value
command used: AlphaImpute2 -genotypes genotypes_mask10.txt -pedigree pedigree.txt -out test -writekey genotypes -onlykeyed -cycles 10 -maxthreads 12
genotypes_mask10.txt
genotypes_original.txt
pedigree.txt

I can reproduce the error on my end. And I will try to identify the cause of the error.

I have found out the cause of the error. It is because if there are a lot of '9' in 'genotypes.txt' file, 'self.haplotypes' of function 'setup_library' in file 'BurrowsWheelerLibrary.py' has shape (0,), but we use self.haplotypes.shape[1], which does not exist and leads to the error. I have now modified the function 'setup_library'.


Version 1.4.1 is incompatible with Leaflet versions older than 1.3

[x] I'm reporting a bug, not asking for help
[x] I'm sure this is a Leaflet.MarkerCluster code issue, not an issue with my own code nor with the framework I'm using (Cordova, Ionic, Angular, React…)
[x] I've searched through the issues to make sure it's not yet reported

How to reproduce

Leaflet version I'm using: ^1.4.0
Leaflet.MarkerCluster version I'm using: ^1.4.1
Browser (with version) I'm using: Chrome
OS/Platform (with version) I'm using: Linux

What behaviour I'm expecting and which behaviour I'm seeing
The latest version of Leaflet.markercluster is incompatible with Leaflet versions older than 1.3

[x] this example is as simple as possible
[x] this example does not rely on any third party code

Using http://leafletjs.com/edit.html or any other jsfiddle-like site.

this should have been resolved by >=1.5.0 versions, let me know if the problem persists.


Minimum Viable Product

See README for big picture, JSDoc for details
TODO:

[x] implement ci
[ ] implement cd
[ ] update PRODUCTION_URL placeholders

Might not be a bad idea to have someone who knows anything at all about React look at it to confirm that you're doing it right

any chance @Anbranin is willing to make a celebrity guest appearance?

Oh how I wish the SortOrder in the rest API sorted alphabetically...

Mention running npm install as part of setup for a dev environment in README

Yeah you're probably right, I was banking on it being implicit but that's probably wishful thinking

I think the border on the table should be a darker color

It's actually another piece ripped from bootstrap, so I think I'd rather stick with it


Critical Bug: Images delete all exiting editor data on adding

@JiHong88 In the latest release, when you try adding images twice, the first image gets replaced.
Steps to reproduce:

Initialize an empty editor
Add an image
Now add another image (or same image)

You will see that you still have only one image in the editor (the latest one you tried copying)
Even if you click on the enter icon on the bottom of the image and try pasting the new image, it still replaces the old image.
However, if I add a character after clicking the enter icon on the bottom of the image, the new image gets pasted fine.

The 2.33.1 version has been updated.
If this issue has not been resolved, please reopen this issue.
Thank you.


ci: refactor to one job

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

GitHub release
v1.0.0

Your semantic-release bot :package::rocket:


feat(connector): add dummy connector template code

Type of Change

[ ] Bugfix
[x] New feature
[ ] Enhancement
[ ] Refactoring
[ ] Dependency updates
[ ] Documentation
[ ] CI/CD

Description
Add template code for dummy connector and feature flags to enable and disable it.
Additional Changes

[ ] This PR modifies the API contract
[ ] This PR modifies the database schema
[ ] This PR modifies application configuration/environment variables

Motivation and Context

Closes #726.
How did you test it?

Checklist

[x] I formatted the code cargo +nightly fmt --all
[x] I addressed lints thrown by cargo clippy
[ ] I reviewed submitted code
[ ] I added unit tests for my changes where possible
[ ] I added a CHANGELOG entry if applicable

When you're opening PRs that fix an open issue, please link the issue to your PR by using one of the keywords recognized by GitHub. It makes tracking issues and PRs easier for us. For this PR, I've done it for you, please try to follow it for further PRs you open.

Hi @ThisIsMani , Is dummyconnector planned to behind a compile time feature flag? I thought the plan was to also use it as dummy connector for any customer who signs up, to experience the dashboard.

Hi @ThisIsMani , Is dummyconnector planned to behind a compile time feature flag? I thought the plan was to also use it as dummy connector for any customer who signs up, to experience the dashboard.

@ashokkjag, yes the usecase for the dummyconnector is the same as you said. I wanted to make it as an option to have the dummyconnector to be disabled using a feature flag.


Initial setup

Setup linting
Setup proof of life route
Setup jest tests
Setup ci checks

Closes: #6  & #7

Codecov Report

:exclamation: No coverage uploaded for pull request base (dev@c660f43). Click here to learn what that means.
The diff coverage is n/a.

@@          Coverage Diff           @@
##             dev      #12   +/-   ##
======================================
  Coverage       ?   85.71%
======================================
  Files          ?        1
  Lines          ?        7
  Branches       ?        0
======================================
  Hits           ?        6
  Misses         ?        1
  Partials       ?        0

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 c660f43...c7aaf50. Read the comment docs.


Support display: flex ?

react-sortable-hoc is unique in supporting display: grid (while other libraries only support vertical or horizontal direction).
Are there any plans to support display: flex ?
Demo: https://codesandbox.io/s/sortable-hoc-yp7h7?file=/src/App.js

Hi, see an example here
https://codesandbox.io/s/r18p280o?file=/src/index.js

Could someone explain please why doesn't it work in the first example but works in the second? I have the same problem as #1

@oyatek Add axis="xy" on  SortableContainer and problem solved

I found a problem, if the child element width is not fixed, it may overflow the container during the drag process, causing horizontal scrolling
https://codesandbox.io/s/sortable-flexbox-layout-with-resizable-blocks-using-react-sortable-hoc-re-resizable-forked-6kdm73?file=/src/index.js

I found a problem, if the child element width is not fixed, it may overflow the container during the drag process, causing horizontal scrolling
https://codesandbox.io/s/sortable-flexbox-layout-with-resizable-blocks-using-react-sortable-hoc-re-resizable-forked-6kdm73?file=/src/index.js

@microlabig Do you have a solution


Blue screen after loading the driver

Blue screen after loading the driver
Windows 10 1909

Error message?
Do you have an Intel processor with VT-x support enabled?

错误信息？
您是否具有启用了VT-x支持的Intel处理器？

I enabled AMD processor that supports VT-x

AMD processors do not support VT-x, it's AMD-V and hvpp does not support it, sorry.


Update whats-new.md

updated multi-turn / QnA Maker section.
added link to sample

closing this old request


ENH: Add a warning when we find comments

Comments are not valid in the most recent specification of the sample
sheet document. We show a warning and ignore that data. Without
this code processing old sample sheets would lead to an error unless the
comments were removed.

Everything looks good.

@charles-cowart if this looks good to you would you mind merging?

Thanks @charles-cowart!

On Sep 8, 2021, at 4:00 PM, Charles Cowart @.***> wrote:
Merged #14 into master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


make: *** No rule to make target '/repo/target/snitch_cluster/test/testharness.sv', needed by 'work-vlt/Vtestharness__ALL.a'.  Stop.

Hello!
In case you need help for this @jjl1075337132, this happens because you need to call make CFG_OVERRIDE=cfg/<insert config name here> rtl-gen first.
The rtl-gen recipe pre-makes all necessary components first before proceeding.


The download app section has poor or no css

The download app section has poor or no css , there are uneven gaps,
uneven alignment and these is an image that does not exist in the given path.

i can help to improve the css and make it more UI compatible.
@sunny0625 @khushi-joshi-05 I want to work on this project. So kindly assign me this issue i will work on it . Add gssoc and level label to it.


support for Unicode regular expressions

What behavior of the library made you think about the improvement?
I'm trying to restrict the output of a multi-lingual LLM to a single language (Korean), as it was trained in multiple languages and sometimes mixes them in the output.
with this regular expression:
([0-9\uAC00-\uD7AF\u1100-\u11FF\u3130-\u318F\uA960-\uA97F\uD7B0-\uD7FF\n,\s\.\']*)

I get the error:
Interegular: regex module unicode properties are not supported

How would you like it to behave?
There should be a way to restrict output to a specific language's character set.

The grammar is parsed via Lark (have a look in their docs, import unicode functionality and try again)
https://lark-parser.readthedocs.io/en/stable/grammar.html#import

It's not obvious to me why your expression fails, but generator = generate.regex(model, r'[😨]+') works. Maybe we need to update Outlines so it allows escaped unicode along with literal unicode?
Could you leave the issue open so we can address this at some point, but for now, try the literals instead? e.g. instead of \uAC00 use 가


Some characters are automatically deleted when the user types in the Properties Editor Panel

The bug appears in developer mode and can happen in http://localhost:8080. When the user types quickly in Properties Panel, some characters are randomly deleted.

Discussion 2022.05.12: Mostly solved by #1712 except numerical ones. @zuozhiw will see if numerical ones can also be solved.


MTL-2257 (part 1) Add HTTP Proxies

Summary and Scope

Fixes: MTL-2257

Issue Type

RFE Pull Request

Includes apache2 proxy configurations for Grafana, Git, Prometheus, and
Nexus.
The Nexus proxy works for the following URLs:

http://<management-vm-ip>/nexus
http://<management-vm-ip>/nexus/
http://packages/
http://packages.mtl
http://packages.mtl

Both the Grafana, and Prometheus proxies require additional changes in
metal-observability.
The Gitea proxy requires the new gitea role to be completed (MTL-2247).
The following, additional changes were included:

A templated SSL role for setting up apache2 with SSL. It still needs
additional vhosts file for our services.
conman was left out of the management-vm, now it's installed
metal-observability services were not set to automatically start, now
they are (grafana, prometheus, grok-exporter)
New cnames were added to the MTL.conf file for dnsmasq

Prerequisites

[ ] I have included documentation in my PR (or it is not required)
[ ] I have tested this by building an image using this branch HEAD, or this is does not pertain to the node-images pipeline.
[ ] I tested this on internal system or this pertains to the node-images pipeline (if yes and not build related, please include results or a description of the test)
[ ] I tested this on a vshasta system or this pertains to the node-images pipeline (if yes and not build related, please include results or a description of the test)

Idempotency

Risks and Mitigations

/backport lts/csm-1.5


TP Progress step for displaying

thanks to pheenoh for creating the github actions!

Should you delete the progress file and add a widget to the readme or is this for another PR?

@hatal175 didn't think about that rn. For now I'd prefer still keeping the progress.md file because you can see all the single rels too there. And about a json-shield widget, we might add that later


i18n support

With custom HTML support, i18n can be done by the user with their favorite i18n solutions. Won't implement for now.


Create project config option to specify base path

Due to the set up of my development environment, I can't change the PHP error log to be in the same directory as my base path.
Can you please allow for manual setting of a base path in the sublime project settings, so that my links can work?

Hi, you can use "set as base" command in the context menu in sidebar. Or do
you need something different way ?

오전 12:30에 "Rob Record"<EMAIL_ADDRESS>작성:

Due to the set up of my development environment, I can't change the PHP
error log to be in the same directory as my base path.
Can you please allow for manual setting of a base path in the sublime
project settings, so that my links can work?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/poucotm/Log-Highlight/issues/8, or mute the thread
https://github.com/notifications/unsubscribe-auth/ASUglRoV6ATjMV7c2DZKoyaZ8tdLWRZsks5suLyhgaJpZM4QA1gY
.

Thanks, I didn't know this was a possibility.
Where does it save it to? Can I allow it to save this base path to my .sublime-project file?

Hi,
The package has been updated (v1.8.3). Originally, when you select 'Log Highlight - Set as base ...' in the context menu, the path will be stored in the view settings. Now, it also will be stored in the .sublime-project file if a project file exists. When the package searches base, it will be the first candidate path.

Thank you, I really appreciate that you added this. It will make my workflow much easier when working on different machines or across multiple developers.

Hmm, the stored path is absolute. I don't think it can be used across machnes ... You may need the relative path from the top project folder, don't you?

Thank you poucotm for doing this, I will try it today.


feat: add ability to override source definition for historic version ranges

@mason-org/triage notify(Reason::NewPullRequest)
This comment ensures a notification is delivered to maintainers.
 🤖 This is an automated comment.    📖 Source code


upda

Summary
Details and comments

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: FabianaCampanari:x: ImgBotAppYou have signed the CLA already but the status is still pending? Let us recheck it.

We will not be adding your sponsor link to this project.  This is your second attempt on this repository, and it's not appreciated.  If you continue to send such PRs, you will be blocked from interacting with the Qiskit organisation.


Physics based animations

Problem or feature description
First, just wanted to say what a wonderful library this is and thank you for making it! I'm coming from using animated and react-motion and have read the comparison, but was curious if there are any plans for physics based animations? Would it possible to allow other libraries like wobble to be plugged in? I'd be willing to help with whatever and submit a PR, please let me know.

Have you tried using https://GitHub.com/TannerLinsley/Springer? It can
achieve a physics-based-like animation in time based animation
environments. The actual technical difference between time based and
physics based animation logic is the way the system handles interruption.
On Sun, Nov 12, 2017 at 1:46 PM Travis Arnold<EMAIL_ADDRESS>wrote:

Problem or feature description
First, just wanted to say what a wonderful library this is and thank you
for making it! I'm coming from using animated and react-motion and have
read the comparison, but was curious if there are any plans for physics
based animations? Would it possible to allow other libraries like wobble
https://github.com/skevy/wobble to be plugged in? I'd be willing to
help with whatever and submit a PR, please let me know.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/react-tools/react-move/issues/33, or mute the thread
https://github.com/notifications/unsubscribe-auth/AFUmCaOpdP-hFf6wKIIR6qNRHcfoyCyzks5s11kMgaJpZM4QbCQK
.

Yes I have :) sorry, I should have mentioned that. I'd like to be able to have better interruptible animations. Is there any way to do have both options in react-move or would it take too much rearchitecting?

That's a question for @sghall
On Sun, Nov 12, 2017 at 6:40 PM Travis Arnold<EMAIL_ADDRESS>wrote:

Yes I have :) sorry, I should have mentioned that. I'd like to be able to
have better interruptible animations. Is there any way to do have both
options in react-move or would it take too much rearchitecting?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/react-tools/react-move/issues/33#issuecomment-343787744,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFUmCQ_tZIjwJSW0CyGe-JM5J9atnakKks5s1539gaJpZM4QbCQK
.

@souporserious I think it would be great to support these types of animations.  It would require some work, but I believe it's possible we could make some tweaks and support both styles. If you want to do a little leg work on this, that would be awesome.  Would definitely would welcome a PR.
Off the top of my head. I think for physics based animations (you may actually know better than I do) you really want to stop ticking when some criteria is met (e.g. the value has reached the goal value or velocity === 0) rather than a specific elapsed time.
Looks like wobble, for example, does a check like this:
https://github.com/skevy/wobble/blob/develop/src/index.js#L390
And is called here:
https://github.com/skevy/wobble/blob/develop/src/index.js#L364
(I just took a quick look so take this with a grain of salt)
In react-move checking is done here:
https://github.com/react-tools/react-move/blob/master/src/core/transition/schedule.js#L124
Not sure what all would be involved from there, but seems like it would be possible.  Need to consider interrupts carefully I suppose.
Be interested to see what you come up with.

Awesome, sounds good! I only know a little bit about how it works, but I'm up for the challenge. I'll work on a PR as soon as I get some time. Thanks for the info!


Added function to show line number

The function shows the line number of the first error/warning that appears in the current buffer. If there are 20 warnings and the first warning exists on line 33, then vim-airline would show W:20(L33).
One can change how the line number is represented using: g:airline#extensions#ale#open_lnum_symbol where the default is (L and airline#extensions#ale#close_lnum_symbol where the default is ). I don't know if a variable that lets the user toggle seeing the line number or a toggle seeing the line number of the last warning/error in the buffer would be worthwhile additions.

please squash into a single commit and make the required changes. Thanks.

@chrisbra @w0rp please check the changes I have made.

thanks!


[SPARK-8922] [Documentation, MLlib] Add @since tags to mllib.evaluation

Can one of the admins verify this patch?

Can one of the admins verify this patch?

@mosessky There are other methods under each class. Could you also help check their since versions? Thanks!

@mengxr I add in more @since tags. Hope this time I add them correctly.

Can one of the admins verify this patch?

ok to test

@coderxiang Could you help review this PR? Thanks!

Merged build triggered.

Merged build started.

Test build #37958 has started for   PR 7429 at commit 59dc104.

Test build #37958 has finished for   PR 7429 at commit 59dc104.

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

Merged build finished. Test PASSed.

@mosessky I made one pass, and found only one issue commented inline. Besides it, could you also add since tags to constructors? Thanks!

@mengxr I've added in contructors' since tags.

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

test this please

Merged build triggered.

Merged build started.

Test build #40648 has started for   PR 7429 at commit e2db571.

Test build #40648 has finished for   PR 7429 at commit e2db571.

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

Merged build finished. Test PASSed.

LGTM. Merged into master and branch-1.5. Thanks! @mosessky Could you ping me on the JIRA page so I can assign the ticket to you? Thanks!

@mengxr Sure. I will do that right now. Thanks for the guide.


This commit resolves #98 so custom location can forward to custom path.

This PR resolves #98 sub-folder forwarding.

Docker Image for build 1 is available on DockerHub as jc21/nginx-proxy-manager:github-pr-99-amd64


Update weapons.json

Added Camo Arms BGH

Whoops - been busy ingame so haven't seen half of this. Added this on https://github.com/euloggeradmin/LootNanny/commit/d377a75ffce478739ac2eeb299257cb4044bac31


Command line support

Add/reintroduce the support to import catalogs via the command line interface and allow passing arguments via the command line.
Ideally, the commands and arguments would mimic the lsd example shown here https://github.com/mjuric/lsd/wiki/Release-Notes-v0.5.3, to simplify onboarding of previous users of lsd.

Additional info: This is the type of operation we're trying to make runnable via the command line https://hipscat-import.readthedocs.io/en/latest/catalogs/public/index.html


<EMAIL_ADDRESS>hash check failed

Installing 'openssh' (7.6p1) [64bit]
gcc-libs-6.4.0-1-x86_64.pkg.tar.xz (821.9 KB) [===============================================================] 100%
Checking hash of gcc-libs-6.4.0-1-x86_64.pkg.tar.xz ... ok.
heimdal-1.5.3-9-x86_64.pkg.tar.xz (546.6 KB) [================================================================] 100%
Checking hash of heimdal-1.5.3-9-x86_64.pkg.tar.xz ... ok.
heimdal-libs-1.5.3-9-x86_64.pkg.tar.xz (592.7 KB) [===========================================================] 100%
Checking hash of heimdal-libs-1.5.3-9-x86_64.pkg.tar.xz ... ok.
icu-59.1-1-x86_64.pkg.tar.xz (7.3 MB) [===============================================================>       ]  90%
Checking hash of icu-59.1-1-x86_64.pkg.tar.xz ... ERROR Hash check failed!
App:         openssh
URL:         http://repo.msys2.org/msys/x86_64/icu-59.1-1-x86_64.pkg.tar.xz
First bytes: FD 37 7A 58 5A 00 00 04
Expected:    d64bbf81b569b322f428cc4a18071991abca4b0d56c2ec2ce74052348d2b2e7a
Actual:      b259a660e662ae7457a4129f54b46515acb03fc9c36d708347082a5ae341a8a8
Please try again or create a new issue by using the following link and paste your console output:
https://github.com/lukesampson/scoop/issues/new?title=openssh%407.6p1%3A+hash+check+failed
PS C:\Users\xekri> scoop install openssh
ERROR It looks like a previous installation of openssh failed.
Run 'scoop uninstall openssh' before retrying the install.

Actually, I think I goofed. I just noticed that the download didn't finish. Sorry.


Fix the defineClass exception in camel-quarkus-jsonpath while running in native mode

How to reproduce:
Set false in integration-tests/jsonpath/pom.xml
Run mvn clean verify -P native
An issue where the @Deleted defineClass method would be accessed is reported.

Thanks @lburgazzoli for discussing the case.
I will try adding the jsonb extension, or then find what to substitute in order to cut the possibly false unreachable code path detection.

looking a little bit into this issue you probably need to substitute:

net.minidev.json.JSONValue
net.minidev.json.JSONWriter

Something like:
@TargetClass(JSONValue.class)
class JSONValueSubstitution {

    @Substitute
	public static void writeJSONString(Object value, Appendable out, JSONStyle compression) throws IOException {
		if (value == null) {
			out.append("null");
			return;
		}
		Class<?> clz = value.getClass();
		@SuppressWarnings("rawtypes")
		JsonWriterI w = defaultWriter.getWrite(clz);
		if (w == null) {
			if (clz.isArray())
				w = JsonWriter.arrayWriter;
			else {
				w = defaultWriter.getWriterByInterface(value.getClass());
				if (w == null)
					throw new UnsupportedOperationException("...")
			}
			defaultWriter.registerWriter(w, clz);
		}
		w.writeJSONString(value, out, compression);
	}
}

@TargetClass(JSONWriter.class)
class JSONWriterSubstitution {
    @Delete
    static public JsonWriterI<Object> beansWriterASM;
}

Not sure it it is enough but the issue is that the library tries to generate classes in case it does not find a suitable writer.
An potential future evolution would be to generate such classes at build time.


refactor selecting and dragging tools

much of the utility of the selecting and dragging files currently in SingleEdit and UnifiedEdit in feature/343 are more broadly applicable to any type of editing interface. Move them into the utils folder and make sure that all the dependencies still work while having the behaviour of these classes/modules generally applicable

done in #370


Prepare for 1.6.3

I think we should use conventional-changelog because CHANGELOG should be generated automatically;)
https://github.com/conventional-changelog/conventional-changelog
@sotarok What do you think?

@abouthiroppy  That looks nice.
Should we comply the commit comment if we use conventional-changelog?

Yeah, we should set a rule for conventional-changelog.
I recommend an angular style because many projects adopt it.
FYI: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit


Can't Set CV_CAP_PROP_BUFFERSIZE

Problem
Given an unknown source framerate and unknown frame processing time for each frame, we want to be able to always grab the most recent frame at the time of a read() call. In contrast to traditional process-every-frame stream workflows, which opencv-python seems to have been designed  around.
Ideally we could follow cap.set(CV_CAP_PROP_BUFFERSIZE,1) and then always have the most recent frame available. Unfortunately, contrary to this suggestion, we don't appear to be able to set this property in Python:
In : cap.set(cv2.CAP_PROP_BUFFERSIZE,1)
Out: False

It appears everyone tries to manually flush the buffer themselves e.g. 1 2a 2b
Current Workaround
As a workaround, I parameterized the buffer skipping rate. So users of this package still have to be conscious of their source framerate and set a flush rate accordingly.
Possible Solutions
Some options to consider to fix this:

Find out how to set the CAP_PROP_BUFFERSIZE property for OpenCV.
Use another thread to spool frames as quickly as possible. This is no ideal as we don't want to force every user into multithreading situations, especially when OpenCV supposedly has this capability already.

I have also notice that `cv2.CAP_PROP_BUFFERSIZE,1) does not work.

This seems feature seems essential for live machine learning workflows.

On my Raspberry Pi project, cv2.CAP_PROP_BUFFERSIZE, 1 does actually work, but it means there's still a buffer of 1 that needs to be cleared before reading a live image. cv2.CAP_PROP_BUFFERSIZE, 0 is what I have been trying to get to work, and it does work on my Mac and Windows PCs.