Ensure ChangeType is updating method invocation type information

ChangeType appears not to be updating the type info of method invocations to the new target class.

Right now method invocation types aren't being updated by ChangeType.visitMethodInvocation() because it calls super.visitMethodInvocation() which calls this:

m = m.withMethodType((JavaType.Method) visitType(m.getMethodType(), p));

But since ChangeType doesn't have an override for visitType() the method type is unchanged

(I don't have a demonstrable unit test at the moment.)

I've verified that ChangeType is correctly updating method invocation type information.
I remember when we first encountered this issue it was about a week before the issue got filed. At that time TypeMapping was significantly less correct than it is now, so I think the problem was actually there and has already been fixed.


P10 Outdoor Panel Problem

Hi,
I have a problem. My RGB LED Matrix shows only funny things. No matter what I hire.
P10 RGB 32x16
Cable connected as described. A B C D
Have it already
"Display.begin (4);
display.setScanPattern (ZAGGIZ);
display.setMuxPattern (STRAIGHT); "
but it tries only as in the video
https://youtu.be/Nmd7f6M5Kak
Plattern_test
https://youtu.be/LN4MGtVa4TM
https://de.aliexpress.com/item/1248297006.html?spm=a2g0s.90423<IP_ADDRESS>be4c4dxRtA3N
EDIT:
https://github.com/hzeller/rpi-rgb-led-matrix/issues/529
Maybe that helps? I'm not that good at programming

@Jetiman This worked for me after some hacking around, search for the following code in PxMatrix.h and comment it out or delete it, it should be around line number 494 in the file.
  if ((_scan_pattern == ZAGGIZ) && ((y % (_row_pattern * 2)) < _row_pattern))
    bit_select = 7 - bit_select;

I have my modes set as
  display.begin(4);
  display.setScanPattern(ZAGGIZ);
  display.setMuxPattern(BINARY);

same matrix?
makes the same mistake with the changes

@Jetiman It looked like I had a similar problem with you on the "pattern test" video you have.  The Y-Axis pixels came out in the wrong order, however the X-axis was in the correct order.
I'm using this panel: http://www.ylrled.net/product/75992050.html
After the fix I showed the Y-Axis ordering was corrected.

Could you try the latest master with
 display.setScanPattern(ZAGZIG);
please?

It does something different, but not yet the right one
plattern test
https://youtu.be/LISa_5ivWgw
pixelime
https://youtu.be/RLEhaaQUw8c

OK ... I screwed up the boolean algebra bit ... can you try again with the latest master?

with display.setScanPattern(ZAGZIG); of course

gets better. But it is not right yet
what is better for testing, pixeltime or plates test
https://youtu.be/rbGpSaQU_7w

just to get this straight .. you only commented
  if ((_scan_pattern == ZAGGIZ) && ((y % (_row_pattern * 2)) < _row_pattern))
    bit_select = 7 - bit_select;

out and it worked with   display.setScanPattern(ZAGGIZ);  ?

can you repeat/verify with the latest master?

latest master
Okay, I commented that out in PxMatrix.h
if ((_scan_pattern == ZAGGIZ) && ((y % (_row_pattern * 2)) < _row_pattern))     bit_select = 7 - bit_select;
My settings are:
PxMATRIX display(32,16,P_LAT, P_OE,P_A,P_B,P_C,P_D);
  display.begin(4);
  display.setScanPattern(ZAGGIZ);
  display.setMuxPattern(STRAIGHT);

added (at (((_scan_pattern ----- because otherwise an error comes
if ((yy<=y) && (y<yy+_row_pattern))         total_offset_r=base_offset-row_sector__offset*row_sector-(((_scan_pattern==ZAGGIZ)||(_scan_pattern==ZAGZIG)) ? 1: 0);
https://youtu.be/wYsXzSe81IE

OK ... lets start from the beginning. Please run the pattern test and place
display.displayTestPixel(70);
in the display_updater() (and post the video)

https://youtu.be/F9kLLQD2Cac

Ca you post you display_update function....still looks like the pattern test

sorry I have set the wrong setting
https://youtu.be/mxRiKaEZDpQ
#include <PxMatrix.h>

#ifdef ESP32

#define P_LAT 22
#define P_A 19
#define P_B 23
#define P_C 18
#define P_D 5
#define P_E 15
#define P_OE 2
hw_timer_t * timer = NULL;
portMUX_TYPE timerMux = portMUX_INITIALIZER_UNLOCKED;

#endif

#ifdef ESP8266

#include <Ticker.h>
Ticker display_ticker;
#define P_LAT 16
#define P_A 5
#define P_B 4
#define P_C 15
#define P_D 12
#define P_E 0
#define P_OE 2

#endif
// Pins for LED MATRIX

//PxMATRIX display(32,16,P_LAT, P_OE,P_A,P_B,P_C);
PxMATRIX display(32,16,P_LAT, P_OE,P_A,P_B,P_C,P_D);
//PxMATRIX display(64,64,P_LAT, P_OE,P_A,P_B,P_C,P_D,P_E);

#ifdef ESP8266
// ISR for display refresh
void display_updater()
{
  //display.displayTestPattern(70);
   display.displayTestPixel(70);
  //display.display(70);
}
#endif

#ifdef ESP32
void IRAM_ATTR display_updater(){
  // Increment the counter and set the time of ISR
  portENTER_CRITICAL_ISR(&timerMux);
  //isplay.display(70);
  display.displayTestPixel(70);
  portEXIT_CRITICAL_ISR(&timerMux);
}
#endif

uint16_t myCYAN = display.color565(0, 255, 255);
void setup() {
  // put your setup code here, to run once:
Serial.begin(9600);
  display.begin(4);
  display.flushDisplay();
  display.setTextColor(myCYAN);
  display.setCursor(2,0);
  display.print("Pixel");
  Serial.println("hello");
  display.setMuxPattern(STRAIGHT);

  #ifdef ESP8266
    display_ticker.attach(0.002, display_updater);
  #endif

  #ifdef ESP32
    timer = timerBegin(0, 80, true);
    timerAttachInterrupt(timer, &display_updater, true);
    timerAlarmWrite(timer, 2000, true);
    timerAlarmEnable(timer);
  #endif

  delay(1000);
}

void loop() {

 delay(100);

}

OK ... that is a really strange byte split pattern. I tried to implement it.
You can try the latest master, use pixeltime example with display.setScanPattern(ZZAGG);

It works. There are only a few single pixel errors in it. Above the font and top right
https://youtu.be/ZHA9_0a_gL0

Ok...a few basic things to check. Do you have a power supply rated >3A and proper cables (beefy) between panel and power supply

Verify the ground connection between panel and esp

think it's up to my jumper cables. Power supply is a 5v -10A with big power cords

Another thing is to make sure that the E wire is connected or grounded (try both)

If you leave E floating on the panel it leads to artifacts on some panels

I do not have an E pin. Have three GND. I have also connected. Will the days test other cables

@Jetiman I'm not sure this will help in your case, but just throwing it out there in case it can solve your problem.
Things you can try:

Turn off fastUpdate and choose a "display_draw_time" other than zero (e.g. 25)
Reduce the SPI clock rate SPI.setFrequency();  I set mine to 7,500,000 [This could help with long lossy cables, lower frequencies will have less loss and less noise).

Thanks @kenle !

its work to p10 outdor
// This is how many color levels the display shows - the more the slower the update
//#define PxMATRIX_COLOR_DEPTH 8
// Defines the buffer height / the maximum height of the matrix
//#define PxMATRIX_MAX_HEIGHT 64
// Defines the buffer width / the maximum width of the matrix
//#define PxMATRIX_MAX_WIDTH 64
// Defines how long we display things by default
//#define PxMATRIX_DEFAULT_SHOWTIME 30
// Defines the speed of the SPI bus (reducing this may help if you experience noisy images)
//#define PxMATRIX_SPI_FREQUENCY 20000000
// Creates a second buffer for backround drawing (doubles the required RAM)
//#define PxMATRIX_double_buffer true
#include <PxMatrix.h>
// Pins for LED MATRIX
#ifdef ESP32
#define P_LAT 22
#define P_A 19
#define P_B 23
#define P_C 18
#define P_D 5
#define P_E 15
#define P_OE 2
hw_timer_t * timer = NULL;
portMUX_TYPE timerMux = portMUX_INITIALIZER_UNLOCKED;
#endif
#ifdef ESP8266
#include <Ticker.h>
Ticker display_ticker;
#define P_LAT 16
#define P_A 5
#define P_B 4
#define P_C 15
#define P_D 12
#define P_E 0
#define P_OE 2
#endif
#define matrix_width 32
#define matrix_height 16
// This defines the 'on' time of the display is us. The larger this number,
// the brighter the display. If too large the ESP will crash
uint8_t display_draw_time=60; //30-70 is usually fine
//PxMATRIX display(32,16,P_LAT, P_OE,P_A,P_B,P_C);
PxMATRIX display(32,16,P_LAT, P_OE,P_A,P_B,P_C,P_D);
//PxMATRIX display(64,64,P_LAT, P_OE,P_A,P_B,P_C,P_D,P_E);
// Some standard colors
uint16_t myRED = display.color565(255, 0, 0);
uint16_t myGREEN = display.color565(0, 255, 0);
uint16_t myBLUE = display.color565(0, 0, 255);
uint16_t myWHITE = display.color565(255, 255, 255);
uint16_t myYELLOW = display.color565(255, 255, 0);
uint16_t myCYAN = display.color565(0, 255, 255);
uint16_t myMAGENTA = display.color565(255, 0, 255);
uint16_t myBLACK = display.color565(0, 0, 0);
uint16_t myCOLORS[8]={myRED,myGREEN,myBLUE,myWHITE,myYELLOW,myCYAN,myMAGENTA,myBLACK};
uint8_t static weather_icons[]={0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x20,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x20,0x00,0x00,0xff,0xe0,0x00,0x00,0x00,0x00,0xff,0xe0,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x20,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x20,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x20,0x00,0x00,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x20,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0x00,0x00,0x00,0x20,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xff,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x20,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0x00,0x00,0x00,0x00,0x00,0x00
,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0xff,0xe0,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x20,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xdf,0x07,0xdf,0x07,0xdf,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x20,0x00,0x20,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xff,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xff,0x07,0xdf,0x00,0x00,0x00,0x00,0x07,0xff,0x00,0x00,0x00,0x00,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0x00,0x00,0x00,0x00,0x00,0x00,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0x00,0x00,0x00,0x00
,0x00,0x00,0x00,0x00,0xff,0xe0,0x00,0x00,0x00,0x00,0x00,0x00,0xff,0xe0,0x00,0x00,0x00,0x00,0x00,0x20,0x00,0x00,0x00,0x00,0xff,0xe0,0x00,0x00,0xff,0xe0,0xff,0xe0,0xff,0xe0,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xdf,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0x00,0x20,0x00,0x00,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xff,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0x00,0x00,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0x00,0x00
,0x00,0x20,0x00,0x00,0x00,0x00,0xff,0xe0,0xff,0xe0,0xff,0xe0,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xff,0x07,0xff,0xff,0xe0,0xff,0xe0,0xff,0xe0,0x00,0x00,0xff,0xe0,0x00,0x00,0x07,0xff,0x07,0xff,0x07,0xdf,0x07,0xff,0x07,0xdf,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xdf,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x00,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xdf,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0x00,0x00,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0x00,0x00,0x00,0x20,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xff,0x00,0x00,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x00,0x07,0xff,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0x00,0x00,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0x07,0xdf,0x07,0xdf,0x07,0xff,0xff,0xe0,0xff,0xe0,0x00,0x00
,0x00,0x00,0xff,0xe0,0x00,0x00,0xff,0xe0,0xff,0xe0,0xff,0xe0,0x00,0x00,0xff,0xe0,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xdf,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0xff,0xe0,0x00,0x20,0x00,0x00,0x07,0xdf,0x07,0xdf,0x07,0xdf,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x00,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xdf,0x07,0xdf,0x07,0xff,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x20,0x00,0x00,0x00,0x00,0x00,0x00,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0xff,0xff,0x07,0xff,0x07,0xff,0x07,0xdf,0x07,0xff,0x00,0x00,0x07,0xff,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xff,0x07,0xdf,0x00,0x00,0x00,0x00,0x07,0xff,0x00,0x00,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0x00,0x00,0xff,0xe0,0xff,0xe0,0xff,0xe0,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x00
,0x00,0x00,0x00,0x00,0x00,0x00,0xff,0xe0,0xff,0xe0,0xff,0xe0,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xdf,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0x00,0x20,0x00,0x00,0x07,0xff,0x00,0x20,0xff,0xff,0x00,0x00,0xff,0xff,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xff,0x00,0x00,0xff,0xff,0x00,0x00,0xff,0xff,0x00,0x20,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xdf,0x00,0x00,0x07,0xff,0x07,0xff,0x07,0xdf,0x00,0x00,0x07,0xff,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xdf,0x00,0x00,0x00,0x00,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0x00,0x00,0xff,0xe0,0xff,0xe0,0x07,0xdf,0x07,0xdf,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x00
,0x00,0x00,0x00,0x00,0xff,0xe0,0x00,0x00,0x00,0x00,0x00,0x00,0xff,0xe0,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0xff,0xe0,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x20,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0xff,0xff,0x00,0x00,0xff,0xff,0x00,0x00,0x00,0x00,0x00,0x00,0xff,0xe0,0x00,0x00,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xff,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x20,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0x00,0x00,0xff,0xe0,0xff,0xe0,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x00
,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0xff,0xe0,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xdf,0x07,0xdf,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x20,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x20,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0xff,0xff,0x00,0x00,0xff,0xff,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0xff,0xff,0x00,0x00,0xff,0xff,0x00,0x00,0x00,0x00,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x20,0x00,0x00,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x20,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xff,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xdf,0x07,0xff,0x00,0x00,0x00,0x00,0x07,0xff,0x00,0x00,0x00,0x00,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0x00,0x00,0x00,0x00,0x00,0x00,0xff,0xe0,0xff,0xe0,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00
,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0x00,0x20,0x00,0x00,0x00,0x20,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xdf,0x07,0xdf,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0xff,0xff,0x00,0x00,0xff,0xff,0x00,0x00,0x00,0x00,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0x00,0x00,0x00,0x20,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xff,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xdf,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0xff,0xe0,0xff,0xe0,0x07,0xdf,0x07,0xff,0x07,0xff,0x00,0x00,0x00,0x00,0x00,0x00
,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x20,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0xff,0xe0,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x20,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00
};
#ifdef ESP8266
// ISR for display refresh
void display_updater()
{
display.display(display_draw_time);
}
#endif
#ifdef ESP32
void IRAM_ATTR display_updater(){
// Increment the counter and set the time of ISR
portENTER_CRITICAL_ISR(&timerMux);
display.display(display_draw_time);
portEXIT_CRITICAL_ISR(&timerMux);
}
#endif
void display_update_enable(bool is_enable)
{
#ifdef ESP8266
if (is_enable)
display_ticker.attach(0.004, display_updater);
else
display_ticker.detach();
#endif
#ifdef ESP32
if (is_enable)
{
timer = timerBegin(0, 80, true);
timerAttachInterrupt(timer, &display_updater, true);
timerAlarmWrite(timer, 4000, true);
timerAlarmEnable(timer);
}
else
{
timerDetachInterrupt(timer);
timerAlarmDisable(timer);
}
#endif
}
void setup() {
Serial.begin(9600);
// Define your display layout here, e.g. 1/8 step, and optional SPI pins begin(row_pattern, CLK, MOSI, MISO, SS)
display.begin(4);
//display.begin(8, 14, 13, 12, 4);
// Define multiplex implemention here {BINARY, STRAIGHT} (default is BINARY)
//display.setMuxPattern(BINARY);
display.setMuxPattern (STRAIGHT);
// Set the multiplex pattern {LINE, ZIGZAG,ZZAGG, ZAGGIZ, WZAGZIG, VZAG, ZAGZIG} (default is LINE)
//display.setScanPattern(LINE);
display.setScanPattern(ZZAGG);
// Rotate display
//display.setRotate(true);
// Flip display
//display.setFlip(true);
// Control the minimum color values that result in an active pixel
//display.setColorOffset(5, 5,5);
// Set the multiplex implemention {BINARY, STRAIGHT} (default is BINARY)
//display.setMuxPattern(BINARY);
// Set the color order {RRGGBB, RRBBGG, GGRRBB, GGBBRR, BBRRGG, BBGGRR} (default is RRGGBB)
//display.setColorOrder(RRGGBB);
// Set the time in microseconds that we pause after selecting each mux channel
// (May help if some rows are missing / the mux chip is too slow)
//display.setMuxDelay(0,1,0,0,0);
// Set the number of panels that make up the display area width (default is 1)
//display.setPanelsWidth(2);
// Set the brightness of the panels (default is 255)
//display.setBrightness(50);
// Set driver chip type
//display.setDriverChip(FM6124);
display.clearDisplay();
display.setTextColor(myCYAN);
display.setCursor(2,0);
display.print("Pixel");
display.setTextColor(myMAGENTA);
display.setCursor(2,8);
display.print("Time");
display_update_enable(true);
delay(3000);
}
union single_double{
uint8_t two[2];
uint16_t one;
} this_single_double;
// This draws the weather icons
void draw_weather_icon (uint8_t icon)
{
if (icon>10)
icon=10;
for (int yy=0; yy<10;yy++)
{
for (int xx=0; xx<10;xx++)
{
uint16_t byte_pos=(xx+icon*10)2+yy220;
this_single_double.two[1]=weather_icons[byte_pos];
this_single_double.two[0]=weather_icons[byte_pos+1];
display.drawPixel(1+xx,yy,this_single_double.one);
}
}
}
unsigned long last_draw=0;
void scroll_text(uint8_t ypos, unsigned long scroll_delay, String text, uint8_t colorR, uint8_t colorG, uint8_t colorB)
{
uint16_t text_length = text.length();
display.setTextWrap(false);  // we don't wrap text so it scrolls nicely
display.setTextSize(1);
display.setRotation(0);
display.setTextColor(display.color565(colorR,colorG,colorB));
// Asuming 5 pixel average character width
for (int xpos=matrix_width; xpos>-(matrix_width+text_length*5); xpos--)
{
  display.setTextColor(display.color565(colorR,colorG,colorB));
  display.clearDisplay();
  display.setCursor(xpos,ypos);
  display.println(text);
  delay(scroll_delay);
  yield();

  // This might smooth the transition a bit if we go slow
  // display.setTextColor(display.color565(colorR/4,colorG/4,colorB/4));
  // display.setCursor(xpos-1,ypos);
  // display.println(text);

  delay(scroll_delay/5);
  yield();

}

}
uint8_t icon_index=0;
void loop() {
scroll_text(1,50,"Welcome to PxMatrix!",96,96,250);
display.clearDisplay();
draw_weather_icon(icon_index);
icon_index++;
if (icon_index>10)
icon_index=0;
for (int xx=0; xx<16;xx++)
{
display.drawLine(xx+16,0,xx+16,5,display.color565(xx16,0,0));
display.drawLine(xx+16,6,xx+16,10,display.color565(0,xx16,0));
display.drawLine(xx+16,11,xx+16,15,display.color565(0,0,xx*16));
}
delay(1000);
for (uint8_t dimm=255; dimm>0; dimm--)
{
display.setBrightness(dimm);
delay(5);
}
for (uint8_t dimm=0; dimm<255; dimm++)
{
display.setBrightness(dimm);
delay(5);
}
}


Add a memory tracker. i need to profile where i allocate memory.

Right now its unknown how much memory i heap allocate and how much memory i stack allocate.
i only got info on the 2d renderer

Right now its unknown how much memory i heap allocate and how much memory i stack allocate.
i only got info on the 2d renderer

Why not just use valgrind?

Well this is a very old issue i opened. Even before i created cebus and an 'arena' allocator.
The idea was that the user can also profile their own allocated memory.
Should be pretty easy to see now since i added arena_size() to cebus.
Thank you for the contribution. Much appreciated.


Calendar not returning data to Modal

Let me start by saying this is a really great project that you have going here. I have a problem that is outlined below:
I have a button in a Modal that shows the calendar and when I click on the check icon to save the data, nothing is sent back to the Modal. Just to make sure I was doing the right thing, I copied my code to a page verbatim and it worked perfectly on there. Is there any work around for using this component in Modals? My code below
    this.calendarCtrl.openCalendar({
      isRadio: false,
      title: 'PartyUp Calendar',
      monthTitle: ' MMMM-yy',
      weekdaysTitle: ["Sun", "Mon", "Tue", "Wed", "Thu", "Fri", "Sat"],
      from: new Date(),
      cssClass: 'calendar-class',
      to: yearFromNow,
      //isSaveHistory: true,
      closeLabel: 'CANCEL',
    })
      .then((res: any) => {
        console.log(res);
      })
      .catch((err) => {
        console.log("Error", err);
      });

same for me .
its not returning data after selecting date

According to something I saw somewhere, a Modal can't have another modal return data to it since it isn't an actual page. I ended up having to just make my modal into a page and then Calendar works fine.

I have same issue.


G keys and logo stay lit whatever profile/effect is on

as the title says no matter what profile the G keys stay the same color settled by logitech gaming software. Keyboard layout is the right one and you can see in aurora the g keys/logo change color, but not the physical keyboard.

The G-keys and logos are not supported by the Logitech SDK. When they are supported, I will enable updating for those lights.

wow that is a very fast answer thanks! btw great work ! really amazing


Type alias not recognised as such

 Environment data

Language Server version: 2023.2.10
OS and version: win32 x64
Python version (and distribution if applicable, e.g. Anaconda): 3.10.8
python.analysis.indexing: false
python.analysis.typeCheckingMode: basic

 Code Snippet

In homegrown_type_annotation_1.py:
import pydantic # pydantic==1.10.4

NewType = pydantic.constr(min_length=1, strip_whitespace=True)

x: NewType = 'foo'

 Expected behavior
No errors/warnings.
 Actual behavior
Newtype underlined in x: NewType = 'foo', with Pylance warning: "Illegal type annotation: variable not allowed unless it is a type alias".
 What I've tried:
In `homegrown_type_annotation_2.py`:
import pydantic # pydantic==1.10.4
from typing import Type

NewType: Type = pydantic.constr(min_length=1, strip_whitespace=True)

x: NewType = 'foo'

This makes no difference.
However, when I create a separate file example_utilities.py as follows...
import pydantic # pydantic==1.10.4

NewType = pydantic.constr(min_length=1, strip_whitespace=True)

And then in imported_type_annotation.py:
from example_utilities import NewType

x: NewType = 'foo'

...I don't get the same warning.
I created these .py files just to demonstrate/reproduce this issue, but I can't seem to upload them, so i've reported their names and content here as exactly as possible. Happy to provide the files by some other means if required.
requirements.txt is attached - but I created a new, clean workspace, and a new venv to reproduce this issue, so the only item listed there is pydantic.
 Logs

[Info  - 8:17:46 PM] (41052) Pylance language server 2023.2.10 (pyright 01758105) starting
[Info  - 8:17:46 PM] (41052) Server root directory: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist
[Info  - 8:17:46 PM] (41052) Starting service instance "PylanceBugReportWS"
[Info  - 8:17:46 PM] (41052) No configuration file found.
[Info  - 8:17:46 PM] (41052) No pyproject.toml file found.
[Info  - 8:17:46 PM] (41052) Setting pythonPath for service "PylanceBugReportWS": "c:\Users\vrajasekhar\Py\PylanceBugReportWS\.venv\Scripts\python.exe"
[Warn  - 8:17:46 PM] (41052) stubPath c:\Users\vrajasekhar\Py\PylanceBugReportWS\typings is not a valid directory.
[Info  - 8:17:47 PM] (41052) Assuming Python version 3.10
[Info  - 8:17:47 PM] (41052) Assuming Python platform Windows
[Info  - 8:17:47 PM] (41052) Search paths for c:\Users\vrajasekhar\Py\PylanceBugReportWS
[Info  - 8:17:47 PM] (41052)   c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib
[Info  - 8:17:47 PM] (41052)   c:\Users\vrajasekhar\Py\PylanceBugReportWS
[Info  - 8:17:47 PM] (41052)   C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages
[Info  - 8:17:47 PM] (41052)   c:\users\vrajasekhar\py\paradesign repo\nz pump station design tool\backend_working
[Info  - 8:17:47 PM] (41052)   C:\Users\vrajasekhar\Py\Paradesign Repo\NZ Pump Station Design Tool\backend_working\
[Info  - 8:17:47 PM] (41052)   c:\Users\vrajasekhar\Py\PylanceBugReportWS\typings
[Info  - 8:17:47 PM] (41052)   c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stubs\...
[Info  - 8:17:47 PM] (41052)   c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\bundled\stubs
[Info  - 8:17:47 PM] (41052)   c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\DLLs
[Info  - 8:17:47 PM] (41052)   c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib
[Info  - 8:17:47 PM] (41052)   c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310
[Info  - 8:17:47 PM] (41052)   c:\Users\vrajasekhar\Py\PylanceBugReportWS\.venv
[Info  - 8:17:47 PM] (41052)   c:\Users\vrajasekhar\Py\PylanceBugReportWS\.venv\Lib\site-packages
[Info  - 8:17:47 PM] (41052) Adding fs watcher for library directories:
 C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\DLLs
C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\lib
C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310
c:\Users\vrajasekhar\Py\PylanceBugReportWS\.venv
c:\Users\vrajasekhar\Py\PylanceBugReportWS\.venv\lib\site-packages
[Info  - 8:17:47 PM] (41052) Adding fs watcher for directories:
 c:\Users\vrajasekhar\Py\PylanceBugReportWS
[Info  - 8:17:47 PM] (41052) Searching for source files
[Info  - 8:17:47 PM] (41052) Found 4 source files
[Info  - 8:17:47 PM] (41052) Background analysis(1) root directory: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist
[Info  - 8:17:47 PM] (41052) Background analysis(1) started
(41052) Background analysis message: setConfigOptions
(41052) Background analysis message: setImportResolver
(41052) Background analysis message: ensurePartialStubPackages
(41052) Background analysis message: setTrackedFiles
(41052) Background analysis message: markAllFilesDirty
(41052) Background analysis message: analyze
(41052) [IDX(FG)] index libraries c:\Users\vrajasekhar\Py\PylanceBugReportWS (index) ...
(41052) [IDX(FG)]   read stdlib indices (42ms)
(41052) [IDX(FG)] index libraries c:\Users\vrajasekhar\Py\PylanceBugReportWS (index) [succeed] (45ms)
(41052) Background analysis message: setFileOpened
(41052) [FG] parsing: c:\Users\vrajasekhar\Py\PylanceBugReportWS\example_utilities.py (45ms)
(41052) [FG] parsing: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\builtins.pyi [fs read 4ms] (179ms)
(41052) [FG] binding: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\builtins.pyi (47ms)
(41052) [FG] binding: c:\Users\vrajasekhar\Py\PylanceBugReportWS\example_utilities.py (1ms)
(41052) Background analysis message: getDiagnosticsForRange
(41052) Background analysis message: analyze
(41052) [BG(1)] analyzing: c:\Users\vrajasekhar\Py\PylanceBugReportWS\example_utilities.py ...
(41052) [BG(1)]   parsing: c:\Users\vrajasekhar\Py\PylanceBugReportWS\example_utilities.py (31ms)
(41052) [BG(1)]   parsing: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\builtins.pyi [fs read 4ms] (121ms)
(41052) [BG(1)]   binding: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\builtins.pyi (48ms)
(41052) [BG(1)]   binding: c:\Users\vrajasekhar\Py\PylanceBugReportWS\example_utilities.py (1ms)
(41052) [BG(1)]   checking: c:\Users\vrajasekhar\Py\PylanceBugReportWS\example_utilities.py ...
(41052) [BG(1)]     parsing: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\typing.pyi [fs read 2ms] (33ms)
(41052) [BG(1)]     binding: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\typing.pyi (11ms)
(41052) [BG(1)]     parsing: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\typing_extensions.pyi [fs read 0ms] (4ms)
(41052) [BG(1)]     binding: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\typing_extensions.pyi (2ms)
(41052) [BG(1)]     parsing: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\_typeshed\__init__.pyi [fs read 1ms] (19ms)
(41052) [BG(1)]     binding: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\_typeshed\__init__.pyi (4ms)
(41052) [BG(1)]     parsing: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\types.pyi [fs read 1ms] (11ms)
(41052) [BG(1)]     binding: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\types.pyi (14ms)
(41052) [BG(1)]     parsing: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\abc.pyi [fs read 1ms] (2ms)
(41052) [BG(1)]     binding: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\abc.pyi (1ms)
(41052) [BG(1)]     parsing: C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\__init__.py [fs read 0ms] (17ms)
(41052) [BG(1)]     binding: C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\__init__.py ...
(41052) [BG(1)]       parsing: C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\errors.py [fs read 1ms] (19ms)
(41052) [BG(1)]       binding: C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\errors.py (5ms)
(41052) [BG(1)]       parsing: C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\main.py [fs read 1ms] (51ms)
(41052) [BG(1)]       binding: C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\main.py (15ms)
(41052) [BG(1)]       parsing: C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\networks.py [fs read 1ms] (25ms)
[Info  - 8:17:53 PM] (41052) Could not import 'email_validator' in file 'C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\networks.py'
[Info  - 8:17:53 PM] (41052)   Looking in stubPath 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\typings'
[Info  - 8:17:53 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\typings'
[Info  - 8:17:53 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\typings'
[Info  - 8:17:53 PM] (41052)   Looking in root directory of execution environment 'c:\Users\vrajasekhar\Py\PylanceBugReportWS'
[Info  - 8:17:53 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS'
[Info  - 8:17:53 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS'
[Info  - 8:17:53 PM] (41052)   Looking in extraPath 'C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages'
[Info  - 8:17:53 PM] (41052)   Attempting to resolve stub package using root path 'C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages'
[Info  - 8:17:53 PM] (41052)   Attempting to resolve using root path 'C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages'
[Info  - 8:17:53 PM] (41052)   Looking in extraPath 'c:\users\vrajasekhar\py\paradesign repo\nz pump station design tool\backend_working'
[Info  - 8:17:53 PM] (41052)   Attempting to resolve stub package using root path 'c:\users\vrajasekhar\py\paradesign repo\nz pump station design tool\backend_working'
[Info  - 8:17:53 PM] (41052)   Attempting to resolve using root path 'c:\users\vrajasekhar\py\paradesign repo\nz pump station design tool\backend_working'
[Info  - 8:17:53 PM] (41052)   Looking in extraPath 'C:\Users\vrajasekhar\Py\Paradesign Repo\NZ Pump Station Design Tool\backend_working\'
[Info  - 8:17:53 PM] (41052)   Attempting to resolve stub package using root path 'C:\Users\vrajasekhar\Py\Paradesign Repo\NZ Pump Station Design Tool\backend_working\'
[Info  - 8:17:53 PM] (41052)   Attempting to resolve using root path 'C:\Users\vrajasekhar\Py\Paradesign Repo\NZ Pump Station Design Tool\backend_working\'
[Info  - 8:17:53 PM] (41052)   Looking in python search path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\DLLs'
[Info  - 8:17:53 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\DLLs'
[Info  - 8:17:53 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\DLLs'
[Info  - 8:17:53 PM] (41052)   Looking in python search path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib'
[Info  - 8:17:53 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib'
[Info  - 8:17:53 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib'
[Info  - 8:17:53 PM] (41052)   Looking in python search path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310'
[Info  - 8:17:53 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310'
[Info  - 8:17:53 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310'
[Info  - 8:17:53 PM] (41052)   Looking in python search path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\.venv'
[Info  - 8:17:53 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\.venv'
[Info  - 8:17:53 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\.venv'
[Info  - 8:17:53 PM] (41052)   Looking in python search path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\.venv\Lib\site-packages'
[Info  - 8:17:53 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\.venv\Lib\site-packages'
[Info  - 8:17:53 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\.venv\Lib\site-packages'
[Info  - 8:17:53 PM] (41052)   Looking in bundled stubs path 'c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\bundled\stubs'
[Info  - 8:17:53 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\bundled\stubs'
[Info  - 8:17:53 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\bundled\stubs'
[Info  - 8:17:53 PM] (41052)   Looking for typeshed stdlib path
[Info  - 8:17:53 PM] (41052)   Looking for typeshed stdlib path
[Info  - 8:17:53 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib'
[Info  - 8:17:53 PM] (41052)   Typeshed path not found
[Info  - 8:17:53 PM] (41052)   Looking for typeshed third-party path
[Info  - 8:17:53 PM] (41052)   Looking for typeshed stubs path
[Info  - 8:17:53 PM] (41052)   Typeshed path not found
[Info  - 8:17:54 PM] (41052) Could not import 'email_validator' in file 'C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\networks.py'
[Info  - 8:17:54 PM] (41052)   Looking in stubPath 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\typings'
[Info  - 8:17:54 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\typings'
[Info  - 8:17:54 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\typings'
[Info  - 8:17:54 PM] (41052)   Looking in root directory of execution environment 'c:\Users\vrajasekhar\Py\PylanceBugReportWS'
[Info  - 8:17:54 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS'
[Info  - 8:17:54 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS'
[Info  - 8:17:54 PM] (41052)   Looking in extraPath 'C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages'
[Info  - 8:17:54 PM] (41052)   Attempting to resolve stub package using root path 'C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages'
[Info  - 8:17:54 PM] (41052)   Attempting to resolve using root path 'C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages'
[Info  - 8:17:54 PM] (41052)   Looking in extraPath 'c:\users\vrajasekhar\py\paradesign repo\nz pump station design tool\backend_working'
[Info  - 8:17:54 PM] (41052)   Attempting to resolve stub package using root path 'c:\users\vrajasekhar\py\paradesign repo\nz pump station design tool\backend_working'
[Info  - 8:17:54 PM] (41052)   Attempting to resolve using root path 'c:\users\vrajasekhar\py\paradesign repo\nz pump station design tool\backend_working'
[Info  - 8:17:54 PM] (41052)   Looking in extraPath 'C:\Users\vrajasekhar\Py\Paradesign Repo\NZ Pump Station Design Tool\backend_working\'
[Info  - 8:17:54 PM] (41052)   Attempting to resolve stub package using root path 'C:\Users\vrajasekhar\Py\Paradesign Repo\NZ Pump Station Design Tool\backend_working\'
[Info  - 8:17:54 PM] (41052)   Attempting to resolve using root path 'C:\Users\vrajasekhar\Py\Paradesign Repo\NZ Pump Station Design Tool\backend_working\'
[Info  - 8:17:54 PM] (41052)   Looking in python search path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\DLLs'
[Info  - 8:17:54 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\DLLs'
[Info  - 8:17:54 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\DLLs'
[Info  - 8:17:54 PM] (41052)   Looking in python search path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib'
[Info  - 8:17:54 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib'
[Info  - 8:17:54 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib'
[Info  - 8:17:54 PM] (41052)   Looking in python search path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310'
[Info  - 8:17:54 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310'
[Info  - 8:17:54 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310'
[Info  - 8:17:54 PM] (41052)   Looking in python search path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\.venv'
[Info  - 8:17:54 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\.venv'
[Info  - 8:17:54 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\.venv'
[Info  - 8:17:54 PM] (41052)   Looking in python search path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\.venv\Lib\site-packages'
[Info  - 8:17:54 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\.venv\Lib\site-packages'
[Info  - 8:17:54 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\.venv\Lib\site-packages'
[Info  - 8:17:54 PM] (41052)   Looking in bundled stubs path 'c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\bundled\stubs'
[Info  - 8:17:54 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\bundled\stubs'
[Info  - 8:17:54 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\bundled\stubs'
[Info  - 8:17:54 PM] (41052)   Looking for typeshed stdlib path
[Info  - 8:17:54 PM] (41052)   Looking for typeshed stdlib path
[Info  - 8:17:54 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib'
[Info  - 8:17:54 PM] (41052)   Typeshed path not found
[Info  - 8:17:54 PM] (41052)   Looking for typeshed third-party path
[Info  - 8:17:54 PM] (41052)   Looking for typeshed stubs path
[Info  - 8:17:54 PM] (41052)   Typeshed path not found
(41052) [BG(1)]       binding: C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\networks.py (6ms)
(41052) [BG(1)]       parsing: C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\tools.py [fs read 0ms] (5ms)
(41052) [BG(1)]       binding: C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\tools.py (1ms)
(41052) [BG(1)]       parsing: C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\types.py [fs read 0ms] (48ms)
(41052) [BG(1)]       binding: C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\types.py (11ms)
(41052) [BG(1)]     binding: C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\__init__.py (190ms)
(41052) [BG(1)]     parsing: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\weakref.pyi [fs read 0ms] (9ms)
(41052) [BG(1)]     binding: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\weakref.pyi (2ms)
(41052) [BG(1)]     parsing: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\_weakrefset.pyi [fs read 1ms] (3ms)
(41052) [BG(1)]     binding: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\_weakrefset.pyi (2ms)
(41052) [BG(1)]     parsing: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\collections\abc.pyi [fs read 1ms] (1ms)
(41052) [BG(1)]     binding: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\collections\abc.pyi ...
(41052) [BG(1)]       parsing: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\_collections_abc.pyi [fs read 1ms] (3ms)
(41052) [BG(1)]       binding: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\_collections_abc.pyi (1ms)
(41052) [BG(1)]     binding: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\collections\abc.pyi (4ms)
(41052) [BG(1)]   checking: c:\Users\vrajasekhar\Py\PylanceBugReportWS\example_utilities.py (426ms)
(41052) [BG(1)] analyzing: c:\Users\vrajasekhar\Py\PylanceBugReportWS\example_utilities.py (631ms)
(41052) Background analysis message: getDiagnosticsForRange
(41052) Background analysis message: getSemanticTokens full
(41052) [BG(1)] getSemanticTokens full at c:\Users\vrajasekhar\Py\PylanceBugReportWS\example_utilities.py (4ms)
(41052) Background analysis message: getSemanticTokens range
(41052) [BG(1)] getSemanticTokens range 0:0 - 3:0 at c:\Users\vrajasekhar\Py\PylanceBugReportWS\example_utilities.py (2ms)
(41052) Background analysis message: resumeAnalysis
(41052) Background analysis message: setFileOpened
(41052) Background analysis message: getDiagnosticsForRange
(41052) [FG] parsing: c:\Users\vrajasekhar\Py\PylanceBugReportWS\imported_type_annotation.py (3ms)
(41052) [FG] binding: c:\Users\vrajasekhar\Py\PylanceBugReportWS\imported_type_annotation.py (0ms)
(41052) Background analysis message: getDiagnosticsForRange
(41052) Background analysis message: getSemanticTokens full
(41052) [BG(1)] getSemanticTokens full at c:\Users\vrajasekhar\Py\PylanceBugReportWS\imported_type_annotation.py ...
(41052) [BG(1)]   parsing: c:\Users\vrajasekhar\Py\PylanceBugReportWS\imported_type_annotation.py (2ms)
(41052) [BG(1)]   binding: c:\Users\vrajasekhar\Py\PylanceBugReportWS\imported_type_annotation.py (0ms)
(41052) [BG(1)] getSemanticTokens full at c:\Users\vrajasekhar\Py\PylanceBugReportWS\imported_type_annotation.py (4ms)
(41052) Background analysis message: getDiagnosticsForRange
(41052) Background analysis message: getDiagnosticsForRange
(41052) Background analysis message: analyze
(41052) [BG(1)] analyzing: c:\Users\vrajasekhar\Py\PylanceBugReportWS\imported_type_annotation.py ...
(41052) [BG(1)]   checking: c:\Users\vrajasekhar\Py\PylanceBugReportWS\imported_type_annotation.py (4ms)
(41052) [BG(1)] analyzing: c:\Users\vrajasekhar\Py\PylanceBugReportWS\imported_type_annotation.py (4ms)
(41052) Background analysis message: resumeAnalysis
(41052) Background analysis message: setFileOpened
(41052) Background analysis message: getDiagnosticsForRange
(41052) [FG] parsing: c:\Users\vrajasekhar\Py\PylanceBugReportWS\homegrown_type_annotation_1.py (1ms)
(41052) [FG] binding: c:\Users\vrajasekhar\Py\PylanceBugReportWS\homegrown_type_annotation_1.py (1ms)
(41052) Background analysis message: getDiagnosticsForRange
(41052) [FG] parsing: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\typing.pyi [fs read 1ms] (74ms)
(41052) [FG] binding: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\typing.pyi (11ms)
(41052) [FG] parsing: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\typing_extensions.pyi [fs read 0ms] (6ms)
(41052) [FG] binding: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\typing_extensions.pyi (4ms)
(41052) [FG] parsing: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\_typeshed\__init__.pyi [fs read 1ms] (25ms)
(41052) [FG] binding: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\_typeshed\__init__.pyi (3ms)
(41052) [FG] parsing: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\types.pyi [fs read 1ms] (20ms)
(41052) [FG] binding: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\types.pyi (6ms)
(41052) [FG] parsing: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\abc.pyi [fs read 1ms] (2ms)
(41052) [FG] binding: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\abc.pyi (1ms)
(41052) [FG] parsing: C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\__init__.py [fs read 1ms] (15ms)
(41052) [FG] binding: C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\__init__.py ...
(41052) [FG]   parsing: C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\errors.py [fs read 0ms] (13ms)
(41052) [FG]   binding: C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\errors.py (7ms)
(41052) [FG]   parsing: C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\main.py [fs read 1ms] (41ms)
(41052) [FG]   binding: C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\main.py (18ms)
(41052) [FG]   parsing: C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\networks.py [fs read 0ms] (22ms)
[Info  - 8:17:59 PM] (41052) Could not import 'email_validator' in file 'C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\networks.py'
[Info  - 8:17:59 PM] (41052)   Looking in stubPath 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\typings'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\typings'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\typings'
[Info  - 8:17:59 PM] (41052)   Looking in root directory of execution environment 'c:\Users\vrajasekhar\Py\PylanceBugReportWS'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS'
[Info  - 8:17:59 PM] (41052)   Looking in extraPath 'C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve stub package using root path 'C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve using root path 'C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages'
[Info  - 8:17:59 PM] (41052)   Looking in extraPath 'c:\users\vrajasekhar\py\paradesign repo\nz pump station design tool\backend_working'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve stub package using root path 'c:\users\vrajasekhar\py\paradesign repo\nz pump station design tool\backend_working'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve using root path 'c:\users\vrajasekhar\py\paradesign repo\nz pump station design tool\backend_working'
[Info  - 8:17:59 PM] (41052)   Looking in extraPath 'C:\Users\vrajasekhar\Py\Paradesign Repo\NZ Pump Station Design Tool\backend_working\'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve stub package using root path 'C:\Users\vrajasekhar\Py\Paradesign Repo\NZ Pump Station Design Tool\backend_working\'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve using root path 'C:\Users\vrajasekhar\Py\Paradesign Repo\NZ Pump Station Design Tool\backend_working\'
[Info  - 8:17:59 PM] (41052)   Looking in python search path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\DLLs'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\DLLs'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\DLLs'
[Info  - 8:17:59 PM] (41052)   Looking in python search path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib'
[Info  - 8:17:59 PM] (41052)   Looking in python search path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310'
[Info  - 8:17:59 PM] (41052)   Looking in python search path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\.venv'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\.venv'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\.venv'
[Info  - 8:17:59 PM] (41052)   Looking in python search path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\.venv\Lib\site-packages'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\.venv\Lib\site-packages'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\.venv\Lib\site-packages'
[Info  - 8:17:59 PM] (41052)   Looking in bundled stubs path 'c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\bundled\stubs'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\bundled\stubs'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\bundled\stubs'
[Info  - 8:17:59 PM] (41052)   Looking for typeshed stdlib path
[Info  - 8:17:59 PM] (41052)   Looking for typeshed stdlib path
[Info  - 8:17:59 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib'
[Info  - 8:17:59 PM] (41052)   Typeshed path not found
[Info  - 8:17:59 PM] (41052)   Looking for typeshed third-party path
[Info  - 8:17:59 PM] (41052)   Looking for typeshed stubs path
[Info  - 8:17:59 PM] (41052)   Typeshed path not found
[Info  - 8:17:59 PM] (41052) Could not import 'email_validator' in file 'C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\networks.py'
[Info  - 8:17:59 PM] (41052)   Looking in stubPath 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\typings'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\typings'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\typings'
[Info  - 8:17:59 PM] (41052)   Looking in root directory of execution environment 'c:\Users\vrajasekhar\Py\PylanceBugReportWS'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS'
[Info  - 8:17:59 PM] (41052)   Looking in extraPath 'C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve stub package using root path 'C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve using root path 'C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages'
[Info  - 8:17:59 PM] (41052)   Looking in extraPath 'c:\users\vrajasekhar\py\paradesign repo\nz pump station design tool\backend_working'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve stub package using root path 'c:\users\vrajasekhar\py\paradesign repo\nz pump station design tool\backend_working'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve using root path 'c:\users\vrajasekhar\py\paradesign repo\nz pump station design tool\backend_working'
[Info  - 8:17:59 PM] (41052)   Looking in extraPath 'C:\Users\vrajasekhar\Py\Paradesign Repo\NZ Pump Station Design Tool\backend_working\'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve stub package using root path 'C:\Users\vrajasekhar\Py\Paradesign Repo\NZ Pump Station Design Tool\backend_working\'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve using root path 'C:\Users\vrajasekhar\Py\Paradesign Repo\NZ Pump Station Design Tool\backend_working\'
[Info  - 8:17:59 PM] (41052)   Looking in python search path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\DLLs'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\DLLs'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\DLLs'
[Info  - 8:17:59 PM] (41052)   Looking in python search path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib'
[Info  - 8:17:59 PM] (41052)   Looking in python search path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310'
[Info  - 8:17:59 PM] (41052)   Looking in python search path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\.venv'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\.venv'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\.venv'
[Info  - 8:17:59 PM] (41052)   Looking in python search path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\.venv\Lib\site-packages'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\.venv\Lib\site-packages'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\Py\PylanceBugReportWS\.venv\Lib\site-packages'
[Info  - 8:17:59 PM] (41052)   Looking in bundled stubs path 'c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\bundled\stubs'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve stub package using root path 'c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\bundled\stubs'
[Info  - 8:17:59 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\bundled\stubs'
[Info  - 8:17:59 PM] (41052)   Looking for typeshed stdlib path
[Info  - 8:17:59 PM] (41052)   Looking for typeshed stdlib path
[Info  - 8:17:59 PM] (41052)   Attempting to resolve using root path 'c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib'
[Info  - 8:17:59 PM] (41052)   Typeshed path not found
[Info  - 8:17:59 PM] (41052)   Looking for typeshed third-party path
[Info  - 8:17:59 PM] (41052)   Looking for typeshed stubs path
[Info  - 8:17:59 PM] (41052)   Typeshed path not found
(41052) [FG]   binding: C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\networks.py (8ms)
(41052) [FG]   parsing: C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\tools.py [fs read 1ms] (9ms)
(41052) [FG]   binding: C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\tools.py (1ms)
(41052) [FG]   parsing: C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\types.py [fs read 1ms] (32ms)
(41052) [FG]   binding: C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\types.py (6ms)
(41052) [FG] binding: C:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic\__init__.py (164ms)
(41052) [FG] parsing: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\weakref.pyi [fs read 1ms] (5ms)
(41052) [FG] binding: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\weakref.pyi (2ms)
(41052) [FG] parsing: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\_weakrefset.pyi [fs read 0ms] (1ms)
(41052) [FG] binding: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\_weakrefset.pyi (1ms)
(41052) [FG] parsing: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\collections\abc.pyi [fs read 0ms] (0ms)
(41052) [FG] binding: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\collections\abc.pyi ...
(41052) [FG]   parsing: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\_collections_abc.pyi [fs read 1ms] (1ms)
(41052) [FG]   binding: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\_collections_abc.pyi (1ms)
(41052) [FG] binding: c:\Users\vrajasekhar\.vscode\extensions\ms-python.vscode-pylance-2023.2.10\dist\typeshed-fallback\stdlib\collections\abc.pyi (2ms)
(41052) Background analysis message: analyze
(41052) [BG(1)] analyzing: c:\Users\vrajasekhar\Py\PylanceBugReportWS\homegrown_type_annotation_1.py ...
(41052) [BG(1)]   parsing: c:\Users\vrajasekhar\Py\PylanceBugReportWS\homegrown_type_annotation_1.py (1ms)
(41052) [BG(1)]   binding: c:\Users\vrajasekhar\Py\PylanceBugReportWS\homegrown_type_annotation_1.py (0ms)
(41052) [BG(1)]   checking: c:\Users\vrajasekhar\Py\PylanceBugReportWS\homegrown_type_annotation_1.py (3ms)
(41052) [BG(1)] analyzing: c:\Users\vrajasekhar\Py\PylanceBugReportWS\homegrown_type_annotation_1.py (4ms)
(41052) Background analysis message: getSemanticTokens full
(41052) [BG(1)] getSemanticTokens full at c:\Users\vrajasekhar\Py\PylanceBugReportWS\homegrown_type_annotation_1.py (1ms)
(41052) Background analysis message: getDiagnosticsForRange
(41052) Background analysis message: resumeAnalysis
(41052) Background analysis message: getDiagnosticsForRange
(41052) Background analysis message: getDiagnosticsForRange
(41052) Background analysis message: getDiagnosticsForRange
(41052) Background analysis message: setFileOpened
(41052) Background analysis message: getDiagnosticsForRange
(41052) [FG] parsing: c:\Users\vrajasekhar\Py\PylanceBugReportWS\homegrown_type_annotation_2.py (1ms)
(41052) [FG] binding: c:\Users\vrajasekhar\Py\PylanceBugReportWS\homegrown_type_annotation_2.py (0ms)
(41052) Background analysis message: getDiagnosticsForRange
(41052) Background analysis message: getSemanticTokens full
(41052) [BG(1)] getSemanticTokens full at c:\Users\vrajasekhar\Py\PylanceBugReportWS\homegrown_type_annotation_2.py ...
(41052) [BG(1)]   parsing: c:\Users\vrajasekhar\Py\PylanceBugReportWS\homegrown_type_annotation_2.py (1ms)
(41052) [BG(1)]   binding: c:\Users\vrajasekhar\Py\PylanceBugReportWS\homegrown_type_annotation_2.py (0ms)
(41052) [BG(1)] getSemanticTokens full at c:\Users\vrajasekhar\Py\PylanceBugReportWS\homegrown_type_annotation_2.py (3ms)
(41052) Background analysis message: analyze
(41052) [BG(1)] analyzing: c:\Users\vrajasekhar\Py\PylanceBugReportWS\homegrown_type_annotation_2.py ...
(41052) [BG(1)]   checking: c:\Users\vrajasekhar\Py\PylanceBugReportWS\homegrown_type_annotation_2.py ...
(41052) [BG(1)]     parsing: c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\typing.py [fs read 1ms] (47ms)
(41052) [BG(1)]     binding: c:\Users\vrajasekhar\AppData\Local\Programs\Python\Python310\Lib\typing.py (22ms)
(41052) [BG(1)]   checking: c:\Users\vrajasekhar\Py\PylanceBugReportWS\homegrown_type_annotation_2.py (73ms)
(41052) [BG(1)] analyzing: c:\Users\vrajasekhar\Py\PylanceBugReportWS\homegrown_type_annotation_2.py (73ms)
(41052) Background analysis message: resumeAnalysis

requirements.txt

This is similar to this issue.

A type alias definition must use an expression that is a valid type annotation. You're using a complex expression (a call to pydantic.constr()), which is not valid for a type annotation and is therefore not legal to use in a type alias definition. It is therefore interpreted as a variable, not a type alias.
As expected, mypy generates the same error in this case.

Thank you for your reply. Is there a particular reason the same warning isn't raised when importing the variable from a different module?

That's a false negative. Pyright should generate an error in this case. Mypy does. I've filed this bug to track this issue.

Thanks for addressing this. I'll raise this matter with pydantic, as canonical use of pydantic shouldn't register as erroneous, perhaps they can change the return type of their more complex field types...
I'll close this once I've raised that report and linked it here.

I regret that I missed this in my initial search for solutions - but there is a workaround for this problem. It feels clumsy, but offers at least one way to use canonical (if un-idiomatic) Pydantic without attracting the Wrath of Pylance. Applied to my example issue, the workaround allows me to do this:
import pydantic

class NewType(pydantic.ConstrainedStr):
    min_length = 1
    strip_whitespace = True

class Model(pydantic.BaseModel):
    my_field: NewType

... with no pylance warnings/errors.
My apologies for not having found this workaround prior to raising this issue. Thank you for your help.

I have raised this companion issue with Pydantic.

Here's another workaround that's actually quite clean - much better than the one I posted above. The following raises a Pylance error:
import pydantic

class MyClass(pydantic.BaseModel):
    myvar: pydantic.confloat(gt=0, lt=1)

x = MyClass(myvar=0.1)

But using typing.Annotated silences the Pylance error without adding too much weight to the use of confloat():
from typing import Annotated

import pydantic

class MyClass(pydantic.BaseModel):
    myvar: Annotated[float, pydantic.confloat(gt=0, lt=1)]

x = MyClass(myvar=0.1)

Based on this comment from Pydantic's maintainer Samuel Colvin, it sounds like Pydantic V2 will bring a similar feature natively to the table.


Improvement of regex-interpolation trap section

The problem
The section is unclear and seems to cause more confusion than it solves. For instance, phrases like "the latter only works sometimes" and  "$(…) lexically interpolates the given string. So <{…}> immediately breaks with more complicated inputs" provide no accurate description of anything.
The solution
The distinction between $(...) and <{...}> is currently described in the (updated) regex interpolation section of regex.pod6, which makes it clear that for the second example in the traps section to work it should have the to-be-interpolated string defined with a quoted hash, like this: my $x = 'ailemac"#"';, simply because <{...}> interpolates the return value/string as a regex. Since the situation is now clearly described in the regexes doc, this section may be deleted.

Just because something is described somewhere in the docs doesn't mean that people wouldn't erroneously use the wrong feature.

which makes it clear that for the second example in the traps section to work it should have the to-be-interpolated string defined with a quoted hash

Correct, and the point is that often this is used with arbitrary input, so quoting something is not really a solution to anything. IMO people should prefer $($x) over <{$x}> in almost all cases, but this is currently not the case.
That section should stay, but we can clarify it if it's unclear.

But trap documentation is created for a reason, and I don't think that reason has disappeared, so I would rather have it stay.

Can you clarify then what the reason is that this documentation was created? To me it seems the reason was that the difference between the two constructs $(...) and <{...} was not understood (likely because it was not clearly documented), a problem which has been dealt with in the updated regexes page.

...and the point is that often this is used with arbitrary input, so quoting something is not really a solution to anything. IMO people should prefer $($x) over <{$x}> in almost all cases, but this is currently not the case.

Can you give an example of arbitrary input that causes a problem? Or indicate why people should use $(...) over <{...}>, even though they do different things and one is not a straightforward alternative for the other? It seems to me that one should "prefer" '$(...)' in case literal interpolation is desired, and '<{...}>' in case interpolation as a regex is desired, in much the same way that people should "prefer" +` if addition is desired, and '-' if subtraction is desired.
In summary: I don't understand the point that this section is trying to communicate. And it seems that what it is communicating is confusing if not plain wrong. Even the main message in the heading <{$x}> vs $($x): Implicit EVAL, i.e. that <{...}> uses IMPLICIT EVAL while $(...) does not, does not seem correct; at any rate, both constructs can evaluate arbitrary code.

if there are issues with the text, it's much better if you raise the issues
and try to improve what we have instead of deleting it.
El mié., 7 ago. 2019 a las 9:12, Alexander<EMAIL_ADDRESS>escribió:

But trap documentation is created for a reason, and I don't think that
reason has disappeared, so I would rather have it stay.
Can you clarify then what the reason is that this documentation was
created? To me it seems the reason was that the difference between the two
constructs $(...) and <{...} was not understood (likely because it was
not clearly documented), a problem which has been dealt with in the updated
regexes page.
...and the point is that often this is used with arbitrary input, so
quoting something is not really a solution to anything. IMO people should
prefer $($x) over <{$x}> in almost all cases, but this is currently not the
case.
Can you give an example of arbitrary input that causes a problem? Or
indicate why people should use $(...) over <{...}>, even though they do
different things and one is not a straightforward alternative for the
other? It seems to me that one should "prefer" '$(...)' in case literal
interpolation is desired, and '<{...}>' in case interpolation as a regex is
desired, in much the same way that people should "prefer" +` if addition
is desired, and '-' if subtraction is desired.
In summary: I don't understand the point that this section is trying to
communicate. And it seems that what it is communicating is confusing if
not plain wrong. Even the main message in the heading <{$x}> vs $($x):
Implicit EVAL, i.e. that <{...}> uses IMPLICIT EVAL while $(...) does
not, does not seem correct; at any rate, both constructs can evaluate
arbitrary code.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/perl6/doc/pull/2940?email_source=notifications&email_token=AAAAD5GRGOITPQWJBODTTNLQDJYWHA5CNFSM4IJ2T7DKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3XOAKA#issuecomment-518971432,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAAD5BQY4RZGTZ47V6YDD3QDJYWHANCNFSM4IJ2T7DA
.

--
JJ

That's not answering the pivotal question: what is the point this section is trying to communicate? Without knowing what point needs to be communicated, there is no sense in trying to clarify the text.

Can you give an example of arbitrary input that causes a problem?

Let's say you want to match a flipped variable. Like $x.flip. Both $($x.flip) and <{$x.flip}> will work for simple cases, but not for all input (so it's not really like + and -). Example of input that exposes the problem is $x = ‘ailemac#’. Sometimes people use <{}> when they actually need $(). That sections tells not to do that.

That being said, I like the idea of removing some stuff that is not useful. But that section is not that.

El mié., 7 ago. 2019 a las 9:42, Aleks-Daniel Jakimenko-Aleksejev (<
<EMAIL_ADDRESS>escribió:

That being said, I like the idea of removing some stuff that is not
useful. But that section is not that.

Also, the best place to discuss this kind of things are issues, not pull
requests. Ideally, a PR should address an issue.

Let's say you want to match a flipped variable. Like $x.flip. Both $($x.flip) and <{$x.flip}> will work for simple cases, but not for all input (so it's not really like + and -). Example of input that exposes the problem is $x = ‘ailemac#’. Sometimes people use <{}> when they actually need $(). That sections tells not to do that.

I see. But the updated regex page (note: at the time of writing only to be found in the github repo, as it is not rendered under docs.perl6.org yet) essentially does the same, also in a side-by-side description/comparison of interpolation constructs.
Anyway, although I think it smells a bit of documentation bloat, I prepared a new/rewritten trap section that aims to retain the above pointer, but without the confusing languange.

I'll review this today. There are some things that need to be changed.

@AlexDaniel I noticed you self-assigned this PR. Does this mean you prefer to fix the issue with the regex-interpolation traps section yourself? Then I'll leave it for what it is and let it dangle...

@AlexDaniel I noticed you self-assigned this PR. Does this mean you prefer to fix the issue with the regex-interpolation traps section yourself? Then I'll leave it for what it is and let it dangle...

Not really, just wanted to make sure I don't forget about this (I have a backlog of things I have to resolve…).
For example, I don't like that the title of the section was renamed. The traps page (at least the sections that I wrote) are highly inspired by BashPitfalls, and I highly recommend to steal ideas from that resource. For example, every title there is a code snippet, and that's very useful. You can just scroll through the titles to refresh your skills, without trying to figure out what titles like “Interpolation constructs” and such mean.
I'm not sure if the rewritten section conveys the “if you're using <{}>, then you're most likely wrong” idea, but it probably should.

@AlexDaniel Thanks. I now better understand what the idea behind the traps section is (love Wooledge's Bash site btw). I changed the title of the interpolation section, and removed some construct explanation (that can be found via the link) to put more emphasis on the code. I guess this is more in line with what you have in mind.

I don't think I've seen anybody use <$foo>, but I did see people use <{code}> when they needed $(code). Maybe it should be adjusted, but this looks good to me.

I think the discussed issues should have been resolved (but I may have screwed up with the pushed commits, not sure, because github does indeed display one of the issues as not outdated. Should the issue be present after a merge, I'll fix it.)


add link to file github issue directly from demo

This is on top of PR #934.

This looks fine to me, would like to see a demo before merging though.

Looks good to me, go ahead and merge.

Released in 7.2.3


Add oniguruma package

I've followed this guide
step by step carefully. Yes

I've tested this package remotely and have excluded all broken builds.
Here is the links to the Travis/AppVeyor with status "All passed":

https://ci.appveyor.com/project/isaachier/hunter/build/1.0.428
https://travis-ci.org/isaachier/hunter/builds/358912772

I have submitted CI configs to https://github.com/ingenue/hunter targeting pkg.template branch,
see this merged pull request https://github.com/ingenue/hunter/pull/214

Testing:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.3540
https://travis-ci.org/ingenue/hunter/builds/359028156?utm_source=github_status&utm_medium=notification

Uploading:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.3544
https://travis-ci.org/ingenue/hunter/builds/359350412?utm_source=github_status&utm_medium=notification

Released: https://github.com/ruslo/hunter/releases/tag/v0.20.31


NullPointerException when you are trying cancel subscription ver 3.0.0-dev5

NullPointerException
Android 11
3.0.0-dev5
Description
java.lang.NullPointerException
        at com.apollographql.apollo3.internal.subscription.RealSubscriptionManager.removeSubscriptionById(RealSubscriptionManager.kt:370)
        at com.apollographql.apollo3.internal.subscription.RealSubscriptionManager.onCompleteServerMessage(RealSubscriptionManager.kt:354)
        at com.apollographql.apollo3.internal.subscription.RealSubscriptionManager.onOperationServerMessage(RealSubscriptionManager.kt:208)
        at com.apollographql.apollo3.internal.subscription.RealSubscriptionManager$SubscriptionTransportCallback$onMessage$1.run(RealSubscriptionManager.kt:410)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
        at java.lang.Thread.run(Thread.java:923)

Woohoo, thanks for the very first bug report on dev-3.x 🎉  🍾 ! Will look into this!
Also heads up that -dev releases are for developer previews so it's fine to look into what's happening and file bugs but bugs/breaking changes are expected. We'll change to -alpha when things stabilize a bit and drop the -alpha qualifier when API is stable.

Ok, I see, thank you for your feedback, actually, for unsubscribing, I use currently this method => apolloClient.subscriptionManager.stop() it stops and disconnects the client.

Ok, I see, thank you for your feedback, actually, for unsubscribing, I use currently this method => apolloClient.subscriptionManager.stop() it stops and disconnects the client.

Is there a reason you're not using the stable 2.5.4 version?

The problem with subscriptions, workaround from the GitHub doesn't work for me. only with 3.0.0
val connectionParams = mapOf(AUTH_TOKEN to token) subscriptionConnectionParams(SubscriptionConnectionParams(connectionParams))

I'm confused. Is there something in 2.5.4 that doesn't work and works in 3.0.0-dev5 ? Can you point to the original 2.5.4 issue? We might want to fix it there since it's the stable branch

@SergeyMilevskiy Since 3.x is moving fast, I'm going to close this one. Let me know if you want me to reopen it.


haskell.compiler.ghc901: drop LLVM version to 9

GHC 9.0.1 only supports LLVM 9 and spews a lot of warnings about LLVM 10
when using the LLVM backend atm.
See also: https://www.haskell.org/ghc/download_ghc_9_0_1.html

Motivation for this change
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg build haskell.packages.ghc901.hello

Okay, since I've discovered some issues with how we handle LLVM atm and it seems to require a set rebuild (currently still waiting on the current build finishing to start a new rotation), I'm gonna make this into a bigger PR that changes and refactors LLVM-related stuff for our GHCs, in particular:

[x] Inherit llvmPackages from the ghc derivation in the package sets
[x] Use LLVM 9 for GHC 9.0.1
[ ] Upgrade all other GHC LLVM versions to the latest supported (for e. g. aarch64-darwin support)
[ ] Unify the use LLVM condition in the compiler expressions an ghcWithPackages


[REQ] Improvements to UserGroup & UserRule tables

Both tables only record the user ID, would it be possible to have a column to automatically search for the Name of the user ID just for easier identification?
This name would be automatically taken based on the User table column name, and placed in the UserGroup & UserRule tables when we register someone in them.

User ID is the only source of truth for user identification, name and other columns can be pretty much the same for other users. Ideally some other app should be managing the users using those tables.


[FEAT] Intervall Trigger with fixed starting point

Problem Description
Sometimes you want to trigger something every hour at full hour.
Therefor you have to create 24 TimeTriggers. Don´t want to think about every quarter hour. 😮
It would be nice if you can preperate a trigger with a starting point or smth like that.
Proposed Solution
I tinkered around a bit and created a Trigger Class based on the OrTrigger.
At first you give a general TimeTrigger and then some intervall informations (hours, minutes, seconds)
It creates the self.triggers list with the initial Timetrigger and for each delta an extra Timetrigger
Some code i figured out:
class TimeIntervallTrigger(OrTrigger):
    _t = int | float

    def __init__(self, trigger: TimeTrigger, seconds: _t = 0, minutes: _t = 0, hours: _t = 0) -> None:
        self.intervall_delta = timedelta(hours=hours, minutes=minutes, seconds=seconds)
        self.triggers: list[BaseTrigger] = self._create_triggerlist(trigger)
        self.current_trigger: BaseTrigger = None

    def _create_triggerlist(self, trigger: TimeTrigger):
        now = datetime.now()
        target = datetime(
            now.year,
            now.month,
            now.day,
            trigger.target_time[0],
            trigger.target_time[1],
            trigger.target_time[2],
            tzinfo=trigger.tz,
        )
        triggers: list[TimeTrigger] = []
        while target.date() == now.date():
            triggers.append(TimeTrigger(hour=target.hour, minute=target.minute, seconds=target.second, utc=target.tzinfo))
            target = target + self.intervall_delta
        return triggers

in the program you can use it like that: (it prints every 10 seconds; at 00:00:10, 00:00:20, 00:00:30...)
@Task.create(
    TimeIntervallTrigger(
        trigger=TimeTrigger(hour=0, minute=0, seconds=0),
        seconds=10,
    )
)
async def cron_print():
    print(f"cron at {datetime.now()}")

The code is not optimized yet.
As alternative to a class I think about a function which returns a Trigger list to use in a regular OrTrigger.
Alternatives Considered
As alternative to a class I think about a function which returns a Trigger list to use in a regular OrTrigger.
Additional Information
What are your thoughts about it?
Code of Conduct

[X] I agree to follow the contribution requirements.

I actually do like this idea - I have a similar pattern in my code. Not fully sure of how it should be designed though (or if the code snippet here is the best way it could be designed), but in general I'm all for this.

I dislike the nomenclature you've opted for, but overall its a good suggestion. I'd welcome a pr for it

thanks for the positiv feedback.
I also think about an extra argument (offset) for IntervallTrigger but cannot figure it out how to resolve it.
The nomenclature was not the main aspect here and will be optimize.
Would you prefer the class solution or only a function which creates multiple Triggers?


Schema not recognised by cherry bomb

Hello,
Thank you for your project, however I aim unable to run it on the Lichess spec due to the following error:
$ cherrybomb --file ../berserk/lichess-spec-fixed.json --profile passive

╭━━━┳╮╱╱╱╱╱╱╱╱╱╱╱╱╭╮╱╱╱╱╱╱╱╭╮
┃╭━╮┃┃╱╱╱╱╱╱╱╱╱╱╱╱┃┃╱╱╱╱╱╱╱┃┃
┃┃╱╰┫╰━┳━━┳━┳━┳╮╱╭┫╰━┳━━┳╮╭┫╰━╮
┃┃╱╭┫╭╮┃┃━┫╭┫╭┫┃╱┃┃╭╮┃╭╮┃╰╯┃╭╮┃
┃╰━╯┃┃┃┃┃━┫┃┃┃┃╰━╯┃╰╯┃╰╯┃┃┃┃╰╯┃
╰━━━┻╯╰┻━━┻╯╰╯╰━╮╭┻━━┻━━┻┻┻┻━━╯
╱╱╱╱╱╱╱╱╱╱╱╱╱╱╭━╯┃
╱╱╱╱╱╱╱╱╱╱╱╱╱╱╰━━╯       v1.0.0

Starting Cherrybomb...
Opening OAS file...
Parsing OAS file...
Error: Error creating OAS struct: data did not match any variant of untagged enum SchemaRef

I believe it's the same as https://github.com/blst-security/cherrybomb/issues/100.
You can find the spec online at: https://lichess.org/api.

Thanks for reaching out :)

Hey @OmerWow! What is the progress of this issue? I'm trying your tool with openapi.json generated by FastAPI but have the same error as @kraktus

Hi @karolpawlowski, we are still checking it out, we'll should get back to you pretty soon, sorry for the delay

Hi, I am also running into the same error:
Starting Cherrybomb...
Opening OAS file...
Parsing OAS file...
Error: Error creating OAS struct: data did not match any variant of untagged enum SchemaRef

I'm using an openapi.json file generated by swagger.

Hi, I am also running into the same error:
Starting Cherrybomb...
Opening OAS file...
Parsing OAS file...
Error: Error creating OAS struct: data did not match any variant of untagged enum SecSchemeRef
Cherrybomb v1.0.0 within the ECR provided container


Added 4 Datasets by MihirRajeshPanchal

🛠 Fixes Issue
Closes #244
👨💻 Changes proposed

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers
MonkeyPox Patient Dataset added by MihirRajeshPanchal
Google Play Store Dataset added by MihirRajeshPanchal
World Population Dataset added by MihirRajeshPanchal
Milk Quality Dataset added by MihirRajeshPanchal
Clueless Community Profile : https://www.clueless.tech/profile/admin/105093933941494861305
📷 Screenshots

Sorry @nikhil25803 about the separate Pull requests and Issues I created .
I have merged all the newly made datasets into one PR

Good one @MihirRajeshPanchal
Congrats 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow these steps.

Star this repository. ⭐
SignIn / SignUp in [ClueLess Website](https://www.clueless.tech/) .
Go to the profile section from the top right-hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard!
And don’t forget to share your achievement with your friends.

@nikhil25803 https://www.clueless.tech/profile/admin/105093933941494861305


Support flysystem 3

I just added support of Flysystem v3 in 99a30ebea11f9780ff2238fee8782703d1311d4d, which is available from v0.4.0


import module in linux

I downloaded a ps1 module and i am not able to import the module into. Can you provide steps to import. below is what i am attempting to import for testing.
https://github.com/dafthack/MailSniper

Steps to reproduce
Expected behavior
Actual behavior
Environment data

> $PSVersionTable

That's a script (.ps1) not a module (.psm1).
Either dot-source it, to import the functions to your current scope:
. .\MailSniper.ps1

Or rename it to .psm1 and then import-module .\MailSniper.psm1

Ahhh okay thank you!
On Sat, Oct 1, 2016, 12:02 AM Joel Bennett<EMAIL_ADDRESS>wrote:

That's a script (.ps1) not a module (.psm1).
Either dot-source it, to import the functions to your current scope:
. .\MailSniper.ps1
Or rename it to .psm1 and then import-module .\MailSniper.psm1
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/PowerShell/PowerShell/issues/2399#issuecomment-250892833,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATwSo3Ts34rQNUNPuZRl_SeeUI6V1-7Xks5qveltgaJpZM4KLnR4
.

I tried both ways to no avail.

What is the error when you dot-sourcing?

PS /root> . .\MailSniper.ps1
. : The term '.\MailSniper.ps1' is not recognized as the name of a cmdlet,
function, script file, or operable program. Check the spelling of the name, or
if a path was included, verify that the path is correct and try again.
At line:1 char:3

. .\MailSniper.ps1

+ CategoryInfo          : ObjectNotFound: (.\MailSniper.ps1:String) [], Co

mmandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
PS /root> . .\MailSniper.psm1
. : The term '.\MailSniper.psm1' is not recognized as the name of a cmdlet,
function, script file, or operable program. Check the spelling of the name, or
if a path was included, verify that the path is correct and try again.
At line:1 char:3

. .\MailSniper.psm1

+ CategoryInfo          : ObjectNotFound: (.\MailSniper.psm1:String) [], C

ommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
PS /root> .\MailSniper.psm1
.\MailSniper.psm1 : The term '.\MailSniper.psm1' is not recognized as the name
of a cmdlet, function, script file, or operable program. Check the spelling of
the name, or if a path was included, verify that the path is correct and try
again.
At line:1 char:1

.\MailSniper.psm1

  + CategoryInfo          : ObjectNotFound: (.\MailSniper.psm1:String) [], C
 ommandNotFoundException
  + FullyQualifiedErrorId : CommandNotFoundException

if i am in the directory and do the following i get this
PS /root/MailSniper> ./MailSniper.psm1
PS /root/MailSniper>
PS /root/MailSniper> Import-Module ./MailSniper.psm1
PS /root/MailSniper>

Disregard. I got it to work now. Sorry for the trouble!

@usmarine2141 Im having the same trouble. I got it to work when i cd into the directory. But other than than it does not recognize it.

@EkremSel - you need to be in the directory where this is downloaded for you to be able to import scripts into your session which is a standard behaviour (since PowerShell v1)
The exception to this is if you have a PowerShell Module in one of the paths that is in the PSModulePath environmental variable then you can call Import-Module <Module Name>

Thanks
Sezai Ekrem SELAH
Selah Shipbuilding and Repair Co.
Member of Board
www.selahshipyard.com

On May 21, 2018, at 15:59, Ryan Yates<EMAIL_ADDRESS>wrote:
@EkremSel - you need to be in the directory where this is downloaded for you to be able to import scripts into your session which is a standard behaviour (since PowerShell v1)
The exception to this is if you have a PowerShell Module in one of the paths that is in the PSModulePath environmental variable then you can call Import-Module
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Allow user to type specific labels when suggesting a project

Projects often have different labels than the ones that are on the checkbox list:

When suggesting projects, we should be able to type in the labels that are used by the project.
I suggest we add a textbox for the user to type the labels that he wants (as a CSV)

Of course, in an ideal world, after putting the URL of the GitHub project, all the labels for that project should be fetched and we should be able to select the ones we want to promote, but this can be for another issue ;).

relates to #967

Thanks for reporting this @caioproiete! I'm going to close this one as it's a duplicate of the earlier issue #967, so please keep an eye on that issue for updates.


Allow define multiple plugin with separated  -env.d.ts

Describe the bug
we can via multiple plugins:
  "plugins": [
      {
        "name": "@0no-co/graphqlsp",
        "schema": "http://localhost:9001/shop-api",
        "tadaOutputLocation": "./e2e/graphql/graphql-shop-env.d.ts"
      },
      {
        "name": "@0no-co/graphqlsp",
        "schema": "http://localhost:9001/admin-api",
        "tadaOutputLocation": "./e2e/graphql/graphql-admin-env.d.ts"
      }
    ]

it will correct generated graphql-shop-env.d.ts and graphql-admin-env.d.ts
but cause of  each -env.d.ts have the same declare module will typings merge via  interface setupSchema
declare module 'gql.tada' {
  interface setupSchema {
    introspection: introspection
  }
}

if we want to create two individual grapql
import { initGraphQLTada } from '@semic/testing';
import type { introspection } from './graphql-admin-env.js';

export const graphql = initGraphQLTada<{
  introspection: introspection;
}>();

import { initGraphQLTada } from '@semic/testing';
import type { introspection } from './graphql-shop-env.js';

export const graphql = initGraphQLTada<{
  introspection: introspection;
}>();

only one is valid it's conflict , how we can resolve this?
Reproduction

gql.tada version
"gql.tada": "1.4.3",
Validations

[X] I can confirm that this is a bug report, and not a feature request, RFC, question, or discussion, for which GitHub Discussions should be used
[X] Read the docs.
[X] Follow our Code of Conduct

Duplicate of https://github.com/0no-co/gql.tada/issues/190


Data section diagram is actually the one from the Identity section

https://docs.microsoft.com/en-us/security/zero-trust/data / Traditional data security objectives section:
This is diagram is actually taken from the Identity section, I'm sure not the one intended for this section.

Thank you for catching this! I am opening a PR to replace with the correct image.


coqPackages.CoLoR: 1.7.0 → 1.8.1

Motivation for this change
Support for recent versions of Coq.
Things done

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

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

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

@GrahamcOfBorg build coqPackages_8_13.CoLoR