feat(rtc_manager_rviz_plugin): add_indivisual_exe

Signed-off-by: tanaka3<EMAIL_ADDRESS>Description
add individual execution for RTC modules
Related links
resolve https://github.com/autowarefoundation/autoware.universe/issues/2010
[tier4 INTERNAL LINK]
Tests performed
by psim
https://user-images.githubusercontent.com/65527974/193985856-cbdef527-9192-4cb6-bc71-117657961a11.mp4
Notes for reviewers
this PR can be tested by psim
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@rej55
can you review this PR?


Don't install GoogleTest and GoogleMock artifacts along with sq.

GoogleTest and GoogleMock artifacts are being installed along with sq:
INFO:root:Running command ["ninja", "install"] with options {}
[0/1] Install the project...
-- Install configuration: "Release"
-- Up-to-date: /usr/local/include
-- Installing: /usr/local/include/gmock
-- Installing: /usr/local/include/gmock/gmock-generated-function-mockers.h
-- Installing: /usr/local/include/gmock/gmock-more-matchers.h
-- Installing: /usr/local/include/gmock/gmock.h
-- Installing: /usr/local/include/gmock/gmock-matchers.h
-- Installing: /usr/local/include/gmock/gmock-generated-matchers.h
-- Installing: /usr/local/include/gmock/gmock-generated-function-mockers.h.pump
-- Installing: /usr/local/include/gmock/gmock-cardinalities.h

That's not supposed to be happening because we put set(INSTALL_GTEST OFF) in CMakeLists.txt.

Earlier in the build output:
CMake Warning (dev) at build/_deps/get_googletest-src/CMakeLists.txt:30 (option):
  Policy CMP0077 is not set: option() honors normal variables.  Run "cmake
  --help-policy CMP0077" for policy details.  Use the cmake_policy command to
  set the policy and suppress this warning.

  For compatibility with older versions of CMake, option is clearing the
  normal variable 'INSTALL_GTEST'.
This warning is for project developers.  Use -Wno-dev to suppress it.


mbed-os.lib not pointing to mbed 5.6.0 release candidate in branch mbed-os-5.6.0-oob

It appears mbed-os.lib is not pointing to the correct commit number that is tagged as the mbed OS 5.6.0 release candidate in the branch mbed-os-5.6.0-oob. This is causing the CLI and mbed-ls tools to believe it has checked out the correct branch when running mbed update mbed-os-5.6.0-oob but the underlying mbed-os folder is still reporting as being checked out to mbed-os-5.5.0.
For example, when checking out the mbed-os-5.6.0-oob branch:
C:\Users\davwal04\Desktop\Out of box campaigns\mbed OS 5.6\mbed-os-example-blinky>mbed update mbed-os-5.6.0-oob
[mbed] Updating program "mbed-os-example-blinky" to branch mbed-os-5.6.0-oob
[mbed] Updating library "mbed-os" to rev #afffea9a848b
fatal: reference is not a tree: afffea9a848b443796d952cb406206f1a6f8d257
[mbed] ERROR: Unable to update "mbed-os" to rev #afffea9a848b

When looking inside the mbed-os-example-blinky folder:
C:\Users\davwal04\Desktop\Out of box campaigns\mbed OS 5.6\mbed-os-example-blinky>git status
On branch mbed-os-5.6.0-oob
Your branch is up-to-date with 'origin/mbed-os-5.6.0-oob'.
nothing to commit, working tree clean

but when you look into the underlying mbed-os folder:
C:\Users\davwal04\Desktop\Out of box campaigns\mbed OS 5.6\mbed-os-example-blinky>cd mbed-os
C:\Users\davwal04\Desktop\Out of box campaigns\mbed OS 5.6\mbed-os-example-blinky\mbed-os>git status
On branch mbed-os-5.5
Your branch is up-to-date with 'origin/mbed-os-5.5'.
nothing to commit, working tree clean

The correct commit that mbed-os.lib should be pointing to is:
+https://github.com/ARMmbed/mbed-os/#a4056fb8bf3ee10b8e037d332f8fbd0c68169ef1
Please reference PR: https://github.com/ARMmbed/mbed-os-example-blinky/pull/80/commits/6f8c4e64586836b457164183fdfc364b63bcb631

@dhwalters423 thanks for raising this! I'm also able to reproduce
@sg- @adbridge are you ok if we update all examples to suggested commit? (a4056fb8bf3ee10b8e037d332f8fbd0c68169ef1)

@dhwalters423 fyi @adbridge has re-created the branches using this name: mbed-os-5.6-oob
I've verified and works ok. OOB spreadsheet updated.


Modify redis guestbook example to use a term other than 'slaves'

I'd like to see us avoid the use of the term 'slave' in the guestbook redis stuff where possible.
Maybe use 'minion' instead for all the names and labels.
As part of this, the frontend image (kubernetes/example-guestbook-php-redis:v2) will need to be rebuilt, since it references 'redis-slave' in the php script.

This is a Redis term, for what it's worth.  http://redis.io/topics/replication  We still may or may not want to change what we use.

yeah, I know... I still constantly wince, though, and suspect many others do the same.

If we are going to get rid of salve then do we also need to get rid of master?

After discussion w/ Brendan, we're going to punt on doing this, at least for now.


Freezing on update / install

VSCode Version: 1.6.1
OS Version: Win 10 pro

Steps to Reproduce:

New Install from download
Click "Update Now" on pop up in program

When I click the update now pop up it takes me to the 'Preparing to Install' dialog box and freezes.  No dialog appears in the box and hovering over it only shows the windows loading cursor.  Only way to close the box is through task manager.  The same happens if I download the latest version and try to install that way.

Do you have any antivirus installed? Does it reproduce if you disable it temporarily?

Apologies for the delay in replying.  Yes I have Panda Global Protection installed and disabling it enabled the update to work without a problem.  Thanks.


Unit Test is too slow

On Mac OSX, current unit test takes 20+min to complete all unit test. One of reason is now unit test run both SQLite and ForestDB. On Android device, ridiculously slow. Need to complete in 5 min at least.
Especially ReplicationTest and RouterTest.

Timeboxing for 2 hours max to see if some easy win can be found.

I have observed the following in the ReplicatorTests.

testContinuousPullReplicationGoesIdleTwice
Always wait for ~18 seconds:
success = enteredRunningState.await(30, TimeUnit.SECONDS);

testContinuousPullReplicationSendStoppedOnce
Always wait for 30 seconds to make sure that no 2 stopped state events notified:

// 4. wait until its RUNNING
Log.d(TAG, "WAIT for STOPPED");
success = enteredStoppedState.await(30, TimeUnit.SECONDS);

testOneTimePullReplicationSendStoppedOnce
Always wait for 30 seconds to make sure that no 2 stopped state events notified:

// 2. wait until its RUNNING
Log.d(TAG, "WAIT for STOPPED");
boolean success = enteredStoppedState.await(30, TimeUnit.SECONDS);
// if STOPPED notification was sent twice, enteredStoppedState becomes 0.
assertEquals(1, enteredStoppedState.getCount());
assertFalse(success);

Sometimes (occurred randomly) when closing the database in tearDown(), wait for ~60 seconds.

Here is where it got stuck when running testPushUpdatedDocWithoutReSendingAttachments:
"Instr: android.test.InstrumentationTestRunner@3795" prio=5 waiting
 java.lang.Thread.State: WAITING
    blocks Instr: android.test.InstrumentationTestRunner@3795
     at java.lang.Object.wait(Object.java:-1)
     at java.lang.Thread.parkFor(Thread.java:1220)
     - locked <0x1069> (a java.lang.Object)
     at sun.misc.Unsafe.park(Unsafe.java:299)
     at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:197)
     at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1014)
     at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1304)
     at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:248)
     at com.couchbase.lite.Database.close(Database.java:1143)
     at com.couchbase.lite.LiteTestCase.stopDatabase(LiteTestCase.java:156)
     at com.couchbase.lite.LiteTestCase.tearDown(LiteTestCase.java:259)
     at junit.framework.TestCase.runBare(TestCase.java:140)
     at com.couchbase.lite.LiteTestCase.runBare(LiteTestCase.java:844)
     at junit.framework.TestResult$1.protect(TestResult.java:115)
     at junit.framework.TestResult.runProtected(TestResult.java:133)
     at junit.framework.TestResult.run(TestResult.java:118)
     at junit.framework.TestCase.run(TestCase.java:124)
     at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:191)
     at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:176)
     at android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:555)
     at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1853)

I think there is a race condition between the following codes:
https://github.com/couchbase/couchbase-lite-java-core/blob/master/src/main/java/com/couchbase/lite/Database.java#L1649-L1654 (activeReplicators doesn't get synchronized)
https://github.com/couchbase/couchbase-lite-java-core/blob/master/src/main/java/com/couchbase/lite/Database.java#L1120-L1138

ReplicationTest each test duration (sec)
Notes:

Test env: Genymotion API 19 (Android 4.4.4)
This is only for forestdb storage (exclude SQLite storage)
ReplicationTest takes around 8-9min for forestdb

09-22 13:19:15.976: testAttachmentsDeletedOnPull: duration=8 sec
09-22 13:19:15.984: testBuildRelativeURLString: duration=0 sec
09-22 13:19:15.992: testBuildRelativeURLStringWithLeadingSlash: duration=0 sec
09-22 13:19:17.520: testChangeTrackerError: duration=1 sec
09-22 13:19:24.064: testChangesFeedWithPurgedDoc: duration=6 sec
09-22 13:19:24.072: testChannels: duration=0 sec
09-22 13:19:25.600: testChannelsFilter: duration=1 sec
09-22 13:19:25.616: testChannelsMore: duration=0 sec
09-22 13:19:34.984: testCheckSessionAndCheckpointWhenRetryingReplication: duration=9 sec
09-22 13:19:36.520: testCheckSessionAtPath: duration=1 sec
09-22 13:19:38.040: testContinuousPullEntersIdleState: duration=1 sec
09-22 13:19:59.600: testContinuousPullReplicationGoesIdleTwice: duration=21 sec
09-22 13:20:31.136: testContinuousPullReplicationSendStoppedOnce: duration=31 sec
09-22 13:20:36.672: testContinuousPushReplicationGoesIdle: duration=5 sec
09-22 13:20:42.280: testContinuousPushReplicationGoesIdleTooSoon: duration=5 sec
09-22 13:20:42.824: testContinuousPushReplicationGoesIdleTwice: duration=0 sec
09-22 13:20:52.172: testContinuousPushRetryBehavior: duration=9 sec
09-22 13:20:53.800: testContinuousReplication404Changes: duration=1 sec
09-22 13:20:53.856: testContinuousReplicationErrorNotification: duration=0 sec
09-22 13:20:53.868: testDifferentCheckpointsFilteredReplication: duration=0 sec
09-22 13:20:54.392: testGetReplicator: duration=0 sec
09-22 13:20:54.408: testGetReplicatorWithAuth: duration=0 sec
09-22 13:20:54.932: testGetReplicatorWithCustomHeader: duration=0 sec
09-22 13:21:10.028: testGoOffline: duration=15 sec
09-22 13:21:23.696: testGoOfflinePusher: duration=13 sec
09-22 13:21:33.824: testGoOnlinePuller: duration=10 sec
09-22 13:21:44.264: testMockContinuousPullCouchDb: duration=10 sec
09-22 13:21:52.836: testMockMultiplePullCouchDb: duration=8 sec
09-22 13:22:01.564: testMockMultiplePullSyncGw: duration=8 sec
09-22 13:22:07.616: testMockPullBulkDocsSyncGw: duration=6 sec
09-22 13:22:19.196: testMockPullerRestart: duration=11 sec
09-22 13:22:25.724: testMockSinglePullCouchDb: duration=6 sec
09-22 13:22:32.492: testMockSinglePullCouchDbAttachments: duration=6 sec
09-22 13:22:39.176: testMockSinglePullSyncGw: duration=6 sec
09-22 13:22:46.044: testMockSinglePullSyncGwAttachments: duration=6 sec
09-22 13:22:51.672: testMockSinglePush: duration=5 sec
09-22 13:22:51.732: testOneShotReplicationErrorNotification: duration=0 sec
09-22 13:23:21.748: testOneTimePullReplicationSendStoppedOnce: duration=30 sec
09-22 13:23:38.296: testPullReplicatonSendIdleStateAfterCheckPoint: duration=16 sec
09-22 13:23:58.568: testPullReplicatonWithManyAttachmentRevisions: duration=20 sec
09-22 13:24:05.448: testPullerWithLiveQuery: duration=6 sec
09-22 13:24:11.972: testPushPurgedDoc: duration=6 sec
09-22 13:24:12.608: testPushReplActiveState: duration=0 sec
09-22 13:24:13.648: testPushReplicationCanMissDocs: duration=1 sec
09-22 13:24:14.228: testPushReplicationNonRecoverableError: duration=0 sec
09-22 13:24:19.820: testPushReplicationRecoverableError: duration=5 sec
09-22 13:25:20.876: testPushUpdatedDocWithoutReSendingAttachments: duration=61 sec
09-22 13:25:25.936: testPusherBatching: duration=5 sec
09-22 13:25:35.960: testPutCheckpoint409Recovery: duration=10 sec
09-22 13:25:52.616: testReplicationOnlineExtraneousChangeTrackers: duration=10 sec
09-22 13:25:52.656: testReplicationRestartPreservesValues: duration=0 sec
09-22 13:25:53.180: testReplicatorErrorStatus: duration=0 sec
09-22 13:26:04.724: testRestartWithStoppedReplicator: duration=11 sec
09-22 13:26:04.740: testRunReplicationWithError: duration=0 sec
09-22 13:26:10.336: testServerDoesNotSupportMultipart: duration=5 sec
09-22 13:26:10.348: testServerIsSyncGatewayVersion: duration=0 sec
09-22 13:26:15.912: testSetFilterParams: duration=5 sec
09-22 13:26:15.932: testSetReplicationCookie: duration=0 sec
09-22 13:26:15.948: testStartReplicationClosedDb: duration=0 sec
09-22 13:26:25.976: testStop: duration=10 sec
09-22 13:26:26.600: testStopReplicatorWhenRetryingReplicationWithPermanentError: duration=0 sec
09-22 13:27:28.140: testValidationBlockCalled: duration=61 sec
09-22 13:27:34.672: testVerifyPullerInsertsDocsWithValidation: duration=6 sec
09-22 13:27:34.680: testAndroidTestCaseSetupProperly: duration=0 sec

@pasin
For item 4, I believe it does not have problem by race condition because of synchronization block with activeReplicators variable. https://github.com/couchbase/couchbase-lite-java-core/blob/master/src/main/java/com/couchbase/lite/Database.java#L1120

Another thing about https://github.com/couchbase/couchbase-lite-java-core/blob/master/src/main/java/com/couchbase/lite/Database.java#L1649-L1654 is that while creating a countdown latch for each active replicator, the replicator might already be in the stopped state so the count down latch will never be down.

I assume this is more higher possibility for the problem.

After applied https://github.com/couchbase/couchbase-lite-java-core/commit/45a83b950afc7e476af50ec48b5d2f4e3d76bf8d for item 4.  During the iteration at https://github.com/couchbase/couchbase-lite-java-core/blob/master/src/main/java/com/couchbase/lite/Database.java#L1120-L1138 , item should not be removed.
this.activeReplicators = Collections.synchronizedSet(new HashSet());

https://github.com/couchbase/couchbase-lite-java-core/blob/master/src/main/java/com/couchbase/lite/Database.java#L141

Hi @hideki,
I don't think Collections.synchronizedSet(new HashSet()); would completely guard for this case that there is an iterating action over the activeReplicators on https://github.com/couchbase/couchbase-lite-java-core/blob/master/src/main/java/com/couchbase/lite/Database.java#L1121.
For example,

The for loop in line 1121 is executed.
At the same time, line 1653 get executed by another thread.  I believe this could happen even though the activeReplicators is a synchronized set and this could cause a race condition or even exception as altering the list while iterating.

@hideki , you are right. the activeReplicators itself is synchronized along with the synchronized block as the synchronized block is sync with the activeReplicators. I have looked into the Collections.synchronizedSet() source code and it does synchronized block with this internally. So please ignore my comment.

With standard emulator with arm API 19 (Android 4.4.4), it takes Total time: 17 mins 51.586 secs for running SQLite and ForestDB.

Genymotion API 19 (Android 4.4.4)
SQLite: Tests that take more than 5 sec
09-23 15:51:42.788: DURATION: testOneTimePullReplicationSendStoppedOnce: 15sec - [SLOW]
09-23 15:51:59.364: DURATION: testPullReplicatonSendIdleStateAfterCheckPoint: 16sec - [SLOW]
09-23 15:52:10.004: DURATION: testPullReplicatonWithManyAttachmentRevisions: 10sec - [SLOW]
09-23 15:52:19.200: DURATION: testPushPurgedDoc: 6sec - [SLOW]
09-23 15:52:31.584: DURATION: testPutCheckpoint409Recovery: 8sec - [SLOW]
09-23 15:52:47.040: DURATION: testStop: 6sec - [SLOW]

ForestDB: Tests that take more than 5 sec
09-23 16:00:39.999: DURATION: testClose: 15sec - [SLOW]
09-23 16:01:03.107: DURATION: testChangeTrackerBackoffExceptions: 10sec - [SLOW]
09-23 16:01:13.127: DURATION: testChangeTrackerBackoffInvalidJson: 10sec - [SLOW]
09-23 16:01:19.615: DURATION: testExcessiveCheckpointingDuringPushReplication: 5sec - [SLOW]
09-23 16:01:30.107: DURATION: testAttachmentsDeletedOnPull: 8sec - [SLOW]
09-23 16:01:44.143: DURATION: testCheckSessionAndCheckpointWhenRetryingReplication: 9sec - [SLOW]
09-23 16:02:03.779: DURATION: testContinuousPullReplicationGoesIdleTwice: 16sec - [SLOW]
09-23 16:02:20.319: DURATION: testContinuousPullReplicationSendStoppedOnce: 16sec - [SLOW]
09-23 16:02:31.903: DURATION: testContinuousPushRetryBehavior: 9sec - [SLOW]
09-23 16:02:42.811: DURATION: testGoOffline: 8sec - [SLOW]
09-23 16:02:56.595: DURATION: testGoOfflinePusher: 13sec - [SLOW]
09-23 16:03:04.827: DURATION: testGoOnlinePuller: 8sec - [SLOW]
09-23 16:03:42.863: DURATION: testOneTimePullReplicationSendStoppedOnce: 15sec - [SLOW]
09-23 16:03:59.411: DURATION: testPullReplicatonSendIdleStateAfterCheckPoint: 16sec - [SLOW]
09-23 16:04:09.727: DURATION: testPullReplicatonWithManyAttachmentRevisions: 10sec - [SLOW]
09-23 16:04:18.563: DURATION: testPushPurgedDoc: 6sec - [SLOW]
09-23 16:04:30.731: DURATION: testPutCheckpoint409Recovery: 8sec - [SLOW]
09-23 16:04:45.803: DURATION: testStop: 6sec - [SLOW]


Mozilla: Naming conventions for vectorized modules (_Vec256 vs _256)

I am fine with anything, but we should decide on which to use.
        'verified/Hacl_Chacha20_Vec256.c',
        'verified/Hacl_Chacha20Poly1305_256.c',
        'verified/Hacl_Poly1305_256.c',

Yeah. Shall we standardize on Scalar32 and Vec128/256?
On Wed, Feb 12, 2020, 18:06 Benjamin Beurdouche<EMAIL_ADDRESS>wrote:

I am fine with anything, but we should decide on which to use.
    'verified/Hacl_Chacha20_Vec256.c',
    'verified/Hacl_Chacha20Poly1305_256.c',
    'verified/Hacl_Poly1305_256.c',

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/project-everest/hacl-star/issues/234?email_source=notifications&email_token=ABFUVSY5TGXHL7AFGMP6VR3RCPUMZA5CNFSM4KTY6PM2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IM5Q3RQ,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABFUVS52XADWGXTYYKOCRZDRCPUMZANCNFSM4KTY6PMQ
.

👍

Subsumed by #675


Could not compile openpoints with cuda11.3

Hi, I could create the openpoints environment using source install.sh, but I could not compile openpoints with cuda11.3 now. The bugs are the following. Could you please help me out?
/cm/shared/apps/cuda11.3/toolkit/11.3.0/include/crt/host_config.h:139:2: error: #error -- unsupported GNU version! gcc versions later than 10 are not supported! The nvcc flag '-allow-unsupported-compiler' can be used to override this version check; however, using an unsupported host compiler may cause compilation failure or incorrect run time execution. Use at your own risk.
139 | #error -- unsupported GNU version! gcc versions later than 10 are not supported! The nvcc flag '-allow-unsupported-compiler' can be used to override this version check; however, using an unsupported host compiler may cause compilation failure or incorrect run time execution. Use at your own risk.
|  ^~~~~
ninja: build stopped: subcommand failed.
Traceback (most recent call last):
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 1723, in _run_ninja_build
env=env)
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/subprocess.py", line 512, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['ninja', '-v']' returned non-zero exit status 1.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "setup.py", line 26, in
'build_ext': BuildExtension
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/site-packages/setuptools/init.py", line 153, in setup
return distutils.core.setup(**attrs)
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/distutils/core.py", line 148, in setup
dist.run_commands()
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/distutils/dist.py", line 966, in run_commands
self.run_command(cmd)
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/site-packages/setuptools/command/install.py", line 74, in run
self.do_egg_install()
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/site-packages/setuptools/command/install.py", line 116, in do_egg_install
self.run_command('bdist_egg')
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/site-packages/setuptools/command/bdist_egg.py", line 164, in run
cmd = self.call_command('install_lib', warn_dir=0)
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/site-packages/setuptools/command/bdist_egg.py", line 150, in call_command
self.run_command(cmdname)
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/site-packages/setuptools/command/install_lib.py", line 11, in run
self.build()
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/distutils/command/install_lib.py", line 107, in build
self.run_command('build_ext')
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/site-packages/setuptools/command/build_ext.py", line 79, in run
_build_ext.run(self)
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/site-packages/Cython/Distutils/old_build_ext.py", line 186, in run
_build_ext.build_ext.run(self)
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/distutils/command/build_ext.py", line 340, in run
self.build_extensions()
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 735, in build_extensions
build_ext.build_extensions(self)
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/site-packages/Cython/Distutils/old_build_ext.py", line 195, in build_extensions
_build_ext.build_ext.build_extensions(self)
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/distutils/command/build_ext.py", line 449, in build_extensions
self._build_extensions_serial()
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/distutils/command/build_ext.py", line 474, in _build_extensions_serial
self.build_extension(ext)
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/site-packages/setuptools/command/build_ext.py", line 202, in build_extension
_build_ext.build_extension(self, ext)
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/distutils/command/build_ext.py", line 534, in build_extension
depends=ext.depends)
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 565, in unix_wrap_ninja_compile
with_cuda=with_cuda)
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 1404, in _write_ninja_file_and_compile_objects
error_prefix='Error compiling objects for extension')
File "/export/home2/hanxiaobing/anaconda3/envs/openpoints/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 1733, in _run_ninja_build
raise RuntimeError(message) from e
RuntimeError: Error compiling objects for extension

error said:  error: #error -- unsupported GNU version! gcc versions later than 10 are not supported!
please downsample GCC

Commenting a couple of lines as mentioned in the below link can support gcc > 10. It worked for me with gcc 11.
https://github.com/NVIDIA/nccl/issues/650#issuecomment-1145173577


docs: fix Experimental Features page not loading completely

Fix Experimental Features page not loading completely due to ReadMore sections that were not closed.

🔗 Linked issue
#22540
❓ Type of change

[x] 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
Fix the ReadMore syntax on the Experimental Features page to match other uses of ReadMore like in this example on the State Management page.
📝 Checklist

[x] I have linked an issue or discussion.
[x] I have updated the documentation accordingly.

I was unable to reproduce this issue locally, but the ReadMore syntax on this particular page did not match other uses, so for now I am thinking that was causing the issue with the page not loading completely.
I cloned the Nuxt repo, ran pnpm install, pnpm build, and pnpm docs:dev. The docs load locally, but the issue is not present, and the docs also look pretty different in style compared to what is live at https://nuxt.com/docs at the moment. I am not sure if I missed a step (I could not find clear documentation on running the docs site locally) or if there are larger changes in flux with the docs (I did see https://github.com/nuxt/nuxt/pull/22469).
local docs dev

nuxt.com/docs

Thank you for spotting and fixing this! ❤


Implement anonymous shapes

Add a std::VirtualObject singleton object, similar to
stdgraphql::Query, and make SELECT { foo := expr, ... } implicity
operate on a detached VirtualObject.
For annoying LR(1) reasons, we don't support link properties in
anonymous shapes, but that doesn't seem like a big problem.
Elvis suggested removing stdgraphql::Query/Mutation, but I'm holding
off on that in this version because those have an extra __typename
field that would require some handling and I didn't want to muck
around with the graphql compiler in this version. (I tried making
them aliases but trying to create aliases in std library modules
triggers errors about them being read-only.)
Fixes #2533.

@vpetrovykh

Elvis suggested removing stdgraphql::Query/Mutation

Victor, once this PR is in, please implement the changes in the GraphQL backend.

Victor, once this PR is in, please implement the changes in the GraphQL backend.

If we think that using aliases is the right thing, I can fix the stuff that causes aliases to not work in the standard library, but it might just be best to have the graphql compiler use std::VirtualObject directly?

After a bunch of offline discussion, we agreed on sticking with this approach for now, but banning DISTINCT on virtual objects.
While I was at it, I also banned different variants of equality, but I can drop those bans if people prefer.

Impl lgtm, please add documentation.

I'm going to merge as is and do docs in a follow up so that I can get the parser changes committed and not need to rebuild grammars as I switch branches


release/3.1.x

Changelog
v3.1.0
🚀 Features:

Legacy: Sunsetting Libcore 🎉 💥 @gre #2329
Ethereum: Add support for Goerli @hzheng-ledger #2349
Testing: Add a POC w/ Detox 🧑🔬 @ggilchrist-ledger #2211 // Reverted @valpinkman https://github.com/LedgerHQ/ledger-live-mobile/commit/f72d9619794e4890488d8b111778da459e9001d0 // Reimplemented @valpinkman @ggilchrist-ledger #2484
WalletConnect: Adding Polygon & BSC to supported chains @nparigi-ledger #2473 #2443
UI: Add a stake button to TRON, TEZOS, COSMOS and DOT accounts @nparigi-ledger #2459
UI: Polishing portfolio page v3 (Graphs are back! 📈) @LFBarreto #2455
NFT: New architecture and activation of Polygon NFTs @lambertkevin #2363
NFT: Add hidding collection feature to remove scams @grsoares21 @lambertkevin #2452
UI: Update terms of use popup @thomasrogerlux #2442
Devices: Add FTS support @juan-cortes #2429
Language: Add Spanish and Chinese to fully supported languages @ofreyssinet-ledger #2440

🐛 Bufixes:

UI: Fixing settings row being difficult to click on @nparigi-ledger #2445
UI: Polishing welcome screen with video @nparigi-ledger #2454
Platform: Reenabling navigation to Lido @ofreyssinet-ledger #2457
Scripting: Fixing families generator @nparigi-ledger #2456
Manager: Allow name edition only for Nano X @alexandremgo #2404
UI: Fixing user still seing empty subaccounts with the option activated @nparigi-ledger #2467
UI: Set default timeframe to months instead of days @nparigi-ledger #2453
UI: Fix strategy fee checkbox not tappable @nparigi-ledger #2468
UI: Fix hide token modal design @nparigi-ledger #2471
UI: Fix warning icon size in the onboarding @ofreyssinet-ledger #2465
UI: Address not in upercase anymore to respect EIP55 @ofreyssinet-ledger #2472
UI: Add padding to bottom modals @nparigi-ledger #2474
UI: Fixing QR code scanning info panel @nparigi-ledger #2479
UI: Use discrete mode on market page @nparigi-ledger #2478
Navigation: Fixing navigation in operation details @nparigi-ledger #2482
UI: Upgrading carousels from v2 to v3 in recommended section @ofreyssinet-ledger #2480
UI: Prevent being stuck in read only mode during the onboarding @LFBarreto #2469
UI: Fixing graphs hovering on zero values @LFBarreto #2489
NFT: Fixing crash when entering the account settings without any hidden collections @LFBarreto #2490
UI: Removed curriencies without settings from Crypto Assets settings @ofreyssinet-ledger #2494
UI: Fix redirection when deleting an account @cgrellard-ledger #2493
UI: Fixing graphs getting out of bound due to too big delta between min and max in Y axis @LFBarreto #2495

🧱 Support:

Network: Add HTTP user-agent to network calls @hzheng-ledger #2371
Cleanup: Removing JS files + Linting @LFBarreto #2450
Cleanup: Update Podlock checksum @Justkant #2458
Logs: Restrictions of errors sent to Sentry & upgrade to latest lib @gre #2447
Documentation: Update readme to add more pre-requisites @ofreyssinet-ledger #2461
Documentation: Adding onboarding guide for Linux @nparigi-ledger #2466
Language: Add first batch of Crowdin updates #2444

🔗 Dependencies:

Updating @LedgerHQ/native-ui to 0.7.16 @ofreyssinet-ledger #2475
Upgrade to @LedgerHQ/live-common 22.1.0 @lambertkevin https://github.com/LedgerHQ/ledger-live-mobile/pull/2486/commits/2b7cb988afc8ae3a38ec2562b6fa8e3468efd1c3
Cleanup: Fixing flow errors @valpinkman https://github.com/LedgerHQ/ledger-live-mobile/commit/0ea574f60741ba8be0c18c37beb9a74cfdb05f2d || Reverted and fixed @LFBarreto https://github.com/LedgerHQ/ledger-live-mobile/commit/fe44b76ceef60f83b3f3674240de7e07165c5ffd

⚠ Dependabots:

Bump urijs from 1.19.10 to 1.19.11 #2426
Bump plist from 3.0.4 to 3.0.5 #2421
Bump moment from 2.29.1 to 2.29.2 #2410
Bump minimist from 1.2.5 to 1.2.6 #2411

Changelog
v3.1.0
🚀 Features:

Legacy: Sunsetting Libcore 🎉 💥 @gre #2329
Ethereum: Add support for Goerli @hzheng-ledger #2349
Testing: Add a POC w/ Detox 🧑🔬 @ggilchrist-ledger #2211 // Reverted @valpinkman #2211 // Reimplemented @valpinkman @ggilchrist-ledger #2484
WalletConnect: Adding Polygon & BSC to supported chains @nparigi-ledger #2473 #2443
UI: Add a stake button to TRON, TEZOS, COSMOS and DOT accounts @nparigi-ledger #2459
UI: Polishing portfolio page v3 (Graphs are back! 📈) @LFBarreto #2455
NFT: New architecture and activation of Polygon NFTs @lambertkevin #2363
NFT: Add hidding collection feature to remove scams @grsoares21 @lambertkevin #2452
UI: Update terms of use popup @thomasrogerlux #2442
Devices: Add FTS support @juan-cortes #2429
Language: Add Spanish and Chinese to fully supported languages @ofreyssinet-ledger #2440

🐛 Bufixes:

UI: Fixing settings row being difficult to click on @nparigi-ledger #2445
UI: Polishing welcome screen with video @nparigi-ledger #2454
Platform: Reenabling navigation to Lido @ofreyssinet-ledger #2457
Scripting: Fixing families generator @nparigi-ledger #2456
Manager: Allow name edition only for Nano X @alexandremgo #2404
UI: Fixing user still seing empty subaccounts with the option activated @nparigi-ledger #2467
UI: Set default timeframe to months instead of days @nparigi-ledger #2453
UI: Fix strategy fee checkbox not tappable @nparigi-ledger #2468
UI: Fix hide token modal design @nparigi-ledger #2471
UI: Fix warning icon size in the onboarding @ofreyssinet-ledger #2465
UI: Address not in upercase anymore to respect EIP55 @ofreyssinet-ledger #2472
UI: Add padding to bottom modals @nparigi-ledger #2474
UI: Fixing QR code scanning info panel @nparigi-ledger #2479
UI: Use discrete mode on market page @nparigi-ledger #2478
Navigation: Fixing navigation in operation details @nparigi-ledger #2482
UI: Upgrading carousels from v2 to v3 in recommended section @ofreyssinet-ledger #2480
UI: Prevent being stuck in read only mode during the onboarding @LFBarreto #2469

🧱 Support:

Network: Add HTTP user-agent to network calls @hzheng-ledger #2371
Cleanup: Removing JS files + Linting @LFBarreto #2450
Cleanup: Update Podlock checksum @Justkant #2458
Logs: Restrictions of errors sent to Sentry & upgrade to latest lib @gre #2447
Documentation: Update readme to add more pre-requisites @ofreyssinet-ledger #2461
Documentation: Adding onboarding guide for Linux @nparigi-ledger #2466
Language: Add first batch of Crowdin updates #2444

🔗 Dependencies:

Updating @LedgerHQ/native-ui to 0.7.16 @ofreyssinet-ledger #2475

⚠ Dependabots:

Bump urijs from 1.19.10 to 1.19.11 #2426
Bump plist from 3.0.4 to 3.0.5 #2421
Bump moment from 2.29.1 to 2.29.2 #2410
Bump minimist from 1.2.5 to 1.2.6 #2411

Changelog
v3.41.0-rc1
🐛 Bugfixes:

UI: Fixing graphs hovering on zero values @LFBarreto #2489
NFT: Fixing crash when entering the account settings without any hidden collections @lambertkevin #2490
UI: Removed curriencies without settings from Crypto Assets settings @ofreyssinet-ledger #2494
UI: Fix redirection when deleting an account @cgrellard-ledger #2493
UI: Fixing graphs getting out of bound due to too big delta between min and max in Y axis @LFBarreto #2495

🧱 Support:

Cleanup: Fixing flow errors @valpinkman https://github.com/LedgerHQ/ledger-live-mobile/commit/0ea574f60741ba8be0c18c37beb9a74cfdb05f2d || Reverted and fixed @LFBarreto https://github.com/LedgerHQ/ledger-live-mobile/commit/fe44b76ceef60f83b3f3674240de7e07165c5ffd

Changelog
v3.1.0-rc2
🐛 Bugfixes:

Onboarding: Fixing crash on Chrome OS (Chromebook device) due to react-native-video @gre #2470
UI: Fixing discreet mode not applied to transaction history on wallet screen @ofreyssinet-ledger #2498
UI: Fixing NFT screen titles that were using background from the old branding @nparigi-ledger #2496

🧱 Support:

Language: Latest batch of Crowdin updates #2488


Using HSM for device attestation certificate

Problem
HSM (NXP Se05x) specific device attestation creds provider file has device attestation certificate used from file system. This should be changed to using certificate from HSM.
Change overview

HSM (NXP Se05x) specific device attestation creds provider file is updated to use the device certificate from HSM.
Also the NXP Se05x submodule (simw-top) is updated. The updates contain support for additional secure element family of NXP.

Testing
Tested using lighting app example.

Can this PR be merged please ?

Can this PR be merged please ?


0.8.0 RC-7 (Request for Comments)

The latest Request for Comments is 7.  THIS IS THE LATEST RC.
This issue is for reporting issues with this specific version of MeerK40t.
Please do all further testing on this release. Please do not report any further bugs with previous beta releases. Do give any other types of feedback, questions, concerns or comments.

Previous Issue: https://github.com/meerk40t/meerk40t/issues/1065
RC-3 Issues:

[ ] GAG-Union can cause long infinite looped pause.
[ ] People want to fiddle with the write buffer thinking it will fix buffer underruns. This might be better off being suppressed as a feature.
[ ] Property window doesn't do multiple item manipulations rather adds more things to the notebook. (still true, but stroke/fill/stroke width can be circumvented by using the tools in the statusbar)

RC-4
FPS.

[ ] Preferences is “gone” mac style in the 0.8.0005 frozen build. No longer in the menu or working with “Apple-,” keyboard command.

RC-5
Flow test ideas.

[ ] If flow text pointer exceeds data then the current run-batch is degenerate. This should issue a warning during plotplanning.

RC-5 Addenda

[ ] estop over tcp does not work (clarification: estop works. Recovery from estop is a disaster)

RC-6
ot respected.

[ ] GRBL driver failed to shutdown correctly, weirdly insists on sending buffered data in error.
[ ] Forced close of update_status for lhystudioscontrollergui constantly tries to update byte_0 when things have already been killed.

Additional comments provided in Discord

[ ] Ruidacontrol needs to respect (receive) EOF before starting the received job.
[ ] Rasters at even 100mm/s are problematic. 200mm/s seems unusable.
[ ] balor image is running for a very long time on a 5mm x 5mm image; setting step to 1,000 doesn’t seem to change that run time.
[ ] Inkscape to make an inset to be able to use on a specific path for that reason (to be able to respect the path as a cut).
[ ] console Operation frequency xxx is not a valid command
[ ] ez cad shows an elapsed time for the last "execution" in the status bar at the bottom of the window, which is extremely helpful in tuning a job for cutting as fast as possible for example.
[ ]  The galvo light (on with any setting) and no galvo buttons will turn on the red laser and leave it on. But not in the same way console red on does….
[ ]  Red light in ez cad has a unique scale value not shown in balor-configuration

No executable assets as yet.

Discussion continued in https://github.com/meerk40t/meerk40t/issues/1224


Namespace dirs imports

Clear and concise description of the problem
Namespace all imports from a directory. Instead of using foo(), use api.foo() to import functions.
Why -

Avoid name collisions
Tree shaking

Suggested solution

Config:

dirs: [
  'src/logic/composables',
  ['api', 'src/logic/requests']
]

src/logic/requests/index.ts

export function fetchBlogs() {}
export function fetchProducts() {}

Then in project files:

api.fetchBlogs()
api.fetchProducts()

Under the hood:
export function fetchBlogs() {}
export function fetchProducts() {}

import { fetchBlogs as api_fetchBlogs, fetchProducts as api_fetchProducts } from '...'

api_fetchBlogs()
api_fetchProducts()

Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

you can try this:
config:
dirs: [ 'src/apis/']

src/apis/index.ts:
import * as api from "...";
export { api };

auto-imports.d.ts:
// Generated by 'unplugin-auto-import'
export {}
declare global {
  const api: typeof import('./src/apis/index')['api']
}


chore(package): update source-map-support to 0.4.x

Now, The package source-map-support is out of date.
The 0.3.x version has some problem with sourceMap path. And If some one use source-map-support in they own project(which must be the latest version), so The source-map-support will load twice, which may lead to some weird bug.

@shepherdwind Thank you for your contribution again.
I'll release this too.

espower-loader 1.2.1 is out. Thanks!


"Go To Definition" unnecessarily shows import definition when using jsconfig.json

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.62.1
OS Version: Windows 11 Home (21H2)

Steps to Reproduce:

Clone this minimal example
Open file /src/pages/test.jsx
Focus the jsx-tag <HelloWorlder />
Invoke "Go To Definition" (Ctrl+Click / via context menu / F12)
The focus jumps to the import statement in line 2

This behavior might be correct, but highly useless. This way, you have to always manually focus the imported filename and invoke the command again in order to open the corresponding file.
Also, this behavior does not occur when deleting the jsconfig.json file.

Does this reproduce in the latest VS Code insiders build?

Yes, it does in 1.63.0-insider (commit 035eaab). As far as I can distinguish, this problem seems to be limited to JSX-Code, though.


Improve checkpointer docs and testing

First commits improves KV Store-based checkpointer's documentation and second commit rewrites all the tests for both KV Store and file based checkpointers.

Codecov Report

Merging #122 (001b022) into main (07221e7) will increase coverage by 0.62%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #122      +/-   ##
==========================================
+ Coverage   88.39%   89.02%   +0.62%
==========================================
  Files          23       23
  Lines        1827     1831       +4
==========================================
+ Hits         1615     1630      +15
+ Misses        212      201      -11

Impacted Files
Coverage Δ

solnlib/modular_input/checkpointer.py
100.00% <100.00%> (+13.48%)
:arrow_up:

solnlib/file_monitor.py
89.47% <0.00%> (-1.76%)
:arrow_down:

Continue to review full report at Codecov.

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

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

v4.4.1
GitHub release

Your semantic-release bot :package::rocket:


If index 3 is not a list, assume Redis Enterprise and return index 4 as slowlog command

Pull Request check-list
Please make sure to review and check all of these items:

[ ] Does $ tox pass with this change (including linting)?
[ ] Does travis tests pass with this change (enable it first in your forked repo and wait for the travis build to finish)?
[ ] Is the new or changed code fully tested?
[ ] Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?

NOTE: these things are not required to open a PR and can be done
afterwards / while the PR is open.
Description of change
Some redis instances, Redislabs for example, return slowlog entries with the commands at item[4] instead of item[3].
command is always a list; return item[4] if item[3] is not a list.
 I'm not sure what extra entires (if any) Redis Labs returns, but this change won't work for the open source version.

Hi @ian28223,
Thank you for bringing this up.
It seems Redis Enterprise injects another entry at index [3], which has the complexity info (i.e. the value of N in case the command has an O(N) complexity).
Whatever the schema of this response is, we need it to be standardized and documented in order to introduce it to redis-py, otherwise it might change it a way we can't predict.
I'll reach out to the relevant developers in Redislabs, to get the Redis Enterprise slowlog get schema standardized and documented, but this is outside the scope of redis-py.
For now, I'm creating a new issue to support the Client IP address and port and Client name added in v4 of Redis OSS
https://github.com/andymccurdy/redis-py/issues/1374.

I think the right way to work around this incompatibility of RE (until it gets fixed), is to look at the entry at [3] and see if it's an array or a string.
The command arguments will always be a multi-bulk, so if we see that [3] is an array, we can assume this is the OSS redis format, and if we see [3] is a string, we can assume that's RE complexity field, and shift all the fields forward by one, i.e. the command is at [4], and the client details at [5] and [6] (instead of [4], [5] like in OSS redis)

@oranagra

I think the right way to work around this incompatibility of RE (until it gets fixed), is to look at the entry at [3] and see if it's an array or a string.

I think in case of Redis Enterprise the field is an int as @ RoeyPrat said

It seems Redis Enterprise injects another entry at index [3], which has the complexity info (i.e. the value of N in case the command has an O(N) complexity).

In either case checking if it's a string might still be the solution

by [3] i meant 0 based. the output posted above is from redis-cli which is 1 based.
in that example the field is empty, but had this response been from standard redis, it would have been the arguments array.

I've applied the suggestion which is to return index 4 as the command if index 3 is not a list.

Seems the build has failed due to a pull limit. Is there a way to rerun it?

@ian28223 Nit-picky, but can you fix the flake8 error please? Looks like the line is too long now.

The error that Travis is reporting doesn't seem related to this PR. It looks like a test case that mixes mocks and threading is failing on PyPy3 suddenly. Not sure why off the top of my head, but I'll look into it this afternoon.

Codecov Report

Merging #1352 (ba4ad9f) into master (15dafb1) will increase coverage by 0.68%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #1352      +/-   ##
==========================================
+ Coverage   85.90%   86.58%   +0.68%
==========================================
  Files           6        7       +1
  Lines        2894     2914      +20
==========================================
+ Hits         2486     2523      +37
+ Misses        408      391      -17

Impacted Files
Coverage Δ

redis/client.py
87.02% <100.00%> (+1.09%)
:arrow_up:

redis/lock.py
100.00% <0.00%> (ø)

redis/__init__.py
83.33% <0.00%> (ø)

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 7e466f7...ba4ad9f. Read the comment docs.

Seems builds are green now. Can we get this in?

@ian28223 Can you rebase your PR off of the latest master? Thanks.

Seems an unrelated test is failing after rebasing?

I haven't tracked down the PyPy error yet, but it's definitely not related to this change. Thanks for putting this together.

I haven't tracked down the PyPy error yet, but it's definitely not related to this change. Thanks for putting this together.

Much appreciated for the merge! Any chance we can get a new release including it? A 3.5.4 perchance?

When is next release planed? It's been a year since the latest


[Support Powertools for AWS Lambda (Java)]: Europace AG

Organization Name
Europace AG
Your Name
Alexander Sparkowsky
Your current position
Tech Lead
(Optional) Company logo
No response
(Optional) Use case
We are using various packages of the Powertools for AWS Lambda (Java) to speed up our development.
Most helpful are the parameters, idempotency and observability packages.
Also using other Powertools for AWS Lambda (Java) languages?

[ ] Python
[ ] TypeScript
[ ] .NET

Thank you very much @roamingthings for your support. We'll update the README to mention this.
Let us know if you would need additional features or improvements. We're working on the v2 definition right now, so it's a good time to share your thoughts ;)

Thanks again, you can now see reference customers in the readme.


Move device log to after Logging is configured

This should fix the repeated prints in the distributed log.

bors r+

bors r+


Create boaty-Hype-Man Plugin

Plugin is similar to CEngineers' completed plugin that plays certain sounds when different actions happen ingame but with the sounds being audio clips from the streamer/youtuber B0aty with the following proccing an audio file

Level ups
Quests completed
Max hits
When you login to the game
When you hit a ruby bolt spec
Get a drop above a value specified in Ground items
Get a combat task
Collection log or get a Pet

Do you have permission from b0aty to use his voice clips for this plugin?

Yes
https://clips.twitch.tv/OilyTardySageBrokeBack-lALYoBKA5NOweOoI

Code LGTM, but you need to give proper attribution to the C Engineer plugin, as most of your code is straight-up copied from it. Please read the license terms and make the appropriate changes

Updated to include reference and thanks to the C Engineer Completed plugin


Find and replace - Allow to swap the two strings easily

Currently, using the text entered in the Find field as the replace string and vice versa requires you to copy/overwrite both of them manually.
For instance, if you were replacing "Lorem" with "Ipsum" before and you want to replace "Ipsum" with "Lorem" again now, you have to

cut "Lorem" from the Find field
cut "Ipsum" from the Replace field
paste "Ipsum" into the Find field
paste "Lorem" into the Replace field

By adding a button Swap find and replace next to the existing ones for Previous Match, Next Match, Find in selection and Close, this task could be facilitated.

Huge +1 for this. I often need to do a quick F+R to replace a remote URL with localhost for testing and then flip it back.

@rebornix Could you please add the ID of the issue this one is a duplicate one to the comments?
After a quick search, I only found #121010, but this is definitely a different one according to the author:
"(Not to be confused with another proposal which proposed a way to swap the contents of the find&replace fields)"

#59652

@yume-chan Thanks.
Pity that this won't be implemented anytime soon, this would still be very helpful.


Bump spring boot starter 2.7.2

Bump spring boot starter 2.7.2, lose up circular dependencies, remove WebSecurityConfigurerAdapter.
I've made an initial attempt to upgrade spring boot starter, partly because this is required to complete PR #69.
Tests are passing with mvn test -Dtest=\!TestAppRecovery,\!TestIntegrationOnKube.

Hi @janhh
Thanks for the effort, really appreciated! Upgrading Spring Boot is always a bit tricky, but it appears you already have fixed quite some stuff.
There might be a less verbose way to fix the circular dependencies, e.g. such as here: https://github.com/openanalytics/containerproxy/blob/master/src/main/java/eu/openanalytics/containerproxy/auth/impl/KeycloakAuthenticationBackend.java#L97
Currently we are still developing a few new features for the next release, once I have some time, I'll merge your PR and perform some extensive testing we have to do. I'll of course merge your other PRs regarding PKCE as well.

Thank you, @LEDfan .
It might work with the @Lazy annotation. I did an early but not so successful attempt with @Lazy first. But maybe the explicit approach can make it a little easier to see where the circular dependencies appear if there will a design change later.
The changes I did in WebSecurityConfig took me a bit guesswork, so I think it'll be good if that class gets carefully reviewed by someone else in particular.
I rebased #68 and #69 on top of #74 successfully and it appears to be working fine with ShinyProxy 2.6.1. I am changing this draft to a pull request. 👍

Thanks, Spring has been upgrade to 2.7.4 in ShinyProxy 3.0.0!


feat: port CategoryTheory.DifferentialObject

todo:

[x] hasZeroMorphisms tactic 'aesop' failed, failed to prove the goal after exhaustive search
[x] Hom.comm defLemma linter
[x] DifferentialObject.d_squared defLemma linter

bors d+

bors merge


Cannot read property 'composing' of undefined

Vue.js version
2.0.alpha-8 / 7
Reproduction Link

http://forum.vuejs.org/topic/4353/the-correct-way-to-use-twoway-directive-in-vue-2-0/3
Steps to reproduce
Use the provided example
What is Expected?
Update of value on the vm
What is actually happening?
In genDefaultModel, code is set to a string $event.target.composing.  During the function call, $event has no target property.  Changing that line to ( "$event.hasOwnproperty('target') && $event.target.composing) allows it to continue, but then fails with cannot read property 'value' of undefined.

Are you referring to Select 2 example ? Please check Evan comment here https://github.com/vuejs/vue/issues/3179#issuecomment-229410710
As you can see, the syntax has changed a little bit, so select 2 example is up to date but $emit update  will be shipped in next alpha-9 release

Yep. The select example is alread updated to reflect the latest changes in the next branch, and in this case it's a breaking change for alpha-8 previous versions, as outlined in the comment that @sqal linked to.
If you clone the repo locally and check out the next branch, the example works as intended.
I will close this issue as this is not a bug.


Enable "Copying of local resources" to LSSD

Description
The LSSD (Landscape Setup Dependencies) at the moment does not support the copying of local resources. This needs to be added.

DONE added function to cc-utils to copy an oci artifact with its blobs
PR OPEN use this function to replace the previous copying mechanism
IN PROGRESS also copy resources with access.type OciRegistry (currently, only resource.type oci image is copied)


added a public Direction facing() method in Pos.java

Hello, this is my first pull request here ! This can be useful for WorldEdit-like stuff

Specific ranges for yaw and pitch are unnecessary, you should be able to have 1000 yaw, as a solution, you can mod the yaw/pitch where needed.

But clients don't even support more than 90 / less than -90 pitch ? As for the yaw, I saw it is automatically "fixed" to be between -180 and 180

Making already existing code break because of that is an issue though, we can mod the yaw if the client complains, but I think it's not a great idea to enforce that on the Dev.

Well I think the range annotation can stay since the pitch range is standard, anything outside -90 and 90 doesn't make sense, but the client accepts values outside it so the runtime check should be gone. I have the same opinion for the yaw, it shouldn't be force fixed but at this point removing it would be a hidden breaking change.

Yes, I didn't touch to the yaw, I think it is good like this, for example for things like incrementing the yaw a little at each tick to make a player rotate, it would be annoying having to manually fix the yaw. As for the pitch, I don't see any use for it being less than -90 or more than 90... But I can remove that check throwing an exception if needed

ok, I removed the range annotation as long as ```java
if (pitch < -90 || pitch > 90) throw new IllegalArgumentException("Pitch must be between -90 and 90");


Mean identity calculated as more than 100%

I'm seeing several cases where mean identity is calculated as over 100%. For example:
Yield [Gb]	39.86
Mean coverage	12.86
N50	21602
Median length	1600.00
Mean length	5308
Median identity	97.98
Mean identity	103.01

I wouldn't expect this to be possible, correct?

I agree that shouldn't be possible. Which aligner was used, and which version? Cramino uses the de tag from minimap2, if available.

Minimap2, 2.17-r941.

Most likely a known bug then: https://github.com/lh3/minimap2/releases/tag/v2.18

Ah, good catch. I'm super excited to re-align my data with a new version. :)

Since I was also using v2.17 alignments I dismissed similar results I saw in my tests, but there was something more going on which is now solved by using f64s rather than f32s for the read identity. Version 0.9.4 has this fix, and I'll make a new release soon.


Exchange issuance zero ex

Pull Request Template
Type of Change

[ ] Bug Fix
[ ] Content
[x] New Feature
[ ] Documentation
[ ] Code Refactoring

Summary of Changes
Integrate the new Exchange Issuance Contract based on the 0xAPI into the frontend:

Extend the buy / sell widget for index products to allow switching between token swap (current buy / sell implementation) and exchange issuance. (The latter only being available on mainnet)

Add logic to retrieve all the necessary "quotes" from the 0x api for exchange issuance (one for each index component)

Add logic to forward the 0x quotes as well as the user inputs to the Exchange Issuance smart contract

Fixes: Issue #

Test Data or Screenshots
Include proof that your changes function properly and resolve the linked issue.

Submission Reminders
By submitting this pull request, you are confirming the following to be true:

I have reviewed the Contribution Guidelines.
I have performed a self-review of my own code.
I have updated my repository to match the master at SetProtocol/index-ui.
I have included test data or screenshots that prove my fix is effective or that my feature works.

Replaced by: https://github.com/IndexCoop/index-coop-smart-contracts/pull/85


Folder organisation (front)

In this project, it's normally to have modules right inside you src/ folder
But in larger projects better to use something like project structure:
src/
App.jsx
yarn.lock
package.json
...
modules/
components/ <-- common components
connected/
disconnected/
helpers/
mockData/

"But in larger projects better to use something like project structure:" should be the point here. Go take a look at my bigger projects.


fix: ignore ssr

this incorrectly turned on by a client. setting it to be ignored

/hotfix

hotfix-v1.27


[WIP] Add matplotlib based drawer

This commit adds a a new python visualization module which contains a
matplotlib drawer for retworkx graphs. This first iteration of the
visualization function is porting networkx's equivalent functionality.
For now the api is basically identical to networkx's functionality
except it takes a retworkx graph object instead of a networkx graph
object. However, in follow-on commits to this branch the API will be
adapted to be more retworkx native (i.e. using callbacks to generate
labels from nodes and edges, etc).
To implement this a basic random_layout function is added to retworkx
and a corresponding 2D layout type Pos2DMapping which is used to
return the layouts efficiently (instead of creating a dict).
This is still a rough draft and before this merges into master things
will be updated.
Fixes #298
TODO:

[ ] Update API to be flatter and more retworkx-like

[ ] Reduce number of public facing APIs (only need a single draw() entrypoint)
[ ] remove retworkx from function names
[ ] Remove label functions and rely on a callback for a node's payload
[ ] Return a Figure object

[ ] Split out layout functionality into a separate PR (integrated here for first draft testing)
[ ] Add docs to build
[ ] Rewrite docs in standard sphinx style and update for new api
[ ] Add tests
[ ] Add release notes

Just to show the basics here, running:
import retworkx
from retworkx import visualization
import matplotlib.pyplot as plt

g = retworkx.directed_gnp_random_graph(10, .9)
fig = plt.figure()
ax = fig.gca()
visualization.draw(g, ax=ax)
fig.savefig('test.png', dpi=600)

yields:

There is still a lot of work to do here, but the basics work for now.

Pull Request Test Coverage Report for Build 723950749

11 of 159 (6.92%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-2.2%) to 94.491%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/lib.rs
5
28
17.86%

src/iterators.rs
6
131
4.58%

Totals

Change from base Build 723600097:
-2.2%

Covered Lines:
6158

Relevant Lines:
6517

💛  - Coveralls

I've split out the layout functionality into #305


How to use this in angular project?

I added the "import 'object-fit-images/dist/ofi.min.js"; in my polyfill.ts.
Added the font-family: 'object-fit: contain;'; in css file.

Does this requires anything else?

The usage is the same for all https://github.com/bfred-it/object-fit-images#usage

@bfred-it, I did the same changes, Could you clarify the 3rd point in the usage.
Where do I need to add objectFitImages();??


setTheme to DatePickerDialog

How I can set different theme to DatePickerDialog?
Suppose I have set AppThemeBlue to Activity  and using a fragment with AppThemeGreen in same activity. In this case DatePickerDialog showing AppThemeBlue(i.e Activity Theme) but I have to set AppThemeGreen. Need to set theme to DatePickerDialog dynamically.

https://github.com/wdullaer/MaterialDateTimePicker#additional-options
Use setAccentColor

Thanks @wdullaer its working fine


How can we track global changes without submit button?

I would like to track changes on formData with something like ng-change but ng-change gave error when I added to the dynamic-form directive. Is it possible to achieve such thing?

I'm non aware of any reason for that non to work.  Can you provide more detail on the error, and some sample code that generates it?

When you add ng-change to the directive directly on html. It gaves "ngChange requires ngModel control" on console and not rendering. But eventually it has ng-model also. I did solve the problem by detecting the page leave rather than form change to update my collection. I will try to arrange a fiddle also. Thanks for your rapid response by the way! Congrats!


Eliminate ErrorProne warnings

@googlebot I signed it!

@rainyShine thanks for the PR. The builds are failing due to style violation. Try running ./gradlew googleJavaFormat.

@chanseokoh Certainly.
I'm sorry to reread the guidelines.And I try that.

@chanseokoh I've run below command ./gradlew googleJavaFormat and pushed.
Could you check again?

This is for #3359.


appservice sending seems to stall sometimes for hours

Problem:
Messages to Signal show up sometimes (perhaps once every two, three weeks) with significant delay (hours+).
Version: docker latest tag.
I originally blamed Mautrix-Signal (where it seems to be happening most commonly for me), as described in https://github.com/mautrix/signal/issues/561.
But following sequence of events today (and lack of buffering in mautrix-signal) caused me to open this ticket too:

the messages I sent were missing (visible in Matrix clients, not in Signal)
restarting the appservice (bridge) did nothing
restarting the conduwuit caused messages to wind up in appservice, and subsequently Signal clients

Just to be sure, you're 100% confident that restarting conduwuit "clears the backlog"?
Because something we inherited from Conduit was this suspicious code that performs exponential backoff on appservice URL sending if there are issues reaching the appservice connecction URL. And I don't understand why one would want to perform exponential backoff on an appservice, because it does cause problems.
So as long as you can repeatedly reproduce that restarting conduwuit does fully clear the stuck messages, I think we can just delete exponential backoff for appservices.

This happens once every few weeks (reason: unknown) but at least in this one case messages did pop up immediately after Conduwuit was restarted. If there is some log message that would be helpful I could look it up, but I get quite a bit of conduwuit logging in general.
Before the restart of both Signal bridge and Conduwuit, there were two log messages like this spaced ~20 minutes apart:
sender:appservice{id="signal"}: conduit_service::sending::appservice: Could not send request to appservice "signal" at http://fw.lan:19328: error sending request for url (http://fw.lan:19328/_matrix/app/v1/transactions/...)

Oddly enough, there was also similar message about slack appservice at same time.
It is possible that as I did not wait very long (minute or two?) between restarting appservice and Conduwuit, that the  appservice started actually listening properly and it was really result of appservice being restarted that fixed the problem and the slow backoff causing me to suspect Conduwuit for it.
It is curious though that two different appservices, it started at ~13+ (when the Signal 'buffering' event started) for both Slack and Signal, and cleared at ~14 when I restarted them both.

Another interesting datapoint is that at 10 o'clock (roughly), both signal and slack experienced one blip of ^ log message but went ahead fine after that (I didn't notice it).

Usually I have not done restarts and it has recovered on its own, but it has taken usually couple of hours (no idea why); my bridges and Conduwuit have usually quite high uptime (Signal one was at 2 week uptime, Slack is still at 12 days, and Conduwuit container was probably up a month or so before this restart).

Most likely exponential backoff is kicking in when you see an error message log like that.
Does this issue happen consistently when you see that log? Or is this just randomly the appservice will have long delays with messages?
Regardless I think us deleting the silly exponential backoff code for appservices may be a good start.

The log is much more common than the delays I notice but of course most of the time I do not look at signal client to see when my messages are delivered. The log message seems to be printed couple of times a day for slack and signal bridges, but not for other app services ( no idea why ).
I use Slack very seldom now so it might be also doing the same thing. I vaguely remember some similar delayed send episode from months ago with it.

If you would like to, could you please test and see if the issue still persists on main branch?

I switched to main; I'll know in practice probably not very soon (as I don't notice the lag usually that often) but at least the log pattern I can tell about in a day or two.

Have you noticed an improvement?

It is hard to measure. The rate of those messages in log is perhaps slightly less, but they still appear (no idea why appservice communication on same host would fail).
I have not seen the user-visible lag yet, though, I think I'll just close this for now, and reopen if it happens again.

I think us adding the exclusion for appservices on exponential backoff has solved it then, if you said you observe appservice URL sending failures in your logs, but no user-visible lag is noticeable.
Appservice URL sending failures would cause exponential backoff to kick in and start to delay sending requests to your appservice, and then definitely the user-visible lag would show up.
As for why you are seeing those logs in the first place; they are indicative of a network or host issue of some kind. Unfortunately the HTTP Rust libraries we use don't let us pull the real error message (TCP error? DNS error? I/O error? etc) unless you use a debug build of conduwuit, or build with debug info (release-debuginfo), and grep your logs for the host. It might be good to check your appservice's logs itself too and see if it says anything possibly related.


[3.0.0] Webpack example not working

I'm submitting a ...  (check one with "x")
[x] bug report => check the FAQ and search github for a similar issue or PR before submitting
[ ] support request => check the FAQ and search github for a similar issue before submitting
[ ] feature request

Current behavior

Uncaught TypeError: Cannot read property 'prototype' of undefined

Expected/desired behavior
to work out of the box
Reproduction of the problem
git clone https://github.com/ocombe/ng2-translate.git
cd ng2-translate/examples/webpack
npm install
npm start
watch console output...
ng2-translate version: 3.0.0
Browser: [all]
don't think it's browser related

What repository are you cloning ?

Maybe due to the fact that the library isn't distributed in commonjs format ?

yes I need to update the examples with the new umd format

This has been updated, closing it now.


Add git_info module; Include create release GitHub Actions; Include PyPI publishing GitHub Actions

Closes #2
Closes #3
Closes #6

[ ] Bump version from v0.0.1 -> v0.1.0
[ ] Add CHANGELOG file
[x] Add create release GitHub Action #3
[x] Add git_info module
[x] Add PyPI publishing GitHub actions #6
[x] Add PyPI API token secrets (@astrochun) [Note: token will need to change with scope limited to redata package] #6

Commit history:

Add git_info module
Add init.py for redata_commons
Add unit tests for git_info module
Add setup.py script for packaging
Add python-package GitHub Actions
Add create-release.yml #3 [ci skip]
Exclude PyCharm from .gitignore
git_info: Remove os library usage
Add MANIFEST.in [ci skip]

I was able to build locally. Except for a minor fix, everything looks good. I was wondering if we should test it on https://test.pypi.org/

What was the minor fix that was needed?
Yes, we can publish say v0.0.1 to test PyPI. Note that versioning is fix on PyPI.  Once you publish you can't re-publish with the same version. It's not like GitHub where you can delete a tag to re-tag it. The final version of this release is 0.1.0 so that won't be an issue here. You can pip install --index-url https://test.pypi.org/simple/ redata to use Test PyPI. Once I have it published I'll note it in the PR.

Yes, we can publish say v0.0.1 to test PyPI. Note that versioning is fix on PyPI. Once you publish you can't re-publish with the same version. It's not like GitHub where you can delete a tag to re-tag it. The final version of this release is 0.1.0 so that won't be an issue here. You can pip install --index-url https://test.pypi.org/simple/ redata=0.1.0 to use Test PyPI. Once I have it published I'll note it in the PR.

Sounds good. I'll be on the lookout for when you want me to merge this into main. If I understand correctly, this repository will be using GitHub flow instead of git flow.

I did publish v0.0.1 to Test PyPI: https://test.pypi.org/project/redata/
pip install -i https://test.pypi.org/simple/ redata==0.0.1 should work


Project hierarchie III

second PR to fix the project hierarchie. This time exceptions are being moved to the places where they where thrown.
Ref.:

#253
#39

This PR is based on:

#282

Hi @serious6, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, AZPRBOT;

I didnt know where to put the following exceptions best because they are thrown from all over the project:

ServiceValidationException
ServiceVersionException

maybe you guys have an idea on this?

@serious6 I don't think we should purely base where exception is homed based on where it is thrown.  I think we should categorize exceptions in two buckets:

General exceptions - e.g. ServiceValidationException, ArgumentNullException, serialization exceptions, timeout exceptions.  Even if these are not thrown from a package today, we may want to do that in version 2.x.  Such exceptions can be included in some "low dependency" package in the dependency tree.  For example, an exceptions package, misc, core, or something along these lines.

Domain specific exception - e.g. auto-discover specific exception, calendar specific exception, etc.  These should be located close to where they are thrown.  Because it is unlikely that somewhere else outside auto-discover where we would want to throw an auto-discover exception.  So it is easy to guess the location and the location should be stable.

ok so closing this for now

@vboctor hmm looking into the things you said this should be really close to my approach.
I created a more general exception type under
 \- misc
        \-exception
                \- ArgumentException
                \- FormatException
                \- ...

and some other places like:

security -> exception for Xml related Exceptions (this is close to ews-managed-api)
property -> exception for AttachmentException and TimezoneDefinitionException
core -> exception for lots of the Service...Exceptions and the ones used in core (as mentioned close to where they are thrown)
autodiscover already has a exception package with the ones which I expected there.

I tried to devide the exceptions as close located to where they are thrown thats why I splitted these exceptions under core and property. I dont know if getting really closer makes sense because this will result in multiple single exception packages.

Because it is unlikely that somewhere else outside auto-discover where we would want to throw an auto-discover exception. So it is easy to guess the location and the location should be stable.

Unfortunately this is not the current state provided for example if you look at ServiceRequestException this has 3 new instance creation references in autodiscover and 12 in core.request. So guessing is not always easy. From my point of view regarding this particular situation we should on the one hand remove the occurences in one of the package or provide a new exception under autodiscover because once we put this only under core we will create a circular dependency.
This will also be a real pain regarding the enumerations because there are even more references all over the place.


Adding logic to skip old events

What does this PR do?
After letting the event collection run for some time, we noticed that even with the new logic, some events would still be submitted in the past.
As we migrate towards an informer for the events in the interim we need to make sure those old events are not submitted.
In order to be consistent with teh APIServer's behavior, we use 1 hour:
NAMESPACE                               LAST SEEN   FIRST SEEN   COUNT   NAME                                                                               KIND                      SUBOBJECT                                               TYPE      REASON                         SOURCE                                    MESSAGE
process                                 1h          3h           39      XX-5d4444d5-m5qkf.15d27fCCC4                                   Pod                       spec.containers{process}                         Normal    P
ulled                         kubelet, ip-10-00000-72.ec2.internal    Container image "XX.dkr.ecr.us-east-1.amazonaws.com/image:latest" already present on machine
mortar                                  1h          3h           16      obj-runner-799CCC5f-l8b9c.15d2CCC553f2                              Pod                       spec.containers{obj-runner}                    Normal    S
tarted                        kubelet, ip-10-0000-82.ec2.internal    Started container
mortar                                  1h          3h           16      obj-runner-799XXf5f-l8b9c.15d2CCCC47                              Pod                       spec.containers{obj-runner}                    Normal    C
reated                        kubelet, ip-10-000002.ec2.internal    Created container
datadog

With this logic, we can see that we do not submit old events anymore:

Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?

@CharlyF I think we can close this PR. WDYT?


Fix to set color space from color convenience ops

Pull request
Filing this PR as described (and as requested) in #779. In brief:
Section 4.5 of the PDF reference says: "Color values are interpreted according to the current color space, another parameter of the graphics state. A PDF content stream first selects a color space by invoking the CS operator (for the stroking color) or the cs operator (for the non-stroking color). It then selects color values within that color space with the SC operator (stroking) or the sc operator (nonstroking).  There are also convenience operators—G, g, RG, rg, K, and k—that select both a color space and a color value within it in a single step."
Previously, those convenience operators did not set the color space.  This commit, following on filed issue #779, fixes this.
How Has This Been Tested?
The PR also adds a test to demonstrate that, at least for the do_rg method, the fix works as intended. The other methods should, at least in theory, work analogously. I can try to find PDF(s) that allow for testing those other ones if needed.
Note: I added the test to test_converter.py since that seemed to be the closest fit among pre-existing test files, but I can move it elsewhere if desired.
Checklist

[X] I have read CONTRIBUTING.md.
[X] I have added a concise human-readable description of the change to CHANGELOG.md.
[X] I have tested that this fix is effective or that this feature works.
[n/a] I have added docstrings to newly created methods and classes.
[n/a] I have updated the README.md and the readthedocs documentation. Or verified that this is not necessary.

Thanks for the kind words, and thanks for the merge!


New GUI/IDE build script support

Pull Request Description

Important Notes

Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[ ] The documentation has been updated, if necessary.
[ ] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[ ] All code follows the
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[ ] Unit tests have been written where possible.
[ ] If GUI codebase was changed, the GUI was tested when built using ./run ide build.

Yup, thank you for catching this!
sob., 30 wrz 2023 o 23:30 somebody1234 @.***>
napisał(a):

@.**** commented on this pull request.
In app/ide-desktop/lib/client/electron-builder-config.ts
https://github.com/enso-org/enso/pull/7832#discussion_r1342010771:

@@ -99,7 +99,7 @@ export function createElectronBuilderConfig(passedArgs: Arguments): electronBuil
extraMetadata: {
version: BUILD_INFO.version,
},

   copyright: 'Copyright © 2022 ${author}.',

   copyright: `Copyright © ${new Date().getFullYear()} ${common.PRODUCT_NAME}`,

is this supposed to be common.COMPANY_NAME instead?
—
Reply to this email directly, view it on GitHub
https://github.com/enso-org/enso/pull/7832#pullrequestreview-1651750581,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAL2A5Z44PETA5PYMOFKTY3X5CFPFANCNFSM6AAAAAA44Z5IMQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Would be good to have PR description filled in for those not being in the loop :)


Add require lock file input parameter

Description
Resolves #249
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

PR checklist

[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING.md document.
[ ] I have added tests to cover my changes.

Thank you for your time.


Remove duplicate logback from jetty-maven-plugin's classpath

When running a build, I get the following warning in the Maven output:
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/tmp/jetty-<IP_ADDRESS>-0-fcrepo.war-_fcrepo-any-8021681995411204556.dir/webapp/WEB-INF/lib/logback-classic-1.1.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/kevin/.m2/repository/ch/qos/logback/logback-classic/1.1.2/logback-classic-1.1.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]

This pull request removes the logback dependency from the jetty-maven-plugin configuration since there is already a version of it on the app's classpath.

:+1: pending iCLA


Links in weekly report of ExoPlayer needs the organisation replaced

The links of issues in the email report of non-firebase repositories still use 'firebase' as the organisation and produce a 404.
The URL would need to have 'firebase' replaced with 'google' in the case of the exoplayer repository:
https://github.com/firebase/exoplayer/issues/5568
It seems to me that report.ts can already deal with the org but the org for GetWeeklyEmail is hardcoded to 'firebase':
https://github.com/firebase/oss-bot/blob/master/functions/src/report.ts#L459
https://github.com/firebase/oss-bot/blob/master/functions/src/report.ts#L568

Should be fixed by https://github.com/firebase/oss-bot/commit/4a24cc6e78e1e53c1c927725a6cab32470258404

Ha! I want to see the SAM score of this repo! :D


dict().values returns dict_values in python 3.6

When calling the .values method on a dict() object in python 3.6, a dict_values is returned, not a list as was the case in earlier versions.
This causes an error in the vis.utils.get_class_weight method in python 3.6. To fix this, you need to change
total = np.sum(class_number.values())
max_samples = np.max(class_number.values())

to
total = np.sum(list(class_number.values()))
max_samples = np.max(list(class_number.values()))

My understanding is that this patch shouldn't affect 2.* versions of python.

@jszym, Thanks man. I confirm your proposed change works with Python 3.5 as well


⚠ Bofrost.de has degraded performance

In 11d5e07, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1720 ms

Resolved: Bofrost.de performance has improved in c933d51 after 10 minutes.


How do I build/run the demo project?

Hi,
I cloned the project, and tried running it..
node app starts the server,
but it dont find the required JS file. at js/build/vendor.min.js and js/build/script.min.js.
So how to build and run the demo?

Hi,
You are required to run grunt using the command
grunt dev


Typo "**Mobility services (Preview) **"→"**Mobility services (Preview…

…)**"
https://docs.microsoft.com/en-us/azure/azure-maps/migrate-from-google-maps-web-services
#PingMSFTDocs

@hyoshioka0128 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@hyoshioka0128 - thanks for the catch.


Corrected one heading and fixed English on another

There seems to be a copy/paste issue with one of the headings. It's the same as the previous heading and doesn't reflect the next steps.
Another heading just has a grammatical error.
Module: 00
Lab/Demo: 00
Fixes # .
Changes proposed in this pull request:

Thanks for the help Greg.


[Fix #5221] Switch Layout/SpaceBeforeBlockBraces's empty braces default

As discussed on #5221 , the EnforcedStyleForEmptyBraces config for Layout/SpaceBeforeBlockBraces should be space and not no_space. This PR makes that switch.

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.
[x] Run rake default or rake parallel. It executes all tests and RuboCop for itself, and generates the documentation.

That was some epic oversight on my part. Thanks for fixing this!


fixing pathway of Transaction Fees

correction of pathway https://docs.optimism.io/stack/transactions/fees

Please create a pull request with only this changed file pages/build-on-superseed/differences-compared-to-ethereum.mdx

https://github.com/superseed-xyz/docs/pull/50/commits/a6fdf371519724ddc40ee5ff719b14f3f2041037 done


gnome3.gnome-klotski: 3.22.3 -> 3.31.3

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/gnome-klotski/versions.
meta.description for gnome3.gnome-klotski is: '"Slide blocks to solve the puzzle"'.

Checks done (click to expand)

built on NixOS
/nix/store/fbysld4647cy1fb55qq4xdkvb3dpmd96-gnome-klotski-3.31.3/bin/gnome-klotski passed the binary check.
/nix/store/fbysld4647cy1fb55qq4xdkvb3dpmd96-gnome-klotski-3.31.3/bin/.gnome-klotski-wrapped passed the binary check.
2 of 2 passed binary check by having a zero exit code.
2 of 2 passed binary check by having the new version present in output.
found 3.31.3 with grep in /nix/store/fbysld4647cy1fb55qq4xdkvb3dpmd96-gnome-klotski-3.31.3
directory tree listing: https://gist.github.com/7c8072e94cf11c3de8d484f677b4f6ba
du listing: https://gist.github.com/87a9efbe70fa30318fe395526f428f32

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
gnome3.gnome-klotski

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/fbysld4647cy1fb55qq4xdkvb3dpmd96-gnome-klotski-3.31.3 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A gnome3.gnome-klotski https://github.com/r-ryantm/nixpkgs/archive/45f89a4ed01ab46d23f14a61e6bb34c552327190.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/fbysld4647cy1fb55qq4xdkvb3dpmd96-gnome-klotski-3.31.3
ls -la /nix/store/fbysld4647cy1fb55qq4xdkvb3dpmd96-gnome-klotski-3.31.3/bin

cc @lethalman @jtojnar @hedning for testing.

Unstable version


Add step to navigate to Run-config - fiori app using ABAP

Hello,
Scenario URL: https://developers.sap.com/tutorials/abap-environment-deploy-cf-production.html
Issue: Step 5.2: Press the run button and select press button for Start ztravel_app_xxx to run your SAP Fiori application. -> Need to navigate to "run-Configurations" tab from left pane.
Please add this step to navigate, as we will be in "file explorer" after opening workspace.
Landscape Labels: trail1, trail2
Sprint Label: SCPTest-2009A
Scenario Label:SCPTest-fabap
priority label: high-prio

Hi @i353590 ,
thank your for your feedback. We updated this tutorial with following PR: #6017.
@MichaelCzcz can you merge?
Thank you.
Best regards,
Merve

Thank you for your feedback. The issue seems to be resolved, so I am closing the issue.
If you still have questions, feel free to reopen the issue.


Rename repository

coiled/benchmarks?

Renaming is something I want to do as part of https://github.com/coiled/coiled-runtime/issues/732

Anything stopping us from moving forward immediately?

+1 I also think we can rename with or without the metapackage being there or not

@jrbourbeau I'm about to send this repository link to someone external and, for the purposes of that conversation I'd much rather this was called coiled/benchmarks rather than coiled/coiled-runtime.  Do you object to me changing the name?

Okay, that was quicker than I thought. I'be got a branch. Going to change the name and push up a PR to make sure it passes


Remove GIL lock and manual garbage collection

When running this code in a worker-type application (dask), there were a couple performance bottlenecks. This PR tries to address these, provided these tweaks do not interfere with workloads that are typically used with this library.

To put a number on it, I see ~75% of time in GC toward then end of an evaluation of a 200x768x768 single-channel image.  The screenshot below is from a Google Cloud worker, showing the GC causes the iterations on the GPU to slow down as the duty cycle falls off.    The jump at 8:10 is the next image being evaluated.

This sounds good to me, @carsen-stringer ?


Python Petl - _csv.Error: line contains NULL byte

I'm running this:
table = petl.fromcsv('file.txt', delimiter = ',' , encoding = 'utf-8)
petl.todb(table, connection, 'table')

And i am getting this error on insert step:

File "/usr/local/lib/python2.7/dist-packages/petl/util/base.py", line 28, in __len__
 return sum(1 for _ in self)
 File "/usr/local/lib/python2.7/dist-packages/petl/util/base.py", line 28, in <genexpr>
 return sum(1 for _ in self)
 File "/usr/local/lib/python2.7/dist-packages/petl/io/csv_py2.py", line 45, in __iter__
 for row in reader:
 File "/usr/local/lib/python2.7/dist-packages/petl/io/csv_py2.py", line 149, in next
 row = self.reader.next()
_csv.Error: line contains NULL byte

What i can to do to solve this problem?

Hi Gabriel, this is not something I have come across myself so I don't have
an answer I'm afraid. I guess the CSV file you are reading contains a NULL
byte somewhere, my next step would be to try and find these and remove them.
On Monday, June 27, 2016, Gabriel Almeida<EMAIL_ADDRESS>wrote:

I'm running this:
table = petl.fromcsv('file.txt', delimiter = ',' , encoding = 'utf-8)
petl.todb(table, connection, 'table')
And i am getting this error on insert step:
File "/usr/local/lib/python2.7/dist-packages/petl/util/base.py", line 28, in len
return sum(1 for _ in self)
File "/usr/local/lib/python2.7/dist-packages/petl/util/base.py", line 28, in
return sum(1 for _ in self)
File "/usr/local/lib/python2.7/dist-packages/petl/io/csv_py2.py", line 45, in iter
for row in reader:
File "/usr/local/lib/python2.7/dist-packages/petl/io/csv_py2.py", line 149, in next
row = self.reader.next()
_csv.Error: line contains NULL byte
What i can to do to solve this problem?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/alimanfoo/petl/issues/380, or mute the thread
https://github.com/notifications/unsubscribe/AAq8Qk7mJ2c2nPiGdeXRguFDJlZU0xpwks5qP9NMgaJpZM4I_Gtq
.

--
Alistair Miles
Head of Epidemiological Informatics
Centre for Genomics and Global Health http://cggh.org
The Wellcome Trust Centre for Human Genetics
Roosevelt Drive
Oxford
OX3 7BN
United Kingdom
Email<EMAIL_ADDRESS><EMAIL_ADDRESS>Web: http://purl.org/net/aliman
Twitter: https://twitter.com/alimanfoo
Tel: +44 (0)1865 287721


Fix to not overflow max elements

https://github.com/DataTorrent/Netlet#contributions - please provide the unit test(s).

Added it

squashed and merged it.


Move to form-js project

What should we do?
Move to form-js project.
Why should we do it?
Support it in the bpmn-io sphere
Cf. https://camunda.slack.com/archives/C046XS3GGCR/p1698413354381529?thread_ts=1698413354.381529&cid=C046XS3GGCR

Will be done via https://github.com/bpmn-io/form-js/pull/870
Todo:

[ ] Deprecate this project


[AVM Module Issue]: AGW and Subnet in different resource group

Check for previous/existing GitHub issues

[X] I have checked for previous/existing GitHub issues

Issue Type?
Feature Request
(Optional) Module Version
v0.1.1
(Optional) Correlation Id
No response
Description
Dear module owner,
I would like to request a feature/change where we can deploy the gateway in a different resource group other than the resource group where the subnet is deployed.

2 weeks 0 comments...

Thanks for highlighting this. Let me work this and get back to you :-)

Thank you @mofaizal
Would also like to see a rewrite_rule_set block for creating rules.
Ex.
## Rewrite rules
dynamic "rewrite_rule_set" {
  for_each = var.rewrite_rule_set

  content {
    name = rewrite_rule_set.value.name

    dynamic "rewrite_rule" {
      for_each = rewrite_rule_set.value.rewrite_rules != null ? rewrite_rule_set.value.rewrite_rules : {}

      content {
        name          = rewrite_rule.value.name
        rule_sequence = rewrite_rule.value.rule_sequence

        dynamic "condition" {
          for_each = lookup(rewrite_rule_set.value, "condition", [])
          content {
            variable    = condition.value.variable
            pattern     = condition.value.pattern
            ignore_case = condition.value.ignore_case
            negate      = condition.value.negate
          }
        }

        dynamic "request_header_configuration" {
          for_each = lookup(rewrite_rule.value, "request_header_configuration", [])
          content {
            header_name  = request_header_configuration.value.header_name
            header_value = request_header_configuration.value.header_value
          }
        }

        dynamic "response_header_configuration" {
          for_each = lookup(rewrite_rule.value, "response_header_configuration", [])
          content {
            header_name  = response_header_configuration.value.header_name
            header_value = response_header_configuration.value.header_value
          }
        }

        dynamic "url" {
          for_each = lookup(rewrite_rule.value, "url", [])
          content {
            path         = url.value.path
            query_string = url.value.query_string
            reroute      = url.value.reroute
          }
        }
      }
    }
  }
}

Variable
variable "rewrite_rule_set" {
  description = "List of rewrite rule set"
  type        = any
  default     = []
}

Input
rewrite_rule_set = [
  {
    name = "XFF-Headers"

    rewrite_rules = {
      rule_1 = {
        name          = "x-forwarded-for"
        rule_sequence = 102
        request_header_configuration = [
          {
            header_name  = "X-Forwarded-For"
            header_value = "{var_client_ip}"
          }
        ]
      }
    }
  }
]

Thanks @vicrem for the feedback on rewrite_rule_set adding block for creating rules need time i need validate all the test case. Please create sperate issue for this.

Will do!

hi - i have some questions noted on the PR - it may solve the issue specifically raised here, but it does not align well to the hashcorp azurerm provider.

Yes that's much better!

@kewalaka Here is updated branch (version-0.2.0) link, Azure/terraform-azurerm-avm-res-network-applicationgateway at version-0.2.0 (github.com)

Please call out issue # in the comments g so that we have clarity when we look at the code.
Make sure that all the existing example is pass the test.
Any new scenario add please create example to test (Rewirte_rule) and update home page link


Alleviate some build warnings

Summary
Compilation outputs quite a few warnings for minor stuff such as unused variables and/or function arguments.
I decided to comment them out as they don't have any effect currently but could serve a good reminder if someone wants to use something similar in the future.
Look at my changes as deprecation before removal? :sweat_smile:

Thank you for this!
Once CI clears I'll merge


Sourced from wutime.com

I submitted wide-character construct - if you have a poignant question let me know through https://www.wutime.com

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9565cf21-a9b5-39a3-34df-1db5242f1863
Version Independent ID: ff3a236b-abbe-c74a-ca48-49081ababe36
Content: _utime, _utime32, _utime64, _wutime, _wutime32, _wutime64
Content Source: docs/c-runtime-library/reference/utime-utime32-utime64-wutime-wutime32-wutime64.md
Product: visual-cpp
Technology: cpp-ucrt
GitHub Login: @corob-msft
Microsoft Alias: corob

@Wutime This issue doesn't appear to identify a problem in the documentation. Could you clarify what's wrong? I'll reopen it if something needs to be fixed.


kafka: remove messaging.kafka.connect_errors.count metric

In #479 we introduced separate dimensions on messaging.kafka.connects.count to track successes and failures for connections to Kafka.
To prevent a breaking change we did not remove messaging.kafka.connect_errors.count, the metric we inherited from franz-go kotel plugin, with the plan to remove it at a later moment.
This issue is here to keep track of its removal.

@endorama how long do we need to keep the messaging.kafka.connect_errors.count metric ?


Add telemetry

We want to gather some information about our user's usage to help us drive the development  of the product.
It should be possible to disable telemetry via an environment variable.
Telemetry failure should be "swallowed" and "ignored".
The telemetry should contain the following information

an scrambled host specific identifier
event information or errors

@fulmicoton  Do currently have any tool/library (ex. open telemetry) in mind or is this open for discussion?

@evanxg852000 no tools. We are actually still discussing whether this is a good idea or not.

could be interesting to log which backend is used S3 or file.


x/tools/gopls: incorrect signature help for method expressions

Gopls shows the method signature rather than receiver type as the first parameter type in signatureHelp on method expressions:

This screenshot should instead show X.n(X, string) or n(X, string). Notably, the associated diagnostic shows the correct signature.

@findleyr This issue looks like it's been fixed by https://go.dev/cl/611836.


Replace $text-muted with $secondary-text-color

$text-muted derived using lighten($gray, 20%) outputs #7E8188 which was replaced by #676971.

@TheSharpieOne I see you are referring to my branch name. I am sorry for the confusion; the offending colour #7E8188 was affecting my <h5>s. I do not mention <h5> in the PR title nor in the commit.
$text-muted is used in cards, in mega-menu and in type.
If #7E8188 is not an offending colour like I had understood, I can close this PR and make the changes I need to be 508 compliant elsewhere.

closing due to inactivity