Web UI - Error loading available metrics!

Bug Report
What did you do?
Successfully upgraded Prometheus 2.0 to 2.15.0-rc0 and then open WEB UI.
What did you expect to see?
I expect /graph page without error and with working search suggest drop-down list.
What did you see instead? Under which circumstances?

Open Web UI behind Apache proxy on https://prometheus.company.org/ via Google Chrome.
I am forwarded to https://prometheus.company.org/graph page where I see "Error loading available metrics!" error.
Search suggest drop-down list is not working, there are no suggestions.

Environment

System information:

Linux 3.10.0-1062.4.1.el7.x86_64 x86_64

Prometheus version:

prometheus, version 2.15.0-rc.0 (branch: HEAD, revision: 61f1953c50148b3857bad6ab9a5622e1f1277695)
  build user:       root@67bb57f8015b
  build date:       20191218-17:10:23
  go version:       go1.13.5

Prometheus parameters:

/opt/prometheus/prometheus --storage.tsdb.retention.time=60d --storage.tsdb.retention.size=98GB --config.file=/opt/prometheus/prometheus.yml --storage.tsdb.path=/opt/prometheus/data --web.external-url=https://prometheus.company.org/ --web.console.templates=/opt/prometheus/consoles --query.timeout=1m --web.read-timeout=1m --web.route-prefix=/

That might be related to a bug that was fixed in 2.15.1. could you check? Also, do you have the requests/response? Thanks

I upgraded Prometheus to the latest version - 2.15.1, but I still have the problem.
Request:
Request URL: https://prometheus.monetplus.cz/api/v1/label/__name__/values?_=1577954456741 Request Method: GET Status Code: 422 Unprocessable Entity
Response:
{"status":"error","errorType":"execution","error":"block: 01DRVWKQ2RT4YA8QT23G09XMNZ: get postings offset entry: invalid size"}

Have got the same issue here, is there anything I can provide you with to help solve the issue?

I also have the same issue. I tried rolling back to v2.14.0 but my data is still empty. I hope that it's not permanently lost... the data directory still shows a size of 150mb

@gbolo Hmm... so 2.15 introduced this? And to clarify, this is only on the old web UI on /graph, right? Or are you getting the same problem on /new/graph (the new React UI)?
It's interesting because there weren't any changes directly to the old graph UI code since 2.14 got released on Nov 11, 2019: https://github.com/prometheus/prometheus/commits/master/web/ui/static/js/graph/index.js

Related to #6418

@roidelapluie Ah thanks. I didn't see the TSDB-specific error. So not a UI problem then.

/cc @brian-brazil

Was the block in question created by 2.15 or an earlier version? Can you share the HTTP request, and the index file?

@brian-brazil The HTTP request is in https://github.com/prometheus/prometheus/issues/6535#issuecomment-570146356, just the normal fetching of all metric names.

@juliusv I have this problem also in the new React UI, but with different error message:

Warning: Error fetching metrics list: Unexpected response status when fetching metric names: Unprocessable Entity

HTTP request in new React UI:
Request URL: https://prometheus.company.org/api/v1/label/__name__/values
Request Method: GET
Status Code: 422 Unprocessable Entity

Response:
{"status":"error","errorType":"execution","error":"block: 01DS1P0FNEAM2YPR8DAKCACNDJ: get postings offset entry: invalid size"}

@Rohlik Thanks!
For @brian-brazil's questions, could you share data/01DS1P0FNEAM2YPR8DAKCACNDJ/meta.json and data/01DS1P0FNEAM2YPR8DAKCACNDJ/index (careful, might contain sensitive data if your metrics are sensitive), as well as whether the time range in the block's meta.json file happened before or after the upgrade to 2.15?

@brian-brazil here you have what you need :)
meta.json:
{
        "version": 1,
        "ulid": "01DS1P0FNEAM2YPR8DAKCACNDJ",
        "minTime":<PHONE_NUMBER>000,
        "maxTime":<PHONE_NUMBER>000,
        "stats": {
                "numSamples": 343318557,
                "numSeries": 54892,
                "numChunks": 2861464
        },
        "compaction": {
                "level": 4,
                "sources": [
                        "01DRW3F8TFKRG0JYWVH908TA8Y",
                        "01DRWAB02PH017ZB9ZEQHX5X38",
                        "01DRWH6QATKYJ8S6HXP665NF25",
                        "01DRWR2EJFJM21WKM8GQ405APT",
                        "01DRWYY5TP3R2YNNQGK60JQMKQ",
                        "01DRX5SX3F62WHSYZ2NVYXC4MD",
                        "01DRXCNMABS6A4ZQ6AYXPX26PR",
                        "01DRXKHBKRZ0AXT2W3CK377R9W",
                        "01DRXTD2TCT1BVCD52RP4B337K",
                        "01DRY18T327QE2GAQH1P49V5DE",
                        "01DRY84HANDP7G549NWBB3WCFB",
                        "01DRYF08J50XH6EBC1B0RFSHRG",
                        "01DRYNVZTV50A6FJKNQE5S8QJE",
                        "01DRYWQQ2S842T024J37BYYT2G",
                        "01DRZ3KEB17CERPWRTASRN285S",
                        "01DRZAF5JN6CTBBXWR0KSTKDMG",
                        "01DRZHAWV3MSH0CE4SC1Y22QE6",
                        "01DRZR6M34CT87MYANMSBXDKVT",
                        "01DRZZ2BA5ZRVCZ00PR95BTJ9F",
                        "01DS05Y2J6QJHRBNN9P3GJCKAF",
                        "01DS0CSSTHBDGPRN32MWRWJT7Z",
                        "01DS0KNH2BZ5N828SX5EDM2XCA",
                        "01DS0TH8ACKW736WAD9SQ21K0B",
                        "01DS11CZJMK2Q35WHEC7EAFDH9",
                        "01DS188PTKE5VQ4C8XVZJCJ4RA",
                        "01DS1F4E32AAG8SDCYDDTNF7RZ",
                        "01DS1P05AFF8DPYM2XZY2XKVJV"
                ]
        }
}

index file have 27MB, so I uploaded it on GDrive - https://drive.google.com/file/d/1NXQbZqBDRqJwCPzUzgEI3BIeVUgEdUIR/view?usp=sharing
The time range in meta.json is related to time before upgrade to higher version.

Okay, looks like the issue here is that the postings offset table isn't sorted - which it should be.

So the sorting was only added in https://github.com/prometheus/tsdb/pull/216, which went into 2.1.0.
Given that noone should be using 2.0.0 for a variety of reasons (there are far worse bugs than this), I propose that we detect this at startup and error out rather than trying to deal with it gracefully. This would mean that a straight upgrade from 2.0.0 would no longer work.

Even if you dont use 2.9 you might still have 2.0 blocks around. I would prefer some kind of repairs here.

2.9 would have compacted them down at some point.

@gbolo Hmm... so 2.15 introduced this? And to clarify, this is only on the old web UI on /graph, right? Or are you getting the same problem on /new/graph (the new React UI)?
It's interesting because there weren't any changes directly to the old graph UI code since 2.14 got released on Nov 11, 2019: https://github.com/prometheus/prometheus/commits/master/web/ui/static/js/graph/index.js

sorry to confuse this issue with another one I had. Please ignore my comment

Thank you. After upgrade to the latest version of Prometheus is everything good.


Make everything searchable

This is a (multiple allowed):

[x] feature-discussion (RFC)

SocialPlexus Framework Core Version: N/A

Platform and Target: N/A

What you did
N/A
What happened
N/A
What you expected to happen
N/A

This should probably be another plug-in

https://github.com/SocialPlexus/search

This issue was moved to SocialPlexus/search#2


issue with exceptions

code
command -send <number>:
	trigger:
		set {_g} to "0"
		retrieve member with id {_m} from {_g} and store it in {_me}
		open private channel of {_me} and store it in {_c}
		post "%arg-1%" to {_c}
		broadcast "%last disky exception%"

Issue: if used a unknow member id, the execution stops

Should be fixed here:
https://github.com/DiSkyOrg/DiSky/commit/17f75012aa978b9d125e48e3e191d377b5cc78b1
Tysm for the report!


unit tests for changes

This is now filemap.

FileMap is just an alias for HashMap<String, StringBuffer> now.


book: Acquisition outdated

At https://defmt.ferrous-systems.com/acq-rel, the book talks about if let Some(logger) = Logger::acquire() {. However, the latest API documentation (and source code) have acquire() return the unit value.
I don't have any fix to offer for the book, because I'd rely on the book to understand how it's supposed to be used :-)
(In particular, I'd love to make a note that I've dropped a log line and make the writer stop writing, because for my logger I neither want to create a critical section nor multiple channels -- and given I'm working with a multithreaded OS I can't just keep ignoring data sent from the later caller until its release is called, for the other thread may continue -- but that's off topic for here, as this issue is just about the inconsistency between book and docs).

I believe this is an error on the book part. I see the API changed quite some time ago and perhaps the example was not updated.  Thank you for reporting this and apologies it is confusing.  I will add this to our triage.

Closed in favor of https://github.com/knurling-rs/defmt/issues/906.


Noob help

Can anyone explain to me how I don't need to make a product Model for products to be saved into the database and whatnot.  I'm extreme confused. I follow the guide on adding products and I'm even more lost.

Shoppe already has all the basic models required. To add a product you login to the admin panel (at /shoppe by default), go to products and create

@deanperry i keep getting an error when i try to add products that way
ArgumentError in Shoppe::ProductsController#create
string contains null byte

What's your setup? What database are you using, SQLite, MySQL or PostgreSQL? Also what version of Ruby and also what version of Rails?
Dean Perry
Sent from Outlook on my iPhone
On Sat, Mar 14, 2015 at 4:30 PM -0700, "5sp4lr"<EMAIL_ADDRESS>wrote:
@deanperry i keep getting an error when i try to add products that way
ArgumentError in Shoppe::ProductsController#create
string contains null byte
—
Reply to this email directly or view it on GitHub.

database - postgresql
ruby version - 2.1.5
rails version -  4.0.1

Ok. I'm not sure if Shoppe has been tested with PostgreSQL. It has been fully tested on MySQL however but I'll see if I can look into Postgres support. I don't have any experience with it so I'll have to get it installed first and play around with it.
Dean Perry
Sent from Outlook on my iPhone
On Sat, Mar 14, 2015 at 5:26 PM -0700, "5sp4lr"<EMAIL_ADDRESS>wrote:
database - postgresql
ruby version - 2.1.5
rails version -  4.0.1
—
Reply to this email directly or view it on GitHub.

@deanperry  it appears that this error only comes up when i try to add an image with the product. :c

Ah yes, I think that's one of the plugins we are using for image uploads

I've had a look into this issue today and it's a bug in Rails 4.2.0.
It is fixed in Rails 4.2.1 (using 4.2.1.rc4 doesn't show the error) - https://github.com/rails/rails/pull/17680

@5sp4lr  is closed. :D


Document how to implement HttpClient's delegating handlers

Type of issue
Typo
Description
The docs do not have a basic example on how to implement HttpClient's delegating handlers without dependency injection, something like:
private static readonly HttpClient MyClient =
    new HttpClient(
        new AddBearerTokenDelegatingHandler(
            new HttpClientHandler()))
    {
        BaseAddress = new Uri(ConfigurationManager.AppSettings["MyUri"])
    };

public class AddBearerTokenDelegatingHandler : DelegatingHandler
{
    public AddBearerTokenDelegatingHandler(HttpMessageHandler innerHandler)
        : base(innerHandler)
    {
    }

    protected override Task<HttpResponseMessage> SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
    {
        var token = GetBearerToken();
        if (!string.IsNullOrWhiteSpace(token))
        {
            request.Headers.Add("Authorization", $"Bearer {token}");
        }

        return base.SendAsync(request, cancellationToken);
    }

    private static string GetBearerToken()
    {
        var principal = Thread.CurrentPrincipal as ClaimsPrincipal;
        var identity = principal?.Identity as ClaimsIdentity;
        var claims = identity?.Claims;

        return claims?.FirstOrDefault(claim => claim.Type == ClaimTypes.Authentication)?.Value;
    }
}

This would be even more useful considering that the docs somehow recommend a static instance and there' soo much boilerplate around HttpClient usage everywhere.
Page URL
https://learn.microsoft.com/en-us/dotnet/fundamentals/networking/http/httpclient
Content source URL
https://github.com/dotnet/docs/blob/main/docs/fundamentals/networking/http/httpclient.md
Document Version Independent Id
857f2b65-3e05-2cb7-9820-05dddad22605
Article author
@IEvangelist
Metadata

ID: 4e2c563b-3150-f2a1-2afa-711cf3c022bf
Service: dotnet-fundamentals

Wrong type of issure, reopened in #42098.


Bytecode

Before we start instrumenting anything else we need to bite the bullet and speed things up with bytecode. The POC works we need speed for usability.

This may change how packages interface with sauros so we should do this before we setup things for packages any further

no. leave it. stop


[BUG] Lexicon Navigation

Clicking a satellite subsection in the Lexicon Navigation will expand the component accordion. This also happens when you're in another section and click the satellite link.

I'm not trolling you this time @plhnk :P

fixed in #846 — thanks @victorvalle !

fixed in #846 — thanks @victorvalle !


Method 2: The Unzip Method is not work in v1.2.2

Can not load Plugin in PS when I used v1.2.2, but v1.2.0 and v1.1.7 are fine. Is there any difference between v1.2.2 and the previous one？

i unzipped it on the adobe addons folder and it worked for both versions

Same here. Photoshop is version 2022. Tried using the clicking install but it won't recognize it. The unzipping doesn't work either.


Invalid Built-In 2FA key

Describe the bug
After every update I have to reconfirm the login credentials to the Amazon service. After reboot of HA I always got a new 2FA key from Amazon automatically and entered this in the HA-Alexa-Integration dialog. And it worked!
But after the last update I get the message "Invalid Built-In 2FA key" after submitting the login data and 2FA key. although I have entered the just received 2FA-Key via SMS from Amazon.
An ideas? Thanks!

Dupe of #1617. Please search before opening new issues.


Documentation on javascript

Hello.
I am trying to use semantic ui on a new project, while I can get the html to render properly (overriding the styles is super hard btw), there is no javascript documentation for several components.
Taking in the example of the  "Menu" from the docs, the exact first one "Browse Courses" is impossible to replicate, you get the html, but nothing will happen without the required javascript.
To get the dropdown to work you use this javascript :
Template.mainheader.onRendered(function(){
    console.log('mainheader... rendered');
    this.$('.ui.dropdown').dropdown({
        on: 'hover'
    });
});

But for the Browse Courses link there is no javascript. Are we supose to implement our own solution?
On the front page it says "Intuitive javascript", but it should also come with some docs.

I failed to understand that there is the concept of "Modules" and thats where the javascript is.
My bad.


What is the status of this project?

Hi, the idea of zkPoEX is very cool. While I notice that no updates in recent 1 year.
I wonder what is the status of this project, and will it continue to be advanced? Thanks~

Hi,
Thanks for reaching out! I'm currently busy with other projects and haven't had the time to continue development on zkPoEX. However, if the community is interested in picking it up, I'd be happy to support 🍊
Best,
zkoranges


Open API Overwrites Models In Schema

Describe the feature
I've put this as a feature request rather than a bug as it appears to be documented behaviour in the underlying Swagger implementation.  Basically, if you create two classes with the same name, but in a different package, you only end up with one underlying model in the schema which means your API documentation is now wrong!
In other words, if I have an API for Thing1 and an API for Thing2 and I create a package structure like
thing1
  dto
    CreationDTO
    UpdateDTO
thing2
  dto
    CreationDTO
    UpdateDTO

Then any API documentation for thing2 will refer to the DTOs for Thing1 which isn't good...
Additional context
This is down to the fact that the swagger model generator, by default, just uses the class name - not the fully qualified name.  This can be quite a pain if you want to have models called UpdateRequest or UpdateDTO or similar and keep the names consistent.  Obviously, you could rename to Thing1UpdateRequest and Thing2UpdateRequest but there is are some alternative options discussed here
https://github.com/ministryofjustice/prison-api/pull/273
https://github.com/springfox/springfox/issues/182
and this thread (for .NET) suggests a solution by overriding the schemaID generation function in Swagger / OpenAPI
https://stackoverflow.com/questions/46071513/swagger-error-conflicting-schemaids-duplicate-schemaids-detected-for-types-a-a

I've had a look into this by the way.  There is an existing OpenAPI annotation which can be used to get round this behaviour, which is called APIModel
https://docs.swagger.io/swagger-core/v1.5.0/apidocs/io/swagger/annotations/ApiModel.html
In there, you can provide a different value for the name which will be used in the OpenAPI schema but you have to manually check your codeback before you know whether you have any naming conflicts.
I'm currently looking into writing a custom TypeNameResolver.  Implementing it in the OpenAPI plugin was easy (provide an option to set it in OpenAPIOptions, pass it to the JacksonModelConverterFactory and then on to the JacksonModelConverter) but I'm trying to work out how often it gets called so I can work out if there is a way of raising an error on duplicate model names

This helped me:
TypeNameResolver.std.setUseFqn(true);


Could not find a version that satisfies the requirement openvino==2022.1.0

ERROR: Could not find a version that satisfies the requirement openvino==2022.1.0 (from -r requirements.txt (line 6)) (from versions: 2021.2, 2021.3.0, 2021.4.0, 2021.4.1, 2021.4.2)
ERROR: No matching distribution found for openvino==2022.1.0 (from -r requirements.txt (line 6))

Use python 3.8 or 3.9
Where is no openvino==2022.1.0 yet for python 3.10+

python 3.8
you can use openvino: 2022.1.0

@MonoBen Try updating PIP to the highest version.

I used python 3.9 and update the pip.

the same issue on Ubuntu

Using windows wsl, with ubuntu, after installing python 3.9 with:

sudo apt install python3.9
Running
python3.9 -m pip3 install --upgrade pip
as it says https://www.intel.com/content/www/us/en/support/articles/000091171/software/development-software.html worked

In pop_os/ubuntu/etc, it's important to use python3.9, for python3.10 there is no package of openvino it seems.
I had an issue creating a venv, solved it by installing python3.9-venv like it says here: https://www.liquidweb.com/kb/how-to-install-and-update-python-to-3-9-in-ubuntu/ and then the installation of the requirements ran fine.

sudo apt install python3.9
python-3.9 -m pip install -r requirements.txt

It work for me

I tried all the solution but still getting the error
pip install openvino==2022.1.0
ERROR: Could not find a version that satisfies the requirement openvino==2022.1.0 (from versions: 2021.3.0, 2021.4.0, 2021.4.1, 2021.4.2, 2023.0.0.dev20230217, 2023.0.0.dev20230407)
ERROR: No matching distribution found for openvino==2022.1.0

Can you provide more details about your environment, like which OperatingSystem in which version, please?
How have you tried "all the solution"?
Do you try to install "natively" in the OS, or within a Python virtual-env, or within a container?
Do you want to use pip or pip3?
Do you have multiple versions of Python installed side-by-side? How to you use python then, via a symbolic link, or calling python3.9?

By "all the solution", I meant the solutions listed above in this thread. I installed openvino runtime  and ran the "source setupvar.sh" again. After which "pip install openvino==2022.1.0" worked. Thank you!

I had the same error, it happened because I had a 32-bit version of python installed. I removed it and installed a 64-bit one


Changed styling of edit links; changed section title

Description
This PR just changes some styles in the Summary component (aka Review page).  The Edit links are now moved over 20 pixels from the section titles and the Backup Contact section is now named Backup Contact Info.
Reviewer Notes
To maintain consistency, note that I also changed the Edit links that show up on the same page for a PPM.  We will need to make sure the upcoming HHG shipment section does the same.
Setup
make server_run
make client_run
Create either a PPM or HHG move to the point of the Review page and examine the styles mentioned above.
Code Review Verification Steps

[ ] End to end tests pass (make e2e_test).
[ ] There are no aXe warnings for UI.
[ ] This works in IE.
[ ] Request review from a member of a different team.
[ ] Have the Pivotal acceptance criteria been met for this change?

References

Pivotal story for this change

Screenshots
Before:

After:

LGTM!


After upgrading to 1.0.2 images return 403 forbidden

I mentioned this earlier on twitter and thought it was just an issue with my cache in chrome, because if I did a hard refresh, all the images came through.  But then all throughout the day (even after clearing my chrome cache) they would still come back as forbidden on normal refreshes.  On twitter, you mentioned that 1.1 might resolve this: https://twitter.com/#!/getcassette/status/172348135602003969
I went in and with NuGet updated to 1.1.0-beta4 and it appears that everything is good--the images show up consistently.  However, in the 1.0.2 security announcement: http://groups.google.com/group/cassette/browse_thread/thread/61333cf79bd16815?pli=1, you mention that 1.1 still suffers from the vulnerability that 1.0.2 fixes, so I thought i'd still add this issue.  (My thinking is--perhaps naively--that if you ultimately do the same thing to 1.1 that fixed 1.0.2, then we might run into the same problem in 1.1.)  Here (http://www.diigo.com/item/image/2283i/nkq7) is a screenshot of what it looks like in chrome console. It's strange, because if I right click on the forbidden resource and tell chrome to open it in a new tab and refresh a bunch, it might come up one of those times.  I think it has something to do with the 304 redirect caused by the cache-control headers and the way chrome handles those.  Your tweets led me to believe that this wouldn't be a problem in debug="false" and that seems true in my limited testing, but its really a pain trying to code in debug="true" when half the page doesn't load.
So, as it stands right now, i'm on 1.1.0-beta4, and that's probably ok for the short term, because I don't plan on putting this into production for the next little bit.
Hopefully this helps...
-- Jorin

My plan is to get 1.1.0 finally released on Sunday. This will have the security fix applied.
Another improvement coming: The asset cache busters in debug mode will be based on the output of the asset, rather than the original file. This takes into account transformations applied to the assets (expanding CSS URLs, compiling coffeescript, etc).

Cassette 1.1.0 is now available via nuget and should resolve this issue.

Awesome. I'll check it out tonight.


Doubt on how legal is this for scraping jobs on linkedin

Hi,
Can any member of this repo comment on how legal is using of this repo to scrap jobs from linkedin legal ?
Does it violate any laws cuz its publicly available data.
Scraping violates linkedin tos. But still can this be done ?
I wanted to know the details before i start my project on it using this library.

Is LinkedIn scraping legal?
Scraping LinkedIn data without permission violates LinkedIn's terms of service and can lead to legal consequences.
What are the benefits of LinkedIn scraping?
Benefits include market research, lead generation, job market analysis, and competitive intelligence.
What are the risks of LinkedIn scraping?
Risks include legal action, ethical concerns, and technical challenges related to data accuracy and anti-scraping measures.
Source:
https://www.linkedin.com/pulse/what-scraping-linkedin-radhika-rajput-h3alc/

But we are not logging in the website and so not agreeing to TOS.
So just want to know if this github repo is ok to be used in my project

Yes, we're not logging in and only scraping public data. This is legal to use.


In game controls menu

User Story: As a noob player, I want to be able to look at the controls in game so I dont have to use the readme every time I forget.
Definition of Done: A command or button on pause screen can be executed to display the commands listed on the project's readme

Until pause screen is implemented, plan is to add a user side command that acts like the /help command in server.py


After fix in Pyright, Pylance still complains when using modules as implementations of protocol

This is related to issue https://github.com/microsoft/pyright/issues/6117, which was addressed and closed in Pyright version 1.1.332.
However, when using Pylance in VSCode, this issue persists.
I'm using Pylance version 2023.10.40.
I have checked that in Pylance version 2023.10.31, the Pyright copy has been updated to version 1.1.332, which is the version that solves problem.
I have installed the CLI version of Pyright and the type checking passes for the following snippet.
Environment data

Language Server version: 2023.10.40
OS and version: macOS Sonoma
Python version (& distribution if applicable, e.g. Anaconda): Python 3.12.0 (main, Oct  2 2023, 12:03:24) [Clang 15.0.0 (clang-15<IP_ADDRESS>)] on darwin

Code Snippet
# pyright: strict

from typing import Protocol

import example

class Person(Protocol):
    @property
    def AGE(self) -> int: ...

person: Person = example

Inside example.py:
AGE = 10

Expected behavior
I expect Pylance does not complain this.
Actual behavior
Expression of type "Module("example")" cannot be assigned to declared type "Person"
  "AGE" is an incompatible type
    "Literal[10]" is incompatible with "property"
Pylance[reportGeneralTypeIssues](https://github.com/microsoft/pyright/blob/main/docs/configuration.md#reportGeneralTypeIssues)

Logs
2023-10-25 10:33:20.618 [info] [Info  - 10:33:20] (53254) Pylance language server 2023.10.40 (pyright 088ebaa5) starting
2023-10-25 10:33:20.619 [info] [Info  - 10:33:20] (53254) Server root directory: /Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist
2023-10-25 10:33:20.619 [info] [Info  - 10:33:20] (53254) Starting service instance "mre-pylance-bug"
2023-10-25 10:33:20.635 [info] (53254) No configuration file found.
2023-10-25 10:33:20.635 [info] (53254) No pyproject.toml file found.
2023-10-25 10:33:20.635 [info] [Info  - 10:33:20] (53254) Setting pythonPath for service "mre-pylance-bug": "/opt/homebrew/bin/python3.12"
2023-10-25 10:33:20.635 [info] [Info  - 10:33:20] (53254) Setting environmentName for service "mre-pylance-bug": "3.12.0 (global)"
2023-10-25 10:33:20.656 [info] [Info  - 10:33:20] (53254) Assuming Python version 3.12
2023-10-25 10:33:20.656 [info] (53254) Assuming Python platform Darwin
2023-10-25 10:33:20.684 [info] [Info  - 10:33:20] (53254) Search paths for /Users/gz/Documents/tmp/mre-pylance-bug
2023-10-25 10:33:20.684 [info] [Info  - 10:33:20] (53254)   /Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/typeshed-fallback/stdlib
2023-10-25 10:33:20.684 [info] [Info  - 10:33:20] (53254)   /Users/gz/Documents/tmp/mre-pylance-bug
2023-10-25 10:33:20.684 [info] [Info  - 10:33:20] (53254)   /Users/gz/Documents/tmp/mre-pylance-bug/typings
2023-10-25 10:33:20.685 [info] [Info  - 10:33:20] (53254)   /Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/typeshed-fallback/stubs/...
2023-10-25 10:33:20.685 [info] [Info  - 10:33:20] (53254)   /Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/bundled/stubs
2023-10-25 10:33:20.685 [info] [Info  - 10:33:20] (53254<EMAIL_ADDRESS>2023-10-25 10:33:20.685 [info] [Info  - 10:33:20] (53254<EMAIL_ADDRESS>2023-10-25 10:33:20.685 [info] [Info  - 10:33:20] (53254)   /opt/homebrew/lib/python3.12/site-packages
2023-10-25 10:33:20.685 [info] [Info  - 10:33:20] (53254) Adding fs watcher for library directories:
<EMAIL_ADDRESS><EMAIL_ADDRESS>/opt/homebrew/lib/python3.12/site-packages
2023-10-25 10:33:20.685 [info] [Info  - 10:33:20] (53254) Adding fs watcher for directories:
 /Users/gz/Documents/tmp/mre-pylance-bug
2023-10-25 10:33:20.685 [info] (53254) Searching for source files
2023-10-25 10:33:20.687 [info] [Info  - 10:33:20] (53254) Found 2 source files
2023-10-25 10:33:20.687 [info] (53254) pytest configurations: {"message":"script","classes":["Test"],"files":["test_*.py","*_test.py"],"functions":["test"]}
2023-10-25 10:33:20.687 [info] (53254) pytest configurations: {"message":"script","classes":["Test"],"files":["test_*.py","*_test.py"],"functions":["test"]}
2023-10-25 10:33:20.901 [info] (53254) pytest configurations: {"message":"request cancelled","classes":["Test"],"files":["test_*.py","*_test.py"],"functions":["test"]}
2023-10-25 10:33:20.919 [info] (53254) [BG(1)] getSemanticTokens full at /Users/gz/Documents/tmp/mre-pylance-bug/module_protocol.py ...
2023-10-25 10:33:20.919 [info] (53254) [BG(1)]   parsing: /Users/gz/Documents/tmp/mre-pylance-bug/module_protocol.py (16ms)
2023-10-25 10:33:20.938 [info] (53254) [FG] parsing: /Users/gz/Documents/tmp/mre-pylance-bug/module_protocol.py (11ms)
2023-10-25 10:33:20.988 [info] (53254) [FG] parsing: /Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/typeshed-fallback/stdlib/builtins.pyi [fs read 6ms] (50ms)
2023-10-25 10:33:21.012 [info] (53254) [FG] binding: /Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/typeshed-fallback/stdlib/builtins.pyi (24ms)
2023-10-25 10:33:21.013 [info] (53254) [FG] binding: /Users/gz/Documents/tmp/mre-pylance-bug/module_protocol.py (0ms)
2023-10-25 10:33:21.015 [info] (53254) [BG(1)]   parsing: /Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/typeshed-fallback/stdlib/builtins.pyi [fs read 1ms] (39ms)
2023-10-25 10:33:21.016 [info] (53254) [BG(1)]   binding: /Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/typeshed-fallback/stdlib/builtins.pyi (24ms)
2023-10-25 10:33:21.016 [info] (53254) [BG(1)]   binding: /Users/gz/Documents/tmp/mre-pylance-bug/module_protocol.py (0ms)
2023-10-25 10:33:21.016 [info] (53254) [BG(1)]   parsing: /Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/typeshed-fallback/stdlib/typing.pyi [fs read 0ms] (8ms)
2023-10-25 10:33:21.016 [info] (53254) [BG(1)]   binding: /Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/typeshed-fallback/stdlib/typing.pyi (4ms)
2023-10-25 10:33:21.017 [info] (53254) [BG(1)]   parsing: /Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/typeshed-fallback/stdlib/typing_extensions.pyi [fs read 0ms] (3ms)
2023-10-25 10:33:21.017 [info] (53254) [BG(1)]   binding: /Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/typeshed-fallback/stdlib/typing_extensions.pyi (1ms)
2023-10-25 10:33:21.017 [info] (53254) [IDX(2)] scan packages /Users/gz/Documents/tmp/mre-pylance-bug ...
2023-10-25 10:33:21.017 [info] (53254) [IDX(2)]   read stdlib indices (18ms)
2023-10-25 10:33:21.022 [info] (53254) [BG(1)]   parsing: /Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi [fs read 0ms] (6ms)
2023-10-25 10:33:21.023 [info] (53254) [BG(1)]   binding: /Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi (1ms)
2023-10-25 10:33:21.027 [info] (53254) [BG(1)]   parsing: /Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/typeshed-fallback/stdlib/types.pyi [fs read 0ms] (4ms)
2023-10-25 10:33:21.030 [info] (53254) [BG(1)]   binding: /Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/typeshed-fallback/stdlib/types.pyi (2ms)
2023-10-25 10:33:21.033 [info] (53254) [BG(1)]   parsing: /Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/typeshed-fallback/stdlib/abc.pyi [fs read 0ms] (0ms)
2023-10-25 10:33:21.033 [info] (53254) [BG(1)]   binding: /Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/typeshed-fallback/stdlib/abc.pyi (1ms)
2023-10-25 10:33:21.035 [info] (53254) [BG(1)]   parsing: /Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/typeshed-fallback/stdlib/collections/abc.pyi [fs read 0ms] (0ms)
2023-10-25 10:33:21.035 [info] (53254) [BG(1)]   binding: /Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/typeshed-fallback/stdlib/collections/abc.pyi ...
2023-10-25 10:33:21.035 [info] (53254) [BG(1)]     parsing: /Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/typeshed-fallback/stdlib/_collections_abc.pyi [fs read 0ms] (1ms)
2023-10-25 10:33:21.035 [info] (53254) [BG(1)]     binding: /Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/typeshed-fallback/stdlib/_collections_abc.pyi (0ms)
2023-10-25 10:33:21.036 [info] (53254) [BG(1)]   binding: /Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/typeshed-fallback/stdlib/collections/abc.pyi (2ms)
2023-10-25 10:33:21.038 [info] (53254) [BG(1)]   parsing: /Users/gz/Documents/tmp/mre-pylance-bug/example.py [fs read 0ms] (1ms)
2023-10-25 10:33:21.038 [info] (53254) [BG(1)]   binding: /Users/gz/Documents/tmp/mre-pylance-bug/example.py (0ms)
2023-10-25 10:33:21.049 [info] (53254) [BG(1)] getSemanticTokens full at /Users/gz/Documents/tmp/mre-pylance-bug/module_protocol.py (146ms)
2023-10-25 10:33:21.050 [info] (53254) [BG(1)] getSemanticTokens range 0:0 - 15:0 at /Users/gz/Documents/tmp/mre-pylance-bug/module_protocol.py (0ms)
2023-10-25 10:33:21.094 [info] (53254) [BG(1)] analyzing: /Users/gz/Documents/tmp/mre-pylance-bug/module_protocol.py ...
2023-10-25 10:33:21.095 [info] (53254) [BG(1)]   checking: /Users/gz/Documents/tmp/mre-pylance-bug/module_protocol.py ...
2023-10-25 10:33:21.095 [info] (53254) [BG(1)]     parsing<EMAIL_ADDRESS>[fs read 0ms] (40ms)
2023-10-25 10:33:21.095 [info] [Info  - 10:33:21] (53254) Could not import '_typing' in file<EMAIL_ADDRESS>2023-10-25 10:33:21.095 [info] [Info  - 10:33:21] (53254)   Looking in stubPath '/Users/gz/Documents/tmp/mre-pylance-bug/typings'
2023-10-25 10:33:21.095 [info] [Info  - 10:33:21] (53254)   Attempting to resolve stub package using root path '/Users/gz/Documents/tmp/mre-pylance-bug/typings'
2023-10-25 10:33:21.096 [info] [Info  - 10:33:21] (53254)   Attempting to resolve using root path '/Users/gz/Documents/tmp/mre-pylance-bug/typings'
2023-10-25 10:33:21.096 [info] [Info  - 10:33:21] (53254)   Looking in root directory of execution environment '/Users/gz/Documents/tmp/mre-pylance-bug'
2023-10-25 10:33:21.096 [info] [Info  - 10:33:21] (53254)   Attempting to resolve stub package using root path '/Users/gz/Documents/tmp/mre-pylance-bug'
2023-10-25 10:33:21.096 [info] [Info  - 10:33:21] (53254)   Attempting to resolve using root path '/Users/gz/Documents/tmp/mre-pylance-bug'
2023-10-25 10:33:21.096 [info] [Info  - 10:33:21] (53254)   Finding python search paths
2023-10-25 10:33:21.096 [info] [Info  - 10:33:21] (53254)   Executing interpreter: '/opt/homebrew/bin/python3.12'
2023-10-25 10:33:21.096 [info] [Info  - 10:33:21] (53254)   Skipping<EMAIL_ADDRESS>because it is not a valid directory
2023-10-25 10:33:21.097 [info] [Info  - 10:33:21] (53254)   Received 3 paths from interpreter
2023-10-25 10:33:21.097 [info] [Info  - 10:33:21] (53254<EMAIL_ADDRESS>2023-10-25 10:33:21.097 [info] [Info  - 10:33:21] (53254<EMAIL_ADDRESS>2023-10-25 10:33:21.098 [info] [Info  - 10:33:21] (53254)     /opt/homebrew/lib/python3.12/site-packages
2023-10-25 10:33:21.098 [info] [Info  - 10:33:21] (53254)   Looking in python search path<EMAIL_ADDRESS>2023-10-25 10:33:21.098 [info] [Info  - 10:33:21] (53254)   Attempting to resolve stub package using root path<EMAIL_ADDRESS>2023-10-25 10:33:21.098 [info] [Info  - 10:33:21] (53254)   Attempting to resolve using root path<EMAIL_ADDRESS>2023-10-25 10:33:21.098 [info] [Info  - 10:33:21] (53254)   Looking in python search path<EMAIL_ADDRESS>2023-10-25 10:33:21.099 [info] [Info  - 10:33:21] (53254)   Attempting to resolve stub package using root path<EMAIL_ADDRESS>2023-10-25 10:33:21.099 [info] [Info  - 10:33:21] (53254)   Attempting to resolve using root path<EMAIL_ADDRESS>2023-10-25 10:33:21.100 [info] [Info  - 10:33:21] (53254)   Looking in python search path '/opt/homebrew/lib/python3.12/site-packages'
2023-10-25 10:33:21.100 [info] [Info  - 10:33:21] (53254)   Attempting to resolve stub package using root path '/opt/homebrew/lib/python3.12/site-packages'
2023-10-25 10:33:21.100 [info] [Info  - 10:33:21] (53254)   Attempting to resolve using root path '/opt/homebrew/lib/python3.12/site-packages'
2023-10-25 10:33:21.100 [info] [Info  - 10:33:21] (53254)   Looking in bundled stubs path '/Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/bundled/stubs'
2023-10-25 10:33:21.101 [info] [Info  - 10:33:21] (53254)   Attempting to resolve stub package using root path '/Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/bundled/stubs'
2023-10-25 10:33:21.101 [info] [Info  - 10:33:21] (53254)   Attempting to resolve using root path '/Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/bundled/stubs'
2023-10-25 10:33:21.103 [info] [Info  - 10:33:21] (53254)   Looking for typeshed stdlib path
2023-10-25 10:33:21.104 [info] [Info  - 10:33:21] (53254)   Looking for typeshed stdlib path
2023-10-25 10:33:21.104 [info] [Info  - 10:33:21] (53254)   Attempting to resolve using root path '/Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/typeshed-fallback/stdlib'
2023-10-25 10:33:21.104 [info] [Info  - 10:33:21] (53254)   Typeshed path not found
2023-10-25 10:33:21.105 [info] [Info  - 10:33:21] (53254)   Looking for typeshed third-party path
2023-10-25 10:33:21.105 [info] [Info  - 10:33:21] (53254)   Looking for typeshed stubs path
2023-10-25 10:33:21.105 [info] [Info  - 10:33:21] (53254)   Typeshed path not found
2023-10-25 10:33:21.116 [info] (53254) [BG(1)]     binding<EMAIL_ADDRESS>(22ms)
2023-10-25 10:33:21.119 [info] (53254) [BG(1)]     parsing<EMAIL_ADDRESS>[fs read 0ms] (2ms)
2023-10-25 10:33:21.120 [info] [Info  - 10:33:21] (53254) Could not import '_abc' in file<EMAIL_ADDRESS>2023-10-25 10:33:21.122 [info] [Info  - 10:33:21] (53254)   Looking in stubPath '/Users/gz/Documents/tmp/mre-pylance-bug/typings'
2023-10-25 10:33:21.123 [info] [Info  - 10:33:21] (53254)   Attempting to resolve stub package using root path '/Users/gz/Documents/tmp/mre-pylance-bug/typings'
2023-10-25 10:33:21.124 [info] [Info  - 10:33:21] (53254)   Attempting to resolve using root path '/Users/gz/Documents/tmp/mre-pylance-bug/typings'
2023-10-25 10:33:21.124 [info] [Info  - 10:33:21] (53254)   Looking in root directory of execution environment '/Users/gz/Documents/tmp/mre-pylance-bug'
2023-10-25 10:33:21.126 [info] [Info  - 10:33:21] (53254)   Attempting to resolve stub package using root path '/Users/gz/Documents/tmp/mre-pylance-bug'
2023-10-25 10:33:21.127 [info] [Info  - 10:33:21] (53254)   Attempting to resolve using root path '/Users/gz/Documents/tmp/mre-pylance-bug'
2023-10-25 10:33:21.127 [info] [Info  - 10:33:21] (53254)   Finding python search paths
2023-10-25 10:33:21.128 [info] [Info  - 10:33:21] (53254)   Executing interpreter: '/opt/homebrew/bin/python3.12'
2023-10-25 10:33:21.129 [info] [Info  - 10:33:21] (53254)   Skipping<EMAIL_ADDRESS>because it is not a valid directory
2023-10-25 10:33:21.129 [info] [Info  - 10:33:21] (53254)   Received 3 paths from interpreter
2023-10-25 10:33:21.129 [info] [Info  - 10:33:21] (53254<EMAIL_ADDRESS>2023-10-25 10:33:21.129 [info] [Info  - 10:33:21] (53254<EMAIL_ADDRESS>2023-10-25 10:33:21.130 [info] [Info  - 10:33:21] (53254)     /opt/homebrew/lib/python3.12/site-packages
2023-10-25 10:33:21.130 [info] [Info  - 10:33:21] (53254)   Looking in python search path<EMAIL_ADDRESS>2023-10-25 10:33:21.130 [info] [Info  - 10:33:21] (53254)   Attempting to resolve stub package using root path<EMAIL_ADDRESS>2023-10-25 10:33:21.131 [info] [Info  - 10:33:21] (53254)   Attempting to resolve using root path<EMAIL_ADDRESS>2023-10-25 10:33:21.131 [info] [Info  - 10:33:21] (53254)   Looking in python search path<EMAIL_ADDRESS>2023-10-25 10:33:21.131 [info] [Info  - 10:33:21] (53254)   Attempting to resolve stub package using root path<EMAIL_ADDRESS>2023-10-25 10:33:21.132 [info] [Info  - 10:33:21] (53254)   Attempting to resolve using root path<EMAIL_ADDRESS>2023-10-25 10:33:21.132 [info] [Info  - 10:33:21] (53254)   Looking in python search path '/opt/homebrew/lib/python3.12/site-packages'
2023-10-25 10:33:21.132 [info] [Info  - 10:33:21] (53254)   Attempting to resolve stub package using root path '/opt/homebrew/lib/python3.12/site-packages'
2023-10-25 10:33:21.132 [info] [Info  - 10:33:21] (53254)   Attempting to resolve using root path '/opt/homebrew/lib/python3.12/site-packages'
2023-10-25 10:33:21.132 [info] [Info  - 10:33:21] (53254)   Looking in bundled stubs path '/Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/bundled/stubs'
2023-10-25 10:33:21.132 [info] [Info  - 10:33:21] (53254)   Attempting to resolve stub package using root path '/Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/bundled/stubs'
2023-10-25 10:33:21.133 [info] [Info  - 10:33:21] (53254)   Attempting to resolve using root path '/Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/bundled/stubs'
2023-10-25 10:33:21.133 [info] [Info  - 10:33:21] (53254)   Looking for typeshed stdlib path
2023-10-25 10:33:21.133 [info] [Info  - 10:33:21] (53254)   Looking for typeshed stdlib path
2023-10-25 10:33:21.134 [info] [Info  - 10:33:21] (53254)   Attempting to resolve using root path '/Users/gz/.vscode/extensions/ms-python.vscode-pylance-2023.10.40/dist/typeshed-fallback/stdlib'
2023-10-25 10:33:21.134 [info] [Info  - 10:33:21] (53254)   Typeshed path not found
2023-10-25 10:33:21.134 [info] [Info  - 10:33:21] (53254)   Looking for typeshed third-party path
2023-10-25 10:33:21.134 [info] [Info  - 10:33:21] (53254)   Looking for typeshed stubs path
2023-10-25 10:33:21.134 [info] [Info  - 10:33:21] (53254)   Typeshed path not found
2023-10-25 10:33:21.134 [info] (53254) [BG(1)]     binding<EMAIL_ADDRESS>(0ms)
2023-10-25 10:33:21.134 [info] (53254) [BG(1)]   checking: /Users/gz/Documents/tmp/mre-pylance-bug/module_protocol.py (77ms)
2023-10-25 10:33:21.134 [info] (53254) [BG(1)] analyzing: /Users/gz/Documents/tmp/mre-pylance-bug/module_protocol.py (77ms)
2023-10-25 10:33:21.135 [info] (53254) pytest configurations: {"message":"script","classes":["Test"],"files":["test_*.py","*_test.py"],"functions":["test"]}
2023-10-25 10:33:21.135 [info] (53254) [BG(1)] indexing: /Users/gz/Documents/tmp/mre-pylance-bug/example.py [found 1] (1ms)
2023-10-25 10:33:21.135 [info] (53254) [BG(1)] indexing: /Users/gz/Documents/tmp/mre-pylance-bug/module_protocol.py [found 2] (0ms)
2023-10-25 10:33:21.148 [info] (53254) [IDX(2)] scan packages /Users/gz/Documents/tmp/mre-pylance-bug (186ms)
2023-10-25 10:33:21.172 [info] (53254) [IDX(2)] index packages /Users/gz/Documents/tmp/mre-pylance-bug ...
2023-10-25 10:33:21.173 [info] (53254) [IDX(2)]   index execution environment /Users/gz/Documents/tmp/mre-pylance-bug ...
2023-10-25 10:33:21.173 [info] (53254) [IDX(2)]     indexing<EMAIL_ADDRESS>[skipped: no '__all__' defined] (0ms)
2023-10-25 10:33:21.173 [info] (53254) [IDX(2)]     indexing<EMAIL_ADDRESS>[skipped: no '__all__' defined] (0ms)
2023-10-25 10:33:21.173 [info] (53254) [IDX(2)]     indexing<EMAIL_ADDRESS>[skipped: no '__all__' defined] (0ms)
2023-10-25 10:33:21.173 [info] (53254) [IDX(2)]     indexing<EMAIL_ADDRESS>[skipped: no '__all__' defined] (0ms)
2023-10-25 10:33:21.173 [info] (53254) [IDX(2)]     indexing<EMAIL_ADDRESS>[skipped: no '__all__' defined] (0ms)
2023-10-25 10:33:21.173 [info] (53254) [IDX(2)]     indexing<EMAIL_ADDRESS>[skipped: no '__all__' defined] (1ms)
2023-10-25 10:33:21.173 [info] (53254) [IDX(2)]     indexing<EMAIL_ADDRESS>[skipped: no '__all__' defined] (0ms)
2023-10-25 10:33:21.173 [info] (53254) [IDX(2)]     indexing<EMAIL_ADDRESS>[skipped: no '__all__' defined] (0ms)
2023-10-25 10:33:21.173 [info] (53254) [IDX(2)]     indexing<EMAIL_ADDRESS>[skipped: no '__all__' defined] (0ms)
2023-10-25 10:33:21.174 [info] (53254) [IDX(2)]     indexing<EMAIL_ADDRESS>[skipped: no '__all__' defined] (0ms)
2023-10-25 10:33:21.174 [info] (53254) [IDX(2)]     indexing: /opt/homebrew/lib/python3.12/site-packages/wheel/__init__.py [skipped: no '__all__' defined] (0ms)
2023-10-25 10:33:21.174 [info] (53254) [IDX(2)]   index execution environment /Users/gz/Documents/tmp/mre-pylance-bug [found 11 in 4 files] (2ms)
2023-10-25 10:33:21.174 [info] (53254) [IDX(2)] index packages /Users/gz/Documents/tmp/mre-pylance-bug [found 11 in 1 exec envs] (5ms)

Pylance 2023.10.40 was a hot fix, so it was based on last week's production release of pylance which didn't include Pyright 1.1.332.
Version 2023.10.41 was a hot fix of the prerelease version, which did include Pyright 1.1.332, so that should include this fix. Assuming there are no other hot fixes, this will become this week's production version of pylance (2023.10.50).

Pylance 2023.10.40 was a hot fix, so it was based on last week's production release of pylance which didn't include Pyright 1.1.332.
Version 2023.10.41 was a hot fix of the prerelease version, which did include Pyright 1.1.332, so that should include this fix. Assuming there are no other hot fixes, this will become this week's production version of pylance (2023.10.50).

Thank you for your clarification and time! Sorry for not having read the Pylance CHANGELOG more carefully.


Broken URL in README.md

This URL in the readme is broken: https://sid343.reinvent-workshop.com/

up

Hmm. Still not loading for me. Tried it from two different networks and no go.

Fixed, can you test again to confirm?

The connection has timed out
The server at sid343.reinvent-workshop.com is taking too long to respond.
I seems just offline for me.

Interesting... just discovered that http://sid343.reinvent-workshop.com/ works, but https://sid343.reinvent-workshop.com/ does not.
It appears the readme link has been changed from https to http so that resolves the issue.


filter high level groups and action groups by cluster and index

Description
Filters high level groups based on cluster or index panel and also filters the actiongroups based on their associated type
Category
[Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation]
Why these changes are required?
What is the old behavior before changes and new behavior after changes?
Issues Resolved
fix: #1346
fix: #1347
Testing
[Please provide details of testing done: unit testing, integration testing and manual testing]
Check List

[ ] New functionality includes testing
[ ] New functionality has been documented
[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Thank you for the PR @derek-ho ! Would you be able to add a test to verify the new behavior?

@derek-ho Does this fix #1347 too or just #1346? I took a quick glance at the code and it looks like this fixes #1346 , but not #1347

@derek-ho Would you please fetch the latest changes from main.

@derek-ho Does this fix #1347 too or just #1346? I took a quick glance at the code and it looks like this fixes #1346 , but not #1347

This should fix both. It is both filtering action groups (which comes from the network call), and also creates a separate variable, so that only cluster/index respectively permissions from the constants file is included


Code cleanups and small fixes

@mark-at-pieces I think that's all for that PR merge it

@BishoyHanyRaafat can you update the description on this pr on all the things that were cleaned up and link any issue to this pr that are fixed


Add Typing to baseio, baserawio, and exampleio

Replaces #1229 because that now has merge conflicts.
I know this has been discussed #1123. Sam is against, others are typically for. This is just a draft to think about (& correct or reject), but I think adding type hints to some places exposed to the user would be beneficial. By putting the hints into the base it propagates to all ios to minimize other typing needing to be added, although developers can override the typing in their specific io.
I know that neo has complicated inputs, but I think type hints work best to give a suggested appropriate input (And as a nod to Sam I didn't add type hints for the returns yet).

Hello @zm711! Thanks for opening this PR.

I would add my support to such a PR. Typing is fantastic for catching bugs, in general improving robustness. Since I started using type hints last year they have caught a lot of potential bugs and saved me a lot of trouble!

Having the role of the old dinosaur is not so easy in a group but I am trying my best to maintain my public character.

Having the role of the old dinosaur is not so easy in a group but I am trying my best to maintain my public character.

@samuelgarcia never change. Your example error messages here and in probeinterface are always the highlight of my proofreading.

@zm711 this looks good to me!
@samuelgarcia can we merge?

Thanks @alejoe91. I have a feeling when there is typing in the PR title @samuelgarcia has a filter for his alerts to jeter dans la poubelle.

@zm711 it is even worst. typing PR are triggering in me a brain state nearby freezing.
I always need to turn off the computer for at least one hour to recover totally.

I am in favour of this PR, but some changes are needed for the type hints to be compatible with Python 3.8 and 3.9.

I think I addressed all of this in comments. But just to overall explain for future reference
I have added:
from __future__ import annotations

to the three files with typing, which allows us to use type hints from 3.9 and 3.10 in 3.8, 3.9, and 3.10 to keep things clean. This means we can:

use | instead of needing Literal, but if Literal is preferred I can switch to that.
use built-in types even in 3.8 list instead of List, dict instead of Dict

so if | was going to break the code we should've seen that during the testing.

yes, that confused me, but since you've explained about from __future__ import annotations it all makes sense!
There's one remaining point I'm not sure about (numpy.dtype), but otherwise this looks good.

Officially the better typing would be:
import numpy.typing as npt

my_function(x, dtype: npt.DTypeLike = 'int32')

This indicates that something can be coerced into a numpy dtype. I currently have the dtype listed as the dtype constructor which is the constructor that takes an input and attempts to convert it to a numpy.dtype. So @apdavison you are correct that the current type is not strictly correct. Would you like me to change or do you think people will understand despite the mention of the constructor rather than the typing. I think the issue we will run into is that some old versions of numpy won't have the numpy typing module so it would be harder to support.

I think the issue we will run into is that some old versions of numpy won't have the numpy typing module so it would be harder to support

That's a good point. For now we're not doing strict type checking with mypy or whatever, so I agree let's leave it as is for now.

Also just for reference I checked and typing was added in 1.21 so we would need to wait until our minimum numpy is that to be safe.


Disable CG Check for Partner Release Pipelines

Add flag for skipping Component Governance steps

/check-enforcer override

/check-enforcer override


FIX Imported namespaces now correctly used to determine class inhertance

Fixes #3707
see #3899

@assertchris  :) namespacing, whoo

Much more lovely code @dhensby :D Sorry for giving you pain over your other PR.

Should this fix be back-ported to 3.1?

@sminee was of the opinion that only the most low risk bug fixes should go into 3.1, which makes sense. The upgrade to 3.2 should be quite frictionless.
Though, if when you release the next patch to 3.1, you want it in there.. Then why not?


mrb_symbol_value() gives empty string

Not sure if this is a bug or me mistaking the API if I return a symbol like this:
return mrb_symbol_value(mrb_intern_lit(mrb, "dummy"));

I always get an empty symbol on the Ruby side ?

Sounds like a bug, but I need more info, especially reproducing code.

    auto* ruby = mrb_open();
    auto sym = mrb_intern_cstr(ruby, "testing");
    mrb_define_global_const(ruby, "TEST", mrb_symbol_value(sym));
    mrb_load_string(ruby, "p TEST.class ; p TEST ; TEST = :testing ; p TEST");

prints
Symbol
:""
:testing

However, replacing the third line with
mrb_define_global_const(ruby, "TEST", mrb_check_intern_cstr(sym, "testing"));

works. But I can only use that workaround when I know the string representation of the symbol.

Actually, this seems to be fixed in the latest version... sorry :)


Gradle 8.5

Draft until final version is released.

Gradle 8.5 is out now. Any plans on taking this PR forward?

Yes

Warnings

:warning:
It looks like this PR contains functional changes without a corresponding test.

  Generated by :no_entry_sign: dangerJS against 49ebb7e594396fd1bee536f157ba342ed132aaf1


Fix vscode-elixir compaitibllity

Make sure that the plugin is compatible with vscode-elixir since the name of the file format is case sensitive.
Fix for #1

Ping :)

This project is apparently unmaintained.

Closing because of no reaction.

Closing because of no reaction.

I included your cahnges manually. Thanks!

I included your cahnges manually. Thanks!


_addComplexObserverEffect adds useless property effects for litteral arguments

When you declare an observer like this one: observe(12,"foo",bar.*) then _addComplexObserverEffect() will create a property effect for 12 and "foo".
Looks like a if(arg.litteral) is missing in this function.
_addComplexObserverEffect: function(observer) {
  var sig = this._parseMethod(observer);
    sig.args.forEach(function(arg) {
      if(arg.litteral)
        return;
      this._addPropertyEffect(arg.model, 'complexObserver', {
        method: sig.method,
        args: sig.args,
        trigger: arg
      });
    }, this);
},

Referencing #3153 as it solved a similar issue, but with parent properties.

This should since be fixed as computed functions now keep track if they were static or not.


feat(configuration): Change configuration API response to dictionary

Description
Update configuration api to use dictionaries.
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #283
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[x] Created/updated tests
[ ] Extended the documentation

This proto is a part of unreleased Dapr, right? We should wait for the next release before changing this here. Thoughts?
/cc @XavierGeerinck

This proto is a part of unreleased Dapr, right? We should wait for the next release before changing this here. Thoughts?
/cc @XavierGeerinck

Yes. Makes sense. We have to wait until the dapr changes goes in like we always do.

This proto is a part of unreleased Dapr, right? We should wait for the next release before changing this here. Thoughts?
/cc @XavierGeerinck

Yes. Makes sense. We have to wait until the dapr change goes in like we always do.

The Java SDK does not have this requirement as we allow to point to a git commit for dapr and build it as part of the SDK workflow for testing. Can this be achieved in this SDK too?

This proto is a part of unreleased Dapr, right? We should wait for the next release before changing this here. Thoughts?
/cc @XavierGeerinck

Yes. Makes sense. We have to wait until the dapr change goes in like we always do.

The Java SDK does not have this requirement as we allow to point to a git commit for dapr and build it as part of the SDK workflow for testing. Can this be achieved in this SDK too?

Yes, we can do that @artursouza, but I only have one concern. JavaScript SDK has a separate release cadence than runtime/Java-SDK, this will cause unreleased Dapr proto definitions to be a part of JavaScript SDK releases. For Java it must be ok since they only cut their release after Dapr release gets cut. WDYT?

@XavierGeerinck for thoughts

I think version management is always going to be difficult as we need to couple releases to certain Dapr versions, thus subsequent updates will not receive certain bug fixes or features.
We could adapt the testing workflow to point to a certain Dapr commit version, but I don't see the real benefit for it, what would this be? As we would be testing against the newest and be ready, but in the end the PRs are there and validated by the developers at the end stage to be released when the latest Dapr version is.

Hello @addjuarez, can you please fix conflicts?

@addjuarez the build is failing due to prettify, you can run npm run pretty-fix to solve these issues.

LGTM!

Looks good to me!


CMake installation rules for the project should be fixed

It seems that  there is a bug in CMakeLists.txt.
Installation rules for header files doesn't work since the header source path is set wrong.
You should use "include/" instead of "src/" source path  to install header files.
Please replace /src directory with include/ in the CMakeLists.txt as follows:
install(DIRECTORY include/ DESTINATION ${PROJECT_BINARY_DIR}/include
FILES_MATCHING PATTERN "*.hh"

hi,
i've pushed a fix to master. Thank you for the bug report!


Add toss3 TPL and host-config for clang with libc++

A user recently experienced an issue with a clang-based configuration that used libc++ instead of glibc as its standard library.
We should add a host-config + TPL build on LLNL's toss3 platform for this configuration.
Links:

Similar host-config in blt --<EMAIL_ADDRESS>Related issues and PRs: #179, #180

will re-open if user issue comes up again


Sensors values not adding up (Potentially sensor.goodwe_house_consumption)

Good day,
As per all the comments so far, a big thank you for all the work and effort to get this integration off the ground and working so well.
Since the last two or three version upgrades, I have noticed that the sensor values on my power distribution card are way out.  Although they never added up 100% previously, they were very close, and could be used to reliably automate my geyser, pool pump etc.
To explain this better, previously when adding sensor.goodwe_ppv, sensor.goodwe_pgrid and sensor.goodwe_pbattery1 together you would have had a value close to senor.goodwe_house_consumption (Current Consumption).
After the last couple of versions this has changed to huge gaps for long periods of time.  As an example below, I am consuming 653 Wats more than possible.

Another Example

Your assistance and advice will be greatly appreciated.
Regards

Out of interest sake, what card is that?

It is the Power Distribution Card, you can install it through HACS.
https://github.com/JonahKr/power-distribution-card

Release v0.9.0 did have wrong formula from house_consumption calculation, but it was fixed in v0.9.1.
Is the problem still present there ?

I think so, I am currently running 0.9.1

Hmm, prior to 0.9.0 the formula for house_consumption was ppv1 + ppv2 + pbattery - pgrid.
Since 0.9.1 I have changed it to pload + pback_up - pgrid since it was reported the previous formula was somehow ignoring consumption of backup line.
If you say it's still not correct, than one of these sensor do not provide correct values.
I'm not sure what to do, whether to revert to 0.8.x behavior, since here #66 it seemed 0.9.1 does provide +/- proper values.

If you are referring to the Backup Port VS On Grid port of the inverter I can definitely state with out a doubt that 0.8.x was not ignoring the backup line. Most of my house is on the backup line with only the big appliances such as stove and geyser on the On Grid line.
However, let me read #66 and see if I am missing something, maybe revert to 0.8.x to confirm what I see.
Thank you for your patience and assistance so far, will revert back with what I find as soon as possible,

I am on 0.8.9 still I think and can confirm this card works correctly.

I agree that 0.8.x looks the most reliable.
But there's at least one sensor which is reporting wrong data (or is improperly identified).
Since you obviously can't feed 885 to pback with only 760 and no import.

I have done a couple of more tests.
Test 1 - Only my router switched on
In this test 0.8.x wins hands down

Test 2 - Add +- 4KW to On Grid Leg only
In this test 0.8.x still seems the best but 0.9.1 is very close to 0.8.x

Test 3 - Add +-1.6KW to Backup Leg only
All of them are very close however there is +- 200w more than I expected on all of them, could just be that my appliance pulls a bit more than specified.

Although it is almost impossible to compare the near real time data with the SEMS Portal is also seems more aligned with the 0.8.x calc.

It does not seem that  0.9.1 is using the calculations as I have done it above for sensor.goodwe_house_consumption (Represented by H-Con) as it almost doubles my consumption. The 6KW number is correct value, am I missing something?

I agree that 0.8.x looks the most reliable.
But there's at least one sensor which is reporting wrong data (or is improperly identified).
Since you obviously can't feed 885 to pback with only 760 coming from battery and no import.

So this is something else I noticed.
Using version 0.8.9 and earlier, the values always matched up, with the exception that sometimes it looked as if pback is actually updated out of sync and I think this is the inverter doing it. If I just accepted that pback is accurate and in sync most of the time then the values always aligned up.
I created a template sensor to see how much non-essential load I have and it uses home consumption - pback and sometimes the non-essentials side just shows a load that makes no sense at all. Eg. all non-essential items turned off on the db board, there should be 0w load on non-essentials, but with pback reading sometimes lower or higher than it should, when its lower then it looks like there is load on non-essentials when it is impossible.
Personally, my vote is also to go back to 0.8.9 version calculation for now until you think you can figure this out. Otherwise I think I will just be forced to stay on version 0.8.9 myself. Knowing, that pback doesn't read accurately.

Here is 2 consecutive readings showing how it jumps around.

I have reverted the code to the 0.8.x behavior, it should get to next release (over the weekend I hope).
From all the observations it really seems the pback is not reliable sensor and should be treated as such.

I have reverted the code to the 0.8.x behavior, it should get to next release (over the weekend I hope).
From all the observations it really seems the pback is not reliable sensor and should be treated as such.

Thank you very much for you effort and your patience. Much appreciated.

Also agree, many thanks for your time and trying to assist everyone with this addon!

You're welcome ;-)
The main problem is that those 3 families of inverters behave quite differently and I have only 1 inverter at home.
So anything I develop for the other two, I unfortunately have no way how to verify/test it directly.
And then it happens that attempt to improve something may actually make it worse ...

Happy to spin up a dev HA and test things for you on the ES if you want. Let me know.

Closing the issue, since v0.9.2 returned back to 0.8.x version of house consumption formulas which seem to be the best ones.


Javatar has some additional levels now:

Per Will Henstrom:
New levels:
10A - Alternative lvl 10 map
11A - Alternative lvl 11 map
12A - Alternative lvl 12 map
14B - Through the portals on lvl 14
Extra side lvls:
ST1 - Snake Temple lvl 1 (off of lvl 1)
ST2 - Snake Temple lvl 2
ST3 - Snake Temple lvl 3
ST4 - Snake Temple lvl 4
ST5 - Snake Temple lvl 5
ST6 - Snake Temple lvl 6
WF - Wofat’s Lair (off of lvl 3)
OP1 - Outpost lvl 1 (off of lvl 4)
OP2 - Outpost lvl 2
BGS - Beyond the Glowing Sword (off of lvl 6)
BL - Bansidhe’s Lair (off of lvl 7)
DT - Dark Tunnel (off of lvl 8)
DK - Deep FKeyhole (off of lvl15)

Adding levels is pretty easy, my notes/script from having added 16b is:
LEVEL=16b
echo "insert into levels SET num='$LEVEL', version=1;"| mysql -u root javatar
for x in $(seq 30); do for y in $(seq 30); do echo "insert into map SET level='$LEVEL', x=$x, y=$y;"; done; done | mysql -u root javatar

However, some of the pages on the site are static (about.html, edit.html and legend.html) and they require editing to make them match the dynamic pages.
Also with this many levels, the list of levels at the top is gonna be way to long and so some other kind of level selection UX is required.

There appears to be another level accessible from the 15 Keyhole.  Not yet confirmed it is it's own plate, but it might make sense to add DK1 and DK2, just in case.


Writing for Note Air 3c

Cannot write on the Boox Note Air 3c.  Has been the same with other 3rd party apps (ie notable, tools for boox), although a solution was just found for tools for boox.  Would be awesome to get this working

I imagine this commit 3bd80e44bdb5bde758bf3f0cd315614c67c9937e will have fixed it as I guess it's the same issue as the tab c pro. I haven't yet recompiled the apk but will do that shortly

the new apk is here apk
I don't have a device to test on but can you let me know if it works and I'll add it as a release

can you try now - I had a look at the tools for boox fix and that had an additional step which I've now included

it works! thanks very much for the update


Update: KDE.KDEConnect version 21.12.3

Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 437
Microsoft Reviewers: Open in CodeFlow

/azp run


Add missing package to install psycopg2 module

This fixes the build of docker image.

:+1:

:+1:


Gh 3019 Add an anet service graphql interface - GH 2081 Change email address message

This PR adds the following features to the ANET

Now admin users can reload ANET dictionary without any need of restarting server.

The dictionary that was previously in anet.yml is now included in the new anet-dictionary.yml file
This file is placed in the same folder with anet.yml . When anet-dictionary file is modified manually by an Admin the new values of dictionary can be reloaded through admin UI page.

Admin users can empty domain users cache through admin UI page

Admin users can track user activities on UI page in 2 different format

Sorts all activities in time descending order without any grouping
Displays most recent activity of each user

A new logging file is added to track these user activities

New logging mechanism works like below :

A new log type is defined in anet.yml file as userActivities
Every POST request that has a user principal is logged through ViewResponseFilter and written in this new log file
This file has a maxFileSize limit of 1MB by default but it can be set any value,it is up to Admin
When this maxFileSize is reached system rollovers current userActivities.log file
(and it creates a new archive file for only once if it does not exist)
On admin page when Admin clicks the related button : userActivities.log file is read and displayed on page

A new file "version.properties" is placed under resources.

This file is edited during build of project through build.gradle file ,it replaces the
"APP_VERSION_TOKEN" value with the recent build number of project.On startup of service this info is injected into index.hbs file
Also a rest service is added to read the file and return the version info
Application version is displayed on ANET banner page

While creating a new person : If person is a NATO member then email field displays a placeholder. (#2081 )

This placeholder is read from anet-dictionary.yml file.
In this way,Admins can customize placeholder value according to their own needs

Release notes
Closes #2081
Closes #3019
User changes
Now all users can see project version on ANET page
Super User changes
The same with user changes
Admin changes
Admins are now able to change and reload anet dictionary without restarting server
They can empty domain users cache through admin page
They can track user activities through admin page
System admin changes
They should place a ViewResponseFilter logger in anet.yml
They should remove dictionary from anet.yml
They should place a valid anet-dictionary.yml file in anet package(Should be in the same location with anet.yml)

[x] anet.yml needs change
[ ] db needs migration
[ ] documentation has changed ( TODO : INSTALL.md,anet.yml.production.template files should be updated )
[x] graphql schema has changed

Checklist

[x] Described the user behavior in PR body
[x] Referenced/updated all related issues
[x] commits follow a repo#issue: Title title format and these 7 rules
[x] commits have a clean history, otherwise PR may be squash-merged
[x] Added and/or updated unit tests
[ ] Added and/or updated e2e tests
[ ] Added and/or updated data migrations
[ ] Updated documentation ( TODO : INSTALL.md,anet.yml.production.template files should be updated )
[x] Resolved all build errors and warnings
[ ] Opened debt issues for anything not resolved here

Unfortunately this branch doesn't seem to have a clean history. Apparently, amendable changes have been commited separately. I would re-write this branch's history as follows;
# create a temporary local branch where we will create new commits. Make sure it is up-to-date with candidate.
git checkout candidate
git fetch && git pull && git status
git checkout -b GH-3019-tmp

# bring in all changes from our main branch
git merge --squash GH-3019-Add-an-ANET-service-graphql-interface
# all changes will be staged for commit
git status
# remove changes from stage so that we can create dedicated commits
git reset
git status

# create necessary amount of commits as if we are implementing from scratch.
# you should create as many as necessary as per https://epage.github.io/dev/commits/

# commit code changes. this is an example that creates one commit.
git add ./
git status
git commit

# we have all changes committed in our temp branch with a clean history
git status
git log --pretty=fuller

# now we will bring changes in from our temp branch to our main branch
git checkout GH-3019-Add-an-ANET-service-graphql-interface

# make sure it is up-to-date with remote
git fetch && git pull && git status

# trim the dirty history
git reset --hard HEAD~50

# bring all recent changes from remote candidate
git pull origin candidate

# finally bring is changes from our temp branch
git merge GH-3019-tmp

# at this point git status should produce following message
# "Your branch and 'origin/GH-3019-Add-an-ANET-service-graphql-interface' have diverged,
# and have 5 and 40 different commits each, respectively."
git status

# 5 is correct since, as of this writing 'origin/GH-3019-Add-an-ANET-service-graphql-interface'
# is 4 commits behind candidate and we created 1 new commit. 4+1 = 6 :)

# you can display recent commits/history with following command
git log --pretty=fuller

# push changes to remote
git push --force

# after making sure that everything is fine, code is working, tests are passing, builds are successful
git branch -D GH-3019-tmp

Unfortunately this branch doesn't seem to have a clean history. Apparently, amendable changes have been commited separately. I would re-write this branch's history as follows;
# create a temporary local branch where we will create new commits. Make sure it is up-to-date with candidate.
git checkout candidate
git fetch && git pull && git status
git checkout -b GH-3019-tmp

# bring in all changes from our main branch
git merge --squash GH-3019-Add-an-ANET-service-graphql-interface
# all changes will be staged for commit
git status
# remove changes from stage so that we can create dedicated commits
git reset
git status

# create necessary amount of commits as if we are implementing from scratch.
# you should create as many as necessary as per https://epage.github.io/dev/commits/

# commit code changes. this is an example that creates one commit.
git add ./
git status
git commit

# we have all changes committed in our temp branch with a clean history
git status
git log --pretty=fuller

# now we will bring changes in from our temp branch to our main branch
git checkout GH-3019-Add-an-ANET-service-graphql-interface

# make sure it is up-to-date with remote
git fetch && git pull && git status

# trim the dirty history
git reset --hard HEAD~50

# bring all recent changes from remote candidate
git pull origin candidate

# finally bring is changes from our temp branch
git merge GH-3019-tmp

# at this point git status should produce following message
# "Your branch and 'origin/GH-3019-Add-an-ANET-service-graphql-interface' have diverged,
# and have 5 and 40 different commits each, respectively."
git status

# 5 is correct since, as of this writing 'origin/GH-3019-Add-an-ANET-service-graphql-interface'
# is 4 commits behind candidate and we created 1 new commit. 4+1 = 6 :)

# you can display recent commits/history with following command
git log --pretty=fuller

# push changes to remote
git push --force

# after making sure that everything is fine, code is working, tests are passing, builds are successful
git branch -D GH-3019-tmp

don't worry about it too much


Logic to enable YARN RM HA is incorrect

The code in yarn-site expects more than 2 nodes to run YARN RM which need to be changed to check for 2 RMs in the cluster.

This is being fixed as part of HA enablement of various components in chef-bach move to HDP 2.2.

Fixed in 5e236e96f26dabef8ac1118cd8fee3eb515d1112


Building rclrs nodes causes python nodes to break

I am getting an
"AttributeError: 'ParameterDescriptor' object has no attribute 'dynamic_typing'"
when trying to start python nodes after building a rclrs node and sourcing the installation.
If I don't build and source the rust node, the python node runs fine. But after I build the rust node and source the installation, I can't sart python nodes, even "ros2 topic list" and similar commands give this error.
For the "ros2 topic" command it seems to help to call it once before sourcing the rust node, then it continues to run normally. The same does not work for my python nodes.
I am running Ros-Humble in a podman container, with ros2_rust installed per instuctions.

with ros2_rust installed per instructions

I think this may be your issue actually. The instructions in the readme have you clone the foxy repos
vcs import src < src/ros2_rust/ros2_rust_foxy.repos
. /opt/ros/foxy/setup.sh

You're likely hitting this line. This attribute is not present in foxy, seems to have been added in galactic.
I was able to reproduce with the following

Follow the instructions as they are in the README and clone the foxy repos in the ros2_rust workspace.
Source'd my system humble installation
Source'd the ros2_rust workspace
Ran the py_pubsub listener example

sam@orange:~/rust_ws_humble$ ros2 run py_pubsub listener
Traceback (most recent call last):

...

AttributeError: 'ParameterDescriptor' object has no attribute 'dynamic_typing'
[ros2run]: Process exited with failure 1

So to resolve this, make sure you clone the humble repos
vcs import src < src/ros2_rust/ros2_rust_humble.repos

Clean your workspace build and install folders, rebuild, source, and you should be good.

In my setup, which is based on one of my Docker environments, I couldn't replicate your problem either. Would you like to tell us about your environment?

What is your hardware architecture?
Which Podman container do you use? Would you link it?
What were the nodes for that caused the crash?

Thanks for looking at this.
Ill be honest, I have not worked on  the project I had this project in, for quite a while
and I don't have the container anymore. I would be absolutly fine closing this, It seems to be a Problem only I had, so it might have been my fault.
Sorry for forgetting about is issue.
If you want to look into this deeper I would be happy trying to repoduce my old setup.


⚠.gitignore issue⚠

Be cautious of tracking files like node_modules in your repository, as it can lead to unnecessary issues. 😒
In the CampusShare project, where the frontend and backend folders are structured under the parent directory, it is ideal to have a single .gitignore file located at the root of the CampusShare directory. Avoid creating additional .gitignore files within the subdirectories. Use proper path settings in the root .gitignore to ensure files specific to each folder (e.g., node_modules, build files, environment files, etc.) are ignored appropriately.

In the CampusShare project, How about clearly specifying the location of the root .gitignore file in the CampusShare project and adding comments  to discourage adding additional .gitignore files in the subdirectories.

# .gitignore is located at the root of the CampusShare directory.
# Do not add additional .gitignore files in subdirectories.

Thank you both for the insights! I agree that managing .gitignore effectively is crucial to avoiding unnecessary issues, especially with large projects like CampusShare. Adding a clear comment about the root .gitignore location, as Youjune suggested, seems like a practical step. I’ll review the current setup and implement these changes.


Viem support?

Is there any plan to support Viem? It's made by the wagmi team as an alternative to ethers.

+1

I created a view version here https://github.com/feelsgoodman-web3/siwveim

Hello, we are discussing how to address this, since the library went through an audit it gets a little more complicated to replace such a vital library. Hope you understand!

in the end, we should 👍

+1 vote to have viem support 🙏🏼

also found https://github.com/softwarecurator/eip-login by @softwarecurator
but it's probably worth rewriting to viem 2.

So i write small lib, also welcome to testing simplified siwe with Viem 2
https://github.com/reslear/simple-siwe

any update on this?

We are not planning to add support for viem but would welcome a contribution. As this library already supports both ethers.js v5 and v6 I believe the "crypto backend" is abstracted enough to make such addition relatively easily, unless I'm missing something.

Say no more!

@nfts2me Yes and no, there's also a deps problem (like parsers), See my Comparison above packages on viem ~2mb.
however siwe 2.8 + ethers 18.8MB = ~20mb
hence the motivation to make https://github.com/reslear/simple-siwe a scaled-down copy without dependencies

Good news https://github.com/wevm/viem/pull/2280

we can close the subject @sbihel


devices/stm32l4r9.yaml: patch TIM3 and TIM4

TIM3 and TIM4 work the same way in stm32l4r9 and stm32l4x6.
Since stm32l4x6.yaml contains these _copy and _derive lines, they should also be added to this yaml file.
Note that I've simply verified this empirically, with these lines added I can now use TIM3 and TIM4 to generate a PWM signal,
and that I don't fully comprehend the SVD files yet.

Memory map comparison

That's pretty neat.

Spurious network error
bors retry


chore(package.json): Use npm's @types packages to manage d.ts files

We can remove the dependency for typings package.
And it will simplify a dependency management.

Duplicated #1837

I'll reopen as a separated tracking issue.

I believe this issue is already resolved in latest master.

@kwonoj Oops, I missed it. Thank you!


hide closed cases

I think it would be useful to have a "hide closed cases" checkbox.   keeps important stuff up front.

[ ] add a "hide closed cases" checkbox.

Agree. As long as we are adding filters, we ought to consider whether there are any others that are essential.


SVG implementation details unimplemented

This module implements, and quite literally, the grammar for path strings as described in the SVG 1.1 docs in 8.3.9 The grammar for path data. Unfortunately, being a strictly literal implementation of the grammar, it assumes the absolute correctness of the input, simply giving up and erroring on any input strings that are imperfect according to the grammar.  This fails at least two of the requirements from the SVG docs.

In the first section of F.5 ‘path’ element implementation notes the spec talks about error handling for path strings.  In particular it uses the example of 'M 10,10 L 20,20,30' which should successfully process the first two commands, which here should return the result (as shown by using a shortened string):
> parse('M 10,10 L 20,20')
[ { code: 'M', command: 'moveto', x: 10, y: 10 },
  { code: 'L', command: 'lineto', x: 20, y: 20 } ]

Instead this strict parser simply errors out with

SyntaxError: Expected ",", ".", [ \t\n\r], [+-], [0-9], or [eE] but end of input found.

In the section 8.3.8 The elliptical arc curve commands describing the arc command it mentions

Refer to Elliptical arc implementation notes for detailed implementation notes for the path data elliptical arc commands.

In those implementation notes subsection F.6.2 Out-of-range parameters among other notes says:

If rx or ry have negative signs, these are dropped; the absolute value is used instead.
That is, the following should return something like:

> parse('M 12.5,550 a-50,-50,0,1,0,-100,0')
[ { code: 'M', command: 'moveto', x: 12.5, y: 550 },
  { code: 'a',
    command: 'elliptical arc',
    relative: true,
    rx: 50,
    ry: 50,
    xAxisRotation: 0,
    largeArc: true,
    sweep: false,
    x: -100,
    y: 0 } ]

but instead an immediate fatal error is seen

SyntaxError: Expected ".", [ \t\n\r], or [0-9] but "-" found.

Note that the released grammar.peg accurately reflects the SVG grammar, with lines 142-143
142  elliptical_arc_argument
143    = rx:nonnegative_number comma_wsp? ry:nonnegative_number comma_wsp?

agreeing with the spec's grammar
elliptical-arc-argument:
    nonnegative-number comma-wsp? nonnegative-number comma-wsp?

Changing nonnegative_number to number works around the error, but still doesn't quite match the implementation note.
The problem with the elliptical arc parsing is simply that the implementation notes were not considered, which probably can be remedied with some inline code?
But how you would re-architect the whole module to permit return of both an error and the partial results from before the error was detected?  This would certainly seem to be far beyond a simple tweak.
At the very least the description of the module needs to say that strict parsing is done with any grammar deviations treated as fatal and no results will be returned.  And in addition that some SVG implementation details are not handled within this module.

Would something like this (tested and works)
143c159
<   = rx:nonnegative_number comma_wsp? ry:nonnegative_number comma_wsp?
---
>   = rx:number comma_wsp? ry:number comma_wsp?
145c161
<   { return { rx:rx, ry:ry, xAxisRotation:xrot, largeArc:large, sweep:sweep, x:xy.x, y:xy.y } }
---
>   { return { rx:Math.abs(rx), ry:Math.abs(ry), xAxisRotation:xrot, largeArc:large, sweep:sweep, x:xy.x, y:xy.y } }

be usable for a pull request?


Update iif.md

Update the description of IIF function and add one more example for explanation.

#sign-off

Since I can't sign off, I will pull this into another PR and merge it manually.
Thanks @yaoce95, for your contribution.
#hold-off
#please-close


v1.11.0

Fixed issue with target location not saved
Fixed issues with ntrode not getting deleted
Added age and dob


fix mountainclient docs

@wysota
mt.login() and mt.configRemote*() have been deprecated.
Instead use mt.configDownloadFrom()
In addition to getting/setting to pairio (formerly cairio) mountainclient now interacts with kachery servers for remote content upload/download
Also we will need to document how to set kachery upload/download tokens. For example, create a ~/.mountaintools/kachery_tokens file with the following content
spikeforest.kbucket download *******secret-token***********
spikeforest.kbucket upload ******secret-token************
http://some-ip-or-host download ******secret-token************

It would be nice to have a tool which does that.


Build: Nightly Release needs to find another place for the artifacts

Our token for CN Cloud has expired, and we no longer have access to it. Maybe we should use Github release for the following release artifacts?

Oops, it seems been fixed.


Add files via upload

Please add my college to the list.

@edushoppy I have to close this request without merging, because you requested to add a non-existent domain to this repository: Host wcstudents.wc not found: 3(NXDOMAIN) Please ensure that you are familiar with this repository rules located at the bottom of this page and submit a new request with the correct information. Thank you for your understanding!


Hi Rich,
I am having trouble reproducing your issue and I have never really tested the project with VS 2015. Can you try VS 2019? I have made some changes that might help. Let me know how it goes.
Finally, thank you for the submitting the first issue in the project. Hopefully, I will come up with a better way to contact me than Telegram.

I was able to do it with the community/free 2019 version... I will try again in 2015 if you think the changes you made may make a difference. The ReadMe talked about pre-compiled binaries and I never could locate those so I tried to compile with what I already had installed. Compiled it just fine. Ran it with FULL and VERBOSE as local-admin, and seemed to work! As non-admin some registry reads failed and it barf'd. I think I see some results that I don't 100% agree with but I'm going to cross my I's and dot my T's first before I create any other tickets ;) Pretty cool tool so far though!

Hi Rich,
You can access the pre-compiled binaries under releases here. Let me know for any specific findings that seem inaccurate. I will happily take a look and fix them.
Happy to hear that it works on Win7. Never really tested it on that :)


better emulate imports via dynamic imports

These are the variants of "normal" imports
import defaultExport from "module-name";
import * as name from "module-name";
import { export1 } from "module-name";
import { export1 as alias1 } from "module-name";
import { default as alias } from "module-name";
import { export1, export2 } from "module-name";
import { export1, export2 as alias2, /* … */ } from "module-name";
import { "string name" as alias } from "module-name";
import defaultExport, { export1, /* … */ } from "module-name";
import defaultExport, * as name from "module-name";
import "module-name";

Since none of them work in eval provided user code, these things don't work in xeus-javascript.
But we can emulate some of them. For instance import "module-name"; can be rewritten as importScripts("module-name");
Since we anyhow use an AST parser, rewriting these statements is trivial, we just need to find a mapping from each of these imports to importScripts / await import
Here is a table of what might work.
I am not sure if everything I did here is correct.

user code
rewritten code

import defaultExport from "module-name";
const { default: defaultExport } = await import("module-name");

import * as name from "module-name";
const name = await import("module-name");

import { export1 } from "module-name";
const {export1} = await import("module-name");

import { export1 as alias1 } from "module-name";
const {export1} = await import("module-name"); const alias1=export1;

import { default as alias } from "module-name";
const { default: alias } = await import("module-name");

import { export1, export2 } from "module-name";
const {export1, export2} = await import("module-name");

import { export1, export2 as alias2, /* … */ } from "module-name";
const {export1, export2} = await import("module-name"); const alias2=export1;

import { "string name" as alias } from "module-name";
?

import defaultExport, { export1, /* … */ } from "module-name";
const { default: defaultFunc,export1 } = await import("module-name");

import defaultExport, * as name from "module-name";
const { default: defaultExport } = await import("module-name");const name = await import("module-name");

import "module-name";
importScripts("module-name)"

implemented via #10


fix typo

This was intentional :)
The non-DSL part is now called "Anko Commons".
anko-common artifact is still available in 0.10.0, but it is deprecated and will be eventually removed.

I see


Add support for points in Web Worker layers

Description
The current implementation of Web Worker layers within ViziCities only supports polygon geometry. Point geometry is required for 100% coverage of GeoJSON.
Solution
This PR adds point support for Web Worker layers as well as generally tidying up point logic across the board.

👍 Good to go


Handle code fence info string and HTML type 7 on new algorithm

@elynnyap and I got code fence info strings and html type 7 working in the new algorithm. Now passing 370/621 spec tests.
We're a little unsure about the memory management of code info strings. Currently they are being cloned in item_to_tag.

Made requested changes.
Escaping code info strings gave us two more passing tests.

Awesome, thanks! Always nice to catch something in code inspection.


Fix valyukhov tq

Changes proposed in this pull request:

Has the changelog been added to what is being done in this pull request
@foxprogs @Vorobushec @Valyukhov

не добавлены изменения в changelog

не добавлены изменения в changelog


Support adding and removing ys from RecentLines

The task here is to make RecentLines.ys an observable list instead of an immutable tuple. When its contents are changed, lines must be correspondingly added or removed. Also, the axes y label and title should be updated.
For now I propose to not make x settable. To change x, just make another plot. Three reasons:

If you change x everything has to re-plotted anyway, so it isn't much more expensive to just create a new RecentLines instance from scratch.
In a GUI, we don't need to expose this asymmetry to the user. We can make changing x look like just changing y; they don't need to know that we'll be making a new RecentLines instance internally when they change x.
It seems to be useful for higher layers (e.g. AutoRecentLines) to treat x as fixed, so I'd like to leave it that way unless we hit a good reason to make it settable.

Note about updating the axes y label and title:
We should modify RecentLines to take control of the AxesSpec title but not touch with FigureSpec. Giving axes to RecentLines is giving it control of title / labels, but it should not mess with the figure that those axes are embedded in. This might require #70 because we currently require figures to have a title.


chore: add check_code_format.yml

This PR adds a workflow, which checks the used code formatting (and makes the necessary changes in the currently existing files).
As suggested by @Ramy-Badr-Ahmed in #13, the new workflow uses fprettify. I could not force it to fail, if there are some changes necessary, so I used a fail if needs reformatting approach as in TheAlgorithms/Nim#19.
Beside the indentation size being set to 4, I used the default setting of the fprettify. Please let me know if you prefer other settings.
The failing part works logs for 8663d150dc0a7c6c9fbc49e74405cd7bdd508c43.

This PR adds a workflow, which checks the used code formatting (and makes the necessary changes in the currently existing files).
As suggested by @Ramy-Badr-Ahmed in #13, the new workflow uses fprettify. I could not force it to fail, if there are some changes necessary, so I used a fail if needs reformatting approach as in TheAlgorithms/Nim#19.
Beside the indentation size being set to 4, I used the default setting of the fprettify. Please let me know if you prefer other settings.
The failing part works logs for 8663d15.

Adding the debug output -d to fprettify --indent 4 -d --recursive . can help identifiy the styling mismatches.

Beside the indentation size being set to 4, I used the default setting of the fprettify. Please let me know if you prefer other settings.
The failing part works logs for 8663d15.

Adding the debug output -d to fprettify --indent 4 -d --recursive . can help identifiy the styling mismatches by contributors.
Here's an example output: logs

Strange... the output does not appear in the actions logs:

https://github.com/TheAlgorithms/Fortran/actions/runs/11040556555/job/30668810319
https://github.com/TheAlgorithms/Fortran/actions/runs/11040442388/job/30668440497
https://github.com/TheAlgorithms/Fortran/actions/runs/11040275300/job/30667876416

Strange... the output does not appear in the actions logs:
* https://github.com/TheAlgorithms/Fortran/actions/runs/11040556555/job/30668810319
* https://github.com/TheAlgorithms/Fortran/actions/runs/11040442388/job/30668440497
* https://github.com/TheAlgorithms/Fortran/actions/runs/11040275300/job/30667876416

I see. I tried it out and it would work with git diff in the failure step:
      - name: Format Fortran files
        run: |
          fprettify -i 4 --recursive .
      - name: Fail if needs reformatting
        run: |
          if [[ $(git status --porcelain) ]]; then
            echo "please reformat/fprettify these files:"
            git diff
            exit 1
          else
            echo "All files are properly formatted."
          fi

My logs: https://github.com/Ramy-Badr-Ahmed/Fortran-DSA/actions/runs/11043111068/job/30676793615
Let's have another try 🙂

So as mentioned above: the output was empty, because obviously the files were already reformatted. I used git diff.
Now it works as expected, cf. the failing case: https://github.com/TheAlgorithms/Fortran/actions/runs/11045781263/job/30683988597


No uSync Vendr options available in Dashboard

Hi Matt,
We are currently running an Umbraco 8.17 instance with uSync Complete version 8.10.2, and Vendr version 2.0.2.
After the installation of the latest version of Vendr uSync (2.0.0), no options that involve Vendr show on the uSync Synchronisation Dashboard. (i.e. no Vendr options available under the Report, Import or Export button).
What is suprising is that 'Vendr.Usync (v2.0.0)' does show up in the label at the top of the uSync dashboard itself, next to all the other uSync addons that are installed. Another thing that I noted is that during the install, it only added the Vendr.uSync package to the package.config, but no other App_Plugins/uSync files were touched or added to the solution during the install.
Hope you can help me figure out what's going wrong!
Kind regards,
Corné Hoskam

Hi,
I am guessing the part of the nuget package that adds the handlers to the usync8.config file failed 😢
after install the following should be added to the default handler set (you can add them by hand if you need to)
  <Handler Alias="vendrStoreHandler" Enabled="true" />
  <Handler Alias="vendrCurrencyHandler" Enabled="true" />
  <Handler Alias="vendrCountryHandler" Enabled="true" />
  <Handler Alias="vendrEmailTemplateHandler" Enabled="true" />
  <Handler Alias="vendrPrintTemplateHandler" Enabled="true" />
  <Handler Alias="vendrExportTemplateHandler" Enabled="true" />
  <Handler Alias="vendrOrderStatusHandler" Enabled="true" />
  <Handler Alias="vendrPaymentMethodHandler" Enabled="true" />
  <Handler Alias="vendrRegionHandler" Enabled="true" />
  <Handler Alias="vendrShippingMethodHandler" Enabled="true" />
  <Handler Alias="vendrTaxClassHandler" Enabled="true" />

Hi Kevin!
Thank you very much! Adding those handlers did the trick for making the Sync itself work!
The only thing that is missing is the translations for the Vendr.Usync buttons under Report & Import, as they now still say [usync_report-vendr] and [usync_import-vendr]. Luckily they do function, so it's more of an aesthetics thing! 😄

If anybody is coming to this for Umbraco 9/10 and not seeing anything, you may need to enable the Vendr group in the UiEnabledGroups setting.
"UiEnabledGroups": "Settings,Vendr"

https://docs.jumoo.co.uk/usync/reference/config#group-values


CI: coverage for ut.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


How can I use libuv  raw socket in windows?

has example about libuv raw socket in windows?

You mean these? https://learn.microsoft.com/en-us/windows/win32/winsock/tcp-ip-raw-sockets-2
No, libuv does not support those out of the box.
You might be able to make them work by creating the socket yourself and using uv_poll_t, not sure that will work though.