Clean invalid utf-8 chars from subject

Maybe now it's a little clearer. Right @gabebw. :wink:

@gabebw? Someone else?

Merged -- thanks!

:tada: :fireworks: :shipit:


Failed migration leaves database in a bad state

Gitea version (or commit ref): df255783
Git version: 2.17.1
Operating system: Linux x86_64
Database (use [x]):

[x] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[x] Yes (provide example URL) - https://try.gitea.io/rob2/nope
[ ] No
[ ] Not relevant

Log gist:

Description
Failed migration does not rollback database properly.
To recreate:

Visit https://try.gitea.io/repo/migrate
Enter clone URL https://github.com/nope/nope.git and repo name nope
Leave clone authentication blank
Submit form

**Expected behaviour: **
See error message Authentication failed: Clone: exit status 128 - fatal: could not read Username for 'https://github.com': No such device or address and no repo is created in the database
Actual behaviour
Error message above is displayed but an empty repo is also created in the database, shows on the user's profile and generates a 500 when visited.
Note that deleting the repo from the DB is not enough to clean this up, there are also entries in the action table too (and possibly elsewhere)
Screenshots
N/A

This occurs because when the rollback should be attempted here, g.repo is nil.


[SPARK-15658][SQL] UDT serializer should declare its data type as udt instead of udt.sqlType

What changes were proposed in this pull request?
When we build serializer for UDT object, we should declare its data type as udt instead of udt.sqlType, or if we deserialize it again, we lose the information that it's a udt object and throw analysis exception.
How was this patch tested?
new test in UserDefiendTypeSuite

cc @yhuai @zsxwing

Test build #59633 has started for PR 13402 at commit 6d614dd.

Test build #59633 has finished for PR 13402 at commit 6d614dd.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59633/
Test PASSed.

Merged build finished. Test PASSed.

LGTM. Merging to master and branch 2.0.


4.17.0 breaking changes

v4.17.0 or v4.17.1 seems to include breaking changes. Got a failing build with an un-edited schema
                                 # Importing Amplify environment: dev (amplify env import)
2020-03-23T23:50:33.758Z [INFO]: Successfully added environment from your project
2020-03-23T23:50:33.779Z [INFO]: # Initializing existing Amplify environment: dev (amplify init)
2020-03-23T23:50:37.172Z [INFO]: Note: It is recommended to run this command from the root of your app directory
2020-03-23T23:50:41.009Z [WARNING]: - Initializing your environment: dev
2020-03-23T23:50:42.817Z [WARNING]: ✔ Initialized provider successfully.
2020-03-23T23:50:42.979Z [WARNING]: ✖ An error occurred when pushing the resources to the cloud
2020-03-23T23:50:42.979Z [WARNING]: ✖ There was an error initializing your environment.
2020-03-23T23:50:42.980Z [INFO]: init failed
2020-03-23T23:50:42.981Z [INFO]: { SchemaValidationError: Schema Errors:
                                 Unknown argument "keyName" on directive "@connection". Did you mean "name"?
                                 GraphQL request (53:56)
                                 52:   riskControlLinks: [RiskControlComplianceControlLink] @connection(name: "ComplianceRiskLink")
                                 53:   recommendations: [ControlRecommendation] @connection(keyName: "byControl", fields: ["id"])
                                 ^
                                 54:   changes: [ControlChange] @connection(keyName: "changesByControl", fields: ["id"])
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (53:78)
                                 52:   riskControlLinks: [RiskControlComplianceControlLink] @connection(name: "ComplianceRiskLink")
                                 53:   recommendations: [ControlRecommendation] @connection(keyName: "byControl", fields: ["id"])
                                 ^
                                 54:   changes: [ControlChange] @connection(keyName: "changesByControl", fields: ["id"])
                                 Unknown argument "keyName" on directive "@connection". Did you mean "name"?
                                 GraphQL request (54:40)
                                 53:   recommendations: [ControlRecommendation] @connection(keyName: "byControl", fields: ["id"])
                                 54:   changes: [ControlChange] @connection(keyName: "changesByControl", fields: ["id"])
                                 ^
                                 55: }
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (54:69)
                                 53:   recommendations: [ControlRecommendation] @connection(keyName: "byControl", fields: ["id"])
                                 54:   changes: [ControlChange] @connection(keyName: "changesByControl", fields: ["id"])
                                 ^
                                 55: }
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (85:32)
                                 84:   controlID: ID!
                                 85:   control: Control @connection(fields: ["controlID"])
                                 ^
                                 86:   resolved: String
                                 Unknown argument "keyName" on directive "@connection". Did you mean "name"?
                                 GraphQL request (165:63)
                                 164:   riskControlOverrides: [RiskControlOverride]
                                 165:   informationAssets: [SystemInformationAssetLink] @connection(keyName: "bySystem", fields: ["id"])
                                 ^
                                 166:   organizationRisks: [OrganizationRiskSystemLink] @connection(keyName: "bySystem", fields: ["id"])
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (165:84)
                                 164:   riskControlOverrides: [RiskControlOverride]
                                 165:   informationAssets: [SystemInformationAssetLink] @connection(keyName: "bySystem", fields: ["id"])
                                 ^
                                 166:   organizationRisks: [OrganizationRiskSystemLink] @connection(keyName: "bySystem", fields: ["id"])
                                 Unknown argument "keyName" on directive "@connection". Did you mean "name"?
                                 GraphQL request (166:63)
                                 165:   informationAssets: [SystemInformationAssetLink] @connection(keyName: "bySystem", fields: ["id"])
                                 166:   organizationRisks: [OrganizationRiskSystemLink] @connection(keyName: "bySystem", fields: ["id"])
                                 ^
                                 167:   controlCategories: [SystemControlCategoryLink] @connection(keyName: "systemByControlCategory", fields: ["id"])
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (166:84)
                                 165:   informationAssets: [SystemInformationAssetLink] @connection(keyName: "bySystem", fields: ["id"])
                                 166:   organizationRisks: [OrganizationRiskSystemLink] @connection(keyName: "bySystem", fields: ["id"])
                                 ^
                                 167:   controlCategories: [SystemControlCategoryLink] @connection(keyName: "systemByControlCategory", fields: ["id"])
                                 Unknown argument "keyName" on directive "@connection". Did you mean "name"?
                                 GraphQL request (167:62)
                                 166:   organizationRisks: [OrganizationRiskSystemLink] @connection(keyName: "bySystem", fields: ["id"])
                                 167:   controlCategories: [SystemControlCategoryLink] @connection(keyName: "systemByControlCategory", fields: ["id"])
                                 ^
                                 168: }
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (167:98)
                                 166:   organizationRisks: [OrganizationRiskSystemLink] @connection(keyName: "bySystem", fields: ["id"])
                                 167:   controlCategories: [SystemControlCategoryLink] @connection(keyName: "systemByControlCategory", fields: ["id"])
                                 ^
                                 168: }
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (181:31)
                                 180:   informationAssetID: ID!
                                 181:   system: System! @connection(fields: ["systemID"])
                                 ^
                                 182:   informationAsset: InformationAsset! @connection(fields: ["informationAssetID"])
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (182:51)
                                 181:   system: System! @connection(fields: ["systemID"])
                                 182:   informationAsset: InformationAsset! @connection(fields: ["informationAssetID"])
                                 ^
                                 183:   numberOfRecords: Int
                                 Unknown argument "keyName" on directive "@connection". Did you mean "name"?
                                 GraphQL request (194:53)
                                 193:   integrity: RatingScale
                                 194:   systems: [SystemInformationAssetLink] @connection(keyName: "byInformationAsset", fields: ["id"])
                                 ^
                                 195:   ownerGroup: String
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (194:84)
                                 193:   integrity: RatingScale
                                 194:   systems: [SystemInformationAssetLink] @connection(keyName: "byInformationAsset", fields: ["id"])
                                 ^
                                 195:   ownerGroup: String
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (286:52)
                                 285:   controlCategoryID: ID!
                                 286:   controlCategory: RiskControlCategory @connection(fields: ["controlCategoryID"])
                                 ^
                                 287:   riskControls: [RiskControl] @connection(name: "RiskControls")
                                 Unknown argument "keyName" on directive "@connection". Did you mean "name"?
                                 GraphQL request (288:64)
                                 287:   riskControls: [RiskControl] @connection(name: "RiskControls")
                                 288:   riskControlCategories: [RiskControlCategoryLink] @connection(keyName: "riskByControlCategory", fields: ["id"])
                                 ^
                                 289:   systems: [SystemRiskLink] @connection(name: "RiskSystemLink")
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (288:98)
                                 287:   riskControls: [RiskControl] @connection(name: "RiskControls")
                                 288:   riskControlCategories: [RiskControlCategoryLink] @connection(keyName: "riskByControlCategory", fields: ["id"])
                                 ^
                                 289:   systems: [SystemRiskLink] @connection(name: "RiskSystemLink")
                                 Unknown argument "keyName" on directive "@connection". Did you mean "name"?
                                 GraphQL request (334:43)
                                 333:   ownerGroup: String
                                 334:   systems: [SystemThreatLink] @connection(keyName: "byThreat", fields: ["id"])
                                 ^
                                 335:   systemRiskLinks: [SystemRiskThreatLink] @connection(name: "SystemRiskLinkThreat")
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (334:64)
                                 333:   ownerGroup: String
                                 334:   systems: [SystemThreatLink] @connection(keyName: "byThreat", fields: ["id"])
                                 ^
                                 335:   systemRiskLinks: [SystemRiskThreatLink] @connection(name: "SystemRiskLinkThreat")
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (349:31)
                                 348:   threatID: ID!
                                 349:   system: System! @connection(fields: ["systemID"])
                                 ^
                                 350:   threat: Threat! @connection(fields: ["threatID"])
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (350:31)
                                 349:   system: System! @connection(fields: ["systemID"])
                                 350:   threat: Threat! @connection(fields: ["threatID"])
                                 ^
                                 351:   ownerGroup: String
                                 Unknown argument "keyName" on directive "@connection". Did you mean "name"?
                                 GraphQL request (385:42)
                                 384:   description: String
                                 385:   subControls: [RiskControl] @connection(keyName: "byControlCategory", fields: ["id"])
                                 ^
                                 386:   systems: [SystemControlCategoryLink] @connection(keyName: "controlCategoryBySystem", fields: ["id"])
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (385:72)
                                 384:   description: String
                                 385:   subControls: [RiskControl] @connection(keyName: "byControlCategory", fields: ["id"])
                                 ^
                                 386:   systems: [SystemControlCategoryLink] @connection(keyName: "controlCategoryBySystem", fields: ["id"])
                                 Unknown argument "keyName" on directive "@connection". Did you mean "name"?
                                 GraphQL request (386:52)
                                 385:   subControls: [RiskControl] @connection(keyName: "byControlCategory", fields: ["id"])
                                 386:   systems: [SystemControlCategoryLink] @connection(keyName: "controlCategoryBySystem", fields: ["id"])
                                 ^
                                 387: #  keyRiskIndicatorID: ID!
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (386:88)
                                 385:   subControls: [RiskControl] @connection(keyName: "byControlCategory", fields: ["id"])
                                 386:   systems: [SystemControlCategoryLink] @connection(keyName: "controlCategoryBySystem", fields: ["id"])
                                 ^
                                 387: #  keyRiskIndicatorID: ID!
                                 Unknown argument "keyName" on directive "@connection". Did you mean "name"?
                                 GraphQL request (389:48)
                                 388: #  keyRiskIndicator: Risk @connection(fields: ["keyRiskIndicatorID"])
                                 389:   risks: [RiskControlCategoryLink] @connection(keyName: "controlCategoryByRisk", fields: ["id"])
                                 ^
                                 390: }
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (389:82)
                                 388: #  keyRiskIndicator: Risk @connection(fields: ["keyRiskIndicatorID"])
                                 389:   risks: [RiskControlCategoryLink] @connection(keyName: "controlCategoryByRisk", fields: ["id"])
                                 ^
                                 390: }
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (405:57)
                                 404:   riskID: ID!
                                 405:   riskControlCategory: RiskControlCategory! @connection(fields: ["riskControlCategoryID"])
                                 ^
                                 406:   risk: Risk! @connection(fields: ["riskID"])
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (406:27)
                                 405:   riskControlCategory: RiskControlCategory! @connection(fields: ["riskControlCategoryID"])
                                 406:   risk: Risk! @connection(fields: ["riskID"])
                                 ^
                                 407: }
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (422:57)
                                 421:   systemID: ID!
                                 422:   riskControlCategory: RiskControlCategory! @connection(fields: ["riskControlCategoryID"])
                                 ^
                                 423:   system: System! @connection(fields: ["systemID"])
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (423:31)
                                 422:   riskControlCategory: RiskControlCategory! @connection(fields: ["riskControlCategoryID"])
                                 423:   system: System! @connection(fields: ["systemID"])
                                 ^
                                 424: }
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (450:52)
                                 449:   controlCategoryID: ID!
                                 450:   controlCategory: RiskControlCategory @connection(fields: ["controlCategoryID"])
                                 ^
                                 451: }
                                 Unknown argument "keyName" on directive "@connection". Did you mean "name"?
                                 GraphQL request (535:53)
                                 534:   ownerGroup: String
                                 535:   systems: [OrganizationRiskSystemLink] @connection(keyName: "byOrganizationRisk", fields: ["id"])
                                 ^
                                 536: #  risks: [RiskOrganizationRiskLink] @connection(keyName: "risksByOrganizationRisk", fields: ["id"])
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (535:84)
                                 534:   ownerGroup: String
                                 535:   systems: [OrganizationRiskSystemLink] @connection(keyName: "byOrganizationRisk", fields: ["id"])
                                 ^
                                 536: #  risks: [RiskOrganizationRiskLink] @connection(keyName: "risksByOrganizationRisk", fields: ["id"])
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (547:51)
                                 546:   systemID: ID!
                                 547:   organizationRisk: OrganizationRisk! @connection(fields: ["organizationRiskID"])
                                 ^
                                 548:   system: System! @connection(fields: ["systemID"])
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (548:31)
                                 547:   organizationRisk: OrganizationRisk! @connection(fields: ["organizationRiskID"])
                                 548:   system: System! @connection(fields: ["systemID"])
                                 ^
                                 549: }
                                 Expected type AuthStrategy, found public.
                                 GraphQL request (668:12)
                                 667:   { allow: groups, groups: ["Admin"] },
                                 668:   { allow: public, provider: iam }
                                 ^
                                 669: ]){
                                 Field "provider" is not defined by type AuthRule.
                                 GraphQL request (668:20)
                                 667:   { allow: groups, groups: ["Admin"] },
                                 668:   { allow: public, provider: iam }
                                 ^
                                 669: ]){
                                 Unknown argument "keyName" on directive "@connection". Did you mean "name"?
                                 GraphQL request (677:53)
                                 676:   targets: [Target] @connection(name: "AssessmentTargets")
                                 677:   findingLinks: [AssessmentFindingLink] @connection(keyName: "byAssessment", fields: ["id"])
                                 ^
                                 678:   pointOfContact: PointOfContact @connection(name: "AssessmentPointOfContact")
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (677:78)
                                 676:   targets: [Target] @connection(name: "AssessmentTargets")
                                 677:   findingLinks: [AssessmentFindingLink] @connection(keyName: "byAssessment", fields: ["id"])
                                 ^
                                 678:   pointOfContact: PointOfContact @connection(name: "AssessmentPointOfContact")
                                 Expected type AuthStrategy, found public.
                                 GraphQL request (699:12)
                                 698:   { allow: groups, groups: ["Admin"] },
                                 699:   { allow: public, provider: iam }
                                 ^
                                 700: ]){
                                 Field "provider" is not defined by type AuthRule.
                                 GraphQL request (699:20)
                                 698:   { allow: groups, groups: ["Admin"] },
                                 699:   { allow: public, provider: iam }
                                 ^
                                 700: ]){
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (704:39)
                                 703:   findingID: ID!
                                 704:   assessment: Assessment! @connection(fields: ["assessmentID"])
                                 ^
                                 705:   finding: Finding! @connection(fields: ["findingID"])
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (705:33)
                                 704:   assessment: Assessment! @connection(fields: ["assessmentID"])
                                 705:   finding: Finding! @connection(fields: ["findingID"])
                                 ^
                                 706:   ownerGroup: String
                                 Expected type AuthStrategy, found public.
                                 GraphQL request (712:12)
                                 711:   { allow: groups, groups: ["Admin"] },
                                 712:   { allow: public, provider: iam }
                                 ^
                                 713: ]){
                                 Field "provider" is not defined by type AuthRule.
                                 GraphQL request (712:20)
                                 711:   { allow: groups, groups: ["Admin"] },
                                 712:   { allow: public, provider: iam }
                                 ^
                                 713: ]){
                                 Expected type AuthStrategy, found public.
                                 GraphQL request (747:12)
                                 746:   { allow: groups, groups: ["Admin"] },
                                 747:   { allow: public, provider: iam }
                                 ^
                                 748: ]){
                                 Field "provider" is not defined by type AuthRule.
                                 GraphQL request (747:20)
                                 746:   { allow: groups, groups: ["Admin"] },
                                 747:   { allow: public, provider: iam }
                                 ^
                                 748: ]){
                                 Unknown argument "keyName" on directive "@connection". Did you mean "name"?
                                 GraphQL request (764:56)
                                 763:   findingTargetId: String
                                 764:   assessmentLinks: [AssessmentFindingLink] @connection(keyName: "byFinding", fields: ["id"])
                                 ^
                                 765:   findingAssessmentId: String
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (764:78)
                                 763:   findingTargetId: String
                                 764:   assessmentLinks: [AssessmentFindingLink] @connection(keyName: "byFinding", fields: ["id"])
                                 ^
                                 765:   findingAssessmentId: String
                                 Expected type AuthStrategy, found public.
                                 GraphQL request (773:12)
                                 772:   { allow: groups, groups: ["Admin"] },
                                 773:   { allow: public, provider: iam }
                                 ^
                                 774: ]){
                                 Field "provider" is not defined by type AuthRule.
                                 GraphQL request (773:20)
                                 772:   { allow: groups, groups: ["Admin"] },
                                 773:   { allow: public, provider: iam }
                                 ^
                                 774: ]){
                                 Unknown argument "keyName" on directive "@connection". Did you mean "name"?
                                 GraphQL request (801:42)
                                 800:   accountType: String
                                 801:   roleLinks:  [UserRoleLink] @connection(keyName: "byUser", fields: ["id"])
                                 ^
                                 802: }
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (801:61)
                                 800:   accountType: String
                                 801:   roleLinks:  [UserRoleLink] @connection(keyName: "byUser", fields: ["id"])
                                 ^
                                 802: }
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (815:27)
                                 814:   roleID: ID!
                                 815:   user: User! @connection(fields: ["userID"])
                                 ^
                                 816:   role: Role! @connection(fields: ["roleID"])
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (816:27)
                                 815:   user: User! @connection(fields: ["userID"])
                                 816:   role: Role! @connection(fields: ["roleID"])
                                 ^
                                 817:   ownerGroup: String
                                 Unknown argument "keyName" on directive "@connection". Did you mean "name"?
                                 GraphQL request (845:41)
                                 844:   name: String!
                                 845:   userLinks: [UserRoleLink] @connection(keyName: "byRole", fields: ["id"])
                                 ^
                                 846:   roleConfig: AWSJSON
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (845:60)
                                 844:   name: String!
                                 845:   userLinks: [UserRoleLink] @connection(keyName: "byRole", fields: ["id"])
                                 ^
                                 846:   roleConfig: AWSJSON
                                 Unknown argument "keyName" on directive "@connection". Did you mean "name"?
                                 GraphQL request (992:37)
                                 991:   ownerGroup: String
                                 992:   reviewers: [Reviewer] @connection(keyName: "byPolicyVersion", fields: ["id"])
                                 ^
                                 993:   policy: Policy @connection(name: "PolicyPolicyVersions")
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (992:65)
                                 991:   ownerGroup: String
                                 992:   reviewers: [Reviewer] @connection(keyName: "byPolicyVersion", fields: ["id"])
                                 ^
                                 993:   policy: Policy @connection(name: "PolicyPolicyVersions")
                                 Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
                                 GraphQL request (1010:44)
                                 1009:   policyVersionID: ID!
                                 1010:   policyVersion: PolicyVersion @connection(fields: ["policyVersionID"])
                                 ^
                                 1011: }
                                 at GraphQLTransform.transform (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/graphql-transformer-core/lib/GraphQLTransform.js:191:19)
                                 at /root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/graphql-transformer-core/lib/util/amplifyUtils.js:100:49
                                 at step (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/graphql-transformer-core/lib/util/amplifyUtils.js:43:23)
                                 at Object.next (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/graphql-transformer-core/lib/util/amplifyUtils.js:24:53)
                                 at fulfilled (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/graphql-transformer-core/lib/util/amplifyUtils.js:15:58) name: 'SchemaValidationError' }
2020-03-23T23:50:43.031Z [ERROR]: !!! Build failed
2020-03-23T23:50:43.031Z [ERROR]: !!! Non-Zero Exit Code detected
2020-03-23T23:50:43.031Z [INFO]: # Starting environment caching...
2020-03-23T23:50:43.032Z [INFO]: # Uploading environment cache artifact...
2020-03-23T23:50:43.127Z [INFO]: # Environment caching completed
Terminating logging...

Reverting back to 4.16.1 allows the build to success.

@blazinaj this should not be an issue, could you please share your schema with us? if you can't post it here, please send it to<EMAIL_ADDRESS>

@blazinaj this should not be an issue, could you please share your schema with us? if you can't post it here, please send it to<EMAIL_ADDRESS>
New to amplify but believe i am getting the same issue (though tried reverting version and still same message) - let me know if you dont get what you need to reproduce, I can share my schema.
Thanks

I have the same issue. Adding example type and error, but it's breaking for all types in the schema.
Schema (one of the types)
type Restaurant
  @model(subscriptions: null)
  @auth(
    rules: [
      { allow: owner }
      { allow: groups, groups: ["Admin"] }
      { allow: public, operations: [read] }
    ]
  ) {
  id: ID!
  createdAt: AWSDateTime
  updatedAt: AWSDateTime

  name: String!
  description: String
  cuisine: String
  rating: Float
  openingHours: AWSJSON
  priceRange: String
  image: String
  logo: String
  active: Boolean
  avgPickupTime: String
  city: City @connection(name: "RestaurantCity")
  location: AWSJSON
  carts: [Cart] @connection(name: "RestaurantCarts")
  orders: [Order] @connection(name: "RestaurantOrders")
  categories: [Category] @connection(name: "RestaurantCategory")
  items: [Item] @connection(keyName: "byRestaurant", keyField: ["id"])
}

Error:
{ SchemaValidationError: Schema Errors:
Expected type AuthStrategy, found public.
GraphQL request (35:16)
34:       { allow: groups, groups: ["Admin"] }
35:       { allow: public, operations: [read] }
^
36:     ]
Unknown argument "keyName" on directive "@connection". Did you mean "name"?
GraphQL request (57:29)
56:   categories: [Category] @connection(name: "RestaurantCategory")
57:   items: [Item] @connection(keyName: "byRestaurant", fields: ["id"])
^
58:   # items: [Item] @connection(name: "RestaurantItems")
Unknown argument "fields" on directive "@connection". Did you mean "keyField"?
GraphQL request (57:54)
56:   categories: [Category] @connection(name: "RestaurantCategory")
57:   items: [Item] @connection(keyName: "byRestaurant", fields: ["id"])
^
58:   # items: [Item] @connection(name: "RestaurantItems")

Try changing the @connection in city, carts, orders and categories to be keyName rather than name.

@blazinaj & @thejool Were you'll able to get unblocked based on @kevstafford82's recommendation?

It started to work again after I updated the CLI at a certain point. I don't know what version it was though. Seems to have been isolated to 4.17.x

For anyone else running into this, make sure you have this option set in your build image settings


Fix: handle NULL input for regex match operations

Which issue does this PR close?
Closes #11623
Rationale for this change
For regex match operations, handle NULL input, such as
select v1 ~ null from t; --- described in #11623
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?

Thanks again @HuSen8891


updated the command for the inventory UI

I had issues with this command and found a solution to resolve these issues.

closing... kubectl get -n tools secrets | grep -E "binding.*appid" did not realized the -n flag is the specific pod label we are looking for.


bluetooth usb adaptor not working : No such file or directory

Hi !
Before all, thanks so much for this project !
I'm french, so please excuse my possible mistakes :sweat_smile:
I'm trying to have a surround sound system using bluetooth speakers.
I have a raspberry pi 3 B with raspbian Stretch installed on it, and v1.2.0 of bluealsa.

First, I configured stereo (with .asoundrc file) and it was working very well.

Then, I connected 4 speakers (using bluetoothctl) to the the pi's bluetooth chip.
I try running a multi-channels file (aplay -D surround4 surround4.wav), sometimes it is working (I can hear 4 different sounds on each speaker) but other times I've this error : aplay: xrun:1624: read/write error, state = PREPARED
According to my search, it may come because of underruns (I quite surprised because it's working when my speakers have an auto connection   - when they reconnect without my help : param trust  on bluetoothctl -  but it's not working just after doing a manual connection).

Here comes my main issue : I want to test connecting two speakers to the pi's chip and two others on a usb bluetooth. And it works.
But I don't know why I can't play anything on the devices connected to the usb dongle (corresponding to hci1)

I have this error :
$aplay -D bluealsa:HCI=hci1,DEV=00:E0:4C:7C:1A:62,PROFILE=a2dp test.wav
../../../src/asound/../shared/ctl-client.c:102: Connecting to socket: /var/run/bluealsa/hci1
ALSA lib ../../../src/asound/bluealsa-pcm.c:666:(_snd_pcm_bluealsa_open) BlueALSA connection failed: No such file or directory
aplay: main:788: audio open error: No such file or directory

I think I have to initialize hci1 thread (there is no hci1 in /var/run/bluealsa/ but hci0, corresponding to the pi's chip, exist) but I don't know how to do it...
Thanks for your help ! (and sorry for the english mistakes :speak_no_evil: )

My .asoundrc file ( I modify hci0 in hci1 in LeftSur and RightSur when I try to play on the bluetooth adaptor.)
pcm.!default {
    type plug;
    slave.pcm "stereo";
}

pcm.surround6 {
    type route;
    slave.pcm {
        type multi;
        slaves {
            a { channels 1 pcm "left" }
            b { channels 1 pcm "center" }
            c { channels 1 pcm "right" }
            d { channels 1 pcm "rightSur" }
            e { channels 1 pcm "leftSur" }
            f { channels 1 pcm "subwoofer" }
        }

        bindings {
         0 { slave a channel 0 }
         1 { slave b channel 0 }
         2 { slave c channel 0 }
         3 { slave d channel 0 }
         4 { slave e channel 0 }
         5 { slave f channel 0 }
        }
    }

    ttable [
        [ 1 0 0 0 0 0 ]
        [ 0 1 0 0 0 0 ]
        [ 0 0 1 0 0 0 ]
        [ 0 0 0 1 0 0 ]
        [ 0 0 0 0 1 0 ]
        [ 0 0 0 0 0 1 ]
    ]

}

pcm.surround4 {
    type route;
    slave.pcm {
        type multi;
        slaves {
            a { channels 1 pcm "left" }
            b { channels 1 pcm "right" }
            c { channels 1 pcm "rightSur" }
            d { channels 1 pcm "leftSur" }
        }

        bindings {
         0 { slave a channel 0 }
         1 { slave b channel 0 }
         2 { slave c channel 0 }
         3 { slave d channel 0 }
        }
    }
    ttable [
        [ 1 0 0 0 ]
        [ 0 1 0 0 ]
        [ 0 0 1 0 ]
        [ 0 0 0 1 ]
    ]

}

pcm.stereo {
    type route;
    slave.pcm {
        type multi;
        slaves {
            a { channels 1 pcm "left" }
            b { channels 1 pcm "right" }
        }

        bindings {
         0 { slave a channel 0 }
         1 { slave b channel 0 }
        }
    }

    ttable [
        [ 1 0 ]
        [ 0 1 ]
    ]
}

pcm.stereoSur {
    type route;
    slave.pcm {
        type multi;
        slaves {
            a { channels 1 pcm "leftSur" }
            b { channels 1 pcm "rightSur" }
        }

        bindings {
         0 { slave a channel 0 }
         1 { slave b channel 0 }
        }
    }

    ttable [
        [ 1 0 ]
        [ 0 1 ]
    ]
}

pcm.left {
    type plug;
    slave.pcm {
        type bluealsa;
        interface "hci0";
        device "00:E0:4C:3E:7E:C0";
        profile "a2dp";
    }
}

pcm.center {
    type plug;
    slave.pcm {
        type bluealsa;
        interface "hci0";
        device "00:E0:4C:0E:69:A5"
        profile "a2dp";
    }
}

pcm.right {
    type plug;
    slave.pcm {
        type bluealsa;
        interface "hci0";
        device "00:E0:4C:D7:57:80";
        profile "a2dp";
    }
}

pcm.rightSur {
    type plug;
    slave.pcm {
        type bluealsa;
        interface "hci0";
        device "00:E0:4C:7C:1A:62";
        profile "a2dp";
    }
}

pcm.leftSur {
    type plug;
    slave.pcm {
        type bluealsa;
        interface "hci0";
        device "00:E0:4C:8B:19:72";
        profile "a2dp";
    }
}

pcm.subwoofer {
    type plug;
    slave.pcm {
        type bluealsa;
        interface "hci0";
        device "40:EF:4C:C7:DF:95";
        profile "a2dp";
    }
}

ctl.left {
    type bluealsa;
}

ctl.center {
    type bluealsa
}

ctl.rigth {
    type bluealsa;
}

ctl.subwoofer {
    type bluealsa;
}

I try initialize hci1 but here is the error :
$ bluealsa -i hci1
bluealsa: Couldn't initialize controller thread: Bad file descriptor


[3.11] elasticloadbalancing:DescribeTags permission is missing when run a cluster with login nodes

My 3.11.0 ParallelCluster deployment failed due to insufficient AWS permissions for a Lambda role created by the API stack. The Lambda function requires the permission 'elasticloadbalancing:DescribeTags', but this permission is not included in the policy configuration.
Most likely, this issue was caused by changes to the permissions in the 'cloudformation/policies/parallelcluster-policies.yaml' file since ParallelCluster version 3.10.1 where the elasticloadbalancing:Describe* permission was included.
The deployment succeeds when there are no login nodes in the cluster configuration, but fails when the login nodes section is included.
The cluster configuration:
  Region: eu-central-1
  CustomS3Bucket: parallelcluster-custom-bucket-name
  Image:
    Os: alinux2
  SharedStorage:
    - MountDir: /home
      Name: parallelcluster_shared
      StorageType: Ebs
      EbsSettings:
        VolumeType: gp3
        Size: 1000
        DeletionPolicy: Delete
  HeadNode:
    InstanceType: c5.large
    LocalStorage:
      RootVolume:
        Size: 100
        VolumeType: gp3
        DeleteOnTermination: true
    Networking:
      SubnetId: subnet-123456789123
    Iam:
      AdditionalIamPolicies:
        - Policy: arn:aws:iam::aws:policy/AmazonSSMManagedInstanceCore
    Ssh:
      KeyName: parallelcluster_ssh_key
  LoginNodes:
    Pools:
      - Name: login
        Count: 1
        InstanceType: t3.small
        Ssh:
          KeyName: parallelcluster_ssh_key
        Networking:
          SubnetIds:
            - subnet-123456789123
        Iam:
          AdditionalIamPolicies:
            - Policy: arn:aws:iam::aws:policy/AmazonSSMManagedInstanceCore
  Scheduling:
    Scheduler: slurm
    SlurmQueues:
      - Name: queue1
        CapacityType: SPOT
        Networking:
          SubnetIds:
            - subnet-123456789123
        Iam:
          AdditionalIamPolicies:
            - Policy: arn:aws:iam::aws:policy/AmazonSSMManagedInstanceCore
        ComputeResources:
          - InstanceType: c5.xlarge
            MinCount: 0
            MaxCount: 10
            Name: c5xlarge
    SlurmSettings:
      QueueUpdateStrategy: TERMINATE
      Dns:
        DisableManagedDns: true
        UseEc2Hostnames: true

Lambda logs for evidence:
    "level": "ERROR",
    "location": "common.py:107:wrapper()",
    "message": "Encountered error when performing boto3 call in describe_tags: User: arn:aws:sts::123456789123:assumed-role/ParallelClusterLambdaRole-1d812250/ParallelClusterAPI-ParallelClusterFunction-MxG8NLI7N3Nq is not authorized to perform: elasticloadbalancing:DescribeTags because no identity-based policy allows the elasticloadbalancing:DescribeTags action",
    "timestamp": "2024-10-20 14:49:14,667+0000",
    "service": "pcluster",
    "cold_start": false,
    "function_name": "ParallelClusterAPI-ParallelClusterFunction-MxG8NLI7N3Nq",
    "function_memory_size": "2048",
    "function_arn": "arn:aws:lambda:eu-central-1:123456789123:function:ParallelClusterAPI-ParallelClusterFunction-MxG8NLI7N3Nq",
    "function_request_id": "3948efa8-700f-4b83-b396-fc593f04033e",
    "xray_trace_id": "1-67151869-23d459f976b54e012b1dd398"

Hi,
this issue has been fixed in ParallelCluster 3.11.1


Can It play a blob file?

Should the player be able to play a blob file?
I am trying to download 2 vimeo clips from my vimeo account both with vanilla XHR and with axios, then make them into their respective blob in order to have 'em ready to play without having to load first. I need really quick response and no loading time.
So when I call this.load(url), can url be a blob file?
At the moment, I can't make it work. Here is the code that I have to fetch the clips.
With axios:
  const endpoint = '/oembed.json';

  function fetchRessource(url) {
    return axios(endpoint, {
      method: 'GET',
      baseURL: 'https://vimeo.com/api/',
      params: { url: url, },
      responseType: 'blob',
      onDownloadProgress: event => console.log('Downloading... -> ', event)
    })
      .then(blob => { return blobUtil.createObjectURL(new Blob([blob])) })
      .catch(err => `Could not create the objectURL from the arrayBuffer - ${err}`); // IE10+
  }

  return axios.all([
    fetchRessource(url1),
    fetchRessource(url2)
  ])
  .then(axios.spread((url1, url2) => {
    return [url1, url2];
  }));

This gives me back the blobURLs but throws this when I am trying to play them:
onError Event {isTrusted: true, type: "error", target: video, currentTarget: video, eventPhase: 2…}bubbles: falsecancelBubble: falsecancelable: truecomposed: falsecurrentTarget: nulldefaultPrevented: falseeventPhase: 0isTrusted: truepath: Array[10]returnValue: truesrcElement: videotarget: videotimeStamp: 9187.02type: "error"__proto__: Event
Looks like a Media error: code 4
With XHR:
function loadIt(file) {
  const req = new XMLHttpRequest();
  req.onload = () => { return URL.createObjectURL(req.response) };
  req.open("GET", file);
  req.setRequestHeader('Access-Control-Allow-Origin', '*');
  req.responseType = "blob";
  req.send();
}

This throws another error and is not even able to get anything from the server:
XMLHttpRequest cannot load https://vimeo.com/187265782/83876b2cdc. Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:3000' is therefore not allowed access.

Have you tried copying and pasting the resulting blob string into a new tab to see if the file plays? ReactPlayer should play blob strings fine as long as the HTML5 media player can handle it when set as the src. I have tested playing a blob string from a simple <input type='file' /> and it seemed to work ok.

Yeah, it seems to be working when uploading a file through the input form but what I am trying to do is to download an entire vimeo clip from my account (about 17 seconds), store it in a blob and then have it play instantly when needed, without having to spend 1 or 2 seconds of loading time.
And no, the blob that I've gotten from the XHR call to vimeo does not play on its own when url is copy/pasted in an empty browser tab.
Not sure what to do next...

Oh, actually, when I copy/paste the blobURL in the address bar, this is what I get:
[object Object]
Means anything to you?

Is there any reason you aren't just rendering a player and waiting for the onReady callback instead of waiting for an XHR to complete?
// state = { playing: false }
<ReactPlayer
  url='http://vimeo.com/blah'
  playing={this.state.playing}
  onReady={() => {
    // Video is loaded and ready to play now
    // To start playing:
    this.setState({ playing: true })
  }}
/>

Seems like it would get the same result without the blob weirdness.

I am building an app in which I work clips by 3's; a question clip, a right answer clip and a wrong answer clip. When the question clip is loaded and fires the onReady event, I want to load both answer clips in blobs so that when the question clip offers a set of choices, and the user clicks on one, either the right and wrong answer clips are ready to fire off without any delay.
So the onReady event of the question clip is used to make 2 ajax calls to vimeo to get the 2 answer clips.

I would simply render three ReactPlayers with the question and answer clips all loaded (with playing set to false for the answer clips), then just hide/show/play the relevant player depending on the answer. You would be waiting the same amount of time (probably longer) to load in blob strings compared to waiting for each iframe to call onReady.

That is a considerable suggestion, thank you. I'll see how I can implement that in my project.

@CookPete From what I can see, react-player no longer plays blobs, does it? I'm trying to feed it a file from <input type="file"... if anything. And it plays the video when I paste the URL into another tab.

@x-yuri ReactPlayer will fall back to the FilePlayer if it cannot play the URL with other players. Playing blobs should still work. It works for me in this fiddle using URL.createObjectURL():
https://jsfiddle.net/0pn9avov/

@CookPete Is it possible to do the same with the hls (.m3u8) video file?


Python script started as .\script.py runs in new window

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
Tested under Windows Terminal 1.15.3466.0 in Windows 11 22H2 22621.963 in PowerShell 7.3.1 profile with Python 3.11.0 installed. Steps to reproduce:

Execute python script directly by specifying its name: .\script.py.

script.py:
print("Hello, press ENTER")
input()

File association as shown by the Command Prompt (cmd.exe):
C:\Users\work> ftype Python.File
Python.File="C:\WINDOWS\py.exe" "%L" %*

When the following is executed directly in the PowerShell prompt, it works fine, i.e. no new window is opened:

C:\WINDOWS\py.exe .\script.py
C:\Users\work\AppData\Local\Programs\Python\Python311\python.exe .\script.py

The same .\script.py works fine when executed from Command Prompt profile (cmd.exe).
Expected behavior
The script is executed in the same window, i.e. with output:
C:\Users\work\> .\script.py
Hello, press ENTER

Actual behavior
New console window opens with text:
Hello, press ENTER

Error details
No response
Environment data
Name                           Value
----                           -----
PSVersion                      7.3.1
PSEdition                      Core
GitCommitId                    7.3.1
OS                             Microsoft Windows 10.0.22621
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Visuals
No response

You are my hero, it finally works. I could not find anything mentioning this very crucial information.


Added two traits for testing using the new trait testing support in grails 3.

Allows to do this:
class AccountSpec extends Specification implements BuildDomainUnitTest<Account>{

    void "expect validation to succeed when account is saved "(){
        when:
            domain.save()
        then:
            domain.errors.errorCount == 0
    }
}

Changing implementation


Fix “formatter shortcut” logic in cell function.

I came across a bug: given the following setup, the table cells would not display correct value.
// data:
[{someColumn: 42}]

// columns:
[{
  property: 'someColumn',
  cell: v => v-42
}]

// Expected: A cell that shows "0"
// Actual: A cell that shows "42"

The cause lies in L73 of src/table.js. If val is falsy (like 0 in this case), it won't get wrapped as {value: val}, and merge() in L78 would ignore all non-object arguments when merging.
L73 should be testing if val needs wrapping. Thus I've fixed this by checking if val is a plain object instead. Hope it makes sense :)

Thanks for the fix! Just published a patch version containing it.


Denial of service vulnerability in adapter-node

Describe the bug
There is a remote denial of service vulnerability that allows attackers to crash the default web server for adapter-node.
Logs
The only logs I have are this:
May 22 22:36:08 sanipasse node[117756]: node:internal/process/promises:246
May 22 22:36:08 sanipasse node[117756]:           triggerUncaughtException(err, true /* fromPromise */);
May 22 22:36:08 sanipasse node[117756]:           ^
May 22 22:36:08 sanipasse node[117756]: Error: aborted
May 22 22:36:08 sanipasse node[117756]:     at connResetException (node:internal/errors:683:14)
May 22 22:36:08 sanipasse node[117756]:     at abortIncoming (node:_http_server:592:17)
May 22 22:36:08 sanipasse node[117756]:     at socketOnClose (node:_http_server:586:3)
May 22 22:36:08 sanipasse node[117756]:     at Socket.emit (node:events:377:35)
May 22 22:36:08 sanipasse node[117756]:     at TCP.<anonymous> (node:net:661:12) {
May 22 22:36:08 sanipasse node[117756]:   code: 'ECONNRESET'
May 22 22:36:08 sanipasse node[117756]: }
May 22 22:36:09 sanipasse systemd[1]: sanipasse.service: Main process exited, code=exited, status=1/FAILURE
May 22 22:36:09 sanipasse systemd[1]: sanipasse.service: Failed with result 'exit-code'.

To Reproduce
Run the default template sveltekit application with adapter-node on port 3000, then, from a terminal :
$ nc localhost 3000
POST /x HTTP/1.1
Content-Length: 1000
Content-Type: application/json

^C

Expected behavior
No one should be able to remotely crash the server.
Whatever their payload, the sveltekit server should not crash, especially before entering user-defined code.
Stacktraces
node:internal/process/promises:246
           triggerUncaughtException(err, true /* fromPromise */);
          ^
 Error: aborted
    at connResetException (node:internal/errors:683:14)
    at abortIncoming (node:_http_server:592:17)
    at socketOnClose (node:_http_server:586:3)
    at Socket.emit (node:events:377:35)
    at TCP.<anonymous> (node:net:661:12) {

Information about your SvelteKit Installation:

kit 1.0.0-next.107
node v16.1.0
Your adapter : node

Severity
This is a severe security vulnerability which allows anyone on the internet to take down any SvelteKit server.
I found this issue in my server logs, so there are actual people making these requests this in the wild.
All that is needed to crash the server is a client that closes the connection early while they are sending a json payload.
Additional context
I'll keep this issue updated if I manager to reproduce the crash myself.
Edit: I initially couldn't reproduce the crash myself. I edited the issue with the reproduction once I managed to reproduce the issue.

Looking a little deeper, it looks like adapter-node is using "polka" to handle requests, a framework which was last updated on npm 2 years ago, has just 200 commits on github, and seems to be maintained (not very actively) by a single person.
From an security point of view, this doesn't look great.

The problem is that neither adapter-node, nor polka itself catch the exception that may be thrown by getRawBody in
https://github.com/sveltejs/kit/blob/master/packages/adapter-node/src/server.js#L47

a framework which was last updated on npm 2 years ago

1.0.0-next.14 was added to GitHub just 2 months ago

This one is not stable. The latest stable version is 0.5.2, published 2 years ago

next.14 is the version currently being used by the Node adapter, not the two-year-old 0.5.2.


ionicbrackets.com has the wrong url listed for the zip file.

The url is ionicbrackets.org instead of .com .

Doh! Fixed


Enable kprobe-multi backend for kernel modules tracing (--kmods)

I'd be interested to work on this as my first contribution to pwru, any pointers to where I should start would be helpful 🙏

Thanks!
This commit https://github.com/cilium/pwru/commit/820fbb26 has some pointers why we did not enable the kprobe-multi backend when used with --kmods. IIRC the kernel fix should have been merged and backported.
You could try the following:

Drop the kmod check from https://github.com/cilium/pwru/blob/v1.0.9/main.go#L91
Troubleshoot if there are any ignored attachments when starting pwru (reporting as Attached (ignored X)). kmods might be not visible in available_filter_functions (https://github.com/cilium/pwru/blob/v1.0.9/internal/pwru/utils.go#L27), so more conditions might need to be relaxed.


Update ATM to use BTB 0.1.0

Update ATM to use BTB version 0.1.0 for comaptability.

merging. We will update ATM later to use the new api for BTB.


Repo sync for protected CLA branch

The pull request is created from main637792489552450241 to main to fix git push error for protected CLA branch

@huypub : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Do not store the WidgetTag + base impl of visitIds

Storing the WidgetTag is a waste of space. We rarely use it, and even then it's only an int so we can just codegen returning it directly.
Do not generate implementations of visitIds for nodes with no children. Have the base class invoke the lambda with the current node ID by default. Only nodes for widgets with children will override and do codegen.

[ ] CHANGELOG.md's "Unreleased" section has been updated, if applicable.

Working on #2145 and pulling some prerequisites out


Add circlehs

http://hackage.haskell.org/package/circlehs

servant-<IP_ADDRESS> (Haskell Servant<EMAIL_ADDRESS>@jkarni) is out of bounds for:

[ ] circlehs-0.0.3 (>=0.7 && < 0.9). Denis Shevchenko<EMAIL_ADDRESS>@denisshevchenko. @denisshevchenko

servant-client-<IP_ADDRESS> (Haskell Servant<EMAIL_ADDRESS>@jkarni) is out of bounds for:

[ ] circlehs-0.0.3 (>=0.7 && < 0.9). Denis Shevchenko<EMAIL_ADDRESS>@denisshevchenko. @denisshevchenko

Thanks. Unfortunately, servant has too many deep changes between versions 0.4* and 0.7.
I'll be waiting for your LTS with servant-0.7.

Okay, thanks - as a first step we're moving Nightly to 0.6 now hopefully.


Homophily batch support.

#3028
This PR updates torch_geometric.utils.homophily. homophily can now be called with batch.

Super. Thanks a lot!


Files app crashes often

Description
A lot of times, randomly without any patterns, the app crashes and says, "Files encountered an error not seen before" and then crashes without any error codes.
Steps To Reproduce

Open app
Try opening random folders

Since there is no pattern or error code observed, it is hard to say what exactly triggers the crash.
Expected behavior
The app should keep working smoothly instead of crashing.
Files Version
Version: <IP_ADDRESS>
Windows Version
Windows 11 Version 21HS (OS Build 22000.556)
Relevant Assets/Logs
debug.log
debug_fulltrust.log

Do you have show folder sizes enabled in files settings > experimental

From the log file, the error could be this one (unrelated to the issue of folder size):

11:28:58.3105|ERROR|AppUnhandledException|The parameter is incorrect.
The parameter is incorrect.

 I usually never turn on experimental
features.
Archan V Joshi
Software Engineer
M.S. (Systems Engineering)
On Thu, Mar 24, 2022 at 12:38 PM Josh-65 @.***> wrote:

Do you have show folder sizes enabled in files settings > experimental
—
Reply to this email directly, view it on GitHub
https://github.com/files-community/Files/issues/8759#issuecomment-1077819888,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF66D5SSD2VRJBYB5X6PRNTVBSK6VANCNFSM5RRQVXJQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Do you have show folder sizes enabled in files settings > experimental

Nope, that feature is turned off.

From the log file, the error could be this one (unrelated to the issue of folder size):

11:28:58.3105|ERROR|AppUnhandledException|The parameter is incorrect.
The parameter is incorrect.

It could be, developers can check when is that message printed and look for what use cases have been missed. I am not familiar with C#, so have not followed the codebase. Hopefully, I'd be a contributor at some point in the future.

We made a number of improvements in this area that will be included in the next release.

No idea what parameter it is talking about.
Archan V Joshi
Software Engineer
M.S. (Systems Engineering)
On Thu, Mar 24, 2022 at 2:20 PM Marco Gavelli @.***>
wrote:

From the log file, the error could be this one (unrelated to the issue of
folder size):
11:28:58.3105|ERROR|AppUnhandledException|The parameter is incorrect.
The parameter is incorrect.
—
Reply to this email directly, view it on GitHub
https://github.com/files-community/Files/issues/8759#issuecomment-1077915185,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF66D5TQTLDSAJVRFIECCZLVBSW7HANCNFSM5RRQVXJQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


Project's documentation site returns 404

The project's documentation site mentioned in the Documentation section (https://deck.yolo42.com) returns 404

Hello @jumal ,
I know they were planning to integrate deck's documentation as an official part of Kong's documentation, maybe the previous site has been closed to avoid having to maintain two versions.
You can find the documentation here.

I changed the default branch from master to main and that broke Github Pages. The master branch is still around but that still happened.
This should be fixed now.


Agrego excepciones y detalles de implementacion

Agrego excepciones y detalles de implementacion

Codecov Report

Merging #45 (1526a2a) into master (06bda20) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #45   +/-   ##
=========================================
  Coverage     66.62%   66.62%
  Complexity      304      304
=========================================
  Files            51       51
  Lines           860      860
  Branches         56       56
=========================================
  Hits            573      573
  Misses          286      286
  Partials          1        1

Continue to review full report at Codecov.

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


[iOS] shouldOverrideUrlLoading being called before LoadStart() and redirect URL same with initialUrlRequest.

[x] I have read the Get Started - Installation section
[x] I have read and done the Get Started - Setup Android section
[x] I have read and done the Get Started - Setup iOS section
[x] I have already searched for the same problem

Environment

Technology
Version

Flutter version
2.10.3

Plugin version
5.4.3

iOS version
15.2

Xcode version
13.2.1

initialUrlRequest = https://www.cnbeta.com/articles/tech/1263221.htm

Stacktrace/Logcat
// while on Android there is only an onLoadStart() event.
flutter: [DEBUG] shouldOverrideUrlLoading, isForMainFrame = true, redirectURL = https://www.cnbeta.com/articles/tech/1263221.htm
flutter: [DEBUG] onLoadStart, URL = https://www.cnbeta.com/articles/tech/1263221.htm

I don't understand, where is the problem?
I test the URL on both Android and iOS platforms and I can load the URL correctly.
The fact that the shouldOverrideUrlLoading event is being called before onLoadStart event is something related to the native platform itself.
When I get notified about an event from the native side, I call the event on the flutter side. That's it.

@pichillilorenzo Thank you for your reply.
This behavior seems is introduced in recently updates, so it should be consider as an expected behavior, right?

The code related to these events hasn't changed.
As I said, these events are sent by the native platform itself.
So, if you receive the shouldOverrideUrlLoading event before the onLoadStart event, it means that the native platform is sending them in this order (WKWebView native class on iOS and WebView native class on Android).
The plugin simply propagates these events to the Flutter side when they arrive.
To conclude, just to be clear, this is something that is not decided by my plugin, but by the native WebView engine of the platform.


Power Lora Loader string output?

Hi! Efficiency nodes has a Lora Stack to String converter node that I (want to) use to save the used loras with the image meta data with this custom nodes: https://github.com/alexopus/ComfyUI-Image-Saver. I can already do that with the Wildcard Encode node from the Inspire Pack, but doing it with a lora stacker would be cooler. Could you make this compatible with the Power Lora Loader node? Maybe an output to expose the converted strings or something? Because I like your Lora Loader even better than these lora stackers.
Thank you!

I second this request! I would love a node output that shows a list of all LoRAs activated in the Power LoRA Loader node. It would make logging and troubleshooting much easier.
Thank you.

3rd this request! I was actually just coming here to make the same request - it would be nice if it could be compatible with ComfyUI-Lora-Auto-Trigger-Words or if there were a method implemented into rgthree nodes to get lora trigger words either from comfyui or an associated civitai.info file.

This gets part of the way there.

Out of all LoRA-Loaders i think the Power LoRA Loader is the most comfortable one. I'd like to embedd the Metadata with it too, so i highly second the addition from @DrJKL

Alternatively having second node 'Power Lora Stack' would be great.

I came here looking for this feature, I've been wanting to add metadata, and this is only lora loader I like.


Bugfixes and Updates

:tada: This PR is included in version 1.9.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Road to v1.0

v1.0 has been started for more than a year.
@ceeram and I are now working towards the release of v1 of Opauth.
Some of the changes include:

A complete rewrite from v0.x while retaining the core ideas of Opauth.
No more internal callbacks.
Cleaner code base and API
PSR compliance
and many more...
To bring about these improvements, Opauth v1.x is not backward-compatible with v0.x.

Before we can hit the release of Opauth v1, here are still some tasks for us to complete:

[ ] Updated user guide (documentations):

[x] Upgrading guide (consumer)
[x] Upgrading guide (strategy author)
[ ] Strategy contribution guide

[ ] Updated API docs

[ ] Updated web site for v1

[ ] State support (test and document)

[x] Update strategies maintained by Opauth organisation to v1

[ ] Update community strategies from v0.x strategies to v1, submit PR for it and get all submitted to Packagist.

[ ] Sample app (or this can simply be opauth.org's source)

[ ] Better test coverage

Maybe / good to have

[ ] Fully integrated web site with the following:

User guide
API docs
List of strategies that can be easily updatable

[ ] Contact and/or update framework plugins for v1

[ ] Base strategies for common auth protocols

Schedules

[x] 1.0.0-alpha released on 7 April 2014.
stay tuned for next release schedule.

Wanting to help?
Join us at IRC: #opauth on Freenode

is this project abandoned?
There are just two commits since v1.0.0-alpha.1.

Yup. Sorry
Op 16 aug. 2015 22:52 schreef "Florian Krämer"<EMAIL_ADDRESS>
is this project abandoned?
There are just two commits since v1.0.0-alpha.1.
—
Reply to this email directly or view it on GitHub
https://github.com/opauth/opauth/issues/81#issuecomment-131620693.

@ceeram I read your "Yup" as "Yes, it has been abandoned". Meh... Why? Is there any alternative project? You should communicate on the main page of the project that it has been abandoned and point to an alternative or saying that you're looking for a maintainer.

I agree with @burzum it would be nice to mention that it's no longer developed in the readme. Perhaps you could point to http://hybridauth.sourceforge.net/

@burzum i see you think of writing a successor? how about adding you here as a maintainer instead?

@ceeram there is already a successor -> http://hybridauth.sourceforge.net/
And it would be fair and awesome to tell people that this project is abandoned, see https://github.com/opauth/opauth/issues/112#issuecomment-146530724

Not my job. Hybridauth has been next to opauth for a long time already. I
assumed you prefered to not use that as alternative to opauth and rather
roll your own. Also phpleague has an oauth solution.
Op 8 okt. 2015 19:57 schreef "Florian Krämer"<EMAIL_ADDRESS>
@ceeram https://github.com/ceeram there is already a successor ->
http://hybridauth.sourceforge.net/
And it would be fair and awesome to tell people that this project is
abandoned, see #112 (comment)
https://github.com/opauth/opauth/issues/112#issuecomment-146530724
—
Reply to this email directly or view it on GitHub
https://github.com/opauth/opauth/issues/81#issuecomment-146638258.


[Niri] Ability to query #window by focused app ID

While there is a way to see what the only window in a workspace is, it'd be really nice to be able to query it by the focused window instead.
This example is a bit rough, but it'd be nice to be able to have a different gradient per-app.
#window.code {
	background: linear-gradient(to top right, #31748f, #1f1d2e);
}

#window.firefox {
	background: linear-gradient(to top right, #BF616A, #1f1d2e);
}

/* so on and so forth */

I won't be making a PR for this one, not quite sure how this would be done tbh.

FWIW I made it this way only because the sway and hyprland modules also did it this way, only solo window. It's this line here:
https://github.com/Alexays/Waybar/blob/0d02f6877d88551ea2be0cd151c1e6354e208b1c/src/modules/niri/window.cpp#L78
Replacing isSolo with true should make it work regardless of whether it's the only window.


"Attempt to access an object not found in store" error

When trying to share the pulse logs, there is an error visible "Attemt to access an object not found in store". Didn't experienced myself, but got a video recording showing that.

Thanks for th e report. The design also doesn't look as expected.

We have the same issue. It seems to be only for pulse log format. Switching to text format will allow us to export, but it is hard to debug the logs.

@kean any update on this bug?


add callback to new step and update step

add callback options when for new step event and merge step event.
not let recorder to configure matcher's event emitter.

@netweng PTAL

LGTM


Object method can’t be named “get_”

I found this while looking at #6667:
object foo {
    shared void get_() {}
}

Ceylon backend error: method get_() is already defined in class foo_
Ceylon backend error: non-static method get_() cannot be referenced from a static context
CompilerBugException: Codegen Error

get_ is also the static method used to obtain the object instance. Unfortunately, that method is very much public, so we can’t just rename it without breaking BC.
Perhaps the better fix would be to disallow object members ending in _, just like we already do for toplevel declarations?
As always, generated code, @noanno’d.

There used to be a compiler error for names ending _. I don't know what happened to that, but it should prevent you writing get_()

It still exists, but only for toplevel declarations:

error: toplevel declaration name ending in _ not currently supported

It was changed from “identifiers ending in…” to its current form in e8ceb04eb2da5253cde21885acd4c08353b40b01, almost exactly three years ago. (Damn, if only I’d found this yesterday… :D )

This would indeed be a BC-breaking change. We could either

change com.redhat.ceylon.compiler.java.language.Getter (why one earth did we decide the name get_ was OK for this interface!) and generated code or
quote the method name get_ (when it appeared as a member of an object).

Not for 1.3.1 in any case.

Well, quoting get_ in an object wouldn’t break BC, would it? Because there can’t be any working code referring to such a method. (And the justification for the name is that it shouldn’t be too inconvenient to use from Java, isn’t it?)

No, I guess not, since there can be no methods called 'get_' at the moment. But there would be a lot of things to test: The various paths through the compiler, the metamodel. And this can hardly be a priority.

I definitely agree that this issue is not for 1.3.1. We have much bigger fish to fry.


rootfs: remove unused functions

These files seem confusing to me 😅
@dmcgowan
Signed-off-by: Akihiro Suda<EMAIL_ADDRESS>

Codecov Report

Merging #1348 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1348   +/-   ##
=======================================
  Coverage   35.56%   35.56%
=======================================
  Files          23       23
  Lines        2874     2874
=======================================
  Hits         1022     1022
  Misses       1627     1627
  Partials      225      225

Continue to review full report at Codecov.

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

LGTM
These were left over from creating an init layer inside containerd.

I kept these here so the client could use if it needed an init layer, we can resurrect IF/WHEN it is needed, thanks.
Post merge LGTM

We probably should have left these in...

But now you can make a "resurrect" PR!
On Thu, Aug 17, 2017, 4:42 PM Stephen Day<EMAIL_ADDRESS>wrote:

We probably should have left these in...
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/containerd/containerd/pull/1348#issuecomment-323222755,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APUifukS6zh6eIGUTZo5ZWtsqKV25egqks5sZM_LgaJpZM4O1Vh6
.

--
Sent from my phone.

@mlaventure I don't like wasting fairies and phoenix downs. :P

@ijc @Random-Liu @dmcgowan
Should we revert this and let the client to use it?
ijc [10:11 AM]
Next issue I'm hitting with the sock shop demo on cri-containerd is runc is failing when trying to create `/etc/hosts` in the rootfs as the target of the bind mount because the rootfs is r/o. It looks like Docker is adding an extra layer on top of the image where it adds those mount points in https://github.com/moby/moby/blob/master/daemon/initlayer/setup_unix.go#L19.
`docker.io/library/mongo:latest` is an example of an image which lacks an `etc/hosts` entirely, but in `docker run --read-only -it --rm docker.io/library/mongo:latest cat /proc/self/mountinfo | grep etc` you will see it. Will dig in more tomorrow, this might be an ugly one to fix :confused:

@ijc Can you confirm this is what you're looking for?

@AkihiroSuda / @stevvooe discussion of what is needed is happening on https://github.com/kubernetes-incubator/cri-containerd/issues/220 and to some extent https://github.com/containerd/containerd/pull/1477 although that's considering the more abstract need albeit inspired by my conundrum).


Update dependencies due to audit findings

The patch from lodash has not been published to npm, I bumped the version and also fixed another audit finding.
@gargol please publish 1.0.1 after accepting the PR.
Regards,
Christian

Thanks!


i use fromData after toData, and the draw is not completely the same .

I don't know why i get data and set data will make the draw different.(the line will become shorter)
I make a demo here https://jsfiddle.net/h80phxyr/7/
There is the pic compare.
https://i.stack.imgur.com/fLNmM.png
https://i.stack.imgur.com/bleJn.png
I use  v2.2.0 and chrome 58
Many thanks!

Most likely it's a bug - probably not all data points are stored (the ones at the end of each stroke) and thus when recreating image from these points, each line is a bit shorter.

@szimek thanks for reply. I will take some time try to fix the bug. By the way, signature pad is a wonderful JavaScript library.

@szimek
I think i found the question.
we should push the end point to this._data when _strokeEnd.
SignaturePad.prototype._strokeEnd = function (event) {
  var canDrawCurve = this.points.length > 2;
  var point = this.points[0];

  if (!canDrawCurve && point) {
    this._drawDot(point);
  }

  if (typeof this.onEnd === 'function') {
    this.onEnd(event);
  }
 // ************* new add ************
  this._data[this._data.length - 1].push({
    x: point.x,
    y: point.y,
    time: point.time,
    color: this.penColor
  });
 // ************* new add ************
};

I also met for this problem.
I'll try it later...

@szimek   It seems that , this bug is not fixed .

html dom:

js:
var signatureId = '#signature_container';
signaturePad = new SignaturePad($(signatureId)[0], {
backgroundColor: 'rgb(255,255,255)',
//penColor: 'green',
minWidth: 3,
maxWidth: 3,
});

I see this bug again .

@tempbing I don't - check out the jsfiddle (https://jsfiddle.net/h80phxyr/7/) posted by @c4cat. It works fine now.

Draw some curves(like letter ‘J’ ) (js code use  signaturePad.fromData() +  signaturePad.toData())
js code use  signaturePad.fromDataURL()  + signaturePad.toDataURL())

You can see the bug.
Others:
I also see anther problem . When change the setting , signaturePad.minWidth = 5;             signaturePad.maxWidth = 10;             signaturePad.penColor = "rgb(66, 133, 244)";
use  signaturePad.fromData() +  signaturePad.toData()  . The problem is distinct .

@szimek    A new Demo (https://jsfiddle.net/h80phxyr/10/)

Here's a fixed version: https://jsfiddle.net/szimek/h80phxyr/11/ You need to set canvas size in CSS and adjust its size in JS as well. The canvas size adjustment code is based on the code from the demo (https://github.com/szimek/signature_pad/blob/master/example/js/app.js#L11-L19).

Thanks very much for reply.
On this fixed version: (https://jsfiddle.net/szimek/h80phxyr/11/)
I see the problem again.
You can draw some curves (like six letters "jjJJjj") ,then click "undo" button six times .
On this online demo.: (https://jsfiddle.net/szimek/h80phxyr/11/)
I have a try ,maybe i don't  understand ...
The picture compare.
()

@tempbing Nah, you're right. It's much less noticeable now, but something is still off. I'll check it out.

@szimek , am displaying image on signature-pad...when i draw only  on signature-pad and do undo() operation it  perform correctly..but when am displaying image on signature-pad and  then perform undo then it clear entire image first and then other data..i want to undo only data on image..not an image
my takephoto function()
public  takePicture(sourceType, DestinationType) {
var options = {
quality: 100,
  //sourceType: sourceType,
  // destinationType: DestinationType,
  destinationType: this.camera.DestinationType.DATA_URL,
  saveToPhotoAlbum: true,
  correctOrientation: true,
  //mediaType: 2,
  encodingType: this.camera.EncodingType.JPEG,
 mediaType: this.camera.MediaType.PICTURE,
 // allowEdit : true,
  //height:100,
  //width:200,

  targetWidth :1000,
  targetHeight:1000,
  // width: window.screen.width,
  // height: window.screen.height,

};

this.camera.getPicture(options).then((imagePath) => {
  if (this.platform.is('android') && sourceType === this.camera.PictureSourceType.PHOTOLIBRARY) {
    this.filePath.resolveNativePath(imagePath)
      .then(filePath => {
        this.lastImage = this.createFileName();
        this.tempPath = "data:image/jpeg;base64," + imagePath;
        this.selectedImagePath = imagePath;

       //this.signaturePad.fromDataURL(this.tempPath);
      //this.tempPath = this.signaturePad.toDataURL(this.tempPath);
      });

  } else {

    this.lastImage = this.createFileName();
   this.tempPath = "data:image/jpeg;base64," + imagePath;

 this.selectedImagePath = imagePath;
 this.signaturePad.fromDataURL(this.tempPath);
  // this.selectedImagePath
    this.tempPath = this.signaturePad.toDataURL(this.tempPath);
    // let canvas = document.querySelector('canvas');

    // this.signaturePad.set('canvasWidth', canvas.this.tempath);
    // this.signaturePad.set('canvasHeight', canvas.this.tempath);
    // let tempPathheight =500;
    // this.signaturePad.set('temPath', tempPathheight);
    //this.tempPath.Height = CanvasHeight;
  }
}, (err) => {
 // this.presentToast(err);
 console.log(err);
});

}
private createFileName() {
var d = new Date(),
n = d.getTime(),
newFileName = n + ".jpg";
return newFileName;
}
and my perform()-undo function
perform()
{
var data = this.signaturePad.toData();
if (data) {
      data.pop(); // remove the last dot or line
     this.signaturePad.fromData(data);
  }
   }

please help me to correct my perform() function

@amolumesh12 I'm not sure if there's an easy way to do it at the moment, because SignaturePad#fromData clears the canvas before it redraws everything. If you draw your image after calling this method, it would overwrite the signature.
Currently, you could modify the library to remove this.clear() call from SignaturePad#fromData method. I could change this method to not call SignaturePad#clear, but that would be a breaking change and would require releasing a new major version.

can you please make changes in my code for undo operation because..sorry , but  am not getting what you trying to say ??

@szimek , am displaying image on signature-pad...when i draw only on signature-pad and do undo() operation it perform correctly..but when am displaying image on signature-pad and then perform undo then it clear entire image first and then other data..i want to undo only data on image..not an image

There is one working solution for what you are desiring.

Copy the data Object (Obtained from "toData()") to a local variable
Pop from the local object
Use fromData(localVariable)
You need to create another hidden canvas
Draw the background Image
Draw the actual canvas
Replace the actual canvas with the state of the hidden canvas
For future "undos" modify the data object that you are updating and repeat (2-7).

@amolumesh12 I'm not sure if there's an easy way to do it at the moment, because SignaturePad#fromData clears the canvas before it redraws everything. If you draw your image after calling this method, it would overwrite the signature.
Currently, you could modify the library to remove this.clear() call from SignaturePad#fromData method. I could change this method to not call SignaturePad#clear, but that would be a breaking change and would require releasing a new major version.

How about we add an optional parameter to fromData() like "doNotClear?:Boolean". It wont break the existing code and will be more flexible.


Contributors can't download PDF receipt

Describe the bug
My contributors are not able to download the PDF receipt from the mail sent to them
To Reproduce
I haven't tried myself but one of my contributors forwarded me the mail sent to them thanking them for their donation. And indeed if I click on the link to download a PDF receipt of the donation, I am greeted with
"Internal Server Error: Not authorized to access /material-theme-jetbrains/transactions/xxxxxxxxxx/invoice.pdf. Please provide an authorization header or an app_key."
Expected behavior
Be able to download the receipt
Desktop (please complete the following information):

OS: Mac OS
Browser Chrome
Version 49

Hi @mallowigi, thank you for reporting this issue.
This endpoint previously wasn't requesting authentication. It was protected by the fact that transaction's uuid are private and non-predictable.
We've however enforced the security of this endpoint by requesting authentication, which was a requirement - among others - for the service to generate incognito invoices properly (because we need to check that users can access these private info, #2743).
My suggestion would be to link to the user's transactions page instead, where users can download receipts directly.
@mallowigi if your contributors need their invoice asap, a workaround is for them to go to https://opencollective.com/USERNAME/transactions (USERNAME must be replaced). They'll be able to download the receipts from there.

I got word from my customers and it appears e problem has been resolved

Well actually the underlying issue is real, I was able to reproduce :slightly_smiling_face:


[Quest] Cursor skipping back when typing in the username and password

IMPORTANT: Where possible all PRs must be linked to a Github issue
Fixes #1870
Checklist

[ ] I have written Unit tests for any new feature(s) and edge cases for bug fixes
[ ] I have added any strings visible on UI components to the strings.xml file
[ ] I have updated the  CHANGELOG.md file for any notable changes to the codebase
[ ] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the project's style guide
[ ] I have built and run the fhircore app to verify my change fixes the issue and/or does not break the app

Is it possible to write tests for this?

Is it possible to write tests for this?

both methods of tests are already written and working fine.


Fix pixels when launching Duck Player from serp

Task/Issue URL: https://app.asana.com/0/72649045549333/1208529859806601/f
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

#5128  👈
develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @CrisBarreiro and the rest of your teammates on  Graphite


Python 3.7 needed

Hi,
Elegoo released the Neptune 4 Printers which run on Klipper, but use an old Python Version (3.5).
Your nice Tool runs requests at least 3.7 - Updating the printer is not an option as no one knows if it still will run afterwards.
Is there any chance the reduce the requirements in the tool ?
thx

no one said spoolman needs to run on the printer itself.
PYthon 3.5 is EOL since 09-2020 - even Python 3.7 is EOL since 06.2023.

Yup, what @rufinus said. There is no way I'm downgrading the Python version to 3.5, it's too old. You have to host Spoolman on some other machine.

Sure I know. On my last printer I mwas using octopi on a raspi 3. On the ender i am not able as I don't get the MCU address. Ls is not working. So no external device. The only possible is to install on the printer itself. In addition elegoo does not support any update of python. So I am trapped in a loop.

A year later Python 3.9 is required:

Current version of Python (3.8.10) is too old for Spoolman.
Which features require this version and do not work with an older version?

@Donkie Why are you writing about downgrading? The only point is not to exclude old systems!

Newer python versions brings many features that improve the library compatibility, performance, and development experience.
You have to remember that this project is something I do in my free time, and it's always a trade off between maximizing compatibility and efficiency. Using older Python versions could mean I can't use all the libraries I today depend on for example, which means I would need to code them myself. Older Python versions also has less of the nice syntax features that newer Python has, e.g. type hinting.


Wrong labels in plot in notebook plot_main-tutorial-regression.ipynb

In the notebook plot_main-tutorial-regression.ipynb, the "True confidence intervals" and "Prediction intervals" are not correctly labeled in the plots legend.

Hello, do you mean plot_main-tutorial-regression.py? If I understand correctly, we need to correct these labels right?
    ax.fill_between(X_test, y_pred_low, y_pred_up, alpha=0.3)
    ax.scatter(X_train, y_train, color="red", alpha=0.3, label="Training data")
    ax.plot(X_test, y_test, color="gray", label="True confidence intervals")
    ax.plot(X_test, y_test - y_sigma, color="gray", ls="--")
    ax.plot(X_test, y_test + y_sigma, color="gray", ls="--")
    ax.plot(
        X_test, y_pred, color="blue", alpha=0.5, label="Prediction intervals"
    )

@sulphatet exactly :)


Error when building: undefined: app.Componer

When trying to build the hello world example from https://github.com/murlokswarm/app#hello-world the build fails.
OS: MacOS High Sierra 10.13.3
$ goapp mac build
github.com/murlokswarm/mac
# github.com/murlokswarm/mac
picker.m:32:17: warning: 'NSFileHandlingPanelOKButton' is deprecated: first deprecated in macOS 10.13 [-Wdeprecated-declarations]
/System/Library/Frameworks/AppKit.framework/Headers/NSSavePanel.h:21:5: note: 'NSFileHandlingPanelOKButton' has been explicitly marked deprecated here
# github.com/murlokswarm/mac
../../murlokswarm/mac/menu.go:24: undefined: app.Componer
exit status 2

This repo is not used anymore. The mac driver has been moved into the app package.
Sent from my iPhone
On Jul 5, 2018, at 12:02 AM, Mihkel <notifications<EMAIL_ADDRESS>wrote:
When trying to build the hello world example from https://github.com/murlokswarm/app#hello-world the build fails.
OS: MacOS High Sierra 10.13.3
$ goapp mac build
github.com/murlokswarm/machttp://github.com/murlokswarm/mac
github.com/murlokswarm/machttp://github.com/murlokswarm/mac
picker.m:32:17: warning: 'NSFileHandlingPanelOKButton' is deprecated: first deprecated in macOS 10.13 [-Wdeprecated-declarations]
/System/Library/Frameworks/AppKit.framework/Headers/NSSavePanel.h:21:5: note: 'NSFileHandlingPanelOKButton' has been explicitly marked deprecated here
github.com/murlokswarm/machttp://github.com/murlokswarm/mac
../../murlokswarm/mac/menu.go:24: undefined: app.Componer
exit status 2
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/murlokswarm/mac/issues/25, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACkWe0Ag1Rn21aiY8XnSm-rbLxFC532Zks5uDbn_gaJpZM4VDWH0.


[JBTM-3588]

https://issues.redhat.com/browse/JBTM-3588
This PR is needed by PR https://github.com/jbosstm/narayana/pull/2065
This PR changes are related to:
-removal the use of old narayana "-jakarta" transformed artifacts in order to use the Jakarta native ones.
-migration of submodules (rts, iiop-openjdk...) to Jakarta
-removal of txframework
... (see commits' messages for more info)

Note that this PR is a temporary placeholder pending the merge of https://github.com/wildfly/wildfly/pull/16275

Since wildfly merged @jmfinelli PR (https://github.com/wildfly/wildfly/pull/16310) I therefore close this PR and I will rebase 5_BRANCH with wildfly main branch


replaces SASS with Sass

Sass is not intended to be all caps. It's a bacronym, not and acronym 😄

Right you are! Reference:
http://sass-lang.com
Thanks for the fix.


Move cans to match rules

https://github.com/sourcebots/smallpeice-rules/commit/a96a8f697061d9c122935bfa2399c43b97702649

Rebase to fix CI


feat(highlights): nvim-dap-ui

I basically just copied from astrotheme's configuration
Oy, just noticed I autoformatted the README. If it's a problem, I'll revisit.

I'll take a look at this once v1 is out, if that's fine. I have some contribution guidelines ready and I would like this PR to follow them, if it is to be merged. I will publish those soon.

Sorry for the delay. Here are the contribution guidelines.
Could you please make sure that this PR follows the rules? Also, a screenshot would be appreciated, as the rules are still quite subjective.
Otherwise, based on the fact that you are saying that you basically just copied the highlights from astrotheme, it could be better to move these highlights to a new discussion, or, if you really want the plugin to be added properly, to a new issue.

Oh and yeah, it would be better to not format the README, unless it is done with a different PR, but I don't really see a need for it.


set the TARGET envar for the stdsimd integration test

The stdsimd crate fails to compile with the following. Setting the TARGET envar fixes the problem.
error: custom attribute panicked
   --> crates/core_arch/src/x86/fxsr.rs:102:5
    |
102 |     #[simd_test(enable = "fxsr")]
    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |
    = help: message: TARGET environment variable should be set for rustc: NotPresent

the crate futures-rs fails with https://github.com/rust-lang-nursery/futures-rs/issues/1453

Thanks!


Apply texture transform for main

This seems to be related to https://github.com/CesiumGS/cesium-native/issues/768 , but does not fix it, right?
(I just stumbled over this, and may have to read the changes here more thoroughly...)

Right, it doesn't fix it by itself. But it should fix it (I haven't tested or reviewd it yet) when combined with these PRs:

https://github.com/CesiumGS/cesium-unreal/pull/1315
https://github.com/CesiumGS/cesium-unity/pull/385

Thanks @joseph-kaile!


XAML Previewer failure issue on version 11.0.0 rc1.1

Describe the bug
live previewer failed when I modified XAML.
This seems to only happen in the latest version.
Screenshots

The first image shows the expected results for the stable version and preview 7, which is correct.
The second image shows the results of the test at 11.0.0 rc1.1
This problem is bothering me.
Desktop:

OS: Windows
Version 11.0.0 rc1.1
IDE Visual Studio2022

same issue , see https://github.com/AvaloniaUI/AvaloniaVS/issues/334#issue-1748933035

Have you tried with https://github.com/AvaloniaUI/Avalonia/pull/11755?

having same issue

Duplicate of https://github.com/AvaloniaUI/AvaloniaVS/issues/334#issue-1748933035


ci: code coverage

:tada: This pull request is included in version<EMAIL_ADDRESS>:tada:
The release is available on GitHub release

:tada: This pull request is included in version<EMAIL_ADDRESS>:tada:
The release is available on GitHub release


CS locale format is wrong

Expected behaviour
CS locale format should be 'dd.mm.yyyy'
Actual behaviour
CS locale format is 'dd.m.yyyy', making it difficult to work with moment.js for example.
Datepicker version used
1.7.1

Please, if you can, open a PR with the necessary fixes. Thanks!