Fix code coverage data generation

Description
This PR fixes code coverage data generation for the Almanack (which wasn't generating coverage.xml files properly).
Closes #209
What is the nature of your change?

[ ] Content additions or updates (adds or updates content)
[x] Bug fix (fixes an issue).
[ ] Enhancement (adds functionality).
[ ] Breaking change (these changes would cause existing functionality to not work as expected).

Checklist
Please ensure that all boxes are checked before indicating that this pull request is ready for review.

[x] I have read the CONTRIBUTING.md guidelines.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own contributions.
[x] I have commented my content, particularly in hard-to-understand areas.
[x] I have made corresponding changes to related documentation (outside of book content).
[x] My changes generate no new warnings.
[x] New and existing tests pass locally with my changes.
[ ] I have added tests that prove my additions are effective or that my feature works.
[x] I have deleted all non-relevant text in this pull request template.

CI appears to have become out of sync somehow, referencing out of date versions of files which pertain to the changes. Going to close this PR and reopen in the hopes that it resolves.


not check failed status when doing live migration hook

What this PR does / why we need it:
the live migration hook check should only check completed status , not the failed statue which just indicate a error, sometimes a good live migratino only mark complete but no failed status
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #2652
Special notes for your reviewer:
Release note:

I don't think it would be enough to resolve #2652: let's say we get two migration requests at the same time and no migration was executed before, both may pass this part of the validation webhook.

oh... that's a good suggestion, this seems need some lock introduced..

oh... that's a good suggestion, this seems need some lock introduced..

👍

but this should fix part of the issue?

Yeah, I believe it would fix part of the issue.
Another part I'm not so sure about is whether the following race is possible:

Request A gets to the apiserver
VirtualMachineInstanceMigration is added for request A
The apiserver returns positive response
Request B gets to the apiserver
VirtualMachineInstanceMigration is added for request B
The VMI is updated with the status of the migration initiated by request A


make write_lef and others write out files atomically

Description
A half-written .lef file can be lying around after a crash which complicates e.g. deltaDebug.py.
Suggestion:

modify all write_* commands to write to a temp file
when the write completes, rename temp file to final name

This way there are no partial files lying around
Suggested Solution
No response
Additional Context
No response

Hello @maliberty @oharboe , I'd like to work on this issue. Could you please assign it to me ?

@annapetrosyan26 You can simply create a pull request without being assigned this task, I don't have the role to assign github issues in this project.
I haven't seen that @maliberty assigns github issues to new contributors, but perhaps that's something that would be approperiate?

Thank you @oharboe for the clarification. Then I'll work on the issue and once the code is ready I will create a pull request.

@maliberty Fixed, no?

Fixed in https://github.com/The-OpenROAD-Project/OpenROAD/pull/5109


 Checkout "
OSError: C:\ Users\15729\ Downloads\Qwen2- Boundless- main\Qwen2- Boundless- main does not appear to have a file named config.  json.Checkout  https://huggingface.co/C:\Users\15729\Downloads\Qwen2-Boundless-main\Qwen2-Boundless-main/None'foravailablefiles.


nav-justified doesn't work at any IE versions and description of feature is wrong

Hi! I have recently noticed, that ".nav-justified" class doesn't work in any IE versions. In IE all menu items are rendered with the same width instead of the same indents. And also I've noticed, that in description of this class is written the following:

Easily make tabs or pills equal widths of their parent at screens wider than 768px with .nav-justified. On smaller screens, the nav links are stacked.

But it's definitely wrong, because normal behaviour of nav-justified is rendering menu items with equal indents, but not equal widths

I'm unsure if this was targeted for v3 or v4, but it sounds v3. Justified nav options are coming back in v4 with flexbox being our layout method of choice though, too.


Vectors not connecting

I have wire-prod installed and registered two vectors successfully to it.
The issue comes up when I try to connect to my vectors after they have either shutdown or the service rebooted. If I go to the connect I get this error
error: rpc error: code = Unauthenticated desc = unexpected HTTP status code received from server: 401 (Unauthorized); transport: received unexpected content-type "text/plain; charset=utf-8"
Do I need to re-activate the bots to get it to work?

Just an update, re-activating fixed the issue - but could you explain what the underlying problem was?
Thanks.

I'm experiencing something similar. I've added a Vector, setup is complete, but when I try to connect to it, it does not show up in connectable robots...

I'm experiencing something similar. I've added a Vector, setup is complete, but when I try to connect to it, it does not show up in connectable robots...

Are you saying your drop down box is empty? if that's the case try going to
https://keriganc.com/vector-wirepod-setup
You shouldn't need to re-install the firmware, just pair your bot and click the "Activate" button, this should re-register your vector to the service and it should be connectable.

Closing due to inactivity.


PRs without creating branches?

From my experience it slows down work considerably as i switch from one task to another. Besides my local repo is a mess.
Could we possibly accept PRs in a more traditional way?

yeah im 100% open to that
whats your suggestion?

If you ask me i would keep it as simple as we can for now :)
I'm no expert by any means but allow me to share some more thoughts and ideas:

We're faaaaaaaaaaaaaaaaaaaaaaar from any kind of API stabilization
Farcaster protocol on it's own is heavily evolving and many things WILL change
With regards to above i think we should focus on getting basic things right and start building whatever we think may prove useful in the long run
Lets stick to one branch and accept PRs without requiring additional branching (being early we can always revert!)
More branches can be added as we see fit, but lets branch only when necessary/comfortable (projects with hundreds of branches are very cumbersome to explore)
Lets stick to symantic versioning https://semver.org so a) anything can change below 1.0.0 b) stick to 0.1.0 for now and increase minor/patch version as needed (we don't have to do it often)
I would get rid of extra documentation for now and stick to doc-comments. It becomes a nightmare to update anything except doc-comments with API not stable. We can rm doc for now and bring it back when farcaster-rs becomes usable (so your work is not lost)

Do you use farcaster client with DC support?

re 1-3: heavily agree, what kind of things do you think this includes? i want to add posting & auth support but until the jwt method changes (which it seemingly will) thats a very hard task due to how they sign their jwts
re 4-5: sounds good to me
re 6: sounds good to me. ill bump to 0.1.0 tn
re 7: makes sense, lets do it
re 8: yeah that sounds good to me as well
I don't use DC very much, they just seem fairly unstable right now compared to the alternatives (telegram, twitter dms, etc...) since they can fail at random & disappear after a while

update: merged, bumped to 0.1.0 standard, publishing now
@MistApproach thoughts on using https://github.com/rhysd/cargo-husky to add a cargo-fmt pre-push hook?
we could also avoid writing tests for now since we will probably have to rewrite them multiple times with breaking changes in major ways, but add tests to pre-push eventually

Thanks, never used husky myself but it sounds like a good idea - i find myself forgetting about fmt before pushing sometimes
As for the tests i totally agree


[Bug]: Stuck in end portal + discord unban

/mv version -p output
https://paste.gg/4a1dae1b12b74920bee63063a099a14c
Server logs
https://paste.gg/p/anonymous/d6b220c7be25472ca8eb9afc63ef6d11
Server Version
This server is running Paper version 1.20.6-137-master@bd5867a (2024-06-04T21:04:28Z) (Implementing API version 1.20.6-R0.1-SNAPSHOT)
You are running the latest version
Previous version: 1.20.6-36-3fb77f9 (MC: 1.20.6)

Bug Description
When entering the end portal you will get stuck like you're in a loophole.
Additional:
Looks like I got banned from MV discord long long time ago back when my account got hacked and was used to spam bot msgs. Please unban me. Discord ID: daddyrob
Steps to reproduce

Install Multiverse Plugin
Install latest MC Paper
Enter End portal
Get stuck

Agreements

[X] I have searched for and ensured there isn't already an open or resolved issue(s) regarding this.
[X] I was able to reproduce my issue on a freshly setup and up-to-date server with the latest version of Multiverse plugins with no other plugins and with no kinds of other server or client mods.

Assume you are talking about the exit portal in the end?
/mvm set respawnworld world world_the_end

Oh, so this is how you fix it? I'll take a look at it. Can't this be fixed
in the future so additional commands like this won't be necessary?
On Mon, Jun 10, 2024, 6:34 AM adnap @.***> wrote:

Assume you are talking about the exit portal in the end?
/mvm set respawnworld world world_the_end
—
Reply to this email directly, view it on GitHub
https://github.com/Multiverse/Multiverse-Core/issues/3069#issuecomment-2156819461,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2DRZFFBBQNJTEWEVGQUO73ZGTJ6BAVCNFSM6AAAAABJA7HZN2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJWHAYTSNBWGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Assume you are talking about the exit portal in the end? /mvm set respawnworld world world_the_end

The command you gave me worked!
I don't remember why I didn't remember doing this before. But yeah, I hope this is fixed in the future update of Multiverse since it will help a lot of owners.
Also, could you please unban me on Multiverse Discord?
Discord ID: daddyrob
I'm certain I only got banned long long time ago when my account got hacked.

It's because the exit portal is treated as a death event. It use to be a portal event. Can't remember when it changed. (No doing of multiverse..)
As for discord access, just leave this open for one of the MV team to look in to. I'm just a MV discord helper, that doesn't use multiverse.. lol


Rebindable menu + move menu to default f11

About the PR

Steam users have F12 bound to screenshot, so they would prefer F12 not be bound to anything
It's now possible to bind the menu key yourself via the UI (allows users to put it back on ESC if they want to)

Media

https://user-images.githubusercontent.com/22365940/230997367-e5e69ec3-37eb-429e-b3f6-8ae451aab549.mp4
(In the middle of the test video I forgot F6/F7 are already bound to things :P )

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl:

add: Ability to bind the menu toggle key directly in the UI
tweak: Default menu toggle moved from F12 to F10

F11 is bound to the game's builtin screenshot feature.

F11 is bound to the game's builtin screenshot feature.

Are you sure?

f11 is fullscreen bruh

f11 is fullscreen bruh

f11 doesn't trigger fullscreen for me?

on most linux wms

on most linux wms

I'm actually running on linux (Ubuntu KDE) and don't have this behavior.  A window manager binding to a common function key seems very weird (usually they'd require the meta/super key also be pressed).

my bad i just have that as my config and am so used to it

my bad i just have that as my config and am so used to it

All good, I moved it to f10 any way as people pointed out a lot of games have f11 as fullscreen.  We don't support that yet anyway, but one day we might so... f10!


seperate load/save function

Is there a facility to have separate save/load methods to serialize/de-serialize values similar to Cereal?

Use ‘if constexpr’ trying to see if there was an issue open about this and an example

Check https://github.com/eyalz800/zpp_bits/issues/68


Sort by size has odd behaviour when used on cat Indices

The sort by size doesn't seem to work on the "Cat APIs" -> Indices page.
The docs.count also doesn't seem to work properly.
Using the store.size column as an example:
Initial results

One Click:

Two Clicks:

Could it be sorting as if the column is text because it has a "." or "gb" in it? That wouldn't explain why the docs.count isn't working though as they are whole numbers too.
The pri and rep columns seem to work fine.
Let me know if you need any more info :)

+1

+1


fix(deps): update icr.io/ibm-iac/vuln-host-scanner docker tag to latest

This PR contains the following updates:

Package
Update
Change

icr.io/ibm-iac/vuln-host-scanner
patch
0.7.2 -> 0.7.4

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

:tada: This PR is included in version 1.0.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Agora node does not catch up after restart

Currently, an agora does not catch up after restart.
It should get the latest blocks and catch up with the blockchain.

It was observed that the restarted node tries to enroll, but gets rejected.
2021-01-20 10:37:01,233 Info [agora.consensus.state.ValidatorSet] - Rejected pre-image: validator not enrolled for key: 0x790ab7...

This might happen because the utxo_key of the restarted node is different from the the utxo_key in the genesis block enrollment. It somehow got modified.

It was observed that the restarted node tries to enroll, but gets rejected.
2021-01-20 10:37:01,233 Info [agora.consensus.state.ValidatorSet] - Rejected pre-image: validator not enrolled for key: 0x790ab7...

This might happen because the utxo_key of the restarted node is different from the the utxo_key in the genesis block enrollment. It somehow got modified.

It's expected, if the network is at Height 1999.

It's expected, if the network is at Height 1999.

Currently it is not up to 1999 yet, and the other nodes are able to re-enroll just fine. The restarted one is strange because it can't.

Currently it is not up to 1999 yet, and the other nodes are able to re-enroll just fine. The restarted one is strange because it can't.

Currently it is not up to 1999 yet, and the other nodes are able to re-enroll just fine. The restarted one is strange because it can't.

If the restarted node is not caught up to the network yet, that would explain it as well.

Currently it is not up to 1999 yet, and the other nodes are able to re-enroll just fine. The restarted one is strange because it can't.

If the restarted node is not caught up to the network yet, that would explain it as well.

If the restarted node has not caught up to the network yet, that would explain it as well. It would send bunch of invalid enrollment requests as it is discovering new blocks and at the start()

The node is not attempting to catch up to the network or discover.. That may be the problem.

If the restarted node has not caught up to the network yet, that would explain it as well. It would send bunch of invalid enrollment requests as it is discovering new blocks and at the start()

The node is not attempting to catch up to the network or discover.. That may be the problem.

Well, agora says that is failing to listen to the port 9110. But netstat says the opposite :)
agora:
Jan 20 12:23:27 na-001 docker[19876]: Failed to listen on <IP_ADDRESS>:9110

netstat:
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 <IP_ADDRESS>:34279        <IP_ADDRESS>:*               LISTEN      -
tcp        0      0 <IP_ADDRESS>:4826            <IP_ADDRESS>:*               LISTEN      1/agora
tcp        0      0 :::9110                 :::*                    LISTEN      1/agora

Well, agora says that is failing to listen to the port 9110. But netstat says the opposite :)
agora:
Jan 20 12:23:27 na-001 docker[19876]: Failed to listen on <IP_ADDRESS>:9110

netstat:
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 <IP_ADDRESS>:34279        <IP_ADDRESS>:*               LISTEN      -
tcp        0      0 <IP_ADDRESS>:4826            <IP_ADDRESS>:*               LISTEN      1/agora
tcp        0      0 :::9110                 :::*                    LISTEN      1/agora

I see this in agora service config in ansible:
SIGKILL only manually
TimeoutStopSec=infinity
SendSIGKILL=no
Restart=on-failure
User=agora
Group=nogroup
I know sometimes vibe.d have difficulties terminating and it keeps processes using it hanging... Are you sure the previous agora instances termintated?

I see this in agora service config in ansible:
SIGKILL only manually
TimeoutStopSec=infinity
SendSIGKILL=no
Restart=on-failure
User=agora
Group=nogroup
I know sometimes vibe.d have difficulties terminating and it keeps processes using it hanging... Are you sure the previous agora instances termintated?

Well, top only shows a single instance. But I am not sure if it's the newly created one.

Well, top only shows a single instance. But I am not sure if it's the newly created one.

Will be fully fixed once #1662 is merged.


Prefix Sum of Matrix

💥 Proposal
A CP algorithm of 2D matrix even used in placement questions, I want to add the algorithm in C++ and Python.
Do assign me this issue  so I can add more to NeoAlgo.
Yes I have you read the Contributing Guidelines on Pull Requests?

/assign

Respected Mentors, kindly assign me this issue in Java.

https://github.com/TesseractCoding/NeoAlgo/pull/6341#issue-620293235
Pull request Done

This issue has been assigned to @U-c0de!
It will become unassigned if it isn't closed within 21 days. A maintainer can also add the pinned label to prevent it from being unassigned.

#6341 Done

/assign


Cook to burn percentage ratio

Pretty self explanatory. Make a little window to show the % of food burned vs cooked.

Just count it. Make sure you have cooking plugin enabled.


cleanup: remove cilium <IP_ADDRESS> (for VHD space)

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
Remove unused cilium version
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 79.313%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2285

Relevant Lines:
2881

💛  - Coveralls


Support for easy datasource configuration by vendor.

Support to configure database by vendor, like:
(add-new-datasource-resource :mysql)
(add-new-datasource-resource :oracle)
(add-new-datasource-resource :sql)
(add-new-datasource-resource :...)
This case the TomEE-CLI automatically download the drive and put in TOMEE_HOME/lib and configure the resource.
The user doesn't need to pass jdbc-driver and jdbc-url, the TomEE-CLI should need to receive only the port (has a default value case the user doesn't pass), database-name, username and password.

I'd suggest to remove either "add" or "new". I think both is redundant.

Make sense. I'll remove new.
(add-datasource-resource [...])

Since it will download the driver, I will move the function (download-file) from installation.clj to utils.clj.

Thank you @htmfilho. I'll need this function. :D


site-package content get installed into build_env instead of host_env when cross-compiling

Original issue: https://github.com/mamba-org/boa/issues/158
Within the RoboStack project, we observed that cross-compiling (host: osx, target: osx-arm64) a recipe failed. We were able to pin down the issue to cross-python, in particular those lines in the activation script: https://github.com/conda-forge/cross-python-feedstock/blob/41083676420cef1f476a0bde41632cdf7334279b/recipe/activate-cross-python.sh#L33-L34
While the original issue in https://github.com/mamba-org/boa/issues/158 was observed when using boa and osx cross-compile, I was since able to replicate the same problem with conda build and linux->linux-aarch64 cross-compilation.
Basically, the site-packages directory in the host_env ends up being empty, and its contents are instead copied into the build_env. However, in the case of vtk, the cmake script refers to a library in $HOST/lib/python3.8/site-packages:
CMake Error at /home/tobias/anaconda3/conda-bld/pcl_1621892989199/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho/lib/cmake/vtk-9.0/VTKPython-targets.cmake:395 (message):
  The imported target "VTK::vtkCommonCorePython" references the file

     "/home/tobias/anaconda3/conda-bld/pcl_1621892989199/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho/lib/python3.7/site-packages/vtkmodules/vtkCommonCore.so"

  but this file does not exist.  Possible reasons include:

  * The file was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and contained

     "/home/tobias/anaconda3/conda-bld/pcl_1621892989199/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho/lib/cmake/vtk-9.0/VTKPython-targets.cmake"

  but not all the files it references.

Call Stack (most recent call first):
  /home/tobias/anaconda3/conda-bld/pcl_1621892989199/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho/lib/cmake/vtk-9.0/vtk-config.cmake:147 (include)
  cmake/pcl_find_vtk.cmake:25 (find_package)
  CMakeLists.txt:377 (include)

vtk does not show up with conda list after activating the host_env, but it does show up in the build_env (however note that channel is pypi rather than conda):
# packages in environment at /Users/tobias/opt/anaconda3/conda-bld/ros_1621565257168/_build_env:
...
vtk                       9.0.1                    pypi_0    pypi
...

@wolfv's comment in the original issue:

I think these lines from the cross-python activation script might be relevant:
https://github.com/conda-forge/cross-python-feedstock/blob/41083676420cef1f476a0bde41632cdf7334279b/recipe/activate-cross-python.sh#L33-L34
Maybe @isuruf has an idea (sorry to bother you!). I think for us the problem is that we need to link to the shared libs in site-packages.
However we don't try to execute these python executables so there won't be any issues with executing the wrong arch... maybe we could improve this activation script in a way to not remove some dylib or so files depending on some configured env var ...
@Tobias-Fischer we should probably move this issue to the cross-python feedstock

It's not quite clear to me why the .so / .dylib files have to be removed from the host env (since they are properly compiled for the host arch etc.).
Maybe one way to fix this on our side would be to replace all $PREFIX/lib/python3.x/site-packages references in the CMake files with $BUILD_PREFIX/lib/python....
Or we could have an env var that we can set to prevent this activation script from removing the vtk .so files?

It's not quite clear to me why the .so / .dylib files have to be removed from the host env (since they are properly compiled for the host arch etc.).

Because python will try to load from $PREFIX first and that would fail. If we let python to load from $BUILD_PREFIX, then some paths might be wrong.
For eg: if we let python load numpy from ${PREFIX}, it will fail and if we let python load numpy from ${BUILD_PREFIX}, then the blas paths will be for the BUILD_PREFIX and building scipy would fail.
Solution was to use files from $PREFIX except for the python extensions which comes from BUILD_PREFIX.
If we had used PREFIX/lib/pythonx.y/site-packages to be the place to have this, then PREFIX might get new files from BUILD_PREFIX and get packaged. Safest option was to do this in BUILD_PREFIX.

@wolfv:
So I was able to cross-build PCL (linux -> linux-aarch64; conda-build) by adding this to the build.sh:
PYTHON_VERSION_WITH_DOT="${CONDA_PY:0:1}.${CONDA_PY:1}"
find $PREFIX/lib/cmake -type f -exec sed -i "s~\${_IMPORT_PREFIX}/lib/python$PYTHON_VERSION_WITH_DOT/site-packages~$BUILD_PREFIX/lib/python$PYTHON_VERSION_WITH_DOT/site-packages~g" {} +

However, the pcl-conversions recipe (osx -> osx-arm64; boa) still fails:
if [[ "$CONDA_BUILD_CROSS_COMPILATION" == "1" ]]; then
  find $PREFIX/lib/cmake -type f -exec sed -i "s~\${_IMPORT_PREFIX}/lib/python$ROS_PYTHON_VERSION/site-packages~$BUILD_PREFIX/lib/python$ROS_PYTHON_VERSION/site-packages~g" {} +
fi

In this pcl-conversions case, the so files don't get copied into the build_env, whereas in the pcl case they do. Any ideas?

Hi @wolfv @isuruf - do you have any more ideas re this issue?

I'm also having issues with cross-compiling from linux-64 -> linux-aarch64 due to the deletion of the files from $PREFIX/lib/python/site-packages; which causes a later running of the setup.py script to fail due to setuptools being missing (among other things). What is the suggested remedy for this?

@matthewwardrop, which feedstock?

@isuruf Apologies, I should have provided a bit more context. The package in question is an internal proprietary package, but will be open sourced in the fullness of time. I was attempting to use this package to build internal conda packages for distribution internally until we are ready to open source things.
Assuming that this is a supported use-case, please see below for more details.
Our build looks like:
meta.yaml
{% set data = load_setup_py_data() %}
{% set base_name = "my_package" %}
{% set version = data['version'] | replace('-rc.', 'rc') %}

package:
  name: "{{ name }}"
  version: "{{ version }}"

about:
  home: internal_url
  license: PROPRIETARY
  license_family: PROPRIETARY
  summary: |
    ...

source:
  path: ..

outputs:
  - name: "{{ base_name }}"
    version: "{{ version | replace('-rc.', 'rc') }}"
    requirements:
      build:
        - {{ compiler('cxx') }}
        - python {{ python }}.*                  # [build_platform != target_platform]
        - cross-python_{{ target_platform }}     # [build_platform != target_platform]
        - pybind11 >=2.6                         # [build_platform != target_platform]
        - pybind11-abi                           # [build_platform != target_platform]
      host:
        - python {{ python }}.*
        - pip
        - setupmeta >=2.7.12

        # Required for arrow pointer tool compilation
        - pybind11 >=2.6
        - arrow-cpp {{ arrow }}.*
        - pyarrow {{ arrow }}.*
      run:
        - docstring_parser >=0.6
        - interface_meta
        - numpy
        - pandas >=1.2.0,!=1.3.0  # Indexing regression in 1.3.0 is fixed in 1.3.1
        - pyarrow {{ arrow }}.*
        - python {{ python }}.*
        - rpy2 >=3.4.0,<3.5
        - scipy
        - spec-classes >=1.1.0
        - statsmodels
        - sympy
        - tzlocal
    build:
      number: 0
      script: python -m pip install --no-deps --ignore-installed -vv .

conda_build_config
python:
  - 3.9
arrow:
  - 3.0.0
numpy:
  - 1.18
_openmp_mutex:
  - 4.5=0_gnu
pin_run_as_build:
  arrow_cpp: x.x
  pyarrow: x.x
  _openmp_mutex: x.x.x.x
ignore_version:
  - numpy
target_platform:
  # - linux-64   # [linux]
  - linux-aarch64  # [linux]
  # - osx-64     # [osx]
  # - osx-arm64  # [osx]

The build itself succeeds with this configuration on Linux-64 for aarch64, but then bails out in a later step due to the site-packages directory having removed setuptools (which I now note is needed to properly parse the meta.yaml due to _load_setup_py_data). I will do some testing tomorrow to see if hard-coding the version fixes things, though it is nice not to have to do that.

Can't help you further without a reproducer. Sorry.

I've also just hit this issue. I'm working with a dependency that includes header files, and the location of the header files is in the site-packages/ folder, and there is a separately installed "environment" file that lists the header locations.
Because the site-packages folder has been moved to the build environment: https://github.com/conda-forge/cross-python-feedstock/blob/b01685b23ab70ab6d445d80336d709df130f3616/recipe/activate-cross-python.sh#L57-L59
the build failed. To solve this, I've just added a special case into my build.sh:
if [[ $CONDA_TOOLCHAIN_BUILD != $CONDA_TOOLCHAIN_HOST ]]; then
    CFLAGS="-isystem $BUILD_PREFIX/lib/python$PY_VER/site-packages $CXXFLAGS"
    CXXFLAGS="-isystem $BUILD_PREFIX/lib/python$PY_VER/site-packages $CXXFLAGS"
fi

I'm mainly just documenting this - not really asking for a solution; while it'd be ideal if I didn't have to do anything special in the build.sh script for cross-compiling, realistically it's always going to be a special case; it just took me a while to work out what the cross- build was doing and why.


Update syntax highlighting to better support terraform 0.12

For #157 (but doesn't close it)
I have had a go at improving the syntax highlighting for Terraform 0.12 and beyond. I probably haven't fixed every case, but this should make it better especially for type definitions, expressions and function calls.
NOTE: this will not fix the erroneous syntax errors, but it will at least make the coloring better.
Also NOTE: this is my first time ever contributing to the project or any open source project, so please review closely, and let me know if I have done anything wrong.

The build failed. But as far as I can see all builds have been failing for a while. Doesn't seem to be anything to do with my commit.

The builds are failing for another reason, nothing to do with your commit. Will have a look tonight or tomorrow.
Sent from my iPhone

On 1 Jun 2019, at 14:34, Matt Fenner<EMAIL_ADDRESS>wrote:
The build failed. But as far as I can see all builds have been failing for a while. Doesn't seem to be anything to do with my commit.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hope to see this get merged in soon. It hurts so bad 😭

Thanks for your contribution and thanks for your patience

@mauve can you possibly do an incremental release with the new changes so we can try it out, or maybe put a build out on github that we can grab and install manually?

Can we please cut a release on this?  Happy to pay a $25 USD bounty to make it happen

released as part of 1.3.12


Adding additional icon packs to about.md

Is there a simple way/guide on how to do so? Or are these icon packs stored somewhere in the theme?
In particular I would love to see a "Stackexchange" icon :)
  # Social/Academic Networking
  #
  # Icon pack "fa" includes the following social network icons:
  #
  #   twitter, weibo, linkedin, github, facebook, pinterest, google-plus,
  #   youtube, instagram, soundcloud
  #
  #   For email icon, use "fa" icon pack, "envelope" icon, and
  #<EMAIL_ADDRESS>as the link.
  #
  #   Full list: https://fortawesome.github.io/Font-Awesome/icons/
  #
  # Icon pack "ai" includes the following academic network icons:
  #
  #   google-scholar, arxiv, orcid, researchgate, mendeley
  #
  #   Full list: https://jpswalsh.github.io/academicons/

Visit the link you already posted, use the search bar and find your icon, e.g., "stack-exchange" for the "fa" icon pack...

Thanks, worked.
Tried it before the same way but must have had something wrong in my setup.
Sorry for that trivial issue!


Removed sd_a- particle size parameters: mean, standard deviation

Description
Problem:
Particle size parameters like mean/standard deviation are defined but not used, potentially leading to a situation where the user changes it but it will have no effect
Considerations:
-There isn't one mean standard deviation parameter in size_distribution_parameter.py but sd_p and sd_n for the area-weighted standard deviation of positive and negative electrodes respectively.
-sd_p and sd_n cannot be directly removed as they are used in the calculations of R_min and R_max which like you said determine the geometry. We can remove to parameter by assigning the default value of 0.3 in the calculations.
Solution:
Removed sd_a parameter (area-weighted particle-size standard deviation) from the codebase.
Fixes #3219
Type of change

[X] Bug fix (non-breaking change which fixes an issue)

Key checklist:

[X] No style issues: $ pre-commit run (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)
[X] All tests pass: $ python run-tests.py --all
[X] The documentation builds: $ python run-tests.py --doctest

You can run unit and doctests together at once, using $ python run-tests.py --quick.

I think the docs build failed because I used a special character in the pull request head to highlight that sd_a is a parameter. The local docs build test had passed.

The linkChecker has failed because of a timeout from loading/checking one website.

I think I also have to remove the tests that search for the removed parameter to fix the build checks.
@tinosulzer Kindly confirm

Yes, you need to replace them with a test for a different parameter that should be added by size_distribution_parameters (e.g. the minimum particle radius)

Unsuccessful checks:

linkChecker: Timeout with the link https://www.rse.ox.ac.uk/ in README.md
benchmarks on PR: Originates from a previously merged PR
nox test in Ubuntu 3.10: This PR does not update the requirements of nox or PyBaMM. If the nox tests were recently updated we have to update the hashes also.


DEB package missing user/group creation script

The DEB package for indexer-2.0 is missing a post-install script that creates the algorand user and group, as well as the home directory.  If you install it on a node that's all ready got the algorand package installed, that's all ready handled.  But if you install the indexer on its own, the default systemd init scripts won't work.  They assume a user "algorand" and group "algorand".
The following command creates the user correctly (at least on Ubuntu):
useradd -r -m -d "/var/lib/algorand" algorand

@brianolson do you have any thoughts on this issue? We were just talking about it in grooming today.

Since we don't auto-start the daemon but leave some configuration required I feel it would be inappropriate to do it automatically. Maybe this could be addressed by documentation with a few commands to copy-and-paste to achieve a simple setup?

It's a nice to have to auto-configure, and detect if these are already installed (i.e., have already installed the algorand package, and vice versa). The configuration requirement is an interesting consideration, though.
Maybe we should add to documentation as Brian suggests for now, since you can't just install-and-run yet?

I've found that the preinst maintainer script needs to be updated to not flag the algorand-indexer package.  This will need to be done in conjunction with this ticket.


Issue with /docs/user-guide/replication-controller/

This is a...

[ ] Feature Request
[x] Bug Report

Problem:
The page https://kubernetes.io/docs/user-guide/replication-controller/ states that readiness has not been implemented.
However according to https://github.com/kubernetes/kubernetes/issues/620, readiness has been implemented since 2015. So our k8s (1.4.7 & 1.5.2) support it.
Proposed Solution:
fix the page!
Page to Update:
http://kubernetes.io/...

This looks like a valid issue report. I am not sure which component is responsible for health/readiness checks (kubelet?) or how these relate to ReplicationController. @stephanwesten please feel free to send a patch if you know the answer. Otherwise, I can contribute one if somebody answers.

@stephanwesten Thanks for opening this issue.
@ahmetb Any updates here?

Looks like someone needs to send a patch fixing out of date statement.


Tab index issue with aria-hidden vs. hidden

I see you recently changed the hidden attribute to aria-hidden. Would it be possible to render both attributes? I'm using your component in dynamic forms and it messes up the tab index. hidden will instruct the browser to not include the input when tabbing through the form, aria-hidden won't.

Hey! We only used hidden very briefly, it quickly became clear that it messed up some edge cases if the closed element should still be partially visible. It also required additional fine tuning so the Attribute was only added after the animation ran.
If you absolutely need it, you could add it yourself. This basically works:
<vue-slide-up-down :active="active" :hidden="!active">
  <input placeholder="Only tabbable if active!" />
</vue-slide-up-down>

Alternatively, if you don't want to have to fix the animation, you could
<vue-slide-up-down :active="active">
  <input placeholder="Only tabbable if active!" :tabindex="active ? 0 : -1" />
</vue-slide-up-down>

That makes a lot of sense. Thanks for the detailed response and the great work!

No problem!

Rather than create a new issue, thought I'd query this issue. I encountered the same issue as @fThues with the use of form fields and tab index.
It does go further than just visible tabbing, but also users who rely on assistive devices (such as screen readers) would use their standard keyboard navigation techniques, which encounters the same issue - while tabbing for visual users is odd, tabbing for screen reader users is totally confusing.
I do feel there is valid argument for including "hidden", and while I appreciate the workaround, on a larger scale project I'm on at the moment, does make for quite a lot of additional logic needing to be added.
I've rolled back a version to the one that uses "hidden" (as I haven't encountered any of the edge case issues that mentioned, so works for me) and tweaked to also use aria-hidden, but just wondering @danieldiekmeier can provide any more details on those edge cases where issues were occurring? It may still be worth exploring this one to create a more accessible result.

@martyf Sure!
The edge cases are

hidden will immediately hide the whole element, so you won't see the whole animation
hidden will always hide the whole element, even if the content should be still partially visible in the active === false state (if you set min-height to something larger than 0)

I also feel the general need of adding hidden, but I'm not an expert for accessibility in any way, so I'd like to rely on external contributors, if anybody wants to find a way that does not break backwards compatibility.
Also, I haven't needed this component since 2017, so I'm not really eager to sink time into this.
If the rolled back version works for you, that's great! You could also copy the component into your code base (it's really just one file with a few lines) and make any changes for your specific use case!
Also, you could write a wrapper so you could simplify your code:
<template>
  <vue-slide-up-down :active="active" :hidden="!active">
    <slot/>
  </vue-slide-up-down>
</template>

<script>
export default {
  name: 'MySlideUpDown',

  props: {
    active: Boolean
  }
}
</script>

Excellent that's great thank you @danieldiekmeier - I totally get where you're coming from for your needs too. I will have a play with the latest version and see if I can iron out those kinks to find the best solution for everyone. Just on deadline at the moment, but will do after that, as I find this component absolutely invaluable.

I've made a branch that fixes the first issue above @danieldiekmeier, so any fields/controls within the hidden area are not accessible when it is "closed", but also has complete animations too.
The second one is more challenging though. Basically visible elements can always be access via the keyboard except if the specific element has a tabindex of -1. This means that when it is not active, every child element of the inner content needs to have tabindex of -1 applied - but also means that we need to be able to undo it too - so starts to get really complicated.
For me, I question its usefulness - if I want an element hidden, I want it hidden, not partially visible (i.e. with min height). So feel that having it partially visible does fall in to a specific use case.
Maybe the balance of the two is adding a new flag that allows the developer to disable the "hidden" attribute - with the impact of keyboard focus of internal content. It could (would) still cause accessibility issues for keyboard users, but given the element itself is visible anyway, I think falls in to a different category.
Happy to do a PR with that if you'd like - the first edge case is fixed regardless. It's the tabindex issue that stops the second from really getting bulletproof fixed.

@martyf Thanks! I've been thinking about it and I think I agree with you. The most important use case is completely hiding the element (and then adding a hidden attribute), and the partial hiding can be an opt-in thing. I'd probably add a section to the docs about that and bump the major version.
Can you prepare a PR?

Cool bananas - will polish up today and get it back to you.

PR made... evolved the demo a bit to show off the different props too... wasn't in the scope, I know, but is useful to see things change in realtime. Hopefully you agree too 😇

@martyf Thanks for all the work on this! I just published v2.0.0 with all your good good changes!

No dramas at all - thanks for the foundation work - I use it all the time in a backend UI so happy to keep contributing where needed as I’m still actively using it.


fix(kallsyms): Correct text address value

Renamed /misc/kallsyms to /misc/ebbrt.kallsyms
Fixed cmdline flag: nodns -> nodhcp

@BetsyRT r+

@BetsyRT r+

:pushpin: Commit 7bbcdeb has been approved by jmcadden

:hourglass: Testing commit 7bbcdeb with merge ba56eb3...

:sunny: Test successful - runtests
Approved by: jmcadden
Pushing ba56eb372d31926e6b69156d9213002a17f7af15 to master...


Expose profile_changed signal to XRController3D

Exposes the XRPositionalTracker profile_changed signal to users through XRController3D, just like other XRPositionalTracker signals like button_pressed, input_float_changed, etc.
Because the interaction profile changes as users swap between using controllers and hand tracking, making this signal available to users provides an easy way for them to detect that change. This was discussed a bit in https://github.com/GodotVR/godot_openxr_vendors/pull/98

Thanks!


Problem with caching latents

Describe the bug
The caching of latents frequently stops, for me, at about 1,272 latents. At the same time, latent caching behavior is completely erratic. During one training yesterday, caching was so slow that it estimated 4 hours for 1,400 images (usually takes about 7 minutes).
When caching latents stalls the training, no error messages are produced. You simply return to Colab to find that it stopped, and never reached the end of the caching.
Reproduction
Try it yourself a few times - obviously this is independent of any user-specific settings or hardware. Apart from the instance data, the data being used (the reg images) and the settings are the same defaults that I have been using since early January.
Logs
No response
System Info
Irrelevant, relates to default Colab settings in the main Shivam Dreambooth Colab.

On an A100, it is running. It is possible that the needs of upstream dependencies and other factors are now so much greater than late 2022 that it is no longer possible to run the script reliably on a T4. This increases cost 5-6x for paid users, and is beyond the reach of free users.

I always train on the A100 so I don't have to use 8it-adam or gradient checkpointing, cost is CAD $16 with taxes for 100 units. The A100 uses about 13.08 an hour. I switch to standard GPU for inference.
You don't have to cache the latents, the huggingface train_dreamooth.py doesn't have that option. In this fork you can disable it by adding --not_cache_latents

You don't have to cache the latents, the huggingface train_dreamooth.py doesn't have that option. In this fork you can disable it by adding --not_cache_latents.

What are the consequences of not caching the latents? If they're unnecessary, why are they still in the Colab?

Well the reason to cache images

You don't have to cache the latents, the huggingface train_dreamooth.py doesn't have that option. In this fork you can disable it by adding --not_cache_latents.

What are the consequences of not caching the latents? If they're unnecessary, why are they still in the Colab?

It is still going to learn the latents, but caching might make for a slight speed improvement and/or to secure them better than not caching, like if your image folders got deleted by mistake during training, your session might survive if your images are stored in cache memory. I wouldn't expect a big difference., not caching might actually work better. If you are having trouble caching the latents it could be worth to try without, and set your save intervals at a low number so you can monitor the results for yourself and reach your own conclusion.


Change the way features are registered

When adding a new feature:

src/options.js file no longer needs to be modified
feature's name, id, description and category are now defined in the feature source file, i.e. together with the feature
feature code no longer has to call chrome.storage.sync

This PR is a suggestion with changes to familyTimeline and printerFriendly as examples. If everyone is OK with this change, I'll update other features and the documentation.

Sorry Przemek, I accidentally merged this one instead of the "latest" GitHub pull but haven't looked at it yet.
I think you might have to make another pull request.

I created a new PR with these changes: #69


Remove GOPROXY in docker-compose files

Description
Our docker-compose files were setting the GOPROXY environment variable to point to https://gocenter.io rather than relying on the Go 1.13 default.  Using a non-default GOPROXY sometimes failed with a 404.  Unless there's a good reason to use the non-default proxy, we should remove the explicit setting of it.
Setup
make server_test_docker

@reggieriser I am still getting failures when I run this locally.

@reggieriser I am still getting failures when I run this locally.

Strange.  Were you running make server_test_docker or make server_test_standalone? The latter should work too, but you'll need to first make sure your test DB is reset (or just run make server_test instead which resets the test database then runs server_test_standalone).
If either of those are still failing, let me know what errors you're seeing and I'll investigate further.


InvalidSignatureError

Rasa version:Rasa 1.5.1
Rasa X version (if used & relevant):I dont know
Python version:Python 3.6
Operating system (windows, osx, ...):Ubuntu 16.04
Issue:
rasa init --ok
rasa shell --ok
rasa x --failed
Error (including full traceback):
scrooge@scrooge-X455LD:~/RASA$ rasa x
Traceback (most recent call last):
  File "/usr/local/bin/rasa", line 8, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.6/dist-packages/rasa/__main__.py", line 76, in main
    cmdline_arguments.func(cmdline_arguments)
  File "/usr/local/lib/python3.6/dist-packages/rasa/cli/x.py", line 291, in rasa_x
    run_locally(args)
  File "/usr/local/lib/python3.6/dist-packages/rasa/cli/x.py", line 379, in run_locally
    from rasax.community import local  # pytype: disable=import-error
  File "/usr/local/lib/python3.6/dist-packages/rasax/community/local.py", line 13, in <module>
    import rasax.community.jwt
  File "/usr/local/lib/python3.6/dist-packages/rasax/community/jwt.py", line 5, in <module>
    from jwt import InvalidSignatureError
ImportError: cannot import name 'InvalidSignatureError'

Command or request that led to error:
cd
mkdir RASA
rasa init --no-prompt
rasa shell
/stop
rasa x

Content of configuration file (config.yml) (if relevant):
# Configuration for Rasa NLU.
# https://rasa.com/docs/rasa/nlu/components/
language: en
pipeline: supervised_embeddings

# Configuration for Rasa Core.
# https://rasa.com/docs/rasa/core/policies/
policies:
  - name: MemoizationPolicy
  - name: KerasPolicy
  - name: MappingPolicy

Content of domain file (domain.yml) (if relevant):
intents:
  - greet
  - goodbye
  - affirm
  - deny
  - mood_great
  - mood_unhappy
  - bot_challenge

actions:
- utter_greet
- utter_cheer_up
- utter_did_that_help
- utter_happy
- utter_goodbye
- utter_iamabot

templates:
  utter_greet:
  - text: "Hey! How are you?"

  utter_cheer_up:
  - text: "Here is something to cheer you up:"
    image: "https://i.imgur.com/nGF1K8f.jpg"

  utter_did_that_help:
  - text: "Did that help you?"

  utter_happy:
  - text: "Great, carry on!"

  utter_goodbye:
  - text: "Bye"

  utter_iamabot:
  - text: "I am a bot, powered by Rasa."

Thanks for the issue, @rgstephens will get back to you about it soon!
You may find help in the docs and the forum, too 🤗

i have same problem. is this solved?

i have same problem. is this solved?

Nope


Investigate how to support Service Principal

As an engineer, I would like to investigate whether Benchpress should support checks against service principals and role assignments
More context: I believe service principals cannot be created through bicep, so should Benchpress be responsible for testing against service principals?

[x] Investigation documented
[x] Any subsequent tasks are created

@msha1026  - can you share the results of your investigation?


Bump prismatic/plumbing to fix cljs compilation issues

Originating from this: https://github.com/plumatic/schema/issues/392
New version of plumbing: https://github.com/plumatic/plumbing/pull/133

pushed 0.6.11-SNAPSHOT


Add Task.getinstance(), Task.instantiate(), and getinstances() methods.

Description
Automatic instantiation for dependent tasks via self.getinstance() instead of self.input().
Motivation and Context

When tasks are reused many times, I need to write same instantiation codes in Task.run().
For example, if a task MyTask whose output is a csv is reused many times, I need to write same instantiation codes in its child tasks as:
class ChildTask1(luigi.Task):
    def requires(self):
        return MyTask()
    def output(self):
        pass
    def run(self):
        ### this instantiation is redundant
        with self.input().open('r') as infile:
            reader = csv.reader(infile)
            indata = [row for row in reader]
        # do stuff

class ChildTask2(luigi.Task):
    def requires(self):
        return MyTask()
    def output(self):
        pass
    def run(self):
        ### this instantiation is redundant
        with self.input().open('r') as infile:
            reader = csv.reader(infile)
            indata = [row for row in reader]
        # do another stuff

Instead above, I want to write it like:
class MyTask(luigi.Task):
    def requires(self):
        ...
    def instantiate(self):
        with self.output().open() as outfile:
            reader = csv.reader(outfile)
            outdata = [row for row in reader]
        return outdata

class ChildTask3(luigi.Task):
    def requires(self):
        return MyTask()
    def output(self):
        pass
    def run(self):
        ### automatic instantiation
        indata = self.getinstance()  # get an instance of self.input instead of file pointer
        # do stuff

Have you tested this? If so, how?

I ran my jobs with this code and it works for me.

Because my coding skill (and English) is poor, this pull request should be rejected.
I just want to show my idea and hear some opinions about it.

[Current coverage][cc-pull] is 76.02%

Merging [#1704][cc-pull] into [master][cc-base-branch] will decrease coverage by 2.79%

@@             master      #1704   diff @@
==========================================
  Files            94         94
  Lines         10292      10309    +17
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           8111       7837   -274
- Misses         2181       2472   +291
  Partials          0          0

Powered by Codecov. Last updated by [b274d16...724f19b][cc-compare]
[cc-base-branch]: https://codecov.io/gh/spotify/luigi/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/spotify/luigi/compare/b274d16460937f5061f995f49c2e6b79d491464e...724f19b242a573a657fb7c908b7fdc4a24a6e0af
[cc-pull]: https://codecov.io/gh/spotify/luigi/pull/1704?src=pr

why can't this be solved using normal inheritance?

@erikbern OK here is another implementation for my idea. How about this?
def getinstances(struct):
    if isinstance(struct, luigi.Task):
        return struct.instantiate()
    elif isinstance(struct, dict):
        return {k: getinstances(v) for k, v in six.iteritems(struct)}
    else:
        # Remaining case: assume r is iterable...
        try:
            s = list(struct)
        except TypeError:
            raise Exception('Cannot map %s to Task/dict/list' % str(struct))
    return [getinstances(r) for r in s]

class MyParentTask(luigi.Task):
    def requires(self):...
    def output(self):...
    def run(self):...
    def instantiate(self):
        with self.output().open() as outfile:
            reader = csv.reader(outfile)
            outdata = [row for row in reader]
        return outdata

class MyChildTask(luigi.Task):
    def requires(self):
        return MyParentTask()
    def output(self):...
    def run(self):
        indata = getinstances(self.requires())
        ...

Does the method getinstances() have any chance to be merged into the source?

i don't get why MyChildTask can't just inherit from MyParentTask?

@erikbern Sorry I could not understand why MyChildTask can inherit from MyParentTask...
In my understanding, the class inheritance is different from luigi's Task dependency system.
My motivation is: In every MyChildTask which requires MyParentTask, I need to write the same code to map MyParentTask's output (like csv file) to Python's object (like list of lists), because MyChildTask.input() just returns targets. If MyParentTask has a method for instantiating its own output for its children tasks, children tasks need not to consider how to map input file to object, because its parent task do it.

yeah but why can't you put that stuff on a parent class and use inheritance to duplicate the functionality?

I got it. I can implement my motivation as below. I'm sorry to trouble you.
class DependentTask(luigi.Task):
     def requires(self):...
     def output(self):...
     def run(self):...
     def instantiate(self):
          with self.output().open() as outfile:
              reader = csv.reader(outfile)
              outdata = [row for row in reader]
          return outdata

class MyTask(luigi.Task):
    def requires(self):
        return DependentTask()
    def output(self):...
    def run(self):
        indata = self.requires().instantiate()  # instead of self.input().open()
        ...

Thanks for your pull request @keisuke-nakata. :)


[fix lint warnings: NFTs pallet] fix clippy::missing_docs_in_private_items warnings

This PR fixes the 66 warnings emitted by running cargo clippy -- -A clippy::all -W clippy::missing_docs_in_private_items --no-deps in the NFTs pallet crate. It adds the missing docs for the pallet's helper functions and associated modules.
This is part of an ongoing effort from the https://github.com/orgs/paritytech/teams/devrel team to improve developer experience.

bot rebase

bot fmt


Remove AppInsights from Error Stack

Remove Zone artifacts from Error stack shown in console
Modify error pointer shown in console to inform user that the error was rethrown and originated elsewhere

@OsvaldoRosado Do we want to drop this PR if considering zone --> cls?

@markwolff I think this will be useful in the meantime before that change happens, especially since it's a fairly trivial change with a lot of positive impact.

@GuyHarwood just published 1.0.8


[DO NOT MERGE] Test set dev dep deps with target main branch

Test for this PR: https://github.com/QEDjl-project/QED.jl/pull/41

The PR was merged


Automatically publish tagged master commits to npm

This is the first step to adding versionbot to the SDK. With this, any time we tag a change, travis will publish it to npm. That should mean once we add versionbot, versionbot merges will automatically publish the new version to npm. Neat! This uses the resin.io credentials, but with the standard travis encryption setup to keep them hidden.
This does mean we don't have to sit and wait for the publish tests to run for us locally, but I suspect it also means we'll have to deal with instability on deploy occasionally from #252. That needs solving independently anyway (although I still don't have a useful answer).
Some reformatting here because I set this up with the travis cli tool, and it doesn't like our yaml formatting, I'm inclined to stick with its decisions there.
This might be of interest to @hedss, since this is our solution to https://github.com/resin-io-modules/resin-procbots/issues/30.

I suspect it also means we'll have to deal with instability on deploy occasionally

Yup, one of the Travis tests on this PR has failed already ;-)
Pinging @jviotti too, as he recently added automated publishing of Etcher snapshot builds to S3 from Travis and Appveyor. (but in that case he just used secure env-vars on the CI services, rather than adding encrypted variables to the YAML files)

@lurch Eugh, good point, rerun.
The actual deploy later on should be a fair bit more reliable than normal builds, because the deploy step will be a single test run, rather than four. No need to deploy separately for Node 4 or 6 or appveyor :-). And if it's the case that's the normal test runs are somehow interfering, it should be totally reliable, which would be nice. Fingers crossed.


Support for wildcard paths in externals option

Many a times we want to include multiple external artefacts like images, videos. Adding them each one by path is tedious and error-prone. Supporting single level wildcard will help maintainability of the code.

@abhijit-paul  how exactly wildcard in externals should work? To pre-cache assets it needs to know their URLs and with wildcard it of course doesn't know them.

Closing because of a lack of response. If you have some valid points about this feature then I'll open this again. Thank you.

I'm running a Dex website where I have all images from another CDN's url /images/ and these images are being added routinely. Having the wild card would make this much easier. Also, the actual sw.js does wildcards I believe


tarball cleanup

Currently, the workflow will only download a new tarball while leaving the old one in place. It would be ideal for the workflow to clean up after itself and remove unused dependencies.

Is there a reason this doesn't do helm dependency update, which does the cleanup?

@andy-v-h there is no reason; at the time I couldn't get it properly working with that command... But I also didn't try too hard. Feel free to submit a PR.


Fix for #4733: Profile image for anonymous user is not displayed.

Summary
Added an additional check before calling IsPicVisibleToCurrentUser(userId)
For anonymous user, userId is invalid i.e. less than or equal to zero. For invalid user, IsPicVisibleToCurrentUser() returns false and 403 code is sent to UI.
The additional check of isAnonymousUser, avoids the call to IsPicVisibleToCurrentUser() and image is returned for the anonymous user.
Fixes #4733

@dnnsoftware/approvers We will review this one today, but I believe that the initial behavior was by-design.


Boilerplate

This is the code for the web server. Basic front and back end are there to start the gui for the control systems and it has the routes todo the logic communication to the controller boards.

The notion has a timeline of what work has been done. The person, description, and time are listed just so editors can recall who worked on what at what time. It is just a paper trail.

@Vertycoxe I am going to merge the pull request.

Thanks


feat: Generic Webhook

Overview

Makes the webhook generic.
Adds OpenBao support to the webhook.
Updates nix.

Lets just make sure that old annotations are not deleted to allow users to revert to previous webhook if needed for any reason. Other than that, lgtm!

Lets just make sure that old annotations are not deleted to allow users to revert to previous webhook if needed for any reason.


Used "patterns" inside "other_variables"

"patterns" does not work when "match" is present
currently it doesn't do anything and can be removed

https://github.com/worlpaker/go-syntax/blob/02bd7c945da893fdc9ec87db82eca176d4ff3432/syntaxes/go.tmLanguage.json#L2761-L2772
also the brackets in "match" can be removed \\w+

Thanks. Your details made it easy for me to review.


[Bug]: ArrayIndexOutofBound when ValueCreator.createObjectValue is used

Description
Consider the following class.
public isolated class RequestContext {
    private final string? authString;

    public function init(string? authString = ()) {
        self.authString = authString;
    }
}

When we create an object in the runtime using ValueCreator.createObjectValue(module, "RequestContext"), this throws an exception. When null is passed, ValueCreator.createObjectValue(module, "RequestContext", null) it throws a NullPointer.
Steps to Reproduce
No response
Affected Version(s)
No response
OS, DB, other environment details and versions
No response
Related area
-> Runtime
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

Since createObjectValue(Module packageId, String objectTypeName, Object... fieldValues) API accepts Object[] as the third argument, when we pass null, it gives a NPE. For the time being, we can pass new Object[1] as the third argument if we want to pass null there, to make it work. This will be fixed correctly either to give an error message or accept null.
ArrayIndexOutofBound exception is given due to not handling the default values properly. That will also be fixed.


Hook Problems When Importing Data

I'm trying to create an association where it does not exist before rails_admin_import gem is going to import a record.
It's not creating the association.
def before_import_save(record)
    if Collection.where(title: record[:product_collection]).empty?
      collection = Collection.create!(title: record[:product_collection], site: site)
    end
  end

An image of the error when I upload a file:

What could be happening here?

Can you attach the file?  What else does it say in your rails_admin_import.log?  Did you turn on config.logging = true?

I added a new before_import_associations(record) hook that should help in situations like these


[FEATURE REQUEST] - Occupation

Describe the feature
Please add OCCUPATION field to the Citizen info so someone can type in what they do for work.
Additional Context
No response

Wouldn't this defeat the purpose of having businesses in the CAD 😅? Citizens can already join and create citizens, this field should also show up on name search, etc

Wouldn't this defeat the purpose of having businesses in the CAD 😅? Citizens can already join and create citizens, this field should also show up on name search, etc

Not at all because not every business is official. In our server we only have a select few businesses that we know are serious active RPers with a roster of citizens that could be in it.
But for everyone else they like to just put a few things about what they do for their back story as a personality. Some extra info for LEO to find out about them etc.


Update claims from external provider

When the service processes an external identity, the claims are not updated.
Lets say we use ADFS WS-Federation as external identity provider and an existing user logs in for the second time but with updated claims (because the user account in Active Directory was updated), then it is desired that the claims in the database are also updated.
Furthermore, UpdateAccountFromExternalClaimsAsync is only called in case of a new external identity and not in case of a returning external identity.
If you don't mind I would prefer to create a PR for this rather then running our own implementation. What do you think?

Sure, but there's already the ProcessExistingExternalAccountAsync you can override.

Yeah we can override things and implement it, but I think this is basic functionality others might also benefit from.

Sure, send a PR then.

Any update?

Was on my backlog and has now been added to my sprint. I'll probably start working on this tomorrow.

Update?

I would like to have this functionality too.
To make it work for now I overrode ProcessExistingExternalAccountAsync and  modified UpdateAccountFromExternalClaimsAsync to keep claims in sync. Is it right place to do it?
    protected override async Task<AuthenticateResult> ProcessExistingExternalAccountAsync(string userID, string provider, string providerId, IEnumerable<Claim> claims)
    {
        await UpdateAccountFromExternalClaimsAsync(userID, provider, providerId, claims);
        return await SignInFromExternalProviderAsync(userID, provider);
    }
    protected override async Task<AuthenticateResult> UpdateAccountFromExternalClaimsAsync(string userID, string provider, string providerId, IEnumerable<Claim> claims)
    {
        var existingClaims = await userManager.GetClaimsAsync(userID);
        var intersection = existingClaims.Intersect(claims, new ClaimComparer());
        var newClaims = claims.Except(intersection, new ClaimComparer());
        var oldClaims = existingClaims.Except(intersection, new ClaimComparer());

        foreach (var claim in newClaims)
        {
            var result = await userManager.AddClaimAsync(userID, claim);
            if (!result.Succeeded)
                return new AuthenticateResult(result.Errors.First());
        }
        foreach (var claim in oldClaims)
        {
            if (claim.Issuer.Equals("LOCAL AUTHORITY", StringComparison.InvariantCultureIgnoreCase))
                continue;

            var result = await userManager.RemoveClaimAsync(userID, claim);
            if (!result.Succeeded)
                return new AuthenticateResult(result.Errors.First());
        }
        return null;
    }

Sorry for the delay: we rewrote the implementation since we wanted to keep the link between external claim and external provider. Because the user could have changed his e-mail address for his local account and you don't want to override that when the e-mail address from the external provider changes.

Hi folks,
We're struggling with this exact scenario - any word on when we might see this supported?
R

@AusRob you have the user service -- in 2.0 this is a code file from nuget -- you can modify it (or derive) and modify it any way you want.

HI @brockallen .. I did an implementation similar to @kvoyk 's with no issues.  I'm worried that the default functionality of only storing a user's claims when they first authenticate (and not refreshing ever) might be a bit counter intuitive to folks who aren't expecting this behaviour?

@AusRob different people have different requirements shrug

@AusRob at first sight yes. But when you think of it, when the user changes his/her profile on your webapp, you don't want to override that e-mail address the next time the user signs in using an external identity provider.
We are now keeping external claims in a separate table and each claim has a foreign key to the external provider. This way we never loose any information.
As brockallen says: different people, ... :)


Fixed #18763 -- Added with_perm() to User manager.

https://code.djangoproject.com/ticket/18763

Generally I think this would be useful - I've wanted to know which users have which permissions in the past. However I can think of a many other cases that would be useful:

Which groups have certain permissions, i.e. add GroupManager.with_perm()
Which users have certain permissions directly assigned, i.e. not from membership of a group.
I may want to know what users have permissions regardless of whether they are active.
I may want to to exclude superusers from the output - only show explicit assignations.

Also of note is the obj parameter which is untested. According to the documentation with_perm() should return no users if obj is not None.

Hi @pope1ni,
Thank your for review and suggestions.

Which groups have certain permissions, i.e. add GroupManager.with_perm()

This should probably needs to be discussed in a separate ticket.

I may want to know what users have permissions regardless of whether they are active.
I may want to to exclude superusers from the output - only show explicit assignations.

+1 for adding is_superuser and is_active parameters (or exclude_*) Tim, what do you think?

I think I've addressed all review comments except https://github.com/django/django/pull/7153/files#r78226234 (pending discussion) Thanks!

I've now implemented both my idea from the django-developers thread and Nick Pope's suggestions about adding is_superuser and is_active flags.

Two comments regarding is_active and is_superuser parameters:

is_active has weird behavior IMHO. It's impossible to get ALL users with a permission, including both active and non-active users. I would skip filtering by UserModel.is_active when the value of is_active parameter is None. The valid param values would then be True/False/None. The default value could probably remain True as you only care about active users most of the time (?).
I would rename is_superuser to indicate that it selects whether all superusers are automatically included in results. Maybe e.g. include_superusers?

Closing due to inactivity.

Oh, it's a misunderstanding that a team member has to validate feedback from someone else. You two could at least discuss among yourselves and come to a consensus. I guess it would be better to discuss it on the mailing list thread rather than here. Anyway, I had marked the ticket as "patch needs improvement" given the unresolved comment, so it wasn't going anywhere in the current state.

Well, from a contributor's point of view, it doesn't matter whether we (the contributors) have reached a consensus on our end or not if it doesn't get accepted by the core developers. So what I was trying to say is that at some point it would be nice to know whether we are on the same page or not.
Anyway, thanks for reopening it! I will try to address all review comments this week.

Unfortunately, it's impossible for a team member to give feedback on every issue. The lack of feedback on the mailing list is concerning (maybe there's little demand for this) but If two people come to a consensus, that's a good start.

@berkerpeksag Are you still interested in pursuing this PR?

@rixx thank you for the ping! Yes, I'm still interested in getting this merged. However, last time I discussed it on django-developers, I wasn't able to gather much positive feedback. Perhaps it should be released on PyPI or proposed to a project such as django-extensions first?

@berkerpeksag As far as I could see, there were still some discussions that were not resolved, and the PR is by nature limited, so there are at least documentation warnings missing ("only works with the Django permission backend" would be a start). But I still think this could make for a helpful feature in Django.

I'm glad you found it useful :) I will try to update my branch this weekend.

@berkerpeksag I'd be happy to pick up reviewing this one again and to see some of the other improvements I mentioned up thread implemented. Will keep an eye out for your rebase...

@pope1ni thank you again! I will make sure I've addressed your comments and ping both you and @rixx.

I've addressed most of the review comments. I will add support for Permission instances later tonight.

buildbot

@berkerpeksag Thanks for this patch and your patience 🧘♂ Are you able to prepare this for a final review? (rebase, squash commits, address two nitpicks from me).

Thank you for the review comments! I will address all of them this week.
On Wed, 26 Jun 2019 at 13.10, Mariusz Felisiak<EMAIL_ADDRESS>wrote:

@berkerpeksag https://github.com/berkerpeksag Thanks for this patch and
your patience 🧘♂ Are you able to prepare this for a final review?
(rebase, squash commits, address two nitpicks from me).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/django/django/pull/7153?email_source=notifications&email_token=AAAGNYVLJUGUO6OEPVZGC6TP4M6A5A5CNFSM4CNVA2P2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYTBAZY#issuecomment-505811047,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAGNYQIKHQJ67YKGRBQT5TP4M6A5ANCNFSM4CNVA2PQ
.

--
--Berker

Please uncheck Patch needs improvement flag on the ticket when it's ready.

Superseded by #11625.


Add proposed field names to the mapped named jar

Since @modmuss50 pointed out in #674 that these proposed names should not exist in the tiny gzip'd data, I decided to decompress the tiny data, put enum names in, and then finally map the jar.
Signed-off-by: liach<EMAIL_ADDRESS>

This should be a separate task - the named JAR mapping is for verifying the correctness of Yarn mappings, not augmented Yarn mappings.

Should I tweak this after FabricMC/Enigma#137 or FabricMC/Enigma#138 is merged so that we can use the new task? I will exclude the broken procyon from the dep.

Note to @modmuss50: I have found a way to use new enigma features while holding the procyon dependency back. Will come back to this after FabricMC/Enigma#138 is merged so that we can use the command from enigma lib directly.

@modmuss50 @gegy1000 Pr updated for the latest enigma. Uses latest enigma but still uses the good old procyon. Fixed package mapping errors. Please consider this one before others as this enhances our infrastructure and allows us to do better in the future.

Package fixes should be in another PR, and not mixed in with the gradle changes

@modmuss50 fixed everything and limited scope. Please review this zombie pr again.

Looks good, are we still waiting on fixing Procyon? or reverting it?

procyon is still broken for now, but it is not in the scope of this pr any more. i need to learn procyon like runemoro did in order to fix that.

This should be a separate task - the named JAR mapping is for verifying the correctness of Yarn mappings, not augmented Yarn mappings.

I'd say that if a manually mapped name conflicts with an "augmented" name, the mappings are broken. We've had problems in the past due to a field being named the same as an enum constant.

Merged, not sure why its not shown. Thanks.

Thanks :heart: It just broke for the base branch is pre2 instead of pre4 (I should have updated that)


Error code: Wsl/Service/0x8007273d

Version
Microsoft Windows [Version 10.0.19044.2364]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
No response
Distro Version
Ubuntu 22.04
Other Software
No response
Repro Steps
Start Ubuntu 22.04 or 20.04 installed from the Microsoft Store and notice the following error being reported upon startup:
The attempted operation is not supported for the type of object referenced. Error code: Wsl/Service/0x8007273d Press any key to continue...
Expected Behavior
Ubuntu should start fine.
Actual Behavior
The attempted operation is not supported for the type of object referenced. Error code: Wsl/Service/0x8007273d Press any key to continue...
Diagnostic Logs
No response

@qzmlgfj where di you get the non-store version out of curiosity? This issue happened to me with the latest update of Windows 10, it worked fine before but this is on $corporate machine that forced the upgrade.

Same here, I'm on Windows 10 and this error showed up after installing updates (KB5021233 and KB5021089). Tried the reg fix here but no luck.
Also tried wsl --update and wsl --shutdown then reopen, also no luck

I was able to "fix" this issue by doing the following:

in Add or remove programs: uninstall first "Windows Subsystem for Linux Update" and then "Windows Subsystem for Linux"
try to start your distribution again and it will point you to: https://aka.ms/wsl2kernel
from there download the wsl_update_x64.msi file and run it, install the WSL kernel
start your distribution again

Which seems like what @qzmlgfj did as well.

I was able to "fix" this issue by doing the following:

in Add or remove programs: uninstall first "Windows Subsystem for Linux Update" and then "Windows Subsystem for Linux"
try to start your distribution again and it will point you to: https://aka.ms/wsl2kernel
from there download the wsl_update_x64.msi file and run it, install the WSL kernel
start your distribution again

Which seems like what @qzmlgfj did as well.

Thank you so much, it worked for me

I think it is sufficient just to uninstall "Windows Subsystem for Linux" (either from the Apps Settings, or perhaps instead from the Programs and Features control panel). That takes you back to the old version  of WSL (Windows optional feature, not Windows Store), and everything works again.
I was really looking forward to using the new WSL2 features (especially WSLg and systemd) in Windows 10, so I'd really like to be able to update. But whenever I do update, I always have the same error when I start a distribution:
C:\home>wsl
The attempted operation is not supported for the type of object referenced.
Error code: Wsl/Service/0x8007273d

I get the same error whether I use an old distribution, or a new one created as part of the update. I've tried Ubuntu, Debian, and CentOS7. I've tried uninstalling everything (unregister all distributions, uninstall WSL App, WSL Kernal update, WSL and Virtual Machine Platform from Windows Features) and then installing from scratch with
wsl --install

That runs fine, until it starts the newly-installed distribution, at which point I get the same error code when it tries to set the default username.
Sorry for the long report, but I hope this makes it clear that we don't have a fix, just a way to back out the new version.
For the record, here are the version numbers I get with the broken WSL after the update:
C:\home>wsl --version
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.47
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.2364

@qzmlgfj where di you get the non-store version out of curiosity? This issue happened to me with the latest update of Windows 10, it worked fine before but this is on $corporate machine that forced the upgrade.

@ffainelli I started using WSL in 2020, and it seems the latest update of Windows 10 didn't affect my WSL.
The notification occurs when login WSL tells me to run wsl --update, and everything goes wrong after that.

netsh winsock reset

then restarting my PC works for me
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.47
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.2364

netsh winsock reset

then restarting my PC works for me
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.47
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.2364

This is interesting. The problems I reported before were on an ASUS laptop. I tried on another machine (Dell), and this time it worked! 😄
wsl --update ran smoothly and after that, all my distros ran fine, but now with the new features. So there must be something with my first machine that causes this error with the WSL update.
Here are some differences between the two machines:

ASUS laptop, Intel 7th Gen (i7-6700HQ), Windows 10 22H2 (10.0.19045.2364) - wsl fails after update
Dell laptop, Intel 8th Gen (i5-8350U), Windows 10 21H2 (10.0.19044.2364) - wsl works after update

I don't know if it relevant, but the ASUS's CPU is not on Microsoft's list of Intel processors supported for Windows 11, while the Dell's CPU is. Of course both are running Windows 10, so that shouldn't make a difference. Both CPU have the same feature set, and both work with the previous version of WSL2, so they should work the same.
Apart from the Windows version number reported above, the wsl --version is the same on both machines after update.
Does anyone else who sees this error, have anything that matches my ASUS machine better than my Dell machine? Maybe that'll give us a clue as to what's going on here.

@nurhasyim354:

netsh winsock reset

That fixed the problem for me too! 😁
I ran the winsock reset on my ASUS machine (the one experiencing the problem before I restored the old version of WSL), then ran wsl --update again, and wsl works for both my distros.
Thanks, this is fantastic!

@nurhasyim354:

netsh winsock reset

That fixed the problem for me too! 😁
I ran the winsock reset on my ASUS machine (the one experiencing the problem before I restored the old version of WSL), then ran wsl --update again, and wsl works for both my distros.
Thanks, this is fantastic!

It's really works. Thanks a lot!

netsh winsock reset

then restarting my PC works for me

It works. Thanks for this!

netsh winsock reset

then restarting my PC works for me
WSL version: <IP_ADDRESS> Kernel version: <IP_ADDRESS> WSLg version: 1.0.47 MSRDC version: 1.2.3575 Direct3D version: 1.606.4 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.19045.2364

works for me

netsh winsock reset

then restarting my PC works for me
WSL version: <IP_ADDRESS> Kernel version: <IP_ADDRESS> WSLg version: 1.0.47 MSRDC version: 1.2.3575 Direct3D version: 1.606.4 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.19045.2364

This  Worked for me without event restarting my PC!

netsh winsock reset

Just run this fixed this for me :D
Grateful! Thanks a lot!

I can confirm that using:
netsh winsock reset
works, however after a few hours of uptime, my WSL instances stop responding and just freeze. This did not happen before using the latest WSL update from the store. Anyone seeing this as well?

wsl --update work for me

netsh winsock reset only temporarily fixed the problem for me, second time I try to access wsl I get the error again.
Afterwards I tried running wsl --update and that seems to have fixed it (hopefully).

i have same problem with Proxycap
did fix the problem with proxifire??

I had the same issue,
netsh winsock reset
and
wsl --update
worked for me.

This worked for me:
If you did not enable Windows Subsystem for Linux (see screenshot number 1 below) before downloading WSL from the Microsoft Store, then follow these directions to fix your issue.

Uninstall Windows Subsystem for Linux that was installed from the Microsoft Store (see add/remove programs)

Restart computer
Enable the Windows Subsystem for Linux feature in optional features

Restart computer
Install WSL from the Microsoft Store
All set!  You can now install a distribution.

Screenshots:

Thanks for help guys here!
I run into problem Error code: Wsl/Service/0x8007273d
Tried (downloading, uninstalling ) does not help much
netsh winsock reset        -  helped me .
wsl -l               - quite useful command
if nothing still works you can also downgrade machine to version 1
wsl --set-version Ubuntu-18.04 1   ( for instance downgrade ubuntu version 1 wsl)
wsl --set-version Ubuntu-18.04 2 ( upgrade ubuntu to version 2 wsl)
Before i did winsock reset,  i downgrade to version it was working :)

Thanks @nurhasyim354.
netsh winsock reset   Saved my skin!
WSL: <IP_ADDRESS>
kernel: <IP_ADDRESS>
WSLg: 1.0.51
MSRDC: 1.2.3770
Direct3D: 1.608.2-61064218
DXCore: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows: 10.0.19045.3086

@hycinth22 >
i have same problem with Proxycap did fix the problem with proxifire??

yes, it can be fixed.
Realted issue #4177

Reminder(for windows store users): if you install wsl from windows store, the path to wsl will change and the fix need to be reapplied each time you update to a new version.

I was able to "fix" this issue by doing the following:

in Add or remove programs: uninstall first "Windows Subsystem for Linux Update" and then "Windows Subsystem for Linux"
try to start your distribution again and it will point you to: https://aka.ms/wsl2kernel
from there download the wsl_update_x64.msi file and run it, install the WSL kernel
start your distribution again

Which seems like what @qzmlgfj did as well.

Work for me. Thank you

netsh winsock reset

then restarting my PC works for me
WSL version: <IP_ADDRESS> Kernel version: <IP_ADDRESS> WSLg version: 1.0.47 MSRDC version: 1.2.3575 Direct3D version: 1.606.4 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.19045.2364

netsh winsock reset makes WSL2 works , but also make Proxifier(use winsock) broken. In fact, it is likely that the changes made to Winsock by Proxifier or similar software caused the 0x8007273d error in wsl2.
I found another solution (noLSP): https://wangyj.medium.com/the-solution-to-wsl-error-the-attempted-operation-is-not-supported-for-the-type-of-object-aa559854d1e3 This solution disable proxifier in wsl2, so they can live together.
you can fix Error code: Wsl/Service/0x8007273d by the following steps:
Steps for early version (fresh system installation or install wsl from Windows Feature):

Download Nolsp.exe: http://www.proxifier.com/tmp/Test20200228/NoLsp.exe
configure nolsp via NoLSP.exe "C:\Windows\System32\wsl.exe", it will add a proper registry.
run wsl --shutdown && net stop WslService && net start WslService, close all wsl terminal and reopen wsl
Now, wsl2 can work well.

(Alternatively) If you dont want to use Nolsp.exe binary file, you can Manually add the following items to the registry using regedit.exe.
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\0408F7A3]
"AppFullPath"="C:\Windows\System32\wsl.exe"
"PermittedLspCategories"=dword:80000000

Steps for windows store users or you once run wsl --update (both install wsl from Windows Store):
You are using wsl2 from windows store, so please specify the file path of wsl2 store app("C:\Program Files\WindowsApps\WSL_DIRNAME\wsl.exe") instead of default C:\Windows\System32\wsl.exe.
Firstly, you can obtain the WSL_DIRNAME by the following instruction in cmd(admin):
cd "C:\Program Files\WindowsApps\"
dir MicrosoftCorporationII.WindowsSubsystemForLinux_*

you will see WSL_DIRNAME, it seems like MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe. (different WSL_DIRNAME for different wsl2 versions.)
Next steps:

Download Nolsp.exe: http://www.proxifier.com/tmp/Test20200228/NoLsp.exe
run NoLSP.exe "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\wsl.exe", it will add a proper registry.
run NoLSP.exe "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\wslservice.exe", it will add a proper registry.
(Note: use your WSL_DIRNAME to modify the <IP_ADDRESS>_x64__8wekyb3d8bbwe if you are using a different version.)
run wsl --shutdown && net stop WslService && net start WslService, close all wsl terminal and reopen wsl
Now, wsl2 can work well. And be aware that path to WindowsApps change every time wsl update(so you will need to reconfig nolsp in the future)

(Alternatively) If you dont want to use Nolsp.exe binary file, you can Manually add the following items to the registry using regedit.exe.
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\0A89E33B]
"PermittedLspCategories"=dword:80000000
"AppFullPath"="C:\\Program Files\\WindowsApps\\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\\wsl.exe"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\3A1A96F3]
"PermittedLspCategories"=dword:80000000
"AppFullPath"="C:\\Program Files\\WindowsApps\\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\\wslservice.exe"

(Note: modify the <IP_ADDRESS>_x64__8wekyb3d8bbwe if you are using a different version. And modify the 0A89E33B&3A1A96F3 (yet I dont know how to get valid one if not use NoLSP.exe. so I recommand you use NoLSP.exe)

Thank you. This work for me too, I also have Proxifier installed on my Windows, so I think this is the proper solution/workaround.

netsh winsock reset

then restarting my PC works for me
WSL version: <IP_ADDRESS> Kernel version: <IP_ADDRESS> WSLg version: 1.0.47 MSRDC version: 1.2.3575 Direct3D version: 1.606.4 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.19045.2364

netsh winsock reset makes WSL2 works , but also make Proxifier(use winsock) broken. In fact, it is likely that the changes made to Winsock by Proxifier or similar software caused the 0x8007273d error in wsl2.
I found another solution (noLSP): https://wangyj.medium.com/the-solution-to-wsl-error-the-attempted-operation-is-not-supported-for-the-type-of-object-aa559854d1e3 This solution disable proxifier in wsl2, so they can live together.
you can fix Error code: Wsl/Service/0x8007273d by the following steps:
Steps for early version (fresh system installation or install wsl from Windows Feature):

Download Nolsp.exe: http://www.proxifier.com/tmp/Test20200228/NoLsp.exe
configure nolsp via NoLSP.exe "C:\Windows\System32\wsl.exe", it will add a proper registry.
run wsl --shutdown && net stop WslService && net start WslService, close all wsl terminal and reopen wsl
Now, wsl2 can work well.

(Alternatively) If you dont want to use Nolsp.exe binary file, you can Manually add the following items to the registry using regedit.exe.
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\0408F7A3]
"AppFullPath"="C:\Windows\System32\wsl.exe"
"PermittedLspCategories"=dword:80000000

Steps for windows store users or you once run wsl --update (both install wsl from Windows Store):
You are using wsl2 from windows store, so please specify the file path of wsl2 store app("C:\Program Files\WindowsApps\WSL_DIRNAME\wsl.exe") instead of default C:\Windows\System32\wsl.exe.
Firstly, you can obtain the WSL_DIRNAME by the following instruction in cmd(admin):
cd "C:\Program Files\WindowsApps\"
dir MicrosoftCorporationII.WindowsSubsystemForLinux_*

you will see WSL_DIRNAME, it seems like MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe. (different WSL_DIRNAME for different wsl2 versions.)
Next steps:

Download Nolsp.exe: http://www.proxifier.com/tmp/Test20200228/NoLsp.exe
run NoLSP.exe "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\wsl.exe", it will add a proper registry.
run NoLSP.exe "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\wslservice.exe", it will add a proper registry.
(Note: use your WSL_DIRNAME to modify the <IP_ADDRESS>_x64__8wekyb3d8bbwe if you are using a different version.)
run wsl --shutdown && net stop WslService && net start WslService, close all wsl terminal and reopen wsl
Now, wsl2 can work well. And be aware that path to WindowsApps change every time wsl update(so you will need to reconfig nolsp in the future)

(Alternatively) If you dont want to use Nolsp.exe binary file, you can Manually add the following items to the registry using regedit.exe.
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\0A89E33B]
"PermittedLspCategories"=dword:80000000
"AppFullPath"="C:\\Program Files\\WindowsApps\\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\\wsl.exe"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\3A1A96F3]
"PermittedLspCategories"=dword:80000000
"AppFullPath"="C:\\Program Files\\WindowsApps\\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\\wslservice.exe"

(Note: modify the <IP_ADDRESS>_x64__8wekyb3d8bbwe if you are using a different version. And modify the 0A89E33B&3A1A96F3 (yet I dont know how to get valid one if not use NoLSP.exe. so I recommand you use NoLSP.exe)

Thank you. This work for me too, I also have Proxifier installed on my Windows, so I think this is the proper solution/workaround. In addtion, I run NoLSP.exe C:\Program Files\WSL\wsl.exe and NoLSP.exe C:\Program Files\WSL\wslservice.exe instead of NoLSP.exe "path of the WSL.exe from Microsoft Store".

dunno why this solution is so damn hard to find. It is single solution that worked for me.

netsh winsock reset

then restarting my PC works for me
WSL version: <IP_ADDRESS> Kernel version: <IP_ADDRESS> WSLg version: 1.0.47 MSRDC version: 1.2.3575 Direct3D version: 1.606.4 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.19045.2364

netsh winsock reset makes WSL2 works , but also make Proxifier(use winsock) broken. In fact, it is likely that the changes made to Winsock by Proxifier or similar software caused the 0x8007273d error in wsl2.
I found another solution (noLSP): https://wangyj.medium.com/the-solution-to-wsl-error-the-attempted-operation-is-not-supported-for-the-type-of-object-aa559854d1e3 This solution disable proxifier in wsl2, so they can live together.
you can fix Error code: Wsl/Service/0x8007273d by the following steps:
Steps for early version (fresh system installation or install wsl from Windows Feature):

Download Nolsp.exe: http://www.proxifier.com/tmp/Test20200228/NoLsp.exe
configure nolsp via NoLSP.exe "C:\Windows\System32\wsl.exe", it will add a proper registry.
run wsl --shutdown && net stop WslService && net start WslService, close all wsl terminal and reopen wsl
Now, wsl2 can work well.

(Alternatively) If you dont want to use Nolsp.exe binary file, you can Manually add the following items to the registry using regedit.exe.
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\0408F7A3]
"AppFullPath"="C:\Windows\System32\wsl.exe"
"PermittedLspCategories"=dword:80000000

Steps for windows store users or you once run wsl --update (both install wsl from Windows Store):
You are using wsl2 from windows store, so please specify the file path of wsl2 store app("C:\Program Files\WindowsApps\WSL_DIRNAME\wsl.exe") instead of default C:\Windows\System32\wsl.exe.
Firstly, you can obtain the WSL_DIRNAME by the following instruction in cmd(admin):
cd "C:\Program Files\WindowsApps\"
dir MicrosoftCorporationII.WindowsSubsystemForLinux_*

you will see WSL_DIRNAME, it seems like MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe. (different WSL_DIRNAME for different wsl2 versions.)
Next steps:

Download Nolsp.exe: http://www.proxifier.com/tmp/Test20200228/NoLsp.exe
run NoLSP.exe "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\wsl.exe", it will add a proper registry.
run NoLSP.exe "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\wslservice.exe", it will add a proper registry.
(Note: use your WSL_DIRNAME to modify the <IP_ADDRESS>_x64__8wekyb3d8bbwe if you are using a different version.)
run wsl --shutdown && net stop WslService && net start WslService, close all wsl terminal and reopen wsl
Now, wsl2 can work well. And be aware that path to WindowsApps change every time wsl update(so you will need to reconfig nolsp in the future)

(Alternatively) If you dont want to use Nolsp.exe binary file, you can Manually add the following items to the registry using regedit.exe.
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\0A89E33B]
"PermittedLspCategories"=dword:80000000
"AppFullPath"="C:\\Program Files\\WindowsApps\\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\\wsl.exe"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\3A1A96F3]
"PermittedLspCategories"=dword:80000000
"AppFullPath"="C:\\Program Files\\WindowsApps\\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\\wslservice.exe"

(Note: modify the <IP_ADDRESS>_x64__8wekyb3d8bbwe if you are using a different version. And modify the 0A89E33B&3A1A96F3 (yet I dont know how to get valid one if not use NoLSP.exe. so I recommand you use NoLSP.exe)

This worked for me but with the following paths for wsl and wslservice:

nolsp.exe "C:\Program Files\WSL\wsl.exe"
nolsp.exe "C:\Program Files\WSL\wslservice.exe"

I was able to "fix" this issue by doing the following:

in Add or remove programs: uninstall first "Windows Subsystem for Linux Update" and then "Windows Subsystem for Linux"
try to start your distribution again and it will point you to: https://aka.ms/wsl2kernel
from there download the wsl_update_x64.msi file and run it, install the WSL kernel
start your distribution again

Which seems like what @qzmlgfj did as well.

This solution does not work for me