pip install problem with Windows

Dear RDKit devs,
I'm getting  an error when installing RDkit from pip that didn't show up when installing from conda-forge. I've seen this error in Windows 10 and 11 when I import the rdkit.Chem module in AQME (python program):
  File "PATH\anaconda3\lib\site-packages\aqme\csearch.py", line 18, in <module>
    from rdkit.Chem import AllChem as Chem
  File "PATH\anaconda3\lib\site-packages\rdkit\__init__.py", line 38, in <module>
    from . import rdBase
ImportError: DLL load failed while importing rdBase: The specified module could not be found.

I'm using an Anaconda 3 prompt with python 3.9.7 to run the code.
Thanks,
Juan

Hola Juan,
I don't think this is a bug in RDKit. I'm rather inclined to think this is a problem with your setup:
I just installed the RDKit package using pip under non-Anaconda Python 3.9 on Windows 10, and I can run python -c "from rdkit.Chem import AllChem as Chem" without a traceback, so I don't think the package itself is broken.
But, if I install anaconda, and then again try to install the pypi rdkit package under it using pip, and again run python -c "from rdkit.Chem import AllChem as Chem", then I get a traceback similar to yours. I think this might be happening because of some incompatibility between the pypi package and anaconda.
There's a workaround you can try, though. You can run the following in your anaconda environment before trying to use the rdkit package:
set PATH=%PATH%;{your PATH}\anaconda3\lib\site-packages\rdkit.libs

(Note that {your PATH} should be the same as the PATH in the traceback you posted)
This will tell the OS to also look for DLLs under path {your PATH}\anaconda3\lib\site-packages\rdkit.libs, and find the DLLs that the pypi rdkit package installs there, which are required to use rdkit. But please be aware that this might break dependencies for other anaconda packages. It's up to you to test this workaround and, if it works, decide if you are ok with it. Suerte!
Since, as I said, this is not an RDKit bug, I'm going to close this issue.


updating the repo?

is there some way to easy pull new updates / new components that are added to the library?
since it's not released as a package

You could fork a copy and that way bring in changes as the repo is updated

the problem is that the repo itself isn't a valid nextjs app? i have to use the command

@bryanhpchiang I'm looking into a solution for this. I got something working. I'll update here when we can test it.

@bryanhpchiang  check out https://www.chimera-ui.com/, it’s a fork of shadcn ui but it’s published as a package so you can import the components

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.


[REQUEST] Dog Command

Implement the dog command, which requests a dog media from https://random.dog/woof.json.
The endpoint returns its payload in the format:
{
    "fileSizeBytes": "Integer",
    "url": "String"
}

The media appears to be types .gif, .jpg, and .mp4

Closed by #19


Implement RFC0045: Secure runtime environments

RFC
Summary
This RFC recommends that Paketo Buildpacks should in general strive to avoid making run-time modifications to the Buildpacks layers or the application directory by default. Instead, they should consider the output image to be read-only by default and explicitly set the parts that need to be writeable during runtime.
Implementation
At a high level this would involve the following -

Create base stacks equivalent to the current Paketo stacks but with different runtime user ids. Alternatively, we can also target the next Ubuntu/RHEL-UBI based Paketo stacks to contain a different build/runtime user id.
https://github.com/paketo-buildpacks/stacks/issues/133
Run a parallel test pipeline which is optional and allowed to fail for each buildpack. This pipeline should utilize this new builders to gather the level of compliance for the current set of buildpacks. These tests should also provide appropriate directories for writing ephemeral files during runtime such as /tmp or /run. We can also use docker to mimic read only directories per https://www.thorsten-hans.com/read-only-filesystems-in-docker-and-kubernetes/
Track the compliance status and update buildpacks as necessary to comply with this RFC. The majority changes that would be needed would be for runtime executables/scripts provided by buildpacks such as profile.d or exec.d interfaces. Seperately we would also need to track configuration locations for configurations provided by buildpacks which lead to files being written on the root filesystem, such as log files etc. and configure them to write to ephemeral locations such as /tmp or the runtime user's home directory.
We should create a utility buildpack that allows users to specific path patterns in gitignore format to make such directories group writable.
Once all buildpacks comply, we can release the new set of builders/stacks with hardened security environments to Paketo users. - At some point in the future we can deprecate the current less-secure builders and stacks.

Current status: We believe that Paketo buildpacks are all now set up to create images that run successfully on read-only runtime filesystems. We will not be able to integration test this functionality for buildpacks until they are compatible with the Jammy stack. Therefore, closing this issue is blocked on https://github.com/orgs/paketo-buildpacks/projects/24/views/1.


Github's response to the issues with the CocoaPods repository may be relevant to this repository

Recently, Github has rate-limited the CocoaPods repository because of the scalability issues with using Github as a CDN. Github's response is here.
NixOS uses Github in a similar manner, so it seems to me that the way NixOS distributes package sources needs to change soon. I doubt it's a major issue right now, but if NixOS becomes more popular, this could pose an issue for Github and NixOS.
Thoughts?

Quoting from GitHub's response, linked above:
there have been approximately 1.1 Million clones/fetches from CocoaPods/Specs in the past week.

For comparison, the nixpkgs repo has seen 2319 clones in the time period 02.25--03.09, peaking at 298 clones (according to https://github.com/NixOS/nixpkgs/graphs/traffic).

I believe our typical workflows do not include very frequent clones/fetches. (I discount active contributors, but there will likely never be more than thousands of those.)
It seems to me personally that CocoaPod wasn't using git in a fitting/efficient way. In any case, I believe NixOS.org is rather far from having similar problems and it shouldn't be hard to cope with them in case they appear in (far) future.

I believe our typical workflows do not include very frequent clones/fetches. (I discount active contributors, but there will likely never be more than thousands of those.)
It seems to me personally that CocoaPod wasn't using git in a fitting/efficient way. In any case, I believe NixOS.org is rather far from having similar problems and it shouldn't be hard to cope with them in case they appear in (far) future.

As far as I understand, the things CocoaPods done wrong (according to
GitHub) are:

Not having a way for the end users to use CocoaPods without checking
out from Git (Nix has channels)

Having thousands subdirectories as a flat structure inside one
directory (we have our hierarchical classification, and if we abandon it
I hope we just switch to the n/ng/nginx approach)

Having periodic fetches into a shallow checkout. I think we never
encouraged this specific usage pattern and have not encoded it into any
scripts.

Using Git in an append-only way with adding new versions instead of
ever updating any packages.

Not using a preview API to check whether there are any changes to
fetch before fetching. I am not sure if trying to update NixPkgs and not
getting any new commits because the checkout is already fresh enough is
widespread.

Given our much smaller userbase, I also think going through the
checklist should be enough…
I have no idea about the preview API and adding support for it, though.


creating window on one of Windows virtual desktop affects the workspace layout on another virtual desktop

Version (which release did you use?)
Describe the bug
creating window on one of Windows virtual desktop affects the workspace layout on another virtual desktop
To Reproduce
Steps to reproduce the behavior:

Create more than one virtual desktop
Create a workspace and open a window
Switch to the other virtual desktop
Create another window
You see the window on virtual desktop A and virtual desktop B are both half of the screen

Expected behavior
Workspaces maintain dependent on difference virutal desktops
Actual behavior
creating window on one of Windows virtual desktop affects the workspace layout on another virtual desktop

Is there a reason why you are using virtual desktops together with a window manager?
AFAIK there should be no reason to use them together, so right now we aren't planning on supporting virtual desktops.

after a second thought I think you are right, why should I use virtual desktop along with nog...


Can't submit transfer even I have balance

Seems we are checking the balance on the transfer before submit? If so, I have balance and can't send less than that.
The bug is I can't hit submit button

👋

Hey, this bug has been fixed in https://beta.kodadot.xyz @yangwao
Let's have a try and close this issue.

Well this was from beta, I can try clear cache and try again 👀

@Jarsen136 hey seems the same after clearing the cache. 👀
Like when I open this link it doesn't work https://beta.kodadot.xyz/transfer/?target=HsFee3QAwYrE4oiYGTjQvXQYCaxN5BTLKgJRwVNPZoYzxKE&usdamount=100

@Jarsen136 hey seems the same after clearing the cache. 👀
Like when I open this link it doesn't work https://beta.kodadot.xyz/transfer/?target=HsFee3QAwYrE4oiYGTjQvXQYCaxN5BTLKgJRwVNPZoYzxKE&usdamount=100

So weird. I still could not reproduce this bug even though I open your link.
https://beta.kodadot.xyz/transfer

When I open https://kodadot.xyz/transfer, I could reproduce it.

hmm, let me check it

👋


opusEncodingQuality and resamplingQuality parameters have no noticeable effect

Change request
When adjusting the parameters opusEncodingQuality and resamplingQuality, no change in audio quality or performance is noticeable. The following setup was used:

Configuration:

opusEncodingQuality: 0 (and tests with 10)

resamplingQuality: LOW (and tests with HIGH)

Expected behavior:
Lower quality should improve performance and reduce audio quality, especially with lower values for opusEncodingQuality and resamplingQuality.

Actual behavior:
Audio quality and performance remained constant regardless of the value set for opusEncodingQuality and resamplingQuality.

Relevance
This issue is relevant to the Lavalink community, as many users expect performance optimizations through parameters such as opusEncodingQuality and resamplingQuality to run Lavalink more efficiently on servers with limited resources. If the parameters work as documented, they can help save resources and improve the user experience, especially on large servers or bots with high user traffic.
Could this be a plugin instead?

Checklist

[X] I have checked for duplicate issues
[X] I have checked for existing plugins

what track did you play to try this?

Those settings only take effect when transcoding is involved. If you're playing from sources whose input format is opus (so youtube, soundcloud and possibly HTTP tracks), then they won't have any effect unless you force transcoding via volume or filter application.
Anyway, there is nothing to be fixed or changed here. The opus encoder setting is applied to the native Opus library so it's up to that what it does with the value you give it.
Similarly, with resampling quality, this will apply to the native resampling library (libsamplerate). Outside of native method calls, we have very little control over what we can do with audio configurations.


✨  Replace http and https with got

closes #99

Used got for image-size requests, which is more lightweight and has the huge advantage of following redirects
Added and updated test
indents
Added dependencies:

validator
lodash
got

Coverage decreased (-1.8%) to 96.46% when pulling 9638035c2451e4b181b4a0265cbfd1dfa6870167 on AileenCGN:use-got-and-follow-redirects into 94ac029dc7f973774c9ae78366d88dc8c592a7ec on jbhannah:master.

Coverage decreased (-0.02%) to 98.23% when pulling ebaccdf9e2783924df506f88e9ee91f76febc461 on AileenCGN:use-got-and-follow-redirects into 94ac029dc7f973774c9ae78366d88dc8c592a7ec on jbhannah:master.

Coverage decreased (-0.02%) to 98.23% when pulling ebaccdf9e2783924df506f88e9ee91f76febc461 on AileenCGN:use-got-and-follow-redirects into 94ac029dc7f973774c9ae78366d88dc8c592a7ec on jbhannah:master.

Coverage decreased (-0.2%) to 98.095% when pulling 71349aa937d928b04c975695af444766c913a11d on AileenCGN:use-got-and-follow-redirects into 65d7037bb27cc0957bd9ef20f9343d5e47f290e8 on jbhannah:master.

Coverage decreased (-0.2%) to 98.095% when pulling b15df2f6314975f661ea67d2e69196340f30e8b1 on AileenCGN:use-got-and-follow-redirects into 65d7037bb27cc0957bd9ef20f9343d5e47f290e8 on jbhannah:master.

Coverage decreased (-0.2%) to 98.095% when pulling f1ea202338a4391fb4748f0ca63a55b32e7ed35f on AileenCGN:use-got-and-follow-redirects into 65d7037bb27cc0957bd9ef20f9343d5e47f290e8 on jbhannah:master.

Coverage decreased (-0.2%) to 98.095% when pulling c0f10c7026ff8263096b76403596245afe7a5bd2 on AileenCGN:use-got-and-follow-redirects into 65d7037bb27cc0957bd9ef20f9343d5e47f290e8 on jbhannah:master.

Coverage increased (+1.8%) to 100.0% when pulling 49e9f89a914dd06eaff46b98a0d744f0480ddd52 on AileenCGN:use-got-and-follow-redirects into 65d7037bb27cc0957bd9ef20f9343d5e47f290e8 on jbhannah:master.


Build a simple pipeline documentation doesn't currently work

Describe the bug
I'm trying to follow the example here: https://docs.griptape.ai/en/latest/griptape-framework/#build-a-simple-pipeline and the example fails when trying to run it. It's throwing a value error ValueError: activity query doesn't exist. This is on windows 10, using python 3.10.8 and I also tried with python 3.11.3
To Reproduce
Steps to reproduce the behavior:

create a new virtual environment
pip install griptape griptape-tools
copy the example into main.py
try to run main.py using the interpreter for the venv

Expected behavior
I expected the program to run without errors.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS:Windows 10
Version: 22H2
Build: 19045.2965

The same issue exists when trying to use the examples in the Tool Memory Documentation as well.

@mgcollie, thanks for reporting those! We made several breaking changes in the last update and the docs for two tool activities (in FileManager and TextProcessor) weren't updated. I just pushed a docs update with fixed examples, so it should be all good now.

@vasinov my pleasure. glad to help. I can confirm that the new updated docs are working as expected.  thanks for the quick fix.


install librealsense2-dkms error

Required Info

Camera Model
D435i

Firmware Version

Operating System & Version
Ubuntu 16.04

Kernel Version (Linux Only)
4.4.0-31

Platform
intel PC

SDK Version
2.25

Language
C++/python

Segment
Robot

installl librealsense2-dkms package report the following error, other package is ok
i check the linux header file, i found the marco UVC_PC_PROTOCOL_15 which is defined in file
/usr/include/linux/usb/video.h not in "include/linux/usb.h",
正在设置 librealsense2-dkms (1.3.5-0ubuntu1) ...
Loading new librealsense2-dkms-1.3.5 DKMS files...
Building only for 4.4.0-31-generic
Building initial module for 4.4.0-31-generic
Error! Bad return status for module build on kernel: 4.4.0-31-generic (x86_64)
Consult /var/lib/dkms/librealsense2-dkms/1.3.5/build/make.log for more information.
make: Entering directory '/usr/src/linux-headers-4.4.0-31-generic'
CC [M]  /var/lib/dkms/librealsense2-dkms/1.3.5/build/4.4.0/drivers/media/usb/uvc/uvc_driver.o
In file included from /var/lib/dkms/librealsense2-dkms/1.3.5/build/4.4.0/drivers/media/usb/uvc/uvc_driver.c:19:0:
/var/lib/dkms/librealsense2-dkms/1.3.5/build/4.4.0/drivers/media/usb/uvc/uvc_driver.c:2990:43: error: ‘UVC_PC_PROTOCOL_15’ undeclared here (not in a function)
{ USB_INTERFACE_INFO(USB_CLASS_VIDEO, 1, UVC_PC_PROTOCOL_15) },
^
include/linux/usb.h:952:25: note: in definition of macro ‘USB_INTERFACE_INFO’
.bInterfaceProtocol = (pr)
^
scripts/Makefile.build:258: recipe for target '/var/lib/dkms/librealsense2-dkms/1.3.5/build/4.4.0/drivers/media/usb/uvc/uvc_driver.o' failed
make[1]: *** [/var/lib/dkms/librealsense2-dkms/1.3.5/build/4.4.0/drivers/media/usb/uvc/uvc_driver.o] Error 1
Makefile:1573: recipe for target 'uvcvideo.ko' failed
make: *** [uvcvideo.ko] Error 2
make: Leaving directory '/usr/src/linux-headers-4.4.0-31-generic'
-------------**
other one (4.4.0-159) is install from online  is ok
can you  tell me how to do this?

@comwise , D435i is implemented according to UVC 1.5 standard and the kernel you're running is pre-UVC1.5 (UVC1.1). So even if you manage to resolve compilation issues I don't think it is guaranteed that the device (or at least some controls) will work properly.
Officially UVC1.5 support was added in kernel 4.5, but with most distros (e.g Ubuntu) any kernel beyond ~4.4.0-60+ should be ok, like the 4.4.0-159 that you mention.
Is there any specific reason that you have to use 4.4.0-31 and not the up-to-date 4.4.0-159?

@ev-mp this linux image is clone，all old robots image is base on kernel 4.4.0-31,  if i upgrade the kernel，some devices is unusable，i need to update these device drivers which is a difficulty and complex job, if you can offer good advice, i will upgrade the linux kernel

@comwise  Did you try to update the system? It should be really streamlined -

sudo apt-get update && sudo apt-get upgrade && sudo apt-dist-upgrade -y

The kernel 4.4.0-31 was built into the baseline image, and this apparently the baseline Ubuntu used when started shipping Xenial.
As I mentioned above that kernel is not compatible with D435i as it does not include driver support for UVC1.5 standard. So in case you want to install DKSM upgrading the kernel is necessary.
There are additional benefits for getting the system updated - bug and security fixes, such as the notorious Meltdown and Spectre.
Note the DKMS is not a hard-requirement and in many case can be dismissed/replaced by libuvc backend. So this is another path you can follow if you're stuck with 4.4.0-31.

@ev-mp  i updated the kernel by the following
sudo apt-get update && sudo apt-get upgrade
which can resolve my driver problems,
if i only updated kerner by
 sudo apt-get install linux-image-4.4.0-159-generic linux-image-extra-4.4.0-159-generic,
there is some problems with drvier
thanks for your reply

Hi @comwise,
Glad to hear the problem is resolved.
Closing this ticket unless there is any other question.


Add 3 members to CacheFilter owners list

@penguingao @mpwarres and myself are actively working on CacheFilter, bringing it up to RFC compliance among other functionality.

Can you merge main?
Also, please don't force push in envoy PRs; it shouldn't matter for this one, but force-pushing drops PR comments.

Also, please don't force push in envoy PRs; it shouldn't matter for this one, but force-pushing drops PR comments.

There were no comments when I force pushed, and the alternative was to create a new PR cause I needed to add the Signed-off-by line. I couldn't decide which would bother people less... force-pushing or closing and recreating the PR. Perhaps I chose wrong.

No problem! Just wanted to avoid dropping comments in the future :)
You can set up a git hook to auto-add the signed-off line.


Set fingerprinting noise_factor during document construction

This PR updates fingerprinting-flags-client-rects-and-measuretext.patch to set the noise factor during document construction rather than when an updated layout is requested.  Fixes #2774 and the underlying issue in #2714.
Pre-patch:

https://browserleaks.com/rects:  Values change on refresh
https://www.desmos.com/calculator/gwqlodfcbm:  Constant shifting
Cockpit 313:  Error on networking page

Post-patch:

https://browserleaks.com/rects:  Values change on refresh
https://www.desmos.com/calculator/gwqlodfcbm:  No shifting
Cockpit 313:  Networking page functions as expected

@Ahrotahn Could it potentially fix https://github.com/ungoogled-software/ungoogled-chromium/issues/2389?

I wasn't able to reproduce the error with the original link but I could for the one that happens on github, and this change does solve that issue.


Type: Make leaner, replace enum with assoc consts

As suggested in https://github.com/gtk-rs/glib/pull/728#discussion_r582044041.
(Depends on #728)

@heftig Wrong repository. Can you submit a new PR to https://github.com/gtk-rs/gtk-rs/ ? Thanks!

Looks good to me otherwise


Blueprint Behaviour Tree Tasks (#215) - Blackboard key NextWaypoint issues

At 10:10 in lecture #215 there is mention of "NextWaypoint" Blackboard key, which later I re-watched the video to find that it was "renamed off screen" from "Waypoint" in a video footnote.  This through me off because I was working in a separate monitor and did not see that instruction, but that is just a side note for you and not the real issue here...
When the original Blackboard key is created, either "Waypoint" or "NextWaypoint" it needs to be of Base Class "Actor" in order for the key to appear in the Behavior Tree pull-down for "Move To" task. Thank you and excellent work on this course--very thorough and enjoyable.

Thanks Mackenzie. Does this issue show up in the lectures?
On 5 February 2018 at 23:04, Mackenzie Fisher<EMAIL_ADDRESS>wrote:

At 10:10 in lecture #215 there is mention of "NextWaypoint" Blackboard
key, which later I re-watched the video to find that it was "renamed off
screen" from "Waypoint" in a video footnote. This through me off because I
was working in a separate monitor and did not see that instruction, but
that is just a side note for you and not the real issue here...
When the original Blackboard key is created, either "Waypoint" or
"NextWaypoint" it needs to be of Base Class "Actor" in order for the key to
appear in the Behavior Tree pull-down for "Move To" task. Thank you and
excellent work on this course--very thorough and enjoyable.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/UnrealCourse/05_TestingGrounds/issues/7, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AB4LQDa4uXCxQy8Tb5dZIemOV5UbsQGrks5tR4jlgaJpZM4R6PPT
.


Feature: Add new EnderIO xp to defaults

Hey there! I didn't see a CONTRIBUTING.md so I figured this might be something that I can just open. I've tested it in my own instance and have confirmed that the FluidTank from EnderIO is able to extract directly to the obelisk. The two attached screenshots (as I didn't have a chance to record video but I can try to get it if needed) show the decrease from the fluid tank with a push into the obelisk.

Ah, ty for the heads up. I will include this in the next build.


Azure Java SDK - ChainedTokenCredential not switching to next available TokenCredential in case of 403 forbidden error

Describe the bug
Even though ChainedTokenCredential enables multiple TokenCredential implementations to be tried in order until one of the getToken methods returns an access token, but it can handle only authentication error but not authorization i.e., it will throw 403 error and will not automatically switch to other available authentication if RBAC permissions are not defined. ChainedTokenCredential is not switching from System Assigned Managed Identity to User Assigned Managed Identity if System Assigned Managed Identity don't have RBAC permissions
Exception or Stack Trace
[2022-02-25T11:50:18.018Z] [com.azure.cosmos.implementation.query.DocumentProducer] [cosmos-rntbd-nio-3-2] [199] [ERROR] [] [] Unexpected failure
com.azure.cosmos.implementation.ForbiddenException: {"innerErrorMessage":"["Request is blocked because principal [********************] does not have the required RBAC permissions to perform action [Microsoft.DocumentDB/databaseAccounts/sqlDatabases/containers/executeQuery] with OperationType [15] and ResourceType [2] on resource [dbs/DB/colls/leases]. Learn more: https://aka.ms/cosmos-native-rbac"]","cosmosDiagnostics":{"userAgent":"azsdk-java-cosmos/4.17.0 Linux/5.4.0-1062-azure JRE/11.0.5","requestLatencyInMs":1,"requestStartTimeUTC":"2022-02-25T11:50:18.835348Z","requestEndTimeUTC":"2022-02-25T11:50:18.836635Z","responseStatisticsList":[{"storeResult":{"storePhysicalAddress":"rntbd://cdb-ms-prod-centralus1-fd4.documents.azure.com:14101/apps/dbbeead3-9caa-45e6-8ed7-0af7ac3170f4/services/82a44b12-334c-4fa4-9a86-59ae13ac41ce/partitions/2f904776-c8ff-444d-b5cb-e4ab2945b675/replicas/132803609217458999p/","lsn":11989043,"globalCommittedLsn":11989043,"partitionKeyRangeId":"","isValid":true,"statusCode":403,"subStatusCode":5302,"isGone":false,"isNotFound":false,"isInvalidPartition":false,"isThroughputControlRequestRateTooLarge":false,"requestCharge":0.0,"itemLSN":-1,"sessionToken":"-1#11989043","backendLatencyInMs":0.537,"exception":"["Request is blocked because principal [6cffda75-7cfa-4e47-8488-e76c7bcf92fc] does not have the required RBAC permissions to perform action [Microsoft.DocumentDB/databaseAccounts/sqlDatabases/containers/executeQuery] with OperationType [15] and ResourceType [2] on resource [dbs/DB/colls/leases]. Learn more: https://aka.ms/cosmos-native-rbac"]","transportRequestTimeline":[{"eventName":"created","startTimeUTC":"2022-02-25T11:50:18.835414Z","durationInMicroSec":2},{"eventName":"queued","startTimeUTC":"2022-02-25T11:50:18.835416Z","durationInMicroSec":0},{"eventName":"channelAcquisitionStarted","startTimeUTC":"2022-02-25T11:50:18.835416Z","durationInMicroSec":52},{"eventName":"pipelined","startTimeUTC":"2022-02-25T11:50:18.835468Z","durationInMicroSec":85},{"eventName":"transitTime","startTimeUTC":"2022-02-25T11:50:18.835553Z","durationInMicroSec":1005},{"eventName":"received","startTimeUTC":"2022-02-25T11:50:18.836558Z","durationInMicroSec":50},{"eventName":"completed","startTimeUTC":"2022-02-25T11:50:18.836608Z","durationInMicroSec":23}],"rntbdRequestLengthInBytes":2098,"rntbdResponseLengthInBytes":571,"requestPayloadLengthInBytes":222,"responsePayloadLengthInBytes":null,"channelTaskQueueSize":0,"pendingRequestsCount":0,"serviceEndpointStatistics":{"availableChannels":1,"acquiredChannels":0,"executorTaskQueueSize":0,"inflightRequests":1,"lastSuccessfulRequestTime":"2022-02-25T11:48:19.938Z","lastRequestTime":"2022-02-25T11:50:18.810Z","createdTime":"2022-02-25T11:46:37.623655Z","isClosed":false}},"requestResponseTimeUTC":"2022-02-25T11:50:18.836635Z","requestResourceType":"Document","requestOperationType":"Query"}],"supplementalResponseStatisticsList":[],"addressResolutionStatistics":{},"regionsContacted":["https://-centralus.documents.azure.com:443/"],"retryContext":{"statusAndSubStatusCodes":null,"retryCount":0,"retryLatency":0},"metadataDiagnosticsContext":{"metadataDiagnosticList":null},"serializationDiagnosticsContext":{"serializationDiagnosticsList":null},"gatewayStatistics":null,"systemInformation":{"usedMemory":"118660 KB","availableMemory":"30288124 KB","systemCpuLoad":"(2022-02-25T11:49:53.463058Z 3.6%), (2022-02-25T11:49:58.463068Z 3.0%), (2022-02-25T11:50:03.463029Z 3.8%), (2022-02-25T11:50:08.463059Z 2.8%), (2022-02-25T11:50:13.463074Z 3.4%), (2022-02-25T11:50:18.463054Z 3.0%)","availableProcessors":1},"clientCfgs":{"id":-1,"connectionMode":"DIRECT","numberOfClients":2,"connCfg":{"rntbd":"(cto:PT5S, rto:PT5S, icto:PT0S, ieto:PT1H, mcpe:130, mrpc:30, cer:false)","gw":"(cps:1000, rto:PT5S, icto:null, p:false)","other":"(ed: true, cs: false)"},"consistencyCfg":"(consistency: Eventual, mm: true, prgns: [centralus])"}}}
To Reproduce
Steps to reproduce the behavior:
Code Snippet
`DefaultAzureCredential defaultAzureCredential = new DefaultAzureCredentialBuilder().build();
ManagedIdentityCredential userAssignedmanagedIdentityCredential = new ManagedIdentityCredentialBuilder().clientId("").build();
ChainedTokenCredentialBuilder builder = new ChainedTokenCredentialBuilder();
builder.addFirst(defaultAzureCredential);
builder.addLast(userAssignedmanagedIdentityCredential);
ConnectionPolicy defaultPolicy = ConnectionPolicy.getDefaultPolicy();
defaultPolicy.setUserAgentSuffix(applicationName);
defaultPolicy.setPreferredRegions(Arrays.asList("Central US"));
AsyncDocumentClient asyncDocumentClient = new AsyncDocumentClient.Builder().withServiceEndpoint("").withTokenCredential(builder.build()).withConnectionPolicy(defaultPolicy) .withConsistencyLevel(ConsistencyLevel.EVENTUAL).build();`
<properties>         <java.version>11</java.version>         <reactor-netty>1.0.9</reactor-netty>         <reactor-core>3.4.8</reactor-core>     </properties> <dependencies>         <dependency>             <groupId>com.azure</groupId>             <artifactId>azure-core</artifactId>             <version>1.18.0</version>         </dependency>         <dependency>             <groupId>com.azure</groupId>             <artifactId>azure-storage-blob</artifactId>             <version>12.12.0</version>             <exclusions>                 <exclusion>                     <groupId>io.projectreactor</groupId>                     <artifactId>reactor-core</artifactId>                 </exclusion>             </exclusions>         </dependency>         <dependency>             <groupId>com.azure</groupId>             <artifactId>azure-cosmos</artifactId>             <version>4.17.0</version>             <exclusions>                 <exclusion>                     <groupId>io.projectreactor.netty</groupId>                     <artifactId>reactor-netty</artifactId>                 </exclusion>             </exclusions>         </dependency>         <dependency>             <groupId>com.azure</groupId>             <artifactId>azure-identity</artifactId>             <version>1.3.3</version>         </dependency>         <dependency>             <groupId>io.projectreactor</groupId>             <artifactId>reactor-core</artifactId>             <version>${reactor-core}</version>             <!--$NO-MVN-MAN-VER$ -->             <!-- Please don't remove/degrade the version, possible for compatibility issues -->         </dependency>         <dependency>             <groupId>io.projectreactor.netty</groupId>             <artifactId>reactor-netty</artifactId>             <version>${reactor-netty}</version>             <!--$NO-MVN-MAN-VER$ -->             <!-- Please don't remove/degrade the version, possible for compatibility issues -->         </dependency>
Expected behavior
Automatically switch to other available authentication if RBAC permissions are not defined.
Screenshots
Setup (please complete the following information):

OS: Alpine
Library/Libraries: PFA above placed version of Artifacts
Java version: 11
App Server/Environment: Tomcat (Spring boot embedded)
Frameworks: Spring Boot

@g2vinay could you please follow up with @MulakaluriKartheek?
/cc @billwert

Error Stack trace:
[2022-02-25T11:50:18.018Z] [com.azure.cosmos.implementation.query.DocumentProducer] [cosmos-rntbd-nio-3-2] [199] [ERROR] [] [] Unexpected failure
com.azure.cosmos.implementation.ForbiddenException: {"innerErrorMessage":"["Request is blocked because principal [********************] does not have the required RBAC permissions to perform action [Microsoft.DocumentDB/databaseAccounts/sqlDatabases/containers/executeQuery] with OperationType [15] and ResourceType [2] on resource [dbs/DB/colls/leases]. Learn more: https://aka.ms/cosmos-native-rbac"]","cosmosDiagnostics":{"userAgent":"azsdk-java-cosmos/4.17.0 Linux/5.4.0-1062-azure JRE/11.0.5","requestLatencyInMs":1,"requestStartTimeUTC":"2022-02-25T11:50:18.835348Z","requestEndTimeUTC":"2022-02-25T11:50:18.836635Z","responseStatisticsList":[{"storeResult":{"storePhysicalAddress":"rntbd://cdb-ms-prod-centralus1-fd4.documents.azure.com:14101/apps/dbbeead3-9caa-45e6-8ed7-0af7ac3170f4/services/82a44b12-334c-4fa4-9a86-59ae13ac41ce/partitions/2f904776-c8ff-444d-b5cb-e4ab2945b675/replicas/132803609217458999p/","lsn":11989043,"globalCommittedLsn":11989043,"partitionKeyRangeId":"","isValid":true,"statusCode":403,"subStatusCode":5302,"isGone":false,"isNotFound":false,"isInvalidPartition":false,"isThroughputControlRequestRateTooLarge":false,"requestCharge":0.0,"itemLSN":-1,"sessionToken":"-1#11989043","backendLatencyInMs":0.537,"exception":"["Request is blocked because principal [6cffda75-7cfa-4e47-8488-e76c7bcf92fc] does not have the required RBAC permissions to perform action [Microsoft.DocumentDB/databaseAccounts/sqlDatabases/containers/executeQuery] with OperationType [15] and ResourceType [2] on resource [dbs/DB/colls/leases]. Learn more: https://aka.ms/cosmos-native-rbac"]","transportRequestTimeline":[{"eventName":"created","startTimeUTC":"2022-02-25T11:50:18.835414Z","durationInMicroSec":2},{"eventName":"queued","startTimeUTC":"2022-02-25T11:50:18.835416Z","durationInMicroSec":0},{"eventName":"channelAcquisitionStarted","startTimeUTC":"2022-02-25T11:50:18.835416Z","durationInMicroSec":52},{"eventName":"pipelined","startTimeUTC":"2022-02-25T11:50:18.835468Z","durationInMicroSec":85},{"eventName":"transitTime","startTimeUTC":"2022-02-25T11:50:18.835553Z","durationInMicroSec":1005},{"eventName":"received","startTimeUTC":"2022-02-25T11:50:18.836558Z","durationInMicroSec":50},{"eventName":"completed","startTimeUTC":"2022-02-25T11:50:18.836608Z","durationInMicroSec":23}],"rntbdRequestLengthInBytes":2098,"rntbdResponseLengthInBytes":571,"requestPayloadLengthInBytes":222,"responsePayloadLengthInBytes":null,"channelTaskQueueSize":0,"pendingRequestsCount":0,"serviceEndpointStatistics":{"availableChannels":1,"acquiredChannels":0,"executorTaskQueueSize":0,"inflightRequests":1,"lastSuccessfulRequestTime":"2022-02-25T11:48:19.938Z","lastRequestTime":"2022-02-25T11:50:18.810Z","createdTime":"2022-02-25T11:46:37.623655Z","isClosed":false}},"requestResponseTimeUTC":"2022-02-25T11:50:18.836635Z","requestResourceType":"Document","requestOperationType":"Query"}],"supplementalResponseStatisticsList":[],"addressResolutionStatistics":{},"regionsContacted":["https://-centralus.documents.azure.com:443/"],"retryContext":{"statusAndSubStatusCodes":null,"retryCount":0,"retryLatency":0},"metadataDiagnosticsContext":{"metadataDiagnosticList":null},"serializationDiagnosticsContext":{"serializationDiagnosticsList":null},"gatewayStatistics":null,"systemInformation":{"usedMemory":"118660 KB","availableMemory":"30288124 KB","systemCpuLoad":"(2022-02-25T11:49:53.463058Z 3.6%), (2022-02-25T11:49:58.463068Z 3.0%), (2022-02-25T11:50:03.463029Z 3.8%), (2022-02-25T11:50:08.463059Z 2.8%), (2022-02-25T11:50:13.463074Z 3.4%), (2022-02-25T11:50:18.463054Z 3.0%)","availableProcessors":1},"clientCfgs":{"id":-1,"connectionMode":"DIRECT","numberOfClients":2,"connCfg":{"rntbd":"(cto:PT5S, rto:PT5S, icto:PT0S, ieto:PT1H, mcpe:130, mrpc:30, cer:false)","gw":"(cps:1000, rto:PT5S, icto:null, p:false)","other":"(ed: true, cs: false)"},"consistencyCfg":"(consistency: Eventual, mm: true, prgns: [centralus])"}}}

Could you please let me know any update on the above issue??

Could you please let me know any update on the above issue??

@MulakaluriKartheek
The ChainedTokenCredential is designed to execute the chain of credentials sequentially.
In your scenario, you should enable only one Managed Identity (System Assigned or User Assigned) on the target Azure resource.
Plus you should update your code as follows:
DefaultAzureCredential defaultAzureCredential = new DefaultAzureCredentialBuilder()
.managedIdentityClientId("<Client-Id-Of-User-Assigned-Managed-Identity>")
build();

You don't need to use ChainedTokenCredential, using DefaultAzureCredential as above, will target User Assigned Managed Identity.

Closing this issue as the solution is posted above.


twint add new field to elasticsearch twintgraph index

I need help with adding new fields to twint follow result
I use python3.6 twint -u "username" --followers -es localhost:9200
after creating twintgraph index i get :
_id
_index
_score
_type
essid
follow
user
i want to add new field with name : "name" contain the user name (user)
best regards

You can just change the field name here
https://github.com/twintproject/twint/blob/7ea55b2aa0dd1c5c2fe991347e2dfce7fbdb2d43/twint/storage/elasticsearch.py#L298-L324
Also remember to change the schema before creating the index
https://github.com/twintproject/twint/blob/7ea55b2aa0dd1c5c2fe991347e2dfce7fbdb2d43/twint/storage/elasticsearch.py#L123-L138

#pielco11 thank you for your help it's work :+1: +1:


Support for entire files

Hello!
What about support for entire files?!!
I need that, by the way the idea to combine base64 + a generated key is awesome! Well done!
I tried to adapt your code to support encrypting/decrypting a file, but I am having difficulties ....
Are you available for support? I need ASAP!

@MihaiBairac how about consider your file as a string?


WFLY-5022 If auth is not mandatory do not modify the response when us…

…ing JASPI auth

@darranl @sguilhen does this look ok to you guys?

Windows Build 2318 is now running using a merge of 553b22aea1e160af283161e26448beaff2ca4124

Linux with security manager Build 2134 is now running using a merge of 553b22aea1e160af283161e26448beaff2ca4124

Linux Build 7265 is now running using a merge of 553b22aea1e160af283161e26448beaff2ca4124

Linux with security manager Build 2134 outcome was SUCCESS using a merge of 553b22aea1e160af283161e26448beaff2ca4124
Summary: Tests passed: 897, ignored: 285 Build time: 0:06:23

Linux Build 7265 outcome was SUCCESS using a merge of 553b22aea1e160af283161e26448beaff2ca4124
Summary: Tests passed: 2981, ignored: 361 Build time: 0:48:29

Windows Build 2318 outcome was SUCCESS using a merge of 553b22aea1e160af283161e26448beaff2ca4124
Summary: Tests passed: 2979, ignored: 362, muted: 1 Build time: 0:50:20

Will let @sguilhen comment, he is back in the specs at the moment but a first look seems fine to me.

@stuartwdouglas I'm going to stick a Hold label on this since you can remove it when the discussion is complete.

Based on the current codebase I don't mind if we disable pro-active auth, although it will come back with Elytron we can ensure more control.

Windows Build 2441 is now running using a merge of c89af3f4cc49673c2748446215a2053aa75fed1c

Linux with security manager Build 2256 is now running using a merge of c89af3f4cc49673c2748446215a2053aa75fed1c

Linux Build 7394 is now running using a merge of c89af3f4cc49673c2748446215a2053aa75fed1c

Linux with security manager Build 2256 outcome was FAILURE using a merge of c89af3f4cc49673c2748446215a2053aa75fed1c
Summary: Tests failed: 5 (5 new), passed: 890, ignored: 290 Build time: 0:06:50
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.web.formauth.FormAuthUnitTestCase.testFlushOnSessionInvalidation: <no details avaliable>

org.jboss.as.test.integration.web.formauth.FormAuthUnitTestCase.testFormAuthSubject: <no details avaliable>

org.jboss.as.test.integration.web.formauth.FormAuthUnitTestCase.testFormAuthException: <no details avaliable>

org.jboss.as.test.integration.web.formauth.FormAuthUnitTestCase.testFormAuth: <no details avaliable>

org.jboss.as.test.integration.web.formauth.FormAuthUnitTestCase.testPostDataFormAuth: <no details avaliable>

Windows Build 2441 outcome was FAILURE using a merge of c89af3f4cc49673c2748446215a2053aa75fed1c
Summary: Tests failed: 12 (12 new), passed: 3089, ignored: 370 Build time: 0:52:04
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.web.formauth.FormAuthUnitTestCase.testFlushOnSessionInvalidation: <no details avaliable>

org.jboss.as.test.integration.web.formauth.FormAuthUnitTestCase.testFormAuthSubject: <no details avaliable>

org.jboss.as.test.integration.web.formauth.FormAuthUnitTestCase.testFormAuthException: <no details avaliable>

org.jboss.as.test.integration.web.formauth.FormAuthUnitTestCase.testFormAuth: <no details avaliable>

org.jboss.as.test.integration.web.formauth.FormAuthUnitTestCase.testPostDataFormAuth: <no details avaliable>

org.jboss.as.test.clustering.cluster.web.authentication.FormAuthenticationWebFailoverTestCase(SYNC-tcp).test: <no details avaliable>

org.jboss.as.test.manualmode.web.ssl.CertificateRolesLoginModuleTestCase.testDatabaseCertLoginModule: <no details avaliable>

org.jboss.as.test.manualmode.web.ssl.DatabaseCertLoginModuleTestCase.testDatabaseCertLoginModule: <no details avaliable>

org.jboss.as.test.manualmode.web.ssl.HTTPSWebConnectorTestCase.testVerifyingConnector: <no details avaliable>

org.jboss.as.test.manualmode.web.ssl.HTTPSWebConnectorTestCase.testNonVerifyingConnector: <no details avaliable>

org.jboss.as.test.manualmode.web.ssl.HTTPSWebConnectorTestCase.testDefaultConnector: <no details avaliable>

##### there are 2 more failed tests, see build details

Leaving as hold, this exposed an issue with Undertow's form auth that requires Undertow 1.3.0.Beta8

Linux Build 7394 outcome was FAILURE using a merge of c89af3f4cc49673c2748446215a2053aa75fed1c
Summary: Tests failed: 12 (12 new), passed: 3089, ignored: 370 Build time: 0:54:28
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.web.formauth.FormAuthUnitTestCase.testFlushOnSessionInvalidation: <no details avaliable>

org.jboss.as.test.integration.web.formauth.FormAuthUnitTestCase.testFormAuthSubject: <no details avaliable>

org.jboss.as.test.integration.web.formauth.FormAuthUnitTestCase.testFormAuthException: <no details avaliable>

org.jboss.as.test.integration.web.formauth.FormAuthUnitTestCase.testFormAuth: <no details avaliable>

org.jboss.as.test.integration.web.formauth.FormAuthUnitTestCase.testPostDataFormAuth: <no details avaliable>

org.jboss.as.test.clustering.cluster.web.authentication.FormAuthenticationWebFailoverTestCase(SYNC-tcp).test: <no details avaliable>

org.jboss.as.test.manualmode.web.ssl.CertificateRolesLoginModuleTestCase.testDatabaseCertLoginModule: <no details avaliable>

org.jboss.as.test.manualmode.web.ssl.DatabaseCertLoginModuleTestCase.testDatabaseCertLoginModule: <no details avaliable>

org.jboss.as.test.manualmode.web.ssl.HTTPSWebConnectorTestCase.testVerifyingConnector: <no details avaliable>

org.jboss.as.test.manualmode.web.ssl.HTTPSWebConnectorTestCase.testNonVerifyingConnector: <no details avaliable>

org.jboss.as.test.manualmode.web.ssl.HTTPSWebConnectorTestCase.testDefaultConnector: <no details avaliable>

##### there are 2 more failed tests, see build details

WildFly pull requests Build 32 is now running using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a

WildFly pull requests Build 3688 outcome was FAILURE using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a
Summary: Snapshot dependencies failed: 2 Build time: 00:00:00

WildFly pull requests Build 34 is now running using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a

WildFly pull requests Build 3690 outcome was FAILURE using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a
Summary: Snapshot dependencies failed: 2 Build time: 00:00:01

WildFly pull requests Build 36 is now running using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a

WildFly pull requests Build 3692 outcome was FAILURE using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a
Summary: Snapshot dependencies failed: 2 Build time: 00:00:01

WildFly pull requests Build 38 is now running using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a

WildFly pull requests Build 3694 outcome was FAILURE using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a
Summary: Snapshot dependencies failed: 2 Build time: 00:00:01

WildFly pull requests Build 40 is now running using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a

WildFly pull requests Build 3696 outcome was FAILURE using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a
Summary: Snapshot dependencies failed: 2 Build time: 00:00:01

WildFly pull requests Build 42 is now running using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a

WildFly pull requests Build 3698 outcome was FAILURE using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a
Summary: Snapshot dependencies failed: 2 Build time: 00:00:00

WildFly pull requests Build 44 is now running using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a

WildFly pull requests Build 3700 outcome was FAILURE using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a
Summary: Snapshot dependencies failed: 2 Build time: 00:00:00

WildFly pull requests Build 46 is now running using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a

WildFly pull requests Build 3702 outcome was FAILURE using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a
Summary: Snapshot dependencies failed: 2 Build time: 00:00:01

WildFly pull requests Build 48 is now running using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a

WildFly pull requests Build 3704 outcome was FAILURE using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a
Summary: Snapshot dependencies failed: 2 Build time: 00:00:01

WildFly pull requests Build 50 is now running using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a

WildFly pull requests Build 3706 outcome was FAILURE using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a
Summary: Snapshot dependencies failed: 2 Build time: 00:00:01

WildFly pull requests Build 52 is now running using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a

WildFly pull requests Build 3708 outcome was FAILURE using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a
Summary: Snapshot dependencies failed: 2 Build time: 00:00:01

WildFly pull requests Build 54 is now running using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a

WildFly pull requests Build 3710 outcome was FAILURE using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a
Summary: Snapshot dependencies failed: 2 Build time: 00:00:01

WildFly pull requests Build 56 is now running using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a

WildFly pull requests Build 3712 outcome was FAILURE using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a
Summary: Snapshot dependencies failed: 2 Build time: 00:00:01

WildFly pull requests Build 58 is now running using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a

WildFly pull requests Build 3714 outcome was FAILURE using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a
Summary: Snapshot dependencies failed: 2 Build time: 00:00:00

WildFly pull requests Build 60 is now running using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a

WildFly pull requests Build 3716 outcome was FAILURE using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a
Summary: Snapshot dependencies failed: 2 Build time: 00:00:00

WildFly pull requests Build 62 is now running using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a

WildFly pull requests Build 3718 outcome was FAILURE using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a
Summary: Snapshot dependencies failed: 3 Build time: 00:00:00

WildFly pull requests Build 64 is now running using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a

WildFly pull requests Build 3720 outcome was FAILURE using a merge of b3a936425d7ceeb0299c012c885b38e358385e6a
Summary: Snapshot dependencies failed: 2 Build time: 00:00:00

Retest this please

Retest this please


Fix Cached_op with static_shape=true

Description
Should address https://github.com/apache/incubator-mxnet/issues/15281
@pengzhao-intel @TaoLv @junrushao1994 @zheng-da
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

https://github.com/apache/incubator-mxnet/issues/15297 should be fixed with this PR.

@anirudh2290 @roywei please take a review.

The segfault & core dump is fixed.
On sockeye side, I'm still getting 8 unit test failed with python3 setup.py test

============================================= 8 failed, 536 passed in 42.53 seconds ==============================================
Exception ignored in: <object repr() failed>
Traceback (most recent call last):
  File "/home/ubuntu/incubator-mxnet/python/mxnet/_ctypes/ndarray.py", line 51, in __del__
AttributeError: 'NoneType' object has no attribute 'MXNDArrayFree'

all failure seems to happen at sockeye side.
        # Bucket sentences as padded np arrays
>       for source, target in zip(source_list, target_sentences):
E       TypeError: zip argument #1 must support iteration

@roywei
On my side, sockeye has only 2 failures after this fix:
test/unit/test_data_io.py::test_parallel_sample_iter FAILED
test/unit/test_data_io.py::test_sharded_parallel_sample_iter FAILED
Those failures are also reproducible before merging trouble PR: https://github.com/apache/incubator-mxnet/commit/09202f7f261954383aa387144524d38f83f18d06.
So I think those sockeye failures doesn't relate to that PR.

@ZhennanQin Please verify the performance of this PR with our internal tests and NLP tests.
If everything is OI, I will merge this soon.

@PatricZhao Tested symbolic & gluon inference speed and bert, seems everything works fine.

Thanks, merging now.

Please pick up this fix to r1.5 branch.

@ZhennanQin Please verify the performance of this PR with our internal tests and NLP tests.
If everything is OK, I will merge this soon.

@pengzhao-intel - I will be very interested to learn more about what internal tests and benchmark setup you have. Main motivation is to see if some of these tests should be bought to Nightly CI.

@ZhennanQin Please verify the performance of this PR with our internal tests and NLP tests.
If everything is OK, I will merge this soon.

@pengzhao-intel - I will be very interested to learn more about what internal tests and benchmark setup you have. Main motivation is to see if some of these tests should be bought to Nightly CI.

@sandeep-krishnamurthy It's a good idea :) We have a branch of models and tested the latency and throughput for each CI so we can guarantee the performance of FP32 and INT8. Currently, the 2nd generation scalable processor is available in EC2, C5.12xlarge and C5.24xlarge.
Thus, it's good to move our tests (public models) into the nightly build.  Is it possible to set up these two type of instances for night run?

@ZhennanQin Please verify the performance of this PR with our internal tests and NLP tests.
If everything is OK, I will merge this soon.

@pengzhao-intel - I will be very interested to learn more about what internal tests and benchmark setup you have. Main motivation is to see if some of these tests should be bought to Nightly CI.

@sandeep-krishnamurthy It's a good idea :) We have a branch of models and tested the latency and throughput for each CI so we can guarantee the performance of FP32 and INT8. Currently, the 2nd generation scalable processor is available in EC2, C5.12xlarge and C5.24xlarge.
Thus, it's good to move our tests (public models) into the nightly build. Is it possible to set up these two type of instances for night run?

Thanks @pengzhao-intel - I will create a Github issue to discuss this with community members helping in CI and other activities around benchmarks/performance tests.


Reduce provisioner work

Fixes https://github.com/paritytech/polkadot/issues/5506
polkadot companion: https://github.com/paritytech/polkadot/pull/6328
✄ -----------------------------------------------------------------------------
Thank you for your Pull Request! 🙏
Before you submit, please check that:

[ ] Description: You added a brief description of the PR, e.g.:

What does it do?
What important points should reviewers know?
Is there something left for follow-up PRs?

[ ] Labels: You labeled the PR appropriately if you have permissions to do so:

[ ] A* for PR status (one required)
[ ] B* for changelog (one required)
[ ] C* for release notes (exactly one required)
[ ] D* for various implications/requirements
[ ] Github project assignment

[ ] Related Issues: You mentioned a related issue if this PR is related to it, e.g. Fixes #228 or Related #1337.
[ ] 2 Reviewers: You asked at least two reviewers to review. If you aren't sure, start with GH suggestions.
[ ] Style Guide: Your PR adheres to the style guide

In particular, mind the maximal line length of 100 (120 in exceptional circumstances).
There is no commented code checked in unless necessary.
Any panickers in the runtime have a proof or were removed.

[ ] Runtime Version: You bumped the runtime version if there are breaking changes in the runtime.
[ ] Docs: You updated any rustdocs which may need to change.
[ ] Polkadot Companion: Has the PR altered the external API or interfaces used by Polkadot?

[ ] If so, do you have the corresponding Polkadot PR ready?
[ ] Optionally: Do you have a corresponding Cumulus PR?

Refer to the contributing guide for details.
After you've read this notice feel free to remove it.
Thank you!
✄ -----------------------------------------------------------------------------

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2066137

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2066139

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2066216

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2066393

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2066399

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2067682

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2067873

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2069610

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2069611

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2069612

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2069783

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2070009

The CI pipeline was cancelled due to failure one of the required jobs. Job name: cargo-check-benches Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2070009

@bkchr I tried fixing this with the suggestion the compiler throws at me but it's not helping at all. I also tried use crate::InherentDataProvider but then I get told it's unused. Any idea?
Also please let me know if I should be asking somewhere/-one else in general.

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2072359

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2086512

The CI pipeline was cancelled due to failure one of the required jobs. Job name: cargo-check-benches Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2070009

@bkchr I tried fixing this with the suggestion the compiler throws at me but it's not helping at all. I also tried use crate::InherentDataProvider but then I get told it's unused. Any idea?
Also please let me know if I should be asking somewhere/-one else in general.

Signatures seem to be incompatible. Impl vs trait declaration. The impl adds an additional parameter "data".

The CI pipeline was cancelled due to failure one of the required jobs. Job name: cargo-check-benches Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2070009

@bkchr I tried fixing this with the suggestion the compiler throws at me but it's not helping at all. I also tried use crate::InherentDataProvider but then I get told it's unused. Any idea?
Also please let me know if I should be asking somewhere/-one else in general.

I rerun the test as they succeed for me locally, now it passed. Maybe some caching issue?

The CI pipeline was cancelled due to failure one of the required jobs. Job name: cargo-check-benches Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2070009

@bkchr I tried fixing this with the suggestion the compiler throws at me but it's not helping at all. I also tried use crate::InherentDataProvider but then I get told it's unused. Any idea?
Also please let me know if I should be asking somewhere/-one else in general.

I rerun the test as they succeed for me locally, now it passed. Maybe some caching issue?

Yes could be

bot rebase


can't download a magnet URI

It's entirely possible that I'm setting up webtorrent wrong, but I can't get this simple seed+download test to work in both node, electron, and I was getting the same behavior with a similar setup for the browser. Originally I thought the problem was related to streaming, but the problem is present with files and buffers too.
If I change:
client.add(torrent.magnetURI, function (dl) {

to:
client.add(torrent, function (dl) {

then this test works. Maybe there is an issue with trackers or magnet links? I haven't made much progress on what might be causing this issue.

@substack Thanks for the test case! I'll see what I can figure out.

@substack I figured it out! Fixed in v0.74.0.
Thanks for the test - it was really helpful while debugging this. Let me know if you run into any other issues!


LaTeX in examples on the website are broken

Sorry if this isn't the appropriate place to report, but on the project website the examples involving LaTeX code are currently broken.
For example, the URL http://www.forkosh.com/mathtex.cgi?x_1+2x_2\leq1 returns a 502 error.
Personally, I've found CodeCogs to be useful for such a purpose. The equivalent URL for the example above is: https://latex.codecogs.com/gif.download?x_1+2x_2\leq1
Therefore, fixing the issue would hopefully be a matter of replacing http://www.forkosh.com/mathtex.cgi with https://latex.codecogs.com/gif.download.

Thanks for the pointer. It is now fixed. Sorry for the delay - we have seen this quite late ;-)

Thanks!


Use delta-compression to network ActionState?

We network ActionState directly from server to client when we want to do remote-player prediction. We need to know the other players' input states to be able to correctly predict them.

Currently we just network the entire component value; but maybe we can network diffs?

Inputs are now replicated only via InputMessage instead of ActionState


Make main activity detection more solid

Addresses https://github.com/rnpm/rnpm-plugin-link/issues/26
I completely removed the "getPrefix.js" file along with a ton of other code, because they are no longer needed, I hope you guys don't mind :p. There is now only a single "makeMainActivityPatch.js" that handles all the logic of detecting the type of MainActivity (whether it extends Activity or ReactActivity), and applying the appropriate patch.

+30 -140
I love it! Thanks for that :) Waiting for @Kureev to dbl check and I think we can merge that in!

I'm busy with refactoring patch system for Android right now. I think after that we can try to merge it in (but it'll require some additional efforts)

Isn't this something you could try merging into your branch? (would be cool if you could submit some changes so we can check as you work!)
This looks like a small improvement and since it removes ~140 lines, it could save you a bit of time.

@grabbou this wouldn't scale: https://github.com/rnpm/rnpm-plugin-link/pull/69/files#diff-9be25dfa687d08b7f584875b08c5b1feR11


function  based-view to get data  from the Django session

Hi
I am attempting to integrate the Chargily API into my website developed by Django, How I can integrate the API using function-based-view to get data (mode and amount etc) from the Django session without using the API form?
best regard

Hello @bouchouichaAek,
I trust you're doing well. To implement a function-based-view in chargily-epay-django, I'd like to suggest taking a closer look at how we've implemented this functionality using class-based-views. Adapting this code to suit your needs shouldn't be too challenging.
you can find here  the code source of our class-based-view function.


Test, do not approve. kbqwgb

Test, do not approve. kbqwgb

:grey_exclamation: Build Aborted

The PR is not allowed to run in the CI yet

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2023-04-15T19:01:05.523+0000

Duration: 2 min 50 sec

Steps errors
Expand to view the steps failures

Load a resource file from a library

Took 0 min 0 sec . View more details here
Description: approval-list/elastic/elastic-agent-libs.yml

Error signal

Took 0 min 0 sec . View more details here
Description: githubApiCall: The REST API call https://api.github.com/orgs/elastic/members/hamustabakube return the message : java.lang.Exception: httpRequest: Failure connecting to the service https://api.github.com/orgs/elastic/members/hamustabakube : httpRequest: Failure connecting to the service https://api.github.com/orgs/elastic/members/hamustabakube : Code: 404Error: {"message":"User does not exist or is not a member of the organization","documentation_url":"https://docs.github.com/rest/reference/orgs#check-organization-membership-for-a-user"}

:robot: GitHub comments
Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.


Navigator operation requested with a context that does not include a Navigator

Version Information

Flutter version: 3.22.2
flutter_smart_dialog version: 4.9.6+1

Describe the bug/requirement
════════ Exception caught by gesture ═══════════════════════════════════════════
The following assertion was thrown while handling a gesture:
Navigator operation requested with a context that does not include a Navigator.
The context used to push or pop routes from the Navigator must be that of a widget that is a descendant of a Navigator widget.

Problem demo
          await SmartDialog.show<String?>(
            builder: (context) => DropdownButton<String>(
              items: const [
                DropdownMenuItem(
                  child: Text("data"),
                ),
              ],
              onChanged: (t) {
                print("object $t");
              },
            ),
          );

上面这段简单的例子，执行的时候就报错了：Navigator operation requested with a context that does not include a Navigator.\
请问有没有解决的办法？

DropdownButton依赖了路由, useSystem设置为tue试试

DropdownButton依赖了路由, useSystem设置为tue试试

useSystem: true，一样报这个错误：
The following assertion was thrown while handling a gesture:
Navigator operation requested with a context that does not include a Navigator.
The context used to push or pop routes from the Navigator must be that of a widget that is a descendant of a Navigator widget.

https://github.com/fluttercandies/flutter_smart_dialog/issues/11

#11

谢谢，已经解决
          await SmartDialog.show<String?>(
            builder: (context) {
              return Navigator(
                onGenerateRoute: (settings) => MaterialPageRoute(
                  builder: (context) => FlutterSmartDialog(
                    child: DropdownButton<String>(
                      items: const [
                        DropdownMenuItem(
                          child: Text("data"),
                        ),
                      ],
                      onChanged: (t) {
                        print("object $t");
                      },
                    ),
                  ),
                ),
              );
            },
          );

await SmartDialog.show(
  builder: (context) {
    return Navigator(
      onGenerateRoute: (settings) => MaterialPageRoute(
        builder: (context) => DropdownButton<String>(
          items: const [DropdownMenuItem(child: Text("data"))],
          onChanged: (t) => print("object $t"),
        ),
      ),
    );
  },
);

SmartDialog.show(
  builder: (context) {
    return MaterialApp(
      home: DropdownButton<String>(
        items: const [DropdownMenuItem(child: Text("data"))],
        onChanged: (t) => print("object $t"),
      ),
    );
  },
);

SmartDialog.show(
  builder: (context) {
    return MaterialApp(
      home: DropdownButton<String>(
        items: const [DropdownMenuItem(child: Text("data"))],
        onChanged: (t) => print("object $t"),
      ),
    );
  },
);

这么用home里面某些组件会出现高亮下划线的问题，还是Navigator这个能解决问题。