HDDS-1318. Fix MalformedTracerStateStringException on DN logs. Contributed by Xiaoyu Yao.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
39
Docker mode activated.

_ Prechecks _

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

0
mvndep
70
Maven dependency ordering for branch

+1
mvninstall
1250
trunk passed

+1
compile
1277
trunk passed

+1
checkstyle
210
trunk passed

+1
mvnsite
174
trunk passed

+1
shadedclient
1178
branch has no errors when building and testing our client artifacts.

0
findbugs
0
Skipped patched modules with no Java source: hadoop-ozone/integration-test

+1
findbugs
122
trunk passed

+1
javadoc
103
trunk passed

_ Patch Compile Tests _

0
mvndep
20
Maven dependency ordering for patch

+1
mvninstall
94
the patch passed

+1
compile
1018
the patch passed

+1
javac
1018
the patch passed

+1
checkstyle
200
the patch passed

+1
mvnsite
119
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
702
patch has no errors when building and testing our client artifacts.

0
findbugs
0
Skipped patched modules with no Java source: hadoop-ozone/integration-test

+1
findbugs
130
the patch passed

+1
javadoc
102
the patch passed

_ Other Tests _

+1
unit
30
client in the patch passed.

+1
unit
95
common in the patch passed.

-1
unit
859
integration-test in the patch failed.

+1
asflicense
45
The patch does not generate ASF License warnings.

7730

Reason
Tests

Failed junit tests
hadoop.ozone.container.ozoneimpl.TestSecureOzoneContainer

hadoop.ozone.container.ozoneimpl.TestOzoneContainer

hadoop.ozone.container.TestContainerReplication

hadoop.ozone.container.metrics.TestContainerMetrics

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/hadoop-multibranch/job/PR-641/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/641

Optional Tests
dupname  asflicense  compile  javac  javadoc  mvninstall  mvnsite  unit  shadedclient  findbugs  checkstyle

uname
Linux a8ba333b4d6a 3.13.0-153-generic #203-Ubuntu SMP Thu Jun 14 08:52:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 3f6d6d2

maven
version: Apache Maven 3.3.9

Default Java
1.8.0_191

findbugs
v3.1.0-RC1

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-641/1/artifact/out/patch-unit-hadoop-ozone_integration-test.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-641/1/testReport/

Max. process+thread count
4096 (vs. ulimit of 5500)

modules
C: hadoop-hdds/client hadoop-hdds/common hadoop-ozone/integration-test U: .

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-641/1/console

Powered by
Apache Yetus 0.9.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
28
Docker mode activated.

_ Prechecks _

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 3 new or modified test files.

_ trunk Compile Tests _

0
mvndep
61
Maven dependency ordering for branch

+1
mvninstall
997
trunk passed

+1
compile
921
trunk passed

+1
checkstyle
178
trunk passed

+1
mvnsite
137
trunk passed

+1
shadedclient
997
branch has no errors when building and testing our client artifacts.

0
findbugs
0
Skipped patched modules with no Java source: hadoop-ozone/integration-test

+1
findbugs
110
trunk passed

+1
javadoc
85
trunk passed

_ Patch Compile Tests _

0
mvndep
21
Maven dependency ordering for patch

+1
mvninstall
95
the patch passed

+1
compile
946
the patch passed

+1
javac
946
the patch passed

+1
checkstyle
185
the patch passed

+1
mvnsite
116
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
616
patch has no errors when building and testing our client artifacts.

0
findbugs
0
Skipped patched modules with no Java source: hadoop-ozone/integration-test

+1
findbugs
119
the patch passed

+1
javadoc
104
the patch passed

_ Other Tests _

+1
unit
35
client in the patch passed.

+1
unit
77
common in the patch passed.

-1
unit
1456
integration-test in the patch failed.

+1
asflicense
38
The patch does not generate ASF License warnings.

7273

Reason
Tests

Failed junit tests
hadoop.ozone.om.TestOzoneManagerHA

hadoop.ozone.container.TestContainerReplication

hadoop.ozone.container.metrics.TestContainerMetrics

hadoop.ozone.container.ozoneimpl.TestSecureOzoneContainer

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/hadoop-multibranch/job/PR-641/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/641

Optional Tests
dupname  asflicense  compile  javac  javadoc  mvninstall  mvnsite  unit  shadedclient  findbugs  checkstyle

uname
Linux 089b0d54691b 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / a4cd75e

maven
version: Apache Maven 3.3.9

Default Java
1.8.0_191

findbugs
v3.1.0-RC1

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-641/2/artifact/out/patch-unit-hadoop-ozone_integration-test.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-641/2/testReport/

Max. process+thread count
3674 (vs. ulimit of 5500)

modules
C: hadoop-hdds/client hadoop-hdds/common hadoop-ozone/integration-test U: .

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-641/2/console

Powered by
Apache Yetus 0.9.0 http://yetus.apache.org

This message was automatically generated.

Some of the test failures are related to this change. I'm looking into it.

The current pattern of export and import traceID over the wire (GRPC/Ratis) is via the TraceID in the protocol message. But this changed the original traceID which the test expect to be the same, which is not true with the new yaeger based tracing where the parent:children:... are appended along the invocation chain. Will remove the invalid verification from those tests, cc: @elek .

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
28
Docker mode activated.

_ Prechecks _

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 10 new or modified test files.

_ trunk Compile Tests _

0
mvndep
28
Maven dependency ordering for branch

+1
mvninstall
994
trunk passed

+1
compile
957
trunk passed

+1
checkstyle
193
trunk passed

+1
mvnsite
170
trunk passed

+1
shadedclient
1092
branch has no errors when building and testing our client artifacts.

0
findbugs
0
Skipped patched modules with no Java source: hadoop-ozone/integration-test

+1
findbugs
125
trunk passed

+1
javadoc
117
trunk passed

_ Patch Compile Tests _

0
mvndep
23
Maven dependency ordering for patch

+1
mvninstall
100
the patch passed

+1
compile
904
the patch passed

+1
javac
904
the patch passed

+1
checkstyle
231
the patch passed

+1
mvnsite
150
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
665
patch has no errors when building and testing our client artifacts.

0
findbugs
0
Skipped patched modules with no Java source: hadoop-ozone/integration-test

+1
findbugs
137
the patch passed

+1
javadoc
116
the patch passed

_ Other Tests _

+1
unit
36
client in the patch passed.

+1
unit
77
common in the patch passed.

-1
unit
653
integration-test in the patch failed.

+1
asflicense
52
The patch does not generate ASF License warnings.

6767

Reason
Tests

Failed junit tests
hadoop.ozone.ozShell.TestOzoneShell

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/hadoop-multibranch/job/PR-641/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/641

Optional Tests
dupname  asflicense  compile  javac  javadoc  mvninstall  mvnsite  unit  shadedclient  findbugs  checkstyle

uname
Linux 21d34faea4eb 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 9cd6619

maven
version: Apache Maven 3.3.9

Default Java
1.8.0_191

findbugs
v3.1.0-RC1

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-641/3/artifact/out/patch-unit-hadoop-ozone_integration-test.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-641/3/testReport/

Max. process+thread count
4532 (vs. ulimit of 5500)

modules
C: hadoop-hdds/client hadoop-hdds/common hadoop-ozone/integration-test U: .

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-641/3/console

Powered by
Apache Yetus 0.9.0 http://yetus.apache.org

This message was automatically generated.

The single test failure does not repro locally. Seems unrelated to this patch.

+1

Thanks for the review @ajayydv , the checkstyle issue is not introduced by this patch. I've opened a separate JIRA: https://issues.apache.org/jira/browse/HDDS-1350 so that we can get a clean cherry-pick for ozone-0.4 here.


IDXGIOutput::FindClosestMatchingMode fails when passing in certain ID3D12Devices as argument.

Hello,
We recently discovered that the call to FindClosestMatchingMode on the IDXGIOutput instance always fail with a E_INVALID_CALL return code when certain ID3D12Devices are passed in as the third argument IUnknown *pConcernedDevice.
Enabling the D3D12 Debug Layer does not provide any additional information about the issue apart from an internally thrown com_ptr exception.
I've tested converting to the newer IDXGIOutput1::FindClosestMatchingMode1 function, but it throws the same error.
We suspect this might be due to our usage of the D3D12 Agility SDK, and that this function was never updated to properly support it.
We're currently using D3D12 Agility version 1.606.4.
For now, we can get away without passing any device, since we do all our format checking before even reaching this point.
But it is such a small thing that can easily go unnoticed. (We've had this issue for at least a year)
ID3D12Device* ourDevice; // Assume this is a valid device
IUnknown* d3D12Device = ourDevice;

DXGI_MODE_DESC validatedMode = {};
HRESULT result = output->FindClosestMatchingMode(someModeDesc, &validatedMode, d3D12Device);

I can provide more details and testing if needed as we have a solid repro case for this.

D3D12 devices are never a valid input. Enabling the DXGI debug layer would provide an output message indicating that the passed in device doesn't support the IDXGIDevice interface.

@jenatali
Thanks for clarifying!
If this is the case, I would probably suggest to update the MSDN documentation to clarify the usage of the parameter.
Currently it just specifies this:
[in, optional] pConcernedDevice
Type: IUnknown*
A pointer to the Direct3D device interface. If this parameter is NULL, only modes whose format matches that of pModeToMatch will be returned; otherwise, only those formats that are supported for scan-out by the device are returned. For info about the formats that are supported for scan-out by the device at each feature level:


Add PJM IT SCED LMP 5 Minute

Summary

Adds IT SCED LMPs 5 min for PJM
https://dataminer2.pjm.com/feed/five_min_itsced_lmps/definition

Here's what the IT SCED LMP data looks like now:
| Interval Start            | Interval End              | Case Approval Time        | Location Id | Location Name | Location Short Name | LMP   | Energy             | Congestion | Loss  |
|---------------------------|---------------------------|---------------------------|-------------|---------------|---------------------|-------|--------------------|------------|-------|
| 2024-10-10 00:00:00-04:00 | 2024-10-10 00:05:00-04:00 | 2024-10-09 21:41:12-04:00 | 40523629    | MISO          | MISO                | 15.37 | 17.099999999999998 | -0.9       | -0.83 |
| 2024-10-10 00:00:00-04:00 | 2024-10-10 00:05:00-04:00 | 2024-10-09 21:41:12-04:00 |<PHONE_NUMBER>  | HUDSONTP      | HUDSONTP            | 8.39  | 17.1               | -9.05      | 0.34  |
| 2024-10-10 00:00:00-04:00 | 2024-10-10 00:05:00-04:00 | 2024-10-09 21:41:12-04:00 | 81436855    | LINDENVFT     | LINDENVFT           | 8.41  | 17.1               | -8.96      | 0.27  |
| 2024-10-10 00:00:00-04:00 | 2024-10-10 00:05:00-04:00 | 2024-10-09 21:41:12-04:00 | 56958967    | NEPTUNE       | NEPTUNE             | 9.25  | 17.1               | -7.87      | 0.02  |
| 2024-10-10 00:00:00-04:00 | 2024-10-10 00:05:00-04:00 | 2024-10-09 21:41:12-04:00 | 5413134     | NYIS          | NYIS                | 4.88  | 17.1               | -12.44     | 0.22  |

Compare to LMP real time 5 min:
| Time                      | Interval Start            | Interval End              | Market          | Location Id | Location Name  | Location Short Name | Location Type | LMP   | Energy | Congestion | Loss  |
|---------------------------|---------------------------|---------------------------|-----------------|-------------|----------------|---------------------|---------------|-------|--------|------------|-------|
| 2024-10-10 00:00:00-04:00 | 2024-10-10 00:00:00-04:00 | 2024-10-10 00:05:00-04:00 | REAL_TIME_5_MIN | 116013751   | ATSI GEN HUB   | ATSI GEN HUB        | HUB           | 15.68 | 15.51  | 0.33       | -0.16 |
| 2024-10-10 00:00:00-04:00 | 2024-10-10 00:00:00-04:00 | 2024-10-10 00:05:00-04:00 | REAL_TIME_5_MIN | 51217       | EASTERN HUB    | EASTERN HUB         | HUB           | 15.71 | 15.51  | -0.01      | 0.21  |
| 2024-10-10 00:00:00-04:00 | 2024-10-10 00:00:00-04:00 | 2024-10-10 00:05:00-04:00 | REAL_TIME_5_MIN | 51287       | WEST INT HUB   | WEST INT HUB        | HUB           | 15.92 | 15.51  | 0.41       | 0.0   |
| 2024-10-10 00:00:00-04:00 | 2024-10-10 00:00:00-04:00 | 2024-10-10 00:05:00-04:00 | REAL_TIME_5_MIN | 51288       | WESTERN HUB    | WESTERN HUB         | HUB           | 15.96 | 15.51  | 0.23       | 0.22  |
| 2024-10-10 00:00:00-04:00 | 2024-10-10 00:00:00-04:00 | 2024-10-10 00:05:00-04:00 | REAL_TIME_5_MIN | 4669664     | NEW JERSEY HUB | NEW JERSEY HUB      | HUB           | 15.79 | 15.51  | 0.19       | 0.09  |

One difference is the real time 5 minute data has a Market column. I could add that to the IT SCED LMP data. We'd need to add a new market to the Markets class.

One difference is the real time 5 minute data has a Market column. I could add that to the IT SCED LMP data. We'd need to add a new market to the Markets class.

i dont think we need it. that column isn't that import given it's constant for a given dataset


Screenshots stop working after a while for no reason

Describe the bug
The screenshot works correctly after jailbreaking but as time passes by it stops working, when I click on Power + Home it doesn’t take the screenshot anymore, and I have to respring the device to get it working again.
To Reproduce
I don’t do anything special on my phone, just stops working after a while.
Device (please complete the following information):

iOS Version: 12.4
iOS Device: iPhone 6s
unc0ver Version: Always happened to me since first unc0ver public beta and now is happening at 3.7.0 b3.

Place an "x" between the brackets if true:

[ x ] this issue is present with all tweaks uninstalled(except for default packages) or disabled
[ x ] this issue is present after a rootfs restore
[ x ] this issue is present on the latest version of unc0ver

show a list of the tweaks you are currently using please.

use the tweak "Flame"  to get this list.

7-zip (POSIX): 16.02-1
AnimationsBeFastPlus: 2.0
AppList: 1.5.15~beta1
Apps Managed: 1.5.0-12
AppStore++: 0.9.7
AppSync Unified: 64.0
APT (apt-key): 1.8.2-1
APT (libapt-pkg): 1.8.2-1
APT 0.7 Transitional: 1:0-2
APT 1.4 Transitional: 1:0
APT Strict (lib): 1.8.2-1
APT: 1.8.2-3
AskBeforeCalling Too 12: 1.0.0~beta18-7
Assuan: 2.5.1-1
AwesomePageDots: 1.1.2
BackupAZ 3 (iOS 10 - 12): 1.6.1
Base Structure: 1-5
Baylor: 1.2
Berkeley DB: 6.2.32-1
BetterCCXI: 1.6.0
BigBoss Icon Set: 1.0
blankpass: 0.0.1-1+debug
Bourne-Again SHell: 5.0.3-2
BrickFix: 1.0.1
bzip2: 1.0.6-1
CA Certs: 0.0.2
CallDismiss12: 1.0.0~beta6
Cappd: 1.0.3
CCBrightnessExtended: 1.0
CCModules Pro: 1.0.2
CCSupport: 1.2.2
Cephei: 1.13.1-2
Cercube for YouTube: 5.1.1
ColorBadges: 1.4.1
ColorBanners 2: 1.2.4
CopiedBanner12: 0.0.2
CopyLog: 1.2.5
Core Utilities (/bin): 8.31-1
Core Utilities: 8.31-1
Cuboid: 2.0.1
Cuttlefish: 1.2
Cydia Installer: 1.1.32~b22
Cydia Substrate: 0.9.7033
Cydia Translations: 1.1.32~b1
CyDown: 7.0.1
DarkKeys: 1.1.2
Darwin Tools: 1.1-1
Debian Packager: 1.19.7-1
Debian Utilities: 4.8.6-1
Diff Utilities: 3.6-1
diskdev-cmds: 593.221.1-1
DiskProbe: 0.7.3b
DismissProgress: 1.0.4
DoubleCut: 0.5
Dragspring: 1.2.1
EasyBrightness: 1.1.2
EasySwitcherX: 0.0.7
Essential: 0-1
ExactTime: 1.6
ExactTimeMessages: 1.0
ExactTimePhone: 1.0-1+debug
FastForwardTime: 2.0.2
file: 5.35-2
Filza File Manager: 3.7.0-18
Find Utilities: 4.6.0-2
Flame: 1.3
FloatingDockPlus: <IP_ADDRESS>
Fortune: 1.4.4
FoxFort Tools: 1.0.7
Gawk: 4.2.1-1
gettext: 0.19.8-1
GNU Cryptography: 1.8.3-1
GNU Multiple Precision Arithmetic Library: 6.1.2-1
GnuPG Errors: 1.32-1
GnuPG: 2.2.11-2
GnuTLS: 3.5.19-1
GoodWiFi: 0.0~beta5
grep: 3.1-1
gzip: 1.9-1
iCleaner Pro: 7.7.5
iOS Firmware: 12.4
iPadStatusBar: 1.1.6
iPhone Firmware (/sbin): 0-1
Jailbreak Resources: 1.0~b26
KSBA: 1.3.5-1
LetMeBlock: <IP_ADDRESS>
libcolorpicker: 1.6.4
libCSColorPicker: 1.0.3
libCSPreferences: 1.2.0
Liberty Lite: 0.2.10
libfoxfortutils64: 1.0.9
libidn2: 6.1.2-1
libnotifications: 0.2-3
libpackageinfo (cokepokes): <IP_ADDRESS>-3
libplist: 2.0.0-2
libSparkAppList: 1.0.3
libswift (stable): 5.0
libswift4: 4.2.1-2
libtasn1: 4.13-1
libunistring: 0.9.10-1
Link Identity Editor: 2:2.1.1+elucubratus2
Locale Profiles in UTF-8: 1.0-1
LowBatteryBanner [Public]: 1.0.2
LowPowerCharging: 0.0.2
LZ4: 1.7.5-1
LZMA Utils: 2:4.32.7-2
MathTeacher: 1.1.1
MenushkaPrefs: 1.2.2
MobileSubstrate Dummy Package: 0.9.7033+dummy
Nanobanners: 0.1.2
NCGrabberInfo: 1.0
nControl: 1.2.2-19
Nettle: 3.4.1-1
New Curses: 5.9-1
New Curses: 6.1-1
New GNU Portable Threads: 1.6-1
NoCallBlur: 1.0.1
NoLargeTitles: 1.0-1
OhMyFlash: 1.0.0
OneNotify: 1.2.2
OpenSSL 1.0 Libraries: 1.0.2s-1
p11-kit: 0.23.12-1
PhoenixOS Theme: 1.1.1
PieCrust: 1.0.5-1
PortraitXI: 1.0.5
PowerGuard: 2.0.3
PowerSelector (iOS 11 & 12): 1.2.1
PreferenceLoader: 2.2.4~beta1
PrefixUI: 1.2.6
Profile Directory: 0-1
readline: 8.0-1
RealCC: 1.0.2
ReProvision: 0.5~experimental3
RespringCacheFix: 0.2
RocketBootstrap: 1.0.7~beta3
Rose: 2.2.1
Safari Plus: 1.7.7-2
sed: 4.5-1
SelectionPlus: <IP_ADDRESS>
shell-cmds: 118-8
Shunrai Theme: 1.3
Signing Certificate: 0.0.1
SleepToggle: 1.0.3
SleepyTime: 0.0.2
SlideToShowNotification: 1.0.0
SmallSiri: 1.2.2
SmoothCursor: 1.1.3
SnowBoard Dock Extension: 1.0.5~Beta1
SnowBoard Fonts Extension: 1.0.4~Beta1
SnowBoard Icon Effects Extension: 1.0.8~Beta1
SnowBoard Icon Masks Extension: 1.0.7~Beta1
SnowBoard Labels Extension: 1.0.0~Beta1
SnowBoard Page Dots Extension: 1.0.1~Beta1
SnowBoard Preset Extension: 1.0.14~Beta1
SnowBoard Procedural Wallpapers Extension: 1.0.1~Beta1
SnowBoard Respring Extension: 1.0.1~Beta1
SnowBoard Settings Icons Extension: 1.0.15~Beta1
SnowBoard StatusBar Extension: 1.0.2~Beta1
SnowBoard: 1.2.52~Beta1
Soda Repo Icons: 1.2
Substrate Safe Mode: 0.9.6003
SwipeForMore: 1.1.10
SwitchShades: 1.0
System Memory Reset Fix: 2.0
system-cmds: 790.30.1-2
Tape Archive: 1.30-2
TapTapFlip: 1.5
TechSupport Framework (cokepokes): <IP_ADDRESS>-2
ToneManager: 0.6.2-368
Translomatic: 1.2.10
Trust Cache Injector: 0.4~b5
trustDevAlert: 0.2
TSS Saver: 1.2.0
TweakReviewsDB: 0.4.2
UIKit Tools: 1.1.15-2
Ultrasound: 1.2.9
unrar: 5.6.4-1
unzip: 6.0+deb9u1-1
Viola: 1.9
Watusi 2 for WhatsApp: 1.2.17
WatusiTools: 2.1.8
WiFiScanner: 0.0.6
XZ Utils: 5.2.4-4
YTStatus: 1.2.0
Z Shell: 5.7.1-3
Zebra (BETA): 1.0~beta26-4
zip: 2.32-1

I would download the tweak called crashrepoter. when you have an issue pop up.  check this app.
Im going to guess its calldismiss12 causing your issue.

This bug is not registered by crashreporter since nothing is really crashing, it just stops doing a function. But I will uninstall CallDismiss12 to see if something changes.

Looks like it was caused by CallDismiss12, thank you!


swiftenv install --list doesn't list new releases

Swift 5.0.1 has been released for a long time ago (Apr 18, 2019)
However, when I run
$ swiftenv install --list
2.2-dev
2.2
2.2.1
3.0-dev
3.0
3.0.1
3.0.2
3.1-dev
3.1
3.1.1
4.0-dev
4.0
4.0.2
4.0.3
4.1-dev
4.1
4.2-dev
5.0-dev

It doesn't list the latest Swift versions.
I'm able to install by running swiftenv install 5.0.1, however, it's will be convenient if the list functionality works.

swiftenv install --list only shows versions of Swift it is capable of building. Given the complexities of building Swift and the amount of resources required to do so, these are unmaintained.
You can pass --no-build to see all the versions that you can install without building (binary releases available for your platform):
$ ./bin/swiftenv install --list --no-build
3.0
3.0.1
3.0.2
3.1
3.1.1
4.0
4.0.2
4.0.3
4.1
4.1.1
4.1.2
4.1.3
4.2
4.2.1
4.2.2
4.2.3
4.2.4
5.0
5.0.1

Good to mention, --list --no-build is also only capable of showing versions that the installed version of swiftenv is aware of too, it is expected to return immediately (and used for tab completions) so hitting APIs isn't a good experiance.
In those kind of cases, swiftenv install may succeed for a version that the installed swiftenv doesn't locally know about.

Thanks for the great explanations! Appreciated!


Request for more models in RISC-V benchmarks

Request description
First, I would like to express my appreciation to Che-Yu Wu for his dedicated efforts in enabling RISC-V benchmarks on the IREE dashboard. This highlights the end-to-end performance optimization achieved by IREE on the RISC-V platform.
Currently, the models benchmarking on RISC-V are:
tflite_models.DEEPLABV3_FP32,
tflite_models.MOBILEBERT_FP32,
tflite_models.MOBILENET_V1,
tflite_models.MOBILEBERT_INT8,
tflite_models.PERSON_DETECT_INT8,
tflite_models.EFFICIENTNET_INT8,
tflite_models.MOBILENET_V2_INT8,

Could we enable more models on RISC-V benchmarks? Our specific interest lies in the following:
tf_models.MINILM_L12_H384_UNCASED_INT32_SEQLEN128
tf_models.BERT_LARGE_TF_FP32_SEQLEN384
torch_models.MODEL_CLIP_TEXT_SEQLEN64_FP32_TORCH
torch_models.MODEL_UNET_2D_FP32_TORCH
torch_models.EFFICIENTNET_V2_S_FP32_TORCH

Thanks.
What component(s) does this issue relate to?
No response
Additional context
No response

I'll test them on the FPGA and post the results here, to see how long it will take to run.

Sorry for the delay. Here are some updates:
So the first problem I found is that some models are too big to be copied to our FPGA. The free disk space of ramfs and the SD card are less than 1GB. And these are the model sizes:
1.3G    ./iree_module_BertLargeTF_stablehlo___riscv_64-generic-linux_gnu-llvm_cpu__default-flags_/module.vmfb
470M    ./iree_module_ClipTextSeqLen64PT_linalg___riscv_64-generic-linux_gnu-llvm_cpu__default-flags_/module.vmfb
84M     ./iree_module_EfficientNetV2SPT_linalg___riscv_64-generic-linux_gnu-llvm_cpu__default-flags_/module.vmfb
128M    ./iree_module_MiniLML12H384Uncased_stablehlo___riscv_64-generic-linux_gnu-llvm_cpu__default-flags_/module.vmfb
3.2G    ./iree_module_Unet2dPT_linalg___riscv_64-generic-linux_gnu-llvm_cpu__default-flags_/module.vmfb

For the models that I can copy to the FPGA, here are the run times:

Model
Single thread
2 threads

EfficientNetV2SPT
1340.3s
1119.5s

MiniLML12H384Uncased
21s
18.6s

ClipTextSeqLen64PT
66.7s
42.8s

EfficientNetV2SPT took quite a long time to run but it might be feasible. Single thread vs. 2 threads doesn't seem to be scaled very well but I can double check.
I'm currently testing BertLargeTF and Unet2dPT with model files on NFS to see if they can fit in memory and if the overhead of NFS affects benchmark results.

Thanks for your effort, Jerry.
It a little surprise that EfficientNetV2SPT took quite a long time to run. In the dashboard, EfficientNet_int8(tflite) takes only ~3.3s, I thought their are similar. Do you know any special ops in EfficientNetV2SPT? We can disable it until we find the root cause because 1340.3s might be too long.
My team member @ElEHsiang will help comment the storage part.

Here is the result of BertLarge with models on NFS folder. I also ran MiniLM as the reference and in this case NFS seems to not affect the performance too much (AFAIK the model is loaded into memory before benchmarking).

Model
Single thread with model on NFS

BERT_LARGE_TF_FP32_SEQLEN384
2619.1s

MiniLML12H384Uncased
21.5s

But BertLarge also takes quite a long time to run.

It's a little surprise that EfficientNetV2SPT took quite a long time to run. In the dashboard, EfficientNet_int8(tflite) takes only ~3.3s, I thought their are similar.

I think it also could be the difference in model sizes. IIUC EfficientNet has a variety of sizes. EfficientNetV2SPT also runs 0x slower than EfficientNet_int8 (270s vs, 30s) in our x86_64 benchmarks. @mariecwhite might know more about their differences.
It looks like for now MiniLML12H384Uncased and ClipTextSeqLen64PT can be added. I'll send out the PR soon.
For the storage size, thanks for the instructions and I'll try to extend the rootfs.

IIRC, NFS was faster than the SD on my side so moving from SD to NFS was actually a major improvement.

Regarding NFS, our experience is that single-thread seems no impact but we saw some overhead in multi-thread.
Thanks @pzread, I think we can close this issue after your PRs are merged.


Wait for deployment to finish.

related to #7
oc logs -f prints logs for running deployment and waits until deployment finishes.

yes, It tracks the deploy job. Not the actual container. Tracking actual container is going to be more complicated, it will require setup healthcheck for pods and parsing output of oc  commands.

I've updated this. More explanation is in comments.
For this to work properly health checks has to be set (readines and livelines probes).
rollingParams.timeoutSeconds  - controls how log deployment will wait for pods to become healthy.
If health checks still failing after rollingParams.timeoutSeconds deployment is considered failed.

For this to work properly health checks has to be set (readines and livelines probes).
related https://github.com/almighty/almighty-core/issues/205

@kbsingh Have you had chance to try this?

@kbsingh Can you please try this and give @kadel feedback?

Not sure what I can try, isnt oc logs -f a oc 1.3 feature?

oc logs -f is in 1.2 (probably even in older versions) this is why I used
it.
In 1.3 follow for deploy (oc deploy -f) was introduced. This will make
this little bit easier. (I've tried to explain that in comment in yaml file)
This whole PR is bunch of workarounds to make it work on 1.2.
If this something that is no longer needed, we can close it.
On Thu, Dec 8, 2016 at 7:53 PM Karanbir Singh<EMAIL_ADDRESS>wrote:

Not sure what I can try, isnt oc logs -f a oc 1.3 feature?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/almighty/almighty-jobs/pull/20#issuecomment-265822353,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADfdm-jcHsxTXHCV1TL9honvnJ0Oh7Rks5rGFI3gaJpZM4J_A4o
.


Make email text/signature dynamic based on tenant

For the different tenants , the subject line , signature and email body could be different.
Arrive at an approach so that email can be customised
Whenever someone picks this card up, call an impromptu meeting with devs to chat out.

Verified, new logic is working as expected


1.4.0 causes ... has no method 'split' in karma-sourcemaps

Hi, I just upgraded to 1.4.0 and now I get the following error:
You need to include some adapter that implements karma.start method!
If I use the plugin with the karma sourcemaps plugin I get a huge dump which at the end says that
`Fatal error: Object /******/ (function(modules) { // webpackBootstrap
...
]) has no method 'split'
Downgrading to 1.3.1 works. Any ideas why?
I can provide a full list of my NPM dependencies if that is needed, but here are the main deps:
karma: 0.12.31
├──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>  └─┬<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>  └─┬<EMAIL_ADDRESS>

I see you have both karma-webpack and karma-webpack-plugin. I've been able to find the karma-webpack-plugin on npm, but I don't see it on github. What does this module do and why is can't it be included with karam-webpack?

Hmm, I get the same error without the plugin as well.
npm list |grep webp
├─┬<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>

@tarjei - Need to know if this is still an issue. For the sake of efficiency, we are starting with current versions and the team can work back from there.
If this is still an issue on a recent version of the loader & it's peerDeps, please respond here so we can get this properly triaged.

Hi @d3viant0ne, thanks for reaching out.
I haven't seen this bug in quite a while so I will close this issue. I'm not sure if the bug is fixed or it is just I who have moved on[1].

I've been using karma-webpack-with-fast-source-maps for the last year or so - wish that could be imported into karma-webpack.

Regards,
Tarjei


Contributing files

Added contributing files for the controller and UI charms.

@ColmBhandal Are file names should be capitalized? I.e. CONTRIBUTING.md?


re-design error handling

error_code
error_category
CompletionHandler's signature

Asio based library's error reporting policy is boost::system::error_code as the first argument.

async_mqtt should respect it.

Fixed by #266


Allow separate mount of data directory

"Data Directory" is a loaded term.
In the Nextcloud container, the ansible-nas nextcloud_data_directory is mounted at /var/www/html. Inside that folder is another folder called data that could be useful to define to a different storage. This requires adding another volume mount to /var/www/html/data with a variable to support it. We could default it to mount inside the default ansible-nas docker data location but I find it useful to store it on my samba shares drive.

I could make a pull request if this is agreeable.

I think this PR #493 would address this issue. I'm using a separate data directory so that it's not in the root folder from where nextcloud is served from. I haven't completely finish the changes yet but would love any comments / inputs or thoughts regarding the changes.


Add AnchorJS. Resolves #860

Ported from my site and simplified using defer attribute. I'll leave some inline notes so you understand why I shuffled some stuff around. Please feel free to use and abuse this branch.
Sidebar: It'd be a good idea to use the Google analytics async script too, and move it into the head. It helps performance (especially over HTTP/2).

How does this affect servers not using HTTP/2... i'm guessing most don't. I don't really want to advocate it if it's going to hurt performance for the majority of the users. Especially according to this line:

Only use this tracking snippet if your visitors primarily use modern browsers to access your site.

Been trying not to open the "over-optimized" can of worms with the theme. I've always viewed it as starting point with just enough best practice nods to push newbies in the right direction.
If you care about this sort of stuff you're going to hack it up to your liking anyways and likely should be rolling your own theme. Afraid if I start down this path the next thing will be optimizing for the critical path... which would be really hard as a theme since I have no control over the sort of content people are going to load up.
Then there are fonts... and how best to load those... and responsive images via srcset... and a million other things that would really amp up the complexity of using this theme.

How does this affect servers not using HTTP/2

93% of the worlds' browsers will have no problem using async/defer. In fact, not using it would be in violation of the Pareto principle for both the _main.js scripts as well as Google Analytics.

FYI - Updated last comment to be more explicit and informative. On more thing too, you'll probably need to do some CSS treatments for the links after a little tweaking. This is just an example.

Just tried to test this locally and getting this error in the console
Uncaught ReferenceError: anchors is not defined at main.min.js:5

As far as I can tell plugins/anchor.js was added to main.min.js and properly initialized.

@mmistakes Fixing. Uno momento.

@mmistakes pushed up another commit which should fix the issue. I removed the defer attribute as I've introduced a secret sauce script which uniformly detects the page has been parsed across browsers (the reason you were seeing the undefined error.
This may look like magic, but it's part of the reason jQuery was invented in the first place. If you want to, you could simply move the contents of the run function into the jQuery DOMReady wrapper function and eliminate my JS-fu. I'd've done so myself but cannot, as a good dev, blindly suggest an antipattern without first showing the proper way to do it.
I considered moving the magic into a utils folder but import (from the ES2015 spec) has zero percent adoption in 2017 and would never recommend anyone use Babel or Webpack unless they're building a single-page app.

Whoops. You'll need to run that through the minifier before running.

Updated to fix a bug with use strict (I forgot to put it in quotes) and uglified the script for ya.

You might want to branch off of develop. master doesn't have the latest stuff and it's likely going to be a pain for me to merge this in due to conflicts and such.

I'll just close for now. Just wanted to provide a sample implementation for you to use if you wanted to add the feature (additional treatments necessary from design perspective).


Storage efficient docker build image, CI, linter improvements

Updates docker workflow to reduce image size by 95% (2GB to 90MB)
Lints code and fixes errors
Updates CI to use hadolint, golangci-lint
Updates ambiguous name "server" to ipfs-server

REPOSITORY
TAG
IMAGE ID
CREATED
SIZE

gcr.io/covalent-project/ipfs-pinner
local
feb4387598d1
2 hours ago
90.1MB

gcr.io/covalent-project/ipfs-pinner
latest
c46ba5e79b2c
11 hours ago
2.02GB

I have Mac M1 and it throws
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
when I run
docker run -p 3000:3000 -i --name pinner-instance gcr.io/covalent-project/ipfs-pinner:latest;

also I see
gcr.io/covalent-project/ipfs-pinner:latest
is only 49.7 MB not  2.02GB

I have Mac M1 and it throws qemu: uncaught target signal 11 (Segmentation fault) - core dumped
when I run docker run -p 3000:3000 -i --name pinner-instance gcr.io/covalent-project/ipfs-pinner:latest;

delete all related images from your local first? and then try fresh image docker pull gcr.io/covalent-project/ipfs-pinner:latest@sha256:d4b347bb48a96029df818abc6697b687d1ecf7dcca8eba32fd1048367209c49f

@kitti-katy  @sudeepdino008  add an.env file to your docker run docker run --env-file .env <image_id> in .env add some random web3_jwt or an actual one WEB3_JWT=ABC....XYZ in either case you should see something like
generating 2048-bit RSA keypair...done
peer identity: QmPWG9HmG6GwgT5mGZA4AqhCCRzECHewjMVxsgNJ9ssjmv
2022/11/01 20:14:27 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/lucas-clemente/quic-go/wiki/UDP-Receive-Buffer-Size for details.
2022/11/01 20:14:27 Listening...

@noslav @kitti-katy I've added instructions for docker run in the README.md file. It contains the required port exports and docker volumes setup.

I'm not able to test because I cannot pull (there's some authorization error...checking with @cloggo)

>> ipfs-pinner git:(main) ✗
➜ docker pull gcr.io/covalent-project/ipfs-pinner@sha256:d4b347bb48a96029df818abc6697b687d1ecf7dcca8eba32fd1048367209c49f
Error response from daemon: unauthorized: You don't have the needed permissions to perform this operation, and you may have invalid credentials. To authenticate your request, follow the steps in: https://cloud.google.com/container-registry/docs/advanced-authentication

Logged in using gcloud auth login, still the same error.


Cannot install @langchain/community in project that uses V1 of firecrawl

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain.js documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain.js rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
npm install @langchain/community
Error Message and Stack Trace (if applicable)
npm install @langchain/community
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@mendable/firecrawl-js
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   api
npm ERR<EMAIL_ADDRESS>npm ERR!     node_modules/@monorepo/api
npm ERR!       workspace api from the root project
npm ERR!   peerOptional @mendable/firecrawl-js@"*" from<EMAIL_ADDRESS>npm ERR!   node_modules/langchain
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     api
npm ERR<EMAIL_ADDRESS>npm ERR!       node_modules/@monorepo/api
npm ERR!         workspace api from the root project
npm ERR<EMAIL_ADDRESS><0.4.0" from<EMAIL_ADDRESS>npm ERR!     node_modules/@langchain/community
npm ERR!       @langchain/community@"*" from<EMAIL_ADDRESS>npm ERR!       api
npm ERR<EMAIL_ADDRESS>npm ERR!         node_modules/@monorepo/api
npm ERR!     1 more (@getzep/zep-cloud)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@langchain/community
npm ERR!   @langchain/community@"*" from<EMAIL_ADDRESS>npm ERR!   api
npm ERR<EMAIL_ADDRESS>npm ERR!     node_modules/@monorepo/api
npm ERR!       workspace api from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /Users/jeremy/.npm/_logs/2024-10-21T21_21_26_145Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /Users/jeremy/.npm/_logs/2024-10-21T21_21_26_145Z-debug-0.log

Description
I am not able to install @langchain/community into our project due to dependency resolution issues. It is related to @mendable/firecrawl-js, but I'm not sure how to resolve it. Adding an entry to resolutions in package.json does not seem to work. I am able to work around this using legacy-peer-deps.
There is a PR here that is upgrading firecrawl to V1, and that would likely solve this issue.
System Info
npm info @mendable/firecrawl-js
npm WARN Ignoring workspaces for specified package(s)

<EMAIL_ADDRESS>| MIT | deps: 5 | versions: 71
JavaScript SDK for Firecrawl API
https://github.com/mendableai/firecrawl#readme

keywords: firecrawl, mendable, crawler, web, scraper, api, sdk

dist
.tarball<EMAIL_ADDRESS>.shasum: 1465808b1aa22e933d92424fd34d20ed54695170
.integrity: sha512-mpgNCxmlRMmnN2XgECYmodn4zQlDhCgZuXeDwfkQtY4jYQBwF3ChQYDfL4HYsQL9/DmP/5169HUlR/g8UBS6og==
.unpackedSize: 154.6 kB

dependencies:
axios: ^1.6.8                   typescript-event-target: ^1.1.1 zod: ^3.23.8
isows: ^1.0.4                   zod-to-json-schema: ^3.23.0

maintainers:
- rafaelsideguide<EMAIL_ADDRESS>- cpeffer<EMAIL_ADDRESS>- hello_sideguide<EMAIL_ADDRESS>
dist-tags:
beta: 1.4.5-beta.1  latest: 1.6.1

published a week ago by hello_sideguide<EMAIL_ADDRESS>
platform: mac
Node Version: v20.12.2
npm version: 10.5.0

@dosu I attempted to use the overrides field in package.json (we use npm) but that did not help.
That PR was marked as stale, so I'm worried it won't be merged.

Hey @jmoseley, will look into this and fix!

CC @nickscamara

Fix will go live shortly!

Amazing! Thank you


Too many nested queries when using union

From @blelump on July 13, 2016 11:26
Hi!
I am not sure this is related either to ROM or Sequel, but consider such query:
        users
        .inner_join(:students, id: :verifable_id)
        .where(verifable_type: "student")
        .select(:users__id,:email,:name,:surname)
        .union(
          users.inner_join(:employees, id: :verifable_id)
          .where(verifable_type: "employee")
          .select(:users__id,:email,:name,:surname)
        )

The corresponding SQL is given as:
SELECT * FROM
	(SELECT * FROM (
		SELECT users.id, "email", "name", "surname" FROM "users"
		INNER JOIN "students"  ON ("students"."id" = "users"."verifable_id")
		WHERE ( ("verifable_type" = 'ForeignStudent')) ORDER BY "users"."id"
	) AS "t1"
	UNION
	(SELECT * FROM (
		SELECT "users"."id", "email", "name", "surname" FROM "users"
		INNER JOIN "employees" ON ("employees"."id" = "users"."verifable_id")
		WHERE (("users"."id" IN ('1', '2')) AND ("verifable_type" = 'Employee')) ORDER BY "users"."id")
	AS "t1")
) AS "t1";

which looks quite complex. Are we missing something?
I'd expect smth like:
SELECT users.id, "email", "name", "surname" FROM "users"
INNER JOIN "students"  ON ("students"."id" = "users"."verifable_id")
WHERE ( ("verifable_type" = 'ForeignStudent'))

UNION

SELECT "users"."id", "email", "name", "surname" FROM "users"
INNER JOIN "employees" ON ("employees"."id" = "users"."verifable_id")
WHERE (("users"."id" IN ('1', '2')) AND ("verifable_type" = 'Employee'))

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/35987468-too-many-nested-queries-when-using-union?utm_campaign=plugin&utm_content=tracker%2F155789&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F155789&utm_medium=issues&utm_source=github).

Copied from original issue: rom-rb/rom#348

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/35987619-too-many-nested-queries-when-using-union?utm_campaign=plugin&utm_content=tracker%2F8353094&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F8353094&utm_medium=issues&utm_source=github).

@blelump this is sequel's "issue". You can provide from_self option for union, see this for details. The docs are saying to use it with care (no idea why), so be careful :)

@flash-gordon , thanks for clarification. Knowing that I think this issue can be closed here.


x86_64 version for old macs?

Are there plans to release binaries for x86_64 macs?
I own an old mac and I'm trying to run ethui for a local project and not able to build locally

Hey there @0xaaiden
I didn't realize we were only building for aarch64 until you asked, so I guess this was an oversight when I first worked on the build process. Also, all of my apple-using coworkers use more recent ones I believe, so this never came up in the early tests
I will note a couple of things:

tauri's docs state The minimum version of the operating system required for a Tauri app to run on macOS is 10.13 (source)
our frontend build is targeting safari14

I honestly don't know enough about the apple ecosystem to know if these could be an issue to you as well.
As for the compilation target, hopefully it's as should be as simple as adding a new release job with this target to the CI. I can work on that tomorrow
thanks for reporting!

@0xaaiden at the end of this build you will find an artifact, which you can download, extract, and hopefully install & run
https://github.com/ethui/ethui/actions/runs/9258517515
can you let me know whether or not it works? unfortunately I don't think I have a good way to test it myself (I have a local VM, but only for the aarch64 target, and it was quite a pain to set up a few months ago)


Adds supports for AWS EKS

I was missing support for connecting to AWS EKS, this PR adds support.

@superbrothers, curious to hear what you think!

Thank you for PR. To proceed to merge this PR, please read our CLA. If you accept it, please say so in this thread.

Thanks @superbrothers, I accept the CLA.

Did you try using this resources built from your PR? Did it work correct? I've never used EKS, so I don't know how aws-iam-authenticator get token. It looks like that token isn't contained in kubeconfig file.
    # Optional. Use the AWS EKS authenticator
    local use_aws_iam_authenticator
    use_aws_iam_authenticator="$(jq -r '.source.use_aws_iam_authenticator // ""' < "$payload")"
    local aws_eks_cluster_name
    aws_eks_cluster_name="$(jq -r '.source.aws_eks_cluster_name // ""' < "$payload")"
    if [[ "$use_aws_iam_authenticator" == "true" ]]; then
      if [ -z "$aws_eks_cluster_name" ]; then
        echoerr 'You must specify aws_eks_cluster_name when using aws_iam_authenticator.'
        exit 1
      fi
      echo "    exec:
      apiVersion: client.authentication.k8s.io/v1alpha1
      args:
      - token
      - -i
      - ${aws_eks_cluster_name}
      command: aws-iam-authenticator
      env: null" >> "$KUBECONFIG"
    fi

Yes, it is currently running in production. I'm frankly a little surprised it works. But my assumption is that aws-iam-authenticator uses the aws IAM role that's assigned to concourse workers.

But my assumption is that aws-iam-authenticator uses the aws IAM role that's assigned to concourse workers.

OK, I understand! 😄

@anneschuth ping

Thanks for the ping, @superbrothers, we've got this running in production, it disappeared from my radar.

@anneschuth Thank you for your contribution :blush:


raftstore: check merge entries' length to avoid slice out of range

What have you changed? (mandatory)
In merge process, target region will send entries to laggard source region. During the sending, source region may catch up with the logs, so no need to append entries for source anymore.
In this case, self.raft_group.raft.raft_log.committed - log_idx is equal to entries.len() which leads to entries[(self.raft_group.raft.raft_log.committed - log_idx) as usize..] out of slice range.
So check the len before cutting up the slice.
What are the type of changes? (mandatory)

Bugfix (a change which fixes an issue)

How has this PR been tested? (mandatory)
unit-test (will add later)
Does this PR affect documentation (docs) or release note? (mandatory)
No
Does this PR affect tidb-ansible update? (mandatory)
No
Refer to a related PR or issue link (optional)
https://github.com/pingcap/tidb/issues/11744

/release

/release

/test

/run-all-tests

no test? @Connor1996

@siddontang Already added locally, but it shows the reason is not what I thought. So this PR's fix may be incomplete, still in investigation.


Webpack parser.hooks.call does not working for imported functions

Bug report

What is the current behavior?
I'm trying to write webpack plugin for exporting translation keys per entry-point and export them to .json file.
compiler.hooks.normalModuleFactory.tap(pluginName, factory => {           factory.hooks.parser.for('javascript/auto').tap(pluginName, (parser, options) => {               parser.hooks.call.for("___").tap(pluginName, expression => {                    console.log(expression);               });            });     });
in MyComponent.js if I import the function ___ then call hooks above will not get triggered but if I define ___ as a global function and use it without importing then it works. So how should I solve this problem?

Other relevant information:
webpack version:  4.35.0
Node.js version: 10.15.0

The following works for webpack 5:
The hooks only apply for free variables and tagged variables.
If you want it to work for an imported symbol you need to tag the variable after importing. Similar to this:
https://github.com/webpack/webpack/blob/e82b870007eb353af62b6aa51b7656c67ecbceab/lib/dependencies/HarmonyImportDependencyParserPlugin.js#L62-L75
After that you can hook into parser hooks for the tag:
https://github.com/webpack/webpack/blob/e82b870007eb353af62b6aa51b7656c67ecbceab/lib/dependencies/HarmonyImportDependencyParserPlugin.js#L95-L97


Docs are not working

The Documentation in Gitlab-Pages is not working.

We will be changing that to gitbooks.com, purging the Jekyrll Page soon.


Cannot drop files from Explorer into WebView2 in a WinUI3 app

Describe the bug
When using a WebView2 in a WinUI3 application the drag and drop files from File Explorer into the WebView2 functionality behaves strangely. When displaying a page that is capable of receiving files (via copy when dropping, ex: https://www.remove.bg/ ) initially I am unable to drop files into the browser at all (a red circle with a link through it appears). However, if I click into the browser to manually choose a file through the explorer/file picker, this enables the usual drag and drop behavior, even after that explorer is closed. If I then minimize the application and maximize it again (or interact with a non-browser UI element, such as clicking a button to open a flyout), I am unable to drag and drop again.
Steps to reproduce the bug
Make a new blank WinUI3 project and replace the default button with a WebView2, and set the source to a page that has a file drop control on it (such as remove.bg). Try to drag an image from File Explorer into the browser.
Expected behavior
Dragging files from the file explorer into the browser copies the file to the app.
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.1.2
Windows app type

[ ] UWP
[ ] Win32

Device form factor
Desktop
Windows version
Windows 10 (21H2): Build 19044
Additional context
I reported this in the WebView2 repo and they directed me here (https://github.com/MicrosoftEdge/WebView2Feedback/issues/2546 ). This is not a new bug, it has been occurring since at least 0.8.

Any update on this? Issue persists in WindowsAppSDK 1.2.220909.2-experimental2

I see the same behaviour in WindowsAppsSDK version 1.2.221109.1

Still seeing this in the latest stable 1.2 version and in the prerelease 1.3.230202101-experimental1 version.

Would be nice if we could get this somehow on the roadmap to get fixed @bpulliam .

internal task

@maxibyte Work is currently in progress on this, but there have been a series of issues and it is currently unclear how many more issues need to be solved to get this working. There also might still be fundamental blockers which could require larger feature work. In short, timeline isn't yet clear, other than the good news that this is currently being worked on.

Wondering if there's already a better view on timeline when a fix would become available? Thanks!

This is a huge blocker for us - we use Blazor + MAUI to build a desktop app and this is now preventing us to use drag and drop in the app. It's not just a tiny feature but everything drag and drop related cannot be done...
Ref: https://github.com/MicrosoftEdge/WebView2Feedback/issues/2805

I just tested this in 1.4.230913002 and it's still broken, so I don't know why this was marked as fixed.

@michaelcapps this is fixed in main branch so the fix will be available in the next release from main (1.5 experimental)

Ah I completely missed it being added to the 1.5 milestone, sorry about that. Thank you!

Based on release notes https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/stable-channel#version-15-1 this got moved to 1.6 @codendone ? But is there any timeline around that already available?

@koenvd It looks like we missed some detailed in the release notes:

Dragging into a WebView2 should now be functional in 1.5. A fix for this was checked into 1.5 shortly after 1.4 was released.
Dragging out of a WebView2 (or even within a WebView2, if that drag uses drag-n-drop) is still not fixed and got moved to 1.6. Fixing dragging out requires work both in core WebView2 and the XAML element. That work is still in progress.

I find that with MAUI Blazor Hybrid its still not possible to drag a file onto a html file input element.
I recently ported a Blazor WASM app to Blazor Hybrid and the file input drag drop stopped working.
I use MudBlazor but I've been able to reproduce this with the native element and InputFile in a separate project, just adding the input to the default Blazor Hybrid template.
.NET8 + Microsoft.AspNetCore.Components.WebView 8.0.71 -> Microsoft.WindowsAppSDK 1.5.240607001


Empty curly brackets on destructuring function params raises TypeError

Hi, thanks for babel-eslint. I'm currently having some issues w/ babel-eslint, and not sure if this is a bug on eslint or on babel-eslint. Consider the following:
const foo = ({}) => a

Running eslint on above w/ babel-eslint gives me this error (not just that the syntax is wrong, but linting itself fails and aborts):
/Users/shu/code/debug-eslint/node_modules/eslint/lib/token-store.js:90
        return tokens[starts[node.range[0]] - (skip || 0) - 1];
                                 ^

TypeError: Cannot read property 'range' of undefined
    at SourceCode.api.getTokenBefore (/Users/shu/code/debug-eslint/node_modules/eslint/lib/token-store.js:90:34)
    at EventEmitter.api.(anonymous function) [as getTokenBefore] (/Users/shu/code/debug-eslint/node_modules/eslint/lib/eslint.js:888:48)
    at RuleContext.(anonymous function) [as getTokenBefore] (/Users/shu/code/debug-eslint/node_modules/eslint/lib/rule-context.js:108:33)
    at EventEmitter.ObjectPattern (/Users/shu/code/debug-eslint/node_modules/eslint-plugin-standard/rules/object-curly-even-spacing.js:180:27)
    at emitOne (events.js:82:20)
    at EventEmitter.emit (events.js:169:7)
    at NodeEventGenerator.enterNode (/Users/shu/code/debug-eslint/node_modules/eslint/lib/util/node-event-generator.js:42:22)
    at CommentEventGenerator.enterNode (/Users/shu/code/debug-eslint/node_modules/eslint/lib/util/comment-event-generator.js:98:23)
    at Controller.controller.traverse.enter (/Users/shu/code/debug-eslint/node_modules/eslint/lib/eslint.js:767:36)
    at Controller.__execute (/Users/shu/code/debug-eslint/node_modules/eslint/node_modules/estraverse/estraverse.js:397:31)

The error is never caught, so the error gets raised all the way to my editor:

Of course, the following works:
const foo = ({ a }) => a

Running it:
/Users/shu/code/debug-eslint/pass.js
  1:7  error  "foo" is defined but never used  no-unused-vars

✖ 1 problem (1 error, 0 warnings)

Reproduce Locally
I created a repo to reproduce this. You can check out the repo here: https://github.com/chibicode/debug-eslint
package.json
{
  "private": true,
  "devDependencies": {
    "babel-eslint": "^4.1.6",
    "eslint": "^1.10.3",
    "eslint-config-standard": "^4.4.0",
    "eslint-plugin-standard": "^1.3.1"
  }
}

.eslintrc
{
  "extends": "standard",
  "parser": "babel-eslint"
}

I couldn't reproduce this with latest eslint and babel-eslint 6. You might consider upgrading eslint and babel-eslint. If the error still show up please reopen.

Ok I think i see what is the error, it is a problem with the rule object-curly-even-spacing which assumes, that an object always needs to have properties defined.

I tried and I could reproduce with<EMAIL_ADDRESS>but it works with 1.3.2. :)


chore: MRK-14167 Change pcx field from snake_case to camelCase

Description
In the previous PR, I added a new field pcx-content-type which will be used by Coveo scrapper, in the schema definition however, I used snake case pcx_content_type instead of camelCase pcxContentType.
That resulted in the following deprecation warning

This PR fixes that. 💪🏽

@kevin-wynn  we need it in snake case for the query


Lifecycle hooks for crud operations.

Problem
Sometimes there's a need to run certain function before a record is added or maybe create another record or execute certain workflow after a record is created/deleted (eg: trigger websocket events), and it is useful to have away to tap into those lifecycle events.
Alternatives
Strapi has a great way of handling lifecycle events. Linking doc here.

Hey there. I think you could build this with middlewares already. However, we will be bringing a way to write custom extensions for Prisma Client. I see this one could be built directly via $use, which is a better alternative to middlewares. I can also imagine this being a top-level (client) extension. To learn more about this, you can read our proposal.

This is really useful. Probably is also the only reason I can't use Prisma

Hi @dzcpy, would you be able to elaborate why middlewares aren't meeting your expectations specifically? That would help to understand the differences which may exist between them and what you imagine this feature request to be.
Thank you!

Thanks for the additional details 🙏


Compilation failed but no failure indication is provided.

Details

Project URL: http://poc-library.readthedocs.io/en/release/
Build URL (if applicable): https://readthedocs.org/projects/poc-library/builds/4977100/
Read the Docs username (if applicable): Paebbels

Expected Result
A completed and error-free documentation generation :) -- just kidding.
I would expect an error message instead of good looking reports and a failed message with no failure indication, so I could investigate what's going on. Does our project exceed the compilation time?
Actual Result
Build failed without any visible reason.

Same here http://readthedocs.org/projects/diofant/builds/ in several recent builds.

This is a duplicate of #2614. Closing here, feel free to follow up on the other ticket if you have anything that needs to be added.


Pre-commit hook

Environment

interrogate version(s): 1.5.0, as a pre-commit hook
Operating System(s): Ubuntu (CI/CD)
Python version(s): 3.12.0

Description of the bug
When running pre-commit with interrogate as one of the hooks, the interrogate hook fails with a ModuleNotFoundError for pkg_resources.
The traceback ends with:
ModuleNotFoundError: No module named 'pkg_resources'

What you expected to happen
interrogate should execute successfully when invoked as a hook in pre-commit, without any module import errors.
How to reproduce (as minimally and precisely as possible)

Use Python version 3.12.0 for your virtual environment.
Install pre-commit with a .pre-commit-config.yaml that includes interrogate as one of the hooks.
Run pre-commit run --all-files.

The error occurs during the interrogate hook.
Anything else we need to know?
The issue seems to stem from a couple of interrelated issues:

pre-commit defaults to using the latest Python version available, which, as of October 29, 2023, is version 3.12.
Python 3.12 no longer includes setuptools by default when a new virtual environment is created, thereby causing the absence of pkg_resources.
Given this, the solution could be that interrogate should explicitly depend on setuptools.

I discovered this issue because of my CI/CD pipelines failing. One example is in LlamaBot, linked here.

The issue with pkg_resources is fixed in master with this commit: https://github.com/econchick/interrogate/commit/3aa94a6a9d6dca0a015d97ef389feb788cb466dd
In the commit, import pkg_resources was replaced with from importlib import resources. I suspect this issue will be resolved when 1.6.0 is released.

Any update on this issue's release date please?

released 1.6.0! closing this issue, but if it isn't fixed, feel free to re-open.


Moved Frame-Pointer Validation to GRPC

Moved frame-pointer-validator service and UI from Asio to gRPC.
Also reduces state to be present for the validation on the server (module information/functions) and instead send the functions to be loaded directly (offset and size).
Dissassembling requires the bit'ness of the process (i.e. 64 or 32 bit). This information is available on the client, but we do not want to rely on this, as the service should be able to be used e.g. as a static analysis at some point later. The bit'ness is part of the ElfHeader and as we have the modules path, we can easily read it. This PR extends the ElfFile with a method to retrieve that info.

@dimitry- Addressed the review comments. Could you approve once more, as soon as you looked at the new message we are showing?


Plugin not working

gql inspection not working on ubuntu 18.04

Please follow the issue template to make the issue actionable.
Without steps to reproduce this issue cannot be addressed.

Not actionable, will reopen if details about how to reproduce are provided.


⚠ Cioos Pacific CKAN Sitemap has degraded performance

In 2c17bf8, Cioos Pacific CKAN Sitemap (https://catalogue.cioospacific.ca/sitemap/sitemap-1.xml) experienced degraded performance:

HTTP code: 200
Response time: 5883 ms

Resolved: Cioos Pacific CKAN Sitemap performance has improved in 50286a6 after 1 hour, 3 minutes.


UserControl, IOT, gpio, Raspberry pi3

This issue has been moved from a ticket on Developer Community.

Hello, I am developing in c# for raspberry pi 3, I have a user control that I use as a viewer of states and errors of the app, I call it and it is shown on the page that is currently being shown. This part works well.
The problem I have is that it does not show when I call it from some event of the gpio.   If I touch any button on the screen that is linked to the user control if it is displayed, but from the gpio not.
The same problem I have when receiving an msj from the site, it has to open a page and it does not.
The iot version is 16299. Thanks a lot!

Original Comments
Fiona Niu[MSFT] on 6/22/2022, 11:15 PM:
(private comment, text removed)
cristianfea on 6/29/2022, 07:49 AM:
(private comment, text removed)
Feedback Bot on 6/29/2022, 08:17 PM:
(private comment, text removed)
ET [MSFT] on 6/30/2022, 07:05 AM:
(private comment, text removed)
cristianfea on 6/30/2022, 08:42 AM:
(private comment, text removed)
ET [MSFT] on 6/30/2022, 08:59 AM:
(private comment, text removed)

Original Solutions
(no solutions)

pruebaUserControl.zip


Remove extra border around overlay

Currently, there is some extra space on the right and bottom edges

Not sure why it's like that but I've tried a quick fix


Coverflow Negative margin issue when all items are dynamically removed and new items are inserted

I am using Default Coverflow style Flipster. It Doesn't inject negative margin to list item when all Flipster item is removed and inserted in runtime. Even after using the Index method. I have to right inline Negative margin to make it work. Also Noticed when the browser is resized plugin resets and inject the correct Negative margin to the Flipster items
Here is the PEN url
https://codepen.io/shraftali/pen/rJMYEG

The reason this is happening is because the flipster is initialized for div which are display none or which have height 0. Also this can be caused if flipster is already initialized. So to solve it you can either initialize it only before it is shown And please keep in mind not to initiliaze this again if already initialized

This repository is going into very-low-maintenance mode and declaring backlog bankruptcy


Files list is not rendered for extraction with large number of files

Issue came from UAT
Preconditions:
An annotation job with a large number (e.g., >150) of files exists
Steps to reproduce:

Go to Extractions > {EXTRACTION_NAME} > Files.

Result:
The files list keeps loading indefinitely

can't recreate condition.
@khyurri could you describe the steps in more detail?
> POST /api/v1/jobs/jobs/create_job HTTP/1.1
> Content-Type: application/json
> {"name":"test","files":[524,518,517,516,515,514,513,512,511,510,509,508,478,476,472,471,470,469,468,467,466,465,464,463,462,461,460,459,458,457,456,455,454,453,452,451,450,449,448,447,446,445,443,442,441,440,438,437,432,431,430,429,428,427,426,425,424,423,422,421,420,419,418,417,416,415,414,413,412,411,410,409,408,407,406,405,404,403,402,401,400,399,398,397,396,395,394,393,392,391,390,389,388,387,386,385,384,383,382,381,380,379,378,377,376,375,374,373,372,371,370,369,367,365,362,361,360,359,358,357,356,355,353,351],"datasets":[],"type":"ExtractionWithAnnotationJob","is_draft":false,"is_auto_distribution":true,"start_manual_job_automatically":true,"pipeline_name":"testing","pipeline_version":1,"categories":["Bible_citates"],"validation_type":"cross","owners":["02336646-f5d0-4670-b111-c140a3ad58b5"],"annotators":["a6511931-ddbc-4ea5-a885-5653773d5d48","c2a58313-cffa-4f97-bfcb-dc5aa470f3b7"],"validators":[]}

< HTTP/1.1 406 Not Acceptable
< {"detail":"No valid data (files, datasets) provided"}

I believe @DaryaGurtovenko  should help to reproduce

Verified, closed.
List of files is loaded according to the 'show on page' choice,  the pagination arrows work correctly, the list loads correctly, all files are visible, even 100 (as the largest in the number selection).


[python] Python 3 support

At this time (MDK v2.0) installing in Python 3.x environment fails:
$ curl -# -L https://raw.githubusercontent.com/datawire/mdk/master/install.sh | bash -s -- --python
######################################################################## 100,0%
= Installing the Datawire MDK from master
You seem to have Python $PYVER installed. We only support Python 2,
and we need 2.7 or higher. Check out https://www.python.org to get
that sorted out.

Python 3 has been around since 2008 and we're using it in all our projects at my company. As much as we like what Datawire offers, unfortunately it means that we can't use it at this time :(
As far as I understand this is a limitation of the quark compiler?
What I'm hoping for is that this issue can show there are many of us that would like to use Datawire in our Python 3 projects and the support would be greatly appreciated :)
:+1:

We didn't update the documentation yet, but as of today you can just pip3 install datawire_mdk

@bozzzzo Thank you! Will try and get back to you.

Docs will go out on next release, so closing this as it's now fixed.


[Bug] use xml configration can't set protocol to tri

Pre-check

[X] I am sure that all the content I provide is in English.

Search before asking

[X] I had searched in the issues and found no similar issues.

Apache Dubbo Component
Java SDK (apache/dubbo)
Dubbo Version
Dubbo Java 3.2.10
Steps to reproduce this issue
application.properties
dubbo.consumer.mesh-enable: true
consumer.xml
<dubbo:reference
        interface="io.daocloud.DemoService"
        id="demoService"
        provided-by="demoService"
        provider-port="20880"
        protocol="tri"/>

but

What you expected to happen
use dubbo prorocol in xml configration.
so how to configration triple protocol in xml?
Anything else
No response
Are you willing to submit a pull request to fix on your own?

[ ] Yes I am willing to submit a pull request on my own!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Add <dubbo:protocol name="tri"/> and try it


Apply Spring Boot's solution of coercing false LogLevel to OFF.

Fixes gh-556.

Moves https://github.com/spring-projects/spring-boot/commit/838e0ef33e6b8596b21984c63085896b7ef75e2b changes over to Spring Cloud Commons LoggingRebinder.


x/vuln: outdated govulncheck documentation

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

$ go version
go version go1.20.5 darwin/arm64

Does this issue reproduce at the latest version of golang.org/x/vuln?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env

What did you do?
Executed the following commands based on the latest documentation: https://pkg.go.dev/golang.org/x/vuln/cmd/govulncheck
go install<EMAIL_ADDRESS>govulncheck -v -test ./...

What did you expect to see?
govulncheck is an experimental tool. Share feedback at https://go.dev/s/govulncheck-feedback.

Using go1.20.5 and<EMAIL_ADDRESS>with
vulnerability data from https://vuln.go.dev (last modified 2023-06-26 16:56:57 +0000 UTC).

Scanning your code and 638 packages across 140 dependent modules for known vulnerabilities...
No vulnerabilities found.

What did you see instead?
flag provided but not defined: -v
Govulncheck reports known vulnerabilities in dependencies.

Usage:

	govulncheck [flags] [patterns]
	govulncheck -mode=binary [flags] [binary]

  -C dir
    	change to dir before running govulncheck
  -db url
    	vulnerability database url (default "https://vuln.go.dev/")
  -json
    	output JSON
  -mode string
    	supports source or binary (default "source")
  -scan-level string
    	set the scanning level desired, one of module, package or symbol (default "symbol")
  -show list
    	enable display of additional information specified by list
  -tags list
    	comma-separated list of build tags
  -test
    	analyze test files (only valid for source mode)

For details, see https://pkg.go.dev/golang.org/x/vuln/cmd/govulncheck.
flag provided but not defined: -v

Hi @julieqiu @ianthehat 👋
Looks like govulncheck documentation still mentions about -v flag while it was replaced with -show in this issue.

Thank you @dB2510 for letting us know!

This is fixed at master.


ocamlPackages.core_kernel: 0.14.0 → 0.14.1

Motivation for this change
Support for OCaml 4.12
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 114958 at 9695619f run on x86_64-linux 1

6 packages built:

libbap
patdiff
python37Packages.bap
python38Packages.bap
python39Packages.bap
satysfi


WebUI provisioning on CloudRun

Following resources are provisioned:

WebUI on Cloud Run Service
NEG pointing to the service
External LB pointing to the NEG with SSL enabled and IAP enabled
dedicated service account for the Cloud Run Service

I'll be OOO on Friday so won't get to it tomorrow, but I'll deploy and check first thing on Monday

I'll be OOO on Friday so won't get to it tomorrow, but I'll deploy and check first thing on Monday

@eeaton this PR is ready for review and testing. PTAL when available.

I tried a few things this error:

2024-09-23T14:28:26.549Z	error	cli/run.go:141	scan run failed{error 26 0  failed to load iac file '/tmp/lint/components/webui/terraform/cloudrun.tf'. error:
/tmp/lint/components/webui/terraform/cloudrun.tf:42,5-25: Unsupported argument; An argument named "replace_triggered_by" is not expected here.

However, it looks like this is a known issue with TERRASCAN, that it can't handle certain lifecycle blocks in terraform: https://github.com/tenable/terrascan/issues/1589
I'll disable terrascan from the CI suites for now, as this issue does not need to prevent this PR.


[wip] Basic docker image with Moose installed

TODO:

[x] document release instructions

Instructions added in https://github.com/tf-encrypted/moose/pull/1120


Issue was closed without resolution, again.

See my unresolved issue.

Hi @realsens01,
Let's clarify.
Are you able to run any python examples in librealsense?
Or, is below code not working for you?
**import** pyrealsense2 **as** rs
**import** numpy **as** np
**import** cv2

_# Configure depth and color streams_
pipeline = rs.pipeline()
config = rs.config()
config.enable_stream(rs.stream.depth, 640, 480, rs.format.z16, 30)
config.enable_stream(rs.stream.color, 640, 480, rs.format.bgr8, 30)
config.enable_stream(rs.stream.infrared, 1, 640, 480, rs.format.y8, 30)
config.enable_stream(rs.stream.infrared, 2, 640, 480, rs.format.y8, 30)
config.enable_record_to_file(**"test.bag"**)

_# Start streaming_
pipeline.start(config)

**try**:
 WIN_TITLE1 = **'Color + Depth'**
 WIN_TITLE2 = **'Left IR + Right IR'**
 **while True**:

 _# Wait for a coherent pair of frames: depth and color_
 frames = pipeline.wait_for_frames()
 depth_frame = frames.get_depth_frame()
 color_frame = frames.get_color_frame()
 ir1_frame = frames.get_infrared_frame(1)
 ir2_frame = frames.get_infrared_frame(2)
 **if not** depth_frame **or not** color_frame:
 **continue**

 _# Convert images to numpy arrays_
 depth_image = np.asanyarray(depth_frame.get_data())
 color_image = np.asanyarray(color_frame.get_data())
 ir1_image = np.asanyarray(ir1_frame.get_data())
 ir2_image = np.asanyarray(ir2_frame.get_data())

 _# Apply colormap on depth image (image must be converted to 8-bit per pixel first)_
 depth_colormap = cv2.applyColorMap(cv2.convertScaleAbs(depth_image, alpha=0.03), cv2.COLORMAP_JET)

 _# Stack both images horizontally_
 images = np.hstack((color_image, depth_colormap))
 images2 = np.hstack((ir1_image, ir2_image))

 _# Show images_
 cv2.namedWindow(WIN_TITLE1, cv2.WINDOW_AUTOSIZE)
 cv2.imshow(WIN_TITLE1, images)
 cv2.namedWindow(WIN_TITLE2, cv2.WINDOW_AUTOSIZE)
 cv2.imshow(WIN_TITLE2, images2)

 key = cv2.waitKey(1)
 **if** key == ord(**'q'**) **or** key == 27: _# q or ESC_
 **break**

**finally**:

 _# Stop streaming_
 pipeline.stop()

Hi @RealSenseCustomerSupport .
Thanks for your message. I do not have access to the camera at the moment, but I will test this as soon as I do. However, I'm guessing that it will fail at pipeline.start. If you compare your snippet to what I posted, you can see that they are pretty similar:
The code you posted:
import pyrealsense2 as rs
import numpy as np
import cv2

# Configure depth and color streams
pipeline = rs.pipeline()
config = rs.config()
config.enable_stream(rs.stream.depth, 640, 480, rs.format.z16, 30)
config.enable_stream(rs.stream.color, 640, 480, rs.format.bgr8, 30)
config.enable_stream(rs.stream.infrared, 1, 640, 480, rs.format.y8, 30)
config.enable_stream(rs.stream.infrared, 2, 640, 480, rs.format.y8, 30)
config.enable_record_to_file("test.bag")

# Start streaming
pipeline.start(config)

The code I posted:
import pyrealsense2 as rs2

device = rs2.context().devices[0]
serial_number = device.get_info(rs2.camera_info.serial_number)

pipeline = rs2.pipeline()
config = rs2.config()
config.enable_device(serial_number)
config.enable_stream(rs2.stream.infrared, 0)
config.enable_stream(rs2.stream.infrared, 1)
pipeline.start(config)

The primary difference between the snippets is the call to config.enable_device and the details of the config.enable_stream call. I've tried variations similar to what you posted, but I will confirm again.

Hi @realsense01,
Below code should be fine. Wait for your test update, you can also enable librealsense log to show more info by below command in the same terminal.
set LRS_LOG_LEVEL=DEBUG (windows) or export LRS_LOG_LEVEL=DEBUG (Linux)

@RealSenseCustomerSupport . If that code is fine, then the answer is: yes, the code is not working for me... as stated in my original post. I'll post the log output.

You used :
config.enable_stream(rs2.stream.infrared, 0)
config.enable_stream(rs2.stream.infrared, 1)
If i am not mistaken, you have to do
config.enable_stream(rs2.stream.infrared, 1)
config.enable_stream(rs2.stream.infrared, 2)
I think i had the same trouble and found out that a stream id of 0 provoked an error in my code. Using 1 and 2 instead of 0 and 1 fixed it.

My original post says that I tried that, but I wrote that almost 3 months ago, so I don't remember doing it. It wouldn't hurt to try again. In any case, thanks for your suggestion @bmar45 .
Quote from original:

A reply to another user question suggests using enable_stream with stream indices 1 and 2. This also didn't work. The only stream index that works is 1.

Update to address some of the previous questions.
This uses the stream indices suggested by @bmar45
This uses the code suggested by @RealSenseCustomerSupport

In [3]: import pyrealsense2 as rs
   ...: import numpy as np
   ...:
   ...: # Configure depth and color streams
   ...: pipeline = rs.pipeline()
   ...: config = rs.config()
   ...: config.enable_stream(rs.stream.depth, 640, 480, rs.format.z16, 30)
   ...: config.enable_stream(rs.stream.color, 640, 480, rs.format.bgr8, 30)
   ...: config.enable_stream(rs.stream.infrared, 1, 640, 480, rs.format.y8, 30)
   ...: config.enable_stream(rs.stream.infrared, 2, 640, 480, rs.format.y8, 30)
   ...: config.enable_record_to_file("test.bag")
   ...:
   ...: # Start streaming
   ...: pipeline.start(config)
   ...:
   ...:
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
<ipython-input-3-f010363c7b0c> in <module>()
     12
     13 # Start streaming
---> 14 pipeline.start(config)

RuntimeError: Failed to resolve request. No device found that satisfies all requirements

Requested log output:
 08/08 18:18:10,248 DEBUG [15324] (context.cpp:99) Librealsense VERSION: 2.10.4
 08/08 18:18:10,264 INFO [15324] (win-helpers.cpp:75) res=pSensorManager->GetSensorsByCategory(SENSOR_CATEGORY_ALL, &pSensorColl) returned: HResult 0x80070490: "Element not found."
 08/08 18:18:10,264 INFO [15324] (win-helpers.cpp:75) res=pSensorManager->GetSensorsByCategory(SENSOR_CATEGORY_ALL, &pSensorColl) returned: HResult 0x80070490: "Element not found."
 08/08 18:18:10,264 DEBUG [15324] (ds5-factory.cpp:279) try_fetch_usb_device(...) failed.
 08/08 18:18:10,264 WARNING [15324] (win-uvc.cpp:967) Could not retrieve USB descriptor for device 8086:b07 , id:1e0da80f
 08/08 18:18:10,496 WARNING [15324] (win-uvc.cpp:967) Could not retrieve USB descriptor for device 8086:b07 , id:1e0da80f
 08/08 18:18:10,496 DEBUG [15324] (context.cpp:99) Librealsense VERSION: 2.10.4
 08/08 18:18:10,511 INFO [15324] (win-helpers.cpp:75) res=pSensorManager->GetSensorsByCategory(SENSOR_CATEGORY_ALL, &pSensorColl) returned: HResult 0x80070490: "Element not found."
 08/08 18:18:10,511 INFO [15324] (win-helpers.cpp:75) res=pSensorManager->GetSensorsByCategory(SENSOR_CATEGORY_ALL, &pSensorColl) returned: HResult 0x80070490: "Element not found."
 08/08 18:18:10,511 DEBUG [15324] (ds5-factory.cpp:279) try_fetch_usb_device(...) failed.
 08/08 18:18:10,511 INFO [15324] (win-helpers.cpp:75) res=pSensorManager->GetSensorsByCategory(SENSOR_CATEGORY_ALL, &pSensorColl) returned: HResult 0x80070490: "Element not found."
 08/08 18:18:10,527 DEBUG [15324] (ds5-factory.cpp:279) try_fetch_usb_device(...) failed.
 08/08 18:18:10,527 WARNING [15324] (win-uvc.cpp:967) Could not retrieve USB descriptor for device 8086:b07 , id:1e0da80f
 08/08 18:18:10,781 WARNING [15324] (win-uvc.cpp:967) Could not retrieve USB descriptor for device 8086:b07 , id:1e0da80f
 08/08 18:18:10,834 INFO [15324] (win-helpers.cpp:75) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "The stream number provided was invalid."
 08/08 18:18:10,834 INFO [15324] (win-helpers.cpp:75) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "The stream number provided was invalid."
 08/08 18:18:10,834 INFO [15324] (win-helpers.cpp:75) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "The stream number provided was invalid."
 08/08 18:18:10,834 WARNING [15324] (sensor.cpp:315) Unregistered Media formats : [ UYVY Y12I Y8I  ]; Supported: [ ]
 08/08 18:18:10,881 INFO [15324] (win-helpers.cpp:75) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "The stream number provided was invalid."
 08/08 18:18:10,881 INFO [15324] (win-helpers.cpp:75) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "The stream number provided was invalid."
 08/08 18:18:10,881 INFO [15324] (win-helpers.cpp:75) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "The stream number provided was invalid."
 08/08 18:18:10,881 INFO [15324] (win-helpers.cpp:75) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "The stream number provided was invalid."
 08/08 18:18:10,897 INFO [15324] (win-helpers.cpp:75) res=pSensorManager->GetSensorsByCategory(SENSOR_CATEGORY_ALL, &pSensorColl) returned: HResult 0x80070490: "Element not found."
 08/08 18:18:10,897 DEBUG [15324] (ds5-factory.cpp:279) try_fetch_usb_device(...) failed.
 08/08 18:18:10,897 WARNING [15324] (win-uvc.cpp:967) Could not retrieve USB descriptor for device 8086:b07 , id:1e0da80f
 08/08 18:18:10,897 INFO [15324] (environment.cpp:85) Found fd unreachable streams, 4f1 extrinsics deleted
 08/08 18:18:11,166 WARNING [15324] (win-uvc.cpp:967) Could not retrieve USB descriptor for device 8086:b07 , id:1e0da80f
 08/08 18:18:11,229 INFO [15324] (win-helpers.cpp:75) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "The stream number provided was invalid."
 08/08 18:18:11,229 INFO [15324] (win-helpers.cpp:75) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "The stream number provided was invalid."
 08/08 18:18:11,229 INFO [15324] (win-helpers.cpp:75) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "The stream number provided was invalid."
 08/08 18:18:11,229 WARNING [15324] (sensor.cpp:315) Unregistered Media formats : [ UYVY Y12I Y8I  ]; Supported: [ ]
 08/08 18:18:11,267 INFO [15324] (win-helpers.cpp:75) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "The stream number provided was invalid."
 08/08 18:18:11,267 INFO [15324] (win-helpers.cpp:75) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "The stream number provided was invalid."
 08/08 18:18:11,267 INFO [15324] (win-helpers.cpp:75) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "The stream number provided was invalid."
 08/08 18:18:11,267 INFO [15324] (win-helpers.cpp:75) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "The stream number provided was invalid."
 08/08 18:18:11,282 INFO [15324] (win-helpers.cpp:75) res=pSensorManager->GetSensorsByCategory(SENSOR_CATEGORY_ALL, &pSensorColl) returned: HResult 0x80070490: "Element not found."
 08/08 18:18:11,282 DEBUG [15324] (ds5-factory.cpp:279) try_fetch_usb_device(...) failed.
 08/08 18:18:11,282 WARNING [15324] (win-uvc.cpp:967) Could not retrieve USB descriptor for device 8086:b07 , id:1e0da80f
 08/08 18:18:11,282 INFO [15324] (environment.cpp:85) Found fd unreachable streams, 4f1 extrinsics deleted
 08/08 18:18:11,552 WARNING [15324] (win-uvc.cpp:967) Could not retrieve USB descriptor for device 8086:b07 , id:1e0da80f
 08/08 18:18:11,599 INFO [15324] (win-helpers.cpp:75) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "The stream number provided was invalid."
 08/08 18:18:11,599 INFO [15324] (win-helpers.cpp:75) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "The stream number provided was invalid."
 08/08 18:18:11,599 INFO [15324] (win-helpers.cpp:75) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "The stream number provided was invalid."
 08/08 18:18:11,599 WARNING [15324] (sensor.cpp:315) Unregistered Media formats : [ UYVY Y12I Y8I  ]; Supported: [ ]
 08/08 18:18:11,637 INFO [15324] (win-helpers.cpp:75) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "The stream number provided was invalid."
 08/08 18:18:11,637 INFO [15324] (win-helpers.cpp:75) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "The stream number provided was invalid."
 08/08 18:18:11,637 INFO [15324] (win-helpers.cpp:75) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "The stream number provided was invalid."
 08/08 18:18:11,637 INFO [15324] (win-helpers.cpp:75) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "The stream number provided was invalid."
 08/08 18:18:11,652 WARNING [15324] (rs.cpp:1426) null pointer passed for argument "profile"

Hi @realsens01,
Your D435 camera behavior is quite weird. Per the log, the host even can't retrieve the USB descriptor. Suggest to upgrade your D435 firmware and librealsense and see how it works.

Hi @realsens01,
How is everything going?

I still can't record two IR streams.

Hi @realsense01,
I would suggest to have a RMA process for the failure analysis. You can check with your reseller. By the way, how many cameras do you have with this issue?

Hi @realsense01,
Haven't seen a response on this thread for a while.  Let us know your latest.

I purchased 4 D435 cameras directly from Intel. We use 2 at a time for data collection.

Are you still seeing the original issue that was presented on the thread?

YES. I see the original issue on the four D435 cameras that I purchased directly from Intel.

Hi @realsens01
Did you attempt to RMA the cameras with the return process on the site?

Hi @realsens01
With the latest LRS and FW, does this issue continue?
*If we don’t hear from you in 7 days, this issue will be closed.


Updated CHANGELOG.md and workflows for 1.4.0 release

Changes required for the 1.4.0 release

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

Comparison is base (33dc8ca) 90.68% compared to head (65ceac8) 90.68%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master     #187   +/-   ##
=======================================
  Coverage   90.68%   90.68%
=======================================
  Files          12       12
  Lines         279      279
=======================================
  Hits          253      253
  Misses         26       26

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


Add ability to install dependencies per script

This is a copied versin of https://github.com/ngld/OverlayPlugin/blob/master/tools/fetch_deps.py so credits go to ngld
Please ignore the commits... my brain could not handle git yesterday... <.<

I see many conversations up there, but I think dummy.txt files under ThirdParty directory should be changed quickly. I had hard time making able to be built because of those wrong information.

Why did you update the SDK version? In my experience, users have to use the same parser version you compiled your plugin with or a newer version. This means that it's very desirable to compile with an old SDK because that means your plugin will remain compatible with older parser versions which is very important for Korean and Chinese players.

For better or for worse, I've been compiling against latest versions for a while now and nobody has complained, so I think this might be ok for now given the lack of complaints so far.  It'll only get more loose as time moves forward and these versions are pinned.
Also, the Korean version appears as if it is always ahead: FFXIV_ACT_Plugin_Korean_<IP_ADDRESS>.zip, and so that shouldn't be an issue.


Bundler.bat is not available anymore

When we refresh Ruby versions and gems on build worker images we do not do in-place "upgrade", but we do clean Ruby install. Right after install gem update --system is run to update rubygems. Apparently, Bundler 1.16.0 is being pulled by latest gem update --system and bundler.bat is not in bin folder anymore, only bundle.bat. Is it a regression or intended change?
I just did clean re-install of Ruby 2.4 on my dev machine and got only bundle.bat:

This is installation log for clean Ruby 2.4 install:
c:\>ruby --version
ruby 2.4.2p198 (2017-09-14 revision 59899) [x64-mingw32]

c:\>gem update --system
Updating rubygems-update
Fetching: rubygems-update-2.7.2.gem (100%)
Successfully installed rubygems-update-2.7.2
Parsing documentation for rubygems-update-2.7.2
Installing ri documentation for rubygems-update-2.7.2
Installing darkfish documentation for rubygems-update-2.7.2
Done installing documentation for rubygems-update after 34 seconds
Parsing documentation for rubygems-update-2.7.2
Done installing documentation for rubygems-update after 0 seconds
Installing RubyGems 2.7.2
Bundler 1.16.0 installed
RubyGems 2.7.2 installed
Regenerating binstubs
RubyGems system software updated

This is a rubygems issue, please open a new issue at https://github.com/rubygems/rubygems

If you want the bundler exe, you'll need to install Bundler separately. It is intentional that RubyGems only has the bundle exe, and not bundle-ruby nor bundler

@segiddins Thank you! However, bundler executable is broken after Rubygems update: https://github.com/rubygems/rubygems/issues/2083


aur-build.1: Remove mention of keyserver-options

The option has been deprecated and is now just called auto-key-retrieve.

--keyserver-options {name=value}
…
auto-key-retrieve
This is an obsolete alias for the option auto-key-retrieve.  Please do not use it; it will be removed in future versions..

Cheers


devalue randomly produces "RangeError: Maximum call stack size exceeded"

Version
v2.6.2
Reproduction link
https://github.com/nuxt/devalue
Steps to reproduce
The error pops out randomly when calling devalue on an Axios error object. I noticed that the error pop out more frequently when the nuxt dev server was launched a while ago and not when is freshly launched, but can't find a way to make it happen everytime.
The error comes out even if the axiosError is the simplest error object returned in requests that produces an early NetworkError during OPTIONS pre-flight requests.
The line causing recursion is this
return "{" + Object.keys(thing).map(function (key) { return safeKey(key) + ":" + stringify(thing[key]); }).join(',') + "}";

What is expected ?
devalue() returns a stringified object representation
What is actually happening?
devalue() raises a "RangeError: Maximum call stack size exceeded"

This bug report is available on Nuxt community (#c9066)

any workaround ?

@aldarund can you help out?

Devalue is being used to serialize the state of an SSR rendered page
"OPTIONS" request only happens browser side, not server-side
If Error is unhandled an error page should be thrown without SSR
If an Error object exists in state object, devalue should warn about "non-POJOs"

Without a reproduction repo, it is hard to guess the cause.

I made additional obersavations that could replace the "randomly" I wrote before. But maybe I was using devalue in a wrong way, here's what I did

I have an axios interceptor installed from a plugin using ctx.$axios.onError(myFunc)
When myFunc(err) were triggered, if the error wasn't something expected, it called at the end ctx.error({statusCode: x, message: y, axiosError: err})
On my custom error layout there was a computed property that did return devalue(this.error.axiosError)
If the listener were triggered on server side, the RangeError would come out

But I will build a reproduction repo tomorrow morning and try to verify all that. Sorry for not having investigated better before.

@dappiu Thanks for all additional info. original devalue disallows serializing non-pojos. For nuxt, we made a soft warning to prevent breaking changes for users. I highly recommend not serializing entier axiosError object, but picking needed fields from it.

It's exactly what I end up doing at last. You can close the bug report, provided that I was using devalue in an unorthodox way.
Thank you for support.

Posted a solution here too https://cmty.app/nuxt/nuxt.js/issues/c10415

Posted a solution here too https://cmty.app/nuxt/nuxt.js/issues/c10415

Thanks! That was exactly the point ;)


update the home page

@moonming I just created the issue here.

DONE, feel free to reopen it if there has new issues.


Implement iterable/repeat

This commit implements a repeat() function for indefinitely repeating a given iterator as specified in #13 and #16.

Should be all set now :+1:

you are quick!
another alternative would be:
function* repeat(){
    if( Array.isArray(this) && this.length == 0 ) break;
    while(1){
        yield* this;
    }
}

But i'm not sure if there are any remaining cases which would let the loop spin without yielding...

This doesn't look like it can handle non-restartable iterators, e.g.
function step (start, amount) {
  let current = start;
  while ( true ) {
    yield current;
    current += start;
  }
}

step(2, 2)::head(3)::repeat()::head(6)::to(Array).should.equal([2, 4, 6, 2, 4, 6]);

we should probably iterate over it while yielding and storing first, then keep yielding the stored items.

Yielding and storing the items of the iterator first and then indefinitely yielding from the stored array worked a treat.

Thank you, great stuff! Keep it coming! ;) :heart: :tada:


Add chinese documentations for Packages (#24914)

backport: #24914

This one seems to have brought a lint error onto 1.19:
https://drone.gitea.io/go-gitea/gitea/74958/1/4
docs/content/doc/packages/cran.zh-cn.md:93:3 MD047/single-trailing-newline Files should end with a single newline character

This one seems to have brought a lint error onto 1.19:

will be fix in #25022 🤦♂


RE4 remake: Character heads and some objects do not update position in the right eye

Describe the bug
Occasionally, character heads - Leon, Ashley, Luis, Certain Boss NPC's will not render in the right eye.
Sometimes you can see the head mesh appear stuck, floating where a character was.
When closing the left eye, the characters face is invisible, but their hair and body is still there.
On occasion this will happen to objects in both eyes:
Leon's gun when he meets Ada in the castle.
Luis' cigarettes and lighter during his death scene.
Log
re2_framework_log.txt
Identify the REFramework version
1.5.2 Release
To Reproduce
As far as I can tell, just play in vr on the index
Expected behavior
Both eyes see the same image, and object positions are updated during draw calls
Screenshots

Desktop and VR (please complete the following information):
Steam VR 2.2.3
Windows 10
Nvidia 3080 FE
AMD Ryzen 9 5900x
Virtual Reality
Valve Index
SteamVR (OpenVR)
Additional context
Other than cutscenes, It seems to happen most frequently at the beginning of chapters.
Sometimes, it can "catch up" or only reoccur when a certain distance away from the NPC.

Not an issue in the pd-upscaler branch
Download it here: https://github.com/praydog/REFramework/actions

Not an issue in the pd-upscaler branch
Download it here: https://github.com/praydog/REFramework/actions

@praydog It's worth noting, that even with that branch, objects still disappear. Though it does solve the character mesh problem.
Ada in separate ways cutscenes constantly loses her lower body. Thank you for this mod and for your assistance.


macOS - locateOnScreen() coordinates are off by a factor of 2

locateOnScreen() works perfectly on Ubuntu Linux but on MacOS it always adds a varying offset.
As X increases, the coordinates returned by locateOnScreen() increases by a certain ratio, similar for Y but increases slightly less.
Doesn't matter how many desktop/workspaces I have active, the result is the same.

On my screens, there is a factor 2 on x and y returned by locateCenterOnScreen

On my screens, there is a factor 2 on x and y returned by locateCenterOnScreen

that's correct. the coordinates are off by a factor of 2. so a workaround is to use locateCenterOnScreen() and divide the coordinates by 2 before using them.

I will reopen that because it still needs a fix even if a workaround is available

The factor 2 is devicePixelRatio.
pixelRatio = pyautogui.screenshot().size[0]/pyautogui.size().width

@hangj thanks... instead of a fixed factor 2, a pixel ratio would be better..

very interesting!

The factor 2 is devicePixelRatio. pixelRatio = pyautogui.screenshot().size[0]/pyautogui.size().width

can u explain more about it?

The factor 2 is devicePixelRatio. pixelRatio = pyautogui.screenshot().size[0]/pyautogui.size().width

can u explain more about it?

Sometimes the screen is scaled up/down, either by default, or you can do it manually to make things bigger/smaller. This causes the LocateCenterOnScreen() or any other similar functions to be off by the factor the screen was scaled to. In my case it was a factor of 2. So instead if we use this formula to get a device pixel ratio, it'll work for every scaled screen sizes..


Blank page after click on product name

When I click on Products and then on specific name sometimes I have info about it but after one second it become empty like this:

and sometimes products list disapears and I must refresh or close app.

This is happen when user has a low connection of internet or too much requesting another page frequently. when the app is requesting to the server and has long pending response from server it caused max exceed request per IP.
Since this version is not doing unsubscribe request if user try to request another page and still have pending responses, it will causes blank page.
The good things for now is before further information about this issue, Don't navigate to another page very fast. Because it can make a lot of request to the server.
I will fix this in the next release asap, this is very help me. @PrzemekSkw  thanks for report this, I really appreciated!! Because this is critical issue. Good job! :+1:

Thanks, I noticed sometimes I click too fast :) but in last version it works better I think.

Ok happy to hears that, but still as I said, this version doesn't have unsubscribe function to immediately cancel the request to the server if still has pending requests. And I will fix this asap since this is critical issue, please be patient to the next release, and don't do what I said before to keep the server alive :+1:

OK, don't worry, You make great job :+1:

Fixed on ^1.0.0-beta.9


Add 2 rebus : homepage and cookie

Associated Issue: #121
Summary of Changes
Added 2 rebuses : homepage and cookie

Pull Request Test Coverage Report for Build 915

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.143%

Totals

Change from base Build 514:
0.0%

Covered Lines:
158

Relevant Lines:
180

💛  - Coveralls