Chrome too fast for images

I've had trouble getting the plugin to work with chrome. The images are not loaded before the _callPrint function is called and Chrome is so quick that the images are not picked up in the preview.
The code inside function _printElement:
_callPrint(popupOrIframe);
..should be delayed until content of documentToWriteTo is done loading. The following fixed the problem:
REPLACE:
documentToWriteTo.open();
documentToWriteTo.write(html);
documentToWriteTo.close();
_callPrint(popupOrIframe);
WITH:
documentToWriteTo.onload = _callPrint(popupOrIframe);
documentToWriteTo.open();
documentToWriteTo.write(html);
documentToWriteTo.close();
..and the _callPrint function is called right after all content has been loaded inside the documentToWriteTo window document.
Note: code sequence does matter

We solved this issue for our needs by modifying that function with a settimeout:
function _callPrint(element) {
if (element && element.printPage) {
/* compumatter inserted code. IE displayed blank page every time if no delay was inserted
this was because 'print' was getting ahead of the iframe content being filled' */
setTimeout(function () {
element.printPage();
}, 50);
}
else {
setTimeout(function () {
_callPrint(element);
}, 50);
}
}


DOC: Adding more info button at the below of the each container in blogs option

What's wrong with the existing documentation
There is no specific button to go and refer the information of the content present in blogs in specific. Hence i can add MoreInfo button at the below of the each container so that the user can identify that more brief information is available for ecah topics.
Add ScreenShots
No response
Record

[X] I agree to follow this project's Code of Conduct
[x] I'm a GSSOC'24 contributor
[X] I want to work on this issue

This feature is not required right now.


Tab header for Debugger Errors doesn't reset correctly in editor.

Godot version
master d6f972fad45d28222b1437a047241dd74f0d5b90
System information
Windows 10
Issue description
After running the debugger from the editor and encountering errors/warnings you are left with a tab header highlighting that fact:

Clicking on it opens the debugger tab (dock?), which again highlights the errors/warnings from the debug session:

Clicking the "Clear" button removes the errors from the list, but does not reset the headers:

Hitting "Clear" while the debugger session is still running correctly clears those headers.
Steps to reproduce
See description.
Minimal reproduction project
This should happen for any project. It happens in all the projects I tried this.

I don’t think that this issue was fully fixed. I’m running Godot 4.0 alpha 2 and the number in the bottom panel still doesn’t go away.

Can confirm the number doesn't go away in alpha1 or alpha2

I'm testing alpha 4 and the issue seems to still be there

The problematic code is here:
https://github.com/godotengine/godot/blob/3dac7ff876edae8398cb0f3f27ec0bc68f1bbb8e/editor/debugger/editor_debugger_node.cpp#L278-L303
This is executed in NOTIFICATION_PROCESS, when debugging server is active (i.e. the project is running).


FluentFunctions visitEvent should be deprecated and foldEvent alternative provided

Slated for remove in Cyclops 12.

Released in 10.1.0


(BOLT-1412) Only process task_options for tasks/plans

When running a script there could be positional script arguments that contain = characters. Previously, regardless of the subcommand the cli parser would try to extract task_options by splitting arguments on the = character. This commit updates the parser to only attepmt to built a task_options hash if a task or plan is being run.

CLA signed by all contributors.

Works locally for me!


swift-hash showing 3 contributors, but it only has 1?

Which package(s) are showing incorrect data?

swift-hash

Please explain what data is incorrect and what you expected to see
the page for swift-hash shows “Written by kelvin13 and 2 other contributors”, but (unfortunately) i don’t remember anyone besides me contributing to it?

The default display is based on unique committer names in git history. It's likely there's a couple more in there that you were not aware of. You can run git shortlog to see them.
You can also customise this string completely.
More details here: https://blog.swiftpackageindex.com/posts/recognising-package-authors

Just checked and this is the output of the shortlog on the repo:
    30  kelvin13<EMAIL_ADDRESS>    15  taylorswift<EMAIL_ADDRESS>     1  kelvin<EMAIL_ADDRESS>
It would appear that the same email is being used, but the git username changed at some point (perhaps using different machines, or different GUIs with different configurations).
@daveverwer Is there any desire (one way or another) to dedupe/group based on email?

ah that makes sense, thanks dave!

@daveverwer Is there any desire (one way or another) to dedupe/group based on email?

We could, but then we'd need to make a decision about what name to use, and that's all just more steps down potentially getting it wrong.
We have a mechanism for correcting the automated detection. Unless it becomes a bigger issue, I think we're good for now. 👍


[CLI] Add --show-origin option to extensions list

Fixes https://github.com/microsoft/vscode/issues/196155
This PR add to the --list-extensions command (in the extension management CLI) an option --show-origin that return the origin of each extension while listing them.
It will allow external tools that use this command to parse this result and distinguish between:

Released extensions in the marketplace
Prerelease extensions from the marketplace
Not published (i.e. vscx) extensions

Example of return:
$ ./scripts/code-cli.sh --list-extensions --show-origin
ms-python.python (prerelease)
ms-python.vscode-pylance (marketplace)
vscode-sampless.helloworld-sample (vscx)

This is also compatible with --show-versions argument:
$ ./scripts/code-cli.sh --list-extensions --show-versions --show-origin
<EMAIL_ADDRESS>(prerelease)
<EMAIL_ADDRESS>(marketplace)
<EMAIL_ADDRESS>(vscx)

This have been linted using yarn and tested with the provided test.sh script.

@microsoft-github-policy-service agree

The associated feature is only asking whether the extension is a pre-release or not. Please stick to that.

The associated feature is only asking whether the extension is a pre-release or not. Please stick to that.

Quoting the issue https://github.com/microsoft/vscode/issues/196155:
The feature should be used to distinguish between different extension types.
In particular, it needs to distinguish between extensions:
1. From the marketplace (published)
    - Release
    - Pre-release
 2. Not published

From that quotes I have no doubts this PR is sticking to the issue description.

Thanks for sharing the info. I did not read that comment. Summary and Description says only about the pre-release. Lets stick to that. I would not go with extension type.


Hey @Romi904, I would like to add Check Valid Parenthesis problem code in java, can you please assign that task to me as my Hacktoberfest2022 PR.

The hacktoberfest team has made it clear that maintainers should no longer accept DSA projects or contributions.


Feature/yaxlib visual studio debugger friendly

Hi YAXLib team.
I want to use your fantastic library in my Object Dumper extension for Visual Studio.
Experimental version of extension
What is done in this PR:

Get rid of Lazy & ThreadLocal as they do impossible using this serializer in Visual Studio Debugger extension  "The function evaluation requires all threads to run"

Add the DontSerializeDefaultValues option to YAXSerializationOptions (the algo was taken from Json.Net)

Add the TypeResolver to SerializerOptions.cs (allows type name and members customization without attributes)

MemberWrapperCache and UdtWrapperCache: cache the type by type and SerializerOptions.

Fixed failing tests: if choose Get_PooledObject and Parallel_Load_On_Specialized_Pools and run them only, the Parallel_Load_On_Specialized_Pools will fail.

Hi Yevhen
Thanks for the PR. It includes very nice improvements, while it's really huge and will require some time process.
For the moment, YAXLib team has only 1 member left ;-) so you're welcome to join.
Breaking changes

Yet I'm not aware of all, but the PR includes a couple of breaking changes. Please kindly name the breaking changes introduced in the PR description.
We had significant breaking changes over last months. So for the sake of other YAXLib users, we should be cautious. Is there a way to avoid or reduce them?

Few things that I came across when going throw the code for the first time:

SonarCloud Quality Gate fails for the PR. Please have a look at the Sonar Summary in terms of Maintainability and Coverage.
Well written XmlDoc is useful for users and maintainers. I was trying hard to get what we currently have, and it should not become less.

Naming conventions

Clearly, YAXLib does not follow the common naming convention for types. We should not mix Yax... and YAX... prefixes.
YAXLib 4.x still has few abbreviations used in member names. DoNot is preferred over Dont. In the past it was left as is to avoid a breaking change.

What do you think - does this make sense to you?

Hi @axunonb,
Thanks for the review.
I will try to fix the SonarCloud Quality Gate fails.
I don't clearly understand what you mean when say "breaking changes" - all the functional tests left untouched. The only thing that could be impacted is Default cache sizes. I mean if it was previously cached by Type only but now caches by Type and SerializerOptions, that means that cache will be filled faster for use cases when serialization/deserialization occurs with multiple SerializerOptions.

Hi @axunonb,
I know about WellKnownTypes and used it for the DateTimeOffset serialization.
But, unfortunately, it doesn't allow for skipping members at runtime
In opposition to WellKnownTypes, it provides full control over serialization in runtime, not design time.
It can be a NamingPolicy or even customization of builtin type as DateTime, which is unavailable by defining KnownType.

Thanks! WellKnownTypes can be added/removed at runtime. Skipping members at runtime is the missing feature, I agree, same as the NamingPolicy delegate. I like these two, but still would prefer to have these features in the known types instead of SerializerOptions, because they are actually type-specific. This should be possible.
As you mentioned built-in types like DateTime. You are right, this is an unnecessary limitation. Better move (part of) the logic in ReflectionUtils.ConvertBasicType(...) to the known types / known base types? DateTimeOffset should be a built-in known type, too, same as with DateOnly or TimeOnly which I added in v4.1.0.

Thanks! WellKnownTypes can be added/removed at runtime. Skipping members at runtime is the missing feature, I agree, same as the NamingPolicy delegate. I like these two, but still would prefer to have these features in the known types instead of SerializerOptions, because they are actually type-specific. This should be possible.
As you mentioned built-in types like DateTime. You are right, this is an unnecessary limitation. Better move (part of) the logic in ReflectionUtils.ConvertBasicType(...) to the known types / known base types? DateTimeOffset and IpAddress should be a built-in known type, too, same as with DateOnly or TimeOnly which I added in v4.1.0.

Agree with you that DateTime as KnownType, the Naming policy implemented in YaxLib sounds like a good plan!
Currently, ITypeInfoResolver can help cover features not yet implemented.
Could you rerun the SonarCloud checks?

Thanks! WellKnownTypes can be added/removed at runtime. Skipping members at runtime is the missing feature, I agree, same as the NamingPolicy delegate. I like these two, but still would prefer to have these features in the known types instead of SerializerOptions, because they are actually type-specific. This should be possible.
As you mentioned built-in types like DateTime. You are right, this is an unnecessary limitation. Better move (part of) the logic in ReflectionUtils.ConvertBasicType(...) to the known types / known base types? DateTimeOffset and IpAddress should be a built-in known type, too, same as with DateOnly or TimeOnly which I added in v4.1.0.

Agree with you that DateTime as KnownType, the Naming policy implemented in YaxLib sounds like a good plan! Currently, ITypeInfoResolver can help cover features not yet implemented. Could you rerun the SonarCloud checks?

Would you like to put further changes into this PR?
Another option would be a new branch version/v-next as intermediate step.

I need some time to refine the code of current PR. No new features. Just code polishing.

@axunonb Can we add NetFramework 4.5 support to this PR?

Hi Yevhen,
As I can see you're still refactoring the YAXLib codebase. Having a glance at the 2 recent commits, I'd say you're introducing concepts to the better. For me it would be helpful to identify the target outcome of the PR more clearly, also having current users of YAXLib in mind. Maybe we could define a project which includes more steps to reach the goal, eventually publishing new versions on the way. Would be nice if you shared your thoughts.

Guess, I've already finished this PR. The goal of the two last commits was to make the usage of ITypeInspector easy and do it similarly to Json.NET.ContractResolver or YamlDotNet.TypeInspectorSkeleton

OK. Not a problem. Agree with you.

Yup, agree with you. I would also add the KeyValuePair to known types.


CF Release

Updates
Added

cf-typography: [patch] Note in usage docs about unused italic and demi fonts.

Changed

cf-core: [patch] Fix OL padding-left so numbers aren't cut off in IE
cf-forms: [patch] Updated cf-buttons dependency to v5.0.0
cf-icons: [patch] Make minor improvements to usage doc
cf-pagination: [patch] Updated cf-buttons dependency to v5.0.0
capital-framework: [patch] Updates babel-loader to ^7.1.4,
uglifyjs-webpack-plugin to ^1.2.2, webpack-stream to ^4.0.2.

Removed

cf-core: [patch] Removed text-shadow hack to fix inconsistent demibold font weight in Chrome and other browsers.

Review

@cfpb/front-end-team-admin

I am a bot
After this PR is merged, I will instruct Travis to automagically perform the following steps:

Increment Capital Framework's version per our guidelines.
Add a timestamped entry to the changelog with the new version and its changes.
Tag the release and push it to GitHub.
Publish both capital-framework and any individually updated components to npm.
Update both canary, our development branch, and master, our release branch.

If I do something wrong, blame a human.

MERGE IT


failed to require "moment/locale/fa"

Hi,
I have problem with initial moment-jalaali error me:
Uncaught Error: failed to require "moment/locale/fa"
    at require (moment-jalaali.js:14)
    at moment-jalaali.js:322
    at require (moment-jalaali.js:18)
    at moment-jalaali.js:1224
    at moment-jalaali.js:1226

What should I do?

I use it as bellow.
<script src="/modules/moment/moment.min.js"></script>
<script src="/modules/moment-jalaali/build/moment-jalaali.js"></script>

@behrang This is related to the build system, not the code. I think this needs your attention.

Seems to be related to #134. I changed build script a little. Someone please test the result after  pulling from master.

after add this code
<script src="/plugins/moment/moment.min.js"></script>
<script src="/plugins/moment-jalaali/build/moment-jalaali.js"></script>

error me again:
Uncaught Error: failed to require "../moment"
    at require (moment-jalaali.js:14)
    at symbolMap.1 (moment-jalaali.js:318)
    at moment-jalaali.js:321
    at require (moment-jalaali.js:18)
    at moment-jalaali.js:426
    at require (moment-jalaali.js:18)
    at moment-jalaali.js:1328
    at moment-jalaali.js:1330
require @ moment-jalaali.js:14
symbolMap.1 @ moment-jalaali.js:318
(anonymous) @ moment-jalaali.js:321
require @ moment-jalaali.js:18
(anonymous) @ moment-jalaali.js:426
require @ moment-jalaali.js:18
(anonymous) @ moment-jalaali.js:1328
(anonymous) @ moment-jalaali.js:1330

In #134 this line is added:
require('moment/locale/fa')

Inside fa module, there is a line for requiring ../moment. So that is going to work in node.js environment, unless we also define ../moment.
In #138 that require line is removed. So that fixes the problem.
Also I built the standalone version again, so it includes the removal of that require statement.
It should be fixed now. I close this. Feel free to open it again if anyone find any problems.


Update hive-apache-jdbc to 0.13.1-7

related to https://github.com/prestosql/presto-hive-jdbc/pull/2

I don't think upgrading libthrift is safe, as the generated code, such as for the metastore client, is dependent on the version of the library. Why do we want to upgrade?


Declaring logError as function instead of arrow function.

Fixes #680

I've added tests to this PR.

Thanks @DKvistgaard


Role Assignment fails with ARM template if principalId is of userAssignedIdentities

Document Ref: https://docs.microsoft.com/en-us/azure/role-based-access-control/role-assignments-template
Note:
This template is not idempotent unless the same roleNameGuid value is provided as a parameter for each deployment of the template. If no roleNameGuid is provided, by default a new GUID is generated on each deployment and subsequent deployments will fail with a Conflict: RoleAssignmentExists error.
This does not seem to hold true when principalId is of providers/Microsoft.ManagedIdentity/userAssignedIdentities
"error": {
"code": "RoleAssignmentExists",
"message": "The role assignment already exists."
}
Example Snippet, cannot be run multiple times, even though Name (roleNameGuid ) stays constant. This seems to be specific to userAssignedIdentities as I have multiple roleAssignments that can be re-deployed if roleNameGuid stays constant.
        {
          "name": "abe3c3a0-aaf3-488e-b09e-bcd40958f757",
          "type": "Microsoft.Authorization/roleAssignments",
          "apiVersion": "2020-04-01-preview",
          "properties": {
            "roleDefinitionId": "[subscriptionResourceId('Microsoft.Authorization/roleDefinitions', 'b24988ac-6180-42a0-ab88-20f7382dd24c')]",
            "principalId": "[reference('/subscriptions/576c0000-1111-2222-3333-b36204bf7e09/resourceGroups/demo01-dev-regrp-core-we/providers/Microsoft.ManagedIdentity/userAssignedIdentities/demo01-dev-usrai-core-we', '2018-11-30').principalId]",
            "scope": "[subscriptionResourceId('Microsoft.Resources/resourceGroups', 'demo01-dev-regrp-core-we')]"
          },
          "condition": true,
          "resources": []
        }

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

ID: 8788e944-1b89-9f78-4c7c-409092e073e5
Version Independent ID: 7484bf47-59da-5eaf-17c3-ccaecf45f185
Content: Add Azure role assignments using Azure Resource Manager templates - Azure RBAC
Content Source: articles/role-based-access-control/role-assignments-template.md
Service: role-based-access-control
GitHub Login: @rolyon
Microsoft Alias: rolyon

Thanks for the Comment. We are actively investigating and will get back to you soon.

Hi @dirkslab, I reproduced this scenario in my account and here are the steps that I followed:

I created 2 different Managed Identities.

I ran below template to give Contributor  role to Managed Identity 1:

{
    "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
    "contentVersion": "<IP_ADDRESS>",
    "parameters": {
        "principalId": {
            "type": "string",
            "metadata": {
                "description": "The principal to assign the role to"
            }
        },
        "builtInRoleType": {
            "type": "string",
            "allowedValues": [
                "Owner",
                "Contributor",
                "Reader"
            ],
            "metadata": {
                "description": "Built-in role to assign"
            }
        },
        "roleNameGuid": {
            "type": "string",
            "defaultValue": "8e3af657-a8ff-443c-a75c-2fe8c4bcb636",
            "metadata": {
                "description": "A new GUID used to identify the role assignment"
            }
        }
    },
    "variables": {
        "Owner": "[concat('/subscriptions/', subscription().subscriptionId, '/providers/Microsoft.Authorization/roleDefinitions/', '8e3af657-a8ff-443c-a75c-2fe8c4bcb635')]",
        "Contributor": "[concat('/subscriptions/', subscription().subscriptionId, '/providers/Microsoft.Authorization/roleDefinitions/', 'b24988ac-6180-42a0-ab88-20f7382dd24c')]",
        "Reader": "[concat('/subscriptions/', subscription().subscriptionId, '/providers/Microsoft.Authorization/roleDefinitions/', 'acdd72a7-3385-48ef-bd42-f606fba81ae7')]"
    },
    "resources": [
        {
            "type": "Microsoft.Authorization/roleAssignments",
            "apiVersion": "2018-09-01-preview",
            "name": "[parameters('roleNameGuid')]",
            "properties": {
                "roleDefinitionId": "[variables(parameters('builtInRoleType'))]",
                "principalId": "[reference('/subscriptions/b83********************************c23f/resourceGroups/********/providers/Microsoft.ManagedIdentity/userAssignedIdentities/test-gh-67839', '2018-11-30').principalId]"
            }
        }
    ]
}

This was successful.

I ran below template to give Contributor role to Managed Identity 2:

{
    "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
    "contentVersion": "<IP_ADDRESS>",
    "parameters": {
        "principalId": {
            "type": "string",
            "metadata": {
                "description": "The principal to assign the role to"
            }
        },
        "builtInRoleType": {
            "type": "string",
            "allowedValues": [
                "Owner",
                "Contributor",
                "Reader"
            ],
            "metadata": {
                "description": "Built-in role to assign"
            }
        },
        "roleNameGuid": {
            "type": "string",
            "defaultValue": "8e3af657-a8ff-443c-a75c-2fe8c4bcb636",
            "metadata": {
                "description": "A new GUID used to identify the role assignment"
            }
        }
    },
    "variables": {
        "Owner": "[concat('/subscriptions/', subscription().subscriptionId, '/providers/Microsoft.Authorization/roleDefinitions/', '8e3af657-a8ff-443c-a75c-2fe8c4bcb635')]",
        "Contributor": "[concat('/subscriptions/', subscription().subscriptionId, '/providers/Microsoft.Authorization/roleDefinitions/', 'b24988ac-6180-42a0-ab88-20f7382dd24c')]",
        "Reader": "[concat('/subscriptions/', subscription().subscriptionId, '/providers/Microsoft.Authorization/roleDefinitions/', 'acdd72a7-3385-48ef-bd42-f606fba81ae7')]"
    },
    "resources": [
        {
            "type": "Microsoft.Authorization/roleAssignments",
            "apiVersion": "2018-09-01-preview",
            "name": "[parameters('roleNameGuid')]",
            "properties": {
                "roleDefinitionId": "[variables(parameters('builtInRoleType'))]",
                "principalId": "[reference('/subscriptions/b83*******************************4c23f/resourceGroups/*********/providers/Microsoft.ManagedIdentity/userAssignedIdentities/test-gh-67839-2', '2018-11-30').principalId]"
            }
        }
    ]
}

This template threw error for me:
{
    "status": "Failed",
    "error": {
        "code": "RoleAssignmentUpdateNotPermitted",
        "message": "Tenant ID, application ID, principal ID, and scope are not allowed to be updated."
    }
}

Also, note that as the documentation says:

This template is not idempotent unless the same roleNameGuid value is provided as a parameter for each deployment of the template.

Additionally, when I give different roles to same Managed Identity, it succeeds.
Can you please explain further, what discrepancy you are addressing here in this issue?

Thanks @HarshitaSingh-MSFT
If you run your scenario 1 : give Contributor role to Managed Identity 1 multiple times (same roleNameGuid)
I would expect that you should be able to run successful deployment, because as stated, this can be achieved by keeping the roleNameGuid the same. This does not seem to be the case, so documentation does not seem to hold true.
In my case there is no second managed Identity involved.
In my case managed identity 1 is run multiple times, with same roleNameGuid and fails.
Please advise if this explains my discrepancy to point of understanding?

@dirkslab, I think there can be another cause for this. I am able to run the same script for Managed Identity 1 twice. It is succeeding without any errors:

Let me know if I misunderstood your question.

Thanks @HarshitaSingh-MSFT , you have correctly addressed the question. If you are able to run Managed Identity 1 twice, this might be an indication that something else is wrong. I will run some new tests this morning to see if I can add any additional info or find my error.

@dirkslab , sure, thanks. Keep me posted.
For now, is the issue good to be closed? If you get further question(s) on this, you can reopen the issue and I will be happy to assist you further.

@HarshitaSingh-MSFT please do not close yet, let me give final feedback, to confirm if I do indeed get the same results.

@HarshitaSingh-MSFT you can close the call.
I could re-produce my error multiple times, until I removed the user Managed identity from Contributor group and re-added via template script. Now its working as expected.
I have done the remove and re-add steps before logging the call multiple times.
Anyway, now it is working. Same script, same user Managed Identity and same Contributor group. Same actions different outcome.
I cannot explain this nor point to any mistakes that needed to be corrected.
Thanks for the feedback as it confirmed it should have worked, which it is doing now.

Good to know! @dirkree , shall we proceed to close this ticket?

@HarshitaSingh-MSFT you can proceed and close the call.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue. It was nice working with you!


LEAN-2495 - update json-schema version

The pipeline is failing because of a Jenkins issue, but it made sure things are working locally, so I'll proceed with the merge.


support Xiaomi Occupancy(Human Presence) Sensor XMOSB01XS

Support 2024 New battery based Xiaomi Mijia Occupancy (Human Presence) Sensor (XMOSB01XS)
New test cases are added.
Also verified by adding it to Home Assistant (with a small additional changes in xiaomi-ble component for additional new properties)
Hardware Info:

https://www.aliexpress.com/i/1005007104780534.html
https://www.mi.com/shop/buy/detail?product_id=19994

Lint commit errors are not a problem, but to pass the test, name your commit something like:
feat: add support for xmosb01xs
Use lower case letters only and use feat:  to start with


Display a book page using BookBuilder

How do I display an interactable book page, without giving the player a physical book, using the build in BookItemBuilder,

this library is not a UI library.

you use use

https://mvnrepository.com/artifact/xyz.upperlevel.spigot.book/spigot-book-api/1.4.2
this library show book UI to players.


Port Python Entire CI Recipes

Description
Since the Native CI is entirely in shell scripts, I have to port the existing job recipes here. Data source:
https://github.com/ChewKeanHo/Template-Python
Expected Behavior
Template can initiate a Python workspace immediately.
Current Behavior
To initiate Python workspace, manual efforts are needed.
Associated Data Files
No response

setup CI recipe integrated, both natively and GitHub CI.

start CI recipe integrated, both natively and GitHub CI.

prepare CI recipe integrated, both natively and GitHub CI.

build CI recipe integrated, both natively and GitHub CI.

job is considered fully ported. package, release, and compose are different workflow so it shall be excluded from here.


Unprocessible Entity Error While Publishing AL

When I try to Publish, it gives me an error the specified extension is not published

When you try to publish what? To which server, running which version of BC? From which version of the AL extension for VS Code? etc.

I am publishing an AL extension to an Oprem BC170
vscode

When you try to publish what? To which server, running which version of BC? From which version of the AL extension for VS Code? etc.

Publishing an AL Extension to BC170 OnPrem, VScode version in image

Apparently i have restarted the BC Server and Extension has published successfully,
Thank you @dnpb for your quick response


git-stack Crash Report

Please complete the following tasks

[ ] I have searched the discussions
[ ] I have searched the existing issues

Description
git stack --pull crashes and asks me to file this bug report
Version
git-stack 0.8.4
Steps to reproduce
git stack --pull on a private repo, which I can't share unfortunately.  Let me know what more debugging info I can provide.
Actual Behaviour
Crashes and generates this report file:
name = 'git-stack'
operating_system = 'unix:OSX'
crate_version = '0.8.4'
explanation = '''
Panic occurred in file '/Users/gus/.cargo/registry/src/github.com-1ecc6299db9ec823/git-stack-0.8.4/src/git/repo.rs' at line 179
'''
cause = 'called `Result::unwrap()` on an `Err` value: Error { code: -3, klass: 9, message: "object not found - no match for id (ef618179d19ddd392f74961b51d3d50c854a1f38)" }'
method = 'Panic'
backtrace = '''

   0: 0x104c50390 - rust_begin_unwind
                at /rustc/e092d0b6b43f2de967af0887873151bb1c0b18d3/library/std/src/panicking.rs:584
   1: 0x104c84304 - core::panicking::panic_fmt::hffc63a015c61fdde
                at /rustc/e092d0b6b43f2de967af0887873151bb1c0b18d3/library/core/src/panicking.rs:142
   2: 0x104c843a8 - core::result::unwrap_failed::hd24fd75dfe8b9563
                at /rustc/e092d0b6b43f2de967af0887873151bb1c0b18d3/library/core/src/result.rs:1785
   3: 0x104a88bd8 - git_stack::git::repo::GitRepo::is_dirty::h78aaa75c5121bf1e
   4: 0x104a14340 - git_stack::stack::stack::h811b8f483c070c87
   5: 0x104a3c784 - git_stack::run::ha57fdc8e04ee0839
   6: 0x104a3af74 - git_stack::main::h9a9f8115197e674b
   7: 0x104a442bc - std::sys_common::backtrace::__rust_begin_short_backtrace::h1f8d82ee17b9f1d1
   8: 0x104a253d0 - std::rt::lang_start::{{closure}}::h91f8007fadf389ad
   9: 0x104c460bc - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::h3b331d3fbbcc71c7
                at /rustc/e092d0b6b43f2de967af0887873151bb1c0b18d3/library/core/src/ops/function.rs:280
                 - std::panicking::try::do_call::hff616b6be7bbc015
                at /rustc/e092d0b6b43f2de967af0887873151bb1c0b18d3/library/std/src/panicking.rs:492
                 - std::panicking::try::h298ba2ba2d72fd07
                at /rustc/e092d0b6b43f2de967af0887873151bb1c0b18d3/library/std/src/panicking.rs:456
                 - std::panic::catch_unwind::h82d7a0ad94159423
                at /rustc/e092d0b6b43f2de967af0887873151bb1c0b18d3/library/std/src/panic.rs:137
                 - std::rt::lang_start_internal::{{closure}}::h801a38d4a43d99be
                at /rustc/e092d0b6b43f2de967af0887873151bb1c0b18d3/library/std/src/rt.rs:128
                 - std::panicking::try::do_call::h8ecac938bf293f4a
                at /rustc/e092d0b6b43f2de967af0887873151bb1c0b18d3/library/std/src/panicking.rs:492
                 - std::panicking::try::he8bacc15da046b2c
                at /rustc/e092d0b6b43f2de967af0887873151bb1c0b18d3/library/std/src/panicking.rs:456
                 - std::panic::catch_unwind::hfbee3bd78d2873c3
                at /rustc/e092d0b6b43f2de967af0887873151bb1c0b18d3/library/std/src/panic.rs:137
                 - std::rt::lang_start_internal::hbbfe6e663b24763e
                at /rustc/e092d0b6b43f2de967af0887873151bb1c0b18d3/library/std/src/rt.rs:128
  10: 0x104a40484 - _main'''

Expected Behaviour
No response
Debug Output
gus@Anguss-MBP infrastructure % git stack --pull -vv
[TRACE git_stack::stack] Initializing
[TRACE git_stack::config] Loading gitconfig
[TRACE git_stack::config] Loading /Users/gus/work/infrastructure/.gitconfig
[TRACE git_stack::config] Loading /Users/gus/work/infrastructure/.git/config
[TRACE git_stack::stack] --pull implies --rebase
[TRACE git_stack::stack] Ignoring auto-fixup=move without an explicit --rebase
[TRACE git_stack::stack] Ignoring auto-repair=true without an explicit --rebase
[DEBUG globset] built glob set; 0 literals, 4 basenames, 0 extensions, 0 prefixes, 0 suffixes, 0 required extensions, 0 regexes
[TRACE git_stack::git::repo] Loading local branches
[TRACE git_stack::git::protect] master: ignored "master"
[TRACE git_stack::stack] Branch master is protected
[DEBUG git_stack::stack] Chose branch origin/master as the base for gus-heredoc-noise
[WARN  git_stack::stack] master is 0 ahead and 786 behind origin/master, using d047ea12a0f6bd6a9cebf1fec1039d06a28f15a2 as --base instead
[DEBUG git_stack::stack] Chose branch origin/master as the base for origin/master
[WARN  git_stack::stack] gus-irsa-vs-cni is 1 ahead and 1985 behind origin/master, using 0a42a1769b7bd8fe5469eaac66ff84a53f236cf0 as --base instead
[DEBUG git_stack::stack] Chose branch origin/master as the base for gus-eks-ipv6
[WARN  git_stack::stack] gus-eks-oidc-aud is 1 ahead and 1985 behind origin/master, using 0a42a1769b7bd8fe5469eaac66ff84a53f236cf0 as --base instead
[DEBUG git_stack::stack] Chose branch origin/master as the base for gus-vpc-standard-ipv6
[DEBUG git_stack::stack] git fetch origin master
From github.com:Canva/infrastructure

branch                    master     -> FETCH_HEAD
[DEBUG git_stack::git::repo] Failed to stash: object not found - no match for id (ef618179d19ddd392f74961b51d3d50c854a1f38); class=Odb (9); code=NotFound (-3)
Well, this is embarrassing.

git-stack had a problem and crashed. To help us diagnose the problem you can send us a crash report.
We have generated a report file at "/var/folders/cv/n9y_grn13n9g2rx0v0zdywym0000gn/T/report-a9db590b-b6c7-4911-bcb3-64647230109c.toml". Submit an issue or email with the subject of "git-stack Crash Report" and include the report as an attachment.
We take privacy seriously, and do not perform any automated error collection. In order to improve the software, we rely on people to submit reports.
Thank you kindly!

Could you run with 0.8.5 and pass along the new crash message?
The git library we are using doesn't describe error conditions which makes it difficult to predict how to properly repsond to an error from a function.  In this case, for some reason asking for the status of the repo is failing.  I've updated the crash messages to report more information so we can decide how we should handle the error from the git library


allow asset creation without video

https://trello.com/c/xOU9ZrBi/477-fip-allow-asset-creation-without-video

 FIP: Allow asset creation without video

After some discussion, it was decided to follow the existing implementation where a video is created first and then the asset is attached. Anansi can check and just tag the video as a duplicate (eventually, once it's deployed).


Stuck at Creating Project

Hi. I am evaluating this new product. I've just following the getting started guide and tried to create a "todos" app but now the process has been stuck on the "Creating your project..." step (Nhost console) for days now. Even when I pick my answers and move ahead, the process does not complete and stays at this step for hours.

@seyaobey-dev Thank you for letting us know. We had a small (~15) number of projects getting stuck because of an issue we had with one of our servers.
Regarding your project, I deleted it for you, feel free to create another one - I see you have another project running 👍

Closing for now. Let us know if this was not solved.


Decide on a strategy for macOS application name handling

Currently if you want to correctly change the display name of the macOS example app in FDE you have to change it in a whole lot of places (various XIB items, build settings, project settings, etc.). That's not viable for a long-term approach—we could populate all of these correctly during initial template creation, but renaming later would be very messy. Before making this into a template we should figure out how we want to manage this; it should require as few edits as possible.
Some things to consider:

Have the application delegate (which doesn't yet exist) default to walking a known list of menubar items and replacing a placeholder with a runtime string.
Have the template's window controller to the same with the window title.
Adding a pubspec.yaml entry that we could use to populate a build flag that's set in the xcconfigs.

The name is now in an xcconfig rather than needing to be changed in the project. I think that's enough for an initial create template, so I'm going to take this off the project lists for create and MVP. I'll leave it open for further consideration though, such as using pubspec metadata.


incorrect information ?

Perhaps the screenshots are wrong
Expected : Microsoft Hosted Job should be increased.
Actuel : Self-Hosted was increased.

Documentdetails
⚠ Dit gedeelte niet bewerken. Het is vereist om problemen te koppelen tussen docs.microsoft.com en GitHub.

ID: 7734edca-173b-ba47-bf1b-3c19f9bd93e1
Version Independent ID: d6ea8680-546e-f102-fd55-b35af33a6aa5
Content: Buy CI/CD in Azure DevOps Services
Content Source: docs/organizations/billing/buy-more-build-vs.md
Product: devops
GitHub Login: @chcomley
Microsoft Alias: chcomley

Hi @sqlenders thank you for your feedback. I've created a work item to better clarify that the screen shots are showing as an example of Microsoft-hosted. The first step tells you to select between Microsoft-hosted or Self-hosted. Although the process for both is the same, I'll explain that the screenshots only show an example of the Microsoft-hosted workflow. Thanks again.


Merge n pull

Cheat sheets

Y

i didnt read what i was doing. i am sorry i am now learning the full meaning of every word and code that was created.


fix #485 test failure with recent redis version

Fixed in commit 597c61a in a slightly different way.


Food - "Reset to defaults" reveals unrelated dietary options

Go to Food and choose a Vegetarian diet
Slide some food items
Press "Reset to defaults"
Behind the scenes the button changes the diet to Omnivore, so all the food item options are shown

Hmm, I had made it working correctly previously so that "Reset to defaults" set values to default values of the selected diet, so I must have broke something afterwards, I'll have look.

Ah, this is an old issue. This is fixed in the food section update. I close this issue now.


Ci2

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@19e9900). Click here to learn what that means.
The diff coverage is 0%.

@@            Coverage Diff            @@
##             master     #125   +/-   ##
=========================================
  Coverage          ?   38.04%
=========================================
  Files             ?       62
  Lines             ?    30808
  Branches          ?        0
=========================================
  Hits              ?    11720
  Misses            ?    17967
  Partials          ?     1121

Impacted Files
Coverage Δ

pkg/server/fsm.go
53.3% <ø> (ø)

internal/pkg/config/util.go
6.39% <0%> (ø)

Continue to review full report at Codecov.

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


typechain-types is gone

Hello, it seems this file is missing from the repo, so it can't run
npm run node:fork:polygon-v3

> node:fork:polygon-v3
> FORK=polygon MARKET=polygon-v3 npm run node

> node
> npx hardhat node

An unexpected error occurred:

helpers/utils.ts:16:8 - error TS2307: Cannot find module '../typechain-types' or its corresponding type declarations.

16 } from "../typechain-types";
          ~~~~~~~~~~~~~~~~~~~~

It's used to import these objects:
import {
  IERC20Detailed,
  IERC20DetailedBytes,
  IERC20,
} from "../typechain-types";

The solution:
Before running npm run node:fork:polygon-v3 run npm run compile it will generate the typechain-types folder.

It's closed


bf: ZENKO-332 fix Azure proxy localhost req

This fixes the issue in Federation deployments where Azure backend request would default to localhost when using a proxy.

PR has been updated. Reviewers, please be cautious.


UnannotatedSubPackages option doesn't work correctly.

Reddit user u/rakingleaves recommended that I raise this issue here.
I'm trying to get NullAway working in my existing, large Android app. I've already had ErrorProne working for some time.
My intended approach was to enable NullAway one package at a time so I can add the necessary Nullable annotations gradually (and convince the rest of my dev team of the benefit of doing so). So I was trying to exclude all sub packages at first, then remove one at a time from the UnannotatedSubPackages option as I fix them up. But I just cannot get the UnannotatedSubPackages config to work.
This is the relevant snippet from my build.gradle. The network.xmpp package gets excluded correctly but the service.contacts package still throws up warnings. I've tried putting other packages in the list. Some get filtered out, most don't.
afterEvaluate {
    android.applicationVariants.each {
        it.javaCompiler.toolChain ErrorProneToolChain.create(project)
        it.javaCompiler.options.compilerArgs.addAll()

        if (!name.toLowerCase().contains("test")) {
            it.javaCompiler.options.compilerArgs += [
                "-Xep:NullAway:WARN",
                "-XepOpt:NullAway:AnnotatedPackages=com.mydomain.myapp",
                "-XepOpt:NullAway:UnannotatedSubPackages=com.mydomain.myapp.network.xmpp,com.mydomain.myapp.service.contacts"
            ]
        }
    }

Versions:
errorProne : '2.1.1',
nullAway : '0.1.6',

Thanks for the report!  We'll cut a new release soon

FYI release 0.1.7 was just cut with this fix.  Should be in Maven Central soon


Don't autorelease roots of inner pointers.

Use mark_dependence to track the relationship of a returned inner pointer to its root.
rdar://97408160

@swift-ci please test


Unexpected output when using HALAttributeConverter

I've noticed when using the HALAttributeConverter, the serialized output contains the embedded properties on the model in addition to where I'd expect them, under "_embedded":
{
  "id": 0,
  "firstName": "Bob",
  "lastName": "Smith",
  "display_name": "Bob Smith",
  "pets": [],
  "favouritePet": {
    "id": 0,
    "name": "Benji",
    "petToys": [
      {
        "name": "Rubber Bone"
      }
    ]
  },
  "_links": {
    "self": {
      "href": "~/api/person/0"
    },
    "person": {
      "href": "~/api/person/0"
    }
  },
  "_embedded": {
    "pets": [],
    "favouritePet": {
      "id": 0,
      "name": "Benji",
      "petToys": [
        {
          "name": "Rubber Bone"
        }
      ],
      "_links": {
        "self": {
          "href": "~/api/pets/0"
        }
      },
      "_embedded": {
        "toys": [
          {
            "name": "Rubber Bone",
            "_links": {
              "self": {
                "href": "~/api/pets//toys/Rubber%20Bone"
              }
            }
          }
        ]
      }
    }
  }
}

I think the desired behavior would be to ignore the model properties w/ the HalEmbedded attribute, with a result like:
{
  "id": 0,
  "firstName": "Bob",
  "lastName": "Smith",
  "display_name": "Bob Smith",
  "_links": {
    "self": {
      "href": "~/api/person/0"
    },
    "person": {
      "href": "~/api/person/0"
    }
  },
  "_embedded": {
    "pets": [],
    "favouritePet": {
      "id": 0,
      "name": "Benji",
      "_links": {
        "self": {
          "href": "~/api/pets/0"
        }
      },
      "_embedded": {
        "toys": [
          {
            "name": "Rubber Bone",
            "_links": {
              "self": {
                "href": "~/api/pets//toys/Rubber%20Bone"
              }
            }
          }
        ]
      }
    }
  }
}

I'm also noticing when converted back using ToPlainResponse, as may be the case w/ "application/json" content type, the embedded properties get merged back into the model resulting in duplication:
{
  "id": 0,
  "firstName": "Bob",
  "lastName": "Smith",
  "display_name": "Bob Smith",
  "pets": [],
  "favouritePet": {
    "id": 0,
    "name": "Benji",
    "petToys": [
      {
        "name": "Rubber Bone"
      },
      {
        "name": "Rubber Bone"
      }
    ],
    "toys": [
      {
        "name": "Rubber Bone"
      }
    ]
  }
}

I did some investigation and it looks like it will be a bit of work/overhead to remove these from the model during "conversion" in HALAttributeConverter.  The current workaround I'm using for this is to use a custom contract resolver that simply ignores properties with the the HalEmbedded attribute:
    public class JsonHalAttributesContractResolver : CamelCasePropertyNamesContractResolver
    {
        protected override IList<JsonProperty> CreateProperties(Type type, MemberSerialization memberSerialization)
        {
            var properties = base.CreateProperties(type, memberSerialization);

            // Ignore properties w/ HalEmbedded attribute
            return
                properties.Where(p => !p.AttributeProvider.GetAttributes(typeof(HalEmbeddedAttribute), true).Any())
                    .ToList();
        }
    }

wired in Startup like
            services.AddMvc(options =>
            {
                // Replace default json output formatter w/ the one supporting HAL
                options.OutputFormatters.RemoveType<JsonOutputFormatter>();
                var serializerSettings = JsonSerializerSettingsProvider.CreateSerializerSettings();
                serializerSettings.ContractResolver = new JsonHalAttributesContractResolver();
                options.OutputFormatters.Add(new JsonHalOutputFormatter(serializerSettings,
                    converters: new HALAttributeConverter()));
            });

While this was pretty simple and appears to get around both issues above, it feels a little awkward...basically in order for the HALAttributeConverter to work as expected you'd have to remember to wire in a similar contract resolver.
Any thoughts on this?

I similarly had to work around this issue, but I just added a JsonIgnore attribute to each property that also had the HalEmbedded attribute (using Newtonsoft JSON.NET) rather than a custom contract resolver.


Recordedit input basetype

This PR adds functionality to the recordedit app to check for a column's base type if we don't know how to create an input for it's type if it's a user defined domain type.
This is for issue #1234.

I created a new catalog and schema on dev.isrd, added a domain type to that schema that recordedit did not understand. That domain type had a base type of date. I was then able to create a table with a column using that new domain type. When that column was displayed in the recordedit form, it used the date input we have defined instead of the text input.


Do not throw an exception on missing mrack.log

os.stat throws exception so we use try except when removing file to accept the fact when the file does not exists

@Tiboris, could you please remove the prefix from the commit message? We're not using them to have a consistent release notes. See also the commit recommendations. Thanks.

@happz @Tiboris I've fixed according to what ruff complained. Please ack/nack.

I can ACK on behalf of @Tiboris

Thank you.


change dot const to u8

Hi @tailhook,
Couldn't help but notice that openat doesn't compile.
After this change it does.
Ran the tests, nothing seems negatively affected by this.

That's strange. What version of rustc do you have?

rustc 1.18.0

Oh.. I'm sorry. Didn't realize c_char was defined differently between aarch64 and x86_64. That was why it didn't compile on my odroid C2.

Wow! So after this PR does it compile on both architectures?

No, but with #4 it should.


Fixed issue with not being able to add new service

Description
Now able to add a new service
Motivation and Context
Broken build.
Screenshots

Checklist:

[x] My pull request is properly named
[x] The changes respect the code style of the project ($ npm run lint && npm run reformat-files && npm run manage-translations && npm run apply-branding)
[x] I tested/previewed my changes locally

Fixes #1595

@vraravam I don't understand how this fixes the issue? I only see moving the constant from one file to another and renaming it everywhere?

Yes - @mhatvan - I suspect its with accessing the constant from the relative path into the features namespace. Not sure why, but when I reverted my commit, it seemed to fix the issue. Since the better place for such a hardcoded string is in config.js - i felt it was better to move it as opposed to just reverting the previous commit.


Can someone help? When updating the sdk my old custom moons wont build once in that project.

Its keeps giving me an error saying it cant find the specified file in asset builds talking about the moon im trying to export example it says "MARS.lem is unable to be located" in unity while using the sdk to build my moon.

i copied all files of the moon located under "mods" in unity before changing to the new sdk then put them in that moon mod folder in the mods folder of the new unity sdk version.

now it wont compile, then when switching back to the old sdk using unity it wont build the moon in that version either, what happened?

/Desktop/LethalSDK_Project/Assets/AssetBundles/MARS.lem: The system cannot find the file specified.

/Desktop/LethalSDK_Project/Assets/AssetBundles/MARS.lem: The system cannot find the file specified.

You may have two files with same name
It generates conflict
Read the logs in the unity console to know which file exactly

THANK YOU SO MUCH


Return an empty Line if textToLine is applied to an empty Text

Currently the IsString instance for Line doesn't accept an empty string as an input. This is a bit weird as, I think, an empty string is completely valid data to be used as a Line. This is in practice a source of partiality:
*Turtle> :set -XOverloadedStrings
*Turtle> echo ""
*** Exception: NewlineForbidden

This PR fixes textToLine to return an empty Line if it's applied to an empty Text.

Updated the example above and fixed a bug in the implementation.

Thank you for fixing this!  I agree that "" should be a valid Line


Add mode check for device

This fixes two problems:

docker run --device /dev/sda:rw ubuntu bash doesn't work
--device /dev/zero:/dev/noro:ro doesn't show clear error message,
but fail when writing to cgroup file.

Signed-off-by: Qiang Huang<EMAIL_ADDRESS>

docker run --device /dev/sda:rw ubuntu bash doesn't work

@hqhq you mean it's not supposed to work, so we should validate it, right ?

One nit since there needs to be a change anyway.

@vdemeester @cpuguy83 @calavera Updated, thanks.

LGTM

do we need docs for this?

Doesn't seem like it would need docs to me.

LGTM


feat: Display last commit date in variants list

Specially for plugins with more than a handful of variants, it'd be useful to tell if variants seem abandoned.
For example, tap-purecloud has many variants but none seem to have been updated after 2021:

It's hard to tell which is most recently updated variant (and whether that's the default) without clicking through all the variants.
We probably want to strike a balance between

having a default variant based on a public set of criteria (https://github.com/meltano/hub/issues/1292)
and making it easy for the user to decide which variant to use if they determine the default does not suit their needs

@edgarrmondragon we currently don't have space for this on the new hub design. We could maybe do something on hover 🤔

@edgarrmondragon we currently don't have space for this on the new hub design. We could maybe do something on hover 🤔

@tayloramurphy Yeah, however we indicate most active variants to users without them having to browse would be an improvement i.m.o


TODO: Template10.Services.SerializationService

Controls belong in a folder structure like this:
MyControl root folder
/ Control folder for control project
/ Demo folder for demo project
/ Nuget folder for NuGet setup
readme.md file for docs, previously in wiki
In the case of Services we are doing the same:
MyService root folder
/ Service folder for service project
/ Demo folder for demo project
/ Nuget folder for NuGet setup
readme.md file for docs, previously in wiki
In many cases the folders are already setup. Sometimes they are not. This work item is the assignment to update the folder structure of the solution and to create the resulting assets as needed. This description is shared across several work items so there is no specific instruction.

If you would like to take on this task and submit a PR for it when it is complete, please indicate that you are working on it by adding a comment below. This will keep us from working on the same things. It would be very much appreciated if you would also comment with a status on your progress. If you do not submit a status of your work then this could be taken over by another developer and your subsequent PR will be rejected. What is the takeaway: update the status, please.

I'll work on this one.

@Windows-XAML/template-10-developer-community:
I've published the NuGet package for this library here: https://www.nuget.org/packages/Template10.Services.SerializationService/1.0.0-preview-20170523
My PR containing the code for this update can be found at #1489.
@JerryNixon - I invited you and @darenm as owners for the new package.

This wasn't closed by the merge?


Unclear description of hexadecimal values?

I've been playing around with this utility for a bit, since I have the MSI X370 SLI PLUS motherboard and I was curious if I could control my RGB lighting. However, it seems that the hexadecimal values are poorly explained.
When I run this command:
./msi-rgb -d 60 0F00FF0F F0F0F00F 00FF0F0F

I get a colour sequence of red, green, blue, cyan, magenta, yellow, white, black.
To me, this seems to suggest that the colours follow an 8-step pattern, where the nibbles of each byte are reversed. This means the order is 21436587, and there are 16 different possible brightnesses for each colour.
Is it possible that the order of the steps could be fixed in code, or this be documented?

The behaviour is hardware specific and changes between boards. Currently the data it writes to hardware is pretty much exactly what is specified on the command line – it is the user’s responsibility to figure out the particularities of their own hardware.
The behaviour will not be changed and documenting how exactly any particular board works is way out of scope for this project.


number label does not change

Describe the bug
I followed readme.md and created a file with content below
import React from 'react'
import Board from 'react-trello'
import './App.css'

export default class App extends React.Component {
	render() {
		return <Board data={data} class='board' />
	}
}
const data = {
	lanes: [
		{
			id: 'lane1',
			title: 'To-do',
			label: '2/2',
			cards: [
				{
					id: 'Card1',
					title: 'Write Blog',
					description: 'Can AI make memes',
					label: '30 mins',
					draggable: true,
				},
				{
					id: 'Card2',
					title: 'Pay Rent',
					description: 'Transfer via NEFT',
					label: '5 mins',
					metadata: { sha: 'be312a1' },
				},
			],
		},
		{
			id: 'lane2',
			title: 'Completed',
			label: '0/0',
			cards: [],
		},
	],
}

When I give it a label '0/0' or '2/2', it works, however, when I drag a card from lane 1 to lane 2, the number in lane 2 is still 0/0, likewise, the number in lane 1 is still 2/2.
This would most certainly happen.. I used label to define it. But can I achieve Expected Behaviour in some way?
To Reproduce
Steps to reproduce the behavior:

Create foo.js
Write in code provided above
yarn start
drag cards
see error

Expected behaviour
The numbers are expected to change into 1/2 and 1/0 or something (this is a bad expectation..)
Screenshots

Desktop (please complete the following information):

OS: macOS
Browser: Safari
Version: 14.0

Additional context
Nah.. probably my problem.

speaking of which why is four-spaced tab so large on GitHub??

Not sure if this will help you, looks like it's been a while but I've started using this library recently and wanted my labels to update when I moved cards around and used the onDataChange callback with the eventBus to make it happen
For reference, boardData is my { lanes: [] } object that I pass to <Board data={boardData} />
  const onDataChange = useCallback(( newData: any ) => {
   // Checking if any data changed, otherwise do nothing
   // Also helps with the scenario when data is first loaded from the server and eventBus is not init yet
    if (JSON.stringify(boardData) === JSON.stringify(newData))
    {
      return;
    }

   // Iterate through each lane and count the cards, then set it back in the object
    newData.lanes.forEach((lane : any) => {
      lane.label = `${lane.cards.length}`;
    });

   // Pass the new lane data to the eventBus
    eventBus.publish({ type: "UPDATE_LANES", lanes: newData.lanes });
  },[boardData, eventBus]);

Not sure if this will help you, looks like it's been a while but I've started using this library recently and wanted my labels to update when I moved cards around and used the onDataChange callback with the eventBus to make it happen
For reference, boardData is my { lanes: [] } object that I pass to <Board data={boardData} />
  const onDataChange = useCallback(( newData: any ) => {
   // Checking if any data changed, otherwise do nothing
   // Also helps with the scenario when data is first loaded from the server and eventBus is not init yet
    if (JSON.stringify(boardData) === JSON.stringify(newData))
    {
      return;
    }

   // Iterate through each lane and count the cards, then set it back in the object
    newData.lanes.forEach((lane : any) => {
      lane.label = `${lane.cards.length}`;
    });

   // Pass the new lane data to the eventBus
    eventBus.publish({ type: "UPDATE_LANES", lanes: newData.lanes });
  },[boardData, eventBus]);

Thanks for responding—really appreciate it! I vaguely remember figuring something out in the end back then but I cannot recall how—it has, as you said, been a while. It is quite negligent of me to not post the solution nor close this issue though... as you have provided a useful solution and I myself one a while back, I believe this issue can be closed.
Thanks again!


azcopy sync not handling files/directories with overlapping paths correctly

Version: AzCopy 10.0.4-Preview
Platform: Linux Ubuntu 16.04.5 LTS (Xenial Xerus)
This is the command:
./azcopy sync 'https://somestorageaccount.blob.core.windows.net/logs?<sas>' /mnt/logs --recursive=true --force

If you have something like the following in the source container:
/logs/foo/bar/log.txt
/logs/foo/bar

You'll see failed transfers because the file /logs/foo/bar is created on the destination, preventing the creation of the directory /logs/foo/bar which is needed to create /logs/foo/bar/log.txt on the destination.
You can also see the error in the azcopy log:
2019/01/02 13:27:33 ERR: [P#0-T#8] DOWNLOADFAILED: https://somestorageaccount.blob.core.windows.net/logs/foo/bar/log.txt?si=logs-read-only&sig=REDACTED&sr=c&sv=2018-03-28 :
 000 : File Creation Error open /logs/foo/bar/log.txt: not a directory

I get that this is a result of going from a flat namespace to a hierarchical namespace. The system generating the blobs on the source account is creating the files. My guess is that its because its using the hadoop FileSystem APIs and calling mkdir() somewhere along the way so a placeholder is created. While I can try to get them to change the behavior, its another azure service so that is likely another ticket.
Current workaround is to look for these placeholder files (always 0 bytes in length) and delete them before running azcopy. Ideally, azcopy would also add support for an option to handle this situation by creating the directories first and/or adding an option to ignore 0-length files.

Hi @pmackles, thanks for reaching out!
AzCopy should be able to handle this scenario; there might be a bug if it's not working with sync. Could you please help me verify whether /logs/foo/bar has the metadata hdi_isfolder=true? Thanks!

@zezha-msft - I can confirm that these placeholder blobs (like /logs/foo/bar) have the following metadata key/value pairs:
hdi_isfolder=true
hdi_permission={"owner":"root","group":"supergroup","permissions":"rwxrwxrwx"}

Hi @pmackles, thanks for getting back to us!
It indeed seems that there's a bug in the sync command, we should ignore such blobs. I've logged this item in our backlog. Thank you!

@pmackles sorry for the inconvenience, and I really appreciate your patience!
I've rewritten the sync command and released it in 10.0.8. This issue should be fixed. Please let us know if you still encounter any problem.
Here is a wiki explaining how the new sync command works. Please feel free to reach out if you have any question or concern.


Migrate to bevy v0.6

This PR mostly deals with breaking changes from migrating to bevy version 0.6, as per the Bevy migration guide.
Some callouts:

Used StorageType::SparseSet for FlyCam, since I expect it to only exist approximately for one entity.
Added [[example]] sections to the repository config.

One important note: I did not nudge the version to 0.6, please let me know if that's desirable.

@BlackPhlox Thanks for taking a look at the PR!
I bumped the crate version and reverted the changes to the examples.
I agree, having a large number of FlyCam components and massively adding/removing them both seem like unrealistic scenarios. Given that, my choice of SparseSet for storage was with the goal to minimize memory footprint. However, I think I misunderstood the default archetype-based storage.
Before reverting this to default storage, could you confirm that this will not grow linearly with the number of entities? Thanks!

Thanks! I don't think there is any discernable difference in memory footprint between the two storage types, as they both grow linearly with the size of entities, though I've asked in the discord just to be sure. From what I can see the storage types only affect iteration and operation speed.

@maniwani (Joy) from discord was amazing at taking their time to educate me on bevy_ecs, I can highly recommend reading the response. So yes, the memory footprint is mostly the same, and Sparse might even be potentially bigger than the default storage type because of the required relations.

Apologies for the slow progress, have been busy at work the last days.
@BlackPhlox Thanks for digging up the details on Discord, definitely learned a lot looking through it. I've removed the SparseSet storage type from the PR.
I also pinged @sburris0 via mail since it doesn't seem that they have been active on Github for a while, but let's see what happens.

Thanks and no worries, I've been in contact with Spencer and I have received ownership on crates.io so I can publish a 0.6 version 🎉


Release a spec with tvOS support

Blocked by https://github.com/czechboy0/BuildaUtils/issues/7

Fixed by #124.


Resolves #807: Abstracting a common base for UseLatestVersionsMojo and UseLatestReleasesMojo

Abstracting a common base for UseLatestVersionsMojo and UseLatestReleasesMojo.
Elaborating on the difference between a "release" and a "version"

Two issues:
#807
#516

@slawekjaranowski please review

My own afterthought after this is merged is that, as with other mojos. Across the whole plugin we basically have a host of different features, which may be turned on and off. I think I'll need to review the whole of the plugin and use a pattern like the decorator so that we can simply compose the behaviour of the mojo of different behaviours, depending on which features are enabled. See #289


Fix #676, API docs have wrong signature for isEqualTo()

Thanks!  Let us know if you run into any other problems!


Demo page would be nice.

working on it ;)

just uploaded it, add the URL to the repo. here it is for your convenience: http://callmecavs.github.io/jump.js/

:dancer:


rust_winit> error: Please select a feature to build for unix: x11, wayland

When I try to build https://github.com/magnetophon/vizia-audio-synth, which is basically the first step of https://github.com/geom3trik/vizia-audio-synth, I get the error in the title.
I'm building using nix, with the command:
nix build -L -f Cargo.nix workspaceMembers.audio_synth.build

After a helpful chat with @geom3trik he told me to make an issue for it.

Not sure what exactly the problem on your end is, but I usually use a nix-shell with the shell.nix seen below. It is by no means a minimal shell.nix to compile it but it's what I use for all of my Rust projects.
I tried to compile your fork of the vizia-audio-synth. It didn't work initially with your fork of vizia so I switched it from:
vizia = {git = "https://github.com/magnetophon/vizia", features = ["x11"]}
to:
vizia = {git = "https://github.com/vizia/vizia", features = ["x11"]}
which at least let me compile it without any problems.
let
  moz_overlay = import (builtins.fetchTarball
    "https://github.com/mozilla/nixpkgs-mozilla/archive/master.tar.gz");
  nixpkgs = import <nixpkgs> { overlays = [ moz_overlay ]; };
in with nixpkgs;
stdenv.mkDerivation {
  name = "moz_overlay_shell";
  nativeBuildInputs = [ pkgconfig clang lld ];
  buildInputs = [
    (nixpkgs.rustChannelOf { date = "2022-07-02"; channel = "nightly"; }).rust
    rustup
    pkgconfig
    openssl
    xorg.libxcb
    xlibsWrapper

    glib
    atk
    cairo
    gdk-pixbuf
    pango
    gtk3

    udev
    alsaLib
    alsa-lib
    vulkan-loader
    libGL
    egl-wayland
    xorg.libXcursor
    xorg.libXrandr
    xorg.libXi
    libxkbcommon
  ];
  shellHook = ''
    export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:${
      pkgs.lib.makeLibraryPath [ udev alsaLib vulkan-loader libGL libxkbcommon ]
    }"'';
}

I now tried your solution with the following command:
nix build -L -f Cargo.nix workspaceMembers.audio_synth.build

I was able to reproduce your issue and got a little further by adding features = [ "x11" ] to two of the winit dependencies in the Cargo.nix file. winit is a dependency of glutin and also vizia_winit.
Now I don't get the Please select a feature to build for unix error anymore but now I get Builder called die: Cannot wrap '/nix/store/f9ns7a1d63pb27ccbdqjh4x2bfbarnaa-rust_winit-0.27.1/bin/winit' because it is not an executable file. Not quite how to fix that one though.

@KDecay Thanks a lot for your reply!
Adding the two instances of features has the same effect here: it compiles fine, but complains about the postInstall (which I got here.
What I found really strange:

/nix/store/58fly8hz33al8b04nwwlysh8i5hnz3fb-rust_winit-0.27.1/, where the postInstall error pointed me, is an empty directory
When I comment out those lines, I get  Please select a feature to build for unix again!

I'm now running nix-shell shell.nix, using your shell.nix, followed by cargo run.
Is that how you did it?

I'm now running nix-shell shell.nix, using your shell.nix, followed by cargo run.
Is that how you did it?

Yup, the exact process is as follows:

Create the shell.nix (preferably in the project directory).
cd into the directory of the shell.nix file.
Run nix-shell.
cd into the project directory if you aren't there already.
Run cargo run.

@KDecay Thanks!
When I use the upstream vizia, it builds and runs!
I'd like to get the Cargo.nix working too, as that lets me build remotely, but this at least shows it's a nix or crate2nix issue and not a vizia one.

@KDecay Thanks a lot for your reply!

No worries!

Adding the two instances of features has the same effect here: it compiles fine, but complains about the postInstall (which I got here.

It seems to wrap the wrong thing here. The error message states that it expects a executable file, but winit is a library. What's the reason you added this?

What I found really strange:
/nix/store/58fly8hz33al8b04nwwlysh8i5hnz3fb-rust_winit-0.27.1/, where the postInstall error pointed me, is an empty directory
When I comment out those lines, I get Please select a feature to build for unix again!

Huh interesting. Not sure how libraries get stored in the nix/store. It's complaining about not finding an executable in bin/winit which makes sense since it's not an executable. I wonder why you get the error again though.

When I use the upstream vizia, it builds and runs!

Awesome! Happy to help :)

I'd like to get the Cargo.nix working too, as that lets me build remotely, but this at least shows it's a nix or crate2nix issue and not a vizia one.

Understandable. Let us know if you get it working!

What's the reason you added this?

When I found an example to take the buildInputs from, I just copied it along, see link above.

Not sure how libraries get stored in the nix/store

/nix/store/58fly8hz33al8b04nwwlysh8i5hnz3fb-rust_winit-0.27.1/ is the $out of  winit, the place where winit should be stored. There is nothing there, which I find odd.
I am new to rust, but for other libraries, $out would contain a lib dir, or at least something!

When I found an example to take the buildInputs from, I just copied it along, see link above.

I see. Might be a good idea to ask on the nix discord if they can explain what it does or what it is used for.

/nix/store/58fly8hz33al8b04nwwlysh8i5hnz3fb-rust_winit-0.27.1/ is the $out of winit, the place where winit should be stored. There is nothing there, which I find odd.
I am new to rust, but for other libraries, $out would contain a lib dir, or at least something!

Makes sense. I would expect something similar, but I never really look into the nix/store tbh ^^ It being empty is really weird though. Might also be worth asking the folks over at the nix discord. They have a dedicated #rust channel there.
Here is the link to their discord if you aren't part of it yet:
https://discord.com/invite/RbvHtGa

@KDecay Thanks, I was  already on the nix discord, and asked the question just now.
Are you also there?
What's your nick?

@magnetophon Yup, I'm also there.
My discord is KDecay#9324.


Merry Christmas！About Sweet Berries

Hello, jsorrell.
Someone I talked to the other day asked me how to get Sweet Berries.
I took the time to do some research, and neither original Minecraft nor SkyBlock has a proper way to access it.
That's all.
Merry Christmas!

This is fixed in 3.1.0 -- Foxes can now spawn holding Sweet Berries.


Color Isolation fx bug

I love your color isolation shader, it's exactly what I've been looking for for years. However there seems to be a bug when using reshade in performance mode with it.  In performance mode bright areas on the game, usually text and bright lights turn black. I have attached an example without performance mode and with performance mode.

I'm glad you like the shader! In order to recreate the issue can you please post a screenshot where the bug occurs but without any shader running and also the settings of the shader? Then I can load the image with Reshade and apply the shader with the same settings. Thanks!

Here are the screenshots and zip file that includes the settings.ini I was using. This appears to happen in many games. Also if it is not too much to ask for would it be possible to add an option to run multiple separate color isolations at once so I can I can reject or isolate multiple colors without affecting the colors in between. To do this current I just copy and past the fx file and change the name.

ColorIsolationSettings.zip

Hm, this is weird. I have no idea what causes that difference when using performance mode (could also be a bug in the compiler). Anyway, I try to rewrite the shader a bit on the weekend to add your suggestion - maybe the problem disappears while doing that... :)

Thank you for your quick responses! I'm really looking forward to it.

Hey, I've added ColorIsolation2.fx to Shaders/dev. I tested it a bit and couldn't recreate the bug. You can also add a 2nd color to isolate - but i'ts a little weird to set up right now. :)
If you think the shader works well I can replace the old one.

It's working great now, thank you so much


USB Automount on Kiosk Mode

I don't know if it's just my problem, but from a clean installation of both Raspberry and SpyGuard, in Kiosk mode, it doesn't detect the usb when it asks me to save the report ... I tried to change all the ports and various USB sticks , I also tried to install USBAutomount, but nothing...

finally fixed it. just add "@pcmanfm -d" on autostart file
In this way pcmanfm runs in the background


Add the ability to show/hide sources

Sometimes sources get mixed up and various sources need to be manually shown or hidden on screen. Add a moderator ability to show/hide a source by name.

Added in v1.7.5


Fix flaky golden test

SV scores from sv detector can change a little between each run (after 6 decimal digits). So sort variables by truncating their score to 6 decimal digits and if variables have the same truncated score, sort alphabetically

Thanks!
Would the "proper fix" be to change NL Server to be more deterministic? Should we have TODO?

added TODO


Keivan/keyboard bug

fixed keyboard ux problem where keyboard would block textfield.

Looks good, address comments, then merge


refactor(my collection): reuse auction result component

The type of this PR is: Refactor
Description
Extracts AuctionResult (and AuctionResultFragmentContainer) from ArtistInsightAuctionResults, moves them into a directory with other list components, and reuses them in MyCollectionAuctionResults.
PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have added tests for my changes, or my changes don't require testing, or I have included a link to a separate Jira ticket covering the tests.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a CHANGELOG.yml entry or my changes do not require one.

Is it possible to add a screenshot with the updated component?

Done - it's pretty much the same, although I tweaked the whitespace slightly.

Is this ready to be merged? I didn't merge because I wasn't assigned but looks good to me!


propName should always return a value

Currently, the return value of propName is nullable. It should be able to guarantee a return value all the time.

Coverage decreased (-0.007%) to 98.788% when pulling 33e581ab3b8db45781833dc11bbae745416888f3 on jessebeach:propName--return-value-should-not-be-nullable into bc61ce9a3b4b6f9ef634b092b28b6aa40324bd89 on evcohen:master.

Coverage decreased (-0.007%) to 98.788% when pulling f5202084c8ea7121cfd31b857c3bfeab911d639e on jessebeach:propName--return-value-should-not-be-nullable into bc61ce9a3b4b6f9ef634b092b28b6aa40324bd89 on evcohen:master.

Coverage decreased (-0.007%) to 98.788% when pulling e89722b8282213e6b4fabfff7b8a8dcf179f9999 on jessebeach:propName--return-value-should-not-be-nullable into bc61ce9a3b4b6f9ef634b092b28b6aa40324bd89 on evcohen:master.

Ya, the coverage fall is fine. I removed a test that doesn't test anything.

@evcohen I don't have write access to this repo. Merge is all yours.


chore: fix web3-unit-tests

fix https://github.com/godwokenrises/godwoken/actions/runs/4123672980/jobs/7121973052#step:3:10

8 tests failed - https://github.com/godwokenrises/godwoken/actions/runs/4132676974/jobs/7144129086#step:10:298
cc @classicalliu


Makefile's: Do a cleanup and fix some style issues

Pull Request checklist
Note: these are not necessarily requirements

[ ] I reformatted the code with clang-format
[x] I checked to make sure my submission worked
[x] I am the author of submission or have permission from the original author.

Pull Request description
This PR fix:

The usage of tabs (tabs is only used in code, not in docs)
The double comments (who not know the 0 is disabled/false? :/)
The 80+ char limit (not in OPL Version because it simple break the build)
The rebuild in some modules
The clean in some modules (see https://github.com/ifcaro/Open-PS2-Loader/pull/41/files#diff-1d8ff768f6adafb3f88553127065566bL40)
The whitespace's (ugly)

Bump!

@uyjulian pickup changes if need, closing it.


[iOS] fix: colorFromHexString failed parsing

React Native: v.0.76.0
OS: iOS 18.0

Crash:
Application threw exception NSRangeException: *** -[NSConcreteScanner setScanLocation:]: Index 1 out of bounds; string length 0 Originated at or in a subcall of
For now, we have applied the fix with patch-package.
Thank you for checking it @gbumps

Thanks, will check for it immediately!


Table rowheader does not take into account cells spanning more rows

If I have a DITA topic containing a table like this:
   <table frame="none" rowheader="firstcol">
            <title>Flowers</title>
            <tgroup cols="3">
                <colspec colname="c1" colnum="1" colwidth="171.0pt"/>
                <colspec colname="c2" colnum="2" colwidth="99.0pt"/>
                <colspec colname="newCol3" colnum="3" colwidth="200px"/>
                <thead>
                    <row>
                        <entry>Flower</entry>
                        <entry>Type</entry>
                        <entry>Soil</entry>
                    </row>
                </thead>
                <tbody>
                    <row>
                        <entry morerows="2">Chrysanthemum</entry>
                        <entry>perennial</entry>
                        <entry>well drained</entry>
                    </row>
                    <row>
                        <entry>perennial</entry>
                        <entry>acidic</entry>
                    </row>
                    <row>
                        <entry>annual</entry>
                        <entry>sandy, well-drained</entry>
                    </row>
                </tbody>
            </tgroup>
        </table>

and I publish to PDF, because the attribute (rowheader="firstcol") is specified on the table, only the "Chrysanthemum" cell should be bold. No other cell should be bold because this particular cell spans over two other lines. But for the PDF output both the "perennial" and "annual" cells will be shown as bold.
The XHTML output seems to work properly.
Tested with both DITA OT 2.x and 3.x.

As a possible workaround in the XSLT:
      plugins\org.dita.pdf2\xsl\fo\tables.xsl

there is a check like:
      <xsl:when test="ancestor::*[contains(@class, ' topic/table ')][1]/@rowheader = 'firstcol'
                    and empty(preceding-sibling::*[contains(@class, ' topic/entry ')])">

which can be replaced with:
        <xsl:when test="ancestor::*[contains(@class, ' topic/table ')][1]/@rowheader = 'firstcol'
            and @dita-ot:x = '1'">

because that's how the HTML-based output XSLTs handle the same situation.

Thanks for the pointer, I created a pull request using that fix.

Resolved in #2946.


WIP: NETOBSERV-1637: OVS monitoring ebpf hook

Description
OVS monitoring eBPF hook feature
ebpf configs to enable ovs tracking from operator
      advanced:
        env:
          ENABLE_OVS_MONITORING: "true"

- bpftool perf show -p
[{
        "pid": 2854,
        "fd": 8,
        "prog_id": 143,
        "fd_type": "kprobe",
        "func": "psample_sample_packet",
        "offset": 0
    }
]
- bpftool map dump id 258
"key": {
            "eth_protocol": 2048,
            "direction": 0,
            "src_mac": [2,220,231,139,148,213
            ],
            "dst_mac": [10,88,10,128,2,12
            ],
            "src_ip": [0,0,0,0,0,0,0,0,0,0,255,255,10,128,2,2
            ],
            "dst_ip": [0,0,0,0,0,0,0,0,0,0,255,255,10,128,2,12
            ],
            "src_port": 56546,
            "dst_port": 8080,
            "transport_protocol": 6,
            "icmp_type": 0,
            "icmp_code": 0,
            "if_index": 2
        },
        "values": [{
                "cpu": 0,
                "value": {
                    "packets": 1,
                    "bytes": 74,
                    "start_mono_time_ts":<PHONE_NUMBER>667,
                    "end_mono_time_ts":<PHONE_NUMBER>667,
                    "flags": 2,
                    "errno": 0,
                    "dscp": 0,
                    "pkt_drops": {
                        "packets": 0,
                        "bytes": 0,
                        "latest_flags": 0,
                        "latest_state": 0,
                        "latest_drop_cause": 0
                    },
                    "dns_record": {
                        "id": 0,
                        "flags": 0,
                        "latency": 0,
                        "errno": 0
                    },
                    "flow_rtt": 0,
                     ovs_dp_keys": [[0,0,0,0,12,0,255,238
                        ],[0,0,0,0,0,0,0,0
                        ],[0,0,0,0,0,0,0,0
                        ],[0,0,0,0,0,0,0,0
                        ]

Dependencies

new kernel update with OVS hook
new version of OVS
new version of OVN
https://github.com/ovn-org/ovn-kubernetes/pull/4596
https://github.com/netobserv/network-observability-operator/pull/664
https://github.com/netobserv/flowlogs-pipeline/pull/669
https://github.com/netobserv/network-observability-console-plugin/pull/535

Checklist
If you are not familiar with our processes or don't know what to answer in the list below, let us know in a comment: the maintainers will take care of that.

[ ] Will this change affect NetObserv / Network Observability operator? If not, you can ignore the rest of this checklist.
[ ] Is this PR backed with a JIRA ticket? If so, make sure it is written as a title prefix (in general, PRs affecting the NetObserv/Network Observability product should be backed with a JIRA ticket - especially if they bring user facing changes).
[ ] Does this PR require product documentation?

[ ] If so, make sure the JIRA epic is labelled with "documentation" and provides a description relevant for doc writers, such as use cases or scenarios. Any required step to activate or configure the feature should be documented there, such as new CRD knobs.

[ ] Does this PR require a product release notes entry?

[ ] If so, fill in "Release Note Text" in the JIRA.

[ ] Is there anything else the QE team should know before testing? E.g: configuration changes, environment setup, etc.

[ ] If so, make sure it is described in the JIRA ticket.

QE requirements (check 1 from the list):

[ ] Standard QE validation, with pre-merge tests unless stated otherwise.
[ ] Regression tests only (e.g. refactoring with no user-facing change).
[ ] No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

Codecov Report
Attention: Patch coverage is 0% with 21 lines in your changes are missing coverage. Please review.

Project coverage is 36.14%.  Consider uploading reports for the commit 4f1c2e8 to get more accurate results

Files
Patch %
Lines

pkg/ebpf/tracer.go
0.00%
11 Missing :warning:

pkg/agent/agent.go
0.00%
9 Missing :warning:

pkg/ebpf/bpf_x86_bpfel.go
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #286      +/-   ##
==========================================
+ Coverage   33.30%   36.14%   +2.83%
==========================================
  Files          48       42       -6
  Lines        3489     3807     +318
==========================================
+ Hits         1162     1376     +214
- Misses       2230     2353     +123
+ Partials       97       78      -19

Flag
Coverage Δ

unittests
36.14% <0.00%> (+2.83%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

/ok-to-test

/ok-to-test

/retest

/ok-to-test

/ok-to-test

/ok-to-test

/test unit

/ok-to-test

/test unit

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/test unit

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/retest

/ok-to-test

/ok-to-test

/lgtm

/approve


Can't edit my email

Whenever I try to change my email, I get this.

verified on version 4.0.0
IOS version V18

testcase


[WIP] Add filter for all API endpoints to allow only requests with application/json header

Coverage increased (+0.03%) to 56.204% when pulling 18017742efd9c9b25acfd3e6a750983a58509289 on reasonerjt:xsrf-filter into 1840aefea934b04fcaa90c0adfbf8e4b359c9524 on vmware:master.


Windows framework_tests_misc flakes on live_widget_controller_test

(part of https://github.com/flutter/flutter/issues/97036)
Data is based Q4 2021 flakes that happened from 10/01/2021 to 01/13/2022, and there is 1 flake:
https://ci.chromium.org/ui/p/flutter/builders/prod/Windows framework_tests_misc/2804/overview
00:21 +123 -1: C:\b\s\w\ir\x\w\flutter\packages\flutter_test\test\live_widget_controller_test.dart: Input event array on LiveWidgetController [E]
  'file:///C:/b/s/w/ir/x/w/flutter/packages/flutter_test/test/live_widget_controller_test.dart': Failed assertion: line 150 pos 14: 'diff.inMilliseconds > -1': timeDiffs were: [0:00:00.015592, 0:00:00.041870, 0:00:00.025870, 0:00:00.009870, 0:00:00.009471, 0:00:00.009095, 0:00:00.001905] (offending time was -1ms)
  dart:core                                     _AssertionError._throwNew
  test\live_widget_controller_test.dart 150:14  main.<fn>

/cc @HansMuller Could you help take a further look? We are scanning flakes in shards tests (which contains many unit/integration tests), and want to either fix or skip corresponding flaky tests to try achieving 0 flakes from them. Thanks!

This is still happening: https://ci.chromium.org/ui/p/flutter/builders/prod/Windows framework_tests_misc/4579/overview

@pdblasi-google, @keyonghan  - perhaps this is no longer happening?

Closing this as there have been no further reports.


Remove mentions of backoff from RabbitMQ component documentation

Describe the issue
https://github.com/dapr/dapr/issues/1798 removed backoff support from the RabbitMQ pubsub component, but the docs still mention backoff support.
URL of the docs
https://docs.dapr.io/reference/components-reference/supported-pubsub/setup-rabbitmq/
Expected content
There shouldn't be any backoffs there.

Completed