feat(datastore-filters): add filters for DataStore _deleted property

Description of changes
Added _deleted field to the generated ModelXXXFilterInput so people can query the API without the deleted items, for example.
CDK / CloudFormation Parameters Changed
None.
Issue #, if available
Implemented #78.
I noticed that people are actively asking in the thread to implement the feature, but wasn't sure why it hasn't been implemented yet.
If there's a special reason or an intentional decision not to implement it (or not do it that way), please let me know.
Description of how you validated changes

Created an example Todo model that has the list/sync query, pushed it and made sure the filter applies in the AppSync console
Created the Todo model without sync or list, but connected it to another model (ListOfTodos) with an @hasMany directive. Pushed and made sure the query for Todos through ListOfTodos has this field and that it's working.

Checklist

[X] PR description included
[X] yarn test passes

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@phani-srikar @iartemiev
Thank you guys!

I added it to the tests :)

I see the value in adding the _deleted field to the list query filter input specifically. What are the use cases that justify adding _version and _lastChangedAt as well?

Giving it a second thought, I think you're right. I narrowed it down to only have the _deleted field as a possible filter.

I think that if we make this change, it should only apply to the list query filter input, not the sync query, as DataStore relies on these internal fields and filtering on them can lead to unexpected behavior when using DataStore specifically.

That might be correct. However, the problem with it is that Sync, List and Get queries, all use the same ModelXXXFilterInput object.
Making a new separation to declare a new filter object, and testing it well, might be unworthy and significantly larger than the scope that this PR aims to address.
If that's OK with you, my opinion is that this scope should stay narrow. Let me know if you strongly disagree...
Please feel free to review this once again 😄

@MorCohenAres thank you for making the requested changes.
On the last point - I agree that creating a new filter input object will result in a bigger code change, but I think it's worth it in this case, because it will serve as a guardrail to prevent unintended API use. It's never valid to filter on _deleted when using DataStore, so we don't want to implicitly encourage that by exposing that field in the filter input for sync queries.
Please let us know if you need assistance from the team with this change. We'd be happy to build on top of your PR if that's the case.

@iartemiev Thank you for your comment!
I have made the necessary changes and created a new ModelSyncXXXFilterInput type.
Actually it really wasn’t that hard, because of the already-existing separation between Query and Subscription which we can take influence from.
Also the code in those areas is nice and clean, very comfortable to work with :)
So I updated the tests as well, and you're welcome to review it again.
NOTE:
I'm using the new ModelSyncXXXFilterInput only at the sync query level.
In nested fields inside the sync query it's still uses the regular ModelXXXFilterInput. This is because the main list of items that is returned from the sync query is the part that requires you not to filter by _deleted so you can align your local database with the deleted items. Nested lists of items are not used for this purpose (If you want to sync the nested type you should use the corresponding sync query), so they should use the regular filter.
Please let me know what you think!

@dpilch @phani-srikar Fixed yarn.lock. Thanks!

Thank you for your approvals. Would love to contribute more in the future! ☺

Thank you for your approvals.
Would love to contribute more in the future! ☺

Running e2e tests on this. Follow link if you've access

Running e2e tests on this. Follow link if you've access

I see that it failed bcause of renaming the sync filter input. I have now fixed it.
BUT I'm now realizing that THIS IS A BREAKING change for client Amplify SDKs.
For example here We'll need to change this manually-generated filter name to support!
Same Here (JS) and Here (Android), and also make sure it works in Flutter.
This should be taken into consideration when people upgrade their CLI with these changes. How should we tackle this?

@MorCohenAres - you're right, I didn't account for that with the approach I suggested. With that being said, let's revert back to what you had before: a single Input type with _deleted added. That way the change will be non-breaking across the platforms . Apologies for the back and forth.

Will adding the filter _deleted = 0 by default to the Get and List (when DS enabled) DDB query filter expression address the usecase?

@MorCohenAres - we discussed this amongst the team and would like to go with the original approach you had - single Input object that's shared across the 3 Query fields. Thanks!

(It's me, Mor. I just abandoned the old account)
@iartemiev OK thank you guys. I have now updated everything according to your latest decision.
Let's try e2e again to see if that works? 😄

Follow this link for latest e2e.

The schema-predictions test failure is a known issue which will be fixed when we re-run the pipeline against latest CLI version.

The schema-predictions test failure is a known issue which will be fixed when we re-run the pipeline against latest CLI version.

Then is it ready to be merged? Are we holding it till the CLI updates in the pipeline?

Thanks for the contribution @MorFix. We will keep you updated once this change makes it to Amplify CLI release.

@MorCohenAres Thank you for your contribution! I would like to follow up with you on this. can you please connect with me on Twitter or LinkedIn


Shading language (and. OptiX interaction suggestion)

Hello. I suggest to add OptiX support in FireRays. For use in any GPU: from Nvidia to AMD.
Also, have you shader language?
For example: intersection or shading language for rays (like OpenRL)?

Hi @acterhd,
OptiX has proprietary license, so I am not sure we are allowed to. Anyway FireRays is supposed to work on Nvidia OpenCL (of course not as fast as on AMD), if it does not please file an issue here.

As for shading language: The language is OpenCL C currently, all the shaders for the sample rendrer are written in OpenCL C. However it is not comparable to OpenRL since you can't trace a ray from during shader execution, this is very inefficient on modern GPUs. Our shading approach is closer to Open Shading Language(OSL) where we describe surface appearance  and renderer evaluates it in the way it wants.


bar element type doesn't show properly when axis value is a date

When using a bar element type in conjunction with the primary axis as dates, the bars get huge with no relevance to the graph.
See reproduction
As line:

As bar (with primary axis value as date):

As bar (with primary axis value as string):

Same problem here, did you find a solution ?

👀

it was huge mistake for us to use this dead charts kit


chore: fix eslint error

Before submitting a pull request, please make sure the following is done...

[x] Ensure the pull request title and commit message follow the Commit Specific in English.
[x] Fork the repo and create your branch from main.
[ ] If you've added code that should be tested, add tests!
[ ] If you've changed APIs, update the documentation.
[x] Ensure the test suite passes (npm test).
[x] Make sure your code lints (npm run lint) - we've done our best to make sure these rules match our internal linting guidelines.

Please do not delete the above content

What have you changed?
修改eslint 报错

Codecov Report

Merging #6 (b660c38) into main (f45a4ce) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #6   +/-   ##
=======================================
  Coverage   75.00%   75.00%
=======================================
  Files           1        1
  Lines          16       16
  Branches        4        4
=======================================
  Hits           12       12
  Misses          4        4

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 f45a4ce...b660c38. Read the comment docs.


Script for packaging this app for the Nextcloud hub store

https://docs.nextcloud.com/server/latest/developer_manual/app_publishing_maintenance/code_signing.html#how-to-get-your-app-signed

Closing this as the steps have been documented in the "" section of the README.md and should be part of the automation in #64.


test: scenarios-feature_branch_happy_path (2024-02-26 22:47:41.343017+00:00)

automatic test cleanup


Fix for description case sensitivity

@humboldtux, Thanks for the advice earlier.
This fixes an issue where description may not be displayed, due to a case sensitivity bug. Using 'with' fixes this. The fix also makes the param none sensitive to capitalisation in the config file.

Thanks


remove explicit window.debug export

Exporting to the "outer" scope of the module is more the responsibility
of the module loader (i.e. browserify, webpack, etc.) and thus this
is not necessary. make test-browser still passes after this patch.

Coverage remained the same at 63.462% when pulling 8b18daee705145b6f1cc6912514af717f9ce5d39 on remove/explicit-attach-to-window into 9a18d66282caa2e237d270a0f2cd150362cbf636 on master.


Recommend adding the cocoa troubleshooting issues to documentation

Hi there, I would recommend adding the sed -I “TBB” line for troubleshooting in the dead me as I spent hours figuring out how to make this work on my own  before I found it in your closed issues. I have a feeling this is a common problem with Catalina. Otherwise it works perfectly thank you! Added revision for your review to pull request
Secondly, I am unsure after reading the respondus site, for the physical lockdown browser application, does it record or screen grab our screen and can it see the Helium app open when that is sent to the server?
Thanks

Hi.
Thanks for the PR!
I haven't used this in quite some time, but I doubt teachers/respondus are willing to spend hours sifting though images/videos. Would be like trying to find the needle in the haystack 😊
Back to the TBB thing; I don't think it's required, as it runs fine for me on Catalina without it. I think the easiest fix would just be to remove TBB from the requirements.


Bluetooth: Peripheral: Bond issue when using secure connection

Describe the bug
When using peripheral_sc_only sample on nrf52832_mdk, the first connection from Android nRF Connect application work, but the second always fails.
To Reproduce
Steps to reproduce the behavior:

Build and flash peripheral_sc_only sample on nrf52832_mdk
Connect with nRF Connect application
Retrieve all characteristics using Read characteristics button
Disconnect
Reconnect to the device
Try to retrieve all characteristics again
See error

Expected behavior
Re connection should work and allow to retrieve device characteristics.
Impact
This really affect the secure BLE connection UX. the feature can still be used, but bonding information must be manually deleted before each re-connection.
Logs and console output
Device logs:
*** Booting Zephyr OS build zephyr-v2.6.0  ***
[00:00:00.398,193] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.398,193] <inf> bt_hci_core: HW Variant: nRF52x (0x0002)
[00:00:00.398,223] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 2.6 Build 0
[00:00:00.398,864] <inf> bt_hci_core: Identity: F2:06:B2:D5:EB:EE (random)
[00:00:00.398,864] <inf> bt_hci_core: HCI: version 5.2 (0x0b) revision 0x0000, manufacturer 0x05f1
[00:00:00.398,864] <inf> bt_hci_core: LMP: version 5.2 (0x0b) subver 0xffff
Bluetooth initialized
Advertising successfully started
Connected 6C:16:3C:EF:27:FC (random)
Passkey for 6C:16:3C:EF:27:FC (random): 560967
Security changed: 6C:16:3C:EF:27:FC (random) level 4
Identity resolved 6C:16:3C:EF:27:FC (random) -> 5C:51:81:E8:2B:DC (public)
Pairing Complete
Disconnected from 5C:51:81:E8:2B:DC (public) (reason 0x13)
Connected 5C:51:81:E8:2B:DC (public)
Security failed: 5C:51:81:E8:2B:DC (public) level 1 err 8
Pairing Failed (8). Disconnecting.
Disconnected from 5C:51:81:E8:2B:DC (public) (reason 0x3d)

nRF Connect logs:
nRF Connect, 2021-06-28
SC only peripheral (F2:06:B2:D5:EB:EE)
D 17:03:42.003 gatt.close()
D 17:03:42.006 wait(200)
V 17:03:42.208 Connecting to F2:06:B2:D5:EB:EE...
D 17:03:42.209 gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE)
D 17:03:42.539 [Broadcast] Action received: android.bluetooth.device.action.BOND_STATE_CHANGED, bond state changed to: BOND_BONDING (11)
D 17:03:42.557 [Callback] Connection state changed with status: 0 and new state: CONNECTED (2)
I 17:03:42.558 Connected to F2:06:B2:D5:EB:EE
D 17:03:42.623 [Broadcast] Action received: android.bluetooth.device.action.ACL_CONNECTED
D 17:03:42.623 [Broadcast] Action received: android.bluetooth.device.action.PAIRING_REQUEST, pairing variant: PAIRING_VARIANT_CONSENT (3)
D 17:03:50.881 [Broadcast] Action received: android.bluetooth.device.action.PAIRING_REQUEST, pairing variant: PAIRING_VARIANT_PIN (0)
D 17:04:04.644 [Broadcast] Action received: android.bluetooth.device.action.BOND_STATE_CHANGED, bond state changed to: BOND_BONDED (12)
I 17:04:04.644 Device bonded
D 17:04:04.702 wait(1600ms)
V 17:04:06.304 Discovering services...
D 17:04:06.304 gatt.discoverServices()
D 17:04:06.323 [Callback] Services discovered with status: 0
I 17:04:06.323 Services discovered
V 17:04:06.353 Generic Attribute (0x1801)
- Service Changed [I] (0x2A05)
   Client Characteristic Configuration (0x2902)
- Client Supported Features [R W] (0x2B29)
- Database Hash [R] (0x2B2A)
Generic Access (0x1800)
- Device Name [R] (0x2A00)
- Appearance [R] (0x2A01)
- Peripheral Preferred Connection Parameters [R] (0x2A04)
D 17:04:06.354 gatt.setCharacteristicNotification(00002a05-0000-1000-8000-00805f9b34fb, true)
V 17:04:11.614 Reading all characteristics...
V 17:04:11.614 Reading characteristic 00002b29-0000-1000-8000-00805f9b34fb
D 17:04:11.614 gatt.readCharacteristic(00002b29-0000-1000-8000-00805f9b34fb)
I 17:04:11.697 Read Response received from 00002b29-0000-1000-8000-00805f9b34fb, value: (0x) 00
A 17:04:11.697 "No features" received
V 17:04:11.713 Reading characteristic 00002b2a-0000-1000-8000-00805f9b34fb
D 17:04:11.713 gatt.readCharacteristic(00002b2a-0000-1000-8000-00805f9b34fb)
I 17:04:11.773 Read Response received from 00002b2a-0000-1000-8000-00805f9b34fb, value: (0x) FB-77-E2-2D-82-8A-4B-4D-45-C6-C0-32-1E-CF-57-AF
A 17:04:11.773 "(0x) FB-77-E2-2D-82-8A-4B-4D-45-C6-C0-32-1E-CF-57-AF" received
V 17:04:11.787 Reading characteristic 00002a00-0000-1000-8000-00805f9b34fb
D 17:04:11.787 gatt.readCharacteristic(00002a00-0000-1000-8000-00805f9b34fb)
I 17:04:11.887 Read Response received from 00002a00-0000-1000-8000-00805f9b34fb, value: (0x) 53-43-20-6F-6E-6C-79-20-70-65-72-69-70-68-65-72-61-6C, "SC only peripheral"
A 17:04:11.887 "SC only peripheral" received
V 17:04:11.905 Reading characteristic 00002a01-0000-1000-8000-00805f9b34fb
D 17:04:11.905 gatt.readCharacteristic(00002a01-0000-1000-8000-00805f9b34fb)
I 17:04:11.959 Read Response received from 00002a01-0000-1000-8000-00805f9b34fb, value: (0x) 00-00
A 17:04:11.959 "[0] Unknown" received
V 17:04:11.971 Reading characteristic 00002a04-0000-1000-8000-00805f9b34fb
D 17:04:11.971 gatt.readCharacteristic(00002a04-0000-1000-8000-00805f9b34fb)
I 17:04:12.040 Read Response received from 00002a04-0000-1000-8000-00805f9b34fb, value: (0x) 18-00-28-00-00-00-2A-00
A 17:04:12.040 "Connection Interval: 30.00ms - 50.00ms,
Slave Latency: 0,
Supervision Timeout Multiplier: 42" received
V 17:04:12.060 5 characteristics read
V 17:04:15.906 Disconnecting...
D 17:04:15.906 gatt.disconnect()
D 17:04:15.964 [Callback] Connection state changed with status: 0 and new state: DISCONNECTED (0)
I 17:04:15.964 Disconnected
D 17:04:16.964 [Broadcast] Action received: android.bluetooth.device.action.ACL_DISCONNECTED
D 17:04:26.273 gatt.close()
D 17:04:26.276 wait(200)
V 17:04:26.478 Connecting to F2:06:B2:D5:EB:EE...
D 17:04:26.478 gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE)
D 17:04:26.842 [Broadcast] Action received: android.bluetooth.device.action.ACL_CONNECTED
D 17:04:26.905 [Callback] Connection state changed with status: 0 and new state: CONNECTED (2)
I 17:04:26.905 Connected to F2:06:B2:D5:EB:EE
D 17:04:26.932 wait(1600ms)
V 17:04:28.534 Discovering services...
D 17:04:28.534 gatt.discoverServices()
D 17:04:28.566 [Callback] Services discovered with status: 0
I 17:04:28.566 Services discovered
V 17:04:28.590 Generic Attribute (0x1801)
- Service Changed [I] (0x2A05)
   Client Characteristic Configuration (0x2902)
- Client Supported Features [R W] (0x2B29)
- Database Hash [R] (0x2B2A)
Generic Access (0x1800)
- Device Name [R] (0x2A00)
- Appearance [R] (0x2A01)
- Peripheral Preferred Connection Parameters [R] (0x2A04)
D 17:04:28.590 gatt.setCharacteristicNotification(00002a05-0000-1000-8000-00805f9b34fb, true)
V 17:04:36.008 Reading all characteristics...
V 17:04:36.008 Reading characteristic 00002b29-0000-1000-8000-00805f9b34fb
D 17:04:36.008 gatt.readCharacteristic(00002b29-0000-1000-8000-00805f9b34fb)
D 17:04:56.841 [Broadcast] Action received: android.bluetooth.device.action.BOND_STATE_CHANGED, bond state changed to: BOND_NONE (10)
I 17:04:56.841 Bond information deleted
V 17:04:56.891 Reading characteristic 00002b2a-0000-1000-8000-00805f9b34fb
D 17:04:56.891 gatt.readCharacteristic(00002b2a-0000-1000-8000-00805f9b34fb)
E 17:04:56.891 Exception occurred (Reading characteristic failed)
V 17:04:56.892 Reading characteristic 00002a00-0000-1000-8000-00805f9b34fb
D 17:04:56.892 gatt.readCharacteristic(00002a00-0000-1000-8000-00805f9b34fb)
E 17:04:56.892 Exception occurred (Reading characteristic failed)
V 17:04:56.892 Reading characteristic 00002a01-0000-1000-8000-00805f9b34fb
D 17:04:56.892 gatt.readCharacteristic(00002a01-0000-1000-8000-00805f9b34fb)
E 17:04:56.892 Exception occurred (Reading characteristic failed)
V 17:04:56.892 Reading characteristic 00002a04-0000-1000-8000-00805f9b34fb
D 17:04:56.892 gatt.readCharacteristic(00002a04-0000-1000-8000-00805f9b34fb)
E 17:04:56.892 Exception occurred (Reading characteristic failed)
V 17:04:56.892 5 characteristics read
E 17:04:58.955 Error 133 (0x85): GATT ERROR
D 17:04:58.956 [Callback] Connection state changed with status: 8 and new state: DISCONNECTED (0)
E 17:04:58.956 Error 8 (0x8): GATT CONN TIMEOUT
I 17:04:58.956 Disconnected
D 17:04:59.016 [Broadcast] Action received: android.bluetooth.device.action.ACL_DISCONNECTED

Environment (please complete the following information):

Zephyr v2.6.0 (also reproduced on v2.4.0 and v2.5.0)
nRF Connect version 4.23.3
Android version 7.1.2

I've also try to disable bonding by setting CONFIG_BT_BONDABLE=n but this doesn't change anything.

Hi @joerchan
Were you able to have a first look at this issue?
Does it fells like a mis-usage from my side, maybe a badly configured Kconfig ? Or do you think that's a real bug in Zephyr implementation ?
Thanks for your help.

@XavierChapron, @joerchan is currently on holiday. We will update as soon as he's back.

@XavierChapron The disconnect reason is MIC failure, which means that the two devices are not using the same LTK. Can you please check with another phone (or peer). It could be a problem with your phone.
Also try to go through you existing bonds in the android bluetooth settings and delete possible old bonds for the device.

@XavierChapron The disconnect reason is MIC failure, which means that the two devices are not using the same LTK. Can you please check with another phone (or peer). It could be a problem with your phone.
Also try to go through you existing bonds in the android bluetooth settings and delete possible old bonds for the device.

@joerchan Thanks for your answer.
I've already tested with one other peer (a tablet which I currently don't have access at the moment) and to delete all existing bonds, however this doesn't change anything.
Is there anything else I can test to help understand my issue?

@XavierChapron Ok, I've tried to follow your steps to reproduce it but I've not seen the same thing you are seeing.
*** Booting Zephyr OS build zephyr-v2.6.0  ***
Bluetooth initialized
Advertising successfully started
[00:00:00.367,156] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.367,156] <inf> bt_hci_core: HW Variant: nRF52x (0x0002)
[00:00:00.367,187] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 2.6 Build 0
[00:00:00.367,858] <inf> bt_hci_core: Identity: E2:94:C2:37:BF:F3 (random)
[00:00:00.367,858] <inf> bt_hci_core: HCI: version 5.2 (0x0b) revision 0x0000, manufacturer 0x05f1
[00:00:00.367,889] <inf> bt_hci_core: LMP: version 5.2 (0x0b) subver 0xffff
Connected 5D:26:A8:94:94:E5 (random)
Passkey for 5D:26:A8:94:94:E5 (random): 104033
Security changed: 5D:26:A8:94:94:E5 (random) level 4
Identity resolved 5D:26:A8:94:94:E5 (random) -> 00:BE:3B:48:F8:72 (public)
Pairing Complete
Disconnected from 00:BE:3B:48:F8:72 (public) (reason 0x13)
Connected 00:BE:3B:48:F8:72 (public)
Security changed: 00:BE:3B:48:F8:72 (public) level 4
Disconnected from 00:BE:3B:48:F8:72 (public) (reason 0x08

We have seen issues with peripheral sending security requests to android. Can you tell me if you get the same issue by delaying the call to bt_conn_set_security in main.c. Use k_delayed_work_submit and something like 10 seconds.
Also remove the call to bt_conn_set_security from bt_gatt_connected in gatt.c
I can't see where it goes wrong from the logs, can you please enable CONFIG_BT_DEBUG_SMP=y and see if there for some strange reason ends up with different. Maybe also add logging of the LTK used in le_ltk_reply in hci_core.c.
If you have a spare nrf devkit could you set up the nRF Sniffer for Bluetooth LE and get a capture of the traffic.
In order to decrypt the traffic when encrypted we need to use the debug keys so enable CONFIG_BT_USE_DEBUG_KEYS=y and CONFIG_BT_STORE_DEBUG_KEYS=y, this could potentially alter the behavior of the android device but worth a try.
I used the nrf52840dk_nrf52840 board, you are saying nrf52832_mdk, which is not any board I'm familiar with. Is this something you have added locally?

@joerchan Thanks for your help.

I used the nrf52840dk_nrf52840 board, you are saying nrf52832_mdk, which is not any board I'm familiar with. Is this something you have added locally?
It's a simple nrf52832 dev-kit : https://github.com/zephyrproject-rtos/zephyr/blob/main/boards/arm/nrf52832_mdk/doc/index.rst

I made new tests with the same board and the same phone but using as you recommend a little delay between connection and the call to bt_conn_set_security() using a delayed k_work..
With a delay of 3 seconds it seem to work as expected:
*** Booting Zephyr OS build zephyr-v2.6.0-1-gf7448aeb66b7  ***
[00:00:00.542,083] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.542,083] <inf> bt_hci_core: HW Variant: nRF52x (0x0002)
[00:00:00.542,114] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 2.6 Build 0
[00:00:00.542,755] <inf> bt_hci_core: Identity: F2:06:B2:D5:EB:EE (random)
[00:00:00.542,755] <inf> bt_hci_core: HCI: version 5.2 (0x0b) revision 0x0000, manufacturer 0x05f1
[00:00:00.542,755] <inf> bt_hci_core: LMP: version 5.2 (0x0b) subver 0xffff
[00:00:00.542,785] <inf> main: Bluetooth initialized
[00:00:00.543,243] <inf> main: Advertising successfully started
[00:00:13.106,597] <inf> main: Connected 4C:73:60:06:8B:30 (random)
[00:00:16.106,628] <inf> main: delayed work executed
[00:00:18.066,162] <inf> main: Passkey for 4C:73:60:06:8B:30 (random): 784951
[00:00:29.930,938] <inf> main: Security changed: 4C:73:60:06:8B:30 (random) level 4
[00:00:29.983,612] <inf> main: Identity resolved 4C:73:60:06:8B:30 (random) -> 5C:51:81:E8:2B:DC (public)
[00:00:29.983,917] <inf> main: Pairing Complete
[00:00:58.324,829] <inf> main: Disconnected from 5C:51:81:E8:2B:DC (public) (reason 0x13)
[00:01:06.312,805] <inf> main: Connected 5C:51:81:E8:2B:DC (public)
[00:01:06.665,130] <inf> main: Security changed: 5C:51:81:E8:2B:DC (public) level 4
[00:01:09.312,866] <inf> main: delayed work executed
[00:01:36.370,178] <inf> main: Disconnected from 5C:51:81:E8:2B:DC (public) (reason 0x13)
[00:01:44.576,202] <inf> main: Connected 5C:51:81:E8:2B:DC (public)
[00:01:44.965,423] <inf> main: Security changed: 5C:51:81:E8:2B:DC (public) level 4
[00:01:47.576,232] <inf> main: delayed work executed
[00:02:10.358,154] <inf> main: Disconnected from 5C:51:81:E8:2B:DC (public) (reason 0x13)

Note that the first time, the delayed work triggers a security level change, the other time, the stack handles it itself with a little delay of ~500ms and the k_work probably do nothing.
This seems like a solution for me.
However I've no idea if this solution is hacky or just the expected implementation?
I also wonder what are the implication in regard to security?
Does that means that there is a small moment after connection where characteristics can be read without knowing the device pin?
Let me know if y should run the additional tests with CONFIG_BT_DEBUG_SMP or something else.

This seems like a solution for me.
However I've no idea if this solution is hacky or just the expected implementation?

So this is about who initiates the security, and it appears that the phones expect it to be them. The apple developer guide states this:
"The accessory should not request pairing until an ATT request is rejected using the Insufficient
Authentication error code. See the Bluetooth 4.0 specification, Volume 3, Part F, Section 4 for details"
So what you have run into is a known issue  where android phones when receiving a security request ends up deleting the Bond.

I also wonder what are the implication in regard to security?
Does that means that there is a small moment after connection where characteristics can be read without knowing the device pin?

No, anything requiring security will not be accessible until the security requirement has been met.
But you have to state the security requirement for each characteristic individually.
The peripheral_sc_only sample does not add any characteristics with security requirement, have a look at the peripheral sample instead for some examples of this.

This is not an issue with zephyr, but with the android Bluetooth LE stack not handling security requests.
Workaround for the application is:

Set CONFIG_BT_GATT_AUTO_SEC_REQ=n.
Delay or don't initiate security request (calling bt_conn_set_security in the peripheral role).

@joerchan Thank to your help I was able to make it work as expected!

Long shot here, I think I encountered same issue. CONFIG_BT_GATT_AUTO_SEC_REQ=n doesn't seems to work. Even though i set it. It says in the build that it isn't set. Removing bt_conn_set_security doesn't seems to work either. Because then it won't ask for a bond/pair.  And putting the delay doesn't do anything

@Pmr-precure By not set do you mean that it is marked as CONFIG_BT_GATT_AUT_SEC_REQ is not set, because that is the same as being =n.
This issue is a long time since I dealt with, I don't remember all the details here.
If you have an issue I suggest you either go to the discord channel to discuss your problem there, or open a new github issue and describe your problem there.

@Pmr-precure and @joerchan Hello,
That was a long time ago, and I don't have access to this code anymore, but as I remember it, the fix on my side was:

use a delayed kwork to call bt_conn_set_security() so that it is called in another thread (mainly it needs to be done after the return of connected callback)

@Pmr-precure and @joerchan Hello, That was a long time ago, and I don't have access to this code anymore, but as I remember it, the fix on my side was:

use a delayed kwork to call bt_conn_set_security() so that it is called in another thread (mainly it needs to be done after the return of connected callback)

Thanks for even responding!  I knew it was a long shot! I havnt really been able to make a k_work_delayed_submit implementation correct.


Meta: Use correct certificate path when invoking WPT

We now ensure that the directory for the currently selected build preset is used as the base certificate path.
I've also included a change to ensure that log files are written to the correct place when an absolute path is given, previously the path was always appended to the current directory.
NOTE: The -P option can't be used with realpath since the option isn't available on MacOS.

@tcl3 The second commit actually fails if the log file doesn't already exist:
» ./Meta/WPT.sh run --log-mach results.log /webdriver/tests/classic/set_window_rect/set.py
realpath: results.log: No such file or directory

Oops :sweat_smile: , this should be fixed by #2031.


Update default gateway version to 3.1

What does this Pr do ?
Udpate default gateway version to 3.1.0

Need to change appVersion in chart.yaml too

Forgot it. Thanks :bow:


How to define the size of a Lity window

How can I define (before opening a Lity window) its size and z-index of the resulting Lightbox.
Can it be global or set for each different call?
Thanks!
Current code:
            var lightbox = lity('/mydomain_dir/code.php');                     // Bind as an event handler             $(document).on('click', '[data-lightbox]', lity);

You could use a customer handler (see #71 for an example) or bind to lity:open and add your custom logic.

Would be nice if Lity would get options which support height and width.

Feel free to open a PR for this feature. Closing for now.


Support parsing half-open ranges in patterns.

Fixes #117

Looks good to me but hmm, any idea why libsyntax uses two different enums for Expr ranges vs Pat ranges?
pub enum ExprKind {
    /* ... */

    /// A range (`1..2`, `1..`, `..2`, `1...2`, `1...`, `...2`)
    Range(Option<P<Expr>>, Option<P<Expr>>, RangeLimits),
}

/// Limit types of a range (inclusive or exclusive)
pub enum RangeLimits {
    /// Inclusive at the beginning, exclusive at the end
    HalfOpen,
    /// Inclusive at the beginning and end
    Closed,
}

pub enum PatKind {
    /* ... */

    /// A range pattern, e.g. `1...2` or `1..2`
    Range(P<Expr>, P<Expr>, RangeEnd),
}

pub enum RangeEnd {
    Included,
    Excluded,
}

Nothing that's obvious from the commit message or PR discussion. @oli-obk ?

I think the answer is rather obvious: I didn't know about RangeLimits... XD


BEP for audio/video capture of behaving subjects

I would like to create a BEP to store the audio and/or video recordings of behaving subjects.
While this would obviously be problematic for sharing human data, it would be useful to internal human data and for internal and shared data of non-human subjects.
Following the structure of the Task Events we will define types of files that can be placed in various data_type directories.
sub-<label>/[ses-<label>]
    <data_type>/
        <matches>_behcapture.mp3|.wav|.mp4|.mkv|.avi
        <matches>_behcapture.json

This schema will follow the standard principles of BIDS, listed here for clarity:

If no relevant <data_type> exists, use beh/.
Video or audio files that are continuous recordings split into files will use the _split- entity.
Video or audio files that are recorded simultaneously but from different angles or at different locations would use the _recording- entity to differentiate. We will need to modify the definition of this term to generalize it a bit to accommodate this usage. This entity would also be used to differentiate if a video and audio were recorded simultaneously but from different devices. Not that simply using the file extension to differentiate would not work because it would not be clear which file the .json maps to.
The start time of each audio or video recording should be noted in the scans.tsv file.

The JSON would define "streams" which would define each stream in the file.
The *_beh.json would looks like this:
{
  "device": "Field Recorder X200",
  "streams": [
    {
      "type": "audio",
      "sampling_rate": 44100.0,
      "description": "High-quality stereo audio stream."
    },
    {
      "type": "video",
      "sampling_rate": 30.0,
      "description": "Standard 1080p video stream."
    }
  ]
}

To be specific, it would follow this JSON Schema structure:
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "device": {
      "type": "string"
    },
    "streams": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "type": {
            "type": "string",
            "enum": ["audio", "video"]
          },
          "sampling_rate": {
            "type": "number",
            "format": "float"
          },
          "description": {
            "type": "string"
          }
        },
        "required": ["type", "sampling_rate"],
        "additionalProperties": false
      }
    }
  },
  "required": ["device", "streams"],
  "additionalProperties": false
}

This BEP would be specifically for audio and/or video, and would not include related data like eye tracking, point tracking, pose estimation, or behavioral segmentation. All of these would be considered derived and are reserved for another BEP.

cc @yarikoptic who is providing guidance on this concept.

An alternative idea is to name the files "_video.mp4|avi|mkv|..." and "_audio.mp3|wav|...". The advantage of this is it may be more clear what these files are. The disadvantages are that this does not make it clear that it's a recording of the subject as opposed to a stimulus, and that it's not clear what you should do if you have an audio/video recording.

Another alternative idea is to have the files called "_beh.mp3|.wav|.mp4|.mkv|.avi|...", though this conflicts with the current beh modality.

see https://github.com/bids-standard/bids-specification/pull/750 for a PR that talks about supporting videos in BIDS (but for storing of stimuli)

This BEP would be specifically for audio and/or video, and would not include related data like eye tracking, point tracking, pose estimation, or behavioral segmentation. All of these would be considered derived and are reserved for another BEP.

Some of this may already be covered by the BIDS support for motion data and look at the the eyetracking BEP (PR and HTML)

tagging @gdevenyi who I think mentioned wanting to work on something like this last time I saw him.

The ideas for allowing annotations of movies and audios as expressed in issue #153 could be expanded to allow annotation of participant video/audio but in the imaging directories themselves with appropriate file structure to distinguish.
@neuromechanist @Remi-Gau @yarikoptic @adelavega @dungscout96 @dorahermes @arnodelorme
.

Wouldn't those annotations of videos using HED when experimenters "code" their video be more appropriate as a derivative though.

Not necessarily.... in one group I worked with on experiments on stuttering -- the speech pathologist's annotations were definitely considered part of the original data. Most markers that you see in typical event files didn't come from the imaging equipment but are extracted from the control software or external devices. The eye trackers have algorithms to mark saccades and blinks and these are written as original data.
In my mind, if the annotations pertain to data that has been "calculated" from the original experimental data it should go into the derivatives folder.  Annotations pertaining to data acquired during the experiment itself should probably go in the main folder.

We have potential animal applications in both domains:

Video with annotation timestreams coming from automated touchscreen-based animal behaviour  systems.
Videos of animals in classic "open field test" and similar setups where poostprocessing analysis collects a variety of annotations of the video determined by behaviour.

also I guess a:
3. Manual human annotation of videos of animals in naturalistic environments, like maternal care events

Would non-contiguous recordings (using the same setup) end up in the same or distinct files?
As an example, there could be cases where video recording has been stopped while taking care of a crying baby and resumed later on. Should BIDS try to enforce anything here, or leave it to end users (and data providers)?
What about other types of "time-series" data? Not sure about MEG, for EEG I know the EDF+ format allows discontinuous recordings:

EDF+ allows storage of several NON-CONTIGUOUS recordings into one file. This is the only incompatibility with EDF. All other features are EDF compatible. In fact, old EDF viewers still work and display EDF+ recordings as if they were continuous. Therefore, we recommend EDF+ files of EEG or PSG studies to be continuous if there are no good reasons for the opposite.

@DimitriPapadopoulos I believe this would be different runs. You would specify the start time of each run in the scans file

I think there might be multiple scenarios (entities) how it could be handled:

runs - if e.g. this corresponds also to separate runs of neural data if any acquired along, so primarily as "this is how we intended this all to be".
But I wonder if we should look into adopting/extending (currently they are too narrowly focused) any of other entities meaning of which relate somehow to have "pieces of" (using term which is not yet an entity):  split, part, chunk.

We have potential animal applications in both domains

From the annotation perspective in #153, an annot- entity enables multiple annotations per _media file. It might be useful here as well.

But I wonder if we should look into adopting/extending (currently they are too narrowly focused) any of the other entities meaning of which relate somehow to have "pieces of" (using term which is not yet an entity): split, part, chunk.

Any of them seems great, I currently suggested part- as an entity to use. But I can see any of the three work.

Video or audio files recorded simultaneously but from different angles or at different locations would use the _recording- entity to differentiate.

This is similar to having a stimulus with multiple tracks (left or right video streams, multiple audio channels, or separate video and audio), but they are not recording- per se. So, we might be able to look for a common entity that covers both potentially. We have two suggestions in #153 for now, (1) stream- and (2) track-. Would be happy to have any additional suggestions.

Also, as @bendichter mentioned, this proposal will very soon find its audience in human neuroscience, especially with DeepLabCut adding subject masking capabilities and newer modalities such as LiDAR and wifi motion capture comes into play.
It might be useful to have Motion-BIDS maintainers' (@sjeung and @JuliusWelzel) opinions as well.

How do we feel about this naming convention?
sub-<label>/[ses-<label>]
    <data_type>/
        <matches>_behcapture.mp3|.wav|.mp4|.mkv|.avi
        <matches>_behcapture.json

I'm not 100% on it myself but I can't think of anything better. Other options:

"_video.mp4|avi|mkv|..." and "_audio.mp3|wav|...".
"_behvideo.mp4|avi|mkv|..." and "_behaudio.mp3|wav|...".
"_behmedia.mp4|avi|mkv|mp3|wav|..."

Is there any precedence from other standards we could use here?

Is there any precedence from other standards we could use here?

Technically mkv is container format, it could have different kinds of video/audio streams.
Should we specify non-patent-encumbered video compression formats?

@bendichter would be good to have your input on the proposed entities.
A specific point of discussion is how open the description of the proposed -annot entity would be: for stimuli only or also for other types of annotations as discussed above?

@dorahermes I like the idea of a general text annotations file that annotates a media file, and I think that could certainly be relevant downstream of these behavioral capture files.
I think the needs of stimuli storage and behavioral capture storage are different. With stimuli, you often have a single file that you play many times across different subjects, sessions, and trials, so it makes sense to have a root folder for these where they can be referenced repeatedly. For behavioral captures, every capture is unique, so it would make more sense to store these alongside other types of recordings. So I like what is going on with stimuli, but I don't want that that to engulf these ideas about how to represent behavioral capture.
I also am trying to keep this to an MVP, so I'd like to push off discussion of annotations, though I will say I think the general approach you link to will probably work for behcapture as well with minimal adjustments.

Should we specify non-patent-encumbered video compression formats?

The most likely culprit here would be H264, which is used in mpeg files, however it seems that would be a non-issue since this would be covered under the "Free Internet Broadcasting" consideration (source)

"_behvideo.mp4|avi|mkv|..." and "_behaudio.mp3|wav|...".

FWIW, I also think that we should have "audio", "video" in suffix (ref elsewhere) but do not think we should want to collapse an "intent" (beh) into it, moreover since we do have datatype beh and even modality so in principle could be depicted as _mod-beh but AFAIK so far we never did such way to associate (e.g. for _events.tsv).

I think there is a good amount of overlap (datatypes, extensions) with "stimuli" BEP044. @bendichter when you get a chance, have a look at that BEP google doc.


Go to definition goes to lib.es6.d.ts definition instead of local class

From https://github.com/Microsoft/vscode/issues/17083
TypeScript Version:  2.1.4
Code
class History {
    foo() {
        new History()
    }
}

Trigger go to definition on History in new History()
Expected behavior:
TypeScript server returns definition result for the History class defined in this file
Actual behavior:
Returns definition for History from lib.es6.d.ts instead.

This is a duplicate identifier error; there's no "local" class per se and it's just arbitrary which we go to. If this is in a module (add a top-level export / import statement), the go-to-def goes to the right place.

Yes, if this is in a TypeScript file then we see that error message. If the class is in a JavaScript file, I believe this is valid code and we do not generate any errors or warnings.

not sure there is much we can do here. we should consider showing this error in a .js (as part of https://github.com/Microsoft/TypeScript/issues/6802) file to make it clear that you are overriding a known global declaration.


Allow to control field type

Problem
I opened this issue recently: https://github.com/prisma/prisma/issues/5399 A workaround had been found in this particular case, but I encounter the same issue again.
I have a JSON field and I would like to assign a specific type I would have defined.

How much would your use case overlap with #3219?

It is exactly this use case but more general!

Closing this then, see you over at #3219


Invalid syntax

Hey, great script thanks. Was working few weeks ago, but when im trying it now (1.3.2 version due to no "launcher") I get this error:
File "C:\Users\XXX\Downloads\lol-bot-1.3.2\lol-bot-1.3.2\scripts\client.py", line 74
match self.get_phase():
^
SyntaxError: invalid syntax
Im very new to python. Can you please help me out abit?

You probably need to update ur python to a version later than 3.10


MAINT: Fix version

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Closes #19

Very nice, thanks @larsoner


RFP - OrientDB

Hi,
I did not see any existing RFP for OrientDB so I opened one.
I have an open source project that uses OrientDB. As OSS projects needs contributors, I think installation must be as easy as it can be for people to focus on their ideas.
All other software components of the project are already installable with chocolatey, so it would be great to be able to install the whole requirements within a chocolatey script.
Best regards

@gilwi Can you post a link to the project and the download?

Sure!
Project : https://github.com/iorga-group/debattons
OrientDB Download Page : https://orientdb.com/download-2/
Thank you for answering so fast !

Package pushed for review: https://chocolatey.org/packages/orientdb

This package is published!


Error: GET http://localhost:4200/styles.css

The last step in the Routing Tutorial is to apply a global style to the application. After following the instructions for doing so, I get an error in the browser: GET http://localhost:4200/styles.css. The app is being served using the CLI command: ng serve (if that makes any difference). The styles.css file is located at the default location where the CLI created it. Why can't the browser find the file?
index.html
<head>
  <meta charset="utf-8">
  <title>AngularTourOfHeroes</title>
  <base href="/">
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <link rel="icon" type="image/x-icon" href="favicon.ico">
  <link rel="stylesheet" href="styles.css">
</head>

src directory (filtered for relevance)
.
├── app
│   ├── app-routing.module.ts
│   ├── app.component.css
│   ├── app.component.ts
│   ├── app.module.ts
│   ├── dashboard.component.css
│   ├── dashboard.component.html
│   ├── dashboard.component.ts
│   ├── hero-detail.component.css
│   ├── hero-detail.component.html
│   ├── hero-detail.component.ts
│   ├── hero.service.ts
│   ├── hero.ts
│   ├── heroes.component.css
│   ├── heroes.component.html
│   ├── heroes.component.ts
│   └── in-memory-data.service.ts
├── assets
├── favicon.ico
├── index.html
├── main.ts
└── styles.css

same issu

Hi, ok, I had the same problem and the tutorial is wrong in one place. With the latest version of the angular cli, you no longer have to include the <link rel="stylesheet"...> in the index.html file. The cli will inject the contents automatically. So remove that line from the index.html and all should work. The files that get injected are specified in the .angular-cli.json file, and this works because the styles.css is already preconfigured there for you-
ref - https://github.com/angular/angular-cli/wiki/stories-global-styles

closing since this was rewritten with the CLI

@chriszrc lol

#122
#125

Okay Recently I fetched this problem I have very simple solution for solve this Issue , follow these steps:
go to these directories  src-> app-> index.html open the index.html and find
<base href="your app name "> change this to <base href="/">

Hey , I have once query here. If we use # in place of "/". it is not able to find css. I am using scss.


tailwind autocompletion

Hey Andrew, thank you for all the wonderful Elixir content!
I noticed in your bun video that you had tailwind autocompletion working in heex files and perhaps even within ~H sigils?
I've been using the tailwind and exlir lazyvim extras, e.g., { import = "lazyvim.plugins.extras.lang.tailwind" }
While I do get the colours and the tailwindcss lsp seems to be working fine, I am unable to get autocompletion.
Would you mind sharing your neovim config? Are you doing something custom to make it work?

Nevermind, turned out to be an issue with phx.new....
https://github.com/phoenixframework/phoenix/issues/5967


Make it work for root or users with non-standard home directories

This PR makes the following changes:

Enable root user or users with non-standard home directories to be used as --ec2-user

I tested this PR by manually launching a cluster.
Note: This won't fix this TODO:
# TODO: Make this dependent on HDFS install.
export HADOOP_CONF_DIR="/home/$(logname)/hadoop/conf"

@nchammas, I'm testing this script as a replacement to spark-ec2. As spark-ec2 installs stuff on /root by default and there is some software in our stack that takes this as a convention, I'm trying to keep things smooth for a potential transition.

@nchammas, yes, I tested and it ran a simple spark job that uses HDFS. But I won't guarantee that this installation is 100% functional because I'm couldn't run yet our most complete and demanding jobs due to some differences between this and spark-ec2. I'm just tackling one problem at the time and this was one of the first.

Okie doke, sounds good to me! I'll test this over the weekend and merge in.

@douglaz - Some quick questions for you.

I see that we still have two instances of /home/$(logname) in spark-env.sh and hadoop-env.sh. Shouldn't those also be updated to ~? I assume otherwise this would break on users who have a non-standard home, no?
If I do echo ~ I see that ~ expands to /home/ec2-user for the ec2-user. That means the {u} in the current diff is unnecessary and can be dropped, right?

I agree that it's wrong, but changing it to ~ won't fix it. It's because you don't know who is going to load these environment variables. In our system, for instance, everything is installed under /root but there is a standard user (ec2-user) who's going to read these variables. If ~ is used, this user will think that stuff is installed under his home, which is false. You need to use something like ~{u}, which is an absolute value. Or, better, just define a single time where the spark/hdfs will be installed and use the the full expanded path wherever it's needed
This works if you guarantee the same system user is the one running both commands. This is a reasonable assumption and, AFAIK, true according to current code. But using ~ can be dangerous as shown above because you need to taking in consideration all users that may evaluate this code and guarantee that it's always the same user. I think it's easier and fool-proof to user absolute paths like ~{u} or /tmp (in our system we do something very similar to save metadata about the cluster and we use /tmp)

So to address this problem I believe we need to make the installing user part of the template for spark-env.sh and hadoop-env.sh (like, for example, {master_host}). Does that make sense?
You are correct that we assume the user will stick to one username throughout the cluster's lifecycle, but since as you explained ~{u} is more robust let's leave it that way. 👍

Yes, that would be good

OK, I can merge this in and make that change if you want @douglaz.

Or, alternately, I can directly push to your branch since you've allowed that in this PR.

@nchammas, feel free to push to my branch

Sorry about the delay here. I'm working on a PR that touches many of the templates. Once I get that in I'll revisit this and get it merged in.

Now that #180 is in, I'll get this in next.


Does not work with Jellyfish (2023.3.x)

Plugin is not compatible on newer versions of Android Studio.

Thank you @WonJoongLee !!!


Programatic camera reset

Required Info

Camera Model
D405

Firmware Version
<IP_ADDRESS>

Operating System & Version
Ubuntu20.04

Kernel Version (Linux Only)
5.15.0-76-generic

Platform
PC

SDK Version
latest built from code<IP_ADDRESS>

Language
{C++ }

Segment
{Robot}

We currently need to use the same camera with very different settings, and the only way to achieve this is disconnecting and reconnecting the camera. Not good for production.
Is there a way to do a camera reset  equivalent to that unplug/plug?
Many thanks!
David

Hi @DaveBGld  You do not need to unplug the camera to apply new settings.  You can simply stop the pipeline with an instruction such as pipe.stop(), and then place a new set of cfg instructions after the stop instruction or load a json camera configuration file.  When the pipeline is started again with a pipe.start() instruction then the new settings will be applied.
If you need to reset the camera without an unplug-replug then you can do so with the hardware_reset() script instruction, like the C++ example at https://github.com/IntelRealSense/librealsense/issues/2161#issuecomment-408779150
You could also reset the camera by resetting the entire USB port with an Ubuntu bash script like the example at https://github.com/IntelRealSense/librealsense/issues/8393
An advantage of using a bash script is that the camera does not need to be detected in order for the reset to be initiated.

f you need to reset the camera without an unplug-replug then you can do so with the hardware_reset() script instruction, like the C++ example at #2161 (comment)

After hardware_reset() and restarting the pipe and re-configuring, I get timeout no frames received.

What happens with the first suggestion from #11986 (comment) of stopping the pipeline, applying a new set of cfg instructions and then starting the pipeline again?

That's the start of the problem. After setting manual exposure, only unplugging the camera will allow a new configuration

The main settings that require a pipeline stop and then start to change are resolution and FPS.  With most other settings, including manal exposure, you should be able to change their value with an instruction such as sensor.set_option(RS2_OPTION_EXPOSURE, 33000); whilst the program is running without stopping the pipeline.
On the D405 camera model, you need to access the depth sensor and set a depth exposure value to change the RGB exposure, as D405 does not have a separate RGB sensor and so does not have a separate RGB exposure setting.  Increasing depth exposure will brighten the RGB image and decreasing depth exposure will darken the RGB image.

Hi @DaveBGld  Do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.


Mention factory_factory_girl to readme

Hello, I use factory_girl so often that I created a gem called factory_factory_girl two months ago. It inherited factory_girl_rails's generator and can help generating factory file more convenient. And I wonder if I can add it's link to readme to let more people know about it, thanks.

@st0012 thanks for pointing this out; however, because we don't maintain that gem, I don't feel comfortable linking to it within the docs right now.


Max. length of text documents?

Hi,
I want to use your platform to annotate text documents. But after uploading the txt files, not the entire text document is displayed. It seems to cut each document after 200 lines (+- depending on the file). Is there a specific limit for txt files?
Thanks,
Max

Hi Max,
There are no limits for txt files. We had an issue on the parsing of text files, thank you for spotting it !
A fix should come soon.
Regards,
Maxime

Thanks! When will you release the fixed version? We would like to use it
for a larger annotation task in the next days.  Best,
Max
Maxime Duval @.***> schrieb am Di. 29. Juni 2021 um
17:40:

Hi Max,
There are no limits for txt files. We had an issue on the parsing of text
files, thank you for spotting it !
A fix should come soon.
Regards,
Maxime
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kili-technology/kili-playground/issues/377#issuecomment-870708218,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AASIBLPHEQGYHRIV7HLX5KDTVHSNJANCNFSM47QD3EKA
.

The fix should be deployed now.
Best,
Maxime

It works! Thanks!


Use minimal mock dataset for testing & add testing infrastructure

This can fix #4 and fix #2.
Feel free to tweak this PR as needed. I believe additional iterations & stricter tests, with more edge case testing, can be added as you continue working on this project but this PR should provide a good starting point.

thanks @Bisaloo


making sure the samaritan runs with up to date values for production for

the elections tomorrow

by @noambergIL : prep "good samaritan" for elections tomorrow


GPTQ Integration

What does this PR do ?
This PR adds the possibility to train lora + adalora adapters on top of GPTQ quantized model.
convert to peft model for training
causal_lm_model_id = "marcsun13/opt-350m-gptq-4bit"
tokenizer  = AutoTokenizer.from_pretrained(causal_lm_model_id)
model = AutoModelForCausalLM.from_pretrained(
    causal_lm_model_id,
    torch_dtype=torch.float16,
    device_map="auto"
)
model = prepare_model_for_kbit_training(model)
config = LoraConfig(
      r=16,
      lora_alpha=32,
      target_modules=["q_proj", "v_proj"],
      lora_dropout=0.05,
      bias="none",
      task_type="CAUSAL_LM",
)
model = get_peft_model(model, config)

save adapters after training
model.cpu().save_pretrained(save_dir)

load saved adapters
model = AutoModelForCausalLM.from_pretrained(
    causal_lm_model_id,
    torch_dtype=torch.float16,
    device_map="auto"
)
model = PeftModel.from_pretrained(model ,save_dir)# load saved adapters

to do

[ ] finetune llama2

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Unfortunately, the tests are still failing, I assume because they require the corresponding changes to land in transformers.

I don't want to break the tests so i hardcoded the const value. I will change them back when we will have the next release of transformers


fix: use JsonU256 for deserializing genesis U256s

This uses the JsonU256 deserializer for deserializing each genesis U256, fixing decimal string U256 edge cases like those in https://github.com/gakonst/ethers-rs/pull/2359 for reth's primitive types.

Codecov Report

Merging #2291 (24e38ca) into main (2f61836) will decrease coverage by 14.31%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff             @@
##             main    #2291       +/-   ##
===========================================
- Coverage   72.16%   57.85%   -14.31%
===========================================
  Files         472      472
  Lines       57083    57083
===========================================
- Hits        41195    33028     -8167
- Misses      15888    24055     +8167

Flag
Coverage Δ

integration-tests
14.90% <ø> (-4.25%)
:arrow_down:

unit-tests
54.06% <ø> (-12.78%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

crates/primitives/src/genesis.rs
45.69% <ø> (-51.08%)
:arrow_down:

... and 190 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Bug in example with rotation

Steps:
1)run in portrait mode
2)choose Customization Example
3)expand any cell (for example, iPhone SE)
4)rotate to landscape mode
Result - extra horizontal lines appear

Thank you for mentioning. Next version is going to fix this.


No rows from a simple example, including your examples

Fantastic work and very much appreciated.
Trying to get a feel for this and consistently getting empty rows both for your examples and simple things Im doing, example:
  render() {
    let s = {margin:'100px'};
    return (
      <div style={s}>
	<BigCalendar
	  selectable
	  startAccessor='startDate'
	  endAccessor='endDate'
	  events={[  {
	    'title': 'Long Event',
	    'start': new Date(2016, 9, 18),
	    'end': new Date(2016, 9, 20),
	    'desc': 'Big conference for important people'

	  }]}
	  />
      </div>
    );
  }

yields:

although the other views, the week and day work just fine.
EDIT: I'm pretty sure its my fault and its probably: related to "...which means your container must set an explicit height (feel free to adjust the styles to suit your specific needs)."

Was my fault


fix(readme): trigger semantic release

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Release the latest merged PR

Hello,
I think the latest merged PR are not released right?
When I get the phar with
curl -LO http://pestle.pulsestorm.net/pestle.phar

I don't have their changes, is it done on purpose?
Thanks!

The release process is a little informal -- but generally I keep track of things I'd like to work on most in this Milestone: https://github.com/astorm/pestle/milestone/19  I also add finished PRs from other folks to that Milestone once they're done.
Once we get to around "10 things done" (give or take depending on the size/importance of the things), I cut a release.


Upload to remove server when saved and compiled

Hello,
thank you for you package!
How can I save, compile and automatically upload style.css to remove server?
I have style.scss file, after saving it I need to upload style.css to server. Does it possible?
Thanks!

You can use the "Watch" feature in your .ftpconfig file.  The readme has a pretty good example of them:
"watch":[ // array - Paths to files, directories, or glob patterns that are watched and when edited outside of the atom editor are uploaded. Default : []
        "./dist/stylesheets/main.css", // reference from the root of the project.
        "./dist/stylesheets/",
        "./dist/stylesheets/*.css"
    ],


Add --force flag

Without the --force flag, sanitize-repo will complain if there are untracked or uncommitted tracked files in the repo
Fix #31

@slarse This should now be finished enough to merge


Update to ZAP 2.12.0

As per the title ;)
https://www.zaproxy.org/download/

Closes #9586

[x] I have read the Contributing Guide.

Updated to use java/temurin11-jre 😁


[HUDI-1976] Resolve Hive and Jackson vulnerability

Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contributing.html before opening a pull request.

What is the purpose of the pull request
(For example: This pull request adds quick-start document.)
Brief change log
(for example:)

Modify AnnotationLocation checkstyle rule in checkstyle.xml

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[x] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

The build is passing locally but there are many overlapping classes warnings
jackson-annotations-2.6.7.jar, hive-exec-2.3.9.jar define 58 overlapping classes:

parquet-avro-1.11.1.jar, parquet-column-1.11.1.jar define 145 overlapping classes:

joda-time-2.9.9.jar, hive-exec-2.3.9.jar define 246 overlapping classes:

parquet-format-structures-1.11.1.jar, hive-exec-2.3.9.jar define 81 overlapping classes:

parquet-encoding-1.11.1.jar, hive-exec-2.3.9.jar define 169 overlapping classes:

parquet-common-1.11.1.jar, hive-exec-2.3.9.jar define 44 overlapping classes:

avro-1.10.0.jar, hive-exec-2.3.9.jar define 346 overlapping classes:

jackson-core-2.6.7.jar, hive-exec-2.3.9.jar define 93 overlapping classes:

parquet-hadoop-1.11.1.jar, parquet-avro-1.11.1.jar, parquet-column-1.11.1.jar define 50 overlapping classes:

hive-exec-2.3.9.jar, jackson-databind-<IP_ADDRESS>.jar define 549 overlapping classes:

Also, this needs to be tested properly to ensure that there are no dependency conflict issues arising because of this change

Codecov Report

Merging #3071 (f30b359) into master (ba728d8) will decrease coverage by 2.48%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #3071      +/-   ##
============================================
- Coverage     55.37%   52.88%   -2.49%
+ Complexity     4029     3481     -548
============================================
  Files           521      454      -67
  Lines         25312    22477    -2835
  Branches       2873     2589     -284
============================================
- Hits          14017    11888    -2129
+ Misses         9907     9395     -512
+ Partials       1388     1194     -194

Flag
Coverage Δ

hudicli
39.95% <ø> (ø)

hudiclient
∅ <ø> (∅)

hudicommon
48.21% <ø> (-1.83%)
:arrow_down:

hudiflink
61.50% <ø> (-1.54%)
:arrow_down:

hudihadoopmr
51.34% <ø> (-0.09%)
:arrow_down:

hudisparkdatasource
67.06% <ø> (+0.54%)
:arrow_up:

hudisync
?

huditimelineservice
?

hudiutilities
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

.../org/apache/hudi/sink/compact/CompactFunction.java
86.66% <0.00%> (-13.34%)
:arrow_down:

...e/hudi/sink/partitioner/profile/WriteProfiles.java
46.80% <0.00%> (-13.20%)
:arrow_down:

...apache/hudi/sink/compact/CompactionCommitSink.java
66.66% <0.00%> (-8.34%)
:arrow_down:

...src/main/scala/org/apache/hudi/DefaultSource.scala
75.22% <0.00%> (-4.57%)
:arrow_down:

...i/common/table/timeline/HoodieDefaultTimeline.java
79.22% <0.00%> (-1.30%)
:arrow_down:

...ache/hudi/hadoop/utils/HoodieInputFormatUtils.java
54.35% <0.00%> (-0.85%)
:arrow_down:

...java/org/apache/hudi/sink/StreamWriteFunction.java
84.34% <0.00%> (-0.66%)
:arrow_down:

...va/org/apache/hudi/metadata/BaseTableMetadata.java
0.00% <0.00%> (ø)

.../java/org/apache/hudi/hadoop/InputPathHandler.java
100.00% <0.00%> (ø)

.../org/apache/hudi/streamer/FlinkStreamerConfig.java
0.00% <0.00%> (ø)

... and 116 more

@n3nash @vinothchandar please review

Have not had a chance to debug the tests failures yet. We could rebase and see where to go from there.?

@vinaypatil18 : Can you rebase with latest master. I will try to take a look at the failures.

@codope : can you review this patch please

@veenaypatil @nsivabalan  I've rebased. I can reproduce the error due to which spark3.1.x build failed. Will look into it.

@veenaypatil I've fixed the build failure. But IT tests are failing due to
[ERROR] This symbol is required by ' <none>'.
[ERROR] Make sure that term annotation is in your classpath and check for conflicting dependencies with `-Ylog-classpath`.
[ERROR] A full rebuild may help if 'RDDOperationScope.class' was compiled against an incompatible version of com.fasterxml.jackson.

I see that you also upgraded farterxml version and perhaps that version is incompatible. Is that rally necessary? Can you please check?

@codope there were certain vulnerabilities reported here https://github.com/apache/hudi/issues/2826 due to which we upgrade Jackson, this was specifically for databind only. Should we update only for this dependency in that case ?

Yeah let's try that. Would be better to scope dependency changes to the minimum.

@codope there were certain vulnerabilities reported here #2826 due to which we upgrade Jackson, this was specifically for databind only. Should we update only for this dependency in that case ?

@veenaypatil i tried w/ upgrading only the databind and there were a lot dep failures. Looks like we need to upgrade whole fasterxml but that might cause another compatibility issue https://github.com/apache/hudi/pull/3071#issuecomment-1070668516
Did you get a chance to fix this?

this change will be included / overwritten by https://github.com/apache/hudi/pull/5402
cc @codope @rahil-c


Added scale support for code39

Returned value of Encode method on code39 was not allowing barcode.scale method. So added EncodeWithoutChecksum method code39 encoder

It should already bei scaleable since it implements the barcode Interface

The Link results in 404...

@boombuler Ah my bad. updated the link.
https://i.imgur.com/0dDbtle.png

The problem is that the bcode variable is implicitly declared as BarcodeIntCS If you explicitly declare it as barcode.Barcode it should work fine

maybe I'm too stupid. can you provide a sample code?
i'm trying code128. same problem.

package main

import (
	"github.com/boombuler/barcode"
	"github.com/boombuler/barcode/code128"
)

func main() {
	var code barcode.Barcode
	var err error
	code, err = code128.Encode("Hallo")
	if err != nil {
		fmt.Println(err)
		return
	}
	code, err = barcode.Scale(code, 200, 200)
	// ... Do something with code and err....
}


Thread Detected: Trojan:Win32/Wacatac.DF!ml

When downloading the latest version, N_m3u8DL-CLI_v2.9.5.exe, Windows detects the following malware inside:
Win32/Wacatac.DF!ml
Has this issue been addressed?

https://www.microsoft.com/en-us/wdsi/filesubmission


[Bug]: API link doesn't work

Bug description
Steps to reproduce the problem:

go to the github puppeteer page
click on the api link which is pointing to https://github.com/puppeteer/puppeteer/blob/v11.0.0/docs/api.md it returns a 404

Puppeteer version
NA
Node.js version
NA
npm version
NA
What operating system are you seeing the problem on?
macOS
Relevant log output
No response

Hi @sulthan-ahmed ! Can I work on this issue?

Hi @harshagrawal523 looks like someone has fixed it maybe it was yourself. Thank you either way 🙂


Mockingbird by Eminem

Song Name
Mockingbird
Artist Name
Eminem
Source
Youtube
Youtube Link
Tzs7YPpJ6PA7tldB
Direct File Link
No response
Song ID
559647
Start Offset [ms]
0
Extra
Created from Auto Nong.
Created for level: 8909427

Tzs7YPpJ6PA7tldB


add basic redesign

error overlay has still to be tested

I think I already see the error. The documentation is a bit misleading but I think I told you wrong things there. I corrected the doc and I'll correct the app in the evening


Support to force full refresh on individual models as part of the --models argument

Completely untested, code is for demonstration only
Usage:
dbt run --models !foo !+bar !baz+ @!alpha !@alpha !tag:nightly

Use the ! character at the start of a model filter to require all models matched by that filter to be full refreshed.
Handles multiple matching filters correctly (always prefer full refresh)
Eg if you dag is foo > bar > baz and your command is dbt run --models foo+ !bar+ then bar and baz will have a full refresh
Issues/comments:

Method of implementation feels hacky.
Does not work with models/macros that use flags.FULL_REFRESH, but does work with is_incremental() macro.

Posting here for feedback :)

(Agreed to CLA)

Thanks @elexisvenator! You should be all set on the CLA! (@cla-bot check)
I think this is really cool!! I'd love to combine this with #1009 so that we can nix the flags.FULL_REFRESH global state altogether. We'd just need to replace flags.FULL_REFRESH with config.get('full_refresh'), or similar. This has the added benefit of making full-refresh logic configurable from within a model, eg:
{{ config(materialized='incremental', full_refresh=var('refresh_me', false)) }}

dbt's existing --model selectors are purely for selection purposes. They don't impact the configs/properties of models, they just select a subset of models to run. I'm open to the idea of adding semantically meaningful identifiers like ! to this syntax, but I'd like to explore the idea a little further. How does this selector apply to other resources (like tests, seeds, snapshots, etc). Should it be supported to specify that selector in a dbt test invocation? And are there other sorts of operators like this which we'd want to represent as well?
This is a super neat stake in the ground - I'll give this some more thought and follow up here! Thanks for opening up the conversation :)

I tend to agree that adding meaning to the --model selectors other than selection is confusing, which implies that maybe this goes past what a call to dbt from command line should be able to do.  Maybe this should be something that needs to be passed in (via api?) using a json based run definition? (which will also allow more flexibility later)
Something like:
{
  "steps": [
    { "command": "seed" },
    {
      "command": "run",
      "models": [
        { "filter": "foo+" },
        {
          "filter": "bar+",
          "full-refresh": true
        }
      ],
      "exclude": [{ "filter": "baz" }]
    },
    { "command": "test" },
    { "command": "docs generate" }
  ]
}

I LOVE that! This just came up earlier today. We'll probably end up using yaml for something like this, but I imagine the syntax will look very similar to what you've provided here!
Then, I imagine you could run it with something like:
dbt run -f nightly_refresh.yml

This has the benefit of being both really expressive & version controllable.
Semi-related: https://github.com/fishtown-analytics/dbt/issues/594


Files being deleted from other plugins

I'm not 100% sure if it is the case, but it seems as if permalinks is replacing folders with the permalink structure defined in a given linkset. For example:
When I run a pagination plugin:
A directory is created with paginated post items like this;
blog/
  1/
    index.html
  2/
    index.html

I then want to permalink each post to be blog/2016/08/23/post-title-here, so I implement permalinks after:
{
        "match": { "collection": "posts" },
        "pattern": "blog/:date/:title"
      },

The result is a single folder:
blog/
   2016/
      08/
        23/
          post-title-here/
            index.html

How can I fix this?

Yep, I think this is it: https://github.com/segmentio/metalsmith-permalinks/blob/master/lib/index.js#L93


Bump Go to 1.23.1

Closes #5826

We should probably wait for https://github.com/golang/go/issues/69312 to get fixed in 1.23.x as it impacts libp2p.

as it impacts libp2p.

How did you figure this out? Was it due to failed tests, or are you tracking issues of all our dependencies? :thinking:

Yeah, I'm tracking issues and changelogs of some of our key dependencies :)

Looks like the issue has been fixed in Go 1.23.2.


Unable to pass jvm args

Hi,
The command below works fine on our CI without
  -a -Dorg.gradle.jvmargs=\"-Xmx24g\ -XX:+UseParallelGC\ -XX:NativeMemoryTracking=summary\ -XX:+UseGCOverheadLimit\ -XX:MetaspaceSize=4g\ -XX:MaxMetaspaceSize=12g\ -XX:+UnlockDiagnosticVMOptions\ -XX:+PrintFlagsFinal\"

But when we use it, you'll see the error attached Unknown command-line option '-X'.
The command being executed works fine when I run it, but it seems to have dropped the other args I want to pass to Gradle.

Resolving deltas: 100% (7336/7336), done.
Updating files: 100% (22760/22760), done.

Running first build:
./gradlew --no-build-cache --scan -Dscan.tag.exp1-gradle -Dscan.value.runId=63dd64a6 clean app:aFD -Dorg.gradle.jvmargs="-Xmx24g -XX:+UseParallelGC -XX:NativeMemoryTracking=summary -XX:+UseGCOverheadLimit -XX:MetaspaceSize=4g -XX:MaxMetaspaceSize=12g -XX:+UnlockDiagnosticVMOptions -XX:+PrintFlagsFinal"

Unknown command-line option '-X'.

USAGE: gradlew [option...] [task...]

-?, -h, --help                     Shows this help message.
-a, --no-rebuild                   Do not rebuild project dependencies.
-b, --build-file                   Specify the build file. [deprecated]
--build-cache                      Enables the Gradle build cache. Gradle will try to reuse outputs from previous builds.
-c, --settings-file                Specify the settings file. [deprecated]
--configuration-cache              Enables the configuration cache. Gradle will try to reuse the build configuration from previous builds. [incubating]
--configuration-cache-problems     Configures how the configuration cache handles problems (fail or warn). Defaults to fail. [incubating]
--configure-on-demand              Configure necessary projects only. Gradle will attempt to reduce configuration time for large multi-project builds. [incubating]
--console                          Specifies which type of console output to generate. Values are 'plain', 'auto' (default), 'rich' or 'verbose'.
--continue                         Continue task execution after a task failure.
-D, --system-prop                  Set system property of the JVM (e.g. -Dmyprop=myvalue).
-d, --debug                        Log in debug mode (includes normal stacktrace).
--daemon                           Uses the Gradle daemon to run the build. Starts the daemon if not running.
--export-keys                      Exports the public keys used for dependency verification.
-F, --dependency-verification      Configures the dependency verification mode. Values are 'strict', 'lenient' or 'off'.
--foreground                       Starts the Gradle daemon in the foreground.
-g, --gradle-user-home             Specifies the Gradle user home directory. Defaults to ~/.gradle
-I, --init-script                  Specify an initialization script.
-i, --info                         Set log level to info.
--include-build                    Include the specified build in the composite.
-M, --write-verification-metadata  Generates checksums for dependencies used in the project (comma-separated list)
-m, --dry-run                      Run the builds with all task actions disabled.
--max-workers                      Configure the number of concurrent workers Gradle is allowed to use.
--no-build-cache                   Disables the Gradle build cache.
--no-configuration-cache           Disables the configuration cache. [incubating]
--no-configure-on-demand           Disables the use of configuration on demand. [incubating]
--no-daemon                        Do not use the Gradle daemon to run the build. Useful occasionally if you have configured Gradle to always run with the daemon by default.
--no-parallel                      Disables parallel execution to build projects.
--no-scan                          Disables the creation of a build scan. For more information about build scans, please visit https://gradle.com/build-scans.
--no-watch-fs                      Disables watching the file system.
--offline                          Execute the build without accessing network resources.
-P, --project-prop                 Set project property for the build script (e.g. -Pmyprop=myvalue).
-p, --project-dir                  Specifies the start directory for Gradle. Defaults to current directory.
--parallel                         Build projects in parallel. Gradle will attempt to determine the optimal number of executor threads to use.
--priority                         Specifies the scheduling priority for the Gradle daemon and all processes launched by it. Values are 'normal' (default) or 'low'
--profile                          Profile build execution time and generates a report in the <build_dir>/reports/profile directory.
--project-cache-dir                Specify the project-specific cache directory. Defaults to .gradle in the root project directory.
-q, --quiet                        Log errors only.
--refresh-dependencies             Refresh the state of dependencies.
--refresh-keys                     Refresh the public keys used for dependency verification.
--rerun-tasks                      Ignore previously cached task results.
-S, --full-stacktrace              Print out the full (very verbose) stacktrace for all exceptions.
-s, --stacktrace                   Print out the stacktrace for all exceptions.
--scan                             Creates a build scan. Gradle will emit a warning if the build scan plugin has not been applied. (https://gradle.com/build-scans)
--status                           Shows status of running and recently stopped Gradle daemon(s).
--stop                             Stops the Gradle daemon if it is running.
-t, --continuous                   Enables continuous build. Gradle does not exit and will re-execute tasks when task file inputs change.
--update-locks                     Perform a partial update of the dependency lock, letting passed in module notations change version. [incubating]
-v, --version                      Print version info.
-w, --warn                         Set log level to warn.
--warning-mode                     Specifies which mode of warnings to generate. Values are 'all', 'fail', 'summary'(default) or 'none'
--watch-fs                         Enables watching the file system for changes, allowing data about the file system to be re-used for the next build.
--write-locks                      Persists dependency resolution for locked configurations, ignoring existing locking information if it exists
-x, --exclude-task                 Specify a task to be excluded from execution.

Hi, @changusmc! Thanks for opening this issue.
Could you try wrapping the value of -a in single quotes? For example:
./01-validate-incremental-building.sh \
  -s https://gradle-enterprise.com \
  -r ${BUILDKITE_REPO} \
  -b master \
  --tasks app:aFD \
  -a -PforceDisableAllTasksAndPlugins \
  -a -PforceDisableExtraVariants \
  -a --no-configuration-cache \
  -a '-Dorg.gradle.jvmargs="-Xmx24g -XX:+UseParallelGC -XX:NativeMemoryTracking=summary -XX:+UseGCOverheadLimit -XX:MetaspaceSize=4g -XX:MaxMetaspaceSize=12g -XX:+UnlockDiagnosticVMOptions -XX:+PrintFlagsFinal"'

@changusmc something I just noticed is that you are passing multiple occurrences of -a to the scripts. This is not supported and may result in unexpected behavior. You should instead supply all desired Gradle arguments using one -a like so:
./01-validate-incremental-building.sh \
  -s https://gradle-enterprise.com \
  -r ${BUILDKITE_REPO} \
  -b master \
  --tasks app:aFD \
  -a '-PforceDisableAllTasksAndPlugins -PforceDisableExtraVariants --no-configuration-cache -Dorg.gradle.jvmargs="-Xmx24g -XX:+UseParallelGC -XX:NativeMemoryTracking=summary -XX:+UseGCOverheadLimit -XX:MetaspaceSize=4g -XX:MaxMetaspaceSize=12g -XX:+UnlockDiagnosticVMOptions -XX:+PrintFlagsFinal"'

Hi @erichaagdev , thanks for the quick response!
I tried your suggestion and it's still failing for the same error:

Running first build:
--
  | ./gradlew --build-cache --scan -Dscan.tag.exp3-gradle -Dscan.value.runId=63dd83cd clean app:aFD -PforceDisableAllTasksAndPlugins -PforceDisableExtraVariants --no-configuration-cache -Dorg.gradle.jvmargs="-Xmx24g -XX:+UseParallelGC -XX:NativeMemoryTracking=summary -XX:+UseGCOverheadLimit -XX:MetaspaceSize=4g -XX:MaxMetaspaceSize=12g -XX:+UnlockDiagnosticVMOptions -XX:+PrintFlagsFinal"
  |
  | Unknown command-line option '-X'.

Thanks for trying it out. The additional arguments look much better this time.
I was also able to reproduce this with the following:
./01-validate-incremental-building.sh \
  -r https://github.com/gradle/common-custom-user-data-gradle-plugin \
  -t build \
  -a -Dorg.gradle.jvmargs="-Xmx2g -XX:MaxMetaspaceSize=512m"

Thanks again for reporting the issue. I will continue to investigate it.
In the meantime, are you able to add the additional JVM arguments to your gradle.properties file? You can see Configuring JVM memory in the Gradle documentation for how to do that.


Show/Hide maximized terminal window resizes it briefly

Windows Terminal version
1.13.10984.0
Windows build number
10.0.22000.0
Other Software
No response
Steps to reproduce
Maximize the window
use action to show/hide the terminal window
Expected Behavior
window appears maximized
Actual Behavior
window appears big, but not maximized, and then maximizes, additionally causing the whole terminal size to be recalculated and content re-rendered and shifted slightly upwards

use action to show/hide the terminal window

Which action exactly/? There's a lot of parameters to globalSummon so I wanna make sure I'm checking out the right thing ☺

I'm using the action straight from the GUI so everything is set to defaults

Ah, okay so you're using the quakeMode action, the one that says "Show/Hide Quake window". Hence my confusion, there is a "Show/Hide the Terminal window" action, but that isn't bound by default...................
Wait but that's not right either, the quake window doesn't remember it's size at all. Maximizing that, hiding, then showing won't remotely reappear maximized.
Could you share your settings.json file/?

I'm using the Show/hide the Terminal window action (or globalSummon in the config file), as quake mode as-is doesn't cut it for me, it's not bound by default, but I added it from GUI and haven't changed anything to override any parameters so in config it states
{
            "command":
            {
                "action": "globalSummon"
            },
            "keys": "ctrl+`"
        },

the complete `settings.json` in case it helps:
{
    "$help": "https://aka.ms/terminal-documentation",
    "$schema": "https://aka.ms/terminal-profiles-schema",
    "actions":
    [
        {
            "command":
            {
                "action": "switchToTab",
                "index": 6
            },
            "keys": "ctrl+alt+7"
        },
        {
            "command":
            {
                "action": "newTab",
                "index": 0
            },
            "keys": "ctrl+shift+1"
        },
        {
            "command":
            {
                "action": "moveFocus",
                "direction": "left"
            },
            "keys": "ctrl+alt+left"
        },
        {
            "command":
            {
                "action": "scrollUp"
            },
            "keys": "ctrl+shift+up"
        },
        {
            "command": "closeWindow",
            "keys": "alt+f4"
        },
        {
            "command":
            {
                "action": "moveFocus",
                "direction": "right"
            },
            "keys": "ctrl+alt+right"
        },
        {
            "command": "openTabColorPicker"
        },
        {
            "command": "toggleFullscreen",
            "keys": "alt+enter"
        },
        {
            "command": "toggleFullscreen",
            "keys": "f11"
        },
        {
            "command":
            {
                "action": "switchToTab",
                "index": 0
            },
            "keys": "ctrl+alt+1"
        },
        {
            "command": "openNewTabDropdown",
            "keys": "ctrl+shift+space"
        },
        {
            "command": "toggleFocusMode"
        },
        {
            "command": "openTabRenamer"
        },
        {
            "command":
            {
                "action": "splitPane",
                "split": "down"
            },
            "keys": "alt+shift+minus"
        },
        {
            "command":
            {
                "action": "commandPalette"
            },
            "keys": "ctrl+shift+p"
        },
        {
            "command": "scrollUpPage",
            "keys": "ctrl+shift+pgup"
        },
        {
            "command":
            {
                "action": "openSettings",
                "target": "defaultsFile"
            },
            "keys": "ctrl+alt+comma"
        },
        {
            "command":
            {
                "action": "newTab",
                "index": 6
            },
            "keys": "ctrl+shift+7"
        },
        {
            "command":
            {
                "action": "adjustFontSize",
                "delta": -1
            },
            "keys": "ctrl+minus"
        },
        {
            "command": "find",
            "keys": "ctrl+shift+f"
        },
        {
            "command":
            {
                "action": "newTab",
                "index": 4
            },
            "keys": "ctrl+shift+5"
        },
        {
            "command": "toggleAlwaysOnTop"
        },
        {
            "command":
            {
                "action": "newTab",
                "index": 8
            },
            "keys": "ctrl+shift+9"
        },
        {
            "command": "duplicateTab",
            "keys": "ctrl+shift+d"
        },
        {
            "command":
            {
                "action": "openSettings"
            },
            "keys": "ctrl+comma"
        },
        {
            "command":
            {
                "action": "resizePane",
                "direction": "up"
            },
            "keys": "alt+shift+up"
        },
        {
            "command":
            {
                "action": "renameTab"
            }
        },
        {
            "command":
            {
                "action": "resizePane",
                "direction": "left"
            },
            "keys": "alt+shift+left"
        },
        {
            "command":
            {
                "action": "moveFocus",
                "direction": "down"
            },
            "keys": "ctrl+alt+down"
        },
        {
            "command": "unbound",
            "keys": "win+`"
        },
        {
            "command": "unbound",
            "keys": "alt+left"
        },
        {
            "command": "unbound",
            "keys": "alt+right"
        },
        {
            "command": "unbound",
            "keys": "alt+up"
        },
        {
            "command": "unbound",
            "keys": "alt+down"
        },
        {
            "command": "unbound",
            "keys": "ctrl+shift+`"
        },
        {
            "command":
            {
                "action": "switchToTab",
                "index": 2
            },
            "keys": "ctrl+alt+3"
        },
        {
            "command":
            {
                "action": "switchToTab",
                "index": 7
            },
            "keys": "ctrl+alt+8"
        },
        {
            "command":
            {
                "action": "newTab",
                "index": 2
            },
            "keys": "ctrl+shift+3"
        },
        {
            "command":
            {
                "action": "copy",
                "singleLine": false
            },
            "keys": "ctrl+shift+c"
        },
        {
            "command":
            {
                "action": "copy",
                "singleLine": false
            },
            "keys": "ctrl+insert"
        },
        {
            "command":
            {
                "action": "splitPane",
                "split": "right"
            },
            "keys": "alt+shift+plus"
        },
        {
            "command":
            {
                "action": "prevTab"
            },
            "keys": "ctrl+shift+tab"
        },
        {
            "command":
            {
                "action": "closeOtherTabs"
            }
        },
        {
            "command":
            {
                "action": "closeTab"
            },
            "keys": "ctrl+w"
        },
        {
            "command":
            {
                "action": "closeTabsAfter"
            }
        },
        {
            "command":
            {
                "action": "switchToTab",
                "index": 1
            },
            "keys": "ctrl+alt+2"
        },
        {
            "command":
            {
                "action": "switchToTab",
                "index": 4
            },
            "keys": "ctrl+alt+5"
        },
        {
            "command":
            {
                "action": "adjustFontSize",
                "delta": 1
            },
            "keys": "ctrl+plus"
        },
        {
            "command":
            {
                "action": "newTab"
            },
            "keys": "ctrl+t"
        },
        {
            "command":
            {
                "action": "newTab",
                "index": 1
            },
            "keys": "ctrl+shift+2"
        },
        {
            "command":
            {
                "action": "switchToTab",
                "index": 5
            },
            "keys": "ctrl+alt+6"
        },
        {
            "command":
            {
                "action": "switchToTab",
                "index": 8
            },
            "keys": "ctrl+alt+9"
        },
        {
            "command":
            {
                "action": "moveFocus",
                "direction": "up"
            },
            "keys": "ctrl+alt+up"
        },
        {
            "command":
            {
                "action": "newTab",
                "index": 3
            },
            "keys": "ctrl+shift+4"
        },
        {
            "command": "resetFontSize",
            "keys": "ctrl+0"
        },
        {
            "command":
            {
                "action": "newTab",
                "index": 5
            },
            "keys": "ctrl+shift+6"
        },
        {
            "command":
            {
                "action": "newTab",
                "index": 7
            },
            "keys": "ctrl+shift+8"
        },
        {
            "command":
            {
                "action": "nextTab"
            },
            "keys": "ctrl+tab"
        },
        {
            "command":
            {
                "action": "switchToTab",
                "index": 3
            },
            "keys": "ctrl+alt+4"
        },
        {
            "command":
            {
                "action": "scrollDown"
            },
            "keys": "ctrl+shift+down"
        },
        {
            "command": "closePane",
            "keys": "ctrl+shift+w"
        },
        {
            "command": "togglePaneZoom"
        },
        {
            "command": "scrollDownPage",
            "keys": "ctrl+shift+pgdn"
        },
        {
            "command":
            {
                "action": "resizePane",
                "direction": "down"
            },
            "keys": "alt+shift+down"
        },
        {
            "command":
            {
                "action": "resizePane",
                "direction": "right"
            },
            "keys": "alt+shift+right"
        },
        {
            "command": "paste",
            "keys": "ctrl+shift+v"
        },
        {
            "command": "paste",
            "keys": "shift+insert"
        },
        {
            "command":
            {
                "action": "globalSummon"
            },
            "keys": "ctrl+`"
        },
        // Other commands
        {
            "commands":
            [
                {
                    "command":
                    {
                        "action": "setColorScheme",
                        "colorScheme": "${scheme.name}"
                    },
                    "iterateOn": "schemes",
                    "name": "${scheme.name}"
                }
            ],
            // Select color scheme...
            "name":
            {
                "key": "SetColorSchemeParentCommandName"
            }
        },
        {
            "commands":
            [
                {
                    "commands":
                    [
                        {
                            "command":
                            {
                                "action": "splitPane",
                                "profile": "${profile.name}",
                                "split": "auto"
                            }
                        },
                        {
                            "command":
                            {
                                "action": "splitPane",
                                "profile": "${profile.name}",
                                "split": "vertical"
                            }
                        },
                        {
                            "command":
                            {
                                "action": "splitPane",
                                "profile": "${profile.name}",
                                "split": "horizontal"
                            }
                        }
                    ],
                    "icon": "${profile.icon}",
                    "iterateOn": "profiles",
                    "name": "${profile.name}..."
                 The Terminal comes back to the size of the whole screen, then it maximizes on the next "frame", so to speak. I bet in IslandWindow::_globalActivateWindow, when we SW_RESTORE, we could like, SW_MAXIMIZE instead (if we knew the Terminal was maximized before)

Holy cow, I think I can add to this bug. It's not exactly the same, but it's similar. If you want me to do a new issue, let me know.
My setting that is controlling globalSummon:
"command": {
	"action": "globalSummon",
	"desktop": "toCurrent",
	"dropdownDuration": 250,
	"monitor": "any",
	"toggleVisibility": true
},
"keys": "win+`"
},

With these settings, I get same behavior described by @zakius , except it never maximizes again. If I maximize it by hand by hand, it stays.
If I dismiss and summon it, it goes back to "big but not maximized" mode.
When I saw this thread, I tried reducing the command up there to:
"command": {
	"action": "globalSummon",
},
"keys": "win+`"
},

And now it worked correctly and stayed maximized. I put it all back to the first one, and started troubleshooting. It turns out that in my install at least, if I remove dropdownDuration it all works as expected.
That is the last one I would of expected to cause an issue, but here we are :)
Let me know if you need/want anything else to help with this, but I'm 100% cool living with the default dropdownDuration and having it maximized.

that's an interesting find! unfortunately I just can't stand delays caused by blocking animations so that's not an option for me but may help fixing it! thanks

Oh yeah, for sure not a fix, but hopefully it helps whoever picks this bug up. I am ok with delays as long as functionality is there, so I'm all good on this.
Hopefully they figure out your issue!