Question: a file with variables to be used in docker/rancher compose

Hello,
I find very comfortable to use the .env file for docker-compose when using docker, as specified in their documentation
I didn't understand if there is such a mechanism with rancher and didn't find anything about this in the documentation. This is very important when uploading new stacks from a docker-compose and rancher-compose file, because you may use the same element in different services definition.
May you kindly lead me to a solution?

With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.


feat(tree2): add more snapshot tests

Add more tree2 snapshot tests and a README.
Also adds more docs to some things, reflows comments to ~80 characters, and fixes a data corruption bug.
ADO#5327 (readme), ADO#5326 (expand snapshot test suite), and ADO#5517 (avoid double json stringify in snapshot tests)

^ I did git pull upstream next instead of git pull upstream main -_-


Set kibana/elasticsearch data as mounted volume

I think it would be better to put kibana and elasticsearch data folders in a volume container, so we can backup/restore it and not loose it when the container is gone

Could you provide a PR/documentation for that?
Note that it also relate to the missing documentation : https://github.com/tomav/docker-mailserver/issues/337

OK, I will try to figure out how to do it, as I don't know where/how elasticsearch or kibana store its data.

@citec any news on the PR or a solution?

I'll close this as there has been no answer since 2017. As for the problem itself I would suggest using the official Kibana/Elastic images that are actively maintained and well documented, perhaps with the container in this project as an example for how to configure it.


Typed input for Orchestrator is not deserializing properly. FunctionsOrchestrationContext.JsonElementInputConverter  is case sensitive on Deserialization

Microsoft.Azure.Functions.Worker.Extensions.DurableTask.ObjectConverterShim serializes with camelCase.
However it is case sensitive when deserializing, so the values will end up with defaults.
public class MyOrchestratorParameters
{
    public DateTime FromDate { get; set; }
    public DateTime ToDate { get; set; }
}

will be serialized to
{"fromDate":"2023-07-01T00:00:00","toDate":"2023-11-01T00:00:00"}

The input to my orchestrator is then initialized with default values (DateTime.MinValue) for both FromDate and EndDate.
If I force serialization using PascalCase it works.
public class TripletexImportOrchestratorParameters
{
    [JsonPropertyName("FromDate")]
    public DateTime FromDate { get; set; }
    [JsonPropertyName("ToDate")]
    public DateTime ToDate { get; set; }
}

which will be serialized to
{"FromDate":"2023-07-01T00:00:00","ToDate":"2023-11-01T00:00:00"}

It appears FunctionsOrchestrationContext.JsonElementInputConverter does not provide JsonSerializerOptions, and thus uses
PropertyNameCaseInsensitive = false
PropertyNamingPolicy = null

FunctionsOrchestrationContext.JsonElementInputConverter options conversion can be configured via: services.Configure<JsonSerializerOptions>(o => { ... });. By default this will also configure the JsonConverter used for ObjectConverterShim (as WorkerOptions.ObjectSerializer will use it).
I was unable to reproduce your issue this way.

No serialization customization (all default): pascal case.
Adding .ConfigureServices(s => s.Configure<JsonSerializerOptions>(o => o.PropertyNamingPolicy = JsonNamingPolicy.CamelCase)) to my main method, everything is camel case. Serialization works as expected.

Also by default in functions, JsonSerializerOptions.PropertyNameCaseInsensitive is true. Did you set this to false by chance?

I have created a sample project which demonstrates the issue.
With no serialization customization (all default) everything works.
When adding .ConfigureServices(s => s.Configure<JsonSerializerOptions>(o => o.PropertyNamingPolicy = JsonNamingPolicy.CamelCase)) it breaks.
See repo:
https://github.com/ulvesked/DurableTaskOrchestratorPayloadSerialization

Here are some thing I have found:
FunctionsOrchestrationContext.JsonElementInputConverter.Get<T>() calls Deserialize without options.
https://github.com/Azure/azure-functions-durable-extension/blob/9f750ebc77fda1f52c5042dcdb41e6eb52ee7fdb/src/Worker.Extensions.DurableTask/FunctionsOrchestrationContext.InputConverter.cs#L57
If no options are provided to Deserialize, System.Text.Json.JsonSerializer.GetTypeInfo() defaults to JsonSerializerOptions.Default
https://github.com/dotnet/runtime/blob/deb43368fde438b3e6928d3930f1362a4960fdf4/src/libraries/System.Text.Json/src/System/Text/Json/Serialization/JsonSerializer.Helpers.cs#L36C29-L36C54

Thank you for identifying the version it is fixed in.


[Feature request] Run ping only till the first success

[Feature request] Run ping only till the first success
Currently user can choose the number of pings to make. But in fact quite often 1 successful in enough to understand that the server is online. While 1 fail should not be enough because the problem can be with user's mobile connection, so additional attempts would be required.
Proposal: Add a new checkbox "Stop after the first successful" near the ping amount (3 by default) settings.

Thanks for the suggestion. I see the point but this cannot be done in the way it's currently implemented. Java/Android API does not provide a library for ICMP/ping. The app simply calls the system ping and parses the output for additional info, Success is decided by the the ping process return code (0=success). The ping count is the option "-c" for the ping command and it simply pings n times and does not stop prematurely. Of course I could do several pings with "-c 1" and aggregate everything by myself but I think it's to much effort for to little gain. The current behaviour also makes sense and I like it, so it would mean 2 different implementations and a switch.

Of course I could do several pings with "-c 1" and aggregate everything by myself but I think it's to much effort for to little gain.

In this case I would definitely do that, call it several times.
The current behavior is not making much sense to me. E.g. what should happend if user set 3 pings and got 2 success and 1 fail? Should the user be notified that server is down or up? To my opinion - it is up, but that means that all pings out of 3 were useless except the first that succeeded, which is exactly what I proposed.
Maybe I am missing some use case for the current behavior.

It's the "standard" behaviour of the ping utility. It reports overall success on at least one successful attempt. For me this makes the most sense. More pings on one try offer additional info, like average latency. However with the suggested way I can do whatever behaviour seems reasonable and I'm not fixed to ping behavior, so it's obviously better but a matter if it's worth the effort, since now it may do additonal pings that may not be necessary, depending on ones view on this, but do not hurt too much either. I'll think about it when I find the time for the pings. The time schedule feature will take a lot of time anyway. Maybe I'm in the mood to do other things between, but not now.

Release 1.5.0 does provide "stop on success" switch for ping and connect


Migrate to shopify cli v3 and update express boiler

https://github.com/Shopify/shopify-cli/issues/2434

Completed in v2


Syntax error (class Settings {  constructor() ...)

In nuxt.config.js in the plugins array I try to add a plugin pstephan1187/vue-datatable (it uses ES6 syntax)
After this I get error in IE10, IE11 - Syntax error (class Settings {  constructor() ...)
How can I transform ES6 to ES5 in plugins block?

You don't add the package there directly, but define a plugin file for it https://nuxtjs.org/api/configuration-plugins and should work. Also make sure to include the dist file from the package.

In nuxt.config.js in the plugins array I try to add a plugin pstephan1187/vue-datatable (it uses ES6 syntax). Like this:
module.exports = {     plugins: [         '~components/global',         '~plugins/axios',                '~plugins/datatable',     ],
After this It absolutely works in Chrome but I get error in IE10, IE11 - Syntax error (class Settings { constructor() ...)
In /plugins/datatable.js I do
import Vue from 'vue';  import DatatableFactory from 'vuejs-datatable';  Vue.use(DatatableFactory);
This module doesn't use dist file when I import it from 'vuejs-datatable'.
How can I import module with transform to ES2015 from sources (not dist) folder?

You have to extend the build rules and tell it to also include that library. Check the Nuxt docs.

 Thank you a lot!
I resolved the problem nuxt.config.js
    build: {
    extend (config, { isServer}) {
        config.module.rules.push({
            test: /\.js$/,
            include: [
                path.resolve(__dirname, '../node_modules/vuejs-datatable/')
            ],
            loader: 'babel-loader',
            options: this.getBabelOptions({ isServer })
        })
    },

and this path.resolve(__dirname, '../node_modules/vuejs-datatable/') should be right path.


Negative-size-param in try_read_network

Hello.
I found a Negative-size-param bug in arcus-memcached.
I think you need to change memcached to the latest version.
Please confirm.
Thanks.
OS: CentOS 7 64bit
Version: 004342dccee87f15796b1e8365e1f127c25afc4b
PoC Download:  poc.zip
Steps to reproduce:
1.Download the .POC files.
2.Execute the following command
: ./memcached -p 1234 -E .libs/default_engine.so
netcat localhost 1234 < poc
=================================================================
==3133==ERROR: AddressSanitizer: negative-size-param: (size=-2147483648)
    #0 0x4a75bd in __asan_memmove (/home/karas/arcus-memcached/memcached+0x4a75bd)
    #1 0x4e50da in try_read_network /home/karas/arcus-memcached/memcached.c:13929:13
    #2 0x4e50da in conn_read /home/karas/arcus-memcached/memcached.c:14157
    #3 0x4e0be3 in event_handler /home/karas/arcus-memcached/memcached.c:14592:12
    #4 0x7fc8e2ef14c8 in event_base_loop (/usr/lib/x86_64-linux-gnu/libevent-2.0.so.5+0xd4c8)
    #5 0x5b88d4 in worker_libevent /home/karas/arcus-memcached/thread.c:476:5
    #6 0x7fc8e2cce6b9 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x76b9)
    #7 0x7fc8e20d941c in clone /build/glibc-Cl5G7W/glibc-2.23/misc/../sysdeps/unix/sysv/linux/x86_64/clone.S:109

AddressSanitizer can not describe address in more detail (wild memory access suspected).
SUMMARY: AddressSanitizer: negative-size-param ??:0 __asan_memmove
Thread T2 created by T0 here:
    #0 0x4a5b30 in __interceptor_pthread_create (/home/karas/arcus-memcached/memcached+0x4a5b30)
    #1 0x5b805a in create_worker /home/karas/arcus-memcached/thread.c:387:16
    #2 0x5b805a in thread_init /home/karas/arcus-memcached/thread.c:1115
    #3 0x4f84e2 in main /home/karas/arcus-memcached/memcached.c:16249:5
    #4 0x7fc8e1ff282f in __libc_start_main /build/glibc-Cl5G7W/glibc-2.23/csu/../csu/libc-start.c:291

==3133==ABORTING

#0  __memmove_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:299
No locals.
#1  0x000000000040c340 in memmove (__len=<optimized out>, __src=<optimized out>, __dest=<optimized out>) at /usr/include/x86_64-linux-gnu/bits/string3.h:59
No locals.
#2  try_read_network (c=0x7ffff00323a8) at memcached.c:13929
        gotdata = READ_NO_DATA_RECEIVED
        res = <optimized out>
        num_allocs = 0x0
#3  conn_read (c=0x7ffff00323a8) at memcached.c:14157
        res = <optimized out>
#4  0x0000000000408f5e in event_handler (fd=<optimized out>, which=<optimized out>, arg=0x7ffff00323a8) at memcached.c:14592
        c = 0x7ffff00323a8
        __PRETTY_FUNCTION__ = "event_handler"
#5  0x00007ffff7b9e4c9 in event_base_loop () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5
No symbol table info available.
#6  0x000000000042f229 in worker_libevent (arg=0x691d60) at thread.c:476
        me = 0x691d60
        conn = <optimized out>
        item = <optimized out>
#7  0x00007ffff746e6ba in start_thread (arg=0x7ffff6460700) at pthread_create.c:333
        __res = <optimized out>
        pd = 0x7ffff6460700
        now = <optimized out>
        unwind_buf = {
          cancel_jmp_buf = {{
              jmp_buf = {0x7ffff6460700, 0x4a34a3e4a0c6e7f, 0x0, 0x7fffffffc52f, 0x7ffff64609c0, 0x7fffffffc7c0, 0xfb5ca6b5b4cc6e7f, 0xfb5ca4b386f66e7f},
              mask_was_saved = 0x0
            }},
          priv = {
            pad = {0x0, 0x0, 0x0, 0x0},
            data = {
              prev = 0x0,
              cleanup = 0x0,
              canceltype = 0x0
            }
          }
        }
        not_first_call = <optimized out>
        pagesize_m1 = <optimized out>
        sp = <optimized out>
        freesize = <optimized out>
        __PRETTY_FUNCTION__ = "start_thread"
#8  0x00007ffff71a441d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
No locals.

@gy741
Thank you for raising this issue.
This issue has been resolved by adding validation check for a given value length.
Refer to the commit : https://github.com/naver/arcus-memcached/commit/2453563390da7de7bca103da72f2a6f074c6201b


Update SSH Port 443 process to be useful.

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/authentication/troubleshooting-ssh/using-ssh-over-the-https-port
https://docs.github.com/en/get-started/using-github/troubleshooting-connectivity-problems
What changes are you suggesting?

Missing alternative in general troubleshooting to promote use of SSH over port 443.
Missing Emphasis that hostname changes to ssh.github.com
Missing repository example for git client rewrite to use 443 (vs ssh config)
Missing Known host changes that may be needed to use port 443.

Additional information
No response

@rp-jasonp Thanks for opening an issue and PR! ⚡

Mrs.d.com
Great day Job in Pakistan

``


WIP: feat!: support bulk renaming files in yazi

TODO:

[x] see if the integration tests don't produce false positives. It is possible that many of them should have failed
[ ] tests must pass in ci
[ ] both ways of reading events must be supported and tested

[ ] new way: using ya
[ ] old way: using > events.txt style shell redirection

[ ] using ya sub must be opt in for some time to allow users to adapt to this change (must not be a breaking change without a transition period)
[x] install yazi using https://github.com/cargo-bins/cargo-binstall to keep CI fast

Looks like the tests fail. I think it might be because the integration tests now require the bleeding edge version of yazi and ya, and the version installed might be too old.

On this branch right now, bulk renaming works nicely when the bleeding edge yazi and ya are used. Next, I need to make this opt-in instead of a breaking change, and make sure both ways are tested.
I want to have a transition period from using the current stable yazi to requiring the next version of yazi with ya available, as that will be needed for stuff that I have planned for the future. During this transition period, both approaches need to be supported and tested.

This is now ready to be released! I added a video demo to the original post.
I will merge this in a couple of days.


Only run pkg commands if there are discontinued packages to uninstall

Currently, if there are no outdated/discontinued MongoDB packages installed, we get this output:
Usage: pkg lock [-lqy] [-a|[-Cgix] ]
       pkg lock --has-locked-packages
       pkg unlock [-lqy] [-a|[-Cgix] ]
For more information see 'pkg help lock'.
Usage: pkg delete [-DfnqRy] [-Cgix] ...
       pkg delete [-Dnqy] -a

This is due to the loop still running even if the $old_mongos variable is empty. My changes make it so the pkg unlock/delete commands only run if there are packages to delete.

Superseded by #310


Add r-vctrs

Depends on #1303

Hmm i get this error
 × error └─ r-lifecycle 1.0.4 | 1.0.4 | 1.0.4 | 1.0.4 would require
 × error    └─ r-base >=4.3,<4.4.0a0, for which no candidates were found.
Error:   × Failed to resolve dependencies: Cannot solve the request because of: r-
  │ lifecycle >=1.0.4 cannot be installed because there are no viable options:
  │ └─ r-lifecycle 1.0.4 | 1.0.4 | 1.0.4 | 1.0.4 would require
  │    └─ r-base >=4.3,<4.4.0a0, for which no candidates were found.
  │
  ╰─▶ Cannot solve the request because of: r-lifecycle >=1.0.4 cannot be
      installed because there are no viable options:
      └─ r-lifecycle 1.0.4 | 1.0.4 | 1.0.4 | 1.0.4 would require
         └─ r-base >=4.3,<4.4.0a0, for which no candidates were found.

I guess r-lifecycle is built with the latest r-base (https://github.com/conda-forge/r-lifecycle-feedstock/pull/11)

This doesn't make sense...
╰─λ micromamba repoquery depends r-lifecycle
Using local repodata...

Name        Version Build           Channel     Subdir
──────────────────────────────────────────────────────────
r-base      4.4.1   h745b8e0_14     conda-forge linux-64
r-cli       3.6.3   r44h0d4f4ea_1   conda-forge linux-64
r-glue      1.7.0   r44hb1dbf0f_1   conda-forge linux-64
r-lifecycle 1.0.4   r44hc72bb7e_1   conda-forge noarch
r-rlang     1.1.4   r44ha18555a_1   conda-forge linux-64

This should be ready, just needs to be rebased on top of #1364 and #1365

Okay wasn't expecting this but worked right off the bat. Thanks for the reviews @IsabelParedes :)


Change test var name to match changes in cifmw

Changed var name to match the changes in this patch: https://github.com/openstack-k8s-operators/ci-framework/pull/2374/commits

Please keep the old variable around and default is value to the value of the new variable. In this way the code won't be broken. Otherwise we would need to merge several changes in a coordinate way with an high risk of breaking something.


cmake: Support custom out-of-tree toolchains

Add a new 'custom' option to ZEPHYR_TOOLCHAIN_VARIANT to support
custom cmake toolchains.
When used, the ZEPHYR_TOOLCHAIN_CMAKE_PATH environment variable must
be defined and point to a valid cmake toolchain file.
Signed-off-by: François Delawarde<EMAIL_ADDRESS>

Thanks for the review, I updated the commit to conform to the requested changes (including documentation and commit msg).


Default to latestif version is not provided.

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


Travis config is generated from a template

With this PR, metadatastore is using an autogenerated travis template.
The template can be found at https://github.com/ericdill/travis-little-helper.
Instructions for creating a new travis yml can be found in the readme.
Also added some badges for current dev build on anaconda.org/lightsource2-dev/metadatastore
and latest point release on anaconda.org/lightsource2/metadatastore

This is basically just a bunch of travis jiggery-pokery.  If anyone is interested in what is going on behind the scenes, I'm happy to explain. Otherwise, merge away. Or I can squash commits.  Let me know!
cc @danielballan @klauer @arkilic

Is this still a going concern?  If so it needs a rebase.


[Bug] execute sql error: datasource plugin 'doris' is not found

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
dolphinscheduler-3.2.0
使用dolphinscheduler调度doris，运行报错，提示没有找到doris数据源

What you expected to happen
[INFO] 2023-10-25 15:56:18.438 +0800 - can't find udf function resource
[ERROR] 2023-10-25 15:56:18.439 +0800 - execute sql error: datasource plugin 'doris' is not found
[ERROR] 2023-10-25 15:56:18.439 +0800 - sql task error
java.lang.RuntimeException: datasource plugin 'doris' is not found
How to reproduce

使用sql组件执行
insert into xf_ods_so_somain_copy1 select * from xf_ods_so_somain;
Anything else
No response
Version
3.2.x
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

Is this problem not a bug? How to solve it?

This is a code problem, I will submit the fix code later

It works without fixing it: Change your Doris data source to MYSQL, your IP, port write your Doris configuration, so you can use mysql jdbc connection Doris

This is how it is used now, but the doris data source is not easy to use.


Should preset.js include the manager?

We recently noticed a browser warning in our storybook addon at https://github.com/Lullabot/storybook-drupal-addon/pull/27.

storybook/drupal-addon was loaded twice, this could have bad side-effects

It seems like this export isn't required at all for addons to work: https://github.com/storybookjs/addon-kit/blob/main/preset.js#L5-L7
In our case, we've removed it, but it did come from this repository template. Is there some other reason it is required or useful? If not, can it be removed, or left in place commented as an example with details on why it's useful?

The present has been split into the manager.ts and preview.ts files. Here's the new syntax: https://github.com/storybookjs/addon-kit/tree/main/src/preset
It looks like when you bootstrapped the drupal-addon a while back so, you have the old syntax. But the fix you made updates it to the new syntax.


建议将项目中的 Server酱 链接换成推荐链接

您好，我是 Server酱的作者 Easy 。注意到您的项目中对接或提及了 Server酱，非常感谢对我们的支持。
这里有一个小建议。Server酱最近推出了「推荐返现计划」，您可以在项目中Server酱的官网链接后边加上推荐参数，这样在用户从这里进入Server酱并订阅会员后，您的项目将获得2元/单的佣金。
只需要用微信登录fx.ftqq.com ，然后开通计划就可以获得您的推荐链接，佣金会实时地转入开通账号的微信零钱中。
希望这个计划能让您的开源项目更好。

Hello, I am Easy, the author of ServerChan. I noticed that your project has integrated or mentioned ServerChan, and I am very grateful for that.
I have a small suggestion. ServerChan has recently launched a "Referral Cashback Program". You can add a referral parameter to the link to ServerChan's official website in your project. This way, when users enter ServerChan through your link and subscribe to a membership, your project will earn a commission of 2 RMB per subscription.
You just need to log in to fx.ftqq.com with WeChat, activate the program, and you will get your referral link. The commission will be instantly transferred to the WeChat Wallet of the account that activated the program.
Even though the earnings might not be substantial, I hope this program can provide some additional support for your open-source project.

谢谢提醒，有时间的时候我加一下。
---原始邮件---
发件人: @.>
发送时间: 2024年7月18日(周四) 晚上11:50
收件人: @.>;
抄送: @.***>;
主题: [guanguans/notify] 建议将项目中的 Server酱 链接换成推荐链接 (Issue #91)
您好，我是 Server酱的作者 Easy 。注意到您的项目中对接或提及了 Server酱，非常感谢对我们的支持。
这里有一个小建议。Server酱最近推出了「推荐返现计划」，您可以在项目中Server酱的官网链接后边加上推荐参数，这样在用户从这里进入Server酱并订阅会员后，您的项目将获得2元/单的佣金。
只需要用微信登录fx.ftqq.com ，然后开通计划就可以获得您的推荐链接，佣金会实时地转入开通账号的微信零钱中。
希望这个计划能让您的开源项目更好。
Hello, I am Easy, the author of ServerChan. I noticed that your project has integrated or mentioned ServerChan, and I am very grateful for that.
I have a small suggestion. ServerChan has recently launched a "Referral Cashback Program". You can add a referral parameter to the link to ServerChan's official website in your project. This way, when users enter ServerChan through your link and subscribe to a membership, your project will earn a commission of 2 RMB per subscription.
You just need to log in to fx.ftqq.com with WeChat, activate the program, and you will get your referral link. The commission will be instantly transferred to the WeChat Wallet of the account that activated the program.
Even though the earnings might not be substantial, I hope this program can provide some additional support for your open-source project.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


Sections <IP_ADDRESS> and 2.11.5 - Nonfunctional Figures

A couple of the figures (for the File browse pane in RStudio showing .Renviron file." and the "example of camera data (DP1.30010.001) from the San Joaquin...") are not functioning - instead of the image, they are revealing the code between the   tags. The actual image files are accessible (one on NEON's github, one on the local site), so I'm not sure why they aren't working, since there are no functional  environments in the first two chapters.

Awesome, thanks for catching that David!

@dfailing , do you mean the NEON chapter or the PhenoCam chapter?

The NEON chapter, and the two sections I referenced in the title of this Issue - Sections <IP_ADDRESS> and 2.11.5. I wonder if anyone else is having this issue, or if it's my browser not rendering things properly. I attempted to attach screenshots to this comment of what I'm seeing.

Thanks, fixed it!


Add Nebula scheduled backup CRD

What type of PR is this?

[ ] bug
[x] feature
[ ] enhancement

What problem(s) does this PR solve?
Issue(s) number:
https://github.com/vesoft-inc/nebula-operator/issues/404
Description:
Add Nebula Scheduled backup CRD
How do you solve it?
Added a CRD for a Nebula scheduled backup type
Special notes for your reviewer, ex. impact of this fix, design document, etc:

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


Error install xfastertransformer on CentOS 7.6

在centOS7 上pip install xfastertransformer后， import xfastertransformer 提示如下错误
>>> import xfastertransformer
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/root/.conda/envs/xft_test/lib/python3.8/site-packages/xfastertransformer/__init__.py", line 31, in <module>
    torch.classes.load_library(os.path.dirname(os.path.abspath(__file__)) + "/libxfastertransformer_pt.so")
  File "/root/.conda/envs/xft_test/lib/python3.8/site-packages/torch/_classes.py", line 51, in load_library
    torch.ops.load_library(path)
  File "/root/.conda/envs/xft_test/lib/python3.8/site-packages/torch/_ops.py", line 643, in load_library
    ctypes.CDLL(path)
  File "/root/.conda/envs/xft_test/lib/python3.8/ctypes/__init__.py", line 373, in __init__
    self._handle = _dlopen(self._name, mode)
OSError: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /root/.conda/envs/xft_test/lib/python3.8/site-packages/xfastertransformer/libxfastertransformer_pt.so)

Solved through update libstdc++.so.6


Dependency won't pass to next repository on failure

We just upgraded several of our projects to 4.7 and things have been blowing up all over the place, to the point where many of our projects were forced to downgrade back to 4.2.  I just read that you changed the behavior in 4.3 so that if a dependency repository returns an error, it fails the build instead of falling thru to the next repository in the stack.
https://docs.gradle.org/4.3/release-notes.html?_ga=2.219243034.208527151.1528888504-1998248491.1525192646#avoid-checking-other-repositories-when-dependency-resolution-in-one-repository-fails
I need a way to renable the old logic.  Our problem is that due to our firewall and internal security scanning systems, our artifactory server's connection to the internet is, shall we say, unstable.  It constantly gets false hits on our on the wire bug and virus scanner.  When it does get a  hit, the scanner nukes the network connection, giving artifactory a timeout error.  This in turn gets to the client as a failed connection, and now gradle fails the build.
Now, with 4.2, this was no problem because gradle would just move on to the next repository and try downloading the file from another remote repo in artifactory, usually succeeding.  But, now with this change, builds are blowing up all over the place
Expected Behavior
I get how people would want it fail, i really can see that argument.  But at the same time this has damn near crippled us.  I need some kind of setting that i can put in the build file to say, if there's an error, move to the next repo.  Even a code snippet that i can plug into our enterprise level plugins to override the error handling would be fine.  I need something to kick this thing hard enough to move to the next repo on a failure.  The way our systems work, its very common for the first repo to fail, very rare for all 20 or so to fail.
Current Behavior
as per the link above, this logic was changed in 4.3 to fail the build on connection failure pulling down dependencies
Context
We have so many security scanners listening over the wire and various other tooling managing internet connections, that we constantly get dropped connections.  Its a way of life here.  Most systems we run handle the connection drops in stride, this one did, until we upgraded to 4.7
Your Environment
happens on all environments we run, win7, win10, mac.

That would mean non-reproducible builds, giving you potentially different/untrusted artifacts depending on the environment. See #4629 for a solution that I think would be more appropriate. Would that be a good solution for you?

It may help some cases.  but unfortunately if our system gray flags a site because of a hack, or ddos, or their coffee is at 154 degrees instead of 157, its gray flagged for hours/days/weeks.  retrys won't help, it has to fall thru to the next repo in the chain to try from a different site.
im limited on how i can fix it with artifactory, and changing the order of the repos in my init.gradle is out of the question because i would need a FTE who's whole job is updating and redistributing the file that holds that info, day in and day out.
Is there a way where i can inject my own error handler into that method?  nothing about my network and associated security systems is typical so i imagine the number of people with this problem is limited.  but if i had a way to inject my own error handler via my corp JVM plugin we use across the board, that would solve my problem.

I'm not sure I understand the situation - Why can't you shield your build from external outages using your internal Artifactory instance? I.e. your build has exactly one repo (your artifactory mirror) and Artifactory takes care of holding everything you need inside your organization instead of Gradle trying to get things from the internet.
No, there is no way to change this error handling at the moment.

because due to issues outside my control, i don't have one repo, i have close to 20.  gotta be pushing close to 70 if you count the remotes individually, and i believe around 18 local repos.  We tried one repo to rule them all in the very early days of the implement, but things went bad within minutes for a variety of reasons.  I have to keep things separate and in specific orders.
like i said, im limited on how i can fix it with artifactory

Alright so you have plenty of repos in Artifactory. Still that should shield you from outside failures by mirroring. So why does that not work out?

The change is to improve reproducibility and will stay.
Alternatives are to hide this with a proxy repository, or have conditional repository declarations depending on the network / work environment.


Fix repeat option detection - Closes home-assistant/hassio-addons#375

Fixes https://github.com/home-assistant/hassio-addons/issues/375

sorry faulty request


[BUG] Windows 1click installer no longer working

Traceback (most recent call last):
File "E:\lama-cleaner\installer\Scripts\conda-unpack-script.py", line 226, in
update_prefix(os.path.join(new_prefix, path), new_prefix,
File "E:\lama-cleaner\installer\Scripts\conda-unpack-script.py", line 66, in update_prefix
with open(path, 'rb+') as fh:
FileNotFoundError: [Errno 2] No such file or directory: 'E:\lama-cleaner\installer\Library\bin\libcrypto-1_1-x64.dll.c~.conda_trash'
Collecting package metadata (current_repodata.json): done
Solving environment: done
==> WARNING: A newer version of conda exists. <==
current version: 23.7.4
latest version: 23.9.0
Please update conda by running
$ conda update -n base -c conda-forge conda

Or to minimize the number of packages updated during conda update use
 conda install conda=23.9.0

All requested packages already installed.
Looking in indexes: https://pypi.org/simple, https://download.pytorch.org/whl/cu117
Requirement already satisfied: torch==1.13.1+cu117 in e:\lama-cleaner\installer\lib\site-packages (1.13.1+cu117)
Requirement already satisfied: torchvision==0.14.1+cu117 in e:\lama-cleaner\installer\lib\site-packages (0.14.1+cu117)
Requirement already satisfied: typing-extensions in e:\lama-cleaner\installer\lib\site-packages (from torch==1.13.1+cu117) (4.8.0)
Requirement already satisfied: pillow!=8.3.,>=5.3.0 in e:\lama-cleaner\installer\lib\site-packages (from torchvision==0.14.1+cu117) (10.0.1)
Requirement already satisfied: requests in e:\lama-cleaner\installer\lib\site-packages (from torchvision==0.14.1+cu117) (2.28.1)
Requirement already satisfied: numpy in e:\lama-cleaner\installer\lib\site-packages (from torchvision==0.14.1+cu117) (1.26.1)
Requirement already satisfied: certifi>=2017.4.17 in e:\lama-cleaner\installer\lib\site-packages (from requests->torchvision==0.14.1+cu117) (2023.7.22)
Requirement already satisfied: idna<4,>=2.5 in e:\lama-cleaner\installer\lib\site-packages (from requests->torchvision==0.14.1+cu117) (3.4)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in e:\lama-cleaner\installer\lib\site-packages (from requests->torchvision==0.14.1+cu117) (1.26.12)
Requirement already satisfied: charset-normalizer<3,>=2 in e:\lama-cleaner\installer\lib\site-packages (from requests->torchvision==0.14.1+cu117) (2.0.4)
Requirement already satisfied: xformers==0.0.16 in e:\lama-cleaner\installer\lib\site-packages (0.0.16)
Requirement already satisfied: numpy in e:\lama-cleaner\installer\lib\site-packages (from xformers==0.0.16) (1.26.1)
Requirement already satisfied: torch==1.13.1 in e:\lama-cleaner\installer\lib\site-packages (from xformers==0.0.16) (1.13.1+cu117)
Requirement already satisfied: pyre-extensions==0.0.23 in e:\lama-cleaner\installer\lib\site-packages (from xformers==0.0.16) (0.0.23)
Requirement already satisfied: typing-extensions in e:\lama-cleaner\installer\lib\site-packages (from pyre-extensions==0.0.23->xformers==0.0.16) (4.8.0)
Requirement already satisfied: typing-inspect in e:\lama-cleaner\installer\lib\site-packages (from pyre-extensions==0.0.23->xformers==0.0.16) (0.9.0)
Requirement already satisfied: mypy-extensions>=0.3.0 in e:\lama-cleaner\installer\lib\site-packages (from typing-inspect->pyre-extensions==0.0.23->xformers==0.0.16) (1.0.0)
Requirement already satisfied: lama-cleaner in e:\lama-cleaner\installer\lib\site-packages (1.2.4)
Requirement already satisfied: torch>=1.9.0 in e:\lama-cleaner\installer\lib\site-packages (from lama-cleaner) (1.13.1+cu117)
Requirement already satisfied: loguru in e:\lama-cleaner\installer\lib\site-packages (from lama-cleaner) (0.7.2)
Requirement already satisfied: diffusers==0.16.1 in e:\lama-cleaner\installer\lib\site-packages (from lama-cleaner) (0.16.1)
Requirement already satisfied: flask-cors in e:\lama-cleaner\installer\lib\site-packages (from lama-cleaner) (4.0.0)
Requirement already satisfied: controlnet-aux==0.0.3 in e:\lama-cleaner\installer\lib\site-packages (from lama-cleaner) (0.0.3)
Requirement already satisfied: flaskwebgui==0.3.5 in e:\lama-cleaner\installer\lib\site-packages (from lama-cleaner) (0.3.5)
Requirement already satisfied: pydantic in e:\lama-cleaner\installer\lib\site-packages (from lama-cleaner) (2.4.2)
Requirement already satisfied: transformers==4.27.4 in e:\lama-cleaner\installer\lib\site-packages (from lama-cleaner) (4.27.4)
Requirement already satisfied: simple-websocket in e:\lama-cleaner\installer\lib\site-packages (from lama-cleaner) (1.0.0)
Requirement already satisfied: omegaconf in e:\lama-cleaner\installer\lib\site-packages (from lama-cleaner) (2.3.0)
Requirement already satisfied: safetensors in e:\lama-cleaner\installer\lib\site-packages (from lama-cleaner) (0.4.0)
Requirement already satisfied: rich in e:\lama-cleaner\installer\lib\site-packages (from lama-cleaner) (12.5.1)
Requirement already satisfied: gradio in e:\lama-cleaner\installer\lib\site-packages (from lama-cleaner) (4.0.2)
Requirement already satisfied: yacs in e:\lama-cleaner\installer\lib\site-packages (from lama-cleaner) (0.1.8)
Requirement already satisfied: opencv-python in e:\lama-cleaner\installer\lib\site-packages (from lama-cleaner) (<IP_ADDRESS>)
Requirement already satisfied: flask==2.2.3 in e:\lama-cleaner\installer\lib\site-packages (from lama-cleaner) (2.2.3)
Requirement already satisfied: flask-socketio in e:\lama-cleaner\installer\lib\site-packages (from lama-cleaner) (5.3.6)
Requirement already satisfied: piexif==1.1.3 in e:\lama-cleaner\installer\lib\site-packages (from lama-cleaner) (1.1.3)
Requirement already satisfied: werkzeug==2.2.2 in e:\lama-cleaner\installer\lib\site-packages (from lama-cleaner) (2.2.2)
Requirement already satisfied: numpy in e:\lama-cleaner\installer\lib\site-packages (from controlnet-aux==0.0.3->lama-cleaner) (1.26.1)
Requirement already satisfied: timm in e:\lama-cleaner\installer\lib\site-packages (from controlnet-aux==0.0.3->lama-cleaner) (0.9.8)
Requirement already satisfied: huggingface-hub in e:\lama-cleaner\installer\lib\site-packages (from controlnet-aux==0.0.3->lama-cleaner) (0.18.0)
Requirement already satisfied: filelock in e:\lama-cleaner\installer\lib\site-packages (from controlnet-aux==0.0.3->lama-cleaner) (3.13.1)
Requirement already satisfied: Pillow in e:\lama-cleaner\installer\lib\site-packages (from controlnet-aux==0.0.3->lama-cleaner) (10.0.1)
Requirement already satisfied: importlib-metadata in e:\lama-cleaner\installer\lib\site-packages (from controlnet-aux==0.0.3->lama-cleaner) (6.8.0)
Requirement already satisfied: einops in e:\lama-cleaner\installer\lib\site-packages (from controlnet-aux==0.0.3->lama-cleaner) (0.7.0)
Requirement already satisfied: torchvision in e:\lama-cleaner\installer\lib\site-packages (from controlnet-aux==0.0.3->lama-cleaner) (0.14.1+cu117)
Requirement already satisfied: scikit-image in e:\lama-cleaner\installer\lib\site-packages (from controlnet-aux==0.0.3->lama-cleaner) (0.22.0)
Requirement already satisfied: scipy in e:\lama-cleaner\installer\lib\site-packages (from controlnet-aux==0.0.3->lama-cleaner) (1.11.3)
Requirement already satisfied: regex!=2019.12.17 in e:\lama-cleaner\installer\lib\site-packages (from diffusers==0.16.1->lama-cleaner) (2023.10.3)
Requirement already satisfied: requests in e:\lama-cleaner\installer\lib\site-packages (from diffusers==0.16.1->lama-cleaner) (2.28.1)
Requirement already satisfied: click>=8.0 in e:\lama-cleaner\installer\lib\site-packages (from flask==2.2.3->lama-cleaner) (8.1.7)
Requirement already satisfied: Jinja2>=3.0 in e:\lama-cleaner\installer\lib\site-packages (from flask==2.2.3->lama-cleaner) (3.1.2)
Requirement already satisfied: itsdangerous>=2.0 in e:\lama-cleaner\installer\lib\site-packages (from flask==2.2.3->lama-cleaner) (2.1.2)
Requirement already satisfied: whichcraft in e:\lama-cleaner\installer\lib\site-packages (from flaskwebgui==0.3.5->lama-cleaner) (0.6.1)
Requirement already satisfied: tqdm>=4.27 in e:\lama-cleaner\installer\lib\site-packages (from transformers==4.27.4->lama-cleaner) (4.64.1)
Requirement already satisfied: tokenizers!=0.11.3,<0.14,>=0.11.1 in e:\lama-cleaner\installer\lib\site-packages (from transformers==4.27.4->lama-cleaner) (0.13.3)
Requirement already satisfied: pyyaml>=5.1 in e:\lama-cleaner\installer\lib\site-packages (from transformers==4.27.4->lama-cleaner) (6.0.1)
Requirement already satisfied: packaging>=20.0 in e:\lama-cleaner\installer\lib\site-packages (from transformers==4.27.4->lama-cleaner) (23.2)
Requirement already satisfied: MarkupSafe>=2.1.1 in e:\lama-cleaner\installer\lib\site-packages (from werkzeug==2.2.2->lama-cleaner) (2.1.3)
Requirement already satisfied: typing-extensions in e:\lama-cleaner\installer\lib\site-packages (from torch>=1.9.0->lama-cleaner) (4.8.0)
Requirement already satisfied: python-socketio>=5.0.2 in e:\lama-cleaner\installer\lib\site-packages (from flask-socketio->lama-cleaner) (5.10.0)
Requirement already satisfied: python-multipart in e:\lama-cleaner\installer\lib\site-packages (from gradio->lama-cleaner) (0.0.6)
Requirement already satisfied: semantic-version~=2.0 in e:\lama-cleaner\installer\lib\site-packages (from gradio->lama-cleaner) (2.10.0)
Requirement already satisfied: altair<6.0,>=4.2.0 in e:\lama-cleaner\installer\lib\site-packages (from gradio->lama-cleaner) (5.1.2)
Requirement already satisfied: importlib-resources<7.0,>=1.3 in e:\lama-cleaner\installer\lib\site-packages (from gradio->lama-cleaner) (6.1.0)
Requirement already satisfied: websockets<12.0,>=10.0 in e:\lama-cleaner\installer\lib\site-packages (from gradio->lama-cleaner) (11.0.3)
Requirement already satisfied: aiofiles<24.0,>=22.0 in e:\lama-cleaner\installer\lib\site-packages (from gradio->lama-cleaner) (23.2.1)
Requirement already satisfied: pydub in e:\lama-cleaner\installer\lib\site-packages (from gradio->lama-cleaner) (0.25.1)
Requirement already satisfied: ffmpy in e:\lama-cleaner\installer\lib\site-packages (from gradio->lama-cleaner) (0.3.1)
Requirement already satisfied: orjson~=3.0 in e:\lama-cleaner\installer\lib\site-packages (from gradio->lama-cleaner) (3.9.10)
Requirement already satisfied: tomlkit==0.12.0 in e:\lama-cleaner\installer\lib\site-packages (from gradio->lama-cleaner) (0.12.0)
Requirement already satisfied: typer[all]<1.0,>=0.9 in e:\lama-cleaner\installer\lib\site-packages (from gradio->lama-cleaner) (0.9.0)
Requirement already satisfied: fastapi in e:\lama-cleaner\installer\lib\site-packages (from gradio->lama-cleaner) (0.104.1)
Requirement already satisfied: matplotlib~=3.0 in e:\lama-cleaner\installer\lib\site-packages (from gradio->lama-cleaner) (3.8.0)
Requirement already satisfied: pandas<3.0,>=1.0 in e:\lama-cleaner\installer\lib\site-packages (from gradio->lama-cleaner) (2.1.2)
Requirement already satisfied: uvicorn>=0.14.0 in e:\lama-cleaner\installer\lib\site-packages (from gradio->lama-cleaner) (0.23.2)
Requirement already satisfied: gradio-client==0.7.0 in e:\lama-cleaner\installer\lib\site-packages (from gradio->lama-cleaner) (0.7.0)
Requirement already satisfied: httpx in e:\lama-cleaner\installer\lib\site-packages (from gradio->lama-cleaner) (0.25.0)
Requirement already satisfied: fsspec in e:\lama-cleaner\installer\lib\site-packages (from gradio-client==0.7.0->gradio->lama-cleaner) (2023.10.0)
Requirement already satisfied: pydantic-core==2.10.1 in e:\lama-cleaner\installer\lib\site-packages (from pydantic->lama-cleaner) (2.10.1)
Requirement already satisfied: annotated-types>=0.4.0 in e:\lama-cleaner\installer\lib\site-packages (from pydantic->lama-cleaner) (0.6.0)
Requirement already satisfied: win32-setctime>=1.0.0 in e:\lama-cleaner\installer\lib\site-packages (from loguru->lama-cleaner) (1.1.0)
Requirement already satisfied: colorama>=0.3.4 in e:\lama-cleaner\installer\lib\site-packages (from loguru->lama-cleaner) (0.4.5)
Requirement already satisfied: antlr4-python3-runtime==4.9. in e:\lama-cleaner\installer\lib\site-packages (from omegaconf->lama-cleaner) (4.9.3)
Requirement already satisfied: commonmark<0.10.0,>=0.9.0 in e:\lama-cleaner\installer\lib\site-packages (from rich->lama-cleaner) (0.9.1)
Requirement already satisfied: pygments<3.0.0,>=2.6.0 in e:\lama-cleaner\installer\lib\site-packages (from rich->lama-cleaner) (2.11.2)
Requirement already satisfied: wsproto in e:\lama-cleaner\installer\lib\site-packages (from simple-websocket->lama-cleaner) (1.2.0)
Requirement already satisfied: jsonschema>=3.0 in e:\lama-cleaner\installer\lib\site-packages (from altair<6.0,>=4.2.0->gradio->lama-cleaner) (4.19.2)
Requirement already satisfied: toolz in e:\lama-cleaner\installer\lib\site-packages (from altair<6.0,>=4.2.0->gradio->lama-cleaner) (0.11.2)
Requirement already satisfied: fonttools>=4.22.0 in e:\lama-cleaner\installer\lib\site-packages (from matplotlib~=3.0->gradio->lama-cleaner) (4.43.1)
Requirement already satisfied: cycler>=0.10 in e:\lama-cleaner\installer\lib\site-packages (from matplotlib~=3.0->gradio->lama-cleaner) (0.12.1)
Requirement already satisfied: kiwisolver>=1.0.1 in e:\lama-cleaner\installer\lib\site-packages (from matplotlib~=3.0->gradio->lama-cleaner) (1.4.5)
Requirement already satisfied: contourpy>=1.0.1 in e:\lama-cleaner\installer\lib\site-packages (from matplotlib~=3.0->gradio->lama-cleaner) (1.1.1)
Requirement already satisfied: pyparsing>=2.3.1 in e:\lama-cleaner\installer\lib\site-packages (from matplotlib~=3.0->gradio->lama-cleaner) (3.1.1)
Requirement already satisfied: python-dateutil>=2.7 in e:\lama-cleaner\installer\lib\site-packages (from matplotlib~=3.0->gradio->lama-cleaner) (2.8.2)
Requirement already satisfied: tzdata>=2022.1 in e:\lama-cleaner\installer\lib\site-packages (from pandas<3.0,>=1.0->gradio->lama-cleaner) (2023.3)
Requirement already satisfied: pytz>=2020.1 in e:\lama-cleaner\installer\lib\site-packages (from pandas<3.0,>=1.0->gradio->lama-cleaner) (2023.3.post1)
Requirement already satisfied: bidict>=0.21.0 in e:\lama-cleaner\installer\lib\site-packages (from python-socketio>=5.0.2->flask-socketio->lama-cleaner) (0.22.1)
Requirement already satisfied: python-engineio>=4.8.0 in e:\lama-cleaner\installer\lib\site-packages (from python-socketio>=5.0.2->flask-socketio->lama-cleaner) (4.8.0)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in e:\lama-cleaner\installer\lib\site-packages (from requests->diffusers==0.16.1->lama-cleaner) (1.26.12)
Requirement already satisfied: charset-normalizer<3,>=2 in e:\lama-cleaner\installer\lib\site-packages (from requests->diffusers==0.16.1->lama-cleaner) (2.0.4)
Requirement already satisfied: idna<4,>=2.5 in e:\lama-cleaner\installer\lib\site-packages (from requests->diffusers==0.16.1->lama-cleaner) (3.4)
Requirement already satisfied: certifi>=2017.4.17 in e:\lama-cleaner\installer\lib\site-packages (from requests->diffusers==0.16.1->lama-cleaner) (2023.7.22)
Requirement already satisfied: shellingham<2.0.0,>=1.3.0 in e:\lama-cleaner\installer\lib\site-packages (from typer[all]<1.0,>=0.9->gradio->lama-cleaner) (1.5.4)
Requirement already satisfied: h11>=0.8 in e:\lama-cleaner\installer\lib\site-packages (from uvicorn>=0.14.0->gradio->lama-cleaner) (0.14.0)
Requirement already satisfied: anyio<4.0.0,>=3.7.1 in e:\lama-cleaner\installer\lib\site-packages (from fastapi->gradio->lama-cleaner) (3.7.1)
Requirement already satisfied: starlette<0.28.0,>=0.27.0 in e:\lama-cleaner\installer\lib\site-packages (from fastapi->gradio->lama-cleaner) (0.27.0)
Requirement already satisfied: httpcore<0.19.0,>=0.18.0 in e:\lama-cleaner\installer\lib\site-packages (from httpx->gradio->lama-cleaner) (0.18.0)
Requirement already satisfied: sniffio in e:\lama-cleaner\installer\lib\site-packages (from httpx->gradio->lama-cleaner) (1.3.0)
Requirement already satisfied: zipp>=0.5 in e:\lama-cleaner\installer\lib\site-packages (from importlib-metadata->controlnet-aux==0.0.3->lama-cleaner) (3.17.0)
Requirement already satisfied: imageio>=2.27 in e:\lama-cleaner\installer\lib\site-packages (from scikit-image->controlnet-aux==0.0.3->lama-cleaner) (2.31.6)
Requirement already satisfied: tifffile>=2022.8.12 in e:\lama-cleaner\installer\lib\site-packages (from scikit-image->controlnet-aux==0.0.3->lama-cleaner) (2023.9.26)
Requirement already satisfied: networkx>=2.8 in e:\lama-cleaner\installer\lib\site-packages (from scikit-image->controlnet-aux==0.0.3->lama-cleaner) (3.2.1)
Requirement already satisfied: lazy_loader>=0.3 in e:\lama-cleaner\installer\lib\site-packages (from scikit-image->controlnet-aux==0.0.3->lama-cleaner) (0.3)
Requirement already satisfied: exceptiongroup in e:\lama-cleaner\installer\lib\site-packages (from anyio<4.0.0,>=3.7.1->fastapi->gradio->lama-cleaner) (1.1.3)
Requirement already satisfied: attrs>=22.2.0 in e:\lama-cleaner\installer\lib\site-packages (from jsonschema>=3.0->altair<6.0,>=4.2.0->gradio->lama-cleaner) (23.1.0)
Requirement already satisfied: rpds-py>=0.7.1 in e:\lama-cleaner\installer\lib\site-packages (from jsonschema>=3.0->altair<6.0,>=4.2.0->gradio->lama-cleaner) (0.10.6)
Requirement already satisfied: jsonschema-specifications>=2023.03.6 in e:\lama-cleaner\installer\lib\site-packages (from jsonschema>=3.0->altair<6.0,>=4.2.0->gradio->lama-cleaner) (2023.7.1)
Requirement already satisfied: referencing>=0.28.4 in e:\lama-cleaner\installer\lib\site-packages (from jsonschema>=3.0->altair<6.0,>=4.2.0->gradio->lama-cleaner) (0.30.2)
Requirement already satisfied: six>=1.5 in e:\lama-cleaner\installer\lib\site-packages (from python-dateutil>=2.7->matplotlib~=3.0->gradio->lama-cleaner) (1.16.0)

Platform: Windows-10-10.0.22621-SP0
Python version: 3.10.6
torch: 1.13.1+cu117
torchvision: 0.14.1+cu117
Pillow: 10.0.1
diffusers: 0.16.1
transformers: 4.27.4
opencv-python: <IP_ADDRESS>
xformers: 0.0.16
accelerate: N/A
lama-cleaner: 1.2.4
rembg: 2.0.52
realesrgan: 0.3.0
gfpgan: 1.3.8

Requirement already satisfied: rembg in e:\lama-cleaner\installer\lib\site-packages (2.0.52)
Requirement already satisfied: tqdm in e:\lama-cleaner\installer\lib\site-packages (from rembg) (4.64.1)
Requirement already satisfied: pillow in e:\lama-cleaner\installer\lib\site-packages (from rembg) (10.0.1)
Requirement already satisfied: scikit-image in e:\lama-cleaner\installer\lib\site-packages (from rembg) (0.22.0)
Requirement already satisfied: onnxruntime in e:\lama-cleaner\installer\lib\site-packages (from rembg) (1.16.1)
Requirement already satisfied: opencv-python-headless in e:\lama-cleaner\installer\lib\site-packages (from rembg) (<IP_ADDRESS>)
Requirement already satisfied: jsonschema in e:\lama-cleaner\installer\lib\site-packages (from rembg) (4.19.2)
Requirement already satisfied: pymatting in e:\lama-cleaner\installer\lib\site-packages (from rembg) (1.1.10)
Requirement already satisfied: numpy in e:\lama-cleaner\installer\lib\site-packages (from rembg) (1.26.1)
Requirement already satisfied: pooch in e:\lama-cleaner\installer\lib\site-packages (from rembg) (1.8.0)
Requirement already satisfied: scipy in e:\lama-cleaner\installer\lib\site-packages (from rembg) (1.11.3)
Requirement already satisfied: jsonschema-specifications>=2023.03.6 in e:\lama-cleaner\installer\lib\site-packages (from jsonschema->rembg) (2023.7.1)
Requirement already satisfied: rpds-py>=0.7.1 in e:\lama-cleaner\installer\lib\site-packages (from jsonschema->rembg) (0.10.6)
Requirement already satisfied: attrs>=22.2.0 in e:\lama-cleaner\installer\lib\site-packages (from jsonschema->rembg) (23.1.0)
Requirement already satisfied: referencing>=0.28.4 in e:\lama-cleaner\installer\lib\site-packages (from jsonschema->rembg) (0.30.2)
Requirement already satisfied: flatbuffers in e:\lama-cleaner\installer\lib\site-packages (from onnxruntime->rembg) (23.5.26)
Requirement already satisfied: sympy in e:\lama-cleaner\installer\lib\site-packages (from onnxruntime->rembg) (1.12)
Requirement already satisfied: packaging in e:\lama-cleaner\installer\lib\site-packages (from onnxruntime->rembg) (23.2)
Requirement already satisfied: protobuf in e:\lama-cleaner\installer\lib\site-packages (from onnxruntime->rembg) (4.24.4)
Requirement already satisfied: coloredlogs in e:\lama-cleaner\installer\lib\site-packages (from onnxruntime->rembg) (15.0.1)
Requirement already satisfied: platformdirs>=2.5.0 in e:\lama-cleaner\installer\lib\site-packages (from pooch->rembg) (3.11.0)
Requirement already satisfied: requests>=2.19.0 in e:\lama-cleaner\installer\lib\site-packages (from pooch->rembg) (2.28.1)
Requirement already satisfied: numba!=0.49.0 in e:\lama-cleaner\installer\lib\site-packages (from pymatting->rembg) (0.58.1)
Requirement already satisfied: lazy_loader>=0.3 in e:\lama-cleaner\installer\lib\site-packages (from scikit-image->rembg) (0.3)
Requirement already satisfied: networkx>=2.8 in e:\lama-cleaner\installer\lib\site-packages (from scikit-image->rembg) (3.2.1)
Requirement already satisfied: imageio>=2.27 in e:\lama-cleaner\installer\lib\site-packages (from scikit-image->rembg) (2.31.6)
Requirement already satisfied: tifffile>=2022.8.12 in e:\lama-cleaner\installer\lib\site-packages (from scikit-image->rembg) (2023.9.26)
Requirement already satisfied: colorama in e:\lama-cleaner\installer\lib\site-packages (from tqdm->rembg) (0.4.5)
Requirement already satisfied: llvmlite<0.42,>=0.41.0dev0 in e:\lama-cleaner\installer\lib\site-packages (from numba!=0.49.0->pymatting->rembg) (0.41.1)
Requirement already satisfied: idna<4,>=2.5 in e:\lama-cleaner\installer\lib\site-packages (from requests>=2.19.0->pooch->rembg) (3.4)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in e:\lama-cleaner\installer\lib\site-packages (from requests>=2.19.0->pooch->rembg) (1.26.12)
Requirement already satisfied: charset-normalizer<3,>=2 in e:\lama-cleaner\installer\lib\site-packages (from requests>=2.19.0->pooch->rembg) (2.0.4)
Requirement already satisfied: certifi>=2017.4.17 in e:\lama-cleaner\installer\lib\site-packages (from requests>=2.19.0->pooch->rembg) (2023.7.22)
Requirement already satisfied: humanfriendly>=9.1 in e:\lama-cleaner\installer\lib\site-packages (from coloredlogs->onnxruntime->rembg) (10.0)
Requirement already satisfied: mpmath>=0.19 in e:\lama-cleaner\installer\lib\site-packages (from sympy->onnxruntime->rembg) (1.3.0)
Requirement already satisfied: pyreadline3 in e:\lama-cleaner\installer\lib\site-packages (from humanfriendly>=9.1->coloredlogs->onnxruntime->rembg) (3.4.1)
Requirement already satisfied: realesrgan in e:\lama-cleaner\installer\lib\site-packages (0.3.0)
Requirement already satisfied: torch>=1.7 in e:\lama-cleaner\installer\lib\site-packages (from realesrgan) (1.13.1+cu117)
Requirement already satisfied: basicsr>=1.4.2 in e:\lama-cleaner\installer\lib\site-packages (from realesrgan) (1.4.2)
Requirement already satisfied: facexlib>=0.2.5 in e:\lama-cleaner\installer\lib\site-packages (from realesrgan) (0.3.0)
Requirement already satisfied: opencv-python in e:\lama-cleaner\installer\lib\site-packages (from realesrgan) (<IP_ADDRESS>)
Requirement already satisfied: tqdm in e:\lama-cleaner\installer\lib\site-packages (from realesrgan) (4.64.1)
Requirement already satisfied: torchvision in e:\lama-cleaner\installer\lib\site-packages (from realesrgan) (0.14.1+cu117)
Requirement already satisfied: Pillow in e:\lama-cleaner\installer\lib\site-packages (from realesrgan) (10.0.1)
Requirement already satisfied: numpy in e:\lama-cleaner\installer\lib\site-packages (from realesrgan) (1.26.1)
Requirement already satisfied: gfpgan>=1.3.5 in e:\lama-cleaner\installer\lib\site-packages (from realesrgan) (1.3.8)
Requirement already satisfied: addict in e:\lama-cleaner\installer\lib\site-packages (from basicsr>=1.4.2->realesrgan) (2.4.0)
Requirement already satisfied: scikit-image in e:\lama-cleaner\installer\lib\site-packages (from basicsr>=1.4.2->realesrgan) (0.22.0)
Requirement already satisfied: yapf in e:\lama-cleaner\installer\lib\site-packages (from basicsr>=1.4.2->realesrgan) (0.40.2)
Requirement already satisfied: future in e:\lama-cleaner\installer\lib\site-packages (from basicsr>=1.4.2->realesrgan) (0.18.2)
Requirement already satisfied: tb-nightly in e:\lama-cleaner\installer\lib\site-packages (from basicsr>=1.4.2->realesrgan) (2.16.0a20231031)
Requirement already satisfied: pyyaml in e:\lama-cleaner\installer\lib\site-packages (from basicsr>=1.4.2->realesrgan) (6.0.1)
Requirement already satisfied: scipy in e:\lama-cleaner\installer\lib\site-packages (from basicsr>=1.4.2->realesrgan) (1.11.3)
Requirement already satisfied: requests in e:\lama-cleaner\installer\lib\site-packages (from basicsr>=1.4.2->realesrgan) (2.28.1)
Requirement already satisfied: lmdb in e:\lama-cleaner\installer\lib\site-packages (from basicsr>=1.4.2->realesrgan) (1.4.1)
Requirement already satisfied: filterpy in e:\lama-cleaner\installer\lib\site-packages (from facexlib>=0.2.5->realesrgan) (1.4.5)
Requirement already satisfied: numba in e:\lama-cleaner\installer\lib\site-packages (from facexlib>=0.2.5->realesrgan) (0.58.1)
Requirement already satisfied: typing-extensions in e:\lama-cleaner\installer\lib\site-packages (from torch>=1.7->realesrgan) (4.8.0)
Requirement already satisfied: colorama in e:\lama-cleaner\installer\lib\site-packages (from tqdm->realesrgan) (0.4.5)
Requirement already satisfied: matplotlib in e:\lama-cleaner\installer\lib\site-packages (from filterpy->facexlib>=0.2.5->realesrgan) (3.8.0)
Requirement already satisfied: llvmlite<0.42,>=0.41.0dev0 in e:\lama-cleaner\installer\lib\site-packages (from numba->facexlib>=0.2.5->realesrgan) (0.41.1)
Requirement already satisfied: certifi>=2017.4.17 in e:\lama-cleaner\installer\lib\site-packages (from requests->basicsr>=1.4.2->realesrgan) (2023.7.22)
Requirement already satisfied: charset-normalizer<3,>=2 in e:\lama-cleaner\installer\lib\site-packages (from requests->basicsr>=1.4.2->realesrgan) (2.0.4)
Requirement already satisfied: idna<4,>=2.5 in e:\lama-cleaner\installer\lib\site-packages (from requests->basicsr>=1.4.2->realesrgan) (3.4)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in e:\lama-cleaner\installer\lib\site-packages (from requests->basicsr>=1.4.2->realesrgan) (1.26.12)
Requirement already satisfied: tifffile>=2022.8.12 in e:\lama-cleaner\installer\lib\site-packages (from scikit-image->basicsr>=1.4.2->realesrgan) (2023.9.26)
Requirement already satisfied: lazy_loader>=0.3 in e:\lama-cleaner\installer\lib\site-packages (from scikit-image->basicsr>=1.4.2->realesrgan) (0.3)
Requirement already satisfied: packaging>=21 in e:\lama-cleaner\installer\lib\site-packages (from scikit-image->basicsr>=1.4.2->realesrgan) (23.2)
Requirement already satisfied: networkx>=2.8 in e:\lama-cleaner\installer\lib\site-packages (from scikit-image->basicsr>=1.4.2->realesrgan) (3.2.1)
Requirement already satisfied: imageio>=2.27 in e:\lama-cleaner\installer\lib\site-packages (from scikit-image->basicsr>=1.4.2->realesrgan) (2.31.6)
Requirement already satisfied: werkzeug>=1.0.1 in e:\lama-cleaner\installer\lib\site-packages (from tb-nightly->basicsr>=1.4.2->realesrgan) (2.2.2)
Requirement already satisfied: setuptools>=41.0.0 in e:\lama-cleaner\installer\lib\site-packages (from tb-nightly->basicsr>=1.4.2->realesrgan) (65.4.0)
Requirement already satisfied: markdown>=2.6.8 in e:\lama-cleaner\installer\lib\site-packages (from tb-nightly->basicsr>=1.4.2->realesrgan) (3.5.1)
Requirement already satisfied: tensorboard-data-server<0.8.0,>=0.7.0 in e:\lama-cleaner\installer\lib\site-packages (from tb-nightly->basicsr>=1.4.2->realesrgan) (0.7.2)
Requirement already satisfied: grpcio>=1.48.2 in e:\lama-cleaner\installer\lib\site-packages (from tb-nightly->basicsr>=1.4.2->realesrgan) (1.59.2)
Requirement already satisfied: six>1.9 in e:\lama-cleaner\installer\lib\site-packages (from tb-nightly->basicsr>=1.4.2->realesrgan) (1.16.0)
Requirement already satisfied: google-auth<3,>=1.6.3 in e:\lama-cleaner\installer\lib\site-packages (from tb-nightly->basicsr>=1.4.2->realesrgan) (2.23.4)
Requirement already satisfied: google-auth-oauthlib<2,>=0.5 in e:\lama-cleaner\installer\lib\site-packages (from tb-nightly->basicsr>=1.4.2->realesrgan) (1.1.0)
Requirement already satisfied: absl-py>=0.4 in e:\lama-cleaner\installer\lib\site-packages (from tb-nightly->basicsr>=1.4.2->realesrgan) (2.0.0)
Requirement already satisfied: protobuf>=3.19.6 in e:\lama-cleaner\installer\lib\site-packages (from tb-nightly->basicsr>=1.4.2->realesrgan) (4.24.4)
Requirement already satisfied: importlib-metadata>=6.6.0 in e:\lama-cleaner\installer\lib\site-packages (from yapf->basicsr>=1.4.2->realesrgan) (6.8.0)
Requirement already satisfied: tomli>=2.0.1 in e:\lama-cleaner\installer\lib\site-packages (from yapf->basicsr>=1.4.2->realesrgan) (2.0.1)
Requirement already satisfied: platformdirs>=3.5.1 in e:\lama-cleaner\installer\lib\site-packages (from yapf->basicsr>=1.4.2->realesrgan) (3.11.0)
Requirement already satisfied: pyasn1-modules>=0.2.1 in e:\lama-cleaner\installer\lib\site-packages (from google-auth<3,>=1.6.3->tb-nightly->basicsr>=1.4.2->realesrgan) (0.3.0)
Requirement already satisfied: cachetools<6.0,>=2.0.0 in e:\lama-cleaner\installer\lib\site-packages (from google-auth<3,>=1.6.3->tb-nightly->basicsr>=1.4.2->realesrgan) (5.3.2)
Requirement already satisfied: rsa<5,>=3.1.4 in e:\lama-cleaner\installer\lib\site-packages (from google-auth<3,>=1.6.3->tb-nightly->basicsr>=1.4.2->realesrgan) (4.9)
Requirement already satisfied: requests-oauthlib>=0.7.0 in e:\lama-cleaner\installer\lib\site-packages (from google-auth-oauthlib<2,>=0.5->tb-nightly->basicsr>=1.4.2->realesrgan) (1.3.1)
Requirement already satisfied: zipp>=0.5 in e:\lama-cleaner\installer\lib\site-packages (from importlib-metadata>=6.6.0->yapf->basicsr>=1.4.2->realesrgan) (3.17.0)
Requirement already satisfied: MarkupSafe>=2.1.1 in e:\lama-cleaner\installer\lib\site-packages (from werkzeug>=1.0.1->tb-nightly->basicsr>=1.4.2->realesrgan) (2.1.3)
Requirement already satisfied: fonttools>=4.22.0 in e:\lama-cleaner\installer\lib\site-packages (from matplotlib->filterpy->facexlib>=0.2.5->realesrgan) (4.43.1)
Requirement already satisfied: cycler>=0.10 in e:\lama-cleaner\installer\lib\site-packages (from matplotlib->filterpy->facexlib>=0.2.5->realesrgan) (0.12.1)
Requirement already satisfied: python-dateutil>=2.7 in e:\lama-cleaner\installer\lib\site-packages (from matplotlib->filterpy->facexlib>=0.2.5->realesrgan) (2.8.2)
Requirement already satisfied: pyparsing>=2.3.1 in e:\lama-cleaner\installer\lib\site-packages (from matplotlib->filterpy->facexlib>=0.2.5->realesrgan) (3.1.1)
Requirement already satisfied: kiwisolver>=1.0.1 in e:\lama-cleaner\installer\lib\site-packages (from matplotlib->filterpy->facexlib>=0.2.5->realesrgan) (1.4.5)
Requirement already satisfied: contourpy>=1.0.1 in e:\lama-cleaner\installer\lib\site-packages (from matplotlib->filterpy->facexlib>=0.2.5->realesrgan) (1.1.1)
Requirement already satisfied: pyasn1<0.6.0,>=0.4.6 in e:\lama-cleaner\installer\lib\site-packages (from pyasn1-modules>=0.2.1->google-auth<3,>=1.6.3->tb-nightly->basicsr>=1.4.2->realesrgan) (0.5.0)
Requirement already satisfied: oauthlib>=3.0.0 in e:\lama-cleaner\installer\lib\site-packages (from requests-oauthlib>=0.7.0->google-auth-oauthlib<2,>=0.5->tb-nightly->basicsr>=1.4.2->realesrgan) (3.2.2)
Requirement already satisfied: gfpgan in e:\lama-cleaner\installer\lib\site-packages (1.3.8)
Requirement already satisfied: lmdb in e:\lama-cleaner\installer\lib\site-packages (from gfpgan) (1.4.1)
Requirement already satisfied: scipy in e:\lama-cleaner\installer\lib\site-packages (from gfpgan) (1.11.3)
Requirement already satisfied: tb-nightly in e:\lama-cleaner\installer\lib\site-packages (from gfpgan) (2.16.0a20231031)
Requirement already satisfied: tqdm in e:\lama-cleaner\installer\lib\site-packages (from gfpgan) (4.64.1)
Requirement already satisfied: yapf in e:\lama-cleaner\installer\lib\site-packages (from gfpgan) (0.40.2)
Requirement already satisfied: torchvision in e:\lama-cleaner\installer\lib\site-packages (from gfpgan) (0.14.1+cu117)
Requirement already satisfied: opencv-python in e:\lama-cleaner\installer\lib\site-packages (from gfpgan) (<IP_ADDRESS>)
Requirement already satisfied: facexlib>=0.2.5 in e:\lama-cleaner\installer\lib\site-packages (from gfpgan) (0.3.0)
Requirement already satisfied: basicsr>=1.4.2 in e:\lama-cleaner\installer\lib\site-packages (from gfpgan) (1.4.2)
Requirement already satisfied: pyyaml in e:\lama-cleaner\installer\lib\site-packages (from gfpgan) (6.0.1)
Requirement already satisfied: torch>=1.7 in e:\lama-cleaner\installer\lib\site-packages (from gfpgan) (1.13.1+cu117)
Requirement already satisfied: numpy in e:\lama-cleaner\installer\lib\site-packages (from gfpgan) (1.26.1)
Requirement already satisfied: Pillow in e:\lama-cleaner\installer\lib\site-packages (from basicsr>=1.4.2->gfpgan) (10.0.1)
Requirement already satisfied: requests in e:\lama-cleaner\installer\lib\site-packages (from basicsr>=1.4.2->gfpgan) (2.28.1)
Requirement already satisfied: addict in e:\lama-cleaner\installer\lib\site-packages (from basicsr>=1.4.2->gfpgan) (2.4.0)
Requirement already satisfied: future in e:\lama-cleaner\installer\lib\site-packages (from basicsr>=1.4.2->gfpgan) (0.18.2)
Requirement already satisfied: scikit-image in e:\lama-cleaner\installer\lib\site-packages (from basicsr>=1.4.2->gfpgan) (0.22.0)
Requirement already satisfied: numba in e:\lama-cleaner\installer\lib\site-packages (from facexlib>=0.2.5->gfpgan) (0.58.1)
Requirement already satisfied: filterpy in e:\lama-cleaner\installer\lib\site-packages (from facexlib>=0.2.5->gfpgan) (1.4.5)
Requirement already satisfied: typing-extensions in e:\lama-cleaner\installer\lib\site-packages (from torch>=1.7->gfpgan) (4.8.0)
Requirement already satisfied: markdown>=2.6.8 in e:\lama-cleaner\installer\lib\site-packages (from tb-nightly->gfpgan) (3.5.1)
Requirement already satisfied: werkzeug>=1.0.1 in e:\lama-cleaner\installer\lib\site-packages (from tb-nightly->gfpgan) (2.2.2)
Requirement already satisfied: absl-py>=0.4 in e:\lama-cleaner\installer\lib\site-packages (from tb-nightly->gfpgan) (2.0.0)
Requirement already satisfied: setuptools>=41.0.0 in e:\lama-cleaner\installer\lib\site-packages (from tb-nightly->gfpgan) (65.4.0)
Requirement already satisfied: tensorboard-data-server<0.8.0,>=0.7.0 in e:\lama-cleaner\installer\lib\site-packages (from tb-nightly->gfpgan) (0.7.2)
Requirement already satisfied: grpcio>=1.48.2 in e:\lama-cleaner\installer\lib\site-packages (from tb-nightly->gfpgan) (1.59.2)
Requirement already satisfied: google-auth<3,>=1.6.3 in e:\lama-cleaner\installer\lib\site-packages (from tb-nightly->gfpgan) (2.23.4)
Requirement already satisfied: six>1.9 in e:\lama-cleaner\installer\lib\site-packages (from tb-nightly->gfpgan) (1.16.0)
Requirement already satisfied: protobuf>=3.19.6 in e:\lama-cleaner\installer\lib\site-packages (from tb-nightly->gfpgan) (4.24.4)
Requirement already satisfied: google-auth-oauthlib<2,>=0.5 in e:\lama-cleaner\installer\lib\site-packages (from tb-nightly->gfpgan) (1.1.0)
Requirement already satisfied: colorama in e:\lama-cleaner\installer\lib\site-packages (from tqdm->gfpgan) (0.4.5)
Requirement already satisfied: tomli>=2.0.1 in e:\lama-cleaner\installer\lib\site-packages (from yapf->gfpgan) (2.0.1)
Requirement already satisfied: importlib-metadata>=6.6.0 in e:\lama-cleaner\installer\lib\site-packages (from yapf->gfpgan) (6.8.0)
Requirement already satisfied: platformdirs>=3.5.1 in e:\lama-cleaner\installer\lib\site-packages (from yapf->gfpgan) (3.11.0)
Requirement already satisfied: pyasn1-modules>=0.2.1 in e:\lama-cleaner\installer\lib\site-packages (from google-auth<3,>=1.6.3->tb-nightly->gfpgan) (0.3.0)
Requirement already satisfied: rsa<5,>=3.1.4 in e:\lama-cleaner\installer\lib\site-packages (from google-auth<3,>=1.6.3->tb-nightly->gfpgan) (4.9)
Requirement already satisfied: cachetools<6.0,>=2.0.0 in e:\lama-cleaner\installer\lib\site-packages (from google-auth<3,>=1.6.3->tb-nightly->gfpgan) (5.3.2)
Requirement already satisfied: requests-oauthlib>=0.7.0 in e:\lama-cleaner\installer\lib\site-packages (from google-auth-oauthlib<2,>=0.5->tb-nightly->gfpgan) (1.3.1)
Requirement already satisfied: zipp>=0.5 in e:\lama-cleaner\installer\lib\site-packages (from importlib-metadata>=6.6.0->yapf->gfpgan) (3.17.0)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in e:\lama-cleaner\installer\lib\site-packages (from requests->basicsr>=1.4.2->gfpgan) (1.26.12)
Requirement already satisfied: charset-normalizer<3,>=2 in e:\lama-cleaner\installer\lib\site-packages (from requests->basicsr>=1.4.2->gfpgan) (2.0.4)
Requirement already satisfied: idna<4,>=2.5 in e:\lama-cleaner\installer\lib\site-packages (from requests->basicsr>=1.4.2->gfpgan) (3.4)
Requirement already satisfied: certifi>=2017.4.17 in e:\lama-cleaner\installer\lib\site-packages (from requests->basicsr>=1.4.2->gfpgan) (2023.7.22)
Requirement already satisfied: MarkupSafe>=2.1.1 in e:\lama-cleaner\installer\lib\site-packages (from werkzeug>=1.0.1->tb-nightly->gfpgan) (2.1.3)
Requirement already satisfied: matplotlib in e:\lama-cleaner\installer\lib\site-packages (from filterpy->facexlib>=0.2.5->gfpgan) (3.8.0)
Requirement already satisfied: llvmlite<0.42,>=0.41.0dev0 in e:\lama-cleaner\installer\lib\site-packages (from numba->facexlib>=0.2.5->gfpgan) (0.41.1)
Requirement already satisfied: networkx>=2.8 in e:\lama-cleaner\installer\lib\site-packages (from scikit-image->basicsr>=1.4.2->gfpgan) (3.2.1)
Requirement already satisfied: tifffile>=2022.8.12 in e:\lama-cleaner\installer\lib\site-packages (from scikit-image->basicsr>=1.4.2->gfpgan) (2023.9.26)
Requirement already satisfied: packaging>=21 in e:\lama-cleaner\installer\lib\site-packages (from scikit-image->basicsr>=1.4.2->gfpgan) (23.2)
Requirement already satisfied: lazy_loader>=0.3 in e:\lama-cleaner\installer\lib\site-packages (from scikit-image->basicsr>=1.4.2->gfpgan) (0.3)
Requirement already satisfied: imageio>=2.27 in e:\lama-cleaner\installer\lib\site-packages (from scikit-image->basicsr>=1.4.2->gfpgan) (2.31.6)
Requirement already satisfied: pyasn1<0.6.0,>=0.4.6 in e:\lama-cleaner\installer\lib\site-packages (from pyasn1-modules>=0.2.1->google-auth<3,>=1.6.3->tb-nightly->gfpgan) (0.5.0)
Requirement already satisfied: oauthlib>=3.0.0 in e:\lama-cleaner\installer\lib\site-packages (from requests-oauthlib>=0.7.0->google-auth-oauthlib<2,>=0.5->tb-nightly->gfpgan) (3.2.2)
Requirement already satisfied: python-dateutil>=2.7 in e:\lama-cleaner\installer\lib\site-packages (from matplotlib->filterpy->facexlib>=0.2.5->gfpgan) (2.8.2)
Requirement already satisfied: cycler>=0.10 in e:\lama-cleaner\installer\lib\site-packages (from matplotlib->filterpy->facexlib>=0.2.5->gfpgan) (0.12.1)
Requirement already satisfied: fonttools>=4.22.0 in e:\lama-cleaner\installer\lib\site-packages (from matplotlib->filterpy->facexlib>=0.2.5->gfpgan) (4.43.1)
Requirement already satisfied: pyparsing>=2.3.1 in e:\lama-cleaner\installer\lib\site-packages (from matplotlib->filterpy->facexlib>=0.2.5->gfpgan) (3.1.1)
Requirement already satisfied: kiwisolver>=1.0.1 in e:\lama-cleaner\installer\lib\site-packages (from matplotlib->filterpy->facexlib>=0.2.5->gfpgan) (1.4.5)
Requirement already satisfied: contourpy>=1.0.1 in e:\lama-cleaner\installer\lib\site-packages (from matplotlib->filterpy->facexlib>=0.2.5->gfpgan) (1.1.1)

Platform: Windows-10-10.0.22621-SP0
Python version: 3.10.6
torch: 1.13.1+cu117
torchvision: 0.14.1+cu117
Pillow: 10.0.1
diffusers: 0.16.1
transformers: 4.27.4
opencv-python: <IP_ADDRESS>
xformers: 0.0.16
accelerate: N/A
lama-cleaner: 1.2.4
rembg: 2.0.52
realesrgan: 0.3.0
gfpgan: 1.3.8

2023-11-01 01:19:53.770 | INFO     | lama_cleaner.parse_args:parse_args:185 - Launching installer web config page
Traceback (most recent call last):
File "E:\lama-cleaner\installer\lib\runpy.py", line 196, in _run_module_as_main
return run_code(code, main_globals, None,
File "E:\lama-cleaner\installer\lib\runpy.py", line 86, in run_code
exec(code, run_globals)
File "E:\lama-cleaner\installer\Scripts\lama-cleaner.exe_main.py", line 7, in
sys.exit(entry_point())
File "E:\lama-cleaner\installer\lib\site-packages\lama_cleaner_init.py", line 13, in entry_point
args = parse_args()
File "E:\lama-cleaner\installer\lib\site-packages\lama_cleaner\parse_args.py", line 186, in parse_args
main(args.installer_config)
File "E:\lama-cleaner\installer\lib\site-packages\lama_cleaner\web_config.py", line 186, in main
sd_controlnet_method = gr.Radio(
File "E:\lama-cleaner\installer\lib\site-packages\gradio\component_meta.py", line 146, in wrapper
return fn(self, **kwargs)
TypeError: Radio.init() got an unexpected keyword argument 'lable'
Press any key to continue . . .

Thank you for reporting this, fixed in 1.2.5. Rerun win_config.bat can update to the latest version.

Thanks this worked, closing the issue


Add USI Life Support from Kerbal Stuff

This pull request was automatically generated by Kerbal Stuff on behalf of Roverdude, to add USI Life Support to CKAN.
Please direct questions about this pull request to Roverdude.

Asked RoverDude if he's going to be moving everything to KS and if he'll be keeping it up to date.

No reply. Also no further mods from USI added to KS. We also already index USI-LS. Close for now re-open if RoverDude moves everything to KS?

Yeah, I see no pressing need to cutover to using KS as the indexing source. Closing as already implemented.


Generate all enums in a single separated file

Hello there,
I'm wondering if it could be possible to generate all enums in one single file that is imported by other artemis generated files. Today, if I have 2 schema mappings that may use the same enum, artemis will duplicate the enum declaration. So for example:
Given a enum is used in 2 schema mappings, artemis generates two files with the same enum declaration:
// file 1
enum Gender {
  Female,
  Male,
  ARTEMIS_UNKNOWN,
}

// file 2
enum Gender {
  Female,
  Male,
  ARTEMIS_UNKNOWN,
}

They both are really equal, but for dart they're not. So I can't simple write a file that has some utility functions like this:
  // enum from 1 and enum from 2 are 'kinda' equal, but they are not the same.
  // so this method would need to be duplicated in order to deal with them both.
  String describeGender(Gender gender) {
    switch (gender) {
      case Gender.Male:
        return 'Masculino';
      case Gender.Female:
        return 'Feminino';
      default:
        return 'Desconhecido';
    }
  }

I'm not sure if it's really possible to have a gql operation that 'selects' only some entries of enums (would this make any sense??), so generating all of them in a single file and importing them in generated files would help to dedupe enums, and they could be reused without namespaces conflicts and duplications for functions that may wrap some rules around them.
btw: maybe this idea could be applied to scalars too (?)

Hi. Theoretically this is possible.
Currently we are focused on the existing bugs.
If you map all the output in one file this will help to avoid the issue.

@vasilich6107 thx for the response!
Yeah, I understand that it could be solved like that, but with a single file output I have to use other naming_scheme.. and I get some very long field names.
Unfortunately, Dart does't support type alias yet 😢 so... is either reusable code or ugly as hell long names (for example one here is AccidentsList$Query$Accidents$Items$Person and it's used in a lot of places)... Is there any way to rename those types in gql files? 🤔
I'm gonna stick with the pathedWithFields since it solves this problem for now...

The naming on the graphql is not very easy task to solve.
The latest and most stable solution is pathedWithFields that allows to avoid the naming conflicts.
As you mentioned - fragments definitely solve the issue.

pathWithFields does generate duplicate enums, too, doesn't it. It did not work for me at least.

@saibotma prefer to put output in one file per schema

I happen to resolve this issue by the following
/// hide/show imports
'import something.graphql.dart' show MyQueryOnly;
import 'somewhere.graphql.dart' hide Gender;

/// import aliases
import 'my_query.graphql.dart' as Query;

its not the solution, but an alternative to resolve duplicate enum import/export.

@ram231 it is very unreliable solution
Next day you’ll get enum from one file and you’ll have to compare with enum from other - this will be the end ;-)


when enable volar, exit vscode very slowly

in vue2 project, mac os(m1 pro 10 core),  when enable volar, exit(cmd+q) vscode very very slowly

Can you reproduce this problem in https://github.com/johnsoncodehk/volar-starter?
If it can't, could you provide repro case or screen recording to show the problem?


Rewire throws a Type Error when overriding a const while running Jest tests

🐛 Bug Report
Rewire throws a Type Error when overriding a const variable while running Jest tests.
To Reproduce

Create a javascript file to test with a top-level variable set as a const and a simple test function
Create a Jest test file, use rewire to import the above module, use rewire.set to change the const value

See my repo below for a working example.
Expected behavior
I expect the Jest test to execute succesfully in the same way the Mocha tests currently do.
Link to Repo
Github Repo with bug: https://github.com/Shakakai/jest-rewire-const-error
Run npm test

~~/v8.10.0/bin/node ~~/v8.10.0/lib/node_modules/npm/bin/npm-cli.js test --scripts-prepend-node-path=auto

><EMAIL_ADDRESS>test ~~/jest-rewire-const-error
> mocha ./test/example.mocha.js && jest example

  Show mocha works
    ✓ should add the numbers together

  1 passing (5ms)

 FAIL  test/example.jest.test.js
  ● Test suite failed to run

    TypeError: Assignment to constant variable.

      at eval (eval at __set__ (example.js:72:5), <anonymous>:1:3)
      at Function.__set__ (example.js:72:5)
      at Object.<anonymous> (test/example.jest.test.js:6:15)

Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        0.905s
Ran all test suites matching /example/i.
npm ERR! Test failed.  See above for more details.

Process finished with exit code 1

Also having this problem. Any news here?

Hey all - I'm not familiar with rewire but it seems like they support mocha and not jest?
If someone from the rewire team wants to diagnose and let us know what, if anything, is broken or missing in Jest then I'm happy to take a look!


Exposing browserify requires

Hello @caleb,
your plugin has been very useful and we have needed the require - expose API of browserify.
This small PR implements the following:

exposes the browserify.require functionality
makes entryPoints optional if the require option is specified
adopts the option-passing API of the well-used grunt-browserify plugin
maintains backward-compatibility with the previous { tr: ..., options: ...} transform API
updates documentation accordingly

Thank you!
Jacques

Cool!


Add files via upload

Adding UNAL as an authorized education center. Domain: unal.edu.co

@andresram1 I am sorry, the domain unal.edu.co is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).


Handle error events

Currently errors during syncing are printed out in the operator logs, but ideally those should be streamed back as kubernetes events of the corresponding resource. Besides, there are many TODO in the code relative exactly to this. So we should pass errors by to the event reporter
Follow up of #14

ok, so if I understood this correctly this is generating error events for the resource pod that is running the operator, i.e. print the errors by doing kubectl describe -n cattle-rancheros-operator-system pod/rancheros-operator-6fd66bd6b4-2k8vv and check the events....
Is that even possible lol?

I'm not sure in wrangler context, but with standard k8s api that would involve using "k8s.io/client-go/tools/record" to stream back events recording from the controller.  The event recorder can be retrieved in the manager GetEventRecorderFor sigs.k8s.io/controller-runtime/pkg/manager
We could also think at status reporting for now, so we can propagate at least the error back into the object status, but reporting to events is something that in general we should have in place as a mechanism.

yeah, that I could find about the "standard way" of getting the recorder and the manager but Im pretty lost on where to init that crap in our context with all the autogenerated stuff. AFAI can see, we got no manager around in the wrangler context? anyway, gonna look harder

I'm trying to have a look at how make recorder generally available while working on #23 , but I won't cover propagating back errors from all the involved parts, just covering the new component

it is contained here: https://github.com/rancher-sandbox/rancheros-operator/pull/26 although, I've still not added tests for it yet

closed by #27


Allow course staff to add people to the queue

Candy (in CS Advising) e-mailed me about a problem they had yesterday where 3 people were unable to log into the queue (probably due to the shib auth error).  Even as an admin, she could only add one of them to the queue herself.
A worthwhile feature would be to allow admins ("course staff") to add a question to the queue "as someone else" (eg: an ask a question with a NetID field?).

This seems like a horrible, horrible hack for something that shouldn't ever be needed. The right thing to do is get to the bottom of the Shib issue, not work around it being broken.

I agree that in the current CS 225 usage, it doesn't make sense.  I disagree that it is a horrible hack.
There are models where this method is use right now.  For example, the intro CHEM courses have a similar queuing system that they use in the Chemistry Learning Center (https://chemistry.illinois.edu/clc).  They have students swipe in to register for their queue and then are placed on a queue or assigned someone to help them out.  The student is added to the queue, but cannot add themselves.
At some point in the past (not sure how it is this semester), this was also how CS 125's queue also worked.  They wanted to verify the person was physically there before they were enqeueud.  This may be a model we don't care to support, but is a widely used model.

Gotcha, that was the context I needed. The way you framed it in the original issue made me think you wanted this solely to work around the fact that Shib is misbehaving :)

So yes, this is definitely a model we should support.

And it's Holly, so we definitely want to make sure she's happy. :)


"Bilkul bakwas hai yeh, Aap band kar do isey" for unexpected end of if/while statements

Inspiration 👇🏻

This error message is not able to convey the proper message.


Update to terraform provider 3

Code Review
Please consider the following checklist when reviewing this Pull Request.
More background and details here.

[ ] Does the code actually solve the problem it was meant to solve?
[ ] Is the code covered by unit tests? Integration tests?
[ ] Does anything here need documentation? (Focus on why, not what.)
[ ] Does any of this code deal with privacy sensitive information or affects security? Ask an additional reviewer.
[ ] Is the code easy to understand and change in the future?
[ ] Is the same code or concept duplicated? Find a balance between DRYness and readability.
[ ] Does the code reasonably adhere to the Kabisa coding standards?
[ ] Be kind.

Nope we don't want a pull request to main.


new default kafka-source-dispatcher memory limit leads to it being OOMKilled

Describe the bug
Upgrading to 1.6 using the new kafka-source-dispatcher "statefulset" implementation, a kafka-source-dispatcher is being OOMKilled, due to its 1000Mi memory limit
kafka-source-dispatcher-0                             1/2     CrashLoopBackOff   488 (2m34s ago)   2d8h
kafka-source-dispatcher-1                             2/2     Running            2 (26h ago)       2d8h
kafka-source-dispatcher-2                             2/2     Running            1 (19h ago)       2d8h

with previous version, the same load used to work fine, with the dispatchers taking about ~5Gi of Memory, so the current new limit of 1000Mi seems to be quite limiting.
Expected behavior
There should probably not be a default memory limit. A limit could be defined, if the project declares an explicit expected load in which the expected limit is supposed to be enough for that use case.
To Reproduce
n/t
Knative release version
1.6
Additional context
Using CI builds of Serverless Operator https://github.com/openshift-knative/serverless-operator/tree/release-1.27

/remove-lifecycle stale


Add a "back button" that returns to the last edited file

A back button that would return you to the last file you were editing.  It would also update the left file pane to show the file in the pane (if the file/folder list is long and cannot fit entirely into the pane).  This would be helpful if you are editing a particular file and you just need to look at another file in the project to possibly copy some code or whatever, and then go back to editing the previous file.

Does Ctrl-Tab do what you need?

Ctrl-Tab should be exactly what you need for a "back button". Works quickly to switch between recently edited files.

@fritzwf You can also use SplitView feature of Brackets and open two files at once vertically/horizontally. Enable this feature through menu View > Vertical Split or View > Horizontal Split

If I hit Ctrl-J to jump to a function definition, Ctrl-Tab will not switch back to that same function call.  Can this be achieved?

In which release was this issue fixed?


Language switcher with shortened names

Hi there,
I was wodnering if it's possible to change displayed names from "English (United States)" to something like "EN" in language switcher?
Thanks,
D.

Not without a bit of work...
I think what we need is an extension in FluentExtension::LocaleInformation() so you can inject custom properties such as this.
Something like this?
https://github.com/tractorcow/silverstripe-fluent/blob/master/code/extensions/FluentExtension.php#L423
public function LocaleInformation($locale = null)
{
	// ...
	$data = $this->owner->extend('updateLocaleInformation', $data, $locale);
	return new ArrayData($data);
}

Hi tractorcow,
thank you for your answer. I think I've found a simpler approach tho, correct me if I'm wrong.
I've used $Language variable in my menu template so it looks like this:
`

  $Language.XML

`
... then just styled "a href" with "language-label" class.
What do you think?
Cheers,
D.

oh, that's it, good job!


fs: http: do not timeout on sock_read

We have been getting reports that the timeout on sock_read was raising
timeout error even for chunked uploads, and sometimes even uploading
zero-byte files.
See: https://github.com/iterative/dvc/issues/8065
and https://github.com/iterative/dvc/issues/8100.
These kinds of logic don't belong here and should be upstreamed (eg: RetryClient/ClientTimeout, etc).
We added timeout in https://github.com/iterative/dvc/pull/7460 because of freezes in
https://github.com/iterative/dvc/issues/7414.
I think we can rollback this for now given that there are lots of report of failures/issues with this line,
and if we get any new reports of hangs, we'll investigate it separately.

Thanks for the fix @skshetry , but should we prioritize a proper fix for this? (we had reports of processes hanging, right?) + from my experience before- it's super annoying on the server side when it hangs and there is no way to control it.

Note: this was reverted in https://github.com/iterative/dvc-http/pull/6


Confirm Licencing

This is a great library.  Sorry to be a pain, but can you confirm the licence for use.  Thank you

Haven't added a license yet, I'll be adding an MIT license for this

Also thanks for appreciating my package!

The license is now attached


Add nthKey support

This is a very rough draft pull request. I have no experience with and no tooling for Java application at the moment, so this won't even compile.
The nthKey iOs app can be used a signer in a multisig setup. So far I've only tested it with Specter, so - if you're interested in adding this - we may have to iron out some compatibility issues.
The public key announce format it uses is similar to ColdCard, but using xpub instead of zpub, e.g.:
{"ExtPubKey":"xpub6E...","AccountKeyPath":"48h\/0h\/0h\/2h","MasterFingerprint":"00000000"}

(see also BlueWallet issue https://github.com/BlueWallet/BlueWallet/issues/3653)
The wallet export is the same as Specter:
{ "label": "Wallet McWalletface", "blockheight": 660156, "descriptor": "wsh(sortedmulti(2,[....,...\/0\/*))#00000000" }

Basic characteristics of the app:

keys can be imported using JSON or QR
wallet metadata can be exported using JSON or QR (it can scan the Specter backup PDF)
testnet, signet are free, mainnet is paid (unless you compile yourself from source)
only sh-wpkh (native Segwit) is supported
only multisig is supported (using ~BIP48)

Thumbnails generated with:
convert nthkey-orig.png -channel RGB -negate -resize 300x300 -background white -gravity center -extent 200x200 -type grayscale<EMAIL_ADDRESS>convert nthkey-orig.png -channel RGB -negate -resize 150x150 -background white -gravity center -extent 100x100 -type grayscale<EMAIL_ADDRESS>convert nthkey-orig.png -channel RGB -negate -resize 75x75 -background white -gravity center -extent 50x50 -type grayscale nthkey.png

Apologies for the slow reply on this. I'd like Sparrow to support nthKey and this PR seems like a good start. I will try to find time to review more fully in the coming weeks.


MicroProfile metrics project has CDI beans in it but is not a bean archive

This may or may not be a problem depending on original intent.
The https://github.com/oracle/helidon/tree/master/microprofile/metrics subproject has several classes in it that are annotated with CDI annotations.  Here is one arbitrary example:
https://github.com/oracle/helidon/blob/ca1ffd3b04c38b08993e1b34bdbfbfdfc3a9f633/microprofile/metrics/src/main/java/io/helidon/microprofile/metrics/RegistryProducer.java#L31-L32
The jar file produced by this project does not have a META-INF/beans.xml resource in it, so this jar file will not be recognized as a bean archive (see also section 15.1 of the CDI specification).  That is, it is an implicit bean archive, but in the absence of the javax.enterprise.inject.scan.implicit System property it will not be picked up.  This may or may not be by design and is, itself, not intrinsically a problem, but it is an easy thing to miss, so original intent is important here.
The MetricsCdiExtension programmatically registers the beans found in this jar file:
https://github.com/oracle/helidon/blob/ca1ffd3b04c38b08993e1b34bdbfbfdfc3a9f633/microprofile/metrics/src/main/java/io/helidon/microprofile/metrics/MetricsCdiExtension.java#L164-L169
However, if the contents of this jar file are combined in a fat jar or some other mechanism such that they are in a classpath root that contains a META-INF/beans.xml with an effective bean discovery mode of annotated (or some other mode that results in their discovery), they will be registered twice, and ambiguous dependency errors will result.
We need to either:

mark this subproject as a bean archive (my naïve preference) and eliminate the programmatic adding of the annotated types by MetricsCdiExtension, or
remove the bean-defining annotations that cause these metrics-related bean classes to be automatically discovered and then, during programmatic registration, create programmatic beans for them in the proper scopes, but reading all other metadata from the classes in question

I am for removing the bean defining annotations. I prefer the manual registration in an extension, as it removes jar scanning requirement for this jar file.

Duly noted.  For the record there's no scanning going on because we use Jandex.  In fact, we might be able to lose a reflective method call if we keep the annotations.


Register format decimal128

Format for 128-bit decimal floating-point numbers as proposed in proposal in https://github.com/OAI/OpenAPI-Specification/pull/3190#issuecomment-1466611719.

@baywet @handrews please review

(also the file name has two 1 I guess it's a typo)

Strange: I can only request a re-request a review from a single reviewer, trying to re-request for a second reviewer removes the re-request for the first reviewer 🤔


HighState isn't sent in every network configuration

I have spotted a problem with the return of the HighState, when connected via WiFi.
Current behavior
Currently a difference is made if you are connected via LAN or WiFi.
If you connect via LAN, you direct the UDP messages to <IP_ADDRESS> and if you are connected via WiFi, you direct the UDP messages to <IP_ADDRESS>.
Therefore switching between LAN and WiFi forces you to change the IP in your code and recompile it (which is obviously not what you want, if you switch it regularly).
It is further possible to set the Raspberry Pi into network pass through mode to send IP messages from the <IP_ADDRESS>/24 network to the <IP_ADDRESS>/24 network. For this, a route to the internal network of the robot has to be configured, in your connecting PC,  via the Raspberry Pi (either as default gateway or static route).
If this is set up, you are able to connect to all devices in the .123.0 network, which also includes the Pi's interface with address <IP_ADDRESS>.
You are now able to control the Go1 robot via WiFi by directing the UDP messages to <IP_ADDRESS>, which is great.
The Problem
When doing so, you don't get HighState messages via UDP.
Expected behavior
Since the network connection works in both ways, the HighState should be returned via UDP.

Try <IP_ADDRESS>

@HBSIM0 that's what I currently do.
But having to change it manually every time you switch between wired and wireless is quite error-prone.
I would rather always set the IP to the 161 address and configure the forwarding once and for all.

Sorry, our SDK does not support cross-network segment communication


Making this work with TableViewCells

Hello,
I am a beginner, this controller seems great! However, I am having a hard time implementing it with table viewCell. If you could please tell me how this could be done. I would really appreciate it!
Using : Swift 2.0
Thanks!

i have same requirement, did you already solved this ?


Update webcamXP.py

Fixed missing dependency and a typo in line 5 when getting the SHODAN_API_KEY environment variable.

Thanks a lot but I've already fixed this bug when I see this pull request.


Restoring wallet

The Backup phrase at the bottom (suggested phrase is not visible)Android large device.

Completed


allow ABAC authorization mode

Even though the API endpoint can be TLS secured, service accounts currently have full access to the entire cluster and all its API endpoints. Meaning, if a single pod/container is compromised, everything is.
We're currently doing this manually (by having our own artefacts based on the ones in this repository), but it would be nice if it was possible to define the authorization plugin to use.

Hi @JeanMertz,
You should be able to modify the flags passed to the apiserver in the aws/vagrant/generic installs. It will require editing the api-server manifest, but there is nothing that would disallow using ABAC authrorization mode.
For example, you could add the --authorization-mode=ABAC and --authorization-policy-file=SOME_FILENAME to the api-server manifest for kube-aws: https://github.com/coreos/coreos-kubernetes/blob/master/multi-node/aws/artifacts/manifests/controller/kube-apiserver.yaml#L14-L25
Then follow the instructions for deployment using custom manifests: https://github.com/coreos/coreos-kubernetes/tree/master/multi-node/aws#custom-kubernetes-manifests
Also note, the policy file you specify would need to be deployed to your master nodes (where apiserver is running).

Closing this issue, but please re-open if you're still having trouble.


[Feature Request] Option to have base64 encoded images in-lined as references

Thanks for adding the in lined image download option, really helps with note portability!
If there could be an option to have the images embedded as references, with the full base64 at the end of the clipped text that could help make the clipped notes "cleaner" when viewing the raw markdown. This doesn't make a difference when viewing the rendered markdown, just when going in and viewing/editing the raw text.
Current embedding style:
<note text>
[![Image Alt Text](data:image/png;base64,iVBORw...)]
<note text>

Propose option for something like:
<note text>
![Image1 Alt Text][<hash of image1 or other unique identifier>]
<note text>
![Image2 Alt Text][<hash of image2 or other unique identifier>]
...
<end of note text>

[<hash of image1 or other unique identifier>]:data:image/png;base64,iVBORw...

[<hash of image2 or other unique identifier>]:data:image/png;base64,iVBORw...

I looked at the turndown source for referenced links and implemented that for images (as an option). So whether you've got base64 images or not, as long as the link style isn't just stripped or obsidian related, you choose to output images as referenced.
The reference id is 'fig' + i (where i is an auto-incrementing number), so you end up with something like
<note text>
![Image1 Alt Text][fig1]
<note text>
![Image2 Alt Text][fig2]
...
<end of note text>

[fig1]: data:image/png;base64,iVBORw...

[fig2]: data:image/png;base64,iVBORw...

I've tested the output in VSCode (works fine), and Obsidian (had issues). Notably, Live Preview in Obsidian will not render these images, but it does work in reading view. Also, if there are a lot of base64 images (I was testing with Wait But Why it seems to lock up Obsidian trying to parse/render the reading view.


Modernize core BSK architecture CPP files

Review: By commit
Merge strategy: Merge (no squash)

Description
This code was lifted from the LASP BSK fork and modified to work with Basilisk.
Verification
Did builds and tests of each state.  All unit tests completed successfully.
Documentation
None
Future work
None

Happy to review, though I’m not super up to date on Cpp best practices


add plotting feature in the pipeline

As discussed I want to add the plotting feature in the pipeline so that whenever we need we can visualize the data.

i suggest you include an argument to the mutable structure function that indicates which columns to plot for either 1D, 2D, and 3D plots. also for classification problem, plotting the bargraph or pie-chart of the distribution of different classes will be helpful.


Add flag to append new file extension

Having an option to append .avif is useful so nginx try_files usage stays simple.
Without the flag foo.jpg => foo.avif
With the flag --append-ext foo.jpg => foo.jpg.avif
This implements the footnote on #8

v0.2.0 now available with this option, thank you.