[Package Issue]: Remove The Whole Folder of Fndroid.ClashForWindows

Please confirm these before moving forward

[X] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
[X] I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue
Installation issue.
Brief description of your issue
It appears package Fndroid.ClashForWindows's whole project has been deleted by @Fndroid (Author & Developer). All of its version is unavailable now. Please remove all version for it.
Related to #124619 https://github.com/microsoft/winget-pkgs/issues/124619#issuecomment-1792483273

Please wait a while. I need spot which one is a vanity URL.

@BrandonWanHuanSheng It is no need to verify. The whole project including releases has already deleted.

I will not verify but I need to verify that other app which is also being superseded by same url. Like Google.Chrome.Beta

It might take a while for the operation to complete.

I might be back for a while.

All the manifest queued to the pipelines

Once they are merged, please pin me to mark this issue as complete

All the pipelines is in required moderator to approvef

The pull request is being finalizing...

@CoolPlayLin, Did you noticed that pipelines have been merged. @LiCaoZ The whole directory of Fndroid.ClashforWindows was permanently deleted.

@CoolPlayLin, can you marked this issue as completed.

@CoolPlayLin Please marked it as resolved. All the files has been deleted in winget-pkgs.

Close with reason: Package removed from the repo;


fix: make remote git commands OS independent

The current solution does not work on Windows.

⚠Just realised I made another oopsy because I didn't just clone and make a PR properly. It can't cd and pull content if the directory already exists. Will fix tomorrow.


[Snyk] Security upgrade aiohttp from 3.6.2 to 3.9.4

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

requirements.txt

Vulnerabilities that will be fixed
By pinning:

Severity
Priority Score (*)
Issue
Upgrade
Breaking Change
Exploit Maturity

165/1000  Why? Confidentiality impact: None, Integrity impact: None, Availability impact: High, Scope: Unchanged, Exploit Maturity: No data, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.00045, Social Trends: No, Days since published: 0, Reachable: No, Transitive dependency: No, Is Malicious: No, Business Criticality: High, Provider Urgency: High, Package Popularity Score: 99, Impact: 5.99, Likelihood: 2.74, Score Version: V5
Infinite loop SNYK-PYTHON-AIOHTTP-6808823
aiohttp:  3.6.2 -> 3.9.4
No
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Is there an ETA on this being merged? Thanks in advance.


[Storage] Improve error code for PublicAccessNotPermitted

This PR is for a change to how PublicAccessNotPermitted is raised. Currently, from generated it is a ResourceExistsError, and so it will surface that (and PublicAccessNotPermitted is only known from the XML deserialization).
This PR checks for this special case, and if encountered forces it to be serialized as if it was not serialized from generated, thus allowing it to surface the correct error (auth error). An alternative approach is to make an adjustment at the _generated layer.
Resolves #26919

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-storage-blob

/reopen


Broken link

Hi, https://gcanti.github.io/fp-ts/tutorials/debugging-with-Trace.ts is broken (linked from https://gcanti.github.io/fp-ts/basics/)

Thanks! I now ran a link checker on the whole site and found a few more broken links – sad story …


Feature Request: Large Blogs / Multiple Writer sites would like better organization of content to "users" on Mastodon

What
Think of a large content blog -- with multiple users and sections, like a newspaper. While users will likely love to follow individual writers, they also would like to follow content types or categories of content as well -- instead of just writers or all content. That same site might have user generated content -- like classified ads (sticking with the newspaper idea).
Why
For example in the newspaper site example -- a user may want to follow all sports coverage, but not news or business. So being able to define a post type, category, or tag as a virtual Mastodon user would be ideal for this.
How
Example -- assuming that the newspaper publishes at<EMAIL_ADDRESS>for all content:
All content in the "Sports" category could map to<EMAIL_ADDRESS>All content tagged as San Francisco Giants could map to<EMAIL_ADDRESS>All content with post type "classified ad" could map to<EMAIL_ADDRESS>etc.

Especially for larger sites, this is a very compelling feature request and would enable a robust means of following specific content users care about independently of any individual author from the site. Highly encouraged that this be considered.

This could lead to an almost infinite number of federated accounts being created, rendering account search unusable when trying to find a user.  We don't want a repeat of the BirdSiteLive account creation fiasco - https://write.as/nicolas-constant/closing-the-official-bsl-instance
I suggest:

No matter what, do not allow the creation an account for "<EMAIL_ADDRESS>(800 million user accounts could be created)
Allow the enabling of a federating account for each Contributor and above, but do not do it by default (see fedidb for an example of a wordpress site already showing >10k user accounts https://fedidb.org/software/wordpress)
"tag" already exists in AP https://www.w3.org/TR/activitystreams-vocabulary/#dfn-tag and WP tags can map to this easily
Consider use of AP's Collection to map to WP Category (eg https://www.w3.org/ns/activitystreams#CollectionPage and /category/[slug]/ - AP clients may need to learn to use Collection in...
context. I wonder if wp_post_type could use AP's Object context as a means to help clients know what to do with a given post. This may also help with inReplyTo for threaded replies to a post.
More of an aside, but if more AP clients allowed users to follow an RSS feed as well as AP accounts (1) the world would be a better place (2) people would stop creating "accounts" for RSS feeds and (3) you could then simply use the existing WP rss feeds and hooks.

Yeah, I agree that something automated would not be all that useful. But something more manually created could be very useful. Especially so for content features on a subject -- either long term (a sports team, editorial focus) or short term (Election 2024, Olympics, etc.)
Something like defining a "user" by selecting any mix of single or multiple post_types and taxonomy / taxonomies.
An Example:
user =<EMAIL_ADDRESS>is defined as
post_type = post, category = sports, and tag = worldcup2023
Cheers,
Jeff

Curious if this feature was officially closed, or only closed due to a bot making it so after no action? Any chance of moving this idea back to life?


Docker Install instructions page is broken now that v2.0 is the latest image

URL(s) with the issue:
https://www.tensorflow.org/install/docker
Documentation page with the issue:
https://www.tensorflow.org/install/docker
Description of issue (what needs changing):
Since the latest docker builds are now tensorflow v2.x instead of v1.x the python example script on this page doesn't work out of the box. If the user copy and pastes the commands from this page they'll get a "AttributeError: module 'tensorflow' has no attribute 'enable_eager_execution'" error when trying to verify their docker container.
The python example script can be changing to this to fix it:
import tensorflow.compat.v1 as tf
tf.enable_eager_execution();
print(tf.reduce_sum(tf.random_normal([1000, 1000])))

A better alternative however would be to change it to a TF v2.0 native example.

Thanks. Fixed in https://github.com/tensorflow/docs/pull/1261 and tensorflow/org will get updated next site push.

The docker installation verification code is still broken. There is still a version 1.x API call in there. I've opened PR #1310 which fixes this.

The docker installation verification code is still broken. There is still a version 1.x API call in there. I've opened PR #1310 which fixes this.


Mouse hover is not working in flutter web.

Steps to Reproduce

Run the project by run command flutter run -d chrome.
Uploading mouse_interaction.zip…   Here is a sample.
Step to reproduce :

After running the project just tap on the screen then it shows the tap position.

Then move the mouse pointer over the screen it doesn't show any position.

Note: I have included the MouseRegion widget before the Listener if I include MouseRegion after the Listener mouse hover is working. But I want both MouseRegion and Listener working. I have checked this with the flutter version 1.19.0-4.3.pre, both Mouse and listener is working fine. But in the latest flutter beta, both are not working only the last widget gets work.
Expected results:

Want to get both mouse and listener position.

Actual results:

But, I get a listener position only.

Logs

PS D:\Dart\mouse_interaction> flutter analyze
Analyzing mouse_interaction...
No issues found! (ran in 2.6s)

PS D:\Dart\mouse_interaction> flutter doctor -v
[√] Flutter (Channel beta, 1.20.0-7.4.pre, on Microsoft Windows [Version 10.0.17763.1039], locale en-US)
    • Flutter version 1.20.0-7.4.pre at C:\src\flutter
    • Framework revision 916c3ac648 (4 days ago), 2020-08-01 09:01:12 -0700
    • Engine revision d6ee1499c2
    • Dart version 2.9.0 (build 2.9.0-21.10.beta)

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at C:\Users\AdminUser\AppData\Local\Android\sdk
    • Platform android-29, build-tools 29.0.2
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[√] Android Studio (version 3.6)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 44.0.2
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)

[√] VS Code, 64-bit edition (version 1.47.2)
    • VS Code at C:\Program Files\Microsoft VS Code
    • Flutter extension version 3.13.1

[√] Connected device (3 available)
    • Redmi Note 6 Pro (mobile) • 53a1093e   • android-arm64  • Android 9 (API 28)
    • Web Server (web)          • web-server • web-javascript • Flutter Tools
    • Chrome (web)              • chrome     • web-javascript • Google Chrome 84.0.4147.105

• No issues found!

Hi @Yuvaraj-Gajaraj
The link you provided does not contains a reproducible code of the issue, please provide that code to help you.
thank you.

Hi, @pedromassangocode  Thanks for your reply,
Here is the code snippet
import 'package:flutter/material.dart';

import 'package:flutter/widgets.dart';

void main() => runApp(MyApp());

/// This Widget is the main application widget.
class MyApp extends StatelessWidget {
  static const String _title = 'Flutter Code Sample';

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: _title,
      home: Scaffold(
        appBar: AppBar(title: const Text(_title)),
        body: Center(
          child: MyStatefulWidget(),
        ),
      ),
    );
  }
}

class MyStatefulWidget extends StatefulWidget {

  @override
  _MyStatefulWidgetState createState() => _MyStatefulWidgetState();
}

class _MyStatefulWidgetState extends State<MyStatefulWidget> {
  double x = 0.0;
  double y = 0.0;
  String eventType = 'No event';

  @override
  Widget build(BuildContext context) {
    return Container(
            child: Stack(
              children: <Widget>[
                Text('$eventType : ($x,$y)',style: const TextStyle(fontSize: 28,fontWeight: FontWeight.bold),),
                MouseRegion(
                  child: Container(
                    height: MediaQuery.of(context).size.height,
                    width: MediaQuery.of(context).size.width,
                    decoration: const BoxDecoration(color: Colors.transparent)
                  ),
                    onHover: (PointerEvent event) {
                      setState(() {
                        x = event.position.dx.roundToDouble();
                        y = event.position.dy.roundToDouble();
                        eventType = 'Mouse';
                      });
                    },
                ),
                Listener(
                  child: Container(
                  height: MediaQuery.of(context).size.height,
                  width: MediaQuery.of(context).size.width,
                  decoration: const BoxDecoration(color: Colors.transparent)),
                  onPointerDown: (PointerDownEvent event) {
                    setState(() {
                      x = event.position.dx.roundToDouble();
                      y = event.position.dy.roundToDouble();
                      eventType = 'Listener';
                    });
                  },
                ),
              ],
            ),
          );
  }
}

I guess because you are using Stack, the Listener widget containing the Container is on top of the Stack Tree. That is why the MouseRegion is not working.

Hi @Yuvaraj-Gajaraj
Does the code bellow helps you?
import 'package:flutter/material.dart';

import 'package:flutter/widgets.dart';

void main() => runApp(MyApp());

/// This Widget is the main application widget.
class MyApp extends StatelessWidget {
  static const String _title = 'Flutter Code Sample';

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: _title,
      home: Scaffold(
        appBar: AppBar(title: const Text(_title)),
        body: Center(
          child: MyStatefulWidget(),
        ),
      ),
    );
  }
}

class MyStatefulWidget extends StatefulWidget {

  @override
  _MyStatefulWidgetState createState() => _MyStatefulWidgetState();
}

class _MyStatefulWidgetState extends State<MyStatefulWidget> {
  double x = 0.0;
  double y = 0.0;
  String eventType = 'No event';

  @override
  Widget build(BuildContext context) {
    return MouseRegion(
      onHover: (PointerEvent event) {
        setState(() {
          x = event.position.dx.roundToDouble();
          y = event.position.dy.roundToDouble();
          eventType = 'Mouse';
        });
      },
      child: Container(
        child: Stack(
          children: <Widget>[
            Text('$eventType : ($x,$y)',style: const TextStyle(fontSize: 28,fontWeight: FontWeight.bold),),
            Container(
                height: MediaQuery.of(context).size.height,
                width: MediaQuery.of(context).size.width,
                decoration: const BoxDecoration(color: Colors.transparent)
            ),
            Listener(
              child: Container(
                  height: MediaQuery.of(context).size.height,
                  width: MediaQuery.of(context).size.width,
                  decoration: const BoxDecoration(color: Colors.transparent)),
              onPointerDown: (PointerDownEvent event) {
                setState(() {
                  x = event.position.dx.roundToDouble();
                  y = event.position.dy.roundToDouble();
                  eventType = 'Listener';
                });
              },
            ),
          ],
        ),
      ),
    );
  }
}

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


Cox::LibSodium::NONCE_BYTES points to the wrong function

When I try to instantiate a Cox::Nonce manually, it was raising because it was expecting 16 bytes. The nonce is supposed to be 24 bytes.

Thanks for the quick merge!


102 tests working

Coverage increased (+0.2%) to 96.919% when pulling 158fb917834430b46fe5114b4c3d593169dc81a0 on nassir-issue139 into c13763951b376be5ccea781ce0881b6c7a73e522 on staging-branch.


EditorConfig does not fix tabs in files.

Hello,
I am currently learning Java. I copy/paste a lot of source files from the internet, which sometimes have inconsistent tab sizes.
I work with Atom and installed EditorConfig to fix files I download. They come with 2, 3 or 4 spaces and as well as hard or soft tabs (spaces). I noticed EditorConfig in Atom does not seem to correct the tabs in any file I try. I have Tab Type in Settings -> Editor set to auto.
For instance, in the following file, each indentation is filled with 2 spaces:
public class HelloWorld {
  public static int x = 7;
  public int y = 3;

  public static void main(String[] args) {
    System.out.println("Hello World!");

    HelloWorld a = new HelloWorld();
    HelloWorld b = new HelloWorld();
    a.y = 5;
    b.y = 6;
    a.x = 1;
    b.x = 2;
    System.out.println("a.y = " + a.y);
    System.out.println("b.y = " + b.y);
    System.out.println("a.x = " + a.x);
    System.out.println("b.x = " + b.x);
    System.out.println("HelloWorld.x = " + HelloWorld.x);
  }
}

When I run EditorConfig: Fix File, I get the message:

HelloWorld.java
The file HelloWorld.java conformed to the end_of_line and indent_style properties. No changes were applied.

It seems like EditorConfig considers the file to be correct while it is not, at least according to the .edutorconfig file I shared below. I also run EditorConfig: Show State and got this message:

No problems affecting HelloWorld.java
The editorconfig was applied successfully and the editor for this file should work as expected. If you face any unexpected behavior please report the issue to us
Active Configuration
EditorConfig settings	Current values
charset	utf8
end_of_line	\n
indent_size / tab_width	4
indent_style	space
insert_final_newline	true
max_line_length	unset
trim_trailing_whitespace	true
Note: unset means atom-editorconfig is not influencing a property's behaviour. A full description of all properties can be found on editorconfig.org or their project's Wiki

Is it a bug or have I installed anything that prevents EditorConfig from working?
Thanks
EDIT.
My OS is Ubuntu 20.04 LTS.


Display size when resizing

Abstract
When resizing a terminal window via my window manager I would like to see what the new size will be in characters.
Motivation
I miss this feature from ROXTerm. It's probably a symptom of neurosis but I like to resize windows to round numbers of characters.
Not high priority.
Specification

This is ROXTerm being resized by dragging the window manager decoration in the corner. The sise updates in real time.

didn't we have that fixed? @Yaraslaut ? I barely remember that one of you had been working on this. Am i remembering wrong?
On the other hand, I'm having my one grid-resize refactor branch.
Thanks for stressing me @cqexbesd. Please gimme some time. :)

Lol. I realized I was answering to the wrong topic. Nevertheless, it still applies (what I said). and your wish to display the current screen size can be surely implemented, too. - In various ways. Didn't decide yet to what would be best.

Indicator statusline could permanently display the current screen size in characters
An overlay could be rendered in the middle of the screen during resize.
Actual GUI elements could be used to show the current grid screen size during resize

I think 2 or 3 would be good. 1 is fine but I think it is a different feature.
There is really no hurry to implement my suggestions. I am already quite happy with contour and I can wait for my every whim to be implemented :-)

Implemented in #1203
@cqexbesd   you now can give it a try now

Works great! Thanks!


Look out for maximum canvas size?

TLDR: certain browsers (looking at you Chrome) impose maximum canvas size restrictions, which can lead to weird crashes (frustratingly, without any context). This is described at vega/vega-lite#4974.
It may be a good idea to somehow alert the user if the rank plot will contain, say, more than 30k  features when in "ordinal" mode. Or switch to SVG somehow?
Just writing this down so that it's here for the future.

Worth noting that this appears to impact mobile browsers as well... Chrome on Android consistently just goes empty (it shows the rest of the graph though) right around x=620 when you set the rank plot width to 10px. This seems to be due to a max width of 6200px ish -- at 9px bar widths the limit is around x=688, at 8px bar widths the limit is around x=775, ...

Yeah, yuck, using SVG resolves this (on mobile at least). Easiest solution is probs adding a canvas/SVG toggle and noting somewhere clear that "HEY IF THE PLOT GETS CUT OFF TRY SVG"


Update README version dependency to latest

Coverage decreased (-0.6%) to 78.732% when pulling a9bdfaef1851fc8aa8c60d8e266c4863ba6c99e9 on update-readme-version into a27c09b8b2aaa5a505ced9ddd676181c7955ee55 on master.


Update model to support rate limitis

Is your feature request related to a specific problem?
We need to give users a way to set rate limits for calls within their connectors.
Describe the solution you'd like
A rate_limit config should exist within connectors or saas connectors config:
    "rate_limit_config" : [
      {
          "rate" : 100,
          "period" : seconds,
          "custom_key" : my_custom_key
      },
      {
          "rate" : 500000,
          "period" : days,
          "custom_key" : my_custom_key2
      }
    ]

Additional context
We need to explore if it is feasible to apply rate limits to all connectors or if it just makes sense within saas connectors. We will prioritize saas connectors for this feature if it makes sense to.

Closing in favor of https://github.com/ethyca/fides/issues/1221


Update referrer list in 0.3.0

Update referer.yml file in scala-referer-parser 0.3.0.
Backport to version 0.3.0 possibility to read latest referrers from https://s3-eu-west-1.amazonaws.com/snowplow-hosted-assets/third-party/referer-parser/referers-latest.yml

I'm just not sure the ticket name makes sense. I think 0.3.0 here is irrelevant? It can be just Update referers.yml. We usually try to use same ticket names for recurring tasks, but previous update was too long time ago when we didn't have any conventions.

Ok, I'll rename it.


refactor(gitsigns): use on_attach to set mapping

This PR refactor current gitsigns config, that for setting up key binding we can use on_attach
This makes better customization flow as we can access to vim.fn
Signed-off-by: Aaron Pham<EMAIL_ADDRESS>

A little issue is which-key won't show the command content after <leader>h being pressed in this way.

ah I see. I updated a section in keybinds that allows setting up description
:with_desc


How to preserve page state when a new page is opened

Hi! thank's for making this package as it solves my hours of frustration to make a persistent bottom navbar while navigating on pages.
However, I face difficulties to handle page state when navigating through tabs.
For example:
Supposed that I'm in a homepage, then I clicked the details page. Hence, the homepage is navigating to it's details page. Then, when I'm in the home page's details page, I press another tab and the app is navigating to a new page. But, when I navigating to the homepage again, the page is returned to it's parent page not to details page. I know this happens because we implement navigatorKey.currentState.maybePop();  in the ButtomNavBar's onTap function. Then I tried to comment that line, but what I found is that navigating to another page is not possible since the homepage's details page isn't popped yet.
Another example:
when I'm on a homepage that has a hundred lists, I scroll the page until I reach the end of the list. Then, I'm navigating to another page. But when I'm navigating back to the homepage, I found out that the page is scrolled back to it's first list again. So, how do I preserve the scroll position when navigating through pages?
Thank you, hope my explanation above is clear enough.

We have the same issue on Android. It's not happening on iOS the navigation state is preserved and the navigation work properly between the tabs. On Android, if we don't pop the route, the content of the page is not updated (navigation between page not working).

Hi guys! Could please elaborate more in the issue? When is the navigation preserved vs not preserved? Give me a complete example so we can solve this together

Hi! It seems that on Android we absolutely need to pop to first route when switching bottom tabs.
For now I have this code when I tap on a tab :
              if (Platform.isAndroid) {                 _navigatorKeyByPage.forEach((key) {                   if (key.currentState != null && key.currentState.canPop()) {                     key.currentState?.popUntil((route) => route.isFirst);                   }                 });               }               _views = _getViews();               _selectedTabIndex = index;
This is the code for the custom navigator in my Scaffold :
CustomNavigator(               navigatorKey: _navigatorKeyByPage.elementAt(_selectedTabIndex),               pageRoute: PageRoutes.cupertinoPageRoute,               home: _views.elementAt(_selectedTabIndex)),
So with this on iOS when I switch tabs the navigation state is preserved but on Android I pop until the first route because if I don't do this it doesn't update the body of the page.

    `SafeArea(
        top: false,
        child: IndexedStack(
          index: _currentIndex,
          children: <Widget>[
            CustomNavigator(
              navigatorKey: _navigatorKeys.elementAt(0),
              home: _children.elementAt(0),
              pageRoute: PageRoutes.materialPageRoute,
            ),

            CustomNavigator(
              navigatorKey: _navigatorKeys.elementAt(1),
              home: _children.elementAt(1),
              pageRoute: PageRoutes.materialPageRoute,
            ),

            CustomNavigator(
              navigatorKey: _navigatorKeys.elementAt(2),
              home: _children.elementAt(2),
              pageRoute: PageRoutes.materialPageRoute,
            ),
            CustomNavigator(
              navigatorKey: _navigatorKeys.elementAt(3),
              home: _children.elementAt(3),
              pageRoute: PageRoutes.materialPageRoute,
            ),

          ],

        ),
      ),`


Typescript without Types

When consuming the library through typescript, I have no types, everything is any type.
We need the ability to have the autocomplete when developing.
You can reproduce this bug building the project with
 npm run build

Then you can go to the folder examples and you can see the editor shows typescript errors, because it cannot detect the types from dist/types

Fixed


api: update googleapis buf module version

Commit Message: This updates the version of buf.build/googleapis/googleapis to the latest pushed version. The BSR had a change in the googleapis module to to concerns with the number of files in BSR, requiring previous commits to be removed. See https://docs.buf.build/faq#googleapis-failure for more details. This PR fixes the issue for envoy.
Additional Description:
Risk Level: Low
Testing:
Docs Changes: None
Release Notes:
Platform Specific Features:

LGTM. Thanks.

cc @phlax This should also fix the problem of CI.

we will need to backport this i think


repair DeviceProperties_RunDLL typedef example

It was missing a close-parenthesis, and the indentation was quite inconsistent.

Thanks for the PR, Sam!  The fix should reach the live site in ~10 min


WIP: [JS] Add optional batch hint to Vector.get

Added an optional batch to Vector.get, as well as a *batches iterator. The most significant changes are in ListVector and IndexVector, because I removed the returnWithBatchIndex argument and made some tweaks to the way offset vectors are handled (Rather than subtracting batch when accessing data, use length - 1 to reduce `index while iterating).

Can you add some tests? Are there coverage tools available for Typescript?

@wesm yep we have coverage ready to go, but commented out in the CI script until we set up something like coveralls.
@TheNeuralBit sorry I haven't responded to your comments on 1652 yet, I'll do that right now.

@TheNeuralBit could you add some unit tests and update the PR title with the JIRA number?

@wesm I think this may be irrelevant now based on our new plans for the Vector class
@trxcllnt what do you think? Maybe ARROW-1652 should be changed to "add batch vector accessor" and include your planned changes

@TheNeuralBit yeah that works for me, that way it's still tracked


Fix mapper for Runs and Notifications settings. Fixes #537

Rebased, and merged.
Thanks for your contribution !


main.py just crashes when opened

When I open it, it opens for a second then just crashes.
I have installed the requirements.txt file with the command given.
Here is what my jsonc file looks like from the outside: https://imgur.com/a/8xM9zY9
From the inside: https://imgur.com/a/VEQ2QHo
my whole folder: https://imgur.com/a/ktfxgkJ

Can you send a screenshot of running main.py from the command line / powershell / terminal? Like this

Hello, starting it from cmd somehow fixes it and it works perfectly, thanks for the help!


Fix Xiaomi devices

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.003%) to 80.994%

Totals

Change from base Build<PHONE_NUMBER>:
0.003%

Covered Lines:
4871

Relevant Lines:
6014

💛  - Coveralls

Related PR: https://github.com/zigpy/zha-device-handlers/pull/1248


Proposal: Add HTTP header with hostname component of canonical name

Background
The original registry V2 API specification did not have support for using fully canonical name in the URL. This meant that the name as used by docker (i.e. registry.example.com/someimage) would be given to the registry as "someimage" and "registry.example.com" might be a name component only known to the docker daemon. The docker daemon code developed the concept of a local name (what an image was referred to inside the docker engine) and remote name (the name given to the registry). Additionally when attempting to rectify these difference in the reference package the concept of a canonical name was developed. A canonical name always had a hostname and the "remote name" of the registry. Images inside the docker daemon which were on private registries were also canonical names, however docker hub images may be referred to by a short name (such as "ubunut"), but would have a canonical name "docker.io/library/ubuntu". Despite this addition of the reference package, the registry has no way to re-create the canonical name the daemon daemon uses, however for storage this has need been needed. More recently though, when configuring a registry as a proxy cache, the need arises to re-create the canonical name in order to support the oft-requested feature of proxying to private registries.
Proposal
Define an HTTP header variable to be used to represent the hostname component of the canonical image name. The canonical image name can then be recreate on a proxy or any other registry from joining this HTTP header with the remote name used in the API URL. This HTTP header will need to be added in the registry client and only be available on newer version of Docker which adopt the updated client.
I propose we name use the HTTP header Docker-Image-Hostname to be consistent with similar headers such as  Docker-Upload-UUID, Docker-Content-Digest, and Docker-Distribution-API-Version.

cc @nwt


CLOUDSTACK-9128: Testcase to verify physical_size attribute of snapshot_store_ref table

Verify if physical_size attribute of snapshot_store_ref table stores actual physical size of the snapshot

Testcase result:
Check Snapshots size in database ... === TestName: test_02_snapshot_size_check | Status : SUCCESS ===
ok

Ran 1 test in 337.826s
OK

@remibergsma can you merge these changes?  thanks, Raja

LGTM !!
Test Results:
Check Snapshots size in database ... === TestName: test_02_snapshot_size_check | Status : SUCCESS ===
ok
----------------------------------------------------------------------
Ran 1 tests in 385.302s
OK

@pvr9711 I guess you know what we need before merge, don't you? ;-)

LGTM
based on code review

Did code review. Code looks  good to me

@pritisarap12 Could you please rebase this against the current master?

Rebased with current master.


0.0.5 release?

It would be helpful to cut a 0.0.5 release to bring in a few bugfixes. Anything else we'd want to bring in first @astheeggeggs?

Have bumped version and pushed to pypI.


[Bug]: RFI data never loaded, always raises warning for zip files

Checked for duplicates
Yes - I've already checked
Describe the bug
Zipfiles which contain the RFI data don't get loaded. They always raise the warning that the files don't exist.
(mapping-311) [staniewi@aurora COMPASS]$ unzip -l tests/data/S1A_IW_SLC__1SDV_20221016T015043_20221016T015111_045461_056FC0_6681.zip | grep rfi
        0  02-01-2023 13:39   S1A_IW_SLC__1SDV_20221016T015043_20221016T015111_045461_056FC0_6681.SAFE/annotation/rfi/
     7301  02-01-2023 14:28   S1A_IW_SLC__1SDV_20221016T015043_20221016T015111_045461_056FC0_6681.SAFE/annotation/rfi/rfi-s1a-iw3-slc-vv-20221016t015045-20221016t015110-045461-056fc0-006.xml
     7301  02-01-2023 14:28   S1A_IW_SLC__1SDV_20221016T015043_20221016T015111_045461_056FC0_6681.SAFE/annotation/rfi/rfi-s1a-iw2-slc-vh-20221016t015044-20221016t015109-045461-056fc0-002.xml
     6958  02-01-2023 14:28   S1A_IW_SLC__1SDV_20221016T015043_20221016T015111_045461_056FC0_6681.SAFE/annotation/rfi/rfi-s1a-iw1-slc-vv-20221016t015043-20221016t015111-045461-056fc0-004.xml
     7301  02-01-2023 14:28   S1A_IW_SLC__1SDV_20221016T015043_20221016T015111_045461_056FC0_6681.SAFE/annotation/rfi/rfi-s1a-iw3-slc-vh-20221016t015045-20221016t015110-045461-056fc0-003.xml
     7301  02-01-2023 14:28   S1A_IW_SLC__1SDV_20221016T015043_20221016T015111_045461_056FC0_6681.SAFE/annotation/rfi/rfi-s1a-iw2-slc-vv-20221016t015044-20221016t015109-045461-056fc0-005.xml
     6958  02-01-2023 14:28   S1A_IW_SLC__1SDV_20221016T015043_20221016T015111_045461_056FC0_6681.SAFE/annotation/rfi/rfi-s1a-iw1-slc-vh-20221016t015043-20221016t015111-045461-056fc0-001.xml

(mapping-311) [staniewi@aurora COMPASS]$ s1_info tests/data/S1A_IW_SLC__1SDV_20221016T015043_20221016T015111_045461_056FC0_6681.zip
Found 1 Sentinel-1 SLC products.
Bursts in tests/data/S1A_IW_SLC__1SDV_20221016T015043_20221016T015111_045461_056FC0_6681.zip:
--------------------------------------------------------------------------------
/u/aurora-r0/staniewi/repos/s1-reader/src/s1reader/s1_reader.py:683: UserWarning: No RFI metadata found at S1A_IW_SLC__1SDV_20221016T015043_20221016T015111_045461_056FC0_6681.SAFE/annotation/rfi/rfi-s1a-iw1-slc-vv-20221016t015043-20221016t015111-045461-056fc0-004.xml.
  warnings.warn(f"No RFI metadata found at {rfi_annotation_path}.")
...

https://github.com/isce-framework/s1-reader/blob/559f026e5a47f81e010a0bc47d73dc15afc0b1bd/src/s1reader/s1_reader.py#L673-L675
These lines check if a files exists, but it's inside the zip file.
What did you expect?

No warning should be printed when there's not an RFI file available, since everything pre-2021 has no RFI and it's not a problem
we should add a unit test for an example with RFI loading as a minimum smoke test

Reproducible steps
`s1_info` on any .zip file will print a `UserWarning`

Environment
No response

Thanks for the report Scott. It looks like the culprit has been introduced from your PR #119  that makes RFI loading optional. So I think you would the best person who can fix that issue. Maybe try...except will to the trick.
Let me work on adding a unit test for RFI. That would include not only adding the test code, but also updating the test dataset because the current test data S1A_IW_SLC__1SDV_20200511T135117_20200511T135144_032518_03C421_7768.zip does not have the RFI annotation.


the landscape appears not updated

Some members have updates their entries on Crunchbase but the landscape appears not able to reflect the changes.
Taken a look at https://github.com/cncf/landscape:
processed_landscape.yml
Automated update by CNCF-bot
6 days ago
This file was updated 6 days ago (was automatically updated daily before) … wondering if it is the reason.

@AndreyKozlov1984 can you investigate?

a friendly ping.

Checking why automatic update failed.

FATAL: no headquarter addresses for infracost at https://www.crunchbase.com/organization/infracost
Someone needs to update the crunchbase entry
@taylorwaggoner  or @caniszczyk  can you do it ?

@AndreyKozlov1984 I added a HQ to their Crunchbase, thanks

I am checking if this helps, so far that looks like the only blocking issue

Thx.


Add frontend tests

User Story
As a developer, I would like to have a tested frontend codebase. so that it is less prone to bugs.
Detailed Description
We need to decide if we are going to do this automated or manual.
Automated approach
Add frontend tests using jest and enzyme. Check out this tutorial: https://blog.sapegin.me/all/react-testing-1-best-practices/
Manual approach
Create a frontend testing checklist as a markdown file.
We have to plan the tests anyway, so plan it out on paper and then one of the following:

write automated tests
expand out the paper plan

Subtasks (Please also link task PRs here)

[]
[]
[]

@lorance19  @akanksha003  @ChoiJ0527  to decide whether to do manual or automated testing


Speed insights issue

Hmm, I tried this locally and wasn't able to duplicate this problem. Lighthouse properly detected the test page (in this repo) as not using any deprecated APIs. Perhaps your site wasn't loading the polyfill soon enough, and some native mutation event calls are getting through?


fix: Retroactively sign off on previous commits

Description:
Summarize the changes you're submitting in a few sentences, including Jira ticket ATL-xxxx if applicable.
Link to any discussion, related issues and bug reports to give the context to help the reviewer understand the PR.
Alternatives Considered (optional):
Link to existing ADR (Architecture Decision Record), if any. If relevant, describe other approaches explored and the selected approach. Documenting why the methods were not selected will create a knowledge base for future reference, helping prevent others from revisiting less optimal ideas.
Checklist:

[x] My PR follows the contribution guidelines of this project
[ ] My PR is free of third-party dependencies that don't comply with the Allowlist
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked the PR title to follow the conventional commit specification

coverage: 48.578%. remained the same
when pulling ce8bed4f1661f119938cbc2ef0bc1a87e0846f99 on fix-signoff-old-commits
into f74cc3e374a7c2222b078363e09475cd3cb971b0 on main.


Fix for running on Windows on non-C drive

Thank you very much for making this extension! I use it for hledger on Mac and I love it.
On Windows, the extension unfortunately does not work since it tries to call the command template with workspaceRoot = getWorkspaceFolder(...).uri.path.
https://github.com/oshikiri/vscode-generic-annotator/blob/f808775d10ebbc1f72269650129e123c623e5976/src/extension.ts#L63
https://github.com/oshikiri/vscode-generic-annotator/blob/f808775d10ebbc1f72269650129e123c623e5976/src/decoration.ts#L32
I think it should be ...uri.fsPath.
uri.path => node /g:/Finance/scripts/day-of-week-hints.js /G:/Finance/2023.journal
-- This causes error because it looks for a folder called G: inside C:, like C:/G:/Finance/...
uri.fsPath => node g:\Finance\scripts\day-of-week-hints.js G:\Finance\2023.journal
-- I think this should work (not tested)

I think it should be ...uri.fsPath.

Agreed
https://code.visualstudio.com/api/references/vscode-api#Uri

Released as v2.4.0


decorated and resizable do not work in Debian/Gnome shell/wayland

$ uname -a
Linux *** 4.8.0-2-amd64 #1 SMP Debian 4.8.11-1 (2016-12-02) x86_64 GNU/Linux

with GNOME 3.22.2 using wayland.
I tried the example:
extern crate piston_window;

use piston_window::*;

fn main() {
    let mut window: PistonWindow =
        WindowSettings::new("Hello Piston!", [640, 480])
		.exit_on_esc(true).decorated(true).resizable(true).build().unwrap();
    while let Some(e) = window.next() {
        window.draw_2d(&e, |c, g| {
            clear([1.0; 4], g);
            rectangle([1.0, 0.0, 0.0, 1.0], // red
                      [0.0, 0.0, 100.0, 100.0],
                      c.transform, g);
        });
    }
}

I also tried the frontpage glutin example: there were no window.
My window is not decorated, and I cannot resize it.
I tried in a gnome session using X11, and there were no issue: the window was decorated and resizable.
There is no problem with the SDL2 backend.
(This is a c/c from an issue I opened in a wrong place: https://github.com/PistonDevelopers/piston/issues/1157)

Looks like a duplicate of https://github.com/tomaka/winit/issues/163

Sorry. This is difficult in this kind of big projects to find the right place to report a bug.


Add sum check for bootstraps

This PR is like #25 but for bootstraps.  Unlike #25, it only throws a warning if at least some of the bootstrap runs pass the checksum, discarding the runs that fail (the number discarded is in the warning).  If no bootstraps pass, then it throws an error.
This PR includes a test for a case where some of the bootstrap runs have zero-variance levels for a categorical variable but other runs include all the levels.  As a result, this test should fail until this branch is merged with #27, after which is should pass.
@sinanpl as always let me know if there's anything I can help clarify for this!

NB that I'm pretty sure that this PR clobbers #13, but it'll get the functionality back in #31 anyway, so I'm not correcting it here.


wasm-SPIRV

Feature
SPIRV compilation target
Benefit
Adding SPIRV target for wasm makes it the best way to write code once and use it with CPU and GPU so it's going to be powerful option to use
Implementation
I think we should convert or code to naga-ir , and then use wgpu for running or spirv . I think abstraction over memory allocation copy and etc  cpu<->gpu transfers can improve development time
Alternatives
Directly compiling to spirv

Wasm and SPIR-V have a fundamentally different memory model from each other. Wasm models memory as a single array of bytes, while SPIR-V models it as a bunch of typed objects. Some of these may be arrays into which you can index, but it fundamentally doesn't support arbitrary pointers like wasm does. https://github.com/EmbarkStudios/spirt can lift some uses of untyped memory (rust, wasm, ...) into typed memory (spir-v), but can't lift all of them. Also to make any effective use of a GPU you also need to support work-group local memory and more, which wasm doesn't support.

Wasm and SPIR-V have a fundamentally different memory model from each other. Wasm models memory as a single array of bytes, while SPIR-V models it as a bunch of typed objects. Some of these may be arrays into which you can index, but it fundamentally doesn't support arbitrary pointers like wasm does. https://github.com/EmbarkStudios/spirt can lift some uses of untyped memory (rust, wasm, ...) into typed memory (spir-v), but can't lift all of them. Also to make any effective use of a GPU you also need to support work-group local memory and more, which wasm doesn't support.

All you say is right but , it's still possible .
For last one For example we can add option to user set them , if not setted by default 1,1,1 . Or for first the goal is to job be done not how it done

@SkillfulElectro thanks for the issue!
I was involved in some discussions around this in 2020 or so -- and the conclusion then was essentially the same as @bjorn3's points now, that the target is quite different and this would not be an easy adaptation. The use-case in question ended up finding a different way to program GPUs portably.
That discussion was purely about a Cranelift port, but the Wasm runtime as well is an even bigger question mark: what would it mean for Wasmtime to run on a GPU where there is no operating system, (sometimes) no virtual memory, etc.? Or does the Wasm VM get split between GPU and CPU, with (expensive) calls between them?
And then how does one actually take advantage of the parallelism? Do we need a new "vectorized Wasm call" API in Wasmtime? (Keep in mind that a single thread of a GPU has lower performance than a single thread on a CPU; GPUs only make sense when leveraging the SIMT model. And SIMT != SIMD, i.e., the programming model is not the same as what Wasm has exposed for data parallelism.)
What do we do about branch divergence? Do we have estimates or modeling that show this would be reasonably low overhead for typical Wasms?
For all these reasons I'm pretty skeptical. That doesn't mean we should shut down discussion now, at all. What it does mean is that probably there should be a more detailed writeup: what is the use-case, how would all of these high-level design questions be resolved, etc. This should probably take the form of an RFC discussion eventually, but before that, it would help if you could write a bit more about motivation and these other questions here.

@SkillfulElectro thanks for the issue!
I was involved in some discussions around this in 2020 or so -- and the conclusion then was essentially the same as @bjorn3's points now, that the target is quite different and this would not be an easy adaptation. The use-case in question ended up finding a different way to program GPUs portably.
That discussion was purely about a Cranelift port, but the Wasm runtime as well is an even bigger question mark: what would it mean for Wasmtime to run on a GPU where there is no operating system, (sometimes) no virtual memory, etc.? Or does the Wasm VM get split between GPU and CPU, with (expensive) calls between them?
And then how does one actually take advantage of the parallelism? Do we need a new "vectorized Wasm call" API in Wasmtime? (Keep in mind that a single thread of a GPU has lower performance than a single thread on a CPU; GPUs only make sense when leveraging the SIMT model. And SIMT != SIMD, i.e., the programming model is not the same as what Wasm has exposed for data parallelism.)

What do we do about branch divergence? Do we have estimates or modeling that show this would be reasonably low overhead for typical Wasms?
For all these reasons I'm pretty skeptical. That doesn't mean we should shut down discussion now, at all. What it does mean is that probably there should be a more detailed writeup: what is the use-case, how would all of these high-level design questions be resolved, etc. This should probably take the form of an RFC discussion eventually, but before that, it would help if you could write a bit more about motivation and these other questions here.

Well all of his point is correct but look all the languages compile to wasm so if we can run wasm it means we can run all of our ordinary code without touching on GPU . Also what about compiling to wgsl if managing things this way is hard? We just need to add a functionality to user specify number of blocks and workgroups size and compilation needs to be done once so it's cheap price to make simple codes run on GPU and we can reuse that module again without recompiling . For this we can use wgpu and naga

so if we can run wasm it means we can run all of our ordinary code without touching on GPU

Yes, I don't think anyone doubts that having this target would be very useful. The difficult design questions are really the heart of the problem though -- the question is how to map Wasm to the GPU programming abstraction in a way that makes sense and yields speedup. I'd invite you to give your thoughts on any of the questions I wrote out above!
(I'll actually say a little more directly: the way open-source works is that interested parties come in with time and energy and drive interesting new directions or additions to projects. Leaving a comment asking for a very general high-level goal, and then arguing why you want it without driving the engineering, isn't likely to lead anywhere. What I'm trying to steer you toward is driving the design exploration here yourself, in a way that could break the problem down into actionable pieces.)

@cfallin oki so i think first of all why would we need to use GPU? parallel computing . so some of wasm file types cant be compiled to GPU kernel functions which are using WASI or others which are not related to computing , second we create an struct which stores number of blocks in each dim and number of workgroups (threads) in each block , third the wasm function must get index of type int as its first para and an array of supported data types by wgsl as its second para , with this simple rules most of codes which are compiled to wasm can be ran on gpu . now we compile the wasm bytecode to wgsl and pass it to wgpu ( i say wgpu because i am familiar with it ) the index becomes global invocation id and its calculation and data storage arrays or textures becomes input of our array and we pass them to gpu buffer using wgpu buffer also wasm functions which are compiled to run on GPU must not return anything . their returned value must be written on the input arrays
we have multiple GPU devices for example in the server or smth . so we need to add a way to iterate over them by index for choosing prefered device . smth like https://github.com/SkillfulElectro/EMCompute/blob/main/src/gpu_device.rs .

@SkillfulElectro thanks for your reply. I think there needs to be a deeper exploration of the engineering tradeoffs here. I'll go through your points and my questions above to try to help guide you a bit.

first of all why would we need to use GPU? parallel computing

Sure, again, no one is doubting how useful this would be if it were built!

second we create an struct which stores number of blocks in each dim and number of workgroups (threads) in each block , third the wasm function must get index of type int as its first para and an array of supported data types by wgsl as its second para , with this simple rules most of codes which are compiled to wasm can be ran on gpu

This is a very high-level and vague description of a more detailed system design that I think you have in your head. A few followup questions that could help expand it:

What kind of computation is this intended for? Is there one Wasm instance overall, or are there many invocations of a single Wasm instance, and we are taking blocks of them to run as GPU warps? (I suspect the latter, but let's say it explicitly.)
 Wasm in general supports functions of any allowable signature. Are you describing a way to use this parallelized Wasm instance invocation for a certain problem type?
" also wasm functions which are compiled to run on GPU must not return anything" -- as above: a Wasm engine has to be able to support any Wasm module; we can't ship something that only works for a small subset of Wasm, as that wouldn't be Wasm anymore.
"now we compile the wasm bytecode to wgsl and pass it to wgpu" -- this single statement is encapsulating the hardest part, with many many open questions. All of the questions above apply, and we need to argue that we can support all the needed abstractions (Wasm heaps, tables, hostcalls, etc). Not to mention the questions around compiling to the target: register allocation, do we make use of scratchpad memory or not, etc.

At a higher level, I'll repeat the questions I wrote above; we need crisp answers to all of these I think:

Does the Wasmtime runtime itself run on the GPU or the CPU? If the CPU, how do we handle hostcalls? If the GPU, are we convinced that every abstraction Wasmtime needs is available on the GPU, with no operating system underneath it?

Do we have a "vectorized Wasm call" API in Wasmtime? Or some other way to build the parallel invocation (lazy batching or something)?

What do we do about branch divergence?

Given the answers to the above, do we have some early evidence, even napkin math of some sort, that this will yield feasible performance?

@cfallin well you are right wasmtime is just runtime for wasm .

What kind of computation is this intended for? Is there one Wasm instance overall, or are there many invocations of a single Wasm instance, and we are taking blocks of them to run as GPU warps? (I suspect the latter, but let's say it explicitly.)

look what i said is the way to run from these overheads with a few rules . because as long as you know nothing comes free in engineering , so by compiling to wgsl and using wgpu we run away from these overheads so none we need , we will just use wasm code to produce equivalent wgsl code and then we only manage wgpu instances so we only need one instance and one device and queue for each function in wgpu style code

You say "the Wasm function must get index ... and an array of supported data types ...": here you seem to be confusing the Wasm abstraction layer with a higher-level ABI of some sort. Wasm in general supports functions of any allowable signature. Are you describing a way to use this parallelized Wasm instance invocation for a certain problem type?

well like you said , if we do not use SIMD , using GPU threads instead of CPU ones wont be that effective because CPU threads are so much faster so not all the wasm function are good to use on GPU side unless they are capable of . so this is a cost which helps us convert wasm to wgsl or spirv for gpu use

" also wasm functions which are compiled to run on GPU must not return anything" -- as above: a Wasm engine has to be able to support any Wasm module; we can't ship something that only works for a small subset of Wasm, as that wouldn't be Wasm anymore.

well we still could run it on CPU still , i consider what i said as simple rule to make it possible use SIMD on wasm functions to work with them on gpu side

"now we compile the wasm bytecode to wgsl and pass it to wgpu" -- this single statement is encapsulating the hardest part, with many many open questions. All of the questions above apply, and we need to argue that we can support all the needed abstractions (Wasm heaps, tables, hostcalls, etc). Not to mention the questions around compiling to the target: register allocation, do we make use of scratchpad memory or not, etc.

most of these goes away because the only thing we need is answer to our calc , which wgpu takes care of it . btw not all of the functions are meant to be run on GPU

Does the Wasmtime runtime itself run on the GPU or the CPU? If the CPU, how do we handle hostcalls? If the GPU, are we convinced that every abstraction Wasmtime needs is available on the GPU, with no operating system underneath it?

with what i said , wasmtime will be bridge between CPU and wgpu which will handle most it for us

Given the answers to the above, do we have some early evidence, even napkin math of some sort, that this will yield feasible performance?

its based on our function and calc type

Do we have a "vectorized Wasm call" API in Wasmtime? Or some other way to build the parallel invocation (lazy batching or something)?

i dont get this question because of my lack of knowledge

Running Wasm on the GPU sounds neat! However, it is such a different enough environment that you'd really want to tailor the runtime to that specific use case rather than try and bolt on GPU support to an existing runtime that wasn't designed for GPU interaction.
@SkillfulElectro, I encourage you to create a new Wasm runtime that is specifically designed for executing Wasm on the GPU. I think that would be the best way to leverage the GPU's massive parallelism and not end up with a frankenstein monster that both (a) doesn't realize the ideals you're aiming for and (b) becomes a huge maintenance/portability burden. Such a new project would be super cool, and I would be rooting for its success.
However, I don't think it makes sense to bolt Wasm-on-the-GPU support onto Wasmtime, which is definitely not architected for such use cases, and I highly doubt it would hit the goals you've laid out.
Therefore, I'm going to go ahead an close this issue, but folks should feel free to continue discussion and brainstorming here if they find it useful (at least until the dedicated Wasm-on-the-GPU runtime project is kicked off at which point there will be a better forum for these discussions).


"vim-stay could not read the view session file" for new files

This is a regression today after upgrading to 1.4.0 of the plugin.
When opening an existing file that hasn't been opened before, or after clearing your view directory:
vim-stay could not read the view session file! Vim error E484: Can't open file /Users/eapache/.local/share/nvim/view/~=+test=

It doesn't seem to affect functionality, it's just annoying. It's gone subsequent openings of the file once the view file actually exists.
This is in Neovim from Homebrew on OSX:
NVIM v0.3.0
Build type: Release
LuaJIT 2.0.5
Compilation: /usr/local/Homebrew/Library/Homebrew/shims/mac/super/clang -Wconversion -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DNDEBUG -DMIN_LOG_LEVEL=3 -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -I/tmp/neovim-20180612-71518-1f95nfa/neovim-0.3.0/build/config -I/tmp/neovim-20180612-71518-1f95nfa/neovim-0.3.0/src -I/usr/local/include -I/usr/local/opt/gettext/include -I/usr/include -I/tmp/neovim-20180612-71518-1f95nfa/neovim-0.3.0/build/src/nvim/auto -I/tmp/neovim-20180612-71518-1f95nfa/neovim-0.3.0/build/include
Compiled by<EMAIL_ADDRESS>
Features: +acl +iconv +jemalloc +tui

An ad-hoc bisect seems to point the finger at one of 8b9b2f8, aa413be, or 09100db.

Hm. What branch/commit were you on prior to this happening? master (and therefore v1.3.1)? or were you using the release/1.4.0 branch?

Master of the repo under the old owner. I only found out this was maintained again when I got the email for https://github.com/zhimsel/vim-stay/issues/29 closing.

This is the same issue I was having on the release/1.4.0 before I took over maintainership and merged it: https://github.com/zhimsel/vim-stay/issues/31
I'll close that issue as this one is more concise.
@kopischke you mentioned in #31 that you had a fix for that, but you never pushed it... would you be able to send me over a patch? or push it to a branch here?
I'll see if I can fix this in the meantime.

@eapache you can use the hotfix/view-load-error branch for now to suppress the error message until I'm able to fix the root cause.

Bisected it to aa413be, but not really useful I think.
This happens only in Neovim because of this commit: https://github.com/neovim/neovim/commit/9b1c93937 - Vim silently does nothing: https://github.com/vim/vim/blob/947b39e761b8a95cc1bd37ad0c2c30552238809a/src/ex_docmd.c#L11916.
This appears to be a compatibility issue between Neovim/Vim, and I agree with @elmart somethow that this should not be silent, and therefore this patch should also get forwarded to Vim probably.
And in general it would be good to have a function that would return get_view_file, so that vim-stay could easily check if a view file exists, and not try to load it then (which always adds overhead / hooks).

This appears to make sense for now:
diff --git i/autoload/stay/view.vim w/autoload/stay/view.vim
index ff230e9..556afef 100644
--- i/autoload/stay/view.vim
+++ w/autoload/stay/view.vim
@@ -95,7 +95,14 @@ function! stay#view#load(winid) abort
       silent! normal! zOzz
     endif
     return l:did_load_view
-  catch /\vE48[45]/ " no read access to existing view file
+  catch /E484/ " failed to open view file
+    " This happens with no view file on Neovim.
+    if !has('nvim')
+      let v:errmsg  = 'vim-stay could not open the view session file! '
+      let v:errmsg .= 'Vim error '.s:exception2errmsg(v:exception)
+    endif
+    return -1
+  catch /E485/ " no read access to existing view file
     let v:errmsg  = "vim-stay could not read the view session file! "
     let v:errmsg .= "Vim error ".s:exception2errmsg(v:exception)
     return -1

@zhimsel plans on fix this?

@zhimsel Sorry for the delayed response, and doubly sorry for saying I must have hosed that fix at some point; it’s not in my local repo anymore. However, @blueyed’s patch is more or less exactly what I remember implementing, so that should be fine.

And in general it would be good to have a function that would return get_view_file, so that vim-stay could easily check if a view file exists, and not try to load it then (which always adds overhead / hooks).

That would be exceedingly difficult with the current codebase, as vim-stay has zero notion of view session files as such; the whole view session system is Vim’s and stay  just piggybacks on it. This almost total refusal to handle Vim internals is the reason why the plug-in kept working during years of neglect by yours truly, but it also makes some features structurally impossible to implement (the quoted one, or selective deletion of view files as requested in #41 for instance; note I said “almost” because there is a post hoc detection heuristic to ensure events fire properly, but even that is totally agnostic towards the mechanism used by Vim until the view session file is actually loaded).
This being said, I’m not the maintainer anymore and @zhimsel is of course free to ditch both my philosophy in developing stay and the current codebase. That is what handover of maintainership means, after all 😉.

@kopischke
I've meant that get_view_file should be exposed by Vim, so that vim-stay could use it.. :)
It currently supports the current buffer only, but could be changed to handle a buffer name instead maybe (for #41 etc).
Code: https://github.com/vim/vim/blob/947b39e761b8a95cc1bd37ad0c2c30552238809a/src/ex_docmd.c#L11925
Thanks for all your great work! :)

@eapache @blueyed can you take a look at the hotfix/view-load-error branch again? I just pushed @blueyed's patch to it and tested locally. Seems to work fine. If everything works on your ends, I'll add that into master.
@blueyed thanks for that patch! I see what it's doing and it totally makes sense.

Seems to work for me. Thanks!

Ok, great! I'll apply that patch into master shortly.

Hmm, now I'm getting E227: mapping already exists for \d instead. Not sure if it's strictly related to the fix for this or if it's just a different bug that's cropping up on master?

@eapache under what conditions? Opening a file in vim that doesn't have a view file? What version of vim/neovim are you on?
And you're on vim-stay 1.4.1 right?

Yes, same conditions and same neovim build as I originally filed at https://github.com/zhimsel/vim-stay/issues/42#issue-342476395. vim-stay 1.4.1 aka d69f611.

Hm. Okay. Lemme do some testing and get back to you.

@eapache can you test out the hotfix/viewload_nvim_error_2 branch and let me know how that works in your env?

Works properly, thanks!


Update crossterm to v0.24.0

Automated changes by create-pull-request GitHub action

Codecov Report

Merging #31 (bd962e0) into main (7d2895d) will decrease coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #31      +/-   ##
==========================================
- Coverage   86.07%   86.02%   -0.05%
==========================================
  Files          43       43
  Lines        4415     4415
==========================================
- Hits         3800     3798       -2
- Misses        615      617       +2

Impacted Files
Coverage Δ

src/macros.rs
95.42% <0.00%> (-0.66%)
:arrow_down:

src/generic_steps/generic_filter.rs
99.59% <0.00%> (-0.21%)
:arrow_down:

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 7d2895d...bd962e0. Read the comment docs.


Easiest way to use only one or two analyzers?

The CLI seems unreasonably complicated if you only want to use one analyzer for your project (i.e. npm audit).  What is the simplest way to stop the tool from trying to use 10+ analyzers by default?  Is there a way to disable all but one without listing --disable* for each one individually?

I need the OWASP report and integration with Jenkins/Sonar.  There are just a LOT of analyzers that default to enabled.    Is there some type of concise list for a properties file somewhere?

I suppose you could use a properties file and put all the keys in there:
https://github.com/jeremylong/DependencyCheck/blob/6d263594e57c399300cb80bf6000e0b6a5d770e4/utils/src/main/java/org/owasp/dependencycheck/utils/Settings.java#L281


How to distinguish the class 4(transcritical) and class 5(pitchfork)?

Hello,
I downloaded your project and tried to replace the CNN-LSTM with different networks. However, I've found that regardless of the model used, it's quite challenging to accurately distinguish between the fourth category (transcritical) and the fifth category (pitchfork). They always seem to be easily confused. I have removed the higher-order terms that generate the sequence data for these two categories, but it still does not aid in classification. Is there any method that can help the neural network to differentiate between the fourth and fifth categories? Or is this a difficult issue to resolve when using this data?

Hi @RungeKutta4 !
I have also found that class 4 and 5 are the hardest to tell apart for an ML model. The reason is probably that the transcritical and pitchfork bifurcations have identical linear terms in the normal form equations, so differences in the time series will be very slight, and only noticeable very close to the bifurcation. I talk a little more about this in the paper
https://www.nature.com/articles/s41467-023-42020-z
Interesting to hear that you are finding this to be the case with other ML models. I don't know of specific ways to make these classes easier to distinguish - in some cases it might be impossible.

Thank you for your response! I have indeed noticed in your paper the conclusion about the difficulty in classifying the fourth and fifth categories.
I have attempted to use more complex neural network structures to learn deeper features in the data, yet it seems their effectiveness does not surpass that of simple CNN-LSTM or GRU models. I also tried converting the time series into Recurrence Plots and then applying established image classification models for categorization. However, this approach did not seem to enable the network to learn effective features.
It appears indeed challenging for models to clearly distinguish between pitchfork and transcritical bifurcation points. I plan to try introducing attention mechanisms into the model next. Regardless, thank you for your reply!

Great to see that you are pushing this research forward! I hope you find some interesting results.
Recurrence plots as an input is an interesting idea. I think one issue with using only a recurrence plot as input could be that memory in the system beyond one time step back would be erased. I think measures like the autocorrelation at different lag times are important features, that the ML may be picking up on in the time series, which I don't think would be possible with recurrence plots. Maybe multiple recurrence plots with different time separation as input would be interesting.
When comparing the performance of models, you could also consider performance on the binary classification problem, that does not worry about the type of bifurcation, only that there is a bifurcation. I have often thought that EWS might benefit from two classifiers - one that predicts whether or not a bifurcation is approaching, and another that predicts the type of bifurcation.
Good luck!


Add zh_CN locale

Translated via https://lusito.github.io/web-ext-translator/

@yfdyh000  It's released. Thank you.


Remove node_modules from Git

Create a small HTTP server using Express
It should be assigned to the variable app and this one must be exported
HTTP server should listen on port 1245
Displays Hello Holberton School! in the page body for the endpoint /

recreate the small HTTP server using Express:
It should be assigned to the variable app and this one must be exported
HTTP server should listen on port 1245
It should return plain text
When the URL path is /, it should display Hello Holberton School! in the page body


can't scan

running on raspberry pi 400
been using an older image for a long time
maybe a torchvision update broke something for arm devices?
sudo docker exec --user root backend python3 manage.py scan
throws error
/usr/local/lib/python3.10/dist-packages/torchvision/io/image.py:13: UserWarning: Failed to load image Python extension:
  warn(f"Failed to load image Python extension: {e}")

downgraded torchvision on the running "backend"
docker exec -it backend pip install torchvision==0.11.3
full error of sudo docker exec --user root backend python3 manage.py scan
output
/usr/local/lib/python3.10/dist-packages/torchvision/io/image.py:11: UserWarning: Failed to load image Python extension:
  warn(f"Failed to load image Python extension: {e}")
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/dist-packages/django/db/backends/utils.py", line 84, in _execute
use SECRET_KEY from env
    return self.cursor.execute(sql, params)
psycopg2.errors.UniqueViolation: duplicate key value violates unique constraint "api_longrunningjob_pkey"
DETAIL:  Key (id)=(16) already exists.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/code/manage.py", line 11, in <module>
    execute_from_command_line(sys.argv)
  File "/usr/local/lib/python3.10/dist-packages/django/core/management/__init__.py", line 401, in execute_from_command_line
    utility.execute()
  File "/usr/local/lib/python3.10/dist-packages/django/core/management/__init__.py", line 395, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/local/lib/python3.10/dist-packages/django/core/management/base.py", line 330, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/usr/local/lib/python3.10/dist-packages/django/core/management/base.py", line 371, in execute
    output = self.handle(*args, **options)
  File "/code/api/management/commands/scan.py", line 55, in handle
    scan_photos(
  File "/code/api/directory_watcher.py", line 350, in scan_photos
    lrj = LongRunningJob.objects.create(
  File "/usr/local/lib/python3.10/dist-packages/django/db/models/manager.py", line 85, in manager_method
    return getattr(self.get_queryset(), name)(*args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/django/db/models/query.py", line 447, in create
    obj.save(force_insert=True, using=self.db)
  File "/usr/local/lib/python3.10/dist-packages/django/db/models/base.py", line 753, in save
    self.save_base(using=using, force_insert=force_insert,
  File "/usr/local/lib/python3.10/dist-packages/django/db/models/base.py", line 790, in save_base
    updated = self._save_table(
  File "/usr/local/lib/python3.10/dist-packages/django/db/models/base.py", line 895, in _save_table
    results = self._do_insert(cls._base_manager, using, fields, returning_fields, raw)
  File "/usr/local/lib/python3.10/dist-packages/django/db/models/base.py", line 933, in _do_insert
    return manager._insert(
  File "/usr/local/lib/python3.10/dist-packages/django/db/models/manager.py", line 85, in manager_method
    return getattr(self.get_queryset(), name)(*args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/django/db/models/query.py", line 1254, in _insert
    return query.get_compiler(using=using).execute_sql(returning_fields)
  File "/usr/local/lib/python3.10/dist-packages/django/db/models/sql/compiler.py", line 1397, in execute_sql
    cursor.execute(sql, params)
  File "/usr/local/lib/python3.10/dist-packages/django/db/backends/utils.py", line 66, in execute
    return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
  File "/usr/local/lib/python3.10/dist-packages/django/db/backends/utils.py", line 75, in _execute_with_wrappers
    return executor(sql, params, many, context)
  File "/usr/local/lib/python3.10/dist-packages/django/db/backends/utils.py", line 79, in _execute
    with self.db.wrap_database_errors:
  File "/usr/local/lib/python3.10/dist-packages/django/db/utils.py", line 90, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "/usr/local/lib/python3.10/dist-packages/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
django.db.utils.IntegrityError: duplicate key value violates unique constraint "api_longrunningjob_pkey"
DETAIL:  Key (id)=(16) already exists.

i starrted a new db coz off "api_longrunningjob_pkey" Key (id)=(16) already exists error
and
did a docker exec -it backend pip install --upgrade torch together with docker exec -it backend pip install --upgrade torchvision and docker exec -it backend python3 -m pip install --upgrade pip
/usr/local/lib/python3.10/dist-packages/torchvision/io/image.py:13: UserWarning: Failed to load image Python extension:
  warn(f"Failed to load image Python extension: {e}")

persiists
but
scan managed to reach 100% this time
but the job is still unfinished
the "recycle" has not changed in to a "check mark" icon
last lines from backend logs
[2023-01-31 11:20:17 +0000] [146] [CRITICAL] WORKER TIMEOUT (pid:895)
[2023-01-31 11:20:18 +0000] [146] [WARNING] Worker with pid 895 was terminated due to signal 9
[2023-01-31 11:20:18 +0000] [921] [INFO] Booting worker with pid: 921
use SECRET_KEY from env
/usr/local/lib/python3.10/dist-packages/torchvision/io/image.py:13: UserWarning: Failed to load image Python extension:
  warn(f"Failed to load image Python extension: {e}")
<IP_ADDRESS> - - [2023-01-31 11:20:48] "POST /build/ HTTP/1.1" 200 142 4.873032
[2023-01-31 11:20:48 +0000] [146] [CRITICAL] WORKER TIMEOUT (pid:921)
[2023-01-31 11:20:49 +0000] [921] [INFO] Worker exiting (pid: 921)
[2023-01-31 11:20:50 +0000] [146] [WARNING] Worker with pid 921 was terminated due to signal 9
[2023-01-31 11:20:50 +0000] [928] [INFO] Booting worker with pid: 928

It could be that this line here changed: https://github.com/LibrePhotos/librephotos-docker/blob/00d97785992b8417d82489614d187e38b481288c/backend/base/Dockerfile#L61
We need a custom pytorch dependency, because raspberry pis do not support the whole arm instruction set. We solved this issue by using this 3rd party pytorch dependency:  https://github.com/KumaTea/pytorch-aarch64

I changed a couple of things in the base image and in the entrypoint file. It would be great, if you could test, if it works again.

I changed a couple of things in the base image and in the entrypoint file. It would be great, if you could test, if it works again.

Was using 2022w50 hacienda image
scan was completed successfuly with that image
Just updated to latest and I'll wait for my cron to initiate a scan in the morning
I'll report back tomorow
Thanks

From guicron_django.log looks like workers are exiting again due to torchvision
[2023-03-23 17:58:55 +0000] [226] [INFO] Booting worker with pid: 226
use SECRET_KEY from env
/usr/local/lib/python3.10/dist-packages/torchvision/io/image.py:13: UserWarning: Failed to load image Python extension:
  warn(f"Failed to load image Python extension: {e}")
[2023-03-23 17:59:53 +0000] [146] [CRITICAL] WORKER TIMEOUT (pid:226)
[2023-03-23 17:59:54 +0000] [146] [WARNING] Worker with pid 226 was terminated due to signal 9
[2023-03-23 17:59:54 +0000] [252] [INFO] Booting worker with pid: 252
use SECRET_KEY from env
/usr/local/lib/python3.10/dist-packages/torchvision/io/image.py:13: UserWarning: Failed to load image Python extension:
  warn(f"Failed to load image Python extension: {e}")
[2023-03-23 18:00:24 +0000] [146] [CRITICAL] WORKER TIMEOUT (pid:252)
[2023-03-23 18:00:24 +0000] [252] [INFO] Worker exiting (pid: 252)
[2023-03-23 18:00:25 +0000] [146] [WARNING] Worker with pid 252 was terminated due to signal 9
[2023-03-23 18:00:25 +0000] [259] [INFO] Booting worker with pid: 259
use SECRET_KEY from env
/usr/local/lib/python3.10/dist-packages/torchvision/io/image.py:13: UserWarning: Failed to load image Python extension:
  warn(f"Failed to load image Python extension: {e}")
Unauthorized: /api/searchtermexamples/
Unauthorized: /api/albums/place/list/
Unauthorized: /api/persons/
Unauthorized: /api/albums/thing/list/
Unauthorized: /api/albums/user/list/
[2023-03-23 18:03:40 +0000] [146] [CRITICAL] WORKER TIMEOUT (pid:259)
[2023-03-23 18:03:41 +0000] [146] [WARNING] Worker with pid 259 was terminated due to signal 9
[2023-03-23 18:03:41 +0000] [285] [INFO] Booting worker with pid: 285
use SECRET_KEY from env
/usr/local/lib/python3.10/dist-packages/torchvision/io/image.py:13: UserWarning: Failed to load image Python extension:
  warn(f"Failed to load image Python extension: {e}")
[2023-03-23 18:04:40 +0000] [146] [CRITICAL] WORKER TIMEOUT (pid:285)
[2023-03-23 18:04:41 +0000] [146] [WARNING] Worker with pid 285 was terminated due to signal 9
[2023-03-23 18:04:41 +0000] [311] [INFO] Booting worker with pid: 311
use SECRET_KEY from env
/usr/local/lib/python3.10/dist-packages/torchvision/io/image.py:13: UserWarning: Failed to load image Python extension:
  warn(f"Failed to load image Python extension: {e}")
Unauthorized: /api/sitesettings
Unauthorized: /api/rqavailable/
Unauthorized: /api/user/1/
Unauthorized: /api/user/
Unauthorized: /api/searchtermexamples/
Unauthorized: /api/albums/thing/list/
Unauthorized: /api/albums/user/list/
Unauthorized: /api/persons/
Unauthorized: /api/dirtree/
Unauthorized: /api/albums/place/list/
Unauthorized: /api/albums/date/list/
[2023-03-24 07:59:07 +0000] [146] [CRITICAL] WORKER TIMEOUT (pid:311)
[2023-03-24 07:59:08 +0000] [146] [WARNING] Worker with pid 311 was terminated due to signal 9

From the admin page of the web ui I also see that the scan stuck at 95%
The rqworker.log
use SECRET_KEY from env
/usr/local/lib/python3.10/dist-packages/torchvision/io/image.py:13: UserWarning: Failed to load image Python extension:
  warn(f"Failed to load image Python extension: {e}")
17:44:48 Worker rq:worker:ea2e93bb090e4fab9716304800f2d562: started, version 1.10.1
17:44:48 Subscribing to channel rq:pubsub:ea2e93bb090e4fab9716304800f2d562
17:44:48 *** Listening on default...
17:44:48 Cleaning registries for queue: default
17:44:48 default: api.apps.build_index() (37bd72f5-7c2b-44e1-b8a4-1acb7714869f)
18:11:45 default: Job OK (37bd72f5-7c2b-44e1-b8a4-1acb7714869f)
18:11:45 Result is kept for 60 seconds
18:11:45 Cleaning registries for queue: default
18:11:45 default: api.apps.build_index() (1645d968-8ae7-47a2-9ef7-4335a2da84cf)
18:32:38 default: Job OK (1645d968-8ae7-47a2-9ef7-4335a2da84cf)
18:32:38 Result is kept for 60 seconds
18:32:38 Cleaning registries for queue: default
18:32:38 default: api.apps.build_index() (8e557a7f-f65a-4a91-9d21-a1980dda8f20)
18:47:08 default: Job OK (8e557a7f-f65a-4a91-9d21-a1980dda8f20)
18:47:08 Result is kept for 60 seconds
18:47:09 default: api.apps.build_index() (616a193d-3076-430c-a9b3-f89264278a37)
19:07:22 default: Job OK (616a193d-3076-430c-a9b3-f89264278a37)
19:07:22 Result is kept for 60 seconds
19:07:22 Cleaning registries for queue: default
19:07:22 default: api.apps.build_index() (c9b44047-4919-4d5c-b284-7789d9cd5820)
19:23:53 default: Job OK (c9b44047-4919-4d5c-b284-7789d9cd5820)
19:23:53 Result is kept for 60 seconds
19:23:53 Cleaning registries for queue: default
19:23:53 default: api.apps.build_index() (9d296957-6099-4fdd-977d-742448a02699)
19:41:32 default: Job OK (9d296957-6099-4fdd-977d-742448a02699)
19:41:32 Result is kept for 60 seconds
19:41:32 Cleaning registries for queue: default
19:41:32 default: api.apps.build_index() (1c939256-332d-4826-90ef-fd1d35704484)
20:01:57 default: Job OK (1c939256-332d-4826-90ef-fd1d35704484)
20:01:57 Result is kept for 60 seconds
20:01:58 Cleaning registries for queue: default
20:01:58 default: api.apps.build_index() (cc9c0ff6-f1c7-43ec-a79e-004d9855c07d)
20:18:03 default: Job OK (cc9c0ff6-f1c7-43ec-a79e-004d9855c07d)
20:18:03 Result is kept for 60 seconds
20:18:03 Cleaning registries for queue: default
20:45:03 Cleaning registries for queue: default
21:12:03 Cleaning registries for queue: default
21:39:03 Cleaning registries for queue: default
22:06:04 Cleaning registries for queue: default
22:33:04 Cleaning registries for queue: default
23:00:04 Cleaning registries for queue: default
23:27:04 Cleaning registries for queue: default
23:54:05 Cleaning registries for queue: default
23:59:25 default: api.apps.build_index() (d1e31451-b473-463e-b738-db377e4945c0)
00:01:55 Traceback (most recent call last):
  File "/usr/local/lib/python3.10/dist-packages/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
psycopg2.OperationalError: server closed the connection unexpectedly
	This probably means the server terminated abnormally
	before or while processing the request.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/lib/python3.10/dist-packages/rq/worker.py", line 1061, in perform_job
    rv = job.perform()
  File "/usr/local/lib/python3.10/dist-packages/rq/job.py", line 821, in perform
    self._result = self._execute()
  File "/usr/local/lib/python3.10/dist-packages/rq/job.py", line 844, in _execute
    result = self.func(*self.args, **self.kwargs)
  File "/code/api/apps.py", line 19, in build_index
    build_image_similarity_index(user)
  File "/code/api/image_similarity.py", line 78, in build_image_similarity_index
    for photo in paginator.page(page).object_list:
  File "/usr/local/lib/python3.10/dist-packages/django/db/models/query.py", line 287, in __iter__
    self._fetch_all()
  File "/usr/local/lib/python3.10/dist-packages/django/db/models/query.py", line 1308, in _fetch_all
    self._result_cache = list(self._iterable_class(self))
  File "/usr/local/lib/python3.10/dist-packages/django/db/models/query.py", line 53, in __iter__
    results = compiler.execute_sql(chunked_fetch=self.chunked_fetch, chunk_size=self.chunk_size)
  File "/usr/local/lib/python3.10/dist-packages/django/db/models/sql/compiler.py", line 1156, in execute_sql
    cursor.execute(sql, params)
  File "/usr/local/lib/python3.10/dist-packages/django/db/backends/utils.py", line 66, in execute
    return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
  File "/usr/local/lib/python3.10/dist-packages/django/db/backends/utils.py", line 75, in _execute_with_wrappers
    return executor(sql, params, many, context)
  File "/usr/local/lib/python3.10/dist-packages/django/db/backends/utils.py", line 79, in _execute
    with self.db.wrap_database_errors:
  File "/usr/local/lib/python3.10/dist-packages/django/db/utils.py", line 90, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "/usr/local/lib/python3.10/dist-packages/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
django.db.utils.OperationalError: server closed the connection unexpectedly
	This probably means the server terminated abnormally
	before or while processing the request.

Traceback (most recent call last):
  File "/usr/local/lib/python3.10/dist-packages/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
psycopg2.OperationalError: server closed the connection unexpectedly
	This probably means the server terminated abnormally
	before or while processing the request.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/lib/python3.10/dist-packages/rq/worker.py", line 1061, in perform_job
    rv = job.perform()
  File "/usr/local/lib/python3.10/dist-packages/rq/job.py", line 821, in perform
    self._result = self._execute()
  File "/usr/local/lib/python3.10/dist-packages/rq/job.py", line 844, in _execute
    result = self.func(*self.args, **self.kwargs)
  File "/code/api/apps.py", line 19, in build_index
    build_image_similarity_index(user)
  File "/code/api/image_similarity.py", line 78, in build_image_similarity_index
    for photo in paginator.page(page).object_list:
  File "/usr/local/lib/python3.10/dist-packages/django/db/models/query.py", line 287, in __iter__
    self._fetch_all()
  File "/usr/local/lib/python3.10/dist-packages/django/db/models/query.py", line 1308, in _fetch_all
    self._result_cache = list(self._iterable_class(self))
  File "/usr/local/lib/python3.10/dist-packages/django/db/models/query.py", line 53, in __iter__
    results = compiler.execute_sql(chunked_fetch=self.chunked_fetch, chunk_size=self.chunk_size)
  File "/usr/local/lib/python3.10/dist-packages/django/db/models/sql/compiler.py", line 1156, in execute_sql
    cursor.execute(sql, params)
  File "/usr/local/lib/python3.10/dist-packages/django/db/backends/utils.py", line 66, in execute
    return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
  File "/usr/local/lib/python3.10/dist-packages/django/db/backends/utils.py", line 75, in _execute_with_wrappers
    return executor(sql, params, many, context)
  File "/usr/local/lib/python3.10/dist-packages/django/db/backends/utils.py", line 79, in _execute
    with self.db.wrap_database_errors:
  File "/usr/local/lib/python3.10/dist-packages/django/db/utils.py", line 90, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "/usr/local/lib/python3.10/dist-packages/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
django.db.utils.OperationalError: server closed the connection unexpectedly
	This probably means the server terminated abnormally
	before or while processing the request.

00:22:10 Cleaning registries for queue: default
00:49:10 Cleaning registries for queue: default
01:16:10 Cleaning registries for queue: default
01:43:11 Cleaning registries for queue: default
02:10:11 Cleaning registries for queue: default
02:37:11 Cleaning registries for queue: default
03:04:11 Cleaning registries for queue: default
03:31:12 Cleaning registries for queue: default
03:58:12 Cleaning registries for queue: default
04:25:12 Cleaning registries for queue: default
04:52:12 Cleaning registries for queue: default
05:19:13 Cleaning registries for queue: default
05:46:13 Cleaning registries for queue: default
06:13:13 Cleaning registries for queue: default
06:40:13 Cleaning registries for queue: default
07:07:13 Cleaning registries for queue: default
07:34:13 Cleaning registries for queue: default
07:59:33 default: api.apps.build_index() (b165fe1a-a1f8-495f-af7d-64980af66cd2)
08:25:15 default: Job OK (b165fe1a-a1f8-495f-af7d-64980af66cd2)
08:25:15 Result is kept for 60 seconds
08:25:15 Cleaning registries for queue: default
08:25:15 default: api.apps.build_index() (4415b9c6-e52b-4688-9092-063c15c9987d)

The warning is normal and also happens on the normal setup. It looks like it's a timeout issue, similar to how https://github.com/LibrePhotos/librephotos/issues/744#issuecomment-1426794054 described it. Would be great, if you could open a separate issue for it.


Feature/trees api

Description
Added a route handler to server.ts as well as LinktaFlowRoutes.ts and LinktaFlowsController.ts. Tested via Postman to ensure routes are triggering functions. Set up connection to Mongoose ODM.
Fixes #6
Type of change

[ ] 🐛 Bug fix (non-breaking change which fixes an issue)
[x] ✨ New feature (non-breaking change which adds functionality)
[ ] 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] 📝 Documentation update
[ ] Other 🗒 ______________

How Has This Been Tested?

Step 1: console.log return values

Checklist:

[x] I have performed a self-review of my own code.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[x] My changes generate no new warnings.
[ ] Any dependent changes have been merged and published in downstream modules.
[ ] I have reviewed the Security Best Practices Document.
[ ] I have followed the Naming Conventions Guide for my changes.
[x] I have ensured that my pull request title is descriptive.

Additional Information:

Thank you so much @relandboyle


Does enabling the feature prevent third-party cookies from collecting information even when cookies are enabled?

Does enabling the feature limit the collection of information by third-party cookies, even if I do not block cookies? Using the feature doesn't seem to change cookie settings or delete them. So unless I delete it, the tracking still works? If the user does not delete the cookie completely, it is known to be still readable by the tracker. Can you answer me on this?

Hello, can you clarify which feature you are referring to?
On Fri, Mar 31, 2023, 8:30 AM ghkwd @.***> wrote:

Does enabling the feature limit the collection of information by
third-party cookies, even if I do not block cookies? Using the feature
doesn't seem to change cookie settings or delete them. So unless I delete
it, the tracking still works? If the user does not delete the cookie
completely, it is known to be still readable by the tracker. Can you answer
me on this?
—
Reply to this email directly, view it on GitHub
https://github.com/GoogleChromeLabs/privacy-sandbox-dev-support/issues/99,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAQNUYPDI5GLYNHF73IJHLW63E7XANCNFSM6AAAAAAWOS4QVI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hello, can you clarify which feature you are referring to?
…
On Fri, Mar 31, 2023, 8:30 AM ghkwd @.> wrote: Does enabling the feature limit the collection of information by third-party cookies, even if I do not block cookies? Using the feature doesn't seem to change cookie settings or delete them. So unless I delete it, the tracking still works? If the user does not delete the cookie completely, it is known to be still readable by the tracker. Can you answer me on this? — Reply to this email directly, view it on GitHub <#99>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAQNUYPDI5GLYNHF73IJHLW63E7XANCNFSM6AAAAAAWOS4QVI . You are receiving this because you are subscribed to this thread.Message ID: @.>

Assume that you have enabled the Chrome browser's privacy sandbox.

Privacy Sandbox APIs are separate from cookies. While we are in a situation where both the Privacy Sandbox APIs and third-party cookies exist, it's really down to individual sites and their implementations as to how this data is used.


Consts for order status

Currently you have consts for order intent, however nothing for status

@LeafHacker can you please create a PR for this?


[doc] Add a table to map release tags from the compiler to SwiftSyntax.

@swift-ci please test

@akyrtzi Changed. Mind taking another look?

I'm a little confused personally. Does this need to match the version of swift that you're using?

@mdiep That's correct. Swift-syntax relies on compiler (swiftc) to generate syntax trees to deserialize.  For every major releases of Swift, Syntax tree generated from the compiler can vary structurally. So we have to agree on compatible versions so the parser can generate the tree swift-syntax recognizes, and vice versa. If you have any trouble building your tool on top of swift-syntax, please let us know :)


propose alternative derivation mechanism

in sphere-json & sphere-mongo we propose a generic derivation of typeclass instances based on scala macros & core generation.
I experimented using another derivation mechanism based on magnolia: https://github.com/sphereio/sphere-scala-libs/tree/derive_with_magnolia
I could use this new mechanism for sphere-mongo in our private backend.
Using magnolia instead of our own macros is a trade-of decisions:
(+) we can mutualize our efforts with other contributors to have a better derivation mechanism
(+) Magnolia advertises having good compilation time
(+) we could only rely on scala annotations and fix https://github.com/sphereio/sphere-scala-libs/issues/131
(+) less code in this repository
(-) depending on magnolia
(-) less liberty
I personally think that this way is worth a try.
But I'd like to avoid a big-bang release where we move completely from our macros to magnolia.
My proposal:

phase 1: split out the current libraries to extract the current derivation
phase 2: add magnolia as a possible alternative. The 2 derivations mechanisms coexist. It means that we have to duplicate the tests. But this allow to quickly switch which mechanism we want to use
phase 3: depending on the results of phase 2, we could keep only magnolia

For the transition, we have 2 possibilities. For example if someone is using sphere-mongo:

1st possibility: sphere-mongo can be a library depending on sphere-mongo-core & sphere-mongo-macro-derivation.

This change should be transparent for the user.
Users have to switch to sphere-mongo-core & sphere-mongo-magnolia to test in the phase 2.

2nd possibility: we extract the derivation from sphere-mongo into sphere-mongo-macro-derivation.

We don't need any sphere-mongo-core.
Current users have to add this dependency if they rely on the derivation feature.
Users are then aware that we will propose sphere-mongo-magnolia in the phase 2 as an alternative to sphere-mongo-macro-derivation.

I personally think that this way is worth a try.

I share the same opinion, the pros are really attractive 👍
Regarding the transition, I think I prefer the second alternative, i.e without sphere-mongo-core. (Not a strong opinion).

Json4s has a couple of not fixed vulnerabilities: https://github.com/json4s/json4s/issues?utf8=✓&q=is%3Aissue+is%3Aopen+denial
Please consider switching to a more safe parser (and AST, if it will be required) or help json4s maintainers to fix it.

Json4s has a couple of not fixed vulnerabilities: https://github.com/json4s/json4s/issues?utf8=✓&q=is%3Aissue+is%3Aopen+denial
Please consider switching to a more safe parser (and AST, if it will be required) or help json4s maintainers to fix it.

@plokhotnyuk thx for the feedback. This issue is about changing the derivation mechanism for the type classes and is not about the json parser.
I opened an issue for you about this: https://github.com/sphereio/sphere-scala-libs/issues/203


GitHub Actions: add more details for "workflow_run" event

What article on docs.github.com is affected?

https://docs.github.com/en/developers/webhooks-and-events/webhook-events-and-payloads#workflow_run
What part(s) of the article would you like to see updated?
The properties that are exposed on github.event.workflow_run.

From examples on the web I have learned about the existence of
github.event.workflow_run.conclusion
github.event.workflow_run.head_branch
And these are not documented. I expect there to be many more props available. Why don't you guys automate this process and offer generated reference documentation?
Additional information

Another request exists for this which was closed: https://github.com/github/docs/issues/799

Ehrlich gesagt kenne ich mich garnicht wirklich aus in dieser matetie-ich
wollte weder props noch leute kennenletnen-bin aber auf zufall auf etwas
gestossen was ich persöhnlich gut fande,und eben nur mich geäussert
dazu-ich habe dann zu hören bekommen das es niemanden meine meinung
interrissietrt und ich sie nicht áussern soll-und da wurde ich etwas sauer
Maurice Faber<EMAIL_ADDRESS>schrieb am Mi., 10. März 2021,
15:12:

What article on docs.github.com is affected?
https://docs.github.com/en/developers/webhooks-and-events/webhook-events-and-payloads#workflow_run
What part(s) of the article would you like to see updated?
The properties that are exposed on github.event.workflow_run.
From examples on the web I have learned about the existence of
github.event.workflow_run.conclusion
github.event.workflow_run.head_branch
And these are not documented. I expect there to be many more props
available. Why don't you guys automate this process and offer generated
reference documentation?
Additional information
Another request exists for this which was closed: #799
https://github.com/github/docs/issues/799
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/github/docs/issues/4435, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASCGUTYGOU46ZYJ5KG27XPTTC546VANCNFSM4Y6DHY7A
.

Thanks for opening an issue @Morriz! I'll triage this for the team to take a look 👀

@Morriz - Many thanks for raising this issue.
We've just (yesterday) updated the page (https://docs.github.com/en/developers/webhooks-and-events/webhook-events-and-payloads#workflow_run) adding more details for the workflow_run event.
PR: https://github.com/github/docs/pull/2767
I'm going to close this issue.
Thanks again.

Really? After adding this little bit:
Many workflow_run keys, such as head_branch, conclusion, and pull_requests are the same as those in a check_suite object.

you deem this issue closed?

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

https://github.com/behaviorbot/welcome/pull/19#issue-260303297

Since this is a bigger issue of not having reference documentation on topics like this one I started another issue here: https://github.com/github/docs/issues/4612