audio tick noise

Hi.
How can I remove tick noise when video and audio(music) are encoded together and send to AWS S3 suing rtmp?
Here is test case.

play music in phone
I capture the music sound with mic
also I capture video from camera

Every thing is fine and good except sound. sound have have a tick noise.
Your sample app have a same issue.

Hello,
Try this:
Go to this line: https://github.com/pedroSG94/rtmp-rtsp-stream-client-java/blob/master/app/src/main/java/com/pedro/rtpstreamer/openglexample/OpenGlRtmpActivity.java#L114
And add this:
    rtmpCamera1.setMicrophoneMode(MicrophoneMode.SYNC);

Check if the problem persists.
If your problem is not solved, try with another server to discard a problem with AWS:
https://github.com/pedroSG94/rtmp-rtsp-stream-client-java/wiki/Media-servers-tested#node-rtsp-rtmp-server

One more question on tick noise.
Now I am using Camera2ApiManager.java.
If I use your default app which is use Camera1ApiManager.java, it have much less tick noise than Camera2ApiManager.java.
Dose tick noise come from video and audio sync ?
and also in VideoEncoder.java , how can I change  KEY_COLOR_FORMAT value, currently it seem to be just work for SURFACE only.
Please guide me.. thanks

I haven't audio tick noise with Camera2 or Camera1 in my devices for that reason I told you test using microphone sync mode and check with other server in my last post to try detect the possible reason.
About KEY_COLOR_FORMAT it is only used in Camera1Base with SurfaceView and TextureView, because in this mode, encode frames buffer to buffer mode (you set an Array directly to encoder instead of capture frames from Surface) instead of surface to buffer because this is the only way to support Api 16 and Api 17

I need some guide on audio encoding
in MicrophoneManager.java
I like to test AudioFormat.ENCODING_PCM_8BIT and also ENCODING_PCM_FLOAT, would guide me ?

What do you want exactly?
If you only want encode frames, if you change it in MicrophoneManager all should work fine but you need change few configuration in stream (record should work fine but I never tested it)

Question.
My program is camera2api base, audio from mic make a very crystal sound.
Default RTMP of your app, it make more soft sound.
In program I can not found any differences in audio configuration .
Because tick and popcorn sound is very closely related sound color as I tested results.
Your Default RTMP make tick noise too, but much better than my app which is use camer2api.
And also I download Larix broadcast RTMP app from google store, it dose make any tick noise with AWS medialive.
But sound color is very soft.
that is reason I am trying to make sound soft and I am check video encoding side too.
Please guide me .. . thanks a lots

As I told you before. I can't reproduce any audio problem with AWS medialive with my devices so I need few things to know the posible reason and help you:

Did you try use microphone in sync mode?:

//call it before prepareAudio
rtmpCamera1.setMicrophoneMode(MicrophoneMode.SYNC);

Can you try stream camera1 and camera2 with OpenGlView and share me audio result?
Can you record a video with camera1 and camera2 with OpenGlView and check if you have audio problems?
Can you share me configuration used in AWS medialive (maybe this is realted with that configuration and I can reproduce your problem) and player used?.

About Larix app, Is it making audio ticks? what do you means with sound color very soft?

AWS configuration
{
"name": "ticknoise",
"id": "4592273",
"arn": "arn:aws:medialive:ap-northeast-2:015730161442:channel:4592273",
"inputAttachments": [
{
"inputId": "395987",
"inputAttachmentName": "ticknoise",
"inputSettings": {
"sourceEndBehavior": "CONTINUE",
"inputFilter": "FORCED",
"filterStrength": 5,
"deblockFilter": "ENABLED",
"denoiseFilter": "ENABLED",
"smpte2038DataPreference": "IGNORE",
"audioSelectors": [],
"captionSelectors": []
}
}
],
"state": "RUNNING",
"pipelinesRunningCount": 2,
"destinations": [
{
"id": "stjz1s",
"settings": [
{
"url": "s3://hlsonly/a"
},
{
"url": "s3://hlsonly/b"
}
],
"mediaPackageSettings": []
}
],
"egressEndpoints": [
{
"sourceIp": "<IP_ADDRESS>"
},
{
"sourceIp": "<IP_ADDRESS>"
}
],
"encoderSettings": {
"audioDescriptions": [
{
"codecSettings": {
"aacSettings": {
"inputType": "NORMAL",
"bitrate": 192000,
"codingMode": "CODING_MODE_2_0",
"rawFormat": "NONE",
"spec": "MPEG4",
"profile": "LC",
"rateControlMode": "VBR",
"sampleRate": 48000,
"vbrQuality": "LOW"
}
},
"audioTypeControl": "FOLLOW_INPUT",
"languageCodeControl": "FOLLOW_INPUT",
"name": "audio_242ngc"
}
],
"captionDescriptions": [],
"globalConfiguration": {
"supportLowFramerateInputs": "DISABLED",
"inputEndAction": "NONE",
"outputTimingSource": "INPUT_CLOCK",
"outputLockingMode": "PIPELINE_LOCKING"
},
"outputGroups": [
{
"outputGroupSettings": {
"hlsGroupSettings": {
"incompleteSegmentBehavior": "AUTO",
"discontinuityTags": "INSERT",
"adMarkers": [],
"captionLanguageSetting": "OMIT",
"captionLanguageMappings": [],
"hlsCdnSettings": {
"hlsS3Settings": {
"logUploads": "ENABLED"
}
},
"inputLossAction": "EMIT_OUTPUT",
"manifestCompression": "NONE",
"destination": {
"destinationRefId": "stjz1s"
},
"ivInManifest": "INCLUDE",
"ivSource": "FOLLOWS_SEGMENT_NUMBER",
"clientCache": "ENABLED",
"tsFileMode": "SEGMENTED_FILES",
"manifestDurationFormat": "FLOATING_POINT",
"segmentationMode": "USE_SEGMENT_DURATION",
"redundantManifest": "DISABLED",
"outputSelection": "MANIFESTS_AND_SEGMENTS",
"streamInfResolution": "INCLUDE",
"iFrameOnlyPlaylists": "DISABLED",
"indexNSegments": 10,
"programDateTime": "EXCLUDE",
"programDateTimePeriod": 600,
"keepSegments": 10,
"segmentLength": 60,
"timedMetadataId3Frame": "PRIV",
"timedMetadataId3Period": 10,
"hlsId3SegmentTagging": "DISABLED",
"codecSpecification": "RFC_4281",
"directoryStructure": "SINGLE_DIRECTORY",
"segmentsPerSubdirectory": 10000,
"mode": "LIVE"
}
},
"outputs": [
{
"outputSettings": {
"hlsOutputSettings": {
"nameModifier": "_1",
"hlsSettings": {
"standardHlsSettings": {
"m3u8Settings": {
"audioFramesPerPes": 4,
"audioPids": "492-498",
"nielsenId3Behavior": "NO_PASSTHROUGH",
"patInterval": 0,
"pcrControl": "PCR_EVERY_PES_PACKET",
"pmtPid": "480",
"programNum": 1,
"scte35Pid": "500",
"scte35Behavior": "NO_PASSTHROUGH",
"timedMetadataPid": "502",
"timedMetadataBehavior": "NO_PASSTHROUGH",
"videoPid": "481"
},
"audioRenditionSets": ""
}
},
"h265PackagingType": "HVC1"
}
},
"outputName": "7n21qc",
"videoDescriptionName": "video_n3k9db",
"audioDescriptionNames": [
"audio_242ngc"
],
"captionDescriptionNames": []
}
]
}
],
"timecodeConfig": {
"source": "SYSTEMCLOCK"
},
"videoDescriptions": [
{
"codecSettings": {
"h264Settings": {
"afdSignaling": "NONE",
"colorMetadata": "INSERT",
"adaptiveQuantization": "AUTO",
"bitrate": 2500000,
"bufSize": 3000000,
"entropyEncoding": "CABAC",
"flickerAq": "ENABLED",
"forceFieldPictures": "DISABLED",
"framerateControl": "SPECIFIED",
"framerateNumerator": 30,
"framerateDenominator": 1,
"gopBReference": "DISABLED",
"gopClosedCadence": 1,
"gopSize": 30,
"gopSizeUnits": "FRAMES",
"subgopLength": "DYNAMIC",
"scanType": "PROGRESSIVE",
"level": "H264_LEVEL_AUTO",
"lookAheadRateControl": "MEDIUM",
"maxBitrate": 3000000,
"numRefFrames": 1,
"parControl": "INITIALIZE_FROM_SOURCE",
"profile": "HIGH",
"rateControlMode": "VBR",
"syntax": "DEFAULT",
"sceneChangeDetect": "ENABLED",
"spatialAq": "ENABLED",
"temporalAq": "ENABLED",
"timecodeInsertion": "DISABLED"
}
},
"height": 720,
"name": "video_n3k9db",
"respondToAfd": "NONE",
"sharpness": 50,
"scalingBehavior": "DEFAULT",
"width": 1280
}
]
},
"roleArn": "arn:aws:iam::015730161442:role/AllowMediaLiveAccessRole",
"inputSpecification": {
"codec": "AVC",
"resolution": "HD",
"maximumBitrate": "MAX_10_MBPS"
},
"logLevel": "WARNING",
"tags": {},
"channelClass": "STANDARD",
"pipelineDetails": [
{
"pipelineId": "0",
"activeInputAttachmentName": "",
"activeInputSwitchActionName": "",
"activeMotionGraphicsUri": "",
"activeMotionGraphicsActionName": ""
},
{
"pipelineId": "1",
"activeInputAttachmentName": "",
"activeInputSwitchActionName": "",
"activeMotionGraphicsUri": "",
"activeMotionGraphicsActionName": ""
}
],
"maintenanceWindow": "NOT_NEEDED",
"maintenanceStatus": ""
}

About  Larix app, they do not have any tick noise...

Did you try use microphone in sync mode?:

//call it before prepareAudio
rtmpCamera1.setMicrophoneMode(MicrophoneMode.SYNC);

Can you try stream camera1 and camera2 with OpenGlView and share me audio result?
Can you record a video with camera1 and camera2 with OpenGlView and check if you have audio problems?

Can you check this, please?

Now I am using camera2in my app.
To camera1 I have to change many part of my program.
anyway
I tested rtmpCamera2.setMicrophoneMode(MicrophoneMode.SYNC);
results is same.
I give you the link can find..
https://drive.google.com/file/d/1IguyjySTho1Q110vjIqm4VIx3ziGueyG/view?usp=sharing
can you guide me how to apply OpenGlview ?
I just change the following in camera2base,java
is it ok ?
@Deprecated
//public Camera2Base(SurfaceView surfaceView) {
public Camera2Base(SurfaceView glInterface) {
this.surfaceView = surfaceView;
this.context = surfaceView.getContext();
init(context);
}

Ok, I can heard ticks in the first video but it is really low, the second is clear in my opinion. We can try this:

First of all, compile my app example and record a video to compare audio and you can know if the problem is produced streaming or in microphone.
If you are using noise suppressor or echo cancelation disable it (this filters could produce problem in few devices)

About video codec parameters. How do you set this parameters?
VideoEncoder should not be related with audio noise and your second parameter is for audio not video and it is already in use.
About OpenGlview, you don't need to change anything to support openglview. You can check my app example and use OpenGl as in the example.

It is from streaming.

I off all options, echo and noise cancellation and also set mono.

in my main activity.kt, calling prepareVidfeo
rtmpCamera2.prepareVideo(
if (isVertical) width else height,
if (isVertical) height else width,
30, bitrate, 3, CameraHelper.getCameraOrientation(this),
MediaCodecInfo.CodecProfileLevel.MPEG4ProfileAdvancedCoding,
MediaCodecInfo.CodecProfileLevel.MPEG4Level6
and i tested AudioObjectType.AAC_MAIN and AAC.LC both in aacpacket.kt
From my testing, audio noise is related with video codec and AudioObjectType.

OpenGLview have noise also..

Would you give some sample code for MicrophoneManagerManual ?
I just use your code, means that I did not change anything, I just use as you coded, thread share or not.
So I set SYNC then more noise is made.

SYNC mode use MicrophoneManagerManual and ASYNC mode MicrophoneManager.
The only difference is that MicrophoneManager is designed to drop frames in a callback automatically after start and MicrophoneManagerManual need call a method that get a frame for you instead of drop it automatically.
Code example:
//Create microphone
    MicrophoneManagerManual microphoneManagerManual = new MicrophoneManagerManual();
    //Configure microphone (you can set parameters if needed)
    microphoneManagerManual.createMicrophone();
    //Start microphone
    microphoneManagerManual.start();

    //Get pcm frames from microphone. This block the thread so you should use a thread for it.
    //Get a frame of default size
    microphoneManagerManual.getInputFrame();
    //Get a frame with a custom size (fill ByteBuffer)
    microphoneManagerManual.read(ByteBuffer, size);
    //Stop microphone
    microphoneManagerManual.stop();

Sorry
I tested again with your OpenGlview and recording 10 minutes.
Some part of recorded content have popcorn noises...

Local record using my library with startRecord method, right?
In this case this is related with MicrophoneManager class, maybe with AudioEncoder but it is really weird.
I think that your microphone device produce that noise maybe related with a configuration.
I recommend you test with other sample rate and using mono channel
Do you have other device to test and discard that you only have problems with one device?

I think yes, I just tested it your app.
sorry I have two android phone for test.

Simple question.

I like to disable auto focus mode in camera2.
can I change aac audio encoder to opus ?
I tired, some part of source modify corresponding to opus. but I could not found all to be modified.

thanks for your helping... thanks

Disable auto focus:
// call it after startpreview
rtmpCamera1.disableAutoFocus();

RTMP doesn't support opus audio codec (page 31):
https://www.adobe.com/content/dam/acom/en/devnet/rtmp/pdf/rtmp_specification_1.0.pdf
1 - Did you test multiple sample rate and mono channel in prepareAudio? Specify prepareAudio configuration (all parameters) tested.
2 - Which devices do you have to test? Let me know both models and API
3 - What do you mean with "I think yes". Did you press start/stop record button in my app example? Check the video in folder:
Android/data/com.pedro.rtpstreamer/files/rtmp-rtsp-stream-client-java

Yes, that is the right place.

samplerate tested

44100
22050

Test Device

Galaxy A40(SM-A405S) / AOS 11 ver
Galaxy S10 5G / AOS 11 ver

Yes, I check as you mentioned folder location. ^^

Question

When encoding time, does decoder involve in encoding process ?
Any idea to make sound more soft ...
As my test experiences, if sound were sharper than more noise is happen.

1 - Decoder is only used in FromFile mode I don't understand you.
2 - I have no more idea. Did you test with my video example to configure stream exactly as I did? It is working for me.
https://github.com/pedroSG94/rtmp-rtsp-stream-client-java/issues/925#issuecomment-921588862

rtmpCamera1.setMicrophoneMode(MicrophoneMode.SYNC);
worked for me.
In some devices, library works good, but in some no-name-brand devices the audio has tick noise.
Changing microphone mode to SYNC fixed the problem.
It wasn't a server side problem.

The main problem here is that I can't reproduce it so If you can report all devices where you have audio noise and server used (include configuration if needed) I can try to get one and fix it.

Closing as inactive


fix(volume) Fix the 'Update Replicas Auto Balance' options typo error

https://github.com/longhorn/longhorn/issues/5154
Signed-off-by: Siye Wang<EMAIL_ADDRESS>

@Mergifyio backport v1.4.x


home page

close: #2

@PhongTaKiai, Could you fix merge conflicts and send a review request?

@mafreud resloved conflicts, thank

@PhongTaKiai Thank you.
@rick1919 UIの確認をお願いします。他のissueもお願いします〜。

@PhongTaKiai @mafreud
Sorry, I missed that.
The UI is LGTM!


Dependancies fix

Fixes #13

Thanks @izziaraffaele! Just to check, what version of node/npm are you using?

Need this fix :)

come one Joe @izziaraffaele rocks, merge it !

Sorry for the late merge and thanks!

yeaaah !

Thanks @stephanedemotte, I just do my best :) BTW I made some changes in this branch https://github.com/izziaraffaele/laravel-elixir-webpack/tree/features which will improve the watch command using webpack watch feature instead of gulp/elixir.
As soon as I find the time to clean it up I'll make a PR but maybe you want to have a look at it already since I know it will improve the workflow of everybody using this package

Nice! When you have it done let me know ;)


Update README.md

I have made a refined and visually appealing version of your FinChart README. I've enhanced the formatting, added more emojis for engagement, and made the content more concise

thank you for your contribution @ashvin2005 !
amazing work


Intialization sample error - ImportError: cannot import name 'AutoregressiveWrapper' from 'zeta.structs'

Created a venv, using python 3.10 on Ubuntu 22.04 LTS
Then, used Installation and Initialization steps from the project.
Initialization step error:
(rt2) student@nuc21:~/rt2$ python test.py
Traceback (most recent call last):
  File "/mnt/LexLinux/student/rt2/test.py", line 2, in <module>
    from rt2.model import RT2
  File "/mnt/LexLinux/student/rt2/lib/python3.10/site-packages/rt2/__init__.py", line 1, in <module>
    from rt2.model import RT2
  File "/mnt/LexLinux/student/rt2/lib/python3.10/site-packages/rt2/model.py", line 3, in <module>
    from zeta.structs import (
ImportError: cannot import name 'AutoregressiveWrapper' from 'zeta.structs' (/mnt/LexLinux/student/rt2/lib/python3.10/site-packages/zeta/structs/__init__.py)
(rt2) student@nuc21:~/rt2$

Test app:
import torch
from rt2.model import RT2

# img: (batch_size, 3, 256, 256)
# caption: (batch_size, 1024)
img = torch.randn(1, 3, 256, 256)
caption = torch.randint(0, 20000, (1, 1024))

# model: RT2
model = RT2()

# Run model on img and caption
output = model(img, caption)
print(output)  # (1, 1024, 20000)

Upvote & Fund

We're using Polar.sh so you can upvote and help fund this issue.
We receive the funding once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog.

I found the 'AutoregressiveWrapper' class in zeta is renamed 'AutoRegressiveWrapper' now. So try to replace 'AutoregressiveWrapper' by 'AutoRegressiveWrapper' in model.py. It works fine for me.

Thanks, that worked


video capture Raspbian Pi3 CV3 array

Hi
Trying to get captures at higher rates, everything works fine with the stills port but when I try the video port, I get blackness
Shorter example I've been working from:
# import the necessary packages
from __future__ import print_function
from imutils.video.pivideostream import PiVideoStream
from imutils.video import FPS
from picamera.array import PiRGBArray
from picamera import PiCamera
import argparse
import imutils
import time
import cv2

# construct the argument parse and parse the arguments
ap = argparse.ArgumentParser()
ap.add_argument("-n", "--num-frames", type=int, default=100,
	help="# of frames to loop over for FPS test")
ap.add_argument("-d", "--display", type=int, default=-1,
	help="Whether or not frames should be displayed")
args = vars(ap.parse_args())

# initialize the camera and stream
camera = PiCamera()
camera.resolution = (320, 240)
camera.framerate = 32
rawCapture = PiRGBArray(camera, size=(320, 240))
stream = camera.capture_continuous(rawCapture, format="bgr",
	use_video_port=True)

# allow the camera to warmup and start the FPS counter
print("[INFO] sampling frames from `picamera` module...")
time.sleep(2.0)
fps = FPS().start()

# loop over some frames
for (i, f) in enumerate(stream):
	# grab the frame from the stream and resize it to have a maximum
	# width of 400 pixels
	frame = f.array
	frame = imutils.resize(frame, width=400)

	# check to see if the frame should be displayed to our screen
	if args["display"] > 0:
		cv2.imshow("Frame", frame)
		key = cv2.waitKey(1) & 0xFF

	# clear the stream in preparation for the next frame and update
	# the FPS counter
	rawCapture.truncate(0)
	fps.update()

	# check to see if the desired number of frames have been reached
	if i == args["num_frames"]:
		break

# stop the timer and display FPS information
fps.stop()
print("[INFO] elasped time: {:.2f}".format(fps.elapsed()))
print("[INFO] approx. FPS: {:.2f}".format(fps.fps()))

# do a bit of cleanup
cv2.destroyAllWindows()
stream.close()
rawCapture.close()
camera.close()

# created a *threaded *video stream, allow the camera sensor to warmup,
# and start the FPS counter
print("[INFO] sampling THREADED frames from `picamera` module...")
vs = PiVideoStream().start()
time.sleep(2.0)
fps = FPS().start()

# loop over some frames...this time using the threaded stream
while fps._numFrames < args["num_frames"]:
	# grab the frame from the threaded video stream and resize it
	# to have a maximum width of 400 pixels
	frame = vs.read()
	frame = imutils.resize(frame, width=400)

	# check to see if the frame should be displayed to our screen
	if args["display"] > 0:
		cv2.imshow("Frame", frame)
		key = cv2.waitKey(1) & 0xFF

	# update the FPS counter
	fps.update()

# stop the timer and display FPS information
fps.stop()
print("[INFO] elasped time: {:.2f}".format(fps.elapsed()))
print("[INFO] approx. FPS: {:.2f}".format(fps.fps()))

# do a bit of cleanup
cv2.destroyAllWindows()
vs.stop()

This is published code that works on other machines.
Thanks
cww

That didn't go well

If you're getting black images from BGR captures via the video-port I'm guessing you're using a recent version of picamera (1.11 or 1.12) but you've got out of date firmware. Try running sudo rpi-update, and once that's finished, reboot (to load the new camera firmware) and try again.
I'm afraid this was one of the trade-offs made in 1.11: faster (simpler) capture pipeline, but broken captures on older firmwares under certain circumstances (including unencoded RGB/BGR over the video port). There's some additional detail here.

Thanks a Lot!
BGR now works with the video port and I’ve got enough FPS to stay ahead of the mechanicals
Curt
From: Dave Jones<EMAIL_ADDRESS>Sent: Saturday, July 30, 2016 3:48 PM
To: waveform80/picamera
Cc: Curt Wuollet; State change
Subject: Re: [waveform80/picamera] video capture Raspbian Pi3 CV3 array (#310)
If you're getting black images from BGR captures via the video-port I'm guessing you're using a recent version of picamera (1.11 or 1.12) but you've got out of date firmware. Try running sudo rpi-update, and once that's finished, reboot (to load the new camera firmware) and try again.
I'm afraid this was one of the trade-offs made in 1.11: faster (simpler) capture pipeline, but broken captures on older firmwares under certain circumstances (including unencoded RGB/BGR over the video port). There's some additional detail herehttps://www.raspberrypi.org/forums/viewtopic.php?p=996888#p996888.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/waveform80/picamera/issues/310#issuecomment-236389161, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ATxRXC6O2QZ8qeUYVXaDnJ412nitnCc5ks5qa7iDgaJpZM4JYfZi.


fix(Tactic/Elementwise): type inference in elementwise

added an optional type argument to SimpType; changed type inference in elementwise tactic
Co-authored-by: Kim Morrison<EMAIL_ADDRESS>

I'll add a test to this before we merge.
This mistake in elementwise was causing it to produces lots of incorrect lemmas. The problem was that we were running inferType on the proof, which often disagrees with the expected type signature of the lemma we are making an auxiliary copy of.

I've added a test.

Sorry, yes, we made the change in simpType when at first we thought we needed a deeper fix. I'll make the suggested changes.

bors merge


Rearrange Examples/LocalDebugging package structure to work with archive plugin

I propose to re-arrange the file and package structure in Examples/LocalDebugging to make it work with the archive plugin.
Motivation:
The current directory and package structure in the Examples/LocalDebugging example does not work out of the box with the archive plugin.
See https://github.com/swift-server/swift-aws-lambda-runtime/issues/276
Modifications:
I re-arranged the package structure to share the same Package.swift for the targets MyLambda and Shared.  This allows the plugin to build and archive MyLamba.  I also made minimum changes to the Xcode workspace to continue to be able to build and debug from Xcode.
Let me know if there is a better way to arrange package and file in this project to work with : Xcode builds, command line builds, and the archive plugin.
Result:
Project now builds with swift build
It runs with  export LOCAL_LAMBDA_SERVER_ENABLED=true  && swift run MyLambda.
It packages with swift package --disable-sandbox archive
It runs by selecting the MyLambda target in Xcode
It runs by selecting the MyApp target in Xcode

somewhat replaced by https://github.com/swift-server/swift-aws-lambda-runtime/pull/292

closing in inactive PRs, feel free to re-open if still relevant


do all the conda stuff at the same time

Codecov Report

Merging #140 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #140   +/-   ##
=======================================
  Coverage   86.54%   86.54%
=======================================
  Files          13       13
  Lines        1977     1977
  Branches      371      371
=======================================
  Hits         1711     1711
  Misses        138      138
  Partials      128      128

Continue to review full report at Codecov.

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


output_clob output

output_clob outputs superflous \n every 255 char

The maximum size of a line is 255 char in Oracle 10gR1 or less and 32767 in 10gR2 and above.
I've narrowed down the problem, not solved, seeking a \n in the text to print and start the next put_line from that \n.
But always a new \n will be output if the line is greater than the limit established in each versio


bugs not always scroll works

Hi again,
I updated from v.0.1.7 to 0.1.9. There are new method destroy. Which is great but there are some problems:

Scroll works not always on mousewheel.
On key press, the section is not entirely scrolled. Need to press twice to scroll a section.
On using destroy method: Uncaught TypeError: Cannot set property '0' of null(anonymous function) @ jquery.scrollify.js:369m.extend.each @ jquery.min.js:2m.fn.m.each @ jquery.min.js:2sizePanels @ jquery.scrollify.js:363(anonymous function) @ jquery.scrollify.js:331

I'm not able to recreate any of these issues. Would you be able to look at the demo site: http://projects.lukehaas.me/scrollify and tell me if you're experiencing points 1 and 2 there?
Also can you tell me which browser and which version of jQuery you're using?

Hi!.
I've the same issue in my web page at http://www.sebuscan.es
To be precise:
The issue appears only when you load the page the first time. The scroll wheel doesn't work and you have to press the down arrow twice. But if you reload the page when your script has added the #1 anchor, all is ok.
The css an js in my page is very simple and I don't know if I'm missing something for scrollify to work.
Thank's (nice plugin)

@interoceto which browser are you seeing this on?

Tested on:
firefox 40.0.3 (ubuntu 14.04 64bits)
firefox 40.0.3 (Win 7 Pro 64bits)
Opera Beta 32.0.1948.19 (Win 7 Pro 64bits)
Chromium 15.0.875.0 (Win 7 Pro 64bits)
IE 9 (Win 7 Pro 64bits)
Same behaviour in all of them. You can reproduce the issue loading http://www.sebuscan.es. The first time the page loads I must press twice the down arrow or move the scrollbar down for the script to work.
Cheers!

@interoceto do you see the same thing happening when you view the demo site?
http://projects.lukehaas.me/scrollify

Hi, lukehaas.
No, your demo site is working ok and this issue is not happening.
I'was looking into your code and I can't see what's the difference with mine so I can't understand why scrollify fails in my site.
Have you tried my site?
Thanks

Hi, I encounter this problem too. @interoceto @lukehaas
I have check http://projects.lukehaas.me/scrollify not having this issue and when I break it down it seem like css issue. When I remove global margin: 0, the site will not able to scroll at the first load without #.
I cheated a way to solve this, which is create a javascript function to load second time. So when scroll not working at the first load, second load will be confirm working.
  if( window.localStorage )
  {
    if( !localStorage.getItem('firstLoad') )
    {
      localStorage['firstLoad'] = true;
      window.location.reload();
    }
    else
      localStorage.removeItem('firstLoad');
  }

Great work there Luke!
I'm a beginner and wanted you to ask how to manage to jump to any given anchor using this script ? I've got a menu on top and want to jump on Click to #contacts for example.
Is it something complicated to do ?
I would appreciate your help !
Kind Regards
Lucas

Issues described here are un-recreatable. Please try updating to the latest version of Scrollify and see if the issues still persist.

Hello, I love Scrollify.js great job! I wanted to say that i had an issue with scrolling myself and I found out why. One of my imported css sheets had a property of overflow-x: hidden !important; that was preventing the scrolling action. I removed this property and now it works without issue. Hope this helps!

Hi!
@Lukehaae: thx for the great script!
I´ve got the same problem (mouse-wheel doesnt work sometimes) and I can reproduce it on http://projects.lukehaas.me/scrollify/examples/pagination/ too (Firefox 49.0.1, Win7). The problem occurs when theres more content than fitting the screen. On the example page -> make the browser small, so the content doesnt fit anymore. The try to use the mousewheel. It works, but you need to scroll a lot to move to the next panel. If you got a lot of content, it seems like nothing hapens at all.
Keyboard arrows work fine.
Best,
Chris

Still flickers even from your sample page http://projects.lukehaas.me/scrollify
(Scroll works not always on mousewheel.
On key press, the section is not entirely scrolled. Need to press twice to scroll a section.)

@webeloper in which browser?

I'm using Firefox 53.0.3 and  Chrome 58.0.3029

+1
This issue is happening for me in a SPA. In some cases, when reinitializing scrollify, I am not able to scroll.

Hi ,
Even I am facing this issue in SPA. Kindly resolve this. Scrolls are getting anchored.

Still not fixed

have to press the key twice  to move to next section.

Same thing, still not fixed

+1
... in chrome when i use a mousewheel


Upgraded to Bootstrap 4.1

Theme uses Bootstrap 4.1 now. I also moved css and js to their own files, so they are easier to edit.

Thanks! I really like the use of the include functionality to split the JS and CSS into their own files. I'd actually love to see just that change as its own PR first, then after that is merged a separate PR to update to Bootstrap 4.1, with before and after screenshots of the visible changes (if any). Right now it's a pretty big PR with no clear advantage to update to the newer Bootstrap, yet it's a bunch of changes that I am not familiar with... So splitting up this PR into smaller pieces would be nicer I think.
It also seems unnecessary that this PR modifies package.json and package-lock.json?

I will submit PR for the splitting first. :)
And yeah there is no reason really for package.json edit, it was just for me to see decencies more easily.


Adding a start/stop mode to terminate instances as required without waiting for 60 minutes to TTL to expire.

There should be a start/stop mode for starting the instance when required and stoppping it when its job is done. TTL is good but it won't be useful if my job is done in 5 minutes why would I pay for the rest of 55 minutes as 1 minute is minimum charge per-instance. Please look into this asap, then this action will be unbeatable.

Instances are supposed to terminate about 60 seconds after job completion (failure or success). The 60 seconds grace-period is to give the code a chance for calling GH API in order to perform necessary cleanups.
Are you saying instances stay around after a job has completed ?

      `echo "shutdown -P +1" > $CURRENT_PATH/shutdown_script.sh`,
      "chmod +x $CURRENT_PATH/shutdown_script.sh",
      `echo "./config.sh remove --token ${runnerRegistrationToken.token} || true" > $CURRENT_PATH/shutdown_now_script.sh`,
      `echo "shutdown -h now" > $CURRENT_PATH/shutdown_now_script.sh`,
      "chmod +x $CURRENT_PATH/shutdown_now_script.sh",
      "export ACTIONS_RUNNER_HOOK_JOB_COMPLETED=$CURRENT_PATH/shutdown_script.sh",

The code above is part of our startup cloud-init script.

It creates a shutdown script and then uses ACTIONS_RUNNER_HOOK_JOB_COMPLETED to make sure it is executed once a job finishes.
We also have github_job_start_ttl_seconds which defines how long an instance is allowed to stay idle before a job is executed
Finally we have the instance TTL which would execute if the two options above both fail for any reason.
I just tested with a job which had an error intentionally introduced to make it fail. Exactly 1 minute after failure the instance was terminated.

Do you have an example of a workflow which could trigger a different type of failure ?

Yes, This works, Thank you so much, I will use this in my workflow.


Clock-Timer: disabling a rule by unselecting all weekdays reenables all weekdays

Describe the bug
Disabling a rule by unselecting all weekdays reenables all weekdays.
Expected behavior
The rule should be disabled.
System information (please complete the following information):

Node Version 1.2.4
Node-Red Version: 2.3.1

Additional context
As a workaround to debug a rule, I need to uncomment the current month

This is not a common way for disabling a rule.
It is a consciously wanted behavior that is chosen every day.
One way for disabling rules will be to add a condition which will never be true.
I will think about an other way for disable rules.

implemented rule enable/disable in 2.0.3


First stab at ignoring dirty specs

Per the last paragraph of https://github.com/domfarolino/specfmt/issues/3, I wanted to make the tool refuse to run on specs that have uncommitted changes, just in case the tool ever gets a bug where rewrapping gets screwed up and the author actually loses valuable spec changes that haven't been committed.
If this is too tedious to use and we're confident that there are no bugs of the sort mentioned above, maybe we can remove this, but in the early stages it seems safe to stick with.

@jyasskin You probably know the most about Path stuff, could you take a look? GitHub won't let me add you as a reviewer just yet...


[Snyk] Security upgrade @backstage/plugin-catalog from 0.0.0-use.local to 0.1.1

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):

plugins/catalog-customized/package.json

Note for zero-installs users
If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Cross-site Scripting (XSS) SNYK-JS-ROLLUP-8073097
  109

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Cross-site Scripting (XSS)

🎉 Snyk hasn't found any issues so far.
✅ code/snyk check is completed. No issues were found. (View Details)


Decimal to Binary in HTML CSS JS

Decimal to Binary in HTML CSS JS

This is a HacktoberFest-21 PR! Kindly assign it to me.


add request subclass specs

VmCloudReconfigureRequest and vm_migrate_request and configured_system_request are missing specs, these are the three from https://github.com/ManageIQ/manageiq/issues/19771.
@gmcculloug or @tinaafitz please review, or anyone, I guess
@miq-bot add_label test, technical debt

anyone want to please review this?

anyone, ping?

@tinaafitz please?

anyone else want to look at this?

anyone else want to look at this?

could i please get someone to review this?


(feature) Request body logging

Requirements
In order to properly debug request body/evaluation context is needed.

/assign-me


Failed to build on Windows in GitHub Actions.

Describe the bug
Failed to build on Windows in GitHub Actions.
Error messages:
  --- stderr
  thread 'main' panicked at C:\Users\runneradmin\.cargo\registry\src\index.crates.io-6f17d22bba15001f\ckb-vm-0.24.6\build.rs:51:17:
  Command["yasm" "-p" "gas" "-f" "x64" "-m" "amd64" "REPO_PATH\\target\\debug\\build\\ckb-vm-e4c77d8be0c21cb5\\out\\execute_x64-expanded.S" "-o" "REPO_PATH\\target\\debug\\build\\ckb-vm-e4c77d8be0c21cb5\\out\\execute_x64.o"] exits with non-success status: ExitStatus(ExitStatus(3221225781))

I know there is a new release (0.24.9), but:

I didn't find a fix for this issue in the change log.
I couldn't set the version, because it was introduced through dependencies (ckb-testtool).

p.s. I tried 3 times to make sure it's a deterministic failure.
Environment

OS: windows-latest in GitHub Actions
Version: ckb-vm v0.24.6
Rust Toolchain: 1.76.0
LLVM installation commands:   - name: Install LLVM on Windows
     if: matrix.os == 'windows-latest'
     shell: pwsh
     run: |
       iex "& {$(irm get.scoop.sh)} -RunAsAdmin"
       scoop install llvm yasm
       echo "$env:USERPROFILE\scoop\shims" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append

The cause of the problem is a bug of yasm, we cannot fix this but can bypass it. You can use windows-2019, in this way, ckb-vm can be compiled correctly.
See also: https://github.com/nervosnetwork/ckb-vm/pull/256


Resource depletion

If there are multiple things being consumed by to produce something, 1 of the resources can be totally depleted and the rate of production is only slightly affected if the others have sufficient in the stockpile.
Lots of the code in the JSON branch changes things to do with resources, so probably a good idea to wait until that brach is merged before working on this issue.

Also the rate that parties starve should probably not use the rate that it would normally produce units, but maybe the normal food consumption instead. (I believe taskCosts[task][getResIndex("food")]) would do it. Again, may be best to wait until json code merged.

I believe this is related with #86

Seems that this is not a problem currently, will reopen if otherwise


proposal: os/exec: allow user of CommandContext to specify the kill signal when context is done

What version of Go are you using (go version)?
go version go1.8.3 linux/amd64

Currently, process started from exec.CommandContext will be killed by SIGKILL when the context is done before the process finished. But in some cases, the process should be allow a chance to clean up then exit cleanly ( by received an expected signal like SIGTERM for example). We received a similar request in https://github.com/containerd/go-runc/issues/21

Sounds like a feature request, I'll triage this for Go1.10.
/cc @bradfitz @ianlancetaylor.

In regards to the design, I can see perhaps adding a field to *exec.Cmd
Cmd struct {
   KillSignal os.Signal
}

or better, making a method
func (c *Cmd) SetKillSignal(signal os.Signal) {
     c.sigmu.Lock()
     c.killSignal = &signal
     c.sigmu.Unlock()
}

and then for implementation we can do something altogether like this
diff --git a/src/os/exec/exec.go b/src/os/exec/exec.go
index 893d8ee..9c541d2 100644
--- a/src/os/exec/exec.go
+++ b/src/os/exec/exec.go
@@ -113,6 +113,9 @@ type Cmd struct {
 	// available after a call to Wait or Run.
 	ProcessState *os.ProcessState

+	sigMu      sync.RWMutex // sigMu protects killSignal
+	killSignal *os.Signal
+
 	ctx             context.Context // nil means none
 	lookPathErr     error           // LookPath error, if any.
 	finished        bool            // when Wait was called
@@ -386,7 +389,14 @@ func (c *Cmd) Start() error {
 		go func() {
 			select {
 			case <-c.ctx.Done():
-				c.Process.Kill()
+				c.sigMu.RLock()
+				sig := c.killSignal
+				c.sigMu.RUnlock()
+				if sig == nil {
+					c.Process.Kill()
+				} else {
+					c.Process.Signal(*sig)
+				}
 			case <-c.waitDone:
 			}
 		}()
@@ -395,6 +405,14 @@ func (c *Cmd) Start() error {
 	return nil
 }

+func (c *Cmd) SetKillSignal(sig os.Signal) {
+	c.sigMu.Lock()
+	cpSig := new(os.Signal)
+	*cpSig = sig
+	c.killSignal = cpSig
+	c.sigMu.Unlock()
+}
+
 // An ExitError reports an unsuccessful exit by a command.
 type ExitError struct {
 	*os.ProcessState

However, am not so sure if this design will be cross platform. Some signals differ between Windows and the *NIXes, so I'll defer to @ianlancetaylor to advise me on that.

/cc @bradfitz
It's not clear to me that CommandContext needed to be in os/exec to begin with. You can certainly build other signaling semantics on top of os/exec without it. It's unclear we should embellish this one instead of just encouraging people to do other things (like SIGTERM, sleep 5 seconds, then SIGKILL) with code in other packages.

Maybe not but I sure do appreciate it now that we have it. Recent example: https://twitter.com/bradfitz/status/883357040919232512
I would've risked leaking processes otherwise, or it would've been tediously long.

yah, having os/exec handled context for you is certainly very convenient, but I think @rsc is also quite right that most of the time if user want to handle terminating the process gracefully, adding the custom signal alone probably wont be enough, you probably want to SIGTERM, timeout, then SIGKILL.

Handle this behaviour out of os/exec, probably with some pseudo-code like this:

cmd := exec.Command("sleep", "10")
cmd.Start()
waitDone := make(chan struct{})
go func() {
	select {
	case <-ctx.Done():
		cmd.Process.Signal(syscall.SIGTERM)
		select {
		case <-time.After(time.Second):
			cmd.Process.Kill()
		case <-waitDone:
		}
	case <-waitDone:
	}
}()
cmd.Wait()
close(waitDone)

Instead of adding the custom signal, adding a callback to let user specify custom behavior

cmd := exec.CommandContext(ctx, "sleep", "10")
// reuse waitDone in exec.Cmd
cmd.ContextDone = func(p *os.Process, waitDone <-chan struct{}) {
	p.Signal(syscall.SIGTERM)
	select {
	case <-time.After(time.Second):
		p.Kill()
	case <-waitDone:
	}
}
cmd.Start()
cmd.Wait()

c.waitDone = make(chan struct{})
go func() {
	select {
	case <-c.ctx.Done():
		if c.ContextDone == nil {
			c.Process.Kill()
		} else {
			c.ContextDone(c.Process, c.waitDone)
		}
	case <-c.waitDone:
	}
}()

you probably want to SIGTERM, timeout, then SIGKILL

When we cancel a context.Context, we do not follow up by terminating the process running the goroutine. Why do assume clean, responsive terminations within the process but not in subprocesses?
Just changing the signal should work fine for well-behaved programs, and it is up to the caller to decide whether the program they are executing is likely to be well-behaved.

OK, well, ignoring the fact that the CommandContext ship has sailed, the rest of what I wrote still applies:

You can certainly build other signaling semantics on top of os/exec without it. It's unclear we should embellish this one instead of just encouraging people to do other things (like SIGTERM, sleep 5 seconds, then SIGKILL) with code in other packages.

If you want a custom signal it's still easy to build outside of the standard library. Is there enough demand for putting this in the standard library? It doesn't sound like it.

Could you add a method to set a signal on the context using the Value() methods?
func ContextSignal(ctx context.Context, sig os.Signal) context.Context { }

ctx = exec.ContextSignal(ctx, unix.SIGTERM)
cmd := exec.CommandContext(ctx, ...)

There still has been no clear signal of demand that forces this into the standard library (no responses to my comment from Aug 28 above). Let's let this functionality be provided by packages outside the standard library for now.

Would be nice :)

Closed proposal but am just directing demand here as https://github.com/golang/go/issues/22757 has just been opened and seems like a subset of this issue.


[WIP] Adds support for waypoints

Adds a new field waypoints to GPXTrack with a list of waypoints. These consist of a reduced / relevant set of attributes (coordinate, time, name, description, and comment) each.

Mention in readme.md is missing

Should parsed waypoints also be exported? I would expect it.

Yes, export should be implemented


ClusterIssuer/Issuer failed for domain > 64 char. CSR doesn't contain a SAN short enough to fit in CN

Describe the bug:
ClusterIssuer is unable to generate certificate due to Order error:
Failed to finalize Order: 400 urn:ietf:params:acme:error:badCSR: Error finalizing order :: issuing precertificate: CSR doesn't contain a SAN short enough to fit in CN
Expected behaviour:
Certificate generated.
Steps to reproduce the bug:
Use ClusterIssuer/Issuer to generate a Certificate for a FQDN longer than 64 chars with Acme (letsencrypt).
API Version:  acme.cert-manager.io/v1alpha3
Kind:         Order
....
Status:
  Failure Time:  2020-04-09T16:47:02Z
  Finalize URL:  https://acme-staging-v02.api.letsencrypt.org/acme/finalize/13088958/84103314
  Reason:        Failed to finalize Order: 400 urn:ietf:params:acme:error:badCSR: Error finalizing order :: issuing precertificate: CSR doesn't contain a SAN short enough to fit in CN
  State:         errored
  URL:           https://acme-staging-v02.api.letsencrypt.org/acme/order/13088958/84103314

Environment details::

Kubernetes version (e.g. v1.10.2): 1.15.9-gke.24
Cloud-provider/provisioner (e.g. GKE, kops AWS, etc): GKE
cert-manager version (e.g. v0.4.0): 0.14.1
Install method (e.g. helm or static manifests): helm

/kind bug

I think this is an issue with Let's Encrypt rather than cert-manager as cert-manager does not set the CN in the CSR. Let's Encrypt does that on their side, which is where this error comes from.

Yes, i just realized that.
I solved the limitation by using wildcard subdomain certificate.
Thanks @meyskens. I'm closing this one.

For a LE discussion about this issue see https://github.com/certbot/certbot/issues/1915.


Update JBrowse on usegalaxy.org

The version in #285 wasn't the latest for some reason.

@galaxybot test this

@galaxybot deploy this


Infura returning 403s for L2s like Polygon because of problem with dev key

How did you solve it？

Continuing at #5557


FileUtility - Checks if destination folder exists, then creates one if it doesn't

Unity would throw an IO exception if I tried to copy my $BUILDPATH to another folder if the destination had a path like: C:/path to my google drive/game builds/$PRODUCT_NAME-$VERSION/$ARCHITECTURE. Builds would work as expected without the nested folder.
Adding a check that the folder exists before trying the copy, and creating it if it doesn't, prevents the exception for me and made the build action work as I expected, so I thought I would share.

Thanks for pointing out the bug and submitting a fix. I made a minor change that prevents every file copy/move from looking like an overwrite - not that it really matters at this point anyway because there isn't currently an overwrite option presented to the user.


Change logging default value to be error

Change logging default value to match the one used by pyensight, so that scripts that use both pydynamicreporting and pyensight do not run into unexpected outputs as the logging level is overwritten.

We're currently processing your upload.  This comment will be updated when the results are available.


Error running "vagrant up cd"

I am running vagrant 1.8.5 on a Mac.
I get this error when running vagrant up in the ms-lifecycle directory.
The machine with the name 'core-01' was not found configured for
this Vagrant environment.

This is not an issue with ms-lifecycle. I am new to vagrant. I found the command:
vagrant global-status and  found the core-01 machine.   It took awhile but I was able to find the command: vagrant global-status --prune which cleaned up my environment in some way. After that I was able to use vagrant up.


React Group Project

Hi,
Here, Me and @KanzaTahreem have set up the Kanban board and assigned actions accordingly.
There are just two of us in the group.
Here is the Link to the project.
Kind regards.

Hi @Alhajideen and @KanzaTahreem ,
Good job so far!
There are some issues that you still need to work on to go to the next project but you are almost there!
Highlights
✔  Good design
✔  Good PR and Description
Required Changes ♻

[ ] Kindly ensure you have added all the required cards for this project, you are missing one card for displaying reserved rockets in your profile

Check the comments under the review.
Optional suggestions
Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

_As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

STATUS: APPROVED 🍾✔🎉
Hello @danmainah and @KanzaTahreem 👋
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉
Highlights

You documented your work professionally.✔
You asked for the changes in a polite and friendly way.

Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


perf: remove workspace dependancy from iris-grid-panel and memoize settings redux selector

Discovered as part of #1977 investigation. Typing in a notebook triggers a workspace update, which was triggering all tables to re-render. Removed deprecated dependeny of workspace from iris-grid.
Further settings is derived from workspace and returns a new settings object. Iris-grid depends on settings, but the object had no changes. Memoize the selector so it always returns the same object if settings haven't changed.
Removes ~100ms of lag that was occuring 400ms after the debounce of notebook key press events.
BREAKING CHANGE: getPluginContent deprecatedProps have been removed from iris-grid

Was this tested with enterprise table plugins? I think it would break any customers using table plugins


what happen？

Describe the bug
Error when using sourcemap for reporting an error: Can't resolve original location of error.
✓ 3978 modules transformed.
'default' is not exported by polyfill-node.buffer.js, imported by node_modules/readable-stream/lib/internal/streams/buffer_list.js
file: D:/project/hhhhhhhh/web/vite-hash/node_modules/readable-stream/lib/internal/streams/buffer_list.js:3:7
1: import * as commonjsHelpers from "commonjsHelpers.js";
2: import "\u0000buffer?commonjs-require";
3: import require$$0 from "\u0000buffer?commonjs-proxy";
^
4: import "\u0000util?commonjs-require";
5: import require$$1 from "\u0000util?commonjs-proxy";
error during build:
Error: 'default' is not exported by polyfill-node.buffer.js, imported by node_modules/readable-stream/lib/internal/streams/buffer_list.js
at error (D:\project\hhhhhhhh\web\vite-hash\node_modules\rollup\dist\shared\rollup.js:198:30)
at Module.error (D:\project\hhhhhhhh\web\vite-hash\node_modules\rollup\dist\shared\rollup.js:12560:16)
at Module.traceVariable (D:\project\hhhhhhhh\web\vite-hash\node_modules\rollup\dist\shared\rollup.js:12919:29)
at ModuleScope.findVariable (D:\project\hhhhhhhh\web\vite-hash\node_modules\rollup\dist\shared\rollup.js:11571:39)
at Identifier.bind (D:\project\hhhhhhhh\web\vite-hash\node_modules\rollup\dist\shared\rollup.js:7570:40)
at VariableDeclarator.bind (D:\project\hhhhhhhh\web\vite-hash\node_modules\rollup\dist\shared\rollup.js:5400:23)
at VariableDeclaration.bind (D:\project\hhhhhhhh\web\vite-hash\node_modules\rollup\dist\shared\rollup.js:5396:73)
at Program.bind (D:\project\hhhhhhhh\web\vite-hash\node_modules\rollup\dist\shared\rollup.js:5396:73)
at Module.bindReferences (D:\project\hhhhhhhh\web\vite-hash\node_modules\rollup\dist\shared\rollup.js:12556:18)
at Graph.sortModules (D:\project\hhhhhhhh\web\vite-hash\node_modules\rollup\dist\shared\rollup.js:23162:20)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Reproduction
n
System Info
window10

Used Package Manager
yarn
Logs
NO have
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Please provide a minimal reproduction to reproduce the issue.


work on ha docker version

this have docker image ?
dockerfile need cross-compile for armv8?
and it have different from timescale/timescaledb:latest-pg14 in docker hub?

Hi @0neday
What are you trying to accomplish?
The docker images are on dockerhub., but are automatically pulled by Home Assistant when needed.
Does that answer your question?


#130 Add noPrefix option, removing leading dash from class names when using an empty prefix

As pointed out in #130, using an empty prefix when initializing the autocomplete will cause all nested elements to have a leading dash in their class names. This PR fixes this bug with a noPrefix option, as proposed.

Coverage decreased (-0.06%) to 88.876% when pulling 77dcaf17e06292c8670f3ce170dbdba1129245ce on Tom-Bonnike:master into 3b7d6f06b7090a439931fc41aff5164aeabe6d00 on algolia:master.

LGTM, any blocker @redox?

@Tom-Bonnike Sorry I had to revert this, it seems to have broken the hint feature.
Can you check it again?
yarn dev
# go to http://localhost:8888/test/playground.html, activate hint: true on contacts2, remove appendTo, hint is not working

Discovered this because the integration tests failed. Sorry I missed that in the original PR>

Oh sorry! I will. Probably next week though, as I don't have access to a computer atm.

See #159


fix: LSDV-5031: Adding new region after filter it is not filtered

PR fulfills these requirements

[X] Commit message(s) and PR title follows the format [fix|feat|ci|chore|doc]: TICKET-ID: Short description of change made ex. fix: DEV-XXXX: Removed inconsistent code usage causing intermittent errors
[ ] Tests for the changes have been added/updated (for bug fixes/features)
[ ] Docs have been added/updated (for bug fixes/features)
[X] Best efforts were made to ensure docs/code are concise and coherent (checked for spelling/grammatical errors, commented out code, debug logs etc.)
[X] Self-reviewed and ran all changes on a local instance (for bug fixes/features)

Change has impacts in these area(s)
(check all that apply)

[ ] Product design
[X] Frontend

Describe the reason for change
When filtering and then adding regions the new regions would not appear in the outliner
What does this fix?
This clears out the filter when it is empty so that new additions will be included
What is the new behavior?
The filters is applied to new regions and when deleted it is applied to none
What is the current behavior?
The filter becomes a list of all the regions when deleted which does not include new additions
What libraries were added/updated?
none
Does this change affect performance?
no
Does this change affect security?
no
What alternative approaches were there?
no
What feature flags were used to cover this change?
none
Does this PR introduce a breaking change?
(check only one)

[ ] Yes, and covered entirely by feature flag(s)
[ ] Yes, and covered partially by feature flag(s)
[X] No
[ ] Not sure (briefly explain the situation below)

What level of testing was included in the change?
(check all that apply)

[ ] e2e
[ ] integration
[ ] unit

Which logical domain(s) does this change affect?
Regions filters in the outliner

Codecov Report
Patch coverage has no change and project coverage change: -0.02 :warning:

Comparison is base (32c3ef4) 64.93% compared to head (ffda7fb) 64.92%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1352      +/-   ##
==========================================
- Coverage   64.93%   64.92%   -0.02%
==========================================
  Files         436      436
  Lines       27133    27136       +3
  Branches     7150     7153       +3
==========================================
- Hits        17619    17617       -2
- Misses       8187     8189       +2
- Partials     1327     1330       +3

Impacted Files
Coverage Δ

src/components/Filter/Filter.tsx
97.14% <0.00%> (ø)

src/stores/RegionStore.js
63.54% <0.00%> (-0.63%)
:arrow_down:

... and 1 file with indirect coverage changes

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

/git merge master


Add parameter osc_freq in tests and in tutorial

Summary
In the previous version, all tests ignored osc_freq.
Details and comments
This is a response to issue #176.

Ready for review.

Can we call this just freq?
For example, in resonance analysis
https://github.com/Qiskit/qiskit-experiments/blob/70d9b487dafe78dd9192647af623994fd2f36698/qiskit_experiments/characterization/resonance_analysis.py#L85

Regarding your comment, @nkanazawa1989 , I would rather leave it as osc_freq because f or freq is used for the the fitted frequency. I improved the explanation in the tutorial. It would be great if you could look at the explanation and see if it is correct and clear enough.

@yael, here are responses to your long comment - for some reason I could not answer directly below yours.

I didn't get an answer on what the users expect. For now, I wrote a better explanation at the beginning of the tutorial, so I hope that will suffice. We can change later, if we get such feedback.
Results on the devices are not as nice. It could be that my parameters need more tuning.
See my answer on 1.
Removed the word guess from all parameter names.
I fixed the values of 'osc_freq and 'f as you pointed out.
See 1.
I couldn't find this - I probably corrected it previously.
Added osc_freq to all examples.

@chriseclectic , I believe this PR is in the category of bug fixes, so should be included in the release. Please review and merge.

circuits() looks right to me with the recent changes. Here are a few more comments I had from reading over the docstrings:

The units of osc_freq should be noted in the __init__ docstring
In the circuits() docstring, I would rephrase "a fixed delay, a phase gate (with a linear phase)..." to "a delay, a phase gate (with phase proportional to the delay..." (any individual delay gate is fixed but the delay is being varied across circuits).
In the __init__ docstring, \lambda =2 \pi \times {osc\_freq} should be something like \lambda =2 \pi \times {osc\_freq} \times {delay}.

The units of osc_freq should be noted in the init docstring

Agreed, and it should be Hz.


Support path (*.pth) files in extra paths

I'm using PDM to develop Python projects. It has a really nice feature where instead of installing the dependencies in __pypackages__ directly, it installs them in a cache folder, and writes .pth files pointing to them in __pypackages__. It allows deduplication across projects, which saves a tremendous amount of disk-space, and also makes installs faster.
To work with PDM+VSCode, I use this configuration: https://pdm.fming.dev/#vscode
{
  "python.autoComplete.extraPaths": ["__pypackages__/<major.minor>/lib"],
  "python.analysis.extraPaths": ["__pypackages__/<major.minor>/lib"]
}

However it seems that VSCode does not follow the .pth files, which really are just text files containing the path to the actual source file(s) on a single line:
% cat __pypackages__/3.9/lib/toml.pth
/home/pawamoy/.cache/pdm/packages/toml-0.10.2-py2.py3-none-any/lib

% tree -L 2 /home/pawamoy/.cache/pdm/packages/toml-0.10.2-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/toml-0.10.2-py2.py3-none-any/lib
├── toml
│   ├── decoder.py
│   ├── encoder.py
│   ├── __init__.py
│   ├── ordered.py
│   ├── __pycache__
│   └── tz.py
└── toml-0.10.2.dist-info
    ├── INSTALLER
    ├── LICENSE
    ├── METADATA
    ├── RECORD
    ├── top_level.txt
    └── WHEEL

3 directories, 11 files

I'd like VSCode to follow those .pth files to actually make autoComplete and analysis extra paths work.
If I understand correctly, a .pth file can contain comments starting with #, and an arbitrary number of paths (relative or absolute) separated by new lines:
# a comment
# another comment
a/relative/path
/an/absolute/path

See https://docs.python.org/3/library/site.html.

Firstly, we don't currently support __pypackages__ (#1441).
We do support .pth files, but not in extraPaths. They're currently only supported when you have an interpreter selected (so Python itself executes these files via the site module), or limited support when using the venvPath option.
To be clear, you're looking for us to try and scan directories in extraPaths for .pth files, and then use them?

Hmmmmm. Then it's strange: it should already work, here is why.
PDM offers a command that outputs shell commands to automatically enable PEP582 for the Python interpreter.
% pdm --pep582
if [ -n "$PYTHONPATH" ]; then
    export PYTHONPATH='/home/pawamoy/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/pep582':$PYTHONPATH
else
    export PYTHONPATH='/home/pawamoy/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/pep582'
fi

My shell runs these commands at each startup. So my PYTHONPATH is always at least:
% echo $PYTHONPATH
/home/pawamoy/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/pep582

This folder has a sitecustomize.py, which if I understand correctly gets executed each time Python starts up. I don't understand all of it, but I guess it simply adds the right <major.minor> folder of __pypackages__ to sys.path (if __pypackages__ exists in the current working directory, or a certain number of directories above). See its code here: https://github.com/pdm-project/pdm/blob/main/pdm/pep582/sitecustomize.py
Eventually, it makes my Python interpreter able to find packages under __pypackages__ and under PDM's cache folder:
% python -c "import sys; print('\n'.join(sys.path))"

/home/pawamoy/.basher-packages/pyenv/pyenv/versions/3.9.5/lib/python39.zip
/home/pawamoy/.basher-packages/pyenv/pyenv/versions/3.9.5/lib/python3.9
/home/pawamoy/.basher-packages/pyenv/pyenv/versions/3.9.5/lib/python3.9/lib-dynload
/media/data/dev/python/duty/__pypackages__/3.9/lib
/home/pawamoy/.cache/pdm/packages/ansimarkup-1.5.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/appdirs-1.4.4-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/astor-0.8.1-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/attrs-21.2.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/autoflake-1.4-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/bandit-1.7.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/black-20.8b1-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/certifi-2021.5.30-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/charset_normalizer-2.0.4-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/click-8.0.1-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/colorama-0.4.4-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/coverage-5.5-cp39-cp39-manylinux2010_x86_64/lib
/home/pawamoy/.cache/pdm/packages/darglint-1.8.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/dparse-0.5.1-py3-none-any/lib
/media/data/dev/python/duty/src
/home/pawamoy/.cache/pdm/packages/execnet-1.9.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/failprint-0.8.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/flake8-3.9.2-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/flake8_bandit-2.1.2-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/flake8_black-0.2.3-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/flake8_bugbear-21.4.3-py36.py37.py38-none-any/lib
/home/pawamoy/.cache/pdm/packages/flake8_builtins-1.5.3-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/flake8_comprehensions-3.5.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/flake8_docstrings-1.6.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/flake8_plugin_utils-1.3.2-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/flake8_polyfill-1.0.2-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/flake8_pytest_style-1.5.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/flake8_string_format-0.3.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/flake8_tidy_imports-4.3.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/flake8_variables_names-0.0.4-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/ghp_import-2.0.1-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/git_changelog-0.4.2-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/gitdb-4.0.7-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/GitPython-3.1.20-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/idna-3.2-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/importlib_metadata-4.6.3-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/iniconfig-1.1.1-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/isort-5.8.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/Jinja2-2.11.3-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/Markdown-3.3.4-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/MarkupSafe-2.0.1-cp39-cp39-manylinux2010_x86_64/lib
/home/pawamoy/.cache/pdm/packages/mccabe-0.6.1-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/mergedeep-1.3.4-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/mkdocs-1.2.2-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/mkdocs_autorefs-0.2.1-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/mkdocs_coverage-0.2.4-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/mkdocs_gen_files-0.3.3-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/mkdocs_literate_nav-0.4.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/mkdocs_material-7.2.2-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/mkdocs_material_extensions-1.0.1-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/mkdocstrings-0.15.2-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/mypy-0.910-cp39-cp39-manylinux2010_x86_64/lib
/home/pawamoy/.cache/pdm/packages/mypy_extensions-0.4.3-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/packaging-21.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pathspec-0.9.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pbr-5.6.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pep8_naming-0.12.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pluggy-0.13.1-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/poetry_semver-0.1.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/ptyprocess-0.7.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/py-1.10.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pycodestyle-2.7.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pydocstyle-6.1.1-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pyflakes-2.3.1-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/Pygments-2.9.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pymdown_extensions-8.2-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pyparsing-2.4.7-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pytest-6.2.4-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pytest_cov-2.12.1-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pytest_forked-1.3.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pytest_randomly-3.8.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pytest_sugar-0.9.4-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pytest_xdist-2.3.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/python_dateutil-2.8.2-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pytkdocs-0.11.1-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/PyYAML-5.4.1-cp39-cp39-manylinux1_x86_64/lib
/home/pawamoy/.cache/pdm/packages/pyyaml_env_tag-0.1-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/regex-2021.8.3-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64/lib
/home/pawamoy/.cache/pdm/packages/requests-2.26.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/safety-1.10.3-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/setuptools-57.4.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/six-1.16.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/skjold-0.3.2-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/smmap-4.0.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/snowballstemmer-2.1.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/stevedore-3.3.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/termcolor-1.1.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/toml-0.10.2-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/typed_ast-1.4.3-cp39-cp39-manylinux1_x86_64/lib
/home/pawamoy/.cache/pdm/packages/typing_extensions-<IP_ADDRESS>-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/urllib3-1.26.6-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/watchdog-2.1.3-py3-none-manylinux2014_x86_64/lib
/home/pawamoy/.cache/pdm/packages/wps_light-0.15.2-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/zipp-3.5.0-py3-none-any/lib
/home/pawamoy/.local/lib/python3.9/site-packages
/home/pawamoy/.basher-packages/pyenv/pyenv/versions/3.9.5/lib/python3.9/site-packages

Now, since I run VSCode using the same system user, and since VSCode seems to start Python process in my user's default shell (currently Zsh), all this machinery is enabled in VSCode as well. Indeed, if I select my system Python as the interpreter, and I run the following file using the following run configuration:
import sys

print("\n".join(sys.path))

        {
            "name": "Python: Current File",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal"
        }

It prints the same paths, except for some of them which are now the system paths instead of the pyenv ones:
%  cd /media/data/dev/python/duty ; /usr/bin/env /usr/bin/python /home/pawamoy/.vscode/extensions/ms-python.python-2021.8.1147840270/pythonFiles/lib/python/debugpy/launcher 43833 -- /media/data/dev/python/duty/pathfiles.py
/media/data/dev/python/duty
/usr/lib/python39.zip
/usr/lib/python3.9
/usr/lib/python3.9/lib-dynload
/media/data/dev/python/duty/__pypackages__/3.9/lib
/home/pawamoy/.cache/pdm/packages/ansimarkup-1.5.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/appdirs-1.4.4-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/astor-0.8.1-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/attrs-21.2.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/autoflake-1.4-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/bandit-1.7.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/black-20.8b1-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/certifi-2021.5.30-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/charset_normalizer-2.0.4-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/click-8.0.1-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/colorama-0.4.4-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/coverage-5.5-cp39-cp39-manylinux2010_x86_64/lib
/home/pawamoy/.cache/pdm/packages/darglint-1.8.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/dparse-0.5.1-py3-none-any/lib
/media/data/dev/python/duty/src
/home/pawamoy/.cache/pdm/packages/execnet-1.9.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/failprint-0.8.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/flake8-3.9.2-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/flake8_bandit-2.1.2-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/flake8_black-0.2.3-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/flake8_bugbear-21.4.3-py36.py37.py38-none-any/lib
/home/pawamoy/.cache/pdm/packages/flake8_builtins-1.5.3-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/flake8_comprehensions-3.5.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/flake8_docstrings-1.6.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/flake8_plugin_utils-1.3.2-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/flake8_polyfill-1.0.2-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/flake8_pytest_style-1.5.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/flake8_string_format-0.3.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/flake8_tidy_imports-4.3.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/flake8_variables_names-0.0.4-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/ghp_import-2.0.1-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/git_changelog-0.4.2-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/gitdb-4.0.7-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/GitPython-3.1.20-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/idna-3.2-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/importlib_metadata-4.6.3-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/iniconfig-1.1.1-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/isort-5.8.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/Jinja2-2.11.3-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/Markdown-3.3.4-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/MarkupSafe-2.0.1-cp39-cp39-manylinux2010_x86_64/lib
/home/pawamoy/.cache/pdm/packages/mccabe-0.6.1-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/mergedeep-1.3.4-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/mkdocs-1.2.2-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/mkdocs_autorefs-0.2.1-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/mkdocs_coverage-0.2.4-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/mkdocs_gen_files-0.3.3-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/mkdocs_literate_nav-0.4.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/mkdocs_material-7.2.2-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/mkdocs_material_extensions-1.0.1-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/mkdocstrings-0.15.2-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/mypy-0.910-cp39-cp39-manylinux2010_x86_64/lib
/home/pawamoy/.cache/pdm/packages/mypy_extensions-0.4.3-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/packaging-21.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pathspec-0.9.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pbr-5.6.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pep8_naming-0.12.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pluggy-0.13.1-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/poetry_semver-0.1.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/ptyprocess-0.7.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/py-1.10.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pycodestyle-2.7.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pydocstyle-6.1.1-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pyflakes-2.3.1-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/Pygments-2.9.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pymdown_extensions-8.2-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pyparsing-2.4.7-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pytest-6.2.4-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pytest_cov-2.12.1-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pytest_forked-1.3.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pytest_randomly-3.8.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pytest_sugar-0.9.4-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pytest_xdist-2.3.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/python_dateutil-2.8.2-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/pytkdocs-0.11.1-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/PyYAML-5.4.1-cp39-cp39-manylinux1_x86_64/lib
/home/pawamoy/.cache/pdm/packages/pyyaml_env_tag-0.1-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/regex-2021.8.3-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64/lib
/home/pawamoy/.cache/pdm/packages/requests-2.26.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/safety-1.10.3-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/setuptools-57.4.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/six-1.16.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/skjold-0.3.2-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/smmap-4.0.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/snowballstemmer-2.1.0-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/stevedore-3.3.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/termcolor-1.1.0-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/toml-0.10.2-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/typed_ast-1.4.3-cp39-cp39-manylinux1_x86_64/lib
/home/pawamoy/.cache/pdm/packages/typing_extensions-<IP_ADDRESS>-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/urllib3-1.26.6-py2.py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/watchdog-2.1.3-py3-none-manylinux2014_x86_64/lib
/home/pawamoy/.cache/pdm/packages/wps_light-0.15.2-py3-none-any/lib
/home/pawamoy/.cache/pdm/packages/zipp-3.5.0-py3-none-any/lib
/home/pawamoy/.local/lib/python3.9/site-packages
/usr/lib/python3.9/site-packages

In the end, if VSCode queries Python to get the paths to scan, shouldn't extra paths work for autocomplete and analysis as well, even with .pth files in them?

As you can see, VSCode cannot find the failprint package, which is nevertheless in sys.path (/home/pawamoy/.cache/pdm/packages/failprint-0.8.0-py3-none-any/lib).
But maybe I'm missing something here, like different execution environments/conditions?

Can you provide trace logs from Pylance so we can see what interpreter and paths it is using?
"python.analysis.logLevel": "Trace"

Something like this?
[Info  - 8:28:17 PM] Pylance language server 2021.8.2 (pyright f462f5bb) starting
[Info  - 8:28:17 PM] Server root directory: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist
[Info  - 8:28:17 PM] No configuration file found.
[Info  - 8:28:17 PM] pyproject.toml file found at /media/data/dev/python/duty.
[Info  - 8:28:17 PM] Setting pythonPath for service "duty": "/usr/bin/python"
[Info  - 8:28:17 PM] Loading pyproject.toml file at /media/data/dev/python/duty/pyproject.toml
[Error - 8:28:17 PM] Pyproject file "/media/data/dev/python/duty/pyproject.toml" is missing "[tool.pyright] section.
[Warn  - 8:28:17 PM] stubPath /media/data/dev/python/duty/typings is not a valid directory.
[Info  - 8:28:17 PM] Assuming Python version 3.9
[Info  - 8:28:17 PM] Assuming Python platform Linux
Search paths for /media/data/dev/python/duty
  /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib
  /media/data/dev/python/duty
  /media/data/dev/python/duty/src
  /media/data/dev/python/duty/__pypackages__/3.9/lib
  /home/pawamoy/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/pep582
  /media/data/dev/python/duty/typings
  /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stubs/...
  /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/bundled/stubs
  /usr/lib/python3.9
  /usr/lib/python3.9/lib-dynload
  /home/pawamoy/.local/lib/python3.9/site-packages
  /usr/lib/python3.9/site-packages
[Warn  - 8:28:17 PM] Exception received when installing file system watcher: TypeError [ERR_FEATURE_UNAVAILABLE_ON_PLATFORM]: The feature watch recursively is unavailable on the current platform, which is being used to run Node.js
[Warn  - 8:28:17 PM] Exception received when installing file system watcher: TypeError [ERR_FEATURE_UNAVAILABLE_ON_PLATFORM]: The feature watch recursively is unavailable on the current platform, which is being used to run Node.js
[Warn  - 8:28:17 PM] Exception received when installing file system watcher: TypeError [ERR_FEATURE_UNAVAILABLE_ON_PLATFORM]: The feature watch recursively is unavailable on the current platform, which is being used to run Node.js
[Warn  - 8:28:17 PM] Exception received when installing file system watcher: TypeError [ERR_FEATURE_UNAVAILABLE_ON_PLATFORM]: The feature watch recursively is unavailable on the current platform, which is being used to run Node.js
[Info  - 8:28:17 PM] Searching for source files
[Info  - 8:28:17 PM] Found 37 source files
[Info  - 8:28:17 PM] Background analysis(1) root directory: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist
[Info  - 8:28:17 PM] Background analysis(1) started
Background analysis message: setConfigOptions
Background analysis message: setImportResolver
Background analysis message: ensurePartialStubPackages
Background analysis message: setTrackedFiles
Background analysis message: markAllFilesDirty
Background analysis message: setFileOpened
Background analysis message: getSemanticTokens full
[BG(1)] getSemanticTokens full at /media/data/dev/python/duty/pathfiles.py ...
[BG(1)]   parsing: /media/data/dev/python/duty/pathfiles.py (22ms)
[FG] parsing: /media/data/dev/python/duty/pathfiles.py (18ms)
[FG] parsing: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/builtins.pyi [fs read 2ms] (67ms)
[FG] binding: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/builtins.pyi (29ms)
[FG] binding: /media/data/dev/python/duty/pathfiles.py (0ms)
[BG(1)]   parsing: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/builtins.pyi [fs read 2ms] (71ms)
[BG(1)]   binding: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/builtins.pyi (29ms)
[BG(1)]   binding: /media/data/dev/python/duty/pathfiles.py (0ms)
[BG(1)]   parsing: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/typing.pyi [fs read 2ms] (27ms)
[BG(1)]   binding: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/typing.pyi (8ms)
[BG(1)]   parsing: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi [fs read 0ms] (6ms)
[BG(1)]   binding: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi (1ms)
[BG(1)]   parsing: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/typing_extensions.pyi [fs read 0ms] (3ms)
[BG(1)]   binding: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/typing_extensions.pyi (1ms)
[BG(1)]   parsing: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/sys.pyi [fs read 0ms] (6ms)
[BG(1)]   binding: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/sys.pyi (4ms)
[BG(1)] getSemanticTokens full at /media/data/dev/python/duty/pathfiles.py (204ms)
Background analysis message: getSemanticTokens range
[BG(1)] getSemanticTokens range 0:0 - 3:0 at /media/data/dev/python/duty/pathfiles.py (0ms)
Background analysis message: analyze
[BG(1)] analyzing: /media/data/dev/python/duty/pathfiles.py ...
[BG(1)]   checking: /media/data/dev/python/duty/pathfiles.py (1ms)
[BG(1)] analyzing: /media/data/dev/python/duty/pathfiles.py (2ms)
Background analysis message: resumeAnalysis
Background analysis message: setFileOpened
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
[FG] parsing: /media/data/dev/python/duty/src/duty/cli.py (22ms)
[FG] binding: /media/data/dev/python/duty/src/duty/cli.py (3ms)
Background analysis message: getSemanticTokens full
[BG(1)] getSemanticTokens full at /media/data/dev/python/duty/src/duty/cli.py ...
[BG(1)]   parsing: /media/data/dev/python/duty/src/duty/cli.py (34ms)
[BG(1)]   binding: /media/data/dev/python/duty/src/duty/cli.py (3ms)
[BG(1)]   parsing: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/argparse.pyi [fs read 0ms] (69ms)
[BG(1)]   binding: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/argparse.pyi (5ms)
[BG(1)]   parsing: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/inspect.pyi [fs read 0ms] (11ms)
[BG(1)]   binding: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/inspect.pyi (5ms)
[BG(1)]   parsing: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/textwrap.pyi [fs read 0ms] (3ms)
[BG(1)]   binding: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/textwrap.pyi (1ms)
[BG(1)]   parsing: /media/data/dev/python/duty/src/duty/collection.py [fs read 0ms] (11ms)
[BG(1)]   binding: /media/data/dev/python/duty/src/duty/collection.py (2ms)
[BG(1)]   parsing: /media/data/dev/python/duty/src/duty/exceptions.py [fs read 0ms] (0ms)
[BG(1)]   binding: /media/data/dev/python/duty/src/duty/exceptions.py (0ms)
[BG(1)]   parsing: /media/data/dev/python/duty/src/duty/validation.py [fs read 0ms] (9ms)
[BG(1)]   binding: /media/data/dev/python/duty/src/duty/validation.py (1ms)
[BG(1)]   parsing: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/abc.pyi [fs read 0ms] (1ms)
[BG(1)]   binding: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/abc.pyi (0ms)
[BG(1)] getSemanticTokens full at /media/data/dev/python/duty/src/duty/cli.py (211ms)
Background analysis message: getSemanticTokens range
[BG(1)] getSemanticTokens range 0:0 - 48:28 at /media/data/dev/python/duty/src/duty/cli.py (3ms)
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: analyze
[BG(1)] analyzing: /media/data/dev/python/duty/src/duty/cli.py ...
[BG(1)]   checking: /media/data/dev/python/duty/src/duty/cli.py (10ms)
[BG(1)] analyzing: /media/data/dev/python/duty/src/duty/cli.py (10ms)
Background analysis message: resumeAnalysis
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
[FG] parsing: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/typing.pyi [fs read 0ms] (53ms)
[FG] binding: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/typing.pyi (9ms)
[FG] parsing: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi [fs read 0ms] (8ms)
[FG] binding: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi (1ms)
[FG] parsing: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/typing_extensions.pyi [fs read 0ms] (4ms)
[FG] binding: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/typing_extensions.pyi (1ms)
[FG] parsing: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/inspect.pyi [fs read 0ms] (10ms)
[FG] binding: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/inspect.pyi (3ms)
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
[FG] parsing: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/textwrap.pyi [fs read 0ms] (3ms)
[FG] binding: /home/pawamoy/.vscode/extensions/ms-python.vscode-pylance-2021.8.2/dist/typeshed-fallback/stdlib/textwrap.pyi (2ms)
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: markFilesDirty
Background analysis message: analyze

Yes, exactly. Is /usr/bin/python the same python that you're accessing in the terminal? Most of those paths are just from sys.path from calling python, so I would think that we get all of those paths that your one-liners are printing.
This could also be an instance of your python being special and handling __pypackages__; we don't actually run python within the workspace, we run it in a non-user folder as an extra security measure to prevent random code execution (in addition to other measures).

In a terminal python points to the pyenv-installed one, but the results are the same if I just use /usr/bin/python instead.

we don't actually run python within the workspace, we run it in a non-user folder as an extra security measure to prevent random code execution (in addition to other measures).

That could explain the difference, but then again the Pylance logs show that /home/pawamoy/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/pep582 is in sys.path. If it does not come from my user's shell configuration (exported PYTHONPATH environment variable), where does it come from? And why paths under PDM's cache folder are not added to sys.path? They should be thanks to the sitecustomize.py in /home/pawamoy/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/pep582 . I'm confused :confused:

The fact that this whole thing relies on the directory you execute python in is really problematic (even further than what I mentioned in #1441, as now we can't even trust the interpreter to do the right thing).
I'm not entirely certain what to do here. We could try and remove our code that prevents the running of the python interpreter within the workspace and rely on other code execution protection measures, so that we do run python at the workspace root. That would then allow this custom stuff to find __pypackages__, but overall that doesn't fix __pypackages__ as a concept, because that PEP allows for much more magical sys.path changes based on where you are and what script you're running, which are very very hard to handle in an editor (where we just say "well, it's the workspace root"). Maybe it's not going to be common that a workspace contains more than one __pypackages__, and discovering based on the workspace root is enough, I don't know.
We could reuse the code we use for venvPath to parse out non-code-executing .pth files (just paths), with the assumption that users will be adding __pypackages__ to extraPaths (like you did), which would work for now, but isn't a long-term solution if __pypackages__ gets any traction. We don't want people having to configure paths just to match what the interpreter is supposed to be doing.

I see. Getting the expected paths in a workspace is probably much more complicated than I can imagine. I would be OK with the second solution you mention. PDM itself documents that you need to add extra path to work in VSCode. For a better, long-term solution, I guess we'd have to engage with core Python developers, at https://discuss.python.org/t/pep-582-python-local-packages-directory/963 (if you are not already doing so :relaxed: ).
Thank you very much @jakebailey for your time and help! Let me know if I can help in any way if you wish to proceed forward.

I've implemented a prototype of the second solution and it does work (for simple pth files); we'll discuss whether or not it's a good idea or if the first solution is more robust.

I'll gladly test your prototype if it's possible! Just let me know :slightly_smiling_face: And thanks!

We're probably going to take that second solution for now, as it's the least destructive.
One consideration is handling recursive pths, meaning pths that point to directories that also contain pth files.
I haven't been able to get PDM set up on my machine yet; can you see if you install matplotlib what your search paths come out to be? I believe they include a pth file in their regular release.

One consideration is handling recursive pths, meaning pths that point to directories that also contain pth files.

@jakebailey That is not necessary IMHO. The Python interpreter recognizes all .pth files under a path by site.add_site_dir(). It only adds the paths contained in a pth file and won't look into them recursively.
Thanks for your effort again.

Great, I'll get my fix in for tomorrow.
I do wonder how that affects libs that do contain pth files; would PDM see this and fall back on regular copying? This is somewhat similar to how yarn works with PnP.

I do wonder how that affects libs that do contain pth files; would PDM see this and fall back on regular copying? This is somewhat similar to how yarn works with PnP.

Yes, .pth files are copied


Error "type or namespace name 'SpatialTracking' does not exist in the namespace 'UnityEngine'" with various versions

Hello,
I Need both XR and AR work together, and found there were bugfixes 9 days ago.
So I chosed the two newer branches.
Both give me Always error:
"type or namespace name 'SpatialTracking' does not exist in the namespace 'UnityEngine'"
I tried included packages, then used package Manager to install suggested updates, and even tried the prereleases there. Always get this error.
Thanks a lot!
Unity 2019.2.9
Both Branches Development or PreRelease 2.2.0

Related: #6555

Thanks a lot, Great work with the MRTK by the way!
I did add a reference to the asmdef, now I get this one:
Assets\MixedRealityToolkit.Staging\UnityAR\Utilities\ArEnumConversion.cs(21,23): error CS0246: The type or namespace name 'TrackedPoseDriver' could not be found (are you missing a using directive or an assembly reference?)


Added Tailwind JIT

Description
What does this PR do?
Added Tailwind JIT into the PostCSS config
Related Tickets and Documents
#264
What gif best describes this PR or how it makes you feel? (optional)
http://gph.is/1tKXPLL

Looks great! Merging now


Add git tags for versions

Request: Add git tags for versions
For example, ideally there would be a git tag for 1.4.1

I agree. Tagged releases would be awesome.

We'll add git tags from now on.

Tags are now added for new versions.


Support passing Arrays to Functions Using Piping

Description
This feature enhances the Pode module by enabling full support for passing arrays to functions using the pipeline. The update ensures that the specified functions can correctly handle multiple input objects when piped as arrays, improving flexibility and usability in scripting and automation.
Impacted Functions:

Set-PodeCache
Add-PodeOAResponse
Remove-PodeOAResponse
Set-PodeOARequest
Set-PodeOARouteInfo
Add-PodeOACallBack
Add-PodeOAExternalRoute
ConvertTo-PodeRoute
Update-PodeSecret
Set-PodeSecret
Set-PodeState
Out-PodeHost
Write-PodeHost
Out-PodeVariable

Key Changes:

Modified the impacted functions to support array input via the pipeline.
Enhanced processing logic to aggregate piped values and handle them appropriately.
Ensured backward compatibility by retaining existing parameter functionalities.

This update will streamline the process of handling multiple objects in a single pipeline, making it easier to work with collections of items in Pode scripts.
This update address #1343

Lock-PodeObject
Enter-PodeLockable
I'm not sure if are fixable passing an array the array is transformed to a different object
Maybe is better to set ValueFromPipeline to $false

@Badgerati, I am done with this. Please take a look at it when you have time


Support for Registry Auth using IAM

Platform: AWS
YADP version: 0.1.0-rc37
We use Amazon Elastic Container Registry (ECR) and enable authentication via a combination of an IAM instance profile which is assigned to each slave host in a cluster and the ECR credentials helper (which takes care of getting an authentication token from ECR). This has worked well for us in our docker implementation for some time.
However, YADP does not allow me to specify an AWS Credential for the 'Registry Credentials property of the 'Pull Image Settings'. I can see that it states that only Docker Registry Auth type is supported, but I wondered if it is possible for you to add AWS Credentials support ?
At present if the image is not available on the host where the slave container starts, or if we set the 'Pull Strategy' to anything other than 'Pull Never' then the container will never start since it will get an authentication error attempting to pull the slave image. Actually, I find this a little surprising since the host does have an IAM instance profile that definitely allows pulls from ECR if you SSH onto the instance, but I assume the YADP plugin is performing the pull in a way that this doesn't engage.
So for now we have to 'seed' all of the hosts in our slave cluster with images and set the Pull Strategy to 'Never', which TBH is a bit inconvenient.
If I spin up a slave container (from a pre-seeded image) and perform a docker pull as part of the Jenkins job itself, that works fine and obviously uses to IAM profile and ECR Creds Helper to do so.
So its just that initial pull of the slave image which is the problem (we have several variants of slave images, each containing different build tools).
Whats the possibility of adding AWS Creds ?
Or, can you suggest a different approach than needing to ensure that at least one slave image exists on each host to act as a way of pulling other images ?
Kind Regards
Fraser.

Sorry that didn't answer before, seems i lost email :(

but I wondered if it is possible for you to add AWS Credentials support ?

probably yes... i never used it, what kind of auth does it use?

Actually, I find this a little surprising since the host does have an IAM instance profile that definitely allows pulls from ECR if you SSH onto the instance, but I assume the YADP plugin is performing the pull in a way that this doesn't engage.

Jenkins master handles connection to daemon and that mean that credentials should be in master.

How i can reproduce the same behavior on my laptop?