availabilityStatus "AVAILABLE" does not seem to be enough anymore for document replacement

I've recently tried to replace a document but always got the error
      [WriteDocumentException] Not yet handled: com.oviva.epa.client.model.WriteDocumentException: failed to write document
      status='writing document failed, status='urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Failure'',
      errors='Error[value=, codeContext=SyntaxErrorException: SYNTAX_ERROR(7510) - Business: Fehlerhafte Aufrufparameter.
      Detail: Only an approved DocumentEntry can be target of an urn:ihe:iti:2007:AssociationType:RPLC DE-DE association,
      errorCode=XDSRepositoryError, severity=urn:oasis:names:tc:ebxml-regrep:ErrorSeverityType:Error, location=null]'

after some unsuccessful trying around, I found here https://fachportal.gematik.de/fachportal-import/files/gemSpec_DM_ePA_V1.7.0.pdf (page 12, in the end), that availabilityStatus should be Approved or Deprecated.
AFAIK, for the initial creation of a document, this doesn't matter, but when replacing a document, it certainly does.
I've seen that you have still AVAILABLE in your tests, that is why I'm mentioning it ( diga-epa-client/src/test/java/com/oviva/epa/client/KonnektorServiceAcceptanceTest.java )
Solution: set the availabilityStatus for all documents to urn:oasis:names:tc:ebxmlregrep:StatusType:Approved

Nevermind. I thought the new availabilityStatus fixes the issue. I was wrong. More investigation necessary.


In dev, warn and exit if cable.yml and db yml are missing

bin/setup is responsible for automatically copying these files.
Since you could intentionally remove them, we'll just warn in bin/update.

Good call @skateman, I'll add that.

Ok, @himdel @skateman updated.  I let travis run this just to ensure I didn't break CI.

Works just fine :) If we ever accumulate more than 2 checks, it may make sense to postpone dying until all the checks have carped, but until then.. :)
@jrafanie, @skateman since this is devel-only, I don't see a reason to euwe/yes this, do you?


🐛 TOO_MANY_OPEN_CAMERAS error when rendering multiple Cameras

What's happening?
TOO_MANY_OPEN_CAMERAS is still thrown with 3.7.0 on Android
Reproduceable Code
Check this repo https://github.com/xseignard/black-screen and navigate between screens
Relevant log output
2024-01-11T11:51:52.930Z	29542	PreviewView	Creating PreviewView...
	2024-01-11T11:51:52.931Z	29542	PreviewView	Content Size: 1920x1080 (0.5625) | Container Size: 0x0 (NaN)
	2024-01-11T11:51:52.931Z	29542	PreviewView	PreviewView is 0x0, rendering 1920x1080 content. Resizing to: 0x0 (COVER)
	2024-01-11T11:51:52.933Z	29542	CameraView	Updating CameraSession...
	2024-01-11T11:51:52.934Z	29542	CameraSession	configure { ... }: Waiting for lock...
	2024-01-11T11:51:52.936Z	29542	CameraSession	configure { ... }: Updating CameraSession Configuration... Difference(deviceChanged=true, outputsChanged=true, sidePropsChanged=true, isActiveChanged=true)
	2024-01-11T11:51:52.936Z	29542	CameraSession	isActive is false, skipping CameraDevice configuration.
	2024-01-11T11:51:52.936Z	29542	CameraSession	isActive is false, skipping CameraCaptureSession configuration.
	2024-01-11T11:51:52.936Z	29542	CameraSession	Successfully updated CameraSession Configuration! isActive: false
	2024-01-11T11:51:53.080Z	29542	CameraView	Updating CameraSession...
	2024-01-11T11:51:53.081Z	29542	CameraSession	configure { ... }: Waiting for lock...
	2024-01-11T11:51:53.082Z	29542	CameraSession	configure { ... }: Updating CameraSession Configuration... Difference(deviceChanged=true, outputsChanged=true, sidePropsChanged=true, isActiveChanged=true)
	2024-01-11T11:51:53.082Z	29542	CameraSession	Need to rebuild CameraDevice and CameraCaptureSession...
	2024-01-11T11:51:53.083Z	29542	CameraSession	Configuring Camera #1...
	2024-01-11T11:51:53.083Z	29542	CameraManager	Camera #1: Opening...
	2024-01-11T11:51:53.086Z	29542	PreviewView	Content Size: 1920x1080 (0.5625) | Container Size: 1080x1918 (0.5630865484880083)
	2024-01-11T11:51:53.087Z	29542	PreviewView	PreviewView is 1080x1918, rendering 1920x1080 content. Resizing to: 1080x1920 (COVER)
	2024-01-11T11:51:53.088Z	1969	System.err	java.lang.SecurityException: Caller with uid 1047 is not android
	2024-01-11T11:51:53.088Z	1969	System.err		at com.android.server.devicepolicy.DevicePolicyManagerService.getCallerIdentity(DevicePolicyManagerService.java:2368)
	2024-01-11T11:51:53.088Z	1969	System.err		at com.android.server.devicepolicy.DevicePolicyManagerService.getCameraDisabled(DevicePolicyManagerService.java:9311)
	2024-01-11T11:51:53.088Z	1969	System.err		at android.app.admin.DevicePolicyManager.getCameraDisabled(DevicePolicyManager.java:8423)
	2024-01-11T11:51:53.088Z	1969	System.err		at com.android.server.camera.CameraServiceProxy$2.isCameraDisabled(CameraServiceProxy.java:622)
	2024-01-11T11:51:53.088Z	1969	System.err		at android.hardware.ICameraServiceProxy$Stub.onTransact(ICameraServiceProxy.java:174)
	2024-01-11T11:51:53.088Z	1969	System.err		at android.os.Binder.execTransactInternal(Binder.java:1344)
	2024-01-11T11:51:53.088Z	1969	System.err		at android.os.Binder.execTransact(Binder.java:1275)
	2024-01-11T11:51:53.088Z	1645	CameraService	CameraService::connect call (PID 29542 "com.xseignard.blackscreen", camera ID 1) and Camera API version 2
	2024-01-11T11:51:53.089Z	1645	Camera2ClientBase	Camera 1: Opened. Client: com.xseignard.blackscreen (PID 29542, UID 10618)
	2024-01-11T11:51:53.089Z	1645	CameraDeviceClient	CameraDeviceClient 1: Opened
	2024-01-11T11:51:53.089Z	1645	CameraService	makeClient: Camera2 API, override to portrait 0
	2024-01-11T11:51:53.089Z	1304	GCH_CameraDeviceHwlImpl	CreateCameraDeviceSessionHwl CAMERA_LAUNCH 1
	2024-01-11T11:51:53.090Z	1304	GCH_HwlResultDispatcher	ResultDispatcherHwl: SetRealtimeThread OK
	2024-01-11T11:51:53.090Z	1304	GCH_CameraVendorModule	ValidateConcurrentOpen: All cameras should be opened before any session is configured.
	2024-01-11T11:51:53.090Z	1304	GCH_CameraDeviceSessionHwlImpl	DestroyPipelinesLocked Destroying pipelines
	2024-01-11T11:51:53.090Z	1304	GCH_HwlResultDispatcher	ResultDispatcherThread Result dispatcher thread is existing . . .
	2024-01-11T11:51:53.090Z	1304	GCH_CameraDevice	CreateCameraDeviceSession: Creating a CameraDeviceSessionHwl failed: Too many users(-87)
	2024-01-11T11:51:53.090Z	1304	GCH_AidlCameraDevice	open: Creating CameraDeviceSession failed: Too many users(-87)
	2024-01-11T11:51:53.090Z	1645	CameraProviderManager	openAidlSession: Transaction error opening a session for camera device 1:
	2024-01-11T11:51:53.090Z	1645	Camera3-Device	Camera 1: initialize: Could not open camera session: Too many users (-87)
	2024-01-11T11:51:53.090Z	1645	Camera2ClientBase	initializeImpl: Camera 1: unable to initialize device: Too many users (-87)
	2024-01-11T11:51:53.090Z	1645	CameraService	connectHelper: Could not initialize client from HAL.
	2024-01-11T11:51:53.090Z	1645	Camera2ClientBase	Camera 1: start to disconnect
	2024-01-11T11:51:53.090Z	1645	Camera2ClientBase	Camera 1: serializationLock acquired
	2024-01-11T11:51:53.090Z	1645	Camera2ClientBase	Camera 1: Shutting down
	2024-01-11T11:51:53.090Z	1645	Camera2ClientBase	Camera 1: start to cacheDump
	2024-01-11T11:51:53.099Z	1645	Camera3-Device	disconnectImpl: E
	2024-01-11T11:51:53.099Z	1645	CameraService	disconnect: Disconnected client for camera 1 for PID 29542
	2024-01-11T11:51:53.099Z	1645	cameraserver	FGS Logger Transaction failed
	2024-01-11T11:51:53.099Z	1645	cameraserver	-129
	2024-01-11T11:51:53.099Z	1645	Camera2ClientBase	~Camera2ClientBase: Client object's dtor for Camera Id 1 completed. Client was: com.xseignard.blackscreen (PID 29542, UID 10618)
	2024-01-11T11:51:53.099Z	1645	Camera3-Device	disconnectImpl: E
	2024-01-11T11:51:53.099Z	3182	HbmSvManager	 Request state 0 req 1
	2024-01-11T11:51:53.100Z	29542	CameraManager	Camera #1: Error! 2
	2024-01-11T11:51:53.102Z	29542	CameraSession
	2024-01-11T11:51:53.102Z	29542	CameraView	invokeOnError(...):
	2024-01-11T11:51:53.102Z	29542	System.err	com.mrousavy.camera.core.CameraCannotBeOpenedError: [session/camera-cannot-be-opened] The given Camera device (id: 1) could not be opened! Error: TOO_MANY_OPEN_CAMERAS
	2024-01-11T11:51:53.102Z	29542	System.err		at com.mrousavy.camera.extensions.CameraManager_openCameraKt$openCamera$2$callback$1.onError(CameraManager+openCamera.kt:47)
	2024-01-11T11:51:53.102Z	29542	System.err		at android.hardware.camera2.impl.CameraDeviceImpl$8.run(CameraDeviceImpl.java:385)
	2024-01-11T11:51:53.102Z	29542	System.err		at android.os.Handler.handleCallback(Handler.java:958)
	2024-01-11T11:51:53.102Z	29542	System.err		at android.os.Handler.dispatchMessage(Handler.java:99)
	2024-01-11T11:51:53.102Z	29542	System.err		at android.os.Looper.loopOnce(Looper.java:205)
	2024-01-11T11:51:53.102Z	29542	System.err		at android.os.Looper.loop(Looper.java:294)
	2024-01-11T11:51:53.103Z	29542	System.err		at android.os.HandlerThread.run(HandlerThread.java:67)
	2024-01-11T11:51:53.106Z	29542	CameraSession	PreviewView Surface created! Surface(name=null)/@0xd306005
	2024-01-11T11:51:53.106Z	29542	CameraSession	Setting Preview Output...
	2024-01-11T11:51:53.106Z	29542	CameraSession	PreviewView Surface updated! Surface(name=null)/@0xd306005 1080 x 1920
	2024-01-11T11:51:53.106Z	29542	CameraSession	configure { ... }: Waiting for lock...
	2024-01-11T11:51:53.107Z	29542	CameraSession	configure { ... }: Updating CameraSession Configuration... Difference(deviceChanged=false, outputsChanged=true, sidePropsChanged=true, isActiveChanged=false)
	2024-01-11T11:51:53.107Z	29542	CameraSession	isActive is false, skipping CameraCaptureSession configuration.
	2024-01-11T11:51:53.107Z	29542	CameraSession	Successfully updated CameraSession Configuration! isActive: false
	2024-01-11T11:51:53.123Z	29542	ReactNativeJS	{ [session/camera-cannot-be-opened: [session/camera-cannot-be-opened] The given Camera device (id: 1) could not be opened! Error: TOO_MANY_OPEN_CAMERAS]
  name: 'session/camera-cannot-be-opened',
  _code: 'session/camera-cannot-be-opened',
  _message: '[session/camera-cannot-be-opened] The given Camera device (id: 1) could not be opened! Error: TOO_MANY_OPEN_CAMERAS',
  _cause: undefined }

Camera Device
{
  "sensorOrientation": "landscape-right",
  "hardwareLevel": "full",
  "maxZoom": 7,
  "minZoom": 0.6150000095367432,
  "maxExposure": 24,
  "supportsLowLightBoost": false,
  "neutralZoom": 1,
  "physicalDevices": [
    "wide-angle-camera",
    "ultra-wide-angle-camera"
  ],
  "supportsFocus": true,
  "supportsRawCapture": true,
  "isMultiCam": true,
  "minExposure": -24,
  "name": "BACK (0)",
  "hasFlash": true,
  "hasTorch": true,
  "position": "back",
  "id": "0"
}

Device
Pixel 5 (Android 14)
VisionCamera Version
3.7.0
Can you reproduce this issue in the VisionCamera Example app?
I didn't try (⚠ your issue might get ignored & closed if you don't try this)
Related issues
#1958 #2240
Additional information

[X] I am using Expo
[ ] I have enabled Frame Processors (react-native-worklets-core)
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

Hm, I wonder what's going on here.
The ideal behaviour should be that a new Camera that has isActive is true will take precedence over older Cameras. We need to close older Cameras before opening a new one.
It is normally recommended to just stop the repeating request (captureSession?.stopRepeating()) so that the Camera is available again faster when you open it again - but if you don't open it again, Android OS will close the Camera for you (onDisconnected).
I am wondering now if we need to close the device manually ourselves when isActive is set to false?
Camera2 is so weirdly designed...

The only thing that fixes this issue for me is this https://github.com/mrousavy/react-native-vision-camera/pull/2157
I don't say it is the right way to fix the issue, but at least I works 🤷

Okay thanks - that helps. I have a different idea that should ideally be much more stable, but I need to figure out how to deliver that - quite complex to handle all the threading etc here

Working on a fix for this issue here: https://github.com/mrousavy/react-native-vision-camera/pull/2494 👀
Still in development, so don't test yet. Long way to go, this is a really complicated issue (as you can see in the changes/Files of that PR)...

Just released VisionCamera 3.9.0-beta.1, which includes the big PersistentCaptureSession PR that aims to fix all the blackscreen issues.... :eyes::tada:
You can try that new beta out yourself and let me know if you still encounter blackscreen issues. I'll continue to test on more devices in the meantime, organize the code a bit better, and then I'll tackle the preview stretching, focus, and flash issues!
If that fixes the blackscreen issues for you, please consider sponsoring me on GitHub to say thanks! ❤

Hello @mrousavy
I just tried on my repro project: https://github.com/xseignard/black-screen and the same exact issue is still occurring 🤷

If that fixes the blackscreen issues for you, please consider sponsoring me on GitHub to say thanks! ❤

I actually already sponsor you through my company (https://github.com/alan-eu)

Yet another attempt to fix this in this PR https://github.com/mrousavy/react-native-vision-camera/pull/2539

Let's re-open if the issue still exists!
I'll try to take another look at this, but the PR closes the session which goes against the Closeable paradigm.

First of all many thanks Marc for working on this issue! I tried many recommendations from other threads and latest library version, but camera doesn't work properly. BUT! The device I have is also my main phone (Redmi Note Pro 10) and I often have a similar (same?) problem with other apps: telegram, snapchat, instagram and even original camera app. I am not encouraging to blame hardware and give up, but wanted to share this information anyways.

hahaha okay well I'm currently in a bar so I don't know if my input is valuable but if not even the stock camera app (or Snapchat, which I consider a good camera app) work there's not a lot I can do 😂
I wonder what the actual issue is tho, can u share logs?

@mrousavy
Good afternoon. Reproduced the error in your "com.mrousavy.camera.example" project ("version": "3.9.0")
Steps to reproduce (video):

Grant permissions after the first launch of the application
Go to the Camera screen
Switch the camera to "front"
Open the Qr scanner screen
The camera screen turns black

If you do not switch the camera in step 2, then everything works and the error does not reproduce
Xiaomi Redmi 12 screenshots:
black screen
error
AndroidStudio screenshots:
logcat
I hope you will solve the problem soon, because now this is a blocker for us, as well as for the rest of the community 🫶

Seems like issue with Xiaomi Phones. I am also facing this error in Xiaomi Redmi Note 10S.

Hey! I just released a new V4 beta (v4.0.0-beta.7) where I fixed a bunch of issues! 💪🚀 Can you test that and see if that fixes the issue for you? 😅
yarn add react-native-vision-camera@beta

You might need to increase the compileSdk to the newest Android SDK (34) if you are behind.

Hey :wave:
Thanks for the v4 release, I just tested on:

Samsung Galaxy A54
Pixel 5
Huawei P30 Lite

for this specific issue only
And v4.0.0-beta.8 does fix this issue :partying_face:
Thanks for the hard work 🙇

Great to hear!

Great to hear that V4 now works perfectly! If you appreciate my work, please consider 💖 sponsoring me on GitHub 💖 so I can keep maintaining this library, fixing bugs and building new features! :)

Hey - I think this issue has been fixed in VisionCamera 4.0.0. 🥳
Please try V4 and let me know if you still experience this issue;

if not, please consider 💖 sponsoring me on GitHub 💖 to support the development of VisionCamera and thank me for my time spent on fixing bugs and building new features.
if you still see this issue, please comment and we can re-open this. But please update your native logs with the native (Xcode/Android Studio) logs from running VisionCamera V4 so I can investigate this.


Replace Welcome Screen Assets

The assets of the welcome screen still have that old typo. These new ones are the same size and aspect ration, but no text: also localization-proof if we don't get to finish the refresh of this page.

@jprvita

Hi @jofilizola! Just to be sure, is it intentional that these new assets are zoomed out a bit more than the originals? The old ones were cropped differently, like https://github.com/endlessm/kolibri-explore-plugin/blob/2bc544ad2fd733b74230bf2e635bc96320492232/packages/welcome-screen/src/assets/welcome-bg-bottom-left.jpg.
I added a comparison in https://github.com/endlessm/kolibri-explore-plugin/pull/757#issuecomment-1683158456.

Ha! I think I exported the full assets and Manuel cropped them. Here they are, cropped the same.

Here how it looks with the new assets:

And the original ones, for comparison:

If you look very closely you can tell the new assets are a tiny bit more "zoomed out" (ex., the new "read aloud" tile has a smaller piece cut-off), but I don't think it matters or have any negative effect, so I'm marking the PR as ready for review + merging again.

Looks good to me! Thank you, thank you!

Merged!

And built https://github.com/endlessm/kolibri-explore-plugin/actions/runs/5904366677

Verified Passed in Chromebook Manatee 6.38-389 & Windows <IP_ADDRESS>


Use proper minimum amounts for Forex AMM

Closes #240
I also streamlined some typings, calculations and namings that I found along the code path I had to change.
This function adds the two configuration constants

AMM_MINIMUM_OUTPUT_SOFT_MARGIN = 0.02
AMM_MINIMUM_OUTPUT_HARD_MARGIN = 0.05

The determine the "soft" and "hard" margins:

The hard margin is the one we use for the minimum amount in the transaction. The transaction will fail and revert when the resulting output amount would be less. In that case the transaction cannot be submitted again as the nonce of the ephemeral account will already increase. The funds would become eternally locked.
The soft margin is the one we use to check the quote again directly before submitting the swap transaction. If the quote is less than this margin, we don't submit the transaction in the first place and transition to the failure state. This allows to retry later or for us to continue the process manually as the swap transaction is not wasted.

Why would you even want to distinguish between the soft and hard margin

It is quite a problem if the swap transaction is submitted but reverts. For the current early version that means that the funds are unrecoverably lost (apart from issuing a root transaction).
I wanted to have a way to make this safe and don't even submit the transaction if the current quote deviates too far. But even then there is still some risk that the result changes again between requesting the quote and executing the call.
Alternatively, we could just set the minimum amount in the swap transaction to 0 (this sounded risky to me) or set the minimum amount to the current (i.e., directly after the AMM approval transaction has been submitted and before submitting the swap transaction) quote minus some margin. I think in practice all 3 solutions probably work equally well.

But even then there is still some risk that the result changes again between requesting the quote and executing the call.

I see. So the main reason we don't submit if x < soft_margin is to not get to a situation where the swap reverts.


Adding sync api support for cosmos encryption

Adding sync api support for cosmos encryption.
Public surface changes in Cosmos project -

Added sync CosmosClientEncryptionKey proxy object
Added CosmosClientEncryptionKey apis in CosmosDatabase

Public surface changes in Cosmos encryption project -

Added CosmosEncryptionClient
Added CosmosEncryptionDatabase
Added CosmosEncryptionContainer

/check-enforcer override


AddArray() does not respect initial capacity of Lists

https://github.com/Scobalula/Cast.NET/blob/7cf3dac687047d5c843763abd448b5a7675efa7f/examples/Cast.NET.Example.GltfToCast/Program.cs#L71
Based on the examples I expected AddArray() to use the instance which was passed in and that's why capacity is set, but that does not seem to be the case. Instead it creates another instance with the same values/elements AND ignores capacity, which makes me confused.
Is this the intended behavior of AddArray()?
I can see it being somewhat useful for non-empty Lists as a way to also implicitly Trim them but like in the example for empty ones specifying a capacity —if known— is I believe better to avoid resizing of the internal array.

Unfortunately this library is not receiving support and I will now archive it, unless Cast itself receives more support in general, consider this unsupported.


GJP Page returns a 404 Page.

On the uploadGJComment21 page I clicked the GJP thing to see details about that, but it took me to the 404 page for some reason.

known issue, should be fixed soon. it is essentially this but the xor key is 37526


Add more options for controlling which tests run

It would be nice to have some arguments to pass to pytest that can enable more control over which tests run. The current test suite takes something like 10 minutes to run if only doing the unit tests and about twice that if including examples. There is huge variance in different parts of the test suite, i.e. all of test_parameters.py takes ~10 seconds and just running the serialization tests in test_molecule.py takes about a minute or two despite being stable (on the timescale of a few commits). At different times, one might want to have some of these turned off or on, i.e. to check that a change didn't break the Molecule API, but doing so without running all serialization tests for all molecules and file formats.
Describe the solution you'd like
Some clever use of pytest.mark(https://docs.pytest.org/en/stable/example/markers.html) would enable the toggling on/off ofcategories of tests, i.e.

Serialization (through to_dict formats and {to|from}_file methods)
Parametrizing of molecules
Cheminformatics round-trips (SMILES, IUPAC, etc.)
Molecule.{to_from}_{rdkit|openeye}
Assigning charges
etc.

From a set of options, we can choose the default tests to run for different purposes, i.e. running more tests on nightly cron jobs than normal CI runs. Even if most are on by default, markers could enable focusing on just a set of functionality, i.e. pytest -v -m serialization to only run serialization tests.
Describe alternatives you've considered
In some cases, you can point pytest to a particular TestClass and only run its tests, but that requires a fair amount of intervention and only gives so much control. What often happens is needing to pick between waiting 10+ minutes for all tests to run before pushing a commit(s) or pushing "I think this will work, but I'm not sure" commits and waiting 20-30 minutes for CI to report back.
Additional context
The existing --runslow option (which was recently fixed #707) captures something similar to this idea, but with less granularity.

FWIW, the culprits for examples running fairly slow seem to be those that deal with swapping parameters; each swap_amber_parameters notebook takes ~4 mins
2020-09-15T14:19:41.5005420Z examples/QCArchive_interface/QCarchive_interface.ipynb ..........F.      [ 10%]
2020-09-15T14:19:52.9318940Z examples/SMIRNOFF_simulation/run_simulation.ipynb .......                [ 16%]
2020-09-15T14:19:55.8584790Z examples/check_dataset_parameter_coverage/check_parameter_coverage.ipynb . [ 17%]
2020-09-15T14:20:13.4364370Z ........                                                                 [ 24%]
2020-09-15T14:21:20.7447270Z examples/conformer_energies/conformer_energies.ipynb ....                [ 27%]
2020-09-15T14:21:26.3866390Z examples/forcefield_modification/ManipulateParameters.ipynb ............ [ 37%]
2020-09-15T14:21:39.8035260Z .......                                                                  [ 43%]
2020-09-15T14:21:43.2907910Z examples/inspect_assigned_parameters/inspect_assigned_parameters.ipynb . [ 44%]
2020-09-15T14:21:47.4717100Z .                                                                        [ 45%]
2020-09-15T14:21:57.4420660Z examples/swap_amber_parameters/swap_existing_ligand_parameters.ipynb ... [ 48%]
2020-09-15T14:25:41.6262260Z .............                                                            [ 59%]
2020-09-15T14:25:43.9689300Z examples/swap_amber_parameters/swap_existing_ligand_parameters_with_openmmforcefields.ipynb . [ 60%]
2020-09-15T14:29:06.9583000Z .............                                                            [ 71%]
2020-09-15T14:29:09.8463410Z examples/using_smirnoff_in_amber_or_gromacs/convert_to_amber_gromacs.ipynb . [ 72%]
2020-09-15T14:29:13.5491860Z .......                                                                  [ 78%]
2020-09-15T14:29:15.6338380Z examples/using_smirnoff_with_amber_protein_forcefield/BRD4_inhibitor_benchmark.ipynb . [ 79%]
2020-09-15T14:29:48.2302900Z ........                                                                 [ 86%]
2020-09-15T14:29:51.1549340Z examples/using_smirnoff_with_amber_protein_forcefield/toluene_in_T4_lysozyme.ipynb . [ 87%]
2020-09-15T14:30:09.3719280Z ......                                                                   [ 92%]
2020-09-15T14:30:14.2494480Z examples/visualization/visualization.ipynb ....sssss                     [100%]
2020-09-15T14:30:14.2495340Z

Another motivation/idea (credit @SimonBoothroyd) might be to skip the notebooks and some other slow tasks on CI jobs that are close to dev iterations, which ideally are as fast as possible while covering usage and catching potential breaks, but to enable them at other points (nightly cron jobs, some step in the release process) in which the trade-off of test duration and coverage is different.


Force a black reformat for fewer lines.

Codecov Report
Base: 28.70% // Head: 28.70% // No change to project coverage :thumbsup:

Coverage data is based on head (4fa0159) compared to base (18c324e).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##           stable    #1079   +/-   ##
=======================================
  Coverage   28.70%   28.70%
=======================================
  Files          72       72
  Lines        5852     5852
  Branches      306      306
=======================================
  Hits         1680     1680
  Misses       4109     4109
  Partials       63       63

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


🐛[BUG]: aero_graph_net failed to load dataset

Version
0.8.0
On which installation method(s) does this occur?
No response
Describe the issue
Failed to load dataset when trying to train aero_graph_net.
Is there any way to fix this?
it stuck in the hydra instantiation as shown in the error log.
Minimum reproducible example

Relevant log output
[18:55:46 - agnet - INFO] Loading the training dataset...
Error executing job with overrides: ['+experiment=ahmed/mgn', 'data.data_dir=./data/ahmed_body']
concurrent.futures.process._RemoteTraceback:
'''
Traceback (most recent call last):
  File "/home/willy/anaconda3/envs/modulus/lib/python3.10/concurrent/futures/process.py", line 392, in wait_result_broken_or_wakeup
    result_item = result_reader.recv()
  File "/home/willy/anaconda3/envs/modulus/lib/python3.10/multiprocessing/connection.py", line 251, in recv
    return _ForkingPickler.loads(buf.getbuffer())
  File "/home/willy/anaconda3/envs/modulus/lib/python3.10/site-packages/torch/multiprocessing/reductions.py", line 496, in rebuild_storage_fd
    fd = df.detach()
  File "/home/willy/anaconda3/envs/modulus/lib/python3.10/multiprocessing/resource_sharer.py", line 58, in detach
    return reduction.recv_handle(conn)
  File "/home/willy/anaconda3/envs/modulus/lib/python3.10/multiprocessing/reduction.py", line 189, in recv_handle
    return recvfds(s, 1)[0]
  File "/home/willy/anaconda3/envs/modulus/lib/python3.10/multiprocessing/reduction.py", line 164, in recvfds
    raise RuntimeError('received %d items of ancdata' %
RuntimeError: received 0 items of ancdata
'''

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/willy/anaconda3/envs/modulus/lib/python3.10/site-packages/hydra/_internal/instantiate/_instantiate2.py", line 92, in _call_target
    return _target_(*args, **kwargs)
  File "/home/willy/anaconda3/envs/modulus/lib/python3.10/site-packages/modulus/datapipes/gnn/ahmed_body_dataset.py", line 219, in __init__
    for (i, graph, coeff, normal, area) in executor.map(
  File "/home/willy/anaconda3/envs/modulus/lib/python3.10/concurrent/futures/process.py", line 575, in _chain_from_iterable_of_lists
    for element in iterable:
  File "/home/willy/anaconda3/envs/modulus/lib/python3.10/concurrent/futures/_base.py", line 621, in result_iterator
    yield _result_or_cancel(fs.pop())
  File "/home/willy/anaconda3/envs/modulus/lib/python3.10/concurrent/futures/_base.py", line 319, in _result_or_cancel
    return fut.result(timeout)
  File "/home/willy/anaconda3/envs/modulus/lib/python3.10/concurrent/futures/_base.py", line 458, in result
    return self.__get_result()
  File "/home/willy/anaconda3/envs/modulus/lib/python3.10/concurrent/futures/_base.py", line 403, in __get_result
    raise self._exception
concurrent.futures.process.BrokenProcessPool: A process in the process pool was terminated abruptly while the future was running or pending.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/willy/modulus/modulus/examples/cfd/aero_graph_net/train.py", line 267, in <module>
    main()
  File "/home/willy/anaconda3/envs/modulus/lib/python3.10/site-packages/hydra/main.py", line 94, in decorated_main
    _run_hydra(
  File "/home/willy/anaconda3/envs/modulus/lib/python3.10/site-packages/hydra/_internal/utils.py", line 394, in _run_hydra
    _run_app(
  File "/home/willy/anaconda3/envs/modulus/lib/python3.10/site-packages/hydra/_internal/utils.py", line 457, in _run_app
    run_and_report(
  File "/home/willy/anaconda3/envs/modulus/lib/python3.10/site-packages/hydra/_internal/utils.py", line 223, in run_and_report
    raise ex
  File "/home/willy/anaconda3/envs/modulus/lib/python3.10/site-packages/hydra/_internal/utils.py", line 220, in run_and_report
    return func()
  File "/home/willy/anaconda3/envs/modulus/lib/python3.10/site-packages/hydra/_internal/utils.py", line 458, in <lambda>
    lambda: hydra.run(
  File "/home/willy/anaconda3/envs/modulus/lib/python3.10/site-packages/hydra/_internal/hydra.py", line 132, in run
    _ = ret.return_value
  File "/home/willy/anaconda3/envs/modulus/lib/python3.10/site-packages/hydra/core/utils.py", line 260, in return_value
    raise self._return_value
  File "/home/willy/anaconda3/envs/modulus/lib/python3.10/site-packages/hydra/core/utils.py", line 186, in run_job
    ret.return_value = task_function(task_cfg)
  File "/home/willy/modulus/modulus/examples/cfd/aero_graph_net/train.py", line 219, in main
    trainer = MGNTrainer(cfg)
  File "/home/willy/modulus/modulus/examples/cfd/aero_graph_net/train.py", line 54, in __init__
    self.dataset = instantiate(cfg.data.train)
  File "/home/willy/anaconda3/envs/modulus/lib/python3.10/site-packages/hydra/_internal/instantiate/_instantiate2.py", line 226, in instantiate
    return instantiate_node(
  File "/home/willy/anaconda3/envs/modulus/lib/python3.10/site-packages/hydra/_internal/instantiate/_instantiate2.py", line 347, in instantiate_node
    return _call_target(_target_, partial, args, kwargs, full_key)
  File "/home/willy/anaconda3/envs/modulus/lib/python3.10/site-packages/hydra/_internal/instantiate/_instantiate2.py", line 97, in _call_target
    raise InstantiationException(msg) from e
hydra.errors.InstantiationException: Error in call to target 'modulus.datapipes.gnn.ahmed_body_dataset.AhmedBodyDataset':
BrokenProcessPool('A process in the process pool was terminated abruptly while the future was running or pending.')
full_key: data.train

Environment details

Can you please double check that the path in data.data_dir=./data/ahmed_body is correct? Maybe try using absolute path just to check?

HYDRA_FULL_ERROR=1 python train.py +experiment=ahmed/mgn data.data_dir=/home/willy/modulus/modulus/examples/cfd/aero_graph_net/data/ahmed_body data.train.num_workers=1 data.val.num_workers=1 data.test.num_workers=1 data.train.num_samples=10 data.val.num_samples=5 data.test.num_samples=5
I changed my command as the above, and it passed the dataset loading problem.
But why when I try to change the num_samples higher than that, it returns the same error?

So anything greater than 10 in data.train.num_samples causes that error to appear?
From the error itself, it looks like something happens during dataset pre-loading in one of the graph loading processes.
Unfortunately, I could not reproduce the issue on my side.
You can try adding some simple prints to create_graph function to see if there is a particular file or place where the error occurs (and keep num_workers=1 to simplify the debugging).
Also, which environment does this issue happen in?


rolling out maps/tweets

Updating main script to avoid overwriting changes on
https://dev.azure.com/ceapex/Engineering/_workitems/edit/465558

Docs Build status updates of commit e56a81a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

FromYmlToTOC-INDEX.ps1
:white_check_mark:Succeeded

advocates/index.html.yml
:white_check_mark:Succeeded
View

advocates/map.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Change specification for namespace

Motivation
Basic namespace rule of XML is redundant for Grimoire.js. Each packages are basically managed by npm. (Even the package was not uploaded on npm, the package would be containing package.json if that was build with Node.js)
Therefore, each namespaces of grimoire plugins should be generated from package.json as the specification below.
Specification
Each components, nodes and converters should use the namespace determined by package.json.
In the package named grimoirejs-fundamental, each these contents use fundamental as namespace.
grimoirejs package (this package) will use grimoirejs as a namespace. (This is the only exception of the rule above)

If the plugin does not follow the naming rules, there is a problem that the namespace is not unique.

I suggest to namespaces to be UPPERCASE.
Because it is necessary to unify letters case lower or upper to prevent typing errors, but UPPERCASE letters are more looks like NAMESPACE than lowercase.

The namespace was decided to be lowercase so as to be the same as the package name.
By the way, NSIdentity is not currently used for attributes name.we need to fix this problem.
In order to comprehensively solve these problems with the specification change of the namespace, I propose the namespace specification as follows.

fqn for GomlNode,Component,Converter

[package name].[node name]
ex)  fundamental.goml

fqn for Attribute

[package name].[component name].[attribute]
ex)  fundamental.mesh.geometry

In order to adopt this form, we restrict only available letters to package,node and other names to lowercase letters , numbers and '-'.

This is another idea for namespace feature of Grimoire.
I want to have nesting of namespaces in Grimoire.js.
Motivation
Some shaders can have same name of variables when the material file use multiple techniques.
@Technique default{
   uniform float hello;
}
@Technique depth{
   uniform float hello;
}

Shader engineers need to consider what shader techniques can be used the other technqiue in render stage. So, I want to have nesting attribute namespace.
Suggestion
Assume the shader above was declared in grimoirejs-awesome-shader. Then hello attribute should have grimoirejs-awesome-shader. I would like to use namespace grimoirejs-awesome-shader.depth for second technique declared in the material file to register in attribute variable in Grimoire.js fundamental.

If attribute hello was specified by user without namespace notation, we will use grimoirejs-awesome-shader because it is defined in grimoirejs-awesome-shader. grimoirejs-fundamental` can decide namespace respectively.

But If attribute hello can have a namespace depth as namespace notation, we can use them for specifying depth technique.

If there was no depth attribute with grimoirejs-awesome-shader but there was depth attribute with grimoirejs-awesome-shader.depth, Grimoire will use grimoirejs-awesome-shader.depth for this case even if there was another hello attribute with grimoirejs-the-other-namespace namespace.

Generally, you do not need to limit the depth of namespace hierarchy.
When specifying an object, you can omit the left side of any dot with FQN.
In this case, ambiguity can be resolved according to the situation.

How to consider situation? I think these situations are the most important part of this specifications.


Update elastic-jobs-tsql-create-manage.md

Updated to make it explicit that max_parallelism applies only to elastic pools in a target group

Learn Build status updates of commit 17cac8f:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: GitBranchDeletedOrForcePushed]

Cannot sync git repo to specified commit because ref +refs/pull/8236/merge has been deleted or has been force pushed.
 If this is pull request, please ensure it is mergeable (no merge conflict) and open (not closed).

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Add project to "Awesome Companies Using Truffle" list

as seen here
Truffle is very open to a PR for this. Please reach out with any questions :)

https://github.com/trufflesuite/trufflesuite.github.io/pull/226

closing as that PR above is in review


Enable the interaction with the Field Operations on the Jira issue edit method

Codecov Report

Merging #17 (00dbdcb) into main (f185702) will decrease coverage by 0.24%.
The diff coverage is 76.19%.

@@            Coverage Diff             @@
##             main      #17      +/-   ##
==========================================
- Coverage   97.02%   96.77%   -0.25%
==========================================
  Files          70       70
  Lines        5470     5525      +55
==========================================
+ Hits         5307     5347      +40
- Misses         93      102       +9
- Partials       70       76       +6

Impacted Files
Coverage Δ

jira/issue.go
92.06% <76.19%> (-2.95%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f185702...00dbdcb. Read the comment docs.


Factor of 1.5 between errors from iPidControl::getErrors and actual errors

Hi,
I recorded the data from iPidControl::getErrors and then also data from iEncoders, then I computed the errors by qdes-iEncoders. I have realised that the errors from iPidControl::getErrors are of a factor of circa 1.5 smaller than the ones I computed. By dividing qdes-iEncoders by 1.5 they are basically the same as the ones from iPidControl::getErrors.
See plots below:
In blue errors from iPidControl::getErrors and in red qdes-iEncoders:

In blue errors from iPidControl::getErrors and in red (qdes-iEncoders)/1.5:

I thought that the errors from iPidControl::getErrors are the tracking errors, as this is also what he controlBoardDumper uses to return the position errors.
The questions are: am I doing something wrong? Or is this factor really there? And if yes, what is it and why?
Thanks!

Hi @hu-yue ,
on which joints did you get this data?

@traversaro these specific plots are for the left ankle roll, however I get the same also on left knee and right knee, I can also test other joints.

It seems to be true for all joints, however on the torso the tracking is quite bad, so I'm not sure about the outcome.

I tried to understand if this was due to the latest firmware and software update, since I had data recorded from before. I have to say that I couldn't actually understand it. The computed errors and the errors from iPidControl::getErrors were different, but by dividing the computed errors by 1.5 they did not match with iPidControl::getErrors.
In general, I'd like to go back to my initial questions:

Why are these errors different? Aren't they supposed to be the same or I'm not understanding what are the values from iPidControl::getErrors?

afaik, they should be identical on all joints of your robot. Suspected bug. @ale-git

@randaz81 @ale-git ok, I wait for further updates then
@KevinAStein FYI

Hi @hu-yue , which controlmode has been used for the test? In the plots, is the x axis the time in milliseconds? The errors are measured in degrees? Thanks.

@ale-git

the control mode is position direct
the x axis is the number of samples, but you can also say it's time in ms since I was sending commands with a thread rate of 10 ms
the errors are in degrees

Ok sorry the statement about the time is clearly wrong, total time is 6 sec, so the x axis is just number of samples

Hi @hu-yue , you should consider that there is a transmission delay Tt between your qdes at high level and the qdes_pid inside the pid controller, so qdes - iEncoders is in general different from iPidControl::getErrors = qdes_pid - iEncoders. If the delay between the qdes_pid reference and the joint position is affected by a Tc delay related to the pid time constant, then you have:
qdes = A * sin((2pi/6) * t)
qdes_pid = A * sin((2pi/6) * (t-Tt))
qenc = A * sin((2pi/6) * (t-Tt-Tc))
Thus
qdes - qenc  =(about) A * (2pi/6) * (Tt + Tc) * cos((2pi/6) * t)  (as shown by the plot)
qdes_pid - qenc =(about) A * (2pi/6) * Tc * cos((2*pi/6) * t)  (as shown by the plot)
and finally
(qdes - qenc) / (qdes_pid - qenc) = (Tt + Tc) / Tc
Given your software configuration, can the transmission delay explain the gain factor?

If the above hypothesis is correct, you should read a difference between qdes and iPidControl::getReference.

Hi @hu-yue @ale-git
The acquisitions seem to refer to a steady-state conditions where the error is quite low (~1-2 deg).
I would suggest to repeat the experiment logging all the involved quantities during a reasonable transition of qdes.
This should allow us to better test the hypothesis and appreciate possible latency among these variables.

Just an example:

@ale-git @pattacini thanks for the replies!
I run another experiment on the left knee joint performing a cos wave that moved the joint from 0 to -90 and back in 2 [sec]. I think the transmission delay can explain the difference between the two errors.
The data from iPidControl::getReferences seem to be delayed respect to qDes and then the encoders have a higher delay time.
Here are plots of the case I tested:
Reference trajectory, encoders and iPidControl::getReferences

Errors:

Then I suppose that the actual execution errors should be the ones returned by iPidControl::getErrors and one should not compute qDes - iEncoders, as this would increase the errors due to the delay factor?

Hi @hu-yue, yes, the error you should look at is returned by iPidControl::getErrors because it is synchronized to the encoder data. Using qDes - iEncoders introduces a gain factor due to the delay between the qDes and the low level joint position reference.
Cheers,
Alessandro

@ale-git ok perfect, thanks for all the explanations! Now things are clearer.

Thanks @ale-git for the great handling of this issue 👍
@hu-yue I'd just like to add a brief comment upon closure from a bit higher standpoint.
Taking qdes-enc as a measure of the error remains perfectly viable though, given that controllers can be easily designed to account for latency too, of course depending on the requirements the designer has in mind.

iPidControl::getErrors() has been just implemented in gazebo, see https://github.com/robotology/gazebo-yarp-plugins/issues/260


[docker] condition fails when using another registry than the DockerHub

Describe the bug
It seems that using another Docker registry than the defauklt dockerhub is always failing the condition of kind "docker"
To Reproduce
This snippet always fail:
title: "Bump jx-release-version version on shared library resources"
sources:
  lastVersion:
    kind: githubRelease
    name: Get the latest jx-release-version version
    spec:
      owner: "jenkins-x-plugins"
      repository: "jx-release-version"
      token: "{{ requiredEnv .github.token }}"
      username: "{{ .github.username }}"
      versionFilter:
        kind: semver
conditions:
  checkIfDockerImageIsPublished:
    name: "Check if the Docker Image is published"
    kind: dockerImage
    spec:
      hostname: 'ghcr.io'
      image: 'jenkins-x/jx-release-version'

Expected behavior
The condition should pass
Screenshots
N.A.
Version (please complete the following information):

OS: macOS
Version 0.14.0

Additional context
N.A.

Thanks for reporting this, ghcr should be working but it requires a token.
We are probably just missing the right error message

Good point, thanks (I did not read the documentation correctly).
Trying with the token is giving the following error though:
CONDITIONS:
===========

checkIfDockerImageIsPublished
-----------------------------
ERROR: illegal base64 data at input byte 3

✗ condition not met, skipping pipeline

I guess there is something in the code that does not support the GitHub token format 😅
      token: 'ghp_XXXXXXXXXX' # Input byte 3 is `_`...

No the github token alone used to be working at some point. The documentation on www.updatecli.io must  be updated.
The ghcr token format is now the same as the other registries. You can fetch it from your .docker/config.json
Or something like echo -n 0 "$GITHUB_ACTOR:$GITHUB_TOKEN" | base64
-> https://github.com/updatecli/updatecli/pull/246
I detected that issue with integration tests :trollface:

I can't make it work, could you help me?

My couple username + token works as expected. The command below works as expected (answers HTTP/200 with a temporary token, which mean this token is allowed for this image:

curl -u "$GITHUB_ACTOR:$GITHUB_TOKEN" https://ghcr.io/token\?scope\=repository:updatecli/updatecli:pull

The command echo -n 0 "$GITHUB_ACTOR:$GITHUB_TOKEN" is not valid: it adds a leading 0 and a space separator in the string:

$ echo -n 0 "$GITHUB_ACTOR:$GITHUB_TOKEN"
0 jenkins-infra-bot:ghp_XXXXX

Whatever encoded value I'm using (export UPDATECLI_GHCR_TOKEN="$(echo -n "$GITHUB_ACTOR:$GITHUB_TOKEN" | base64)" or export UPDATECLI_GHCR_TOKEN="$(echo -n 0 "$GITHUB_ACTOR:$GITHUB_TOKEN" | base64)"), updatecli always fails the condition with this message:

$ export UPDATECLI_GHCR_TOKEN="$(echo -n "$GITHUB_ACTOR:$GITHUB_TOKEN" | base64)"
$ updatecli diff <...>
# ...
CONDITIONS:
===========

checkIfDockerImageIsPublished
-----------------------------
ERROR: something went wrong while login to dockerhub

✗ condition not met, skipping pipeline

=============================

with manifest
# ...
conditions:
  checkIfDockerImageIsPublished:
    name: "Check if the Docker Image is published"
    kind: dockerImage
    spec:
      hostname: "ghcr.io"
      image: "updatecli/updatecli"
      token: '{{ requiredEnv "UPDATECLI_GHCR_TOKEN" }}'

Oh found a working case: the hostname is not needed at all (is it deprecated?). When removing it and setting the image field to the full image name, then it works \o/

ok, no need to encode the token:
conditions:
  checkIfDockerImageIsPublished:
    name: "Check if the Docker Image is published"
    kind: dockerImage
    spec:
      image: "ghcr.io/updatecli/updatecli"
      username: "{{ .github.username }}"
      password: "{{ requiredEnv .github.token }}"

seems to work as expected \o/

Closing in favor of https://github.com/updatecli/website/issues/167 (documentation update is required: there is no bug in updatecli)

Oh found a working case: the hostname is not needed at all (is it deprecated?). When removing it and setting the image field to the full image name, then it works \o/

Yes indeed it's deprecated.


how many data should i use to train this model？

Thanks for your job first, I want to know that how many data should i use to train in your repo. I want to use the cmu arctic dataset for training english tts, but there is about one hour for a speaker, can it work to train in you repo？Because i use the nvidia repo to train but the result is bad. Also, the result is very different for different batch size. I also use some of the libritts data to train on nvdia repo, about 3hour for 10 speaker, but the result is quiet bad too. Do you have some idea about how to train on small dataset ？

Multi-speaker is supported as well. For instance, you might collect 8 speakers and one hour for each corpus and record the directory in scripts/train_tacotron2.sh. Then the total amounts of data might help.

@begeekmyfriend Thanks for your reply, but one speaker in libritts just 10-20 min, if i  just use about 10 speaker of this, will it work?

I have no idea about your circumstances but it seems too little for everyone's corpus. You might try yourself but the evaluation can not be warranted.

Thankyou so much sir, for such an amazing work. @begeekmyfriend


crate2nix ignores crate-type

The Cargo.nix generated by crate2nix does not respect the Cargo.toml field specifying the crate build type. For example, if the Cargo.toml contains the following information:
[lib]
crate-type = ["rlib", "staticlib"]

There will be no difference in the Cargo.nix output that reflects our desire to build a statically linkable library. Furthermore, the rustc command executed by buildRustCrate will not include the desired flags --crate-type lib --crate-type staticlib.
The rust machinery in nixpkgs already supports this functionality. It just looks like crate2nix does not. I have identified what needs to be added to Cargo.nix in order to change this. A crate set just needs to have the attribute type which is a list containing one or more of the following strings:
bin  lib  rlib  dylib  cdylib  staticlib  proc-macro

If there is no crate-type in the Cargo.toml, then the type attribute of the crate object in Cargo.nix should not exist. I manually added this type attribute with the appropriate values, and my desired output was achieved.
I have no familiarity with how crate2nix works, so I do not think I will be able to make this feature addition. Hopefully this issue provides sufficient information to make this modification to crate2nix.

I was able to write a quick fix for this. Appreciate feedback:
https://github.com/kolloch/crate2nix/pull/32

I ran into this as well.
In case someone else needs a workaround for this issue: Simply add the types attribute to your crate overrides and it should work (tm).


Error with missing dependency while trying to run the extension in Keycloak 21.0.2

The extension is throwing this error -> Could not send webhook: java.lang.NoClassDefFoundError: com/google/gson/GsonBuilder. It was compiled with JDK 17. Have you seen that error before ?

Ok let me look at this

Ok, found it. You used the wrong probably. Try using the jar ending with -all.jar.


added method for logging plugin deprecation warnings

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests


ESP32 board request: KeeYees ESP32 Mini (Chip ESP-WROOM-32)

It would be nice if the following board could be added:

https://www.amazon.de/dp/B08TBPBJGV?psc=1&ref=ppx_yo2ov_dt_b_product_details

The board is already there, it's called : Wemos D1 Mini ESP32


Cleaned up React Context

Briefly describe the feature or bug that this PR addresses.
Cleaned up some of the unused variables in React Context. Data page state variables must be added when filters are added to that page.
Please link the Airtable ticket associated with this PR.
https://airtable.com/tbli2lWQHAqBa6ZcI/viw8Ro4zYPYcBGXRw/recjrEU9Ba07eYuEe?blocks=hide
If applicable, include screenshots of the feature/bugfix introduced by this PR (Please include both desktop and mobile if there is a significant UI change).
No UI changes, everything should work normally.
Describe the steps you took to test the feature/bugfix introduced by this PR.
Just tested around the website locally to see if any functionality was broken.
Does this PR depend on any recent backend work? If so, please include the PR number from the iit-backend repo and associated Airtable ticket link.
Nope.

Once Austins concern has been addressed it should be good to merge. Looks good!


How to resend Midjourney Bot issue messages?

If user makes mistake in request (for example wrong parameter "--v5" instead of "--v 5"), then server and subscription owner may see error message from Midjourney Bot, but user who made this request will not see it. Is there any way to set up forwarding of this error message to the user who made the request?

same issue，Is there a good solution for this mistake?
Thank you very much!

I meet the banned keyword, the error message is sent to the user, the bot can't catch it.


add support for JSON-LD in script tags

Make the html2md conversion symmetrical with the pipelines md2html by adding support for JSON-LD in script tags within head. Similar to how meta tags are currently handled, insert the value into the metadata table.

is this really a requirement? afaiu from @davidnuescheler , json lds tend to be large. and having a huge metadata-table is not ok.

we already support json-ld in the metadata table, it just doesn't work through script tags (but ends up there from the metadata table in pipeline conversion). This is just making the process symmetrical/roundtripable.
I agree on the size limits, but as @dylandepass said 2kb is too low, maybe 128kb? It's possible the content of the JSON-LD is enough to drive the initial render of some pages, with no other html.. I see a use in it being a higher limit
side note: whatever limit we decide on here should probably be applied to pipeline as well. Here's a page that got 250kb of json-ld from a regular gdoc: https://main--public-test--maxakuru.hlx.page/foo/1/2

whatever limit we decide on here should probably be applied to pipeline as well.

I'm not worried about the amount of JSON-LD in the header, but rather in the markdown. it fear that parsing a huge markdown is slow.

I added a 128kb limit for all metadata values, though I still think that limit would apply to pipeline as well (since it would need to parse markdown, too). Unless you're not concerned about that part since, in practice, it would more likely be BYOM clients to make extraordinarily large JSON-LD and less likely to occur in a word/google doc.
also just to elaborate on why this would be useful: we're working on a project that will use JSON-LD for commerce using BYOM overlays. Ideally the dev server could just use the same format (script tag) as we would see on the published doc. The current way of providing a meta table with json-ld then it being converted to a script tag on published docs is unexpected, imo. Open to other comments if you have any @tripodsan

though I still think that limit would apply to pipeline as well (since it would need to parse markdown, too).

not if the json-ld comes from the metadata.xlsx, not document metadata. which is probably the normal use-case

added a 128kb limit for all metadata values

that's good for now


Set up a "Hello world" project as one app with Webpack

Hello CR :hand:  In this PR i have managed to set up a hello world project as one app with webpack
Project requirements

Create a new Rails app called 'hello-rails-react'.

Use the command rails new -j webpack my_new_rails_app as described in the previous lesson's tutorial.

Verify that the jsbundling-rails gem is added to your Gemfile.

Initialize your project with Git.

Install needed node dependencies as described in the previous lesson's tutorial.

Create a babel.config.js in the root folder of your project as described in the previous lesson's tutorial.

Update webpack.config.js to include the babel loader as described in the previous lesson's tutorial.

Make sure that your project has a Postgres database set up.

Create a table for storing your messages and create 5 different greetings.

Create an API endpoint that selects a random greeting from your table (you will need a controller with an action and Rails route).

Create a static view that will be the root of your app.

Create the App component with react-router and render it in your static view.

Create the Greeting component that will display a greeting. Set it up as a route in your App component.

Create a store, an action, and a reducer that will connect to your API endpoint to get the random greeting.

Display the random greeting in your Greeting component.

Thank you @Ismailco @KDlamini @AnselemOdims  for reviewing my Project


Search; add # results to buttons

Who is this for?
New search
What is it doing for them?

Adds totalResults to query response so we can display it in the Search overview in the buttons linking to the specific sections
formatNumber has an extra option now to compact up the numbers if they are too long ({ notation: "compact" } is the option offered by Intl.NumberFormat(), so numbers from 4 digits will be compacted)
Applied the compact numbers to the concept buttons as well, but the complete number is still displayed in the tabs.

Part of #9236

Looks great!


[Bug] trace viewer opens in empty state while debugging

Bug detected in https://github.com/microsoft/playwright-vscode/pull/513#issuecomment-2274495198, but it also happens with public releases of playwright / playwright-vscode.
To reproduce:

initialize a playwright test project with npm init playwright@latest
in Testing, ensure Show trace viewer is selected
in Testing Explorer, expand and select a leaf test item, e.g. has title
click the Debug Test button

Eventually, it will open the trace viewer app showing Select test to see the trace.
This PR tries to fix it by ensuring that trace paths are only associated with corresponding test items when they are not running in debug.
Environment:
  System:
    OS: Windows 11 10.0.22631
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
    Memory: 11.99 GB / 31.74 GB
  Binaries:
    Node: 20.15.0 - ~\scoop\apps\nvm\current\nodejs\nodejs\node.EXE
    npm: 10.7.0 - ~\scoop\apps\nvm\current\nodejs\nodejs\npm.CMD
    pnpm: 8.15.4 - ~\AppData\Local\pnpm\pnpm.EXE
  IDEs:
    VSCode: 1.92.0 - C:\Users\rui.figueira\scoop\apps\vscode\current\bin\code.CMD
  npmPackages:
    @playwright/test: ^1.46.0 => 1.46.0

Playwright Test for VSCode: v1.1.7

I did not realize this was intended to land first.

I'll rebase it, no worries.

Rebased it again, and adapted it to new changes.
@pavelfeldman I noticed the embeddedTraceViewer setting is not materialized in the actual VS Code, and I found no path to enable it except in the mocked vscode.
I had to change the value directly in the code to be able to test it in VS Code. Is there any other way?


Installing react-navigation not enough if not using expo

The documentation suggests that you just need to install react-navigation, import it and you're ready to go. But this is only true if you're using expo!
If you're not using expo, and you're targeting ios, you also need to install react-native-gesture-handler and link all native dependencies with the commandreact-native link react-native-gesture-handler. If you're targeting Android even more steps are involved.
That's what I learned after finally hitting the reactnavigation website (https://reactnavigation.org/docs/en/getting-started.html). But before I spend a lot of time trying to understand this obscure error "null is not an object (evaluating RNGestureHandlerModuleState)" (image below).

Current version of Navigating Between Screens guide contains correct list of required packages and commands are divided for expo and react-native users.
If you still having problems with navigation packages using the latest guide please create the new issue.


feat: add query parameter validation

why
We should validate incomming requests before handling it. The validator will reject bad requests and protect our service.
what

This PR added request parameter validator for restful api.
SourceController was added as an example for request validator.
Also, some end-to-end test suit is added.

LGTM


Enable more coverage

sanitizer-coverage-level=4
Use 4 instead of 3 to enable the tracing of indirect calls.
This level is undocumented but it's the only way AFAIK to enable
this functionnality in rustc.
Here is the code describing the 4th level: link
Here we can see that this functionnality is used by libFuzzer: link
Here we can see that this functionnality is used by Honggfuzz: link
and enabled by default in their compiler wrapper: link
and recommended to use in their documentation: link
OSS-Fuzz enables it for Hongfuzz: link

sanitizer-coverage-prune-blocks=0
Disable pruning. Explanation here: link
OSS-Fuzz does it: link
Honggfuzz does it: link
In AFL, it seems that the flags was removed because it was
"redondant": link
I don't know if it's also redondant in our case, I haven't found any
evidence in LLVM source code and it's explicitly enabled in LibFuzzer
and Honggfuzz so I think it's better to enable it explicitly anyway.

sanitizer-coverage-trace-compares
It's enabled by default in libFuzzer (and therefore OSS-Fuzz): link
It's enabled by default in Honggfuzz: link , link

sanitizer-coverage-trace-divs and sanitizer-coverage-trace-geps
It's probably enabled by default in libFuzzer (and therefore OSS-Fuzz): link
It's implemented in libFuzzer: link

sanitizer-coverage-trace-pc-guard
I guess this one is already enabled by default but I thought it
was sensible to include it explicitly for completeness

The CI failed on OS X with a symbol error, which is the same error I was experiencing last time I tried to increase the coverage levels.

Oh.. I didn't see that, I only have a linux box.
I'll update my PR to only enable that on linux then.

@nagisa could you tell me which flags should be disabled on OS X?

I honestly have no idea, since I don’t use OS X either. You’ll have to figure out what flag(s) cause this by trial and error, waiting for CI results each time.

Ok, no problem, I'll do that :-)

Ok, so I tested all flags and only pc-guard is causing the build failure on OS X.
I've just removed all my test commits and added a new commit disabling only this flag on OS X.
Everything works well now on both platforms, OS X and Linux.

bors r+

@nagisa hum, it looks like bors isn't working...

bors r=nagisa


Add & use close channel method in the registry

Add all required code to automatically close channels when we're done sending
values in the mock_microgrid.
Required for the datasourcing actor benchmark.

Add private method to allow closing of channels
Update mock_microgrid to close channels when done sending.
Update datasourcing actor to close channels.

Please update release notes.

I updated the branch with the recent feedback but also removed the controversial commit regarding send() in the data sourcing actor and went back to counting the pending tasks before exiting method.
We can still update it later once we decided how exactly


Target unavailable false alarm

I have this script MWE similar in structure to that in #1213 . But instead of having a large global variable I load those variables separately in each nested workflow. It should be equivalent but I get weird errors like
INFO: Target unavailable: sos_step("a_normal")

The MWE is here:
target_mwe.tar.gz
to reproduce,
sos run test_load.sos

Okay, but there is still an exception going on, and the above example does not work. ... should I reopen the ticket?

What exception?
The exception is raised for sos_step missing because sos cannot parse
depends: [sos_step('%s_%s' % (n2a(x[1]).lower(), x[0])) for x in data_io['depends']]

before the step started, and has to create the dependency dynamically. Then the exception is created and workflow_executor runs the steps ...
I did not try to complete the workflow.

What exception?

The except is that INFO line complaining some target is not found.
What I meant by a "false" alarm is because the complained missing target is in the script. But from your explanation it seems SoS does not know it exists because it is parsed dynamically? It makes sense, because my previous version:
depends: [sos_step('%s_%s' % (n2a(x[1]).lower(), x[0])) for x in IO_DB['depends']]

where IO_DB is a parameter in global section, actually works. Is that expected?
So here I merely try to use local variable data_io to elimiate the use of global variables. Now with the current master if you try this workflow, it simply hangs. This is not a good behavior either.

The info line was a debug message that I have just removed. The sos_step target is unknown, so it was passed to the executor and the executor executes the requested step. This part works ok but I need to check the hang behavior.

because sos cannot parse ... before the step started,

If I explicitly use sos_step() it should be able to parse and create dependency beforehand? What if data_io is global variable? i‘m try to figure out the most efficient way to specify dependency -- by efficient I mean a method to make it easiest for SoS to create and execute the workflows.

SoS supports dynamic depends, which make the executor a lot more complex but we are almost there already so there is no reason to withdraw its support. I am trying to make sos_step static and see if the problem is caused by dynamic steps...

Another context switch bug...


Add JSDOC @module support for intellisense.

Search Terms
Intellisense jsdoc support for modules
Suggestion
When adding /** @module moduleName Module Description. */ to a module, then doing this:
import * as myName from "./moduleName";

I think it makes sense, when importing the whole namespace, to include the jsdoc @module comment.
I also think that when pressing Ctrl+Space for code completion on "./" (to get a list of modules) should also show the module documentation.
Use Cases
Better support for module documentation. I'm developing some module libraries and it would be great to give end users a good experience with better intellisense documentation.
Examples
aModule.ts
`/** @module aModule Does something awesome. */`

app.ts
import * as aModule from "./aModule";
// (moduleName should both have the doc details)
// ("./{*.*}" - all files in code completion should show the documentation as well)

Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

Also, quite annoyingly, the module doc comment is shown for the first member:

Playground link

I would like to give this thread a friendly bump to help determine the current status of support plans for this tag. Since we are currently working on stabilizing the experimental module loader API, this knowledge is relevant to the Node.js Modules Team (of which I am an observer) due to its potential as in-band solution for determining a module's format prior to its loading.
If I understand correctly, VS Code uses the TypeScript parser to parse its JavaScript implementation of JSDoc features. In the newest Insiders version of VS Code (possibly older versions as well), the @module JSDoc tag seems to be improperly implemented by the TypeScript parser.  This is evident by the incorrect syntax highlighting as can be seen in my screenshot below. Interestingly, the parser from the @typescript-eslint/parser  package properly detects this as the module type field and provides a warning.

Derived from the official JSDoc page:

@module [ [ { <type> } ] <specifier> ] ]

I believe the square brackets mean optional and the parser should not be using that for tokenization.
Relevant links:

JSDoc - @module
TypeScript ESLint Parser
DocumentJS - @module
LSST DM Developer Guide
TypeScript - Supported JSDoc
Node.js ECMAScript Modules

cc @weswigham @geoffreybooth

It would really great if we could enforce a type for a module. A module is similar to an Object and the ability to check to ensure a module exports the right types would be extremely useful. For example, given this types:
/**
 * @typedef NumberValueModule
 * @prop {number} value
 */

goodModule.js:
/** @module {NumberValueModule} piModule */
export const value = 3.14;

badModule.js:
/** @module {NumberValueModule} helloModule */
export const value = 'hello;
// ^ this should be reported as the wrong type

Is this possible at the moment with typings.d.ts somehow? I would love to start doing this even if it means not using JSDoc yet.

This would be very helpful for Node.js functional programmers. Modules should work just like classes, where intellisense  its type from the code. If you aren't using classes, you are doing double work to define the type in the code and then again in JSDoc. This a bad design. Its too easy for them to get out of sync. Please do for modules what was done for classes.

Please do for modules what was done for classes.

Would you be able to provide a code sample illustrating this? I feel like I'm the only person who uses this convention (even without any tooling benefits). It helps me to keep organized is all.

connect-stream.js
    /**
     * @param {import('stream').Readable} in
     * @param {import('stream').Writable} out
     */
    export async connectStream(in, out) {
      in.pipe(out)
    }

lidar-stream.js
    /**
     * @param {import('stream').Readable} lidar
     * @param {import('stream').Writable}   vision
     * @param {import('./connect-stream').connectStream} cb
     */
    async function detectFighting(lidar, vision, cb) {
      cb (
          lidar.getReadableStream('camera1'),
          vision.getWritableStream('fight')
       )
    }

The jsdoc of the 3rd param in lidar-stream.js is not supported. You can write @callback but, again, the point is to avoid having to do that and having to keep it in sync with the actual function.


requirements.txt file doesn't exist in drf_social directory

requirements.txt file doesn't exist in drf_social directory

Thanks, for the information I have added the file!


fix: decoupling triggers when an edit is made within e2e-test/

Issues:

Removing outdated reference to website/e2e-test/Dockerfile (since moved to ops/e2e-runner/)
Both e2e-runner-push-to-main and web-push-to-main (and thus the full web delivery) gets executed if an edit is made to website/e2e-test/
Fixes broken links describing e2e push to main and e2e nightly testing

Fixes:

Ensures that any edits to e2e-tests/ within website/ only executes e2e-runner-push-to-main
Links should reference correct Tf samples referencing e2e testing

thanks @grayside!


Related keyof T types are not assignable to each other

TypeScript Version:  3.4.2

Search Terms: Generics, keyof, strict function types
Code
interface Foo {
  [type: string]: any // tslint:disable-line no-any
}

type Bar<T, K extends keyof T> = (_: T[K]) => void

class Baz<T extends Foo, K extends keyof T = keyof T> {
  private list: { [key: string]: Bar<T, K>[] } = {}

  callMe<E extends K>(key: E, item: Bar<T, E>): void {
    // Workaround: Type 'E' cannot be used to index type '{ [key: string]: Bar<T, K>[]; }'
    const stringKey: string = key as string
    if (! (key in this.list)) {
      this.list[stringKey] = []
    }

    this.list[stringKey].push(item)
  }
}

Expected behavior: No type errors.
Actual behavior: An error on line 17:
Argument of type 'Bar<T, E>' is not assignable to parameter of type 'Bar<T, K>'.
  Type 'K' is not assignable to type 'E'.
    Type 'keyof T' is not assignable to type 'E'.
      Type 'string | number | symbol' is not assignable to type 'E'.
        Type 'string' is not assignable to type 'E'.

This same code worked fine on Typescript 3.3, but started emitting errors after upgrading to 3.4. The error only occurs when strict function types is enabled.
Playground Link: https://www.typescriptlang.org/play/index.html#src=interface Foo {
  [type%3A string]%3A any %2F%2F tslint%3Adisable-line no-any
}

type Bar<T%2C K extends keyof T> %3D (_%3A T[K]) %3D> void

class Baz<T extends Foo%2C K extends keyof T %3D keyof T> {
  private list%3A { [key%3A string]%3A Bar<T%2C K>[] } %3D {}

  callMe<E extends K>(key%3A E%2C item%3A Bar<T%2C E>)%3A void {
    %2F%2F Workaround%3A Type 'E' cannot be used to index type '{ [key%3A string]%3A Bar<T%2C K>[]%3B }'
    const stringKey%3A string %3D key as string
    if (! (key in this.list))%20%7B%0D%0A%20%20%20%20%20%20this.list%5BstringKey%5D%20%3D%20%5B%5D%0D%0A%20%20%20%20%7D%0D%0A%0D%0A%20%20%20%20this.list%5BstringKey%5D.push(item)%0D%0A%20%20%7D%0D%0A%7D%0D%0A
Related Issues:
#21756 seems similar, but not the same exactly.

I think the error is correct here, otherwise you can end up with unsoundness. E.g.
interface Foo {
  [type: string]: any // tslint:disable-line no-any
}

type Bar<T, K extends keyof T> = (_: T[K]) => void

class Baz<T extends Foo, K extends keyof T = keyof T> {
  private list: { [key: string]: Bar<T, K>[] } = {}

  callMe<E extends K>(key: E, item: Bar<T, E>): void {
    // Workaround: Type 'E' cannot be used to index type '{ [key: string]: Bar<T, K>[]; }'
    const stringKey: string = key as string
    if (! (key in this.list)) {
      this.list[stringKey] = []
    }

    this.list[stringKey].push(item)
  }

  applyMe(key: string) {
    return this.list[key][0];
  }

}

declare const baz: Baz<{ x: number; y: string; z: boolean }, "y" | "z">
baz.callMe("y", (x: string) => undefined);
baz.applyMe("y")(true); // the function was set as something that only accepted strings!

The issue appears to be that you're assigning a Bar<T, E> to a Bar<T, K> when E is related to K, however both those types are used as keys, which are related contravariantly. That is, for Bar<T, E> to be related to Bar<T, K>, is should be that K is related to E.


DockerRegistry name is converted to astericks

Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name: docker
Environment

Server - Azure Pipelines
Agent - Hosted

Issue Description
Whenever I submit my pipeline, my private docker registry is being converted into "***" and breaking my builds.
Task logs
Script contents:
docker tag moll.dev:47 "blahblahblah.azurecr.io/moll.dev/pipeline"
========================== Starting Command Output ===========================
[command]/bin/bash --noprofile --norc /home/vsts/work/_temp/fdb979e8-fc5f-4662-95e9-c0e6ff239597.sh
##[section]Finishing: Tag Image

A random string works fine. Whenever I use the string "molldevhub" it gets converted to stars. This should not be happening.
docker tag moll.dev:47 "***"
========================== Starting Command Output ===========================
[command]/bin/bash --noprofile --norc /home/vsts/work/_temp/c4b711c8-3396-46f8-a167-c68c6f392f6c.sh

Any ideas?

The *** which you're seeing in the logs is just our masking logic of your sensitive information in logs.
Is molldevhub declared as a secret anywhere? Or is molldevhub.azurecr.io your loginServer in the docker registry endpoint you're using?
How is it breaking your builds btw? What's the error that you're seeing?

@QuantumFractal The redaction is most likely not causing any issue. Could you provide the debug logs? This would help us understand your problem better.
@kevinhillinger This is not a newly introduced feature, it has been in the system for a long time. Also, it redacts only the secrets from your logs. I'm not sure if you can opt-out of the redaction.

Closing this issue; feel free to re-open it if you're still facing an issue.
But, it's definitely not failing because of the redaction in the logs.


readme has rgb_a when it should probably be rgb_r

Typically the "A" value when talking about rgba is the Alpha channel for transparency.  I believe these should all say rbg_r, meaning the red channel

@dpalay Great catch, gonna fix this.


fix(#362): Improving documentation for returning customers

Add new section specifically helping with install
Focused on simplicity
Attempting to maintain the conversation style of the README in general

My formatter has had a fun time formatting the Readme too on save (Prettier). Let me know if you want this reducing :)


don't jump while chatting

This issue is a duplicate of #31, which has been resolved by #35. Regardless, thank you for reporting!


FastAPI pagination with resource coming from RESTful APIs

I'm trying to implement an endpoint in my fastAPI application where I 'm trying to gather some resources (job items) from various RESTful resources and after normalisation return them to the caller.
Problem is that pagination doesn't seem to work as I expected as requesting the 2nd page of my results makes all subsequent RESTful APIs to get called again, hence the response time takes just as much the first page required.
My idea was that, per documentation, the pagination adds all results in memory so that next page call the data are already available. Am I missing something here?
@router.get("/job_search",
            response_model=Page[Job],
            summary="Get jobs from various sites based on keyword", tags=["Job search"])
@has_permissions(Permissions.PUBLIC_PERMISSION_LEVEL)
def search_jobs(keyword: str = Query(), user: User = Depends(user_db_crud.get_current_user)):
    """
    Returns jobs found in various sites based on keyword.
    """
    try:
        jobs = search_jobs(preprocess_string(keyword))
        return paginate(jobs)
    except Exception as e:
        raise HTTPException(
            status_code=500, detail=f"An unexpected error occurred. Report this message to support: {e}")

@timing_decorator
def search_jobs:
    url = "some url here"
    response = requests.get(url)
    .
    .
    process here
    .
    .
    return jobs

INFO:     Started server process [19894]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://<IP_ADDRESS>:9999 (Press CTRL+C to quit)
Function search_jobs took 48.73508310317993 seconds to run.
INFO:     <IP_ADDRESS>:55747 - "GET /v1/job_search?keyword=%CE%BF%CE%B4%CE%B7%CE%B3%CE%BF%CF%82&page=1&size=100 HTTP/1.1" 200 OK
Function search_jobs took 52.42994689941406 seconds to run.
INFO:     <IP_ADDRESS>:55752 - "GET /v1/job_search?keyword=%CE%BF%CE%B4%CE%B7%CE%B3%CE%BF%CF%82&page=2&size=100 HTTP/1.1" 200 OK

Misread the documentation I guess, thanks @uriyyo !

Great, then I am closing this issue


typo: progressIndicatorAligment -> progressIndicatorAlignment

progressIndicatorAligment should be changed to progressIndicatorAlignment
(typo occurrences)
Recommend deprecating the property in favor of the correctly spelled one to avoid breaking changes.
It can be annoying at times, but I'd recommend a spell checker like (this one)[https://marketplace.visualstudio.com/items?itemName=streetsidesoftware.code-spell-checker].

thank you @uPaymeiFixit if you have time, can you fix it and create a pr.

fixed on 1.0.4 thanks


inside a reducer function, it is called parameters

a reducer is a function. Inside a function, the passed in values are not arguments. They are parameters.
We call a function by optionally supplying arguments, but once inside of a function, they are called parameters.
Or
never mutate the arguments passed in.

name: "\U0001F4DD Documentation Fix"
about: Fixing a problem in an existing docs page
Checklist

[ ] Is there an existing issue for this PR?

link issue here

[ ] Have the files been linted and formatted?

What docs page needs to be fixed?

Section:
Page:

What is the problem?
What changes does this PR make to fix the problem?

A reducer is just a function. A function in JavaScript has arguments. This is correct as-is.


function cannot define in jupyter notebook

Hello,
I'm very new about matlab.
In matlab, To execute a user-defined function, I heard that the user must define function in script file or function *.m file.
Even if imatlab is not support magic %% , some guideline suggest to define function in jupyter.
https://am111.readthedocs.io/en/latest/jmatlab_use.html#Standard-functions
In my trial, I must make new notebook on python kernel,  write func.m file with %%file magic and call the function from new notebook on matlab kernel.
In the matlab notebook,  %%file was not working because imatlab does not support the magics system.
Could you give a tip instead of my way?
Thanks
ps. I used ubuntu18, anaconda3, python 3.6, matlab 2018a. And I also test the same with python 3.5 .

The documentation you link is for https://github.com/Calysto/matlab_kernel/, which is a different kernel from this one.
imatlab does not support magics.


Update config for runsetting

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 46.52%. Comparing base (20afa9d) to head (9e879ff).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #13      +/-   ##
==========================================
+ Coverage   45.47%   46.52%   +1.05%
==========================================
  Files          93       93
  Lines        1713     1713
  Branches      467      467
==========================================
+ Hits          779      797      +18
+ Misses        916      913       -3
+ Partials       18        3      -15

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Was there ever another word list?

So I made a brain/paper wallet in 2018/2019 and wrote down the 24 words; actually 25, but one might be a password/marker. I don't remember the tool I used back then, neither did I write it down.
Anyway, I'm currently researching how to get to a functioning wallet. Of course I started with this converter. Very quickly I start sweating when it starts telling me some of the words are not in the word list.
I'll present a few of the offending ones so that people have something to work with:

dullness
against
ruined
ounce
madness
rising

Searching online, I find all of them in the Monero project, but it was definitely a BTC tool.
So, given the time frame and some words, can anybody point me in the right direction? I'm fairly certain is was not some random thing I ran back then, but something well-known, like www.bitaddress.org.

Electrum had its own wordlist. But ounce is not on it.


Fix import issue and renaming issue

Fixing some build issues

thanks, had these changes locally but not pushed them :)


[cluster-test] Add help info to grab log once node connection is broken

Add some information print for user, how to grab log if node connection is lost
Motivation
(Write your motivation for proposed changes here.)
Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan
./scripts/cti --pr 5937 --run bench
Pod Spec : /var/folders/qd/tg50mr0d7k75qvztr_8yk2km0000gn/T/tmp.iSxgLQgn
Using cluster : ct-2
If connection aborts, use "kubectl logs ${WORKSPACE}" to fetch logs

Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/libra/website, and link to your PR here.)

/land

@snakech :exclamation: This PR is still missing approvals, unable to queue for landing


Fixed extraargs being ignored

I noticed debugger_args option was ignored while attaching to remote gdbserver. This PR should fix this issue.

related to #206, superseded by #316
@mariotaku it would be nice if you could review that


feat(groups): support groups migration

Support groups migration in the same style of roles.
Fix #11

@daniel-frak I've another feature to implement:
We're multi-tenant here, and it's possible to one email/username exist in multiple tenants hence we need user's realm id to search for realm + username.
I've implemented locally (passing realm id as query param), should I open a new PR or can I commit in this one?
Thanks

I think it will be better to do as a separate PR.
Could you also describe the problem the PR will solve in more detail (in the new PR or an issue)? I must admit I only vaguely understand it at the moment, as the plugin is per-realm (AFAIK).
I'll take a look at the code in this PR later today and hopefully merge it then :)

LGTM, thanks for the contribution!


Deleted GCSTs appearing in download files

Some GCSTs can be found in various places in the Catalog that do not correspond to any publicly available study.
[1] GCST90102290-GCST90102430. These are visible in the unpublished ancestry download*, and the unpublished sumstats table in the UI, with NA in the author and title. Looks to me (based on date and traits)   like these are from the Lotta submission, the one where Annalisa changed the study tags and accidentally created new GCSTs. https://app.zenhub.com/workspaces/gwas-59df823c4a6feb3786810391/issues/ebispot/goci/714
[2] GCST90092507- GCST90092517. These are visible in the unpublished studies download*, and the unpublished sumstats table in the UI, with NA in the sample details. These are from a submission (61d7068b06ff200001948d1d) where the author had submitted every chromosome in a separate file and was asked to resubmit fewer files, we reopened the submission and deleted the old studies. (Note for future - in this scenario it would be better to ask the submitter to create a fresh submission).
These should be fully deleted from the DB so they are not visible to users.
*downloaded 7/6/2022

@ljwh2 the Unpublished studies have been deleted from Curation DB , will reflect in Catalog after DR


Image Stitching

Image Stitching
This be able to stitch two images together, creating a panorama of stitched images.
Sometimes , we click more than image if the object is close and large and then desire it to be in one frame.
Fixes #956
Replace 965 with the issue number which is fixed in this PR
Have you read the Contributing Guidelines on Pull Requests?

[x] Yes
[ ] No

Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My documentation follows Template for README.md
[x] My changes generate no new warnings

@ayush-raj8 please make a separate branch and then make a PR. It causes a lot of issues.

@kaustubhgupta Do I need to create a separate branch before making PR for this?

@ayush-raj8 yes, not only for this PR but all the PRs you make


"Bad Gateway" error on hairy query

This query fails:
{
  bills(first: 1, jurisdiction: "New Hampshire", session: "2018") {
    edges {
      cursor
      node {
        id
        identifier
        title
        classification
        updatedAt
        votes {
          edges {
            node {
              id
              updatedAt
              extras
              identifier
              motionText
              motionClassification
              startDate
              endDate
              result
              organization {
                id
                classification
              }
              billAction {
                description
                date
                order
                extras
              }
            }
          }
        }
        actions {
          date
          description
          classification
          order
          extras
          relatedEntities {
            name
            entityType
            organization {
              id
            }
            person {
              id
            }
          }
        }
        documents {
          date
          note
          links {
            url
          }
        }
        versions {
          date
          note
          links {
            url
          }
        }
        sources {
          url
          note
        }
      }
    }
  }
}

Removing either the sources at the end, or the billAction on the VoteEventNode makes it succeed, leading me to think that some limit somewhere is being exceeded.

interesting, this might be the server intercepting the request or response due to length, I haven't been able to reproduce it locally just yet

I'm surprised it isn't solid reproducible.  It's not the response size; if I remove billAction it works, but the bill I get back has no votes, and is quite small.
I don't know nginx at all well, but I've gotten the sense in the past that there's some way in which it (or the proxied server) can be misconfigured such that some error responses from proxied servers are converted into 502's.  This could be superstition, though!
But if it's true, consider 500 errors as a possibility, for which there could be myriad internal reasons.
If you haven't already, to try to provoke it I'd suggest trying adding more "joins" to the query, for example, roll calls.

It could be the response URL size; the entire query gets encoded into it, e.g. http://alpha.openstates.org/graphql?operationName=null&query={
  bills(first%3A 1%2C jurisdiction%3A "New Hampshire"%2C session%3A "2018") {
    edges {
      cursor
      node {
        id
        identifier
        title
        classification
        updatedAt
        votes {
          edges {
            node {
              id
              updatedAt
              extras
              identifier
              motionText
              motionClassification
              startDate
              endDate
              result
              organization {
                id
                classification
              }
            }
          }
        }
        actions {
          date
          description
          classification
          order
          extras
          relatedEntities {
            name
            entityType
            organization {
              id
            }
            person {
              id
            }
          }
        }
        documents {
          date
          note
          links {
            url
          }
        }
        versions {
          date
          note
          links {
            url
          }
        }
        sources {
          url
          note
        }
      }
    }
  }
}

yep, uwsgi was swallowing the URL, I've doubled the buffer size (requests bigger than that should probably use the post body)

I'm using graphiql, which does use the post body to send the request.  But it also sends the entire url-encoded query in a Referer header, which then gets used as the URL of the response.
I googled around a bit to see if there's some way to tell graphiql not to do that, but found nothing, not even an open issue.  Similar report: https://github.com/graphql/graphiql/issues/159
I figure this is good to close; I just wanted to fill you in, in case it comes back.


chore(ownership) after-install now handles file / directory ownership

do not merge until after 2.2.0

fixed the syntax errors
not sure why the swarm tests are failing
but taking a quick look at the tests, we have some hardcoded versions:

https://github.com/Kong/docker-kong/blob/chore/directory-ownership/tests/01-image.test.sh#L33
https://github.com/Kong/docker-kong/blob/chore/directory-ownership/tests/01-image.test.sh#L113

this file for example is not defaulting KONG_USER to kong https://raw.githubusercontent.com/Kong/docker-kong/1.5.0/swarm/docker-compose.yml
🤔
but this one is: https://raw.githubusercontent.com/Kong/docker-kong/2.2.0/compose/docker-compose.yml
need to investigate

@hutchic

@gszr

@hutchic @gszr please review it again
docker still needs the chown -R kong:0 /usr/local/kong and chown kong:0 /usr/local/bin/kong so we can run Kong as the overridden 1001 user (openshift)
https://github.com/Kong/docker-kong/pull/423/commits/99cba2fee6151dd40c7670055170cf9b9fbc5b2d

the one hardcoded version fix is up for PR https://github.com/Kong/docker-kong/pull/420

@hutchic ok, but I think this is ready to be merged.. will fix/avoid the docker library complains and concerns about our current Dockerfile: https://github.com/docker-library/official-images/pull/8972


feat: add sc_admin to default.meta

Idea from: https://github.com/splunk/splunk-add-on-for-mysql/pull/327

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

v5.11.0
GitHub release

Your semantic-release bot :package::rocket:


Specific Playlist throws JSON error

One of my playlists throws the following error when I try to open it:
Failed to read JSON: invalid type: null, expected a string at line 23 column 19
The playlist is this one: https://open.spotify.com/playlist/35RLOEH1zKsTllJFwL9wvW
This seems like a similar issue as #112
Thanks for taking a look!

Should be fixed in bbca2bc (master), can you please confirm? Local tracks are skipped completely and playlist URL pasting should be fixed as well.

Yes that fixes this error for me. Thanks for the fix.


[QUESTION] Strange noise pattern appears on RGB camera

Describe the bug
When acquiring images with OAK-D Lite a strange noise pattern appears on RGB images.
Left and right cameras are 480p, RGB image camera is 12mp with a preview size of 3840x2160. I'm using depthai <IP_ADDRESS>.
Expected behavior
I don't expect that kind of noise, it seems like an artifact of some kind of post-processing.
Screenshots
Here I show a couple of examples.
Example 1 (a table)
Left image:

Right image:

RGB image:

Crops of the RGB image:

Example 2 (a white sheet on a table)
Left image:

Right image:

RGB image:

Crop of the RGB image:

Example 3 (objects on a table)
Left image:

Right image:

RGB image:

Crop of the RGB image:

Thank you for the answer, is there a way to obtain the raw RGB images from the camera?

I tried the proposed settings and it seems to work.  Thank you.


Add callouts about using light colors ideally on a dark background

would be even better to show those buttons on a dark background, but i assume that'd require a lot more logic behind the scenes (to only show the outline buttons that are contrasty enough against white on a white background, and the others on a dark background)

With #30044 merged a few days ago, it might be quite trivial to handle  backgrounds (but would require to use some kind of containers to apply backgrounds). However the callout *si a good idea :)

Just realised we should probably do the same for https://v5.getbootstrap.com/docs/5.0/helpers/colored-links/ ... i'll add another commit here

Would be very nice to add a background element around them if needed based on the contrast colors. A callout like this feels unnecessary IMO, but I'm down for whatever.

let's do callout just now, and then somebody cleverer than me can work out how to do a conditional bit of light vs dark background

@patrickhlauke this needs a manual backport, can you do it please and ping me?

@XhmikosR done - https://github.com/twbs/bootstrap/pull/32054