与其他第三方插件冲突问题.

ע: C:\Users\lupmi\AppData\Roaming\Pub\Cache\hosted\pub.flutter-io.cn\connectivity-0.4.3+2\android\src\main\java\io\flutter\plugins\connectivity\ConnectivityPlugin.javaʹ�û򸲸����ѹ�ʱ�� API��
ע: �й���ϸ��Ϣ, ��ʹ�� -Xlint:deprecation ���±��롣
ע: E:\CodeManage\Flutter\fake_tencent-master\android\src\main\java\io\github\v7lin\faketencent\FakeTencentPlugin.javaʹ�û򸲸����ѹ�ʱ�� API��
ע: �й���ϸ��Ϣ, ��ʹ�� -Xlint:deprecation ���±��롣
ע: ĳЩ�����ļ�ʹ�û򸲸����ѹ�ʱ�� API��
ע: �й���ϸ��Ϣ, ��ʹ�� -Xlint:deprecation ���±��롣
ע: C:\Users\lupmi\AppData\Roaming\Pub\Cache\hosted\pub.flutter-io.cn\flutter_webview_plugin-0.3.5\android\src\main\java\com\flutter_webview_plugin\WebviewManager.javaʹ����δ�����򲻰�ȫ�Ĳ�����
ע: �й���ϸ��Ϣ, ��ʹ�� -Xlint:unchecked ���±��롣
ע: C:\Users\lupmi\AppData\Roaming\Pub\Cache\hosted\pub.flutter-io.cn\package_info-0.4.0+4\android\src\main\java\io\flutter\plugins\packageinfo\PackageInfoPlugin.javaʹ�û򸲸����ѹ�ʱ�� API��
ע: �й���ϸ��Ϣ, ��ʹ�� -Xlint:deprecation ���±��롣
D8: Program type already present: android.support.v4.media.MediaBrowserCompat$ConnectionCallback$ConnectionCallbackInternal
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:transformDexArchiveWithExternalLibsDexMergerForDebug'.

com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives: E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\4.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\5.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\6.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\7.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\8.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\9.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\13.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\14.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\15.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\16.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\17.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\18.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\19.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\20.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\21.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\22.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\23.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\24.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\25.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\26.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\27.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\28.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\29.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\30.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\31.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\32.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\33.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\34.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\35.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\36.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\37.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\38.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\39.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\40.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\41.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\42.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\43.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\44.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\45.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\46.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\47.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\48.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\49.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\50.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\51.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\52.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\53.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\54.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\55.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\56.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\57.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\62.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\63.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\64.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\65.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\66.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\67.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\68.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\69.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\70.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\71.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\72.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\73.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\74.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\78.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\79.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\80.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\81.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\82.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\83.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\84.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\85.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\86.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\87.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\88.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\89.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\90.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\91.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\92.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\93.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\94.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\95.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\96.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\97.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\98.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\99.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\100.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\101.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\102.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\103.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\104.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\105.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\106.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\107.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\108.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\109.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\110.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\111.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\112.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\113.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\114.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\115.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\116.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\117.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\118.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\119.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\120.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\121.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\122.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\123.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\125.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\126.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\128.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\129.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\130.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\131.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\132.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\134.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\135.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\136.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\137.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\138.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\139.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\141.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\142.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\143.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\144.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\145.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\146.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\147.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\148.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\150.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\151.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\152.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\153.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\154.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\155.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\156.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\158.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\159.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\160.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\161.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\164.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\165.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\166.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\167.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\168.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\169.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\170.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\171.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\172.jar, E:\CodeManage\Flutter\fake_tencent-master\example\build\app\intermediates\transforms\dexBuilder\debug\173.jar
Learn how to resolve the issue at https://developer.android.com/studio/build/dependencies#duplicate_classes.
Program type already present: android.support.v4.media.MediaBrowserCompat$ConnectionCallback$ConnectionCallbackInternal

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 23s

The Gradle failure may have been because of AndroidX incompatibilities in this Flutter app.
See https://goo.gl/CP92wY for more information on the problem and how to fix it.

Finished with error: Gradle task assembleDebug failed with exit code 1
经测试还是这三个插件,请老大指导下如果不替换,如何解决??
flutter_webview_plugin: ^0.3.0+2
flutter_inappbrowser: ^1.2.1
image_picker: ^0.5.0+3

-_-!!! 在我的 example 上加上那三个插件编译通过了，example升级 AndroidX编译也通过了 ... 你要不要上一个 Demo 我好排查问题啊

由于你引入的第三方插件需要将工程升级到AndroidX(AndroidX compatibility)，所以你直接在我这主分支上加插件是不对的，你可以到 androidx-compatibility 分支体验一下

感谢老大,我拉取你得androidx-compatibility测试了,是能运行的,我基础不太好,请问能不能帮我解答下,在我没引入fake_tencent 时,我引入的那第三方插件没有兼容AndroidX也能运行???

具体问题具体分析，不能一概而论

非常感谢,问题解决!

非常感谢,问题解决!
老哥~怎么解决的求指导~


What if we do not predict s and h

I wonder if the model can fit a polyline x = a * y**3 + b * y ** 2 + c * y + d without fitting offset s and horizontal line h, since the problem seems to be poor-formed.
Intuitively, at  point  y = 100pix,  the equation would be x = a * 1000000 + b * 10000 + c * 100 + d.  A tiny perturbation on a would introduce a dramatic change in  x, which makes it too hard to learn the other parameters b, c, d, especially the offset parameter d.
So what are the important points  that make the model successfully fit a polyline?

I am not sure that I follow. How would you know the limits of the polyline?


Added events to Invoice and Credit Memo on insert line and before output

It would be great, if we can manipulate the file, during creation. As well as being able to send the generated files to a webservice instead of just downloading it.

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

I'm missing a not

Why is it you want to skip lines?
Will this give a problem with totals and more?
I think we should mirror to solution on all types.
Please also add test at the end of the review

Why is it you want to skip lines?
Will this give a problem with totals and more?

I'm not interested in skipping lines completely, I would like to let extensions generate lines on their own, with other XML elements than the implemented. Therefore I've included the IsHandled, like described in the Handled-pattern.

Why is it you want to skip lines?
Will this give a problem with totals and more?
I'm not interested in skipping lines completely, I would like to let extensions generate lines on their own, with other XML elements than the implemented. Therefore I've included the IsHandled, like described in the  @Handled-pattern.
@RasmusTidselbak
OK so it is more a substitution.
Thanks

I just realised that the app will fail, if the file is not exported.
I'm working on a solution.

Please also add test at the end of the review
@MarcHansenMicrosoft
How do you wan't the tests to be created. Since I can't hook into events when both the test and the app is in the same project.

It should not be a problem adding event subscribers in the same project but remember to make then manual binding.
If this is not working please tell me we might log a bug on it then.

What happend to the test?

What happend to the test?

I'm working on it.
Remember that I'm working on this in my spare time.

Sorry did not wan't to rush on you. I was just not sure if you still had issues with adding test subscribers.

Hi Marc When you are it making changes
OIOUBL Extension Exports the XML to Server File and after that based on the settings it either downloads / sends the XML File to Document Exchange Service.
Creating a File on the Server is not allowed in the Cloud Version, How are you planning to enhance this extension (Replace File to Streams)? As we are working on an Integration we cannot use files, we are replacing them with Streams. So we need blob fields instead of File Path in few functions, so that it can use the Standard Flow. Can you please let us know your plans on this? Thanks

No current plans to change OIOUBL file handling.
It works in it's current version as the extension is internal.
It could be that @RasmusTidselbak would change the eventing to send a blob or stream instead.

The pull request has been stalled and still requires some work.
@RasmusTidselbak if you want to and have the time you are welcome to reopen and continue.


Trainer + game crashes with new update to change number 24021053 on 06/18/2024

by the way, thank you for your time spent on this project. Being bad at this game is killing me ;)

It looks like the game has been updated. I will check on it when I get home. Thank you for bringing this to my attention.

The trainer has been fixed and can be downloaded from this link. You can also compile it from the source yourself if you prefer. Thank you for your patience.


4525 add new what is your immigration status page

Context
Amendments to the right to work flow.
Feature flag and redundant logic cleanup will be done in a follow up PR.
Changes proposed in this pull request

Surface immigration status page and remove the expandable text box from the original page

Remove immigration route views, controller, routes and form

Use right_to_work_or_study column instead

Use right_to_work_or_study_details column instead

Use right_to_work_or_study_details column instead
Guidance to review

Do we need a RC check?

Edit Nationality and select Citizen of a different country

Choose Yes to the next question.

Notice how the text field no longer expands, but instead you are taken to a new page.

Play around, look for bugs, leave comments.

Link to Trello card
https://trello.com/c/9qNLUUww/4525-add-new-what-is-your-immigration-status-page
https://trello.com/c/oUWLYqAJ/4499-remove-question-from-right-to-work-flow

Minor bug with the error state for "What is your immigration status?"
Steps to reproduce:
1. Select 'French' as a nationality

2. Answer 'Yes' to 'Do you already have the right to work or study in the UK?'

3. Press 'Save and continue' without selecting an option

Issues:
1. Error message is "can't be blank" - should be "Select your immigration status" or similar.

2. The radios should have a red border to the left of all them, and should repeat the error message beneath the question / h1

3. The link in the error summary should focus the first radio option

4. "Other" is selected - no radios should be selected.

Screenshot:

Thanks @frankieroberto, have fixed that now. Ready for you to take another look whenever you are free 😄

One other thing to check (but I'm not sure exactly how): can we check how this appears on Manage, and in the API? If the user selects one of the radio options (eg "EU Settled Status") then that should appear in Manage, but if they select "Other" then the contents of the text box should appear in Manage (rather than "Other").  Same with the API.


Bump is stripping out build info from tag

Hey,
Semver describes the ability to add addition of prerelease and build metadata at the end of a version string. Currently if I pass 1.0.6-1+build-623 to the version option it will only output 1.0.6-1.
Im hoping to use this to output to a constants file for a angular app, allowing me to log errors against a build version in the running app with Sentry. We deploy new builds without updating the version for refactors of the code. We only use patch for bugs.
Not sure if its would help with the internals of gulp bump but Im using semver-utils to parse the string and increment before passing it to bump.
Thanks for the great lib. Currently using it for tagging builds and its working great. 👍

You need to specify the version type as pre release and add the preid as the metadata
{
  type: 'prerelease',
  preid: '1+build-' + metaData
}

Ah ok. Will this also mean that the build metadata will be reset when I do anything other than  a prerelease bump?

Yes as it is creating a new version with the type set to minor, major, etc

Ok, Ill prob have to manually handle updating the strings to keep the build version between versions. :disappointed:
Thanks for your help though! I appreciate it. :neckbeard:


SqlAg: 'EndpointHostName' should be 'ComputerName' but is 'ComputerName.FQDN'

Details of the scenario you tried and the problem that is occurring
Ag is configured correctly but DSC test method fails.
$Params = @{
Ensure               = 'Present'
Name                 = $SqlAgName
ServerName           = $env:COMPUTERNAME
InstanceName         = $SqlInstanceName
PsDscRunAsCredential = $SqlCred
}
Invoke-DscResource -ModuleName SqlServerDsc -Name SqlAG -Property $Params -Method Test
Verbose logs showing the problem
[[SqlAG]DirectResourceAccess] 2019-04-30_14-25-53: 'EndpointHostName' should be 'SRV01' but is 'SRV01.DC.com'
Suggested solution to the issue
The DSC configuration that is used to reproduce the issue (as detailed as possible)
$Params = @{
        Ensure               = 'Present'
        Name                 = $SqlAgName
        ServerName           = $env:COMPUTERNAME
        InstanceName         = $SqlInstanceName
        PsDscRunAsCredential = $SqlCred
    }
Invoke-DscResource -ModuleName SqlServerDsc -Name SqlAG -Property $Params -Method Test

SQL Server edition and version the target node is running
Microsoft SQL Server 2014 (SP3-CU3) (KB4491539) - 12.0.6259.0 (X64)   Apr  1 2019 22:19:54   Copyright (c) Microsoft Corporation  Enterprise Edition (64-bit) on Windows NT 6.3  (Build 9600: ) (Hypervisor)
SQL Server PowerShell modules present on the target node
Name         Version    Path

SqlServer    21.1.18102 C:\Program Files\WindowsPowerShell\Modules\SqlServer\SqlServer.psd1
SQLASCMDLETS 1.0        C:\Program Files (x86)\Microsoft SQL Server\120\Tools\PowerShell\Modules\SQLASCMDLETS\SQLASCMDLETS.psd1
SQLPS        1.0        C:\Program Files (x86)\Microsoft SQL Server\120\Tools\PowerShell\Modules\SQLPS\SQLPS.psd1
The operating system the target node is running
OsName               : Microsoft Windows Server 2012 R2 Standard
OsOperatingSystemSKU : StandardServerEdition
OsArchitecture       : 64-bit
WindowsBuildLabEx    : 9600.19321.amd64fre.winblue_ltsb_escrow.190313-1806
OsLanguage           : en-US
OsMuiLanguages       : {en-US}
Version and build of PowerShell the target node is running
Name                           Value

PSVersion                      5.1.14409.1018
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14409.1018
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
Version of the DSC module that was used ('dev' if using current dev branch)
Name         Version  Path

SqlServerDsc <IP_ADDRESS> C:\Program Files\WindowsPowerShell\Modules\SqlServerDsc\SqlServerDsc.psd1

I think it should not evaluate that property if it is not part of the configuration.

This can be closed. The issue is due to having an EndpointHostName that was not configured by SqlServerDsc. I can pass the TEST method by passing parameter $EndpointHostName.


Modem Control Library

Do you think it feasible to create a cross platform modem control library?

That would probably be a good idea. However, some of the modems (i.e. VARA) are definitely not cross platform. I'm not sure how such a library could handle those.


Decimal value is not stored in Postgresql

Laravel Version: 5.6.12
PHP Version: 7.2.3
Database Driver & Version: (pgsql) Postgresql 10.3

Description:
Using Laravel 5.6 and Postgresql 10.3 I am not able to store a decimal value through Laravel. I can however store the value directly through SQL with PgAdmin.
Steps To Reproduce:
The migration file:
        Schema::create('downloads', function (Blueprint $table) {
            $table->decimal('download_time', 4, 3)->nullable(true);
        });

As expected the column is created as download_time with the numeric(4,3) type.
Tinker does not give any error when inserting / updating the column download_time with value 0.611. When I check my table the value is not updated.
            Download::find(1)->update([
              'download_time' => 0.611
            ]);

While writing SQL in PgAdmin the value is stored correctly:
    update downloads
    set download_time = 0.611
    where id = 1

Did you add download_time to Download::$fillable?

@staudenmeir I am going to cry in the corner of the room and hit myself with a stick. Thank you.


[webview_flutter] In release mode, the NavigationDelegate event is not called.

I am using webview_flutter 4.0.1 version.
The sample code below works fine in debug mode.
But in release mode the NavigaionDelegate event is not called.
I don't know why the problem only occurs in release mode.
I am wondering what could be causing this problem.

Code
late WebViewController _webViewController;

@override
void initState() {
  super.initState();

  ...

  final WebViewController controller =
        WebViewController.fromPlatformCreationParams(params);

  controller
    ..setJavaScriptMode(JavaScriptMode.unrestricted)
    ..setBackgroundColor(const Color(0x00000000))
    ..setNavigationDelegate(
      NavigationDelegate(
        onProgress: (int progress) { <-- not fire
          // Update loading bar.
        },
        onPageStarted: (String url) {}, <-- not fire
        onPageFinished: (String url) {}, <-- not fire
        onWebResourceError: (WebResourceError error) {}, <-- not fire
        onNavigationRequest: (NavigationRequest request) { <-- not fire
          if (request.url.startsWith('https://www.youtube.com/')) {
            return NavigationDecision.prevent;
          }
          return NavigationDecision.navigate;
        },
      ),
    );

  _webViewController = controller;

  WidgetsBinding.instance.addPostFrameCallback((_) async {
     _webViewController.loadRequest(Uri.parse('https://flutter.dev'));
  });
}

Flutter Doctor
[✓] Flutter (Channel stable, 3.3.0, on macOS 13.1 22C65 darwin-x64, locale ko-KR)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.3)
[✓] IntelliJ IDEA Ultimate Edition (version 2022.3.1)
[✓] VS Code (version 1.74.2)
[✓] Connected device (3 available)
[✓] HTTP Host Availability

Hi @JosephNK, what platform(s) are you experiencing this issue on?
Your code sample is not complete, please provide a complete minimal reproducible code sample so we can investigate this.
Thank you

@danagbemava-nc  Only Android is currently being tested, iOS has not been confirmed.
As you can see in the screenshot below, the event is not called in release mode.
Sample Source
https://github.com/JosephNK/flutter_webview
Debug Mode

Release Mode

I have same issue on android that occurs only with release mode.
I can confirm that NavigationDelegate works correctly in both debug and release mode on iOS.

Hi @JosephNK, you are missing the android permission in your AndroidManifest.xml.
The debug manifest already includes the Internet permission because it is required for debugging but you have to manually add it in your main AndroidManifest.xml

@danagbemava-nc Even if  value is entered in AndroidManifest.xml, the event does not work in release mode.
For reference, I added it to github and committed it.

Hi @JosephNK, the issue isn't actually with the NavigationDelegate, it looks like there was an issue in the initialization of the webview. I got the error below on the stable channel (I used the logcat in android studio to check the error). However, I cannot seem to reproduce the issue on the master channel.
Can you switch to the master channel to see if you are still able to reproduce the error over there as well?
You can switch to the master channel by running the commands below
flutter channel master
flutter upgrade

If you still reproduce this on the master channel, kindly provide the flutter doctor -v output of the master channel.
Thank you
[ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: PlatformException(NullPointerException, java.lang.NullPointerException: Attempt to invoke virtual method 'void android.webkit.WebView.loadUrl(java.lang.String, java.util.Map)' on a null object reference, Cause: null, Stacktrace: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.webkit.WebView.loadUrl(java.lang.String, java.util.Map)' on a null object reference
                                                                                at io.flutter.plugins.webviewflutter.k3.w(Unknown Source:12)
                                                                                at io.flutter.plugins.webviewflutter.c2.U(:1)
                                                                                at io.flutter.plugins.webviewflutter.c2.j(:1)
                                                                                at io.flutter.plugins.webviewflutter.b2.a(Unknown Source:2)
                                                                                at c2.a$b.a(Unknown Source:17)
                                                                                at p1.c.j(Unknown Source:18)
                                                                                at p1.c.k(Unknown Source:20)
                                                                                at p1.c.g(Unknown Source:0)
                                                                                at p1.b.run(Unknown Source:12)
                                                                                at android.os.Handler.handleCallback(Handler.java:938)
                                                                                at android.os.Handler.dispatchMessage(Handler.java:99)
                                                                                at android.os.Looper.loopOnce(Looper.java:210)
                                                                                at android.os.Looper.loop(Looper.java:299)
                                                                                at android.app.ActivityThread.main(ActivityThread.java:8319)
                                                                                at java.lang.reflect.Method.invoke(Native Method)
                                                                                at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:556)
                                                                                at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1038)
                                                                                , null)
                                                                                #0      WebViewHostApi.loadUrl (package:webview_flutter_android/src/android_webview.pigeon.dart:377)
                                                                                <asynchronous suspension>

@JosephNK did u find the solution? have the same problem

@MaksimZdanchuk I haven't found it yet 🧐

@JosephNK I ve just tried to downgrade the web_view library to 3.0.4 version and its worked for me)

Same issue here..

@gitoramadhan downgrade the package as i said.

@MaksimZdanchuk Downgrading doesn't seem like a good idea. The reason for solving this and using webview_flutter 4.0.1 is to apply the corrected code for the following problems.
#116954
#104889

Hi @JosephNK, can you move the _webViewController.loadRequest(Uri.parse('https://flutter.dev')); out of the WidgetsBindings.instance.addPostFrameCallback callback and try again to see if it works for you?
It worked for me when I commented out WidgetsBindings.instance.addPostFrameCallback

Hello @danagbemava-nc I need to use WidgetsBindings.instance.addPostFrameCallback because I need to use WidgetsBindings.instance.addPostFrameCallback to handle loadRequest in my current project.
Please note.

Hi @JosephNK, can you move the _webViewController.loadRequest(Uri.parse('https://flutter.dev')); out of the WidgetsBindings.instance.addPostFrameCallback callback and try again to see if it works for you?
It worked for me when I commented out WidgetsBindings.instance.addPostFrameCallback

Were you using stable channel? I still get the same issue

@MaksimZdanchuk Downgrading doesn't seem like a good idea. The reason for solving this and using webview_flutter 4.0.1 is to apply the corrected code for the following problems. #116954, #104889

Until the issue has been resolved, I will have to downgrade.. until the is a suitable fix.

@JosephNK @MaksimZdanchuk  Have you tried this: https://github.com/Earlybyte/aad_oauth/issues/196 ." initialize the NavigationDelegate as it's own variable before creating the WebViewController"
I've applied this and it does work

@danagbemava-nc @gitoramadhan @joshmossas I'm wondering what the difference is between release mode and debug mode for this issue.

Were you using stable channel? I still get the same issue
@gitoramadhan, yes I was on the stable channel. I just tested again and it worked just fine.

Hello @danagbemava-nc I need to use WidgetsBindings.instance.addPostFrameCallback because I need to use WidgetsBindings.instance.addPostFrameCallback to handle loadRequest in my current project.
Please note.

@JosephNK, I'm curious, why exactly do you need to use the WidgetsBindings to handle the loadRequest?

I'm wondering what the difference is between release mode and debug mode for this issue.

It might be a race condition in the initialization of the controller
@JosephNK  Does the workaround in https://github.com/flutter/flutter/issues/108801#issuecomment-1367490174 work for you?

Hello @danagbemava-nc Even if you don't use WidgetsBindings, shouldn't you be able to do a loadRequest on the button click event later? The reason loadRequest is being called in my project's WidgetsBindings is because initState needs to wait through loadRequest and fetch certain data.
I'm curious here. Does it matter if WidgetsBindings are used or not?
I guess I'll have to find another reason to use WidgetsBindings or not.

Does the workaround in https://github.com/flutter/flutter/issues/108801#issuecomment-1367490174 work for you?
@danagbemava-nc I checked that part. I also confirmed that it works.
By the way, I wonder how the debug mode and release mode behave differently in the same code. For that code, if I set NavigationDelegate as a global variable, it works in release mode, otherwise it doesn't work. I wonder why this is.

shouldn't you be able to do a loadRequest on the button click event later

Yes, you can do this later with a click event.

I'm curious here. Does it matter if WidgetsBindings are used or not?
I guess I'll have to find another reason to use WidgetsBindings or not.

I'm not sure I fully understand your use case so I can't say definitively whether or not it is necessary.

I wonder how the debug mode and release mode behave differently in the same code

Debug and release use different compilation modes, so that could be a factor. Debug builds generally are not optimized, tree-shaking doesn't take place and symbols are not stripped, which happens in release mode.

if I set NavigationDelegate as a global variable, it works in release mode, otherwise it doesn't work. I wonder why this is.

I'm not entirely sure of the reason for this, it might have to do with how the modes are compiled but don't quote me on that.

Also, it doesn't work on the Stable channel but works on the Master channel.
What are the reasons for these parts?

There could have been some changes to how certain things are handled in the flutter engine or with dart itself. The master branch is usually several commits ahead of stable so it usually has a lot of improvements over the stable branch.
Given that this has been fixed on the master channel (and workarounds exist for this issue on stable), per our triage policy, I'll be closing this issue.
Thank you


Fails to view SQLite databases containing STRICT tables

If I create a STRICT table in a SQLite database:
CREATE TABLE user(id INTEGER, username TEXT) STRICT;

then try to open it with termdbms, I receive the following error:
database disk image is malformed: malformed database schema (user) - near "STRICT": syntax error (11)

I believe this is a limitation of the SQLite driver I'm using. I opted to go with 100% Go for portability reasons, but there's a C driver that is likely more up to date on all the syntax.


More examples

Are there any plans to add examples such as socket communication in the future?

I think is really needed, a lot of scenarios are not covered.

We hear you. One of the big plans we have for 1.5.0 is a proper homepage with better documentation and examples.


[youtube] Extract error messages from HTTPError response

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[X] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[X] Searched the bugtracker for similar pull requests
[X] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[X] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[X] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
Explanation of your pull request in arbitrary form goes here. Please make sure the description explains the purpose and effect of your pull request and is worded well enough to be understood. Provide as much context and examples as possible.
The Innertube API appears to give useful error messages in the response payload for an HTTP Error. So, this PR attempts to extract such error and raise a warning. This might be useful for debugging future issues relating to the API.
The current implementation is to report the error as a non-fatal alert.
Example:
$ yt-dlp --flat-playlist ytsearchall:youtube-dl
[download] Downloading playlist: youtube-dl
[youtube:search] query "youtube-dl" page 1: Downloading API JSON
WARNING: [youtube:search] YouTube said: ERROR - API key not valid. Please pass a valid API key.
WARNING: [youtube:search] HTTP Error 400: Bad Request. Retrying ...
[youtube:search] query "youtube-dl" page 1: Downloading API JSON (retry #1)
WARNING: [youtube:search] YouTube said: ERROR - API key not valid. Please pass a valid API key.
WARNING: [youtube:search] HTTP Error 400: Bad Request. Retrying ...
[youtube:search] query "youtube-dl" page 1: Downloading API JSON (retry #2)
WARNING: [youtube:search] YouTube said: ERROR - API key not valid. Please pass a valid API key.
WARNING: [youtube:search] HTTP Error 400: Bad Request. Retrying ...
[youtube:search] query "youtube-dl" page 1: Downloading API JSON (retry #3)
WARNING: [youtube:search] YouTube said: ERROR - API key not valid. Please pass a valid API key.
ERROR: Unable to download API page: HTTP Error 400: Bad Request (caused by <HTTPError 400: 'Bad Request'>); please report this issue on  https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --verbose flag and include its complete output.
[youtube:search] playlist youtube-dl: Downloading 0 videos
[download] Finished downloading playlist: youtube-dl

TODO:

[ ] Catch possible errors that can arise from reading/seeking the file object
[ ] Test other errors (rate-limit behaviour)?

Catch possible errors that can arise from reading/seeking the file object
Anyone more knowledgeable in the underlying workings know more specifically what sort of errors may arise from this?


Mobile Wallet

Mobile Wallet
Goal: Develop a mobile wallet which is able to sign cfd trading transactions such as place order, rollover and collaborative settlement.
High level task list:
Wallet

[ ] Setup mobile project
[ ] Generate wallet at onboarding (Bip39)
[ ] Push notifications

Taker daemon extensions

[ ] Extend taker daemon api to accept signed cfd transactions for placing an order.
[ ] Disable auto rollover for cfds created from the mobile wallet.
[ ] Extend taker daemon api to accept rollover triggered by the mobile wallet.
[ ] Extend taker daemon api to accept signed cfd transactions for collaborative settlement.

Open Decisions

What framework should be used for the mobile project - react native? (https://reactnative.dev/)
Do we want to build the wallet in typescript (what library to use) or build a native module using neon (https://neon-bindings.com/)? Second option may be hard to cross-compile for all architectures.
The wallet needs to run a background task which is listening for events from the taker daemon, respectively which is monitoring it's own cfds and triggers an action e.g. if it needs to be rolled over. How should we build that part? headless-js? (https://blog.logrocket.com/run-react-native-background-tasks-headless-js/)

What framework should be used for the mobile project - react native? (reactnative.dev)

Most of the team are already familiar with react, so let's go with react native.

Do we want to build the wallet in typescript (what library to use) or build a native module using neon (neon-bindings.com)? Second option may be hard to cross-compile for all architectures.

I propose to go for cross-compilation. Try for iOS and Android but if we have troubles on iOS drop it because it was mentioned it is easier for us to develop for Android by @klochowicz and @da-kami .

The wallet needs to run a background task which is listening for events from the taker daemon, respectively which is monitoring it's own cfds and triggers an action e.g. if it needs to be rolled over. How should we build that part? headless-js? (blog.logrocket.com/run-react-native-background-tasks-headless-js)

Good question, we could build a simple polling process, which polls a backend every now and then (e.g. regular, on a certain action, or a mix of both).

I've got some questions about the choice of react native:

how convenient is to use that with Rust?
do we need to compile to wasm or is the plan to build the whole thing in TS? or is the idea to actually try compiling itchysats with neon as a nodejs library? or are we going for native compilation? This is the biggest unknown for me as for choosing react native.
does react native have it's own component set or are we trying to use chakra there too?

my personal preference for the framework would be flutter (https://docs.flutter.dev/), as this seems as the fastest way to develop a compelling UI and it's straightforward to bind it to Rust (see: https://github.com/fzyzcjy/flutter_rust_bridge).
It can be readily deployed to both iOS and Android and desktop/web as well without any further change. It is also recommended over react native for the faster app development (in both senses of the word 'faster', the dev speed and resulting app is faster).

I've got some questions about react native:
* how convenient is to use that with Rust?

I personally have no experience but I found a blog post about someone building an ethereum wallet with rust and react native which is very close to what we need

* do we need to compile to wasm or is the plan to build the whole thing in TS? or is the idea to actually try compiling itchysats with neon as a nodejs library? or are we going for native compilation? This is the biggest unknown for me as for choosing react native.

I think compiling to native is the preferred way to build for mobile. Particularly if we want to sign 100s of transactions we will appreciate the performance.

* does react native have it's own component set or are we trying to use chakra there too?

Afaik chakra can't be used in react native but we can reuse our components.

my personal preference for the framework would be flutter (docs.flutter.dev), as this seems as the fastest way to develop a compelling UI and it's straightforward to bind it to Rust (see: fzyzcjy/flutter_rust_bridge).
It can be readily deployed to both iOS and Android and desktop/web as well without any further change. It is also recommended over react native for the faster app development (in both senses of the word 'faster', the dev speed and resulting app is faster).

I'm against flutter because it is a

new framework: flutter
a new language: dart

We have no experience with neither.

I've got some questions about react native:
* how convenient is to use that with Rust?

I personally have no experience but I found a blog post about someone building an ethereum wallet with rust and react native which is very close to what we need

that project went only until setup & "Hello World" stage (!), this does not instil much confidence. It also needed to interact with JNI on android,  and suggested creating custom Java bindings yourself.

* do we need to compile to wasm or is the plan to build the whole thing in TS? or is the idea to actually try compiling itchysats with neon as a nodejs library? or are we going for native compilation? This is the biggest unknown for me as for choosing react native.

I think compiling to native is the preferred way to build for mobile. Particularly if we want to sign 100s of transactions we will appreciate the performance.

* does react native have it's own component set or are we trying to use chakra there too?

Afaik chakra can't be used in react native but we can reuse our components.

my personal preference for the framework would be flutter (docs.flutter.dev), as this seems as the fastest way to develop a compelling UI and it's straightforward to bind it to Rust (see: fzyzcjy/flutter_rust_bridge).
It can be readily deployed to both iOS and Android and desktop/web as well without any further change. It is also recommended over react native for the faster app development (in both senses of the word 'faster', the dev speed and resulting app is faster).

I'm against flutter because it is a

new framework: flutter
a new language: dart

We have no experience with neither.

They seem quite straightforward; it's just declaring a widget tree and hooking up Rust functions. I would expect much, much less pain in the dev process thanks to the lack of virtual DOM, hooks etc.

I've got some questions about react native:
* how convenient is to use that with Rust?

I personally have no experience but I found a blog post about someone building an ethereum wallet with rust and react native which is very close to what we need

that project went only until setup & "Hello World" stage (!), this does not instil much confidence. It also needed to interact with JNI on android, and suggested creating custom Java bindings yourself.

There is a part 2 of this blog post and here is the parity signer which was written in react native and rust and then moved to native iOS and native Android as it looks like.
But maybe React Native + Rust is not the best call afterall. Any other thoughts @holzeis / @da-kami / @luckysori?

Well, any combination where we are cross compiling from rust to android and bridging it will introduce some complexities. I can't judge if this will only be a one time hassle or will follow us along the project. I feel like the easiest way would be to stay completely within TS, yet it does not look like there are many options for that. From a quick google the preferred way seems to build the wallet in rust and bridge to the respective platforms.
I can't say if flutter is better than react or the other way around. On the on hand I do agree with @bonomat arguments on the team skill, which rather speaks for react than for flutter. On the other hand, though, I don't think we should bother too much with that as I am sure the team will pick up the new framework very quickly.
I suggest we make quick prototypes with both frameworks and then go with the framework offering the best dev experience.

@bonomat @klochowicz Lets continue the mobile tech stack discussion here https://github.com/itchysats/itchysats/discussions/3191


chore: drink

We want to offer the developers a test suite for interacting with the pop chain extension. Luckily there is drink!.
Goal
Create an example contract (preferably with some logic around the api to see how what the devex is like - e.g. Error) using drink! for testing.
Steps

[ ] Fork the drink! repository with the following changes to make drink! mostly generic.
[ ] Move the required code from ink sandbox (e.g. the Sandbox trait) to the forked drink repository. This is not dependent of any ink code, see Cargo.toml`, so this should be straightforward. There are some useful macros that can be used as well.
[ ] Now in the pop-node repo we want to create a PopSandbox (here you can see how) which the developers can then use for their drink tests. One thing that I haven't tested yet is including the chain extension. The code says it handles it and there is also an example in the drink repository, so this should be doable.
[ ] When this all works we want to implement the example contract. This contract will be a very important exercise. Not only will we test the api, the error handling, the test suite, exposure to ink!, but also will be used for the first resource (most probably tutorial) for the pop api.

Created a new private repository (will be converted to public later) for pop-drink: https://github.com/r0gue-io/pop-drink


@alloy => no longer query for all: true on desktop artwork pages (for shows)

Based on recent metaphysics latency/memory issues, this fix is timely.
It's the follow-up from https://github.com/artsy/force/pull/2267 and should remove the remaining cases in force where we're using all: true to get all objects via pagination in metaphysics.
I borrowed the logic from the mobile-web side, but we can always revisit with updated language. For now it just says "View all  works".

Looks good, please merge on 💚 👍

merging...


[forge] change compatibility test suite start with older version

change compatibility test suite start with older version can save one time downgrading procedure at the start
Motivation
(Write your motivation for proposed changes here.)
Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan
(Share your test plan here. If you changed code, please provide us with clear instructions for verifying that your changes work.)
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/diem/diem/tree/main/developers.diem.com, and link to your PR here.)
If targeting a release branch, please fill the below out as well

Justification and breaking nature (who does it affect? validators, full nodes, tooling, operators, AOS, etc.)
Comprehensive test results that demonstrate the fix working and not breaking existing workflows.
Why we must have it for V1 launch.
What workarounds and alternative we have if we do not push the PR.

/canary

:broken_heart: Test Failed - ci-test

/land

:lock: Merge Conflict

:broken_heart: Test Failed - ci-test


[v3.0] Allow imports to be done with "no-interaction"

This re-implements #284 (#344) which makes it possible to run adldap:import unattended (e.g. cron / scheduler) For some reason the change done in #284 is missing from v3.0 and dev-master
This is for v3.0 since the importer in dev-master has changed (see #435 for that)

Sorry @syphernl, somehow these slipped through my inbox 😢

No worries @stevebauman!. I've been using my own fork for the time being, now I can safely switch back to yours :+1:


[Loc]String “rerun test” for old results in test panel not localized

Brief Issue Summary
Environment:
VS Code 1.95.1
CMake Tools v1.20.25 (pre-release)
More info:
Repro Language: All loc languages
Repro platform: Windows, Linux, Mac
Repro steps:

Open VS Code and change the display language to CHS
Download and unzip CMakeTestProject.zip
Open the project with VS Code
Click Testing in left navigation bar
Click “Run Test“ 2 times on the “Test” page
After tests run completed, click "Show Output" in Testing page
Focus on buttons next to CMake Tools in "Show Output" window

Actual result:
“Rerun the test” not localized in older results

CMake Tools Diagnostics

Debug Log

Additional Information
No response

We do not own that output pane / window. Closing. Thanks!


Remove header .logo fixed width in order make rtl work properly

This is a fix for the bug 1188678 (https://bugzilla.mozilla.org/show_bug.cgi?id=1188678)

I defer to @spasovski for r?

Looks good from my end. Thanks!


Warn pipenv and black users when LC_ALL isn't set

See #1027

Probably part of https://github.com/Microsoft/vscode-python/issues/648

The underlying problem is https://github.com/Microsoft/vscode-python/issues/1254
We're not logging any errors, its just being swallowed up.

If we do #1338 and log the entire environment then this can help with this as well by providing people with those details (but it's also a lot of info, so we might want to still limit what we send to the Output window).

Talking with Christian at the PyCon US sprints, Python 3.7 is setting LC_ALL=C.UTF-8 by default if it isn't overridden. So we might as well do this as well in other versions of Python when the user has not set it to avoid this issue with Click (we should also double-check that LANG does not need to be set, otherwise it can also be C.UTF-8).

What we might need to do is also provide whatever shell details we can to help people realize why when they have set their LC_ALL appropriately why it isn't being picked up. Best solution is to simply experiment and figure out whether the shell being used is login and/or interactive and tell people that they need to make sure to use the appropriate config file (e.g. .bashrc is not used in the same instances as .bash_profile for bash users).

And if we can tell people which shell is being used then that might also help (e.g. if someone thinks they are using bash when in fact we are using just sh).

My guess is we're executing in a login, non-interactive shell and people are setting stuff in .bashrc and their .bash_profile is not sourcing their .bashrc (context).

Is there a workaround for this to set LC_ALL?  As it stands, whenever I format code in VS Code using Black I end up with RuntimeError: Click will abort further execution because Python 3 was configured to use ASCII as encoding for the environment.  Consult http://click.pocoo.org/python3/for mitigation steps..  Running black on the command line doesn't have this problem, so my understanding is that LC_ALL isn't set when the Python extension runs Black, but I'm not sure how I can manually set that.

@pzelnip manually setting it depends on your shell. If you're using Bash then try your .bash_profile or .bashrc file. For other shells I'm not sure.

@brettcannon My apologies, I misunderstood the conversation earlier, I assumed that from the comment "My guess is we're executing in a login, non-interactive shell and people are setting stuff in .bashrc and their .bash_profile is not sourcing their .bashrc" that changes to my bash_profile/bashrc wouldn't be reflected in the integrated VS Code terminal (which I'm assuming is where Black runs when spawned by VS Code).  As it turns out, in my case the way I got it working was by setting $LC_ALL in my .bashrc as per your suggestion.
What's interesting to me at least is black was working in a Terminal window before this change (just not in VS Code).  Digging into it, on my machine in a plain terminal I had the $LANG env var set to en_CA.UTF-8 but no $LC_ALL set.  It appears as though click was using $LANG as if I unset $LANG in a regular terminal I got the same error about ASCII encoding.
I'm guessing that $LANG isn't set on login/non-interactive shell's, and as such isn't visible to Click when running Black in VS Code, but if it was then would work fine.
In any case, thanks for the workaround. 👍

The workarounds above don't seem to work for me. I'm on High Sierra, and I just installed vs-code and the python extension (2018.8.0). I've tried adding LC_ALL to my bash_profile and bashrc files without any effect, using both export and the launchctl commands mentioned in other issues. I've uninstalled and reinstalled vs-code. I've tried launching it from finder and from the console. I've also added confirmed that in the console (both inside and outside vs-code), the environment variables are set correctly and pipenv --venv works as expected. Here is the error in full:
Workspace contains pipfile but attempt to run 'pipenv --venv' failed with 'Traceback (most recent call last): File "/Users/wcass/.local/bin/pipenv", line 11, in  sys.exit(cli()) File "/Users/wcass/.local/lib/python3.6/site-packages/pipenv/vendor/click/core.py", line 722, in call return self.main(*args, **kwargs) File "/Users/wcass/.local/lib/python3.6/site-packages/pipenv/vendor/click/core.py", line 676, in main _verify_python3_env() File "/Users/wcass/.local/lib/python3.6/site-packages/pipenv/vendor/click/_unicodefun.py", line 118, in _verify_python3_env 'for mitigation steps.' + extra) RuntimeError: Click will abort further execution because Python 3 was configured to use ASCII as encoding for the environment. Consult http://click.pocoo.org/python3/for mitigation steps. This system lists a couple of UTF-8 supporting locales that you can pick from. The following suitable locales where discovered: af_ZA.UTF-8, am_ET.UTF-8, be_BY.UTF-8, bg_BG.UTF-8...
The pipenv is running python 3.6.5 installed via pyenv, and is having the same Click issue that has been mentioned elsewhere. Regardless of what I do, I can't seem to pass the enviroment variables on to the python extension so that it can execute pipenv. Any ideas how to get this to work?

@wcass77 I'll assume you didn't choose what your terminal is. That last option is .profile until we figure out how we want to solve this problem.

Unfortunately, that didn't work for me either.
It's perhaps not a great idea, but I decided to just change the code inside click to set the locale to 'en_US.utf-8' (my actual locale) before checking what the locale is. This isn't for a production project, and I'm just changing it to what it will be when pipenv is called from the command line, so I don't think it should cause issues.
In the file /Users/wcass/.local/lib/python3.6/site-packages/pipenv/vendor/click/_unicodefun.py (path given in the traceback), I changed this at line 53:
try:
    import locale
    fs_enc = codecs.lookup(locale.getpreferredencoding()).name
except Exception:
    fs_enc = 'ascii'
if fs_enc != 'ascii':
    return

To this:
try:
    import locale
    # manually set locale to en_US.UTF8
    locale.setlocale(locale.LC_ALL, 'en_US.utf-8')
    #end my code
    fs_enc = codecs.lookup(locale.getpreferredencoding()).name
except Exception:
    fs_enc = 'ascii'
if fs_enc != 'ascii':
    return

There is probably a better way to change the locale (or at least a better place to put it), but this seemed like the most direct way to ensure that it was set to the correct value when it mattered, and changing the code inside pipenv/click is not a problem in my particular use case. I hope this helps.

@wcass77 If you can switch to Python 3.7 then that might also help as there was work to try and alleviate this kind of locale issue.
And sorry for the trouble. I'm hoping we can address this (and other shell-related issues) in the near future.

No problem. I need to use 3.6 for this particular project, but I will
definitely keep it in mind. Now that I've got everything working, I'm
definitely enjoying vs code, and it's great to have it automatically run
tools like pylint in the right environment. Thanks!
On Tue, Sep 11, 2018 at 2:36 PM Brett Cannon<EMAIL_ADDRESS>wrote:

@wcass77 https://github.com/wcass77 If you can switch to Python 3.7
then that might also help as there was work to try and alleviate this kind
of locale issue.
And sorry for the trouble. I'm hoping we can address this (and other
shell-related issues) in the near future.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode-python/issues/1403#issuecomment-420376527,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABwjNdVfEVrRDLSanSwufrr1RHSSvGiJks5uaAK_gaJpZM4TXXZt
.

Closing as this hasn't been reported in the past few releases.


Documentation broken link

The "Documentation" link on the wiki page https://github.com/nltk/nltk/wiki/FAQ appears to be broken.

Thanks; this is fixed.


DSP: mismatched miner count between power consumption and total buildings required

The power consumed by miners is computed assuming each miner has access to 6 veins. The total number of miners required for the built is shown as the number of veins required across all resources. It would be more useful and correct to show total number of miners required that would match the power consumption (rounded up for each resource).

DSP is not supposed to show a number of miners at all since it can vary, I'll look into this


OpenFile.openDoc open a doc file from network will crash on android

"react": "16.0.0-beta.5",
"react-native": "0.50.0",

Experiencing the same here. Upgrading from 2.7.3 to 2.7.8 is what caused the issue for me. Reverting back to 2.7.3 for the time being.

I used the latest code from master branch, it works well


⚠ Processors has degraded performance

In 0d7e61c, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 67 ms

Resolved: Processors performance has improved in a6fd321.


[Feature Request] Ability to export color themes to Warp terminal format

I'm a Support Engineer at www.warp.dev which is a modern terminal that has a very similar export format to Alacritty. Warp also supports background images in the terminal, but if it's possible, it would be great if terminal.sexy users could at least export the color scheme to Warps yaml format. You can learn more about the format here: https://docs.warp.dev/appearance/custom-themes#create-your-own-custom-theme-manually
Along with an example below:
accent: '#268bd2' # Accent color for UI elements
background: '#002b36' # Terminal background color
details: darker # Whether the theme is lighter or darker.
foreground: '#839496' # The foreground color.
terminal_colors: # Ansi escape colors.
  bright:
    black: '#002b36'
    blue: '#839496'
    cyan: '#93a1a1'
    green: '#586e75'
    magenta: '#6c71c4'
    red: '#cb4b16'
    white: '#fdf6e3'
    yellow: '#657b83'
  normal:
    black: '#073642'
    blue: '#268bd2'
    cyan: '#2aa198'
    green: '#859900'
    magenta: '#d33682'
    red: '#dc322f'
    white: '#eee8d5'
    yellow: **'#b58900'**

We'd be happy to help with co-promotion and/or publishing on the site terminal.sexy's ability to export to Warp.

+1 for this
I literally came here to ask for Warp


Add .so symlinks

Reverting the removal of symlinks in #62.
cc @isuruf

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

+1, I was also needing this

@jschueller, can you add your use-case to https://github.com/conda-forge/openblas-feedstock/issues/67 as well?

These should go in https://github.com/conda-forge/blas-feedstock/blob/master/recipe/build_pkg.sh#L2 if they are to be added.

These should go in https://github.com/conda-forge/blas-feedstock/blob/master/recipe/build_pkg.sh#L2 if they are to be added.

@isuruf I am not sure about this. How can I know if all BLAS implementations will produce a libblas.so.3 file and not some other suffix?

They will. That's how this package is designed. Downstream packages will link to the netlib library which has soname 3 and we symlink that library to the optimized implementation in the other libblas variant.

Thanks! Opening the blas-feedstock PR.


Add an option to enable --runtime-repack in llama.cpp

Is your feature request related to a problem? Please describe.
After updating to 0.3.4 ARM optimized Q4_0_4_4 models are no longer supported by llama.cpp. Instead when loading an error is thrown that "TYPE_Q4_0_4_4 REMOVED, use Q4_0 with runtime repacking". This comes from this change in llama.cpp. I believe a flag must be added to llama-cpp-python and passed down llama.cpp internal to enable this feature.
Describe the solution you'd like
Add a flag for Llama instantiation that enables runtime repack in llama.cpp

After looking at the llama.cpp PR it seems like you just need to set this cmake flag to on, GGML_CPU_AARCH64 but when I tried doing CMAKE_ARGS="-DGGML_CPU_AARCH64=ON" pip install llama-cpp-python --upgrade --force-reinstall --no-cache-dir the performance of the Q4_0 was far worse than Q4_0_4_4 gguf before the update, and nothing in the verbose model output suggests that this was applied.

This may be a bug in llama.cpp. I will close this ticket if repack works after this issue is closed upstream

https://github.com/ggerganov/llama.cpp/pull/10890 apparently fixed this issue. I will test this after update to the latest llama.cpp


Adding the option for running counter with filenameTo:

I find that sometimes I need a running counter in filenames for the same rule.
So I added that.

@Claude123 thanks for your contribution!
May you update your PR and resolve any conflicts so I can review and merge the new features?

Hey @ahochsteger, I updated the PR to fix the conflicts

@Claude123 thanks for your contribution, looks good to me.


Mitigate document loading issues caused by Google Drive API #export method's unreliable size limit

Description of Change

When loading a page that is so large that it hits the (apparently somewhat arbitrary) size limit of the export method provided by the Google Drive library, instead manually get the page via download link:

Get the file's exportLinks (https://developers.google.com/drive/api/reference/rest/v3/files#exportLinks) aka direct download links, by including it in the fields here: https://github.com/nytimes/library/blob/main/server/list.js#L106
Reach it through to here: https://github.com/nytimes/library/blob/main/server/docs.js#L43
If the regular #export method of the Google Drive library returns 403 (File too large), directly make an HTTP call to the export link, which doesn't seem to have the same size limitations

In order to check if the fix works, you can try to access the following link when running this app on your local: http://localhost:3000/hobby-clubs/cars/mmmaija
When running it against the main branch, it should fail with a 500.
When running it against this branch, it should display the page.
Note: It takes a while to load the page with this workaround, since it will

first try to use the regular #export method
fail because it's too big
fall back to the workaround, which will then go ahead and actually download the page (for this example currently 6+ MB)

I've never opened this page in the live Library without the workaround since that's currently not working, so it's hard for me to tell if it previously also took a while to load, or if it is significantly slower now. That said, I figured it's better to implement this change as a fallback for the small-ish number of pages that is affected by the problem, and keep the "normal" way as the default.
Note 2: I noticed that there is a number of tests that are already failing on the main branch, and I'm not including any fixes for those in this PR. I only updated the tests that were directly broken by this change.
Related Issue
This issue is related to behavior of the files.export method of the Google Drive API library (https://developers.google.com/drive/api/reference/rest/v3/files/export), whose export size limit is apparently subject to changes without notice. This has been causing failures to load documents that previously worked perfectly fine and haven't changed in the meantime.
Motivation and Context
We've recently started having issues where we are getting 500 responses when loading certain pages/documents, caused by files.export (https://developers.google.com/drive/api/reference/rest/v3/files/export) returning 403 because the exported content is supposedly too large. According to the documentation, the exported content is limited to 10MB - however, our affected pages/documents did not change in size nor are they larger than 10MB when this problem started happening.
When digging into this some deeper, an old issue on the Google issue tracker came up (https://issuetracker.google.com/issues/36761333) that describes a similar problem. One comment states the following:

I reached out to the engineering team, and this error is working as expected. There is a limit as to how large of a file the files.export() endpoint can handle, and this error is thrown when files are larger than limit. In my testing I'm seeing the limit closer to 10MB, but it's worth noting that the limit is subject to change without warning.
As a workaround, you can use the Drive v2 API's files.get() endpoint to retrieve the exportLinks for the file and fetch that URL instead. From my testing that URL does not have the same limit as files.export() and more closely matches the behavior seen in the Google Docs UI's "File > Download as" menu item.

Seeing as we didn't make any changes to our documents, it looks like the limit was in fact changed without warning, which leads to some documents being unable to load.
Checklist

[x] Ran npm run lint and updated code style accordingly
[x] npm run test passes -> tests that are already broken in main will be addressed separately at a later time
[x] PR has a description and all contributors/stakeholder are noted/cc'ed
[x] tests are updated and/or added to cover new code
[ ] ~relevant documentation is changed and/or added~

Nice drive by refactor of taking away the node-sass aswell.
It was breaking locally otherwise, so it was sort of a forced refactor 😁 Might be good to pull it into a separate PR, since it's not related to the issue at hand.

@tommi-h Addressed all your comments, please have a look when you get a moment.

Will do. Happy midsummer!


Update link on docs.microsoft.com to aspnet

docs.microsoft.com has a link to ASP.NET Core which currently points to docs.asp.net
Make sure this fwlink points to something reasonable, probably not the  ASP.NET hub  page.
See what the .Net folks are doing.

@bradygaster  can you own this

From: Adam Kinney
That’s a good point.
Kim, you will need to update the .NET Hub Page links excel file that you sent Jason. Is that available on a share so the content can be updated?
From: Brady Gaster
Subject: RE: [aspnet/Docs] Update fwlink on docs.microsoft.com (#2069)
I agree with Adam. We want to edit both the .NET and Docs.ms.com home page HTML as late as possible but still get it pushed out in time for Connect so that we link to docs.ms.com/aspnet instead of RTD.

@Rick-Anderson paraphrasing earlier comment and email - i'm working with dev and design to make sure the link is changed on the docs home page at the appropriate time.


remove the extra resolve statement

Closing this PR as the changes are covered in this PR https://github.com/openBackhaul/OamLog/pull/383


[BUG] Nothing happens when I click start

So when ever I try to initiate the delete process I see this in the Developer Console Logs
VM506:1 Uncaught (in promise) SyntaxError: "undefined" is not valid JSON
at JSON.parse ()
at getToken (userscript.html?name=Undiscord.user.js&id=3b5b3e8e-f673-42e5-8204-85850dd7e630:1206:17)
at HTMLButtonElement.start (userscript.html?name=Undiscord.user.js&id=3b5b3e8e-f673-42e5-8204-85850dd7e630:1347:23)

Are you using the old copy paste version or the browser extension stuff?

What do you mean?

Same issue.
This happens with the browser extension version 5.0.3 installed through Greasy Fork. The issue is with getToken(), I think the localStorage keys have changed. LS.token is undefined.

Might be due to the update that lets you now switch between multiple accounts, I imagine some sort of collection of tokens is stored instead of a single one. I haven't had this happen on the 5.0.3 userscript version on Chrome myself however.

Funnily enough I couldn't find anything in localStorage that looked like a token.
I pulled my token out of the authorization header and string searched all of localStorage and couldn't find it.
I think it's related to this: https://stackoverflow.com/a/71759611
When I entered Responsive Design Mode in web developer tools then both token and tokens fields on localStorage got populated.


[18.09 backport] windows.ps1 fixes

https://github.com/moby/moby/pull/38418 PowerShell: various cleanups / fixes
https://github.com/moby/moby/pull/38419 PowerShell: fix "Nuke-Everything" failing to remove images
https://github.com/moby/moby/pull/38680 Windows CI: Dump possible panic log
https://github.com/moby/moby/pull/38860 Delete duplicate words

ping @andrewhsu @ddebroy PTAL

/cc @StefanScherer ptal

LGTM


Rearrangements and Additions

Redone Layout for Sponsorship Tier Sample and Example
Multiple minor changes within different pages
Added Sticker Provider page for different sticker types, sizes and providers
Fixed Current Mobile responsive for Sticker Art (wasn't showing 2 stickers on mobile)

[Apologies with random merge master commits (Issues with upstream fetching)]

lgtm


[Relay][VM][RPC]Use a uint64_t to serialize primitive_attrs in the Relay VM to fix 32bit RPC

cc @tkonolige
Ran into this trying to use RPC with the VM onto a 32bit Raspbian OS. Not sure how to test this in CI....

I don't think there is a good way to test this on CI.

Not sure how to test this in CI....

Could you construct a test that goes over 32 entries? It should fail in ci_i386.

Could you construct a test that goes over 32 entries? It should fail in ci_i386.

The problem is that you should not use types that are different sizes on different platforms. Not sure how going over 32 entries would fail on ci_i386 as it would probably serialize and deserialize just fine. We could possibly try serializing on one platform and deserializing on another but that makes CI really complicated.

@Mousius

Could you construct a test that goes over 32 entries? It should fail in ci_i386.

I don't think that would do it. The problem is that when I'm tuning on a 64 bit host and measuring on a 32 bit edge device, the size_t on the host is a 64 bit value which gets serialized into a byte stream. When the 32bit edge device tries to read that, it thinks the value should be a 32 bit size_t, and ends up corrupting the data stream as it reads it. I don't think it's possible to test that without running RPC across architectures.

Thanks @tkonolige @junrushao1994 @Mousius

hmm it might be possible to write a future test using ci-i386. cc @denise-k could you capture a tracking issue to think about this?


add konfiguration documentation (wis/pis/pid)

configuration description added for gammu.conf, smsgw.conf by myself and mario.


Add testcases to improve coverage and removed unused methods

Added testcases for UserInputHistory and removed unused methods for parsing and editing skill and team

Codecov Report

Merging #152 (943054b) into master (714ce88) will increase coverage by 1.90%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #152      +/-   ##
============================================
+ Coverage     68.23%   70.14%   +1.90%
- Complexity      569      574       +5
============================================
  Files            88       88
  Lines          1867     1839      -28
  Branches        221      212       -9
============================================
+ Hits           1274     1290      +16
+ Misses          510      467      -43
+ Partials         83       82       -1

Impacted Files
Coverage Δ

.../seedu/address/logic/parser/EditCommandParser.java
74.60% <ø> (+11.58%)
:arrow_up:

...in/java/seedu/address/logic/parser/ParserUtil.java
90.78% <ø> (+15.78%)
:arrow_up:

...c/main/java/seedu/address/model/person/Person.java
96.00% <ø> (+3.69%)
:arrow_up:

...n/java/seedu/address/storage/UserInputHistory.java
93.75% <0.00%> (+93.75%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 714ce88...943054b. Read the comment docs.


env -S doesn't work on bionic

env 8.28 doesn't have the -S option, but later versions do (for example 8.32)

I think we should drop bionic since this is EOL at the end of the May.
There is a sub to extend this until 2028... but I don't think we need to deal with this case.


Fix grammatical error

Changed an 'it' to an 'in' on line 17

@nolivermke : Thanks for your contribution! The author, @rayne-wiselman, has been notified to review your proposed change.

@nolivermke thank you for catching that!!
#sign-off

@JennieHubbard: I'm sorry - only the author of this article, @rayne-wiselman, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


Support for socket options to get/set TOS/TTL info

Add support for getting/setting IPv4 type-of-service (TOS) and time-to-live (TTL) information, and IPv6 traffic class (TC) and hop count information.
Depends on https://github.com/rust-lang/libc/pull/3450, which was recently merged.
(This is my first PR to nix, and I'm also reasonably new to Rust. Please let me know if I missed anything I should have changed; am happy to rework this.)

Hi! Thanks for your interest in contributing to Nix! :)
A libc with that patch hasn't been released yet, so we have to wait.
And a CHANGELOG entry is needed, please see CONTRIBUTING.md on how to add one.

@SteveLauC Thanks! I will convert this to a draft PR until libc has been release. Will also update CHANGELOG.

Hi @larseggert, we now use the libc dependency from git, so you don't need to patch it yourself, rebasing your branch should make things work

@asomers I added a test. Note that there is a FIXME in there - cmsg_space! returns too little space when called with the option types. I can't figure out why that is.
@SteveLauC I added a CHANGELOG entry.

Hi, sorry for the late response, I think I will take another look at this PR tomorrow:)


Page does not reload after recovering from server error

If there is e.g a syntax error in the code, browser displays 500 error, then error is fixed, the console shows that code is rebuilt correctly, but the page isn't refreshed automatically (need to hit F5).
Tested with Next 1.1.0.

Hmm, I can't reproduce. Can you post steps to reproduce the problem if possible ?

OK actually the behaviour depends on where the error is thrown. For example take as a base an app which is already running (can clone my app which has next 1.1.1).

if I change something in a getInitialProps (e.g throw new Error() on this line), that code isn't even re-executed when HMR runs.

1b. If I then hit F5, I get a 500 page and error in server log as expected.
1c. If I then remove the throw, HMR runs but nothing happens as in 1. I need to refresh again to clear the error page.

if I throw an error in a render (e.g throw new Error() on this line), I will see the error in the browser log, but the rendered page won't change to an error page

2b. If I remove the throw, the browser log further displays next-dev.bundle.js:35173 TypeError: Cannot read property 'getHostNode' of null (and rendered page doesn't change either)
Maybe there are further places to test, server and browser side, constructors, etc.

if I change something in a getInitialProps (e.g throw new Error() on this line), that code isn't even re-executed when HMR runs.

I'm not sure if we should call getInitialProps in this case, since we wouldn't like to reset props.

if I throw an error in a render (e.g throw new Error() on this line), I will see the error in the browser log, but the rendered page won't change to an error page

This is basically because of https://github.com/facebook/react/issues/2461.
There is a workaround though https://gist.github.com/Aldredcz/4d63b0a9049b00f54439f8780be7f0d8
btw, I'm not sure if we really want to change the page to an error one in this case.

2b. If I remove the throw, the browser log further displays next-dev.bundle.js:35173 TypeError: Cannot read property 'getHostNode' of null (and rendered page doesn't change either)

I have no idea why yet.

I'm not sure if we should call getInitialProps in this case, since we wouldn't like to reset props.

It currently sounds to me like it's better to reset props and actually run the code, than to remain blind. Otherwise can't rely on HMR for quick feedback, which defeats its purpose.

btw, I'm not sure if we really want to change the page to an error one in this case.

IMHO, better to render an error page for this case too, for coherent DX.

@sedubois It's been a while since activity on the issue. Can you check if it's fixed in the latest beta build? ❤

@timneutkens referring to my comment above https://github.com/zeit/next.js/issues/230#issuecomment-260422407:

is still present. If I add a throw new Error() in my getInitialProps and let HMR run, there isn't any error displayed. If I then refresh, error page is displayed, OK. But if I then remove the error and let HMR run, it won't clear the error page.

is fixed 🎉


Fix broken TAP link in SSO README

This should be resolved via https://github.com/vmware-tanzu/application-accelerator-samples/pull/163


[FEAT]: Open the OpenAPI endpoint for customization

What would you like to see?
Dear AnythingLLM team thank you for your quick responses and good work!
As the community is pretty new and still in its finding phase standards are rare and as of now only determined by OpenAPI it seems. More and more endpoints support the OpenAPI standard for example the huggingface text-embeddings-inference. As the AnythingLLM Application already provides the OpenAPI endpoint it might be very beneficial to allow a bit more customization like the URL for this endpoint. This would allow for a major growth of the compatible ecosystem and might be especially beneficial for embedding models.
My reason for requesting this feature is the rapid innovation in embedding models also focused on non-English speakers.
Keep up the good work!

Does the Generic OpenAi LLM provider not fill that gap at this time?
https://github.com/Mintplex-Labs/anything-llm/pull/1178
All the fields are open input and will just get used the OpenAI wrapper SDK - so this should be okay?

If this also includes the embedding model than  #1178 is the feature I would like to have. Yes!
I did not find this request before sorry for that and thank you for letting me know!

I just took a deeper look into feature #1178 and found this is not the feature I would like to have. My specific usecase is using the OpenAI kommunication protocoll for other embedding models.

Hello gentlemens, I'm trying to configure Generic OpenAI and I get an error:
400 Invalid type for 'max_tokens': expected an integer, but got a string instead.

@Vladimir-Va resolved via https://github.com/Mintplex-Labs/anything-llm/pull/1445
(not in most recent desktop version until 1.5.5+)


IE 11 support for customEvent

I manipulated the polyfills with a custom even function to provide support in IE11.
Simply adding the following adds support.
// source: https://developer.mozilla.org/en-US/docs/Web/API/CustomEvent/CustomEvent
(function() {
if (typeof window.CustomEvent === "function") return false
function CustomEvent(event, params) {
params = params || { bubbles: false, cancelable: false, detail: undefined }
var evt = document.createEvent("CustomEvent")
evt.initCustomEvent(event, params.bubbles, params.cancelable, params.detail)
return evt
}
CustomEvent.prototype = window.Event.prototype
window.CustomEvent = CustomEvent
})()

Hi @stwalter01,
Thanks for the feedback.
https://github.com/Vivify-Ideas/vue-draggable/pull/31/files
We can probably merge opened PR.

Thanks, any chance you can publish/release so npm install uses the latest code?
Thanks,
Sam

Hi Sam,
Yeah, it will be available tomorrow.
Sorry for the delay.

v2.0.3 with CustomEvent polyfill is published.


fix: remove concurrently

What kind of change does this PR introduce?
Bug fix
What is the current behaviour?
On my machine concurrently stumbles upon some permission errors when executed by lint-staged.
> concurrently "npm run test:format" "npm run test:ts" "npm t -- --coverage" ".../next-page-tester/src/__tests__/extractPagePathParamsType.test.ts" ".../next-page-tester/src/getPageObject.ts" ".../next-page-tester/src/pagePathParser.ts"

[3] /bin/sh: .../next-page-tester/src/__tests__/extractPagePathParamsType.test.ts: Permission denied
[4] /bin/sh: .../next-page-tester/src/getPageObject.ts: Permission denied
[5] /bin/sh: .../next-page-tester/src/pagePathParser.ts: Permission denied

What is the new behaviour?
This PR removes concurrently, but maybe we find a way to make it work. Is lint-staged running fine on your machine @Meemaw?
Does this PR introduce a breaking change?
No
Other information:
Please check if the PR fulfills these requirements:

[ ] Tests for the changes have been added
[ ] Docs have been added / updated

Coverage remained the same at 100.0% when pulling 0bae427e3486c3e536ffed9843a5cd5254807d13 on remove-concurrently into a389fdc23ca9429bdbe55886bda4414c9aad9346 on master.

Coverage remained the same at 100.0% when pulling 0bae427e3486c3e536ffed9843a5cd5254807d13 on remove-concurrently into a389fdc23ca9429bdbe55886bda4414c9aad9346 on master.

Yes its working fine or my machine. Lets remove it for now if it causes issues for you.

Yes its working fine or my machine. Lets remove it for now if it causes issues for you.


Edit TKC case history

I am Happy until Synthesis. Nice work @fourndo! There are some modifications required:

[x] Lesson worth highlighting needs some work

[x] Susceptibility model should be updated, and corresponding figures:

(All the images in this html except for the first one)

[x] Image for synthesis need to be modified

Looks like there is a duplicate figure label

https://travis-ci.org/geoscixyz/em/builds/278899016?utm_source=email&utm_medium=notification

@lheagy @sgkang  Ready to merge whenever

If you guys are happy - go for it :)


Docker Could not load helper ResembleHelper

Hi,
I am struggling to run my visual tests in docker container.
I am able to run functional tests without codeceptjs-resemblehelper helper in docker.
I am able to run visual tests without docker container.
I have codeceptjs-resemblehelper module added.
Tried to give the absolute path. REquired module manually. Nothing helped.
SImple docker command
docker run --net=host -v “$(pwd):/tests” codeception/codeceptjs codeceptjs run
also tried to give a direct path for mount
All I got is this
Could not load helper ResembleHelper from module ‘codeceptjs-resemblehelper’:
Cannot find module ‘codeceptjs-resemblehelper’
Require stack:
- /codecept/lib/container.js
- /codecept/lib/codecept.js
- /codecept/bin/codecept.js

Error:
    at createHelpers (/codecept/lib/container.js:166:13)
    at Function.create (/codecept/lib/container.js:42:25)
    at Codecept.init (/codecept/lib/codecept.js:57:15)
    at Command.module.exports (/codecept/lib/command/run.js:28:14)
    at Command.listener (/codecept/node_modules/commander/index.js:315:8)
    at Command.emit (events.js:209:13)
    at Command.parseArgs (/codecept/node_modules/commander/index.js:651:12)
at Command.parse (/codecept/node_modules/commander/index.js:474:21)
at Object.<anonymous> (/codecept/bin/codecept.js:228:9)
at Module._compile (internal/modules/cjs/loader.js:936:30)

Isolated issue by creating a basic project.
My config
const { setHeadlessWhen } = require('@codeceptjs/configure');

// turn on headless mode when running with HEADLESS=true environment variable
// HEADLESS=true npx codecept run
setHeadlessWhen(process.env.HEADLESS);

exports.config = {
  tests: './*_test.js',
  output: './output',
  helpers: {
    Puppeteer: {
      url: 'https://www.ss.lv/',
      show: true,
      windowSize: '1200x900',
	  chrome: {args: ['--no-sandbox']}
    },
     "ResembleHelper" : {
       "require": "codeceptjs-resemblehelper",
       "screenshotFolder" : "./tests/output/",
       "baseFolder": "./tests/screenshots/base/",
       "diffFolder": "./tests/screenshots/diff/"
     }
  },
  include: {
    I: './steps_file.js'
  },
  bootstrap: null,
  mocha: {},
  name: 'Tests2',
  plugins: {
    retryFailedStep: {
      enabled: true
    },
    screenshotOnFail: {
      enabled: true
    }
  }
}

@armands226  I suggest you try running your tests on docker container this way
docker run --net=host -v “$(pwd):/tests” -v "$(pwd)/node_modules:/node_modules" codeception/codeceptjs codeceptjs run

Please feel free to open the issue if this issue still persists.