Fix redundant roads.

Overmind is often building 2 or 3 roads between the same startPos and andPos.
Solution: RoadPlanner's costMatrix needs to contain existing roads as well as roads planned (even if planned during the same tick). Weight existing and planned roads in a way so new roads are only built if truly beneficial.

This is already the intended mechanic with it being truly beneficial already

How is this beneficial?
http://666kb.com/i/e26ptiycxpp8fcczy.png
http://666kb.com/i/e26ptpk41pdfgd972.png

It's not that the path is redundant, it's due to being the same length and cost when re-pathing the road after cache is cleared

Then just give really existing roads (in the Screeps world) a slightly lower weight in the cM when re-pathing? Where is the issue? We save 100s of ticks and energy ...

The roads shown in that room are not redundant because only one path is actively maintained. We discussed the future solution in Slack -- new road network logic will be introduced in a future update which will include changes to transporter logic, link placement, and road routing.


Bevy code example

Seeing that the repo is tagged with bevy I took a stab at using it along with Bevy, but I'm kind of stuck... The problem is essentially that I am expected to tick the BT and apply all action logic inside the closure passed to tick:
pub fn tick<E, F>(&mut self, e: &E, f: &mut F) -> (Status, f64)
    where
        E: UpdateEvent,
        F: FnMut(ActionArgs<E, A>, &mut BlackBoard<K>) -> (Status, f64),
        A: Debug,
{}

This means, like the example given under lib.rs, I am suppose to check the action enum I defined and do w/e I need to do there, for example:
let (_status, _dt) = bt.tick(&e, &mut |args, blackboard| match *args.action {
    Actions::Inc => {
        acc += 1;
        (Success, args.dt)
    }
    Actions::Dec => {
        acc -= 1;
        (Success, args.dt)
    }
});

In Bevy, this result in a monolithic system that tries to do everything... so afaik, a system with exclusive world access that looks something like:
fn tick_bt_tree(world: &mut World){
    let mut system_state: SystemState<(
        Res<Time>,
        Query<(Entity, BT)>,
    )> = SystemState::new(world);

    let (time, query) = system_state.get_mut(world);
    let e: Event = UpdateArgs { time.elapsed().to_f64() }.into();
    for (entity, bt) in &mut query {
        let (_status, _dt) = bt.tick(&e, &mut |args, blackboard| match *args.action {
            Actions::Inc => {
                // get data from `world`
                // but we can't do this because we're already borrowing `world` mutably
                (Success, args.dt)
            }
            // ...similarly for other actions
        }
    }
}

Like the comment added, I essentially can't access the same world that I retrieved the BT from since it's mutably borrowed (system_state is a piece of data mutably borrowed from world).
...This feels kind of like a dumb question but it's something that I nevertheless couldn't figure out. Not familiar with this repo but since it's tagged with bevy would it make sense to add something that could explain how someone would go about using it with bevy?

It is a good point. I just clone my BT before ticking it and then assign the cloned BT to override the BT that is inside a bevy component.
I think you may be able to avoid cloning if you wrap your BT inside an Option type in your bevy component and then use std::mem::take to transfer the BT value out of the bevy component to a temporary variable right before ticking the BT inside your bevy system. There might be more ergonomic ways to do the same thing but this should give you the general idea:

#[derive(Clone, Copy, Debug)]
enum AI {
    A, B
}

#[derive(Component)]
struct CompA {
    bt: Option<BT<AI, ()>>
}

#[derive(Resource)]
struct Resource1 {
    value: f32
}

fn tick_bt_tree(world: &mut World){
    let mut system_state: SystemState<(
        ResMut<Resource1>,
        Query<(Entity, &mut CompA)>
    )> = SystemState::new(world);

    let (
        mut resource,
        mut query
    ) = system_state.get_mut(world);

    let e: bonsai_bt::Event = UpdateArgs::zero_dt().into();
    for (entity, mut comp) in query.iter_mut() {

        // pull BT out from component (if it is there):
        if let Some(mut bt) = std::mem::take(&mut comp.bt) {
            let (_status, _dt) = bt.tick(&e, &mut |args, blackboard| {
                match *args.action {
                    AI::A => {
                        resource.value = 55.0;
                        (bonsai_bt::Running, 0.0)
                    }
                    AI::B => {
                        (bonsai_bt::Running, 0.0)
                    }
                }
            });

            // give BT back to component:
            comp.bt = Some(bt);
        }

    }
}


Add CoScale as monitoring solution for ACS with Kubernetes.

@fryckbos,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

@rgardler @dlepow Hi Ross or Dan. This pull request has new content for Container Service. Can you or someone on your team work to move the content to the private repo and then close this pull request? Thanks.

@fryckbos - Thanks for the contribution! We'll be happy to migrate this over to our private repo and start the publishing process there. Before we do, a couple suggestions: 1. Please provide more background on CoScale features/benefits (and link to features), perhaps compared with other monitoring solutions. 2. Provide image of what customer sees when they successfully deploy and use product. See these article for examples::
https://docs.microsoft.com/en-us/azure/container-service/container-service-monitoring-dynatrace
https://docs.microsoft.com/en-us/azure/container-service/container-service-kubernetes-sysdig
@squillace @sauryadas - FYI

Thanks for the quick response. I have added a bit more information about CoScale and I also added some screenshots. Let me know if there are other things you would like me to add / change.

@fryckbos - Thanks for adding the information and screenshots. I'll close this PR and migrate the content  over to our private repo. I'll plan to reach out to you in a few days to have a look again before we publish.
#please-close

@dlepow Excellent, looking forward to it !


.tsconfig.json not working

VSCode Version: 1.23.1
OS Version: Windows 10 x64

Steps to Reproduce:

code --disable-extensions

Create .tsconfig.json in project root:

Create ./src/test.js:

Result: type checking not working
Expected Result: check types as with // @ts-check:

try it by jsconfig.json?

My bad, there should be not dot in front of tsconfig.json


RFC [process]: SIG docs-community assignment during triage

Summary
Prior to June 2022, there was a regular meeting owned by sig-release which was for the assignment of SIGs to issues which were recently filed, in order to sort them per-SIG for triage. This process has now been deprecated, meaning that each SIG is responsible for triaging the O3DE repo on their own, examining needs-sig issues and determining if they own it (and who the ultimate owner may be.) One consequence of removing this meeting is that downstream SIGs such as UI/UX and Docs-Community is that there is no longer a global triage for those SIGs to participate in, and instead individual SIGs will be required to identify when a downstream SIG will be affected by their work.
As a consequence, we need formal guidance for "when do you apply the sig/docs-community label?" during triage sessions. Without early engagement of documentation for certain features or product issues,
What is the motivation for this suggestion?
SIG assignment triage is ending, and being delegated as part of the responsibility of individual SIG triage sessions.
Suggestion design description
The following is a draft for discussion of the guidelines which would be given to SIGs for assigning the sig/docs-community label or assigning docs-community reviewers to pull requests.
When should SIG Docs-Community be informed of an issue?
There are only a few incoming issues where SIG Docs-Community needs to be engaged:

If an issue is kind/bug, Docs-Community does not need to be engaged, unless the bug resolved has a written workaround in official documentation. A user fixing a consequential enough bug that previously required a workaround is expected to follow the Impactful Change requirements for documentation (TBD) to evaluate their bug fix against the documentation.
Issues involving deprecation must always include sig/docs-community so that we can correctly identify any deprecated documentation outside of API reference.
If an issue was mistakenly filed against the o3de repo and relates strictly to documentation, it should be moved to the o3de.org repo and re-labeled to include needs-triage for the docs sig. We will occasionally review O3DE repo items which have not had a SIG assigned or been triaged.
Feature requests which are QoL improvements or would be primarily documentation-oriented, such as requests for full game templates and samples (i.e. a request for a 3rd person shooter sample to be bundled with O3DE.)
Features which are reaching a stage of maturity where the Docs-Community SIG needs to be aware of the current feature state and progress, in order to assist with documentation or help the SIG plan for anything else required.
Features where a quick grep of the website source reveals a large number of impacted files; i.e. renaming a core component, modifying a core feature behavior, or some other work that has an outsized impact. Often this would be considered an "Impactful Change" but for large enough impactful changes, you should err on the side of engaging with SIG Docs-Community. It's easier for us to say "no" than for us to play catch-up later when we should have said "yes".

The SIG does not need to be informed of new feature work when it comes in as an issue - the SIG should be engaged at the RFC stage. For new features SIG Docs-Community should be involved early, to help establish what is needed to meet the minimum viable content guidelines for docs (TBD) and if there is any specialized content that the SIG can help produce or would request as part of the submission (such as sample code or projects.)
When should SIG Docs-Community review a PR?
On most code reviews, you will not need a dedicated reviewer from SIG Docs-Community. The only time you should request a reviewer from our pool is:

You have a question about how the PR impacts documentation which was not considered when triaging the issue
A large amount of user-facing text is impacted in the PR (i.e. you have rewritten a significant number of tooltips for an Editor-facing Component). The exact amount that makes a "large amount" is intentionally nebulous; a good metric is that if "most" or "all" of a file's text has changed, or you anticipate that it will change over a series of pull requests to address a single core issue, make sure that SIG Docs-Community is involved.
Somebody from our SIG has explicitly requested addition as a reviewer

Mitigation of critical misses
A "critical miss" would be considered any issue which:

Does not have sig/docs-community as a label on the issue or pull request
Would be ranked as priority/critical or higher by SIG Docs-Community

While we're unlikely to have a critical miss under the suggested guidelines, we require a mitigation plan in the event that there is one. The proposed plan is to:

Engage with the SIG which did not correctly identify the issue, and ensure that they had access to the guidelines.
Cover the guidelines with the offending SIG to determine if there was a gap in the description of when sig/docs-community should be labeled as a stakeholder of the issue or PR, and make any appropriate amendments to the triage guidelines.
Schedule the identified work under the appropriate priority/X label (priority/critical or priority/blocker, by definition). Docs contributor bandwidth is extremely low, and so even high priority items are likely to languish.

What are the advantages of the suggestion?
sig/docs-community is identified as a stakeholder by other SIGs, preventing us from having to attend and participate in every other individual SIG triage.
What are the disadvantages of the suggestion?
Relies on the best judgement of other SIGs to correctly identify stakeholders. This has two major consequences:

SIGs must be aware of our guidelines for involvement, and follow them.
The Docs and Community SIG will inevitably be left off of a critical item that we should be stakeholders for, and we must have a mitigation plan.

How will this be work within the O3DE project?
During individual SIG triage sessions, the group will be required to evaluate the incoming issues affecting them on documentation, following these guidelines. This will be an additional process overhead to SIG triage but is preferable to every other alternative.
Scope of work
The definition of the process to be followed during triage is in this document. The remainder of work will be:

Formalize this document into something inside of the SIG repo itself
Communicate information to stakeholder SIGs that they are now required to follow this process if they would like the involvement of sig-docs-community

Are there any alternatives to this suggestion?

A member (or members, or rotating group, or however it is "assigned") of sig-docs-community is responsible for attending every other SIG triage.
Do nothing; sig-docs-community is no longer a "stakeholder group" on any O3DE work and focused solely on issues reported to o3de.org.

What is the strategy for adoption?

Produce a formal document for the SIG describing when we should be tagged on issues reported to the o3de repo.
Communicate to SIGs through Discord and the mailing lists that they are now responsible for following this guidance.
Provide availability of Docs-Community members to voluntarily attend triage sessions during an early period of implementing this process (the first 30-45 days) and assist SIG members with understanding the new guidelines.

We should bring this up again, possibly the o3de/community repo is a good place to have this conversation. I think some parts of this guidance can be revived - specifically about providing guidance on when and how to involve sig-docs-community during triage.
Note, this code review guidance references this issue for guidance: https://github.com/o3de/community/blob/main/guides/o3de-code-review-guidelines.md
Closing, @sptramer can you revisit this issue and restart the conversation in o3de/community repo?

We should also require adding sig-docs-community for any code PRs about deprecation


Demo 2 Goals

Demo 2 should build on the first demo and show concrete progress towards the three exploration goals of KCP:

A minimal kube-apiserver as a library that can be forked and easily customized in code at the necessary layers
Transparent multi-cluster of Kube-native applications that preserves 95% of existing developer expectations
Kube-like control plane as a service enabling developer team infrastructure self-service (under policy control!) that scales horizontally

Demo 2 would be a Kubecon or post-Kubecon update of the current demo and validate progress towards these goals.
Minimum demo

Minimal kube-apiserver

User can fork a repo in our tree (kcp-dev/kubernetes) and assemble a simple go build able main function that starts a new kube-apiserver and defines hooks
TODO: exactly what the interfaces look like (should do a session and sketch something)

Transparent multi-cluster

Flow

Start kcp with two kind clusters
Switch to a logical cluster
Create a deployment
Show the deployment not assigned with a condition 'Unschedulable' (no locations)
Create a location and expose it to the logical cluster (somehow)
Scheduler places the workload, syncer agent on the kind cluster performs the spec down -> status up dance
Add a second location
Stop the first kind cluster
Show the deployment moved

Parts

Add ingress to a single deployment with a single hostname, show traffic flowing to whichever kind cluster has the deployment

Policy, organizations, and sharding

Show an "organization workspace" that you can create Workspace kinds in
Show creation of Workspace gating the ability to access to a workspace
Create a controller that LIST/WATCH across a resource in all workspaces and does useful work
Create a Shard type, add assignment to a shard to a Workspace object, then show LIST/WATCH across two independent KCP instances

Show the same controller from above working unchanged

WIP script doc: https://docs.google.com/document/d/1jN6BdhUUIESeHw3_f6HwsNwVM2Ytabr6usUQhYMcNd8/edit#


Initial validation state of a required select fields is always invalid

When marking a select field as required, I'm seeing that the initial state of the field is always invalid.  Here is a demonstration of this issue. Additonally, here  is an example of an equivalent form using angular-formly-bootstrap which does work correctly.
Notice that on initial load, the select field in the material variant has "$valid": false,. Re-selecting the same option from the select dropdown then results in the label being marked red, since the field has now been touched.  Finally, selecting a different option results in validation working correctly henceforth.

After digging into this a bit more It looks very likely that this is an upstream issue with angular-material -- I will confirm and update this issue appropriately.
angular/material#8699

I can confirm that this was an issue within angular-material.  Updating to the the latest in master resolved it.
angular/material#8666


swappable dims

Description
This PR adds support for swappable dims for the image layer (so far) - need to propagate changes to all layers. It adds a swap_display method to the dims object that will swap the display state of the dimensions - see here for usage:

@pranathivemuri - this will have implications for our support of 3D rendering for all layer types. we can work together on anything you're doing around the points layer.
Type of change

[x] New feature (non-breaking change which adds functionality)

How has this been tested?

[x] add new example/swap_dims_image.py

Final checklist:

[x] My PR is the minimum possible work for the desired functionality
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works

I'll note that right now you can't swap XxY to appear as YxX but that is probably desirable too, might need to think of a different way to do this using a vispy transform, but that can come later

Swappable dims now works with the Points layer too:

Changes in this PR also add compatibility for 3D points, but there are some clear vispy issues we need to solve (not how the size of the points changes depending on the view angle), and the selection tools cause errors, and the add tool might not behave as expected. Fixing these problems isn't a goal of this PR, but I wanted to make sure any changes to enable swappable dims were compatible with this usage mode:

This PR now adds swappable dims to all layers apart from the Shapes layer (note this is different from 3D viewing).
For the Shapes layer we need to think about what our shapes should do when we swap dimensions as right now shapes are fundamentally 2D. The more I think about this the more I wonder if we shouldn't do some projection magic like we do in the Vectors layer - this will may make our path towards 3D shapes easier too. Thoughts @jni?
For now though I think we should review this PR as is and we can the focus on the shapes layer and other 3D stuff in the future. Thoughts @royerloic @kne42 @pranathivemuri ?

This PR now adds swappable dims to all layers apart from the Shapes layer (note this is different from 3D viewing).

That's great!

For the Shapes layer we need to think about what our shapes should do when we swap dimensions as right now shapes are fundamentally 2D. The more I think about this the more I wonder if we shouldn't do some projection magic like we do in the Vectors layer - this will may make our path towards 3D shapes easier too. Thoughts @jni?

Even if shapes are only drawn  in 2D, they can still be thought as 3D objects.
When changing the displayed dimensions -- in any case really -- we always show
a 2D or 3D projection or slice of these objects. Slicing is preferred  of course because
that's what we do for images. Of course much easier said than done.
For points it is rather simple, for polygons it gets more difficult. But, we could for example
show the 1D section of a polygon which just means drawing a series of lines.
Projections make sense for vector fields because slicing a vector is a bit uninteresting...

For now though I think we should review this PR as is and we can the focus on the shapes layer and other 3D stuff in the future. Thoughts @royerloic @kne42 @pranathivemuri ?
I agree.
Shapes would have to be extended to meshes, and that becomes very difficult in arbitrary
dimensions. A possible approach is to build all nD shapes by nD simplices (plural of simplex)
which are essentially: triangles (2D),tetrahedra (3D), n-simplex (nD). We might want to take a more pragmatic path and just support adhoc shapes in 2D and 3D. What does the 'Guardian of  Dimensions'
@jni think about that ?

Great job getting the 3D points to work, I was making similar changes in my branch seems like you beat me to it - https://github.com/napari/napari/compare/master...pranathivemuri:pranathi-points
We should discuss the polygon shapes in 3D layers for sure. Do we want to support ROI selection in 3D based on the shapes, it might be cool. but I am not sure how exactly shapes layer should be modified to support that just yet. The selection tool error is related this as when we select now, it draws a square in 2D, but in 3D we should be doing a cube.
Either way, we should merge this PR as is and write notes/todos to fix stuff in points layer to support 3D stuff so we can approach them in the next PR.

I've addressed the changes requested by @kne42 and this PR is now ready for re-review. It now supports transposing axes within the displayed axes by switching the dims model to using (None, None, 0, 1) like representations as suggested by @royerloic. To change the displayed axes you should use the dims.swap method that will swap two axes.
An alternative api would be to have two variables, ndisplay which is either 2 or 3 depending on 2D or 3D mode and order which is a tuple of length ndim that contains the order of the dimensions where the last 2 or 3 are displayed and the order of the others corresponds to the order of the sliders, so if you had order = (2, 0, 1, 3) and ndisplay = 2 then we'd display the 1st and 3rd axis as Y x X. This might actually be a lot cleaner ... maybe I'll do one more refactor!! But can @royerloic, @jni or @kne42 weigh in first?

superseeded by #450

I've addressed the changes requested by @kne42 and this PR is now ready for re-review. It now supports transposing axes within the displayed axes by switching the dims model to using (None, None, 0, 1) like representations as suggested by @royerloic. To change the displayed axes you should use the dims.swap method that will swap two axes.
An alternative api would be to have two variables, ndisplay which is either 2 or 3 depending on 2D or 3D mode and order which is a tuple of length ndim that contains the order of the dimensions where the last 2 or 3 are displayed and the order of the others corresponds to the order of the sliders, so if you had order = (2, 0, 1, 3) and ndisplay = 2 then we'd display the 1st and 3rd axis as Y x X. This might actually be a lot cleaner ... maybe I'll do one more refactor!! But can @royerloic, @jni or @kne42 weigh in first?

So actually I like your proposal, right now the scheme [None, None, 1, 0] mixes two things: (i) what is displayed, (ii) axis ordering. That's bad. The dims model design principle is to avoid mixing things because, for example, the 'None' entries obfuscate the order of the underlying axis which means that you can't change what axis are displayed without 'erasing' information. So yes, I like the idea of the number of axis displayed separately from the ordering of axis.  Great idea.
A slight variation would be to have instead of a number of displayed axis an actual set of axis. This provides maybe an even clearer separation between the two aspects, you can reorder the axis however you want, and then pick a set of two axis to display (e.g. {2,3}), the set does not carry order, that is the job of the permutation list (e.g. [2,0,1,3] ). This gives the freedom to reorder displayed or not displayed axis (think slider order too) independently of which are chosen for display.  So you could for example, permutate slider axis without messing with which axis are displayed. What do  you think?

Thanks. I’ve gone ahead and implemented the new scheme on #450 and closed this PR. I think the number of displayed is working fine, but we’ll see comments after review


gate inclusion of pico.h in binary info, so as not to break picotool or other non SDK builds

fixes regression due to #693


[daw-json-link] update to v3.7.0 and dependency

Library name: daw-json-link to release v3.7.1
Also, one of it's two dependencies need to be upgraded prior/at the same time
daw-header-libraries to v2.75.0
New version number:
[daw-json-link] v3.7.1
[daw-header-libraries] v2.75.0
Other information that may be useful (release notes, etc...)
https://github.com/beached/daw_json_link/compare/v3.1.1...v3.7.1
Highlights

Loosened pessimization on MSVC in some cases where it doesn't show bug
Cleanup of assert code
Fixes to allow cygwin compilation of tests
Bugfix https://github.com/beached/daw_json_link/issues/334
Bugfix https://github.com/beached/daw_json_link/issues/336
MSVC's slow uncaught_exceptions prompted a fix that also only uses at_exist_success code when needed by type(req's RVO as it cannot be copies/moved)
Fixed requirement on JSON Schema export

can this be changed to daw-json-link v3.7.1, a bug came up that was fixed

@beached Thanks for your survey, I will complete the update today. :)

@FrankXie05 Thanks.  I hope it is ok that I changed the original version from 3.7.0 to 3.7.1 a last moment bug came up that is fixed in 3.7.1
What survey?

@beached About the Highlights you mentioned.


Difficult decision maker

Student, group: Бурьянов Дмитрий, 3530901/90202
URL: https://github.com/theburyat/DecisionMaker
Git approach: git-flow

`+


Discrepancy in output length with special characters

With
echo "mÃ" > /tmp/a

With our implementation:
$ cat /tmp/a| ./target/debug/coreutils wc  -L -l
      1      2

With GNU:
$ cat /tmp/a| /usr/bin/wc -L -l
      1      1

Found with the wc differential fuzzer

I can't reproduce this issue locally. GNU wc returns the same result as uutils wc:
$ echo "mÃ" > /tmp/a
$ cat /tmp/a | /usr/bin/wc -L -l
      1       2

try with a different local ?
like with LANG=C ?

I tried LC_ALL=C, LANG=C and LC_COLLATE=C, but no difference. And based on the doc of -L I would expect it to return 2 because there are two characters.

@sylvestre Do you still have the file somewhere? I suspect that this is just an encoding issue, because I can't reproduce it either. For reference, here's my /tmp/a:
$ hexdump -C /tmp/a
00000000  6d c3 83 0a                                       |m...|
00000004


Wiktor Walentynowicz profile added.

https://app.netlify.com/sites/kio/deploys/5ffd50009ffb37000842ace8
YAML zepsuty

https://app.netlify.com/sites/kio/deploys/5ffd50009ffb37000842ace8
YAML zepsuty


Add integration test for table aws_ecs_container_instance

Is your feature request related to a problem? Please describe.
Add an integration test for the existing table.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

terraform resource is not available , with CLI also facing issue.
https://turbothq.slack.com/archives/G01PK0XKPRQ/p1620862906011000


Add classification template

Part of tutorial#1456
Description
Add a classification template
Status
Ready
Please ensure all the checkboxes:

[x] Codeformat tests passed locally by running ./runtests.sh --codeformat.
[ ] In-line docstrings updated.
[ ] Update version and changelog in metadata.json if changing an existing bundle.
[ ] Please ensure the naming rules in config files meet our requirements (please refer to: CONTRIBUTING.md).
[ ] Ensure versions of packages such as monai, pytorch and numpy are correct in metadata.json.
[ ] Descriptions should be consistent with the content, such as eval_metrics of the provided weights and TorchScript modules.
[ ] Files larger than 25MB are excluded and replaced by providing download links in large_file.yml.
[ ] Avoid using path that contains personal information within config files (such as use /home/your_name/ for "bundle_root").

/build

Hi @KumoLiu looks good! I had a few points about how transforms are being applied but it works for you so it's just a best practice thing. One other suggestion is to have a common.yaml file with all the common definitions in it (eg. network_def), then include that when doing things like training. I hadn't done that for the segmentation template because I wanted to maintain compatibility with the current version of MONAILabel. Here we don't need to worry about that so we can change things now to have a common file or leave it for a future refactor.

Hi @ericspod, I didn't get the point of why we need the common.yaml. I see you created an issue here and also mentioned it in the dev meeting. But seems we don't need to specify the common field in multiple configs, we only need to add what we want to override in the evaluate.yaml or inference.yaml or other configs.

After reading again the configs, I think I get the points. It makes sense if we add a common.yaml but every time we may need to specify multiple configs due to the existence of common.yaml.
Perhaps we could refactor it later when we reach a consensus. What do you think?

I'm good to refactor later, it's something we will likely do for both template bundles. I had recommended having a common config file in this bundle tutorial but it's not necessary.


Incorrect approach (overlay vs extension)

This phrase is not correct (or I don't understand the wording correctly):  "Create a project that belongs to the model where you must add the new label extension. For this example, the project is named ApplicationSuite."
Creating the label on the model where the label exists assumes overlayering. A new model (or an existing custom one) that references the original model must be used as an extension, as explained here: https://docs.microsoft.com/it-it/dynamics365/unified-operations/dev-itpro/extensibility/customization-overlayering-extensions#label-extensions

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

ID: 233d83d4-b489-a31d-40da-35e4e29dc901
Version Independent ID: ef9ca1d6-0af5-1a8e-31a7-b71bdc8a3dbf
Content: Change a label - Finance & Operations | Dynamics 365 | #MSDyn365FO
Content Source: articles/dev-itpro/extensibility/change-label.md
Service: dynamics-ax-platform
GitHub Login: @smithanataraj
Microsoft Alias: smnatara

@jaestevan The following topic should have information that clears up the confusion. https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/extensibility/customization-overlayering-extensions#label-extensions


XamlTypeInfo not getting updated when switching git branches

Visual Studio version: 16.10.3
I have a repo that has two branches with different features. In short words, in master branch, the exe project references 1 class library project. In develop branch, it references 1 more.
This only happens for 0.8.x. Doesn't happen for 0.5.x.
When switching from develop to master, the XamlTypeInfo contains types only in develop branch and causes build error. When switching from master to develop, there's no error, but every control in the additional project silently won't load.
Only rebuilding the exe project updates XamlTypeInfo.g.cs.

@alwu-msft FYI


Consider alternative ORM rather than Prisma

Prisma doesn't use native SQL JOIN expressions for queries, which leads to poor performance on relational queries.
At the very least, this should be made clear as a drawback, and directions for replacing prisma with an alternative database client would be welcome.

I only have experience using Prisma.

Unfortunately I have not found another ORM that has syntax as nice as prisma... but prisma's performance on anything beyond simple CRUD non-relational queries is truly horrendous and there's no way (or plan from the team) to fix it.
I personally use Drizzle because I approach my applications from a database-first mindset and when I want data, I think through the SQL queries necessary to get it in the format I need, rather than thinking on the entity level like prisma. It gives me lots of flexibility to do fancy stuff like e.g. given an entity ID, get that entity and the row after it in an ordering:
const init = tx
    .$with("init")
    .as(
      tx
        .select({ surveyId: surveySection.surveyId, index: surveySection.index })
        .from(surveySection)
        .where(eq(surveySection.id, sectionId))
    );
  const [section, nextSection] = await tx
    .with(init)
    .select()
    .from(surveySection)
    .leftJoin(init, sql`TRUE`)
    .leftJoin(survey, eq(survey.id, surveySection.surveyId))
    .where(and(eq(surveySection.surveyId, init.surveyId), gte(surveySection.index, init.index)))
    .orderBy(asc(surveySection.index))
    .limit(2);

This query calculates the index (unique order column for my case) of the passed-in ID, then uses that to select the first two rows with that index or greater, which gives me the row I want and the row after in a single efficient query.
This is far more efficient than the corresponding Prisma code, where the only option is to select with a JOIN (which would issue two sequential queries) for the initial entity, then issue another select afterward for the next entity in the ordering. Not only is this inefficient for the database to compute, but you now pay the cost of the api server -> database latency three times over. But I totally understand people not wanting to drop down to SQL manipulation at this level :)
Kysely and Drizzle are both more query builders than ORMs. I would suggest TypeORM if you want a higher level of abstraction with model classes, relational CRUD, etc that still offers performance using SQL native functionality.

Thank you! 😄 I'm going to look into it.

+1 for Drizzle: great DX and great performance


Added verbose as an option

Added a way so verbose can also be turned on by supplying and option, updated code and readme.

This should be a part of the logger instead of every gulp plugin having to implement this option: https://github.com/gulpjs/gulp-util/issues/33


Add loginctl_linger_users fact

Pull Request (PR) description
Add a fact listing users with linger enabled.
As near as I can tell from the systemd source, root is always able to linger even it not setup explicitly.
This Pull Request (PR) fixes the following issues

Generally not in favor of adding facts like this, particularly on widely used modules. A function or resource may be more appropriate.
That said, what's an sample use case?

My overall plan is to feed this value back into
systemd::logind_settings:
    KillExcludeUsers:

So my users with linger will have the ability to trivially persist processes.
Pat

I'm confused, isn't that redundant if touching a /var/lib/systemd/linger/ file is the same as adding  to KillExcludeUsers in the logind conf file?

I'm confused, isn't that redundant if touching a /var/lib/systemd/linger/ file is the same as adding to KillExcludeUsers in the logind conf file?

Maybe a slight difference:
I guess enable linger will stop things being killed that are running in the systemd --user scope however all other user processes would be killed. Better to encourage users to run long lived processes  in the correct context if they want them to survive.
I'm kind of worried about this fact as it would be pretty large in our case.

If this fact looks to be too much, I can always run it out of one of my private modules.  Just figured I'd default to "share with the community".

I'm kind of worried about this fact as it would be pretty large in our case.

Agree. My basic objection to a fact like this.

No worries, I'll close this out and run the fact privately.

If I was going to do this and am actually thinking about it I would not rely on puppet to maintain that list. I'd set up a path unit and service and sync /var/lib/systemd/linger entries to KillExcludeUsers settings.


[Feature Request] Export and import requests as curl.

Overview
Chrome browser has a feature to copy a request as curl. It would be great if it was possible to then import this request into insomnia and have all of the fields populated. And it would be great if it was possible to get the same export feature as in chrome, right click on request in insomnia and choose copy as curl.

Well @Euphorbium, I have good news for you. Both of these are already possible!
You can import a Curl command by pasting it into the current request's URL bar, and you can export as curl using the Generate Code feature.

Let me know if you have any questions.

@Euphorbium any ideas on how to make that feature more obvious?

Pasting Curl is referenced in the Data tab in Preferences. It might be worth having a dedicated button during the "Create Request" flow to paste a curl command, though.

Also, that's a good point about curl not being code. I agree with that statement as well.

Just added a couple things

@gschier sorry to comment on a closed issue, but I was wondering if it is or would be possible to export the authentication cURL?

Very confused. I keep pasting my cURL into the URL bar but it doesn't do anything special

@Euphorbium any ideas on how to make that feature more obvious?

I was searching for this feature and this issue was where I learned how this works. Of course now it is clear for me. And, pasting to URL works flawlessly for me as well, both "cmd" and "bash" flavors.
(@dginovker : please provide curl command which does not work, might help solving the issue).
Also, created little PR on this: https://github.com/Kong/insomnia-docs/pull/103
But just as an idea:

As a user I normally would like to add new request from copied cURL, so that dropdown item would create new request and get content from clipboard.

As well as not being obvious, pasting into the url bar results in really poor error handling / feedback if there is a problem with the curl. It also looks like a real mess if the curl is large + multiline.
Being able to paste into a dedicated multiline text area with clear feedback if the command can't be parsed would be preferable.

Today i faced with the problem, that the pasted curl request copied from chrome, can't import above the url bar


Test

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

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


enh: Enhance UI of Add Project section

Description

Enhanced the UI of the Add Project section, according to the Figma design.

Issue Ticket Number
Fixes #170

Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[x] I have followed the contributing guidelines of this project as mentioned in CONTRIBUTING.md
[x] I have checked to ensure there aren't other open Pull Requests for the same update/change?
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes needed to the documentation

Congrats @its-ayush-07 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow this steps.

Star this repository. ⭐

SignIn / SignUp in [ClueLess Website](https://www.clueless.tech/) .

Go to profile section from the top right hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard !
And don’t forget to share your achievement with your friends.

@Debajyoti14 https://www.clueless.tech/profile/admin/110535490894696020512


How disable some options

In some case I need to show some options in disable mode, how can i do this?

+1, based on our research this isn't possible...

We found no method for achieving this, so we switched to  ng2-select2, but this needs Jquery and Select2 as Dependencies in Project.

Still can't be done?

My feature is blocked due to same issue. I have to disabled few options and I am unable to find any solution. Anyone find the solution?


data-sort-value clearing 0 values

I`m using data-sort-value for integers and prices, but any value of 0 or 0.00 is being cleared, resulting in:
data-sort-value=""
This means that price lists that contain 0.00 don`t sort properly.
Superb plugin btw, thank you.

 :(


Redisson hibernate entity cache TTL and MaxIdleTime not being set - default region used for entities 2nd level cache

Redis version
latest from Docker
Redisson version
3.20.1
Redisson configuration
hibernate.cache.redisson.entity.expiration.time_to_live=120000
hibernate.cache.redisson.entity.expiration.max_idle_time=180000
hibernate.cache.redisson.entity.eviction.max_entries=200
What is the Expected behavior?
cache should be cleared from redis
What is the Actual behavior?
Cache is not clearing after time is elasped
Additional information
added the sample project in the existing issue : https://github.com/redisson/redisson/issues/1929

You need to set settings like below:
spring.jpa.properties.hibernate.cache.redisson.entity.expiration.time_to_live=120000
spring.jpa.properties.hibernate.cache.redisson.entity.expiration.max_idle_time=180000
spring.jpa.properties.hibernate.cache.redisson.entity.eviction.max_entries=200

Also you need to remove the setting below:
spring.jpa.properties.hibernate.cache.provider_class

@org.hibernate.annotations.Cache(usage = CacheConcurrencyStrategy.READ_ONLY, region = "employee")
public class Employee { //should be expired after 2 hours
}
spring.jpa.properties.hibernate.cache.redisson.employee.expiration.time_to_live=1200000
spring.jpa.properties.hibernate.cache.redisson.employee.expiration.max_idle_time=1800000
spring.jpa.properties.hibernate.cache.redisson.employee.eviction.max_entries=2000
i can use this way ? @mrniko i was referring to this https://github.com/redisson/redisson/issues/4670 .. let me know your thoughts

@abdulwhd964
The settings looks fine


ExecutionPayloadValidator generic over block

Describe the feature
Make ExecutionPayloadValidator generic over block. Either using PhantomData for a block type, or using a generic for block on method signatures that contain SealedBlock so it can be generalised as SealedBlockFor<B>
https://github.com/paradigmxyz/reth/blob/c553b1e86d8200effda90fff5711870fb25642d1/crates/payload/validator/src/lib.rs#L19-L185
Additional context
No response

I don't think we can do this because this type performs the ExecutionPayload -> Block conversion. This is abstracted through https://github.com/paradigmxyz/reth/blob/3d5b1657ab846d579da3b7f225b6303670b8be31/crates/engine/primitives/src/lib.rs#L86-L103
For ExecutionPayloadValidator we could make it generic over transaction thus allowing to convert to the Block<T> type, but entire primitives won't be useful here


feat: partial context info

This PR facilitates augmenting the context of an InfoTree with partial contexts while elaborating a command. Using partial contexts, this PR also adds support for tracking the parent declaration name of a term in the InfoTree. The parent declaration name is needed to compute the call hierarchy in #3082.
Specifically, the Lean.Elab.InfoTree.context constructor is refactored to take a value of the new type Lean.Elab.PartialContextInfo instead of a Lean.Elab.ContextInfo, which now refers to a full InfoTree context. The PartialContextInfo is then merged into a ContextInfo while traversing the tree using Lean.Elab.PartialContextInfo.mergeIntoOuter?. The partial context after executing liftTermElabM is stored in values of a new type Lean.Elab.CommandContextInfo.
As a result of this, Lean.Elab.ContextInfo.save moves to Lean.Elab.CommandContextInfo.save.
For obtaining the parent declaration for a term, a new typeclass MonadParentDecl is introduced to save the parent declaration in Lean.Elab.withSaveParentDeclInfoContext. Lean.Elab.Term.withDeclName x now calls withSaveParentDeclInfoContext x to save the declaration name.
Migration
The changes to the InfoTree.context constructor break backwards compatibility with all downstream users that traverse the InfoTree manually instead of going through the functions in InfoUtils.lean.
To fix this, you can merge the outer ContextInfo in a traversal with the PartialContextInfo of an InfoTree.context node using PartialContextInfo.mergeIntoOuter?. See e.g. Lean.Elab.InfoTree.foldInfo for an example:
partial def InfoTree.foldInfo (f : ContextInfo → Info → α → α) (init : α) : InfoTree → α :=
  go none init
where go ctx? a
  | context ctx t => go (ctx.mergeIntoOuter? ctx?) a t
  | node i ts =>
    let a := match ctx? with
      | none => a
      | some ctx => f ctx i a
    ts.foldl (init := a) (go <| i.updateContext? ctx?)
  | _ => a

Downstream users that manually save InfoTrees may need to adjust calls to ContextInfo.save to use CommandContextInfo.save instead and potentially wrap their CommandContextInfo in a PartialContextInfo.commandCtx constructor when storing it in an InfoTree.
Motivation
As of now, ContextInfos are always full contexts, constructed as if they were always created in liftTermElabM after running the TermElabM action. This is not strictly true; we already create ContextInfos in several places other than liftTermElabM and work around the limitation that ContextInfos are always full contexts in certain places (e.g. Info.updateContext? is a crux that we need because we can't always create partial contexts at the term-level), but it has mostly worked out so far. Note that one must be very careful when saving a ContextInfo in places other than liftTermElabM because the context may not be as complete as we would like (e.g. it may lack meta-variable assignments, potentially leading to a language server panic).
Unfortunately, the parent declaration of a term is another example of a context that cannot be provided in liftTermElabM: The parent declaration is usually set via withDeclName, which itself lives in TermElabM. So by the time we are trying to save the full ContextInfo, the declaration name is already gone. There is no easy fix for this like in the other cases where we would really just like to augment the context with an extra field.
The refactor that we decided on to resolve the issue is to refactor the InfoTree to take a PartialContextInfo instead of a ContextInfo and have code that traverses the InfoTree merge inner contexts with outer contexts to produce a full ContextInfo value.

I've added full-ci, as we're going to need to update ProofWidgets4 to get this tested.


Migrate to react.js or vanilla js

Hi,
Just want to know if percircle support angular 2/4?

Hello @hirwandzahir ,
thank you for your interest in percircle!
To be honest, I do not see this happening for the near future, since I don't have the required time capacity, at the moment.
However, I would be happy to review a pull request that does so.

It's been a while, but I feel like asking this question.
If we're talking about a potential investigation of porting percircle to one of the modern frameworks, what should that be? What would best serve the purpose of this project?

Angular?

React?

Vue.js?

What does the community think about it?

I feel this project is not suited to modern frameworks because the approach and toolset doesn't suit them.
It is uncommon to use jQuery these days as newer js frameworks are transpiled and modern javascript can easily handle a lot of what jQuery does.
Alongside the decoupling of jQuery there would need to be a fair bit of refactoring to be a bit friendlier for integration - e.g. the individual options should be able to be adjusted without having to re-render the entire control (e.g. percent), this is a particular concern for React.

Thanks a lot for your input, @chris--jones .
Moving to react.js sounds indeed right at the moment.
Would you like to pick this up?

I am also time poor at the moment, I will revisit if I get a chance.

Here's my 2c worth:

People using this plugin are probably using it in situations where they can't use a modern web frontend as it doesn't require these frameworks or SVGs.

There are already React alternatives: https://www.npmjs.com/package/reactjs-percentage-circle, https://www.npmjs.com/package/react-circular-progressbar, https://www.npmjs.com/package/react-circle

Therefore, I would consider that if we're going to enter the arena as an alternative we should probably consider:

Focusing on the core objective - This is one of my main concerns with the project - it should focus on a percentage based circle, nothing more.
e.g. Adding support for clocks and countdowns added unnecessary complexity and maintenance effort. It's also quite likely someone will come along with a new requirement or need a slightly different clock or countdown and be unable to produce it with the plugin as it is. We should offer a nice api that makes implementing these things easy rather than implementing everything. I'd probably extend this to the color themes, although management of the css is considerably less maintenance effort with #59 given the less variables, functions and autoprefixes.

Offering different framework options - React just takes care of the rendering and state management side of frontend, there's no reason we couldn't refactor this project and provide a React component as a plugin that utilises a large amount of core code.

Maintaining backwards compatibility - If people are using it because they can't support SVGs (although in this day and age I can't imagine that being reality) or can't use a modern framework (legacy systems, fair enough) then dropping that support would prevent this project standing out against the alternatives.

Offering different render options - SVG really is the superior rendering option here, the main limitation of the current approach is that the background must be a filled colour (although I've been experimenting and may have figured that part out). We could probably refactor and offer both render options.

All this is a big ask and rather opinionated, but I think it's important enough to discuss before anyone jumps into a major coding effort.

Hey @chris--jones , thanks a lot for taking the time to provide your input.
Backward compatibility should be indeed there, so what we developed up until this moment shouldn't just vanish all of a sudden.
Moreover, I concur to anything else that you pointed out. Could we initiate a new branch and start making some progress step-by-step in there?

Hey @chris--jones , any updates here?

Nothing worth sharing yet, it's still early stages, but if you want I'll push a very barebones restructuring of the library as soon as I can.

Any news here @chris--jones ?

#85 introduced a Vue implementation which renders this issue redundant at this moment. Closing.


print statement

print statement implementation

Previously this interpreter was printing all evaluated results to stdout, whether it was in REPL or or not.
This PR introduced similar behaviour to the python -c API.
Examples of print statements and no output programs:
Evaluated program with no output:
$ cargo run '2+2'

Evaluated program with output:
$ cargo run 'print(2+2)'
4

Please squash.

swashed :point_right: f94a7c26fb72f74a262be3eb7dac837a37354643

looks like bors job crashed?
https://app.bors.tech/repositories/61986/log#batch-306900

bors r-

bors ping


Always parse query string parameters when attempting to match a route

I was writing some middleware and surprised that query string parameters were not being parsed when a route wasn't matching. I don't see a good reason not too, and lots of reasons too - middleware that is agnostic to route definitions may be looking for query string parameters.

Awesome, good fix, will release shortly!

Hm, but when no route matches - why would you need to know the params? That's kinda a 404 situation and the params shouldn't matter?

But in general - yes, this behaviour is more "correct" or intuitive. Even unmatched routes trigger transitions, and if the query is there - it seems like it should be parsed.

That's kinda a 404 situation and the params shouldn't matter?

Yes it's still a 404 situation and the transition behaves as normal, just it has the query params parsed out. In my case I have some middleware looking for an SSO token, no matter what the route is, valid or not.


Support composable templates

7.8 introduced composable and component templates. The unique api endpoints mean this is work.
We may want to separate these into different operations given the unique endpoints. A user would therefore index a set of component templates, followed by their composable templates.
Alternatively, we could extend the current create-template action to accept a mode where it first inserts the declared component_templates and then composable_templates that have been declared in the track. This would be a non breaking change as the mode would default to legacy which would cause the current behaviour.
@dliappis @danielmitterdorfer happy to take but please advise

Thanks for raising this. I tend to the first option of dedicated runner(s) as I don't think Rally should abstract the Elasticsearch APIs much.

Also :+1: on dedicated runners; these should be first class citizens in Rally.

@danielmitterdorfer @dliappis the current template implementation uses the deprecated API. I'm not sure if the intention is to remove this in 8.0. For now, i propose we make these additions.
Do we want these to be first class definitions in the track? i.e.  component_templates and index_templates (composable). The former need to be inserted before the latter i believe so a runner could consume both definitions and ensure this occurs.
Alternatively, we could require a single definition e.g. index_templates under which the user defines both composable and component templates. The runner could then either inspect the body to determine the appropriate API or use a type field defined in the track definition for each template e.g.
"index_templates": [
    {
        "name": "my-default-index-template",
        "index-pattern": "my-index-*",
        "template": "default-template.json",
        "type": "component"
    }
]

The benefit of declaring these as first class citizens is that we can use the definitions in other runners should we need them e.g. for validation.

Closed by https://github.com/elastic/rally/pull/1099


element locater by.css throws error if the selector has ":" while by.id works fine

Bug report
I am using element(by.id()) most of the time but tried using $('#myID') and found that the later syntax throw invalid syntax error if the ID contains : .

Node Version: 10.16.0
Protractor Version: 5.3.1
Angular Version: 5.2.2
Browser(s): chrome
Operating System and Version mac os
Your protractor configuration file
A relevant example test
$('#test-05:0C:07:mN')
.getText().then((data) => {
expect(data.split("\n")[0]).equals("test");
});
Output from running the test
InvalidSelectorError: invalid selector: An invalid or illegal selector was specified
Steps to reproduce the bug
Give an ID containing ":" to an element and try to locate it using element(by.css('#yourID') or $('#yourID').
if you use element(by.id('yourID') it works fine.
The URL you are running your tests against (if relevant)

Feature Request

Reasons for adopting new feature
Is this a breaking change? (How will this affect existing functionality)

This is because it does a look up for a WebElement with selenium-webdriver's method. So this should be $('[id="yourId"]').
It is the difference between By.css:
https://github.com/SeleniumHQ/selenium/blob/master/javascript/node/selenium-webdriver/lib/by.js#L151
and By.id:
https://github.com/SeleniumHQ/selenium/blob/master/javascript/node/selenium-webdriver/lib/by.js#L162

Thank you


Add telegram observer

This is quite obviously based on @Qwlouse's SlackObserver.
But I don't use slack, so here goes :)
This requires the user to create their own bot, that's just how telegram bots work.

Coverage decreased (-2.6%) to 83.783% when pulling c49672da89868c793c22754d30044ae48102a5de on black-puppydog:master into 8314abe2ba27db5407161d5157167e73701a4809 on IDSIA:master.

well, apparently, I've got some work to do there. will have a look at that py27 test. sigh :smile:

Coverage decreased (-2.6%) to 83.783% when pulling 8fabe94f4fb5de4b26a6acd6313fda5cde7f0c80 on black-puppydog:master into 8314abe2ba27db5407161d5157167e73701a4809 on IDSIA:master.

Coverage decreased (-2.5%) to 83.918% when pulling c1307045029ec38b457b527f3112f9e8a2525d89 on black-puppydog:master into 8314abe2ba27db5407161d5157167e73701a4809 on IDSIA:master.

Wow, sweet! Thanks for figuring this out! I'm also using Telegram, so this will come in very handy!


Global selection

Added global filter to minimize total amount of latent neurons. Applied this method to the mixed qubit example.

Thanks!


npm Error: Not Found<EMAIL_ADDRESS>

At the first step: npm install -g exp .
When I'm trying to install exp like that, npm throw npm ERR! 404 Not Found: @ccheever/inquirer@0.9.5,how to solve it?(My npm is in latest version)

What version of npm are you using? It sounds like 5? Maybe try npm4
instead of npm5.
That package does live on npm and I was able to just successfully install
it.
Or maybe just try again? Maybe npm's servers had a hiccup.
On Wed, Jun 14, 2017 at 5:16 AM, Nick Chang<EMAIL_ADDRESS>wrote:

At the first step: npm install -g exp .
When I'm trying to install exp like that, npm throw npm ERR! 404 Not
Found: @ccheever/inquirer@0.9.5,how to solve it?(My npm is in latest
version)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/expo/exp/issues/58, or mute the thread
https://github.com/notifications/unsubscribe-auth/AADdj_aYKQMZ4F5TFlCVRq_e8Ht3EjgDks5sD88SgaJpZM4N5y-Y
.

Hi! As requested in the issue template please open issues against https://github.com/expo/expo. As @ccheever mentioned it sounds like this was either an issue with npm 5 or with a temporary network problem on npm's end. If you're still having issues with this please open a new issue at expo/expo. Thanks!

@Nicksapp Hi, I have the same problem in China too. After that I use another npm source, then it works.
I use
npm install -g exp --registry=https://registry.npm.taobao.org
Maybe you can try it.


module 'dask' has no attribute 'config'

Traceback (most recent call last):   File "process_data.py", line 1, in <module>     import featuretools as ft   File "/Users/trinadhimmedisetty/anaconda3/lib/python3.6/site-packages/featuretools-0.2.1-py3.6.egg/featuretools/__init__.py", line 7, in <module>     from .synthesis.api import *   File "/Users/trinadhimmedisetty/anaconda3/lib/python3.6/site-packages/featuretools-0.2.1-py3.6.egg/featuretools/synthesis/__init__.py", line 3, in <module>     from .api import *   File "/Users/trinadhimmedisetty/anaconda3/lib/python3.6/site-packages/featuretools-0.2.1-py3.6.egg/featuretools/synthesis/api.py", line 5, in <module>     from .dfs import dfs   File "/Users/trinadhimmedisetty/anaconda3/lib/python3.6/site-packages/featuretools-0.2.1-py3.6.egg/featuretools/synthesis/dfs.py", line 5, in <module>     from featuretools.computational_backends import calculate_feature_matrix   File "/Users/trinadhimmedisetty/anaconda3/lib/python3.6/site-packages/featuretools-0.2.1-py3.6.egg/featuretools/computational_backends/__init__.py", line 2, in <module>     from .api import *   File "/Users/trinadhimmedisetty/anaconda3/lib/python3.6/site-packages/featuretools-0.2.1-py3.6.egg/featuretools/computational_backends/api.py", line 2, in <module>     from .calculate_feature_matrix import (   File "/Users/trinadhimmedisetty/anaconda3/lib/python3.6/site-packages/featuretools-0.2.1-py3.6.egg/featuretools/computational_backends/calculate_feature_matrix.py", line 17, in <module>     from .utils import (   File "/Users/trinadhimmedisetty/anaconda3/lib/python3.6/site-packages/featuretools-0.2.1-py3.6.egg/featuretools/computational_backends/utils.py", line 9, in <module>     from distributed import Client, LocalCluster   File "/Users/trinadhimmedisetty/anaconda3/lib/python3.6/site-packages/distributed/__init__.py", line 3, in <module>     from . import config   File "/Users/trinadhimmedisetty/anaconda3/lib/python3.6/site-packages/distributed/config.py", line 13, in <module>     config = dask.config.config AttributeError: module 'dask' has no attribute 'config'

Issue occurred due to multiple installations of dask.


Cleanup and repair repo for 2023

This is currently a work in progress to address tech debt and update the project.

Wanted to note that I suspect that the Apple Pay integration tests fail because of an outdated Apple Pay payment method token, where the year is behind, since the response from Spreedly is:
{"errors":[{"attribute":"year","key":"errors.invalid","message":"Year is invalid"}]}

This causes the Optional transaction.applePay to be nil when forcibly unwrapped by the ! "bang" operator. In Swift, Optionals are values that aren't guaranteed to be truth-y, so are usually unwrapped with ? operators. I think using ! in tests where you want failures to reveal themselves is fine, though. But in the SDK, maybe the exception for a bad payment method should be caught sooner, before using it as an Apply Pay PM.


Doc linter

We have several issues in docs that need to be manually checked every release such as broken links and working examples. I'm sure there are many more I don't know about. Having an automated way to check these things would save us a lot of time writing docs and improve their quality.

True. But do we have ideas on how we actually want to go about this? I'm sure there are link-checker tools out there we can try. @dwhitena?
This is pretty low priority I think because things seem to be working ok for now.

stale


Create a Hook to API request

About the task
In the project, we'll be a big code repetition, when our need to create, authenticate and get user's account. This is not good practices, and the correct practices is creating a Hook to simplify these processes.
Objective of task
Create a custom hook to simplify the creation, authenticate and get user's account.

Pull request approved.


AK icon magazine length

The magazine in the AK is the regular size until out of bullets when it changes to the short version.
It should stay the same length.
It should use the short version when a short magazine is inserted.

Pretty sure there's multiple weapons that do this.
@metalgearsloth

From memory and a quick look I only did it for the rifles as I didn't know how they functioned on Eris.
I don't think there's anything to handle different magazines being inserted at the moment so it's probably better to remove the short versions for now as this would also likely tie into any sort of weapon attachment system.

Alright I have a branch with the fixes (6 guns with issues) but I'm getting a dotnet issue so when that's fixed / I workaround it I'll pr it.

Looks like this has been fixed by #734 so i'm going to close it.


Expanding subviews in UICollectionViewCell

Just implemented Re:Lax and it looks great. Thanks
I use a ParallaxContainer in my CollectionViewCell, just like in your example. Works great, except for one problem: how can I prevent a subview from "expanding" when the cell is focussed ?
Here's an example:

Here the red UIView has a constraint so that its leading lines up with the "APP STORE" label, and the trailing of the "8:AM", but when focused this is no longer the case.
Again, thanks for the great work. If you'd like to Testflight the app, let me know I'd be happy to add your email to the list.

The Parallax effect is created by zooming each layer (subviews of the ParallaxContainer) by a different amount and then translating them as the view is transformed. You can put views in a common parent (that is then added as a subview of the container) to give the appearance of being on the same layer.

Thanks very much, I'll try that.


calc: <IP_ADDRESS> -> <IP_ADDRESS>

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/calc/versions.
meta.description for calc is: '"C-style arbitrary precision calculator"'.

Checks done (click to expand)

built on NixOS
Warning: no invocation of /nix/store/5pyh2lwlj2x45qgmahxxvp3ba7yv4xk4-calc-<IP_ADDRESS>/bin/cscript/4dsphere had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/5pyh2lwlj2x45qgmahxxvp3ba7yv4xk4-calc-<IP_ADDRESS>/bin/cscript/fproduct had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/5pyh2lwlj2x45qgmahxxvp3ba7yv4xk4-calc-<IP_ADDRESS>/bin/cscript/mersenne had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/5pyh2lwlj2x45qgmahxxvp3ba7yv4xk4-calc-<IP_ADDRESS>/bin/cscript/piforever had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/5pyh2lwlj2x45qgmahxxvp3ba7yv4xk4-calc-<IP_ADDRESS>/bin/cscript/plus had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/5pyh2lwlj2x45qgmahxxvp3ba7yv4xk4-calc-<IP_ADDRESS>/bin/cscript/powerterm had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/5pyh2lwlj2x45qgmahxxvp3ba7yv4xk4-calc-<IP_ADDRESS>/bin/cscript/simple had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/5pyh2lwlj2x45qgmahxxvp3ba7yv4xk4-calc-<IP_ADDRESS>/bin/cscript/square had a zero exit code or showed the expected version
/nix/store/5pyh2lwlj2x45qgmahxxvp3ba7yv4xk4-calc-<IP_ADDRESS>/bin/calc passed the binary check.
1 of 9 passed binary check by having a zero exit code.
0 of 9 passed binary check by having the new version present in output.
found <IP_ADDRESS> with grep in /nix/store/5pyh2lwlj2x45qgmahxxvp3ba7yv4xk4-calc-<IP_ADDRESS>
directory tree listing: https://gist.github.com/20783495639c79b3a8018182f6560d0c
du listing: https://gist.github.com/465c47ff2763e77a7cffe4a8fd9d4f88

Outpath report (click to expand)

Outpath difference report
4 total rebuild paths
1 package rebuilds
1 x86_64-linux rebuilds
1 i686-linux rebuilds
1 x86_64-darwin rebuilds
1 aarch64-linux rebuilds
First ten rebuilds by attrpath
calc

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/5pyh2lwlj2x45qgmahxxvp3ba7yv4xk4-calc-<IP_ADDRESS> \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A calc https://github.com/r-ryantm/nixpkgs/archive/10aabc182e2001f651b01ce0d3a0568711aa5e71.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/5pyh2lwlj2x45qgmahxxvp3ba7yv4xk4-calc-<IP_ADDRESS>
ls -la /nix/store/5pyh2lwlj2x45qgmahxxvp3ba7yv4xk4-calc-<IP_ADDRESS>/bin

cc @matthewbauer for testing.

Success on x86_64-darwin (full log)
Attempted: calc
Partial log (click to expand)
installed /nix/store/aapam0b97gqk4wa24hjd7v0krchhs1yr-calc-<IP_ADDRESS>/include/have_rusage.h
installed /nix/store/aapam0b97gqk4wa24hjd7v0krchhs1yr-calc-<IP_ADDRESS>/include/have_strdup.h
installed /nix/store/aapam0b97gqk4wa24hjd7v0krchhs1yr-calc-<IP_ADDRESS>/include/have_unused.h
installed /nix/store/aapam0b97gqk4wa24hjd7v0krchhs1yr-calc-<IP_ADDRESS>/share/man/man1/calc.1
post-installation fixup
gzipping man pages under /nix/store/aapam0b97gqk4wa24hjd7v0krchhs1yr-calc-<IP_ADDRESS>/share/man/
strip is /nix/store/g5r4apl0za012ffs6ladinwa5w0m1l3k-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/aapam0b97gqk4wa24hjd7v0krchhs1yr-calc-<IP_ADDRESS>/lib  /nix/store/aapam0b97gqk4wa24hjd7v0krchhs1yr-calc-<IP_ADDRESS>/bin
patching script interpreter paths in /nix/store/aapam0b97gqk4wa24hjd7v0krchhs1yr-calc-<IP_ADDRESS>
/nix/store/aapam0b97gqk4wa24hjd7v0krchhs1yr-calc-<IP_ADDRESS>

Success on aarch64-linux (full log)
Attempted: calc
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/b6nchm4m96p2cgcj1llajjxwvh407716-calc-<IP_ADDRESS>
shrinking /nix/store/b6nchm4m96p2cgcj1llajjxwvh407716-calc-<IP_ADDRESS>/lib/libcustcalc.so.<IP_ADDRESS>
shrinking /nix/store/b6nchm4m96p2cgcj1llajjxwvh407716-calc-<IP_ADDRESS>/lib/libcalc.so.<IP_ADDRESS>
shrinking /nix/store/b6nchm4m96p2cgcj1llajjxwvh407716-calc-<IP_ADDRESS>/bin/calc
gzipping man pages under /nix/store/b6nchm4m96p2cgcj1llajjxwvh407716-calc-<IP_ADDRESS>/share/man/
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/b6nchm4m96p2cgcj1llajjxwvh407716-calc-<IP_ADDRESS>/lib  /nix/store/b6nchm4m96p2cgcj1llajjxwvh407716-calc-<IP_ADDRESS>/bin
patching script interpreter paths in /nix/store/b6nchm4m96p2cgcj1llajjxwvh407716-calc-<IP_ADDRESS>
checking for references to /build in /nix/store/b6nchm4m96p2cgcj1llajjxwvh407716-calc-<IP_ADDRESS>...
/nix/store/b6nchm4m96p2cgcj1llajjxwvh407716-calc-<IP_ADDRESS>

Success on x86_64-linux (full log)
Attempted: calc
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/5pyh2lwlj2x45qgmahxxvp3ba7yv4xk4-calc-<IP_ADDRESS>
shrinking /nix/store/5pyh2lwlj2x45qgmahxxvp3ba7yv4xk4-calc-<IP_ADDRESS>/bin/calc
shrinking /nix/store/5pyh2lwlj2x45qgmahxxvp3ba7yv4xk4-calc-<IP_ADDRESS>/lib/libcustcalc.so.<IP_ADDRESS>
shrinking /nix/store/5pyh2lwlj2x45qgmahxxvp3ba7yv4xk4-calc-<IP_ADDRESS>/lib/libcalc.so.<IP_ADDRESS>
gzipping man pages under /nix/store/5pyh2lwlj2x45qgmahxxvp3ba7yv4xk4-calc-<IP_ADDRESS>/share/man/
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/5pyh2lwlj2x45qgmahxxvp3ba7yv4xk4-calc-<IP_ADDRESS>/lib  /nix/store/5pyh2lwlj2x45qgmahxxvp3ba7yv4xk4-calc-<IP_ADDRESS>/bin
patching script interpreter paths in /nix/store/5pyh2lwlj2x45qgmahxxvp3ba7yv4xk4-calc-<IP_ADDRESS>
checking for references to /build in /nix/store/5pyh2lwlj2x45qgmahxxvp3ba7yv4xk4-calc-<IP_ADDRESS>...


Isolate current tenant modifications

Now we set current tenant in CommandBus and do not restore it back, which is really fragile. The goal of this PR is to isolate the work with multitenancy at the level of repositories.

Here's the plan:

[ ] Move CurrentTenant to the entity package.
[ ] Make setting and re-setting current tenant protected to Repository. A repository should get the current state, remember it and restore when done. Presumably, CurrentTenant would become a stack.
[ ] Make CommandStore and EventStore descend from Repository. These stores are not repositories and it's not convenient. We cannot, for example, load a command status.
[ ] Make CommandStore and EventStore call tenant management methods derived from the Repository class.
[ ] Make CurrentTenant class package-private to the entity package.

@armiol, FYI. See above.

I'm closing this PR because it's set to merge into quite an old branch command-bus-endpoints. Because of this the difference is huge and cannot be reviewed.
I'll create a new PR that would merge the branch isolate-current-tenant-modifications into master.


Make rsync-mode mandatory when using rsync store.

Do we really want to re-introduce obuilder as a vendored submodule?


[Work Item] SMB1- add link to article

When "SMB1 Installed" returns "True", add a link to https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-server-and-smbv1/ba-p/1165615
When "SMB1 Blocked" returns "False", add a link to https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-server-and-smbv1/ba-p/1165615

We are already doing this:
$additionalDisplayValue = [string]::Empty
    $smb1Status = $osInformation.Smb1ServerSettings.Smb1Status

    if ($osInformation.BuildInformation.MajorVersion -gt [HealthChecker.OSServerVersion]::Windows2012) {
        $displayValue = "False"
        $writeType = "Green"

        if ($smb1Status -band 1) {
            $displayValue = "Failed to get install status"
            $writeType = "Yellow"
        } elseif ($smb1Status -band 2) {
            $displayValue = "True"
            $writeType = "Red"
            $additionalDisplayValue = "SMB1 should be uninstalled"
        }

        $analyzedResults = Add-AnalyzedResultInformation -Name "SMB1 Installed" -Details $displayValue `
            -DisplayGroupingKey $keySecuritySettings `
            -DisplayWriteType $writeType `
            -AnalyzedInformation $analyzedResults
    }

    $writeType = "Green"
    $displayValue = "True"

    if ($smb1Status -band 8) {
        $displayValue = "Failed to get block status"
        $writeType = "Yellow"
    } elseif ($smb1Status -band 16) {
        $displayValue = "False"
        $writeType = "Red"
        $additionalDisplayValue += " SMB1 should be blocked"
    }

    $analyzedResults = Add-AnalyzedResultInformation -Name "SMB1 Blocked" -Details $displayValue `
        -DisplayGroupingKey $keySecuritySettings `
        -DisplayWriteType $writeType `
        -AnalyzedInformation $analyzedResults

    if ($additionalDisplayValue -ne [string]::Empty) {
        $additionalDisplayValue += "`r`n`t`tMore Information: https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-server-and-smbv1/ba-p/1165615"

        $analyzedResults = Add-AnalyzedResultInformation -Details $additionalDisplayValue.Trim() `
            -DisplayGroupingKey $keySecuritySettings `
            -DisplayWriteType "Yellow" `
            -DisplayCustomTabNumber 2 `
            -AddHtmlDetailRow $false `
            -AnalyzedInformation $analyzedResults
    }

I'm using version v3.3.5, but all I saw was "Ture" and "False":

I checked the txt-file and it contains the link, but the HTML page doesn't.

Yes you're right. At the moment we only show the link on the screen and not in the html report:
    if ($additionalDisplayValue -ne [string]::Empty) {
        $additionalDisplayValue += "`r`n`t`tMore Information: https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-server-and-smbv1/ba-p/1165615"

        $analyzedResults = Add-AnalyzedResultInformation -Details $additionalDisplayValue.Trim() `
            -DisplayGroupingKey $keySecuritySettings `
            -DisplayWriteType "Yellow" `
            -DisplayCustomTabNumber 2 `
            **-AddHtmlDetailRow $false `**
            -AnalyzedInformation $analyzedResults
    }

Is there a reason why you're not showing the link in the html report, or is it just a mistake?

Normally (there are only a few checks that do, and I think they do because we took some checks over from v2 to v3) we do not provide the link to more information in the html report. Will discuss this inquiry internally and we'll then decide.
@dpaulson45 let's add this to the backlog and decide during the new wiki work

So you provide the possibilty to create an easy to read html-report, but the links to more information I have to dig up from a txt-file? How bizarre!

I was going to submit a feature request to make the links in the html report clickable...

@dpaulson45 if the state is SMB1 installed: True
you might want to include a link to: https://docs.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/detect-enable-and-disable-smbv1-v2-v3 for guidance (if not already included.
from your output you only reference why it should be disabled even when installed is already False.
Thank you for consideration.


[Feature]: Re-factor auth to use access token

Currently the plugin relies on legacy auth with client certs which requires users to give their service account the container.admin role. Ideally we should be using access tokens for auth which would remove this pre-req for the service account.
GKE supports auth using a GCP service account. This would provide an easier means of accomplishing this. Need to investigate how this works with KubeConfig while we still have the dep on the kubectl binary.

Came across this blog post which outlines an approach very similar to the one we'd like to take: https://codeascraft.com/2018/06/05/deploying-to-google-kubernetes-engine/

After doing some investigation here are the steps I've mapped out for accomplishing this:

Modify the KubeConfig class so that instead of retrieving client certs from the cluster's master auth and embedding them in the generated KubeConfig file, rather it uses the Google OAuth to acquire an access token and expiry for the GCP SA and embeds that into KubeConfig's->User->AuthProvider. For reference see gcloud's auth provider impl: https://github.com/google-cloud-sdk/google-cloud-sdk/blob/68b374bc5fe679d1f9a665451bd39fa1ed735581/lib/googlecloudsdk/api_lib/container/kubeconfig.py#L226

Create and document a helm chart which can be applied to a target cluster to grant the GCP SA the necessary cluster roles to enable deployment.

Another note, Etsy's deployinator project will be a good point of reference for this work: https://github.com/etsy/deployinator


[#126686741] Cleanup FIXMEs removing deprecated quotas.

🚨  Note: This should not be merged until #380 has been deployed to production.
What
Cleanup the temporary code to remove the unused quotas.
How to review
Code review
Who can review
Anyone but myself.

Confirmed that the commit has made it to production and they are no longer listed by cf quotas.


Focus on a first input in freshly opened modal window

I want to merge this change because...
It resolves #1325
Pull Request Checklist
(Please keep this section. It will make maintainer's life easier.)

[x] Privileged views and APIs are guarded by proper permission checks.
[x] All visible strings are translated with proper context.
[x] All data-formatting is locale-aware (dates, numbers, and so on).
[x] Database queries are optimized and the number of queries is constant.
[x] The changes are tested.
[x] The code is documented (docstrings, project documentation).
[x] Python code quality checks pass: pycodestyle, pydocstyle, pylint.
[x] JavaScript code quality checks pass: eslint.

Codecov Report

Merging #1337 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master    #1337   +/-   ##
=======================================
  Coverage   70.88%   70.88%
=======================================
  Files         118      118
  Lines        6251     6251
  Branches      790      790
=======================================
  Hits         4431     4431
  Misses       1658     1658
  Partials      162      162

Impacted Files
Coverage Δ

saleor/dashboard/order/forms.py
67.6% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Update PowerModels compat to include 0.19

Codecov Report

Merging #84 (76f4885) into master (b2c995e) will decrease coverage by 1.33%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #84      +/-   ##
==========================================
- Coverage   88.26%   86.93%   -1.34%
==========================================
  Files          12       11       -1
  Lines         537      467      -70
==========================================
- Hits          474      406      -68
+ Misses         63       61       -2

Impacted Files
Coverage Δ

src/core/configuration.jl
77.77% <0.00%> (-11.12%)
:arrow_down:

src/core/utils.jl
88.46% <0.00%> (-6.14%)
:arrow_down:

src/plots/plot.jl
56.00% <0.00%> (-1.70%)
:arrow_down:

src/experimental/experimental.jl
51.51% <0.00%> (-1.43%)
:arrow_down:

src/layouts/common.jl
93.61% <0.00%> (-1.12%)
:arrow_down:

src/core/types.jl
100.00% <0.00%> (ø)

src/core/attribute_validation.jl
100.00% <0.00%> (ø)

src/core/export.jl

src/layouts/kamada_kawaii_layout.jl
96.10% <0.00%> (+1.85%)
:arrow_up:

src/layouts/SFDP_fixed_layout.jl
98.43% <0.00%> (+2.54%)
:arrow_up:

Continue to review full report at Codecov.

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


Optimize ttn_svd

This PR improves scaling of graph-related logic in ttn_svd and related functionality.
Tests test/test_opsum_to_ttn.jl are passing.

@b-kloss looks good to me, thanks for the quick fix. I'll merge once that final comment is addressed.

Nice to see this. Thanks, Benedikt


Connection timeout when trying to execute any build

Hello,
I am getting this error every time I am trying to run a build:
"mvnd clean install"
I am running the software on a VPN, don't know if that may be the issue.
WARNING: Unable to create a system terminal, creating a dumb terminal (enable debug logging for more information)
[main] INFO org.jboss.fuse.mvnd.common.DaemonRegistry - Removing 0 daemon stop events from registry
[main] INFO org.jboss.fuse.mvnd.client.DaemonConnector - Previous Daemon (df642d73-ad18-43a0-9821-0ad3b45610d1) stopped at<PHONE_NUMBER>603 by user or operating system
[main] INFO org.jboss.fuse.mvnd.client.DaemonConnector - Starting a Maven Daemon, 1 stopped Daemon could not be reused, use --status for details
[main] INFO org.jboss.fuse.mvnd.client.DaemonConnector - Removing daemon from the registry due to communication failure. Daemon information: DaemonInfo{uid=9e37e4ec-8243-43e3-9a18-8e33fd9a6de1javaHome=C:\Program Files\Java\jdk1.8.0_251\jre, options=[], mavenHome=C:\apps\mvnd-0.0.4-windows-amd64, pid=35024, address=50141, idleTimeout=10800000, locale=en-US, state=Busy, lastIdle=1599465354751, lastBusy=1599465354751}
Exception in thread "main" org.jboss.fuse.mvnd.common.DaemonException$ConnectException: Could not connect to the Maven daemon.
Daemon uid: 9e37e4ec-8243-43e3-9a18-8e33fd9a6de1
  log file: C:\apps\mvnd-0.0.4-windows-amd64\daemon\daemon-9e37e4ec-8243-43e3-9a18-8e33fd9a6de1.log
----- Last  20 lines from daemon log file - C:\apps\mvnd-0.0.4-windows-amd64\daemon\daemon-9e37e4ec-8243-43e3-9a18-8e33fd9a6de1.log -----
09:55:54.759 I Daemon started
09:55:54.762 D daemon is running. Sleeping until state changes.----- End of the daemon log -----

        at org.jboss.fuse.mvnd.client.DaemonConnector.connectToDaemonWithId(DaemonConnector.java:302)
        at org.jboss.fuse.mvnd.client.DaemonConnector.startDaemon(DaemonConnector.java:233)
        at org.jboss.fuse.mvnd.client.DaemonConnector.connect(DaemonConnector.java:114)
        at org.jboss.fuse.mvnd.client.DefaultClient.execute(DefaultClient.java:188)
        at org.jboss.fuse.mvnd.client.DefaultClient.main(DefaultClient.java:71)
Caused by: org.jboss.fuse.mvnd.common.DaemonException$ConnectException: Could not connect to server <IP_ADDRESS>/<IP_ADDRESS>:50141.
        at org.jboss.fuse.mvnd.client.DaemonConnector.connect(DaemonConnector.java:359)
        at org.jboss.fuse.mvnd.client.DaemonConnector.connectToDaemon(DaemonConnector.java:312)
        at org.jboss.fuse.mvnd.client.DaemonConnector.connectToDaemonWithId(DaemonConnector.java:299)
        ... 4 more
Caused by: java.net.SocketTimeoutException
        at sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:129)
        at org.jboss.fuse.mvnd.client.DaemonConnector.connect(DaemonConnector.java:349)
        ... 6 more

Same here.

Thanks for the report. I admit this project suffers from a lack of developers working on Windows.
To see whether the issue is caused by your local settings (firewall or similar), could you @marcphilipp or @galegofer please run the integration tests on your machine?
It is basically mvn clean verify -Pnative from the root directory of the source tree. Please check  https://github.com/mvndaemon/mvnd#build-mvnd-from-source for prerequisites.
mvn clean verify -Pnative is passing on our Windows CI and I really wonder if it is going to pass on your machines?

For me it fails on macOS.

For me it fails on macOS.

Good to know, thanks. Are the integration tests passing on your machine?

What is the output of mvnd -v on your machines?

It is basically mvn clean verify -Pnative from the root directory of the source tree. Please check https://github.com/mvndaemon/mvnd#build-mvnd-from-source for prerequisites.

BTW, I had to disable sdkman in my ~/bashrc to be able to run the integration tests

mvnd -v
Sep 16, 2020 2:47:16 PM org.jline.utils.Log logr
WARNING: Unable to create a system terminal, creating a dumb terminal (enable debug logging for more information)
[main] INFO org.jboss.fuse.mvnd.common.DaemonRegistry - Removing 1 daemon stop events from registry
[main] INFO org.jboss.fuse.mvnd.client.DaemonConnector - Starting a Maven Daemon, 2 busy Daemons could not be reused, use --status for details
[main] INFO org.jboss.fuse.mvnd.client.DaemonConnector - Removing daemon from the registry due to communication failure. Daemon information: DaemonInfo{uid=26c457c5-70bc-489b-ba74-300461d684d3javaHome=C:\Program Files\Java\jdk1.8.0_251\jre, options=[], mavenHome=C:\apps\mvnd-0.0.4-windows-amd64, pid=24116, address=63613, idleTimeout=10800000, locale=en-US, state=Busy, lastIdle=1600260438719, lastBusy=1600260438719}
Maven Daemon 0.0.4-windows-amd64 (native)
Exception in thread "main" org.jboss.fuse.mvnd.common.DaemonException$ConnectException: Could not connect to the Maven daemon.
Daemon uid: 26c457c5-70bc-489b-ba74-300461d684d3
log file: C:\apps\mvnd-0.0.4-windows-amd64\daemon\daemon-26c457c5-70bc-489b-ba74-300461d684d3.log
----- Last  20 lines from daemon log file - C:\apps\mvnd-0.0.4-windows-amd64\daemon\daemon-26c457c5-70bc-489b-ba74-300461d684d3.log -----
14:47:18.726 I Daemon started
14:47:18.729 D daemon is running. Sleeping until state changes.----- End of the daemon log -----
    at org.jboss.fuse.mvnd.client.DaemonConnector.connectToDaemonWithId(DaemonConnector.java:302)
    at org.jboss.fuse.mvnd.client.DaemonConnector.startDaemon(DaemonConnector.java:233)
    at org.jboss.fuse.mvnd.client.DaemonConnector.connect(DaemonConnector.java:114)
    at org.jboss.fuse.mvnd.client.DefaultClient.execute(DefaultClient.java:188)
    at org.jboss.fuse.mvnd.client.DefaultClient.main(DefaultClient.java:71)

Caused by: org.jboss.fuse.mvnd.common.DaemonException$ConnectException: Could not connect to server <IP_ADDRESS>/<IP_ADDRESS>:63613.
at org.jboss.fuse.mvnd.client.DaemonConnector.connect(DaemonConnector.java:359)
at org.jboss.fuse.mvnd.client.DaemonConnector.connectToDaemon(DaemonConnector.java:312)
at org.jboss.fuse.mvnd.client.DaemonConnector.connectToDaemonWithId(DaemonConnector.java:299)
... 4 more
Caused by: java.net.SocketTimeoutException
at sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:129)
at org.jboss.fuse.mvnd.client.DaemonConnector.connect(DaemonConnector.java:349)
... 6 more
It looks like it's happening all the time.
I didn't manage yet to run the Integration Tests in my local due to some issues with the artifacts repository that we have in the company, not being able to resolve some Takari lifecycle dependencies.

What is your JAVA_VERSION?
BTW, 0.0.5 was released and I guess this issue was not solved by the only included fix?

java --version
java version "1.8.0_251"
Java(TM) SE Runtime Environment (build 1.8.0_251-b08)
Java HotSpot(TM) 64-Bit Server VM (build 25.251-b08, mixed mode)

Does the problem still exist with the freshly released mvnd 0.0.6? https://github.com/mvndaemon/mvnd/releases/tag/0.0.6

Not lucky
λ mvnd -v
Sep 30, 2020 8:55:08 AM org.jline.utils.Log logr
WARNING: Unable to create a system terminal, creating a dumb terminal (enable debug logging for more information)
[main] INFO org.jboss.fuse.mvnd.common.DaemonRegistry - Removing 0 daemon stop events from registry
[main] INFO org.jboss.fuse.mvnd.client.DaemonConnector - Previous Daemon (fe9c36e5-c453-4680-95e4-3b571e3e58fb) stopped at<PHONE_NUMBER>484 by user or operating system
[main] INFO org.jboss.fuse.mvnd.client.DaemonConnector - Previous Daemon (6c5f1cd7-6b4c-48c6-bc98-a13822d800e3) stopped at<PHONE_NUMBER>830 by user or operating system
[main] INFO org.jboss.fuse.mvnd.client.DaemonConnector - Starting a Maven Daemon, 2 stopped Daemons could not be reused, use --status for details
[main] INFO org.jboss.fuse.mvnd.client.DaemonConnector - Removing daemon from the registry due to communication failure. Daemon information: DaemonInfo{uid=e5acb34d-782b-4206-aa46-5f4b31275780javaHome=C:\Program Files\Java\jdk1.8.0_251, options=[], mavenHome=C:\apps\mvnd-0.0.6-windows-amd64, pid=32692, address=56118, idleTimeout=10800000, locale=en-US, state=Busy, lastIdle=1601448910838, lastBusy=1601448910838}
Maven Daemon 0.0.6-windows-amd64 (native)
Exception in thread "main" org.jboss.fuse.mvnd.common.DaemonException$ConnectException: Could not connect to the Maven daemon.
Daemon uid: e5acb34d-782b-4206-aa46-5f4b31275780
log file: C:\apps\mvnd-0.0.6-windows-amd64\daemon\daemon-e5acb34d-782b-4206-aa46-5f4b31275780.log
----- Last  20 lines from daemon log file - C:\apps\mvnd-0.0.6-windows-amd64\daemon\daemon-e5acb34d-782b-4206-aa46-5f4b31275780.log -----
08:55:10.846 I Daemon started
08:55:10.849 D daemon is running. Sleeping until state changes.----- End of the daemon log -----
    at org.jboss.fuse.mvnd.client.DaemonConnector.connectToDaemonWithId(DaemonConnector.java:303)
    at org.jboss.fuse.mvnd.client.DaemonConnector.startDaemon(DaemonConnector.java:233)
    at org.jboss.fuse.mvnd.client.DaemonConnector.connect(DaemonConnector.java:114)
    at org.jboss.fuse.mvnd.client.DefaultClient.execute(DefaultClient.java:188)
    at org.jboss.fuse.mvnd.client.DefaultClient.main(DefaultClient.java:71)

Caused by: org.jboss.fuse.mvnd.common.DaemonException$ConnectException: Could not connect to server <IP_ADDRESS>/<IP_ADDRESS>:56118.
at org.jboss.fuse.mvnd.client.DaemonConnector.connect(DaemonConnector.java:360)
at org.jboss.fuse.mvnd.client.DaemonConnector.connectToDaemon(DaemonConnector.java:313)
at org.jboss.fuse.mvnd.client.DaemonConnector.connectToDaemonWithId(DaemonConnector.java:300)
... 4 more
Caused by: java.net.SocketTimeoutException
at sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:129)
at org.jboss.fuse.mvnd.client.DaemonConnector.connect(DaemonConnector.java:350)
... 6 more

I think something like this may happen if the MVND_HOME env var or mvnd.home property passed to the daemon process does not match what the mvnd client expects. Could you please check the following?

Is MVND_HOME set in your environment? Is the value an ancestor of the full mvnd client path? On my machine I see:

$ echo $MVND_HOME
/home/ppalaga/.sdkman/candidates/mvnd/current
$ which mvnd
~/.sdkman/candidates/mvnd/current/bin/mvnd

Do you have ~/.m2/mvnd.properties? Does the mvnd.home property fulfill the above condition? Note that if you use SDKMAN there is typically no need to have ~/.m2/mvnd.properties because both JAVA_HOME and MVND_HOME are managed by SDKMAN.

The variable MVND_HOME  seems to don't be set.
λ echo $MVND_HOME

In my case I am not using SDKMAN to use mvnd, I just downloaded the release and unpacked it.
λ which mvnd
/c/apps/mvnd-0.0.6-windows-amd64/bin/mvnd

I don't see the file ~/.m2/mvnd.properties in my user directory.

Could you please re-check with the recently released https://github.com/mvndaemon/mvnd/releases/tag/0.0.8 ?
There are two fixes that might help:

https://github.com/mvndaemon/mvnd/commit/e9b92ae65dfb101b902c43ddb36883aee4401ce3
https://github.com/mvndaemon/mvnd/commit/98ba2e20e3c48f98e1bcb464c7982a143cf605f7

Thanks, that fixed it for me on macOS! 👍

How about you, @galegofer?

λ which mvnd
/c/apps/mvnd-0.0.6-windows-amd64/bin/mvnd

@galegofer /c/apps/... actually does not look like stock Windows. Is this windows subsystem for linux or cygwin?

@ppalaga Could also be Git Bash.

Windows got so many different flavors since I stopped using it back in 2006. I wonder if they all need to be tested separately?

No luck yet, I am still getting:
GIT BASH / CMDER
λ mvnd -version
Oct 21, 2020 8:22:48 AM org.jline.utils.Log logr
WARNING: Unable to create a system terminal, creating a dumb terminal (enable debug logging for more information)
Maven Daemon 0.0.8-windows-amd64 (native)
Exception in thread "main" org.jboss.fuse.mvnd.common.DaemonException$ConnectException: Could not connect to the Maven daemon.
Daemon uid: 193e38e7-a14e-4c2d-88ec-6668a87faee3
log file: C:\apps\mvnd-0.0.8-windows-amd64\daemon\daemon-193e38e7-a14e-4c2d-88ec-6668a87faee3.log
----- Last  20 lines from daemon log file - C:\apps\mvnd-0.0.8-windows-amd64\daemon\daemon-193e38e7-a14e-4c2d-88ec-6668a87faee3.log -----
08:22:49.847 I Daemon started
08:22:49.849 D daemon is running. Sleeping until state changes.----- End of the daemon log -----
    at org.jboss.fuse.mvnd.client.DaemonConnector.connectToDaemonWithId(DaemonConnector.java:323)
    at org.jboss.fuse.mvnd.client.DaemonConnector.startDaemon(DaemonConnector.java:238)
    at org.jboss.fuse.mvnd.client.DaemonConnector.connect(DaemonConnector.java:119)
    at org.jboss.fuse.mvnd.client.DefaultClient.execute(DefaultClient.java:185)
    at org.jboss.fuse.mvnd.client.DefaultClient.main(DefaultClient.java:70)

Caused by: org.jboss.fuse.mvnd.common.DaemonException$ConnectException: Could not connect to server <IP_ADDRESS>/<IP_ADDRESS>:58569.
at org.jboss.fuse.mvnd.client.DaemonConnector.connect(DaemonConnector.java:380)
at org.jboss.fuse.mvnd.client.DaemonConnector.connectToDaemon(DaemonConnector.java:333)
at org.jboss.fuse.mvnd.client.DaemonConnector.connectToDaemonWithId(DaemonConnector.java:320)
... 4 more
Caused by: java.net.SocketTimeoutException
at sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:129)
at org.jboss.fuse.mvnd.client.DaemonConnector.connect(DaemonConnector.java:370)
... 6 more
I am using cmder, that uses Git Bash under.
WINDOWS CONSOLE
C:\workspace\test-project>mvnd --version
Oct 21, 2020 8:24:47 AM org.jline.utils.Log logr
WARNING: Unable to create a system terminal, creating a dumb terminal (enable debug logging for more information)
Maven Daemon 0.0.8-windows-amd64 (native)
Exception in thread "main" org.jboss.fuse.mvnd.common.DaemonException$ConnectException: Could not connect to the Maven daemon.
Daemon uid: 37ef6dbe-e148-4cd9-9542-77119b8bbe35
log file: C:\apps\mvnd-0.0.8-windows-amd64\daemon\daemon-37ef6dbe-e148-4cd9-9542-77119b8bbe35.log
----- Last  20 lines from daemon log file - C:\apps\mvnd-0.0.8-windows-amd64\daemon\daemon-37ef6dbe-e148-4cd9-9542-77119b8bbe35.log -----
08:24:50.521 I Daemon started
08:24:50.523 D daemon is running. Sleeping until state changes.----- End of the daemon log -----
    at org.jboss.fuse.mvnd.client.DaemonConnector.connectToDaemonWithId(DaemonConnector.java:323)
    at org.jboss.fuse.mvnd.client.DaemonConnector.startDaemon(DaemonConnector.java:238)
    at org.jboss.fuse.mvnd.client.DaemonConnector.connect(DaemonConnector.java:119)
    at org.jboss.fuse.mvnd.client.DefaultClient.execute(DefaultClient.java:185)
    at org.jboss.fuse.mvnd.client.DefaultClient.main(DefaultClient.java:70)

Caused by: org.jboss.fuse.mvnd.common.DaemonException$ConnectException: Could not connect to server <IP_ADDRESS>/<IP_ADDRESS>:58596.
at org.jboss.fuse.mvnd.client.DaemonConnector.connect(DaemonConnector.java:380)
at org.jboss.fuse.mvnd.client.DaemonConnector.connectToDaemon(DaemonConnector.java:333)
at org.jboss.fuse.mvnd.client.DaemonConnector.connectToDaemonWithId(DaemonConnector.java:320)
... 4 more
Caused by: java.net.SocketTimeoutException
at sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:129)
at org.jboss.fuse.mvnd.client.DaemonConnector.connect(DaemonConnector.java:370)
... 6 more

Just checked this on my business laptop (which is using Checkpoint VPN) and it works for me! TBH I would have expected to see the same problem.
Anway, it might help if one could tell mvnd to bind to  and connect to <IP_ADDRESS> instead of <IP_ADDRESS>.

I was wrong, the second run fails with the same connection timeout! And interestingly, it even fails with disconnected VPN.

What is the output of mvnd --status?
And what happens when you issue mvnd --stop and try again?

I am getting a:
λ mvnd --status
Oct 21, 2020 2:06:06 PM org.jline.utils.Log logr
WARNING: Unable to create a system terminal, creating a dumb terminal (enable debug logging for more information)
                                    UUID      PID   Port   Status  Last activity

Same for Windows CMD.
Running mvnd --stop, doesn't change the above output.
To clarify I am using also Checkpoint VPN, and I am getting this error connected or disconnected as @famod  commented.
Maybe it possible that Checkpoint VPN is using or blocking somehow port 58596?

@galegofer does you machine have other network adapters, e.g. VirtualBox host-only adapters?

@famod  I have ethernet, wifi, "Check point Virtual Network Adapter ..." and "Hyper V Virtual Ethernet Adapter"

@galegofer https://github.com/mvndaemon/mvnd/commit/0656e1337ad75982f07df1acf2805a5f4fdce62c fixed it for me.
So in case you want to try it out before 0.0.9 is released, you can try the SNAPSHOT: https://github.com/mvndaemon/mvnd/suites/1382179406/artifacts/22751642

You got it!, good job!

Can we close this one then?

It looks fixed to me, thanks @famod and @ppalaga !

Fixed by https://github.com/mvndaemon/mvnd/commit/0656e1337ad75982f07df1acf2805a5f4fdce62c

Just for the record, @ppalaga The any local address <IP_ADDRESS> was the issue on one of my macs as well… Using the loopback works. 👍

Thanks for the info. I'd release when I figure out how to integrate the new brew tap into the release pipeline.