Blank Screen appearing after installed sqltools

Not able to load the screen, v0.22.10
Kindly help me!!!

What’s the error message you got on bottom-right?
Also try to check there errors using Open Webview Developer tools from
command palette. This issue as is I don’t know what to say to you
On 29 June 2020 at 11:14:03, sathishkumarkevin<EMAIL_ADDRESS>wrote:
[image: image]
https://user-images.githubusercontent.com/25504642/86016677-bbd20d00-ba40-11ea-9082-ca9e298334d5.png
Not able to load the screen, v0.22.10
Kindly help me!!!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mtxr/vscode-sqltools/issues/639, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFMX2KDBQLHEMXVNCGFDC3RZCOSVANCNFSM4OLIJFRQ
.

I also suddenly got this issue this morning; I'm able to connect to the database just fine it seems. When running a query, the Console Messages says "Not focused to results view," and the SQLTools Results pane is blank.  The webview developer tools shows this.

Any of you are using VSCode insiders?
On 29 June 2020 at 11:14:03, sathishkumarkevin<EMAIL_ADDRESS>wrote:
[image: image]
https://user-images.githubusercontent.com/25504642/86016677-bbd20d00-ba40-11ea-9082-ca9e298334d5.png
Not able to load the screen, v0.22.10
Kindly help me!!!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mtxr/vscode-sqltools/issues/639, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFMX2KDBQLHEMXVNCGFDC3RZCOSVANCNFSM4OLIJFRQ
.

I use the stable VSCode build.

@mgipson @sathishkumarkevin which vscode version are you using exactly?
Switching back to SQLTools v0.22.9 fixes the issue?
I'm afraid this change https://github.com/mtxr/vscode-sqltools/commit/284f44e8427919531509caa88abe93971f0b8714#diff-6e8ca5e7fbf8398ee9f0c5f170f4f66aR64 is breaking on some VSCode versions.

@mgipson @sathishkumarkevin which vscode version are you using exactly?
Switching back to SQLTools v0.22.9 fixes the issue?
I'm afraid this change 284f44e#diff-6e8ca5e7fbf8398ee9f0c5f170f4f66aR64 is breaking on some VSCode versions.

I am using 1.46.1. How i can revert to SQLTools v0.22.9 version ?

Any of you are using VSCode insiders? On 29 June 2020 at 11:14:03, sathishkumarkevin<EMAIL_ADDRESS>wrote: [image: image] https://user-images.githubusercontent.com/25504642/86016677-bbd20d00-ba40-11ea-9082-ca9e298334d5.png Not able to load the screen, v0.22.10 Kindly help me!!! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#639>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFMX2KDBQLHEMXVNCGFDC3RZCOSVANCNFSM4OLIJFRQ .

I am not using insiders.

I am using 1.46.1 as well.

Try this:
Let me know how it goes.
On 29 June 2020 at 11:16:54, Matheus Teixeira<EMAIL_ADDRESS>wrote:
What’s the error message you got on bottom-right?
Also try to check there errors using Open Webview Developer tools from
command palette. This issue as is I don’t know what to say to you
On 29 June 2020 at 11:14:03, sathishkumarkevin<EMAIL_ADDRESS>wrote:
[image: image]
https://user-images.githubusercontent.com/25504642/86016677-bbd20d00-ba40-11ea-9082-ca9e298334d5.png
Not able to load the screen, v0.22.10
Kindly help me!!!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mtxr/vscode-sqltools/issues/639, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFMX2KDBQLHEMXVNCGFDC3RZCOSVANCNFSM4OLIJFRQ
.

I think there's an image missing there; the message is mostly blank.

Sorry, Didn't upload from email

Yeah its working after i rolled back Thanks!!!

Reverting to v0.22.9 worked; thank you!

Don't close yet. We still need to get it fixed

get the same issue,
VSCode Version: 1.46.1
SQLTools Version: 0.22.10

SQLTools version 0.22.9 works perfectly, but same error log still appear

Can someone work on this?
I'm pretty busy this week, I can't get it done before the weekend.
Here is vscode guide for webviews: https://code.visualstudio.com/api/extension-guides/webview
and here is where we setup the resources for webviews: https://github.com/mtxr/vscode-sqltools/commit/284f44e8427919531509caa88abe93971f0b8714#diff-6e8ca5e7fbf8398ee9f0c5f170f4f66aR64
We need to test this on past 3 versions, because VSCode had some webview issues on v1.47 insiders.

Reverting to v0.22.9 not work
VSCode 1.47.0

Any of you are using VSCode insiders? On 29 June 2020 at 11:14:03, sathishkumarkevin<EMAIL_ADDRESS>wrote: [image: image] https://user-images.githubusercontent.com/25504642/86016677-bbd20d00-ba40-11ea-9082-ca9e298334d5.png Not able to load the screen, v0.22.10 Kindly help me!!! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#639>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFMX2KDBQLHEMXVNCGFDC3RZCOSVANCNFSM4OLIJFRQ .

Just subscribe to be an insider. Was this issue resolved on a VSCode insider forum?

Sorry, Didn't upload from email

This seems to work for me, I can now connect to my Database. I went back to two versions.

This works, but I hope a permanent fix is found, as you can see I am being asked to upgrade versions.

Thanks @mtxr I upgraded and the problem is now resolved. I was able to insert data into my database.


Less verbose test suite

Add DumpDirOnFailre() to only print directory structure on failure.
Remove some extraneous logging from the test suite.

Test flake would be fixed by #1911

Restarted appveyor, let's see :)

Codecov Report

Merging #1917 into master will decrease coverage by 0.1%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1917      +/-   ##
==========================================
- Coverage   47.29%   47.18%   -0.11%
==========================================
  Files          89       89
  Lines        8830     8852      +22
==========================================
+ Hits         4176     4177       +1
- Misses       3968     3983      +15
- Partials      686      692       +6

Flag
Coverage Δ

#linux
50.44% <ø> (-0.23%)
:arrow_down:

#windows
42.07% <ø> (-0.18%)
:arrow_down:

Impacted Files
Coverage Δ

filters/scanner.go
68.53% <0%> (-8.99%)
:arrow_down:

content/local/writer.go
55.26% <0%> (+5.26%)
:arrow_up:

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 03bc5e9...49fffe8. Read the comment docs.

LGTM

So, this was in place because not all problems with the filesystem layout result in a failure or can be detected this way...
Also, there were log items in the filters stuff that are extremely useful for debugging token state.
We should remove the -v flag from running tests if we want to get rid of these logs. One should not have to worry about their debugging statements getting removed all the time.

As far as I know, there is no way to print the test names but also hide the verbose test output, which I think should be output of running a test suite.
If there is information that is valuable for debugging failures it should be in the error message from t.Errorf() or t.Fatalf(), right?

As far as I know, there is no way to print the test names but also hide the verbose test output, which I think should be output of running a test suite.

Why do we need the test names to be output? On failure, the relevant log lines get printed.

If there is information that is valuable for debugging failures it should be in the error message from t.Errorf() or t.Fatalf(), right?

There are details about a test run that may not have to do with failure. Not everything can be tested and there may be bugs that are in the test or part of a run that may only be available when logged. They may also inspire a new test ("Ah I see that the mtime is like this, so let's make sure that's tested at the end").
These are only output when the test fails, so shouldn't be a nuisance. Post run file system state is extremely important and being able to see that after a snapshotter run is great training for when there actually is a problem.

As far as I know, there is no way to print the test names but also hide the verbose test output, which I think should be output of running a test suite.

Why do we need the test names to be output? On failure, the relevant log lines get printed.

From my POV:
It's useful to know which tests has been run beforehand or were in the process to be run when a test fails. Also, it helps knowing that the whole thing is just not deadlocking without waiting for the overall test suite timeout to kick in.

Why do we need the test names to be output?

Because it is the only confirmation that any tests have actually run. go test might have been called with the wrong args, or maybe a test was accidentally written as testFoo, or Testfoo. Or every test may have been skipped. You may have run 0 tests without even knowing it. If go test printed a summary of total tests run/skipped/failed it wouldn't be as necessary to print the test names.

Not everything can be tested

Can you provide an example of something that can't be tested?

and there may be bugs that are in the test or part of a run that may only be available when logged.

How does logging it make it easier to spot than testing the value and having a computer tell you when it's wrong?

Post run file system state is extremely important and being able to see that after a snapshotter run is great training for when there actually is a problem.

If it's important it should be tested against an expected value. How is visual inspection a better mechanism for detecting errors than an automated test?


Provide better support for UiAutomator

Internal: b/131923608
cc @mehmetf
cc @jonahwilliams
Not sure how much is possible here, but it's a little bit difficult to use UiAutomator with Flutter. Of particular difficulty is the fact that there's no way to provide any sort of identifier for finding elements. With Android Framework development, you can use resource IDs, but there's no parallel with Flutter. Using UiAutomator is useful for testing inside Google because it's used by an internal testing framework that I expect most teams inside of Google will want to use.
Is it possible to create virtual resource IDs when turning the Flutter semantic tree into the Android view tree (my understanding of how things work)?

There is work ongoing right now to make Espresso work better with Flutter, both inside and outside of google3.  Would that suit your needs?
/cc @adazh @matthew-carroll

Hmm not entirely sure, though would probably guess not. I believe
UiAutomator works by targeting elements using the accessibility layer and
Espresso works by [1] targeting elements in the view layer.
IIRC espresso has more direct access to the actual view hierarchy. I don't
believe the view hierarchy is the same as what's produced by the Flutter
accessibility bridge, which populates sort of a virtual view hierarchy
through the accessibility nodes.
[1] Take my espresso assumptions for a grain of salt since I'm not super
familiar with Espresso.
On Sat, May 4, 2019, 8:26 PM Dan Field<EMAIL_ADDRESS>wrote:

There is work ongoing right now to make Espresso work better with Flutter,
both inside and outside of google3. Would that suit your needs?
/cc @adazh https://github.com/adazh @matthew-carroll
https://github.com/matthew-carroll
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/32062#issuecomment-489385573,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAQ7IZ42EVWBXSLIMWVBLI3PTZHXTANCNFSM4HKXDSRA
.

Part of the work for espresso is making sure we can make these things accessible to testing frameworks, including the semantics tree.  I think @goderbauer knows the bug tracking that bit he's out this week.  I'll try to dig it up

Sounds good. Just to be clear, I'm seeing things visible in the testing framework. It's just hard to access specific elements.
BTW, I forgot to mention that I saw this line (JavaDoc) which appears might be used to set the resource ID, but it's always set to an empty string: https://github.com/flutter/engine/blob/7ce2666e54cb137f35b62950b32b8db80d5027e6/shell/platform/android/io/flutter/view/AccessibilityBridge.java#L516

As Dan described, we are working on making Espresso work with Flutter UI as the way it does with Android UI (analogous to Espresso-Web).
@alanrussian Mind elaborating more on your testing scenarios?
Like how your test flows would look like; what Flutter UI widgets you are interested in interacting with, and how. A (hypothetical) example test case/scenario would be very helpful. Thanks!

Here's something we're trying to do right now in one of our UiAutomator driven tests:

Scroll down on a page to find a ListTile. Tap on it.
Tap on an icon button in the app bar.
Type into a text field (this is broken: #32063 but we have a workaround which doesn't require us to enter text for now).
Repeat step 1.
Tap on some text.
Repeat step 1.
Tap on some text.

However, this is just what we need to do right now. Different customers will obviously need to do different things.

Thanks! Let's chat more then. I'll set up something.

@dnfield @adazh I am interested in using UiAutomator to work with my flutter app and am having similar problems to what @alanrussian described 3.5 years ago. Of particular difficulty is the fact that there's no way to provide any sort of identifier for finding elements.
I am interested in what came of this discussion? I want to use Appium's UiAutomator to find elements on the screen and tap them. Can you help me?

It looks like https://github.com/flutter/engine/pull/48882 should have resolved that, although we may be missing widgets in the framework setting it appropriately....

What do you mean by we may be missing widgets in the framework setting it appropriately ? Are you referencing a bug ticket?

@bartekpacia - what's the status of the semantics identifier work? Is there more framework work left to do?

The work on semantics identifier is completed and is already available on master channel. It can be used like this:
Semantics(
  identifier: 'hello-world',
  child: Container(
    width: 100,
    height: 100,
    color: Colors.red,
  ),
)

PS#1 I think this issue is a duplicate (or a subset) of #17988.
PS#2 Actually @dnfield I have a question for you: how can I check whether these changes will be available in the next Flutter beta in Januray? Is this info publicly available?

The work on semantics identifier is completed and is already available on master channel. It can be used like this:
Semantics(
  identifier: 'hello-world',
  child: Container(
    width: 100,
    height: 100,
    color: Colors.red,
  ),
)

PS#1 I think this issue is a duplicate (or a subset) of #17988.

I agree. However, the part I'm still not clear on is whether we need to add some default identifiers to more framework widgets "out of the box". I suspect that we don't but it's not 100% clear to me.
@samdup123 I'm going to close this issue as a duplicate of #17988, and to be honest I think it's either resolved or mostly resolved (but you'll need to add the kind of code that @bartekpacia suggested above in places in your app where you want it to work).

PS#2 Actually @dnfield I have a question for you: how can I check whether these changes will be available in the next Flutter beta in Januray? Is this info publicly available?

Which commit is it? The first thing to check is whether that commit is part of 3.18, which is the beta that was cut in December. If not I'm pretty sure it'll be part of 3.19 in January :)

However, the part I'm still not clear on is whether we need to add some default identifiers to more framework widgets "out of the box".

No, we don't want to do that. It makes sense to make all the built-in widgets in core framework have sensible accessibility, but Semantics.identifier is an exception since it's only for UI testing.
It would only interfere with identifiers given by developers.

Which commit is it?

Mainly https://github.com/flutter/flutter/commit/948523b80c9cb9659153e13cd60a53a8cc254603 but all the PRs listed here also have to be released for this feature to work.
I see it's not on beta yet. Let's hope for January 🤞🏻


Default stage names

dev / prod for now, "stage" looks redundant with --stage stage etc haha so staying away from that.

development staging and production are the terms a few startups I've worked in use.

If given the choice, I believe most devs would prefer to type less 😉

Yeah for me dev is typically not an env since it's your machine, but I've been using the API Gateway term of "stage" in place of "env" so --stage stage is weird haha, --stage staging is definitely better

@lukeed yea that's how I feel too

case closed, dev/prod good enough for me haha

might change prod to production later specifically because it's large and annoying to type, could prevent some mishaps

I hate when I accidentally write dev as prod 😆
JK, I don't care either way 👻


[18.09 backport] Windows: Bump busybox to v1.1

backport of https://github.com/moby/moby/pull/38278 for 18.09. Cherry-pick was clean; no conflicts
This is a follow-on from https://github.com/moby/moby/pull/38277
but had to be done in a couple of stages to ensure that CI didn't
break. v1.1 of the busybox image is now based on a CMD of "sh"
rather than using an entrypoint. And it also uses the bin directory
rather than c:\busybox. This makes it look a lot closer to the
Linux busybox image, and means that a couple of Windows-isms in
CI tests can be reverted back to be identical to their Linux
equivalents.

ping @andrewhsu @kolyshkin PTAL

LGTM


Exception thrown when interacting with Player

Hello,
Everytime I try to interact with the Player in SpotifyClient.Player, I get some JSON exception. The error is always different, but always follows this pattern :
JsonReaderException: Unexpected character encountered while parsing value: M. Path '', line 0, position 0.
JsonReaderException: Unexpected character encountered while parsing value: n. Path '', line 0, position 0.
JsonReaderException: Unexpected character encountered while parsing value: O. Path '', line 0, position 0.
This appends either when I try to add a track to the queue, try to play/pause Spotify, try to skip to the next song,...
            PlayerAddToQueueRequest r = new PlayerAddToQueueRequest("spotify:track:" + track.ID);
            await spotifyClient.Player.AddToQueue(r);

await spotifyClient.Player.PausePlayback();
await spotifyClient.Player.SkipNext();
Am I doing something wrong?
Thank you

#980 (literally the only issue open)


Convert CallServerInterceptor to Kotlin

Convert CallServerInterceptor to Kotlin

It would be nice to see if we can simplify the logic to remove !! cases. Also the “close” checks might be worth pulling out into internal Request and Response receiver methods to make the code logic simpler.
Sent with GitHawk

@yschimke There are two places use !! statement which is safe because exchange.readResponseHeaders(false) never be null.
Wait until  Exchange.java be converted to Kotlin we can remove these !! case.


Document option syntax for adders, e.g. to use cli tailwind-adder with forms, typography, daisyui

What is the syntax for using an adder and its options?
For example, the Tailwind adder says it has options forms, typography, daisyui.
How to include these options in the typical new project command such as:
npm create @svelte-add/kit@latest app -- --with tailwindcss

Thanks!

Thanks for reaching out!
Indeed, this is currently not documented anywhere, not in the adder itself, nor in this repo.
But using this command seems to work for me locally. Do you mind checking it out?
npm create @svelte-add/kit app -- --with tailwindcss --forms

And for my future self, this seems to be the relevant code:
https://github.com/svelte-add/svelte-add/blob/cc097553c91f6150973c842707387e7b5aa73ece/projects/svelte-add/index.js#L177-L187
I'll leave that issue open for now, so that we can properly document this behavior!

Thanks for the quick reply.
What I'm seeking please is the syntax for using any adder and any of its options.
Suppose adder "a" has options "b" and "c", and adder "d" has options "e" and "f".
If I understand what you wrote above, is this the correct syntax?
npm create @svelte-add/kit app -- --with a --b --c --with d --e --f

If so, what's the process to add the syntax to the documentation?
When I try what you wrote, I'm not seeing how to run it as a test on a CI, such as with a before/after condition. Is there a testing process that I should be trying for the adders and their options?
Thanks!

Super, thank you so much. I never would've guessed that syntax. :-)
What I meant when I asked about test and CI, is approximately this... apologies in advance if you're already fully aware of what I'm about to write.

Some programs have ways to download the program, then run local tests to verify the program behaviors work correctly on the local machine. For example, there could/should be a way to use a test to verify that the command line is correctly setting up Tailwind, PostCSS, etc. such as by checking a before-condition (e.g. no files exist) and an after-condition (e.g. the appropriate config files exist and contain the expected code).

Some programs have ways to submit command lines to a remote testing service, such as a continuous integration service, or a sandbox service, which runs the commands, and does similar checking of a before-condition and after-condition.

I personally like these kinds of tests a lot, because I like learning from them. I can see what the tests expect versus any actual output, and in my experience it's often easier/clearer for me to understand the test code than the program code-- which may be much more complex.

I was asking if there are any tests like this, so I could read them and learn from them.

HTH. Thank you again for your fast response-- I am up and running now because of your help! 🚀

Great to hear, no problem for that :D
We still need to document that, but now that we have this issue, a lot of stuff is already done.

Ahh now I understand what you mean. Svelte Add currently has this feature in a way, but is currently not disposing this functionality publicly (as far as I'm aware at least.)
But after any adder was applied, svelte-add as it's own internal tests, to check what you suggest. Although some are pretty basic.
You will find them in the appropriate repos in the __info.js file. I have linked you the tailwindcss file in example:
https://github.com/svelte-add/tailwindcss/blob/4c0f7323faeea7c529b37056c370a1947bbf3c77/__info.js#L39


US919094: Release prep

https://internal.almoctane.com/ui/entity-navigation?p=131002/6001&entityType=work_item&id=919094

A developer build has not yet been created for this branch. Click here to go ahead and create the build...

CI Build Link:
https://sou-jenkins2.swinfra.net/job/FileAnalysisSuite/job/FileAnalysisSuite~adaptersdk-schema~US919094~CI


Cold wallet functionality

CLI should support cold wallet functionalities which means it should support offline operation for:

signing transactions,
signing account creation,
contract deployments

All these and more operations will be necessary for all future exchanges and similar businesses.
Implementation should support passing values needed for offline signing as arguments (such as last sequence number, keys etc).

Not important or priority as discussed with Kan


Added an optional upper limit to the numbers of items

I've updated to the adapter common 0.2. I added support for hierarchy. I did also fix https://github.com/php-cache/issues/issues/20 by adding an optional upper limit for the numbers of items in the cache.
Ping @andrerom does https://github.com/php-cache/array-adapter/commit/51ec6fcca417a3216ff9f399769da5e8f0cae68f fix your issue?

Current coverage is 100.00%

Merging #4 into master will not affect coverage as of 51ec6fc

@@            master      #4   diff @@
======================================
  Files            1       1
  Stmts           16      42    +26
  Branches         0       0
  Methods          5       7     +2
======================================
+ Hit             16      42    +26
  Partial          0       0
  Missed           0       0

Review entire Coverage Diff as of 51ec6fc

Powered by Codecov. Updated on successful CI builds.

Think so, can't wrap my head around the current position logic right now with a hangover, but the tests are as I would expect so +1


StatsD - Target .Net Standard 2.0

I'm using the StatsD monitoring package (Akka.Monitoring.StatsD 0.7.0).
I'm getting the following warning:
"warning NU1701: Package 'Akka.Monitoring 0.7.0' was restored using '.NETFramework,Version=v4.6.1' instead of the project target framework '.NETCoreApp,Version=v2.0'. This package may not be fully compatible with your project."
Can you guys recompile  targeting .Net Standard 2.0?

+1 for netstandard2.0


refactor(db): unify table macros

Allows for easier modification of Table trait implementations and the Tables enum.
Based on https://github.com/paradigmxyz/reth/pull/6551

The assertion  assert_eq!(table as usize, table_index); is failing since the declaration order is different now because before all dupsort tables were declared at the bottom.
I'm assuming variant order does not matter since it never implemented Ord, so I will just remove this check.


IPython.html.nbextensions is missing

Hi, thanks for the handy pip package. We have taken it into our release. However, the support for IPython seems limited. 'IPython.html.nbextension' went missing in IPython6.1. Would you like to have a look at it too? I have checked ipython 6.1 documentation, it is indeed not there.
here is the issue reference: https://github.com/chenjiandongx/pyecharts/issues/102

Found the info now.
http://ipython.org/news.html#ipython-4-0
For 4.0, we will split up components into several packages. The parts which work for any language will be called Jupyter, while the parts specific to executing Python code will remain as IPython.


Release Google.Cloud.AlloyDb.V1Alpha version 1.0.0-alpha03

Changes in this release:
New features

Add metadata exchange support for AlloyDB connectors (commit 5bd7231)
Adds metadata field describing an AlloyDB backup's quantity based retention (commit 5bd7231)

Created release for Google.Cloud.AlloyDb.V1Alpha-1.0.0-alpha03

This release failed for build machine reasons; we'll probably skip this release and release an alpha04 next week.


fix boilerplate

as part of fix for https://github.com/istio/istio/issues/8996

/lgtm

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

Needs approval from an approver in each of these files:

istioctl/OWNERS [fisherxu]
pilot/OWNERS

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

/assign @hzxuzhonghu

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fisherxu, hzxuzhonghu
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

istioctl/OWNERS [fisherxu]
pilot/OWNERS [hzxuzhonghu]

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

@islinwb: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
837b586b4a33889a23fa6aa7a04e73504408b930
link
/test istio-unit-tests

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

/test istio-unit-tests

@islinwb: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth.sh
837b586b4a33889a23fa6aa7a04e73504408b930
link
/test e2e-mixer-no_auth

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

/test e2e-mixer-no_auth


Add dark theme.

Begin porting Dark theme improvements from https://github.com/dax-leo/Modern.Forms.Toolkit.
Currently this only has the infrastructure to switch themes.
Updates will be needed to ensure each control is properly using the Theme system.

I was thinking to implement some sort of Theme Manager with json or xml config files, but didn't want to loose time on that.
I only needed Light/Dark theme, so I just extended it to have easy to use switch between those 2.

FYI.
Link below is "cleaned up" fork where I will be adding all the changes after I do all proper testing. That "Toolkit" version is something I just use for heavy experimenting.
Toolkit version -> I use it for my tools and some experiments (hence all the mess there)
Fork (link below) -> in sync with your master branch + "verified/tested" updates from my side.
https://github.com/dax-leo/Modern.Forms/tree/single_buffer_mode_forms
I use Toolkit version for my tools mostly due to modifications to render process. I need that memory efficiency or my datatable objects simply fall apart at 4K.


⚠ Bofrost.si has degraded performance

In 4187870, Bofrost.si (https://www.bofrost.si) experienced degraded performance:

HTTP code: 200
Response time: 3859 ms

Resolved: Bofrost.si performance has improved in e5ad628.


Error while switching between range and single slider

Problem is, when you'll try to manually change value from ['0','0'] value to '0', seems like slider property will be computed earlier then template will rerender and refs will not appear in $refs var, so slider will be set to undefined :(
I tried many ways but didn't find a working solution (except rerendering whole slider). May be you have one?

I publish a new version, you can update the component to see if the normal switch.

@NightCatSama now it works like a charm! ) Thank you!


Display glitch when embedded image is animated gif

Use the following cmd handler
Save the following image as /tmp/test.gif
Launch lighthouse
Type 'foo'. Output and theming is normal.
Delete foo, type 'test'
Display stops updating. Logic appears to continue normally -- eg. hitting backspace 5 times causes lighthouse to exit (deleted all characters from the input, and then one more).

cmd handler:
#!/usr/bin/env bash

while read L; do
  if [ "$L" = "test" ]; then
    echo "{%I/tmp/test.gif% $L|$L}"
  else
    echo "{look! $L|$L}"
  fi
done

Image:

Actually, a little further testing reveals it also occurs with non-animated gifs. Replacing test.gif with this:

still triggers the bug.

whoops I did not specify that PNG image types are currently required.  I have yet to figure out a good way to get gifs to load with cairo.


added dependabot and dependent action version bumps

checked all actions: no relevant warnings, no annotations
ready to merge


Specify datatypes for each term

Notes from review meeting: 2022-07-28
Define permissable datatypes for each property in the termlist: string, number, integer, object, array, boolean, null.  This is mostly already defined in the json schema docs, so just need shifting over into a new field in the termlist. Not sure how you'd define something like an array of ltc:class objects, so need to find that out too.

Closed by #382

Here's an extended set if data type definitions that are based on json schema.
Data Type
Definition
enumerated
A list of predefined values
Integer
Numeric values without decimal places that range 32 bits from -2^31 to 2^31.
float
Double-precision floating-point numbers with up to 17 significant digits
boolean
Values that may be represented by a binary data set (true/false, 1/0) and stored as 1 bit. Properties with boolean data types may not be null.
date
A value that contains a date (without time) that conforms to ISO 8601 and follows the format YYYY-MM-DD
datetime
A value that contains a single date and time that conforms to ISO 8601 and follows the format YYYY-MM-DD HH:MM:SS
string
String values may contain letters, numbers, puncutation mark, or symbols (including whitespaces). Text values are also referred to as literals, strings, or varchar. Text values are limited to 255 characters except where explicitly denotted otherwise. Text values may be subject to specific formats (character patterns) or set of valid characters.


contribute and Issue template pages' update

Issue Description
Update of the ISSUE template and CONTRIBUTE section of the GITHUB REPO.

For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.

[x] 1. Is it tagged with a type: defect or task?
[x] 2. Is it tagged with a priority: critical, normal or minor?
[x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
[x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.

[x] 1. If the issue is a defect, is the defect fixed?
[x] 2. If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)
[x] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[x] 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
[x] 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?

see pr #1071

now this issue can be closed with PR #1071


[cxx-interop] Fix reverse interop crash when using raw modules

Some fields in the AST are cached values that are populated lazily. We should not use those values directly as in case they are not yet computed we get back null pointers. Use ASTContext instead which can call the slow path if the cache is not yet populated.
rdar://132746445

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test


Rule suggestion: recommend dict.fromkeys over comprehension

Replace
{elt: None for elt in foo}

with
dict.fromkeys(foo)

dict.fromkeys is more efficient and readable.
In [4]: import random

In [5]: choices = ("red", "green", "blue")

In [6]: dupes = [random.choice(choices) for _ in range(1000)]

In [7]: %timeit list({elt: None for elt in dupes})
18.8 µs ± 97.8 ns per loop (mean ± std. dev. of 7 runs, 100,000 loops each)

In [8]: %timeit list(dict.fromkeys(dupes))
12.6 µs ± 49.9 ns per loop (mean ± std. dev. of 7 runs, 100,000 loops each)

Efficiency boost tested on both Python 3.9 and 3.12.
Note: would have to skip this rule for mutable values (see #4613).

Looks great!

I could pick up this one?

Feel free unless @tjkuson planned to do it or had started on it -- I'll leave it to @tjkuson to confirm!

Feel free unless @tjkuson planned to do it or had started on it -- I'll leave it to @tjkuson to confirm!

Haven't started anything, have at it! @mikeleppane

This would be a great rule for refurb, C4, or perflint. You should consider pinging the author of those libraries as well.

This applies not only to None, but any constant.
In my opinion, {elt: 0 for elt in foo} should also be replaced with dict.fromkeys(foo, 0).

@tjkuson would you agree? ↑

@tjkuson would you agree? ↑

Yes, this was my intention with the PR. Admittedly, I communicated that poorly by using only examples with None.

Closed by https://github.com/astral-sh/ruff/pull/9613. Thanks @mikeleppane!


@kadena/client 0.2.11throwing errors

I was having some bugs such as "account name does not match account......" and some other bugs @Kadena/client. I was using the latest version (^0.2.11) which was messing up, I just switched to the lower version (^0.1.10) and so far so good.

@advanztek It helps identifying the issue if you include a sample code that causes the error.

@team we had conversation here: https://discord.com/channels/502858632178958377/524762252734365696/1112065388591730778

I assume this is fixed with the new (1.x.x) client.


Timeout - Async callback was not invoked within the 500000ms timeout specified by jest.setTimeout.

What is the current behavior?
I am getting Timeout - Async callback was not invoked within the 500000ms timeout specified by jest.setTimeout.
Please provide your exact Jest configuration
My testing is currently running inside docker container.
test

This is not an actionable issue report. Please send a better description of what you want to achieve and provide a repro.

@thymikee I am facing a similar error message when running a Jest test: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.
My test looks like this:
describe('invalid nonces', () => {
  let msg = 'blah blah blah'
  it(`Should have error message ${msg}`, async (done) => {
    let errors = getErrors(exampleResult)
    console.log("errors: " + JSON.stringify(errors, null, 2))
    let filteredErrors = errors.filter(err => err.message == msg)
    console.log('filteredErrors: ' + JSON.stringify(filteredErrors, null, 2))
    expect(errors.length).toBeGreaterThan(0)
    expect(filteredErrors.length).toEqual(1)
    done()
  }, 10000)
})

My assumption is the Async callback being referred to in the error must be something different from the done callback variable I'm passing to this test. How could I find out what the Async callback is referring to?

I figured it out. Had to tweak the test to look like this:
describe('invalid nonces', () => {
  let msg = 'blah blah blah'
  it(`Should have error message ${msg}`, async () => {
    let errors = getErrors(exampleResult)
    console.log("errors: " + JSON.stringify(errors, null, 2))
    let filteredErrors = errors.filter(err => err.message == msg)
    console.log('filteredErrors: ' + JSON.stringify(filteredErrors, null, 2))
    expect(errors.length).toBeGreaterThan(0)
    return expect(filteredErrors.length).toEqual(1)
  }, 10000)
})

I figured it out. Had to tweak the test to look like this:
describe('invalid nonces', () => {
  let msg = 'blah blah blah'
  it(`Should have error message ${msg}`, async () => {
    let errors = getErrors(exampleResult)
    console.log("errors: " + JSON.stringify(errors, null, 2))
    let filteredErrors = errors.filter(err => err.message == msg)
    console.log('filteredErrors: ' + JSON.stringify(filteredErrors, null, 2))
    expect(errors.length).toBeGreaterThan(0)
    return expect(filteredErrors.length).toEqual(1)
  }, 10000)
})

I don't think this will work for multiple tests. When you have code that runs asynchronously, Jest needs to know when the code it is testing has completed, before it can move on to another test. The way to handle this is via done callback. Jest will wait until the done callback is called before finishing the test.

@ashleshsortee  async functions return a Promise, which is how Jest know when the test is complete


Printing and Filterable

Hi,
My English is bad, so i'm sorry.
I have many suggestions about Grid.
1-) Will be printing pretty good? For example
 columns.Add(model => $"  ").Encoded(false).Titled("İşlemler");
when i click to CTRL+P, these links and filter image(rather font) are viewing in print page.
2-)
columns.Add(model => model.transactionDate.ToString("dd/MM/yyyy")).Titled("Date");
is not filterable.
Thank you for Grid :)

Could you rephrase the question? I'm not sure what are you asking or what do you want to achieve here? If you can't, you could try using your native language and translate it using google translate, it might be more understandable.

You should format input by using .Formatted function:
columns.Add(model => model.transactionDate).Titled("Date").Formatted("{0:dd/MM/yyyy}")

http://imgur.com/a/u8zTS

You can hide them using css @media print directives.

Thanks. I agree both of them
You are helpful


eval and evalsha cannot be run on slave nodes

I am not sure this is an issue or I haven't figured it out but as far as I can see there is no way to run custom commands on slave nodes.
In sendCommand, the node is always set to "master" if the command is not explicitly marked as "readonly". "eval" and "evalsha" do not have the "readonly" flag.
        let to = this.options.scaleReads;
        if (to !== "master") {
            const isCommandReadOnly = commands.exists(command.name) &&
                commands.hasFlag(command.name, "readonly");
            if (!isCommandReadOnly) {
                to = "master";
            }
        }

Here is my cluster options:
      const options: ClusterOptions = {
        clusterRetryStrategy: (times: number) => times < 5 ? 2000 : null,
        enableReadyCheck: true,
        scaleReads: 'slave',
        redisOptions: {
          connectTimeout: 4000,
          ...pick(redisConf, REDIS_OPTION_KEYS) as RedisOptions,
          role: 'slave',
          readOnly: true,
          enableReadyCheck: true,
          reconnectOnError: () => true,
          retryStrategy: (times: number) => times < 5 ? 2000 : null,
        },
      };

I am trying to execute lua scripts that do not modify any data on the slaves to make the cluster scale better.
Is there another way to do this?

Has anyone had a chance to look into this?
As a proposed solution I could think of adding a "readonly" flag when defining commands:
    client.defineCommand('myCommand', {
      lua: '',
      numberOfKeys: 1,
      readOnly: true
    });

As a proposed solution I could think of adding a "readonly" flag when defining commands.

I misread this at first. To summarize what above discussion already says

To be safe, eval and evalSha will only run against the redis master node, not against slaves. (Though briefly during a failover, commands may get sent to a slave and get a -READONLY error.
A workaround to force a command to be sent to a slave (aka replica) (or randomly to any hosts with that data) is using defineCommand with readOnly: true to override the default lua behavior.

Known workarounds: I think sendCommand with a Command instance with readOnly: true set can be used to pass the raw eval command and args
A Redis.Script can also be constructed with readOnly: true but that's too brittle right now for me to suggest. Unfortunately, that would require https://github.com/luin/ioredis/pull/1404 since Redis.Script is not documented and internal implementation details may change while it's undocumented.


Allow to manually edit path for exported NodePath

Currently there is no way to manually change path for exported NodePath. It would be great if there would be ability to normally modify the path from the keyboard. It would be especially helpful in cases when we want to write absolute path or when the node we want to target is on another scene (and we are targeting from subscene).

I remember being able to edit it by hand recently.... is this still an issue?

@bojidar-bg tehre is no option to write path manually on the 2.1 alpha build from this week:

@kubecz3k Indeed... The funny thing is that I have a path leading outside some of the scenes (xD), so it should be a recent regression.

Not critical for the upcoming 2.1, so moving to the next milestone.


podium crashes on php 5.4

I.m using now 5.4.45 version of PHP.
After install I had seen the following error:
PHP Compile Error – yii\base\ErrorException

Can't use function return value in write context

...
/vendor/bizley/podium/src/models/db/ThreadActiveRecord.php:147

public function requiredPollAnswers()
    {
        if ($this->pollAdded) {
            $this->pollAnswers = array_unique($this->pollAnswers);
            $filtered = [];
            foreach ($this->pollAnswers as $answer) {
->                if (!empty(trim($answer))) {

Same error in /vendor/bizley/podium/src/models/db/PollActiveRecord.php:89
Please fix it.
Thanks for you greate work!

BTW, Yii2 works on 5.4, but this PHP version is end of life now.
http://php.net/supported-versions.php so IMHO is not a crime to ignore it :-)

Yes, but unfortunately as long as Yii 2.0.* supports this I must as well. With 2.1.* we are back to sanity.


Failed running GLIC missing when running docker

/server/atomic-server-bin: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /server/atomic-server-bin)

It's working again! docker pull joepmeneer/atomic-server:latest + docker run -p 80:80 -p 443:443 -v atomic-storage:/atomic-storage joepmeneer/atomic-server:latest


Allow_suscriptions = True issue

Hey Jayden,
I am having issues subscribing to the "hello world" example from /graphql due to the following error:
"Subscriptions are not allowed. You will need to either use the subscribe function or pass allow_subscriptions=True"
Any help would be greatly appreciated.
Thank You,
Gabriel

https://github.com/jaydenwindle/graphene-subscriptions/issues/1
Please check this link.

Hey @mukluk!
graphene-subscriptions doesn't work out of the box with the Graphene's default GraphiQL client setup. To test subscriptions, I'd recommend using GraphQL Playground. You can also add it to your Django project as a view with django-graphql-playground if you want.
This should definitely be more clearly documented in the readme :)


bugfix: go report tells code needs improvement

fix code improvement
Signed-off-by: zhubingbing<EMAIL_ADDRESS>1.Describe what this PR did
fix code improvement
2.Does this pull request fix one issue?
fixes #124
3.Describe how you did it
4.Describe how to verify it
https://goreportcard.com/report/github.com/alibaba/pouch
5.Special notes for reviews

LGTM. Thanks for your work. @zhubingbing


Consider how to personalize text/ email with results

We've received a number of support queries where parents of multiple children receive the results via text or email. However, because none of them have a specific name, they've tried each of the children's info and then eventually get locked out.
How might we add a name or other identifier to the email or text message to increase parents' or guardians' chance of accessing results?

We believe this ticket is covered by:
https://app.zenhub.com/workspaces/simplereport-better-data-team-605b43d51ea9f700119a48ee/issues/cdcgov/prime-simplereport/3184


Run without building

I suspect this might be an option I overlooked but is it possible to run a target without doing a build first?

Yes, https://github.com/vector-of-bool/vscode-cmake-tools/blob/develop/docs/target_debugging.md#running-program-from-launchjson
However it will run in the debugger (see note at the end of the section).
If you need to run without build and without debugger then you have to create a task, and for this you need to specify path to the built executable. VS Code doesn't allow ${command:} substitutions in tasks.

Closed.
If this issues still persists in the current 0.11.0-beta4, feel free to reopen this one or create a new one.


Support for long touch events

Added enumeration and eventing for long touches.

Looks really good!
I'm a tad curious what "long" is, not that you've defined it, but I didn't yet test it (may be useful to document it neverthless).

Long is an event built in to the nuimo. It's in their latest firmware/iOS app. It's a built in BLE event. In other words, I'm not setting up any kind of timer or anything to measure how long the device is touched. The user simply touches an area for what feels like 1 second or so, and the nuimo sends a touch long event (enumerated as 8-11).

This looks great, thanks very much for the PR!


ISSUES-2700 add funnel window crash test

#2700 https://github.com/yandex/ClickHouse/pull/2735#issuecomment-408389300
This test can rediscover this problem in most cases
I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en

Thank you!


[MS-406] Add unit-tests to bookmarks, bookmarks-api and bookmarkarguments

Description
Update unit test for bookmarks src
Motivation and Context
To add additional validation and check logic
Type of Change

test: Adding or modifying tests

How to Test
In moonshot folder, run ./run_unit_test.sh
Checklist
Please check all the boxes that apply to this pull request using "x":

[x]  I have tested the changes locally and verified that they work as expected.
[ ]  I have added or updated the necessary documentation (README, API docs, etc.).
[x]  I have added appropriate unit tests or functional tests for the changes made.
[x]  I have followed the project's coding conventions and style guidelines.
[ ]  I have rebased my branch onto the latest commit of the main branch.
[ ]  I have squashed or reorganized my commits into logical units.
[ ]  I have added any necessary dependencies or packages to the project's build configuration.
[x]  I have performed a self-review of my own code.
[x]  I have read, understood and agree to the Developer Certificate of Origin below, which this project utilises.

Screenshots (if applicable)
[If the changes involve visual modifications, include screenshots or GIFs that demonstrate the changes.]
Additional Notes
[Add any additional information or context that might be relevant to reviewers.]

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
   have the right to submit it under the open source license
   indicated in the file; or

(b) The contribution is based upon previous work that, to the best
   of my knowledge, is covered under an appropriate open source
   license and I have the right under that license to submit that
   work with modifications, whether created in whole or in part
   by me, under the same open source license (unless I am
   permitted to submit under a different license), as indicated
   in the file; or

(c) The contribution was provided directly to me by some other
   person who certified (a), (b) or (c) and I have not modified
   it.

(d) I understand and agree that this project and the contribution
   are public and that a record of the contribution (including all
   personal information I submit with it, including my sign-off) is
   maintained indefinitely and may be redistributed consistent with
   this project or the open source license(s) involved.

Jira Ticket: https://imda-dsl.atlassian.net/browse/MS-406?atlOrigin=eyJpIjoiMDE3MTM5NTBjMTBkNGNkYzkzMzMxMDNmMTU2MDk0MzQiLCJwIjoiaiJ9


Fix asset not found in android 29+

I use next code to reproduce the #734 issue,
https://github.com/fluttercandies/flutter_photo_manager/blob/a05c22bfae1071ebc6f3115e4f06d6718a0a080c/example/lib/page/developer/issues_page/issue_734.dart#L30-L75
And, the pull_request will fix it.


Fixed #32304 -- Fixed prefixing STATIC_URL and MEDIA_URL by SCRIPT_NAME for absolute URLs with no domain.

ticket-32304
Thanks Adam Hooper for the report.
Regression in c574bec0929cd2527268c96a492d25223a9fd576.

@adamhooper Can you check this patch?

@felixxm LGTM! Thank you for such a quick response.


docs(nuxt): explicit documentation for custom routing #14787

resolves #14787
❓ Type of change

[x] 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
As described in #14787, there is multiples ways to add a route in Nuxt. It is well explained is several places so I created a new guide page dedicated to custom routing. I mainly move some content from the pages directory docs which I find more fitting elsewhere. I also referenced the methods from nuxt kit but couldn't find many documentation about them.
📝 Checklist

[x] I have linked an issue or discussion.
[x] I have updated the documentation accordingly.

Thank you so much for your great work on this!


[FEATURE] Skip samples/ms to avoid latency in models with delay

Thanks for taking the time to write a feature request! Use the following prompts to help you describe what you're looking for.  The more info you provide, the easier it'll be for me to understand what I can do to make it happen for you without having to come back and ask you questions.
Is your feature request related to a problem? Please describe.
Some models have delays for some reason. As in, if I compare the NAM output vs the input signal there's silence at the start of the NAM output.
This is probably due to the training process but can result in models that sound good when reamped but feel bad when tracking/playing.
Describe the solution you'd like
I would like a feature where you can skip samples or milliseconds in a model that has obvious (or non obvious) latency to make it respond faster. Maybe something like a delay knob in an IR loader that is used to align different IRs.
No idea if this is even possible but the biggest problem I have with NAM is when using models that sound good but have a delay that makes them feel bad when playing so it would be great if this issue could be solved. Either by a feature like this if possible or if not something in the training process itself.
Describe alternatives you've considered
The best alternative is to just switch to another model which seems like a waste.
Additional context
N/A

It's highly nontrivial to "fix" a model like you're describing. As I'm typing it, it sounds almost silly to say, but that silence is what the model predicts the gear does--so removing that would be "asking the model to predict the future"!
Unfortunately, the direction in which it's easy to modify the latency is in the direction of increasing it 😉
The best way to keep this from happening is to (A) look closely at the plot when the latency is determined at the start of training with the simplified trainers. If it looks wrong, then (B) set it manually.

I've been looking at a few things around this--tweaking the latency calculation algorithm's parameters, and making it easier to set in the Colab trainer (I accidentally made it kind of hidden when I cleaned up the form UI...oops! 😅 )


i would like to add a automatic slider on the hero section of the main page

Explain a bit more about the issue. Then, I will assign it to you

Currently there is only one image
Wouldn't it be nice that image automatic changes
Like a slider but it will be automatically

@vaibhavsharma1234 start working on it.

Thanks for assigning please add the difficulty of issue tag also

Currently working on this just a little busy due to college


[new function needed] in my environment，i had to set a socks5 （not http） proxy to access the internet

i am wondering if there is a way to add socks proxy function to the config files，and use “true” or “flase” to switch on and off。


Only one lens is displaying when using holographic remoting

Describe the bug
Only the left lens is displaying when using holograohic remoting and there is no error thrown or whatsoever
To reproduce
Steps to reproduce the behavior:
I basically followed the procedure here :
https://microsoft.github.io/MixedRealityToolkit-Unity/Documentation/Tools/HolographicRemoting.html
The bug happens at least with Unity 2019.2.21f1 and Unity 2019.3.7.f1, maybe with other versions (not tested)
Expected behavior
The holographic rendering should be displayed on the 2 lenses
Your setup (please complete the following information)

Unity 2019.2.21f1 or Unity 2019.3.7.f1
MRTK Version 2.3.0

Target platform (please complete the following information)

HoloLens 2

I just found the issue, I was using a custom shader, so I had to change the stereo rendering mode in XR settings from single pass instanced to single pass


proposal: x/sys: Add GetLargePageMinimum() to windows

Hello,
could you please add GetLargePageMinimum() to the windows API wrappers? The VirtualAlloc() flag MEM_LARGE_PAGES is supported, but per the documentation, the block size should then be large page aligned. This alignment information is missing due to the lack of the GetLargePageMinimum() function. The proposed extension closes the gap.
Many thanks for considering my request.

Taking this out of the proposal process, as adding a wrapper for an ordinary Windows call does not require a proposal.
Want to send a patch for this?


Still maintained?

Hello,
Is this package still maintained?
I see there are multiple issues and PR opened with no reaction from maintainers.
Also, it should be refactored to use the JSON endpoints.
Can you update us on that?
Thanks,

Hello,
referring to your question this package is maintainable and we are going to address the pull requests.
However,
please keep in mind it is a public channel so not all Tufin features are supported here.
You are more than welcomed to extend the package capabilities, we'll be happy to assist with any question.
thanks,
Rami.


Default profiles appear even if removed from the config.json

Description of the new feature/enhancement
When one of the default profiles (PowerShell, Command Prompt, Azure Cloud Shell) is deleted from the configuration file, it still appears in the Terminal. As it is not in the configuration file, it can no longer be edited.
It would be more intuitive if the profiles are either re-created in the config file, or they disappear from the new session dropdown in the terminal.
If they were to be removed from the terminal, it would make sense if a dynamic profile was added to the configuration file when a new shell is installed, so that the user would be able to configure or delete it.

@dev-kittens - to "remove" auto-generated profile you need to mark it as "hidden"

@Don-Vito Thank you for the link. I've added the unwanted profiles to disabledProfileSources in my config.
I'm not quite satisfied with this answer, though. It's quite unintuitive to have profiles appear even though they were deleted in the configuration file.
I would suggest for Windows Terminal to either re-add the items to the JSON file on start or to only generate dynamic profiles when creating a configuration or when a new shell is installed.

@dev-kittens - I am not from the team, but what you write makes sense, the behavior is not the most intuitive. Probably you should update the issue title and expected behavior. So once the team gets to it, they know that you are aware of current behavior but ask for an improvement.

Oh, sure. I've just done that.

Thanks for the feedback! We actually went throguh a pretty lengthy design discussion about this last year when we were implementing cascading settings and dynamic profiles the first time. If you really want to read more of our decision making process, you can refer to #1258 and #1321. While this wasn't the most intuitive feature I've ever shipped, this behavior had the least drawbacks.
I've added some additional docs over at https://github.com/MicrosoftDocs/terminal/pull/186, hopefully that should help mitigate the confusion a bit.

So, in order to stop seeing a shell for something I don't have and don't use yet (Azure) I needed to add "disabledProfileSources": ["Windows.Terminal.Azure"], to settings.json. I honestly feel like just deleting it should have been sufficient, but I understand that it probably wasn't up to you.

@Don-Vito / @zadjii-msft - I'm just another Windows Terminal user here, but here are a few thoughts:

Can the Settings UI indicate when a profile is dynamic and provide a one-click option to delete it and do whatever is needed to keep it from showing up again?

For people editing the JSON directly, it seems like a comment for dynamically generated profiles saying how to keep it from getting re-created is needed at a minimum.  Even better, have a setting per dynamic profile to disable the profile (hiding it leaves it in the settings UI).  On a related note, can multiple dynamic profiles come from one profile source?  If so, disabling at the per-profile level seems like a better option than disabling the whole profile source.

Also, I ran into the same issue as @spiralw where I deleted the profile from the config file and found it odd that the deleted profile was restored in the UI but wasn't in the config file.  The suggested solution of Windows Terminal re-adding the items to the JSON file on start seems reasonable to eliminate this confusion.

(1 A) IIRC, the "delete profile" button on a profile in the SUI should hide dynamic profiles, instead of just removing them from the json. @carlos-zamora can correct me if I'm wrong on that. If it doesn't today, the works that's being done as a follow up to #10513, #8324 should take care of this
(1 B) RE:

Can the Settings UI indicate when a profile is dynamic

I thought we were going to be adding that text to the SUI at some point, but clearly we forgot to do that.

Also, I ran into the same issue as @spiralw where I deleted the profile from the config file and found it odd that the deleted profile was restored in the UI but wasn't in the config file. The suggested solution of Windows Terminal re-adding the items to the JSON file on start seems reasonable to eliminate this confusion.

That's definitely unexpected. When the settings UI loads up the settings, it actually just uses the contents of the file, so perhaps it's possible that your editor had the file open and didn't notice that the file contents changed out from underneath it?

(1 A) IIRC, the "delete profile" button on a profile in the SUI should hide dynamic profiles, instead of just removing them from the json. @carlos-zamora can correct me if I'm wrong on that. If it doesn't today, the works that's being done as a follow up to #10513, #8324 should take care of this

The problems in this case are:
a. The Delete Profile button for the Windows PowerShell profile is greyed out.  I added a comment to #10547 about this since that issue is currently closed as a dupe of the work to remember which dynamic profiles have been deleted but won't be fully resolved unless the block on deleting the profile is removed.
b. Hiding the profile doesn't remove it from the Settings menu.  If I delete a profile I expect it to act like it's fully deleted - at least in the UI.

(1 B) RE:

Can the Settings UI indicate when a profile is dynamic

I thought we were going to be adding that text to the SUI at some point, but clearly we forgot to do that.

Thanks for getting an issue opened for this!

Also, I ran into the same issue as @spiralw where I deleted the profile from the config file and found it odd that the deleted profile was restored in the UI but wasn't in the config file. The suggested solution of Windows Terminal re-adding the items to the JSON file on start seems reasonable to eliminate this confusion.

That's definitely unexpected. When the settings UI loads up the settings, it actually just uses the contents of the file, so perhaps it's possible that your editor had the file open and didn't notice that the file contents changed out from underneath it?

This definitely repros:

Run Windows Terminal on Windows 10 19043.1147.
Go to Settings -> Open JSON file
Remove the "Windows PowerShell" profile from the settings JSON.
Close Windows Terminal.
Close the editor.
Run Windows Terminal again.
Go to Settings (notice that Windows PowerShell is still there still) -> Open JSON file
See that the "Windows PowerShell" profile has not been restored.
For extra bonus points, go back to Windows Terminal, click the Save to save Settings, and then see that an empty profile entry has been added to the profile list (i.e. "{}")

(1 A) IIRC, the "delete profile" button on a profile in the SUI should hide dynamic profiles, instead of just removing them from the json. @carlos-zamora can correct me if I'm wrong on that. If it doesn't today, the works that's being done as a follow up to #10513, #8324 should take care of this

In box and dynamic profiles disable the delete button and display a text explaining why it's disabled:

In box profiles (CMD and Windows PowerShell):

Dynamic profiles (WSL distros, PowerShell Core)

We still show hidden profiles in the SUI so hiding it won't fix the issue. We need #8324 so that we can know when the user deleted (via JSON or SUI) the profile and we make sure it doesn't show up again. Not great but we're getting there.
@DaveEM You're seeing the same bug here. The Windows PowerShell profile should basically be an empty profile IIRC. The problem shouldn't repro for non-dynamic non-in-box profiles (brand new profiles you created yourself).

@zadjii-msft removing the Resolution-By-Design tag since we'll want to do this after #8324.


onEnter callback doesn’t fire when you back to the state from the nested one.

If its a child state then you never really leave the parent state so the onEnter wouldn't fire.

closing unless further information is required/requested


In_tail plugin not expending paths properly with subfolders (multiple * in the path)

fluentd version: 1.3.1
environment - official docker image used. (1.3-debian-onbuild)
logging level of fluentd: debug
I have the following setup for in_tail
<source>
  @type tail
  path /container-logs/*/alloc/logs/*.stdout.0
  pos_file /tmp/fluentd/logging-containers.log.pos
  refresh_interval 30
  tag containers.*
  <parse>
      @type none
  </parse>
</source>

if my source is setup like this it never expands the paths and shows no trace/debug logs that it started tailing any files. Also I don't get anything matched and nothing goes to my elasticsearch.
If I just change the path in source to
/container-logs/1235/alloc/logs/*.stdout.0 (replaced first * with exact number of container guid) all works fine. Log would show me that it is tailing the right files, and I am starting to get results.
I've checked the 1.3 ruby code for input tail plugin and I don't see any problems why this should not work. My log structure mounted via docker to fluentd container is like this:
/container-logs/container-guid/alloc/logs/container-name.stdout.0
/container-logs/container-guid2/alloc/logs/container-name2.stdout.0
/container-logs/container-guid3/alloc/logs/container-name3.stdout.0
...
I lost time and time to decipher why it is unable to tail all these logs properly. Am I missing some generic setting, or something?
I've tried the following without success, too.
/container-logs/**/alloc/logs/*.stdout.0
/container-logs/**/*.stdout.0

Does fluentd have the permission for container-logs and its sub-directory?

Great hint. it seems that might be the problem, just checked. Will try to find the best way to inject my user_id and run fluentd as that user instead. If you have any best advice on that it would be appreciated.


Create a tool to make it easier to find the test failures in Travis

Automate the steps described in
https://github.com/azkaban/azkaban/wiki/Developer-Tools-and-Tips#how-to-find-test-failure-from-the-ci-log

@HappyRay It'd be good to change the regex in https://github.com/azkaban/azkaban/wiki/Developer-Tools-and-Tips#how-to-find-test-failure-from-the-ci-log to  > \w* FAILED. This pattern is able to also catch strangely named tests like FlowRunnerTestYaml  (see https://github.com/azkaban/azkaban/issues/1921). Looks like wiki pages can be only edited by repo owners and there's no PR-like process.

Thanks for the suggestion.
I made the change.
I hope it won't make the result too noisy.
I also changed the permission to allow anyone to edit the wiki. Please let me know if it is not working.

@HappyRay thanks.

I hope it won't make the result too noisy.

Not at all, it only had that one hit when the build failed due to FlowRunnerTestYaml.

I also changed the permission to allow anyone to edit the wiki

Nice, it works. I just edited the wiki page to add a single space before '>' in the regex. Not a must, but makes it even more deterministic.


syntax highlight confused by asm """ """ and shows remainder as string

https://github.com/nim-lang/Nim/blob/devel/lib/system.nim at a6f248f3d09f18daab67e25468760f722bb24201

No longer an issue.

@Varriount the problem seems to be this line in $nim_D/NimLime/Syntaxes/Nim.YAML-tmLanguage:
- {include: source.asm}

if i comment it out, it works
perhaps source.asm needs to be somewhere for it to work? maybe another package you've installed for getting asm syntax and that should be a dependency?
anyhow, the workaround is to just comment it and rebuild $nim_D/NimLime/Syntaxes/Nim.tmLanguage using packagedev


Clicking on mesh brings up context menu in wrong location

I left clicked on the left side of the mesh and see where the Mesh Demo context menu goes:

@skalarproduktraum is there any chance this comes from Scene.RaycastResult ?

Is this a hidpi thing?

@skalarproduktraum bump for thoughts

Ah, I see https://github.com/scenerygraphics/sciview/issues/475

Closing this as a duplicate


Linter issue: internal/service/storage.go:31:6: exported type StorageConfig should have comment or be unexported

internal/service/storage.go:31:6: exported type StorageConfig should have comment or be unexported

Fixed in https://github.com/RedHatInsights/insights-operator-gathering-conditions-service/pull/84


change offline mass build webpack output to be stored in static_shared

Pre-Flight checklist

[ ] Testing

[ ] Code is tested
[ ] Changes have been manually tested

What are the relevant tickets?
Closes https://github.com/mitodl/ocw-studio/issues/1685
What's this PR do?
In https://github.com/mitodl/ocw-hugo-themes/pull/1056, we changed ocw-hugo-themes to collect and store all shared static assets (webpack build output, shared static images, etc.) into a folder called static_shared. The purpose of this was to isolate static resources shared by all themes into one folder. This way, it's easier to copy all the necessary static resources into any given offline build of a site built with any theme that inherits base-theme.
In https://github.com/mitodl/ocw-studio/pull/1680, we changed the single site publishing pipeline (site-pipeline.yaml) to sync static_shared from the root of the live site bucket into the offline build instead of static, which closed the loop on that for single site builds. One thing that was missed was the offline mass build, and that's what this PR takes care of. The offline mass build does its own webpack build before building all of the offline sites, and this change ensures that the output goes into static_shared instead of static.
How should this be manually tested?

Make sure you are pointing at the main branches of ocw-hugo-themes and ocw-hugo-projects by setting this in your .env:

OCW_HUGO_THEMES_BRANCH=main
OCW_HUGO_PROJECTS_BRANCH=main

We're going to want to make sure we limit the amount of sites built by the mass build pipeline locally, otherwise the build will take forever. This can be accomplished by changing like 341 of websites/views.py to: sites = sites.prefetch_related("starter").order_by("name")[:10]
Spin up ocw-studio on this branch and ensure you have Concourse and Minio configured properly (see the readme for more info)
You can skip these steps if you already have theme assets generated on the main branch:

Run docker compose exec web upsert_theme_assets_pipeline
Visit the Concourse web UI at http://localhost:8080
Find the theme assets pipeline for the main branch and trigger a build, then wait for it to complete

Upsert the offline mass build pipeline with docker compose exec web ./manage.py upsert_mass_build_pipeline --offline --starter ocw-course-v2
Find the offline mass build pipeline we just upserted, unpause it if necessary and trigger a build
After the build is complete, log into the Minio web UI at http://localhost:9001
Browse to any course built by the offline mass build and download the ZIP file in the course root
Extract the ZIP file, verify that the webpack build output is stored in static_shared
Double click the index.html file and verify that:

There are no errors in the console
Nav links work
Resource links to PDFs and such work
Nothing else seems weird or off about the site

Codecov Report

Merging #1687 (8676516) into master (48959e7) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##           master    #1687   +/-   ##
=======================================
  Coverage   87.82%   87.82%
=======================================
  Files         243      243
  Lines       10378    10378
  Branches     1736     1736
=======================================
  Hits         9114     9114
  Misses       1128     1128
  Partials      136      136

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


todo - version:bump to v1.30.2

Backstage release v1.30.2 has been published, this Pull Request contains the changes to upgrade todo to this new release
Please review the changelog before approving, there may be manual changes needed:

Changelog: v1.30.2
Upgrade Helper: From 1.29.1 to 1.30.2

Created by Version Bump<PHONE_NUMBER>7

Hi @Rugvip, when you have some time could use some help on why this one is failing the type check, please?

@awanlin hmm, something's up. I'll have a look next week but this is prolly a framework issue

Hi @Rugvip, if you could give this another look that would be awesome! 🙏

Pushed a fix for the type issue, wasn't anything too serious. The explicit ServiceRef type without type parameters made the service ref type too open, fix was to remove the explicit type.


Turn into monorepo

Changes the repo into a monorepo by splitting into 'app' and 'lib' directories
The app is now a vite app instead of create-react-app, which is a bit more lightweight
Can run yarn dev in the app dir and it will use the library in the lib directory. It does not automatically build what is in the lib directory, so if you make changes in the lib directory, you should re-run yarn build or run e.g. yarn build:esm --watch for a continuous watcher

this PR is targetted to your make_component branch
It also removed the rollup script for now, but I can revive this if you are interested in having ability to include the seqpanel via a simple script tag, instead of/in addition to,  install from npm ability

note: the readme says @gmod/generic-sequence-panel, but you would want to rename the "name" field in lib/package.json to "@gmod/generic-sequence-panel" to make it publish to that name, currently would just be generic-sequence-panel without the @gmod namespace

essentially, after this PR is added, you can use yarn publish in the lib folder to publish to npm

OK, that is A LOT. I'm going to merge, add the @gmod and do some testing.

yes, it is indeed a large pr and just goes on to show that everything with developing libraries can be weird. there may be ways that could be simpler, but this should be ok. possibly we could remove the separation between lib and app, i read about possibly some ways of doing that


Checking for python_dll makes pip installation impossible if you need to override python_dll

Steps to reproduce the issue
install pyq through pip on a system where python has been built statically
You can attempt to override the python_dll path by using --global-options=configure --global-options="--python-dll=/my/path/to/libs" but it will fail because pip install runs python setup.py egg_info before running python setup.py install
Expected result
Don't throw an error when checking for python_dll in commands that don't require it.

@nugend — we created template in order to speed up troubleshooting steps. Please answer following questions, so we could troubleshoot your issue.

Which operating system are you using (if Linux, please provide flavour of it, i.e RedHat, CentOS or Ubuntu), is it 32-bit, or 64-bit?
Which version of PyQ are you running? You can use pyq --versions or pip list | grep pyq.
Which version of kdb+ are you using, is it 32-bit or 64-bit?

If on 64-bit, is your QLIC set? Please provide output env | grep QLIC on linux/macOS, or set|grep QLIC on Windows.

Did you use virtual environment to install PyQ? If not, why?
Where is your QHOME? Please provide output env | grep QHOME on linux/macOS, or set|grep QHOME on Windows.
Do you use Conda? If so, what version?

Please provide steps to reproduce the issue.
Please provide actual result of installation of PyQ.

Oh, I shot my troubles already. This was for your benefit.


Change display color

I was wondering where I can change the colors to something different.

@Yijia-Chen Hi the visualization color is added to the png via color palette https://github.com/PeikeLi/Self-Correction-Human-Parsing/blob/b1ba867941b7b9e7fe92431925839aac663a5936/evaluate.py#L198.
In brief, each pixel is in the image is the label id. The display color is defined by a customized color palette.

Thank you!


How to setup workflow (Jetson Nano + Ubuntu PC)

Hi,
Can someone explaine me what is a proper way to setup workflow for Jetson app development?
For a past 2 days I can't compile jetson-inference for a x86 Ubuntu machin, each time there is some conflicts or missing libs/headers/whatever stuff.
There is totally no docs how one can develope app on host PC. Jetpack is only for Jetsons, Nvidia SDK Manager lacks TensorRT, manual installation... don't want even talk about it.
Jetson family are ARM64, so there is no IDE.
Any help will be really apreciated. Realy!

Hi @r8d8, I haven't tried to cross-compile jetson-inference, it is intended to be compiled natively on the Jetson.  Sorry for the trouble.

@dusty-nv , it's ok. I appreciate your work.
I am just trying to figure out how to develope for Jetson.
Like all Jetson devices are ARM based, so I bet no one develope directly on them (not much toling for platform). How do you developed this lib?
I need small demo to detect persons, crop image of them from a frame and send it to server.

I personally use GEdit / terminal to develop, however if you search around the Jetson Devtalk forums, there are folks also using Visual Studio Code along with some other IDE's.  There are also some folks who cross-compile their projects, particularly the Linux kernel.

And how about debuging?

It would appear that VS Code can use GDB, others like code::blocks probably can too.
See these threads from the forums:
https://devtalk.nvidia.com/default/topic/1056104/jetson-nano/programing-jetson-nano-with-c-/post/5356971/#5356971
https://devtalk.nvidia.com/default/topic/1050570/jetson-nano/cross-compiling-c-c-code-for-jetson-nano-in-ubuntu-18-04-in-a-host-pc-x86-x64-/post/5331806/#5331806
You could try Nsight Eclipse Edition as a remote IDE.


Does not update the runtime in subsequent submissions. Will like leethub to record/update score with the best runtime

Please review previous closed issues before filling out a new one! Duplicate issues will be closed without comment.
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Add more details. How and when does this happen?
LeetHub doesn't update your results if you submit the same code without change. This has confused people before, and I think you're one of them.


Run job only on pull request

@iMicknl If you forbid direct push on master, we can ease the workflow and avoid to run twice the checks (one for the PR and one for the push).
I also removed the scheduled job, their is no need to do this except for dynamic check like hassfest or hacs.

Good catch! Should we not make sure this one is run on master as well? (Is that possible?).
In case we merge an (outdated) PR, which causes conflicts in master branch.

By the way, doesn't push mean that it will be run on every commit in a PR? Or is this still the same when triggered by pull_request.

@iMicknl If you forbid direct push on the master branch, it will be ok.


[partner request] Correct branding

A minor change to correct the partner name from MediaVine => Mediavine.
cc @kaycebasques

Whoops!
There were 10 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/fundamentals/performance/optimizing-content-efficiency/loading-third-party-javascript/index.md#L343 - '


:ghost: upgrade dependencies

hey folks, CI is breaking because of a mixup on addon release-0.3 branch


this.element.querySelectorAll is not a function

code :  expect(wrapper.contains('p')).toBe(true);
error: this.element.querySelectorAll is not a function
version: 3.2.0

Can you post the entire component you're testing?

I'm getting the same error. I'm in a bit of a Vue + TypeScript + Jest tangle, so it could be something else.
My component and spec are as follows:
<template>

    {{ test }}

    <router-view/>

</template>

import { shallow } from 'avoriaz';
import App from '../App';

describe('App.vue', () => {
  it('should contain a div', () => {
    const wrapper = shallow(App);
    expect(wrapper.contains('div')).toEqual(true);
  });
});

    TypeError: this.element.querySelectorAll is not a function

       5 |   it('should contain a div', () => {
       6 |     const wrapper = shallow(App);
    >  7 |     expect(wrapper.contains('div')).toEqual(true);
         |                    ^
       8 |   });
       9 | });

It sounds like an async thing. Before using Avoriaz I needed to use Vue.nextTick() otherwise the DOM wouldn't be populated.
I'm not using a browser to test, but I believe Jest brings jsdom with it.
Many thanks if you can help.

I believe the issue is that App uses a template rather than a render function. You need to compile it before you can mount it (this is something we should add to avoriaz if you'd like to make a PR).
Something like this:
import { compileToFunctions } from 'vue-template-compiler'

export function compileTemplate (component: Component): void {
  if (component.template) {
    Object.assign(component, compileToFunctions(component.template))
  }

  if (component.components) {
    Object.keys(component.components).forEach(c => {
      const cmp = component.components[c]
      if (!cmp.render) {
        compileTemplate(cmp)
      }
    })
  }

  if (component.extends) {
    compileTemplate(component.extends)
  }

  if (component.extendOptions && !component.options.render) {
    compileTemplate(component.options)
  }
}

import { shallow } from 'avoriaz';
import compileTemplate from './compileTemplate'
import App from '../App';

describe('App.vue', () => {
  it('should contain a div', () => {
    const wrapper = shallow(compileTemplate(App));
    expect(wrapper.contains('div')).toEqual(true);
  });
});

The app was building fine for development and production as far as I can remember. It is now, and I've not changed much. I have swapped out Avoriaz for vue-test-utils and managed to get tests working. Am I right in thinking vue-test-utils is a fork of Avoriaz and being adopted as the official testing library?

Yep Vue Test Utils is based off avoriaz. You're better of using vue-test-utils, so I'm glad it was easy for you to migrate 👍


CORS not work in 2.0

What steps will reproduce the problem?
I add the corsFilter in behaviors of my controller which extend \yii\rest\Controller like below
<?php
/**
 * This is class file for Controller.
 * This is base controller for non-restful apis
 *
 */

namespace backend\components;

use Yii;
use yii\filters\Cors;
use backend\behaviors\ControllerBehavior;

class Controller extends \yii\rest\Controller
{
    /**
     * This method is used to valide the user's authority with token.
     * This method is invoked right before an action is executed.
     *
     * The method will trigger the [[EVENT_BEFORE_ACTION]] event. The return value of the method
     * will determine whether the action should continue to run.
     *
     * If you override this method, your code should look like the following:
     *
     * ```php
     * public function beforeAction($action)
     * {
     *     if (parent::beforeAction($action)) {
     *         // your custom code here
     *         return true;  // or false if needed
     *     } else {
     *         return false;
     *     }
     * }
     * ```
     *
     * @param Action $action the action to be executed.
     * @return boolean whether the action should continue to run.
     */
    public function beforeAction($action)
    {
        if (parent::beforeAction($action)) {
            $this->attachBehavior('ControllerBehavior', new ControllerBehavior);
            return $this->checkAuth();
        }

        throw new HttpException(400, "Fail to resolve the action.");
    }

    /**
     * serialize the response in format of json
     *
     */
    public $serializer = [
        'class' => 'yii\rest\Serializer',
        'collectionEnvelope' => 'items',
    ];

    public function behaviors()
    {
        return array_merge([
          'corsFilter' => [
              'class' => Cors::className(),
              'cors' => [
                'Origin' => [
                    'http://web.wm.com'
                ],
                'Access-Control-Request-Method' => ['GET', 'POST', 'PUT', 'DELETE'],
                'Access-Control-Allow-Credentials' => true,
              ],
          ],
        ], parent::behaviors());
    }
}

I use angular to call the api which use POST verb, but error happens like below

I find the OPTIONS request call the real action, so cause the action throw 400 exception. I don't know why? I think the OPTIONS request should not reach the action.
Additional info

Q
A

Yii version
2.0

PHP version
5.5.37

Operating system
linux

1- you are missing the Options Action which is defined in \yii\rest\ActiveController but not in parent \yii\rest\Controller. you'll need to manually add it. (quick example this + this)
2- CORS should be handled before authentication + parent authenticator already defined in \yii\rest\Controller should be unset. check those 2 links from docs for more details:
http://www.yiiframework.com/doc-2.0/guide-structure-filters.html#cors
http://www.yiiframework.com/doc-2.0/guide-rest-controllers.html#cors


Non Scheduled workflows last logs issue

If we create a workflow without schedule (manual trigger only), the get logs fails. We'll need to fetch data from another airlfow table

I can take a look at this one after the cache fix if needed

closed by https://github.com/open-metadata/OpenMetadata/pull/6296


feat: fix margins

This PR:

Fix bug on the Main page;

Preview

Preview Main page

Steps to test

[ ] Open the preview pages;
[ ] Confirm that everything looks and works as expected;

@xmulligan Hello! Please merge this pull request.


Error running tests: ganache-cli fails to run (?)

Describe the bug
I'm using the latest version of ganache-cli (Ganache CLI v6.12.2 (ganache-core: 2.13.2)), and the tests fail because they cannot connect to the node.
When I check the logs, I see Unknown argument: chain in the first line (I assume that's ganache's output).
Also, at the end of the test output:
Killing opened Ganache-Cli
./run_tests.sh: line 27: kill: (72561) - No such process

To Reproduce
Steps to reproduce the behavior:

clone the project
Install ganache globally
execute ./run_tests.sh

Expected behavior
Tests pass

@mmv08 Last version of ganache is v7.9.1 (@ganache/cli: 0.10.1, @ganache/core: 0.10.1)
Remember that ganache package is now ganache and not ganache-cli

@mmv08 Last version of ganache is v7.9.1 (@ganache/cli: 0.10.1, @ganache/core: 0.10.1)
Remember that ganache package is now ganache and not ganache-cli

I figured that out, but it was not mentioned anywhere in the readme that a global install of ganache-cli is a requirement. I created a PR that adjusts the script to not rely on global environment and use npx :

npx is a command-line tool that comes with npm (Node Package Manager) and is used to execute JavaScript packages. It allows developers to run a package without having to install it globally or locally.


Hide irrelevant fields in sheet template forms

@eudesbarbosa pointed out a thing I completely missed before: in the UI we are showing fields which are not expected to be edited, and which do not affect anything if edited. Example of this is the lib_kits field, which simply provides options for lib_kit.
The initial simple solution is simply to add a "black list" for templates, as we have a fixed set of them and can tell which ones have which fields.
Once we allow for inclusion of user-made templates, we should denote such fields in the templates with a special syntax. @holtgrewe suggested e.g. prefixing them as __field_name. I will add appropriate issues once I'm doing the separation of templates from cubi-tk.
Since the simple solution is trivial to implement, I'll squeeze this to the publication milestone v0.11.3.

Done.

Prefixing them as __field_name already is the official cookiecutter way of defining private/hidden variables. They are in fact already ignored by SODAR in the "Create from template" form (could not find out why though). Converting these field to private variables should be the long-term fix here imo.
https://cookiecutter.readthedocs.io/en/stable/advanced/private_variables.html


UBI 8.6

Description
UBI 8.6 is out, so let's update the main, postgres, and operator images.
Checklist

[x] Investigated and inspected CI test results
~[ ] Unit test and regression tests added~
~[ ] Evaluated and added CHANGELOG entry if required~
~[ ] Determined and documented upgrade steps~
~[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)~

Testing Performed
CI

Ignore the failing test, as quay.io/cgwalters/coreos-assembler@sha256:6ed6cd0006b6331d8cfd4a794afe7d2a87dc9019b80658a21b28d9941a97356d seems to no longer exist. We will replace the need for that image with another image in another PR.


Icon $clr-xxx variables are not accessible

Describe the bug
There is no scss file to import the icon $clr-xxx variables. The dark theme does define and export these, but not for the light theme.
$clr-icon-color-success: hsl(99, 100%, 26%);
$clr-icon-color-danger: hsl(9, 100%, 44%);
$clr-icon-color-warning: hsl(38, 100%, 38%);
$clr-icon-color-error: hsl(9, 100%, 44%);
$clr-icon-color-info: hsl(201, 100%, 36%);
$clr-icon-color-inverse: hsl(201, 0%, 100%);
$clr-icon-color-highlight: hsl(201, 100%, 36%);

I can also not find any css vars with these, e.g.
--clr-icon-color-success
How to reproduce
Looking for the file, I cannot find it among the distributed packages (only see it in the source code):
\clarity\packages\icons\src\clr-icons.scss
Also, that file should probably be split as you don't want to import the styles, and just the variables / mixins
Expected behavior
An icon scss file one can import to access the $clr-xxx variables
Versions
Clarity project:

[ ] Clarity Core
[x] Clarity Angular/UI

Clarity version:

[ ] v3.x
[x] v4.x
[x] v5.x

Framework:

[x] Angular
[ ] React
[ ] Vue
[ ] Other:

Framework version:
Angular 11_

I should mention the reason for this request is that right now we had to copy the lines above into our code. We would like to avoid that in case the colors get updated.


.at[] with complex numbers

import jax
import jax.numpy as jnp

@jax.jit
def f():
    return jnp.zeros((1,), dtype=jnp.complex64).at[0].set(1)

f()

DeviceArray([3.6602185e-37+0.j], dtype=complex64)

And:
import jax
import jax.numpy as jnp

@jax.jit
def f(x):
    return jnp.zeros((1,), dtype=jnp.complex64).at[0].set(x)

print(f(1)) # Correct

The MHLO canonicalizer is mishandling simplifications of complex scatters. This will need a fix in upstream MLIR most likely.

You are always so efficient to fix issues :heart:

This is fixed, but needs a new jaxlib release.

Jaxlib 0.3.5 was released, which should fix this issue.


1.28.0 release

Signed-off-by: MarkAckert<EMAIL_ADDRESS>

1.28.0 preview looks good, merging 👍


Export of Processes: BPMN, Zip, PDF, SVG, PNG

[x] allow the export of a process as a bpmn text file
[x] allow the export of a process as an svg image file
[x] allow the export of a process as a pdf file

[x]  allow export with page size adjusted to process size
[x] allow export with a fixed page size in landscape A4 format

[x] allow export of a process as a raster image (png/jpeg ...): 2-3 options (good, excellent)
[x] give the user options to export additional process artefacts:

[x] allow export of user task html  and images if requested (zip file with bpmn, html and images)
[x] allow export of processes referenced in call activities (in zip in case of image, svg and bpmn or in the same pdf in case of pdf)
[x] allow export of collapsed subprocesses (in zip in case of image, svg or in the same pdf in case of pdf)

[x] allow export of multiple processes in a zip file
[x] copy image to clipboard
[x] export only the selected parts of the Process diagram

if collapsed subprocess are selected, only export the subprocess if the corresponding option is selected
if inside a subprocess: only export the currect "layer" (not the parent)

[ ] consider the process images for the export, see #165
[ ] PDF-Export: Option to Export a complete Process Description with title page (Process Name and Version), the diagram, the description of the process and each element

[ ] convert the markup text of the Description field into the PDF
[ ] Each Element description can contain all Meta-Data from the property Panel: Name, Type, Image, Description, Milestones, Custom Properties
[ ] if the Name field is not filled, then use the Id (and try to show the Id inside the diagram, if possible)

@jjoderis can this issue be closed?


Add special handling for ヿ and ゟ in katakana-hiragana conversion

alternatively, we could change HIRAGANA_END and KATAKANA_END to not include these characters since they're the last ones
const HIRAGANA_END: char = '\u{309e}';
const KATAKANA_START: char = '\u{30a0}';
const KATAKANA_END: char = '\u{30fe}';

Thanks for the PR. I don't want to remove these from the ranges because they are clearly considered Hiragana and Katakana if you look at: http://www.rikai.com/library/kanjitables/kanji_codes.unicode.shtml
As for the conversion, I haven't come across ゟ or ヿ in any writing, but from a quick search you're right that they should not be converted to one another. So I would accept your original commit that adds special handling for them in the convert fns. That said, there are other cases where this would apply just the same (ヷ  ヸ  ヹ  ヺ etc), so a better way to handle this is to add new ranges for a subset inside kana for which conversion applies. Basically this range:

Something like:
const HIRAGANA_CONVERTABLE_START: char = '\u{3041}';
const HIRAGANA_CONVERTABLE_END: char = '\u{3096}';
const KATAKANA_CONVERTABLE_START: char = '\u{30a1}';
const KATAKANA_CONVERTABLE_END: char = '\u{30f6}';

depending on how you view correctness there's more that could be done, for example like converting おう to オー

ah i see you explicitly mention that you don't do that, in the code
fair enough

the problem with the range you suggested is that ゝ ゞ should be converted to ヽ ヾ

actually these characters aren't technically kana, but functional marks, it all depends on your perception of correctness

ヷ    ヸ    ヹ     ヺ
わ゛ゐ゛ゑ゛を゛

I would probably convert these like so, it's not great since these are two characters each instead of one but that's what I would do

actually now that I think about it
ヿ should probably be converted to こと and ゟ to ヨリ


Allow for using MAESTRO_APP_ID env var as appId

Hello team!
As far as I understand, the shell environment variables that can be accessed in flows need to have MAESTRO_ prefix.
https://maestro.mobile.dev/advanced/parameters-and-constants#accessing-variables-from-the-shell
But APP_ID needs to be APP_ID and cannot be MAESTRO_APP_ID.
https://maestro.mobile.dev/troubleshooting/frequently-asked-questions#how-can-i-use-the-same-flow-when-my-apps-have-different-app-ids
This makes it impossible to set the APP_ID from the shell environment variable.
So my feature request is that to add a support for the APP_ID to be read from the shell environment variables.
It would be useful if I can do this so that I don't have to pass the -e APP_ID=xx every time I run the command.
Thank you!

Hey @imjn! Thanks for taking time to create this issue.
You're right, we should allow for:
appId: ${MAESTRO_APP_ID}
---
- launchAppp
- ...

Would you be up to contribute this fix?


Add git version as suggested in #27

Use git rev-parse / describe for version managing as suggested by ShrirajHegde on #27

Ah, I was just about to create a pull request : https://github.com/ShrirajHegde/EdgeGPT-Telegram-Bot/commit/0d71690e2f1f126eecbae7ec1e25f2edf88e1770

Ok, create it and I merge it. That way we avoid adding the new library. Thanks!

Cool, also change git to recommended?

I think I've already added it in the requirements.

Yes, I have LEGACY_VERSION variable at the top to not break code for users who might download zip and use it.
If there is a way to modify this when the action runs on release, then people who download the master zip can use it without git.
(git will fail on downloaded zip as GitHub doesn't include .git directory)


Import users by group

Laravel Version: 5.4
Adldap2-Laravel Version: .3.0.4
PHP Version: 7.0

Description:
How to import users to database by group?
I'm using scopes, but i need help to import
Steps To Reproduce:

Hi @netopvh, you can see the arguments in the command itself:
https://github.com/Adldap2/Adldap2-Laravel/blob/master/src/Commands/Import.php#L20-L25
To import users based on a group using the import command, type:
php artisan adldap:import --filter="(memberof:1.2.840.1135<IP_ADDRESS>1:=cn=MyGroup,dc=corp,dc=org)"

The following prefix shown above memberof:1.2.840.1135<IP_ADDRESS>1: means it will query for all users inside the given group, as well as nested groups within that group.
Remove this if you just want immediate members imported:
php artisan adldap:import --filter="(cn=MyGroup,dc=corp,dc=org)"