add psbt example

resolves #892
@tcharding's psbt-example is the base branch, which was an awesome start cause there is so much new here for me to learn. This includes code to debug. Please bear in mind It's my first PR in Rust, my experience with it has only been the book & -by-example. Because this is an example it's all one commit. A few questions remain in the code.
One suggestion is to alias PartiallySignedTransaction as Psbt in rust-bitcoin
@tcharding  what do you mean by "Clean up this error" on SignError?

what do you mean by "Clean up this error" on SignError?

I stole that error type, and a bunch of the code for signing PSBTs from the bdk project. By 'clean up' I meant remove all the variants that were not being used. Also, in general, all the error handling code is incomplete i.e., usage of expect throughout. I was planning on re-doing all that once everything worked.

One suggestion is to alias PartiallySignedTransaction as Psbt in rust-bitcoin

That's a PR you can do if you would like to. Conceptually simple but likely to get some argument/discussion if you like that sort of thing :) Otherwise I'll do it.
Cheers, will review.

Nice work man! We have the seed passing issue to resolve still. Also, I'm starting to think that this should not be an example but rather should be an integration test. Then, the remaining TODOs are changes to rust-bitcoin. If you want to do them I'm happy to let you run with them :)

Locally this builds fine but CI is including recent changes to the sighash types, no idea what is going on with that. Its your branch @DanGould so I won't mess with it but my blunt guess would be update your local master branch then rebase this and change SigHash -> Sighash and force push.

I'm starting to think that this should not be an example but rather should be an integration test —@tcharding

concept ack to that and your psbt watch-only example as an example. I'll turn these TODOs into PRs.

For your CI fixes you can check out #940 or

Use BTreeMap:new() and then call insert instead of using BTreeMap::from
Add an explicit scope around the immutable/mutable borrow issue (if you hit it)

Why the heck aren't I seeing these errors when running act locally?  I don't use act, in case it helps I can get these errors locally using
RUST_LOG=warn cargo-gen-lockfile-rust-1.29-bitcoin; RUST_LOG=warn cargo +1.29 run --example psbt

And the shell function
function cargo-gen-lockfile-rust-1.29-bitcoin {
    RUST_LOG=warn cargo clean
    rm Cargo.lock

    cargo +1.29 generate-lockfile --verbose && \
        cargo +1.29 update -p cc --precise "1.0.41" --verbose && \
        cargo +1.29 update --package "serde" --precise "1.0.98" --verbose && \
        cargo +1.29 update -p "serde_derive" --precise "1.0.98" --verbose

    export RUST_LOG=$saved_log
}

The CI failure is the scope one I mention above.

@tcharding would it make sense to add this script to contributing.md? I wonder why this doesn't show up with act on its own. I get that this will change when we upgrade rust. this would have saved me 3 pushes at this point

Yeah go for it.

All green! I rekon this is pretty close to ready-for-review. I still rekon we should be asserting against PSBTs not against hex, do you have an opinion on that?

We're asserting against PSBTs now 👍
Sincere thanks for all the guidance. I'm thrilled to be able to contribute :D

We're asserting against PSBTs now

There were a few missed, I pushed a wip patch, you can squash if you like it.
I also pushed a commit that moves the example to tests/ as is customary for Rust integration tests, run it with cargo test bip174_psbt_workflow.

I'm thrilled to be able to contribute

I'm glad you are enjoying it, this is a mad project with good people working on it. I'm learning heaps hacking on this repo.

Oh and incase you want to know why its in tests/: https://doc.rust-lang.org/rust-by-example/testing/integration_testing.html

Hey @DanGould, we can bring these back to life now that MSRV has been bumped and edition 2018 has been enabled. I've got a docs PR to go in first but https://github.com/rust-bitcoin/rust-bitcoin/pull/957 is ready. You could rebase this on top of that and use the psbt.sign method if you want to.

@tcharding rebased on #957 using psbt.sign

I fixed all the dangling issues I found with this PR. How did you plan to merge this before #957? This PR includes that signing code.

I'll review for you in the morning with fresh eyes.

Sorry for the delay, I forgot about this and went on holidays. I pushed a commit that uses the signing code verbatim from #940 so you don't have to do too much more work thanks to me. Just squash it if you want to go this direction or remove it if you disagree. Will need a rebase to pick up a clippy bug fix, then IMO you can force push hit 'Ready for review' :)
Cheers man

Now this uses the same signer as #940, rebased on master, satisfies the clippy gods.
I pair programmed the latest with @0xBEEFCAF3 and added him as a co-author.

Thanks for sticking at this one @DanGould!

Hey @DanGould, now that the ecdsa-psbt module merged and the PSBT signing API improvements, this one should be able to merge. Have you time to check it over and rebase?

I re-named the PR to remove the word "example" because this adds tests not example.

Will need to be rebased once #1345 goes in.

cherry-picked https://github.com/rust-bitcoin/rust-bitcoin/pull/1347 so we have a clean history and pass CI before @tcharding wakes up

ACK b8bd31d5a85fb21ad80e1207997ac5e725f9c879
Thanks man!


structure-aware chunking of code and markdown

The chunker in CodeParser is not structure-aware. We should use something based on treesitter that produces an AST of code structure (even markdown). Especially markdown is a useful case because it can be an intermediate stage in chunking pdf docs (i.e. pdf -> markdown with headers -> structure-aware chunks)

is there a specific use case?

Structure-aware chunking in general is good to have. E.g. in a markdown doc, it's good to avoid having a logically coherent section broken up, as long as chunk size limits and overlap params are respected.

I can work on this issue if it's not assigned yet


Discrepancy between en-us and zh-cn

Hi there, we got a feedback regarding the section Grant service permission to the virtual network in this topic, pointing out that there is discrepancy between en-us and zh-cn and the zh-cn steps doesn't work, would you kindly take a look, thanks!
[Enter feedback here]

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

ID: bee481df-4234-b6a2-7b20-6b3e4bef512c
Version Independent ID: 00f88b4b-45c7-a0c7-4ec5-c51a0115e16f
Content: Deploy Azure Spring Cloud in a virtual network
Content Source: articles/spring-cloud/how-to-deploy-in-azure-virtual-network.md
Service: spring-cloud
GitHub Login: @BrendM
Microsoft Alias: brendm

Hello @Derek1101 , thanks for taking time to share your valuable feedback! We are taking a look into this and will get back to you soon.

I seem to be getting mentions in these Azure topics but I have no idea why. Maybe I was added by mistake?

May be because you are the designated doc owner of this issue?

I never looked at these docs before so I am not sure how that happened

This is to inform that we are working on this.

As it is taking longer than expected, assigning this to author to update the thread once the issue is resolved.

#reassign:karlerickson

The two versions are in sync now. #please-close


Perilous Moons Safespot Missing

Type
Other
Operating System
Windows
OS Version
Windows 11
Bug description
In completing the perilous moons quest I got to the bosses and the 'safespot' the tile that is marked to hit it from does not appear. The tile was not highlighted throughout on any of the bosses. Also tried on MacOS with the same result. Disabled Entity Hider, GPU, and Low Detail plugins and restarted and it was still unchanged.
Screenshots or videos

RuneLite version
Runelite: <IP_ADDRESS>
Launcher: 2.7.1
Logs
launcher.log
client.log

This is very likely caused by a hub plugin, if you are able to replicate the same problem when doing the boss normally post-quest (or if you reported this before finishing the quest), try safe mode.
Mac
In Terminal, run:
/Applications/RuneLite.app/Contents/MacOS/RuneLite --configure

Tick the Safe mode box. Launch RuneLite.


Multiple volumes on same disk

In 2.4 the code below would successfully split a single disk in to multiple volumes. In 2.5 it detects the disk exists, and removes any existing volumes and creates the new one, reporting ERRORS. Thus it eventually leaves you with only one volume on a partially utilized disk
Mount and inititalise disks
    xWaitforDisk Disk
    {
         DiskNumber = 2
         RetryIntervalSec = 60
         RetryCount = 2
    }
    xDisk DataDiskF
    {
        DiskNumber = 2
        DriveLetter = "F"
        FSLabel = "SQL Data"
        Size = 200GB
    }
    xDisk DataDiskL
    {
        DiskNumber = 2
        DriveLetter = "L"
        FSLabel = "SQL Logs"
        Size = 60GB
    }
    xDisk DataDiskM
    {
        DiskNumber = 2
        DriveLetter = "M"
        FSLabel = "SQL Temp"
        Size = 50GB
    }
    xDisk DataDiskK
    {
        DiskNumber = 2
        DriveLetter = "N"
        FSLabel = "SQL Backup"
        Size = 200GB
    }

Discussion:
I've been thinking about this one (while working on the HQRM conversion). It might be possible to do this in xDisk, but the more I think about this the more I feel we need a new resource called xVolume that allows multiple volumes/partitions to be defined on a Disk and be mounted to a Drive Letter and/or one or more Mount Points.
The current xDisk tries to manage Disk Status (Partition Format, Online, Readonly etc) as well as creating Partition/Volumes. This can lead to conflicts in the configuration which could lead to destructive situations occurring on this disk (especially if the Destructive flag is enabled).
xDisk could still be used for "basic" scenarios, but for any more advanced disk management we need new resources:

xDiskStatus (initializes disks, sets readonly etc) - not sure of the best name for this.
xVolume (defines a volume on a Disk based on Disk Number etc and sets DriveLetter, Label, and Mount Points). Keys would be DiskNumber and PartitionNumber.

I don't see this happening this year though and it would require a lot of discussion I expect.
This might actually be redundant though in the long run with Storage Pools being used more in future (which will require an entirely different resource set).

This appears to still be an issue today with version <IP_ADDRESS>. Is there a timeline for addressing this bug, or is it simply awaiting someone with the necessary skills and time to come along and fix it?

Hi @gabrieljtaylor - there are some scenarios where xDisk should work fine for creating multiple volumes on a disk. But there is a bug in <IP_ADDRESS> that caused this to stop working if you weren't specifing a size for one of the disks.
This is fixed (and regression/integration tests added) in the dev version which is being releasd soon. Note: this has breaking changes in it so will be <IP_ADDRESS>.
But I do still plan on releasing a new set of resources that allow more control of the disk setup:
xDiskEx
XPartition
xVolume
But I haven't had time to get them done. But happy for anyone else to pick this up.


Added new properties of JavaScript capabilities

2 new properties added to the power of JavaScript -

JavaScript can add new CSS styles existing HTML elements in the page
JavaScript can remove existing CSS styles of the HTML elements in the page

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

You've created a similar PR #30415 with almost the same changes, only the wording is different. I'm closing this PR and marking it as invalid. Please make valid contributions to the community and reduce redundancy. Hacktoberfest is to encourage good and valid Open Source.


Quick Replies are not supported by Botkit? [Facebook]

Has anyone managed to get it to work with convo.say/ask ?

@morsidi
Are you using the latest version of Botkit? Quick replies should work.
Please paste the code you are using to send the quick replies.

controller.hears(['raleigh'], 'message_received', function(bot,message){
bot.reply(message, {
"text": "What day would you like to go out?",
"quick_replies":
[
{
"content_type": "text",
"title": "Thursday",
"payload": "thursday_test"
},
{
"content_type": "text",
"title": "Friday",
"payload": "friday"
},
{
"content_type": "text",
"title": "Saturday",
"payload": "saturday"
}
]
})
})

controller.on('facebook_postback', function(bot, message) {
if (message.payload == "raleigh_test") {
bot.reply(message, {
"text": "What day would you like to go out?",
"quick_replies":
[
{
"content_type": "text",
"title": "Raleigh",
"payload": "raleigh_test"
},
{
"content_type": "text",
"title": "Chapel Hill",
"payload": "chapel_hill"
},
{
"content_type": "text",
"title": "Boone",
"payload": "boone"
}
]
    },
            function(response, convo) {
            // whoa, I got the postback payload as a response to my convo.ask!
            convo.next();
        }
    )}
})

The issue here seems to be that the current changes that came with Messenger API 1.1 have not been fully implemented in botkit just yet.
Compare #306 for instance (QuickReplies) and #305 for the starting point.
This has been merged into master, but not made it into a release version (https://github.com/howdyai/botkit/releases).
Latest tagged release was v0.2.2 which came out in June (before Messenger API 1.1 on July 1st).
So my (hopefully temporary) solution is: Manually checkout current master branch instead of relying on a pinned version.

0.4 includes these changes!


Manually Generate Data Cube and cell ordering json files

Need
A data cube with the correct dimensions to be queried by the data serving API
Approach

[ ] Set up instance to run on (see benchmarking repo and doc for instance details) in the prod env
[ ] Get list of s3_uris for h5ad files all public, primary data of the correct assay types stored in prod
[ ] Copy all h5ad files, apply rankit and concatenate via code in benchmarking repo, store in S3
[ ] Compute wmg stats, create cube, store in s3
[ ] Generate cell ordering json file broken down by tissue
[ ] copy cube and cell orderings between envs

Definition of Done

[ ] Data cube & cell ordering files stored in dev env for testing/development
[ ] Data cube  & cell ordering files stored in staging env for testing/development
[ ] Data cube  & cell ordering files stored in prod env for testing/development
[ ] Data cube  & cell ordering files stored in rdev env for testing/development
[ ] Data cube  & cell ordering files manually checked by Pablo -- TODO create story for this

Assays to include
All 10X platforms
Drop-seq
CEL-seq2
sci-RNA-seq
Visium
Seqwell
microwell-seq

I've generated a list of datasets ids and assays that are public, non tombstoned, published, primary data here
There are a few datasets that have multiple assays -- with some combos of assays we want to include and assays to exclude, how should we handle datasets with multiple assay types?

 select id, assay from dataset where published='TRUE' and is_primary_data='PRIMARY' and collection_visibility='PUBLIC' and tombstone='f';
 select id, items from dataset,jsonb_to_recordset(dataset.assay) as items(ontology_term_id text) where assay!='null';

Final query for dataset ids that are primary, published data of the appropriate assay type
select id, items
from dataset,
     jsonb_to_recordset(dataset.assay) as items(ontology_term_id text)
where assay != 'null'
  and published = 'TRUE'
  and is_primary_data = 'PRIMARY'
  and collection_visibility = 'PUBLIC'
  and tombstone = 'f'
  and items.ontology_term_id in ('EFO:0008722','EFO:0010010', 'EFO:0010550', 'EFO:0010961', '', 'EFO:0030002', 'EFO:0009901', 'EFO:0011025', 'EFO:0009899', 'EFO:0009900', 'EFO:0009922');

When run in prod this returns the ids of 67 datasets
included_assay_ontology_ids = ('EFO:0008722','EFO:0010010', 'EFO:0010550', 'EFO:0010961', 'EFO:0030002', 'EFO:0009901', 'EFO:0011025', 'EFO:0009899', 'EFO:0009900', 'EFO:0009922') # currently missing the id for seqwell

Final query to get s3_uris for appropriate datasets
select s3_uri from dataset_artifact where filetype='H5AD' and dataset_id in (
    select id
from dataset,
     jsonb_to_recordset(dataset.assay) as items(ontology_term_id text)
where assay != 'null'
  and published = 'TRUE'
  and is_primary_data = 'PRIMARY'
  and collection_visibility = 'PUBLIC'
  and tombstone = 'f'
  and items.ontology_term_id in ('EFO:0008722','EFO:0010010', 'EFO:0010550', 'EFO:0010961', 'EFO:0030002', 'EFO:0009901', 'EFO:0011025', 'EFO:0009899', 'EFO:0009900', 'EFO:0009922')
);

Currently returns a list of 57 datasets
See list of s3_uris

Originally used c6i.8xlarge instance type but ran into memory issues on the 3 largest datasets (larger than 10GB) Rerunning on c6i.16xlarge instance

RE copying datasets
I ran a script to generate presigned urls (for the datasets we needed in dev) from an account with access to prod then in used those urls to download the datasets to a instance in the dev env and wrote them to s3

To manually generate the cube

Tunnel in to prod database and run

select s3_uri from dataset_artifact where filetype='H5AD' and dataset_id in (
    select id
from dataset,
     jsonb_to_recordset(dataset.assay) as items(ontology_term_id text)
where assay != 'null'
  and published = 'TRUE'
  and is_primary_data = 'PRIMARY'
  and collection_visibility = 'PUBLIC'
  and tombstone = 'f'
  and items.ontology_term_id in ('EFO:0008722','EFO:0010010', 'EFO:0010550', 'EFO:0010961', 'EFO:0030002', 'EFO:0009901', 'EFO:0011025', 'EFO:0009899', 'EFO:0009900', 'EFO:0009922', 'EFO_0030003', 'EFO:0030004', 'EFO:0008919')
);

ssh into an EC2 instance (large enough to process/stoer all of the data) in the dev env with the Bruce-power-user role
Copy s3 uris from prod env to machine, and then copy to s3 in dev (I've been using the madison-tmp bucket, subset by date of the copying)
From the ec2 instance fetch origin/dunitz/cube-creation branch from single-cell-data-portal
Install reqs
USING TMUX... open ipython and  import load_data_and_create_cube from backend.wmg.cube_creation.load_cube
run load_data_and_create_cube('$PATH_TO_DATASETS_DIRECTORY', '$CUBE_NAME')
import get_cells_by_tissue_type from backend.wmg.cube_creation.load_cube
import generate_cell_ordering from backend.wmg.cube_creation.load_cube
run
hold = get_cells_by_tissue_type('$CUBE_NAME')
run
generate_cell_ordering(hold)

I wonder if the above instructions could be written as a guide here?

@maniarathi let me know what you think of this


Trailing slash causes redirect loop

What version of Remix are you using?
2.0.0
Are all your remix dependencies & dev-dependencies using the same version?

[X] Yes

Steps to Reproduce

Create a page, ideally a nested path such as app/routes/folder.file._index.tsx (URL path /folder/file)
Set up a reverse proxy (e.g. Shopify App Proxy) pointing to that path (e.g. https://www.example.com/folder/file)
Update remix.config.js to set publicPath = "/folder/file/build/ so assets link through the reverse proxy
Visit the proxy path (e.g. https://example.myshopify.com/folder/file) which reverse proxies to www.example.com
Observe: browser path does not have a trailing slash, but the request from the reverse proxy to the Remix app has a trailing slash (e.g https://www.example.com/folder/file/)
Observe: browser reloads infinitely with error message in browser console that says Initial URL (/folder/file/) does not match URL at time of hydration (/folder/file), reloading page...

Expected Behavior
Expect the refresh behavior to realize that a trailing slash should be ignored.
Temporary fix is to place the following in entry.client.tsx:
  const initialPathname = window.__remixContext.url
  const hydratedPathname = window.location.pathname

  /**
   * Fix initial pathname to match browser if we're dealing with trailing slashes.
   */
  if (
    initialPathname !== hydratedPathname &&
    initialPathname.replace(/\/+$/, '') === hydratedPathname.replace(/\/+$/, '')
  ) {
    window.__remixContext.url = hydratedPathname
  }

Actual Behavior
Refresh doesn't realize the two paths are effectively the same.
UPDATE: It turns out this is also an issue with links and causes the inverse issue. The Link will have a path such as /folder/file and the path in the browser becomes /folder/file/, which I believe is updated by the router. I've updated the script that fixes this (above). I've also updated the steps to reproduce to call out that we are using a custom publicPath.

This should be resolved via #9695 and available in the next release 👍

We had to revert the fix in #9695 so re-opening this.  We should be able to remove this check entirely instead in #9890


Add the ability to eject a stack

Describe the solution you'd like
I would like the ability to generate a stack and a params file, which can be upserted with the aws cli. That is, a way to eject a stack from kombustion.
Additional context
This is a feature, that both prevents lock in, and would enable wider adoption by allowing user to use kombustion to generate a template file, while still using their existing tooling.
We already know the params at generate time, so this is possible.

We're thinking of adding --parameters to kombustion generate to get it to output a params file along with the stack file.


Export fix

Revised exporting issues as stated in #19. Three issues were detected:

A simple one was an undefined attribute (this.serializer) in mechanic instances when done was called over an non-animated SVG image. It was fixed by adding conditional that checks if that attribute is undefined and creates new instance if so. This replicates other similar statements found in frame method.
Another simple issue was an not defined function calling (isSVG). That function was moved to separate file in previous refactor and wasn't properly renamed after.
Video exporting for canvas isn't working on Firefox because of support for webm-writer library, specifically a canvas element method (toDataURL). We decided that for now will only support Chrome-like browsers that support the necessary feature.
SVG animation exporting was crushing because of missing size attributes needed to convert to canvas to then add as a frame to video buffer. Fixed by calling function that extracts size from SVG element on first frame calling.

I think this fixes are fine for now, but the first mentioned issue makes me question if a refactor on the mechanic class flow could be done. Right now there is a lot of if statements and instance attributes that are used in some specific flows, so its hard to keep track what is going on. Also adding to the fact that some logic is passed to the engine, the limits between responsibilities is not completely clear to me yet.

👍


Add bleeding column backgrounds to ffe-grid(-react)

This commit adds support for adding background colors to columns. These background colors will bleed out into their surrounding gutters, to make the content stand out more.
Notice that this is implemented in LESS by simply copying a lot of the ffe-grid__row--bg- classes. I considered pulling these out into their own helper classes, but that would've been quite a breaking change for many consumers - without any real gain (well, a few bytes less CSS I guess).
Fixes #197

Coverage increased (+0.05%) to 79.033% when pulling 31f9055ebed698cf5b6f6ea9b401c6a89e4a81c1 on 197-bleeding-column-backgrounds into 4eecdb2346cda86e98651e9ef82123d766be939c on develop.

 I'll make sure to add them to the gitignore file as well

Here's a screenshot. I've added a minor improvement to the documentation so that it's easier to look at how rows and columns will look with different background colors:


Issues to relate methods of example project to rest equivalent

First of all impressive work! Setting up the backend was super easy to set everything up. I only struggle after starting up the server how to access the hello endpoint using Postman or curl.  How can I do this?
Also tip for documentation I am used to annotation frameworks like KTOR or Spring boot that are closely tied to REST terminology. At the moment I really find the Endpoint class a bit overwhelming and miss a bridge between "old fashioned" API development.

Hey @remonh87 I've just shared within Discussions how to access the ExampleEndpoint with cURL command which you should be able to import into Postman
https://github.com/serverpod/serverpod/discussions/100#discussioncomment-2447775

ah wow totally missed that discussion thanks for sharing. Will close the issue


no type hint when working with inner class

Environment data

Language Server version: pylance 2023.12.1 ~ 2024.3.2
OS and version: Win10 22H2 19045.3803
Python version (& distribution if applicable, e.g. Anaconda): python 3.11~3.12.2

Code Snippet

class foo:
    class bar:
        def __init__(self, a: int = 3):
            self.a = a

    def get_bar() -> bar:
        return foo.bar()

    def get_a_bar(a: int = 3) -> bar:
        return foo.bar(a=a)

test1 = foo.get_bar()
test2 = foo.get_a_bar(4)

Repro Steps

mouse point to test2. (you will see its Any type)
Or any action you want to get type hint from test2
Expected behavior
If we return to Pylance 2023.11.10. It work as expected

Actual behavior
pylance can't found test2's type starting from 2023.12.1

note that test1 is fine.

Also we can see foo.get_a_bar(4) return an bar object.

Logs

2024-03-28 10:30:36.225 [info] (Client) Pylance async client (2024.3.2) started with python extension (2024.2.1)
2024-03-28 10:30:36.580 [info] [Info  - 10:30:36 AM] (35164) Pylance language server 2024.3.2 (pyright version 1.1.351, commit 87171fbf) starting
2024-03-28 10:30:36.581 [info] [Info  - 10:30:36 AM] (35164) Server root directory: file:///c%3A/Users/username/.vscode/extensions/ms-python.vscode-pylance-2024.3.2/dist
2024-03-28 10:30:36.585 [info] [Info  - 10:30:36 AM] (35164) Starting service instance "linterbug"
2024-03-28 10:30:36.623 [info] (35164) No configuration file found.
2024-03-28 10:30:36.624 [info] (35164) No pyproject.toml file found.
2024-03-28 10:30:36.624 [info] [Info  - 10:30:36 AM] (35164) Setting pythonPath for service "linterbug": "C:\Program Files\Python312\python.exe"
2024-03-28 10:30:36.624 [info] [Info  - 10:30:36 AM] (35164) Setting environmentName for service "linterbug": "3.12.2 (global)"
2024-03-28 10:30:36.666 [info] [Info  - 10:30:36 AM] (35164) Assuming Python version 3.12
2024-03-28 10:30:36.666 [info] (35164) Assuming Python platform Windows
2024-03-28 10:30:36.737 [info] [Info  - 10:30:36 AM] (35164) Search paths for file:///c%3A/Users/username/some_program/some_folder/linterbug
2024-03-28 10:30:36.738 [info] [Info  - 10:30:36 AM] (35164)   c:\Users\username\.vscode\extensions\ms-python.vscode-pylance-2024.3.2\dist\typeshed-fallback\stdlib
2024-03-28 10:30:36.738 [info] [Info  - 10:30:36 AM] (35164)   c:\Users\username\some_program\some_folder\linterbug
2024-03-28 10:30:36.738 [info] [Info  - 10:30:36 AM] (35164)   c:\Users\username\some_program\some_folder\linterbug\typings
2024-03-28 10:30:36.738 [info] [Info  - 10:30:36 AM] (35164)   c:\Users\username\.vscode\extensions\ms-python.vscode-pylance-2024.3.2\dist\typeshed-fallback\stubs\...
2024-03-28 10:30:36.738 [info] [Info  - 10:30:36 AM] (35164)   c:\Users\username\.vscode\extensions\ms-python.vscode-pylance-2024.3.2\dist\bundled\stubs
2024-03-28 10:30:36.738 [info] [Info  - 10:30:36 AM] (35164)   c:\Program Files\Python312\DLLs
2024-03-28 10:30:36.738 [info] [Info  - 10:30:36 AM] (35164)   c:\Program Files\Python312\Lib
2024-03-28 10:30:36.738 [info] [Info  - 10:30:36 AM] (35164)   c:\Program Files\Python312
2024-03-28 10:30:36.739 [info] [Info  - 10:30:36 AM] (35164)   c:\Users\username\AppData\Roaming\Python\Python312\site-packages
2024-03-28 10:30:36.739 [info] [Info  - 10:30:36 AM] (35164)   c:\Users\username\AppData\Roaming\Python\Python312\site-packages\win32
2024-03-28 10:30:36.739 [info] [Info  - 10:30:36 AM] (35164)   c:\Users\username\AppData\Roaming\Python\Python312\site-packages\win32\lib
2024-03-28 10:30:36.739 [info] [Info  - 10:30:36 AM] (35164)   c:\Users\username\AppData\Roaming\Python\Python312\site-packages\pythonwin
2024-03-28 10:30:36.739 [info] [Info  - 10:30:36 AM] (35164)   c:\Program Files\Python312\Lib\site-packages
2024-03-28 10:30:36.739 [info] [Info  - 10:30:36 AM] (35164) Adding fs watcher for library directories:
 file:///c%3A/Program%20Files/Python312/DLLs
file:///c%3A/Program%20Files/Python312/Lib
file:///c%3A/Program%20Files/Python312
file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages
file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/win32
file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/win32/lib
file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/pythonwin
file:///c%3A/Program%20Files/Python312/Lib/site-packages
2024-03-28 10:30:36.739 [info] [Info  - 10:30:36 AM] (35164) Adding fs watcher for directories:
 file:///c%3A/Users/username/some_program/some_folder/linterbug
2024-03-28 10:30:36.739 [info] (35164) Searching for source files
2024-03-28 10:30:36.741 [info] [Info  - 10:30:36 AM] (35164) Found 1 source file
2024-03-28 10:30:36.742 [info] (35164) pytest configurations: {"message":"request cancelled","classes":["Test"],"files":["test_*.py","*_test.py"],"functions":["test"]}
2024-03-28 10:30:36.742 [info] (35164) pytest configurations: {"message":"script","classes":["Test"],"files":["test_*.py","*_test.py"],"functions":["test"]}
2024-03-28 10:30:36.866 [info] [Info  - 10:30:36 AM] (35164) Background analysis(1) root directory: file:///c%3A/Users/username/.vscode/extensions/ms-python.vscode-pylance-2024.3.2/dist
2024-03-28 10:30:36.867 [info] [Info  - 10:30:36 AM] (35164) Background analysis(1) started
2024-03-28 10:30:36.938 [info] (35164) [FG] parsing: file:///c%3A/Users/username/some_program/some_folder/linterbug/linterbug.py (28ms)
2024-03-28 10:30:36.975 [info] (35164) [FG] parsing: file:///c%3A/Users/username/.vscode/extensions/ms-python.vscode-pylance-2024.3.2/dist/typeshed-fallback/stdlib/builtins.pyi [fs read 2ms] (37ms)
2024-03-28 10:30:36.998 [info] (35164) [FG] binding: file:///c%3A/Users/username/.vscode/extensions/ms-python.vscode-pylance-2024.3.2/dist/typeshed-fallback/stdlib/builtins.pyi (22ms)
2024-03-28 10:30:36.999 [info] (35164) [FG] binding: file:///c%3A/Users/username/some_program/some_folder/linterbug/linterbug.py (1ms)
2024-03-28 10:30:37.000 [info] (35164) pytest configurations: {"message":"request cancelled","classes":["Test"],"files":["test_*.py","*_test.py"],"functions":["test"]}
2024-03-28 10:30:37.000 [info] (35164) [BG(1)] SemanticTokens range 0:0 - 12:24 at file:///c%3A/Users/username/some_program/some_folder/linterbug/linterbug.py ...
2024-03-28 10:30:37.000 [info] (35164) [BG(1)]   parsing: file:///c%3A/Users/username/some_program/some_folder/linterbug/linterbug.py (44ms)
2024-03-28 10:30:37.004 [info] (35164) [BG(1)]   parsing: file:///c%3A/Users/username/.vscode/extensions/ms-python.vscode-pylance-2024.3.2/dist/typeshed-fallback/stdlib/builtins.pyi [fs read 2ms] (34ms)
2024-03-28 10:30:37.020 [info] (35164) [BG(1)]   binding: file:///c%3A/Users/username/.vscode/extensions/ms-python.vscode-pylance-2024.3.2/dist/typeshed-fallback/stdlib/builtins.pyi (16ms)
2024-03-28 10:30:37.020 [info] (35164) [BG(1)]   binding: file:///c%3A/Users/username/some_program/some_folder/linterbug/linterbug.py (0ms)
2024-03-28 10:30:37.033 [info] (35164) [BG(1)]   parsing: file:///c%3A/Users/username/.vscode/extensions/ms-python.vscode-pylance-2024.3.2/dist/typeshed-fallback/stdlib/typing.pyi [fs read 0ms] (9ms)
2024-03-28 10:30:37.039 [info] (35164) [BG(1)]   binding: file:///c%3A/Users/username/.vscode/extensions/ms-python.vscode-pylance-2024.3.2/dist/typeshed-fallback/stdlib/typing.pyi (5ms)
2024-03-28 10:30:37.048 [info] (35164) [BG(1)]   parsing: file:///c%3A/Users/username/.vscode/extensions/ms-python.vscode-pylance-2024.3.2/dist/typeshed-fallback/stdlib/types.pyi [fs read 0ms] (3ms)
2024-03-28 10:30:37.050 [info] (35164) [BG(1)]   binding: file:///c%3A/Users/username/.vscode/extensions/ms-python.vscode-pylance-2024.3.2/dist/typeshed-fallback/stdlib/types.pyi (2ms)
2024-03-28 10:30:37.055 [info] [Info  - 10:30:37 AM] (35164) Indexer background runner(2) root directory: file:///c%3A/Users/username/.vscode/extensions/ms-python.vscode-pylance-2024.3.2/dist (index)
2024-03-28 10:30:37.066 [info] [Info  - 10:30:37 AM] (35164) Indexing(2) started
2024-03-28 10:30:37.071 [info] (35164) [BG(1)]   parsing: file:///c%3A/Users/username/.vscode/extensions/ms-python.vscode-pylance-2024.3.2/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi [fs read 0ms] (3ms)
2024-03-28 10:30:37.072 [info] (35164) [BG(1)]   binding: file:///c%3A/Users/username/.vscode/extensions/ms-python.vscode-pylance-2024.3.2/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi (1ms)
2024-03-28 10:30:37.072 [info] (35164) [BG(1)]   parsing: file:///c%3A/Users/username/.vscode/extensions/ms-python.vscode-pylance-2024.3.2/dist/typeshed-fallback/stdlib/abc.pyi [fs read 0ms] (1ms)
2024-03-28 10:30:37.072 [info] (35164) [BG(1)]   binding: file:///c%3A/Users/username/.vscode/extensions/ms-python.vscode-pylance-2024.3.2/dist/typeshed-fallback/stdlib/abc.pyi (0ms)
2024-03-28 10:30:37.072 [info] (35164) [BG(1)] SemanticTokens range 0:0 - 12:24 at file:///c%3A/Users/username/some_program/some_folder/linterbug/linterbug.py (143ms)
2024-03-28 10:30:37.078 [info] (35164) [IDX(2)] scan packages file:///c%3A/Users/username/some_program/some_folder/linterbug ...
2024-03-28 10:30:37.079 [info] (35164) [IDX(2)]   read stdlib indices (21ms)
2024-03-28 10:30:37.086 [info] (35164) [BG(1)] analyzing: file:///c%3A/Users/username/some_program/some_folder/linterbug/linterbug.py ...
2024-03-28 10:30:37.086 [info] (35164) [BG(1)]   checking: file:///c%3A/Users/username/some_program/some_folder/linterbug/linterbug.py (17ms)
2024-03-28 10:30:37.086 [info] (35164) [BG(1)] analyzing: file:///c%3A/Users/username/some_program/some_folder/linterbug/linterbug.py (17ms)
2024-03-28 10:30:37.088 [info] (35164) [BG(1)] SemanticTokens full at file:///c%3A/Users/username/some_program/some_folder/linterbug/linterbug.py (0ms)
2024-03-28 10:30:37.088 [info] (35164) [BG(1)] indexing: file:///c%3A/Users/username/some_program/some_folder/linterbug/linterbug.py [found 3] (0ms)
2024-03-28 10:30:37.089 [info] (35164) Indexing Done: file:///c%3A/Users/username/some_program/some_folder/linterbug/linterbug.py
2024-03-28 10:30:37.092 [info] (35164) pytest configurations: {"message":"script","classes":["Test"],"files":["test_*.py","*_test.py"],"functions":["test"]}
2024-03-28 10:30:37.540 [info] (35164) [IDX(2)] scan packages file:///c%3A/Users/username/some_program/some_folder/linterbug (483ms)
2024-03-28 10:30:37.540 [info] [Info  - 10:30:37 AM] (35164) scanned(2) 224 files over 1 exec env
2024-03-28 10:30:37.542 [info] (35164) [BG(1)] SemanticTokens delta previousResultId:1711589437086 at file:///c%3A/Users/username/some_program/some_folder/linterbug/linterbug.py (0ms)
2024-03-28 10:30:38.071 [info] (35164) [IDX(2)] index packages file:///c%3A/Users/username/some_program/some_folder/linterbug ...
2024-03-28 10:30:38.071 [info] (35164) [IDX(2)]   index execution environment file:///c%3A/Users/username/some_program/some_folder/linterbug ...
2024-03-28 10:30:38.071 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/matplotlib/_afm.py [skipped: private or protected file] (0ms)
2024-03-28 10:30:38.071 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/matplotlib/_cm.py [skipped: private or protected file] (0ms)
2024-03-28 10:30:38.071 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/matplotlib/_color_data.pyi [skipped: private or protected file] (0ms)
2024-03-28 10:30:38.072 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/matplotlib/_constrained_layout.py [skipped: private or protected file] (0ms)
2024-03-28 10:30:38.072 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/matplotlib/_c_internal_utils.pyi [skipped: private or protected file] (0ms)
2024-03-28 10:30:38.072 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/matplotlib/_docstring.pyi [skipped: private or protected file] (0ms)
2024-03-28 10:30:38.072 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/matplotlib/_enums.pyi [skipped: private or protected file] (0ms)
2024-03-28 10:30:38.072 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/matplotlib/_fontconfig_pattern.py [skipped: private or protected file] (0ms)
2024-03-28 10:30:38.072 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/matplotlib/_layoutgrid.py [skipped: private or protected file] (0ms)
2024-03-28 10:30:38.072 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/matplotlib/_mathtext.py [skipped: private or protected file] (0ms)
2024-03-28 10:30:38.072 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/matplotlib/_mathtext_data.py [skipped: private or protected file] (0ms)
2024-03-28 10:30:38.072 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/matplotlib/_pylab_helpers.pyi [skipped: private or protected file] (0ms)
2024-03-28 10:30:38.072 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/matplotlib/_text_helpers.py [skipped: private or protected file] (0ms)
2024-03-28 10:30:38.073 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/matplotlib/_tight_bbox.py [skipped: private or protected file] (0ms)
2024-03-28 10:30:38.073 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/matplotlib/_tight_layout.py [skipped: private or protected file] (0ms)
2024-03-28 10:30:38.073 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/matplotlib/_version.py [skipped: private or protected file] (0ms)
2024-03-28 10:30:38.073 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Program%20Files/Python312/Lib/concurrent/__init__.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.073 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Program%20Files/Python312/Lib/idlelib/__init__.py [skipped: no '__all__' defined] (1ms)
2024-03-28 10:30:38.073 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Program%20Files/Python312/Lib/lib2to3/__init__.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.073 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Program%20Files/Python312/Lib/pydoc_data/__init__.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.073 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Program%20Files/Python312/Lib/test/__init__.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.074 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Program%20Files/Python312/Lib/turtledemo/__init__.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.074 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Program%20Files/Python312/Lib/urllib/__init__.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.074 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Program%20Files/Python312/Lib/wsgiref/__init__.py [skipped: no '__all__' defined] (1ms)
2024-03-28 10:30:38.074 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Program%20Files/Python312/Lib/xmlrpc/__init__.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.074 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Program%20Files/Python312/Lib/__phello__/__init__.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.074 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/adodbapi/__init__.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.074 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/alabaster/__init__.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.074 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/altgraph/__init__.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.075 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/Cython/__init__.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.075 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/distlib/__init__.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.075 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/lxml/__init__.py [skipped: no '__all__' defined] (1ms)
2024-03-28 10:30:38.075 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/matplotlib/_animation_data.py [skipped: private or protected file] (0ms)
2024-03-28 10:30:38.075 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/matplotlib/_blocking_input.py [skipped: private or protected file] (0ms)
2024-03-28 10:30:38.075 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/matplotlib/_cm_listed.py [skipped: private or protected file] (0ms)
2024-03-28 10:30:38.075 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/matplotlib/_image.pyi [skipped: private or protected file] (0ms)
2024-03-28 10:30:38.075 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/matplotlib/_internal_utils.py [skipped: private or protected file] (0ms)
2024-03-28 10:30:38.075 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/matplotlib/_path.pyi [skipped: private or protected file] (0ms)
2024-03-28 10:30:38.075 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/matplotlib/_qhull.pyi [skipped: private or protected file] (0ms)
2024-03-28 10:30:38.075 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/matplotlib/_tri.pyi [skipped: private or protected file] (0ms)
2024-03-28 10:30:38.075 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/matplotlib/_ttconv.pyi [skipped: private or protected file] (0ms)
2024-03-28 10:30:38.076 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/matplotlib/_type1font.py [skipped: private or protected file] (0ms)
2024-03-28 10:30:38.076 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/mpl_toolkits/__init__.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.076 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/msgpack/__init__.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.076 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/ordlookup/__init__.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.076 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/poetry_plugin_export/__init__.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.076 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/ptyprocess/__init__.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.076 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/pysubs2/__init__.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.076 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/pyximport/__init__.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.076 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/qdarkstyle/__init__.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.076 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/scipy/conftest.py [skipped: no '__all__' defined] (1ms)
2024-03-28 10:30:38.076 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/scipy/version.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.076 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/scipy/_distributor_init.py [skipped: private or protected file] (0ms)
2024-03-28 10:30:38.076 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/shellingham/__init__.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.077 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/sphinx_intl/__init__.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.077 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/sphinx_rtd_theme/__init__.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.077 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/vsengine/__init__.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.077 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/vsstubs/__init__.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.077 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/wheel/__init__.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.077 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/win32ctypes/__init__.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.077 [info] (35164) [IDX(2)]     indexing: file:///c%3A/Users/username/AppData/Roaming/Python/Python312/site-packages/pythonwin/pywin/__init__.py [skipped: no '__all__' defined] (0ms)
2024-03-28 10:30:38.084 [info] (35164) [IDX(2)]   index execution environment file:///c%3A/Users/username/some_program/some_folder/linterbug [found 7113 in 163 files] (26ms)
2024-03-28 10:30:38.085 [info] (35164) [IDX(2)] index packages file:///c%3A/Users/username/some_program/some_folder/linterbug [found 7113 in 1 exec envs] (52ms)
2024-03-28 10:30:38.085 [info] [Info  - 10:30:38 AM] (35164) indexed(2) 163 files over 1 exec env
2024-03-28 10:30:38.207 [info] [Info  - 10:30:38 AM] (35164) Indexing finished(2).
2024-03-28 10:30:44.478 [info] (35164) [FG] parsing: file:///c%3A/Users/username/.vscode/extensions/ms-python.vscode-pylance-2024.3.2/dist/typeshed-fallback/stdlib/typing.pyi [fs read 0ms] (8ms)
2024-03-28 10:30:44.482 [info] (35164) [FG] binding: file:///c%3A/Users/username/.vscode/extensions/ms-python.vscode-pylance-2024.3.2/dist/typeshed-fallback/stdlib/typing.pyi (4ms)
2024-03-28 10:30:44.491 [info] (35164) [FG] parsing: file:///c%3A/Users/username/.vscode/extensions/ms-python.vscode-pylance-2024.3.2/dist/typeshed-fallback/stdlib/types.pyi [fs read 1ms] (4ms)
2024-03-28 10:30:44.493 [info] (35164) [FG] binding: file:///c%3A/Users/username/.vscode/extensions/ms-python.vscode-pylance-2024.3.2/dist/typeshed-fallback/stdlib/types.pyi (2ms)
2024-03-28 10:30:44.498 [info] (35164) [FG] parsing: file:///c%3A/Users/username/.vscode/extensions/ms-python.vscode-pylance-2024.3.2/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi [fs read 0ms] (2ms)
2024-03-28 10:30:44.499 [info] (35164) [FG] binding: file:///c%3A/Users/username/.vscode/extensions/ms-python.vscode-pylance-2024.3.2/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi (1ms)
2024-03-28 10:30:44.503 [info] (35164) [FG] parsing: file:///c%3A/Users/username/.vscode/extensions/ms-python.vscode-pylance-2024.3.2/dist/typeshed-fallback/stdlib/abc.pyi [fs read 0ms] (1ms)
2024-03-28 10:30:44.503 [info] (35164) [FG] binding: file:///c%3A/Users/username/.vscode/extensions/ms-python.vscode-pylance-2024.3.2/dist/typeshed-fallback/stdlib/abc.pyi (0ms)

Pyright (the type checker upon which pylance is built) is working correctly here. This isn't a bug.
You have defined two instance methods get_bar and get_a_bar. Instance methods must have a self parameter. If your intent is for these to be static methods, you should add a @staticmethod decorator.
    @staticmethod
    def get_bar() -> bar:
        return foo.bar()

    @staticmethod
    def get_a_bar(a: int = 3) -> bar:
        return foo.bar(a=a)

@erictraut
I understand. However, in my case, I will never instantiate the foo class. Therefore, it's acceptable to call bar() as foo.bar() without using the @staticmethod decorator.

If you want a static type analyzer to understand your code, you will need to decorate these as @staticmethod.

@erictraut
If this behavior is expected, I still believe it is non-conformant.
At least in my opinion, these type hints should either not function at all, or work perfectly. But not partially working.
This means:

test1 should not be hinted as a bar() object.
Neither foo.get_bar() nor foo.get_a_bar() should hint their return type as a bar() object.
Alternatively,
test2 should be hinted as a bar() object, which is what I expect."

Add a @staticmethod decorator if you want this to work with pyright.

@erictraut
We should not merely avoid triggering bugs as a solution; instead, we should address and resolve the underlying issues that cause the bugs, right?


Undercover picking up changes from master and reporting false negative

I have a branch which implements undercover in our ci (buildkite) pipeline. I have added undercover as a step after all specs run. I see false negative results every now and then. The changes that undercover points out needs coverage are always things someone else on the team has merged to master recently.
The command that I run is undercover --lcov <file.lcov> --compare origin/master
Steps:

Create a branch and add all logic for undercover to work.(logic - Generate all lcov files in each ci container, aggregate them into one file which is passed as an argument to undercover command. Similar to what is described here - https://github.com/grodowski/undercover/blob/master/docs/circleci_advanced.yml )

Push the branch to build on ci - it works fine so far. Undercover does not identify any non-covered changes

Pull master into my branch and push branch to origin

The ci build that was triggered shows bunch of methods as not covered. These are changes already on master, merged by team member recently.

The changes which undercover reports as uncovered are not part of what I am working on.

Hi! Thanks for using undercover and reporting the issue.
I couldn't reproduce your exact scenario based on the description, so I'd welcome more details. A sample git tree is one option.
However, I noticed a strange behaviour of undercover -c master when master has diverged from a feature branch with new commits.
#  git log --graph test-untested master
* commit a00a293bb7c2284b0436de0c331f47f6f8761352 (HEAD -> master)
|
|     change #3
|
| *   commit bbe55cd3e0435861d0411c35c5d0c2307d7f3e8b (test-untested)
| |\  Merge: 0d8ee01 0279ca5
| |/
|/|     Merge branch 'master' into test-untested
| |
* | commit 0279ca5d7a0ae2c1e6aa13d79708dd2dff4b9015
| |
| |     untested :o #2
| |
| * commit 0d8ee017d8c37ac6dba4efab6cae5151f61d831d
|/
|       foo #1
|
*   commit a71309fa6e5f9465ec040f36b3f4f53e64b51824 (origin/master)

Change 3 is not included in the undercover changeset. Specifically:

undercover would currently compare bbe55cd3 with a71309fa6
we'd expect it to compare bbe55cd3 with a00a293b

Not sure if this relates to your problem, but I will take a deeper look and possibly change
https://github.com/grodowski/undercover/blob/a71309fa6e5f9465ec040f36b3f4f53e64b51824/lib/undercover/changeset.rb#L76
to something like
repo.branches.find { |b| b.name == compare_base }.target

This could be more predictable than merge_base in more complex workflows
FYI https://git-scm.com/docs/git-merge-base

@hiralmodi22 this could help with diff issues, please lmk if it does

@grodowski To simplify the branch illustration a bit;
(branch)       M - N - O - P
              /       /
(master) A - B - C - D - E - F

Briefly, we branched at B, and then ran git merge master at D.
So if we want to see what untested code blocks would be introduced by our branch, we would want to diff P vs D, correct? #68 causes us to diff P vs. F, which will include changes from E and F. The result is that Undercover would include irrelevant changes in its results.
Unless I'm missing something?
To get the correct commit to diff, I've been running git merge-base master current-branch locally, which looks like the same strategy as before #68. Granted, my workflows aren't quite as complex as in your example, so that may be a poor general-purpose solution. One suggestion, as a compromise, would be to have usage of merge_base vs rev_parse controlled via a command-line switch.
All that being said, I'm not totally sure what caused the original issue @hiralmodi22 was encountering. Could be a nuance of shallow clone? Git is more clever about that than it used to be, but could be a gap here.

Thanks for your comment @Redapted. I am not sure what caused the issue either and it would be cool to get more input from @hiralmodi22.
Looking into the rev-parse versus merge-base question, I think it depends on the workflow we want undercover to best support.
In your example, if all code changes went through review (including undercover) that used merge-base, we would be sure that all additions from E and F are covered and we could safely check P w.r.t. D.  On the other hand rev-parse could yield code locations that have been deleted or changed in F, but are still present in P, meaning they require tests if we merge P into F. Should we still call these false positives? I might as well be missing some obvious edge case here
There might be some confusion too, because undercover triggers on class, method and block diffs instead of individual lines.
Finally, #68 is still unreleased and I'm debating whether to just roll it back from master. Not sure if there's really that much benefit in using rev-parse.

I'm reverting #68 from master a closing this issue as not much has happened here.


Bring Back Preboot Language Servers

Reverts the revert: https://github.com/dotnet/aspnetcore-tooling/pull/1940
Did validations on LSP Local + LSP Liveshare.
Fixes: https://github.com/dotnet/aspnetcore/issues/22331

Local codespaces

To ensure things don't fall over. Also in local codespaces scenario it'll be important to verify the C# experience as well because when we originally did this it broke that experience.

How would I validate local codespaces? Wouldn't it need to be merged & propagated to codespaces? Is there a local variant?

How would I validate local codespaces?

https://dev.azure.com/devdiv/DevDiv/_wiki/wikis/DevDiv.wiki/6693/Nexus-hosting-advanced-scenarios-and-configuration

To ensure things don't fall over. Also in local codespaces scenario it'll be important to verify the C# experience as well because when we originally did this it broke that experience.

Did some basic validations, is there something specific which broke previously?
I noticed hover descriptions had duplicated bodys, however I believe this is likely an unrelated issue?

/cc @dibarbet


Migration from other project management tools like pdm or poetry

I personally have been using pdm to manage python projects, and I'd really love a way to easily migrate a couple of them over to try rye out. If this already exists or is being discussed elsewhere, my bad, but I couldn't find anything that looked like this in the gh issues or the website.
rye init fails when a project already exists, so having at least some way of adding rye management to an existing project would be a first step.
I'm not sure about how well an automated migration tool would work, since it would involve supporting the (potentially changing) features of other project managers, but maybe the migration tool could at least supporting the detection of the project.toml keys for various tools like tools.pdm and tools.poetry and refer the user to a particular "migration guide" on the website?
Otherwise maybe some sort of migration plugin system, where the migration implementation is managed independently from the main project. That way people could bring their own migration implementation without tying it to the main project's version. Maybe a couple plugins under the astral-sh org for some of the more popular alternative tools.
so, as far as expectation, it would be something like:

rye init --migrate flag which tells the initializer to add rye non-destructively to the project
rye init --migrate=MIGRATE_TOOL where MIGRATE_TOOL is a string which represents some version of another pypi-registered project which handles the migration from a specific tool, examples:

--migrate=rye_migrate_from_pdm for the latest version of the astral-sh provided pdm migration tool
--migrate=rye_migrate_from_poetry==2.0.0 for the 2.0.0 version of the astral-sh provided poetry migration tool

poetry2rye exists, haven't tried it though. We're evaluating this direction on our team so curious if there's an official recommendation


[Small Cleanup] Remove console log

Removing an unnecessary console log. Also, first warmup PR :)

closing to add changes to development branch instead


package.json: Update node requirement to v20 or greater

Change-type: patch
Addresses https://github.com/balena-os/jetson-flash/issues/179
The warning reported in #179 is not present when issuing npm install .  on a host with Node v21.6.2 installed.

@acostach My original post of Issue #179 was wrong. The drivelist package supports node >=18 for drivelist v11.2.0+. The problem was that my build brought in drivelist v11.1.0. I will review and clarify here.

@acostach My original post of Issue #179 was wrong. The drivelist package supports node >=18 for drivelist v11.2.0+. The problem was that my build brought in drivelist v11.1.0. See the issue for more discussion. Let's understand that first before proceeding here to be sure we update all the right components.


Firebreak - Data Hub Test Data - Investment Project Generator

Description of change

[!IMPORTANT]
This is part of the Firebreak project "Data Hub Test Data" and is being merged into a feature branch.

This PR creates an initial investment project generator that can be used to create a batch of random projects, simply by calling the script. It also lays out some boilerplate code to allow other generators to be added more easily going forward.
Checklist

[ ] Has this branch been rebased on top of the current main branch?

Explanation
The branch should not be stale or have conflicts at the time reviews are requested.

[ ] Is the CircleCI build passing?

General points

Other things to check

Make sure fixtures/test_data.yaml is maintained when updating models
Consider the admin site when making changes to models
Use select-/prefetch-related field lists in views and search apps, and update them when fields are added
Make sure the README is updated e.g. when adding new environment variables

See docs/CONTRIBUTING.md for more guidelines.

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

Project coverage is 96.57%. Comparing base (35b1e02) to head (112f072).
Report is 2 commits behind head on firebreak/data-hub-test-data.

Additional details and impacted files
@@                      Coverage Diff                      @@
##           firebreak/data-hub-test-data    #5343   +/-   ##
=============================================================
  Coverage                         96.57%   96.57%
=============================================================
  Files                               927      927
  Lines                             21989    21989
  Branches                           1967     1967
=============================================================
  Hits                              21236    21236
  Misses                              610      610
  Partials                            143      143

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


Add Mint Programming Language to SUPPORTED_LANGUAGES.md

Adds Mint programming language to the list of supported languages

Could you please add a suitable README to your repository as well?  Thanks!

@joshgoebel Done


Create healthyr

After creating the pull request, the R-multiverse GitHub bot will review your contribution on its next scheduled run. Thank you for your contribution!

Closing for the time being as the GitHub release has not yet been made.

Published release https://github.com/humaniverse/healthyr/releases/tag/0.0.1


cmd/go: unable to get x/crypto with go get

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

$ go version
go version go1.13 darwin/amd64

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env

What did you do?
$ go get -u golang.org/x/crypto/
What did you expect to see?
nothing
What did you see instead?
package golang.org/x/crypto: unrecognized import path "golang.org/x/crypto" (https fetch: Get https://golang.org/x/crypto?go-get=1: EOF)

What happens if you visit that URL in a browser or using curl?

It forwards me to the docs page.  My assumption is that this was the correct place to put an issue that I was not able to get the crypto library, given it was from golang.org.

Yes, this is a reasonable place to file an issue, but I don't know how to help you. Perhaps there's something extra in your browser's configuration that allows it to contact golang.org, or something in your Go environment that breaks it.

I have no idea why you are seeing that particular error.
But go get golang.org/x/crypto is not expected to work as that package does not exist.  There are a number of packages under x/crypto, as can be seen at https://godoc.org/golang.org/x/crypto.  But x/crypto is not itself a package.  What happens if you try, say, go get golang.org/x/crypto/blowfish?

Closing, since some time has passed without update. Please comment if you're still seeing this.


Dh 679 buyer account page

Ticket:  https://trello.com/c/FiR3NLyZ/679-buyer-account-page

cherry picked onto another PR


Fix support for "std" import path

Since Go 1.4, stdlib lives in GOROOT/src, not GOROOT/src/pkg. The wrong
gorootSrcPkg broke the "std" pattern.

There are a few more upstream changes that we should pick up at the same time. I'll take care of this.

See 8f348af.


Fix html, body styling, update head

I was testing the site in Lighthouse, and it was complaining that we didn't have a <!DOCTYPE html>.  We do have it, but the way that the styles for html and body were being done by Chakra UI, it was putting a <style> tag outside the document.  This fixes it.
I also updated the <head> to fix the title and description.

I had to modify this a bit to work on the login page.


Extend scope with "completion" command

Completion of commands is enabled by calling:
source <(./bin/linux/x86_64/scope completion bash)
Fixes #361
Ref: https://github.com/spf13/cobra/blob/master/shell_completions.md#creating-your-own-completion-command
Tested with following binary: ./bin/linux/x86_64/scope
TODO:

[x] Extend Docker etc shell completion configuration with scope completion config

I've reviewed this and don't have any comments...  I'm not merging yet because I understand that @michalbiesek is trying to make sure that we get the command completion enabled in the AppScope container that we publish on github.  It looks to me like the changes here to docker/base/Dockerfile would be what we want, but I'm not certain...  I'll wait to hear back on this.

Rebased.
With changes from #528 (thanks @pdugas !) the PR could be tested in following way:

make image
docker run -it --entrypoint bash

FYI: impact on the image size:
Before the changes from the PR:
REPOSITORY                              TAG               IMAGE ID       CREATED         SIZE
cribl/scope                             dev-x86_64        17c9dcff82a4   8 seconds ago   181MB

After the changes from the PR:
REPOSITORY                              TAG               IMAGE ID       CREATED         SIZE
cribl/scope                             dev-x86_64        4843fe0eec62   3 seconds ago   183MB

Merging.  Thanks all!


Adds scores, scoreboard and combo counter to ddr mode

I may be getting better at Stomp, but it just felt better when testing!


fix: configuration subscribe nil ptr map

Description

Issue reference

Please reference the issue this PR will close: #[issue number]
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
[x] Unit tests passing
[x] End-to-end tests passing
[x] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[x] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[x] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

This is already fixed in 1.5 via https://github.com/dapr/dapr/pull/3971


function to exclude use_treesitter on some file types?

Im aware that treesitter for python is a bit buggy and im not asking for a fix, i want to have some function that will make the use_treesitter option to be off for some file types like .py file.
i have found that keeping that option off when editing a python file results in good indentation, exactly the same as vscode
but having this option on (in combination with show_trailing_blankline_indent = false) results in faulty indentation like in lua:

somewhat related to: #226 #362

Context
current configuration:
require("indent_blankline").setup {
    char = "▏",
    context_char = "▎",
    show_trailing_blankline_indent = false,
    show_current_context = true,
    show_current_context_start = true,
    use_treesitter = true,
}

use_treesitter: on

use_treesitter: off

I might consider adding this.
But TBH, just turning treesitter indent off should give you better results in most filetypes, not just Python.

I might consider adding this. But TBH, just turning treesitter indent off should give you better results in most filetypes, not just Python.

treesitter on

treesitter off

eh not really, (lua file)

I might consider adding this. But TBH, just turning treesitter indent off should give you better results in most filetypes, not just Python.

wouldnt it be possible to toggle this option on/off by cheching what filetype is the buffer in neovim?

Hi, did anyone find any solution to this yet?

wouldnt it be possible to toggle this option on/off by cheching what filetype is the buffer in neovim?

You can change (almost) any option of indent-blankline global, per tab, and per buffer.
So if you want to turn off treesitter only for Python, add vim.b.indent_blankline_use_treesitter =  false to ftplugin/python.lua
I think this is a good enough solution, I won't add a dedicated option for excluding filetypes for treesitter.


boards: s32z270dc2_r52: support board revision D

Add a board revision D for the s32z270dc2_r52 boards and make the existing revision B the default. The main difference between these revisions affecting current Zephyr port is the USB/UART port that was moved from LINFlexD instance 0 to 9.

hi @dleach02 @mmahadevan108 may I have a look on these changes? thanks


version = 0.17.3, added default for types.rs

I'm afraid #115 was a breaking change, and we can't just bump the patch version. Let's bump the minor?


Debugger is not working

From @wtang3 on November 20, 2015 3:16
Getting error when running app in debug mode.
When hitting play on debugger, debugger options appear for split second and exception occurs.
error while processing request '{_request}' (exception: {_exception})

OS: Mac
Copied from original issue: Microsoft/vscode#306

The problem with the unreadable error message has been fixed through PR #4

Thank you very much weinand!

@weinand, I'm also getting the same error. How we can solve this?

@mbcrump, I'm getting the same error. How we can solve this?

@amansingh36 I have created a new release of the mono-debug adapter that should fix the problem with the unreadable error message. Please give it a try and let me know what the real error is.
A 'how-to install vsix extensions' can be found here.

@weinand, Thanks for the reply. I've installed your extension via below method still receiving error.
INSTALL METHOD:
"You can also install a .vsix by opening the file from within VS Code. Run File | Open File... or unassigned and select the extension .vsix."
ERROR:
error while processing request '{_request}' (exception: {_exception})
Please help. Thanks

@weinand, I'm trying new method which will load the extension every time when Visual Studio Code will run. But the problem is I don't know where the ".vscode/extensions" folder is located on Mac.
NEW METHOD TRYING:
If you want to load your extension or customization each time VS Code runs, copy your project to a new folder under .vscode/extensions.
$HOME/.vscode/extensions/myextension

@weinand, tried both ways to install but didn't helped. I also found one error in OUTPUT window:
[ERROR:OmniSharp.Dnx.DnxPaths] The specified runtime path 'default' does not exist. Searched locations

@weinand, Everything sorted except ERROR:
error while processing request '{_request}' (exception: {_exception})

my pre-release version 0.10.2 of mono-debug had the wrong publisher, so you are still seeing the original mono-debug. Could you please try it again with this release 0.10.3.
First install the previous mono-debug extension by

pressing F1
type "ext"
select "Show Installed Extensions"
pick "mono-debug 0.10.2"
click the "X" on the right of the entry to delete it.
let VS Code restart

Then install 0.10.3 mono-debug by opening it via VS Code open action.

Where is .vsix file? Because I don't know how to install via source.

Sorry, I forgot to attach it...

@weinand, Thanks for the support. But still receiving error:
"error while processing request 'launch' (exception: The best overloaded method match for `OpenDebug.Terminal.LaunchInTerminal(string, string, string[], string, string[], System.Collections.Generic.Dictionary<string,string>)' has some invalid arguments)"

@weinand, Thanks for the support. But now receiving another error:
"error while processing request 'launch' (exception: The best overloaded method match for `OpenDebug.Terminal.LaunchInTerminal(string, string, string[], string, string[], System.Collections.Generic.Dictionary<string,string>)' has some invalid arguments)"

yes, as I said above, I first had to fix the problem with the unreadable error message. Now, that we can see the real error message, I will reopen this bug and work on the fix. Thanks for helping me with this.

@amansingh36 what version of mono do you have installed on your OS X?

The latest Mono release: 4.2 Stable (<IP_ADDRESS>)

The latest Mono release: 4.2 Stable (<IP_ADDRESS>)
Mono for Mac OS X Universal (32 & 64 bit) preview
This package contains both 32 and 64-bit Mono for OS X.

@amansingh36 I think I know what the problem is. Could you please remove the environment variables (the "env": [...])  in your launch config and see whether that makes a difference?

@weinand, If I remove "env": { }" still receiving error:
error while processing request 'launch' (exception: The best overloaded method match for `OpenDebug.Terminal.LaunchInTerminal(string, string, string[], string, string[], System.Collections.Generic.Dictionary<string,string>)' has some invalid arguments)

@amansingh36 Could you please try this release.

@weinand Everything working perfectly fine now. Thanks
I've an idea shall we write an article together on Visual Studio Code for Setup to Use (End to End). Will you help?

@weinand, Everything working perfectly fine now. Thanks for your help.
I've an idea shall we write an article together on Visual Studio Code for Setup to Use (End to End). Will you help?

@weinand, Everything worked perfectly fine with your latest release - 0.10.4. Thanks for your help and prompt replies.
I've a personal request for you, will you be interested to spare some time from your busy schedule and become an author on Visual Studio Code, Visual Studio, etc. at Asian Fox Developments, Blog (Worldwide) www.asianfoxdevelopments.com.
I will be obliged. Thanks

@weinand, I've a personal request for you, will you be interested to spare some time from your busy schedule and become an author on Visual Studio Code, Visual Studio, etc. at Asian Fox Developments, Blog (Worldwide) www.asianfoxdevelopments.com.
I will be obliged. Thanks
Aman Singh
Senior .NET Dev.
Technical Department
Asian Fox Developments


embedded: Fix a few problems with vtable specialization

Make sure to specialize tables of superclasses
Fixes an IRGen crash if a superclass of a class is generic and not used otherwise.
rdar://122405558

make the ManagedBuffer initializer public in the embedded stdlib
Otherwise derived classes cannot be specialized.
Fixes a compile time error when using ManagedBuffer in embedded mode.
rdar://122414669

support printing and parsing specialized vtables

@swift-ci test

@swift-ci test

@swift-ci test

@swift-ci smoke test


New version: Ryujinx.Ryujinx version 1.1.1154

Pull request has been created with komac v2.0.3 :rocket:
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

No errors to post.

(Automated response - build 694.)

@wingetbot waivers Add Validation-Executable-Error

For moderators
This account is automated by Github Actions and the source code was created by CoolPlayLin. If you have any questions about any pull request, don't hesitate to ping @Exorcism0666, I'll get a notification.

[!important]
Please carefully review these Pull Request before merging. If it is a Pull Request for removing incorrect content and the URLs are issue, free upon manual checking, please close this Pull Request directly. (It is best to inform Exorcism0666 of the closure.)

良い一日をお過ごしください！


Make params compatible with old ruby version

Poms wouldn't run inside Zappelin because of this.

I guess this PR can just be closed as duplicate.


FAM load testing - phase 1

Describe the task
Perform level 2 testing
Acceptance Criteria

[ ] Topic documented in Confluence  -what are the levels (1,2,3), objectives, tools and process description
[ ] Plan for load testing - performance risk assessment, user/role volume calculation, responsiveness requirement for login, etc.

--Split out to new ticket:

[ ] Generate Realistic user/role volumes
[ ] Test UI responsiveness based on bigger user/role volumes
[ ] Demo / pair with team

Additional context

Good topic for internal demo and/or FDS demo

Confluence documentation: https://apps.nrs.gov.bc.ca/int/confluence/display/FSAST1/Load+Testing


DockerHub

Hello team,
Could you please provide and keep up-to-date a docker image / docker compose ?
Thanks

I created an initial docker build for this, you're welcome to copy / use it as you wish
https://hub.docker.com/r/kwillia/filegator_docker
https://github.com/kwilliams312/filegator_docker_image

After a year working on CI and so on, it will be easier to create a CI and automate the workflow to push every release on dockerhub. @alcalbg Why don't you create a workflow dedicated on that with filegator account ?

Thanks everyone. Yes, CI pipeline would be the optimal solution. I am working on another project atm, will do that eventually.

Official Docker hub image is here:
https://hub.docker.com/r/filegator/filegator
TODO: automated build

Any chance for arm support?

just added arm/v7 and arm64, can you try again?
https://hub.docker.com/r/filegator/filegator

amazing fast response
sadly getting this error

Creating filegator ... done
Attaching to filegator
filegator    | AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using <IP_ADDRESS>. Set the 'ServerName' directive globally to suppress this message
filegator    | (13)Permission denied: AH00072: make_sock: could not bind to address <IP_ADDRESS>:80
filegator    | no listening sockets available, shutting down
filegator    | AH00015: Unable to open logs
filegator exited with code 1

I guess I'm probably missing some ENV vars but docker-compose nor Dockerfile in repo doesn't specify some.

Huh, this seems like some permissions issue. Can you try with root user or something?

Dockerhub CI workflow created, closing this now

Sadly running uder root is not a solution. Since the error is from the container complaining about env var l would racommend to attach docker-compose file.
Also another "fast closing issue" l see :)

Check this https://github.com/filegator/filegator/blob/master/docker-compose.yml
I don't see complains about env vars, from your log it's permission issue. I could be wrong tho.
filegator    | (13)Permission denied: AH00072: make_sock: could not bind to address <IP_ADDRESS>:80

Anyone else with similar issues running this? On arm? As non-root? Help?
docker run -p 8888:80 filegator/filegator:v7.8.5-multiarch

http://localhost:8888

How I said eadlier - the error is within the container so running the container as a root doesn't help.
odroidxu4:~:% docker run --rm -p 8883:80 filegator/filegator
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using <IP_ADDRESS>. Set the 'ServerName' directi
ve globally to suppress this message
(13)Permission denied: AH00072: make_sock: could not bind to address <IP_ADDRESS>:80
no listening sockets available, shutting down
AH00015: Unable to open logs
odroidxu4:~:% sudo docker run --rm -p 8883:80 filegator/filegator
[sudo] password for n1:
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using <IP_ADDRESS>. Set the 'ServerName' directi
ve globally to suppress this message
(13)Permission denied: AH00072: make_sock: could not bind to address <IP_ADDRESS>:80
no listening sockets available, shutting down
AH00015: Unable to open logs

I am getting the exact same error in v7.8.7.

Ok, can someone try one more time with arm please?
docker run -p 8080:8080 filegator/filegator:v7.9.2-multiarch
http://localhost:8080
ref: https://github.com/filegator/filegator/commit/37d25ef88152af5b0019f627905909bf8601ff56

I'm able to start the service but sooner of later I'm getting [Wed Jan 25 20:36:36.164049 2023] [mpm_prefork:notice] [pid 1] AH00170: caught SIGWINCH, shutting down gracefully and it dies.

Yes, I've noticed this as well. It sounds stupid, but it happens when you resize your terminal window, hence the name of the signal - window change!
https://bz.apache.org/bugzilla/show_bug.cgi?id=50669
Anyway, this should not happen if you're using it as a normal service, with docker compose etc.

Cannot confirm that. Havent resized the window term at all.

Are you getting the SIGWINCH if you detach it and run it as a background service?
docker run -d --name filegatorservice -p 8080:8080 filegator/filegator:v7.9.2-multiarch
docker logs filegatorservice -f

Cannot explain that but the issue vanished. so i guess the whole SIGWINCH problem is gone.
I have 2 quick questions and 2 suggestions:
question a)  How do I completely disable auth? Tried to comment out Auth module in config - got fatal error. Ended up with giving all pesmissions to Guest and then delete Admin user.
question b) How to make run the whole thing under a different user but www-data? This is crucial for new files that are created by this tool.
suggestion a) Please state in docs that app root in container is /var/www/filegator so when one wants to use it's own config file via volumes he can add something like:
volumes:
  - ./config/configuration.php:/var/www/filegator/configuration.php

This is very common among Docker images.
suggestion b) Plese state in docs that THE DIRECTORY Filegator is gonna manage sits under /var/www/filegator/reporitory. One can then do:
volumes:
  - ./my_dir:/var/www/filegator/repository

Thanks in advance and my apologies if the suggestion stuff already are in docs and I overlooked them.

Giving all permissions to Guest is the way to disable auth. That's how it is done here: https://demo.filegator.io
To change the user you must customize the Dockerfile. However, file permissions for volumes and matching the uid/gid with host seems to be a huge mess.
All the info related to Docker is now listed here: https://hub.docker.com/r/filegator/filegator
Suggestions are welcome.

Multiarch builds seems outdated, what is the reason?

The CI workflow is missing multiarch config/setup https://github.com/filegator/filegator/blob/master/.github/workflows/ci-dockerhub.yml

Giving all permissions to Guest i

Hi, would you explain how to give all permissions to Guest? Thank you!

Automatic multiarch build added in #517
docker pull filegator/filegator:latest-multiarch
or specific version:
docker pull filegator/filegator:v7.12.0-multiarch


argo submit --log fails on 2.9.1

Using argo 2.9.1:
argo submit --log workflows/wk.yaml

returns:
Error: unknown flag: --log
Usage:
  argo submit [FILE... | --from `kind/name] [flags]

Examples:
# Submit multiple workflows from files:

  argo submit my-wf.yaml
...

Associated PR is https://github.com/argoproj/argo/pull/3279

Ok I just realized on the PR it is planned for 2.9.10.


Return token as JSON, remove Room from grant

In order for the Video Quickstart JS to be able to process the token, it needs to be returned as a JSON.

As far as I know all of the token servers return the same format - a raw text body. Please don't merge a change unless its coordinated with the other dependencies of this project:
https://github.com/twilio/video-quickstart-swift
https://github.com/twilio/video-quickstart-objc
https://github.com/twilio/video-quickstart-android

The Node.js quickstart's /token returns JSON:
https://github.com/twilio/video-quickstart-js/blob/master/server/index.js#L73-L76
And the JS client expects JSON:
https://github.com/twilio/video-quickstart-js/blob/master/quickstart/src/index.js#L43
Good point about the other dependencies, I'm not sure what format those need.
But this should probably be unified one way or the other.


feat: add custom attributes for assets

Follow up on an issue/request.

Custom attributes function as an extra dictionary where people can specify their own asset properties

To add a custom attribute, specify --custom-attribute my_key=my_value
To remove a custom attribute (in update), specify --custom-attribute my_key=""

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact<EMAIL_ADDRESS>with any additional questions or comments.
Thank you for contributing to Azure IoT Operations tooling!
This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines
Intent for Production

[ ] It is expected that pull requests made to default or core branches such as dev or main are of production grade. Corollary to this, any merged contributions to these branches may be deployed in a public release at any given time. By checking this box, you agree and commit to the expected production quality of code.

Basic expectations

[ ] If introducing new functionality or modified behavior, are they backed by unit and/or integration tests?
[ ] In the same context as above are command names and their parameter definitions accurate? Do help docs have sufficient content?
[ ] Have all the relevant unit and integration tests pass? i.e. pytest <project root> -vv. Please provide evidence in the form of a screenshot showing a succesful run of tests locally OR a link to a test pipeline that has been run against the change-set.
[ ] Have linter checks passed using the .pylintrc and .flake8 rules? Look at the CI scripts for example usage.
[ ] Have extraneous print or debug statements, commented out code-blocks or code-statements (if any) been removed from the surface area of changes?
[ ] Have you made an entry in HISTORY.rst which concisely explains your user-facing feature or change?

Azure IoT Operations CLI maintainers reserve the right to enforce any of the outlined expectations.
A PR is considered ready for review when all basic expectations have been met (or do not apply).

Support for issue #203


Any link, and the text after, is stripped from the task when dragged to a new time.

Describe the bug
When there is a link in a task description the link and all text after it is removed when dragging the task to a new time. It also doesn't appear in the planner view.
To Reproduce
Steps to reproduce the behavior:

Add a task with a link such as "go [[here]] for more info"
In the planner notice it will only display "go"
Drag the task to a new time
The original task now reads "go" with no link or text after

Expected behavior
Links appear in planner and are not stripped from the task when it is moved.

Hey @gypsyav this is unfortunately not reproducible with the steps you provided. But I reproduced the behavior with additional information.
As long as the task does not end with something like  [completion:: 2024-06-12] as done when checking the box with the Tasks plugin enabled, it seems to work fine. To be precise whenever the regex"[.::.]"gm appears anywhere in the text, only the text before the first bracket is recognized.

Please update and re-check.

The issue is still persisting for me with 0.25.0
Here and example to reproduce it:
Add this to the planner section

[x] 19:00 - 19:30 Reproduce issue [[Some Link]]  [completion:: 2024-11-04]

You should first of all see that only "19:00 - 19:30 Reproduce issue" is shown in the day planner widget and that as soon as you drag this only the text shown remains in the note cutting of the link and the completion date dataview property.


fix(docker): Make Gunicorn max_requests and max_requests_jitter adjustable

SUMMARY
This PR allows to adjust Gunicorn max_requests and max_requests_jitter which allows to restart the Gunicorn worker process periodically.
This is a simple method to help limit the damage of memory leaks like one reported in 15132.
For more details, Please refer to: https://docs.gunicorn.org/en/stable/settings.html#max-requests
Default values are set to zero to match gunicorn's default i.e. automatic worker restarts are disabled by default.
Note: This change is non-disruptive, no end user will be impacted unless they turn on settings.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS
Set the values like:
gunicorn --max-requests 1024 --max-requests-jitter 100 ....
ADDITIONAL INFORMATION

[x] Has associated issue: 15132
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

@zhaoyongjie please review and approve.

Seeing this in logs during docker compose (posting in case related):
superset_app | gunicorn: error: argument --max-requests: expected one argument

Seeing this in logs during docker compose (posting in case related):
superset_app | gunicorn: error: argument --max-requests: expected one argument

getting default value should be ${parameter:-word}. I will push the fix.

sorry. my bad, i missed the hyphen. Thanks for reporting @z6cr0b3rts and thanks for the quick fix @zhaoyongjie.

@evkuzin updated build is available now.

We have tried this solution sometime back with custom docker image, but faced lot of intermittent http504s.
Our setup to serve requests is aws alb -> superset pods in k8.
Please share your findings as well @mdeshmu @zhaoyongjie @evkuzin

I have it enabled for a while now but I don’t see any 504's.
For you, Is it 502 bad gateway or 504 gateway time out?

504 gateway timeout @mdeshmu .

@low-on-mana Please make sure you have appropriate jitter parameter value as it is needed to avoid simultaneous restarts of workers.
Another possibility, Maybe your queries are occasionally taking longer time. Please make sure you are having large enough timeout values at all places.
This is what i have,
ALB idle timeout (120s) >
GUNICORN_TIMEOUT (115s) =
SUPERSET_WEBSERVER_TIMEOUT
I also have ecs task (gunicorn + superset) directly under alb and was intermittently getting 502 bad gateway because of low keep alive of gunicorn. Then i set it below and all errors were gone.
GUNICORN_KEEPALIVE (125s) >
ALB idle timeout (120s)

@mdeshmu Thanks for sharing this, I will check these configuration out.


Remove unnecessary lock on stats thread

Motivation
We found there has a block between the pulsar-ordered executor and
the pulsar-stats-updater executor.
The pulsar-ordered executor is trying to createManagedLedgerOffloader,
and the pulsar-stats-updater is getting the compactor. Both them want
to get the lock.
We have an improvement about the createManagedLedgerOffloader before.
https://github.com/apache/pulsar/pull/15883
We are using getCompactor(false) for the stats related operations.
The getCompactor is guarded by synchronized. Actually, the stats
just want to get the current compactor without initializing it. We
don't need to use synchronized to guard this operation.
Modifications
Remove unnecessary synchronized on the getCompactor method.
Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API: (yes / no)
The schema: (yes / no / don't know)
The default values of configurations: (yes / no)
The wire protocol: (yes / no)
The rest endpoints: (yes / no)
The admin cli options: (yes / no)
Anything that affects deployment: (yes / no / don't know)

Documentation
Check the box below or label this PR directly.
Need to update docs?

[ ] doc-required
(Your PR needs to update docs and you will update later)

[x] doc-not-needed
(Please explain why)

[ ] doc
(Your PR contains doc changes)

[ ] doc-complete
(Docs have been already added)

@zymap I have updated the PR title, please check.


Update Django to 1.10

I don't know well Django so I would prefer to get a review on this change.
cc @brettcannon @alex @fijal.

Keep in mind, this is changing the code that's running, so it's really a different benchmark.

alex: "Keep in mind, this is changing the code that's running, so it's really a different benchmark."
I know. I consider that you should only compare benchmark results produced with the same version of the benchmark suite. At this point, I don't really care of backward compatibility. I prefer to upgrade dependencies to be more representative of nowadays applications.
The previous Python benchmark suite used a different approach of duplicating completely benchmarks to upgrade a library. Because it's more complex to upgrade libraries, old versions of libraries were used. For example, it uses Mercurial 1.2.1 which was released in 2009 (7 years ago).
But you are right that we need a clear policy about upgrading library. For example, use semantic versionning and increase the major version number when a library is upgraded to notice that results become incompatible?

FYI I increased the "major" version from 0.1.x to 0.2.0 because Django was upgraded.


Update update-intro.html

This documentation is wrong. See https://github.com/kubernetes/kubernetes/issues/94533

It does take a bit of setting up.

Exactly! In fact, it takes a lot of set up and quite a bit of trial and error to get the timings right. There is no article that details this process or what is required in order to get a zero down time deployment. At best this is very misleading because every time I have explained to a developer in my company the process required to get a true zero down time deployment, their response has always been

I thought Kubernetes offered that out of the box

My company has a support contract with a Kubernetes vendor who provides production support and their response to this question was...

There will be blips during an upgrade but there's no way around this, the pods need to be redeployed

Due to the way Kubernetes tears down pods, the pod can and will often be terminated before it is removed from the service. I opened https://github.com/kubernetes/kubernetes/issues/94533 but no one has addressed the issue. Either the issue needs to be addressed or the documentation should be updated to reflect reality.
If you disagree, lets engage the relevant SIG.

As it happens I aslo work for a Kubernetes certified service provider, and we provide support to customers who run Kubernetes in production. I contend that you can set up a web workload to deploy (planned) changes with zero downtime, using Kubernetes.
As a technical lead for SIG Docs, I would 100% welcome a PR to add a tutorial about how to do that (it's somewhat involved). However, I couldn't accept a PR to document that “a rolling update will cause a short period of downtime” because that implies that the downtime you mention is an unavoidable side-effect.
It would be OK to explain that this introduction page does not by itself explain all the details you need to know to minimise downtime and availability risk during rollouts.

I contend that you can set up a web workload to deploy (planned) changes with zero downtime, using Kubernetes.

To reiterate, I know it can be done. As stated above, I have done it. My issue is not that it is not possible to achieve using probes and a preStop hook, my issue is that this is totally missing from the documentation.

As a technical lead for SIG Docs, I would 100% welcome a PR to add a tutorial about how to do that (it's somewhat involved).

I do not think that is the proper way to address this. The proper way to address this is to modify Kubernetes to remove the pod from the service before any other termination action is executed. But there has been no activity on my issue for 9 months.

It would be OK to explain that this introduction page does not by itself explain all the details you need to know to minimise downtime and availability risk during rollouts.

I can update the docs to say that "it may cause an outage". That, I agree, reflects reality.

Closing this based on the comments.
/close


Where customize timeout_ms parameter in envoy?

I'm trying to customize timeout_ms this way:
--- apiVersion: ambassador/v0 kind:  Mapping name: service_mapping prefix: /path/ service: service:80 tls: false envoy_override:   timeout_ms: 30000
and not working.

If you're filing a bug report, please complete the full bug report template.
Otherwise, if you need help, please join our Slack at https://d6e.co/slack.
In regards to your specific issue, timeout_ms is a native Ambassador annotation; there's no need to use envoy_override. See the documentation: https://www.getambassador.io/reference/mappings#configuring-mappings.


SIL: Add parser support for has_symbol instructions

Implements the SIL parsing that was left as a FIXME in #62147.

@swift-ci please smoke test and merge