cuda version error and cstr error

ComfyUI-Manager: EXECUTE => ['/home/daehwa/miniconda3/envs/ComfyUI/bin/python', 'install.py']
[!] Traceback (most recent call last):
[!]   File "/home/daehwa/Documents/ComfyUI/custom_nodes/ComfyUI-3D-Pack/install.py", line 19, in
[!]     from build_utils import (
[!]   File "/home/daehwa/Documents/ComfyUI/custom_nodes/ComfyUI-3D-Pack/_Pre_Builds/_Build_Scripts/build_utils.py", line 41, in
[!]     CUDA_VERSION = get_cuda_version()
[!]                    ^^^^^^^^^^^^^^^^^^
[!]   File "/home/daehwa/Documents/ComfyUI/custom_nodes/ComfyUI-3D-Pack/_Pre_Builds/_Build_Scripts/build_utils.py", line 38, in get_cuda_version
[!]     raise RuntimeError(f"Please install/reinstall CUDA tookit with any of the following supported version: {build_config.supported_cuda_versions}")
[!] RuntimeError: Please install/reinstall CUDA tookit with any of the following supported version: ['12.1', '11.8']
[!]
[!] During handling of the above exception, another exception occurred:
[!]
[!] Traceback (most recent call last):
[!]   File "/home/daehwa/Documents/ComfyUI/custom_nodes/ComfyUI-3D-Pack/install.py", line 83, in
[!]     cstr("Comfy3D install failed: Dependency installation has failed. Please install manually: https://github.com/MrForExample/ComfyUI-3D-Pack/tree/main/_Pre_Builds/README.md.").error.print()
[!]     ^^^^
[!] NameError: name 'cstr' is not defined. Did you mean: 'str'?
install script failed: https://github.com/MrForExample/ComfyUI-3D-Pack
Attempt to fixing '['https://github.com/MrForExample/ComfyUI-3D-Pack']' is done.
After restarting ComfyUI, please refresh the browser.
I got the above error.
but when the print the my computer's Cuda driver version, It correctly worked.
What is the matter? Thank you.
daehwa@daehwa:~$ nvcc -V
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2023 NVIDIA Corporation
Built on Tue_Feb__7_19:32:13_PST_2023
Cuda compilation tools, release 12.1, V12.1.66
Build cuda_12.1.r12.1/compiler.32415258_0

Hi @daehwa00 I'm not sure exactly why that's the case for you, if that's your nvcc output then it should pick it up.
But we can do a simple debug first, can you go to _Pre_Builds_Build_Scripts\build_utils.py at line 33 add following and see what's been print out:
print(f"[DEBUG] Returncode: {result.returncode} \n Output: {result.stdout} \n Error: {result.stderr}")

Just updated the build script, that issue is fixed now! Cheers

Thank you for your help 😀


api denied with 'forbidden' error response

I am running actual budget as a docker container. It is accessible on localhost:5006.
However, when trying to use actual-http-api on port 5007 I get the following response:
{
  "error": "Forbidden"
}

I have correctly configured actual-http-api with my username and password of my actual budget login.
Is there some additional configuration I need to make to my actual budget docker instance to get the API to work?

Hey, so there are 2 environment variables you need to configure when deploying actual http api:

ACTUAL_SERVER_PASSWORD: Here you put the actual budget server password
API_KEY: This is a custom random string value that you create. There are some special characters that can cause problems, see issue 8.

Then when you call the api you have to pass the random string (API_KEY) as header:
curl -X 'GET' 'http://localhost:5007/v1/budgets/{BUDGET-SYNC-ID}/accounts' \
 -H 'accept: application/json' \
 -H 'x-api-key: {API_KEY}'

Closing for inactivity, feel free to re-open if more help is needed.


Run the tool as a CLI

Instead of launching the tool via python scripts (python some_script.py args), run it as a CLI (using click or cloup packages).
This means, users don't have to clone the project, they'll just need to install it as a python package, and launch it right away with correct parameters.
Also add a packaging CI Pipeline, to make the pushing of the packages to the PyPI Index automatic. (in addition to more CI steps, like running Unit tests, reformatting code with black, sonar analysis, tagging releases, etc ...)
Will happily contribute.

Hi @MokhFn, thanks a lot for your suggestions and contributions! We'll try to review the issues you've raised and the PRs you've opened soon.
Just a note, please request reviews from @dimkarakostas and myself when opening a PR, to make sure we get notified about it :)

Thanks for reaching back @LadyChristina.
I will do as requested, whenever the PRs are ready for reviewing.
It's a habit to open the PR as soon as i start developing.


error AL0999: Internal error: 'One or more errors occurred.', Stack trace=unknown

Using AL Language 0.12.20065 with NAV 2018 CU05 we experience the following error when building the package.
error AL0999: Internal error: 'One or more errors occurred.', Stack trace=unknown
The package is dependent on another extension. There are several related issue describing the same problem, but none has the same resolution.
When removing the dependency (and code) the problem goes away.
It turns out that the problem is caused by the published events are defined as local. The compiler does not show this, thus we at first thought this was a platform problem. After updating the dependent extension and making the events non-local, the package builds and publishes as expected.
This issue is created should other run into the same problem.

Yes, "now" them should (or must) - I guess that Microsoft was not alliged on this back in early 2019 when the compiler was released


Clean up prompt management across the repo

Is your feature request related to a problem? Please describe.
We currently include the prompt as part of the code passed directly to Ray via settings. https://github.com/mozilla-ai/lumigator/blob/6daec13ac45838923b3fd9d92c3c12eec49a1579/lumigator/python/mzai/backend/backend/settings.py#L43, and we also pass directly in some cases. https://github.com/mozilla-ai/lumigator/blob/6daec13ac45838923b3fd9d92c3c12eec49a1579/lumigator/python/mzai/backend/backend/services/completions.py#L25
We need to test that this gets passed correctly when overridden at job input time, and offer the ability to test a single prompt per job and multiple prompts per experiment.
Describe the solution you'd like

Inventory of all places we currently pass prompt
Aggregate them all in a single class/template for easy reference
For models that have default summarization prompts (Mistral), pass those directly
Test that overridden prompts get passed correctly to the model

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

HI @veekaybee ,can create a PromptManager class to centralize prompt definitions or can store the prompt in json file , including defaults prompts .


fix for assign source button

closed: https://issues.redhat.com/browse/COST-1758
The assign sources button should be disabled until there is a change from the current config.

With the fix we can see the button is disabled util there is change from current state/config

With a source previously assigned

Codecov Report

Merging #2068 (2a6dfce) into master (a1020a8) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           master    #2068    +/-   ##
========================================
  Coverage   70.68%   70.68%
========================================
  Files         404      404
  Lines        7347     7347
  Branches     1573     1441   -132
========================================
  Hits         5193     5193
- Misses       2128     2130     +2
+ Partials       26       24     -2

Impacted Files
Coverage Δ

src/components/charts/costChart/costChart.tsx
9.37% <0.00%> (ø)

...omponents/charts/dailyCostChart/dailyCostChart.tsx
7.89% <0.00%> (ø)

Continue to review full report at Codecov.

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

Tested locally and noticed that the button remains enabled after deselecting the checkbox
The select-all toggle should update the button as well

https://user-images.githubusercontent.com/57504257/128567076-9aae6b3b-9081-4ea6-abb8-9085c909a44e.mov


Remove ostruct dependency from specs

Starting in Ruby 3.4, the following deprecation warning is printed when running the childprocess specs:

childprocess/spec/spec_helper.rb:14: warning: ostruct was loaded from the standard library, but will no longer be part of the default gems since Ruby 3.5.0. Add ostruct to your Gemfile or gemspec.

This commit fixes this warning by removing the dependency on the ostruct gem entirely, replacing it with a normal Struct.

Thanks! Test failures seem unrelated.

Thanks!

The failures are because ruby < 2.6 can't be build on macos-arm64, on macos-latest magically moved to arm64.
I'll improve the error message in setup-ruby for it, and make a PR here.

https://github.com/enkessler/childprocess/pull/197


[MTDSA-578] Add feature switching to individual tax year properties.

Modify the findTaxYearProperties method to exclude items that are not currently enabled.
Modify the FeatureSwitch class to include an override for isEnabled that takes a TaxYearPropertyType

Closing as it requires implementation change.


Added default TextStyle() to TextSpan constructor

Description
Added default TextStyle() to TextSpan constructor (here)

before
  const TextSpan({
    this.text,
    this.children,
    TextStyle? style,
    this.recognizer,
    this.semanticsLabel,
  }) : super(style: style);

after
  const TextSpan({
    this.text,
    this.children,
    TextStyle? style = const TextStyle(),
    this.recognizer,
    this.semanticsLabel,
  }) : super(style: style);

Related Issues
Fixes https://github.com/flutter/flutter/issues/66196
Tests
[edit] please see this comment
Checklist
Before you create this PR, confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I signed the [CLA].
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read [Handling breaking changes].

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

[ ] I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
[ ] I got input from the developer relations team, specifically from: Replace with the names of who gave advice
[ ] I wrote a migration guide: https://flutter.dev/go/breaking-changes-template Replace this with a link to a pull request that adds the migration guide to https://flutter.dev/docs/release/breaking-changes

Good catch, thanks for making a PR!
This definitely needs tests, could you add one?

I've added 2 tests here

verifies that a TextSpan() 's style by default is TextStyle()

  test('TextSpan should have non-null default TextStyle()', () {
    const TextSpan textSpan = TextSpan();
    expect(textSpan.style, const TextStyle());
  });

verifies that textScaleFactor affect TextSpan() when painted

test('TextSpan in TextPainter should scale according to textScaleFactor', () {
    const TextSpan textSpan = TextSpan(text: ' ');
    final TextPainter painterScaleOne = TextPainter(
      text: textSpan,
      textScaleFactor: 1,
      textDirection: TextDirection.ltr,
      maxLines: 1,
    );
    final TextPainter painterScaleDouble = TextPainter(
      text: textSpan,
      textScaleFactor: 2,
      textDirection: TextDirection.ltr,
      maxLines: 1,
    );
    painterScaleOne.layout();
    painterScaleDouble.layout();
    expect(painterScaleOne.size.width < painterScaleDouble.size.width, true);
  });

with the latest master

doctor
[✓] Flutter (Channel master, 1.22.0-10.0.pre.269, on Linux, locale en_US.UTF-8)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[✓] Chrome - develop for the web
[✓] Linux toolchain - develop for Linux desktop
[!] Android Studio (not installed)
[✓] Connected device (4 available)

! Doctor found issues in 1 category.

this code returns this output
withTextStyle: true
withoutTextStyle: false

Looks like this is making some existing tests fail. Can you take a look at those.
It's also not clear to me that just providing a default value is the right fix here. Did you investigate why the TestPainter is ignoring the scale factor when no style is provided?
/cc @GaryQian

Text widgets including TextSpan should inherit TextStyle from the parent TextSpan, if available, and then inherit from the theme. Setting a default here breaks this inheritance.
Ignoring of scale should be resolved in a different way.

I believe the problem lies at text_painter.dart:411 where we check for _text.style being null, and then fail to pass textScaleFactor.

https://github.com/flutter/flutter/pull/66375 Fixes the defaulting problem without setting a default TextStyle for all TextSpans. Thanks for your PR and narrowing down the problem area!

@GaryQian do you mean this change should be closed to defer to #66375?

Yes, I'll go ahead and close this now.


Create EN date model

@Jeasmine What we should do with this PR?

Maybe we show close it and redo it


Fix windows slaves

Fix windows configs on not first position..

@stephenashank Please confirm and merge if its something left after testing..


Add automated release process

This PR adds a GitHub Action workflow which automatically bumps the version in semantic versioning and creates a release in GitHub with the installable resource pack .zip-file and a SHA1 checksum file appended.
This only affects pushes that change the resource pack files inside the Sodium Translations folder.
Also, this updates the README to contain the current pack.png image for eyecandy reasons and also updates the instructions to the URL of the latest GitHub release.

When would it run? Would it attach to the commits by Crowdin?

It runs whenever there's a push to the main branch which changes something inside the Sodium Translations folder:
https://github.com/Madis0/sodium-fabric-translations/blob/5e1cdfdb6d024132e5c07d7bed2187e0b42b10f2/.github/workflows/build.yml#L3-L8
It doesn't matter who pushes to the main branch, as long as the commit hasn't been pushed by another GitHub Action workflow. This is a restriction by GitHub to prevent recursive workflow runs:
https://docs.github.com/en/actions/using-workflows/triggering-a-workflow#triggering-a-workflow-from-a-workflow

Alright. I changed the branch to l10n_main for now, to prevent having to reconfigure Crowdin. Let's see if this works...
On another note, could you also help with a CI to push those releases to CurseForge and Modrinth? I don't have projects there yet, but a template could help a lot.

Woo, it worked! I changed the version number manually after release, let's see if subsequent releases pick it up.

Awesome!


Bump golang.org/x/net

What this PR does / why we need it:
Bump golang.org/x/net
Which issue(s) this PR fixes:

Fixes #
Does this PR introduce a user-facing change?

NONE

Additional Notes for your reviewer:
Review Checklist:

[ ] Follows the developer guidelines
[ ] Relevant tests are added or updated
[ ] Relevant docs in this repo added or updated
[ ] Relevant carvel.dev docs added or updated in a separate PR and there's
a link to that PR
[ ] Code is at least as readable and maintainable as it was before this
change

Additional documentation e.g., Proposal, usage docs, etc.:

Closing as it is already done as part of kapp-controller bump PR.


Authentication section in readme is out of date

https://github.com/adswerve/target-bigquery#authentication
Let's update it. As of right now, we only support service account authentication.

Fixed, README updates merged into Master

Fixed, README updates merged into Master


Refactor SpringApplication to make ApplicationContext creation optionally non-reflective

I found I needed to access the applicationContextClass reflectively in order to reason about whether I needed to change the default. This was specifically when trying to avoid annotation-based @Configuration processing, but I guess there might be other reasons to want to do it. So adding a public accessor for SpringApplication.applicationContextClass would get me where I need to go.
Example code in Spring Init:
WebApplicationType type = getWebApplicationType(application, prepared.getEnvironment()); // assumptions made here
Class<?> contextType = getApplicationContextType(application); // reflective access here
if (type == WebApplicationType.NONE) {
	if (contextType == AnnotationConfigApplicationContext.class || contextType == null) {
		application.setApplicationContextClass(GenericApplicationContext.class);
	}
} else if (type == WebApplicationType.REACTIVE) {
	if (contextType == AnnotationConfigReactiveWebApplicationContext.class || contextType == null) {
		application.setApplicationContextClass(ReactiveWebServerApplicationContext.class);
	}
} else if (type == WebApplicationType.SERVLET) {
	if (contextType == AnnotationConfigServletWebServerApplicationContext.class || contextType == null) {
		application.setApplicationContextClass(ServletWebServerApplicationContext.class);
	}
}

Alternatively we could encapsulate the concern of mapping a WebApplicationType to a default ApplicationContext. Even better would be to optionally avoid reflective instantiation of the ApplicationContext together.

Wrong repo.


enhance of restore command

restore  command support REPLACE arg
Add cluster dump restore support

Hi , all. i start a new pull request at #1451 .
Closing now


⚠ twitter has degraded performance

In adb0b43, twitter (https://twitter.com/9renpoto) experienced degraded performance:

HTTP code: 200
Response time: 2900 ms

Resolved: twitter performance has improved in 5e6ed5c after 14 days, 17 hours, 4 minutes.


select 1+1

This
select 1+1  fails however
select (2 + 2) as sum -- Int  works
Fix SQL parser

fixed in devel branch


To torch 1.3.1

Move to torch 1.3.1

Thanks to nikolase90 for setting up actions with the pythonpackage.yml file.


Atom doesn't handle .gitignore/exclude files with trailing whitespace

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
Atom doesn't handle .gitignore/exclude files with trailing whitespace. This means that files that are followed by trailing whitespace in .gitignore/exclude always show up as new.
Obviously no one is going to create such files on purpose. I only got bitten by this due to Windows being Windows and adding a trailing whitespace when I innocently did a simple echo command. 😛
I checked the git-diff package first and saw that the actual calculation is implemented in Atom using the git-utils npm package, which I think uses libgit2. This might be an issue in libgit2 or it's usage in git-utils or it might be an issue in the way Atom is using git-utils.
Steps to Reproduce

Execute in a Windows console (Not Git Bash):

git init test-repo && cd test-repo
echo. > test.txt && echo. > test2.txt
echo test.txt > .gitignore
echo test2.txt >> .git/info/exclude

Open test-repo in Atom with the default VCS exclude settings.
Look at the tree view.

Expected behavior: test2.txt doesn't appear in the tree view or in fuzzy finder since it's ignored.
Actual behavior: test2.txt appears in the tree view as a new file and also appears in the fuzzy finder. But is ignored by standard Git (git status).
Reproduces how often: 100%
Versions
Atom    : 1.17.2
Electron: 1.3.15
Chrome  : 52.0.2743.82
Node    : 6.5.0

apm  1.17.0
npm  3.10.5
node 6.9.5 x64
python 2.7.13
git 2.13.0.windows.1
visual studio 2015

Windows 10.0.14393 x64

Thanks for the report!

Expected behavior: test2.txt doesn't appear in the tree view or in fuzzy finder since it's ignored.

Actual behavior: test2.txt appears in the tree view as a new file and also appears in the fuzzy finder.

You can hide VCS ignored files in the tree-view by enabling Settings > Packages > tree-view > Hide VCS Ignored Files.  If I enable that, test.txt and test2.txt aren't shown in the tree view.
But I'm unable to reproduce seeing test2.txt from fuzzy finder and test2.txt also isn't showing up as new for me on 1.17.2 and Windows 10.  I ran your commands from step 1 to create the test repo and then started Atom with atom --safe . but test2.txt doesn't show up in fuzzy finder unless I remove it from .git/info/exclude.

@rsese
It seems the real issue is different than what I thought it was... Try this in a cmd/Windows console (Not Git bash):
git init test-repo && cd test-repo
echo. > test.txt && echo. > test2.txt
echo test.txt > .gitignore
echo test2.txt >> .git/info/exclude

The entry in the .gitignore/exclude files ends up with a trailing space on my computer... (WTF Windows?!) Which works in Git but fails in Atom.
I will update the issue description/title.

Thanks @segevfiner :+1:  If I open .git/info/exclude in Atom and add a trailing space, I see the same behavior.  test2.txt isn't shown as ignored in the tree view anymore and it shows up in the fuzzy finder results.  If I remove the trailing space and the reload the window, ignoring works again.

Will be fixed by https://github.com/libgit2/libgit2/pull/4386 once a new
stable libgit2 is released with it and is pulled into Atom's git-utils.
בתאריך 7 ביונ' 2017 00:46, "Robert Sese"<EMAIL_ADDRESS>כתב:

Thanks @segevfiner https://github.com/segevfiner 👍 If I open
.git/info/exclude in Atom and add a trailing space, I see the same
behavior. test2.txt isn't shown as ignored in the tree view anymore and
it shows up in the fuzzy finder results. If I remove the trailing space and
the reload the window, ignoring works again.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/atom/atom/issues/14706#issuecomment-306626719, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AXlg_yCIXUg2FSJRnjzaZ24y-RD4SCoAks5sBciYgaJpZM4NuMYP
.


Demo for Machine Learning with Classical Shadows

Title: Learning ground state of 2D antiferromagnetic Heisenberg model
Summary: Explains how classical shadow formalism can be used with classical machine learning for predicting ground state properties of a Heisenberg model.
Relevant references: Provably efficient machine learning for quantum many-body problems, arXiv:2106.12627 (2021)

Hi @obliviateandsurrender, a note on references: the plan would be to add a CSS rule for how references are handled in the repository (see #452) and hence a ref like [[#preskill]_] would have to become [#preskill]_ once the relevant PR is merged.


Not compatible with latest accounts-ui

This package seem to be not compatible with the latest release of accounts-ui.
For example error messages are not displayed correct.

Hi all,
Having issues too, although I'm only recently getting familiar with the whole JS/Meteor/React world. I created a small project still very similar around the todos tutorial, and I got the sign-in/register page to display using react-router. However, the display misses a few things, and I can't sign up/in (see below)
Any advice welcome. In the meantime I'll fall back on the accounts-ui which seems more up-to-date (last update 7 days ago). Thanks for the good work overall though!


qt6.qtwebengine: correct how NIX_BUILD_CORES is propagated to the gn …

…ninja
port of https://github.com/NixOS/nixpkgs/pull/37889
should fix the current build failure on hydra.
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/why-is-qt6-qtwebengine-failing-ulimit-n/19539/15

The 16 cores limit is arbitrary and may not be required, just trying to play it safe.

Would it make sense to update the ninja setup hook in a future PR to append this to NINJAFLAGS instead of only doing it when it invokes it? That way it'd help for other projects which have cmake invoking ninja like this one.
https://github.com/NixOS/nixpkgs/blob/0badfc4936de7a895165ca170b422c443ca7e289/pkgs/development/tools/build-managers/ninja/setup-hook.sh#L8

Testing with nix build -j 1 --cores 1 .#qt6Packages.qtwebengine, at times it still used many cc instances for the first build step. The build step with 30k steps does seem to be fixed.
qtwebengine> [5/253] Performing build step for 'gn'
qtwebengine> [0/1] Generating gn
qtwebengine> ninja: Entering directory `/build/qtwebengine-everywhere-src-6.4.0/build/src/gn/Release'
qtwebengine> [1/195] CXX src/base/third_party/icu/icu_utf.o
...

This was the section that still used 32 cores.

Should we just merge and see what happens? People are hitting this a bunch now, and it'll only get worse as more things move to qt6.


Ensure the grid layout span is never below 1

Task/Issue URL: https://app.asana.com/0/488551667048375/1207235055389858/f
Description
Ensure grid layout span cannot be below 1, otherwise it'll crash
Steps to test this PR
Code review

#4515  👈
develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @aitorvs and the rest of your teammates on  Graphite


[BEAM-12051] fix target/go-licenses: no such file or directory

COPY target/LICENSE target/go-licenses/* /opt/apache/beam/third_party_licenses/golang/ doesn't work on macOS when docker-pull-licenses is not set.
#7 [3/8] ADD target/linux_amd64/boot /opt/apache/beam/
#7 sha256:ba5950ec9b4d3dd4ccf61c67169a80c60727f4a8c4cdcca9487ba724d4521925
#7 DONE 0.1s

#8 [4/8] COPY target/LICENSE /opt/apache/beam/
#8 sha256:c985e805fc702262e6a25884ffdd287334450a61b32213cecd7431453084a710
#8 DONE 0.0s

#9 [5/8] COPY target/NOTICE /opt/apache/beam/
#9 sha256:657942f798562ea47d4f0899783382ae2f7bda6c9a185dc7e0ec8142efb7281b
#9 DONE 0.0s

#10 [6/8] COPY target/LICENSE target/go-licenses/* /opt/apache/beam/third_party_licenses/golang/
#10 sha256:e72eaf77fc75ad38a81071b0cb703717258889925f68ad811f4412d7145f2ea6
#10 ERROR: lstat /var/lib/docker/tmp/buildkit-mount721990318/target/go-licenses: no such file or directory
------
 > [6/8] COPY target/LICENSE target/go-licenses/* /opt/apache/beam/third_party_licenses/golang/:
------
lstat /var/lib/docker/tmp/buildkit-mount721990318/target/go-licenses: no such file or directory

> Task :sdks:go:container:docker FAILED

I guess the semantics of COPY command is different between Linux and macOS docker implementation.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @emilymye

Run java precommit


Bubble up errors

I see...makes sense why that was causing the problem, a schema-validation error of a child gets caught just like any other error, and converted to warn if applicable.
But, doesn't something need to set force?
Also, more broadly, doesn't that basically make policy="warn" on SubRecords useless, since the only type of error that will actually get "warned" is the trivial "this is not a dict" one? Maybe that's fine, because the alternative is even worse. But I can definitely see a case where you would genuinely not care if a SubRecord failed because some otherwise-critical field failed. E.g
MyType = SubRecordType({
    "stable_field": SubRecord({
    }, validation_policy="error"),
    "unstable_field": SubRecord({
         "certificate_chain": ListOf(Certificate())
    }, validation_policy="warn")
}, validation_policy="error")

there, it would make sense for e.g. certificate.subject to have validation_policy="error"...but we just don't care if unstable_field fails for whatever reason.
So maybe we need another policy type? Something like the inverse of force that gets set on the parent SubRecord.

Also, more broadly, doesn't that basically make policy="warn" on SubRecords useless, since the only type of error that will actually get "warned" is the trivial "this is not a dict" one?

Yes, that, as well as unknown sub keys.

👍


[Question] How to deploy botframework on an intranet ?

Hi !
Currently, i've a client accessing the bot framework using directline. So, the bot framework is deployed in Azure. What i want to do is "disconnect" the bot framework from Azure and deploy it locally, on an intranet.  Just for security reason. How can i do that ?
Thanks.

The Bot Framework works with bots deployed on any cloud hosting service, as long as you have an internet-accessible endpoint and a valid HTTPS cert.
The Bot Framework requires that the x.509v3 certificate exposed by your endpoint be current and valid. Most of the checks for "current and valid" are standard checks for server certs: the CN must match the hostname, it must not be expired, it must not be listed in a CRL, it must have the correct set of EKUs, etc.
Most importantly, your cert must chain to a root certificate authority trusted by Microsoft. The latest list of these CAs is available here: http://social.technet.microsoft.com/wiki/contents/articles/31634.microsoft-trusted-root-certificate-program-participants-v-2016-april.aspx
For more information on deploying your bot, see: https://docs.microsoft.com/en-us/bot-framework/deploy-bot-overview
Relates to:
https://stackoverflow.com/questions/40888489/bot-framework-without-azure-possible
https://stackoverflow.com/questions/44558760/deploy-bot-in-local-iis-and-incle-it-in-custom-chat-in-a-webpage/44571251#44571251

Hi,
Thanks for the answer, but after some research and i've some questions.

If i deploy my bot on another cloud hosting service, the bot will still on Azure. Just the connector will be on my cloud, right ?

Can i use the bot framework on a local network ? All channels (directline/webchat...) will not be available, but i just want to know if there is a way to run a code using the botframework on a local network and access it from a client using a "custom directline" that i can create. To resume : Use the botframework without publish it on Azure.

Thanks.

#1 - You can deploy your bot to any cloud service as long as it has a valid SSL certificate and supports HTTPS protocol. Your bot will only be on Azure if you deploy it there.
#2 - You can can expose your bot's API endpoint on your local network or to the public web using NGROK tool. For more information, see: https://ngrok.com/

I guess the short answer is 'NO' you cannot put it on your intranet if you want to keep everything local.


height

when the height changes the background still shows up and the bottomnavbar doest stick to the bottom.

be more specific... whose height??


perf: use -o2 optimization for starlingmonkey

We're in the process of investigating performance differences on StarlingMonkey, and this is one obvious difference between js-compute-runtime and StarlingMonkey that might be worth starting with.
I'd like to roll this out into the 3.24 release today to test it out more widely, and then use that information to inform further investigation here.

Closing, as we have another solution here for investigation.


Fix libmesos

Updated the libmesos version to 1.8.7-1.0.2-2 in a couple more places.
Fixed the setting of LD_LIBRARY_PATH

ClusterTaskOfferRequirementProviderTest error. I'll fix it.


Corrects rendering of png's with colors having alpha values

When a gif is rendered with png images having some alpha values, these colors will get mixed with the black background giving unusual output. As it is shown in #45, the gif won't render perfectly.
The solution to this would be to use a {copy: true} option on png images with a background color of white. for the gif. But this won't work as well because in the getImageData function setFill property of canvas is used which doesn't set the desired fill color instead fillStyle property should be used.

Thanks, can you rebase this without the build?

@jnordberg rebased.

Thanks!


C API Docs: Clarify that IPL_PLACEMENT_OCTREE is not supported currently

http://steamcommunity.com/app/596420/discussions/0/3182216552773622208/

Resolved in 2.0-beta.11 release.


setTypeface() Doesn't WORK !!!

Please Add It I Need It

bug fix
MaterialDesign project - Button class
TextView textButton; → protected TextView textButton;
MaterialDesign project - ButtonRectangle class
TextView textButton; → //TextView textButton;
comment out
ButtonRectangle variable name in the class exists same thing. How can that be overridden, because setText processing is carried out in the Button class, it falls in the null pointer because you can not refer to an instance of the child class.
I'm sorry the poor English


Modify the unix script

Modifies the line containing CLASSPATH= in generated unix script file and add entries for

$APP_HOME/ext-lib/* - To be used to add extra jars to classpath
$APP_HOME/config - To be used to add custom application.conf

This PR is for issue #3057

Updated docs as per feedback


SVault daemon for server side support

Needs additional executable for server side daemon to support #6.

Closing for now.


[Maybe Issue] Maybe wrong word in 'api/commands/pools_cli.py:151'

Description
In api/commands/pools_cli.py:151 there is this phrase:

Successfully left pool, switching to self plotting. Please wait a few minutes or more to complete. DO NOT immediately re-submit your request. View the log for details.

Argument
Leaving a pool leads to self pooling. And regardless of being in a pool or not, you always plot by yourself for yourself.
So, I think that is not appropriate to use  self plotting in the first phrase above.
Proposed solution
Change the first phrase above to:

Successfully left pool, switching to self pooling.

Thanks.  Fixed in development stream.


nonblocking connect

It would be very useful to have a way to do non-blocking connect. Socket2's existing code in connect_timeout()/poll_connect() already implements 99% of this. All that is needed is for body of the loop in poll_connect() to be exposed as a separate function that can be used to check if the connection has been established.

I'm afraid socket2 isn't the library to do this in, a non-blocking connect isn't as simple as it seems see https://github.com/Thomasdezeeuw/heph/blob/5dbc14b32d12241e48d4afc022b8bc617f5a9ce8/rt/src/net/tcp/stream.rs#L562-L583 for some more information. You can try Mio for this (happen to have the same maintainer ;) )

Hi @Thomasdezeeuw can you clarify? It seems to me that the code already implements nonblocking connect inside connect_timeout(), the functionality is just not exported in a reusable way.

Hi @Thomasdezeeuw can you clarify? It seems to me that the code already implements nonblocking connect inside connect_timeout(), the functionality is just not exported in a reusable way.

I reluctantly accepted connect_timeout back in https://github.com/rust-lang/socket2/issues/190 / https://github.com/rust-lang/socket2/pull/194. It's not the goals of socket2 to support non-blocking I/O, other libraries already exists for that and they do a good job at it. I know that because I maintain one. Supporting non-blocking connect isn't as easy as it seems when you want to give back control to the user. connect_timeout is simple because it can still block by calling poll(2)/WSAPoll, it's not really non-blocking.

I'm not sure what you are getting at when you say "it isn't as simple as it seems". If the code in connect_timeout() works correctly then why shouldn't it be exposed to the user to allow checking for completion of the connection?

I've stated this before and I'll state it for the last time: socket2 is not the place for non-blocking I/O.
Doing non-blocking I/O effectively is not easy. Socket2 however can help in doing non-blocking I/O as most socket related system calls are wrapped. You can call socket.set_nonblocking(true) and then do the poll(2) calls yourself. Or you can use another library for that. Socket2 isn't going to do it, it's simply out of scope for the library.

You've stated 3 times that "it's not easy", but I don't understand what relevance this has. The supposedly difficult code is already written in the library and therefore the maintenance burden is already present?
Can you explain how it makes more sense for users to copy-paste the existing code out of the lib (for each platform) than simply providing a pub fn to the existing logic that is already being maintained? That is what I have already done BTW since I needed this right away, but it's obviously less than ideal for many reasons.


Writing cheeps is an essential part of a service such as Chirp, and is expected by users to add their own messages to the message boards.

Criteria for success:
A user can input a message and share it on the public timeline


Downloads not working on tv.nrk.no

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like this: [x])
Use the Preview tab to see what your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2018.07.04. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2018.07.04

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones
[x] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[x] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add the -v flag to your command line you run youtube-dl with (youtube-dl -v <your command line>), copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
$ youtube-dl -v https://tv.nrk.no/serie/backstage/sesong/1/episode/8
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'-v', u'https://tv.nrk.no/serie/backstage/sesong/1/episode/8']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2018.07.04
[debug] Python version 2.7.10 (CPython) - Darwin-17.6.0-x86_64-i386-64bit
[debug] exe versions: none
[debug] Proxy map: {}
[NRKTVSeries] backstage: Downloading webpage
[download] Downloading playlist: NRK TV – Backstage
[NRKTVSeries] playlist NRK TV – Backstage: Collected 0 video ids (downloading 0 of them)
[download] Finished downloading playlist: NRK TV – Backstage

If the purpose of this issue is a site support request please provide all kinds of example URLs support for which should be included (replace following example URLs by yours):

Single video: https://tv.nrk.no/serie/backstage/sesong/1/episode/8

Description of your issue, suggested solution and other information
It seems like they have changed their URLs, they used to include some sort of ID before, but now its all text for each episode. That might be the cause of the problem.

hello. i have the same issues. how can I fix this?

It still works by manually reconstructing the old-style URL. View page HTML source and search for the @id value in the meta summary for the episode:
New style URL (not working as from bug report):
https://tv.nrk.no/serie/backstage/sesong/1/episode/8
Old style URL (still works with youtube-dl, but will redirect to new style URL in a browser):
https://tv.nrk.no/serie/backstage/MSUI14000816/sesong-1/episode-8
Also note that not all series are affected by the redesign. Visiting some series from the archives show pages still using old visual layout with all episode URLs working as expected (at least for now). See for instance https://tv.nrk.no/serie/glimt-av-norge.

Yep, they did a redesign. Hope a fix will come within a week or so, as I use this all the time.


Use entrySet instead of keySet when iterating over the whole map

PR Description
This replaces keySet with entrySet for loops that iterate over the whole map.
It is more efficient to use an iterator on the entrySet of the map, avoiding the extra HashMap.get(key) lookup.
See: https://stackoverflow.com/a/3870093 & https://stackoverflow.com/a/38116169
Documentation

[x] I thought about documentation and added the doc-change-required label to this PR if updates are required.

Changelog

[x] I thought about adding a changelog entry, and added one if I deemed necessary.

These were identified using Facebook's Infer static analysis tool. The Inefficient Keyset Iterator issue type.

I came to the same conclusion about Infer. Neat tool but lots of false negatives.


rosh_robot_plugins: 1.0.2-0 in 'jade/distribution.yaml' [bloom]

Increasing version of package(s) in repository rosh_robot_plugins to 1.0.2-0:

upstream repository: https://github.com/OSUrobotics/rosh_robot_plugins.git
release repository: https://github.com/OSUrobotics/rosh_robot_plugins-release.git
distro file: jade/distribution.yaml
bloom version: 0.5.20
previous version for package: null

rosh_common

No changes

rosh_geometry
* Prevent beginning of tf frame names from being lost in ipython tab completion
* Fix error creating QuaternionStamped
* Contributors: Dan Lazewatsky

rosh_robot

No changes

rosh_robot_plugins
* fix maintainer
* Remove "rosh" run depend
  Fixes wiki package header for this and rosh
* Contributors: Dan Lazewatsky

@dlaz You'll have to rebase this pr or close it an open a new one (just run the same bloom command with an add -p option). This happens sometimes when two subsequent pr's touch the same part of the file and an automatic merge cannot be done.

Thanks @wjwwood. See #10039.


openpgp: invalid argument: no valid signing keys after "pgp select"

For daily use my keyring has the original signing subkey removed and I only physically mount that master key whenever I need to sign/revoke/cert etc (one of the pain points keybase is solving so nicely). While trying to link my PGP key to keybase i mounted the master keypair and set the GNUPGHOME env variable to the directory containing the master key which has the signing key included. Running gpg -K afterwards confirms the key status as "sec" instead of "sec#" with a flag of "SC". I then run keybase pgp select which prompts me for my key (no "Created" displayed) and my passphrase which I confirm. This process then fails with error:  ERROR key generation error: openpgp: invalid argument: no valid signing key. I suspect something wrong on my side but would appreciate any insight on getting this to work.

keybase version 1.0.11-0
gpg (GnuPG/MacGPG2) 2.0.28
libgcrypt 1.6.3

keybase -d debug output shortly before the error but after the key and passphrase confirmation:
Failure in intermediate SignJson()
Delegator.Run() -> ERROR: openpgp: invalid argument: no valid signing keys
PGPKeyImportEngine::Run
RunEngine(PGPKeyImportEngine) -> ERROR: openpgp: invalid argument: no valid signing keys
RunEngine(GPGImportKeyEngine) -> ERROR: key generation error: openpgp: invalid argument: no valid signing keys

It could be your signing subkey is expired.  Can you post me your public key?  Also, gpg -K | gpg --list-packets might be helpful too, though that's slightly more revealing --- it describes how your secret keys are layed out, but obviously doesn't display any secret data.

Thank you for the prompt response. My signing key was expired before i started using keybase but during the process i updated the expiration dates (as far i understood) and published the new key.
The public key can be found at 5C558AAC.

gpg --export-secret-key | gpg --list-packets

:secret key packet:
	version 4, algo 1, created<PHONE_NUMBER>, expires 0
	skey[0]: [2048 bits]
	skey[1]: [17 bits]
	iter+salt S2K, algo: 3, SHA1 protection, hash: 2, salt: 6dc46084f6de5e35
	protect count: 8912896 (209)
	protect IV:  9b ec 61 b8 0b a2 77 f7
	encrypted stuff follows
	keyid: 276B98015C558AAC
:user ID packet: "Manuel Kreutz<EMAIL_ADDRESS>:signature packet: algo 1, keyid 276B98015C558AAC
	version 4, created<PHONE_NUMBER>, md5len 0, sigclass 0x13
	digest algo 10, begin of digest 17 c0
	hashed subpkt 27 len 1 (key flags: 03)
	hashed subpkt 30 len 1 (features: 01)
	hashed subpkt 23 len 1 (key server preferences: 80)
	hashed subpkt 11 len 4 (pref-sym-algos: 9 8 7 3)
	hashed subpkt 21 len 4 (pref-hash-algos: 10 9 8 11)
	hashed subpkt 22 len 4 (pref-zip-algos: 2 3 1 0)
	hashed subpkt 25 len 1 (primary user ID)
	hashed subpkt 2 len 4 (sig created 2016-02-10)
	hashed subpkt 9 len 4 (key expires after 3y24d17h53m)
	subpkt 16 len 8 (issuer key ID 276B98015C558AAC)
	data: [2046 bits]
:secret sub key packet:
	version 4, algo 1, created<PHONE_NUMBER>, expires 0
	skey[0]: [4096 bits]
	skey[1]: [17 bits]
	iter+salt S2K, algo: 3, SHA1 protection, hash: 2, salt: 6efdb788b7c348d4
	protect count: 8388608 (208)
	protect IV:  2d 28 59 65 b8 4c 44 45
	encrypted stuff follows
	keyid: 5BA9C90518F7709D
:signature packet: algo 1, keyid 276B98015C558AAC
	version 4, created<PHONE_NUMBER>, md5len 0, sigclass 0x18
	digest algo 10, begin of digest 36 07
	hashed subpkt 27 len 1 (key flags: 0C)
	hashed subpkt 2 len 4 (sig created 2016-02-10)
	hashed subpkt 9 len 4 (key expires after 2y361d14h13m)
	subpkt 16 len 8 (issuer key ID 276B98015C558AAC)
	data: [2047 bits]
:secret sub key packet:
	version 4, algo 1, created<PHONE_NUMBER>, expires 0
	skey[0]: [4096 bits]
	skey[1]: [17 bits]
	iter+salt S2K, algo: 3, SHA1 protection, hash: 2, salt: 319fa01a3931767d
	protect count: 8388608 (208)
	protect IV:  be be a9 30 02 75 74 a1
	encrypted stuff follows
	keyid: 159DD63FD1CD3CD1
:signature packet: algo 1, keyid 276B98015C558AAC
	version 4, created<PHONE_NUMBER>, md5len 0, sigclass 0x18
	digest algo 10, begin of digest 71 66
	hashed subpkt 2 len 4 (sig created 2014-02-13)
	hashed subpkt 27 len 1 (key flags: 0C)
	hashed subpkt 9 len 4 (key expires after 321d0h0m)
	subpkt 16 len 8 (issuer key ID 276B98015C558AAC)
	data: [2044 bits]

Oh, your signing subkey is expired:
:secret sub key packet:
    version 4, algo 1, created<PHONE_NUMBER>, expires 0
    skey[0]: [4096 bits]
    skey[1]: [17 bits]
    iter+salt S2K, algo: 3, SHA1 protection, hash: 2, salt: 319fa01a3931767d
    protect count: 8388608 (208)
    protect IV:  be be a9 30 02 75 74 a1
    encrypted stuff follows
    keyid: 159DD63FD1CD3CD1
:signature packet: algo 1, keyid 276B98015C558AAC
    version 4, created<PHONE_NUMBER>, md5len 0, sigclass 0x18
    digest algo 10, begin of digest 71 66
    hashed subpkt 2 len 4 (sig created 2014-02-13)
    hashed subpkt 27 len 1 (key flags: 0C)
    hashed subpkt 9 len 4 (key expires after 321d0h0m)
    subpkt 16 len 8 (issuer key ID 276B98015C558AAC)
    data: [2044 bits]

See directions here on how to extend your signing subkey: https://github.com/keybase/keybase-issues/issues/2072

Oh! You don't have a signing subkey.  You only have an encryption subkey.  Though you can sign with your primary, it's offline.

So my best guess is that the forked background service didn't get the setting for GNUPGHOME, which we do respect.  Maybe try:
keybase ctl stop # stop the background process
GNUPGHOME=/blarg/foo keybase --standalone pgp select

I haven't tried this before, so it may or may not work.
Thanks for this well-documented bug report!

That worked perfectly :+1: Thank you!


Scheduler rework -- part three, inventory and locking

Based on #105
Regarding the locking part -- to the best of my knowledge, the only part that needs locking is authentication (and artifact_name as @lluiscampos pointed out) which is out of scope of this PR.

Okey, but to have the locking mechanism in place is part of your current task? Or will you create a follow-up task?

There are mutexes available for both POSIX and Zephyr so all the building blocks are there. Or am I missing something?

Okey, but to have the locking mechanism in place is part of your current task? Or will you create a follow-up task?

There are mutexes available for both POSIX and Zephyr so all the building blocks are there. Or am I missing something?

Perfect! (I didn't check it)


Error:Execution failed for task ':app:transformDexArchiveWithExternalLibsDexMergerForDebug'. > com.android.builder.dexing.DexArchiveMergerException: Unable to merge dex

i have this error.. i cant run my app.

This is dependency clash / dev environment problem, not something I could help you with.


[AutoPR eventhub/resource-manager] typo: eventhub/resource-manager/Microsoft.EventHub/EventHub

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/4553

(message created by the CI based on PR content)

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/3873


WebDriverException on clean install

I try to run simple test from /test directory and I get an error like
~/needle/tests$ nosetests3 test_driver.py --with-save-baseline
...EE
======================================================================
ERROR: test_get_dimensions (tests.test_driver.TestWebElement)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/damian/needle/tests/test_driver.py", line 47, in test_get_dimensions
    self.assertEqual(e.get_dimensions(), {
  File "/usr/local/lib/python3.5/dist-packages/needle/driver.py", line 44, in get_dimensions
    location = self.location
  File "/home/damian/.local/lib/python3.5/site-packages/selenium/webdriver/remote/webelement.py", line 402, in location
    old_loc = self._execute(Command.GET_ELEMENT_LOCATION)['value']
  File "/home/damian/.local/lib/python3.5/site-packages/selenium/webdriver/remote/webelement.py", line 494, in _execute
    return self._parent.execute(command, params)
  File "/home/damian/.local/lib/python3.5/site-packages/selenium/webdriver/remote/webdriver.py", line 236, in execute
    self.error_handler.check_response(response)
  File "/home/damian/.local/lib/python3.5/site-packages/selenium/webdriver/remote/errorhandler.py", line 192, in check_response
    raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.WebDriverException: Message: GET /session/cd8c0384-21b8-49a4-8493-e7dd682e33cf/element/85d8038e-6e97-4c88-b62f-672cca2f95be/location did not match a known command

To me this looks like a potential bug with Selenium itself. Which version of Selenium are you using, and have you tried upgrading to the latest version?

Selenium 3.0.2 version
Firefox in 50.1
python 2.7.12 and 3.5.2
nosetest 1.3.7
ubuntu 16.04 on virtual box

Thanks. My gut feeling is that it's a bug with the Selenium package with regard to Firefox. I haven't had a chance to test firsthand yet though. On a side note, it'd be useful to add Firefox to the Travis test matrix — I've created a separate issue for that in #60.

this is not going to work in firefox using geckodriver, since the Actions class is yet to be implemented.  I think the only temporary solution would be to use selenium 2.x

Ran into this issue, this is related to a bug with Geckodriver and Selenium:
https://github.com/mozilla/geckodriver/issues/548
https://github.com/mozilla/geckodriver/issues/159
A temporary fix for this issue is to downgrade to Selenium 2.53.6 and firefox 45.6. There may be other version combinations that work but in the meantime these have worked for me.

This should be fixed with the code now in master (support was added for Geckodriver and recent Firefox versions).


Fix the squoosh for TextElide rendering

Fixes: #1406
The third line should be cut off. Max line in this case is Int.MAX and is not gating the max lines being drawn. Using canvas.clip to clip to the computed height plus extra space for shadow and stroke.

Looking at the Alignment test, it looks like the "28px Line Height C" text on the bottom right has been improved. So now it calculates the max lines based off of layout size, whereas before it would wrap -- is that correct? I looked at the non-squoosh version and it looks like it also wraps, but doesn't render the second line.

Do you know why Text-Elide_SQUOOSH_compare.png looks like it got a lot wider?

Do you know why Text-Elide_SQUOOSH_compare.png looks like it got a lot wider?

No. Not really.
It seems the screenshot captures the UI outside of the DesignDoc. @timothyfroehlich Tim, do you know if it is expected? I added some UI elements below the figma design in the TextElideTest.

Do you know why Text-Elide_SQUOOSH_compare.png looks like it got a lot wider?

No. Not really.
It seems the screenshot captures the UI outside of the DesignDoc. @timothyfroehlich Tim, do you know if it is expected? I added some UI elements below the figma design in the TextElideTest.

I think I know what's going on, will dig in soon.

@yiqunw700 try cherry-picking https://github.com/google/automotive-design-compose/pull/1547. I changed the way it captures the images to only capture the DesignComposable instead of the whole test composable.


animated background

What is your question?
how do i add an animated background (0.5.2h)

ym in the song or menus

if for song/stage but lua you can try check the wiki


i18n(ko-KR): update authentication.mdx

Description (required)

update authentication.mdx
#8908

Related issues & labels (optional)

Closes #
Suggested label:

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

ko
guides/authentication.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Objects with zero mass disappear on collision

When an object with zero mass is colliding with anything else it will disappear due to its position and velocity becoming (NaN, NaN).

Fixed by making the mass have a minimum of 0.01


Fix .travis.yml

Add fixes from documentation update here as well

It looks like this is only the fix to the repo's .travis.yml =/

Alright, going to land this and re-run the other PR

This has been merged/released in 1.0.3.


grpc does not use SOCK_CLOEXEC

Reopening #34114. It is a clear race condition caused by this library not following well-established and well-documented Linux best practices.

I have been trying to read through the C++ code but it is very complicated. From what I can tell, this library does not use SOCK_CLOEXEC except as a parameter to accept4. I do see a reference to FD_CLOEXEC, but this is racy and should only be used on platforms that don't support SOCK_CLOEXEC.
See the description of O_CLOEXEC for why SOCK_CLOEXEC is needed instead of FD_CLOEXEC. https://man7.org/linux/man-pages/man2/open.2.html
Please fix all calls to socket to properly pass SOCK_CLOEXEC on platforms that support it (namely, Linux). (And conversely, don't bother with FD_CLOEXEC on such platforms.)

Our team does not prioritize fixing this at this time but we are open to discussing the external contributions.


[ExpertView] Containers - show logs

Add "show logs" column to Containers expert view, which will redirect to Logs with correct filters

tarnas14 commented:
we could prepare grafana dashboards for each container and have a link to that here


Fix QuantumCircuit.compose with Index exprs

Summary
This was an oversight in d6c74c265 (gh-12310), where an ExprVisitor was missed in the testing.

Details and comments
No release note because it's fixing an unreleased bug.  I did another check for ExprVisitor classes in Qiskit, and all of them appear to be updated.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
22 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.03%) to 89.605%

Files with Coverage Reduction
New Missed Lines
%

crates/qasm2/src/lex.rs
4
91.86%

crates/qasm2/src/parse.rs
18
95.77%

Totals

Change from base Build<PHONE_NUMBER>:
-0.03%

Covered Lines:
62187

Relevant Lines:
69401

💛  - Coveralls


Bullet match

Bullet match challenge with solution.

Maybe a note should be added that mirroring is not allowed?


print: Add print styles targeted at topics.

This adds some essential print styles via a new print.css stylesheet to ensure better printing especially of Zulip topics.
There are still things that could be improved, given enough time. In particular, there are slight differences when printing from light vs. dark mode; some additional work could be done on borders and things, but this PR is really about trying to faithfully present the content of topics and their messages as faithfully and accessibly as possible.
CZO Discussion
Screenshots and screen captures:

Before, Emoji (invisible)
After

Before, Long Posts
After, Long Posts (print in their expanded form regardless of their state on screen)

Before, Links
After, Links (only links beginning with http are presented parenthetically after the link text)

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

This seems like a great start, merged, thanks @karlstolley! I love the comments.
There's probably a follow-up to be done after testing in the dark theme -- I'm guessing that will prove to have issues with the font colors that need to be managed.


[core-client-rest] Idea: Add discriminator for body shape

Packages impacted by this PR

@azure-rest/core-client

Describe the problem that is addressed by this PR
At the moment, core-client-rest tries to infer what kind of body the caller is trying to send based on a few arbitrary rules based on

the content-type header
the actual type of the body (e.g. if the body is a stream, just forward it, otherwise if the content type is multipart/form-data, check if it looks like form data and then handle it appropriately, etc...)
...among others

This is okay in the general case but sometimes could lead to issues when we can't conclusively determine the body type. For example, what if the content type is multipart/form-data, but we need finer control over the multipart shape than FormDataMap provides, e.g. to set the boundary or to set multipart headers using MultipartRequestBody? In this case there is no way to be certain based on just the shape of the request body what the caller's intent is.
This PR proposes an 'escape hatch' discriminator property (tentatively called bodyKind) which would allow users or the generated code to specify explicitly what kind of request body they are passing in and how they would like it to be handled. At the moment, this discriminator has three possible values:

when left undefined, the original logic (inferring based on what is passed in and the content-type header) is used. I expect this to be fine in the majority of cases
when set to formData, the body must be a FormDataMap which will then be eventually passed to the formData property on PipelineRequest
when set to multipart, the body must be a MultipartRequestBody which will then be passed to the multipartBody property on PipelineRequest.

I could envision other values being added to this list as needed. For example, maybe we would want a passthrough value which tells the client that the body value should be passed to core-rest-pipeline directly without any special handling.

API change check
APIView has identified API level changes in this PR and created following API reviews.
@azure-rest/core-client


Can't get balance

I always get zero balance even though my wallet still have money, a few days ago it still shows the balance, anyone know what the problem is?

@trien-tran Looks like the change of RPC rpc.mainnet.sui.io leads to CORS forbiddance on the browser. Will look at this problem and fix it soon

@trien-tran I've confirmed with Sui team that there is a bug of RPC where the prefix of Sui coin type changed from 0x2 to 0x0000...2, which led to the failure to get the accurate balance. It should be fixed in the next 1.1.1 hotfix version of Sui Node, please wait until they fix it.

how fix

@trien-tran @ser25 Now the Sui RPC has fixed the issue. Everything should work well now


Text on proof automation

See #920
The current structure (and even title modification) are just suggestions, happy to discuss them in this PR of course!
Closes #920

I have directly fixed a bunch of typos I have found together with all those found by @vlad902 and resolved the relevant review comments.

I think I've addressed all the suggestions now. Happy to have either a second round of reviews/suggestions or merge this and continue expanding with more PRs.

I think it's good to merge for now.  If anyone wants to work on the section more, they can say so in the Zulip chat, and I'll open a new issue for it.


As a user, I want to see the correct favicon and title.

Correct the title page and favicon on the tab
Description
Bug Summary:
The title page and the favicon on the tab are not displaying correctly. The title currently reads "Vite + React + TS" instead of the appropriate project name, and the CFIA favicon is missing on the browser tab.
Steps to Reproduce:

Open the browser and go to fertiscan.inspection.alpha.canada.ca.
Observe the tab title and small favicon/logo

Expected Behavior:
The tab should display the correct title relevant to the project and the favicon should be visible on the tab.

duplicate of #162 and merged in #164


Add check for user path existence

Is this what you want in issue #1  ?
Looks like it's working this way. It handles not existing files and also invalid paths.

With the information I provided yes, it will help me. Thank you for the contribution.
Note: In the long term, Part of my CSharp learning, I will look for a solution using try-catch-finally blocks.
Here YouTube Ref found:
Handling Exceptions in C# - When to catch them
C# Exception Handling Best Practices You Need to Know


Fixes #1700 - docs for ip access rules

Coverage: 93.976%. Remained the same when pulling f6a14e86e23a1cf9476b8cbd7c418aafff00fd20 on cody-doc-ip-access-rules into f7461fb1e11af99ab058492e5aed8d64bf9fd3be on main.


Fix the CLI --diff-unified flag.

Minimist doesn't convert CLI args to camel case, which was preventing the --diff-unified flag from working.

thanks! it would take me forever to realize this was broken since I only use the default --diff

No problem. Thanks for merging so quickly!

just published v0.7.2 that includes this fix,. thanks once again.


Issue using with latest F*

Hi team,
I'm trying to use vale for a project. Unfortunately, I've run into a problem: I can't make F* build at 9f2cb7e2c9934b0134b46d5c83a5a5c074d8463b for some reason, although I can build more recent commits. So, using F* at version 9f2cb7e2c9934b0134b46d5c83a5a5c074d8463b seems like a non-option for new users.
But recent versions of F* do not work with Vale. In particular, when I run scons --FSTAR --FSTAR-PATH=[path to my fstar] --FSTAR-MY-VERSION, I see this error:
##### Verification error
Printing contents of obj/fstar/specs/defs/Words.Two_s.fsti.verified.stderr #####
fstar/specs/defs/Words.Two_s.fsti(27,6-27,17): (Error 114) Type of pattern (Words_s.two (Words_s.natN (Words_s.pow2_norm size))) does not match type of scrutinee (Words_s.two (Words_s.natN (match size with
        | 0 -> 1
        | _ -> 2 * Prims.pow2 (size - 1)))); parameter Words_s.natN (Words_s.pow2_norm size) <> parameter Words_s.natN (match size with
    | 0 -> 1
    | _ -> 2 * Prims.pow2 (size - 1))
1 error was reported (see above)

I looked deeper into this issue. The problem is in this definition:
unfold
let two_to_nat_unfold (size:nat) (x:two (natN (pow2_norm size))) : natN (pow2_norm (2 * size)) =
  let n1 = pow2_norm size in
  let n2 = pow2_norm (2 * size) in
  let Mktwo x0 x1 = x in
  int_to_natN n2 (x0 + x1 * n1)

The types seem correct to me. I tried adding fuel (#push-options "--max_fuel 256") in a fruitless attempt to get F* to normalize, but that didn't help. I noticed this recent PR in F* -- at a first glance, I think it's possible this introduced the issue. But I'm not an expert, so take it with a grain of salt.

Ok, I updated to the latest F* version, so hopefully it should work now.


Fix unstable test with set job assignee

Motivation and context

My current suggestion that test case_4_assign_task_job_users.js fails because of two consecutive interceps in one it
cy.intercept('PATCH', '/api/jobs/**').as('patchJobAssignee');

I couldn't reproduce the issue locally, will try to test it several times on CI
How has this been tested?

Checklist

[ ] I submit my changes into the develop branch
[ ] I have added a description of my changes into the CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (see GitHub docs)
[ ] I have increased versions of npm packages if it is necessary
(cvat-canvas,
cvat-core,
cvat-data and
cvat-ui)

License

[ ] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.

/check

@bsekachev
I think this patch fixes instability in case_4_assign_task_job_users.js with 4 runs without fail in actions_users pipeline

/check

@bsekachev  /check command runs tests on develop branch without my changes :disappointed:


No captcha image - can't login

Describe the bug
HA notification asks me to configure the addon. Required captcha never displays
To Reproduce
Steps to reproduce the behavior

Click Notifications
Click Configure on the notification
Click "confirm" to refresh as requested
Captcha is not displayed

Expected behavior
Captcha displays properly
Screenshots
If applicable, add screenshots to help explain your problem.
System details

Home-assistant (version): 0.110.1
Hassio (Yes/No): Yes
alexa_media  (version from const.py or HA startup): 2.8.1l
alexapy (version from pip show alexapy or HA startup):

Logs
Please provide logs. We'll be most likely asking for them anyway

Seems I suffer for the first time of the same issue:

Simone

The captcha url is 5 hours expired for me and results in

AccessDeniedRequest has expired

It Eventually just worked for me 🤷♂ try many times, it'll probably work at some point

I did some testing, image is always corrupted on first opening then works fine.
Simone


Added additional scenario/fix for UWP

When the .NET Native tool chain is used (e.g., to submit to the Microsoft Store), the renderer could be missing. To prevent this from happening additional code is added to the app initializer for UWP.

Should fix #59.


Cannot Make API call to http endpoint when using formData[Tried with both fetch and axios]

Description
Cannot Make API call to http endpoint when using formData[Tried with both fetch and axios]
I've tried addring clearTextTrafic true in android Mainfest.xml file
Working fine in iOS, and working well with normal APIs ( without formData), only API with formData having this issue.
Steps to reproduce
const formData = new FormData()
formData.append('audio_file', {
name: fileName,
type: 'audio/mp3',
uri: filePath
})
await fetch('http endpoint', {
    body: formData,
    method: 'POST',
    headers: {
        'Content-Type': 'multipart/form-data',
        Authorization:
            'Bearer token'
    }
})
    .then(res => {
        console.log('test result ', res)
        console.log('test result status ', res.status)
    })
    .catch(e => {
        console.log('test e ', e)
    })

This returns network error
React Native Version
0.74.1
Affected Platforms
Runtime - Android
Output of npx react-native info
REACT-NATIVE-INFO output:-

System:
OS: macOS 14.2.1
CPU: (8) arm64 Apple M1
Memory: 599.88 MB / 16.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 18.19.0
path: ~/.nvm/versions/node/v18.19.0/bin/node
Yarn:
version: 3.6.4
path: /opt/homebrew/bin/yarn
npm:
version: 10.2.3
path: ~/.nvm/versions/node/v18.19.0/bin/npm
Watchman:
version: 2<IP_ADDRESS>
path: /opt/homebrew/bin/watchman
Managers:
CocoaPods:
version: 1.15.2
path: /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 23.0
- iOS 17.0
- macOS 14.0
- tvOS 17.0
- watchOS 10.0
Android SDK:
API Levels:
- "27"
- "28"
- "29"
- "30"
- "31"
- "32"
- "33"
- "34"
Build Tools:
- 27.0.3
- 28.0.3
- 29.0.2
- 29.0.3
- 30.0.2
- 30.0.3
- 31.0.0
- 32.0.0
- 32.1.0
- 33.0.0
- 33.0.0
- 33.0.1
- 34.0.0
System Images:
- android-32 | Google APIs ARM 64 v8a
- android-33 | Google APIs ARM 64 v8a
Android NDK: Not Found
IDEs:
Android Studio: 2023.1 AI-231.9392.1.2311.11330709
Xcode:
version: 15.0/15A240d
path: /usr/bin/xcodebuild
Languages:
Java:
version: 21.0.2
path: /usr/bin/javac
Ruby:
version: 2.6.10
path: /usr/bin/ruby
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 18.2.0
wanted: 18.2.0
react-native:
installed: 0.74.1
wanted: 0.74.1
react-native-macos: Not Found
npmGlobalPackages:
"react-native": Not Found
Android:
hermesEnabled: true
newArchEnabled: false
iOS:
hermesEnabled: true
newArchEnabled: false

Stacktrace or Logs
Instance Create Error [AxiosError: Network Error]

Reproducer
private repo cannot provide link
Screenshots and Videos
No response

Hello,
I've come across your issue and would like to suggest a couple of potential solutions that might resolve the problem you're experiencing with FormData on Android.
Firstly, ensure that the URI for the file you're appending to FormData has the correct scheme. On Android, the file URI should start with file://. Additionally, verify that the MIME type is accurate. For audio files, instead of 'audio/mp3', you should use 'audio/mpeg'.
Here's an updated snippet of your code with these changes:
const formData = new FormData();
formData.append('audio_file', {
  name: fileName,
  type: 'audio/mpeg', // Correct MIME type
  uri: `file://${filePath}` // Correct URI scheme
});

try {
  const response = await fetch('http endpoint', {
    body: formData,
    method: 'POST',
    headers: {
      'Content-Type': 'multipart/form-data',
      Authorization: 'Bearer token'
    }
  });
  console.log('test result ', response);
  console.log('test result status ', response.status);
} catch (e) {
  console.error('test error ', e);
}

accurate

Tried everything including your suggestion, still no luck 😓

@chr4ss12 Not sure why you mentioned me. This change of filename* added support for non-ascii filenames, and it's suggested to keep both filename= and filename*= in the header value for maximum compatibility. As the MDN doc says, "when both filename and filename* are present in a single header field value, filename* is preferred over filename when both are understood."
Check the encoded name. If the filename*= part is correctly encoded, but you still get errors from the request, it might be an issue with the HTTP server that's handling the header.

@robertying I saw you created the commit (sorry if that's not the case - and you only approved it). I am using very simple code to upload files to google cloud storage, and it stopped working after that commit, there's nothing I can do with the HTTP server that's handling the header (the name= is always hardcoded to "myfile.jpg"),
just giving heads up to anyone else experiencing this issue.

@chr4ss12 I did make the change. This change was necessary to support utf-8 filenames.
If you could have a repro or try constructing the same header value in a form data request in Postman to isolate it, and see if it fixes the issue, it would be easier to see where it went wrong. I previously tested the multipart upload with Express.js and Multer, they received files fine.

@robertying I've checked the code, the spec, played around the request in Charles, and everything checks out - as far as I can tell it looks all right.
The problem is with google Cloud storage not knowing how to read the filename*=UTF-8''dummy.jpg part of the request - I will try and see if I can raise an issue in google tracker.
In meanwhile, am not too convinced of this change though, mainly because the way they implemented the syntax in the first place:
filename*=utf-8''
I. mean really? did they not want to throw in anything else that for sure will break ANY implementation that has no filename*= parsing support, unless that was their idea to begin with...
Also the app I use 'Charles' which I use for debugging could not parse the multipart data because it thought it is malformed (it is not), it seems this filename*= syntax is not that well adapted, perhaps something more along side of lines
if (name contains non ascii characters) //emit  the filename*=

@chr4ss12 Yes in theory if the parser doesn't know the keys in the header value, it should throw them away, according to the doc. In practice though, I can definitely see implementations that don't conform to the spec.
Feel free to file a bug and propose a fix in a PR.
Thank you for investigating this. 🙏

We experienced this exact same issue due to this bug - it looks like it's either that we're not encoding the name correctly or the server cannot parse this value.
In our case, our server is Go-based and will not parse the filename provided if there are any parentheses in the filename.
This is an example of a header that we're getting from React Native now, which is not being parsed correctly by Go.
form-data; name="1"; filename="84fb1493-321f-471f-9c63-7e98019b2931 (1).pdf"; filename*=utf-8''84fb1493-321f-471f-9c63-7e98019b2931 (1).pdf

This is the go stdlib for mime parsing:
https://cs.opensource.google/go/go/+/refs/tags/go1.22.6:src/mime/mediatype.go;l=161-169
Do we know if encodeURI is valid per the RFC to encode a filename in utf-8?
https://github.com/facebook/react-native/commit/7c7e9e6571c1f702213e9ffbb40921cd5a1a786b#diff-756cfe2421bc80e4c12e447a744cff5190da329b1a59614a7ebd853873f6a741R87

@Tadimsky encodeURIComponent doesn't encode parentheses () either.
Maybe check if the server can parse the header if you get rid of the filename*= part.

Ah you're right, sorry about that!
It looks like MDN has an example of how to create RFC-5987 valid values for Content-Disposition which is a combination of encodeURIComponent and some custom replacements.
I think we should probably be using something like that in React Native?
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/encodeURIComponent#encoding_for_content-disposition_and_link_headers

@Tadimsky Thanks so much for finding that. Would you like to raise a PR with that?

Yes, let me give that a try!

Hello,
I Think i'm having the same problem here.
async postMultipart(url: string, data: any) {
        const formData = new FormData();
        let imageUrl: string = '';

        Object.keys(data).map(key => {
            console.log(key);
            const value = data[key];

            if (key == 'tags' || key == 'image') {
                console.log('tags value will be ignored');
            } else if (key == 'imageString') {
                imageUrl = value;
            } else if (key == 'aiGenerated') {
                formData.append('ai_generated', value);
            } else if (Array.isArray(value)) {
                value.forEach(item => formData.append(`${key}`, item));
            } else {
                if (value === '') {
                    formData.append(key, 'none');
                } else {
                    formData.append(key, value);
                }
            }

            return true;
        });

        const imageBlob = await loadImageFile(imageUrl);
        const extension = imageBlob.type.split('/')[1];
        const fileName = imageUrl.split('/').pop();
        console.log('value');
        const file = await new File([imageBlob], fileName + '.' + extension);
        console.log(file);
        await formData.append('image', file, fileName + '.' + extension);
        /*await formData.append('image', {
            uri: imageUrl,
            name: file.name,
            type: file.type,
        });*/
        console.log('formData', formData);

        const token = await getPersistData(DataPersistKeys.TOKEN);

        const response = await fetch(this.config.url + url, {
            method: 'POST',
            headers: {
                'Content-Type': 'multipart/form-data',
                Authorization: `Bearer ${token}`,
            },
            body: formData,
        });

        /*await this.axiosInstance.post(url, formData, {
            headers: {
                'Content-Type': 'multipart/form-data',
            },
            transformRequest: (data, headers) => {
                return data;
            },
        }); */

        return response;
    }

Even when using the code that has been commented out, a network error keep occurs. (both fetch and axios)

Same problem in Aliyun OSS form upload service. The service can't encoding the filename*= till now. Maybe we can make filename*= optional for RN developer.

@Tadimsky Thanks so much for finding that. Would you like to raise a PR with that?

@robertying Can you help verify whether https://github.com/facebook/react-native/pull/46543 fulfills the original intent of your PR?

@yungsters Looks good to me! Thanks @foyarash and @yungsters and everyone who helped file and triage this issue.

Just run into this issue, any workaround until the fix is landed in expo?


ngf-select superslow on Chrome

After pressing a ngf-select element i'm experiencing up to 10 seconds delay before the file browser comes up.
No errors in console, other browsers work fine.
I'm on MacOSX Chrome 53.0.2785.116.
The demo seems affected too
https://angular-file-upload.appspot.com/

Same here

same here

same here

We are seeing this as well...happens on Chrome > 52.  Chrome 51.0.2704 seems fine.

We are seeing this, as well, on both Mac and Windows versions of Chrome. It seems to get worse the more images you upload (as if it's a memory leak):
Windows 7, Chrome Version 53.0.2785.116 m
OSX 10.105, Chrome Version 53.0.2785.116 m

Not seeing the problem with:
Windows 10, Version 53.0.2785.116 m
ng-file-upload @ 12.2.11
Is everyone seeing this problem at 12.2.12?

I am seeing this too but it seems to be a much worse delay when using the ngf-pattern attribute.
Without whitelisting files to upload it is fairly fast and not much of a delay but when I started using the file types supported by my server the delay is close to 10 seconds:
ngf-pattern= ".jpg,.xlsx,.xlt,.bmp,.svg,.csv,.png,.xsd,.docx,.pptx,.txt,.pdf,.ico,.ppt,.uml,.xml,.jpeg,.doc,.json,.yml,.xls"

This happened for me for a minute on the demo page but while I was trying to debug it, it just went away and never happened again. Could it be that it might happen if you have the developer console on? Can you guys constantly reproduce it

@JohnsonBM the issue is about the delay between when you click and popup window shows up. The ngf-pattern is for after the file selection so that is not related to this issue.

I see the popup shows "All Files" when no pattern is set and "Custom Files" when some pattern is set but I am not able to constantly reproduce this anymore.
My Chrome just updated to Version 53.0.2785.143 m so who knows but I haven't reproduced since that update

This is so strange. I was definitely seeing this issue earlier (which had led me to this ticket), but now I can't reproduce it. I tried with the developer console both open and closed.
OSX 10.11.6 (15G1004)
Chrome 53.0.2785.116

It is intermittent for us, as well, and doesn't ever seem to happen on my more powerful developer machine; only on standard user workstations. I think I can say with confidence that these users do not have the developer console open; though, ironically, I probably nearly always have it open and it doesn't seem to affect me.

I have the issue here too after upgraded the chrome( 53.0.2785.116 m).
I notice that it works well if I remove the ngf-accept attribute and the speed is very slow if the ngf-accept attribute has value  (e.g. ngf-accept="'image/*'").
Hope that it is helpful to reproduce issue.

Same here + variation of the issue:

infinite-scroll is super slow on Chrome Version 53.0.2785.116 (64-bit) (Ubuntu 14.0 and Mac OSX) is there is ngf-select on the same page (even if not pressed).

@a455bcd9 Could you create a reproducible jsfiddle?

The problem is solved for me, i guess it was caused by Chrome version.
Yesterday i was experiencing the bug with both developer console closed and open. Before opening the bug i tried other file browsers on the web and they were all working fine.

Since this is only happening in Chrome this is most probably the browser's issues. Since I cannot reproduce it, I won't be able to investigate. If you guys can reproduce it, while it is waiting for the popup to show up click on the pause button the the dev console and see if it stops anywhere in the ng-file-upload code or something like that which could give us a clue.
Also if you are able to reproduce try it in incognito tab to make sure it is not a Chrome plugin causing it.

May be useful to check Chromium bug:
https://bugs.chromium.org/p/chromium/issues/detail?id=638874

@brainsqueezer Thanks! That Chromium bug work-around (https://bugs.chromium.org/p/chromium/issues/detail?id=638874#c13) fixed our problem.  Essentially, we changed this:
<input type="file" .... accept="image/*">

to this:
<input type="file" .... accept="image/gif, image/png, image/jpeg">

and the problem went away.

same here~trying above~


Reflect current menu options

closes https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/issues/3650

@JoanneHendrickson

@JoanneHendrickson
PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

@JoanneHendrickson

@JoanneHendrickson
PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

This file had been changed by me earlier before I saw the edits that were made.


Add VRF proof verification / generation to the Schnorrkel wrapper

[KNOWN ISSUE] Build automation is broken. The original jar task for managing the native rust lib (removed by 015023e) was meant to pick up the lib as output from cargo (built for the current architecture) and place it in its corresponding place. This, however, is a single-target automation.
Our fork of PolkaJ requires multi-target builds, so this approach is not suitable, thus jar has been removed.
For now, manual intervention is necessary: paste the rust lib manually from ./polkaj-schnorrkel/build/rust/release (that's the cargo build result; path relative from repository root) into its corresponding target architecture folder under ./polkaj-schnorrkel/src/main/resources/native, before then building again to obtain the properly updated .jar.
Unfortunately, compilation for all target architectures must happen manually in a similar way as described above, before officially "deploying a new version" for multi-arch usage.


[Bug] sw-context-token not working properly

What happened?
So I am working with store-api to crate customers and work with the shop.
So when I create a customer I get sw-context-token, which is the same as cart ID and I can perform customer shop interactions with that (Fetch a cart, add items, create an order).
The strange thing happening is that after registering a customer, after approx 1 day, when I fetch a cart with the same context-token it fetches different carts every time. When I check if customer is logged in with that token it brings all the customer information with that token, but when trying to fetch a cart it acts like not logged in customer and generates a random cart every time. If I try to create an order with that token, it says cart is empty. If I try to create an order with randomly generated cart id (new context token) it says customer is not logged in.
Am I missing something?
Steps To Reproduce

Create a customer
Fetch a cart
Add items to the cart
Create an order
Wait 24 hours
Fetch a cart again and it doesn't bring the same token as you have put in the header. It brings cart with randomly generated token. But it had to be the same

Is there an existing issue for this?

[X] I have searched the existing issues

Version
Latest stable (generated by CLI)
Which element is affected?
No response
Environment
- OS: Ubuntu 20.04.1 LTS
- Node: 14
- Shopware API: 6.4.0
- Shopware PWA version: 1.0.0-RC.1

Relevant log output
No response

Hi @henrikawl! thanks for reporting.
I'm not sure if it's due to an old version of Shopware 6 (you noted v<IP_ADDRESS>) or something different.
In general, Shopware PWA is only an API Client, which means that we are not setting/invoking a token change and the application only receive the token and if it changes - the same token is being saved under a cookie. In that model "client/receiver" we actually don't know why token is changing or when, and what's behind it. We just set it and send further request with current token. If you find that behavior of session handling is wrong, please report it at the Shopware 6 Core project.

Thanks for the response @mkucmus ! Will check there


Investigate efficent methods to handle the counters table as a sparse matrix

Relatedo to #330

Obsoleted by moving to ClickHouse


An error message shows in "Azure Functions" output panel when creating a C#/Node.js V3/Python/PowerShell Function project

OS: Win10
Build Version: 20230730.1
Repro Steps:

Create a C# .NET 7 project with HttpTrigger template.
Navigate to "Azure Functions" output panel.
Check whether no error message shows in "Azure Functions" output panel.

Expect:
No error message shows in "Azure Functions" output panel.
Actual:
An error message "Failed to get latest templates: Cannot read properties of undefined (reading 'resources')" shows in "Azure Functions" output panel.

More Info:

This issue also reproduces when creating Node.js V3/Python/PowerShell projects.
This issue does not reproduce when creating Node.js V4/Python V2 projects.

This is due to an external issue. I filed an issue on the templates repository here.

It was fixed by the feed, but we also added our own logic to not completely rely on the template version from the bundle feed.


Conflicts with dragula throwing Uncaught DOMException

Hi guys, I’m having a few issues with glimmer 2 after I tried to upgrade my app to Ember 2.10.0.
I'm using a library for drag and drop called dragula, which is being wrapped through ember-dragula.

My scenario is the following:
I have a model for categories which has_many items.  I use dragula so that our users can drag an item from one category into the other and when they drop it, I make the proper model updates.
The thing is, this was working just fine with Ember 2.9.1, but when I tried to upgrade to 2.10.0, I keep getting this error messages on console:

Uncaught DOMException: Failed to execute 'insertBefore' on 'Node': The node before which the new node is to be inserted is not a child of this node.

Uncaught DOMException: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.

Uncaught Error: Cannot call next() on an empty iterator

It seems like there is a conflict between the changes that dragula makes to the DOM and what Ember expects to see in the DOM. I tried to debug as much as I could, but I couldn’t find a solution.
Console is showing that the errors are coming from these files:

glimmer-runtime/lib/dom/helper
glimmer-runtime/lib/bounds

Initially I thought the issue was related to ember-dragula, because the add-on isn't updated often. But after some debugging, it seems like it's more of a conflict than an actual bug.
Any help on that would be much appreciated!

My team and I are looking forward to see our app running on 2.10!

I am seeing the Uncaught DOMException: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node. within one of our components that integrates with a charting library. The error occurs from https://github.com/tildeio/glimmer/blob/master/packages/glimmer-runtime/lib/bounds.ts#L82-L83. Upon pausing execution, the parent was a valid element attached to the DOM, but next was null. My hunch is that the external library's DOM manipulation causes a mismatch with Glimmer or vice versa.
happy to isolate this into a test case too.

Prior versions of Ember did bounds tracking that would be confused by manual DOM manipulation, however, this bounds checking did not cache parentNode of the boundary nodes, this allowed for more  manual DOM manipulation to just work, so long as you didn't mess up the boundary nodes you could move the boundary nodes and the contents and everything would just work (ember-wormhole).  The bounds objects in glimmer have cached parentNode, which has added more caveats to manual DOM manipulation mixing with glimmer DOM manipulation.

Thus, the error  is expected behavior @krisselden ? e.g. Glimmer2 requires stricter validation of DOM states in order to provide the performance benefits. That makes sense; however, I would like to help documenting a best practice / workaround for everyone out there who has to refactor part of their application to handle this.

@efx the only workaround at the moment is the same as ember-wormhole you need a static Element in your template that you move, you can't move Nodes that touch the bounds that Glimmer manages in a way that changes the first, last and parent of those bounds. The first and last thing has always been true, the parent is new.
Drag and drop is best "previewed" then you update the source state and let the glimmer update the DOM to reflect the state.  Within a single list, if properly keyed, glimmer will move instead of recreate the elements.  Between two lists there is no move option that currently works, it is always a remove from one list and rebuild in the other.  In order to declaritively handle the latter, we need to be able to pass the same block to more than one each, and scope the key across lists.

@krisselden thanks so much for the help!
I ended up doing what you suggested... I'm reverting the drop event and then updating the model, so that ember/glimmer can take care of the re-rendering.
If anyone is interested, for dragula there is a way to revert the drop event with drake.cancel(true).
More details here:
https://github.com/bevacqua/dragula/issues/188#issuecomment-146703638
and here:
https://github.com/kalcifer/ember-dragula/issues/25
Appreciate the help guys! I've being fighting this bug for quite some time now! 🐛  🔫

Should I close the issue then?

Yes, but thank you for following up with your solution!


[docs] Add a new site to showcase (hifivework)

[ ] I have followed (at least) the PR section of the contributing guide.

No objection from my end, @mbrookes what do you think? Also, we will need the screenshot to respect the correct dimension (same as the others).

@oliviertassinari I'll resize the image and get you a new PR.
We're a start-up based in Montpellier, France. We have developed other products around MUI. I'll submit other products if you're interested. It's a great way to show what we can do with MUI.
There are our products :

https://www.coderkaine.com/ (showcase website)
https://demo.hifivework.com/#/ ( demo app, I am creating the demo system that allows people to log in to our application and see the design )
http://demo.resilive.fr/#/ ( demo app, with demo user soon )
http://www.resilive.fr/#/ ( showcase website for resilive product, not in https yet, It will be soon)

All the design of these projects are based on MUI with the dark/light mode implemented directly with the MUI theme.
I'm attaching screenshots of the 2 applications because for the moment I don't have a demo user system that allows you to navigate in the application. It will be done very soon.


Das Schwarze Auge (TDE) 5 OFFICIAL: Fix checkbox sizing

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

Changes / Description

To the attention of @Plushtoast.
This small CSS change fixes some weird behavior in checkbox sizing that appears on the character sheet when using longer strings (from the Italian translation, for instance).
For reference, this is the sheet previously:

And this is the same sheet with the fix:

Character Sheet Info Roll20 Internal Use only.

Because this is an official sheet we need to hear from @Plushtoast before merging this.

@mperes I reviewed the change. You can merge the pull-request. Thank you.
@LorenzCK Please submit change requests here: https://github.com/Plushtoast/TDE-Roll20-Official/issues
The sheet is build in an external process with automation out of several parts. If you do pull requests on the compiled template, they will not be included in the source files and thus be lost on the next official update.

Excellent, thanks @Plushtoast! I have submitted the changes and the patch file as an issue here, as requested.


Removed requirements.txt, added poetry dependency manager, its easier…

… to install now, also added installation guide to readme.
authors = ["Your Name<EMAIL_ADDRESS>should be changed
For easier dependecy tracking and env usage, poetry should be considered.
This should also help when there is a plan to containerize the app.

Great Contribution @ktomi96 :+1:


sc-4464 Reintroduce Language Dropdown Menu

Codecov Report

Merging #488 (cd58f93) into main (b5b4f98) will decrease coverage by 9.48%.
The diff coverage is n/a.

:exclamation: Current head cd58f93 differs from pull request most recent head d9255a2. Consider uploading reports for the commit d9255a2 to get more accurate results

@@            Coverage Diff             @@
##             main     #488      +/-   ##
==========================================
- Coverage   46.94%   37.46%   -9.49%
==========================================
  Files         233      151      -82
  Lines       11673     2389    -9284
  Branches      608      608
==========================================
- Hits         5480      895    -4585
+ Misses       5234     1319    -3915
+ Partials      959      175     -784

Impacted Files
Coverage Δ

...m/trisacrypto/directory/pkg/gds/store/trtl/trtl.go

...com/trisacrypto/directory/pkg/gds/emails/emails.go

...m/trisacrypto/directory/pkg/trtl/replica/stream.go

...rypto/directory/pkg/trtl/internal/pagination.pb.go

...isacrypto/directory/pkg/gds/models/v1/models.pb.go

...com/trisacrypto/directory/pkg/gds/config/config.go

...om/trisacrypto/directory/pkg/gds/client/profile.go

.../trisacrypto/directory/pkg/gds/models/v1/models.go

...m/trisacrypto/directory/pkg/gds/client/profiles.go

...com/trisacrypto/directory/pkg/gds/admin/v2/auth.go

... and 72 more

Continue to review full report at Codecov.

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