Make a way to have this install itself after building or something

Like make install but whatever the cmake way is or whatever, idc.

On it.

Done.


Added Vietnamese locale

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
New locale for Vietnamese
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

Coverage increased (+0.01%) to 41.857% when pulling cc319b4b352bb59efaa8313d92b31d8692eda845 on xgenvn:master into c85111a882129a4ed95da66cc685ead178b1b10f on NG-ZORRO:master.

Hi @xgenvn , thanks for your pr, please modify your commit message to follow the guidelines https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit

Hi @vthinkxie, please let me know whether I need to change anything else.
Thanks.

Coverage increased (+0.01%) to 41.857% when pulling 8449af394e3e525eb888ad4396b921495c38908e on xgenvn:master into c85111a882129a4ed95da66cc685ead178b1b10f on NG-ZORRO:master.

Hi @xgenvn ,
this is your commit https://github.com/NG-ZORRO/ng-zorro-antd/pull/589/commits
and this is a valid commit https://github.com/NG-ZORRO/ng-zorro-antd/pull/578/commits
please make the commit format follow the Commit Message Guidelines
and every commit log make sense.


Test to approve action with any 3 space.owners rule

This PR implements a test to approve the action that requires any 3 space owners approval. As of now, there is a bug with persisting action approvals, so this test will fail.

Summary by CodeRabbit

New Features

Introduced a test case for the governance feature within the Warden protocol, validating multi-user approval processes.
Enhanced the testing framework to ensure robustness in the approval mechanism for actions requiring multiple approvals.

the test was added as part of #572, closing this


THEEDGE-2589 Added new status and retry popover on device details

Description

Added new status and retry popover on device details.
Added new props on the popover component to change the position.
Refactored getDevicesStatus for reuse and maintainability.

Fixes # (THEEDGE-2589)
Type of change
What is it?

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update

Checklist:

[ ] 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
[x] New and existing unit tests pass locally with my changes
[x] I run npm run lint:js:fix to check that my code is properly formatted

Depends on https://github.com/RedHatInsights/edge-frontend/pull/533, need to wait until this PR is merged.

Codecov Report
Base: 30.68% // Head: 30.21% // Decreases project coverage by -0.47% :warning:

Coverage data is based on head (7031c28) compared to base (94614d2).
Patch coverage: 8.97% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #548      +/-   ##
==========================================
- Coverage   30.68%   30.21%   -0.48%
==========================================
  Files         125      126       +1
  Lines        2656     2711      +55
  Branches      806      832      +26
==========================================
+ Hits          815      819       +4
- Misses       1689     1731      +42
- Partials      152      161       +9

Impacted Files
Coverage Δ

src/Routes/DeviceDetail/DeviceDetail.js
0.00% <0.00%> (ø)

src/Routes/Repositories/RepositoryTable.js
75.00% <ø> (ø)

src/constants/index.js
84.21% <ø> (ø)

src/constants/status.js
100.00% <ø> (ø)

src/utils/apiWithToast.js
6.66% <0.00%> (-1.03%)
:arrow_down:

src/Routes/Devices/RetryUpdatePopover.js
5.12% <5.12%> (ø)

src/components/Status.js
52.00% <18.18%> (-26.58%)
:arrow_down:

src/Routes/Devices/DeviceTable.js
28.37% <27.27%> (-1.20%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

The breadcrumbs for the system details page are broken:


datadog on minikube

Contribution Type
Tutorial
Description
Install Datadog agent on Minikube via Helm or DaemonSet
Value Add / Motivation
A guided tutorial for beginners who want to try out Datadog with Kubernetes on Minikube

Hi @saphoooo , this seems like something that should go into the https://github.com/DataDog/Miscellany repo. It plays no role in the use of DPN (Datadog Partner Network) sandboxes as far as I can tell.
Would you mind submitting this to the Miscellany repo instead?


Fix security vulnerabilities

Note: npm audit doesn't run clean yet -- we'll need to wait for the next version of coveralls to be released.

@bhaibel ping

@bhaibel Thank you, every contribution is very important to us. 👍


Power Calculator

Before jumping into Pr first comment for assign.
Problem statement :Power Calculator
Probelm Link : https://edabit.com/challenge/wAdE9te55cowBLcPs
Choose one Cateorgy - Very Easy, Easy, Medium, Hard, Very Hard, Expert
question category : Very Easy

Before submitting a PR please Check some details.

[ ] fileName formet should be in camelcase
example- returnTheNextNumber.py
[ ]  Choose label for Problem , example- "good first issue", "easy"
[ ]  In file there should be problem statement and link to problem

/* Problem-Task : This program will calculate power by given voltage and current
 * Problem Link : https://edabit.com/challenge/wAdE9te55cowBLcPs
*/
int main() {
    int bla;
    return 0;
}

This repository is vaild for HacktoberFest2020
Read before making PR - How to contribute on Github
Good Luck,

I would like to solve this problem .Plzz assign me this issue

I would like to work over it.

@ashishrrs  Plzz create your own issue

Assign this work to me!

Please assign this to me

Can you assign me this problem?


Add github link for "Allophant: Cross-lingual Phoneme Recognition with Articulatory Attributes" to README

This PR adds a link to the second GitHub repository for our paper to the README.

Great! Your attention to detail is much appreciated.


Update README to reflect current size

I really like this framework, great job.
However, I showed it to some colleagues and immediately they called bs on 5kb framework size and well technically they are right. It's 7.3kb plus a basically essential 11kb html module for total of 18.3kb. That's hardly something to be ashamed off, in fact it's great, but it's not 5kb as stated.
It's a very minor niggle but hey, we all know how this industry attracts pedants and this framework lost a bit of credibility almost immediately because of this claim.
Sorry to be "that guy", please consider updating README.

If I recall correctly, Yosh measured how much choo represents in a bundled app. And when you bundle it, you'd use unassertify and yo-yoify which significantly reduce the bundle size, not to mention uglify/uglifyify/gzip. You sound be able to reproduce it using a script in the scripts folder. But maybe things have changed with v4, I'll defer to @yoshuawuyts there.

The way I measured was to run build:min which does run both of those transforms and uglify, then I ran the two generated artefacts through gzip so unless there is some other magic involved I think my measurements stand.
Should probably have clarified in the original description so to be clear
choo is currently 18.3kb minified and gzipped

looks like we might have a regression when bundling, gonna dig in and see what's up. If it's anything it's probably browserify's process package being pulled in or something similar (:

Oh, also it's worth noting that the html package should not be included in production; as we mention in the readme for production releases you should strip the runtime compiler with static document.createElement() calls using yo-yoify - this both lowers the resulting bundle size and significantly improves performance.
So yeah, you shouldn't be hitting 18kb in production, like ever

Ah, alright - yeah we made a bit of a regression in terms of size for the 4.x patch - just ran it again on my machine and everything's as expected. It comes in at 6.41kb gzipped. The difference is probably because I'm running zopfli rather than stock gzip which on average saves somewhere around 20% I believe.

For some historical backdrop on why we're past 6kb now - in the 1.x days we were at ~6kb, we dropped to 4.6kb in 2.x because of yo-yoify - but then the addition of our plugin system, more advanced router and event system pushed us back past 6kb again.
We're probably going to shed like another 1-2kb if we'd move on-load out of core (currently included in bel) and replace morphdom with nanomorph. I suspect this might happen in the near future and I don't want to update the file size in the readme every time we patch a dependency in the tree - I'd rather spend my time differently.

On a completely different note: this issue is actually getting to me. The tone of voice, especially the Sorry to be "that guy" remark - it puts me on edge. I get that you wanna be straight forward, and think this helps - but to me it comes off as rude. You highlight one of your findings as fact, and make me feel like I need to reply immediately or else this could spin out of control. I'm not a fan of people dropping into my mentions like that. I'm sure you have no bad intent, but still I'd urge you going forward to consider the humans behind the project and exercising patience before making bold claims. Thanks heaps!

Oh I'm sorry, that was not my intention at all, I wasn't going to raise this at all but then I figured this was literally stopping someone else from looking at this framework which I really like and if it was mine I wouldn't want something so simple to do that.
However I had totally missed the point that the html stuff is supposed to be rewritten anyway. That's really interesting, I will look at it some more. If so that renders this more or less irrelevant feel free to close, sorry to waste your time 👍

@antiBaconMachine all good!
PS I just ran a lil test of what would happen if we adopted nanomorph today and we'd be back at 5.1kb :tada:

The biggest dependency then becomes sheet-router which I'm quite sure we can optimize (:

Think this is quite enough for now tho (: Thanks for opening the issue; we'll keep the file size in mind going forward - perhaps we should also publish the gzip version to the CDN? Anyway, closing :sparkles:


Get arbitrary word using DFS

This PR adds a method to get an arbitrary word accepted by an NFA using DFS. Since we are using a bit vector of searched states, the NFA does not need to be trimmed to prevent cycling in DFS.
This PR resolves #411.

Since the addition of the new method was approved, I will merge the trimmed PR.


Fix typo in the Introduction of the configuration page

** Fixes #9 **

@Caetano-Lopes Thanks for this! I've left you a comment.
Have you reviewed all the documentation? If not, would you be able to change your pull request description to say ** Adds to #9 ** so we still review the other pages.

@Caetano-Lopes Thanks for this! I've left you a comment.
Have you reviewed all the documentation? If not, would you be able to change your pull request description to say ** Adds to #9 ** so we still review the other pages.
Could you also change the pull request to be against the dev branch, as we don't usually accept changes to master.

I reverted what you requested and reviewed all the documents. Check if it helps! Cheers :D

Thanks a lot for your help, hope you get some use out of this package!


Add argument/status checking to methods in Channel class

I found that the methods in Channel were unsafe:

when close is called twice
when receive is called against the closed channel
when deliver is called against the closed channel

Using a status flag ChannelState might look unsophisticated. I'd be glad if someone else have a better idea for this.
But I think the methods are now safer than before, or it might be safer than raw Golang 😆
Well, I'm wondering how to release the ChannelObject when closed.

I think it's ready to merge. Could you do that?


Support async iterable DOM types

Search Terms
asynciterator asynciterable async iterable iterator
Suggestion
Add a dom.asynciterable option to --lib to support DOM types that define a Symbol.asyncIterator method.
Use Cases
The streams spec has recently been updated to add a Symbol.asyncIterator method to ReadableStream, making it the first DOM type to implement the ES2018 AsyncIterable interface.
I would like to update the type definitions for streams in TSJS-lib-generator to include this new async iterator method. However, this requires Symbol.asyncIterator, which is not available before ES2018 and thus cannot be readily used in the DOM type definitions.
Previously, a dom.iterable option was added to support DOM types that define a Symbol.iterator method. I think it would make sense to use this same strategy to support Symbol.asyncIterator.
Examples
TypeScript would have (generated) type definitions in lib/lib.dom.asynciterable.d.ts:
interface ReadableStream<R = any> {
  [Symbol.asyncIterator](): AsyncIterator<R>;
}

Users could then use a ReadableStream in a for await..of loop by compiling with --target es2018:
const readable = new ReadableStream<Uint8Array>();
for await (const chunk of readable) {
  console.log(chunk);
}

Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

Hi, I just stumbled upon this. I noticed forEach was removed from ReadableStream in src/lib/dom.generated.d.ts in 4e237ed66fd1293602aaf5836087ba5d3108c5ea, but async iteration was not added. The ReadableStream in lib/lib.dom.d.ts still has a forEach and no async iteration.
Is there anything I can do to help?

The forEach method was mistakenly added to the ReadableStream type definition. It never existed in the specification nor in any implementation. This was fixed in https://github.com/microsoft/TypeScript-DOM-lib-generator/pull/1134, and should no longer be in lib.dom.d.ts. (Maybe double-check that you're on the latest version of TypeScript?)
At the moment, ReadableStream is not yet marked as an async iterable because it is not implemented by any browser, and thus it does not meet the criteria for being added to the DOM type definitions.

Is there anything I can do to help?

Not a whole lot. You can try to convince Chromium (#929585), Gecko (#1496770) and/or WebKit (#194379) to implement async iteration on ReadableStream, because we need at least two of them to implement it before we can add an official TypeScript type definition. 😅

The forEach method was mistakenly added to the ReadableStream type definition. It never existed in the specification nor in any implementation. This was fixed in microsoft/TypeScript-DOM-lib-generator#1134, and should no longer be in lib.dom.d.ts. (Maybe double-check that you're on the latest version of TypeScript?)

I have a current clone, but the last commit to change that file is from Jul 1, 2021 and forEach is still there:
https://github.com/microsoft/TypeScript/blob/main/lib/lib.dom.d.ts#L11924

At the moment, ReadableStream is not yet marked as an async iterable because it is not implemented by any browser, and thus it does not meet the criteria for being added to the DOM type definitions.

I guess that explains why deno has its own .d.ts :-)

Is there anything I can do to help?

Not a whole lot. You can try to convince Chromium (#929585), Gecko (#1496770) and/or WebKit (#194379) to implement async iteration on ReadableStream, because we need at least two of them to implement it before we can add an official TypeScript type definition. sweat_smile

I would be more likely to try to convince "TSC" of the value of having a deno mode :-)
Thanks for the explanation, the situation makes a lot more sense now.

I have a current clone, but the last commit to change that file is from Jul 1, 2021 and forEach is still there:
https://github.com/microsoft/TypeScript/blob/main/lib/lib.dom.d.ts#L11924

Huh, strange. It looks like TypeScript's main branch is behind the latest v4.5.5 tag (committed on 12 November 2021). Not sure what's going on with that, you'd have to ask the TypeScript team. 😛

Yup, this just bit me. Have to do a weird thing like:
const stream = response.body as unknown as AsyncIterable<ConcreteType>;

Because fetch is already implemented in Node v18+, people stumbling over this will likely be more common.

This is now supported in three runtimes (Node, Deno, and Bun). Can we merge this?

dom.asynciterable generation from the lib side is done in Sept 2022 (thanks Mattias!), we need to add a corresponding option from TypeScript side.

@saschanaz @sandersn lib.dom.asynciterable.d.ts doesn't seem to many of the intended type defs.  I'm confused but in Mattias' PR it only has
interface FileSystemDirectoryHandle {
    [Symbol.asyncIterator](): AsyncIterableIterator<[string, FileSystemHandle]>;
    entries(): AsyncIterableIterator<[string, FileSystemHandle]>;
    keys(): AsyncIterableIterator<string>;
    values(): AsyncIterableIterator<FileSystemHandle>;
}

I can't find ReadableStream[Symbol.asyncIterator]() etc anywhere in TS 5.4.5.  Can we reopen?

That's added later because of browser support state and should be added in a future TS version.

@saschanaz as people have mentioned, this has been supported in many runtimes for over a year, so shouldn't we have a way to opt into these type defs already?

I mean asyncIterable support is already there, what we need is just a new TS release.
ReadableStream.from problem is real and it's still Firefox only. Opting in is not available as we don't have conditional types in TS 😞 and declaration merge is also blocked by web-interfaces-not-being-actual-classes 😭.

As @saschanaz said, it's already in TypeScript Nightly. You can try it in the Playground.

I'm not sure I'm understanding correctly - are the new type defs going to be included in the next release, or are they being delayed until environment support is more widely available?  This was implemented awhile ago so I was assuming it's the latter...
If they're being delayed I just wish TS would officially release some lib def we can opt into (in compilerOptions.lib) now even though environment support is still behind, so we wouldn't have to use a nightly build.


Directory.listSync does not return files

Thank you for taking the time to file an issue!
This tracker is for issues related to:

Dart core libraries ("dart:async", "dart:io", etc.)

SDK:
Dart SDK version: 2.10.3 (stable) (Tue Oct 27 14:44:30 2020 +0100) on "windows_x64"
Running on Google Pixel 4a Android 11 (Flutter)
Issue
While building an application which needs to be able to browse through local files. I think I stumped on a bug. The Direcotry.listSync (and also the Directory.list) methods do not return any files.
I have checked, there are files in the Download folder and I have tried in other directories as well.
Directories are listed, but files are not.
Steps to Reproduce
import 'dart:io';

import 'package:flutter/material.dart';

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

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    final files = Directory('/storage/emulated/0/Download').listSync();
    print(files);
    return MaterialApp(
      home: Scaffold(
        body: ListView.builder(
          itemCount: files.length,
          itemBuilder: (context, i) => Text(files[i].path),
        ),
      ),
    );
  }
}

Related issue on flutter github:
https://github.com/flutter/flutter/issues/75268

Scoped storage enabled in Android 11

Are you able to open any of the files you know are in the directory by their absolute path?

No, I get a FileSystemException
Code:
import 'dart:io';

void main() {
  final file = File('/storage/emulated/0/Documents/test.txt');
  print(file.readAsStringSync());
}

Exception:
Unhandled exception:
FileSystemException: Cannot open file, path = '/storage/emulated/0/Documents/test.txt' (OS Error: The system cannot find the path specified.
, errno = 3)
#0      _File.throwIfError (dart:io/file_impl.dart:635:7)
#1      _File.openSync (dart:io/file_impl.dart:479:5)
#2      _File.readAsBytesSync (dart:io/file_impl.dart:539:18)
#3      _File.readAsStringSync (dart:io/file_impl.dart:584:18)
#4      main (file:///C:/Users/wvl/source/repos/FileX/tool/main.dart:11:14)
#5      _startIsolate.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:299:32)
#6      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:168:12)

The file does exist though:

PS: this does work when I try it in on windows in terminal:
➜  tool git:(master) ✗ dart .\main.dart ./main.dart
import 'dart:io';

void main(List<String> args) {
  File file;
  if (args?.isNotEmpty != true) {
    file = File('/storage/emulated/0/Documents/test.txt');
  } else {
    file = File(args[0]);
  }

  print(file.readAsStringSync());
}

You're getting a permission denied error for the file, not that it doesn't exist. It seems more probable that your app permissions are somehow wrong rather than Flutter/Dart being this broken? I don't know much about Flutter and Android permissions though, so I am not quite able to help you. Note that you may have a different set of app permissions if you're using a debug version of your app.

Well, as you can see in the image, all file permissions are accepted. I have added all storage permissions to the AndroidManifest:
    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
    <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>
    <uses-permission android:name="android.permission.MANAGE_EXTERNAL_STORAGE"
        tools:ignore="ScopedStorage" />

If this is not the place to ask this question and the flutter repo isn't either, where should I post it?

(Ah, not saying this is the wrong place to ask the question, just that I'm not the right person to triage this issue. I'm not currently responsible for the component in question, I was just dropping in with some drive by comments in case it's helpful.)

I don't think you can read files in Download directory like this in recent versions of Android, this has been restricted. See warning at Environment.getExternalStoragePublicDirectory. You need to use one of the suggested alternatives (some of them have corresponding flutter plugins, e.g. https://pub.dev/packages/flutter_document_picker).

I have the same problem, if I rename the file to png / jpeg / pdf / ... then it appears in the list.
...

in android 11 and above the permission to the storage is limited by default to read media files only
in order to have access to all files you need to go to your device settings
Settings > Privacy > Permission manager > Files and media
and select your app and click
Allowed for all files
don't forget to set permission tags in your AndroidManifest.xml file

Same error on Android 11  (Pixel 3a):

Code implemented:

List<StorageInfo> storageInfo = await PathProviderEx.getStorageInfo();
    var root = storageInfo[0].rootDir;
    var fm = FileManager(root: Directory(root));
    final files = await fm.filesTree(excludedPaths: ["/storage/emulated/0/Android"], extensions: ["png"]);

The error:

FileSystemException: Directory listing failed, path = '/storage/emulated/0/Android/obb' (OS Error: Permission denied, errno = 13

As I debugged, the checking excludedPaths != null is performed after var contents = root.listSync(recursive: true, followLinks: followLinks);:
Future<List<Directory>> dirsTree(
      {List<String> excludedPaths,
      bool followLinks: false,
      bool excludeHidden: false,
      FileManagerSorting sortedBy}) async {
    List<Directory> dirs = [];

    try {
      var contents = root.listSync(recursive: true, followLinks: followLinks);
      if (excludedPaths != null) {
....

in android 11 and above the permission to the storage is limited by default to read media files only in order to have access to all files you need to go to your device settings Settings > Privacy > Permission manager > Files and media and select your app and click Allowed for all files
don't forget to set permission tags in your AndroidManifest.xml file
for more info: https://developer.android.com/about/versions/11/privacy/storage

This one worked for me. Thanks @ABDERRAHMANE-OUALI .

For android 11 plus, there is a security update. If you are using flutter's permission_handler package and you want to access files in the android filesystem, then you have to use "manageExternalStorage" instead of "storage" type of the Permission class. It's all about security.
to be clear, do this:
await Permission.manageExternalStorage.request()
instead of:
await Permission.storage.request().
Here is a code sample.
var permission = await Permission.manageExternalStorage.status;   List<String> files = [];   if (permission.isDenied) {     debugPrint("Permission is denied");     await Permission.manageExternalStorage.request();   }   if (permission.isGranted) {     Directory directory = Directory('/storage/emulated/0/Documents'); Do something     }.
Remember "manageExternalStorage" replaces "storage" if you want to access the filesystem.
If this helps you, remember to mark it as answer. Dart isn't the problem, you aren't asking the permissions correctly. I did it too.

@PatrickOjiambo
I don't think this is the answer. Google restrict the use of MANAGE_EXTERNAL_STORAGE to apps like virus scanners, file managers etc. Apps that need broad access to all files without user interaction. I am building a cloud-based file storage app and they have questioned why I need it. They argue that I should be able to import/export files with user interaction and by using the existing Scoped Access APIs, so you may have problems getting your app approved if you try to use that permission. I am still looking for a solution however for Android 12 and above where I need to read access to the files in a chosen directory. Perhaps https://pub.dev/packages/flutter_document_picker is the answer.


Placeholders in @EnableFeignClients annotation couldn't be resolved

Good day !
Currently I have need to specify base packages in @EnableFeignClients annotation using spring placeholders, that it should automatically resolve. But I've been a little bit confused when those placeholder haven't been resolved properly.
I've got a deep dive into this problem and have discovered further facts:

client registration is performed using org.springframework.cloud.netflix.feign.FeignClientsRegistrar

scanning for the feign clients is performed using bean, that is constructed using getScanner() method, which returns an anonymous impl of the ClassPathScanningCandidateComponentProvider,  which have been constructed using further constructor ClassPathScanningCandidateComponentProvider(boolean useDefaultFilters)

this constructor reduces the scope of the available properties (it creates new StandardEnvironment(), instead of using Environment from context), and scanner operates only using system properties, and ignores user defined properties, that breaks resolving process

For this reason my placeholder couldn't be resolved, could you please explain, is this a proper behaviour, or maybe you know any workarounds to solve my pain ))
The version of the spring-cloud-starter-feign is provided by version of spring-cloud-bom (Brixton.SR6)
Thx !

I think the solution here is to make FeignClientsRegistrar implement EnvironmentAware.  I will try to take a look at this today and see if I can come up with a reproducible scenario and a fix.


Include sqlpp11/sqlite3/sqlite3.h (tag 0.63) got compile error

Hi, I compiled my program including "sqlpp11/sqlite3/sqlite3.h" with sqlpp11 0.63, -std=c++11, gcc version 4.8.5 on CentOs 7.3
I got compile error:
error: function 'sqlpp::sqlite3::connection& sqlpp::sqlite3::connection::operator=(sqlpp::sqlite3::connection&&)' defaulted on its first declaration with an exception-specification that differs from the implicit declaration 'sqlpp::sqlite3::connection& sqlpp::sqlite3::connection::operator=(sqlpp::sqlite3::connection&&)'
       connection& operator=(connection&&) noexcept = default;

The compiler can not generated defaulted noexcept move assignement operator for sqlpp::sqlite3::connection
(https://stackoverflow.com/questions/47032077/noexcept-default-compilation-error)
Is this caused by the member data _handle's move assignment operator having no noexcept specifer?
PS, I compiled successfully after manually removing the noexcept specifer at /sqlpp11/sqlite3/connection.h:307

Indeed the MySQL and SQLite3 connectors in v0.63 have
connection& connection::operator=(connection&&) noexcept = default;

What is interesting, the PostgreSQL connector in v0.63 does not have noexcept = default in the declaration of the assignment operator.
After the connection pool code has been merged, a large part of the connectors' code has been unified so in the latest development version no connector has noexcept = default in its code. So instead of manually editing the connector code, you could try the latest dev. version and see if it will build and work for you.
However the fact that it noexcept = default fails to build seems to be a bug/limitation of gcc 4.8.5. I think that it probably makes more sense just to upgrade your gcc - on Fedora the latest gcc is 13.1.1, so 4.8.5 seems to be a really old one that probably has multiple other bugs too. It seems that you are installing sqlpp11 on your dev machine as it makes no sense to install sqlpp11 on a production machine. So you have several options:

Upgrade your gcc.
Upgrade to the latest development version of sqlpp11.
Manually modify the source code by removing the noexcept specifier and use the modified version.

Hi, @MeanSquaredError
Thank you very much for your reply to remind it could be gcc 4.8.5 bug. For some reason, I can not upgrade compiler now. I saw your connection pool commit on 7/17. We will wait for next tag or manually modify 0.63 to fit current environment before new release.
Thanks!

Closing as 0.64 has been released for a while now.


License?

Mind adding a license to this repo? I'm exploring firecracker a bit and interested in the code & configs you've created here, but don't want to start deriving my own configs from it unless the license allows for it. Many thanks in advance

Fixed in 8057b44

Fixed in 8057b44


added getUserById

Coverage decreased (-0.06%) to 84.187% when pulling a2813a94c8d77cc2dd44875d22b6df2bd86cdc53 on ljbergmann:master into 6171b99ec10e7dd9822b057667ba3180779158a4 on Alpha-Trader:master.


Support reading Iceberg split with equality deletes

This commit introduces EqualityDeleteFileReader, which is used to read Iceberg splits with equality delete files.

Closing in favor of https://github.com/facebookincubator/velox/pull/11088


brainrender-gui does not display anything and throws errors in the console

Describe the bug
brainrender-gui does not display anything and throws the following errors in the console:

This is how the GUI looks:

To Reproduce
brainrender v: <IP_ADDRESS>
vedo v: 2021.0.5
python v: 3.7.16
anaconda v: custom
OS: Widnows 10
Then tell us the steps to reproduce the behavior:
type brainrender-gui at the terminal
Expected behavior
Nothing displays in the brainrender GUI and when you close it, the above error messages show up.
Screenshots
Added these in the problem description

Any update about this? I got the same error.

seems to be the same issue as: https://github.com/brainglobe/brainrender/issues/183

No, I tried pip install PyQt5. It did not fix the error:

Here is my installation and initiation procedure:
conda create -n brainrender python=3.8
conda activate brainrender
pip install -U git+https://github.com/brainglobe/brainrender.git
pip install PySide2
pip install PyQt5
brainrender-gui

Closing as this is a duplicate of #286 and the brainrender GUI will be removed in the next release, in favour of brainrender-napari.


Refactor chat_generate

Description

I create ERROR_ERRORS_TO_MESSAGES to make the error handling clearer for _throttled_openai_completion_acreate and _throttled_openai_chat_completion_acreate.
There is no TimeoutError in openai.error, so I delete it.
I add a new parameter n for both completion, which is the number of responses to generate for each API call.

References

https://github.com/zeno-ml/zeno-build/issues/169
https://platform.openai.com/docs/api-reference/chat/create

Blocked by

This one works fine. Sorry for the previous one. I don't know why it's so strange.

Hey @neubig and @cabreraalex, sorry for reopening this. I failed several times for the pre-commit, then I uninstall all the environments for my local Python 3.11.3 and use 3.9.17. It seems to work out. 🤔

Thanks so much for your help and advise for this PR and issue #169!

Thanks @zhaochenyang20 , this looks great! There is just one small change request. I used Github's suggestion functionality, so you should just be able to click "accept suggestion".
And sorry about the trouble with the isort stuff, I'm not sure what was causing that

Done! The other part is just fine. I don't know what causes this strange behavior of isort either. 🤷🏻♀

Great, merged. Thanks for the contribution!


script-must-have-extension gets confused if path contains a dot

Both script-must-have-extension and script-must-not-have-extension fail on files that don't have an extension but do have a dot in the path leading up to them.  Here are some pathological examples:
my_dir/.foo/executable_script  # script-must-not-have-extension complains
my_dir/.foo/non_executable_script  # script-must-have-extension does not complain
Scripts that begin with a dot are also problematic.  For example: my_dir/.script

Thanks, Dan, for reporting this!
I've created https://github.com/jumanjihouse/pre-commit-hooks/pull/54 to fix this.
It works for me, including fixtures that match the path names you provided, so I'm going to merge the PR.
If you run into any other corner cases, please reopen this (or a new issue if it won't let you reopen).
Thanks again,
-paul

ps. the fix is in tag 2.0.2
https://github.com/jumanjihouse/pre-commit-hooks/releases/tag/2.0.2

@jumanjiman Thank you for fixing this so quickly!


Excessive "unable to read golang buildinfo error=not a Go executable file" warnings in versions after v0.62.1

Please provide a set of steps on how to reproduce the issue
I'm not sure to be honest, we see this against every container image we build, and have locked the sfyt version to 0.62.1 now as the mass warnings were annoying developers, it doesn't seem to affect the eventual output of the tool from what I can tell.  It could be something specific in our baseimage that syft fundamentally doesn't like I guess, but it seems like a problem in syft in that it's expecting everything it finds to be a go executable.
What happened:
In 0.62.3 there are over 2000 lines of warnings generated (unable to read golang buildinfo error / golang cataloger: bin parsing: number of builds and readers doesn't match)
[0000]  INFO syft version: 0.62.3
[0011]  INFO identified distro: Red Hat Enterprise Linux 8.7 (Ootpa)
[0011]  INFO cataloging image
[0017]  WARN unable to read golang buildinfo error=not a Go executable file=/usr/bin/bash
[0017]  WARN golang cataloger: bin parsing: number of builds and readers doesn't match
[0017]  WARN unable to read golang buildinfo error=not a Go executable file=/usr/bin/brotli
[0017]  WARN golang cataloger: bin parsing: number of builds and readers doesn't match
[0017]  WARN unable to read golang buildinfo error=not a Go executable file=/usr/bin/busctl
[0017]  WARN golang cataloger: bin parsing: number of builds and readers doesn't match
<snip ... another 2000 lines of the same 2 warnings for various files>

In 0.63 it's the same, with over 2k warnings when scanning the container image:
[0000]  INFO syft version: 0.63.0
[0012]  INFO identified distro: Red Hat Enterprise Linux 8.7 (Ootpa)
[0012]  INFO cataloging image
[0019]  WARN unable to read golang buildinfo error=not a Go executable file=/usr/bin/python3
[0019]  WARN golang cataloger: bin parsing: number of builds and readers doesn't match
[0019]  WARN unable to read golang buildinfo error=not a Go executable file=/usr/share/filebeat/bin/filebeat-god
[0019]  WARN golang cataloger: bin parsing: number of builds and readers doesn't match
[0019]  WARN unable to read golang buildinfo error=not a Go executable file=/usr/local/lib/python3.9/site-packages/clidriver/bin/db2cli
[0019]  WARN golang cataloger: bin parsing: number of builds and readers doesn't match
[0019]  WARN unable to read golang buildinfo error=not a Go executable file=/usr/local/lib/python3.9/site-packages/clidriver/bin/db2diag
[0019]  WARN golang cataloger: bin parsing: number of builds and readers doesn't match
[0019]  WARN unable to read golang buildinfo error=not a Go executable file=/usr/local/lib/python3.9/site-packages/clidriver/bin/db2drdat
[0019]  WARN golang cataloger: bin parsing: number of builds and readers doesn't match
<snip ... another 2000 lines of the same 2 warnings for various files>

What you expected to happen:
Exact same image, using 0.62.1 throws a couple of info messages only (this is the complete output)...
[0000]  INFO syft version: 0.62.1
[0010]  INFO identified distro: Red Hat Enterprise Linux 8.7 (Ootpa)
[0010]  INFO cataloging image
[0016]  INFO golang cataloger: unable to read buildinfo (file="/usr/local/lib/python3.9/site-packages/cassandra/io/libevwrapper.cpython-39-x86_64-linux-gnu.so"): EOF
[0016]  INFO golang cataloger: unable to read buildinfo (file="/usr/local/lib/python3.9/site-packages/cassandra_driver.libs/libev-aea52ade.so.4.0.0"): EOF
[0016]  INFO golang cataloger: unable to read buildinfo (file="/usr/local/lib/python3.9/site-packages/confluent_kafka.libs/librdkafka-ab776cb1.so.1"): EOF
[0016]  INFO golang cataloger: unable to read buildinfo (file="/usr/local/lib/python3.9/site-packages/confluent_kafka/cimpl.cpython-39-x86_64-linux-gnu.so"): EOF

Anything else we need to know?: I don't think so
Environment:

Output of syft version:

syft version
Application:        syft
Version:            0.63.0
JsonSchemaVersion:  6.0.0
BuildDate:          2022-12-12T21:03:41Z
GitCommit:          23a3173c9f2461e5906d1b9e3ac20b4806d74777
GitDescription:     v0.63.0
Platform:           linux/amd64
GoVersion:          go1.18.8
Compiler:           gc

OS (e.g: cat /etc/os-release or similar): This is when running on a Travis build engine (dist: bionic), but we see the same thing running syft locally too.

I'm seeing this aswell same issue

Hi and thanks for this report! Is there any public image you could reference that this happens with?

I was unable to find a public example of this however I have a feeling it is in relation to multi stage builds and scratch images.

Adding context from @wagoodman on https://github.com/anchore/grype/issues/1039:

I agree the log output should not appear. The issue is here https://github.com/anchore/syft/blob/main/syft/pkg/cataloger/golang/scan_binary.go where we're making the assumption that any binary passed in is a go binary, however, that is not always the case since we select files by MIME type.
We should probably change the execution path to return an error and ignore the error in the context of the go binary cataloger.


Can't turn off animation looping

Some of the animations don't need to loop. SLASH for example.
If I turn off looping on that animation the plugin just turns it back on again.

Ok, I'll look into that!

Update to make the default animation for other than walk to not loop. Se if it helps you!

Thanks for the quick response. That seems to have fixed the looping.


Will I need a graphical environment and chrome to run on vps/vds?

xvfb

It does, but it can be ran in a virtual graphical environment, such as xvfb as acheong08 mentioned above. To run the program with xvfb vge sandbox, run:
xvfb-run python proxy.py
In my Pull Request there's an implementation as a configurable option "virtualdisplay" which provides an integrated ability to automatically create a virtual graphical environment for that.

Thanks guys


Improve docs

Improve docs. Resolves #87.

Created #93 to start keeping previous expected images (and update the documentation to reflect this).


Not working with latest version of @vue/tsconfig version 0.4.0

Hi,
Thanks for this excelent tutorial, unfortunately is not working with the version 0.4.0 of vue tsconfig and node 18.13.0.
Basically is not working with extendind tsconfig.dom.json. Do you have any idea about how it should be configured?
Thanks,
Radu

Check your typescript version.
When you're using typescript >5.0 you should use<EMAIL_ADDRESS>See:
https://github.com/vuejs/tsconfig/blob/v0.4.0/README.md


Postprocessing: check_if_csv_dirs_equal() fails

Functions fails on files named oemoflex.log.2020-03-18 with a cryptic error. It should better say "no csv file"
Traceback (most recent call last):
  File "/home/unndreay/Workspaces/oemo-flex/experiment_1/scripts/FlexMex1_10/FlexMex1_10_postprocessing.py", line 310, in <module>
    main()
  File "/home/unndreay/Workspaces/oemo-flex/experiment_1/scripts/FlexMex1_10/FlexMex1_10_postprocessing.py", line 301, in main
    check_if_csv_dirs_equal(new_results_path, previous_results_path)
  File "/home/unndreay/Workspaces/oemo-flex/oemoflex/helpers.py", line 80, in check_if_csv_dirs_equal
    check_if_csv_files_equal(file_a, file_b)
  File "/home/unndreay/Workspaces/oemo-flex/oemoflex/helpers.py", line 58, in check_if_csv_files_equal
    df1 = pd.read_csv(csv_file_a)
  File "/home/unndreay/.virtualenvs/oemo-flex/lib/python3.7/site-packages/pandas/io/parsers.py", line 676, in parser_f
    return _read(filepath_or_buffer, kwds)
  File "/home/unndreay/.virtualenvs/oemo-flex/lib/python3.7/site-packages/pandas/io/parsers.py", line 454, in _read
    data = parser.read(nrows)
  File "/home/unndreay/.virtualenvs/oemo-flex/lib/python3.7/site-packages/pandas/io/parsers.py", line 1133, in read
    ret = self._engine.read(nrows)
  File "/home/unndreay/.virtualenvs/oemo-flex/lib/python3.7/site-packages/pandas/io/parsers.py", line 2037, in read
    data = self._reader.read(nrows)
  File "pandas/_libs/parsers.pyx", line 860, in pandas._libs.parsers.TextReader.read
  File "pandas/_libs/parsers.pyx", line 875, in pandas._libs.parsers.TextReader._read_low_memory
  File "pandas/_libs/parsers.pyx", line 929, in pandas._libs.parsers.TextReader._read_rows
  File "pandas/_libs/parsers.pyx", line 916, in pandas._libs.parsers.TextReader._tokenize_rows
  File "pandas/_libs/parsers.pyx", line 2071, in pandas._libs.parsers.raise_parser_error
pandas.errors.ParserError: Error tokenizing data. C error: Expected 2 fields in line 7, saw 4

The problem seems to be that the logfile is not ignored by the function, as it should. These lines here check for the end of the filename, however the logfiles names are appended with dates for older runs, which is why they are not ignored any more:
https://github.com/modex-flexmex/oemo-flex/blob/5e6529670fc454c0fee9aadf68297fa2fe71d6a1/oemoflex/helpers.py#L64-L65
Adapting the string check could help. Or restricting the method to only csv-files, abandoning the option to ignore specific file formats.


Some questions about future plans for RLSL

I've already professed my excitement for RLSL in #40, but here I'd like to get a stronger idea about the kind of future you envisage for the project and the ways in which it might be able to inter-operate with regular Rust code.
Also, I apologise ahead of time if any of the following questions seem silly - I'm still new to SPIR-V and have a very limited understanding of what's possible and what is not!
cargo
In the README you mention that one of the goals is to support cargo - could you elaborate on your plans for this? In particular, I'm curious where the boundaries lie. For example, could I write a crate that may be depended upon downstream by both RLSL and rust code? I can imagine it would be particularly useful to be able to use a math crate (something like cgmath) both in regular cpu code and in RLSL.
Further, is it necessary to have separate, specific files for RLSL code? E.g. could I one day write my RLSL shaders within my regular .rs rust modules, perhaps using a decorator of some sort to indicate entry/exit points?
compute shaders
I would love to be able to use something like RLSL for doing general compute - is this something you would like to see at some point?
I think one of the things I love about the idea of RLSL is the reduction of friction between programming for the CPU and programming for the GPU. I've had a dream for a little while that one day we might be able to do something like pass a closure to a function which executes the closure in parallel on the GPU, returning either a Future or the result directly. I realise it is not possible to execute arbitrary Rust code on the GPU, but perhaps there would be some way to constrain the kinds of functions that could be executed on the GPU using a trait of some sort that extended Fn? I guess a similar/easier alternative might be to pass an instance of some type that implements some GpuFn trait?
RLSL & Rust
I wonder if at some point down the track yourself and the rust-lang team might be interested in including (lower tier) support for something like RLSL out of the box, treating SPIR-V as an alternative target to LLVM or something along these lines? I realise I'm getting way ahead of myself here, but it can be fun to theorize and plant seeds :)
Anyway, thanks again for all your work on this - looking forward to watching (and hopefully taking-part-in one day) RLSL progress!

I can imagine it would be particularly useful to be able to use a math crate (something like cgmath) both in regular cpu code and in RLSL.

Yes that will be possible, but I currently only work on my own math library. I still need a nice way to map specific intrinsic types in external math libs. It is a bit awkward at the moment and relies on custom attributes. The rlsl-math library btw is also just an external library, and can be used as an example.

Further, is it necessary to have separate, specific files for RLSL code? E.g. could I one day write my RLSL shaders within my regular .rs rust modules, perhaps using a decorator of some sort to indicate entry/exit points?

No rlsl is basically is just Rust and only the entry points are sort of custom. As you mention you just annotate some function with fragment, vertex, compute etc. At the moment you can only define entry points in non lib files. For example in files that are in the /bin folder. Every entry point in the same file will included in the same spirv module.

I think one of the things I love about the idea of RLSL is the reduction of friction between programming for the CPU and programming for the GPU. I've had a dream for a little while that one day we might be able to do something like pass a closure to a function which executes the closure in parallel on the GPU, returning either a Future or the result directly. I realise it is not possible to execute arbitrary Rust code on the GPU, but perhaps there would be some way to constrain the kinds of functions that could be executed on the GPU using a trait of some sort that extended Fn? I guess a similar/easier alternative might be to pass an instance of some type that implements some GpuFn trait?

I don't see why this wouldn't be possible. You probably want to compile the "closure" ahead of time though, maybe in some kind of proc macro/custom derive and then just execute the spv file at runtime. I actually want to do something super similar in my test suit. It is kind of hacky at the moment but you can look at https://github.com/MaikKlein/rlsl/blob/master/rlsl-test/src/lib.rs#L240-L256
    quickcheck! {
        fn compute_u32_add(input: Vec<f32>) -> TestResult {
            compute("compute", input, "../.shaders/u32-add.spv", issues::u32_add)
        }
        fn compute_square(input: Vec<f32>) -> TestResult {
            compute("compute", input, "../.shaders/square.spv", issues::square)
        }

        fn compute_single_branch(input: Vec<f32>) -> TestResult {
            compute("compute", input, "../.shaders/single-branch.spv", issues::single_branch)
        }

        fn compute_single_branch_glsl(input: Vec<f32>) -> TestResult {
            compute("main", input, "../issues/.shaders-glsl/single-branch.spv", issues::single_branch)
        }
}

And the .spv files are generated from rlsl, like https://github.com/MaikKlein/rlsl/blob/master/issues/src/bin/square.rs
Essentially I execute the same function on the cpu/gpu and compare the results. It is a bit awkward at the moment.  I'll do this manually at the moment, but I'll definitely going to automate this soon.

I wonder if at some point down the track yourself and the rust-lang team might be interested in including (lower tier) support for something like RLSL out of the box, treating SPIR-V as an alternative target to LLVM or something along these lines? I realise I'm getting way ahead of myself here, but it can be fun to theorize and plant seeds :)

I definitely would be open to it, but I haven't contacted anyone so far.


Incompatible CLI options for VS 2019 Debug build

🐛 Bug Report

When building in Visual Studio 2019 in Debug mode I get this error:

Only happens in Debug build; Release, MinSizeRel, RelWithDebInfo build fine
Expected Behavior
The project should build fine
Current Behavior
The project did not build :(
Possible Solution
There's this: https://stackoverflow.com/a/44416270
But having /O2 for a debug build seems incorrect. Also had an issue with CLion+Linux where Debug build skipped breakpoints, which can be proof of incorrect configuration.
Steps to Reproduce

git clone https://github.com/metacall/core.git
install VS 2019
mkdir build
cd build
cmake ..
Hit Local Windows Debugger here

Context (Environment)
I was trying to build the project

Opened with wrong account oops


⚠ Minecraft has degraded performance

In 3d620d6, Minecraft (https://www.minecraft.net) experienced degraded performance:

HTTP code: 200
Response time: 1167 ms

Resolved: Minecraft performance has improved in 1ccb916.


auto-create yaml file for model in repo

Added YAML IO to cobrapy. The cookiecutter-memote now has a git pre-commit hook that creates a YAML on every commit.


Add documentation on how to run/investigate e2e tests

What
I would like to add a document on how to:

~run the e2e tests, particularly how to run specific tests~ (I see this is explained here)
keep the test namespace around for investigating failures
accessing the rabbitmq profiling dashboard

Why
I was running the e2e tests recently, and I had trouble finding out how to debug a failure. I only got "unstuck" by some direct conversation on Slack. I think it would be helpful to have this information more visible.

I thought about this some more, and I think the things I want documented are a pretty specific to my problem.
keeping a test namespace around for investigating is only specific to the e2e tests that have a finish step
And the rabbitmq profiling dashboard might not be as useful on tests that you can't as easily keep around


[Enhancement] Remove internal_service_async_thread_num

Why I'm doing:
What I'm doing:
This PR removes the _async_thread_pool limitation. With the new implementation, the size of the thread pool _async_thread_pool is determined by the number of simultaneous tasks submitted by the FE.
Fixes #issue
What type of PR is this:

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

Does this PR entail a change in behavior?

[x] Yes, this PR will result in a change in behavior.
[ ] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[x] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

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

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

[ ] This is a backport pr

Bugfix cherry-pick branch check:

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

[ ] 3.3
[ ] 3.2
[ ] 3.1
[x] 3.0
[x] 2.5

@mergifyio backport branch-3.0

@Mergifyio backport branch-3.0


Hessian benchmark that takes about 30s

@kpamnany, here's a benchmark script that uses the Hessian and takes about 30s on my machine.
Ryan

Thanks! How can I increase the runtime? Increase S?

Yep, that's right.


Opening the Action Center in landscape mode should have everything rotated if the user wants to have it that way, including notifications.

Basically, the battery percentage and everything would be rotated just like the time. For notifications, the part of the Action Center that shows them would also rotate, but they'll be to the side of the Quick Actions instead of below them. The Quick Actions would change to a vertical list.
As cool as this is, thinking about it more makes it sound like it might not work, or at least be easy to do. Doing it iOS-style where you pull it down from the top may be necessary, unless I can figure out a way to rotate the controls when the display is wider than it is tall, or however rotation would be checked.

This seems a bit much, so I should leave this up to the user to choose.


Add tracer to optimizer to see how original expression is transformed to optimized expression

General Problem
Currently, we don't have a way of investigating the exact steps the optimizer took to convert some original expression to its optimized form. As a result, it's harder for us to know how to improve the heuristics (#10) or how one change propagates through to some other change. Similarly, when one is trying to optimize a specific expression and it's not producing what is expected, it's hard to know why. Ideally, there would be an option in this project that would enable such tracing.
Design Questions

In adding a tracer feature, should this feature be exposed by adding it to an existing command (e.g. build/bundle)? Or should it be its own command (e.g. purs-backend-es trace)? I assume the latter for a few reasons:

I imagine there will be a lot of different configuration values defined via CLI args. A dev who calls purs-backend-es build likely doesn't care about that as the dev is just trying to produce an optimized build. Moreover, the flags/args may spam the docs for the build command, which would otherwise remain simple if these two are kept separate.
A trace command doesn't need to produce any build output. If anything, the trace is the output of the command.

Potential User Workflows
There's a few workflows that this feature could support.

For a single top-level identifier, allow a user to see the original expression, the optimized expression, and the steps taken to optimize it. In other words, is this identifier being optimized as much as it could be? Or are there optimizations not firing here that should be firing?
For all or some select set of identifiers (host identifier) using a specific top-level identifier (target identifier), allow a user to see the original expression, the optimized expression, and the steps taken to optimize it for each one of the host identifiers. In other words, where does the target identifier get used in host identifiers, does the target identifier get inlined, why or why not, and how well does the target identifier inline?
For all type class instances of a given type class, see how how well they optimize (1 above) or how well they inline (2 above) as this is often where inlining would be useful.
For all data constructor of a given type, same as 3 above.
For a specific let/where binding within a top-level identifier, see how how well they optimize and/or how well they inline into their usage site within the top-level identifier.

Implementing tracing using 'best practices'
Tracing at its heart is a form of logging. To prevent spamming this codebase with a bunch of log statements that force us to pass in additional context so as to properly format/display the exact String there, I propose we use Contravariant Logging (explained in "co-log: Composable Contravariant Combinatorial Comonadic Configurable Convenient Logging") via the library purescript-logging to achieve this goal. I read through the post yesterday and wrote myself a cheat sheet of the various functions and my current understanding of their usages.
The general idea of Contravariant Logging has similarities to the "Imperative Shell, Functional Core" idea. In the "Functional Core", one passes in to a callback function the values that make sense within that particular context. In other words, one does not pass the context into functions just for logging. Rather, functions pass in the values to the callback, and the callback adds context over time. As one moves from the "Functional Core" towards the "Imperative Shell", additional context is added to the callback's input function via cmap. divide logs a large amount of information by splitting it into smaller pieces and logging each separately. One can decide what to log and what to ignore via choose/cfilter in contexts where it makes sense to do so. Once in the "Imperative Shell", one defines the actual callback that runs logs the now-context-rich value in whatever way they want.
When I traced the control flow from purs-backend-es to where optimize is called, it took the following steps. Along the way, I note where we can add information to the context of the tracer via cmap:

purs-backend-es

Main.main will call buildCmd (where binding) when either the build or bundle CLI commands are used.
buildCmd (where binding) calls EcmaScript.Builder.basicBuildCmd with a few options set.
basicBuildCmd calls Optimizer.Builder.buildModules

in basicBuildCmd, if coreFnModulesFromOutput also included the module's file path in its success path, we could add the module's file path to the context via cmap: Record.insert "filePath" filePath >$< logger).

purescript-backend-optimizer

buildModules folds through each module via go (where binding), using the accumulated value in the next fold. However, it doesn't currently return any data from the accumulated value.

in buildModules's go binding, we could actually run the callback in the line above options.onCodegenModule as we're in a monadic context and can use effects like Console.log.
in buildModules's go binding, we could add the module's name to the context via cmap: Record.insert "moduleName" moduleName >$< logger).

go calls the pure function, Optimizer.Convert.toBackendModule, on every module.
toBackendModule via moduleBindings (where binding) calls Optimizer.Convert.toBackendTopLevelBindingGroups, which is a preprocessing step to determine whether a binding group is recursive or not.
toBackendTopLevelBindingGroups calls Optimizer.Convert.toBackendTopLevelBindingGroup, which converts either a recursive or non-recursive top-level binding group.

in toBackendTopLevelBindingGroup, we could add to the logger's context the following information:

what other identifiers are included in the group: Record.insert "recursiveGroup" (NonEmptyArray.fromArray bindingsInGroup) >$< logger
whether the group is recursive or not: either via Record.insert "recursive" isRecursive >$< logger or by deriving that information from the previous one

toBackendTopLevelBindingGroup calls Semantics.optimize a single top-level identifier is optimized.
Finally, optimize starts a "quote-eval" loop that iteratively optimizes the expression until the analysis indicates that no more rewriting is possible.
in optimize, we could log our main values:

the original expression before the loop
the final expression after the loop
a list of steps taken here to go from the original to the optimized expression by logging:

the expression at the loop step's start (i.e. before)
the expression at the loop step's end (i.e. after)
the loop step count

Or put differently, I think the "application-level" type we can log would be:
type OptimizationStep =
  { before :: Expr -- expression before this loop step
  , after :: Expr -- expression after this loop step
  , index :: Int -- which loop step this is
  , rewrite :: Boolean -- whether we will continue the loop
  }

type LogType =
  { filePath :: FilePath
  , moduleName :: ModuleName
  , identifier :: Ident
  , recursiveGroup :: Maybe (NonEmptyArray Ident)
  , originalExpr :: Expr
  , optimizedExpr :: Expr
  , steps :: List OptimizationStep
  -- these latter two values may require an `analysisOf` call
  -- to determine what other identifiers this one depends on
  , usedLocalIdentifiers :: Array Ident -- identifiers defined within the module
  , usedExternalIdentifiers :: Array (Qualified Ident) -- identifiers defined in an imported module
  }

We could then take the above type and easily configure the following:

via cfilter, determine which log events we actually output to the console (e.g. a specific identifier, all identifiers that use a specific identifier, all identifiers from a given module, all identifiers whose associated file path matches some source glob). I imagine these would be determined via CLI flags/args.
via different printers, how we print the information and format it before printing to the console. For example,

pretty print things via dodo-printer with ansi colors for clear readability
rather than printing an optimization step's before expression and after expression, we could show one expression that contains a diff by using purescript-debug.

I talked with Nate about this yesterday and he raised a few points:

All the information stored in the OptimizationStep type above can be derived from the simpler type of NonEmptyArray BackendExpr (or NonEmptyList BackendExpr). We should use the simpler type.
We don't have a clear problem we're trying to solve aside from understanding why Snapshots produce the output that they do, and why it does or doesn't match our expectations. So, it's simpler to focus on that problem instead of other things in the future.
Regarding the design question 1, it wasn't clear to us whether or not the trace feature should be exposed as a CLI arg in the build command or as a separate trace command.
The contravariant logging approach assumes users will always log something. As such, it forces the library authors to pass some value into the callback logging function, even if that value is immediately ignored via cfilter (const false) someOtherLogger. In this project's case, we would need to pass in a NonEmptyArray BackendExpr value, which is a memory-heavy message value. So, even if we don't use the message value to log something, we still pay for the memory cost of creating it.


[docs] Task guide for semantic segmentation with LoRA

Moves LoRA for semantic segmentation notebook into the docs.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


feat: added cancelled event for invite acceptor

This PR add cancelled event for invite acceptor. More details in ring_invite example

Recreate for run CI


Name of anime not being intepreted as a string

description
When I pass the name of the anime to the dl function, I get an error stating that an extra argument has been passed. It's as if the name of the anime is being split into separate arguments. The command I used is directly copied from the wiki as I was just testing this out now.

anime dl 'code geass' --provider kissanime

LOG

```
Usage: anime-script.py dl [OPTIONS] ANIME_URL
Error: Got unexpected extra argument (geass')
Using Windows 8.1
</details>

Does this happen with " as well? ie anime dl "code geass"?

No it does not, thanks though. But strange nonetheless, should probably update the wiki or maybe just a Windows thing.

Did you fix it somehow? If yes I can update the wiki with the info.


Eliminate the need for jekyll-load

Move the data in _data to the front-matter of the corresponding .md files. This eliminates the need to mirror files.

One problem is that jekyll-load sets the items list on index.md pages, and the _prep scripts use the items lists to add properties like subtitle to the data.

Done.


[QUESTION] Dynamic provisioning Persistent Volumes

Not creating dynamic Persistent Volumes
Hello! Can you help me .   I deploy the following
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: juicefs-pvc
  namespace: infra
spec:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 2Gi
  storageClassName: juicefs-sc
---
apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app: app-test
  name: app-test
  namespace: infra
spec:
  replicas: 1
  selector:
    matchLabels:
      app: app-test
  template:
    metadata:
      labels:
        app: app-test
      annotations:
        app: app-test
    spec:
      containers:
        - args:
          - -c
          - while true; do echo $(date -u) >> /data/out.txt; sleep 5; done
          command:
          - /bin/sh
          image: busybox
          name: app
          volumeMounts:
          - mountPath: /data
            name: juicefs-pv
          resources:
            limits:
              cpu: 400m
              memory: 1Gi
            requests:
              cpu: 100m
              memory: 100Mi
      volumes:
      - name: juicefs-pv
        persistentVolumeClaim:
          claimName: juicefs-pvc

Look PVC :
kubectl describe pvc -n infra juicefs-pvc
Name:          juicefs-pvc
Namespace:     infra
StorageClass:  juicefs-sc
Status:        Pending
Volume:
Labels:        <none>
Annotations:   volume.beta.kubernetes.io/storage-provisioner: csi.juicefs.com
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode:    Filesystem
Used By:       app-test-9fdc8f479-qmqkx
Events:
  Type    Reason                Age                     From                         Message
  ----    ------                ----                    ----                         -------
  Normal  ExternalProvisioning  2m50s (x26 over 8m45s)  persistentvolume-controller  waiting for a volume to be created, either by external provisioner "csi.juicefs.com" or manually created by system administrator

persistentvolume  PV not created automatically
but if I  deploy this
apiVersion: v1
kind: PersistentVolume
metadata:
  name: juicefs-pv
  labels:
    juicefs-name: ten-pb-fs
spec:
  # For now, JuiceFS CSI Driver doesn't support setting storage capacity for static PV. Fill in any valid string is fine.
  capacity:
    storage: 10Gi
  volumeMode: Filesystem
  accessModes:
    - ReadWriteMany
  persistentVolumeReclaimPolicy: Retain
  csi:
    # A CSIDriver named csi.juicefs.com is created during installation
    driver: csi.juicefs.com
    # volumeHandle needs to be unique within the cluster, simply using the PV name is recommended
    volumeHandle: juicefs-pv
    fsType: juicefs
    # Reference the volume credentials (Secret) created in previous step
    # If you need to use different credentials, or even use different JuiceFS volumes, you'll need to create different volume credentials
    nodePublishSecretRef:
      name: myjfs
      namespace: infra
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: juicefs-pvc
  namespace: infra
  annotations:
    csi.juicefs.com/additional-mount-options: "writeback,upload-delay=1m,metrics=<IP_ADDRESS>:9567" # Add JuiceFS settings if necessary.
    juicefs/mount-annotations: '{"prometheus.io/port":"9567","prometheus.io/scrape":"true"}'
    juicefs/mount-cpu-limit: 4000m
    juicefs/mount-cpu-request: 100m
    juicefs/mount-memory-limit: 5Gi
    juicefs/mount-memory-request: 100Mi
spec:
  accessModes:
    - ReadWriteMany
  volumeMode: Filesystem
  # Must use an empty string as storageClassName
  # Meaning that this PV will not use any StorageClass, instead will use the PV specified by selector
  storageClassName: ""
  # For now, JuiceFS CSI Driver doesn't support setting storage capacity for static PV. Fill in any valid string that's lower than the PV capacity.
  resources:
    requests:
      storage: 10Gi
  selector:
    matchLabels:
      juicefs-name: ten-pb-fs
---
apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app: app-test
  name: app-test
  namespace: infra
spec:
  replicas: 1
  selector:
    matchLabels:
      app: app-test
  template:
    metadata:
      labels:
        app: app-test
      annotations:
        app: app-test
    spec:
      containers:
        - args:
          - -c
          - while true; do echo $(date -u) >> /data/out.txt; sleep 5; done
          command:
          - /bin/sh
          image: busybox
          name: app
          volumeMounts:
          - mountPath: /data
            name: data
          resources:
            limits:
              cpu: 400m
              memory: 1Gi
            requests:
              cpu: 100m
              memory: 100Mi
      volumes:
      - name: data
        persistentVolumeClaim:
          claimName: juicefs-pvc

this OK works.
I use in helm
mountMode: process

this my parametrs:
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  annotations:
    meta.helm.sh/release-name: jucefs
    meta.helm.sh/release-namespace: infra
  creationTimestamp: "2024-07-04T05:04:33Z"
  labels:
    app.kubernetes.io/instance: jucefs
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: juicefs-csi-driver
    app.kubernetes.io/version: 0.24.1
    helm.sh/chart: juicefs-csi-driver-0.20.3
  name: juicefs-sc
  resourceVersion: "2705151405"
  uid: 910b954e-5886-4832-bfad-1269e34975fd
mountOptions:
- buffer-size=10240
- max-uploads=50
- cache-size=204800
- cache-dir=/var/jfsCache
- writeback
- upload-delay=20s
- metrics=<IP_ADDRESS>:9567
parameters:
  csi.storage.k8s.io/controller-expand-secret-name: juicefs-sc-secret
  csi.storage.k8s.io/controller-expand-secret-namespace: infra
  csi.storage.k8s.io/node-publish-secret-name: juicefs-sc-secret
  csi.storage.k8s.io/node-publish-secret-namespace: infra
  csi.storage.k8s.io/provisioner-secret-name: juicefs-sc-secret
  csi.storage.k8s.io/provisioner-secret-namespace: infra
  juicefs/mount-annotations: '{"prometheus.io/port":"9567","prometheus.io/scrape":"true"}'
  juicefs/mount-cpu-limit: 4000m
  juicefs/mount-cpu-request: 100m
  juicefs/mount-memory-limit: 5Gi
  juicefs/mount-memory-request: 100Mi
  pathPattern: ${.PVC.namespace}-${.PVC.name}
provisioner: csi.juicefs.com
reclaimPolicy: Delete
volumeBindingMode: Immediate
---
apiVersion: v1
data:
  access-key: {this key}
  bucket: {name bucket}
  format-options: trash-days=1,block-size=4096
  metaurl: {meta url}
  name: myjfs
  secret-key: {key}
  storage: s3
kind: Secret
metadata:
  annotations:
    meta.helm.sh/release-name: jucefs
    meta.helm.sh/release-namespace: infra
  creationTimestamp: "2024-07-04T05:04:33Z"
  labels:
    app.kubernetes.io/instance: jucefs
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: juicefs-csi-driver
    app.kubernetes.io/version: 0.24.1
    helm.sh/chart: juicefs-csi-driver-0.20.3
  name: juicefs-sc-secret
  namespace: infra
  resourceVersion: "2705151399"
  uid: 6ec3d58b-6374-4ae7-b9a1-9a849ebbcd88
type: Opaque

how to specify automatic creation Persistent Volume in mountMode process . Because in  mountMode: mountpod and sidecar,  Persistent Volume auto created.
can you help please.

plz disable controller.provisioner in helm chart values
process mode not support provisioner
see docs https://juicefs.com/docs/csi/guide/configurations/#provioner
will fix this default value in processmode later

Thank you friend.  Didn't understand the documentation correctly.


Training service error: NNIManager version is 9, TrialKeeper version is 2.3, NNI version does not match!

Describe the issue:
I am running the mnist-pytorch example in the kubeflow mode ,following is the config file
authorName: default
experimentName: example_dist_pytorch
trialConcurrency: 1
maxExecDuration: 1h
maxTrialNum: 1
#choice: local, remote, pai, kubeflow
trainingServicePlatform: kubeflow
searchSpacePath: search_space.json
#choice: true, false
useAnnotation: false
tuner:
#choice: TPE, Random, Anneal, Evolution, BatchTuner, MetisTuner, GPTuner
builtinTunerName: TPE
classArgs:
#choice: maximize, minimize
optimize_mode: maximize
trial:
codeDir: .
master:
replicas: 1
command: python3 dist_mnist.py
gpuNum: 0
cpuNum: 1
memoryMB: 4096
image: tensorflow/tensorflow
worker:
replicas: 1
command: python3 dist_mnist.py
gpuNum: 0
cpuNum: 1
memoryMB: 4096
image: mapler/pytorch-cpu:latest
kubeflowConfig:
operator: pytorch-operator
apiVersion: v1
storage: azureStorage
keyVault:
vaultName: keyautoml
name: ExamplePassword
azureStorage:
accountName: automlstore
azureShare: myshare
nniManagerIp: <IP_ADDRESS>
Environment:

NNI version:999.dev0
Training service (local|remote|pai|aml|etc):kubeflow
Client OS: ubuntu 18.04
Is running in Docker?: yes

nni dispatcher status :  Training service error: NNIManager version is 9, TrialKeeper version is 2.3, NNI version does not match!
log files
[2021-08-02 06:48:18] INFO (NNIDataStore) Datastore initialization done
[2021-08-02 06:48:18] INFO (RestServer) RestServer start
[2021-08-02 06:48:18] WARNING (NNITensorboardManager) Tensorboard may not installed, if you want to use tensorboard, please check if tensorboard installed.
[2021-08-02 06:48:18] INFO (RestServer) RestServer base port is 5080
[2021-08-02 06:48:18] INFO (main) Rest server listening on: http://<IP_ADDRESS>:5080
[2021-08-02 06:48:18] INFO (NNIManager) Setup training service...
[2021-08-02 06:48:19] INFO (KubernetesTrainingService) Construct Kubeflow training service.
[2021-08-02 06:48:20] INFO (NNIManager) Starting experiment: 1Cmxe5ng
[2021-08-02 06:48:20] INFO (NNIManager) Setup tuner...
[2021-08-02 06:48:20] INFO (NNIManager) Change NNIManager status from: INITIALIZED to: RUNNING
[2021-08-02 06:48:20] INFO (NNIManager) Add event listeners
[2021-08-02 06:48:20] INFO (KubernetesTrainingService) Run Kubeflow training service.
[2021-08-02 06:48:20] INFO (RestServer) RestServer start
[2021-08-02 06:48:20] INFO (RestServer) RestServer base port is 5081
[2021-08-02 06:48:20] INFO (KubernetesTrainingService) Kubeflow Training service rest server listening on: http://<IP_ADDRESS>:5081
[2021-08-02 06:48:21] INFO (NNIManager) NNIManager received command from dispatcher: ID,
[2021-08-02 06:48:21] INFO (NNIManager) NNIManager received command from dispatcher: TR, {"parameter_id": 0, "parameter_source": "algorithm", "parameters": {"lr": 1e-06}, "parameter_index": 0}
[2021-08-02 06:48:25] INFO (NNIManager) submitTrialJob: form: { sequenceId: 0,
hyperParameters:
{ value:
'{"parameter_id": 0, "parameter_source": "algorithm", "parameters": {"lr": 1e-06}, "parameter_index": 0}',
index: 0 } }
[2021-08-02 06:48:25] INFO (KubernetesTrainingService) Construct Kubeflow training service.
[2021-08-02 06:50:20] INFO (NNIManager) Trial job O41cy status changed from WAITING to RUNNING
[2021-08-02 06:50:47] INFO (RestServer) POST: /version/1Cmxe5ng/O41cy: body: { tag: 'VCFail',
msg:
'NNIManager version is 9, TrialKeeper version is 2.3, NNI version does not match!' }
[2021-08-02 06:50:47] INFO (RestServer) POST: /stdout/1Cmxe5ng/O41cy: body: { tag: 'trial_keeper',
stdOutputType: 'Stdout',
msg:
'[2021-08-02 06:50:47.303442] INFO Trial keeper spawns a subprocess (pid 24) to run command: ['python3', 'train.py']' }
[2021-08-02 06:50:48] ERROR (NNIManager) Error: NNIManager version is 9, TrialKeeper version is 2.3, NNI version does not match!
at KubeflowTrainingService.run (/media/sladmin/nlp_disk/Kruthika/nni/ts/nni_manager/dist/training_service/kubernetes/kubeflow/kubeflowTrainingService.js:49:23)
at process._tickCallback (internal/process/next_tick.js:68:7)
[2021-08-02 06:50:48] INFO (NNIManager) Change NNIManager status from: RUNNING to: ERROR
[2021-08-02 06:50:59] INFO (RestServer) POST: /stdout/1Cmxe5ng/O41cy: body: { tag: 'trial_keeper',
stdOutputType: 'Stdout',
msg:
'[2021-08-02 06:50:59.380902] INFO subprocess terminated. Exit code is 1. Quit' }
[2021-08-02 06:50:59] INFO (RestServer) POST: /stdout/1Cmxe5ng/O41cy: body: { tag: 'trial_keeper',
stdOutputType: 'Stdout',
msg:
'[2021-08-02 06:50:59.447080] INFO NNI trial keeper exit with code 1' }
[2021-08-02 06:52:00] INFO (RestServer) POST: /version/1Cmxe5ng/O41cy: body: { tag: 'VCFail',
msg:
'NNIManager version is 9, TrialKeeper version is 2.3, NNI version does not match!' }
[2021-08-02 06:52:01] INFO (RestServer) POST: /stdout/1Cmxe5ng/O41cy: body: { tag: 'trial_keeper',
stdOutputType: 'Stdout',
msg:

@SparkSnail  any solution to this error ?  the nni dashboard  status will be error due to this ?

@kruthikakr because you install NNI from source code in local machine.
There are two ways to solve this:

Uninstall NNI firstly, and reinstall NNI v2.3.
Set versionCheck: false in your config yaml file, refer https://github.com/microsoft/nni/blob/master/docs/en_US/Tutorial/ExperimentConfig.rst#versioncheck

Yes it is solved. Thank you


Not all roles synced. Discord API limit reached.

I am getting the error:  'Not all roles synced. Discord API limit reached.' when I am manually running the task ONCE on only one test account, however I am getting rate limited already?

same

There has been some API changes since the last update to this code...

I've figured how to fix it: https://github.com/opt-natter/discord-mybb-sync/issues/20

Thanks Terran


Running a powershell script works in one environment and throws internal server error in another

Please provide us with the following information:

This issue is a: (mark with an x)

[x ] bug report -> please search issues before submitting
[ ] documentation issue or request
[ ] regression (a behavior that used to work and stopped in a new release)

Issue description
A clear and concise description of the observed issue.
github task

name: Deploy DB Boostrap
shell: pwsh
env:
ARM_CLIENT_ID: ${{ secrets.ARM_CLIENT_ID }}
ARM_CLIENT_SECRET: ${{ secrets.ARM_CLIENT_SECRET }}
ARM_SUBSCRIPTION_ID: ${{ secrets.ARM_SUBSCRIPTION_ID }}
ARM_TENANT_ID: ${{ secrets.ARM_TENANT_ID }}
AZURE_CREDENTIALS: ${{ secrets.AZURE_CREDENTIALS }}
REPO_TOKEN: ${{ secrets.REPO_TOKEN }}
DB_HOST: ${{ steps.myGetSecretAction.outputs.postgresHost }}
DB_NAME: ${{ steps.myGetSecretAction.outputs.postgresName }}
DB_USER: ${{ steps.myGetSecretAction.outputs.postgresUser }}
DB_PASS: ${{ steps.myGetSecretAction.outputs.postgresPassword }}
REDIS_KEY: ${{ steps.myGetSecretAction.outputs.redisKey }}
REDIS_URL: ${{ steps.myGetSecretAction.outputs.redisHostName }}
AZURE_ACCESS_KEY: ${{ steps.myGetSecretAction.outputs.storageAccountKey }}
AZURE_ACCOUNT_NAME: ${{ steps.myGetSecretAction.outputs.storageAccountName }}
AZURE_KEY_VAULT_NAME: ${{ inputs.keyvaultName }}
USER_ASSIGNED_PRINCIPAL_ID: ${{ steps.myGetSecretAction.outputs.userAssignedPrincipalId }}
USER_ASSIGNED_ID: ${{ steps.myGetSecretAction.outputs.userAssignedId }}
SHOWROOM_DB: ${{ steps.myGetSecretAction.outputs.showroomDB }}
run: |
pwsh deployment_script/deployBootstrap.ps1 -containerAppEnvName ${{ inputs.containerAppEnvName }}   -backendAppId ${{ inputs.bootstrapApp }}  -revisionSuffix  ${{ github.run_number }} -dockerImageName ${{ inputs.bootstrapImageName }} -environment ${{ inputs.environment }} -resourceGroup ${{ inputs.resourceGroup }} -location ${{ inputs.location }} -subscription_id ${{ secrets.ARM_SUBSCRIPTION_ID }} -acr_password ${{ secrets.REGISTRY_PASSWORD }}

DEV ENVIRONMENT
Run pwsh deployment_script/deployBootstrap.ps1 -containerAppEnvName cae-ds-dev-westeurope   -backendAppId bootstrap-ds-dev-westeurope  -revisionSuffix  167 -dockerImageName ds-bootstrap -environment Dev -resourceGroup rg-DigitalShowroom-dev-westeurope-001 -location westeurope -subscription_id *** -acr_password ***
WARNING: The installed extension 'containerapp' is in preview.
/ Running ..
| Running ..
\ Running ..
WARNING:

TEST  ENVIRONMENT
Run pwsh deployment_script/deployBootstrap.ps1 -containerAppEnvName cae-ds-test-westeurope   -backendAppId bootstrap-ds-test-westeurope  -revisionSuffix  167 -dockerImageName ds-bootstrap -environment test -resourceGroup rg-DigitalShowroom-test-westeurope-001 -location westeurope -subscription_id *** -acr_password ***
WARNING: The installed extension 'containerapp' is in preview.
ERROR: (InternalServerError) Internal server error occurred. correlation ID: 080c23ac-8b11-47b5-a9b5-31169f72a6f3

Steps to reproduce

.. running powershell script to deploy az containerapp

..

Expected behavior [What you expected to happen.]
Deployment
Actual behavior [What actually happened.]
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Ex. In CLI with pwsh ubuntu-latest

Your app seems to be missing. If this is still an issue please reopen.


Browserify Transform support

You can now use the prepr as the browserify transform, which will transform all files on fly.
browserify:     {
    options:      {
        transform:  [ require('grunt-prepr').browserify(["DEBUG"]) ],
    }
}

Thank you, I will check it out, merge, and publish an update.

If you will be merging this pull request do not forget to add index.js to files section in package.json

Looks good, thanks, I will merge.

You need to add index.js to files section in package.json. If you do not do this then the file index.js will be missing after npm install.

Thanks for noticing this, I included index.js into the file list and published an updated NPM package.


[FEATURE - PoC] Integrate OSD visualizations to Operational Panels

Is your feature request related to a problem?
Here's the summary: https://github.com/opensearch-project/dashboards-observability/issues/106
This issue tracks the dashboards component for initial POC

PoC is complete


Cannot export configuration

Thank you for making such a great extension. However, with the current version, I cannot export the configuration to a json file to use it in another computer.
Also, some more suggestions. It would be better if there is a way to rename the config instead of naming it with the URL. And also, a better way to change the position of the actions and configs would make this extension perfect to me :)

Please refer Export/Import Guide


[flutter_tools] Fix Intellij minor patches detection on Windows

Complete details here https://github.com/flutter/flutter/pull/82663#issue-645391202
It is now to possible detect minor patches by reading .appinfo file and this PR makes it possible to report intellij's  version including minor patches
This PR fixes IntelliJ minor patches detection
IntelliJ (installed via the installer on windows)
Before
[✓] IntelliJ IDEA Community Edition (version 2021.1)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2021.1.1
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

After
[√] IntelliJ IDEA Community Edition (version 2021.1.1)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2021.1.1
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart

IntelliJ (installed via toolbox app on windows)
Before
[✓] IntelliJ IDEA Community Edition (version 2021.1)
    • IntelliJ at C:\Users\Taha\AppData\Local\JetBrains\Toolbox\apps\IDEA-C\ch-0\211.7142.45
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

After
[√] IntelliJ IDEA Community Edition (version 2021.1.1)
    • IntelliJ at C:\Users\Taha\AppData\Local\JetBrains\Toolbox\apps\IDEA-C\ch-0\211.7142.45
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart

We should close https://github.com/flutter/flutter/issues/70387 as there is no way to fix this in an older version of Android Studio. ex: `Android Studio 4.1.1, this would also apply to older Intellij versions
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Similar question to what I had on the AS detection

I have tried 2020 versions, they don't have this appinfo dot file, 2021.1 version has this file (this is the first 2021 stable release). Please check this Intellij other version archive

Unlike https://github.com/flutter/flutter/pull/82663, for IntelliJ we scan for all versions 2020+ version, appinfo dot file only exists after 2021.1 so I am close this PR until I find a better solution to solve this for newer versions only (2021+)


feat(katana): db storage integration

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

dev/katana

PR #6

PR #7   👈

This stack of pull requests is managed by Graphite.


Connecting multiple swarm hosts (backend)

Hi!
I'm trying to set up a swarm cluster on the backend but am having a couple of issues. Reading the code, in Pipe.js it says that a pipe is a channel to a remote swarm host. This works great when the connection is from client -> server, but not so much when doing server -> server. I am able to connect servers to each other but there does not appear to be any replication going on between different instances.
My issue is that we need more then one machine on the back end and since users that share models could be connected to different physical hosts we need a way to ensure that each server stays up to date and that data is replicated correctly.
Is there a way to accomplish this today?

Hi! That part of the code is lagging behind and I don't expect it to work as of now. Ironically, a consistent hashing server cluster was our first demo back in 2013.
The most of the code is still in place, e.g. https://github.com/gritzko/swarm/blob/master/lib/Syncable.js#L797
Consistent hashing logic is the same on client and server, as the client may connect several servers at once or choose what server to connect to.
I am elbow-deep in v0.4 at the moment, may be @abalandin will find some time to revitalize that code.

Thanks for your response, I will try digging further to see if I can solve this.
If not, is this something that is planned for v0.4 otherwise?

Yep, 0.4 puts an accent on server-side stuff.

Is that feature done for 0.4 ?

Consistent hashing server rings, ETA is early-December.


Create chichesterfreeschool.txt

@tyler201 Pull request merged. Please notice that free educational license for JetBrains tools is for high and higher schools students, i.e. those who are over 13 of age. Thank you!


The programming experience with IDEA is terrible

Have you read the Contributing Guidelines on issues?

[ ] I have read the Contributing Guidelines on issues.

Motivation

Can you come up with an IDEA plugin so that these components can code hints normally on IDEA?
Self-service

[ ] I'd be willing to do some initial work on this proposal myself.

This is a known limitation but it is not related in any way to IDEA: we simply do not provide TypeScript definitions for wrapped components because we don't have a system to emit those.
Please don't be condescending. If you know how to fix it, your PR is welcome.


The errors after applying images

@RQuispeC  When we launched your code the errors appeared, for example "out of range" and problems with shape. If you have some info about training model on Shanghai Tech dataset, please inform us.
P.S. We tried to train our models on Shanghai Tech dataset

I have limited information to help you solve your problem and We trained on shanghai tech (results on paper).  Please make sure your are following step 2 of the README to make sure your files/directories follow the expected hierarchy.


eSTREAM finalists round reduced

Round reduced:

Rabbit
F-FCSR
Dragon (not finalist)

Fixed wrong round reduction (unused code):

HC-128

Small fixes of generator added as well...
@mitko501 you do not have to check the code (but it would be nice), it is enough to agree with changed files of this pull request.

Wait with this, I fight with submodules again...

Added TEA fix.


add [--] into --help output

so instead of
usage: duct [-h] [-p OUTPUT_PREFIX] [--sample-interval SAMPLE_INTERVAL] [--report-interval REPORT_INTERVAL] [-c {all,none,stdout,stderr}] [-o {all,none,stdout,stderr}]
            [-t {all,system-summary,processes-samples}]
            command [arguments ...]

looks like
usage: duct [-h] [-p OUTPUT_PREFIX] [--sample-interval SAMPLE_INTERVAL] [--report-interval REPORT_INTERVAL] [-c {all,none,stdout,stderr}] [-o {all,none,stdout,stderr}]
            [-t {all,system-summary,processes-samples}]
            [--] command [arguments ...]

and add description on -- as to be recommended to ensure that arguments are not treated as arguments to duct.
On the other hand, I think we might need to look into how to tune argparser here: ideally we should automagically stop parsing when reaching command.  @jwodder , you did some heavy CLI parsing tune up in datalad-installer, may be you know what would be the best way here to ensure that parsing stops and [arguments] for the command do not interfer with our duct  arguments?

@yarikoptic Unless duct is calling parser.parse_intermixed_args(), I think it should stop at the first non-option argument by default.

duct is using  parser.parse_args()
https://github.com/con/duct/blob/0eec46d9c7527a7f17d3205447223f27b622aa87/src/duct.py#L271

not quite -- it does consume [arguments] and spits out error, e.g. we get

for
yoh@typhon:/tmp/repro-TccSlQF/ds000003-qc$ cat .datalad/config
[datalad "dataset"]
        id = 621f77c3-4a35-4147-8146-67fa49b66369
[datalad "containers.bids-mriqc"]
        image = containers/images/bids/bids-mriqc--0.16.0.sing
        cmdexec = duct {img_dspath}/containers/scripts/singularity_cmd run {img} {cmd}

in repronim/containers - I had to add -- after duct there

Then try parse_known_args() instead.

Is there a reason you need to use argparse in the first place?  Click is really the better option for both this sort of thing and in general.

We wanted duct to be "pure" to be as portable as possible.

The undocumented nargs value argparse.REMAINDER should do what you want:
import argparse

parser = argparse.ArgumentParser()
parser.add_argument("-f", "--foo")
parser.add_argument("rest", nargs=argparse.REMAINDER)

print(parser.parse_args(["bar", "--foo", "quux"]))
# Prints: Namespace(foo=None, rest=['bar', '--foo', 'quux'])


Release 0.3.1

Getting Shoes 4.0.0.pre4 out the door (https://github.com/shoes/shoes4/pull/1116), we need a new gem release of furoshiki (0.3.1)
Any objections to me making that release?
#16 is out there, but I haven't been able to duplicate it, and we can always rev furoshiki independently of shoes since we've got a ~> on it in shoes-package.
If I don't hear anything to the contrary, likely to cut the gem on Friday evening.

:shipit: :ship: :rocket:


when download  dataset，error

Traceback (most recent call last):
  File "C:\Anaconda3\envs\tensorflow\lib\runpy.py", line 184, in _run_module_as_main
    "__main__", mod_spec)
  File "C:\Anaconda3\envs\tensorflow\lib\runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "C:\Users\zhang\Desktop\cellcount-master\cellcount-master\cellcount\cli\main.py", line 53, in <module>
    main()
  File "C:\Users\zhang\Desktop\cellcount-master\cellcount-master\cellcount\cli\main.py", line 34, in main
    args_func(args, p)
  File "C:\Users\zhang\Desktop\cellcount-master\cellcount-master\cellcount\cli\main.py", line 39, in args_func
    args.func(args, p)
  File "C:\Users\zhang\Desktop\cellcount-master\cellcount-master\cellcount\cli\parser_download.py", line 88, in func
    dl_unzip(image_uri, outdir, update)
  File "C:\Users\zhang\Desktop\cellcount-master\cellcount-master\cellcount\cli\parser_download.py", line 58, in dl_unzip
    reporthook=reporthook)
  File "C:\Anaconda3\envs\tensorflow\lib\urllib\request.py", line 198, in urlretrieve
    tfp = open(filename, 'wb')
PermissionError: [Errno 13] Permission denied: 'C:\\Users\\ZHANG~1\\AppData\\Local\\Temp\\tmp6qzt4v45'

As the error states there seems to be an issue with write-access permissions in your temporary files directory when using urllib.request.urlretrieve.
Since this isn't necessarily an issue with the cellcount package and I have relatively little experience with Windows, I'd defer to searching StackOverflow for a solution.


wget script gen fails. Same as issue #615 and issue #614. Solution of signing out and back in doesn't work.

Describe the bug
wget script fails to generate on second+ attempt. Same error on Chrome (including incognito) and Safari. Sign-in and sign-out is not fixing the problem.
Mac OS Ventura 13.2.1

OS:
Chrome Version 125.0.6422.112
Safari Version 16.3 (186<IP_ADDRESS>.6)

This morning, I put ~30 files in my cart. wget script successfully generated and I downloaded the files.
On the second attempt in the same browser with new data, wget script fails to generate. See screenshot for error

Error workaround for me was:
a. opening a new browser window (worked once, then failed to work a second time)
b. opening an incognito browser window (worked once, then failed to work a second time)
c. opening a different browser and putting together the same order (worked once, then failed to work a second time)

For issues #614 and #615 the solution is signing out and signing back in. I'm unable to sign in. When I click sign in, I can authenticate but then it takes me back to the same page with "sign-in" as an option at the top again (see screenshot for page, plus javascript error)

Thank you for reporting, I am conferring with the team. There is a problem detected on the server too and so we need to investigate.
In the meantime we have a separate deployment:  https://nimbus.llnl.gov/metagrid/search
it runs on better server hardware so might be worth a try,  I could sign in/out/in just now and generate two separate scripts from new searches each time.

Thanks. I encountered the same problem, but the workaround of signing in and back out worked with the separate deployment.

Do you recall which specific data in the search in the second attempt? (you can "copy" to share if you still have it)


lug-helper: init at 2.17

Description of changes
lug-helper is a script designed to help you manage and optimize star citizen on linux.
Source: https://github.com/starcitizen-lug/lug-helper/
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Requested changes have been made.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4394

A new version has been released, I have adjusted the package to for the new version:
Changelog: https://github.com/starcitizen-lug/lug-helper/releases/tag/v2.18
Diff: https://github.com/starcitizen-lug/lug-helper/compare/v1.17...v1.18

I haven't tested this but looks like helper_dir will have to be patched in order for the bundled files to work.
We should also change the pixmap from lug-helper to lug-logo since that's what upstream uses.

If you can get someone else to test and confirm that it works that'd be great

requested changes made, tested on two separate machines.


Incorrect naming of "bool_model"

The operation group "bool" should be renamed "bool_model" in BodyBoolean Swagger.

Python name issue on operation group

fixed


Create ssrf.yaml，xxe.yaml，pathtraversal.yaml

Hi @pwnhxl, The response time to this PR was much longer than usual. Thank you for taking the time to create this issue and for contributing to this project 🍻
I have made a few changes to your PR here. Let me know if it looks good to you.