Add tls client certificate parameters to example

Add parameters for TLS client authentication.
Notice, this may lead to the following error: mqtt_async_client::client::client] IoTask: Error connecting: invalid certificate: BadDER.
Not sure if this is related to my cert setup yet or a general rustls issue, similar issue is described here,   dirty workaround here.

Your code seems correct, so I've merged it.
rustls errors can be a little hard to track down. Can you add some example client certificates that seem to cause a problem? That would help us reproduce the issue.

So issues I ran into were basically when following this guide that openssl generates x.509 version 1 certificates which are not supported by rustls. Next I ran into issues with self signed certificates. I just created this client / server example.

I haven't had time to look at your example yet, but one way I have had success is by using the scripts included in the rustls tree.


SignalR tutorial shows different code than is in code sample and in link.

If you go to this link, and look at the code presented for chat.js, it shows that you should use this line of code:
https://docs.microsoft.com/en-us/aspnet/core/signalr/get-started?view=aspnetcore-2.1&tabs=visual-studio
This code doesn't work.
const connection = new signalR.HubConnection(
    "/chathub",
    { logger: signalR.LogLevel.Information });

If you edit this tutorial example (or use the following link), in place of the code, you will find a [!code-javascriptIndex].  If you follow that link, it takes you to the chat.js file and a different line of code is showing.
Link to the tutorial get-started.md
https://github.com/aspnet/Docs/blob/master/aspnetcore/signalr/get-started.md
Link to the chat.js the tutorial has in it:
https://github.com/aspnet/Docs/blob/master/aspnetcore/signalr/get-started/sample/wwwroot/js/chat.js
This code works.
const connection = new signalR.HubConnectionBuilder()
    .withUrl("/chatHub")
    .build();

Duplicate to #6563.


Update Harvey.podspec bumping to 0.1.0

👻 0.1.0 minor version released
https://github.com/Moya/Harvey/releases

Update Harvey.podspec bumping to 0.1.0 for supporting Cocoapods

Hey @cruisediary, this project is no longer being maintained and is not ready for use. See this comment

@SD10 I close this PR 👻


Ability to change the buffer size of the player

Describe the idea you'd like for Amethyst to have
I'm not sure if this is implementable with the web apis, but it's nice to have.

closing as this feature has been deprecated from webaudio api
https://developer.mozilla.org/en-US/docs/Web/API/ScriptProcessorNode/bufferSize


Fixes and Updates for UNETR

I checked up for UNETR, and tried to fix the overalls (one final thing is still missing - the switch between ViT models)
To address some previous questions -

We do the preprocessing for the inputs to make sure that the dimensions are as SAM's ViT appreciates (1024 * 1024)
The initialization of SAM works now (the parameters are getting updated)
Added training script for Cremi (and updated for LiveCell)

In general, UNETR models can now be called from two obvious functions super easily (from torch_em.model import build_unetr_with_sam_initialization, build_unetr_without_sam_initialization) (not 100% of the nomenclature though)

And now the final fix is also in (other ViT models can be switched and used as well) ;) Thanks!

The test failure is unrelated. I will merge and fix that in a separate PR.


Hybrid package

Coverage remained the same at 100.0% when pulling b2d30a50827226600e1627865edd48a0395e46bc on hybrid-package into fd4874969d488ed725115bff009d5d24c75148ed on master.


WIFI-1458-Tx-Power-Range

This patch will resolve the radio config fail problem, when tx
power configured more than allowed operational range of AP.
Signed-off-by: Nagendrababu<EMAIL_ADDRESS>

Merged, thanks


Catch C++ exceptions for empty segments

This fixes issue #56 by annotating the PSL.getPLD method as possibly raising an exception.
https://stackoverflow.com/questions/26904268/cython-both-const-and-except-in-c-method-declaration references the fact that the const and except + qualifiers cannot co-exist, but also that the trailing const qualifier is unnecessary.

Closing this in favor of #58.


Question: any plans to release wheels for Python 3.10 ?

title

Released 1.0.4 and added support for 3.10. Let me know if it does not work for you.

Like a charm, thank you very much for releasing so quickly !


Either communicate in English or move your project to a different place.

If you open-source a project, then ensure that everyone is able to participate.
English is spoken by everyone in the open-source communities.
Either accept this fact and ensure that every communication is in English AND NOT in Chinese or move your projects please to a different place.
This is very arrogant to communicate in Chinese here.
如果你開源一個項目，那麼確保每個人都能參與。
開源社區中的每個人都說英語。
要么接受這個事實，並確保每一次交流都是用英語而不是中文，要么把你的項目移到不同的地方。
在這裡用中文交流是很囂張的。

。。。。。

If you open-source a project, then ensure that everyone is able to participate.
English is spoken by everyone in the open-source communities.
Either accept this fact and ensure that every communication is in English AND NOT in Chinese or move your projects please to a different place.
This is very arrogant to communicate in Chinese here.
如果你開源一個項目，那麼確保每個人都能參與。
開源社區中的每個人都說英語。
要么接受這個事實，並確保每一次交流都是用英語而不是中文，要么把你的項目移到不同的地方。
在這裡用中文交流是很囂張的。

Hi Zopyx,
Thank you for your suggestion and opinion. I am full agree your opinion about "If you open-source a project, then ensure that everyone is able to participate.", and I am also full understand what your feeling about you meet so many Chinese when you look this webpage. I ever work in Israel and USA for years, I ever hope everyone speak English also. :) Based on our early discuss, and consider your request and feeling, we got some common rules, hope you help check and verify, if you have any doubt, please let me to know , we are open mind community, anything can be discuss with polite attitude.

We hope everyone raise opinion and have hotness discuss. but must be polite attitude. otherwise the reply will be delete base on your suggestion. and I had delete some reply since the wording is impolite.

In our team, we will use English by default. and base on my experience cooperation with foreign team, if any foreigner on the spot，we will speak English. It's not only for talk but also it's respect!

Beside our team, we don't hope to force speak English or Chinese or German etc. and we will try to reply the question by quizzer language, you know the Language is just an instrument for communication, the opinion is more important. For important issue, we will reply by bilingual, and make you understand easily. Based on my experience, if force to use English may get bad communication results. You know the English level is different for everyone, force english will get more misunderstand, and more difficult to know each other sometime.

So We will keep the relevant contents is english and don't have any impolite wording in the discuss group. For other Chinese part, you may ignore, or you can try to translate by google if you want to learn more Chinese, or you want know what the guys talk about. I think we will became good friends when we know each other more. :)

@zopyx You are posting discriminatory content. I am reporting this to GitHub.

@zopyx You are posting discriminatory content. I am reporting this to GitHub.

Do it. But perhaps you should learn how to handle open-source projects before releasing something.

Chinese or move your projects please to a different place.
This is very arrogant to communicate in Chinese hereChinese.

You are in no position to accuse someone else being arrogant, unless they pose exactly the same accusation to you first.

Hi Guys, We got ave some misunderstanding at beginning,  now we have got common rules based on all our opinion, please check and confirm, if any doubt, we can fix it as soon as possible, then we can stop useless squabble.

Chinese or move your projects please to a different place.
This is very arrogant to communicate in Chinese hereChinese.

You are in no position to accuse someone else being arrogant, unless they pose exactly the same accusation to you first.

Will do..obviously you do not care about community building and about contributions and feedback from outside the Chinese world...your problem...good luck :)

Of course the maintainers care about community building, only that comes from contributors that submit bug reports and PRs, but not trolls.
You have deleted your comments, so obviously you KNEW that you are not being well-behaved.

人家种族歧视，你们搁这用英文回复，不是正中下怀？

@zopyx 就你这点破开源参与度，有资格代表 GitHub 在这说话么，滑稽，还没一个中国本科生参与开源贡献多

@zopyx 你寄吧谁啊？

Again, you are unwilling to communicate properly? Do want you want. This project is obviously of zero interest for the English-speaking world (means the rest of the world outside China) 🤷🏻♂

Please don't use hate speech against discriminative content. I am reporting all of them to GitHub.

Again, you are unwilling to communicate properly? Do want you want. This project is obviously of zero interest for the English-speaking world (means the rest of the world outside China) 🤷🏻♂

Hi Zopyx, I am very respect your opinions and suggestions, and have lots discuss in group for common rules to make all of us to happy, and I have waste more than 1h to reply your part, I hope you like our idea or give more useful suggestion. Do you ever read my reply?  I will post it again.
Hi Zopyx,
Thank you for your suggestion and opinion. I am full agree your opinion about "If you open-source a project, then ensure that everyone is able to participate.", and I am also full understand what your feeling about you meet so many Chinese when you look this webpage. I ever work in Israel and USA for years, I ever hope everyone speak English also. :) Based on our early discuss, and consider your request and feeling, we got some common rules, hope you help check and verify, if you have any doubt, please let me to know , we are open mind community, anything can be discuss with polite attitude.
We hope everyone raise opinion and have hotness discuss. but must be polite attitude. otherwise the reply will be delete base on your suggestion. and I had delete some reply since the wording is impolite.
In our team, we will use English by default. and base on my experience cooperation with foreign team, if any foreigner on the spot，we will speak English. It's not only for talk but also it's respect!
Beside our team, we don't hope to force speak English or Chinese or German etc. and we will try to reply the question by quizzer language, you know the Language is just an instrument for communication, the opinion is more important. For important issue, we will reply by bilingual, and make you understand easily. Based on my experience, if force to use English may get bad communication results. You know the English level is different for everyone, force english will get more misunderstand, and more difficult to know each other sometime.
So We will keep the relevant contents is english and don't have any impolite wording in the discuss group. For other Chinese part, you may ignore, or you can try to translate by google if you want to learn more Chinese, or you want know what the guys talk about. I think we will became good friends when we know each other more. :)

If you open-source a project, then ensure that everyone is able to participate.
English is spoken by everyone in the open-source communities.
Either accept this fact and ensure that every communication is in English AND NOT in Chinese.
如果你開源一個項目，那麼確保每個人都能參與。
開源社區中的每個人都說英語。
要么接受這個事實，並確保每一次交流都是用英語而不是中文，要么把你的項目移到不同的地方。
在這裡用中文交流是很囂張的。
It's better to use English in the open source communities.  But could you use Simple Chinese instead of Traditional Chinese? We are modern people now, not in Qing dynasty anymore.

种族歧视者，你没有资格教我们做事，我们有使用中文的权力！

好，原来说事实也能被删

原来一个外国的地图炮喷子的 issue 不用被删，一个用事实上反怼回去的 comment 要被删掉，我笑了

好，原来说事实也能被删

原来一个外国的地图炮喷子的 issue 不用被删，一个用事实上反怼回去的 comment 要被删掉，我笑了

Hi Richardchien， 你的回复包含人身攻击的内容了，换位思考下，有人这样说我，我肯定不开心啦。zopyx的帖子，最初不好的内容，他自己已经删除了，中文的部分还保留了“在這裡用中文交流是很囂張的。”内容，他知道的话，应该也会删除的。关于用中文还是英文，我觉得是个好问题，群里有那么多外国人，如何才能让大家能更好的交流，确实是值得讨论的，只是开始有人说了脏活，才闹得大家都不愉快的，后面有了规则，这种情况会直接删除评论，这种问题应该就不会发生了。

中文:
如果有人喜欢用中文，用google翻译翻译一下，把对应的英文一起贴下面就行了。不过还是鼓励用英文，毕竟现在全世界的通用语言还是是英文。

要么接受這個事實，並確保每一次交流都是用英語而不是中文，要么把你的項目移到不同的地方

@zopyx 为什么不用英文就得把项目移到不同的地方，你也太偏激了，只是鼓励，不是强制，如果你真的需要了解什么信息而没有英文的话，翻译软件也能帮你。

English:
If someone likes to use Chinese, use Google Translate to translate it and paste the corresponding English together below. However, the use of English is still encouraged, after all, the common language in the world is still English.

要么接受這個事實，並確保每一次交流都是用英語而不是中文，要么把你的項目移到不同的地方

@zopyx Why do you have to move the project to a different place without using English?  It's just encouragement, not mandatory. If you really need to know something and don't have English, translation software can help you.


Drop mockito for flutter_goldens

Part of a minor quest to get rid of mockito to make NNBD migrations easier.
During this, I noticed that tests were creating files on me and found that the goldens client was not using its process manager but instead using io.Process.run, so I fixed that up too.

Yeah, I'm having trouble reproducing it locally cause I think it goes down a different code path on CI

Yeah, I'm having trouble reproducing it locally cause I think it goes down a different code path on CI

Ok, I had one method where I forgot to add _goldctl to the list of arguments. It should hopefully pass now.

Ok, I had one method where I forgot to add _goldctl to the list of arguments. It should hopefully pass now.

Tests appear to be happy now

Tests appear to be happy now


403 ForbiddenException: null while updateThingShadow

I have been hacking at this all day. I can do iotdata.getThingShadow from working with service objects in aws-amplify but for some reason i get a brutal 403 when i try to iotdata.updateThingShadow. I busted out Postman and everything seems to work raw API. Any help would go a long long long way before i become a farmer.
Auth.currentCredentials()
.then(credentials => {
const iotdata = new AWS.IotData({
endpoint: 'xxxx',
region:'us-east-1',
credentials: Auth.essentialCredentials(credentials)
});
var boom ={state:{userID:"BEDFORD"}};
            var params = {
                payload:JSON.stringify(boom),
                thingName: 'lawndart'
            };

            iotdata.updateThingShadow(params, function(err, data) {
                if (err) console.log(err, err.stack); // an error occurred
                else     console.log(data);           // successful response
            })

        });

needed to add "iot:UpdateThingShadow" to the local cert in IOT web console for thing.


Text function: thousands grouping incorrectly applied when preceded by an escaped numeric format char

The result of Text(12345.34567, "0\#,0") should be "1234#,5" - since the , character is not between two numeric format chars, it should not be interpreted as a thousands separator. The function currently returns "12,34#5".

Fixed in 1997


Web.Config overridden when using publish

Repro:

Create a new ASP VNext project using the template
Add a web.config to wwwroot
Modify the web.config as you like
right click the project and hit Publish
In the Publish Web window that comes up go to Settings and set
5.1. Configuration:Release
5.2. Target Kre Version: KRE-CLR-amd641.0.0-beta1
5.3. File Publish Options: Unmark both options

Hit Publish
choose To FIle System.
go to the deployment folder you have set under the Connection tab in the Publish Web window.
go to wwwroot and open the web.config.
You will find that it now contains configurations for the kre instead of using your web.config.

Yeap, Web.config is not transformed, but replaced. It is not good, I need to specify rewrite rules for IIS. Are web.Debug.config nad web.Release.config added automatically to your project?

/cc @ChengTian I believe this has since been fixed. If you can still repro it then reopen the bug

Just verified with latest version of DNX (1.0.0-beta6-12170), couldn't reproduce.


{split} is treatas invalid

\begin{split}  \cos 2x &= \cos^2x - \sin^2x \\  &=2\cos^2x-1  \end{split}

should be

Not implemented yet, so I am treating this as feature request

Not implemented yet, so I am treating this as feature request

hi, this type  \begin{xxxx}  like \begin{align}  also not implemented yet!


How to send a request which payload is byte array

I want to send an instruction to the client, requiring payload is byte array. But I couldn't find a request that met this requirement.

(feel free to reopen it, if needed)


[docs] Improvement ideas for Base UI docs

This is an umbrella issue to gather together the documentation projects and tasks we'd like to complete before the stable release of Base UI (or very soon thereafter).
As decided in the Core documentation forum, we will prioritize improvements to the Base UI docs. These improvements include:

mui/material-ui#36193
revamping the Getting Started section of the docs

making the Overview page more visually appealing; sharpening the value proposition - creating a Why Base UI? page to follow the Overview

one final round of editorial polishing: fixing broken header links, minor grammar and style inconsistencies

mui/material-ui#38529
mui/material-ui#38826

adding Introduction demos where they're missing, and removing Basics demos when they're duplicates of Intro demos

One key improvement we still need to deliberate on is how to present demos/examples of Base UI components implemented in real(istic) use cases (rather than isolated in feature demos), like we do with Templates for Material UI and Joy UI. Templates as such don't necessarily make sense for Base UI, because it doesn't really "look" or "feel" like anything special out of the box with no styles, and it doesn't come packaged with any layout components. Plus, it kind of misses the purpose of Base UI, which is about maximizing freedom and flexibility—meaning we probably don't want to impose any style opinions on the developer.
Ideas floated include:

component gallery - showing off (any and all) design system implementations - akin to a project showcase
recipe kits - possibly implementing Joy Design (or else a very minimal but still production-ready system) via an "own your code" pattern à la shadcn/ui - but then what styling solution do we choose and why? (this may not be feasible to accomplish before the stable but is worth considering)
design system scaffold - optimized for implementing a custom design system with Storybook and other relevant tooling already installed, with very minimal style decisions made
all of the above? none of the above? something else entirely? 🙃

I'll create separate issues and PRs for the improvements we've already settled on.
I'd love to hear people's thoughts about the latter half. Assuming we'll never have time to do them all—what would be most useful to the community when they show up on day one of the stable release? That's what we want to do!
Note that the scope here is limited to documentation content rather than infrastructure.

@colmtuite, @vladmoroz, FYI, we discussed this a long time ago (regarding the old Base UI docs). Perhaps something to consider in the new docs as well?


Unbox small records

Problem

We allocate memory blocks for records of any size unless they have no field.
Those extra heap allocations are sometimes expensive.

Solution

Unbox small records that have only a field of a size less than a word.

Those fields are all simple concrete types (i.e. non-union types.)

This is safe even for recursive types but might need some tweaks for a compiler.

For example, LLVM might complain about a self-recursive type of type foo { x foo }.
They can be represented as type foo { x usize } instead.

Do we want to change the FFI library too to implement easy-to-use new() constructors automatically.

They box or unbox records depending on a number of fields.

What about bigger primitives that aren't implemented by the language, such as complex numbers?

Thanks for your question!

What about bigger primitives that aren't implemented by the language, such as complex numbers?

It doesn't matter how big the primitives in the language are because this optimization is totally internal and not actually limited to small records but also applicable to any multi-word values. We can just box or unbox big primitives on demand at boundaries if necessary (e.g. to box big primitives into "variant" types or to make big primitives FFI-safe.)

Would such a target qualify for this optimization?

So yes!
But of course, data transfer between Pen and foreign languages like Rust is another topic on optimization!


[feature request] Add CAST function

CAST is the function that converts field type in the select query.
For example, if convert from string field 'fieldA' to integer, query is like this:
select cast(fieldA AS integer), ...

At least, It is preferable to support integer/float/string as conversion type.

I think CAST function is the ideal solution.
But we needed to use sum function for string field of decimal number in 0.9 ASAP.
So I implemented conversion feature in sum function, that converts from string to integer/float implicitly.
https://github.com/sudabon/influxdb/commit/9e8290a8bfbe5354b17428f5c4e329beedcccf95
If you decide not to implement CAST function, I hope you merge this.
When you contact with me, I will send pull request.

As mentioned in my post to the mailing list we are experimenting with simplifying our open GitHub Issues. This feature request has been rolled into an aggregate issue for all function requests, so that we can close this issue until we are ready to work on it.
You may continue to make comments here. Closing the issue does not mean we are rejecting this idea.

I am also in dire need of a cast function to run aggregate queries on columns that are strings. Any suggestions?

I am also in dire need of a cast function to run aggregate queries on columns that are strings. Any suggestions?

I strongly support either this function or the ability to change field type ( #2651 ). Ideally both of them - would add so much flexibility!
My use case:
I had ifluxdb populated with logstash plugin via use_event_fields_for_data_points option. However, I forgot to set up coerce_values properly, thus logstash sent everything as strings. Now I have no option to fix this except deleting all the stuff and running it from scratch which is not very pleasant option.


Add content about the rules

link to the rules
link to the accreditations
link to awesome apps about the rules (eg the one from wfdf)

We could merge Essentials and Tactics to make room for the rules

Videos about the rules have been added there https://github.com/disc-in/UltimateApp/pull/288

Videos about the rules have been added there https://github.com/disc-in/UltimateApp/pull/288


Terminal content is limited

Issue Type: Bug
When I open new terminal, sometimes it's content is limited. I can't explain it properly, but it looks like the actual terminal only took about 15% of the available area.
Screenshot
VS Code version: Code 1.42.1 (c47d83b293181d9be64f27ff093689e8e7aed054, 2020-02-11T14:45:59.656Z)
OS version: Windows_NT x64 10.0.18362

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (8 x 2592)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_offsurface_control: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.80GB (1.71GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (2)

Extension
Author (truncated)
Version

vscode-eslint
dba
2.1.1

graphql-for-vscode
kum
1.15.3

I believe this is already fixed, can you see if you can reproduce in the Insiders build?

I can. It might be the issue with my OS, since the terminal opened normally looks like that too.


⚠ Bofrost.at has degraded performance

In af91ac2, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 4769 ms

Resolved: Bofrost.at performance has improved in ca906eb.


fixing bug that caused clients to fail connection completion on Windows

Yeah you read that right.  I've been messing around with the windows subsystem for Linux and ran into this issue pretty quickly.  Apparently this whole time client connections (probably only to localhost) have not worked on Windows because we weren't properly handling the result of SocketChannel.connect().
At least on Linux and MacOs, connecting to localhost is asynchronous, so SocketChannel.connect() returns false and we must subscribe the selection key to OP_CONNECT.  However on windows it appears that the method returns true and the connection is immediately established.  This meant not only were we never calling Connection.handleConnected(), but because the OP_CONNECT interest is apparently the same as OP_WRITE, it would cause the worker to go nuts constantly selecting the connection over and over with nothing to do, pegging the CPU.
Best I can tell this totally fixes the issue.  All tests pass locally and I can run all the examples.  I also had to tweak timeouts on a few tests, as it appears there is a delay when a connection on windows to localhost is refused.

Current coverage is 83.79% (diff: 50.00%)

Merging #474 into master will decrease coverage by 0.02%

@@             master       #474   diff @@
==========================================
  Files            79         79
  Lines          3924       3925     +1
  Methods        3571       3567     -4
  Messages          0          0
  Branches        353        358     +5
==========================================
  Hits           3289       3289
- Misses          635        636     +1
  Partials          0          0

Powered by Codecov. Last update 909c42b...d87382a

👍

👍


Jenkinsfile from example for testing and setup

Pull request open as testing purposes for Jenkins.
Need to install Android Development environment for Jenkins server before this actually works.

So finally working but with following notes:

Must have: GRADLE_USER_HOME environmental variable set with some folder as cache like: C:/gradle-cache (stackoverflow)
Jenkinsfile environment config is important.
Unit test -> None written so not enabled, Deploy part commented out, not implemented full pipeline yet.
Static analysis -> linting should be enabled... do that.


[Feature]: Propagate unhandled errors from resource requests

What is the new or updated feature that you are suggesting?
The framework should allow developers to handle unhandled errors that are thrown within loaders/actions within resource routes.
Why should this feature be included?
Errors that are thrown within these routes are captured and automatically processed by the framework. This leads to the error being logged to the console and an internal server error response being returned to the caller. This makes sense for document requests since a developer is able to use a CatchBoundary or ErrorBoundary to get access to the error that was thrown.
The particular scenario that this affects is error logging/monitoring. Currently the automatic logic makes it difficult to globally send these errors to Sentry and/or some other external service without wrapping try/catch blocks around each instance.

Here is the block of code for reference: https://github.com/remix-run/remix/blob/1fd70960e4d88740df5bf407a6ba2cd2b9549459/packages/remix-server-runtime/server.ts#L512-L550


'insightface'

building 'insightface.thirdparty.face3d.mesh.cython.mesh_core_cython' extension
***       error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
***       [end of output]

***   note: This error originates from a subprocess, and is likely not a problem with pip.
***   ERROR: Failed building wheel for insightface
*** ERROR: Could not build wheels for insightface, which is required to install pyproject.toml-based projects
 File "F:\aipeiyin\sd-\sd-A\sd-webui-aki-directml-v4.4\extensions\sd-wav2lip-uhq\scripts\faceswap\swap.py", line 6, in <module>
    import insightface
ModuleNotFoundError: No module named 'insightface'

提示：Python 运行时抛出了一个异常。请检查疑难解答页面。

Hi,
Thanks for report
Yes, you need to install  Microsoft Visual C++ 14.0 from https://visualstudio.microsoft.com/visual-cpp-build-tools/
I'll add it in README.md
Let me know if it works after install it
regards

Thanks for report
Regards


Getting vagrant working out of the box.

I cloned this repo for the first time and ran vagrant up on ubuntu 18.04.
I got the following error:
TASK [lobsters : migrate database] *********************************************
Saturday 24 August 2019  18:47:59 -0500 (0:01:46.212)       0:03:19.467 *******
fatal: [lobsters.xen.prgmr.com]: FAILED! => {"changed": true, "cmd": ["bundle", "exec", "rails", "db:migrate"], "delta": "0:00:02.318427", "end": "2019-08-24 23:48:01.101530", "msg": "non-zero return code", "rc": 1, "start": "2019-08-24 23:47:58.783103", "stderr": "rails aborted!\nCannot load database configuration:\nCould not load database configuration. No such file - [\"config/database.yml\"]\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/application/configuration.rb:185:in `database_configuration'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activerecord-5.2.3/lib/active_record/railtie.rb:133:in `block (2 levels) in <class:Railtie>'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/lazy_load_hooks.rb:71:in `instance_eval'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/lazy_load_hooks.rb:71:in `block in execute_hook'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/lazy_load_hooks.rb:62:in `with_execution_control'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/lazy_load_hooks.rb:67:in `execute_hook'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/lazy_load_hooks.rb:52:in `block in run_load_hooks'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/lazy_load_hooks.rb:51:in `each'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/lazy_load_hooks.rb:51:in `run_load_hooks'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activerecord-5.2.3/lib/active_record/base.rb:328:in `<module:ActiveRecord>'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activerecord-5.2.3/lib/active_record/base.rb:27:in `<top (required)>'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `require'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `block in require'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:257:in `load_dependency'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `require'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/scenic-1.5.1/lib/scenic/adapters/postgres.rb:38:in `initialize'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/scenic-1.5.1/lib/scenic/configuration.rb:10:in `new'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/scenic-1.5.1/lib/scenic/configuration.rb:10:in `initialize'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/scenic-1.5.1/lib/scenic/configuration.rb:16:in `new'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/scenic-1.5.1/lib/scenic/configuration.rb:16:in `configuration'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/scenic-1.5.1/lib/scenic/configuration.rb:35:in `configure'\n/srv/lobste.rs/http/config/initializers/scenic.rb:1:in `<top (required)>'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:285:in `load'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:285:in `block in load'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:257:in `load_dependency'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:285:in `load'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/engine.rb:657:in `block in load_config_initializer'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/notifications.rb:170:in `instrument'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/engine.rb:656:in `load_config_initializer'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/engine.rb:614:in `block (2 levels) in <class:Engine>'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/engine.rb:613:in `each'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/engine.rb:613:in `block in <class:Engine>'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/initializable.rb:32:in `instance_exec'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/initializable.rb:32:in `run'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/initializable.rb:61:in `block in run_initializers'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/initializable.rb:50:in `each'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/initializable.rb:50:in `tsort_each_child'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/initializable.rb:60:in `run_initializers'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/application.rb:361:in `initialize!'\n/srv/lobste.rs/http/config/environment.rb:5:in `<top (required)>'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `require'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `block in require'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:257:in `load_dependency'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `require'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/application.rb:337:in `require_environment!'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/application.rb:520:in `block in run_tasks_blocks'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/commands/rake/rake_command.rb:23:in `block in perform'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/commands/rake/rake_command.rb:20:in `perform'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/command.rb:48:in `invoke'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/commands.rb:18:in `<top (required)>'\nbin/rails:4:in `require'\nbin/rails:4:in `<main>'\n\nCaused by:\nCould not load database configuration. No such file - [\"config/database.yml\"]\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/application/configuration.rb:185:in `database_configuration'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activerecord-5.2.3/lib/active_record/railtie.rb:133:in `block (2 levels) in <class:Railtie>'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/lazy_load_hooks.rb:71:in `instance_eval'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/lazy_load_hooks.rb:71:in `block in execute_hook'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/lazy_load_hooks.rb:62:in `with_execution_control'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/lazy_load_hooks.rb:67:in `execute_hook'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/lazy_load_hooks.rb:52:in `block in run_load_hooks'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/lazy_load_hooks.rb:51:in `each'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/lazy_load_hooks.rb:51:in `run_load_hooks'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activerecord-5.2.3/lib/active_record/base.rb:328:in `<module:ActiveRecord>'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activerecord-5.2.3/lib/active_record/base.rb:27:in `<top (required)>'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `require'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `block in require'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:257:in `load_dependency'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `require'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/scenic-1.5.1/lib/scenic/adapters/postgres.rb:38:in `initialize'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/scenic-1.5.1/lib/scenic/configuration.rb:10:in `new'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/scenic-1.5.1/lib/scenic/configuration.rb:10:in `initialize'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/scenic-1.5.1/lib/scenic/configuration.rb:16:in `new'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/scenic-1.5.1/lib/scenic/configuration.rb:16:in `configuration'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/scenic-1.5.1/lib/scenic/configuration.rb:35:in `configure'\n/srv/lobste.rs/http/config/initializers/scenic.rb:1:in `<top (required)>'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:285:in `load'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:285:in `block in load'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:257:in `load_dependency'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:285:in `load'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/engine.rb:657:in `block in load_config_initializer'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/notifications.rb:170:in `instrument'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/engine.rb:656:in `load_config_initializer'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/engine.rb:614:in `block (2 levels) in <class:Engine>'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/engine.rb:613:in `each'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/engine.rb:613:in `block in <class:Engine>'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/initializable.rb:32:in `instance_exec'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/initializable.rb:32:in `run'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/initializable.rb:61:in `block in run_initializers'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/initializable.rb:50:in `each'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/initializable.rb:50:in `tsort_each_child'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/initializable.rb:60:in `run_initializers'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/application.rb:361:in `initialize!'\n/srv/lobste.rs/http/config/environment.rb:5:in `<top (required)>'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `require'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `block in require'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:257:in `load_dependency'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `require'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/application.rb:337:in `require_environment!'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/application.rb:520:in `block in run_tasks_blocks'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/commands/rake/rake_command.rb:23:in `block in perform'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/commands/rake/rake_command.rb:20:in `perform'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/command.rb:48:in `invoke'\n/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/commands.rb:18:in `<top (required)>'\nbin/rails:4:in `require'\nbin/rails:4:in `<main>'\nTasks: TOP => db:migrate => db:load_config => environment\n(See full trace by running task with --trace)", "stderr_lines": ["rails aborted!", "Cannot load database configuration:", "Could not load database configuration. No such file - [\"config/database.yml\"]", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/application/configuration.rb:185:in `database_configuration'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activerecord-5.2.3/lib/active_record/railtie.rb:133:in `block (2 levels) in <class:Railtie>'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/lazy_load_hooks.rb:71:in `instance_eval'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/lazy_load_hooks.rb:71:in `block in execute_hook'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/lazy_load_hooks.rb:62:in `with_execution_control'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/lazy_load_hooks.rb:67:in `execute_hook'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/lazy_load_hooks.rb:52:in `block in run_load_hooks'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/lazy_load_hooks.rb:51:in `each'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/lazy_load_hooks.rb:51:in `run_load_hooks'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activerecord-5.2.3/lib/active_record/base.rb:328:in `<module:ActiveRecord>'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activerecord-5.2.3/lib/active_record/base.rb:27:in `<top (required)>'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `require'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `block in require'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:257:in `load_dependency'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `require'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/scenic-1.5.1/lib/scenic/adapters/postgres.rb:38:in `initialize'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/scenic-1.5.1/lib/scenic/configuration.rb:10:in `new'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/scenic-1.5.1/lib/scenic/configuration.rb:10:in `initialize'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/scenic-1.5.1/lib/scenic/configuration.rb:16:in `new'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/scenic-1.5.1/lib/scenic/configuration.rb:16:in `configuration'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/scenic-1.5.1/lib/scenic/configuration.rb:35:in `configure'", "/srv/lobste.rs/http/config/initializers/scenic.rb:1:in `<top (required)>'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:285:in `load'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:285:in `block in load'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:257:in `load_dependency'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:285:in `load'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/engine.rb:657:in `block in load_config_initializer'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/notifications.rb:170:in `instrument'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/engine.rb:656:in `load_config_initializer'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/engine.rb:614:in `block (2 levels) in <class:Engine>'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/engine.rb:613:in `each'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/engine.rb:613:in `block in <class:Engine>'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/initializable.rb:32:in `instance_exec'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/initializable.rb:32:in `run'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/initializable.rb:61:in `block in run_initializers'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/initializable.rb:50:in `each'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/initializable.rb:50:in `tsort_each_child'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/initializable.rb:60:in `run_initializers'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/application.rb:361:in `initialize!'", "/srv/lobste.rs/http/config/environment.rb:5:in `<top (required)>'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `require'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `block in require'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:257:in `load_dependency'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `require'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/application.rb:337:in `require_environment!'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/application.rb:520:in `block in run_tasks_blocks'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/commands/rake/rake_command.rb:23:in `block in perform'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/commands/rake/rake_command.rb:20:in `perform'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/command.rb:48:in `invoke'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/commands.rb:18:in `<top (required)>'", "bin/rails:4:in `require'", "bin/rails:4:in `<main>'", "", "Caused by:", "Could not load database configuration. No such file - [\"config/database.yml\"]", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/application/configuration.rb:185:in `database_configuration'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activerecord-5.2.3/lib/active_record/railtie.rb:133:in `block (2 levels) in <class:Railtie>'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/lazy_load_hooks.rb:71:in `instance_eval'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/lazy_load_hooks.rb:71:in `block in execute_hook'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/lazy_load_hooks.rb:62:in `with_execution_control'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/lazy_load_hooks.rb:67:in `execute_hook'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/lazy_load_hooks.rb:52:in `block in run_load_hooks'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/lazy_load_hooks.rb:51:in `each'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/lazy_load_hooks.rb:51:in `run_load_hooks'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activerecord-5.2.3/lib/active_record/base.rb:328:in `<module:ActiveRecord>'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activerecord-5.2.3/lib/active_record/base.rb:27:in `<top (required)>'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `require'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `block in require'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:257:in `load_dependency'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `require'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/scenic-1.5.1/lib/scenic/adapters/postgres.rb:38:in `initialize'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/scenic-1.5.1/lib/scenic/configuration.rb:10:in `new'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/scenic-1.5.1/lib/scenic/configuration.rb:10:in `initialize'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/scenic-1.5.1/lib/scenic/configuration.rb:16:in `new'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/scenic-1.5.1/lib/scenic/configuration.rb:16:in `configuration'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/scenic-1.5.1/lib/scenic/configuration.rb:35:in `configure'", "/srv/lobste.rs/http/config/initializers/scenic.rb:1:in `<top (required)>'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:285:in `load'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:285:in `block in load'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:257:in `load_dependency'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:285:in `load'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/engine.rb:657:in `block in load_config_initializer'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/notifications.rb:170:in `instrument'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/engine.rb:656:in `load_config_initializer'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/engine.rb:614:in `block (2 levels) in <class:Engine>'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/engine.rb:613:in `each'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/engine.rb:613:in `block in <class:Engine>'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/initializable.rb:32:in `instance_exec'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/initializable.rb:32:in `run'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/initializable.rb:61:in `block in run_initializers'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/initializable.rb:50:in `each'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/initializable.rb:50:in `tsort_each_child'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/initializable.rb:60:in `run_initializers'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/application.rb:361:in `initialize!'", "/srv/lobste.rs/http/config/environment.rb:5:in `<top (required)>'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `require'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `block in require'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:257:in `load_dependency'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `require'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/application.rb:337:in `require_environment!'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/application.rb:520:in `block in run_tasks_blocks'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/commands/rake/rake_command.rb:23:in `block in perform'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/commands/rake/rake_command.rb:20:in `perform'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/command.rb:48:in `invoke'", "/srv/lobste.rs/http/vendor/bundle/ruby/2.3.0/gems/railties-5.2.3/lib/rails/commands.rb:18:in `<top (required)>'", "bin/rails:4:in `require'", "bin/rails:4:in `<main>'", "Tasks: TOP => db:migrate => db:load_config => environment", "(See full trace by running task with --trace)"], "stdout": "", "stdout_lines": []}

It looks like out of the box, it's cloning the lobsters git repo and then running db:migrate without creating a config/database.yml which results in the error.
How am I supposed to set up this repo so that it cleanly runs?

@jstoja Do you want to chime in on this? I don't think it's been touched much since #10.

Started to fix it, but hit #68. All in all, the configuration file should probably be templated by Ansible in the future.
Since it contains secrets, this kind of information should be stored in ansible-vault (AES256).

I've removed the Vagrantfile because I don't know how to maintain it. Like with the Docker repo and our Rails app, I'd prefer to link to an external repo.

I've removed the Vagrantfile because I don't know how to maintain it. Like with the Docker repo and our Rails app, I'd prefer to link to an external repo.


softDelete and react-admin, how do I send extra params to the api during update requests

I have posted the following question on stack-overflow as well. https://stackoverflow.com/questions/57599531/softdelete-and-react-admin-how-do-i-send-extra-params-to-the-api-during-update
We are using softDelete, from feathers-hooks-common for our users. In order for us to edit (or undelete) users that have been softDeleted, we need to pass $ignoreDeletedAt: true to the api in the update request. I have been digging through the react-admin and ra-data-feathers documentation, but I don't see a way to do that.
We are using the ra-data-feathers data provider, which says this:
const options = {
  id: 'id', // If your database uses an id field other than 'id'. Optional.
  usePatch: false, // Use PATCH instead of PUT for UPDATE requests. Optional.
  my_resource: { // Options for individual resources can be set by adding an object with the same name. Optional.
    id: 'id', // If this specific table uses an id field other than 'id'. Optional.
  },
}

This my_resource option is the only place I have seen in the documentation to interact with the query. I have tried to add a 'users' resource to Admin to pass my parameter
<Admin loginPage={Login} authProvider={authProvider} dataProvider={restClient(app, { id: '_id', usePatch: true, users: { params: { $ignoreDeletedAt: true } } })}>

I have also attempted a few other syntaxes, but nothing extra seems to be passed to the server when trying to update the user. Any direction would be most welcome. Thanks in advance.

I think you can do a PR to support that. Some clues to do it:

add in options a softDelete flag with false as defulat

const options = {
  id: 'id', // If your database uses an id field other than 'id'. Optional.
  usePatch: false, // Use PATCH instead of PUT for UPDATE requests. Optional.
  softDelete: false,
  my_resource: { // Options for individual resources can be set by adding an object with the same name. Optional.
    id: 'id', // If this specific table uses an id field other than 'id'. Optional.
  },
}

Then for PATCH, UPDATE or UPDATE_MANY you can check if softDelete is true, if is you add $ignoreDeletedAt: true to data (sent to feathers client)

Tell what do you think about?

@josx Thanks for the reply! I have been looking into this, and think this is what you're suggesting. In /node_modules/ra-data-feathers/lib/restClient.js starting line 83
case _reactAdmin.UPDATE:
        if (usePatch) {
          var data = params.previousData ? (0, _objectDiff2.default)(params.previousData, params.data) : params.data;
          data.ignoreDeletedAt = true; // ADDED BY ME
          return service.patch(params.id, data);
        } else {
          var _data = idKey !== defaultIdKey ? deleteProp(params.data, defaultIdKey) : params.data;
          return service.update(params.id, _data);
        }

(I am not checking for softDelete before adding ignoreDeletedAt at the moment, I will add the conditional for that later.) I am attempting to send a request to my local api server with ignoreDeletedAt in the right spot. SoftDelete.js is looking for context.params.$ignoreDeletedAt, but adding data.ignoreDeletedAt = true; as above, places ignoreDeletedAt in context.data and context.arguments[1]. Any ideas on how would I go about getting that option into context.params Thanks again!

Check feathers doc:
https://docs.feathersjs.com/api/services.html#patchid-data-params
You have to send a third argument to that function in this way:
service.patch(params.id, data, { ignoreDeleteAt: true});

Awesome, thanks for that! I was able to get it to show up on my server by using paramsForServer from feathers-hooks-common (and on my server I use paramsFromClient to allow it in) . I am hoping it will be okay to add that dependency. I will create a PR with my changes soon.
I have not been working with Node and related technologies that long, and therefore I am not really familiar with how your repo is set up. In my local server, ra-data-feathers has a lib folder (complied by babel, maybe? idk), which is where I made my changes for testing locally. For the pull request, I just ported my changes into src/restClient.js If that is problematic or just completely wrong, please instruct and I will correct, thanks!

#121


Saved search dropdown api/event/logs

To test, pull branch and navigate to

#reports/logbrowser
#reports/apibrowser
#reports/eventbrowser

and check that the predefined searches in the dropdowns are as expected.
Then...
click on the gear next to any of the predefined search dropdowns and create a new predefined search for api/log/event.
Navigate back to the reports and verify that your predefined searches show up in the dropdown list.
Also, please test updating and deletion of your own predefined searches.
your custom predefined searches in events/api will not trigger chart changes. That functionality is ticketed and will be handled then.

Current coverage is 70.43%

Merging #334 into master will decrease coverage by -0.28% as of 4559ca2

@@            master    #334   diff @@
======================================
  Files           84      84
  Stmts         2718    2709     -9
  Branches         0       0
  Methods          0       0
======================================
- Hit           1922    1908    -14
  Partial          0       0
- Missed         796     801     +5

Review entire Coverage Diff as of 4559ca2

Uncovered Suggestions

+0.62% via goldstone/views.py#30...46
+0.59% via ...stone/drfes/views.py#134...149
+0.37% via ...dstone/core/tasks.py#134...143
See 7 more...

Powered by Codecov. Updated on successful CI builds.

Some general changes to headers and buttons:

Applies to all viewers.

Applies to all:

Don't quite understand the statement about wiring up the search.  When you create it, you should have a refreshed list in the "predefined search" dropdown.  When it's selected, the call should be made to /saved_search/{uuid} just like any other search.
If you're concerned about whether the search is well formed and has the right aggregation to draw the chart, don't be.  Consider this MVP.  We'll work on validation both on the front/back.  For now, assume that the search will:
a) be well formed with proper aggregation
b) be bell formed without aggregation (maybe then put a popup alert in the chart: "No chart data defined in search"
c) be poorly formed and you will get an error response back from server, then show a popup alert and go back to the default search.
To test each scenario:
a) take query from any of existing searches that works, and save it as a new one.
b) same as above, but remove the aggs block
c) use {} as the query

updates headings and button tags:

updates dropdown title with current saved search
works with i18n as it takes the text from the dom for the title. so if the title was entered in another language, or translated, the dropdown title will be as well.

pretty prints (only works with valid JSON):
and sets input to a text area, not just a single line input field.

:+1:


fix chef client 14 error

@ivadim I haven't had the chance to test this yet, but this should fix the error on chef 14 clients

@Stromweld thank you for contribution.
I tested it and found one more issue with Chef 14. I merge this and make small fix it in the next PR.


Edit docs to meet content strategy TBA requirements

Update all projects to meet the content strategy requirements for organization and content reuse.

change 'quick start guide' to 'quick reference guide'

should move the docs guidelines to the docs-training repo


setoid use strict equality test optimisation (fixes #699)

Before submitting a pull request, please make sure the following is done:

Fork the repository and create your branch from master.
Run npm install in the repository root.
If you've fixed a bug or added code that should be tested, add tests!
Ensure the test suite passes (npm test).

Note. If you find a typo in the documentation, make sure to modify the corresponding source (docs are generated).

@sledorze this is error prone. Since it's always safe to check for strict equality while defining a Setoid, I propose to add a fromEquals helper (like fromCompare in Ord) to the Setoid module
// Setoid.ts

export const fromEquals = <A>(equals: (x: A, y: A) => boolean): Setoid<A> => {
  return {
    // optimization --v
    equals: (x, y) => x === y || equals(x, y)
  }
}

and then use it all over the place
// Identity.ts

export const getSetoid = <A>(setoid: Setoid<A>): Setoid<Identity<A>> => {
  return fromEquals((x, y) => setoid.equals(x.value, y.value))
}

Honestly, I like the combinator but I fear the runtime overhead.
By error prone, what do you mean?

the runtime overhead

The inner call?
// this ---v
x === y || equals(x, y)

Seems negligible.

By error prone, what do you mean?

"fix issue with wrong getProductSetoid optimisation"

@gcanti I'll do the changes

Way cleaner!

@gcanti should be good now

@gcanti may I push the button? :)


Fuse crashing VVVV .net unhandled exception error CS0246

How to replicate the crash. : Make new vvvv patch, add fuse dependency, start scrolling list of examples from dependency menu. Crash
Crash Report. Screen shot of the window that cannot be copy/pasted and the text of the crash attached below.

20211125_Crash_report.txt

Hey, may I ask which version of vvvv you're using? Thanks.

Just updated and yes this crash is solved. Thanks


Recovery the issue 659

Recovery the issue 659

#659

If needs of putting instance method in blueprint is nothing, nobody try to put instance method in blueprint.
I think this is unnecessary if nobody try to put instance method in blueprint.

Actually,not nobody
In issue 659 , he want to use class and method to make his code structure more clear. Although it's not right , but I can understand it.
So,as what he say, It's necessary to give me some guide/exception for that blueprint handler shouldn't be a instance method

If it is necessary to add exception for instance method,
I think making it possible like #676 is better than adding exception.

@38elements
Seriously , I dont't think it's better than raise exception
here is detail:
If you have N instance method to add in the blueprint , that means you have to make another N _handler to decorate it .
If the N is huge , Python have to use a lot of memory to maintain a call stack , I think is a wasting-memory way.
So, I don't think it's right to allow people add instance method in blueprint route.

I think this and #676 are not necessary.
#676 making it possible to put instance method, I think it is better.


How to align chain ID of two complexes before running DockQ?

I am writing a python script to rename chain ID in predicted PDB file to align with native PBD file, and confronted with a lot of problems.
I was wondering how do you align chain IDs before running DockQ? Is there any tool?
Thank you.

I've encountered similar issues.  I left my current thoughts in a closely related issue: https://github.com/deepmind/alphafold/issues/251#issuecomment-1438190499

Before running scoring applications, I always perform smith-waterman alignment to find best matches and make the corresponding residues to have the same chain id and residue sequence number.
(It is annoying process and possibly it implement bugs :/)
If your structures have the subunits with the same sequence, you must consider permutations.
The easiest way is running MMalign (currently -mm 1 in USalign https://github.com/pylelab/USalign/blob/master/USalign.cpp ?) and weight the score with identity of the aligned residues.


feat: BYO Subnet Per AKSNodeClass + Subnet Drift

Fixes #
Description
This PR introduces support for bringing your own subnet per AKSNodeClass. Karpenter has decided to opt into subnet drift. This pr does not solve validation of the subnet and its compatibility with other subnets on the cluster.  This PR does also not solve any observability considerations.
How was this change tested?

make az-all
make test

Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[ ] No

Release Note

Pull Request Test Coverage Report for Build<PHONE_NUMBER>8
Details

47 of 67 (70.15%)  changed or added relevant lines in 9 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.05%) to 97.651%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/providers/instance/armutils.go
5
6
83.33%

pkg/cloudprovider/cloudprovider.go
3
7
42.86%

pkg/cloudprovider/drift.go
10
25
40.0%

Totals

Change from base Build<PHONE_NUMBER>0:
-0.05%

Covered Lines:
36336

Relevant Lines:
37210

💛  - Coveralls

see test result of drift e2e: https://github.com/Azure/karpenter-provider-azure/actions/runs/11111946917/job/30885575958


Support configuring a custom function with the request object as an input param for URL pattern

sw-toolbox has two  options, Express-style Routes and
Regular Expression Routes,  for configuring the routes,  but it's not flexible enough for users. If it can support  configuring a custom function with the request object as an input param for url pattern，users can do more processing according to the request object.  In order to meet this need, I have changed  two files, lib/router.js and lib/route.js,  and added some test cases in the test folder. These changes will not affect the original Routes config.Your prompt attention to this matter will be appreciated.
An example of using Function Expression routing include:
toolbox.router.get(
function(request){
  // users can get request object, do some processing accroding to the request object and return a boolean value
  if (request && reqest.headers && request.headers.referer) {
     return true;
  }
}, apiHandler);

First off, thanks for your contribution!
While sw-toolbox continues to be a supported project, we're not looking to make significant changes to the public API at this time.
A newer set of libraries, called Workbox, already provides similar functionality to what you're proposing. Specifically, the WorkboxSW.router.registerRoute() method will allow you to pass in a custom function for determining whether there's a match, and then apply a handler similar to what's supported in sw-toolbox.
If you'd prefer to continue using sw-toolbox, what you're proposing is possible without actually changing the public interface if you avoid using the sw-toolbox router, and instead use your own custom routing logic alongside the sw-toolbox strategies, like:
importScripts('/path/to/sw-toolbox.js');

self.addEventListener('fetch', event => {
  if (event.request.headers.has('referer')) {
     event.respondWith(toolbox.networkFirst(event.request));
  }
});


ContentLength isn't long enough

We love your framework! But we need requests with more than Integer.MAX_VALUE content length. We changed it in your code and we would like to share it with you :)

Thx!


wip: thorchain lp fees

Description

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #
Risk

High Risk PRs Require 2 approvals

What protocols, transaction types or contract interactions might be affected by this PR?

Testing

Engineering

Operations

Screenshots (if applicable)

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

Current dependencies on/for this PR:

develop

PR #6126

PR #6127   👈

This stack of pull requests is managed by Graphite.


The AWS Access Key Id needs a subscription for the service

ClientError: An error occurred (SubscriptionRequiredException) when calling the CreateFunction operation: The AWS Access Key Id needs a subscription for the service

Did you get a resolution to this issue?

You should look at Zappa, not django-zappa.

I've just reported an issue as Miserlou/Zappa#1220 for anyone who stumbles on this.


feat(core) tls protocol upstream support upstream tls config

Summary

tls protocol upstream support upstream tls config
add stream upstream tls function pdk API

FTI-1479

because rebase brunch is too hard, so recreate this pr for https://github.com/Kong/kong/pull/9754

@flrgh would you help me review child PR for this? Thanks. https://github.com/Kong/lua-kong-nginx-module/pull/50

please make sure docs is updated


"smooth only accepts 1 dimension arrays."

Hi there,
I was trying to use your code to do keyframe extraction, but I got "smooth only accepts 1 dimension arrays." Do you know is there anything I did wrong?
File "scene_div.py", line 63
raise ValueError, "smooth only accepts 1 dimension arrays."
^
SyntaxError: invalid syntax

Figured out it caused by python version

弄清楚了是由python版本引起的
hi there
I want to know which version of python is required


Fix malfunction on closeUnclosedXmlTags when an open  has " ins…

…ide, reported issue #49
Sample OFX attached.
sample_nubankMemoComAspas.txt

This is a duplicate PR of #48. As per the other PR, I'm happy to merge this but would it be possible to provide a new test case in the test suite please? Thanks!

Thanks @renatomb !

Released in https://github.com/asgrim/ofxparser/releases/tag/1.2.2 - thanks!


what is the exactly usage of -w --waitforcopy

Hi:
First I would like to thank the creator for this great tools.
I recently update the madmax plotter but find every time the plotting finished, the plotter is waiting for the plot copied to the destination and then start the next plotting job.  I saw a new parameter added and tried -w false or -w 0 but the plotter seems have the same behaviour.  May I ask anyone give me a example to use the -w parameter, please? thank you indeed
Happy plotting and happy farming
Kind regards

When a plot is done it is a .tmp file and being copied to the -d location, -w pauses the plotter until the copy is completed. This is useful if you are using ramdisk's or several other use cases, like overrunning the destination storage location. I have used it for PCI bus contention, network i/o normalization, and to slow down the plotters when I am waiting on more disks.
In my case I can generate a couple of hundred plots a day, I run a 40gb network, and on my fast plotters I have to set this flag or it will hit swap, and slow to a crawl if the network is saturated when the plotters drift to the same copy periods. Having seven machines copying 110gb files to two destinations slows things to a crawl.
I try and use the -w to keep the finish times not synced. It does help me, marginally.

After cleaning the

When a plot is done it is a .tmp file and being copied to the -d location, -w pauses the plotter until the copy is completed. This is useful if you are using ramdisk's or several other use cases, like overrunning the destination storage location. I have used it for PCI bus contention, network i/o normalization, and to slow down the plotters when I am waiting on more disks.
In my case I can generate a couple of hundred plots a day, I run a 40gb network, and on my fast plotters I have to set this flag or it will hit swap, and slow to a crawl if the network is saturated when the plotters drift to the same copy periods. Having seven machines copying 110gb files to two destinations slows things to a crawl.
I try and use the -w to keep the finish times not synced. It does help me, marginally.

Thank you for the reply. I am actually want to know how to use the -w parameter because no matter I use it or not, my plotter always wait the copy finished and then start a new job.

After I cleaned my old version plotter and compile from the fresh, the problem solved. If the left the -w parameter in the command, the plotter will continue to start a new job during copying the plot to my hard drive.


applets/interactive-test.py needs prompt_toolkit package

Hi,
In the docs it says to run applets/interactive-test.py to test LUNA, but this file relies on the prompt_toolkit package which is not listed in the pyproject.toml in the normal dependencies section. pip install prompt_toolkit fixes the issue.
Feel free to close this as wont-fix if you understandably don't want to add the extra dependency, but it might be good to add to the docs that you need to install the package anyway.

This is actually an Apollo bug, and I've opened https://github.com/greatscottgadgets/apollo/issues/35 to track it.
Closing it here on the LUNA side.


503 Sender already specified

Sometimes, when there is a lot of sending going on I get a "503 Sender already specified" from pool.Send() when the pool has been instantiated with
pool, err := smtppool.New(smtppool.Opt{
                Host:            os.Getenv("SMTP_HOST"),
                Port:            587,
                MaxConns:        10,
                IdleTimeout:     time.Second * 10,
                PoolWaitTimeout: time.Second * 3,
                Auth: smtp.PlainAuth("",
                        os.Getenv("SMTP_USERNAME"),
                        os.Getenv("SMTP_PASSWORD"),
                        os.Getenv("SMTP_HOST")),
                TLSConfig: &tls.Config{ServerName: os.Getenv("SMTP_HOST")},
        })

There seems to be some race condition going on possibly where a connection gets used by a different send request and I wonder if this explains also https://github.com/knadh/listmonk/issues/300 (although I am not using listmonk, only smtppool).
I only send to only one address, but there are many send requests coming in in parallel sometimes.

But I see also that there was a commit done - https://github.com/knadh/smtppool/commit/6f93552458dfbeeb5b7d1b43899eac1970260e68
, which I am not using I think. Perhaps that is the fix actually and perhaps I should just upgrade

Yep, this issue was fixed in the last release. Please upgrade.


v1beta2 changes

This issue is to track API changes that the project wants to make as part of an API bump from v1beta1 to v1beta2.

[ ] Introduce a KThreesControlPlaneMachineTemplate kind that will contain the existing InfrastructureRef  & NodeDrainTimeout and will additionally introduce ObjectMeta (which will require a converstion from the change done in #59 )

Thanks @richardcase. We should probably also do an audit of k3s flags that are missing and make sure v1beta2 considers them in its design.

Sounds good to me.
I'll also check what we have added to the RKE2 provider to see if there is anything we add here as well.

I think https://github.com/cluster-api-provider-k3s/cluster-api-k3s/issues/63 is part of the consideration for this version change (just linking them together).

link https://github.com/cluster-api-provider-k3s/cluster-api-k3s/issues/73
Need add machineSpec properties nodeDeletionTimeout in KThreesControlPlaneMachineTemplate
Better add nodeVolumeDetachTimeout as well in case we need it in future.

link #73
Need add machineSpec properties nodeDeletionTimeout in KThreesControlPlaneMachineTemplate
Better add nodeVolumeDetachTimeout as well in case we need it in future.

Seems that we do not have these fields yet, should we also add them?


Improved search variable name for selects

Per this discussion, this PR improves the default search string variable for the Form Select Components. Previously, the variable had to be $query, which could sometimes be confusing when the Laravel Query builder was also used. This PR allows either $search or $query to be used, and updates the docs to default to $search.
I also changed the variable name in a few other related methods for the sake of consistency.

I know I said that I like $search the other day, I just checked in the codebase for other instances to make sure we don't miss any, and I saw that we use $searchQuery in quite a few places.
Problem is, if we changed $searchQuery to $search in those places, some of those changes would break existing apps (as methods could be overridden, like getGlobalSearchResults(string $searchQuery) on the resource to implement Laravel Scout).
So we either make it $search in some places and $searchQuery in others, or we use $searchQuery everywhere. Thoughts? I'm not expecting you to make this change, you've done loads of work already and I told you specifically to use $search the other day.

@danharrin I say we use $searchQuery and put it on our list of breaking changes to make in the future.

That certainly makes sense. I have updated the PR to reflect $searchQuery instead. I do think it makes sense as a future breaking change though, since the variable name implies it's the actual query of the search, rather than the text being searched for.

Thanks :)


Instructions for configuring AIY Vision HAT on Raspbian

After going through the aiyprojects branch, I did not find clear documentation to setup the Vision HAT with Raspbian.
Could someone plese point to documentation in this regard?

@anilmaddala Could you please clarify what kind of instruction you are looking for? We have all setup instructions for VisionKit at https://aiyprojects.withgoogle.com/vision right now.

Please check the latest version of HACKING.md.


code-signed builds and auto-update

https://electronjs.org/docs/api/auto-updater

opt-in
display feedback when update is available/downloading
"update downloaded. restart now?" popup

now that GitHub Actions builds releases, this would be particularly cool since you'd be able to deploy updates to people's apps by pushing a git tag.

this requires that builds are code-signed. maybe someone can help with that


Add Copy Fixes to Spanish per requested typos

Description
Fix spanish copy per feedback from denisse https://docs.google.com/spreadsheets/d/1_-UQLvUE5QYEsv2jXo2Z0yW59dFZXa8sUQ1A5TrxA-U/edit?pli=1#gid=0
Other changes
n/a
Tested
not tested
Related issues

Fixes https://github.com/celo-org/celo-monorepo/issues/3711

Backwards compatibility
Brief explanation of why these changes are/are not backwards compatible.

if @martinvol or another Spanish speaker in EU is able to take a quick look, would be super appreciated 🙏

@jeanregisser , @nityas  i dont have access of provided docs: https://docs.google.com/spreadsheets/d/1_-UQLvUE5QYEsv2jXo2Z0yW59dFZXa8sUQ1A5TrxA-U/edit?pli=1#gid=0
However, i have check major screen of app in Espanol (America Latina) and it shown translate for me
can you please give access so i can verify and give update here.


Feat/36 blogs page

Descriptions

refactored MemberCard component.
completed blog page with testing

Link to Vercel preview: https://website-git-feat-36-blogs-page-taodemy.vercel.app/blog
Link to Zenhub: https://app.zenhub.com/workspaces/taodemy-63c3dec267d0df73ca6087cb/issues/gh/taodemy/website/36
Link to UI design (if possible): https://www.figma.com/file/q2ZHM8s0LcNxz3otGFLDzO/Website?node-id=0%3A1&t=kWkf0CRDhQoT32Nc-0

Provide screenshots or videos that the function is working.

Provide screenshots of no warning, or error in the console.

[x] All unit tests passing and coverage of testing is more than 90% unless special needs.
[x] No merge conflict with the main branch, make sure your code is up to date with main.
[x] Check PR title is aligned with your ticket.
[x] Check your app will run without crashes.
[x] Check if there are hard-coded values.
[x] No //eslint-disable-next-line no-unused-vars, unless otherwise specified.
[x] Check you are using camelCase && PascalCase correctly.
[x] Remove unused comments.

All of the files inside of general/Blog, they do not need inside of a general folder. Also need to care about naming conventions.
Think about components/blog/Blogxxx.tsx


[Feature Request] Add navigator outside component

What problem does this feature solve?
I recently converted to vue2.7 and vite.
I imported the existing router object and used it outside the component, but I can't use it anymore because of the circular reference problem. It would be nice to create a function that can be routed outside the component. like react-router
What does the proposed API look like?
// axios
import { navigate } from 'vue-router'

axios.interceptors.response.use((res) => {
    navigate(path);
})

You need to solve your circular reference. It's simply not possible to create such API because it depends on the router instance created with new VueRouter().


add metadata information

Improve descriptions and comments in the reconstruction script
Add ComplementaryData folder for all metadata files that are either required for input or generated as output

@edkerk I'd like to keep the line with date information "% DATE CREATED: 2018-01-08", because it is an important time stamp.


xml package version error

Because excel >=1.0.4 <2.0.0-null-safety depends on xml ^4.1.0 and pdf 3.7.1 depends on xml ^5.1.0, excel >=1.0.4 <2.0.0-null-safety is incompatible with pdf 3.7.1.
And because no versions of pdf match >3.7.1 <4.0.0, excel >=1.0.4 <2.0.0-null-safety is incompatible with pdf ^3.7.1.
So, because oms depend on both pdf ^3.7.1 and excel ^1.1.5, version solving failed.
pub get failed (1; So, because oms depend on both pdf ^3.7.1 and excel ^1.1.5, version solving failed.)
Kindly upgrade the XML version in a package so that people can use the latest one thank you.

You can ref to version 2.0.0 -null-safety-3. It works for me.


Description cascade

A couple more fields are available: vote_title, vote_question_text, and amendment_author. They could go right before description, perhaps. This will help for recent congresses in House and Senate votes that may have them.

Added these to the waterfall, still doesn't help link amendments to bills but is much better I think. Closing for now.

This didn't get added to the waterfall for the member vote list.

That is what that last commit does.

I swear when I checked earlier it wasn't in the waterfall somewhere.

Can we close this or am I missing something?


Add option to show the count of selected items, not items themselves inside input [suggestion]

Hi,
I have a project, where I have a rather limited space for all filters. One option that I would love this plugin to have is ability to show only the count of selected items inside input, instead of showing selected items themselves.
So now when you select an item, it is added into input with little "X" to remove it. Having an option to select 5 or more items, the input itself is starting to grow in width and height. When dealing with tight spaces, it would be nice to have that input limited to the width and instead show something like "5 of 10 items selected".
Also maybe would be nice to show checkboxes next to dropdown items, but that is not necessary.

Any way to achieve this behavior using adapters maybe?
https://developer.snapappointments.com/bootstrap-select/examples/#limit-the-number-of-selections


fix: use session in the example instead of a query param

Overview

Type:

🐛Fix

Problem
The $_GET can be confusing in the viewer auth example. Users assume that they will get a user query parameter on their auth endpoint.
Solution
Using $_SESSION suggests, that they have to read their own user session, and pass back the user identifier in the token

@paukenba I think you meant to push this last commit to a different branch.

thanks, I should have created a separate branch for this fix, but meanwhile I started working on a parallel documentation


Test data as code feature concept

TestNG Version

Note: only the latest version is supported
7.5.0

The point of this concept is to write test data files as code on kotlin
(or any other language). This allows to put dynamic data
(i.e. generated on each launch, for example, today's date or random string)
into data files.
The problem:
I was involved in a project, where test data was stored in yaml files.
They parsed those yaml files, and used it in a tests.
The problem was, they needed dynamic values,
like today's date, or random sequence of characters.
This data cannot be places in yaml testdata files by default.
So they used custom markup language, to define, for example random alphabetic sequence
of length 6. This custom markup language was processed by custom yaml deserializer,
to replace markup with calculated values. In this case, why can't we write test data
in code?
How test data as kotlin code may look like?
Kotlin code may seem like declarative language, when using named constuctors
for example:
data class Person(
    val name: String,
    val age: Int,
    val profession: String
)

val person = Person(
    name = "Cris",
    age = 18,
    profession = "student"
)

The problem with this approach is that all data-generation code, and consequently
data(because it's essentially hardcoded) remains in RAM, and may lead to OOM.
We may overcome this with custom classloader, for example:
data class Person(
    val name: String,
    val age: Int,
    val profession: String
)

val person = getPerson()

fun getPerson() {
    /**
     * This custom classloader is used to load code that provides data
     * When loaded code executed, and method returned, classloader, and all
     * classes, loaded by it, will be cleared by GC.
     * */
    val dataClassLoader = DataClassLoader()
    val providerClass = dataClassLoader.loadClass("PersonProvider")
    val providerMethod = providerClass.declaredMethod("provide")
    val person = providerMethod.invoke(
        providerClass.getDeclaredConstructor().newInstance()
    )

    return person
}

class PersonProvider {
    fun provide() = Person(
        name = "Cris",
        age = 18,
        profession = "student"
    )
}

How a test class may look like?
class TestClass {
    @Test(dataAsCode = [["PersonProvider#provide"]])
    fun test(person: Person) {

    }
}

What do you guys think? Would you accept such feature in testNG?

Sounds like a .kts file would be a better fit than a .kt but either way, I agree it sounds useful.

I don't catch the difference between data as code and data provider using code.
It sounds to me like a SPI on top of the data provider logic.
Something like https://junit.org/junit5/docs/current/user-guide/#writing-tests-parameterized-tests
Am I right?

@cbeust  , .kts files would require a kotlin embedded compiler and script runtime dependencies in tests. It's consume a lot of RAM, and some time to load, which may slow down single test run, when debugging.
@juherr Data provider's code will never be unloaded from heap, so it's not really scalable to put a data generation code there, because it will sit in RAM for entire test run and may eventually lead to OOM, As for junit implementation, I don't know if they unload their method providers, after use. Will look at it later.
Maybe we may make dynamically load / unload dataproviders, when it's possible, i.e. when dataprovider is in different class?

Ok. I'm just a bit surprised because our known memory problem is on the test results.
If we are going to the way you say, is there any reason to not implement the current data provider feature over it?
If you plan to try something, please share your results here.

Yes, if we do dataproviders unloadable, test data may be written as a data provider in a separate class, loaded on demand, and unloaded after data is generated.
I never met teems, coding any sophisticated data in dataproviders. I think there was some reasons  for that:

developers are tought that hardcoding is bad, and that you need to store data in files.
java code seem like really imperative and defining data in it is not pretty.
memory consumption - dataproviders code will stay in memory all test run

But when memory consumption will not threat scalability, and with scripting language usage it makes sense for me.

@dsankouski - I am still not sure as to what problem are we trying to solve here. Can you please help me understand that ?
I ask this because, TestNG always remembers the parameters that were passed to a @Test method or to a constructor (in the case of @Factory methods). So irrespective of whether you attempt at getting rid of their references from data provider classes (The kotlin sample didn't make it clear to me as to how are you going to trigger a GC by removing references of the data provider parameters), GC is still not going to happen, because as @juherr mentioned TestNG still has references to the parameters via the ITestResult object.
So can you please break down the problem statement into a bit more elaborate details so that I can understand the problem statement.

@krmahadevan
Suppose, you're decided to use
data provider, like in example:
import org.testng.annotations.DataProvider;

class DataProviders {
    @DataProvider
    public static Object[][] dp() {
        return new Object[][] {
                {"Mike", 34, "student"},
                {"Mike", 23, "driver"},
                {"Paul", 20, "director"}
        };
    }
}

class Test {
    @Test(dataprovider = "dp", dataproviderClass = DataProviders.class)
    public void test(String name, int age, String prof) {
        // test code
    }
}

All data in DataProviders class will be placed in constant pool $4.4 upon compilation
When loading DataProviders.class $5.3, it's internal binary representation
will be created in the method area $2.5.4.
This binary representation contains per-class runtime constant pool $2.5.5,
which contains all the data we need for test.
So our code will basically "copy" data from runtime constant pool to Object[][] instance:
$4.4: Java Virtual Machine instructions do not rely on the run-time layout of classes, interfaces, class instances, or arrays. Instead, instructions refer to symbolic information in the constant_pool table
When dp method is invoked, Object[][] instance is created in
heap area, thus duplicating data, contained in method area.
With current DP implementation we end up with data being duplicated
in heap and in method area
Since we only need data itself, i.e. Object[][] instance,
we may load this class on demand with custom classloader.

Few words about interned strings:
Though there's string literal pool in java,
it's located in heap, and represent string objects.
String literals in class contant pool are also "interned"
in a sense, that unique literal contained only once in a
class file, and bytecode instructions like LDC "Mike"
refer to string index in constant pool.
See also $4.4.3
$4.4.7
Note, $2.5.4 states: Although the method area is logically part of the heap, simple implementations may choose not to either garbage collect or compact it. This specification does not mandate the location of the method area or the policies used to manage compiled code
This means, that method area garbage collecting is implementation
dependent.

@dsankouski - Wow that's an amazing insight into the internals of the JVM. Thank you for taking the time to share that. I will go through it in detail and come back.
In the meantime if I understand your requirement, you are basically proposing a way wherein I can basically have the following for a data driven test

The test should be able to specify a class loader powered data provider class which TestNG would basically load on-demand.
After TestNG has finished loading the class via the class loader and then reading the data via the data provider method, TestNG at some point decides to offload the loaded class via some mechanism (I don't know what that mechanism is yet)

Is my understanding correct ?
If it's correct, then this is a very specialised usecase for data providers, because usually people build data providers that feed off an external data source (xml|xls|json|yaml|db|csv) and so there's no need for loading/unloading one class because it wouldn't have any fields that are constants as in your example.
PS: My knowledge on the JVM internals is very primitive, so please bear with me if my questions sound naive.. Excited to understand this even more from a personal learning perspective :)

@krmahadevan
1 - correct
2 - correct, the easiest way to offload a dataprovider would be to rely on GC, I think. When there's no links to user's classloader, and classes loaded by it, GC may collect that, depending on implementation (Although JVM spec doesn't guarantee that, $2.5.4)
So, what I'm thinking of, is to add dataProviderClass string parameter to @Test annotation, and if that's not empty, load dataprovider via custom classloader, when resolving it's data.
This indeed may be specialized case. Because, when we're got dataProviderClass param as .class variable in @Test annotation, mentioned class will be loaded automatically upon test class loading. Class should be specified as String to be able to load it dynamically.

@dsankouski

So, what I'm thinking of, is to add dataProviderClass string parameter to @Test annotation, and if that's not empty, load dataprovider via custom classloader, when resolving it's data.

Yes. It has to be a string parameter so that we can use reflection backed by a custom class loader to be used to load up the class. Then again, I think you would also need to consider providing a means to inject a custom class loader itself. So would it basically mean that we would now need to add up 2 string parameters (1 which specifies the data provider class and the other which specifies the custom class loader that we would like to be used.). I say this because if we end up specifying the classloader as a class parameter then we are back to square one.