✨ Initial experimental Azure DevOps client

What kind of change does this PR introduce?
This PR introduces early experimental support for Azure DevOps. It's the MVP for a scorecard scan to complete without panicing.

[x] PR title follows the guidelines defined in our pull request documentation

What is the current behavior?
No Support for Azure DevOps repository scanning
What is the new behavior (if this is a feature change)?**
This is a followup from #4178, and the next step for #4177. It is the minimal client implementation for Azure DevOps repository support.
I'd like to get feedback at this stage, before I implement the remainder of the client.

[x] Tests for the changes have been added (for bug fixes/features)

Which issue(s) this PR fixes
Continued work on #4177
Special notes for your reviewer
This change is currenltly gated behind the SCORECARD_EXPERIMENTAL environment variable, same as the initial GitLab client was.
Does this PR introduce a user-facing change?
For user-facing changes, please add a concise, human-readable release note to
the release-note
(In particular, describe what changes users might need to make in their
application as a result of this pull request.)

Initial experimental Azure DevOps client

There's a lot of linter errors that I'm sure you're waiting to resolve until after your approach got reviewed. So I didn't review any of that sort of thing, happy to give tips if desired.

panicing, or completing without runtime errors? What's the manual testing of this look like for the maintainers? Are there any world-public azuredevops repos?

Completing without runtime errors. Here's the output, running against https://dev.azure.com/jamiemagee/jamiemagee/_git/jamiemagee, after my most recent changes:

Details
Aggregate score: 0.0 / 10

Check scores:
|--------|------------------------|---------------------------------------|-----------------------------------------------------------------------------------|
| SCORE  |          NAME          |                REASON                 |                             DOCUMENTATION/REMEDIATION                             |
|--------|------------------------|---------------------------------------|-----------------------------------------------------------------------------------|
| ?      | Binary-Artifacts       | internal error: error during          | https://github.com/ossf/scorecard/blob/main/docs/checks.md#binary-artifacts       |
|        |                        | ListFiles: unsupported feature        |                                                                                |
|--------|------------------------|---------------------------------------|-----------------------------------------------------------------------------------|
| ?      | Branch-Protection      | internal error: unsupported           | https://github.com/ossf/scorecard/blob/main/docs/checks.md#branch-protection      |
|        |                        | feature                               |                                                                                |
|--------|------------------------|---------------------------------------|-----------------------------------------------------------------------------------|
| ?      | CI-Tests               | no pull request found                 | https://github.com/ossf/scorecard/blob/main/docs/checks.md#ci-tests               |
|--------|------------------------|---------------------------------------|-----------------------------------------------------------------------------------|
| 0 / 10 | CII-Best-Practices     | no effort to earn an OpenSSF          | https://github.com/ossf/scorecard/blob/main/docs/checks.md#cii-best-practices     |
|        |                        | best practices badge detected         |                                                                                |
|--------|------------------------|---------------------------------------|-----------------------------------------------------------------------------------|
| 0 / 10 | Code-Review            | Found 0/1 approved changesets         | https://github.com/ossf/scorecard/blob/main/docs/checks.md#code-review            |
|        |                        | -- score normalized to 0              |                                                                                |
|--------|------------------------|---------------------------------------|-----------------------------------------------------------------------------------|
| ?      | Contributors           | internal error:                       | https://github.com/ossf/scorecard/blob/main/docs/checks.md#contributors           |
|        |                        | Client.Repositories.ListContributors: |                                                                                |
|        |                        | unsupported feature                   |                                                                                |
|--------|------------------------|---------------------------------------|-----------------------------------------------------------------------------------|
| ?      | Dangerous-Workflow     | internal error: error during          | https://github.com/ossf/scorecard/blob/main/docs/checks.md#dangerous-workflow     |
|        |                        | ListFiles: unsupported feature        |                                                                                |
|--------|------------------------|---------------------------------------|-----------------------------------------------------------------------------------|
| ?      | Dependency-Update-Tool | internal error: error during          | https://github.com/ossf/scorecard/blob/main/docs/checks.md#dependency-update-tool |
|        |                        | ListFiles: unsupported feature        |                                                                                |
|--------|------------------------|---------------------------------------|-----------------------------------------------------------------------------------|
| ?      | Fuzzing                | internal error: error during          | https://github.com/ossf/scorecard/blob/main/docs/checks.md#fuzzing                |
|        |                        | ListFiles: unsupported feature        |                                                                                |
|--------|------------------------|---------------------------------------|-----------------------------------------------------------------------------------|
| ?      | License                | internal error:                       | https://github.com/ossf/scorecard/blob/main/docs/checks.md#license                |
|        |                        | fileparser.OnAllFilesDo: error        |                                                                                |
|        |                        | during ListFiles: unsupported         |                                                                                |
|        |                        | feature                               |                                                                                |
|--------|------------------------|---------------------------------------|-----------------------------------------------------------------------------------|
| ?      | Maintained             | internal error: unsupported           | https://github.com/ossf/scorecard/blob/main/docs/checks.md#maintained             |
|        |                        | feature                               |                                                                                |
|--------|------------------------|---------------------------------------|-----------------------------------------------------------------------------------|
| ?      | Packaging              | packaging workflow not                | https://github.com/ossf/scorecard/blob/main/docs/checks.md#packaging              |
|        |                        | detected                              |                                                                                |
|--------|------------------------|---------------------------------------|-----------------------------------------------------------------------------------|
| ?      | Pinned-Dependencies    | internal error: error during          | https://github.com/ossf/scorecard/blob/main/docs/checks.md#pinned-dependencies    |
|        |                        | ListFiles: unsupported feature        |                                                                                |
|--------|------------------------|---------------------------------------|-----------------------------------------------------------------------------------|
| ?      | SAST                   | internal error: error during          | https://github.com/ossf/scorecard/blob/main/docs/checks.md#sast                   |
|        |                        | ListFiles: unsupported feature        |                                                                                |
|--------|------------------------|---------------------------------------|-----------------------------------------------------------------------------------|
| ?      | SBOM                   | internal error:                       | https://github.com/ossf/scorecard/blob/main/docs/checks.md#sbom                   |
|        |                        | RepoClient.ListReleases:              |                                                                                |
|        |                        | unsupported feature                   |                                                                                |
|--------|------------------------|---------------------------------------|-----------------------------------------------------------------------------------|
| ?      | Security-Policy        | internal error: error during          | https://github.com/ossf/scorecard/blob/main/docs/checks.md#security-policy        |
|        |                        | ListFiles: unsupported feature        |                                                                                |
|--------|------------------------|---------------------------------------|-----------------------------------------------------------------------------------|
| ?      | Signed-Releases        | internal error: unsupported           | https://github.com/ossf/scorecard/blob/main/docs/checks.md#signed-releases        |
|        |                        | feature                               |                                                                                |
|--------|------------------------|---------------------------------------|-----------------------------------------------------------------------------------|
| ?      | Token-Permissions      | internal error: error during          | https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions      |
|        |                        | ListFiles: unsupported feature        |                                                                                |
|--------|------------------------|---------------------------------------|-----------------------------------------------------------------------------------|
| ?      | Vulnerabilities        | internal error:                       | https://github.com/ossf/scorecard/blob/main/docs/checks.md#vulnerabilities        |
|        |                        | RepoClient.LocalPath:                 |                                                                                |
|        |                        | unsupported feature                   |                                                                                |
|--------|------------------------|---------------------------------------|-----------------------------------------------------------------------------------|
| ?      | Webhooks               | internal error: internal error:       | https://github.com/ossf/scorecard/blob/main/docs/checks.md#webhooks               |
|        |                        | Client.Repositories.ListWebhooks      |                                                                                |
|--------|------------------------|---------------------------------------|-----------------------------------------------------------------------------------|

Did you plan on finishing the client in this PR or followups? Breaking it up in separate PRs may be easier. Your first approach was "run scorecard without panicing", but I think a good next step is "run a specific check"
So start with something like go run main.go --repo <blah> --checks Maintained, which just needs some info about the repo, commits, and issues. Code-Review is probably in this group too.
Then you can move on to checks which need file content (Binary-Artifacts may be a good one?), and then some of the more involved ones that rely on CI/CD data etc.

I think I'd like to finish the client in a followup PR if that's possible? I think it'd be easier for you to review in smaller chunks instead of one, big bang, pull request.
I plan to attend the scorecard APAC meeting on Thursday to gauge interest as well.

There's a lot of linter errors that I'm sure you're waiting to resolve until after your approach got reviewed. So I didn't review any of that sort of thing, happy to give tips if desired.

I'll tackle those in the next day or two.
Thanks so much for the review!

also your latest commit wasn't DCO'd. that will also be a blocker.

@spencerschrock I think I've addressed all your comments. If so, this should be ready to merge.

@spencerschrock I think I've addressed all your comments. If so, this should be ready to merge.

I've been out on the office on personal time, will take a look in the next day or two.

Wooo, thanks for this contribution, @JamieMagee!


Enable jballerina-unit-tests for ForEach statement

Purpose
$subject
Fixes #23430
Check List

[ ] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

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

@@           Coverage Diff           @@
##           master   #23431   +/-   ##
=======================================
  Coverage   14.59%   14.59%
=======================================
  Files          51       51
  Lines        1411     1411
  Branches      219      219
=======================================
  Hits          206      206
  Misses       1189     1189
  Partials       16       16

Continue to review full report at Codecov.

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


Detox error running tests on real Android device

Description
I am trying to run some simple test on my real Android device, attached with USB to my machine.
If I run the same tests through the emulator everything works fine, but with the real android device I get the following errors:

Example › should show the welcome screen
Timeout - Async callback was not invoked within the 120000ms timeout specified by jest.setTimeout.

  at mapper (../node_modules/jest-jasmine2/build/queue_runner.js:41:52)

● Example › should show the welcome screen
ReferenceError: device is not defined

   5 | describe('Example', () => {
   6 |   beforeAll(async () => {
>  7 |     await device.launchApp({ delete: true, newInstance: true });
     |     ^
   8 |   });
   9 |
  10 |   it('should show the welcome screen', async () => {

  at Object.beforeAll (firstTest.spec.js:7:5)

This is my detox config:
"android.emu.debug-original-device-win": {
        "binaryPath": "android/app/build/outputs/apk/dev/debug/app-dev-debug.apk",
        "build": "pushd android && gradlew assembleDebug assembleAndroidTest -DtestBuildType=debug && popd",
        "type": "android.attached",
        "name": "73QDU17803001744"
      },

The app runs correctly on my device, but the tests do not start at all.
I've tried to run the tests using the RCT_METRO_PORT=8099 env variable and doing the adb reverse tcp:8099 tcp:8099, but no luck.
What is this issue related to? And how can I get it through?
Thanks a lot
Steps to Reproduce
The official page related to Android works totally fine with emulator.
When I try to run tests on my real Android device, I get the issue above.
Detox, Node, Device, Xcode and macOS Versions

Detox: 10.0.9
React Native: 0.57.7
Node: 8.11.1
Device: Honor 8

Device and verbose Detox logs

$ set RCT_METRO_PORT=8099&& detox test --configuration android.emu.debug-original-device-win -l verbose
configuration="android.emu.debug-original-device-win" loglevel="verbose" artifactsLocation="artifacts\android.emu.debug-original-device-win.2019-02-26 14-24-33Z" node_modules.bin\jest "e2e" --config=e2e/config.json --maxWorkers=1 "--testNamePattern=^((?!:ios:).)*$"
detox[13064] INFO:  [DetoxServer.js] server listening on localhost:61909...
detox[13064] DEBUG: [AsyncWebSocket.js/WEBSOCKET_OPEN] opened web socket to: ws://localhost:61909
detox[13064] DEBUG: [DetoxServer.js/LOGIN] role=tester, sessionId=39bf037f-902b-c3fb-79b6-284793175467
detox[13064] DEBUG: [DetoxServer.js/LOGIN_SUCCESS] role=tester, sessionId=39bf037f-902b-c3fb-79b6-284793175467
detox[13064] DEBUG: [exec.js/EXEC_CMD, #0] C:\Users\quiri\AppData\Local\Android\Sdk\platform-tools\adb  devices
detox[13064] DEBUG: [exec.js/EXEC_CMD, #1] C:\Users\quiri\AppData\Local\Android\Sdk\platform-tools\adb -s 73QDU17803001744 shell "getprop ro.build.version.sdk"
detox[13064] DEBUG: [exec.js/EXEC_CMD, #2] C:\Users\quiri\AppData\Local\Android\Sdk\platform-tools\adb -s 73QDU17803001744 shell "dumpsys power | grep "^[ ]m[UW].=""
detox[13064] DEBUG: [exec.js/EXEC_CMD, #3] C:\Users\quiri\AppData\Local\Android\Sdk\build-tools\28.0.3\aapt dump badging "E:\Development\poinz\poinz-app\android\app\build\outputs\apk\dev\debug\app-dev-debug.apk" | findstr /C:"package: name="
detox[13064] DEBUG: [exec.js/EXEC_CMD, #4] C:\Users\quiri\AppData\Local\Android\Sdk\platform-tools\adb -s 73QDU17803001744 shell "pm list packages ch.poinz.dev"
detox[13064] DEBUG: [exec.js/EXEC_CMD, #5] C:\Users\quiri\AppData\Local\Android\Sdk\platform-tools\adb -s 73QDU17803001744 uninstall ch.poinz.dev
detox[13064] DEBUG: [exec.js/EXEC_CMD, #6] C:\Users\quiri\AppData\Local\Android\Sdk\platform-tools\adb -s 73QDU17803001744 shell "pm list packages ch.poinz.dev.test"
detox[13064] DEBUG: [exec.js/EXEC_CMD, #7] C:\Users\quiri\AppData\Local\Android\Sdk\platform-tools\adb -s 73QDU17803001744 uninstall ch.poinz.dev.test
detox[13064] DEBUG: [exec.js/EXEC_CMD, #8] C:\Users\quiri\AppData\Local\Android\Sdk\platform-tools\adb -s 73QDU17803001744 install -r -g -t E:\Development\poinz\poinz-app\android\app\build\outputs\apk\dev\debug\app-dev-debug.apk
detox[13064] DEBUG: [exec.js/EXEC_CMD, #9] C:\Users\quiri\AppData\Local\Android\Sdk\platform-tools\adb -s 73QDU17803001744 install -r -g -t E:\Development\poinz\poinz-app\android\app\build\outputs\apk\androidTest\dev\debug\app-dev-debug-androidTest.apk
detox[13064] DEBUG: [exec.js/EXEC_CMD, #10] C:\Users\quiri\AppData\Local\Android\Sdk\platform-tools\adb -s 73QDU17803001744 shell "am force-stop ch.poinz.dev"
detox[13064] DEBUG: [exec.js/EXEC_CMD, #11] C:\Users\quiri\AppData\Local\Android\Sdk\platform-tools\adb -s 73QDU17803001744 shell "pm list instrumentation"
detox[13064] DEBUG: [exec.js/SPAWN_CMD, #12] [pid=11416] C:\Users\quiri\AppData\Local\Android\Sdk\platform-tools\adb -s 73QDU17803001744 shell am instrument -w -r "-e detoxServer ws://localhost:61909 -e detoxSessionId 39bf037f-902b-c3fb-79b6-284793175467" -e debug false ch.poinz.dev.test/android.support.test.runner.AndroidJUnitRunner
detox[13064] DEBUG: [exec.js/EXEC_CMD, #13] C:\Users\quiri\AppData\Local\Android\Sdk\platform-tools\adb -s 73QDU17803001744 shell "ps | grep "ch.poinz.dev$""
detox[13064] DEBUG: [DetoxServer.js/CANNOT_FORWARD] role=testee not connected, cannot fw action (sessionId=39bf037f-902b-c3fb-79b6-284793175467)
FAIL  e2e/firstTest.spec.js (121.725s)
Example
× should show the welcome screen
× should close the welcome screen and show the home screen
× should open the deep link https://poinz.page.link/rewards
● Example › should show the welcome screen
Timeout - Async callback was not invoked within the 120000ms timeout specified by jest.setTimeout.

  at mapper (../node_modules/jest-jasmine2/build/queue_runner.js:41:52)

● Example › should show the welcome screen
ReferenceError: device is not defined

   5 | describe('Example', () => {
   6 |   beforeAll(async () => {
>  7 |     await device.launchApp({ delete: true, newInstance: true });
     |     ^
   8 |   });
   9 |
  10 |   it('should show the welcome screen', async () => {

  at Object.beforeAll (firstTest.spec.js:7:5)

● Example › should show the welcome screen
ReferenceError: waitFor is not defined

   9 |
  10 |   it('should show the welcome screen', async () => {
> 11 |     await waitFor(element(by.id('welcome'))).toBeVisible().withTimeout(5000);
     |     ^
  12 |     await expect(element(by.id('welcome'))).toBeVisible();
  13 |   });
  14 |

  at Object.it (firstTest.spec.js:11:5)

● Example › should close the welcome screen and show the home screen
Timeout - Async callback was not invoked within the 120000ms timeout specified by jest.setTimeout.

  at mapper (../node_modules/jest-jasmine2/build/queue_runner.js:41:52)

● Example › should close the welcome screen and show the home screen
ReferenceError: device is not defined

   5 | describe('Example', () => {
   6 |   beforeAll(async () => {
>  7 |     await device.launchApp({ delete: true, newInstance: true });
     |     ^
   8 |   });
   9 |
  10 |   it('should show the welcome screen', async () => {

  at Object.beforeAll (firstTest.spec.js:7:5)

● Example › should close the welcome screen and show the home screen
ReferenceError: element is not defined

  14 |
  15 |   it('should close the welcome screen and show the home screen', async () => {
> 16 |     await element(by.label('terms')).tap();
     |     ^
  17 |     await element(by.label('close')).tap();
  18 |     await waitFor(element(by.id('home'))).toBeVisible().withTimeout(5000);
  19 |     await expect(element(by.id('home'))).toBeVisible();

  at Object.it (firstTest.spec.js:16:5)

● Example › should open the deep link https://poinz.page.link/rewards
Timeout - Async callback was not invoked within the 120000ms timeout specified by jest.setTimeout.

  at mapper (../node_modules/jest-jasmine2/build/queue_runner.js:41:52)

● Example › should open the deep link https://poinz.page.link/rewards
ReferenceError: device is not defined

   5 | describe('Example', () => {
   6 |   beforeAll(async () => {
>  7 |     await device.launchApp({ delete: true, newInstance: true });
     |     ^
   8 |   });
   9 |
  10 |   it('should show the welcome screen', async () => {

  at Object.beforeAll (firstTest.spec.js:7:5)

● Example › should open the deep link https://poinz.page.link/rewards
ReferenceError: device is not defined

  21 |
  22 |   it('should open the deep link https://poinz.page.link/rewards', async () => {
> 23 |     await device.relaunchApp({ url: 'https://poinz.page.link/rewards' });
     |     ^
  24 |     await waitFor(element(by.label('deals'))).toBeVisible().withTimeout(20000);
  25 |     await expect(element(by.label('deals'))).toBeVisible();
  26 |   });

  at Object.it (firstTest.spec.js:23:5)

Test Suites: 1 failed, 1 total
Tests:       3 failed, 3 total
Snapshots:   0 total
Time:        121.806s, estimated 122s

I had to do the following steps in order to make it work. Posting it hoping it will be helpful for someone else .

In the detox config inside your package.json , add the following:

"session": {
      "sessionId": "manualsession",
      "server": "ws://<IP_ADDRESS>:8099" // ip of your machine where detox is running
    },

Start the detox server on your machine in another shell through the command:

detox run-server
You should see an output saying:

[DetoxServer.js] server listening on localhost:8099...

In your script for running detox test, specify the env variable pointing to 8099 port RCT_METRO_PORT=8099

Run adb reverse tcp:8099 tcp:8099

You should now be able to run your tests on your attached device too.
Closing the issue as fixed with the above steps.


helperfunctions to common Slice operations

This PR is about following example.
E.g.
len(split("https://www.example.com/", ".", -1)) != 3
// true, the len has toString() make the []string => string first and wrap it with [ and ] and make calc the len => 25

E.g.
(split("https://www.example.com/", '.',-1))[1] == 'example'
// It has no such expression [n] to get the index[n] string
// and also this expression is not return bool. It make result as []string

@tarunKoyalwar

Great bounds checking

lgtm !


Building dependency in Fusesoc step fails on Ubuntu 20.04

Hii, I am trying to run the ibex core on my Ubuntu 20.04 system as suggested in https://github.com/lowRISC/ibex/tree/master/examples/simple_system.
The dependencies are correctly installed, but the fusesoc building simulation step fails inspite of that:
fusesoc --cores-root=. run --target=sim --setup --build lowrisc:ibex:ibex_simple_system --RV32E=0 --RV32M=ibex_pkg::RV32MFast
The error is as follows:
INFO: Running pre_build script check_tool_requirements
INFO: Tool verilator present: Sufficiently recent version (found 4.213; needed 4.028)
INFO: Tool edalize present: Sufficiently recent version (found 0.2.2; needed 0.2.0)
INFO: Building simulation model
verilator -f lowrisc_ibex_ibex_simple_system_0.vc --trace --trace-fst --trace-structs --trace-params --trace-max-array 1024 -CFLAGS "-std=c++11 -Wall -DVM_TRACE_FMT_FST -DTOPLEVEL_NAME=ibex_simple_system -g" -LDFLAGS "-pthread -lutil -lelf" -Wall -Wwarn-IMPERFECTSCH --unroll-count 72
%Warning-UNUSED: ../src/lowrisc_ibex_ibex_top_tracing_0.1/rtl/ibex_top_tracing.sv:27:26: Parameter is not used: 'RndCnstLfsrSeed'
: ... In instance ibex_simple_system.u_top
27 |   parameter lfsr_seed_t  RndCnstLfsrSeed  = RndCnstLfsrSeedDefault,
|                          ^~~~~~~~~~~~~~~
... For warning description see https://verilator.org/warn/UNUSED?v=4.213
... Use "/* verilator lint_off UNUSED */" and lint_on around source to disable this message.
%Warning-UNUSED: ../src/lowrisc_ibex_ibex_top_tracing_0.1/rtl/ibex_top_tracing.sv:28:26: Parameter is not used: 'RndCnstLfsrPerm'
: ... In instance ibex_simple_system.u_top
28 |   parameter lfsr_perm_t  RndCnstLfsrPerm  = RndCnstLfsrPermDefault,
|                          ^~~~~~~~~~~~~~~
%Error: Exiting due to 2 warning(s)
Makefile:16: recipe for target 'Vibex_simple_system.mk' failed
make: *** [Vibex_simple_system.mk] Error 1
ERROR: Failed to build lowrisc:ibex:ibex_simple_system:0 : 'make' exited with an error code
I am new to ibex, can anyone be kind to help me with the resolution of the error.
Thanks in advance.
My Environment

EDA tool and version:

Operating system:

Version of the Ibex source code:

Seems like these two parameters are declared in the module but not used (IDK why it is), there are two ways to off these warnings.

Comment line 27 and 28 in the module ibex_top_tracing.sv. https://github.com/lowRISC/ibex/blob/45f727dfc6e59119347aca62e38e69175f680bf6/rtl/ibex_top_tracing.sv#L27
Add - "-Wno-UNUSED" after line 146 in ibex_simple_system.core file.

But the first one is recommended.

These parameters are used when the SecureIbex parameter is set, but we forgot to waive them if not: I'll push up a patch in a minute to fix that, thanks. They are to allow systems that integrate the chip to specify the initial state of the LFSR that we use to insert dummy instructions.

Oh, actually we forgot to connect them at all. Oops!

Wow, Thank you, guys. I just tried the updated code, and everything works perfectly.
Thanks for promptly solving the issue.


Add support for React 15

Add support for react 15 as peer dependency

Thanks!

Would be awesome if you could also release a new version now that this has been merged :)

Done


How do I write a 403 to the client?

There's a SessionEventArgs.Ok(...) which writes 200 OK responses, but I don't want that - I want my proxy to be able to block things, and have the clients be able to detect that. It shouldn't say the request has made it through fine when it hasn't.
I can create my own Response object and set the ResponseStatusCode manually and send it, but then I can't set the body to something useful because ResponseBody is internal. The RFC says clients can ignore the ResponseStatusDescription, and many do.
Additionally, I can't call set the CancelRequest field on the Request object if I try to do this stuff manually, either, so I get a round-trip even though I don't want one.
In short, I can't see a way to do this without patching the library to add SessionEventArgs.CustomReturnCode(...) type method.
Am I missing something?

We can add the feature. If you have already written a fix feel free for a PR.

For a private release, add a new class under \http\Reponses\GenericResponse.cs, with this content:
using System.Net;

namespace Titanium.Web.Proxy.Http.Responses
{
    /// <summary>
    /// Anything other than a 200 or 302 response
    /// </summary>
    public class GenericResponse : Response
    {
        public GenericResponse(HttpStatusCode status)
        {
            ResponseStatusCode = ((int)status).ToString();
            ResponseStatusDescription = status.ToString();
        }

        public GenericResponse(string statusCode, string statusDescription)
        {
            ResponseStatusCode = statusCode;
            ResponseStatusDescription = statusCode;
        }
    }
}

And then, in SessionEventArgs.cs, add this:
public async Task GenericResponse(string html, HttpStatusCode status)
{
	await GenericResponse(html, null, status);
}

public async Task GenericResponse(string html, Dictionary<string, HttpHeader> headers, HttpStatusCode status)
{
	if (WebSession.Request.RequestLocked)
	{
		throw new Exception("You cannot call this function after request is made to server.");
	}

	if (html == null)
	{
		html = string.Empty;
	}

	var result = Encoding.Default.GetBytes(html);

	await GenericResponse(result, headers, status);
}

public async Task GenericResponse(byte[] result, Dictionary<string, HttpHeader> headers, HttpStatusCode status)
{
	var response = new GenericResponse(status);

	if (headers != null && headers.Count > 0)
	{
		response.ResponseHeaders = headers;
	}
	response.HttpVersion = WebSession.Request.HttpVersion;
	response.ResponseBody = result;

	await Respond(response);

	WebSession.Request.CancelRequest = true;
}

Then in OnRequest, call like this:
await e.GenericResponse("<HTML>Server error</HTML>", HttpStatusCode.500);

Of course, if we add this, should probably derive OK from GenericResponse.

I've added this code, just waiting for it to be merged.

Good work. @kevinrmcd Thanks


some of the new domains / ips

a new pull request because it's easier :P

Thanks! Manually merged those into the dictionary and forced an update!


Updating setting description to fpModel

DO NOT MERGE! LET JOHN MERGE THIS ONE!

What is the change?

Why is the change being made?
close #1701
There was a request to update the description of the setting fpModel.

Checklist

[x] This PR has only one purpose or idea.
[x] Tests have been added/updated to verify any new/changed code.

[x] The code style follows good practices.
[x] The commit message(s) follow good practices.

[x] The release notes have been updated if necessary.
[x] The documentation is still up-to-date in the doc folder.
[x] The dependencies are still up-to-date in pyproject.toml.

@wcscherer Here is the PR for that change.


Example for api instrospection

In the example/client/api i always get 401 from token instrospection when calling /protected.
resp, err := rs.Introspect(r.Context(), provider, token)
if err != nil {
	http.Error(w, err.Error(), http.StatusForbidden)
	return
}

The step:

Get an access token from example/client/service
Pass the token as Authorization Bearer to /protected.

Did i miss something?

Hey @iambudi
The introspection endpoint is a protected endpoint of the Authorization Server itself.
Therefore the API will need to authenticate. In the example it does so with the JWT Profile. See also our docs in ZITADEL: https://docs.zitadel.com/docs/apis/openidoauth/endpoints#introspection_endpoint

You will need to provide a key to the example:
func main() {
	keyPath := os.Getenv("KEY")
	port := os.Getenv("PORT")
	issuer := os.Getenv("ISSUER")

	provider, err := rs.NewResourceServerFromKeyFile(issuer, keyPath)

If your Authorization Server / OpenID Provider does not support this authentication method on the introspection endpoint, you could change the example to use Basic Auth using the rs.NewResourceServerClientCredentials

We will close this issue, since it is resolved from our perspective.
Please feel free to reopen if something is missing

You should use a JWT issued for the client for client authentication, not service user.

Select a project
Add "New" application

Under type off application select "API"

Select Authentication method JWT

After the app is created, you can add and download keys.

{"type":"application","keyId":"207069897346253057","key":"-----BEGIN RSA PRIVATE KEY-----xxxx-----END RSA PRIVATE KEY-----\n","appId":"207069806615068929","clientId":"207069806615134465@test1"}

Use the application JWT in KEY= variable in the go run api.go command

KEY="/home/timz/Downloads/207069897346253057.json" PORT="9099" ISSUER="https://tims-zitadel-instance-oj7iry.zitadel.cloud" go run example/client/api/api.go
2023/03/27 15:19:50 listening on http://<IP_ADDRESS>:9099/

For the service user, create a "personal access token" and set it in the curl header.

curl localhost:9099/protected --header "Authorization: Bearer RznbuQZBQVH2ySfe2zbQh6iSYTF-esvbRS0ad1pTErxTngxPUyh_A7GQma6NuOhGJlsmjnA"
{"active":true,"aud":["207069806615134465@test1"],"exp":1680037200,"iat":1679919769,"iss":"https://tims-zitadel-instance-oj7iry.zitadel.cloud","jti":"207070723204710657","nbf":1679919769,"scope":"openid urn:zitadel:iam:user:metadata urn:zitadel:iam:user:resourceowner","sub":"207068608000426241","token_type":"Bearer","urn:zitadel:iam:user:resourceowner:id":"207065153319993601","urn:zitadel:iam:user:resourceowner:name":"TimsZitadelInstance","urn:zitadel:iam:user:resourceowner:primary_domain":"timszitadelinstance.zitadel.cloud"}

If you have any other questions, please reach out over discord or github discussions for the zitadel product.

You should use a JWT issued for the client for client authentication, not service user.

Select a project
Add "New" application

Under type off application select "API"

Select Authentication method JWT

After the app is created, you can add and download keys.

{"type":"application","keyId":"207069897346253057","key":"-----BEGIN RSA PRIVATE KEY-----xxxx-----END RSA PRIVATE KEY-----\n","appId":"207069806615068929","clientId":"207069806615134465@test1"}

Use the application JWT in KEY= variable in the go run api.go command

KEY="/home/timz/Downloads/207069897346253057.json" PORT="9099" ISSUER="https://tims-zitadel-instance-oj7iry.zitadel.cloud" go run example/client/api/api.go
2023/03/27 15:19:50 listening on http://<IP_ADDRESS>:9099/

For the service user, create a "personal access token" and set it in the curl header.

curl localhost:9099/protected --header "Authorization: Bearer RznbuQZBQVH2ySfe2zbQh6iSYTF-esvbRS0ad1pTErxTngxPUyh_A7GQma6NuOhGJlsmjnA"
{"active":true,"aud":["207069806615134465@test1"],"exp":1680037200,"iat":1679919769,"iss":"https://tims-zitadel-instance-oj7iry.zitadel.cloud","jti":"207070723204710657","nbf":1679919769,"scope":"openid urn:zitadel:iam:user:metadata urn:zitadel:iam:user:resourceowner","sub":"207068608000426241","token_type":"Bearer","urn:zitadel:iam:user:resourceowner:id":"207065153319993601","urn:zitadel:iam:user:resourceowner:name":"TimsZitadelInstance","urn:zitadel:iam:user:resourceowner:primary_domain":"timszitadelinstance.zitadel.cloud"}

If you have any other questions, please reach out over discord or github discussions for the zitadel product.

You should use a JWT issued for the client for client authentication, not service user.

Select a project
Add "New" application

Under type off application select "API"

Select Authentication method JWT

After the app is created, you can add and download keys.

{"type":"application","keyId":"207069897346253057","key":"-----BEGIN RSA PRIVATE KEY-----xxxx-----END RSA PRIVATE KEY-----\n","appId":"207069806615068929","clientId":"207069806615134465@test1"}

Use the application JWT in KEY= variable in the go run api.go command

KEY="/home/timz/Downloads/207069897346253057.json" PORT="9099" ISSUER="https://tims-zitadel-instance-oj7iry.zitadel.cloud" go run example/client/api/api.go
2023/03/27 15:19:50 listening on http://<IP_ADDRESS>:9099/

For the service user, create a "personal access token" and set it in the curl header.

curl localhost:9099/protected --header "Authorization: Bearer RznbuQZBQVH2ySfe2zbQh6iSYTF-esvbRS0ad1pTErxTngxPUyh_A7GQma6NuOhGJlsmjnA"
{"active":true,"aud":["207069806615134465@test1"],"exp":1680037200,"iat":1679919769,"iss":"https://tims-zitadel-instance-oj7iry.zitadel.cloud","jti":"207070723204710657","nbf":1679919769,"scope":"openid urn:zitadel:iam:user:metadata urn:zitadel:iam:user:resourceowner","sub":"207068608000426241","token_type":"Bearer","urn:zitadel:iam:user:resourceowner:id":"207065153319993601","urn:zitadel:iam:user:resourceowner:name":"TimsZitadelInstance","urn:zitadel:iam:user:resourceowner:primary_domain":"timszitadelinstance.zitadel.cloud"}

If you have any other questions, please reach out over discord or github discussions for the zitadel product.

You should use a JWT issued for the client for client authentication, not service user.

Select a project
Add "New" application

Under type off application select "API"

Select Authentication method JWT

After the app is created, you can add and download keys.

{"type":"application","keyId":"207069897346253057","key":"-----BEGIN RSA PRIVATE KEY-----xxxx-----END RSA PRIVATE KEY-----\n","appId":"207069806615068929","clientId":"207069806615134465@test1"}

Use the application JWT in KEY= variable in the go run api.go command

KEY="/home/timz/Downloads/207069897346253057.json" PORT="9099" ISSUER="https://tims-zitadel-instance-oj7iry.zitadel.cloud" go run example/client/api/api.go
2023/03/27 15:19:50 listening on http://<IP_ADDRESS>:9099/

For the service user, create a "personal access token" and set it in the curl header.

curl localhost:9099/protected --header "Authorization: Bearer RznbuQZBQVH2ySfe2zbQh6iSYTF-esvbRS0ad1pTErxTngxPUyh_A7GQma6NuOhGJlsmjnA"
{"active":true,"aud":["207069806615134465@test1"],"exp":1680037200,"iat":1679919769,"iss":"https://tims-zitadel-instance-oj7iry.zitadel.cloud","jti":"207070723204710657","nbf":1679919769,"scope":"openid urn:zitadel:iam:user:metadata urn:zitadel:iam:user:resourceowner","sub":"207068608000426241","token_type":"Bearer","urn:zitadel:iam:user:resourceowner:id":"207065153319993601","urn:zitadel:iam:user:resourceowner:name":"TimsZitadelInstance","urn:zitadel:iam:user:resourceowner:primary_domain":"timszitadelinstance.zitadel.cloud"}

If you have any other questions, please reach out over discord or github discussions for the zitadel product.

Thanks, that works! I think the wording in docs is a bit misleading here. At the moment, it states that you should create an api and download the key for the service user https://zitadel.com/docs/examples/secure-api/go#prerequisites

I've posted an issue on zitadel for follow up :point_up:


FIX: code coverage was not running and now displays badge

YAY! Nice work @nocollier

Thanks :) guess it automatically tagged you for review since you added CODEOWNERS?

Thanks :) guess it automatically tagged you for review since you added CODEOWNERS?

yep!!


[Security] Workflow codecov.yml is using vulnerable action s-weigand/setup-conda

The workflow codecov.yml is referencing action s-weigand/setup-conda using references v1. However this reference is missing the commit a30654e576ab9e21a25825bf7a5d5f2a9b95b202 which may contain fix to the some vulnerability.
The vulnerability fix that is missing by actions version could be related to:
(1) CVE fix
(2) upgrade of vulnerable dependency
(3) fix to secret leak and others.
Please consider to update the reference to the action.

fixed via #974


Decimals and floats not supported?

I try to  get a value with NSDecimalNumber and Float and it not work:
let valor = Expression<Float32>("valor")
let valorPagar = Expression<NSDecimalNumber>("valorPagar")

I get this error here:

$0.value = deuda[valorPagar]

Type 'Row!' has no subscript members

However, If I change the expression to Int or Str it work fine.

Well, Double works too.

I get the same error with Double

dup of #331


{test:name} show null in Version 7

Laravel Version: 7.x.x
PHP Version: 7.3.0
Database Driver & Version: MySQL 5.6

Description:
Route:
Route::get('test/{test:id}', 'TestController@debug');
$pTest->name show null
I have two values in the table tests.
`class TestController extends Controller
{
public function debug(Test $pTest)
{
    var_dump($pTest->name);
    var_dump(Test::all());
}

}`
Steps To Reproduce:

The parameter needs to have the same name as the route segment: https://laravel.com/docs/routing#implicit-binding
class TestController extends Controller
{
    public function debug(Test $test)
    {
        var_dump($test->name);
    }
}

In which PHP file the new functionality is implemented?

How do you mean? You only need to rename the parameter of TestController::debug().

I would like to know where the changes in the framework for this functionality were made. Because I like that in version 6.14. want to customize for a current project

https://github.com/laravel/framework/pull/30471/files


Eliminate max/min distinct

Which issue does this PR close?
Closes #2045 .
Rationale for this change
related: #1315
What changes are included in this PR?
Eliminate distinct in the aggregate instead of rewrite
Now the target is rewrite from
| initial_logical_plan | Projection: #Max(DISTINCT test.c1)
|                      |   Aggregate: groupBy=[[]], aggr=[[Max(DISTINCT #test.c1)]]
|                      |     TableScan: test projection=None

to
| initial_logical_plan | Projection: #Max(DISTINCT test.c1)
|                      |   Projection: #Max(#test.c1) AS Max(DISTINCT test.c1)
|                      |     Aggregate: groupBy=[[]], aggr=[[Max(#test.c1)]]
|                      |       TableScan: test projection=None

instead of
| logical_plan  | Projection: #Max(DISTINCT test.c1)
|               |   Projection: #Max(alias1) AS Max(DISTINCT test.c1)
|               |     Aggregate: groupBy=[[]], aggr=[[Max(#alias1)]]
|               |       Aggregate: groupBy=[[#test.c1 AS alias1]], aggr=[[]]
|               |       Aggregate: groupBy=[[#test.c1 AS alias1]], aggr=[[]]
|               |         TableScan: test projection=Some([0])

Are there any user-facing changes?
None

I encountered some problems during development. Ask for some help. ❤🙌
key point is how to rewrite the shema and expr of alias_projection and rewrited_aggregation. It's will make the entire plan suitable.
Now my code is with bugs. And I can't  rewrite the shema and expr  successful to fix it.

@Dandandan @alamb @ic4y @houqp PTAL, Thanks! ❤

I found that draft PR also trigger CI

I found that problem occur when  call ExprSchema data_type(), it will be error.
Because index_of_column_by_name can't get test.c1  from max(test.c1)

Now I rewrite the logical plan. and println! log in terminal.
I think it's ok. but there will be error.
Projection: #MAX(#test.c1) AS MAX(DISTINCT test.c1)
DFSchema { fields: [DFField { qualifier: None, field: Field { name: "MAX(DISTINCT test.c1)", data_type: Float32, nullable: true, dict_id: 0, dict_is_ordered: false, metadata: None } }], metadata: {} }
Expr[MAX(#test.c1) AS MAX(DISTINCT test.c1)]

	Aggregate: groupBy=[[]], aggr=[[MAX(#test.c1)]]
	DFSchema { fields: [DFField { qualifier: None, field: Field { name: "MAX(test.c1)", data_type: Float32, nullable: true, dict_id: 0, dict_is_ordered: false, metadata: None } }], metadata: {} }
	Expr[MAX(#test.c1)]

		TableScan: test projection=Some([0])
		DFSchema { fields: [DFField { qualifier: Some("test"), field: Field { name: "c1", data_type: Float32, nullable: false, dict_id: 0, dict_is_ordered: false, metadata: None } }], metadata: {} }


Kubernetes backend for docker compose

Tell us about your request
Create a new backend enabling docker compose to deploy Compose apps  to Kubernetes clusters.
Which service(s) is this request for?
Compose CLI in docker/compose-cli

I'll gladly +1 this, but maybe with a caveat as I've been playing around with the experimental support for a little while.
What makes Kubernetes interesting is that there are so many ways to do the same things. Some teams deploy their manifests directly, some teams use GitOps (Flux, Argo, etc.). Some teams are using various tooling to build out manifests (Terraform, Kompose, Cue, etc.).
In addition, the Compose spec doesn't outline everything needed to run an application, Ingress being one of them. Even with Ingress, we are unable to use the stable release of Ingress because the version of Traefik we're running still only supports the beta version.
So... one of the thoughts I've been having is how nice it would be to use the docker compose tooling for everything except the actual launching/destruction of the stack. I can leverage our platform's toolchain to do the deployments (which in our case is Flux), but use the rest of the toolchain for debugging, monitoring, etc. (docker compose logs or docker compose exec being two examples).
To do this, the Compose tooling could outline specific labels/metadata that can be used to discovery projects/services. It then uses that to query for projects, get logs, etc. I've actually updated my Helm project (compose-deployer) to define the labels and a makeshift Helm configmap to get it working. It's super slick, but would be an interesting idea to support it going forward.

Anyone know, what is the status of the k8s / helm backend for docker compose?
Are there instructions somewhere for how to use the experimental support referenced here?
Isn't the docker/compose-cli project kinda dead now that docker compose v2 is available? I believe the docker/compose project now covers the golang rewrite, correct?


ui.router - hook add event to state resolve

In order to avoid FOUC

Is this issue resolved? I still see flash when changing states.


[Network] vpn vnet gateway 100% support

Description

Testing Guide

History Notes

[Network] az network vpn-connection list: support parameter --vnet-gateway.
[Network] New command az network vnet-gateway disconnect-vpn-connections.
[Network] New command az network vnet-gateway vpn-client show-health.
[Network] New command az network vnet-gateway vpn-client ipsec-policy show. TODO add test
[Network] New command az network vnet-gateway vpn-client ipsec-policy set. TODO add test

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Network

[Network] New command az network vpn-connection show-device-config-script. (cannot setup test environment, needs service team support)
'(cannot setup test environment, needs service team support)' should move to 'description', otherwise it will be added to 'HISTORY.rst'


QR code is displayed together with the error message when bluetooth is disabled (Android and iOS version)

Describe the bug
QR code is displayed together with the error message when bluetooth is disabled (Android version)
To Reproduce
Steps to reproduce the behavior:
For Android

Disable bluetooth
Open resident app
Go to the third icon from the left (REQUEST)
Click Deny on the toast for turning on bluetooth
Error message is displayed: Please enable Bluetooth to be able to request ID
Enable bluetooth - verify that QR code is displayed
Go to HOME and disable bluetooth
Go to the third icon from the left (REQUEST)
Click Deny on the toast for turning on bluetooth
SEE ERROR

For iOS

Open Resident app
Go to the third icon from the left (REQUEST)
Go to HOME
Disable Bluetooth connection in toggle
Go to the third icon from the left (REQUEST)
SEE ERROR

Device:
Samsung Galaxy A23
iPhone 11
Resident app build:
v0.4.0 R2 (android)
v0.4.0 (7.1)
MOSIP server:
QA4
Screenshots
https://user-images.githubusercontent.com/102940764/190963920-943e23d1-66e3-4f28-8fcb-416b2eaced79.mp4

Tested on:
QA4 - 0.4.0 (8.0) -iOS
QA4_io.mosip.residentapp-0.4.0-rc3-dirty-newlogic_20220927_0710.apk - Android
Resident app build version:
v0.4.0 (8.0) - iOS
v0.4.0 R3 - Android
MOSIP server: QA4
Devices:
Samsung Galaxy A23
Samsung Galaxy A20s
iPhone SE
iPhone 11
WORKS AS EXPECTED
@kyanthony @pmigueld

Tested in the BLE build (le730bf), the QR code is not displayed with the go-to settings button in both android and IOS, hence closing the bug


import types of schema A into schema B

Thank you for more idiomatic graphql option for go.
I am currently using https://github.com/graphql-go/graphql, though it is incredibly verbose, I could structure the schema so it is kept at module level.
I see one thread in graphql-js regarding the same, in which lee says
https://github.com/graphql/graphql-js/issues/223

If you're using the schema language to build a schema than you need to first combine it into a single string before calling buildSchema. That typically is a nice developer experience for small to medium sized schema, though for more complex schema we recommend building the schema programmatically. Even in this case you still need to collect all the types to assemble the schema. A similar operation to collecting all the strings before calling buildSchema

I wonder what is the best approach you propose with this library. Any plan for incrementally building the schema by registering the graphql schema and resolve functions for isolated modules ?
thanks again for providing this library.

Hi @bsr203, thanks for looking into my project.
My current plan is to not expose the schema data structures. The only way to create a schema is via the schema language. However, at some point I want to add a way to load multiple schema strings and have one schema import types from another schema. Then each schema still has its own namespace, but you can use them together as one big schema.
Does that sound good to you? Do you need such a feature soon?

Thank you for the quick response. What you described would be ideal, and I am in no rush :-) I just wanted to make sure it is considered so we may add it in the future without much of breaking the existing implementation. Do you want to keep this open till it is implemented?
Thank you for all your effort on this.

Yes, we can keep it open. I've changed the title accordingly.

Just adding reference to an approach I saw.
apollostack/graphql-tools allows easy mocking of resolvers, and uses graphql language and resolver very similar to this library. see the example on readme. There is a section about modularization.
I currently modularize the schema by exporting the schema of the module and concatenate before pass to ParseSchema. Resolvers work naturally. AFAIK, the order of type def in schema doesn't matter, hence not much trouble splitting and referencing the schema. I am happy with this approach and you are free to close this.

Happy to hear that! String concatenation sounds like a very clear and simple way of implementing modularization. Do you see any potential limitations?

not really, it works great for me as the order of types within schema doesn't matter. Also, namespacing is not supported  by graphql. There been need for this, but for the moment, we are good :-)

Cool, I'll close this issue. Maybe I'll even replace SchemaBuilder with some simpler API at some point.


[FoldConstant] Create Interpreter for each constant subgraph

This is related to https://discuss.tvm.ai/t/vm-slow-compilation-of-tf-object-detection-models/7479
For TF object detection models, a module has many functions (TF SSD mobilenet has 48), where a couple of functions are pretty huge (more than 10k call nodes). FoldConstant, because it is a function pass, is called for each function in the module. However, FoldConstant also creates an Interpreter on every invocation, which currently is based on the full mod and therefore expensive.
This PR creates an interpreter for each constant subgraph. I am not sure if this is the right way. The purpose of this PR is to start a discussion and identify if there is some other higher-level design issue that needs to be resolved.
With this PR, compilation time of

SSD reduced from 955 to 453 seconds
Faster RCNN reduced from 4630 to 1227 seconds

@zhiics @masahi @kevinthesun @icemelon9

This look right.

Thanks @anijain2305 @MarisaKirisame

It is consistent with your findings
CC: @were

Interestingly this PR seems to have introduced a bug in the VTA image classification example: https://github.com/apache/incubator-tvm/commits/master/vta/tutorials/frontend/deploy_classification.py
To reproduce you can go back to d892881c4cc8c9a29bc03233aeac2b1532a9c6891 and the test passes.
Edit the config.cmake lines to run the VTA simulator:
echo 'set(USE_VTA_FSIM ON)' >> config.cmake
echo 'set(USE_LLVM llvm-config-10)' >> config.cmake

Go to 3684a51728e929576c93ff9887ac23e1b51582de (this PR), and the test fails with the following stack trace:
Stack trace:
  [bt] (0) 1   libmxnet.so                         0x000000011a0e92b0 mxnet::Storage::Get() + 4880
  [bt] (1) 2   libsystem_platform.dylib            0x00007fff690495fd _sigtramp + 29
  [bt] (2) 3   libvta_fsim.dylib                   0x0000000136ad14d0 _ZZN4dmlc16ThreadLocalStoreIN3tvm7runtime16VTAWorkspacePoolEE3GetEvE4inst$tlv$init + 0
  [bt] (3) 4   ???                                 0x0000000137dd1494 0x0 +<PHONE_NUMBER>
  [bt] (4) 5   libtvm.dylib                        0x0000000131d09f3c tvm::relay::Interpreter::InvokePrimitiveOp(tvm::relay::Function const&, tvm::runtime::Array<tvm::runtime::ObjectRef, void> const&) + 3516
  [bt] (5) 6   libtvm.dylib                        0x0000000131d0824b tvm::relay::Interpreter::Invoke(tvm::relay::InterpreterClosure const&, tvm::runtime::Array<tvm::runtime::ObjectRef, void> const&, tvm::relay::Var const&) + 171
  [bt] (6) 7   libtvm.dylib                        0x0000000131d03481 tvm::relay::Interpreter::VisitExpr_(tvm::relay::CallNode const*) + 961
  [bt] (7) 8   libtvm.dylib                        0x0000000131d070f8 tvm::relay::ExprFunctor<tvm::runtime::ObjectRef (tvm::RelayExpr const&)>::InitVTable()::'lambda4'(tvm::runtime::ObjectRef const&, tvm::relay::ExprFunctor<tvm::runtime::ObjectRef (tvm::RelayExpr const&)>*)::__invoke(tvm::runtime::ObjectRef const&, tvm::relay::ExprFunctor<tvm::runtime::ObjectRef (tvm::RelayExpr const&)>*) + 24
  [bt] (8) 9   libtvm.dylib                        0x0000000131d05aaf tvm::NodeFunctor<tvm::runtime::ObjectRef (tvm::runtime::ObjectRef const&, tvm::relay::ExprFunctor<tvm::runtime::ObjectRef (tvm::RelayExpr const&)>*)>::operator()(tvm::runtime::ObjectRef const&, tvm::relay::ExprFunctor<tvm::runtime::ObjectRef (tvm::RelayExpr const&)>*) const + 255
Stack trace:
  [bt] (0) 1   libmxnet.so                         0x000000011a0e92b0 mxnet::Storage::Get() + 4880
  [bt] (1) 2   libsystem_platform.dylib            0x00007fff690495fd _sigtramp + 29
  [bt] (2) 3   ???                                 0x0000000000000012 0x0 + 18
  [bt] (3) 4   libtvm.dylib                        0x0000000131e652ee void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, tvm::runtime::threading::ThreadGroup::Impl::Impl(int, std::__1::function<void (int)>, bool)::'lambda'()> >(void*) + 62
  [bt] (4) 5   libsystem_pthread.dylib             0x00007fff69055109 _pthread_start + 148
  [bt] (5) 6   libsystem_pthread.dylib             0x00007fff69050b8b thread_start + 15
Stack trace:
  [bt] (0) 1   libmxnet.so                         0x000000011a0e92b0 mxnet::Storage::Get() + 4880
  [bt] (1) 2   libsystem_platform.dylib            0x00007fff690495fd _sigtramp + 29
  [bt] (2) 3   ???                                 0x0000000000000012 0x0 + 18
  [bt] (3) 4   libtvm.dylib                        0x0000000131e652ee void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, tvm::runtime::threading::ThreadGroup::Impl::Impl(int, std::__1::function<void (int)>, bool)::'lambda'()> >(void*) + 62
  [bt] (4) 5   libsystem_pthread.dylib             0x00007fff69055109 _pthread_start + 148
  [bt] (5) 6   libsystem_pthread.dylib             0x00007fff69050b8b thread_start + 15
Stack trace:
  [bt] (0) 1   libmxnet.so                         0x000000011a0e92b0 mxnet::Storage::Get() + 4880
  [bt] (1) 2   libsystem_platform.dylib            0x00007fff690495fd _sigtramp + 29
  [bt] (2) 3   ???                                 0x0000000000000012 0x0 + 18
  [bt] (3) 4   libtvm.dylib                        0x0000000131e652ee void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, tvm::runtime::threading::ThreadGroup::Impl::Impl(int, std::__1::function<void (int)>, bool)::'lambda'()> >(void*) + 62
  [bt] (4) 5   libsystem_pthread.dylib             0x00007fff69055109 _pthread_start + 148
  [bt] (5) 6   libsystem_pthread.dylib             0x00007fff69050b8b thread_start + 15


Ring Central REST "Redirect URIs do not match"

I was hoping to use your OAuth2 Library to pull Ring Central call data for recording in my instance of Google BigQuery via Google Apps Script. To start, I added the library and used doGet to render a simple page to generate a token that I can start making calls with. On clicking Authorize, I get the following HTTPS response:
{   "error" : "invalid_grant",   "error_description" : "Redirect URIs do not match",   "errors" : [ {     "errorCode" : "OAU-109",     "message" : "Redirect URIs do not match"   } ] }
For Reference, My result from logCallback is this:
https://script.google.com/macros/d/[MY SCRIPT ID]/usercallback
Attached are my .gs files to get me this far.
OAuthTest.txt
OAuthLibrary.txt
Could you help me make this work? I'm sure you can tell I have practically no experience handling OAuth requests.
Thanks!

I've posed a sample for the RingCentral API, which I hope should help:
https://github.com/gsuitedevs/apps-script-oauth2/blob/master/samples/RingCentral.gs
This error usually indicates that you've registered the wrong redirect URI in the developer console. Double check that the value of "OAuth Redirect URI" in the RingCentral developer console matches the value that logRedirectUri() returns.

Thanks for Getting Back to me. Running the script did get me to an authorization prompt I hadn't reached before (image 1), and I logged in with my project credentials and my actual Ring Central User account, but was redirected both times to the following URL: https://script.google.com/a/macros/coordinationcentric.com/d/[My Project ID]/usercallback?error=invalid_request&error_description=OAU-144:Only+bot+extension+can+be+used+with+given+app+type
I can confirm that my project is currently set to expect OAuth Redirect URI https://script.google.com/macros/d/[MY PROJECT ID]/usercallback (image 2), which is what GAS is configured to put out (image 3).
Anything else I can try?

It looks like you selected Server/Bot for the platform type in the
RingCentral console, instead of Server/Web which is what you need.
On Tue, Jul 17, 2018, 3:51 PM Nathaniel-MacIver<EMAIL_ADDRESS>wrote:

Thanks for Getting Back to me. Running the script did get me to an
authorization prompt I hadn't reached before (image 1), and I logged in
with my project credentials and my actual Ring Central User account, but
was redirected both times to the following URL:
https://script.google.com/a/macros/coordinationcentric.com/d/[My Project
ID]/usercallback?error=invalid_request&error_description=OAU-144:Only+bot+extension+can+be+used+with+given+app+type
I can confirm that my project is currently set to expect OAuth Redirect
URI https://script.google.com/macros/d/[MY PROJECT ID]/usercallback
(image 2), which is what GAS is configured to put out (image 3).
Anything else I can try?
[image: screenshot 1]
https://user-images.githubusercontent.com/26629632/42841701-e5eb71de-89d8-11e8-8cc2-7bdd3f09c386.png
[image: screenshot2]
https://user-images.githubusercontent.com/26629632/42841535-634691d2-89d8-11e8-9155-ae465d68d7a9.png
[image: screenshot 3]
https://user-images.githubusercontent.com/26629632/42841644-b4b6544e-89d8-11e8-8d5d-9d4bf4a90d39.png
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/gsuitedevs/apps-script-oauth2/issues/129#issuecomment-405705850,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA8gmKvC0rwUYuobL54RZA3tv_L_xZpFks5uHkAngaJpZM4VRxDB
.

Got it. I recreated the app under "Web Browser," and now it accepts calls from my Apps Script Environment. You rock, Eric!


opae-sdk: remove ase sim build flag

Signed-off-by: anandaravuri<EMAIL_ADDRESS>

Coverage increased (+0.03%) to 65.516% when pulling 3310f0d93d75b54ba233c0686676f62829d4201f on aravuri/rm_ase_build into 2b8fcbfcf068518ad89442e65703fd5d915ac672 on master.

scripts/cover.sh: -DOPAE_BUILD_SIM=OFF scripts/unit-tests.sh: -DOPAE_BUILD_SIM=OFF
[Ananda]: removed in files cover.sh and unit-tests.sh:


honor supportedTargets in pxt.json

Ignore if missing, otherwise must be part of the list

fixed by https://github.com/microsoft/pxt-mkc/commit/ef5b2e51f21efe7267ebc04298e3f21c150dd3bb


Couple the constructor params of already updated classes

I checked how it looks in CodeLense of VSCode. Seems fine to me. From my perspective, we can go ahead and do this for everything we touch. But as mentioned already, I wouldn't necessarily revisit everything we have already touched just for this. But it definitely makes sense for things we touch anyways.


Excluding a hostname

I tried setting up a renewal for all host names of a site, except one. So I choose M: Create new certificate (full options) and 2: All bindings of an IIS website and choose the website. Then I get the choose to exclude host names:
 1: www.somedomain.nl
 2: somedomain.nl
 3: www.some-domain.nl
 4: some-domain.nl

 Press enter to include all listed hosts, or type a comma-separated lists of exclusions:

My first intuation was to type just 1 to exclude that host name. That didn't work. From issue #572 I understood that I should not enter the number but the actual full hostname. I find this counter-intuitive, especially since you navigate everywhere with just typing one letter or entering a number.
But OK, then I tried with entering the full host name:
 1: www.somedomain.nl
 2: somedomain.nl
 3: www.some-domain.nl
 4: some-domain.nl

 Press enter to include all listed hosts, or type a comma-separated lists of exclusions: www.somedomain.nl

 1: somedomain.nl
 2: www.some-domain.nl
 3: some-domain.nl
 <Enter>: Default

 Select primary domain (common name): 1

 [INFO] Target generated using plugin IISSite: somedomain.nl and 2 alternatives

 Suggested FriendlyName is '[IISSite] www.somedomain.nl', press enter to accept or type an alternative:

That seems to work better except that for the FriendlyName it still suggest a name that includes the host name that I just excluded. That seems like a bug to me.

Just realize that the suggested name for the FriedlyName is based on the actual website name of the website in IIS. So never mind that. But I would still like to suggest that instead of excluding host names by typing the names, it should (also) be possible to exclude them just by the number.

That would be a nice little usability improvement indeed.

Included in the 2.1.2 release


JWT signature url and sub are mismatching

Setup overview

Steps:

Trigger background job in NextJS with the following code:

const WEBSCRAPER_URL = "https://backend.my-domain.com/webscraper";

const result = await startBackgroundJob(
      'myJobName',
      { ...payload },
      { urlOverride: WEBSCRAPER_URL }
);

// The above function summarized:
const startBackgroundJob = async (jobKey, payload, options) => {
  const url = options.urlOverride ?? `my-domain.com/api/jobs?jobkey=${jobKey}`
  const request = {
      url,
      body: payload,
      delay: options?.delay,
      contentBasedDeduplication: true
  };
  await queue.enqueueJSON(request);
}

// Full version of that same function
const startBackgroundJob = async (
  jobName: JobKey,
  payload: JobPayload,
  options?: {
    delay?: number;
    queueName?: string;
    urlOverride?: string;
  }
): Promise<JobResult> => {
  noStore(); // import { unstable_noStore as noStore } from 'next/cache';

  try {
    const url =
      options?.urlOverride ??
      new URL(
        `/api/jobs?job=${jobName}`,
        process.env.NODE_ENV === 'production'
          ? process.env.NEXT_PUBLIC_HOST_URL
          : process.env.TUNNEL_URL
      ).toString();

    const request = {
      url,
      body: payload,
      delay: options?.delay,
      contentBasedDeduplication: true
    };

    let qstashMessageId: string;
    if (options?.queueName) {
      const queue = jobClient.queue({
        queueName: options.queueName
      });

      const { messageId } = await queue.enqueueJSON(request);
      qstashMessageId = messageId;
    } else {
      // import { Client as JobClient } from '@upstash/qstash';
      const { messageId } = await jobClient.publishJSON(request);
      qstashMessageId = messageId;
    }

    return {
      success: true,
      message: `Messsage ID from QStash: ${qstashMessageId}`
    };
  } catch (error) {
    console.error(`Error starting job '${jobName}': ${error}`);
    return {
      success: false,
      error: `Error starting job '${jobName}': ${error}`
    };
  }
};

In the logs of that function I see the following:
iss: Upstash, sub: https://backend.my-domain.com/webscraper, url: https://backend.my-domain.com

So I invoked with domain.com/path, but somehow the URL that I have in the event in AWS Lambda is not the same:
# From the docs  https://upstash.com/docs/qstash/quickstarts/aws-lambda/python
url = 'https://{}'.format(event['requestContext']['domainName'])
decoded = jwt.decode(jwt_token, options={"verify_signature": False})
sub = decoded['sub']
if sub != url:
        raise Exception("Invalid subject: {}".format(sub))

Also when you just get a regular URL, so without a path, you will get a mismatch because one of the two has a trailing backslash. So with and without a path it won't work, the intended verify method that you have posted in the docs is my suspicion.

Hey @dejoma, your reference example seems to be archived and a bit outdated. I will make sure to update this all over our content.
To fix this issue, here are the necessary changes:

add the pathname to url in the handler

url = "https://{}{}".format(event["requestContext"]["domainName"], event["rawPath"])

strip "/"s from url and sub in the verifier function

    if sub.rstrip("/") != url.rstrip("/"):
        raise Exception("Invalid subject: {}".format(sub))


Add support for rendering LiveViews

This could make it a great playground for teaching LiveView. This will require two features on the Phoenix side:

The ability to sanitize HTML from LiveView side
The ability in Phoenix to spawn channels in remote nodes

Probably via a socket configuration here: https://github.com/phoenixframework/phoenix/blob/master/lib/phoenix/channel/server.ex#L26

Closing this one for now because, while the above is doable, there is still another huge open question, which is CSS, and at the moment I am not convinced the work and the limitations make it worth.
Plus there is also the issue that the client is in Livebook and it works only for certain LiveView versions while the notebook will install its own LiveView which may have another version. And the only way to address this is to tie those together, which will affect the notebook reproducibility.

I have some ideas when reading this issue.
I was thinking about rendering generic html and also liveviews. Maybe rendering it in an iframe is the solution for css.
And for this liveview versions - can it maybe be solved by using hot code reloading somehow - the 2 module versions running at the same time sounds like designed exactly for this problem.


improve performance

i wrote this to make as much sense as possible. however, it seems to be slow.
Benchmarks with koa-compose:
  1 middleware
  6263.00

  5 middleware
  6201.30

  10 middleware
  5620.48

  15 middleware
  5820.87

  20 middleware
  5815.40

  30 middleware
  5556.27

  50 middleware
  5417.80

  100 middleware
  4905.64

With<EMAIL_ADDRESS>  1 middleware
A promise was converted into a generator, which is an anti-pattern. Please avoid using `yield* next`!
  4674.86

  5 middleware
A promise was converted into a generator, which is an anti-pattern. Please avoid using `yield* next`!
  4246.33

  10 middleware
A promise was converted into a generator, which is an anti-pattern. Please avoid using `yield* next`!
  3886.12

  15 middleware
A promise was converted into a generator, which is an anti-pattern. Please avoid using `yield* next`!
  3549.33

  20 middleware
A promise was converted into a generator, which is an anti-pattern. Please avoid using `yield* next`!
  3108.21

  30 middleware
A promise was converted into a generator, which is an anti-pattern. Please avoid using `yield* next`!
  2565.69

  50 middleware
A promise was converted into a generator, which is an anti-pattern. Please avoid using `yield* next`!
  1931.79

  100 middleware
A promise was converted into a generator, which is an anti-pattern. Please avoid using `yield* next`!
  1316.32

With<EMAIL_ADDRESS>while changing yield* next to yield next:
  1 middleware
  4597.07

  5 middleware
  3645.16

  10 middleware
  2853.25

  15 middleware
  2405.67

  20 middleware
  2052.63

  30 middleware
  1646.47

  50 middleware
  1137.48

  100 middleware
  648.19

When is this going into Koa?  I know there's a branch for it now.

not any time soon. it pretty much destroys performance.

Thanks for fast reply.  Is there any other way to use async await in Koa now?

nope sorry.

added benchmarks if anyone would like to help

actually i'm going to open a PR in koa and see what people say


Can I install Vitis-AI tools without docker?

Hi, I am trying to use the repo in the cloud，but the cloud doesn't support install docker. Do you have any ideas to install the reop without docker？

Hi @Gang-Chen-China , Vitis AI packages are not distributed separately on a repo. Docker is required to run Vitis AI.


Virtual Component Groups in the Hierarchical Action List (2/2)

Pull Request Description

Put information about Virtual Component Groups in the Hierarchical Actions List.
https://www.pivotaltracker.com/story/show/181865548
Important Notes

This PR implements the subtask 2 of 2 in the "Virtual Component Groups in the Hierarchical Action List" task.
Note: the PR description does not include a screencast due to the changes in this PR not having any visual effect at this moment. The result of this PR's changes would be only observed in the Component Browser, but the Component Browser is not merged yet. As described in the task's Acceptance Criteria, the changes in this PR are currently only covered by tests.
Manual integration testing with the Engine showed that a response to an executionContext/getComponentGroups request is non-empty only after an executionContext/executionComplete message is received by the IDE. (See also a discussion on Discord.) This was not known by the IDE team or documented before, and the existing code was modified to take this into account. The protocol docs are expected to be updated by the Engine team.
A list of component groups looked up in the suggestion database is cached in the node searcher as an optimization.

[ci no changelog needed]
Checklist
Please include the following checklist in your PR:

[x] The documentation has been updated if necessary.
[x] All code conforms to the
Scala,
Java,
and
Rust
style guides.
All code has been tested:

[x] Unit tests have been written where possible.
[x] If GUI codebase was changed: Enso GUI was tested when built using BOTH
./run ide dist and ./run ide watch.

Mateusz, can you include the screencast in the PR description or add an information why screencast is not needed, please?

@wdanilo done!

I did not check the logic. If @farmaazon is OK with it, we can merge it :)

(Process note: the code-review is now Approved, therefore the PR is waiting for an Acceptance/QA Review by @farmaazon  on Task https://www.pivotaltracker.com/story/show/181865548 before merge.)


Add updateThesisProgress

Coverage decreased (-0.5%) to 58.293% when pulling 1f750478eb75ba073bcdfb8f8bbd45b58967667d on jsdoc into 935de1d57bad021d100add1c018113f4c40351a3 on master.


[target=_blank] to external websites vulnerability

We're using [target=_blank] which has a vulnerability (https://mathiasbynens.github.io/rel-noopener/)

https://github.com/alphagov/static/blob/caac6ba9a5768957c22f6440ea01bf865100db55/app/assets/javascripts/surveys.js#L12

This has been fixed in government-frontend with the following PR alphagov/government-frontend#217

Thanks a lot @h-lame 🎉  👍  💃


create docker container registry

As Etienne mentioned in the telegram group, we need a docker container registry (here on github, on dockerhub, ...), where the built images can be uploaded to.
Afterwards we have to change https://github.com/RoboCupAtHome/Simulation-OPL-TiaGO/blob/main/docker-compose.tiago.yml#L15
Optionally we can automatically build images via github actions.

You can inspire by this workflow if you want to push on github registry : https://github.com/EtienneSchmitz/ros-devcontainer-vscode/tree/master/.github/workflows.
You need to change only this line : https://github.com/EtienneSchmitz/ros-devcontainer-vscode/blob/31b6a82b5fc5cee504ae1ef4d81dbc2f5beecf5a/.github/workflows/docker-publish.yml#L18

I will handle it tommorow !

https://github.com/RoboCupAtHome/Simulation-OPL-TiaGO/pkgs/container/simulation-opl-tiago


Optimize the WFA proofs.

These proofs work using fewer states (and the weights should not be worse).
Diff is a bit bigger than necessary due to reordering. I'll try to regen using "-cores 1" if this comes up again...

I was able to improve the helixes further by shifting where I was using weights.
I want to do this in a less intrusive way, since the 1=dead states were there on purpose.


Tweet whenever a new app is published

Not sure if it should be from our account or a new account, but it would be rad if we automatically tweeted out the AppCenter link whenever a new app was published.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Is this still something we want to do? We can set up a GitHub action to create an RSS feed for new releases. That's probably the best way to do this.


EventEmitter and stampit object

What is the best "stampit" way to mixin stamp with node EventEmitter ?
I tried using convertConstructor feature, but resulting object doesn't works properly

We have an example of using EventEmitter with convertConstructor here.
There is also stampit-event-bus as an alternative.

There was a similar problem a while ago. https://github.com/stampit-org/stampit/issues/148
The issue was that with node 0.12 they introduced the init() static function to the EvenEmitter class which collides with stampit's init() static method.
@eddyLazar can you show us your error?

It seems i've been using some other emitter library, with node 'events' everything works properly. Thanks for reply.


chore: peer dep adjustments

Current dependencies on/for this PR:

main

PR #2388   👈

This comment was auto-generated by Graphite.


jt.mean produces computation results with insufficient floating point precision

A simple testing code example
import jittor as jt
# create a tensor
arr = jt.ones((1, 3, 20, 20))
# 1st case
arr.mean()  # expect to get 1, but not in reality
# 2nd case
arr.mean(dims=[0, 1]).mean(dims=[0, 1]) # expect to get 1, but not in reality
# 3rd case
arr.data.mean() # expect to get 1, and get 1 in reality. However, grad information is removed

screenshot of the above example

This may be a bug in jittor, and it has brought inconsistent results with numpy or pytorch in terms of SSIM metrics.

The above results may be due to the IEEE floating representation.
However, when arr has shape [1, 3, 321, 481], jt.mean(arr) offers unexpected results with error ~4.3e-3 as shown below.

Same result in my case, which leads to imprecise SSIM.


Tailwindcss Integration

Is your feature request related to a problem?
Discussion is here https://github.com/kodadot/nft-gallery/discussions/8066
Describe the solution you would like

Integrate Tailwindcss
Use it for some small components like Checkbox or Button

Describe alternatives you have considered
--
Screenshots
No response
Are there opened related issues?
No response

cc @roiLeo @preschian do you have any suggestions/questions?

lmk if any clarifications needed

lmk if any clarifications needed

To make things easier, we might need to have a components page on Figma with the detail of our Design system.

do you have any suggestions/questions?

put component in extenal package (libs/ui), no business logic inside, vue3, make a preview of the component inside package (Story with different params) and that would be nice!

👋

Hi @exezbcz, do you have a figma file with a color palette?

@shashkovdanil hello hello, yeah, its now added into the handoff file

https://www.figma.com/file/JXNtryaNYhY0XJNArzvPQx/Handoff?type=design&node-id=5311%3A18771&mode=design&t=5BXhDaQFMuwQI7wZ-1


Xcode 10 Carthage compile error

JGProgressHUDIndeterminateIndicatorView.m:17:97: error: use of undeclared identifier 'UIActivityIndicatorViewStyleLarge'
activityIndicatorView = [[UIActivityIndicatorView alloc] initWithActivityIndicatorStyle:UIActivityIndicatorViewStyleLarge];
Please make sure all iOS 13 specific calls/variables/constants are in available(iOS 13, *) tests.

I updated the tag for v2.1. It should work now if you do a clean install with Carthage.


[abseil] update to 20230125.3 version

Protobuf >= 23.0 will require Abseil 20230125.3 or higher.

[x] Changes comply with the maintainer guide
[x] SHA512s are updated for each updated download
[x] The "supports" clause reflects platforms that may be fixed by this new version
[x] Any fixed CI baseline entries are removed from that file.
[x] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

The failures on arm64_windows look unrelated, download errors:
Downloading https://vcpkgassetcacheeastasia.blob.core.windows.net/cache/0daf2748948b963a17865908c469976a55f1f53af57ba79f534191a613f900ab07e1149c351c26e24e2b8e4e73e1f1c16e263d10e1384d31484ee92452dcb7e2?*** SECRET ***
Downloading https://download.qt.io/archive/qt/6.5/6.5.1/submodules/qtactiveqt-everywhere-src-6.5.1.tar.xz
error: Failed to download from mirror set
error: https://vcpkgassetcacheeastasia.blob.core.windows.net/cache/0daf2748948b963a17865908c469976a55f1f53af57ba79f534191a613f900ab07e1149c351c26e24e2b8e4e73e1f1c16e263d10e1384d31484ee92452dcb7e2?*** SECRET ***: failed: status code 403
error: https://download.qt.io/archive/qt/6.5/6.5.1/submodules/qtactiveqt-everywhere-src-6.5.1.tar.xz: failed: status code 403

/azp run

Rebased to give the builds another chance.  All looks good now.


chore(FDS-376): [Cascara] - Some official custom prop types

Export custom prop types
New Component Checklist

[x] Includes unit tests for ALL required FDS use cases
[x] Does not mute any top level API props in React
[x] Includes an explanation for any changes to Jest snapshots (should be a PR tag automatically added if this happens)
[x] Component uses React.forwardRef() when a single DOM node is returned, AND it makes React-sense to access that DOM node

@rociobaena @lordpixel I think there is some confusion around what this ticket is about. This is not about us consistently exporting all of the type shapes from our components (though that is I think something we should be doing to help ourselves outside of Cascara). This ticket is about creating custom prop types for use when defining types on a component. Basically we want to extend what prop types are available for building types. I will expand on this in the ticket itself. I thought it was going to be clear what our use case was with the code example on the ticket... but when I look at it now, I can see why it is not clear. Sorry!

@rociobaena When there is a PR we put up that we are just getting feedback on, we can set the PR as a draft in Github. Please go ahead and do that with this one so we know it is not supposed to be merged yet.

This implementation was not no the expected one. Declining this in favor of https://github.com/Espressive/cascara/pull/312 instead.


Update restify to 4.3.0

Update needed for nodejs8 image update in the ch06 lab.

can we test if this is backward compatible with the 4.1 instructions and cluster?

I checked those changes, and those are backwards compatible with node:6 (and hence with DO288-OCP4.1).
Some evidence:


operator mariadb-operator (0.31.0)

Added operator mariadb-operator (0.31.0)

/pipeline restart operator-hosted-pipeline


Auto-connect extra choice: auto-mirror

Hi, I use escrcpy with USB cable (since wifi 2.4 and 5Ghz  video stream always lags and stops after some seconds),
but USB cable works wonderful, realtime and with perfect audio.
Would it be possible to have a setting to auto-mirror when I connect the phone with USB cable to my Linux computer?
It would be wonderful to have an option to automatically display the screen just after the phone is connected, since I often switch around 2 phones via USB-cable to make them display on my TV, however I am always having to interact with the computer to manually run the mirroring.
I could not find this setting in escrcpy, besides the auto-connect.

v1.17.6 Supported auto-mirror


build: flatten monorepo

this looks good to me, files in /public are being served correctly too.
next step is to nest explorer inside th react application right?

@stphnnnn that's certainly needed, there are a couple of other issues remaining too.
You can see the state of things in the project: https://github.com/neontribe/gbptm/projects/7


Unable to search files on mapped network drives

Environment
Windows build number: Microsoft Windows [Version 10.0.18363.836]
PowerToys version: v0.18.1
PowerToy module for which you are reporting the bug (if applicable): PowerToys Run

Steps to reproduce

Open PowerToys Run
Search for files you know to be located on mapped network drives.

Expected behavior
Files located on mapped network drives should appear in the search results.
Actual behavior
Files located on mapped network drives do not appear in the search results.  Please note that search for all local files is working as intended.
Screenshots

Related to #3976

Related to #3975

at end of the day, this is issue https://github.com/microsoft/PowerToys/issues/2041.  If the drive isn't indexed, we can't search it

at end of the day, this is issue #2041. If the drive isn't indexed, we can't search it

Right, but it seems there is no way to manually index said drives through control panel, and I also insured that I checked "Allow files on this drive to have contents indexed in addition to file properties" so you'd think they would be indexed due to this checkbox.  Following #2041 now


appropriate Python tool/method to integrate IMU data with my existing code

I am implementing an algorithm for object pose estimation, where position is estimated by a camera+Tag system, and orientation is fused using the camera+Tag and IMU orientation reading.
I already have the python code for computing position and orientation through a camera + Tag system , as well as the sensor fusing algorithm.
My question is about the best approach to integrate IMU data reading into my existing setup for object pose estimation.
One idea is to send out the orientation through sockets, and use a different python file to read the real-time data, but I am encountering some issues. Not sure what the best approach is.
Any suggestions would be appreciated! Thanks!

I'm struggling to understand this post.  Did you mean to post in this repository?  Are you using an x-IMU3 or the x-IMU3 Software?

I am using both x-imu3 sensor and the software. I wasn't sure what the best way to integrate the sensor reading to my existing python framework. But I just found using threading and maintaining a few global variables is a good option for me.
Thank you for getting back to me, and if you have other suggestions, please let me know.


How do we get an Evaluation Lab environment?

My assumption is we need to start with a free trial first?

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

ID: 12e5744d-46dd-7f90-e42e-70caf9dd56d2
Version Independent ID: 1a627400-9585-e482-3820-e58f6c172a87
Content: Microsoft Defender ATP evaluation lab
Content Source: windows/security/threat-protection/microsoft-defender-atp/evaluation-lab.md
Product: w10
Technology: windows
GitHub Login: @mjcaparas
Microsoft Alias: macapara

@officedocsbot assign @mypil

@cw123williams - Thank you for submitting feedback.
I will get this issue over to the Win10 ITPro writing team for investigation.
Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

Dear @cw123williams , evaluation lab is a part Windows Defender ATP, sot the requirements are the same: Minimum requirements for Microsoft Defender ATP
My assumption is we need to start with a free trial first? - yes, sure, you just need to get WD ATP free trial
Thank you

@cw123williams - From our understanding, the issue you raised has been answered by MaratMussabekov. If you feel it hasn't been answered, please re-open this issue.
Thank you for your contribution to make the docs better! Much appreciated!

@officedocsbot close


Handle invalid wrangler.toml files

What this PR solves / how to test
Handle non-Pages wrangler.toml files better. This PR ensures that wrangler pages functions build-env and wrangler pages functions build fail fast with the appropriate error message if a non-pages wrangler.toml file is found. This ensure that config validation isn't run, which was inadvertently throwing errors for non-pages wrangler.toml files.
Fixes #[insert GH or internal issue number(s)].
Author has addressed the following

Tests

[ ] TODO (before merge)
[x] Included
[ ] Not necessary because:

Changeset (Changeset guidelines)

[x] TODO (before merge)
[ ] Included
[ ] Not necessary because:

Public documentation

[ ] TODO (before merge)
[ ] Cloudflare docs PR(s): https://github.com/cloudflare/cloudflare-docs/pull/...
[x] Not necessary because: Not yet documented

And don't forget the changeset...


Invalid language tests - reference name "v" in "v" variable initializer

language/block_scope_test
language/lazy_static3_test
It is a compile-time error if e refers to the name v or the name v=.

The spec has changed so that local variables are in scope for the entire block that they are declared in, and so that a reference to a variable before the end of its initializer expression is a compile-time error.
The tests seem OK.  language/block_scope_test was either deleted or renamed.  The similarly-named language/scope_variable_test seems OK.


__typename always String for mutations

I noticed that while pg_graphql returns the correct typename for queries, it doesn't seem to work for mutations yet.
Example:
mutation insertAuthor {
  insertIntoAuthorCollection(objects: [{ name: "John Doe" }]) {
    __typename
    records {
      id
      name
      __typename
    }
  }
}

{
  "data": {
    "insertIntoAuthorCollection": {
      "records": [
        {
          "id": 9,
          "name": "John Doe",
          "__typename": "String"
        }
      ],
      "__typename": "String"
    }
  },
  "errors": []
}

Versions:

pg_graphql 0.1.5

This likely wont get an off-cycle release so it may not hit production for a week or so. If you send me your project ref I'll update it in your db

@olirice No hurry. Thanks for the fix!


Change Addin Name + Version

#61 -
ProSymbolEditor -> MilitarySymbolEditor
0.1.0 -> 1.0.0

Assigning to @tlauver to verify (and note the new addin name).
After the merge - I'll fix register script in https://github.com/Esri/military-tools-for-arcgis & work with @ACueva to fix anything the might break in the autobuild as a result (last bullet in #61).


Setup all CI jobs

Setup all CI jobs: build, verify, etc.
We should wait until this merges https://github.com/kubernetes/test-infra/pull/24768
/hold

/retest

/unhold

Are we planning to resolve the apidiff issue separately?

@JoelSpeed Yes, I will make a follow up

/approve

@elmiko make test-junit is expected to fail if you don't have _artifacts directory, and thanks for finding issue with lint task, I pushed a fix


re-worded site-entry spec

i think it is more clear about which parameters are needed for what parts

I agree.


Game of Life example doesn't work with latest fasthtml

I was trying to get the Game of Life example to work with the latest fasthtml but I couldn't.
I was getting 400 errors. It turns out that hx-vals seem to be messed up.
As the code hasn't changed in 4 weeks, it must have been a breaking change in fasthtml?
Relevant line:
https://github.com/AnswerDotAI/fasthtml-example/blob/bdd4cc2257cf3c641e158ab23e83ab090d7c090a/00_game_of_life/main.py#L47
This is the html as produced by the working example (probably using old fasthtml):

This is using latest example and fasthtml locally:

Note that hx-vals arg is not valid JSON anymore! If I substitute  hx_vals=json.dumps({'x': x, 'y': y}) then things work again.
So 2 options:

A) This was an intentional breaking change. Then example needs to change
B) This is unintentional, a bug.

@ncoop57 any chance you could take a look?

This was fixed with #288 - just confirmed with v0.3.6! Thanks @jph00.


Remove the boolean flag from ArmeriaMessageDeframer.deframe()

Motivation:
ArmeriaMessageDeframer.deframe(HttpData data, boolean endOfStream) does not have to take endOfStream flag
because the HttpData has endOfStream flag.
Modifications:

Remove the boolean flag from ArmeriaMessageDeframer.deframe().

Result:

ArmeriaMessageDeframer.deframe() now takes HttpData only.

This could allocate an extra instance when the flag is different so let me close this. 🤣


fix: allow button to be clicked in React with IE11

Alaska Airlines Pull Request
Summary:
When used in a React application in IE11, the button was not responding to clicks. Adding a no-op click handler on the button within the component fixed the issue and does not appear to have any negative side effects in a non-React environment.
Tested on Polymer demo page and in OrionReactDemo in Firefox, Chrome, and IE11.
Type of change:
Please delete options that are not relevant.

[x] Revision of an existing capability

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Orion Design System Team

@blackfalcon The package-lock change only increments the version of ods-button from 4.0.0 to 4.1.0. Does this change need to be reverted?

@geoffrey1218 I think it will be fine ... it's just weird that it happened? Not critical. Approved to merge.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


fix(oci): clean dead code

Referring to the issue #281
Helmfile supports the OCI format but executes the helm pull command twice, resulting in :

slow down the use of Helmfile when using multiple registries supporting OCI format
impact the possible rate limits of a registry

How

deletion of a "pull chanel" which never really used as the destination path isn't shared with the other commands (like the template command)
separation of concerns about chartPull and chartExport

@jycamier Please fix DCO issue.

ping

@yxxhero Fixed the conflict in fd786c0. I believe this is good to go once the CI build passes.

@mumoshu yes. I think so.

Your welcome @mumoshu. This is my first golang contribution 🍼


[Bug] upgrade to jackson-databind <IP_ADDRESS> (due to cve)

What happened
dependabot alert
https://github.com/advisories/GHSA-57j2-w4cx-62h2
only jackson-databind has a <IP_ADDRESS> release - other jackson jars should be upgraded to 2.12.6
What you expected to happen
n/a
How to reproduce
n/a
Environment
No response
InLong version
master
InLong Component
InLong Manager
Are you willing to submit PR?

[ ] Yes, I am willing to submit a PR!

Code of Conduct

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

Did anyone else start dealing with it? If not, I'll upgrade this component

I added https://github.com/apache/incubator-inlong/pull/3570


datetime field in filters does not trigger listView update when value changed

datetime field in filters does not trigger listView update when value changed.
Both when press enter or when a date is picked.

Update:
Found that it was actually caused by Me Myself using '$' as the field name for those 'gte', 'lte', 'lt' , 'gt' staff ...

You can close this issue ;).


Making debug command test target in sync

What is the purpose of this change? What does it change?

Test target execution method should be in sync with other test target
Was the change discussed in an issue?
No

How to test changes?

make test-cmd-debug

/lgtm
/approve


Read alltypes_plain.parquet

This is a test file in data folder, need to make sure library can handle it and make mods if necessary.

all done!


how can i use only pagination with my table content (not using entire clr-data)grid

Summary
Summary the request and address the questions as appropriate.

What is the change?
Why should it go in Clarity?
Does this change impact existing behaviors? If so how?
If this change introduces a new behavior, is this behavior accessible?

Use case
Provide some specific details about how this change would improve your application and use case.
Examples
Are there any examples in other projects that demonstrate this feature or enhancement?
Workarounds
Is there a workaround for this feature at the moment, even if it is less than ideal?

Clarity doesn't offer a stand alone pagination component. There is an open issue for it here: https://github.com/vmware/clarity/issues/2268 but at this time its not currently prioritized by the team.
Please subscribe to that issue and leave any relevant feedback on there.

Thank you for quick replay.
is there any way to implement in grid first three column and last column fixed with horizontal scroll to scroll intermediate five column in clarity data-grid.


Log window autoscroll turn off trigger

@AlehFiliutsich Care to give more details? A description would not kill anybody.