[arm-trafficmanager] Fix linter validation 2017-03-01

PR Swagger Modeling comments: https://github.com/Azure/azure-rest-api-specs/pull/1180 to be addressed.
++
Command: autorest --azure-arm=true --input-file=arm-trafficmanager/2017-05-01/swagger/trafficmanager.json --message-format=json
Travis-CI: https://travis-ci.org/Azure/azure-rest-api-specs/jobs/232921454#L1765
Validation Results:
[
{
  "type": "Error",
  "code": "OperationsAPIImplementationValidation",
  "message": "Operations API must be implemented for '/providers/Microsoft.Network/operations'.",
  "id": "M3023",
  "validationCategory": "RPCViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:17:2 ($.paths)"
  ]
}
{
  "type": "Error",
  "code": "PutResponseResourceValidation",
  "message": "The 200 response model for an ARM PUT operation must have x-ms-azure-resource extension set to true in its hierarchy. Operation: 'Endpoints_CreateOrUpdate' Model: 'Endpoint'.",
  "id": "M2062",
  "validationCategory": "RPCViolation",
  "providerNamespace": "Microsoft.Network",
  "resourceType": "trafficmanagerprofiles",
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:142:6 ($.paths[\"/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/trafficmanagerprofiles/{profileName}/{endpointType}/{endpointName}\"].put)"
  ]
}
{
  "type": "Error",
  "code": "XmsExamplesProvidedValidation",
  "message": "Please provide x-ms-examples describing minimum/maximum property set for response/request payloads for operations.",
  "id": "M2022",
  "validationCategory": "SDKViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:17:2 ($.paths)"
  ]
}
{
  "type": "Error",
  "code": "ResourceModelValidation",
  "message": "Model definition 'Endpoint' must have the properties 'name', 'id' and 'type' in its hierarchy and these properties must be marked as readonly.",
  "id": "M2020",
  "validationCategory": "RPCViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:682:4 ($.definitions.Endpoint)"
  ]
}
{
  "type": "Warning",
  "code": "DescriptionMissing",
  "message": "'SubResource' model/property lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation.",
  "id": "M4000",
  "validationCategory": "SDKViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:925:4 ($.definitions.SubResource)"
  ]
}
{
  "type": "Warning",
  "code": "DescriptionMissing",
  "message": "'CloudError' model/property lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation.",
  "id": "M4000",
  "validationCategory": "SDKViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:934:4 ($.definitions.CloudError)"
  ]
}
{
  "type": "Warning",
  "code": "DescriptionMissing",
  "message": "'CloudErrorBody' model/property lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation.",
  "id": "M4000",
  "validationCategory": "SDKViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:939:4 ($.definitions.CloudErrorBody)"
  ]
}
{
  "type": "Warning",
  "code": "BooleanPropertyNotRecommended",
  "message": "Booleans are not descriptive and make them hard to use. Instead use string enums with allowed set of values defined.",
  "id": "M3018",
  "validationCategory": "RPCViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:626:8 ($.definitions.DeleteOperationResult.properties.boolean)"
  ]
}
{
  "type": "Warning",
  "code": "DescriptionMissing",
  "message": "'properties' model/property lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation.",
  "id": "M4000",
  "validationCategory": "SDKViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:696:8 ($.definitions.Endpoint.properties.properties)"
  ]
}
{
  "type": "Warning",
  "code": "DescriptionMissing",
  "message": "'properties' model/property lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation.",
  "id": "M4000",
  "validationCategory": "SDKViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:801:8 ($.definitions.Profile.properties.properties)"
  ]
}
{
  "type": "Warning",
  "code": "BooleanPropertyNotRecommended",
  "message": "Booleans are not descriptive and make them hard to use. Instead use string enums with allowed set of values defined.",
  "id": "M3018",
  "validationCategory": "RPCViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:835:8 ($.definitions.TrafficManagerNameAvailability.properties.nameAvailable)"
  ]
}
{
  "type": "Warning",
  "code": "DescriptionMissing",
  "message": "'properties' model/property lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation.",
  "id": "M4000",
  "validationCategory": "SDKViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:881:8 ($.definitions.TrafficManagerGeographicHierarchy.properties.properties)"
  ]
}
{
  "type": "Warning",
  "code": "DescriptionMissing",
  "message": "'error' model/property lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation.",
  "id": "M4000",
  "validationCategory": "SDKViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:936:22 ($.definitions.CloudError.properties.error)"
  ]
}
{
  "type": "Warning",
  "code": "DescriptionMissing",
  "message": "'code' model/property lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation.",
  "id": "M4000",
  "validationCategory": "SDKViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:942:8 ($.definitions.CloudErrorBody.properties.code)"
  ]
}
{
  "type": "Warning",
  "code": "DescriptionMissing",
  "message": "'message' model/property lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation.",
  "id": "M4000",
  "validationCategory": "SDKViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:943:8 ($.definitions.CloudErrorBody.properties.message)"
  ]
}
{
  "type": "Warning",
  "code": "DescriptionMissing",
  "message": "'target' model/property lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation.",
  "id": "M4000",
  "validationCategory": "SDKViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:944:8 ($.definitions.CloudErrorBody.properties.target)"
  ]
}
{
  "type": "Warning",
  "code": "DescriptionMissing",
  "message": "'details' model/property lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation.",
  "id": "M4000",
  "validationCategory": "SDKViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:945:8 ($.definitions.CloudErrorBody.properties.details)"
  ]
}
{
  "type": "Error",
  "code": "SecurityDefinitionsStructureValidation",
  "message": "Every swagger/configuration must have a security definitions section and it must adhere to the structure described in: https://github.com/Azure/autorest/tree/master/docs/developer/validation-rules/security-definitions-structure-validation.md",
  "id": "M2054",
  "validationCategory": "SDKViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:1:0 ($)"
  ]
}
An error occurred while running the linter on arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:
{ Error: Command failed: autorest --azure-arm=true --input-file=arm-trafficmanager/2017-05-01/swagger/trafficmanager.json --message-format=json
{
  "type": "Error",
  "code": "OperationsAPIImplementationValidation",
  "message": "Operations API must be implemented for '/providers/Microsoft.Network/operations'.",
  "id": "M3023",
  "validationCategory": "RPCViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:17:2 ($.paths)"
  ]
}
{
  "type": "Error",
  "code": "PutResponseResourceValidation",
  "message": "The 200 response model for an ARM PUT operation must have x-ms-azure-resource extension set to true in its hierarchy. Operation: 'Endpoints_CreateOrUpdate' Model: 'Endpoint'.",
  "id": "M2062",
  "validationCategory": "RPCViolation",
  "providerNamespace": "Microsoft.Network",
  "resourceType": "trafficmanagerprofiles",
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:142:6 ($.paths[\"/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/trafficmanagerprofiles/{profileName}/{endpointType}/{endpointName}\"].put)"
  ]
}
{
  "type": "Error",
  "code": "XmsExamplesProvidedValidation",
  "message": "Please provide x-ms-examples describing minimum/maximum property set for response/request payloads for operations.",
  "id": "M2022",
  "validationCategory": "SDKViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:17:2 ($.paths)"
  ]
}
{
  "type": "Error",
  "code": "ResourceModelValidation",
  "message": "Model definition 'Endpoint' must have the properties 'name', 'id' and 'type' in its hierarchy and these properties must be marked as readonly.",
  "id": "M2020",
  "validationCategory": "RPCViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:682:4 ($.definitions.Endpoint)"
  ]
}
{
  "type": "Warning",
  "code": "DescriptionMissing",
  "message": "'SubResource' model/property lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation.",
  "id": "M4000",
  "validationCategory": "SDKViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:925:4 ($.definitions.SubResource)"
  ]
}
{
  "type": "Warning",
  "code": "DescriptionMissing",
  "message": "'CloudError' model/property lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation.",
  "id": "M4000",
  "validationCategory": "SDKViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:934:4 ($.definitions.CloudError)"
  ]
}
{
  "type": "Warning",
  "code": "DescriptionMissing",
  "message": "'CloudErrorBody' model/property lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation.",
  "id": "M4000",
  "validationCategory": "SDKViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:939:4 ($.definitions.CloudErrorBody)"
  ]
}
{
  "type": "Warning",
  "code": "BooleanPropertyNotRecommended",
  "message": "Booleans are not descriptive and make them hard to use. Instead use string enums with allowed set of values defined.",
  "id": "M3018",
  "validationCategory": "RPCViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:626:8 ($.definitions.DeleteOperationResult.properties.boolean)"
  ]
}
{
  "type": "Warning",
  "code": "DescriptionMissing",
  "message": "'properties' model/property lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation.",
  "id": "M4000",
  "validationCategory": "SDKViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:696:8 ($.definitions.Endpoint.properties.properties)"
  ]
}
{
  "type": "Warning",
  "code": "DescriptionMissing",
  "message": "'properties' model/property lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation.",
  "id": "M4000",
  "validationCategory": "SDKViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:801:8 ($.definitions.Profile.properties.properties)"
  ]
}
{
  "type": "Warning",
  "code": "BooleanPropertyNotRecommended",
  "message": "Booleans are not descriptive and make them hard to use. Instead use string enums with allowed set of values defined.",
  "id": "M3018",
  "validationCategory": "RPCViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:835:8 ($.definitions.TrafficManagerNameAvailability.properties.nameAvailable)"
  ]
}
{
  "type": "Warning",
  "code": "DescriptionMissing",
  "message": "'properties' model/property lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation.",
  "id": "M4000",
  "validationCategory": "SDKViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:881:8 ($.definitions.TrafficManagerGeographicHierarchy.properties.properties)"
  ]
}
{
  "type": "Warning",
  "code": "DescriptionMissing",
  "message": "'error' model/property lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation.",
  "id": "M4000",
  "validationCategory": "SDKViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:936:22 ($.definitions.CloudError.properties.error)"
  ]
}
{
  "type": "Warning",
  "code": "DescriptionMissing",
  "message": "'code' model/property lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation.",
  "id": "M4000",
  "validationCategory": "SDKViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:942:8 ($.definitions.CloudErrorBody.properties.code)"
  ]
}
{
  "type": "Warning",
  "code": "DescriptionMissing",
  "message": "'message' model/property lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation.",
  "id": "M4000",
  "validationCategory": "SDKViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:943:8 ($.definitions.CloudErrorBody.properties.message)"
  ]
}
{
  "type": "Warning",
  "code": "DescriptionMissing",
  "message": "'target' model/property lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation.",
  "id": "M4000",
  "validationCategory": "SDKViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:944:8 ($.definitions.CloudErrorBody.properties.target)"
  ]
}
{
  "type": "Warning",
  "code": "DescriptionMissing",
  "message": "'details' model/property lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation.",
  "id": "M4000",
  "validationCategory": "SDKViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:945:8 ($.definitions.CloudErrorBody.properties.details)"
  ]
}
{
  "type": "Error",
  "code": "SecurityDefinitionsStructureValidation",
  "message": "Every swagger/configuration must have a security definitions section and it must adhere to the structure described in: https://github.com/Azure/autorest/tree/master/docs/developer/validation-rules/security-definitions-structure-validation.md",
  "id": "M2054",
  "validationCategory": "SDKViolation",
  "providerNamespace": null,
  "resourceType": null,
  "sources": [
    "file:///home/travis/build/Azure/azure-rest-api-specs/arm-trafficmanager/2017-05-01/swagger/trafficmanager.json:1:0 ($)"
  ]
}
]

cc:
@vladca

clean old issue which may not valid any more


[Bug]: gemini-streamlit-cloudrun - default service account isn't granted correct permissions leading to failure

File Name
gemini/sample-apps/gemini-streamlit-cloudrun/README.md
What happened?
The command gcloud builds submit --tag "$GCP_REGION-docker.pkg.dev/$GCP_PROJECT/$AR_REPO/$SERVICE_NAME" fails as the default service account isn't granted the following permissions:

storage.objects.list access to the Google Cloud Storage bucket. Permission 'storage.objects.list' denied on resource (or it may not exist).
Permission "artifactregistry.repositories.uploadArtifacts" denied on resource

I used a new project that did not manually configure a service account. Once I granted the appropriate permissions to the default service account, the build was able to continue.
Relevant log output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

The default service account gets created with the correct permissions if the SETUP.md file was run before executing some of the commands. This is mentioned in the README.md file. Please check if this was done.


Update logback-classic, logback-core to 1.5.0

About this PR
📦 Updates

ch.qos.logback:logback-classic
ch.qos.logback:logback-core

from 1.2.13 to 1.5.0
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "ch.qos.logback" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "ch.qos.logback" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #529.


Git ignore

Questions on 'give-me-an-overview' seems like there should be an easier way to do that


WAD crash report

Hi,
Attach application error and .NET runtime crash details, not sure why they occur
Faulting application name: WinAppDriver.exe, version: 1.1.1809.18001, time stamp: 0x5ba1465c
Faulting module name: WinAppDriverCore.dll, version: 1.1.1809.18001, time stamp: 0x5ba1464e
Exception code: 0xc0000005
Fault offset: 0x0007e032
Faulting process id: 0x3508
Faulting application start time: 0x01d70ea09310b99c
Faulting application path: C:\Program Files (x86)\Windows Application Driver\WinAppDriver.exe
Faulting module path: C:\Program Files (x86)\Windows Application Driver\WinAppDriverCore.dll
Report Id: 5451f6a9-0e30-45c8-bec6-be981d5f1a5c
Faulting package full name:
Faulting package-relative application ID:
Application: WinAppDriver.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 6F33E032
Stack:

I am having the same issue occasionally WinAppDriver closes. The CMD window for it disappears but you cannot launch WinAppDriver again because it obviously "thinks" it's still running and WinAppDriver cannot run more than once.


Add ActionAndFuncDelegates-By<EMAIL_ADDRESS>

Evaluation article by Daniel LAURENS
Object: Action and Func delegates
Source code

Reopened to add tests

Reopened to add tests


Don't use isSnapshot because it is not reliable (fix #95)

sbt-dynver can set isSnapshot to true even when the version is not able to upload to sonatype snapshot repository.

Good. Thanks for the fix.

Continuing from https://github.com/xerial/sbt-sonatype/issues/95#issuecomment-531732325, you could use:
isVersionStable.?.value.getOrElse(isSnapshot.value)

Good to know that: Defining an empty setting interface of isVersionStable to pass sbt compilation, and let plugin define it.

Feel like redefining extern symbols in a C header.
Taro L. Saito<EMAIL_ADDRESS>周一上午8:55写道：

Good to know that: Defining an empty setting interface of isVersionStable
to pass sbt compilation, and let plugin define it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/xerial/sbt-sonatype/pull/96?email_source=notifications&email_token=AAES3ORZMLANTGLE773WRMDQJ6UAJA5CNFSM4IUMJFC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6ZT4SI#issuecomment-531840585,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAES3OWUAEV3JOJYLDCBLYDQJ6UAJANCNFSM4IUMJFCQ
.


Research if USB device ID's for Finch/Turtle can be built into VM image

Doesn't appear to be part of the appliance spec. Could be documented, but can't be packaged.


[Enhancement] Graph List not updated in dropdown Menu after compilation of Create_graph

When we want to create a new graph, then should compile below command-

[ ] SELECT * FROM ag_catalog.create_graph('graph_name');
After successfully comiping,  new graph has been created but not shown in dropdown menu. such as-

But if we reload age-viewer, then the new graph has shown on that dropdown menu. such as-

So that, this feature should be implemented so that after compiling query, graph should be shown on that menu without refresh or redirect.

Actually it was the purpose of refresh button to perform that functionality but overall I have created a pull request for that at #132


German umlauts (äöüÄÖÜß) in Obsidian and coding of german.dic

Thanks for your great plugin, which I currently have installed.
When I want to write for example "Vorwürfe", I get "Vorw�rfe" shown in the list and inserted in the text. Some UTF-8 issue, I guess.
I use the german dictionary german.dic from https://sourceforge.net/projects/germandict/ I tried to open it in Notepad++. Regardless of the coding (ansi or utf-8) I see all german umlauts as they are (äöüÄÖÜß). I converted the file to utf-8, imported it again with your plugin but the problem remained the same in Obsidian.
When I activate "ignore diacritics when filtering" and try to write "Würfelaugen" (a word, which exists in the dictionary), I didn't get it in the list.
Then I went to P:\Obsidian.obsidian\plugins\obsidian-completr\wordLists\german.dic and changed the existing file to my utf-8 coded file. And it works. ;-)

Windows 10, latest with 16GB RAM
Obsidian, latest 1.0.3
Your plugin, latest
.obsidian/plugins/obsidian-completr/wordLists/german.dic

Hope, that helps you to do something that makes it easier to use your plugin with german texts.

Looks like the german.dic file uses windows-1252 encoding, which I didn't notice before. I added some code which tries to detect the encoding and then performs a conversion. This should work with this file at least. c00a4a6e7e90d93f6ec5168cd631da21d1c8df86


Install push-jobs client failed: packagecloud_repo[imeyer/runit] (runit::default line 36) had an error

Cookbook version
runit (3.0.0)
Chef-client version
Chef: 12.13.37
Platform Details
Centos 6
Scenario:
After i upload the push-jobs cookbook to my server, and when i use chef-client command to configure the node, it occurs below error. As i know it's a network issue, but this is a network policy of my company, I can access the packagecloud.io by web, but not with ping, do you have any way to avoid this error ?

Recipe: yum-epel::default
* yum_repository[epel] action create
* template[/etc/yum.repos.d/epel.repo] action create (up to date)
* execute[yum clean metadata epel] action nothing (skipped due to action :nothing)
* execute[yum-makecache-epel] action nothing (skipped due to action :nothing)
* ruby_block[yum-cache-reload-epel] action nothing (skipped due to action :nothing)
(up to date)
Recipe: runit::default
* packagecloud_repo[imeyer/runit] action add
  ================================================================================
  Error executing action `add` on resource 'packagecloud_repo[imeyer/runit]'
  ================================================================================

  Errno::ENETUNREACH
  ------------------
  Network is unreachable - connect(2) for "packagecloud.io" port 443

Steps to Reproduce:
Expected Result:
install push-jobs successfully.
Actual Result:
failed with the whole error.
[root@delta opt]# chef-client
Starting Chef Client, version 12.13.37
resolving cookbooks for run list: ["push-jobs"]
Synchronizing Cookbooks:

push-jobs (3.2.2)
runit (3.0.0)
packagecloud (0.2.5)
yum-epel (1.0.1)
yum (4.0.0)
chef-ingredient (0.21.0)
compat_resource (12.14.7)
Installing Cookbook Gems:
Compiling Cookbooks...
Converging 5 resources
Recipe: push-jobs::package

remote_file[/var/chef/cache/push-jobs-client-2.1.1-1.el6.x86_64.rpm] action create (up to date)
chef_ingredient[push-jobs-client] action install
Recipe:

chef_gem[mixlib-install] action install (up to date)
ruby_block[stop chef run] action nothing (skipped due to action :nothing)
yum_package[push-jobs-client] action install (up to date)
(up to date)
Recipe: push-jobs::config

directory[/etc/chef] action create (up to date)
template[/etc/chef/push-jobs-client.rb] action create (up to date)
Recipe: push-jobs::service
push_jobs_service_runit[push-jobs] action start[2016-09-27T18:54:51+08:00] WARN: Cloning resource attributes for runit_service[chef-push-jobs-client] from prior resource (CHEF-3694)
Previous runit_service[chef-push-jobs-client]: /var/chef/cache/cookbooks/push-jobs/resources/service_runit.rb:87:in create_init' Current  runit_service[chef-push-jobs-client]: /var/chef/cache/cookbooks/push-jobs/resources/service_runit.rb:28:in block in class_from_file' at /var/chef/cache/cookbooks/push-jobs/resources/service_runit.rb:28:in `block in class_from_file'

Recipe: runit::default
* service[runit] action nothing (skipped due to action :nothing)
* execute[start-runsvdir] action nothing (skipped due to action :nothing)
Recipe: yum-epel::default
* yum_repository[epel] action create
* template[/etc/yum.repos.d/epel.repo] action create (up to date)
* execute[yum clean metadata epel] action nothing (skipped due to action :nothing)
* execute[yum-makecache-epel] action nothing (skipped due to action :nothing)
* ruby_block[yum-cache-reload-epel] action nothing (skipped due to action :nothing)
(up to date)
Recipe: runit::default
* packagecloud_repo[imeyer/runit] action add
  ================================================================================
  Error executing action `add` on resource 'packagecloud_repo[imeyer/runit]'
  ================================================================================

  Errno::ENETUNREACH
  ------------------
  Network is unreachable - connect(2) for "packagecloud.io" port 443

  Cookbook Trace:
  ---------------
  /var/chef/cache/cookbooks/packagecloud/libraries/helper.rb:14:in `get'
  /var/chef/cache/cookbooks/packagecloud/providers/repo.rb:80:in `install_rpm'
  /var/chef/cache/cookbooks/packagecloud/providers/repo.rb:12:in `block in class_from_file'
  /var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:78:in `run_action'
  /var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:106:in `block (2 levels) in converge'
  /var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:106:in `each'
  /var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:106:in `block in converge'
  /var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:105:in `converge'
  /var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/copied_from_chef/chef/provider.rb:133:in `compile_and_converge_action'
  /var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:78:in `run_action'
  /var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:106:in `block (2 levels) in converge'
  /var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:106:in `each'
  /var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:106:in `block in converge'
  /var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:105:in `converge'

  Resource Declaration:
  ---------------------
  # In /var/chef/cache/cookbooks/runit/recipes/default.rb

   36:     packagecloud_repo 'imeyer/runit' do
   37:       force_os 'rhel' if node['platform'].eql?('oracle')
   38:     end
   39:   end

  Compiled Resource:
  ------------------
  # Declared in /var/chef/cache/cookbooks/runit/recipes/default.rb:36:in `from_file'

  packagecloud_repo("imeyer/runit") do
    action [:add]
    retries 0
    retry_delay 2
    default_guard_interpreter :default
    declared_type :packagecloud_repo
    cookbook_name "runit"
    recipe_name "default"
    type "rpm"
    base_url "https://packagecloud.io"
    repository "imeyer/runit"
  end

  Platform:
  ---------
  x86_64-linux

================================================================================
Error executing action `start` on resource 'push_jobs_service_runit[push-jobs]'
================================================================================

Errno::ENETUNREACH
------------------
packagecloud_repo[imeyer/runit] (runit::default line 36) had an error: Errno::ENETUNREACH: Network is unreachable - connect(2) for "packagecloud.io" port 443

Cookbook Trace:
---------------
/var/chef/cache/cookbooks/packagecloud/libraries/helper.rb:14:in `get'
/var/chef/cache/cookbooks/packagecloud/providers/repo.rb:80:in `install_rpm'
/var/chef/cache/cookbooks/packagecloud/providers/repo.rb:12:in `block in class_from_file'
/var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:78:in `run_action'
/var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:106:in `block (2 levels) in converge'
/var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:106:in `each'
/var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:106:in `block in converge'
/var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:105:in `converge'
/var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/copied_from_chef/chef/provider.rb:133:in `compile_and_converge_action'
/var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:78:in `run_action'
/var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:106:in `block (2 levels) in converge'
/var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:106:in `each'
/var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:106:in `block in converge'
/var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:105:in `converge'

Resource Declaration:
---------------------
# In /var/chef/cache/cookbooks/push-jobs/recipes/service.rb

 29:   push_jobs_service 'push-jobs' do
 30:     action [:start, :enable]
 31:     subscribes :restart, "template[#{PushJobsHelper.config_path}]"
 32:   end
 33: end

Compiled Resource:
------------------
# Declared in /var/chef/cache/cookbooks/push-jobs/recipes/service.rb:29:in `from_file'

push_jobs_service_runit("push-jobs") do
  action [:start, :enable]
  retries 0
  retry_delay 2
  default_guard_interpreter :default
  declared_type :push_jobs_service
  cookbook_name "push-jobs"
  recipe_name "service"
end

Platform:
---------
x86_64-linux

Running handlers:
[2016-09-27T18:54:54+08:00] ERROR: Running exception handlers
Running handlers complete
[2016-09-27T18:54:54+08:00] ERROR: Exception handlers complete
Chef Client failed. 0 resources updated in 09 seconds
[2016-09-27T18:54:55+08:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
[2016-09-27T18:54:55+08:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
[2016-09-27T18:54:55+08:00] ERROR: push_jobs_service_runit[push-jobs] (push-jobs::service line 29) had an error: Errno::ENETUNREACH: packagecloud_repo[imeyer/runit] (runit::default line 36) had an error: Errno::ENETUNREACH: Network is unreachable - connect(2) for "packagecloud.io" port 443
[2016-09-27T18:54:55+08:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

+1
This will also lead to failures in all air-gapped and vpc environments w/o access to internet or doing some odd routing gymnastics.

Finally, after i changing the routing policy of my machine by adding packagecloud.io(<IP_ADDRESS>) to our router, this issue has been avoided.


ZED camera error - Camera already in use

Hello,
We are trying to connect ZED stereo cam with our new Ubuntu PC (Please note that it works fine with our previous machine).
The camera is detected, but we end up with an error in Camera test (ZED Diagnostic):
Camera already in use
Several program cannot use ZED at the same time, make sure to close them.

The config currently used is:
Ubuntu - 4.15.0-46-generic #49~16.04.1-Ubuntu SMP  x86_64 x86_64 x86_64 GNU/Linux
CUDA Toolkit version: "V10.0.130"
ZED SDK - ZED_SDK_Ubuntu16_v2.7.1
Also please find the Diagnostic results file attached:
ZED_Diagonistic_Results.txt
Thank you,
Subodh

Hi,
I have the same problem over here.
Ubuntu - <IP_ADDRESS>-generic -- 16.04
CUDA Tookit version: 9.0
ZED SDK - 2.8
The camera works only the first time.
Context:

Connect the camera
Open the ZED Explorer
The camera works fine and I can see the video
Close the ZED Explorer
Open the ZED Explorer again or any other program which open the camera.
The camera doesn't work anymore and the diagnostic tool indicates that the camera is already in use and Several program cannot use the ZED...

I'm using the latest available firmware.

Same issue for me. Ubuntu 16 + CUDA 9.
No program is using the camera but ZED Diagnostic still says 'camera in use'.

Same issue too. Ubuntu 16.04 CUDA 10.0, ZED SDK 2.8
The ZED explorer is frozen even if no camera is running.

Running multiple cameras  in ubuntu 16 cuda 8  with any linux kernel newer than 4.9  causes problems and works only with kernal 4.9.70. I thought the issue will be fixed when upgrading the system to ubuntu 18, kernal 4.18.0 and cuda 10. And upgrading zed sdk from 2.2.0 to 2.8.1 and firmware of cameras to latest. Unfortunately  error "process is already in use" still happening when connecting 3 cameras and i had to revert back to kernal 4.9.70 to fix it. Any explanation?

After you open the zed camera, like say in python, you have to close it before you can open it again.
In my case, I was running into errors from the start so I didn't even notice, but my python script did indeed leave the camera open before throwing an error.
Doing the Diagnostic test afterwards showed that the camera was busy, but when I tried opening the ZED Explorer once and then closed it, everything seemed to be reset properly and working again.


GoViral: use push/pull to fix field ordering in xs/sm views of sign up form

In https://www.goviralstudy.com/#sign-up the field ordering is messed up when the fields are collapsed to single column by Bootstrap (for xs and sm screen widths):

First name
Password
Last name
Confirm password

Also,

Email address
Birthdate
Confirm email address

Should use Bootstrap's "push" and "pull" to get correct order while having the same display on larger screen widths. http://getbootstrap.com/css/#grid-column-ordering

Unfortunately not as easy as using push/pull since the fields are split up between columns that won't allow for easy re-ordering.
Shouldn't be too hard to re-build the form such that it makes sense in regular or collapsed form though, I'll add an estimate.


feat: sdpchange event

Added sdpchange event that will be called whenever sdp is created
This includes

createOffer (offer - premunged)
setLocalDescription (offer - munged)
setRemoteDescription (answer - munged)

premunged answer is created outside webrtc-core so it should be emitted using
peerConnection.emit(PeerConnection.Events.SdpChange, {
  type: 'answer',
  munged: false,
  sdp: sdp, // sdp string
});

I think we should consider here what the native events look like and think about being consistent:  the real events don't fire an event with the SDP on createOffer, for example, but instead createOfferOnSuccess, I believe.  Same for setLocalDescription, etc.


Feature request: Quick copy commit subject/hash/tag

Hopefully there can be a way to quickly copy the commit subjects, hashes, tag names, etc. This would be handy for searching or when reusing / referencing / sharing commit info.
Perhaps a copy icon next to the commit subject/hash on the list that only shows up when hovering over them.
Or maybe some options in the context menu like Copy... >Subject / Hash / Tag etc.
Thank you!

hmm I can see how that could be helpful

Perhaps a copy icon next to the commit subject/hash on the list that only shows up when hovering over them.

sure but then you'd need said icon next to all elements on hover: author name, hash, subject, date. And branches, stashes, where an additional icon would be hard to squeeze in.
I'm thinking perhaps really adding a new context action "Copy..." to all things (commit, commits, branches, tags, stashes) might be an idea, and clicking that shows a popup with various options for what you want to copy (hash, author name, name if it's a branch, origin, full name/origin, and so on). And when you're in a commit details pane, pressing CTRL+C will also open up this dialog.
perhaps this would be ... too much thoughh

If using icons, it would probably be fine to add them only for the most commonly used elements such as subject, hash. I've seen other extensions do this and it looks good and convenient.
If using the context menu, then it can be added for any suitable elements. I personally prefer a quicker and lighter way, better with one~two steps, like directly in the menu/submenu rather than right-click>Click Copy...>popup>select the copy option>(maybe have to close the popup afterwards).
See Git Graph, right click on tags it shows Copy Tag, right click on branch it shows Copy Branch, right click on commit it shows Copy Subject/Hash, etc. This way seems more flexible and WYSIWYG.
Or, it would also be nice to simply put all the options into one submenu.

I think the context menu does not necessarily need icons. I think it's better to have no icons instead of misleading ones.

Speaking of the context menu, I think it is better to use the VS Code "native" menu than the current menu which is limited in the view.
(This is not a really bothersome issue, since it's mentioned it would be nice if there could be any improvement about it!)
For example, I am placing git log graph in the bottom panel and it takes up very little height. When I right-click, the context menu only expands down and gets truncated by the panel height, so I will need to scroll up and down to see the full menu.

If using the VS Code menu, then it can automatically expand up or down depending on the clicking position, and can be shown above and beyond the panel.
For this copy feature, It would also be good for putting various copy options into one submenu, so it just needs two clicks: right click > hover Copy... > click on the option that needs to be copied. Like:

I've added a copy hash entry to the context menu (not yet released) for now.

I think the context menu does not necessarily need icons. I think it's better to have no icons instead of misleading ones.

@hansu Are any of the current ones misleading to you? If not, do you really think they should go? Or perhaps be disable-able? As a last resort, with the custom CSS option they can already be hidden out.

Speaking of the context menu, I think it is better to use the VS Code "native" menu than the current menu which is limited in the view.

@Amanoki I don't think this is possible because the extension lives inside a "web view" which is basically a normal web page, entirely separated from the outside world including styles etc. There is communication with the backend via message parsing though.
It's definitely a problem however that when you right click too far down, the menu is half hidden. The menu needs to be improved to the standard context menu logic so that it opens upwards instead in this case.

also agree that submenus would be better than a popup

I've added a copy hash entry to the context menu (not yet released) for now.

:+1:

I think the context menu does not necessarily need icons. I think it's better to have no icons instead of misleading ones.

@hansu Are any of the current ones misleading to you? If not, do you really think they should go? Or perhaps be disable-able? As a last resort, with the custom CSS option they can already be hidden out.

They are much better and almost not misleading. I didn't remember exactly how they looked before.
I know it's difficult to find icons for functions that are very specific and end up in similar icons :upside_down_face: .

As a last resort, with the custom CSS option they can already be hidden out.

Is there any documentation of the classes or elements which can be modified by css? Or just look in the code in web/src/views ?

All styles can be modified - you need to toggle the VSCode developer tools by its command and use the inspector element picker to find the right spot and target its class/id/whatever directly.
In this case, it'd be .context-menu-wrapper i:before { content: ''; }.

You could also look into web/src/, yes, but since the Vue compiler does a lot of magic it's probably always easier to use the inspector instead. In the case of context menu icons, it's even more difficult because there is no template for it, the html is generated dynamically inside the context directive's code

Thanks!
I played a bit around and found that it looks good to me if the active branch is filled with the same color as the line instead of white:

What do you think?  (Sorry a bit off topic)

I think that could work, would have to try a few different colors though.
But is it really an improvement over the white fill color? (black in light theme) I haven't had any issue with it so far and like the fact that "HEAD" is generally always a white/-ish color: The bubbles' filling, the line's shadow (should be bit darker though), the  (HEAD) or HEAD branch. Somewhat contrary to that is the coloring of origins, stashes and tags which is also white, which doesn't fit the narrative.

But is it really an improvement over the white fill color?

IMHO yes. Especially with the a light theme.
But still a great improvement that the active branch is emphasized from the other branches :-).
However, I discovered a little design bug in light theme. The branch name background shouldn't be black in this case, right?:

Two other things regarding the color come into my mind looking at this:

The color of the branch which is merged with message "merge remote-tracking..." should not be the same as the master branch.
Can you change the color-order (or make it configurable)? red-orange-blue-cyan gives not a good contrast.
Maybe just take the colors from Git Graph?

Sorry to spam this issue full with unrelated annotations :innocent:


[Clojure] follow up pr 14531 to fix tests

Description
This is a follow up PR to https://github.com/apache/incubator-mxnet/pull/14531 which fixed some Clojure tests that were not testing what they thought they were.
This PR resolves the FIXME disabled tests in there

@Chouffe would you mind taking a look and reviewing this when you get a chance?

@gigasquid I will take a look shortly when I get a chance. Thanks for finishing the fixes ^^

@mxnet-label-bot add [Clojure, test]

Thanks for reviewing @Chouffe !


[WIP] Create devices and organizations templates

I'm seeing the same problem with obi-edit.owl as #1113, stripping all the xsd:string datatypes, etc.

Could you point me to where you're seeing this? I ran the following and didn't see the xsd:string problem...
git diff 4787400 055fd9e src/ontology/obi-edit.owl

(4787400 is the last commit before this branch)

You're right, my mistake.

We'll discuss this on Monday's call.

This aims to address #1107 by creating templates for devices and manufacturers (actually all organizations) that enforce patterns and let us add terms quickly.
In converting from OWL to ROBOT templates we were careful not to drop axioms or annotations, but in a handful of cases I decided to remove some redundant or incorrect logical axioms.
I have two concerns to discuss on the call today:

The tables have more columns than we really need. Can we remove some?

I don't like the way that organizations are modelled as having anonymous roles. Organizations are individuals, not classes, but we've tended to say very class-y things about them such as "Illumina 'has role' some 'manufacturer role'". In pseudo-Turtle this would look like 'Illumina' 'has role' [rdf:type 'manufacturer role'] . Since we don't care to specify the particular 'manufacturer role' that Illumina has, this adds complexity with no benefit. It seems much cleaner to me to just say 'Illumina' rdf:type 'manufacturer' . and we've already defined a class 'manufacturer' as subclass of "'has role' some 'manufacturer role'".

In other words, I'd rather give individuals one or more named classes as rdf:type, and avoid linking individuals to anonymous structures. The current modelling required use to add a weird new feature to ROBOT

I won't be able to be on the call today unfortunately. Some quick input on
roles: we wanted to enable a given organization having different roles,
e.g. Illumina is a manufacturer, but also provides sequencing as a service.
So if we go with asserting parents for instances, we will end up asserting
multiple parentage. I don't particularly like that, but am also not overly
worried (if we keep it to instances).
On Mon, Feb 24, 2020 at 5:39 AM James A. Overton<EMAIL_ADDRESS>wrote:

This aims to address #1107
https://github.com/obi-ontology/obi/issues/1107 by creating templates
for devices and manufacturers (actually all organizations) that enforce
patterns and let us add terms quickly.
In converting from OWL to ROBOT templates we were careful not to drop
axioms or annotations, but in a handful of cases I decided to remove some
redundant or incorrect logical axioms.
I have two concerns to discuss on the call today:

The tables have more columns than we really need. Can we remove some?
2.
I don't like the way that organizations are modelled as having
anonymous roles. Organizations are individuals, not classes, but we've
tended to say very class-y things about them such as "Illumina 'has role'
some 'manufacturer role'". In pseudo-Turtle this would look like 'Illumina'
'has role' [rdf:type 'manufacturer role'] . Since we don't care to
specify the particular 'manufacturer role' that Illumina has, this adds
complexity with no benefit. It seems much cleaner to me to just say 'Illumina'
rdf:type 'manufacturer' . and we've already defined a class
'manufacturer' as subclass of "'has role' some 'manufacturer role'".
In other words, I'd rather give individuals one or more named classes as
rdf:type, and avoid linking individuals to anonymous structures. The
current modelling required use to add a weird new feature to ROBOT
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/obi-ontology/obi/pull/1114?email_source=notifications&email_token=ADJX2ITSBXGFX6KNX6CJJPTREPE2ZA5CNFSM4KXOAQMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMX2EAI#issuecomment-590324225,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADJX2IWYH43WV4QRXP4MHCTREPE2ZANCNFSM4KXOAQMA
.

--
Bjoern Peters
Professor
La Jolla Institute for Allergy and Immunology
9420 Athena Circle
La Jolla, CA 92037, USA
Tel: 858/752-6914
Fax: 858/752-6987
http://www.liai.org/pages/faculty-peters

Discussed on the 2020-02-24 OBI developer call. I was convinced to leave the role modelling alone. I'll follow up on issue #1107 with a few questions, but we plan to move forward and merge this. If you want more time to review, please let me know right away.


Copy favicon to public folder to squash FatalError on load

I rule and have completed some work on Case Manager that's ready for review!
Copy favicon.ico into public folder to squash a FatalError on app load

Make a copy of the favicon and paste it in /public

Eliminates the following errors:
[FATAL] ActionController::RoutingError (No route matches [GET] "/favicon.ico")
[FATAL] actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/debug_exceptions.rb:65:in `call'

Fixes #1630

thank you very much @drubaby ! We're glad to have you on the team!


[Android] Inappropriate error ‘Invalid Phone Number’ message is shown on the ‘Welcome to celo wallet’ page when sign up without entering ‘Full Name’.

Frequency: 100%
App version: Celo Staging v1.4.2
APK File: app-armeabi-v7a-staging, app-x86-staging.
Repro on:  Moto z play (7.0), Moto G5 + (8.1.0), Samsung Galaxy Note 9 (9.0)
Priority: medium
Repro Steps:

Launch the fresh install app.
Select the English language.
Tap on the continue button.
Make sure ‘Welcome to celo wallet’ page is opened
Enter ‘country code’ and ‘Mobile Number’.
Make sure Full name fields is blank
Tap on the Continue and observe.

Impact:  Wrong popup message may confuse the user about the information added in the app.
Expected Behavior:
Appropriate validation message "Please enter full name" should be shown.
Current Behavior:
Inappropriate error ‘Invalid Phone Number’ message is shown even when the user has entered the correct number but not fill the full name field.
Attachment (Bug observe at18 sec)

Verified with the Android play store build v1.5.0 and found that the issue is still reproduced.
Attachment: Android_InappropriateErrorMessageIssue.mp4

Verified with the Android play store build v1.5.0 and found that the issue is still reproduced.
Attachment: Android_InappropriateErrorMessageIssue.mp4

Verified with the Android play store build v1.5.0 and found that the issue is still reproduced.
Attachment: Android_InappropriateErrorMessageIssue.mp4

@i1skn  @jmrossy Verified with the Android Celo Alfajores Wallet Playstore build (1.6.0 (104794306)) and found that the issue is fixed now.
Verified on Devices : Samsung Galaxy A5 (7.0), Redmi Note 7 Pro (9.0)
'Name cannot be empty' error message is shown when user taps on 'Continue' button without entering 'Full name' on 'Welcome to Celo Wallet' page
Attachment: Android_Name cannot be empty error is shown


One annotation per phenotype

Multiple guidelines matching one phenotype should be shown in scroll-able window on guideline page
Open question: how to handle "No result" or "n/a"


Partition number discovery

Pippin files may have a pnX part, where X is a number, to make the partition number easily available.
File discovery should be able to cope without this by loading the header if necessary in order to find the number. It may assume that files with the same prefix (up to -ssY-) have the same partition number.
Note TODO marker in doc/repo-files.md.

This should work now (no test case since the pnX part is not optional in name generation, though it could be).


can't extract pretrained model

after i download it, i still can't extract it

in fact, only pretrained_sceneflow_new can be extracted

The .tar file itself is the checkpoint, you don't need to extract it


[jvm-packages] try setting default profile

https://github.com/dmlc/xgboost/issues/1858 sbt is not properly interpreting the properties specified in the per profile section of the pom.xml
Be sure to delete the cached variant in ~/.ivy2/caches/ml.dmlc....

 Last update cee4aaf...6b5f5ce

@CodingCat

@CodingCat LGTM. Could you take a look to double check?

@geoHeil would you mind removing the unrelated changes?

You mean the fix of maven profiles? Sure. Can look into that
Nan Zhu<EMAIL_ADDRESS>schrieb am Di. 31. Jan. 2017 um 03:21:

@geoHeil https://github.com/geoHeil would you mind removing the
unrelated changes?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dmlc/xgboost/pull/1891#issuecomment-276255248, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABnc9KnkmWdEgJQrWjlhAmBw4XZEm8m1ks5rXpqJgaJpZM4LR8MB
.

no, I mean those changes on scala files

@CodingCat you mean the previous changes? Because this pull request should only have modified the pom.xml, the commit you sent me was my attempt to remove these unnecessary edits introduced in 24fcb0729d76e3087c263dce9890411b995ae6ed.

you can click Files changed view, you can see XGBoostModel.scala was unexpectedly modified

besides that Travis CI seems to be failing?

Yes, the latest changes were incomplete. I was missing the second file. Now travis should be green again.

thanks, will approve the PR once Travis passes

@tqchen , problem on codecov/project checking?

Codecov is not required to get things merged, let me know if you cannot otherwise nexttime


fix a typo

fix typo, rename BOOST_TEST_I_ASSRT to BOOST_TEST_I_ASSERT

Hi,
This is an internal interface, why would your changes make any difference?

I though that is a typo, but it appears not.


[1.17] gateway: remove internal annotation from propogating (#44220)

Fixes https://github.com/istio/istio/issues/44223
No notes as it is a bug-fix for an unreleased patch.

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio_release-1.17
1c11d5c475f2ae40d3062799b395dc6e2faaf43e
link
unknown
/test integ-security-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


executable file (test1) in ubuntu

Hi my influxdb version is 1.7.x and i am trying to use it with c.
I have pulled the files and made an executable test1 file to make a database with the code.
But unfortunately when i execute the file it doesn't happen anything.
Will it have an solution to solve it?
Thank you

@ydh6226 thanks for opening this. Looks like this repo hasn't been touched in quite a while and isn't compatible with the latest influxdb. I'll work on getting this repo archived to avoid confusion, but you might have more luck with this community maintained library: https://github.com/orca-zhang/influxdb-c


Implemented token hud with string layout and fixed click behavior

[Added] Formatting on the TokenHUD. The name labels are optional, the removal all button is always there.

[Fixed] Click on the token statuses updates the actor sheets properly
[Change] The data format of the condition images to provide metadata required for modules. The effects of this can be seen in the final HTML

I found a case where it was possible to sometimes get double icons on the token. I discovered I missed an await on the setCondition call which is why it was working so well in the first place. Once I added the await I got double icons consistently. After a little experimentation, I decided to allow the actor to control the token toggling since that is more reliable than a hybrid system. The one remaining bug has to do with conditions that toggle other conditions. There seem to be double updates happening there. I'll have to get into the code that handles those cases to find out why.

The Flat-Footed check always had a double update. Now there's a triple update thanks to Foundry. There's a check that's maybe a little shortsighted in the code that checks if the effect data has an icon property. If it does then it takes an adventure through active effects and then calls toggleEffect again with more processed data that allows the icon to work properly in overlay mode.
To summarize: I fixed everything but there is a triple update on the tokenHUD every time a condition changes and there's not much I can do about it unless foundry improves the conditions in their Token.toggleEffect method.

@TimToxopeus your comments should have been addressed by these commits


extension manage window isn't draggable?

In the latest brackets, I cannot drag the extension manage.When the brackets is not  maximized,I cannot see all the manage window and the close button in the lower right.

 I am not sure if we could drag this in earlier versions even. I just tried a really old version of brackets (V0.38 on Mac mavericks) and could not drag the extension manager window.
Also the close button issue not being visible, is that a duplicate of bug #10728 ?

@linuxjd How big is the window size you normally use for Brackets?  If your window is at least 760x513, you should be able to see all of the Extension Manager dialog...

I think adding something like this extension into Brackets by default (like you guys did with the code folding) would be a good idea. It'd fix issues like this one and the one @prksingh linked.

I'm going to go ahead and close this because it's not something we're planning on changing. Since the extension is there to make them draggable, that seems like a good workaround.
I think the rendering issues are something that we'll be fixing in an update so hopefully that will alleviate the need to drag.


Update readme with more information about extension

Details about Python Extension dependency ..

@greazer We've updated the readme since this time, so closing, just reopen if I'm off on this.


IE compatibility issues

EventSource and Promise need to be poly-filled.

https://github.com/gatsbyjs/gatsby/pull/6183
This seems to be the culprit. I made some progress with CDNs but I realize now that there might be a better solution.

@Troy-Lawson Can we add this to Sprint 46?

Completed.


[Feature] Docker centralized logging

Adding this for myself so it is not forgotten (already started):

Add centralized logging with fluentd / elasticsearch / kibana

not needed


Safe way to convert PyAny -> PyDict

I'm writing about PyDict here, but I think this applies to all native types.
I can't find a safe API to convert PyAny to PyDict. It looks like FromPyObject is the appropriate trait, but it's not implemented for PyDict.
The pyobject_downcast! macro looks like it's supposed to define these conversions:
https://github.com/PyO3/pyo3/blob/c8cb3adc23d297955bf8a08be19976fdb11e3a76/src/types/mod.rs#L28-L48
But it doesn't look like the macro is ever actually invoked.

Oh; I see that there is also the PyTryFrom trait, which is implemented for PyDict thanks to the blanket impl:
impl<'v, T> PyTryFrom<'v> for T
where
    T: PyTypeInfo

Strangely, this blanket impl doesn't show in the docs for PyDict?

Might be a discussion for another day why the trait is missing from the docs, but at least there is a way!


utils/mnt: fix mount permissions

This is a follow up to #1550 where we enabled a rw permissions mode, which is not ideal since it would theoretically be possible to set both ro and rw modes at the same time. This commit fixes the issue by only allowing one option at a time.
Fixes #1588

Thanks for the change.
The approach is OK from my PoV, although I'm not a huge fan of passing string values as arguments to functions, which should be most probably a pre-defined constants.

Sure, that makes sense. I will update


#5716: Enabling WH tests for SD model

This PR contains:

Enabling WH tests for SD model by removing @skip_for_wormhole_b0() fixtures
Passed device parameter to geglu and feedforward sub_module tests as previously the test was failing because of not passing device parameter to sub_module

@punithsekar you will need to edit tests/scripts/run_models.sh as it is currently only calling ttnn tests for GS
if [[ $ARCH_NAME == "grayskull" ]]; then
  # TODO(arakhmati): Run ttnn tests only on graskull until the issue with ttnn.reshape on wormhole is resolved
  env pytest tests/ttnn/integration_tests
fi

env pytest tests/ttnn/integration_tests/stable_diffusion should also run when arch is WH.
Also, please make sure to run env pytest tests/ttnn/integration_tests/stable_diffusion locally on a WH machine and ensure all tests are passing before merging.


Skip tables on pull_db

Hi,
I would like to know if it is possible to skip some tables on pull_db command ?
Indeed I have a warning which I may be able to solve.
mysqldump: Couldn’t execute ‘SELECT COLUMN_NAME,                       JSON_EXTRACT(HISTOGRAM, ‘$.“number-of-buckets-specified”’)                FROM information_schema.COLUMN_STATISTICS                WHERE SCHEMA_NAME = ‘db_name’ AND TABLE_NAME = ‘ct_assetindexdata’;’: Unknown table ‘column_statistics’ in information_schema (1109) mysqldump: [Warning] Using a password on the command line interface can be insecure. mysqldump: Couldn’t execute ‘SELECT COLUMN_NAME,                       JSON_EXTRACT(HISTOGRAM, ‘$.“number-of-buckets-specified”’)                FROM information_schema.COLUMN_STATISTICS                WHERE SCHEMA_NAME = ‘db_name’ AND TABLE_NAME = ‘ct_assets’;’: Unknown table ‘column_statistics’ in information_schema (1109)
Thanks !

This is happening because you're using a MySQL 8 client with a MySQL 5.7 db. I'd sync up the versions.


Keyword missing

I typed in " Oh!!! The bow-tie is nice but does not match with suit."
The only emoji came up was Bow-tie, I was expecting 'thumbs up' emoji to come up instead of 'nice'.
For 'suit', the emoji came up were not relevant.

Thanks for trying it out! The mappings are actually taken from https://github.com/muan/emojilib, which is open source -- you can send a PR for those keywords to be added! :)
(closing, since this is an issue upstream)


[?bug] Nested Relationships error

I Have
Item  model
ItemCompetitor model with Item hasMany
ItemCompetitorSales model with ItemCompetitor hasMany
now, when showing single item i want to get last 2 rows of ItemCompetitorSales for each ItemCompetitor
so my ItemCompetitor looks like this
public function sales()
    {
        return  $this->hasMany(ItemCompetitorSaleCount::class)
            ->orderBy('created_at','desc')
            ->take(2);
    }

So lets say for item = 1,
there are 10 competetirors,
each competitor has 5 competitor sales
so i want to get 10 x 2 = 20 rows from ItemCompetitorSale model
but i am getting only 2
if i change take(2) to take(20) it returns 20 rows but again 5 rows from each for first 4 competitors which is not what i want.
Is this a possible bug with laravel or am i doing wrong?

Take 2 literally just means limit the result size of the whole thing to 2, so this looks correct.

but when we call  take(2),
it should take 2 items for each nested table.
or i should not use take() in this scenario?


IDE crash on cam reset

When using Reset OpenMV Cam with the RT1062, it crashes the IDE and stops responding until it is quit and reopen. This has been confirmed with tests on multiple windows machines, with cameras running the newest firmware updated directly from the IDE.

@cyber-run - Yes, I can confirm this if you save to Disk and then click reset. If you disconnect first and then reconnect and save to disk you do not get a crash.
I'll get this debugged soon.

sounds good thanks !

Please leave the issue open until I fixed it.

This issue appears to have been fixed via recent firmware updates in MicroPython.


Master nodes are taking up to 4.5 minutes to be listening

Since the ELB health checks expire in 200 seconds, often the api server
is not yet listening. Extend the check interval to 45 seconds to allow a
450 second start time.

👍


description more readable, remove note

This makes task result description a bit more readable (1 RPM per line).
It adds a URL to report issues. It also removes detail.note from
resultsdb, because it seemed unnecessary and also made the field
contents overly long for failures (all RPMs listed).

Log before:
389-ds-base-<IP_ADDRESS>-1.fc26.aarch64.rpm,389-ds-base-<IP_ADDRESS>-1.fc26.armv7hl.rpm,389-ds-base-<IP_ADDRESS>-1.fc26.i686.rpm,389-ds-base-<IP_ADDRESS>-1.fc26.x86_64.rpm require both Pythons, i.e. Python 2 and 3.

Read https://python-rpm-porting.readthedocs.io/en/latest/applications.html#are-shebangs-dragging-you-down-to-python-2 to find more information and possible cause.
Or ask at #fedora-python IRC channel for help.

If you think the result is false or intentional, file a bug against TODO.

And after:
These RPMs require both Python 2 and Python 3:
389-ds-base-<IP_ADDRESS>-1.fc26.armv7hl.rpm
389-ds-base-<IP_ADDRESS>-1.fc26.i686.rpm
389-ds-base-<IP_ADDRESS>-1.fc26.x86_64.rpm

Read the following document to find more information and a possible cause:
https://python-rpm-porting.readthedocs.io/en/latest/applications.html#are-shebangs-dragging-you-down-to-python-2
Or ask at #fedora-python IRC channel for help.

If you think the result is false or intentional, file a bug against:
https://github.com/fedora-python/task-python-versions/issues

An overly long note in resultsdb is visible here.

I submitted this PR against master, because it was set as the default branch and I didn't notice that. But it'd be better to merge it to develop instead (so that it takes an immediate effect in taskotron testing).

Thanks!


Date cells: YYYY-MM-DD please

I'm so used to seeing dates rendered YYYY-MM-DD, I'd like to be able to do this in Notion-like Tables, too. It's the only date format that sorts automatically in chronological order when multiple years are involved.

Hi @miscemw. Thank you for your feature request. Yes, I can change this.

Hi. How can i change the date format, mine is still YYYY/MM/DD. I'm using lastest obsidian and plugin version


Improve support for symfony

I am trying to start a Symfony proiect and I have noticed some problems. Probably support for SF was not a priority.

[ ] Add support for blackfire
[ ] Add default ELASTICSEARCH_VERSION in .env
[ ] Nginx support for Symfony < 4 https://symfony.com/doc/current/setup/web_server_configuration.html vs https://symfony.com/doc/3.4/setup/web_server_configuration.html. Probably new nginx template needs to be added.
[ ] Support for symfony developer mode
[ ] Mutagen?

Nginx support for Symfony < 4

If you're starting a new Symfony project, why would you not start with a more current and maintained version of Symfony?
Would be happy to see PRs adding support for Blackfire, docs on using Eleasticsearch with Symfony, etc, but adding support for unmaintained old versions of frameworks is not something I intend to do here.
You're also welcome to mount a custom Nginx template into the nginx container yourself however to accomplish whatever changes you require for your project using info from these pages as a guide:

https://github.com/davidalger/warden/issues/325
https://docs.warden.dev/environments/customizing.html#php-specific-customizations

Mutagen?

See here: https://github.com/davidalger/warden/issues/203#issuecomment-677774991

I am not starting a new project. I want to migrate an existing one from vagrant to docker with warden.
I agree with you regarding Symfony versions <4.
I will create a custom nginx template inside my project.
I will submit only the setting for Blackfire and ElasticSearch.

I am not starting a new project

Gotcha, my bad, I read "trying to start a Symfony proiect" the wrong way then. :)

I will create a custom nginx template inside my project.

After glancing at the docs you linked, you might try putting the following in a .warden/warden-env.yml file (in the project root) to override the NGINX_PUBLIC variable to use web vs public dir. Not sure if it's the only Nginx change they're asking for, but at a glance it appears it could be
version: "3.5"
services:
  nginx:
    environment:
      - NGINX_PUBLIC=/web

I will submit only the setting for Blackfire and ElasticSearch.

Sounds good.


Fix broken links to postinstall documentation

Proposed changes
In the distribution specific instructions for installing docker-ee, the links to the post-installation steps are broken.  For instance, see https://docs.docker.com/install/linux/docker-ee/ubuntu/ halfway through the page at the end of the section INSTALL DOCKER EE.  This fixes the broken links to point to the correct location.
Unreleased project version (optional)
N/A
Related issues (optional)
N/A

Reusable content should always use absolute paths since you don't know where that snippet is going to be rendered. Thanks for fixing this @russellcardullo. Let's ship it!


adding firestoreRole to products doesn't add userCustomClaims stripeRole

Bug report

Extension name: [e.g. firestore-stripe-subscriptions]

Describe the bug
Not really sure where to report/ask this, so I figured here would be a good place.
If a product has a firestoreRole value in Stripe, and there's a customer subscription, that user should have the same value on the user claim key stripeRole... right? That's my understanding. If I'm wrong, can someone clear this up for me? If I'm correct in that assumption, something may be up with the extension
To Reproduce
Here's my setup:

I have a freshly installed extension, pre-existing products in Stripe: Basic, Pro, Premium.
each product has a firestoreRole value: basic, pro, premium

Retrieving the customClaims on a front-end next.js app with this:
export async function getCustomClaimRole() {
  await firebase.auth().currentUser.getIdToken(true);
  const decodedToken = await firebase.auth().currentUser.getIdTokenResult();
  console.log("decodedToken", decodedToken.claims.stripeRole); // output is undefined, stripeRole doesn't exist :( more on that below
  return decodedToken.claims.stripeRole;
}

Expected behavior
stripeRole should exist on user custom claims if firebaseRole exists on products.
Not really sure why the claim isn't there.
Screenshots
Here's the entire decodedToken object consoled I mentioned above:

Here's the metadata firebaseRole on a product in stripe:

Happy to provide any further details to help debug this. I've been wracking my brain on this one 😅 hope all of this makes sense

I have no idea why or how... but i took a beat, and when I came back getCustomClaimRole began working as expected and the stripeRole claim appeared 😅

@smpetrey the metadata key needs to be firebaseRole not firestoreRole, that might have been the issue. Glad that it's working now :)

Thanks @thorsten-stripe! I think that may have been the issue 😅


Lambda requires DD_API_KEY envar even though Datadog is already provided with apiKeySecret

Expected Behavior
I expected that when I initialise the Datadog construct with an apiKeySecret it should use this to populate any envars related to the api key and set permissions to read the secret.
Actual Behavior
I get errors in the lambda cloudwatch logs:
DD_EXTENSION | ERROR | Unable to load trace agent config: you must specify an API Key, either via a configuration file or the DD_API_KEY env var
Steps to Reproduce the Problem

Create the datadog construct

      const datadogApiKeySecret = Secret.fromSecretPartialArn(
        this,
        'datadogApiKeySecret',
        props.envConfig.datadogApiSecretArn,
      );
      // add datadog integration - this is passed to the constructs so they can add the datadog layer to the lambdas
      this.datadog = new Datadog(this, "Datadog", {
        nodeLayerVersion: 99,
        extensionLayerVersion: 49,
        site: 'datadoghq.com',
        apiKeySecret: datadogApiKeySecret,
        env: `${props.envConfig.envName}`,
        version: props.deployName,
        captureLambdaPayload: true,
      });

Create a lambda function

// Create a lambda function to create a transaction when triggered by an IoT rules
    this.myLambdaFunction = new NodejsFunction(this, 'myLambdaFunction', {
      entry: 'resources/lambda/handler.ts',
      handler: 'myHandler',
      vpc: props.vpc,
      securityGroups: [lambdaSecurityGroup],
      environment: {
        DD_SERVICE: 'myLambdaFunction',
        env: props.envConfig.envName,
      },
      logRetention: logs.RetentionDays.ONE_WEEK,
      timeout: cdk.Duration.minutes(1),
      tracing: lambda.Tracing.ACTIVE,
    });
    this.datadog.addLambdaFunctions([ this.myLambdaFunction ]);

The logs show the error describe
Add the DD_API_KEY envvar and it starts working

    ...
    environment: {
        DD_SERVICE: 'myLambdaFunction',
        DD_API_KEY: this.datadog.props.apiKeySecret?.secretValue.unsafeUnwrap() || '',
        env: props.envConfig.envName,
      },
    ...

Specifications

Datadog Lambda Layer version: 49
Node version: 99
<EMAIL_ADDRESS>

hi @bencaldwell, thanks for reaching out!
Can you enable debug logs and see what the error is? I'd also suggest verifying that your secret is not a JSON object but instead a plain stright.
Thanks!

I'm experiencing the same issue.
pythonLayerVersion: 87,
extensionLayerVersion: 43,
apiKeySecret: datadogSecret,
If I go to the Lambda function and manually set the DD_API_KEY, the problems go away.

Hi @bencaldwell, given Matt's update here and no response I'm going to close this for now but will happily take a second look if you have time to get back to us. Otherwise, please feel free to reach out to support with questions<EMAIL_ADDRESS>Thanks!


MDK Viewpoint TablePropertyColumn cannot find basic UML Profile Properties

When I'm creating my view point and using TablePropertyColumns I'm having a tough time being able to point to the most basic UML Profile stuff such as "Owner" for blocks, or "Source" and "Target" for Dependencies, and I think it's because when I'm searching under DesiredProperty, I'm looking all over but I just cannot find the base UML Profile to say, "hey, I want to select the owner".
Do you have any hints like we don't have the UML Profile loaded to our project or it's not viewable?? Or why I cannot point to such properties to display when I generate my document?

TablePropertyColumn is intended for getting the property value of classifiers or slot values of stereotype tags, not uml profile properties. To show things like owner, you can use the structured activity version of TableAttributeColumn and do more collect/filtering inside the column to get the element you want (this will be applied to the element for each row in the table), then use Name as the attribute to display.


Set CMS_Type job classad based on the dashboard activity - wmagent version

wmagent branch version of https://github.com/dmwm/WMCore/pull/9270

 Fix #9271 - Set CMS_Type job classad based on the dashboard activity

Pushed in to all production agents.


Update setup.cfg for non-verbose pytest tests

When tests fail in the CI, the output logs are truncated to the point that you can't see which tests have tailed you can only see some of the earliest failing tests, but not necessarily the important tests for a specific PR's changes (eg: this example)

This step has been truncated due to its large size. Download the full logs from the menu once the workflow run has completed.

Has this problem been affecting other people?
While it should be possible to download the full logs archive and search through that, that's an extra step and also sometimes the download file is corrupted (this was the case when I tried to download the logs here several times).
If GitHub actions only allows approximately a few thousand lines in the logs for each CI stage, I think we should remove the pytest verbose flag & rely on the summarized list of failures/errors (from the pytest -rfE command line flag). This PR does that.

Yeah - this is the first time I've ever seen this too. I wasn't sure if it was a recent change in how GitHub actions handled its logs or what.
I would certainly prefer to have the full verbose output, so I agree with waiting to see how much this is actually a problem.


the example project seems to be missing stuff

by default if i press the button in the example project
a exception is raised, since compute is not implemented.
if i override the compute on the button node to avoid the exception
it only executes the current node. since run_output_nodes doesnt do anyhting.

your comment in https://github.com/bhowiebkr/python-node-editor/discussions/2 clarified this project is not finished.

Sorry yeah I don’t have compute code implemented yet, started but not finished. When I get some time I’ll see about finishing that portion of the system.
In the meantime If anyone wants to take a crack at it and do a pull request that’d be great!

no worries.
i decided to use http://chantonic.com/NodeGraphQt/api/index.html since it has more features.
it's also UI only, so I'm implementing my own compute


Update documentation from 0.4.0 to 0.5.0 in readiness for new release

Signed-off-by: tpmccallum<EMAIL_ADDRESS>Updated 0.4.0 to 0.5.0 in a few spots; in readiness for new release.

This is a subset of the steps required for a new release — see https://spin.fermyon.dev/release-process

I was just updating the docs in anticipation of the new 0.5.0 release. My apologies, I did not realise that there was a bullet point for Check the docs for hard-coded version strings in the first part of the spin.fermyon.dev/release-process. I did not want to steal anyones thunder on the 0.5.0 release, please go ahead and update as planned and disregard this PR if/as required.

Thanks for the reminder here @tpmccallum!  I had nearly forgotten to update versions.  Full set of updates is in https://github.com/fermyon/spin/pull/734.  I'll close this one now.


Fix issue #1102 by including the dbms attribute on the mysql specific…

Update changeset to include dbms attr.

@natechadwick  it is working now. Good to merge.


Bring in initial TCK tests

Initial delivery of TCK tests. This PR adds a single optional test class from the MP JWT Auth TCK: EjbTest.

@sberyozkin How does this look to start us off?

Apologies @ayoho for missing out on your PR, thanks a million for the effort, let me have a look asap, I'll also request others to double check, cheers

Hey @ayoho I pushed a minor update, specifically, the build was failing because it was trying to execute the TCK test.

@sberyozkin Thanks! Forgot I was running with -DskipTests locally to get everything going.

@ayoho Np at all, thanks for starting the process, and great you will follow up with another PR to complete the TCK move, cheers


[REQUEST] Update for puppeteer 2.1

What would you like to have implemented?
New release that includes the chromium version (80.0.3987.0) associated with puppeteer v2.1.0
Why would it be useful?
Bug fixes and stuff.

@CodeVision v2.1.1 just released. :tada:


chore: bdd-spring-1573083739 to 0.0.1

chore: Promote bdd-spring-1573083739 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


404 when calling homegraph reportStateAndNotification

Environment details

OS type and version: wsl2 linux
Python version: Python 3.9.6
pip version: pip 21.1.3 from /usr/lib/python3.9/site-packages/pip (python 3.9)
google-api-python-client version: 2.15.0

Steps to reproduce

Use the Actions on Google Console to add a new smart home project.
Navigate to the
Google Cloud Console API Manager . Enable the HomeGraph API.
Navigate to the Google Cloud Console API & Services page. Using role Service Account > Service Account Token Creator. Create the account and download a JSON file. Save this as smart-home-key.json.
run python code below

Code example
# -*- coding: utf-8 -*-
import random
from google.oauth2 import service_account
from googleapiclient.discovery import build
import os

rootPath = os.path.dirname(os.path.realpath(__file__))
credentials = service_account.Credentials.from_service_account_file(
        os.path.join(rootPath, 'smart-home-key.json'),
        scopes=['https://www.googleapis.com/auth/homegraph'])
service = build('homegraph', 'v1', credentials=credentials)
obj = service.devices()
request_dict = {
    'requestId': str(random.random()),
    "agentUserId": "14711",
    "payload": {
        "devices": {
            "states": {
                "aa:01:03:11:22:cc": {
                    "on": True
                }
            },
        }
    }
}
request = service.devices().reportStateAndNotification(body=request_dict)
response = request.execute()
print("response", response)

Stack trace
$ python bug.py
Traceback (most recent call last):
  File "/home/ltl/smart-home-python/bug.py", line 27, in <module>
    response = request.execute()
  File "/home/ltl/.local/lib/python3.9/site-packages/googleapiclient/_helpers.py", line 131, in positional_wrapper
    return wrapped(*args, **kwargs)
  File "/home/ltl/.local/lib/python3.9/site-packages/googleapiclient/http.py", line 937, in execute
    raise HttpError(resp, content, uri=self.uri)
googleapiclient.errors.HttpError: <HttpError 404 when requesting https://homegraph.googleapis.com/v1/devices:reportStateAndNotification?alt=json returned "Requested entity was not found.". Details: "Requested entity was not found.">

Curl return 403, so the entity exists.
$ curl -XPOST https://homegraph.googleapis.com/v1/devices:reportStateAndNotification?alt=json
{
  "error": {
    "code": 403,
    "message": "The request is missing a valid API key.",
    "status": "PERMISSION_DENIED"
  }
}

my fault, device "aa:01:03:11:22:cc" not exists. closed


Add initial implementation of multichase benchmark.

Addresses some of the scenarios in #848.

@ehankland PTAL

LGTM


Difference between created and closed dates in hours

Hi,
I am trying to figure out to calculate difference between two dates i.e closed_on and created_on in hours to calculate downtime for my project issues. But i am unable to trace out how to do this. can you please help in this.
Thanks in advance.
Dileep.

Hi, try this
((self.closed_on-self.created_on)/3600).round(2) if self.closed_on.present?

Output format of computed custom field must be 'float'

Thank You So much. It worked.

You are welcome.

Sensational!! That's what needed.
I observed something that only worked after I updated the tasks. For tasks that were already closed the calculation was not done. That's right?
Thanks for the fast feedback.

Hi!
How would I calculate that this disregard day Saturday and Sunday?
Calculated based only on week days.
Thanks!

Hi
Try this formula
 if self.closed_on.present?
  holidays_count = (self.created_on..self.closed_on).count { |d| d.wday.in?([6,0]) }
  result = ((self.closed_on-self.created_on)/3600).round(2)-(holidays_count*24)
  result = 0 if result < 0
  result
end

Hi!
Thanks for your help and feedback.
Replace the formula with this and no calculation was performed. I think it did not work.
Thanks

oh, sorry I forgot to convert a Time object to a Date
holidays_count = (self.created_on.to_date..self.closed_on.to_date).count { |d| d.wday.in?([6,0]) }

Hello!
The calculation worked but I think that is not correct. Take this example the amount brought and the value that I think should have bring
Exemple:
created 02/17/2016 05:16pm - 02/20/2016 11:25am result calculated = 42.099999999999994
created 02/17/2016 5:16 pm - 02/20/2016 11:25 am (to consider thisl 02/19/2016 12:59:59 pm) result should be calculated = 55.43 (about this value) - Agree?

You are right, the formula works correct only if an issue was closed in work day.

How about this?
 if self.closed_on.present?
  holidays_count = (self.created_on.to_date..self.closed_on.to_date).count { |d| d.wday.in?([6,0]) }
  result = ((self.closed_on-self.created_on)/3600).round(2)-(holidays_count*24)
  result += self.closed_on.hour if self.closed_on.to_date.wday.in?([6,0])
  result = 0 if result < 0
  result
end

It seems that now work, perfect!
Again, thank you for quick return.
Thank you!
Hugs!

You are welcome.


Add Support for Azure Frontdoor

Terraform Resource:
azurerm_frontdoor
Pricing Information:
https://azure.microsoft.com/en-us/pricing/details/frontdoor/

Thanks @Theragus!
Adding some details for the cost components, cc @alikhajeh1 and @tim775 for the open question.
Open questions:

Frontend hosts are charged for when there are >100. We can count the number by counting the frontend_endpoint attributes of the azurerm_frontdoor resource, but I can't work out if the 100 limit is per-account or per-frontdoor instance. Options are:
a. Ignore this for now
b. Always show price for the frontend hosts but have a - cost
c. Assume per-frontdoor instance and only show the cost for these if there are >100.

azurerm_frontdoor
Terraform resource: https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/frontdoor
Cost components:

Outbound data transfer - all of these should have unit GB

North America, Europe (first 10TB)
North America, Europe (next 40TB)
North America, Europe (next 100TB)
Asia Pacific (including Japan) (first 10TB)
Asia Pacific (including Japan) (next 40TB)
Asia Pacific (including Japan) (next 100TB)
South America (first 10TB)
South America (next 40TB)
South America (next 100TB)
Australia (first 10TB)
Australia (next 40TB)
Australia (next 100TB)
India (first 10TB)
India (next 40TB)
India (next 100TB)

Inbound data transfer - unit GB
Routing rules (first 5 rules) - unit rules
Routing rules (per additional rule) - unit rules

Notes:

For "Outbound data transfer", if no usage is passed in we should only show the prices for the "X (first 10TB)" cost components. If usage is passed in we should only show the relevant ones. This is similar to what we do for the aws_cloudfront_distribution resource.
For "Routing rules" we should only show the "(per additional rule)" cost component if there are more than 5 rules. We can find the number of routing rules by finding the number of routing_rule attributes on the resource.

Usage file:
  azurerm_frontdoor.my_frontdoor:
    monthly_outbound_data_transfer_gb: # Monthly outbound data transfer from the following, in GB:
      north_america_europe: 51200000 # North America, Europe
      asia_pacific: 220000           # Asia Pacific (including Japan)
      south_america: 10000           # South America
      australia: 50000               # Australia
      india: 387000                  # India
    monthly_inbound_data_transfer_gb: 1000 # Monthly inbound data transfer in GB

azurerm_frontdoor_firewall_policy
Terraform resource: https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/frontdoor_firewall_policy
Cost components:

Policy - unit months
Custom rules - unit rules
Custom rule requests - unit 1M requests
Managed rulesets - unit rulesets
Managed ruleset requests - unit 1M requests

Notes:

For "Custom rules" the quantity can be retrieved by counting the number of custom_rule attributes.
For "Managed rulesets" the quantity can be retrieved by counting the number of managed_rule attributes.

Usage file:
  azurerm_frontdoor_firewall_policy.my_frontdoor_firewall_policy:
    monthly_custom_rule_requests: 10000 # Monthly number of custom rule requests
    monthly_managed_ruleset_requests: 10000 # Monthly number of managed ruleset requests

Free resources

azurerm_frontdoor_custom_https_configuration

Unsupported resources
Azure Front Door Standard/Premium (this isn't supported by Terraform yet: https://github.com/hashicorp/terraform-provider-azurerm/issues/11983)

@aliscott should we only show "North America, Europe (first 10TB)" by default unless usage-file params exist for the other ones? That's what we ended-up doing for CloudFront to simplify the output

@aliscott should we only show "North America, Europe (first 10TB)" by default unless usage-file params exist for the other ones? That's what we ended-up doing for CloudFront to simplify the output

+1 good point. This is now how we are doing it for other resources.

Thanks @aliscott - I updated the desc, I also tweaked it with my thinking for the open question.

This has been merged to master and will go live with the v0.9.14 release sometime next week.

@Theragus this is live in v0.9.14


Add locking support

Implemented locking mechanism to prevent simultaneous updates from corrupting index. It is used optionally with the -l option.
Previously if 2 users were to update the repository in S3 at the same time, one of the packages would end up missing from Packages.gz and Release.
I've tried to follow the existing code as closely as possible, and added MiniTest specs for the extra code.

BTW eventual consistency is not a problem unless you use the US Standard region. See http://shlomoswidler.com/2009/12/read-after-write-consistency-in-amazon.html

@krobertson - Any chance of releasing a new gem with this option included?

Other item worth noting, README.md would need to be updated at that time showing the -l option. Happy to do a PR for that work if it'll make you more willing to release a new gem.

@krobertson - Scratch that, hold off on doing a release. Found a pretty critical bug in locking. Will make an issue shortly, and tag @alexmreis on it.

Curious as to what the issue is, we've been using the patched version in a
CI environment since last October without any major issues.
On Wed, Feb 10, 2016 at 5:35 PM, jjshoe<EMAIL_ADDRESS>wrote:

@krobertson https://github.com/krobertson - Scratch that, hold off on
doing a release. Found a pretty critical bug in locking. Will make an issue
shortly, and tag @alexmreis https://github.com/alexmreis on it.
—
Reply to this email directly or view it on GitHub
https://github.com/krobertson/deb-s3/pull/89#issuecomment-182466765.

https://github.com/krobertson/deb-s3/issues/97


Feed page - Front end

[ ]  - show posts in frontend
[ ]  - show comments in frontend

Requirements for Feed UI
https://www.notion.so/fightpandemics/Feed-UI-653658508c4649869787c48f3e4eee13


fix CFA for BindingElement. #49759

Fixes #49759

@typescript-bot perf test this

I didn't notice a performance difference, which is a little surprising if every parameter is now getting a control flow node.

I think it's because no extra flow node is created if initializers are not used.

Just the one change for consistency, but LGTM at this point. Thanks for making that change.

Seems good to me; I was worried that I might be missing a case where nodes are bound more than once, but in my testing, this PR doesn't do that, which is good. (Some code paths do, but that's another issue.)

This is kind of a new feature, likely to expose some new breaks because of better typing, and we're getting close to the 4.8 RC. Let's hold this until 4.9.
(Unless @DanielRosenwasser disagrees)

I agree - but also, why not actually run the tests here?
@typescript-bot test this
@typescript-bot user test this
@typescript-bot run dt