docs: update contributor docs

Adds steps to set up a local dev environment
Fixes dead links/references

Should some of these changes be made to the Copa install docs as well?

Should some of these changes be made to the Copa install docs as well?

I think its okay to leave it in one place! But could we also update https://project-copacetic.github.io/copacetic/website/contributing? it looks like the two weren't in sync with each other

Sorry about that! I tried to get the PR done right before work. Everything should be good to go now.

LGTM, waiting on DCO fix


ddev auth ssh: the input device is not a TTY

Describe the bug

The command "ddev auth ssh" throws the error "the input device is not a TTY" when executed by a remote script
To Reproduce

Create a file auth.sh in DDEV_APPROOT  with the following content:
#!/usr/bin/env bash
ddev auth ssh

Add a pre-start hook
exec-host: "curl -fsSL file:///$DDEV_APPROOT/auth.sh | bash"

Start the project with ddev start and you will get an error like
=== Running task: Exec command 'curl -fsSL file:///$DDEV_APPROOT/auth.sh | bash' on the host (silicon), output below
the input device is not a TTY
Docker command 'docker [run -it --rm --volumes-from=ddev-ssh-agent --user=501 --entrypoint= --mount=type=bind,src=/Users/foo/.ssh,dst=/tmp/sshtmp drud/ddev-ssh-agent:v1.17.0-built bash -c cp -r /tmp/sshtmp ~/.ssh && chmod -R go-rwx ~/.ssh && cd ~/.ssh && ssh-add $(file * | awk -F: "/private key/ { print \$1 }")]' failed: exit status 1

Expected behavior

Of course no error
Version and configuration information:

Host computer OS and Version: macOS Big Sur
Docker Desktop version: 3.5.2
ddev version: v1.18.0-alpha2

Additional context
If I understand it right it is more or less a docker bug. The workaround seems to be to either use COMPOSE_INTERACTIVE_NO_CLI=1 or docker-compose exec -T .... I tried export COMPOSE_INTERACTIVE_NO_CLI=1 with no success
https://github.com/docker/compose/issues/5696

ssh-add which is what's underneath here insists that you type the password on a terminal. You can't script it.
But you might be able to just exec-host: ddev auth ssh

OK, I see the point. For typing a password, which is not always necessary, you would need a tty. So the only chance is to put it directly in the hook of the config.yaml?

I think I will give process substitution a try
bash <( curl -s ... )

Doesn't look nice but it works. Thank you for your input, you can close this issue.

I'm glad you got it to work. I didn't actually end up understanding what you were trying to do or how you solved it.


Add-Code-Coverage-Report

TL/DR
This PR updates the test script, allowing a coverage report to be generated upon running
npm run test
Overview of Change
package.json

add coverage flag & turned off watchAll to our test script
add jest configuration to ignore reportWebVitals.js when running tests

this will be a good setup for coveralls or another code coverage "badging" system for PRs


Allow finish game in example mines

Allow finish game in example mines.
Added:

detection of victory.
showing mines, at the end of game.
generation of board after first player click, for not losing on first step.

Not implemented: reveal nearby unmarket cells by middle mouse click and count scores.
There is known bug: do not shows mines when game is defeated. But almost the same implementation for victory case works.

Closed in favor of the larger PR doing the same thing


Add Ability to display an entry's notes

It would be quite useful to display the notes field from an entry. It could be a flag on -plaintext or a setting for the database's profile. But beyond username and password , the notes field is absolutely critical (at least for me).
Also, this module is MUCH appreciated. Thanks!

Hi @erichiller, thank you for the feedback and praise it is well received.
The functionality that you mention is already part of the -AsPlainText option. It is just not part of the Default Property Set. This mean that is won't be displayed by default when outputting the entries results. You can always access the notes property by piping to the select-object function like so.
Get-KeePassEntry <options> -AsPlainText | Select-Object -Property Title,UserName,Password,FullPath,Notes

To see other properties that are exposed via the -AsPlainText option pipe the results to the Get-Member Command.
Get-KeePassEntry <options> -AsPlainText | Get-Member

In this case, it will return a list with the following properties:

Uuid
CreationTime
Expires
ExpireTime
LastAccessTime
LastModificationTime
LocationChanged
Tags
Touched
UsageCount
ParentGroup
FullPath
Title
UserName
Password
URL
Notes
IconId

If you think this should be a default property let me know and I will look into adding it.

To me it would be a default property, but I suppose that is a matter of opinion. It can also be modified by the end user I suppose to. Since there was not any search functionality or a few other things I desired, I wrote a function on top of the module to do so, and it took care of much of what I was after - your example code helped greatly. So I suppose if enough others agreed I would too.

Nice wrapper, I have something similar in my profile. I just opened issue #92 to change out we build the default sets and format output. Part of that issue will be to consider what properties should be defaults.
Thanks.


Ignore dev files in published package

These files are not used by library consumers and therefore should be ignored by the published files.
(I'm using babel from the project that consumes this library and babel attempts to use the .babelrc file, which is an option that can't be disabled - not in my setup, at least.)
Furthermore, I propose the following changes (which I'll make a separate PR for if agreed to):

It is fairly common practice in the npm ecosystem to make your main entry point adhere to ES5 code with require calls for external dependencies.
I suggest pointing the main entry point to the compiled dist file.
The reliance upon a global variable (jQuery & $) is making this project impossible/very hard to use when bundling without explicit modifications to standard loader logic.
I suggest adding jquery as a peerDependency and adding a import for it on the places the global var is referenced.
Additionally, an default export could be added to src/index.js that would be a patched version of jQuery with the filterizr plugin added to it.

@jariz I agree with your thoughts.
Could you please set as the base to this and the future PR the develop branch?
Once merged and tested I will then prepare a new version and merge to master.

Cool, base changed.

@jariz as an update, I am not aware if you got to start working on the rest of the changes you proposed, but as a matter of fact I implemented them myself, they're already on develop and coming in the next release tomorrow.

hiya @giotiskl, I haven't had the time yet myself, so thats awesome!


Question on test execution

Question
I realized today that a mutant is not properly "tested" by Stryker and I wonder about the root cause.
Long story short, the MemoryTracker.spec.ts keeps track of long strings in two arrays and Stryker mutated the first one.
During the mutation testing, the mutant survives but if I produce the mutation and run the tests manually, they fail.
Looking into the report details (see screenshot), I can see that only 15 tests are "covering" this mutation.
In particular, the describe "reference counts big strings" is ignored... which is the place where the tests should fail.
After changing the beforeAll into a beforeEach, the mutation is correctly detected but I wonder why.
Is this a bug or an expected behavior ?
Thx !

Stryker environment
    "@stryker-mutator/core": "^6.4.2",
    "@stryker-mutator/jest-runner": "^6.4.2",
    "@stryker-mutator/typescript-checker": "^6.4.2",

    "jest": "^29.5.0",

Additional context
https://github.com/progbots/engine
version : https://github.com/progbots/engine/blob/0cd9046b9051089e7d5e2f617768503861a7c334/state/MemoryTracker.spec.ts#L74

This sounds like a bug. Thanks for opening this issue and providing an open-source example of the failure that will help reproduce and fix this issue.

More than welcome if I can help, please not that the code evolved since that's why I gave you a versioned link

I noticed this behavior too.
I'd like to fix it, but I'm not familiar with the stryker-js code, so it seems difficult...
I'm looking forward to the fix 🙏


Build failure: sapling

Steps To Reproduce
Steps to reproduce the behavior:

nix -v profile upgrade sapling

Expected
sapling is downloaded from binary cache, as it always was before.
What happens instead
Build dependencies are downloaded and sapling is building locally
Build log
https://gist.github.com/develop7/81a63f79c655d4141f7b3cfe2316b056
Additional context
Fails in hydra as well: https://hydra.nixos.org/build/266337169/nixlog/2
Notify maintainers
@pbar @thoughtpolice
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
❯  nix-shell -p nix-info --run "nix-info -m"                                                                                2024-07-13 14:53
this path will be fetched (0.00 MiB download, 0.00 MiB unpacked):
  /nix/store/5nlrrxmz0qj3a685j2p4hlmqp907x9rs-nix-info
copying path '/nix/store/5nlrrxmz0qj3a685j2p4hlmqp907x9rs-nix-info' from 'https://cache.nixos.org'...
 - system: `"x86_64-linux"`
 - host os: `Linux 6.9.7-1-default, openSUSE Tumbleweed, noversion, nobuild`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.21.2`
 - channels(root): `""`
 - nixpkgs: `/nix/store/038zs5b21569pjv6v0dwhi6fd95jbzvx-source`

Add a :+1: reaction to issues you find important.

dupe of #326455


Feature/instrument chroma client query embeddings

Hi, this is just a draft PR, not quite ready yet, but figured I would ask a couple of things before proceeding now.
I wanted to first understand what I was doing in the repository, so I worked towards a basic telemetry that pushes the Chroma query embeddings as span attribute. Once this is in good shape, I would clean the code and add the proper unit test.
Here's a first look:

As you can notice, it's pretty much unreadable as it is :)

Anyway, here goes the questions:

In the issue description, it is mentioned that because this payload is too big, a span attribute might not be a good idea. Are there suggestions on how we can workaround this? The only idea I had was to do something similar to numpy does when printing an array, e.g., just store the first and last elements of the array.
It seemed like it was inevitable to glue back into an private class/method in Chroma to listen to the query embeddings, which is not ideal. What's your opinion on this, is it acceptable to wrap on segment.SegmentAPI._query?
I suppose this is just the first telemetry out of many, since ideally we'd support all vector databases. Would you be OK if I raised one PR per database, rather than one monolithic PR for all databases?

Thanks a lot!

Oh, I just read the issue again and it mentions this: https://opentelemetry.io/docs/concepts/signals/traces/#span-events
I'll take a look at that now, would still be useful to get some feedback on the other questions though.

It seems like adding events instead of attributes is not as straightforward as calling span.add_events(...), as I don't see the events rendered in the frontend.

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

@paolorechia thanks! I'll try to comment on everything here:

Yes, span events is the recommended approach. We don't support it yet in our UI cause it's like a chicken-and-egg - we need to figure out the right format and then we can add proper support. There are other observability platforms like SigNoz that just output everything so you should be able to see it there for debugging. You can also enable console debugging
The main issue here is figuring out the right systematic way to output these span events so it will be easier to understand where do they belong. This may require some research and looking at other instrumentations that use span events (here are all of them - https://github.com/open-telemetry/opentelemetry-python-contrib/tree/main/instrumentation).
I think it's ok to patch private classes. We'll just need proper tests to make sure this isn't breaking in future versions.
Yes, sure. Makes total sense to separate DBs per PR.

@nirga Thank you very much for the throughout explanation. I'm sorry, but there's an incoming wall of text for you :)
I used the ConsoleExporter to see the payload, the events are indeed there.
So from a "code" perspective, I can already provide something useful as soon I clean up the code.
The tough part left is, as you said, figuring out the best format.
I did a quick search on the link you provided for projects implementing opentelemetry and couldn't find any matches to add_event(, which is how I'm adding events to the trace payload.
If I simply search for event, I found a couple of unit tests that are checking for events:

django
celery

Reading these unit tests, it seems both packages use events for abnormal cases such as errors or exceptions that were triggered, which seems very different from what we're proposing for traceloop.
It seems like their occurrence is consequence of using this API for recording an exception, which is implemented by the function record_exception. For instance, found this call in celery.
What about Logs?
I looked briefly at OpenTelemetry Logs documentation, and also don't seem to fit well into our use case because it's meant to capture actual log events. For instance, this documentation example shows that it's useful to automatically ingest typical log events:
import logging

from opentelemetry import trace

tracer = trace.get_tracer_provider().get_tracer(__name__)

# Trace context correlation
with tracer.start_as_current_span("foo"):
    # Do something
    current_span = trace.get_current_span()
    current_span.add_event("This is a span event")
    logging.getLogger().error("This is a log message")

Also, the Log API for Python SDK is experimental on OpenTelemetry.
Conclusions So Far

Logging the entire embedding vector into a span attribute yields an unreadeable data in frontend because it's too large.
Log API does not make much sense in our use case.
Events API might make sense, but I couldn't find good examples out there. So we'll have to come up with our own conventions.

Proposal
I still agree that we should probably go with Events API. It seems the simplest way to go for is to just loop over the query embeddings list and add an event for each vector. As you might have seen in the gist above, it currently looks like this (but without the truncation):
    "events": [
        {
            "name": "[-0.07656381279230118, ...,  0.06179634854197502]",
            "timestamp": "2024-01-21T18:44:56.736717Z",
            "attributes": {}
        },
        {
            "name": "[0.040931396186351776,  ..., -0.046594858169555664]",
            "timestamp": "2024-01-21T18:44:56.736929Z",
            "attributes": {}
        }

Now I'd ask you though a few questions:

How would you expect this feature to help the user?
Do we really need to render the full vector as a string here?

Could we instead do the following?

Show only the first and last element like in this example snippet?
Serialize it into a binary format to reduce size?

Anyway, I'll start cleaning up the code from the PR and will add an unit test. Will let you know once it's ready for a real review.

An alternative format could be (to avoid converting the list to string)
    "events": [
        {
            "name": "query_embedding_0",
            "timestamp": "2024-01-21T18:44:56.736717Z",
            "attributes": {
                "0": -0.07656381279230118,
                "1": 0.06179634854197502
             }
        },
        {
            "name": "query_embedding_1",
            "timestamp": "2024-01-21T18:44:56.736929Z",
            "attributes": {
               "0": 0.040931396186351776,
               "1": -0.046594858169555664
            }
        }

Here's an gist for the second proposed format as dict

Apparently there's a limitation in the number of attributes of an event, and it's deleting the first 256 elements. So the second format doesn't seem to work.

Thanks @paolorechia this looks really good overall. And I do agree that this requires discussions so thanks so much for this :)
I have 2 questions / thoughts:

Should we also output the result from the query call as span events?
Can we add the span attribute name as a semantic attribute?

@nirga regarding question 1., sure, we can easily do it. It also not a bad idea, just thinking whether it’s better in ‘query’ or ‘segment._query’ function.
I’m not sure I understand the second question. Could you elaborate which name you would like to add and where?

For the 2nd question I meant that maybe we should add query_embeddings_ as Semantic Convention

Hi, @nirga
I'm trying to add a new attribute into the semantic-conventions-ai, but I'm having a hard time testing it locally. If I install the package in dev mode, the module is not imported correctly.
How do you handle it normally? Do you bump the version separately of semantic-conventions-ai? I already opened a PR with the new enum/attribute:
https://github.com/traceloop/openllmetry/pull/358

Regarding your first question, I've implemented the tracing for the query results as events. Let me know if you like the format:
    "events": [
        {
            "name": "db.chroma.query.result.0",
            "timestamp": "2024-01-23T21:47:09.047876Z",
            "attributes": {
                "ids": [
                    "36474",
                    "4983",
                    "19238"
                ],
                "distances": [
                    1.7072678804397583,
                    1.7307902574539185,
                    1.7318366765975952
                ],
                "metadata": [],
                "documents": [
                    "Efficient targeting of expressed and silent genes in human ESCs and iPSCs using zinc-finger nucleases. Realizing the full potential of human embryonic stem cells (hESCs) and induced pluripotent stem cells (hiPSCs) requires efficient methods for genetic modification. However, techniques to generate cell type\u2013specific lineage reporters, as well as reliable tools to disrupt, repair or overexpress genes by gene targeting, are inefficient at best and thus are not routinely used. Here we report the highly efficient targeting of three genes in human pluripotent cells using zinc-finger nuclease (ZFN)\u2013mediated genome editing. First, using ZFNs specific for the OCT4 (POU5F1) locus, we generated OCT4-eGFP reporter cells to monitor the pluripotent state of hESCs. Second, we inserted a transgene into the AAVS1 locus to generate a robust drug-inducible overexpression system in hESCs. Finally, we targeted the PITX3 gene, demonstrating that ZFNs can be used to generate reporter cells by targeting non-expressed genes in hESCs and hiPSCs.",
                    "Microstructural development of human newborn cerebral white matter assessed in vivo by diffusion tensor magnetic resonance imaging.. Alterations of the architecture of cerebral white matter in the developing human brain can affect cortical development and result in functional disabilities. A line scan diffusion-weighted magnetic resonance imaging (MRI) sequence with diffusion tensor analysis was applied to measure the apparent diffusion coefficient, to calculate relative anisotropy, and to delineate three-dimensional fiber architecture in cerebral white matter in preterm (n = 17) and full-term infants (n = 7). To assess effects of prematurity on cerebral white matter development, early gestation preterm infants (n = 10) were studied a second time at term. In the central white matter the mean apparent diffusion coefficient at 28 wk was high, 1.8 microm2/ms, and decreased toward term to 1.2 microm2/ms. In the posterior limb of the internal capsule, the mean apparent diffusion coefficients at both times were similar (1.2 versus 1.1 microm2/ms). Relative anisotropy was higher the closer birth was to term with greater absolute values in the internal capsule than in the central white matter. Preterm infants at term showed higher mean diffusion coefficients in the central white matter (1.4 +/- 0.24 versus 1.15 +/- 0.09 microm2/ms, p = 0.016) and lower relative anisotropy in both areas compared with full-term infants (white matter, 10.9 +/- 0.6 versus 22.9 +/- 3.0%, p = 0.001; internal capsule, 24.0 +/- 4.44 versus 33.1 +/- 0.6% p = 0.006). Nonmyelinated fibers in the corpus callosum were visible by diffusion tensor MRI as early as 28 wk; full-term and preterm infants at term showed marked differences in white matter fiber organization. The data indicate that quantitative assessment of water diffusion by diffusion tensor MRI provides insight into microstructural development in cerebral white matter in living infants.",
                    "The human myelin basic protein gene is included within a 179-kilobase transcription unit: expression in the immune and central nervous systems.. Two human Golli (for gene expressed in the oligodendrocyte lineage)-MBP (for myelin basic protein) cDNAs have been isolated from a human oligodendroglioma cell line. Analysis of these cDNAs has enabled us to determine the entire structure of the human Golli-MBP gene. The Golli-MBP gene, which encompasses the MBP transcription unit, is approximately 179 kb in length and consists of 10 exons, seven of which constitute the MBP gene. The human Golli-MBP gene contains two transcription start sites, each of which gives rise to a family of alternatively spliced transcripts. At least two Golli-MBP transcripts, containing the first three exons of the gene and one or more MBP exons, are produced from the first transcription start site. The second family of transcripts contains only MBP exons and produces the well-known MBPs. In humans, RNA blot analysis revealed that Golli-MBP transcripts were expressed in fetal thymus, spleen, and human B-cell and macrophage cell lines, as well as in fetal spinal cord. These findings clearly link the expression of exons encoding the autoimmunogen/encephalitogen MBP in the central nervous system to cells and tissues of the immune system through normal expression of the Golli-MBP gene. They also establish that this genetic locus, which includes the MBP gene, is conserved among species, providing further evidence that the MBP transcription unit is an integral part of the Golli transcription unit and suggest that this structural arrangement is important for the genetic function and/or regulation of these genes."
                ]
            }
        },

full trace

Thanks @paolorechia
Because poetry doesn't support nested dependencies in monorepos, we need to manually release and update the semconv. I've done that now on #358 and will merge it soon so you can rebase here.

@nirga I was able to use the new EventName from semantic conventions ai :)
Now that I'm understanding it, I'm thinking we should add more elements to the semantic-conventions-ai, specially now that we are also returning the query results.

@paolorechia nice :) what did you have in mind?

What do you think of these?
https://github.com/traceloop/openllmetry/pull/362

@nirga let me know what you think of the extra semanatic-conventions-ai. I think we're close to finishing this PR :)
Maybe this helps you to visualize, the trace of current version (without the newer proposed conventions):
https://gist.github.com/paolorechia/6688faeabc0ed04faa0ce547d5239b29
I'm also curious regarding the scope of the issue I'm tackling (https://github.com/traceloop/openllmetry/issues/250), from the description it seems like we should implement this convention on all vendors:

ChromeDB
Pinecone
Weaviate

What would you see a next step? I saw someone working on Pinecone, so maybe Weaviate (I've never worked with this one before)?

@paolorechia looking into this now. I'd say all vector DBs. No one is working on Pinecone on Python.

@nirga Got it. I guess it was pinecone js then. I will work on it next

Is there a way to get the textual response if the query call?

@nirga Do you mean maybe what is displayed currently as db.chroma.query.result.0.documents.0? e.g., the document that matched the query the best?

@nirga I've updated this PR to use the newer semantic conventions we merged yesterday, but I think it's not yet ideal. Here's an example:
            "name": "vector_db.query.result.1",
            "timestamp": "2024-01-26T06:46:10.304852Z",
            "attributes": {
                "vector_db.query.result.ids": [
                    "70490",
                    "4983",
                    "18670"
                ],
                "vector_db.query.result.distances": [
                    1.5630203485488892,
                    1.5724878311157227,
                    1.733376383781433
                ],
                "vector_db.query.result.metadata": [],
                "vector_db.query.result.documents": [
                    "Simplifying likelihood ratios. Likelihood ratios are one of the best measures of diagnostic accuracy, although they are seldom used, because interpreting them requires a calculator to convert back and forth between \u201cprobability\u201d and \u201codds\u201d of disease. This article describes a simpler method of interpreting likelihood ratios, one that avoids calculators, nomograms, and conversions to \u201codds\u201d of disease. Several examples illustrate how the clinician can use this method to refine diagnostic decisions at the bedside.",
                    "Microstructural development of human newborn cerebral white matter assessed in vivo by diffusion tensor magnetic resonance imaging.. Alterations of the architecture of cerebral white matter in the developing human brain can affect cortical development and result in functional disabilities. A line scan diffusion-weighted magnetic resonance imaging (MRI) sequence with diffusion tensor analysis was applied to measure the apparent diffusion coefficient, to calculate relative anisotropy, and to delineate three-dimensional fiber architecture in cerebral white matter in preterm (n = 17) and full-term infants (n = 7). To assess effects of prematurity on cerebral white matter development, early gestation preterm infants (n = 10) were studied a second time at term. In the central white matter the mean apparent diffusion coefficient at 28 wk was high, 1.8 microm2/ms, and decreased toward term to 1.2 microm2/ms. In the posterior limb of the internal capsule, the mean apparent diffusion coefficients at both times were similar (1.2 versus 1.1 microm2/ms). Relative anisotropy was higher the closer birth was to term with greater absolute values in the internal capsule than in the central white matter. Preterm infants at term showed higher mean diffusion coefficients in the central white matter (1.4 +/- 0.24 versus 1.15 +/- 0.09 microm2/ms, p = 0.016) and lower relative anisotropy in both areas compared with full-term infants (white matter, 10.9 +/- 0.6 versus 22.9 +/- 3.0%, p = 0.001; internal capsule, 24.0 +/- 4.44 versus 33.1 +/- 0.6% p = 0.006). Nonmyelinated fibers in the corpus callosum were visible by diffusion tensor MRI as early as 28 wk; full-term and preterm infants at term showed marked differences in white matter fiber organization. The data indicate that quantitative assessment of water diffusion by diffusion tensor MRI provides insight into microstructural development in cerebral white matter in living infants.",
                    "The DNA Methylome of Human Peripheral Blood Mononuclear Cells. DNA methylation plays an important role in biological processes in human health and disease. Recent technological advances allow unbiased whole-genome DNA methylation (methylome) analysis to be carried out on human cells. Using whole-genome bisulfite sequencing at 24.7-fold coverage (12.3-fold per strand), we report a comprehensive (92.62%) methylome and analysis of the unique sequences in human peripheral blood mononuclear cells (PBMC) from the same Asian individual whose genome was deciphered in the YH project. PBMC constitute an important source for clinical blood tests world-wide. We found that 68.4% of CpG sites and <0.2% of non-CpG sites were methylated, demonstrating that non-CpG cytosine methylation is minor in human PBMC. Analysis of the PBMC methylome revealed a rich epigenomic landscape for 20 distinct genomic features, including regulatory, protein-coding, non-coding, RNA-coding, and repeat sequences. Integration of our methylome data with the YH genome sequence enabled a first comprehensive assessment of allele-specific methylation (ASM) between the two haploid methylomes of any individual and allowed the identification of 599 haploid differentially methylated regions (hDMRs) covering 287 genes. Of these, 76 genes had hDMRs within 2 kb of their transcriptional start sites of which >80% displayed allele-specific expression (ASE). These data demonstrate that ASM is a recurrent phenomenon and is highly correlated with ASE in human PBMCs. Together with recently reported similar studies, our study provides a comprehensive resource for future epigenomic research and confirms new sequencing technology as a paradigm for large-scale epigenomics studies."
                ]
            }

You see, the event is named vector_db.query.result.1 and the attribute vector_db.query.result.ids. I think it would be better if the attribute would be named vector_db.query.result.1.ids.
For the time being, I went ahead and used only the new Events(Enum) directly, to implement this change:
            name=f"{Events.VECTOR_DB_QUERY_RESULT.value}.{i}",
            attributes={
                f"{Events.VECTOR_DB_QUERY_RESULT.value}.{i}.ids": tuple_[0] or [],
                f"{Events.VECTOR_DB_QUERY_RESULT.value}.{i}.distances": tuple_[1] or [],
                f"{Events.VECTOR_DB_QUERY_RESULT.value}.{i}.metadata": tuple_[2] or [],
                f"{Events.VECTOR_DB_QUERY_RESULT.value}.{i}.documents": tuple_[3] or [],

Which yields IMO a better final format. Vector embeddings:
    "events": [
        {
            "name": "vector_db.query.embeddings.0",
            "timestamp": "2024-01-26T07:01:20.163930Z",
            "attributes": {
                "vector_db.query.embeddings.0.vector": [
                    -0.0879037007689476,
                    -0.14504265785217285,
                   ...

Vector result event:
"events": [
        {
            "name": "vector_db.query.result.0",
            "timestamp": "2024-01-26T07:01:20.165695Z",
            "attributes": {
                "vector_db.query.result.0.ids": [
                    "33370",
                    "36474",
                    "7912"
                ],
                "vector_db.query.result.0.distances": [
                    1.4396635293960571,
                    1.4754178524017334,
                    1.4771554470062256
                ],
                "vector_db.query.result.0.metadata": [],
                "vector_db.query.result.0.documents": [
                    "Targeting A20 Decreases Glioma St...

Sadly, we would require yet another update to semantic-conventions-ai... I'm sorry for not seeing this before :disappointed:  :see_no_evil:
I see three options at the moment:

Deleting the EventAttributes enum entirely
Making it contain only the last name of the namespace, e.g., ids, or documents and so forth, like this:

class EventAttributes(Enum):
    # Query Embeddings
    VECTOR = "vector"

    # Query Result
    IDS = "ids"
    DISTANCES = "distances"
    METADATA = "metadata"
    DOCUMENTS = "documents"

Making the semantic conventions indexed by a {i} variable, which must be formatted when generating traces:

class EventAttributes(Enum):
    # Query Embeddings
    VECTOR_DB_QUERY_EMBEDDINGS_VECTOR = "vector_db.query.embeddings.vector"

    # Query Result
    VECTOR_DB_QUERY_RESULT_IDS = "vector_db.query.result.{i}.ids"
    VECTOR_DB_QUERY_RESULT_DISTANCES = "vector_db.query.result.{i}.distances"
    VECTOR_DB_QUERY_RESULT_METADATA = "vector_db.query.result.{i}.metadata"
    VECTOR_DB_QUERY_RESULT_DOCUMENTS = "vector_db.query.result.{i}.documents"

Again, really sorry for taking so many iterations on this PR to get it polished. I want to make sure this looks good before moving into the next Vector Databases.
What are your thoughts though?

@nirga I think this is ready for another review and maybe merge.


Support thread pools

Create a safe ThreadPool type wrapping ZSTD_threadPool. Allow binding a &ThreadPool to a CCtx, which requires that the lifetime of the &ThreadPool outlive the CCtx.
Fixes: #282

Hi, and thanks for the work! This looks perfect!


[apply-login-partner-changes] - Login with an user that does not has profile - not showing any error

Describe the bug
Trying to login as user<EMAIL_ADDRESS>- who is a Mentee user - enter user email, password, click in button Partner, or in button Mentor, app is doing nothing, it must show error that user - profile combination does not exists.
To Reproduce
Steps to reproduce the behavior:

Go to login page, enter<EMAIL_ADDRESS>/ pass123
Click on Mentor Button
Nothing happens

Expected behavior
An error message must be shown to user
Screenshots
NA

when I test it I saw error try it again just make sure that this email only have mentee profile from admin dashboard check account-data then test again, it works fine @robert-dm


Dashboard view toggle and "More Options" rename button and modal + DOM manipulation on dashboard cards

I redid of the Javascript, hopefully it helps on your end. Let me know if you're still having issues

The change is when you click on the ellipsis, then click on the rename
option, a modal pops up to modify the name and description of the goal.
On Thu, Oct 6, 2022 at 7:21 PM Brian Gormanly @.***>
wrote:

@.**** requested changes on this pull request.
Is this the same as PR #173
https://github.com/briangormanly/agora/pull/173 from yesterday? If so,
don't close them in the future unless what is being submitted is completely
new. Having the history is helpful.
When I run off main, and click on any of the items on the dashboard, there
is a pop-up
[image: Screen Shot 2022-10-06 at 7 16 33 PM]
https://user-images.githubusercontent.com/2549569/194435271-16253349-08b3-434f-b507-c9e90e660ad6.png
when i switch to your branch that does not happen. I am not sure what this
PR is supposed to change and I am not sure if the models are supposed to go
away. There are javascript errors in the console so I thought they might be
the reason or perhaps you just wanted to remove them but the name /
description of the PR is not really giving me much to go on.
Screenshots of the changes are helpful, descriptions of what I should
expect to be different so I know what to look for is also helpful.
Let me know if the modals are supposed to go away. And please pull main
into this branch.
—
Reply to this email directly, view it on GitHub
https://github.com/briangormanly/agora/pull/179#pullrequestreview-1133734700,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFR4ASBTDPGECO7Z4NKJYVDWB5NGTANCNFSM6AAAAAAQ6HSLMA
.
You are receiving this because you authored the thread.Message ID:
@.***>

The change is when you click on the ellipsis, then click on the rename option, a modal pops up to modify the name and description of the goal.
…
On Thu, Oct 6, 2022 at 7:21 PM Brian Gormanly @.> wrote: @.* requested changes on this pull request. Is this the same as PR #173 <#173> from yesterday? If so, don't close them in the future unless what is being submitted is completely new. Having the history is helpful. When I run off main, and click on any of the items on the dashboard, there is a pop-up [image: Screen Shot 2022-10-06 at 7 16 33 PM] https://user-images.githubusercontent.com/2549569/194435271-16253349-08b3-434f-b507-c9e90e660ad6.png when i switch to your branch that does not happen. I am not sure what this PR is supposed to change and I am not sure if the models are supposed to go away. There are javascript errors in the console so I thought they might be the reason or perhaps you just wanted to remove them but the name / description of the PR is not really giving me much to go on. Screenshots of the changes are helpful, descriptions of what I should expect to be different so I know what to look for is also helpful. Let me know if the modals are supposed to go away. And please pull main into this branch. — Reply to this email directly, view it on GitHub <#179 (review)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFR4ASBTDPGECO7Z4NKJYVDWB5NGTANCNFSM6AAAAAAQ6HSLMA . You are receiving this because you authored the thread.Message ID: @.***>

okay i see that now, but what about the modals that do not work? are they supposed to be removed or is that accidental?

I thought that might've been something that Kyle added but it seems to be
an appendage from the old dashboard page. If you remove it and the import
in note-gallery, it works fine.
On Thu, Oct 6, 2022 at 7:38 PM Brian Gormanly @.***>
wrote:

The change is when you click on the ellipsis, then click on the rename
option, a modal pops up to modify the name and description of the goal.
… <#m_4588978463204424096_>
On Thu, Oct 6, 2022 at 7:21 PM Brian Gormanly @.> wrote: @.**
requested changes on this pull request. Is this the same as PR #173
https://github.com/briangormanly/agora/pull/173 <#173
https://github.com/briangormanly/agora/pull/173> from yesterday? If so,
don't close them in the future unless what is being submitted is completely
new. Having the history is helpful. When I run off main, and click on any
of the items on the dashboard, there is a pop-up [image: Screen Shot
2022-10-06 at 7 16 33 PM]
https://user-images.githubusercontent.com/2549569/194435271-16253349-08b3-434f-b507-c9e90e660ad6.png
when i switch to your branch that does not happen. I am not sure what this
PR is supposed to change and I am not sure if the models are supposed to go
away. There are javascript errors in the console so I thought they might be
the reason or perhaps you just wanted to remove them but the name /
description of the PR is not really giving me much to go on. Screenshots of
the changes are helpful, descriptions of what I should expect to be
different so I know what to look for is also helpful. Let me know if the
modals are supposed to go away. And please pull main into this branch. —
Reply to this email directly, view it on GitHub <#179 (review)
https://github.com/briangormanly/agora/pull/179#pullrequestreview-1133734700>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFR4ASBTDPGECO7Z4NKJYVDWB5NGTANCNFSM6AAAAAAQ6HSLMA
. You are receiving this because you authored the thread.Message ID: @
.**>
okay i see that now, but what about the modals that do not work? are they
supposed to be removed or is that accidental?
—
Reply to this email directly, view it on GitHub
https://github.com/briangormanly/agora/pull/179#issuecomment-1270844452,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFR4ASFS64CG6YDMSJRVZTLWB5PG7ANCNFSM6AAAAAAQ6HSLMA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hey yes PR is supposed to remove the clicking modal popup. We now have the edit functionality for name and description within the more-options button(see below). The errors and console log you see in console are unrelated to this change and will be fixed in the next PR(those errors at least the ones were seeing too are in main).


[Event Change] codeunit 12 "Gen. Jnl.-Post Line"

Please change OnAfterPostGLAcc event as below :
    [IntegrationEvent(true, false)]
    local procedure OnAfterPostGLAcc(var GenJnlLine: Record "Gen. Journal Line"; var TempGLEntryBuf: Record "G/L Entry" temporary; var NextEntryNo: Integer; var NextTransactionNo: Integer; Balancing: Boolean)
    begin
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


mitmweb "Address already in use" on MacOS 10.15

Problem Description
tornado/netutil.py, line 174 throws OSError (48) "Address already in use" when starting mitmweb -- mitmproxy 4.04. from macports, Tornado 6.0.3_0 pulled as a dependency. I'm positive nothing actually listens on the port I select (or on the default one for that matter). Could this be related to ports?
Steps to reproduce the behavior:

$ mitmweb-3.7 --listen-host <IP_ADDRESS> --listen-port 65012
Traceback (most recent call last):
File "/opt/local/bin/mitmweb-3.7", line 11, in
load_entry_point('mitmproxy==4.0.4', 'console_scripts', 'mitmweb')()
File "/opt/local/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/mitmproxy/tools/_main.py", line 174, in mitmweb
run(web.master.WebMaster, cmdline.mitmweb, args)
File "/opt/local/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/mitmproxy/tools/_main.py", line 133, in run
master.run()
File "/opt/local/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/mitmproxy/tools/web/master.py", line 110, in run
http_server.listen(self.options.web_port, self.options.web_iface)
File "/opt/local/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/tornado/tcpserver.py", line 151, in listen
sockets = bind_sockets(port, address=address)
File "/opt/local/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/tornado/netutil.py", line 174, in bind_sockets
sock.bind(sockaddr)
OSError: [Errno 48] Address already in use
$ nc -l 65012
$ lsof -i -n -P | egrep LIST
Spotify    2141    33u  IPv4 0xe37c6710344ffca9      0t0  TCP *:59116 (LISTEN)
Spotify    2141    52u  IPv4 0xe37c67101dedf4a1      0t0  TCP *:57621 (LISTEN)
nc        17929     3u  IPv4 0xe37c67101c2ef831      0t0  TCP *:65012 (LISTEN)

System Information
Paste the output of "mitmproxy --version" here.
Mitmproxy: 4.0.4
Python:    3.7.6
OpenSSL:   OpenSSL 1.1.1d  10 Sep 2019
Platform:  Darwin-19.2.0-x86_64-i386-64bit

This is for a newer version installed by pip with all-dependencies (after uninstalling all relevant ports):
$ mitmweb
Traceback (most recent call last):
File "/Users//Library/Python/3.7/bin/mitmweb", line 8, in
sys.exit(mitmweb())
File "/Users//Library/Python/3.7/lib/python/site-packages/mitmproxy/tools/_main.py", line 172, in mitmweb
run(web.master.WebMaster, cmdline.mitmweb, args)
File "/Users//Library/Python/3.7/lib/python/site-packages/mitmproxy/tools/_main.py", line 131, in run
master.run()
File "/Users//Library/Python/3.7/lib/python/site-packages/mitmproxy/tools/web/master.py", line 110, in run
http_server.listen(self.options.web_port, self.options.web_iface)
File "/Users//Library/Python/3.7/lib/python/site-packages/tornado/tcpserver.py", line 151, in listen
sockets = bind_sockets(port, address=address)
File "/Users//Library/Python/3.7/lib/python/site-packages/tornado/netutil.py", line 174, in bind_sockets
sock.bind(sockaddr)
OSError: [Errno 48] Address already in use
[greg.staniak@dyngus ~]$ mitmproxy --version
Mitmproxy: 5.0.1
Python:    3.7.6
OpenSSL:   OpenSSL 1.1.0j  20 Nov 2018
Platform:  Darwin-19.2.0-x86_64-i386-64bit

OSError: [Errno 48] Address already in use

MacOS returns an error when mitmproxy tries to bind to 65012. I think this is not a mitmproxy bug, but maybe macOS now allowing you to bind to ephemeral ports.

I don't think it's an OS issue: I can start mitmproxy on port 65012 without any issue, it's mitmweb that has a problem with that, in the versions and configurations that I tried. Please re-open the ticket.

@gstaniak Hi did u solve this issue?
almost same here like this
## working well
mitmproxy

## it is not working
(Error starting proxy server: OSError(48, 'Address already in use')
mitmweb

Hi @hsskey, I didn't solve it anyway. The issue was closed as an OS-level problem, even though it didn't look like that at all. I just switched to Charles.

If mitmproxy is working but mitmweb isn't, we probably can't bind to port 8081. We don't do anything fancy at all here, so you likely have something running on 8081.

@mhils thansk for your reply but it is not real
cuz when i checked port 80 (sudo lsof -i :81)
there is no using port on my mac


Support for cloud based Redis instance

Problem
Currently, the set up instructions for the RedisStreamSource have us install a cluster local version of redis. We should be able to use other instances of Redis as well, for example a cloud provided Redis instance.
Persona:
Which persona is this feature for?
Event Producer & Consumer
Exit Criteria
A measurable (binary) test that would indicate that the problem has been resolved.
I am able to use a redis instance from a cloud provider instead of the locally installed sample/redis.
Time Estimate (optional):
How many developer-days do you think this may take to resolve?
Additional context (optional)
Add any other context about the feature request here.

/assign @aavarghese


Search 197 (Investigate Compression Performance Optimization)

Changed the compression from zip to lz4.
@VikasShashidhar @jay-k & @serkanmulayim Please review. Thanks
Note: Will be moving the library paths to a configuration file and here is the JIRA ticket

@VishwasShashidhar Can you please review the ".aip" related stuff? Thanks.

@keerthi16 Please squash your commits and have one that says what this ticket is supposed to do. Thanks.


File structure json5 for .json files

We've got some json files that we treat as json5, but they're still just en.json and the extension doesn't like that. It'll read the files just fine, but when I modify one it'll write out a file en.json5 even though it's reading en.json, it sounds like the file writer isn't following the pattern *.json and just always writes out .json5 files. Can this be changed?

When the translations are transformed back into the respective file format, information such as comments would be lost anyway.
Apart from the comment function, why should normal json files be treated as json5?

We're using the multi line string feature in json5 as some of our translations are quite long and some team members edit the files manually or use vscode.


Deprecated initialize_all_variables

Deprecated initialize_all_variables
WARNING:tensorflow:From .../env/eliana/lib/python3.6/site-packages/tensorflow/python/util/tf_should_use.py:175: initialize_all_variables (from tensorflow.python.ops.variables) is deprecated and will be removed after 2017-03-02.

Fixed by 2211740.


Placement and Mining exploit

It seems that blocks not listed as -1 in restrictedBlocks.yml can be used to clear exploit protection for blocks that are listed in restrictedBlocks.yml
Methodology:  Place a block not listed as -1 in restrictedBlocks.yml.  Wait for your configured cooldown and mine the block.   Place a block with income potential.  Wait for your configured cooldown.  The player can now mine the block for income.
**Server Type: Paperspigot
**Server Version: 1.14.4

So, basically in the default jobs config, you can:

Place a stone block
Mine the stone you just placed with a silk touch pickaxe
Place a diamond ore in the location of the stone you just mined
Mine the diamond ore you just placed with a silk touch pickaxe
Repeat 1-4

Quick and easy exploitative income.

We're getting this issue as well, it's quite a severe issue, but a temporary solution for those curious would be to make the job give negative money for placing the item. This isn't a good solution cause with digger and miner, placing stone or dirt, which is common to do, results in reduced balance, but it's necessary for the time being.
Hopefully this will be fixed soon.

This makes no sense and does not need to be improved. If you place one block, wait for the cooldown to expire, break it, put another down, so the block duration changes. Even if we try in the same place, there will be a payment delay for each block anyway. If the position of a block has changed, it is no longer considered a protected block because it does not make much sense. Thus, protection on other blocks can be canceled if the previous block has been broken and the type has also changed.


NETOBSERV-915 add conversation direction

This PR adds direction fields to conversation tracking
Also, it adds JSON fields sorting to be able to easy compare 2 items
Related PRs:

https://github.com/netobserv/network-observability-operator/pull/313
https://github.com/netobserv/flowlogs-pipeline/pull/430

/hold

/hold

/ok-to-test

Addressed feedback on json sort + include _RecordType as secondary criteria to sort start / end time columns to ensure start < tick < end order when logs have exact same time:

/ok-to-test

/ok-to-test

/label qe-approved

/approve


Fix the Enhanced Compilation Failure Issue

What type of PR is this?
/kind bug
What this PR does / why we need it:
Fix the Enhanced Compilation Failure Issue
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
#309
For enhanced kernel, without changing BpfKmesh to point type, would report an error pkg/bpf/bpf.go:58:18: cannot use NewBpfKmesh(l.config) (value of type BpfKmesh) as *BpfKmesh value in assignment at kmesh-daemon compile time.
Does this PR introduce a user-facing change?:

/ok-to-test

Ensure you have a local copy of your branch by [checking out the pull request locally via command line](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally).
In your local branch, run: git rebase HEAD~1 --signoff
Force push your changes to overwrite the branch: git push --force-with-lease origin kmesh-issues

time="2024-05-10T07:23:33Z" level=info msg="FLAG: --bpf-fs-path="/sys/fs/bpf"" subsys=manager
time="2024-05-10T07:23:33Z" level=info msg="FLAG: --cgroup2-path="/mnt/kmesh_cgroup2"" subsys=manager
time="2024-05-10T07:23:33Z" level=info msg="FLAG: --cni-etc-path="/etc/cni/net.d"" subsys=manager
time="2024-05-10T07:23:33Z" level=info msg="FLAG: --conflist-name=""" subsys=manager
time="2024-05-10T07:23:33Z" level=info msg="FLAG: --enable-mda="false"" subsys=manager
time="2024-05-10T07:23:33Z" level=info msg="FLAG: --help="false"" subsys=manager
time="2024-05-10T07:23:33Z" level=info msg="FLAG: --mode="workload"" subsys=manager
time="2024-05-10T07:23:33Z" level=info msg="FLAG: --plugin-cni-chained="true"" subsys=manager
time="2024-05-10T07:23:33Z" level=info msg="bpf Start successful" subsys=manager
time="2024-05-10T07:23:33Z" level=info msg="service node sidecar~<IP_ADDRESS>~kmesh-vpvg9.kmesh-system~kmesh-system.svc.cluster.local connect to discovery address istiod.istio-system.svc:15012" subsys=controller/config
time="2024-05-10T07:23:33Z" level=info msg="controller Start successful" subsys=manager
time="2024-05-10T07:23:33Z" level=info msg="dump StartServer successful" subsys=manager
time="2024-05-10T07:23:33Z" level=info msg="start write CNI config\n" subsys="cni installer"
time="2024-05-10T07:23:33Z" level=info msg="kmesh cni use chained\n" subsys="cni installer"
time="2024-05-10T07:23:36Z" level=info msg="Copied /usr/bin/kmesh-cni to /opt/cni/bin." subsys="cni installer"
time="2024-05-10T07:23:36Z" level=info msg="kubeconfig either does not exist or is out of date, writing a new one" subsys="cni installer"
time="2024-05-10T07:23:36Z" level=info msg="wrote kubeconfig file /etc/cni/net.d/kmesh-cni-kubeconfig" subsys="cni installer"
time="2024-05-10T07:23:36Z" level=info msg="cni config file: /etc/cni/net.d/10-kindnet.conflist" subsys="cni installer"
time="2024-05-10T07:23:36Z" level=info msg="command Start cni successful" subsys=manager

Can be compiled and launched normally

okay，I had followed with your commnds.


Add tests for Tornado adapter

This pull request adds tests for the Tornado adapter.
Category (place an x in each of the [ ])

[ ] slack_bolt.App and/or its core components
[ ] slack_bolt.async_app.AsyncApp and/or its core components
[x] Adapters in slack_bolt.adapter

Requirements (place an x in each [ ])
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.

[x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've run ./scripts/run_tests.sh after making the changes.

Codecov Report

Merging #86 into main will increase coverage by 6.03%.
The diff coverage is 94.82%.

@@            Coverage Diff             @@
##             main      #86      +/-   ##
==========================================
+ Coverage   78.56%   84.59%   +6.03%
==========================================
  Files         128      128
  Lines        3527     3558      +31
==========================================
+ Hits         2771     3010     +239
+ Misses        756      548     -208

Impacted Files
Coverage Δ

slack_bolt/adapter/aws_lambda/chalice_handler.py
0.00% <0.00%> (ø)

slack_bolt/oauth/async_oauth_flow.py
90.19% <ø> (+9.80%)
:arrow_up:

slack_bolt/oauth/oauth_flow.py
90.09% <ø> (+9.90%)
:arrow_up:

slack_bolt/context/ack/internals.py
90.00% <83.33%> (+11.81%)
:arrow_up:

slack_bolt/listener_matcher/builtins.py
89.18% <97.29%> (+1.76%)
:arrow_up:

slack_bolt/adapter/bottle/handler.py
83.33% <100.00%> (+83.33%)
:arrow_up:

slack_bolt/adapter/falcon/resource.py
84.61% <100.00%> (+84.61%)
:arrow_up:

slack_bolt/adapter/pyramid/handler.py
89.18% <100.00%> (+89.18%)
:arrow_up:

slack_bolt/request/internals.py
89.65% <100.00%> (+4.90%)
:arrow_up:

slack_bolt/version.py
100.00% <100.00%> (ø)

... and 19 more

Continue to review full report at Codecov.

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


XRayImage query regression test data type mismatch (int32 vs int64) errors on Windows

Describe the bug
Tests labeled  Blueprint_HDF5_X_Ray_Output1_xray_view  fail with this error:
   perspective:
      errors:
        - "node::diff: data type mismatch (int32 vs int64)"
      valid: "false"
valid: "false"
" .eq. "" : False

and  tests labeled Blueprint_HDF5_X_Ray_Output1_xray_query fail with:
    divide_emis_by_absorb:
      errors:
        - "node::diff: data type mismatch (int32 vs int64)"
      valid: "false"
    num_x_pixels:
      errors:
        - "node::diff: data type mismatch (int32 vs int64)"
      valid: "false"
    num_y_pixels:
      errors:
        - "node::diff: data type mismatch (int32 vs int64)"
      valid: "false"
    num_bins:
      errors:
        - "node::diff: data type mismatch (int32 vs int64)"
      valid: "false"
valid: "false"
" .eq. "" : False

Desktop

OS and version: Windows
VisIt Version: 3.4, develop

This is very strange. I am purposely casting all 5 of those values to wide int types. Must have something to do with python ints on windows, maybe they are 32 bit?
@cyrush shouldn't this turn a value into int64? This is what I'm already doing for all of those values.
val = int(node[leafname])
node.remove_child(leafname)
node[leafname] = val

On windows, ints will often be 32-bit, you have to use long to get 64-bit.
On linux and macos, ints are often 64-bit (as are longs).
If we want int64, which is reasonable -- its best o use int64 when setting.

How can I do that with Python @cyrush ? Just use long?

I think you can use numpy's int64 type numpy.int64


redux-logger definitions

https://github.com/fcomb/redux-logger

@theaqua, Can you review PR?

@theaqua Thank you!
@vvakame Probably it's ready to merge?

redux-logger/redux-logger.d.ts
check list

[ ] is collect naming convention?

https://www.npmjs.com/package/redux-logger
http://bower.io/search/?q=redux-logger
others?

[X] has a test file? (redux-logger/redux-logger-tests.ts or others)
[ ] pass the Travis-CI test?

@theaqua thanks!
@arusakov thanks mate :+1:


feat(patterns): prepare main codebase for blog

Summary
Deep refactor of React Native codebase for preparation of blog articles and education:

Improved UX
Improved Error handling
Better visual alignment with React JS app
Additional comments along with debugger statements
Reduction of abstractions and indirections for easier understanding

Code Review
It is recommended that you just download this branch onto a local computer and review the React Native code while running it. This refactor's too big to review via PR. Sorry!
Screen Recording of UX

Split Swift bridge code into two files: one file for the bridge class (FRAuthSampleBridge.swift) and the other file with the types/struct/enum definitions (FRAuthSampleTypes.swift). I also added verbose code comments to help aid the reader in understanding the logic/intent of the Swift code as well as breaking some of the very long lines to help avoid horizontal scrolling.

@george-bafaloukas-forgerock & @vahancouver: PR has been updated with improved comments and more Swifty style :) Please review and test!


[BugFix] Merge overlap segments of one rowset in lake tablet compaction

What type of PR is this：

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

In compaction, all the overlap segments should be merged to ensure that the output rowset data is in order
Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[ ] 2.5
[ ] 2.4
[ ] 2.3
[ ] 2.2

run starrocks_admit_test


we need some form of update notifications

Possibly have the application notify the user when there's a new release on the releases page

done


Encoder GFX errors

I am trying to run the encoder to compress my video stream. The v4l2_camera node outputs the video stream in RGB8 format with a resolution of 1920x1080 pixels. This is the complete log when running the encoder:
nvidia@tegra-ubuntu:~/Projects/autonomy$ ros2 launch isaac_ros_h264_encoder isaac_ros_h264_encoder.launch.py
[INFO] [launch]: All log files can be found below /home/nvidia/.ros/log/2024-05-16-13-59-46-379247-tegra-ubuntu-2933
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [component_container-1]: process started with pid [2946]
[component_container-1] [INFO] [1715867987.012505907] [encoder_container]: Load Library: /opt/ros/humble/lib/libencoder_node.so
[component_container-1] [INFO] [1715867987.055813639] [encoder_container]: Found class: rclcpp_components::NodeFactoryTemplate<nvidia::isaac_ros::h264_encoder::EncoderNode>
[component_container-1] [INFO] [1715867987.055943371] [encoder_container]: Instantiate class: rclcpp_components::NodeFactoryTemplate<nvidia::isaac_ros::h264_encoder::EncoderNode>
[component_container-1] [INFO] [1715867987.064485368] [NitrosContext]: [NitrosContext] Creating a new shared context
[component_container-1] [INFO] [1715867987.064770945] [encoder]: [NitrosNode] Initializing NitrosNode
[component_container-1] [INFO] [1715867987.065782273] [NitrosContext]: [NitrosContext] Loading extension: gxf/lib/std/libgxf_std.so
[component_container-1] [INFO] [1715867987.075685465] [NitrosContext]: [NitrosContext] Loading extension: gxf/lib/libgxf_gxf_helpers.so
[component_container-1] [INFO] [1715867987.080819034] [NitrosContext]: [NitrosContext] Loading extension: gxf/lib/libgxf_sight.so
[component_container-1] [INFO] [1715867987.087217412] [NitrosContext]: [NitrosContext] Loading extension: gxf/lib/libgxf_atlas.so
[component_container-1] [INFO] [1715867987.093736369] [NitrosContext]: [NitrosContext] Loading application: '/opt/ros/humble/share/isaac_ros_nitros/config/type_adapter_nitros_context_graph.yaml'
[component_container-1] [INFO] [1715867987.095303906] [NitrosContext]: [NitrosContext] Initializing application...
[component_container-1] [INFO] [1715867987.100450149] [NitrosContext]: [NitrosContext] Running application...
[component_container-1] 2024-05-16 13:59:47.100 WARN  gxf/std/program.cpp@514: No system specified.
[INFO] [launch_ros.actions.load_composable_nodes]: Loaded node '/encoder' in container '/encoder_container'
[component_container-1] [INFO] [1715867987.265878142] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.273569424] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.278022268] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.282964216] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.287133051] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.300516161] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.314412982] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.321416435] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.327821437] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.353363617] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.361255322] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.369017742] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.378941287] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.393599828] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.410459367] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.426806474] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.443531993] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.459325642] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.477366466] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.503145966] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.520248872] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.532304132] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.553277177] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.563497402] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.589027774] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.603186524] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.624449658] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.634597753] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.652878521] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.669885713] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.686772869] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.694535961] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.719176065] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.737544451] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.753365750] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.770023906] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.788592107] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.823769439] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.828526709] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.857608072] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.869316761] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.874262837] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.900512976] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.906230532] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.941997706] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.949193197] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.955347662] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.968773077] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.977755536] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867987.993826698] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867988.010489367] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867988.028241638] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867988.043269663] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867988.059706437] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867988.077097512] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867988.093798710] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867988.110184218] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867988.125980940] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867988.143423953] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867988.159436809] [encoder]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container-1] [INFO] [1715867988.165345827] [encoder]: [NitrosNode] Starting post negotiation setup
[component_container-1] [INFO] [1715867988.165511465] [encoder]: [NitrosNode] Getting data format negotiation results
[component_container-1] [INFO] [1715867988.165550762] [encoder]: [NitrosSubscriber] Negotiation ended with no results
[component_container-1] [INFO] [1715867988.165571947] [encoder]: [NitrosSubscriber] Use the compatible subscriber: topic_name="/image_raw", data_format="nitros_image_bgr8"
[component_container-1] [INFO] [1715867988.165676270] [encoder]: [NitrosPublisher] Negotiation ended with no results
[component_container-1] [INFO] [1715867988.165699855] [encoder]: [NitrosPublisher] Use only the compatible publisher: topic_name="/image_compressed", data_format="nitros_compressed_image"
[component_container-1] [INFO] [1715867988.168834641] [encoder]: [NitrosNode] Exporting the final graph based on the negotiation results
[component_container-1] [INFO] [1715867988.177364830] [encoder]: [NitrosNode] Wrote the final top level YAML graph to "/tmp/isaac_ros_nitros/graphs/OXBWGRJEFH/OXBWGRJEFH.yaml"
[component_container-1] [INFO] [1715867988.177526019] [encoder]: [NitrosNode] Calling user's pre-load-graph callback
[component_container-1] [INFO] [1715867988.177580997] [encoder]: [EncoderNode] preLoadGraphCallback().
[component_container-1] [INFO] [1715867988.177600741] [encoder]: [NitrosNode] Loading application
[component_container-1] [INFO] [1715867988.177653543] [encoder]: [NitrosContext] Loading application: '/tmp/isaac_ros_nitros/graphs/OXBWGRJEFH/OXBWGRJEFH.yaml'
[component_container-1] [INFO] [1715867988.181164502] [encoder]: [NitrosNode] Linking Nitros pub/sub to the loaded application
[component_container-1] [INFO] [1715867988.181431966] [encoder]: [NitrosNode] Calling user's post-load-graph callback
[component_container-1] [INFO] [1715867988.181463167] [encoder]: [EncoderNode] postLoadGraphCallback().
[component_container-1] [INFO] [1715867988.181557634] [encoder]: [NitrosContext] Initializing application...
[component_container-1] 2024-05-16 13:59:48.540 ERROR /data/jenkins/ros/workspace/ly_debian-compatible-release-2.1/isaac_ros-dev/ros_ws/src/isaac_ros_compression/isaac_ros_h264_encoder/gxf/codec/video_encoder/videoencoder_context.cpp@147: Failed to open device:v4l2_open() failed
[component_container-1] 2024-05-16 13:59:48.540 ERROR /data/jenkins/ros/workspace/ly_debian-compatible-release-2.1/isaac_ros-dev/ros_ws/src/isaac_ros_compression/isaac_ros_h264_encoder/gxf/codec/video_encoder/videoencoder_context.cpp@79: Failed to create default encoder context
[component_container-1] 2024-05-16 13:59:48.540 ERROR gxf/std/entity_warden.cpp@406: Failed to initialize component 00268 (encoder_context)
[component_container-1] 2024-05-16 13:59:48.540 ERROR gxf/core/runtime.cpp@685: Could not initialize entity 'OXBWGRJEFH_global' (E265): GXF_FAILURE
[component_container-1] 2024-05-16 13:59:48.540 ERROR gxf/std/program.cpp@236: Failed to activate entity 00265 named OXBWGRJEFH_global: GXF_FAILURE
[component_container-1] 2024-05-16 13:59:48.540 ERROR gxf/std/program.cpp@238: Deactivating...
[component_container-1] 2024-05-16 13:59:48.551 ERROR gxf/core/runtime.cpp@1384: Graph activation failed with error: GXF_FAILURE
[component_container-1] [ERROR] [1715867988.551915345] [encoder]: [NitrosContext] GxfGraphActivate Error: GXF_FAILURE
[component_container-1] [ERROR] [1715867988.552110679] [encoder]: [NitrosNode] runGraphAsync Error: GXF_FAILURE
[component_container-1] terminate called after throwing an instance of 'std::runtime_error'
[component_container-1]   what():  [NitrosNode] runGraphAsync Error: GXF_FAILURE
[ERROR] [component_container-1]: process has died [pid 2946, exit code -6, cmd '/opt/ros/humble/lib/rclcpp_components/component_container --ros-args --log-level info --ros-args -r __node:=encoder_container -r __ns:=/'].
nvidia@tegra-ubuntu:~/Projects/

Hi @mvanlobensels , I am facing the same error with all the launch file. How did you solve the issue?
Thank you in advanced.

I did not

Hello @jaiveersinghNV , do you have any clue to solve this issue?
I believe this is a bug since I can reproduce it by simply following the Quickstart in the document on multiple different machine.

Same for me.. Any news?


it IS possible to get users' email via Twitter v1.1 OAuth but we need a tweak...

If you peruse this thread: https://twittercommunity.com/t/how-to-get-email-from-twitter-user-using-oauthtokens/558/202
you will find enough information on getting user emails out of Twitter.
Here's a quick summary:

Use this form https://support.twitter.com/forms/platform and click 'I need access to special permissions'
Fill out the form with all relevant info, requesting that you would like access to user emails and click Submit.
This will generate an email from Twitter explaining their policy towards user email access.  It will reference XAuth - don't worry that means OAuth too for them.  Reply to the email as per their instructions - I DID NOT have to send them a link to a video however.
You should receive another email from Twitter within 24 hours granting you access.
Go back to your App page on Twitter, fill in Privacy Policy and User Agreement links as they request.  Save your changes.
On the 'Permissions' tab of your App page, enable asking for User email.  Save your changes.

After doing all of that, I was still not getting user email by just setting email: 'email' in Sorcery's twitter config config.twitter.user_info_mapping.
Debugging the request Sorcery was making for user info, I found that appending 'include_email=true' to the 'verify_credentials.json' endpoint did the trick.
I looked around for as clean as possible a way to add this but without modifying Sorcery configs, this was the quickest way for me to keep working.  Hope it helps out.

+1

+1

the project has moved to https://github.com/Sorcery/sorcery/


Return type of extension is not being updated based on args

Bug description
With the following db tables:
model User {
  id       String    @id() @default(uuid()) @db.Uuid()
  comments Comment[]
}

model Comment {
  id     String @id() @default(uuid()) @db.Uuid()
  text   String
  userId String @db.Uuid()
  user   User   @relation(fields: [userId], references: [id])
}

And the following extension:
const prismax = prisma.$extends({
  model: {
    $allModels: {
      myFancyFind<T, A>(
        this: T,
        args: Prisma.Args<T, "findFirst">
      ): Prisma.Result<T, "findFirst"> {
        const ctx = Prisma.getExtensionContext(this);

        return ctx.findFirst(args);
      },
    },
  },
});

I expect this to work.
type CommentWithUser = Comment & { user: User };

function fancyFindCommentWithUser(id: string): CommentWithUser {
  return this.prisma.comment.myFancyFind({
    where: { id },
    include: { user: true },
  });
}

However, it seems like the return type of myFancyFind is not correctly reflecting the args which I'm passing in (which have the include).
How to reproduce

Create prisma schema
Write extension
Call the extension with the expected return type
See error

Expected behavior
Return type of extension should be updated based on the type of the args passed in to the Prisma.Result<...> type, from the generic passed in to the extension.
Prisma information

model User {
  id       String    @id() @default(uuid()) @db.Uuid()
  comments Comment[]
}

model Comment {
  id     String @id() @default(uuid()) @db.Uuid()
  text   String
  userId String @db.Uuid()
  user   User   @relation(fields: [userId], references: [id])
}

const prismax = prisma.$extends({
  model: {
    $allModels: {
      myFancyFind<T, A>(
        this: T,
        args: Prisma.Args<T, "findFirst">
      ): Prisma.Result<T, "findFirst"> {
        const ctx = Prisma.getExtensionContext(this);

        return ctx.findFirst(args);
      },
    },
  },
});

type CommentWithUser = Comment & { user: User };

function fancyFindCommentWithUser(id: string): CommentWithUser {
  return this.prisma.comment.myFancyFind({
    where: { id },
    include: { user: true },
  });
}

Environment & setup

OS: macOS
Database: PostgreSQL
Node.js version: v18.18.2

Prisma Version
Environment variables loaded from .env
prisma                  : 4.13.0
@prisma/client          : 5.17.0
Current platform        : darwin-arm64
Query Engine (Node-API) : libquery-engine 1e7af066ee9cb95cf3a403c78d9aab3e6b04f37a (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli 1e7af066ee9cb95cf3a403c78d9aab3e6b04f37a (at ../../.npm-global/lib/node_modules/prisma/node_modules/@prisma/engines/migration-engine-darwin-arm64)
Format Wasm             : @prisma/prisma-fmt-wasm 4.13.0-50.1e7af066ee9cb95cf3a403c78d9aab3e6b04f37a
Default Engines Hash    : 1e7af066ee9cb95cf3a403c78d9aab3e6b04f37a

(Although my package.json and my package-lock.json both show that I'm running prisma version 5.17.0)

Hi @kguirguis, would something like https://github.com/prisma/prisma/issues/14595#issuecomment-1712821034 help you out in here?


Cosmos DB Readme Issues

Section link:

Suggestion:
Remove redundant words.
@sandeep-sen, @joshfree, @aayush3011 , @kyle-patterson and @KrzysztofCwalina for notification.

@faynef is individual feature team supposed to take any action on this or will the Eng team handle it generically for each feature readme?

@faynef is individual feature team supposed to take any action on this or will the Eng team handle it generically for each feature readme?

@kushagraThapar Usually, the individuals mentioned in the issues are responsible for addressing them. Since it's now assigned to you, it means that you are required to handle it.

Makes sense, can you please review this PR? https://github.com/Azure/azure-sdk-for-java/pull/39308


HEADERS

PLEASE MAKE THE USE OF HEADERS MORE CLEAR.

THANKS.

Go away...


ac-primitive-polyline

hey,
there is no primitive single (not as part of a layer) polyline option,
ive looked at it , as you suggested its just changing the drawer from polylinedrawer to primitive polyline drawer ,but couldnt test it.
ill be super glad to have an 'ac-primitive-polyline' component.
Thanks !

maybe that?
ac-polyline-primitive-desc


fix: add shivamp1998

resolves #1454
Checklist for profile addition

[x] Name the PR fix: add <your-username>.
[x] You've added file named your-username.json in the profiles directory.
[x] You've linked the PR to the correct issue.

Other additions/changes

[ ] Changes made in this PR are mentioned below
[ ] Search previous suggestions before making a new one, as yours may be a duplicate.
[ ] I acknowledge that all my contributions will be made under the project's license.
[ ] I've read the contributing guidelines

This PR adds/fixes

Notes

Is it possible to add hacktoberfest label to this?


Update README.md Fixed spelling mistake

Fix spelling on line 50 "Howvever" to "However".

File(s) Modified: 1-Two-Sum.py, 2-Add-Two-Numbers.py, etc...
Language(s) Used: python, javascript, etc...
Submission URL: _https://leetcode.com/submissions/detail/xxxxxxxxx/_

Thanks, @DaltonVislisel!


add missing comma to example options

On the website, a comma is missing on the options example. Here's the fix. :)

Thanks, appreciate it!


Support isInstanceOf(...) as implying non-null in assertion libraries.

Generally speaking, all these libraries implement the assertion by calling Class.isInstance, which
will return false whenever the argument is null. Similar to the instanceof operator:
https://docs.oracle.com/javase/1.5.0/docs/api/java/lang/Class.html#isInstance(java.lang.Object)
Given this, we can avoid some redundant assertions by adding knowledge about these calls directly
in AssertionsHandler.

Pull Request Test Coverage Report for Build #1049

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.04%) to 93.057%

Files with Coverage Reduction
New Missed Lines
%

../nullaway/src/main/java/com/uber/nullaway/handlers/MethodNameUtil.java
1
98.77%

Totals

Change from base Build #1047:
0.04%

Covered Lines:
5294

Relevant Lines:
5689

💛  - Coveralls


BUG: linalg: raise an error in dnrm2(..., incx<0)

Reference issue

closes gh-16930
What does this implement/fix?

As discussed in the issue, esp https://github.com/scipy/scipy/issues/16930#issuecomment-1993994703

All good from my side, thanks both!


Add docs about server$ middleware

Overview

What is it?

[ ] Feature / enhancement
[ ] Bug
[x] Docs / tests / types / typos

Description
Fixes: https://github.com/BuilderIO/qwik/issues/4366
It's not really clear from documentation, how you can define a middleware for server$ endpoints/functions. This adds a little bit more clarity.
Use cases and why

One use case

Another use case

Checklist:

[ ] My code follows the developer guidelines of this project
[ ] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation
[ ] Added new tests to cover the fix / functionality

Thanks for your contribution @RaeesBhatti 💪


Write manual test cases for "OregonPage"

Please write a manual test case for "https://prayersconnect.com/regions/provinces?id=45&cid=1" which involves breaking down the functionality of the webpage into specific steps that can be tested.
OregonPage: https://prayersconnect.com/mosques/search/Portland%252C%2520Oregon%252C%2520United%2520States/45.5122308%2C-122.6587185/45.5122308%2C-122.6587185
Please use this Google Sheet for your test cases.
https://docs.google.com/spreadsheets/d/1FT33mi7lZ9RcyDcln0vpu1PTX4RUNqeuBdA3uGEAOsE/edit?usp=sharing

Done.


Get UI FQDN from route instead of infrastructure

With BZ#1813012, the etcdDiscoveryDomain attribute of the cluster infrastructure is not set by the OpenShift installer. The consequence is that the cluster_dns_suffix is empty and then the redirect URL for the OAuthClient CR is incomplete.
Moreover, Kubernetes doesn't have the Infrastructure kind, which is part of the config.openshift.io/v1 API, so this configuration mechanism is not available in a Kubernetes cluster.
This pull request restores the previous mechanism. We create the UI route earlier, as it is the one we need for the redirect URL. Then, we retrieve the Route object and extract the FQDN from its spec.

Tested in live environment. Merging.

Tested in live environment. Merging.


InputEvent cannot be created from GDscript

Using Godot 3 alpha 2 on linux64 (ubuntu 16.04).
Having a script with:
var event = InputEvent()

Cause a crash with error Invalid call. Nonexistant function "InputEvent()" in base 'Node (Node.gd)'.
Same thing with any type of InputEvent like InputEventKey for instance.

InputEvents are no longer built-in types, so use InputEventKey.new()

Indeed, that's a feature(tm).


Fixing file with rules I001, Q004 cause panic

ruff 0.5.0+130 (7c8112614 2024-07-02)
ruff *.py --select I001,Q004 --no-cache --fix --unsafe-fixes --preview --output-format concise --isolated

file content(at the bottom should be attached raw, not formatted file - github removes some non-printable characters, so copying from here may not work):
import typing as t

from .filters import FILTERS as DEFAULT_FILTERS  # noqa: F401
from .tests import TESTS as DEFAULT_TESTS  # noqa: F401
from .utils import Cycler
from .utils import generate_lorem_ipsum
from .utÕls import Joiner
from Éutils import Namespace

if t.TYPE_CHECKING:
    import typing_extensions as te

# defaults for the parser / lexer
BLOCK_START_STRING = "{%"
BLOCK_END_STRING = "%}"
VARIABLE_START_STRING = "{{"
VARIABLE_END_STRING = "}}"
COMMENT_START_STRING = "{#"
COMMENT_END_STRING = "#}"
LINE_STATEMENT_PREFIX: t.Optional[str] = None
LINE_COMMENT_PREFIX: t.Optional[str] = None
TRIM_BLOCKS = False
LSTRIP_BLOCKS = False
NEWLINE_SEQUENCE: "te.Literal['\\n', '\\r\\n', '\\r']" = "\n"
KEEP_TRAILING_NEWLINE = False

# default filters, tests and namespace

DEFAULT_NAMESPACE = {
    "range": range,
    "dict": dict,
    "lipsum": generate_lorem_ipsum,
    "cycler": Cycler,
    "joiner": Joiner,
    "namespace": Namespace,
}

# default policies
DEFAULT_POLICIES: t.Dict[str, t.Any] = {
    "compiler.ascii_str": True,
    "urlize.rel": "noopener",
    "urlize.target": None,
    "urlize.extra_schemes": None,
    "truncate.leeway": 5,
    "json.dumps_function": None,
    "json.dumps_kwargs": {"sort_keys": True},
    "ext.i18n.trimmed": False,
}

error
All checks passed!

error: Panicked while linting /home/rafal/test/tmp_folder/14537502851910987982.py: This indicates a bug in Ruff. If you could open an issue at:

    https://github.com/astral-sh/ruff/issues/new?title=%5BLinter%20panic%5D

...with the relevant file contents, the `pyproject.toml` settings, and the following stack trace, we'd be very appreciative!

panicked at crates/ruff_linter/src/rules/flake8_quotes/helpers.rs:7:14:
byte index 1 is not a char boundary; it is inside 'É' (bytes 0..2) of `Éut`
Backtrace:    0: ruff::panic::catch_unwind::{{closure}}
             at /home/runner/work/Automated-Fuzzer/Automated-Fuzzer/ruff/crates/ruff/src/panic.rs:31:25
   1: <alloc::boxed::Box<F,A> as core::ops::function::Fn<Args>>::call
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/alloc/src/boxed.rs:2036:9
   2: std::panicking::rust_panic_with_hook
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/std/src/panicking.rs:799:13
   3: std::panicking::begin_panic_handler::{{closure}}
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/std/src/panicking.rs:664:13
   4: std::sys_common::backtrace::__rust_end_short_backtrace
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/std/src/sys_common/backtrace.rs:171:18
   5: rust_begin_unwind
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/std/src/panicking.rs:652:5
   6: core::panicking::panic_fmt
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/core/src/panicking.rs:72:14
   7: core::str::slice_error_fail_rt
   8: core::str::slice_error_fail
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/core/src/str/mod.rs:89:5
   9: core::str::traits::<impl core::slice::index::SliceIndex<str> for core::ops::range::Range<usize>>::index
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/core/src/str/traits.rs:244:21
  10: core::str::traits::<impl core::ops::index::Index<I> for str>::index
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/core/src/str/traits.rs:62:15
  11: ruff_linter::rules::flake8_quotes::helpers::raw_contents
             at /home/runner/work/Automated-Fuzzer/Automated-Fuzzer/ruff/crates/ruff_linter/src/rules/flake8_quotes/helpers.rs:7:14
  12: ruff_linter::rules::flake8_quotes::rules::unnecessary_escaped_quote::check_string_or_bytes
             at /home/runner/work/Automated-Fuzzer/Automated-Fuzzer/ruff/crates/ruff_linter/src/rules/flake8_quotes/rules/unnecessary_escaped_quote.rs:101:20
  13: ruff_linter::rules::flake8_quotes::rules::unnecessary_escaped_quote::unnecessary_escaped_quote
             at /home/runner/work/Automated-Fuzzer/Automated-Fuzzer/ruff/crates/ruff_linter/src/rules/flake8_quotes/rules/unnecessary_escaped_quote.rs:59:43
  14: ruff_linter::checkers::ast::analyze::string_like::string_like
             at /home/runner/work/Automated-Fuzzer/Automated-Fuzzer/ruff/crates/ruff_linter/src/checkers/ast/analyze/string_like.rs:34:9
  15: <ruff_linter::checkers::ast::Checker as ruff_python_ast::visitor::Visitor>::visit_expr
  16: ruff_python_ast::visitor::walk_expr
             at /home/runner/work/Automated-Fuzzer/Automated-Fuzzer/ruff/crates/ruff_python_ast/src/visitor.rs:543:17
  17: <ruff_linter::checkers::ast::Checker as ruff_python_ast::visitor::Visitor>::visit_expr
  18: <ruff_linter::checkers::ast::Checker as ruff_python_ast::visitor::Visitor>::visit_expr
  19: ruff_linter::checkers::ast::Checker::visit_deferred_string_type_definitions
             at /home/runner/work/Automated-Fuzzer/Automated-Fuzzer/ruff/crates/ruff_linter/src/checkers/ast/mod.rs:2203:21
  20: ruff_linter::checkers::ast::Checker::visit_deferred
             at /home/runner/work/Automated-Fuzzer/Automated-Fuzzer/ruff/crates/ruff_linter/src/checkers/ast/mod.rs:2286:13
  21: ruff_linter::checkers::ast::check_ast
             at /home/runner/work/Automated-Fuzzer/Automated-Fuzzer/ruff/crates/ruff_linter/src/checkers/ast/mod.rs:2414:5
  22: ruff_linter::linter::check_path
             at /home/runner/work/Automated-Fuzzer/Automated-Fuzzer/ruff/crates/ruff_linter/src/linter.rs:146:36
  23: ruff_linter::linter::lint_fix
             at /home/runner/work/Automated-Fuzzer/Automated-Fuzzer/ruff/crates/ruff_linter/src/linter.rs:511:27
  24: ruff::diagnostics::lint_path
             at /home/runner/work/Automated-Fuzzer/Automated-Fuzzer/ruff/crates/ruff/src/diagnostics.rs:277:14
  25: ruff::commands::check::lint_path::{{closure}}
             at /home/runner/work/Automated-Fuzzer/Automated-Fuzzer/ruff/crates/ruff/src/commands/check.rs:192:9
  26: std::panicking::try::do_call
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/std/src/panicking.rs:559:40
  27: std::panicking::try
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/std/src/panicking.rs:523:19
  28: std::panic::catch_unwind
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/std/src/panic.rs:149:14
  29: ruff::panic::catch_unwind
             at /home/runner/work/Automated-Fuzzer/Automated-Fuzzer/ruff/crates/ruff/src/panic.rs:40:18
  30: ruff::commands::check::lint_path
             at /home/runner/work/Automated-Fuzzer/Automated-Fuzzer/ruff/crates/ruff/src/commands/check.rs:191:18
  31: ruff::commands::check::check::{{closure}}
             at /home/runner/work/Automated-Fuzzer/Automated-Fuzzer/ruff/crates/ruff/src/commands/check.rs:93:17
  32: <rayon::iter::filter_map::FilterMapFolder<C,P> as rayon::iter::plumbing::Folder<T>>::consume
             at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-1.10.0/src/iter/filter_map.rs:123:36
  33: rayon::iter::plumbing::Folder::consume_iter
             at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-1.10.0/src/iter/plumbing/mod.rs:178:20
  34: rayon::iter::plumbing::Producer::fold_with
             at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-1.10.0/src/iter/plumbing/mod.rs:109:9
  35: rayon::iter::plumbing::bridge_producer_consumer::helper
             at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-1.10.0/src/iter/plumbing/mod.rs:437:13
  36: rayon::iter::plumbing::bridge_producer_consumer
             at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-1.10.0/src/iter/plumbing/mod.rs:396:12
  37: <rayon::iter::plumbing::bridge::Callback<C> as rayon::iter::plumbing::ProducerCallback<I>>::callback
             at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-1.10.0/src/iter/plumbing/mod.rs:372:13
  38: <rayon::slice::Iter<T> as rayon::iter::IndexedParallelIterator>::with_producer
             at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-1.10.0/src/slice/mod.rs:826:9
  39: rayon::iter::plumbing::bridge
             at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-1.10.0/src/iter/plumbing/mod.rs:356:12
  40: <rayon::slice::Iter<T> as rayon::iter::ParallelIterator>::drive_unindexed
             at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-1.10.0/src/slice/mod.rs:802:9
  41: <rayon::iter::filter_map::FilterMap<I,P> as rayon::iter::ParallelIterator>::drive_unindexed
             at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-1.10.0/src/iter/filter_map.rs:46:9
  42: <rayon::iter::fold::Fold<I,ID,F> as rayon::iter::ParallelIterator>::drive_unindexed
             at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-1.10.0/src/iter/fold.rs:59:9
  43: rayon::iter::reduce::reduce
             at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-1.10.0/src/iter/reduce.rs:15:5
  44: rayon::iter::ParallelIterator::reduce
             at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-1.10.0/src/iter/mod.rs:998:9
  45: ruff::commands::check::check
             at /home/runner/work/Automated-Fuzzer/Automated-Fuzzer/ruff/crates/ruff/src/commands/check.rs:163:10
  46: ruff::check
             at /home/runner/work/Automated-Fuzzer/Automated-Fuzzer/ruff/crates/ruff/src/lib.rs:413:13
  47: ruff::run
             at /home/runner/work/Automated-Fuzzer/Automated-Fuzzer/ruff/crates/ruff/src/lib.rs:186:33
  48: ruff::main
             at /home/runner/work/Automated-Fuzzer/Automated-Fuzzer/ruff/crates/ruff/src/main.rs:85:11
  49: core::ops::function::FnOnce::call_once
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/core/src/ops/function.rs:250:5
  50: std::sys_common::backtrace::__rust_begin_short_backtrace
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/std/src/sys_common/backtrace.rs:155:18
  51: std::rt::lang_start::{{closure}}
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/std/src/rt.rs:159:18
  52: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/core/src/ops/function.rs:284:13
  53: std::panicking::try::do_call
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/std/src/panicking.rs:559:40
  54: std::panicking::try
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/std/src/panicking.rs:523:19
  55: std::panic::catch_unwind
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/std/src/panic.rs:149:14
  56: std::rt::lang_start_internal::{{closure}}
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/std/src/rt.rs:141:48
  57: std::panicking::try::do_call
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/std/src/panicking.rs:559:40
  58: std::panicking::try
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/std/src/panicking.rs:523:19
  59: std::panic::catch_unwind
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/std/src/panic.rs:149:14
  60: std::rt::lang_start_internal
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/std/src/rt.rs:141:20
  61: main
  62: __libc_start_call_main
             at ./csu/../sysdeps/nptl/libc_start_call_main.h:58:16
  63: __libc_start_main_impl
             at ./csu/../csu/libc-start.c:360:3
  64: _start

Ruff build, that was used to reproduce problem(compiled on Ubuntu 22.04 with relase mode + debug symbols + debug assertions + overflow checks) - https://github.com/qarmin/Automated-Fuzzer/releases/download/Nightly/ruff.7z
python_compressed.zip

I think this might be related to https://github.com/astral-sh/ruff/issues/12165#issuecomment-2206138090

I can confirm that this is related to https://github.com/astral-sh/ruff/issues/12165#issuecomment-2208130739 because the I001 rule puts the import statement with the unicode character up to and the relative string position tries to slice within it.
Closing in favor of #10586


Angular gantt chart slow downs for large amount of data

I am using angular gantt chart from https://github.com/angular-gantt/angular-gantt and this works smoothly except when my count of orders crosses range of 500. Then it starts hanging and makes the system very slow. I have gone through the link : https://github.com/angular-gantt/angular-gantt/issues/72  but it couldn't help me.
Please help me as I do not want to change this chart and cannot keep this with this latency problem.
Thanks in Advance.

Duplicates #597, sadly I think there's no solution but implementing a read-only mode with no watchers, or rewriting using a framework that doesn't use a dirty checking loop (React, Angular 2 ...)

Do you know the cause of the problem or where is the loop so that we can make some changes in angular file's to make it faster?

It's the main issue of angular, and the main reason they rewrite from scracth for Angular 2. Just search for "angular digest performance" and "angular watchers performance" in google, and you will find many articles about the "design issue" of this framework (directy checking loop, also called digest loop).

Alright, thanks for help.

@pratibhasharma5 did you found an alternative way to work around slow down issue?

@Toilal, any tips for implementing an integration/plugin with bindone?