Isolate.resolvePackageUri returns different values on dart run vs dart test or dart run path

Hello, I maintain dargon2 and tmthecoder/dargon2#8 was raised by @AaronFeickert where it was found out that running dart test or dart run path/to/main.dart worked fine while dart run with no path caused a failure in the plugin's FFI loading, which is done through the Isolate.resolvePackageUri method to determine the location of the dargon2 package in the execution environment.
This was the reported stacktrace:
Building package executable...
Built dargon2_test:dargon2_test.
Unhandled exception:
Invalid argument(s): Failed to load dynamic library '/home/test/dargon2-test/.dart_tool/pub/bin/dargon2_testlibargon2-linux.so': /home/test/dargon2-test/.dart_tool/pub/bin/dargon2_testlibargon2-linux.so: cannot open shared object file: No such file or directory
#0      _open (dart:ffi-patch/ffi_dynamic_library_patch.dart:12:43)
#1      new DynamicLibrary.open (dart:ffi-patch/ffi_dynamic_library_patch.dart:23:12)
#2      DartLibLoader.loadLib (package:dargon2/src/native/dart_lib_loader.dart:24:27)
#3      new LocalBinder._ (package:dargon2_core/src/native/local_binder.dart:155:31)
#4      LocalBinder.initialize (package:dargon2_core/src/native/local_binder.dart:130:38)
#5      new DArgon2Native (package:dargon2_core/src/native/dargon2_native.dart:19:17)
#6      argon2 (package:dargon2/src/argon2.dart:11:16)
#7      argon2 (package:dargon2/src/argon2.dart)
#8      main (file:///home/test/dargon2-test/bin/dargon2_test.dart:4:9)
#9      _delayEntrypointInvocation.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:297:19)
#10     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:192:12)

His test was on Linux with Dart 2.17.5 and I was able to reproduce the same error on Dart 2.17.5 on a Mac.
The issue I see here is that the dynamic library's path is showing to be in the dargon2_test which is the name of the created project by @AaronFeickert and not the path of the dargon2 package. However, when we run dart run path/to/main.dart or dart test the library resolution seems to work fine and we are able to perform the FFI calls without any changes to executable or package code, hence why I believe this is an issue within something in the language or run command.
Please let me know if I should provide any additional information. Thank you!

Looks like the Platform.script is /home/test/dargon2-test/.dart_tool/pub/bin/something and you choose the
    String rootPath;
    if (Platform.script.path.endsWith('.snapshot')) {
      rootPath = File.fromUri(Platform.script).parent.path;
    }

path of the resolution code.
So, dart run probably runs a snapshot script located there, maybe one which tries to locate the actual entry point, whereas dart test and dart run actualscript.dart will run what you point it to instead.

That fixed the issue on dargon2's end, but was this intended? I can't recall it happening previously


Multiple directories in / looking like wslRaNDoM

Windows Build Number
Microsoft Windows [Version 10.0.22000.51]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
5.10.16
Distro Version
Ubuntu & Ubuntu-20.04
Other Software
NA
Repro Steps
There are 410 directories in my / directory that all start with "wsl" and what appears to be a random string of 6 letters in mixed case. I can't seem to find any information about these and when I get properties on them they are 0 bytes in size.
They are owned by root, and when I use the root account to enter them they are empty. I have included how they appear in Windows and the results of ls -l for the directory.
Unsure how this occurred, my apologies

Expected Behavior
My guess based on the time these were created is that they are residual temporary folders used from a apt update run that for some reason weren't deleted. However given the number of them and the difficulty in searching for this issue given the keywords to describe the problem just bring up generic info on WSL and directories I thought I would ask more directly.
Actual Behavior
These exist instead of being deleted.
Diagnostic Logs
No response

Thanks for reporting this @cochetti.
These  temporary directories are created during the WSL boot processes, but we've had a bug where those weren't deleted.
This bug has been fixed recently though, if you start wsl after deleting all those directories, do you still see those ?

Not sure if a new bug should be open or that one should be re-opened but I observe the same issue on Windows 11 build 22631.3007 & Oracle Linux 9.1.

Yes, this still remains a problem for me as well.

I have the same issue as well. Below is distro info through neofetch, though I am running Windows 11:
OS: Ubuntu 22.04.3 LTS on Windows 10 x86_64
Kernel: <IP_ADDRESS>-microsoft-standard-WSL2

same issue here as well

same here

I just followed this for now.

Why was this issue closed? It is still occurring.

Why was this issue closed? It is still occurring.

Can you run ls -ogah and see what the creation dates are for those directories? I had the same issue on another device if mine, and they turned out to be some two years old.
In which case, closing this issue is valid, as it has seemingly been addressed in future updates.
If your directories were generated newly then this may be a thing to reopen!

I created the WSL instance about 3 months ago so it is at least that recent.

The issue is still present with some files created this year:
$ pe ls -ogdltr wsl* | tail -20
drwx------ 2 4096 Dec 20 02:45 wslPfNbGf
drwx------ 2 4096 Dec 20 02:45 wslLcFanE
drwx------ 2 4096 Dec 20 02:45 wslIBAEpP
drwx------ 2 4096 Dec 20 02:45 wslBpgclD
drwx------ 2 4096 Dec 21 00:35 wslmiiKhL
drwx------ 2 4096 Dec 21 00:35 wslMEljNg
drwx------ 2 4096 Dec 21 00:35 wslJoKBBa
drwx------ 2 4096 Dec 21 00:35 wslflGgip
drwx------ 2 4096 Dec 21 00:38 wslOmoAbA
drwx------ 2 4096 Dec 21 00:38 wsliaanod
drwx------ 2 4096 Dec 21 00:38 wslFeoKGA
drwx------ 2 4096 Dec 21 00:38 wsleMGIab
drwx------ 2 4096 Jan 22 13:48 wslpLNkoD
drwx------ 2 4096 Jan 22 13:48 wsloCgEhf
drwx------ 2 4096 Jan 22 13:48 wslFhigOg
drwx------ 2 4096 Jan 22 13:48 wslCOlGBM
drwx------ 2 4096 Jan 22 14:27 wslogfDHc
drwx------ 2 4096 Jan 22 14:27 wsliKaOol
drwx------ 2 4096 Jan 22 14:27 wsleblKGO
drwx------ 2 4096 Jan 22 14:27 wslajalii

Note that in my case, the issue happens on the second distribution installed, Oracle Linux but not on the initial one, Debian.
$ uname -a
Linux ol91a <IP_ADDRESS>-microsoft-standard-WSL2 #1 SMP Thu Jan 11 04:09:03 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
$ wsl --version
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>-2
WSLg version: 1.0.60
MSRDC version: 1.2.5105
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22631.3447

OS version is actually Windows 11 23H2 (build 22631.3447)

Yep, still happening.


Astrolauncher not working on winserver2012

astrolauncher has been placed in the root directory of the game server,
but it will stop when running,
The window will close after running.

What is the console output? Can you share your debug.log file?
https://discord.gg/astroneer because this is most likely not an Astro Launcher problem

No output No console, After double-clicking to run, the console automatically closes

Astroneer is operational and the game server is accessible.
Astro launcher can not run

No output No console, After double-clicking to run, the console automatically closes

Then run it using a separate CMD window...

Astroneer is operational and the game server is accessible. Astro launcher can not run

Wdym server runs? Astro Launcher needs to be the first thing to start, which then automatically starts the server. Not the other way around.

I try to run AstroLauncher using CMD.
Show Error Loading python DLL.
But I'm sure I have python related runtime libraries and programs installed

https://discord.gg/astroneer


Java tests won't start for Java project(plugin) when Haxe plugin is enabled

Java tests won't start for Java project(plugin) when Haxe plugin is enabled
IDEA 13.1.6
Project - Haxe plugin
If I enable Haxe plugin, then when I try to run tests on Java project(plugin) I got this error:
no main class

This is weird.  This is either the second or third case where we have issues with other language plugins when Haxe is installed.  I wonder if the Haxe plugin is installing/registering one of it's subclasses as a (mismarked?) subsystem for the Java language, and is thus overriding the standard Java behavior.  Or, more likely, that one of the Java classes that are sub-classed (re-used) by the Haxe plugin does this normally, and is now actually installing the sub-class when it thinks it is installing itself.
git bisect can probably help us here, but it's going to be tedious uninstalling and re-installing the plugin every time we want to test.
Have you noticed whether the issue occurs when we are debugging the Haxe plugin (e.g. debugging or running a secondary instance in the plugin playground), or only when the plugin is installed normally in a primary instance?

primary instance, not sure about secondary

This turned out to be a blocker at TiVo for Android team.
One of the Android developers came to my cube just now and complained that -
They are compelled to upgrade to IJ IDEA 14 for other reason - they use multi-dexing which needs this upgrade. So, they upgrade IDEA to 14 - now, they need to get latest Haxe plugin (0.9.2) for functional Haxe plugin. Once they install this latest plugin - it  is blocking all kinds of builds... gradle, Java / Android etc.
They need this fixed rather urgently - needs to be escalated because entire Android development team is  blocked.

Srikanth described the situation and so I will get to the business of how to produce this issue and add more details.
IntelliJ Version: 14.1.1 Build #IU-141.178
Haxe Plugin: 0.9.2
Please use below google drive link to get sample project, my idea logs and the list of plugins I have installed.
https://drive.google.com/folderview?id=0B5MqYzzaFCjUfmhqMXNPQTNOeXl6ak1Ga0IwSHN0eExyV1pDTWltVFJoSjlNdUJyMGQzeFk&usp=sharing
Steps to produce:

Import the sample project (which is sample Android gradle project)
Hit the little green play button to build

Error Logs from above steps:
Information:4/8/15, 1:34 PM - Compilation completed with 2 errors and 0 warnings in 19ms
Error:No main class for module: app
Error:Compilation failed
LMK if I can provide any more information.

Fix for this issue https://github.com/TiVo/intellij-haxe/pull/218

Same thing for secondary instance, used to happen all the time.

Boyan fixed this a couple of days ago.  It is in the 0.9.3 release.  fede5889b55f68e9ac54cfc1e9a651d045ee405e


Feat marxan 1005 endpoint permission projects

Adds Controller and Tests for Project access control
Feature relevant tickets
MARXAN-1005

Merging and taking smaller PR's for the comments in this one


Re-enable dmwatch

Due to popular demand, our community has encouraged us to re-release the plugin.
Since the deactivation of the plugin we have seen many people scamming again due to no ‘Runewatch’ equal for Deathmatching.
For the public good of the Deathmatching scene, we would like to see DMWatch back on the hub to be available to help keep scammers accountable like we originally set out to.

In the past, inclusion of pvp deathmatching "safety" plugins has lead to an
uptick in abusive behavior toward the RuneLite project, and caused degradation of some of our
services which negatively impacted other RuneLite users, even those who did not use those plugins.
Furthermore, we are increasingly uncomfortable with supporting, and effectively, mediating, the
unregulated gambling which is promoted by such plugins. For these reasons, we are not accepting
this or other related plugins.


Create GRANTA importer

First draft of the GRANTA importer (specifically using a template from MAPTIS/MMPDS) is complete. I used the record for "Inconel718,PrecipitationHardenedforCreep-ruptureap_cations,Bar,Thickness0.26to1.501in,AMS5962,ABasis" to test the importer and it worked, minus the TODO features of #27 #28 #29 #30. I'll come back to those later.


Require Sudo permission

Problem encountered on https://dotnet.microsoft.com/en-us/learn/aspnet/blazor-tutorial/install
Operating System: linux
Running on Ubuntu
After following the instruction  https://docs.microsoft.com/en-us/dotnet/core/install/linux-snap could not use dotnet but sudo dotnet worked

Other people seem to have this issue as well. There is also a known workaround this for now.
https://github.com/dotnet/core/issues/4446#issuecomment-605629427

cc @leecow

This issue has been resolved.


How can I get the code in the vender folder

How can I get the code in the vender folder. Because the example needs the autoload.php file. How can I get it.

By useing composer. but I can't new the Client Object .


mautrix-signal: Fix incorrect escaping in wrapper

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 121564 at 9fb7b6dc run on aarch64-linux 1

1 package built successfully:

mautrix-signal

1 suggestion:

warning: python-include-tests
Consider adding a checkPhase for tests, or if not feasible, pythonImportsCheck.
Near pkgs/servers/mautrix-signal/default.nix:50:0:
   |
50 |     description = "A Matrix-Signal puppeting bridge";
   | ^

Thanks
On Mon, 3 May 2021, 11:02 pm Sandro, @.***> wrote:

Merged #121564 https://github.com/NixOS/nixpkgs/pull/121564 into master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/121564#event-4678604915, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGRJXFXQ3PQLBDFWKU7FEDTL23HPANCNFSM44AGUJPQ
.


Using date to sort the order of posts

On the home and posts pages, the posts would show up in order of file number.
Adding a new post would mean that all should be renamed by incrementing their index.
Using sort to display posts in order of latest to oldest.

@all-contributors add @khushChopra for code

great catch ;) @khushChopra thanks!

My pleasure! I really like this template.
Btw I am using this template to run my blog/portfolio. I have quite a few tweaks to add to it.
Do let me know if at any point I should not make PRs to this repo.


Variety of CHANNELS_10_20

Why TopoPlots.CHANNELS_10_20 currently has only option for 19 electrodes? Why not to allow an option for 32, 64 and 128 electrodes?

There is no reason not to include them besides nobody having done it. Simon and I only had use for those 19 channels, which are the most common in clinical research, where higher density setups are rare. Pull requests are most welcome. 😊


Minor update for ENGLISH for README.md file

Minor update for ENGLISH for README.md file

Hi @rfdy,
it's OK for me, could you take a look ?

Done, see: https://github.com/rfdy/trader/commit/5d338160138782ab877efe2cca75e9199410dc80


Clicking notifications sends to blank page

When clicking on notifications they open as normal.
But clicking on individual notification it sends to blank page. (Screenshots are in discord issues room)
Vision 3.0.26
OS - Pop!OS 22.04 (Ubuntu 22.04)
Fully updated/upgraded on all packages
Screenshot 1
https://cdn.discordapp.com/attachments/385448634197737484/1021104381996839052/click-note.png
Screenshot 2
https://cdn.discordapp.com/attachments/385448634197737484/1021104382445625394/blan-ecency.png
Screenshot Neofetch with computer info

have the same issue on Windows 11 + firefox

Closing this issue as its now been fixed for me.

Closed for me


Add Error: This action is not supported by the default controller

Hello,
First of all, thanks for this wonderful app.
Please pardon my ignorance, I could not find a solution for this error anywhere, hence raising it as a issue.
I am using Raspberry Pi and cast to Google Home Mini.
I have 'cast' a youtube video URL and it is playing fine.
Then I am issuing an 'add' command and I get the below error message.
Error: This action is not supported by the default controller.
Please suggest.

The problem is that Google does not make the YouTube chromecast app available to your Home Mini (and other audio-only devices). And because of this, catt is defaulting to a generic chromecast app. Queing is currently not supported with this app, hence the error message you are getting.


Remove '-C' flag from 'account cli' subcommand

Removes the -C flag from the account cli subcommand, as it's no longer a viable option after a recent backplane update.

As far as I can tell, the new backplane rollout shouldn't have had any impact on osdctl's ability to get AWS access to clusters using older account roles. I'd like to hold off on this and dig in a bit more together if you have some time tomorrow, but I also won't hold up this pr if others feel the flag should be removed.

/lgtm
After further discussion, let's remove this.


Design for orthographic camera

Use Case
As a user viewing a trajectory in the viewer, I want to be able to switch the camera to orthographic view so that I can see spatial relationships without distortion from perspective.
Acceptance Criteria
UI controls on the viewer allow a user to toggle back and forth between ortho and perspective camera modes.
Details
This can be really useful for seeing how objects receding into the distance line up in the plane of the screen.
orthographic projection wiki

This dev work might fit nicely with https://github.com/simularium/simularium-website/issues/320


request permission for plugin-nomad

Description
https://github.com/jenkinsci/nomad-plugin
https://issues.jenkins-ci.org/browse/HOSTING-740
Submitter checklist for changing permissions
Always

[x] Add link to plugin/component Git repository in description above

When adding new uploaders (this includes newly created permissions files)

[x] Make sure to @mention an existing maintainer to confirm the permissions request, if applicable CC @iverberk
[x] Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
[x] All newly added users have logged in to Artifactory at least once

@oleg-nenashev https://github.com/jenkinsci/nomad-plugin/pull/33#issuecomment-479861480

@jippi is not listed in the permission file, I am not sure he is considered as a maintainer.
This is a disadvantage of Giving Admin access to teams in GitHub, we lose a public trace of ownership changes. CC @daniel-beck @batmat

LGTM

Done, thanks!
On Mon, Apr 8, 2019, 13:53 Ant Weiss<EMAIL_ADDRESS>wrote:

LGTM
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jenkins-infra/repository-permissions-updater/pull/1093#issuecomment-480783233,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC3IoEfH21qMNi8EhsUKLoqVGwQb8WcTks5vex-QgaJpZM4cho2X
.

Yes, I agree plugin maintainers should ideally not have access to teams. So people go through the IRC bot for instance for traceability and the likes. I think I saw a similar case recently on JenkinsPipelineUnit...


[Suggestion] Space Bar to climb

I don't know if it would be possible. but I'm wondering if you could have it so when we are hanging on a ledge that we can press "space bar" to climb up instead of pressing W? or perhaps have a toggle we can swap between space bar and W?
i don't know if having it as space bar would interfere with anything. so I'm just wondering

completely forgot about this issue. Added this some time ago, so just update your beatrun and you can climb up with W or Space


Confused how to set enemy/etc spawns

For example, I try to modify Vow and set all the enemies to Rarity=0, MaxEnemyCount=0, except the one spawn that I want to appear--which I gave a high rarity value (does that make it more or less common relative to others)... Still all kinds of monsters appear but the one I intended, any tips?

Are you modifying the LethalQuantities/Moons/Vow/Enemies.cfg, and did you set the config to enabled in the General section? And, do you have any other mods installed?

Hilariously I forgot to reinstall it after troubleshooting, I was only modifying the remaining config files apparently.
For now I think it's probably working. Might check later with further mods and if I run into issues I'll probably post here.
Thanks for this useful tool though! Cheers!

Ok great! Definitely re-open this if you run into any more issues, thanks!


Add detailed documentation in README.md

Include the following

Project description
Heroku app link
Updated instructions for running locally
Screenshots of the polished game

Fixed in https://github.com/joeyshi12/platform-party/pull/10. Screenshots can wait until game is more polished


Merge pull request #78392 from Mic92/kresd-doh

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

.listenDoH is now being switched to new implementation: https://github.com/NixOS/nixpkgs/pull/103633


perf-regression:

Describe the feature here
Check if update to ${quarkus.platform.group-id} would be better.
As evoked in this pr.

Actually, the perf-regression pom and sample poms do not depends on build-parent-it, so it does not make sense to align.
Closing.


integration tests: Remove preserve_old_config fixture

The preserve_old_config fixture fails when Nmstate reports a
configuration that it cannot set, for example a gateway together with
DHCPv6 and autoconf. If someone needs to restore a certain network state
after running the tests, they need to use a custom wrapper/script to do
so.
References:
<EMAIL_ADDRESS>https://nmstate.atlassian.net/browse/NMSTATE-275
Signed-off-by: Till Maas<EMAIL_ADDRESS>

This change is

Coverage increased (+3.07%) to 81.173% when pulling 3e32099cc1f06acbc7c091cb75541c1324ddc80f on tyll:cleanup_fixture into f70fe88bc00d386be117b73dcd7b5f879112a0f3 on nmstate:master.

Added a new check to warn in case the Nmstate state differs after the test run.


Updated SQLPS installation an remarks

some processes in docs still use SQLPS and I've recently installed SQL 2017 on Server 2019. SQLPS was not part of it. I update this doc to complete the documentation.
Credits: https://sqlpadawan.com/2018/08/01/how-to-install-sql-server-sqlps-powershell-module/

@Karl-WE : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Related PR: https://github.com/MicrosoftDocs/sql-docs/pull/4827

@Karl-WE
Investigating.  Apologizes for the delay.
Once I hear back, I will update this PR.

@Karl-WE
SQLPS is part of the core SQL Setup – so, even if you just install the Engine, you get it. I do not know if you installed some random stuff (down in the feature tree, like SDK or Back Compat stuff… or pretty obscure things), but I know that Engine carries SQLPS.
I would NOT recommend installing the ancient PowerShellTools.MSI (it shipped until SQL2014 or maybe SQL2016, as part of the so-called Feature Pack). The process outlined in the referenced article (=install 3 MSIs) is correct.
Please don’t install the SQLPS module. Install the SQLServer module instead.
I have to reject this PR.

@Karl-WE
SQLPS is part of the core SQL Setup – so, even if you just install the Engine, you get it. I do not know if you installed some random stuff (down in the feature tree, like SDK or Back Compat stuff… or pretty obscure things), but I know that Engine carries SQLPS.
I would NOT recommend installing the ancient PowerShellTools.MSI (it shipped until SQL2014 or maybe SQL2016, as part of the so-called Feature Pack). The process outlined in the referenced article (=install 3 MSIs) is correct.
Please don’t install the SQLPS module. Install the SQLServer module instead.
I have to reject this PR.

Hello @markingmyname thanks for the review. I can assure you it was reproducible that SQLPS was missing, reproducibly on the following scenario:
Server 2019 core
SQL Server 2017 (RTM) from customer VLSC
It took me a lot of time to investigate this problem see related #4827 and hoped the efforts would be dealing out. I specificially we can correct my PR if it is correct to say it is not included but I did describe well what to do if it IS missing.
I was not feeling well about installing this old packages but please triage the issue and let us then decide how to help people that run into the same spike of "missing" documentation.
Can we agree?

@ktoliver since @markingmyname is not responding after the close is anyone free to review my concern / issue, even more as I wouldn't have spent so much time for this PR plus related #4827 if SQLPS wasn't missing by default.
Thank you for your time.

Hi, @Karl-WE
I reopened this PR to continue our conversation.
I apologize for the delayed response.
I recently made some updates to both the [SQL Server PowerShell] article(https://docs.microsoft.com/en-us/sql/powershell/sql-server-powershell?view=sql-server-ver15) and the Install the SQL Server PowerShell module article describing the purpose between SQLPS and SQLServer modules.
However, if I understand you right, are you stating that SQLPS is installed with SQL engine?

Hi @markingmyname your articles are fine. But both advice users how to install sqlserver module. All docs are clear SQLPS is deprecated, also you outlined my documented workaround, found on the web might not be a good solution.
My point is that we reproed that SQLPS was missing with the above scenario.
L Thus I spent the time to document this workaround if other users facing the same issue. Sqlserver module is not sufficient for the task described in #4827. In fact it needs SQLPS.

@Karl-WE,
I believe I understand more clearly that you are trying to just bring to light a special situation where you have offered the workaround.
If that is the case, I can think of adding a Considerations and Limitations section that could offer this information.
However, this PR is not out of sync with the master branch.  Would it be too much trouble to ask for you to update this Pr with the latest version of the article and add an H2 titled -  Limitations and Considerations - and then offer your workaround there?
After that, I will discuss with the parties involved if that is accepted.
Thank you.

Aye @markingmyname
since I would like to create a new PR based on "all servers" if needed who will update the changes to the subsequent versions?

If I don't have to care about this, I will create a new PR on this article, okay?
https://docs.microsoft.com/SQL/powershell/download-sql-server-ps-module

@Karl-WE
The metadata will take care of versioning.
Just choose the latest version of the PS file and update that.
Please let me know when you have completed this.
Thank you.

Closing PR as since this is out of sync with the current version, @Karl-WE will create a new PR to be reviewed.

"Closing PR as since this is out of sync with the current version, @Karl-WE will create a new PR to be reviewed."
Done. Unfortunately we should update several articles, or at least cross reference them.


Inappropriate value for attribute "days": a number is required

Description
Weirdly I have an error saying the type of attribute "days" should be a number. But it is a number in my code... or maybe I'm missing something...
Versions

Module version: v3.14.0

Terraform version: v1.5.7

Provider version(s): v5.17.0

Reproduction Code [Required]

Steps to reproduce the behavior:
main.tf
module "s3_bucket_alb_logs" {
  for_each = var.s3_log_bucket_settings_and_rules
  source   = "terraform-aws-modules/s3-bucket/aws"
  version  = "v3.14.0"

  bucket = format("%s-%s-access-logs", var.Project, each.key)
  acl    = "log-delivery-write"
  lifecycle_rule = [
    {
      enabled = each.value.lifecycle_rules.enable_lifecycle_configuration
      id      = format("%s-public-alb-access-logs-lifecycle-rule", var.Project)

      abort_incomplete_multipart_upload_days = 1
      filter_and                             = null
      expiration = {
        days = each.value.lifecycle_rules.expiration_days
      }
      transition = [
        {
          days          = each.value.lifecycle_rules.first_transition_days
          storage_class = each.value.lifecycle_rules.second_transition_days
        },
        {
          days          = each.value.lifecycle_rules.first_transition_class_type
          storage_class = each.value.lifecycle_rules.second_transition_class_type
        }
      ]
    }
  ]

  # Allow deletion of non-empty bucket
  force_destroy = each.value.force_destroy

  control_object_ownership = each.value.control_object_ownership
  object_ownership         = each.value.object_ownership

  attach_elb_log_delivery_policy = true # Required for ALB logs
  attach_lb_log_delivery_policy  = true # Required for ALB/NLB logs

  access_log_delivery_policy_source_accounts = each.value.access_log_delivery_policy_source_accounts
}

variables.tf
variable "s3_log_bucket_settings_and_rules" {
  description = "All settings and rules for S3 Log Bucket creation"
  type = map(object({
    lifecycle_rules = object({
      enable_lifecycle_configuration = bool
      expiration_days                = number
      first_transition_days          = number
      first_transition_class_type    = string
      second_transition_days         = number
      second_transition_class_type   = string
    })
    force_destroy                              = bool
    control_object_ownership                   = bool
    object_ownership                           = string
    access_log_delivery_policy_source_accounts = list(string)
  }))
}

terraform.tfvars
s3_log_bucket_settings_and_rules = {
   private-alb = {
    lifecycle_rules = {
      enable_lifecycle_configuration = true
      expiration_days                = 365
      first_transition_days          = 30
      second_transition_days         = 90
      first_transition_class_type    = "STANDARD_IA"
      second_transition_class_type   = "GLACIER"
    }
    force_destroy            = true
    control_object_ownership = true
    ....

As you can see my variable is correctly setup with "expiration_days" as a number and I put a number inside my .tfvars. Am I missing something ?
Expected behavior
tf plan goes smoothly and plan a lifecycle policy where my expiration days is correctly setup to 365

Actual behavior
tf plan erorr says "Inappropriate value for attribute "days": a number is required"

Terminal Output Screenshot(s)

Additional context

@bientavu you put wrong values on days and storage_class. Please change your code from this
        {
          days          = each.value.lifecycle_rules.first_transition_days
          storage_class = each.value.lifecycle_rules.second_transition_days
        },
        {
          days          = each.value.lifecycle_rules.first_transition_class_type
          storage_class = each.value.lifecycle_rules.second_transition_class_type
        }

to this
        {
          days          = each.value.lifecycle_rules.first_transition_days
          storage_class = each.value.lifecycle_rules.first_transition_class_type
        },
        {
          days          = each.value.lifecycle_rules.second_transition_days
          storage_class = each.value.lifecycle_rules.second_transition_class_type
        }

@abaidgulshan, oh my bad I should have seen that... thanks a lot!


Fixed typo in comment in iteration.lisp

There was a small typo in both iteration.lisp files.

Sorry, forgot the CLA.

Did you sign the cla? There's some internal changes to permissions and I'm not sure this repo was updated successfully.

Sorry for the late response,
Yes, I signed the CLA, unfortunately I forgot to sign it before the merge request.


Ephemeral Sessions

See: https://github.com/thombruce/helvellyn/issues/79
And: https://github.com/thombruce/credible/pull/33
Session behaviour is changing server-side. Nothing needs to be done client-side to adopt this change.
However, the client application should make its self aware of expiry and utilise the refresh token before an access token becomes invalid.
Question
I know that a hard refresh will acquire the new refreshToken if it has been updated in another tab. Does this get updated without a refresh though?
I can confirm that the refresh-token in Local Storage does indeed change when a session is loaded in another tab. Good.

I appear to have broken manual signOut at some point - this warrants a separate investigation.


Command line args

When launching with command lines arguments length is 0 do I need to add a link in pom to get them to work?

I think this is something that should really be covered in the samples, i.e. when launching helloFX with an optional name passed as a command line parameter. In the current form, the samples pass args on to Application.launch(), which suggests that everything should work as expected, but args is really always just an empty array, no matter what you give on the command line.
Sorry, I can only support you in stressing how important this is, but I have not found the answer myself.

I stumbled over the empty args array as well. Is there any workaround on getting hold of the actually passed arguments?

Fixed with #566


Change precedence of assumption classes

Related to cbeust/testng#2352.
Check List:

Fixes #1961
Unit tests : NA
Javadoc with a code example (on API only) : NA

@joel-costigliola PR ready


Add observability, reporting, query workbench and gantt chart to manifests

Description
Add observability, reporting and gantt chart to manifests
Issues Resolved
List any issues this PR will resolve, e.g. Closes [...].
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #3048 (e1d1dd2) into main (9ab0203) will decrease coverage by 0.30%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #3048      +/-   ##
==========================================
- Coverage   93.17%   92.87%   -0.31%
==========================================
  Files         167      167
  Lines        4602     4602
==========================================
- Hits         4288     4274      -14
- Misses        314      328      +14

Impacted Files
Coverage Δ

src/system/temporary_directory.py
64.44% <0.00%> (-28.89%)
:arrow_down:

src/system/os.py
94.73% <0.00%> (-5.27%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

CI is failing as OpenSearch has bumped to 2.6.0 for 2.x branch. Will need to rebase after this PR merged. https://github.com/opensearch-project/opensearch-build/pull/3059

@peterzhuamazon @zelinh can we review and merge this soon ?

@peterzhuamazon @zelinh can we review and merge this soon ?

@anirudha Yes, once the CI checks completed, I could help merge this.


Fix redirect to admin when user log out

Fix redirect to admin when  user log out and redirect when the user does not have the required site

tested redirect for unathorized user, and the redirect when trying to access another user's site dashboard


add max_pool2d

add support for max_pool2d and provide a simple test for it.

Looks good, thanks for the PR. I'll merge once the CI has run. For the future, note that it would be great to provide cuda kernels too as we would rather not accumulate too many ops for which we only have a cpu implementation.


Rollout planning for transforms v2

This issue is for discussing how and when we are going to roll out transforms v2 from torchvision.prototype.transforms to torchvision.transforms. The new API depends on the torchvision.prototype.datapoints namespace. Since no equivalent exist in the stable torchvision yet, we can simply move it.
Functional API
The functional API of v2 is fully BC with v1, and so we can just drop it in.
In addition, since v2 now has public kernels for tensor and PIL images, we should also deprecate the torchvision/transforms/functional_{pil,tensor}.py modules. Although not prefixed by an underscore, they were always considered private. Note that the public kernels of v2 are mostly but not always a drop-in replacement for the private kernels of v1. In v1 sometimes some common preprocessing was done on the dispatcher, e.g.
https://github.com/pytorch/vision/blob/8985b598a69250d65959941c863d76a4225ae7ac/torchvision/transforms/functional.py#L690-L696
https://github.com/pytorch/vision/blob/8985b598a69250d65959941c863d76a4225ae7ac/torchvision/transforms/functional.py#L725
https://github.com/pytorch/vision/blob/8985b598a69250d65959941c863d76a4225ae7ac/torchvision/transforms/functional_tensor.py#L695-L700
Since in v2 the kernels have to be able to stand alone, this preprocessing had to be moved into the kernels and thus changing the signature:
https://github.com/pytorch/vision/blob/8985b598a69250d65959941c863d76a4225ae7ac/torchvision/prototype/transforms/functional/_geometry.py#L1457-L1464
https://github.com/pytorch/vision/blob/8985b598a69250d65959941c863d76a4225ae7ac/torchvision/prototype/transforms/functional/_geometry.py#L1272-L1279
But, to reiterate, since the kernels were considered private in v1, this doesn't constitute a BC break.
Class API
The class API of v2 breaks BC in two ways compared to v1:

The transforms are no longer JIT scriptable. JIT requires pretty static behavior, but core design choices of the transforms go against that. For example, the independence of the input structure as well as the dynamic dispatch are not supported by JIT. Meaning, JIT is simply not compatible with what we want to achieve.
[EDIT] we have decided to provide BC for these methods (at least with a proper deprecation cycle https://github.com/pytorch/vision/pull/7092#issuecomment-1384325813)
Some random transformations have a public and static method get_params that allows users to perform the random sampling without instantiating the transform. This is a common idiom for v1, since it doesn't support transforming multiple inputs jointly. Meaning, to transform an image and a bounding box at the same time, one would sample the parameters once by calling get_params and subsequently call the respective functionals themselves. The latter can range from a single call to more complex ones that basically replicate the original transform. Transforms v2 supports jointly transforming multiple datapoints natively and thus there is no longer a need for this to be public.
Since the random sampling of course still needs to happen, it is possible to temporarily keep the public method, but start to deprecate it as soon as transforms v2 is considered stable. We have identified another low-priority use case for a public get_params, but there is already a design proposal for v2 that would improve the UX over v1 quite a bit and doesn't rely on public parameter sampling.

The BC breakages are not random, but transforms v2 brings a lot of new functionality. Although we have extensive tests and made sure our own training pipelines run smoothly with it, the API cannot be considered stable from the get go, since it wasn't battle tested yet. This means that we will start out in a beta state. We are confident that we can bring it to a stable state in one or two release cycles. During this time we are not yet bound to BC, but we don't expect any large scale changes.
Even after transforms v2 is considered stable, we can't replace v1 directly due to the BC breakages. Thus, the roll-out plan suggested here is to create two new namespaces: torchvision.transforms.v1 and torchvision.transforms.v2. With that, both versions of the API can coexist until we are confident that v2 can replace v1. Initially torchvision/transforms/__init__.py will do from .v1 import * and thus users don't have to change anything. As soon as we consider v2 stable, we deprecate the two features of v1 for which we won't keep BC, but only under the main namespace, i.e. torchvision.transforms. Users that imported directly from torchvision.transforms.v1 should not see a warning. Finally, after the deprecation period is over, we switch the import in torchvision/transforms/__init__.py to from .v2 import * and complete the transition.
Afterwards, we still need to decide what we do with the v1 and v2 namespaces:

v1: We could keep this indefinitely so users for which the parts where we break BC are critical, can continue to use the v1 transforms and only need to change an import once. Given that only the JIT scriptability is broken without replacement, we could also start to deprecate the namespace as soon as JIT is deprecated in PyTorch core. It makes little sense to keep the old API around if their only significant difference is something that is no longer maintained or maybe even replaced by something else. In any case, everything in this namespace would no longer be maintained by us.
v2: Although this obsolete after the transition is complete, we might still keep it around to minimize disruption. Users that started using the v2 API before the transition was complete, could continue to import torchvision.transforms.v2 and are not forced to change the namespace a second time.

Timeline summary

0.15:

Move torchvision.prototype.datapoints to a new namespace torchvision.datapoints
Drop torchvision.prototype.transforms.functional into torchvision.transforms.functional
Deprecate torchvision.transforms.functional_pil and torchvision.transforms.functional_tensor [^1]
Move torchvision.transforms.transforms to a new namespace torchvision.transforms.v1 and deprecate the old one [^1]
Move torchvision.prototype.transforms to a new namespace torchvision.transforms.v2
Expose everything from torchvision.transforms.v1 through torchvision.transforms

0.15 + x [^2]

Deprecate JIT scriptability and usage of static get_params methods where applicable on transforms exposed through torchvision.transforms. Let the warning point torchvision.transforms.v1 in case the deprecated functionality is critical for the users.

0.15 + x + 2 [^2]

Expose everything from torchvision.transforms.v2 through torchvision.transforms
Keep torchvision.transforms.v1 indefinitely or until JIT is deprecated from PyTorch core, albeit unmaintained in any case

Going by our regular release cycles, this means transforms v2 should be accessible from a stable release in H1 2023, will likely be considered stable in H2 2023 and fully replace transforms v1 in H1 2024.
[^1]: Although initiated by the v2 roll out, the deprecation is independent of it and should happen according to the deprecation policy.
[^2]: x denotes the time we need to bring the transforms v2 from a beta to a stable state. Current estimate is one or two release cycles.
cc @vfdev-5 @datumbox @bjuncek

Thanks a lot Philip for the proposal. I'm largely on board with it. Below are a few thoughts / items we could discuss more:

whether we need the v1 namespace right from 0.15. Perhaps we would only need it later in 0.17 once we migrate .v2 in .transforms, or even ideally not at all if the jit compatibility isn't critical after all.
whether we'll want to programmatically protect the access of the .v2 namespace while it's still Beta (and thus may entail API changes). Something like what I proposed in https://github.com/pytorch/vision/pull/6173 . I think it will depend on how much we expect the API to change before we move it out of v2.
Depending on how our BC requirements evolve (JIT support is still unclear at this point, etc.) there's a hardcore / risky option of migrating everything straight into torchvision.transforms right from the start. I'm not advocating for it, but it's still something to think about (even if it's just to come to the conclusion that this is clearly too risky!)

I noticed that the v2 perspective function has an extra coefficients argument compared to its v1 sister in torchvision.transforms.functional: can you confirm that the default behaviour is still the same between v1 and v2 (and that this is the case for all functionals in torchvision.transforms.functional)?
Also, I've always been uncomfortable with that view:

the torchvision/transforms/functional_{pil,tensor}.py modules [...] although not prefixed by an underscore, they were always considered private.

and I don't think we should assume users understand that we don't want them to use these files. I don't think we should break anything there. I don't think we need to anyway, because since we have to implement the migration mitigation for the class API, it shouldn't be too much more work to do that for the .functional namespace either.

I noticed that the v2 perspective function has an extra coefficients argument compared to its v1 sister in torchvision.transforms.functional: can you confirm that the default behaviour is still the same between v1 and v2 (and that this is the case for all functionals in torchvision.transforms.functional)?

In v2 we have 2 kinds of API to keep BC: https://github.com/pytorch/vision/pull/6902


doc: fix grammar: "your" -> "you're"

Replace "your" by "you're" where it's meant to be a contraction of "you are" rather than a possessive pronoun.

I did recognize somone's handwriting in the previous version. :wink:
Thanks @das-g ! Can't wait to see your next contribution!
If it's going to be something more involved, check out the develop branch for ongoing development.
Big :+1:


Enable kdump in VMs and collect dumps from kernel panics

ref https://neondb.slack.com/archives/C03TN5G758R/p1690216475962149?thread_ts=1690175203.472599&cid=C03TN5G758R
This should significantly help with debugging in the event of kernel panics in the VMs — which is made much more likely by memory hotplugging.
Tangentially related to #176.

kernel panicked
dump saved somewhere in guest fs (let say /kdumps)
vm exited (poweroff'ed)
qemu exited
runner pod terminated
all pod context removed

question - how and where store these dumps for further inspection.

dump saved somewhere in guest fs (let say /kdumps)

Can we mount a separate fs into the guest at /kdumps, and then have neonvm/runner copy that filesystem into some directory on the host k8s node? e.g. at /neonvm-kdumps/$PODNAME/... We'd want to enforce a reasonable size limit, etc. in case the VM is compromised or crash looping, but perhaps an option?

Mounting host folders to VMs means using virtio-fs, which means no live migration (the host in our case is the runner pod file system). As a possible solution - try disconnecting (hot unplug) the virtio-fs device from the VM before the trigger migration, but this approach needs to be tested (whether it's possible or not).

Mounting host folders to VMs means using virtio-fs, which means no live migration (the host in our case is the runner pod file system)

Ah, right. Is it possible for us e.g. mount an extra qcow2 filesystem, and then read that from the "host" (i.e. runner pod) afterwards to copy somewhere else? (asking because I'm not sure how opaque qcow is)
Might also fit well with some of the ideas I just wrote up in #449, which could have the runner notified when the VM panics, so it could immediately copy over (rather than e.g. periodically checking the filesystem, or using inotify to listen for modifications to the qcow file :sweat_smile:)

Also related to #450.


Feature/oauth

Description
This pull request let UDM support using OAuth2 to access NF and verify NF request with token.
Usage
Add the following config to enable OAuth2.0 feature.
  sbi: # Service-based interface information
    oauth: true

Refactor the serviceList config.
configuration:
  serviceList:
    - serviceName: nudm-sdm  # Nudm_SubscriberDataManagement service
      allowedNfTypes:
        - All
    - serviceName: nudm-uecm # Nudm_UEContextManagement service
      allowedNfTypes:
        - All
    - serviceName: nudm-ueau # Nudm_UEAuthenticationManagement service
      allowedNfTypes:
        - All
    - serviceName: nudm-ee   # Nudm_EventExposureManagement service
      allowedNfTypes:
        - All
    - serviceName: nudm-pp   # Nudm_ParameterProvisionDataManagement service
      allowedNfTypes:
        - All

Note
The pull request depends on:

NRF's PR#25. https://github.com/free5gc/nrf/pull/25
openapi's PR#17 https://github.com/free5gc/openapi/pull/17

Is it duplicated with https://github.com/free5gc/udm/pull/29?

Is it duplicated with #29?

No, this PR is depend on #29 and support service authorization via OAuth2 token.
The PR description had been update.


Thanks for your packaging, there are few suggestions by packaging to implement later :)

Prior following text wall - thanks for packaging for MS Store :) Almost zero fixups required after installation, but I have bad feeling on usage upstream distro name for publication due to trademark policy and CoC... Anyway, not my business, but Antergos used own branding, and used mainline repos with few own decorative packages (and graphical installer) optional repo, built from AUR.
For those, who look for ready recipes without 3hrs waste of MSDN weird documentation reading (can be safely ignored otherwise, as this setup way is somewhat dumb and beer-inspired...):
Prepare Windows host for WSL2

PS > DISM.exe /Online /Enable-Feature /FeatureName:VirtualMachinePlatform /All
PS > wsl.exe --shutdown
PS > wsl.exe --update
PS > wsl.exe --set-version Arch 2

Setting up Arch

# cat /etc/wsl.conf

[automount]
enabled = true
# For sharing storage with other WSL instances.
crossDistro = true
root = /mnt/
# dirs = 755, files = 644, disable char case check.
options = "metadata,uid=1000,gid=1000,umask=0000,fmask=0033,dmask=0022,case=off"
# UID/GID 1000 is default, can be omitted.
# options = "metadata,umask=0000,fmask=0033,dmask=0022,case=off"
# mountFsTab = true

[network]
hostname = archlinux.wsl
generateHosts = true
## LATE EDIT - there are few more undocumented (on MSDN at least) options for this section, like bridged mode setup:
## https://github.com/microsoft/WSL/issues/4150#issuecomment-1310028257
## By default Hyper-V network stack doesn't support IPv6 for WSL2 instances, if you have IPv6-primary ISP connection - worth to try.
generateResolvConf = true

# Set both keys to false to disable ability to call windows binaries from WSL envinroment
[interop]
enabled = true
appendWindowsPath = true

[user]
default = defaultuser

[boot]
systemd = true

PS > cat %USERPROFILE%/.wslconfig (on windows host)

[wsl2]
memory = 6GB
processors = 8
kernelCommandLine = mmio_stale_data=off
swap = 4GB
pageReporting = true
# Well, guess this key should break things if more than one WSL running... Enable direct access to WSL resources, listening on localhost/<IP_ADDRESS> from host side using localhost as address.
localhostForwarding = true
nestedVirtualization = true
debugConsole = false
# flatpak applications looks like started without any issues (Wayland).
guiApplications = true
vmIdleTimeout = 60000
idleThreshold = 10000

Some fixup of default systemd unit configurations, due to somewhat messed implementation from WSL init side

# cat /etc/systemd/system/fixshm.service

[Unit]
Description=Fix the /dev/shm symlink to be a mount
DefaultDependencies=no
Before=sysinit.target
ConditionPathExists=/dev/shm
ConditionPathIsSymbolicLink=/dev/shm
ConditionPathIsMountPoint=/run/shm

[Service]
Type=oneshot
ExecStart=/usr/bin/rm /dev/shm
ExecStart=/usr/bin/mkdir /dev/shm
ExecStart=/bin/umount /run/shm
ExecStart=/usr/bin/rmdir /run/shm
ExecStart=/bin/mount -t tmpfs -o mode=1777,nosuid,nodev,strictatime tmpfs /dev/shm
ExecStart=/usr/bin/ln -s /dev/shm /run/shm

[Install]
WantedBy=sysinit.target

Another fix...

# cat /etc/systemd/system/systemd-sysctl.service.d/override.conf
# cat /etc/systemd/system/systemd-sysusers.service.d/override.conf

Or use # systemctl edit systemd-sysusers.service; systemctl edit systemd-sysctl.service

[Service]
LoadCredential=

After this modifications -

PS > wsl.exe --shutdown

Next boot should be systemd-backed.

# systemctl list-units --type=service - to check if systemd is working. At least podman works fine :)

Solution source links to be added later via UPD.
Known sound journald entries

WSL (2) ERROR: InitCreateSessionLeader:1088: /sbin/init failed to start within 10000ms - can be safely ignored, no impact observed in 2 hours.
9pnet_virtio: no channels available for device drvfs - guess can be ignored too, everything seems working.

Suggestions:
I don't see any reason to additionaly modify/update upstream docker image during package preparation, to be honest, as it rebuilds daily on GitLab, and weekly - pushed on DockerHub. Maybe it is more suitable to use full pipeline to prepare image from scratch, and replace sudo (someone using other privilege escalation options, worth to mention - su is provided from base group) configuration with systemd-firstboot :) Well, it needs to be configured - but Arch, for painless usage, anyway requires recently added WSL2 features, as I remember - there are no packages in "main" repositories with other init options, but systemd... Yes, they are all in AUR, and WSL anyway will configure system each run.
So, I guess, less "vanilla" image packaging suitable in this case - polishing required anyway just to run Arch not in single-user mode under WSL.

Hey, thanks for your suggestions, regarding the trademark i think I read somewhere in the arch wiki that if you are making minimal/no changes to the base you can use arch name but i am not exactly sure but i will look into it again. I included sudo so it would be a coherent experience with other wsl distributions and help people not get stuck from the get go if they are following some tutorial for wsl. The same goes for systemd boot wsl is not designed to use systemd boot by default but they can do it if they want to, i have seen in newer versions of wsl it is relatively easy to use systemd anyway so probably should let the user decide what they want.


fix: add JACQUES-650-MIB

:tada: This PR is included in version 1.15.5-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Timeout after hundreds of translations

Googletrans version:

[x] 3.x
[ ] 2.x

I'm submitting a ...

[x] bug report
[ ] feature request

Current behavior:

I am using Googletrans in China. I set the translator as Translator(service_urls=['translate.google.cn']) and It works. But when I try to translate thousands of individual sentences, exception httpcore._exceptions.ConnectTimeout: timed out always happen. If I translate one sentence each time, exception will happen after about 300 translations; if I try a batch of sentences (Advances Usage), exception happens and translation will never finish. I have tried to sleep for every 50 or 200 translations but it never worked. I want to know if there is a solution for this problem, otherwise I have to translate 300 sentences each time and It is time consuming.
Expected behavior:

Steps to reproduce:

Related code:

translator = Translator(service_urls=['translate.google.cn'])
for index, row in data.iterrows():
    query, id = str(row['searched.query']).strip(), row['searched.clicked_content_id']
    if query != np.nan or id != np.nan:
        count += 1
        translation = translator.translate(query)
        print(str(count) + '   ', translation.origin, ' -> ', translation.text)
        query = translation.text
        result.append({'query': query, 'id': id})

Other information:

If I'm right, there should be a limitation for times of translation. 300 is a reasonable number. When trying to translate tons of things, I usually will run the script in the Google Colab and record the number when it stops. After it stops, you can restart the kernel and start to translate the spot right after the number you recorded.
Otherwise, I may need to @ssut .

If I'm right, there should be a limitation for times of translation. 300 is a reasonable number. When trying to translate tons of things, I usually will run the script in the Google Colab and record the number when it stops. After it stops, you can restart the kernel and start to translate the spot right after the number you recorded.
Otherwise, I may need to @ssut .

Well, I have tried like this and it successed. I just wonder if there is a more elegant way or can we develop a new feature?

We may find a better way to solve this but the limitation itself is implemented in the original Google Translation setting.

I have checked that the current implementation of the library does not support HTTP/2 so this may affect. I currently am working on fixing this issue with async/await support, and think this work may help handling this issue.

I have checked that the current implementation of the library does not support HTTP/2 so this may affect. I currently am working on fixing this issue with async/await support, and think this work may help handling this issue.

That's great, thank you!

If I'm right, there should be a limitation for times of translation. 300 is a reasonable number. When trying to translate tons of things, I usually will run the script in the Google Colab and record the number when it stops. After it stops, you can restart the kernel and start to translate the spot right after the number you recorded.
Otherwise, I may need to @ssut .
can you tell me how to restart the kernel? thx


javac not found, found Java 8 expected 11

Hi, I am using the tag 11.0.3_1.2.8_2.12.9 to switch to open JDK 11 from 8
But after installing it, I got confronted by
java.io.IOException: Cannot run program "javac" (in directory "/www/war/backend"): error=2, No such file or directory

I can't find this one. But what is more surprising is this:
war@712acceb888e:/www/war$ java -version
openjdk version "1.8.0_222"
OpenJDK Runtime Environment (build 1.8.0_222-8u222-b10-1~deb9u1-b10)
OpenJDK 64-Bit Server VM (build 25.222-b10, mixed mode)

I needed to change the path to get it
export PATH=/usr/local/openjdk-11/bin:$PATH

Are you sure you got the right image?
➜  ~ docker run --rm -t hseeberger/scala-sbt:11.0.3_1.2.8_2.12.9 java -version
openjdk version "11.0.3" 2019-04-16
OpenJDK Runtime Environment 18.9 (build 11.0.3+7)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.3+7, mixed mode)
➜  ~ docker run --rm -t hseeberger/scala-sbt:11.0.3_1.2.8_2.12.9 javac -version
javac 11.0.3


"Call to undefined function" error, when the remote function exist

Getting:
lib/checker.ex: Call to undefined function Checker.Util.child_pid/1 on line 128
lib/checker.ex: Call to undefined function Checker.Util.child_pid/1 on line 136

You can see this repo at this specific commit to replicate the error
https://github.com/eksperimental/checker_basic/tree/bd2bcbe717863c4a1c0c7acc1866072815608e52
Also getting:
lib/checker/mock.ex: Undefined remote type Checker.url/0 on line 15

when the type does exist.

Thanks for reporting :) I will investigate it. Seems that modules are not loaded to the Gradualizer.

Thank you for the fix @Premwoik


dnspython3 has merged with dnspython

Just got the message:

dnspython3 is now superseded by the regular dnspython kit, which now supports Python 2 and Python 3.  Installing dnspython as a dependency.

Test and update dependencies accordingly.

Pending merge with #149

Merged in #159


renamed Datarized to Dataized

The name "dataization" is better, since it comes from "data" instead or "data_r_"

@rultor release, tag is 0.1.25

@rultor release, tag is 0.1.25

@yegor256 OK, I will release it now. Please check the progress here

@rultor release, tag is 0.1.25

@yegor256 Done! FYI, the full log is here (took me 9min)


Fix/multiple fixes

This commit contains:

Image Editor changes
Translation fix + remove redundant log message

I still have to check how the image editor stuff works, but does this PR fixes this issue?

Also, what about always declaring the types of parameters and return values? This greatly helps avoiding bugs IMHO.
Examples:

Instead ofpublic function checkDefaultEditor()
{
   ...
}

I'd writepublic function checkDefaultEditor(): void
{
   ...
}

Instead of /**
  * Return an array of Types that are associated with a specific package.
  *
  * @param Package $package
  *
  * @return Editor[]
  */
public function getListByPackage($package)
{
   ...
}

I'd write /**
  * Return an array of Types that are associated with a specific package.
  *
  * @return Editor[]
  */
public function getListByPackage(Package $package): array
{
   ...
}

No. Can't reproduce your issue

Can you give further details?

Okay i was writing too fast. When manually changing the slider this error occurs.

Maybe using a non English language? I logged in using Italian (you can install other languages on the fly in the /dashboard/system/basics/multilingual/update dashboard page).
In Italy we use commas instead of dots as the decimal separator (for example, in English we write 1,234.46 and in Italian we write 1.234,56): maybe this breaks the javascript library?

When i develop code i perform a lot of check and first submit a php file when my IDE (phpStorm) is telling me that everything is correctly. I know that's not a 100% guarantee but is your coding style really making the code less error-prone?
IMO the even opposite is the case.
In the past i had multiple help requests from customers because the core has changed anything and make the code more "bullet-proof" with these strict types like you suggested and then the core crashed because a 3rd-party-add-ons is dealing with the core and passing an invalid data type.
I'm using always PhpDocs to suggest to correct types.
Furthermore there are a lot of cases where you have to deal with multiple return types for example. I don't like the mixed coding styles. Since PHP 8 it is possible to return union types. But until the core doesn't depend on PHP 8 for me it doesn't make really sense to use the strict type conventions.

@mlocati No this has nothing to do with the language i think because i was able to reproduce with an english version too. I will investigate this.

About coding style: if someone is passing an invalid value to a function, it's already a problem. For example, in the case of the getListByPackage above, the code would break inside the findBy method of the Repository instance (maybe in a much deeper level), and that's makes less clear where the actual error occurred. If you expect a type, force that type.
Sure, a good IDE helps writing better code, but in complex situations automatic type inference is not always possible, and you think that the code works, but it simply hides a bug that may be discovered later on (maybe when the site went on production).
Of course, union types helps a lot in this direction; in the meanwhile I'd avoid writing "mixed", documenting the possible types with phpdoc.

@mlocati Because of the slider issue i don't get any details in the console. All other functions seems to work. This issue seems to be related to the image editor itself's, see https://github.com/nhn/tui.image-editor/issues/381

And yes i can confirm the ticket error description it's only happening on first load. When you re-opening the image editor this still works.

I still have to check how the image editor stuff works, but does this PR fix this issue?

I think I found the cause of that issue: https://github.com/concrete5/concrete5/pull/9258
We basically need to fully the CSS of the image editor before using it.


Fix telemetry state change event

Closes #6123

@pandemicsyn Do we have anything setup to run Docker containers under Pytest? I'm pretty uncomfortable with how we currently (don't) test telemetry, and it'd be great if we could spin-up Snowplow micro to ensure we're getting all the events/contexts we expect. If we don't have anything like this already, we can probably use https://github.com/avast/pytest-docker to help

@WillDaSilva we don't at the moment , but IMHO we should break this up into functional tests and plain unit tests. Starting with some unit tests would go along way. In that initial PR there was some brokeness with the Environment context generation, so when I added the PluginsContext I added some quick test coverage (https://github.com/meltano/meltano/blob/main/tests/meltano/core/tracking/test_plugins.py).
If we can get some unittest coverage we can follow it up and augment it with some functional tests that run as part of CI that make sure things are landing in snowplow micro as expected.


feat: notify user of token expiry

Fix #518
Fix #553

@tripodsan I had to make some more changes to fix a window reload bug and make the notifications show up more consistently. Appreciate you taking another look!

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

GitHub release
v6.33.0

Your semantic-release bot :package::rocket:


Max Volume

This is 100 in Minecraft, but in all our other targets it's 255.
Any thoughts on this?  Should we be consistent?

Minecraft volume is different from how volume is handled in our other targets. I'm guessing we're using 255 in micro:bit and arcade due to hardware considerations, but since there isn't any hardware to consider in Minecraft, the max volume value of 100 makes sense.
Basically, Minecraft volume is on a float spectrum between 0 and 1 and the 0 to 100 value used in the block is essentially a multiplier. So if a user sets the volume to 50, the value that will be used for Minecraft volume will be 0.5. According to the Minecraft wiki about volume, changing the volume value will just modify the distance in which a sound can be heard, so higher values allows the sound to be heard from farther distances and lower values not as far.


Date picker - autoOk prop for automatically Accepting if you click on a date directly.

Would be nice to have.

+1
And also it will be great if it also support minDate or maxDate such restrict function..

+1

Fixed with #538


Is it possible to change the intensity color based on the number of heatpoints combined in view?

I want to achieve this coloring.
1-1000 yellow
1001-2000 orange
2001-3000 red
3001-4000 maroon
4001-5000 mahogany

I don't think it is a built in feature. A workaround could possibly be: If each of these points have an intensity of 0.0001 you could input these five colours and set max point intensity to 0.5.
NB:  I have not read the actual source code. This assumes the colours in the heatmap is simply calculated from the sum of point intensities in the grids it creates. Meaning, If there are 5000 points in one square of the grid, that square should get intensity  5000 * 0.0001 = 0.5, which will be mahogany. We also have to assume the range is divided equally between the five colours, I don't know if any of this is true.

@Sti2nd thanks. I'll try this.

Doesn't work. All I get is mahogany and I have 296 heats. It should return yellow.

Well, it does depend on your zoom level or how large the clusters in the grid are in the source code.
You only have 296 points on your map?

@Sti2nd yeah. But I am not getting yellow. I tried it in all zoom value. all mahogany

Oh well, I guess my assumptions were wrong or it might be a bug somewhere.
I see there are quite a few issues about heat colour, and a some pull requests as well... https://github.com/Leaflet/Leaflet.heat/pull/78
Since this repo is not actively maintained anymore, your best shot is perhaps to modify the source by e.g. basing it off the already existing pull requests.


Update develop with main changes

These changes slipped under the radar.

Does it make sense to keep this branching main/develop? Can't we just use main a do releases?

Probably it makes sense to use main only. But will double check things first.


BUG: CanvasWrapper's onDrop event assumes canvas is positioned in the top left of the document.

Right now the onDrop event handler assumes determines the position to place a node when the on drop event fires based on the clientX and clientY properties of the drop event, correcting for the Chart's offset.
This works when the canvas is in the top left hand corner of the document. However, when the Canvas is positioned to the right, or down, the clientX and clientY values do not correspond to the position of a users mouse when the drop event occurred.
Proposing making the following change to the onDrop method that gets passed to ComponentInner in Canvas.wrapper.tsx
onDrop={ (e) => {
  const data = JSON.parse(e.dataTransfer.getData(REACT_FLOW_CHART))
  let elementOffset;
  if (this.ref.current){
    elementOffset = {
      x: this.ref.current.offsetLeft,
      y: this.ref.current.offsetTop
    }
  }else{
    elementOffset = {x: 0, y: 0}
  }
  onCanvasDrop({ data, position: {
    x: e.clientX - (position.x + elementOffset.x),
    y: e.clientY - (position.y + elementOffset.y),
  }})
} }

this would get the actual offset of the HTML element on the page and include this when calculating where the node should drop.
Does anyone see any issues with this? Should I make a PR?

On further testing, offsetLeft and offsetTop probably aren't sufficient.
Would probably need to be something like:
let elementOffset;
  if (this.ref.current){
    let {x,y} = this.ref.getBoundingClientRect()
    elementOffset = { x, y }
  }else{
    elementOffset = {x: 0, y: 0}
  }

Is there a better place that this offset could be calculated and stored somewhere stateful? Does it make sense to add it to the resize observer?

This has been bugging me as well - would be great to get this sorted.

Looks like the offset is already being stored in state, and updated through the resize observer, just not being used when calculating the position property of the new node created on the onDrop event.
Made a PR that adds it in, since it seems pretty cut and dry and unlikely to affect anything else
https://github.com/MrBlenny/react-flow-chart/pull/34


Investigate --coverage support

It's possible that this is already working, because Babel uses this runner and collects a coverage when running it's tests: https://github.com/babel/babel/runs/5789483528. If it already works great, I just need to document it.
It's also possible that it's only working partially, or that it's not working at all and that Babel's coverage reporting is based on something else.
(cc @psychobolt - https://github.com/facebook/jest/issues/9430#issuecomment-1086946059)

I would assume coverage doesn't work, but I've been wrong before! 😀 However, adding support for v8 based coverage should be straight forward. E.g. use https://github.com/SimenB/collect-v8-coverage (what Jest uses) and store it as v8Coverage on the test result: https://github.com/facebook/jest/blob/80cf80055682919251b9567ef482755d5f060d47/packages/jest-runner/src/runTest.ts#L338.

Thank you!

I don't think the coverage works, I added c8 when using in Prettier, https://github.com/prettier/prettier/blob/3cbee742a792413211eea1e4fe2d0dad26ff37ea/.github/workflows/dev-test.yml#L79

Yes I assumed --coverageReporter=v8 would work. However, that seems to not work as well.

Yeah, runner needs to hook it up. But should as mentioned be very little code 🤞

This CI log maybe useful, I got a error message here

Details
ERROR: Cannot assign to read only property 'message' of object 'SyntaxError: import.meta may appear only with 'sourceType: "module"' (293:39)
Consider renaming the file to '.mjs', or setting sourceType:module or sourceType:unambiguous in your Babel config for this file.'
STACK: TypeError: Cannot assign to read only property 'message' of object 'SyntaxError: import.meta may appear only with 'sourceType: "module"' (293:39)
Consider renaming the file to '.mjs', or setting sourceType:module or sourceType:unambiguous in your Babel config for this file.'
    at parser (/home/runner/work/prettier/prettier/node_modules/@babel/core/lib/parser/index.js:87:21)
    at parser.next ()
    at parse (/home/runner/work/prettier/prettier/node_modules/@babel/core/lib/parse.js:31:37)
    at parse.next ()
    at evaluateSync (/home/runner/work/prettier/prettier/node_modules/gensync/index.js:251:28)
    at sync (/home/runner/work/prettier/prettier/node_modules/gensync/index.js:89:14)
    at getAst (/home/runner/work/prettier/prettier/node_modules/istanbul-lib-instrument/src/read-coverage.js:16:12)
    at readInitialCoverage (/home/runner/work/prettier/prettier/node_modules/istanbul-lib-instrument/src/read-coverage.js:31:17)
    at generateEmptyCoverage (/home/runner/work/prettier/prettier/node_modules/@jest/reporters/build/generateEmptyCoverage.js:155:72)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

And the error disappear when add coverageProvider: 'v8', log

Yeah, the error is probably caused by istanbul/nyc reading coverage data that does not exist (I'm still wondering how Babel's coverage currently works :shrug:)

I wounder why this error swallowed? https://github.com/nicolo-ribaudo/jest-light-runner/issues/6#issuecomment-1090208879

See #13, I think that's working 🙂

Hi all, this might be obvious for some, but maybe not for others, so I'm leaving it here.
The jest-light-runner decreased our running time by almost a 5-fold, which is a tremendous performance increase, thanks! 🎉
But we couldn't get the coverage to work trying the proposed on-the-fly babel-register-esm loader option, but that doesn't seem to work.
As an alternative, we now use the v8 instrumentation and c8 as follows:
npx c8 npx jest


new: new field 'input'

#50 this is my proposal for this fields.
The test are not amazing for now (they accept any attribute regardless of the input type).

Thank you for your PR. I need more time to check it, ok?

I think, we can't handle all types with one field. Because date* types there are extra properties and methods to format date to the input and to the model like here
Do you have any idea how to solve it?

A simple check to see the this.schema.format could be enough:
if (typeof this.schema.format !== "undefined" && value != null) {
	return moment(value, this.schema.format).format(this.getDateFormat());
}
return value;

If the user don't want to format the date or if there is no reason to use format (for non date like input), it simply return the raw value.

Not enough, because current date fields (datePicker, pickaday) are stored the data in Unix format without format. If you set format property it will store as a formatted date string. But HTML5 date* field raw format is string. So we always should format this raw values.
I created a fiddle to check the raw values of HTML5 date fields: https://jsfiddle.net/ndz05ku4/2/

What about using inputType ?
if (value != null) {
    if (this.schema.inputType === date ||
        this.schema.inputType === datetime ||
        this.schema.inputType === datetimelocal ||
        this.schema.inputType === time ||
        this.schema.inputType === week ||
        this.schema.inputType === month) {
            if (typeof this.schema.format === "undefined"){
                // Unix formating
            }else{
                return moment(value, this.schema.format).format(this.getDateFormat());
            }
    }
}
return value;

Ok, but skip month and week. They are not full date, can't be format with moment. Stays in string.

I'm skipping time too

Progress: date, datetime and datetime-local can use the same model as Pikaday, dateTime (with date format) without problem. Modifying one or the other end in the same model format (UNIX) and update value.
time work well with dateTime (with time format), although Chrome don't allow to input seconds (but display them if set). Edge is fine with seconds.
month and week are treated as string.

Great thank you!

@icebob Can I add a new schema to the commit ?
I have reorganize the fields so that it is easier to use
screenshot

Sure :)

@icebob I think it is ready to merge, no ?


Fix pulsar-dashboard and docker-compose.yml,Port 8080 is valuable. We should release it.

Port 8080 is valuable. We should release it.
Expected behavior
Browser at pulsar-dashboard, should be have Tenants   |   Brokers   |   Topics   |   Clusters data.
Actual behavior
Browser at pulsar-dashboard, Non data:No tenants,,,etc.
Steps to reproduce
How can we reproduce the issue

Create file:docker-compose.yml

version: '3.5'

networks:
  cherry-network:
    name: cherry-network
    driver: bridge

services:
  pulsar-0:
    container_name: pulsar-0
    hostname: pulsar-0
    image: apachepulsar/pulsar
    networks:
    - cherry-network
    environment:
    - PULSAR_MEM=" -Xms512m -Xmx512m -XX:MaxDirectMemorySize=1g"
    command: >
      /bin/bash -c
      "bin/apply-config-from-env.py conf/standalone.conf
      && bin/pulsar standalone"
#    volumes:
#    - ~/volumes/cherry/data/pulsar:/pulsar/data
    ports:
    - "6650:6650"
    - "9393:8080"

  pulsar-dashboard:
    container_name: pulsar-dashboard
    hostname: pulsar-dashboard
    networks:
    - cherry-network
    image: apachepulsar/pulsar-dashboard
    depends_on:
    - pulsar-0
    ports:
    - "83:80"
    environment:
    - SERVICE_URL=http://pulsar-0:9393

docker-compose up
browser at http://<IP_ADDRESS>:9393/admin/v2/persistent/public/functions/coordinate/stats it is ok
browser at http://<IP_ADDRESS>:83 All data is null.

System configuration
Pulsar version: 2.2.0

I had found how to change config.

/volumes/cherry/configs/pulsar/standalone.conf:/pulsar/conf/standalone.conf

webServicePort=9393

That is wokr fine


[BC] Merge from sgpyc/bkj/bc-v2 to bkj/bkj/bc-v2

Most edits are formatting and removing completed TODOs.
Some actual actual code edits:
bc_problem.cuh :
*. src_node is a single value, not can be past into kernel via lambda parameters.
*. inserted a streamSynchronize for each GPU in Problem::Init(), otherwise the sub-graph may not be fully transmitted to GPU when computation starts.
bc_enactor.cuh :
*. change -1 to util::PreDefinedValues<>::InvalidValue, when it means invalid value; this is more suitable for multiple datatypes, both signed and unsigned.
*. added frontier.reset = true before advance in backward iterations, otherwise it won't take the frontier set by Gather().
*. replaced replace MemsetCopyVectorKernel() with Array1D::ForAll().
*. enabled size checking in Gather().
bc_test.cuh:
*. enabled result print out and validation.
bc_app.cuh :
*. enabled src parameter, "srcs" is an internal parameter based on "src" given in the command line.
*. enabled external interfaces gunrock_bc() and bc().
TODOs after merging:
*. accumulated BC values and CPU reference (boost, OpenMP, or serial)
*. solve inf and nan values issue when running on delaunay_n21

Sorry for picking a wrong branch.
The accumulated BC values are calculated from multiple sources, not just from a single one. If I remembered correctly, running BC multiple times without resetting the BC values will produce that.
The CPU reference also need to add back the Boost part.
The nan and inf values are only for one dataset; I suspect it's caused by some edge cases.
This issue happens with both CPU and GPU implementations, so it should be straight forward to find, but may take some time. I will file an issue in the main repo when merged, so we can keep track of it latter


ci: fix ci tests

fix ci tests
Enhancement:
Reason:
Result:
Issue Tracker Tickets (Jira or BZ if any):

[citest]

[citest]


Assertion error

Hi,
I get an assertion error when setting a dummy presence device to false. When setting it again to false I don't get the error.
The error is
"AssertionError: state is 'event' or state is true or state is false"

I cannot reproduce. Can you provide some screenshots of you configuration?

I've used this flow. When injecting true and then false it goes into the error. The strange thing is for some presence devices I don't get this error.
[{"id":"f719549d.894238","type":"device out","z":"526c0929.103db8","device":"rik-samsung","action":"changePresenceTo","parameter":"","x":1364.8665771484375,"y":152.46661376953125,"wires":[]},{"id":"fc88ed5e.8e0ab","type":"change","z":"526c0929.103db8","name":"","rules":[{"t":"set","p":"parameter","pt":"msg","to":"payload","tot":"msg"}],"action":"","property":"","from":"","to":"","reg":false,"x":983,"y":272,"wires":[["f719549d.894238","cad8651a.151a78"]]},{"id":"e2e9fe9.b8db1","type":"inject","z":"526c0929.103db8","name":"","topic":"","payload":"false","payloadType":"bool","repeat":"","crontab":"","once":false,"x":790,"y":252,"wires":[["fc88ed5e.8e0ab"]]},{"id":"dcff804d.a8654","type":"inject","z":"526c0929.103db8","name":"","topic":"","payload":"true","payloadType":"bool","repeat":"","crontab":"","once":false,"x":799,"y":299.3333435058594,"wires":[["fc88ed5e.8e0ab"]]},{"id":"cad8651a.151a78","type":"debug","z":"526c0929.103db8","name":"","active":true,"console":"false","complete":"true","x":1285,"y":268,"wires":[]}]

I created a DummyPresence device called "rik-samsung" and used your flow. Unfortunately I was not able to reproduce this on my system.....

Thanks for your help. I have deleted the devices from pimatic and created new ones (with new names). Now it is working ok. So nothing node-red related it seems.


Notifications

I just got the very basic building blocks "done" even though this doesn't actually properly register the token to HA yet. Hoping someone else can help out to finish it up. The success point for this is being able to receive simple text only notifications. Extra credit if you implement any of the iOS features like custom sounds, inline images/camera stream/map or whatever. Full detail on those here.
Things to do still:

[ ] Implement foreground receiving
[ ] Store push token somewhere so it can be sent as part of device registration and/or get the FirebaseInstanceId.getInstance().instanceId call working (I don't have a firm grasp on Kotlin co-routines yet, I'm sure someone a bit more competent can get it done quick!)
[ ] Ensure we are listening for new and updated tokens and send to Home Assistant
[ ] Adapt server side code as needed for Android (this is entirely on me, @robbiet480)

Fixes #7

Closing in favor of #140


Add htmx

Name with link
htmx
https://htmx.org
Description
Link to the vector file, preferably from an official source
Unofficial SVG: https://plugins.jetbrains.com/files/20588/418328/icon/pluginIcon.svg
Official logo 1: https://github.com/bigskysoftware/htmx/blob/master/www/static/img/htmx_logo.1.png
Official logo 2: https://github.com/bigskysoftware/htmx/blob/master/www/static/img/htmx_logo.2.png

Added in 92bb74e98bca1ea1ad794442676ebc4e75038adc
Thanks


DBeaver EE asks for license which blocks access to preferences to set proxy

DBeaver EE tries to connect to internet to generate a trial license.
But it is not possible to access internet without entering proxy information, which is blocked by UI.
Since EE version is for Enterprise and most enterprise company uses proxy, it makes it impossible to have use EE version.

For such cases it is possible to generate trial license on the web site (https://dbeaver.com/trial/).
And then copy-paste license text in the license manager dialog.
Although providing access to proxy settings from license manager dialog also makes much sense, thanks for noticing.


Strange behavior of feature setStyle on Selection interaction

As of version 3.15.0, I've noticed that the setting feature style on the 'select' event for the Selection interaction has behaved very strangely. The style I'm attempting to set on the selected feature will either be set on seemingly random nearby features as well, or the entire background will have the style applied... I'm not sure what's going on here.
I've made an attempt at creating a minimal jsfiddle of the problem here.
At first I thought it was a problem with using setStyle on features in general, but I couldn't reproduce the problem until using the selection interaction.

Thanks for the good bug report. Obviously the recent vector renderer optimizations (#5149) do not work when features are skipped in the replay - the Select interacion uses ol.Map#skipFeature.
To make it work, when skipping a feature in the replay, we need to check if a fill or stroke is pending, and call context.fill() or context.stroke() and context.beginPath().

@fredj, do you want me to take a closer look? Or are you guys working on it?

I'm not looking at it right now but I've added the label to not forget that we must address this issue


Update Hexo.gitignore

Pull Request
Thank you for contributing to @dvcs/gitignore and https://www.gitignore.io.
New or update
Select the appropriate check box for this pull request. This helps when merging to ensure there are no conflicts with other templates or misunderstandings of how thee template list works.
New

[ ] Template - New .gitignore template
[ ] Composition - Template made from smaller templates
[ ] Inheritance - Template similar to an existing template
[ ] Patch - Template extending functionality of existing template

Update

[x] Template - Update existing .gitignore template

Details
Current Hexo.gitignore would ignore not only ./db.json from repo root dir, but also node_modules/mime-db/db.json. Missing of the last one will cause Error: Cannot find module './db.json' after cloning into a new client.

@kongwy Thank you for your contribution. I'm closing this PR for now, though, since we haven't got a feedback regarding our question.
Feel free to reach out if you still feel this should be accepted.


Add plot xy

Please note that we don't use d3.js to manipulate the dom. The dom is managed by React. However there are many very practical utilities in d3.

This means that you should render svg elements with jsx, not with d3

Thanks
It still draft
I will use dj just for calculations

two components created:
-create multilines plot in details (add axes lines)
-create plot directly from xml file

You can completely remove the XmlPlotXY component. It's not part of the scope of this project to generate a plot from the json Luc sent in the issue (variables.json). The json was only to give you some XY data for the stories.

You can completely remove the XmlPlotXY component. It's not part of the scope of this project to generate a plot from the json Luc sent in the issue (variables.json). The json was only to give you some XY data for the stories.

Aaaa okey , i added a question in the issus but i finished working on it before getting an answer, thank you

Do i have to delete the story?

We focus on react-plot instead.


Where to find examples for the current source version?

Where to find examples for the current source version?
The files reffered in the readme are not longer present in this repository.

For an example of the current code, see ucat.c at the root of the repo.


Task 24

The duration of time must be dynamic, because the mouse click is relative, it different from one mouse to another

@RanimHelamiah build is failing for a type issue, also when I tested clicking on the background did not deselecting the module anymore


[Bug]: Terminal is not blur / transparent

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
The terminal of VSCode is always of the color of the Theme. I tested with many Themes you suggested and there is the same issue with all.

Expected Behavior
I expect to have the terminal in blur / transparent effect.
Steps To Reproduce
No response
Environment
- OS: Windows 11 23H2
- VSCode: 1.85.2
- Extension: 1.1.29
- Theme: Tokyo Night Storm

Anything else?
No response

Please check FAQ: https://github.com/illixion/vscode-vibrancy-continued#effect-doesnt-work-for-terminal


Add additional ensemble filename patterns

Based on Stephen's regexes in overlays:
http://fcm1/projects/roses_mi/browser/b/c/6/0/6/trunk/oemplotlib/oemplotlib/config.conf?rev=167053#L25
Also need to handle duplicate member numbers, such as in Global. This might be renumbering, or something else.

Under /net/home/h02/frhl/CSET/CSET, I tried running cset bake input.pp test.nc first_recipe.yaml
where my first_recipe.yaml is copy/paste from https://metoffice.github.io/CSET/reference/recipe-format.html and was aiming to point to a 'random' K-Scale .pp output file. My input.pp is a soft-link to a file somewhere else, but on first reading I got similar issue with filename reading. Looks like maybe there are some default assumptions on filenames currently?? My trying to specify filename format in the recipe didn't do much.

– Huw

t would be good to be able to read in filenames with wildcards for dates to grab several files (* or [1-3]?))

It is already possible to use a wildcard (*) for getting multiple files, though I don't think this is documented in the read operator.


Remove the full-screen button

The full-screen button at the bottom-left corner should be hidden when PWA is installed. As PWA will already be in full-screen mode.

I can do this for you assign me this work.

can you please time how to run this project in our system?

can you please time how to run this project in our system?

It's a react app. You need node.js installed.
npm install
npm run start

Solved-------The full-screen button at the bottom-left corner should be hidden when PWA is installed. As PWA will already be in full-screen mode.
https://user-images.githubusercontent.com/88885329/189996105-1cd3e4cc-4121-4c8d-b31f-cfb9e6863bd1.mp4

Solved-------The full-screen button at the bottom-left corner should be hidden when PWA is installed. As PWA will already be in full-screen mode.
https://user-images.githubusercontent.com/88885329/189996105-1cd3e4cc-4121-4c8d-b31f-cfb9e6863bd1.mp4

Good Work but full-screen icon should be hidden only when the app is installed and not when it's running on a mobile device.

Hello there, @yashchaudhari008! I can solve this issue!!!
Can you please assign this issue to me?

Hey there @yashchaudhari008,
I made a Pull Request #17 for this issue, can you please review it?
Thanks!


🐞 Interactive UI drops stderr

What is the issue?
Just upgraded to the latest version of dagger 0.5.2 (golang sdk) to use the new pipeline logging features. I see the error output in the regular view, and in the "non interactive view" but I dont see stderr in the "interactive view".
Client initialization looks like this
c, err = dagger.Connect(ctx, dagger.WithLogOutput(os.Stdout), dagger.WithLogOutput(os.Stderr))

Step execution looks like this
_, err := t.plan(client, dir).Stderr(gctx)

Log output
Here's the output in each view. Note that I can't scroll down any further to see the error details in my terraform init step.
interactive dagger run -i <my_cli>

regular dagger run <my_cli>

standlone <my_cli>

Steps to reproduce
See above client initialization and step execution.
SDK version
0.5.2
OS version
osx 13.3.1

Hard to tell what's going on here - would you be able to put together steps to reproduce this that I can run myself?
I just pushed some more fixes/tweaks for the interactive TUI (#5232), so this might be fixed by the next release, but I can't be completely sure. I haven't seen any issues with dropping output.

@stobias123 just wanted to check in to see if you could add some additional details that @vito requested?

Hey guys sorry for the delay here. @vito  - just added the details of the t.plan func - is that sufficient?

@stobias123 we will close this as resolved for now, but feel free to reopen if you need additional support.


Allow godot exports to be command line programs: do not load the first positional argument as a scene path; or allow overriding command line processing

Does not have a posted use case. Needs to recreate.


Update readme for Leap's collection of examples page

Added content is mostly from the JN but also added an installation section.

I'll just note here that the CI failures are just because of the API token, locally the unit tests pass


[Task] DSL to support export , comments

The dsl should start with 'export ' syntax and shall support comments outside the export block

Hey team! Please add your planning poker estimate with Zenhub @ayushpahwa @nsarupr @srix


Inconsistent reporting of a current day's price

When trying to retrieve stock data for the current day, it does it extremely inconsistently, if at all. Setting period='2d' only gives me yesterdays data, and period='1d' also will only give me yesterdays  data. Even if i lower the interval.
SOMETIMES it will give me the current days data, but its extremely inconsistent on if it does or not. Sometimes it will also show 'nan' for today's data, and other times todays date will just be left off the data entirely. This bug occurs with the yf.Tickers object, yf.download, and yf.TickerI'm not sure if this is a bug with yfinance or a change that yahoo finance made internally.

It looks like this is just an issue with YahooFinance not providing the most recent days' ticker values in Historical Data

I have the same issue. sometimes the current day's data is returned and sometimes it's not. Unfortunately, I have not found any solutions for this. I noticed that even when I checked the prices on Yahoo Finance website, for a brief moment after the page is loaded, the data is the same old data I get from History(ticker)

Problem still happening?

yes this does still happen, has anyone been able to workaround this?

I will provide the output results tomorrow when it is intraday, but here was the code I used to see inconsistencies. The code seems to work consistently at market close.
import yfinance as yf
test = yf.download('SPY', start=datetime(2023, 6, 12))
test

Review debug log - new feature since this issue was created

Nevermind, I think I see the issue now.
I see the end parameter is defaulted 1 day prior to now(), so I understand now why.
end: str
    Download end date string (YYYY-MM-DD) or _datetime, exclusive.
    Default is now
    E.g. for end="2023-01-01", the last data point will be on "2022-12-31"


Wrap all date/time intervals with isoparse

closes #1182
(Note: I considered doing this in d3-time, but it would mean adding d3-time-format as a dependency of d3-time.)

I had the same hesitation but went the other way:

since we're not going to remove the duck-typing of d3 time intervals (for the bin transform), we might as well use it consistently.
this could help people who use string dates and funky intervals—for example, transitioning from 1 month interval to 2 months interval requires only one operation (switching from "month" to d3.utcMonth.every(2)), instead of that + coercion of strings to dates.

And, it's well defined in the README: “Time intervals are intervals that are also functions that return a Date instance when called with no arguments.”

I’ve surveyed the code base to see where we might need coercion for intervals.
The (implicit) interval transform uses intervals in maybeIntervalK and maybeIntervalMidK. Both of these would benefit from an implicitly-coercing interval. (Though it would also be possible to coerce all the values prior to invoking the interval.)
https://github.com/observablehq/plot/blob/820144e4a89b07f2a212f66156b4af0dc48a250b/src/transforms/interval.js#L31
https://github.com/observablehq/plot/blob/820144e4a89b07f2a212f66156b4af0dc48a250b/src/transforms/interval.js#L50
A scale transform can be specified as an interval as described in #1182. This happens in applyScaleTransform when the interval.floor is promoted to a transform. This would benefit from an implicitly-coercing interval, too.
https://github.com/observablehq/plot/blob/820144e4a89b07f2a212f66156b4af0dc48a250b/src/plot.js#L365-L367
The axisMark can also use the scale interval to compute ticks. This would not benefit from an implicitly-coercing interval: the scale should already have coerced values at this point, and we wouldn’t want the interval to use different coercion than the scale.
https://github.com/observablehq/plot/blob/820144e4a89b07f2a212f66156b4af0dc48a250b/src/marks/axis.js#L520-L521
Ordinal scales use intervals to compute the domain. This would not benefit from an implicitly-coercing interval: we would need to do the coercion earlier on the scale’s associated channel values, so that the extent is computed correctly and so that the scale’s imputed domain matches the channel values.
https://github.com/observablehq/plot/blob/820144e4a89b07f2a212f66156b4af0dc48a250b/src/scales/ordinal.js#L100-L101
The contour mark can use an interval to compute thresholds. The majority of the time the contour mark will be used with numeric data, but it is theoretically possible to compute contours of arbitrary values, including temporal data. So, this might benefit from implicit coercion. However, it again would not work to perform that coercion within the interval; we would need to coerce all the contour values, not just coerce when computing ticks.
https://github.com/observablehq/plot/blob/820144e4a89b07f2a212f66156b4af0dc48a250b/src/marks/contour.js#L191
The bin mark can likewise use an interval to compute thresholds. It already performs coercion and would not benefit from additional implicit coercion inside the interval.
https://github.com/observablehq/plot/blob/820144e4a89b07f2a212f66156b4af0dc48a250b/src/transforms/bin.js#L232
To summarize the effect of implicitly-coercing intervals:

interval transform 👍
scale transform 👍
ordinal scales 👎 (incorrect result)
contour mark 👎 (incorrect result)
axis mark 👎 (redundant with existing coercion)
bin transform 👎 (redundant with existing coercion)

My recommendation therefore is, instead of implicitly-coercing time intervals, that we coerce values as appropriate prior to using the interval similar to what the bin transform already does. In the case of ordinal scales, we’ll also need to coerce to numbers, not just dates, so that we compute the extent correctly.

I have revised this PR's description with the TODO.


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 206 ms

Resolved: ClamAV performance has improved in 5165864 after 539 days, 23 hours, 42 minutes.


StaticFile / fromResource: effects not handled.

As described in https://github.com/http4s/http4s/pull/2541, the fromResource method of the StaticFile has some effectual operations (getResource) that should be wrapped in delay.

Fixed by cherry-picking #2611.