Refactor task reconciliation logic

As described in this draft document: https://gist.github.com/bmahler/18409fc4f052df43f403.

Has to wait until 0.8.3.

Pretty sure this has been refactored.


RCNFetch.m line 246 Random crash after updating the SDK to 6.26.0

[REQUIRED] Step 1: Describe your environment

Xcode version: 11.4.1
Firebase SDK version: 6.26.0
Firebase Component: "Crashlytics", "Analytics", "Auth", "RemoteConfig", "Database", "Performance"
Installation method: CocoaPods

[REQUIRED] Step 2: Describe the problem
Random crash after upgrading the SDK to 6.26.0
Steps to reproduce:
The following crash happens on low network on app launch or app update.
Crashed: com.apple.main-thread
0  ******                        0x106dabb94 __65-[RCNConfigFetch refreshInstallationsTokenWithCompletionHandler:]_block_invoke_2 + 246 (RCNFetch.m:246)
1  ******                         0x106d2f964 __49-[FIRInstallations installationIDWithCompletion:]_block_invoke + 181 (FIRInstallations.m:181)
2  FBLPromises                    0x10805b9f8 __56-[FBLPromise chainOnQueue:chainedFulfill:chainedReject:]_block_invoke.48 + 273 (FBLPromise.m:273)
3  libdispatch.dylib              0x190f0e9a8 _dispatch_call_block_and_release + 24
4  libdispatch.dylib              0x190f0f524 _dispatch_client_callout + 16
5  libdispatch.dylib              0x190ec1640 _dispatch_main_queue_callback_4CF$VARIANT$mp + 1044
6  CoreFoundation                 0x1911c7748 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 12
7  CoreFoundation                 0x1911c261c __CFRunLoopRun + 1724
8  CoreFoundation                 0x1911c1c34 CFRunLoopRunSpecific + 424
9  GraphicsServices               0x19b30b38c GSEventRunModal + 160
10 UIKitCore                      0x1952f422c UIApplicationMain + 1932
11 *********                        0x1046cd180 main + 17 (AccessibilityIdentifiers.swift:17)
12 libdyld.dylib                  0x191049800 start + 4

@vinitam I'm sorry you encountered the issue. Could you please also share the supplementary crash info like an exception, crash reason, etc. if available?
One of potential crash reasons I can see so far is passing NULL as a dispatch_queue to dispatch_async here due to the unchecked weakSelf variable. We will provide a fix for this potential issue to be included into the next releases. As far as I can see, this part may lead to the crash only when Firebase application is deleted by the app. Do you know if your app calls something like FirebaseApp.app(). deleteApp {...} ?

`
Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000028
VM Region Info: 0x28 is not in any region.  Bytes before following region:<PHONE_NUMBER>
REGION TYPE                      START - END             [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
UNUSED SPACE AT START
--->
__TEXT<PHONE_NUMBER>57c000-0000000102580000 [   16K] r-x/r-x SM=COW  ....app/*******]
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [0]
Triggered by Thread:  0
Thread 0 name:
Thread 0 Crashed:
0   *******                       	0x0000000104afdd74 __65-[RCNConfigFetch refreshInstallationsTokenWithCompletionHandler:]_block_invoke_2 + 84 (RCNFetch.m:246)
1   *******                       	0x0000000104a81af8 __49-[FIRInstallations installationIDWithCompletion:]_block_invoke + 68 (FIRInstallations.m:181)
2   FBLPromises                   	0x0000000105c739f8 __56-[FBLPromise chainOnQueue:chainedFulfill:chainedReject:]_block_invoke.48 + 52 (FBLPromise.m:273)
3   libdispatch.dylib             	0x00000001862fea54 _dispatch_call_block_and_release + 24 (init.c:994)
4   libdispatch.dylib             	0x00000001862fea14 _dispatch_client_callout + 16 (object.m:502)
5   libdispatch.dylib             	0x000000018630b4d8 _dispatch_main_queue_callback_4CF$VARIANT$mp + 568 (inline_internal.h:2486)
6   CoreFoundation                	0x0000000186927344 CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE + 12 (CFRunLoop.c:1815)
7   CoreFoundation                	0x0000000186924f20 __CFRunLoopRun + 2012 (CFRunLoop.c:3111)
8   CoreFoundation                	0x0000000186844c58 CFRunLoopRunSpecific + 436 (CFRunLoop.c:3245)
9   GraphicsServices              	0x00000001886f0f84 GSEventRunModal + 100 (GSEvent.c:2245)
10  UIKit                         	0x000000018ff9d5c4 UIApplicationMain + 236 (UIApplication.m:3956)
12  libdyld.dylib                 	0x000000018636456c start + 4
`

We are calling deleteApp within our app which was called previously as well.
Attaching the exception for details:
Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000028
VM Region Info: 0x28 is not in any region.  Bytes before following region:<PHONE_NUMBER>
      REGION TYPE                      START - END             [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      UNUSED SPACE AT START
--->
      __TEXT<PHONE_NUMBER>57c000-0000000102580000 [   16K] r-x/r-x SM=COW  ....app/*******]

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [0]
Triggered by Thread:  0

Thread 0 name:
Thread 0 Crashed:
0   *******                       	0x0000000104afdd74 __65-[RCNConfigFetch refreshInstallationsTokenWithCompletionHandler:]_block_invoke_2 + 84 (RCNFetch.m:246)
1   *******                       	0x0000000104a81af8 __49-[FIRInstallations installationIDWithCompletion:]_block_invoke + 68 (FIRInstallations.m:181)
2   FBLPromises                   	0x0000000105c739f8 __56-[FBLPromise chainOnQueue:chainedFulfill:chainedReject:]_block_invoke.48 + 52 (FBLPromise.m:273)
3   libdispatch.dylib             	0x00000001862fea54 _dispatch_call_block_and_release + 24 (init.c:994)
4   libdispatch.dylib             	0x00000001862fea14 _dispatch_client_callout + 16 (object.m:502)
5   libdispatch.dylib             	0x000000018630b4d8 _dispatch_main_queue_callback_4CF$VARIANT$mp + 568 (inline_internal.h:2486)
6   CoreFoundation                	0x0000000186927344 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 12 (CFRunLoop.c:1815)
7   CoreFoundation                	0x0000000186924f20 __CFRunLoopRun + 2012 (CFRunLoop.c:3111)
8   CoreFoundation                	0x0000000186844c58 CFRunLoopRunSpecific + 436 (CFRunLoop.c:3245)
9   GraphicsServices              	0x00000001886f0f84 GSEventRunModal + 100 (GSEvent.c:2245)
10  UIKit                         	0x000000018ff9d5c4 UIApplicationMain + 236 (UIApplication.m:3956)
12  libdyld.dylib                 	0x000000018636456c start + 4

@vinitam Thank you for the quick response. The information you provided proves that the reason I described above is most likely behind the crash.
As a temporary workaround while waiting for the fix to be released you may try to avoid deleteApp if possible.
A bit a side question - I wonder why deleteApp is needed in you app?

We are dynamically setting firebase config. So every time we set the new config we call deleteApp.
As suggested we will remove deleteApp till this is fixed. Also wanted to understand if there will be any side effect in our scenario in case we remove deleteApp.

@vinitam In general Firebase has a very limited support for dynamic configuration for now, e.g. the default Firebase app should always be configured at the app start for Analytics to work correctly. Could you please provide more details on the way you dynamically configure Firebase so we can better under if your use case is supported or you may need to make any adjustments?

Thanks for the response @maksymmalyhin.
Just to give you some idea, we are setting firebase with default options at the start of the app. We then make an API call to fetch dynamic config (api key, db url) from the backend and then use the function deleteApp and reconfigure firebase. In case, I do not use  the deleteApp function I get an error saying Terminating app due to uncaught exception 'com.firebase.core', reason: 'Default app has already been configured.

@vinitam Your use case looks reasonable and supported. Calling deleteApp is required to reconfigure an app, so you were doing it correct. Another possible option for you to avoid deleting and re-configuring the default app could be configuring a second firebase app with the config received from server. If you decide to go with multi apps please note that not all products support secondary apps so such products will keep using the default one.
The PR #6133 that should fix the crash was merged. The fix should be available in the next Firebase release. If you have a chance to test it, you may try to use remote config version from master.
Feel free to reopen the issue with more details if you still experience the crash. Thanks.

@maksymmalyhin I believe I might be having the same sort of problem?
Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000028
VM Region Info: 0x28 is not in any region.  Bytes before following region:<PHONE_NUMBER>
      REGION TYPE                      START - END             [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      UNUSED SPACE AT START
--->
      __TEXT<PHONE_NUMBER>d68000-00000001033e4000 [ 6640K] r-x/r-x SM=COW  ....app/*********

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [1074]
Triggered by Thread:  0

Thread 0 name:  Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0   *********                      	0x0000000102f044b8 __65-[RCNConfigFetch refreshInstallationsTokenWithCompletionHandler:]_block_invoke_2 + 1688760 (RCNFetch.m:244)
1   *********                      	0x0000000102eb92fc __49-[FIRInstallations installationIDWithCompletion:]_block_invoke + 1381116 (FIRInstallations.m:176)
2   *********                      	0x0000000102f3b8e8 __56-[FBLPromise chainOnQueue:chainedFulfill:chainedReject:]_block_invoke.48 + 1915112 (FBLPromise.m:273)
3   libdispatch.dylib             	0x0000000196652134 _dispatch_call_block_and_release + 32
4   libdispatch.dylib             	0x00000001966535ac _dispatch_client_callout + 20
5   libdispatch.dylib             	0x000000019665f85c _dispatch_main_queue_callback_4CF + 968
6   CoreFoundation                	0x000000019692c8d4 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 16
7   CoreFoundation                	0x000000019692758c __CFRunLoopRun + 1692
8   CoreFoundation                	0x0000000196926bc8 CFRunLoopRunSpecific + 480
9   GraphicsServices              	0x00000001a0d085cc GSEventRunModal + 164
10  UIKitCore                     	0x000000019aad9744 UIApplicationMain + 1936
11  *********                      	0x0000000102d6f3d8 main + 29656 (main.m:16)
12  libdyld.dylib                 	0x00000001967a3384 start + 4

I'm trying to use the master branch like you suggested like this:
  pod 'Firebase/Core'
  pod 'Firebase/Messaging'
  pod 'Firebase/RemoteConfig', :git => 'https://github.com/firebase/firebase-ios-sdk.git'

But I seem to run into this and it might be because of my use of react-native-firebase v5:
[!] There are multiple dependencies with different sources for `Firebase` in `Podfile`:

- Firebase/Core
- Firebase/Messaging
- Firebase/RemoteConfig (from `https://github.com/firebase/firebase-ios-sdk.git`)

@Pashtunzoy you can check the version of FirebaseRemoteConfig that was installed by looking at the Podfile.lock.

@morganchen12 It's FirebaseRemoteConfig (1.3.0)

The latest public (non-master) version is 4.8.0. Something in your Podfile (possibly react?) is causing the Remote Config dependency to be very out-of-date.


kubernetes: 1.30.2 -> 1.30.3

Description of changes
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

@saschagrunert
The job "OfBorg / kubernetes, kubernetes.passthru.tests on aarch64-darwin" is stuck for 24hrs, anything that can be done?

@saschagrunert
@srhb
@johanot
@offlinehacker
Anything else to merge this?

Super seeded by: https://github.com/NixOS/nixpkgs/pull/334417


Testing CI

Do not merge this pull request, just want to make a test run with an almost empty PR

@dotnet-bot test Windows 7 daily_dev12_x64_debug please

I re-triggered all the failing daily builds on the release/1.4 Build Status Page to confirm. It looks like this was introduced in a separate change from #2228

closing this as it looks like it repro in the build status page


Bug 2091113: Query child resources only when new ones are being created

During ZTP scale test, it was discovered that the list operations could be too slow when the number of objects in the namespace get higher than a few hundreds, even though the number of objects matching the label selector is fairly small. This change minimizes the use of the list operation so that TALO can sustain higher rate of SNO deployment scenario. It was tested in the scale lab and achieved 100% du profile applied at 50 clusters per 10 minutes (1.5 times the highest rate achieved without this change)

/assign @vitus133 @serngawy

sounds good, would you squash the comments

It will be squashed as part of the merge process.

/cherrypick release-4.10


A question in the basic usage

In your usage, you note that:
<View style={styles.container}>   <Button     text="Show Dialog"     onPress={() => {       this.popupDialog.show();     }}   /> </View>
Is the "text" prop in Button should be "title"? I think your Button has conflict with the built-in Button.
Also, this onPress cannot pop up the dialog

@chen4393 It's just example.

@chen4393 However I updated README. Thanks for your opinion!


chore(main): release 3.1.6

:robot: I have created a release beep boop
3.1.6 (2024-07-26)
Bug Fixes

escape spaces in paths for grug-far integration (#267) (f265e95)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v3.1.6
:sunflower:


Fix ConcurrentModificationException in Datafeed loop #475

A ConcurrentModificationException can happen in the Datafeed (DF) loop upon startup.
The access to the listeners collection in the DF loop is not protected
and accessed by multiple threads.
Because of the for loop we need to synchronize on the list itself.
Fixes #475

I'm not super happy with the sleep in the test but I could not a better way :/


Progress bar indicator not showing

Describe the bug
The Dialog datatype seems to ignore the UPDATE of a percentage bar indicator.
To Reproduce
Steps and to reproduce the behavior:
Create a report like:
report 50100 "Progress Bar TEST"
{
Caption = 'Demo Contract Billing Simulation';
ProcessingOnly = true;
ShowPrintStatus = false;
dataset
{
}

    trigger OnPostReport()
    var
        i: Integer;
        Window: Dialog;
    begin
        Window.OPEN('Processing\#1##################\@2@@@@@@@@@@@@@');
        for i := 1 to 100 do begin
            Sleep(100);
            Window.Update(1, ROUND(i / 100 * 10000, 1));
            Window.Update(2, ROUND(i / 100 * 10000, 1));
        end;
        Window.Close();
        message('Ready');
    end;
}

}
Expected behavior
2 bars: 1 with percentage of done, and 1 with a number
But only the number is shown, not the percentage bar.
Screenshots

5. Versions:

AL Language: v5.0.288712

Business Central: Version: W1 16.2 (Platform 16.0.13402.0 + Application 16.2.13449.0)

https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/methods-auto/dialog/dialog-open-method

Note
With the Dynamics NAV Client connected to Business Central, you can use @ characters instead of # characters for the String parameter to display the value as percentage and a progress indicator. The percentage value that is displayed is the percentage of the variable value from 0 to 9999. This is not supported in the Business Central Web client.

Thanks Natalie, But does this mean it is not an issue and is not in the backlog: will this be solved in a future release?

It is on Microsoft to answer this :-) I could only guess.

I did a quick search in the base app code on '@.*@@@@'. And there are still many. So I guess this will still have some value in the future ;).

Thank you @NKarolak for your investigation and your answer.
@MaartenGerritsen, the decision on whether to fix it or to consider it as by-design (because this limitation is publicly documented) would have to be done by the team owning this area/feature.
We suggest that you open a support case or file a bug in Collaborate. To open a support case, you can:

Open a support request to CSS through the PartnerSource portal
Contact your Service Account Manager (SAM) in your local subsidiary to understand what is included in your contract as of support incident and PAH (Partner Advisory Hours). Your SAM might also direct you "step by step" how to open a support request or how to get credentials, if this is the first time for you or your company

If you file the bug in Collaborate, remember to include steps to reproduce the issue, and the Business Central build number and country version you're using.


Omnisharp failing due to System.IO.IOException: The process cannot access the file ... because it is being used by another process

Issue Description
When saving a C# file (/filesChanged), Omnisharp fails due to a System.IO.IOException, stating that it is being used by another process.
Steps to Reproduce

Create a new project.
Have Omnisharp set to format on save.
Make changes to a C# file.
Save or otherwise trigger the /filesChanged command.

Expected Behavior
The C# file should be formatted and saved.
Actual Behavior
The file does not get formatted, and the output log prints the log below.
Logs
OmniSharp log

[warn]: OmniSharp.Stdio.Host
        ************ Request ************
{
  "Type": "request",
  "Seq": 180,
  "Command": "/filesChanged",
  "Arguments": [
    {
      "FileName": "d:\\Programming\\GithubRepos\\CsLorax\\LoraxTest\\LoraxTest.cs",
      "changeType": "Change"
    }
  ]
}
[fail]: OmniSharp.Stdio.Host
        ************  Response (0.7794ms) ************
{
  "Request_seq": 180,
  "Command": "/filesChanged",
  "Running": true,
  "Success": false,
  "Message": "\"System.IO.IOException: The process cannot access the file 'd:\\\\Programming\\\\GithubRepos\\\\CsLorax\\\\LoraxTest\\\\LoraxTest.cs' because it is being used by another process.\\r\\n   at Microsoft.Win32.SafeHandles.SafeFileHandle.CreateFile(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options)\\r\\n   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize)\\r\\n   at System.IO.Strategies.OSFileStreamStrategy..ctor(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize)\\r\\n   at System.IO.Strategies.FileStreamHelpers.ChooseStrategy(FileStream fileStream, String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, Int64 preallocationSize)\\r\\n   at System.IO.StreamReader.ValidateArgsAndOpenPath(String path, Encoding encoding, Int32 bufferSize)\\r\\n   at System.IO.File.InternalReadAllText(String path, Encoding encoding)\\r\\n   at System.IO.File.ReadAllText(String path)\\r\\n   at OmniSharp.Roslyn.BufferManager.UpdateBufferAsync(Request request, Boolean isCreate) in D:\\\\a\\\\1\\\\s\\\\src\\\\OmniSharp.Roslyn\\\\BufferManager.cs:line 49\"",
  "Body": null,
  "Seq": 3960,
  "Type": "response"
}

C# log

Getting latest OmniSharp version information
Downloading package 'Latest OmniSharp Version Information' (1 KB).................... Done!

I have the same issue, and as @DanteMarshal pointed out, I don't have format on save enabled either.
But otherwise, the error message is exactly the same. I'm using .NET SDK Version: 6.0.307  Commit: 55b7c993a1
I also saw this issue that has been marked as completed but the error message from this one is slightly different.
My only solution right now is to use the Restart OmniSharp command, but the error usually happens again soon after..
If anyone has a solution of info on this problem that would be fantastic :)

A lot has changed with O#  since this issue was opened. If you are still having problems, please open a new issue at https://github.com/omnisharp/omnisharp-roslyn/issues


fix(floating-point): use bcmath extension instead of simple division

#172

Sorry for ling delay. Good one, thanks @Ni-vek !


iOS shareInstagram parameters

For Android: Just use the InstagramSharePlus.shareInstagram("path", mediaType: "video" or "image");
For iOS: Just use the InstagramSharePlus.shareInstagram();

Is this a typo? Should we not supply iOS with a path?
I have a video file downloaded in my app in to the cache and I want the user to be able to share it to Instagram Stories.
Also what are the lowest OS levels supported with this plugin?

You can currently only select video or an image from files.
Supported for iOS 14 and up.

@milanciganovic can we supply the plugin with the video path like you allow it with Android API?

To share asset to Instagram you have to provide a "localId" (local identifier) from the PHAsset object, which you can access from the native picker.
If someone knows a better solution feel free to open a PR.

Hi @milanciganovic :)
I am not familiar with the native side especially iOS
to be clear, I don't need the media picker at all.
I want to share to Instagram stories directly by specifying a video asset from code.
Right now, your plugin works like this for Android. So I want the iOS side to be similar to the Android.
I hope the community can help
Because the share_plus plugin can not share a video to Instagram stories and I searched the whole packages and none of them can do this :/

As of now, I do not think the feature you described is supported by Instagram.
Sharing to stories


Teach basics of Public VM to team

References:

Miden VM: https://wiki.polygon.technology/docs/miden/intro/main/
Zac's and Mike's public VM spec: https://hackmd.io/@aztec-network/HJwFbl68i?type=view

Public VM Circuit

Spec!!!
Native version
Genericise Plonk Columns
Circuit version

Closing, as status moved to 'Done' (it's a GitHub bug... closing will move an item to 'Done', but not the other way around)


ActionSet: expressive buttons have max width in latest carbon update

What package(s) are you using?

[X] Cloud & Cognitive
[ ] Legacy/CDAI
[ ] Legacy/Security

Detailed description

Describe in detail the issue you're having.
In the latest carbon version, the expressive buttons in the ActionSet have a max-width set on them which causes layout issues when used in larger scenarios (Tearsheet, CreateTearsheet, max size side panels).
Is this issue related to a specific component?
ActionSet
What did you expect to happen? What happened instead? What would you like to
see changed?
The ActionSet buttons should not have a max-width so that they can always take up the available space they fit in.
What browser are you working in?
Chrome
What version of the @carbon/ibm-cloud-cognitive packge are you using?
Latest

Steps to reproduce the issue

You can see this issue in the code sandbox for CreateTearsheet

Please create a reduced test case in CodeSandbox

https://codesandbox.io/s/createtearsheet-example-jzj7y?file=/src/MultiStepExample.js)
Additional information

Screenshots or code

Notes

https://github.com/carbon-design-system/ibm-cloud-cognitive/pull/859

Complete


Feature request: Support for declaring language on elements in rich text.

Let's say I am writing an English text on my Wagtail site. In my richt text editor I have my paragraph:

Wagtail is a leading open source CMS. The Dutch call it: geweldig.

According to Web Accessibility guidelines I should declare something like lang="nl" on the Dutch word geweldig. Currently, this is not possible using de Draftail editor.
Does anyone else recognize the need for declaring language on elements? Do you think this should be a feature supported by Wagtail?
My efforts
I tried creating a basic Draftail plugin (the L-button). A span element having the lang attribute set to whatever the user inputs into a browser prompt popup gets wrapped around text you select.
This works, in a basic way, but is not a very user friendly solutions. In addition, preferably we should be able to declare language on other elements such as blockquote, em, strong, etc.

Geweldig idea.

Tagging as Accessibility thanks to @kevinhowbrook mentioning this on Slack! I think this should be done as a style (LANG_<ISO language code>), potentially with a custom control that ensures elements can only be declared as one language (can’t have multiple languages on a single range of text like other styles support).

We discussed this in today’s accessibility team meeting. There is interest in this feature, and potentially having ways to do this at the level of the whole field, or a block within the field, rather than just inline spans of text.

If anyone is already doing something similar to this on their site I would be interested to learn from examples – whether that’s with other CMSes having built-in functionality like this, or custom implementations. It’s not really clear at what level of granularity this should ideally be implemented.
The initial issue here is for runs of text within a sentence, which is as granular as it gets, but I imagine it would also be beneficial to set the language for whole "blocks" – it’s just not too clear how to build that in a sensible way (Rich text blocks? StreamField blocks? Something else entirely?).
I would also welcome examples of sites/pages out there that use mixed language as a reference.

@thibaudcolas is there an idea when this will be implemented?

I’m not aware of anyone currently planning to work on this. I’d be interested to help someone make it happen though!


Project name (pREST) and support for other database types besides PostgreSQL

pREST was born with the need to open the Postgres database as a remaining API (in this issue #41 I explain better), with the evolution of the project came the opportunity to support other databases (ex MariaDB/MySQL #239), we modeled the pREST core to accept other database adapters.
Segnified (initial) from the prefix p in the name pREST?

p = Postgres

With support for other databases it no longer makes sense to tie the prefix with Postgres but to be an agnostic name for the database. After reflecting on a resignified p prefix I came up with the following idea - I will try to share it here.

p = Pure

Because Pure? Comes from Pure functions have lots of properties that are important in functional programming, including referential transparency (you can replace a function call with its resulting value without changing the meaning of the program).

Makes sense? Leave your comment, recommendation or constructive criticism

Pure may not be a good value because it would lead you to think that it is a clean implementation of rest, perhaps restful.
And a reminder, maybe the logo should also be modified.

we can replace pure by powerful or Passionate
other ideas here: https://chi-nese.com/list-of-positive-words-that-start-with-p/

I agree with @cassiobotaro and @sebastianwebber.
Since the project work with databases, I think will make more sense to use the p as persistent.

Hi folks,
For obvious reasons I'm totally skeptical about it and every time I see a multi-database tool sounds like a "one ring to rule them all", and in practice this kind of tool always lack of specific (and cool) database features because of the idea of standardization of API/UI/etc.
Although my skeptical opinion I'm not saying is a bad idea, because thinking from the user/developer perspective we can provide one RESTfull API to be a middle-ware between different database flavors and it's awesome, but anyway I can see some limitations:

transactions: we can't enable transactions between different adapters... ok depending of the database implementation we can use 2PC (Two-phase Commit) but it's somehow hard to maintain and error prone

endpoints: different databases have different ways to deal with schemas,  so we'll need to think very well about GET /DATABASE/SCHEMA/TABLE

query statements: can be hard to standardize due to differences of SQL syntax between databases. I know we have the ability to write our own SQL scripts but the idea of a RESTfull API is to avoid it, no?

My two cents!


Fix dockerfile fail on arm64

Description
Dockerfile build on Arm64 fail due to

gcc-multilib and g++-multilib are not available in Arm64
Get libnettle 2.7.1 from https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/11961574

Status
READY/IN DEVELOPMENT/HOLD

Removing legacy gnutls and libnettle 2.7.1 makes it so that this dockerfile is incomplete.
Without it all.sh will not succeed, as compat.sh will fail (thus the description is incorrect).
I can see that there are builds of libnettle 2.7.1 on ARM64 (for example here: https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/11961574), so what's the underlying issue? If it exists, could you please link the issue with logs?

Thanks @AndrzejKurek . I has fix that base on your link.
I will upload new patch after self test and revert previous one.

Note that the dockerfile we actually use on our CI is now public: https://github.com/ARMmbed/mbedtls-test/tree/master/resources/docker_files . Rather than maintain a separate docker file in the mbedtls repository, we should probably delete it and refer people to the one we use.

Note that the dockerfile we actually use on our CI is now public: https://github.com/ARMmbed/mbedtls-test/tree/master/resources/docker_files . Rather than maintain a separate docker file in the mbedtls repository, we should probably delete it and refer people to the one we use.

The build success but github does not show pass

@yuhaoth . There is an ongoing work (PR31)to re-allign and cleanup docker files. As @gilles-peskine-arm mentioned it may be worth to test this change on top of that image.
Two things to note:

libnettle is compiled from source

# Install Gnu TLS 3.4.10 (nettle 3.1) - main version, in the PATH
RUN wget -q https://ftp.gnu.org/gnu/nettle/nettle-3.1.tar.gz && \
    tar -zxf nettle-3.1.tar.gz && cd nettle-3.1 && \
    ./configure --prefix=/usr/local/libnettle-3.1 --exec_prefix=/usr/local/libnettle-3.1  --disable-shared --disable-openssl && \
    make && make install && cd .. && rm -rf nettle-3.1* && \
    export PKG_CONFIG_PATH=/usr/local/libnettle-3.1/lib/pkgconfig:/usr/local/libnettle-3.1/lib64/pkgconfig:/usr/local/lib/pkgconfig &&

Security Universe repo contains a gcc-multilib-package which we could potentially use. Is there any requirement for g++-multilib?

Is there any requirement for g++-multilib?
I did not know, just copy origin packages.

Security Universe repo contains a gcc-multilib-package which we could potentially use.

Yes and no. In the official dockerfile, we use it only to uninstall it.

Is there any requirement for g++-multilib?

No. The only C++ build we do is to check that the header files are compatible with C++ (e.g. no use of a variable called new), and that only requires a host compiler.

What's the point in maintaining this dockerfile? We don't use it at Arm, we don't ever intend to use it, and our official dockerfile is now public. We should remove the dockerfile in the mbedtls repository.

What's the point in maintaining this dockerfile? We don't use it at Arm, we don't ever intend to use it, and our official dockerfile is now public. We should remove the dockerfile in the mbedtls repository.

I use this file to setup my local environment. And some local PC are arm64.
And I think we should think about arm64 support.  As I know, Arm64 PC and server have been available. like AWS graviton2 and Apple M1

https://github.com/ARMmbed/mbedtls-test/pull/35 is created. Close this one


Mobile App failes to register new sensors

The problem

Using mobile app on android. I think this is a backend issue, but I'm not sure.
While one of the android phones works well and registers all it's sensors the other one failes to register the new sensors. According to the logs it sends updates, but there are no sensors registered. I've already disconnected, reinstalled and reconnected the app.
Environment

Home Assistant release with the issue: 0.106.0b0
Last working Home Assistant release (if known): Unknown, never
Operating environment (Hass.io/Docker/Windows/etc.): HA Core in Docker
Integration causing this issue: mobile_app
Link to integration documentation on our website: https://www.home-assistant.io/integrations/mobile_app/

Problem-relevant configuration.yaml

None

Traceback/Error logs

2020-02-19 18:17:22 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.mobile_app
2020-02-19 18:17:22 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.mobile_app
2020-02-19 18:17:22 INFO (MainThread) [homeassistant.components.device_tracker] Setting up device_tracker.mobile_app
2020-02-19 18:18:01 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Refusing to update non-registered sensor: ee1f6659a0f651c84a6a62505b35800db6f8703d143bfcba1070208ddf29c2b0_battery_level
2020-02-19 18:18:01 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Refusing to update non-registered sensor: ee1f6659a0f651c84a6a62505b35800db6f8703d143bfcba1070208ddf29c2b0_wifi_connection
2020-02-19 18:19:01 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Refusing to update non-registered sensor: ee1f6659a0f651c84a6a62505b35800db6f8703d143bfcba1070208ddf29c2b0_battery_level
2020-02-19 18:19:01 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Refusing to update non-registered sensor: ee1f6659a0f651c84a6a62505b35800db6f8703d143bfcba1070208ddf29c2b0_wifi_connection
2020-02-19 18:22:17 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Refusing to update non-registered sensor: ee1f6659a0f651c84a6a62505b35800db6f8703d143bfcba1070208ddf29c2b0_battery_level
2020-02-19 18:22:17 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Refusing to update non-registered sensor: ee1f6659a0f651c84a6a62505b35800db6f8703d143bfcba1070208ddf29c2b0_wifi_connection
2020-02-19 18:23:45 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook ee1f6659a0f651c84a6a62505b35800db6f8703d143bfcba1070208ddf29c2b0
2020-02-19 18:23:45 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook ee1f6659a0f651c84a6a62505b35800db6f8703d143bfcba1070208ddf29c2b0
2020-02-19 18:24:45 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new device_tracker.mobile_app entity: device_tracker.nokia_8_1
2020-02-19 18:24:45 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.mobile_app
2020-02-19 18:24:45 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.mobile_app
2020-02-19 18:24:45 INFO (MainThread) [homeassistant.components.device_tracker] Setting up device_tracker.mobile_app
2020-02-19 18:25:21 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Refusing to update non-registered sensor: cfe18a0dd90515f72bd650485a89be6d185345b60b7cab9040e9e77ff685fe33_battery_level
2020-02-19 18:25:21 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Refusing to update non-registered sensor: cfe18a0dd90515f72bd650485a89be6d185345b60b7cab9040e9e77ff685fe33_wifi_connection

Additional information

@Santobert when you reinstalled the application did you make sure to delete the existing integration for the device? The proper steps for reinstalling are noted here: https://companion.home-assistant.io/docs/troubleshooting/faqs/#starting-fresh-with-the-android-app

@dshokouhi yes, I did. The docs are new to me, but I did everything that's listed there.

Could you test with this PR either reverted or rollback to 0.105.5?
https://github.com/home-assistant/home-assistant/pull/31756
I think it might be related but not sure.  The device name in the traceback looks very odd but the unregistered entity issue was usually related to needing a fresh integration for mobile_app.  Can you also confirm the device name from App Configuration screen?

I am more curious about the device name that is set by the device since it should be the same model that was registered.  What device is having this issue too? Is it the Nokia listed in traceback? Because that is the name the PR is using.

It is not related. The error was there before. I've hoped it would solve the issue.
Well, I've followed the steps you mentioned before and it works now. I guess I've missed one before. Thanks for your help

I am more curious about the device name that is set by the device since it should be the same model that was registered. What device is having this issue too? Is it the Nokia listed in traceback? Because that is the name the PR is using.

I've a nokia 7 plus which works fine. The nokia 8.1 was having issues.

@Santobert yea the docs are brand new I started updating them a week ago lol.  Glad to know its resolved.  Yea the start fresh steps need to be done in a specific order and since the app is new it may need to be done when things go odd like that.


Reconsider curatedData value

Split from https://github.com/nf-osi/nf-metadata-dictionary/issues/171

Consider removing curatedData as value, or determine better, more precise term.

Was removed


cmd/compile: explicit zeroing memory returned by newobject

Compiling this code at 249aca5dee:
package p

type x [256][]byte

//go:noinline
func (*x) m() {}

func f() {
        a := x{}
        a.m()
}

generates a call to newobject (to heap allocate a) followed by code to zero it out (e.g., the call to typedmemmove).
There's a couple related questions:

newobject returns zero'd memory, so why are we still generating explicit zeroing code? Replacing a := x{} with var a x eliminates the explicit zero'ing.
typedmemclr would be better for explicit zero'ing, and CL 34566 actually fixes this... except I'm not sure why. (Edit: @cherrymui pointed out why in the CL.)
Why is a being heap allocated anyway? Shouldn't escape analysis be able to identify that (*x).m's parameters don't escape? (Edit: This appears to be #18001.)

/cc @randall77 @cherrymui @josharian @aclements @dr2chase

It still uses statictmp probably because CL https://go-review.googlesource.com/c/35261/ doesn't cover array?
I'm working on the new write barrier insertion code for #17583 (almost ready). Along that line I have prepared some changes that will remove the explicit zeroing (given that it doesn't use statictmp).
For the escape analysis, probably related to #18001?

It still uses statictmp probably because CL https://go-review.googlesource.com/c/35261/ doesn't cover array?

That explains why we were using statictmp originally. I don't understand though why s/OASWB/OAS/ would cause us to stop using statictmp though, since it's still an array literal assignment.

For the escape analysis, probably related to #18001?

Yes, that seems to be the same bug.

That explains why we were using statictmp originally. I don't understand though why s/OASWB/OAS/ would cause us to stop using statictmp though, since it's still an array literal assignment.

I replied in your CL.

@cherrymui is this fixed? If not, what remains to be done?

I believe this is fixed. Thanks.
Closing.


[issue/request] Imgur album failures (w/ easy solution)

http://imgur.com/gallery/AlbumName fails for a gallery/album link rip. But if you simply replace "gallery" with "a", and that album will download.

Fixed in 1.1.9 9b09852


VideoView sporadically shows nothing

Describe the bug
VideoView sporadically shows nothing after track is set. In order to minimise explanation this bug is reproduced and reported based on minimal UIKit example. But I also reproduce it  for local track but within flip animation when camera is switched. So seems like issue not due to CollectionView.reloadData(). Reproduction is very sporadic. Sometimes it can be stable as rock, sometimes it shows empty VideoView after a few reloadData calls.
SDK Version
1.1.6
iOS/macOS Version
iPhone SE 2 gen, iOS 15.5
Steps to Reproduce

Download minimal UIKit example (https://github.com/livekit-examples/swift-example-collection)
Switch to commit aa4cb2c (before LiveKit  2.x.x). (can be found in attached screenshots)
Update Livekit to 1.1.6 instead of 0.9.13 (can be found in attached screenshots)
Update server and token (can be found in attached screenshots)
Update bundleID so app can run on your device (can be found in attached screenshots)
Compile and run app
Do some taps on cell and/or do some taps on shuffle button and get empty VideoView (step can be found in attached video)

Expected behavior
VideoView should show video track
Screenshots

https://github.com/livekit/client-sdk-swift/assets/135046095/678e3027-8226-4680-a323-77f979e0d614
Logs
logs_without_server.txt

This is in v1.1.6 ? Can you make sure all access to the VideoView is from the main thread ?

This is in v1.1.6 ?

As far as I can use Xcode and SPM I'd say it is 1.1.6. Logs that I've attached earlier also have line:

2024-03-07T17:05:59+0300 debug LiveKitSDK : [LiveKit] Engine.init(connectOptions:) sdk: 1.1.6, os: iOS(15.5), modelId: iPhone8,4

So seems like yes - it is 1.1.6

Can you make sure all access to the VideoView is from the main thread ?

As for my current project that tries to use LiveKit as a solution to organise Video calls so I can't be sure for 100% as there are many abstraction layers. But minimal example seems to be pretty easy and seems to have access from main thread. Anyway let's go from different side - let's explicitly use background thread and see if something happens. So I changed setFirstVideoTrack to something like:
private func setFirstVideoTrack() {
   DispatchQueue.global(qos: .background).async {
       let track = self.participant?.videoTracks.first?.track as? VideoTrack
       self.videoView.track = track
   }
}

I am a bit confused but it works. I haven't tired to reproduce the issue but tapping on shuffle button or on cell itself still OK. I even set breakpoint and got clarification that self.videoView.track = track was executed from background. Also I slightly dived into track setter and seems like it is executed via _state.mutate and it inside has lock but found no main thread dispatch.
After a careful eyeballing initial logs I found 2 lines that look suspicious to me. Line 608 or thereabout:
2024-03-07T17:06:22+0300 debug LiveKitSDK : [LiveKit] RemoteTrackPublication.onAdaptiveStreamTimer() [adaptiveStream] disabling sid: TR_VCYTsCdRLAHHwh, videoRenderersCount: 0,
2024-03-07T17:06:22+0300 debug LiveKitSDK : [LiveKit] RemoteTrackPublication.onAdaptiveStreamTimer() VideoTrack.shouldReceive: false

Attaching one more log. Same steps - tap on cell or on shuffle button. To make it more obvious I killed app after I got grey video view. So it is easier to extract logs with issue.
002_adaptive_noo_serrver.txt
Line 461 or thereabout also contains suspicious [adaptiveStream] disabling sid. Adding abstract here with extra !!!! to point this 2 suspicious lines:
numberOfItemsInSection...
sizeForItemAt...
prepareForReuse, cellId: 1
2024-03-10T21:40:27+0300 debug LiveKitSDK : [LiveKit] VideoView.init(frame:) isRendering true -> false
2024-03-10T21:40:27+0300 debug LiveKitSDK : [LiveKit] MulticastDelegate<VideoViewDelegate>.notify(label:_:) [notify] videoView.didUpdate isRendering: false
2024-03-10T21:40:27+0300 debug LiveKitSDK : [LiveKit] VideoView.createNativeRendererView(for:) Using RTCMTLVideoView for VideoView's Renderer
2024-03-10T21:40:27+0300 debug LiveKitSDK : [LiveKit] VideoView.createNativeRendererView(for:) preferredFramesPerSecond = 60
2024-03-10T21:40:27+0300 debug LiveKitSDK : [LiveKit] VideoView.init(frame:) rendering cached frame tack: TR_VCkYAZTEF4Z9FE
2024-03-10T21:40:27+0300 debug LiveKitSDK : [LiveKit] MulticastDelegate<TrackDelegate>.notify(label:_:) [notify] track.didAttach videoView: <LiveKit.VideoView: 0x105d2f8d0; frame = (0 0; 160 160); clipsToBounds = YES; layer = <CALayer: 0x281bcb9a0>>
2024-03-10T21:40:27+0300 debug LiveKitSDK : [LiveKit] VideoView.init(frame:) removing nativeRenderer
2024-03-10T21:40:27+0300 debug LiveKitSDK : [LiveKit] MulticastDelegate<TrackDelegate>.notify(label:_:) [notify] track.didDetach videoView: <LiveKit.VideoView: 0x105d2f8d0; frame = (0 0; 160 160); clipsToBounds = YES; layer = <CALayer: 0x281bcb9a0>>
!!!!!!
2024-03-10T21:40:27+0300 debug LiveKitSDK : [LiveKit] RemoteTrackPublication.onAdaptiveStreamTimer() [adaptiveStream] disabling sid: TR_VCkYAZTEF4Z9FE, videoRenderersCount: 0,
2024-03-10T21:40:27+0300 debug LiveKitSDK : [LiveKit] RemoteTrackPublication.onAdaptiveStreamTimer() VideoTrack.shouldReceive: false
!!!!!!
2024-03-10T21:40:27+0300 debug LiveKitSDK : [LiveKit] RemoteTrackPublication.send(trackSettings:) [adaptiveStream] sending TrackSettings(enabled: false, dimensions: Dimensions(0x0), videoQuality: low), sid: TR_VCkYAZTEF4Z9FE
2024-03-10T21:40:27+0300 debug LiveKitSDK : [LiveKit] SignalClient.sendUpdateTrackSettings(sid:settings:) sending track settings... sid: TR_VCkYAZTEF4Z9FE, settings: TrackSettings(enabled: false, dimensions: Dimensions(0x0), videoQuality: low)
2024-03-10T21:40:28+0300 debug LiveKitSDK : [LiveKit] MulticastDelegate<RoomDelegateObjC>.notify(label:_:) [notify] room.didReceive data: 0 bytes
2024-03-10T21:40:28+0300 debug LiveKitSDK : [LiveKit] MulticastDelegate<ParticipantDelegate>.notify(label:_:) [notify] participant.didReceive data: 0 bytes
2024-03-10T21:40:28+0300 debug LiveKitSDK : [LiveKit] VideoView.init(frame:) isRendering true -> false
2024-03-10T21:40:28+0300 debug LiveKitSDK : [LiveKit] MulticastDelegate<VideoViewDelegate>.notify(label:_:) [notify] videoView.didUpdate isRendering: false
2024-03-10T21:40:29+0300 debug LiveKitSDK : [LiveKit] MulticastDelegate<RoomDelegateObjC>.notify(label:_:) [notify] room.didReceive data: 0 bytes
2024-03-10T21:40:29

Hello, do you still see this issue with v2 ?

Alas haven't moved to v2. Still using  v1.1.6.

Hi @hiroshihorie , I'm having similar issue on 2.0.7. Occasionally nothing redered on VideoView for remote participants.
@bombruch 's work-around actually resolves this issue for me too.
This doesn't work
func room(_ room: Room, participant: RemoteParticipant, didSubscribeTrack publication: RemoteTrackPublication) {
    guard let videoTrack = publication.track as? RemoteVideoTrack  else { return }
    DispatchQueue.main.async { [weak self] in
        let videoView = VideoView()
        // setting remote participant's video track on main thread
        videoView.track = videoTrack

        ....

    }
}

but this works.
func room(_ room: Room, participant: RemoteParticipant, didSubscribeTrack publication: RemoteTrackPublication) {
    guard let videoTrack = publication.track as? RemoteVideoTrack  else { return }
    DispatchQueue.main.async { [weak self] in
        let videoView = VideoView()
        // setting remote participant's video track on background thread
        DispatchQueue.global().async {
            videoView.track = videoTrack
        }

        ....

    }
}

Thanks @Yabby1997 for the detailed report, this is interesting and odd...
I've noticed you let videoView = VideoView() in the delegate, can you initialize VideoView somewhere else (but main thread) and try again ?

@hiroshihorie I have the quite similar issue. I found when set videoView.track = nil and set it to a new track, it does not remove the LKRTCVideo, but rendering the new one on the top of that -> It makes so many tracks stack with each other.
First time I think it is the collectionView issue, but after checking around, I think it's not
For my temporary solution. Instead of set videoView.track = nil and set it again, I will remove the videoTrack and intial a new one.
I using the SDK ver 2.0.15


Support data passing and storage on window.name

Support data passing and storage on window.name and fallback to queryParams if window.name is overridden.

Coverage decreased (-5.9%) to 86.104% when pulling 74fa35514d145df2b1c6e3fbd7b4a94b50d7fb54 on shauryakalia:master into eb09b353684315373dd04209214175c804be36ae on wingify:master.


Allow panel routes at root

[x] Changes have been thoroughly tested to not break existing functionality.
[x] New functionality has been documented or existing documentation has been updated to reflect changes.
[x] Visual changes are explained in the PR description using a screenshot/recording of before and after.

Currently, Filaments home route at / overrides any panel routes you register at /, since it's registered in the routes file after the routes you've configured in the panel provider.

Duplicate of many other PRs, we can't do this without other unintended consequences


"Slave_only" config setting not working as expected

Hi @rc0r
So I am trying out the "slave_only" setting as documented. Here's my use case:
$ cat asan.conf
...
"slave_only": true
...
$ cat harden.conf
...
"slave_only": false
...

$ afl-multicore -c harden.conf start 2
$ afl-multicore -c asan.conf add 2

but then I notice 2 sets of master/slave afl instances. I was expecting 1 master/ 1 slave (harden.conf), and 2 slaves (asan.conf). Am I not doing something right?
Thanks!

slave_only was dropped in afl-utils v1.32a (not yet released, but implemented in experimental branch in commit b39c41b) in favor of master_instances. See #36 for details or updated README.md on experimental.
If you're not using the latest version from experimental this may be a real bug.

So for your specific use case, you'd want to change your configs to:
asan.conf:
"master_instances": 1

In the above case you may omit master_instances. If not present, afl-multicore will default to single-master mode.
harden.conf
"master_instances": 0

Thanks a ton. I will update my code accordingly. Another issue I have noticed is that on resuming old slave-only sessions, new afl sync subdirs are created, like so:
# old 1 master (harden.conf) 2 slave-only (asan.conf)
$ ls
HARDEN000 ASAN001 ASAN002
# On afl-multicore -c asan.conf resume 2
$ ls
HARDEN000 ASAN001 ASAN002 ASAN003 ASAN005

I was hoping the resume would reuse old sub dirs. Is this expected?

This is not supposed to happen.
Did you fully terminate the asan fuzzing instances (ASAN001 and ASAN002)?
Another strange thing is that the newly created slaves do not have consecutive job numbers jumping from ASAN003 to ASAN005.
If you're using interactive screen mode, make sure to start afl-multicore from the first window with no other windows present in the current screen session. This should in most cases avoid screen hickups. However I doubt this screen thingy has sth. to do with the problem you're seeing.
If this problem persists, I'd need to setup a minimal config like yours to reproduce the issue.
Thanks for your valuable feedback! :)

Sorry, this was a bug in my code. Turns out, I was doing start followed by resume for the master config but add followed by another add (instead of resume) for the slave config. After the fix, the workflow works as expected :+1:
I am closing this issue...


NO LICENSE, godoc shows no doc

The repo lacks a license file, so godoc does not display the docs.

The repo lacks a license file

It clearly does not.


Issue #321- bound setter support

I have implemented the bound setter feature, please read my comments here:
https://code.google.com/p/projectlombok/issues/detail?id=321
Please get in touch with me to discuss required code changes to get this feature integrated into lombok master branch (e.g. documentation is missing right now).

Apologies that it's taken this long; we've had 'fix existing features' at the top of our todo lists for rather longer than we intended.
This is excellent work, which means another round of apologies are in order because we cannot accept this pull request. After some debate and a review of the joda.beans project, we've concluded, definitively, that we consider the java beans spec beyond salvation and can't reasonably support it.
We've expanded on this a bit at the relevant issue page:
https://code.google.com/p/projectlombok/issues/detail?id=321


OOM during training

Hi, thank you for sharing!
I met OOM problem and my process was killed during training on Linux with 32G memory.
I set the parameter batch_size and eval_batch_size to 32, but the OOM problem remained.
Do you have any suggestions as to what I should do to fix this problem? Or could you share your model parameters that you have trained?

Hi,
I used a batch size of 1000 and it works well on a machine with 60G memory. I guess the issue might comes from the file label_corr.py. Please check if you can run that file.


Respect meta types when doing constant method calls for autocompletion

Fixes #57669

@@ -1756,7 +1760,7 @@ static bool _guess_expression_type(GDScriptParser::CompletionContext &p_context,
 							}
 						}

-						if (native_type.kind == GDScriptParser::DataType::NATIVE) {
+						if (native_type.is_constant && native_type.kind == GDScriptParser::DataType::NATIVE) {
 							MethodBind *mb = ClassDB::get_method(native_type.native_type, call->function_name);
 							if (mb && mb->is_const()) {
 								bool all_is_const = true;

This is needed to fix autocompletion (reduced value is still GDScriptNativeClass metatype):

When doing this we loose any kind of autocompletion on the result of get_script (and probably some other cases which currently work well).
I don't think this is the right place to fix this issue. Seems more like meta types aren't handled properly when listing out the properties.


Files do not get deleted, whenever you group the file field into a Panel

If you group the file / image field into a Panel like this:
Panel::make(__('CompanyInformation'), [
    Image::make(__('Logo'), 'company_logo')->prunable(),
]),

Then the deleteImage method from the SettingsController does not recognize the field, but the panel, which does not has an attribute with the field name:
$field = collect(NovaSettings::getFields($pathName))->firstWhere('attribute', $fieldName);

Cannot overwrite the Controller myself afaik.

Same issue with the eminiarts/nova-tabs field.

Fixed by @marttinnotta  in version 5.1.0. Good luck!


[BUG] [CAMERA] Flutter camera freezes when start recording video on Android

Description
I'm using Flutter camera plugin camera: ^0.5.4+1. For some reason, my camera freezes when I start recording video.
This is the error I'm getting.
I/flutter (28050): startVideoRecording
I/RequestQueue(28050): Repeating capture request cancelled.
I/CameraDeviceState(28050): Legacy camera service transitioning to state IDLE
E/CameraDevice-0-LE(28050): Surface with size (w=3840, h=2160) and format 0x22 is not valid, size not in valid set: [2048x1536, 1920x1440, 2048x1080, 1920x1080, 2560x800, 1440x1080, 1280x960, 1280x720, 1280x480, 1280x400, 864x480, 640x640, 800x480, 720x480, 768x432, 640x480, 576x432, 640x360, 480x360, 480x320, 384x288, 352x288, 320x240, 240x160, 176x144, 160x120]
E/CameraDevice-0-LE(28050): submitRequestList - cannot use a surface that wasn't configured
E/MediaRecorder(28050): stop called in an invalid state: 8
I/flutter (28050): Error: videoRecordingFailed
I/flutter (28050): Error Message: null

Here is my code of start and stop video recording. The same code use to work before but it's not working now.
Future<String> startVideoRecording() async {
    print('startVideoRecording');
    if (!_controller.value.isInitialized) {
      return null;
    }
    setState(() {
      _isRecording = true;
    });
    _timerKey.currentState.startTimer();

    final Directory extDir = await getApplicationDocumentsDirectory();
    final String dirPath = '${extDir.path}/Videos/Post';
    await Directory(dirPath).create(recursive: true);
    final String filePath = '$dirPath/${_timestamp()}.mp4';

    if (_controller.value.isRecordingVideo) {
      // A recording is already started, do nothing.
      return null;
    }

    try {
      videoPath = filePath;
      await _controller.startVideoRecording(filePath);
    } on CameraException catch (e) {
      _showCameraException(e);
      return null;
    }
    return filePath;
  }

  Future<void> stopVideoRecording() async {
    if (!_controller.value.isRecordingVideo) {
      return null;
    }
    _timerKey.currentState.stopTimer();
    setState(() {
      _isRecording = false;
    });

    try {
      await _controller.stopVideoRecording();
    } on CameraException catch (e) {
      _showCameraException(e);
      return null;
    }
  }

Logs
flutter doctor -v
[✓] Flutter (Channel stable, v1.9.1+hotfix.2, on Mac OS X 10.14.6 18G87, locale en-IN)
    • Flutter version 1.9.1+hotfix.2 at /Users/divyanshub024/Softwares/flutter
    • Framework revision 2d2a1ffec9 (8 days ago), 2019-09-06 18:39:49 -0700
    • Engine revision b863200c37
    • Dart version 2.5.0

[!] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/divyanshub024/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • ANDROID_HOME = /Users/divyanshub024/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    ! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses

[✓] Xcode - develop for iOS and macOS (Xcode 10.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.3, Build version 10G8
    • CocoaPods version 1.7.1

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 39.0.3
    • Dart plugin version 191.8423
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[✓] IntelliJ IDEA Community Edition (version 2018.3.4)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 32.0.3
    • Dart plugin version 183.5429.25

[✓] Connected device (1 available)
    • ASUS X00TD • J7AAGF01H563MZA • android-arm64 • Android 9 (API 28)

! Doctor found issues in 1 category.

Facing similar error on one of my test Samsung phone (GT N7100) . I have also tried the example flutter camera app (camera: ^0.5.4+1) but it freezes and the recorded video is also corrupted.
Logs when recording started:
I/RequestQueue(21539): Repeating capture request cancelled.
I/CameraDeviceState(21539): Legacy camera service transitioning to state IDLE
I/CameraDeviceState(21539): Legacy camera service transitioning to state CONFIGURING
I/RequestThread-1(21539): Configure outputs: 2 surfaces configured.
D/Camera  (21539): app passed NULL surface
I/CameraDeviceState(21539): Legacy camera service transitioning to state IDLE
W/art     (21539): Long monitor contention event with owner method=void java.lang.Object.wait!() from Object.java:4294967294 waiters=0 for 235ms
I/RequestQueue(21539): Repeating capture request set.
W/LegacyRequestMapper(21539): convertRequestMetadata - control.awbRegions setting is not supported, ignoring value
I/CameraDeviceState(21539): Legacy camera service transitioning to state CAPTURING

At this point the surface is working, I can see things moving.

Logs after recording stopped
E/[EGL-ERROR](21539): void __egl_platform_dequeue_buffer(egl_surface*):1618: failed to dequeue buffer from native window (0x530ae438); err = -19, buf = 0x0,max_allowed_dequeued_buffers 3
E/[EGL-ERROR](21539): void __egl_platform_dequeue_buffer(egl_surface*):1618: failed to dequeue buffer from native window (0x530ae438); err = -19, buf = 0x0,max_allowed_dequeued_buffers 3
E/[EGL-ERROR](21539): void __egl_platform_dequeue_buffer(egl_surface*):1618: failed to dequeue buffer from native window (0x530ae438); err = -19, buf = 0x0,max_allowed_dequeued_buffers 3
E/[EGL-ERROR](21539): void __egl_platform_dequeue_buffer(egl_surface*):1618: failed to dequeue buffer from native window (0x530ae438); err = -19, buf = 0x0,max_allowed_dequeued_buffers 3
E/CameraDeviceGLThread-1(21539): Received exception on GL render thread:
E/CameraDeviceGLThread-1(21539): java.lang.IllegalStateException: swapBuffers: EGL error: 0x300d
E/CameraDeviceGLThread-1(21539): 	at android.hardware.camera2.legacy.SurfaceTextureRenderer.checkEglError(SurfaceTextureRenderer.java:544)
E/CameraDeviceGLThread-1(21539): 	at android.hardware.camera2.legacy.SurfaceTextureRenderer.swapBuffers(SurfaceTextureRenderer.java:537)
E/CameraDeviceGLThread-1(21539): 	at android.hardware.camera2.legacy.SurfaceTextureRenderer.drawIntoSurfaces(SurfaceTextureRenderer.java:741)
E/CameraDeviceGLThread-1(21539): 	at android.hardware.camera2.legacy.GLThreadManager$1.handleMessage(GLThreadManager.java:105)
E/CameraDeviceGLThread-1(21539): 	at android.os.Handler.dispatchMessage(Handler.java:98)
E/CameraDeviceGLThread-1(21539): 	at android.os.Looper.loop(Looper.java:148)
E/CameraDeviceGLThread-1(21539): 	at android.os.HandlerThread.run(HandlerThread.java:61)
I/CameraDeviceState(21539): Legacy camera service transitioning to state ERROR
E/CameraCaptureSession(21539): Session 1: Exception while stopping repeating:
E/CameraCaptureSession(21539): android.hardware.camera2.CameraAccessException: The camera device has encountered a serious error
E/CameraCaptureSession(21539): 	at android.hardware.camera2.impl.CameraDeviceImpl.checkIfCameraClosedOrInError(CameraDeviceImpl.java:2000)
E/CameraCaptureSession(21539): 	at android.hardware.camera2.impl.CameraDeviceImpl.stopRepeating(CameraDeviceImpl.java:913)
E/CameraCaptureSession(21539): 	at android.hardware.camera2.impl.CameraCaptureSessionImpl.close(CameraCaptureSessionImpl.java:378)
E/CameraCaptureSession(21539): 	at io.flutter.plugins.camera.Camera.closeCaptureSession(Camera.java:508)
E/CameraCaptureSession(21539): 	at io.flutter.plugins.camera.Camera.createCaptureSession(Camera.java:304)
E/CameraCaptureSession(21539): 	at io.flutter.plugins.camera.Camera.createCaptureSession(Camera.java:297)
E/CameraCaptureSession(21539): 	at io.flutter.plugins.camera.Camera.startPreview(Camera.java:436)
E/CameraCaptureSession(21539): 	at io.flutter.plugins.camera.Camera.stopVideoRecording(Camera.java:385)
E/CameraCaptureSession(21539): 	at io.flutter.plugins.camera.CameraPlugin.onMethodCall(CameraPlugin.java:112)
E/CameraCaptureSession(21539): 	at io.flutter.plugin.common.MethodChannel$IncomingMethodCallHandler.onMessage(MethodChannel.java:222)
E/CameraCaptureSession(21539): 	at io.flutter.embedding.engine.dart.DartMessenger.handleMessageFromDart(DartMessenger.java:96)
E/CameraCaptureSession(21539): 	at io.flutter.embedding.engine.FlutterJNI.handlePlatformMessage(FlutterJNI.java:643)
E/CameraCaptureSession(21539): 	at android.os.MessageQueue.nativePollOnce(Native Method)
E/CameraCaptureSession(21539): 	at android.os.MessageQueue.next(MessageQueue.java:323)
E/CameraCaptureSession(21539): 	at android.os.Looper.loop(Looper.java:135)
E/CameraCaptureSession(21539): 	at android.app.ActivityThread.main(ActivityThread.java:5461)
E/CameraCaptureSession(21539): 	at java.lang.reflect.Method.invoke(Native Method)
E/CameraCaptureSession(21539): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
E/CameraCaptureSession(21539): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
I/flutter (21539): Error: videoRecordingFailed
I/flutter (21539): Error Message: The camera device has encountered a serious error
E/RequestThread-1(21539): Timed out while waiting for request to complete.
W/CaptureCollector(21539): Preview buffers dropped for request: 1
E/CameraDeviceState(21539): Cannot receive result while in state: 0
E/CameraDeviceState(21539): Cannot receive result while in state: 0
E/CameraDeviceState(21539): Cannot receive result while in state: 0
E/BufferQueueProducer(21539): [SurfaceTexture-1-21539-31] queueBuffer: BufferQueue has been abandoned

After recording stopped the surface freezes.

Flutter doctor:
[√] Flutter (Channel stable, v1.7.8+hotfix.3, on Microsoft Windows [Version 10.0.17763.737], locale en-IN)
    • Flutter version 1.7.8+hotfix.3 at C:\Users\heysu\Documents\flutter
    • Framework revision b712a172f9 (2 months ago), 2019-07-09 13:14:38 -0700
    • Engine revision 54ad777fd2
    • Dart version 2.4.0

[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at C:\Users\heysu\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
    • All Android licenses accepted.

[√] Android Studio (version 3.5)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 38.2.3
    • Dart plugin version 191.8423
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)

[√] VS Code (version 1.38.1)
    • VS Code at C:\Users\heysu\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.4.1

[√] Connected device (1 available)
    • GT N7100 • 4df7985e7bf1cf25 • android-arm • Android 6.0.1 (API 23)

And the above error comes which @divyanshub024 mentioned is  when the ResolutionPreset is high on the CameraController.
 controller = CameraController(
      cameraDescription,
      ResolutionPreset.high,  //This is high
      enableAudio: enableAudio,
    );

Error Logs:
I/RequestQueue(21539): Repeating capture request cancelled.
I/CameraDeviceState(21539): Legacy camera service transitioning to state IDLE
E/CameraDevice-1-LE(21539): Surface with size (w=1280, h=720) and format 0x1 is not valid, size not in valid set: [704x704, 640x480, 320x320, 320x240]
W/CameraDevice-JV-1(21539): Stream configuration failed
E/CameraCaptureSession(21539): Session 1: Failed to create capture session; configuration failed
E/MediaRecorder(21539): stop called in an invalid state: 8
I/flutter (21539): Error: videoRecordingFailed
I/flutter (21539): Error Message: null

All this occurred on Samsung  (GT N7100) as far I have tested.

The same for Pixel 3 with Android Q onboard...

I'm having the same freeze for Pixel 3 with Android Q onboard...

@troy379 have you tried low or medium settings?

@Sp4Rx Yes, I've tried the medium one and got the same behavior

For me, it works when ResolutionPreset is medium.

I hope you're not suggesting decreasing the resolution preset is the correct way to counter this bug @divyanshub024
This is something that happens after migrating to the new embedding. I don't know why yet but I'm hopeful @matthew-carroll or someone else from the Flutter team will figure it out. On my Note 10+ it freezes after a couple of seconds moving the camera around. Until this is properly fixed, I guess you need to roll back to a commit before the new embedding commits.
E/CameraCaptureSession( 5749): Session 1: Exception while stopping repeating:
E/CameraCaptureSession( 5749): android.hardware.camera2.CameraAccessException: CAMERA_ERROR (3): The camera device has encountered a serious error
E/CameraCaptureSession( 5749): 	at android.hardware.camera2.impl.CameraDeviceImpl.checkIfCameraClosedOrInError(CameraDeviceImpl.java:2435)
E/CameraCaptureSession( 5749): 	at android.hardware.camera2.impl.CameraDeviceImpl.stopRepeating(CameraDeviceImpl.java:1126)
E/CameraCaptureSession( 5749): 	at android.hardware.camera2.impl.CameraCaptureSessionImpl.close(CameraCaptureSessionImpl.java:526)
E/CameraCaptureSession( 5749): 	at io.flutter.plugins.camera.Camera.closeCaptureSession(Camera.java:539)
E/CameraCaptureSession( 5749): 	at io.flutter.plugins.camera.Camera.close(Camera.java:545)
E/CameraCaptureSession( 5749): 	at io.flutter.plugins.camera.Camera$2.onError(Camera.java:203)
E/CameraCaptureSession( 5749): 	at android.hardware.camera2.impl.CameraDeviceImpl$CameraDeviceCallbacks.notifyError(CameraDeviceImpl.java:1929)
E/CameraCaptureSession( 5749): 	at android.hardware.camera2.impl.CameraDeviceImpl$CameraDeviceCallbacks.lambda$Sm85frAzwGZVMAK-NE_gwckYXVQ(Unknown Source:0)
E/CameraCaptureSession( 5749): 	at android.hardware.camera2.impl.-$$Lambda$CameraDeviceImpl$CameraDeviceCallbacks$Sm85frAzwGZVMAK-NE_gwckYXVQ.accept(Unknown Source:8)
E/CameraCaptureSession( 5749): 	at com.android.internal.util.function.pooled.PooledLambdaImpl.doInvoke(PooledLambdaImpl.java:258)
E/CameraCaptureSession( 5749): 	at com.android.internal.util.function.pooled.PooledLambdaImpl.invoke(PooledLambdaImpl.java:182)
E/CameraCaptureSession( 5749): 	at com.android.internal.util.function.pooled.OmniFunction.run(OmniFunction.java:77)
E/CameraCaptureSession( 5749): 	at android.os.Handler.handleCallback(Handler.java:873)
E/CameraCaptureSession( 5749): 	at android.os.Handler.dispatchMessage(Handler.java:99)
E/CameraCaptureSession( 5749): 	at android.os.Looper.loop(Looper.java:216)
E/CameraCaptureSession( 5749): 	at android.app.ActivityThread.main(ActivityThread.java:7263)
E/CameraCaptureSession( 5749): 	at java.lang.reflect.Method.invoke(Native Method)
E/CameraCaptureSession( 5749): 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:494)
E/CameraCaptureSession( 5749): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:975)
E/BufferQueueProducer( 5749): [ImageReader-1280x720f23m2-5749-1] dequeueBuffer: attempting to exceed the max dequeued buffer count (9)

@bparrishMines do you happen to know anything about this bug? Do you know if the migrated plugin suffers from this?

@matthew-carroll @PerLycke It looks like this was reported before the plugin was migrated. I can test it on previous versions to see where it started misbehaving. It may be caused by adding pause and resume functionality or by the resolution fix by @mklim.

Ok thanks. I did exactly this now to reproduce the issue:
Run ml_vision example package together with latest camera source. In the example app I selected CameraPreviewScanner. Took just a couple of seconds for everything to freeze.
Tested on the Note 10+.
Btw, we have a production app in store with camera sources up to 86d245f7efdf0a9043dc975f039bc94a28b26529 with no issues, so it's not the commits you mention @bparrishMines , but something after that.

@bparrishMines It seems like a different issue from the one OP encountered, I'm not completely sure why I ended up posting it here. I hope my steps to reproduce it above makes sense though. Should I open a new issue?

Actually never mind. The ml_vision camera streaming seems broken in unmodified state on the Note 10+. I reverted back the camera plugin 6 months and it's still broken, so no recent commits is the cause.
We do some lifting of heavy camera tasks to background thread in our production app, and it's working when having these patches.
Sorry that I didn't spend more time debugging before coming to this conclusion, I thought the ml_vision / camera streaming was working out of the box.
Bottom line: ml_vision camera streaming is not working on the Note 10+.

I'm having the same issue as OP, on a Xiaomi A1.
My device can take full HD videos, but when using the flutter camera plugin, any resolution above "medium" causes the the camera to freeze, with the exception ...and format 0x22 is not valid, size not in valid set:...
From doing a bit of online research, it seems that the cause is flutter camera plugin's usage of android's Camera2 API, which many android devices don't support.
I've tested Camera(1) API on the same device and it can record full HD videos.
I've come across this library which implements a good fallback to the old Camera API when necessary: https://github.com/infinum/Android-GoldenEye
It might be a good direction to follow for solving this problem within the flutter camera plugin.

After Updating to the latest version (in this case :  0.5.7+4) the video recording works fine for ResolutionPreset.high , but for the ultraHigh , veryHigh and max it doesn't freeze but instead of that it stretches the camera .

same here

Same issue as OP. Any updates on this flutter team? Camera plugin is turning out to be a real pain and roadblock in using flutter for a production app!

Hi Team,
any update on this issue.

Same here, stop recording always encountered error :
Error Message: Failed to configure camera session
I'm just using Example from camera plugin.

Same problem. Did anyone find any workarounds?

I also have it in IOS

When will you solve the damn problem?

Facing same issue on different devices.
ResolutionPreset is max

Emulator with API R:
Aspect ratio: 0.5625
Size: 1280 X 720
Front camera: CameraPreview working and Video records as expected. ✅
Rear camera: CameraPreview freezes and video corrupted.❌

Xiaomi Mi A2 with android 10:
Aspect ratio: 0.5625
Size: 1280 X 720
Front camera: CameraPreview working and Video records as expected.✅
Rear camera: CameraPreview freezes and video corrupted.❌

Xiaomi Redmi 5A with Android 8.1:
Aspect ratio: 0.5625
Size: 1280 X 720
Front camera: CameraPreview freezes, video corrupted, and image preview was weird.❌
Rear camera: CameraPreview freezes and video corrupted.❌

Camera is core feature that many apps use, this needs to fix ASAP.

Has a solution occurred about this problem?

I can't think of anything other than migrating to image_picker :(

Has a solution occurred about this problem?

Image capturing and video recording working as expected with medium resolution on emulator and two other devices I tested.
If quality is not your priority then you can try this option, else image picker is the way.

I am testing in Asus Zenfone Max 3 and All Presets are not working
Flutter Doctor
[✓] Flutter (Channel stable, 1.22.2, on Mac OS X 10.15.7 19H2, locale en-PH)
    • Flutter version 1.22.2 at /Users/zonilyjamepesquera/flutter
    • Framework revision 84f3d28555 (12 days ago), 2020-10-15 16:26:19 -0700
    • Engine revision b8752bbfff
    • Dart version 2.10.2

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/zonilyjamepesquera/Library/Android/sdk
    • Platform android-29, build-tools 29.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.1, Build version 12A7403
    • CocoaPods version 1.9.3

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 49.0.2
    • Dart plugin version 193.7547
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.50.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.15.1

[✓] Connected device (3 available)
    • Redmi 7 (mobile)      • 118af079                  • android-arm64 • Android 9 (API 28)
    • ASUS X00DDA (mobile)  • H4AXHM03W879CD5           • android-arm64 • Android 8.1.0 (API 27)
    • TempuraPhone (mobile) • 00008030-001925DE3C12802E • ios           • iOS 14.0.1

Other Info

Redmi 7 (mobile) - Works fine
ASUS X00DDA (mobile) - is the Zenfome Max 3 and doesn't work at all
TempuraPhone (mobile) - Works fine

Hey @kuyazee could you check this solution? Its a hacky one though
https://github.com/flutter/flutter/issues/41370

I have a small freeze when i start or stop recording videos with every resolution setting.
Used device: Samsung S9

I am trying to reproduce the issue mentioned by the OP but having a hard time doing so on the current version (0.6.3+2). I am trying to reproduce it using the [camera example] App and tested on the following devices (all I have available at the moment):

Samsung Galaxy S6 (SM-G900F);
LG Nexus 5X;
Emulator (Android Q and R).

Can anyone confirm this issue is still happening in the latest versions of the plugin? If so could you supply some information on the device you are testing on (make/ model/ Android version)?

Hi @mvanbeusekom ,
I have upgraded camera plugin from 0.5.7+3 => 0.6.3+2 as suggested. Then I tried the example code provided in camera plugin example page .
After running the on my emulator (Android 11 - API R) I couldn't see the camera preview at all instead I see a message Tap a Camera, even I tried to change cameras from front and rear.
I also tested this on the physical device Xiaomi Redmi 5A (Android 8.0) and found the same issue, the Screen showing Tap a Camera.
As said I tried to click on the radio button to change the cameras from rear to front and vice versa but, not working.
All the permissions were granted for the application, required to access the camera. By downgrading to 0.5.7+3, I was able to access the camera in the same application.

Hi @mvanbeusekom ,
I have upgraded camera plugin from 0.5.7+3 => 0.6.3+2 as suggested. Then I tried the example code provided in camera plugin example page .
After running the on my emulator (Android 11 - API R) I couldn't see the camera preview at all instead I see a message Tap a Camera, even I tried to change cameras from front and rear.
I also tested this on the physical device Xiaomi Redmi 5A (Android 8.0) and found the same issue, the Screen showing Tap a Camera.
As said I tried to click on the radio button to change the cameras from rear to front and vice versa but, not working.
All the permissions were granted for the application, required to access the camera. By downgrading to 0.5.7+3, I was able to access the camera in the same application.

Hi @harshapulikollu,
This can happen when you have run flutter pub upgrade. Due to an unfortunate configuration error in the camera 0.6.3+2 release it depends on the wrong version of the camera_platform_interface package which contains a breaking change. This has already been fixed in master but hasn't been published yet.
To work around this issue you can add a dependency override to your pubspec.yaml file and run a flutter pub get command:
  dependency_overrides:
    camera_platform_interface: ">=1.0.4 <1.1.0"

See also issue #73091 for more details.

Hi @harshapulikollu,
This can happen when you have run flutter pub upgrade. Due to an unfortunate configuration error in the camera 0.6.3+2 release it depends on the wrong version of the camera_platform_interface package which contains a breaking change. This has already been fixed in master but hasn't been published yet.
To work around this issue you can add a dependency override to your pubspec.yaml file and run a flutter pub get command:
  dependency_overrides:
    camera_platform_interface: ">=1.0.4 <1.1.0"

See also issue #73091 for more details.

Hi @mvanbeusekom,
Thank you for the suggestion, I added the dependency overrides and now with the camera update(0.6.3+2) version able to access the video and tested the video recording.
It's working as expected on the device( Xiaomi Redmi 5A) and that initially wasn't working.

Hi @mvanbeusekom,
Thank you for the suggestion, I added the dependency overrides and now with the camera update(0.6.3+2) version able to access the video and tested the video recording.
It's working as expected on the device( Xiaomi Redmi 5A) and that initially wasn't working.

@harshapulikollu thank you very much for confirming it now works on the Xiaomi Redmi 5A, that is very helpful to know.
@divyanshub024, it's been a long time since you posted this issue, but noticed you are still active in the community, could you maybe confirm if this is still an issue on the latest version of the camera plugin?

@harshapulikollu thank you very much for confirming it now works on the Xiaomi Redmi 5A, that is very helpful to know.
@divyanshub024, it's been a long time since you posted this issue, but noticed you are still active in the community, could you maybe confirm if this is still an issue on the latest version of the camera plugin?

Hey @mvanbeusekom!! Looks like this issue does not occur on the latest version. I'm closing this issue. If anyone faces this issue again then we'll reopen this issue.
Thanks!!

Hey @mvanbeusekom!! Looks like this issue does not occur on the latest version. I'm closing this issue. If anyone faces this issue again then we'll reopen this issue.
Thanks!!

Thanks a lot @divyanshub024!

Thanks a lot @divyanshub024!

I am still facing this issue. bug log is as:
I/flutter ( 3986): Error: camera initialized
I/RequestQueue( 3986): Repeating capture request cancelled.
I/RequestQueue( 3986): Repeating capture request set.
W/LegacyRequestMapper( 3986): convertRequestMetadata - control.awbRegions setting is not supported, ignoring value
W/LegacyRequestMapper( 3986): mapAeAndFlashMode - Ignore control.aeMode == ON_AUTO_FLASH;camera does not support it
W/LegacyRequestMapper( 3986): convertRequestToMetadata - Ignoring android.lens.focusDistance false, only 0.0f is supported
I/art     ( 3986): Do partial code cache collection, code=60KB, data=61KB
I/art     ( 3986): After code cache collection, code=60KB, data=61KB
I/art     ( 3986): Increasing code cache capacity to 256KB
D/AndroidRuntime( 3986): Shutting down VM
E/AndroidRuntime( 3986): FATAL EXCEPTION: main
E/AndroidRuntime( 3986): Process: com.example.whatsupflutter, PID: 3986
E/AndroidRuntime( 3986): java.lang.NullPointerException: Attempt to invoke virtual method 'int java.lang.Enum.ordinal()' on a null object reference
E/AndroidRuntime( 3986): 	at io.flutter.plugins.camera.DeviceOrientationManager.getMediaOrientation(DeviceOrientationManager.java:60)
E/AndroidRuntime( 3986): 	at io.flutter.plugins.camera.DeviceOrientationManager.getMediaOrientation(DeviceOrientationManager.java:55)
E/AndroidRuntime( 3986): 	at io.flutter.plugins.camera.Camera.runPictureCapture(Camera.java:552)
E/AndroidRuntime( 3986): 	at io.flutter.plugins.camera.Camera.access$1500(Camera.java:73)
E/AndroidRuntime( 3986): 	at io.flutter.plugins.camera.Camera$3.processCapture(Camera.java:510)
E/AndroidRuntime( 3986): 	at io.flutter.plugins.camera.Camera$3.onCaptureCompleted(Camera.java:442)
E/AndroidRuntime( 3986): 	at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime( 3986): 	at android.hardware.camera2.dispatch.InvokeDispatcher.dispatch(InvokeDispatcher.java:39)
E/AndroidRuntime( 3986): 	at android.hardware.camera2.dispatch.HandlerDispatcher$1.run(HandlerDispatcher.java:65)
E/AndroidRuntime( 3986): 	at android.os.Handler.handleCallback(Handler.java:754)
E/AndroidRuntime( 3986): 	at android.os.Handler.dispatchMessage(Handler.java:95)
E/AndroidRuntime( 3986): 	at android.os.Looper.loop(Looper.java:165)
E/AndroidRuntime( 3986): 	at android.app.ActivityThread.main(ActivityThread.java:6375)
E/AndroidRuntime( 3986): 	at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime( 3986): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:912)
E/AndroidRuntime( 3986): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:802)
I/Process ( 3986): Sending signal. PID: 3986 SIG: 9
Lost connection to device.
Exited (sigterm)

@kamleshwebtech could you please share some more information on your environment? The following information would be very helpful:

The version of the camera plugin you are using;
The output of flutter doctor -v command;

@mvanbeusekom  I am new to flutter and the camera plugin but I think I am hitting the same issue.  I am using the camera version 0.7.0+2. The camera preview works fine in the emulator by on my device Sony XPeria F5321 (mobile)  android-arm64 • Android 8.0.0 (API 26) it errors with the follow and doesn't show the preview. I can create a new issue if that is easier to manager please let me know @mvanbeusekom
The error I am getting is
E/CameraCaptureSession(18550): Session 0: Exception while stopping repeating:
E/CameraCaptureSession(18550): android.hardware.camera2.CameraAccessException: CAMERA_ERROR (3): The camera device has encountered a serious error
E/CameraCaptureSession(18550): 	at android.hardware.camera2.impl.CameraDeviceImpl.checkIfCameraClosedOrInError(CameraDeviceImpl.java:2220)
E/CameraCaptureSession(18550): 	at android.hardware.camera2.impl.CameraDeviceImpl.stopRepeating(CameraDeviceImpl.java:993)
E/CameraCaptureSession(18550): 	at android.hardware.camera2.impl.CameraCaptureSessionImpl.close(CameraCaptureSessionImpl.java:391)
E/CameraCaptureSession(18550): 	at io.flutter.plugins.camera.Camera.closeCaptureSession(Camera.java:1147)
E/CameraCaptureSession(18550): 	at io.flutter.plugins.camera.Camera.close(Camera.java:1153)
E/CameraCaptureSession(18550): 	at io.flutter.plugins.camera.Camera$1.onError(Camera.java:247)
E/CameraCaptureSession(18550): 	at android.hardware.camera2.impl.CameraDeviceImpl$CameraDeviceCallbacks$1.run(CameraDeviceImpl.java:1791)
E/CameraCaptureSession(18550): 	at android.os.Handler.handleCallback(Handler.java:789)
E/CameraCaptureSession(18550): 	at android.os.Handler.dispatchMessage(Handler.java:98)
E/CameraCaptureSession(18550): 	at android.os.Looper.loop(Looper.java:251)
E/CameraCaptureSession(18550): 	at android.app.ActivityThread.main(ActivityThread.java:6589)
E/CameraCaptureSession(18550): 	at java.lang.reflect.Method.invoke(Native Method)
E/CameraCaptureSession(18550): 	at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:240)
E/CameraCaptureSession(18550): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:767)
I/zygote64(18550): Thread[3,tid=18564,WaitingInMainSignalCatcherLoop,Thread*=0x720a0c4400,peer=0x17dc05e8,"Signal Catcher"]: reacting to signal 3
I/zygote64(18550):
I/zygote64(18550): Wrote mini stack traces to '/data/anr/traces.txt.mini'
I/zygote64(18550): Wrote stack traces to '/data/anr/traces.txt'
E/FirebaseInstanceId(18550): binding to the service failed

Flutter Doctor Output
[√] Flutter (Channel stable, 1.22.6, on Microsoft Windows [Version 10.0.19042.789], locale en-US)
    • Flutter version 1.22.6 at C:\dev\flutter
    • Framework revision 9b2d32b605 (2 weeks ago), 2021-01-22 14:36:39 -0800
    • Engine revision 2f0af37152
    • Dart version 2.10.5

[√] Android toolchain - develop for Android devices (Android SDK version 30.0.1)
    • Android SDK at C:\Users\mmanela\AppData\Local\Android\sdk
    • Platform android-30, build-tools 30.0.1
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[!] Android Studio (version 4.1.0)
    • Android Studio at C:\Program Files\Android\Android Studio
    X Flutter plugin not installed; this adds Flutter specific functionality.
    X Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

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

[√] Connected device (2 available)
    • F5321 (mobile)                     • BH903K6A5P    • android-arm64 • Android 8.0.0 (API 26)
    • Android SDK built for x86 (mobile) • emulator-5554 • android-x86   • Android 10 (API 29) (emulator)

! Doctor found issues in 1 category.

I face the same error with a Samsung SM J730G.
This issue should be reopened.
E/CameraCaptureSession(13206): Session 1: Exception while stopping repeating: E/CameraCaptureSession(13206): android.hardware.camera2.CameraAccessException: CAMERA_ERROR (3): The camera device has encountered a serious error E/CameraCaptureSession(13206): 	at android.hardware.camera2.impl.CameraDeviceImpl.checkIfCameraClosedOrInError(CameraDeviceImpl.java:2219) E/CameraCaptureSession(13206): 	at android.hardware.camera2.impl.CameraDeviceImpl.stopRepeating(CameraDeviceImpl.java:1003) E/CameraCaptureSession(13206): 	at android.hardware.camera2.impl.CameraCaptureSessionImpl.close(CameraCaptureSessionImpl.java:394) E/CameraCaptureSession(13206): 	at io.flutter.plugins.camera.Camera.closeCaptureSession(Camera.java:1171) E/CameraCaptureSession(13206): 	at io.flutter.plugins.camera.Camera.close(Camera.java:1177) E/CameraCaptureSession(13206): 	at io.flutter.plugins.camera.Camera$1.onError(Camera.java:252) E/CameraCaptureSession(13206): 	at android.hardware.camera2.impl.CameraDeviceImpl$11.run(CameraDeviceImpl.java:2251) E/CameraCaptureSession(13206): 	at android.os.Handler.handleCallback(Handler.java:790) E/CameraCaptureSession(13206): 	at android.os.Handler.dispatchMessage(Handler.java:99) E/CameraCaptureSession(13206): 	at android.os.Looper.loop(Looper.java:164) E/CameraCaptureSession(13206): 	at android.app.ActivityThread.main(ActivityThread.java:7000) E/CameraCaptureSession(13206): 	at java.lang.reflect.Method.invoke(Native Method) E/CameraCaptureSession(13206): 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:441) E/CameraCaptureSession(13206): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1408)

It seems that this issue going to be fixed with this PR: #3651


Unable to select brackets for link title in markdown

This problem still occurs even if you disable all extensions.

Unable to select brackets for [link title] in markdown
When creating a link, the brackets surrounding a link title do not seem to be recognized well.
Similarly, the same symptom occurs when pasting an image.
I often use editor.action.selectToBracket to select inside brackets, but currently I can't select inside brackets surrounding link title with this command.
[Example Domain](http://example.com/)

This behavior is the same when a link is created as follows:
[Example Domain][link]

[link]: http://example.com/

Example of running:
I want to select the link title Example Domain, but the URL is selected.
Changing the link title is a bit annoying because I can't select contents of the brackets.

Also, "editor.bracketPairColorization.enabled": true is set, but brackets surrounding link title are not highlighted.
Sample image:

I reported this issue to Markdown All in One as an extension problem, but it was pointed out that it may be a problem in VS Code, so I reported it here.

https://github.com/yzhang-gh/vscode-markdown/issues/1063

Version

OS
Windows10 x64 21H1

VS Code version
1.62.1

Installed extensions version

Extension
Version

alefragnani.project-manager
12.4.0

BriteSnow.vscode-toggle-quotes
0.3.5

James-Yu.latex-workshop
8.22.0

MS-CEINTL.vscode-language-pack-ja
1.62.4

ms-vscode.cpptools
1.7.1

oderwat.indent-rainbow
8.2.2

patricklee.vsnotes
0.7.1

shd101wyy.markdown-preview-enhanced
0.6.1

TakumiI.markdowntable
0.7.2

tamasfe.even-better-toml
0.14.2

yzhang.dictionary-completion
1.1.2

yzhang.markdown-all-in-one
3.4.0

zokugun.explicit-folding
0.20.0

Not sure whether related.
Currently, the command editor.action.jumpToBracket not work for Markdown link nor wikilink.
I am not insider. Would the latest version cover this problem?
repro
Given Markdown like:
aaa [bbb] ccc
[[foobar]]
xxx [yyy] zzz

if cursor is before the ]], the command would pin the cursor at the center of ]].
if cursor is after the ]], the command would do nothing.
if removed [[foobar]], the command would do nothing.

version info
Version: 1.63.2 (user setup)
Commit: 899d46d82c4c95423fb7e10e68eba52050e30ba3
Date: 2021-12-15T09:40:02.816Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.19043

Tested when all extensions disabled.
Tested the setting editor.language.brackets for any of following:

  "[md]": { "editor.language.brackets": [ ["[",   "]"],               ], },

  "[md]": { "editor.language.brackets": [ ["[[", "]]"],               ], },

  "[md]": { "editor.language.brackets": [ ["[[", "]]"], ["[",   "]"], ], },

without this setting


Extend logging and error reporting

Summary
This PR introduces two changes (both should improve usability):
1. ProviderRs232: Be more verbose about correct device in error case
QtSerialPort accepts only certain names as SerialPort devices, not
paths. Guessing this names can be cumbersome so give some hint in the
log, if the given device name cannot be detected.
2. webconfig: better error description, if Kodi is not found
Even if the normal Kodi webinterface is activated and capable of
receiving JSON RPC calls (on port 8080), the js in Hyperion sets the
port to 9090 (normally only accessible via localhost). Since the js code
is executed on the users device, Kodi denies access even if Hyperion and
Kodi are installed on the same device.
This change helps in this situation by pointing to the correct Kodi setting.
Unfortunately, I'm only able to modify English and German.
What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Docs
[ ] Build-related changes
[x] Other, please describe:
maybe improved usability?

If changing the UI of web configuration, please provide the before/after screenshot:
I will hand in later.
Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing setups:
The PR fulfills these requirements:

[ ] When resolving a specific issue, it's referenced in the PR's body (e.g. Fixes: #xxx[,#xxx], where "xxx" is the issue number)

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature
[ ] Related documents have been updated (docs/docs/en)
[ ] Related tests have been updated

PLEASE DON'T FORGET TO ADD YOUR CHANGES TO CHANGELOG.MD

[ ] Yes, CHANGELOG.md is also updated

To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.
Other information:

@gerion0 Thanks for your contribution!
In spirit of the idea, I rearrange the output a bit that information provided is per single log-line.
This will help readability, given that other components update the log in parallel.
As a side-note, I am currently working on a change, which will present the user the available serial devices for selection.

More to come soon....

@gerion0 Thanks for your contribution!
In spirit of the idea, I rearrange the output a bit that information provided is per single log-line.
This will help readability, given that other components update the log in parallel.
As a side-note, I am currently working on a change, which will present the user the available serial devices for selection.

More to come soon....


v2 protocols MUST expect any of the attachment formats

Currently the issue credential v2 protocol expects the attachments to always use base64 encoding although the RFCs mention it can be any of the formats (json, base64, links + sha).
From the issue credential v2 RFC:

Any of the 0017-attachments RFC embedded inline attachments can be used. In the examples below, base64 is used in most cases, but implementations MUST expect any of the formats.

And the present proof v2 RFC:

The messages that include ~attach attachments may use any form of the embedded attachment. In the examples below, the forms of the attachment are arbitrary.

@sklump maybe something to take into account for present proof v2? Otherwise we'll make sure to adjust this when adding the new format.

I'll take it on this week


Use float instead of np.float alias

The confusing np.float alias has been deprecated since 1.20 and removed in 1.24, see
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated

Ended  up force-pushing to remove the evidence that this branch ever existed due to missing one of the np.float changes somehow...


regenerate nginx default.conf

to sync with zebrunner/mcloud#181 we have to add new location rule for nginx. it menase during upgrade this file should be regenerated

done. testing scenario should include:

setup from master (v2.2)
do basic acceptance executing api/web jobs
switch to develop and do recursive pull git pull --recurse-submodules
./zebrunner.sh update
do again basic acceptance after restart

to confirm nginx regenertion make sure all subcomponent are available: jenkins, stf, sonar


Add .zshrc and Oh My Zsh

These will need to be added in a sane way, so that they can be included in the setup script.

This is almost finished.

Resolved in 9605df645701dfa489629e77c669e96ac69f3f0c for Oh My Zsh and in<PHONE_NUMBER>ef6a0af53d4e544dd9f5017ac54abe for .zshrc.


Redesign Hexa

some additional pieces to consider when adding new Backup/ Security screens to Hexa from HexaPay

As backup is now simpler it does not need its own tab and can go into settings. (Similar to HexaPay. Though there is no profile needed in Hexa at this point). We are only considering Seed Words and Cloud Backup at this point and not Keeper.
2.When there is a alert from the backup for health check, the CTA is driven from the messages on the screen. And the user directly lands on the backup history page with the relevant CTA to confirm the backup
3.In the settings the user will have the option of “Wallet Backup”. When no setup is done it will give the option of choosing one (like in Hexa Pay).
4.And when one is set up, it will show the history page of that backup e.g. Seed Backup or Cloud Backup. With CTAs to Change (to the other option) or to Confirm the backup.
5.The tab space available now, needs to be used for Gifts which is hidden away in the F&F tab. And needs to be taken away from the F&F tab.
So the tabs will be Home, F&F, Gifts and Settings.
Have also Shared the flows
Check Image for reference

https://xd.adobe.com/view/2883dbb1-761e-4f51-91ae-4f76114e8fdb-7dd0/