Build stability --- remove maxcpucount from msbuild switches

Build has been quite unstable, locally and on the CI for a few days.
trying to revert the maxcpu change.

@dotnet-bot test this please : passed let's try again.

@dotnet-bot test this please : passed let's try again.

@dotnet-bot test this please : passed let's try again.

Okay that seems to work relatively well. Going to merge it.

Hmmm.. Would be good to solve the underlying issue at some point :) Any links to unstable build logs?
Note that building VisualFSharp.sln in Visual Studio uses multi-proc build by default so contributors are exposed to any problems

The build is going to get obliterated shortly.   The move to netstandard2.0 will change the way we do virtually everything.  So I would just hold off trying to fix it for now.
From: Don Syme<EMAIL_ADDRESS>Sent: Tuesday, May 23, 2017 6:12 AM
To: Microsoft/visualfsharp<EMAIL_ADDRESS>Cc: Kevin Ransom<EMAIL_ADDRESS>State change<EMAIL_ADDRESS>Subject: Re: [Microsoft/visualfsharp] Build stability --- remove maxcpucount from msbuild switches (#3103)
Hmmm.. Would be good to solve the underlying issue at some point :) Any links to unstable build logs?
Note that building VisualFSharp.sln in Visual Studio uses multi-proc build by default so contributors are exposed to any problems
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fvisualfsharp%2Fpull%2F3103%23issuecomment-303393052&data=02|01|Kevin.Ransom%40microsoft.com|dc903894f65b41a9517308d4a1dd571b|72f988bf86f141af91ab2d7cd011db47|1|0|636311419405377196&sdata=dCZ9C5KRi3XsYwNJHlpmVXBDZSR3m%2FlLzqqc%2BLvHrnw%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAE76FgxUrsA7GeGqXhMsJdHidRyDTG3jks5r8tsqgaJpZM4NiuP4&data=02|01|Kevin.Ransom%40microsoft.com|dc903894f65b41a9517308d4a1dd571b|72f988bf86f141af91ab2d7cd011db47|1|0|636311419405377196&sdata=p05IKn7YWaOcC3ax%2FsHdV0h9GZoDGuOqmLfaBqf5L9I%3D&reserved=0.

The build is going to get obliterated shortly.   The move to netstandard2.0 will change the way we do virtually everything.  So I would just hold off trying to fix it for now.

Okey dokey.


Destroy interactive on mobile lead to Uncaught TypeError on other sprite events.

Version

Phaser Version: 3.15.1

Operating system: android

Browser: chrome

Description
On mobile device, when a draggable interactive image is destroyed, the 'pointerdown' event on other 'draggable' sprite lead to 'Uncaught Type Error' exception.
Here is the example to illustrate:
const sprite1 = this.add.image(150, 150, 'Character Pink Girl');
sprite1.setInteractive({
    pixelPerfect: true,
    draggable: true,
});
sprite1.on('pointerdown', () => {
    sprite1.destroy();
});

const sprite2 = this.add.image(250, 150, 'Character Pink Girl');
sprite2.setInteractive({
    pixelPerfect: true,
    draggable: true,
});
sprite2.on('pointerdown', () => {
    sprite2.destroy();
});

On Desktop, everything is fine. We can click on both images and both are deleted properly.
On my Android phone, the first one works well but the second one does not works.
It generate the following LogCat log:
12-13 16:28:51.817 14773 14773 I chromium: [INFO:CONSOLE(76876)] "Uncaught TypeError: Cannot read property 'dragState' of undefined", source: http://<IP_ADDRESS>:4000/vendors~game.js (76876)

After some investigation, it appears that problem come from the fact to destroy the image into the event.
When doing this:
const sprite1 = this.add.image(150, 150, 'Character Pink Girl');
sprite1.destroy();

const sprite2 = this.add.image(250, 150, 'Character Pink Girl');
sprite2.setInteractive({
    pixelPerfect: true,
    draggable: true,
});
sprite2.on('pointerdown', () => {
    sprite2.destroy();
});

it works well.
Thanks
Big thank to Phaser team :+1:

Found source of the problem.
We must destroy the event first:
const sprite1 = this.add.image(150, 150, 'Character Pink Girl');
sprite1.setInteractive({
    pixelPerfect: true,
    draggable: true,
});
const handler = () => {
    sprite1.off('pointerdown', handler);
    sprite1.destroy();
};
sprite1.on('pointerdown', handler);

I don't know if it is even a bug or my misunderstanding :-)

i get the same error when i destroy my image inside of the dragenter event
          this.input.on('dragenter',  (pointer:PointerEvent, gameObject, dropZone)=> {

            try {
              this.myBillet = gameObject as Billet;

              let v:string = gameObject.texture.key;
              v=v.substr(0,v.length-2);

              if(this.myBillet._zone!="ZONE_REPONSE" && dropZone.name=="ZONE_REPONSE"){

                this.myBillet._zone=dropZone.name;
                this.billets_sur_table.push(this.myBillet);
                if(!this.tables.containsKey(v)){

                  this.tables.add(dropZone.name,this.billets_sur_table);

                 }
                 else{
                  this.tables[this.myBillet._zone]=this.billets_sur_table;
                 }
                 var billet = new Billet(this,gameObject.input.dragStartX, gameObject.input.dragStartY,v,this.groupe_portefeuilles,"ZONE_CREATION", {font:"20px 'Arial'",fill:"#000"});
                 this.tweens.add({
                  targets: gameObject,
                  y: pointer.y,
                  x:pointer.x,
                  duration: 1000,
                  ease: 'Power2',
                  completeDelay: 1000
              });
              }else if(this.myBillet._zone=="ZONE_REPONSE" && dropZone.name=="ZONE_CREATION"){

                var b = this.myBillet;
                var evens = _.remove(this.billets_sur_table, function(n) {
                  return n == b;
                });

                this.tables["ZONE_REPONSE"]=this.billets_sur_table;
                this.myBillet.input.enabled=false;
                this.myBillet.destroy();

              }

Thank you for submitting this issue. We have fixed this and the fix has been pushed to the master branch. It will be part of the next release. If you get time to build and test it for yourself we would appreciate that.

Many thanks @photonstorm. I Put to test it as an entry in my backlog. Therefor it will be done soon :-)

I've just tested on v3.16.2 and it works perfectly. Many thanks again.


Update to 2021 ROSES support

As part of the update, remove all tabs as well as previous years' support for ROSES program which are no longer necessary.   Leave the existing pages in place for the moment; they may be deleted at a later date.

done


CAMEL-18201 Enhance CamelTestSupport to turn off context stopping

fixes https://issues.apache.org/jira/browse/CAMEL-18201
This PR adds an option to turn  off the context stopping. It is possible by junit5's ConfigurationProperty (which falls back also to system variable - used in the junit test). If context does not stop automatically method doSetUp is not called if context already exists.
I added 2 tests to cover both option values (off and on).

WDYT? @davsclaus  This change will allow camel quarkus to run CamelTestSupport based tests (See https://github.com/apache/camel-quarkus/issues/3511) and will  allow users to reuse old camel tests in camel-quarkus JVM mode (without need of bigger refactor)..

Hmmm so this seems a bit like the camelContextPerClass functionality that is already there.
And the name of this option is maybe a bit unclear as it will reuse the previous context in the following tests.

Functionality may look similar but it is not. PerClass functionality will stop context after each class. This option won't stop context after each class, it will never stop context.
As for the name, I see that it may be a bit unclear, what about NEVER_STOP_CONTEXT/DONT_STOP_CONTEXT or SHARE_CONTEXT_FOR_ALL_TEST/SHARE_CONTEXT?

Maybe what CEQ needs is being able to override some protected methods in CamelTestSupport to control more fine grained what CEQ needs to do in the doSetup and teardown methods.
Then CEQ can override these methods and do something different.
Maybe the existing doStopCamelContext and setup is useable as-is, eg you can try to implement this in CEQ and then override doStopCamelContext to not stop camel, or only stop when really needed. And doSetup you can then skip calling super if already started.
Then maybe this is possible to just do in CEQ only and keep camel core as-is

Overriding method in CEQ was mt preferred solution, unfortunatelly method I need to override is private static  private static void doStopCamelContext(
If making it non-static protected is a better solution, I will use that. (I chose a configurable option, as I saw similar options there)
If you agree, I'll modify the PR to change method signature and allow overriding of it.

Yeah its better to make the method protected

Thank you! I change only 2 signatures and keep 1 test covering the overriding of both methods.

LGTM great work @JiriOndrusek

I'll check it.

I've found the reason in https://github.com/apache/camel/actions/runs/2515347416
[ERROR] Failed to execute goal net.revelc.code.formatter:formatter-maven-plugin:2.17.1:validate (validate) on project camel-test-junit5: File '/home/runner/work/camel/camel/components/camel-test/camel-test-junit5/src/test/java/org/apache/camel/test/junit5/CamelTestSupporOneContextForAllTest.java' has not been previously formatted.  Please format file and commit before running validation! -> [Help 1]

I'fixed by running mvn process-resources -Pformat


Row fieldclasses unclear

Hi there,
I'm using the Row field quite often but for some reason whatever I try to change
i.e. childConfig / wrapperClasses / fieldClasses etc. I don't see anything happen and it's very unclear form the documentation which method is meant for which classes.
Would it be possible to get a clearer picture in the documentation what all these methos for the Row field do?

It looks like row wrappers are actually using itemWrapperClasses, and individual items don't have wrappers at all (they are just plain paragraphs, unless the field is a File or Boolean field), if I understand the source and docs correctly.
Below, in the Vue component, the div looks like a row wrapper (because it wraps all items in a given row), but it uses itemWrapperClasses
// resources/js/components/row/DetailField.vue

  <DetailFieldItem
  // ...
  />

There are some default classes defined in the Row nova field:
// src/Row.php

public $rowWrapperClasses = 'flex items-center border-40 border relative';

But they don't seem to be rendered anywhere.
Field items don't seem to have wrappers at all (they are paragraphs), unless they are Boolean or File fields:
// resources/js/components/row/DetailFieldItem.vue

<template>

  <detail-nova-fields-file
    v-else-if="isFile"
    :value="display"
    v-bind="{ ...$props }"
  />

{{ display }}

</template>

It looks like row wrappers are actually using itemWrapperClasses, and individual items don't have wrappers at all (they are just plain paragraphs, unless the field is a File or Boolean field), if I understand the source and docs correctly.
Below, in the Vue component, the div looks like a row wrapper (because it wraps all items in a given row), but it uses itemWrapperClasses
// resources/js/components/row/DetailField.vue

  <DetailFieldItem
  // ...
  />

There are some default classes defined in the Row nova field:
// src/Row.php

public $rowWrapperClasses = 'flex items-center border-40 border relative';

But they don't seem to be rendered anywhere.
Field items don't seem to have wrappers at all (they are paragraphs), unless they are Boolean or File fields:
// resources/js/components/row/DetailFieldItem.vue

<template>

  <detail-nova-fields-file
    v-else-if="isFile"
    :value="display"
    v-bind="{ ...$props }"
  />

{{ display }}

</template>

Ok, I just realized that rowWrapperClasses are used in form views (creating/updating a model), while itemWrapperClasses are used in detail views. In any case, I think this could be made clearer in the documentation.

Ok, I just realized that rowWrapperClasses are used in form views (creating/updating a model), while itemWrapperClasses are used in detail views. In any case, I think this could be made clearer in the documentation.

Thank you @malinowskip will merge!

Thank you @malinowskip will merge!


"UTF-8 decoding error: Not enough space" when using Japanese Text

using Japanese text with Text:send('確認」を押して続行します') produces an error.
Error: lib/slog-text.lua:326: UTF-8 decoding error: Not enough space
stack traceback:
        [string "boot.lua"]:777: in function <[string "boot.lua"]:773>
        [C]: in function 'get_character_width'
        lib/slog-text.lua:326: in function 'send'
        main.lua:63: in function 'load'
        [string "boot.lua"]:586: in function <[string "boot.lua"]:585>
        [C]: in function 'xpcall'
        [string "boot.lua"]:793: in function <[string "boot.lua"]:780>
        [C]: in function 'xpcall'

This only occurs in context of the library and does not occur with love.graphics.print

Yes, due to how I'm reading the strings byte by byte, Unicode requires a wrapper.
If you wrap the string [|like this] or character by character [|a][|b][|c] it will work.
You can see this in the example main.lua

Update, in case you were still looking at this library @applesaucyy. In 1.5 (Unicode) release and above you no longer have to tag utf8 text strings.


Link to Slack inviter somewhere too: slack.cncf.io

Link to Slack inviter somewhere too: slack.cncf.io - I just talked to somebody to whom it was not obvious: "looks like this Slack is only for cool people".

Taken care of in #28.


Implement clear submit errors action

An initial implementation to be able to supress existing submit errors.

Codecov Report

Merging #2615 into master will decrease coverage by -0.08%.
The diff coverage is 80%.

@@            Coverage Diff             @@
##           master    #2615      +/-   ##
==========================================
- Coverage     100%   99.92%   -0.08%
==========================================
  Files          66       66
  Lines        1371     1375       +4
==========================================
+ Hits         1371     1374       +3
- Misses          0        1       +1

Impacted Files
Coverage Δ

src/actionTypes.js
100% <100%> (ø)
:white_check_mark:

src/actions.js
100% <100%> (ø)
:white_check_mark:

src/reducer.js
99.58% <50%> (-0.42%)
:x:

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 fc2b82f...450753a. Read the comment docs.

Published in v6.6.0.


pvc cleanup fixes

IMPORTANT: Please do not create a Pull Request without creating an issue first.
Problem:

In certain cases when the VM is created and deleted immediately the ownership references may not be cleaned up from the PVC.
The harvester validation webhook, prevents deletion of such PVCs. The only options in such a scenario are to edit the PVC to drop the ownership annotation or remove the same from longhorn console.
The problem is likely caused by a race condition in the virtualmachine controller, which has an OnChange method and OnRemove method to SetOwnerReferences and RemovedOwnerReferences from the PVC's making up the VM.
Solution:

The PR introduces a possible fix, by merging the OnChange and OnRemove handlers into a single OnChange handler, along with custom finalizers to ensure resource cleanup.
Related Issue:
https://github.com/harvester/harvester/issues/2677
Test plan:

To replicate the issue, I used the following VM json and shell script to trigger the VM creation and deletion.
{
    "apiVersion": "kubevirt.io/v1",
    "kind": "VirtualMachine",
    "metadata": {
        "annotations": {
            "harvesterhci.io/vmRunStrategy": "RerunOnFailure",
            "harvesterhci.io/volumeClaimTemplates": "[{\"metadata\":{\"name\":\"workload-1-disk-0-8p4bi\",\"annotations\":{\"harvesterhci.io/imageId\":\"default/image-98xqv\"}},\"spec\":{\"accessModes\":[\"ReadWriteMany\"],\"resources\":{\"requests\":{\"storage\":\"10Gi\"}},\"volumeMode\":\"Block\",\"storageClassName\":\"longhorn-image-98xqv\"}}]",
            "kubevirt.io/latest-observed-api-version": "v1",
            "kubevirt.io/storage-observed-api-version": "v1alpha3",
            "network.harvesterhci.io/ips": "[]"
        },
        "labels": {
            "harvesterhci.io/creator": "harvester",
            "harvesterhci.io/os": "ubuntu"
        },
        "name": "workload-1",
        "namespace": "default"
    },
    "spec": {
        "runStrategy": "RerunOnFailure",
        "template": {
            "metadata": {
                "annotations": {
                    "harvesterhci.io/sshNames": "[]"
                },
                "creationTimestamp": null,
                "labels": {
                    "harvesterhci.io/vmName": "workload-1"
                }
            },
            "spec": {
                "domain": {
                    "cpu": {
                        "cores": 2,
                        "sockets": 1,
                        "threads": 1
                    },
                    "devices": {
                        "disks": [
                            {
                                "bootOrder": 1,
                                "disk": {
                                    "bus": "virtio"
                                },
                                "name": "disk-0"
                            },
                            {
                                "disk": {
                                    "bus": "virtio"
                                },
                                "name": "cloudinitdisk"
                            }
                        ],
                        "inputs": [
                            {
                                "bus": "usb",
                                "name": "tablet",
                                "type": "tablet"
                            }
                        ],
                        "interfaces": [
                            {
                                "masquerade": {},
                                "model": "virtio",
                                "name": "default"
                            }
                        ]
                    },
                    "features": {
                        "acpi": {
                            "enabled": true
                        }
                    },
                    "machine": {
                        "type": "q35"
                    },
                    "memory": {
                        "guest": "3996Mi"
                    },
                    "resources": {
                        "limits": {
                            "cpu": "2",
                            "memory": "4Gi"
                        },
                        "requests": {
                            "cpu": "125m",
                            "memory": "2730Mi"
                        }
                    }
                },
                "evictionStrategy": "LiveMigrate",
                "hostname": "workload-1",
                "networks": [
                    {
                        "name": "default",
                        "pod": {}
                    }
                ],
                "volumes": [
                    {
                        "name": "disk-0",
                        "persistentVolumeClaim": {
                            "claimName": "workload-1-disk-0-8p4bi"
                        }
                    },
                    {
                        "cloudInitNoCloud": {
                            "networkDataSecretRef": {
                                "name": "workload-1-sg8ma"
                            },
                            "secretRef": {
                                "name": "workload-1-sg8ma"
                            }
                        },
                        "name": "cloudinitdisk"
                    }
                ]
            }
        }
    }
}

#!/bin/sh
TOKEN="token"
ENDPOINT="endpoint"

curl -k -u "${TOKEN}" -H "Content-Type: application/json" -X POST --data @workload.json ${ENDPOINT}/v1/kubevirt.io.virtualmachines &
sleep 1
curl -k -u "${TOKEN}" -H "Content-Type: application/json" -X DELETE ${ENDPOINT}/v1/kubevirt.io.virtualmachines/default/workload-1 &
sleep 10
curl -k -u "${TOKEN}" -H "Content-Type: application/json" -X DELETE ${ENDPOINT}/v1/persistentvolumeclaims/default/workload-1-disk-0-8p4bi

The script will create a workload-1 VM along with PVC claim workload-1-disk-0-8p4bi
NOTE: Before using the script please ensure that image and storageclass details are updated in the VM json.

Do we still need to verify the OwnerReference on the PVC webhook when it is deleted?
https://github.com/ibrokethecloud/harvester/blob/c7b0d16e33a83291e4e7c637bc64fee00005df34/pkg/webhook/resources/persistentvolumeclaim/validator.go#L69-L82

the webhook check would be to avoid an in-use pvc from being deleted

@mergify backport v1.1


Delete unnecessary files

Fixes : [#110 ]
Description :
Delete some unnecessary files and resolve the conflicts in App.js from last pr.
Screenshot of changes :

Please ensure Checkmark the following :

[x] - Tested Localy
[x] - Checked in IE11 and Firefox
[ ] - Checked in mobile
[ ] - Backend work
[x] - Frontend work
[x] - Bug Fixes
[ ] - Enhancements

@hsluoyz @BetaCat0 @nodece There are some conflicts after last merge. Please review.


Feat side bar/#114

Issue: #114

Feature

Create sidebar and header section.

Bugfix

Description
Adjust main container borders and paddings

Cause
The borders and paddings was just for testing, and were conflicting with our new components

Solution
Remove borders and adjust paddings

Changelog

Add new header section
Add new sidebar section
Adjust sizes of home containers

Visual evidences :framed_picture:

Checklist

[x] Issue linked
[x] Build working correctly
[ ] Tests created

A senhorita Flavia não assinou o PR

adicionei o ladle stories para o header e sidebar hj c um novo commit


Support more colors

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (f1124c9) to head (191908f).

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #88   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           57        57
  Lines         1767      1779   +12
=========================================
+ Hits          1767      1779   +12

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Added global http proxy argument for using with tor in k8s or in dock…

Now you can set -http-proxy <IP_ADDRESS>:8080 as argument and use tor for http runner

@Arriven reworked in more universal way


Any Plans to support Apple Authentication Key (.p8) files?

Hi there,
since a while Apple supports authentication keys that never expire and can be re-configured after creation. Some services already support this. Any plans my favourite push testing utility supports this too in near future?

Hi @Blackjacx, thanks for the considerate argumentation. At this point there are no plans to support this. There's little overlap with the deprecated binary interface, so it would either require a significant redesign or starting from scratch. I figure a new tool, from the ground up, would be a better approach, but not something I've had time for. There's more discussion here: https://github.com/noodlewerk/NWPusher/issues/55.


Move regression tests to evaluation/

This pr is to address https://github.com/OpenDevin/OpenDevin/issues/76
Changes include:

move regression folder to evaluation folder
change directory structure to /case/ouputs/agents/worspace or /case/output/agents/logs.txt
change run.sh to iterate every agent as well if defined in the case/output/agents folder

Agree, now that #93 is in, we should use python opendevin/main.py instead of docker run


chore: Do not report flakes on main branch with no corresponding issue

Not sure on how to test this, but builds on main are reporting as failing due to no corresponding issue to post a comment to

Looks like this indeed works: https://github.com/subconsciousnetwork/noosphere/actions/workflows/run_test_suite.yaml?query=branch%3Amain


show the content size in kB, MB, etc., according to the size

Currently, the content size is shown in bytes in the HTML preview, which can sometimes make it inconvenient to interpret the file's size.

I updated the Jinja2 template in a brute-force manner...


Added afterImport callback for datatypes

[x] I updated the changelog
[x] I updated the composer.json version
[ ] I wrote tests
[x] I am proud of my code

There are even more cache resets in Schematic currently, can't they be made to work with this?

Maybe, I'll need to do some more work


Switch to Biome

I'd like us to consider switching to Biome. Biome provides both a formatter and a linter, and is super fast compared to ESLint and Prettier. I've been using Biome for some other projects and I've been really pleased with it. It has a really sane default configuration, is easy to configure, has good editor/IDE support, and I find its output/suggestions much more helpful.
Its Differences with Prettier page is also a good read.
Below are some timing results (using GNU time) on the Samf4 project on master, using the default Biome config.
ESLint
root@e72eafc92be7:/app# time yarn run eslint:check

real	0m6.858s
user	0m9.880s
sys	0m1.168s

Time to run: ~6s
Biome lint
root@e72eafc92be7:/app# time yarn run biome lint .

***truncated output***

real	0m0.668s
user	0m0.841s
sys	0m0.210s

Time to run: ~0.6s
Biome format
root@e72eafc92be7:/app# time yarn run biome format .

***truncated output***

real	0m0.710s
user	0m0.747s
sys	0m0.271s

Time to run: ~0.7s
Biome check (same as lint+format in one step)
root@e72eafc92be7:/app# time yarn run biome check .

***truncated output***

real	0m0.733s
user	0m0.953s
sys	0m0.270s

Time to run: ~0.7s

@emilte Noen tanker om dette? Har gjort endringene i #1226 hvis du vil teste det ut

Hittil synes jeg alt rundt formatter og linter har vært herk i frontend verden. Jeg støtter å prøve noe annet


Omit test- and config files from test coverage

It doesn't make much sense to track coverage of test- and configuration files, so let's just omit them from coverage reporting.

[X] You have squashed relevant commits together.
[X] Your PR relates to one subject.

*If you do not know what makes a good commit message, or why it
is important, please refer to these resources: 1, 2, 3.

:+1:


Update llama_guard_version in inference.py

What does this PR do?
This PR updates the llama_guard_version argument in inference.py as it takes only string

Fixes # (issue)
Feature/Issue validation/testing
Please describe the tests that you ran to verify your changes and relevant result summary. Provide instructions so it can be reproduced.
Please also list any relevant details for your test configuration.

[ ] Test A
Logs for Test A

[ ] Test B
Logs for Test B

Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you read the contributor guideline,
Pull Request section?
[ ] Was this discussed/approved via a Github issue? Please add a link
to it if that's the case.
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

Thanks for contributing 🎉!

Closing since the repo has been updated but please feel free to update the PR if you are still interested in contributing!


correct isolated margin account transfer API endpoint

the "raw" part is updated with transfer, but "path" still has create

the "raw" part is updated with transfer, but "path" still has create

Thanks for pointing it out, corrected.


Items count blinking when accessed via AE2 storage bus

Industrial Foregoing Version: 1.12.13
TeslaCoreLib Version: 1.12.2-1.0.15
Crashlog (If Any): none
When:

machine, i.e. Material Stonework Factory:
** is set to make i.e sand (replicated with gravel, silicon, etc)
** has ae2 storage bus attached (in my case from the bottom)
additionally some number (1) of the items produced is also stored in attached chest
Then the items count on ae2 terminals keeps changing constantly - making it unreadable.

:wave: Sorry but Industrial Foregoing has ended support for version 1.12. I'm closing this issue as it will no longer be updated for that version. Thanks for playing with the mod.


Add new functions

Close #49
Close #51
Close #60

Codecov Report

Merging #62 into develop will decrease coverage by 3.53%.
The diff coverage is 70.83%.

@@            Coverage Diff             @@
##           develop     #62      +/-   ##
==========================================
- Coverage    84.44%   80.9%   -3.54%
==========================================
  Files            5       5
  Lines           90     110      +20
==========================================
+ Hits            76      89      +13
- Misses          14      21       +7

Impacted Files
Coverage Δ

pycep_correios/__init__.py
100% <100%> (ø)
:arrow_up:

pycep_correios/client.py
78.26% <68.18%> (-5.74%)
:arrow_down:

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 8516be7...3cc2514. Read the comment docs.


(Task) Add S3 Connector - Accelerators E2E test

Closed by: https://github.com/spiceai/spiceai/pull/3154


goBack({key:key}) not working

Current Behavior
I have a page with key 'Init' in stack and I want pop to this page with goBack({key:'Init'}),
But nothing happen.
I check code in src/routers/StackRouter.js,
if (action.type === NavigationActions.BACK) {         let backRouteIndex = null;         if (action.key) {           const backRoute = state.routes.find(             /* $FlowFixMe */             (route: *) => route.key === action.key,           );           /* $FlowFixMe */           backRouteIndex = state.routes.indexOf(backRoute);         }
The first route's key should equal to action'key. but return false.

Your Environment

software
version

react-navigation
1.0.0-beta.9

react-native
0.44.0

node
v6.9.1

npm
3.10.8

Having this issue myself. Did you resolve it?

Having this issue myself. Did you resolve it?

The goBack docs are meaningless.  What does this mean??

key - string or null - optional - If set, navigation will go back from the given key. If null, navigation will go back anywhere.

Hmm.. I didn't notice that is says "will go back FROM the given key".
I was under the impression that it would go back TO the given key.

I have noticed this as well. Tried passing, some other key to a screen, null and nothing. Can't seem to get a screen to dismiss programatically.

If A,B,C in stack,and you want goback to A,you should pass the key of B screen.Like goBack('keyofB'). It seem very strange to me,but it works.

#905 This pr is related to the strange usage,maybe the library need some extra info to make the animation so they need the page route name which you back from.

None work for me!!

@dann1609 you're probably providing the wrong key.. in a stack with multiple screens, the key of the screen is different from the routeName... just log the entire this.props.nav object.. you might find the key looks something like:
key:id-1510829501204-2
routeName:Splash

if you provide that key, the goBack will work!

thanks @lsorin81  I found this solutions weeks ago but I do not post here. Thanks for post!

@lsorin81  thanks for that! Right before reading this issue, I was thinking if I needed to use key instead of the actual routeName I use to navigate to new screens.
Is there any reason why react-navigation generates a random keys for some routes?
The way is done, we have to pass the route key thru navigation params


What happens when an observation is started for a target which is already intersecting?

My suggestion: since the previous intersection rect is currently null for this observer/target pair, the next layout step should see that the new intersection is different and enqueue a callback at that point in time. This keeps us from requiring a layout at the time observer.observe() is called, and the only gap would be if nothing happens on the main thread after the observation is started.

LGTM

Followup observations:

This works regardless of if the target was previously being observed, since the previous intersection rect is stored 'per observer/target pair'
We should probably call the target 'dirty' and mark that it needs a re-layout, otherwise app developers will intentionally make a change to force layout, since that's the only way to guarantee the callback gets triggered.
Thoughts?

Agree that firing the callback in the next frame makes sense.  No need to do it immediately, but there is need to do it.
Also agree that the target should definitely do a re-layout asap, so you get dependable callback firing.

Discussed in person. Don't want to force the whole rendering pipeline to run if nothing changed. Instead, will post a task to run just the IO update steps.
This has a slight downside of making it so that we might run the update steps twice in the rare case where observe is called, then the task fires, then the dom is modified, then the rendering steps run. Maybe that's OK?
In an ideal world, we could say that we'd post the task only if a new rendering frame isn't scheduled, but we're unsure if there's a way to say that in the specs.

That should be possible, actually.  Put together some generic language about it not posting if it's about to be posted anyway, and then give the specific example of our rendering frames.

esprehn says we should just schedule a frame. but it's cheap since no layout is dirty.

And that it's very rare to observe without changing anything in the page that schedules a frame.


Animation becomes slow after a while (memory leak?)

Have a look at this video:
https://user-images.githubusercontent.com/19586719/149635636-594687cc-bb11-4a90-baaf-219a2ee0238a.mp4
I'm using this animation in my application. After the app is left to run for a while, it starts lagging (as shown in the initial part of the video), after a refresh it works fine for a while. Maybe there's a memory leak somewhere.

Hey @a-y-u-s-h, thanks for raising this! I've investigated and found a bug in our render loop, which has now been fixed. If you upgrade to version 0.0.31 of rive-react you should not see this lagging any more.

Hey @a-y-u-s-h, thanks for raising this! I've investigated and found a bug in our render loop, which has now been fixed. If you upgrade to version 0.0.31 of rive-react you should not see this lagging any more.

Thank you! I had the same issue, and I solved it easily by updating the version!


Install Generator doesn't generate in SCSS file

I read the documentation, and got as far as step 3.
Running the command
rails generate jquery:datatables:install

It added //= require dataTables/jquery.dataTables to my application.js file.
When I checked my application.css.scss file, it wasn't there.
Needless to say, datatables did not work.

also doesnt work for me..
rails generate jquery:datatables:install bootstrap3
=> Could not find generator jquery:datatables:install.

@lichtamberg I also faced this issue. Please update your Gemfile like as gem 'jquery-datatables-rails', '~> 3.2' would you solve your issue.
@ricardodovalle If css minifest extension is .css.scss then install generator wont edit css minifest file. I think it seems an issue. Thoughts please?

@sivagollapalli I agree that the generator does not recognize .css.scss filetypes. I tried the generate the LOC myself and found that only the JavaScript line was inserted.


Fix "re.match object is not serializable" and correctly read the...

... _uses_js property

Closing because selected wrong branch to merge into


library not found for -lRNDeviceInfo-tvOS

I just installed the library, and before the project was building fine, now I just get this error:
react-native run-ios
Error:
ld: library not found for -lRNDeviceInfo-tvOS
clang: error: linker command failed with exit code 1 (use -v to see invocation)
** BUILD FAILED **

Hi, this is a know problem with a known solution:
https://github.com/rebeccahughes/react-native-device-info#troubleshooting

Sorry I did not see that section! Works great now :


IPv6 support

https://github.com/eclipse-opendut/opendut/blob/90a4bfeb7e382ece7c56d11b151f50e002423a2f/opendut-edgar/src/service/network_device/manager.rs#L80

Hi, thanks for reaching out and reading the code. The IPv4 supports is only relevant for the virtual private network provided by netbird. We are still able to bridge any kind of layer two (or above) traffic over this private network including IPv6. Therefore, it is not a restriction to our use case. Unless netbird is changing the address assignment we don't need to change this at all.

Hi. Yes. I agree this should be low prio for now. Seems like netbird is slowly moving in that direction, so we should at least keep that in mind:
https://github.com/netbirdio/netbird/pull/578


Fix for problem where agent is stopped and does not restart

This fixes a problem where the agent on a controller is stopped when a node leaves a swarm and is never restarted. By adding a check to see if the agent is nil the agent init routine will run and the other checks that guard against multiple agents will still function as intended. Here's some more information about how this problem presents itself https://github.com/docker/for-linux/issues/495.

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "fix-agent-init-problem" git@github.com:kylewuolle/libnetwork.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

ping @fcrisciani @euank ptal

whoops, wrong Euan. Meant @euanh :blush:

Can you pls fix below error
^@^@🐳 check-protobuf
🐳 lint
🐳 gosimple
🐳 vet
🐳 ineffassign
🐳 fmt
controller.go
👹 please format Go code with 'gofmt -s -w'
Makefile:155: recipe for target 'fmt' failed
make: *** [fmt] Error 1
Makefile:114: recipe for target 'check' failed
make: *** [check] Error 2
Exited with code 2


dotnet command does not exsit

Problem encountered on https://dotnet.microsoft.com/en-us/learn/dotnet/hello-world-tutorial/install
Operating System: linux
It says dotnet command does not exsit

Have you tried opening a new command prompt window after installing the SDK?


PP-3061 Add gateway account external ID

We are currently using the internal gateway_account_id for publicauth's paths
This has worked fine until we added direct debit gateway accounts. As we store
gateway accounts in two different connectors / dbs, there will be clashes in account ids
Using external account ids will avoid this issue. For now, as credit card account don't have
any external id, we are going to support both accounts.
If the <accountId> is numeric, it's an internal account id and we will search in the db for
CC tokens. If it's alphanumeric, it's an external account id and we will search for DD tokens.

This piece of logic will be removed once we backfill the data and assign an external id to all
existing card gateway accounts in cc connector.
with @simad

sorry @alexbishop1  and @chrisgrimble  :/ the gods of selfservice decided this is not needed anymore, as we can't send both internal and external ids due to how things work over there. Closing this for now.


How impactful is can_bus usage?

I find that the transformer queries incorporate ego can_bus information.
https://github.com/zhiqi-li/BEVFormer/blob/5a25c8b3b70956174b3c1876321967e265b2da42/projects/mmdet3d_plugin/bevformer/modules/transformer.py#L158-L162
I was wondering how the performance changes without can_bus?
Thank you!

So the B means to disable the Temporal Self-Attention??


Upgrade to Rust 2021

Replace #172 and fix all clippy warnings
Resolves https://github.com/hermitcore/rusty-hermit/issues/166.

bors r+

The toolchain should stay at nightly-2021-09-29 see https://github.com/hermitcore/libhermit-rs/pull/297

bors +1

bors r+


libguestfs-appliance: Add aarch64-linux to meta.platforms

Description of changes
Added aarch64-linux to meta.platforms of libguestfs-appliance.
Recent update of package added the meta.platforms, which didn't contain aarch64-linux and thus aarch64-linux builds with guestfstools started to fail.
Things done
I also built virtual machine on aarch64-linux platform to verify this works.

Built on platform(s)

[ ] x86_64-linux
[X] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

@ofborg build libguestfs-with-appliance libguestfs-with-appliance.passthru.tests

Same questions as in #226509:

How is the prebuilt appliance useful on aarch64-linux if it's an x86 image? Does the installCheck pass?
If yes, should we extend the platforms to platforms.linux?

And it doesn't pass on ofborg.


RDKit first build

Forked from conda-forge with some modifications to make the recipe simpler and adapt it to our standards.
For some reason, some Prefect builds randomly fail after building the package as the next "task" fails to start. You can verify through the logs that the package is built and tested correctly.
win-64 had to be skipped because of some issues with boost. The same recipe works with boost from conda-forge so it's an issue with our boost for sure, but it will take some time to figure it out and win-64 isn't a priority.
s390x is not supported.
THIS PACKAGE WILL NOT BE UPLOADED TO defaults, so once reviewed we will just merge and upload to Snowflake's private channel.

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_936ai3ms95/clone/recipe/meta.yaml:36: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_936ai3ms95/clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_936ai3ms95/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_936ai3ms95/clone/recipe/meta.yaml:76: invalid_url: https://rdkit.org : Not reachable: 406
ERROR: /tmp/abs_936ai3ms95/clone/recipe/meta.yaml:84: invalid_url: https://www.rdkit.org/docs/index.html : Not reachable: 406
ERROR: /tmp/abs_936ai3ms95/clone/recipe/meta.yaml:85: missing_license_family: The recipe is missing the about/license_family key.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_cfo3sfgstp/clone/recipe/meta.yaml:34: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_cfo3sfgstp/clone/recipe/meta.yaml:35: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_cfo3sfgstp/clone/recipe/meta.yaml:37: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_cfo3sfgstp/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_cfo3sfgstp/clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_cfo3sfgstp/clone/recipe/meta.yaml:78: invalid_url: https://rdkit.org : Not reachable: 406
ERROR: /tmp/abs_cfo3sfgstp/clone/recipe/meta.yaml:87: invalid_url: https://www.rdkit.org/docs/index.html : Not reachable: 406
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_188do_ueo5/clone/recipe/meta.yaml:39: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_188do_ueo5/clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_188do_ueo5/clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_188do_ueo5/clone/recipe/meta.yaml:46: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_188do_ueo5/clone/recipe/meta.yaml:47: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_188do_ueo5/clone/recipe/meta.yaml:83: invalid_url: https://rdkit.org : Not reachable: 406
ERROR: /tmp/abs_188do_ueo5/clone/recipe/meta.yaml:92: invalid_url: https://www.rdkit.org/docs/index.html : Not reachable: 406
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_1b1yst53y2/clone/recipe/meta.yaml:37: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1b1yst53y2/clone/recipe/meta.yaml:38: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1b1yst53y2/clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1b1yst53y2/clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1b1yst53y2/clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1b1yst53y2/clone/recipe/meta.yaml:81: invalid_url: https://rdkit.org : Not reachable: 406
ERROR: /tmp/abs_1b1yst53y2/clone/recipe/meta.yaml:90: invalid_url: https://www.rdkit.org/docs/index.html : Not reachable: 406
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_6bbs3ldwx9/clone/recipe/meta.yaml:39: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_6bbs3ldwx9/clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_6bbs3ldwx9/clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_6bbs3ldwx9/clone/recipe/meta.yaml:46: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_6bbs3ldwx9/clone/recipe/meta.yaml:47: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_6bbs3ldwx9/clone/recipe/meta.yaml:83: invalid_url: https://rdkit.org : Not reachable: 406
ERROR: /tmp/abs_6bbs3ldwx9/clone/recipe/meta.yaml:92: invalid_url: https://www.rdkit.org/docs/index.html : Not reachable: 406
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_b917fnnqtv/clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_b917fnnqtv/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_b917fnnqtv/clone/recipe/meta.yaml:43: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_b917fnnqtv/clone/recipe/meta.yaml:47: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_b917fnnqtv/clone/recipe/meta.yaml:48: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_b917fnnqtv/clone/recipe/meta.yaml:84: invalid_url: https://rdkit.org : Not reachable: 406
ERROR: /tmp/abs_b917fnnqtv/clone/recipe/meta.yaml:93: invalid_url: https://www.rdkit.org/docs/index.html : Not reachable: 406
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_32gewg5dii/clone/recipe/meta.yaml:39: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_32gewg5dii/clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_32gewg5dii/clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_32gewg5dii/clone/recipe/meta.yaml:46: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_32gewg5dii/clone/recipe/meta.yaml:47: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_32gewg5dii/clone/recipe/meta.yaml:83: invalid_url: https://rdkit.org : Not reachable: 406
ERROR: /tmp/abs_32gewg5dii/clone/recipe/meta.yaml:92: invalid_url: https://www.rdkit.org/docs/index.html : Not reachable: 406
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_4c_tstaiux/clone/recipe/meta.yaml:39: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_4c_tstaiux/clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_4c_tstaiux/clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_4c_tstaiux/clone/recipe/meta.yaml:46: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_4c_tstaiux/clone/recipe/meta.yaml:47: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_4c_tstaiux/clone/recipe/meta.yaml:83: invalid_url: https://rdkit.org : Not reachable: 406
ERROR: /tmp/abs_4c_tstaiux/clone/recipe/meta.yaml:92: invalid_url: https://www.rdkit.org/docs/index.html : Not reachable: 406
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_bcihwh72ay/clone/recipe/meta.yaml:39: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_bcihwh72ay/clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_bcihwh72ay/clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_bcihwh72ay/clone/recipe/meta.yaml:46: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_bcihwh72ay/clone/recipe/meta.yaml:47: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_bcihwh72ay/clone/recipe/meta.yaml:83: invalid_url: https://rdkit.org : Not reachable: 406
ERROR: /tmp/abs_bcihwh72ay/clone/recipe/meta.yaml:92: invalid_url: https://www.rdkit.org/docs/index.html : Not reachable: 406
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_f8vsi8ar4a/clone/recipe/meta.yaml:37: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_f8vsi8ar4a/clone/recipe/meta.yaml:38: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_f8vsi8ar4a/clone/recipe/meta.yaml:39: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_f8vsi8ar4a/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_f8vsi8ar4a/clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_f8vsi8ar4a/clone/recipe/meta.yaml:46: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_f8vsi8ar4a/clone/recipe/meta.yaml:82: invalid_url: https://rdkit.org : Not reachable: 406
ERROR: /tmp/abs_f8vsi8ar4a/clone/recipe/meta.yaml:91: invalid_url: https://www.rdkit.org/docs/index.html : Not reachable: 406
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_5akme_d459/clone/recipe/meta.yaml:37: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_5akme_d459/clone/recipe/meta.yaml:38: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_5akme_d459/clone/recipe/meta.yaml:39: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_5akme_d459/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_5akme_d459/clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_5akme_d459/clone/recipe/meta.yaml:46: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_5akme_d459/clone/recipe/meta.yaml:82: invalid_url: https://rdkit.org : Not reachable: 406
ERROR: /tmp/abs_5akme_d459/clone/recipe/meta.yaml:91: invalid_url: https://www.rdkit.org/docs/index.html : Not reachable: 406
Errors were found


Simplify SVG paths on import

Design software sometimes adds a bunch of unnecessary points to the exported SVG. Since the initially added SVG points can never be deleted, it might be good to simplify SVGs on import and then let the user decide if they want to re-add those points back in later.

Fixed in v0.1.1.


doc2query reproduction test

Successfully reproduce doc2query experiments on MSMARCO and TREC-CAR.
OS:  Ubuntu 18.04.2 LTS
JAVA: openjdk version "11.0.4" 2019-07-1
Python: 3.6.7

Awesome. Can you indicate which commit point, as in here? https://github.com/castorini/anserini/blob/master/docs/regressions-robust04.md

Sorry for the miss. I have added the information of the commit that I run the reproduction test.

Great, thanks for your contribution!


[misc] Remove rebasing Chromium feature samples

Please also check sampleapp-tizen-tests, thanks.

@zqzhang  I have submitted another pr #2678 to remove sampleapp-tizen-tests chromium samples.


Add support *

What you think about support *
i.e. *example.com or *.example.com ?

Thanks your feedback!
It could be done, but just think is supporting a regexp match necessary(just a thought)?

Hi, code has been pushed to master and you can help test!

@Unknwon, thank for quick response, I'm going to test it at home

No problem


german translation review

tossed the autotranslate files and reviewed the existing

WIP for now, there is a regex to solve


Constant water sound and eagle screeching in space stations in Advanced Rocketry.

Mod Version:
<IP_ADDRESS> for 1.12.2
Forge Version:
1.12.2-<IP_ADDRESS>04
Link to crash log (if applicable):
Not applicable
Description:
I discovered this annoying glitch where you can hear a watery sound(somethin along the lines of a stream/river) and occasional eagles or hawks screeching, in space stations. This should not happen in the vacuum of space, and since it's a really minor issue, is there any chance at all for it to be addressed? As a side note, there is no water at all in my station.

Have you checked which biome(s) are registered for that station? My guess is that DS correctly plays the sounds for these biomes, the dimension should just not have them. You can review the current biome in the F3 screen, some other mods can display it as well (JourneyMap, IngameInfoXML and others).

It seems like the AR devs have made their own, the biome name is "Space", although space stations spawn at about 130 height in the world, which is where hawks and eagles would normally appear on Earth, I suppose. Although I still can't explain the river sound.

P.S.: I just checked dsurround.cfg and found no dimension blacklisting option. Maybe that would be a good addition?

I strongly agree!

DS has a fake biome called Space.  It is not something Minecraft is aware of.  Its something that DS uses to attach effects for Y values > world height + 32, or about Y >= 288 for Overworld.  It also has a fake biome called "Clouds" which starts at Y = skyheight / 2, or about Y = 128 for Overworld.
I haven't used the AR mod so I am not entirely sure what it is doing.  In the Revelation instance I am using the AR mod only registers a single biome called "Alien Forest" which has the biome attribute of PLAINS.  Needless to say that biome will have plains sound effects.  The log, though, has some errors related to biome registration and AR so the pack may not be fully sane.

That sounds very sweet. You might even add space-relevant sounds for mods like Advanced Rocketry and Galacticraft one day. Although realistically, those would chiefly be spacesuit breathing and maybe some computer-gizmo sounds suggesting a working space suit.

@Ulisse54 Can you do me a favor and post your planetsDef.xml file from the advRocketry config directory?

I'm sorry to say that I have no such file in my config directory, not in  .minecraft/config or .minecraft/config/advRocketry Although, by searching "planetDefs" in the whole .minecraft folder I have found that the file is created in each world, so here is the world I play in usually.
planetDefs.zip
I'm sorry I had to zip it, GitHub doesn't allow XML files to be uploaded.

I'm going to add the dimension blacklist option for now to bridge the gap.  I will replace at some point when I have a better system devised.

That sounds great! Thanks for your time :D

Pushed v<IP_ADDRESS> with a config option to blacklist dimensions for biome sound play.


Ration measures with 2 IP are not supported at the moment

Earlier there was an issue with measure observation calculation for ratio measures. We raised the ticket https://github.com/projecttacoma/cqm-execution/issues/246. Thanks to @dczulada, he fixed the issue(haven’t pulled it into Bonnie yet). There was also a discussion on that ticket about supporting ratio measures with multiple IPs. Since the original issue was addressed in that ticket, created this ticket to address the calculation of 2 IP ratio measure.
It looks like cqm-execution doesn't support ratio measures with more than 1 IP. This was raised by the measure developer community at multiple community meetings. This is a blocker to upcoming AU. Bonnie needs this for the contingency plan. cc @nicole-hunter

@adongare @nicole-hunter.  Have they drafted a Ratio measure with 2 IPPs?  If so, is it supported in CQM-Parsers?  If you can provide an example measure, I'm sure we can get this updated in cqm-execution. What timeframe are you looking at?

@adongare @nicole-hunter
Just did a quick look here.  I believe supporting a Ratio measure with distinct IPPs would also require updates to CQM-Models and CQM-Parsers as well.  As currently written, they assume a singular IPP/initialPopulationCriteria.
https://github.com/projecttacoma/cqm-models/blob/a7d4f58ed50a8bda465f372440e7b449ba0473c6/app/models/cqm/population_set.rb#L64
https://github.com/projecttacoma/cqm-parsers/blob/847019101f1a122f44e3cda0b7313d40cb71e6bb/lib/measure-loader/hqmf_measure_loader.rb#L124

@adongare Here are some thoughts.  Note that any changes to the measure model in cqm-models could have significant ramifications in Bonnie (and/or Cypress).  Here is one approach I've experimented with.  You can look at the commits to see possible changes that would be needed across cqm-models, cqm-parsers, bonnie and cqm-execution.

First, cqm-models will need to be updated to support multiple IPPs for Ratio Measures.  This approach creates a new arbitrarily named population IPP_1 which could be used in Ratio Measures

cqm-models will need to be updated to include a subject field for StatementReference.  This is how the hqmf indicates which IPP the NUMER or DENOM reference
CQM-Models
https://github.com/projecttacoma/cqm-models/commit/d7e29568c4f28a587d19a405ac3b33c04e113e91

cqm-parsers will need to be updated to extract this new information from the HQMF files
CQM-Parsers
https://github.com/projecttacoma/cqm-parsers/commit/a4b6d4c31dd317cada3805653c413709394dad0e

Bonnie will need to be updated to pass this new information in cqm-execution
Bonnie Updates
https://github.com/projectcypress/bonnie/commit/a00d5fce735879834df4df1d991ae944093638c9

cqm-execution can use this new measure information to support calculation with multiple IPPs
CQM-Execution
https://github.com/projecttacoma/cqm-execution/commit/cca2bb0f9b53440bcb1fac4960fcb6ed6a2005b1

@adongare @nicole-hunter
Any thoughts on the analysis above.  I believe any updates in the underlying Bonnie and Cypress data models (in cqm-models) should to go through some regression testing in both tools prior to inclusion in the library.  From what I remember, I believe Bonnie can be somewhat brittle when it comes to changing its database model.

Hi @dczulada, thank you for the thorough analysis of all the repos. the steps outlined look good to me. seems like a big change. I did not get a chance to go through this. was busy with some other assignments. I'll play with this lil bit. Also, I did not find 2 IP measures(clinically meaningful). I've asked our SMEs to look into it. I'll post it here as soon as I get one.

@adongare The reason why I asked about a specific measure is due to the significant amount of changes needed to get the functionality in Bonnie.  If measure developers do not have a measure with multiple IPPs in the development pipeline for this next Annual Update it would likely make sense to defer this functionality to MADiE.
However, if measure developers do have a measure with multiple IPPs in the development pipeline for this next Annual Update we should work together to get these changes into the shared libraries and Bonnie.

@dczulada I think you are right. We might be able to defer this to MADiE. We do not know if there is any 2 IP measure right now. We reached out to the community to solicit more info on this since it came from MDs. We will let you know if there is one.


Backmerge/release/july 2024 2024 07 29

:x: There is undocummented changes. Run chronus add to add a changeset or click here.
The following packages have changes but are not documented.

:x:@azure-tools/typespec-client-generator-core

Show changes

You can try these changes here

🛝 Playground
🌐 Website
📚 Next docs


Add Mapillary Vistas (Import only)

Summary

How to test

Checklist

[ ] I submit my changes into the develop branch
[ ] I have added description of my changes into CHANGELOG
[x] I have updated the documentation accordingly
[x] I have added tests to cover my changes
[ ] I have linked related issues

License

[ ] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[ ] I have updated the license header for each file (see an example below)

# Copyright (C) 2021 Intel Corporation
#
# SPDX-License-Identifier: MIT

Please update the changelog.


Small typo in readme

Change:
END_TIME = 24 hour format hour you would like to start the program, if timer is enabled. Defaults to 19, 7 PM
to:
END_TIME = 24 hour format hour you would like to end the program, if timer is enabled. Defaults to 19, 7 PM

You can submit pull requests by editing the readme yourself, creating a pull request, and the repo owner can update.
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request


Update docs for feat: initial twcs impl

A document change request is generated from
https://github.com/GreptimeTeam/greptimedb/pull/1851

duplicate with #1009


Unhandled Exception: MissingPluginException(No implementation found for method getAll on channel plugins.flutter.io/shared_preferences)

I'm solved with change code from mainactivity.kt or mainactivity.java.
import androidx.annotation.NonNull
import io.flutter.embedding.engine.FlutterEngine
import io.flutter.embedding.android.FlutterFragmentActivity
import io.flutter.plugins.GeneratedPluginRegistrant

class MainActivity: FlutterFragmentActivity() {
   override fun configureFlutterEngine(@NonNull flutterEngine:
     FlutterEngine) {
     GeneratedPluginRegistrant.registerWith(flutterEngine)
   }
}

after that, flutter clean and run
Originally posted by @iqbalabdurrazaq in https://github.com/flutter/flutter/issues/65334#issuecomment-747936118

solved

thanks for your answer. It worked for me. @iqbalabdurrazaq


consistent building color

at certain zoom, buildings change color :/  tm2 not working atm, so eventually.

fixed in https://github.com/skorasaurus/pascalpastel.tm2/commit/0281c408c10137963ac4f5c11607f808f6f4bb90


Frontend progress bar

PULL REQUEST
Summary
Implemented progress bar
Related Issue
Fixes # https://app.zenhub.com/workspaces/secret-6480bf2ee530095ab41ebbe9/issues/gh/cdcgov/phdi/818
Additional Information
Anything else the review team should know?

thanks for sending these screenshots over @nickbristow ! there a few changes that need to be made, happy to either pair on it or review again async:

are you using the basic header component from USWDS? the "DIBBs Pipeline Demo Site" isn't centered vertically within the header so I'm curious as to why that's happening
also for the header and footer, the margin between the left edge of the screen and the text should only be 32px. should also be 32px for the footer on the right edge of the screen
a lot of the text styling and spacing looks pretty off from the design - I'm wondering if you could borrow from the styling Kenneth used on his most recent ticket? instead of reinventing the wheel? if not, I'll write up all of the things to be fixed in a follow up comment just lmk
the width of the content on the page looks pretty large, it should only be 641px across for the alert and the progress bar, except the "Parsing relevant data fields" text will go slightly beyond that max
the steps in the pipeline aren't matching the design. it should be "Standardizing and cleaning" as one step, not 3. and then I don't see "enriching location data" for the geocoding step
some of the icons don't seem centered within the circles, not sure how tricky that is to fix though

@sarahtress

thanks for sending more screenshots, it's still looking like the first heading text and spacing won't be aligned with what Kenneth had for the first two pages, which will be a jarring transition for users
the two things that stand out visually is that there should be 48 px of spacing between the page navigation header and the "Processing your eCR" text, and then it looks like the "Processing your eCR text" is not public sans, not sure what's happening there.


Questions regarding the behavior of CompositionMaskBrush

I am on build 14901 and SDK 14393, Visual Studio 2015 Update 3.
I have a couple of questions regarding the behavior of CompositionMaskBrush in certain scenarios.
Scenario 1
I am creating a CompositionDrawingSurface of size (400, 400) and drawing a CanvasGeometry on it. I am then creating a CompositionSurfaceBrush from the surface. This surface brush is used to provide the Mask for the CompositionMaskBrush.
Now when I apply the mask brush to a visual of size (200, 200) I see that the canvas geometry is resized to fit the visual.
Is there a way to prevent the brush from resizing its surface to fit the target visual? Also it would be great if there was an option to specify the alignment (horizontal and vertical) of the unresized mask within the visual.

Here is the code
private void OnLoaded(object sender, RoutedEventArgs e)
{
    var compositor = ElementCompositionPreview.GetElementVisual(this).Compositor;
    var canvasDevice = CanvasDevice.GetSharedDevice();
    var graphicsDevice = CanvasComposition.CreateCompositionGraphicsDevice(compositor,
                                                                         canvasDevice);

    var surfaceSize = new Size(400, 400);
    var drawingSurface = graphicsDevice.CreateDrawingSurface(surfaceSize,
                                              DirectXPixelFormat.B8G8R8A8UIntNormalized,
                                              DirectXAlphaMode.Premultiplied);

    var width = (float)surfaceSize.Width;
    var height = (float) surfaceSize.Height;

    // Create the combined geometry
    var ellipse1 = CanvasGeometry.CreateEllipse(canvasDevice, width / 2,
                                          height / 2, 0.45f * width, 0.225f * height);
    var ellipse2 = CanvasGeometry.CreateEllipse(canvasDevice, width / 2, height / 2,
                                          0.225f * width, 0.45f * height);
    var combinedGeometry = ellipse1.CombineWith(ellipse2, Matrix3x2.Identity,
                                                 CanvasGeometryCombine.Union);

    using (var session = CanvasComposition.CreateDrawingSession(drawingSurface))
    {
        session.FillGeometry(combinedGeometry, Colors.Black);
    }

    var surfaceBrush = compositor.CreateSurfaceBrush(drawingSurface);
    var maskBrush = compositor.CreateMaskBrush();
    maskBrush.Mask = surfaceBrush;
    maskBrush.Source = compositor.CreateColorBrush(Colors.Red);

    var visual1 = compositor.CreateSpriteVisual();
    visual1.Size = surfaceSize.ToVector2() * 0.5f;
    visual1.Offset = new Vector3(100, 100, 0);
    visual1.Brush = maskBrush;

    ElementCompositionPreview.SetElementChildVisual(this, visual1);
}

Scenario 2
When I apply a mask to a SpriteVisual, the mask is not applied to its children in its visual tree. Is there a way to enforce it (rather than traverse through the visual tree and apply it manually)?

I found the solution to Scenario 2 myself. The simple answer is: Use a LayerVisual.
Here is the sample code (I have used CompositionProToolkit for generating the mask)
private void InitComposition()
{
    Compositor compositor = ElementCompositionPreview.GetElementVisual(this).Compositor;
    ICompositionGenerator generator = CompositionGeneratorFactory.GetCompositionGenerator(compositor);

    //// Create the combined geometry
    var ellipse1 = CanvasGeometry.CreateEllipse(canvasDevice, width / 2, height / 2, 0.45f * width, 0.225f * height);
    var ellipse2 = CanvasGeometry.CreateEllipse(canvasDevice, width / 2, height / 2, 0.225f * width, 0.45f * height);
    var combinedGeometry = ellipse1.CombineWith(ellipse2, Matrix3x2.Identity, CanvasGeometryCombine.Union);

    var visualLayer = compositor.CreateLayerVisual();
    visualLayer.Size = surfaceSize.ToVector2();
    visualLayer.Offset = new Vector3(400, 100, 0);

    var v1 = compositor.CreateSpriteVisual();
    v1.Size = new Vector2(300, 300);
    v1.Brush = compositor.CreateColorBrush(Colors.Red);
    v1.Offset = new Vector3(30, 30, 0);
    visualLayer.Children.InsertAtTop(v1);

    var v2 = compositor.CreateSpriteVisual();
    v2.Size = new Vector2(300, 300);
    v2.Brush = compositor.CreateColorBrush(Colors.YellowGreen);
    v2.Offset = new Vector3(130, 130, 0);
    visualLayer.Children.InsertAtTop(v2);

    // Create the effect to create the opacity mask
    var layerEffect = new CompositeEffect
    {
        // CanvasComposite.DestinationIn - Intersection of source and mask.
        // Equation: O = MA * S
        // where O - Output pixel, MA - Mask Alpha, S - Source pixel.
        Mode = CanvasComposite.DestinationIn,
        Sources =
                {
                    new CompositionEffectSourceParameter("source"),
                    new CompositionEffectSourceParameter("mask")
                }
    };

    var layerEffectFactory = compositor.CreateEffectFactory(layerEffect);
    var layerEffectBrush = layerEffectFactory.CreateBrush();

    var layerMask = generator.CreateMask(surfaceSize, combinedGeometry);
    layerEffectBrush.SetSourceParameter("mask", compositor.CreateSurfaceBrush(layerMask.Surface));

    visualLayer.Effect = layerEffectBrush;

    ElementCompositionPreview.SetElementChildVisual(this, visualLayer);
}

Thank you for the images for context. Since you already figured out Scenario 2, all you need is to add in one (or two) lines of code for Scenario 1!
You need to adjust the Stretch and Vertical / Horizontal  AlignmentRatio properties on your CompositionSurfaceBrush! The default behavior for Stretch is Uniform, thence the result you're seeing. It seems like what you're looking for is CompositionStretch.None.
Also, in the Anniversary Update, we added new properties on SurfaceBrush to mirror all the transformations on Visual (anchorPoint, centerPoint, offset, rotationAngle, scale, transformMatrix), so, should you wish to do something more custom depending on more complicated scenarios (something not addressed by simply using Stretch and Alignment), you can achieve those too.
Hope this helps.

@sohchatt Thanks a lot. Those are the properties I was looking for.
I must have missed those properties during my initial investigation.


Github

Please help how can got code

Hi @rafiq34!
Could you elaborate what your issue is? What code do you mean?
I recommend you to visit our chat on www.livechatinc.com and elaborate your question to get help immediately. Our Support Heroes would be happy to help you :-) Our operators are available 24/7/365.
You can always shoot us an email too<EMAIL_ADDRESS>

Closed due to inactivity.


Riak claim property-based tests are misleading

Associated with this issue is a long read:
https://github.com/martinsumner/riak_core/blob/mas-claimv2issues/docs/ring_claim.md
We have done some analysis of claim, because of a history of noting oddities about the outcomes of certain claim plans.  The headline issue we discovered was that the property-based tests make an assumption about how cluster plans are formed that does not reflect the real world, and also don't test some properties that could lead to issue sin the real world.  This means that assumptions which appear to be demonstrated to be true in the property-based tests, may commonly not be true in the real world: so bad claim behaviour is leaking into production systems.
The intention (hopefully over the next two weeks) is to both address the issues with the property-based tests, and then propose & test fixes to claim v2 which resolve these issues.
Further details on the proposed changes are in the long read.  The reasoning for fixing v2 and not v3 is also explained.

The document you link is excellent.
A suggestion is that you add (perhaps toward the beginning) that in the riak system, a vnode is the unit of concurrency and "ring size" is essentially mapping units of concurrency to a slice of the keyspace riak manages.

Thanks for the feedback Mark.  I've added a terminology section to the top of the overview.  Does that read better for you?

Somewhere there is commentary about claim, rack awareness, and current vnode size.  This was to lead to balancing algorithms where an algorithm (I put forth a genetic algorithm and Reid proposed a standard Dijkstra algorithm ... no prototypes were created of either) would match the restrictions of rack awareness and facilitate minimized handoff of vnodes to balance against existing nodes or change in number of nodes ... I will look around.

@martinsumner I think the glossary is great. Thanks!

Going to close this, as we shipped improvements. I do think that the riak claim statem we started on needs finishing, when there is time (I'll open a new issue for that, specifically that leave needs modelling)


Invalid logger line

https://github.com/socketry/async-dns/blob/3cb580150619da2a32d4939368217abf6de9fb82/lib/async/dns/handler.rb#L62
                |   ArgumentError: wrong number of arguments (given 2, expected 0..1)
                |   → /usr/lib/ruby/2.7.0/logger.rb:545 in `error'
                |     /var/lib/gems/2.7.0/gems/async-dns-1.2.5/lib/async/dns/handler.rb:62 in `rescue in process_query'
                |     /var/lib/gems/2.7.0/gems/async-dns-1.2.5/lib/async/dns/handler.rb:57 in `process_query'
                |     /var/lib/gems/2.7.0/gems/async-dns-1.2.5/lib/async/dns/handler.rb:82 in `respond'
                |     /var/lib/gems/2.7.0/gems/async-dns-1.2.5/lib/async/dns/handler.rb:76 in `block in run'
                |     /var/lib/gems/2.7.0/gems/async-1.28.9/lib/async/task.rb:265 in `block in make_fiber'

  RubyDNS.run_server(INTERFACES) do
    self.logger = Logger.new(STDOUT)

Looks like there is an incompatibility between Console::Logger and Ruby's standard Logger. We can fix this by writing it like this:
@logger.error(self) {error}


Style guide is incorrect regarding to the page objects

As per my question, the style guide needs to be updated. The answer of @alecxe solves the problem.

@andresdominguez FYI.

I do not think there is anything wrong with the style guide as it is. In the style guide we recommend declaring element finders and functions. An ElementFinder will not execute until you call a function on it, like getText(), isPresent(), etc.
When you mention "initialize some fields", what are you actually doing? Please update your question with the code that is causing a problem.

@andresdominguez I suspect the OP is trying to do something with the found elements right inside the constructor. That would explain why my advice to move the page object initializations to beforeEach() helped. Let's wait for the code. Thanks for looking into this.

@sjelin can you close this one as "Intended behavior"?

Here's the code, as requested:
var LoginPage = function() {
  this.form = browser.driver.findElement(by.name('ldap_login_form'));
  this.usernameInput = browser.driver.findElement(by.id('username'));
  this.passwordInput = browser.driver.findElement(by.id('password'));

  this.get = function() {
    browser.driver.get('http://xxxxxxx');
  };

  this.login = function(username, password) {
    this.usernameInput.sendKeys(username);
    this.passwordInput.sendKeys(password);
    this.form.submit();
  };
};

module.exports = LoginPage;

var LoginPage = require('./page-objects/consulent/LoginPage.js');

describe('SMP+', function() {

  var loginPage = new LoginPage();

  it('Login', function() {
    console.log('------------------->' + loginPage)
    loginPage.get();
    loginPage.login('vdabcor1', 'ldv');
  });
});

If you are using a non-angular app I would recommend you to do:
browser.ignoreSynchronization = true;

And then use standard element finders:
var LoginPage = function() {
  this.form = element(by.name('ldap_login_form'));
  this.usernameInput = $('#username');
  this.passwordInput = $('#password');

  this.get = function() {
    browser.get('http://xxxxxxx');
  };

  this.login = function(username, password) {
    this.usernameInput.sendKeys(username);
    this.passwordInput.sendKeys(password);
    this.form.submit();
  };
};

module.exports = LoginPage;

I bypassed it by just putting the whole code in an onPrepare function in the conf-file.
No need for pageobjects for the non-angular pages then.


Scale up while hovering on social buttons

Description
Add a little hover effect on the social buttons of the Team member card on the About Page. like scale up the button little add some dark tone on the color while hovering.
Screenshots

Additional information
No response

hii , can you assign me this task , i would love to work on it.

@ankitkumar0622 Assigning you.

Can i work on this issue .. If available ..

after @ankitkumar0622 I can assign you @rmgb05

@ankitkumar0622 What's the progress?

I have almost finished , it will be done by tomorrow noon , sorry for the delay . @Debajyoti14

@ankitkumar0622 no worries 😇

@ankitkumar0622 any updates?


1

1

have you opened an issue for this code change? You need to specify the purpose of your code changes.


Keep Back Slot gamerule

Hi there!
Firstly, thank you for creating this amazing and adorable mod! I understand that my feature request may have a very low priority, but if it were possible to have an option that could be turned on, perhaps in the config, where the backpack and its contents do not drop when this option is enabled, it would be greatly appreciated. Maybe in a future update? :3

Sure! Just to be clear, when a player dies you want to keep back slot's item on the player but on death still drop the player's inventory?

I was thinking that when the player dies, they usually lose their items except for the backpack and the items within it, acting like a mini safe inventory to make death less harsh!

I've got you, so when a player respawns their inventory's empty except for the backpack they were wearing. This should be easy since in much earlier versions this was actually an issue I was having lol.
I'll try to get it out in 20.1-0.22-v2. Sorry it didn't make this update, buttons are surprisingly really complicated

Added in 20.1-0.23-v2! You can enable it by using the command /beansmod gamerule keepBackSlot true


Create Spork::VERSION

Hi Tim,
Here's a solution for Spork to know its own version number. Could you pull this?
This follows the version example from Carl Lerche and Yehuda Katz in the bundler gem:

New file /lib/spork/version.rb that defines Spork::VERSION

Update to spork.gemspec to require the version.rb for Spork::VERSION

Note that I bumped the version to rc10 to show how it works-- you may want to alter this. The gem builds fine on my setup.
My contact info is joelparkerhenderson on Gmail and Google Talk if you'd like to ask about it.
Thanks,
Joel

@SixArm is there a lib/spork/version.rb missing from the pull request?

Yes - pushing it now. Thanks for the heads up.

@Tim be sure to update the version # for the current spork.


lines_cop: Add condition to prevent false positives

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[] Have you written new tests for your changes? Here's an example.
[x] Have you successfully run brew tests with your changes locally?

Fixes this bug
https://github.com/Homebrew/homebrew-core/pull/18736
https://github.com/Homebrew/homebrew-core/pull/18736#issuecomment-346739752
This was the original audit rule.
if line =~ /(Dir\[("[^\*{},]+")\])/
      problem "#{Regexp.last_match(1)} is unnecessary; just use #{Regexp.last_match(2)}"
end

Issue:  I was just running the check on first argument without checking number of arguments but original rule I think doesn't match multiple arguments

Thanks again @GauthamGoli!


fix EventLoopFuture.and's serious threading issues [alternative]

alternative to #175
Motivation:
EventLoopFuture.and had serious threading issues if the EventLoops
weren't the same.
Modifications:
Fixed the threading issues and tested them properly.
Result:
Hopefully and and andAll now don't crash if you use them across
EventLoops.

thanks for pushing me to do something @Lukasa , thought the alternatives would be too risky (in perf/bugs) but wasn't quite right ;)


knack conversion for advisor module

View a preview at https://prompt.ws/r/Azure/azure-cli/5083
This is an experimental preview for @microsoft.com users.
(It may take a minute or two for your instance to be ready)
Email feedback to 'azfeedback' with subject 'Prompt Feedback'.


Generate and upload coverage report for unit tests

Description
This change:

Adds unit test for GetCommitSHA method
Adds the first coverage report for unit tests named coverage.txt
Upload coverage.txt to CodeCov

This PR fixes #3134
Notes for Reviewers
Not merge. This is WIP.
Signed commits

[X] Yes, I signed my commits.

After merging to master, we'll see something like this:


Revert YugaByteFixture back to yugabyte:lastest image after next release

I'm having trouble when creating indexes for the identity-service user database.  Some indexes are created OK but others appear to fail with a backfill failed error.  The thing is that the tables were just created and are completely empty and supposedly, online back filling is disabled anyway so we shouldn't see this.  The interesting thing is that the index was created even though the backfill operation failed.  YugaByte has an open issue:
https://github.com/yugabyte/yugabyte-db/issues/6494
I've temporarily modified our YugaByteFixture test fixture to use the yugabytedb/yugabyte:<IP_ADDRESS>-b2 Docker image rather than yugabytedb/yugabyte:latest.  The newer image doesn't have this problem.
We need to revert back to yugabytedb/yugabyte:latest after it's updated to a version that works.

It looks like yugabyte/yugabyte-db#6494 has been fixed since 2.4.0, although they haven't closed the issue yet.
I've updated out fixture to use latest and our tests are passing, so I'm going to close this,


CSharpMath.Forms doesn't work with Xamarin Forms

I have integrated CSharpMath.Forms in a Xamarin Forms project and in the view it shows an empty space. It does not show the mathematical formula. Am I doing something wrong?

Code? Screenshot?

This is the code:
<Label
    Text="Mis Actividades"
    FontSize="Title"
    FontAttributes="Bold"
    Padding="30,20,30,10"
    TextColor="#666666"/>

<math:MathView
    BackgroundColor="red"
    TextColor="White"
    x:Name="View"
    HorizontalOptions="FillAndExpand"
    VerticalOptions="FillAndExpand">
    \frac\sqrt23
</math:MathView>

<math:TextView
    BackgroundColor="LightBlue"
    TextColor="Black"
    LaTeX="Text text text text text \( \frac{\sqrt a}{b} \) text text text text text"/>

and this is the result (screen): https://drive.google.com/file/d/15Su2xm5Rd990k-0Cs5fZ3kNxGsdIEEPd/view?usp=sharing

I tried with other versions and it worked for me with version 0.3.0.
I have noticed that in this version, the nugget asks to accept other terms that it does not ask for in the new versions. It is possibly the reason, it asks to accept the following:
System.Drawing.Primitives
System.Runtime.Extensions
I hope my comment will help solve the problem soon.

Try to add SkiaSharp as a nugget package to your project and see if that solves the issue


Add dark preview option to the preview in workspace

Deploy preview for pf-next ready!
Built with commit bf592849e9b35993bffe04c540869d4faf662cf8
https://deploy-preview-197--pf-next.netlify.com


Update core

Update core to https://github.com/temporalio/sdk-core/commit/8691fed95ffa1ea220ccb29b67acead76c116336

May have to upgrade tonic and tonic build (probably just a cargo update to update all deps in the lock would do it, probably don't need toml change)

I agree. I think this PR should be the first PR post-release, rather than the last PR pre-release.

:+1: It would have been nice to get https://github.com/temporalio/sdk-core/issues/818 and https://github.com/temporalio/sdk-core/pull/815 and some others in this release, but I understand that reviewing this core change may take longer than we're wanting for some pure Python changes pending release.

My intention was that this upgrade should also include the changes to avoid applying jobs in different sets and thus match the behavior mentioned in https://github.com/temporalio/sdk-python/issues/606
Having all the SDKs work the same way in that regard will be a long term win I think, and is in general just a bit simpler to think about.

@dandavison - can you do a cargo update to help solve #671?

(added #671 as being closed by this)


fix: synthesize shape in sub-environment scope

Hi, I resolved generic names leaking. I'm not sure if I'm right...
#196

wrap shape-synthesizes operation with new inner lexical scope
add an edge test case

Awesome! I think I will be around to merge this later

Sorry dealing with college stuff and don't want to rush a release. Will be in next week!


Adds over2, under2, over2F and under2F

Could you please give some examples of where these would be useful in the comments?

Looks good to me 👍. Any more comments @paf31?

👍 Looks great, thanks @mlang!


Sync watched status with remote server

Related to #19, this is a placeholder for when the feature is complete.

Codecov Report

Merging #21 into master will decrease coverage by 16.66%.
The diff coverage is 21.21%.

@@             Coverage Diff             @@
##           master      #21       +/-   ##
===========================================
- Coverage   57.14%   40.47%   -16.67%
===========================================
  Files           1        1
  Lines          56       84       +28
===========================================
+ Hits           32       34        +2
- Misses         21       47       +26
  Partials        3        3

Impacted Files
Coverage Δ

plex/myplex.go
40.47% <21.21%> (-16.67%)
:arrow_down:

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 cbe8b18...e708510. Read the comment docs.

Codecov Report

Merging #21 into master will decrease coverage by 18.5%.
The diff coverage is 18.91%.

@@             Coverage Diff             @@
##           master      #21       +/-   ##
===========================================
- Coverage   57.14%   38.63%   -18.51%
===========================================
  Files           1        1
  Lines          56       88       +32
===========================================
+ Hits           32       34        +2
- Misses         21       51       +30
  Partials        3        3

Impacted Files
Coverage Δ

plex/myplex.go
38.63% <18.91%> (-18.51%)
:arrow_down:

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 cbe8b18...e708510. Read the comment docs.

Codecov Report

Merging #21 into master will decrease coverage by 18.5%.
The diff coverage is 18.91%.

@@             Coverage Diff             @@
##           master      #21       +/-   ##
===========================================
- Coverage   57.14%   38.63%   -18.51%
===========================================
  Files           1        1
  Lines          56       88       +32
===========================================
+ Hits           32       34        +2
- Misses         21       51       +30
  Partials        3        3

Impacted Files
Coverage Δ

plex/myplex.go
38.63% <18.91%> (-18.51%)
:arrow_down:

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 cbe8b18...04b8eef. Read the comment docs.

Codecov Report

Merging #21 into master will decrease coverage by 18.5%.
The diff coverage is 18.91%.

@@             Coverage Diff             @@
##           master      #21       +/-   ##
===========================================
- Coverage   57.14%   38.63%   -18.51%
===========================================
  Files           1        1
  Lines          56       88       +32
===========================================
+ Hits           32       34        +2
- Misses         21       51       +30
  Partials        3        3

Impacted Files
Coverage Δ

plex/myplex.go
38.63% <18.91%> (-18.51%)
:arrow_down:

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 cbe8b18...04b8eef. Read the comment docs.


pip install beeware failed on Ubuntu 16.04

I'm trying to install beeware on my virtual environment venv - Linux Ubuntu 16.04 but it failed. It worked like a charm on MacOS though. Below are the steps I followed
python3 -m venv venv
. venv/bin/activate
pip install beeware
During the installation, I get this error in my terminal
ImportError: /home/alejeune/Development/beeware/pycon/venv/lib/python3.6/site-packages/cairo/_cairo.cpython-36m-x86_64-linux-gnu.so: undefined symbol: cairo_tee_surface_index
See below the command highlited in my terminal
Command "/home/alejeune/Development/beeware/pycon/venv/bin/python3 -u -c "import setuptools, tokenize;__file__='/tmp/pip-install-yqr0u95l/pygobject/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-record-3kdlzyar/install-record.txt --single-version-externally-managed --compile --install-headers /home/alejeune/Development/beeware/pycon/venv/include/site/python3.6/pygobject" failed with error code 1 in /tmp/pip-install-yqr0u95l/pygobject/
I'm new with Cairo but it looks like they migrated to pyCairo. I've also seen this issue with pygobject.
https://github.com/pygobject/pycairo/issues/105
Can you please suggest how to address this issue?

I can't install either because cairo fails to install. Skipping cairo makes possible to create the project tree using beeware, but the app fails to launch.

I had the same issue. I went to pycairo docs https://pycairo.readthedocs.io/en/latest/getting_started.html In the documentation the show the following dependencies for ubuntu.
sudo apt install libcairo2-dev pkg-config python3-dev.
After installing them I try to install beeware with pip.
pip install beeware
It show me another error where it sugested to install
sudo apt install libgirepository1.0-dev
After installing that the installation of beeware didn't show any more errors

I had similar issues. One with headers (libraries) another one related to my python being Anaconda distro. I managed to solve both of them in a following way:

Headers and dependencies
I was unable to install pycairo because I couldn't install cairo headers with apt-get. Problem was that cairo headers were dependant on headers that were dependant on zlib1g older than the one I had installed on my system. So I had to downgrade zlib1g and following line made the trick:
sudo apt-get install zlib1g-dev=1:1.2.8.dfsg-2ubuntu4
By adding = after package name I specified the version I want to reinstall and it worked. Following this one I normally installed cairo headers by running:
sudo apt-get install libcairo2-dev

Issue related to Anaconda
was that I couldn't use "normal" virtual environments without issues. So idea was to make conda virtualenv instead with this:
conda create --name BeeWareDev python=[version here] --channel conda-forge
Where [version here] is the version of Python you want to run your BeeWare on. 3.6.8 in my case.
Next step is to make sure that you are running your BeeWare within newly forged dev environment. which is done by running following:
conda activate dev (if it doesn't work try conda init bash -> restart the Terminal -> if you see (base)> then it's all good and try to rerun conda activate dev)

Next thing is to install all of the needed packages within this environment as stated in BeeWare Getting Started Tutorial and you are ready to go.

This appears to be a problem with having the required dependencies in place; these have now been added to the Beeware tutorial.


fix: contribution operator meets nan value

SUMMARY

fix: when NaN value in contribution operator can't calculate.
add unit test to guarantee nan value in contribution.

closes: https://github.com/apache/superset/issues/18774
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

After

Before

TESTING INSTRUCTIONS

Select birth_name as datasource
Select Line Chart on explore page. notice that, use echart version of Line Chart
Drag ds in x-axis
Select sum(num_boys) in metrics
Drag name in group by
Select total in contribution mode
You can look at a line chart as before screenshort.

ADDITIONAL INFORMATION

[x] Has associated issue: https://github.com/apache/superset/issues/18774
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

LGTM with a non-blocking comment to think about (as this PR fixes a clear bug I consider my comment mostly a nit). Also, an unrelated observation: I wonder if we should rename "Total" to something that describes more clearly that it's actually the "row" or "x-axis" that we're calculating the contribution for, not the "total", which I feel would be calculated in relation to the sum of the matrix.

nice catch! done!