Update Microsoft.Sql ManagedInstance 2022-11-01-preview Swagger Docs

ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[x] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
N/A
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
Version update - EO March 2023.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

please copy paste arm-id corresponding change to your PR. we will add auto-generation process for them next month.
❌ 1023 - TypeFormatChanged	The new version has a different format than the previous one.New: Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L950:9Old: Microsoft.Sql/stable/2021-11-01/ManagedInstances.json#L864:9
❌ 1023 - TypeFormatChanged	The new version has a different format than the previous one.New: Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L994:9Old: Microsoft.Sql/stable/2021-11-01/ManagedInstances.json#L916:9
❌ 1023 - TypeFormatChanged	The new version has a different format than the previous one.New: Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L1005:9Old: Microsoft.Sql/stable/2021-11-01/ManagedInstances.json#L928:9
❌ 1023 - TypeFormatChanged	The new version has a different format than the previous one.New: Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L1098:9Old: Microsoft.Sql/stable/2021-11-01/ManagedInstances.json#L1022:9

please copy paste arm-id corresponding change to your PR. we will add auto-generation process for them next month.
❌ 1023 - TypeFormatChanged	The new version has a different format than the previous one.New: Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L950:9Old: Microsoft.Sql/stable/2021-11-01/ManagedInstances.json#L864:9
❌ 1023 - TypeFormatChanged	The new version has a different format than the previous one.New: Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L994:9Old: Microsoft.Sql/stable/2021-11-01/ManagedInstances.json#L916:9
❌ 1023 - TypeFormatChanged	The new version has a different format than the previous one.New: Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L1005:9Old: Microsoft.Sql/stable/2021-11-01/ManagedInstances.json#L928:9
❌ 1023 - TypeFormatChanged	The new version has a different format than the previous one.New: Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L1098:9Old: Microsoft.Sql/stable/2021-11-01/ManagedInstances.json#L1022:9

Done, I copied over arm-id's manually.

@ericshape

@ericshape I don't understand why is this validation of Enum failing when we were fixing this issue https://portal.azure-devex-tools.com/amekpis/linting/detail?errorId=3611EA06-DC20-4131-A667-D21DC9EF2C34.

@ericshape I don't understand why is this validation of Enum failing when we were fixing this issue https://portal.azure-devex-tools.com/amekpis/linting/detail?errorId=3611EA06-DC20-4131-A667-D21DC9EF2C34.

if you are adding the following enum setup, it is expected.
      "x-ms-enum": {
        "name": "ProvisioningState",
        "modelAsString": true
      }

@ericshape I don't understand why is this validation of Enum failing when we were fixing this issue https://portal.azure-devex-tools.com/amekpis/linting/detail?errorId=3611EA06-DC20-4131-A667-D21DC9EF2C34.

if you are adding the following enum setup, it is expected.
      "x-ms-enum": {
        "name": "ProvisioningState",
        "modelAsString": true
      }

So do we need to modify the current setup or we should ignore this break and treat it as expected? Because we primarily want to fix the 360 issue?

@ericshape I don't understand why is this validation of Enum failing when we were fixing this issue https://portal.azure-devex-tools.com/amekpis/linting/detail?errorId=3611EA06-DC20-4131-A667-D21DC9EF2C34.

if you are adding the following enum setup, it is expected.
      "x-ms-enum": {
        "name": "ProvisioningState",
        "modelAsString": true
      }

@ericshape so do we need to modify the current setup or we should ignore this break and treat it as expected? Because we primarily want to fix the 360 issue?

yes.
please make sure there is no property name change

Following breaks are expected.
Since last version we made following changes:

Added new optional parameter - virtualClusterId
Added missing HTTP 200 paths/examples for Start/Stop actions
Added missing enum values for property provisioningState
Added missing property x-ms-enum to resolve 360 issue

Rule
Message

❌ 1048 - AddedXmsEnum
The new version adds a x-ms-enum extension.New: Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L892:9Old: Microsoft.Sql/stable/2021-11-01/ManagedInstances.json#L806:9

💬 1020 - AddedEnumValue
The new version is adding enum value(s) 'Creating, Deleting, Updating, Unknown, Accepted, Deleted, Unrecognized, Running, NotSpecified, Registering, TimedOut' from the old version.New: Microsoft.Sql/preview/2022-11-01-preview/JobExecutions.json#L567:9Old: Microsoft.Sql/stable/2021-11-01/JobExecutions.json#L567:9

💬 1020 - AddedEnumValue
The new version is adding enum value(s) 'Creating, Deleting, Updating, Unknown, Accepted, Deleted, Unrecognized, Running, NotSpecified, Registering, TimedOut' from the old version.New: Microsoft.Sql/preview/2022-11-01-preview/JobStepExecutions.json#L291:9Old: Microsoft.Sql/stable/2021-11-01/JobStepExecutions.json#L291:9

💬 1020 - AddedEnumValue
The new version is adding enum value(s) 'Creating, Deleting, Updating, Unknown, Accepted, Deleted, Unrecognized, Running, NotSpecified, Registering, TimedOut' from the old version.New: Microsoft.Sql/preview/2022-11-01-preview/JobTargetExecutions.json#L425:9Old: Microsoft.Sql/stable/2021-11-01/JobTargetExecutions.json#L425:9

💬 1020 - AddedEnumValue
The new version is adding enum value(s) 'InProgress' from the old version.New: Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L892:9Old: Microsoft.Sql/stable/2021-11-01/ManagedInstances.json#L806:9

💬 1038 - AddedPath
The new version is adding a path that was not found in the old version.New: Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L476:5

💬 1038 - AddedPath
The new version is adding a path that was not found in the old version.New: Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L519:5

💬 1040 - AddedReadOnlyPropertyInResponse
The new version has a new read-only property 'virtualClusterId' in response that was not found in the old version.New: Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L891:7Old: Microsoft.Sql/stable/2021-11-01/ManagedInstances.json#L805:7

💬 1045 - AddedOptionalProperty
The new version has a new optional property 'virtualClusterId' that was not found in the old version.New: Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L891:7Old: Microsoft.Sql/stable/2021-11-01/ManagedInstances.json#L805:7

Rule	Message
❌ [1048 - AddedXmsEnum](https://github.com/Azure/openapi-diff/tree/master/docs/rules/1048.md)	The new version adds a x-ms-enum extension.
New: [Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L892:9](https://github.com/Azure/azure-rest-api-specs/blob/2d7c8501b3f55ff588c18df16530cb5a2bcdaa82/specification/sql/resource-manager/Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L892:9)
Old: [Microsoft.Sql/stable/2021-11-01/ManagedInstances.json#L806:9](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/sql/resource-manager/Microsoft.Sql/stable/2021-11-01/ManagedInstances.json#L806:9)
💬 [1020 - AddedEnumValue](https://github.com/Azure/openapi-diff/tree/master/docs/rules/1020.md)	The new version is adding enum value(s) 'Creating, Deleting, Updating, Unknown, Accepted, Deleted, Unrecognized, Running, NotSpecified, Registering, TimedOut' from the old version.
New: [Microsoft.Sql/preview/2022-11-01-preview/JobExecutions.json#L567:9](https://github.com/Azure/azure-rest-api-specs/blob/2d7c8501b3f55ff588c18df16530cb5a2bcdaa82/specification/sql/resource-manager/Microsoft.Sql/preview/2022-11-01-preview/JobExecutions.json#L567:9)
Old: [Microsoft.Sql/stable/2021-11-01/JobExecutions.json#L567:9](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/sql/resource-manager/Microsoft.Sql/stable/2021-11-01/JobExecutions.json#L567:9)
💬 [1020 - AddedEnumValue](https://github.com/Azure/openapi-diff/tree/master/docs/rules/1020.md)	The new version is adding enum value(s) 'Creating, Deleting, Updating, Unknown, Accepted, Deleted, Unrecognized, Running, NotSpecified, Registering, TimedOut' from the old version.
New: [Microsoft.Sql/preview/2022-11-01-preview/JobStepExecutions.json#L291:9](https://github.com/Azure/azure-rest-api-specs/blob/2d7c8501b3f55ff588c18df16530cb5a2bcdaa82/specification/sql/resource-manager/Microsoft.Sql/preview/2022-11-01-preview/JobStepExecutions.json#L291:9)
Old: [Microsoft.Sql/stable/2021-11-01/JobStepExecutions.json#L291:9](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/sql/resource-manager/Microsoft.Sql/stable/2021-11-01/JobStepExecutions.json#L291:9)
💬 [1020 - AddedEnumValue](https://github.com/Azure/openapi-diff/tree/master/docs/rules/1020.md)	The new version is adding enum value(s) 'Creating, Deleting, Updating, Unknown, Accepted, Deleted, Unrecognized, Running, NotSpecified, Registering, TimedOut' from the old version.
New: [Microsoft.Sql/preview/2022-11-01-preview/JobTargetExecutions.json#L425:9](https://github.com/Azure/azure-rest-api-specs/blob/2d7c8501b3f55ff588c18df16530cb5a2bcdaa82/specification/sql/resource-manager/Microsoft.Sql/preview/2022-11-01-preview/JobTargetExecutions.json#L425:9)
Old: [Microsoft.Sql/stable/2021-11-01/JobTargetExecutions.json#L425:9](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/sql/resource-manager/Microsoft.Sql/stable/2021-11-01/JobTargetExecutions.json#L425:9)
💬 [1020 - AddedEnumValue](https://github.com/Azure/openapi-diff/tree/master/docs/rules/1020.md)	The new version is adding enum value(s) 'InProgress' from the old version.
New: [Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L892:9](https://github.com/Azure/azure-rest-api-specs/blob/2d7c8501b3f55ff588c18df16530cb5a2bcdaa82/specification/sql/resource-manager/Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L892:9)
Old: [Microsoft.Sql/stable/2021-11-01/ManagedInstances.json#L806:9](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/sql/resource-manager/Microsoft.Sql/stable/2021-11-01/ManagedInstances.json#L806:9)
💬 [1038 - AddedPath](https://github.com/Azure/openapi-diff/tree/master/docs/rules/1038.md)	The new version is adding a path that was not found in the old version.
New: [Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L476:5](https://github.com/Azure/azure-rest-api-specs/blob/2d7c8501b3f55ff588c18df16530cb5a2bcdaa82/specification/sql/resource-manager/Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L476:5)
💬 [1038 - AddedPath](https://github.com/Azure/openapi-diff/tree/master/docs/rules/1038.md)	The new version is adding a path that was not found in the old version.
New: [Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L519:5](https://github.com/Azure/azure-rest-api-specs/blob/2d7c8501b3f55ff588c18df16530cb5a2bcdaa82/specification/sql/resource-manager/Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L519:5)
💬 [1040 - AddedReadOnlyPropertyInResponse](https://github.com/Azure/openapi-diff/tree/master/docs/rules/1040.md)	The new version has a new read-only property 'virtualClusterId' in response that was not found in the old version.
New: [Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L891:7](https://github.com/Azure/azure-rest-api-specs/blob/2d7c8501b3f55ff588c18df16530cb5a2bcdaa82/specification/sql/resource-manager/Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L891:7)
Old: [Microsoft.Sql/stable/2021-11-01/ManagedInstances.json#L805:7](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/sql/resource-manager/Microsoft.Sql/stable/2021-11-01/ManagedInstances.json#L805:7)
💬 [1045 - AddedOptionalProperty](https://github.com/Azure/openapi-diff/tree/master/docs/rules/1045.md)	The new version has a new optional property 'virtualClusterId' that was not found in the old version.
New: [Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L891:7](https://github.com/Azure/azure-rest-api-specs/blob/2d7c8501b3f55ff588c18df16530cb5a2bcdaa82/specification/sql/resource-manager/Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L891:7)
Old: [Microsoft.Sql/stable/2021-11-01/ManagedInstances.json#L805:7](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/sql/resource-manager/Microsoft.Sql/stable/2021-11-01/ManagedInstances.json#L805:7)

Following breaks are expected.
Since last version we made following changes:

Added new optional parameter - virtualClusterId
Added missing HTTP 200 paths/examples for Start/Stop actions
Added missing enum values for property provisioningState
Added missing property x-ms-enum to resolve 360 issue https://portal.azure-devex-tools.com/amekpis/linting/detail?errorId=3611EA06-DC20-4131-A667-D21DC9EF2C34

Rule	Message
❌ 1048 - AddedXmsEnum	The new version adds a x-ms-enum extension.New: Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L892:9Old: Microsoft.Sql/stable/2021-11-01/ManagedInstances.json#L806:9
💬 1020 - AddedEnumValue	The new version is adding enum value(s) 'Creating, Deleting, Updating, Unknown, Accepted, Deleted, Unrecognized, Running, NotSpecified, Registering, TimedOut' from the old version.New: Microsoft.Sql/preview/2022-11-01-preview/JobExecutions.json#L567:9Old: Microsoft.Sql/stable/2021-11-01/JobExecutions.json#L567:9
💬 1020 - AddedEnumValue	The new version is adding enum value(s) 'Creating, Deleting, Updating, Unknown, Accepted, Deleted, Unrecognized, Running, NotSpecified, Registering, TimedOut' from the old version.New: Microsoft.Sql/preview/2022-11-01-preview/JobStepExecutions.json#L291:9Old: Microsoft.Sql/stable/2021-11-01/JobStepExecutions.json#L291:9
💬 1020 - AddedEnumValue	The new version is adding enum value(s) 'Creating, Deleting, Updating, Unknown, Accepted, Deleted, Unrecognized, Running, NotSpecified, Registering, TimedOut' from the old version.New: Microsoft.Sql/preview/2022-11-01-preview/JobTargetExecutions.json#L425:9Old: Microsoft.Sql/stable/2021-11-01/JobTargetExecutions.json#L425:9
💬 1020 - AddedEnumValue	The new version is adding enum value(s) 'InProgress' from the old version.New: Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L892:9Old: Microsoft.Sql/stable/2021-11-01/ManagedInstances.json#L806:9
💬 1038 - AddedPath	The new version is adding a path that was not found in the old version.New: Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L476:5
💬 1038 - AddedPath	The new version is adding a path that was not found in the old version.New: Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L519:5
💬 1040 - AddedReadOnlyPropertyInResponse	The new version has a new read-only property 'virtualClusterId' in response that was not found in the old version.New: Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L891:7Old: Microsoft.Sql/stable/2021-11-01/ManagedInstances.json#L805:7
💬 1045 - AddedOptionalProperty	The new version has a new optional property 'virtualClusterId' that was not found in the old version.New: Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L891:7Old: Microsoft.Sql/stable/2021-11-01/ManagedInstances.json#L805:7

Can you talk to Jeffrey or mikekistler to get breaking change review approval?

Following breaks are expected.
Since last version we made following changes:

Added new optional parameter - virtualClusterId
Added missing enum values for property provisioningState
Added missing property x-ms-enum to resolve 360 issue https://portal.azure-devex-tools.com/amekpis/linting/detail?errorId=3611EA06-DC20-4131-A667-D21DC9EF2C34

Rule	Message
❌ 1048 - AddedXmsEnum	The new version adds a x-ms-enum extension.New: Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L892:9Old: Microsoft.Sql/stable/2021-11-01/ManagedInstances.json#L806:9
💬 1020 - AddedEnumValue	The new version is adding enum value(s) 'Creating, Deleting, Updating, Unknown, Accepted, Deleted, Unrecognized, Running, NotSpecified, Registering, TimedOut' from the old version.New: Microsoft.Sql/preview/2022-11-01-preview/JobExecutions.json#L567:9Old: Microsoft.Sql/stable/2021-11-01/JobExecutions.json#L567:9
💬 1020 - AddedEnumValue	The new version is adding enum value(s) 'Creating, Deleting, Updating, Unknown, Accepted, Deleted, Unrecognized, Running, NotSpecified, Registering, TimedOut' from the old version.New: Microsoft.Sql/preview/2022-11-01-preview/JobStepExecutions.json#L291:9Old: Microsoft.Sql/stable/2021-11-01/JobStepExecutions.json#L291:9
💬 1020 - AddedEnumValue	The new version is adding enum value(s) 'Creating, Deleting, Updating, Unknown, Accepted, Deleted, Unrecognized, Running, NotSpecified, Registering, TimedOut' from the old version.New: Microsoft.Sql/preview/2022-11-01-preview/JobTargetExecutions.json#L425:9Old: Microsoft.Sql/stable/2021-11-01/JobTargetExecutions.json#L425:9
💬 1020 - AddedEnumValue	The new version is adding enum value(s) 'InProgress' from the old version.New: Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L892:9Old: Microsoft.Sql/stable/2021-11-01/ManagedInstances.json#L806:9
💬 1038 - AddedPath	The new version is adding a path that was not found in the old version.New: Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L476:5
💬 1038 - AddedPath	The new version is adding a path that was not found in the old version.New: Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L519:5
💬 1040 - AddedReadOnlyPropertyInResponse	The new version has a new read-only property 'virtualClusterId' in response that was not found in the old version.New: Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L891:7Old: Microsoft.Sql/stable/2021-11-01/ManagedInstances.json#L805:7
💬 1045 - AddedOptionalProperty	The new version has a new optional property 'virtualClusterId' that was not found in the old version.New: Microsoft.Sql/preview/2022-11-01-preview/ManagedInstances.json#L891:7Old: Microsoft.Sql/stable/2021-11-01/ManagedInstances.json#L805:7

@JeffreyRichter @mikekistler can you please review following breaking changes report?
@ericshape to confirm that breaking change regarding x-ms-enum property is expected due to 360 issue.
cc @raych1

@raych1 Jeffery Approved the breaking change. Do you need anything else to merge this PR?

@raych1 please wait with merging this PR. We might need to make an additional change regarding provisioningStateEnum property.

@raych1 please merge this PR when you get a chance. @toki95 and me reviewed everything and it was correct, no additional changes were needed.


Clarity on Reader role

Reader role has the following action: */read
Read resources of all types, except secrets. What isn't clear is this is on the management plane and not on data plane. Reader only allows on the management level. I cannot assign the Reader role to a user and expect them to be able to read containers/blobs for storage. Instead they should use the preview Blob Data reader role. I believe this should be more clear in the documentation.

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

ID: 99581afb-7950-6daa-7227-055d04446b7e
Version Independent ID: f1a5bf89-9e54-aede-3a9a-70788a95927b
Content: Built-in roles for Azure resources
Content Source: articles/role-based-access-control/built-in-roles.md
Service: role-based-access-control
GitHub Login: @rolyon
Microsoft Alias: rolyon

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

Hi @shraboin
Thanks for your feedback. On the built-in role page, you might have noticed that operations are grouped into sections. Most operations are listed under an Actions section, but there are some listed under a DataActions section. Actions apply to the management plane and DataActions apply to the data plane. Since the Reader role doesn't have any DataActions, the operations apply only to the management plane.
Do you have any suggestions on how we can make this clearer? Would it be helpful if we included an empty DataActions section like this?

DataActions

none

thanks

@rolyon I think that would help. I work developer support related to Azure Storage. Customers are sometimes unaware of the data/management planes. I think a quick addition would be a link that explains the difference or some sort of highlight in the article explaining the distinction of actions between management and data. The link in question would be the following: https://docs.microsoft.com/en-us/azure/storage/common/storage-security-guide . Either an asterisk next to DataActions or some annotation to reference would help. Thanks for looking into this! If this isn't clear feel free to reply or reach me on Teams/Skype. My alias is the same as my GitHub name.

@shraboin
Okay, sounds good. Just so you know, we also have this example where we try to explain actions on the management and data planes:
https://docs.microsoft.com/en-us/azure/role-based-access-control/role-definitions#data-operations-example

Hi @shraboin
I made the following changes to the docs:
Included DataActions in all the built-in roles list.
https://docs.microsoft.com/en-us/azure/role-based-access-control/built-in-roles
Added a link to the Understand role definitions article, which talks more about DataActions.
https://docs.microsoft.com/en-us/azure/role-based-access-control/built-in-roles
Added a link to Azure Storage security guide.
https://docs.microsoft.com/en-us/azure/role-based-access-control/role-definitions#data-operations-example
Hopefully this helps makes the management and data planes a little more clear. Let me know if you have any additional feedback.
thanks

@MicrosoftDocs/azure-cxp-triage
#please-close

Thank you Robert.


Table of endpoints is lacking graph api

Hi.
The table of endpoints difference between regular and government is lacking the endpoint "graph.microsoft.com" that should be "graph.microsoft.us" for gov cloud.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 7d38c31a-c048-c398-7343-30f39dbdc2fa
Version Independent ID: 7f55864f-acd4-762d-bd58-11c6d1660057
Content: Compare Azure Government and global Azure - Azure Government
Content Source: articles/azure-government/compare-azure-government-global-azure.md
Service: azure-government
GitHub Login: @stevevi
Microsoft Alias: stevevi

Thanks @alahav for your feedback.  This table isn't meant to track API endpoints for every service - it's focused instead on some of the more popular Azure services given that this article is part of Azure documentation.  Graph API endpoints are tracked in Microsoft 365 documentation:
https://learn.microsoft.com/en-us/graph/deployments#microsoft-graph-and-graph-explorer-service-root-endpoints
Note that different Graph API endpoints exist for GCC, GCC High, and DoD environments, as explained in the above article.

#please-close


Don't reexport sdl2-sys modules

Just a bit of cleanup.
ll was showing up on the Rustdocs, which means users can use it directly. Probably best to encourage people to use sdl2_sys for raw bindings instead. :]

Good catch! Cheers :)


chore: build charm in independent workflow step

Description
We move the charm build process to its own workflow stage. We build the charm, we test it, and we publish it, all with the same artifact.
Usage
tox -e integration -- \
  --charm_path=<vault charm path> \
  --kv_requirer_charm_path=<KV requirer charm path>

Rationale

This reduces the amount of resources taken by the integration tests. While working on the backup/restore task, I kept getting github runners issues because they were getting out of available disk space. Here by moving the build stage prior, the integration tests get leaner in terms of space and time to complete.

Integration tests completion time goes from ~18min to ~13min

Each step has its own precise role instead of having the built artifact be a side effect of running the integration tests.

In cases where the CI fails because the charm doesn't build, it's quicker to identify that this isse is build related.
Integration tests won't run if the build fails

Notes

If we agree with this being a good idea here, we should probably take the same approach in other charm workflows.

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that validate the behaviour of the software
[ ] I validated that new and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

I've done something similar in the vault k8s charm, so here are my thoughts:
It looks to me like extracting this to separate workflows extends the total time required to pass all checks from ~18 minutes to max(5, 2) + 14 = ~19 minutes since the integration test relies on both the charms being built. I like the change in conftest, and I like the fact that the step to build the charms are separate since it helps save memory, but I feel that splitting it into different workflows adds unnecessary complexity and overhead. We now end up reinstalling charmcraft and LXD 3 times.
I would prefer to keep the separate build step as a conftest or any other type of fixture, but avoid splitting the build process into multiple workflows unless we have more than 1 other workflow inheriting these artifacts.
If there's a concern about rebuilding the charm twice, how about saving the built charm from the integration test and producing it if it completes successfully?

One of the issues I'm trying to solve with the approach is the runners were getting out of space by having the build + integration tests in 1 workflow (image and reference below), and going back to this approach will keep on producing those errors as we add complexity to integration tests.
As for complexity, I don't think this change makes the CI more complex, though it does increase the number of steps. I think the side effect of the integration tests building the charm was surprising for a non-initiated and having the artefact being built in its own stage is more intuitive. The complexity was always there but hidden in the implementation details of the integration tests.
I agree that installing lxd + charmcraft in multiple workflow steps is wasteful. We do this in most project's CI. For example, in gocert, we install go in all of the workflow steps that require it (unit tests, lint, vet, etc.) In charms, we install tox in all workflow steps. I don't think we should have  a  singular workflow to run everything that has the same dependencies for this reason. Simply put, resource usage is important but I wouldn't trade off the CI usefulness/quality for a marginal gain.
Reference

https://github.com/canonical/vault-operator/actions/runs/8472292490

Screenshots


Ignore images/

Ignores the images/ directory when packaging the extension with vsce package.
https://code.visualstudio.com/api/working-with-extensions/publishing-extension#.vscodeignore
The resulting vsix file is about 0.5mb smaller.
Signed-off-by: David Kwon<EMAIL_ADDRESS>

Once you install the visx, how does the readme look like in the extensions view?

We still see the main image:

This is because vsce package will replace the relative links in the readme to absolute urls.
When I open the .vsix file and look at the readme, it looks like this:
![](https://github.com/redhat-developer/vscode-quarkus/raw/master/images/propertiesSupport.png)

vsce package does this even if images/ is ignored


Jr/june23 code cleanup

[x] Remove or comment out unused code fragments.
[x] Consolidate css and functional code where appropriate.
[ ] Clean up HTML elements and structure where possible.
[ ] Validate Accessibility and other bets practices (high percentile Lighthouse scores).

Because of the redesign that was required to Layout and Structure goal, as well as Accessibility goal, those items were moved to PR #38 .


Assassin's creed 3 broken snow

The snow doesn't work properly on AMD, but spoofing as an NVIDIA make it work  properly.
Bug:

Spoofed as NVIDIA With low quality:

Software information
The executable name is AC3MP.exe and AC3SP.exe
Happens on the max setting of enviroment quality.
System information

GPU: RX 580
Driver: mesa 21.1.1
Wine version: lutris 6.4
DXVK version: 1.8.1

Apitrace file(s)

Put a link here

Log files

d3d9.log: AC3SP_d3d9.log
d3d11.log: AC3SP_d3d11.log
dxgi.log: AC3SP_dxgi.log

Does this even work on Windows?

Does this even work on Windows?

I don't have install windows to test but setting dxgi.customDeviceId = 0402 dxgi.customVendorId = 10de on dxvk.conf makes it work properly

I thought that it was fixed, but no, since spoofing as nvidia reset the graphic configuration to the lowest value, by setting the enviroment quality to the max it happens, with the other two doesn't.

@somebody1121 Friendly ping. Could i get you to retest this with latest dxvk and drivers? :slightly_smiling_face:

@somebody1121 Friendly ping. Could i get you to retest this with latest dxvk and drivers? slightly_smiling_face

Sorry for not replying sooner. It appears to be fixed, tested on the lastest drivers and dxvk.


Deprecation Ember 2+

DEPRECATION: Ember.keys is deprecated in favor of Object.keys [deprecation id: ember-metal.ember.keys]
Update please

Feel free to submit a PR!

https://github.com/hhff/ember-infinity/pull/102


Expose autofillHints

Currently, the library exposes a flag withHint and inject AutofillHints.telephoneNumberNational if true.
On iOS, I doesn't seem to work. I need to specify AutofillHints.telephoneNumber instead.
Can we simply expose the whole Iterable<String>? autofillHints instead of the bool flag?

I don't have an apple phone nor a mac. The problem is that there is two "inputs". One for the dial code and one for the national number (the telephone number without the dial code).
My worries with this are two fold:

the fact that AutofillHints.telephoneNumber does not work on ios seem to be a bug on flutter itself and not this library
exposing the autofill hints would make people perplex as they would use AutofillHints.telephoneNumber which is not really the autofill hint expected. The one expected is the national number.

However this is an easy feature to add.

Would it be possible that the field detect that it is filled (or pasted) with an international prefix and automatically change the national code?
ie. In if I paste "+32477123456" into the PhoneField, I expect it will change the national field.

Well the phone number parser library allows to parse a phone number in its entirety. So parsing a full phone number and extracting the two parts is possible. What I'm not sure about is if it's possible to hi-jack the process of autofill hint in a non-hacky way,

I imagine that the AutoFill feature can't be 100% correct all the time. I imagine it works by looking at data entered in other apps with annotated textfield.
I think the best thing to do are:

Have the field detect that it is filled with an international phone and update the dropdown automatically.
Let the user specify it's own list of AutofillHints.

This seems to be the best course of action although that will make one breaking change:

phone_numbers_parser library exposes two parsers, a light and an heavy one.
phone_form_field lets the user decide which one to use via the param bool lightParser

The issue is that the light parser cannot parse a phone number without the country code (because multiple countries share the same dial code).
Therefor I'll have to remove the possibility to use the light parser with this feature. I guess something functional is preferable though.

This will be done with a breaking change:

The possibility to use the light parser will be removed and only the bigger phone parser from the phone_numbers_parser library will be used, as its the only one that can parse phone numbers without country code. It was introduced recently in this library via the param bool lightParser however it seems to me that this is an essential feature, more essential than the possibility to chose a parser.

Can you try the latest :
dependencies:
  phone_form_field:
    git:
      url: https://github.com/cedvdb/phone_form_field

Hi @cedvdb,
I tried the latest version, thanks a lot!
AutofillHints is not exposed directly so it is good for me.
There is still one thing I would like: when I fill with an international phone number, it should update the country code. I think internally we should try a parsing with PhoneNumber().parseRaw() first and check if the isoCode is the same or not.

when I fill with an international phone number, it should update the country code

Hum if you copy paste an international phone number or auto fill it should update the country code

it is now AutofillHints.telephoneNumber. It is also exposed in BasePhoneFormField but that requires some manual setups

Sorry the "not" in my sentence was a typo :-(

Hum if you copy paste an international phone number or auto fill it should update the country code. Doesn't that work for you ?

Yes I don't see this behaviour.
When I create a PhoneFormField with default values. When I focus, it chooses "+1" (us) by default. Now I paste "+32477124578". The country code stays "+1" and it displays "invalid phone number"

Now I paste "+32477124578". The country code stays "+1" and it displays "invalid phone number"

What device are you on ? it works for me here https://cedvdb.github.io/phone_form_field/#/

This is with an iPhone (real and simulator). I seems the prefix "+" is lost somewhere before it is pasted.
Indeed it work well in the web page.

Should be fixed in next release
https://github.com/cedvdb/phone_form_field/pull/32


also handle SIGPIPE in cleanup routines

fixes gh-1413: restic fails to cleanup locks when bash pipeline fails.
Something else to consider: is it still appropriate to exit(0) when a SIGPIPE is received, as we currently do for SIGINT?
If the bash pipeline fails, even if it's not the fault of restic, perhaps restic should maybe exit(1)? I think it would be bad for restic to give the false impression of success (0) when in fact it had a problem. I don't really know what standard practice is.

Codecov Report

Merging #1415 into master will decrease coverage by 5.67%.
The diff coverage is 80%.

@@            Coverage Diff             @@
##           master    #1415      +/-   ##
==========================================
- Coverage   51.22%   45.55%   -5.68%
==========================================
  Files         136      136
  Lines       13612    13614       +2
==========================================
- Hits         6973     6202     -771
- Misses       5781     6614     +833
+ Partials      858      798      -60

Impacted Files
Coverage Δ

cmd/restic/cleanup.go
38.09% <80%> (+0.59%)
:arrow_up:

internal/backend/b2/b2.go
0% <0%> (-79.41%)
:arrow_down:

internal/backend/azure/azure.go
0% <0%> (-75.35%)
:arrow_down:

internal/backend/swift/swift.go
0% <0%> (-73.9%)
:arrow_down:

internal/backend/gs/gs.go
0% <0%> (-68.96%)
:arrow_down:

internal/backend/swift/config.go
34.37% <0%> (-56.25%)
:arrow_down:

internal/checker/checker.go
68.31% <0%> (-3.67%)
:arrow_down:

internal/archiver/archiver.go
65.2% <0%> (-0.17%)
:arrow_down:

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 f39f7c7...c347431. Read the comment docs.

Hmm, good point. I'm also not sure, but I lean towards using a non-zero exit code in this case.

Cloning into 'restic/restic'...
fatal: unable to access 'https://github.com/restic/restic.git/': Could not resolve host: github.com

This looks like some kind of transitory DNS failure I think.


Deprecate X.C.Prime

Problem Description
XMonad.Config.Prime doesn't work with most extensions and has confused at least one user who stumbled across it. Let's deprecate it now and make it go away in a few versions, since it's unlikely to ever be updated.
Steps to Reproduce
Try to build a config around XMonad.Config.Prime, using extensions beyond anything directly supported by it. X.U.NamedScratchpad and X.U.EZConfig specifically came up.
Configuration File
Please include the smallest full configuration file that reproduces
the problem you are experiencing:
module Main (main) where

import XMonad
import XMonad.Config.Prime

main :: IO ()
main = xmonad $ do
  nothing

Checklist

[x] I've read CONTRIBUTING.md

I tested my configuration

[x] With xmonad version 0.17.0
[x] With xmonad-contrib version 0.17.0

:+1:  Seems like a cool proof of concept, but it also requires a nontrivial effort to keep up-to-date.

And X.C.Monad is even worse.

:+1: from me as well.  We could start the deprecation process (along with starting to take care of #595) once https://github.com/xmonad/xmonad-web/pull/49 is merged

No strong opinion from me. Last time I looked, X.C.Prime seemed somewhat nice, but I've never heard about anyone using it, and if it's actually impossible or impractical to use it, we might as well deprecate it. After all, we've been moving towards extensions having an XConfig a → XConfig a API anyway, which probably makes X.C.Prime unnecessary, right?

Yes. But my main worries are (a) do we even know if this and X.C.Monad have been updated with new fields or defaults added to XConfig? (b) you can use this with most extensions but it's noticeably more painful.

Also X.C.Monad says in its own description "probably broken".


General improvements

What changed?

Most notably, refactored the customQuery function to execute a normal search job so that we can poll it for a status, whereas before we used the export job which doesn't support polling
Validator function now uses regex to find patterns
Added consistent docstrings
converted print statements to use the displayMD function from jupyter_integration_utility
provide suggestion to the user if | table * doesn't exist in the user's search query
cleaned up import statements and organized them
removed unused variables, and renamed some to be more user friendly

This looks good, I want it to be merged.


Make compatible with kitspace.org

Hey, I thought this would be a nice project to add to https://kitspace.org. The idea of Kitspace is to make it as easy as possible to actually build people's open source hardware designs.
All that's required to add your project is to merge this PR. It includes a kitspace.yaml manifest file that helps us find the right files. After you merge the Kitspace page will keep updating with your repo.
Here is a preview of what your project would look like. If you have any questions don't hesitate to ask.

Wow! I didn't know about kitspace but that's got to be the coolest site I've seen in a long time!
Your parts viewer also correctly previews the parts and where they should be placed (I had trouble getting JLC's preview to work correctly with my position file).
Very nice, I'd be happy to add this :)

Thanks, glad you like it :)
It's up now: https://kitspace.org/boards/github.com/bschwind/key-ripper/


User defined error messages with key regions

Suppose I have the following example.toml file:
foo = 1
bar = 2

After parsing this, I'd like to be able to print an error message like:
[error] Key `bar` is not allowed
 --> example.toml
 2 | bar = 2
   | ~~~ here

And I... can't seem to figure out how to make this happen.  toml::key is an alias to std::string and not toml::string, so it loses (and the parser doesn't seem to track) the region information.  I tried to get something close by using toml::get_region( toml::find( data, "bar" ) ) to get the value's region and trying to work backwards in the line from there, but base_region doesn't give me something like location::retrace nor can I construct a new location covering [line_begin(), begin()).
How can I get a source_location describing the location of a key in a table?

Sorry, currently, it does not have the feature you said. To do that, as you pointed out, we need to define toml::key as a struct and add region information in parser. So far, I personally did not need to do that and no one craimed it. That is why it does not have the feature.
I'm now refactoring region related stuff to reduce complexity around it and once I've done it, maybe we would have full control on it. But since the region is an internal component, essentially interface might be changed without anouncement even in a minor release.
Since region of a key seems to be useful feature, so I will consider implementing it in the future release.


[MediaBundle] Bugs after Uploading a new file version

By @pjeroen from https://github.com/sulu-cmf/SuluMediaBundle/issues/72

After uploading a new file version, the previous contents for title, description and tags are deleted.
After confirming, the listview has to be updated, in order to show the new file thumbnail.

Your first bug seems to be fixed, the other one is a duplicate of #770


make processing of multiple thematic_objects for multiple relevant difference asynchronous?

When executing aligner.process() for a series of relevant_distances, a for-loop is executed to loop over all thematic objects; and to loop over all relevant distances. These calculations are indipendent form eachother, so maybe it is an option to do these processin asynchronous, so it results in a faster processing, when doing the calculation for a lot of thematicobjects and relevant distances?

@roefem , what do you think about this one? Could that be an option? pitfalls? It could result in a big performance gain of calculations for 60 distances are started at once instead of executing them one by one?
https://github.com/OnroerendErfgoed/brdr/blob/0c588f46b21c400670390d53a143da0d93b263a4/brdr/aligner.py#L328-L343

My 2c:
I think the way to go here would be relying on shapely's ufunc interfaces to the geos library, which already allow for multithreading/processing outside of python. I'm not sure the current code could be easily refactored in this way though. In essence, this would require us to rewrite the algorithm to do all geometric operations on the arrays of thematic objects instead of using a for loop and processing each item individually.
# this will execute sequentially
for geom in geoms:
   shapely.buffer(geom, 10)

# this will execute in parallel
shapely.buffer(geoms, 10)

Alternatively, we could implementing your own form of multithreading or multiprocessing is, but whether this would be beneficial would depend on the actual CPU usage. Assuming most of our users would be using cPython (and thus be subject to the GIL), you would need to use multiprocessing to leverage more cpu cores. This would create quite a bit of complexity to the code, so the performance gain has to be quite big in order to offset the added complexity to the code base and the performance penalty multiprocessing would bring for single distance use cases. I also doubt the result would be faster than an approach based on the approach outlined above. But the proof of the pudding is in the eating...

We should also consider the possible impact on memory usage, as this will go up as well.

With Threadpoolexecutor:
duration: [28.681322, 14.334717, 12.512052, 13.467091, 30.641785, 32.707651, 12.23049, 13.854096, 14.236291]
Min: 12.23049
Max: 32.707651
Mean: 19.185055
Median: 14.236291
Stdv: 8.705756538000847
without Threadpoolexecutor:
duration: [21.313991, 16.558168, 16.590126, 18.111118, 16.872433, 17.928071, 18.32295, 17.87116, 19.516652, 16.729241]
Min: 16.558168
Max: 21.313991
Mean: 17.981391
Median: 17.8996155
Stdv: 1.504459449440969


Fixing subtype errors

I'm new to Flutter and also on Dartz package but I cannot find any solution online that would answer my question...
What I did is not rocket science, I'm just testing a very simple endpoint that return { message: 'success' } and what I did so far is the following:
class StatusHelper {
  final api = StatusApi();
  Future<Either<Glitch, Status>> getStatus() async {
    final apiResult = await api.getStatus();
    return apiResult.fold((l) {
      return Left(NoInternetGlitch());
    }, (r) {
      final status = Status.fromMap(jsonDecode(r));
      return Right(status);
    });
  }
}

And
class StatusApi {
  String endpoint = 'myApi.net';

  Future<Either<Exception, String>> getStatus() async {
    try {
      final uri = Uri.https(endpoint, 'status').toString();
      final response = await dio.get(uri);
      print('RESPONSE: ${response.data}');
      return Right(response.data);
    } catch (e) {
      print('ERROR: $e');
      return (Left(e));
    }
  }
}

Very simple and it also return the correct data when used.
The point is that I don't like to see errors and warnings on my terminal and I wish to fix every single thing.
Actually, I have the success message and 2 errors when I create the request:
flutter: RESPONSE: {message: success}
flutter: ERROR: type '_InternalLinkedHashMap<String, dynamic>' is not a subtype of type 'String'
[VERBOSE-2:ui_dart_state.cc(186)] Unhandled Exception: type '_TypeError' is not a subtype of type 'Exception'
#0      StatusApi.getStatus (package:flutter_test/models/services/status_api.dart:15:20)
<asynchronous suspension>
#1      StatusHelper.getStatus (package:flutter_test/models/helper/status_helper.dart:11:23)
<asynchronous suspension>

How can I fix those 2 errors?
What I'm doing wrong?
Thanks for your help in advance!

Hi @Torone!
This doesn't look related to dartz. While I don't have access to all the type information, I believe you have multiple type errors in the code above. I would highly recommend using https://pub.dev/packages/pedantic, or better yet, https://pub.dev/packages/extra_pedantic. These packages provide good analyzer settings and should highlight unsafe type assumptions with at least e and response.data above, as well as provide helpful information about the actual types involved.
Hope that helps!

Thanks for your reply and useful hint!


Set Fan speed?

Hello, Thomas,
i have currently built something similar for my home project and found your project while searching for information.
Do you have any idea how I can set values ?
e.g. case fan.
I would be very grateful for your help.

Hi Saul Goodman :-)
sorry for my late answer. I don't saw this issue.
Maybe you can control the fan with the CIM Class Win32_Fan. There is a method setspeed
Get-CimClass -ClassName Win32_Fan | select CimClassMethods
Unfortunately i can't test it, because i don't have fans anymore :-)


Regression: SQLiteException: no such table: maps_1 (code 1)

We had this issue in some previous CBL (think that in 1.2.1). Our app version: 3.6
But it's back after upgrade from 1.3.1-91 to 1.4.4x. Our app version 4.4
http://crashes.to/s/fa605cc8295
Note to self: 5702f8d9ffcdc042506d114f
Fatal Exception: java.lang.RuntimeException: Unable to create application com.droid4you.application.wallet.Application: com.couchbase.lite.internal.database.sqlite.exception.SQLiteException: no such table: maps_1 (code 1): , while compiling: SELECT key, value, docid, revs.sequence FROM 'maps_1', revs, docs WHERE 1 AND revs.sequence = 'maps_1'.sequence AND docs.doc_id = revs.doc_id ORDER BY key, docid LIMIT ? OFFSET ?
       at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4687)
       at android.app.ActivityThread.access$1400(ActivityThread.java:159)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1376)
       at android.os.Handler.dispatchMessage(Handler.java:99)
       at android.os.Looper.loop(Looper.java:176)
       at android.app.ActivityThread.main(ActivityThread.java:5419)
       at java.lang.reflect.Method.invokeNative(Method.java)
       at java.lang.reflect.Method.invoke(Method.java:525)
       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1046)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:862)
       at dalvik.system.NativeStart.main(NativeStart.java)
Caused by com.couchbase.lite.internal.database.sqlite.exception.SQLiteException: no such table: maps_1 (code 1): , while compiling: SELECT key, value, docid, revs.sequence FROM 'maps_1', revs, docs WHERE 1 AND revs.sequence = 'maps_1'.sequence AND docs.doc_id = revs.doc_id ORDER BY key, docid LIMIT ? OFFSET ?
       at com.couchbase.lite.internal.database.sqlite.SQLiteConnection.nativePrepareStatement(SQLiteConnection.java)
       at com.couchbase.lite.internal.database.sqlite.SQLiteConnection.acquirePreparedStatement(SQLiteConnection.java:718)
       at com.couchbase.lite.internal.database.sqlite.SQLiteConnection.prepare(SQLiteConnection.java:431)
       at com.couchbase.lite.internal.database.sqlite.SQLiteSession.prepare(SQLiteSession.java:595)
       at com.couchbase.lite.internal.database.sqlite.SQLiteProgram.(SQLiteProgram.java:64)
       at com.couchbase.lite.internal.database.sqlite.SQLiteQuery.(SQLiteQuery.java:37)
       at com.couchbase.lite.internal.database.sqlite.SQLiteDirectCursorDriver.query(SQLiteDirectCursorDriver.java:48)
       at com.couchbase.lite.internal.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1300)
       at com.couchbase.lite.internal.database.sqlite.SQLiteDatabase.rawQuery(SQLiteDatabase.java:1239)
       at com.couchbase.lite.storage.SQLiteStorageEngineBase.rawQuery(SQLiteStorageEngineBase.java:183)
       at com.couchbase.lite.store.SQLiteViewStore.runQuery(SQLiteViewStore.java:1014)
       at com.couchbase.lite.store.SQLiteViewStore.regularQuery(SQLiteViewStore.java:627)
       at com.couchbase.lite.View.query(View.java:358)
       at com.couchbase.lite.Database.queryViewNamed(Database.java:2469)
       at com.couchbase.lite.Query.run(Query.java:446)

Maybe relevant?  #880, #966, #1008

Hi @mtrakal,
Based on an error message, no such table: maps_1 (code 1):, it seems the issue is related with Arabic issue we fixed. As error message say maps_1, so it indicates that table name generations is fine. I guess that the table was created with previous version of CBL which has Arabic issue,  then upgrade to new one. Then new one try to query, but it can not find map_1 table.

Looks, that users are really Arabic old users. No new users, but have no idea why it start crashing after upgrade to 1.4.4x, because we have there workaround for migration: https://github.com/couchbase/couchbase-lite-android/issues/966#issuecomment-241646746

@mtrakal Thanks for your inputs.

The user uses the app with the old version of CBL which has the bug with Arabic, it created maps_١ table.
The user upgraded the app that includes the newer version of CBL which has the fix. Also, the app increased the view version number to 2 from 1, I believe it recreates map table with maps_1 table name.
However, maps_1 tables does not exist.... SQLiteException...

I guess that view query could be executed before maps table is recreated.

@sethrosetter @raghusarangapani is there a way to run our functional tests with Arabic locale?

@hideki Do you know how to enable Arabic locale?

@raghusarangapani
[Settings] ->[Lanugage & Input]  -> [Language]

I ran the testsuites/listener/shared/client_sg/test_views.py (which calls  /{db}/_design/{doc}) on nexus 6p with Android 7.1.1 with English(US) and Arabic. The test passed, no issues.

@raghusarangapani Is it easy for you to kick of the whole client_sg suite?

Ran the entire client_sg suite against nexus 6p with Android 7.1.1 and Arabic locale. The test passed, no issues.

As test pass, I will close this.


Error when emitting a BOOL param as part of contract event

I have eventeum running in docker using the eventeum/eventeum:latest image. I can receive contract events without a problem. However when I try to subscribe to an event that has a BOOL parameter I get an Unsupported type: bool error.
This is the entry in contractEventFilter :
     {"_id":"LoanStarted","contractAddress":"0x59712F44CDbAD771E8761035C6d3B4A5611c6D7F","node":"default","eventSpecification":{"eventName":"LoanStarted","indexedParameterDefinitions":[],"nonIndexedParameterDefinitions":[{"position":{"$numberInt":"0"},"type":"UINT256"},{"position":{"$numberInt":"1"},"type":"ADDRESS"},{"position":{"$numberInt":"2"},"type":"ADDRESS"},{"position":{"$numberInt":"3"},"type":"UINT256"},{"position":{"$numberInt":"4"},"type":"UINT256"},{"position":{"$numberInt":"5"},"type":"UINT256"},{"position":{"$numberInt":"6"},"type":"UINT256"},{"position":{"$numberInt":"7"},"type":"UINT256"},{"position":{"$numberInt":"8"},"type":"UINT256"},{"position":{"$numberInt":"9"},"type":"ADDRESS"},{"position":{"$numberInt":"10"},"type":"ADDRESS"},{"position":{"$numberInt":"11"},"type":"BOOL"}]},"startBlock":"6267926","_class":"net.consensys.eventeum.dto.event.filter.ContractEventFilter"}`

The event in Solidity looks like this :
event LoanStarted(
    uint256 loanId,
    address borrower,
    address lender,
    uint256 loanPrincipalAmount,
    uint256 maximumRepaymentAmount,
    uint256 nftCollateralId,
    uint256 loanStartTime,
    uint256 loanDuration,
    uint256 loanInterestRateForDurationInBasisPoints,
    address nftCollateralContract,
    address loanERC20Denomination,
    bool interestIsProRated
);

When the event fires I get the following logs in the Eventeum service:
DEBUG net.consensys.eventeum.chain.service.Web3jService: lambda$registerEventListener$0 -
Dispatching log: Log{removed=false, logIndex='0x6', transactionIndex='0x7', transactionHash='0x3934b2643608849ba2b1c83251ad69ee6ea12eb6ac700ad8b9778b5d10c2c9ea', blockHash='0x5174501c37803e7baa66984fc34ab1b98410f7c3b2a1bf586c25c35318f621f5', blockNumber='0x5fa470', address='0x59712f44cdbad771e8761035c6d3b4a5611c6d7f', data='0x0000000000000000000000000000000000000000000000000000000000000001000000000000000000000000f2730c7d84aa9fe0c7bad3fd7ca1e763e3c3f3df000000000000000000000000685d05cafada2e26d8d2df2ea06dc113817735610000000000000000000000000000000000000000000000000de0b6b3a764000000000000000000000000000000000000000000000000000010a741a462780000000000000000000000000000000000000000000000000000000000000000000a000000000000000000000000000000000000000000000000000000005e8b1dc3000000000000000000000000000000000000000000000000000000000000000700000000000000000000000000000000000000000000000000000000ffffffff000000000000000000000000fdf703b22a13f825d348af43d2bfc140054d0e3d000000000000000000000000c778417e063141139fce010982780140aa0cd5ab0000000000000000000000000000000000000000000000000000000000000000', type='null', topics=[0x7a9a95acdaec2726663658ce76ffb4b960ce244a001b3252a5bb3db586e28c1b]}

2020-04-06 12:17:11.096 [pool-3-thread-5] ERROR org.web3j.protocol.core.filters.Filter: lambda$run$25 - Error sending request

rx.exceptions.OnErrorNotImplementedException: Unsupported type: bool

at rx.internal.util.InternalObservableUtils$ErrorNotImplementedAction.call(InternalObservableUtils.java:386) ~[rxjava-1.3.8.jar!/:1.3.8]

at rx.internal.util.InternalObservableUtils$ErrorNotImplementedAction.call(InternalObservableUtils.java:383) ~[rxjava-1.3.8.jar!/:1.3.8]

at rx.internal.util.ActionSubscriber.onError(ActionSubscriber.java:44) ~[rxjava-1.3.8.jar!/:1.3.8]

at rx.observers.SafeSubscriber._onError(SafeSubscriber.java:153) ~[rxjava-1.3.8.jar!/:1.3.8]

at rx.observers.SafeSubscriber.onError(SafeSubscriber.java:115) ~[rxjava-1.3.8.jar!/:1.3.8]

at rx.exceptions.Exceptions.throwOrReport(Exceptions.java:212) ~[rxjava-1.3.8.jar!/:1.3.8]

at rx.observers.SafeSubscriber.onNext(SafeSubscriber.java:139) ~[rxjava-1.3.8.jar!/:1.3.8]

at org.web3j.protocol.core.filters.LogFilter.process(LogFilter.java:39) ~[core-3.6.0.jar!/:na]

at org.web3j.protocol.core.filters.Filter.pollFilter(Filter.java:129) ~[core-3.6.0.jar!/:na]

at org.web3j.protocol.core.filters.Filter.lambda$run$25(Filter.java:83) ~[core-3.6.0.jar!/:na]

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[na:1.8.0_222]

at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) ~[na:1.8.0_222]

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) ~[na:1.8.0_222]

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) ~[na:1.8.0_222]

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[na:1.8.0_222]

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[na:1.8.0_222]

at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_222]

Caused by: net.consensys.eventeum.chain.converter.TypeConversionException: Unsupported type: bool

at net.consensys.eventeum.chain.converter.Web3jEventParameterConverter.convert(Web3jEventParameterConverter.java:53) ~[eventeum-core-0.7.0-RELEASE.jar!/:0.7.0-RELEASE]

at net.consensys.eventeum.chain.converter.Web3jEventParameterConverter.convert(Web3jEventParameterConverter.java:21) ~[eventeum-core-0.7.0-RELEASE.jar!/:0.7.0-RELEASE]

at net.consensys.eventeum.chain.factory.DefaultContractEventDetailsFactory.lambda$typeListToParameterList$0(DefaultContractEventDetailsFactory.java:78) ~[eventeum-core-0.7.0-RELEASE.jar!/:0.7.0-RELEASE]

at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) ~[na:1.8.0_222]

at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382) ~[na:1.8.0_222]

at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482) ~[na:1.8.0_222]

at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472) ~[na:1.8.0_222]

at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708) ~[na:1.8.0_222]

at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) ~[na:1.8.0_222]

at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:566) ~[na:1.8.0_222]

at net.consensys.eventeum.chain.factory.DefaultContractEventDetailsFactory.typeListToParameterList(DefaultContractEventDetailsFactory.java:79) ~[eventeum-core-0.7.0-RELEASE.jar!/:0.7.0-RELEASE]

at net.consensys.eventeum.chain.factory.DefaultContractEventDetailsFactory.createEventDetails(DefaultContractEventDetailsFactory.java:42) ~[eventeum-core-0.7.0-RELEASE.jar!/:0.7.0-RELEASE]

at net.consensys.eventeum.chain.service.Web3jService.lambda$registerEventListener$0(Web3jService.java:109) ~[eventeum-core-0.7.0-RELEASE.jar!/:0.7.0-RELEASE]

at rx.internal.util.ActionSubscriber.onNext(ActionSubscriber.java:39) ~[rxjava-1.3.8.jar!/:1.3.8]

at rx.observers.SafeSubscriber.onNext(SafeSubscriber.java:134) ~[rxjava-1.3.8.jar!/:1.3.8]

... 10 common frames omitted

2020-04-06 12:17:11.096 [pool-3-thread-1] ERROR org.web3j.protocol.core.filters.Filter: lambda$run$25 - Error sending request

Hey Stephen!  From your stack trace, it looks like you're running version 0.7.0 of Eventeum.  This should be fixed in the latest 0.8.0 release.  Try upgrading and let me know if you're still having issues.

Hey, did updating to the latest version fix this issue?

Integration tests cover boolean events so I think this was a versioning issue.   Feel free to reopen if you're still having problems!

Hi there,
Sorry for the late reply. Upgrading to 0.8 worked. I was using the
eventeum/eventeum:latest docker image. I thought that was v 0.8 but turns
out it’s still 0.7 swapping to a different image worked. Thanks
On Sat, 18 Apr 2020 at 00:53, Craig Williams<EMAIL_ADDRESS>wrote:

Closed #127 https://github.com/ConsenSys/eventeum/issues/127.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ConsenSys/eventeum/issues/127#event-3246224340, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAUNXMQP3KS32MYEFSM2YTRNDMVRANCNFSM4MCHVSXQ
.


Low training efficiency and warning "batch_size shortened from 8 to 1, points from 640000 to 80000."

Hello!
Thanks for your great work. I tried to implement your code in my workstation.
I found that the max_batch_points and voxel_max were set to 140000 and 80000 in s3dis_stratified_transformer.yaml, respectively.
And batch_size was set to 8. In this case, the number of points in one batch can easily exceed 14w, say, the maximum is 8w*8=64w.
Maybe that's the reason why I often got this kind of warning,
"WARNING [main-logger]: batch_size shortened from 8 to 1, points from 640000 to 80000."
If I set the batch size to 1, the warning disappears, but less batch size brings more steps. Since I observed a low training speed per step, the overall training efficiency per epoch was poor with the whole S3DIS dataset. Do you have any suggestions to improve it?
I trained some other models like KPConv in my workstation. The training speed was higher and acceptable.
May I know whether the transformer model is relatively low in training efficiency? I am a layman in ML.
Cheers,
Eric.

Thanks for your interest in our work.
First, max_batch_points can be adjusted according to your hardware condition. These two arguments are set to avoid memory explosion. If you are using GPUs whose memory are more than 11G, you can set max_batch_points to a suitable value in your case as long as you have enough GPU memory.
Second, the training speed of the self-attention operator is slower than the convolutional counterpart. But in our model, you can change the training epochs to 50 for quick training (the performance gap with 100 epochs would be within 1.0% mIoU).
Hope these can be helpful.

Thanks for your useful suggestions. Will have a try.

Here is 1 A100 (80GB Memory) GPU's training warning:
WARNING [04/20 14:40:43 main-logger]: batch_size shortened from 16 to 3, points from 901297 to 119988 WARNING [04/20 14:40:44 main-logger]: batch_size shortened from 16 to 3, points from 793041 to 114682 WARNING [04/20 14:40:45 main-logger]: batch_size shortened from 16 to 2, points from 1034501 to 136452 WARNING [04/20 14:40:49 main-logger]: batch_size shortened from 16 to 2, points from 1184282 to 120392 WARNING [04/20 14:40:49 main-logger]: batch_size shortened from 16 to 3, points from 853986 to 134254 WARNING [04/20 14:40:51 main-logger]: batch_size shortened from 16 to 2, points from 1089032 to 130792 WARNING [04/20 14:40:51 main-logger]: batch_size shortened from 16 to 1, points from 1023600 to 80000 WARNING [04/20 14:40:56 main-logger]: batch_size shortened from 16 to 2, points from 938096 to 113808 WARNING [04/20 14:40:56 main-logger]: batch_size shortened from 16 to 1, points from 1057780 to 66051 WARNING [04/20 14:40:58 main-logger]: batch_size shortened from 16 to 1, points from 839600 to 80000 WARNING [04/20 14:40:59 main-logger]: batch_size shortened from 16 to 1, points from 983264 to 72251 WARNING [04/20 14:41:04 main-logger]: batch_size shortened from 16 to 2, points from 1112184 to 123175 WARNING [04/20 14:41:05 main-logger]: batch_size shortened from 16 to 1, points from 1014559 to 63709 WARNING [04/20 14:41:06 main-logger]: batch_size shortened from 16 to 3, points from 887254 to 113941 WARNING [04/20 14:41:09 main-logger]: batch_size shortened from 16 to 2, points from 901949 to 124336 WARNING [04/20 14:41:11 main-logger]: batch_size shortened from 16 to 1, points from 983095 to 80000 WARNING [04/20 14:41:13 main-logger]: batch_size shortened from 16 to 2, points from 1020434 to 128505 WARNING [04/20 14:41:15 main-logger]: batch_size shortened from 16 to 3, points from 1044181 to 105055 WARNING [04/20 14:41:15 main-logger]: batch_size shortened from 16 to 2, points from 844335 to 135936 WARNING [04/20 14:41:16 main-logger]: batch_size shortened from 16 to 2, points from 854786 to 111498 WARNING [04/20 14:41:16 main-logger]: batch_size shortened from 16 to 3, points from 879924 to 112379 WARNING [04/20 14:41:19 main-logger]: batch_size shortened from 16 to 4, points from 952785 to 127065

@yuchenlichuck So you can change the argument max_batch_points in the .yaml file to a much larger value.


Renaming the cask

Hi there! This issue directed to the brew cask command. I think the cask yandex should be yandex-browser to make sure its not another app of this company.

Could you reopen this at https://github.com/caskroom/homebrew-cask? Thanks!


Refactor vitest

This PR is replacing mocha and all of its dependencies and replacing them with vite and vitest.
Tests have been refactored accordingly, while changing their names to include 'spec'.
removed:

@types/mocha
mocha
ts-mocha
should

added:

vite
vitest

Other improvements:

add IDE folders to gitignore

Codecov Report
Patch coverage has no change and project coverage change: +3.14% :tada:

Comparison is base (7d29eb8) 92.67% compared to head (66ec559) 95.81%.
Report is 3 commits behind head on typescript.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@              Coverage Diff               @@
##           typescript       #2      +/-   ##
==============================================
+ Coverage       92.67%   95.81%   +3.14%
==============================================
  Files               5        5
  Lines             191      191
  Branches           42       37       -5
==============================================
+ Hits              177      183       +6
+ Misses             10        6       -4
+ Partials            4        2       -2

see 4 files with indirect coverage changes

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


Parallel Hash Level

We need a concurrent hash table level.

It's not clear yet whether this is a priority. Closing for now


[Imporve] add sequence type header

Proposed changes
add new stream load header : function_column.sequence_col
doc link: https://doris.apache.org/docs/data-operate/update-delete/sequence-column-manual/
Issue Number: close #xxx
Problem Summary:
Describe the overview of changes.
Checklist(Required)

Does it affect the original behavior: (Yes/No/I Don't know)
Has unit tests been added: (Yes/No/No Need)
Has document been added or modified: (Yes/No/No Need)
Does it need to update dependencies: (Yes/No)
Are there any changes that cannot be rolled back: (Yes/No)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

closed : instead of args : "sink.properties.function_column.sequence_col"


What param stylingOptions receive?

In readme.md and demo project don't have any exemple for this param. How configure that?

My problem is: How to change text color programally?


ttt

ansible-playbook local_prepare.yml

Hi, you can run the local_prepare.yml playbook again, if there's no errors, it will download prometheus-2.2.1.tar.gz to the Control Machine /home/tidb/tidb-ansible/downloads directory.


Add new Staking messages and queries under feature flag

Replaces #211
Closes #174
I think everything is now implemented except for the test cases. Happy for a review and feedback,

[x] Add new types
[x] Update CHANGELOG
[x] Generate proper schemas
[x] Add mock Querier support
[ ] Test MockQuerier, especially StakingQuerier

For another PR:

Demo usage in a contract

Note: I like the feature flag approach, as it allows us to downgrade and support non-PoS chains easily (eg. if someone wants to run cosmwasm in a PoA environment or other novel consensus mechanism.). However, I realize that the schemas generated for cosmwasm_std are now incomplete.... We can either generate them with or without staking info.
My idea (which I tentatively did in https://github.com/CosmWasm/cosmwasm/pull/300/commits/a15b22b874dbf754eb388bf97465859e3fea7307) is to make staking on by default and use --no-default-features to disable it, as it will be the case in almost all cosmwasm chains in the near future. And the other chains can just ignore some entries in the schema (rather than having missing specs). Open for more ideas.

I agree with limiting feature flags. I would be careful to add more, but I also think if we get some dynamic check from #301 that maybe we can remove the compiler feature for staking and add that as a runtime argument controlling upload of contracts. I agree this is suboptimal, and we definitely don't want to add 10 more.

@webmaster128 This should be complete now. Let me know what you think.
The actual types we used have been discussed with @yys in #211, so the question is mainly on the organization (and feature flags). As I said above, I would love to remove the feature flag when #301 is in and we have another way to check for optional features.

Thanks for the tips, I will keep the rustdoc more in mind. I really need to set up (and review) the public rustdoc for this package. Would make a nice last-minute pre-0.8 polish.

I will keep the rustdoc more in mind. I really need to set up (and review) the public rustdoc for this package. Would make a nice last-minute pre-0.8 polish.

Any idea if it is possible to publish pre-releases to crates.io? I did not find a possibility without overriding the "latest" version.

Any idea if it is possible to publish pre-releases to crates.io? I did not find a possibility without overriding the "latest" version.

AFAIK the latest version is always taken, so not really a "pre-release". I guess we could call it 0.8.0-alpha or 0.8.0-rc1 if that is what you mean?
We can also check rustdoc locally and make sure the 0.7.2 is published, to prepare for the update, if that is why you are asking.

Publishing a pre-release like 0.8.0-rc1 would be easy. However, we don't want people that do cargo add cosmwasm-std to use that version. But then again, this command does not exist in Rust world and users need to manually add entries to their Cargo.toml, so maybe it does not hurt to publish pre-releases.


Timed out poll connections kill the connection

If a poll connection times out the server throws:
System.InvalidOperationException occurred
  HResult=-2146233079
  Message=Concurrent reads are not supported.
  Source=System.Private.CoreLib
  StackTrace:
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Channels.Channel.Channels.IReadableBufferAwaiter.GetResult()
       at Microsoft.AspNetCore.Sockets.LongPolling.<ProcessRequestAsync>d__3.MoveNext() in C:\source\NetworkingProtoype\src\Microsoft.AspNetCore.Sockets\LongPolling.cs:line 21
  InnerException:

and kills the connection. The client restarts the poll only to get:
GET http://localhost:5000/hubs/poll?id=87085e15-6bb5-492e-850b-f7965c7e9bbc&87085e15-6bb5-492e-850b-f7965c7e9bbc 500 (Internal Server Error)

Fixed


Core 1.3.1 cannot start due to "Newtonsoft.Json.JsonReaderException: Unterminated string. Expected delimiter"

I went to check on my Core wallet and apparently it wasn't running. It hasn't been running since 5 days ago according to the last log. I started Core and the app could not load; I waited for about 10-15 minutes. I check the logs:
[2019-11-26 06:42:24.0456 1] INFO: Stratis.Bitcoin.FullNode.Initialize Full node initialized on StratisMain.
[2019-11-26 06:42:24.1057 1] INFO: Stratis.Bitcoin.FullNode.Start Starting node.
[2019-11-26 06:42:25.0212 1] INFO: Stratis.Bitcoin.Features.Api.ApiFeature.InitializeAsync API starting on URL 'http://localhost:37221/'.
[2019-11-26 06:42:29.2815 1] INFO: Stratis.Bitcoin.Base.BaseFeature+d__30.MoveNext Loading finalized block height.
[2019-11-26 06:42:29.4998 5] INFO: Stratis.Bitcoin.Base.BaseFeature+d__30.MoveNext Loading chain.
[2019-11-26 06:46:09.6715 6] INFO: Stratis.Bitcoin.Base.BaseFeature+d__30.MoveNext Chain loaded at height 1551209.
[2019-11-26 06:46:09.7410 19] INFO: Stratis.Bitcoin.Utilities.AsyncLoop+<>c__DisplayClass20_0+<b__0>d.MoveNext FlushChain starting in 60 seconds.
[2019-11-26 06:46:11.1087 20] INFO: Stratis.Bitcoin.Base.BaseFeature.StartAddressManager Loading peers from : C:\Users\Stratis\AppData\Roaming\StratisNode\stratis\StratisMain.
[2019-11-26 06:46:13.6348 1] ERROR: Stratis.Bitcoin.Builder.FullNodeFeatureExecutor.LogAndAddException An error occurred: 'Newtonsoft.Json.JsonReaderException: Unterminated string. Expected delimiter: ". Path '[32810].endpoint', line 1, position 9966510.
at Newtonsoft.Json.JsonTextReader.ReadStringIntoBuffer(Char quote)
at Newtonsoft.Json.JsonTextReader.ParseValue()
at Newtonsoft.Json.JsonReader.ReadForType(JsonContract contract, Boolean hasConverter)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateObject(Object newObject, JsonReader reader, JsonObjectContract contract, JsonProperty member, String id)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateObject(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateList(IList list, JsonReader reader, JsonArrayContract contract, JsonProperty containerProperty, String id)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateList(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, Object existingValue, String id)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)
at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)
at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)
at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings)
at Stratis.Bitcoin.Utilities.FileStorage1.LoadByFileName(String fileName) in C:\Users\StratisTest\Desktop\DevOps\Agent1\_work\4\s\StratisBitcoinFullNode\src\Stratis.Bitcoin\Utilities\FileStorage.cs:line 193    at Stratis.Bitcoin.P2P.PeerAddressManager.LoadPeers() in C:\Users\StratisTest\Desktop\DevOps\Agent1\_work\4\s\StratisBitcoinFullNode\src\Stratis.Bitcoin\P2P\PeerAddressManager.cs:line 62    at Stratis.Bitcoin.Base.BaseFeature.StartAddressManager(NetworkPeerConnectionParameters connectionParameters) in C:\Users\StratisTest\Desktop\DevOps\Agent1\_work\4\s\StratisBitcoinFullNode\src\Stratis.Bitcoin\Base\BaseFeature.cs:line 290    at Stratis.Bitcoin.Base.BaseFeature.InitializeAsync() in C:\Users\StratisTest\Desktop\DevOps\Agent1\_work\4\s\StratisBitcoinFullNode\src\Stratis.Bitcoin\Base\BaseFeature.cs:line 214    at Stratis.Bitcoin.Builder.FullNodeFeatureExecutor.<>c.<Initialize>b__3_1(IFullNodeFeature service) in C:\Users\StratisTest\Desktop\DevOps\Agent1\_work\4\s\StratisBitcoinFullNode\src\Stratis.Bitcoin\Builder\FullNodeFeatureExecutor.cs:line 56    at Stratis.Bitcoin.Builder.FullNodeFeatureExecutor.Execute(Action1 callback, Boolean disposing) in C:\Users\StratisTest\Desktop\DevOps\Agent1_work\4\s\StratisBitcoinFullNode\src\Stratis.Bitcoin\Builder\FullNodeFeatureExecutor.cs:line 130'
[2019-11-26 06:46:13.6695 1] ERROR: Stratis.Bitcoin.Builder.FullNodeFeatureExecutor.Initialize An error occurred starting the application.
@dev0tion @zeptin @fassadlr any ideas? how do I resolve this issue?

@trunghieud this sounds a lot like your peers.json is corrupt. Try making a copy and deleting the original, then restart the node. And have a look in the file to see if it's a well-formed JSON object.

@rowandh i backup the original file, delete, and restart node. Now it finally started and waiting to sync.
I looked at the backup file and it is corrupted. Toward the end there is just a bunch of “NUL” and “NUI”. I don’t use this system for anything other than staking. I rarely check it. I noticed that windows update was running, updated, and restart the system.
I check the log and no errors. The last block was 1551151. Anything further to troubleshoot?

Thanks, I think that's enough info. I think it's unlikely to have been caused by a bug in the FN.
Probably one of these things:

The machine crashed/restarted/updated while writing the file
The machine ran out of disk space

Got it. It's definitely not running out of disk space. I'll monitor it
closely now. Thanks for taking the quick replies.
On Wed, Nov 27, 2019 at 12:04 AM Rowan de Haas<EMAIL_ADDRESS>wrote:

Thanks, I think that's enough info. I think it's unlikely to have been
caused by a bug in the FN.
Probably one of these things:

The machine crashed/restarted/updated while writing the file
The machine ran out of disk space

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/stratisproject/StratisBitcoinFullNode/issues/4096?email_source=notifications&email_token=AHCW7RFQURN57KCMIPAJGJDQVYSXLA5CNFSM4JRTMAS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFIUUPQ#issuecomment-558975550,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHCW7RFESW4JF4U3OBWNS73QVYSXLANCNFSM4JRTMASQ
.


Fixes #77 by updating to Eigen 3.3.4

The only behavior change is:

Dropped support for determinants of integer matrices

Have you confirmed that removing the ::internal layer is done correctly?  Specifically, it seems that previously Index was a type defined by template as a trait of arbitrary Eigen types, and now it is simply a type in the Eigen namespace.  Did Eigen consolidate to have a single Index type throughout?

Yes, Eigen did consolidate to have a single index type throughout. That type is now ptrdiff_t.


feat(foundryup): robustness checks and shell improvements

Motivation
foundryup is not robust.
make it robust.
Solution
sanity checks and etc.
check_bins_in_use
Introduces a new function, check_bins_in_use which makes sure that something like forge build -w isn't running.
fix check_cmd
also fixes check_cmd output
fix curl/wget
enforce TLS v1.2

[!NOTE]
need_cmd curl actually would prevent wget from running, as the script would error out and there is no if/else logic to fail over to using wget anyway.

really some testing of the scripts should be implemented, however after trying to get Docker container testing added, not willing to just yolo some tests into here


Hidden flag prevents saving of posts

This is a bug
- What is the current behavior?
When attempting to save a new or current post I receive the following error in the console:
Uncaught TypeError: r.componentValidate[e.get(...)] is not a function
    at ControlPane.js:20
    at Le.__iterate (immutable.js:2208)
    at Le.forEach (immutable.js:4383)
    at t.r.validate (ControlPane.js:20)
    at r.handleOnPersist (EntryEditor.js:24)
    at Object.r (ReactErrorUtils.js:26)
    at a (EventPluginUtils.js:85)
    at Object.s [as executeDispatchesInOrder] (EventPluginUtils.js:108)
    at d (EventPluginHub.js:43)
    at m (EventPluginHub.js:54)

When I remove the hidden flag from my layout attribute in my config.yml fixes the issue. https://github.com/bdougie/blog/commit/ff7ace6b51bfc81fed134eed8db4ed3bc2bbd0b0
- If the current behavior is a bug, please provide the steps to reproduce.
I prefer having the hidden flag to not surface layout in the cms
- What is the expected behavior?
This should save a post without an error
- Please mention your node.js, and operating system version.
v0.3.7
node v7
static site generator: middleman
repo: https://github.com/bdougie/blog
I need to work on other things but can dig into this issue later today. I image hidden flags are not being validated.

This commit fixes this https://github.com/netlify/netlify-cms/commit/507b4cb957fd4a211aa03bbc87d17906a7f48e78


Allow overriding of TempDataAttribute key so separate properties can be backed by same TempData value

Need to figure out the scoping / prefix / naming rules for TempData in Razor Pages.

/cc @kichalla you were interested in this as well.

@DamianEdwards ok to close?

We still haven't come up with a need for this so I'm closing it. If we find a scenario where this matters we can bring it back.


failed to bind column for cte with table alias

Describe the bug
with cte as (select 1) select x from cte t(x);
ERROR:  QueryError: Bind error: failed to bind expression: x

Caused by:
  Item not found: Invalid column: x

But this is ok:
dev=> with cte(y) as (select 1) select x from cte t(x);
 x
---
 1
(1 row)

Error message/log
No response
To Reproduce
No response
Expected behavior
No response
How did you deploy RisingWave?
No response
The version of RisingWave
No response
Additional context
found in https://github.com/risingwavelabs/risingwave/issues/5987

dev=> with cte as (select 1) select * from cte t(x);
 ?column?
----------
        1
(1 row)

similar problem
with cte(a) as (select 1,2) select * from cte t(x,y);
 x | ?column?
---+----------
 1 |        2
(1 row)


Add loganconnolly.com to sites.yml

This PR is:

[x] Adding a new domain
[ ] Updating existing domain size
[ ] Changing domain name
[ ] Removing existing domain from list
[ ] Website code changes (512kb.club site)
[ ] Other not listed

[x] I used the uncompressed size of the site
[x] I have included a link to the Cloudflare report
[x] This site is not an ultra lightweight site
[x] The following information is filled identical to the data file

I confirm that I have read the FAQ section, particularly the two red items around minimal pages and inappropriate content and I attest that this site is neither of these things.

[x] Check to confirm

- domain: loganconnolly.com
  url: https://loganconnolly.com/
  size: 33.6
  last_checked: 2024-02-28

Cloudflare Report: https://radar.cloudflare.com/scan/20d25b77-50c2-4cb4-a5e2-eed4482308b6/summary

Thanks!


Fixes failing tests on Windows

Description
Updated DriverServiceTest and let java.nio.file..Paths handle the URI construction
Related Issue
#294
Motivation and Context
Make the tests run on Windows
How Has This Been Tested?
Ran it on Windows x64
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Merged manually due to conflicts.


feat: Show Code in Context

With this change, the messages for code and explanation are re-merged. Thus, the code is shown with syntax highlighting embedded into its original explanation from the LLM. This avoids showing two distinct messages for code and explanation which felt a bit out-of-order.

Nice cleanup! This was bugging me as well


Error occured while reading

    ❌ Error occured while reading /home/kali/.config/whoisxml.conf ⚠ Make sure a valid API Key exists at /home/kali/.config/whoisxml.conf
I can't create a file: whoisxml.conf
how to fix it?
thx.

sudo nano /home/kali/.config/whoisxml.conf

Paste your API key, and you are should be all set.


fault_tolerance_test fails on some systems

Click to expand!
Issue Type
Bug
Source
source
Tensorflow Version
2.7.1
Custom Code
No
OS Platform and Distribution
Linux RHEL 7
Mobile device
No response
Python version
3.9.6
Bazel version
3.7.2
GCC/Compiler version
11.2
CUDA/cuDNN version
11.4.1 / cuDNN <IP_ADDRESS>
GPU model and memory
8 * Tesla A100
Current Behaviour?
When running the test suite during/after the build the test `//tensorflow/python/data/experimental/kernel_tests/service:fault_tolerance_test` fails on this system, while it seemingly passes on another system.
It seems to be very flaky or dependent on the number of CPUs/GPUs. This system has 96 cores and 8 GPUs.
Output is something like
> //tensorflow/python/data/experimental/kernel_tests/service:fault_tolerance_test (2/20 cached) FAILED in 18 out of 20 in 13.5s

Standalone code to reproduce the issue
Run the following build command: `bazel test --config=noaws --config=nogcp --config=nohdfs --compilation_mode=opt --config=opt --subcommands --verbose_failures --jobs=1 --distinct_host_configuration=false --test_output=errors --build_tests_only --local_test_jobs=1 -- //tensorflow/python/data/experimental/kernel_tests/service:fault_tolerance_test`

Relevant log output
======================================================================
FAIL: testAddWorkerMidJob_test_mode_eager_tfapiversion_2 (__main__.FaultToleranceTest)
FaultToleranceTest.testAddWorkerMidJob_test_mode_eager_tfapiversion_2
testAddWorkerMidJob_test_mode_eager_tfapiversion_2(mode='eager', tf_api_version=2)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/tmp/software/TensorFlow/2.7.1-foss-2021b-CUDA-11.4.1/lib/python3.9/site-packages/absl/testing/parameterized.py", line 314, in bound_param_test
    return test_method(self, **testcase_params)
  File "/dev/shm/s3248973-EasyBuild/TensorFlow/2.7.1/foss-2021b-CUDA-11.4.1/tmpBD23m_-bazel-tf/69a307561ec5a7cdace7b5c5a8971ea2/execroot/org_tensorflow/bazel-out/k8-opt/bin/tensorflow/python/data/experimental/kernel_tests/service/fault_tolerance_test.runfiles/org_tensorflow/tensorflow/python/framework/test_combinations.py", line 366, in decorated
    execute_test_method()
  File "/dev/shm/s3248973-EasyBuild/TensorFlow/2.7.1/foss-2021b-CUDA-11.4.1/tmpBD23m_-bazel-tf/69a307561ec5a7cdace7b5c5a8971ea2/execroot/org_tensorflow/bazel-out/k8-opt/bin/tensorflow/python/data/experimental/kernel_tests/service/fault_tolerance_test.runfiles/org_tensorflow/tensorflow/python/framework/test_combinations.py", line 349, in execute_test_method
    test_method(**kwargs_to_pass)
  File "/dev/shm/s3248973-EasyBuild/TensorFlow/2.7.1/foss-2021b-CUDA-11.4.1/tmpBD23m_-bazel-tf/69a307561ec5a7cdace7b5c5a8971ea2/execroot/org_tensorflow/bazel-out/k8-opt/bin/tensorflow/python/data/experimental/kernel_tests/service/fault_tolerance_test.runfiles/org_tensorflow/tensorflow/python/data/experimental/kernel_tests/service/fault_tolerance_test.py", line 220, in testAddWorkerMidJob
    self.assertCountEqual(2 * list(range(num_elements)), results)
AssertionError: Element counts were not equal:

Build output and Test log file of a test with --test_env=CUDA_VISIBLE_DEVICES='1,2,3,4'
See also https://github.com/tensorflow/tensorflow/commit/c08fda5cb7927acb5c20fa031c2d28f80d4a03c5 which disables this test on mac

Hi @Flamefire !
Could you re-test with the below command and let us know .
bazel test --config=noaws --config=nogcp --config=nohdfs --compilation_mode=opt -c opt --subcommands --verbose_failures --jobs=1 --distinct_host_configuration=false --test_output=errors --build_tests_only --local_test_jobs=1 -- //tensorflow/python/data/experimental/kernel_tests/service:fault_tolerance_test
Attached gist in 2.9 for reference.
Thank you!

So the change is: --config=opt replaced by -c opt, correct?
Same issue. I also checked the Bazel output, started a new bash and set up the environment for this test as per the Bazel output, changed the CWD to .../execroot/org_tensorflow/bazel-out/k8-opt/bin and ran tensorflow/python/data/experimental/kernel_tests/service/fault_tolerance_test. Same error.
Ran 41 tests in 19.142s

FAILED (failures=1, errors=6, skipped=22)

From what I can tell the test is faulty. See for example this error log:
ERROR: testRestartWorker_test_mode_eager_tfapiversion_2_usesameport_True_faulttolerantmode_True_workdir_tmpworkdirplaceholder (__main__.FaultToleranceTest)
FaultToleranceTest.testRestartWorker_test_mode_eager_tfapiversion_2_usesameport_True_faulttolerantmode_True_workdir_tmpworkdirplaceholder
testRestartWorker_test_mode_eager_tfapiversion_2_usesameport_True_faulttolerantmode_True_workdir_tmpworkdirplaceholder(mode='eager', tf_api_version=2, use_same_port=True, fault_tolerant_mode=True, work_dir='tmp_work_dir_placeholder')
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/dev/shm/s3248973-EasyBuild/TensorFlow/2.7.1/foss-2021b-CUDA-11.4.1/tmp5xgzay-bazel-tf/69a307561ec5a7cdace7b5c5a8971ea2/execroot/org_tensorflow/bazel-out/k8-opt/bin/tensorflow/python/data/experimental/kernel_tests/service/fault_tolerance_test.runfiles/org_tensorflow/tensorflow/python/data/ops/iterator_ops.py", line 800, in __next__
    return self._next_internal()
  File "/dev/shm/s3248973-EasyBuild/TensorFlow/2.7.1/foss-2021b-CUDA-11.4.1/tmp5xgzay-bazel-tf/69a307561ec5a7cdace7b5c5a8971ea2/execroot/org_tensorflow/bazel-out/k8-opt/bin/tensorflow/python/data/experimental/kernel_tests/service/fault_tolerance_test.runfiles/org_tensorflow/tensorflow/python/data/ops/iterator_ops.py", line 783, in _next_internal
    ret = gen_dataset_ops.iterator_get_next(
  File "/dev/shm/s3248973-EasyBuild/TensorFlow/2.7.1/foss-2021b-CUDA-11.4.1/tmp5xgzay-bazel-tf/69a307561ec5a7cdace7b5c5a8971ea2/execroot/org_tensorflow/bazel-out/k8-opt/bin/tensorflow/python/data/experimental/kernel_tests/service/fault_tolerance_test.runfiles/org_tensorflow/tensorflow/python/ops/gen_dataset_ops.py", line 2845, in iterator_get_next
    _ops.raise_from_not_ok_status(e, name)
  File "/dev/shm/s3248973-EasyBuild/TensorFlow/2.7.1/foss-2021b-CUDA-11.4.1/tmp5xgzay-bazel-tf/69a307561ec5a7cdace7b5c5a8971ea2/execroot/org_tensorflow/bazel-out/k8-opt/bin/tensorflow/python/data/experimental/kernel_tests/service/fault_tolerance_test.runfiles/org_tensorflow/tensorflow/python/framework/ops.py", line 7107, in raise_from_not_ok_status
    raise core._status_to_exception(e) from None  # pylint: disable=protected-access
tensorflow.python.framework.errors_impl.OutOfRangeError: End of sequence [Op:IteratorGetNext]

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/tmp/software/TensorFlow/2.7.1-foss-2021b-CUDA-11.4.1/lib/python3.9/site-packages/absl/testing/parameterized.py", line 314, in bound_param_test
    return test_method(self, **testcase_params)
  File "/dev/shm/s3248973-EasyBuild/TensorFlow/2.7.1/foss-2021b-CUDA-11.4.1/tmp5xgzay-bazel-tf/69a307561ec5a7cdace7b5c5a8971ea2/execroot/org_tensorflow/bazel-out/k8-opt/bin/tensorflow/python/data/experimental/kernel_tests/service/fault_tolerance_test.runfiles/org_tensorflow/tensorflow/python/framework/test_combinations.py", line 366, in decorated
    execute_test_method()
  File "/dev/shm/s3248973-EasyBuild/TensorFlow/2.7.1/foss-2021b-CUDA-11.4.1/tmp5xgzay-bazel-tf/69a307561ec5a7cdace7b5c5a8971ea2/execroot/org_tensorflow/bazel-out/k8-opt/bin/tensorflow/python/data/experimental/kernel_tests/service/fault_tolerance_test.runfiles/org_tensorflow/tensorflow/python/framework/test_combinations.py", line 349, in execute_test_method
    test_method(**kwargs_to_pass)
  File "/dev/shm/s3248973-EasyBuild/TensorFlow/2.7.1/foss-2021b-CUDA-11.4.1/tmp5xgzay-bazel-tf/69a307561ec5a7cdace7b5c5a8971ea2/execroot/org_tensorflow/bazel-out/k8-opt/bin/tensorflow/python/data/experimental/kernel_tests/service/fault_tolerance_test.runfiles/org_tensorflow/tensorflow/python/data/experimental/kernel_tests/service/fault_tolerance_test.py", line 245, in testRestartWorker
    val = next(iterator).numpy()
  File "/dev/shm/s3248973-EasyBuild/TensorFlow/2.7.1/foss-2021b-CUDA-11.4.1/tmp5xgzay-bazel-tf/69a307561ec5a7cdace7b5c5a8971ea2/execroot/org_tensorflow/bazel-out/k8-opt/bin/tensorflow/python/data/experimental/kernel_tests/service/fault_tolerance_test.runfiles/org_tensorflow/tensorflow/python/data/ops/iterator_ops.py", line 802, in __next__
    raise StopIteration
StopIteration

So we have a raise StopIteration in a __next__ function which is a valid (Python) way to signal the end-of-sequence. Going up the stack to the val = next(iterator).numpy() line we have this code https://github.com/tensorflow/tensorflow/blob/v2.7.1/tensorflow/python/data/experimental/kernel_tests/service/fault_tolerance_test.py#L242-L247 or in master https://github.com/tensorflow/tensorflow/blob/51fe2b12452415e9a96751b5e5df0c8567f6c561/tensorflow/python/data/experimental/kernel_tests/service/fault_tolerance_test.py#L239-L244
So there the comment clearly states "There may have been some elements prefetched from the first worker before it was stopped." yet it unconditionally(!) calls next(iterator) in a while True loop
Not only is that code better written as while next(iterator).numpy() != 0 but the case that the iterator is exhausted before it returns 0 isn't handled at all! So better would be:
# For loops handle StopIteration and call `next` already
for val in iterator:
    if val.numpy() == 0:
        break

To further investigate this I added print statements to the loops at https://github.com/tensorflow/tensorflow/blob/51fe2b12452415e9a96751b5e5df0c8567f6c561/tensorflow/python/data/experimental/kernel_tests/service/fault_tolerance_test.py#L234 and https://github.com/tensorflow/tensorflow/blob/51fe2b12452415e9a96751b5e5df0c8567f6c561/tensorflow/python/data/experimental/kernel_tests/service/fault_tolerance_test.py#L242 to print out the values from next(iterator)
The first loop prints out tensors with 0-49, the 2nd 50-99. So it looks like the comment "The dataset starts over now that we read from the new worker." doesn't seem to hold: The dataset continues till the end.
I'm not sure where the mistake is and what the expected behavior should be. To me it looks like the fault tolerance works very well: The dataset is not disturbed by the worker restart (if that really happens)
I hope that helps

Hi @gadagashwini !
Could you look at this issue, Attached 2.7 , 2.8, 2.9 and nightly gist for reference (--config=opt is not working rather than - c opt)
Thank you!

Hi @Flamefire ,
The PR proposed by you has been merged.Is it good to to close the issue now? Please check and confirm. Thanks!

@SuryanarayanaY I haven't proposed a PR to tensorflow to fix this issue so this is (likely) still an issue which needs investigation and a fix. See my comment above:

I'm not sure where the mistake is and what the expected behavior should be. To me it looks like the fault tolerance works very well: The dataset is not disturbed by the worker restart (if that really happens)

If you were referring to https://github.com/easybuilders/easybuild-easyconfigs/pull/15882: This is a PR against something using TF were in order to run the tests I disabled the test which is seemingly broken as reported in this issue. So that is only a workaround and not even to TF so the issue in TF is unaffected by that PR.

@Flamefire ,
Could you please confirm whether this issue is specific to RHEL7 or to your particular system with the mentioned CPUs and GPUs?I can see you mentioned that the test passes in other system.
Please also confirm if this is still an issue with latest version ?
Also currently TF supports Ubuntu Linux instructions officially as per this source.

Hi,
Thank you for opening this issue. Since this issue has been open for a long time, the code/debug information for this issue may not be relevant with the current state of the code base.
The Tensorflow team is constantly improving the framework by fixing bugs and adding new features. We suggest you try the latest TensorFlow version with the latest compatible hardware configuration which could potentially resolve the issue. If you are still facing the issue, please create a new GitHub issue with your latest findings, with all the debugging information which could help us investigate.
Please follow the release notes to stay up to date with the latest developments which are happening in the Tensorflow space.