initial data inspection, missing data interpolation (unfinished), bas…

…eline model

I finished the interpolation (got stuck there for a while bc my fillna was filling in 0s where there should still be nans). Can update you on what i did and what were the issues i faced.
Did not do any validation bc I am struggling to figure out how since we have place x time data.


/bin/sh shells cannot read /etc/profile.d/path.sh

Description:
A script with header #/bin/sh -l or a user logging in with this shell will have a broken environment on ubuntu (22.04) as /bin/sh is a symlink to dash and dash cannot read the bash syntax in /etc/profile.d/path.sh

Affected versions
PC-version: 3.*

Thank you for reporting this!
I've create task to track this internally. We will assign someone to work on reviewing the PR and testing the changes
Thanks


fix name of AdoptOpenJDK

closes: https://github.com/AdoptOpenJDK/openjdk-build/issues/935

closing: fixing in the source code


WIP: Incorrect arg splitting when using .. syntax for git log

PR Summary
Fix #15279
PR Context
The current NativeParameterBinder (NPB) receives 2 distinct parameters from the parser which need to be combined, but does not as the following example shows:
PS> trace-command -PSHost -name param* { git diff $b..master }
DEBUG: 2023-08-21 13:39:51.0417 ParameterBinding Information: 0 : BIND NAMED native application line args [/usr/local/bin/git]
DEBUG: 2023-08-21 13:39:51.0503 ParameterBinding Information: 0 :     BIND cmd line arg [diff] to position [0]
DEBUG: 2023-08-21 13:39:51.0503 ParameterBinding Information: 0 :     BIND cmd line arg [Issue15279_3] to position [1]
DEBUG: 2023-08-21 13:39:51.0504 ParameterBinding Information: 0 :     BIND cmd line arg [..master] to position [2]
DEBUG: 2023-08-21 13:39:51.0614 ParameterBinding Information: 0 : CALLING BeginProcessing

While investigating this, i discovered other behavior which makes it difficult to interact with native executables. There are native applications which allow parameters to be expressed as -parm=value which can be very useful if you can use variables: -param=${param}.
Unfortunately, this is currently converted to:
> trace-command -pshost -name param* { echoit -foo=${thing} }
DEBUG: 2023-08-21 13:43:40.7358 ParameterBinding Information: 0 : BIND NAMED native application line args [/Users/james/bin/echoit]
DEBUG: 2023-08-21 13:43:40.7360 ParameterBinding Information: 0 :     BIND cmd line arg [-foo=$] to position [0]
DEBUG: 2023-08-21 13:43:40.7360 ParameterBinding Information: 0 :     BIND cmd line arg [-encodedCommand] to position [1]
DEBUG: 2023-08-21 13:43:40.7361 ParameterBinding Information: 0 :     BIND cmd line arg [dABoAGkAbgBnAA==] to position [2]
DEBUG: 2023-08-21 13:43:40.7361 ParameterBinding Information: 0 :     BIND cmd line arg [-inputFormat] to position [3]
DEBUG: 2023-08-21 13:43:40.7361 ParameterBinding Information: 0 :     BIND cmd line arg [xml] to position [4]
DEBUG: 2023-08-21 13:43:40.7361 ParameterBinding Information: 0 :     BIND cmd line arg [-outputFormat] to position [5]
DEBUG: 2023-08-21 13:43:40.7361 ParameterBinding Information: 0 :     BIND cmd line arg [xml] to position [6]
DEBUG: 2023-08-21 13:43:40.7509 ParameterBinding Information: 0 : CALLING BeginProcessing

The parser recognizes the -foo=$ as the parameter because of the opening brace, and then the minish treatment converts the second argument (which looks like a scriptblock) to a base64 encoded string. After this minishell conversion the NPB is called with these newly constructed parameters.
There is a work-around: using double quotes "-foo=${thing}" will properly pass the argument to the NPB, but this is somewhat difficult to discover after the case because the behavior is so unexpected and in most cases, the error just looks like you've used the command incorrectly.
The change does two things:

It changes the parsing of parameters to treat = similarly to : (but retains the = as a part of the parameter)
it combines parameters and arguments which have no space between them

There is a breaking behavior here:
Currently, it is possible to support parameters (in scripts, not in compiled code) which look like param (${z=p}).
for the function function zap { param (${p=z}); "p=z:" + ${p=z}; "args: " + $args }, the current behavior is
PS> zap -p=z arg!
p=z: arg!
args:

The new behavior is:
> zap -p=z arg!
p=z: -p=z
Args: arg!

the parameter is bound positionally rather than by the parameter name because -p=z is no longer recognized as a parameter, but an argument. Although I do not believe that this change will affect many (if any) current pwsh users.
Because e now re-parse a parameter with an = as an argument rather than parameter is the reason that the behavior when using a : is now:
> zap -p=z:arg!
p=z:-p=z:arg!
args:

the entire -p=z:arg! string is seen as a non-positional argument and is bound to the p=z parameter.
We can see this by inspecting the ASTs as follows:
Present:
PS>  { echo -p=one=1 }.Ast.FindAll({$true},$true) | ft {$_.GetType()},Extent

$_.GetType()                                                      Extent
------------                                                      ------
System.Management.Automation.Language.ScriptBlockAst              { echo -p=one=1 }
System.Management.Automation.Language.NamedBlockAst               echo -p=one=1
System.Management.Automation.Language.PipelineAst                 echo -p=one=1
System.Management.Automation.Language.CommandAst                  echo -p=one=1
System.Management.Automation.Language.StringConstantExpressionAst echo
System.Management.Automation.Language.CommandParameterAst         -p=one=1

and new:
PS>  { echo -p=one=1 }.Ast.FindAll({$true},$true) | ft {$_.GetType()},Extent

$_.GetType()                                                      Extent
------------                                                      ------
System.Management.Automation.Language.ScriptBlockAst              { echo -p=one=1 }
System.Management.Automation.Language.NamedBlockAst               echo -p=one=1
System.Management.Automation.Language.PipelineAst                 echo -p=one=1
System.Management.Automation.Language.CommandAst                  echo -p=one=1
System.Management.Automation.Language.StringConstantExpressionAst echo
System.Management.Automation.Language.StringConstantExpressionAst -p=one=1

This PR behavior is accessible by enabling the PSNativeParameterParsing Experimental feature.

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[ ] None
OR
[x] Experimental feature(s) needed

[x] Experimental feature name(s): PSNativeParameterParsing

User-facing changes

[ ] Not Applicable
OR
[x] Documentation needed

[ ] Issue filed:

Testing - New and feature

[ ] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:

[ ] Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
(which runs in a different PS Host).

[ ] Issue filed:

[ ] Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.

[ ] Issue filed:

[ ] Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).

[ ] Issue filed:

[ ] Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[ ] Issue filed:

@PowerShell/powershell-committee discussed this and agree with the new behavior regarding .. and =:

.. within an arg value will be a single argument with this change instead of two (previously).  This will be less surprising to users as there isn't a whitespace that would have indicated this would have been two args.
= previously script functions could use this character within a parameter name and with this change, the = character is treated as a delimiter separating the arg name and arg value.  This also seems unlikely to be used by existing script functions and was never allowed for C# cmdlets.

Overall, although a breaking change, we believe this is bucket 3 and improves the command-line experience overall so worth taking.


[Model Update]: bamm:io.catenax.fleet.diagnostic_data:1.0.0 to version 2.0.0 with SAMM

Update Reason
The use case quality group decided to upgrade this model to version 2.0.0:

Use new versions of ESMF toolings
Convert from BAMM to SAMM
Make adaptions in model structure

MS1 Criteria

[X] The model that should be updated exists
[X ] The referenced use case exists: It is use case CX QAX
[X] The potential updates are discussed with all stakeholders
[X] A decision on versioning was made in consensus with the affected parties according to the guidelines.
--> new version will be 2.0.0
[ ] The potential update will be either

[ ] backward compatible or
[X] a (chain of) migration strategy(-ies) from all non-deprecated previous versions to the new model will be developed

[ ] A modeling steward has been assigned

@modeling_team


[REVIEW] VaibhavUpreti

GitHub Profile Link
https://github.com/VaibhavUpreti

Hey @VaibhavUpreti great profile, here are some suggestion:
1.You can add some relatable cover

2.There are so many icons going on here can you make it look little neat or horizontal aligned.


feath: add doc method

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

Project coverage is 92.91%. Comparing base (ea1f4e0) to head (a64358a).

Files
Patch %
Lines

parser.go
78.94%
2 Missing and 2 partials :warning:

drivers/tag/tag.go
0.00%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main       #3      +/-   ##
==========================================
+ Coverage   92.88%   92.91%   +0.03%
==========================================
  Files          10       10
  Lines         253      367     +114
==========================================
+ Hits          235      341     +106
- Misses         17       22       +5
- Partials        1        4       +3

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


[NT-0] refac: Refactor Org test accounts

I have made the following quality of life improvements to remove the requirement to create/add new org test accounts to the test_account_creds.txt file:

I have reverted the test_account_creds.txt so that it only requires the default and alt email address and password information.
I have reduced the Organization test account requirements down to a single test account with the member and admin roles.
I have introduced a new organization_test_account_creds.txt file which contains the credentials for this new test account.
I have updated the Functional Test TeamCity deployment steps to account for this.

For the reviewer

[ ] If required, are the changes covered by appropriate tests?
[ ] Are any public-facing API changes well documented?
[ ] Is the code easily readable and extensible and/or follow existing conventions?

Why do we need 3 test accounts for this? I would much rather we not introduce another test accounts txt file requirement and just use the existing 2 accounts.

We can't do that unfortunately. We need an account that belongs to the organization and has at least admin privileges so that they can perform organization operations such as invite other members. We can also not grant one of existing accounts that role as part of the test as they need to be invited by another user who is an admin, owner or superuser.


Migrate to GitHub Actions

Beginning of November 2020, Travis CI introduced a new pricing model which in practice stops providing unlimited hours to open source projects. In only few weeks, pysteps ran out of its allocated hours (which are not renewable). For this reason, we have decided to migrate to GitHub Actions, since this still offers unlimited hours to public repositories.

The black test is failing, but I suggest we reformat the code separately once all the remaining pull requests are merged, right before releasing v1.4,

Did the tests fail, when you tried python 3.9?

Did the tests fail, when you tried python 3.9?

For py39 there were conflicts during the creation of the conda environment and the tests failed. I think that maybe we should wait a little bit until the packages dependencies are updated in conda-forge for the windows build.
Once we can build the conda environment in windows, we could replace 3.8 with 3.9. In that way we test the minimum required python version and the latest version.

Great work on this short notice, @dnerini and @aperezhortal! Looks like we only have to make some code adjustments (later) to successfully pass the Black test, right?

I  included the black tests to check that the code base is compliant with the latest black version. Black is changing quite frequently so this can be used to indicate that we need to update black in our local development environment.
Once we merge this PR, we can run black and push the changes to the main branch directly.

Did the tests fail, when you tried python 3.9?

For py39 there were conflicts during the creation of the conda environment and the tests failed. I think that maybe we should wait a little bit until the packages dependencies are updated in conda-forge for the windows build.
Once we can build the conda environment in windows, we could replace 3.8 with 3.9. In that way we test the minimum required python version and the latest version.

Agreed. Btw, we have the same issue with the PR on our conda-forge pysteps-feedstock: https://github.com/conda-forge/pysteps-feedstock/pull/11

should we add a pylint workflow?

I was thinking about this too. Now we have several pep8 on the codebase and pylint gives a very detailed report on the code (that means, it will point out several violations). I think that we can postpone the pylint checks for a little while and perhaps start with some flake8 checks on future PRs. Adding and fixing one or a few types of errors at each PR.
Once the codebase passes many flake8 tests, we can certainly add pylint.


Running web request and heavy computing at same time

Is your feature request related to a problem? Please describe.
I thought snakemake sees the computing necessity of tasks, and if they can be run simultaneously, will attemp to do so, dividing the resources as needed. I have, in my pipeline, two tasks that should be run at same time: a request using UPIMAPI to retrieve information from UniProt - which takes a lot, because must respect the limits of the API, but takes little computation effort, and a functional annotation using reCOGnizer - which is multithreaded, so computationally intensive.
Describe the solution you'd like
I would like for there to be a way both tasks can be run simultaneously, so UPIMAPI's requests can take their time while reCOGnizer works hard on those protein sequences.
Describe alternatives you've considered
I though snakemake did this by default, considering the cores not being used by UPIMAPI, and allocating them to reCOGnizer.

Can you show the snakemake spell you are using? And the Snakefile you are using? Snakemake definitely permits parallel execution of rules.

This may have already been solved by setting threads information, since that is likely what snakemake uses to determine computation usage. Have not tested it yet, however. Now, the Snakefile already has that information explicit. Where max threads are now 1, there was no information before.

I can't predict behavior without knowing the actual snakemake command you are running. Seems like your snakefile is fine. If you aren't careful, you will set "-j" to be equal to "config['threads']". If you do, than any time a job uses "config["threads"]" threads, there will be no cores left to run any other job at the same time.

Exactly, that was what I was always doing! xD Will have to test it now, to see if it working as intended


EpicsMotor alarm fails to trigger FailedStatus

We can see (using caproto!) that the motor alarm goes high but ophyd doesn't raise FailedStats. Need more interactive debugging at SIX to sort this out.

What PV is the alarm on?
We only check the alarm state on the user readback
https://github.com/NSLS-II/ophyd/blob/f1c0710217e3c95f5eb9cb700e1ef9fd66b065b5/ophyd/epics_motor.py#L253-L260

@danielballan Would you mind describing what is the situation that causes it?
Also, as @tacaswell which PV is the one that you mentioned?
https://www3.aps.anl.gov/bcda/synApps/motor/R6-9/motorRecord.html#Fields_alarm

Cut power to motor.
Ask ophyd to move motor.
Ophyd reports success.

Get Outlook for iOShttps://aka.ms/o0ukef
On Thu, Oct 26, 2017 at 7:33 PM -0400, "Hugo Slepicka" <notifications<EMAIL_ADDRESS>wrote:
@danielballanhttps://github.com/danielballan Would you mind describing what is the situation that causes it?
Also, as @tacaswellhttps://github.com/tacaswell which PV is the one that you mentioned?
https://www3.aps.anl.gov/bcda/synApps/motor/R6-9/motorRecord.html#Fields_alarm
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/NSLS-II/ophyd/issues/449#issuecomment-339829306, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACLIri1nUNXlL9mtj2-YSFLIPddWJ_E9ks5swRVvgaJpZM4P9n1g.

Cut power to motor you mean turn off the motor controller? Shutdown the
IOC? What is the case?
Which alarm do you see raised?
On Thu, Oct 26, 2017 at 5:34 PM Dan Allan<EMAIL_ADDRESS>wrote:

Cut power to motor.
Ask ophyd to move motor.
Ophyd reports success.

Get Outlook for iOShttps://aka.ms/o0ukef
On Thu, Oct 26, 2017 at 7:33 PM -0400, "Hugo Slepicka" <
notifications<EMAIL_ADDRESS>wrote:
@danielballanhttps://github.com/danielballan Would you mind describing
what is the situation that causes it?
Also, as @tacaswellhttps://github.com/tacaswell which PV is the one
that you mentioned?
https://www3.aps.anl.gov/bcda/synApps/motor/R6-9/motorRecord.html#Fields_alarm
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<
https://github.com/NSLS-II/ophyd/issues/449#issuecomment-339829306>, or
mute the thread<
https://github.com/notifications/unsubscribe-auth/ACLIri1nUNXlL9mtj2-YSFLIPddWJ_E9ks5swRVvgaJpZM4P9n1g

.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/NSLS-II/ophyd/issues/449#issuecomment-339839328, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHzmUTlEig1EQsRY55-_cVDumee2KmeCks5swSUZgaJpZM4P9n1g
.

The controller. The IOC stays online.
Get Outlook for iOShttps://aka.ms/o0ukef
On Thu, Oct 26, 2017 at 9:08 PM -0400, "Hugo Slepicka" <notifications<EMAIL_ADDRESS>wrote:
Cut power to motor you mean turn off the motor controller? Shutdown the
IOC? What is the case?
Which alarm do you see raised?
On Thu, Oct 26, 2017 at 5:34 PM Dan Allan<EMAIL_ADDRESS>wrote:

Cut power to motor.
Ask ophyd to move motor.
Ophyd reports success.

Get Outlook for iOShttps://aka.ms/o0ukef
On Thu, Oct 26, 2017 at 7:33 PM -0400, "Hugo Slepicka" <
notifications<EMAIL_ADDRESS>wrote:
@danielballanhttps://github.com/danielballan Would you mind describing
what is the situation that causes it?
Also, as @tacaswellhttps://github.com/tacaswell which PV is the one
that you mentioned?
https://www3.aps.anl.gov/bcda/synApps/motor/R6-9/motorRecord.html#Fields_alarm
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<
https://github.com/NSLS-II/ophyd/issues/449#issuecomment-339829306>, or
mute the thread<
https://github.com/notifications/unsubscribe-auth/ACLIri1nUNXlL9mtj2-YSFLIPddWJ_E9ks5swRVvgaJpZM4P9n1g

.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/NSLS-II/ophyd/issues/449#issuecomment-339839328, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHzmUTlEig1EQsRY55-_cVDumee2KmeCks5swSUZgaJpZM4P9n1g
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/NSLS-II/ophyd/issues/449#issuecomment-339843860, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACLIrv3IPzAMXaBUJIyfJmx4i6t81Tlqks5swSz8gaJpZM4P9n1g.

We need access to a real motor controller / IOC to work on this, punting to next cycle.

anybody interested in picking this back up? we can schedule some time to test during the shutdown at the beamline this was found at.

Tentatively yes. We are struggling to use current ophyd master in production, period, and we need to resolve that first before we can build changes like this one on top. Can we schedule the time and use it both to take ophyd master through its paces and (if that goes well) work on alarms?


feat(tabs): removable tabs

Enlarge Tabs component with possibility to remove tabs.
Demo page and Readme file, updated.

Updated request with new commit, check please

Looks good, please squash commits and force push to your local branch

Done, Thanx for your time.

LGTM!


Auto-complete of @ in extension sidebar stops working when text is deleted from search box

Having initially reported #46333, I was eager to test the functionality that was implemented in #53915. I came across the following issue that doesn't sound like desirable/intentional behavior.

VSCode Version: 1.26.0
OS Version: Ubuntu 16.04.5 LTS

Steps to Reproduce:

Open the extension sidebar.
Type @ in the search box. An auto-complete menu appears with several possible options (@builtin, @disabled, etc.)
Type or pick one of the options, e.g. @builtin. A list of extensions is shown below.
Select all the text in the box except the @, and delete it

Expected behavior: the initial list of available keywords should appear again.
Actual behavior: The autocomplete list is not shown, and the extension sidebar shows simply "No extensions found."

Does triggering suggestions cause the list to appear again? This is ctrl+space be default.

Testing on 1.26 just now I'm seeing that simply deleting to the @ does not trigger suggestions, but pressing ctrl+space from there does show the suggestions again. This is as designed, it works the same in the editor: if you type this. suggestions will appear, but if you delete until the period, the wont appear.
As a side note, you actually don't need to type the @ at all; you can use ctrl+space from the empty search box or any word boundary within the query and it will show suggestions. The @ is simply what we call a trigger character, which means the act of typing it forces suggestions to show, but the act of deleting something up until it does nothing.

Does triggering suggestions cause the list to appear again? This is ctrl+space be default.

Yes, it does.


feat(website): RPC connect Metamask Networks

Modified:
https://github.com/taikoxyz/taiko-mono/pull/14068
to not have the Metamask pnpm package to handle the
window.ethereum

object.
Instead
(window as any).ethereum

is used to keep things simple for package dependencies.

final comment. i see this was added to RPC configuration, which is great. however, i can't help but to feel, is RPC configuration a duplicate of: https://website-lyc4taqy3-taikoxyz.vercel.app/docs/guides/configure-your-wallet ? Should we add it to configure your wallet as well or somehow consolidate the two? Should configure your wallet guide just be a link to RPC configuration? i think any of these are fine, at the least maybe we just add it to configure-your-wallet

I think we should redirect the wallet connection page to the RPC connection page based on links on the wallet connection page.


"Area IFS4 (IFS) - left hemisphere" of Julich Brain 2.9 in BigBrain is showing "Area IFS4 (IFS) - right hemisphere"

This is a configuration issue. It is fixed with https://jugit.fz-juelich.de/t.dickscheid/brainscapes-configurations/-/commit/1ed2de5f81377833df91b19d430dd5d751251b34, however, this will be available with the next siibra-python release (0.4a85).

Configuartion is updated https://jugit.fz-juelich.de/t.dickscheid/brainscapes-configurations/-/tags/siibra-0.4a85. Next siibra-explorer release will include this fix.


'Book Now' and 'Explore More' button functional

Fixes: https://github.com/PriyaGhosal/BuddyTrail/issues/172
Fixes: https://github.com/PriyaGhosal/BuddyTrail/issues/171
Description
I have now made the 'Book Now' and 'Explore More' button functional, as it previously wasn’t working for every deal. I created a new webpage for each deal, as each one has different requirements. A reference video is provided below, showing the changes made.
Please make sure to add label 3 for both pr.
https://github.com/PriyaGhosal/BuddyTrail/issues/172 completed
https://github.com/PriyaGhosal/BuddyTrail/issues/171 completed
Type of PR
[ x] Feature enhancement
Screenshots / videos (if applicable)
Book now button is working (https://github.com/PriyaGhosal/BuddyTrail/issues/172 )

Explore More button is working(https://github.com/PriyaGhosal/BuddyTrail/issues/171 )
https://github.com/user-attachments/assets/aab2eff1-b0bc-4369-b2b4-62f671b0eeca
Checklist:
[ x] I have made this change from my own.
[x ] My code follows the style guidelines of this project.
[ x] I have performed a self-review of my own code.
[ x] I have commented my code, particularly in hard-to-understand areas.
[ x] I have made corresponding changes to the documentation.
[ x] My changes generate no new warnings.
[ x] I have tested the changes thoroughly before submitting this pull request.
[ x] I have provided relevant issue numbers and screenshots after making the changes.

@PriyaGhosal don't merge it right now i am resolving these conflicts i will let yk then merge it please

@INam1995 Can you tell me how can I deploy the project in my local machine, I have successfully forked this repository

@INam1995

Please see the conflicts . Resolve the conflicts . Ensure you pull all the latest changes before pushing your feature/bug fixes to the main branch. After resolving the conflicts, please open a new PR for review.
Thank you!


network-rule command not working

here is the error I am seeing - az keyvault: 'network-rule' is not an az keyvault command. See 'az keyvault --help'
az --version is "azure-cli (2.0.38)"

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

ID: caa4484b-7b01-45d5-4d5c-61f274395eac
Version Independent ID: de5c4486-080b-6406-5dcb-febd66a5a626
Content: az keyvault network-rule
Content Source: latest/docs-ref-autogen/ext/keyvault-preview/keyvault/network-rule.yml
Service: key-vault
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

This might be a feature in the KeyVault extension. @schaabs can you verify?

@rameshjanjyam This feature is currently only supported in the keyvault-preview extension. To install the extension run the command
az extension add -n keyvault-preview

You can get more info on the extension, as well as file any issues here.  We are currently in the process of releasing the features in the preview extension, so they should be available in a standard install of the CLI in July.

awesome. it worked. Thank you very much @schaabs and @tjprescott


add backup test

Description
test backup and restore VDC
Changes
Related Issues
https://github.com/threefoldtech/js-sdk/issues/2695
Checklist

[ ] Pre-commit hook is installed to do formatting checks before committing code...etc
[ ] Tests included
[ ] Build pass
[ ] Documentation
[ ] Code format and docstrings

Please add a screenshot for running this test.

Codecov Report

Merging #2760 (fe3594b) into development (c0dd169) will decrease coverage by 25.72%.
The diff coverage is 26.35%.

@@               Coverage Diff                @@
##           development    #2760       +/-   ##
================================================
- Coverage        58.75%   33.02%   -25.73%
================================================
  Files              218      192       -26
  Lines            19935    18149     -1786
================================================
- Hits             11713     5994     -5719
- Misses            8222    12155     +3933

Impacted Files
Coverage Δ

jumpscale/clients/stellar/__init__.py
50.84% <ø> (-8.48%)
:arrow_down:

jumpscale/packages/vdc_dashboard/bottle/backup.py
23.17% <0.00%> (ø)

...umpscale/packages/vdc_dashboard/chats/discourse.py
45.45% <ø> (ø)

...le/packages/vdc_dashboard/chats/monitoringstack.py
60.97% <ø> (-31.89%)
:arrow_down:

...umpscale/packages/vdc_dashboard/services/domain.py
10.84% <0.00%> (-0.27%)
:arrow_down:

...ale/packages/vdc_dashboard/services/etcd_backup.py
29.62% <0.00%> (-2.38%)
:arrow_down:

jumpscale/sals/vdc/kubernetes.py
7.43% <ø> (-42.11%)
:arrow_down:

jumpscale/sals/vdc/s3_auto_topup.py
13.71% <0.00%> (-36.00%)
:arrow_down:

jumpscale/sals/vdc/threebot.py
15.38% <ø> (-37.61%)
:arrow_down:

...mpscale/packages/threebot_deployer/bottle/utils.py
9.32% <6.25%> (-72.35%)
:arrow_down:

... and 144 more

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 cd2a9a4...fe3594b. Read the comment docs.

the test fail when try reaching to the cryptpad after restore (the wait time is 600 seconds)
https://github.com/threefoldtech/js-sdk/runs/2287298999?check_suite_focus=true#step:6:716


403 (unauthorized) with authorized account

I'm trying to use the example code for the sdk with the api-key and secret I got on my profile on censys.io. however I get the following error:
Traceback (most recent call last):
  File "main.py", line 10, in <module>
    res = c.new_job("select count(*) from certificates.certificates")
  File "/venv/lib/python2.7/site-packages/censys/query.py", line 13, in new_job
    return self._post("query", data=data)
  File "/venv/lib/python2.7/site-packages/censys/base.py", line 111, in _post
    return self._make_call(self._session.post, endpoint, args, data)
  File "/venv/lib/python2.7/site-packages/censys/base.py", line 105, in _make_call
    const=const)
censys.base.CensysUnauthorizedException: 403 (unauthorized): Unauthorized. You do not have access to this service.

It actually worked for the direct API urls using this code:
	import sys
	import json
	import requests

	API_URL = "https://www.censys.io/api/v1"
	UID = "_UID_"
	SECRET = "_SECRET_"

	res = requests.get(API_URL + "/data", auth=(UID, SECRET))
	if res.status_code != 200:
	    print "error occurred: %s" % res.json()["error"]
	    sys.exit(1)
	for name, series in res.json()["raw_series"].iteritems():
	    print series["name"], "was last updated at", series["latest_result"]["timestamp"]


License to WTFPL

License the code to WTFPL, #16

closing this since MIT license is already present


FootState calculation

Hi there,
I'm testing quad-sdk on hardware, but there's a problem that's been troubling me. The FootState calculated by robot_driver occasionally goes wrong and the z position of the feet becomes negative, has anyone encountered a similar problem?
I read the paper and know how the foot position is calculated, does this phenomenon imply that I have to switch to a more stable method of estimating the foot position?

Is this data with online state estimation or external (i.e. mocap)? The foot position calculation should be pretty reliable (assuming your kinematics match the actual robot, so I'll assume that is a Spirit for now), but since the foot position data is in the world frame it is affected by the state estimation and any drift present.

Is this data with online state estimation or external (i.e. mocap)? The foot position calculation should be pretty reliable (assuming your kinematics match the actual robot, so I'll assume that is a Spirit for now), but since the foot position data is in the world frame it is affected by the state estimation and any drift present.

Hi Joe,
Thank you very much for your reply!
I didn't use online state estimation. I used T265 tracking camera to publish the mocap topic, to get the position and orientation of the robot body, and for IMU I used LPMS-IG1.
I did not test with Spirit robot or Unitree's A1 robot, but I made sure I used the correct URDF model and also generated the dynamics model with a matlab script.
I noticed that Robomechanics Lab posted a test video on YouTube where the robot is moving outdoors, is it using the T265 camera as well?

Hi @jrenaf
Many thanks for the advice! :)
I tested with a standalone PC running the quad-sdk controller as ROS slave and the robot running ROS Master. They are connected with a CAT-6 cable.
The signals from the T265, IMU and encoder are sent to the PC as separate topics. We were aware of the possibility of delays, but didn't think it would be a serious problem. Later we will try to transmit these signals directly by means of the UDP protocol.

Closing this issue due to lack of activity, also seems like a implementation-specific issue (correct me if wrong). Also t265 data is known to drift quite a bit and particularly during locomotion, and that seems to be what is happening here (10cm of drift over 5 seconds makes sense).
That said, better state estimation/robot frame controls are certainly in the works, so this may be included in a future update.


allow for user configured aliases

@mambocab & @ptnapoleon: please review.
Just a little tweak. I'm trying to allow users to define aliases of git urls in a configuration file. Seems easier than -v git:smccarthy788/cassandra-fork every time.
Config files should look like
alias_name = some.git.url

be located at .ccm/config, and can be used as ccm create -v alias:alias_name ...

At ~/.ccm/config, you mean?

Maybe we should make it a .ini formatted file, with an [alias] section, for future proofing? There should be a python library that handles that

I think we can drop the explicit need for alias? When we receive a slug that we don't know how to handle, we can just check the user specified aliases, rather than making the user explicitly mark it as an alias. You can just make it an else check instead of an elif. You'll have to move the version in 'stable', 'oldstable block higher up, though

@ptnapoleon, we could not be explicit about alias, but since so many other parts of ccm touch repository.py we either end up printing something like alias not found in config file everytime we run ccm status | start | remove | etc., or we increase scope, and refactor repository.py.
The problem is we need something to specify we're trying to use alias. When we call setup() to do something other than actually setup the cluster, it counts on the fact that the version passed doesn't start with any of git: local: binary: etc., but that's also what you're trying to do by not specifying alias:, so setup() falls into just returning the cluster directory and version name.
It's easy enough to always check the config file for the alias, but if the alias isn't there (as is the case when running start() ), I have to catch ConfigParser.NoOptionError. Since we can't determine if we're trying to actually setup a cluster or just get the cluster directory, handling the error is just to print a warning. If we're trying to setup a cluster and we don't find the alias, it will end up just falling into the default 'download cassandra from git', which is also not what we want.

Sounds like we're using alias: explicitly until we refactor this, then

This lgtm. @mambocab ?

Smoke tested it locally, works for me, doesn't break the git: slug. +1.


Smart Nested Populate, self relation

Hello I have an entity that has a relationship with the pk itself:
A category can have a category as a parent, and a category has a collection of sub categories
@Entity({ tableName: 'product_categories' })
export class ProductCategory {
  @PrimaryKey()
  public readonly id: string;
  @ManyToOne(() => ProductCategory, {
    nullable: true,
    fieldName: 'parent_id',
  })
  public parent: ProductCategory;
  @Property()
  public name: string;
  @OneToMany(() => Product, product => product.category)
  public products = new Collection<Product>(this);
  @OneToMany({
    entity: () => ProductCategory,
    mappedBy: 'parent',
    orphanRemoval: true,
  })
  public parents = new Collection<ProductCategory>(this);
  @Property()
  public created_at = new Date();
  @Property({ onUpdate: () => new Date() })
  public updated_at = new Date();
  @Property()
  public deleted_at?: Date;

  constructor(container: categoryContainer) {
    this.id = container.id ? container.id : v4();
    this.name = container.name;
    if (container.parent) this.parent = container.parent;
  }
}

my repository:
  public byId = async (id: string): Promise<ProductCategory | undefined> => {
    const category = await this.repository.findOne(
      { id },
      { parents: LoadStrategy.JOINED },
    );
    if (!category) return;
    return category;
  };

for some reason I can load my collection correctly, but when I use getItems / load items it doesn't load:
  private validateParent = async (parent_id: string) => {
    const parent = parent_id
      ? await this.categoryRepository.byId(parent_id)
      : null;
    if (parent === undefined) {
      throw new Error('Parent Category Dont Exists.');
    }
    return parent;
  };

  public execute = async ({
    name,
    parent_id,
  }: CreateProductCategoryDTO): Promise<Either<AppError, ProductCategory>> => {
    const hasCategory = await this.categoryRepository.byCategoryName(name);
    if (hasCategory) return left(new Error('Category Already Exists.'));
    const parent = parent_id ? await this.validateParent(parent_id) : null;
    const category = await this.categoryRepository.create(
      ProductCategory.build({ name, parent }),
    );
    console.log(await category.parents.loadItems())
    return right(category);
  };

my getItems / load returns an empty array, but if I give a console.log in the instance of my entity I can see the collection as in the following print:

You need to mark the collection as populated to have it as part of the serialized response. Ideally you should use populate parameter when loading the entity, or em.populate() afterwards.

You need to mark the collection as populated to have it as part of the serialized response. Ideally you should use populate parameter when loading the entity, or em.populate() afterwards.
https://mikro-orm.io/docs/nested-populate/#populating-already-loaded-entities
Or mark it explicitly:
await category.parents.loadItems();
category.parents.populated();

i make this here:
  public byId = async (id: string): Promise<ProductCategory | undefined> => {
    const category = await this.repository.findOne(
      { id },
      { populate: {parents: LoadStrategy.JOINED} },
    );
    if (!category) return;
    return category;
  };

would it be the same thing?
or do i need to do something in the insertion too?
  public create = async (
    category: ProductCategory,
  ): Promise<ProductCategory> => {
    if (!(category instanceof ProductCategory))
      throw new Error(`Invalid Data Type`);
    await this.repository.persist(category).flush();
    return category;
  };

my getItems / load returns an empty array, but if I give a console.log in the instance of my entity I can see the collection as in the following print:

Mmm I missed this sentence. What getItems() returns is definitely correct - if it gives you empty array, the collection is empty. What you see in the console might not be accurate, as that is not the list of entities, it's the indexed array accessors (so we can do coll[1] to access second element of the collection) and they might be out of sync for some reason.
I was wrong with the previous hint about explicit population - even without that, the collection would be still part of the responses. Loaded collections are always there, without population they will be array of PKs, if you populate them, you will have array of entities. And you have empty array, that means the collection is empty.

my getItems / load returns an empty array, but if I give a console.log in the instance of my entity I can see the collection as in the following print:

Mmm I missed this sentence. What getItems() returns is definitely correct - if it gives you empty array, the collection is empty. What you see in the console might not be accurate, as that is not the list of entities, it's the indexed array accessors (so we can do coll[1] to access second element of the collection) and they might be out of sync for some reason.
I was wrong with the previous hint about explicit population - even without that, the collection would be still part of the responses. Loaded collections are always there, without population they will be array of PKs, if you populate them, you will have array of entities. And you have empty array, that means the collection is empty.

omg my bad i made a mess in fact my parent relationship that has the populated parents collection.
@B4nan thaks u

Looking more into your code, this part does not make sense:
const category = await this.categoryRepository.create(
      ProductCategory.build({ name, parent }),
    );
    console.log(await category.parents.loadItems())

Calling loadItems() will load the collection state from database, but your entity is not yet persisted anywhere, you just created its instance. You can get current collection items via getItems() instead, without making any database query.

~Looking more into your code, this part does not make sense:~
const category = await this.categoryRepository.create(
      ProductCategory.build({ name, parent }),
    );
    console.log(await category.parents.loadItems())

~Calling loadItems() will load the collection state from database, but your entity is not yet persisted anywhere, you just created its instance. You can get current collection items via getItems() instead, without making any database query.~
edit: or maybe not, my bad, it will not make a query as the collection is initialized, this approach is fine

Hello could you help me with this?
I have a table to represent an n: n relationship, but it is getting complicated because I have to create an entity for each relationship,
i would like to know if i could just create with id?
@Entity({ tableName: 'supplied_products' })
export class SuppliedProducts {
  @ManyToOne(() => Product,{ primary: true, fieldName:'product_id' })
  public product!: ReferecedProduct;
  @ManyToOne(() => Supply,{ primary: true, fieldName:'supply_id' })
  public supply!: Supply;
  @Property()
  public unit_price: number;
  @Property()
  public quantity: number;
  @Property()
  public created_at = new Date();
  @Property({ onUpdate: () => new Date() })
  public updated_at = new Date();
  @Property()
  public deleted_at?: Date;
  [PrimaryKeyType]: [number, number];
  constructor(container:SuppliedProductsProps) {
    this.quantity = container.quantity
    this.product = container.product
    this.supply = container.supply
    this.unit_price = container.unit_price
  }
  public static build = (
    {supply,quantity,product, unit_price}:SuppliedProductsProps
  ): SuppliedProducts => {
    if (!(supply instanceof Supply)) throw new Error(`Invalid Supply Type`);
    if (!(product instanceof Product)) throw new Error(`Invalid Product Type`);
    return new SuppliedProducts({product, supply, quantity, unit_price});
  };
}

now i have this:
const supplyResult = Supply.build(supply, hasContract);
    supplyResult.suppliedProducts.set(
      suppliedProducts.map(supplied => {
        return SuppliedProducts.build({
          product: ensure(hasProducts.find(x => x.id == supplied.product_id)),
          quantity: supplied.quantity,
          supply: supplyResult,
          unit_price: supplied.unit_price
        });
      }),
    );

i want like this:
const supplyResult = Supply.build(supply, hasContract);
    supplyResult.suppliedProducts.set(
      suppliedProducts.map(supplied => {
        return SuppliedProducts.build({
          product: supplied.product.id,
          quantity: supplied.quantity,
          supply: supplyResult.id,
          unit_price: supplied.unit_price
        });
      }),
    );

that is, instead of the relationship being an entity, just being an id that references the entity


Show in menubar has no effect  - macOS Ventura

I have the application set to hide the icon in the menu bar, but regardless of the setting, the icon persists.
Restart has no effect.

M1 Macbook Pro

Hi, @polloralph!
Thank you for your feedback.
Maybe duplicates of #271.

@lujjjh Can confirm, was a duplicate of #271, I also have a m1 macbook pro, and the issue was resolved after updating to 0.7.5.


Add depfile output flags to dart compile

The Dart SDK internal binaries, such as gen_snapshot support a depsfile output:
https://github.com/dart-lang/sdk/blob/a3c6d0569702e8cd5da693f0235b79dbdd38cfa7/runtime/bin/main_options.cc#L794
The Flutter tool, and Flutter engine, use this option to correctly rebuild from various build systems.
It would be nice to have this available in dart compile so that Dart SDK internal binaries are (less?) not needed.

Ben to add some context to this request as well: https://github.com/flutter/flutter/issues/155769. Thanks!


Set JAX_PLATFORMS=tpu,cpu on TPUs

Set JAX_PLATFORMS=tpu,cpu automatically if libtpu is installed.
It would make JAX raise an error if TPU cannot be initialized instead of falling back to CPU.
Tests:

Run test file below on a non-TPU platform, it throws Unable to initialize backend 'tpu': NOT_FOUND error
Run test file below on a non-TPU platform with export JAX_PLATFORMS=cpu, and it runs with CPU (No GPU/TPU found, falling back to CPU).

import jax
import os
import time

for i in range(5):
    print("checking...")
    print(os.environ.get('JAX_PLATFORMS'))
    print(jax.devices())
    time.sleep(10)

We should make sure it's possible for users to manually override to the default behavor (i.e. preferring TPU if available, but falling back to CPU if not). Can you test that manually setting JAX_PLATFORMS= (empty string) causes it to pickup the default behavior? I'm not totally sure if this will work, it might override the empty string (vs. just overriding if it's not set at all).
We might also wanna provide some guidance in the error message for users who hit this. I'm not totally sure how best to do this. Maybe add to err_msg here: (Set JAX_PLATFORMS='' to auto fallback to CPU or JAX_PLATFORMS=cpu to always use CPU) or something like that? You should test it out and make sure it looks reasonable.

Sure! Added changes for error message.

Ran test file on a non-TPU platform with both export JAX_PLATFORMS='' and export JAX_PLATFORMS= separately, and it executed with CPU (No GPU/TPU found, falling back to CPU).
Ran test file on both non-TPU and TPU platforms with export JAX_PLATFORMS=ccc, and got error message below.

Traceback (most recent call last):
  File "/usr/local/google/home/ranran/jax/jax_test.py", line 8, in <module>
    print(jax.devices())
  File "/usr/local/google/home/ranran/jax/jax/_src/lib/xla_bridge.py", line 487, in devices
    return get_backend(backend).devices()
  File "/usr/local/google/home/ranran/jax/jax/_src/lib/xla_bridge.py", line 429, in get_backend
    return _get_backend_uncached(platform)
  File "/usr/local/google/home/ranran/jax/jax/_src/lib/xla_bridge.py", line 413, in _get_backend_uncached
    bs = backends()
  File "/usr/local/google/home/ranran/jax/jax/_src/lib/xla_bridge.py", line 354, in backends
    raise RuntimeError(err_msg + setup_msg)
RuntimeError: Unable to initialize backend 'ccc': Unknown backend 'ccc'(Set JAX_PLATFORMS='' to auto fallback to CPU or JAX_PLATFORMS=cpu to always use CPU)

Oops two more things: update the CHANGELOG, and fix the lint error


spec file extension is case sensitive

On Windows, the .spec extension is case sensitive.  Files without .spec as the extension are not seen as specs that can be run.  Example:   .Spec instead of .spec
This caused confusion as the IntelliJ plugin sees .Spec as a valid Gauge spec for the plugin, but the run command does not see the file as a spec.
Other OSes have not been tested - I think OS X handles file case sensitivity different than Windows does.
Expected behavior
Any case combination of .spec will be run by Gauge (EG:  .spec, .Spec, .SPEC, .SpEc, etc) provided the file matches the arguments passed to the run command.
Actual behavior
Running a spec with a file extension other than .spec, gives No specifications found in {supplied path to specs}
If a directory is passed as the spec path, then only specs with extension .spec are run.
Steps to reproduce

Make a new directory
Run gauge init java in the new directory
In new directory\specs, copy example.spec to example2.Spec
Open a command prompt to the new directory
Run gauge run specs\example2.Spec
Observe message No specifications found in specs/example2.Spec.

Gauge version
Windows7 Enterprise - Service Pack 1

Gauge version: 0.9.7
Commit Hash: bc9784c

Plugins
-------
csharp (0.10.3)
flash (0.0.1)
html-report (4.0.3)
java (0.6.6)
json-report (0.2.1)
screenshot (0.0.1)
spectacle (0.1.2)
xml-report (0.2.1.nightly-2018-05-07)```

to my surprise this seems normal windows behavior. Changing the exentions of eg. doc to DOc or dOC etc does not make it ignorant to the respective programs (in this case word)

This issue was moved to getgauge/gauge#1058