new(builder): added an archlinux builder.

What type of PR is this?
/kind feature

Any specific area of the project related to this PR?
/area pkg
What this PR does / why we need it:
It can be useful to quickly test newest kernel releases.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
new(builder): added an archlinux builder.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: FedeDP
To complete the pull request process, please assign leodido after the PR has been reviewed.
You can assign the PR to them by writing /assign @leodido in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 19f291dd763d13ad53890d9bb494cbc9f4ff9705

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: dwindsor, FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [dwindsor]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: dwindsor, FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [dwindsor]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Page Up/Page Down binds (default behaviour) removed by LS: Glass

These bindings allow for jumping around in the chat and LS: Glass
is making them not work.
I use them a lot and got bummed as I really enjoyed the aestetics of your addon.

Huh? I didn't even know about these. I'll look into it later this week, thanks for bringing it up!


Installation error "Failed to create symlink"

Issue Summary
On Windows when running yarn run init from a newly cloned instance of Ghost the command fails with the message Failed to create symlink
Steps to Reproduce

git clone git@github.com:TryGhost/Ghost.git ghost
cd ghost
yarn run init

Resulting output:
yarn run v0.24.5
$ yarn global add knex-migrator ember-cli grunt-cli && yarn install && grunt symlink && grunt init || true
yarn global v0.24.5
warning No license field
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Installed<EMAIL_ADDRESS>with binaries:
      - knex-migrator
      - knex-migrator-init
      - knex-migrator-health
      - knex-migrator-migrate
      - knex-migrator-reset
success Installed<EMAIL_ADDRESS>with binaries:
      - ember
      - 🐹
success Installed<EMAIL_ADDRESS>with binaries:
      - grunt
warning No license field
Done in 7.10s.
yarn install v0.24.5
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
Done in 84.78s.
Running "symlink:githooks" (symlink) task
>> Error: EPERM: operation not permitted, symlink '..\..\.github\hooks\pre-commit' -> 'C:\Users\seanfuture\Home\Canvas\Platform\ghost\.git\hooks\pre-commit'
Warning: Failed to create symlink: (file) .git/hooks/pre-commit -> ..\..\.github\hooks\pre-commit. Use --force to continue.

Aborted due to warnings.
'true' is not recognized as an internal or external command,
operable program or batch file.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Technical details:

Ghost Version:  master / a61e6e7cc2e0bee11c69aab64fee9d375959eb3e
Node Version: v7.10.0
Browser/OS: Chrome Version 58.0.3029.110 (64-bit) .. Windows 10 v1607 Build 14393.1198
Database: sqlite3

Hey @seanfuture 👋

EPERM: operation not permitted

You don't have enough permissions to create the symlink.
Try and open the terminal as admin.
If you need any help, come say hello on our slack channel.
We use github solely for bug and issue tracking. I'm going to close this issue.
Thanks 👋

e use github solely for bug and issue tr

谢谢，解决了我的问题


Package request: Monsterwm

"tiny but monstrous tiling window manager" - c00kiemon5ter
Small bar-less X11 window manager.

homepage URL:
source URL: https://github.com/c00kiemon5ter/monsterwm/
license: MIT/X Consortium License
platforms: unix, linux

Are you sure we should add this? It hasn't had a commit in 12+ years.
Might it be a package for your personal config?


Fix openOrder and completedOrder

Fix for https://github.com/stoqey/ib/issues/34
Not tested at my side, it was just a good guess as follow up on the decoder issue from yesterday.
@Tsopic can't add you to reviewer list. I will wait with merge for your approval / confirmation that it works now.

I'm not sure how to consume this package outside npm/yarn.
Any way I could use this branch as a package directly from package repo?

I'm not sure how to consume this package outside npm/yarn.
Any way I could use this branch as a package directly from package repo?
@mfrener

You can update it manually:
Do "npm run build" on root folder of this package. It will create /dist folder containing the transplanted .js files.
Than find the node_modules/@stoqey/ib folder on your App project and replace node_modules@stoqey\ib\dist copy with the /dist from above.

Wasn't able to get it working just yet. Sent the errors in slack

Closed this PR as it will be part of overhaul branch.
We will collect changes there first to avoid too much noise on the master.


Pattern: Content group - horizontal template changes Prod QA testing

User Story

As a [user role below]:
developer using the ibm.com Library Content group - horizontal

I need to:
have a version of the pattern or component that has been tested for accessibility compliance as well as on multiple browsers and platforms

so that I can:
be confident that my ibm.com web site users will have a good experience

Additional information

Browser Stack link
Browser Standard
Browser versions to be tested:  Tier 1 browsers will be tested with defects created as Sev 1 or Sev 2.  Tier 2 browser defects will be created as Sev 3 defects.
Platforms to be tested, by priority:  1)  Desktop  2)  Mobile  3)  Tablet
Mobile & Tablet iOS versions: 13.1 and 13.3
Mobile & Tablet Android versions: 9.0 Pie and 8.1 Oreo
Browsers to be tested:  Desktop: Chrome, Firefox, Safari, Edge, Mobile: Chrome, Safari, Samsung Internet, UC Browser, Tablet: Safari, Chrome, Android
Accessibility Checklist
Creating a QA bug
See the Epic for the Design and Functional specs information
Dev issue (#2816)

Acceptance criteria

[ ] Accessibility testing is complete.  Pattern is compliant.
[ ] All browser versions are tested
[ ] All operating systems are tested
[ ] All devices are tested
[ ] Defects are recorded and retested when fixed

@Praveen-sr @chetankan The code has been merged and is ready for testing.
Deploy preview created for package React:
https://ibmdotcom-react.s3.us-south.cloud-object-storage.appdomain.cloud/deploy-previews/2852/index.html
Built with commit: 15acf6ca281e8e7145a51e2477cd45318ae3eb51

7/6/2020  The above URL is not correct.  Praveen and Chetan will use the canary URL for testing.  Moving to sprint 20-14.

All testing is finished.


Flesh out rules from Node.js and CommonJS

Need strong opinions on http://eslint.org/docs/rules/#nodejs-and-commonjs

callback-return: error
global-require: error (some loaders have issue with conditional requires)
handle-callback-err: error
no-new-require: error
no-path-concat: error
no-process-env: error (use a config loader)
no-process-exit: error (throw errors and handle them)
no-sync: error
sorry, no strong opinions here
no-mixed-requires: why? also, most everything should be es6, which has a different syntax anyway
no-restricted-modules: i can see the reasoning, but if the developer is making an OS specific app (for instance), thats up to them
if you can't tell, my general methodology here is to error and add inline exceptions when needed.

Currently the on.js file has everything turned off. If you want to make a PR, we can discuss it there. <3


Support ":authority" header for Camunda Cloud 1.1

Camunda Cloud 1.1 changes the way that DNS works for Camunda Cloud SaaS clusters.
There are not enough DNS addresses to go around, so we're going to use a single address per region, and route requests from the load-balancing proxy based on the ":authority" pseudo-header.
The Zeebe Gateway URL will point to a single controller for each region - for the current Belgium region it is bru-2.operate.camunda.io. The :authority header should be set to ${clusterId}.zeebe.camunda.io.

At the moment, for a Camunda Cloud connection, we require these four to be set:
export ZEEBE_ADDRESS='3b640f45-0dcd-469c-8551-7f68a5d4f54b.zeebe.camunda.io:443'
export ZEEBE_CLIENT_ID='...'
export ZEEBE_CLIENT_SECRET='...'
export ZEEBE_AUTHORIZATION_SERVER_URL='https://login.cloud.camunda.io/oauth/token'


⚠ Bofrost.be has degraded performance

In ec81ad2, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1082 ms

Resolved: Bofrost.be performance has improved in 26d910f after 6 minutes.


Update httplug and php-http/client-common dependencies

Change Summary
This pull request just updates a couple of seemingly conflicting dependencies which were preventing the package from being installed (see #12).
However, I haven't actually had a chance to test if the updates break anything in the package! All I know is that this solves the installation problem. Before merging this, the maintainers should see if this causes any issues for the package.
PR Checklist

[x] I have read and signed the Contributor License Agreement.

Thanks @karptonite!

Thanks @karptonite!


Spevacus: Watch +1<PHONE_NUMBER>

Spevacus requests the watch of the watch_number +1<PHONE_NUMBER>. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Approved by Mast in Charcoal HQ


Improve Shift + Click behavior

Behaviors should be clarified:

Ctrl+Click: Add/Remove selection
Shift+Click: Expand selection FROM intial pivot
Ctrl+Shift+Click: Expand selection from LATEST pivot

To achive this, selections should change from [min, max] to [p1, p2] to remember initial pivot point.

Plus, in MacOS, ctrl~cmd modifier key combination is pretty inconsistent, more like just confusing. Need to be improved.


Prevent experimental features from being set by default setting multimodelserver flags to false

What this PR does / why we need it: By default the flags in inferenceservice.yaml for SKLearn, XGBoost, LightGMB, and Triton have been set to true which means MMS is enabled without users knowing. We want to prevent this from happening.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:

Using MMS requires flags to be set in inferenceservice.yaml

/assign @yuzisun @yuzliu

/LGTM

@abchoo what happens when user submits trained model when the flag is off?

@abchoo Can you help regenerate the 0.5 release yaml by running hack/generate-install.sh v0.5.0 ?

@abchoo Can you help regenerate the 0.5 release yaml by running hack/generate-install.sh v0.5.0 ?

@yuzisun  Should we cut release after the validation webhook is in?

/ok-to-test

/retest

/retest

Thanks @abchoo!
/lgtm
/approve


ehancement(e2e): Run E2e with build tags

Description
This PR ensures that e2e(s) are run with build tags and no longer runs with unit tests
What type of PR is this? (check all applicable)

[ ] 🍕 Feature
[ ] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[x] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

A successful unit test execution without e2e can be seen here - https://github.com/cloudoperators/greenhouse/actions/runs/11114597574/job/30881363362?pr=613


Native Notebooks: Can't figure out how to start kernel

Environment data

VS Code version:  1.57.1
Jupyter Extension version (available under the Extensions sidebar): v2021.6.999662501
Python Extension version (available under the Extensions sidebar): v2021.6.944021595
OS (Windows | Mac | Linux distro) and version: 11.4
Python and/or Anaconda version: n/a
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): n/a
Jupyter server running: Local

Turned on experiment with:
    "workbench.editorAssociations": {
        "*.ipynb": "jupyter-notebook"
    },
    "jupyter.experiments.optInto": [
        "__NativeNotebookEditor__"
    ],

Expected behaviour
I opened up a new blank native notebook, but can't seem to get a kernel running.
Actual behaviour

Steps to reproduce:
Logs
Log doesn't change through this process.

The kernel picker is empty, which suggests that we failed to register any Jupyter kernels with VS Code. Do you happen to have Python interpreters and/or kernels installed locally?

Many. The other oddity is that the kernel selection button wasn't appearing in the top right.
Unfortunately, about an hour later I realized everything was working again -- the kernel selection button had returned, and that list is populated. The only thing that I think I did in the interim was play around with the Cell Toolbar setting, but... I've tried to put stuff back to where it was before I did anything, and I can't get the bug to return. So... this may be one of those intermittent problems I don't know how to recreate. Sorry!

@nickeubank, sorry for the trouble. Please reopen if you run into this again.


Update to a more recent version of ruby

After install ruby 2.3.1(used in release v 2.0.1) with rvm I get the following warning:
Install of ruby-2.3.1 - #complete
Please be aware that you just installed a ruby that requires 2 patches just to be compiled on an up to date linux system.
This may have known and unaccounted for security vulnerabilities.
Please consider upgrading to ruby-2.4.2 which will have all of the latest security patches.

#37 brought ruby 2.5 support, I need to try that.

I tested dev branch with ruby 2.5.1, install works well.

No issues heard after release.  Closing.


Manually set the padding between legendTitle and legendCells

Hi,
I wanted to reduce the space between the title and the cells but I didn't find the option.

I found here the transform of the cells.
The fix is simple but not very pretty. Do you have an option to do it?
// For exemple, a padding of 7px
svg.select('.legendCells').attr('transform', 'translate(0, 7)')

Thanks

This actually follows the post-modification pattern in all the D3 generators. You'd need to do the same thing to modify elements created by brush, axis or the like.

Ok, I'll go this way so.
Thanks


Refuse nonsense component attribute combinations

Thanks for this awesome project!
This is not a priority, of course, but it would be pretty cool: Would it be viable to throw errors (or at least warnings) when components contain "conflicting" attributes? Super basic example: <sui-button primary secondary>Click me for nonsense</sui-button>
Thanks in advance!

Agree on that

That would be amazing, feel free to submit a PR


0.5 hours device timer fails

Describe the bug
Most likely similar issue to timer had, must've missed this one when casting from init to float caused an issue further down the line.

Although this worked fine when first changed, later on it half hour timer working. Need to revisit.

Although this worked fine when first changed, later on it half hour timer working. Need to revisit.

Sorted this one now I believe.

Sorted this one now I believe.


V0.0.3.post2

V0.0.4 features merge early in post2 for stability
Notably:

Redshift driver
Frontend thresholds
Better reporting

Redshift integration should be added to master, but this is no longer correct and merge-able

Handled in v0.1.0-alpha release


docs(readme): fix configuration section

Closes https://github.com/hermit-os/uhyve/issues/837.
This was introduced in https://github.com/hermit-os/uhyve/commit/0384c1d050057035d892e2b52f825a4be4bc73a7.

:+1:


[Heads Up] SwiftLint may soon support remote configurations, which won't work out of the box here

I noticed this PR in the SwiftLint repo, which adds support for parent, child, and remote configurations.
I'm experimenting with it here and noticed that a "stock" configuration of the plugin won't work if you have a remote configuration. The reason is the same as why nested configurations don't work, as per this issue.
To be specific, this config file
# .swiftlint.yml
parent_config: https://raw.githubusercontent.com/Automattic/swiftlint-config/6e2333f88294a03e4e72d287367e1fd62000b049/.swiftlint.yml
remote_timeout: 10.0

will result in this output by the plugin.
# Output of `danger pr`, with `switlint.verbose = true`
Using config file: .swiftlint.yml
Swiftlint will be run from /Users/gio/Developer/a8c/WordPress-iOS-Shared
Swiftlint will exclude the following paths: []
Swiftlint includes the following paths: []
linting with options: {:config=>".swiftlint.yml", :reporter=>"json", :quiet=>true, :pwd=>"/Users/gio/Developer/a8c/WordPress-iOS-Shared", :force_exclude=>true}
Swiftlint will lint the following files:
Received from Swiftlint: {}

The workaround is the same as for the nested configuration, use the all_files flag.
I've been able to use it successfully here, with this Dangerfile
require 'git_diff_parser'

# The plugin looks into the .swiftlint.yml config to know in which folders to
# look for files to lint. Our config only has the URL of the remote config,
# though, so no file to lint would be found. This option makes the plugin lint
# all the files, and is "the same as [if] you were running `swiftlint` on the
# root folder".
# See
# https://github.com/ashfurrow/danger-ruby-swiftlint/tree/a8d6b3a6e82994f500411ad7acc2039d2d7409c7#usage
swiftlint.lint_all_files = true

# Despite using we want inline comments only in the files that changed in the
# PR, instead of a long wall of text with each of the files in the repo failing
# to lint. This extra code makes it possible.
# See
# https://github.com/ashfurrow/danger-ruby-swiftlint/tree/a8d6b3a6e82994f500411ad7acc2039d2d7409c7#usage
diff = GitDiffParser::Patches.parse(github.pr_diff)
dir = "#{Dir.pwd}/"
swiftlint.lint_files(inline_mode: true) { |violation|
  diff_filename = violation['file'].gsub(dir, '')
  file_patch = diff.find_patch_by_file(diff_filename)
  file_patch != nil && file_patch.changed_lines.any? { |line| line.number == violation['line']}
}

I don't think any action is required right now, but just wanted to give the team a heads up. 👌
Maybe when the SwiftLint feature ships a README update could help. In the meantime, this issue should do.

@mokagio Huge props for opening this issue up 👏 No doubt it will help others. Agreed about next steps and waiting for the readme update. Hope you're well!


swift pt命令报错，把缓存的数据集全删了重新下载 还是报错

Describe the bug
Downloading data: 238MB [00:04, 50.7MB/s]
[INFO:modelscope] storing https://www.modelscope.cn/api/v1/datasets/swift/chinese-c4/repo?Source=SDK&Revision=master&FilePath=data%2Fchinese-c4-0095-of-0096.jsonl.zst in cache at /home/apus/.cache/modelscope/hub/datasets/downloads/6a7c2b63616521fb647938b845e8dcd292ffb01342f2c58f869214a6a47289fe
[INFO:modelscope] creating metadata file for /home/apus/.cache/modelscope/hub/datasets/downloads/6a7c2b63616521fb647938b845e8dcd292ffb01342f2c58f869214a6a47289fe
Generating train split: 0 examples [00:00, ? examples/s]
Generating train split: 19255347 examples [03:14, 97585.27 examples/s]
Generating train split: 19271505 examples [03:14, 96790.75 examples/s]
Generating train split: 19273007 examples [03:14, 99111.74 examples/s]
[INFO:modelscope] Context manager of ms-dataset exited.
Using the latest cached version of the dataset since swift/chinese-c4 couldn't be found on the Hugging Face Hub
[INFO:modelscope] Context manager of ms-dataset exited.
[ERROR:swift] Dataset swift/chinese-c4 load failed: subset_name=default,split=train with error: Couldn't find cache for swift/chinese-c4 for config 'default'
Available configs in the cache: ['default-1fc53a3c66964980']
[rank5]: Traceback (most recent call last):
[rank5]:   File "/data/zengzijian/Projects/LLaMA-Factory-202407/swift/swift/cli/sft.py", line 5, in
[rank5]:     sft_main()
[rank5]:   File "/data/zengzijian/Projects/LLaMA-Factory-202407/swift/swift/utils/run_utils.py", line 27, in x_main
[rank5]:     result = llm_x(args, **kwargs)
[rank5]:   File "/data/zengzijian/Projects/LLaMA-Factory-202407/swift/swift/llm/sft.py", line 258, in llm_sft
[rank5]:     train_dataset, val_dataset = _get_train_val_dataset(args)
[rank5]:   File "/data/zengzijian/Projects/LLaMA-Factory-202407/swift/swift/llm/sft.py", line 30, in _get_train_val_dataset
[rank5]:     train_dataset, val_dataset = get_dataset(
[rank5]:   File "/data/zengzijian/Projects/LLaMA-Factory-202407/swift/swift/llm/utils/dataset.py", line 2488, in get_dataset
[rank5]:     dataset = get_function(
[rank5]:   File "/data/zengzijian/Projects/LLaMA-Factory-202407/swift/swift/llm/utils/dataset.py", line 429, in get_dataset_from_repo
[rank5]:     dataset = load_ms_dataset(dataset_id, subset_split_list, use_hf)
[rank5]:   File "/data/zengzijian/Projects/LLaMA-Factory-202407/swift/swift/llm/utils/dataset.py", line 353, in load_ms_dataset
[rank5]:     return concatenate_datasets(dataset_list)
[rank5]:   File "/home/apus/mambaforge/envs/etuning4/lib/python3.10/site-packages/datasets/combine.py", line 188, in concatenate_datasets
[rank5]:     raise ValueError("Unable to concatenate an empty list of datasets.")
[rank5]: ValueError: Unable to concatenate an empty list of datasets.
Using the latest cached version of the dataset since swift/chinese-c4 couldn't be found on the Hugging Face Hub
[INFO:modelscope] Context manager of ms-dataset exited.
[ERROR:swift] Dataset swift/chinese-c4 load failed: subset_name=default,split=train with error: Couldn't find cache for swift/chinese-c4 for config 'default'
Available configs in the cache: ['default-1fc53a3c66964980']
[rank1]: Traceback (most recent call last):
[rank1]:   File "/data/zengzijian/Projects/LLaMA-Factory-202407/swift/swift/cli/sft.py", line 5, in
[rank1]:     sft_main()
[rank1]:   File "/data/zengzijian/Projects/LLaMA-Factory-202407/swift/swift/utils/run_utils.py", line 27, in x_main
[rank1]:     result = llm_x(args, **kwargs)
[rank1]:   File "/data/zengzijian/Projects/LLaMA-Factory-202407/swift/swift/llm/sft.py", line 258, in llm_sft
[rank1]:     train_dataset, val_dataset = _get_train_val_dataset(args)
[rank1]:   File "/data/zengzijian/Projects/LLaMA-Factory-202407/swift/swift/llm/sft.py", line 30, in _get_train_val_dataset
[rank1]:     train_dataset, val_dataset = get_dataset(
[rank1]:   File "/data/zengzijian/Projects/LLaMA-Factory-202407/swift/swift/llm/utils/dataset.py", line 2488, in get_dataset
[rank1]:     dataset = get_function(
[rank1]:   File "/data/zengzijian/Projects/LLaMA-Factory-202407/swift/swift/llm/utils/dataset.py", line 429, in get_dataset_from_repo
[rank1]:     dataset = load_ms_dataset(dataset_id, subset_split_list, use_hf)
[rank1]:   File "/data/zengzijian/Projects/LLaMA-Factory-202407/swift/swift/llm/utils/dataset.py", line 353, in load_ms_dataset
[rank1]:     return concatenate_datasets(dataset_list)
[rank1]:   File "/home/apus/mambaforge/envs/etuning4/lib/python3.10/site-packages/datasets/combine.py", line 188, in concatenate_datasets
[rank1]:     raise ValueError("Unable to concatenate an empty list of datasets.")
[rank1]: ValueError: Unable to concatenate an empty list of datasets.
Using the latest cached version of the dataset since swift/chinese-c4 couldn't be found on the Hugging Face Hub
[INFO:modelscope] Context manager of ms-dataset exited.
[ERROR:swift] Dataset swift/chinese-c4 load failed: subset_name=default,split=train with error: Couldn't find cache for swift/chinese-c4 for config 'default'
Available configs in the cache: ['default-1fc53a3c66964980']
What the bug is, and how to reproduce, better with screenshots(描述bug以及复现过程，最好有截图)
Your hardware and system info
Write your system info like CUDA version/system/GPU/torch version here(在这里给出硬件信息和系统信息，如CUDA版本，系统，GPU型号和torch版本等)
Additional context
Add any other context about the problem here(在这里补充其他信息)

哈咯，拉取一下modelscope的main分支进行实验试试呢


DRACOLoader: Property 'Worker' doesn't exist

I am using threejs, @react-three/fiber, @react-three/drei on react native.
Trying to load compressed gltf model but getting Reference Error: Property 'Worker' doesn't exist error.
Here is the related code:
import React from 'react';
import { useGLTF } from '@react-three/drei/native';

function A1() {
  const { scene } = useGLTF(require("./assets/a1_compressed.glb"));
  return <primitive object={scene} />
}

export default function Model(props) {
  return (
    <group>
      <A1 />
    </group>
  );
}

There are the dependencies:
  "dependencies": {
    "@react-three/drei": "^9.99.7",
    "@react-three/fiber": "^8.15.19",
    "expo": "^50.0.8",
    "expo-gl": "~13.6.0",
    "react": "18.2.0",
    "react-native": "0.73.5",
    "react-native-url-polyfill": "^2.0.0",
    "three": "^0.162.0"
  },

DRACO can't be used with react-native, as it relies on both workers but importantly WASM/JIT. You'd need to implement http://github.com/google/draco over JSI and write the loader to interface with it. This is not something this library can support. I would suggest forgoing DRACO or meshopt on native, and/or rewriting the latter's encoders in JS or over JSI.


fix: lsp completion docs missing property detail

The LSP completion docs are currently missing the property detail docs.
First screenshot shows the current experience. It is missing the information on what type the completion item is.

This second screenshot shows after applying the fix in this PR. You can see the detail displayed.

So, the funny thing is that the only thing the override does, is hide the detail :)
For Lua for example, the detail is not useful.
Simply disable the cmp override to keep the detail. The rendering etc will still be Noice, due to the otheroverrides.

So, the funny thing is that the only thing the override does, is hide the detail :)
For Lua for example, the detail is not useful.

ahh makes sense!


Android Basics: LiveData

URL of codelab
https://developer.android.com/codelabs/basic-android-kotlin-training-livedata?continue=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-kotlin-unit-3-pathway-3%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-training-livedata#6
In which task and step of the codelab can this issue be found?
4
Describe the problem
inflation from DataBindingUtil didn't work
Steps to reproduce?

Go to...
Click on...
See error...

Versions
Android Studio version:   4.1.2
API version of the emulator: 30
Additional information
Include screenshots if they would be useful in clarifying the problem.

My fault

My fault


Update view.go

Refactor view helper functions to improve code readability and maintainability

Introduced a generic getContextValue helper function to reduce redundancy in context value retrieval.
Enhanced documentation and comments for better understanding and maintainability.
Simplified error handling with default values in context retrieval.

@Mclawrenceco Thank you. Really liked the context helper.


Fix an export name check exception

we are thinking about using an extra length field to store the length of a string, in our case an unicode string.


Evaluate applicability to Servo/Gecko

Hello everyone! We've talked historically about a Cargo subcommand to help work on edits to dependencies locally, and this repository contains a subcommand which I hope will ease this work flow. I wrote a usage example in the README. The usage basically looks like:

Work on a Rust project, realize you need to work on the log dependency.
cargo install cargo-edit-locally
cargo edit-locally log
Copy output into Cargo.toml for [replace]
Edit log/src/lib.rs
Push changes/PRs to the log repo
Delete [replace] and log folder

I wanted to cc a few folks and get a wider audience for this as well. I'm curious if this would be helpful for developmentin Servo/Gecko or if it's completely missing the mark entirely! This represents what I recall our conversations were, but please let me know if I'm misremembering! I'd love any feedback in terms of usability, improvements to make, etc.
cc @SimonSapin, @metajack, @nox, @jdm, @larsbergstrom, @bholley

Also cc @luser, @froydnj, @hsivonen, you may be quite interested in this crate for working with Gecko! (the OP of the issue has more information, along with the README in this repo)

Nice! Does this work with vendored crates, allowing the user to edit the vendored source directly rather than making another copy?

This does work with vendored crates, yeah (or at least it's intended to, not tested yet). It'd make a fresh copy elsewhere for tweaking as Cargo doesn't allow modification of vendored crates. The intention of this command though is to automate the process of tweaking vendored crates and make it as easy as possible.

It'd make a fresh copy elsewhere for tweaking as Cargo doesn't allow modification of vendored crates.

Why can't it just allow modifying the vendored crates directly? That's what we do right now, it's just very annoying to come up with the right [replace] syntax and do all the cargo updating.

i.e. I would like to automate the creation of patches like https://gist.github.com/bholley/85dc2277aaa732bce04cc9e672915595

Modifying the in-tree source is nice because it means I don't need to add a whole bunch of new files to the repository just to push to try.

In general I think that strategy unfortunately won't work. I ran into this problem when testing this subcommand. When using [replace] Cargo will follow path dependencies of the crate that you point to. Typically vendored crates do not have those path dependencies in place.
The other intention of this subcommand was to encourage easily upstreaming work on local crates, e.g. by having a git repo in place and ready to go to track work, send a PR, etc. Additionally by checking crates out from the actual source we can ensure that path dependencies all match up as the git repo is likely structured for itself to build correctly.

I'm currently primarily interested in these two use cases:

Edit a vendored crate in my local working directory for mozilla-central to add println! debugging or to change something a bit to see if it makes a bug go away. This should be possible with minimal ceremony. Ideally, one mach command that names the crate I want to edit would unlock it from checksum checks while letting its existing dependencies and dependents continue working. The sources should stay in their current directory location to make git diff show what I actually edited. It should also be possible to push the edited state to the try server. (I'd be OK with the editing being detectable in such a way that a commit hook on mozilla-inbound / central / autoland could block pushing edits like this to the real product repo.)

Edit a vendored crate as in the above case, but instead of pushing to try, allowing the result to be pushed to ESR, beta or release repos as a targeted fix without having to reflect the old-version-with-fix state on crates.io. Let's say ESR has crate foo version 0.4.2 and mozilla-central has 0.6.1. There's a security bug in 0.6.1, and a fixed 0.6.2 is released on crates.io, but the upsteam looks ahead, not back, and doesn't publish the same security fix as 0.4.3 on crates.io.  I wouldn't want to have to maintain old compatibility series of a crate I develop on crates.io for the life of Debian stable or RHEL.) Upgrading to the 0.6.x series on ESR would have massive impact on the dependency graph. We should be able to decouple the ESR copy of the crate from crates.io and apply the security fix. This should be possible with minimal ceremony and should happen in place in the directory structure to see what changed using version control tools.

When using [replace] Cargo will follow path dependencies of the crate that you point to. Typically vendored crates do not have those path dependencies in place.

It seems that [replace] wouldn't address my use cases, then. Replacing the checksum file with a non-checksum marker that opts the crate out of checksumming and participation in crates.io sync would.

@bholley @hsivonen hm so maybe it'd help to help clarify and/or ask questions about vendoring first. Sounds like there's definitely a few ways to improve this command as-is, but I figure we should explore the motivations first.
In general the vendoring support in Cargo is designed to very much discourage modifying vendored sources. The motivations behind that are because in general modifying a vendored source is, by definition, making it not a vendored source at that point (but instead a patched source). This means that the lock file for a crate must change to reflect that it's a modified version of a crate, not an exact copy. The [replace] feature is intended to express this ability by encoding "this version with patches is being used".
Additionally this command is designed (or at least so I've thought) to compound on that by encouraging upstreaming any local changes. In that sense it checks out a git repository so you can track modifications over time or to test with on CI.
Do you disagree with these motivations? If so is there perhaps a middle ground you can think of which is both easy to use for you but also upholds to the conventions of the existing features in Cargo (e.g vendoring and [replace])?
@bholley can you expand on the downside of "add a whole bunch of new files to the repository just to push to try"? I am not familiar with Gecko's development model so this is unfortunately just jargon to me. If I were to attempt to understand this in git terms I'd see it as pushing a local branch to a remote location, which to me is a very cheap operation without downsides, but I may be missing something underlying in Gecko's process.
@hsivonen do you believe your first case is not satisfied by a subcommand such as this? The intention is that this is the "one command" you execute to get everything locally to start modifying sources. Right now it doesn't auto-modify Cargo.toml/Cargo.lock but I think I've figured out a way to do that and can implement it. Diffs should be possible as it's checked out to a local git repo, but is that not sufficient? Could you expand on the constraints of what it means to push to a try server?
Your second case is also interesting, but I don't think directly related to this subcommand. I'll expand here on my thoughts but it may be best to continue this conversation elsewhere perhaps. There's a few situations I could imagine this being in.

First, Gecko could directly depend on the crate in question. At that point I think you'd just fork it, make the changes necessary, and then depend on the fork. The vendored version would then come in tree through the typical channels.
Next the dependency could be somewhere deep inside the dependency graph. In this case I think you'd do the same process of forking and making changes, and then the difference would be to use [replace] to depend on the fork. You'd probably vendor the source for the crate itself and use a path dependency in this case.

@bholley can you expand on the downside of "add a whole bunch of new files to the repository just to push to try"?

Let me try to provide a hypothetical example of why the cargo restrictions are annoying.
Suppose we have some test that fails intermittently in automation, and I'm supposed to debug it. I'm not intimately familiar with all the code involved, because nobody is. But I trace through what happens and add some logging in various places, so that I can push it to try, retrigger it 50 times, and hopefully get something interesting. I add throwaway logging in Gecko C++ code, in Firefox JS code, in devtools code, in the test harness, in the webdriver implementation, in the taskcluster glue, in NSS, and in a vendored rust crate.
All of those are different projects with different owners, conventions, approval processes, build systems, and canonical repos. But the joy of monorepos is that the code is all in-tree, and so I can grep for it, find the pieces I'm interested in, and add logging or experimentation without understanding the intricacies of how each one is developed and tied into the final product. I certainly couldn't push my patch to mozilla-central, but I can run it locally and push it to try just fine in all the cases.
Except not quite all the cases, because in the case of the Rust crate the build system will fail and waggle its finger at me, telling me that the code is there in my tree but that I'm not supposed to be changing it because then I might not upstream what I'm doing. In this case my first reaction would be to curse at this cargo thing, whatever it is, and go and try to update the checksum it's choking on to match my modifications, only to find that further checksums fail, and that I've wasted even more time.
Now, if the build system helpfully says "hey, sorry about the bother - if you want to just experiment with stuff, run this command to remove the restriction", I can live with that. But if that command then adds another repo somewhere, then I need to find where in the source tree it decided to put that repo (topsrcdir? third_party/rust? toolkit/library/rust?), and then scratch my head over whether I'm supposed to commit the files in this inner git repository to my outer git repository and whether that will break git somehow, and then I have to trust that the new copy will actually be the one that's compiled and executed rather than the other copy that's still in my tree, whereas if I could just modify the existing copy I could verify with grep that I was modifying the only function of that name in the tree.
Somebody who's deeply familiar with the whole Gecko-cargo integration story obviously will have a much easier time with this. But the point is that we should try hard to make the obvious thing work, because mozilla-central is enormous and we want to empower people to make educated guesses about things to get things done.

And this isn't hypothetical. Julian Seward (the author of valgrind) has been kind enough to look at allocation performance in Stylo, but ran into trouble just a few days ago trying to hack up measurement changes in Rayon [1]. I then had to point him to all the threads discussing workarounds, but all in all it wasted a minimum of an hour of his time.
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1291355#c26

@bholley sorry I definitely don't mean to give the impression that I think things aren't annoying or the system's perfect today, I realize and very much acknowledge there's downsides. What I'm trying to do is thread the needle here. Gecko is using Cargo which is a tool not just for Gecko but the entire Rust ecosystem. That means that the development of Cargo is not beholden to the whims of any one project. If Cargo were built exclusively for Gecko it would obviously look much dfferent. As a result that just means that features of Cargo need to be weighed against the Rust community as a whole.
Consequently we've reached a situation where "cargo will wag its finger at you", but this decision was reached with the understanding that there still exists an easy way to perform modifications to vendored source code. What I was hoping to do with this repository's subcommand is to develop this and have it suitable for use (or suitable to model after) in Gecko. The purpose of this issue was to collect constraints and understand use cases.
I think it's very much possible to support the use cases you're thinking of. It sounds like your constraints are:

Exactly one command needs to be issued to do everything
Such command should print out exactly how to modify the vendored sources
There should be a way to track modifications to the vendored sources

I think (1) and (2) are quite plausible. This repo doesn't do that today, but I think it's not super hard to do so, I'd just like to confirm first. For (3) I'm not really sure the best way do to do this. Do you have a recommendation? Of course commiting a repo in a repo will not work, but again this was proof of concept.

I may not fully understand [1]. The patch I linked to works. Is there a fundamental constraint that prevents Cargo from generating that patch?
[1] https://github.com/alexcrichton/cargo-edit-locally/issues/1#issuecomment-298962396

If the issue is just not knowing where the vendored sources are, we can certainly tell cargo that. But doesn't cargo know that anyway, since it builds from those sources?

It sounds like your constraints are

I think one that is missing is that we'd like there to be only one place the code is. It seems completely silly to have the code right there but create a second copy for philosophical reasons which benefit no one in this use case.
This limitation means that instead of protecting people from local modifications that won't be upstreamed, it will just discourage any modifications which is probably worse.
I think the fundament problem is that Cargo is trying to enforce policy that is not build-time policy, but commit-time policy, which is out of its scope.

In general the vendoring support in Cargo is designed to very much discourage modifying vendored sources. The motivations behind that are because in general modifying a vendored source is, by definition, making it not a vendored source at that point (but instead a patched source).

I think that 1. during development and 2. when applying uplifted fixes to an old branch of the larger product (ESR, release, beta in the Firefox case) that contains vendored crates, as a practical matter, transitions from "vendored source" to "patched source" need to happen. If the transition isn't absolutely trivial to make happen, it feels like the tool isn't working for the users of the tool but the users are working for the tool, which is bad for productivity.

Do you disagree with these motivations?

Yes.
While I agree that it's good to encourage the development repo of record (mozilla-central in the Firefox case) staying in sync with crates.io and to encourage upstreaming, I very much disagree with enforcing (i.e. requiring enough ceremony to waive the restriction so as to in practice enforce) this to the point that it's impractical for crates whose source has been copied to the repo of the larger project that uses them to be edited in place either for local testing or for unsynced-with crates.io branch patching.
Software from crates.io comes, licensing-wise, with all the four freedoms. I think it should be practical to exercise all four. To the extent that accidental exercise of Freedom 1 (local modifications) and Freedom 3 (shipping modifications) is known to cause problems, it's fine for a tool like Cargo to help its user not to make local modifications or ship modifications accidentally, but I think the user of the tool should be in control and it should be easy to unlock the exercise of Freedom 1 and Freedom 3. (As easy as running a single command to say that I want to unlock crate foo and not being de facto punished for doing so by a cascade of required Cargo.toml/Cargo.lock edits.)

If so is there perhaps a middle ground you can think of which is both easy to use for you but also upholds to the conventions of the existing features in Cargo (e.g vendoring and [replace])?

So far, both my brief experience with [replace] in the context of mozilla-central and your earlier comment in this thread indicate that [replace] has too many consequences to be practical.
Here's a solution that would address my concern (names subject to bikeshedding, of course):

Add a cargo subcommand allow-modification that takes the name of a vendored crate and adds a marker file .cargo-locally-patched file to the directory of the crate.
When cargo builds the project, ignore checksums in .cargo-checksum.json if there's a .cargo-locally-patched file next to it.
When updating crates from crates.io (or remote source more generally), refuse to overwrite crates that have .cargo-locally-patched unless some kind of "I really mean it" flag like --force is provided.
Make crates.io reject packages that contain a file named .cargo-locally-patched.
Bonus: Add a cargo subcommand list-modifications that iterates over crates that have the .cargo-locally-patched marked file, computes the checksums for all the files in the crate and prints out files whose checksum has changed or that have been added or deleted relative to the list in .cargo-checksum.json.

What's good about this:

The way cargo traverses the dependency graph and the directory tree would be unchanged (except for the checksum waiver), so there wouldn't be cascading consequences of having to edit Cargo.toml/Cargo.lock files.
You still can't edit vendored crates by accident. You need to show intent, but showing intent is trivial.
A command like find . | grep cargo-locally-patched easily shows what crates have been decoupled from their crates.io source of truth.
The files don't move, so the history of the monorepo containing the vendored (now patched) crates works.
There's a marker file that can easily be looked for in commit hooks for repos that want to enforce a policy of no landing of crates before upstreaming and syncing back. (If someone fails to git add/hg add the .cargo-locally-patched file and evades the commit hook, things will fail quickly in CI.)

@alexcrichton and I had a chance today to talk through the workflow here and the considerations involved.
TLDR, something like what @hsivonen proposed seems quite good, and with a few tweaks it can satisfy the constraints we have on the Cargo side.
I think there's been some confusion about the "principles" that Cargo is trying to maintain, and I think it'd be good to lay out one of the core ones clearly here for all parties:
If you are able to use Cargo to build a Rust project in two different contexts, but with the same lock file, you are guaranteed that the Rust sources being built is the same.
In other words, the lock file should function consistently as a "complete fingerprint" for the Rust dependencies being built, and as long as it doesn't change, you know the Rust build is the same. The checksum we have currently for vendoring is part of ensuring this. And I know, in general, this is a very valuable property for ensuring predictable, reproducible builds.
But this principle in no way rules out the desired workflow! All we need to do is reflect the "locally-patched" status in the lock file, just like we do when you are pulling dependencies from git rather than a crate index. The CI system for Gecko can ensure that nothing gets committed with a lockfile in this state, but for try builds it's just fine.
I believe this is the moral equivalent to what @hsivonen, just respecting the invariant that the relevant info is in the lock file. And I believe we can support all of the workflows he outlined.
If all of this sounds good to all stakeholders, we can get to work implementing it!

Modifying the lockfile sounds totally fine (and desirable), so this SGTM. We just need the tooling to helpfully do the right thing so that novice users don't get frustrated.
Thanks for giving this so much thought and consideration!

Oh, I forgot to mention one important aspect of this approach.
Vendored code, which comes from the crates.io index, is often "incomplete" in a certain sense -- it may not include test code that's present in the git repo for the dependency, for example. In addition, it's a snapshot of a particular publication, not the master branch, so any changes may need to be rebased in order to upstream them.
For that and other reasons, we'd expect the workflow here to be:

Run cargo edit-locally
Edit the vendored code directly
Build and test the top-level project
Upstream changes
Re-vendor

We believe this workflow is well-suited for debugging and tweaking dependency code, and not as well-suited for making bigger changes/feature additions to dependencies (where you'd want to be able to run the local test suite).
However, we probably want to keep the original incarnation of this tool around for Servo (which doesn't vendor sources), which would also give you a workflow that's better for hacking on the master branch of some dependency in a bigger way. We're still working that part of the story out.
Just wanted to make sure everyone was aware of these limitations and use-cases.

All we need to do is reflect the "locally-patched" status in the lock file, just like we do when you are pulling dependencies from git rather than a crate index.

Works for my use cases. Thank you!

Ok I've opened a bunch of issues to track work items here:

https://github.com/rust-lang/cargo/issues/4027
https://github.com/alexcrichton/cargo-edit-locally/issues/2
https://github.com/alexcrichton/cargo-edit-locally/issues/3
https://github.com/alexcrichton/cargo-edit-locally/issues/4

The workflow is slightly different after talking with @wycats some more, but it's morally the same. For Gecko it will look like:

Decide you wish to edit a crate foo
cargo edit-locally foo --path third-party/rust/foo
Edit code in third-part/rust/foo and see changes
When finished, remove [replace] section in Cargo.toml

Essentially with https://github.com/rust-lang/cargo/issues/4027 implemented @bholley solution above will work, and cargo edit-locally will automate the process of modifying the Cargo.toml and Cargo.lock for you.
I'm going to close this in favor of the other work items, but I'll check back in once they're implemented.

This sounds good, and we should be able to wrap the cargo command in a mach command to make it just something like ./mach edit-crate foo.


Resolve standard options and verbosity

From: https://github.com/AcademySoftwareFoundation/openexr/issues/881

Please don't write messages unless it's an error. By default, I'm seeing:

 Configure ILMBASE Version: 2.5.3 Lib API: 25.0.2
 -- WARNING pkg-config generation disabled
 Configure OpenEXR Version: 2.5.3 Lib API: 25.0.2

This happens on every single configuration. That quickly adds up when every project does it.

It would be great if all options are prefixed OPENEXR_ consistently

Don't add CDashBoard targets unconditionally when built as a submodule (this can be worked around by setting BUILD_TESTING to off -- would be nice to have it off by default for submodules though.)

if you're not the top-level project don't set global options. ~An easy check is to compare the CMAKE_CURRENT_SOURCE_DIR with CMAKE_SOURCE_DIR and not turn on global options if OpenEXR is a submodule.~

Note, rather than checking source directory, OpenEXR already has this code in place:
if(NOT "${CMAKE_PROJECT_NAME}" STREQUAL "${PROJECT_NAME}")
  set(OPENEXR_IS_SUBPROJECT ON)
  message(NOTICE "OpenEXR is configuring as a cmake sub project")
endif()

reference:
https://github.com/AcademySoftwareFoundation/openexr/issues/881
https://github.com/AcademySoftwareFoundation/openexr/issues/871
https://github.com/AcademySoftwareFoundation/openexr/issues/833
https://github.com/AcademySoftwareFoundation/openexr/issues/748

For the first point regarding errors, see #899.

For the first point regarding errors, see #899.

These should be addressed in the v3.0.0 release, so closing for now, but feel free to reopen if you encounter further problems.


VS Code Window Losing Focus

Type: Bug
Issue Description:
The Visual Studio Code (VS Code) window frequently loses focus and moves behind other open windows on the same monitor. This issue occurs randomly when clicking within the VS Code window while coding. It can be particularly disruptive, as sometimes even minor mouse movements or clicks trigger this behavior.
Steps to Reproduce:
Open VS Code.
Have multiple windows open on the same monitor.
Click within the VS Code window while coding.
Expected Behavior:
The VS Code window should retain focus and remain in the foreground unless intentionally switched to another window.
Actual Behavior:
The VS Code window loses focus and moves behind other open windows on the same monitor.
Additional Information:
I am using Ubuntu 24.04.
This issue began occurring after updating to version 1.91.
It does not appear to be related to my mouse hardware, as other applications do not exhibit this behavior.
Please investigate this issue, as it significantly affects the usability of the application. Thank you for your assistance.
VS Code version: Code 1.91.0 (ea1445cc7016315d0f5728f8e8b12a45dc0a7286, 2024-07-01T18:52:41.959Z)
OS version: Linux x64 6.8.0-36-generic snap
Modes:

System Info

Item
Value

CPUs
AMD Ryzen 5 5500 (12 x 4249)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
1, 1, 2

Memory (System)
31.21GB (17.18GB free)

Process Argv
--no-sandbox --force-user-env /home/xxx/Code/Projects/Personal/vcalscraper/vcalscraper.code-workspace --crash-reporter-id f54c82e1-86d2-407f-a595-d5b81cfaeb83

Screen Reader
no

VM
0%

DESKTOP_SESSION
ubuntu

XDG_CURRENT_DESKTOP
Unity

XDG_SESSION_DESKTOP
ubuntu

XDG_SESSION_TYPE
x11

Extensions (12)

Extension
Author (truncated)
Version

laravel-extra-intellisense
ami
0.6.6

laravel-goto-view
cod
1.3.11

composer-php-vscode
DEV
1.49.15728

phptools-vscode
DEV
1.49.15728

profiler-php-vscode
DEV
1.49.15728

githistory
don
0.6.20

gitlens
eam
15.1.0

git-graph
mhu
1.30.0

makefile-tools
ms-
0.9.10

laravel5-snippets
one
1.18.0

vscode-blade-formatter
shu
0.24.2

php-debug
xde
1.34.0

A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
vscaat:30438848
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonnoceb:30805159
asynctok:30898717
pythonregdiag2:30936856
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
jchc7451:31067544
chatpanelt:31048053
dsvsc021:30996838
f3je6385:31013174
pythoncenvpt:31062603
a69g1124:31058053
dvdeprecation:31068756
dwnewjupyter:31046869
legacy_priority:31082724

Seems to be happening more when there is a text selection in the window or/and when switching tabs.

Appreciate it @yankuangxindaL4 !!!

Please check if the issue is present with our insiders using both xwayland and wayland backend https://code.visualstudio.com/insiders

I do notice this or very similar issue happening with other application, so at this point I am not sure if this is VS Code specific issue. So, I will close this ticket now.


accelerator.prepare for non-standard PyTorch objects

System Info
- `Accelerate` version: 0.15.0
- Platform: Linux-5.18.19-051819-generic-x86_64-with-glibc2.10
- Python version: 3.8.15
- Numpy version: 1.23.4
- PyTorch version (GPU?): 1.11.0 (True)
- `Accelerate` default config:
        - compute_environment: LOCAL_MACHINE
        - distributed_type: MULTI_GPU
        - mixed_precision: no
        - use_cpu: False
        - dynamo_backend: NO
        - num_processes: 1
        - machine_rank: 0
        - num_machines: 1
        - gpu_ids: all
        - main_process_ip: None
        - main_process_port: None
        - rdzv_backend: static
        - same_network: True
        - main_training_function: main
        - deepspeed_config: {}
        - fsdp_config: {}
        - megatron_lm_config: {}
        - downcast_bf16: no
        - tpu_name: None
        - tpu_zone: None
        - command_file: None
        - commands: None

Information

[ ] The official example scripts
[X] My own modified scripts

Tasks

[ ] One of the scripts in the examples/ folder of Accelerate or an officially supported no_trainer script in the examples folder of the transformers repo (such as run_no_trainer_glue.py)
[X] My own task or dataset (give details below)

Reproduction
I want to adapt the accelerator to mmlab libraries, such as mmseg, mmdet.
I have faced some challenges because accelerator.prepare only accepts standard torch.nn objects. However, in mmlab libraries, they rewrite a container class inherited from torch.nn.
For instance, mmcv has a module called base_module  which implements a few core functionality for downstream components. Therefore simply using accelerator.prepare contains the model in mmlab series won't work.
My current modification in mmdet provided train.py.
    if args.launcher == 'accelerator':
        model, datasets = accelerator.prepare(model, datasets)

    train_detector(
        model,
        datasets,
        cfg,
        distributed=distributed,
        validate=(not args.no_validate),
        timestamp=timestamp,
        meta=meta)

When I was launching the training script by the accelerator, the following errors were given due to force cast  base_module class back to torch.nn.Module while some core logits have been erased.
─────────────────────────────── Traceback (most recent call last) ────────────────────────────────╮
│ /home/akide/pychram_remote/xxx/xxx/tools/train_accelerator.py:446   │
│ in <module>                                                                                │
│                                                                                │
│   443 │   runner.run(data_loaders, cfg.workflow)                                                 │
│   444                                                                                │
│   445 if __name__ == '__main__':                                                                 │
│ ❱ 446 │   main()                                                                                │
│   447                                                                                │
│                                                                                │
│ /home/akide/pychram_remote/xxx/xxx/tools/train_accelerator.py:300   │
│ in main                                                                                │
│                                                                                │
│   297 │   if args.launcher == 'accelerator':                                                     │
│   298 │   │   model, data = accelerator.prepare(model, datasets)                                 │
│   299 │                                                                                │
│ ❱ 300 │   train_detector(                                                                        │
│   301 │   │   model,                                                                             │
│   302 │   │   datasets,                                                                          │
│   303 │   │   cfg,                                                                               │
│                                                                                │
│ /home/akide/pychram_remote/xxx/xxx/tools/train_accelerator.py:443   │
│   442 │   │   runner.load_checkpoint(cfg.load_from)                                              │
│   141 │   │   │   │   for _ in range(iters):                                                     │
│                                                                                │
│   1182 │   │   │   modules = self.__dict__['_modules']                                           │
│   1183 │   │   │   if name in modules:                                                           │
│   1184 │   │   │   │   return modules[name]                                                      │
│ ❱ 1185 │   │   raise AttributeError("'{}' object has no attribute '{}'".format(                  │
│   1186 │   │   │   type(self).__name__, name))                                                   │
│   1187 │                                                                                │
│   1188 │   def __setattr__(self, name: str, value: Union[Tensor, 'Module']) -> None:             │
╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
AttributeError: 'DistributedDataParallel' object has no attribute 'train_step'
[08:52:52] ERROR    failed (exitcode: 1) local_rank: 0 (pid: 4144685) of binary:                           api.py:684
                    /home/akide/anaconda3/envs/xxx/bin/python3.8

Expected behavior
Does there have some kind of way to prevent forced object casting when using `accelerator.prepare` ?

No there is no way to change this. You can however call accelerator.unwrap(model) to get back you original model and call its methods. For instance in Transformers, we often do accelerator.unwrap(model).generate() in evaluation of NLP models.

No there is no way to change this. You can however call accelerator.unwrap(model) to get back you original model and call its methods. For instance in Transformers, we often do accelerator.unwrap(model).generate() in evaluation of NLP models.

Did you perhaps mean accelerator.unwrap_model(model)? And it's not clear if unwrap_model is also applicable to non-model objects, e.g. a custom dataloader?

@claforte yes, unwrap_model is what you want. When it comes to non-model objects, at this time no there isn't a way to un-DDP-inize them. If you want to use a DataLoader in such a way you should make a new one later.

Are these assumptions/limitations documented somewhere? That would make it a lot easier to integrate in complex code bases...
(Thanks a lot for creating and continuing to improve Accelerate BTW... we used it a lot in my previous job at AMD, and I'm eager to use it again now that I joined Stability AI. ;-) )


PVS-Studio warning fixes

Fix some cmake warnings.
Use stricter options for cmake to catch problems with it eariler.
Fix some warnings found by PVS-Studio.
Add windows manifests for supported OS, visual styles and DPI v. 1/v. 2 awareness.

Product page: https://www.viva64.com/en/pvs-studio/
How to use for free: https://www.viva64.com/en/b/0600/

Hi @dimhotepus, great to see you again! And thank you for all that care for our project! 👍
Is it possible to rebase this on 0.52.0/sync branch, and possibly re-run your tool on this branch? Once rebased, you can edit the PR to change the target branch.
We are in the very final steps of our release candidate phase for our next release, the 0.52 one. It's now a matter of days before we release it. So, the master branch which is intended to be compatible with our 3 years old 0.51 version lacks a lot of new code, or stuff may have already been fixed on 0.52.0/sync, like the https thing: https://github.com/DaemonEngine/Daemon/pull/444 🙂.

Thank you for the rebase! I modified the PR target accordingly. 😉

I assume the [cmake] Use https:// proto instead of http:// commit can now be renamed to something else, it looks like the remaining change from this commit is a minified url expected to redirect to the final one, being replaced by the final one?

I'd like to see the stuff that adds new code in a separate PR from the warning fixes, as the PR is becoming unwieldily long.
Regarding the part that makes CMake warnings into errors, I'll need to check whether the CMake version is fixed or not in our CI systems (Travis, Appveyor, Azure Pipelines). If the version is not fixed and can change without any change to our configuration, then I would prefer not to make warnings into errors, because it's annoying to have the build break in a way that does not correspond to a code change, and CMake warnings have a low signal-to-noise ratio.

Now that 0.52.0/sync is merged on master, I modified this PR target to master again. 🙂

@slipher, @illwieckz, @bmorel
I've splitted PR as requested, feel free to review / comment.

I didn't found a way to validate each commit independently so we can focus only on a part of the PR.
So what I did is that I cherry-picked and merged some commits that looked super obvious to me or were a comment from @slipher said this was ok.
So 15 commits were merged, ony 9 are left:
https://github.com/DaemonEngine/Daemon/pull/457/commits/a0f6906a81dc80173118d4d5f009e4a4c832f8c2
https://github.com/DaemonEngine/Daemon/pull/457/commits/de231b053ea3667b585618a214d89d0207b64ecd
https://github.com/DaemonEngine/Daemon/pull/457/commits/cf9be78ae8592520d556d68f56748321f9bd61fc
https://github.com/DaemonEngine/Daemon/pull/457/commits/b67f4c9f03c8199976d6b12fdf660ed0cab06721
https://github.com/DaemonEngine/Daemon/pull/457/commits/bbc761b4598bdb76403c1c292d52fdeaefa394f6
https://github.com/DaemonEngine/Daemon/pull/457/commits/d61c323f0999c50c08327754e4bb7b26369d8bf5
https://github.com/DaemonEngine/Daemon/pull/457/commits/3ecbb31a445f452139e17c3c0667f3fa19f2128e
https://github.com/DaemonEngine/Daemon/pull/457/commits/f75a21a284c40e54c40300ca56d1be3290f89fe4
https://github.com/DaemonEngine/Daemon/pull/457/commits/14c7354c5f18f5c6f8e4f5f4d4cd9697af952e70
@dimhotepus what you can do is to reset your branch on parent commit 7c864f98e01efd89cc73e917c28c96b0242b19e0, rebase on upstream master then reimport the 9 remaining commits this way:
git cherry-pick a0f6906a81dc80173118d4d5f009e4a4c832f8c2
git cherry-pick de231b053ea3667b585618a214d89d0207b64ecd
git cherry-pick cf9be78ae8592520d556d68f56748321f9bd61fc
git cherry-pick b67f4c9f03c8199976d6b12fdf660ed0cab06721
git cherry-pick bbc761b4598bdb76403c1c292d52fdeaefa394f6
git cherry-pick d61c323f0999c50c08327754e4bb7b26369d8bf5
git cherry-pick 3ecbb31a445f452139e17c3c0667f3fa19f2128e
git cherry-pick f75a21a284c40e54c40300ca56d1be3290f89fe4
git cherry-pick 14c7354c5f18f5c6f8e4f5f4d4cd9697af952e70

And force push, this way there would be only 9 commits remaining in that PR.

I had a few more stylistic quibbles, but didn't want to eat up any more of your time, so I patched the changes a bit and pushed them to master. Thanks!


[BUG]: pnpm run play 失败

Describe the bug
我用ni安装完项目依赖，执行nr play后，显示以下报错：

我发现在packages/components、packages/onu-ui和packages/preset中，并没有build生成的dist文件夹，所以我分别在这三个项目中去执行build生成dist。然后再执行nr play,结果显示另外一个错误。如下图所示：

Reproduction
No response
System Info
System:
    OS: Windows 10 10.0.19044
    CPU: (16) x64 11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz
    Memory: 3.27 GB / 15.72 GB
  Binaries:
    Node: 16.17.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - C:\Program Files\nodejs\yarn.CMD
    npm: 8.15.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (105.0.1343.53)
    Internet Explorer: 11.0.19041.1566
  npmPackages:
    vue: ^3.2.39 => 3.2.39

Used Package Manager
pnpm
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a OnuUI issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/core instead.
[X] The provided reproduction is a minimal reproducible example of the bug.

Try to nr build then nr play

按照你的方法解决问题了，非常感谢解答。


ci: update git submodule

Description
..to pull in latest updates for run-catalog-onboarding-pipeline.sh
Types of changes in this PR
No release required

[ ] Examples or tests (addition or updates of examples or tests)
[ ] Documentation update
[ ] CI-related update (pipeline, etc.)
[ ] Other changes that don't affect Terraform code

Release required

[ ] Bug fix (patch release (x.x.X): Change that fixes an issue and is compatible with earlier versions)
[ ] New feature (minor release (x.X.x): Change that adds functionality and is compatible with earlier versions)
[ ] Breaking change (major release (X.x.x): Change that is likely incompatible with previous versions)

Release notes content
Replace this text with information that users need to know about the bug fixes, features, and breaking changes. This information helps the merger write the commit message that is published in the release notes for the module.

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

Merge actions for mergers

Merge by using "Squash and merge".

Use a relevant conventional commit message that is based on the PR contents and any release notes provided by the PR author.
The commit message determines whether a new version of the module is needed, and if so, which semver increment to use (major, minor, or patch).

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

GitHub release
v3.5.1

Your semantic-release bot :package::rocket:


Support deletion of Data Products

Today a producer can't delete a data product.

This should block on existing subscriptions, and only delete data products once there are no existing subscriptions.


Question: Is this package side effect free?

I found this on Reddit and saw it exports as an EcmaScript Module, but doesn't have a sideEffects property in package.json.
Details on the sideEffects property: https://webpack.js.org/guides/tree-shaking/#mark-the-file-as-side-effect-free
It's a link to the Webpack guides, but it's the most in-depth explanation on sideEffects with examples that applies to Javascript itself and other bundlers used by consumers.

Hello James @wopian,
Thank you for your question. I'll take a look at it and get back to you when I have something.
Kindly,
David

Hi again James @wopian,
Forgive me if I'm misunderstanding this question after reading the docs 😊, but Embla Carousel should be tree shakable, according to Bundlephobia:

Do you have any further thoughts about this, like if there are other aspects of this that I may have missed?
Best,
David

@davidcetinkaya sideEffects is a part of tree-shaking. Bundlers will check the property instead of evaluating the code (much slower and less accurate) to check if there are no side effects when the property is not present, before they will drop the unused code from the consumer's bundle.
In the bundlephobia example, it wasn't able to analyse the exports due to this property not being present.
As bundlephobia says it's tree-shakeable it's likely safe to add sideEffects: false, but I havent read the source code to verify.

Hi again @wopian,
Thank you for the explanation, it was clear and concise and better than the Webpack explanation 😉. Feel free to submit a PR adding this to package.json after analyzing the code if you want to contribute. Otherwise I'll dig into this as soon as possible.


No /navigate endpoint documentation

Graphhopper has a /navigate endpoint that is very useful for integration of Graphhopper into projects like MapLibre Navigation or Ferrostar, which both support OSRM type responses. But the documentation within Graphhopper for this is lacking:

https://docs.graphhopper.com/#tag/Routing-API just points to the navigation example app for android.
https://explorer.graphhopper.com doesn't even list the navigation endpoint.

Sometimes the documentation also references mapbox's API documentation, but as Graphhopper doesn't actually support the full Mapbox/OSRM spec, it is extremely difficult to determine which parts of the spec are already supported, which one's are not. It would be awesome if the /navigate endpoint could get some official documentation, or an official openapi spec.

Ferrostar has a built in OSRM parser, Ferrostar does not have a  built in parser for a graphhopper response. Same goes for Maplibre Navigation. OSRM/Mapbox is a defacto global standard. Most 3rd parties I am aware of write parsers for OSRM, but not for Graphhopper's response format - thats what make graphhopper so awesome, as it can provide both.

Especially for ferrorstar the /route endpoint should be used and not the rather limiting /navigate endpoint.

Hmm, do you consider the OSRM response format too limiting for routing, or do you mean that the /navigate implementation is limited and isn't exposing as much as /route because not everything has been implemented here yet?
In my opinion Graphhopper should embrace its /navigate endpoint proudly and make it a first class citizen, as it makes Graphhopper directly usable by a wider community - and that could start with better own documentation.


Fix extra Japanese font-family settings

Additional specification and adjustment of Japanese font environment in Windows environment.

MS Gothic/MS Mincho is specified first, so it is displayed with top priority. However, I don't think it's very good because the jaggies are noticeable on the display.
Therefore, I would like to prioritize the BIZ UD fonts added in recent years, and replace them in the order of Yu fonts and then MS fonts.

With the standard font settings, the BIZ font also clogs up the margins of punctuation marks, but I think it's better than the Yu/MS font.

For macOS, I think there will be no problem for the time being by having the Hiragino font specified first.
In current browsers, it is no longer necessary to specify both English and Japanese when specifying the Japanese font-family. Therefore, I chose to use only English.

However, Yu Fonts has different English names ("Yu Gothic", "YuGothic") in Windows and macOS environments... Therefore, it is necessary to specify both.

Hi,
Maintainer of ReadiumCSS here.
I guess this change would be better suited in the source of ReadiumCSS itself, as it would consequently benefit all apps using it. In addition, there is a risk losing it while updating the distribution/built stylesheets navigator-js is using as we’re in the process of updating ReadiumCSS right now, with multiple changes and bug fixes planned. We’ve already started implementing features initially implemented into Thorium for instance.
In branch develop:

the patch is a module on its own;
the font-stacks are located in module “base”.

Please let me know if that sounds good to you, and how I can help make the process smoother.

@JayPanoz Thank you for following up. I'm going to close this pull request and submit a pull request to Readium-CSS.
If possible, please tell me about the following:

Did you add ReadiumCSS-ebpaj_fonts_patch.css at the request of ebpaj? I couldn't really understand it by looking at the Readium-CSS commit log. If I were asked to do so, I thought it would be better not to remove the font specification for Japanese names, so I wanted to ask.
In ReadiumCSS-base.css, I didn't really understand the difference between -RS__baseFontFamily: and the four specifications that follow. Where is the font specified with -RS__baseFontFamily: used? (The four specifications that follow specify the font of the book, right?)

For the time being, I submitted a pull request to Readium-CSS. Thank you.
https://github.com/readium/readium-css/pull/146

Resolution: https://github.com/readium/readium-css/pull/146

Backport of ReadiumCSS here: https://github.com/readium/r2-navigator-js/commit/17b86f29487ff90f73ae8e754287ee91dc1c222e


[SPARK-16240][ML] ML persistence backward compatibility for LDA

What changes were proposed in this pull request?
Allow Spark 2.x to load instances of LDA, LocalLDAModel, and DistributedLDAModel saved from Spark 1.6.
How was this patch tested?
I tested this manually, saving the 3 types from 1.6 and loading them into master (2.x).  In the future, we can add generic tests for testing backwards compatibility across all ML models in SPARK-15573.

To reviewers: This code was taken and modified from [https://github.com/apache/spark/pull/14112].  @GayathriMurali should be the primary author when we merge this into master and branch-2.0

CC @hhbyyh Would you mind taking a look? thanks!

Test build #65168 has started for PR 15034 at commit a931b25.

Test build #65168 has finished for PR 15034 at commit a931b25.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65168/
Test PASSed.

Merged build finished. Test PASSed.

Thanks @jkbradley. This matches what I had in mind. LGTM.

Test build #3279 has started for PR 15034 at commit a931b25.

Thanks @hhbyyh !

Test build #3279 has finished for PR 15034 at commit a931b25.

This patch fails Spark unit tests.
This patch does not merge cleanly.
This patch adds no public classes.

Jenkins, retest this please.

Test build #65621 has started for PR 15034 at commit a931b25.

Test build #65621 has finished for PR 15034 at commit a931b25.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65621/
Test FAILed.

Merged build finished. Test FAILed.

@jkbradley, it looks like this is legitimately failing MiMa (not sure why it passed on the first run...):
[error]  * the type hierarchy of object org.apache.spark.ml.clustering.LDA is different in current version. Missing types {org.apache.spark.ml.util.DefaultParamsReadable}
[error]    filter with: ProblemFilters.exclude[MissingTypesProblem]("org.apache.spark.ml.clustering.LDA$")

@JoshRosen That is weird; MiMa passes for me locally, but I see that it shouldn't.  I added a MiMaException; this should not be a problem for users.

Test build #65789 has started for PR 15034 at commit 3b499df.

Test build #65789 has finished for PR 15034 at commit 3b499df.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65789/
Test PASSed.

I'll go ahead and merge this.  Thanks @hhbyyh for reviewing it!


Roll engine 113b91fe82f1..9f92324fd6aa (7 commits)

https://github.com/flutter/engine/compare/113b91fe82f1...9f92324fd6aa
git log 113b91fe82f147b3fb77899726736171c06dad26..9f92324fd6aa9f592db19bf380186c4ed6da2e7c --no-merges --oneline
9f92324fd Suppress deprecation warning for usage of Configuration.locale (flutter/engine#7973)
9b21ea857 Roll src/third_party/dart 385be0cf31..05bba46133 (6 commits)
e3f1bdc4d Roll src/third_party/skia adfc6e40df30..4dbb96dfaa04 (6 commits) (flutter/engine#7970)
e32531f0e Switch flutter's dart sdk to full and add dartdevc libraries (flutter/engine#7968)
fb1c543dd Link dart:* sources into engine for debugger source support (flutter/engine#7908)
dd3656a51 Roll src/third_party/dart 0f9a5198bd..385be0cf31 (14 commits)
4434a39c7 Add api 21 check to LocalizationChannel.java (flutter/engine#7967)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff (garyq@google.com), and stop
the roller if necessary.

Trybots failed. These were the failed builds: https://cirrus-ci.com/task/6308769890828288 , https://cirrus-ci.com/task/5042132495630336 , https://cirrus-ci.com/task/6730982355894272

Commit queue failed; closing this roll.


Issue#2 with savestate

This is the result with an 80 ton allowance and negotiated for all salvage (negative cbill outcome as a result).
It was saved and loaded a few times so that part is working.

I havent forgotten you, sorry it takes so long, having some slight health problems right now, so dont feel like testing, but i promise before i start work on another mod i will test this first.

I appreciate the reply I was honestly wondering a bit.  I hope you feel
better soon, no rush on the mods, just a hobby for me, health first!
On Mon, Jun 11, 2018 at 2:52 PM Morphyum<EMAIL_ADDRESS>wrote:

I havent forgotten you, sorry it takes so long, having some slight health
problems right now, so dont feel like testing, but i promise before i start
work on another mod i will test this first.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Morphyum/DropCostPerMech/pull/9#issuecomment-396383396,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARmQpdfm6F30gpKA8LmtpP8oICYRf3fvks5t7tiLgaJpZM4UheAm
.

Woo!  thanks Morphyum
On Tue, Jun 12, 2018, 8:03 AM Morphyum<EMAIL_ADDRESS>wrote:

Merged #9 https://github.com/Morphyum/DropCostPerMech/pull/9.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Morphyum/DropCostPerMech/pull/9#event-1676376246, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ARmQpYTFX8VxNgsFztnydSyH2athFFo3ks5t78ongaJpZM4UheAm
.

i thank you for delivering people that want this feature :)


Clear Command UI Bug

The panel turns to grey upon clear command which makes the UI uncomprehensive

Solved in #197


Add test services and a test integration framework

The old border patrol has test services and a test integration framework. We need those too.

@trane do you think this is taken care of? Or this is an issue to cover integration tests?

scalatest coverage is north of 95%.


[PURIS KIT] 24.08 Release Checks

This issue tracks all relevant release checks for your KIT.

[!IMPORTANT]
Follow the guidance on how to use the templates.

Release Info
Please provide information on what you want to be included in the Eclipse Tractus-X release.
If you are not owner of this issue, please provide the information as comment to the issue.
Have your prepared content reviewed by a professional peer group before submitting it for committer approval.
Best practice: have a professional Peer review your prepared content before you submit for expert approvals.
Please link the open or merged PR that includes the changes.
Version to be included in Eclipse Tractus-X release: 0.3.0

KIT semantic version of change log.
Date of KIT publication must be aligned with overall release date.

If changes to your KIT are not yet live on our website, link the open PR introducing the changes for this release.
If changes are already live, also point out the PRs witch included the changes for this version if possible.

https://github.com/eclipse-tractusx/eclipse-tractusx.github.io/pull/986

General

[x] CHANGELOG available and maintained
[x] Tractus-X Release Guidelines fulfilled

Adoption View

[x] Vision and Mission statement present
[x] Business Value statement present
[x] Semantic Models linked and described
[ ] Logic / Schema available and described
[x] Business Process documentation available
[x] Standards submitted / published via the Catena-X e.V. process and linked with current version (e.g., semantic models)
[ ] Tutorials available
[ ] White Paper available
[x] Notice CC BY 4.0 licence statement available

Development View

[ ] API Specification published on SwaggerHub
[x] Protocols available (e.g., dataspace protocol)
[x] Sample Data available
[x] Architecture integration into the overall Catena-X architecture and / or product architecture (e.g., Arc42) available.
[x] Reference Implementation available
[x] Access and Usage Policies documented

Operation View

[x] Setup Guide available (e.g., installation guides)
[x] Deployment Script available (e.g., helm charts)

Helpful Links
Standards
The relevant standards can be found in the Catena-X Association Standard Library:

CX-0118 Delivery Information Exchange 2.0.0
CX-0120 Short-Term Material Demand Exchange 2.0.0
CX-0121 Planned Production Output Exchange
CX-0122 Item Stock Exchange 2.0.0
CX-0145 Days of Supply Exchange 1.0.0

cc @jSchuetz88

Puris Kit is merged!

Hi @dominikoeh,
thank you for all your efforts :), as the PR has been approved and already merged, I changed the status to done.


NestedScrollView is broken. Body is scrollable even if it has no elements

Steps to Reproduce

Execute flutter run on the code sample
...
...

Expected results:
I expect NestedScrollView body to not be scrollable when there are no items.
Actual results:
NestedScrollView is scrollable. There is no way to implement RefreshIndicator with SliverAppBar, which is very discouraging, considering this is so a simple feature.

Code sample

NestedScrollView(
  headerSliverBuilder: (_, __) => SliverAppBar(
    pinned: true,
    floating: true,
    flexibleSpace: SomeWidget(),
  ),
  body: ListView.builder(
  ....
);

Logs

You can wrap the ListView.builder in a ScrollController and only allow it to scroll when there are items in it.
final _scrollController = ScrollController(); ... NestedScrollView(   headerSliverBuilder: (_, __) => SliverAppBar(     pinned: true,     floating: true,     flexibleSpace: SomeWidget(),   ),   body: ListView.builder(     controller: _scrollController,     physics: items.isEmpty ?  NeverScrollableScrollPhysics doesn't block the scroll in this case

@nzkn
Check this out:
https://dartpad.dev/?id=3ce3c0a47f7f93249048dd989df94be0
Additionally, if you want, you can set NestedScrollView widget's physics property to NeverScrollableScrollPhysics().

@ravanalaskarov Do you test your code before posting? Both solutions you suggested doesn't solve the issue

@nzkn Please provide a completed and minimal reproducible code sample so that we may verify this. Also, please provide the output of flutter doctor -v as well.


[BUG] [Monitor] Logs sent through AzureMonitorLogExporter are not interpolated properly

Library name and version
Azure.Monitor.OpenTelemetry.AspNetCore 1.2.0
Describe the bug
Hello all. I have an ASP.NET 8 application which is currently using the old Application Insights SDK to ship logs and metrics to Application Insights. I am currently in the process of replacing the old SDK with the new OpenTelemetry package.
Our application uses Serilog for logging, which has a dedicated Application Insights sink. Since there is no official Serilog sink using the OTel package, I had to write my own to get feature parity. I implemented the sink according to the migration docs. However, when logging messages to the OTel-enabled ILogger, the messages arrive into Application Insights without being interpolated.
Expected behavior
Log messages are properly interpolated so that they are easily readable. Instead of Message with placeholder: {hole}, the message should be Message with placeholder: 42, same as what the console logger does:

Actual behavior
Logs show up in Application Insights without interpolation, with correct customDimensions:

Reproduction Steps
I created a small repro using a console application:
using Azure.Monitor.OpenTelemetry.Exporter;
using Microsoft.Extensions.Logging;
using OpenTelemetry.Resources;

using var loggerFactory = LoggerFactory.Create(builder => builder
    .AddConsole()
    .AddOpenTelemetry(logging =>
    {
            logging.SetResourceBuilder(ResourceBuilder.CreateDefault());
            logging.AddAzureMonitorLogExporter(c => c.ConnectionString = "...");
    }));

var logger = loggerFactory.CreateLogger<Program>();

logger.LogInformation("Message with placeholder: {hole}", 42);

Console.ReadLine();

Environment
VS Code 1.95.1 + C# + C# DevKit.
.NET SDK:
 Version:           9.0.100-rc.2.24474.11
 Commit:            315e1305db
 Workload version:  9.0.100-manifests.cea95dba
 MSBuild version:   17.12.0-preview-24473-03+fea15fbd1

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.22631
 OS Platform: Windows
 RID:         win-x64
 Base Path:   C:\Program Files\dotnet\sdk\9.0.100-rc.2.24474.11\

.NET workloads installed:
 [aspire]
   Installation Source: VS 17.11.35327.3
   Manifest Version:    8.2.0/8.0.100
   Manifest Path:       C:\Program Files\dotnet\sdk-manifests\8.0.100\microsoft.net.sdk.aspire\8.2.0\WorkloadManifest.json
   Install Type:              Msi

Configured to use loose manifests when installing new manifests.

Host:
  Version:      9.0.0-rc.2.24473.5
  Architecture: x64
  Commit:       990ebf52fc

.NET SDKs installed:
  8.0.403 [C:\Program Files\dotnet\sdk]
  9.0.100-rc.2.24474.11 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 8.0.10 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 9.0.0-rc.2.24474.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 6.0.35 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.10 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 9.0.0-rc.2.24473.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 6.0.35 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 8.0.10 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 9.0.0-rc.2.24474.4 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Other architectures found:
  x86   [C:\Program Files (x86)\dotnet]
    registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]

Environment variables:
  Not set

global.json file:
  Not found

Learn more:
  https://aka.ms/dotnet/info

Download .NET:
  https://aka.ms/dotnet/download

I think you need to set IncludeFormattedmessage = true in your AddOpenTelemetry config.
https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/docs/logs/customizing-the-sdk/README.md#includeformattedmessage
.AddOpenTelemetry(logging =>
{
    logging.IncludeFormattedMessage = true;

Thanks for pointing me to the configuration setting, that solves the issue.
However, I would like to ask why isn't this the default behavior - at least for modern ASP.NET applications, it is strongly recommended to use message templates when logging. This also works out-of-the-box for the original AppInsights SDK so I expect most people migrating to the Monitor Distro will encounter this.
I would either expect this behavior to be enabled by default (to ensure a behavior consistent with other logging sinks) or the migration documentation to mention this explicitly in the Sending Logs section to mitigate confusion.

Thanks for looking into the documentation! Since the original question got answered, feel free to close the issue (unless you wish to keep it open to track the docs update).


Creating new tool section during installation

It should be possible to also create new sections and put tools into multiple sections. @afgane do you know if the API supports this?

Adding to this, it should also be possible to leave out the section entirely, for repositories that do not include tools (e.g. package_*).

@bgruening Creating new sections via the Galaxy API is not possible - the tool will just get installed outside any section: https://github.com/galaxyproject/galaxy/blob/dev/lib/galaxy/webapps/galaxy/api/tool_shed_repositories.py#L206
I couldn't think of a reason why this needs be like that so I think it's a matter of implementing it properly but I never got to it (clearly, nobody else has either).
@natefoo Not sure I get what you mean?

@afgane I may occasionally want to install a repository that does not go in a section at all. Typically this is not the case, but it can happen (and was in fact my first test case for this role).

@bgruening @natefoo @afgane I believe creating a new tool panel section during an installation is now possible with this fix: https://github.com/galaxyproject/ansible-galaxy-tools/pull/34

This should have long been closed with https://github.com/galaxyproject/ansible-galaxy-tools/pull/8/files ... I'm just curious why it has worked for me all along, while others seem to struggle.

@mvdbeek This PR https://github.com/galaxyproject/ansible-galaxy-tools/pull/8/files only allows for adding a tool to an existing section in the tool panel - just the same as using tool_panel_section_id.  The approach will not work with bioblend though, since the function signature does not accept a tool_panel_section_label.  This PR: https://github.com/galaxyproject/ansible-galaxy-tools/pull/34 allows for adding a new tool panel section label for the installation.  It uses the new_tool_panel_section_label param (which is supported by bioblend) rather than the tool_panel_section_label (which is not).

Please see my comments on #34.
So what's going on here is that we have never used the kwargs of bioblend.
Now the version of bioblend adds one field, so indeed it's misaligned, but this has also been fixed in ephemeris.


Makes User.promotions_muted_at property fillable

What's this PR do?
This pull request fixes a bug in #1121 -- when I added the promotions_muted_at field, it wasn't editable via API request.
How should this be reviewed?
👀
Any background context you want to provide?
I wondered whether the additional test is kind of repetitive alongside a lot of the other tests, but at the same time -- I didn't catch this bug until trying to edit the field over in a new Chompy import.
Relevant tickets
References Pivotal #176771234.
Checklist

[x] This PR has been added to the relevant Pivotal card.
[x] Documentation added for new features/changed endpoints.
[x] Added appropriate feature/unit tests.
[ ] If new attributes were added to users, there is a corresponding PR to surface these in Aurora.
[ ] If new attributes were added to users, then the data team already knows about these changes.

I wondered whether the additional test is kind of repetitive alongside a lot of the other tests, but at the same time -- I didn't catch this bug until trying to edit the field over in a new Chompy import.

👍  And this does feel like a good "feature/integration" test especially now that we're actively updating this field via Chompy!


Issue 48193: LKS: Creating file directories with same name & different casing on hosted servers

Rationale
Issue 48193: LKS: Creating file directories with same name & different casing on hosted servers
The per request resourceCache uses Path as key. Path is case insensitive. For a file system is case sensitive, such as linux, the case insensitive resourceCache is failing to return resources with different casing.
This PR create a subclass DavPath, that checks OS to guess desired case-sensitivity for the file system.
Additionally, a new subclass S3Path is created for S3 files, to accommodate scenarios of using S3 storage for on premise deployments.
Related Pull Requests

https://github.com/LabKey/platform/pull/4629
https://github.com/LabKey/cloud/pull/130

Changes

Use DavPath as resourceCache key, which checks OS to determine case-sensitivity
(Optional change) Special casing S3 resources to use a separate S3Path that's always case-sensitive

It looks like we might be able to add a toPath() method on WebdavResource. Most resources can return a DavPath but the S3 resources can override and return S3Path. I think that might let us get rid of the separate s3ResourceCache.
We already have more code than I'd like that's special-casing for S3, so I'm looking for ways to avoid adding more checks.

I thought about using a single cache, but couldn't think a way that won't break equals() contract. For example, there are 2 resources, one on macOs ("/labkey_webdav/folder1"), one on S3 ("/labkey_webdav/FOLDER1"). macOs.equals(S3) would return true, but S3.equals(macOs) would return false. Though in reality this scenario is unlikely to happen because a file root is either mounted or not, but not a mix.


Automate the default bond denom value setting

Currently when starting the chain, after the genesis creation, we need to remember to edit the genesis.json file and change the bond_denom param inside the staking module from stake to desmos.
I personally find this thing a little bit tedious to do  by hand and I think we can automate it by creating a wrapper staking module that acts exactly as the default one but simply sets the proper bond_denom value (desmos) during genesis.
This would allow for easier on-boarding of new developers and faster local development of the chain itself.

That would be great. Or we can add a flag to the command too. https://github.com/cosmos/cosmos-sdk/issues/5228

How about updating the staking module directly and make a PR to the SDK? https://github.com/cosmos/cosmos-sdk/issues/5228#issuecomment-544987386

Cosmos SDK PR reference: cosmos/cosmos-sdk#5247

What do you think about Henrik's approach? I do notice that the params can be overridden but doing this to every module we would like to change looks a bit ad-hoc and Bez comment seems valid. Unless there is a method signature in the module interface, there is currently no elegant way to do this.


fix(wallaby): update compiler presets

Deploy preview processing.
Built with commit 2eb12a69e7197cd21be1192d1efa137d85d709f6
https://app.netlify.com/sites/swan-example/deploys/586b9b27a7e2d2721ba336c6