Prevent status and system bar appearance on touch or on keyboard in flutter

I have asking my problem in stackoverflow but no answer or comment as for now.
My problem is a below.
I have flutter app that will be put within public in tablet or in android box. My app should be run on full screen. I have user SystemChrome.setEnabledSystemUIOverlays([]); on initState().
But, the problem is whenever user slide top or bottom, the status and system bar will be appear like the answer in stackoverflow. Public can close or exit the app in back button. Same thing goes with keyboard input appearance.
What is the way to prevent or hide status and system navigation bar until I close the app? The app can be closing on administrator access page to exit the app. Is there something that can be done on MainActivity.java? I cannot find any way currently to prevent status and system bar from user access while app is running.
In Xamarin Forms that I use before, I have below code that I apply from online:
//Remove title bar
RequestWindowFeature(WindowFeatures.NoTitle);
//Remove notification bar
Window.SetFlags(WindowManagerFlags.Fullscreen, WindowManagerFlags.Fullscreen);
//Wake screen when app is added to task
Window.SetFlags(WindowManagerFlags.TurnScreenOn, WindowManagerFlags.TurnScreenOn);
//Keep screen on without timeout
Window.SetFlags(WindowManagerFlags.KeepScreenOn, WindowManagerFlags.KeepScreenOn);

if (Build.VERSION.SdkInt >= BuildVersionCodes.Lollipop)
{
    var stBarHeight = typeof(Xamarin.Forms.Platform.Android.FormsAppCompatActivity).GetField("statusBarHeight", System.Reflection.BindingFlags.Instance | System.Reflection.BindingFlags.NonPublic);
    if (stBarHeight == null)
    {
        stBarHeight = typeof(Xamarin.Forms.Platform.Android.FormsAppCompatActivity).GetField("_statusBarHeight", System.Reflection.BindingFlags.Instance | System.Reflection.BindingFlags.NonPublic);
    }
    stBarHeight?.SetValue(this, 0);
}

I have the same problem. When users clicks on a TextFormField it shows the keyboard and status bar.

This doesn't look like a easy fix or example issue, there needs to be a solution to this issue

I wish this navigation bar would go away and die.
My use case is for a COSU/Kiosk application, where the user should not be able to use any of the navigation functions.
By setting the application as a device admin (using adminreceiver as in docs), setting kiosk mode (locktask) and using SystemChrome.setEnabledSystemUIMode(SystemUiMode.manual, overlays: []), the following is true;
Upon upward swipe of device, both navigation and status bar appears, slightly transparent - not needed
Upon downward swipe, both navigation and status bar appears, slightly transparent - not needed
(You actually can get around these by nulling input from the top/bottom x pixels in android module)
Upon text entry  (Keyboardtype inputtype.text etc), navigation bar appears. - not needed
Upon text entry (Keyboardtype inputtype.none), navigation bar DOES NOT APPEAR. yay! <- might help someone i guess.
This last option would be fine, except i need to use hardware input, which text fields do not accept input from when inputtype.none is used.
So, the upshot is, every time i need to use the hardware input a big,  black, completely empty and pointless stripe comes and overlays itself over my beautiful app.
Im not sure if this is all intended behaviour, what would be great though is if a small change could be made to allow hardware to input data through text inputType.none
like...Text inputType.hardwareOnly.. or whatever.
Thanks for your time i do hope some of this can help someone in a similar situ sorry if i sound a bit grumpy

It seems that using
adb shell wm overscan 0,0,0,-75
gets rid of that pesky black keyboard bar. I guess this can work for now, although overscan API has been deprecated in Android 11.
The black bar of death seems to be related to the keyboard only and while this overscan method works for me for now, i wonder if there will ever be a way to really get rid of it completely given Android's latest change?
While im still developing for <11, is there a way to run commands to WindowManager to set this overscan programmatically?


feat: bump release level to production/stable

Fixes #46  🦕

It looks like the last release was on April 30, so the 30 day bake time isn't yet satisfied  https://github.com/googleapis/python-workflows/commit/e9233695ced66da9fdea6cd089003df87ea13943

On hold until May 30th, 2021.


Styling cursor with url does not work, second parameter is lost after compilation

Versions
@angular/cli: 1.7.0
@angular-devkit/build-optimizer: 0.3.1
@angular-devkit/core: 0.0.28
@angular-devkit/schematics: 0.3.1
@ngtools/json-schema: 1.2.0
@ngtools/webpack: 1.10.0
@schematics/angular: 0.3.1
@schematics/package-update: 0.3.1
typescript: 2.3.4
webpack: 3.11.0

Repro steps

Create scss file with styles.
Add class which has cursor style using asset file, e.g.
cursor: url('../../../assets/cursors/grab.cur'), move;

Observed behavior
It compiles to
cursor: url(grab.b06c243f534d9c5461d1.cur);

Desired behavior
Should be
cursor: url(grab.b06c243f534d9c5461d1.cur), move;

Mention any other details that might be useful (optional)
I tried same on 1.6.8 and it worked fine. Style for cursor provided with url does not work without second parameter.

Duplicate of #9642


Fix skinned mesh normal handling in mesh shader

Objective
Update pbr mesh shader to use correct normals for skinned meshes.
Solution
Only use mesh_normal_local_to_world for normals if SKINNED is not defined.

bors r+


tickscript change alert state

Hi,
I want to get critical alert level messages, when write data if value>5 into influxdb using tickscript, my script is:
var data = stream
    |from()
        .database('data')
        .retentionPolicy('autogen')
        .measurement('table')
        .where(lambda: "dataType" == 'push')

data
    |eval(lambda: float("VC_XR"))
        .as('value')
    |alert()
        .crit(lambda: "value" > 5)
        .message('get value')
        .post('')

If push a data more than 5, like 7, I will got a critical alert level message, and push another data ,like 9, also got a critical alert level message. It looks right, then I push 5 or other less than 5 data, I can also got a critical alert level message, just for one time.
I'm trying to use critReset to fix this problem, but it doesn't work.
I don't know where's wrong, and how to fix it.
Thanks!

@CwjXFH thank you for the issue. I moved it to the kapacitor repo since it deals with tickscript.
You might also try the Slack Community (https://influxdata.com/slack) or the discourse site (https://community.influxdata.com).


Bracket Pair Colorization Settings

The settings text for Bracket Pair Colorization Settings is not intuitive.
Editor > Bracket Pair Colorization: Enabled

Even if it is not enabled. Checkmark bellow tells everything and the :Enabled text can be omitted.

Additionally, the default value could be Enabled.

It's common pattern ho have separate enabled flag in settings and also reflect it to setting name

(Not all of linked has .enabled in ID but most have)

Additionally, the default value could be Enabled.

It's debatable. People created issues because "syntax highlighting for brackets is broken" when Insiders builds has it enabled by default for testing purposes. So at this moment I doubt that it can be enabled by default for everyone.
/assign @hediet

It's debatable. People created issues because "syntax highlighting for brackets is broken" when Insiders builds has it enabled by default for testing purposes. So at this moment I doubt that it can be enabled by default for everyone.

Currently, we do not intend to enable it by default. Not only are there some bugs left to fix, some people find the colors distracting. Also, for some programming languages (such as Lean), it cannot work reliably: The assumption that brackets can be analyzed separately from the syntactical structure by just looking at tokens does not hold for all languages.

It's common pattern ho have separate enabled flag in settings and also reflect it to setting name

Yes. As such, this issue will not be fixed for bracket pair colorization alone.
However, you could open another issue to discuss changing the general pattern for all enableable features.

I agree that it should not be fixed for bracket pair colorization alone.
An issue to make enableable features settings consistent and intuitive has been opened: #132986


docs: how to docs for overrides

Description of your changes

Fixes #
I have:

[ ] Run make reviewable to ensure this PR is ready for review.

How has this code been tested

Special notes for your reviewer

Overall looks pretty good. Can we add some callout not sure if in concept docs or other place highlighting difference between ClusterResourceOverride and ResourceOverride?


typo: Double word "under"

@nschonni Thank you for for fixing these. I am merging this PR and it should be live soon.


https://cdn.pika.dev/octokit-plugin-create-pull-request is broken

https://cdn.pika.dev/octokit-plugin-create-pull-request at the moment has content:
/*
 * [Package Error]<EMAIL_ADDRESS>could not be built.
 *
 *   [1/5] Verifying package is valid…
 *   [2/5] Installing dependencies from npm…
 *   [3/5] Building package using esinstall…
 *   Running esinstall...
 *   We resolved "octokit-plugin-create-pull-request" to octokit-plugin-create-pull-request/dist-web/index.js, but the file does not exist on disk.
 *   We resolved "octokit-plugin-create-pull-request" to /tmp/cdn/_X7JFDEVVSouxbVqoIt07/node_modules/octokit-plugin-create-pull-request/dist-web/index.js, but the file does not exist on disk.
 *
 * How to fix:
 *   - If you believe this to be an error in Skypack, file an issue here: https://github.com/skypackjs/skypack-cdn/issues
 *   - If you believe this to be an issue in the package, share this URL with the package authors to help them debug & fix.
 *   - Use https://skypack.dev/ to find a web-friendly alternative to find another package.
 */

console.warn("[Package Error]<EMAIL_ADDRESS>could not be built. \n[1/5] Verifying package is valid…\n[2/5] Installing dependencies from npm…\n[3/5] Building package using esinstall…\nRunning esinstall...\nWe resolved \"octokit-plugin-create-pull-request\" to octokit-plugin-create-pull-request/dist-web/index.js, but the file does not exist on disk.\nWe resolved \"octokit-plugin-create-pull-request\" to /tmp/cdn/_X7JFDEVVSouxbVqoIt07/node_modules/octokit-plugin-create-pull-request/dist-web/index.js, but the file does not exist on disk.");
throw new Error("[Package Error]<EMAIL_ADDRESS>could not be built. ");
export default null;

Probably related to #124


Not working for 6.3

I'm using this repo https://github.com/a08381/Dalamud.SkipCutscene/raw/dist/repo.json
but it says is outdated for the latest patch :c

I have updated it for 6.3 and you can try it now.

Thank you so much! ♥


Allow AWS role based authentication to Secrets Manager and Systems Manager

What this PR does / why we need it:
This minor change that is localised to AWS Secrets Manager and Systems Manager based deployments allows configurations that utilise role based authentication (on the EC2 instance or pod level using annotations) without the requirement of providing a key and secret.
Prior to this change, role based auth will fail as not setting these values (commented out in values.yaml) will result in the chart setting these environment variables on the web container instance with empty values resulting in failure to authenticate at run-time.
This change only sets these values at the container level to be used by Concourse when they are specified in the configuration.
Which issue this PR fixes

fixes #8489

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

Hi @tareks,
Thanks for the updates, and sorry for the long time to get back to you! I'm currently traveling, getting back next week. Will get to it shortly then 😁
Thanks!

@cirocosta Take your time. I'm using something similar to option 2 that I described above in the meantime, but I have no risk of breaking any existing configuration for myself. I prefer to wait for feedback on what is best in terms of code base and user impact.

Hi @tareks ,
Sorry for the long delay!

I think option 1 looks good!
Although it'd be breaking for the sessionToken case as you mentioned, I think it's an important one as @william-tran said (regarding not checking .values.secrets directly).
That said, this would require a bump in the major number of the versioning.

Thank you!

Thanks @cirocosta . I've pushed some new commits in to follow option 1. Unfortunately, I'm pretty busy at the moment so I might need a few more days to verify that everything is working as intended. I know @Jeeppler was using SSM, so it would be good to get verification that the changes are acceptable.
In the meantime, if you and @william-tran can take a look to see if you're happy with the changes, that would be great.
Let me know if I've missed something or additional changes are required.

Thanks for putting the time on it @tareks !

/ok-to-test

Made a couple of additional commits to address the feedback. Let me know if anything else needs attention or if testing results in unexpected behavior.

Hey @william-tran ,
Any thoughts?
Thanks!

Thanks @cirocosta for helping with this! @william-tran can this be merged or are there additional changes needed?

Updated Chart version numbers based on the latest 5.0.0 app release.

Thanks!
cc @william-tran

Is there there is a reason why this isn't being merged while other PRs are?

Hi @tareks, sorry for the super long delay! I just pinged Will to ensure that it's all good on his side too so we can get this in.
That's my fault though, I should've followed up more actively. Sorry!
Meanwhile, could you please bump the versions again?
Thanks!

@cirocosta done

/hold cancel

/lgtm


Avoid duration calculation panic when clock jumps back (#10544)

Cherry-pick #10544
Release note
Fix duration calculation panics on certain platforms

/merge


Updates for the 1.1.0 release

This branch prepares everything for release, in the hopes of being able to discuss the final issues in the next meeting and finalize the release. The remaining issues to discuss and potentially merge includes:
#227 - schema version for projjson
#198 - antimeridian crossing - @jorisvandenbossche had some potential ideas.
#123 - Test data - not sure if Joris had a couple more he wanted to get in.
#229 - version compatibility suggestion that just landed, but seems pretty good.

It looks like there is another version number in the example_metadata.json file that needs to be manually updated as part of the release process (alternatively, maybe the scripts/generate_example.py script could be updated to generate this file so we have fewer places to update version numbers).
https://github.com/opengeospatial/geoparquet/blob/a684d7a72f950f290e64f057d47932ae03e457c6/examples/example_metadata.json#L138

It looks like there is another version number in the example_metadata.json file that needs to be manually updated as part of the release process (alternatively, maybe the scripts/generate_example.py script could be updated to generate this file so we have fewer places to update version numbers).

Good catch, thanks. Will fix it (and at least mention something in the release wiki).

Ok, I think this is all ready to go. Approvals are now open! Our conclusions on the call were as follows:
https://github.com/opengeospatial/geoparquet/pull/227 - (projjson schema version update) datemerged
https://github.com/opengeospatial/geoparquet/issues/198 - (antimeridian crossing) - we don't feel like we have a great solution all ready, so moving to 1.2 and retaining the official guidance of just saying 'don't do that'.
https://github.com/opengeospatial/geoparquet/issues/123 - Test data - Joris may try to get something in, but there's lots more test data, we're just missing some for 1.0, which we didn't have for 1.0 anyways, so we decided not to block on this (but he may try to get it in soon).
https://github.com/opengeospatial/geoparquet/pull/229 - (version compatibility) merged - with a bit of back and forth on 'forward compatibility'.
And I couldn't find where @tschaub pointed out that the version was off. If reviewers could make sure that there are no 1.1.0-dev versions anywhere on this branch then that'd be much appreciated.
I'm aiming for at least 4 +1's before releasing. When we've got that I'll tag the release and push it out. Thanks all!

Looks like it is the example_metadata_point.json file that has the wrong version number:
https://github.com/opengeospatial/geoparquet/blob/3048e5f30c7ec42714fb06790f3aff7282a2fd94/examples/example_metadata_point.json#L12
We could:

manually update the version number in this file as well and update the release process so that others do the same in the future
remove this file (not clear to me that it is used)
update things so that this file is generated from a corresponding example_point.parquet file (that would be generated from the generate_example.py script and would mean fewer version numbers to maintain)

Any preferences?

Good catch.
I think for now I lean towards #2, as I'm not clear what it's for, and then at some point get better test data.

Oh wait, I see, it's meant to be an example of the geoarrow encoding. So probably shouldn't just remove it. Ideally we'd have an example that is actually in the geoarrow encoding in parquet, not just the metadata.

I updated the version in example_point_metadata.json and opened #232 to suggest consolidating the example/test data.


Adding .sarif extension for validation.

I have added validation for .sarif extension.

Could you please approve workflow once more ?

is there anything from my side for now ?

Hey folks,
Not entirely sure if this is the most optimal way to validate .sarif files.
I've spent a couple of days implementing the validation myself.
Didn't want to intervene, since this issue was already assigned to @complexconst, but I was curious so I've researched and partially implemented it.
Partially - because I'm neither good, nor decent in Go ):
Here's my take.
Since files with .sarif extension are essentially JSON files, we need a way to somehow distinguish them.
In  SARIF v2.1.0 specification we can determine which fields should be present in a .sarif file, so it can be considered valid.
After skimming rather quickly through it, and playing around with .sarif files with a VSCode's SARIF Viewer extension.
I could make this observation:
Minimal .sarif file should include the following fields:

$schema - preferably should be present, my idea was to spit a warning if this field doesn't exist in the file
version - key should be present, and a value shouldn't be an empty string
runs - amount of runs should be at least >= 1
results - can be an empty slice, but it should be present (in a file, explicitly)
tool.driver.name - keys should be present, and value shouldn't be an empty string

Let me know what you think.
@complexconst @kehoecj

Ok, I will make required changes.

Please approve the workflows

Hey folks,
Not entirely sure if this is the most optimal way to validate .sarif files.
I've spent a couple of days implementing the validation myself. Didn't want to intervene, since this issue was already assigned to @complexconst, but I was curious so I've researched and partially implemented it.
Partially - because I'm neither good, nor decent in Go ):
Here's my take. Since files with .sarif extension are essentially JSON files, we need a way to somehow distinguish them. In SARIF v2.1.0 specification we can determine which fields should be present in a .sarif file, so it can be considered valid. After skimming rather quickly through it, and playing around with .sarif files with a VSCode's SARIF Viewer extension. I could make this observation:
Minimal .sarif file should include the following fields:
* **$schema** - preferably should be present, my idea was to spit a warning if this field doesn't exist in the file

* **version** - key should be present, and a value shouldn't be an empty string

* **runs** - amount of _runs_ should be at least >= 1

* **results** - can be an empty slice, but it should be present (in a file, explicitly)

* **tool.driver.name** - keys should be present, and value shouldn't be an empty string

Let me know what you think. @complexconst @kehoecj

Thanks for the thoughts @arthurflame . I completely agree that just validating serif as valid JSON doesn't provide much value. I was hoping to use a go serif library to validate both the schema and the syntax as schema validation is the direction the config-file-validator is moving towards. @complexconst Please take a look at go serif libraries to provide schema and syntax validation

I could not find any sarif library, related to our use case on the web, should I implement a custom logic to validate ?

I could not find any sarif library, related to our use case on the web, should I implement a custom logic to validate ?

Did go-sarif not work?

It explicitly does not provide a method to validate files according to the conditions mentioned above.

In my view, we should unmarshall the file as json, and check for various cases.

Does sarif.Open not work?

takes a file path and loads the sarif from that location. Returns a report and any corresponding error

I do not want to add a sarif parser to the validator tool. That should be a separate library

This is the implementation of sarif.open method, in this, it is treating .sarif file just like any other json file, and throwing error during unmarshalling
// Open loads a Report from a file
func Open(filename string) (*Report, error) {
if _, err := os.Stat(filename); err != nil && os.IsNotExist(err) {
return nil, fmt.Errorf("the provided file path doesn't have a file")
}
content, err := os.ReadFile(filename)
if err != nil {
	return nil, fmt.Errorf("the provided filepath could not be opened. %w", err)
}
return FromBytes(content)

}
// FromString loads a Report from string content
func FromString(content string) (*Report, error) {
return FromBytes([]byte(content))
}
// FromBytes loads a Report from a byte array
func FromBytes(content []byte) (*Report, error) {
var report Report
if err := json.Unmarshal(content, &report); err != nil {
return nil, err
}
return &report, nil
}

This is the implementation of sarif.open method, in this, it is treating .sarif file just like any other json file, and throwing error during unmarshalling
// Open loads a Report from a file func Open(filename string) (*Report, error) { if _, err := os.Stat(filename); err != nil && os.IsNotExist(err) { return nil, fmt.Errorf("the provided file path doesn't have a file") }
content, err := os.ReadFile(filename)
if err != nil {
	return nil, fmt.Errorf("the provided filepath could not be opened. %w", err)
}
return FromBytes(content)

}
// FromString loads a Report from string content func FromString(content string) (*Report, error) { return FromBytes([]byte(content)) }
// FromBytes loads a Report from a byte array func FromBytes(content []byte) (*Report, error) { var report Report if err := json.Unmarshal(content, &report); err != nil { return nil, err } return &report, nil }

Okay that doesn't look like it will be an option then. I've reached out to the maintainer to see if we're missing something but it looks like go-sarif doesn't provide what we need.
Here's another option that may in fact be better. We have a plan for adding JSON schema validation in addition to syntax. While we aren't ready to fully roll that out yet I think we can do that for Sarif-only since the $schema attribute is enforced. Here's what I'm thinking:

For .sarif files only use a golang JSON schema validator
In the .sarif file, check to see if it's missing $schema, if it is then fail immediately with that error
If it does have a declared $schema then load it, validate the syntax as JSON, then validate it against the sarif schema (might be able to do both in the same step)
Output the error message or return as valid

@complexconst @arthurflame WDTY?

This is the implementation of sarif.open method, in this, it is treating .sarif file just like any other json file, and throwing error during unmarshalling
// Open loads a Report from a file func Open(filename string) (*Report, error) { if _, err := os.Stat(filename); err != nil && os.IsNotExist(err) { return nil, fmt.Errorf("the provided file path doesn't have a file") }
content, err := os.ReadFile(filename)
if err != nil {
	return nil, fmt.Errorf("the provided filepath could not be opened. %w", err)
}
return FromBytes(content)

}
// FromString loads a Report from string content func FromString(content string) (*Report, error) { return FromBytes([]byte(content)) }
// FromBytes loads a Report from a byte array func FromBytes(content []byte) (*Report, error) { var report Report if err := json.Unmarshal(content, &report); err != nil { return nil, err } return &report, nil }

Okay that doesn't look like it will be an option then. I've reached out to the maintainer to see if we're missing something but it looks like go-sarif doesn't provide what we need.
Here's another option that may in fact be better. We have a plan for adding JSON schema validation in addition to syntax. While we aren't ready to fully roll that out yet I think we can do that for Sarif-only since the $schema attribute is enforced. Here's what I'm thinking:

For .sarif files only use a golang JSON schema validator
In the .sarif file, check to see if it's missing $schema, if it is then fail immediately with that error
If it does have a declared $schema then load it, validate the syntax as JSON, then validate it against the sarif schema (might be able to do both in the same step)
Output the error message or return as valid

@complexconst @arthurflame WDTY?

That does make sense to me.
Since we don't want to make a .sarif parser, I guess this approach is most likely the way to go.

This is the implementation of sarif.open method, in this, it is treating .sarif file just like any other json file, and throwing error during unmarshalling
// Open loads a Report from a file func Open(filename string) (*Report, error) { if _, err := os.Stat(filename); err != nil && os.IsNotExist(err) { return nil, fmt.Errorf("the provided file path doesn't have a file") }
content, err := os.ReadFile(filename)
if err != nil {
	return nil, fmt.Errorf("the provided filepath could not be opened. %w", err)
}
return FromBytes(content)

}
// FromString loads a Report from string content func FromString(content string) (*Report, error) { return FromBytes([]byte(content)) }
// FromBytes loads a Report from a byte array func FromBytes(content []byte) (*Report, error) { var report Report if err := json.Unmarshal(content, &report); err != nil { return nil, err } return &report, nil }

Okay that doesn't look like it will be an option then. I've reached out to the maintainer to see if we're missing something but it looks like go-sarif doesn't provide what we need.
Here's another option that may in fact be better. We have a plan for adding JSON schema validation in addition to syntax. While we aren't ready to fully roll that out yet I think we can do that for Sarif-only since the $schema attribute is enforced. Here's what I'm thinking:

For .sarif files only use a golang JSON schema validator
In the .sarif file, check to see if it's missing $schema, if it is then fail immediately with that error
If it does have a declared $schema then load it, validate the syntax as JSON, then validate it against the sarif schema (might be able to do both in the same step)
Output the error message or return as valid

@complexconst @arthurflame WDTY?

@kehoecj
Hey, just to be clear.
What do you mean by loading schema?
Does it mean that we would need to download the schema that is specified in the $schema key, parse it as JSON, and then go through the keys that are present in .sarif file we are trying to validate, and compare them with the keys retrieved from $schema?
Does it make sense, am I interpreting it correctly?

Hey, just to be clear. What do you mean by loading schema? Does it mean that we would need to download the schema that is specified in the $schema key, parse it as JSON, and then go through the keys that are present in .sarif file we are trying to validate, and compare them with the keys retrieved from $schema?
Does it make sense, am I interpreting it correctly?

@arthurflame Yes that was my thought

Hey guys, I've created a different PR with the implementation.
Please take a look.
@complexconst, @kehoecj
https://github.com/Boeing/config-file-validator/pull/217


Fixed generation of PK

In the newer version of Laravel PK is added to the CREATE TABLE statement. See https://github.com/laravel/framework/pull/49374/files Our implementation added it from commands and didn't take into account that it is marked as ignored.
Closes #76

@AdalbertMemSQL it would be great to release a new version so we could use the fix on projects

@AmirHossein Yea. Just published it.

Thanks


Testscript engine update

This pull request updates the TestScript engine to execute the examples included with the specification... with the following exceptions

multiple server tests are not supported
tests requiring rules or rulesets are not supported

I'll update the engine again in separate branch to handle the connectathon test scripts.

Need to make more updates...


[Error Handler] Use BlockingWaitStrategy instead of BusySpinWaitStrategy as the disruptor's wait strategy, to avoid high CPU usage

Description:
BusySpinWaitStrategy has been used as the waiting strategy of the disruptor - which is used in Siddhi Error Handler [1]. This waiting strategy is CPU intensive.
In order to avoid high CPU consumption, BlockingWaitStrategy can be used, similar to what has been done in StreamJunction [2].
[1] https://github.com/siddhi-io/siddhi/blob/2070f55a378b9c94415557d142a08c22f82c6f54/modules/siddhi-core/src/main/java/io/siddhi/core/util/error/handler/store/ErrorStore.java#L59
[2] https://github.com/siddhi-io/siddhi/blob/bd28ff8a9fb05d644e227a25b7a2b035117f31a8/modules/siddhi-core/src/main/java/io/siddhi/core/stream/StreamJunction.java#L288
Affected Siddhi Version:
5.1.14 and above

Fixed by https://github.com/siddhi-io/siddhi/pull/1706


Variable name is missing in Pseudo C windows

Version and Platform (required):

Binary Ninja Version: 3.2.3786-dev Personal (Build ID  85f1719)
OS: Windows
OS Version: Windows 10
CPU Architecture: x64

Bug Description:
Variable name is missing in Pseudo C windows
Steps To Reproduce:

Load the binary in attachment to Binary Ninja
Goto function address "sub_11ba"

Expected Behavior:
Variable name should be show as HLIL Windows
Screenshots:

revme.zip

Looks like the pseudo c renderer is missing a call to HighLevelILFunction::GetVariableNameOrDefault. Good find.

This will be fixed in 3.2.3791


how to use lib

do you have any examples?

hi,
there is no example as of yet. i will try to add an example

hi,
there is no example as of yet. i will try to add an example

OK thank you


Ctda 1154/header updates

Header updates
Ticket

Are the svg files being moved from the service guide or are they duplicated?
The filenames that have versions in them, e.g. diagram (1).svg, should be renamed without the version.

These files are all auto generated by running the build, should I go though and change them still?


Updated default gate display color docs

partially fixes #335
Summary
Added default gate display color docs in terra/visualizing_a_quantum_circuit.rst with reference to this

Is this still WIP? It LGTM, just wanted to make sure there wasn't more work ongoing before approving.

I guess.. Everything looks alright for now! You can approve. Thank you. @mtreinish @lzdanski @diego-plan9


Tasty exception after update

It seems the new artifacts published recently are compiled against a Scala 3.4 release candidate, which makes them not usable from Scala 3.3:
[error] error while loading resource$package,
[error] class file ox/resource$package.class is broken, reading aborted with class dotty.tools.tasty.UnpickleException
[error] TASTy signature has wrong version.
[error]  expected: {majorVersion: 28, minorVersion: 3}
[error]  found   : {majorVersion: 28, minorVersion: 4 [unstable release: 1]}
[error]
[error] This TASTy file was produced by an unstable release.
[error] To read this TASTy file, your tooling must be at the same version.
[error] The TASTy file was produced by Scala 3.4.0-RC1-bin-20230825-2616c8b-NIGHTLY-git-2616c8b.

Would it be possible to publish artifacts for Scala 3.3?

Yes, Scala 3.3.0 didn't work with Java 21 (EA). But 3.3.1 just came out, and things work fine now - releasing an updated version.


Can you please explain a bit regarding the number returns by getOptimumX?

Describe your problem/question
On the readme page of the plugin, I see an example code like this:
window.lazySizesConfig = window.lazySizesConfig || {};
window.lazySizesConfig.config.getOptimumX = function(/*element*/){
    var dpr = window.devicePixelRatio || 1;
    if(dpr > 2.5){
        dpr *= 0.6; // returns 1.8 for 3
    } else if(dpr > 1.9){
        dpr *= 0.8; // returns 1.6 for 2
    } else {
        dpr -= 0.01;
    }
    return Math.min(Math.round(dpr * 100) / 100, 2);
};

My question is related to the part where you try to return say 0.99 for 1, why should we always reduce that number a bit like that instead of returning exactly 1? I could not find it mentioned anywhere on the readme.
Add tags/keywords
optimumx

If you set optimumx to the same value as the users dpr or lower the image candidates are not constrained and only the browsers native implementation is used. This can result in to the situation that a browser with 1 dpr chooses 2 dpr image because the next lower resolution is 0.95


Sending x-goog-api-client header in Bigtable.

We missed this because it does not use GAPIC (the most recent generated Bigtable GAPIC surface is 5+ months old).

NOTE: This will fail all CI since google-gax==0.15.7 isn't out yet, but I wanted to get reviewers a chance to see it before 0.15.7 gets released tomorrow. (I have personally run the tests locally by installed google-gax from HEAD.)

@lukesneeringer Builds are green! Thanks for releasing 0.15.7. PTAL, as the gRPC layer for datastore needs the same treatment that this PR gives to Bigtable. (As an easy-to-implement stopgap while #2746 is in progress.)

@lukesneeringer Should I cut bigtable-0.23.1?

Yes, please.


Extend compiler support and improve table output

Hi,
Few additions made after using your great script!
Prevent warnings for c++11 extensions to avoid clutering output.
Compiler support is extended by accounting for clang and clang++ rather than limiting to executables with -## version number extension.
Table has been changed to show up with aligned column separators:
| Lang-uage | Oper-ation | Temp-lated | Op Time [us/#fn] | Slowdown vs [Best] | Run Time [us/#fn] | Version | Exec |
| :-------: | :--------: | ---------- | :--------------: | :----------------: | :---------------: | :-----: | :--: |
| C++       | Check      | No         | 15.0             | 1.0 [C++]          | N/A               | version | `g++` |
| C++       | Check      | No         | 26.8             | 1.8 [C++]          | N/A               | GCC     | `g++-10` |
| C++       | Check      | No         | 33.3             | 2.2 [C++]          | N/A               | 11.0.0  | `clang++` |
| C++       | Check      | No         | 383.5            | 25.5 [C++]         | N/A               | 12.0.0  | `clang++-12` |
| C++       | Check      | Yes        | 24.0             | 1.6 [C++]          | N/A               | version | `g++` |
| C++       | Check      | Yes        | 47.6             | 3.2 [C++]          | N/A               | GCC     | `g++-10` |
| C++       | Check      | Yes        | 52.2             | 3.5 [C++]          | N/A               | 11.0.0  | `clang++` |
| C++       | Check      | Yes        | 640.4            | 42.6 [C++]         | N/A               | 12.0.0  | `clang++-12` |
| C++       | Build      | No         | 134.4            | 1.0 [C++]          | 1818              | version | `g++` |
| C++       | Build      | No         | 460.0            | 3.4 [C++]          | 511               | GCC     | `g++-10` |
| C++       | Build      | No         | 219.0            | 1.6 [C++]          | 2662              | 11.0.0  | `clang++` |
| C++       | Build      | No         | 1765.1           | 13.1 [C++]         | 4564              | 12.0.0  | `clang++-12` |
| C++       | Build      | Yes        | 139.4            | 1.0 [C++]          | 1718              | version | `g++` |
| C++       | Build      | Yes        | 493.2            | 3.7 [C++]          | 372               | GCC     | `g++-10` |
| C++       | Build      | Yes        | 218.9            | 1.6 [C++]          | 2705              | 11.0.0  | `clang++` |
| C++       | Build      | Yes        | 2002.8           | 14.9 [C++]         | 4481              | 12.0.0  | `clang++-12` |

Awesome. Thanks!


Scripting section has broken links

Nakama and Unity photon has broken links, please fix :)

Feel free to submit a PR if you like.


Proposal: RBAC best-practices changes

(Ref: RBAC comments in jetstack/cert-manager#229, Helm issue #3098)
In discussion of a Jetstack PR, I have come to believe we need to at least update the best practices doc for RBAC in charts, and possibly refactor those practices.
The bit that needs updating is the current assertion that "serviceAccountName is effectively a required value".  It should be optional, but generated to a unique name if not specified.
However, additional cases not handled by the current practice are:

a service account already exists, and a new release should create RBAC or other resources that use it
a service account should be created for an RBAC-enabled chart even when RBAC is not being used

In the Jetstack PR discussion, it was proposed that service account values should be split out from RBAC (since they are used by RBAC but exist independently of it) and created or not independently, e.g.:
rbac:
  create: true

serviceAccount:
  create: false
  serviceAccountName: "foo"

This adds a bit of complexity, but resolves the issue described above, and additionally allows charts to specify and use multiple service accounts if we add a layer under serviceAccount like so:
serviceAccounts:
  client:
    serviceAccountName: client-account
    create: false
  server:
    serviceAccountName: server-account
    create: true

My personal feeling is that the additional functionality, especially of the second form, is worth the small added complexity.

Guys, I looked thru all discussions which were mentions here, but I didn't find why serviceAccount is on the root level of values and not under RBAC? Even that most of the clusters have RBAC enabled by default. But sometimes people are setting RBAC off cluster for testing purpose. And in those environments, SA creation might fail. So it looks like for rbac.enable=false, chart should not even try to create SA.

Hi @depohmel. Service Account creation won't fail even if you don't have or use RBAC. Service Accounts know nothing of RBAC, and don't care whether you have it or not 😄
This is because Service Accounts are not part of RBAC. They are a separate function that exists independent of RBAC. RBAC is something you optionally add on top, to tell the k8s API to limit access to the API for certain Service Accounts.
You still need Service Accounts, even you don't use RBAC (or you use ABAC or some future RBACv2 instead).

Oohhhh. Thanks. This was a missing part. Now it does make sense.

Fixed in #3408.

/close

good stuff!
...aaron boodles off to update all his old charts... 😢


add versioning or latest commit information to our about page

It seems like we have some problems with our deployments, or with the caching mechanism, and the frontend isn't always up-to-date on production.
It would help to have some endpoint / entry in the about page that will show the current version
Suggested steps (can be done in same PR or seperated PRs):

add the commit hash to environment variable or a file in the docker image
expose this variable

@ofirc77 sure, thanks!
I think a good starting point would be the build workflow - https://github.com/hasadna/open-bus-map-search/blob/main/.github/workflows/build.yml
Writing the commit sha to a file called version-info.json in the public folder could be a nice starting point :)


Packs (was "Virtual Roles")

Epic
Packs

Epic Title
Packs

T-shirt size default is L(arge)
XL (cause it's an Epic after all)

Business Need (the why):
NEXT should have the ability to create/aggregate bundles of roles to accurately reflect real-world usage.

User Scenarios
#85

I believe we refer to this data structure as "Pack" now.

Not migrated to new tmobile/sawtooth-next-directory repo
Just closing this here since we only have one story left to complete and it has been migrated.


ImportError: cannot import name '_unicodefun' from 'click'

Environment:

Python version: 3.10.2
Click version: 8.1.0

This used to work fine with previous version, now I get this error when running tools like black:
ImportError: cannot import name '_unicodefun' from 'click' (/lib/python3.10/site-packages/click/__init__.py)

This internal module is no longer needed for any supported version of Python, and has been removed.

when will the fixed version be out?

https://github.com/psf/black/blob/f239d227c003c52126239e1b9a37c36c2b2b8305/src/black/__init__.py#L1430-L1434
looks like you just need to use a recent black version.

@karthiknadig This is an issue with black, not with click. https://github.com/psf/black/issues/2964

@Sillocan Thanks for info and Sorry for missing the details on this.

It is an issue with click too. Namely, very short notices on deprecations.

Black 22.3.0 has already been released to address this.

There are multiple other packages affected: to me those are typer and prefect.
I've updated black and changed formatting of projects.
Now I see other parts are not working and I probably need to downgrade black and revert formatting again.
I have previously suffered from click not being able to maintain relatively stable API (7 vs 8), but these immediate deprecations in minor versions are over my understanding.

A module starting with an underscore was always internal and never meant to be relied upon / used by anyone else. so while you may have a strong opinion about removing/deprecating anything that was part of a public API, this certainly cannot applied to _unicodefun...

typer and prefect are broken because of change in public API and yes, I do have strong opinion on this.
And I have strong opinion on that function from public API that you deleted - it could be there for years in deprecated mode and nothing would break, but it was deleted.


Actualize Inc.'s fix for for issue #28

Uses bind_rows from the dplyr package as opposed to the native do.call to fix the issues highlighted in #28.

I need to test this manually (Travis and Appveyor don't have access to an Elasticsearch cluster), but I should be able to do this before the weekend is out.


ZEPPELIN-1129 Zeppelin fails to load notebooks with old date format

What is this PR for?
Old notebook fails to load due to date parse exception
What type of PR is it?
Bug Fix
What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1129
How should this be tested?
Keep a notebook with old date format in the notebook dir and reload notebooks on zeppelin home page
Questions:

Does the licenses files need update? n/a
Is there breaking changes for older versions? n/a
Does this needs documentation? n/a

Nice, good catch.
LGTM!

Test case would help to understand this change.

Thanks for the fix.
I have marked fix version 0.6.1 for issue ZEPPELIN-1129. So we can support old date format in the next minor release.
Looks good to me and merge it into master and branch-0.6 if there're no more discussions.


Separate connection specific args in EvaluateArgs.

Adds nested class PerChannelArgs within EvaluateArgs. PerChannelArgs contains channel specific attributes (includes endpoint and auth_context fields).
This helps improve performance, by ensuring that the channel attributes are constructed only once, and not on a per-call basis. We will include EvaluateArgs::PerChannelArgs in authorization filter's channel_data structure.
This PR also updates the endpoint getters logic to support IPv6 format as well.

This change is

Thanks for the review, Zhen!:)
Majority of the test failures were caused by tool failure. On rerunning these tests, we see two failures, which are irrelevant.

Thanks for the review, Jiangtao!:)


Error in docs: Fine-grained access control example using wrong syntax

https://github.com/maoosi/prisma-appsync/blob/8a93d2f7894b5dd56f4b76ab2b3758aedbd20bfd/docs/advanced/securing-api.md?plain=1#L153
https://github.com/maoosi/prisma-appsync/blob/8a93d2f7894b5dd56f4b76ab2b3758aedbd20bfd/docs/advanced/securing-api.md?plain=1#L178
After further inspection, it seems like the paths are more like the log on the bottom, rather than in the format the docs are instructing.

I've looked at the code for a little bit and it seems like the aliasing is not used at all for the shield / guard feature, relying more on match the actual GraphQL query paths, which is not very flexible.
It would be nice also for nested writes / reads to call the top level guards, e.g: I have a guard on createPhone, but I am creating a phone number through createUser/phone/**. Only that path will be checked, and not the more basic one. Ideally, it would be checked before the nested path.
https://github.com/maoosi/prisma-appsync/blob/a874bc5ce48edef53014b9015c0dda97f4884335/docs/advanced/securing-api.md?plain=1#L169
Is it possible to access the authorization and/or identity fields from within a Prisma middleware somehow?

Thanks @Tenrys! The documentation has been updated with the new syntax: https://prisma-appsync.vercel.app/advanced/securing-api.html#👉-fine-grained-access-control
In regards to protecting nested fields, you could do something like this:
return await prismaAppSync.resolve({
  event,
  shield: () => {
    return {
      '**/create*/phone{,/**}' {
        rule: false
      },
    }
  },
})

Here is an online tool to interactively create rules and check them against paths:
https://globster.xyz/?q=**%2Fcreate*%2Fphone{%2C%2F**}&f=%2FcreatePhone%2Fphone%2C%2FcreateUser%2Fphone


Codegen with printSchema fails for ForbiddenError

Hello and thank you for all your hard work.
I was trying the error plugin along with the ScopeAuthPlugin and everything is working on the server side. I tried to execute the codegen and I am gettting
PothosSchemaError: Received undefined as a type ref.

This is often caused by a circular import
If this ref is imported from a file that re-exports it (like index.ts)
you may be able to resolve this by importing it directly from the file that defines it.

If I replace schema: printSchema(schema), in codegen with `schema: 'http://localhost:4000/graphql', the codegen works.
I have a sample repo that the issue is reproducable: https://github.com/trixobird/typescript_playground/tree/pothos-codegen-auth-bug. Just execute the codegen script pnpm codegen

Thanks for the reproduction.  I was able to reproduce the issue, unfortunately I don't think this is something I'll be able to help fix.  This is a bug in graphql-code-generator (or more accurately, whatever they use to load typescript).  After some debugging, I found that their loader doesn't expose any named exports if you also have a default export.
You can run graphql-codegenerator manually with tsx
pnpm add -D tsx @graphql-codegen/core @graphql-codegen/schema-ast

then update codegen.tsx
import { printSchema, parse } from 'graphql';
import schema from './index.js';
import { codegen } from '@graphql-codegen/core'
import * as schemaAstPlugin from '@graphql-codegen/schema-ast'
import { writeFileSync } from 'node:fs';

const filename = './src/schema/generated/schema.graphql'
const result = await codegen({
  documents: [],
  schema: parse(printSchema(schema)),
  filename,
  plugins: [{
    'schema-ast': {}
  }],
  config: {
    scalars: {
      Date: 'Date',
      UUID: 'string',
    },
  },
  pluginMap: {
    'schema-ast': schemaAstPlugin
  }
})

writeFileSync(filename, result)

then run pnpm tsx src/schema/codegen.ts
But at that point, using graphql-code-generator is a bit over the top, and its better to just print the schema directly:
import { printSchema } from 'graphql';
import schema from './index.js';
import { writeFileSync } from 'node:fs';

const filename = './src/schema/generated/schema.graphql'

writeFileSync(filename, printSchema(schema))


get local provider reponse data

How can I get the response data on local provide sign in method. I tried it like this
   const  {data}  = await signIn({})
But it return undefined value

hi @prabodhana
on your Login.vue, you need to setup login
`
const { signIn, getProviders } = useAuth()
const result = ref()
result.value = await signIn('credentials', {
username: values.username,
password: values.password,
redirect: false,
callbackUrl: '/clinic'
})
`
if you want to retrieve signed in data
in other your protected page
example dashboard.vue :
`
const { data } = useAuth()
console.log(JSON.stringify(data))
`

hello @karis
const { data } = useAuth() provide the session data. Its working without an issue. I need to get my login response data. not the session response data.

hi @prabodhana
on your Login.vue, you need to setup login ` const { signIn, getProviders } = useAuth()
const result = ref() result.value = await signIn('credentials', { username: values.username, password: values.password, redirect: false, callbackUrl: '/clinic' }) ` if you want to retrieve signed in data
in other your protected page example dashboard.vue : `
const { data } = useAuth()
console.log(JSON.stringify(data)) `

sure, have you try this?
const result = ref()
result.value = await signIn('credentials', {
username: values.username,
password: values.password,
redirect: false, callbackUrl: '/clinic' })

 console.log(JSON.stringify(data))

credentials

Yes. it return undefined

@prabodhana
can you build your reproduction? stackblitz
or may be you can share your

nuxt.config.ts
login.vue
api/auth/[...].ts

@prabodhana
can you build your reproduction? stackblitz or may be you can share your
* nuxt.config.ts

* login.vue

* api/auth/[...].ts

Ok. I'm not use authjs provider. I'm used new 0.6 local-auth-provider

check this in your nuxt.config.ts
signInResponseTokenPointer: ''
this will point to your token from BE response
in my case, I got this response from BackEnd
{     "code": 200,     "message": "Success",     "data": {         "token": "eyBlablabla",         "expired": "2023-12-06T05:51:30.936795Z"     } }
so I set signInResponseTokenPointer to
signInResponseTokenPointer: '/data/token'

check this in your nuxt.config.ts signInResponseTokenPointer: '' this will point to your token from BE response in my case, I got this response from BackEnd { "code": 200, "message": "Success", "data": { "token": "eyBlablabla", "expired": "2023-12-06T05:51:30.936795Z" } }
so I set signInResponseTokenPointer to signInResponseTokenPointer: '/data/token'

Yes. But I need get some extra data from the response like this
{ "code": 200, "message": "Success", "data": { "token": "eyBlablabla", "expired": "2023-12-06T05:51:30.936795Z" , "extra_date" : '######'} }

Hey @prabodhana,
As you can see in the code, the http response is not returned so it's not possible.
Feel free to send a PR if you want! In this case, remember to update the refresh provider as well.


Release 0.3.0

We should release after current sprint that finishes 2020-04-09.

0.3.0 is out!
Hi!

The Nmstate project proudly presents:
        nmstate 0.3.0

This release contains fixes, new features and breaking changes:

=> Bug Fixes
 * Bond: Fix switch between miimon and arp_interval:
https://bugzilla.redhat.com/1806549
 * Bond: Fix switch bond mode from 1 (active-backup) to 5 (balance-tlb).
 * Bond: Allow miimon=100 when ethernet setting not included:
https://bugzilla.redhat.com/1806549
 * Bond: Allow missing arp_ip_target when ARP monitoring is disabled.
 * SR-IOV: Properly return when the device not exists.
 * SR-IOV: Fix verification due to MAC address upper or lower cases:
https://bugzilla.redhat.com/1818750
 * SR-IOV: Raise an exception when a SR-IOV parameter is not supported
by driver: https://bugzilla.redhat.com/1819588
 * Fix verification errors due to outdated values.
 * Report DNS nameservers and domains only once:
https://bugzilla.redhat.com/1806969
 * OVS: Raise an exception if the necessary services are not running.
 * Linux Bridge: Show unmanaged ports: https://bugzilla.redhat.com/1806452
 * Team: Fix verification error due to unsorted ports.
 * Raise an exception when IP configuration is enabled in slaves or ports.
 * Raise warning if interfaces exceeds 1000 in a single desired state.
 * Support route rule host without prefix length.

=> New  Features
 * Linux Bridge: Support VLAN filtering.
 * Add --version and version command in nmstatectl.
 * Support 3+ single stack DNS nameservers: https://bugzilla.redhat.com/1816043
 * Allow route rule filtering by interface when showing.

=> Breaking changes
 * Enforce keyword args for APIs functions.
 * Drop LinuxBridge_* constants support.

Please note that the packages are already available.
 * Fedora 32: https://koji.fedoraproject.org/koji/taskinfo?taskID=44222925
 * Fedora rawhide: https://koji.fedoraproject.org/koji/buildinfo?buildID=1505051
 * Copr nmstate-git:
https://copr.fedorainfracloud.org/coprs/nmstate/nmstate-git/packages/
 * Copr nmstate:
https://copr.fedorainfracloud.org/coprs/nmstate/nmstate/packages/
 * PyPi: https://pypi.org/project/nmstate/0.3.0/

 * Tarball: https://github.com/nmstate/nmstate/releases/download/v0.3.0/nmstate-0.3.0.tar.gz
 * Tarball signature:
https://github.com/nmstate/nmstate/releases/download/v0.3.0/nmstate-0.3.0.tar.gz.asc

Happy networking!


Create Pages “contact”

Automatically generated by Netlify CMS

👷 Deploy Preview for nuxt-decap-cms processing.

Name
Link

🔨 Latest commit
8184df633aca90a5922db400fbe1d0c19f894a79

🔍 Latest deploy log
https://app.netlify.com/sites/nuxt-decap-cms/deploys/66730754e9b36500089629a4


Wind object unavailable in Forecast

Wind object is unavailable in forecast.
Is it possible to add it or this information is unavailable in general ?

Yahoo doesn't provide that data through their API.


[bug]: TabsTrigger must be used within Tabs

Describe the bug
When I use this code snippet from the docs, I get the following error:
		<Tabs defaultValue="account">
			<TabsList>
			  <TabsTrigger value="account">Account</TabsTrigger>
			  <TabsTrigger value="password">Password</TabsTrigger>
			</TabsList>
			<TabsContent value="account">Make changes to your account here.</TabsContent>
			<TabsContent value="password">Change your password here.</TabsContent>
		</Tabs>

Affected component/components
Tabs, TabsTrigger
How to reproduce

Setup astro with shadcn
Use the provided code snippet
Hopefully encounter the error.

Codesandbox/StackBlitz link
I can't figure out how to pop open a terminal to install shadcn in these 2 apps...
Logs
Error: `TabsTrigger` must be used within `Tabs`
    at useContext2 (file:///Users/brad/CCClient/node_modules/@radix-ui/react-context/dist/index.mjs:38:13)
    at file:///Users/brad/CCClient/node_modules/@radix-ui/react-tabs/dist/index.mjs:95:21
    at renderWithHooks (/Users/brad/CCClient/node_modules/react-dom/cjs/react-dom-server.node.development.js:5724:16)
    at renderForwardRef (/Users/brad/CCClient/node_modules/react-dom/cjs/react-dom-server.node.development.js:5919:18)
    at renderElement (/Users/brad/CCClient/node_modules/react-dom/cjs/react-dom-server.node.development.js:6082:11)
    at renderNodeDestructiveImpl (/Users/brad/CCClient/node_modules/react-dom/cjs/react-dom-server.node.development.js:6181:11)
    at renderNodeDestructive (/Users/brad/CCClient/node_modules/react-dom/cjs/react-dom-server.node.development.js:6153:14)
    at renderForwardRef (/Users/brad/CCClient/node_modules/react-dom/cjs/react-dom-server.node.development.js:5936:5)
    at renderElement (/Users/brad/CCClient/node_modules/react-dom/cjs/react-dom-server.node.development.js:6082:11)
    at renderNodeDestructiveImpl (/Users/brad/CCClient/node_modules/react-dom/cjs/react-dom-server.node.development.js:6181:11)

System Info
macOS 14

Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues

It seems like it does this for HoverCardContent too?

Are you trying to use this in an astro template? If so, I think this might have to do with the way astro handles children components. You can try to extract this whole thing to its own react component and then load that in astro, or try to enable the experimental react children flag.

Ah yeah I figured that out. I do have to put it in a seperate component. Thank you!


Aligning methods for fetching doc in IndexReaderUtils and SimpleSearcher

InderReaderUtils and SimpleSearcher should have the same methods for access documents. Implements documentByField, which was previous missing in SimpleSearcher. Also aligns documentation so they say the same thing.

+1


Possibility to mark the job as failure?

Hi @jwgmeligmeyling ,
At first thank you for the Action
I started using your GHA in the micronaut-camunda-bpm project.
so far it works as I understood from your readme
https://github.com/arolfes/micronaut-camunda-bpm/pull/2/commits/5753bec3437d15c2da1910f84fe6168a2f6a2ec1

I personally miss a possibility to mark the job as failure run when there was at least one violation found.
Did I configure something wrong? Or will it always be green when upload succeed?
What other chance do I have to mark the build as failure?
Best Regards

It doesnt have this feature yet, but it was definitely intended to have it

This would be the extension point: https://github.com/jwgmeligmeyling/spotbugs-github-action/blob/master/src/main.ts#L81

Ok, let me try to provide an PR. Thanks for the hint

I implented a threshold where you can configure the number of annations which leads the upload to fail
But I can't create the PR because I'm not able to build the current master which relates to my local setup
Can you help me?

ok, upgrading every dependency to latest except nodejs works fine

arl@dev-vm-20:/workspace/sources/arolfes/spotbugs-github-action (master)$ rm -rf node_modules/
arl@dev-vm-20:/workspace/sources/arolfes/spotbugs-github-action (master)$ npm install
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated<EMAIL_ADDRESS>this library is no longer supported
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/jest-haste-map/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

added 725 packages from 477 contributors and audited 730 packages in 90.388s

68 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

arl@dev-vm-20:/workspace/sources/arolfes/spotbugs-github-action (master)$ npm run build

><EMAIL_ADDRESS>build /workspace/sources/arolfes/spotbugs-github-action
> tsc

arl@dev-vm-20:/workspace/sources/arolfes/spotbugs-github-action (master)$ npm run pack

><EMAIL_ADDRESS>pack /workspace/sources/arolfes/spotbugs-github-action
> ncc build

ncc: Version 0.20.5
ncc: Compiling file index.js
1022kB  dist/index.js
1022kB  [57369ms] - ncc 0.20.5
arl@dev-vm-20:/workspace/sources/arolfes/spotbugs-github-action (master)$ npm test

><EMAIL_ADDRESS>test /workspace/sources/arolfes/spotbugs-github-action
> jest

 PASS  __tests__/main.test.ts (58.646 s)
  ✓ parses file (298 ms)

Creating annotations for /workspace/sources/arolfes/spotbugs-github-action/reports/spotbugsXml.xml
/workspace/sources/arolfes/spotbugs-github-action/reports/spotbugsXml.xml has 12 violations
::debug::/home/runner/work/athena-hibernate-test/athena-hibernate-test/external/capsule-crm/src/main/java/com/pallasathenagroup/capsule/client/impl/CapsuleTargetTest.java does exists
Test Suites: 1 passed, 1 total
Tests:       1 passed, 1 total
Snapshots:   0 total
Time:        58.831 s
Ran all test suites.
arl@dev-vm-20:/workspace/sources/arolfes/spotbugs-github-action (master)$

Hello, any update on this change? It'd be a helpful feature!


Unsupported site with two languages (?)

I encountered an issue while trying to extract text from articles from the korean university site. I wanted to slurp an article, which is written on English, but I failed. I guess they have two versions of site for korean and english speakers. Therefore, when I try to slurp the page, I get the korean text. You can see an example of this issue in the article from this URL: Welcome message from the Head school.

 Slurp is an amazing plugin. I just wanted to know if there is a solution to this issue.
Obsidian: 1.6.7
OS: Windows 11
Slurp: 0.1.12

it looks like they use cookies or something similar to determine what language to load in, without checking the browser's locale.
Slurp can't do much about that since it won't have the same cookies as your browser and doesn't have a way to click the button before slurping the data. Many sites use the URL to carry locale info, eg http://.../lang=en_US for this exact reason.
This is something that the browser extension may be able to handle though. I'll link this issue there for future reference.
Thanks for the report!


aio-lib-java-events-xdm add Adobe I/O Events Extensions models.

Release a new module : aio-lib-java-events-xdm
It should hold (Adobe I/O Events) Xdm Extensions models.

decided to stuff this into aio-event-osgimapping module for now


Unify identifier and accessibility modifier

Allowing call site to specify AccessibilityID also as an Identifier using a single modifier at the same time.

Seems like an antipattern to me 🤷. If we have to have this, why not put it in the app instead?

Closed, but kept the branch for future reference


Run tests on PHP 8.1

Let's try to remove offending methods and see how many of them there are that are offending. Can you do that?

I would like to fix it but I'm not sure how.
This PR installs the Redis extension from develop and they seem to have introduced strict types like https://github.com/phpredis/phpredis/blob/aac42cd33510030bb62973f8886f4cd98b9b8003/redis.stub.php and https://github.com/phpredis/phpredis/blob/aac42cd33510030bb62973f8886f4cd98b9b8003/redis_cluster.stub.php
Not sure what happens when you run it with the older untyped extension installed. Any advice? 😊

This needs to be finished to fix issues like this https://github.com/snc/SncRedisBundle/pull/511. I think until we have that, we won't have release for PHP 8.1

Superseded by https://github.com/snc/SncRedisBundle/pull/636


support assertions on expectedEvents

The default "expectEvent(s)" does an equals comparison of the caught events and passed expected events, which fails when values are set in the commandhandler that are not under control of the caller (generated aggregateId, generated timestamps, ...).
Idea: capture the actual events as in mockitos ArgumentCaptor and then assert manually on that list of events.

I'll even suggest to implement an ObjectAssert and ListAssert for EventMessage.


F 612 add priority to category and main category

@FatemeGhasemi  due to changing the issue spec, @CarlosQ96 has created #637 , so I close this PR


fix types in help

Fix types in help on multiple commits.
If there are unnecessary changes, I will delete it.

Merged.


Using Windows 10 screen edge sweet spots does not work

Trying to use the Windows 10 "drag to sweet spots" at the edge of the screen sides to attach to half of the screen or at the top edge spot to maximize the window do not work for Hyper.
Hyper 1.3.3
Electron 1.4.16
win32 x64 10.0.15063

Moving the window with the Windows keyboard key + direction keys doesn't work either. This is specially annoying when Hyper is left out of the screen. I can't get it back, and every time hyper launches, it does so outside of the visible bounds of the screen. So, right now I'm not able to use Hyper.
Can someone at least tell me where does Hyper store its window position between application launches? If not, I'll dig into the code myself, but somebody might help me out... 😄

I'm having the same issue with Windows Keys. Seems odd, don't have this issue with other Electron apps.

This is already working in the latest version 1.4.3, I can confirm that. Please see #2094 also for reference as I think they were related.

@axelitus After reading your comment in #2094, I was desesperatly  searching this issue. That was because you had already closed it 😍
Thank you so much! 🙏

Haha sorry, helping a bit to clean up the open issues. I've also referenced this issue from #2094 for anyone that comes across that has any of the issues described in one or the other.


Downgrade from Stateless Mode to Backup/CDN Modes

A Sync option to downgrade from Stateless mode to Backup/CDN modes would be very useful.

Hello @matthewlenz
You can change mode to Backup or CDN

And when you re-sync - all media will be stored locally.
Closing the ticket.


Link to cloud signup page rather than the console

It provides more context for new users

Looks good to me. Let's 🚀


USHIFT-1956: Reinstate greenboot fail fast checks

Which issue(s) this PR addresses:

Closes #

/lgtm

/test microshift-metal-tests-arm


Make changes to WLS <IP_ADDRESS> Domain image to comply with environment variables for Domain creation.

Resolve Issues #452 and #449.
Made following Changes
1- Create WebLogic domain at runtime.
2- Define environment variables at runtime in file domain.properties and pass them in at runtime by using --env-file option.  Set:
ADMIN_NAME, ADMIN_PASSWORD, ADMIN_USERNAME, ADMIN_HOST, DOMAIN_NAME, MS_PORT, PRODUCTION_MODE, DEBUG_FLAG, CLUSTER_NAME.
3- Externalize DOMAIN HOME by mapping the domain to a data volume so that Admin Server and Managed Servers can all write/read to the same DOMAIN_HOME.

I am curious whether the Manager Server could join the domain successfully after this changes, I do not see related changes in createServer.sh
docker run -e ADMIN_PASSWORD="welcome1" --link wlsadmin:wlsadmin -p 7002:7002 12212-domain-debug createServer.sh
I developed a same patch, Admin server could startup successfully and manager server always failed to join due to invalid username or password. I do provide the correct username and password indeed. I really have no idea about about what is going wrong there.

@bluzed try again make sure you follow instructions in README

@mriccell I wanna know whether the Manager Server could join the domain successfully after this changes, if so that would be great, I can read it to know what is going wrong in my side after merging.

@bluezd yes the Managed Server can join the domain/cluster after these changes.


Retrieve project main class / class path

In a java language server there are plugins that allow extra functions like
vscode.java.resolveMainClass and vscode.java.resolveClasspath commands. Is there a similar one for C#?

This is a long shot seeing as how I don't know what those Java functions are doing, but could you perhaps be looking for IServiceProvider.GetService()? We use it do so something like:
WorkspaceService workspaceService = languageServer.Services.GetService<WorkspaceService>();

It resolves the instance of the "service" / class given the type, as long as it was previously registered.


ROX-20493, ROX-20494, ROX-20495: Miscellaneous vulnerability exception validations

Description

ROX-20493: Prohibit changing a deferral vuln exception to false-positive and vice-versa. The updated function UpdateRequest is protected by the feature flag and is used by v2 APIs only.
ROX-20494: Only allow deleting vulnerability exceptions or updates in pending state.
ROX-20495: Prohibit updates that do not change exceptions. Updates go through the approval process, so the updates that do not change the original exception can be annoying for admin, so prohibit such updates.

Checklist

[ ] 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)

If any of these don't apply, please comment below.
Testing Performed
Unit test

couple of nits.
I do have a suggestion that is way out of scope of this PR. There are a lot of moving pieces in the datastore, so I was wondering if we should have a ticket to either refactor datastore_impl_test to use the actual database instead of mocks or create a new one that does a subset of things against the actual database. I know many of our datastore tests use the actual database. This datastore is pretty complicated so I'm thinking that might be beneficial here to make it more integration test than unit test.

We have tests that test complete workflow here. I think the code that doesn't actually touch the database like in this PR the pre-requisites need not be tested against the database.

couple of nits.
I do have a suggestion that is way out of scope of this PR. There are a lot of moving pieces in the datastore, so I was wondering if we should have a ticket to either refactor datastore_impl_test to use the actual database instead of mocks or create a new one that does a subset of things against the actual database. I know many of our datastore tests use the actual database. This datastore is pretty complicated so I'm thinking that might be beneficial here to make it more integration test than unit test.

We have tests that test complete workflow here. I think the code that doesn't actually touch the database like in this PR the pre-requisites need not be tested against the database.

That works.  Those manager tests cover the type of thing I was looking for.


Support for catalog in common catalog format

Hello Luke @kixelated , thank you for your work, we ( Gwendal Simon , Tilson Joji ) from Synamedia would like to convey our interest in contributing.
With this PR have attempted to support formatting the catalog as per common catalog format defined in spec https://datatracker.ietf.org/doc/html/draft-wilaw-moq-catalogformat-02
A PR has been requested in moq-rs as well to support this change, here is the link to the PR https://github.com/kixelated/moq-rs/pull/174
Kindly review and let us know your thoughts.

Thanks for this, @TilsonJoji (and @gwendalsimon) - the catalog support we have right now is still mostly a placeholder and the format is left over from before the current common catalog spec existed, so I see no reason not to update it both here and in moq-pub!

Thank you @englishm.
Thank you @kixelated  for the detailed review and the feedback . I will address the comments and update the PR.

Hello Luke @kixelated , i have attempted to address the comments and followed the latest version of the spec , kindly review and let me know your thoughts.

Thanks @TilsonJoji , I'll take a look hopefully tomorrow.

@TilsonJoji I pushed some changes inline. It passes the typescript checks (npm run build) but I haven't actually tested it yet, nor updated the Rust side.

I made some PRs on the catalog Github if you want to voice any opinions after having implemented this: https://github.com/moq-wg/catalog-format

Hello Luke @kixelated , thank you for the refactoring the code with commit 7baad29.
Regarding moq-rs , I performed a test and have updated the RUST PR .
The commits in moq-rs PR are [commit to address PR comments in moq-rs , commit to address cargo build warning , and commit to update RS to work with your refactoring commit .
The commits in moq-rs have passed the PR build check. Kindly have a look at the moq-rs PR  as time allows.
Regarding moq-js , Have done a minor tweak to your commit to fix issue observed in UT and have pushed the changes in this commit.

Hello Luke @kixelated , commit b8d5a80 to update moq-js namespace access to make it compatible with commit 73bad56 f05c00e in PR : https://github.com/kixelated/moq-rs/pull/174


add workspace folder as target

What this PR does / why we need it
use GITHUB_WORKSPACE as default target folder for OCM binary download

@hilmarf I guess it needs to be the WORKSPACE and not the TARGET as PATH, or? PATH contains the folder, whereas TARGET here specifies the execution target, the binary, or?

superseded by https://github.com/open-component-model/ocm-setup-action/pull/13


Fix Linux build of Xenoncat solver

I'm sure you already have this in hand, but I was impatient so did it for you... feel free to amend or ignore!

Hi @ngreatorex. This looks great. But I have tried it on a VM and two real machines (Ubuntu 14.04 and 16.04) and it fails to build. Can you explain how did you make your build work?


CAMEL-11259 - Add Distinct Query support to camel-mongodb

This pull request is sync'd as of 2055 EST.  This pull request contains new functionality to allow for distinct mongodb queries and also unit tests to support optional query parameters.

Updated the code based on your suggestions and also sync'd with the master branch from Came's github repo.

There is also a camel-mongodb3 component. I wonder if this should also have such a functionality as this? If so you are welcome to work on a new PR for that

Thanks for the PR it has been merged. Do you mind closing this?


Eye Tracking no longer working

Before VRCFT 5.0, I was getting no issues with the eye tracking and for months I could launch the application and my eye tracking worked immediately for my avatar that I put in custom eye tracking for.
Now after the 5.0 update and with this module it began working with avatars that had simple eye look, which was awesome. I could actually look around and blink with pretty much any avatar. However, it is so inconsistent with getting the module or the application to work anymore. I've spent tens of hours reinstalling, unblocking .dlls, using custom libs and the module within the VRCFT application itself just to try and get the eye tracking to start working, but only when I get super lucky does it just magically turn on sometimes. It's so inconsistent, sometimes I can restart everything a few times then maybe it may work, other times I'll spend hours reinstalling everything and restarting my PC and could yield no results.
Every day I've been getting on for the past few weeks it just doesn't work immediately anymore, maybe only once or twice out of this whole time and it's driving me mad so I have to make a post, since I don't know what else to do. I've meticulously followed everything I've been recommended to do in the VRCFT Discord to no real avail.
I've even fully disabled my firewall and everything just trying to get this working but it just won't. I don't know why.
Attached below is VRCFT application examples, and showing that everything for my sensors are on for Omnicept.
Please help

In the photo I'm having to use a public model with basic eye look, but even those avatars should be able to look around and blink but they aren't even. I can't test my custom made avatar with my own custom made eye tracking at the moment, but i'm sure it wouldn't work right either, I consistently get this issue now.

Is the first screenshot provided an example of when the Avatar is visibly working, or not? Do you notice anything special when this issue occurs, or when it works? All the messages are NOT coming in through the OSC Debug, right?
I'm also noticing that you're using this alongside with HRtoVRChat_OSC, can you verify that you aren't having port blocking issues with that? (For example, not running an OSC proxy [like VOR] can cause issues with them trying to bind on the same port, but I could've sworn VRCFT had some sort of patch for that, but I don't remember)
I mean this issue sounds really weird to me, and I just honestly could not tell you what could cause this. This is the first time I'm hearing of this issue. I myself do not have an Omnicept so it's really hard for me to debug this software; all I have is the simulator app, and it just seemed to work with it just fine, and for other people who have tested it. If you find any more information, please let me know!

In all screenshots there the eye tracking wasn't functioning or turning on. I've started to open up the the eye tracking debug in VRChat's settings where you can see a blue ball wherever you look to, which was not showing up at all. I don't notice anything out the ordinary, with it working or not, I don't really find out until I'm in game. With the built-in Console that VRCFT uses, it may show something concerning, like how many the tokens come back as null, but I wasn't sure if that really meant anything. In VRC OSC Debug I don't get messages at all, and it asks me to restart the application or let it through the firewall (which it is), only when I reset OSC by turning it off and on, then I get eye tracking values but they are stuck at 0%.
HRtoVRChat is something I occasionally use, but I 95% of the time never even open that application so it's always closed when I start the game at first. But maybe that could be an issue, I could try removing it off of the Authorized Clients List and see if that helps, but even before 5.0 I would run both applications at the same time when I got my headset for a couple months. The gasket is less comfortable so I just switch over to the cloth so that's why I don't use the heart rate too much, unless I'm being active. It has worked a couple times but that application was giving me issues at first but not the last couple times I've used it.
I did eventually get it working after 2 hours of reinstalling VRCFT, Resetting the application, and restarting my PC but again after I reinstalled it like 5 times it suddenly started working again. So when I go through that process I can never pinpoint what the issue is because everything I try specifically doesn't really seem to work. I wish I could see through the Omnicept software that the Eye Tracking is on and working, but the only way I can try that is by Calibrating Eye Tracking but I've only ever had to do that once before and it keeps that calibration even after all of these uninstalls of the VRCFT Software. Every time I run the Calibration it does successfully work so I feel like it isn't the Omnicept itself.  I think that is why it is either the module, VRCFT, or the port not getting anything like it should. I do always get the whole 0ms Outgoing when it isn't working.
Also small side note, I have a custom avatar where I can check Dilation and such, which consistently stays between 30-95% when it is working. When it doesn't work it is at 0% but lately I started seeing this crazy number when it doesn't work sometimes I'll post a picture of it.

Once it is on and working, it stays working perfectly the whole time for that session, the only real issue seems to be it starting, that's the only real inconsistency. I don't know what isn't launching, or not getting information even though all software and osc is on.
I also have converted my Omnicept to be tracked by a tracker so it has base station tracking but I'm not sure if that causes any hiccups, I hope not because Base Station tracking is needed in in my opinion. Though on the earlier version on VRCFT it did work consistently, even with the base tracking conversion.
Thank you for helping me out with this! I just wish I could pinpoint the issue because it's hard to tell where it's deciding to not work with.

With the built-in Console that VRCFT uses, it may show something concerning, like how many the tokens come back as null, but I wasn't sure if that really meant anything

This sounds really concerning, assuming these are CancellationTokenSources. Do you have any screenshots/logs of this?

I could try removing it off of the Authorized Clients List and see if that helps

probably not

HRtoVRChat is something I occasionally use, but I 95% of the time never even open that application so it's always closed when I start the game at first.

Then there should be no issue there.

I did eventually get it working after 2 hours of reinstalling VRCFT, Resetting the application, and restarting my PC but again after I reinstalled it like 5 times it suddenly started working again.

Has it been consistently working? Any logs anywhere that point out when it stops working?

When it doesn't work it is at 0% but lately I started seeing this crazy number when it doesn't work sometimes I'll post a picture of it.

This number is the minimum value for a signed 32-bit integer (int), -2,147,483,648, which can also be referenced by Int32.MinValue. Afaik, I don't use minvalue anywhere (please correct me if I'm wrong), so that could either be VRCFT or Omnicept, but more probably Omnicept.

I was referring to this, about the null token.

However on booting it up today, it started without a single issue this time and it just worked. The public key token is still null, so that must be nothing.
I don't know where to pull logs besides from that VRCFT screenshot I've shown you earlier, which doesn't really seem to provide any information about anything not working when it isn't.
Sometimes I'm lucky and it just works or I'll have to uninstall/restart my pc for an hour to get it working. So I'm really unsure. I booted everything up in the same order as I did yesterday and all, and this time it worked, but yesterday it didn't. I don't know, it's just being inconsistent for me.
I personally don't know anyone else with an Omnicept myself, so I don't know, maybe it could just be me or something do with my pc, but it's all so confusing because as I said when it stops working, I have no clue why.

I was referring to this, about the null token.

Never mind, that's not to worry.

I don't know where to pull logs

Latest log file can be found at %appdata%/VRCFaceTracking/latest.log
Not too sure I can deduce an issue here. I hate pulling a "it works on mine and other people's computers," but I mean there's just not much I'm working with here lol. I'll leave this open, but let me know if it happens again. Hopefully there can be more to investigate there.

I've had this issue a lot of times where it does stop working, but the last 3 times it has been working well with no problems, and I really haven't done anything different. I just wanted to let you know.
Thank you for your support though, it's much appreciated! I pray it keeps working this time.


Multiple aliases

Hi, thank you very much for developing this useful tool!
One small feature I've been missing is the ability to specify multiple aliases (which would, I guess, expand to multiple host definitions). I haven't found anything about this in the docs, so I'm assuming it doesn't exist yet. It would be great for defining multiple names for a server (like, the name of the host, as well as the service that provides it, which is my usecase)
Thanks for considering! :)

Hi, I'm happy to hear you find this tool useful. :)
When it comes to the feature request, I believe what you are looking for is possible to achieve already, please look at the second bullet in the tips and tricks (alias can accept multiple space separated entries):
https://github.com/dankraw/ssh-aliases#tips-and-tricks

Ah, seems I missed that! I tried with commas but that didn't work. This works perfectly for me :)
Thanks for the quick reply!


Having multiple fullstops in a game's title will cause it to crash upon trying to test it

Tested versions
v4.3.beta1.official [a4f2ea91a]
System information
Godot v4.3.beta1 - Windows 10.0.26227 - Vulkan (Forward+) - integrated AMD Radeon(TM) Vega 8 Graphics (Advanced Micro Devices, Inc.; 31.0.21024.2004) - AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx (8 Threads)
Issue description
game fails to launch with multiple fullstops in the title.
Steps to reproduce

put two fullstops in the title of your game

Minimal reproduction project (MRP)
game-with-two-fullstops.zip

whoops, just found out it was multiple fullstops that did it instead of one. silly me

https://github.com/godotengine/godot/assets/82868738/58d550ef-4ff9-48f2-9825-4d689284f574


pgbouncer-rr patch install fails with pgbouncer release v1.11.0

For now, workaround is to checkout pgbouncer v1.10.0 and use that version for pgbouncer-rr.
Replace the documented pgbouncer clone command with:
git clone https://github.com/pgbouncer/pgbouncer.git --branch "pgbouncer_1_10_0"
before installing the patch.

Compatability with pgbouncer 1.12 committed in https://github.com/awslabs/pgbouncer-rr-patch/commit/5d5cd0f57601717118dd8ec6c7f34c9537854a6e


stylePreprocessorOptions not used for unit tests

Please provide us with the following information:

OS?
Mac OSX El Capitan
Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:

angular-cli: 1.0.0-beta.26
node: 6.9.1
os: darwin x64
@angular/common: 2.4.4
@angular/compiler: 2.4.4
@angular/core: 2.4.4
@angular/forms: 2.4.4
@angular/http: 2.4.4
@angular/platform-browser: 2.4.4
@angular/platform-browser-dynamic: 2.4.4
@angular/router: 3.4.4
@angular/compiler-cli: 2.4.4
@angular/tsc-wrapped: 0.5.1
Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.

Make use of the recently added "stylePreprocessorOptions" in angular-cli.json in combination with stylus (https://github.com/angular/angular-cli/pull/4003).
This is my config:
"stylePreprocessorOptions": {
        "includePaths": [
          "../node_modules/bootstrap-styl",
          "../node_modules/bootstrap-styl/stylus",
          "styles"
        ]
      },

In a *.component.styl stylus file I added @import('globals') which resolves to src/styles/globals.styl. With ng serve it works, but ng test fails.
The log given by the failure.
Error: Module build failed: Error: /Users/patrick/dev/leanix-pathfinder-web/src/app/app.component.styl:1:25
     1| @require('lib/constants')
  ------------------------------^
     2|
     3| .App
     4|   padding-top: 51px

  failed to locate @require file lib/constants.styl

      at CachedPathEvaluator.visitImport (/Users/patrick/dev/leanix-pathfinder-web/node_modules/stylus-loader/lib/evaluator.js:157:21)
      at CachedPathEvaluator.Visitor.visit (/Users/patrick/dev/leanix-pathfinder-web/node_modules/stylus/lib/visitor/index.js:28:40)
      at CachedPathEvaluator.Evaluator.visit (/Users/patrick/dev/leanix-pathfinder-web/node_modules/stylus/lib/visitor/evaluator.js:160:18)
      at CachedPathEvaluator.Evaluator.visitRoot (/Users/patrick/dev/leanix-pathfinder-web/node_modules/stylus/lib/visitor/evaluator.js:707:27)
      at CachedPathEvaluator.Visitor.visit (/Users/patrick/dev/leanix-pathfinder-web/node_modules/stylus/lib/visitor/index.js:28:40)
      at CachedPathEvaluator.Evaluator.visit (/Users/patrick/dev/leanix-pathfinder-web/node_modules/stylus/lib/visitor/evaluator.js:160:18)
      at CachedPathEvaluator.Evaluator.evaluate (/Users/patrick/dev/leanix-pathfinder-web/node_modules/stylus/lib/visitor/evaluator.js:247:15)
      at Renderer.render (/Users/patrick/dev/leanix-pathfinder-web/node_modules/stylus/lib/renderer.js:86:26)
      at /Users/patrick/dev/leanix-pathfinder-web/node_modules/stylus-loader/index.js:163:12
      at tryCatchReject (/Users/patrick/dev/leanix-pathfinder-web/node_modules/when/lib/makePromise.js:840:30)
      at runContinuation1 (/Users/patrick/dev/leanix-pathfinder-web/node_modules/when/lib/makePromise.js:799:4)
      at Fulfilled.when (/Users/patrick/dev/leanix-pathfinder-web/node_modules/when/lib/makePromise.js:590:4)
      at Pending.run (/Users/patrick/dev/leanix-pathfinder-web/node_modules/when/lib/makePromise.js:481:13)
      at Scheduler._drain (/Users/patrick/dev/leanix-pathfinder-web/node_modules/when/lib/Scheduler.js:62:19)
      at Scheduler.drain (/Users/patrick/dev/leanix-pathfinder-web/node_modules/when/lib/Scheduler.js:27:9)
      at _combinedTickCallback (internal/process/next_tick.js:67:7)
      at process._tickCallback (internal/process/next_tick.js:98:9)
  at src/test.ts:279131

Mention any other details that might be useful.
I have found that in models/webpack-build-test.js the stylus-load has no configuration as it does here: https://github.com/angular/angular-cli/pull/4003/files#diff-422be7f05c4af54ddd02152bfc358260R79
I think it should be added there as well!?

Thanks! We'll be in touch soon.

Yeap, bug. Sorry for that :/
I'll close in favor of https://github.com/angular/angular-cli/issues/3605, since it's the same 'thing' so to speak.

Perfect, thank you.
Appreciate your work!


Blacklisting incoming requests

@markmacgillivray is this really a september thing? Seems like it could wait...

No requirement for this if requests do not continue far into the future.


Cat and Dog image classifier (issue)

Describe the Issue
for probability, answer in zip(probabilities, answers):
if round(probability) == answer:
correct +=1
///// this is wrong , code in line 11
///// it should be
for probability, answer in zip(probabilities, answers):
if np.round(probability) == answer:
correct +=1
Affected Page
https://www.freecodecamp.org/learn/machine-learning-with-python/machine-learning-with-python-projects/cat-and-dog-image-classifier
Your code
# 11
answers =  [1, 0, 0, 1, 0, 0, 0, 0, 1, 1, 0,
            1, 0, 1, 0, 1, 1, 0, 1, 1, 0, 0,
            1, 1, 1, 1, 1, 0, 0, 0, 0, 0, 1,
            1, 0, 1, 1, 1, 1, 0, 1, 0, 1, 1,
            0, 0, 0, 0, 0, 0]

correct = 0

for probability, answer in zip(probabilities, answers):
  if np.round(probability) == answer:
    correct +=1

percentage_identified = (correct / len(answers)) * 100

passed_challenge = percentage_identified >= 63

print(f"Your model correctly identified {round(percentage_identified, 2)}% of the images of cats and dogs.")

if passed_challenge:
  print("You passed the challenge!")
else:
  print("You haven't passed yet. Your model should identify at least 63% of the images. Keep trying. You will get it!")

Expected behavior
for probability, answer in zip(probabilities, answers):
if np.round(probability) == answer:
correct +=1
Screenshots
No response
System

Device: [e.g. iPhone 6, Laptop]
OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04]
Browser: [e.g. Chrome, Safari]
Version: [e.g. 22]

Additional context
No response

hey,could u ellaborate the problem.

while running this code in google colab , google colab is showing error
11
answers =  [1, 0, 0, 1, 0, 0, 0, 0, 1, 1, 0,
1, 0, 1, 0, 1, 1, 0, 1, 1, 0, 0,
1, 1, 1, 1, 1, 0, 0, 0, 0, 0, 1,
1, 0, 1, 1, 1, 1, 0, 1, 0, 1, 1,
0, 0, 0, 0, 0, 0]
correct = 0
for probability, answer in zip(probabilities, answers):
if round(probability) == answer:
correct +=1
percentage_identified = (correct / len(answers)) * 100
passed_challenge = percentage_identified >= 63
print(f"Your model correctly identified {round(percentage_identified, 2)}% of the images of cats and dogs.")
if passed_challenge:
print("You passed the challenge!")
else:
print("You haven't passed yet. Your model should identify at least 63% of the images. Keep trying. You will get it!")
////////////////////////////
the corrected is
11
answers =  [1, 0, 0, 1, 0, 0, 0, 0, 1, 1, 0,
1, 0, 1, 0, 1, 1, 0, 1, 1, 0, 0,
1, 1, 1, 1, 1, 0, 0, 0, 0, 0, 1,
1, 0, 1, 1, 1, 1, 0, 1, 0, 1, 1,
0, 0, 0, 0, 0, 0]
correct = 0
for probability, answer in zip(probabilities, answers):
if np.round(probability) == answer:
correct +=1
percentage_identified = (correct / len(answers)) * 100
passed_challenge = percentage_identified >= 63
print(f"Your model correctly identified {round(percentage_identified, 2)}% of the images of cats and dogs.")
if passed_challenge:
print("You passed the challenge!")
else:
print("You haven't passed yet. Your model should identify at least 63% of the images. Keep trying. You will get it!")
it should be np.round , on doing np.round and then running in the google colab , we are getting the correct syntax

Closing as stale


WIP: Add entity_picture_template options to Template Cover, Template Light, Template Sensor, and Template Switch

Description:
This is a work-in-progress PR to provide an entity_picture_template configuration option to all Template platforms (except for the Template Binary Sensor, which derives its iconography from its device class).
Like icons, the use case is to be able to change entity pictures based on Jinja templates – for example, a device tracker might show a colorized version of a person's picture when they're home and a monochromatic version when they aren't.
Additionally, this PR adds icon_template support to the Template Light, since it wasn't present.
Related issue (if applicable): N/A
Pull request in home-assistant.github.io with documentation (if applicable): TBD
Example entry for configuration.yaml (if applicable):
cover:
  - platform: template
    covers:
      garage_door:
        friendly_name: "Garage Door"
        value_template: "{{ states('sensor.garage_door')|float > 0 }}"
        open_cover:
          service: script.open_garage_door
        close_cover:
          service: script.close_garage_door
        stop_cover:
          service: script.stop_garage_door
        entity_picture_template: >-
          {% if is_state('cover.garage_door', 'True') %}
            /local/images/garage_open.png
          {% else %}
            /local/images/garage_closed.png
          {% endif %}

light:
  - platform: template
    lights:
      theater_lights:
        friendly_name: "Theater Lights"
        level_template: "{{ sensor.theater_brightness.attributes.lux|int }}"
        value_template: "{{ sensor.theater_brightness.attributes.lux|int > 0 }}"
        turn_on:
          service: script.theater_lights_on
        turn_off:
          service: script.theater_lights_off
        set_level:
          service: script.theater_lights_level
          data_template:
            brightness: "{{ brightness }}"
        entity_picture_template: >-
          {% if is_state('light.theater_lights', 'True') %}
            /local/images/light_on.png
          {% else %}
            /local/images/light_off.png
          {% endif %}

sensor:
  - platform: template
    sensors:
      sunrise:
        value_template: "{{ states.sun.sun.attributes.next_rising }}"
      entity_picture_template: >-
          {% if is_state('sensor.sunrise', 'True') %}
            /local/images/sunrise.png
          {% else %}
            /local/images/sunset.png
          {% endif %}

switch:
  - platform: template
    switches:
      skylight:
        value_template: "{{ is_state('sensor.skylight', 'on') }}"
        turn_on:
          service: switch.turn_on
          data:
            entity_id: switch.skylight_open
        turn_off:
          service: switch.turn_on
          data:
            entity_id: switch.skylight_close
        entity_picture_template: >-
          {% if is_state('switch.skylight', 'True') %}
            /local/images/on.png
          {% else %}
            /local/images/off.png
          {% endif %}

Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] Tests have been added to verify that the new code works.

Forgot to do a force push with the last rebase... 😞 Going to close this out and re-open a new PR.