VORC issues with robot localization - Should we switch to Melodic?

When I run the VORC localization example from https://github.com/osrf/vorc/wiki/sensors
roslaunch vorc_gazebo marina.launch verbose:=true

and then
roslaunch vorc_gazebo localization_example.launch

I get the SPAM Warnings below.
Perhaps we should switch the image back to Melodic to minimize new issues with VORC?
SPAM Warnings
Warning: Warning: TF_REPEATED_DATA ignoring data with redundant timestamp for frame right_engine_link at time 18.340000 according to authority unknown_publisherTF_REPEATED_DATA ignoring data with redundant timestamp for frame right_engine_link at time 18.340000 according to authority unknown_publisher

         at line          at line 278278 in  in /tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp/tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp

Warning: TF_REPEATED_DATA ignoring data with redundant timestamp for frame right_propeller_link at time 18.340000 according to authority unknown_publisher
         at line 278 in /tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp
Warning: TF_REPEATED_DATA ignoring data with redundant timestamp for frame right_propeller_link at time 18.340000 according to authority unknown_publisher
         at line 278 in /tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp
Warning: Warning: TF_REPEATED_DATA ignoring data with redundant timestamp for frame left_engine_link at time 18.940000 according to authority unknown_publisher
         at line 278 in TF_REPEATED_DATA ignoring data with redundant timestamp for frame left_engine_link at time 18.940000 according to authority unknown_publisher/tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp
Warning: TF_REPEATED_DATA ignoring data with redundant timestamp for frame left_propeller_link at time 18.940000 according to authority unknown_publisher
         at line 278 in
         at line 278 in /tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp
Warning: TF_REPEATED_DATA ignoring data with redundant timestamp for frame left_propeller_link at time 18.940000 according to authority unknown_publisher
         at line 278 in /tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp/tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp

Warning: Warning: TF_REPEATED_DATA ignoring data with redundant timestamp for frame right_engine_link at time 18.940000 according to authority unknown_publisher
         at line TF_REPEATED_DATA ignoring data with redundant timestamp for frame right_engine_link at time 18.940000 according to authority unknown_publisher278
 in          at line /tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp278
 in Warning: /tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp
TF_REPEATED_DATA ignoring data with redundant timestamp for frame right_propeller_link at time 18.940000 according to authority unknown_publisherWarning:
         at line TF_REPEATED_DATA ignoring data with redundant timestamp for frame right_propeller_link at time 18.940000 according to authority unknown_publisher278
 in          at line /tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp278
 in /tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp
[ WARN] [1619374392.793045111, 19.210000000]: Could not obtain transform from cora/imu_link to cora/base_link. Error was "cora/base_link" passed to lookupTransform argument target_frame does not exist.

Warning: TF_REPEATED_DATA ignoring data with redundant timestamp for frame left_engine_link at time 19.340000 according to authority unknown_publisher
         at line 278 in /tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp
Warning: TF_REPEATED_DATA ignoring data with redundant timestamp for frame left_propeller_link at time 19.340000 according to authority unknown_publisher
         at line 278 in /tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp
Warning: TF_REPEATED_DATA ignoring data with redundant timestamp for frame right_engine_link at time 19.340000 according to authority unknown_publisher
         at line 278 in /tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp
Warning: TF_REPEATED_DATA ignoring data with redundant timestamp for frame right_propeller_link at time 19.340000 according to authority unknown_publisher
         at line 278 in /tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp
Warning: TF_REPEATED_DATA ignoring data with redundant timestamp for frame left_engine_link at time 19.340000 according to authority unknown_publisher
         at line 278 in /tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp
Warning: TF_REPEATED_DATA ignoring data with redundant timestamp for frame left_propeller_link at time 19.340000 according to authority unknown_publisher
         at line 278 in /tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp
Warning: TF_REPEATED_DATA ignoring data with redundant timestamp for frame right_engine_link at time 19.340000 according to authority unknown_publisher
         at line 278 in /tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp
Warning: TF_REPEATED_DATA ignoring data with redundant timestamp for frame right_propeller_link at time 19.340000 according to authority unknown_publisher
         at line 278 in /tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp
Warning: Warning: TF_REPEATED_DATA ignoring data with redundant timestamp for frame left_engine_link at time 19.640000 according to authority unknown_publisherTF_REPEATED_DATA ignoring data with redundant timestamp for frame left_engine_link at time 19.640000 according to authority unknown_publisher

         at line          at line 278278 in  in /tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp/tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp

Warning: TF_REPEATED_DATA ignoring data with redundant timestamp for frame left_propeller_link at time 19.640000 according to authority unknown_publisher
         at line Warning: TF_REPEATED_DATA ignoring data with redundant timestamp for frame left_propeller_link at time 19.640000 according to authority unknown_publisher
278         at line  in 278/tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp in
/tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp
Warning: Warning: TF_REPEATED_DATA ignoring data with redundant timestamp for frame right_engine_link at time 19.640000 according to authority unknown_publisherTF_REPEATED_DATA ignoring data with redundant timestamp for frame right_engine_link at time 19.640000 according to authority unknown_publisher

         at line          at line 278278 in  in /tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp
/tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cppWarning:
TF_REPEATED_DATA ignoring data with redundant timestamp for frame right_propeller_link at time 19.640000 according to authority unknown_publisher
         at line 278 in /tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp
Warning: TF_REPEATED_DATA ignoring data with redundant timestamp for frame right_propeller_link at time 19.640000 according to authority unknown_publisher
         at line 278 in /tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp
Warning: TF_REPEATED_DATA ignoring data with redundant timestamp for frame left_engine_link at time 20.240000 according to authority unknown_publisher
         at line 278 in Warning: /tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cppTF_REPEATED_DATA ignoring data with redundant timestamp for frame left_engine_link at time 20.240000 according to authority unknown_publisher

         at line Warning: 278TF_REPEATED_DATA ignoring data with redundant timestamp for frame left_propeller_link at time 20.240000 according to authority unknown_publisher in
/tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp         at line
278 in /tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cppWarning:
TF_REPEATED_DATA ignoring data with redundant timestamp for frame left_propeller_link at time 20.240000 according to authority unknown_publisher
         at line Warning: 278TF_REPEATED_DATA ignoring data with redundant timestamp for frame right_engine_link at time 20.240000 according to authority unknown_publisher in
/tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp         at line
278 in Warning: /tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cppTF_REPEATED_DATA ignoring data with redundant timestamp for frame right_engine_link at time 20.240000 according to authority unknown_publisher

         at line 278Warning:  in TF_REPEATED_DATA ignoring data with redundant timestamp for frame right_propeller_link at time 20.240000 according to authority unknown_publisher/tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp

         at line Warning: TF_REPEATED_DATA ignoring data with redundant timestamp for frame right_propeller_link at time 20.240000 according to authority unknown_publisher
278         at line  in 278/tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp in /tmp/binarydeb/ros-noetic-tf2-0.7.5/src/buffer_core.cpp

@M1chaelM Could you try on your Noetic host and see if you get the same?

@bsb808 Yes. I just ran it and I'm seeing the same output locally. Also, as we discussed, I think it would be better to fix this if possible than to roll back to melodic.

After looking into running VORC on Noetic, I saw quite a few issues, and I would say more time is required to do an actual port of VORC to Noetic.

The issue in this ticket is actually a known issue. You can ignore the warnings:
https://answers.ros.org/question/359968/tf_repeated_data-error-with-robot_localization-ukf-package/
There is a very long discussion here between authorities of robot_localization and tf, with this resolution:
https://github.com/ros/geometry2/issues/467#issuecomment-695052790
which seems to not have been implemented.
A workaround to hide the ugliness is by piping the output:
roslaunch vorc_gazebo localization_example.launch 2>/dev/null

A bigger problem though is that tf_prefix is no longer supported in Noetic https://github.com/ros/robot_state_publisher/pull/82
There has been requests to restore it https://github.com/ros/robot_state_publisher/pull/139
But currently Noetic does not support tf_prefix, which is used in localization_example.launch.
There is a workaround suggested here of adding a prefix to every link in the URDF. That wasn't straight forward, because SDF did not like slashes being in link or joint names https://github.com/ros/robot_state_publisher/issues/147
A quick and dirty workaround is to strip all the tf prefixes (@caguero would that work with all the sensors?), but even then, there are still a few other issues in RViz.

I stopped for the week after stripping the tf prefixes from everything. The following issues remain.

In RViz, the tf tree complains that utm cannot find a transform to base_link.

In RViz, the point cloud is still published with respect to a cora prefix, so it cannot be displayed. That should be an easy fix, either in VORC or in VRX, but I haven't looked at where.

RViz cannot show the robot model currently, which may or may not matter depending on the use case:
[ WARN] [1619859868.191737509, 12.309000000]: OGRE EXCEPTION(6:FileNotFoundException): Cannot locate resource package://cora_description/models/meshes/propellerR.dae in resource group Autodetect or any other group. in ResourceGroupManager::openResource at /build/ogre-1.9-kiU5_5/ogre-1.9-1.9.0+dfsg1/OgreMain/src/OgreResourceGroupManager.cpp (line 753)
[ERROR] [1619859868.191772353, 12.309000000]: Could not load model 'package://cora_description/models/meshes/propellerR.dae' for link 'right_propeller_link': OGRE EXCEPTION(6:FileNotFoundException): Cannot locate resource package://cora_description/models/meshes/propellerR.dae in resource group Autodetect or any other group. in ResourceGroupManager::openResource at /build/ogre-1.9-kiU5_5/ogre-1.9-1.9.0+dfsg1/OgreMain/src/OgreResourceGroupManager.cpp (line 753)

I haven't looked into the remaining issues to say how long they would take. For the time being, I would suggest allocating time to properly port VRX and VORC to Noetic. Cc @caguero .

Thank you @mabelzhang for taking a look and getting a first cut at the scope of the effort.
For the problem at hand I'm going to skirt around using robot_localization.  Instead we'll use the P3D plugin and a custom node to emulate the interface to a GPS-aided IMU solution.


ctr: wrong relative path

$ pwd
/home/pi/ocibundles/armv7/blink

$ sudo ctr containers start . blink
[ctr] rpc error: code = 2 desc = "JSON specification file at /home/pi/ocibundles/armv7/blink/blink/config.json not found"

What is expected is reading the bundle from /home/pi/ocibundles/armv7/blink/config.json not from /home/pi/ocibundles/armv7/blink/blink/config.json.
Related to https://github.com/docker/containerd/commit/facfce3e8e436d863a45f9e972ede1c77ec48653.

It should be ctr containers start blink .
Wrong positioning of the arguments. The relative paths are properly calculated. Closing the issue.


Conway fee calculation

Makes the internal wallet use the right computation depending on the current era. We support Babbage and Conway in that part of the application now by making things a bit more polymorphic on the era.
Co-authored by @noonio and @ffakenz

[x] CHANGELOG updated
[x] Documentation update not needed
[x] Haddocks updated
[ ] No new TODOs introduced or explained herafter

Left a FIXME in the TxSpec which seems to not do its job (for longer already).

We can verify this working correctly on our open head on preview too before merging this.


Add missing client paths to CNS Client

These were forgotten during a previous effort to add endpoints to the
CNS client. Consequently, those endpoints don't actually work unless
these paths are present here.

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests

Notes:

bypassing broken akse tests

Heh, I was confused why those were broken and wailed on "re-build" a couple of times. Thanks for merging it :)


Add option to cobot to close an issue

https://gitlab.com/coala/cobot/issues/30

@jayvdb Can we limit this command to devs and maintainers?

@jayvdb Can we limit this command to devs and maintainers?

Actually I don't want to give developers the control to close issues, I think maintainers should take a look and decide whether an issue is solved/valid/etc, because they usually have a better overview of the situation / know where to get the relevant information.
As maintainers are already able to close issues/PRs to their likings directly via GitHub UI, I would vote to tag this issue as invalid.
@jayvdb you are more or less my opinion if I've read correctly on the GitLab issue. But the issue is quite old, maybe it has changed? ;)

IMO if an issue is opened through corobo then the only person that should be able to close it with corobo should be the original issue author

IMO if an issue is opened through corobo then the only person that should be able to close it with corobo should be the original issue author

Even in that case I'm not always sure. Sometimes they might close them because they think they filed them "badly" (e.g. typo) instead of editing them (although only maintainers can do this), or because of other reasons.

@jayvdb or @Makman2  is this issue still need enhancement? I mean do we need an option to close issue because ithink @Makman2 is saying absolutely true that rights for closing any issue should be only with maintainers

@AkshJain99 Yeah I think the command should only cater to maintainers or developers since the right to close an issue should rest with the developers.

do you think that developer should be given rights to close issue?

@AkshJain99 No they should not be given be given rights they should only be available to maintainers, because they are the ones to merge an issue so they should be the ones to close it as well.

yes i thought the same :+1:

It's decided: we won't implement something in this direction without a major reason.


init() got an unexpected keyword argument 'use_linear_in_transformer'

I have installed stable-diffusion v2 and run following commands in the provided ldm environment:
python scripts/txt2img.py --prompt "a professional photograph of an astronaut riding a horse" --ckpt .\v2-1_768-ema-pruned.ckpt --config .\configs\stable-diffusion\v2-inference.yaml
But I keep getting an error:
(ldm) PS C:\Programming\Python\stablediffusion> python scripts/txt2img.py --prompt "a professional photograph of an astronaut riding a horse" --ckpt .\v2-1_768-ema-pruned.ckpt --config .\configs\stable-diffusion\v2-inference.yaml
Global seed set to 42
Loading model from .\v2-1_768-ema-pruned.ckpt
Global Step: 110000
LatentDiffusion: Running in eps-prediction mode
Traceback (most recent call last):
  File "scripts/txt2img.py", line 289, in <module>
    main(opt)
  File "scripts/txt2img.py", line 190, in main
    model = load_model_from_config(config, f"{opt.ckpt}")
  File "scripts/txt2img.py", line 34, in load_model_from_config
    model = instantiate_from_config(config.model)
  File "c:\programming\python\stable-diffusion\ldm\util.py", line 85, in instantiate_from_config
    return get_obj_from_str(config["target"])(**config.get("params", dict()))
  File "c:\programming\python\stable-diffusion\ldm\models\diffusion\ddpm.py", line 448, in __init__
    super().__init__(conditioning_key=conditioning_key, *args, **kwargs)
  File "c:\programming\python\stable-diffusion\ldm\models\diffusion\ddpm.py", line 86, in __init__
    self.model = DiffusionWrapper(unet_config, conditioning_key)
  File "c:\programming\python\stable-diffusion\ldm\models\diffusion\ddpm.py", line 1398, in __init__
    self.diffusion_model = instantiate_from_config(diff_model_config)
  File "c:\programming\python\stable-diffusion\ldm\util.py", line 85, in instantiate_from_config
    return get_obj_from_str(config["target"])(**config.get("params", dict()))
TypeError: __init__() got an unexpected keyword argument 'use_linear_in_transformer'

Also tried not providing a config. Didn't help.
How to solve it?

+1  - I have the same issue

This issue should because you have an old version of stable diffusion in your path.

No, I checked, I have the latest pull

I have installed stable-diffusion v2 and run following commands in the provided ldm environment: python scripts/txt2img.py --prompt "a professional photograph of an astronaut riding a horse" --ckpt .\v2-1_768-ema-pruned.ckpt --config .\configs\stable-diffusion\v2-inference.yaml
But I keep getting an error:
(ldm) PS C:\Programming\Python\stablediffusion> python scripts/txt2img.py --prompt "a professional photograph of an astronaut riding a horse" --ckpt .\v2-1_768-ema-pruned.ckpt --config .\configs\stable-diffusion\v2-inference.yaml
Global seed set to 42
Loading model from .\v2-1_768-ema-pruned.ckpt
Global Step: 110000
LatentDiffusion: Running in eps-prediction mode
Traceback (most recent call last):
  File "scripts/txt2img.py", line 289, in <module>
    main(opt)
  File "scripts/txt2img.py", line 190, in main
    model = load_model_from_config(config, f"{opt.ckpt}")
  File "scripts/txt2img.py", line 34, in load_model_from_config
    model = instantiate_from_config(config.model)
  File "c:\programming\python\stable-diffusion\ldm\util.py", line 85, in instantiate_from_config
    return get_obj_from_str(config["target"])(**config.get("params", dict()))
  File "c:\programming\python\stable-diffusion\ldm\models\diffusion\ddpm.py", line 448, in __init__
    super().__init__(conditioning_key=conditioning_key, *args, **kwargs)
  File "c:\programming\python\stable-diffusion\ldm\models\diffusion\ddpm.py", line 86, in __init__
    self.model = DiffusionWrapper(unet_config, conditioning_key)
  File "c:\programming\python\stable-diffusion\ldm\models\diffusion\ddpm.py", line 1398, in __init__
    self.diffusion_model = instantiate_from_config(diff_model_config)
  File "c:\programming\python\stable-diffusion\ldm\util.py", line 85, in instantiate_from_config
    return get_obj_from_str(config["target"])(**config.get("params", dict()))
TypeError: __init__() got an unexpected keyword argument 'use_linear_in_transformer'

Also tried not providing a config. Didn't help.
How to solve it?

Have you solved it?

No, I haven't

Same issue

But I just remove that line in v2-inference.yaml and it works
use_linear_in_transformer: True

I fixed it by reinstalling miniconda.

I have installed stable-diffusion v2 and run following commands in the provided ldm environment: python scripts/txt2img.py --prompt "a professional photograph of an astronaut riding a horse" --ckpt .\v2-1_768-ema-pruned.ckpt --config .\configs\stable-diffusion\v2-inference.yaml
But I keep getting an error:
(ldm) PS C:\Programming\Python\stablediffusion> python scripts/txt2img.py --prompt "a professional photograph of an astronaut riding a horse" --ckpt .\v2-1_768-ema-pruned.ckpt --config .\configs\stable-diffusion\v2-inference.yaml
Global seed set to 42
Loading model from .\v2-1_768-ema-pruned.ckpt
Global Step: 110000
LatentDiffusion: Running in eps-prediction mode
Traceback (most recent call last):
  File "scripts/txt2img.py", line 289, in <module>
    main(opt)
  File "scripts/txt2img.py", line 190, in main
    model = load_model_from_config(config, f"{opt.ckpt}")
  File "scripts/txt2img.py", line 34, in load_model_from_config
    model = instantiate_from_config(config.model)
  File "c:\programming\python\stable-diffusion\ldm\util.py", line 85, in instantiate_from_config
    return get_obj_from_str(config["target"])(**config.get("params", dict()))
  File "c:\programming\python\stable-diffusion\ldm\models\diffusion\ddpm.py", line 448, in __init__
    super().__init__(conditioning_key=conditioning_key, *args, **kwargs)
  File "c:\programming\python\stable-diffusion\ldm\models\diffusion\ddpm.py", line 86, in __init__
    self.model = DiffusionWrapper(unet_config, conditioning_key)
  File "c:\programming\python\stable-diffusion\ldm\models\diffusion\ddpm.py", line 1398, in __init__
    self.diffusion_model = instantiate_from_config(diff_model_config)
  File "c:\programming\python\stable-diffusion\ldm\util.py", line 85, in instantiate_from_config
    return get_obj_from_str(config["target"])(**config.get("params", dict()))
TypeError: __init__() got an unexpected keyword argument 'use_linear_in_transformer'

Also tried not providing a config. Didn't help.
How to solve it?

Hi, I think reinstall miniconda is not the key to solve this problem. Please note that your path includes "stable-diffusion", indicating that you have not only downloaded this repo, but also downloaded v1. Additionally, you should have also installed v1 (possibly by running pip install -e ., though I'm not entirely sure). Therefore, the code is executing stable-diffusion instead of stablediffusion. There is no corresponding implementation in stable-diffusion, leading to this error.


bower dependencies OOD

bower-asset/ngclipboard 1.1.1 requires bower-asset/clipboard ~1.5.5 -> no matching package found.

 "clipboard": "~1.5.5", doesn't match later clipboard versions like v1.6.x and v1.7.x


Remove extraneous mimetype from EncryptedFile examples, per MSC2582

MSC: https://github.com/matrix-org/matrix-doc/pull/2582

This duplicates https://github.com/matrix-org/matrix-doc/pull/3314, but it also removes two spaces. So technically it is the superior PR.

oops, sorry @anoadragon453 - didn't see that PR :(


Update survey_data.rst

Use Ohm-m for the units of resistivity (in mathtype)

@dccowan: would you mind taking a quick look at this? Thanks!


Fix Travis

For #2839 and IRC.

Ready for review.

1b212b9 (second commit) looks fine, I'm doubtful about fb11677.
I did a few tests for this on my fork - I added the below commands to before_install to see what they output.
For a push to master:
$ echo "`git rev-parse --abbrev-ref HEAD`"
> HEAD
$ echo "${TRAVIS_BRANCH}"
> master

For a pull request:
$ echo "`git rev-parse --abbrev-ref HEAD`"
> HEAD
$ echo "${TRAVIS_BRANCH}"
> to-test-travis

So our if condition is useless, since it uses git rev-parse --abbrev-ref HEAD. I guess it should work if we used TRAVIS_BRANCH instead. What do you think, @Changaco?

I'd also mentioned this earlier on https://github.com/gratipay/gratipay.com/issues/2806#issuecomment-58930269

@rohitpaulk Done.

Actually, no, that's not correct.

http://docs.travis-ci.com/user/ci-environment/

TRAVIS_BRANCH: For builds not triggered by a pull request this is the name of the branch currently being built; whereas for builds triggered by a pull request this is the name of the branch targeted by the pull request (in many cases this will be master).

I've modified the commit to also check "${TRAVIS_PULL_REQUEST}" = "false":

TRAVIS_PULL_REQUEST: The pull request number if the current job is a pull request, "false" if it's not a pull request.

Aah yh you're right, I was looking at the build triggered by the push, not the PR.


Update content of consignment submission confirmation

This PR updates the content of the consignment submission confirmation, and makes some related small changes to the consignment submission failure.
Submission confirmation

Tapping "Done" will close the modal; tapping "Browse new works for sale" will close the modal and take you to the home tab.
Submission failure

Oops, I always forget to deal with the changelog. I consider this to fall under the umbrella of an existing changelog entry.


Bug: Import from a Compendium don't bring the entity data

In GitLab by @brunocalado on Apr 2, 2021, 17:23
Bug: Import from a Compendium don't bring the entity data
If you export a folder to a compendium, it looks like worked.
But, if import it back, it don't bring the data.
You can test with this module: https://github.com/brunocalado/masks-newgeneration-unofficial
Labels (do-not-change)
/cc @Asacolips

In GitLab by @brunocalado on Apr 4, 2021, 13:50
Before Import

After Import

In GitLab by @Asacolips on Apr 4, 2021, 12:06
My logic to initialize actors and items with clean data from the TOML sheet config was too aggressive and was essentially deleting the incoming data if coming from a compendium or other duplicate source. This should be resolved in the public beta50-0.1.0 build.

In GitLab by @Asacolips on Apr 4, 2021, 12:02
mentioned in commit 02f81ed74c52b4ac6e13b26ed91b35433d3f91bd

In GitLab by @brunocalado on Apr 4, 2021, 13:15
Still not working.
Now it have the description. But, not the move roll.


Multiple Network Interfaces

Hello Everyone,
Is it possible to assign multiple network interfaces, NOT multiple IPs, to AWS instances via Vagrant?  I tried using aws.elastic_ip=true hoping that an additional NIC would get assigned, but that was an incorrect expectation.
I need to create two interfaces per instance for the environment that I'm building, and it would be great if anyone can advise how this may be possible via Vagrant.
Thanks,
Trevor

I need two interface per instance as well. Did you find if is possible to create two interfaces with Vagrant AWS?


Implement a proper shape checking rule for scatter.

The implementation is based on the corresponding shape inference
code in tensorflow/compiler/xla/service/shape_inference.cc. The
tests added in tests/lax_test.py are similarly mirroring the
corresponding tests in tensorflow, with slight adaptations for
the particular setting of JAX.

This should close #3724, #2427


fix: remove noFeedback from external link embeds, add divider

Otherwise it looks like a picture instead of a link embed. Closes #752

I need to re-read some suggestions I got around this before I act on it; going to put this off for a bit.

Thanks again for this contribution! I think we've solved core intent of this PR and the issue, and we have more link/pressable improvements on the todo list, so gonna close for now. If you feel differently please let us know! 🙂


[OpPerf] Add norm, cast ops, remaining optimizer ops

Description
Adds following ops to OpPerf [once all the OpPerf PRs get merged, all MXNet ops in NDArray namespace will be completed in OpPerf coverage (minus deprecated, _contrib ops and few other ops with known issues)]

norm op to reduction category
Following Optimizer ops

mp_nag_mom
nag_mom
lambd_update_phase_1 and 2
preloaded_multi_*
multi_*

Cast ops

cast
amp_cast
amp_multicast

Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage:
[x] Code is well-documented:
[x] To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Comments
Ops falling in the category of multi_* and preloaded_multi_* were notorious
They don't have standard keyworded arguments (data=data)
They expect variable positional args (*data)
It was previously handled such that only 1 value of variable positional arg could be passed
Now, you can pass as many values for positional args as you want.
However for running run_performance_test, inputs have to be key:value pair
That is handled as args0, args1, arg2, etc
So as long as the name of the key starts with args it will be considered as input for the operator.
This is a very rare case that the operator doesn't take keyworded args. Most other ops in MXNet NDArray namespace take keyworded args.

Category specific operators gist : https://gist.github.com/ChaiBapchya/8c4ffb924fe20de1297d53fb4d1a5b1e
Basically result of running
>>> from benchmark.opperf.nd_operations.nn_optimizer_operators import run_optimizer_operators_benchmarks
>>> run_optimizer_operators_benchmarks()

>>> from benchmark.opperf.nd_operations.reduction_operators import run_mx_reduction_operators_benchmarks
>>> run_mx_reduction_operators_benchmarks()

>>> from benchmark.opperf.nd_operations.unary_operators import run_mx_unary_operators_benchmarks
>>> run_mx_unary_operators_benchmarks()

Entire OpPerf Suite
CPU results : https://gist.github.com/ChaiBapchya/1c26e5a904d9ce9342d61b29f195c5cf

Previously entire NDArray that was input used to get printed
This would not be rendered correctly on Markdown (come up as new lines).
Now after this fix, only the shape of NDArray is stored as a String (much more readable and rendered correctly on Markdown)
CPU : https://gist.github.com/ChaiBapchya/12d7fdd4ac15703e537aefbc8055c981
GPU : https://gist.github.com/ChaiBapchya/c62c7fff4deb115b64ec69b5c4aa6a7d

@mxnet-label-bot add [pr-awaiting-review]

Updated OpPerf results after dtype fix
CPU : https://gist.github.com/ChaiBapchya/dbe941cb65d493c6e435c68a6bbc5b19
GPU : https://gist.github.com/ChaiBapchya/479b3b8efb68398d290a5e5863c7809f


First Name, Last Name and Subject should be required fields on contact us page

Please assign me this under LGMSOC'21

Make all the fields required @Sukhseerat-Kaur


ModuleNotFoundError: No module named 'llama_index'

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
from llama_index.core.query_engine import RetrieverQueryEngine
ModuleNotFoundError: No module named 'llama_index'
...its showing module NotFounderror how to fix it??

Did you run pip install llama-index ?
Maybe start with a fresh venv
pip uninstall llama-index # Remove any global install
python -m venv venv
source venv/bin/activate
pip install llama-index

Thank you for your suggestion..I'll try and see if it works

isn't happening with fresh env

ModuleNotFoundError: No module named 'llama_index'
iam also facing the same issue but it shows llama_indexa after running the command pip list
But when i run the code
from llama_index import VectorStoreIndex, SimpleDirectoryReader, ServiceContext
from llama_index.llms import HuggingFaceLLM
it is showing the error:
ModuleNotFoundError: No module named 'llama_index'

One error that I had at my end was my file name was "llama_index.py" and when I tried to import from llama_index.llms etc, it would do a circular import and throw this error. Change your file name and it works fine.

Thanks for the tip!
On Mon, 24 Jun 2024 at 17:47, Ashmal Vayani @.***>
wrote:

One error that I had at my end was my file name was "llama_index.py" and
when I tried to import from llama_index.llms etc, it would do a circular
import and throw this error. Change your file name and it works fine.
—
Reply to this email directly, view it on GitHub
https://github.com/run-llama/llama_index/issues/11584#issuecomment-2186443778,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BI7V4KM7G2NM7R3VJGVKR3LZJAE6PAVCNFSM6AAAAABED2LKLCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBWGQ2DGNZXHA
.
You are receiving this because you commented.Message ID:
@.***>

--
The information in this message may be proprietary and/or confidential and
protected from disclosure. If the reader of this message is not the
intended recipient, you are hereby notified that any dissemination,
distribution, or copying of this communication is strictly prohibited. If
you have received this communication in error, please notify ATMECS and
delete it from your computer.

One error that I had at my end was my file name was "llama_index.py" and when I tried to import from llama_index.llms etc, it would do a circular import and throw this error. Change your file name and it works fine.

you mean i need to download the py file of llama_index

There's no need to download anything. I made a custom python file through which I was running my code. The name of that file was "llana_index.py", I just changed the name of that file and it worked for me.


SaveStateAsync and QueryStateAsync dont seem to work well together with redis-stack

Hello:
I have issues when trying to query Redis state using QueryStateAsync.
I am running Dapr 1.9.4 with redis-stack:latest (to be able to use RedisJSON and RediSearch) and .Net C# Dapr.AspNetCore 1.9.0.
I first run this to add an entry to RedisDB:
await daprClient.SaveStateAsync("statestore", "post10", "post10");
The call above creates correctly a HASH statestore||post10 entry on Redis with data:"post10" and version:1 as shown below:

On Redis I have created an index like this:
FT.CREATE dataIdx ON HASH PREFIX 1 statestore SCHEMA data AS data TEXT
and when testing directly with the Redis command it works well, so:
FT.SEARCH dataIdx @data:(post10) returns:
1) "1"
2) "statestore||post10"
3) 1) "data"
   2) "\"post10\""
   3) "version"
   4) "1"

On my Dapr Config I have created the index like this:
- name: queryIndexes
  value: |
      [
          {
              "name": "dataIdx",
              "indexes": [
                {
                  "key": "data",
                  "type": "TEXT"
                }
              ]
          }
      ]

Then I run this to retrieve the same entry using DaprClient:
Dictionary<string, string> metadata = new() { { "contentType", "application/json" }, { "queryIndexName", "dataIdx" } };
await daprClient.QueryStateAsync<object>("statestore", query, metadata: metadata);
The query is just this:
{
  "filter": {
    "EQ": { "data": "post10" }
  }
}

From the above request I get empty result and when I check with WireShark I see the query is almost the same, the only difference is the replace of 'data' by 'var0':
*7
$9
FT.SEARCH
$7
dataIdx
$14
@var0:(post10)
$6
RETURN
$1
2
$6
$.data
$9
$.version
*1
:0

Thanks in advance for any help.

Did you solve a problem?
I follow your steps, and always get "invalid output" error.


Need fast cold start from peer snapshots

Fixed.
Exp: https://www.notion.so/comcom/Blockchain-node-sync-time-in-cold-start-975d8325745e4797ba1d9ea4dccc1e72


Improve brightness (luminescence) calculation

Was looking at your code in how you calculate brightness. R+G+B/255/3 isn't accurate as to how humans perceive luminescence. A more accurate formula is as follows.
L=0.2126R_+0.7152G_+0.0722*B from Relative Luminance
Happy to make an attempt at this change and go through some comparison of the results.

Nice! Good work man.


fix: GoogleMap in preview early return breaking preview layout

Fixes #212

Thank you for your contribution @claytongreen!


Factorial should take precedence over fractions

Description
The equation f(x) / 2 gets implicitly parenthesized as (f(x)) / 2 when rendered. This is a great feature, which should be extended to factorials: currently, n! / 2 is implicitly parenthesized as n (! / 2), which is very likely not to be what the user wants.
n! / 2 is rendered as

but I expected

Workaround
The current workaround is to add explicit parentheses: (n!) / 2.
Reproduction URL
No response
Operating system
No response
Typst version

[X] I am using the latest version of Typst

As someone who has faced this before, I agree this would be very nice to have in general, as this usage of fractions is very common in the math world (though I have no idea how feasible it is to implement).

I have no idea how feasible it is to implement

I don't know much about the compiler internals either, but a similar effect has already been achieved for function-like stuff: f(x) / y is parenthesized as (f(x)) / y, but f (x) / y is parenthesized as f ((x) / y).

I’ll take a look at this.


runtime: idle GC interferes with auto-scaling

What version of Go are you using (go version)?

$ go version
go version go1.14 linux/amd64

But this has been true for years.
What did you do?
Run a mostly-idle application in a container with CPU limits under a mechanism that monitors CPU use and increases the job's CPU reservation if it appears to be too little. Specifically, this was observed with a latency-sensitive policy that looked at high percentile usage sampled over a short time period.
What did you expect to see?
Since the application is mostly idle, a small CPU reservation should be adequate and the auto-scaler should not need to grow that reservation.
What did you see instead?
Because the garbage collector attempts to use any idle cores up to GOMAXPROCS, even an otherwise mostly idle application will see periodic spikes of CPU activity. These will happen at least every 2 minutes if not more frequently. In this case, the auto-scaler's policy was sensitive enough that these spikes caused it to grow the job's CPU reservation. However, then the garbage collector uses all of the new CPU reservation. This leads to a feedback cycle where the auto-scaler continually grows the reservation.
See also #17969, https://github.com/golang/go/issues/14812#issuecomment-518902192.
/cc @mknyszek
Thoughts
We've been thinking for a while now that idle GC may be more trouble than it's worth. The idea was to speed up the mark phase, so the write barrier is on for less time and we allocate black for less time. However, if an application is mostly idle, then it's not very sensitive to the (very small) performance impact of the write barrier and probably doesn't produce much floating garbage from allocate-black; and if an application isn't mostly idle, then it's not benefiting from idle GC anyway.

Out of curiosity I looked up when we started doing a GC every two minutes.  It was introduced in  https://golang.org/cl/5451057, a CL whose purpose was to release unused memory to the operating system.  The specific suggestion to ensure that a GC is run at least once every two minutes was https://codereview.appspot.com/5451057/#msg14.
Of course the garbage collector is very different now than it was in 2012.  But it does seem valid to consider whether an idle program will eventually release unused memory to the operating system.

Or we could monitor how much was released to the OS in a GC at N minutes that recovered R memory, and if it was not "enough", then delay next GC till either 2N minutes pass or 2R bytes allocated (or the GOGC threshold is hit).  Reset this policy after periods of rapid allocation, and perhaps, start at a smaller number of minutes than 2.
This might have a poor interaction with finalizers in programs that relied on them being even vaguely timely.

Regarding the autoscaler, I am not entirely sure that this will seal the deal for them.  Once upon a time I wrote an all-singing-all-dancing implementation of CRC32 for Java, that would use fork-join parallelism from the system pool to make CRC run faster (CRCs are somewhat embarrassingly parallel, the combine step requires a little work but not tons).  I went so far as to demonstrate superlinear speedup.  This did not get checked in, because the Java library team was apparently too nervous about people actually using fork-join parallelism in libraries, even though it was there for all the Collections stuff.  My attitude was (and remains) "there is no such thing as unexpected parallelism in this millennium, and if a user doesn't want it to happen, they can size the system fork join pool to what they want, that's what it's there for".  And of course, pay no attention to that multithreaded same-address-space optimizing compiler behind the curtain.  But no dice, then.
My opinion is that if you don't want a process using more than N cores, that is what GOMAXPROCS is for, set it to the number that you want.  An autotuning algorithm that gives you more cores after you use all the cores it told you you could use, is broken, especially now.  We should not be surprised if people start using all the cores they can to handle embarrassingly parallel problems.

There's a difference between bulk computational tasks (where you can expect them to use what you give them) and demand-driven tasks (which will not use it, and if they're using it they might need more). Autoscalers are designed to respond to the latter type. But idle GC that uses easily 10x the CPU of the task's recent 1 minute usage completely throws off that assumption -- there's no way to tell the difference between "task is hammered with demand" and "task is doing a random GC".

But it does seem valid to consider whether an idle program will eventually release unused memory to the operating system.

:100: I think it would be a mistake to not let idle programs eventually return unused memory.

there's no way to tell the difference between "task is hammered with demand" and "task is doing a random GC"

Random suggestion: expose an expvar that tracks inflight real work (e.g. number of "real work" requests being currently served) and inhibit autoscaling if that metric is 0.

Alternatively, since idle GC isn't triggered by any real memory pressure, run it single-threaded?

Oops.
I want to clarify that I didn't mean the two minute GC. That also has some downsides, but I think the benefits outweigh the costs.
I was talking about how the garbage collector schedules GC work during idle time on every GC cycle. This is what interferes with autoscaling.

I
see, then IIUC what you mean then  https://github.com/golang/go/issues/14812#issuecomment-518902192 can also be considered as a reason to fix this.

It’s not just the write barrier and allocating black,the GC needs to race
to a state where it isn’t trashing the caches and causing mutators to take
capacity misses.
The problem of having multiple schedulers, each thinking they are
omnipotent, is as fascinating as it is a hard research problem. If the
autoscaler has access to various HW monitors perhaps they could be used to
discriminate whether the demand increase is caused by the GC or by the
mutators. It feels like a problem for machine learning using the GC logs to
automate training.
Finally, I suspect Java and other GC languages have similar problems, does
the autoscalor have this problem with Java and if not what can be learned.
On Fri, Jul 3, 2020 at 6:56 PM Carlo Alberto Ferraris <
<EMAIL_ADDRESS>wrote:

I see, then IIUC what you mean then #14812 (comment)
https://github.com/golang/go/issues/14812#issuecomment-518902192 can
also be considered as a reason to fix this.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/39983#issuecomment-653691821, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHNNH7MSXBTKMUE2HS3YXTRZZO3DANCNFSM4OOCANKA
.

Java's GC is heavily tunable. One could f.ex. restrict the number of threads it runs on.

I see, IIUC what you mean then #14812 (comment) (GC causing ~100ms latency spikes when running in containers with CPU limits) can also be considered as an additional argument in favor of fixing this.

@CAFxX , yep! (Thanks for that cross-reference, I've added it to the top post.)

In the short run, how would autoscalers respond if GC limited it's "looks like nobody's using those cores" resource consumption to min(idle/2, idle-1)?  So for example, a single-threaded app, on a 2-core box, would leave the 2nd core alone and do 25% time-slicing against the mutator in one core.
3 and 4 cores -> GC takes 100% of one idle core (leaving 1 or 2 still idle)
5, 6 -> 2 (leaving 2 or 3 still idle)
(alternate formula: 1 + idle/3, which would use the second core for the 1-busy-1-idle case).
This doesn't mean the cores are actually idle, if there are other processes or if the OS decides it has important work to do, perhaps induced by GC activity.
Another possibility is capping the idle parallelism; have we measured how much marginal returns diminish as the number of cores devoted to GC increases?  For the CRC example above, it turned out that 4 cores was very much a sweet spot; speedup fell into the almost-linear to superlinear range.
(I still think autoscalers will need to cope more gracefully with the existence of embarrassingly parallel subproblems.  Clock rates are stuck, people will look for these.  It would be nice if the OS/autoscaler had some way to communicate the "cost" of an extra core.  Otherwise, sure the marginal returns per core are falling, but it's "my" core and it's "idle", so why not use it? )

Limiting idle GC is certainly a possibility. In the past we've talked about letting one P enter scheduler idle even if GC is running so that there's a P to quickly wake up and also to block in netpoll (though if you do wake it up, do you have to shut down idle GC running on another P to keep a spare P?).
It's actually been a very long time since we've measured the scalability of the garbage collector. It certainly has limits. I suspect they're high enough that they're significantly higher than a mostly-idle latency-sensitive application is likely to use on its own, but at least it would cap out the feedback cycle.

Circa 2002 when Intel first introduced hyperthreading (SMT) I was asked to
find ways to use this extra underutilized hyperthread. I rewrote Cheney
scan to use the extra hyperthread to effectively prefetch the targets of
objects some distance ahead of the scan pointer. Seemed like a good idea at
the time but was a loser due to limited memory bandwidth. Perhaps the Go GC
is also memory bandwidth limited. If so then limiting the CPUs the GC gets
based on available bandwidth is a win.
On Mon, Jul 6, 2020 at 12:22 PM Austin Clements<EMAIL_ADDRESS>wrote:

Limiting idle GC is certainly a possibility. In the past we've talked
about letting one P enter scheduler idle even if GC is running so that
there's a P to quickly wake up and also to block in netpoll (though if you
do wake it up, do you have to shut down idle GC running on another P to
keep a spare P?).
It's actually been a very long time since we've measured the scalability
of the garbage collector. It certainly has limits. I suspect they're high
enough that they're significantly higher than a mostly-idle
latency-sensitive application is likely to use on its own, but at least it
would cap out the feedback cycle.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/39983#issuecomment-654336486, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHNNH4GMBMESJFRNCHTMWLR2H25DANCNFSM4OOCANKA
.

This may be a naive question but here goes anyway: wouldn't it be ideal to have the idle GC have its own pacer, so that it can be throttled up/down to finish roughly when the next GC cycle is expected to start, as to avoid as much as possible any spiky behavior that we know can cause issues with autoscalers, cpu quotas, and latency in general?

A naive question that I have also asked, so I know some of the answer.  Running the garbage collector has additional costs above and beyond the work of garbage collection;

memory is "allocated black" during garbage collection, meaning already marked which adds to the size of the live set at the end of GC.
any writes to pointers must also process a write barrier, which slows down the application in general.
the GC is thought to be generally disruptive of otherwise useful processing; it tends to trash caches and use a lot of memory bandwidth.

From the point of view of energy efficiency, it is believed (with some historical evidence) that the "best" way to collect garbage is as quickly as possible, subject to constraints of letting the mutator get its job done.  When I've raised the question of "does the GC's intermittent 25% cpu tax require a 33% container overprovision to ensure that latency/throughput goals are met?", the answer has been that in any large (multiple containers handling requests) service, this is not that different from variations in service load over time, variable request sizes, etc.  Stuff happens, loads get balanced.  And, this is probably fair, anyone running a single-node service probably has to overprovision anyway because reasons, and how much could a single node cost, anyway?

The Go 1.5 Concurrent GC Pacing
https://docs.google.com/document/d/1wmjrocXIWTr1JxU-3EQBI6BK6KgtiFArkG47XK73xIQ/edit
document
does a good job of explaining the GC pacer.
On Mon, Jul 6, 2020 at 6:24 PM David Chase<EMAIL_ADDRESS>wrote:

A naive question that I have also asked, so I know some of the answer.
Running the garbage collector has additional costs above and beyond the
work of garbage collection;

memory is "allocated black" during garbage collection, meaning
already marked which adds to the size of the live set at the end of GC.
any writes to pointers must also process a write barrier, which
slows down the application in general.
the GC is thought to be generally disruptive of otherwise useful
processing; it tends to trash caches and use a lot of memory bandwidth.

From the point of view of energy efficiency, it is believed (with some
historical evidence) that the "best" way to collect garbage is as quickly
as possible, subject to constraints of letting the mutator get its job
done. When I've raised the question of "does the GC's intermittent 25% cpu
tax require a 33% container overprovision to ensure that latency/throughput
goals are met?", the answer has been that in any large (multiple containers
handling requests) service, this is not that different from variations in
service load over time, variable request sizes, etc. Stuff happens, loads
get balanced. And, this is probably fair, anyone running a single-node
service probably has to overprovision anyway because reasons, and how much
could a single node cost, anyway?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/39983#issuecomment-654494750, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHNNH64KJ2UU5RYUEYEUMDR2JFJFANCNFSM4OOCANKA
.

@mknyszek  Does https://go-review.googlesource.com/c/go/+/393394/ fixes this issue?

I think it addresses the issue in the circumstance that matters most, i.e. idle applications. Theoretically an application that is idle enough to say, GC every minute, but not every 2 minutes, is probably going to have problems. That's a cliff which would still be nice to fix, so I'm inclined to leave this open.
I'm not sure we can justify removing the idle mark workers at this point. As I've noted on other issues, it seems to cost about +1% latency and -1% throughput in most situations where the application is active.


fn parse_frame_size: Cleanup and make mostly safe

The only remaining unsafety is rav1d_get_bit(s), which I'll do soon, and Rav1dPicture::frame_hdr, which will be Arced.

This is too far removed from the original C code. Why? All you needed here was to replace the pointer usage with references. Most of this PR is changes that reorganize the code, when it was already clean and effectively identical to the original C.

Which commits?  Do you mean 2e9c2e3, 2c5dc3e, or any of the others ones?  I didn't think they were that big changes, as most of the diff was just moving code/indentation around.

Most of the commits, but especially https://github.com/memorysafety/rav1d/commit/2e9c2e323d4e5e118be8db571a0859013be1ab85 and https://github.com/memorysafety/rav1d/commit/2c5dc3e9e645a837763bd7697691a0f6df4de0ce, here will make it harder to backport changes from upstream dav1d, and don't improve memory safety. We should be making the minimal edits necessary to get to safe Rust without diverging too much from upstream where we don't need to. Of course we want things to be readable, but we should not be trying to improve on the upstream C code readability or make things more idiomatic unless the original was unreadable.

I didn't think they were that big changes, as most of the diff was just moving code/indentation around.
Moving code/indentation are the biggest changes in terms of diffs and divergence from upstream. If it's necessary, that's one thing, but where it's not necessary we should try to avoid it.

Most of the commits, but especially 2e9c2e3 and 2c5dc3e, here will make it harder to backport changes from upstream dav1d, and don't improve memory safety. We should be making the minimal edits necessary to get to safe Rust without diverging too much from upstream where we don't need to. Of course we want things to be readable, but we should not be trying to improve on the upstream C code readability or make things more idiomatic unless the original was unreadable.

Did our general aims change?  I know we're focusing on more strictly memory safety now, but it's generally been a future goal to make things more idiomatic Rust and to keep things performant (usually the idiomatic way in Rust, e.x. iterators, is more performant).  Even with performance not the top top concern anymore (after safety), it's still quite important, so I've been converting things to iterators where that's simple (like here).  Also, for this part of the code specifically, I don't imagine there'd be many significant changes since the bitstream is frozen.

https://www.memorysafety.org/initiative/av1/

Milestones 1-4 of our work plan are funded.

Migrate block decoding
[...]As soon as it is possible, we will change types to be safe and idiomatic.[...]

I've removed the 2e9c2e3 and 2c5dc3e commits; the remaining ones are small and mostly around removing &muts and stuff.


Change latestExecutionSummary to executionSummary

https://github.com/microsoft/vscode/issues/93265#issuecomment-839538242

[ ] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[ ] Title summarizes what is changing.
[ ] Has a news entry file (remember to thank yourself!).
[ ] Appropriate comments and documentation strings in the code.
[ ] Has sufficient logging.
[ ] Has telemetry for enhancements.
[ ] Unit tests & system/integration tests are added/updated.
[ ] Test plan is updated as appropriate.
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed).

Test will fail as this is a breaking API change.

Codecov Report

Merging #5863 (ed3cfc4) into main (2a1dca2) will decrease coverage by 0%.
The diff coverage is 0%.

@@          Coverage Diff           @@
##            main   #5863    +/-   ##
======================================
- Coverage     69%     69%    -1%
======================================
  Files        403     403
  Lines      26962   26962
  Branches    3935    3935
======================================
- Hits       18815   18647   -168
- Misses      6512    6680   +168
  Partials    1635    1635

Impacted Files
Coverage Δ

...lient/datascience/jupyter/kernels/cellExecution.ts
40% <0%> (ø)

src/client/datascience/notebook/helpers/helpers.ts
58% <ø> (+2%)
:arrow_up:

src/client/datascience/utils.ts
63% <ø> (ø)

...lient/datascience/variablesView/notebookWatcher.ts
60% <0%> (-29%)
:arrow_down:

...ience/variablesView/variableViewMessageListener.ts
22% <0%> (-78%)
:arrow_down:

...ent/common/application/webviewViews/webviewView.ts
14% <0%> (-72%)
:arrow_down:

...c/client/datascience/variablesView/variableView.ts
18% <0%> (-58%)
:arrow_down:

src/client/datascience/webviews/webviewViewHost.ts
19% <0%> (-53%)
:arrow_down:

...t/datascience/jupyter/jupyterInvalidKernelError.ts
66% <0%> (-34%)
:arrow_down:

... and 19 more


Adds changes on behalf of author KeithRettig

We can close this PR.  All my edits got added to HIP82 already.


Revert "Updates PoolResponse from block header to PoSW proof"

Reverts AleoHQ/snarkOS#1527
Reverting for a precautionary measure with Cargo.

This PR has been unreverted on testnet2.
The issue was caused by a bug in how Cargo indexes branches for a git dependency. It has been resolved manually on our end.


Fix invalid scaladoc links which cannot be found (#353)

Refs #353
I fixed invalid scaladoc links.

Add enough package name
Fix invalid syntax of links to a method

@ydash thanks, this is epic, but the changeset is large than I expected, will import these classes directly reduce the lines of change?

Probably, it's not possible.
If you import classes which are used in only scaladoc link, following compile error is appeared:
[error] /path/actor/src/main/scala/org/apache/pekko/actor/Scheduler.scala:16:18: Unused import
[error] Applicable -Wconf / @nowarn filters for this fatal warning: msg=<part of the message>, cat=unused-imports, site=org.apache.pekko.actor
[error] import java.lang.IllegalArgumentException
[error]                  ^
[error] one error found
[error] (actor / Compile / compileIncremental) Compilation failed

@ydash I think that should be a bug in Scaladoc, because in Java, we can do it. would you like to report it scala/bug ?

@He-Pin You mean it is a bug that failures of linking to classes under java.lang package without the java.lang. prefix?

@He-Pin You mean it is a bug that failures of linking to classes under java.lang package without the java.lang. prefix?

Yes @ydash this is what is being requested. Scaladoc should not require us to hack the scaladoc like you are doing in this PR.

@ydash If you don't have time, I will openup an issue in scala/bug.

@ydash @He-Pin this change is the cause of #687 - I don't know if reverting some parts of this will be enough or if we would be better off doing a full revert and starting again.
Scaladoc has so many bugs that it may not be worth our while trying to improve it.


swag init generates empty paths/routes with v1.8.3 onwards

Describe the bug
Not able to generate swagger files for my project. Tried swag init --parseDependency -g main.go as well. Still the same.
Only these lines are outputted in the console.
create docs.go at docs/docs.go
create swagger.json at docs/swagger.json
create swagger.yaml at docs/swagger.yaml

It works fine with version v1.8.2 and below.
Your swag version
swag v1.8.3 and onwards
Your go version
Go 1.19.3

Same problem here.
Project structure:
project
|-- cmd
|    |-- server
|        |-- main.go
|-- server
|-- server.go
main function is importing a StartServer function from the server package, where the router is settled.
The question is: how swaggo is parsing the server endpoints?

Same problem here.
Project structure:
project |-- cmd | |-- server | |-- main.go |-- server |-- server.go
main function is importing a StartServer function from the server package, where the router is settled.
The question is: how swaggo is parsing the server endpoints?

swag init -g ./cmd/main.go -d ./server

Same problem here.
Project structure:
project |-- cmd | |-- server | |-- main.go |-- server |-- server.go
main function is importing a StartServer function from the server package, where the router is settled.
The question is: how swaggo is parsing the server endpoints?

swag init -g ./cmd/main.go -d ./server

That doesn't work either swag init -g ./cmd/server/main.go -d ./server
Got this error:
2023/07/17 21:03:17 Generate swagger docs....
2023/07/17 21:03:17 Generate general API Info, search dir:./server
2023/07/17 21:03:17 cannot parse source files /home/axelr/go-projects/swagger-chi-playground/server/cmd/server/main.go: open /home/axelr/go-projects/swagger-chi-playground/server/cmd/server/main.go: no such file or directory

The resolution of the folder structure is incorrect.

Same issue here, project structure :
├── README.md
├── controllers
│   ├── bozo-coin.go
│   ├── controller.go
│   ├── default-route.go
│   └── user.go
├── docs
│   ├── docs.go
│   ├── swagger.json
│   └── swagger.yaml
├── go.mod
├── go.sum
├── license
├── main.go
├── metrics
│   ├── bozo-coin.go
│   └── metrics.go
├── models
│   ├── bozo-coin.go
│   ├── models.go
│   └── user.go
└── utils
    ├── db-connection.go
    ├── error.go
    └── message.go

Go version : 1.18.10
Swag version 1.8.10
Output json :
{
    "swagger": "2.0",
    "info": {
        "description": "A Bozo coin management service API in Go using Gin framework, storing data in PostgreSQL and using Prometheus for metrics.",
        "title": "Bozo API",
        "contact": {
            "name": "Bozo Support",
            "url": "https://danstonkube.fr",
            "email"<EMAIL_ADDRESS>        },
        "license": {
            "name": "Apache 2.0",
            "url": "http://www.apache.org/licenses/LICENSE-2.0.html"
        },
        "version": "1.0"
    },
    "basePath": "/api/v1",
    "paths": {}
}

Obtained by running :
swag init --pd -g main.go

In my case empty paths were due to runtime.GOROOT() producting an empty string (and, I believe, since swag ignores all paths with runtime.GOROOT() prefix, it ignored all of them).
The reason runtime.GOROOT() would be empty could be b/c of the way swag is built. In my case it was a nix package, with this issue: https://github.com/NixOS/nixpkgs/issues/224701

I am adding more context b/c it could be related :
$~: swag init --pd
2023/07/27 14:22:36 Generate swagger docs....
2023/07/27 14:22:36 Generate general API Info, search dir:./
2023/07/27 14:22:38 warning: failed to evaluate const locb at /Users/panz/go/1.18.10/pkg/mod/github.com/pelletier/go-toml/v2@v2.0.8/internal/characters/utf8.go:183:2, strconv.ParseUint: parsing "b10000000": invalid syntax
2023/07/27 14:22:38 warning: failed to evaluate const hicb at /Users/panz/go/1.18.10/pkg/mod/github.com/pelletier/go-toml/v2@v2.0.8/internal/characters/utf8.go:184:2, strconv.ParseUint: parsing "b10111111": invalid syntax
2023/07/27 14:22:40 create docs.go at docs/docs.go
2023/07/27 14:22:40 create swagger.json at docs/swagger.json
2023/07/27 14:22:40 create swagger.yaml at docs/swagger.yaml

Issue on this repo

Any updates?

I have this issue as well, the paths block is empty, even though I've added a section to (minimally) describe it:

// handleNewToken godoc
// @Summary Create New Token
// @ID new-token
// @Accept json
// @Produce json
// @Success 200
// @Failure 404
// @Router /newToken [post]
func handleNewToken(s *Server) http.HandlerFunc {

The title and version info are created in the generated swagger.json, but the paths entry is empty.
My GoRoot is set (/usr/local/go) and this application is not in that path, so it should not be skipped.
I do also get the invalid syntax that I see some other folks posting when I run with --pd:

swag init --pd
2023/08/09 12:18:21 Generate swagger docs....
2023/08/09 12:18:21 Generate general API Info, search dir:./
2023/08/09 12:18:22 warning: failed to evaluate const locb at /home/abc/gocode/pkg/mod/github.com/pelletier/go-toml/v2@v2.0.6/internal/characters/utf8.go:183:2, strconv.ParseUint: parsing "b10000000": invalid syntax
2023/08/09 12:18:22 warning: failed to evaluate const hicb at /home/abc/gocode/pkg/mod/github.com/pelletier/go-toml/v2@v2.0.6/internal/characters/utf8.go:184:2, strconv.ParseUint: parsing "b10111111": invalid syntax
2023/08/09 12:18:22 create docs.go at docs/docs.go
2023/08/09 12:18:22 create swagger.json at docs/swagger.json
2023/08/09 12:18:22 create swagger.yaml at docs/swagger.yaml

Posting an update since I somehow figured how to generate documentation, it seems that including my controller directory and persist dependencies affected swag's behavior :
❯ swag init -g main.go --pd -d ./,./controllers
2023/08/17 14:36:38 Generate swagger docs....
2023/08/17 14:36:38 Generate general API Info, search dir:./
2023/08/17 14:36:38 Generate general API Info, search dir:./controllers
2023/08/17 14:36:40 warning: failed to evaluate const locb at /Users/panz/go/1.20.1/pkg/mod/github.com/pelletier/go-toml/v2@v2.0.8/internal/characters/utf8.go:183:2, strconv.ParseUint: parsing "b10000000": invalid syntax
2023/08/17 14:36:40 warning: failed to evaluate const hicb at /Users/panz/go/1.20.1/pkg/mod/github.com/pelletier/go-toml/v2@v2.0.8/internal/characters/utf8.go:184:2, strconv.ParseUint: parsing "b10111111": invalid syntax
2023/08/17 14:36:40 Generating utils.HTTPError
2023/08/17 14:36:40 Generating controllers.FindBozoCoinResponse
2023/08/17 14:36:40 Generating models.BozoCoin
2023/08/17 14:36:40 Generating gorm.Model
2023/08/17 14:36:40 Generating gorm.DeletedAt
2023/08/17 14:36:40 Generating sql.NullTime
2023/08/17 14:36:40 Generating utils.Message
2023/08/17 14:36:40 Generating models.CreateBozoCoinInput
2023/08/17 14:36:40 Generating controllers.CreateBozoCoinResponse
2023/08/17 14:36:40 Generating models.DeleteBozoCoinInput
2023/08/17 14:36:40 Generating controllers.DeleteBozoCoinResponse
2023/08/17 14:36:40 Generating controllers.FindGroupsResponse
2023/08/17 14:36:40 Generating models.Group
2023/08/17 14:36:40 Generating models.User
2023/08/17 14:36:40 Generating models.ReverseBozoCoin
2023/08/17 14:36:40 Generating models.UserAchievement
2023/08/17 14:36:40 Generating models.CreateGroupInput
2023/08/17 14:36:40 Generating controllers.CreateGroupResponse
2023/08/17 14:36:40 Generating controllers.DeleteGroupResponse
2023/08/17 14:36:40 Generating controllers.LivenessResponse
2023/08/17 14:36:40 Generating models.AdminUserLoginInput
2023/08/17 14:36:40 Generating controllers.LoginResponse
2023/08/17 14:36:40 Generating controllers.ReadinessResponse
2023/08/17 14:36:40 Generating controllers.FindReverseBozoCoinResponse
2023/08/17 14:36:40 Generating models.CreateReverseBozoCoinInput
2023/08/17 14:36:40 Generating controllers.CreateReverseBozoCoinResponse
2023/08/17 14:36:40 Generating models.DeleteReverseBozoCoinInput
2023/08/17 14:36:40 Generating controllers.DeleteReverseBozoCoinResponse
2023/08/17 14:36:40 Generating controllers.FindUsersResponse
2023/08/17 14:36:40 Generating models.CreateUserInput
2023/08/17 14:36:40 Generating controllers.CreateUserResponse
2023/08/17 14:36:40 Generating controllers.DeleteUserResponse
2023/08/17 14:36:40 create docs.go at docs/docs.go
2023/08/17 14:36:40 create swagger.json at docs/swagger.json
2023/08/17 14:36:40 create swagger.yaml at docs/swagger.yaml

This warning may be irrelevent warning: failed to evaluate const locb at /Users/panz/go/1.20.1/pkg/mod/github.com/pelletier/go-toml/v2@v2.0.8/internal/characters/utf8.go:183:2, strconv.ParseUint: parsing "b10000000": invalid syntax
Sample controller func :
type FindGroupsResponse struct {
	Data []models.Group `json:"data"`
}

// FindGroups godoc
//
//	@Summary		Find Groups
//	@Description	Retrieve a list of all groups along with their associated users.
//	@Tags			Groups
//	@Accept			json
//	@Produce		json
//	@Success		200	{object}	FindGroupsResponse
//	@Failure		400	{object}	utils.HTTPError
//	@Failure		500	{object}	utils.HTTPError
//	@Router			/groups [get]
func (c *Controller) FindGroups(ctx *gin.Context) {
	var groups []models.Group
	if err := c.Database.Preload("Users").Find(&groups).Error; err != nil {
		utils.NewError(ctx, 500, err)
		return
	}

	// Append Group data to to FindGroupsResponse
	var response FindGroupsResponse
	response.Data = groups

	// Return group data
	ctx.JSON(200, response)
}

Same issue here, project structure :
├── README.md
├── controllers
│   ├── bozo-coin.go
│   ├── controller.go
│   ├── default-route.go
│   └── user.go
├── docs
│   ├── docs.go
│   ├── swagger.json
│   └── swagger.yaml
├── go.mod
├── go.sum
├── license
├── main.go
├── metrics
│   ├── bozo-coin.go
│   └── metrics.go
├── models
│   ├── bozo-coin.go
│   ├── models.go
│   └── user.go
└── utils
    ├── db-connection.go
    ├── error.go
    └── message.go

Go version : 1.18.10 (also tried in 1.20.1 and 1.17.10) Swag version 1.8.10
Output json :
{
    "swagger": "2.0",
    "info": {
        "description": "A Bozo coin management service API in Go using Gin framework, storing data in PostgreSQL and using Prometheus for metrics.",
        "title": "Bozo API",
        "contact": {
            "name": "Bozo Support",
            "url": "https://danstonkube.fr",
            "email"<EMAIL_ADDRESS>        },
        "license": {
            "name": "Apache 2.0",
            "url": "http://www.apache.org/licenses/LICENSE-2.0.html"
        },
        "version": "1.0"
    },
    "basePath": "/api/v1",
    "paths": {}
}

Obtained by running :
swag init --pd -g main.go

I have the same problem

Mitrate to version 1.7.0
Work to me

2023/08/17 14:35:10 Generate swagger docs....
2023/08/17 14:35:10 Generate general API Info, search dir:./
2023/08/17 14:35:11 Generating model.PayLoadData
2023/08/17 14:35:11 create docs.go at docs/docs.go
2023/08/17 14:35:11 create swagger.json at docs/swagger.json
2023/08/17 14:35:11 create swagger.yaml at docs/swagger.yaml

go clean -i github.com/swaggo/swag/cmd/swag
go install<EMAIL_ADDRESS>

Mitrate to version 1.7.0
Work to me

2023/08/17 14:35:10 Generate swagger docs....
2023/08/17 14:35:10 Generate general API Info, search dir:./
2023/08/17 14:35:11 Generating model.PayLoadData
2023/08/17 14:35:11 create docs.go at docs/docs.go
2023/08/17 14:35:11 create swagger.json at docs/swagger.json
2023/08/17 14:35:11 create swagger.yaml at docs/swagger.yaml

go clean -i github.com/swaggo/swag/cmd/swag go install<EMAIL_ADDRESS>
Mine works if I downgrade to v1.8.2 or less. But v1.8.3 onwards the swag build time is improved. The point is to able to use the latest versions.

I think I was running into a similar thing and it turned out that I was adding an extra space or newline in between my doc comments and my function definition. at least for me and just posting in case this helps

迁移到版本1.7.0
为我工作

2023/08/17 14:35:10 生成 swagger 文档....
2023/08/17 14:35:10 生成通用 API 信息，搜索目录：./
2023/08/17 14:35:11 生成模型。 PayLoadData
2023/08/17 14:35:11 在 docs/docs.go 创建 docs.go
2023/08/17 14:35:11 在 docs/swagger.json
2023/08/17 14:35 创建 swagger.json： 11 在 docs/swagger.yaml 创建 swagger.yaml

go clean -i github.com/swaggo/swag/cmd/swag go install<EMAIL_ADDRESS>
如果我降级到 v1.8.2 或更低版本，我的可以工作。但从 v1.8.3 开始，swag 构建时间得到了改进。重点是能够使用最新版本。

I encountered the same problem, and when I introduced the vendor dependency in main.go, the generation speed changed from one minute to one second.

Mitrate to version 1.7.0
Work to me

2023/08/17 14:35:10 Generate swagger docs....
2023/08/17 14:35:10 Generate general API Info, search dir:./
2023/08/17 14:35:11 Generating model.PayLoadData
2023/08/17 14:35:11 create docs.go at docs/docs.go
2023/08/17 14:35:11 create swagger.json at docs/swagger.json
2023/08/17 14:35:11 create swagger.yaml at docs/swagger.yaml

go clean -i github.com/swaggo/swag/cmd/swag go install<EMAIL_ADDRESS>
Mine works if I downgrade to v1.8.2 or less. But v1.8.3 onwards the swag build time is improved. The point is to able to use the latest versions.

I encountered the same problem, and when I introduced the vendor dependency in main.go, the generation speed changed from one minute to one second.

In my case empty paths were due to runtime.GOROOT() producting an empty string (and, I believe, since swag ignores all paths with runtime.GOROOT() prefix, it ignored all of them). The reason runtime.GOROOT() would be empty could be b/c of the way swag is built. In my case it was a nix package, with this issue: NixOS/nixpkgs#224701

I'm using go-swag from nixpkgs and I had the same problem, as a workaround I'm invoking swag with:
(source <(go env) && swag init)

in my Makefile.

Same at my end with 1.16.3.
Is there any solution to it? I am using the go-chi router.
Thanks


Fix environment block creation

Summary of the Pull Request
This fixes a regression in environment variable loading introduced as part of the new environment block creation that prevents some system-defined, volatile environment variables from being defined.
References
https://github.com/microsoft/terminal/pull/7243#discussion_r476603599
PR Checklist

[x] Closes #7399
[x] CLA signed. If not, go over here and sign the CLA
[x] Tests added/passed - manually verified
[ ] Documentation updated. If checked, please file a pull request on our docs repo and link it here: #xxx
[ ] Schema updated.
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Validation Steps Performed
Manually verified locally.

@msftbot merge this in 10 minutes


Documentation for Number Insight in README

We've got one for Ruby, we should have one for Python.

@timcraft @judy2k done.


Image Processing

I think Still should solve the hardest parts of building a website out of the box. Dealing with images on the web isn't simple: you need multiple sizes, the right "srcset" attributes, lazy loading, etc. Gatsby is the only framework I've used that does it right and I think we should draw some inspiration from it. Here's what we need to do:

resize large images to the necessary sizes.
generate smaller images to be used by devices with smaller screens or resolution.
optimize images.
lazy-loading.

In gatsby, they distinguish between fluid and fixed images. You use fixed images when you know the image's width and height and you only need to change images based on the screen resolution. I propose we start with two functions:
<div>
  <%= fluid_image "banner.png", max_width: "1000px", alt: "Something", class: "Image" %>
  <%= fixed_image "banner.png", width: "1000px", alt: "Something", id: "#banner" %>
</div>

We'll need to write a preprocessor, two view helpers, and maybe change the SourceFile module to allow for the attributes.
@naps62 gatsby uses https://github.com/libvips/libvips because:

Resizing an image is typically 4x-5x faster than using the quickest ImageMagick and GraphicsMagick settings due to its use of libvips.

Source. What do you think?

@gabrielpoca rust comes in and says: "hold my beer, vips"
https://github.com/imazen/imageflow
comparison between imageflow, vips and imagemagick:

Nice! I can't find any bindings, I guess it's time for rustler?

I guess, yes

This can be closed, right? @gabrielpoca - we already have rudimentary image processing

This can be closed, right? @gabrielpoca - we already have rudimentary image processing

Yap

Yap


[BUG] - transaction build does not balance correctly when the certificate is already submitted

Internal/External
Internal   if an IOHK staff member.
Area
Other   Any other topic (Delegation, Ranking, ...).

Expected behavior
The tx should be already correctly balanced.
System info (please complete the following information):

OS Name: Ubuntu

$ cardano-cli --version
cardano-cli 1.28.0 - linux-x86_64 - ghc-8.10
git rev 708de685d49ec6af4b2d8b3cbfa0eca0e9e43edf

$ cardano-node --version
cardano-node 1.28.0 - linux-x86_64 - ghc-8.10
git rev 708de685d49ec6af4b2d8b3cbfa0eca0e9e43edf

Thats not an error of the application, thats an user error 😄
Behavior was always this way, if there is already a pool registered, you don't have to pay the 500 ada registration fee again. In that case just send the new certificate but reduce the amount to send with the poolRegistrationFee of 500 ada.

We suspect that the cause of this bug is that the cli is currently passing an empty set of pool ids rather. To do this properly will require querying the current set of pool ids and passing them in place of the empty set.

Related #3101

Fixed in: https://github.com/input-output-hk/cardano-node/pull/3176


Feedback for “Install Memgraph on Ubuntu”

Memgraph cannot be installed on Ubuntu.  Looks like the product is not reliable since there is absolutely no documentation available to install this on Ubuntu.

Hi @datapoesy, is this documentation not working for you? Can you please tell me what exactly is not working?
Here is the download hub to download Memgraph for Ubuntu: https://memgraph.com/download

Hi, I got it running  on a vm with higher system configuration.  My initial attempts were on a 2 Core 4GB machine.  It would be great to mention system requirements in the documentation.
It works for me now.  Very much appreciate your quick response; very much reassuring.  I am closing this ticket
Thanks again.

Hi @datapoesy, thank you for the feedback, we will definitely work on improving that. Until then, I hope our FAQ can help.
If you have more questions, you can join our Discord server of book an office hours call.


Animate appearing if needed

I was asked to animate from placeholder to loaded image so I see no other way to do it without changing WebView code. Usage could be like this:
WebImage(url: url)
    .placeholder {
        ...
    }
    .resizable()
    .shouldAnimateAppearanceOnSuccess(perform: { _, _, cacheType in
        return cacheType.shouldAnimateAppearance
    })

public extension SDImageCacheType {
    var shouldAnimateAppearance: Bool {
        switch self {
        case .none, .disk:
            return true
        default:
            return false
        }
    }
}

What's your mean animate from placeholder to loaded image
Actually, the placeholder and final loaded image, is Different View Identity. So the automatic animation provided by SwiftUI can only show the fade-in/fade-out animation
See more: https://developer.apple.com/videos/play/wwdc2021/10022/


Added Russian translation

My humble translation into Russian.
I don't know how you can check the modal window with the "additionalInfo" button, perhaps "Дополнительная информация" takes up a lot of space, then you can then replace it with "Доп. инфа" for compactness
for native speakers:
"Custom CSS" пока не стал трогать, но думаю можно перевести как "Свой/Ваш CSS" ?
"Emotes" вообще нету идей как переводить, думаю пусть так и будет ? перевод как "Эмоции" мне кажется не очень

Hi I appreciate you going out of your way to add russian translations, I do have to warn you though that the strings are still rather volatile while development is active. We hope to use a crowd-translation tool to make this easier for both sides.

@rauenzi I was working on a PR for another language but just saw your comment on this. Does this mean I should just drop the PR and wait for further developments on the crown-translation front?

@lunabunn @userXinos You can add your translations through POEditor by joining here https://poeditor.com/join/project?hash=nRljcnV0ET this is the recommended way now. You will also be able to check periodically in case there are new strings added as BD adds new features.


Add release info for v0.41.1

This commit adds links to docs, examples, and the release tag for v0.41.1.
/kind documentation
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[x] Has Docs included if any changes are user facing
n/a Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
n/a Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
n/a Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
NONE

/retest


Improved polyglot Date support

Pull Request Description
Significantly improves the polyglot Date support (as introduced by #3374). It enhances the Date_Spec to run it in four flavors:

with Enso Date (as of now)
with JavaScript Date
with JavaScript Date wrapped in (JavaScript) array
with Java LocalDate allocated directly

The code is then improved by necessary modifications to make the Date_Spec pass.
Important Notes
James has requested in #181755990 - e.g. Review and improve InMemory Table support for Dates, Times, DateTimes, BigIntegers the following program to work:
foreign js dateArr = """
    return [1, new Date(), 7]

main =
    IO.println <| (dateArr.at 1).week_of_year

the program works with here in provided changes and prints 27 as of today.
Marcin would like us to further improve the Date implementation. That may happen, but it needs more time and these changes already improve the behavior a lot. Let's integrate them and later rewrite the internals. If you like the changes and you are in hurry, let Hubert take over and integrate. Otherwise I'll be back in ten days.
The support for Time isn't part of this PR yet.
Checklist
Please include the following checklist in your PR:

[ x ] The documentation has been updated if necessary.
[ x ] All code conforms to the Java style guide
All code has been tested:

[ x ] Unit tests have been written where possible.

Generally this works really well.
I added some tests for Table.
The one part that doesn't work is when we send an Enso Data to Java it is represented as a PolyglotMap

This means we don't use DateFormatter and end up calling back to Enso.
Ideally when we pass the object into Java it would be a LocalDate rather than a PolyglotMap

I added some tests for Table.

Great. Thanks for the use-case.

The one part that doesn't work is when we send an Enso Data to Java it is represented as a PolyglotMap

I've got that part working in https://github.com/JaroslavTulach/enso/commit/a4edf9f211077f715f357ce0488929af32f209f1 however that is unlikely the preferred solution - it requires one to know the type of the Column ahead of time and request conversion to the array of right objects.

This means we don't use DateFormatter and end up calling back to Enso. Ideally when we pass the object into Java it would be a LocalDate rather than a PolyglotMap

The problem is that Column.fromItems uses List<Object> argument - GraalVM properly converts the Enso Array to List and notes that elements of that list should be java.lang.Object - however they already are! E.g. when one requests list.get(i) there is no conversion requested and Atom is returned as Atom wrapped into PolyglotMap.
My workaround patch fixes that by having two conversion methods. The other one requests List<LocalDate> - then the conversion happens.
Solution exists, but it is very ugly. Maybe we are not doing the conversions correctly! Also most of the current conversions is hidden behind @TruffleBoundary - e.g. it is magnitudes slower than it could be.

Without e9b0800 I am getting following output when I execute the test:
enso$ enso --run test/Table_Tests/src/Table_Date_Spec.enso --in-project test/Table_Tests/
File.read (Delimited) should work with Dates:
    - should be able to read in a table with dates
    - should be able to treat a single value as a Date
    - should be able to compare columns and table
Should be able to serialise a table with Dates to Text:
    - should serialise back to input
    - [FAILED] should serialise dates with format
        Reason: 'From\n1979-05-04\n1990-11-28\n1997-05-02\n2007-06-27\n2010-05-11\n2016-07-13\n2019-07-24\n' did not equal 'From\n04.05.1979\n28.11.1990\n02.05.1997\n27.06.2007\n11.05.2010\n13.07.2016\n24.07.2019\n' (at enso/test/Table_Tests/src/Table_Date_Spec.enso:51:13-48).

with the e9b0800 change the should serialise dates with format error goes away:
enso$ enso --run test/Table_Tests/src/Table_Date_Spec.enso --in-project test/Table_Tests/
Listening for transport dt_socket at address: 8000
File.read (Delimited) should work with Dates:
    - should be able to read in a table with dates
    - should be able to treat a single value as a Date
    - [FAILED] should be able to compare columns and table
        Reason: [1979-05-04, 1990-11-28, 1997-05-02, 2007-06-27, 2010-05-11, 2016-07-13, 2019-07-24] did not equal [1979-05-04, 1990-11-28, 1997-05-02, 2007-06-27, 2010-05-11, 2016-07-13, 2019-07-24] (at enso/test/Table_Tests/src/Util.enso:16:5-50).
Should be able to serialise a table with Dates to Text:
    - should serialise back to input
    - should serialise dates with format

however another problem appears should be able to compare columns and table - e.g. the solution has some collateral damage which has to be avoided.

I believe I addressed major concerns by introducing EnsoDate. I am requesting another round of reviews.

This is a step backwards, away from proper date support: now every single date object
will get wrapped eagerly, instead of being wrapped on demand.
... we always mangle polyglot dates even if no such need exists)

Now wrapping only happens when a method is invoked on isDate(object). The object is wrapped into EnsoDate.

we'll get 4x the mess when trying to support the whole set of time-like types.

Right. Only asDate(...) is currently supported.

I was told by the Truffle team that Env.asGuestValue is discouraged and poised for deprecation.

The new version isn't using the method anymore. However the Env.asGuestValue does the same thing (creates an HostObject) as polyglot java import .... - it is unlikely to go away.

And with Hubert's changes to builtin objects, doing it right is trivial.

@hubertp suggested to also do other simplifications. I'll replace some nodes with DSL soon:

https://github.com/hubertp/enso/commit/e56a0f35845428eb6e98d6efb07a827aec9fd927
https://github.com/hubertp/enso/commit/0a466d9e77a52dca768a21411a5c263235c49549

@kustosz, @4e6, @jdunkerley & co. all. I have addressed all your comments. Please give me an approval to integrate.


Parse Quantity Strings

Fix missing number in Quantity formatting for small values
Add function to allow parsing of Quantity strings

Updated and ready for review

CI failing with:

pylint src benchmarks docs examples noxfile.py tests
************* Module frequenz.sdk.timeseries._quantities
src/frequenz/sdk/timeseries/_quantities.py:204:4: R0912: Too many branches (16/12) (too-many-branches)
************* Module tests.timeseries.test_quantities
tests/timeseries/test_quantities.py:582:4: W0212: Access to a protected member _base_value of a client class (protected-access)

CI failing with:..

haha, I had that fixed, I just didn't add it to the commit XD

Please re-request a review from me when this is ready for another round.

About the rounding issue when formatting, really tricky, I wonder if it wouldn't be simpler to do a string roundtrip in the formatting function itself, like convert to string, convert again to float, and only then check which exponent is more appropriate, then convert again to string. It might be less efficient (maybe?) but it seems easier to implement and likely more robust.

Yes, I thought about this particular solution as well. It might be less elegant, but it would be pretty reliable and covering pretty much all possibilities.
Maybe in a future PR?

For "Fix quantity formatting bug with -0/0" it might be good to describe what the bug actually was, is not completely clear to me by just reading the diff.

Basically it would only print the unit, no number (the strip removed the 0)

Maybe in a future PR?

Sure

Extended the commit description with the "no unit" explanation

Maybe in a future PR?

https://github.com/frequenz-floss/frequenz-sdk-python/issues/857


Can you make the Jerboa from Alex’s mobs interact with golden seeds?

Sorry, but it looks like there's no easy way to implement this, so for now I'll close the feature request.


warning: regexp match /.../n against to UTF-8 string

Hey there,
I'm getting several warnings when receive tweets with especial characters like "é ç ã â".
/home/melquic/.rvm/gems/ruby-1.9.2-p180/gems/faraday-0.7.5/lib/faraday/utils.rb:128: warning: regexp match /.../n against to UTF-8 string
Thanks,
Melquisedeque

Can you post a code sample that illustrates this? TweetStream doesn't have a dependency on Faraday so I'm not entirely sure where this might be coming from. Thanks.
On Dec 4, 2011, at 7:39 AM<EMAIL_ADDRESS>wrote:

Hey there,
I'm getting several warnings when receive tweets with especial characters like "é ç ã â".
/home/melquic/.rvm/gems/ruby-1.9.2-p180/gems/faraday-0.7.5/lib/faraday/utils.rb:128: warning: regexp match /.../n against to UTF-8 string
Thanks,
Melquisedeque

Reply to this email directly or view it on GitHub:
https://github.com/intridea/tweetstream/issues/53

Sorry. I figured out that the problem is with twitter gem and not tweetstreem.
I will close this issue and raise one for twitter gem guys. Thanks.


BIP44 uses 32bit int for coin type

Discovered trying to implement a coin with a coin type > 65535 causes coin type to overflow which in turns causes "Unusual derivation path".
This app currently uses unsigned short for coin types, changing to unsigned int would support all BIP44 coin types such as the ones listed here - https://github.com/satoshilabs/slips/blob/master/slip-0044.md
For example, https://github.com/LedgerHQ/app-bitcoin-new/pull/6 coin type would overflow.

Closing, only relevant for altcoins that will rather be handled in the legacy bitcoin app repo.


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 83 ms

Resolved: ClamAV performance has improved in 5dfe921 after 12 minutes.


Rabbitmq Image Failed:  OCI runtime create failed: permission denied

I am getting this error when trying to run container image of rabbit mq. Please help in fixing this as soon as possible.
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/usr/local/bin/rabbitmq-server-docker-entrypoint.sh": permission denied: unknown.
https://mcr.microsoft.com/en-us/product/cbl-mariner/base/rabbitmq-server/about
Command that I am trying to run:
docker run -d --hostname my-rabbit --name some-rabbit mcr.microsoft.com/cbl-mariner/base/rabbitmq-server:3

I see similar behavior - Tagging @sameluch who may have more insight on this rabbitmq container composition

@sukhbir-singh I have made some updates on our build side that will solve this issue in the next release of the container.


Use MTM with Android Studio/Gradle

Hi,
I am trying to integrate MTM in an Android Studio project with gradle.
Can you assist me in integrating it? I added "android.library.reference.1=submodules/MemorizingTrustManager" to gradle.properties (since I don't have a default.properties - is that correct?).
Unfortunately it cannot resolve the name of the activity, when I add it to the AndroidManifest.xml of my app.
Any idea?
Thanks folks!

add include submodules:MemorizingTrustManager to settings.gradle
in your build.gradle add into project dependencies:
compile project('submodules:MemorizingTrustManager')

You could probably use it through Jitpack too: https://jitpack.io/

For me that did not work, I had to do it slightly different.
settings.gradle:
include ':MemorizingTrustManager'
project(':MemorizingTrustManager').projectDir = new File('libs/MemorizingTrustManager')

app/build.gradle:
dependencies {
    compile project(':MemorizingTrustManager')
}

I follow the above steps to do, the results appeared some problems
Error:Could not get unknown property 'MemorizingTrustManager' for settings 'GoRunning' of type org.gradle.initialization.DefaultSettings.
my local.properties
 sdk.dir=F\:\\sofeMuLu\\sdk\\androidsdk_4_5_6 #android.library.reference.1=E\:\\Application0206\\Git\\MemorizingTrustManager-master\\src android.library.reference.1=submodules/MemorizingTrustManager
settings.gradle
include ':app' include submodules:MemorizingTrustManager project(':MemorizingTrustManager').projectDir = new File('libs/MemorizingTrustManager')
build.gradle
dependencies {     compile fileTree(dir: 'libs', include: ['*.jar'])     testCompile 'junit:junit:4.12'     compile 'com.android.support:appcompat-v7:23.2.1'     compile 'org.igniterealtime.smack:smack-android-extensions:4.1.4'     compile 'org.igniterealtime.smack:smack-tcp:4.1.4'     compile project('submodules:MemorizingTrustManager') }
what should I do？


Update sample policy as its very confusing.

You are right this is confusing!
Would you mind doing step 2 of the contributing guide? https://github.com/elastic/logstash/blob/master/CONTRIBUTING.md#contribution-steps

Jenkins standing by to test this. If you aren't a maintainer, you can ignore this comment. Someone with commit access, please review this and clear it for Jenkins to run; then  say 'jenkins, test it'.

jenkins, test it

@azdlowry Thanks I just merged it, it will appear when we generate the new documentations.


single gpu run

Hi! I'd like to debug through your model to explore your proposal further, but from what I understand (and after trying to do so), fairseq doesn't allow working with breakpoints to stop the code mid run. Do you have any command suggestions for debugging? In addition, I have computational restraints and would like to know if there is any modification I can do to the training command so that it trains in only one gpu (or at least not occupy all the gpus in my device). Thanks.

Hi!
To my knowledge, you can add the breakpoint into the fairseq code, and the code should stop at that point.
If you want to specify the GPUs, you can firstly set the environment variable CUDA_VISIBLE_DEVICES before runing python script.


Feature/Add Preprint Provider LawArXiv [OSF-7810]

Purpose
Add OSF-side changes for adding LawArXiv preprint provider. Companion to https://github.com/CenterForOpenScience/ember-preprints/pull/325
Changes
Adds placeholder images and modifies populate_preprint_providers script.
LawArXiv sign up screen

Ticket
https://openscience.atlassian.net/browse/OSF-7810

Pulling from develop works @brianjgeiger!

Closed in favor of hotfix https://github.com/CenterForOpenScience/osf.io/pull/7145


Exception when reading settings

Traceback (most recent call last):
  File "/opt/sublime_text/Lib/python33/sublime_plugin.py", line 478, in on_api_ready
    plc()
  File "/home/raoul/.config/sublime-text-3/Packages/LSP/plugin/core/main.py", line 26, in startup
    load_handlers()
  File "/home/raoul/.config/sublime-text-3/Packages/LSP/plugin/core/registry.py", line 59, in load_handlers
    register_language_handler(handler)
  File "/home/raoul/.config/sublime-text-3/Packages/LSP/plugin/core/registry.py", line 65, in register_language_handler
    client_configs.add_external_config(handler.config)
  File "/home/raoul/.config/sublime-text-3/Packages/LSP-lemminx/plugin.py", line 153, in config
    for key, value in merge_configs(default_config, user_config):
  File "/home/raoul/.config/sublime-text-3/Packages/LSP-lemminx/plugin.py", line 29, in merge_configs
    yield key, dict(merge_configs(value, new_value))
  File "/home/raoul/.config/sublime-text-3/Packages/LSP-lemminx/plugin.py", line 29, in merge_configs
    yield key, dict(merge_configs(value, new_value))
  File "/home/raoul/.config/sublime-text-3/Packages/LSP-lemminx/plugin.py", line 32, in merge_configs
    if isinstance(value[0], dict):
IndexError: list index out of range

It breaks at reading the catalogs value.

@deathaxe maybe it would be a good idea to have PRs for changes? I wouldn't mind having a look.

In combination with setting up some tests, yea.


Windows Glob support has broken arguments in v3.0

Had a heck of a time trying to get this to work on windows. I kept getting the error of 'missing destination argument' even though debug displayed the program taking in the destination argument. Downgrading to v2.4 apparently fixed the issue. my guess is glob support, whatever that is, broke it, but I don't know enough to guess. This program is a lifesaver if it works properly, so I hope it is kept maintained.

I'm currently stuck learning for exams so I don't have any time on my hands right now but I plan on keeping this tool maintained.
It might take a few weeks until I have time to fix it.
In the meantime can you please give an example when the tool failed so I can fix it as fast as possible once I have the time?

the above command works when using 2.4, so I'm guessing it's something from 3.0 that breaks it. I might be missing something.


Vagueness with city

For example I live in San Jose, USA but the script thinks that I live in the Mexican San Jose as seen here. It might also apply with different cities that also share the same name (e.g. Springfield, Franklin).

Never mind, wttr.in also thinks I am in Mexico...

This is a problem with wttr.in, as a workaround I'd suggest using zip codes or something like San_Jose_USA with the -c option until I create a way to have a config file with defaults.


[Feature Request]:  Quiz section in tailwind

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
As many students are lagging in mcqs in placements. Quiz section will be very much helpful for them.
Use Case
It will help students to practice the mcqs before placements or interviews.
Benefits
No response
Add ScreenShots

Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

Can you label level 2 atleast coz its time consuming task for adding more questions , and validating answers. @Ajay-Dhangar

@mukilan2815 Please complete your task otherwise I will close it. and if you have any queries then ask me on our live chat for support: https://codeharborhub.github.io/community/supports#-how-to-get-support

I will complete within 2 days

I will complete within 2 days

Ok

@mukilan2815 Please complete your task.

@Ajay-Dhangar can u assign this issue to me

@Ajay-Dhangar can u pls assign this issue to me

@Ajay-Dhangar pls assign this issue to me

@Ajay-Dhangar pls assign this issue to me

@Khushi-Pushkar now work on it

@Ajay-Dhangar Pls assign this task to me..

Hey @Amruta7203 . I am currently working on that task. While it may seem easy, it is actually quite challenging. Therefore, I will need some more time to complete it. In the meantime, you may address other issues or create new issues related to the quiz section in different languages.


Some small things

btw I love this crate tysm for the rust port it's just as wonderful to work with as the original API
I'm currently using it to develop this tool
Changes

I think I fixed add_fname because it wasn't updating the index of the returned FName
I added a get_name_mut function to PropertyDataTrait to prevent monstrosities like this

OH gotcha sorry from context that's what I thought it was

That's especially confusing because when ByteProperty contains an enum value it stores the index of a name

Ok changed that now so only the get_name_mut method and removal of unnecessary as_str calls are left