Migrate to ESLint plugin.

http://eslint.org/blog/2016/04/welcoming-jscs-to-eslint

Let us know how we can help

https://github.com/jonathanKingston/ember-cli-eslint
Aren't this and the repo above now slowly moving in  same direction? In the end both will be using ESLint.

@raido - No, these projects are not at odds. ember-cli-eslint is providing the engine to run eslint rules within ember-cli, this project aims to provide a set of suave rules for your project.  Either way, ember-suave requires an engine to run the rules in (we use broccoli-jscs to run JSCS rules today and will use ember-cli-eslint to run rules in the future).

@rwjblue: Got it :)

@rwjblue This is something I'd be interested in helping with, now that ember-cli-eslint is maturing.  How would you want to see this happen?  I'd imagine you would install ember-cli-eslint and ember-suave and it would "just work" from there... Is that your goal?

So, I'm not sure that it makes sense to turn this repo into an ESLint plugin. Don't they have to be standalone packages named eslint-plugin-*?
I'm leaning towards this:

Have a separate repo, called eslint-plugin-ember-suave or something. This would host all the custom rules and desired config.
This repo could then be its own Ember CLI addon that works in conjunction with ember-cli-eslint, by:

npm installing the eslint-plugin-ember-suave plugin
updating the project's .eslintrc.js and tests/.eslintrc.js files that ember-cli-eslint generates to use the plugin and extend from the plugin's config, something like:

module.exports = {
  plugins: ['ember-suave'],
  extends: [
    './node_modules/ember-cli-eslint/coding-standard/ember-application.js',
    'plugin:ember-suave/recommended'
  ],
  rules: {
    // This is where users can override ember-suave rules
  }
};

Yeah the equivalent of a jscs preset is a "eslint config" with the namespace eslint-config- which exports a eslintrc basically (I thought eslint-preset- works and it does but the shorthand way of using it doesn't).

For anyone curious, I've started a new repo that's porting over the rules one-for-one into ESLint.
https://github.com/alexlafroscia/eslint-plugin-ember-suave
Once the rules are equivalent, I'm happy to transfer the repo over to Dockyard.

My repo (linked above) has the four custom rules that this repo contains, with the same test cases, all passing.  My test infrastructure isn't quite as robust as what you use here, but ESLint provides a setup for testing rules so I just stuck with the defaults for now.  I'm thinking about ways to have the tests in ESLint run the same was as these, where you can just add a .js file to the right folder and it will be tested as valid/invalid automatically.
I do have a further question about the tests, though; why are there tests for so many of the built-in rules?  Is that something that you want the new ESLint package to also do?  It is just to show what the rules will pass and fail on?  ESLint provides pretty clear docs for their rules on their website, so if that's the reason, maybe having tests run for all of them can be avoided?
I think the next task is to port jscs-ember-deprecations over to ESLint as well, if that's something that should still be part of ember-suave.

why are there tests for so many of the built-in rules?

Many of them were not always built-in, we created them then the JSCS team pulled them into the upstream repo.

Also, the tests were meant to ensure that ember-suave had the correct rules enabled or configured per DockYard's styleguide. I think the way you have set up the tests in the plugin repo itself should be fine though.

I think the next task is to port jscs-ember-deprecations over to ESLint as well, if that's something that should still be part of ember-suave.

I have been wanting to drop support for it, given exactly what you said: it hasn't been maintained.
Thank you so much for working on this issue by the way! I will take a look at the plugin repo you created and create an eslint branch on ember-suave that integrates it.

@rwjblue I see, that makes sense.
@brzpegasus sure thing; I love Suave and ESLint so this was something I've been wanting to do for a while, even before JSCS and ESLint got pulled together.  Plus it's been a great opportunity to learn more about writing ESLint rules, which I've never really done.

Just figured I would drop this link in here; I think you'll want to provide a shareable config for Ember Suave with all of your favorite rules turned on.  It seems really verbose to have it in a separate repo than the rules, but the ESLint convention seems to be custom rules in an eslint-plugin-foo repo and custom configs in an eslint-config-foo repo.

Just as an update: I added a "recommended" config, just like @brzpegasus described, at plugin:ember-suave/recommended.  I don't know if it's a perfect port, but I started converting the rules from JSCS to ESLint by hand and realized it was going to take too long, so I just used Polyjuice to do it.  It doesn't include any of the ember-deprecations rules, but should, in theory, cover all of the ESLint default and ember-suave custom rules.

@alexlafroscia I'm experimenting with an eslint-config-ember-suave that sets up all the config for the built in rules, as well as the custom rules from your plugin. The idea is that the ember-suave config would bring together all the rules from various places: eslint (defaults), the custom rules from the suave plugin, and possibly rules from other third-party plugins, as applicable in the future. As such, I think it'd be preferable to leave out the config from the suave plugin you created.
I've also created a local branch that has ember-suave install the blueprint from ember-cli-eslint, so that it can then update it with the suave config.
I'm just running into some npm dependency issues at the moment because the plugin has to be a top-level dependency, not just a dependency of eslint-config-ember-suave (must be a peer dependency, essentially). I could also drop the config repo altogether and just have ember-suave hosts the config file but then users would have to reference the config using require.resolve('ember-suave/config/index.js') or something. I suppose that wouldn't be so bad either.
Still a WIP but that's the update.

@alexlafroscia Feel free to post new comments rather than editing your previous posts by the way. Otherwise, I don't get notified when you post an edit.

Sorry about that, just didn't want to be too noisy here.
I'm curious about the difference between having an eslint-config-ember-suave repo and having a config within the plugin, like I have set up now. I personally feel like having three repos for Suave is a lot; is there a benefit to splitting the config out into its own repo?

I'm curious about the difference between having an eslint-config-ember-suave repo and having a config within the plugin

Right now, the plugin defines a set of custom rules, but the config that lives in that repo isn't just for those custom rules. It's for everything that we want to support. Let's say that in the future, we would like the config to enable custom rules that are defined in other plugins, I don't think we should have eslint-plugin-ember-suave pull in other plugins. I'd rather have the repo where the config is defined be the aggregator. It would pull in any custom rules that it needs from various sources, e.g.:
  plugins: [
    'ember-suave', // for custom rules not defined anywhere else
    'foo-plugin',
    'bar-plugin'
  ]

I agree that having 3 different repos seems excessive. We could technically get away with just having an eslint-config-ember-suave for the "preset", and eslint-plugin-ember-suave for the custom rules, and they could be used by any ESLint-enabled tool even outside of the Ember addon realm (see #126). The only benefit of having the ember-suave addon at this point is so that it would do the npm install and ESLint configuration steps for you instead of you manually setting up ember-cli-eslint, then eslint-config-ember-suave, then update .eslintrc.js in both the project root and tests folder.
The alternative that I mentioned, which would reduce the number of repos involved, is to simply host the config file within the ember-suave addon itself. We'd still keep eslint-plugin-ember-suave around for when we need to define custom rules. But the config file in that case would look more like this:
  plugins: [
    require.resolve('ember-suave/lib/config/index.js'),
    'foo-plugin',
    'bar-plugin'
  ]

Thoughts?

I don't think we should have eslint-plugin-ember-suave pull in other plugins

Yeah, I suppose that does make sense.  At the same time, I'm not sure there's a reason not to have it pull in or configure others, especially when it's pretty easy to turn off any of that behavior that you're not interested in.
If the config is going to live outside of the plugin, then I think it should have it's own config repo that matches the pattern of the ESLint community.  Better to go with the convention, and I like the idea of other projects being able to use the configuration if they want to.
I think the idea of the ember-suave addon simply running some installation steps for the other packages a little strange.  Assuming the user already is using ember-cli-eslint, they'll likely already have .eslintrc.js files in place.  I feel like it would be just as easy to have people just install ember-cli-eslint and add the one plugin:ember-suave/recommended to their configuration; that's all they need to do.

@alexlafroscia I'm going to stick to my original suggestion of having the recommended config inside eslint-plugin-ember-suave (basically what you ended up implementing). I agree it does simplify things. I had second thoughts for a while, so I consulted the experts, who confirmed that for the use case of sharing configs across projects within a company, hosting the entire config within the plugin is acceptable. That's essentially what ember-suave set out to be: a way to share config across Ember projects at DockYard. Even if others within the Ember community can benefit from it, it is easy enough to override or extend the config within their own projects.
Progress has been slow on my part so far (can be challenging with a 2-month old to take care of at the same time) but I really want to get this over the finish line sooner rather than later. I might try to recruit other DYers to complete any missing rules as needed as well, since we'll want to use it on our next projects.

I'm happy to transfer the repo over to Dockyard

This would be greatly appreciated. We'll certainly make sure to give you credit and we'll be happy to continue accepting contributions from you!

We'll certainly make sure to give you credit and we'll be happy to continue accepting contributions from you!

Sounds good to me!  I'll set up the transfer now.  Who should I transfer the NPM package to?

Can you transfer to my GH account, then I can transfer to DockYard?
For NPM, it can go to edeblois.

Maybe we can work together on coming up with a master list of what's missing

👍

Alright, I initiated the transfer of the Github repo to you, and added you as an owner on NPM and removed myself (since I figured you don't want me to retain publishing access on NPM).

What can I do to help you guys with this effort?

@rwwagner90 this issue has a list of rules that existed in the JSCS version but do not (as far as I can tell) have an existing, built-in ESLint equivalent.  One of the major tasks left at this point is going through the ones that are left and either finding an ESLint rule that can be configured to cover it or implementing the rule ourselves.  Finding an existing third-party plugin might also be an appropriate solution but you'd have to talk to @brzpegasus about that, we might want to just keep the rules limited to built-ins or ones in that repo.

I believe we have ported everything to ESLint, have we not @alexlafroscia @brzpegasus?

As far as I know, yes. Only things that come to mind are dropping babel-eslint and that generator thing. IMO the generator spacing issue is a non-blocker on a switch but, since this is really the Dockyard style guide, it's their call.

I've been using the ESLint version across a few apps and addons (like Ember AJAX) and it's been great.

The generator styling is not a blocker by any means. In fact, if the eslint team does not think it is worth supporting the config, then it is probably worth revisiting our stance on it rather than creating a custom rule for a style that does not reflect widespread usage.
The repo can be used as it currently stands. I just need to remove the parser config (defaulting to Espree) and update documentation in light of some recent changes in ember-cli-eslint but nothing that should hold up the switch.
FWIW, I return to work next week from my extended leave, so there should be more activity from me in the near future.

btw: https://github.com/eslint/eslint/issues/6053 will cover array/object destructuring as part of the JSCS Compatibility Milestone

The plugin now exists as eslint-plugin-ember-suave.


chore: Simplify CI and Releases

Condenses the CI and Release workflows into a single workflow called "CI" that:

golang-lints for each PR, commit to main and tags
runs tests for each PR, commit to main and tags
releases on tag creation with GoReleaser

Also adds a brews stanza to the GoReleaser configuration that updates the Homebrew definition for subo, automatically. This update mechanism does not allow the tap to build from HEAD/source. This is different than how Homebrew traditionally structures its Formulae, but is more effective at shipping the pre-built binaries without requiring others to have Go installed and compile from source (like we do  now).

Oh, one more question. Will it push to the main branch of the homebrew repo, or open a PR?

@javorszky It will just push: https://github.com/goreleaser/goreleaser/issues/2870


FYI: this is not Meteora in Greece

http://www.bing.com/az/hprichbg/rb/Meteora_EN-US6763889417_1920x1080.jpg
This is not Meteora in Greece ...

Sorry but this library simply reflects whatever the Bing API returns. There's no way to control the output...
The API is available under a link like the following:
https://www.bing.com/HPImageArchive.aspx?format=js&idx=0&n=1&mkt=en-US


Implements a proxy, serving content from gatsby and functions

What is the purpose of this pull request?
It adds a proxy server to serve the Gatsby store and functions from the same server, using the same port
What problem is this solving?

We need to support serverless functions on StoreFramework JAMStack. This PR allows developers to test their functions locally in a similar environment we will provide on production.
How should this be manually tested?
You will need a Gatsby store with a directory api containing functions. You can use this project as an example: vtex-site/storefaas.store.

Clone this repo (cli-plugin-functions) and run yarn link.
Clone vtex/toolbelt, switch to add/serverless-functions.
Now run yarn link @vtex/cli-plugin-functions on the vtex/toolbelt project, and install other dependencies running yarn.
Run yarn watch on the vtex/toolbelt
Test the command on a Gatsby store with vtex-test functions

Screenshots or example usage
Run vtex-test functions on a Gatsby store with functions.
It will create three servers:

http://localhost:3000, the Express functions server
http://localhost:8000, the Gatsby server
http://localhost:8080, the proxy server

The proxy server will rewrite ^/functions/ to / on the functions server. Any other path will have its request forwarded to the Gatsby server.
Types of changes

[ ] Refactor (non-breaking change that only makes the code better)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Requires change to documentation, which has been updated accordingly.

Chores checklist

[ ] Update CHANGELOG.md

Very nice work you've doing, @rodorgas, congratulations!
I'm curious if you've considered using koa instead of express for this and why did you end up choosing express. It's my framework-of-choice, but using koa wouldn't make it easier to eventually migrate plain-old-vtex-io-services to this new model (not sure if you're going for it)?
Again, congrats 🎉

Very nice work you've doing, @rodorgas, congratulations!
I'm curious if you've considered using koa instead of express for this and why did you end up choosing express. It's my framework-of-choice, but using koa wouldn't make it easier to eventually migrate plain-old-vtex-io-services to this new model (not sure if you're going for it)?
Again, congrats 🎉

Thanks @lucis! I actually chose Express over Koa for no specific reason. I know that the request handlers are different between them, is there any others framework specific features that I should pay attention to?
The handler used in our functions follows the AWS Lambda signature function (event, context). If we were using Koa, I'd still have to translate function (ctx, next) to the Lambda pattern. On production, we won't be using either, since it will run directly on Lambda.
In future, we can also allow developers to specify which handler signature they want to use in a config file, just like Vercel lets us choose the Express handler (function (req, res)) or the Lambda handler.

Thanks @lucis! I actually chose Express over Koa for no specific reason. I know that the request handlers are different between them, is there any others framework specific features that I should pay attention to?
The handler used in our functions follows the AWS Lambda signature function (event, context). If we were using Koa, I'd still have to translate function (ctx, next) to the Lambda pattern. On production, we won't be using either, since it will run directly on Lambda.
In future, we can also allow developers to specify which handler signature they want to use in a config file, just like Vercel lets us choose the Express handler (function (req, res)) or the Lambda handler.


Fail to install with rancher/system-agent-installer-rke2:v1.21.3-rc6-rke2r2 image

I'm using the new rancherd to deploy RKE2 runtime for Harvester.
TodayI can't install RKE2, here is the log from rancherd:
Aug 18 03:22:32 node1 rancherd[1832]: time="2021-08-18T03:22:32Z" level=debug msg="Found index.docker.io/rancher/system-agent-installer-rke2:v1.21.3-rc6-rke2r2 in /var/lib/rancher/agent/images/rancherd-bootstrap-images.tar.zst"
Aug 18 03:22:32 node1 rancherd[1832]: time="2021-08-18T03:22:32Z" level=info msg="Extracting file installer.sh to /var/lib/rancher/rancherd/plan/work/20210818-032231-applied.plan/_0/installer.sh"
Aug 18 03:22:32 node1 rancherd[1832]: time="2021-08-18T03:22:32Z" level=info msg="Extracting file rke2.linux-amd64.tar.gz to /var/lib/rancher/rancherd/plan/work/20210818-032231-applied.plan/_0/rke2.linux-amd64.tar.gz"
Aug 18 03:22:32 node1 rancherd[1832]: time="2021-08-18T03:22:32Z" level=info msg="Extracting file sha256sum-amd64.txt to /var/lib/rancher/rancherd/plan/work/20210818-032231-applied.plan/_0/sha256sum-amd64.txt"
Aug 18 03:22:32 node1 rancherd[1832]: time="2021-08-18T03:22:32Z" level=info msg="Extracting file run.sh to /var/lib/rancher/rancherd/plan/work/20210818-032231-applied.plan/_0/run.sh"
Aug 18 03:22:32 node1 rancherd[1832]: time="2021-08-18T03:22:32Z" level=debug msg="Command was not specified, defaulting to /var/lib/rancher/rancherd/plan/work/20210818-032231-applied.plan/
_0/run.sh"
Aug 18 03:22:32 node1 rancherd[1832]: time="2021-08-18T03:22:32Z" level=info msg="Running command:  []"
Aug 18 03:22:32 node1 rancherd[1832]: time="2021-08-18T03:22:32Z" level=info msg="[stderr]: + mkdir -p /var/lib/rancher/rke2"
Aug 18 03:22:32 node1 rancherd[1832]: time="2021-08-18T03:22:32Z" level=info msg="[stderr]: + RESTART_STAMP_FILE=/var/lib/rancher/rke2/restart_stamp"
Aug 18 03:22:32 node1 rancherd[1832]: time="2021-08-18T03:22:32Z" level=info msg="[stderr]: + RKE2_SA_ENV_FILE_NAME=rke2-sa.env"
Aug 18 03:22:32 node1 rancherd[1832]: time="2021-08-18T03:22:32Z" level=info msg="[stderr]: + RKE2_SA_ENV_FILE_PATH=/usr/local/lib/systemd/system/rke2-sa.env"
Aug 18 03:22:32 node1 rancherd[1832]: time="2021-08-18T03:22:32Z" level=info msg="[stderr]: + RKE2_SA_ENV_SRV_REF=EnvironmentFile=-/usr/local/lib/systemd/system/rke2-sa.env"
Aug 18 03:22:32 node1 rancherd[1832]: time="2021-08-18T03:22:32Z" level=info msg="[stderr]: + '[' -f /var/lib/rancher/rke2/restart_stamp ']'"
Aug 18 03:22:32 node1 rancherd[1832]: time="2021-08-18T03:22:32Z" level=info msg="[stderr]: + '[' -n '2021-08-18 03:22:31.968427116 +0000 UTC m=+313.803182215' ']'"
Aug 18 03:22:32 node1 rancherd[1832]: time="2021-08-18T03:22:32Z" level=info msg="[stderr]: + '[' '' '!=' '2021-08-18 03:22:31.968427116 +0000 UTC m=+313.803182215' ']'"
Aug 18 03:22:32 node1 rancherd[1832]: time="2021-08-18T03:22:32Z" level=info msg="[stderr]: + RESTART=true"
Aug 18 03:22:32 node1 rancherd[1832]: time="2021-08-18T03:22:32Z" level=info msg="[stderr]: + env INSTALL_RKE2_ARTIFACT_PATH=/var/lib/rancher/rancherd/plan/work/20210818-032231-applied.plan
/_0 installer.sh"
Aug 18 03:22:32 node1 rancherd[1832]: time="2021-08-18T03:22:32Z" level=info msg="[stderr]: [WARN]  /usr/local is read-only or a mount point; installing to /opt/rke2"
Aug 18 03:22:32 node1 rancherd[1832]: time="2021-08-18T03:22:32Z" level=info msg="[stdout]: [INFO]  staging local checksums from /var/lib/rancher/rancherd/plan/work/20210818-032231-applied.
plan/_0/sha256sum-amd64.txt"
Aug 18 03:22:32 node1 rancherd[1832]: time="2021-08-18T03:22:32Z" level=info msg="[stdout]: [INFO]  staging tarball from /var/lib/rancher/rancherd/plan/work/20210818-032231-applied.plan/_0/
rke2.linux-amd64.tar.gz"
Aug 18 03:22:32 node1 rancherd[1832]: time="2021-08-18T03:22:32Z" level=info msg="[stdout]: [INFO]  verifying tarball"
Aug 18 03:22:32 node1 rancherd[1832]: time="2021-08-18T03:22:32Z" level=info msg="[stdout]: [INFO]  unpacking tarball file to /opt/rke2"
Aug 18 03:22:34 node1 rancherd[1832]: time="2021-08-18T03:22:34Z" level=info msg="[stdout]: [INFO]  updating tarball contents to reflect install path"
Aug 18 03:22:34 node1 rancherd[1832]: time="2021-08-18T03:22:34Z" level=info msg="[stdout]: [INFO]  moving systemd units to /etc/systemd/system"
Aug 18 03:22:34 node1 rancherd[1832]: time="2021-08-18T03:22:34Z" level=info msg="[stdout]: [INFO]  install complete; you may want to run:  export PATH=$PATH:/opt/rke2/bin"
Aug 18 03:22:34 node1 rancherd[1832]: time="2021-08-18T03:22:34Z" level=info msg="[stderr]: + '[' '!' -f /usr/local/lib/systemd/system/rke2-sa.env ']'"
Aug 18 03:22:34 node1 rancherd[1832]: time="2021-08-18T03:22:34Z" level=info msg="[stderr]: + install -m 600 /dev/null /usr/local/lib/systemd/system/rke2-sa.env"
Aug 18 03:22:34 node1 rancherd[1832]: time="2021-08-18T03:22:34Z" level=info msg="[stderr]: install: cannot create regular file '/usr/local/lib/systemd/system/rke2-sa.env': No such file or
directory"
Aug 18 03:22:34 node1 rancherd[1832]: time="2021-08-18T03:22:34Z" level=info msg="failed to bootstrap system, will retry: running plan: error executing instruction 0: exit status 1"

On my system, path /usr/local/lib/systemd/system/ doesn't exist. I can workaround by creating the directory on my won. But it would be great the run.sh script can also do that.

I guess the installation fails after this PR

@briandowns looks like we need to duplicate the logic to choose whether we use /usr/local/lib or /etc/systemd/system

I'll update this tomorrow morning.

according @briandowns and @Oats87, this is already fixed. im going to transfer this issue to rke2 project and move into proper milestone


refactor(headers): fix checkstyle on headers and configure error for header check

What this PR changes/adds
Fixes all checkstyle warning on file headers
Why it does that
Consistency in file headers and less warning when building and in the IDE
Further notes
List other areas of code that have changed but are not necessarily linked to the main feature. This could be method signature changes, package declarations, bugs that were encountered and were fixed inline, etc.
Linked Issue(s)
Closes #2322
Checklist

[ ] added appropriate tests?
[ ] performed checkstyle check locally?
[ ] added/updated copyright headers?
[ ] documented public classes/methods?
[ ] added/updated relevant documentation?
[ ] assigned appropriate label? (exclude from changelog with label no-changelog)
[ ] formatted title correctly? (take a look at the CONTRIBUTING and Etiquette for pull requests for details)

Those were actually wrong because the file where created in 2022.
Probably it' was my fault in previous PR with my configuration

I guess the regex is fine, since it checks the range from - to but since there was no blocker i was able to sneak wrong range from-to cause i had the wrong settings in Intellij. But for those files the modified in this PR the correct year is 2022


Enable ORC Writer for Spark

We already have the Spark ORC writer written - org.apache.iceberg.spark.data.SparkOrcWriter . We need to hook this up in Spark Datasource

@shawnding are you working on this issue?

Yes, I am working on this. now

@venkata91 Yes I am working on this.


Add WPS Office version <IP_ADDRESS>00

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

I know it is a duplicate of #20102 but testing if it works or not.


TypeScript-Urql generates invalid type for subscription handler with Operation Suffix config

Describe the bug
An addendum to #3062.
The generated subscription handler types for TypeScipt-Urql do not respect these config options:
  omitOperationSuffix: true
  operationResultSuffix: Data

The generated type with the above config is <OperationName>Subscription  when the expected type is <OperationName>Data.
To Reproduce
Add the above config options to your codegen.yml

@Pytal This issue needs reproduction. I tried to reproduce this, but it also depends on the operation name that you are using.

I think line 76 should be:
export function use${operationName}<TData = any>(options: Omit<Urql.Use${operationType}Args<${operationVariablesTypes}>, 'query'> = {}, handler?: Urql.SubscriptionHandler<${operationResultType}, TData>) {

Replacing Urql.SubscriptionHandler<${operationName} with Urql.SubscriptionHandler<${operationResultType}

Fixed in v1.15.2


Don't panic if command args are the wrong type

Coverage increased (+0.04%) to 70.186% when pulling e31aa73687932047d4790687a2c70fd4e2e3db76 on ricochet1k:fix-panic into 22a195acdf7457e8684596c47f70f943156bc9e0 on limetext:master.

LGTM.


feature: Allow setting new Cardinalities if they are more restrictive than the respective Cardinalities of a possibly existing super class

Pull Request Checklist
Task Description/Number

closes DEV-1563
All checks are done in the context of a class/property combination on which the new cardinality should be set.
Adds an ontology check for subclasses and super-classes so that the new cardinality is compatible, i.e. :

Ontologycheck:

The new cardinality must be included in the the respective cardinalities of the super-classes
The respective subclasses's cardinalities must be included in the new cardinality

Persistencecheck: A simple sanity check for persistent data which prevents incompatible changes: Either the property is not in use or the new cardinality on the class is included in the old cardinality of that class.

Given the property on the current class is not used the ontology check (1.+2.) is sufficient. Otherwise data might exist that possibly does not comply with the new cardinality. In this PR this is not a deeper check, in a later PR I will add a check which would allow to set a new cardinality in the case the the property on that class is in use and the new cardinality is not included in the old cardinality. In this case it could still be possible that the data complies with the new cardinality. This case is not possible in this PR but should later be enabled.
Basic Requirements
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix: represents bug fixes
[ ] Refactor: represents production code refactoring
[x] Feature: represents a new feature
[ ] Documentation: documentation changes (no production code change)
[ ] Chore: maintenance tasks (no production code change)
[ ] Style: styles updates (no production code change)
[ ] Test: all about tests: adding, refactoring tests (no production code change)
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Does this PR change client-test-data?

[ ] Yes (don't forget to update the JS-LIB team about the change)
[x] No

@seakayone wrong PR title prefix, it should be feat.


Added support lifecycle page

Page to clarify our support lifecycle

TODO:
[ ] Add link on TOC
[ ] Add link on Home page


Integration list

We should have a tutorial/documentation for the following frameworks, libs, tools, and wallets:
Relayers

[ ] Running Local Relayer
[ ] Connecting to remote relayer

Bridges

[x] Aurora Bridge (ERC20 and ETH) for Ethereum

Wallets

[x] Metamask
[ ] MethWallet
[ ] Ledger
[ ] Trezor

Libraries

[ ] Ethers.js
[ ] Web3.js
[ ] Web3.py

IDE & Frameworks

[x] Hardhat
[ ] Hardhat Verify
[x] Truffle
[ ] Truffle Verify
[x] RemixIDE

Oracles

[ ] ChainLink
[ ] Band Protocol
[ ] Razor Network

Indexers

[ ] The Graph
[ ] Covalent API

@birchmd @artob Feel free to update this Epic :)


Removed -Wfloat-conversion from the conversion warnings as it's impli…

…ed by -Wconversion
Note that -Wfloat-conversion was only introduced in GCC 4.9 so 4.8 (for Houdini 16.5) complains that it's unknown. It's also implied by -Wconversion so I removed it instead of branching
Signed-off-by: Nick Avramoussis<EMAIL_ADDRESS>

This actually fails in our CI:
https://circleci.com/gh/AcademySoftwareFoundation/openvdb/47
Perhaps this means a pragma warning for conversion doesn't imply float-conversion. Either way, I think we need to branch for GCC >= 4.9 as you suggested. I'm going to re-enable this...


Ability to override HAPROXY_0_VHOST

Make it possible to override HAPROXY_0_VHOST before deployment

Perhaps a generic JSONPath replacement support would be preferable?


Implementing Dependency-Responsive Liveliness Probes in Frontend Pod

Is your feature request related to a problem? Please describe.
We have identified a critical issue in our system architecture related to service interdependencies. Specifically, this problem arises when the matching pod encounters a failure, leading to a disruption in the connection. This disruption necessitates a manual restart of the frontend pod. The reason behind this is that the connections to dependent services are initialized during the startup phase of the frontend pod. Consequently, any interruption in these services post-launch results in the following error:
If that happens then we get this error:

Describe the solution you'd like
To mitigate this issue, we propose the implementation of advanced liveliness probes within the frontend pod. These probes will be responsible for continuously monitoring the health status of all dependent services. In the event of a service failure, these probes will automatically initiate a restart of the frontend pod, thereby restoring the system's operational status without manual intervention.
Additional context
I'm not sure about the root-cause of matching pod failing, if I establish that I will add those details to the issue.

If the frontend pods do not automatically reconnect to the matching service, please file an issue against the Temporal repo. Compensating for that should not be handled at the Kubernetes layer. It should not be the case, for example, that everytime matching is rolled out that the frontend pods report themselves unhealthy and get restarted. That will cause frontend connection churn for no reason.


Sign column

How to disbale sign colum from syntatics configuration not from vim because i have other plugin (Ale) wich also uses sign columns

:h syntastic-error-signs


Throw an error if duplicate entries in the voltage table produce zero slope

Fixes https://github.com/NREL/ssc/issues/1007
Testing with the case in the issue should produce an error message, testing with the defaults should not.

Updated Help to explain that duplicate voltage values are not allowed in voltage table for Fall 2023 version.


Deliver activities to shared inboxes

If there are more than one recipients from the same ActivityPub server, we should deliver the activity to the shared inbox of the server.

Is there any reason to avoid the shared inbox if there is only one recipient?


[5.5] Allow to fetch specific key when using json helper

This PR allows to fetch a specific key off of the TestResponse class.
Example:
$title = $this->post('/posts', $data)
    ->json('data.title');

vs
$title = $this->post('/posts', $data)
    ->json()['data']['title'];

🌵

If in the old version, data or title was missing or title, you would get an immediate error (which I consider good).
OTOH with data_get you will always receive a value (default value) back and your test breaks at a later point.
Not sure I would consider that an improvement?
Iff it didn't matter for I test I would probably writ ->json()['data']['title'] ?? ''.

A quick reminder that even the TestResponse class is a documented public api. Changing a method signature in a public api is a breaking change. Have you considered targeting the 5.6 release?

But this change, as I see it, is completley optional. You don't need to pass a key in it.

If the $key is null, the normal object will be returned like before.
https://github.com/illuminate/support/blob/master/helpers.php#L454

The breaking isn't for those that call the method, but for those that have overridden it. You will get php warnings stating that your model signature does not match the signature that you are overriding.

Could you change the targeted branch to master to target the 5.6 release since this has breaking changes (changes to method signatures)?

Honestly, I do not consider this PR to be a breaking change. I'd like it to be merged into 5.5 so it becomes available right away.

I hate these back-and-forths on breaks, however, whether something is a BC break does not change if you don't agree. It either is or isn't. Technically, if the class isn't declared final, adding a parameter ( even with a default value) is a BC break. If the method is being overwritten (likely), then that app will break. Period.
Should target master, as we shouldn't intentionally break people's apps unless it is an important bug fix(this is not), but that's definitely up to Taylor.


Added cask for Lego Mindstorms EV3 Home Edition IDE.

It’s missing uninstall. There are scripts and documentation geared for that.

.pkg need an uninstall stanza. You can find details on how to write one here.
Let us know if you have any trouble!

Please squash your commits.

Is there anything else to action from my end?

Just took another look at the Cask, I'm thinking it should be lego-mindstorms-ev3 (because there are other installers for lego mindstorms, and also, the uninstall stanza should be more specific (ie. list out the packages to uninstall, instead of using the wildcard), as it could break people's installs with other versions of the software installed.

com.ni.pkg.lego.ev3.Eng.1.1.1
com.ni.pkg.lego.x<IP_ADDRESS>.core
com.ni.pkg.lego.x<IP_ADDRESS>.update
com.ni.pkg.legodriver```
are the pkg ids it installs, should it specify all the *.lego* ones in the uninstall or just the one specific to ev3?

Ah I see. In this case, do something like:
uninstall :pkgutil => [
                         'com.ni.pkg.lego.ev3.Eng.1.1.1',
                         'com.ni.pkg.lego.x<IP_ADDRESS>.core',
                         'com.ni.pkg.lego.x<IP_ADDRESS>.update'
                        ]

zap :pkgutil => 'com.ni.pkg.legodriver'

As of right now, there aren't other lego mindstorms casks, but explicitly defining things to uninstall is always a better option.
Comment when the Cask is updated (or if you have any problems) so that we get a notification and can go ahead and merge it.
Thanks!

I think that's everything, waiting on CI.

Thank you for the contribution. It was merged directly as d0187946ed1b3e0579efe48a73af128a10beb15b to keep commit history cleaner. Your contribution is still credited to you.

@adityadalal924 Were you able to verify the download url? I still can’t access the website.

@vitorgalvao Yep, it downloads fine on my end.
wget http://esd.lego.com.edgesuite.net/digitaldelivery/mindstorms/6ecda7c2-1189-4816-b2dd-440e22d65814/public/LMS-EV3-OSX-ENUS-01-01-01-full-setup.dmg
--2015-12-11 18:25:55--  http://esd.lego.com.edgesuite.net/digitaldelivery/mindstorms/6ecda7c2-1189-4816-b2dd-440e22d65814/public/LMS-EV3-OSX-ENUS-01-01-01-full-setup.dmg
Resolving esd.lego.com.edgesuite.net... <IP_ADDRESS>, <IP_ADDRESS>
Connecting to esd.lego.com.edgesuite.net|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 664126388 (633M) [application/octet-stream]
Saving to: 'LMS-EV3-OSX-ENUS-01-01-01-full-setup.dmg'
{snip}

I mean if you were able to verify that it is indeed the correct download as shown by the homepage (since hosts differ).

Yes, the url is the same one as found on http://www.lego.com/en-us/mindstorms/downloads/download-software (http://esd.lego.com.edgesuite.net/digitaldelivery/mindstorms/6ecda7c2-1189-4816-b2dd-440e22d65814/public/LMS-EV3-OSX-ENUS-01-01-01-full-setup.dmg)


uninitialized constant UNIXSocket using dalli 1.1.3

Windows 7
Ruby 1.8.7 (Patch 352)
Rails (3.1.1)
dalli (1.1.3)
--
Trying to start my application either via Webrick or Thin, both fail to start up.
rails s
APP_PATH/bin/ruby/1.8/gems/dalli-1.1.3/lib/dalli/socket.rb:152: uninitialized constant UNIXSocket (NameError)
from APP_PATH/bin/ruby/1.8/gems/dalli-1.1.3/lib/dalli.rb:4
from c:/Ruby187/lib/ruby/gems/1.8/gems/bundler-1.0.21/lib/bundler/runtime.rb:68:in require'         from c:/Ruby187/lib/ruby/gems/1.8/gems/bundler-1.0.21/lib/bundler/runtime.rb:68:in require'
from c:/Ruby187/lib/ruby/gems/1.8/gems/bundler-1.0.21/lib/bundler/runtime.rb:66:in each'         from c:/Ruby187/lib/ruby/gems/1.8/gems/bundler-1.0.21/lib/bundler/runtime.rb:66:in require'
from c:/Ruby187/lib/ruby/gems/1.8/gems/bundler-1.0.21/lib/bundler/runtime.rb:55:in each'         from c:/Ruby187/lib/ruby/gems/1.8/gems/bundler-1.0.21/lib/bundler/runtime.rb:55:in require'
from c:/Ruby187/lib/ruby/gems/1.8/gems/bundler-1.0.21/lib/bundler.rb:122:in require'         from APP_PATH/config/application.rb:7         from APP_PATH/bin/ruby/1.8/gems/railties-3.1.1/lib/rails/commands.rb:52:in require'
from APP_PATH/bin/ruby/1.8/gems/railties-3.1.1/lib/rails/commands.rb:52
from APP_PATH/bin/ruby/1.8/gems/railties-3.1.1/lib/rails/commands.rb:49:in tap'         from APP_PATH/bin/ruby/1.8/gems/railties-3.1.1/lib/rails/commands.rb:49         from script/rails:6:in require'
from script/rails:6

Additional info : reverting to 1.1.2 works.

Good catch, try this workaround in your Gemfile:
gem 'dalli', :require => ['socket', 'dalli']

maybe there should be added some conditional for windows system (is there any way to support unix socket on windows? if not unix socket support may be conditional - by detecting system)

Ah, I didn't even think about that.  I guess requiring 'socket' isn't going to magically implement UnixSockets on Windows.  :-|
@algritz What value does RUBY_PLATFORM have on your system? e.g.
> irb
ruby-1.9.3-rc1 :001 > RUBY_PLATFORM
 => "x86_64-darwin11.1.0"

windows system be checked by
RUBY_PLATFORM.downcase.include?("mswin")
so USocket should be defined only if this condition is not satisfied, also is_unix_socket? should raise error if platorm is windows and there is provided unix path to socket

gem 'dalli', :require => ['socket', 'dalli']
didn't help, still getting the exact same error

if i'll provide commit for this, could you check it? (don't have windows here)

I can try indeed, I might not be able to test it within the next 3 hours though (got a meeting), maybe after.

I provided solution here https://github.com/dfens/dalli/commit/131394fce5c435800faa0f9b66203df18c42f56d
Tell mi if it does the thing for you

1 more thing, this may not work when using JRUBY

@dfens Welcome to the project, bro.  Take care of this, will ya?  :-)

I've tried to update my bundle, it didn't change the problem
So I simply cut / pasted the changes in the socket.rb file and it worked

thanks

Any chances to push this to the master branch ?


Really remove default for speed

Commit 4b8ebcf removed the default of 1 turn per day, but this removes the default of turn-based (vs realtime).
Fixes #39.

Weird. I thought I fixed this. Thanks for the patch.


No space between i and < in for loop breaks formatting

No formatting in Sublime:
  for(var i = 0; i< totalTerms; i++) {
    let num = arr[i];
    counts[num] = counts[num] ? counts[num]+1 : 1;
  }

Formatting (note space between i and < in the first line):
  for(var i = 0; i < totalTerms; i++) {
    let num = arr[i];
    counts[num] = counts[num] ? counts[num]+1 : 1;
  }

Sublime Text 2, Typescript plugin version 0.1.7

Duplicate of https://github.com/Microsoft/TypeScript-Sublime-Plugin/issues/285. We haven't found a good solution for this issue.


Kubefirst Local - Github Auth Flow - Repeat Token Request

Overview
Repeated prompting for GitHub device auth flow
Details
When not used the variable KUBEFIRST_GITHUB_AUTH_TOKEN on your terminal for the installation. The installer by design don't store the users token, so every interactions with installer that needs a github token may request access to github.
export KUBEFIRST_GITHUB_AUTH_TOKEN='your github token'

It is not clear from the feedback, if there is multiple request of token on the same interaction, but I believe that is not the case.
Goal
If possible, to explore a better User Experience to handle this credentials and flow to get a token, and document better the existence of workarounds.
Source: https://github.com/kubefirst/kubefirst/discussions/848

@converge  / @jarededwards Is this a 1.11 deliverable?

There was a PR in work by @converge  exploring this, I am not aware if this was completed.  I don't see changes in the code related to this flow:

https://github.com/kubefirst/kubefirst/blob/main/internal/wrappers/github.go#L13

created a new ticket with story details https://github.com/kubefirst/kubefirst/issues/1065

I think we should keep this ticket open at least to allow the workaround documentation to be covered on the current release.


RFToolsdim - Spamming Console

This is constantly spamming our console, any way to disable it?
(Ftb Beyond)

That's AE2 reporting this. Ask them why it is telling you that and what it means

Thanks.


Add imap for both Python 2 and 3

Provides imap with expected functionality (returning an iterator) on both Python's and makes use of it where possible.

Checks out. Landscape error is a false positive. Coveralls stat is not showing up, but is computed to be a slight up tick. ( https://coveralls.io/builds/5427402 )


Carla Stops to load or fails while launching after successful execution of "make Launch" command

Followed all the steps at windows Build to setup carla on windows VM
1.I’m trying to build Carla 0.9.10
2.Have all the prerequisites installed.
3.“make PythonAPI” cmd was built properly.
4.After successful execution of “make launch” cmd…the CarlaUE4 is launching with this error.

Onclick of OK-option…the editor is opening but the screen is blank no map is visible.
Please help!

Did you download the assets and kept it in content folder ? or did you run update.sh/update.bat ?

I downloaded the asset and kept it in content/carla folder

I downloaded the asset and kept it in content/carla folder

Did you extract it ?

@nagasanjay is this problem still bothering you?

@nagasanjay is this problem still bothering you?


CASMINST-4684 Remove Manual Wipe Steps

Description

With the fix from MTL-1288, manually wiping is no longer necessary. To rebuild an NCN after following respective procedures for expunging the NCN from its clusters, only metal.no-wipe=0 must be set and the node PXE booted.
Checklist Before Merging

[x] If I added any command snippets, the steps they belong to follow the prompt conventions (see example).
[x] If I added a new directory, I also updated .github/CODEOWNERS with the corresponding team in Cray-HPE.
[x] My commits or Pull-Request Title contain my JIRA information, or I don't have a JIRA.

I did some linting. Among other things, this cleared up the stuff the linter was barking about.

I might've overwritten those but I'll factor them back in. Was going to appease the linter after I was done with content changes, I have a few more changes to the upgrade script incoming.

I still need to add a piece to the rebuild script that mitigates the possibly of the node disk-booting during a rebuild (since wiping is removed).


asciidoctor: WARNING: unknown unordered list style: something

https://github.com/asciidoctor/asciidoctor-pdf/blob/5aebe179c9c8931de4ba5e501696cadb3206d469/lib/asciidoctor/pdf/converter.rb#L1575
=== title

[something]
* blah blah

Hello, I encountered a warning while building asciidoctor-pdf.
I would like to connect js, css to adoc.
When does this happen and what options should I add?

The behavior here is correct. something is not a valid list style according to https://docs.asciidoctor.org/asciidoc/latest/lists/unordered/#custom-markers
If you need help with AsciiDoc, please ask in the project chat at https://chat.asciidoctor.org.

Thanks for answer ! 👍


enable errorlint and testifylint linters

Which problem is this PR solving?

Description of the changes

applies errorlint and testifylint linters

How was this change tested?

The ci passes

Checklist

[x] I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
[x] I have signed all commits
[ ] I have added unit tests for the new functionality
[ ] I have run lint and test steps successfully

for jaeger: make lint test
for jaeger-ui: yarn lint and yarn test

Hi @mmorel-35, thanks for your PR!
To make it easier to track the changes and review the PR, could you split it? For instance, one can be enabling the linters, and the other one enabling errorlint and testifylint linters.
Thanks!

Missing "ok-to-test" label ?

Isn't the "ok-to-test" label missing ?

Yes, but I wanted the @rubenvp8510 review before adding it.


Use suppressed data in CrossTalk script for GRIFFIN.

Moving forward, the Cross talk correction script will likely perform better with suppressed data. Since data with no suppressors will just return the same result as unsuppressed data, this should be relatively easy.

This would only require changing the selector that creates the spectra, right? As far as I can see the GriffinCTFix program simply uses histograms of the form det_ and doesn't require any knowledge whether the data is suppressed or not.
On a side note, it looks like GriffinCTFix only acts on channels A of GRIFFIN, not the B channels. Has anyone looked into whether there is a difference between the two? If the cross talk is purely happening within the detector, the effect should be the same for both channels (if corrected for different gains), right?

Alex would have at some point I believe. He is looking at 128 crystals.
The selector should be changed to accept both crystal types if they exists.

Does the above PR render this issue closed?

I guess so?


Select/unselect all features

Description
Hi! Refined GitHub is pretty cool and has a lot of features. But it does have a performance impact, and I'd really like to limit the impact by selectively enabling features rather than having them all enabled and opting out of features I don't want. Would it be possible to add a "select all"/"unselect all" button so that we could do this more easily? Thanks!
Screenshot
No response
Example URLs
https://github.com/refined-github/refined-github

Duplicate of https://github.com/refined-github/refined-github/issues/3535

Duplicate of https://github.com/refined-github/refined-github/issues/2684

Also, an option to disable new features by default would be nice.


[1.10.2] Redstone performance issues.

I made three redstone clocks, one of one type and two of another type (to test clocks with repeaters and clocks with redstone torches), made timings in a 1.8.9 SpongeForge server and then a 1.10.2 SpongeForge server, here are the results:
1.8.9: https://timings.aikar.co/v2/?id=259f160ae9964a94b69a2a8e5e940835
1.10.2: https://timings.aikar.co/v2/?id=62a1adb48c134cf5a9bf798ccb783bc3
As you can see, redstone performance is way worse in 1.10.2.
Original SF Issue: #772

@LuxusDarkangel Please perform another test using the latest builds.

Performance is amazing now even aside from redstone, (15~ms in a freshly generated world doing nothing before, 25-30~ with redstone clocks to 6~ ms with redstone clocks)
But repeaters behaves weird now:
http://i.imgur.com/CjT49GS.png
http://i.imgur.com/NrLrmAU.png

@gabizou ^


Notebook data directory

Location of Data for Migrated Notebook
Many old notebooks have been moved to this repository (hurray!), but they currently don't work because they reference old data locations.
Problem
These notebooks need to be updated:

All 3.0 notebooks
4.0-hef-beacon-op-check

Solution
Just need to take the time to go in and make the changes. Comment with new notebooks when they have been imported.

Notebooks are for the most part up to date or at least the relevant code works with minor tweaks.


Fix

This theme seems to be broken on jsonresume.org. When I cloned the repo I couldn't get it running because of some error in resume-schema but bumping that version fixed the problem.
I also remove the node_modules folder as I personally don't normally track dependencies in a repository in case there are some binary compilation steps that would compile diffrently on different users computers. If I'm wrong about this I can revert those commits :)

Thanks for this! I just haven't been too active on Github lately, and I hadn't checked this for some time. Hope these all work.


ANP CSS azure-cli-vm-tutorial-2.md

Updated PowerShell code to use PowerShell commandlets instead of CLI

@microsoft-github-policy-service agree
@microsoft-github-policy-service agree company="Microsoft"
Marcus Gilbertson
Technical Advisor
Azure - Networking
+1<PHONE_NUMBER>
Working Hours: M-F 8:00 AM - 5:00 PM Central Standard Time
Need help outside of my working hours?
Locate an engineer<EMAIL_ADDRESS>Manager: Sarah Purdy /<EMAIL_ADDRESS>[Image result for microsoft logo]
From: microsoft-github-policy-service[bot] @.>
Sent: Monday, August 5, 2024 4:10 PM
To: MicrosoftDocs/azure-docs-cli @.>
Cc: Marcus Gilbertson @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs-cli] ANP CSS azure-cli-vm-tutorial-2.md (PR #4524)
@magilbehttps://github.com/magilbe please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]
Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term "You" includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement
Contribution License Agreement
This Contribution License Agreement ("Agreement") is agreed to by the party signing below ("You"),
and conveys certain license rights to Microsoft Corporation and its affiliates ("Microsoft") for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

Definitions.
"Code" means the computer software code, whether in human-readable or machine-executable form,
that is delivered by You to Microsoft under this Agreement.
"Project" means any of the projects owned or managed by Microsoft and offered under a license
approved by the Open Source Initiative (www.opensource.orghttp://www.opensource.org/).
"Submit" is the act of uploading, submitting, transmitting, or distributing code or other content to any
Project, including but not limited to communication on electronic mailing lists, source code control
systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
discussing and improving that Project, but excluding communication that is conspicuously marked or
otherwise designated in writing by You as "Not a Submission."
"Submission" means the Code and any other copyrightable material Submitted by You, including any
associated comments and documentation.
Your Submission. You must agree to the terms of this Agreement before making a Submission to any
Project. This Agreement covers any and all Submissions that You, now or in the future (except as
described in Section 4 below), Submit to any Project.
Originality of Work. You represent that each of Your Submissions is entirely Your original work.
Should You wish to Submit materials that are not Your original work, You may Submit them separately
to the Project if You (a) retain all copyright and license information that was in the materials as You
received them, (b) in the description accompanying Your Submission, include the phrase "Submission
containing materials of a third party:" followed by the names of the third party and any licenses or other
restrictions of which You are aware, and (c) follow any other instructions in the Project's written
guidelines concerning Submissions.
Your Employer. References to "employer" in this Agreement include Your employer or anyone else
for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
Submission is made in the course of Your work for an employer or Your employer has intellectual
property rights in Your Submission by contract or applicable law, You must secure permission from Your
employer to make the Submission before signing this Agreement. In that case, the term "You" in this
Agreement will refer to You and the employer collectively. If You change employers in the future and
desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
and secure permission from the new employer before Submitting those Submissions.
Licenses.

Copyright License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
parties.
Patent License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
Your patent claims that are necessarily infringed by the Submission or the combination of the
Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
import or otherwise dispose of the Submission alone or with the Project.
Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
granted by implication, exhaustion, estoppel or otherwise.

Representations and Warranties. You represent that You are legally entitled to grant the above
licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
have disclosed under Section 3). You represent that You have secured permission from Your employer to
make the Submission in cases where Your Submission is made in the course of Your work for Your
employer or Your employer has intellectual property rights in Your Submission by contract or applicable
law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
You later become aware that would make Your representations in this Agreement inaccurate in any
respect.
Information about Submissions. You agree that contributions to Projects and information about
contributions may be maintained indefinitely and disclosed publicly, including Your name and other
information that You submit with Your Submission.
Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
defenses of lack of personal jurisdiction and forum non-conveniens.
Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
supersedes any and all prior agreements, understandings or communications, written or oral, between
the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs-cli/pull/4524#issuecomment-2269924641, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJWP4Y7O6MR5RWKHOMAK2FTZP7S3RAVCNFSM6AAAAABMBBBF4OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRZHEZDINRUGE.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

#sign-off

@magilbe, thank you for your input on this article; however, the intent is to teach developers how to use the Azure CLI in a PowerShell environment.  You can find more information in Considerations for running the Azure CLI in a PowerShell scripting language.


Let versions and bundles use nested accessors

Fixes #16676

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.

Successfully verified on production:

@bot-gradle test and merge

OK, I've already triggered a build for you.


Powershell 7 support in Azure Functions

While this blog article isn't 100% clear: https://azure.microsoft.com/en-us/updates/azure-functions-powershell-7-support-is-now-generally-available/ would it be possible to get this page updated with Function RunTime versions support which version of Powershell?

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

ID: 40e84dea-0cdb-2aa7-6aa0-a4c697ef19ac
Version Independent ID: 2fe0dbd3-7e5b-04b1-46e5-fecd89c4a780
Content: Supported languages in Azure Functions
Content Source: articles/azure-functions/supported-languages.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@Rabbit994 Thank you for your feedback! We have assigned this issue to the author to review further and take the next course of action.

Thanks for the heads up, and sorry it took so long to get back to you. The page you reference should be up-to-date at this point. If not, please open a new issue. #please-close


Feature/tdSearchBar_fix 新增只读属性与点击事件

🤔 这个 PR 的性质是？

[ ] 日常 bug 修复
[ ] 新特性提交
[ ] 文档改进
[ ] 演示代码改进
[ ] 组件样式/交互改进
[ ] CI/CD 改进
[ ] 重构
[ ] 代码风格优化
[ ] 测试用例
[ ] 分支合并
[ ] 其他

🔗 相关 Issue

https://github.com/Tencent/tdesign-flutter/issues/389
💡 需求背景和解决方案

📝 更新日志

fix(组件名称): 处理问题或特性描述 ...

[ ] 本条 PR 不需要纳入 Changelog

☑ 请求合并前的自查清单
⚠ 请自检并全部勾选全部选项。⚠

[ ] 文档已补充或无须补充
[ ] 代码演示已提供或无须提供
[ ] Changelog 已提供或无须提供

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: Luozf12345:white_check_mark: q920447939:x: v_szheshiv_szheshi seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Cleaner builder

Add wrapper method to builder and deprecate the :tag and :class options to use and optional.
Related with #434

:blue_heart:


Add search bar

Related: #166
Adds a search bar to the asset featured page.
Signed-off-by: Andrew-Butler<EMAIL_ADDRESS>

@drewbutlerbb4 can you add a screenshot with where you moved the search box?

@ckadner I've left it in place for now. I can move it when we have a better idea of what we want. Here is where it stands now.

in the package.json, we need to add the "fuzzysort": "^1.1.4", package

/lgtm


task_set_result resulting 0?

Hey there. I changed my old code a bit, in the old code I stored the ID in a seperate variable, now I instead pass the ID over task_set_result.
https://pastebin.com/pb4YWxGQ
When someone does the /badge command, it executes the SelectPlayerFaction function, which then checks how many factions the player is a member of. If there's only one faction, it should set the ID of that faction as the result. It does set a result, but for some reason it always sends back 0 to the command. I also printed out the value of Iter_First and it does print out the currect value. What is also odd, is that when a player is a member of multiple factions and he goes through the dialog and selects a faction, it does somehow work.
I've tried everything, there's no errors, warnings or anything strange in any of the logs. This is also all of my code in regards to the PlayerInfo[playerid][pAwaitMembershipSelection] task, so it's not being reset or something in the background. I even reverted back to the old style where I stored the information in a seperate variable, and that doesn't work either, leading me to think it has something to do with the "case 1" part I added inbetween, but there's nothing wrong there, so I'm legitimately confused.

task_valid returns false for the task then, doesn't it? If you use task_set_result, it will invoke all registered continuations (i.e. paused calls to task_wait) and then automatically delete the task, unless task_keep is called (or task_reset is called inside the continuation).
You can call task_keep to prevent the task from being automatically collected, but you also need to call task_delete in that case. I suggest you not to use a task at all, if you don't want need to wait for anything.

task_valid returns true before task_set_result in SelectPlayerFaction under case 1:  is called, but task_get_result in /badge returns 0 when it's supposed to return 4.

task_valid should return false after task_set_result.

Yes it does, but I still should be able to use task_get_result to get the result after a task has ended, correct?

Ahh, I still believe I found a bug in that case which is the reason I got confused, because task_get_result did return 4 (the value I needed) when characters had multiple factions (meaning they would go through the dialog and once they selected their faction from the dialog the task_await code would continue) even though I had no task_keep on at that time.
It's clear now, thanks for your help.

In that case, the task will be available immediately in the continuation (i.e. after task_await) but will be collected once the continuation returns (and the code after task_set_result will continue as usual).

So, what's the difference between task_set_result in SelectPlayerFaction and task_set_result in the dialog (e.g. why does it work fine in the dialog, and not in the function)? Because that's my intended behavior, to return a faction ID and continue the task_await. It works fine with task_keep now but I'm curious because I don't really get the difference between both scenarios.

A call to task_await registers a continuation in the task object. The continuation consists of the code that follows the call to task_await up until the end of the callback.
In the first case, the order of operations is 1) task_set_result, 2) task_await. Since there is no continuation registered when you call task_set_result, nothing will happen, and the task is collected (since it is completed and nothing can wait for it). Further calls are performed on a nonexistent task and thus return invalid values.
In the second case, task_await is called first. This pauses the code, registers the continuation, and exits the callback. Calling task_set_result then will restore the original code and call the continuation. This call actually happens entirely inside task_set_result, so during its execution, the task is still alive. After all continuations are executed, the task is collected.
Using task_keep in the first case prevents task_set_result from deleting the task, so a call to task_await returns immediately (the task is already completed). This way, you must use task_delete to explicitly destroy the task, or you'll end up with a memory leak. You have no other option than to put it after task_await, which is fine in the first case, but in the second case, it deletes the task in the middle of task_set_result, which may potentially result in undefined behaviour. You should not call task_keep and task_delete in the second case.
Also note that task_await is (at least in the latest version) a combination of task_wait and task_get_result. You can simplify your code to:
        new memberSelected = task_awaitPlayerInfo[playerid][pAwaitMembershipSelection]);

Oh damn, thank you for your help, it's been really helpful to me. It seems like there's no way to call SelectPlayerFaction after the continuation is registered, seeing as task_await freezes the code until the task is finished. So I have no choice but to use task_keep and task_delete in both cases. I'll probably do some tests to see if it shows any 'undefined behavior' first.

I still think not creating a task when not needed is the best option, but to address your case, I have modified task_set_result to prevent the task object from being destroyed inside a continuation. It will be more or less okay to delete it then (the task will be removed from the task pool, but the actual object will be kept alive until task_set_result ends).


Adds support for computing update state

Towards https://github.com/giantswarm/giantswarm/issues/1482

I reckon I'm being a bit too defensive in testing, and am testing against some guarantees that operatorkit has, but my brain is happier this way :D

@xh3b4sd I could use some clarification here https://github.com/giantswarm/prometheus-config-controller/pull/11#discussion_r144067773, other particulars should be fixed.


How to use RebuildVersionStrategy

My issues is similar to #188 but the links on that PR seem to be dead. We're putting together the gradle-kubernetes-plugin and want to to be able to trigger a new version/tag from the desktop but then in a CI environment, in our case travis-ci, we still want to run the release task but to use the existing version.
Our code is all within our root build.gradle file HERE. I've followed the instructions on the wiki here and from other sources and still can't seem to get things to work properly. Running with --info I get:
Skipping rebuild strategy because clean is true, "release." properties are true and head version is null
Skipping development strategy because stage (SNAPSHOT) is not one of: [dev]
Skipping pre-release strategy because stage (SNAPSHOT) is not one of: [milestone, rc]
Skipping final strategy because stage (SNAPSHOT) is not one of: [final]
Using snapshot default strategy because repo is clean and no stage defined
Falling back to default strategy: snapshot

I don't understand why rebuild strategy is getting skipped. When I do a git tag locally I see the v0.0.1 present so not sure why it's not getting picked up and instead falling back to the snapshot version.
Any ideas?

So it looks like 2 issues looking at the logic:

"release." properties are true implies that you are providing the release.scope or release.stage properties. (This behavior is due to #68.)
head version is null implies that it can't find a tag on HEAD that it considers a version tag. (Not sure why it would think that.)

I think the main thing you'll want to change is removing this block that sets release.stage and release.scope. If you provide either, the plugin assumes you're trying to influence the version and will always try to increment.

 I assumed that:
gradle.properties
    ciRelease=false

build.gradle
    if (ciRelease) {
         println "should never get here"
    }

the line should never get here would be reached but I had forgotten that gradle would treat the property as a boolean until it is cast as one and so was entering that code block every time.
Thanks for taking a look anyway and great work on the plugin.


Memory leak?

I frequently find vrcx using upwards of 3+GB of ram for no conceivable reason, and it progressively increases the longer the program is open.
As time has gone on, the program has taken longer and longer to load at startup each update, making restarting it a chore.

There are a few options you can set to help with RAM usage, In Appearance lower Max Table Size and in Advanced lower Auto Clear Cache timer. Also next release has slightly faster startup times.

There's no reason for it to be using 5GB of memory... most of this should be read off of the api or files on disk when needed.

Hence my previous comment, try lower those values.


python extension

Issue Type: Bug
I am not sure but was told my problem was with the python extension... Python 3.10.5. Built a flask app and it was running fine and now it and other flask apps will not work.. reporting import errors that are not there. Everything was running fine and now all of a sudden it isnt running fine
Extension version: 2022.10.1
VS Code version: Code 1.69.2 (3b889b090b5ad5793f524b5d1d39fda662b96a2a, 2022-07-18T16:12:52.460Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz (4 x 2904)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
11.89GB (2.79GB free)

Process Argv
--crash-reporter-id 91448f35-f0fc-4683-a4e9-8e0b60ce003c

Screen Reader
no

VM
0%

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30525688
vsaa593cf:30376535
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vscscmwlcmt:30465135
cppdebug:30492333
pylanb8912cf:30529770
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253

@jturnerFL You need to provide logs from Output >Python panel for us to diagnose this.

Thanks for the bug report, but unfortunately, we need some more information from you in order to triage this issue appropriately. Please follow instructions here to create a new bug with all the critical details we need for diagnosis.


Bugfix: fix reuse_port and accept_mutex conflict

Bugfix: enable reuse_port will cause some request not to be accepted

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.guanwei seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

#942   thx @gwtony


Week 4 You Wan

Very Hard...
Didn't understand OHE
I found that the dropout is the most decisive factor in test tuning

Lab 4 accepted. There is a pretty good description of OHE in this tutorial:
http://machinelearningmastery.com/text-generation-lstm-recurrent-neural-networks-python-keras/
We will use OHE again in the week 6 lab. It's more of a technicality and you don't need it to do the assignment but it's helpful to understand how it works and why we use it.
Well done!


Email component tooltip not working

No tooltip appears for the email component upon hover.
{
    label: 'Email label',
    value: 'Test default value',
    tooltip: 'This is a tip',
    onChange: (value) => {
       console.log('Email value changed', value)
    },
    type: whisper.WhisperComponentType.Email
}

This has been resolved. Please update to the latest versions of Olive Helps (V 0.17.3) and the LDK (V 3.0.0.beta-3). If you are still seeing this problem, please re-open this issue.


${ELASTICSEARCH_URL} not defined

In the wizard there is a tooltip that says that you can use ${ELASTICSEARCH_URL} to connect to ElasticSearch in your logstash.conf, however this doesn't seem to exist for me. When SSHing into the Logstash machine, no such environment variable is present (manually setting it to <IP_ADDRESS>:9200 makes it work). I also had to manually set the password for the elastic user in the logstash.conf to get it to work, and then the kibana user doesn't seem to have access to any index - it does work when I log in with the elastic user in Kibana, but I have a feeling that this is not how it's meant to be. Could someone point me in the right direction in regards to where this went wrong?

Hi,
I'm trying to execute the lines you said:
set +o history
export the keystore password into env variable
pass=$(sudo grep -Po "(?<=^LOGSTASH_KEYSTORE_PASS=).*" /etc/sysconfig/logstash)
export LOGSTASH_KEYSTORE_PASS=$pass
set -o history
list keys in keystore
sudo -E /usr/share/logstash/bin/logstash-keystore --path.settings /etc/logstash list
But I get this error:
ERROR: Failed to load settings file from "path.settings". Aborting... path.setting=/etc/logstash, exception=Java::OrgLogstashSecretStore::SecretStoreException::AccessException, message=>Can not access Logstash keystore at /etc/logstash/logstash.keystore. Please verify correct file permissions and keystore password.
[ERROR] 2019-10-01 07:28:23.048 [main] secretstorecli - Can not access Logstash keystore at /etc/logstash/logstash.keystore. Please verify correct file permissions and keystore password. {:cause=>java.io.IOException: Integrity check failed: java.security.UnrecoverableKeyException: Failed PKCS12 integrity checking, :backtrace=>["org.logstash.secret.store.backend.JavaKeyStore.load(org/logstash/secret/store/backend/JavaKeyStore.java:265)", "org.logstash.secret.store.backend.JavaKeyStore.load(org/logstash/secret/store/backend/JavaKeyStore.java:40)", "org.logstash.secret.store.SecretStoreFactory.doIt(org/logstash/secret/store/SecretStoreFactory.java:109)", "org.logstash.secret.store.SecretStoreFactory.load(org/logstash/secret/store/SecretStoreFactory.java:95)", "org.logstash.secret.cli.SecretStoreCli.command(org/logstash/secret/cli/SecretStoreCli.java:77)", "java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498)", "org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:425)", "org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:292)", "RUBY.class:SecretStoreCli(/usr/share/logstash/lib/secretstore/cli.rb:35)", "RUBY.(/usr/share/logstash/lib/secretstore/cli.rb:16)", "org.jruby.Ruby.runInterpreter(org/jruby/Ruby.java:891)", "org.jruby.Ruby.runInterpreter(org/jruby/Ruby.java:895)", "org.jruby.Ruby.runNormally(org/jruby/Ruby.java:784)", "org.jruby.Ruby.runNormally(org/jruby/Ruby.java:797)", "org.jruby.Ruby.runFromMain(org/jruby/Ruby.java:609)", "org.jruby.Main.doRunFromMain(org/jruby/Main.java:415)", "org.jruby.Main.internalRun(org/jruby/Main.java:307)", "org.jruby.Main.run(org/jruby/Main.java:234)", "org.jruby.Main.main(org/jruby/Main.java:206)"]}
any ideas?
Thanks!

@0GiS0 try with the logstash user
sudo -Eu logstash /usr/share/logstash/bin/logstash-keystore --path.settings /etc/logstash list

Hi Russ,
I get the same error :(
`gis@logstash-0:/usr/share/logstash$ sudo -Eu logstash /usr/share/logstash/bin/logstash-keystore --path.settings /etc/logstash list
[ERROR] 2019-10-01 08:09:43.463 [main] secretstorecli - Can not access Logstash keystore at /etc/logstash/logstash.keystore. Please verify correct file permissions and keystore password. {:cause=>java.io.IOException: Integrity check failed: java.security.UnrecoverableKeyException: Failed PKCS12 integrity checking, :backtrace=>["org.logstash.secret.store.backend.JavaKeyStore.load(org/logstash/secret/store/backend/JavaKeyStore.java:265)", "org.logstash.secret.store.backend.JavaKeyStore.load(org/logstash/secret/store/backend/JavaKeyStore.java:40)", "org.logstash.secret.store.SecretStoreFactory.doIt(org/logstash/secret/store/SecretStoreFactory.java:109)", "org.logstash.secret.store.SecretStoreFactory.load(org/logstash/secret/store/SecretStoreFactory.java:95)", "org.logstash.secret.cli.SecretStoreCli.command(org/logstash/secret/cli/SecretStoreCli.java:77)", "java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498)", "org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:425)", "org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:292)", "RUBY.class:SecretStoreCli(/usr/share/logstash/lib/secretstore/cli.rb:35)", "RUBY.(/usr/share/logstash/lib/secretstore/cli.rb:16)", "org.jruby.Ruby.runInterpreter(org/jruby/Ruby.java:891)", "org.jruby.Ruby.runInterpreter(org/jruby/Ruby.java:895)", "org.jruby.Ruby.runNormally(org/jruby/Ruby.java:784)", "org.jruby.Ruby.runNormally(org/jruby/Ruby.java:797)", "org.jruby.Ruby.runFromMain(org/jruby/Ruby.java:609)", "org.jruby.Main.doRunFromMain(org/jruby/Main.java:415)", "org.jruby.Main.internalRun(org/jruby/Main.java:307)", "org.jruby.Main.run(org/jruby/Main.java:234)", "org.jruby.Main.main(org/jruby/Main.java:206)"]}
`

I think the exporting of the keystore pass may include the surrounding double quotes. Try this
set +o history
# export the keystore password into env variable
pass=$(sudo grep -Po "(?<=^LOGSTASH_KEYSTORE_PASS=).*" /etc/sysconfig/logstash | sed 's/"//g')
export LOGSTASH_KEYSTORE_PASS="$pass"
set -o history

# list keys in keystore
sudo -Eu logstash /usr/share/logstash/bin/logstash-keystore --path.settings /etc/logstash list

Thanks @russcam!
Now It works:
gis@logstash-0:/usr/share/logstash$ set +o history
gis@logstash-0:/usr/share/logstash$ # export the keystore password into env variable
gis@logstash-0:/usr/share/logstash$ pass=$(sudo grep -Po "(?<=^LOGSTASH_KEYSTORE_PASS=).*" /etc/sysconfig/logstash | sed 's/"//g')
gis@logstash-0:/usr/share/logstash$ export LOGSTASH_KEYSTORE_PASS="$pass"
gis@logstash-0:/usr/share/logstash$ set -o history
gis@logstash-0:/usr/share/logstash$
gis@logstash-0:/usr/share/logstash$ # list keys in keystore
gis@logstash-0:/usr/share/logstash$ sudo -Eu logstash /usr/share/logstash/bin/logstash-keystore --path.settings /etc/logstash list

elasticsearch_url
logstash_system_password

However, when I run this:
sudo ./bin/logstash --setup --path.settings /etc/logstash/
I get a different error:
gis@logstash-0:/usr/share/logstash$ sudo ./bin/logstash --setup --path.settings /etc/logstash/
Thread.exclusive is deprecated, use Thread::Mutex
ERROR: Failed to load settings file from "path.settings". Aborting... path.setting=/etc/logstash/, exception=Java::OrgLogstashSecretStore::SecretStoreException::LoadException, message=>Found a file at /etc/logstash/logstash.keystore, but it is not a valid Logstash keystore.
[ERROR] 2019-10-01 08:30:17.611 [main] Logstash - java.lang.IllegalStateException: Logstash stopped processing because of an error: (SystemExit) exit

Thanks

Logstash installed by the template runs as a service managed by systemd, so it should be started with
sudo systemctl start logstash.service

If you do need to start it manually, it should be started using the logstash user, and the keystore password needs to be exported as before (if not already exported)
set +o history
# export the keystore password into env variable
pass=$(sudo grep -Po "(?<=^LOGSTASH_KEYSTORE_PASS=).*" /etc/sysconfig/logstash | sed 's/"//g')
export LOGSTASH_KEYSTORE_PASS="$pass"
set -o history

sudo -Eu logstash /usr/share/logstash/bin/logstash --path.settings /etc/logstash --setup

Looking at the steps posted, it looks like you might be trying to configure the Logstash monitor module? There's an example in the azure-marketplace-examples repository that may help.

Thanks @russcam !
What I could see was I didn't have some parameters in the Azure Monitoring Module because the documentation doesn't say anything about them. (var.elasticsearch.username/password and  var.kibana.username/password)
I also wrote a post about the configuration to help others :)
Thank you so much for your help!


FYI you can change the repo name on github

And the old name will stay as an alias

I did do that. If you go to http://github.com/lexi-lambda/rascal, you’ll see that it redirects here.


KIE forms jBPM integration:

Setting default resource name when creating a form for process / task
UX changes
Moved NewResourceView to Errai Template & Errai I18n

Comment: merge with https://github.com/droolsjbpm/jbpm-console-ng/pull/584

@manstis can you take a look please?

merge with droolsjbpm/jbpm-console-ng#584

@manstis could you review again?


Import and modify historical reputation data

Before the attackathon, just replace historical_data/raw_data_csv with the base data (using _csv because your gitignore has *.csv) and build and push the image.

https://github.com/bitcoin-dev-project/warnet/pull/334 adds an option to warnet RPC import-json so (when your image is cross-platform and ready for the attackathon) you can convert Clara's json to a warnet graphml file like this:
warcli graph import-json /test/data/LN_100.json --outfile=ln100.graphml --cb=carlakirkcohen/circuitbreaker:attackathon

and then start a war:
warcli network start ln100.graphml


init_project should link schema.yml to ~/.testtrack

There's no reason to force that extra step on the init'ing developer.

Or maybe we shouldn't to encourage them to wire up testtrack schema link --force to their developer bootstrapping scripts. Hmmm.

yeah, nah, this shouldn't do a thing that the consumer must do in code in order to have a replicable dev environment. It's in the README that you have to do this, so closing this issue.


Upgrade to ember-template-imports 4.1.1

Overview
This fixes a problem on dependencies using ember-appuniversum v3, which was being hidden by a working combination of versions existing in the lockfile. This doesn't fix these versions for the test-app in this repo.
connected issues and PRs:
Plugins PR tbc
Setup
N/A
How to test/reproduce
Test that everything works... Should also be tested in plugins PR.
Challenges/uncertainties
N/A
Checks PR readiness

[ ] UI: works on smaller screen sizes
[ ] UI: feedback for any loading/error states
[ ] Check cancel/go-back flows
[ ] Check database state correct when deleting/updating (especially regarding relationships)
[ ] changelog
[ ] npm lint
[ ] no new deprecations

maybe we should regen the lockfile with pnpm 9 also?

@abeforgit The reason I never asked for any reviews on this one (I meant to turn it into a draft), is that this is actually a breaking change in some cases. While a user of the library does not need to depend on ember-template-imports, it seems that any user of it that does depend on it, needs to use v4 also (I haven't tested which exact versions, but I tested with 4.1.1). I don't know a way to encode this in the dependencies. I'm also not sure how AU gets away with this, but I suspect that it's to do with how ember-nodes are rendered by code here, but provided by plugins, so it's possible that it's a unique problem for those two libraries.
I'll put in another PR with more breaking updates. I'll also see if just updating ember-template-imports on the plugins, without the other updates works, and if so, put in two PRs there.


Miss icon on iOS14

As title.
Already rebuilded icon caches.

@CySxL Does version 1.1.1 fix it?

@PoomSmart sadly no

Did you rebuild the icon caches via TrollStore?

yes literally using TrollStore to rebuild icon cache.
But my TrollStore is 2.0.8, would that be the culprit?

TS version probably doesn't matter.  @CySxL

Also, can you see if the app icons are inside TrollLEDs.app in your fs?

TS version probably doesn't matter.  @CySxL

Haven't done that. Will try it now.

TS version probably doesn't matter.  @CySxL

Also tried: uicache, rebuild icon cache in TS, respring, and reboot userspace after all of them. Still no luck.

Also, can you see if the app icons are inside TrollLEDs.app in your fs?

@PoomSmart Yeah, but there are some of the PNGs are 0kb. So I guess we found the issue.

Also it's kinda like this issue: https://github.com/donato-fiore/TrollDecrypt/issues/2
Hope that helps xd

I don't recall TrollLEDs has this many app icons.

I don't recall TrollLEDs has this many app icons. It only has two.

Yeah somehow it duplicates itself on iOS 14 device like what I had with TrollDecryptor.

@CySxL I suggest you uninstall the app and install the latest version (1.1.1) again.

Yeah I just tried that haha. Uninstalled and reinstalled.
Video: https://streamable.com/0jwewr

I see, Theos duplicates the icons.

Fixed in v1.1.2

Feel bad to say... but 1.1.2 is still having the same issue on my device 🥲

@CySxL I made sure that there are two icons in TrollLEDs.app, that's why the file size was reduced to just 50 KB.
What's inside your TrollLEDs.app now?

What's inside your TrollLEDs.app now?

@PoomSmart Seems like they all now disappear

Yeah that's expected and it should work now, no?

By the way, you should rebuild the icon caches before doing uicache -a

Yeah that's expected and it should work now, no?

Sadly not working for me.

@CySxL I will connect you via Discord

Gotcha! I just saw a friend request, is that you? 😂😅

Fixed in 1.2.1
Thanks @PoomSmart ❤


tests failing (OS X)

On master, about 10 tests are failing on port attribute access:
RuntimeError: Cannot get port because this server has more than 1 listeners.

also test_wrap_server_stream() appears to be blocking indefinitely on client.send_message

I can confirm that 12 of 23 tests fail on OS X for me as well. The tests currently pass on Ubuntu 18.04. I will troubleshoot the failing tests and then set up a CI instance to test on multiple platforms.


Handling scenario when MSA sign in is down

Looking back to a week or two ago when MSA was down.
Do we have guidance on properly (gracefully) handling the situation when MSA sign-in is down?

The advice is
a) Use the approved Microsoft Account SDK (OneDrive / Live SDK) for authentication.
b) Use the client-flow version of LoginAsync() to validate the token.
If MSA is down, the MSA SDK will be used to handle the error, and you can handle it in their approved way.  There is not much you can do when a provider is down on the server-flow side.


No jsDoc intellisense when function is declared as part of prototype.

From @DenysYefimenko on April 18, 2016 12:51

VSCode Version: 1.0.0
OS Version: Windows 10

Steps to Reproduce:

Create js file with following code:

function constructorFunction () {}

/**
 * The prototype method.
 * @param {String} a Parameter definition.
 */
function prototypeMember(a) {}

constructorFunction.prototype.method = prototypeMember;

var x = new constructorFunction();
x.method();

Check that intellisense shows parameter description for x.method().
Replace method definition with shorter syntax:

/**
 * The prototype method.
 * @param {String} a Parameter definition.
 */
constructorFunction.prototype.method = function (a) {};

Intellisense for x.method() is not working now both for function and param descriptions.
Copied from original issue: Microsoft/vscode#5449

Moving to TS.

@RyanCavanaugh I thought we fixed this very issue? Does this repro in 'master'?

This works for me on master.
@DenysYefimenko, can you test this by installing typescript@next in a test package and in Code's settings.json temporarily setting "typescript.tsdk": ".../node_modules/typescript/bin", where ... is the path of your test npm package? (You'll have to restart Code or Reload Window to get the changes.)

but when I use prototype in this way, it still not work
constructorFunction.prototype =  {
  method: function(a) {}
}


Maven 3 task: JAVA_HOME is not correctly set.

We have a problem with Artifactory Maven 3 task and maven-javadoc-plugin:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.1.1:jar (attach-javadocs) on project: MavenReportException: Error while creating archive: Unable to find javadoc command: The environment variable JAVA_HOME is not correctly set.

Looks like Bamboo Artifactory Plugin doesn't set JAVA_HOME
There is a point about it on http://maven.apache.org/install.html

Ensure JAVA_HOME environment variable is set and points to your JDK installation

artifactory.task.override.jdk isn't working too (https://www.jfrog.com/confluence/pages/viewpage.action?pageId=46108401#BambooArtifactoryPlug-in-ControllingtheBuildJDKusingBambooVariables)
I tried artifactory.task.override.jdk.env.var=bamboo_capability_system_jdk_JDK_11 and artifactory.task.override.jdk.env.var=bamboo.capability.system.jdk.JDK-11

The task is configured to use the 'bamboo_capability_system_jdk_JDK_11' environment variable for the build JDK, but this environment variable is not defined.`

I also tried builder.artifactoryMaven3Builder.environmentVariables="JAVA_HOME=${bamboo_capability_system_jdk_JDK_11}"
Doesn't work. bamboo_capability_system_jdk_JDK_11 and bamboo.capability.system.jdk.JDK-11

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.1.1:jar (attach-javadocs) on project: MavenReportException: Error while generating Javadoc: Unable to find javadoc command: The environment variable JAVA_HOME=${bamboo_capability_system_jdk_JDK_11} doesn't exist or is not a valid directory.`

So we only can hardcode JDK-path in builder.artifactoryMaven3Builder.environmentVariables="JAVA_HOME=/path/to/jdk" or make changes in pom.xml (https://stackoverflow.com/a/54323506) for all projects
Meanwhile, the default Maven 3 plugin (https://docs.atlassian.com/bamboo/docs-0606/Maven) works fine.

@efimovee
Bamboo Artifactory plugin 3.2.0 is released.
This version includes https://github.com/jfrog/bamboo-artifactory-plugin/pull/100 which contributed by @clarkperkins.
Feel free to upgrade - we'd also appreciate your feedback for that!

Please read the Bamboo version compatibility matrix, before upgrading to version 3.2.o of tbe plugin.


How do I install?

I tried cloning the repo to the same folder as where bashrc is located, but it still says command not found.
I had this installed before but can't remember how I did it. Can you give me some quick instructions?
Thank you!

https://marketplace.visualstudio.com/items?itemName=babakks.vscode-copy-from-terminal&ssr=false#overview

Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
ext install babakks.vscode-copy-from-terminal


Use with React Native

Hi there,
I use cortex in React Native, it works and there is a callback, however, I can't setState in the callback function as I use createClass which only grants me a descriptor. So where can I get an instance able to call setState because it is react native, the elements are very different, I don't think I could use the way in your example code (can't use renderComponent to gain instance..).
Thanks.

Can't you get a handle of your root component like this?
var myRootComponent = AppRegistry.registerComponent('MyRootComponent', () => MyRootComponent);

yeah, I can get the root component, but how can I modify its child component's state?

Then you pass cortex in as props and pass it down to your child component as prop. Please follow the README example if you have anymore question

Yes, this is what I did. My main concern is to use the upstream data in cortex callback outside the components to update UI.

The example in the README also setProps outside of the component, what's wrong with that?

Example works well but for my code, I use NavigatorIOS in root component to route, then I don't have a way to get router's child component and set its state when callback is called which is outside, so I can't use refs.

Do you have code sample?

Sure,
This is render function in root:
render: function() {
    return (
      <TabBarIOS>
        <TabBarIOS.Item
          title='Upload'
          selected={this.state.selectedTab === 'AddItemTab'}
          onPress={() => {
            this.setState({
              selectedTab: 'AddItemTab',
            });
          }}>
          <Router
            firstRoute={AddItemRoute}
            backButtonComponent={BackButton}
          />
        </TabBarIOS.Item>
        <TabBarIOS.Item
          title='Delivery'
          selected={this.state.selectedTab === 'DeliverItemTab'}
          onPress={() => {
            this.setState({
              selectedTab: 'DeliverItemTab',
            });
          }}>
          <Router
            firstRoute={{
              name: '发货',
              component: DeliverItemView
            }}
            backButtonComponent={BackButton}
          />
        </TabBarIOS.Item>
      </TabBarIOS>
    );

My cortex outside:
// cortext callbacks
formCortex.on("update", function() {
  console.log(rootComponent.refs);
  var brand = formCortex.brand.getValue();
});

What component is that render function? and where is the formCortex defined?

This is defined outside from components:
// upstream data
var formData = {brand: {}, category: {}, sizeChart: {}};
var formCortex = new Cortex(formData);

The render function is for root component, aka, component get from AppRegistry:
var rootComponent = AppRegistry.registerComponent('Client', () => Client);

And where's the Client component?

All of them are in the same file.

Router is react-native-router, I am an iOS developer and very new in React, thanks for the great help.

so you can use getDefaultProps to pass formCortex in as your props or use rootComponent.setProps. Then just pass the cortex object into child components under Client component. Callback should be
formCortex.on("update", function(updatedCortex) {
  rootComponent.setProps(....)
});

rootComponent.setProps(....)

This causes an error, undefined is not a function. I think it is because of rootComponent?

well you have to make sure rootComponent is a React Native component. Because what AppRegistry.registerComponent return may not be. If not you can always initialize it in getInitialState
getInitialState: function() {
  var formCortex = new Cortex(formData);
  formCortex.on("update", function(updatedCortex) {
    this.setState({cortex: updatedCortex});
  });
  return { cortex: formCortex };
}

Thanks mquan, but the this is also undefined. I am really curious about the context in callback function.

do this
getInitialState: function() {
  var formCortex = new Cortex(formData);
  var self = this;
  formCortex.on("update", function(updatedCortex) {
    self.setState({cortex: updatedCortex});
  });
  return { cortex: formCortex };
}

It finally works! Great! Thank you very much mquan. Can you please explain why this here is undefined? Is it in cortex context?

You should read up on this in javascript https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/this

@iceNuts Because callbacks normally lose the value of this when they get passed around. To ensure that this gets preserved in the callback, either use .bind() or arrow functions

@mquan @RangerMauve thank you guys. let me dig it deeper.


Update dead MS connect link

MS Connect is dead.
The bug was moved from https://connect.microsoft.com/IE/feedback/details/811408/ie10-11-a-textareas-placeholder-text-becomes-its-actual-value-when-using-innertext-innerhtml-or-outerhtml to https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/101525/
I also mention the bug at the innertext features because it is effected as well.

See #4067

Thanks!


Enabling Ruby Language Metrics

In an ongoing effort to understand where performance becomes a problem, we'd like to know how much value we get when we scale up the Heroku Dynos. Heroku offers some ruby specific metrics that may help us see whether the app is over or under provisioned. See here: https://devcenter.heroku.com/articles/language-runtime-metrics-ruby#getting-started
This adds and configures the barnes gem to get this info from Heroku. We probably don't need to keep this permanently.

Selfie


Performance memoize instructions

For each pair of class and hasharray, I parse the query to come up with instructions that can be reused the next time the same pair is encountered.

While testing it on some real data in Blend Board, I decreased the average serialization time form 26 ms to 19 ms.

The tests pass for Rails 6 and 7 locally. I can't get bundle install to run without an error when the version of active record is 7+ in GitHub actions...


Update to rails 6.1.5

Update to 6.1.4 makes the app faster.
Rails 5
32 requests
4.24 MB / 4.15 MB transferred
Finish: 1.51 s
DOMContentLoaded: 558 ms
load: 1.42 s
Rails 6.1.5
32 requests
8.45 MB / 8.36 MB transferred
Finish: 1.04 s
DOMContentLoaded: 307 ms
load: 899 ms

@tyranja it didn't work on my machine. After running make setup I got a new schema where blob_id was changed into an integer. Besides I discovered a typo (?) in storage.yml. Was that a mistake or a planned change?
When deploying to staging I got the error: undefined method service_name for active storage