Allow multiple host feilds in the HttpScaledObject

Hi, we have a deployment that is exposed via multiple hostname in the ingress; As a workaround, I tried creating multiple HttpScaledObject, and in the targetRef added the same deployment and service with the different host but seem the http-scaller component crashes trying to handle with fatal error: concurrent map writes
Use-Case
Ability to handle multiple host to scale the same deployment
Specification
The HttpScaledObject should accept a list of strings in the host field and the route should be added for all those hosts to the service; i.e. request to any one of those hosts would scale up the service.

We have a similar requirement for this, currently using list of httpscaledobject resource. Will raise a PR for this.

That would be awesome, thank you @someshkoli!

We have a similar requirement for this, currently using list of httpscaledobject resource. Will raise a PR for this.

Do you use different deployments? I wonder if the HTTPScaledObjects would conflict with each other?

also have a use case for this (I think it is the same?) - we have multiple ingresses pointing to the same deployment
demo.domain1.com -> mydemo deployment
demo.domain2.com > mydemo deployment
We do this so we can check the domain and display different branding based on that.
We want to scale the single deployment up no matter which of the URLs you hit


Use loose generics as much as possible

Before, you need to cast generics in some cases:
List<EmiStack> all;
@Override
public List<EmiIngredient> getInputs() {
    return (List<EmiIngredient>) (List<? extends EmiIngredient>) all;
}
@Override
public List<EmiStack> getOutputs() {
    return all;
}

Now you can just return it directly:
List<EmiStack> all;
@Override
public List<? extends EmiIngredient> getInputs() {
    return all;
}
@Override
public List<? extends EmiStack> getOutputs() {
    return all;
}

I appreciate the thought here but unfortunately this is a breaking API change, so it cannot be merged. In addition, the PR contains a handful of unrelated adjustments and changes, and some notable style violations like usage of var which is not something I use in my codebases. I don't think this PR can be merged even with changes, however, because of the status as a serious out of band API breakage.
As a justification for why the API is like it is: it's more convenient for callers, and for implementations, you're expected to just be constructing a list and storing it as a field, the use case of duplicate inputs and outputs is relatively niche, and the cast isn't that bad or common.
Sorry to close this immediately but all breaking changes need to be considered carefully and managed during an update cycle with concern to not cause undue churn for API consumers.

Oh no, I didn't realize it was a breaking update. Alas, I should have reacted when I encountered a large number of variable declaration compilation errors.


Adds Rewrite rule set for Header CRUD

Adds the structure of rewriteRuleSets in the applicationGatewayProperties.
Adds recursively the sub structures in the rewriteRuleSet.
Adds the reference to rewriteRuleSet in the requestRoutingRule for both Basic rule and Path based rule.
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-sdk-for-java

Can one of the admins verify this patch?

Automation for azure-sdk-for-js

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-node

Automation for azure-sdk-for-python

Automation for azure-sdk-for-go

do we need to create any examples?

do we need to create any examples?
@MikhailTryakhov , I have added the examples.

Checks have passed but it is not merged automatically. Should we merge it manually?


[MIPS64] Google.Protobuf.Tools cannot determine host OS and CPU

Hi,

What version of gRPC and what language are you using?

v1.28.0 and master
C#

What operating system (Linux, Windows,...) and version?
Linux 3.10.84-20.fc21.loongson.3.mips64el
What runtime / compiler are you using (e.g. python version or version of gcc)
gcc 4.9.4
What did you do?

dotnet new grpc
dotnet build

dotnet SDK for MIPS64:  https://github.com/gsvm/loongson-dotnet/releases
What did you expect to see?
Support MIPS64:  https://github.com/grpc/grpc/pull/24068
What did you see instead?
/home/loongson/.nuget/packages/grpc.tools/2.27.0/build/_protobuf/Google.Protobuf.Tools.targets(84,5): error : Google.Protobuf.Tools cannot determine host OS and CPU. [/home/loongson/zhaixiang/HelloGRPC/HelloGRPC.csproj]
/home/loongson/.nuget/packages/grpc.tools/2.27.0/build/_protobuf/Google.Protobuf.Tools.targets(84,5): error : Use environment variables PROTOBUF_TOOLS_OS={linux|macosx|windows} and PROTOBUF_TOOLS_CPU={x86|x64} to try the closest match to your system. [/home/loongson/zhaixiang/HelloGRPC/HelloGRPC.csproj]
/home/loongson/.nuget/packages/grpc.tools/2.27.0/build/_protobuf/Google.Protobuf.Tools.targets(84,5): error : You may also set PROTOBUF_PROTOC to specify full path to the host-provided compiler (v3.5+ is required). [/home/loongson/zhaixiang/HelloGRPC/HelloGRPC.csproj]
    0 Warning(s)
    1 Error(s)

Thanks,
Leslie Zhai

We don't support MIPS64 as a platform, sorry. There is also no plan to add such support because there's little demand, it would require a lot of work and we also don't have a way to test on MIPS64


Results giving weird look after using your shader.

Results giving weird look after using your shader.
I have followed the instructions given in readme file, still giving weird looks.
Please see the below screenshot, for better understanding.

Kindly help me solve this issue.
Appreciate if anyone faced and help me for this issue.

turn on _ProjectionAngleDiscardEnable

Thank you for the response,
I've turned on _ProjectionAngleDiscardEnable, below is the result after setting threshold value to 0.02, but the bottom is not projecting right.

My expectation result should be something below.

Is there any other settings do I need to apply? Kindly help me solve this issue.

@ColinLeung-NiloCat

Thank you for the response,
I've turned on _ProjectionAngleDiscardEnable, below is the result after setting threshold value to 0.02, but the bottom is not projecting right.

My expectation result should be something below.

Is there any other settings do I need to apply? Kindly help me solve this issue.

rotate the decal gameobject a bit

@ColinLeung-NiloCat
Yes, I have tried X rotation about 20 units, then it started showing better results.

I am implementing FPS shooter game.
If I shoot straight wall or ground alone it works well, but if I shoot corner of both straight wall or ground, then how can I detect that bullet is hitting at corner? in other words, when should I rotate if the bullet is hitting the corner? Is there any workaround for this? Kindly help me to solve this issue.
Thanks,
Avinash.


Update Composer dependencies (2021-11-24-21-13)

Visual regression test passed!
View the visual regression test report


ROX-19862: Add manual entry for CVE-2023-32697

CVE-2023-32697 was not being detected for sqlite-jdbc-<IP_ADDRESS>.jar due to an inaccurate CPE URI on the NVD entry.
To fix the match a manual entry was created with cpe:2.3:a:xerial:sqlite-jdbc:*:*:*:*:*:*:*:* added.
You'll notice some information appears missing when comparing the updater output to the NVD page and API, such as  references and CWE.  This appears to be because the updater omits data that was not provided by NVD, such as other CNA's, in this case GitHub.  Consider this while reviewing the PR - if the additional data is used by Scanner / ACS it may be worthwhile adding it, unless there is a reason not to (such as licensing).

JSON output from Scanner updater
Output from: ./bin/updater generate-dump...
  {
    "cve": {
      "affects": null,
      "CVE_data_meta": {
        "ASSIGNER": "",
        "ID": "CVE-2023-32697"
      },
      "data_format": "",
      "data_type": "",
      "data_version": "",
      "description": {
        "description_data": [
          {
            "lang": "en",
            "value": "SQLite JDBC is a library for accessing and creating SQLite database files in Java. Sqlite-jdbc addresses a remote code execution vulnerability via JDBC URL. This issue impacting versions <IP_ADDRESS> through <IP_ADDRESS> and has been fixed in version <IP_ADDRESS>.\n"
          }
        ]
      },
      "problemtype": null,
      "references": null
    },
    "configurations": {
      "CVE_data_version": "",
      "nodes": [
        {
          "cpe_match": [
            {
              "cpe23Uri": "cpe:2.3:a:sqlite_jdbc_project:sqlite_jdbc:*:*:*:*:*:*:*:*",
              "versionEndExcluding": "<IP_ADDRESS>",
              "versionStartIncluding": "<IP_ADDRESS>",
              "vulnerable": true
            }
          ],
          "operator": "OR"
        }
      ]
    },
    "impact": {
      "baseMetricV3": {
        "cvssV3": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "HIGH",
          "baseScore": 9.8,
          "baseSeverity": "CRITICAL",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
          "version": "3.1"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 5.9
      }
    },
    "lastModifiedDate": "2023-05-31T18:10Z",
    "publishedDate": "2023-05-23T23:15Z"
  },

JSON output from NVD API
Output from: curl -sS -H "apiKey: $NVD_API_KEY" https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2023-32697 | jq
{
  "resultsPerPage": 1,
  "startIndex": 0,
  "totalResults": 1,
  "format": "NVD_CVE",
  "version": "2.0",
  "timestamp": "2024-04-04T16:46:42.043",
  "vulnerabilities": [
    {
      "cve": {
        "id": "CVE-2023-32697",
        "sourceIdentifier"<EMAIL_ADDRESS>        "published": "2023-05-23T23:15:09.337",
        "lastModified": "2023-05-31T18:10:04.943",
        "vulnStatus": "Analyzed",
        "descriptions": [
          {
            "lang": "en",
            "value": "SQLite JDBC is a library for accessing and creating SQLite database files in Java. Sqlite-jdbc addresses a remote code execution vulnerability via JDBC URL. This issue impacting versions <IP_ADDRESS> through <IP_ADDRESS> and has been fixed in version <IP_ADDRESS>.\n"
          }
        ],
        "metrics": {
          "cvssMetricV31": [
            {
              "source"<EMAIL_ADDRESS>              "type": "Primary",
              "cvssData": {
                "version": "3.1",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
                "attackVector": "NETWORK",
                "attackComplexity": "LOW",
                "privilegesRequired": "NONE",
                "userInteraction": "NONE",
                "scope": "UNCHANGED",
                "confidentialityImpact": "HIGH",
                "integrityImpact": "HIGH",
                "availabilityImpact": "HIGH",
                "baseScore": 9.8,
                "baseSeverity": "CRITICAL"
              },
              "exploitabilityScore": 3.9,
              "impactScore": 5.9
            },
            {
              "source"<EMAIL_ADDRESS>              "type": "Secondary",
              "cvssData": {
                "version": "3.1",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
                "attackVector": "NETWORK",
                "attackComplexity": "LOW",
                "privilegesRequired": "LOW",
                "userInteraction": "NONE",
                "scope": "UNCHANGED",
                "confidentialityImpact": "HIGH",
                "integrityImpact": "HIGH",
                "availabilityImpact": "HIGH",
                "baseScore": 8.8,
                "baseSeverity": "HIGH"
              },
              "exploitabilityScore": 2.8,
              "impactScore": 5.9
            }
          ]
        },
        "weaknesses": [
          {
            "source"<EMAIL_ADDRESS>            "type": "Primary",
            "description": [
              {
                "lang": "en",
                "value": "CWE-94"
              }
            ]
          }
        ],
        "configurations": [
          {
            "nodes": [
              {
                "operator": "OR",
                "negate": false,
                "cpeMatch": [
                  {
                    "vulnerable": true,
                    "criteria": "cpe:2.3:a:sqlite_jdbc_project:sqlite_jdbc:*:*:*:*:*:*:*:*",
                    "versionStartIncluding": "<IP_ADDRESS>",
                    "versionEndExcluding": "<IP_ADDRESS>",
                    "matchCriteriaId": "47BF8145-F503-4906-B97C-F58153E21309"
                  }
                ]
              }
            ]
          }
        ],
        "references": [
          {
            "url": "https://github.com/xerial/sqlite-jdbc/releases/tag/<IP_ADDRESS>",
            "source"<EMAIL_ADDRESS>            "tags": [
              "Release Notes"
            ]
          },
          {
            "url": "https://github.com/xerial/sqlite-jdbc/security/advisories/GHSA-6phf-6h5g-97j2",
            "source"<EMAIL_ADDRESS>            "tags": [
              "Vendor Advisory"
            ]
          }
        ]
      }
    }
  ]
}

Testing
Created image quay.io/rhacs-eng/qa:sqlite-jdbc-CVE-2023-32697 and added E2E test:
❯ go test -tags e2e -count=1 -timeout=20m -v -run='TestImageSanity/^quay.io/rhacs-eng/qa:sqlite*' ./e2etests/...
=== RUN   TestImageSanity
=== RUN   TestImageSanity/quay.io/rhacs-eng/qa:sqlite-jdbc-CVE-2023-32697
=== RUN   TestImageSanity/quay.io/rhacs-eng/qa:sqlite-jdbc-CVE-2023-32697/sqlite-jdbc/<IP_ADDRESS>
--- PASS: TestImageSanity (4.60s)
    --- PASS: TestImageSanity/quay.io/rhacs-eng/qa:sqlite-jdbc-CVE-2023-32697 (4.60s)
        --- PASS: TestImageSanity/quay.io/rhacs-eng/qa:sqlite-jdbc-CVE-2023-32697/sqlite-jdbc/<IP_ADDRESS> (0.00s)

Also verified via the local dev utility
Before adding manual entry:
$ go run ./localdev/
INFO[0000] Loading NVD definitions into cache
INFO[0000] Loading definitions directory                 dir=/Users/dcaravel/dev/stackrox/scanner/image/scanner/dump/nvd
INFO[0017] Total vulns in "/Users/dcaravel/dev/stackrox/scanner/image/scanner/dump/nvd": 168634
INFO[0018] Done loading NVD definitions into cache
dignore/jdbc.tar
&{{0} rhel:8 rpm}
RHELv2 Components (0): rhel:8 - [ ][ ]
Removed components: []
182ebcf44f9194d116dce494b9036b87fe6b1496bed826a3c8e0eaa4158b93c6/layer.tar (0 components)
RHELv2 Components (0): rhel:8 - [ ][ ]
Removed components: []
0f25cb3bd57225cecc7d0d6091bb4629edec37720562a97477759f8da5712d8b/layer.tar (1 components)

0.0001 seconds took Checking for vulns

After adding manual entry and re-running updater:
$ go run ./localdev/
INFO[0000] Loading NVD definitions into cache
INFO[0000] Loading definitions directory                 dir=/Users/dcaravel/dev/stackrox/scanner/image/scanner/dump/nvd
INFO[0017] Total vulns in "/Users/dcaravel/dev/stackrox/scanner/image/scanner/dump/nvd": 168634
INFO[0018] Done loading NVD definitions into cache
dignore/jdbc.tar
&{{0} rhel:8 rpm}
RHELv2 Components (0): rhel:8 - [ ][ ]
Removed components: []
182ebcf44f9194d116dce494b9036b87fe6b1496bed826a3c8e0eaa4158b93c6/layer.tar (0 components)
RHELv2 Components (0): rhel:8 - [ ][ ]
Removed components: []
0f25cb3bd57225cecc7d0d6091bb4629edec37720562a97477759f8da5712d8b/layer.tar (1 components)
	 sqlite-jdbc <IP_ADDRESS> JavaSourceType sqlite-jdbc-<IP_ADDRESS>.jar (1 vulns)
		 CVE-2023-32697 <IP_ADDRESS>

0.0001 seconds took Checking for vulns

@dcaravel can you add your sample image to quay.io/rhacs-eng/qa:<whatever> and then add that as a testcase in testcases_test.go? From there, you can add the generate-dumps-on-pr to ensure everything is good to go

@dcaravel can you add your sample image to quay.io/rhacs-eng/qa:<whatever> and then add that as a testcase in testcases_test.go? From there, you can add the generate-dumps-on-pr to ensure everything is good to go

Excellent idea, will do.

Hrm, failure confuses me, works outside of CI...
❯ go test -tags e2e -count=1 -timeout=20m -v -run='TestImageSanity/^quay.io/rhacs-eng/qa:sqlite*' ./e2etests/...
=== RUN   TestImageSanity
=== RUN   TestImageSanity/quay.io/rhacs-eng/qa:sqlite-jdbc-CVE-2023-32697
=== RUN   TestImageSanity/quay.io/rhacs-eng/qa:sqlite-jdbc-CVE-2023-32697/sqlite-jdbc/<IP_ADDRESS>
--- PASS: TestImageSanity (4.60s)
    --- PASS: TestImageSanity/quay.io/rhacs-eng/qa:sqlite-jdbc-CVE-2023-32697 (4.60s)
        --- PASS: TestImageSanity/quay.io/rhacs-eng/qa:sqlite-jdbc-CVE-2023-32697/sqlite-jdbc/<IP_ADDRESS> (0.00s)

/retest

Manual entry not making it into the image:
docker save quay.io/rhacs-eng/scanner:2.33.x-29-g2dfc5cc703 > img.tar
tar -xvf img.tar
# find layer with `dive`
cd 8707d58bc14c1fa3dd569c241faf81fbfc0b2d5490af5928450200c0bf1a0dea
tar -xvf layer.tar
cd nvd_definitions

$ CVE="CVE-2023-32697"
$ grep -il "CVE-2023-32697" *
10.json

$ cat 10.json | jq ".CVE_Items[] | select( .cve.CVE_data_meta.ID == \"$CVE\")"

{
  "cve": {
    "affects": null,
    "CVE_data_meta": {
      "ASSIGNER": "",
      "ID": "CVE-2023-32697"
    },
    "data_format": "",
    "data_type": "",
    "data_version": "",
    "description": {
      "description_data": [
        {
          "lang": "en",
          "value": "SQLite JDBC is a library for accessing and creating SQLite database files in Java. Sqlite-jdbc addresses a remote code execution vulnerability via JDBC URL. This issue impacting versions <IP_ADDRESS> through <IP_ADDRESS> and has been fixed in version <IP_ADDRESS>.\n"
        }
      ]
    },
    "problemtype": null,
    "references": null
  },
  "configurations": {
    "CVE_data_version": "",
    "nodes": [
      {
        "cpe_match": [
          {
            "cpe23Uri": "cpe:2.3:a:sqlite_jdbc_project:sqlite_jdbc:*:*:*:*:*:*:*:*",
            "versionEndExcluding": "<IP_ADDRESS>",
            "versionStartIncluding": "<IP_ADDRESS>",
            "vulnerable": true
          }
        ],
        "operator": "OR"
      }
    ]
  },
  "impact": {
    "baseMetricV3": {
      "cvssV3": {
        "attackComplexity": "LOW",
        "attackVector": "NETWORK",
        "availabilityImpact": "HIGH",
        "baseScore": 9.8,
        "baseSeverity": "CRITICAL",
        "confidentialityImpact": "HIGH",
        "integrityImpact": "HIGH",
        "privilegesRequired": "NONE",
        "scope": "UNCHANGED",
        "userInteraction": "NONE",
        "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
        "version": "3.1"
      },
      "exploitabilityScore": 3.9,
      "impactScore": 5.9
    }
  },
  "lastModifiedDate": "2023-05-31T18:10Z",
  "publishedDate": "2023-05-23T23:15Z"
}

Looks like made it into the genesis dump (https://github.com/stackrox/scanner/actions/runs/8575012414/artifacts/1389590520)
$ grep -il "CVE-2023-32697" *
0.json
1.json
10.json
11.json
2.json
3.json
4.json
5.json
6.json
7.json
8.json
9.json

$ cat 10.json | jq ".CVE_Items[] | select( .cve.CVE_data_meta.ID == \"$CVE\")" | jq '.configurations.nodes'

[
  {
    "cpe_match": [
      {
        "cpe23Uri": "cpe:2.3:a:sqlite_jdbc_project:sqlite_jdbc:*:*:*:*:*:*:*:*",
        "versionEndExcluding": "<IP_ADDRESS>",
        "versionStartIncluding": "<IP_ADDRESS>",
        "vulnerable": true
      },
      {
        "cpe23Uri": "cpe:2.3:a:xerial:sqlite-jdbc:*:*:*:*:*:*:*:*",
        "versionEndExcluding": "<IP_ADDRESS>",
        "versionStartIncluding": "<IP_ADDRESS>",
        "vulnerable": true
      }
    ],
    "operator": "OR"
  }
]

/retest

/retest


Use vagrant

Installed Vrtual box and vagrant.
Successfully started server and created contribution.
It was working fine.


Added debug printer to transmit debug messages over UART for debugging

Added a debug printer to debug over UART.  Still have to fix an issue with format strings. For now only  unformatted or preformatted strings work.

All this looks very C-esque, did we end up deciding on not using cpp?

How does the code look c-esque lol. because it's in a .c file? I could change that. or because it's not in a class? Not everything needs to be oop. you don't need to create a class for something with no data fields and just one function to interact with.

well you pretty much answered your question, if higher level statemachine is in cpp, then you can just generate a .cpp STM project, else just make everything C. Although it doesn't really matter, just consistency for consistency's sake

I renamed the file to .cpp


Not all races show up in selection

Not all the races I have available, show up in the list. This happens both in the latest versions of v11 and v10.
See picture:

Hi, the video was helpful and when I remove the requirements, it indeed fixes it, but I did doublecheck the list and Air Genacy(Legacy) had just Genasi in there, which didn't work. To make it even weirder: if I add genasi to both, they just don't appear at all.
All the races I'm using are gotten through DDB importer, I have gone through a lot of the races and all of them have the requirement "racial feature" as feature type, which is something your video warns against doing.

In your images, you would need to have a race called "Genasi" for the Legacy to show up.  The reason the AG show up is because they do not have a required race.
I too imported races from DDB into my world.  There is a lot you have to fix if you want things to look clean.  DDBI will copy the same info as a core race, meaning if you have an Elf, and then have the High Elf look to Elf as a requirement, your High Elf in the builder will show the information from Elf, and for High Elf.  What I did with my races, was to keep the things that is shared between every subrace in the core "Elf", then I trimmed "High Elf" of any duplicate data like Keen Senses.  This way when I look at my High Elf, it does not show Keep Senses twice.  I also removed the feature.  There is a lot of work involved with what I did, but in the end, it looks cleaner in the builder.


Fixed UploadedFile::moveTo() so it actually removes the original file when used in CLI context, and doesn't leave orphaned files

Signed-off-by: katsuren<EMAIL_ADDRESS>UploadedFile::moveTo doesn't work in CLI. Original file leave it as is.

Q
A

Documentation
no

Bugfix
yes

BC Break
no

New Feature
no

RFC
no

QA
no

Description
Calling UploadedFile::moveTo in CLI, it just copies the file to the targetPath.
In addition to this, the stream grabs the original file, so it cannot delete the file, and I cannot access the stream so I couldn't release the file pointer.
In a test for uploading file, I want to remove the uploaded file to keep clean the test folder.

Also to be asked here: do we merge to 2.11.x (bugfix), or is it OK to merge to 2.12.x (feature)? Would probably be better to release a bugfix.

@k2rn Please create an issue report to report the problem. Thanks in advance! 👍🏻

@froschdesign
https://github.com/laminas/laminas-diactoros/issues/108
I created the issue and close it. Thank you!

I agree that this PR should be considered at the very least as a minor breaking change. It broke quite a few of my unit tests. At least it was easy to notice the breakage. But now I need to use what feels like a dirty workaround, something similar to:
 <?php

 use Laminas\Diactoros\Stream;
 use Laminas\Diactoros\UploadedFile;

- new UploadedFile('my-file-for-unit-test', 999, UPLOAD_ERR_OK),
+ new UploadedFile(new Stream('my-file-for-unit-test'), 999, UPLOAD_ERR_OK),

Well, the fact that the file wasn't moved is an actual bug, and yes, it breaks compat for some tests, but unlikely for prod code.
This is an XKCD 1172:


TypeError: Reflect.get called on non-object on Cloudflare

Confirm this is a Node library issue and not an underlying OpenAI API issue

[X] This is an issue with the Node library

Describe the bug
Hi I am using Next js and deploying it on cloudflare. I am making sure everything is running on edge runtime. When I run my project locally, everything works fine.
However, on my deployed project, when I try to make a call to my api endpoint. I get an error of
TypeError: Reflect.get called on non-object in the logs on cloudflare.
To Reproduce

Create a simple next js project with openai api call.
Deploy it on Cloudflare.
You will not be able to make a call.

Code snippets
No response
OS
Linux
Node version
18+
Library version
openai v.4.21.0

Can you share a stacktrace?

Unfortunately cloudflare logs only give me this info when i make call to openai
    {
      "message": [
        "TypeError: Reflect.get called on non-object"
      ],
      "level": "error",
      "timestamp":<PHONE_NUMBER>370
    }

Found out this issue is not related with open package but instead with next-on-pages package used to build next js project.
There is already an open issue on there :D
https://github.com/cloudflare/next-on-pages/issues/499

Found out this issue is not related with open package but instead with next-on-pages package used to build next js project.
There is already an open issue on there :D
https://github.com/cloudflare/next-on-pages/issues/499


Author, please help me！！！！！

HELLO,my english not good,hope you can understand
i am make it,doncon io and doncon pad，but ，end ，the don is ok.80 can to use and very sensitive ,but the ka is not ok after on the Arcade drum skin,if 2 is Automatic triggering, set 3 also need a certain amount of force to trigger,so, How should I debug code,.Make the ka more sensitive, thank you very much, i really need your help, please

Hi,
happy to see someone attempting to build this project :)
Getting the sensitivity right is not easy and I'm also not entirely happy with my build yet. From my experience, the largest influence is the construction of the drum itself. I don't know your build and I sadly have no access to a arcade drum skin to see how it behaves.
I can give you some general tips which helped me to increase sensitivity:

Make sure all pads have the same height and are level. There should be no gap between the drum skin and the pads. I used paper washers for leveling the individual pads.
Sensors need to be attached as firmly as possible to the pads. I used some custom build metal brackets.
You can also try to attach the sensors closer to the to (where you hit the drum)

You can also try to increase the amplifier gain only for the KAs, but this might not solve the actual issue.

感谢您给的回答，为了提高咔的灵敏度，我做了以下改进方案，确实如您所说，1，我改变了，咔传播的介质，调整了咔的位置，使之相同力度产生更大的数值，2，我给做的木板边缘做了倒角处理，使之更贴合橡胶，3，我改变了2个咔的前端电路，把2个1兆欧的电阻换成了100k，试图让咔产生的信号加大，如您所说，您说的建议我都尝试过，但是假如感应器和木板之间像官机加了一层铁板的话，哪怕上面情况都调整了，触发力度仍然不够，不加铁板，阀值也必须设置个位数才行，太极限了，咚是贴木板的，咔是贴铁板的，官机就是这样，所以我想让您调试下代码，告诉我调哪里可以提升咔的灵敏度，或者告诉我如何调整咔的前端电路，阻值应该如何更换大小，才能更有效的提升咔产生的数值，非常感谢

Thank you for your answer.
In order to improve the consistency of the click,
I made the following improvements to the plan.
It is exactly as you said,

I changed the medium of click propagation and adjusted the position of the click so that the same intensity can produce greater The value,
2, I chamfered the edge of the wooden board to make it fit the rubber better,
3, I made 2 front-end changes to the circuit, and replaced the two 1M欧 with 100k, Trying to adjust the signal strength generated by the card,
as you said,
but I have tried everything you said. Assuming that a layer of iron plate is added between the sensor and the wooden board like the official machine,
the above conditions have been adjusted,
and the triggering strength It’s still not enough.
If you don’t add an iron plate, the threshold must also be adjusted. It’s too extreme. The dong is attached to the wooden board, and the click is attached to the iron plate. This is how the official machine is, so I want you to debug the code. Tell me where to adjust to improve the click sound, or tell me how to adjust the pre-circuit of the click, and how to change the resistance value to more effectively improve the value generated by the click. Thank you very much.

Thankyou very much and i am finished
ka is ok，problem is The size of the board

Sorry for the delayed answer, I've been busy the last few days.
Nice to hear that you got it working, I will close this issue then.
I you like to share some details which could help other people, feel free to use the 'Discussions' section.


Handle unclosed C# code blocks better when intermingling HTML

Original issue: https://github.com/aspnet/Razor/issues/2566
Paste the following code with test as a TagHelper.
<test>
        @if (ShowFooter){
        { }
</test>

The end test gets understood as an invalid closing tag because of the above unclosed C# statement. In our journey of re-writing the syntax tree we should handle this scenario better and close out the incomplete C# code block once we see an unpaired closing tag.
@ajaybhargavb could you cost this based on what you feel it would take to do with the new world Html aware Razor parser?

@ajaybhargavb could you cost this based on what you feel it would take to do with the new world Html aware Razor parser?

Correct me if I am wrong but from what I understand currently, this would be a fairly major change in the way the CSharp parser works. I would say given the way it works, this is almost by design. Consider this case,
<test>
@if (ShowFooter){
</test>
var x = Foo;
}

When the CSharp parser encounters the first <test>, it needs to make a choice. If it closes out the statement block when it sees an Html block then var x = Foo will be parsed as Html. But we definitely don't want that. CSharp parser would need to have a LOT more context in order to know the difference between "I just forgot to close my statement block" vs "I just forgot to write a start tag".

You've convinced me. @rynowak what do you think?

lol why did you create a separate bug for this.


HAI-2402 Show car traffic nuisance categories in nuisance control plan page

Description
Show car traffic nuisance categories in nuisance control plan page
Jira Issue: https://helsinkisolutionoffice.atlassian.net/browse/HAI-2402
Type of change

[ ] Bug fix
[x] New feature
[ ] Other

Instructions for testing
Open a project, draw some geometries for it and give nuisance values and go to "Haittojen hallinta" page. There should be car traffic nuisance with an index and indexed subcatagories under it.
Checklist:

[x] I have written new tests (if applicable)
[x] I have ran the tests myself (if applicable)
[ ] I have made necessary changes to the documentation, link to confluence
or other location:

Other relevant info
Please describe here if there is e.g. some requirements for this change or
other info that the tester/user needs to know.

According to Figma the sub sections should not have "Haittaindeksi" text above the index.

According to Figma the sub sections should not have "Haittaindeksi" text above the index.

That's right! Thank you for noticing. I set the showLabel parameter to false.


Graph view theme colors sometimes go opposite / out of sync from the page theme

Here the colors applied to the graph view get out of sync from the actual theme leaving the grpah view very hard to read;

This shoud be fixed in 1.7.1


Question: how to remove server name from completion popup

I'm using Intelephense with vim-lsp and I see [Intelephense] everywhere inside the completion popup.
How do I disable this?

call ncm2#override_source('intelephense', {'mark': ''})


Signal VC_EVENT_READ_COMPLETE when ATS received trailing header fields

One of the fixes for #6313. As @maskit pointed out on #6401, the VC_EVENT_READ_COMPLETE event was not sent when ATS received trailing header fields after c55001b. It uncovered an issue of  HttpTunnel ( this should be fixed in another PR ).
TODO: Add AuTest to cover this trailer case.
I used nghttp with --trailer option in local tests. But I'm wondering we can use curl to avoid increasing dependencies of AuTest.

I think requiring nghttp on the ci box is quite reasonable. A curl supporting HTTP2 is already pulling in the nghttp2 libraries.   I already have added an autest that requires nghttp (which is currently being skipped on the CI).

Does the state machine even understand and set up VIO's for trailing headers yet?  I'd argue that this change doesn't help much until the state machine deals with trailing headers.

[approve ci centos]

Why is  VC_EVENT_READ_COMPLETE not sent?

As noted on PR #6401 the crashes we are seeing in our environment are not due to trailing headers.

@shinrich
I didn't know nghttp command is already used in AuTest. Let's install nghttp on the box.

Does the state machine even understand and set up VIO's for trailing headers yet? I'd argue that this change doesn't help much until the state machine deals with trailing headers.

This change doesn't add trailing headers support. Just fix the missing READ_COMPLETE event with the trailing header.

And should it send READ_COMPLETE? Or an EOS?

Good point. I'm wondering that the EOS flag on HTTP/2 frame should trigger VC_EVENT_EOS instead of VC_EVENT_READ_COMPLETE. I'll dig more.

@vmamidi As Susan described on #6313 & #6401, after c55001bec19d4db63f58b484186b942fbec5ae2a change, Http2Stream signal VC_EVENT_READ_COMPLETE only if EOS flag is set on the HTTP/2 frame.
In general case, the last DATA frame has the  EOS flag, but in this trailing header case, the last HEADERS frame has the EOS flag, but it was just ignored.

As for VC_EVENT_EOS vs VC_EVENT_READ_COMPLETE, I think VC_EVENT_READ_COMPLETE is appropriate here. Because VC_EVENT_EOS is signaled from UnixNetVConnection/SSLNetVConnection in error cases.

[approve ci autest]

[approve ci autest]

Cherry-picked to v9.0.x branch.


Add v to version number.  Should be v0.12.1

Thanks @lightiv .  See ovrclk/docs#170 - I changed the documentation.


the export model and read_checkpoint is conflict

in the export.py file,  in the version1_export and version2_export function, have these codes
    # first write out the header. the header will be 256 bytes
    # 1) write magic, which will be uint32 of "ak42" in ASCII
    out_file.write(struct.pack('I', 0x616b3432))
    # 2) write version, which will be int
    out_file.write(struct.pack('i', version))

but, in the run.c, read_checkpoint function， not handle the magic and version bytes.
so, it when i export model use verion 1 or 2, it will have a fatal
malloc failed!

i think, the code in the version1_export and version2_export function should delete, or handle the magic and version bytes in the read_checkpoint function
    char magic[4];
    int version;
    if (fread(&magic, sizeof(unsigned int), 1, file) != 1) { exit(EXIT_FAILURE); }
    printf("magic is %s\n", magic);
    if (fread(&version, sizeof(int), 1, file) != 1) { exit(EXIT_FAILURE); }
    printf("version is %d\n", version);
    ......
    float* weights_ptr = *data + sizeof(Config)/sizeof(float) + 2;

Hi @l1351868270
I think the issue I get is similar to this: https://github.com/karpathy/llama2.c/issues/510
Did you have any directions to how to fix this in run.c?

Use legacy version for run.c and version 2 for runq.c


Create eleventy-neat-starter

Eleventy Starter Template with NEAT Stack - Netlify CMS, Eleventy, Alphine JS & Tailwind CSS

Needs a .json file extension!

@zachleat Oops. did not realize that. Fixed now.

@zachleat Just revisiting this pull request. Anything else needed from my side?

I'd assume, he's busy.

Thank you!


Test-MSS shows a read time out port=25484

https://github.com/Open-MSS/MSS/actions/runs/5674856356/job/15379139922?pr=1838#step:9:2266
ERROR tests/_test_msui/test_mscolab.py::Test_Mscolab::test_add_operation - requests.exceptions.ReadTimeout: HTTPConnectionPool(host='<IP_ADDRESS>', port=25484): Read timed out. (read timeout=10)
= 1 failed, 499 passed, 27 skipped, 286 warnings, 1 error in 616.03s (0:10:16) =

the test-develop-xdist doesn't
This needs investigation. It is maybe the amount of used ports?

with the test refactoring the behaviour changed


feat: add option to remap URLs before opening

This is a naive solution to #8.  It adds a config option, which is a json dict where each key is replaced by the value in the sourcegraph url before opening it.
For example, if you have git running at<EMAIL_ADDRESS>this fixes #8 by setting the sourcegraph.remoteUrlReplacements option to {"git@git.example.org:": ""}.
As another example, if git@othergit.example.org:repo should show up in sourcegraph as src.example.org/othergit/repo, you can add "git@othergit.example.org:": "othergit/".
I am not super happy with this implementation, so I am open to suggestions for how to make the configuration easier to understand.

I noticed linting in CI didn't work correctly which is now fixed. @matthewbentley could you fix the ESLint violations?

This would be really nice to get in.

I wasn't able to locate the documentation on this feature. Can it be used to map any branch to master? I find when opening local branches that are not pushed to master, my link fails when 99% of the time what I really want is to fall back to master so I can send someone a link to existing code, not something I modified on my branch.


error messages when running gradle plugin

The annotation processor of querydsl gives a number of error messages that should be info/debug messages:
Note: Running JPAAnnotationProcessor
Note: Serializing Embeddable types
Note: Generating ch.adnovum.jcan.jpa.audit.QAuditInfo for [ch.adnovum.jcan.jpa.audit.AuditInfo]
environment: gradle, windows, java 8

Which gradle plugin do you use?
I think you mean this gradle plugin.
It is not hosted or maintained by us.
(or at least, we do not have a gradle plugin)

oh, sorry, the ticket was not quite correct, there is no dedicated plugin, just the querydsl annotation processed plugged into gradle.

We already print to the APT messager with NOTE level.
This is the 'informative message' level.
http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/8u40-b25/javax/tools/Diagnostic.java#Diagnostic.Kind

Do you mean the red text during compilation?
I think Gradle doesn't have a way of discerning which text gets printed (javac bad output, or annotation processing tool info output).

yes, the red text. Is a bit annoying as red text is supposed to be a problem.
I think it is a general problem with the notes log level. There is a ticket for that in the jdk:
https://bugs.openjdk.java.net/browse/JDK-6949601
that is open for a while now. It would be helpful if there is is a possiblity to disable the logging messages in querydsl.

I think the problem is that you cannot opt out from just the NOTE messages with javac. you either have INFO and WARN, or you have nothing (see -nowarn flag for javac).
This is quite frustrating for me as well, since if I am curious if my build has warnings, I have to also opt-in for the NOTE level messages, that querydsl prints.

Maybe make it opt-in with 'SupportedOptions' https://docs.oracle.com/javase/8/docs/api/javax/annotation/processing/Processor.html#getSupportedOptions--
Then you could pass a command line arg to javac that enables the NOTE messages when someone still needs it.


v. 0.7.3 broken with 414: url too long

It seems that v. 0.7.3 broke the possibility to use @changeset as the parameter for form_for.  Given this sample code (that works well with 0.7.1)
<!--File index.html.drab -->
  <button type="button" drab="click:drab_test">DRAB TEST</button>

  <%= form_for @changeset, "/my/path",  fn f -> %>
    <%= input f, :test_field %>
    <%= submit "Submit" %>
  <% end %>

# File test_commander.ex
  defmodule MyApp.TestCommander do
    use Drab.Commander
    def drab_test(socket, sender) do
      IO.inspect sender, label: "drab_test"
    end
  end

the Commander function isn't called at all when the button is clicked, and the browser console show many WebSocket errors like these when the page is loaded:

WebSocket connection to 'ws://localhost:4000/socket/websocket?__drab_return=SFMyNTY.g3QAAAACZAAEZGF0YWwAAAAFaAJkAAxfX2NvbnRyb2xsZXJkACRFbGl4aXIuRnJvbnRlbmRXZWIuQWNjb3VudENvbnRyb2xsZXJoAmQAC19fY29tbWFuZGVyZAAjRWxpeGlyLkZyb250ZW5kV2ViLkFjY291bnRDb21tYW5kZXJoAmQABl9fdmlld2QAHkVsaXhpci5Gcm9udGVuZFdlYi5BY2NvdW50Vmlld2gCZAAIX19hY3Rpb25kAARlZGl0aAJkAAlfX2Fzc2lnbnNqamQABnNpZ25lZG4GAG98J59iAQ.3tZAACbsnr3ThtDXrGGKdEk9YlFA8LAH5QBEX45Ults&__priv%5Bassigns%5D%5Bge3daojrga2dmmrq%5D%5Bchangeset%5D=QTEyOEdDTQ.pcBDLYjF5vwOQRHLgc3usgeLO37Yo4H9X78qB...a8laiwyu0w7hPZUFS_7GlIuSe1WMul3fCesBeomaKVd_9G6RHOopzPU9_ncbH5gluD0_oDGBVMMLSjALasN7e8w9K7BGddSeBX2U_cOfb1mbjKjh017b-Dt1rsWAxJgLCI6JUnlsvMq5Dk8uuJjkwr_sLWNqXWK98Z0nYaLauZNEHtfJvvdqXbwniKKDRAae18zpE79BJ_5jkH1Zqs4LCZlVnmGqV9sJ7F-fEJgMtYe6P4OGtMtfdMBJG9jJw3Fg_ECKZxDgLUG0PxncsocG74lFtgiqPFbBD4HyBMsubuNepG3FgwV84mw6xz2j7scS2xWevJuUB4AhhbnNK-3zSmrg16KK7uoW6Qf0Tq_F3hozvE6Kyi0Fdb59VaJTGMSROwha_LxJ7-ewfBq6tk4T2N9cCKYApJmy1wcvsDHU9SY-1zOiVMC9pzqiH.NndL55U2To5TFBOq50-jJA&&__priv%5Bindex%5D=ge3daojrga2dmmrq&vsn=2.0.0' failed: Unexpected response code: 414
WebSocket network error: The operation couldn’t be completed. Connection reset by peer

Instead, if we use@conn instead of @changeset
<!--File test.html.drab -->
  <button type="button" drab="click:drab_test">DRAB TEST</button>

  <%= form_for @conn, "/my/path",  fn f -> %>
    <%= input f, :test_field %>
    <%= submit "Submit" %>
  <% end %>

drabs work well as usual without any WebSocket error also using 0.7.3.

Hi @guidotripaldi, thanks for reporting!
Is there any log on the server side? Should be something about Drab.Socket.verify.

No I'm sorry, I cannot see any log from Drab one the server side

Yes, I missed the http response: 414 (url too long).
This is a bug, and must be solved quickly, as it will cause errors on every page with big assigns.

I haven't yet studied your code so I cannot give help in fixing errors, but I'm at your disposal for debugging.

Thanks a lot! I already know what is wrong.
When the page connects, client sends all assigns to the server (to have in cached on the server side, so there is no latency in peek, and less latency in poke). In 0.7.2 I've changed the way it is doing it, moving it to the connect token, which is passed as url parameter.
This caused an error, when there is too many assigns or they contain too many data.

v 0.7.4 installed, all seems ok now! I check it extensively and will report any error


Add term server links to DD content (website)

21/12/21 - Maxine: has this been done? It says "This is a refinement to 3+"

That was the aspiration. Subsequently agreed on demo calls that this is a post 3++ deliverable.

This is to add a Terminology Server link to every coded Attribute.


Handle NPE during get remote hosts

This is for MMENG-4206 [repo service] get remote repos failed on NPE due to invalid remote url

LGTM.


Cannot get file placement to work

When I run:
Storage::disk('local')->put('testphoto.png', file_get_contents('https://example.com/photo.png')

The method returns true and the file get placed in my local storage directory.
When I try to use the GCS driver (i called it images) I get this Exception:
Storage::disk('images')->put('testphoto.png', file_get_contents('https://example.com/photo.png')

League \ Flysystem\ UnableToWriteFile

Unable to write file at location: testphoto.png.

This is my configuration in filesystems.php:
'images' => [
            'driver' => 'gcs',
            'key_file_path' => env('GOOGLE_CLOUD_IMAGES_KEY_FILE', null),
            'key_file' => [], // optional: Array of data that substitutes the .json file (see below)
            'project_id' => env('GOOGLE_CLOUD_PROJECT_ID', 'your-project-id'), // optional: is included in key file
            'bucket' => env('GOOGLE_CLOUD_STORAGE_IMAGES_BUCKET', 'your-bucket'),
            'path_prefix' => env('GOOGLE_CLOUD_STORAGE_PATH_PREFIX', ''), // optional: /default/path/to/apply/in/bucket
            'apiEndpoint' => env('GOOGLE_CLOUD_STORAGE_API_URI', null), // see: Public URLs below
            'visibility' => 'public', // optional: public|private
            'metadata' => ['cacheControl'=> 'public,max-age=86400'], // optional: default metadata
            'throw' => true,
        ],

The error is thrown in  League \ Flysystem \ GoogleCloudStorage \ GoogleCloudStorageAdapter: 156 when running $this->bucket->upload($contents, $options); but there is no Exception explaining why the file cannot be written.
Making this into an issue because I ran the exact same code in another Laravel 8.40 environment with version 1.0 of the spatie/laravel-google-cloud-storage package and it worked on that environment (using the GCS key config from the example below).
So for me the problem exists on Laravel 9 with the most recent version of the package.
What did I miss?

Diving further into the code (catching the GCS output) I get this Exception:
{ "error": { "code": 400, "message": "Cannot insert legacy ACL for an object when uniform bucket-level access is enabled. Read more at https://cloud.google.com/storage/docs/uniform-bucket-level-access", "errors": [ { "message": "Cannot insert legacy ACL for an object

When uncommenting line 141 in the GoogleCloudStorageAdapter, it works:

Is there a way to disable the $options['predefinedAcl'] = $predefinedAcl;?

I have found that changing the 'visibility' to this (according to the README) has fixed the problem:
'images' => [
            'driver' => env('IMAGES_DRIVER', 'local'), // use IMAGES_DRIVER=gcs for Google Cloud Storage
            'key_file_path' => env('GOOGLE_CLOUD_IMAGES_KEY_FILE', base_path('.local/gcs-keys/we-compare-images-testing.json')),
            'key_file' => [],
            'project_id' => env('GOOGLE_CLOUD_PROJECT_ID'),
            'bucket' => env('GOOGLE_CLOUD_STORAGE_IMAGES_BUCKET'),
            'path_prefix' => env('GOOGLE_CLOUD_STORAGE_PATH_PREFIX', null),
            'storage_api_uri' => env('GOOGLE_CLOUD_STORAGE_API_URI', null),
            'visibility' => PortableVisibilityHandler::NO_PREDEFINED_VISIBILITY,
            'metadata' => ['cacheControl'=> 'public,max-age=86400'],
            'root' => storage_path('app/public'),
            'url' => env('APP_URL') . '/storage',
            'throw' => true,
        ],


compiling using OpenJDK

Looks like compilation fails when we are using openjdk. Error logs can also be seen on the travisci bug log. as its marked as ignore error at this point so i  am assuming author is aware of it. Can you suggest what's the reason why compilation is failing. any plans on getting it to build on openjdk.

Yes compilation with OpenJDK does not work. The build requires the Oracle JDK (7 or 8) currently. I'll update the build information to specify that.


Accept any credentials to log in

We should change the logic to accept any email/password so we don't have to keep resetting the credentials.
Re https://github.com/keystonejs/keystone/issues/2137

alternatively, if we integrate oauth with google plus that would solve the vandalism issue altogether

@morenoh149 The credentials are now protected, so this is no longer an issue, correct?

Reopen this if you disagree with the above - I'm trying to clear up the issue tracker.

Still show The email and password you entered are not valid. when use<EMAIL_ADDRESS>/ demo login.

Yeah, I agree. I can't log in to the demo site at the moment. @bassjacob / @JedWatson ?


Labels for Messidor-2

In your paper you mention that you used the Messidor-2 set for testing. As far as I know the Messidor-2 set does not come with DR labels, in contrast to Messidor-Original. Did you assess DR for the images in Messidor-2 yourself, or did you have an ophthalmologist who labeled the images for your research?

It is here:
https://medicine.uiowa.edu/eye/abramoff

Thanks! Strange that they are not uploaded here http://latim.univ-brest.fr/indexfce0.html.
In your study you used a definition of referable diabetic retinopathy (rDR) of ICDR levels 1 to 4. As far as I can see, is that the labels on that website (Messidor-2 labels) assess rDR defined by ICDR levels 2 to 4. How were you able to test Messidor-2 for your definition of rDR?

They aren't same indeed, and I pointed this out in the paper. My model might be more sensitive to level 1 DR than others reported on Messidor-2, but I can not attest this qualitatively. Are you doing this on business? If yes, I am available for collaboration,

OK, understood. What you could do is get the Messidor-Original data set and use the labels from there to evaluate. They didn't grade by using ICDR, but since your model detects mild DR as rDR you can simply translate the Messidor-Original labels to 0 and 1. And then use the image pairing labels in Messidor-Original which can be retrieved from Messidor-2 for improved performance as well.
Thanks for your insights :)


Documentation for previous version

Hello Julian,
I am using <IP_ADDRESS>, and running some of the current examples (0.5), keep throwing lots of errors, which I assume , would not happen if the examples were from previous versions. (Case in point, I am looking for a mixed variable example for the previous version)
Would it be possible to also have the documentation of the previous version in place?

I tried to access documentation of version 0.5.0 (last is 0.6.0), but archive.pymoo.org is asking me a username and a password.
Am I missing something?

Checkout the link again: https://pymoo.org/versions.html
The credentials are mentioned at the very top of the page.
We have this to prevent search engines from crawling old pages.

@blankjul thank you very much for the quick answer.
I am sorry I overlooked the first lines of the documentation.


Choice value always displays null when loading page first

i expect that the init value would be from SharedPreferences,so i invoke initSoundSetting,but when loading page ,it always displays null
class _StudyModelSoundSettingState extends State<StudyModelSoundSetting>{

  int soundSetting;
  void initState(){
    super.initState();
    initSoundSetting();
  }

  void initSoundSetting()async{
    final SharedPreferences prefs = await widget.sp;
    final soundSettingValue = prefs.getInt('soundSetting');
    this.setState(() {
      this.soundSetting = soundSettingValue==null?4:soundSettingValue;
    });
  }

  void changeSoundSetting(int newValue)async{
    final SharedPreferences prefs = await widget.sp;
    setState(() {
      this.soundSetting = newValue;
    });
    prefs.setInt('soundSetting', newValue);
  }

  List<S2Choice<int>> soundSettingOptions=[
    S2Choice<int>(value:1,title:'正常'),
    S2Choice<int>(value:2,title:'震动'),
    S2Choice<int>(value:3,title:'静音'),
    S2Choice<int>(value:4,title:'系统预设'),
  ];

  Widget build(BuildContext context){
    print(this.soundSetting);
    return SmartSelect<int>.single(
        title:'铃声模式',
        choiceItems:soundSettingOptions,
        modalType: S2ModalType.bottomSheet,
        value: this.soundSetting,
        onChange: (state){
          changeSoundSetting(state.value);
        },
    );
  }
}

I released https://pub.dev/packages/flutter_awesome_select with fixed null safety.
Could you check that everything works for you?

i expect that the init value would be from SharedPreferences,so i invoke initSoundSetting,but when loading page ,it always displays null
class _StudyModelSoundSettingState extends State<StudyModelSoundSetting>{

  int soundSetting;
  void initState(){
    super.initState();
    initSoundSetting();
  }

  void initSoundSetting()async{
    final SharedPreferences prefs = await widget.sp;
    final soundSettingValue = prefs.getInt('soundSetting');
    this.setState(() {
      this.soundSetting = soundSettingValue==null?4:soundSettingValue;
    });
  }

  void changeSoundSetting(int newValue)async{
    final SharedPreferences prefs = await widget.sp;
    setState(() {
      this.soundSetting = newValue;
    });
    prefs.setInt('soundSetting', newValue);
  }

  List<S2Choice<int>> soundSettingOptions=[
    S2Choice<int>(value:1,title:'正常'),
    S2Choice<int>(value:2,title:'震动'),
    S2Choice<int>(value:3,title:'静音'),
    S2Choice<int>(value:4,title:'系统预设'),
  ];

  Widget build(BuildContext context){
    print(this.soundSetting);
    return SmartSelect<int>.single(
        title:'铃声模式',
        choiceItems:soundSettingOptions,
        modalType: S2ModalType.bottomSheet,
        value: this.soundSetting,
        onChange: (state){
          changeSoundSetting(state.value);
        },
    );
  }
}

Same problem here, any solution?

Hi everyone,
I'm really sorry for not maintaining the smart_select package in a long time. It's been a great project, but it's become too difficult for me to maintain, especially since I've been going through a tough time for the past few years.
In its place, I've released a new package called choice. The combination to smart_select and chips_choice with cleaner, more flexible, and composable API for creating inline or prompted choice widgets with single or multiple selection.
I hope you'll check out choice. I think you'll find it to be a great replacement for smart_select.
Thanks for your understanding.


Don't show zero-width non-breaking spaces in expression editor

If a table or measure contains zero-width non-breaking space characters in the object name they are displayed as spaces in the expression editor.  In the properties window however, they are not displayed as spaces.
The request is to use a different font or change a setting in the text (expression) editor so that zero-width non-breaking spaces are not displayed (with any width) just like in the properties window.

The expression editor uses a mono width font by design, since features like block select, etc. would not work correctly if all characters does not have equal width.

Daniel, thanks for the quick response.
Can you elaborate on or provide links to the features that require mono-spaced font? I'm not familiar with them.
DAX Studio seems to have a fairly robust editor and still allows for a variety of fonts.


Refactor Codes : Use onViewCreated()

What changed?

file name : HomeViewPagerFragment.kt
Use onViewCreated() for initialization and other tasks.

Why changed?

I learned about the Fragment Life Cycle.
onCreateView() is for having the fragment instantiate. and returns the instantiated view to onViewCreated().
I think separating onCreateView() and onViewCreated() is more suitable for the meaning of the Fragment life cycle.
What do you think of this?

I am not good at English, but thank you for reading.😃

Hi there, thank you for the PR.
I'm unable to compile the code - view.tabs, view.view_pager, and view.toolbar don't resolve. Could you take a look? Thank you!

Hi there, thank you for the PR.
I'm unable to compile the code - view.tabs, view.view_pager, and view.toolbar don't resolve. Could you take a look? Thank you!

Closing as this is no longer relevant since Sunflower was migrated to Compose


Except wrong answer

TPCDS qualification query87 will do two except.
select count(*)
from ((select distinct c_last_name, c_first_name, d_date
       from store_sales, date_dim, customer
       where store_sales.ss_sold_date_sk = date_dim.d_date_sk
         and store_sales.ss_customer_sk = customer.c_customer_sk
         and d_month_seq between 1200 and 1200+11)
       except
      (select distinct c_last_name, c_first_name, d_date
       from catalog_sales, date_dim, customer
       where catalog_sales.cs_sold_date_sk = date_dim.d_date_sk
         and catalog_sales.cs_bill_customer_sk = customer.c_customer_sk
         and d_month_seq between 1200 and 1200+11)
       except
      (select distinct c_last_name, c_first_name, d_date
       from web_sales, date_dim, customer
       where web_sales.ws_sold_date_sk = date_dim.d_date_sk
         and web_sales.ws_bill_customer_sk = customer.c_customer_sk
         and d_month_seq between 1200 and 1200+11)
) cool_cust
;

excepted answer
+----------+
| count(*) |
+----------+
|    47298 |
+----------+

Now the answer
+----------+
| count(*) |
+----------+
|    47297 |
+----------+


Status updates in ExternalClient.Create are omitted

What problem are you facing?
With https://github.com/crossplane/crossplane-runtime/pull/283, we issue a standard update in all cases and that causes the status to be lost since managed resources treat it as subresource. But there are cases where some information about the resource is available only in the response of the creation call to the API.
How could Crossplane help solve your problem?
We could possibly expand resource.Managed interface to have GetStatus() runtime.Object and SetStatus(runtime.Object) and then DeepCopy the status before the update operation and later call SetStatus on the returned object and issue a status update this time.

Whoops - good catch. I always look at events now so I didn't even notice. I think there's a simpler fix for status conditions specifically per #292. That won't cover the case in which a Create implementation itself is mutating status, but I don't think that is a pattern I've seen yet.

I don't think that is a pattern I've seen yet.

We noted in https://github.com/crossplane/crossplane-runtime/pull/292#issuecomment-921777252 that this pattern does in fact exist, at least in some AWS and Azure controllers.

We could possibly expand resource.Managed interface to have GetStatus() runtime.Object and SetStatus(runtime.Object) and then DeepCopy the status before the update operation and later call SetStatus on the returned object and issue a status update this time.

https://github.com/crossplane/crossplane-runtime/pull/280#discussion_r689872890
Hasan had a similar suggestion during review of a PR that lead to #283.

Despite the guidance around the status field's "recreatability" being relaxed per https://github.com/kubernetes/enhancements/pull/2537 I think we should be warning folks to update status (or really any part of the managed resource) during the Create call as only as a last resort, given that we can't just call Create again on the next Reconcile if we fail to persist the result. It's always better to update the managed resource during Observe where possible.
That said, we know there are edge cases where we have no alternative but to rely on persisting updates made during Create so it does seem like we need a solution here.
I don't love the idea of having to extract and save status so we can later persist it again, especially if it requires modifying the resource.Managed interface. 🤔  Some potential alternatives (that I don't particularly love either):

We could consider Create updating status to be enough of an edge case that folks should plumb a Kubernetes client down into their ExternalClient to do so.
We could call Status().Update() before we called UpdateCriticalAnnotations(). The risk being if the status update failed we'd fail to persist our critical annotation and get stuck waiting for human intervention. We could alleviate that by retrying the status update, and further alleviate it by adding a UpdatedStatus bool result to the ExternalObservation struct to allow us to avoid trying to persist status at all when there was no need to.

I think the alternative I like the best is still just trying to establish a "thou shalt not update anything (except annotations)" during Create rule. If I understand correctly we haven't yet found any AWS resources that make status updates in Create that they couldn't also make in Observe. We do know some Azure controllers rely on saving their operations, but it actually seems like they do that to workaround the fact that the external resources don't show up in the Azure API for some time after they're created, so we could probably just ignore the operation completely and use the new WithCreationGracePeriod option to cover that case.

FYI, this causes reconciler to drop any status update made in Observe before the first successful Create call.

I'm working through this today, trying to determine how much of a blocker it could be for updating providers to the latest version of crossplane-runtime. First let me make sure I understand the situation. You're pointing out that in some cases a Create call will appear to succeed, but then later during Observe we'll find out that it didn't really. In this case we probably want to record this situation somehow to the managed resource status.
As far as I can tell, we still will update the status in most cases. For example:

If during Observe we update the MR status then return ResourceExists: true (e.g. the resource was created but is in a bad state) we should fall through to the "resource is up-to-date" clause where we'll persist the status update. I think this is what the RDS example you linked does.
If during Observe we return an error the reconciler should persist that error as a status condition (and event), bringing along any other status updates that were made before the error was returned. I think this is what the Azure Postgres example you linked does.

Is my understanding here correct, or am I missing something? Also, can you let me know whether Terrajet providers are still affected by this? I notice that https://github.com/crossplane-contrib/terrajet/pull/103 removed the block you referenced where we were previously recording a status condition during Observe.

If during Observe we update the MR status then return ResourceExists: true

The case I'm referring to is where we have to return ResourceExists: false because creation actually failed (even though external.Create succeeded in earlier reconcile) and needs to be retried. But in the current implementation if we return ResourceExists: false at any time, the status is lost, which contained the error about the late-failed creation.

Also, can you let me know whether Terrajet providers are still affected by this? I notice that crossplane-contrib/terrajet#103 removed the block you referenced where we were previously recording a status condition during Observe.

That was a workaround and now we're doing a similar thing in callback mechanism by issuing a status update right after the operation completes, but that doesn't apply to native async resources since they don't have such callback mechanism from the APIs they consume. But for Terrajet, we should be good.

The case I'm referring to is where we have to return ResourceExists: false because creation actually failed (even though external.Create succeeded in earlier reconcile) and needs to be retried.

Is this hypothetical, or do we do this in practice? As far as I could tell none of the examples you provided follow this pattern.

@negz  We do that in Terrajet in this line to trigger a new creation, here in Azure PostgreSQL.
In fact, I think it can be considered a bug if we don't do that because then it'd mean we just never retry once a long-running creation fails. We don't see that very often since cloud providers like AWS and GCP make their best to do all validations in the creation calls, albeit there are always cases in those, too, where validation passes but creation fails due to external factors like insufficient capacity.

@negz Opened https://github.com/crossplane/crossplane-runtime/issues/307 to be more specific about the problem I mentioned above. We can keep this issue contained to status updates being omitted after ExternalClient.Create.


line wraps in validation errors confuse inquirer

Validation errors that are longer than the terminal width and wrap around to the next line cause inquirer to get confused about how to position the cursor back on the preceding line.

This issue was moved to neon-bindings/neon#237


In included file: expected ';' after top level declarator [clang: invalid_token_after_toplevel_declarator]

I get the error
In included file: expected ';' after top level declarator
[clang: invalid_token_after_toplevel_declarator]

however, I checked the files and the only place with this error was an include of a standard file, I even checked that but it stopped having that error.

Can you provide a minimal example that reproduces the problem? This might be a bug, but it's not possible to tell from a screenshot.


[Swift 3.1] Fix for initFromArray test on big endian

Account for byte order in initFromArray test. This will allow the test to pass on s390x
This is for swift-3.1-branch.  It is the same as https://github.com/apple/swift/pull/9458

@swift-ci please test

@swift-ci test

Since all tests have passed, can we merge this?  Would also like to merge this on master (#9458)  Thanks.

Fixed in Swift 4.0.  Will close this


Build error. grafana/toolkit Request failed 404 not found

Hi,
How can i fix this?
error An unexpected error occurred<EMAIL_ADDRESS>Request failed "404 Not Found"".
Using node v12.20.0
coder@e4410408e8a7:~/project/image-viewer-panel$ yarn install
yarn install v1.22.10
[1/5] Validating package.json...
[2/5] Resolving packages...
warning Lockfile has incorrect entry for "<EMAIL_ADDRESS>Ignoring it.
[3/5] Fetching packages...
error An unexpected error occurred<EMAIL_ADDRESS>Request failed \"404 Not Found\"".
info If you think this is a bug, please open a bug report with the information provided in "/home/coder/project/image-viewer-panel/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

ty,
C.

worked with npm i npm run build


Flutter TimePicker Doesn't Work Properly

Hi,
I implement timepicker in my flutter app but it's colors doesn't work properly. Here is my code
class HomePage extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    _pickTime() async {
      await showTimePicker(
        context: context,
        initialTime: TimeOfDay.now(),
      );
    }

    return Scaffold(
      appBar: AppBar(
        title: Text("Time Picker"),
      ),
      body: RaisedButton(
        onPressed: () {
          _pickTime();
        },
        child: Text("Time Picker"),
      ),
    );
  }
}

Hi @draxex
Can you please provide your flutter doctor -v and flutter run --verbose logs, and a minimal complete reproducible code sample?
Thank you

Here is my flutter doctor -v result

Here is my flutter run--verbose result
[ +166 ms] executing: [D:\src\flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[  +73 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[   +2 ms] 2ae34518b87dd891355ed6c6ea8cb68c4d52bb9d
[   +3 ms] executing: [D:\src\flutter/] git tag --contains HEAD
[ +267 ms] Exit code 0 from: git tag --contains HEAD
[   +2 ms] 1.20.1
[  +15 ms] executing: [D:\src\flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[  +43 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[   +1 ms] origin/stable
[   +3 ms] executing: [D:\src\flutter/] git ls-remote --get-url origin
[  +41 ms] Exit code 0 from: git ls-remote --get-url origin
[   +2 ms] https://github.com/flutter/flutter.git
[  +93 ms] executing: [D:\src\flutter/] git rev-parse --abbrev-ref HEAD
[  +47 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[   +2 ms] stable
[  +92 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[   +2 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[   +2 ms] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +4 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[   +3 ms] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[   +2 ms] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[  +50 ms] executing: C:\Users\Draxex\AppData\Local\Android\sdk\platform-tools\adb.exe devices -l
[  +61 ms] List of devices attached
[   +6 ms] Artifact Instance of 'MaterialFonts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'GradleWrapper' is not required, skipping update.
[        ] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[        ] Artifact Instance of 'FlutterSdk' is not required, skipping update.
[        ] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[   +2 ms] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[   +2 ms] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'FontSubsetArtifacts' is not required, skipping update.
[  +66 ms] No supported devices connected.
[  +14 ms] "flutter run" took 265ms.
[  +25 ms]
           #0      throwToolExit (package:flutter_tools/src/base/common.dart:14:3)
           #1      RunCommand.validateCommand (package:flutter_tools/src/commands/run.dart:343:7)
           <asynchronous suspension>
           #2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:836:11)
           <asynchronous suspension>
           #3      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:741:33)
           <asynchronous suspension>
           #4      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart)
           #5      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:29)
           #6      _rootRun (dart:async/zone.dart:1190:13)
           #7      _CustomZone.run (dart:async/zone.dart:1093:19)
           #8      _runZoned (dart:async/zone.dart:1630:10)
           #9      runZoned (dart:async/zone.dart:1550:10)
           #10     AppContext.run (package:flutter_tools/src/base/context.dart:149:18)
           #11     FlutterCommand.run (package:flutter_tools/src/runner/flutter_command.dart:730:20)
           #12     CommandRunner.runCommand (package:args/command_runner.dart:197:27)
           #13     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:332:21)
           #14     _rootRunUnary (dart:async/zone.dart:1198:47)
           #15     _CustomZone.runUnary (dart:async/zone.dart:1100:19)
           #16     _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
           #17     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
           #18     Future._propagateToListeners (dart:async/future_impl.dart:725:32)
           #19     Future._completeWithValue (dart:async/future_impl.dart:529:5)
           #20     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:40:15)
           #21     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:311:13)
           #22     FlutterVersion.checkFlutterVersionFreshness (package:flutter_tools/src/version.dart)
           #23     _rootRunUnary (dart:async/zone.dart:1198:47)
           #24     _CustomZone.runUnary (dart:async/zone.dart:1100:19)
           #25     _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
           #26     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
           #27     Future._propagateToListeners (dart:async/future_impl.dart:725:32)
           #28     Future._completeWithValue (dart:async/future_impl.dart:529:5)
           #29     Future._asyncCompleteWithValue.<anonymous closure> (dart:async/future_impl.dart:567:7)
           #30     _rootRun (dart:async/zone.dart:1190:13)
           #31     _CustomZone.run (dart:async/zone.dart:1093:19)
           #32     _CustomZone.runGuarded (dart:async/zone.dart:997:7)
           #33     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:1037:23)
           #34     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
           #35     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
           #36     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
           #37     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:169:5)

[ +278 ms] ensureAnalyticsSent: 266ms
[  +10 ms] Running shutdown hooks
[   +3 ms] Shutdown hooks complete
[   +6 ms] exiting with code 1

In my code, this function shows timepicker
_pickTime() async {
      await showTimePicker(
        context: context,
        initialTime: TimeOfDay.now(),
      );
    }

And I just trigger this function with my RaisedButton
RaisedButton(
        onPressed: () {
          _pickTime();
        },
        child: Text("Time Picker"),
      ),

@draxex What is the issue you are having with TimePiceker exactly?

My TimePicker views like this, it works properly but why it is viewing like that I don't know, It should have blue background on top.

That's the new Time Picker from Material guidelines: https://material.io/components/time-pickers
It no longer has a primary color header. However, the hour ring should show a circular background (maybe you changed that color)

@Zazo032 thank you so much, that's what I looking for

The default TimePicker actually doesn't have the background for the hour ring. Leaving this open in case it doesn't match Material Design spec. Feel free to just close if this isn't the case.

Minimal reproducible code sample
import 'package:flutter/material.dart';

void main() => runApp(MaterialApp(title: 'Sample', home: MyApp()));

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text('Sample'),
      ),
      body: Container(
        child: Center(
          child: RaisedButton(
            onPressed: () {
              showTimePicker(context: context, initialTime: TimeOfDay.now());
            },
            child: Text("Time Picker"),
          ),
        ),
      ),
    );
  }
}

flutter doctor -v
[√] Flutter (Channel master, 1.21.0-10.0.pre.70, on Microsoft Windows [Version 10.0.19041.450], locale en-US)
    • Flutter version 1.21.0-10.0.pre.70 at C:\Development\flutter_master
    • Framework revision 0629030a05 (5 hours ago), 2020-08-13 00:01:03 -0400
    • Engine revision 7571e7c380
    • Dart version 2.10.0 (build 2.10.0-11.0.dev)

[√] Android toolchain - develop for Android devices (Android SDK version 30.0.1)
    • Android SDK at C:\Users\marku\AppData\Local\Android\sdk
    • Platform android-30, build-tools 30.0.1
    • Java binary at: C:\Users\marku\AppData\Local\JetBrains\Toolbox\apps\AndroidStudio\ch-0\193.6626763\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.6.5)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Community
    • Visual Studio Community 2019 version 16.6.30320.27
    • Windows 10 SDK version 10.0.18362.0

[√] Android Studio (version 4.0)
    • Android Studio at C:\Users\marku\AppData\Local\JetBrains\Toolbox\apps\AndroidStudio\ch-0\193.6626763
    • Flutter plugin version 47.1.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[√] Connected device (5 available)
    • SM G950F (mobile)           • ce12171c51cc001c03 • android-arm64  • Android 9 (API 28)
    • sdk gphone x86 arm (mobile) • emulator-5554      • android-x86    • Android 11 (API 30) (emulator)
    • Windows (desktop)           • windows            • windows-x64    • Microsoft Windows [Version 10.0.19041.450]
    • Web Server (web)            • web-server         • web-javascript • Flutter Tools
    • Chrome (web)                • chrome             • web-javascript • Google Chrome 84.0.4147.125

• No issues found!

@darrenaustin is this a fidelity issue with the new time picker?

That was directed towards any flutter team member that looks at this issue @draxex

@markusaksli-nc thank you

CC @rami-a @darrenaustin

Hello, the new time picker reads the colors from the ColorScheme by default. If you use ColorScheme.light() (or dark) in your theme you should get the correct colors. Additionally, you can customize basically all the colors by providing a TimePickerThemeData to your theme.

Thank you for clarifying, didn't know that. I don't see this mentioned in the documentation for showTimePicker. Maybe a reference to TimePickerTheme should be added to the See also: section?

@markusaksli-nc good idea, I've created a PR to update the documentation. https://github.com/flutter/flutter/pull/63776


Different error responses based on DEBUG flag

Not sure if this is a bug or a gap in my understanding (I am very new to Flask, and Python in general).
Since I felt constrained by the dict-based error handling in Flask-Restful, I used the 'errorhandler' decorator provided by Flask. The issue is, the errorhandlers work fine when DEBUG=True (and show custom error responses that I have set up), but show a cryptic {'message': 'Internal Server Error'} when DEBUG=False.
After a lot of struggle, I figured out that it was due to 2 reasons:

The PROPAGATE_ERRORS flag being set and unset on DEBUG=True/False.
This snippet of code in the flask_restful/__init__.py file:

        if not isinstance(e, HTTPException) and current_app.propagate_exceptions:
            exc_type, exc_value, tb = sys.exc_info()
            if exc_value is e:
                raise
            else:
                raise e

        headers = Headers()
        if isinstance(e, HTTPException):
            code = e.code
            default_data = {
                'message': getattr(e, 'description', http_status_message(code))
            }
            headers = e.get_response().headers
        else:
            code = 500
            default_data = {
                'message': http_status_message(code),
            }

which raises the exception and lets the flask errorhandler deal with it if propagate_exceptions is True, but handles the exception by itself if otherwise.
I have 2 suggestions:

You should mention in the documentation that Flask-Restful overrides the default Flask error handlers.

It looks weird to me that flask_restful handles error responses differently based on the DEBUG flag. Is there a way I can disable FR error handling? Is there a flexible error handing option in FR so that I can avoid the Flask errorhandler ?

I have this question too.

I have a similar problem.
My code look like this:
apiv1 = Blueprint('apiv1', __name__)
api = Api(apiv1)

@apiv1.errorhandler(CustomException)
def hander_(error):
    return jsonify({}), 400

In debug mode, the flask errorhandler works fine.
But in none-debug mode, the errorhandler will not work. It never catch the CustomException.

Yes, this is an issue with flask-restful:
As I've understood flask-restful tries to unify the output format of all errors returned by the app. So far that's reasonable. It does this however by completely overriding the usual flask error handling code (for all routes under its control). This is the problem.
There was an attempt to rewrite the error-handling code at some point, but the pull-request was given up. -> #544

Has this been resolved? Or has anyone found a safe workaround?

@harrylewis The workaround is mentioned in #280 comments.

If debug mode is disabled, the PROPAGATE_EXCEPTIONS setting can still be set to True explicitly:
app.config['PROPAGATE_EXCEPTIONS'] = True

The workaround in #280 also works, but does so by completely bypassing flask_restful error handling which I think is a bit of a blunt solution.
Setting PROPAGATE_EXCEPTIONS = True also works, but is a bad solution. When flask_restful is initialised with a flask app, it hijacks Flask's native error handler functions - app.handle_user_exception and app.handle_exception.
When PROPAGATE_EXCEPTIONS = True, flask_restful will forego it's own error handler, and fall back to these original flask app.handle_user_exception and app.handle_exception implementations. This means you can either use flask errorhandlers OR flask_restful's error handler (you might want both).
What these original Flask error handler functions do is check to see if there is a defined custom handler for that given error (a function decorated by @app.errorhandler) and let that function handle the error - which is what we want. Hence why setting PROPAGATE_EXCEPTIONS = True makes @app.errorhandler functions work.
The problem with this is that Flask also does something with PROPAGATE_EXCEPTIONS. In Flask when this is True and there is no defined handler for the error, it will reraise the exception instead of returning a stock werkzeug.exceptions.InternalServerError when the flag is False. This is bad because this single flag does 2 distinct but deceptively similar things, and there is no way to do one, and not the other.
I propose:

The flask_restful error handler should check if there is a flask error handler for the given error and use that.
Additionally if we actually want to forego the flask_restful error handler, flask_restful should do so using a different config flag value. Something like USE_FLASK_ERROR_HANDLER perhaps.

Thoughts? Happy to open a PR with these changes.

@ramshaw888 I think you should open a PR implementing the solution using a config flag value


Docker Toolbox missing from the list

https://www.docker.com/products/docker-toolbox is missing Docker Toolbox from the What's in Docker Toolbox list.

Sorry @arun-gupta, I don't understand your feedback. are you saying that this list

Contain an entry for 'Docker Toolbox'?

Ah, I meant Virtual Box instead.

@bettyjunod can you take a look at this?

Closing as this is not a docs bug


Cleanup GOCART2G: nm-to-m and present

This PR is an attempt to close #72 and #73 which were brought up by @rmontuoro.
First, the nm-to-m issue (#73 ), this solution looks a little different to that in #65 because testing showed it needed to be. However, I believe it accomplishes the same thing.
Now for the more "fun" one, the issue with present(), #72 . The current code might or probably is a Fortran Standard violation (@tclune can say for certain), but it definitely "looks wrong":
   if (present(aerindx) .and. associated(aerindx))  aerindx = 0.0  ! for now

The "fun" part is that the preferred way to do this would have been with a function using an assumed-rank array:
      logical function present_and_associated(p) result(a)
         real, pointer, dimension(..), optional, intent(in) :: p
         a = .false.
         if (present(p)) then
            if (associated(p)) then
               a = .true.
            end if
         end if
      end function present_and_associated

but it turns out the Intel compiler has a probable bug with this, though GNU is happy.
So, after quite a bit of test coding by @tclune and myself, it turns out the best way to handle this for now is with a macro:
#define __PRESENT_AND_ASSOCIATED__(ptr,res) if(present(ptr)) then; res=associated(ptr); else; res=.false.; endif

This is uglier since we now have to make a logical variable for each test and then use that variable. So this:
   if (present(aerindx) .and. associated(aerindx))  aerindx = 0.0  ! for now

becomes:
   logical :: has_aerindx
...
   __PRESENT_AND_ASSOCIATED__(aerindx,has_aerindx)
   if ( has_aerindx )  aerindx = 0.0  ! for now

instead of a nice clean:
   if ( present_and_associated(aerindx) )  aerindx = 0.0  ! for now

That said, @tclune might see some way to make this cleaner.
Still, hopefully this all works. My testing shows it is zero-diff in the Ginoux and K14 cases compared to develop (aka v2.0.0-rc.1)

My prediction is that it does not even have a cost.   There are so many other non FP operations lying around this bit of code, that the compiler can almost certainly bury these (scalar) conversions within some superscalar instruction that is accomplishing something else.      But regardless, compared to the inefficiency of retrieving the value from the resource in the first place such operations are inconsequential.
Perhaps I've missed a bit of the back and forth, but my understanding is that the conversions would only happen once when the quantity in question is first retrieved from the resource file.   So it does not even contribute during the run phase.


Tenant Admin rights

When adding Microsoft 365 learning pathway from https://lookbook.microsoft.com I get an error that I need to be Tenant Admin. The account I am using is a Global Admin so why am I getting this error. Additionally I  have confirmed the requirements for the App Store and language
The full error is listed below:
Provisioning could not be completed
The configuration of your tenant does not satisfy the requirements of the selected template.
Here are the details of missing prerequisites:
In order to provision the template you need Tenant Admin rights. Please ask a Tenant Admin to provision the template for you or to promote yourself to a Tenant Admin.
Please address the missing prerequisites, then try again.

This should have been fixed, please try again

This should have been fixed, please try again

Thanks for the quick feedback, it looks like it is working

Thanks for the quick feedback, it looks like it is working


Replace AppVeyor on GitHub Actions

Implemented workflow for building/testing and publish code coverage results to Codecov during PR creation.
Implemented workflow for publish nuget package to NuGet/MyGet (NuGet by default) after release creation or run  manually.
Removed AppVeyor yaml file.

Also should be performed next steps:

Add NUGET_API_KEY and NUGET_SOURCE secrets.
Add MYGET_API_KEY and MYGET_SOURCE secrets.

For release I propose to skip testing stage at all
release triggers only on tag
ci triggers on every commit
NUGET_SOURCE is not a secret
I propose pushing package to MyGet on every commit into develop

@nvborisenko

release workflow was split on release and release-myget. I kept trigger for release workflow as is, cuz github actions doesn't support easy way for triggering workflow after adding a tag to specific branch. I think on.release.published is the best trigger here.
NuGet source has been hardcoded into workflow.

Should I keep MyGet source as a secret or not?


fix: publish major upgrades of many packages and configuration

BREAKING CHANGE: This removes the static build of Paragon.
Paragon 4.0.0
This PR removes support for the static, css-namespaced build that is used in edx-platform. See all uses here: https://github.com/search?q=org%3Aedx+"paragon%2Fstatic"&type=Code
In letting go of this requirement the following changes are contained in this release:
CSS Modules have been removed.
SCSS is no longer imported into Paragon component JSX files and those that no longer serve a purpose have been deleted.
The way to include Paragon SCSS has changed
Include in your SCSS file:
import '~bootstrap/scss/bootstrap'; // Or other inclusion of bootstrap
import<EMAIL_ADDRESS>
This file contains style modifications for all paragon components. It is not large and is the simplest way to include Paragon styles. Note

It does not include bootstrap. You must include that yourself.
It must be included after bootstrap functions, variables, and mixins

If you are not using SCSS you can include a minified CSS file that also does not include bootstrap:
import<EMAIL_ADDRESS>
You will see minor changes in your snapshot tests
There are no breaking changes in the usage of Paragon components, but there are a couple minor changes in html output.

null values will be present on scope attributes in tables (this seems to be a change in the way React handles null values)
Dropdowns with icons have a className that is no longer outputted incorrectly as an array.

Coverage decreased (-7.7%) to 91.368% when pulling adc05642a32f5667db1710faba2d82663697fd14 on revert-403-revert-breaking-change into 61728b23c1e1a9995bef21af5ce45369473c9578 on master.

Two PR reviews cover code contained in this commit:
#398 feat: remove static build output
#399 feat: remove css module and namespace support

:tada: This PR is included in version 4.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Missing icons (unicode characters?)

As seen on Mageia 6 with Firefox ESR 45.3.0.

I don't know if it's a regression, it's the first time I see it but it might be that previously I had always been using Chrome/Windows 7, thus it could just be a font issue.

Looks like glyphicons fails to load. @alketii Any ideas?
I guess we might switch to fontawsome in this case...
@akien-mga can you confirm the same on http://getbootstrap.com/components/#glyphicons ?

can you confirm the same on http://getbootstrap.com/components/#glyphicons ?

Those work fine for me.

It works fine on Chrome/Windows 7, so it seems to be system-specific.

I'll have to double check but I did not notice this issue anymore on Mageia 6/Firefox, so it might have been a temporary issue.

@akien-mga Probably related to the recent re-push of the bower_components folder.

I confirm it fixed on Mageia.


Add support for 3DTILES_bounding_volume_S2

This does not cover the implicit tiling side of it (that's a separate PR). Just support for the extension and new bounding volume type.
Still needs a bit more test and doc work.
This covers part of #364.

I'm reasonably happy with the doc and test situation now, so I think this is ready.

@kring I cherry picked some small changes made on implicit-s2 that belong here, including the addition of fromQuadtreeTileID(...), getFace(), the HilberOrder class, and formatting / gcc + clang warning fixes.


SAA-1389 initial WIP commit for paid and unpaid activities when allocating to an activity.

Codecov Report
Attention: 11 lines in your changes are missing coverage. Please review.

Comparison is base (e3da273) 86.73% compared to head (3fa5b1b) 86.70%.

Files
Patch %
Lines

...esmanagementapi/service/ActivityScheduleService.kt
25.00%
1 Missing and 5 partials :warning:

...activitiesmanagementapi/service/ActivityService.kt
25.00%
0 Missing and 3 partials :warning:

.../hmppsactivitiesmanagementapi/entity/Allocation.kt
81.81%
0 Missing and 2 partials :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #698      +/-   ##
============================================
- Coverage     86.73%   86.70%   -0.04%
- Complexity     3359     3367       +8
============================================
  Files           356      356
  Lines         11619    11630      +11
  Branches        910      916       +6
============================================
+ Hits          10078    10084       +6
  Misses         1112     1112
- Partials        429      434       +5

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


Getting "RequestTooLarge" on batch follow.

"{"code": 413, "detail": "The request body was too large (limit is 128k)", "duration": "0ms", "exception": "RequestTooLarge", "status_code": 413}"
Any tips?

it seems like you are pushing too much data to the API endpoint. Could you
paste an example activity here?
ᐧ
On Tue, Jun 23, 2015 at 5:01 PM, Joshua Rountree<EMAIL_ADDRESS>wrote:

"{"code": 413, "detail": "The request body was too large (limit is
128k)", "duration": "0ms", "exception": "RequestTooLarge",
"status_code": 413}"
Any tips?
—
Reply to this email directly or view it on GitHub
https://github.com/GetStream/stream-ruby/issues/26.


Panic: Undefined SMS type: 24

As the title says, getting a panic on SMS type 24 when trying to format.
According to my novice interpretation of Signal's code repo, it looks like it's choking on the SENT_FAILED type:
protected static final long BASE_INBOX_TYPE                    = 20;
protected static final long BASE_OUTBOX_TYPE                   = 21;
protected static final long BASE_SENDING_TYPE                  = 22;
protected static final long BASE_SENT_TYPE                     = 23;
protected static final long BASE_SENT_FAILED_TYPE              = 24;
protected static final long BASE_PENDING_SECURE_SMS_FALLBACK   = 25;

I'd provide more info about the specific message, if you can let me know how. I'm unsure how to dive into the backup itself.

Thanks for reporting. Looks like I forgot to hook up Signal's insecure protocols.


[Lancer RPG (1.8)] Bugfix and Additional Mech Data for Frame Selection

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

Changes / Description
Fixed White Witch missing semicolon.
Made IPS-N Caliban selectable in Frame list.
Added data for other official mech frames from expansions:
GMS Chomolungma
GMS Sagarmatha
IPS-N Empakaai
IPS-N Kidd
IPS-N Störtebeker
SSC Emperor
SSC Orchis
SSC Swallowtail (Ranger Variant)
SSC Viceroy
Horus Calendula
HA Enkidu
HA 'Worldkiller' Genghis MK I

Character Sheet Info Roll20 Internal Use only.

Hi @Lightwave8
These frames don't seem to be publicly available through any official channels we can find. We're going to need to block this until we can verify whether this meets our code of conduct

After poking around a bit more, we found all of these stats accessible through the demo files included on the expansions' itchio pages, so this is good to go!


Fixes #2267. Toplevel.EnsureVisibleBounds throws an exception if border is null.

Fixes #2267 - The check was only done on the if condition and not in the set.
Pull Request checklist:

[x] I've named my PR in the form of "Fixes #issue. Terse description."
[x] My code follows the style guidelines of Terminal.Gui - if you use Visual Studio, hit CTRL-K-D to automatically reformat your files before committing.
[x] My code follows the Terminal.Gui library design guidelines
[x] I ran dotnet test before commit
[ ] I have made corresponding changes to the API documentation (using /// style comments)
[x] My changes generate no new warnings
[x] I have checked my code and corrected any poor grammar or misspellings
[x] I conducted basic QA to assure all features are working

@tig I updated the https://github.com/gui-cs/Terminal.Gui/issues/2267#issue-1517378308 to show a visible issue that this PR will fix. Can you merge this to avoid making a cherry.pick on every branches where I'm working on, please. Thanks.