Add workshop: 2018-09-25 Uni Bergen, Norway

Or perhaps this is generated from somewhere else?

Hi @danmichaelo We might generate this a different way in future but for now it is done the way you have done it. Merging it now - thanks !

Thanks! Good you spotted the extra comma :)

The page kept failing to build @danmichaelo so I asked @jduckles and he discovered that names with special characters need to be enclosed in square brackets like this:
["Hans Gunnar Slokvik Lian", "Kyrre Traavik Låberg", "Dan Michael Olsen Heggø"]
or the YAML chokes. All fixed now - and it only took more than 30 minutes ;-)
Glad your workshop is finally listed !

We actually want this to be the string: "Hans Gunnar Slokvik Lian, Kyrre Traavik Låberg, Dan Michael Olsen Heggø" (note there are no intermediate quotes).  I have PR'd that as a more sustainable fix.

The list form with square brackets is probably a preferred long-term approach, but none of the other who: items use a list form, and the Jekyll templates these data feed to probably don't expect a list. In SWC/DC workshop web pages, the list form is used, so to be consistent I'd recommend moving to using lists of distinct instructor names rather than a string naming many people within it.

Ouch, must have worked for too long yesterday. Thanks for fixing! Yes, an array would be more intuitive :)


Update README.md

Add more details explaining how to use this library.

@TomVasile, could you help us unblock this build so we can merge, please :)

Manually merging. Only markdown changed.


[g3doc] Fix image link error

Can one of the admins verify this patch?

I signed it!

Thanks for spotting the broken link!
We understand that the images are not checked in into github at the moment and that github looks broken right now. If you are building your internal version of the docs, we'd recommend you post-process the markdowns with a script.
We don't really want an absolute link since it will impair our ability to have multiple sites, for instance, a doc site for v1.0, and the last of the v0.xx.

@drpngx Thank you for your answer. I understand.


openssl instruction produces invalid .pem file on macOS

Prerequisites

[X] Write a descriptive title.
[X] Search the existing issues.
[X] I am reporting the documentation problem for the current version of Azure CLI.

Azure CLI version being used
azure-cli                         2.36.0  core                              2.36.0 telemetry                          1.0.6  Dependencies: msal                              1.17.0 azure-mgmt-resource               20.0.0  Python location '/opt/homebrew/Cellar/azure-cli/2.36.0/libexec/bin/python' Extensions directory '/Users//.azure/cliextensions'  Python (Darwin) 3.10.4 (main, Apr 26 2022, 19:36:29) [Clang 13.1.6 (clang-13<IP_ADDRESS>)]
Link to affected document
https://github.com/MicrosoftDocs/azure-docs-cli/blob/main/docs-ref-conceptual/create-an-azure-service-principal-azure-cli.md#certificate-based-authentication
Description of the documentation error
OK, so first off, I'm not 100% sure this is only a macOS issue, but I have too many hurdles to jump through on my side to make another machine valid for az login, so I hope you'll forgive me for not testing on other setups.
I am setting up a terraform project, so it's possible that there is an issue there. Anyway.
I used the following command to produce a Service Principal with a cert: az ad sp create-for-rbac --create-cert --cert acert -n automation-global --role Contributor --keyvault automation-global --scopes /subscriptions/<redacted>
Then this to download:
az keyvault secret download --file ./.certs/acert.pfx --vault-name automation-global --name acert --encoding base64
And this to convert openssl pkcs12 -info -in ./.certs/acert.pfx -passin pass: -out ./.certs/acert.pem -nodes
I set up an Azure Devops Service Connection with this output and it verified correctly.
However, it doesn't actually work. On the local terraform init I get:
2022-05-19T12:25:16.677+0200 [INFO]  Terraform version: 1.1.9
2022-05-19T12:25:16.677+0200 [INFO]  Go runtime version: go1.17.2
2022-05-19T12:25:16.677+0200 [INFO]  CLI args: []string{"terraform", "init"}
2022-05-19T12:25:16.677+0200 [DEBUG] Attempting to open CLI config file: /Users/<redacted>/.terraformrc
2022-05-19T12:25:16.678+0200 [DEBUG] File doesn't exist, but doesn't need to. Ignoring.
2022-05-19T12:25:16.678+0200 [DEBUG] ignoring non-existing provider search directory terraform.d/plugins
2022-05-19T12:25:16.678+0200 [DEBUG] ignoring non-existing provider search directory /Users/<redacted>/.terraform.d/plugins
2022-05-19T12:25:16.678+0200 [DEBUG] ignoring non-existing provider search directory /Users<redacted>/Library/Application Support/io.terraform/plugins
2022-05-19T12:25:16.678+0200 [DEBUG] ignoring non-existing provider search directory /Library/Application Support/io.terraform/plugins
2022-05-19T12:25:16.679+0200 [INFO]  CLI command args: []string{"init"}

Initializing the backend...
2022-05-19T12:25:16.695+0200 [INFO]  Testing if Service Principal / Client Certificate is applicable for Authentication..
2022-05-19T12:25:16.695+0200 [INFO]  Using Service Principal / Client Certificate for Authentication
╷
│ Error: Error building ARM Config: 1 error occurred:
│       * the Client Certificate Path is not a valid pfx file: pkcs12: error reading P12 data: asn1: structure error: tags don't match (16 vs {class:1 tag:2 length:97 isCompound:false}) {optional:false explicit:false application:false private:false defaultValue:<nil> tag:<nil> stringType:0 timeType:0 set:false omitEmpty:false} pfxPdu @2

I thought at first that perhaps there was something wrong locally. However, I was getting the following output on the CI:
│ Error: Error building ARM Config: obtain subscription(<redacted>) from Azure CLI: parsing json result from the Azure CLI: waiting for the Azure CLI: exit status 1: ERROR: Please run 'az login' to setup account.
│
│
╵

##[error]Terraform command 'init' failed with exit code '1'.
##[error]╷
│ Error: Error building ARM Config: obtain subscription(<redacted>) from Azure CLI: parsing json result from the Azure CLI: waiting for the Azure CLI: exit status 1: ERROR: Please run 'az login' to setup account.
│

I then followed the steps in the terraform guide and set up the service connection  with the .pfx output from the guide (the service connection now had both cert in the certificates tab): https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/guides/service_principal_client_certificate
This connected fine locally.
However, if I tried to run the conversion command (openssl pkcs12 -info -in ./.certs/input.pfx -passin pass: -out ./.certs/output.pem -nodes) on this cert and use the outputed cert for the service connection, it also fails, and fails locally as well.
So I think maybe the command doesn't work properly on macOS, or maybe it will never work for anyone.
Suggested fix
No response

I'd recommend posting your question in https://github.com/Azure/azure-cli/issues since it's not directly related to the documentation. We'll follow up there. We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

@DerekHerman-MSFT Hi, thanks for the response.
I'll follow your advice is you reaffirm it, but my sense is that there either an error in the instructions for using openssl for the use case or there is a need to issue macOS specific instructions. It does seem to me like something that should be covered in process docs rather than a specific cli issue.
I suspect if I post this there it'll get closed as not relevant to them.
What do you think?


I'm having to press Action Buttons twice

First let me say that this seemed to happen with the original Action Buttons extension too.
I've set up a couple of Action Buttons for use with ESP-IDF.
Let's say I want to run the Build button (see bottom of this message for my Action Buttons config). With the first press of the button, the integrated terminal opens according to its own settings, which are:
"terminal.integrated.defaultProfile.windows": "Command Prompt",
    "terminal.integrated.profiles.windows": {
        "Command Prompt": {
            "path": [
                "${env:windir}\\Sysnative\\cmd.exe",
                "${env:windir}\\System32\\cmd.exe"
            ],
            "args": [
                "/k",
                "C:/Espressif/idf_cmd_init.bat esp-idf-95fc7f73a381402d241e04a22ce81be3"
            ],
            "icon": "terminal-cmd"
        }
    },
    ...

As you can see, the integrated terminal automatically executes the ESP-IDF batch file to set up the environment in the usual manner. I then have to press the Build button again for the build to actually happen.
The same thing goes for the Flash button :(.
Here are my Action Buttons settings:
"actionButtons": {
    "defaultColor": "white",
    "reloadButton": "↻",
    "loadNpmCommands": false,
    "commands": [
        {
            "name": "Build",
            "terminalName": "ESP-IDF CMD BUILD",
            "color": "white",
            "useVsCodeApi": false,
            "ignoreCwd": true,
            "ignoreClear": true,
            "command": "idf.py build",
            // "extraCommands": [
            // ],
            "focus": true,
        },
        {
            "name": "Flash",
            "terminalName": "ESP-IDF CMD FLASH",
            "color": "white",
            "useVsCodeApi": false,
            "ignoreCwd": true,
            "ignoreClear": true,
            "command": "idf.py flash -p ${port} -b ${baud} monitor",
            // "command": "idf.py flash -p ${port} -b ${baud} 921600",
            // "extraCommands": [
            // ]
            "focus": true,
        }
    ]
"customVars": {
        "port": "COM8", /* Can be used in command as `${port}`*/
        "baud": "921600"
    }
}

hi, ESP-IDF terminal requires some time for running batch file. Use timeoutAfterCreate option to delay, so ESP-IDF batch file will have a time to complete. Choose resonable delay in milliseconds.
    "commands": [
        {
            "name": "Build",
            "terminalName": "ESP-IDF CMD BUILD",
            "color": "white",
            "useVsCodeApi": false,
            "ignoreCwd": true,
            "ignoreClear": true,
            "command": "idf.py build",
            // "extraCommands": [
            // ],
            "focus": true,
            "timeoutAfterCreate": 2000,
        },

Thank you for your help.
I have added a timeout in addition to using "singleInstance": true. Now I seem to get the desired behaviour :)


ampstart failing to run with Ubuntu 18.04

I am having trouble getting ampstart to run on Ubuntu 18.04.
npm i runs and finishes without problems
npm run watch and npm run build both return the same error:
[21:05:19] Finished 'configurator:json' after 66 ms
events.js:165
      throw er; // Unhandled 'error' event
      ^

Error: spawn java ENOENT
  at Process.ChildProcess._handle.onexit (internal/child_process.js:201:19)
  at onErrorNT (internal/child_process.js:379:16)
  at process._tickCallback (internal/process/next_tick.js:178:19)

Emitted 'error' event at:
  at Process.ChildProcess._handle.onexit (internal/child_process.js:207:12)
  at onErrorNT (internal/child_process.js:379:16)
  at process._tickCallback (internal/process/next_tick.js:178:19)

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! kickstart@ build: `gulp build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the kickstart@ build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:

I've tried to run it with node versions 8.x, 9.x and 10.x, yet I still get the same error message. I also have the build-essential -package installed. I've gotten the ampstart-package to run on my macOS just fine, but this problem keeps persisting on Ubuntu.

Perhaps Java is not installed? What's the output of java -version?

Doh.


babel-plugin-flow-react-proptypes still cause React 15.5 PropTypes deprecated warning

babel-plugin-flow-react-proptypes still cause React 15.5 PropTypes deprecated warning.
import type { Interpolation } from '../types'
transpiled to
var babelPluginFlowReactPropTypes_proptype_Interpolation = require('../types').babelPluginFlowReactPropTypes_proptype_Interpolation || require('react').PropTypes.any;

I'm also still encountering prop-types warnings after adding styled-components. The babel-plugin-flow-react-proptypes package has fixed their prop-types usage in the 1.0.0 release:
https://github.com/brigand/babel-plugin-flow-react-proptypes/commit/192e12895759917898179ad7520157021d5e91fe

Submitted a pr. Not sure whether this'll break things, but this way we can get the process started.

Just upgrade to styled-components v1.4.5
But, the devtools console still gives me warning

For me 1.4.5 fixes the devtools console warning, but still logs warnings when running my jest tests on the command line:

PR #683 fixes those warnings.

hey @mxstbr @geelen,
this is still an issue
I just tried to do a fresh install of create-react-app
then install and import styled-components (v1.4.5) in App.js
the devtools console still logs the proptypes warning
the terminal also still logs the warning everytime I run a test

It's been fixed:
v1: https://github.com/styled-components/styled-components/commit/769be58e8558dd8d1bbbf3e4c5d3d93e802ebff0
v2: https://github.com/styled-components/styled-components/commit/9e7ce0e9881a144466a8cac85c5447973e81fe17
Just needs to be released on npm


Double-definition in a JS literal pass compiler and IR checker

The example code that caused this was essentially:
js.Dynamic.literal(
  url = "http://something.com/",
  // ... other stuff
  url = "http://somethingelse.com/"
)

The actual error from test was swallowed, but @gzm0 says that PhantomJS reports a "parse error" on this situation -- the output JS is considered invalid.
Conversation on Gitter suggests that the compiler should catch this double-definition before we get to runtime.

So, actually, this is not an error in ECMAScript 6 anymore. It is an (early) error in ES5 strict mode, but in ES6 (even strict mode) they have reverted to the ES5 sloppy mode behavior of last-definition wins. Given this, I believe we should keep the compiler and the IR as they are now, and fix JSDesugaring to desugar an object literal with a double definition as a series of successive assignments to an initially empty object. In ES6 output mode we wouldn't do this desugaring. (Potentially, the compiler could emit a warning.)
Actually, we could even allow non-constant keys in JSObjectConstr in the IR. Non-constant keys (aka computed properties) are now possible in ES6 as well (and is the reason the early errors have been canceled). Desugar could similarly transform that to gradually constructing the object when emitting to ES5.

Fine by me -- my only real concern is that the above code not cause hard-to-figure-out parse errors.  (Even those wouldn't be critical if #1594 gets fixed: it was really the combination of the two that is really bad, since the JS parser crashed and there was difficult to figure out why.)


Simple expression parser silently fails

Hi I got the following code for a very simple parser that supports addition. The problem is that the parser returns a result with "IsError=True" but no error messages or any other kind of information and i cant figure out why this is happening.
public enum ExpressionToken
    {
        // Base types
        [Lexeme(@"[0-9]+")]
        INT = 1,

        [Lexeme(@"TRUE|FALSE")]
        BOOL,

        [Lexeme(@"'[^']*'")]
        STRING,

        // Variables and such
        [Lexeme(@"[\w]+")]
        ID,

        [Lexeme(@"\$\$[\w]+")]
        PARAMETER,

        [Lexeme(@"\+")]
        PLUS,

        [Lexeme("[ \t\n]+", isSkippable: true)]
        WS
    }
    public class ExpressionParser
    {
        [Operation((int) ExpressionToken.PLUS, Affix.InFix, Associativity.Left, 10)]
        public Expression Comparison(Expression e1, Token<ExpressionToken> op, Expression e2)
        {
            return new BinaryOpExpression()
            {
                op = BinaryOperator.Plus,
                left_expr = e1,
                right_expr = e2
            };
        }

        [Operand]
        [Production("expr: term")]
        public Expression Operand(Expression f)
        {
            return f;
        }

        [Production("term: INT")]
        public Expression PrimaryInt(Token<ExpressionToken> tok)
        {
            return new IntExpression()
            {
                value = tok.IntValue
            };
        }

        [Production("term: STRING")]
        public Expression PrimaryStr(Token<ExpressionToken> tok)
        {
            return new StringExpression()
            {
                value = tok.Value.Substring(1, tok.Value.Length - 2)
            };
        }

        [Production("term: BOOL")]
        public Expression PrimaryBool(Token<ExpressionToken> tok)
        {
            return new BoolExpression()
            {
                value = bool.Parse(tok.Value)
            };
        }

        [Production("term: ID")]
        public Expression PrimaryId(Token<ExpressionToken> tok)
        {
            return new IdExpression()
            {
                name = tok.Value
            };
        }

        [Production("term: PARAMETER")]
        public Expression PrimaryParam(Token<ExpressionToken> tok)
        {
            return new ParamExpression
            {
                name = tok.Value.Substring(2)
            };
        }
    }

var parse_inst = new ExpressionParser();
var builder = new ParserBuilder<ExpressionToken, Expression>();
var parser = builder.BuildParser(parse_inst, ParserType.EBNF_LL_RECURSIVE_DESCENT, "expr");

var r = parser.Result.Parse("ba + bb");

hello,
first your parser can not succeed at parsing "a + b".
Let me explain :
your starting rule is expr as stated by
var parser = builder.BuildParser(parse_inst, ParserType.EBNF_LL_RECURSIVE_DESCENT, "expr");

and expr is term which in turn is either an int a bool a string or an id. So at best you will match the first ID "aa" but you could never parse an addition.
When using the expression parser generator the root rule for expression parsing is _expressions (as stated here : https://github.com/b3b00/csly/wiki/expression-parsing#using-the-expression-parser)
So in your case you can call the parser this way :
var r = parser.Result.Parse("ba + bb", nameof(ExpressionParser)+"_expressions");

Nevertheless this does not explain why you dont have an error message and I will investigate it.
hope this helps

I've just found the bug and fixed it. Now you should have a message like
syntax error :unexpected  "PLUS [+] @line 1, column 4 on channel 0" (PLUS).

I've not yet published a new nuget though

@leryss have you found my answer ok ? please answer...

@leryss I've just public v<IP_ADDRESS> that fixes your issue returning an error message. Please! tell me if you're ok with this fix ! It's important for CSLy to keep improving.


Vue apollo v3.0.5 not compatible with apollo client v3 despite having apparently being fixed

Describe the bug
I can see from your commit here that you updated the package dependencies to use @apollo/client": "^3.2.1". However it does not appear that you correctly followed the apollo client v3 migration docs to change the import statements for apollo client see line 4 here for example.
Unless theres something else going on this would explain why our current project using

vue-apollo v3.0.5
@apollo/client v3.2.5

is having the following errors when we build our dev server (and our production code as well).
node_modules/vue-apollo/types/apollo-provider.d.ts(4,30):
TS2307: Cannot find module 'apollo-client'.
node_modules/vue-apollo/types/options.d.ts(8,8):
TS2307: Cannot find module 'apollo-client'.
node_modules/vue-apollo/types/vue-apollo.d.ts(11,8):
TS2307: Cannot find module 'apollo-client'.
To Reproduce
create simple vue project using quasar cli (as it makes everything easy).

install vue-apollo v3.0.5
@apollo/client v3.2.5

Expected behavior
apollo client v3 docs clearly state that that imports must follow the new syntax of
import { ApolloClient } from "@apollo/client/core"
instead of
import { ApolloClient } from 'apollo-client'

Is there a workaround for this? Would love to finally migrate to apollo 3 :)

npm i apollo-client -D
I saved the apollo-client as dev dependency just to get pass the type checking.


Add "make test" during build (as requested by upstream)

This explicitly removes a few failing tests in Alpine while we work with upstream to figure out why they're failing and hopefully get them fixed.
See also https://github.com/memcached/memcached/issues/286#issuecomment-315645936.
cc @zoidbergwill

Still no dice for #20:
$ docker run -it --rm 08c33800554f sh
/ $ memcached -o modern
Segmentation fault

Will try to follow the debugging steps in https://github.com/memcached/memcached/issues/286 and report back there.  Meanwhile, I'll remove that patch from this PR.

Doh, I got too excited and forgot that I have to redirect to patch's stdin, so I wasn't actually testing the patch.  The patch does make -o modern work; adding it back.

Build time differences (still worth adding, IMO):

Debian: ~1m8s before, ~4m10s after
Alpine: ~40s before, ~3m40s after


Fix the backgroundImage BUG

Setting backgroundImage will error, Has been resolved!

You fix is too specific to a use case that is not officially supported by anime.js (only numerical values can be animated)


Validate Blacklist content, and show the regular expression notation name in the Blacklist title of the preferences which is must be used

Blacklist can content invalid regular expressions that's result in extension non-working.
Which is regex notation used for blacklist (PCRE, POSIX basic, POSIX extended, ...)?
I suggest to:

check validity of blacklist content before preferences saving.
show regex style name in the title of Blacklist: (you may use ... regular expressions ...)

Today I save after every keystroke and validating directly could make typing difficult. How to display errors would be difficult too. But I can imagine adding a validate button.
It's Javascript regular expressions, but if I'd add that, I feel I have to do some more explaining, which I don't want.

But I can imagine adding a validate button

It's acceptable too.

It's Javascript regular expressions, but if I'd add that, I feel I have to do some more explaining, which I don't want

Even (you may use JavaScript' regular expressions) gets enough information about notation. So additional word can enhance title.
Do I right understand that blacklist lines always are interpreted as RegExp? Particularly, is the dot . symbol always interpreted as any symbol?

This is what happens: https://github.com/sblask/webextension-skip-redirect/blob/master/url.js#L102 exceptions is an array of the lines of either blacklist or whitelist.

I don't think I will do anything about this. If someone wants to add a validator, they can reopen this case.


Paillier DecryptFull

Added DecryptFull to paillier package. This function returns both the message and the randomness used to create it. This is sometimes necessary for zero-knowledge proofs about the ciphertext.

New function DecryptFull
New unit test
Updated automatically compiled protobuf files with latest version
Added clean_test to Makefile
README2.md file with instructions for testing, dependencies, etc.

Made in error


TaskGroup reorder resumeWaiting->run and reenable async_taskgroup_discarding_dontLeak

We had resolved rdar://109998145 via the lock ordering fix in https://github.com/apple/swift/pull/67700
This is the same kind of test and cause radar to have disabled the test, so re-enable it.
We also have the "bad order" of
    resumeWaitingTask(completedTask, assumed, hadErrorResult);
    unlock(); // bad, unlock first (!)

that we should correct in a separate commit here.
I'd like to use this PR to give this a few runs to verify.

@swift-ci please test


OAuth2: Unregistered Scopes and/or additional data via Access Token

I have the following situation: When identifying a user using our own authentication system (SAML based) I also get information on the user being authorized (licenses) to access the API or not. I would like to pass on this information with the upstream call, enriched via the access token.
We want to use Kong to secure a content API which delivers different results depending on which content products (identified by product IDs) the user has licensed.
A possibility to do this would be using OAuth2 scopes. The problem I have now is quite stupid: We  literally have thousands of product IDs, and each one would need to be registered with the API's OAuth2 Scopes. And they change once in a while, meaning I would have to keep the API definition updated via some kind of integration.
My question now is: Could I solve this in a different way? The obvious way is to tell the API implementation to go ask the license server itself, but it sort of feels stupid as I do have the information at hand in the Authorization Server.
Other ways I see which would be nice (or at least would solve my problem):

Allow the oauth2 plugin to allow arbitrary scopes when authorizing; i.e. allow an access token to be created for any list of scopes, even if the plugin of the API does not have scopes defined (this is what I mean with "unregistered scopes").
Allow the authorize end point to not only pass on X-Authenticated-UserId, but additionally arbitrary other headers, e.g. in my case X-Authenticated-Products (this is what I mean with "additional data via Access Token").

These both "solutions" would probably mean changes to the OAuth2 Plugin. It would definitely increase the usability for my use cases if one of those were implemented.
I could also encode the information inside the X-Authenticated-UserId header, but that feels strange.

@DonMartin76 Is this issue still relevant or did you find a solution?

We found a bunch of workarounds, mostly we resorted to encoding more information into the X-Authenticated-UserId header. This kind of feels wrong, but does the work. We also implemented that abovementioned integration for one use case, where we periodically poll one service and update the OAuth2 scopes of the API with an updated list of product information.
So, strictly speaking we're probably not needing this anymore.


Some videos load when saved, some don't?

Hello, I just started working on this library a few hours ago, decided to give it a shot for fun, and it's functioning perfectly, just one thing I noticed, I'm retrieving video snaps as MP4, when saving them and trying to open them, some work and some don't, the ones that aren't working did work at some case (removed the video and saved it again and it stopped working, although some I removed and saved again did work), I'm not really able to tell any difference between the videos working and the videos not working (when viewing them on an app that saves snaps on phone), no overlay or anything, what do you think could be causing this?
Thanks.

Oh, it seems like it's not passing the isMedia check.

Oh, it seems like it's not passing the isMedia check.

If it isn't passing the first isMedia check then it should means it's zipped with an overlay. I am working on tuning the isMedia script to return the actual type of media, I'll keep you updated.

If it isn't passing the first isMedia check then it should means it's zipped with an overlay. I am working on tuning the isMedia script to return the actual type of media, I'll keep you updated.

It doesn't have an overlay, I checked with an app on Android and it's just a normal 8 seconds video, it also worked a few times with some tries then stopped working, then worked again.


[WIP] feat: Relate to MySQL database via mysql_client interface

Fixes https://github.com/canonical/mlmd-operator/issues/64

Closing due to https://github.com/canonical/mlmd-operator/issues/64#issuecomment-1779322287

Sent https://github.com/canonical/mlmd-operator/pull/66 in order to just bump the image


converting to single expression

@rossabaker Thanks
I have corrected the scalafmt check. Please see if it's good to go now

@rossabaker Could you please add the second reviewer.

@rossabaker Please add the second reviewer as I'm not very sure who would be the best person to review this.

Thanks, @hamnis for approval
@rossabaker Are we good to merge this?


need to update godep dependency on bosh-agent

Hi, @zhang-hua,
@posijon is working on a similar issue for softlayer-go. Hopefully the same solution can be applied here.
Best,
@maximilien

This looks to be related to issue #31, so I'm closing this as well.


Bring DX to core

This project uses semver, please check the scope of this pr:

[ ] #patch# - backwards-compatible bug fix
[x] #minor# - adding functionality in a backwards-compatible manner
[ ] #major# - incompatible API change

CHANGELOG

Added some aria attributes to frost-select in order to make it a little bit more accessibility friendly.

Updated testem to use custom reporter for better DX.

Updated linting to leverage new linting tools provided by ember-test-utils which gives us the following output:

Changes Unknown when pulling 9b3831ada1ad995a122fa5524d1ea55ab1a801a4 on sandersky:master into ** on ciena-frost:master**.

Approved

Changes Unknown when pulling d802224834b3077366022b1a0d508bfab17fcea3 on sandersky:master into ** on ciena-frost:master**.


Enhance the color picker with the LCh() color model and optional hex "#" format

Description of the new feature / enhancement

Add a new color format to the list to support the LCh (luminance/chroma/hue, aka HCL) color model. This model is now supported by all of the major browsers and is seeing increased adoption due to its larger color space and human-centric chroma model.
Add a second format for hex values ("hex#"?) that includes the leading # sign that is one of the two most common ways of actually specifying hex colors.

Scenario when this would be used?
Professional programmer encounter hex "#"-encodings everywhere. LCh isn't as common but is gaining increased adoption both in the programming and digital art world.
Supporting information
I doubt I need to provide supporting information about the "#" hex format. You know it, you've used it.
Regarding LCh:

https://www.w3.org/TR/css-color-5/#relative-LCH
https://en.wikipedia.org/wiki/HCL_color_space
https://developer.mozilla.org/en-US/docs/Web/CSS/color_value/lch

About the #: this has been mentioned a lot of times, see (for example) #19430 for info.

Would you prefer LCHab or LCHuv?

I saw a discussion about using the hashtag hex notation but it appeared to be suggesting changing the hex notation. I'm suggesting here simply adding a hex# notation as another alternative format in the selection option list.
As for LCHab vs LCHuv, I believe LCHab is more commonly used and the W3C CSS implementation for the LCh function. That being said, the implementations for these are widely available (eg, the Julia Colors package that implements both of these and many others) so there may not be much reason not to provide both. I would be more than happy to help.

Regarding the hash format "#xxxxxx", this is what CSS and many CSS tools and libraries are using, so why not add it?
There is already 13 image formats available, and many of them are much more rare than wildly used CSS.
Alternatively, maybe just add a checkbox "Include hash (#)" for the HEX format.

In the past, the copied value did include the #. However, a number of apps only accept 6 characters input.  Compared to that, typing a # by hand is not an effort. #8305 would be everybody's solution. But, you know, it takes time and "manpower" and we sure could use more of that... :)

You can't say "typing a # by hand is not an effort", there is not even key for that character on the English keyboard :), you need to Shift + 3 to write that.
I would argue that adding new hex format called "#HEX" is a small effort and it would save how much time to how many users. Just imagine all those happy users that will be able to simply paste the color and it works.

hi everyone, we just did https://github.com/microsoft/PowerToys/issues/8305.
Does this solve this for you now that you can do whatever format you want now? /needinfo


About lider sensor

I found an issue. The screen in the game would go dark when the lidar sensor was attached on the car, and I  set the setting is_visualised=false. The scene brightness is not restored, which I thought was a mistake.

When I add lider...

Maybe someone can help me answer that question.

Hello @ccc-fire
Thank you for reporting the LiDAR sensor issue affecting the camera view, even when LiDAR visualization is off. Our team is actively working on a fix for the next release. Please feel free to share any additional feedback.
Best regards,

Hi, this issue is fixed for BeamNG.tech 0.30 and BeamNGpy 1.27.


Fix handshake failure in suite B

Description
Fix handshake failure where PK key is translated as MBEDTLS_ECKEY
instead of MBEDTLS_ECDSA, when the profile used is mbedtls_x509_crt_profile_suiteb
Fixes #1351
Status
READY
Requires Backporting
Yes
Which branch?
mbedtls-2.4
Additional comments
Any additional information that could be of interest
Todos

[x] Tests
[ ] Documentation
[x] Changelog updated
[ ] Backported

Steps to test or reproduce
Outline the steps to test or reproduce the PR here.

@mpg I'll add positive tests

@mpg I have added some tests for suite b profile and for the next profile.
I have also modified the Changlog per your suggestion.
Please review.

@RonEld Could you also provide a backport for this?

@hanno-arm I am working on a bakport, but the backport will inclde more changes to the tests, as I will need to update the test function to receive the profile as parameter

@hanno-arm I have backported to branch 2.1
no need to backport to 1.3, as there are no profiles in that branch


Fixed Issue #44

[v1.2.8] Set default args parameter value to process.argv.split(2)

Codecov Report

Merging #45 (0d3cf8e) into main (fdbb909) will not change coverage.
The diff coverage is 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##             main      #45   +/-   ##
=======================================
  Coverage   98.78%   98.78%
=======================================
  Files           1        1
  Lines         165      165
  Branches       70       71    +1
=======================================
  Hits          163      163
  Misses          2        2

Files Changed
Coverage Δ

index.js
98.78% <100.00%> (ø)

(I started the tests, but of course they won/t show up any problems since this won't be covered by the existing tests.)
This Code does not like it will work. Have you tried it?
You can mark a Pull Request as Draft while you are still working on it and especially when not ready for review.

→ #46.


Update readme to use this project's source

Hey @gbj,
I'm assuming start-axum-0.7 will eventually replace start-axum, but for the time being it might help to provide the correct repository target.

I clicked merge too fast on that one :smile: Just curious, does the command as you wrote it (cargo leptos new --git leptos-rs/start-axum-0.7) actually work for you? In the version of cargo-leptos I have installed, it does not, because other than a few built-ins it requires a full URL for the repo.

@gbj apologies, Greg.
The command I had to run for this to work was:
cargo generate -g https://github.com/leptos-rs/start-axum-0.7


Retrying setup: Cannot connect to host none:80 ssl:default [Name does not resolve]

Version of the custom_component
v2.1.1
Deco Model
3 x M4(v2)
Main (Cabinet)
Second (Landing)
Third (Kitchen)
Describe the bug
Initial setup went fine, configured and found all devices, needed to restart HACS and HA to update other integrations and found that the error below was present on the HA Integrations page.
Retrying setup: Cannot connect to host none:80 ssl:default [Name does not resolve]
When I checked the config, the main host had defaulted back to the original address <IP_ADDRESS> and the password had disappeared.  Have tried several times to reset configuration which it seems to do (says finished successfully) but the error remains and the config entries are still missing.
Home Assistant log
Log Details (ERROR)
This error originated from a custom integration.
Logger: custom_components.tplink_deco
Source: custom_components/tplink_deco/api.py:390
Integration: TP-Link Deco (documentation, issues)
First occurred: 21:41:46 (8 occurrences)
Last logged: 21:47:14
Fetch keys client error: Cannot connect to host none:80 ssl:default [Name does not resolve]
Log Details (WARNING)
Logger: homeassistant.config_entries
Source: config_entries.py:366
First occurred: 21:50:52 (1 occurrences)
Last logged: 21:50:52
Config entry 'WiFi Network' for tplink_deco integration not ready yet: Cannot connect to host none:80 ssl:default [Name does not resolve]; Retrying in background

I have tried this morning to remove and reinstall the integration in HA, it works to get to the same point as last night in that it works but as soon as I restart HA I get the error messages back again.
Any other tests I can do to help diagnose please do let me know.

Having exactly the same issue.

@antonyslater That's quite the mystery to me, since it says "Cannot connect to host none:80 ssl:default", that indicates that the host config field value is not set, hence the "none". That is pretty strange since it worked before. So seems to indicate it's not saving the host value somehow? I'm unable to repro at all.
Did you try turning on debug logs and see if you get any other interesting logs? Also does downgrading to v2.1.0 as @schwieb mentioned help you?

I agree that it doesn't seem to be saving the information. Unfortunately you also cannot edit/re-add and save them.
I wanted to clean up some settings so I completely wiped them, uninstalled, upgraded and readded the integration. You may want to try the same to duplicate the bug.
Now that I'm running the version 2.1.0 successfully, I can try upgrading from here to see if the settings are kept allowing it to work fine. I will do that later today or tomorrow morning and report back.

Ok, I upgraded and the application worked for the first boot.  Unfortunately, it stopped working again after a reboot with the same error:
Retrying setup: Cannot connect to host none:80 ssl:default [Name does not resolve]

I have the X20 with the same issue.

Same issue here on the Deco w3600

Same here on the Deco M5.
It seems to work until I make any kind of change to the config (such as disabling some entities or changing an entity display name), the all entities go unavailable and won't come back until I delete and reinstall the integration.

For people who are experiencing this error. Please do the following:

Turn on debug logs and confirm if you are getting that error Cannot connect to host none:80 ssl:default [Name does not resolve] or if you are getting other errors.
Try downgrading to v2.1.0 and let me know if that fixes the problem.

I'm on v2.1.0 and get the following errors:
aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host none:80 ssl:default [Name does not resolve]
homeassistant.exceptions.ConfigEntryNotReady: Cannot connect to host none:80 ssl:default [Name does not resolve]

After this all devices go permanently unavailable.
I think I've got to the bottom of my issue:
These errors happen as soon as I rename the integration (using the Three dots->Rename option in the integration UI).
Everything is fine until then, but within seconds of renaming I get the above errors.
Changing the integration name back to what it was (the IP of my router) and restarting Home Assistant doesn't fix the problem, the only thing that helps is deleting the integration and re-installing.

Upgraded to v2.2.0 and get the same behaviour.
As well as changing the name of the integration I also get the errors if I change the 'Enable newly added entities' option through the UI.
So it's looking like it happens as soon as I make any kind of config change to the integration after initial install. If I leave it alone after initially setting it up then it works fine.

I no longer seem to be having the issue but I upgraded straight from 2.1.0 to 2.1.2.  I have not yet updated to 2.2.0

I'm unable to reproduce on 2.2.0

Closing this issue for now as fixed.


jRuby compatibility

POSIX::Spawn causes issues with the latest version of jRuby. Is there a way to remove this dependency  or alter it for jRuby so that it is not needed?

For reference, if you install the following gem:
$ gem install pygments.rb-jruby

Then replace the call to popen4 as @bartkamphorst suggested:
require 'open3' if RUBY_ENGINE == 'jruby'

...

@in, @out, @err, @wait = Open3.popen3(script)
@pid = @wait[:pid]

Then it works. Of course, that's an older version of the gem ;(

I put together a pull request that implements these changes. I'm happy to say it works as expected!


[DEV-1937] name check

Release Checklist
Pre-Release

[ ] Check migrations

No database related infos (sqldb-xxx)
Impact on GS (new/removed columns)

[ ] Check for linter errors (in PR)
[ ] Test basic user operations

Login/logout
Registration
Update user data
Create/delete payment routes

Post-Release

Test basic user operations
Monitor application insights log

Add migration


Support for ball joints

I wanted to use k for a forward kinematics solver for a human pose. In order to accomplish this I would need the ability to have ball joints, such as the joints on your hip and spine. Could this functionality be added? I know its possible by using three rotational joints but thinking about permutations of rotations, etc, is confusing to me and I'm not sure I'm up to the challenge as someone unfamiliar with all of this.

Hi, thank you for good feedback!
I don't know about the ball joint so much. Could you tell me about what is the input of ball joint what you think?
For example, it might be a quaternion or rotation matrix?

I know very little at all about IK or FK. That was why I came to this crate :P
But in this case, the ball joint was like your hip or shoulder joint, for example. Presumably input is quaternion.


Environment monitoring screen shot

User activity part is not visible in screen shot.

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

ID: 64b5b03d-9169-f94e-f999-63bc5a8e68ac
Version Independent ID: 177eb187-6962-ba30-7a63-86b0bf3452d7
Content: Monitoring and diagnostics tools in Lifecycle Services (LCS) - Finance & Operations | Dynamics 365
Content Source: articles/fin-ops-core/dev-itpro/lifecycle-services/monitoring-diagnostics.md
Service: dynamics-ax-platform
Product: ****
Technology: ****
GitHub Login: @meeramahabala
Microsoft Alias: meeram

@Navneetkat, thank you for the feedback.
@meeramahabala, please review.


[#103088246] Add skeleton DOS schema and allow DOS drafts to be created

The tests add the dos framework to the database to allow the tests to run - once dos exists in all environments we should remove the bootstrap_dos() part of these tests.

:+1:


Downsampling on query_range

Would people be interested in an implementation of down sampling for query_range? I've been considering the following:

add a downsample param to query_range, defaults to none, everything works as presently if it's not set.
downsample=METHOD, would select a downsampling method.
if a downsample method is requested, a samples parameter would select how many samples to return to the caller.
Add an internal Downsampler interface of roughly:
 func (ds sample.Matrix) Downsample(samples int) sample.Matrix

I'd then add LTTB downsampling (I have a tested implementation), and probably max/min/mean (any aggregator?) methods.
The primary motivation is to support graphing with minimal visual feature loss (that is what LTTB is really meant for).
If people are interested, I'd very much like to have a go at contributing this.

How would this work semantically? query_range already downsamples.

Does it? That isn't clear from the documentation. The only this that sounds like downsampling is step
step=<duration>: Query resolution step width.
Which sounds more like it is skipping samples than aggregating them. If it's aggregating them in some way, it should say how they are being aggregated.
I've been assuming that step is skipping samples, and giving me the ones that fall every ````` between the start and end. If it's doing some downsampling of the data, then I'll have to think about this  abit harder.

if it's not actually aggregating, then step and samples would just do both. Take the current data that woul be returned by step=... and downsample that to samples=X samples.
If it's doing some aggregation, I'll have to rethink the interface. Possibly just adding LTTB as an option, and defaulting to the existing method (then calculating the resolution from the (end - start) / duration

I think you misunderstand how query_range works. It evaluates the expression every step seconds and returns the result. If you want to downsample further, increase step. Query_range has no notion of samples.

I think that's pretty much what I assumed was happening. I'm trying to cater for the case where step results in missing spikes on a graph when it's auto-calculated based on the graph resolution. You can set step manually, but then you are returning potentially more data to the client. e.g., I have a task:thing:rate1m rule , if I graph that for a week on a 800 pixel wide graph, that a step of something like 12m per pixel, plenty of space for me to lose a spike.
if I do a step=1m, then I get 10080 datapoints to squeeze onto my 800 pixel graph, and my graphing library gets to decide what I should see (and I don't neccesarily know what decision it made). I also am transferring a lot more data.
So step=1m, downsample=max, samples=800 would get me 800  the max the max of 800 buckets of the 10080.

As a work around, you could emulate downsampling strategies by using avg_over_time, max_over_time and such.
They only work on time series, though, not on arbitrary expressions, so you might need a recording rule as a middle man if you want to apply the approach to a complex expression.

yes, you'd need to need to know the time range you are typically
displaying, and the resolution of the graph you are displaying it on though.
Adding support seems like it should be reasonably easy, backward
compatible, and give people a bit more control. I think the grafana
integration could make good use of this.
On Mon, 26 Sep 2016 at 09:15 Björn Rabenstein<EMAIL_ADDRESS>wrote:

As a work around, you could emulate downsampling strategies by using
avg_over_time, max_over_time and such.
They only work on time series, though, not on arbitrary expressions, so
you might need a recording rule as a middle man if you want to apply the
approach to a complex expression.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/prometheus/prometheus/issues/2031#issuecomment-249506700,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEo8zpmLhRZXzsJR9YluH9U82pEZqrWks5qt38QgaJpZM4KGNKY
.

I'm not sure this would be as useful as you think, we'd still want the limit on the number of steps evaluated in order to avoid queries of death/sloth.

This is pretty much what I'm thinking about... https://github.com/prometheus/prometheus/compare/master...tcolgate:downsampling

I'll avoid any further work on it until someone decides either way if this is wanted. I do think it has some value. OpenTSDB provides for it, I'm not sure if Influx or Graphite do. I think it gives a more complete set of features for querying.

I don't think downsampling the final result like that in the web API will be very useful - most of the effort is happening already before that (loading the data from disk and evaluating the expression). In your case, you'd have to either start with a super high query resolution and then downsample on that in the end (but then you still do most of the work before that final step), or you start at a normal query resolution, but then you already skipped over a lot of raw sample data and there's not much more useful downsampling you can do.
The theoretically "right" way to do it would be to downsample at the raw sample layer. As in, have the storage layer already provide you with downsampled data that your expression can then work on faster. You still need to go through all the data on disk to downsample it correctly, but at least the query evaluation will have to process less.

That sounds like we're getting into long term storage downsampling then.

I wasn't really thinking of this as an optimization on the server side, more a convenience for the user (explicit control over downsampling, and minimizing data transfer to the client).
Downsampling when reading from storage seems more problematic. Yes, it minimizes effort in the query engine, but it'll also be happening before, for instance, a rate()/increase(), which seems like it could potentially result in very different query results, which could be even more confusing to users (LTTB would be very dubious if done pre-calculation, the result would be potentially very dubious, and unlikely to represent the LTTB of the original final result).
If there is some long term desire to downsample at storage read, then that probably needs to be included in the remote storage discussions?

If there is some long term desire to downsample at storage read, then that probably needs to be included in the remote storage discussions?

That's an implementation detail for the remote storage, as downsampling in storage is explicitly out of scope for Prometheus itself.

@brian-brazil surely if the user is requesting downsampling, there has to be a means for that request to be passed to the storage layer (if the idea is for the query engine to process less data)? Any RPC would need to take that into account?
I'll close this ticket now, thanks for the time.

surely if the user is requesting downsampling, there has to be a means for that request to be passed to the storage layer (if the idea is for the query engine to process less data)?

I never said the user requested downsampling for long term storage. The issue is that long term storage must downsample in it's response for bandwidth reasons. How to do that transparently remains an open question, but seems like it should be possible.


Add support for iOS 10 & macOS Sierra new OS Logging

https://developer.apple.com/reference/os/1891852-logging
Apple's new logging system is a major improvement over NSLog, let's create a 3rd console output stream that will use os_log too.  It will be left to developers consuming the framework to create a combo output stream that will use os_log for new OS versions and NSLog for old OS versions.

done


Add installation options to use, run & exec commands to install node version if not installed

Operating system and version:
macOS 10.15.4 (19E287)
nvm debug output:

🍺 nvm debug
nvm --version: v0.34.0
$TERM_PROGRAM: iTerm.app
$SHELL: /usr/local/bin/bash
$SHLVL: 1
$HOME: /Users/matthewadams
$NVM_DIR: '$HOME/.nvm'
$PATH: $HOME/.yarn/bin:$HOME/.config/yarn/global/node_modules/.bin:$HOME/bin:$NVM_DIR/versions/node/v10.1.0/bin:$HOME/.sdkman/candidates/scala/current/bin:$HOME/.sdkman/candidates/java/current/bin:$HOME/.sdkman/candidates/groovy/current/bin:$HOME/.sdkman/candidates/gradle/current/bin:$HOME/google-cloud-sdk/bin:$HOME/.git-subrepo/lib:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/usr/local/MacGPG2/bin:/usr/local/share/dotnet:~/.dotnet/tools:/Library/Frameworks/Mono.framework/Versions/Current/Commands:/Applications/Xamarin Workbooks.app/Contents/SharedSupport/path-bin
$PREFIX: ''
$NPM_CONFIG_PREFIX: ''
$NVM_NODEJS_ORG_MIRROR: ''
$NVM_IOJS_ORG_MIRROR: ''
shell version: 'GNU bash, version 5.0.16(1)-release (x86_64-apple-darwin19.3.0)'
uname -a: 'Darwin 19.4.0 Darwin Kernel Version 19.4.0: Wed Mar 4 22:28:40 PST 2020; root:xnu-6153.101.6~15/RELEASE_X86_64 x86_64'
OS version: Mac 10.15.4 19E287
curl: /usr/bin/curl, curl 7.64.1 (x86_64-apple-darwin19.0) libcurl/7.64.1 (SecureTransport) LibreSSL/2.8.3 zlib/1.2.11 nghttp2/1.39.2
wget: /usr/local/bin/wget, GNU Wget 1.20.3 built on darwin18.6.0.
git: /usr/local/bin/git, git version 2.24.0
grep: /usr/bin/grep (grep --color=auto), grep (BSD grep) 2.5.1-FreeBSD
awk: /usr/bin/awk, awk version 20070501
sed: illegal option -- -
usage: sed script [-Ealn] [-i extension] [file ...]
       sed [-Ealn] [-i extension] [-e script] ... [-f script_file] ... [file ...]
sed: /usr/bin/sed,
cut: illegal option -- -
usage: cut -b list [-n] [file ...]
       cut -c list [file ...]
       cut -f list [-s] [-d delim] [file ...]
cut: /usr/bin/cut,
basename: illegal option -- -
usage: basename string [suffix]
       basename [-a] [-s suffix] string [...]
basename: /usr/bin/basename,
rm: illegal option -- -
usage: rm [-f | -i] [-dPRrvW] file ...
       unlink file
rm: /bin/rm,
mkdir: illegal option -- -
usage: mkdir [-pv] [-m mode] directory ...
mkdir: /bin/mkdir,
xargs: illegal option -- -
usage: xargs [-0opt] [-E eofstr] [-I replstr [-R replacements]] [-J replstr]
             [-L number] [-n number [-x]] [-P maxprocs] [-s size]
             [utility [argument ...]]
xargs: /usr/bin/xargs,
nvm current: v10.1.0
which node: $NVM_DIR/versions/node/v10.1.0/bin/node
which iojs:
which npm: $NVM_DIR/versions/node/v10.1.0/bin/npm
npm config get prefix: $NVM_DIR/versions/node/v10.1.0
npm root -g: $NVM_DIR/versions/node/v10.1.0/lib/node_modules

nvm ls output:

🍺 nvm ls
       v0.12.18
         v4.9.1
        v5.12.0
         v6.0.0
        v6.17.1
         v8.0.0
         v8.3.0
         v8.4.0
         v8.6.0
        v8.10.0
        v8.15.1
        v8.16.2
        v8.17.0
        v9.11.2
        v10.0.0
->      v10.1.0
       v10.12.0
       v10.13.0
       v10.14.2
       v10.15.3
       v10.16.3
       v10.17.0
       v10.20.1
       v11.13.0
       v11.15.0
       v12.10.0
       v12.13.0
       v12.14.0
       v12.16.0
       v12.16.3
       v12.17.0
        v13.5.0
       v13.14.0
        v14.1.0
        v14.2.0
        v14.8.0
         system
default -> 14 (-> v14.8.0)
node -> stable (-> v14.8.0) (default)
stable -> 14.8 (-> v14.8.0) (default)
iojs -> N/A (default)
unstable -> N/A (default)
lts/* -> lts/erbium (-> N/A)
lts/argon -> v4.9.1
lts/boron -> v6.17.1
lts/carbon -> v8.17.0
lts/dubnium -> v10.22.0 (-> N/A)
lts/erbium -> v12.18.3 (-> N/A)

How did you install nvm?
install script in readme
What steps did you perform?
nvm use --install 10.4.0 without having installed 10.4.0 prior to invocation
What happened?
N/A: version "10.4.0 -> N/A" is not yet installed.

You need to run "nvm install 10.4.0" to install it before using it.

What did you expect to happen?
nvm should have automatically installed 10.4.0 if it wasn't already installed.
It would be great if use, run & exec provided options for automatically installing the targeted node version if it's not already installed.  I'd expect the option to be --install/-i.  It would also be nice if a --silent/-s option were supported for silent installation.  That way, a user could issue the command nvm run -is 10.4.0 blah.js and nvm would silently install 10.4.0 if it wasn't there then run the command.  Running nvm run -is blah.js would silently install & use the node version according to .nvmrc.

nvm use --install isn't a thing; nvm install already does "install if needed + use".
Supporting --silent on nvm install seems somewhat reasonable, but i'm not excited about silently installing a node version that doesn't get cleaned up later.

@ljharb I don't see the big deal WRT clean up.  I have many nvm-managed node versions.
However, if you wanted to, you could make the default behavior to be to remove the installed version after execution, and let users pass a flag to opt out of automatic cleanup with a --no-remove option or something.
The point of my request is really just to reduce the number of commands that have to be run.  I just want to nvm run blah.js and it should Just Work™ without me having to install the targeted Node version or not in a separate step.

I'm not sure why nvm install && nvm run blah is all that much harder?

It's just more to type, that's all.


support Namespace and change Web UI to support

Let's support Namespace.
I think it requires a big Web UI design change, because all resources are now created on the same namespace. We need to change Web UI to make it easier to understand which namespace each resource resides in.

/kind feature

Hello, again. if no one working on it, I'd like to try it!
For backend side, I have an image for this implement like as follows.

Add namespace service that has Get, List, Apply and Delete method, same as node or pod
Change some method for namespaced resources to pass namespace info to them

Is my understanding almost correct?

Hi @momom-i.
This issue is not started. Please feel free to assign yourself with /assign
Yeah, your thought is right, but I feel the development for this issue should be done after #95.
After #95, we don't need to change the backend and can create/edit/delete namespaces by requesting kube-apiserver directly.

Thank you! I understand, so first I'm trying to work on #95 and then if it works, will be back on this issue later.

Hi @momom-i✋
Are you currently working on this?
Would you like me to take it on?

@196Ikuchil Hi! No, I'm not working on it so you can take this freely.
@sanposhiho I've been a bit busy right now, but I'd like to contribute to this project. So I hope I can be back in the near future and we can work together :)

@momom-i Thanks for the reply👌 Have a good GW.
/assign

implementation tasks:

[ ] Design how to show Pods on namespace

I, personally, think it's difficult to show on current Web UI 😓 . And given the current web UI may be deprecated, just add namespace column on table views is enough..?

[ ] support namespace as other resources.

create namespace store, API client functions for namespace... etc

@sanposhiho
For about #161.
Sorry for the lack of explanation.
I'm not talking about client.
When we use the importing function, some namespaced resources may belong to various namespaces.
And if we operate these resources (e.g. Delete), we call our API directory from web UI. Therefore, the namespace must also be registered with the API
The importing function call Apply method on each ResourceService (e.g. PodService).
So, I think that we must do register the namespace if it is new before applying.

And also there is another bug.
We can't use metav1.NamespaceAll in call DeleteCollection method.
if err := s.podService.DeleteCollection(ctx, metav1.NamespaceAll, lopts); err != nil {
    return xerrors.Errorf("failed to delete pods on node %s: %w\n", n.Name, err)
}

https://github.com/kubernetes-sigs/kube-scheduler-simulator/pull/137/files#diff-375d57e386f20eaa5f09f02bb9d28bfc48ac3dca18d0325f59492208219e5618R112
Therefore, I think it needs to be modified to check all namespaces recursively.
This issue will be resolved in #162.

/triage accepted
Not to mark as stale.

/area web

Design how to show Pods on namespace
I, personally, think it's difficult to show namespace on current Web UI 😓 . And given the current web UI may be deprecated, just add namespace column on table views is enough..?
support namespace as other resources.
create New Namepace button, namespace store, API client functions for namespace... etc
https://github.com/kubernetes-sigs/kube-scheduler-simulator/issues/84#issuecomment-1119312105

The first one, I think is related to the table view which is the alpha feature on the web. We wouldn't need to spend any time discussing it if the feature is adopted early.
The second one is a basic function and should be implemented as soon as possible.

/remove-lifecycle rotten
/lifecycle frozen

This issue already has been resolved in #236
/close


Fixed the variable names in the powershell script

Fixed the variable names in the powershell script

@dixitsuneel The format you gave is PS but the format in the docs is Bash formatting (using Cloud Shell Bash mode). #please-close

Thank you. I didn't realize that.


MB-5002 enable gomodguard check

Description
From time to time deprecated packages are accidentally imported. This PR enables gomodguard in golangci-lint to check for these and return an error.
Reviewer Notes
To get golangci-lint to run gomodguard I needed to upgrade to the latest version. This also revealed some gosec errors that had not been reported by the old version.
Count Rule Description
01 G304 File path provided as taint input
01 G306 Poor file permissions used when writing to a new file
15 G307 Deferring a method which returns an error
07 G402 Look for bad TLS connection settings
08 G404 Insecure random number source (rand)
44 G601 Implicit memory aliasing of items from a range statement

Setup
Import one or all of the following and ensure that pre-commit flags the errors when creating a commit or when run manually
Run golangci-lint on all files
pre-commit run -v --all-files golangci-lint

Code Review Verification Steps

[X] Request review from a member of a different team.
[X] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change
this slack thread explains more about the approach used.
this slack thread

Messages

:book:
:link: MB-5002

  Generated by :no_entry_sign: dangerJS against 0605d22ee7277f95d4f6e48df182e479f8ca146e

Thanks for getting this new linter in there and raising the issues the new golangci-lint version found. I noticed that you deleted the make_blackout_date.go because I assume it wasn't used anymore, but I also still see the model and see it used in the assertion struct. You may not want to deal with that in this PR, but can we make a story to purge that?

Yes I couldn't find any calls to the functions in make_blackout_date.go so I removed it. The model is only used in the assertions so I'll clean that up here too since I don't have an approval yet.

Also, I was curious about the nature of the change in random_sequencer.go.

Replied to that comment directly

Will we still be making the stories to review each of the types of the errors?

I didn't have time yesterday to make the stories, I will check with @kimallen and @donaldthai first though since they are reviewing all the violations this month too. I don't want to duplicate the work.


[Fix-3324][master] Fix master task dependency check bug

What is the purpose of the pull request
Fixes #3324
Brief change log
Just change the function (in MasterExecThread.java) which is for checking task dependency.
Verify this pull request
This pull request is already covered by existing tests, such as master test.

Hi,
Please change the title to [Fix-3324][master] Fix master task dependency check bug. Thx a lot~

Hi,
Please change the title to [Fix-3324][master] Fix master task dependency check bug. Thx a lot~

No problem. And  I've found that there's another fix plan, so need I close this issue?

Hi,
Please change the title to [Fix-3324][master] Fix master task dependency check bug. Thx a lot~

No problem. And I've found that there's another fix plan, so need I close this pull request?

You can confirm with the another issue's author.

Hi,
Please change the title to [Fix-3324][master] Fix master task dependency check bug. Thx a lot~

No problem. And I've found that there's another fix plan, so need I close this pull request?

if you want, You can still submit your code.


Community Partner user error

throws an error when trying to update community partner user

@shashankpatibandla Please test this. I believe it is fixed based on last night's discussion.

@jerrodanzalone I can replicate the same error in sta. Is this not pushed yet to sta and can I check with whoever fixed this?

@EdemD Same note as 1037 :)

Roger

@EdemD Please test the profile picture as well. It should give a error when the picture is above 600*600 pixel or more than 10mb in size. The same with 1037. Thanks


Fix build and add CI so the build won't break again

Sorry About My Mess of a pull request
Also the super.markRemoved() call seems to have disappeared from TextBlockEntity thats not Good

wagh


Failures on [ddc] Refactor _isSubtype...[dart2js] dart format --fix in serialization/

There are new test failures on [ddc] Refactor _isSubtype...[dart2js] dart format --fix in serialization/.
The tests
pkg/vm/test/incremental_compiler_test RuntimeError (expected Pass)

are failing on configurations
unittest-asserts-release-mac-arm64

Here is a log of the failure https://logs.chromium.org/logs/dart/buildbucket/cr-buildbucket/8835535925485368977/+/u/test_results/new_test_failures__logs_

//cc @jensjoha could you tell us why the incremental_compiler_test is failing on unrelated changes ?

Looks similar to https://github.com/dart-lang/sdk/issues/46450.

I have no real insight here --- worth noticing, though, is that it's in _computeMainId on line return isolates.first['id']; that it fails.
Maybe _computeMainId should be updated to (upon failure) wait a little and try again.
It seems to me that the interaction goes something like "launch vm, connect via observatory, execute getVM, and that this then doesn't return any isolates, so probably the VM isn't ready yet?

Duplicate of #46450.  Another problem, besides the test flaking, is that this flakiness is not detected on the CI, because on each CI run, the test either always fails or always passes all the deflaking runs.  I can mark this test as flaky manually, and have been looking at making a tool to do this.  Closing as duplicate.


Fix Bigquery ADC project id overriding

Describe your changes :

Fixes ADC Bigquery Project ID issue where project id doesn't get  overriden if we use ADC

Type of change :

[x] Bug fix
[x] Improvement
[x] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Frontend Preview (Screenshots) :
For frontend related change, please link screenshots of your changes preview! Optional for backend related changes.

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers

@open-metadata/ingestion

Merging this as cypress failing are not related to this PR


feature: Add new cache refresh tasks

Adding new gh > cache command that allows the user to clear specific caches e.g just repos.
Trying to get GH Actions and Semantic Release to handle the whole release process

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add IP checking for incoming callback requests without keys

I don't understand this "fix". Can you please explain?

It changes logic of incoming checking. callbackUrl has order_id and order_key to verify requests. But old versions of plugin didn't have this check. So we check the request by IP address.

It changes logic of incoming checking. callbackUrl has order_id and order_key to verify requests. But old versions of plugin didn't have this check. So we check the request by IP address.

But we only throw an exception if the IP address is different from <IP_ADDRESS>? Why? What does that IP address represent?

It changes logic of incoming checking. callbackUrl has order_id and order_key to verify requests. But old versions of plugin didn't have this check. So we check the request by IP address.

But we only throw an exception if the IP address is different from <IP_ADDRESS>? Why? What does that IP address represent?

There's the method where implemented incoming callback request handler. We should ensure that there's request from payex side (not hacker who can make fake requets to mark order "paid" as example). This ip from payex side.

I see. But shouldn't we just ignore requests coming from an IP other than <IP_ADDRESS>, then?

I see. But shouldn't we just ignore requests coming from an IP other than <IP_ADDRESS>, then?

That's a good idea. Can you clarify which IPs does payex use for that? Is that the same for test and prod envs?

That's a good idea. Can you clarify which IPs does payex use for that? Is that the same for test and prod envs?

I believe the IP is the same for both environments, but I'll investigate. Can you do a quick test in external integration and see which IP you get request from there?

@aait, I've investigated and we have the same outgoing IP address from both production and external integration (test).


Note that dhparam does support X9.42

Fixes: #13151

This interface is legacy as far as I am concerned.. There are 4 type of DH keygen (this only does 2 of them).
Using genpkey with a named group should be the recommended way for DH.

Thoughts for what it should say?  It would be funny but adding "This command itself is superseded by genpkey (perhaps with a named groups) and XXX" right after the "replaces" sentence. :)  Happy to do that, XXX is what?

Something like:
See L<openssl-genpkey(1)/EXAMPLES> to Generate a DH key using a named safe prime group without generating intermediate parameters.
The FIPS186-4 code is really a deprecated usecase - so probably not even worth mentioning.

Thanks @slontis, made some changes and pushed an updated commit.

This pull request is ready to merge

Merged to master, thanks.


[python] College Algebra Word Problems page numbers

Describe the Issue
Assignments are given as:

Assignments
Complete the problems on pages 63, 75, 85, and 118 from "Business Math, a Step-by-Step Handbook (2021)".
Complete the problems on pages 304, 308, and 321 from "Algebra and Trigonometry".

In the video page 304 is listed as "304" but also 322 of that document. In my PDF https://assets.openstax.org/oscms-prodcms/media/documents/Algebra-and-Trigonometry-2e-WEB.pdf This question about skiing is on page 353 of the book or page 363 of my PDF.
The problem is that all of these referenced page numbers are different. I was able to find the question by searching for "skiing" in the text. It's not even clear if we are to solve just the word problems or all of the problems on this page? The section is "word problems" but in the video they go over other problems as well.
There's also the online version which has no page numbers at all: https://openstax.org/books/algebra-and-trigonometry-2e/pages/4-1-linear-functions
I would suggest to refer to the questions explicitly by section and question # which are more consistent. For example:

Complete problems 1 - 5 in section 4.1 of "Algebra and Trigonometry".

Affected Page
https://www.freecodecamp.org/learn/college-algebra-with-python/learn-applications-of-linear-systems/word-problems
Your code

NA

Expected behavior
NA
Screenshots

System

Device: [e.g. iPhone 6, Laptop] NA
OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04]
Browser: [e.g. Chrome, Safari]
Version: [e.g. 22]

Additional context
No response

Hey @pkdvalis,
It seems you will need the 2021 version of the textbook. I assume you have the revisioned 2023 textbook. Is that correct?

Thank you for bringing this to our attention, we hope to resolve this soon.
The version of the books have been updated.


Migrate the path_provider plugin to null safety.

Internal bug: http://b/177908022
This is one of the blocking migrations that need to happen before a number of internal packages can be migrated to null safety.

Hi @enetor Could this issue be open until path_provider is fully migrated? It will be useful for others who want to track its progress.

Hi @enetor Could this issue be open until path_provider is fully migrated? It will be useful for others who want to track its progress.

Hi @enetor Could this issue be open until path_provider is fully migrated? It will be useful for others who want to track its progress.

Same here!

Hi @enetor Could this issue be open until path_provider is fully migrated? It will be useful for others who want to track its progress.

Same here!


Add file change messages in watch mode, so that a vscode lint task can be configured.

Hi dear maintainers,
Thanks for all your hard works to this awesome project, it makes following good coding style easier.

It would be great to configure a vscode lint task for Solidity with Solium watch mode, so any style error would be instantly shows up in editor on file change.
To achieve that, Solium needs proper linting begin and end messages so that vscode problem matcher can capture the updated style errors.
Currently, the output of solium --file Bounty.sol --watch --reporter=gcc looks like:
*************************************************

Bounty.sol:11:0: warning: ContractStatement 'Bounty' must be preceded by a 2-line gap.

it starts with 49 '*'s and ends with nothing.
Ideally, messages with clear begin and end patterns ...
File change detected. Start linting.

Bounty.sol:11:0: warning: ContractStatement 'Bounty' must be preceded by a 2-line gap.
Linting complete. Watching for file changes.

... make linting task easier to be configured like this
"beginsPattern": "^File change detected\\. Start linting\\.$",
"endsPattern": "^Linting complete\\. Watching for file changes\\.$"

So here's my fork and source code change, if that does not break anything I can send a PR right away.

@ChihChengLiang changes merged, this is extremely helpful, thanks! :D

Solium v1 makes this available.
npm install -g solium@v1-beta
http://solium.readthedocs.io/en/latest/


[Bug](point query) cancel future when meet timeout in PointQueryExec

Proposed changes

cancel future when meet timeout and add config to modify rpc timeout
add config to modify numof BackendServiceProxy since under high concurrent work load GRPC channel will be blocked

…rrent workd load BRPC channel will be blocked frenquently
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 54.28 seconds
stream load tsv:          500 seconds loaded<PHONE_NUMBER>9 Bytes, about 142 MB/s
stream load json:         19 seconds loaded<PHONE_NUMBER> Bytes, about 118 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          30 seconds loaded 861443392 Bytes, about 27 MB/s
insert into select:          86.8 seconds inserted 10000000 Rows, about 115K ops/s
storage size:<PHONE_NUMBER>0 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230706170314_clickbench_pr_173565.html

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 48.24 seconds
stream load tsv:          441 seconds loaded<PHONE_NUMBER>9 Bytes, about 161 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          56 seconds loaded<PHONE_NUMBER> Bytes, about 18 MB/s
stream load parquet:          28 seconds loaded 861443392 Bytes, about 29 MB/s
insert into select:          70.0 seconds inserted 10000000 Rows, about 142K ops/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230706091915_clickbench_pr_173562.html

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 50.75 seconds
stream load tsv:          498 seconds loaded<PHONE_NUMBER>9 Bytes, about 143 MB/s
stream load json:         19 seconds loaded<PHONE_NUMBER> Bytes, about 118 MB/s
stream load orc:          64 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          87.2 seconds inserted 10000000 Rows, about 114K ops/s
storage size:<PHONE_NUMBER>9 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230706181850_clickbench_pr_173652.html

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 50.24 seconds
stream load tsv:          449 seconds loaded<PHONE_NUMBER>9 Bytes, about 158 MB/s
stream load json:         21 seconds loaded<PHONE_NUMBER> Bytes, about 107 MB/s
stream load orc:          57 seconds loaded<PHONE_NUMBER> Bytes, about 18 MB/s
stream load parquet:          30 seconds loaded 861443392 Bytes, about 27 MB/s
insert into select:          68.8 seconds inserted 10000000 Rows, about 145K ops/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230706103256_clickbench_pr_173650.html

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 53.76 seconds
stream load tsv:          501 seconds loaded<PHONE_NUMBER>9 Bytes, about 142 MB/s
stream load json:         19 seconds loaded<PHONE_NUMBER> Bytes, about 118 MB/s
stream load orc:          64 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          30 seconds loaded 861443392 Bytes, about 27 MB/s
insert into select:          89.8 seconds inserted 10000000 Rows, about 111K ops/s
storage size:<PHONE_NUMBER>2 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230708224246_clickbench_pr_174930.html

run buildall

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 53.67 seconds
stream load tsv:          445 seconds loaded<PHONE_NUMBER>9 Bytes, about 160 MB/s
stream load json:         19 seconds loaded<PHONE_NUMBER> Bytes, about 118 MB/s
stream load orc:          56 seconds loaded<PHONE_NUMBER> Bytes, about 18 MB/s
stream load parquet:          30 seconds loaded 861443392 Bytes, about 27 MB/s
insert into select:          68.3 seconds inserted 10000000 Rows, about 146K ops/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230709120551_clickbench_pr_175209.html

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 52.71 seconds
stream load tsv:          499 seconds loaded<PHONE_NUMBER>9 Bytes, about 142 MB/s
stream load json:         19 seconds loaded<PHONE_NUMBER> Bytes, about 118 MB/s
stream load orc:          64 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          30 seconds loaded 861443392 Bytes, about 27 MB/s
insert into select:          86.8 seconds inserted 10000000 Rows, about 115K ops/s
storage size:<PHONE_NUMBER>8 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230709201838_clickbench_pr_175207.html


Upgrade notes for CI 2.0.1 in user guide don't mention migrations config file

http://codeigniter.com/user_guide/installation/upgrade_210.html needs to be updated to mention the creation of the migration.php config file as required by the library and explained in http://codeigniter.com/user_guide/libraries/migration.html

Duplicate of #748


Updated to click the firstVisibleElement

Earlier it seems like it was clicking the first element. Now it clicks the first visible element,
Motivation/Description of the PR

Description of this PR, which problem it solves
Resolves https://github.com/Codeception/CodeceptJS/issues/2226

Applicable helpers:

[ ] WebDriver
[ ] Puppeteer
[ ] Nightmare
[ ] REST
[ ] FileHelper
[ ] Appium
[ ] Protractor
[x] TestCafe
[ ] Playwright

Applicable plugins:

[ ] allure
[ ] autoDelay
[ ] autoLogin
[ ] customLocator
[ ] pauseOnFail
[ ] puppeteerCoverage
[ ] retryFailedStep
[ ] screenshotOnFail
[ ] selenoid
[ ] stepByStepReport
[ ] wdio

Type of change

[ ] :fire: Breaking changes
[ ] :rocket: New functionality
[x] :bug: Bug fix
[ ] :clipboard: Documentation changes/updates
[ ] :hotsprings: Hot fix
[ ] :hammer: Markdown files fix - not related to source code
[ ] :nail_care: Polish code

Checklist:

[ ] Tests have been added
[ ] Documentation has been added (Run npm run docs)
[ ] Lint checking (Run npm run lint)
[ ] Local tests are passed (Run npm test)

Thank you!


git fetch --tags, or how to have CI working

Currently I believe tags have to be pushed, something like:
git clone https://github.com/duckdb/duckdb
cd duckdb
git fetch --tags
git remote add your_remote  PATH/TO/REMOVE
git push your_remote v0.8.0

is needed to have CI work properly, possibly something else also.
Unsure whether this is docs or main repo issue, but for now it could be for sure patched by documenting what's expected.
This came up at various times, like https://github.com/duckdb/duckdb/pull/7864 or with new devs.

Seems to already be documented on main repo:
https://github.com/duckdb/duckdb/blob/master/CONTRIBUTING.md#testing

Thanks, I had not looked for it in the most obvious place.
I also find the explanation is somehow misleading / could be improved (as in if default remote is yours, then I'd say you pull from duckdb/duckdb).
I still think some end-to-end guide, ideally mostly via code snippets, could be useful for newer contributors (both external and internal), and seems significative enough to be present both in docs AND contributing.

Let's revisit this sometime soon. What sort of built guide do we want to provide as part of the docs?
Currently, we have this: https://duckdb.org/dev/building

@Mytherin we should probably only have one place where we document dev info, either website or markdown in repo. either is fine with me


Ethnic Category Code - missing de default code

ETHNIC_CATEGORY_CODE:

Has extra codes
The codes are now on the Data Element, but the extra codes are still incorrectly in the list

Data item updated - all attribute codes now showing correctly....However - loss of meaning with headings omitted. One for a patch update and do we worry about history?

Also note - default code on ETHNIC_CATEGORY de is missing from beta

Headings for this item can be omitted from beta

Next step is to check why default code is missing.

Hi Likin - please check why default codes have not been passed along in the knitted txa file for Ethnic_Category

Newly split items (to avoid the historic default code clashes) are still not being sent to ontoserver (Oct 2020). Bespoke handling will be needed.

21/06/2021 - in progress.

Still outstanding.

Hi Angela,
Can you please let me know what is missing and where. I have checked it on my end and it seems fine to me

Awaiting Maxine response from Angela's email.

Discussed with Likin - de-prioritised until branch migration work is completed.

From Maxine 28/1/22:
Put these in the backlog for now. Likin has been prioritised towards enabling branch migration and CR migration ahead of any tickets re FHIR gen history. Ideally – these will be addressed pre migration – Only post migration if we really have to.

Hi ,as per my last comment above. No default code is missing. There is no default code 'de' is present. Hence closing the issue

16/05/22 - confirmed with Maxine that this is OK to be closed.


Update README.md

standalone edited

Sorry for the late reply and thanks for the contribution. New hub versions will ship with an installer script that will take care of this for you automatically!


Windows: visibility of anaconda installation in the git bash

Windows users who install Anaconda need to start the Anaconda shell to see the Python packages. But if they start the Git bash, they don't see these unless they edit the PATH. We need to describe how to do that or make that smoother.

+1
Also anaconda has git according to the windows package list. No bash, though, so we probably don't want to fully use anaconda for git talks too.

I think this is now solved in https://coderefinery.github.io/installation/troubleshooting/.


Add CircleCI configuration

tests
semantic-release

We have travis. Just need to fix semantic-release.


Password with symbols can cause errors parsing rally.ini file

Rally version: 0.11.0
OS version: Ubuntu 16.04
Description of the problem including expected versus actual behavior:
I specified an Elastic Cloud cluster as the metrics store and picked a password that contained a $ followed by a character. This resulted in the following error when I tried to run the eventdata track:
Traceback (most recent call last):
  File "/usr/local/bin/esrally", line 11, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.6/site-packages/esrally/rally.py", line 588, in main
    ensure_configuration_present(cfg, args, sub_command)
  File "/usr/local/lib/python3.6/site-packages/esrally/rally.py", line 428, in ensure_configuration_present
    cfg.load_config(auto_upgrade=True)
  File "/usr/local/lib/python3.6/site-packages/esrally/config.py", line 206, in load_config
    self.migrate_config()
  File "/usr/local/lib/python3.6/site-packages/esrally/config.py", line 239, in migrate_config
    migrate(self.config_file, self._stored_config_version(), Config.CURRENT_CONFIG_VERSION)
  File "/usr/local/lib/python3.6/site-packages/esrally/config.py", line 588, in migrate
    .format(config_file.location, PROGRAM_NAME))
esrally.config.ConfigError: ('The config file in /home/ubuntu/.rally/rally.ini is too old. Please delete it and reconfigure Rally from scratch with esrally configure.', None)

It looks as if this problem is caused by something else. The error message says:

The config file in /home/ubuntu/.rally/rally.ini is too old. Please delete it and reconfigure Rally from scratch with esrally configure.

We recently dropped support for ancient config file format versions (i.e. config.version < 12) and this is why it fails. I suggest you reconfigure Rally with esrally configure --advanced-config and retry.

Sorry. Must have copied the wrong stack trace. I now configured it locally using the configure utility and got the following:
esrally
Traceback (most recent call last):
  File "/usr/local/bin/esrally", line 11, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.6/site-packages/esrally/rally.py", line 580, in main
    arg_parser = create_arg_parser()
  File "/usr/local/lib/python3.6/site-packages/esrally/rally.py", line 107, in create_arg_parser
    cfg.load_config()
  File "/usr/local/lib/python3.6/site-packages/esrally/config.py", line 204, in load_config
    self._do_load_config()
  File "/usr/local/lib/python3.6/site-packages/esrally/config.py", line 214, in _do_load_config
    self._fill_from_config_file(config)
  File "/usr/local/lib/python3.6/site-packages/esrally/config.py", line 233, in _fill_from_config_file
    self.add(Scope.application, section, key, config[section][key])
  File "/usr/local/Cellar/python/3.6.5/Frameworks/Python.framework/Versions/3.6/lib/python3.6/configparser.py", line 1234, in __getitem__
    return self._parser.get(self._name, key)
  File "/usr/local/Cellar/python/3.6.5/Frameworks/Python.framework/Versions/3.6/lib/python3.6/configparser.py", line 800, in get
    d)
  File "/usr/local/Cellar/python/3.6.5/Frameworks/Python.framework/Versions/3.6/lib/python3.6/configparser.py", line 455, in before_get
    self._interpolate_some(parser, option, L, value, section, defaults, 1)
  File "/usr/local/Cellar/python/3.6.5/Frameworks/Python.framework/Versions/3.6/lib/python3.6/configparser.py", line 518, in _interpolate_some
    "found: %r" % (rest,))
configparser.InterpolationSyntaxError: '$' must be followed by '$' or '{', found: '$tPa$$word'

Thanks for reporting. Now I could reproduce it. Fixed in #524 and scheduled to be released with 1.0.0.