The Release versions Wiki has wrong versions

The following wiki is creating a new section for each new patch, so version 3.3.5 is not inside version 3.3, but inside version 3.5, which doesn't exist.
https://github.com/flutter/flutter/wiki/Hotfixes-to-the-Stable-Channel

The latest hot-fix section 3.3.5 now correctly shows under 3.3 changes as below:
https://github.com/flutter/flutter/wiki/Hotfixes-to-the-Stable-Channel#flutter-33-changes
I think when you opened this issue, it might be showing that way, but seem to have been fixed since.
Closing. If you disagree, write in comments and I'll reopen it.


Clearing cookies on every exit

I encountered a problem where ungoogled-chromium would clear out all of my data and cookies on exit, due to an option in settings.

This option is turned off by default in regular Chrome, but enabled by default in ungoogled-chromium. Which file of ungooged-chromium source do I have to modify so that it is disabled by default? I've been trying to figure this one out for a while.

You can disable it once and this setting will be persisted for that particular profile for the future.

You can disable it once and this setting will be persisted for that particular profile for the future.

Yes, but given that I constantly have to create new profiles and switch to them, it is very uncomfortable to disable it every time. Plus if I miss it one time, all of the cookies are gone and that's very frustrating. That's why I am searching particularly for a way to disable it in the source code

You probably need to remove or revert ungoogled-chromium/patches/extra/iridium-browser/prefs-only-keep-cookies-until-exit.patch
If you're compiling it yourself, just removing this line should suffice:
https://github.com/Eloston/ungoogled-chromium/blob/e46b774c538cb8e1e249fe69e3e8d62c18f8c1b9/patches/series#L55

You probably need to remove or revert ungoogled-chromium/patches/extra/iridium-browser/prefs-only-keep-cookies-until-exit.patch
If you're compiling it yourself, just removing this line should suffice:
https://github.com/Eloston/ungoogled-chromium/blob/e46b774c538cb8e1e249fe69e3e8d62c18f8c1b9/patches/series#L55

Yep, that helped. Thanks


eq-parser initial MCI schema

What
First version of the json needed for MCI
How to test
Please check the format
_Who
Anyone but @LJBabbage

For example: https://github.com/ONSdigital/eq-survey-runner/blob/master/app/main/data.json#L98

I though that the response in this schema is equivalent to your field?

You're right, I confused myself there.
LGTM :+1:

Actually no, I do think fields are still relevant as they do have attributes that are possibly author-able such as validation messages or stuff that restricts user input, etc

@hamishtaplin there is no longer a one-to-one mapping between questionnaire responses and the html fields used to collect them.  Where a particular html widget needs additional authorable elements supplied to the html widget, it makes sense if we design and name a particular response type which can then contain the neccessary fields.
For simple response types (such as integer) there are attributes of the response that are implied by the type (e.g. non zero, whole number, numeric characters only allowed) that won't need additional labels displayed, but will effect the input control created in the front end.
For things like the date range "type", there will be additional fields, and perhaps the notion of conditional display that we discussed the other day, but we can cross that bridge when we get to it and will obviously need to have a discussion with you.

Can we change the encompassing folder to be called surveys - json doesn't mean anything apart from the format.

@hamishtaplin @weapdiv-david - I think you're talking at cross purposes, the field is still relevant at a schema model level, it's just not implemented here as it's a presentational decision about how a date field for example is presented. The form question then reassembles those field values into a single answer that is mapped to a statistical variable for downstream processing.


ffmpeg segment_times options

Problem/Use Case
splitting without transcoding results in segments overlaping at begining and ending.
Solutions
ffmpeg segment_times option
segment_times times

    Specify a list of split points. times contains a list of comma separated duration specifications, in increasing order. See also the segment_time option.

Proposed Implementation:
scenedetect just provide those split points, and let ffmpeg do the segment job.
Alternatives:
List any alternative solutions or related ideas you've considered.
Examples:
Attach or link to any relevant videos or images that are relevant.

Without transcoding, isn't this the same as running ffmpeg several times with -c:v copy -c:a copy?

I'm a noob about ffmpeg, since it's so complicated. But I'm sure the segment muxer won't output overlapping segments.

Likewise, could definitely use some guidance on the proper way to go about this.  That being said, in the latest version of PySceneDetect, you can configure the output of the cutting list to whatever format you want (frames, seconds, etc...).  You should be able to use that as the input to ffmpeg for this purpose.
Does that work?  You can customize the output of PySceneDetect so you can pipe the output into another command as well.l

Can you try that, and let me know if that works? And if so, what command line arguments you are using?
I'd love to, but not now, maybe a fews days later.

I took a glance at split_video_ffmpeg code, and saw it's using -ss <start> -i <input> -t <duration> without -avoid_negative_ts 1. That maybe the cause I think.
https://trac.ffmpeg.org/wiki/Seeking#Cuttingsmallsections

If you cut with stream copy (-c copy) you need to use the -avoid_negative_ts 1 option if you want to use that segment with the concat demuxer .

Yes, I'm using that concat demuxer, and I see overlapping in the concat output.


Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c4ded2ce-d8c3-7118-bec9-865f6225dbe0
Version Independent ID: a4089752-177c-866c-7237-3ac02c7750d9
Content: Dependency Tracking in Azure Application Insights - Azure Monitor
Content Source: articles/azure-monitor/app/asp-net-dependencies.md
Service: azure-monitor
Sub-service: application-insights
GitHub Login: @lgayhardt
Microsoft Alias: lagayhar

@benjamin-goldman Thanks for your question. We are checking on this and will respond to you soon.

Assigning this issue to our document author @lgayhardt to further evaluate the feedback. Thank you

@MicrosoftDocs/azure-cxp-triage This isn't a doc-bug it is a doc-enhancement request. There is nothing technically incorrect about the recommendation that if a dependency is not tracked automatically you can either not track it, or you can track it manually. The suggested linked content is still effectively manually tracking the dependency albeit with a different pattern/syntax that may prove useful in certain scenarios.
The currently linked content also provides context for manually tracking dependencies across all the languages the SDKs currently support whereas the suggested article provides context only for .NET. While .NET has the TelemetryClient.StartOperation available the other SDKs don't. I think perhaps a more productive fix that would address the concerns from this issue would be to leave this article as-is and instead add a Note at the top of this section of the TrackDependency API doc: api-custom-events-metrics.md#trackdependency that cross links to the suggested page. There is absolutely value in .NET customers  having awareness of the TelemetryClient.StartOperation extension method as an option for dependency tracking, but there is also a reason why we are linking to the generic API article which also has much greater reach from a pageview/SEO perspective.

The following has been added to the dependency section of the API doc and will go live later today:

#please-close


Does MSFT rotate the credentials of the Service Principals behind the Managed Identity?

As one of our requirement, the credentials need to be frequently rotated. Does Azure rotate the service principal credentials behind managed identities?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 72861cc1-7081-cf6e-b7f9-e700a16faa9a
Version Independent ID: c870872d-0559-6b77-280f-f478e8c84776
Content: Managed identities for Azure resources
Content Source: articles/active-directory/managed-identities-azure-resources/overview.md
Service: active-directory
Sub-service: msi
GitHub Login: @MarkusVi
Microsoft Alias: markvi

@CharmanderJieniJieni Thanks for your feedback! We will investigate and update as appropriate.

@CharmanderJieniJieni No, once the managed identity is created it is tied to the resource till the resource is deleted or managed identity is turned off from Azure portal.

Thanks, does this apply to both system-assigned or user-assigned managed
identity?
On Thu, Apr 9, 2020 at 4:44 PM SaurabhSharma-MSFT<EMAIL_ADDRESS>wrote:

@CharmanderJieniJieni https://github.com/CharmanderJieniJieni No, once
the managed identity is created it is tied to the resource till the
resource is deleted or managed identity is turned off from Azure portal.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/52087#issuecomment-611743605,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFPUB5GCG4WGWMASQDP5WELRLYXSVANCNFSM4MEZMHRQ
.

@CharmanderJieniJieni yes, Azure does not rotate the credentials for both System and User assigned managed identities.

Thanks. Does it use password or certificate to authenticate in backend? This is important information and would you please make sure the document mention this?

@CharmanderJieniJieni Sorry, my apologies, I thought of service principals rotation in Managed Identities and the answer is Yes for the credential rotation as it is managed in the background and whenever a UserAssigned or SystemAssigned Identity is created, the Managed Identity Resource Provider (MSRP) issues a certificate to that identity. The default rotation occurs every 46 days and credential rotation is controlled by the resource provider that hosts the Azure resource. It's up to the resource provider to call for new credentials, so the resource provider could wait longer than 45 days.
Please refer to document to know how the managed identities for Azure resources work.

Thanks. This is important reference for us, could you update it somewhere in the document?

@CharmanderJieniJieni Sure, I have submitted a PR to update the documentation and it will be merged once approved by the document author. Thanks again for pointing this out, I am closing the issue based on this update, please let us know if there is something else that we can help you with.

This conversation was very helpful :) I have a follow-up question: You mention that the default rotations occurs every 46 days, and that it can be changed/controlled by the resource provider. If a user-assigned managed identity is being used by multiple resource providers (e.g. Function App & DevTest Lab), then which resource provider would control the rotation period?


Added timer controller to remove duplicate offers

:tada: This PR is included in version 2.0.5 :tada:
Your semantic-release bot :package::rocket:


[xtest] no fail fast, and lcov support

Motivation
replace code_coverage.sh script which takes a very long time due to massive recompilation, with a call to xtest.
Seems to save about 2-3 hours of computation.
Capture failed tests and send them to slack.
Fixed up xtest to not fail fast, but instead still generate coverage reports if the xtest run ends in errors.
xtest now supports lcov as well with --html-lcov-dir.
the lcov.info file will get generated to that dir as well as the html report based on lcov.
Have you read the [Contributing Guidelines on pull requests]
Yes
Test Plan
Run in a test-1 branch with the once a day gating logic turned off....
Here's a coverage run:
https://app.circleci.com/pipelines/github/libra/libra/32146/workflows/570bd495-9afb-4eb8-b64d-d1d985580e08/jobs/227368
Here's my latest test run with the test reporting baked in, and running the test-suite as well.
https://app.circleci.com/pipelines/github/libra/libra/32177/workflows/1aef8d46-623e-4f9f-9e40-2b3888418de7/jobs/227680
Need to check slack when it's done to verify the message, though I tested the shell locally with a different, less time consuming command.
Related PRs
None.

So a full 4 h 58 min run succeed today.
https://app.circleci.com/pipelines/github/libra/libra/32306/workflows/aeff4077-c2fa-46ad-b33f-9e29148c4c43/jobs/228889
Coverage reported at
Overall coverage rate:
lines......: 80.4% (98013 of 121855 lines)
functions..: 16.6% (59851 of 359478 functions)
This run in 2 hrs 4min
https://app.circleci.com/pipelines/github/libra/libra/32341/workflows/4e38ae2d-ff4f-485e-96ef-f06390598c00/jobs/229198
Overall coverage rate:
lines......: 77.7% (99606 of 128206 lines)
functions..: 34.4% (37750 of 109625 functions)
Compiling crates individually vs compiling them together.  Larger code coverage difference than I'd expect, but looks like the number of functions generated 3.5 times less.
Updated movelang doc.

also the use of piping to a tee breaks in circleci and hangs indefinitely.   Good times.

/land

also the use of piping to a tee breaks in circleci and hangs indefinitely. Good times.

I'm glad that you were able to figure out what the root cause of that hang was, and i'm glad it wasn't actually anything in our tooling (e.g. x)


Search initial prototype

Linked delivery tickets

#99

Search now available at
https://data.youthfuturesfoundation.org/search/


Main Gauche

Lowering energy of sinister strike aspect of main gauche is not working. Ty for your work <3

Fixed in #895


Trouble with coding, version latest from dockerhub.

Trouble with coding, version latest from dockerhub. Please help me. Thanks

As redis does not have any information about string encodings there is no way to select the appropriate one if its not UTF-8. Or to tell if its really a string or binary. Redis wont tell you. The UI has to guess.
For binary data special handling is implemented for string type only so far. Nothing for set/list/hash/...

closed due of missing feedback


Passing BranchName environment variable to the CI-Action Pipeline build stage.

Hello,
Thanks for putting this together, it's just what I need right now!
I noticed that the BranchName was always set to 'master' in the CI-Action (and other actions as well) stage of the pipeline.
Here is how to reproduce:

Create the 'develop' branch.
Check the pipeline actions build outputs and you will see the echo of the BranchName which is 'master'. Should be 'develop'. This is true for any branch creation, the build output always says 'master'.

I was able to fix by adding an 'EnvironmentVariables' section to the CI-Action:
    - Name: Continuous-Integration
      Actions:
        - Name: CI-Action
          ActionTypeId:
            Category: Build
            Owner: AWS
            Version: "1"
            Provider: CodeBuild
          OutputArtifacts:
            - Name: CIAction
          InputArtifacts:
            - Name: Source
          Configuration:
            ProjectName: !Join ['-', [!Ref 'RepositoryName', 'CIAction' ]]
            EnvironmentVariables: !Sub "[{\"name\":\"BranchName\",\"value\":\"${BranchName}\",\"type\":\"PLAINTEXT\"}]"
          RunOrder: 1

Note that this is not the CIAction Codebuild project which does have the EnvironmentVariables set. This is the Action defined under Codepipeline.

I have also observed same issue  of BranchName always master in CodeBuild EnvironmentVariables section. is there any alternate solution for this. please let me know.


[Feature] Legend selectedMode to keep at least one active

What problem does this feature solve?
When all series are disabled from legend chart looks empty and even y-axis disappears.
https://echarts.apache.org/examples/en/editor.html?c=line-stack - disable all series from legend

What does the proposed API look like?
Add one more option to selectedMode(inside legend) which disables unselecting last active series.
legend: {
selectedMode: 'atLeastOne'
}

This will be very useful if done!