dotnetCorePackages.*_6_0: 6.0.0 -> 6.0.3

Description of changes
Upgrades to the latest .NET 6 release, supersedes #161285
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[x] 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

[x] 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.05 Release Notes (or backporting 21.11 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.

Thanks for the work, it looks like you need to regenerate the lockfile for ArchiSteamFarm, github-runner and ryujinx as well.
Result of nixpkgs-review pr 164276 run on x86_64-linux 1

1 package blacklisted:

tests.writers

3 packages failed to build:

ArchiSteamFarm
github-runner
ryujinx

11 packages built:

btcpayserver
discordchatexporter-cli
dotnet-aspnetcore (dotnetCorePackages.aspnetcore_6_0)
dotnet-runtime (dotnetCorePackages.runtime_6_0)
dotnet-sdk (dotnet-sdk_6 ,dotnetCorePackages.sdk_6_0)
inklecate
jackett
nbxplorer
omnisharp-roslyn
opentabletdriver
pinta

3 packages failed to build:

ArchiSteamFarm
github-runner
ryujinx

I guess these failing packages didn't get picked up by nixpkgs-review because they're not compatible with my darwin machine?
Is there any way to know of packages that wont get built with nixpkgs-review but depend on the changes you've made?
I'll install nix on my linux machine and see what I can do about it.

I guess these failing packages didn't get picked up by nixpkgs-review because they're not compatible with my darwin machine?

I guess so, that's pretty annoying.

Is there any way to know of packages that wont get built with nixpkgs-review but depend on the changes you've made?

I'm not entirely sure, I have been meaning to write a script to automatically regenerate the lockfiles (at least for buildDotnetModule derivations), which would need that as well. Maybe @SuperSandro2000 or @Mic92 know?
In the meantime I've updated the lockfiles at this branch, feel free to cherry-pick those commits. I've also fixed the commit order there, the *: update dependencies commits were made before the actual update of the sdk.

Result of nixpkgs-review pr 164276 run on x86_64-linux 1

1 package blacklisted:

tests.writers

14 packages built:

ArchiSteamFarm
btcpayserver
discordchatexporter-cli
dotnet-aspnetcore (dotnetCorePackages.aspnetcore_6_0)
dotnet-runtime (dotnetCorePackages.runtime_6_0)
dotnet-sdk (dotnet-sdk_6 ,dotnetCorePackages.sdk_6_0)
github-runner
inklecate
jackett
nbxplorer
omnisharp-roslyn
opentabletdriver
pinta
ryujinx


Investigate using SQS instead of Redis for job queues

I would add a strong +1 on this investigation. I find the current Redis based implementation to have the following risk factors:

The job queues share the same hosts as all of the caching usecases. 1 rampant queue could end up running the Redis host out of memory.
The worker implementations are not specifying a Redis hashtag via the prefix option on queue configs.
ElastiCache itself (what the CDK stack is using here) was not architected for workloads that cannot sustain data loss, it was built purely with caching use-cases in mind. While it complies with the Redis api, a workload like queuing is better suited for running on a provider that has better support for Redis's persistence backends (like the AOF).

That said, the solution doesn't HAVE to be SQS. Alternatively you could:

Split the queuing use-case out into a separate Redis cluster, using Amazon MemoryDB for Redis as the provider for this cluster. Solves the durability and isolation issues, but increases COGS.
Add use-case specific prefixes to all of the job queues (subscriptions, downloads, crons, websockets). This fixes any Redis Clustering related issues (like cross slot errors) that will come when scaling out clusters.


Cant remove pin when click backspace button

Cant remove pin when click backspace button

yes, I not handle this feature.
I plan to add this in next release.
Btw, PR is appreciated

Implemented in 0.4.0 :  https://github.com/gkueny/react-native-pin-code/releases/tag/v0.4.0


bug: Fix docker actions.

We renamed directories in docker/ which broke the actions.
Also try to refactor the action files a little so that we can run (but not publish) these images on pull requests that change the docker/ dir as an extra check. Note this only seems to be supported by the dockerhub plugin; the github plugin doesn't support this (so that will be an issue when we move to it only).
Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable)

(squashed the old PR)

Also how come it kicks off so many actions?

Also how come it kicks off so many actions?

It seems to list out each "job" now. And we have more jobs. imo that's actually a little more useful to see what stage fails (not that our stages are very fine grained).


Load all processes from configuration even when starting specific ones

Defect
When starting specific processes, the remaining processes should be able to be started.

[x] Included the relevant configuration snippet
[x] Included the relevant process-compose log (log location: process-compose info)
[x] Included a [Minimal, Complete, and Verifiable example] (https://stackoverflow.com/help/mcve)

Version of process-compose:
v0.77.6
OS environment:
Darwin aarch64
Steps or code to reproduce the issue:
processes:
  p1:
    command: "sleep infinity"
  p2:
    command: "sleep infinity"

Run process-compose up p1.
Expected result:
I should now be able to start p2 from the TUI or remote client.
Actual result:
Only p1 is available in the UI.

Hey @sciyoshi,
Thanks for trying process-compose.
What is the desired outcome in this case? The selected processes are running and the rest are disabled?

Yes, ideally starting a subset of processes would simply disable the other ones, not remove them from the config entirely.

Fixed in v0.77.8

Awesome, thank you for the quick response + release! Much appreciated 👍


pip-tools doesn't handle duplicates

Test requirements.txt
reportlab==2.6
reportlab==3.1.44

Result:
$ pip-compile -v requirements.txt
Using indexes:
  https://pypi.python.org/simple

                          ROUND 1
Current constraints:
  reportlab==2.6,==3.1.44

Finding the best candidates:
Traceback (most recent call last):
  File "/usr/local/bin/pip-compile", line 11, in <module>
    sys.exit(cli())
  File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 716, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 696, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 889, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 534, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/piptools/scripts/compile.py", line 163, in cli
    results = resolver.resolve()
  File "/usr/local/lib/python2.7/dist-packages/piptools/resolver.py", line 78, in resolve
    has_changed, best_matches = self._resolve_one_round()
  File "/usr/local/lib/python2.7/dist-packages/piptools/resolver.py", line 154, in _resolve_one_round
    best_matches = set(self.get_best_match(ireq) for ireq in constraints)
  File "/usr/local/lib/python2.7/dist-packages/piptools/resolver.py", line 154, in <genexpr>
    best_matches = set(self.get_best_match(ireq) for ireq in constraints)
  File "/usr/local/lib/python2.7/dist-packages/piptools/resolver.py", line 201, in get_best_match
    best_match = self.repository.find_best_match(ireq, prereleases=self.prereleases)
  File "/usr/local/lib/python2.7/dist-packages/piptools/repositories/pypi.py", line 106, in find_best_match
    matching_candidates = [candidates_by_version[ver] for ver in matching_versions]
  File "/usr/share/python-wheels/pkg_resources-0.0.0-py2.py3-none-any.whl/pkg_resources/_vendor/packaging/specifiers.py", line 200, in filter
  File "/usr/share/python-wheels/pkg_resources-0.0.0-py2.py3-none-any.whl/pkg_resources/_vendor/packaging/specifiers.py", line 201, in filter
  File "/usr/share/python-wheels/pkg_resources-0.0.0-py2.py3-none-any.whl/pkg_resources/_vendor/packaging/specifiers.py", line 151, in _coerce_version
  File "/usr/share/python-wheels/pkg_resources-0.0.0-py2.py3-none-any.whl/pkg_resources/_vendor/packaging/version.py", line 41, in parse
  File "/usr/share/python-wheels/pkg_resources-0.0.0-py2.py3-none-any.whl/pkg_resources/_vendor/packaging/version.py", line 210, in __init__
TypeError: expected string or buffer

do you mean that there should be a better error msg? though it's not directly saying there's a duplicate constraint, the issue is obvious from the error

The error message definitely needs to be improved, this is a low-level error that should be handled. That said, these requirements conflict and pip-tools will not be able to handle this.

I'm actually unable to reproduce this locally using latest pip (8.1.1) and latest pip-tools. @LuisAlejandro what's versions are you using?

Yes, i mean pip-tools should die gracefully here. Although, personally i would like it to have an option to use the most recent version if there's a conflict like this, what do you think? I'm willing to make a PR with such a feature.
$ pip --version
pip 8.1.1 from /usr/lib/python2.7/dist-packages (python 2.7)

$ pip-compile --version
pip-compile, version 1.6.1

Nevermind, this is a bug related to Debian.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814397
After reinstalling pip from pypi, this is the output, which seems like a good one.
$ pip-compile -r -v text.txt
Using indexes:
  https://pypi.python.org/simple

                          ROUND 1
Current constraints:
  reportlab==2.6,==3.1.44

Finding the best candidates:
Could not find a version that matches reportlab==2.6,==3.1.44
Tried: 2.3, 2.3, 2.4, 2.5, 2.6, 2.7, 3.0, 3.1.8, 3.1.44, 3.2.0, 3.3.0

Thanks anyway.

I don't think picking either version is a good choice. pip-tools was born from the need to make these conflicts explicit in the first place. In a way, detecting these conflicts is it's job. The conflict itself should be addressed, pip-tools should not ignore it.


PEM_read_bio_PUBKEY from thread, looks like meory leak

Hello. Can't understand reason for memory leak detection. Below my example for reproduce
void PureSSL()
{
	const std::string_view swPUB_KEY = ("-----BEGIN PUBLIC KEY-----"
		"MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA61BjmfXGEvWmegnBGSuS"
		"+rU9soUg2FnODva32D1AqhwdziwHINFaD1MVlcrYG6XRKfkcxnaXGfFDWHLEvNBS"
		"EVCgJjtHAGZIm5GL/KA86KDp/CwDFMSwluowcXwDwoyinmeOY9eKyh6aY72xJh7n"
		"oLBBq1N0bWi1e2i+83txOCg4yV2oVXhBo8pYEJ8LT3el6Smxol3C1oFMVdwPgc0v"
		"Tl25XucMcG/ALE/KNY6pqC2AQ6R2ERlVgPiUWOPatVkt7+Bs3h5Ramxh7XjBOXeu"
		"lmCpGSynXNcpZ/06+vofGi/2MlpQZNhHAo8eayMp6FcvNucIpUndo1X8dKMv3Y26"
		"ZQIDAQAB"
		"-----END PUBLIC KEY-----");

	auto bufkey = BIO_new_mem_buf((void*)swPUB_KEY.data(), swPUB_KEY.length());
	if (!bufkey) {
		return;
	}
	auto xMem = PEM_read_bio_PUBKEY(bufkey, nullptr, nullptr, nullptr);
	EVP_PKEY_free(xMem);
	if (bufkey)
		BIO_free_all(bufkey);
}

void SslLeak()
{
	// no memory leak
	//PureSSL();

	// VLD https://github.com/KindDragon/vld detect leaks
	std::thread th1(PureSSL);
	th1.join();
}

What are the leak(s) that you see? I'd suggest valgrind to see the details of the leaked memory.

WARNING: Visual Leak Detector detected memory leaks!

---------- Block 21 at 0x012ACCB0: 12 bytes ----------
Leak Hash: 0x7F60B251, Count: 1, Total 12 bytes
Call Stack (TID 32256):
ucrtbased.dll!malloc()
LibTests.exe!0x00920846()
LibTests.exe!0x00920BAE()
LibTests.exe!0x00954EE7()
LibTests.exe!0x009551DD()
LibTests.exe!0x00922343()
LibTests.exe!0x009228D2()
LibTests.exe!0x00952D46()
LibTests.exe!0x00951E6F()
LibTests.exe!0x0095305F()
LibTests.exe!0x00951296()
LibTests.exe!0x00950AA1()
LibTests.exe!0x0091E0C2()
LibTests.exe!0x008DB675()
LibTests.exe!0x008A140A()
LibTests.exe!0x008BFC5A()
LibTests.exe!0x008A6B43()
LibTests.exe!0x008ECDF2()
LibTests.exe!0x008E6836()
LibTests.exe!0x008DDE56()
ucrtbased.dll!register_onexit_function() + 0x49C bytes
ucrtbased.dll!register_onexit_function() + 0x1E9 bytes
KERNEL32.dll!BaseThreadInitThunk() + 0x19 bytes
ntdll.dll!RtlGetAppContainerNamedObjectPath() + 0x11E bytes
ntdll.dll!RtlGetAppContainerNamedObjectPath() + 0xEE bytes
Data:
00 00 00 00    01 00 00 00    00 00 00 00                    ........ ........

CD                                                           ........ ........
Visual Leak Detector detected 3 memory leaks (593 bytes).
Largest number used: 127152 bytes.
Total allocations: 135649 bytes.
Visual Leak Detector is now exiting.

Unfortunately this output is not really useful. Perhaps you need to build OpenSSL with debugging information? I suppose you're linking with OpenSSL statically?

Link Static, build Debug.
Agree about not useful VLD output, but this is what I have for now...
I assumed that is VLD issue, but I tested obvious allocation+free, allocation+leak in the thread, VLD showed properly.

Building similiar code on mac and using valgrind shows no leaks.

x:\WinProjects_lib\openssl\Debug\bin>openssl.exe /?
OpenSSL> version
OpenSSL 1.1.1m-dev  xx XXX xxxx
maybe this can be helpful

marking as inactive, to be closed at the end of 3.4 dev barring further input


Feature/ais 96

Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Enables X functionality; fixes bug NIFI-YYYY.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ ] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] Have you verified that the full build is successful on JDK 8?
[ ] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

Fixed tests error.

It still doesn't work. I have the same problems.

Tests are running run successfully  on <IP_ADDRESS> server now. Exceptions handled.

All tests are running now. Checked on <IP_ADDRESS> server


Merge pull request #1 from apereo/master

merge apereo/cas/master
Closes #IssueNumber
Ensure that you include the following:

[] Brief description of changes applied
[] Any documentation on how to configure, test
[] Any possible limitations, side effects, etc
[] Reference any other pull requests that might be related.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


Hot reload does not work properly

If i enable ExtractTextPluggin, i lost HMR on CSS
Without this puggin in dev, the HMR on CSS / SCSS / LESS Works
Look at for an example with the JS / Angular


fix: [IconColor="Color.Custom"] in [FluentNavLink] : the color cannot be set

🐛 Bug Report

I want to set the color of the Icon in the FluentNavLink tag to a custom color. That does not seem to work.
💻 Repro or Code Sample
I downloaded the Fluent UI blazor template with Individual Accounts (dotnet 8). In the NavMenu.Razor component, I tried to change the color of an icon to a custom color. I used the following code :
<FluentNavLink Href="auth" Icon="@(new Icons.Regular.Size20.LockClosedKey().WithColor("#ff0000"))" IconColor="Color.Custom">Auth Required
🌍 Your Environment
Windows 11
Visual Studio (latest)
Dotnet 8 (latest)
Blazor
C#
Fluent Blazor Web app
Browser : Edge, Chrome

Thanks,
This issue will be fixed when this PR #1539 is merged into the dev branch.
This will be included in the next release.


Update APIRef macro for new event organisation

This is a work item for #685, and was originally discussed in https://github.com/mdn/sprints/issues/906.
The APIRef macro currently refers to GroupData to list events. We need to change this as part of the event refactoring wok, and instead treat events more like other subpages of the API (e.g. properties and methods).
But APIRef is complex, used in many pages, and has no tests. So a prerequisite for changing it is adding tests.
In this user story we will:

add tests for APIRef, using the test plan here: https://github.com/mdn/kumascript/pull/1080#issuecomment-466114220 as a guide
update APIRef to look for events in subpages instead of GroupData

AC are that both those changes are committed to KumaScript, deployed, and verified.

@Elchi3 , @chrisdavidmills , I've run into a problem with this and I'd like to know what you think we should do.
I've written tests for APIRef's current behavior, and that's merged. I'd then updated the macro to look in subpages for events, as it does for properties and methods. This is easy, but: the macro uses the page titles for the link text, which, given our format of "Interface: eventname event" looks like:

...which looks terrible.
The easy hacky thing to do is munge the titles in the macro, to try to transform, say, SpeechRecognition: audioend event into audioend. I don't really like this because I think it's likely to be fragile, but I think this is probably what I'll end up doing. Do you have any better ideas?

Check if the title starts with `${interfaceName}:`, and if so, do substring(interfaceName.length+1).trim().

@ExE-Boss , that's what I meant by "munge the titles in the macro". Of course I understand that it's possible to write more or less complicated string-munging code here. But my point is that doing a transformation like this is inherently fragile. For example, how will this work for Arabic or Chinese titles? More generally, though, how are we to guarantee that titles follow the format that our hacky code assumes? And how are pages authors to know that somewhere, some hacky code is relying on page titles having a given format?
It feels like a more correct approach is to model this, so a page can indicate (in its metadata, say)

this is the name I want to use when I'm being included in a place where my context is clear

Also this problem is not specific to event pages. It's just never come up before because we've never used different title before. But now we are experimenting with different titles, it's coming up there too: see for example the first item under "Properties" in the sidebar at  https://developer.mozilla.org/en-US/docs/Web/CSS/border-image.
(I think this doesn't happen for HTML pages because they use the slug, not the title. I guess we could do that, but it's still fragile.

We could use the slug everywhere.

This is an interesting and tricky problem
I think the main thing causing it to look messy is that it goes onto multiple lines.
To mitigate this for the events in particular, could we just remove ParentInterface + separator (": " in the case of English) and leave "event" (or whatever the equivalent is in other languages)? Only having to remove one side would probably be less brittle/difficult than having to trim both sides?
You could do some research into how other languages would show the interface and separator, but I think this might make it easier.
In terms of overly long page titles in general, could we mitigate the problem by using https://developer.mozilla.org/en-US/docs/Web/CSS/text-overflow; text-overflow: ellipsis perhaps?

The multi‑line case used to be so much worse before https://github.com/mozilla/kuma/pull/5131#pullrequestreview-179618826

I think the main thing causing it to look messy is that it goes onto multiple lines.

To mitigate this for the events in particular, could we just remove ParentInterface + separator (": " in the case of English) and leave "event" (or whatever the equivalent is in other languages)?

That's probably a bit less fragile, and it does look better, but tbh it still looks pretty silly:

I mean: we know that they are events, since they're under the "Events" subheading. So why does it have to tell us again and again? Also it makes the list harder to scan. cf:

I think: any mechanism that's based on munging strings (from title or slug) is inherently fragile, because it relies on an implicit contract with the title/slug to have a particular structure. We have no mechanism to enforce this structure or to flag cases (by linting, for example) where the structure isn't what we expect. We also have no explicit representation of this assumption (meaning that, for example, someone editing a page title would have no way of knowing that particular changes to it would break sidebars).
But: if we are to go with one of these options, munging the slug (just splitting on "_" and using the first part) is probably the least fragile and would have the best effect.
Unfortunately other options (like explicitly modelling this in the page metadata) seem like much more expensive things to do.
It's sad that the corner we've painted ourselves into with Kuma is such that these kinds of hacks seem like the only option, and that there are already so many hacks like this that it's easy to think "we'll just add another".

I can't say I disagree with any of this ;-)
I see you've put the PR in already; it looks to me to be the least worst option.

I see you've put the PR in already; it looks to me to be the least worst option.

Yes, I thought it would be better to have something concrete to look at :)

This change is merged, deployed and the new sidebar is visible in pages like https://developer.mozilla.org/en-US/docs/Web/API/SpeechRecognition/audiostart_event and https://developer.mozilla.org/en-US/docs/Web/API/IDBOpenDBRequest.

@wbamberg this is great work Will, thanks for driving this forward.


iotas: 0.2.7 -> 0.2.10

Description of changes
Known issue: spell check, related to #295026 (not an issue)
00:31:16 | spellcheck | WARNING | no installed dictionary for language "en_US" and english, fallback to first language inlanguage list ("he")

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 295645 run on aarch64-linux 1

1 package built:

iotas


There is no "Microsoft" folder

Explain the bug
There is no path to the "Microsoft" folder
To reproduce

Go to "AppData" (then "Roaming") or "ProgramData"
Scroll down to folders that start with "M"
No "Microsoft", just "Microsoft Teams"

Expected behavior
To see the "Microsoft" folder
Logfile
debug.txt
debug_fulltrust.txt
Screenshots

System Information

OS Version:
Edition	Windows 10 Pro
Version	20H2
Installed on	8/26/2020
OS build	19042.867
Experience	Windows Feature Experience Pack 120.2212.551.0

App version:
Version <IP_ADDRESS>

Additional comment
I appear to no longer be able to open Roaming using Files in the middle of writing this report (just after copying the debug files to here)

If you manage to solve the other issue, could you try if the folder shows up if you enable "show hidden files" (even if the folder is not hidden) and disable "hidden system files and folders"?

Ah, yup, that appears to have done it (disabling hide system files; I already had show hidden files on), thanks. I now also see a bunch of other folders that didn't show with File Explorer.

Thanks for confirming @Archeol 👍


[visualstudio] Fix typo on 17.6 lts field

While working on API v1 tests:

#2080

, I felt on this:

According to https://learn.microsoft.com/en-us/visualstudio/releases/2022/release-notes

:+1: much better :ok_hand:


inquiry about Loading scATAC-seq matrices into R

Hi
i want to analyze some scATAC-seq data. And after unzip, i got 10 folders (1 patient per folder). In folder, there are 2 subfolders in whcih scRNAseq data and scATAC-seq data exist seperately. Within these 2 subfolders, there are files generated by cell ranger ( i attached 2 pic.)
How may i loading scATAC-seq matrices as well as scRNAseq data into R? Could you kindly provide some codes?

jzhou@jiang:/mnt/d/##files/#atac/HD2$ tail atac_peaks.bed
GL000218.1      83275   84106
KI270726.1      27131   28058
KI270726.1      41490   42368
KI270711.1      7979    8731
KI270711.1      8887    9380
KI270713.1      15800   16459
KI270713.1      17290   18022
KI270713.1      21445   22340
KI270713.1      32734   33486
KI270713.1      36862   37780
jzhou@jiang:/mnt/d/##files/#atac/HD2$ head atac_peak_annotation.tsv
chrom   start   end     gene    distance        peak_type
chr1    9778    10667   MIR1302-2HG     -18887  distal
chr1    180732  181004  AL627309.5      -6871   distal
chr1    181116  181809  AL627309.5      -7255   distal
chr1    183935  184770  AL627309.5      -10074  distal
chr1    191103  192028  AL627309.5      -17242  distal
chr1    267627  268482  AP006222.2      773     distal
chr1    629498  630379  AC114498.1      41870   distal
chr1    633577  634503  AC114498.1      45949   distal
chr1    778280  779196  LINC01409       0       promoter
jzhou@jiang:/mnt/d/##files/#atac/HD2$ tail -5 atac_fragments.tsv
KI270713.1      39073   39449   TAAGTAGCACAGGATG-1      1
KI270713.1      39075   39208   GCTTAACAGTTCCCGT-1      2
KI270713.1      39697   39805   TGTTATGAGGGCTTTG-1      2
KI270713.1      40366   40677   GACCTAAGTTCCGGCT-1      2
KI270713.1      40639   40708   GGATGGCCACACCAAC-1      2

Hello,
i analyzed upstream data in this dataset (GSE199994) . i download SRA file from EBI, then i change then into fastq file, then i transform their names to standard name and run cellranger_atac. i got error as following:
2.7% (< 10%) of read pairs have a valid 10x barcode. This could be a result of poor sequencing quality,
a sample mixup, or running the wrong pipeline, for example, running cellranger-atac on Multiome ATAC + GEX data, or vice versa.
The whole code is as following :
ascp -QT -l 300m -P33001 -i ~/miniconda3/envs/my10x/etc/asperaweb_id_dsa.openssh \era-fasp@fasp.sra.ebi.ac.uk:/vol1/srr/SRR186/006/SRR18613306 .
mv SRR18613306 SRR18613306.sra
parallel-fastq-dump -t 12  -O ./ --split-files --gzip -s SRR18613306.sra
mv *.fastq.gz /home/ubuntu/GSE199994/scATAC/2.raw_fastq
mv SRR18613295_1.fastq.gz SRR18613295-P5_S9_L001_I1_001.fastq.gz
mv SRR18613295_2.fastq.gz SRR18613295-P5_S9_L001_R1_001.fastq.gz
mv SRR18613295_3.fastq.gz SRR18613295-P5_S9_L001_R2_001.fastq.gz
mv SRR18613295_4.fastq.gz SRR18613295-P5_S9_L001_R3_001.fastq.gz
cellranger-atac count --id=SRR18613295-P5
--reference=/home/ubuntu/biosoftware/refdata-cellranger-arc-GRCh38-2020-A-2.0.0
--fastqs=/home/ubuntu/GSE199994/scATAC/2.raw_fastq
--sample=SRR18613295-P5
--localcores=24
--localmem=96
could you help me?

Please, join the R/Bioconductor community and ask there. https://bioc-community.herokuapp.com/


Fix recent regressions and make the example work again.

Make the buildargs argument optional
Fix: don't prefix from_dockerfile with step.build_dir if none was present
Use argparse.FileType() to ensure ArgumentParser flags unreadable files
** Let the shell expand ~ in paths on the command line

Remove debug output

is there any was to "compile" this as a pip/script rather than run as an image? Total noob in python

@elmpp You can download the branch at https://github.com/owbear/DockerMake/archive/buildargs_fix.zip

I had to comment out lines 71-75 but seems good now thanks

Apologies, I'm haven't been getting notifications from github for this project (hopefully I should be getting them now).
I've just pushed a major update that includes CI to test the examples, can be installed as a CLI tool from pypi (pip install DockerMake will put the docker-make executable into your $PATH), and has some major reorganization and new features. Please let me know if you're still having issues after this!


fix(protocol): improve TKoToken, BridgedERC20, and ERC20Vault

BEGIN_COMMIT_OVERRIDE
refactor(protocol): merge BridgedERC20Baseinto BridgedERC20for simplicity
feat(protocol):  allow contract owner to mint/burn tokens (besides ERC20Vault)
feat(protocol): check new bridged token implements IBridgedERC20 interface for migration
feat(protocol): disallow bridged token contract owner to trigger migration directly (must go through ERC20Vault)
feat(protocol): disallow migration within 90 days post the previous migration
feat(protoocl): make BridgedERC20 no longer inherit ERC20VotesUpgradeable
feat(protocol): add BridgedTaikoToken that inherits ERC20VotesUpgradeable
END_COMMIT_OVERRIDE
This is to respond this feedback from OZ

Tokens inheriting from the BridgedERC20Base contract can be migrated by the owner or by calling the changeMigrationStatus function of the ERC20Vault. If a migration is triggered, token owners can burn their tokens to mint the same amount of tokens on the new contract. If the migration is triggered by the bridge, old tokens are added to a blacklist and have to be migrated before being able to bridge.
However, there are multiple migration scenarios that could cause accidental user losses:

If a new migration is triggered before some users have migrated from a previous migration, then these users would effectively lose their tokens as they would no longer be able to call mint() on the new contract nor bridge their tokens.
If a migration is triggered by the owner instead of the ERC20Vault, the vault would no longer be able to call burn or mint on the migrated token. This would prevent users from bridging and could cause losses as the new migrated token would not be bridging to the same contract when bridging through the vault.
If a migration happens to a token that doesn't implement the IBridgedERC20 interface, user losses could happen as well.
If such concerns are shared, consider addressing the above instances to protect users' funds from errors during migrations. Potential solutions include adding a delay to migrations during which no new migration can be done, preventing the owner from calling changeMigrationStatus, and validating that the new token implements the IBridgedERC20 using ERC-165 during migrations.

@davidtaikocha TaikoToken's storage layout stays the same!


feat: update to stable rust

Goal
The goal of this PR is update to rust stable toolchain.
Discussion

Checklist

[ ] Chain spec updated
[ ] Custom RPC OR Runtime API added/changed? Updated js/api-augment.
[ ] Design doc(s) updated
[ ] Tests added
[ ] Benchmarks added
[ ] Weights updated

Archiving


[OAuth] Document scope to create PRs on private repo

See discussion on slack (private) cc @hysts @coyotte508

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


A higher proposal

Hi, this has been an unique package that is helpful already in many scenarios.
Recently, I have this thought that it would be even better that the tree item highlight would sync with editor page scrolling (without mouse clicking).
I know now if you click mouse anywhere in the editor, the tree highlight would jump to according position, and the proposal upward seems a step forward.
Best regards

I have made a research, but i cannot find any api to catch the view scroll. If anyone has idea how to do it, the help will be appreciated.

A feature has been added https://github.com/bacadra/pulsar-navigation-panel/pull/5.


how can i config a watcher then the  attachment will send with mail at V6.2.4

HI all,
i want to config  a watcher,send alarm with mail.
alarm will filting the log and send to the user there are how many errors and what's them are.
i try to send the error logs by attachment , how should i config it ?
my watcher like this:
{
  "actions": {
    "email_admin": {
      "throttle_period": "1m",
      "email": {
        "to": "XX",
        "from": "XX",
        "subject": "{{payload.hits.total}} ...",
        "priority": "high",
        "body": "......."
          }
        }
      }
    }
  },
"input"{},
"condition"{},
....
}

@tom143tc it would be easier to help if we had some sample data, could you provide that?
Check the documentation on howto create a watcher

@tom143tc do you know Elasticsearch Query DSL? This is a must for working with Sentinl.

@tom143tc do you know Elasticsearch Query DSL? This is a must for working with Sentinl.

i can query the error logs, i don't know how can the logs be send with mail by attachment....

@sergibondarenko Although the attempt still failed，thanks very much  for you help. I think i using the sentinl on a wrong way.My original intention is using sentinl for alerting the coding man that the app had some running exception and sending the error count by email and the error logs  about the part of exception  by attachment .And, i find the config of email.body can't send the detials of payload.hits.hits[i].


Mobilelogin-Bugfixes

Fixes login error if you are using no Authenticator apps like Google Authenticator

Fixes login error if you are using a Xbox account

https://github.com/trydis/FIFA-Ultimate-Team-Toolkit/pull/251/commits/83c345c9e2bf46f88c95cd9e7488c7ff7b1e4ffe should named 	Bugfix: Login Error with E-Mail TwoFactorAuthentication instead of Fix for Error 465 at mobile login process - I had no chance to rename the commit

I'll fix it. If you want to learn how, look into interactive rebasing.

Thanks! I will learn it :)

Forgot to edit the commit message, but we'll survive :smile:

Hopefully I'll remember it when merging into master...


fixes import plugins for browser

Fixes import of plugin using browserify;
fixes unintentional changes from plugabilly
DCO 1.1 Signed-off-by: {{Ayush Gupta}}<EMAIL_ADDRESS>

@ayush2k can you please change the name of the util.js file to utils.js? (we don't want confusion with the node util module itself.)

@scottnath changes util to utils


Lan adapter temperature shows instead of CPU.

Describe the bug
The function si.cpuTemperature as the main parameter returns the temperature for the i350bb-pci-0600. This is a LAN adapter.
Below I insert a comparison of the output of the function and the sensors command.
To Reproduce
Steps to reproduce the behavior:

used function
si.cpuTemperature().then(data => console.log(data));
Code output

Promise {
  <pending>,
  domain:
   Domain {
     domain: null,
     _events:
      [Object: null prototype] {
        removeListener: [Function: updateExceptionCapture],
        newListener: [Function: updateExceptionCapture],
        error: [Function: debugDomainError] },
     _eventsCount: 3,
     _maxListeners: undefined,
     members: [],
     [Symbol(kWeak)]: WeakReference {} } }
> { main: 68,
  cores:
   [ 39, 34, 37, 39, 39, 39, 38, 35, 40, 42, 38, 44, 36, 38, 39, 40 ],
  max: 68,
  socket: [],
  chipset: null }

sensors command output:

coretemp-isa-0001
Adapter: ISA adapter
Package id 1:  +40.0°C  (high = +79.0°C, crit = +89.0°C)
Core 0:        +36.0°C  (high = +79.0°C, crit = +89.0°C)
Core 1:        +37.0°C  (high = +79.0°C, crit = +89.0°C)
Core 2:        +33.0°C  (high = +79.0°C, crit = +89.0°C)
Core 3:        +38.0°C  (high = +79.0°C, crit = +89.0°C)
Core 4:        +32.0°C  (high = +79.0°C, crit = +89.0°C)
Core 5:        +33.0°C  (high = +79.0°C, crit = +89.0°C)
Core 6:        +34.0°C  (high = +79.0°C, crit = +89.0°C)
Core 7:        +36.0°C  (high = +79.0°C, crit = +89.0°C)

i350bb-pci-0600
Adapter: PCI adapter
loc1:         +69.0°C  (high = +120.0°C, crit = +110.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +39.0°C  (high = +79.0°C, crit = +89.0°C)
Core 0:        +38.0°C  (high = +79.0°C, crit = +89.0°C)
Core 1:        +34.0°C  (high = +79.0°C, crit = +89.0°C)
Core 2:        +37.0°C  (high = +79.0°C, crit = +89.0°C)
Core 3:        +38.0°C  (high = +79.0°C, crit = +89.0°C)
Core 4:        +39.0°C  (high = +79.0°C, crit = +89.0°C)
Core 5:        +39.0°C  (high = +79.0°C, crit = +89.0°C)
Core 6:        +38.0°C  (high = +79.0°C, crit = +89.0°C)
Core 7:        +36.0°C  (high = +79.0°C, crit = +89.0°C)

Expected behavior
Main parameter should return the temperature of the processor or ambient sensor.
Environment (please complete the following information):

systeminformation package version:
OS: Ubuntu 20.04 x86_64
Hardware IBM X3650 M4

@rest2t Thank you for providing detailed information!! I will make further investigation and will try to come up with a solution.

@rest2t can you provide also the output of:
cat /sys/class/thermal/thermal_zone*/type  2>/dev/null; echo "-----"; cat /sys/class/thermal/thermal_zone*/temp 2>/dev/null;

and
for mon in /sys/class/hwmon/hwmon*; do for label in "$mon"/temp*_label; do if [ -f $label ]; then value=${label%_*}_input; echo $(cat "$label")___$(cat "$value"); fi; done; done;

@sebhildebrandt
`x86_pkg_temp
x86_pkg_temp
38000
37000
andloc1___67000
Package id 0___38000
Core 0___37000
Core 1___30000
Core 2___34000
Core 3___35000
Core 4___37000
Core 5___38000
Core 6___35000
Core 7___32000
Package id 1___38000
Core 0___37000
Core 1___35000
Core 2___32000
Core 3___37000
Core 4___29000
Core 5___32000
Core 6___33000
Core 7___35000
`

@rest2t thank you. I guess I see the problem and will try to fix it.

@rest2t I implemented a fix for that. Version 5.13.2 just released. Can you check it on your side?

@sebhildebrandt unfortunately. the same problem continues .
ubuntu@ubuntu:~/ubuntu$ npm update systeminformation
+<EMAIL_ADDRESS>updated 1 package and audited 168 packages in 3.983s
9 packages are looking for funding
  run 'npm fund' for details
found 5 vulnerabilities (2 high, 3 critical)
 run 'npm audit fix' to fix them, ornpm audit for details
ubuntu@ubuntu:~/ubuntu$ node
> const si = require('systeminformation');
undefined
> si.cpuTemperature().then(data => console.log(data));
Promise {
  <pending>,
  domain:
   Domain {
     domain: null,
     _events:
      [Object: null prototype] {
        removeListener: [Function: updateExceptionCapture],
        newListener: [Function: updateExceptionCapture],
        error: [Function: debugDomainError] },
     _eventsCount: 3,
     _maxListeners: undefined,
     members: [],
     [Symbol(kWeak)]: WeakReference {} } }
> { main: 69,
  cores:
   [ 45, 43, 44, 45, 46, 45, 45, 42, 42, 45, 41, 46, 39, 41, 42, 43 ],
  max: 69,
  socket: [],
  chipset: null }
(To exit, press ^C again or type .exit)
> .exit
soseman@dockerownia:~/soseman-client$ sensors
coretemp-isa-0001
Adapter: ISA adapter
Package id 1:  +45.0°C  (high = +79.0°C, crit = +89.0°C)
Core 0:        +42.0°C  (high = +79.0°C, crit = +89.0°C)
Core 1:        +43.0°C  (high = +79.0°C, crit = +89.0°C)
Core 2:        +41.0°C  (high = +79.0°C, crit = +89.0°C)
Core 3:        +45.0°C  (high = +79.0°C, crit = +89.0°C)
Core 4:        +38.0°C  (high = +79.0°C, crit = +89.0°C)
Core 5:        +43.0°C  (high = +79.0°C, crit = +89.0°C)
Core 6:        +41.0°C  (high = +79.0°C, crit = +89.0°C)
Core 7:        +43.0°C  (high = +79.0°C, crit = +89.0°C)
i350bb-pci-0600
Adapter: PCI adapter
loc1:         +69.0°C  (high = +120.0°C, crit = +110.0°C)
coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +45.0°C  (high = +79.0°C, crit = +89.0°C)
Core 0:        +44.0°C  (high = +79.0°C, crit = +89.0°C)
Core 1:        +41.0°C  (high = +79.0°C, crit = +89.0°C)
Core 2:        +42.0°C  (high = +79.0°C, crit = +89.0°C)
Core 3:        +45.0°C  (high = +79.0°C, crit = +89.0°C)
Core 4:        +45.0°C  (high = +79.0°C, crit = +89.0°C)
Core 5:        +44.0°C  (high = +79.0°C, crit = +89.0°C)
Core 6:        +44.0°C  (high = +79.0°C, crit = +89.0°C)
Core 7:        +41.0°C  (high = +79.0°C, crit = +89.0°C)

@rest2t thank you for testing ... actually as the other commands I gave you return values, sensors output is not needed. So what I would like to see one more time:
can you add the following line in the node_modules/systeminformation/lib/cpu.jsafter line 1040:
console.log(lines);

and post then again the full output (so the console.log as well as the data spitted out from your code)

Version 5.13.3 just released.

Unrelated to The function si.cpuTemperature as the main parameter returns the temperature for the i350bb-pci-0600. This is a LAN adapter., but the latest version fixed my problem with cpu temperature returning 0.
Thank you so much!

@rest2t did you had time to test it once again? Then we can close this issue ;-) Thank you in advance!

@sebhildebrandt I just tested the latest version. Everything works as expected, thanks!


Commits cause lots of failed GHA builds

See https://github.com/LukePrior/nbn-upgrade-map/commits/main

Looks like the auto-build is doing a commit, and triggering another build (besides the one it means to).  Perhaps a filter to prevent the other build running.

Ok I think this should be fixed


update vue version 3.1.5 -> 3.2.47

Hi!
Thanks for the great plugin. I appreciate it.
Today i found one problem, i have a problem with I am using Vue.js 3.2.45 and I get errors about types.
This is because the type required by the :ref property of the input tag is different from the type provided by useField().ref.

The :ref property must be of type VNodeRef, but this VNodeRef type has been changed since v3.2.35 of vuejs/core. See the link for details.
[https://github.com/vuejs/core/commit/0c7fd13ea628a2f1b72c6f4150c0dba32da4468e#diff-9b2ba253038f7b71dbbbcb545e028d2d51d27d88b041b 918c9eb102a83fef189](https://github. co.uk) 028d2d51d27d88b041b918c9eb102a83fef189)
So I first upgraded vue to the latest version and then updated the FieldNode type returned by useField().ref.
I hope you can merge them. Thanks.
Translated with www.DeepL.com/Translator (free version)

hi! thanks for plugin! please merge this branch

available on<EMAIL_ADDRESS>


AppCompatActivity

Why does Material-CAB take a AppCompatActivity and not a simple context?

Because a Context is not dependent on a specific window in your app, it could be a Service, etc.


Pre-Trained LSTM.ipynb -  Key rnn/basic_lstm_cell/kernel not found in checkpoint

saver.restore(sess, tf.train.latest_checkpoint('/tmp/models'))
INFO:tensorflow:Restoring parameters from /tmp/models\pretrained_lstm.ckpt-90000
NotFoundError (see above for traceback): Key rnn/basic_lstm_cell/kernel not found in checkpoint
[[Node: save_1/RestoreV2_4 = RestoreV2[dtypes=[DT_FLOAT], _device="/job:localhost/replica:0/task:0/cpu:0"](_arg_save_1/Const_0_0, save_1/RestoreV2_4/tensor_names, save_1/RestoreV2_4/shape_and_slices)]]

What version of Tensorflow are you using?

I'm getting the same error while using tensorflow-1.4.0 with python 3.5

Ok, got it. It works for tensorflow-1.1

Yeah sorry about it. Haven't had time to make the code compatible with versions above 1.1, but yeah 1.1 should work.

import tensorflow as tf
print (tf.VERSION)
1.3.0

You'll need to downgrade to version 1.1. Need to look into why the code is breaking for versions later than that


Dockerfile does not build, speedtest not a package

Hi,
When trying to build the speedtest docker image I discovered that it fails in building for me. The applicable log are as follows:
Step 4/6 : RUN apt-get install speedtest
 ---> Running in 4064acb0cbd4
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package speedtest
The command '/bin/sh -c apt-get install speedtest' returned a non-zero code: 100

Searching for installable packages I found that there is a package called speedtest-cli. Have they change the name of the package or is there some other strange error?
The binary installed with speedtest-cli package have different formats of the command line arguments and the output is slightly different resulting in the the file speedtest.sh needs to be modified.
If this is the way to go I can make a pull request fixing it if it would help.
I am running the commands on Ubuntu 22.04 on a x86_64 platform and using docker version 20.10.14.
/Morgan

Hi again,
Looking more into this I found that the reason speedtest package is not available is since the key is unavailable. Among the last lines of the install_deb.sh file hides the output of apt update. The output is for me:.
Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
Hit:2 http://deb.debian.org/debian bullseye InRelease
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
Get:4 https://packagecloud.io/ookla/speedtest-cli/debian bullseye InRelease [24.5 kB]
Err:4 https://packagecloud.io/ookla/speedtest-cli/debian bullseye InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8E61C2AB9A6D1557
Reading package lists... Done
W: GPG error: https://packagecloud.io/ookla/speedtest-cli/debian bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8E61C2AB9A6D1557
E: The repository 'https://packagecloud.io/ookla/speedtest-cli/debian bullseye InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Will continue to look why key is not installed.
/Morgan

Hi again,
Received the following anser from the Speedtest support, i.e. they are aware of the problem and hopefully working on fixing it.
We are aware of an issue installing the CLI via the Debian/Ubuntu instructions. For the time being you can download the tarball version of the CLI client and use that. You can download the tar file by clicking the Download for Linux button at the bottom of the CLI page. Select the architecture you need from the dropdown menu and the tar file should download.
I can close the ticket when they have fixed the issue, or you can close it now since it is no error in this code.

Thanks for documenting this here!


[SQL] Add required properties to failover groups

Generated from RestAPI PR: https://github.com/Azure/azure-rest-api-specs/pull/1445

In https://github.com/Azure/azure-sdk-for-python/pull/1413


libswscale #error in execution of opencv 2.4.11 install shell script

While installing OpenCV, I get the following error.
"libswscale is necessary to build the newer OpenCV ffmpeg wrapper"
#error "libswscale is necessary to build the newer OpenCV ffmpeg wrapper"
^
How can I resolve this? Note that libswscale is present in the ffmpeg folder.

Does the last answer https://github.com/opencv/opencv/issues/5930 help?
I'll move the code to OpenCV 3.0, the problem should go away.

Nope, this did not solve the issue.

It seems then it's an OpenCV, ffmpeg, pkg-config-related issue. I'll try upgrading mpegflow to OpenCV 3.x when I have time.
For time being, I'd suggest you also migrate to OpenCV 3.x if you can afford it. Otherwise keep investigating the issue, unfortunately, I could not help further on this one.


Add support for groups param for ranking to RayDMatrix

groups in DMatrix cannot be currently set, limiting ranking functionality. Should be added at some point.

cc @mmui

starting to look into this today

This should be addressed in https://github.com/ray-project/xgboost_ray/pull/239 with @atomic

@Yard1 i believe we can close this


Grey list test

Encompassed in named tests, but not implemented for any BGC variables right now.

Closing, not needed at this stage.


Platform updates

General updates to improve usability & fix typos.
https://github.com/Jays-Home-Assistant-Add-ons/repository/issues/5

Fix non-rendering icons
Disable SSL by default. The documentation was written as such, but the config.yaml file had ssl=true
Clarify importance of a step during integration with HA

Thanks @ibhm for your help here


Enable search by network

Expose the ability to search for literature based on the networks (plural) a dataset might belong to.
The intention is to be able to showcase the scientific papers that have been published that made use of datasets connected with e.g. hosted portals that scope their data by a network. It will also make it possible to show citation metrics for e.g. the OBIS network
This will require changes in the backend that builds the index as well.

now in prod with project identifiers, network and gbifProgramme filters and facets
https://api.gbif.org/v1/literature/search?facet=gbifProgramme&facet=gbifProjectIdentifier
https://api.gbif.org/v1/literature/search?gbifProgramme=BID
https://api.gbif.org/v1/literature/search?gbifProjectIdentifier=BIFA4_015
https://api.gbif.org/v1/literature/search?gbifNetworkKey=379a0de5-f377-4661-9a30-33dd844e7b9a
https://api.gbif.org/v1/literature/search?facet=gbifNetworkKey


[Feature request] Handle multiple download sources/ mirrors

Description of the new feature/enhancement
Request

Ability to add multiple URLs to same installer

Why?

Speed

Example: Foxit CDN is super slow. But they got two CDNs. Forces combined, 2x super slow = slow.

Reliability, redundance.

Example

https://cdn01.foxitsoftware.com/product/reader/desktop/win/11.0.1/FoxitPDFReader1101_L10N_Setup_Prom.exe
https://cdn02.foxitsoftware.com/product/reader/desktop/win/11.0.1/FoxitPDFReader1101_L10N_Setup_Prom.exe

Potential blocker

Requires complex download logic that might not be in place already?

Free Download Manager manages it for instance

Proposed technical implementation details (optional)

Update cli to handle the download logic, if not already implemented.
Update manifest scheme to accept one or multiple URLs to the same file.

Related to:

#225
#673

Similor issue with KiCad, Different mirrors has different bandwidth available depending on the location you are downloading from. Default github source is very very slow.


Narrow the scope of accessable VerifiableGroupInfo fields.

Currently, we can access the ciphersuite (VerifiableGroupInfo.payload.group_context.ciphersuite), signer (VerifiableGroupInfo.payload.signer), and extensions (VerifiableGroupInfo.payload.extensions) via pub(crate) methods.

This is a bit difficult to resolve cleanly. I experimented a bit on duesee/issue_1185 and we could make it so that we expose only one VerifiableGroupInfo::process method. This method would take (backend, external_nodes), do the signature verification, and return (group_info, nodes, use_ratchet_tree_extension). This way we won't have to construct the ratchet tree twice. It seems to reduce the code and narrows the scope of VerifiableGroupInfo. But I'm not sure if this is the best way to go about this.

Sounds like a good way to me. From what I can see, we process GroupInfo in two places: new_from_welcome and join_by_external_commit and in both cases your solution seems to fit quite well.

Okay, cool. Before I make the PR: Currently I just used this to experiment around. Do you think we should introduce a variant WelcomeError::GroupInfo instead and use ...
pub enum WelcomeError<KeyStoreError> {
   // ...
   #[error(transparent)]
    GroupInfo(#[from] GroupInfoProcessError),

... or similar instead?

Good question. In the past, I believe we chose to have duplicate code in favor of tight error enums. The API in general needs a bit of an overhaul, so we need to touch the errors at some point anyway, so for now I'd be okay with less than tight error enums if it allows us to move a bit faster.

Alright, thanks! I'll go with the #[from] GroupInfoProcessError variant then. Luckily, we are still "tight" here so we can delay this issue a bit. Moving a bit fast sounds good :+1:

Unassigning for now until I have validation straigt.


Update versionize crate documentation.

Reason for This PR
Update versionize crate documentation.
Description of Changes
Provided in commit messages.
License Acceptance
By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license.
PR Checklist
[Author TODO: Meet these criteria.]
[Reviewer TODO: Verify that these criteria are met. Request changes if not]

[x] All commits in this PR are signed (git commit -s).
[x] The reason for this PR is clearly provided (issue no. or explanation).
[x] The description of changes is clear and encompassing.
[x] Any required documentation changes (code and docs) are included in this PR.
[x] Any newly added unsafe code is properly documented.
[x] Any user-facing changes are mentioned in CHANGELOG.md.

@luminitavoicu @georgepisaltu updated, PTAL.

@luminitavoicu @georgepisaltu updated, PTAL.


[github] show PR controller in PR context

This PR fixes gitpod-io/gitpod#4081

This still lacks the case that the user hasn't granted the necessary scopes in the GitHub access yet. Should we add a notification on this?

@JanKoehnlein How does it behave in such case? Nothing happens, then it would be good to add a notification.

I see this dialog for each worskpace on PR now:

Regardless whether GitHub PR extension already has access rights or not.

https://github.com/gitpod-io/gitpod/issues/4081#issuecomment-892607493


"Backup Now" functionality?

Hello there!
Great addon - just wanted to ask if there's a hidden "Backup now!" mechanic somewhere. I am playing around ALOT with HA and would love to have the ability to instantly create a backup when needed.
 After I was looking through the projects main github page i've posted, not reading up on the more detailed documentation linked from within the addon.
Here's a solution anyway for anyone else wondering:
Create a new automation "backupnow"
In your dashboard create a card with the following:
show_name: true show_icon: true type: entity-button tap_action:   action: call-service   service: automation.trigger   service_data:     entity_id: automation.backupnow hold_action:   action: more-info entity: automation.sys_backupnow icon_height: 25px name: Create backup now icon: mdi:cloud-upload

Yes, using a manual trigger from a script is the way to go.
--> https://github.com/thomasmauerer/hassio-addons/blob/master/samba-backup/DOCS.md#manual-triggers


Iterators for resultsets

Provide an iterator type that allows iterating over a resultset (only for sync ops).

Doesn't make sense with the new resultset + execution_state model.


The curtain motor cannot be controlled in HomeKit

The curtain motor cannot be controlled in HomeKit, but the status can be updated. I added the motor to HomeKit using HomeKit Bridge, and I could control it before, but not now. It only works properly when the type is selected as garage door or gate. If I connect it to HomeKit via Xiaomi Miot Auto, I can also control it.
Home Assistant version is 2024.11.0, but it seems to have stopped working since 2024.10.3, and I'm not sure which version it started to fail.

Start from device diagnostics. I have no idea what device you talking about.

It's a strange converter. It's not in the component. Maybe there's a bug in it.
It's definitely not supposed to be like this: "target-position", "target_position"

It's a strange converter. It's not in the component. Maybe there's a bug in it. It's definitely not supposed to be like this: "target-position", "target_position"

But it works fine in Home Assistant, and I have been using this motor for almost a year. It also worked fine in HomeKit before. It has only recently started to become uncontrollable. When I click the icon in HomeKit, it prompts that it is shutting down, but the motor does not actually move.

Because your converter wrong. Target position shouldn't be a number. It should be helper for cover. Without domain and with right name. Check other cover covers.

Because your converter wrong. Target position shouldn't be a number. It should be helper for cover. Without domain and with right name. Check other cover converters.

10807: ["Linptech", "Linp Smart Curtain Motor", "linp.curtain.c2"],

"spec": [
    MapConv("motor", "cover", mi="2.p.1", map={0: "stop", 1: "open", 2: "close"}),
    BaseConv("target_position", mi="2.p.2"),
    MathConv("target-position", "number", mi="2.p.2", min=0, max=100, entity=ENTITY_CONFIG),
    CurtainPosConv("position", mi="2.p.3"),
    BaseConv("motor_reverse", "switch", mi="2.p.4"),
    MapConv("mode", "select", mi="2.p.5", map={0: "default", 1: "doublmode", 2: "leftmode", 3: "rightmode"}),
],

Now it works!Thx!

https://github.com/AlexxIT/XiaomiGateway3/releases/tag/v4.0.7


Added contact us button for easy navigation and added email validation

Description
I have added a contact us button in the navbar for easy navigation to the 'connect with us' form.
I have also improved the email validation by adding a RegEx to it.
Pull Request Checklist
Please make sure that your PR meets the following requirements:

[ ] The app is working correctly after applying the changes.
[ ] The app is responsive and displays properly on different screen sizes and devices.
[ ] The changes are thoroughly documented in the appropriate files or documentation sections.
[ ] The coding conventions and style guidelines are followed consistently.

Checklist
Please check all applicable boxes and provide any additional information if needed.

[ ] I have tested the changes locally and ensured that the app is functioning as expected.
[ ] I have verified that the app is responsive and looks good on various screen sizes and devices.
[ ] I have reviewed the documentation and ensured that it accurately reflects the changes made.
[ ] I have followed the coding conventions and style guidelines defined in the project.
[ ] I have run the automated tests and all of them pass.
[ ] I have considered the performance implications of the changes made.
[ ] I have considered the security implications of the changes made.
[ ] I have checked for any potential regressions or side effects caused by the changes.
[ ] I have performed a self-review of my code.
[ ] Starred the repository.
[ ] Added My Name to the Contributor's List.
[ ] Followed the repository's Contributing Guidelines.
[ ] I ran the app and tested it locally to verify that it works as expected.

Screenshots - If Any (Optional)
email validation

contact us button

Additional Notes(Optional)
NA
Related Issues
NA
Reviewers
Please tag the relevant team members or reviewers who should review this pull request.

could you also fix the form validation? I see form isn't accepting email id

could you also fix the form validation? I see form isn't accepting email id

Could you please elaborate which email id are you trying with! I think some edge cases might be remaining, it would be helpful if you could provide me with your sample

On clicking the 'contact us' button , there should be a scroll effecct just like that in courses section

+1 and this pR would be merged after https://github.com/amupedia2021/Project-Amupedia/pull/291


return value of scipy.optimize.minimize not consistent for 1D

For 1D problems some optimizers return the result as a scalar (Powell, COBYLA), some
as a list with one element.
There are other optimizers that need the Jacobian, I did not check them.
from scipy.optimize import minimize, rosen

o = ['Nelder-Mead', 'Powell', 'CG',  'BFGS', 'L-BFGS-B',
      'TNC', 'COBYLA', 'SLSQP']

for k in o:

    x0 = [1.3] #, 0.7, 0.8, 1.9, 1.2]
    res = minimize(rosen, x0, method=k, tol=1e-6)

    print(k, res.x)

print()

for k in o:

    x0 = 1.3 #, 0.7, 0.8, 1.9, 1.2]
    res = minimize(rosen, x0, method=k, tol=1e-6)

    print(k, res.x)

print()

for k in o:

    x0 = [1.3, 0.7]
    res = minimize(rosen, x0, method=k, tol=1e-6)

    print(k, res.x)

ISTM the most consistent thing would be to return an array in all cases. In that case the culprits are 'POWELL' (always returns a scalar) and 'COBYLA' (returns a scalar if given a scalar).

Other than updating the docs to make this clear, I can't see what you can do here without breaking backwards compatibility?

The documentation for OptimizeResult:
https://docs.scipy.org/doc/scipy/reference/generated/scipy.optimize.OptimizeResult.html#scipy.optimize.OptimizeResult
says that res.x is an ndarray. Also I just noticed that
>>> res = minimize(lambda x: x**2, 0.1, method='POWELL')
>>> res.x
array(4.163336342344337e-17)
>>> res = minimize(lambda x: x**2, 0.1, method='COBYLA')
>>> res.x
array(0.00010234375000000536)

so they are returning arrays; this would just be changing their shape to 1x1. (Importantly, float(res.x) works in either case.)
This makes me feel like it would be an acceptable back-compat break to make them all return 1x1 arrays. But maybe others are more conservative?

My guess is that backwards compatibility consistent, uniform return types here.  Does anyone know for sure is this breaks any unit tests? Even if it doesn't it still breaks back-compat. This needs a decision.

While we may not want to break backwards compatibility right now, this is definitely something that should be made consistent in a future version release.

It looks like this is already fixed, and there is already a test
https://github.com/scipy/scipy/blob/3123229c02fc2f31a368098b81a17f8723c209ab/scipy/optimize/tests/test_optimize.py#L2433
A snipped that can be run locally to confirm:
import numpy as np
from scipy import optimize
from scipy.optimize._minimize import MINIMIZE_METHODS, MINIMIZE_SCALAR_METHODS

def f(x, a):
    return x**2 + a.sum()

def df(x, a):
    return 2*x

def ddf(x, a):
    return 2

a = np.array([-1, -2])

for method in MINIMIZE_METHODS:

    kwargs = {'fun': f, 'x0': 1, 'args': a, 'method': method}
    if method in {'newton-cg', 'dogleg', 'trust-ncg',
                  'trust-exact', 'trust-krylov'}:
        kwargs['jac'] = df
        kwargs['hess'] = ddf

    res = optimize.minimize(**kwargs)
    assert res.x.shape == (1,)
    print(res.x)


fix: Windows build

Issue:
Fixes #43 / #54
Description of changes:
sqlite3-parser version must be > 0.8 and include the version bump to fallible-iterator to rectify the above build issues on Windows.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

This fix would be really valuable for the Spin framework (https://github.com/fermyon/spin) too. At the moment we keep having to coerce libsql-client back to an earlier rev to work around the sqlite3-parser issue.  Thanks!


Why??

The blog post doesnt detail on why you are closing patse fown!!

Good question!

@jonasman They need the servers for Facebook and all that bullshit.

I don't think that is something we can get into here.

oh guys parse was very useful why did you do that ?

Please be transparent.
If you are building something new and better let us know and we wont be mad at you :)

@gfosco Are you gonna update all SDK docs to the parse-server API?

Because this is business. You cannot give everyone the same unicorn forever.


Add dynamic commitment

DRAFT: I have not yet tested this sufficiently--it's looking alright with the old data in testnet, but I need more clarity on testing strategy before I'm confident. Will discuss offline, but any feedback on the code so far is appreciated!

Update help messages for all assignment options
Rename Edit to Modify
Update suspend icon
Add action for new dynamic commit
Fix popup-proxy background color on mobile

This should be working. In doing this I discovered bugs in both suspend/withdraw: (1) using an id field that doesn't seem to exist anymore -> switched it to hash and (2) fixed the redirect after those are called so that it doesnt 404 (there was an extra 's'). However, neither of those actions seems to be implemented on the backend at the moment from my perspective, so we will probably need to do a bit more testing on all these functions as those features are brought in

Ready for review!

@gregory-latinier Updated variable name for clarity. Can't merge until the block is resolved. Thanks!


[QUESTION] Load a excel with many rows

Package version, Laravel version
Package version 2.1.21
Laravel 5.4.35
I have a very large excel, about 74.000 rows and 39 columns, and I need to load.
How can I load that excel without getting a 500 server error?
I tried this:
$path = Input::file('import_file')->getRealPath();                     $data = Excel::load($path, function($reader) {                     })->get();
Is it possible to load the file by chunks?

Solved with
Excel::filter('chunk')->load($path)->chunk(200, function ($results)                     {                         foreach ($results as $row)                         {                             $group = new Group();                             $group->name = $row->codigo;                             $group->save();                         }                     });
But it 12 hours to import de 74000 rows to the database.
Some idea to how can I optimize that?

You have to fiddle around with the chunk size; for each machine the most optimal size is different. Also inserting each row seperatly is not the most efficient on big batches. Try inserting multiple rows in one query, it should be lots faster.


Can DiffDock generate gibbs free energy scores?

Hello! Thank you for developing an amazing tool. I'm trying DiffDock to verify binding of a potential drug-protein interaction. Is gibbs free energy available for DiffDock? Or maybe I missed it, may I ask where I can find it from the results? Thank you!

Hi @levinhein
No, at the moment DiffDock does not compute gibbs free energies. This will hopefully be added in future versions.
However, we (and collaborators) have observed positive correlation between the confidence score given by DiffDock (to the first or first few poses) and the binding affinity. This correlation can be made even stronger by combining DiffDock's score with traditional docking scoring functions (e.g. Vina or GNINA).
I hope this helps!


Improve make-ability

regenerate package-lock.jsons
Makefile in browser-demo will build the root dir if not yet built

After this build we can also turn on travis-ci for this repo and it will check that running make in both project root and browser-demo runs ok https://travis-ci.com/gobengo/node-pubcontrol/builds/95312471


intellisense find all references hangs when mostly c# solution includes an f# project

Intellisense "Find All References" from a c# project with a large-ish solution containing an f# project shows the "References" output tab but never displays the results. Unloading the f# project and performing the same, displays the results as expected. The popup tooltip version of references from the editor works correctly in either case.
This issue has been moved from https://developercommunity.visualstudio.com/content/problem/232907/intellisense-find-all-references-hangs-when-mostly.html
VSTS ticketId: 599200
These are the original issue comments:
(no comments)
These are the original issue solutions:
(no solutions)

Note: I don't believe that this is FAR hanging; but rather, FAR not supporting F# symbols coming from C#


chore(deps-dev): bump npm-package-json-lint to 4.6.0 in package.json

There was a bug with npm-package-json-lint where sub-package node_modules weren't being ignored. That has since been fixed, so this removes the unnecessary .npmpackagejsonlintignore.
See: https://github.com/tclindner/npm-package-json-lint/issues/168#issuecomment-581205438

Great stuff!


Deleting a folder previously used in VSC without restarting the OS

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: latest
OS Version: Win 11/10

Steps to Reproduce:

open a project.
close VSC and all applis linked to what is in the folder.
try to delete the folder. You can't.
It's only possible after an OS restart

Well I tried through the console and it's telling about git
rm: remove write-protected regular file './obsidian-tools/.git/objects/02/5ad1d92c19a4847d5f9a17ba3e1993dbeea9c3'?
I don't know if it's only linked to git or git in VSC. I ran a npm install & run dev on this folder before. And the console was closed of course

This is just file locking, there's not anything VS Code can do. Whatever process is using the files must stop and in this case it looks like git has locked your files.


[DOCS] Add new conf about kryo registrator to spark start command

Change Logs
make the spark start command consistent with the README.md
Impact
none
Risk level (write none, low medium or high below)
none
Documentation Update

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

Thanks @eric9204 for revising the Spark guide.  Could you also update the docs of release 0.13.x under website/versioned_docs?

Thanks @eric9204 for revising the Spark guide. Could you also update the docs of release 0.13.x under website/versioned_docs?

@yihua Has been updated！


Added script for creating a file with all of the icons.

Usually it would be better to use a build tool to import only the icons you use and build a file like this specific to your project, but having a single file with all of the icons can be convenient for some scenarios (mine).
Lets you use the icons like this:
<svg class="icon">
    <use xlink:href="/path/to/feather.svg#calendar" />
</svg>

Take a look at #101, here we reach a consensus on how Feather will be used.

This is #2 on the list of the stuff that consensus has been reached on:
An SVG sprite sheet should be generated from the icons directory.
I just didn't see a spritesheet in the repo yet.


Compilation fails with -Wshadow + -Werror

Pulling Arrow from Homebrew with brew install apache-arrow pulls the latest tagged version 6.0.0.
Compiling with -Wshadow (and treating warnings as errors) leads to compilation failure. See here.
The culprit seems to be a re-declaration of c_type inside of the ArrayDataInlineVisitor struct here.

Thanks for reporting this.

@dantrim
Initial attempt to reproduce this error using
cmake -DCMAKE_BUILD_TYPE=Debug -DARROW_BUILD_TESTS=ON -DCMAKE_CXX_FLAGS="-Wshadow -Werror" -DARROW_COMPUTE=ON -DARROW_PARQUET=ON  ..
make

indicates that RE2 has this error also
-- stderr output is:
In file included from /home/arrow/cpp/build/re2_ep-prefix/src/re2_ep/re2/compile.cc:22:
/home/arrow/cpp/build/re2_ep-prefix/src/re2_ep/re2/walker-inl.h:172:13: error: declaration shadows a local variable [-Werror,-Wshadow]
    Regexp* re = s->re;
            ^
/home/arrow/cpp/build/re2_ep-prefix/src/re2_ep/re2/walker-inl.h:157:64: note: previous declaration is here
template<typename T> T Regexp::Walker<T>::WalkInternal(Regexp* re, T top_arg,

Trying
cmake -DCMAKE_BUILD_TYPE=Release -DARROW_BUILD_TESTS=OFF -DCMAKE_CXX_FLAGS="-Wshadow -Werror" -DARROW_COMPUTE=OFF -DARROW_PARQUET=ON  -DARROW_WITH_RE2=OFF ..

Gives a similar problem with Thrift. The project uses Jira for issue tracking and can raise this there, though fixes in dependencies may take more time to get included since the latest versions are not used in the releases.


Load styles async

<link rel="preload" href="/path/to/my.css" as="style">
<link rel="stylesheet" href="/path/to/my.css" media="print" onload="this.media='all'">

Explored in #78 but the flash of content was too much. Will have to explore more later.


Windows 2022: couldn't determine visual studio generator

We use the cmake crate in our CI for building msquic. We just tried updating the Azure Pipeline to use Windows Server 2022 instead of 2019 to build it and the CI failed.
We are getting the following error (from here):
  --- stderr
  thread 'main' panicked at '

  couldn't determine visual studio generator
  if VisualStudio is installed, however, consider running the appropriate vcvars script before building this crate

We have no problem with any non-Rust cmake builds, so I suspect this is something specific to the the cmake crate. Do you know of any work around for this? For the time being we can continue to use 2019, but eventually that will be deprecated. Thanks!

Looks like the error is coming from the cc crate: https://github.com/alexcrichton/cc-rs/blob/030baede12f079793cc50d6f90b677b889c49fcd/src/windows_registry.rs#L150

Thanks, this helped me to fix the same issue by settings runs-on: windows-2019 for the time being.

@aloucks Looks to me like it's not cc but cmake: https://github.com/alexcrichton/cmake-rs/blob/7793895d88acc45d29fac7c711ddaef11c897ea9/src/lib.rs#L610
I assume Vs17 must be added.
@nibanks Is your target i686?

Hi, for anyone interested in a temporary solution - just add this patch to your root Cargo.toml, VS2022 support is already merged, but new cc version is not yet released:
[patch.crates-io]
cc = { git = "https://github.com/alexcrichton/cc-rs" }


Apply the gallery visibility settings in New Search UI

Checklist

[x] the [contributor license agreement][] is signed
[x] commit message follows [commit guidelines][]
[x] tests are included
[x] screenshots are included showing significant UI changes
[ ] documentation is changed or added

Description of change
Apply the gallery visibility settings in New Search UI.
https://user-images.githubusercontent.com/47203811/120432568-75f29700-c3bd-11eb-90c5-2a123721204c.mp4

Ah, flaked on the known LDAPTest - ldapLogon. Not worth worrying about.


URI fails install tests under rakudo-moar-2021.10-47-gab02205ed

See errors below, when trying to install into rakudo-moar-2021.10-47-gab02205ed:
===> Searching for: URI
===> Testing: URI:ver<0.3.3>
[URI]         # Failed test 'right exception type (X::Assignment::RO)'
[URI]         # at SETTING::src/core.c/Exception.pm6 line 62
[URI]         # Expected: X::Assignment::RO
[URI]         # Got:      X::Attribute::Required
[URI]         # Exception message: The attribute '$!value' is required, but you did not provide a value for it.
[URI]         # You failed 1 test of 2
[URI]     # Failed test 'cannot set query<>[] because it is immutable'
[URI]     # at t/mutate.t line 79
[URI]         # Failed test 'right exception type (X::Assignment::RO)'
[URI]         # at SETTING::src/core.c/Exception.pm6 line 62
[URI]         # Expected: X::Assignment::RO
[URI]         # Got:      X::Attribute::Required
[URI]         # Exception message: The attribute '$!value' is required, but you did not provide a value for it.
[URI]         # You failed 1 test of 2
[URI]     # Failed test 'cannot set query<>[] because it is immutable'
[URI]     # at t/mutate.t line 91
[URI]     # You failed 2 tests of 12
[URI] # Failed test 'hash-format = Mixed'
[URI] # at t/mutate.t line 71
[URI]         # Failed test 'right exception type (X::Assignment::RO)'
[URI]         # at SETTING::src/core.c/Exception.pm6 line 62
[URI]         # Expected: X::Assignment::RO
[URI]         # Got:      X::Attribute::Required
[URI]         # Exception message: The attribute '$!value' is required, but you did not provide a value for it.
[URI]         # You failed 1 test of 2
[URI]     # Failed test 'cannot set query<>[] because it is immutable'
[URI]     # at t/mutate.t line 133
[URI]     # You failed 1 test of 9
[URI] # Failed test 'hash-format = Lists'
[URI] # at t/mutate.t line 119
[URI] # You failed 2 tests of 35
[URI]         # Failed test 'right exception type (X::Assignment::RO)'
[URI]         # at SETTING::src/core.c/Exception.pm6 line 62
[URI]         # Expected: X::Assignment::RO
[URI]         # Got:      X::Attribute::Required
[URI]         # Exception message: The attribute '$!value' is required, but you did not provide a value for it.
[URI]         # You failed 1 test of 2
[URI]     # Failed test 'did we throws-like X::Assignment::RO?'
[URI]     # at t/query.t line 91
[URI]     # You failed 1 test of 12
[URI] # Failed test 'hash-ish lists bits'
[URI] # at t/query.t line 84
[URI]         # Failed test 'right exception type (X::Assignment::RO)'
[URI]         # at SETTING::src/core.c/Exception.pm6 line 62
[URI]         # Expected: X::Assignment::RO
[URI]         # Got:      X::Attribute::Required
[URI]         # Exception message: The attribute '$!value' is required, but you did not provide a value for it.
[URI]         # You failed 1 test of 2
[URI]     # Failed test 'did we throws-like X::Assignment::RO?'
[URI]     # at t/query.t line 116
[URI]     # You failed 1 test of 12
[URI] # Failed test 'hash-ish mixed bits'
[URI] # at t/query.t line 109
[URI] # You failed 2 tests of 24
===> Testing [FAIL]: URI:ver<0.3.3>
Aborting due to test failure: URI:ver<0.3.3> (use --force-test to override)

FWIW, URI:ver<0.3.3> installed fine the last time I built Rakudo, which was rakudo-moar-2021.10-11-g3127861cb.

I'm not sure this isn't something that should be considered a core issue, given that the module hasn't changed in the interim.

@jonathanstowe Yeah, I pinged #raku-dev about this issue as well, just in case.

Narrowed down to the Rakudo merge commit 4fece6137 -- though given that the merged commits, 15ed1566a and 1ea47322a, appear to be bug fixes around RO assignment exceptions, I'm not 100% sure where the exception interpretation is wrong.
My current reading is that it is indeed a problem in this module, because of this line which does not supply the RO value (but happened to work before because that attribute had previously not been marked required): https://github.com/raku-community-modules/URI/blob/master/lib/URI/Query.rakumod#L99

@dwarring It looks like you've done the last couple releases of this module -- up for doing 0.3.4?

@japhb version bumped


Fixture selection

Short description
When I click on fixture item neither onChange nor onSuggestSelect are fired.
Expected results
I suppose onChange should be fired

it happens only when there is no location in a fixture

Closing this because there is no feedback. Reopen if this problem still exists and provide an example.


kube-config - Allow arbitrary 'extension' objects

Prior to this change the type of NamedExtension.extension was String.
However, the k8s golang type defines this as a runtime.RawExtension,
which allows for setting arbitrary objects as the value of the extension
key.
For example, minikube sets the value to:
- extension:
     last-update: 'Thu, 18 Feb 2021 16:59:26 PST'
     provider: minikube.sigs.k8s.io
     version: v1.17.1
  name: context_info

When kube-rs tries to parse this as a String you'll end up with an error like this:
thread 'config::file_config::tests::kubeconfig_deserialize' panicked at 'called `Result::unwrap()`
on an `Err` value: ParseYaml(Message("invalid type: map, expected a string",
Some(Pos { marker: Marker { index: 312, line: 12, col: 23 }, path:
"clusters[1].cluster.extensions[0].extension" })))', kube/src/config/file_config.rs:407:14

This PR changes the type from String to serde_yaml::Value
to allow for parsing, reading, writing, and round-tripping any
valid yaml value.
Further, the Cluster struct is filled with all known existing fields defined here: https://github.com/kubernetes/client-go/blob/30548acd0a9e231d42d406433aef55b111b36240/tools/clientcmd/api/v1/types.go#L63 , with the extensions field most relevant to this PR as it is set by minikube.

Released in kube 0.51.0, thanks again!


Use cpp consistently in check_linker_need_libatomic

check_linker_need_libatomic will always fail its second check, because cxx is now a list. This affects piwheel builds since 1.46.0.
2022-05-20T21:01:38,827   Running command python setup.py egg_info
2022-05-20T21:01:42,599   Traceback (most recent call last):
2022-05-20T21:01:42,601     File "<string>", line 2, in <module>
2022-05-20T21:01:42,601     File "<pip-setuptools-caller>", line 34, in <module>
2022-05-20T21:01:42,602     File "/tmp/pip-wheel-6bjraj6j/grpcio_27b0a215ff714c6f93177ad66c3f3c03/setup.py", line 257, in <module>
2022-05-20T21:01:42,602       if check_linker_need_libatomic():
2022-05-20T21:01:42,603     File "/tmp/pip-wheel-6bjraj6j/grpcio_27b0a215ff714c6f93177ad66c3f3c03/setup.py", line 213, in check_linker_need_libatomic
2022-05-20T21:01:42,604       cpp_test = subprocess.Popen(
2022-05-20T21:01:42,604     File "/usr/lib/python3.9/subprocess.py", line 951, in __init__
2022-05-20T21:01:42,606       self._execute_child(args, executable, preexec_fn, close_fds,
2022-05-20T21:01:42,607     File "/usr/lib/python3.9/subprocess.py", line 1698, in _execute_child
2022-05-20T21:01:42,609       and os.path.dirname(executable)
2022-05-20T21:01:42,610     File "/usr/lib/python3.9/posixpath.py", line 152, in dirname
2022-05-20T21:01:42,628       p = os.fspath(p)
2022-05-20T21:01:42,629   TypeError: expected str, bytes or os.PathLike object, not list
2022-05-20T21:01:42,824   ERROR: [present-rich] python setup.py egg_info exited with 1
2022-05-20T21:01:42,863   [bold magenta]full command[/]: [blue]/usr/bin/python3 -c '

Full log

This simple fix looks good. @veblush or @lidizheng can one of you add the required label and approve this? It's causing constant build failures which result in the package being unavailable on piwheels https://github.com/piwheels/packages/issues/308

It's not clear to me why shlex.split is now returning a list of lists. And I am not able to reproduce myself. For posterity, it might be helpful if you could include a log of what shlex.split is actually returning in this case, since none of the logs I've seen seem to include it.
With that said, as long as this passes CI, I'm happy to get the fix in. @fedej can you please resolve merge conflicts?

There is no need for this PR. issue has been fixed in https://github.com/grpc/grpc/pull/30522


Terraform cleanup after aks migration

Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

There's nothing in the resource group so I think that should go too?
https://github.com/hmcts/sscs-track-your-appeal-notifications/blob/removease/infrastructure/main.tf#L1-L8
<EMAIL_ADDRESS>
true, i assumed that their db wiil be in there.

There's nothing in the resource group so I think that should go too?
/infrastructure/main.tf@removease#L1-L8
<EMAIL_ADDRESS>
true, i assumed that their db wiil be in there.

DBs go into a resource group with data added to its name, intentionally separated from infra that is easy to rebuild / doesn't matter much


Livingston County, MI

Hi Justin,
The entire data set for all of Livingston County is $36,000  according to our Enhanced Access Fee Schedule.
At the time of purchase you would be required to sign a Non Disclosure form.
Let me know if you are interested.
Thanks

e-mailed to verify cost and requested non-disclosure form:
<EMAIL_ADDRESS>

How many records in Livingston County?! That’s a pretty steep price tag :\
On Thu, Jan 19, 2017 at 1:35 PM, Justin Meyers<EMAIL_ADDRESS>wrote:

e-mailed to verify cost and requested non-disclosure form:
<EMAIL_ADDRESS>—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/openaddresses/openaddresses/issues/2377#issuecomment-273905859,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0EO7ZiuoMqe7sC_pPdE9-tvQIU89xeks5rT9cVgaJpZM4Looc2
.

can we grab their buildings looks like there is an addr field (*not sure if it is tiles though): http://tiles4.arcgis.com/tiles/cL47lSDX9wW9Ylgx/arcgis/rest/services/Basemap/MapServer/7 @iandees ?

@nvkelso
Hello Justin,
$36,000 is for just for the address points and the accompanying attribute table. We currently have 81,861 address points in GIS for the county.
Parcels are a separate dataset of 86,381 parcels. The cost is $1 per parcel.
A sample of our Nondisclosure Agreement can be found at the following link,
https://www.livgov.com/gis/Documents/NondisclosureSample.pdf
Feel free to contact me if you have any questions.
Thanks,
Sandon Lettieri
GIS Technician
Livingston County
<EMAIL_ADDRESS>P: (517) 540 - 8780
F: (517) 545 - 9608


Response status meters for @ResponseMetered annotated service methods

This is already opt-in since it will only apply to service methods that the developer annotates with @ResponseMetered. For other methods, this interceptor will not be registered.
Regarding performance: From personal experience, Dropwizard meters & timers add negligible overhead even to methods that take a few microseconds.