Is Hash ordered based on when the entry was inserted?

Hi, everybody.
I just want to make sure whether Hash#keys or Hash#each returns entries in order based on when they were inserted. I found it's mentioned in Hash#key_index in document,  and it looks like it's ordered viewing the code of key_index. But nothing mentioned in any other place about this, and the document of Set  say Set based on Hash is unordered.

And more is it safe to insert new entry into Hash during the iteration of it, and will the new inserted entry be visited in the iteration?

Key-value pairs in a Hash are sorted by insertion order.
A Set by definition has no order. In practice, the items will be sorted by insertion order because of the implementation. But it's not guaranteed. If we change the implementation, this might not longer be true. Sets should always be considered unordered.
It should be safe to add elements to any stdlib collection while enumerating it and newly added items should be enumerated as well.

We should use this issue to improve the documentation.

For 2, a Set has an order. In theory it doesn't have one, but in practice it does. Same with Hash: in theory a mapping of keys from values isn't ordered, but in practice it is. And for example Ruby guarantees this (because they guarantee this through the implementation, and they won't suddenly change the implementation to unordered). We should do the same (guarantee that Set will stay ordered).

@asterite I can't find such a guarantee for Set in Ruby. The API docs explicitly state that it's an unordered collection and that the order of elements returned by #to_a is uncertain.

@straight-shoota Oh, I guess it's ordered then because it's built on top of Hash. Nevermind.

BTW: Hash wasn't ordered in Ruby 1.8.


Binded props for stubs in wrapper HTML

What problem does this feature solve?
As a member of front developper with React Framework, we did a lost of tests on our components with Enzyme.
In order to have "Unit tests" we mainly use "Shallow" rendering feature to test our components.
Coupled with Jest snapshot checks, it made our test very easy and quick to write.
We tried to apply those usage with Vue and test utils but we were confronted to lacks of feature:

Auto stubs component feature

We would often want to have a stub component with name of component as tag.  In the current state of the API, we have to define a stub for every childComponent to have a humanly readable tag in .html()

Props of type Object in tags

Not printable props type are not showing well in .html() generated. For example with Object types.
<stub my-props="[object Object]"/>

What does the proposed API look like?

It could be awesome to have autoStubs mounting options with tag generated on child names.

It would be very usefull to have readable/comparable props in html() rendered.

To fill this lack of feature, we developed a utils to generate our stubs and handle props.

Our generateStubs implementation
import _ from 'lodash';

export default function generateStubs(component) {
  return Object.values(component.components).reduce((stubs, componentToStub) => {
    const kebabCaseName = _.kebabCase(componentToStub.name);
    stubs[kebabCaseName] = {
      render(createElement) {
        return createElement(
          kebabCaseName,
          {
            attrs: _.transform(this.$vnode.data.attrs, (acc, attribute, key) => {
              acc[`data-${key}`] = (JSON.stringify(attribute) || '').replace(/"/g, "'");
            }),
          },
          this.$slots.default,
        );
      },
    };

    return stubs;
  }, {});
}

It generate those kind of html :
<stub
 data-my-props="{'id':'cjgqp3mp421gk016335mrvp36','name':'name'}"
 my-props="[object Object]"
/>

In the next release all stubbed components will render as their tag name with a stub suffix:
const TestComponent = {
  template: '<some-component />,
  components: {
    SomeComponent
  }
}

mount(TestComponent).html() // <some-component-stub />

Does that solve your issue?

And what complex prop types ?

Ah sorry I missed that part of your feature request. Currently they will be rendered as an object, we could investigate calling JSON.stringify on the attributes like you have.
My initial concern is handling circular references and checking that a prop object equals the object you passed in.

"checking that a prop object equals the object you passed in."

We could only change how the component is stringified ?

"My initial concern is handling circular references"

It should not be vue test utils concern to check circular references of props passed to component.
At the beginning I wanted to do it myself but I have to confess I have no idea where those features are handled. With some hints I may help.

Is there a flag for not rendering the props? I have a ton of snapshot tests that are now failing because the mocked date being set as a prop is rendering to a string in UTC on the CI server but EDT on our dev machines. (dates suck)

In the next release all stubbed components will render as their tag name with a stub suffix, and the props they receive:
const TestComponent = {
  template: '<some-component prop="yes" />',
  components: {
    SomeComponent
  }
}

mount(TestComponent).html() // <some-component-stub prop="yes" />

Does that satisfy your feature request?

Yes, this is working perfectly in vue-test-utils:1.0.0-beta.29, for locally registered components.
However, for globally registered components, the rendered stub does not include the props.
Shouldn't it also be renderred with the props?

https://github.com/vuejs/vue-test-utils/issues/1564#issuecomment-1424857260


Bugfix/schema connecting cases and judges

Description
Judge names were not showing on the case table or in case details and if a user saved a case or judge it would cause an error in the backend and an infinite loading wheel, resolved only by restarting the server.
Model functions that joined the cases to judges table were causing this backend error (see screenshot below) because judge_id no longer existed as a column in the cases table. I added judge_id back into cases as a foreign key so these joins worked properly again and I changed the findAll() model function in caseModel.js from joining judges_to_case to case and separately querying judges to directly join cases and judges.

judge_id was added to the case table seeds (I randomly assigned judges because this is just test seed data) and the readme documentation is updated to reflect this change in case schema.
Corresponding frontend PR
Trello Card

Loom Video
Fixes judge names not appearing and the infinite loading wheel when saving a case or judge as a user.
Type of change

[X] Bug fix (non-breaking change which fixes an issue)
[X] This change requires a documentation update

Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have removed unnecessary comments/console logs from my code
[X] I have made corresponding changes to the documentation if necessary (optional)
[X] My changes generate no new warnings
[X] I have checked my code and corrected any misspellings
[X] No duplicate code left within changed files
[X] Size of pull request kept to a minimum
[X] Pull request description clearly describes changes made & motivations for said changes

I would check with Paul though to see why the PR page is giving a warning regarding the Sonar Cloud warning at the bottom of the page.

I believe the failed check has to do with the ds_case table that is commented out. We were going to discuss if this table is needed anymore as a separate issue. Thanks for reminding me, I just added a ticket to the Trello board so we don't forget!


Super Linter Does Not Pick Up .github/linters/.golangci.yaml Configuration File

Is there an existing issue for this?

[X] I have searched the existing issues

Are you using the latest Super-linter version available?

[X] I am using the latest Super-linter version.

[X] I can reproduce the issue running Super-linter using complete version identifier (example: vX.Y.Z), and not just with a partial one (example: vX)

[X] I am using the super-linter/super-linter action or container image, and not the deprecated github/super-linter action or container image.

Are you resonably sure that it's a Super-linter issue, and not an issue related to a tool that Super-linter runs?

[X] I think that this is a Super-linter issue.

Current Behavior
I get the following error when the super-linter is used to validate my go module
level=error msg="Running error: context loading failed: failed to load packages: failed to load packages: failed to load with go/packages: context deadline exceeded"
level=error msg="Timeout exceeded: try increasing it by passing --timeout option"
level=error msg="Running error: context loading failed: failed to load packages: failed to load packages: failed to load with go/packages: context deadline exceeded"
level=error msg="Timeout exceeded: try increasing it by passing --timeout option"

I have provided the .golangci.yaml file in the .github/linters directory as follows
run:
  timeout: 5m
  modules-download-mode: readonly

and it still fails in under 1min which is the default timeout in golangci-lint.
                 @%      / Don't mind me  \
2024-10-23T15:28:12.8728856Z       @@%           .&@&&/@.@//&/////(//////////    @@@@@@@@@         .. &@    / I'm just looking \
2024-10-23T15:28:12.8729330Z     @@%               @@@@@   @&/////////////////#   @/       V  @@/ ,@@@ @   <  for some trash... |
2024-10-23T15:28:12.8729792Z @@@%                   @@@@        .%@@@@//////#@ @   @@         @     .,.     \__________________/
2024-10-23T15:28:12.8730222Z                                           @@@/@(  (@@@@% @/\      %
2024-10-23T15:28:12.8730780Z                                            @@@@(    .     .@@/\   #
2024-10-23T15:28:12.8731304Z                                              @                  %@%
2024-10-23T15:28:12.8731491Z
2024-10-23T15:28:12.8731995Z --------------------------------------------------------------------------------
2024-10-23T15:28:12.8751699Z 2024-10-23 15:28:12 [INFO]   ---------------------------------------------
2024-10-23T15:28:12.8796156Z 2024-10-23 15:28:12 [INFO]   --- GitHub Actions Multi Language Linter ----
2024-10-23T15:28:12.8839126Z 2024-10-23 15:28:12 [INFO]    - Image Creation Date: 2024-10-14T17:31:34Z
2024-10-23T15:28:12.8895145Z 2024-10-23 15:28:12 [INFO]    - Image Revision: e69f0364d2fd33c3ea08a4ca973762de2a4e655b
2024-10-23T15:28:12.8943995Z 2024-10-23 15:28:12 [INFO]    - Image Version: e69f0364d2fd33c3ea08a4ca973762de2a4e655b
2024-10-23T15:28:12.8997342Z 2024-10-23 15:28:12 [INFO]   ---------------------------------------------
2024-10-23T15:28:12.9046702Z 2024-10-23 15:28:12 [INFO]   ---------------------------------------------
2024-10-23T15:28:12.9108134Z 2024-10-23 15:28:12 [INFO]   The Super-Linter source code can be found at:
2024-10-23T15:28:12.9153774Z 2024-10-23 15:28:12 [INFO]    - https://github.com/super-linter/super-linter
2024-10-23T15:28:12.9203420Z 2024-10-23 15:28:12 [INFO]   ---------------------------------------------
2024-10-23T15:28:12.9250941Z 2024-10-23 15:28:12 [INFO]   - Validating all files in code base...
2024-10-23T15:28:12.9899082Z 2024-10-23 15:28:12 [INFO]   This version of Super-linter includes the following tools:
2024-10-23T15:28:12.9899548Z [ANSIBLE] ansible-lint: 24.7.0
2024-10-23T15:28:12.9899780Z [BASH] shellcheck: 0.10.0
2024-10-23T15:28:12.9900100Z [BASH_EXEC] bash-exec: Version command not supported
2024-10-23T15:28:12.9900345Z [CHECKOV] checkov: 3.2.236
2024-10-23T15:28:12.9900625Z [CLANG_FORMAT] clang-format: 17.0.6
2024-10-23T15:28:12.9900908Z [CLOJURE] clj-kondo: v2024.08.01
2024-10-23T15:28:12.9901187Z [CLOUDFORMATION] cfn-lint: 1.10.3
2024-10-23T15:28:12.9901427Z [COFFEESCRIPT] coffeelint: 5.2.11
2024-10-23T15:28:12.9901639Z [CPP] cpplint: 1.6.1
2024-10-23T15:28:12.9901846Z [CSS] stylelint: 15.11.0
2024-10-23T15:28:12.9902060Z [CSS_PRETTIER] prettier: 3.3.3
2024-10-23T15:28:12.9902272Z [DART] dart: 3.5.1
2024-10-23T15:28:12.9902487Z [DOCKERFILE_HADOLINT] hadolint: 2.12.0
2024-10-23T15:28:12.9902801Z [EDITORCONFIG] editorconfig-checker: v3.0.3
2024-10-23T15:28:12.9903086Z [ENV] dotenv-linter: 3.3.0
2024-10-23T15:28:12.9903397Z [GHERKIN] gherkin-lint: Version command not supported
2024-10-23T15:28:12.9903924Z [GITHUB_ACTIONS] actionlint: 1.7.1
2024-10-23T15:28:12.9904150Z [GITLEAKS] gitleaks: v8.18.4
2024-10-23T15:28:12.9904388Z [GIT_COMMITLINT] commitlint<EMAIL_ADDRESS>2024-10-23T15:28:12.9904752Z [GIT_MERGE_CONFLICT_MARKERS] git-merge-conflict-markers: 1.0.0
2024-10-23T15:28:12.9905094Z [GOOGLE_JAVA_FORMAT] google-java-format: 1.24.0
2024-10-23T15:28:12.9905376Z [GO] golangci-lint: 1.60.3
2024-10-23T15:28:12.9905653Z [GO_MODULES] golangci-lint: 1.60.3
2024-10-23T15:28:12.9906006Z [GO_RELEASER] goreleaser: 2.2.0
2024-10-23T15:28:12.9906230Z [GRAPHQL_PRETTIER] prettier: 3.3.3
2024-10-23T15:28:12.9906517Z [GROOVY] npm-groovy-lint: 14.6.0
2024-10-23T15:28:12.9906737Z [HTML] htmlhint: 1.1.4
2024-10-23T15:28:12.9906952Z [HTML_PRETTIER] prettier: 3.3.3
2024-10-23T15:28:12.9907174Z [JAVASCRIPT_ES] eslint: v8.57.1
2024-10-23T15:28:12.9907402Z [JAVASCRIPT_PRETTIER] prettier: 3.3.3
2024-10-23T15:28:12.9907635Z [JAVASCRIPT_STANDARD] standard: 17.1.0
2024-10-23T15:28:12.9907857Z [JAVA] checkstyle: 10.18.2
2024-10-23T15:28:12.9908071Z [JSCPD] jscpd: 4.0.5
2024-10-23T15:28:12.9908281Z [JSONC] eslint: v8.57.1
2024-10-23T15:28:12.9908496Z [JSONC_PRETTIER] prettier: 3.3.3
2024-10-23T15:28:12.9908710Z [JSON] eslint: v8.57.1
2024-10-23T15:28:12.9908900Z [JSON_PRETTIER] prettier: 3.3.3
2024-10-23T15:28:12.9909114Z [JSX] eslint: v8.57.1
2024-10-23T15:28:12.9909326Z [JSX_PRETTIER] prettier: 3.3.3
2024-10-23T15:28:12.9909540Z [KOTLIN] ktlint: 1.3.1
2024-10-23T15:28:12.9909772Z [KUBERNETES_KUBECONFORM] kubeconform: v0.6.7
2024-10-23T15:28:12.9909995Z [LATEX] chktex: v1.7.9
2024-10-23T15:28:12.9910195Z [LUA] lua: 5.4.6
2024-10-23T15:28:12.9910403Z [MARKDOWN] markdownlint: 0.42.0
2024-10-23T15:28:12.9910630Z [MARKDOWN_PRETTIER] prettier: 3.3.3
2024-10-23T15:28:12.9910859Z [NATURAL_LANGUAGE] textlint: v14.2.1
2024-10-23T15:28:12.9911078Z [OPENAPI] spectral: 6.13.1
2024-10-23T15:28:12.9911286Z [PERL] perl: (v5.38.2)
2024-10-23T15:28:12.9911493Z [PHP_BUILTIN] php: 8.3.12
2024-10-23T15:28:12.9911702Z [PHP_PHPCS] phpcs: 3.10.3
2024-10-23T15:28:12.9911923Z [PHP_PHPSTAN] phpstan: 1.12.6
2024-10-23T15:28:12.9912175Z [PHP_PSALM] psalm: 5.26.1@d747f6500b38ac4f7dfc5edbcae6e4b637d7add0
2024-10-23T15:28:12.9912436Z [PROTOBUF] protolint: 0.50.5(6cc254e)
2024-10-23T15:28:12.9912661Z [PYTHON_BLACK] black: 24.10.0
2024-10-23T15:28:12.9912878Z [PYTHON_FLAKE8] flake8: 7.1.1
2024-10-23T15:28:12.9913091Z [PYTHON_ISORT] isort: 5.13.2
2024-10-23T15:28:12.9913302Z [PYTHON_MYPY] mypy: 1.11.2
2024-10-23T15:28:12.9913518Z [PYTHON_PYINK] pyink: 24.3.0
2024-10-23T15:28:12.9913732Z [PYTHON_PYLINT] pylint: 3.2.6
2024-10-23T15:28:12.9913944Z [PYTHON_RUFF] ruff: 0.6.2
2024-10-23T15:28:12.9914153Z [RAKU] raku: v2024.04
2024-10-23T15:28:12.9914463Z [RENOVATE] renovate-config-validator: 38.55.1
2024-10-23T15:28:12.9914697Z [RUBY] rubocop: 1.66.1
2024-10-23T15:28:12.9914890Z [R] R: 4.4.0
2024-10-23T15:28:12.9915091Z [SCALAFMT] scalafmt: 3.8.3
2024-10-23T15:28:12.9915301Z [SHELL_SHFMT] shfmt: v3.9.0
2024-10-23T15:28:12.9915521Z [SNAKEMAKE_LINT] snakemake: 8.18.2
2024-10-23T15:28:12.9915757Z [SNAKEMAKE_SNAKEFMT] snakefmt: 0.10.2
2024-10-23T15:28:12.9915976Z [SQLFLUFF] sqlfluff: 3.1.1
2024-10-23T15:28:12.9916252Z [STATES] asl-validator: 3.8.3
2024-10-23T15:28:12.9916515Z [TEKTON] tekton-lint: 1.1.0
2024-10-23T15:28:12.9916735Z [TERRAFORM_FMT] terraform: v1.9.5
2024-10-23T15:28:12.9916969Z [TERRAFORM_TERRASCAN] terrascan: v1.19.1
2024-10-23T15:28:12.9917201Z [TERRAFORM_TFLINT] tflint: 0.53.0
2024-10-23T15:28:12.9917431Z [TERRAGRUNT] terragrunt: version
2024-10-23T15:28:12.9917646Z [TSX] eslint: v8.57.1
2024-10-23T15:28:12.9917861Z [TYPESCRIPT_ES] eslint: v8.57.1
2024-10-23T15:28:12.9918088Z [TYPESCRIPT_PRETTIER] prettier: 3.3.3
2024-10-23T15:28:12.9918395Z [TYPESCRIPT_STANDARD] ts-standard: 12.0.2
2024-10-23T15:28:12.9918631Z [VUE_PRETTIER] prettier: 3.3.3
2024-10-23T15:28:12.9918842Z [XML] xmllint: 21207
2024-10-23T15:28:12.9919047Z [YAML] yamllint: 1.35.1
2024-10-23T15:28:12.9919262Z [YAML_PRETTIER] prettier: 3.3.3
2024-10-23T15:28:12.9943734Z 2024-10-23 15:28:12 [INFO]   --------------------------------------------
2024-10-23T15:28:12.9994721Z 2024-10-23 15:28:12 [INFO]   Gathering GitHub information...
2024-10-23T15:28:13.0042651Z 2024-10-23 15:28:13 [INFO]   RUN_LOCAL has been set to: true. Bypassing GitHub Actions variables...
2024-10-23T15:28:13.0100085Z 2024-10-23 15:28:13 [INFO]   Successfully validated GITHUB_WORKSPACE: /tmp/lint
2024-10-23T15:28:13.0830679Z 2024-10-23 15:28:13 [INFO]   The default branch for this repository is set to: main
2024-10-23T15:28:13.1463254Z 2024-10-23 15:28:13 [INFO]   --------------------------------------------
2024-10-23T15:28:13.1506049Z 2024-10-23 15:28:13 [INFO]   Validating the configuration
2024-10-23T15:28:14.8465560Z .git
2024-10-23T15:28:14.9112560Z 2024-10-23 15:28:14 [INFO]   The main branch doesn't exist in /tmp/lint
2024-10-23T15:28:14.9228643Z d347ca3e1ca8f69c792198653bcdef7021ce4930
2024-10-23T15:28:14.9323355Z 2024-10-23 15:28:14 [INFO]   main doesn't exist, however origin/main exists. Setting DEFAULT_BRANCH to: origin/main
2024-10-23T15:28:19.9438268Z 2024-10-23 15:28:19 [INFO]   Building the list of files and directories to check
2024-10-23T15:28:22.0265219Z 2024-10-23 15:28:22 [INFO]   Successfully gathered list of files...
2024-10-23T15:29:45.0609907Z 2024-10-23 15:29:45 [INFO]   Command output when running linters:
2024-10-23T15:29:45.0617225Z ------
2024-10-23T15:29:45.0621367Z 2024-10-23 15:28:22 [INFO]   Linting BASH items...
2024-10-23T15:29:45.0676162Z 2024-10-23 15:28:22 [NOTICE]   BASH linted successfully
2024-10-23T15:29:45.0676735Z 2024-10-23 15:28:22 [INFO]   Linting GITLEAKS items...
2024-10-23T15:29:45.0677416Z 2024-10-23 15:28:25 [NOTICE]   GITLEAKS linted successfully
2024-10-23T15:29:45.0677784Z 2024-10-23 15:28:25 [INFO]   Stderr contents for GITLEAKS:
2024-10-23T15:29:45.0678032Z ------
2024-10-23T15:29:45.0678309Z 3:28PM INF scan completed in 4.91ms
2024-10-23T15:29:45.0678616Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0678923Z 3:28PM INF scan completed in 8.45ms
2024-10-23T15:29:45.0679238Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0679543Z 3:28PM INF scan completed in 11.7ms
2024-10-23T15:29:45.0679838Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0680142Z 3:28PM INF scan completed in 19.8ms
2024-10-23T15:29:45.0680590Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0680873Z 3:28PM INF scan completed in 2.38ms
2024-10-23T15:29:45.0681156Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0681436Z 3:28PM INF scan completed in 9.98ms
2024-10-23T15:29:45.0681711Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0681994Z 3:28PM INF scan completed in 7.15ms
2024-10-23T15:29:45.0682265Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0682546Z 3:28PM INF scan completed in 3.24ms
2024-10-23T15:29:45.0682816Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0683106Z 3:28PM INF scan completed in 12.7ms
2024-10-23T15:29:45.0683380Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0683663Z 3:28PM INF scan completed in 12.8ms
2024-10-23T15:29:45.0683935Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0684216Z 3:28PM INF scan completed in 18.2ms
2024-10-23T15:29:45.0684488Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0684775Z 3:28PM INF scan completed in 7.24ms
2024-10-23T15:29:45.0685049Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0685332Z 3:28PM INF scan completed in 16.7ms
2024-10-23T15:29:45.0685604Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0685883Z 3:28PM INF scan completed in 4.27ms
2024-10-23T15:29:45.0686387Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0686678Z 3:28PM INF scan completed in 4.61ms
2024-10-23T15:29:45.0687271Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0687566Z 3:28PM INF scan completed in 61.1ms
2024-10-23T15:29:45.0687848Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0688321Z 3:28PM INF scan completed in 7.11ms
2024-10-23T15:29:45.0688614Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0688915Z 3:28PM INF scan completed in 5.84ms
2024-10-23T15:29:45.0689522Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0689821Z 3:28PM INF scan completed in 8.03ms
2024-10-23T15:29:45.0690105Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0690399Z 3:28PM INF scan completed in 8.68ms
2024-10-23T15:29:45.0690682Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0690972Z 3:28PM INF scan completed in 9.32ms
2024-10-23T15:29:45.0691254Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0691716Z 3:28PM INF scan completed in 7.08ms
2024-10-23T15:29:45.0691993Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0692278Z 3:28PM INF scan completed in 8.92ms
2024-10-23T15:29:45.0692550Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0692834Z 3:28PM INF scan completed in 4.59ms
2024-10-23T15:29:45.0693107Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0693393Z 3:28PM INF scan completed in 71.2ms
2024-10-23T15:29:45.0694068Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0694413Z 3:28PM INF scan completed in 11ms
2024-10-23T15:29:45.0694709Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0695202Z 3:28PM INF scan completed in 19.2ms
2024-10-23T15:29:45.0695506Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0695817Z 3:28PM INF scan completed in 8.87ms
2024-10-23T15:29:45.0696126Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0696435Z 3:28PM INF scan completed in 13ms
2024-10-23T15:29:45.0696735Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0697204Z 3:28PM INF scan completed in 18.1ms
2024-10-23T15:29:45.0697655Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0697945Z 3:28PM INF scan completed in 14.2ms
2024-10-23T15:29:45.0698400Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0698681Z 3:28PM INF scan completed in 53.6ms
2024-10-23T15:29:45.0698953Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0699233Z 3:28PM INF scan completed in 10.6ms
2024-10-23T15:29:45.0699507Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0699787Z 3:28PM INF scan completed in 13.5ms
2024-10-23T15:29:45.0700128Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0700413Z 3:28PM INF scan completed in 6.96ms
2024-10-23T15:29:45.0700689Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0700970Z 3:28PM INF scan completed in 3.48ms
2024-10-23T15:29:45.0701242Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0701520Z 3:28PM INF scan completed in 5.93ms
2024-10-23T15:29:45.0701794Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0702079Z 3:28PM INF scan completed in 20.8ms
2024-10-23T15:29:45.0702353Z 3:28PM INF no leaks found
2024-10-23T15:29:45.0702562Z ------
2024-10-23T15:29:45.0702838Z 2024-10-23 15:28:22 [INFO]   Linting GO_MODULES items...
2024-10-23T15:29:45.0703193Z 2024-10-23 15:29:44 [ERROR]   Found errors when linting GO_MODULES. Exit code: 2.
2024-10-23T15:29:45.0703529Z 2024-10-23 15:29:44 [INFO]   Command output for GO_MODULES:
2024-10-23T15:29:45.0703762Z ------
2024-10-23T15:29:45.0703948Z Linted: /tmp/lint/pkg/providers/vultr
2024-10-23T15:29:45.0704298Z Linted: /tmp/lint/pkg/parser
2024-10-23T15:29:45.0704489Z Linted: /tmp/lint/pkg/pdp
2024-10-23T15:29:45.0704862Z Linted: /tmp/lint/pkg/providers
2024-10-23T15:29:45.0705059Z Linted: /tmp/lint/pkg/util
2024-10-23T15:29:45.0705274Z ------
2024-10-23T15:29:45.0705565Z 2024-10-23 15:29:44 [INFO]   Stderr contents for GO_MODULES:
2024-10-23T15:29:45.0705804Z ------
2024-10-23T15:29:45.0706283Z level=error msg="Running error: context loading failed: failed to load packages: failed to load packages: failed to load with go/packages: context deadline exceeded"
2024-10-23T15:29:45.0707034Z level=error msg="Timeout exceeded: try increasing it by passing --timeout option"
2024-10-23T15:29:45.0707416Z level=error msg="Running error: context loading failed: failed to load packages: failed to load packages: failed to load with go/packages: context deadline exceeded"
2024-10-23T15:29:45.0707880Z level=error msg="Timeout exceeded: try increasing it by passing --timeout option"
2024-10-23T15:29:45.0708151Z ------
2024-10-23T15:29:45.0708441Z 2024-10-23 15:28:27 [INFO]   Linting YAML items...
2024-10-23T15:29:45.0708780Z 2024-10-23 15:28:28 [NOTICE]   YAML linted successfully
2024-10-23T15:29:45.0709120Z 2024-10-23 15:28:28 [INFO]   Command output for YAML:
2024-10-23T15:29:45.0709527Z ------
2024-10-23T15:29:45.0710225Z /tmp/lint/.azure/pr-check.yaml:8:81: [warning] line too long (88 > 80 characters) (line-length)
2024-10-23T15:29:45.0711565Z /tmp/lint/.azure/pr-check.yaml:12:1: [warning] missing document start "---" (document-start)
2024-10-23T15:29:45.0712085Z /tmp/lint/.azure/pr-check.yaml:41:17: [warning] too few spaces inside empty brackets (brackets)
2024-10-23T15:29:45.0712560Z /tmp/lint/.azure/release.yaml:8:81: [warning] line too long (88 > 80 characters) (line-length)
2024-10-23T15:29:45.0713025Z /tmp/lint/.azure/release.yaml:12:1: [warning] missing document start "---" (document-start)
2024-10-23T15:29:45.0713505Z /tmp/lint/.azure/templates/test.yaml:8:81: [warning] line too long (88 > 80 characters) (line-length)
2024-10-23T15:29:45.0713994Z /tmp/lint/.azure/templates/test.yaml:12:1: [warning] missing document start "---" (document-start)
2024-10-23T15:29:45.0714628Z /tmp/lint/.azure/templates/test.yaml:23:81: [warning] line too long (86 > 80 characters) (line-length)
2024-10-23T15:29:45.0715045Z /tmp/lint/.azure/templates/test.yaml:25:81: [warning] line too long (83 > 80 characters) (line-length)
2024-10-23T15:29:45.0715433Z /tmp/lint/cmd/config.yaml:1:1: [warning] missing document start "---" (document-start)
2024-10-23T15:29:45.0715839Z /tmp/lint/.github/linters/.golangci.yaml:1:1: [warning] missing document start "---" (document-start)
2024-10-23T15:29:45.0716445Z /tmp/lint/configs/example.yaml:8:81: [warning] line too long (88 > 80 characters) (line-length)
2024-10-23T15:29:45.0716849Z /tmp/lint/configs/example.yaml:12:1: [warning] missing document start "---" (document-start)
2024-10-23T15:29:45.0717241Z /tmp/lint/.golangci.yaml:1:1: [warning] missing document start "---" (document-start)
2024-10-23T15:29:45.0717499Z ------
2024-10-23T15:29:45.0717689Z ------
2024-10-23T15:29:45.0819713Z 2024-10-23 15:29:45 [INFO]   ----------------------------------------------
2024-10-23T15:29:45.0866400Z 2024-10-23 15:29:45 [INFO]   ----------------------------------------------
2024-10-23T15:29:45.1016864Z 2024-10-23 15:29:45 [NOTICE]   Successfully linted BASH
2024-10-23T15:29:45.1944092Z 2024-10-23 15:29:45 [NOTICE]   Successfully linted GITLEAKS
2024-10-23T15:29:45.2355873Z 2024-10-23 15:29:45 [ERROR]   Errors found in GO_MODULES
2024-10-23T15:29:45.5549542Z 2024-10-23 15:29:45 [NOTICE]   Successfully linted YAML
2024-10-23T15:29:45.5819562Z 2024-10-23 15:29:45 [ERROR]   Super-linter detected linting errors
2024-10-23T15:29:45.9735769Z
2024-10-23T15:29:45.9793701Z ##[error]Bash exited with code '2'.
2024-10-23T15:29:45.9813379Z ##[section]Finishing: Run Super Linter

Steps To Reproduce
Run super linter in a github repo by providing the .golangci.yaml inside .github/linters and see if it picks up any configuration
Anything else?
No response

Hi @SachithKasthuriarachchi .
Can you reproduce the issue by running super-linter locally?

Closing for lack of replies


Improve warning message in Data Plane SDK Release app

Improve warning message by including more specific information about who the PM is and how to contact the PM.

@ladonnaq Is this a PM from our team? or any PM? :)

Since our apps have multiple pop-ups, I created a new component to have consistency across them.
I did the required changes for this pop-up.
Clicking on Email us will pre-fill the email with the Work Item URL. There's no deep link to do that in a Teams channel.


Support date math in index names

 Issue by smowky
Wednesday Sep 23, 2020 at 10:05 GMT
Originally opened as https://github.com/opendistro-for-elasticsearch/alerting/issues/254

Is your feature request related to a problem? Please describe.
I’m using elasticsearch ILM to rotate my indexes and now alerts are searching through all indexes metricbeat-* which is quite expensive operation.
It would be nice to have a possibility to search only for last 2 day indexes instead
Describe the solution you'd like
Would be nice define search index as:
<logstash-{now/d-2d}>,<logstash-{now/d-1d}>,<logstash-{now/d}>
or
%3Clogstash-%7Bnow%2Fd-2d%7D%3E%2C%3Clogstash-%7Bnow%2Fd-1d%7D%3E%2C%3Clogstash-%7Bnow%2Fd%7D%3E
Describe alternatives you've considered
Alternative solutions is using aliases , which is be default not as easy since elasticsearch ILM actions does not have a possibility do add/remove alias

 Comment by aditjind
Wednesday Jun 02, 2021 at 03:34 GMT

Hi @smowky,
ES already has the support built in for Date Math Index Name Resolution to search over a range of indices. Since alerting uses the Node Client to index and search this should be possible with-in the current implementation.
Please check once with our latest release.

Hi @smowky
We have added the support for the Date Math Index Name support via API. Please use this  documentation to create monitors via API calls to the cluster endpoint. You can provide date math index pattern as specified in the documentation here. Please note that special % encoding for the date math characters is not required while listing the indices for the search query in the monitor.
The support for date math encoding in the OSD dashboards is tracked as a part of this issue. https://github.com/opensearch-project/alerting-dashboards-plugin/issues/17

Hi @smowky
We have added the support for the Date Math Index Name support via API. Please use this  documentation to create monitors via API calls to the cluster endpoint. You can provide date math index pattern as specified in the documentation here. Please note that special % encoding for the date math characters is not required while listing the indices for the search query in the monitor.
The support for date math encoding in the OSD dashboards is tracked as a part of this issue. https://github.com/opensearch-project/alerting-dashboards-plugin/issues/17
Sample Indices and Monitors for your reference.
Resolving this issue as no support is required here. Feel free to open if any questions further.


Video from resources is stuck at BUFFERING state

Version
Media3 1.2.0
More version details
No response
Devices that reproduce the issue

Xiaomi Mi 10T Lite 5G, Android 12
Samsung Galaxy A12, Android 12

Devices that do not reproduce the issue

Samsung Galaxy A34

Reproducible in the demo app?
Not tested
Reproduction steps
I am playing video as a background of the app. The app is using Jetpack Compose. The video is located in the raw folder in the resources and it is played automatically when the app is started. Sometimes the video is not playing and a black screen is shown. I've attached EventLogger and saw that the player is stuck at BUFFERING state.
 On Xiaomi Mi10 Lite is happening once in 20-30 startups, while on Samsung A12 almost whenever the app is opened. I tried reproducing it on an emulator with low RAM and memory, but the video was still playing.
Expected result
Play the video all the time.
Actual result
Video is not played sometimes.
Media
Not applicable
Bug Report

[ ] You will email the zip file produced by adb bugreport to<EMAIL_ADDRESS>after filing this issue.

Thanks for your report.
Difficult to say without such a device to repro. If you can help me narrow down a bit with the devices and media you have available, it would be interesting to know whether this happens with a different video file as well. On the other side it would be interesting to see whether the same problem can be observed when the video is loaded with a DataSource other than RawResourceDataSource like when loaded from the network with http. You can also try to load with the video in the asset folder and the load with an asset URI (file:///android_asset/sample.mp4).
Testing in the demo app would also be useful to rule out app problems. I wonder if you see the same in another app. You can change L294 of the PlayerActivivty in a hacky way to always set the same media item:
player.setMediaItem(
    MediaItem.fromUri(
        new Uri.Builder()
            .scheme(ContentResolver.SCHEME_ANDROID_RESOURCE)
            .path(Integer.toString(R.raw.sample))
            .build()),
    /* resetPosition= */ !haveStartPosition);

After this starting any video in the demo app will load that media from the raw source.
This information may help us to see whether and what component in ExoPlayer makes the problem and whether it is media, app or device specific.
Unless you see the same behaviour with another file as well.  It would be helpful to have the file for repro. If you're unable to share bug reports or test content publicly, please send them to<EMAIL_ADDRESS>using a subject in the format "Issue #944". Please also update this issue to indicate you’ve done this.

Sorry for the delay marcbaechinge. I've tried with the ExoPlayer demo app and I was able to reproduce the bug. I've sent a bug report and the sample video to the email as you requested.


Introduction Roles description

Roles: particularly separation and necessity of administrator and administrator owner roles:#

Sounds somehow of zero trust where there are distributed permissions to foreign authority for integrated handled BlackBox components.
Principally okay if there are posed clear reqs to foreign authority in form of a within manufacturing cycle integrated secure process.
In section there cannot be read s.th. like this

I find both the comment and the Roles section to be confusing. If we look at FMT_SMR .1, it very simply states that there are two roles.  In real life it might not be so simple, but these requirements deal only with two. (Although FMT_MSA.1 calls for a "list of roles," which seems odd.) I suggest searching on "role" throughout the document to make sure the term is used consistently.


Cleaning up repository; Updating use menu and GitHub issue formatting

Closed Issue #18 on this repository shows the new GitHub output


Read collection name from @document value in addition to collection attribute.

While debugging #62 I found some issue when not using @Document(collection="cars")
In PersistentPropertySavingCallback Line 115
String collection = ReflectionsUtil.getGenericType(field).getAnnotation(Document.class).collection();

Only a getter for collection() is used. However like in my example you can define the collection name also by omitting document= and just using the value attribute.
@Document("cars")
data class Car(
    @Id
    val id: String,
    val name: String,
)

The logic therefore ignores the collection name. Unfortunately it does not solve the problem I mentioned above

Hello @xetra11 thank you for reporting the issue, it will be fixed in the coming release.

@kaiso I already created a pull request

@xetra11 Fixed in version 3.4.1
please feel free to report new issues if any and thank you for using RelMongo


Add integration for StreamElements

Stream elements integration will be needed to trigger events based on donations, redemptions etc.
The main concern here is that we use implicit oauth flow (so we don't need to bundle client secrets etc), so need to verify that we can auth the same way as we do with twitch etc.

I have tried multiple times in their discord server to confirm terms and PKCE support for OAuth as this is not being done under a company banner and they require a company, also their docs only seem to support secret based OAuth.
I will try again in the future but not much I can do at the moment.

I have pestered again and no progress, until they allow API access there isnt much I can do this side, also its unclear if they are able to offer PKCE style oauth scenarios, or at least implicit auth etc where we do not need to pass the secret around.

Another month, no feedback from them, so I assume for the moment we won't be able to integrate with their API.

So turns out we can use JWT tokens to communicate which should make this doable, going to research it and see if I can get a feature merged in soon for it.

Basic triggers have now been implemented here in #78

Im going to mark this as done as unless someone else wants more triggers it does everything needed for my current use case and a new issues/PR can be added for specifics.


[usbdev,dv] Remove usb20_if uses from usbdev block-level DV

There's a slightly complicated situation where we currently have two USB interfaces (usb20_if and usb20_block_if).
At the moment, usb20_if is used at chip-level (interfacing over DPI with a USB reference model) and usb20_block_if is used at block level.
Keeping them separate avoids block-level DV engineers who can't run chip-level tests breaking chip-level sims. This is a slightly silly situation and the right eventual solution would probably be to merge the two interfaces again.
But a short-term cleanup is to remove the chip-level-only interface from the block-level testbench.

After we discussed this, I've given it a bit more thought and I think this is really not the right time to be performing this tidy up when things aren't actually broken, so I'd rather park it for now, please.
The DPI model does an awful lot more verification than our DV block level presently does, including:

reads descriptors using complete Control Transfers as per a real USB host, and configure the device
streaming and checking of LFSR-generated test to/from maximal endpoints, most transfer types
injection of faults
Low Speed traffic, invalid traffic, unexpected device addresses and endpoints
Suspend, Resume signaling, Disconnect, Reconnect, Bus Resets

The main limitations of the DPI model are not in the DPI model itself but rather the way that it is used; at chip level, it takes a long time to build the chip model, and then to simulate.
At block level, if connected into the DV environment it could more readily offer randomization, particularly signal timing/inter-packet delays etc, and would likely give us greatly improved coverage even without modification, since it is already the product of months of work that still remain to be done in the block level SV/UVM code.

Ok, that makes sense. My long-term aim is to merge the two interfaces, and switch the block-level DV to use the merged version. But I don't have strong feelings about the ordering! Let's leave things as they are for now.


Publish on PyPI?

Would it be possible to publish this package on PyPI, to make installation easier?
There doesn't appear to be any way to actually install the package.
Even installing from source fails:
$ git clone git@github.com:pykaldi/pykaldi.git
$ cd pykaldi
$ virtualenv -p python3.7 .env
$ . .env/bin/activate
(.env) python setup.py install
Could not find pyclif.
Please add pyclif binary to your PATH or set PYCLIF environment variable.

What is pyclif? It doesn't appear to be available on PyPI or the Ubuntu standard repo. Searching Google only finds references to this repo. I'm not sure if this was intentional, but setup.py should not depend on tools that are only available in the package it's meant to install.

Please read the installation instructions on the README.
And refer to my reply #164 for what is needed for a pip package.

Sorry, didn't see the conda commands.

The conda commands don't seem to result in a functioning install, even though I already have the libkaldi-asr Ubuntu package installed.
I ran:
conda create --prefix ./.cenv -c defaults -y python=3.6
conda activate ./.cenv
conda install -c pykaldi pykaldi-cpu
python
>>> from kaldi.asr import NnetLatticeFasterRecognizer
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/chris/git/pykaldi/kaldi/__init__.py", line 14, in <module>
    from . import base
  File "/home/chris/git/pykaldi/kaldi/base/__init__.py", line 1, in <module>
    from ._kaldi_error import *
ModuleNotFoundError: No module named 'kaldi.base._kaldi_error'

I ran all commands successfully in a docker container running miniconda.
So it seems to me that this is likely due to the location of where you ran this command.
It is picking on this file: /home/chris/git/pykaldi/kaldi/__init__.py instead of the ones shipped with the conda package.


Race in STM32 v2 I2C DMA TX

It seems there is a subtle race in the DMA TX I2c routine.
Steps to recreate:

Initiate a vectored write on a v2 I2c peripheral (tested with STM32L431RC) that has DMA configured.

First transfer is small (2 bytes in my example; the address to write to on an I2c FRAM device)
Second transfer is large (in the attached example it's 1288 bytes, but this happens in any transfer that is over 256 bytes).

See the second transfer results in a panic on the call to master_continue AFTER the last chunk has been queued, but before the I2c EV irq has fired.

I've attached a gist with a patch to show the log statements I added to narrow down the issue, as well as a sample of the output (which is 100% re-creatable).
From what I've seen (and from my rough understanding of how the wakers/task storage works), it appears that on the last chunk's transfer being completed by the DMA peripheral, it fires it's IRQ to indicate that the transfer has completed. Since the DMA Transfer object was created/registered from the same task as the actual poll_fn in the DMA write implementation, the task is polled again, where the poll_fn in the I2c dma write is polled, however, this happens before the I2c peripheral has triggered it's EV Irq, which updates the number of chunks transferred, so in this instance the poll_fn triggers another master_continue call, which panics, since it is sent a length of 0.
https://gist.github.com/ericyanush/c362e883a0ded1a367e9d5d44c8f8852

In terms of a fix I see two options:

Track whether the EV irq has completed before reading state.chunks_transferred.
Move to remaining_len as the tracking variable.

Looking at the code, I can't see a reason why chunks_transferred needs to be independently tracked when remaining_len is available. I don't have access to an l4 at this point, but if you want I can propose changes that you can try to see if they resolve the problem.

@ericyanush can you confirm whether #1370 fixes your issue? Thanks!

I can confirm that #1370 fixes the issue I encountered! Thanks @xoviat for getting that fixed so quickly!


[CM-1829] ??? coming for non English titled docs while uploading

Summary

Removed AWS-ENCRYPTED- from the file name.

@AbhijeetRanjan308  docs need to be updated


Authenticate user

Hello,
Thanks for this bundle!
I was wondering, is there any way to authenticate a user with this current version?

Hi Elodie,
this is not yet possible with the bundle, but I am working on it - the base library this bundle is based upon already has the authentication support, so you could implement that in the meantime: https://github.com/kreait/firebase-php/releases
I hope that I can update the bundle in the next week.
Cheers

Jérôme

OK, I was thinking about doing a PR after updating firebase-php to version 0.6.1 but if you're going to work on it, I can wait :)
Thanks again.

If you already have something, please proceed - I am only hoping to get to it next week :)

I don't have anything yet. I just took a look around and found an issue : the http-adapter-bundle requires version 0.6.0 for the http-adapter whereas firebase-php requires version 0.7.0. I'll try to work on it this weekend.

I just released a new version of the bundle which includes the latest firebase-php release. It's a bit rough on the edges and includes manual work in your application code, but I think it is a start.
https://github.com/kreait/firebase-bundle#authentication
It includes adding a new configuration parameter secret to a connection, an additional composer require firebase/token-generator and the addition of some code in your controller or service:
$firebase       = $this->container->get('kreait_firebase.connection.main');
$tokenGenerator = $firebase->getConfiguration()->getAuthTokenGenerator();

$adminToken     = $tokenGenerator->createAdminToken();

$firebase->setAuthToken($adminToken);

Please let me know if this is a starting point you could work with.

Hello Jérôme,
Thanks a lot it's perfectly working! You did a great job.
Cheers

Thanks for the feedback, Elodie - I will close this issue then :)


PI-648 Improve error logging in Risk Assessment Scores to Delius consumer

Adds parsing of validation errors from the stored procedure, to better categorise them in Sentry and App Insights
Adds new method addToContext to the TelemetryService, to ensure customDimensions are added to requests and exceptions as well as custom events.
Adds tests for the RiskScoreService

Notice end to end tests are now ran against the branch - nice, but does it matter they failed? Not for the same project as the PR -- but since common telemetry was changed I guess it ran them all.

@anthony-britton-moj sorry no I'm just doing some testing from by triggering the pipeline from the branch, to check what appears in Sentry/App Insights.


PoC for additional metadata

This adds a new Dict[str, str] to the metadata in a SafeTensors objects, that can save any user metadata associated to some weight file in this format.
The main use right now is to save the format used when saving a model (PyTorch, TensorFlow etc) so I know on the Transformers side if a conversion of weights should be applied or not.

Thank you !
And congrats for the first rust PR !
I would suggest moving the structure Metadata to an actual struct, and ideally without breaking change (not because we can't at this point everything is up in the air but more because it feels more JSONy to have a "special" field)
Something like this:
#[derive(Debug, Deserialize, Serialize)]
pub struct Metadata {
  #[serde(skip_serializing_if = "Option::is_none")]
  #[serde(rename = "__metadata__")]
  metadata: Option<HashMap<String, String>>,
  #[serde(flatten)]
  tensors: HashMap<String, TensorInfo>,
}

Here is one example: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=e7561254982212418f956549a538d2d8
Another example (Option vs empty hashmap) : https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=e7561254982212418f956549a538d2d8
Aside from that the rest looks really nice !


Default styling for react

Does this come with any default styling?

No, there aren't any styles that ship by default. It is unopinionated as far as styling goes. The CSS styles in the example folder might help if you're looking for a place to start.


Project directory structure for "modern CMake"

Brief Issue Summary
First I am new to VS Code and vscode-cmake-tools, so this may be a case of total ignorance.
In general we try to layout our CMake projects alog the lines of :  https://cliutils.gitlab.io/modern-cmake/chapters/basics/structure.html
So we have dir structure that look like:

CMakeLists.txt
docs
src

CMakeLists.txt
fred.cpp
sue.f90    (Yes we still use FORTRAN)

test

CMakeLists.txt
test1.cpp

I am having issues with VS-Code following the hierarchy  .... should it be able to follow the sub dirs?
Thanks.

This should work fine.  Could you explain what isn't working?

Sorry it took a while to get back to this. I think I have things working fairly well. Let me discuss a few of my issues:

My projects can take a while for a clean build, sometimes up to an hour. This makes the single binary "build" dir inconvenient as it gets purged every time you toggle build types.  This little gem get's me around that issue: ( in the settings.json file)
cmake.buildDirectory": "${workspaceRoot}/build/${buildType}

I use Conan (conan.io) as my C/C++/FORTRAN package manager across Win/*nix OS ... to get Intellisense to work : ( again in the settings.json file)

"C_Cpp.default.includePath": [
        "c:\\Users\\${env.USERNAME}\\.conan\\data\\**",
        "C:\\.conan\\**"
    ]

This last one is a little weird because conan could be installed in two locations.  For a normal user, in $HOME, for my Jenkins build node just on c:\

Overall I am still quite positive on VS Code. I am a mechanical engineer by training and know the value of a tool that feels "right" in your hand as you use it.  (Think of a hammer :), you know what to do with it when you pick it up )

So this tool has to fit in my work flow task list ...

- Check code in/out of Git
- Edit Code
- Build debug/release code
- Generate developer & user doc
- Run unit test
- Perform static code analysis
- sure I missed something here .....

VS Code seems to do a reasonable job.  ( I may sound jaded but after ~40 yrs in the business you see tools come and go, and it is hard to get TOOOO excited )

Thanks and regards

Thank you for the feedback.
Regarding bullet (2.), you don't need to set any include paths if you allow CMake Tools to be the configuration provider.
Try to set C_Cpp.default.configurationProvider to "ms-vscode.cmake-tools" in your project settings.
Let us know if conan isn't working for you in this case.


Add fake utility for cli calls

Description of your changes
Fixes #81
This PR adds a utility for the command calls. There are two interfaces to manage the command and command outputs.
Mock tests can be written by using this utility. StdErr and StdOut values can be manipulated via FakeExec struct that implements the Fake call of the CombinedOutput function.
In real CombinedOutput function, the StdErr and StdOut values are assigned to the same bytes.Buffer instance. Therefore, I also tried to implement the same logic in this PR.
I have:

[x] Read and followed Crossplane's contribution process.
[x] Run make reviewable to ensure this PR is ready for review.
[x] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested
This PR was tested by adding a toy test to observe the fake functions are working properly.

Hi @muvaf thanks for your review. I addressed many of your comments. However, I left a few questions to better understand some of them.

@sergenyalcin has decided to use an implementation from k8s libraries, which turned out to be very similar to his design, so we don't need this anymore.


[QSP-11] emit events before external calls

Codecov Report

Merging #268 (995d399) into develop (ef970de) will increase coverage by 17.79%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           develop     #268       +/-   ##
============================================
+ Coverage    71.73%   89.52%   +17.79%
============================================
  Files           68       33       -35
  Lines         2257     1079     -1178
  Branches       335      150      -185
============================================
- Hits          1619      966      -653
+ Misses         638      113      -525

Flag
Coverage Δ

batch-submitter
?

contracts
89.52% <ø> (ø)

core-utils
?

data-transport-layer
?

message-relayer
?

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

Impacted Files
Coverage Δ

packages/data-transport-layer/src/utils/eth-tx.ts

packages/core-utils/src/watcher.ts

packages/core-utils/src/index.ts

.../batch-submitter/src/transaction-chain-contract.ts

...ices/l1-ingestion/handlers/state-batch-appended.ts

...ices/l1-ingestion/handlers/transaction-enqueued.ts

packages/batch-submitter/hardhat.config.ts

...ubmitter/src/batch-submitter/tx-batch-submitter.ts

...kages/data-transport-layer/src/utils/validation.ts

packages/core-utils/src/coders/sequencer-batch.ts

... and 25 more

Continue to review full report at Codecov.

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


indilib pkg, added support for aarm64, added snick as maintainer

Hi @hjones2199 ,
I'm one of the developers for sky360.org and I want to add support for indilib QHY firmwares for raspberry pi 4. Was wondering if you can share some thoughts?
I created 3 issues with some dependencies to start.
https://github.com/NixOS/nixpkgs/issues/200135 'indi-full' support for aarch64
https://github.com/NixOS/nixpkgs/issues/200154 QHY CCD SDK
https://github.com/NixOS/nixpkgs/issues/200152 fxload does not support USB3 devices using the -fx3 flag
Best,
snick

@hjones2199 any chance you can review this PR?

@hjones2199 can you review this PR?

Closed by #243071 for the title. If there are any other changes, please open a new PR, thanks.


cloudsql error thinking sql instance onprem

Hello,
I am running into an issue executing terraformer plan google --resources=cloudsql --regions=us-east4 --projects=project1
The command errors out after these lines. The error is google error initializing resources in service cloudsql, err: googleapi: Error 400: The requested operation is not valid for an on-premises instance., errorOnPremisesInstanceInvalidOperation
If I am reading the code correctly, it is supposed to run sqladmin.Service.Instances.List and sqladmin.Service.Databases.List. I've tried both methods (databases.list and instances.list) under the Try this method windows that pop up and I was able to retrieve the data no problem.
I am hoping to understand how the terraformer API call is detecting that my instances are on-premises or is it even erroring out on those two methods and I am missing something?
Thanks in advance and please let me know if you need more info!

FWIW - the command works fine on another project I have. I believe it is how the CloudSQL instances in the "project1" was created and I would like to know what the root of the issue is.


Question: Do the Accelerometer/Gyroscope values need to be divided by their corresponding sensitivity values?

Required Info

Camera Model
D400

Firmware Version
<IP_ADDRESS>

Operating System & Version
Linux (Ubuntu 18)

Kernel Version (Linux Only)
5.4.0

Platform
Computer

SDK Version
2.44.0

Language
C++

Segment
{Robot/Smartphone/VR/AR/others}

Issue Description:
When we get linear acceleration values from the accelerometer and the angular velocity values from the gyroscope, do they need to be divided by their corresponding sensitivity values to get the actual physical linear accelerations and angular velocities? or that step is already done by the librealsense API before outputting those values so I don't have to worry about that?
For example, as per the datasheet and https://github.com/IntelRealSense/librealsense/issues/12492#issuecomment-1843001319,

Sensor
Range
Sensitivity

Accelerometer
±4 g
512 LSB/g

Gyroscope
±1000 °/sec
32.8 LSB/°/sec

So, when I get the rs2::motion_frames through the API, do I need to divide the motion_data by 512 (for RS2_STREAM_ACCEL) or 32.8 (for RS2_STREAM_GYRO) to get the actual physical value? or the librealsense API has already abstracted that step?
Note:

The main confusion is for the Gyroscopt because everything in the datasheet is in deg/sec but from my understanding/observation and https://github.com/IntelRealSense/librealsense/issues/3107#issuecomment-456702580:

The gyro readings provided by Librealsense are rad/sec

In the case of the accelerometer, everything in the datasheet is in g i.e. m/s^2 and the accel readings provided by the API are also in m/s^2. So, what should I do for the accelerometer?

Hi @milan-r-shah  You do not need to perform division on the IMU values.
The table below from Intel's Getting IMU Data guide confirms that the unit of Accel is m/s2 and the unit of Gyro is rad/sec.
https://www.intelrealsense.com/how-to-getting-imu-data-from-d435i-and-t265/

Hi @milan-r-shah  Do you require further assistance with this case, please?  Thanks!

@MartyG-RealSense thank you for your response.
So, whatever output I get from either the accelerometer or gyroscope, represents the actual physical quantity, correct?
The librealsense API abstracts all the internal calculations that convert the BMI055 raw data into the actual physical measurements, right?

Yes, the outputs represent the actual values.
The notes in the table related to that bias and scale reference indicate that whilst correction is not built in to 400 Series cameras equipped with an IMU, the correction can be performed with the SDK.  https://github.com/IntelRealSense/librealsense/issues/3166 shows that it is likely referring to the SDK's Python IMU calibration tool.

Hi @milan-r-shah  Do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.


Clip not works well in centos

Puppeteer version: 0.10.2
Platform / OS version: centos7

I want to clip one web page into lots of images so I can put the images on my home page to replacing the origin HTML.
The following code is trying clip images from one page, it works well in OSX. When I put the code into the server(server is running centos7), a weird thing happens, some images are not in the right size, just like the pic under the code.
const browser = await puppeteer.launch({
    dumpio: true,
    args: ["--no-sandbox"],
    timeout: 10000
});
const page = await browser.newPage();
await page.emulate(iPhone);
await page.goto(url);

const dimensions = await page.evaluate(() => {
    return {
        width: document.documentElement.clientWidth,
        height: document.documentElement.clientHeight
    };
});

var htmlHeight = dimensions.height
var htmlWidth = dimensions.width

var clipHeight = 300
var y = 0
var index = 1;
var imageArray = []
console.log(chalk.green('generating images....'))
while (y < htmlHeight) {
    var clip = {
        x: 0,
        y: y,
        width: htmlWidth,
        height: clipHeight
    }
    index++
    var data = await page.screenshot({ type: 'jpeg', quality: 90, clip: clip })
    data = data.toString('base64')
    imageArray.push(data)
    y += clipHeight

    if (y + clipHeight > htmlHeight)
        clipHeight = htmlHeight - y
}

var head = ''
var images = '';
imageArray.forEach(img => {
    images = images + '

'
})
var foot = ''
var html = head + images + foot

The wrong clip:

The right clip should be like this:

As it shows in the pic, the image I highlighted is not in the right size. It looks a little small.
This phenomenon never happens on my Mac, but it happens in Linux. I can't understand why this happens...

Similar issue to #802

It seems I have found the reason for this phenomenon...
My Linux device performance is better than my Mac, so the code in Linux is running faster than Mac. As far as I can see, if the clip of a page in Mac need 15s, the same operation in Linux may just need 2s~3s.
Maybe the operation running too fast caused this bug? An idea comes to my mind by chance, So I change the clip code to this
before
var data = await page.screenshot({ type: 'jpeg', quality: 90, clip: clip })

after
var data = await doScreenshot(page, clip)

var doScreenshot = (page, clip) => {
  return new Promise(resolve => {
    setTimeout(() => {
      page.screenshot({ type: 'jpeg', quality: 90, clip: clip }).then(data => {
        resolve(data)
      })
    }, 200); // wait 200ms between every clip
  })
}

I added intervals between every clip, so the operation speed in Linux is slowed. After changing the source code, I tested A dozen times and the bug is gone.
I am feeling strange of this, and I think my new way is a dirty hack, I can't understand why the speed
too fast can make this question.

My workaround was to check the image size, and re-render if it was incorrect.
Your idea about something happening too fast is consistent with how the bug manifested for me. It works mostly fine on my local machine (in a 4cpu docker container), but running on a 16 cpu vm, it happens much more often.

May I ask how to check the image size?

There are various node modules that do this. Quick googling will help you
On Sep 17, 2017 8:06 PM, "Derobukal"<EMAIL_ADDRESS>wrote:

May I ask how to check the image size?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GoogleChrome/puppeteer/issues/800#issuecomment-330119647,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB1HfDoY8-IzAuEn8jrZLb9i_MdbbODTks5sjd4ogaJpZM4PZEoU
.

try to set: await page.setJavaScriptEnabled(false);
I have same issue and this works...

@RitterHou is this still an issue? Can you please try on the latest puppeteer and see if it works.


remove duplicated word definitions

Hi @44uk We are using the integration branch for now for all PRs, could you rebase the integration to yours, please?

Create new branch from integration.

It is already resolved.


Call git-ps ls after git-ps pull

Currently whenever I called git-ps pull I usually end up having to call git-ps ls after since the stack has changed. Or I just do git-ps pull && git-ps ls in a single call so I can see the updated stack.

One thing I have been talking with other people about on this front is exposing additional commands that are lower level (plumbing) commands if you will to facilitate people being able to easily configure shell aliases or scripts.
I know this isn't necessarily answering this specific request. But what do you think about this stance in general? Should we provide examples of zsh aliases or something?
My take so far is that I think we should provide these lower level (plumbing) commands because it opens up the scriptability of different workflows with Git Patch Stack.

Once we have issue #37 maybe this is something that could be added just as a configuration.

This has been integrated into mainline therefore I am closing this issue.


Use a larger hitbox for selecting pedestrians and bicycles.

As discussed in Slack, this is an initial attempt to make it easier to click tiny moving pedestrians and cyclists. It enlarges the hitbox to a circle with 2m radius and draws the hover style as an outline.
TODO before considering merging this:

[ ] Also implement for pedestrian crowds (which are always half the sidewalk width, but rarely may grow to be kind of long)
[ ] when the hitboxes overlap, pick the agent closest to the cursor

TODO before considering merging this:
Also implement for pedestrian crowds (which are always half the sidewalk width, but rarely may grow to be kind of long)
when the hitboxes overlap, pick the agent closest to the cursor

My 2cents is that this is an incremental improvement worthy of merging even without these TODO's

@michaelkirk, it kind of felt like a regression in functionality to remove the player's ability to precisely pick an agent, so I felt weird about checking in this without a bit more work. But I added the "closest to the cursor" logic and it feels pretty good, so I think this is ready now.


Is there a faster way

Hello!
when l use run-asm-pipeline.sh to get the final things,l find the speed is really slow. is there any way to use multicore to get the result quicker?
Yours!

The pipeline is already parallelized if you have GNU parallel. If you do not have parallel it will give you a warning. Otherwise you should see the multiple cores being utilized during scaffolding. If there is a particular step that is you concern please list details.
Olga

On Aug 1, 2021, at 6:01 AM, ld9866 @.***> wrote:

Hello!
when l use run-asm-pipeline.sh to get the final things,l find the speed is really slow. is there any way to use multicore to get the result quicker?
Yours!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Column Picker Presets in toolbar

HI there,
I've been transitioning a lot of my code into the .TypeScript flavor of serenity and I've been playing around with the column picker.
I got the thought of using preset column pickers to create templates for the toolbar that will make up for quick preset I can then export using the excel exporter or pdf printer.
I'm picking through the column-picker code but I figured I'd ask if you have any suggestion on the approach to create tool buttons that designates which columns to hide.
i've been playing with the xyzGrid.ts with the following but still no success:
getButtons() {
var buttons = super.getButtons();
var MyRow = MatrixRow.Fields;
        buttons.push(Serenity.ColumnPickerDialog.createToolButton({
            grid: this,
            visibleColumns: MyRow.Make, MyRow.SerialNumber

        }));

        return buttons;
    }

I also find interesting the possibility of having these views appear in separate windows if possible since I could then set it in the navigation file so that I can click right into the view of choice from the side menu and then control the access to the views according to tenancy.
Anyhow, Any guidance?

You shouldn't use ColumnPicker for this, see guide about persisting / restoring settings manually.

I continue to read on the persistent storage but, i may be (definitely am) in over my head. I've managed to get the persistent storage to function as needed while using the UserPreferences without much issue but I'm having difficulty in figuring out how to properly define multiple predefined lists of which columns to hide so that I may create button triggers for them.
Here is what I have so far:
In ScriptInitialization.ts (btw, manual says SiteInitialization.ts. Typo) I added the line:
Serenity.DataGrid.defaultPersistanceStorage = new UserLocalStorage();

Then defined the custom provider in a separate .ts file:
namespace FMCDashboardv3 {
export class UserLocalStorage implements Serenity.SettingStorage {
    getItem(key: string): string {
        return window.localStorage.getItem(
            Authorization.userDefinition.Username + ":" + key);
    }

    setItem(key: string, value: string): void {
        window.localStorage.setItem(
            Authorization.userDefinition.Username + ":" + key, value);
    }
}

}
In the MatrixGrid.cs (the section I want with the views) I will be adding multiple buttons that will call the predefined view on click.
           buttons.push({
            title: 'ReportView1',
            cssClass: 'add-button',
            onClick: () => {
                this.getPersistanceStorage(<FMCorp.MatrixRow>{/*//<reference to function that hides un-needed columns>//*/ });
            }
        });

If I make progress on my own I'll write an update

See methods at the end of guide, they are what you should call to store some settings manually and restore. Anyway user store is not somewhere you should store your custom settings. Take them from there ok but save them to a global table.

Alright, I'll give that a try and let you know how it plays out. thanks for the gudance

I may add a sample later for presets. Probably in a reporting page.


Only fullscreen activities can request orientation

when I call Orientation.lockToLandscape(),App crash on resume.
log:
Only fullscreen activities can request orientation
"react-native-orientation": "^3.1.3",
Environment:
OS: Windows 7
Node: 8.12.0
Yarn: 1.9.4
npm: 6.4.1
Watchman: Not Found
Xcode: N/A
Android Studio: Not Found
Packages: (wanted => installed)
react: 16.3.1 => 16.3.1
react-native: ^0.55.4 => 0.55.4

Use a react-native-orientation-locker module with normal support ! :+1:

@retyui thanks,it works well.


Restore NodeSelections correctly

When restoring a selection, currently NodeSelections are erroneously converted to a TextSelection.
Here is the default prosemirror collab example which does not use y-prosemirror the NodeSelection is preserved correctly while syncing updates from another editor:
https://user-images.githubusercontent.com/7319708/181288342-6bd356e6-65ce-439e-ba16-ea1c4dc07bcc.mov
Here is a tiptap example which uses yjs, NodeSelection (use CTRL+CLICK to select a text node) gets converted to a TextSelection while syncing updates from another editor:
https://user-images.githubusercontent.com/7319708/181289479-5f86ad5d-4ee5-4bf6-9051-0521db6a13b1.mov
This commit ensures that NodeSelection is correctly restored as a NodeSelection while syncing yjs updates across editors.

Another example demonstrating the issue where a NodeSelection gets converted to a TextSelection using the yjs prosemirror demo at https://github.com/yjs/yjs-demos/tree/main/prosemirror
https://user-images.githubusercontent.com/7319708/181356184-d2fc43e1-4a3f-4fd5-b6f0-44a58958428d.mov

yjs prosemirror demo with the changes in this MR retains the NodeSelection as expected:
https://user-images.githubusercontent.com/7319708/181357428-64a792cc-5c3b-4d08-8628-b4fbbb63b4fc.mov


Add Service-Down-URL

Change Log

Adds the ability to configure Service-Down-URL with the bin/configure-login-hook.sh script

Thank you, I'll run the tests and make sure any relevant docs are updated.


population statistics: student credits since start caclucated more wrong than ever

Eläinlääketieteen koulutusohjelma 2013:

This "bug" seems strange. The "all credits" value comes from the student/:number/info endpoint directly as a number and when we checked the credits list for the affected students it seemed like the list did not contains any wrong/flunked courses and the sum of the credits is exactly the value shown under the "credits since start" column.


Create testarti.yaml

Welcome to npm, 0e.vc2!
To complete your npm sign up, and as an additional security measure, you are requested to enter the one-time password (OTP) provided in this email.
The OTP code is: 83124234
We are also recommending that you enable two-factor authentication (2FA) with a trusted device so you will not be asked for an OTP over email with each log in.
2FA is an extra layer of security used when logging into websites or apps. With 2FA, you have to log in with your username and password and provide another form of authentication that only you know or have access to. 2FA also protects package publishing. When you publish a package from the command line you will be prompted to provide a generated token in order to do so. Don’t worry, if you want to automate publishing in CI/CD you can use an Automation Token to allow for publishing via token only without 2FA. https://github.blog/changelog/2020-10-02-npm-automation-tokens/
To enable 2FA, please follow the instructions found here. https://docs.npmjs.com/configuring-two-factor-authentication
To create an automation token, please follow the instructions found here. https://docs.npmjs.com/creating-and-viewing-access-tokens
If you have any questions or concerns please feel free to reach out to the npm support team. https://www.npmjs.com/support
You’re receiving this email because you recently created an npm account. If this wasn’t you, please ignore this email.
Thanks,
The npm team

Hi, 0e.vc2!
It looks like you are trying to log in to npm using your username and password. As an additional security measure you are requested to enter the OTP code (one-time password) provided in this email.
If you did not intend to log in to npm, please ignore this email.
The OTP code is: 23244609
If you enable two-factor authentication (2FA) with a trusted device you will not be asked for an OTP over email anymore.
2FA is an extra layer of security used when logging into websites or apps. With 2FA, you have to log in with your username and password and provide another form of authentication that only you know or have access to. 2FA also protects package publishing. When you publish a package from the command line you will be prompted to provide a generated token in order to do so. Don’t worry, if you want to automate publishing in CI/CD you can use an Automation Token to allow for publishing via token only without 2FA. https://github.blog/changelog/2020-10-02-npm-automation-tokens/
To enable 2FA, please follow the instructions found here. https://docs.npmjs.com/configuring-two-factor-authentication
To create an automation token, please follow the instructions found here. https://docs.npmjs.com/creating-and-viewing-access-tokens
If you have any questions or concerns please feel free to reach out to the npm support team. https://www.npmjs.com/support
Thanks,
The npm team

Hi 0e.vc2!
A new version of the package test-codecpetjs-bdd-tests (1.2.1) was published at 2023-12-19T14:52:49.701Z from <IP_ADDRESS>.
The shasum of this package is 4bea709fc33cb52b14fc28c436fa352161b81cdc.
If you have questions or security concerns, you can contact us at https://www.npmjs.com/support.
Thanks,
The npm team.

Hi 0e.vc2!
A new version of the package test-codecpetjs-bdd-tests (1.2.2) was published at 2023-12-19T14:53:39.229Z from <IP_ADDRESS>.
The shasum of this package is 715e01d989469f2225e0f8ace4c8d344fd414187.
If you have questions or security concerns, you can contact us at https://www.npmjs.com/support.
Thanks,
The npm team.

Hi 0e.vc2!
A new version of the package test-codecpetjs-bdd-tests (1.2.4) was published at 2023-12-19T15:03:03.453Z from <IP_ADDRESS>.
The shasum of this package is 0b78a4cc1cdacddeb408fe30898af87c1be7696c.
If you have questions or security concerns, you can contact us at https://www.npmjs.com/support.
Thanks,
The npm team.


Update #158 fix for request module and strict SSL

Commit 48e8be5 added a compatibility fix for users of the request
NPM module and strict SSL cert checking. The request module has
since been updated (see https://github.com/request/request/pull/1615
for more details), and a corresponding change should be made in
nock to ensure compatibility.

@jeffomatic thanks!
Landed on v3.6.0.

Thanks for the super-quick review/merge!
On Wed, Dec 23, 2015 at 4:01 AM, Pedro Teixeira<EMAIL_ADDRESS>wrote:

@jeffomatic https://github.com/jeffomatic thanks!
Landed on v3.6.0.
—
Reply to this email directly or view it on GitHub
https://github.com/pgte/nock/pull/430#issuecomment-166875566.


could not compile pyo3 90 or so specialization errors.

I am trying to install a python module on an M1 macbook, and pip is failing to do so. I have tracked the problem as far as pyo3, which fails to compile because of errors like:
         --> /Users/cdock01/.cargo/registry/src/github.com-1ecc6299db9ec823/pyo3-0.6.0/src/instance.rs:564:5
          |
      549 | impl<T: ToPyObject + ?Sized> ManagedPyRefDispatch for T {}
          | ------------------------------------------------------- parent "impl" is here
      ...
      564 |     fn drop_impl(_: &mut ManagedPyRef<T>) {}
          |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ cannot specialize default item "drop_impl"
          |

And then finally error: could not compile "pyo3" due to 89 previous errors
That appear when running pip install autopy.
Output of rustup show is:
Default host: aarch64-apple-darwin
rustup home:  /Users/cdock01/.rustup

nightly-aarch64-apple-darwin (directory override for '/Users/cdock01')
rustc 1.66.0-nightly (ce7f0f1aa 2022-09-28)

PyO3 0.6 is really old (0.17 is current). Could you try this using a newer version of PyO3? Or at least a stable version of Rust?
(This might be really old code that uses nightly feature from that time. Those features do have the same stability guarantees as the rest of the Rust language and hence might have been broken by changes to the Rust compiler in the time since PyO3 0.6 was released.)

Oh good call, solution is here: https://pypi.org/project/autopy/
Somehow I missed it:
"Note: AutoPy currently requires the 2019-10-05 Rust nightly in order to build from source. This is to maintain compatibility with an older version of PyO3, as the latest version has dropped Python 2 support. Python 2 support will likely be dropped from AutoPy as well sometime later this year, depending on how necessary it is to upgrade to a more recent version of PyO3 or Rust. In the meantime, it may be necessary to install the required nightly via the following when building locally:
rustup install nightly 2019-10-05 --force
This is due to rustup complaining that it doesn't include certain components such as rustfmt."

Except that toolchain name is invalid. Looks like I need to find a replacement for autopy.

Except that toolchain name is invalid. Looks like I need to find a replacement for autopy.

Yeah, they do not archive all those nightly that far back. I am not sure if this work, but dirty hack might be to install a stable version that was released around the same time (those should be archived much longer) and set the environment variable RUSTC_BOOTSTRAP=1 to make its nightly features available?
But yes, updating autopy to use a recent version of PyO3 would certainly be best (especially since PyO3 does not require nightly any more).

In the end for me it's not worth using libraries that use ancient versions of their dependencies lol, I switched to pynput and that worked fine.

Yeah, the "later this year" would have been 2020.


⚠ ClamAV has degraded performance

In e56e927, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 503 ms

Resolved: ClamAV performance has improved in 39b95d7.


Unsupported Filter over SemiJoin

Semi-joins with additional filters are not yet supported in Prestissimo / Velox:
SELECT * FROM lineitem
WHERE orderkey < 10 OR orderkey IN (SELECT orderkey FROM orders WHERE (orderkey + custkey) % 2 = 0);

VeloxUserError:  Unsupported Filter over SemiJoin: ...

From @XuPingyong
TPC-DS q45 fails with: Unsupported Filter over SemiJoin
--TPC-DS Q45
select  ca_zip, ca_city, sum(ws_sales_price)
 from web_sales, customer, customer_address, date_dim, item
 where ws_bill_customer_sk = c_customer_sk
 	and c_current_addr_sk = ca_address_sk
 	and ws_item_sk = i_item_sk
 	and ( substr(ca_zip,1,5) in ('85669', '86197','88274','83405','86475', '85392', '85460', '80348', '81792')
 	      or
 	      i_item_id in (select i_item_id
                             from item
                             where i_item_sk in (2, 3, 5, 7, 11, 13, 17, 19, 23, 29)
                             )
 	    )
 	and ws_sold_date_sk = d_date_sk
 	and d_qoy = 2 and d_year = 2002
 group by ca_zip, ca_city
 order by ca_zip, ca_city
 limit 100;

Originally posted by @XuPingyong in https://github.com/facebookincubator/velox/issues/2820#issuecomment-1276917192

CC: @rui-mo Rui, I'm curious how Gluten plans with query (TPC-DS q45). Does it use Spark's Java operators for the semi join?

CC: @rui-mo Rui, I'm curious how Gluten plans with query (TPC-DS q45). Does it use Spark's Java operators for the semi join?

Masha, I checked both q45 and above query, and found they were similar. In Spark, it is planned as a ShuffledHashJoin with existence join type and a filter as below.
(122) ShuffledHashJoin
Left keys [1]: [i_item_id#363]
Right keys [1]: [i_item_id#852]
Join condition: None

(123) Filter
Input [5]: [ws_sales_price#751, ca_city#244, ca_zip#247, i_item_id#363, exists#913]
Condition : (substr(ca_zip#247, 1, 5) IN (85669,86197,88274,83405,86475,85392,85460,80348,81792) OR exists#913)

ExistenceJoin in Spark appends a column of boolean type after the left table to illustrate whether one row is joined or not. This join type is not supported in Gluten for now, so in TPC-DS q45, this join is executed by vanilla Spark and this filter is executed by Velox. But we are working on enabling more operators and functions to offload more computing into Velox.

@rui-mo Rui, thank you for the clarifying. This is very helpful. ExistingJoin in Spark appears to work similar to SemiJoin in Presto. Both act as a projection by emitting all rows from the left side with an additional boolean column set to true if there is a match, false if there is no match and null if "unknown" (left key is null and build side is not empty or there is no match and build side has a null).
In Velox, SemiJoin acts as a filter by emitting a subset of rows from the left side for which there is a match on the right side. There is a left semi join and right semi join to allow for using the smaller side as the build side. Both semi joins support filter pushdown from build to probe side.
As @XuPingyong pointed out, the existing implementation of SemiJoin in Velox doesn’t support queries like TPC-DS q45.
Presto’s and Spark's semantics for the semi join do not allow for dynamic filter pushdown. Hence, we may want to keep Velox’s implementation, but extend it to allow the queries above. One option is to extend the plan node to allow for specifying whether semi join should act as a filter, i.e. produce a subset of the left side rows, or as a project, i.e. emit all the left side rows with an extra boolean column.
CC: @oerling

@XuPingyong I added support for semi join project in #3068. Would you try it out and let us know how it goes?

Thanks very much. LGTM.
But the error "Unsupported Filter over SemiJoin" still exists in prestodb/presto native-engine.

@XuPingyong That's right. I didn't update the plan translation in Prestissimo yet to use the kSemiJoinProject join type. Let me send out a PR with these changes.

@XuPingyong Here is a PR to update plan translation in Prestissimo to use kLeftSemiProject join:
https://github.com/prestodb/presto/pull/18616

@storm-dance Thank you for confirming that these changes are sufficient to fix the original issue.


System.cmd should call magick mogrify instead of mogrify

When using the portable binary version of imagemagick, the correct command on unix systems is magick mogrify.
https://github.com/route/mogrify/blob/master/lib/mogrify.ex#L381
the direct call to mogrify would only apply when installed from source (if i'm not mistaken).
I receive the following error tuple when attempting to save using Mogrify.save/2:
{:error, %ErlangError{original: :enoent}}

Full error is as follows:
iex(1)> Mogrify.open("~/Downloads/test.jpg") |> Mogrify.save()
** (ErlangError) Erlang error: :enoent
    (elixir) lib/system.ex:791: System.cmd("mogrify", ["-write", "/tmp/255784-test.jpg", "/home/ziinc/Downloads/test.jpg"], [stderr_to_stdout: true])
    (mogrify) lib/mogrify.ex:28: Mogrify.save/2
iex(1)>

I have tried writing a bash function in ~/.bashrc that points to magick but I think System.cmd calls the sh instead.

In case someone else comes across this issue, I am not sure this is related, but I was able to solve similar error I was having only when using Docker container (Homebrew works fine). I had to add imagemagick-dev as well imagemagick to final build to fix.

This library adds ImageMagick executable path configuration support in v0.8.0 (#89). Hopefully that helps with this issue.

This is manageable by adding to config.exs:
config :mogrify, mogrify_command: [
    path: "magick",
    args: ["mogrify"]
]
config :mogrify, convert_command: [
    path: "magick",
    args: ["convert"]
]
config :mogrify, identify_command: [
    path: "magick",
    args: ["identify"]
]


Why cfg parameter TRAIN.HAS_RPN printed out is different from actual value?

Even though TRAIN.HAS_RPN is set to True in yml file, it shows false in running time.
The console log is as below.
'TRAIN': {'ASPECT_GROUPING': True,
'BATCH_SIZE': 128,
'BBOX_INSIDE_WEIGHTS': [1.0, 1.0, 1.0, 1.0],
'HAS_RPN': True,
'IMS_PER_BATCH': 1,
'LEARNING_RATE': 0.001,
... ...
'USE_FLIPPED': True,
'USE_PREFETCH': False},
'USE_GPU_NMS': True}
cfg.TRAIN.HAS_RPN = False

See @cdathuraliya 's answer to #60 : the config file is not loaded properly

maybe config in experiments/cfgs/faster_rcnn_end2end.yml will overwrite them.


chores:  components of static indicators/error/async load

Description

fix: ui layout
fix: security alerts
feat: components of static indicators/error/async load

Modules

[x] UI
[ ] Controller
[ ] Agent
[ ] Client
[ ] Python-SDK
[ ] Others

Checklist

[ ] run code format and lint check
[ ] add unit test
[ ] add necessary doc

@waynelwz  should we commit yarn.lock file into repo?


Fix for the negative lines error for flake8

For #7349

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR)
[x] Title summarizes what is changing
[ ] Has a news entry file (remember to thank yourself!)
[x] Appropriate comments and documentation strings in the code
[x] ~Has sufficient logging.~
[x] ~Has telemetry for enhancements.~
[x] ~Unit tests & system/integration tests are added/updated~
[x] ~Test plan is updated as appropriate~
[x] ~package-lock.json has been regenerated by running npm install (if dependencies have changed)~
[x] ~The wiki is updated with any design decisions/details.~

Codecov Report

Merging #8476 into master will decrease coverage by 0.36%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #8476      +/-   ##
==========================================
- Coverage   59.39%   59.02%   -0.37%
==========================================
  Files         509      509
  Lines       23422    23423       +1
  Branches     3786     3782       -4
==========================================
- Hits        13912    13826      -86
- Misses       8604     8683      +79
- Partials      906      914       +8

Impacted Files
Coverage Δ

src/client/linters/flake8.ts
90.9% <0%> (-9.1%)
:arrow_down:

src/client/testing/serviceRegistry.ts
48.64% <0%> (-46.85%)
:arrow_down:

src/client/testing/codeLenses/main.ts
44.44% <0%> (-33.34%)
:arrow_down:

...t/datascience/jupyter/jupyterDataRateLimitError.ts
66.66% <0%> (-33.34%)
:arrow_down:

src/client/formatters/serviceRegistry.ts
75% <0%> (-25%)
:arrow_down:

...ience/jupyter/jupyterDebuggerRemoteNotSupported.ts
75% <0%> (-25%)
:arrow_down:

...cience/jupyter/jupyterDebuggerNotInstalledError.ts
60% <0%> (-20%)
:arrow_down:

src/client/common/utils/icons.ts
83.33% <0%> (-16.67%)
:arrow_down:

src/client/api.ts
78.57% <0%> (-14.29%)
:arrow_down:

src/client/datascience/cellFactory.ts
57.69% <0%> (-12.83%)
:arrow_down:

... and 10 more

Continue to review full report at Codecov.

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

@Ma007ks Thanks for the PR. Please add a new entry file.

 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.:x: Ma007ks sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@Ma007ks Thanks for the PR. Please add a new entry file.

Added.


Login related question

It runs very well. Not sure how to use it with my wechat account. Should I replace the appid and the password of my own in the following code? If true, do I need to encode it? If so, how?
HttpRequest request = HttpRequest.get(Constant.JS_LOGIN_URL, true, "appid", "wx782c26e4c19acffb", "fun", "new","lang", "zh_CN", "_", DateKit.getCurrentUnixTime());

Don't reply, I got it. I it is the appid used by webchat


Failed to activate the editorconfig package

[Enter steps to reproduce below:]

Update to 2.0

Atom Version: 1.11.2
Electron Version: 0.37.8
System: Mac OS X 10.11.6
Thrown From: editorconfig package, v2.0.0
Stack Trace
Failed to activate the editorconfig package
At Cannot find module './commands/generate'

Error: Cannot find module './commands/generate'
    at Module._resolveFilename (module.js:339:15)
    at Function.Module._resolveFilename (/Applications/Atom.app/Contents/Resources/app.asar/src/module-cache.js:383:52)
    at Function.Module._load (module.js:290:25)
    at Module.require (module.js:367:17)
    at require (/Applications/Atom.app/Contents/Resources/app.asar/src/native-compile-cache.js:50:27)
    at Object.<anonymous> (/Users/vovkasm/.atom/packages/editorconfig/index.js:9:25)
    at Module._compile (/Applications/Atom.app/Contents/Resources/app.asar/src/native-compile-cache.js:103:30)
    at Object.defineProperty.value [as .js] (/Applications/Atom.app/Contents/Resources/app.asar/src/compile-cache.js:208:21)
    at Module.load (module.js:357:32)
    at Function.Module._load (module.js:314:12)
    at Module.require (module.js:367:17)
    at require (/Applications/Atom.app/Contents/Resources/app.asar/src/native-compile-cache.js:50:27)
    at Package.module.exports.Package.requireMainModule (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:721:27)
    at Package.module.exports.Package.activateNow (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:173:16)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/package.js:156:32
    at Package.module.exports.Package.measure (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:92:15)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/package.js:149:26
    at Package.module.exports.Package.activate (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:146:34)
    at PackageManager.module.exports.PackageManager.activatePackage (/Applications/Atom.app/Contents/Resources/app.asar/src/package-manager.js:538:21)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/package-manager.js:519:29
    at Config.module.exports.Config.transactAsync (/Applications/Atom.app/Contents/Resources/app.asar/src/config.js:337:18)
    at PackageManager.module.exports.PackageManager.activatePackages (/Applications/Atom.app/Contents/Resources/app.asar/src/package-manager.js:514:19)
    at PackageManager.module.exports.PackageManager.activate (/Applications/Atom.app/Contents/Resources/app.asar/src/package-manager.js:497:46)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/atom-environment.js:779:28

Commands

Config
{
  "core": {
    "disabledPackages": [
      "metrics",
      "atom-ternjs"
    ],
    "excludeVcsIgnoredPaths": false,
    "openEmptyEditorOnStart": false,
    "projectHome": "/Users/vovkasm/work",
    "telemetryConsent": "no"
  }
}

Installed Packages
# User
atom-ternjs, v0.15.0 (inactive)
editorconfig, v2.0.0 (inactive)
language-babel, v2.40.0 (inactive)
language-gradle, v0.0.3 (inactive)
language-jade, v0.7.2 (inactive)
language-pug, v0.0.19 (inactive)
linter, v1.11.18 (inactive)
linter-eslint, v8.0.0 (inactive)
linter-jsonlint, v1.3.0 (inactive)
pretty-json, v1.6.1 (inactive)
atom-dark-syntax, v0.27.0 (inactive)
atom-dark-ui, v0.52.0 (inactive)
atom-light-syntax, v0.28.0 (inactive)
atom-light-ui, v0.44.0 (inactive)
base16-tomorrow-dark-theme, v1.2.0 (inactive)
base16-tomorrow-light-theme, v1.2.0 (inactive)
one-dark-ui, v1.6.0 (inactive)
one-light-ui, v1.6.0 (inactive)
one-dark-syntax, v1.3.0 (inactive)
one-light-syntax, v1.3.0 (inactive)
solarized-dark-syntax, v1.0.2 (inactive)
solarized-light-syntax, v1.0.2 (inactive)
about, v1.7.0 (inactive)
archive-view, v0.61.1 (inactive)
autocomplete-atom-api, v0.10.0 (inactive)
autocomplete-css, v0.11.2 (inactive)
autocomplete-html, v0.7.2 (inactive)
autocomplete-plus, v2.31.1 (inactive)
autocomplete-snippets, v1.11.0 (inactive)
autoflow, v0.27.0 (inactive)
autosave, v0.23.1 (inactive)
background-tips, v0.26.1 (inactive)
bookmarks, v0.42.0 (inactive)
bracket-matcher, v0.82.1 (inactive)
command-palette, v0.38.0 (inactive)
deprecation-cop, v0.54.1 (inactive)
dev-live-reload, v0.47.0 (inactive)
encoding-selector, v0.22.0 (inactive)
exception-reporting, v0.40.0 (inactive)
find-and-replace, v0.201.1 (inactive)
fuzzy-finder, v1.4.0 (inactive)
git-diff, v1.1.0 (inactive)
go-to-line, v0.31.0 (inactive)
grammar-selector, v0.48.2 (inactive)
image-view, v0.59.0 (inactive)
incompatible-packages, v0.26.1 (inactive)
keybinding-resolver, v0.35.0 (inactive)
line-ending-selector, v0.5.0 (inactive)
link, v0.31.1 (inactive)
markdown-preview, v0.158.0 (inactive)
metrics, v1.0.0 (inactive)
notifications, v0.65.1 (inactive)
open-on-github, v1.2.0 (inactive)
package-generator, v1.0.0 (inactive)
settings-view, v0.242.2-hotfix1 (inactive)
snippets, v1.0.2 (inactive)
spell-check, v0.68.2 (inactive)
status-bar, v1.4.1 (inactive)
styleguide, v0.47.0 (inactive)
symbols-view, v0.113.1 (inactive)
tabs, v0.101.0 (inactive)
timecop, v0.33.2 (inactive)
tree-view, v0.209.3 (inactive)
update-package-dependencies, v0.10.0 (inactive)
welcome, v0.35.1 (inactive)
whitespace, v0.33.0 (inactive)
wrap-guide, v0.38.2 (inactive)
language-c, v0.52.1 (inactive)
language-clojure, v0.21.0 (inactive)
language-coffee-script, v0.47.2 (inactive)
language-csharp, v0.12.1 (inactive)
language-css, v0.37.1 (inactive)
language-gfm, v0.88.0 (inactive)
language-git, v0.15.0 (inactive)
language-go, v0.42.1 (inactive)
language-html, v0.45.1 (inactive)
language-hyperlink, v0.16.0 (inactive)
language-java, v0.23.0 (inactive)
language-javascript, v0.119.0 (inactive)
language-json, v0.18.2 (inactive)
language-less, v0.29.5 (inactive)
language-make, v0.22.2 (inactive)
language-mustache, v0.13.0 (inactive)
language-objective-c, v0.15.1 (inactive)
language-perl, v0.35.0 (inactive)
language-php, v0.37.2 (inactive)
language-property-list, v0.8.0 (inactive)
language-python, v0.45.0 (inactive)
language-ruby, v0.69.0 (inactive)
language-ruby-on-rails, v0.25.0 (inactive)
language-sass, v0.56.0 (inactive)
language-shellscript, v0.22.4 (inactive)
language-source, v0.9.0 (inactive)
language-sql, v0.23.0 (inactive)
language-text, v0.7.1 (inactive)
language-todo, v0.28.0 (inactive)
language-toml, v0.18.0 (inactive)
language-xml, v0.34.9 (inactive)
language-yaml, v0.26.0 (inactive)

# Dev
No dev packages

Hi @vovkasm, thanks for getting in touch. Could you please try to un- and reinstall the editorconfig-package?

Hi, after upgrade to 2.0.1 from Atom Setting ui, errors disappeared. Thanks!

Just in case anyone else comes here with the same error -- try updating the Atom IDE itself if you haven't done so already. That was causing the same error for me (was on 1.8).

Running Ubuntu 16.04 for some reason I had to uninstall, download from the releases page, and reinstall.


Set up project structure, Redux, navigation, and initial pages

Set up project structure, Redux, navigation, and initial pages
Description:
This pull request includes the following changes:

Set up the React project with create-react-app.
Installed necessary dependencies, including react-router-dom and axios.
Configured the Redux store by creating the store, reducers, and actions.
Created the necessary components for navigation, including the App component and the Navigation component.
Set up routing using react-router-dom, including routes for the home page and sound details page.
Created the Home page component to display the list of sounds.
Integrated the Redux store with the Home page component to fetch and display sounds.
Created the SoundDetails page component to display the details of a selected sound.
Integrated the Redux store with the SoundDetails page component to fetch and display sound details.
Refactored the SoundDetails component to use the stored sound details from the Redux store.
Updated the SoundCard component to navigate to the SoundDetails page and update the soundDetails state with the selected sound object.

Please review the changes and let me know if any further modifications are needed. Great job so far! 👏

aproved
Good job so far


Unique-usage coupon code with newSubscription when the Stripe customer also doesn't exist is invalid

So it seems that if you have a coupon code that can only be redeemed once, and you use it on a new subscription, on a Stripe customer that does not yet exist, the coupon code is sent once with the customer creation, and then once again with the subscription payload... And since the coupon is only valid once, Stripe fails to create the subscription because the coupon code has already been used, or burnt.
I think the SubscriptionBuilder's getStripeCustomer function should clear the coupon attribute after it creates the Stripe customer? (line 197)
Thanks!

I can confirm this is a real bug; results in duplicate application of the coupon (once upon creation of the customer and once on creation of the subscription).

Also confirmed and has been a problem since commit 428f24b. The problem is that when a subscription is created for a model (user) that hasn't yet been registered as a Stripe customer, the coupon is tied to both the customer AND the subscription. This may not be a problem when the Stripe coupon is meant to be used repeatedly. However, when the coupon is set to be used once, this bug results in the user receiving the coupon discount twice.
An example to reproduce the problem:
$user = BillableUser::create([ 'first' => 'Taylor', 'last' => 'Otwell']);
$user->newSubscription($subscription, $plan)->with($coupon);

I think maybe the solution is to not apply coupons that are set on the SubscriptionBuilder (via with($coupon)) to the owner entity when being registered with Stripe. Unless there are scenarios where coupons need to be applied to a user account (anyone know?), it seems like only applying them to the subscription is a more logical approach, especially since the with($coupon) method is on the SubscriptionBuilder (not a Stripe Customer object). If needed, a coupon may still be attached to a new Stripe customer by first explicitly using the Billable@createAsStripeCustomer method and passing in the coupon as one of the options. See PR#350.


[Custom] add possibility to have an expiration date to the app

Based on https://github.com/medInria/medInria-public/pull/1094
Commit: https://github.com/medInria/medInria-public/commit/4e22ca6e0cfa76de74bbac9112626e9b612f1db6
From a feature on MUSICardio, this PR adds the possibility (by default deactivated) to add an expiration time to a binary. If the binary is too old (from the compilation date), it will display a message box instead of the application.
:m:

The private plugins should handle their own expiration date (or other DRM method), not the core, because one can simply recompile the core and copy the private plugins into it).


Improve developer-facing evaluations API

Fixes # (issue)

Overall LGTM - could you update docs quick?
I also did a quick scan and didn't see smith/index.ts or runner_utils.ts imported anywhere else but would be good to triple check just in case.

Thank you!