Ability to reset skip version status.

I wanted to use combination of Harpy and our own server controlled way of forcing user to update the app, and I needed to reset the skipped version status for it. There are a lot of other ways to go by this, like exposing alert method or writing our own method but I thought it would be a good addition to API.

We have an endpoint that we call to see if we need to force user to update the app. However I still wanted to show user when a new version is out, Harpy helps there. However if user already set to skip the version and later on we want to force the user to update to that version then I had to show custom alert and not use harpy. So, that why I had to reset the skip version status, so that I can use the Harpy code without having to repeat the code that is already written there.
So I first check if need to force user then I set the alert type to force and reset skip version status and call checkVersion and it works as expected.

I like the idea of adding a way for Harpy to coordinate with an external API on forcing an update. In one project I did this by exposing a “minimum supported version” endpoint and checking that response before initializing Harpy. I also had to reset this for the reason you mentioned. I wonder if there’s a more intuitive interface we could use. Otherwise this seems like a a potentially helpful addition

Probably parse custom api response to get minimum version to force and pass it to Harpy, which can then automatically check once more if user skipped and if the version is greater than the current version.

Got it - I will follow up on Friday. Would you mind making the same changes on the Siren repository?
Sent with GitHawk

I will check check it out later today

I have update the interface, removed the reset method with a new parameter (same like I did in Siren), I will create a new pull request and close this one.


Citrix Daas Machine Catalog Allocation type "Static" is not working with MultiSession VMs.

Hello,
I got an error below when i created MC with allocation type "Static" with MultiSession VMs.
"provider["registry.terraform.io/citrix/citrix"]" produced an unexpected new value: .allocation_type: was
│ cty.StringVal("Static"), but now cty.StringVal("Random").
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

Hi @venugopal-chinnasamy ,
Thank you for raising this issue. Static allocation type is not supported when using MultiSession session support. We will take this as a bug and enforce validation on the schema.
Thank you.


Model Comparison crushes, when source or target model contains Roles named other language than English

It shows an error " index and length must refer to a location within the string. parameter name length"
TabularProject4.zip

Hi, thanks for the feedback and sorry for the delayed response. I just tried it on the latest version and I seem unable to repro. Are you still getting this issue?

Hm! Latest version... it seems to be working fine now
Thanks! ))

Great!


Changes for publisher display name and 3P extension platform fees

Docs Build status updates of commit 7d8e187:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/extensions-chromium/publish/create-dev-account.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/manage-settings.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/publish-extension.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 80eb9ae:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/extensions-chromium/publish/create-dev-account.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/manage-settings.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/publish-extension.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit b9f4541:
:warning: Validation status: warnings

File
Status
Preview URL
Details

microsoft-edge/extensions-chromium/publish/publish-extension.md
:warning:Warning
View
Details

microsoft-edge/extensions-chromium/publish/create-dev-account.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/manage-settings.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/publish-extension.md

Line 155, Column 202: [Warning-file-not-found] Invalid file link: '../developer-policies.md'.
Line 157, Column 2: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/microsoft-edge/extensions-chromium/store-policies/developer-policies#181-paid-features' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 157, Column 2: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/en-us/microsoft-edge/extensions-chromium/store-policies/developer-policies#181-paid-features' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 8470cfe:
:warning: Validation status: warnings

File
Status
Preview URL
Details

microsoft-edge/extensions-chromium/publish/publish-extension.md
:warning:Warning
View
Details

microsoft-edge/extensions-chromium/publish/create-dev-account.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/manage-settings.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/publish-extension.md

Line 155, Column 202: [Warning-file-not-found] Invalid file link: '../store-policies/developer-policies'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 108e0c4:
:warning: Validation status: warnings

File
Status
Preview URL
Details

microsoft-edge/extensions-chromium/publish/publish-extension.md
:warning:Warning
View
Details

microsoft-edge/extensions-chromium/publish/create-dev-account.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/manage-settings.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/publish-extension.md

Line 155, Column 198: [Warning-file-not-found] Invalid file link: '../store-policies/developer-policies'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Contract loading

What was wrong?
How was it fixed?
To-Do

[ ] OPTIONAL: Update Spec if applicable

[ ] Add entry to the release notes (may forgo for trivial changes)

[ ] Clean up commit history

Codecov Report

Merging #204 (e2cfe6f) into master (e108a74) will decrease coverage by 0.24%.
The diff coverage is 15.38%.

@@            Coverage Diff             @@
##           master     #204      +/-   ##
==========================================
- Coverage   77.50%   77.26%   -0.25%
==========================================
  Files          47       47
  Lines        3308     3321      +13
==========================================
+ Hits         2564     2566       +2
- Misses        744      755      +11

Impacted Files
Coverage Δ

semantics/src/lib.rs
76.10% <0.00%> (-0.68%)
:arrow_down:

semantics/src/namespace/operations.rs
87.50% <0.00%> (-2.83%)
:arrow_down:

semantics/src/namespace/types.rs
51.94% <0.00%> (-0.46%)
:arrow_down:

semantics/src/traversal/contracts.rs
100.00% <ø> (ø)

semantics/src/traversal/expressions.rs
67.82% <0.00%> (-2.13%)
:arrow_down:

semantics/src/namespace/scopes.rs
94.18% <100.00%> (+0.06%)
:arrow_up:

Continue to review full report at Codecov.

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

Codecov Report

Merging #204 (e2cfe6f) into master (e108a74) will decrease coverage by 0.24%.
The diff coverage is 15.38%.

@@            Coverage Diff             @@
##           master     #204      +/-   ##
==========================================
- Coverage   77.50%   77.26%   -0.25%
==========================================
  Files          47       47
  Lines        3308     3321      +13
==========================================
+ Hits         2564     2566       +2
- Misses        744      755      +11

Impacted Files
Coverage Δ

semantics/src/lib.rs
76.10% <0.00%> (-0.68%)
:arrow_down:

semantics/src/namespace/operations.rs
87.50% <0.00%> (-2.83%)
:arrow_down:

semantics/src/namespace/types.rs
51.94% <0.00%> (-0.46%)
:arrow_down:

semantics/src/traversal/contracts.rs
100.00% <ø> (ø)

semantics/src/traversal/expressions.rs
67.82% <0.00%> (-2.13%)
:arrow_down:

semantics/src/namespace/scopes.rs
94.18% <100.00%> (+0.06%)
:arrow_up:

Continue to review full report at Codecov.

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


same residue with different itp

Dear reader,
I am interested in the comparison of chain length polymers. To build a blend of the same polymer with different chain lengths, how should I change the residue name correctly or use gmx solvate?
Many thanks
Matthew

Hi Matthew,
If I understand correctly you want to have different chain lengths but the same residues? Like PS-10, PS-100 etc. Then you can simply generate the itp files for multiple chains using polyply gen_itp. For example, for Martini PS:
polyply gen_itp -lib martini2_polymers -seq PS:#number_of_monomers -o name.itp -name PS100

Subsequently you simply need to write a top file with the desired composition and use polyply gen_coords. Also check out this tutorial in the wiki section https://github.com/marrink-lab/polyply_1.0/wiki/Tutorial:-martini-polymer-melts.
Let me know if you have any more questions.

Yes brilliant,
I hadn't thought that -name PS100... would correctly adjust the residue name.
Many thanks
Matthew

@mw00847 is issue resolved? In case you've no other questions I'd close it.

Yes
used polyply to generate two .itp files shortpolymer.itp, longpolymer.itp
but needed to change the residue name separately so Gromacs could differentiate the two otherwise both are named PS etc, as below
before
[ moleculetype ]
PEO 1
[ atoms ]
1 EO 1 PEO COC 1 0.0 45.0
2 EO 2 PEO COC 2 0.0 45.0
after
[ moleculetype ]
PEOlong 1
[ atoms ]
1 EO   1 PEOL COC   1 0.0 45.0
2 EO   2 PEOL COC   2 0.0 45.0
3 EO   3 PEOL COC   3 0.0 45.0
4 EO   4 PEOL COC   4 0.0 45.0
[ moleculetype ]
PEOshort 1
[ atoms ]
1 EO 1 PEO COC 1 0.0 45.0
2 EO 2 PEO COC 2 0.0 45.0


Make the list yearwise

The page is getting longer day to day.
How about listing the conferences by year
For ex: We mention the year in the readme and a link which redirects to the conferences of that year.

@shivakrishna9 Thanks for the suggestion! Yes, I had plans to keep only the current year on the README and move everything else to a separate directory.
Example:

2017 conferences stay on the README as-is.
two more directories are created for 2016 and 2018 and the conferences are moved to a markdown file in those directories (respectively).

Would you like to work on this?

Yes. Sure. I will work on this. :) @nikhita

@shivakrishna9 do you want to continue to work on this?

Yup! Unable to do it as I am away from GitHub since a month.

Yup! Unable to do it as I am away from GitHub since a month.

No problem, feel free to send a PR when ready. :)

What next is you need help with ?

@techsethi If you'd like to contribute, see my comment here: https://github.com/nikhita/tech-conferences-india/issues/28#issuecomment-320519797. The plan is to move the conferences according to the year.
Let me know if you have any further questions!

@nikhita Done, please check & merge. Let me know, if there are any issues.
https://github.com/nikhita/tech-conferences-india/pull/39


build!: upgrade to pydantic v2

closes #132

I'm also getting some failed tests. I thought aws dev ddb was being used, so that's the one I used to run tests.
FAILED tests/test_fusor.py::test_add_gene_descriptor - AssertionError: alt labels
FAILED tests/test_fusor.py::test_gene_element - AssertionError: len of extensions
FAILED tests/test_fusor.py::test_functional_domain - AssertionError: len of extensions
FAILED tests/test_fusor.py::test_regulatory_element - AssertionError: len of extensions

oh yeah, I meant to add another comment about this. I have never had these tests pass locally due to data issues. Was going to recruit @jsstevenson to help look

@jsstevenson prod ddb is not updated. We’ve been testing on dev ddb.

@jsstevenson prod ddb is not updated. We’ve been testing on dev ddb. Dev and prod should point to the same data tho

Confirmed that prod ddb and dev ddb point to same data. Stick with dev for now until we update prod.

I was having trouble getting the AWS connection to work (wouldn't you need to use a previous version of gene-normalizer since the current one combines the metadata and concept tables?) so I tried with a local DB copy, freshly updated today.
It looks like the test fixtures are a bit ahead of where the prod table is, update-wise, but they're behind the current version of gene-normalizer/current data. if you:

remove all ChromosomeLocations
add Strand extensions to all gene descriptors
update one of the expected validation error messages

then all tests pass against the most recent gene-normalizer stuff. This commit shows the specific changes: 5bdcbb6. You can see specific data versioning here: https://gist.github.com/jsstevenson/82e8d1bb71ad1ca3af66810788c2445f
The change to that expected error message should definitely go through, since it's a Pydantic v2 thing. The others, though, are coming up because we're testing specifics about the Gene Normalizer, not about how FUSOR is using it. In a perfect world, we could just test that our API calls out to external services are correct, and not worry about the particulars of their responses in tests, but this project isn't set up well to support that without a lot of labor. In the meantime, IMO, I think we should drastically reduce the number of value checks that we perform on data from external services, focusing on specific, relevant, less-likely to change items that signal correct usage -- for example, the concept ID on a normalized gene, the populated existence of fields that you wouldn't find on a minimized gene descriptor, etc. These things could still change from time to time, but with fewer checks, it'd at least be much easier to pinpoint their locations, and it'd be less work to keep them up-to-date.
**alternatively, since we're using the prod DB as a shared source of truth for test purposes, we could just go back through the gene descriptor fixtures and make sure that their fields match whatever https://normalize.cancervariants.org/gene/ says they should be

added these changes. I think everything should be addressed and taken care of now. However, the tests still fail locally for me because the database I am pointing to does not have the same data as was expected in this commit: https://github.com/cancervariants/fusor/pull/108/files#diff-e52e4ddd58b7ef887ab03c04116e676f6280b824ab7469d5d3080e5cba4f2128
Bright side: the failures are not related to the changes in this PR
bad side: failing tests :(.
how should I proceed here? Additionally, with changes that will eventually be made in gene-normalizer to combine the gene concept and source tables (https://github.com/cancervariants/gene-normalization/commit/76579daa7d67f101740c5e0dfaaae8093ab193ff) what special steps will I need to take as this gets merged? Should fusion-curation just point to this fusor version until we update fusor to work with those changes (or is this even necessary? I can't remember)
I can see this causing issues with fusion-curation pointing to this fusor version but then being released into production and using production dbs... I think it would be helpful if we come up with a roadmap here so we (I) don't break anything while pushing this through the pipeline.


Accessing array out of bounds

.pio/libdeps/m5stack-core-esp32/Adeon/src/AdeonGSM.cpp: In member function 'bool Adeon::Parser::isHashParsingValid()':
.pio/libdeps/m5stack-core-esp32/Adeon/src/AdeonGSM.cpp:358:25: warning: array subscript is above array bounds [-Warray-bounds]
_tmpHash[hashLen] = _nullChar;

I fixed the issue in b884af1. However, @Robert-Faltus please check if I did it correctly.
You allocated an array to store short hash of 5 bytes, and then you wrote \0 character as a 6-th byte. I increased the size of an array. However, if the hash should be 5 bytes including the \0 character, then my fix is wrong.

OK, so short hash has 5 characters, e.g., e4917. Therefore, my fix is correct. I store the \0 character at the end.


Issue with "node e2e test" link results 404 not found on k8s.io/docs/setup/best-practices/node-conformance/#running-selected-test

This is a Bug Report

Problem:
Link to node e2e test on documentation page (at end of Running Selected Test section):
https://kubernetes.io/docs/setup/best-practices/node-conformance/#running-selected-test
reaches 404 page not found on github.
Page to Update:
content/en/docs/setup/best-practices/node-conformance.md

I would like to take this issue.

/lifecycle active

/priority backlog


Status Update Error Requeue and Bug Fix

Modifications

On status update error, requeue the reconcile key to retry.
BugFix on kustomization file for following error:

> kubectl kustomize tests/manifests | sed 's@quay.io/numaproj/@quay.io/numaproj/@' | sed 's/numaplane-controller:latest/numaplane-controller:latest/' | kubectl apply -f -

error: merging from generator &{0xc0013029c0 <nil>}: id resid.ResId{Gvk:resid.Gvk{Group:"", Version:"v1", Kind:"ConfigMap", isClusterScoped:false}, Name:"numaflow-controller-definitions-config", Namespace:"numaplane-system"} does not exist; cannot merge or replace

Codecov Report
Attention: Patch coverage is 0% with 10 lines in your changes missing coverage. Please review.

Project coverage is 52.66%. Comparing base (c34318e) to head (1d496bf).

Files
Patch %
Lines

internal/controller/pipelinerollout_controller.go
0.00%
4 Missing :warning:

...nternal/controller/isbservicerollout_controller.go
0.00%
3 Missing :warning:

...controller/numaflowcontrollerrollout_controller.go
0.00%
3 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #128   +/-   ##
=======================================
  Coverage   52.66%   52.66%
=======================================
  Files          15       15
  Lines        1540     1540
=======================================
  Hits          811      811
  Misses        602      602
  Partials      127      127

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


Feature Request with gitlab to include a Merge Request ID in pipeline hook

I opened a pull request to https://github.com/xanzy/go-gitlab/pull/752
I'll make the development, after merged

Amazing! Thank you!

Thank you! 💥


Kytos base image name does not match in kytos-sdx-topology Dockerfile

Hi,
The data-plane/1_build_kytos.sh creates a base docker image for Kytos and tag it as kytos-base. On the other hand, kytos-sdx-topology/Dockerfile consumes an image named kytos_base.
At least on the docker setup I have, docker was not able to resolve this naming typo, resulting in the following error:
ubuntu@sdx:~/sdx-continuous-development/data-plane$ ./2_build_oxpos.sh
[+] Building 0.8s (3/3) FINISHED
 => [internal] load build definition from Dockerfile                                                                                0.1s
 => => transferring dockerfile: 275B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.1s
 => => transferring context: 2B                                                                                0.0s
 => ERROR [internal] load metadata for docker.io/library/kytos_base:latest                                                                                0.4s
------
 > [internal] load metadata for docker.io/library/kytos_base:latest:
------
Dockerfile:2
--------------------
   1 |     # pull os base image
   2 | >>> FROM kytos_base
   3 |
   4 |     # set work directory
--------------------
ERROR: failed to solve: kytos_base: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
[+] Building 0.7s (3/3) FINISHED
 => [internal] load build definition from Dockerfile                                                                                0.1s
 => => transferring dockerfile: 275B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.1s
 => => transferring context: 2B                                                                                0.0s
 => ERROR [internal] load metadata for docker.io/library/kytos_base:latest                                                                                0.3s
------
 > [internal] load metadata for docker.io/library/kytos_base:latest:
------
Dockerfile:2
--------------------
   1 |     # pull os base image
   2 | >>> FROM kytos_base
   3 |
   4 |     # set work directory
--------------------
ERROR: failed to solve: kytos_base: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
[+] Building 0.6s (3/3) FINISHED
 => [internal] load build definition from Dockerfile                                                                                0.1s
 => => transferring dockerfile: 275B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.1s
 => => transferring context: 2B                                                                                0.0s
 => ERROR [internal] load metadata for docker.io/library/kytos_base:latest                                                                                0.3s
------
 > [internal] load metadata for docker.io/library/kytos_base:latest:
------
Dockerfile:2
--------------------
   1 |     # pull os base image
   2 | >>> FROM kytos_base
   3 |
   4 |     # set work directory
--------------------
ERROR: failed to solve: kytos_base: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
[+] Building 0.7s (3/3) FINISHED
 => [internal] load build definition from Dockerfile                                                                                0.1s
 => => transferring dockerfile: 275B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.1s
 => => transferring context: 2B                                                                                0.0s
 => ERROR [internal] load metadata for docker.io/library/kytos_base:latest                                                                                0.3s
------
 > [internal] load metadata for docker.io/library/kytos_base:latest:
------
Dockerfile:2
--------------------
   1 |     # pull os base image
   2 | >>> FROM kytos_base
   3 |
   4 |     # set work directory
--------------------
ERROR: failed to solve: kytos_base: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
[+] Building 2.4s (8/8) FINISHED
 => [internal] load build definition from Dockerfile                                                                                0.1s
 => => transferring dockerfile: 99B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.1s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load metadata for docker.io/library/python-base:latest                                                                                0.0s
 => [1/3] FROM docker.io/library/python-base                                                                                0.5s
 => [internal] load build context                                                                                0.3s
 => => transferring context: 1.21kB                                                                                0.0s
 => [2/3] WORKDIR /app                                                                                0.5s
 => [3/3] COPY ./container-worker/ /app                                                                                0.4s
 => exporting to image                                                                                0.5s
...

I was able to fix the above error by applying the following change:
diff --git a/data-plane/1_build_kytos.sh b/data-plane/1_build_kytos.sh
index f8f1002..c796cc9 100755
--- a/data-plane/1_build_kytos.sh
+++ b/data-plane/1_build_kytos.sh
@@ -1,5 +1,5 @@
 #!/bin/sh
-docker build -f os_base/kytos_base/Dockerfile -t kytos-base .
+docker build -f os_base/kytos_base/Dockerfile -t kytos_base .
 docker build --no-cache -f container-mininet/Dockerfile -t mininet .
 docker build --no-cache -f os_base/mongo_base/Dockerfile -t sdx-mongo .
 docker build --no-cache -f os_base/python_base/Dockerfile -t python-base .


Update Level

Finished creating the next level. Added more four spots kitchen, two living spaces one with a book shelf, a table with chairs. However, with the new slingshot the it's very easy for the cat to get the yarn. There is one spot that is very high for the player, where I would want the player to create a platform for the ball but needs more testing. Please let me know if I messed something else or I misunderstood something

Doesn't have all changes from current develop, so had to merge in from develop, but otherwise, the layout looks good

PR was going to be merged in main, edited it to merge into develop


Show errors when changeset fails to create

Currently this just shows that the waiter failed - instead we should get the failure reason from the changeset.

Unfortunately, I didn't make a note of when ChangeSet failures occur as they are pretty rare.
At the time I was working on this it was for a Lambda function, so it was probably related to that, but it's unclear what the failure was that I saw.
Errors in the template (invalid resource types, circular references) or missing parameters cause ValidationError instead and the error handling is OK for these.
If there are missing required properties, or imports that do not exist the changeset still creates successfully.
For now, resolving this by changing the exception that is thrown to include the reason/failure message and hope that covers all cases.


Optional Add Resource button for resource component

Added checkbox to show Add Resource button.  If it's checked the control to set the button's label will be visible.

Pulling this into the next build.


Sample Visualization and Metrics

We have trained the diffusion model in more than 100,000 steps and sampled the test images.
However, the predictions seem wrong as pixel values vary from 0 to tens instead of 0,1.
How to obtain the final segmentation mask?

I tried to visualize the prediction in the heatmap and it is like this:

It should be 0-1. Have you modified the code? Is it the prediction saved by the scource code in ./results fold?

I have not modified the code. I will check the details. Thanks.

@jcwang123 Hi, have you solved this question? I met the same problem.

I have not modified the code. I will check the details. Thanks.
Hi, did you figure out this problem? I have the same problem in visualization.

I have not modified the code. I will check the details. Thanks.

@jcwang123 Hi, did you figure out this problem? I have the same problem in visualization.

Did you figure out this problem?

I have not modified the code. I will check the details. Thanks.

@jcwang123 Hi, did you figure out this problem? I have the same problem in visualization.
Did you figure out this problem?


Use global TypeScript instead of local

I am using the latest version 3.1.4, and when I use it in my project I get the following error:

gulp-typescript: TypeScript not installed - install with npm install typescript --save-dev
As of gulp-typescript 3.0, TypeScript isn't bundled with gulp-typescript any more.
Install the latest stable version with npm install typescript --save-dev
or a nightly with npm install typescript@next --save-dev
More information: http://dev.ivogabe.com/gulp-typescript-3/

I do however, have the extension installed globally.
npm install typescript -g

Is there anyway that the extension could use the globally installed version instead of the locally installed version?

It's the design of Node that modules use local dependencies. In this case, gulp-typescript is thus using a local installation of TypeScript. Before 3.0, gulp-typescript was installing a local installation. As of 3.0 you should do it yourself, such that you can easily choose the right version. You can install it using npm install typescript --save-dev


 It has an issue

whatisit

I dunno. You tell me?

what

it has an issue which you know about and oyu won't tell me

Actually...

There's two. One more minor tho

streeettcchh
/ᐠ-ꞈ-ᐟ
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█
█_∫

whatarethey

tellmenow

aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

f in e

godnignt jfk sdafsfksgdjfshdaf ky839p5;.k,3


Fix failing check on an invalid version

https://github.com/flitbit/fpipe/blob/360035252ce54951bc05c97907f59343ced35a48/package.json
was failing (because version was not a string).

ping @gorillamania.

This is now live with 0.6.1

Thanks!


[Bug]:  NocoDB service does not allow external database connections despite correct configuration

Is there an existing issue for this?

[X] I have searched the existing issues

Description
The nocoDB service does not appear to be honoring the environment variable to allow external database connections ("Disable External Database" in coolify UI).
The default service configuration sets this environment variable to 0 by default, which should allow nocoDB to connect to external databases.
I read in the nocoDB documentation here that it will disable all external database connections if NC_CONNECT_TO_EXTERNAL_DB_DISABLED is set to a non-empty string.
I'm wondering if the configuration of the environment variables in coolify could possibly be triggering this. Thanks in advance for your help with this and for all of your hard work on coolify!
Steps To Reproduce

Create a new nocoDB service using the default configuration.
Log in to the nocoDB service as the superuser
Attempt to create a new project by connecting to an external database (the dropdown menu will not appear)

Version
3.11.13

I'm closing this issue, because tracking features will be moved to GitHub discussions. Github issues will be only for bugs.
Version 4 is in full focus. v3 related issues will be closed, if it is not a critical bug.
Thanks for your understanding.


[Skyway] Paloma needs to identify if an event is real or not and skip otherwise

@maharifu is this something that will make the release for tomorrow?

@maharifu is this something that will make the release for tomorrow?

No, this will not make it into this release.


Scan iOS App (.ipa) file

I scanned my Android file (.apk) for SAST. How do I scan iOS version app for static scan (SAST) using this tool?
Technology used: Flutter

Hello, we regret to inform you that this type of files are not yet supported in our scan.


Add more docs to framework.dart

There are still more to go, but this patch completes the widget section.

@Hixie


Move legends to below chart to avoid word wrapping issues

The standard Lines of Code, and Quality Trend charts have the legend to the write. On my display at least, this causes word wrapping issues that render the legends pretty much useless.
This change moves the legends to below the chart which improves things considerably.
Before the change:
https://www.dropbox.com/s/55yrz602a3h1uba/Screenshot 2015-02-01 15.20.07.png?dl=0
After the change:
https://www.dropbox.com/s/1qiw8nakpnj2c48/Screenshot 2015-02-01 15.21.58.png?dl=0

Thanks @leewillis77 - This has been merged.


[Go-SDK] Check correct cache for wrapped structs.

The registry for wrapped struct methods is looking at the wrong cache before the overwrite warning.
No behavioral change other than correctly warning on duplicate registrations.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R: @youngoli


Color picker glitches while animation is playing

Godot version:

3.2.4.rc3.mono.official
OS/device including version:

Win10, gtx1060
Issue description:

When an animation is playing and the color picker is open and the eyedropper is active, the displayed color randomly jumps around:
https://user-images.githubusercontent.com/8841352/110208047-2ae0ea80-7e87-11eb-9130-cb371426a210.mp4
Steps to reproduce:
See, video

https://user-images.githubusercontent.com/64188282/110232214-71057f00-7f57-11eb-8166-86e8eb0f4bf6.mov
can reproduce issue on Mac too but only when using animation player, animation tree is fine. also this glitches only happened when mouse moving, if mouse stop moving, the color picker won't pick any color instead it will return the color you have setted


PackageProvider system not in sync between Windows PS and PS Core

Steps to reproduce
1. perform (Package Management) commands Get-PackageSource or Get-PackageProvider on PS Core
2. perform the same commands on Windows PS v5.1

Expected behavior
-----------------

I'd expect both PS implementations using the same Package Management as being implemented in .NET, including access to the same PackageSource's or PackageProvider's. Which means in a powershell script I have to determine in the script of it's going to be executed in PS Core or the Windows PS.
Having the OS abstraction with PS Core having the abstraction of the execution environment to use the package management would make software management by PS much more effective.

Actual behavior
---------------

PS Core only provides access to the Package Provider PowerShellGet but provides not access to the msi, msu, or Programs package providers. As well extension on PackageProviders, or Sources are not taken into account in one or the other environment.

Environment data
----------------

<!-- provide the output of $PSVersionTable -->

```powershell
> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      6.0.2
PSEdition                      Core
GitCommitId                    v6.0.2
OS                             Microsoft Windows 10.0.17134
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

PowerShell Core seems to be at the beginning of the road.

@SydneyhSmith can this issue be closed or moved to the OneGet repo?


Write SMD schema to file

It is a bit inconvenient to expose SMD schema only as an http endpoint.
For example, you might have other tools that work with SMD schema and you could not use them automatically with zenrpc without SMD schema in a file.

Its can done manually ,I implemented a cli subcmd to generate the smd file manaually though cobra for ci usage
simplified version
rpc := zenrpc.NewServer(zenrpc.Options{ExposeSMD: true})
rpc.Register("user", UserService{})
rpc.Register("data", DataService{})
data, err := json.MarshalIndent(rpcServer.SMD(), "", "\t")
if err != nil {
	panic(err)
	return
}
err = ioutil.WriteFile("smd.json", data, 0644)
if err != nil {
	panic(err)
	return
}


Implement the Orchestra runner

The Orchestra runner and related workflow service is the new workflow engine for StackStorm. This new workflow engine and the new workflow DSL that accompanies the new engine will replace Mistral in StackStorm. For this beta release, Orchestra will support the following features.

Run, pause, resume, and cancel of workflows and subworkflows.
Sequential workflows and workflows with cycles, branches, forks, and joins.
YAQL and Jinja expressions in workflow input, vars, task (action, input, when, publish, do), & output
Multipoint inspection of syntax, semantics, context, and expressions on the workflow definition in a single pass.
Improved runtime traceability and error handling.

As this is a new feature, let's please make sure all the new and affected tests also run and pass under Python 3.

@m4dcoder Here is an example of how we do it inside st2 repo using tox - https://github.com/StackStorm/st2/blob/master/tox.ini#L29.


Nubian 74 refactor sdk logic

What?
Added simple methods that can be called to swap on Pancakeswap and deposit and withdraw on Venus. These functions handle the casting, the frontend just calls them.
Why?
This is to prevent the frontend from casting and formatting values before they are sent to the smart contract, the SDK handles all that now.
How?
The SDK now provides methods for each protocol directly on an instantiated Nub class. E.g nub.pancakeswap.swap for swapping. These functions directly do the casting and format the values passed to them to be used on the smart contract.
Testing?
I've added coverage for testing Pancakeswap swap methods and Venus deposit and withdraw methods. Follow these steps to run tests:

Start up a node with npx hardhat node --fork https://speedy-nodes-nyc.moralis.io/40fcc85be509fe0b0f81c26e/bsc/mainnet/archive
Run all tests with npm run test

It's just used to recongnise BNB transactions and handle them appropriately
on the smart contracts.
On Mon, Mar 7, 2022, 16:57 kayroy247 @.***> wrote:

@.**** commented on this pull request.
In src/constants/addresses/index.ts
https://github.com/NestcoinCo/nubian-coven-sdk/pull/16#discussion_r820847408
:

@@ -11,6 +11,7 @@ import { TOKENS as TOKENS_TESTNET  } from './testnet/tokens';

export const Addresses = {
genesis: '0x0000000000000000000000000000000000000000',

bnb: "0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE",

Is there a reason you are using this address for BNB? Because BNB is not a
BEP-20 token and as such does not have an address
—
Reply to this email directly, view it on GitHub
https://github.com/NestcoinCo/nubian-coven-sdk/pull/16#pullrequestreview-901893342,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJC4VLKMV7ADID3QVN7JE4LU6YRPTANCNFSM5QBGJFVQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


Distance isn't remembered after screen rotation

I downloaded new example v2.0.0 and set the distance but it seams it doesn't stay after screen rotation
self.sd.show(drawer: vc) { config in
    var newConfig = config
    newConfig.distance = 300.0
    return newConfig
}

I think that after the rotation the config should be called once more i.e. if I want to have 75% width in portrait and 50% in landscape
Portrait

Landscape

I make the the ratio of drawer's distance to screen width after rotation equal to the radio of config's distance to screen width before rotation.

I understand. Personally, I would prefer the option of setting a constant width regardless of the screen orientation, but I understand that you want to do it your own way. Alternatively, I will try to figure it out myself.

Maybe I can add a public property to indicate whether distance is absolute or not.

Yes, that would be nice

@Bruce-pac any updates?


Collect frontend code coverage from Cypress tests

CATEGORY

[x] Build / Development Environment

SUMMARY
College frontend code coverage from Cypress tests and add proper tagging for coverage reports.
With this, we can finally start to take code coverage numbers more seriously.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TEST PLAN

ADDITIONAL INFORMATION
N/A
REVIEWERS

Will do this after the Github Actions were merged.


chore: update with current upstream

Current upstream used is 6df92d9c0e29842c634a956588c561dbf939e42b, which is 1.8.0 + some fixes in master.
Also updates CI builder images and OTP/Elixir/distro versions.
TODO

[x] use builder 5.1-3 once it's released

tagged 1.8.0-emqx-1


embed an X in a J (2nd attempt)

https://www.notion.so/statechannels/Virtual-funding-research-11388f704f84496ba8febe30ddb522d2

In favour of #3565 (cleaner history)


Resources not being configured

I created a simple eks terrafrom template with managed eks node groups but the issue I am facing is that no resources are being created. I can see the eks cluster there but the other resources nodes, replica sets and other necessary configurations are not being mapped. I have attached the template I am using below:
`module "eks" {
source          = "terraform-aws-modules/eks/aws"
version         = "20.2.1"  # Use the latest version
cluster_name    = "my-eks-cluster"
cluster_endpoint_public_access = true
cluster_addons = {
coredns = {
most_recent = true
}
kube-proxy = {
most_recent = true
}
vpc-cni = {
most_recent = true
}
}
vpc_id                   = module.vpc.vpc_id
subnet_ids               = module.vpc.private_subnets
control_plane_subnet_ids = module.vpc.intra_subnets
enable_cluster_creator_admin_permissions = true
EKS Managed Node Group(s)
eks_managed_node_group_defaults = {
ami_type       = "AL2_x86_64"
instance_types = ["m5.large"]
attach_cluster_primary_security_group = true

}
eks_managed_node_groups = {
my-node-group = {
min_size     = 1
max_size     = 2  # Keep the max size low for cost savings
desired_size = 1
  instance_types = ["t3.micro"]
  capacity_type  = "ON_DEMAND"  # Use SPOT instances for further savings
}

}
tags = local.tags
}
`
Is there something that I am not doing right? The core dns is not getting installed and the health check failure suggests that it is due to the fact that there are not sufficient replica sets

Have you checked the karpenter logs?
kubectl logs -n kube-system karpenter........
I might have similar issue after using the example tf files from github.
I'm not sure why it's trying to create a spot instance, maybe capacity_type  = "ON_DEMAND" is not supported.
error":"launching nodeclaim, creating instance, with fleet error(s), AuthFailure.ServiceLinkedRoleCreationNotPermitted: The provided credentials do not have permission to create the service-linked role for EC2 Spot Instances."}


Parallelize the workflows of http and sdk examples

Parallelize the workflows of http and sdk examples.

Hi - what are we trying to solve here, the time to build and test?  Does this improve the failure rates for the tests?
@amulyavarote


What is "Outbound authentication"

[Enter feedback here]
"Outbound authentication" is referenced 5 times on this page, but has no reference as to what that means.
A search with your search engine of choice for ' "Outbound authentication" site:microsoft.com ' also doesn't seem to turn up anything immediately relevant.

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

ID: a31db532-baae-df07-4ab6-d9714db8b33d
Version Independent ID: f6f28a52-6a57-7507-2912-7d0770f2bcaa
Content: Getting Started with Group Managed Service Accounts
Content Source: WindowsServerDocs/security/group-managed-service-accounts/getting-started-with-group-managed-service-accounts.md
Product: windows-server
Technology: security
GitHub Login: @JasonGerend
Microsoft Alias: jgerend

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


chore: update xterm imports to use @xterm/xterm package (#4036)

Types

[x] 🧹 Chores

Migrate xterm to @xterm/xterm and update related addon packages accordingly
Background or solution
Changelog

Summary by CodeRabbit

新特性

更新了终端功能的依赖，采用了新的 @xterm 包，提升了终端的性能和功能。
增加了对多个新依赖的支持，如 @xterm/addon-canvas 和 @xterm/addon-fit。

修复

修正了终端服务中的命令建议和提示的逻辑，提升了用户交互体验。

文档

更新了相关的导入路径，确保一致性和可维护性。

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@nxps 请签署一下上面的 CLA 证书 ~ 感谢贡献

@erha19 Done


Create .npmignore

Remove test/ folder from being published with the npm package

Please show that this makes a meaningful difference, i.e. only if the tarball is significantly smaller will I consider the pull, otherwise not since for some people working offline it is important to access the tests as part of the packages they installed locally on their machine.
You can compare the sizes as follows:
git checkout master
npm pack
du -h *.tgz

git checkout <your-branch>
npm pack
du -h *.tgz

Decided to go ahead with that in bdac11df.
It reduces the package size twice (13kb -> 7kb), which saves about 6000*3500000/(1024**3) 19Gb of traffic every week for NPM users.


Add type guard to 'is' and 'is.not' methods

As each instances are defined as branded type of the extended enum (#7), type guards should be supported.
enum _Fruit { Apple, Orange }

class Fruit extends extend<typeof _Fruit, _Fruit>(_Fruit) {}

declare const f: Fruit;

if (f === Fruit.Apple) {
  type T = typeof f; // should be Fruit.Apple, it is not working now regardless of type guards
}

if (f.is(Fruit.Apple)) {
  type T = typeof f; // Fruit.Apple
}

if (f.is.not(fruit.Apple)) {
  type T = typeof f; // Exclude<F, Fruit.Apple> or something similar
}

Apparently, type guards by nested property is not supported in current version of TypeScript. (related issue - https://github.com/microsoft/TypeScript/pull/38839)
Therefore, providing a type guard for is.not is not possible right now.
We propose an alternative to use isNot as an alias of is.not. isNot lives as a direct property of ExtendedEnum, hence it can be used for type narrowing.
is.not will continue to be supported, but type guards will not be provided.


Grab the latest version of pypairtree from GitHub.

ping @ldko, @madhulika95b, this is ready for review.


fix: remove alert link styling

Swap bootstraps alert mixin with just the styles required in Paragon

Coverage remained the same at 87.223% when pulling e89f6c88254e59765a3d76ab741c71b7ca308993 on abutterworth-patch-1 into aa29f96edf30a941b73103906a455d0cf441730a on master.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Deal with Waters data that has lockmass channel, but leads with measurements in a non-MS channel…

… which confused our lockmass channel detection logic

I think the "skip functions greater than the presumed lockmass function" log is pretty much an optimization since they'd be ignore anyway with an MS level. But ideally, yes, they'd never get passed in at all, nor would lockmass. There's already a flag for ReaderConfig "ignoreCalibrationScans" but it doesn't seem to be doing anything in this case.

Huh, somehow I had read the new for loop as only looking at the first 5 spectra. That's why I mentioned there perhaps being dozens or hundreds of EMR spectra. If you're potentially checking the whole list, that's not an issue.


File based items do not display JSON

When viewing an item's JSON, ago-assistant displays both sharing/rest/content/items/<itemid> and sharing/rest/content/items/<itemid>/data.  This is great for things like WebMaps.  However, for file based items like a .zip or .sd, the /data call attempts to download the actual file.  Unfortunately, this causes that entire item's JSON to not display.
We need to alter the JSON just slightly to first get the item description and then only display the /data if it is not a file based item.  How do we know this?  Well, without building a list of all possible file based item Types, I was once told that if the "name" key value has a period '.' in the name, you can assume it is file based, e.g. myroads_shapefile.zip.  Not sure how valid that is.

Fixed via PR #197


Tabs accept href attribute

Lets you change the tab on a link, using the angular uiRoutes allows you to upload the contents of the page only when it is selected.
Ex.
$stateProvider
  .state('tabs', {
    url: '/tabs',
      views: {
        'master': {
          templateUrl: 'tabs.html'
        }
      }
    })
    .state('tabs.one', {
      url: '/one',
      views: {
        'one': {
          templateUrl: 'one.html'
        }
      }
    })
    .state('tabs.two', {
      url: '/two',
      views: {
        'two': {
          templateUrl: 'two.html'
        }
      }
    });

    <lx-tabs links-tc="light" links-bgc="teal-500" indicator="white" no-divider="true" z-depth="1">
        <lx-tab icon="store" href="#/tabs/one">

        </lx-tab>
        <lx-tab icon="history" href="#/tabs/two">

        </lx-tab>
    </lx-tabs>

Cool PR, thanks! Maybe it would be better to have the tabs directive require ngHref? Not sure if it's possible, but I don't see why not. Regarding your commits, could you rewrite them to follow the contributing guidelines please? Thanks in advance!

As LumX has ben completly reworked, I unfortunatly need to close your PR. Thanks for contributing. This feature can still be a good enhancement, maybe you can take a look to the new LumX version ? ;-)


Not At Position rule causes the word to be longer

Introduced by #14
If a not-at-position rule refers to a position beyond the last required word, it causes the required length to be extended.
Shown below is an example and its resulting regex. The not-at-position rule causes filler to be added, incorrectly making the word longer.
A better way would be to replace .{6}[^c\n].* with (.{0,5}|.{6}[^c\n].*)
This is only needed if there are no future at-position rules or exact/min word length that requires it to be that long regardless.
^(?<word>(?=(.*[t].*){1,})(?=(.*[h].*){1,})(?=(.*[i].*){1,})(?=(.*[n].*){1,})(?=(.*[g].*){1,}).{2}[e].{6}[^c\n].*)$

A potential solution would be to check the max position for at-position rules and check the exact/min length. If the not-at-position rule is beyond either, then use the or operator.

A different potential solution is to keep the current method only for positions known to be in the word (before min length or before an "at position rule"). And use a lookahead for any others.
So when the "at position" rules are handled, any "not at position" rules will also be handled. This already happens, but instead the maxPosition be determined only by the "at position" rules.
Might also check how exact length is handled.


belinda-nextjs-feature-194-update-to-mui

updated some styling on the main page, set some styling in the global theme, big updates to the donation page and add product page to use Material UI

Thank you for making these updates.
My concern is that other pages are styled a bit differently such as:
Home page
Login page
Product page
We may need to decide on one of these to make pages consistent.
Home page

Login page

Product Page

@tinpham5614 I'll work on making them consistent in the next update and try to get a pull request up by the end of tomorrow. I'll go with the general layout of the sign-in page with the wider center div. I don't know if that will be the final design in the end, but at least getting all the pages on the same layout will make it easier to change them all if we decide to change things in the future.


Replace dask_ml.wrappers.ParallelPostFit with custom ParallelPostFit class

As part of our initiative to move away from Dask-ML, I've migrated some code from Dask-ML into Dask-SQL to support ParallelPostFit.

Codecov Report

Merging #832 (7f27005) into main (bc7f82c) will decrease coverage by 1.68%.
The diff coverage is 33.57%.

@@            Coverage Diff             @@
##             main     #832      +/-   ##
==========================================
- Coverage   74.88%   73.20%   -1.69%
==========================================
  Files          71       72       +1
  Lines        3588     3725     +137
  Branches      748      772      +24
==========================================
+ Hits         2687     2727      +40
- Misses        771      859      +88
- Partials      130      139       +9

Impacted Files
Coverage Δ

dask_sql/physical/rel/custom/wrappers.py
33.09% <33.09%> (ø)

dask_sql/physical/rel/custom/create_model.py
84.48% <100.00%> (-0.27%)
:arrow_down:

dask_sql/physical/rel/logical/window.py
95.37% <0.00%> (-1.74%)
:arrow_down:

dask_sql/physical/rel/custom/predict.py
88.88% <0.00%> (-0.40%)
:arrow_down:

dask_sql/_version.py
32.27% <0.00%> (-0.29%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Let me know if you think any tests from Dask-ML's tests/test_parallel_post_fit.py or from https://github.com/dask/dask-ml/pull/912 should be added.


utils/netutils: handle Atoi conversion error

The unit tests passed. The system tests are still running.

LGTM

LGTM


Create Skyrim

Description

Related Issue

Fixes #
Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

This looks like spam to me. If this is a serious pull request please fill it more info in the description, and ideally link to an existing issue, and we can reopen it.


TFW: Made Testify its own library + Docs + misc changes

I could not edit the changes, so I merged them under a separate PR.


Model versioning

Currently, deepnog ships one model per eggnog level and network architecture.
If we ever decide to retrain certain models, users need to individually come up with strategies to tell models apart, or use a specific model (e.g., for reproducibility), such as manually moving files around, renaming accordingly, etc.
Retraining, however, could sometimes make sense. For example, we might want to use different data splits, increase the share of training sequences compared to test sequences to squeeze a little more performance out of the model.
We should at least introduce some versioning, model identifiers, etc., that are stored with the model. Could be a simple string inside the model_dict. This could even be "backported" to existing models.
Ideally, automatic model download should also be version-aware. Currently, a user that already has downloaded a model will not receive any updated model.

To summarize some key points of the recent discussion:
Models will receive a metadata field that holds the following information,

UUID as model identifier
Date & timestamp of training
training params (incl. learning rate, scheduler, number of epochs, etc.)
Orthology DB name
Taxonomic level in DB
metadata format version (v1 for now, v2 if this ever needs to be extended)
Technically, this can be implemented as a dict that is serialized into the .pth model file.
This can be backported to old models.

Model filenames obtain a version hint, e.g. the date, or v1, v2, etc., and a "latest" pointer to the most up-to-date version.
The client subcommand deepnog infer will use a use_latest boolean flag to use the latest model (otherwise, the one currently installed). A warning/info could be issued to users, when new models are available.


#753 Workshop name overlaps

Workshop name overlaps

you don't need just to cut the title, you should show the full title on hover, as we do for all other cases. Check how it's done for workshopcard


Added automation to create  phar file

It creates phar file when a new release is created.

the code looks good to me!


Renaming LogLevel.Verbose to Trace #299

Renaming LogLevels in logging so that Verbose is renamed to Trace and is considered less severe than Debug.
Most severe level listed first:

Current Levels
New Levels

Critical
Critical

Error
Error

Warning
Warning

Information
Information

Verbose
Debug

Debug
Trace

I will update the affected repos:

DataProtection https://github.com/aspnet/DataProtection/pull/112
UserSecrets https://github.com/aspnet/UserSecrets/pull/52
dnx-watch https://github.com/aspnet/dnx-watch/pull/39
Hosting https://github.com/aspnet/Hosting/pull/512
WebListener
EntityFramework
StaticFiles
Routing
Diagnostics
Session
Security
MVC
SignalR-Server
Identity
SignalR-Redis
SignalR-SqlServer
SignalR-ServiceBus
Performance

To keep the current order of severity existing Verbose messages will be changed to Debug and existing Debug messages will be changed to Trace.

Hi @JunTaoLuo, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

cc @kichalla

To keep the current order of severity existing Verbose messages will be changed to Debug and existing Debug messages will be changed to Trace.

I am a bit confused...the title says Verbose is becoming Trace, but the above statement is different...which is correct?

@kichalla the original intent of #299 was to swap the order of verbose and debug. But it was later decided to rename verbose to trace. To illustrate how the current severity level are maintained, take a look at DataProtection

:shipit:

All PRs are out. I'll start merging and keeping an eye on the CI.


fix: missing plugins to handle domain and route level ACL

Description:

Testing done:

Affected area:

Functional Area

New Functionality
[ ]

CI System
[ ]

CLI Tool
[ ]

Certificate Management
[ ]

Control Plane
[ ]

Demo
[ ]

Documentation
[ ]

Egress
[ ]

Ingress
[ ]

Install
[ ]

Networking
[ ]

Observability
[ ]

Performance
[ ]

SMI Policy
[ ]

Security
[ ]

Sidecar Injection
[ ]

Tests
[ ]

Upgrade
[ ]

Other
[ ]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project?

Did you notify the maintainers and provide attribution?

Is this a breaking change?

Has documentation corresponding to this change been updated in the fsm-docs repo (if applicable)?

Codecov Report
Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (89c9f65) 48.42% compared to head (4329e99) 48.44%.
Report is 2 commits behind head on release/v1.2.

Files
Patch %
Lines

pkg/k8s/client.go
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@               Coverage Diff                @@
##           release/v1.2     #144      +/-   ##
================================================
+ Coverage         48.42%   48.44%   +0.01%
================================================
  Files               194      194
  Lines             14636    14636
================================================
+ Hits               7088     7090       +2
+ Misses             7504     7502       -2
  Partials             44       44

Flag
Coverage Δ

unittests
48.44% <0.00%> (+0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

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


is possible to show the buffers bar only when more than 1 buffer is open?

Hi,
I have installed vim-airline and I find it amazing. I have seen that I can enable a buffers bar in the top if I define this option in my .vimrc
let g:airline#extensions#tabline#enabled = 1
My perfect setup would be to not show the top buffers bar when editing a single file but get the buffers bar only when multiple buffers are open. Is it possible to have the top buffers bar hidden when opening a single file but get it automatically shown in top when opening a a second buffer?
thanks for you help.

open ./vim-airline/autoload/airline/extensions/tabline/autoshow.vim
modified line 25 and 44 to  set showtabline=1
see  :h showtabline

thanks for your help @shusoar
your solution didn't work for me but you pointed me to the right file to modify :) I could fix it by editing line 5 in this file and changing "(g:, 'airline#extensions#tabline#buffer_min_count', 0)" from 0 to 2
https://github.com/bling/vim-airline/blob/master/autoload/airline/extensions/tabline/autoshow.vim#L5
thanks!


Package is failing to install

When trying to install hsdev or hdocs separately this error occurs:
Resolving dependencies...
Configuring hdocs-<IP_ADDRESS>...
Building hdocs-<IP_ADDRESS>...
Failed to install hdocs-<IP_ADDRESS>
Build log ( /Users/username/.cabal/logs/hdocs-<IP_ADDRESS>.log ):
Configuring hdocs-<IP_ADDRESS>...
Building hdocs-<IP_ADDRESS>...
Preprocessing library hdocs-<IP_ADDRESS>...
[1 of 4] Compiling HDocs.Ghc.Compat ( src/HDocs/Ghc/Compat.hs, dist/build/HDocs/Ghc/Compat.o )
[2 of 4] Compiling HDocs.Base       ( src/HDocs/Base.hs, dist/build/HDocs/Base.o )

src/HDocs/Base.hs:66:13:
    Not in scope: data constructor ‘DocMathInline’

src/HDocs/Base.hs:67:13:
    Not in scope: data constructor ‘DocMathDisplay’
cabal: Error: some packages failed to install:
hdocs-<IP_ADDRESS> failed during the building phase. The exception was:
ExitFailure 1

Even after rm -rf ~/.ghc and reinstall. The log file mentioned just contains the same message.

@lonelyelk this with GHC 7.10.3, right?

ghc --version
The Glorious Glasgow Haskell Compilation System, version 7.10.2

@lonelyelk I've revised the meta-data on Hackage; so if you cabal update and retry, cabal should now try to install hdocs-<IP_ADDRESS> (which is the most last version known to work w/ GHC 7.10.*)
@mvoidex fyi, the problem is that hdocs-<IP_ADDRESS> started depending on new constructors via 313951cb9c7f89e5480a1325086c79e137069742 which require haddock-api >= 2.17

@hvr, thanks, I'll release new version for 7.10.3 soon

Ok. Now i have further problems installing hsdev. The hdocs dependency was the only one stopping it from compiling. Should I move this report in hsdev's issues or here is fine?
$ cabal install hsdev
Resolving dependencies...
Downloading hdocs-<IP_ADDRESS>...
Configuring hdocs-<IP_ADDRESS>...
Building hdocs-<IP_ADDRESS>...
Installed hdocs-<IP_ADDRESS>
Downloading hsdev-<IP_ADDRESS>...
Configuring hsdev-<IP_ADDRESS>...
Building hsdev-<IP_ADDRESS>...
Failed to install hsdev-<IP_ADDRESS>
Build log ( /Users/kruk/.cabal/logs/hsdev-<IP_ADDRESS>.log ):
Configuring hsdev-<IP_ADDRESS>...
Building hsdev-<IP_ADDRESS>...
Preprocessing library hsdev-<IP_ADDRESS>...
[ 1 of 62] Compiling HsDev.Tools.Ghc.Prelude ( src/HsDev/Tools/Ghc/Prelude.hs, dist/build/HsDev/Tools/Ghc/Prelude.o )
[ 2 of 62] Compiling HsDev.Tools.Ghc.MGhc ( src/HsDev/Tools/Ghc/MGhc.hs, dist/build/HsDev/Tools/Ghc/MGhc.o )

src/HsDev/Tools/Ghc/MGhc.hs:31:1: Warning:
    The import of ‘Packages’ is redundant
      except perhaps to import instances from ‘Packages’
    To import instances alone, use: import Packages()
[ 3 of 62] Compiling HsDev.Version    ( src/HsDev/Version.hs, dist/build/HsDev/Version.o )
[ 4 of 62] Compiling HsDev.Tools.Ghc.Compat ( src/HsDev/Tools/Ghc/Compat.hs, dist/build/HsDev/Tools/Ghc/Compat.o )
[ 5 of 62] Compiling System.Directory.Paths ( src/System/Directory/Paths.hs, dist/build/System/Directory/Paths.o )
[ 6 of 62] Compiling System.Directory.Watcher ( src/System/Directory/Watcher.hs, dist/build/System/Directory/Watcher.o )
[ 7 of 62] Compiling HsDev.Util       ( src/HsDev/Util.hs, dist/build/HsDev/Util.o )

src/HsDev/Util.hs:77:19: Not in scope: ‘Dir.isSymbolicLink’
Updating documentation index
/Users/kruk/Library/Haskell/share/doc/x86_64-osx-ghc-7.10.2/index.html
cabal: Error: some packages failed to install:
hsdev-<IP_ADDRESS> failed during the building phase. The exception was:
ExitFailure 1

Thank you! Issue on hsdev installation is reported.

I'll comment on https://github.com/mvoidex/hsdev/issues/50

Uploaded hdocs-<IP_ADDRESS>


HIVE-27581: Upgrade jackson  from 2.9.4 to 2.12.0

What changes were proposed in this pull request?
This is the second step to remove dependency on jackson-core-asl and jackson-mapper-asl.
Why are the changes needed?
To fix SPARK-44719: NoClassDefFoundError when using Hive UDF.
Does this PR introduce any user-facing change?
Is the change a dependency upgrade?
How was this patch tested?

cc @sunchao @pan3793

@wangyum please resolve the conflicts and then I'll merge this. Thanks

Thank you @sunchao. Conflict resolved.

Merged, thanks @wangyum !


Task push mode using reactivex.

This PR changes the way Tasks are executed to a push model using Reactivex (http://reactivex.io/).
Main changes:

Task no longer handles records, instead it handles a record stream containing a Reactivex Flowable along with metadata.
Constructs modified to handle the stream instead of individual records:

Extractor: Main point of interaction is recordStream method. By default, create a stream that repeatedly calls readRecord.
Converter / Quality checker: Main point of interaction is processStream method. By default, map records using convertRecord and executePolicies.
Writer: minimal changes, mostly around RecordEnvelope explained later.

Forks work a little different. A Forker takes a ForkOperator and splits the record stream into multiple record streams. Then, we call Fork.consumeRecordStream for each such mirrored stream.
All records are wrapped in RecordEnvelope (introduced previously). This is a first step to more closely unify batch and streaming. There's nothing special about RecordEnvelope, everything works transparently, except metrics get a little tricky.

@ydai1124 can you review? @shirshanka you might be interested.

There are also build failures.

@ibuenros : High level question is how are you planning to mitigate risk with this change to the core pipeline?

@shirshanka the plan was to do it through testing, but I understand even that is risky. An alternative is to leave the old pipeline and put a configuration switch, but I don't know how ugly that may get

@ibuenros : I'd like to think through how we might do that... maybe a new Task impl ?

@shirshanka restored old task execution (albeit refactored into a separate method), which is the default execution method. However, it does still use RecordEnvelopes as that is necessary to start unifying stream and batch.


package.json: attempt to fix erroneous npm test failures

See, for example, https://travis-ci.org/ramda/ramda/jobs/57303350.

I don't see how this would help anything.  The Grunt script already does this internally.

I don't see how this would help anything.

Running four commands in series is different from running one command which does four things. I don't know why this change fixes the problem for me, but the problem was causing lots of pull requests to fail. I'm happy to rely on empirical evidence in this case.

I have no problem using it if it does fix things.  I just didn't know if it was a magical incantation or if you'd run down the source of the problem.

Definitely a magical incantation. :frog:

The really odd thing is that as far as I can tell, this should be making us run jshint, jscs, and browserify each twice, but that doesn't seem to be happening...  I wish I understood magic.

I have noticed one thing and I don't know if it is related but grunt-cli is installed globally. I think it would be better if it was added as a devDependency. Then anyone could use grunt in the npm scripts after doing npm install. I have previously seen conflicts between global and local modules. But agan, not sure that is the case here.

in that case the solution is to drop grunt


podman exec fails

BUG REPORT
/kind bug
Can't exec command in running container
After starting a container I can't use exec to execute a command int the container.
Steps to reproduce the issue:

podman run --name ubuntu -it registry.hub.docker.com/library/ubuntu bash

Open new terminal window/tab

podman exec -it ubuntu bash

Describe the results you received:
mpa@mpa-MacBookPro:~$ podman exec -it ubuntu bash
exec failed: container_linux.go:345: starting container process caused "process_linux.go:91: executing setns process caused \"exit status 22\""
Error: exit status 1

Describe the results you expected:
A bash promt inside the container
Additional information you deem important (e.g. issue happens only occasionally):
Happens always
Output of podman version:
Version:            1.3.0-dev
RemoteAPI Version:  1
Go Version:         go1.10.4
OS/Arch:            linux/amd64

Output of podman info --debug:
mpa@mpa-MacBookPro:~$ podman info --debug
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0xf8 pc=0x111dda3]

goroutine 1 [running]:
github.com/containers/libpod/libpod.(*Runtime).storeInfo(0xc4208e4b60, 0x2417fb0, 0x0, 0x0)
	/build/podman-OeFyYA/podman-1.3.0/src/github.com/containers/libpod/libpod/info.go:119 +0x53
github.com/containers/libpod/libpod.(*Runtime).Info(0xc4208e4b60, 0x16aeea8, 0xc4208e4b60, 0x0, 0x0, 0x1661be6)
	/build/podman-OeFyYA/podman-1.3.0/src/github.com/containers/libpod/libpod/runtime.go:1075 +0x110
main.infoCmd(0x23f5ac0, 0x0, 0x0)
	/build/podman-OeFyYA/podman-1.3.0/src/github.com/containers/libpod/cmd/podman/info.go:59 +0xc7
main.glob..func49(0x23934c0, 0xc420374d40, 0x0, 0x1, 0x0, 0x0)
	/build/podman-OeFyYA/podman-1.3.0/src/github.com/containers/libpod/cmd/podman/info.go:32 +0x87
github.com/containers/libpod/vendor/github.com/spf13/cobra.(*Command).execute(0x23934c0, 0xc4200cc080, 0x1, 0x1, 0x23934c0, 0xc4200cc080)
	/build/podman-OeFyYA/podman-1.3.0/src/github.com/containers/libpod/vendor/github.com/spf13/cobra/command.go:762 +0x468
github.com/containers/libpod/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0x2394c80, 0x6, 0x24199e0, 0xc4201d7100)
	/build/podman-OeFyYA/podman-1.3.0/src/github.com/containers/libpod/vendor/github.com/spf13/cobra/command.go:852 +0x30a
github.com/containers/libpod/vendor/github.com/spf13/cobra.(*Command).Execute(0x2394c80, 0xc420704370, 0xc4200bc058)
	/build/podman-OeFyYA/podman-1.3.0/src/github.com/containers/libpod/vendor/github.com/spf13/cobra/command.go:800 +0x2b
main.main()
	/build/podman-OeFyYA/podman-1.3.0/src/github.com/containers/libpod/cmd/podman/main.go:150 +0x3e

Additional environment details (AWS, VirtualBox, physical, etc.):
Ubuntu 16.04 installen on a MacBook Pro 15 without any virutalization.

Where did you get the software for this?  Do you have an up 2 date version of runc.
@lsm5 PTAL

I followed the Ubuntu instructions here
https://github.com/containers/libpod/blob/master/install.md
and had the latest docker installed
mpa@mpa-MacBookPro:/tmp$ runc -v
runc version 1.0.0-rc6+dev
commit: 2b18fe1d885ee5083ef9f0838fee39b62d653e30
spec: 1.0.1-dev

Info seems to be segfaulting on trying to dereference r.store. Given the way the PPA works, this is probably master, which means it has the single rootless userns patch, which I think means we always configure the rootless userns.

@panzerdev Can you try those commands as root, and see if they work?

If I run podman as root for the run and exec command it works a expected.
Hav

No, this sounds like a bug, but one specific to our rootless code - we need to do more work to get Podman running without root (setting up a user namespace so we can gain limited versions of certain capabilities), and some piece of that seems to be breaking.

@panzerdev is this working for you now? @giuseppe ptal if not

@baude I am running
Version:            1.3.2-dev
RemoteAPI Version:  1
Go Version:         go1.10.4
OS/Arch:            linux/amd64

and it is still the same issue.

Does podman info work now, and if so, can you post it?
If it doesn't, that still tells us something

if you have no problems to run the container, could you run a process inside of it.  And from the host do a cat /proc/$(PID_OF_THE_PROCESS_INSIDE_THE_CONTAINER)/uid_map?
You could for example do:
$ podman run --rm -d registry.hub.docker.com/library/ubuntu sleep 123.4
$ cat /proc/$(pgrep -f 123.4)/uid_map

@giuseppe
mpa@mpa-MacBookPro:~$ cat /proc/$(pgrep -f 123.4)/uid_map
         0       1000          1
         1     100000      65536

That's the result
@mheon
mpa@mpa-MacBookPro:~$ podman ps
CONTAINER ID  IMAGE                                          COMMAND      CREATED             STATUS                 PORTS  NAMES
4faddae85d25  registry.hub.docker.com/library/ubuntu:latest  sleep 123.4  About a minute ago  Up About a minute ago         determined_wozniak
mpa@mpa-MacBookPro:~$ podman exec -it determined_wozniak bash
exec failed: container_linux.go:346: starting container process caused "process_linux.go:101: executing setns process caused \"exit status 1\""
Error: exit status 1
mpa@mpa-MacBookPro:~$ podman info
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x100 pc=0x1131cb3]

goroutine 1 [running]:
github.com/containers/libpod/libpod.(*Runtime).storeInfo(0xc4203ec1e0, 0x2461f78, 0x0, 0x0)
	/build/podman-qFWEMp/podman-1.3.2/src/github.com/containers/libpod/libpod/info.go:119 +0x53
github.com/containers/libpod/libpod.(*Runtime).Info(0xc4203ec1e0, 0x16d3998, 0xc4203ec1e0, 0xc420911100, 0x0, 0x0)
	/build/podman-qFWEMp/podman-1.3.2/src/github.com/containers/libpod/libpod/runtime.go:1114 +0x10d
main.infoCmd(0x243f7c0, 0x0, 0x0)
	/build/podman-qFWEMp/podman-1.3.2/src/github.com/containers/libpod/cmd/podman/info.go:60 +0xe8
main.glob..func64(0x23dcc60, 0x2461f78, 0x0, 0x0, 0x0, 0x0)
	/build/podman-qFWEMp/podman-1.3.2/src/github.com/containers/libpod/cmd/podman/info.go:33 +0x87
github.com/containers/libpod/vendor/github.com/spf13/cobra.(*Command).execute(0x23dcc60, 0xc42000c070, 0x0, 0x0, 0x23dcc60, 0xc42000c070)
	/build/podman-qFWEMp/podman-1.3.2/src/github.com/containers/libpod/vendor/github.com/spf13/cobra/command.go:762 +0x468
github.com/containers/libpod/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0x23de420, 0x6, 0x24639a0, 0xc42019cf00)
	/build/podman-qFWEMp/podman-1.3.2/src/github.com/containers/libpod/vendor/github.com/spf13/cobra/command.go:852 +0x30a
github.com/containers/libpod/vendor/github.com/spf13/cobra.(*Command).Execute(0x23de420, 0xc420712160, 0xc4200aa058)
	/build/podman-qFWEMp/podman-1.3.2/src/github.com/containers/libpod/vendor/github.com/spf13/cobra/command.go:800 +0x2b
main.main()
	/build/podman-qFWEMp/podman-1.3.2/src/github.com/containers/libpod/cmd/podman/main.go:142 +0x3e
mpa@mpa-MacBookPro:~$

That's the result of podman info after I tried call exec.
Before:
mpa@mpa-MacBookPro:~$ podman info
host:
  BuildahVersion: 1.8.2
  Conmon:
    package: 'conmon: /usr/libexec/crio/conmon'
    path: /usr/libexec/crio/conmon
    version: 'conmon version , commit: '
  Distribution:
    distribution: ubuntu
    version: "16.04"
  MemFree:<PHONE_NUMBER>
  MemTotal:<PHONE_NUMBER>6
  OCIRuntime:
    package: 'cri-o-runc: /usr/lib/cri-o-runc/sbin/runc'
    path: /usr/lib/cri-o-runc/sbin/runc
    version: 'runc version spec: 1.0.1-dev'
  SwapFree:<PHONE_NUMBER>2
  SwapTotal:<PHONE_NUMBER>4
  arch: amd64
  cpus: 8
  hostname: mpa-MacBookPro
  kernel: 4.4.0-148-generic
  os: linux
  rootless: true
  uptime: 26h 47m 40.53s (Approximately 1.08 days)
registries:
  blocked: null
  insecure: null
  search: null
store:
  ConfigFile: /home/mpa/.config/containers/storage.conf
  ContainerStore:
    number: 1
  GraphDriverName: vfs
  GraphOptions: null
  GraphRoot: /home/mpa/.local/share/containers/storage
  GraphStatus: {}
  ImageStore:
    number: 1
  RunRoot: /tmp/1000
  VolumePath: /home/mpa/.local/share/containers/storage/volumes

could you please attach the output of podman --log-level=debug info --debug?

Of course @giuseppe
INFO[0000] running as rootless
DEBU[0000] Initializing boltdb state at /home/mpa/.local/share/containers/storage/libpod/bolt_state.db
DEBU[0000] Using graph driver vfs
DEBU[0000] Using graph root /home/mpa/.local/share/containers/storage
DEBU[0000] Using run root /tmp/1000
DEBU[0000] Using static dir /home/mpa/.local/share/containers/storage/libpod
DEBU[0000] Using tmp dir /run/user/1000/libpod/tmp
DEBU[0000] Using volume path /home/mpa/.local/share/containers/storage/volumes
DEBU[0000] Set libpod namespace to ""
DEBU[0000] Not configuring container store
DEBU[0000] Initializing event backend file
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x100 pc=0x1131cb3]

goroutine 1 [running]:
github.com/containers/libpod/libpod.(*Runtime).storeInfo(0xc4203d61e0, 0x2461f78, 0x0, 0x0)
	/build/podman-qFWEMp/podman-1.3.2/src/github.com/containers/libpod/libpod/info.go:119 +0x53
github.com/containers/libpod/libpod.(*Runtime).Info(0xc4203d61e0, 0x16d3998, 0xc4203d61e0, 0xc420587200, 0x0, 0x0)
	/build/podman-qFWEMp/podman-1.3.2/src/github.com/containers/libpod/libpod/runtime.go:1114 +0x10d
main.infoCmd(0x243f7c0, 0x0, 0x0)
	/build/podman-qFWEMp/podman-1.3.2/src/github.com/containers/libpod/cmd/podman/info.go:60 +0xe8
main.glob..func64(0x23dcc60, 0xc4202da010, 0x0, 0x1, 0x0, 0x0)
	/build/podman-qFWEMp/podman-1.3.2/src/github.com/containers/libpod/cmd/podman/info.go:33 +0x87
github.com/containers/libpod/vendor/github.com/spf13/cobra.(*Command).execute(0x23dcc60, 0xc42003a130, 0x1, 0x1, 0x23dcc60, 0xc42003a130)
	/build/podman-qFWEMp/podman-1.3.2/src/github.com/containers/libpod/vendor/github.com/spf13/cobra/command.go:762 +0x468
github.com/containers/libpod/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0x23de420, 0x6, 0x24639a0, 0xc42019af00)
	/build/podman-qFWEMp/podman-1.3.2/src/github.com/containers/libpod/vendor/github.com/spf13/cobra/command.go:852 +0x30a
github.com/containers/libpod/vendor/github.com/spf13/cobra.(*Command).Execute(0x23de420, 0xc420702160, 0xc4200ac058)
	/build/podman-qFWEMp/podman-1.3.2/src/github.com/containers/libpod/vendor/github.com/spf13/cobra/command.go:800 +0x2b
main.main()
	/build/podman-qFWEMp/podman-1.3.2/src/github.com/containers/libpod/cmd/podman/main.go:142 +0x3e

thanks.
Something strange is happening here, I see "Not configuring container store"
it seems it is trying to use info without re-execing in the user namespace.  That should never happen with info

I see the issue, I've opened a PR here: https://github.com/containers/libpod/pull/3271


Migrate users into firestore

Change the flow of users registration and login to save data into firestore
What needs to be done to complete this task?

[x] Structure the new user collection
[x] Check user when signed with provider
[x] On new users, create and save minimun information
[x] On old users, do not save it.
[x] Create a service-like class to interact with Firestore as a REST CRUD.

There is a new UserService that uses Firestore functions, but the index and destroy method are not implemented as right now there is no need to do it.


Parse fixed joints from URDF

Some robot URDF files contain semantic information (wrist, ankle, sole, etc.) which is stored as a pair (fixed joint, empty link). For now, it seems such joints are not parsed in the robot structure, and thus cannot be used in control and/or planning.
Is there any computational limitation that would prevent storing the fixed joints, and computing their positions and jacobians whenever needed?

Currently fixed joints are handled in the way that the following link  parameters (inertia, mass..) are aggregated to its parent and/or repercuted to its children ( for relative position for exemple). But there is no entity called "fixed joint" for which we could perform these computations and adding this kind of joint as it in the kinematic chain may need some tricks i think
A solution would be to add a list a spot in the model (storing the parent joint, relative position to its parent, and its name) and then compute positions and jacobians when needed.
If it is ok for you, we may add it to future releases

This sounds like a good solution, thanks.

Hi,
Just a quick feedback on this point. I recently parsed a URDF model (tiago) with the devel branch of pinocchio. The URDF model contains tons of fixed frame and its works beautifully for my application.
So thanks a lot ! P.S. : I did not try the Jacobian computation.

#96 solves the issue. Closing.


What is the reason for this？

This problem occurs when I run with./ exploits. Sh
[*] Checking dependencies configuration
[ X ] Internet.............[ working ]

Check ur internet connection and then run the script again ....its simple

ye,thanks!


Set expires_in as number instead of string

As per spec https://tools.ietf.org/html/rfc6749#section-4.1.4 shows an integer, not a string.
and rfc6749 section 5.1 notes:
Parameter names and string values are included as JSON strings.
Numerical values are included as JSON numbers. The order of
parameters does not matter and can vary.

Changing expires_in to be as number

@keyurkarnik @gaonkar18y FYI

Any updates by when this will be available?


feat(header-navigation): add implementation

add header navigation implementation

it seems like the hamburger icon is not in the middle

also, for the menu should we use point cursor instead of the text?

it seems like the hamburger icon is not in the middle
@gergelyke
fixed

also, for the menu should we use point cursor instead of the text?
@gergelyke
Menu is used with it's own default styles, however I added cursor for better customization

are you planning to add tests in a separate PR?

yes, next commit

Tab links in the example are not keyboard navigatable. Could you fix it please?

Tab links in the example are not keyboard navigatable. Could you fix it please?

@nadiia fixed

Can you update the cursor to use the pointer style instead of text?

also, can you please add the warning that says that this component is in a beta state, and may change without notice in the near future?

Can you update the cursor to use the pointer style instead of text?

updated for the whole header navigation

also, can you please add the warning that says that this component is in a beta state, and may change without notice in the near future?

added in componentDidMount method for client-side warnings

can you please use the theme variables for the hamburger icon too?

can you please use the theme variables for the hamburger icon too?

fixed. @gergelyke

Deploy preview for baseui ready!
Built with commit 79438de18d4672bc3489d789dcb25a9f41aaa9e9
https://deploy-preview-525--baseui.netlify.com

Before merging please make sure that the Styled component wrapped in HOC behaves as a styled component in cases of restyling

added example for that


a crash occurs when drawing and erasing back and forth

Lorien version:
v0.5.0
OS/device including version:
Linux kernel version: 5.19.13
Linux distro: Arch
Window System: X11
RAM: DDR3 8GB RAM 1600MHz
CPU: Intel core i7-5500U 3.0GHz (2 cores / 4 threads)
Integrated GPU: Intel HD Graphics 5500 (Mesa)
Dedicated GPU: AMD Radeon R5 M330 (Mesa)
Issue description:
when drawing and erasing back and forth (switching between brush and eraser) it crashes and then a segmentation fault error appear in the terminal, it happens on both GPUs
Steps to reproduce:
grab a brush, try to draw a line
grab an eraser, erase the thing you drew
repeat until it crashes
what got printed into the terminal:

This is likely duplicate of #153, which was fixed after v0.5.0 release. @mbrlabs Maybe create v0.5.1 release with latest changes?

Yes, duplicate of https://github.com/mbrlabs/Lorien/issues/153. The next release will contain the fix. Thanks for reporting!


Isolated fix for Atlas viewer

Should fix #232
cc @bulbil

Can confirm this did update Atlas (and appears to be working)
There is a preview build:
https://ci.codesandbox.io/status/digirati-co-uk/iiif-canvas-panel/pr/238/builds/472080


fbgate interaction dont work.

Impossible enter on fbgate furnis.

Can  you post a screenie please?

Edit: Works Fine.

Impossible enter on fbgate furniture.
I think no bad coded, just packet error.
Video: http://tinypic.com/player.php?v=2wpo58o>&s=9#.V5syjxWLS70

Did you tried click directly in the gate?

Yes, and dont work ^^.

Sad. We will try to fix it in LINUX branch Release's. But, we are currently busy by rewriting the entirely Emulator..


spelling error; s/strenghts/strengths/

"strengths" is misspelled at
https://github.com/LambdaHack/LambdaHack/blob/master/Game/LambdaHack/Client/UI/InventoryM.hs#L55

Fixed. Thanks a lot!


Development

For the next development cycles.

Have on development main branch.
Have branches for features.
Merge features into development branch.
Merge development branch into main branch.

My current plan is to merge this branch in to the main branch because this branch IS already more than only for a new release, this branch is like a re-write of rusvid as a project.


feat: Add list_targets and add_file_to_targets to actions

Hi!
First of all, thank you for this amazing plugin. I'm having a lot of fun with it :)
I wanted to add files/directories non interactively via autocmds when creating new swift files so I added some small helper functions. Hopefully they are general enough.
However this is as far as I got, I couldn't get list_targets to return anything, even though it's identical to the call in run_select_targets. Perhaps you see something I don't? And if you like the changes we can merge them.

I wanted to add files/directories non interactively via autocmds when creating new swift files so I added some small helper functions. Hopefully they are general enough.

I refactored the code. Could you explain what you are trying to achieve with it? There is already some integration with nvim-tree to add files automatically :).

First of all, thank you for this amazing plugin. I'm having a lot of fun with it :)

Great to hear, thank you! 🍻

I refactored the code and fixed some bugs, I think in this form it could be merged.

Cool!

Could you explain what you are trying to achieve with it? There is already some integration with nvim-tree to add files automatically :). Are you working on some automation to generate some skeleton with multiple files?

Well done with the nvim-tree integration. I'm however not currently using nvim-tree, and unfortunately it doesn't match how I work.
You are absolutely right. I've ported my old vim-skeleton plugin from using Ultisnips to luasnips and am working to create some boilerplate generation for swift. Currently the automatic adding looks like this:
local function is_xcode_project(filepath)
  local lsp_util = require('lspconfig.util')
  return lsp_util.root_pattern('buildServer.json')(filepath)
    or lsp_util.root_pattern('*.xcodeproj', '*.xcworkspace')(filepath)
    or lsp_util.root_pattern('Package.swift')(filepath)
end

-- Automatically adds the file and group to XCode
vim.api.nvim_create_autocmd({ 'BufNewFile' }, {
  pattern = '*.swift',
  group = "srydell_swift",
  callback = function()
    local actions = require('xcodebuild.actions')
    local filepath = vim.fn.expand('%:p')
    if is_xcode_project(filepath) then
      actions.add_file_to_targets(filepath, actions.list_targets())
    end
  end,
})

What do you think? :)

Looks good! Ok, then I’m merging these changes. Make sure to adjust your calls, because I changed some names. Thank you for the first contribution 🍻


error in “Encode SIGSEP MUS to STEMS format ”

command line should be:
docker run --rm -v $(~)/data/ESTIMATE_DIR:/data faroit/sigsep-mus-io /scripts/encode.sh

thanks for that comment, do you want to make a pull request?

Uh I've already forgotten what this is. Can u help me setup?
On Wed, 15 Jul 2020, 10:22 weimisa341<EMAIL_ADDRESS>wrote:

command line should be:
docker run --rm -v $(~)/data/ESTIMATE_DIR:/data faroit/sigsep-mus-io
/scripts/encode.sh
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sigsep/sigsep-mus-io/issues/2, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIBEZJCHKYKLAU6J4B5BKODR3VRMXANCNFSM4O2JKQ7Q
.

no problem, I just fixed it myself. thanks again

Can u help me I have coffee for u
On Wed, 15 Jul 2020, 10:33 Fabian-Robert Stöter<EMAIL_ADDRESS>wrote:

no problem, I just fixed it myself. thanks again
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/sigsep/sigsep-mus-io/issues/2#issuecomment-658628427,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIBEZJESHPPSHXZ3NNJYEHTR3VSV7ANCNFSM4O2JKQ7Q
.


Improve time index validation

Minor fix converting an elif to if. In the current code, if the code paths related to index were taken, the elif to handle the time index wouldn't get called.
Our test case for this didn't check error message so it was passing. This has been updated. Also added another test related to another unchecked message.

Codecov Report

Merging #285 into master will increase coverage by 0.02%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #285      +/-   ##
==========================================
+ Coverage   94.44%   94.47%   +0.02%
==========================================
  Files          71       71
  Lines        7704     7708       +4
==========================================
+ Hits         7276     7282       +6
+ Misses        428      426       -2

Impacted Files
Coverage Δ

featuretools/entityset/entityset.py
93.82% <100%> (+0.18%)
:arrow_up:

featuretools/tests/entityset_tests/test_es.py
99.36% <100%> (ø)
:arrow_up:

featuretools/utils/gen_utils.py
70.58% <0%> (+1.96%)
:arrow_up:

Continue to review full report at Codecov.

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


Refactor ContentDigester and use ChecksummingTransferDecorator for Folo tracking checksums

This depends on a refactored ChecksummingTransferDecorator in Galley, but will eliminate the need to write the file then immediately reopen it and re-read it to calculate checksums. It should cut down on NFS load and potential for latent race conditions to be a problem, if there are any.

retest this please

retest this please

retest this please

retest this please


Suppress COVID data from Puerto Rico

Problem
According to Katrina's analysis, Puerto Rico's number of reported COVID cases is below our threshold compared to the NYtimes Data.
Solution
We should:

suppress the Puerto Rico COVID data
add it to the list of suppressed states in the disclaimers
change the text of the disclaimer to say "states and territories"

Based on Katrina's latest analysis, the data for Puerto Rico is complete enough that we do not need to suppress it:


tcp-reset is deprecated but still in docs

[Enter feedback here]
Option tcp-reset is still given in the document for LB annotation, but it doesn't work. Please update the doc accordingly.

root@piyush-gaur 17:42:02:$ kubectl version Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.2", GitCommit:"f5743093fd1c663cb0cbc89748f730662345d44d", GitTreeState:"clean", BuildDate:"2020-09-16T13:41:02Z", GoVersion:"go1.15", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.9", GitCommit:"a5e4de7e277a707bd28d448bd75de58b4f1cdc22", GitTreeState:"clean", BuildDate:"2021-11-16T01:09:55Z", GoVersion:"go1.15.14", Compiler:"gc", Platform:"linux/amd64"} root@piyush-gaur 17:42:21:$
root@piyush-gaur 17:42:56:$ cat ilb.yaml
apiVersion: v1
kind: Service
metadata:
name: internal-app
annotations:
service.beta.kubernetes.io/azure-load-balancer-internal: "true"
service.beta.kubernetes.io/azure-load-balancer-enable-high-availability-ports: "true"
service.beta.kubernetes.io/azure-load-balancer-disable-tcp-reset: "true"
spec:
type: LoadBalancer
loadBalancerIP: <IP_ADDRESS>
ports:

port: 80
selector:
app: internal-app
root@piyush-gaur 17:43:05:$

Connect with me at<EMAIL_ADDRESS>
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 60a7a0a8-97e7-0fda-763c-1a9972f4e9bc
Version Independent ID: 82b46441-43fc-fe48-97e2-0f3fca3d6eab
Content: Use a Public Load Balancer - Azure Kubernetes Service
Content Source: articles/aks/load-balancer-standard.md
Service: container-service
GitHub Login: @palma21
Microsoft Alias: jpalma

ilb.txt

Hi @blessedwithsins,
Thank you for your feedback. We will investigate the content to be modified and update the thread further.

@blessedwithsins
Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as
appropriate.
@palma21 - Please review this and share an update on this.

Hi, thank you for your contribution! We've just completed a full review and update of the Load Balancer doc, so I will be closing the issue. #please-close


rhash incorrectly outputs "Everything OK" when verifying embedded CRC32 checksums

Reproduction steps:
touch 'a [00000001]'
touch 'b [00000001]'
rhash -k 'a [00000001]' 'b [00000001]'

The rhash command prints out:
a [00000001]                                        ERR
b [00000001]                                        ERR
Everything OK

While the checksum errors are printed correctly for each file, the "Everything OK" summary is incorrect and confusing.
Version info:
rhash --version
RHash v1.4.0

Thank you for the bug report!
The bug is confirmed for versions 1.3.9-1.4.2 and for the latest sources code (no bug in versions <= 1.3.8).

Fixed by 5796c94b1eba4fb7407868555e630b409340b78e.

Thank you!

Fix included into RHash v1.4.3.