Can't install from Microsoft Store?

Microsoft PowerToys version
latest
Running as admin

[ ] Yes

Area(s) with issue?
General
Steps to reproduce

Go to the windows store
type "powertoys" in the search
Click the "Get" button
Wait ...

✔ Expected Behavior
Powertoys gets installed.
❌ Actual Behavior
Just a waiting indicator, with the text "something happened on our ...", and never finishes.

I've tested installing other apps from the store while this is happening, and they install fine, so it seems line it's not on my end.
I would just use one of the installers from the Releases page, but I like to use the store for the easy updates when newer version get released.
Other Software
No response

I would just use one of the installers from the Releases page, but I like to use the store for the easy updates when newer version get released.

PowerToys do not use the update system from Microsoft Store (win32 app cannot use it), and we use our own auto-updater. So there is no difference in this. 😄

@franky920920 ok, thank you :)

PowerToys do not use the update system from Microsoft Store (win32 app cannot use it), and we use our own auto-updater. So there is no difference in this. 😄

I feel like this should be stated on the Store page, because background updates are literally the only reason I prefer Store versions other than the improved security.
So then do I just uninstall the Store version and reinstall the winget/Github version now?
Or is there a way to switch without reinstalling?

Could you re-open this?
Because the issue still exists - I can't install PowerToys from the MS store.
In my case, since I can't run it as an administrator, that's the only way I can install it...


Excersize 2, Step 9, "select" Container terraform? Or enter?

The instruction say to "select" container terraform. But there is no container terraform.
I have to manually enter it.
Did I miss a step somewhere, or is the instruction ambigous? It's a smart dropdown that can read my Azure account, so it could be either way. (Missing container or have to enter the name myself.)

Hi Cyberman,
Yes, You need to enter the Container name. We will update the instruction.
Thanks


Same identifier in two for-let-of loops throws error.

for (let x of a) {}
for (let x of a) {}

x is already declared
If one of the loops is a regular for loop, the exception is still thrown. If both are regular for loops, everything works fine.

Something I bumped into while I was narrowing down this error case -
for (let x of a);

This by itself seems to get minified fine. With check: true, it says it generated invalid JS, but it looks valid to me.

Actually,
for (let x;;) {}
for (let x;;) {}

minifies as
for(let x;;){}for(x;;){}

which is no good.
I was poking around a bit and I saw a createdScope value on various elements that some code is trying to use, but I don't actually see where it's set. If that's always undefined (falsy) that feels like it could be related to this behavior.

Thanks – fixed in #37. The short answer for why mysterious properties like createdScope are in the codebase is that I forked it from Bublé several months ago as an experiment for a talk, then left it to gather dust until a few days ago. I'm still trying to figure out my way around it tbh!

:+1: The issues with for and for-of loops that I was seeing look fixed in your PR.
I took another look at what I mentioned in my second comment here - there does actually seem to be a code generation error here. I'll open another ticket for that, but it really is a bit of an edge case.


[BE Refactoring] KafkaService & ClusterService services decomposition

Reason:
currently this services contains various logic that should be transformed into more fine grained fashion
Steps:

Create new services: TopicService, MetricService, ConsumerGroupService, MessagesService
Move current logic from KafkaService & ClusterService to new & existing services
rm KafkaService & ClusterService

implemented


PublicCourse API ViewSet

Add APIs for the public course feature. Following up on #30.
Jira

RED-794: Support the public course feature

Related Issues
This PR also refactors the module to ensure is_active check for both OrganizationCourse and UserOrganizationMapping. Closes #32. I skipped on adding tests because we don't really use those active flags. Nevertheless adding them is worthwhile.

@OmarIthawi Since you added is_active checks to UserOrganizationMapping I think it is important to check this access for both True and False for the UserFieldWithPermission serializer: https://github.com/appsembler/course-access-groups/blob/omar/api-public-courses/course_access_groups/serializers.py#L69 and also for user_has_public_access_to_course function in permissions

Thanks @johnbaldwin. I'm not sure I don't understand. Because both of UserFieldWithPermission and the user_has_public_access_to_course has those checks:
https://github.com/appsembler/course-access-groups/blob/6bca3ec88304a9e30dc61b64b8f43a70ee9d8807/course_access_groups/serializers.py#L74-L81
https://github.com/appsembler/course-access-groups/blob/6bca3ec88304a9e30dc61b64b8f43a70ee9d8807/course_access_groups/permissions.py#L87-L94
Could you please share what do you think the change would look like in a git diff?

@OmarIthawi I see that the production code has is_active checks now, but I do not see where this flag is tested in the tests. Am I missing something?

@OmarIthawi I see that the production code has is_active checks now, but I do not see where this flag is tested in the tests. Am I missing something?

@johnbaldwin Not really I actually haven't added tests. I took the liberty of just changing the code quickly without tests. I agree with you that tests should be placed here, but probably for a bit later. So I added an issue for me to address shortly: https://github.com/appsembler/course-access-groups/issues/39

@OmarIthawi Thanks for creating PR #39 to make sure is_active is properly tested!


git subcommands display uncolored output in all terminals under xfce

Describe the bug
git status, git pull shows (red and green) colors, whereas git diff,git show,git log no longer do.
I first noticed this issue when I updated unstable to commit 3320a06049f
PS: This has nothing to do with dircolors or git's color configuration.
To Reproduce
Steps to reproduce the behavior:

open a terminal emulator. Tested with xterm, xfce-terminal and alacritty under xfce

Expected behavior
git diff/ git show have colored output, unless you have changed this in preferences
Notify maintainers
@peti @wmertens @globin
Metadata

system: "x86_64-linux"
host os: Linux 5.6.15, NixOS, 20.09pre227577.135073a87b7 (Nightingale)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.5
channels(root): "nixos-20.09pre227577.135073a87b7, nixpkgs-20.09pre218717.05f0934825c"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

What's the output of dircolors on the terminals you tested? I think you should also try eval "$(eval dircolors)".

What's the output of dircolors on the terminals you tested? I think you should also try eval "$(eval dircolors)".

LS_COLORS='';
export LS_COLORS

> $(eval dircolors)
LS_COLORS='';: command not found

Sorry, typed wrong. I meant:
eval "$(dircolors)"

But that's irrelevant, because the issue is that you don't have any colors set on your terminal. What is your $TERM?

Well, on xterm, if you'd run:
eval "$(dircolors)"

I expect colors to work for you.

Hm. On xterm eval "$(dircolors)" produces no output, while just dircolors produces the above output.
On alacritty eval "$(dircolors)"` produces:
LS_COLORS='';
export LS_COLORS

It shouldn't produce output, it should make git be colroful afterwards.

Well, it doesn't do that. As before, git status shows colorful elements, but git log, git diff etc don't.

For alacritty, ideally dircolors would have print non empty strings. See: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=35247  I'm not sure what's the status of this though...
What's the output of git config --get color.ui?

> git config --get color.ui

output is empty. But setting it to always also doesn't do anything

Set it to true.

Also does nothing

I didn't change any configuration for this to happen. I just updated my system, to the best of my knowledge. Can you reproduce this behavior?

No .... When did you update it?

It was working before for me before commit https://github.com/NixOS/nixpkgs/commit/3320a06049fc259e87a2bd98f4cd42f15f746b96 (March 27). I updated again today in the hopes that the problem might have gone away.

Seems unrelated to me, though I feel you my friend, these stuff are totally annoying.

Obviously I'm not saying that particular commit caused it, that just happened to be the version I pulled in. It could be anything between that and the last version that worked. This problem clearly has nothing to do with git's color configuration, and unlikely with any particular terminal either. Thanks for your time, if you could delete your comments though that would be great because maybe someone else can help and doesn't have to read this conversation. I will add the findings to the original description.

I don't think deleting the columns is necessary. In any case, for me colored git log is still working and I'm on latest unstable. I use bash and my $TERM is xterm-256color

Perhaps it has something to do with less? Since both log and diff allow scrolling in a less-like manner.

Hm. It seems to be my version of less is bundled as part of the busybox multi-call executable. Is this normal? My man, ls etc are also.

Maybe export LESS=-r?
On 2 June 2020 1:45:16 GMT+03:00, Gregor Alexandru<EMAIL_ADDRESS>wrote:

Hm. It seems to be my version of less is bundled as part of the busybox multi-call executable. Is this normal? My man, ls etc are also.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/NixOS/nixpkgs/issues/89315#issuecomment-637164421

I can observe the same behavior as the OP. I am pretty desperate.
All the basic linux programs seem to be busybox commands.
# readlink $(which less)
/nix/store/hf8bf3n475a5ag6hj5983zs5d16c77fd-busybox-1.31.1/bin/less

I am bringing this up since my man pages don't work anymore
# man man
man: no manual entry for 'man'
# ls /run/current-system/sw/share/man/man1/man.1.gz
/run/current-system/sw/share/man/man1/man.1.gz

And other nixos commands are doing weird things, e.g.:
# nixos-container create my-system --flake grep: unrecognized option '--flake'
BusyBox v1.31.1 () multi-call binary.

Usage: grep [-HhnlLoqvsriwFE] [-m N] [-A/B/C N] PATTERN/-e PATTERN.../-f FILE [FILE]...

Search for PATTERN in FILEs (or stdin)

	-H	Add 'filename:' prefix
	-h	Do not add 'filename:' prefix
	-n	Add 'line_no:' prefix
	-l	Show only names of files that match
	-L	Show only names of files that don't match
	-c	Show only count of matching lines
	-o	Show only the matching part of line
	-q	Quiet. Return 0 if PATTERN is found, 1 otherwise
	-v	Select non-matching lines
	-s	Suppress open and read errors
	-r	Recurse
	-i	Ignore case
	-w	Match whole words only
	-x	Match whole lines only
	-F	PATTERN is a literal (not regexp)
	-E	PATTERN is an extended regexp
	-m N	Match up to N times per file
	-A N	Print N lines of trailing context
	-B N	Print N lines of leading context
	-C N	Same as '-A N -B N'
	-e PTRN	Pattern to match
	-f FILE	Read pattern from file

This output appears when I try to expand the command nixos-container create my-system --flake  and then tap TAB to complete.

@cxandru Hey, I think I found a cure.
I had a version of busybox installed in my nix profile as root user. I removed it from the root profile and since then I can access man pages again, do have colored git output and the weird behavior of the nixos-container command stopped.

I'm closing assuming OP has found a fix for the issue / got along somehow.


Support local files

Right now, the library does not support local file storage. This, of course, should be a thing that is essential to such a library. Are there any plans on supporting this?
Is there any way to override the URL checker?

Yes Janyk, we are working on this feature, very soon the library will support local files too.

it supports if you start the file path as file:///

It does play them, yes @kiyos88. However, you cannot put them into a playlist, as the url checker does not allow this.
Thanks for the update @jeancsanchez, I'm looking forward to it.

As in issue #9, I modified the code and temprary disable url checking for file. What your suggestion about url checking? How we do a better checking that allow file path?

Please see the issue #2

Hi , i have some issue here , in  5.0 and above versions its not working.... it just loading ...finally getting not responding ...please give a solution
Thanks in advance


release: 0.2.16

Codecov Report

Merging #40 (e20509a) into main (fcdd208) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main      #40   +/-   ##
=======================================
  Coverage   73.03%   73.03%
=======================================
  Files          10       10
  Lines        1042     1042
=======================================
  Hits          761      761
  Misses        281      281

Impacted Files
Coverage Δ

clippy-sarif/src/bin.rs
93.75% <100.00%> (ø)

hadolint-sarif/src/bin.rs
93.75% <100.00%> (ø)

sarif-fmt/src/bin.rs
57.48% <100.00%> (ø)

serde-sarif/src/lib.rs
100.00% <100.00%> (ø)

shellcheck-sarif/src/bin.rs
93.75% <100.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 fcdd208...e20509a. Read the comment docs.


Remove push-aur job

Description
This never built the PR job, and doesn't handle pushing to AUR
The new plan is to have a separate AUR-specific repo that handles events
& rebuilding on dependency-change etc
Closes #2819

Great job, looks good to me!


ci: disable windows free-thread build

Which issue does this PR close?

Rationale for this change
free threading build is currently broken on windows
https://github.com/apache/opendal/actions/runs/12470186276

This is due to the bug fix in https://github.com/PyO3/python3-dll-a/pull/84, we still need a pyo3 fix to make it work again. The previous build works but links to wrong python3.13.dll, I suggest let's disable windows free-threaded build for now.

can we release python package again?

Would you like to start a discussion for it? We can cut off a 0.51.1 release.

Any change create a branch from 0.51.0 and backport this PR without create a new release?

Hi, that's not allowed in the ASF. All releases must follow the release process and be verified by OpenDAL PMC members. Sorry, we must comply with the policy to protect our users from potential legal conflicts.

Any change create a branch from 0.51.0 and backport this PR without create a new release?

Hi, @Zheaoli has discovered that the 0.51.0-rc.3 release was successful. I reused the artifacts from there and published them to PyPI. Please double-check.


feat!: remove deprecated platform qt

Platforms affected
n/a
Motivation, Context & Description

Remove deprecated/archived platform qt from coho.
This platform no longer is supported and does not recieve updates.
Testing

n/a
Checklist

[ ] I've run the tests to see all new and existing tests pass
[ ] I added automated test coverage as appropriate for this change
[ ] Commit is prefixed with (platform) if this change only applies to one platform (e.g. (android))
[ ] If this Pull Request resolves an issue, I linked to the issue in the text above (and used the correct keyword to close issues using keywords)
[ ] I've updated the documentation if necessary

Codecov Report

Merging #313 (fe8dd33) into master (9967287) will decrease coverage by 1.83%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #313      +/-   ##
==========================================
- Coverage   58.73%   56.91%   -1.83%
==========================================
  Files           8        8
  Lines         492      492
==========================================
- Hits          289      280       -9
- Misses        203      212       +9

Impacted Files
Coverage Δ

src/repoutil.js
68.91% <ø> (ø)

... and 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Unable to compile Docker container via GH Actions

Seems like the pipeline is currently struggling to compile the container, with issues arising when AMD64 support was added to the build.
These errors are inconsistent in message too, but they point to the same aspect of the build:
------
 > [linux/arm64 build-worker 5/7] RUN dotnet restore "Discapp.Worker/Discapp.Worker.csproj":
27.06   Determining projects to restore...
90.05 /src/Discapp.Worker/Discapp.Worker.csproj : warning NU1900: Error occurred while getting package vulnerability data: Unable to cast object of type 'System.Net.Http.HttpRequestMessage' to type 'System.Text.Json.Serialization.Metadata.JsonPropertyInfo'.
90.05 /src/Discapp.Shared/Discapp.Shared.csproj : warning NU1900: Error occurred while getting package vulnerability data: Unable to cast object of type 'System.Net.Http.HttpRequestMessage' to type 'System.Text.Json.Serialization.Metadata.JsonPropertyInfo'. [/src/Discapp.Worker/Discapp.Worker.csproj]
93.27 Segmentation fault (core dumped)
------
Dockerfile:16
--------------------
  14 |     COPY Discapp.Worker/*.csproj Discapp.Worker/
  15 |     COPY Discapp.Shared/*.csproj Discapp.Shared/
  16 | >>> RUN dotnet restore "Discapp.Worker/Discapp.Worker.csproj"
  17 |     COPY . .
  18 |     RUN dotnet publish "Discapp.Worker/Discapp.Worker.csproj" -c Release -o /publish
--------------------

  > [linux/arm64 build-api 5/7] RUN dotnet restore "Discapp.API/Discapp.API.csproj":
28.07   Determining projects to restore...
29.68 /usr/share/dotnet/sdk/8.0.303/NuGet.targets(1113,5): error MSB4018: The "ConvertToAbsolutePath" task failed unexpectedly. [/src/Discapp.Shared/Discapp.Shared.csproj]
29.68 /usr/share/dotnet/sdk/8.0.303/NuGet.targets(1113,5): error MSB4018: System.ArgumentNullException: Parameter "Paths" cannot be null. [/src/Discapp.Shared/Discapp.Shared.csproj]
29.68 /usr/share/dotnet/sdk/8.0.303/NuGet.targets(1113,5): error MSB4018:    at Microsoft.Build.Shared.ErrorUtilities.ThrowArgumentNull(String parameterName, String resourceName) [/src/Discapp.Shared/Discapp.Shared.csproj]
29.68 /usr/share/dotnet/sdk/8.0.303/NuGet.targets(1113,5): error MSB4018:    at Microsoft.Build.Tasks.ConvertToAbsolutePath.Execute() [/src/Discapp.Shared/Discapp.Shared.csproj]
29.68 /usr/share/dotnet/sdk/8.0.303/NuGet.targets(1113,5): error MSB4018:    at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute() [/src/Discapp.Shared/Discapp.Shared.csproj]
29.68 /usr/share/dotnet/sdk/8.0.303/NuGet.targets(1113,5): error MSB4018:    at Microsoft.Build.BackEnd.TaskBuilder.ExecuteInstantiatedTask(ITaskExecutionHost taskExecutionHost, TaskLoggingContext taskLoggingContext, TaskHost taskHost, ItemBucket bucket, TaskExecutionMode howToExecuteTask) [/src/Discapp.Shared/Discapp.Shared.csproj]
------
Dockerfile:7
--------------------
   5 |     COPY Discapp.Shared/*.csproj Discapp.Shared/
   6 |
   7 | >>> RUN dotnet restore "Discapp.API/Discapp.API.csproj"
   8 |     COPY . .
   9 |     RUN dotnet publish "Discapp.API/Discapp.API.csproj" -c Release -o /publish
--------------------

This appears to be possibly related to the QEMU build process. Might perhaps switch to using a self-hosted ARM builder?

ARM64 builds disabled for now. To be clear, bizarrely this does compile on ARM, just not via GHA/QEMU for some strange reason.


Loss does not decrease accordingly

I'm running the training file using the Cityscapes datasets mentioned, however the loss does not decrease accordingly. In the beginningg it was around 2, in 90th epoch it's struggling around 1. All my hyper parameters are at default; the learning rate is 1e-2, momentum is 0.9 and weight decay is 1e-4.

Hi, maybe your lr is too large, try 0.001 instead.

Hi, maybe your lr is too large, try 0.001 instead.

@mertmerci Hi, I have the same situation as you. And I tried lr=0.001 or lr=0.0003, it still doesn't work. Have you solved this problem? what't your best training loss you can get now?

@mertmerci Hi, I have the same situation as you. And I tried lr=0.001 or lr=0.0003, it still doesn't work. Have you solved this problem? what't your best training loss you can get now?

I have not solved the problem yet. The best loss I can get is around 0.7.

I have not solved the problem yet. The best loss I can get is around 0.7.

Epoch: [ 5/500] Iter [ 345/ 647] || Time: 1166.8377 sec || lr: 0.00990037 || Loss: 0.6414
Epoch: [ 5/500] Iter [ 355/ 647] || Time: 1170.0967 sec || lr: 0.00990010 || Loss: 0.4728
Epoch: [ 5/500] Iter [ 365/ 647] || Time: 1173.3334 sec || lr: 0.00989982 || Loss: 0.6681
Epoch: [ 5/500] Iter [ 375/ 647] || Time: 1176.5961 sec || lr: 0.00989954 || Loss: 0.5141
Epoch: [ 5/500] Iter [ 385/ 647] || Time: 1179.8637 sec || lr: 0.00989926 || Loss: 0.4688
Epoch: [ 5/500] Iter [ 395/ 647] || Time: 1183.0879 sec || lr: 0.00989898 || Loss: 0.6347
Epoch: [ 5/500] Iter [ 405/ 647] || Time: 1186.2374 sec || lr: 0.00989870 || Loss: 0.4698
Epoch: [ 5/500] Iter [ 415/ 647] || Time: 1189.4530 sec || lr: 0.00989842 || Loss: 0.6898
Epoch: [ 5/500] Iter [ 425/ 647] || Time: 1192.6652 sec || lr: 0.00989815 || Loss: 0.5331
Epoch: [ 5/500] Iter [ 435/ 647] || Time: 1195.9574 sec || lr: 0.00989787 || Loss: 0.7055
Epoch: [ 5/500] Iter [ 445/ 647] || Time: 1199.3273 sec || lr: 0.00989759 || Loss: 0.5093
Epoch: [ 5/500] Iter [ 455/ 647] || Time: 1202.6462 sec || lr: 0.00989731 || Loss: 0.4337
Epoch: [ 5/500] Iter [ 465/ 647] || Time: 1205.8542 sec || lr: 0.00989703 || Loss: 0.4287
Epoch: [ 5/500] Iter [ 475/ 647] || Time: 1209.0492 sec || lr: 0.00989675 || Loss: 0.6152
Epoch: [ 5/500] Iter [ 485/ 647] || Time: 1212.3493 sec || lr: 0.00989647 || Loss: 1.2922
Epoch: [ 5/500] Iter [ 495/ 647] || Time: 1215.4831 sec || lr: 0.00989620 || Loss: 0.4719
Epoch: [ 5/500] Iter [ 505/ 647] || Time: 1218.5399 sec || lr: 0.00989592 || Loss: 0.9275
Epoch: [ 5/500] Iter [ 515/ 647] || Time: 1221.7445 sec || lr: 0.00989564 || Loss: 0.5310
Epoch: [ 5/500] Iter [ 525/ 647] || Time: 1224.8567 sec || lr: 0.00989536 || Loss: 0.7151
Epoch: [ 5/500] Iter [ 535/ 647] || Time: 1228.1229 sec || lr: 0.00989508 || Loss: 0.4688
Epoch: [ 5/500] Iter [ 545/ 647] || Time: 1231.3132 sec || lr: 0.00989480 || Loss: 0.5770
Epoch: [ 5/500] Iter [ 555/ 647] || Time: 1234.6185 sec || lr: 0.00989453 || Loss: 0.6590
Epoch: [ 5/500] Iter [ 565/ 647] || Time: 1238.0210 sec || lr: 0.00989425 || Loss: 0.3722

Epoch: [12/500] Iter [ 166/ 647] || Time: 2583.1239 sec || lr: 0.00977914 || Loss: 0.5476
Epoch: [12/500] Iter [ 176/ 647] || Time: 2586.6632 sec || lr: 0.00977886 || Loss: 0.7562
Epoch: [12/500] Iter [ 186/ 647] || Time: 2590.0186 sec || lr: 0.00977858 || Loss: 0.5186
Epoch: [12/500] Iter [ 196/ 647] || Time: 2593.0659 sec || lr: 0.00977830 || Loss: 1.0565
Epoch: [12/500] Iter [ 206/ 647] || Time: 2596.3114 sec || lr: 0.00977802 || Loss: 0.6302
Epoch: [12/500] Iter [ 216/ 647] || Time: 2599.6234 sec || lr: 0.00977774 || Loss: 0.5147
Epoch: [12/500] Iter [ 226/ 647] || Time: 2602.8056 sec || lr: 0.00977746 || Loss: 0.8301
Epoch: [12/500] Iter [ 236/ 647] || Time: 2605.9763 sec || lr: 0.00977718 || Loss: 0.5063
Epoch: [12/500] Iter [ 246/ 647] || Time: 2609.2808 sec || lr: 0.00977690 || Loss: 0.6625
Epoch: [12/500] Iter [ 256/ 647] || Time: 2612.6594 sec || lr: 0.00977663 || Loss: 0.6614
Epoch: [12/500] Iter [ 266/ 647] || Time: 2615.8317 sec || lr: 0.00977635 || Loss: 1.1284
Epoch: [12/500] Iter [ 276/ 647] || Time: 2619.1268 sec || lr: 0.00977607 || Loss: 0.6293
Epoch: [12/500] Iter [ 286/ 647] || Time: 2622.3897 sec || lr: 0.00977579 || Loss: 0.4887
Epoch: [12/500] Iter [ 296/ 647] || Time: 2625.7109 sec || lr: 0.00977551 || Loss: 0.6670
Epoch: [12/500] Iter [ 306/ 647] || Time: 2629.1389 sec || lr: 0.00977523 || Loss: 0.6722
Train my own data set, there are 2 categories (including background)

Epoch: [12/500] Iter [ 166/ 647] || Time: 2583.1239 sec || lr: 0.00977914 || Loss: 0.5476
Epoch: [12/500] Iter [ 176/ 647] || Time: 2586.6632 sec || lr: 0.00977886 || Loss: 0.7562
Epoch: [12/500] Iter [ 186/ 647] || Time: 2590.0186 sec || lr: 0.00977858 || Loss: 0.5186
Epoch: [12/500] Iter [ 196/ 647] || Time: 2593.0659 sec || lr: 0.00977830 || Loss: 1.0565
Epoch: [12/500] Iter [ 206/ 647] || Time: 2596.3114 sec || lr: 0.00977802 || Loss: 0.6302
Epoch: [12/500] Iter [ 216/ 647] || Time: 2599.6234 sec || lr: 0.00977774 || Loss: 0.5147
Epoch: [12/500] Iter [ 226/ 647] || Time: 2602.8056 sec || lr: 0.00977746 || Loss: 0.8301
Epoch: [12/500] Iter [ 236/ 647] || Time: 2605.9763 sec || lr: 0.00977718 || Loss: 0.5063
Epoch: [12/500] Iter [ 246/ 647] || Time: 2609.2808 sec || lr: 0.00977690 || Loss: 0.6625
Epoch: [12/500] Iter [ 256/ 647] || Time: 2612.6594 sec || lr: 0.00977663 || Loss: 0.6614
Epoch: [12/500] Iter [ 266/ 647] || Time: 2615.8317 sec || lr: 0.00977635 || Loss: 1.1284
Epoch: [12/500] Iter [ 276/ 647] || Time: 2619.1268 sec || lr: 0.00977607 || Loss: 0.6293
Epoch: [12/500] Iter [ 286/ 647] || Time: 2622.3897 sec || lr: 0.00977579 || Loss: 0.4887
Epoch: [12/500] Iter [ 296/ 647] || Time: 2625.7109 sec || lr: 0.00977551 || Loss: 0.6670
Epoch: [12/500] Iter [ 306/ 647] || Time: 2629.1389 sec || lr: 0.00977523 || Loss: 0.6722
Train my own data set, there are 2 categories (including background)

Please confirm that the label is correct, maybe we can talk through the WeChat more smoothly.

Epoch: [12/500] Iter [ 166/ 647] || Time: 2583.1239 sec || lr: 0.00977914 || Loss: 0.5476
Epoch: [12/500] Iter [ 176/ 647] || Time: 2586.6632 sec || lr: 0.00977886 || Loss: 0.7562
Epoch: [12/500] Iter [ 186/ 647] || Time: 2590.0186 sec || lr: 0.00977858 || Loss: 0.5186
Epoch: [12/500] Iter [ 196/ 647] || Time: 2593.0659 sec || lr: 0.00977830 || Loss: 1.0565
Epoch: [12/500] Iter [ 206/ 647] || Time: 2596.3114 sec || lr: 0.00977802 || Loss: 0.6302
Epoch: [12/500] Iter [ 216/ 647] || Time: 2599.6234 sec || lr: 0.00977774 || Loss: 0.5147
Epoch: [12/500] Iter [ 226/ 647] || Time: 2602.8056 sec || lr: 0.00977746 || Loss: 0.8301
Epoch: [12/500] Iter [ 236/ 647] || Time: 2605.9763 sec || lr: 0.00977718 || Loss: 0.5063
Epoch: [12/500] Iter [ 246/ 647] || Time: 2609.2808 sec || lr: 0.00977690 || Loss: 0.6625
Epoch: [12/500] Iter [ 256/ 647] || Time: 2612.6594 sec || lr: 0.00977663 || Loss: 0.6614
Epoch: [12/500] Iter [ 266/ 647] || Time: 2615.8317 sec || lr: 0.00977635 || Loss: 1.1284
Epoch: [12/500] Iter [ 276/ 647] || Time: 2619.1268 sec || lr: 0.00977607 || Loss: 0.6293
Epoch: [12/500] Iter [ 286/ 647] || Time: 2622.3897 sec || lr: 0.00977579 || Loss: 0.4887
Epoch: [12/500] Iter [ 296/ 647] || Time: 2625.7109 sec || lr: 0.00977551 || Loss: 0.6670
Epoch: [12/500] Iter [ 306/ 647] || Time: 2629.1389 sec || lr: 0.00977523 || Loss: 0.6722
Train my own data set, there are 2 categories (including background)

Please confirm that the label is correct, maybe we can talk through the WeChat more smoothly.

Thank you very much , and this is my wechat phone number,13716670388

Having the same problem. What was the solution?

I have the same problem. Have you solve this problem? Could you share us with your learning rate and batch_size? Thank you!


Modifications to Mopitt L3 reader

Reader updates for MOPITT L3 necessary for pairing with model data.

Fixed a naming inconsistency for apriori_prof
Moved -9999 missing data filter so that it is applied to all variables read in and not just to column.
Developed functions to build 3d pressure array and to combine partial apriori profile with surface apriori. Follows code in  https://github.com/NCAR/CAM-chem/blob/main/Python/advanced/apply_mopitt_AK_example.ipynb
Modified open_dataset to read in more than one variable and prepare for pairing observation and model.

Looks good - thanks for updating this Maggie!


Do we need to install Excel 2016 into azure SSIS?

Do we need to install any office components like excel into azure ssis? One of our packages uses the excel 2016 to create some files and we are getting the error when doing it.

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

ID: b3adb930-4c78-e69a-eeb9-d01e90e8aaa6
Version Independent ID: f0560a94-e26f-a7ae-aab2-301b0cc972f0
Content: Provision the Azure-SSIS Integration Runtime
Content Source: articles/data-factory/tutorial-deploy-ssis-packages-azure.md
Service: data-factory
GitHub Login: @swinarko
Microsoft Alias: sawinark

@Anmolgan81 Thanks for the Comment. We are actively investigating and will get back to you soon.

We already install Access Database Engine 2016, which is an Excel runtime lib, on SSIS IR to support Excel connectors.  If your package uses similar functionalities as those in Excel connectors, then you need not install additional libs, otherwise you need to do so via custom setup.

Hi @swinarko thanks for your comment, can we get on a skype call so that I can share what kind of package we are running and maybe we can fix this?

Sure, you have my email address already, so you can contact me directly and raise support tickets for future questions that need deeper investigations.

@Anmolgan81 We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


replace "dev" with "development"

What needs to happen?
Any instance of "dev" is changed to "development"
Why should we do this?
webpack uses "development" as a keyword, but we have "dev" as our own variable, and it just seems unnecessarily confusing
When does this need to get done?
No time line

But Webpack doesn't support a staging mode.  I basically have no problem using dev or development but conforming to webpack is not necessarily going to solve the staging part.  Do they let you define your own modes?

But Webpack doesn't support a staging mode. I basically have no problem using dev or development but conforming to webpack is not necessarily going to solve the staging part. Do they let you define your own modes?

Sorry, what does staging have to do with this issue? I'm confused now 😆

I know I'm probably overthinking this, but:
We usually talk about 3 different build/deploy configurations for AICS software: dev(development), stg(staging), and prod(production).   Webpack has modes development and production but they don't include a staging mode.
I'm just saying we should make sure we are not diverging away from general AICS deployment practices, so that our stuff is able to plug in to any devops deployment tooling.

Maybe this isn't important to do. I just know there was some issue in CFE where a script was expecting "development" but the "dev" var got sent in, and I thought it was easier to just use the word most packages use instead of keeping track. It might have been in either the gradle or Jenkins file, so it might not matter anymore.

Uncertain priority / scope, closing for now


[feature] search in Forum

Addresses: https://github.com/restarone/violet_rails/issues/567
forum_search.webm

⚠ the routing is broken, undo-ing release candidate:

@lascau


Resolve difference in META-INF/MANIFEST.MF files between 3.x and 4.x

Fix Gradle deprecation warnings
JAVA-3566
Evergreen patch: https://evergreen.mongodb.com/version/5e0cd44132f4171208419450
I used the bnd command-line tool to check the difference between the 3.x and 4.x versions of the manifest file. Using the command
bnd print <jar file>

the contents of the manifest file would be pretty-printed for easier examination. Running diff on the output of bnd print for the 3.x and 4.x JAR files provided clues on what changes needed to be made in the various build.gradle files. With these changes, most differences have been accounted for. One minor difference is the order of the attributes for packages in the Export-Package list. The order of the uses and version attributes has changed with the newer version of bnd. The other difference to note has to do with split packages - packages that are included in both Export-Package and Import-Package in the manifest. Split packages can be found in the JARs for driver-sync and driver-reactive-streams. With the newer version of bnd, the version attribute is not included with the package in Import-Package, but version continues to be included with the package in Export-Package. I found a couple of bugs filed on this, and the conclusion was that this behavior is normal.
As for the Gradle deprecations, the only deprecation warnings now come from plugin dependencies. Both SpotBugs and Spotless have fixes for these warnings that will be available in their next releases.

I'll review once Jeffs latest comments have been resolved

The differences mentioned at https://github.com/jstewart-mongo/mongo-java-driver/pull/87#issue-358512037 regarding the uses and version order and split packages are of note. We now no longer generate the JAR file for driver-benchmarks. Other than this, the new JAR files align well with the 3.x versions.

Just looked at reactive streams, and it doesn't look right:
~/mongo-java-driver ((d9172ee6d...))$ cat META-INF/MANIFEST.MF
Manifest-Version: 1.0
-exportcontents: *;-noimport:=true
Automatic-Module-Name: org.mongodb.driver.reactivestreams
Build-Version: 3.12.0-212-gd9172ee6d
Bundle-Version: 4.0.0-SNAPSHOT
Bundle-Name: mongodb-driver-reactivestreams
Bundle-SymbolicName: org.mongodb.driver-reactivestreams
Import-Package: org.bson.*,com.mongodb.*

This is the manifest that I see in the JAR:
Manifest-Version: 1.0
Automatic-Module-Name: org.mongodb.driver.reactivestreams
Bnd-LastModified:<PHONE_NUMBER>201
Build-Version: 3.12.0-212-gd9172ee6d
Bundle-ManifestVersion: 2
Bundle-Name: mongodb-driver-reactivestreams
Bundle-SymbolicName: org.mongodb.driver-reactivestreams
Bundle-Version: 4.0.0.SNAPSHOT
Created-By: 11.0.2 (Oracle Corporation)
Export-Package: com.mongodb.reactivestreams.client;uses:="com.mongodb,
 com.mongodb.annotations,com.mongodb.bulk,com.mongodb.client.model,com
 .mongodb.client.model.changestream,com.mongodb.client.result,com.mong
 odb.internal.async.client,com.mongodb.session,org.bson,org.bson.codec
 s.configuration,org.bson.conversions";version="4.0.0.SNAPSHOT",com.mo
 ngodb.reactivestreams.client.gridfs;uses:="com.mongodb,com.mongodb.an
 notations,com.mongodb.client.gridfs.model,com.mongodb.client.model,co
 m.mongodb.reactivestreams.client,org.bson,org.bson.conversions,org.bs
 on.types";version="4.0.0.SNAPSHOT",com.mongodb.reactivestreams.client
 .internal;uses:="com.mongodb,com.mongodb.client.gridfs.model,com.mong
 odb.client.model,com.mongodb.internal.async,com.mongodb.internal.asyn
 c.client,com.mongodb.internal.async.client.gridfs,com.mongodb.reactiv
 estreams.client,com.mongodb.reactivestreams.client.gridfs,org.bson,or
 g.bson.codecs.configuration,org.bson.conversions,org.bson.types";vers
 ion="4.0.0.SNAPSHOT",com.mongodb.reactivestreams.client.vault;uses:="
 com.mongodb,com.mongodb.client.model.vault,org.bson";version="4.0.0.S
 NAPSHOT"
Import-Package: org.bson;version="[4.0,5)",org.bson.codecs.configurati
 on;version="[4.0,5)",org.bson.conversions;version="[4.0,5)",org.bson.
 types;version="[4.0,5)",com.mongodb;version="[4.0,5)",com.mongodb.ann
 otations;version="[4.0,5)",com.mongodb.assertions;version="[4.0,5)",c
 om.mongodb.bulk;version="[4.0,5)",com.mongodb.client.gridfs.model;ver
 sion="[4.0,5)",com.mongodb.client.model;version="[4.0,5)",com.mongodb
 .client.model.changestream;version="[4.0,5)",com.mongodb.client.model
 .vault;version="[4.0,5)",com.mongodb.client.result;version="[4.0,5)",
 com.mongodb.diagnostics.logging;version="[4.0,5)",com.mongodb.interna
 l.async;version="[4.0,5)",com.mongodb.internal.async.client;version="
 [4.0,5)",com.mongodb.internal.async.client.gridfs;version="[4.0,5)",c
 om.mongodb.internal.async.client.vault;version="[4.0,5)",com.mongodb.
 lang;version="[4.0,5)",com.mongodb.session;version="[4.0,5)"
Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=1.8))"
Tool: Bnd-<IP_ADDRESS>911131708

I see the manifest you posted in build/tmp/jar/MANIFEST.MF.

Ah, you're right about the manifest.  My bad.


Delete VM is not working

Getting this error message:
The api-version '2016-03-30' is invalid. The supported versions are '2016-09-01,2016-07-01,2016-06-01,2016-02-01,2015-11-01,2015-01-01,2014-04-01-preview,2014-04-01,2014-01-01,2013-03-01,2014-02-26,2014-04'.: The api-version '2016-03-30' is invalid. The supported versions are '2016-09-01,2016-07-01,2016-06-01,2016-02-01,2015-11-01,2015-01-01,2014-04-01-preview,2014-04-01,2014-01-01,2013-03-01,2014-02-26,2014-04'.
at com.microsoft.azure.AzureClient.createExceptionFromResponse(AzureClient.java:521)
at com.microsoft.azure.AzureClient.access$000(AzureClient.java:34)
at com.microsoft.azure.AzureClient$3.call(AzureClient.java:281)
at com.microsoft.azure.AzureClient$3.call(AzureClient.java:278)
at rx.internal.operators.OnSubscribeMap$MapSubscriber.onNext(OnSubscribeMap.java:69)
at retrofit2.adapter.rxjava.RxJavaCallAdapterFactory$RequestArbiter.request(RxJavaCallAdapterFactory.java:173)
at rx.Subscriber.setProducer(Subscriber.java:211)
at rx.internal.operators.OnSubscribeMap$MapSubscriber.setProducer(OnSubscribeMap.java:102)
at retrofit2.adapter.rxjava.RxJavaCallAdapterFactory$CallOnSubscribe.call(RxJavaCallAdapterFactory.java:152)
at retrofit2.adapter.rxjava.RxJavaCallAdapterFactory$CallOnSubscribe.call(RxJavaCallAdapterFactory.java:138)
at rx.Observable.unsafeSubscribe(Observable.java:9861)
at rx.internal.operators.OnSubscribeMap.call(OnSubscribeMap.java:48)
at rx.internal.operators.OnSubscribeMap.call(OnSubscribeMap.java:33)
at rx.internal.operators.OnSubscribeLift.call(OnSubscribeLift.java:48)
at rx.internal.operators.OnSubscribeLift.call(OnSubscribeLift.java:30)
at rx.Observable.unsafeSubscribe(Observable.java:9861)
at rx.internal.operators.OnSubscribeMap.call(OnSubscribeMap.java:48)
at rx.internal.operators.OnSubscribeMap.call(OnSubscribeMap.java:33)
at rx.Observable.subscribe(Observable.java:9957)
at rx.Observable.subscribe(Observable.java:9924)
at rx.observables.BlockingObservable.subscribe(BlockingObservable.java:479)
at com.microsoft.azure.management.resources.fluentcore.arm.collection.implementation.GroupableResourcesImpl.deleteByGroup(GroupableResourcesImpl.java:60)

@puneet101 thanks for reporting, let me investigate.

I am unable to repro this, so to debug this further can you turn on the log and share the log, log level HttpLoggingInterceptor.Level.BASIC is sufficient which can be set as below:
            Azure azure = Azure
                    .configure()
                    .withLogLevel(HttpLoggingInterceptor.Level.BASIC)
                    .authenticate(credFile)
                    .withDefaultSubscription();

Oct 27, 2016 10:28:20 PM okhttp3.internal.Platform log
INFO: --> GET https://management.azure.com/subscriptions/1945149d-d86e-4767-b400-f03a7eb98cf0/resourceGroups/WORKSPOT-RG/providers/Microsoft.Compute/virtualMachines/azuredemo-0001?api-version=2016-03-30 http/1.1
Oct 27, 2016 10:28:20 PM okhttp3.internal.Platform log
INFO: <-- 200 OK https://management.azure.com/subscriptions/1945149d-d86e-4767-b400-f03a7eb98cf0/resourceGroups/WORKSPOT-RG/providers/Microsoft.Compute/virtualMachines/azuredemo-0001?api-version=2016-03-30 (75ms, unknown-length body)
Oct 27, 2016 10:28:20 PM okhttp3.internal.Platform log
INFO: --> DELETE https://management.azure.com/subscriptions/1945149d-d86e-4767-b400-f03a7eb98cf0/resourceGroups/%2Fsubscriptions%2F1945149d-d86e-4767-b400-f03a7eb98cf0%2FresourceGroups%2FWORKSPOT-RG%2Fproviders%2FMicrosoft.Compute%2FvirtualMachines%2Fazuredemo-0001/providers/Microsoft.Compute/virtualMachines/WORKSPOT-RG?api-version=2016-03-30 http/1.1 (0-byte body)
Oct 27, 2016 10:28:20 PM okhttp3.internal.Platform log
INFO: <-- 400 Bad Request https://management.azure.com/subscriptions/1945149d-d86e-4767-b400-f03a7eb98cf0/resourceGroups/%2Fsubscriptions%2F1945149d-d86e-4767-b400-f03a7eb98cf0%2FresourceGroups%2FWORKSPOT-RG%2Fproviders%2FMicrosoft.Compute%2FvirtualMachines%2Fazuredemo-0001/providers/Microsoft.Compute/virtualMachines/WORKSPOT-RG?api-version=2016-03-30 (25ms, 267-byte body)
22:28:20.909 [main] DEBUG c.w.connector.azure.AzureManager - Exception: The api-version '2016-03-30' is invalid. The supported versions are '2016-09-01,2016-07-01,2016-06-01,2016-02-01,2015-11-01,2015-01-01,2014-04-01-preview,2014-04-01,2014-01-01,2013-03-01,2014-02-26,2014-04'.
com.microsoft.azure.CloudException: The api-version '2016-03-30' is invalid. The supported versions are '2016-09-01,2016-07-01,2016-06-01,2016-02-01,2015-11-01,2015-01-01,2014-04-01-preview,2014-04-01,2014-01-01,2013-03-01,2014-02-26,2014-04'.: The api-version '2016-03-30' is invalid. The supported versions are '2016-09-01,2016-07-01,2016-06-01,2016-02-01,2015-11-01,2015-01-01,2014-04-01-preview,2014-04-01,2014-01-01,2013-03-01,2014-02-26,2014-04'.
at com.microsoft.azure.AzureClient.createExceptionFromResponse(AzureClient.java:521)
at com.microsoft.azure.AzureClient.access$000(AzureClient.java:34)
at com.microsoft.azure.AzureClient$3.call(AzureClient.java:281)
at com.microsoft.azure.AzureClient$3.call(AzureClient.java:278)
at rx.internal.operators.OnSubscribeMap$MapSubscriber.onNext(OnSubscribeMap.java:69)
at retrofit2.adapter.rxjava.RxJavaCallAdapterFactory$RequestArbiter.request(RxJavaCallAdapterFactory.java:173)
at rx.Subscriber.setProducer(Subscriber.java:211)
at rx.internal.operators.OnSubscribeMap$MapSubscriber.setProducer(OnSubscribeMap.java:102)
at retrofit2.adapter.rxjava.RxJavaCallAdapterFactory$CallOnSubscribe.call(RxJavaCallAdapterFactory.java:152)
at retrofit2.adapter.rxjava.RxJavaCallAdapterFactory$CallOnSubscribe.call(RxJavaCallAdapterFactory.java:138)
at rx.Observable.unsafeSubscribe(Observable.java:9861)
at rx.internal.operators.OnSubscribeMap.call(OnSubscribeMap.java:48)
at rx.internal.operators.OnSubscribeMap.call(OnSubscribeMap.java:33)
at rx.internal.operators.OnSubscribeLift.call(OnSubscribeLift.java:48)
at rx.internal.operators.OnSubscribeLift.call(OnSubscribeLift.java:30)
at rx.Observable.unsafeSubscribe(Observable.java:9861)
at rx.internal.operators.OnSubscribeMap.call(OnSubscribeMap.java:48)
at rx.internal.operators.OnSubscribeMap.call(OnSubscribeMap.java:33)
at rx.Observable.subscribe(Observable.java:9957)
at rx.Observable.subscribe(Observable.java:9924)
at rx.observables.BlockingObservable.subscribe(BlockingObservable.java:479)
at com.microsoft.azure.management.resources.fluentcore.arm.collection.implementation.GroupableResourcesImpl.deleteByGroup(GroupableResourcesImpl.java:60)
at com.workspot.connector.azure.AzureManager.deleteVM(AzureManager.java:1087)
We are using:
        VirtualMachine machine = azureInstance.virtualMachines().getById(vmUuid);
	String resourceGroup = machine.resourceGroupName();
	azureInstance.virtualMachines().deleteByGroup(vmUuid, resourceGroup);

	azureInstance.virtualMachines().deleteById(vmUuid);

seems to be working.
Can you share an example of
deleteByGroup(arg1, arg2)

Can you confirm you are using this method like below?
e.g. deleteByGroup("WORKSPOT-RG", "azuredemo-0001");
i.e. the first param is resource group name and second is virtual machine name, not id.

Yes, we were not using it correctly. False Alarm.
Is there a way to populate arg1, arg2 in the docs auto-generated to help avoid such mistakes. Thanks!

BTW, is there a way to delete VM w/ all it's dependencies? Looks like VM-delete does not delete all the internal resources like OS disk and network interface are not deleted.
Is there a sample to understand how to delete a VM with all the internal resources? Thanks!

Today the easiest way to handle this is - use one resource group per virtual machine and it's associated resources and delete the resource group when you want to clean up.
There is no option in the virtual machine delete API where we can specify a flag for this, i assume the reason is - resources such as NIC, subnet, storage account etc are not internal resources, they are top level resources that can exists without a virtual machine.
Regarding deleteByGroup - below is the comment for deleting a resource (e.g. VM) from a resource group, i don't think we use param names such as arg1, arg2, am i missing something?
void deleteByGroup(String groupName, String name)
  Deletes a resource from Azure, identifying it by its name and its resource group.
  Parameters:
  groupName - The group the resource is part of
  name - The name of the resource


Typo in Weights-only saving

There is a typo in the Weights-only saving example.
model.save_weights('my_model.weights.5')
It should be:
model.save_weights('my_model.weights.h5')
Please let me know I can raise a PR.

Thanks for reporting the issue. I have linked the PR here with correction.


Add connection tests for selecting binary uuid

Added the tests you mentioned in the last PR. I left out the array tests because it seems like the encoding is using json so it won't be able to cast the bytes properly all the time.

Yea arrays aren't supported in SQLite natively. We have to use json for that.


silentTranslationWarn true not working

Environment

Operating System: Windows_NT
Node Version:     v18.14.2
Nuxt Version:     3.5.1
Nitro Version:    2.4.1
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      typescript, modules, extends, runtimeConfig, app, routeRules, eslint, i18n, svgo, piniaPersistedstate, delayHydration
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction

Describe the bug
I'm not sure if this should work in dev or not, but it's not working and fallback warns are still printed to console like this:
[intlify] Not found 'yes' key in 'tr' locale messages.
[intlify] Fall back to translate 'yes' with root locale.

this is my i18n.config.ts:
export default defineI18nConfig(() => ({
  legacy: false,
  silentFallbackWarn: true,
}));

Additional context
I'm using 8.0.0-beta.12
Logs
No response

Thank you for your reporting!
We need minimal reproduction.
Issue bug report said:

Please use a template below to create a minimal reproduction, and provide to us your issue cases
👉 https://stackblitz.com/github/nuxt/starter/tree/v3-stackblitz
👉 https://codesandbox.io/p/github/nuxt/starter/v3-codesandbox

Could you give us your minimal reproduction please?

@kazupon please let me know if there's anything else missing

Hi!
Thank you for you reproduction!
I noticed that your i18n configuration has mis-taken.
To stop warnings in case of Translation Missing and Fallbacking, from Nuxt I18n v8 (vue-i18n v9), use the following options:
export default defineI18nConfig(() => ({
  legacy: false,
  fallbackWarn: false,
  missingWarn: false,
}));

I will close this issue, but please comment if you still have issue.
Happy coding! :)


[CMD/PKG] Adopted resource not replaced when using upgrade --install --force

Signed-off-by: Vaibhav Sharma<EMAIL_ADDRESS>
What this PR does / why we need it:
closes #11585
Adds the support for --force flag to be passed while performing an upgrade.
Special notes for your reviewer:
I saw a comment in the issue discussion regarding putting this behind a feature flag. I am not sure where such flags are maintained in the repo can someone please point that out to me.
If applicable:

[ ] this PR contains documentation
[ ] this PR contains unit tests
[ ] this PR has been tested for backwards compatibility

I saw a comment in the issue discussion regarding putting this behind a feature flag. I am not sure where such flags are maintained in the repo can someone please point that out to me.

The PR looks good to me. If --force is not specified, the default (false) is the existing value.

@gjenkins8 Any update on this ?

This makes sense. It enables adopted resources on install to be force restarted. This is required for force to work on upgrade with the install flag.


CAS-492 Serialise reconfigure

Ensure only one reconfigure task is active per-nexus at a time.
This is achieved by locking an async mutex at the start of Nexus::reconfigure().

Build failed:
* [continuous-integration/jenkins/branch](https://mayastor-ci.mayadata.io/job/Mayastor/job/staging/114/display/redirect)

@chriswldenyer I cancelled the build because you need to update the cargoSha256 first

bors retry

bors retry

bors retry

bors retry


Add EmDrive - Release 1 from Kerbal Stuff

This pull request was automatically generated by Kerbal Stuff on behalf of raptorep, to add EmDrive - Release 1 to CKAN.
Please direct questions about this pull request to raptorep.

From what I can tell..
GameData/Emdrive R1 is the main mod.
GameData/Flags is just a flag that isn't installed in the mod's folder.
GameData/TweakScal is a patch for tweakscale compat.
GameData/PartList I'm not sure which mod this is meant for.
So.. If all that is correct the TweakScale compatibility will need to be a seperate .netkan, and the same for the PartList folder. The flag can probably be ignored, and the EmDrive R1 folder name will potentially change (since R1 is short for Release 1).


Dataset load error with pandas 1.3.1

Cannot load mulitple dates when pandas 1.3.1 is installed, however, with 1.1.5 it works and also with a single date.
import climetlab as cml
cmlds = cml.load_dataset(
        'maelstrom-a1',
        size='5GB',
        parameter='air_temperature',
        dates=['2017-01-01', '2017-01-02']
    )
ds = cmlds.to_xarray()

gives the error message:
File "pandas/_libs/tslibs/conversion.pyx", line 298, in pandas._libs.tslibs.conversion.ensure_timedelta64ns
pandas._libs.tslibs.conversion.OutOfBoundsTimedelta: Out of bounds for nanosecond timedelta64[h] -2147483647 hours

SOLUTION: It is probably because the last leadtime in leadtime_predictor is undefined.

Solved by adding "leadtime_predictor" to drop_variables


Build fails on Ubuntu 22.04 (gcc)

Problem
Build fails using the instructions for Linux as provided
How to reproduce
git clone --recurse-submodules https://github.com/free-audio/clap-host
git fetch
git pull origin (up to date)
Changes made
sudo apt-get install ninja-build
sudo apt-get install gettext
sudo apt-get install bison
sudo apt-get install autoconf
make build file executable:
cd scripts
chmod +x build.sh
cd ..
scripts/build.sh
Result (as of 18Jun22)
error: building libb2:x64-linux-clap-host failed with: BUILD_FAILED
Please ensure you're using the latest port files with git pull and vcpkg update.
Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+libb2
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?template=report-package-build-failure.md&title=[libb2]+Build+error
Include '[libb2] Build error' in your bug report title, the following version information in your bug description, and attach any relevant failure logs from above.
vcpkg-tool version: 2022-06-15-b0f08e40f8e8752dd0b260138ee078bd9599559c
vcpkg-scripts version: ac6ef2f66 2022-06-15 (2 days ago)
You can also use the prefilled template from  clap/clap-host/vcpkg/installed/vcpkg/issue_body.md.

The github actions also runs on ubuntu.
See https://github.com/free-audio/clap-host/blob/main/.github/workflows/build.yml#L81

Thanks. but,the question was about building it on a an on-premises ubuntu desktop/server instead of the Github CI.
Edited the solution as above et voila !


Update sql database projects to 0.12.0 in insiders gallery

Build with VSIX: https://mssqltools.visualstudio.com/CrossPlatBuildScripts/_build/results?buildId=115233&view=artifacts&pathAsName=false&type=publishedArtifacts

Gallery updated!


It seems the interval is ignored.

It seems the interval is ignored. No matter what I put in there, the job is executed every second. Not, sure whether that is the purpose of 'seconds' cause it is not explained in the readme.
import time

from apscheduler.schedulers.background import BackgroundScheduler
from django_apscheduler.jobstores import DjangoJobStore, register_events, register_job

scheduler = BackgroundScheduler()
scheduler.add_jobstore(DjangoJobStore(), 'djangojobstore')

@register_job(scheduler, "interval", minutes=60, id="job1")
def test_job():
    #time.sleep(10)
    print("I'm the first test job!")
    # raise ValueError("Olala!")

register_events(scheduler)
scheduler.start()
print("Scheduler started!")

I think this is documented in upstream APScheduler - have a look at https://apscheduler.readthedocs.io/en/latest/modules/triggers/interval.html?highlight=interval#module-apscheduler.triggers.interval.


Mirror moci shared repo

resolution_fixed   |    by<EMAIL_ADDRESS>
Add moci (Met Office Coupling Infrastructure) to metoffice-mirror
https://code.metoffice.gov.uk/trac/moci

Issue migrated from trac:255 at 2024-01-31 18:22:06 +1100

<EMAIL_ADDRESS>commented

Repository is now mirrored and a fcm keyword has been added to accessdev

<EMAIL_ADDRESS>changed resolution from `` to fixed

<EMAIL_ADDRESS>changed status from new to closed


Missing Operations for TfLite GPU Delegate

System information

TensorFlow version (you are using):
on Android: 'org.tensorflow:tensorflow-lite:0.0.0-nightly' and 'org.tensorflow:tensorflow-lite-gpu:0.0.0-nightly'
Are you willing to contribute it (Yes/No): Yes to the best of my possibilities

Describe the feature and the current behavior/state.
I'm trying to use the GPU delegate for my custom tflite model. Creating the interpreter with the GPU delegate using this code:
 val options = Options()
options.setUseNNAPI(false)
options.setAllowFp16PrecisionForFp32(true)
options.setNumThreads(NUM_THREADS)
val gpuDelegate = GpuDelegate()
options.addDelegate(gpuDelegate)

d.tfLite = Interpreter( loadModelFile(assetManager)!!, options)

results in my model being run normally, hence delivering the correct outputs but not being accelerated by the GPU in my opinion, since the execution time is exactly the same as without using the delegate. Adding the line  d.tfLite!!.modifyGraphWithDelegate(gpuDelegate) (I don't know if this is necessary, it would also be nice to know?) results in the following error:
java.lang.IllegalArgumentException: Internal error: Failed to apply delegate: Next operations are not supported by GPU delegate:
    CONV_2D: Max version supported: 1. Requested version 2.
    LOCAL_RESPONSE_NORMALIZATION: Operation is not supported.
    SPLIT: Operation is not supported.
    First 0 operations will run on the GPU, and the remaining 12 on the CPU.ModifyGraphWithDelegate is disallowed when graph is immutable.
    java.lang.RuntimeException: java.lang.IllegalArgumentException: Internal error: Failed to apply delegate: Next operations are not supported by GPU delegate:
    CONV_2D: Max version supported: 1. Requested version 2.
    LOCAL_RESPONSE_NORMALIZATION: Operation is not supported.
    SPLIT: Operation is not supported.
    First 0 operations will run on the GPU, and the remaining 12 on the CPU.ModifyGraphWithDelegate is disallowed when graph is immutable.

So first of all: It would be nice to have those unsupported operations, i.e.

CONV_2D v2
LOCAL_RESPONSE_NORMALIZATION
SPLIT

Second of all: what does ModifyGraphWithDelegate is disallowed when graph is immutable mean? Do I have to make any changes to my tflite model?

@impjdi are there any plans to support dilation with GPU conv?

@jdduke IIRC we have dilation for all our conv operators.  What is different in CONV_2D v2 vs. v1?
@Noltibus

We have limited resource, and probably can't accommodate individual requests of op shader implementations.  We'll keep your request in mind.

The error message is coming from //tensorflow/lite/core/subgraph.cc... you can grep for that.  I have the impression you're calling ModifyGraphWithDelegate twice or maybe after AllocateTensors or something?  I'm not entirely sure when a graph is considered immutable without studying the code path.

IIRC we have dilation for all our conv operators. What is different in CONV_2D v2 vs. v1?

v2 will have dilation values that aren't 1. If that's supported, we can update the GPU delegate to handle that version.

Is there any way I can help with those operations. For example, the SPLIT operator? It might be somewhat similar to the SLICE operator?

IIRC we have dilation for all our conv operators. What is different in CONV_2D v2 vs. v1?

v2 will have dilation values that aren't 1. If that's supported, we can update the GPU delegate to handle that version.

Does that mean CONV v2 is "almost" supported?

@Noltibus
Yeah, I have a change that will open it up which is being reviewed.  In the meantime, you can just comment out the CONV_2D operator's version check in //tensorflow/lite/delegates/gpu/common/model_builder.ccand things should just work.

Ok, thank you!! So you will keep my request for LRN in mind? Is there any way I can help with SPLIT. I never wrote an Operation before but I learn pretty quickly ;-)

@Noltibus
Sure thing.  This is an open source project, and contributions are welcome :)
Before you dig into the shader code, I would advise to understand the DHWC4 format (or PHWC4... we renamed the format at one point) first.  It's essentially slicing a HWC tensor into 4-channel slices; that's used throughout the OpenGL delegate.  I'm not so sure about the OpenCL delegate; it has more complicated formats.
Then, when it comes to the shader code, OpenGL delegate uses shader code generation to avoid code duplication, but unfortunately, it makes reading & understanding hard.  OpenCL doesn't use the code generation logic and might be easier to author one.  After that, you want to also write some unit tests to make sure things work as intended.
Of course, the easiest is to find the closest op implementation and modifying that :)

@Noltibus
hi i'm running posenet example of Tensorflow lite.
i got a same issue in GPU Delegate.
i found where this app select CPU,GPU, NNAPI.
that file is at android/posenet/src/main/java/org.tensorflow.lite.examples.posenet.lib/Posenet.kt
Unfortunately, posenet example is written of kotlin. so i can't insert your same java code.
i modified,
`class Posenet(
val context: Context,
val filename: String = "posenet_model.tflite",
val device: Device = Device.GPU
) : AutoCloseable {
var lastInferenceTimeNanos: Long = -1
private set
/** An Interpreter for the TFLite model.   */
private var interpreter: Interpreter? = null
private var gpuDelegate: GpuDelegate? = null
private fun getInterpreter(): Interpreter {
if (interpreter != null) {
return interpreter!!
}
val options = Interpreter.Options()
when (device) {
Device.CPU -> { }
Device.GPU -> {
gpuDelegate = GpuDelegate()
options.addDelegate(gpuDelegate)
options.setNumThreads(4)
options.setAllowFp16PrecisionForFp32(true)
}`
but it doesn't change fps. i guess that i just change name of device, not device's actual running.
how can i use correctly device's GPU? how can i modify?
And.. why you insert
options.setAllowFp16PrecisionForFp32(true) options.setNumThreads(NUM_THREADS)
this line?
if this is absent, it doesn'y use GPU?

@terryheo can help further diagnose.

@eQueue you don't need set threads for GPU.
Just changing
val device: Device = Device.CPU

to
val device: Device = Device.GPU

is enough for Posenet example.
BTW, I've found that the current Posenet example depends on TFLite 2.0.0. I'll update it to use TFLite 2.2.0 which gives slightly better performance.
In my testing GPU gives about 35ms inference time with Posenet model.

@Noltibus Is this still an issue ?
Please refer to the comment above and let us know ?Thanks!

According to the documentation here: https://www.tensorflow.org/lite/performance/gpu_advanced none of the operations I listed above are supported, yet, so this is an ongoing issue for me.

Our documentation is not always up to date.  You want to check the source code ;)
LOCAL_RESPONSE_NORMALIZATION <- I've never seen this op and it's unlikely that we'll add this.
SPLIT <- depending on the axis, this might be supported or not.
Also, it might be good to upgrade from 0.0.0 to whatever is at the top of the master branch.

@Noltibus,
As requested the changes were made with the commit 98203f8. Kindly take a look at the model_builder.cc file where split_node was added.
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/lite/delegates/gpu/common/model_builder.cc
    Node* split_node = graph->NewNode();
    RETURN_IF_ERROR(reader->AddInput(split_node, 0));
    {
      SplitAttributes split_attr;
      split_attr.axis = Axis::CHANNELS;
      split_node->operation.type = ToString(OperationType::SPLIT);
      split_node->operation.attributes = split_attr;
    }

Closing this as stale. Please reopen if this is still a valid request.


Item Level Stat Sync for Eurekan Elemental Weapons/Gear Broken in Eureka

Prior to 7.1 they were displaying the synced stats properly (item level 300), but now it doesn't anymore.
For example, the substat max in the main weapon is actually 114 (ignoring Elemental stat).
Not sure if it's because the game isn't saying they're synced anymore? But they still are, a simple way to test is by melding materia on the Elemental +2 gear (or Kirin/Vermilion) to verify no changes.

Thanks for the report, looks like this is a bug in Dalamud. I've created a PR on the side of ClientStructs that should mitigate the issue once its merged https://github.com/aers/FFXIVClientStructs/pull/1233


UWP packaged app leaves files locked after closing

Not sure if this is somehow an upstream Electron issue that only manifests itself in UWP packaged apps.
Basically I'm packaging my application like so
  const child = spawn(
    path.resolve(__dirname, 'node_modules', '.bin', 'electron-windows-store.cmd'),
    [
      '--input-directory',
      '"dist\\Google Play Music Desktop Player-win32-ia32"',
      '--output-directory',
      'dist\\uwp',
      '--flatten',
      'true',
      '--package-version',
      '<IP_ADDRESS>',
      '--package-name',
      'GPMDP',
      '--package-display-name',
      'Google Play Music Desktop Player',
      '--package-executable',
      'Google Play Music Desktop Player.exe'
    ]
  );

  // spit stdout to screen
  child.stdout.on('data', (data) => process.stdout.write(data));

  // Send stderr to the main console
  child.stderr.on('data', (data) => process.stderr.write(data));

  child.on('close', (code) => {
    done();
  });

So pretty standard I think.  When I run the application it launches correctly 🎉 And everything appears to work.
However when I close the application and attempt to run the normal non-UWP win32 version I get a load of "resource locked" errors on the shared files that I create while running the app (Settings and generic Data Storage).

Is this a limitation of the appx magic that is happening because I had to reboot my PC to get those files unlocked which is an absolute nightmare when developing 😢

I assume this is actually not an error inside Electron, but totally with Windows. I hope that Microsoft will get that fixed before Project Centennial launches publically.

This should now be fixed in Windows itself, so I'm closing this.


No member named 'cancelButtonTintColor' in 'JS::NativeActionSheetManager::SpecShowActionSheetWithOptionsOptions'

Description
How to fix this error.    I have created simple project with latest version and when try to build the project via Xcode it generate error?
Version
0.67.3
Output of npx react-native info
System:
OS: macOS 11.5.2
CPU: (8) x64 Intel(R) Core(TM) i7-4980HQ CPU @ 2.80GHz
Memory: 83.30 MB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 14.18.2 - /usr/local/opt/node@14/bin/node
Yarn: 1.22.15 - /usr/local/bin/yarn
npm: 6.14.15 - /usr/local/opt/node@14/bin/npm
Watchman: Not Found
Managers:
CocoaPods: 1.11.2 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.2, iOS 15.2, macOS 12.1, tvOS 15.2, watchOS 8.3
Android SDK: Not Found
IDEs:
Android Studio: 2020.3 AI-203.7717.56.2031.7583922
Xcode: 13.2.1/13C100 - /usr/bin/xcodebuild
Languages:
Java: 15.0.2 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.67.3 => 0.67.3
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
Please init new react native project with command and try to build the project in the xcode after pod install
Snack, code example, screenshot, or link to a repository

Having the same issue here

any one got the solution ?

Hey guys, same error here but with a strange behaviour. If I try to build from terminal with "npm run ios" i got the error, but if I open the xCode project with xCode and clean and rebuild everything works fine, even from the terminal.

Was having these same issues, and the problem for me ended up being that i had postinstall scripts ignored. Can't really confirm whether that's the root cause, but re-enabling postinstall (removing --ignore-scripts from npm or yarn whichever you use), fixed it for me 🤷

@vsmobiledevs Thanks for the tip !
Here is the patch file content to create inside patches directory in root directory (patches/react-native+0.67.3.patch) for npx patch-package during postinstall script
diff --git a/node_modules/react-native/React/CoreModules/RCTActionSheetManager.mm b/node_modules/react-native/React/CoreModules/RCTActionSheetManager.mm
index 5cd782e..d60e510 100644
--- a/node_modules/react-native/React/CoreModules/RCTActionSheetManager.mm
+++ b/node_modules/react-native/React/CoreModules/RCTActionSheetManager.mm
@@ -94,8 +94,8 @@ RCT_EXPORT_METHOD(showActionSheetWithOptions
   UIViewController *controller = RCTPresentedViewController();
   NSNumber *anchor = [RCTConvert NSNumber:options.anchor() ? @(*options.anchor()) : nil];
   UIColor *tintColor = [RCTConvert UIColor:options.tintColor() ? @(*options.tintColor()) : nil];
-  UIColor *cancelButtonTintColor =
-      [RCTConvert UIColor:options.cancelButtonTintColor() ? @(*options.cancelButtonTintColor()) : nil];
+  UIColor *cancelButtonTintColor = [RCTConvert UIColor:options.tintColor() ?
+      @(*options.tintColor()) : nil];

   if (controller == nil) {
     RCTLogError(

Update: resolved this error by clearing the build from xcode and building the app again

If you are installing new modules do the following:

Ensure to go to the IOS folder and run pod install.
Open the .workspace file and run CMD + SHIFT + K (Clean the project)
Run Again.

The same problem happened.
error: no member named 'cancelButtonTintColor' in 'JS::NativeActionSheetManager::SpecShowActionSheetWithOptionsOptions'


Translations update from Weblate

Translations update from Weblate for Playbooks/webapp.
Current translation status:

Hello @weblate,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

Partial Spanish translation to test Weblate webook.

OK, the flow reflected in weblate correctly. @calebroseland let me know when you want to unlock the component to outside contributors.


net/http: http.DialContext breaks existing code

In Go 1.7 the new http.Transport.DialContext field overrides the Dial field.
This breaks any existing code that takes the http.DefaultTransport,
sets Dial and expects network calls to be made using that value.
This did actually break some of our test code that used this functionality
to prevent accidental external network access in tests.
For better backward compatibility, perhaps it might be better to make Dial
override DialContext - existing code will continue to work unchanged
and most new code will never touch Dial, so the override isn't so important
in that case.

This might've been something to consider changing during the betas or first 5 release candidates. Too late now, though.
There might be something we could add to the Go 1 compatibility document (similar to what we added about unkeyed struct literals) about promises (or lack thereof?) here.

Sorry for the late report - I only encountered the issue this morning. I can accept that it won't be changed now, but I think perhaps the issue points towards a better way to do compatibility in general. I would certainly have been inclined to give precedence to new fields until I saw this.

I went to document this, but I'm not sure what to document.
Closing for now, but please reopen if you have suggestions.


Add verbose Sierra output to Scarb

Problem
Scarb compilation step creates Sierra output but without human-readable names.
Proposed Solution
It would be great to move to human readable Sierra by default or alternatively add a flag scarb build -r which would map to cairo-compile -r.
Notes
Reading Sierra code will be useful for performance optimization.

Note: as a temporary measure I've added the following command to Makefile in the default Cairo template: https://github.com/auditless/cairo-template/blob/main/Makefile#L4.


TrustKit.sharedInstance().pinningValidator.handle(challenge, completionHandler: completionHandler)

TrustKit.sharedInstance().pinningValidator.handle(challenge, completionHandler: completionHandler)
Always return false
configured & unconfigured all domains are successful.
Already enabled kTSKEnforcePinning = true

Was facing the same issue with React native .

Hi @anishtr4 As of now I didn't get any solution.

@Ramprasathselvam ,
the pinning validator wont look /validate the unpinned domain. Trustkit only validate the request which are being made to the pinned domain to verify whether the provided public-key is valid for the pinned domain.
@nabla-c0d3  can you please confirm this then i think you can close this ticket as well.


fix: fix mis-merge with 3 days old data

commit c50239b4f476f87119eceb33f9343dadcf271314 reverted back to old data.

Thanks for this, can you please rebase to resolve the conflicts (since the scrapers still run to update the data)

done 😉

Thanks a lot @dr-itz


Challenge validation failed

Challenge validation is occurring on port 80 which my server does not listen on. How can I get the URL to be HTTPS for the validation?
See the relevant sections in below full error where is says Fetching HTTP... and lower on PORT 80.
 + Challenge validation has failed :(
ERROR: Challenge is invalid! (returned: invalid) (result: {
  "type": "http-01",
  "status": "invalid",
  "error": {
    "type": "urn:acme:error:connection",
    "detail": "Fetching http://mydomain.hopto.org/.well-known/acme-challenge/cnIJifPA7EHQPCBBuhUoxxxxpJLxcUChlP6RvR_Udwg: Timeout during connect (likely firewall problem)",
    "status": 400
  },
  "uri": "https://acme-staging.api.letsencrypt.org/acme/challenge/u4EBhGAy-AwER19ZbOxxxxhwiqdfmLJbxz1bsE4dEBg/331778724",
  "token": "cnIJifPA7EHQPCBBuhUoxxxxpJLxcUChlP6RvR_Udwg",
  "validationRecord": [
    {
      "url": "http://mydomain.hopto.org/.well-known/acme-challenge/cnIJifPA7EHQPCBBuhUoxxxxpJLxcUChlP6RvR_Udwg",
      "hostname": "mydomain.hopto.org",
      "port": "80",
      "addressesResolved": [
        "7x.xx.xx.xxx"
      ],
      "addressUsed": "7x.xx.xx.xxx"
    }
  ]
})

http-01 verification will always use port 80. if you need verification over port 443 you'll have to use tls-alpn verification, which is a bit more complicated. see the docs for more information.


Does not run in LinqPad

Steps to reproduce

Open LinqPAD 5 (Developer Edition)
add the following NuGet packages:

Tensorflow.NET 0.9.0

This will also install the following packages:

Google.Protobuf 3.8.0
Microsoft.ML.TensorFlow.Redist 0.14.0
NumSharp 0.10.3

insert the following code

var m = new double[,] { { 1.0, 2.0 }, {3.0,4.0} };
var c = tf.constant(m);
c.Dump();

Execute

Current Behaviour
I get a DllNotFoundException;
Unable to load DLL 'tensorflow': The specified module could not be found. (Exception from HRESULT: 0x8007007E) | Unable to load DLL 'tensorflow': The specified module could not be found. (Exception from HRESULT: 0x8007007E)

Stacktrace:
at Tensorflow.c_api.TFE_NewContextOptions()   at Tensorflow.Eager.ContextOptions..ctor()   at Tensorflow.tf..cctor() | at Tensorflow.c_api.TFE_NewContextOptions()   at Tensorflow.Eager.ContextOptions..ctor()   at Tensorflow.tf..cctor()

Apparently the problem lies with the [DllImport("tensorflow", EntryPoint="TFE_NewContextOptions")] statement.

same issue with Tensorflow.NET 0.10.0-rc

apparently the issue is because LinqPad runs in x86/32 bit mode.

@MovGP0 What's LinqPad ? TensorFlow only run x64 platform.

LinqPad is kinda like Python's Jupiter Notebook, but for C#, F# and SQL.
https://www.linqpad.net/

Understand, You can try SciSharp Cube with Jupyter Notebook built-in.

That problem might be caused by the common issue the native tensorflow lib cannot be loaded automatically. You can try install tensorflow to a location like one dir in PATH in advance.

Thanks for the tipp 👍 I still think that it should work with both.
Simply unsure if it's better to run LinqPad in x64 mode or rather modify the Tensorflow.NET NuGet to work with both, x68 and x64 dll, dependent on the build target.
Maybe a init.ps1 script that modifies the .csproj file such that there is something like the following
<!-- pseudocode -->
<ItemGroup>
<Reference Condition="'$(Platform)' = 'x86'" Include="tensorflow">
   <HintPath>..\lib\tensorflow-x86.dll</HintPath>
</Reference>
<Reference Condition="'$(Platform)' = 'x64'" Include="tensorflow">
   <HintPath>..\lib\tensorflow-x64.dll</HintPath>
</Reference>
</ItemGroup>

@MovGP0 TensorFlow only works on x64 platform. Try to use the preview 0.10.0rc.


Fixed example code of edit-text

fixed this error:
[bot.error.event] TypeError: Cannot read property 'message_id' of undefined
    at bot.sendMessage.then.re (/home/eko24/workspace/wasteland-charisma-calculator-bot/bot2.js:34:43)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:118:7)

Thank you for merging this @mullwar, may I ask you to have a look at https://github.com/mullwar/telebot/issues/132 ?

@eko24ive yep, I’ll take a look.

god bless you sir


⚠ Bofrost.at has degraded performance

In 9fa7e2f, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 3156 ms

Resolved: Bofrost.at performance has improved in f354d2c.


[W6.2][F11-B2] Phua Han Siang

Accepting this PR after minimal review because another of your PRs for this tutorial was reviewed in detail.


conky: 1.12.2 -> 1.13.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/conky/versions.
meta.description for conky is: "Advanced, highly configurable system monitor based on torsmo"
meta.homepage for conky is: "http://conky.sourceforge.net/"
meta.changelog for conky is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.13.1 with grep in /nix/store/q6avv3hgfqykymwb7z1dsbgylr86hs3n-conky-1.13.1
found 1.13.1 in filename of file in /nix/store/q6avv3hgfqykymwb7z1dsbgylr86hs3n-conky-1.13.1

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
conky

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/q6avv3hgfqykymwb7z1dsbgylr86hs3n-conky-1.13.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A conky https://github.com/r-ryantm/nixpkgs/archive/c4ee6537fa8180103185090ff027318623c3f90c.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/q6avv3hgfqykymwb7z1dsbgylr86hs3n-conky-1.13.1
ls -la /nix/store/q6avv3hgfqykymwb7z1dsbgylr86hs3n-conky-1.13.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

conky

Maintainer pings
cc @dguibert for testing.

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

1 package built:

conky


Integration trash-ai in citizen science project

Hi Everyone,
In terms of my master thesis I am developping a mobile application to gather data about the waste consumption on the island of Aruba. I am trying to integrate the trash-ai algorithm, so that users just have to take a photo of their trash and the trash can be recognized by the algorithm (and than later saved in a database).
I am a newbie in software, and certainly in docker, AWS, ... . I just want to communicate with the trashai API. So that I can send post requests (with the photo) and get a response that has the information of the recognized data.
Currently I am trying deploy the application locally (with docker) on the google cloud shell. But I am totally not sure if this is the right way and I am also really struggling to get it on GCS.
Could someone help me please?

Hi, I know I wasn't the one who initiated the request but I do have a relevant question, me and my friends wanted to use an API of this model for an app we are building (open-source), and we have a paged dedicated to trash classification. Now I was looking for a specific endpoint that I can upload and retrieve an image through the app because the web app does not help with this task. Let me know if you have anything currently that could help me.
Thank you!

Thanks for reaching out! An API isn't built yet but would be a welcomed
addition to the tool if you can build it.
On Tue, Oct 24, 2023, 9:38 AM DhruvSingh0905 @.***>
wrote:

Hi, I know I wasn't the one who initiated the request but I do have a
relevant question, me and my friends wanted to use an API of this model for
an app we are building (open-source), and we have a paged dedicated to
trash classification. Now I was looking for a specific endpoint that I can
upload and retrieve an image through the app because the web app does not
help with this task. Let me know if you have anything currently that could
help me.
Thank you!
—
Reply to this email directly, view it on GitHub
https://github.com/code4sac/trash-ai/issues/130#issuecomment-1777615598,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGMUJU475AOQGBDMFSR7YNTYA7VHJAVCNFSM6AAAAAAWEMC5KSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZXGYYTKNJZHA
.
You are receiving this because you commented.Message ID:
@.***>

Would be happy to build it out and add it, would need access to the model itself, I do believe I already have the code for mapping the classifications. I looked through GitHub and Docker, but I could not find the model itself. If you have a directory or a link, I could start building it.

This should help to get the model up and running:
https://github.com/code4sac/trash-ai/tree/aws/trashai-staging/model/build
On Thu, Oct 26, 2023, 12:25 PM DhruvSingh0905 @.***>
wrote:

Would be happy to build it out and add it, would need access to the model
itself, I do believe I already have the code for mapping the
classifications. I looked through GitHub and Docker, but I could not find
the model itself. If you have a directory or a link, I could start building
it.
—
Reply to this email directly, view it on GitHub
https://github.com/code4sac/trash-ai/issues/130#issuecomment-1781769296,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGMUJUY7TVLSYCTRRGOE27TYBK2KBAVCNFSM6AAAAAAWEMC5KSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBRG43DSMRZGY
.
You are receiving this because you commented.Message ID:
@.***>


Ability to fix X axis min,max and switch to log on both axis

Ability to fix X axis max and switch to log on both axis
Also show the target url on page
(Needed to patch in
https://github.com/chartjs/Chart.js/pull/4198
In order to get https://github.com/chartjs/Chart.js/issues/4939
Axis type switching to work)

Thx ! I test on chrome and safari mac myself
Added a custom build from my branch with all the fixes and removing the unused modules,
that shaved about 1/3rd of the minified size
https://github.com/ldemailly/Chart.js/commit/d71f4184bdd017a680a04c6168cd52a147724bac

note that you need to ctrl or shift reload to get the .js otherwise log won't work


Update brachiograph.py

Hi,
What is the reason for this change? Can you please explain it?
The way I see it, it only breaks the f-string, so the print won't work correctly anymore.
If you need to support python before 3.6, you need to replace this with a "".format()

@balakrishnankom BrachioGraph uses f-strings, and requires Python 3.6 or later.


pin hvad to < 1.0.0

aldryn addons that support hvad are not yet supporting this newer hvad version

:+1:
would be cool to add a comment about why we pinned the version.

btw: individual packages should also add the <1.0.0 dependency, as long as they are not compatible to both <1.0.0 and >=1.0.0. (/cc @mkoistinen ). Our build process will complain if there are incompatible dependencies.


Add list of supported data sources and status/counters on home page

It would be useful to report the set of importers and their status on the VCIO homepage

@poju3185 go ahead!

Hi @pombredanne, could you please clarify what specific information or metrics you are referring to when you mention "status"?

@poju3185 I am returning the question :)
Given the data model, and the data sources we support, what could be helpful for a new user or a returning user to know?

May be the list of importers? And some information about when they lats run?
Same for improvers?
Some counts of package/package versions/vulnerabilities and advisories?

What else would you have liked to know?
@DennisClark ping

i would suggest:

list of importers: the specific importer name and the last date (full timestamp) it was run.
list of improvers: the specific improver name and the last date (full timestamp) it was run.
list of the 25 most recent vulnerabilities imported or improved, with links to a public VCIO instance.

list of the 25 most recent vulnerabilities imported or improved, with links to a public VCIO instance.

I see these as being links on the current instance, would you agree?

@DennisClark @pombredanne, thank you for your guidence and suggestion, I will first try to implement these:

list of importers: the specific importer name and the last date (full timestamp) it was run.
list of improvers: the specific improver name and the last date (full timestamp) it was run.
list of the 25 most recent vulnerabilities imported or improved, with links to a public VCIO instance.

Will report here if I have any progress. Thanks again.

This is my current progress, may I ask if there's anything that needs improvement?
https://github.com/nexB/vulnerablecode/assets/81625625/6280f48d-c620-45d6-b0d3-f9829c8abbe8


Rename edge entry point from devices to fleet-management

Rename devices to fleet management
Since we need some entry point and devices page should not be just another inventory view let's change devices route to fleet-management.
Merge after: https://github.com/RedHatInsights/cloud-services-config/pull/589

Codecov Report

Merging #31 (ebfeb95) into master (03f40a8) will decrease coverage by 1.43%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master      #31      +/-   ##
==========================================
- Coverage   50.34%   48.91%   -1.44%
==========================================
  Files          37       40       +3
  Lines         431      460      +29
  Branches       46       48       +2
==========================================
+ Hits          217      225       +8
- Misses        192      211      +19
- Partials       22       24       +2

Impacted Files
Coverage Δ

src/App.js
0.00% <0.00%> (ø)

src/Routes.js
0.00% <ø> (ø)

src/Routes/DeviceDetail/DeviceDetail.js
0.00% <ø> (ø)

src/Routes/Devices/Devices.js
0.00% <ø> (ø)

src/store/actions.js
83.33% <0.00%> (-16.67%)
:arrow_down:

src/api/index.js
80.76% <0.00%> (-1.24%)
:arrow_down:

src/store/action-types.js
100.00% <0.00%> (ø)

src/components/Tiles.js
0.00% <0.00%> (ø)

src/store/images.js
100.00% <0.00%> (ø)

... and 1 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 03f40a8...ebfeb95. Read the comment docs.


Consistentcy in FaceQuadratureInterpolator and pa_data

When applying FaceQuadratureInterpolator to a field it returns the data in the order <quad, dim, nf>; while pa_data will organize it in terms of <dim, quad, nf> (ex. DG trace pa setup kernels)
QuadratureInterpolator has a method to switch between layouts,
SetOutputLayout(QVectorLayout::byVDIM);
Can something like that be introduced to FaceQuadratureInterpolator to maintain consistency?

@artv3 Could you be a bit more specific on which kernels you are thinking of?
Here is one in quadinterpolator_face.cpp:FaceQuadratureInterpolator::Eval3D:
nor(q1,q2,0,f) = n[0]/norm;

Here is another in bilininteg_dgtrace_pa.cpp:PADGTraceSetup3D:
qd(q1,q2,0,0,f) = w*( alpha/2 * dot + beta * abs );

They both seem to use <quad, dim, nf> ordering.

yes, right above that when you take the velocity
https://github.com/mfem/mfem/blob/5308d285f732c45f3c381bcee415581fd34b1cb2/fem/bilininteg_dgtrace_pa.cpp#L95-L97
the ordering is <dim, quad, nf> so if the user wants to provide the velocity we have to flip the layout from what FaceQuadrature interpolator gives which is <quad, dim, nf> to <dim, quad, nf>

I have an application where I compute the velocity and I would like to pass that to mfem in a container.

Ok, I can change that, the only question is if it will impact codes using VectorQuadratureFunctionCoefficient, do you use that? Technically it may break backward compatibility.

I think we just need to add a method to switch between the layouts in FaceQuadratureInterpolator, that shouldn't break things.

We could still do something like in qinterp eval for the layout if we can't wait for a more generic way to handle it.

This can be done as part of #1656. The idea will be to make sure we can evaluate GridFunctionCoefficients on face quadrature spaces, so that the resulting data is ordered as needed by the face quadrature space which will then be used inside face-based PA kernels.

This issue will be addressed as part of the unification of #1656 and #2891, so I'll close it.


mwic: 0.7.9 -> 0.7.10

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/jwilk/mwic/releases.
meta.description for mwic is: spell-checker that groups possible misspellings and shows them in their contexts
meta.homepage for mwic is: http://jwilk.net/software/mwic
Updates performed

Version update

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.7.10 with grep in /nix/store/f9pjdg0fcdicj7sva71irwcn2fclnngy-mwic-0.7.10
found 0.7.10 in filename of file in /nix/store/f9pjdg0fcdicj7sva71irwcn2fclnngy-mwic-0.7.10

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
mwic

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/f9pjdg0fcdicj7sva71irwcn2fclnngy-mwic-0.7.10 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A mwic https://github.com/r-ryantm/nixpkgs/archive/546a42df3cdc3bdf85bd5c8fd7b4faf89d996af3.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/f9pjdg0fcdicj7sva71irwcn2fclnngy-mwic-0.7.10
ls -la /nix/store/f9pjdg0fcdicj7sva71irwcn2fclnngy-mwic-0.7.10/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

mwic

Maintainer pings
cc @matthiasbeyer for testing.

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


HDFS-15918. Replace deprecated RAND_pseudo_bytes

RAND_pseudo_bytes is deprecated in OpenSSL
1.1.1 and must be replaced by RAND_bytes.

This PR fixes the following compilation warning -
[WARNING] /home/jenkins/jenkins-home/workspace/hadoop-multibranch_PR-2792/src/hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/libhdfspp/lib/common/sasl_digest_md5.cc:97:74: warning: 'int RAND_pseudo_bytes(unsigned char*, int)' is deprecated [-Wdeprecated-declarations]
[WARNING]                  from /home/jenkins/jenkins-home/workspace/hadoop-multibranch_PR-2792/src/hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/libhdfspp/lib/common/sasl_digest_md5.cc:20:
[WARNING] /usr/include/openssl/rand.h:44:1: note: declared here

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 37s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
32m 32s

trunk passed

+1 :green_heart:
compile
2m 39s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
2m 41s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
mvnsite
0m 30s

trunk passed

+1 :green_heart:
shadedclient
51m 46s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 16s

the patch passed

+1 :green_heart:
compile
2m 28s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

-1 :x:
cc
2m 28s
/results-compile-cc-hadoop-hdfs-project_hadoop-hdfs-native-client-jdkUbuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04.txt
hadoop-hdfs-project_hadoop-hdfs-native-client-jdkUbuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04 with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04 generated 7 new + 80 unchanged - 13 fixed = 87 total (was 93)

+1 :green_heart:
golang
2m 28s

the patch passed

+1 :green_heart:
javac
2m 28s

the patch passed

+1 :green_heart:
compile
2m 32s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

-1 :x:
cc
2m 32s
/results-compile-cc-hadoop-hdfs-project_hadoop-hdfs-native-client-jdkPrivateBuild-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08.txt
hadoop-hdfs-project_hadoop-hdfs-native-client-jdkPrivateBuild-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08 with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08 generated 3 new + 84 unchanged - 9 fixed = 87 total (was 93)

+1 :green_heart:
golang
2m 32s

the patch passed

+1 :green_heart:
javac
2m 32s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
0m 19s

the patch passed

+1 :green_heart:
shadedclient
13m 12s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
31m 53s

hadoop-hdfs-native-client in the patch passed.

+1 :green_heart:
asflicense
0m 33s

The patch does not generate ASF License warnings.

105m 54s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2811/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2811

Optional Tests
dupname asflicense compile cc mvnsite javac unit codespell golang

uname
Linux 3a133aed974d 4.15.0-136-generic #140-Ubuntu SMP Thu Jan 28 05:20:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 936b080994c403b3e5b5f4d37de133adafe30c3f

Default Java
Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2811/1/testReport/

Max. process+thread count
723 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs-native-client U: hadoop-hdfs-project/hadoop-hdfs-native-client

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2811/1/console

versions
git=2.25.1 maven=3.6.3

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

This PR doesn't modify any existing functionality and thus no extra unit tests are required. The warnings reported in the CI run aren't related to my PR.

This PR fixes the warnings reported as part of https://github.com/apache/hadoop/pull/2792 in CI run https://github.com/apache/hadoop/pull/2792#issuecomment-803456441
[WARNING] /home/jenkins/jenkins-home/workspace/hadoop-multibranch_PR-2792/src/hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/libhdfspp/lib/common/sasl_digest_md5.cc:97:74: warning: 'int RAND_pseudo_bytes(unsigned char*, int)' is deprecated [-Wdeprecated-declarations]
[WARNING]                  from /home/jenkins/jenkins-home/workspace/hadoop-multibranch_PR-2792/src/hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/libhdfspp/lib/common/sasl_digest_md5.cc:20:
[WARNING] /usr/include/openssl/rand.h:44:1: note: declared here


Spring integration

Pulled Spring DI under the application, so farewell for the manually wired managers. Had a bit trouble with the application initialization, but now JME's application and most of its managers are added manually to the spring context and are available through injection. This PR requires/contains the Gradle facelift!

Now the guns have a bit spread and are positioned according to their location in the gun's description.