Can I run inference with batch of images ?

Hi
I am replicating the colab notebook to run on my dataset of 120K images. I would like to speed it up by using batch inference.
outputs = predictor(im) takes only one image at a time.
Is there a way to run inference with batch of images or any other tips which may help speed up inference ?
Thanks,
Subham

Hi,
Thank you for your interest. Our code by default does not support batch-inference. You can prepare your batched data following here and feed them to the predictor.model.

Hi @xingyizhou
I have tried running the below code depending upon your suggestion, hope this is on the right track.
results = []
with torch.no_grad():
    for i in tqdm(range(0, len(img_lst), 10)):
        img_batch = img_lst[i:i+10]
        inp_lst = []
        for j in img_batch:
            original_image = cv2.imread(j)
            original_image = original_image[:, :, ::-1]
            height, width = original_image.shape[:2]
            image = aug.get_transform(original_image).apply_image(original_image)
            image = torch.as_tensor(image.astype("float32").transpose(2, 0, 1))
            inputs = {"image": image, "height": height, "width": width}
            inp_lst.append(inputs)
        results.append(predictor.model(inp_lst))
        torch.cuda.empty_cache()

I am using T4 GPU with 16gb ram but I am unable to use more than 10 images at a time for batching. The perfomance seems to be the same as running in a loop with outputs = predictor(im)
What am I missing ?

Does Detic need the image height and width information for a forward pass? For example, is there a way to do model(batch) where batch is NxCxHxW?
Trying :
predictor.model(batch)
Gives :
*** IndexError: too many indices for tensor of dimension 3
I couldn't immediately tell if the dict {"image": image, "height": height, "width": width} was just because of Detectron2?

Now I can  inference batch  images in the backbone forward stage. But in the RPN forward stage,  it seems  the "proposal_generator" function work in

Now I can inference batch images in the backbone forward stage.  But in the RPN forward stage, it seems the "proposal_generator" function work in sequence manner.

Now I can inference batch images in the backbone forward stage. But in the RPN forward stage, it seems the "proposal_generator" function work in sequence manner.

Now I can inference batch images in the backbone forward stage. But in the RPN forward stage, it seems the "proposal_generator" function work in sequence manner.
when bsize=1,  backbone time = 0.03 , rpn_time = 0.07;  when bsize  = 8,   backbone time = 0.03 7, rpn_time = 0.85.

@SiftingSands
what was the change to L96 in order to run  model(batch)


[Feature Request]: want to add Add Solution for a problem 244 (Premium)

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
0244- Shortest Word Distance II
The problem provides us with the task of designing a data structure that must be able to compute the shortest distance between any two distinct strings within an array of strings. This implies that we first need to initialize the data structure with an array of strings, which we'll refer to as wordsDict. Once initialized, we should be able to query this data structure with two different strings, and it should return the smallest possible index difference between these two strings within the wordsDict array.
This could be visualized as an array where we want to find the minimum distance between two elements, where the elements are the positions of the words we're interested in. For example, if wordsDict is ["practice", "makes", "perfect", "coding", "makes"], and we query for the distance between "coding" and "practice", the returned value should be 3, as the closest "practice" to "coding" is three indices away.
Use Case
Let's demonstrate how the WordDistance class and its methods work using a simple example.
Suppose our wordsDict is ["the", "quick", "brown", "fox", "quick"]. We initialize the WordDistance class with this list of strings. During the initialization process, the class builds the hash map self.d which will contain:
"the" -> [0]
"quick" -> [1, 4]
"brown" -> [2]
"fox" -> [3]
Now, let's say we want to find the shortest distance between the words "brown" and "quick". We call the shortest method with these two words. Here's what happens inside this method:
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

@pallasivasai, please follow our DSA structure.
---
id: enter-id-for-routes
title: Title of Problem
sidebar_label: Number of Problem
tags: [tag1, tag2, ...., tagn]
description: Write description for SEO in few words and in only string and can't use any HTML tags in this line
sidebar_position: enter position number
---

## Problem Statement

### Problem Description

### Examples

### Constraints

## Solution of Given Problem

### Intuition and Approach

### Approaches

## Video Explanation of Given Problem

<Tabs>
  <TabItem value="en" label="English">
    <Tabs>
      <TabItem value="javascript" label="JavaScript">
        <LiteYouTubeEmbed
          id="video_id"
          params="autoplay=1&autohide=1&showinfo=0&rel=0"
          title="Problem Explanation | Solution | Approach"
          poster="maxresdefault"
          webp
        />
      </TabItem>
      <TabItem value="python" label="Python">
        <LiteYouTubeEmbed
          id="video_id"
          params="autoplay=1&autohide=1&showinfo=0&rel=0"
          title="Problem Explanation | Solution | Approach"
          poster="maxresdefault"
          webp
        />
      </TabItem>
      <TabItem value="java" label="Java">
        <LiteYouTubeEmbed
          id="video_id"
          params="autoplay=1&autohide=1&showinfo=0&rel=0"
          title="Problem Explanation | Solution | Approach"
          poster="maxresdefault"
          webp
        />
      </TabItem>
    </Tabs>
  </TabItem>

  <TabItem value="hi" label="Hindi">
    <LiteYouTubeEmbed
      id="video_id"
      params="autoplay=1&autohide=1&showinfo=0&rel=0"
      title="Problem Explanation | Solution | Approach"
      poster="maxresdefault"
      webp
    />
  </TabItem>
</Tabs>

---

Authors:

{['github_username'].map(username => (
 <Author key={username} username={username} />
))}

Detailed Guidelines

id: Unique identifier for the route.
title: Title of the problem.
sidebar_label: Problem number or label for the sidebar.
tags: Relevant tags for the problem.
description: A short SEO-friendly description. No HTML tags.


Blue screen of death

What happened?
A bug happened! Every time i click "personalize" it gives me a blue screen of death. could blue fix this

To reproduce the behavior?
reproduce!
What browser are you seeing the problem on?
Firefox

Thank you for creating an issue. We will normally respond within 24 hours.

please respond now this issue is serious

This issue is now stale because of the seriousness of the issue


Sorting the Vertices of a Polygon

Hi,
In my app the user can add vertices to a polygon and then it gets re-drawn.
The problem is that I don't know how the points will get connected and most of the times the lines overlap, instead of connecting the point clockwise.
The following article describes well my problem with some pictures and might have a solution.
http://shiffman.net/general/2011/12/23/night-4-sorting-the-vertices-of-a-polygon/
The question is: How to ensure the polygon will get correctly drawn? Does It has something to do with the sorting of the coordinates when the polygon is created?
This is my code for when the user adds a "corner" to the polygon.
this.Positions is a ObservableCollection
It starts with 4 pre-defined positions forming a square and the user can add more by tapping in the desired position and then choosing "Add Corner"
`if (action == "Add Corner")
{
    var pos = new Position(position.Latitude, position.Longitude);

    this.Positions.Add(pos);

    this.Polygons = new ObservableCollection<TKPolygon>();

    var poly = new TKPolygon
    {

            StrokeColor = Color.Yellow,
            StrokeWidth = 2f,
            Color = AreaColor,
            Coordinates = this.Positions.ToList()
    };
    this._polygons.Add(poly);

}`

I was able to implement the solution above.
Here is the basic code:
`if (action == "Add Corner")
{
                                this.Positions.Add(position);

                                var centroid = GetCentroid(this.Positions.ToList());

                                List<Position> listPositions = this.Positions.ToList();

                                listPositions = listPositions.OrderBy(o => DegreeBearing(centroid.Latitude, centroid.Longitude, o.Latitude, o.Longitude)).ToList();

                                var pin = new TKCustomMapPin
                                {
                                    Position = pos,
                                    Title = string.Format("Corner " + (this.Positions.Count).ToString()),
                                    ShowCallout = false,
                                    IsDraggable = true
                                };
                                this._pins.Add(pin);
                                await Task.Delay(500);

                                this.Polygons = new ObservableCollection<TKPolygon>();

                                var poly = new TKPolygon
                                {
                                    StrokeColor = Color.Yellow,
                                    StrokeWidth = 2f,
                                    Color = AreaColor,
                                    Coordinates = listPositions
                                };

                                this._polygons.Add(poly);

                            }`


Settings overhaul French locale

This PR provides French translations for the settings overhaul.
It will stay as a draft until translations are pinned for release.
Related to: #195

Thank you, merging this in!


Fixed Issue #42 -- [BUG] Savify crashes when attempting to download a track whose title, author or album ends with an ellipsis.

This pull request implements a fix for the issue outlined in Issue #42. This change uses regex to remove all trailing full-stops/periods from a string that is intended to be converted to a directory, via the safe_path_string(string) function in utils.py.
Due to how Savify saves metadata, the full-stops/periods remain in the metadata of the saved file.

I've added two further commits: https://github.com/LaurenceRawlings/savify/pull/43/commits/53b6a2c584705b1c7dad86f8b32d043277d636e4 and https://github.com/LaurenceRawlings/savify/pull/43/commits/7e1804585ddaac6f1d6f63c4f8b53a546334a072. These increment upon the initial changes of https://github.com/LaurenceRawlings/savify/pull/43/commits/f4ec18f262c018161c947b51ed82b7b567e21ce7 and https://github.com/LaurenceRawlings/savify/pull/43/commits/f70aa84730211e62c6b261fd6fa631ce290ed029. These new commits intend to remove a bug where non-utf8 compliant characters would cause crashes and issues with creating & saving directories.


How can I save an image shown by such as img element in html to file in my local file system?

What are you trying to achieve? (Expected behavior)

I want to save a picture in html such as: http://www.63si.com.cn:8888/lswtqt/CaptchaImg
What do you get instead? (Actual behavior)

How could the issue be reproduced? (Steps to reproduce)

        $this->validateNumberElem = $this->webDriver->findElement(WebDriverBy::id('captcha_gr'));
        $this->webDriver->wait(3);
        $url = $this->validateNumberElem->getText();
        $curl = curl_init($url);
        $filename = date("Ymdhis") . ".jpg";
        curl_setopt($curl, CURLOPT_RETURNTRANSFER, 1);
        $imageData = curl_exec($curl);
        curl_close($curl);
        $tp = @fopen($filename, 'a');
        fwrite($tp, $imageData);
        fclose($tp);

Details

Php-webdriver version: latest
PHP version: latest
Selenium server version: latest
Operating system: MacOSX latest
Browser used + version: Chrome  latest

Hi, so the issue is the content of the target URL always change? So the download file using php approach wont help you?
Is so, I would try taking screenshot of the actual rendered element. See eg. https://stackoverflow.com/questions/13832322/how-to-capture-the-screenshot-of-a-specific-element-rather-than-entire-page-usin

thanks a lot @OndraM


GH-44795: [C++] Use arrow::util::span on BooleanBuilder APIs instead of std::vector&

Rationale for this change
arrow::util::span (a backport of C++20 std::span) is more generally applicable than std::vector, so any public API currently accepting a vector const-ref argument should instead accept a span argument.
What changes are included in this PR?
BooleanBuilder accepts arrow::util::span  instead of std::vector on its API
Are these changes tested?
Via CI
Are there any user-facing changes?
Yes, from std::vector& to arrow::util::span.

GitHub Issue: #44795

This is the error I get:
code/arrow/cpp/src/arrow/array/builder_primitive.h:474:46:
        note:   no known conversion for argument 1 from ‘std::vector<bool>’ to ‘arrow::util::span<bool>’
  474 |   Status AppendValues(const util::span<bool> values);
      |                       ~~~~~~~~~~~~~~~~~~~~~~~^~~~~~

when trying to convert on this test:
  BooleanBuilder builder;
  std::vector<bool> zeros(length);
  ASSERT_OK(builder.AppendValues(zeros));

@bkietz my C++ skills aren't great but shouldn't we be able to use ‘std::vector’ for our span?

@raulcd That's because std::vector<bool> is special, so you can replace it with a span like that. Sorry!


Is there any options to only inserting the route name instead of replacing existing text?

Just trying out this plugin based on this recommendation and immediately noticed that when I type @route(' and select one of the options it replace existing text with route('route.name')') including the closing single quote and parenthesis.
https://github.com/user-attachments/assets/14829473-3302-42f3-8e09-1b95cf148f2e
Is there any option to only inserting the route.name?

Hi @feryardiant the issue is your auto close feature that I do not use.
The issue can be solve by  adding an option like close_tag_on_complete that you can turn off by setting it to false, that way the text is replaced but it wont include the closing ')

Check main.
the config:
  "ricardoramirezr/blade-nav.nvim",
  ft = { "blade", "php" },
  opts = {
    close_tag_on_complete = false,
  },
}

It will be in the next release.

Hey @RicardoRamirezR, I think not_close_tag is always false even with the option.
M.not_close_tag = not (opts.close_tag_on_complete or true)

-- M.not_close_tag = not (false or true)
-- M.not_close_tag = not (true)
-- M.not_close_tag = false

I don't know lua yet, but if you  give me some time, I may PR  a fix.

@cbaconnier nice catch. Over looked the expression, take your time


When creating a framebuffer, VKFramebufferCreateInfo.layers is not checked to be > 0

https://www.khronos.org/registry/vulkan/specs/1.0/man/html/VkFramebufferCreateInfo.html says:
layers must be greater than 0.

But if I try to create a framebuffer with validation enabled and layers = 0, no warning is issued.
Making a draw call with such a framebuffer bound crashes the driver on at least one major GPU family. I accidentally did this and had tons of "fun" debugging... Oh well :)

width and height are also not currently validated as nonzero. I can take care of all three checks later today.

Those are harder to accidentally leave out though :) But yeah, they should of course be checked too.

@hrydgard @cdwfs If resolved, could you close this issue?  Thanks


Add sorting for Chromium Usage

Fixes #929

@jcscottiii the linter raised an unparam error and had me remove a parameter from the buildFullClause function. The change is in the most recent commit if you'd like to check if it makes sense to you. 🙂


update all docs pages with committer and commit timestamp

Originally: https://github.com/influxdb/influxdb.com/issues/111
This will make it more clear what pages are going stale. In or near the footer let's print in a small font the last committer and the last commit time for that page. E.g.
"Last updated at 2015-07-08 15:32 by mjdesa"

Would be great, but this is old and not happened yet so closing.


source maps not working

The source-maps are not linking back to the original source

Are you using the latest version of jspm against Traceur 0.0.82?

fixed in 0.5.7


error and searchNoResult events not working

Please describe your problem in as much detail as possible:
Error and searchNoResult events aren't working on my bot. For example, if I play a private playlist my bot will give an error without sending any message in the channel and the bot stops. Other events work fine.
Further information:

DisTube version: 4.0.4
discord.js version: 14.7.1
Node.js version: 18.16.0
Operating system: Windows

error event only emits while the playing stream has an issue.
searchNoResult is same as searchResult and other search events, Emitted when DisTubeOptions.searchSongs bigger than 0, and song param of DisTube#play is an invalid url, and has message option

searchNoResult is not work with interaction or #search
To handle those errors, use await try catch or .catch instead since they are Promises


Should empty HTTP header values be allowed?

Should empty HTTP header values be allowed?
Trying to append an empty header value to an inlined header ends up doing nothing.
(https://github.com/envoyproxy/envoy/blob/master/source/common/http/header_map_impl.cc#L300-L302)
So a list of headers like [('inlined_key','a'), ('inlined_key',''), ('inlined_key,'b')] becomes inlined_key: a,b. (This doesn't happen for non-inlined headers.)
But I'm not sure empty headers are disallowed. Here's a StackOverflow post from 2012 which cites RFC2616 Sec2.1.
Thoughts?
Possibly related to:

Issue #2004: Envoy inline headers do not support appending values
PR #3560: headers: Fixing addCopy and addViaMove for multiple inline headers

@alyssawilk @PiotrSikora

Empty headers are being allowed, by they are being folded, and the empty one is being dropped. I'm not sure how to handle empty headers during folding. The fix is likely simple.

I have interest in reviving @ambuc's PR - this can lead to surprising behavior when using request_headers_to_add with a variable, e.g.
                    - header:
                        key: x-foobar
                        value: '%REQ(x-bizbaz)%`
                      append: false

I would expect x-foobar to be zero'd out if x-bizbaz is not present, but since we ignore empty headers x-foobar can be overridden by any incoming request if x-bizbaz is not set, e.g.
GET / HTTP/1.1
x-foobar: override

No objections, though I don't think we had any of the spec experts weigh in: @PiotrSikora @DavidSchinazi
If we do revive, we should runtime guard though.

Empty HTTP header field values are allowed as per Section 3.2 of RFC 7230.

Sweet. feel free to revive/runtime-guard/release-note and send it my way :-)

They are unfortunately allowed, and I believe that the only reason why is that the empty Accept-Encoding header has a special meaning. From RFC7231, sec. 5.3.4:
   An Accept-Encoding header field with a combined field-value that is
   empty implies that the user agent does not want any content-coding in
   response.

A possible alternative solution to my concern could be adding something like a protected boolean attribute to HeaderValueOptionsuch that if one tries to set it to an empty value, it still gets stripped but cannot be set by the downstream request either. It'd be a reduced blast radius, but a bit clunky in the API imo.
I don't know what kind of headaches empty header values can cause 😄 (but runtime-guarded as mentioned)


 Preview did not work and the window poped a "Couldn't save font." message when I tried to import the font.
Everything worked fine when I moved the font elsewhere, where it would not have a path with accented characters.

Might be related to #7309

First of all thank you for your report and sorry for the delay.
We released Godot 3.0 in January 2018 after 18 months of work, fixing many old issues either directly, or by obsoleting/replacing the features they were referring to.
We still have hundreds of issues whose relevance/reproducibility needs to be checked against the current stable version, and that's where you can help us.
Could you check if the issue that you described initially is still relevant/reproducible in Godot 3.0 or any newer version, and comment about its current status here?
For bug reports, please also make sure that the issue contains detailed steps to reproduce the bug and, if possible, a zipped project that can be used to reproduce it right away. This greatly speeds up debugging and bugfixing tasks for our contributors.
Our Bugsquad will review this issue more in-depth in 15 days, and potentially close it if its relevance could not be confirmed.
Thanks in advance.
Note: This message is being copy-pasted to many "stale" issues (90+ days without activity). It might happen that it is not meaningful for this specific issue or appears oblivious of the issue's context, if so please comment to notify the Bugsquad about it.

Hi,
Sorry for the delay.
Everything seems to work fine now, accented character or not :1st_place_medal:
This issue is not relevant anymore (tested on Godot 3.0)

Yay, closing as fixed then.


Changes lost when updating title or comment and navigating

Description
When adding a new comment for an issue, the browser navigation is blocked with a warning that changes will be lost.
This warning does not occur when editing issue titles or when editing an existing comment.
Gitea Version
1.22.3
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
Docker
Database
None

can i take this issue?

Sure - I cannot work on this. I was just reporting it.


Map titles hard to read against map background

Actual Behavior:

When I select a county and the map zooms me in to that county, the map title can be hard to read against the background, depending on the map colors behind it.
Steps to Reproduce the Bug:

go to https://cms-staging.andrew.cmu.edu/covid/?sensor=fb-survey-smoothed_hh_cmnty_cli&level=county&date=20200925&signalType=value&encoding=color&mode=overview&region=49049
look at the map title

Expected behavior
Some way to make it visible against the background. I'm not sure what would work; putting the title in another bubble/block may feel cluttered.
Also, it appears the title is forced to be 12px font, while the other navigation links on the top of the page are 16px, and the graph titles on the right are 1em/14px, so the map title is nearly the smallest text on the entire page.

Screenshots

Rating Scale (1 is minor, 7 is severe):
3

Context

Browser: Firefox 81

An easy fix might be to make the text black and increase the font size to be consistent with the other elements?  Thoughts, @sgratzl?

in v1.8 it looked like:

on mobile:


Improve warnings in charts/tables

@andypetrella
TODO: still such warnings are messed up for pivotchart !

I fixed the pivot crap...
Let's merge that!

oups - these sampling warnings disappear after kernel is shutdown, and reopened.
do not seem to disappear on notebook-page refresh if the kernel is stays alive.


Implement Pickle capacities for classifiers

Describe the solution you'd like
Provide __setstate__ and __getstate__ implementations for all classifiers in order to support serialization with pickle. To be determined if all frameworks can support this. The function can build on the pre existing save function from the Classifier API.

[x] Keras
[ ] MXNet
[ ] PyTorch
[ ] TensorFlow

I will help on Pytorch and TF versions.

PyTorch and TF pickling implemented in #68.


(22)Invalid argument: CA url for  invalid (missing uri scheme): accepted

Apache (2.4.38 on Debian) crashes on startup and writes this in error.log:
[md:error] [pid 42:tid xxx] (22)Invalid argument: CA url for <domain> invalid (missing uri scheme): accepted
[md:error] [pid 42:tid xxx] (22)Invalid argument: AH10073: synching 10 mds to registry
AH00016: Configuration Failed

There are no files under the accounts, challenges or staging folders and this is what's in my md_store.json:
{
    "store": {
        "version": 3.0
    },
    "key": "some key"
}

What could be causing this issue / How can I diagnose it further?

The „accepted“ setting is a feature of the newer 2.x versions of the module. For older version you need to specify the link. I believe the following will work:
https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf
I recommend upgrading your version, since it probably uses the old ACME service endpoints.

Am 19.06.2020 um 16:40 schrieb Mr<EMAIL_ADDRESS>
Apache (2.4.38 on Debian) crashes on startup and writes this in error.log:
[md:error] [pid 42:tid xxx] (22)Invalid argument: CA url for  invalid (missing uri scheme): accepted
[md:error] [pid 42:tid xxx] (22)Invalid argument: AH10073: synching 10 mds to registry
AH00016: Configuration Failed
There are no files under the accounts, challenges or staging folders and this is what's in my md_store.json:
{
"store": {
"version": 3.0
},
"key": "some key"
}
What could be causing this issue / How can I diagnose it further?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

That was it, thanks.


Adapt the event message regex in the OOM tracker (release-1.18)

Get rid of Kill process <PID> (<PROCESS_NAME>) score 0 or sacrifice child\n part of the OOM event message regex as it's no longer printed out in the kernel logs.
Backports #1579.
/sig scalability
/assign @jkaniuk

/lgtm
/approve


WIP/tracking: Confidential containers goes CNCF Incubation

Confidential Containers Incubation Application
v1.6
This template provides the project with a framework to inform the TOC of their conformance to the Incubation Level Criteria.
Project Repo(s): https://github.com/confidential-containers
Project Site:  https://confidentialcontainers.org/
Sub-Projects: TBD
Communication: #confidential-containers
Project points of contacts: @ariel-adam, @mythi, @magowan

[ ] (Post Incubation only) Book a meeting with CNCF staff to understand project benefits and event resources.

Incubation Criteria Summary for Confidential Containers
Application Level Assertion

[x] This project is currently Sandbox, accepted on 20220626 and applying to Incubation.
[ ] This project is applying to join the CNCF at the Incubation level.

Adoption Assertion
The project has been adopted by the following organizations in a testing and integration or production capacity:

https://github.com/confidential-containers/confidential-containers/blob/main/ADOPTERS.md

Application Process Principles
Suggested
N/A
Required

[x] Give a presentation and engage with the domain specific TAG(s) to increase awareness

This was completed and occurred on 28-Aug-2024, and can be discovered at https://zoom.us/rec/share/nCSdjZxN4DjxA7RopMqocddvDBPzxuO-Xpa2u-9xzB8MbumatD1Vtw0ePpNrobHy.Cby9t12K1IJfq_tk
https://github.com/cncf/tag-security/issues/1320

[x] TAG provides insight/recommendation of the project in the context of the landscape
- Insight provided as part of presentation to engage on 28-Aug 2024 recorded here -> https://zoom.us/rec/share/nCSdjZxN4DjxA7RopMqocddvDBPzxuO-Xpa2u-9xzB8MbumatD1Vtw0ePpNrobHy.Cby9t12K1IJfq_tk
- Further insight provided when Marina Moore presented to CoCo Project weekly meeting on 12 Sep 2024 -> https://zoom.us/rec/share/CoBjav5zAv_AOZaOSJMgSJTlvz6vrzs8rFxfuaTy6qG8Q5fwToc7l5xyiS5U_rJj.Qurwv3NKGNSjKO8i

[x] All project metadata and resources are vendor-neutral.

Confidential containers github The CoCo project is in a public github repo vendor neutral.

[x] Review and acknowledgement of expectations for Sandbox projects and requirements for moving forward through the CNCF Maturity levels.

CNCF Sandbox Onboarding completed 26-06-2022.

[ ] Due Diligence Review.

Completion of this due diligence document, resolution of concerns raised, and presented for public comment satisfies the Due Diligence Review criteria.

[x] Additional documentation as appropriate for project type, e.g.: installation documentation, end user documentation, reference implementation and/or code samples.

Quickstart guides: https://github.com/confidential-containers/confidential-containers/blob/main/quickstart.md
Confidential containers website (docs, blogs and additional information): https://confidentialcontainers.org/
Governance and Maintainers
Note: this section may be augmented by the completion of a Governance Review from TAG Contributor Strategy.
Suggested

[x] Clear and discoverable project governance documentation.

The project governance doc is maintained in the main community repository.

[x] Governance has continuously been iterated upon by the project as a result of their experience applying it, with the governance history demonstrating evolution of maturity alongside the project's maturity evolution.

See examples of iterations below.
#235
#229

[x] Governance is up to date with actual project activities, including any meetings, elections, leadership, or approval processes.

Regular updates of TSC members when companies are doing rotation

[x] Governance clearly documents vendor-neutrality of project direction.

The Confidential container project goals include specific points for enforcing vendor neutrality:

Transparent deployment of unmodified containers
Support for multiple TEE and hardware platforms

[x] Document how the project makes decisions on leadership, contribution acceptance, requests to the CNCF, and changes to governance or project goals.

See the community governance document

[x] Document how role, function-based members, or sub-teams are assigned, onboarded, and removed for specific teams (example: Security Response Committee).

See the community governance document

[x] Document a complete maintainer lifecycle process (including roles, onboarding, offboarding, and emeritus

See the community governance document

[x] Demonstrate usage of the maintainer lifecycle with outcomes, either through the addition or replacement of maintainers as project events have required.

Trustee maintainer updates
guest-components maintainer updates

[x] If the project has subprojects: subproject leadership, contribution, maturity status documented, including add/remove process.

subprojects follow the project org-level governance for contributions, maintainership etc.
the removal is not documented. bigger contributions that'd justify a sub-project creation follows the RFC process (NB: we used to have a Github issue template for it)

Required

[x] Document complete list of current maintainers, including names, contact information, domain of responsibility, and affiliation.

The community uses the github teams feature to track maintainers for the different repos: confidential containers teams

[x] A number of active maintainers which is appropriate to the size and scope of the project.

See confidential containers teams responsible for the different efforts in this project.

[x] Code and Doc ownership in Github and elsewhere matches documented governance roles.

Each repo has their CODEOWNERS pointing to the maintainers.

[x] Document agreement that project will adopt CNCF Code of Conduct.

https://github.com/confidential-containers/confidential-containers/blob/main/CODE_OF_CONDUCT.md

[x] CNCF Code of Conduct is cross-linked from other governance documents.

https://github.com/confidential-containers/confidential-containers/blob/main/CODE_OF_CONDUCT.md

[x] All subprojects, if any, are listed.

Trustee - CoCo attestation services
guest-components - CoCo TEE/client side components
cloud-api-adaptor - CoCo "peer-pods" deployment
operator - CoCo "installer"
trustee-operator - CoCo Trustee "installer"
td-shim - CoCo minimal virtual firmware

Contributors and Community
Note: this section may be augmented by the completion of a Governance Review from TAG Contributor Strategy.
Suggested

[x] Contributor ladder with multiple roles for contributors.

See community members and roles
Required

[x] Clearly defined and discoverable process to submit issues or changes.

Documented in the contribution guide.

[x] Project must have, and document, at least one public communications channel for users and/or contributors.

CNCF Slack (#confidential-containers)
Github org "front page": https://github.com/confidential-containers/

[x] List and document all project communication channels, including subprojects (mail list/slack/etc.).  List any non-public communications channels and what their special purpose is.

Github org "front page": https://github.com/confidential-containers/

[x] Up-to-date public meeting schedulers and/or integration with CNCF calendar.

Github org "front page": https://github.com/confidential-containers/ has a pointer to our community meetings calendar. The meetings do not show up on CNCF Calendar yet.

[x] Documentation of how to contribute, with increasing detail as the project matures

Documented in the contribution guide.

[x] Demonstrate contributor activity and recruitment.

CNCF Dev Stats for Confidential Containers is available: https://confidentialcontainers.devstats.cncf.io/d/8/dashboards?orgId=1&refresh=15m
Engineering Principles
Suggested

[x] Roadmap change process is documented.

All changes to the CoCo roadmap are documented in the Confidential containers SC meeting notes and have also been shared with the communicate and documented in Confidential Containers Community Meeting

[x] History of regular, quality releases.

See our documented release folder: https://github.com/confidential-containers/confidential-containers/tree/main/releases
Required

[x] Document project goals and objectives that illustrate the project’s differentiation in the Cloud Native landscape as well as outlines how this project fulfills an outstanding need and/or solves a problem differently.

See the projects goals in our website: https://confidentialcontainers.org/

[x] Document what the project does, and why it does it - including viable cloud native use cases.

See the projects WHAT/WHY/HOW statement in our website: https://confidentialcontainers.org/about/

[x] Document and maintain a public roadmap or other forward looking planning document or tracking mechanism.

https://github.com/confidential-containers/confidential-containers/blob/main/roadmap.md

[x] Document overview of project architecture and software design that demonstrates viable cloud native use cases, as part of the project's documentation.

The project website as a detailed architecture section.

[x] Document the project's release process.

The goal of the project is to release every 6 weeks (documented in https://github.com/confidential-containers/confidential-containers/blob/main/README.md)
The release process is documented here: https://github.com/confidential-containers/confidential-containers/blob/main/.github/ISSUE_TEMPLATE/release-check-list.md
Security
Note: this section may be augmented by a joint-assessment performed by TAG Security.
Suggested
N/A
Required

[x] Clearly defined and discoverable process to report security issues.

Github org-wide setting.

[x] Enforcing Access Control Rules to secure the code base against attacks (Example: two factor authentication enforcement, and/or use of ACL tools.)

All project maintainers use a two factor authentication: https://github.com/confidential-containers/confidential-containers/blob/main/MAINTAINERS

[x] Document assignment of security response roles and how reports are handled.

https://github.com/confidential-containers/.github/blob/main/SECURITY.md

[x] Document Security Self-Assessment.

Documented on Tag-Security website.

[x] Achieve the Open Source Security Foundation (OpenSSF) Best Practices passing badge.

Ecosystem
Suggested
N/A
Required

[x] Publicly documented list of adopters, which may indicate their adoption level (dev/trialing, prod, etc.)

List of project adopters: https://github.com/confidential-containers/confidential-containers/blob/main/ADOPTERS.md

[x] Used in appropriate capacity by at least 3 independent + indirect/direct adopters, (these are not required to be in the publicly documented list of adopters)

Will be provided on demand.
The project provided the TOC with a list of adopters for verification of use of the project at the level expected, i.e. production use for graduation, dev/test for incubation.

[ ] TOC verification of adopters.

Refer to the Adoption portion of this document.

[x] Clearly documented integrations and/or compatibility with other CNCF projects as well as non-CNCF projects.

See confidential containers design overview.
CoCo interacts with the following CNCF projects:

containerd
cri-o
nydus
Operator Framework

CoCo interacts with the following non-CNCF projects:

kata containers
Open Container Initiative
IETF Remote Attestation Procedures Architecture
skopeo

Additional Information

This issue served its purpose very well and getting the official application submitted was just a simple copy&paste.
CoCo application can be followed in https://github.com/cncf/toc/issues/1504
Thanks to everyone who helped to get this far!


Color picker is not standard

In most graphics software like Photoshop you will see the color picker be like the right side. When you flip the colors like this it gets confusing for me and probably for a lot of other people. Please consider changing it.
Also the color selection circle is very huge. I don't know about that...

it opens right bottom and so on mobile it won't be accessible if the button is let's say also near the bottom.
parts of the widget are inaccessible and the picker can't be moved.
to fix that I had to modify repo with the line that defaults and kinda anchors it, so that it opened elsewhere and was movable

Perhaps I am misunderstanding what you are saying, or it's the other way around, but I am talking about the colors inside the picker, not it's position. Notice how the white corner is bottom-right, but the standard is top-left.

Not sure that this is the rule. Shutter uses egui layout:

It's not a rule of course, it's just the most common way of doing it. Things that use my suggestion include: Photoshop; Krita; plugins for the aforementioned; Blender; Procreate; Artstudio pro; Rebelle; Painttool Sai; Clip Studio Paint; google search color picker; etc...

I'm for going with the majority here - should be an easy PR if anyone wants to tackle it!

Accomplished by swapping hsva's saturation and value in the color_slider_2d in my fork's hsva_color_slider_2d_orientation branch


docs; update README.md

ran -> run

I noticed in the readme the pull instructions are default git template too still oopsie
Thanks, youre the first contributor now 🫡


Replace Vertices with generic objects in netlists.

This change makes the netlists dumped by create_network_netlist contain nothing
but Rig Nets and python objects with no references to internal types. This
makes the pickling process more robust on Python 2 and avoids unnecessary
dependencies being required by the user of the netlist.
@mundya Would you be happy to sign this off?

LGTM!


virtiofsd exits as soon as viofs.sys is loaded

Hello,
i'm currently trying to setup the new virtiofs in my WS2019 virtual machine.
 Read -1 instead of 12. Original request<PHONE_NUMBER>.
2020-07-28T19:20:57.568120Z qemu-system-x86_64: Fail to update device iotlb
2020-07-28T19:20:57.568147Z qemu-system-x86_64: Failed to read msg header. Read 0 instead of 12. Original request<PHONE_NUMBER>.
2020-07-28T19:20:57.568151Z qemu-system-x86_64: Fail to update device iotlb
2020-07-28T19:20:57.568153Z qemu-system-x86_64: Failed to set msg fds.
2020-07-28T19:20:57.568156Z qemu-system-x86_64: vhost_set_vring_call failed: Invalid argument (22)
2020-07-28T19:20:57.568160Z qemu-system-x86_64: Failed to set msg fds.
2020-07-28T19:20:57.568162Z qemu-system-x86_64: vhost_set_vring_call failed: Invalid argument (22)
2020-07-28T19:20:57.568296Z qemu-system-x86_64: Failed to read from slave.

If i try to start virtiofsd afterwards with the "-d" parameter it prints:
[6470894613556] [ID: 00316440] virtio_session_mount: Waiting for vhost-user socket connection...
[6470894631129] [ID: 00316440] vhost socket accept: Bad file descriptor

Many thanks for any advice.

I narrowed down the issue. Tried it on a fresh vm without any special configuration like pci-passthrough.
The issue occurs if "iommu_platform=on" is used. With this knowledge i could reproduce this issue also in a linux-based vm.
So after all it's not a windows-driver-only issue.

@hammerg @ybendito Please take a look at why "iommu_platform=on" is causing a failure.
@Marco98 Can you please provide the info regarding the host - CPU info will be the most interesting one?
Thanks,
Yan.

CPU
AMD Ryzen 7 1700

Chipset
X370

Mainboard
AX370-Gaming 5 (FW: F50a)

Kernel
Linux 5.7.10

QEMU Version
5.0.0

OS
Arch Linux amd64

relevant kernel cmdline
amd_iommu=on iommu=pt vfio-pci.ids=10de:13c0,10de:0fbb

modprobe kvm_amd opts
options kvm_amd npt=1 nested=1 avic=1

modprobe kvm opts
options kvm ignore_msrs=1

Just let me know if you need anything else.
Many Thanks.

Thanks!
I think it is similar to https://bugzilla.redhat.com/show_bug.cgi?id=1842832

@Marco98 @YanVugenfirer where are we at with that issue?

@hammerg is an owner of the virtio-fs driver. He is on vacation now.
I suggest removing "iommu_platform=on" setting from command line for now.

Hello All,
Please help us understanding you use cases for using virtio-fs, and thus make us virtio-fs support better.
Please participate in the discussion and add your use cases: https://github.com/virtio-win/kvm-guest-drivers-windows/discussions/726
Thanks a lot,
Yan.

@Marco98 Is this bug solved for you in the latest release?

This seems like it might still be broken though it's not because of the use of the iommu_platform option. I'm not sure what is causing it but the symptom is the same, as soon as the guest connects then virtiofsd exits.
$ virtiofsd --version
virtiofsd backend 1.6.0

$ qemu-system-x86_64 --version
QEMU emulator version 8.0.50 (v8.0.0-192-ga14b8206c5)

virtiofsd exits with message:
ERROR virtiofsd] Waiting for daemon failed: HandleRequest(InvalidParam)

qemu also prints:
qemu-system-x86_64: Unexpected end-of-file before all data were read

Hi @c---
At the moment, virtiofsd doesn't use DMA API which is required to work with IOMMU.
Also, the original issue seems to be outdated.


AKPlayer class not visible when compiling for real iOS device (objective c)

After updating the iPad to iOS 12.2 I had to update to Xcode 10.2.
Then I had the issue #1734 and updated to AudioKit 4.7, that fixed issue #1734 for me.
Since then I can compile my app only for the simulator.
When I switch to a real iPad or to "Generic iOS device", the AKPlayer class is no longer visible for the compiler. I get the error "Unknown type 'AKPlayer'".

We're aware of this issue. It appears that Swift 5 breaks universal frameworks somehow.

I have a fix for this and we should have version 4.7.1 out very soon.

Thank you very much
I'm looking forward to 4.7.1.


86 listen to and execute issue events in vault client

This is just a draft!  Not for merging.
Based on branch 90-create-issue-pallet and main.
The files to focus on are in the clients dir.

Closing this in favor of #146.


[Docs] Document Macros that can be declared by user

Describe your issue
C file generated by Cython contains a lot of defined macros. Some of them are expected to be used by users to finetune compilation process - e.g. __PYX_EXTERN_C - https://github.com/cython/cython/pull/5040#discussion_r980296238
I have created a PR for mentioning this macro in documentation #5366. But we are missing separate section in Source Files and Compilation documentation providing list of macros with explanation.
There are two motivation for doing this:

to improve documentation (of course)
to explicitly define public "API" otherwise we will loose control which macro should be used and which is "internal" (and can be changed anytime)

Note: I can create a documentation, but I am not 100% sure which macros can be changed/used by users...

Most of the CYTHON_USE_* macros can be. Mostly you don't need to (they're set right already) but useful for extra compatibility
CYTHON_LIMITED_API can I think.

Probably worth emphasising, most of these really are "advanced options" - the normal use shouldn't have to worry about them (but that doesn't mean they shouldn't be documented, just that we should make it clear most users shouldn't worry)


Document ORDER BY and row ordering

Fixes  #2518.
@RaduBerinde can you have a look at the new page. Can you in particular remind me where ordering is significant so I can add the cases to the list.

This change is

@RaduBerinde  in particular what is the rule again for order-sensitive aggregations like array_agg or concat_agg?

Very nice!
Regarding array_agg and concat_agg - strictly speaking (SQL standard), I don't think they need to respect the datasource ordering. But in practice, I'm guessing people expect it. Postgres doc says "it will usually work" but notes that it's not portable; the recommended way is to use an ORDER BY clause inside the aggregate function call: SELECT array_agg(a ORDER BY b DESC) FROM table; (which we don't support AFAIK).
I believe that implementation-wise CRDB does respect the datasource ordering currently.

Review status: 0 of 4 files reviewed at latest revision, all discussions resolved, some commit checks failed.

v2.0/query-order.md, line 57 at r1 (raw file):

significant:

- the ordering of the data source in a `SELECT` clause that uses

Is this true if the ORDER BY is inside the datasource, or is this only true for the top-level ORDER BY?
I'm pretty sure that currently we do preserve the ordering in both cases, just not sure of what semantics we need to promise.

v2.0/query-order.md, line 64 at r1 (raw file):

  statement that also uses `LIMIT`, is preserved.

(FIXME: Radu, what are the other cases?)

I can't think of any other cases to mention here (other than concat_agg/array_agg/json_agg).

v2.0/query-order.md, line 182 at r1 (raw file):

in the order of a given index.

The particular advantage is that for most queries, this guarantees the

for queries using that index

Comments from Reviewable

Yes you and I know what cockroachdb currently happens to do for local execution, but I'd say with the current code we're throwing ordering out of the door as soon as a query is distributed. So I think I won't tell anything about what crdb currently happens to preserve and stick to what's guaranteed.

Review status: 0 of 4 files reviewed at latest revision, 3 unresolved discussions, some commit checks pending.

v2.0/query-order.md, line 57 at r1 (raw file):
Previously, RaduBerinde wrote…
Is this true if the ORDER BY is inside the datasource, or is this only true for the top-level ORDER BY?
I'm pretty sure that currently we do preserve the ordering in both cases, just not sure of what semantics we need to promise.

This point was bogus, I checked: DISTINCT ON respects the ORDER BY in the same SELECT.

v2.0/query-order.md, line 64 at r1 (raw file):
Previously, RaduBerinde wrote…
I can't think of any other cases to mention here (other than concat_agg/array_agg/json_agg).

There were two more: WITH ORDINALITY and scalar subqueries.

v2.0/query-order.md, line 182 at r1 (raw file):
Previously, RaduBerinde wrote…
for queries using that index

Done.

Comments from Reviewable

I added a paragraph about aggregation ordering and the known limitation.

Review status: 0 of 4 files reviewed at latest revision, 3 unresolved discussions.

Comments from Reviewable

@jseldess please take this over, including generating the missing diagram.
I might make a final pass to check the copy-edits

LGTM

Yes you and I know what cockroachdb currently happens to do for local execution, but I'd say with the current code we're throwing ordering out of the door as soon as a query is distributed.

I don't think that's the case. We've been careful to guarantee orderings required by sort nodes anywhere in the plan, and we specifically don't do local aggregation for ARRAY_AGG. E.g. check out these testcases: https://github.com/cockroachdb/cockroach/blob/master/pkg/sql/logictest/testdata/logic_test/distsql_agg#L618

We've been careful to guarantee orderings required by sort nodes anywhere in the plan, and we specifically don't do local aggregation for ARRAY_AGG.

I see. Well maybe we could drop some of them. I'm ok with being closer to the sql standard and pg if it makes some queries run fast(er).

Do you agree that we should not document the current behavior to not provide these guarantees?

Yes, definitely. We might indeed relax these in the optimizer.

Thanks very much, @knz. Hope to take this over sometime today.

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/ec0c5fc3b211a3a0ad2625f3ff211fbd16eda9df/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/c4eea2932e5f9925c03b564b32eb3c2441a3f591/

@knz, sorry for the delay. Please take a look at my edits. In the meantime, I'll generate and add the sql diagram to the query-order.md file.

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/1be0966f34abc0ac3721f5d2880929bc51214083/

 thank you!

Reviewed 5 of 5 files at r2.
Review status: all files reviewed at latest revision, 4 unresolved discussions, some commit checks failed.

_includes/sidebar-data-v2.0.json, line 660 at r2 (raw file):

              "/${VERSION}/query-order.html"
            ]
          },

nit: stray spaces

v2.0/query-order.md, line 8 at r2 (raw file):

The `ORDER BY` clause controls the order in which rows are returned or processed.
It can be used in [`SELECT` clauses](select.html) and [`DELETE`](delete.html) and [`UPDATE`](update.html) statements.

Also INSERT and UPSERT. I forgot.

Comments from Reviewable

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/3330f24eb9b5674ccf3f2c3d11c800dc4ca5f66f/

Review status: 4 of 7 files reviewed at latest revision, 4 unresolved discussions, some commit checks failed.

_includes/sidebar-data-v2.0.json, line 660 at r2 (raw file):
Previously, knz (kena) wrote…
nit: stray spaces

Done.

v2.0/query-order.md, line 8 at r2 (raw file):
Previously, knz (kena) wrote…
Also INSERT and UPSERT. I forgot.

Done.

Comments from Reviewable

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/97eb9c3b4e7126ce67232c8088520afb07389bb5/

Can't generate the sort_clause diagram until this is fixed: https://github.com/cockroachdb/docs/issues/2712

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/5ede921ea997383718a22e46d46ac92959373fb7/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/ed17e18354417945b474080fa50a1b4a5c81229d/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/e523ad12c5d171f3e4a2a4147fd689bb1f0d22d4/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/56db50a01994f3c01da496fcea1fcef27eb671c4/

Updated the full grammar page for 2.0, which exposed a bunch of broken links.

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/ea689ed6cc60a1927d12f0ca45f244f4194eae91/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/7c3e503e8b7dad509d119c6c77a7659763046a73/

@knz, I'm finally ready to merge this. But while regenerating a bunch of sql diagrams to match the full 2.0 grammar, I noticed that INSERT and UPSERT do not have any sort_clause:

INSERT
UPSERT

We call out those two statements in the Ordering Query Results page, though, so I'm a little confused. Any idea why the grammar wouldn't indicate support for ORDERY BY for those statements?

So insert and upsert accept "order by" because their operand is an entire select_stmt which itself can contain an order by clause. We'd need to massage the diagram parameters for them to reveal that properly.

Oh it's actually worse than that.
We say that "the SELECT statement and the SELECT clause are more or less the same thing" but this is very wrong actually. A SELECT statement can do several things more than a SELECT clause.
INSERT / UPSERT take an entire SELECT statement, which has more ORDER BY abilities than a SELECT clause.
Also a SELECT statement can also be any selection clause, not just SELECT clauses.
I think if we spend a little time later to discuss (#2719) we should also discuss a strategy on how to reveal all this properly.

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/47650b970126dc4e91e928c2221512c3c04019a2/

Thanks, @knz. I've recorded the open issues here: https://github.com/cockroachdb/docs/issues/2719. I'll merge this PR, since it already adds a lot of value, and schedule time for us to finish up.


Add cuda-cccl conflict with thrust/cub packages.

Checklist

[x] Ran python show_diff.py and posted the output as part of the PR. (see below)
[x] Modifications won't affect packages built in the future.

cc: @kkraus14

Output of show_diff.py:
Downloading: https://conda.anaconda.org/conda-forge/noarch/repodata_from_packages.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/noarch/repodata.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/linux-64/repodata_from_packages.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/linux-64/repodata.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/linux-armv7l/repodata_from_packages.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/linux-armv7l/repodata.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/linux-aarch64/repodata_from_packages.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/linux-aarch64/repodata.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/linux-ppc64le/repodata_from_packages.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/linux-ppc64le/repodata.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/osx-64/repodata_from_packages.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/osx-64/repodata.json.bz2
linux-64::cub-1.10.0-2.tar.bz2
-    "thrust 1.10.0.*"
+    "thrust 1.10.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-64 <0.0.0a0"
linux-64::cub-1.10.0-3.tar.bz2
-    "thrust 1.10.0.*"
+    "thrust 1.10.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-64 <0.0.0a0"
linux-64::cub-1.11.0-ha770c72_0.tar.bz2
-    "thrust 1.11.0.*"
+    "thrust 1.11.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-64 <0.0.0a0"
linux-64::cub-1.11.0-ha770c72_1.tar.bz2
-    "thrust 1.11.0.*"
+    "thrust 1.11.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-64 <0.0.0a0"
linux-64::cub-1.15.0-h0800d71_0.tar.bz2
-    "thrust 1.15.0.*"
+    "thrust 1.15.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-64 <0.0.0a0"
linux-64::cub-1.16.0-h0800d71_1.tar.bz2
-    "thrust 1.16.0.*"
+    "thrust 1.16.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-64 <0.0.0a0"
linux-64::cub-1.16.0-ha770c72_0.tar.bz2
-    "thrust 1.16.0.*"
+    "thrust 1.16.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-64 <0.0.0a0"
linux-64::cub-1.9.10-0.tar.bz2
-  "version": "1.9.10"
+  "version": "1.9.10",
+  "constrains": [
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-64 <0.0.0a0"
+  ]
linux-64::cub-1.9.10-1.tar.bz2
-  "version": "1.9.10"
+  "version": "1.9.10",
+  "constrains": [
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-64 <0.0.0a0"
+  ]
linux-64::cub-1.9.10-2.tar.bz2
-  "version": "1.9.10"
+  "version": "1.9.10",
+  "constrains": [
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-64 <0.0.0a0"
+  ]
linux-64::cub-1.9.8-0.tar.bz2
-  "version": "1.9.8"
+  "version": "1.9.8",
+  "constrains": [
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-64 <0.0.0a0"
+  ]
linux-64::cub-1.9.9-0.tar.bz2
-  "version": "1.9.9"
+  "version": "1.9.9",
+  "constrains": [
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-64 <0.0.0a0"
+  ]
linux-64::thrust-1.10.0-0.tar.bz2
-    "cub 1.10.0.*"
+    "cub 1.10.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-64 <0.0.0a0"
linux-64::thrust-1.10.0-1.tar.bz2
-    "cub 1.10.0.*"
+    "cub 1.10.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-64 <0.0.0a0"
linux-64::thrust-1.11.0-ha770c72_0.tar.bz2
-    "cub 1.11.0.*"
+    "cub 1.11.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-64 <0.0.0a0"
linux-64::thrust-1.11.0-ha770c72_1.tar.bz2
-    "cub 1.11.0.*"
+    "cub 1.11.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-64 <0.0.0a0"
linux-64::thrust-1.15.0-h0800d71_0.tar.bz2
-    "cub 1.15.0.*"
+    "cub 1.15.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-64 <0.0.0a0"
linux-64::thrust-1.16.0-h0800d71_1.tar.bz2
-    "cub 1.16.0.*"
+    "cub 1.16.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-64 <0.0.0a0"
linux-64::thrust-1.16.0-ha770c72_0.tar.bz2
-    "cub 1.16.0.*"
+    "cub 1.16.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-64 <0.0.0a0"
linux-64::thrust-1.9.10-0.tar.bz2
-  "version": "1.9.10"
+  "version": "1.9.10",
+  "constrains": [
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-64 <0.0.0a0"
+  ]
linux-64::thrust-1.9.8-0.tar.bz2
-  "version": "1.9.8"
+  "version": "1.9.8",
+  "constrains": [
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-64 <0.0.0a0"
+  ]
linux-64::thrust-1.9.9-0.tar.bz2
-  "version": "1.9.9"
+  "version": "1.9.9",
+  "constrains": [
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-64 <0.0.0a0"
+  ]
linux-aarch64::cub-1.11.0-h8af1aa0_1.tar.bz2
-    "thrust 1.11.0.*"
+    "thrust 1.11.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-aarch64 <0.0.0a0"
linux-aarch64::cub-1.15.0-h1212f3d_0.tar.bz2
-    "thrust 1.15.0.*"
+    "thrust 1.15.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-aarch64 <0.0.0a0"
linux-aarch64::cub-1.16.0-h1212f3d_1.tar.bz2
-    "thrust 1.16.0.*"
+    "thrust 1.16.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-aarch64 <0.0.0a0"
linux-aarch64::cub-1.16.0-h8af1aa0_0.tar.bz2
-    "thrust 1.16.0.*"
+    "thrust 1.16.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-aarch64 <0.0.0a0"
linux-aarch64::thrust-1.11.0-h8af1aa0_1.tar.bz2
-    "cub 1.11.0.*"
+    "cub 1.11.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-aarch64 <0.0.0a0"
linux-aarch64::thrust-1.15.0-h1212f3d_0.tar.bz2
-    "cub 1.15.0.*"
+    "cub 1.15.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-aarch64 <0.0.0a0"
linux-aarch64::thrust-1.16.0-h1212f3d_1.tar.bz2
-    "cub 1.16.0.*"
+    "cub 1.16.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-aarch64 <0.0.0a0"
linux-aarch64::thrust-1.16.0-h8af1aa0_0.tar.bz2
-    "cub 1.16.0.*"
+    "cub 1.16.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-aarch64 <0.0.0a0"
linux-ppc64le::cub-1.11.0-ha3edaa6_1.tar.bz2
-    "thrust 1.11.0.*"
+    "thrust 1.11.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-ppc64le <0.0.0a0"
linux-ppc64le::cub-1.15.0-hc9efd5c_0.tar.bz2
-    "thrust 1.15.0.*"
+    "thrust 1.15.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-ppc64le <0.0.0a0"
linux-ppc64le::cub-1.16.0-ha3edaa6_0.tar.bz2
-    "thrust 1.16.0.*"
+    "thrust 1.16.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-ppc64le <0.0.0a0"
linux-ppc64le::cub-1.16.0-hc9efd5c_1.tar.bz2
-    "thrust 1.16.0.*"
+    "thrust 1.16.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-ppc64le <0.0.0a0"
linux-ppc64le::thrust-1.11.0-ha3edaa6_1.tar.bz2
-    "cub 1.11.0.*"
+    "cub 1.11.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-ppc64le <0.0.0a0"
linux-ppc64le::thrust-1.15.0-hc9efd5c_0.tar.bz2
-    "cub 1.15.0.*"
+    "cub 1.15.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-ppc64le <0.0.0a0"
linux-ppc64le::thrust-1.16.0-ha3edaa6_0.tar.bz2
-    "cub 1.16.0.*"
+    "cub 1.16.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-ppc64le <0.0.0a0"
linux-ppc64le::thrust-1.16.0-hc9efd5c_1.tar.bz2
-    "cub 1.16.0.*"
+    "cub 1.16.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_linux-ppc64le <0.0.0a0"
osx-64::cub-1.10.0-2.tar.bz2
-    "thrust 1.10.0.*"
+    "thrust 1.10.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_osx-64 <0.0.0a0"
osx-64::cub-1.10.0-3.tar.bz2
-    "thrust 1.10.0.*"
+    "thrust 1.10.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_osx-64 <0.0.0a0"
osx-64::cub-1.11.0-h694c41f_0.tar.bz2
-    "thrust 1.11.0.*"
+    "thrust 1.11.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_osx-64 <0.0.0a0"
osx-64::cub-1.11.0-h694c41f_1.tar.bz2
-    "thrust 1.11.0.*"
+    "thrust 1.11.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_osx-64 <0.0.0a0"
osx-64::cub-1.16.0-h694c41f_0.tar.bz2
-    "thrust 1.16.0.*"
+    "thrust 1.16.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_osx-64 <0.0.0a0"
osx-64::cub-1.9.10-0.tar.bz2
-  "version": "1.9.10"
+  "version": "1.9.10",
+  "constrains": [
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_osx-64 <0.0.0a0"
+  ]
osx-64::cub-1.9.10-1.tar.bz2
-  "version": "1.9.10"
Downloading: https://conda.anaconda.org/conda-forge/osx-arm64/repodata_from_packages.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/osx-arm64/repodata.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/win-32/repodata_from_packages.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/win-32/repodata.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/win-64/repodata_from_packages.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/win-64/repodata.json.bz2
+  "version": "1.9.10",
+  "constrains": [
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_osx-64 <0.0.0a0"
+  ]
osx-64::cub-1.9.10-2.tar.bz2
-  "version": "1.9.10"
+  "version": "1.9.10",
+  "constrains": [
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_osx-64 <0.0.0a0"
+  ]
osx-64::cub-1.9.8-0.tar.bz2
-  "version": "1.9.8"
+  "version": "1.9.8",
+  "constrains": [
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_osx-64 <0.0.0a0"
+  ]
osx-64::cub-1.9.9-0.tar.bz2
-  "version": "1.9.9"
+  "version": "1.9.9",
+  "constrains": [
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_osx-64 <0.0.0a0"
+  ]
osx-64::thrust-1.10.0-0.tar.bz2
-    "cub 1.10.0.*"
+    "cub 1.10.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_osx-64 <0.0.0a0"
osx-64::thrust-1.10.0-1.tar.bz2
-    "cub 1.10.0.*"
+    "cub 1.10.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_osx-64 <0.0.0a0"
osx-64::thrust-1.11.0-h694c41f_0.tar.bz2
-    "cub 1.11.0.*"
+    "cub 1.11.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_osx-64 <0.0.0a0"
osx-64::thrust-1.11.0-h694c41f_1.tar.bz2
-    "cub 1.11.0.*"
+    "cub 1.11.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_osx-64 <0.0.0a0"
osx-64::thrust-1.15.0-h50699ec_0.tar.bz2
-    "cub 1.15.0.*"
+    "cub 1.15.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_osx-64 <0.0.0a0"
osx-64::thrust-1.16.0-h694c41f_0.tar.bz2
-    "cub 1.16.0.*"
+    "cub 1.16.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_osx-64 <0.0.0a0"
osx-64::thrust-1.16.0-hda26842_1.tar.bz2
-    "cub 1.16.0.*"
+    "cub 1.16.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_osx-64 <0.0.0a0"
osx-64::thrust-1.9.10-0.tar.bz2
-  "version": "1.9.10"
+  "version": "1.9.10",
+  "constrains": [
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_osx-64 <0.0.0a0"
+  ]
osx-64::thrust-1.9.8-0.tar.bz2
-  "version": "1.9.8"
+  "version": "1.9.8",
+  "constrains": [
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_osx-64 <0.0.0a0"
+  ]
osx-64::thrust-1.9.9-0.tar.bz2
-  "version": "1.9.9"
+  "version": "1.9.9",
+  "constrains": [
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_osx-64 <0.0.0a0"
+  ]
win-64::cub-1.10.0-2.tar.bz2
-    "thrust 1.10.0.*"
+    "thrust 1.10.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_win-64 <0.0.0a0"
win-64::cub-1.10.0-3.tar.bz2
-    "thrust 1.10.0.*"
+    "thrust 1.10.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_win-64 <0.0.0a0"
win-64::cub-1.11.0-h57928b3_0.tar.bz2
-    "thrust 1.11.0.*"
+    "thrust 1.11.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_win-64 <0.0.0a0"
win-64::cub-1.11.0-h57928b3_1.tar.bz2
-    "thrust 1.11.0.*"
+    "thrust 1.11.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_win-64 <0.0.0a0"
win-64::cub-1.15.0-h929061a_0.tar.bz2
-    "thrust 1.15.0.*"
+    "thrust 1.15.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_win-64 <0.0.0a0"
win-64::cub-1.16.0-h57928b3_0.tar.bz2
-    "thrust 1.16.0.*"
+    "thrust 1.16.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_win-64 <0.0.0a0"
win-64::cub-1.16.0-h929061a_1.tar.bz2
-    "thrust 1.16.0.*"
+    "thrust 1.16.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_win-64 <0.0.0a0"
win-64::cub-1.9.10-0.tar.bz2
-  "version": "1.9.10"
+  "version": "1.9.10",
+  "constrains": [
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_win-64 <0.0.0a0"
+  ]
win-64::cub-1.9.10-1.tar.bz2
-  "version": "1.9.10"
+  "version": "1.9.10",
+  "constrains": [
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_win-64 <0.0.0a0"
+  ]
win-64::cub-1.9.10-2.tar.bz2
-  "version": "1.9.10"
+  "version": "1.9.10",
+  "constrains": [
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_win-64 <0.0.0a0"
+  ]
win-64::cub-1.9.8-0.tar.bz2
-  "version": "1.9.8"
+  "version": "1.9.8",
+  "constrains": [
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_win-64 <0.0.0a0"
+  ]
win-64::cub-1.9.9-0.tar.bz2
-  "version": "1.9.9"
+  "version": "1.9.9",
+  "constrains": [
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_win-64 <0.0.0a0"
+  ]
win-64::thrust-1.10.0-0.tar.bz2
-    "cub 1.10.0.*"
+    "cub 1.10.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_win-64 <0.0.0a0"
win-64::thrust-1.10.0-1.tar.bz2
-    "cub 1.10.0.*"
+    "cub 1.10.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_win-64 <0.0.0a0"
win-64::thrust-1.11.0-h57928b3_0.tar.bz2
-    "cub 1.11.0.*"
+    "cub 1.11.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_win-64 <0.0.0a0"
win-64::thrust-1.11.0-h57928b3_1.tar.bz2
-    "cub 1.11.0.*"
+    "cub 1.11.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_win-64 <0.0.0a0"
win-64::thrust-1.15.0-h929061a_0.tar.bz2
-    "cub 1.15.0.*"
+    "cub 1.15.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_win-64 <0.0.0a0"
win-64::thrust-1.16.0-h57928b3_0.tar.bz2
-    "cub 1.16.0.*"
+    "cub 1.16.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_win-64 <0.0.0a0"
win-64::thrust-1.16.0-h929061a_1.tar.bz2
-    "cub 1.16.0.*"
+    "cub 1.16.0.*",
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_win-64 <0.0.0a0"
win-64::thrust-1.9.10-0.tar.bz2
-  "version": "1.9.10"
+  "version": "1.9.10",
+  "constrains": [
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_win-64 <0.0.0a0"
+  ]
win-64::thrust-1.9.8-0.tar.bz2
-  "version": "1.9.8"
+  "version": "1.9.8",
+  "constrains": [
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_win-64 <0.0.0a0"
+  ]
win-64::thrust-1.9.9-0.tar.bz2
-  "version": "1.9.9"
+  "version": "1.9.9",
+  "constrains": [
+    "cuda-cccl <0.0.0a0",
+    "cuda-cccl-impl <0.0.0a0",
+    "cuda-cccl_win-64 <0.0.0a0"
+  ]

I'm not clear why some package report the diff as constrains while others don't.
@conda-forge/core is this normal?

Thanks @kkraus14!

Thanks Keith and Bradley! 🙏
Should we also add this constraint to the thrust and cub feedstocks?
Asking as I think we would want any new packages to have these constraints as well

@kkraus14 Right now librmm on conda-forge still uses thrust, it might be an issue:
https://github.com/conda-forge/librmm-feedstock/blob/4bae48eb13c3fad6a0941047a89d2edfd2830736/recipe/meta.yaml#L31
(though, IIRC librmm also came with a bundled Thrust, so maybe for this case we just need to update the recipe and rebuild. But the point here is there might be other packages depending on thrust/cub and we should not archive them right away.)

~I'm not clear why some package report the diff as constrains while others don't.~
...
EDIT: This is because the cub / thrust packages changed how they handled their dependencies vs constrains with regards to each other at the time. This is fine.

Was also confused about this and had to dig further to understand what was going on. AIUI cub and thrust use to have run dependencies on each other. These were later softened to run_constrained in PRs ( https://github.com/conda-forge/cub-feedstock/pull/8 ) ( https://github.com/conda-forge/thrust-feedstock/pull/4 ).
Since some packages have run, the diff above shows those packages with constrains as a newly added field with this patch. As the rest have run_constrained, they show a diff with constrains adding new items (so constrains itself is not new).
Anyways hopefully this makes it clearer for anyone else stumbling upon this and looking for more context

@kkraus14 Right now librmm on conda-forge still uses thrust, it might be an issue: https://github.com/conda-forge/librmm-feedstock/blob/4bae48eb13c3fad6a0941047a89d2edfd2830736/recipe/meta.yaml#L31 (though, IIRC librmm also came with a bundled Thrust, so maybe for this case we just need to update the recipe and rebuild. But the point here is there might be other packages depending on thrust/cub and we should not archive them right away.)

Archiving the repo doesn't remove or mark the existing packages as broken as far as I'm aware. It just makes it clear that no future changes will happen to the recipe and no further packages will be produced.

For what it's worth, $ mamba repoquery whoneeds -c conda-forge thrust indicates that thrust is only used by librmm.
I think it's safe to archive the repos for thrust/cub. We can adapt the conda-forge librmm to use cuda-cccl-impl at some point, and perhaps add CUDA 12 support at the same time.

Let's go ahead and fix those feedstocks since the usual process is fix the feedstock and then add a repodata patch with link to the PR fixing the feedstock
As to archiving them, could someone please follow this process to archive feedstocks?

For what it's worth, $ mamba repoquery whoneeds -c conda-forge thrust indicates that thrust is only used by librmm. cub has no consumers besides thrust. @leofang Luckily we don't need to worry about other downstream consumers.
I think it's safe to archive the repos for thrust/cub. We can adapt the conda-forge librmm to use cuda-cccl-impl at some point, and perhaps add CUDA 12 support at the same time.

@bdice It's confusing. Could you try this search instead?
https://github.com/search?q=org%3Aconda-forge+thrust+lang%3Ayaml&type=code
I found at least one more feedstock:
https://github.com/conda-forge/polyhedral-gravity-model-feedstock/blob/0a98ab21a5e271832fc736df30d492433cd3577d/recipe/meta.yaml#L33
I

And please do the same check for cub:
https://github.com/search?q=org%3Aconda-forge+cub+lang%3Ayaml&type=code

Let's go ahead and fix those feedstocks since the usual process is fix the feedstock and then add a repodata patch with link to the PR fixing the feedstock

Well sometimes I was asked to do it differently, but anyway @bdice has kindly sent fixes:

https://github.com/conda-forge/cub-feedstock/pull/23
https://github.com/conda-forge/thrust-feedstock/pull/18

@leofang Good find. Apparently mamba repoquery wasn't complete.
I searched with these queries (thrust, cub) and found the following packages depending on thrust or cub:

deepmd-kit -- this only depends on cub for CUDA 10.2, which is being explicitly skip'd, so it may not be used
polyhedral-gravity-model -- this can probably be left alone or updated to cuda-cccl-impl
librmm, discussed above

The two additional

Yup. Or we can create a migrator for doing the work for us, once cccl is up. This would ensure the entire CF infra does not use thrust/cub anymore (now or future), not just touching the feedstocks we find.

Yeah think since thrust and cub are header only, searching for package dependencies winds up being a subset (as packages may only use them during the build)


Fixed binary download path when calling initializeIsarCore

Currently using Isar.initializeIsarCore(download: true) on Windows does not work when running tests from Git Bash/command prompt.
I tested this fix on Windows, Mac, and Linux and it seems to work correctly on all of them.

Wow that's awesome thanks so much!!

@all-contributors please add @Moseco for bug fixing


Deleting the dev branch workflow instructions

Fixes #512
In this pull request I aimed to correct any contributing docs and scripts that might reference the dead dev branch.

Because GitHub product doesn't do anything special with the RELEASING.md file, I decided that making release instructions part of the CONTRIBUTING.md file was better.
I also read through CONTRIBUTING.md and corrected anything that might not make sense anymore.

/cc @primer/ds-core

Whenever this goes through I'll happily adjust my PR 😆 Just didn't feel right using dev as base but error on the side of following instructions right?

@AustinPaquette No worries, we're making adjustments I can take what you sent and run with it. Thanks!


Fix for the case when both indent-delta and indent-width-cont are enabled

When both indent-delta and indent-width-cont options are enabled, I'd expect the following HTML to be correct, but it isn't as indent-delta doesn't take into account the existence of indent-width-cont.

     mySecondAttr="b">

hello

This PR fixes the problem. A test with this example is included.
@mlochbaum if merged, I'd really appreciate the release of a new version of htmllint (0.7.3) so that we can use the library in our project. Thanks! :)

Coverage remained the same at 100.0% when pulling 308c28c3be210cb750d20935eaf2ef5e9db251d8 on acalvo:master into fe68744c1ea87ebd92e6545fb342f7006237d20e on htmllint:master.

That seems pretty sane. Sorry to keep you waiting so long. I'll put out a new release today.


generate asset amount as string

Need a function that generates a string representation of an asset.
Something along these lines will be great to have in asset.hpp:
https://medium.com/@cc32d9/printing-asset-amount-in-eosio-assert-99122107bfdd

oops, eosiolib is not in this repo. Should I recreate it in eos repo?

We are doing some clean up and are closing old issues. Please reopen in the new token repo.


⚠ Bofrost.fr has degraded performance

In 3f4c17a, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1250 ms

Resolved: Bofrost.fr performance has improved in 59d5d05 after 10 minutes.


[3.0]Fix netty ssl file leak

What is the purpose of the change
fix #7161
Brief changelog
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #9245 (345b91a) into 3.0 (3b9d6af) will decrease coverage by 0.16%.
The diff coverage is 1.69%.

@@             Coverage Diff              @@
##                3.0    #9245      +/-   ##
============================================
- Coverage     64.76%   64.60%   -0.17%
+ Complexity      329      327       -2
============================================
  Files          1206     1206
  Lines         51802    51803       +1
  Branches       7716     7685      -31
============================================
- Hits          33551    33466      -85
- Misses        14637    14713      +76
- Partials       3614     3624      +10

Impacted Files
Coverage Δ

...ava/org/apache/dubbo/remoting/api/SslContexts.java
0.00% <0.00%> (ø)

...ache/dubbo/rpc/protocol/grpc/GrpcOptionsUtils.java
31.81% <3.57%> (-5.14%)
:arrow_down:

...ache/dubbo/remoting/transport/AbstractChannel.java
75.00% <0.00%> (-12.50%)
:arrow_down:

...dubbo/common/status/support/LoadStatusChecker.java
50.00% <0.00%> (-11.54%)
:arrow_down:

...e/dubbo/remoting/transport/netty/NettyChannel.java
52.27% <0.00%> (-7.96%)
:arrow_down:

...mmon/threadpool/support/fixed/FixedThreadPool.java
80.00% <0.00%> (-7.50%)
:arrow_down:

.../common/threadpool/serial/SerializingExecutor.java
70.37% <0.00%> (-7.41%)
:arrow_down:

...ng/transport/dispatcher/all/AllChannelHandler.java
62.06% <0.00%> (-6.90%)
:arrow_down:

.../threadpool/support/limited/LimitedThreadPool.java
83.33% <0.00%> (-5.56%)
:arrow_down:

...mmon/threadpool/support/AbortPolicyWithReport.java
78.94% <0.00%> (-5.27%)
:arrow_down:

... and 38 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 3b9d6af...345b91a. Read the comment docs.


POSIX layer is not well developed

POSIX layer is not well developed. Look at how TI has it:
http://software-dl.ti.com/simplelink/esd/simplelink_msp432_sdk/<IP_ADDRESS>/docs/tiposix/Users_Guide.html#summary-of-functions-supported-in-ti-posix

Thank you for this feedback. We will take into consideration improvements to the POSIX layer and related items and prioritize it.

Hello edbk,
By the way, are there any specific functions or variables that you looking for?
The https://github.com/aws/aws-iot-device-sdk-embedded-C/tree/v4_beta uses a posix implementation for their Linux port. It may be helpful to check out.


ERROR: for volumes_data  Mounts denied: er -> Preferences.

Hi there!
I can't "docker-compose up" if I'm using DBs. I don't have local folders on my macOS machine, for example for mysql, no /var/lib/mysql. With my own images/containers, I create my DVC like this: "docker create -v /var/lib/mysql --name ...".
Is there any way to handle it in the same way with docker-compose? I'm not familiar with it yet. Or is there a way to create /var/lib/mysql on the fly like I do for my other containers, with some options in the docker-compose.yml? Curious.
Thanks!

For info:
How I start my containers from my own images:

The issue I currently have with docker-compose up:

@godbout So if you want to make it work on a Mac OS X - you may need to create a folder in your home directory: 'var' and modify the docker-compose.yml file to include the '~' in front of the volumes in the database container:
`### Databases Data Container ################################
volumes_data:
    build: ./volumes/data
    volumes:
        - ~/var/lib/mysql:/var/lib/mysql
        - ~/var/lib/postgres:/var/lib/postgres
        - ~/var/lib/mariadb:/var/lib/mariadb
        - ~/var/lib/memcached:/var/lib/memcached
        - ~/var/lib/redis:/data
        - ~/var/lib/neo4j:/var/lib/neo4j/data
        - ~/var/lib/mongo:/data/db

`

Hey @ronpeled thanks for idea. As I don't need to use mysql for now I didn't dig into but yeah, that sure makes sense. When I'll have time I'll check if there's still a way to do like the "docker create" within a docker-compose.yml. Thanks

Actually I looked a bit, and it's possible to let the Docker Engine create a container by default with the db data:
volumes:
  # Just specify a path and let the Engine create a volume
  - /var/lib/mysql

  # Specify an absolute path mapping
  - /opt/data:/var/lib/mysql

New release of LaraDock was released today (LaraDock v4.*).

Upgrade your LaraDock git pull origin master
Rebuild your containers docker-compose build --no-cache (This might wipe your Data container)
Try again.


Project addition by Abhay-raj19.

Add a new project to the list
Add a new project to the list
I want to add a new project to the list. The name of the project is the Newsletter which is created using react,HTML,CSS,JS,etc.
Please assign me this issue.
Thank you!
Code of Conduct

[X] I agree to follow this project's Code of Conduct

I will be completing it as soon as possible.
Thankyou for assigning😊.

Completed. Thanks for your contributions 🎉 ❤


Add Flickr filter

It converts flickr's link into a linkable image

Thanks for the pull! The code looks fine, but I think it belongs in it's own separate gem because it isn't a general filter. If you do create one, let me know, and I can link it from the readme. Closing https://github.com/jch/html-pipeline/pull/209 for the same reason.

Ok, thx

@jch I just create html-pipeline-youtube gem for youtube filter. You can check it through the link, thanks for your advice.

Updated readme to link to your project https://github.com/jch/html-pipeline/commit/c2350a09b1fdec7806076418bc5fbf732e9eb02e

@jch thank you


Feature Request: Implement textType(text, charsPerMinute) method

The problem
Consider having AJAX driven text box on the screen (think about selecting airport on the travel website). In this case, user is typing text into input box, and AJAX calls are firing how user is typing the text.
Details
If we use simple text("Los Angeles") , then AJAX calls test would break, since the value "Los Angeles" is quickly injected into input box.
How to solve this?
Have a new textType("Los Angeles", 400) method, which would enter "Los Angeles" by typing each character with delay between them of 60/400 [seconds] .
"400" can be default value in config, and can be dev changed as needed. In that case secondary method textType("Los Angeles") can be implemented
CHEERS ON THE GREAT FRAMEWORK!

@DuskoV Have you tried $.sendKeys("Los Angeles") instead of $.text("Los Angeles")?
It does emulate exactly what real users do: type keys one-by-one. But without any delays.

@DuskoV Have you tried $.sendKeys("Los Angeles") instead of $.text("Los Angeles")?
It does emulate exactly what real users do: type keys one-by-one. But without any delays.

Yes, would be great to add delay to this method. Thanks!
On Fri, Jan 22, 2021 at 1:35 AM Andrei Solntsev<EMAIL_ADDRESS>wrote:

@DuskoV https://github.com/DuskoV Have you tried $.sendKeys("Los
Angeles") instead of $.text("Los Angeles")?
It does emulate exactly what real users do: type keys one-by-one. But
without any delays.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/selenide/selenide/issues/1358#issuecomment-765272069,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAL6S4RZNQJDOYVGFVTXUIDS3FBFLANCNFSM4VOWTDEQ
.

I implemented similar functionality through Actions (C#).

Implement custom Interaction:
 public class PauseInteraction : Interaction {
 	private readonly TimeSpan _duration;

 	public PauseInteraction(TimeSpan duration) : base(new KeyInputDevice("default keyboard")) {
 		_duration = duration;
 	}

 	public override Dictionary<string, object> ToDictionary()
 		=> new () {
 			["type"] = "pause",
 			["duration"] = Convert.ToInt64(_duration.TotalMilliseconds)
 		};

 	public override bool IsValidFor(InputDeviceKind sourceDeviceKind) {
 		return true;
 	}

 	public override string ToString() {
 		return string.Format(CultureInfo.InvariantCulture, "Pause [duration: {0} ms]", _duration.TotalMilliseconds);
 	}
 }

Implement new action as extension:
 public static class ActionsExtensions {
 	private static ActionBuilder GetActionsBuilder(Actions actions) => typeof(Actions).GetField("actionBuilder", BindingFlags.Instance | BindingFlags.NonPublic)
 	                                                                              ?.GetValue(actions) as ActionBuilder
 	                                                                   ?? throw new InvalidOperationException("private field ActionBuilder actionBuilder not found in class Actions");

 	public static Actions Wait(this Actions actions, TimeSpan duration) {
 		var pauseInteraction = new PauseInteraction(duration);
 		ActionBuilder actionBuilder = GetActionsBuilder(actions);
 		ActionSequence lastActionSequence = actionBuilder.ToActionSequenceList().LastOrDefault();

 		if (lastActionSequence == null) {
 			throw new WebDriverException($"You cannot use the action '{nameof(Wait)}' first");
 		}

 		lastActionSequence.AddAction(pauseInteraction);

 		return actions;
 	}
 }

Call 'Wait' action in code (for example):
 	foreach (char c in text) {
 		fillActions.SendKeys(c.ToString(new CultureInfo("En-Us", false)))
 		           .Wait(TimeSpan.FromMilliseconds(100));
 	}

@DuskoV So you need this "type with delays" feature just to test debounce? Probably it's not a good idea because such a test may be flaky. You never know in which order and with what speed the keys and requests will be sent and processed.
Anyway, you can always emulate such behaviour with just calling sendKeys("part of string") and sleep(ms) several times.
It doesn't seem to be a widely used feature at the moment.


Update sbt to 1.9.8

About this PR
📦 Updates org.scala-sbt:sbt from 1.9.7 to 1.9.8
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-sbt", artifactId = "sbt" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, version-scheme:early-semver, commit-count:1

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

Comparison is base (6f2c610) 89.44% compared to head (f6dffd1) 89.52%.

:exclamation: Current head f6dffd1 differs from pull request most recent head 5bf5c11. Consider uploading reports for the commit 5bf5c11 to get more accurate results

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1156      +/-   ##
===========================================
+ Coverage    89.44%   89.52%   +0.07%
===========================================
  Files          124      124
  Lines        10028    10028
  Branches       782      782
===========================================
+ Hits          8970     8978       +8
+ Misses        1058     1050       -8

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


Update docs: testStateMachine is neither a method nor exported

Hi,
Thanks for making this nice abstraction of xstate for react. I found that in the Readme and in the palyground you import and use the method testStateMachine, which is not exported by react-automata and indeed I can't find it in the source code.
I presume that it has been superceded by testStatechart? If I can help, please let me know.

Apologies, I see that I was on @3.0.0, and the @4.0.0 does indeed have the method. Closing.


Roll Flutter Engine from 5a0fd5fbecc6 to a9120452610a (5 revisions)

https://github.com/flutter/engine/compare/5a0fd5fbecc6...a9120452610a
2024-08-07<EMAIL_ADDRESS>Roll Skia from 5267a5a1e26a to 0c6dd1e6ff8e (1 revision) (flutter/engine#54392)
2024-08-07<EMAIL_ADDRESS>Roll Skia from a0e775f706cd to 5267a5a1e26a (1 revision) (flutter/engine#54389)
2024-08-07<EMAIL_ADDRESS>Roll Skia from 968a00456bc5 to a0e775f706cd (3 revisions) (flutter/engine#54386)
2024-08-07<EMAIL_ADDRESS>Roll buildroot to 6ef931b950d5b9477dba0e278b7006ae327e12f7 (flutter/engine#54384)
2024-08-07<EMAIL_ADDRESS>Roll Fuchsia Test Scripts from oOZyP3ets0uHdEqWW... to 3FWYCLt6cV86gWU8E... (flutter/engine#54382)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC jsimmons@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


SPSS 27 prod recipes should not have update policies

There should be no update/auto-update policies for SPSS, because if multiple versions are installed, these policies can get confused. We do not ever supply updates anyway, so they serve no purpose.

Removed the policies.

Deleted all the existing policies.


Starting off

Issue: UI Development for Mirage Chat App
Hello, Hacktoberfest participants!
As part of our Hacktoberfest project, we are looking for talented developers to help create a user interface for our chat app, Mirage.
What We Need
We need a user-friendly and visually appealing UI that interacts seamlessly with our backend server. The UI should allow users to create rooms, join existing rooms, send and receive messages, and manage their user experience effectively.
Resources
You can check the list of endpoints that Mirage's server code utilizes for communication. This will provide you with all the necessary information on how to integrate the frontend with the backend:

Mirage Server Endpoints

How to Get Started

Fork the repository and clone it to your local machine.
Review the existing endpoints to understand the data flow and functionalities.
Start designing the UI based on the requirements of a chat application.
Submit your pull requests to contribute your work!

Additional Notes

Feel free to reach out if you have any questions or need clarification on the project.
We encourage creativity in design and functionality, so bring your ideas to the table!

Looking forward to your contributions!
wrt #1

Launching Testnet Server for Mirage
We are excited to announce that in approximately 24 hours, we will launch the testnet server for Mirage! This will allow contributors to work with the endpoints without needing to install all the requirements and Python dependencies.
What You Can Do

Experiment with Endpoints: You can interact with the Mirage server endpoints and test the functionality without setting up a local environment.
Develop UI: If you’re interested in creating a user interface for the chat application, this is a great opportunity!

Stay tuned for updates, and feel free to reach out if you have any questions!

@KorryKatti
I have a strong foundation in front-end technologies, and as a UI/UX designer, I am passionate about creating user-friendly and visually appealing interfaces. I would love the opportunity to contribute to the Mirage Chat App project. If possible, please assign me a task, as I am eager to get started and collaborate with the team!

@KorryKatti
I have a strong foundation in front-end technologies, and as a UI/UX designer, I am passionate about creating user-friendly and visually appealing interfaces. I would love the opportunity to contribute to the Mirage Chat App project. If possible, please assign me a task, as I am eager to get started and collaborate with the team!

assigned, will be waiting for your PR

NOTE :  ONLY LOOKING FOR DESIGING OF THE APP RIGHT NOW , CONNECTING THE BACKEND WILL BE DONE AFTER 10-12 DAYS

@mahenoorsalat
As you seem to have the ui foundation i am willing to work such that we handle it
@KorryKatti you can assign me also

HEY @KorryKatti i've made one page for the same can u assign me so that i can pull the page

assigning now


Mount a local directory and login as the user

A very frequent test case is to be able to mount a local directory (say a git checkout, or $HOME) to expose parts of the host fs inside the machine.
There's one detail though, we are likely to want that, when writing files to that mount, we want to write them with the id, gid of the user of the host machine.

#43 has one idea for what the configuration for this feature could look like (mirrorUser):
cluster:
  name: cluster
  privateKey: cluster-key
machines:
- count: 3
  spec:
    image: quay.io/footloose/centos7
    name: node%d
    portMappings:
    - containerPort: 22
    mirrorUser: true


CI: add py39 and py310

Extend the Python versions tested.

8 tests are still failing.

The 3.8 failures look transient, the 3.10 failures look real.

Closing as replaced by #1030


Add in other 2 tables

I assume people will want to use this on the other tables. The shader for the CottonFox table may not be there, but I assume it is possible, so the textures are there once its created.

wrong branch. gonna try to push to the right one :/


[Asana] ...

Extension
https://www.raycast.com/raycast/asana
Description
Error:
Error: Error while refreshing tokens: 400 (Bad Request)
{"error":"invalid_grant"}

    at withAccessToken(r3)
Dr:index.js:11:2490
    at ray-navigation-stack
Lo:index.js:11:2088

Steps To Reproduce
Creating a task with the Asana Extension via Raycast
Current Behaviour
No response
Expected Behaviour
No response

It should be fixed in the latest release of the extension


Do I have to keep alive a long knx tunneling connection?

I'm creating a window service that will monitor knx events.
Should I do something manually to keep alive the connection, like requesting a status every minute, or isn't it needed?

For any type of connection you don't need to do anything
KNX Routing doesn't have state
KNX Tunneling (the one you're using) already has it's own keep alive (implemented in knx.net)
If you still want to be sure you can always request the state of the devices you want to monitor each X secs/mins

https://github.com/lifeemotions/knx.net/blob/master/src/KNXLib/KnxConnectionTunneling.cs#L203
Method StateRequest is called every 60s to send the 'keep alive'

Thanks for the info. I have now had a connection up for a week without problems.
When I look at my own logs, the keep alive polling address seems to be 1/1/1 because that is regularly shown in my logs. Maybe that address could be specified in the constructor to some defined value that I could then filter out.