Incorrect path for app image (in higher JDK versions?)

When creating a pkg using packagePkg task, after installation on my Mac it is installed like this:

This is incorrect, should not be in a subfolder.
Maybe it's only for the newer JDK version, not sure. This was with JDK 17.
I originally found the issue while working on https://github.com/JetBrains/compose-jb/pull/1613. Because this bug would cause the build to fail completely in that case.
I added a workaround for building with appStore = true:
https://github.com/JetBrains/compose-jb/blob/ca382431c57f76e48ca27be531b3898879ae556b/gradle-plugins/compose/src/main/kotlin/org/jetbrains/compose/desktop/application/tasks/AbstractJPackageTask.kt#L304-L309
However, the screenshot shown in this issue is without building for the app store, so the workaround should be extended to all build/packages.
Maybe it's only an issue for a certain JDK version. Not sure if any other platforms have this issue.

@AlexeyTsvetkov

I am still experiencing this issue, when I install my application from the pkg file built with buildPkg it is installed into /Applications/app/Myapp.app subfolder instead of /Applications/Myapp.app (without appStore = true)
Is there a solution or a workaround?

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Upgrade to SpringBoot 2.6

Upgrade to SpringBoot 2.6.

SpringBoot 2.6 is not yet released, but a snapshot is already available: https://docs.spring.io/spring-boot/docs/2.6.0-SNAPSHOT/api/.
A M1 release of 2.6 is getting prepared for release in July: https://github.com/spring-projects/spring-boot/milestone/214

SpringBoot 2.6 M2 was released: https://spring.io/blog/2021/08/19/spring-boot-2-6-0-m2-is-now-available

Spring Boot 2.6 RC1 was released: https://spring.io/blog/2021/10/21/spring-boot-2-6-0-rc1-is-available-now
Spring Boot 2.6 is scheduled for release on the 18th Nov.

Spring Boot 2.6 is available: https://spring.io/blog/2021/11/19/spring-boot-2-6-is-now-available

SpringBoot 2.5 will only be supported until May 2022: https://spring.io/projects/spring-boot#support

SpringBoot gradle dependencies: https://github.com/spring-projects/spring-boot/blob/v2.6.2/spring-boot-project/spring-boot-dependencies/build.gradle


RobotModel Status Error in default simulation setting running SLAM

I am following the default installation guide and setting, and trying the SLAM with ros2 launch turtlebot4_ignition_bringup ignition.launch.py slam:=sync nav2:=true rviz:=true.
I encounter the bug that left_wheel, 'right_wheel', 'wheel_drop_left', 'wheel_drop_right' transformations are not correct. (No transformation from [left_wheel], etc.)
The console log message:
[rviz2-15]          at line 156 in /tmp/binarydeb/ros-galactic-tf2-0.17.4/src/buffer_core.cpp
[rviz2-15] Warning: Invalid frame ID "right_wheel" passed to canTransform argument source_frame - frame does not exist
[rviz2-15]          at line 156 in /tmp/binarydeb/ros-galactic-tf2-0.17.4/src/buffer_core.cpp
[rviz2-15] Warning: Invalid frame ID "wheel_drop_left" passed to canTransform argument source_frame - frame does not exist
[rviz2-15]          at line 156 in /tmp/binarydeb/ros-galactic-tf2-0.17.4/src/buffer_core.cpp
[rviz2-15] Warning: Invalid frame ID "wheel_drop_right" passed to canTransform argument source_frame - frame does not exist

See https://github.com/iRobotEducation/create3_sim/issues/125


json_encode error

there's a error when I use phpjs json_encode in my project
I found it,s undefined of  this.window.JSON,
is there anything wrong with dependencies?
Unexpected error type in json_encode()
at Object.exports.json_encode (/data/www/htdocs/tsb-api/node_modules/phpjs/build/npm.js:3842:15)

Might you have the steps to reproduce for us?


Issues with package imports after migrating to crd2pulumi 1.5.1

What happened?
Quite similar to https://github.com/pulumi/crd2pulumi/issues/142
Example
Generating types from https://github.com/prometheus-operator/prometheus-operator/releases/download/v0.76.2/bundle.yaml causes to create use types like pulumi.StringMapArrayMapOutput which doesn't really exist in pulumi
Output of pulumi about
$ crd2pulumi version
v1.5.1

Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Thanks for reporting this issue. We'll add this to our backlog to resolve!


search-service never completes deployment

Please provide us with the following information:

This issue is for a: (mark with an x)
- [x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce
using github spaces with project code version as of 2/1/24 (today)
successfully run azd auth login
run azd env new - use a new project name/rg.
run azd up with no changes to code.
select east us for both the services and openai.
starts to build deployment, gets to search-service - runs for > 1 hour, never completes.
in azure portal, I killed the deployment and tried over again. same.
Any log messages given by the failure

Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

azd version?

run azd version and copy paste here.

Versions

Mention any other details that might be useful

Thanks! We'll be in touch soon.

:( When you get that error, could you try to log a support ticket from the Portal? Oftentimes the folks that respond to those support inquiries can look up more detailed logs. That sort of error looks like service flakiness to me, to be honest, so I would suggest retrying or trying a different region.

Was a glitch w/ that region. Moved to westus and it worked.


Support node taints with data downloader

If the data downloader is set up to download data to hostPath, and the data isn't ready yet, support tainting the node so that services dependent on the data aren't scheduled on the node.

Wondering if this is just overkill and the services that need certain files to exist should just crashloop until they are there.


jsyaml.addConstructor fails (at least in browserified versions)

I’m trying to add a constructor for custom tags using
jsyaml.addConstructor(
  '!sometag',
  function(node) { return "test"} );

This fails with "(Loader || _loader.Loader).addConstructor is not a function". I checked _loader.Loader using Firebug, and it indeed does not have that function. If it’s not a bug, do you have any hints on what I am doing wrong?

Thanks for reporting. I forgot to check exported function. Will fix it soon.

Usage of custom constructors added on online demo as well.


better error message when xcode requires license agreement

vim +PluginInstall +qall will fail if Xcode has been updated and requires a license agreement:
Agreeing to the Xcode/iOS license requires admin privileges, please re-run as root via sudo.
The failure happens when running git commands.

Hi @gnawhleinad, to me this looks like an actual issue, but I am not able to confirm this as I'm not using Xcode. Could you please have a look at the guidelines for posting an issue, and try to provide a bit more information with your issue?
Do you have any suggestions to how this can be fixed?
Thank you.

try to provide a bit more information with your issue?

When Xcode has been updated, it may prompt users to accept their license before using Xcode tools (e.g. git).

Do you have any suggestions to how this can be fixed?

On OS X, Vundle could test the git command for the Agreeing to the Xcode... message and exit code. A user can manually run Xcode and agree to the license or run sudo xcodebuild -license accept. Homebrew uses this approach, Homebrew/install@c0c0534a0432a4001209201128aa84079575167d.


fix(hooks): check if should finalize before calling hook

When a GC finalizer is on the parent (.e.g, foregroundDeletion), I noticed the finalizer hook was getting called immediately during delete instead of waiting for the GC finalizer to be removed. This should wait for the GC finalizer to be removed before calling the finalizer hook.
I have made an assumption on the expected behavior here. If this is wrong, feel free to close the PR.

@mjsmith1028 AFAIU the method ShouldFinalize  answer the question if we should finalize children, not the parent object. Is there any particular reason/use case which makes you think this conditions is needed ?

@mjsmith1028 AFAIU the method ShouldFinalize answer the question if we should finalize children, not the parent object. Is there any particular reason/use case which makes you think this conditions is needed ?

When a GC finalizer is on the parent (.e.g, foregroundDeletion), I noticed the finalizer hook was getting called immediately during delete instead of waiting for the GC finalizer to be removed. This should wait for the GC finalizer to be removed before calling the finalizer hook.
I have made an assumption on the expected behavior here. If this is wrong, feel free to close the PR.

Oh, just found this.
I do not think there is any ordering around finalizing in kubernetes API

@mjsmith1028 AFAIU the method ShouldFinalize answer the question if we should finalize children, not the parent object. Is there any particular reason/use case which makes you think this conditions is needed ?

When a GC finalizer is on the parent (.e.g, foregroundDeletion), I noticed the finalizer hook was getting called immediately during delete instead of waiting for the GC finalizer to be removed. This should wait for the GC finalizer to be removed before calling the finalizer hook.
I have made an assumption on the expected behavior here. If this is wrong, feel free to close the PR.

Oh, just found this.
I do not think there is any ordering around finalizing in kubernetes API

I saw this in the code: https://github.com/metacontroller/metacontroller/blob/5bfcb905f1d100eb71f5ac32c8081879aa5fbbed/pkg/controller/common/finalizer/finalizer.go#L64 which made me think it is not necessary to call the finalize hook until the GC finalizers were removed.
Thinking about this a bit though, maybe this approach doesn't make sense to have metacontroller control the behavior. Instead in the controller finalizer hook logic itself I could check if the foregroundDeletion finalizer is present and handle the delete logic appropriately.
I ended up pivoting and not relying on foreground delete anyway so my specific case no longer applies. I'm fine closing this one out.

I will close this one for now, in case you found some bogus behavior related to finalizing please let me know.


Preview is not working for me

Screenshot attached.

I'm sorry about that, and thanks for giving me the screenshot, unfortunately i cannot see the error, but judging by the line number and the "B" at the start of the error it looks like it cannot find the bat command in your PATH.
Can you check if you have bat installed and available with your PATH?

Yeah right, I did not install this one.
Thanks,
Luca

Can I suggest to give a better explanation on the preview, or even fallback to normal cat?

Yes, my initial tought was to "force" people to install bat, because it is very hard to understand what you're looking for when it's all white, especially because the center line is not highlighted, but now i think i'll follow your suggestion falling back to cat. Thanks!


Create ContextMenu.cs

Before this one can be used, we need a check to prevent disabled entries from being selected

Oh, good point. I completely forgot those can be disabled


Add github workflow file for CI

I think this needs to be committed to run the action, going to try it out.


Refresh session & add admin pages entry point

Codecov Report

Merging #973 into master will increase coverage by 0.01%.
The diff coverage is 0%.

@@             Coverage Diff              @@
##             master     #973      +/-   ##
============================================
+ Coverage     46.91%   46.93%   +0.01%
- Complexity     1554     1555       +1
============================================
  Files           354      354
  Lines          9755     9754       -1
  Branches        968      968
============================================
+ Hits           4577     4578       +1
+ Misses         4835     4833       -2
  Partials        343      343

Impacted Files
Coverage Δ
Complexity Δ

...llo/portal/spi/ctrip/CtripSsoHeartbeatHandler.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...al/spi/defaultimpl/DefaultSsoHeartbeatHandler.java
20% <0%> (+3.33%)
1 <0> (ø)
:arrow_down:

...ervice/service/ReleaseMessageServiceWithCache.java
84.52% <0%> (-1.2%)
23% <0%> (-1%)

...work/apollo/biz/message/DatabaseMessageSender.java
60.41% <0%> (+4.16%)
8% <0%> (+2%)
:arrow_up:

Continue to review full report at Codecov.

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

Coverage increased (+0.02%) to 50.451% when pulling 9c71307c1fa93f711db369022a736e28ccf45f98 on lepdou:refresh_session into 7edfb1aa8c06311202a013fe77e8e1c892638e2a on ctripcorp:master.


hashicorp/kubernetes provider v2.25.0 breaks "cloudposse/eks-cluster/aws" module

Describe the Bug
In mid-december I was using "cloudposse/eks-cluster/aws" module pinned to version 3.0.0 to provision EKS clusters without issue.  Last week I tried to provision a cluster using this module and was unable to do so.  No matter which parameters I adjusted, I was unable to use make it past this error:
╷
│ Error: Value Conversion Error
│
│   with module.eks_cluster.provider["registry.terraform.io/hashicorp/kubernetes"],
│   on .terraform/modules/eks_cluster/auth.tf line 96, in provider "kubernetes":
│   96: provider "kubernetes" {
│
│ An unexpected error was encountered trying to build a value. This is always
│ an error in the provider. Please report the following to the provider
│ developer:
│
│ Received unknown value, however the target type cannot handle unknown
│ values. Use the corresponding `types` package type or a custom type that
│ handles unknown values.
│
│ Path: exec
│ Target Type: []struct { APIVersion basetypes.StringValue
│ "tfsdk:\"api_version\""; Command basetypes.StringValue "tfsdk:\"command\"";
│ Env map[string]basetypes.StringValue "tfsdk:\"env\""; Args
│ []basetypes.StringValue "tfsdk:\"args\"" }
│ Suggested Type: basetypes.ListValue

With the "cloudposse/eks-cluster/aws" module download locally, I was able to manually pin the hashicorp/kubernetes provider to version "v2.24.0" and provision a cluster without failure.  Using any version of the kubernetes provider >v2.24.0 cause the failure to appear.
Expected Behavior
Using the "cloudposse/eks-cluster/aws" I would expect to be able to provision an EKS cluster without the need to locally modify the versions.tf file provided by the module.
Steps to Reproduce
Trying to create an eks-cluster with the example provided in the repo should fail without manually editing the versions.tf file to point the hashicorp/kubernetes provider to version: v2.24.0
Screenshots
No response
Environment
No response
Additional Context
No response

This is a bug in the Hashicorp/Kubernetes provider, not this module. I do not know why the creator of https://github.com/hashicorp/terraform-provider-kubernetes/issues/2388 closed that bug, because pinning to an old version is not a solution to the bug. I encourage you to open a new bug with the provider project.
We are working on entirely removing the Kubernetes provider from this module, and should have that available in the next few weeks. Because of that, we are not expecting to take any other action to resolve this issue.

@jessicuzwhynot Please try v4.0.0-rc1 (#206) and let us know what you think.
Note: at present, v4.0.0-rc1 is not available via the Terraform registry. Use a git ref instead:
source = "github.com/cloudposse/terraform-aws-eks-cluster?ref=v4.0.0-rc1"


tests always pass bug

Description
test('View 200', (t) => {
  server.inject({
    method: 'GET',
    url: '/login'
  }, (response) => {
    console.log(response.statusCode); // 200
    t.deepEqual(response.statusCode, 789); // not equal
  });
});

ava -v

  ✔ login › View 200
  ✔ index › Redirect 302
  ✔ login › Success 200
  ✔ doc › Redirect 302
200
> |

Environment
v0.14.0
Node.js v5.10.1
darwin 15.4.0
hapi 13.2.1

ERROR
test('View 200', async(t) => {
  const response = await server.inject({
    method: 'GET',
    url: '/login'
  });
  console.log(response.statusCode); // 200
  t.deepEqual(response.statusCode, 789); // not equal, fail
});

ava -v

  ✔ index › Redirect 302
  ✔ doc › Redirect 302
200
(node) Server.connections property is deprecated. Use Server.getConnections method instead.

SUCCESS
test('View 200', async(t) => {
  const response = await server.inject({
    method: 'GET',
    url: '/login'
  });
  console.log(response.statusCode); // 200
  t.deepEqual(response.statusCode, 200); // equal, success
});

ava -v

  ✔ index › Redirect 302
  ✔ doc › Redirect 302
200
  ✔ login › View 200

  3 tests passed
> |

@willin
Not sure I understand the problem, but here's my thoughts on your three examples:
Your first example will hang forever. It needs to use t.cb:
test.cb('View 200', (t) => {
  server.inject({
    method: 'GET',
    url: '/login'
  }, (response) => {
    console.log(response.statusCode); // 200
    t.deepEqual(response.statusCode, 789); // not equal
    t.end(); // you need to call t.end() when using `test.cb`
  });
});

Your second example should fail since 200 !== 789.
Your third example looks like it should pass, which it apparently does.
Can you provide a more detailed description of what's going wrong?

Your first example will hang forever.

@jamestalmage It won't. Sync tests end in the same tick. But yeah, needs to use test.cb(). Any way we could catch this mistake in eslint-plugin-ava? I think we'll see more of this as people move from tap/tape.

test('View 200', (t) => {
  server.inject({
    method: 'GET',
    url: '/login'
  }, (response) => {
    console.log(response.statusCode); // 200
    t.deepEqual(response.statusCode, 789); // not equal
  });
});

ava -v

  ✔ login › View 200
  ✔ index › Redirect 302
  ✔ login › Success 200
  ✔ doc › Redirect 302
200
> |

should fail
and tried:
test.cb('View 200', (t) => {
  server.inject({
    method: 'GET',
    url: '/login'
  }, (response) => {
    console.log(response.statusCode); // 200
    t.deepEqual(response.statusCode, 789); // not equal
    t.end(); // you need to call t.end() when using `test.cb`
  });
});

ava -v

  ✔ index › Redirect 302
  ✔ doc › Redirect 302
  ✔ login › View 200
200
(node) Server.connections property is deprecated. Use Server.getConnections method instead.

should fail

No it shouldn't. In that case you're incorrectly using an async callback in a sync test. The test ends before the callback is executed.

and tried:

What's the problem here?

What's the problem here?

I think it's that:
    console.log(response.statusCode); // 200
    t.deepEqual(response.statusCode, 789); // not equal

Produces output:
  ✔ login › View 200
200

Which makes no sense. The log statement prints after the tests passes (and the test passes).
I've tried to reproduce, thinking there's maybe some problem with deepEqual when used to compare literals (there does not appear to be).
@willin - Something doesn't seem right. Can you post some code to a GitHub repo that we can use to reproduce?

server.inject doc: http://hapijs.com/api#serverinjectoptions-callback
sample server: http://hapijs.com/tutorials

@willin.
Please post some of your own code on GH in a repo we can clone that shows the problem.

Closing as OP is non-responsive.
@willin - If you are able to elaborate on the problem more, and provide a minimal reproduction, please open a new issue.

Although this issue has been closed. I found something interested. The following code outputs the node warning (Server.connections property is deprecated. Use Server.getConnections method instead.) and process hangs
test.cb('hello', (t)=> {
	server.inject('/hello', (res) => {
		t.is(res.statusCode, 300);
		t.end();
	});
});

But the following code results in expected result (test fails and process doesn't hang):
test.cb('hello', (t)=> {
	server.inject('/hello', (res) => {
		const code=res.statusCode
		t.is(code, 300);
		t.end();
	});
});

@midnightcodr I'd guess in the former example power-assert is getting stuck serializing res. If this is still an issue with the latest version would you mind opening a new issue?


Python Redis Memory Connector should be able to take existing redis connection, not just connection string

Python redis memory connector should be able to take an existing redis connection. For example, some enterprises require/have other methodologies to connect to redis beyond the default connection string and those connections require additional parameters that cannot work with the default connection string.
Since connecting via the connection string also returns a redis.Redis object and sets it to the memory connector's database attribute, passing in an existing redis connector to set to that attribute should also work.
Have already discussed this briefly with a member of the team.
I will provide the implementation/fix that worked in my enterprise in PR.

Please let me know if/when/what next steps are before I can raise a PR. Thanks!

As of SK Python 1.5.0 the redis_store supports creating the object with an existing Redis database.


added my name to guestbook.md

Added my name to the guest book

adding my name to the guest book.

Thank you!


"color" dependancy

go get github.com/celrenheit/lion
# github.com/celrenheit/lion
../../celrenheit/lion/middlewares.go:20: undefined: color.FgHiMagenta
../../celrenheit/lion/middlewares.go:24: undefined: color.FgHiBlue
../../celrenheit/lion/middlewares.go:25: undefined: color.FgHiGreen

might want to vendor, or add to the docs

Which go version / OS are you using ?
I tried to reproduce the error with go get github.com/celrenheit/lion but it seems to work fine.
Yes, I am going to vendor them to avoid these kind of issues or any version incompatibility problems.

go version go1.6 darwin/amd64

Thank you for the feedback.
Does the last commit solves your issue ?

It creates a different issue when vendoring golang.org/x/net/context and used outside of this library:
cannot convert func literal (type func("golang.org/x/net/context".Context, http.ResponseWriter, *http.Request)) to type lion.HandlerFunc

So I am going to remove golang.org/x/net/context from the vendor folder (more info here) and document it in the README.md


Build Module Error - Solution

Here are the Steps I took:
1- Downloaded the master repo
2- Downloaded the SDK from https://creativesdk.adobe.com/downloads.html
3- Copy/Pasted the AdobeCreativeSDKFoundation.framework & AdobeCreativeSDKImage.framework into the MasterRepo/iPhone:

4- Copy/Pasted the AdobeCreativeSDKFoundationResources.bundle and AdobeCreativeSDKImageResources.bundle into .../myTitaniumWorkSpace/TiAdobeCreativeSDK/iphone
5- Updated module.config: (on line 28) to: OTHER_LDFLAGS=$(inherited) -F".../myTitaniumWorkSpace/TiAdobeCreativeSDK/iphone" -framework AdobeCreativeSDKFoundation -framework AdobeCreativeSDKImage -ObjC
6- Opened Terminal:
$> cd MasterRepo/iphone
$> python ./build.py
Result:
[WARN] please update the manifest key: 'license' to a non-default value
[WARN] please update the LICENSE file with your license text before distributing
Traceback (most recent call last):
File "./build.py", line 263, in
build_module(manifest,config)
File "./build.py", line 174, in build_module
from tools import ensure_dev_path
ImportError: No module named tools
7- Updated manifest line 10 from license: Specify your license to  license: MIT (just to change the value) & LICENSE file with Some Distribution License
8- Ran build.py again...
Result:
Traceback (most recent call last):
File "./build.py", line 263, in
build_module(manifest,config)
File "./build.py", line 174, in build_module
from tools import ensure_dev_path
9 - Obviously it couldn't find the Ti SDK, so reopening the titanium.xcconfig, and noticed a ~ was missing, so on line 13 I simply added the ~:
TITANIUM_SDK = ~/Library/Application Support/Titanium/mobilesdk/osx/3.5.0.GA
and now it built properly :+1:

:+1:
Thanks for explaining it a bit better than I did ;)
Yes, everyone seems to have a slightly different installation setup of their Ti.SDK.
Also the limitations on filesizes on Github meant that couldn't push the frameworks up too.


Bug: [Validation] required_without will not work if the field is specified with asterisk

See https://github.com/codeigniter4/CodeIgniter4/issues/5922#issuecomment-1113904559
The following test fails. The validation passes.
    public function testRequireWithoutWithWildCard()
    {
        $data = [
            'a' => [
                ['b' => 1, 'c' => 2],
                ['c' => ''],
            ],
        ];

        $this->validation->setRules([
            'a.*.c' => 'required_without[a.*.b]',
        ])->run($data);

        $this->assertSame(
            'The a.*.c field is required when a.*.b is not present.',
            $this->validation->getError('a.1.c')
        );
    }

I think the description of required_without is strange.

The field is required when all of the other fields are present in the data but not required.

Is the description different from the value of getError means ?

@kenjis What kind of design should I use?

Is the description different from the value of getError means ?

Yes. The explanation is the same as the following comment, but it seems different from the Example blow:
https://github.com/codeigniter4/CodeIgniter4/blob/ac2ad223531210bf4624a113469cb099c35e09fe/system/Validation/Rules.php#L274-L279

The field is required when all of the other fields are present in the data but not required.

I think this explanation and description of official document of required_without[] isn't right , the right explanation should be as below.

The field is required when any of the other required fields are not present in any data.

https://github.com/codeigniter4/CodeIgniter4/blob/ac2ad223531210bf4624a113469cb099c35e09fe/system/Validation/Rules.php#L302-L304

empty(dot_array_search($field, $data))

As the conditional shows, it judge whether the param field of required_without[] isn't presented in data.
For example:
public function testRequireWithoutWithWildCard()
    {
        $data = [
            'a' => [
                ['b' => 1, 'c' => 2],
                ['c' => ''],
            ],
        ];

        $this->validation->setRules([
            'a.*.c' => 'required_without[a.*.b]',
        ])->run($data);

        $this->assertSame(
            'The a.*.c field is required when a.*.b is not present.',
            $this->validation->getError('a.1.c')
        );
    }

In this test case, a.*.c field will be required when all of a.*.b field don't present in data.
If any data is presented in a.*.b field, a.*.c will not be required, so the dataset of this test case should be chaged as below.
$data = [
    'a' => [
        ['b' => '', 'c' => 2],
        ['c' => ''],
    ],
];

@ping-yee Do you mean this is not a bug?
I thought that a.1.c field will be required when a.1.b field doesn't present in data.
It seems we need a realistic use case.

Do you mean this is not a bug?

Yes, I think this is not a bug, it just need to change the command out and the description of official document.

I thought that a.1.c field will be required when a.1.b field doesn't present in data.

Yes, It should be that.
So the data set of this case should be as below.
    public function testRequireWithoutWithWildCard()
    {
        $data = [
            'a' => [
                ['b' => '', 'c' => 2],
                ['c' => ''],
            ],
        ];

        $this->validation->setRules([
            'a.*.c' => 'required_without[a.*.b]',
        ])->run($data);

        $this->assertSame(
            'The a.*.c field is required when a.*.b is not present.',
            $this->validation->getError('a.1.c')
        );
    }

When a.0.b field doesn't present in data, the a.0.c and a.1.c field will be required.
But a.1.c field doesn't have any data, it will get the error The a.*.c field is required when a.*.b is not present..

When a.0.b field doesn't present in data, the a.0.c and a.1.c field will be required.

I thought the checking should be done for each array (a.0, a.1).
When a.0.b field does not pass required check, the a.0.c field will be required.
When a.1.b field does not pass required check, the a.1.c field will be required.

I read through this whole thread and thought to myself: "has our validation system gotten too abstruse?"
I can't think of an example where I would use this, but also it seems so difficult to understand I think if I did have such a case I would break it into smaller validations.

To be frank, I am not sure of the correct specifications.
I would like to hold off until a use case can be found.

Sorry, I think What I express is too abstruse 😢
To put it in another way, let start at required_with[] function.
I think this function is more easy to understand.
    public function index()
    {
        $data = [
            'a' => [
                ['b' => 2, 'c' => 2],
                ['b' => 3, 'c' => 3],
            ],
        ];

        // there isn't any error occur.
        $this->validation->setRules([
            'a.*.c' => 'required_with[a.*.b]',
        ])->run($data);
    }

It means when all of a.*.b fields (like a.0.b, a.1.b, ......) present in data, the all of a.*.c fields (like a.0.c, a.1.c, ......) become required.
In this case, if any of a.*.c fields don't present in data, it will get the error "The a.*.c field is required when a.*.b is present." by using getError() function.
I think this is useful for checking the dependency between one field and the other field(s).

Sorry, I think What I express is too abstruse 😢, I think I figure out and find a bug last night.
And I want to check the process logic and design with you all.

In asterisk fields case.

    public function index()
    {
        $data = [
            'a' => [
                ['b' => 1, 'c' => ''],
                ['b' => '', 'c' => 2],
                ['c' => ''],
            ],
        ];

        $this->validation->setRules([
            'a.*.c' => 'required_without[a.*.b]',
        ])->run($data);

        dd($this->validation->getError('a.2.c'));
    }

To begin with, we can see these code in last run() function as below :
https://github.com/codeigniter4/CodeIgniter4/blob/ac2ad223531210bf4624a113469cb099c35e09fe/system/Validation/Validation.php#L168-L176
In this case, it input the one by one a.*.c field (a.0.c, a.1.c, etc...) by using foreach into the processRules() function to judge this field whether following the rule of setRule() or not.

Now a.0.c field in first round

In processRules() function, it load the correspondence rule instances and put $value, $param, $data, $error these data into correspondence rule function (like required_with(), required_without(), etc...) as below :
https://github.com/codeigniter4/CodeIgniter4/blob/ac2ad223531210bf4624a113469cb099c35e09fe/system/Validation/Validation.php#L313-L315

There is value of each required_without() params :
$value   => "" (This is key of setRule() field data, in this case is  a.0.c field data so that is "")
$param => "a.*.b" (This is the param field of required_without[] in this case, so it's a.*.b)
$data    => $data array (This is the data set of present in).
$error   => This isn't used in this case.

Here we are required_without() function, it call the required() function to judge the $str (I don't think this is a good name, $str correspond $value as shown above) whether the field value isn't empty string or not In line 293.
If it isn't empty string, means there is data in key of setRule() field this time then return true and finish the judgement of this field (because key of setRule() field have data, it will never error occur in this rule) in line 296.
If it is empty string, then we keep go on. 😓
https://github.com/codeigniter4/CodeIgniter4/blob/ac2ad223531210bf4624a113469cb099c35e09fe/system/Validation/Rules.php#L283-L308
https://github.com/codeigniter4/CodeIgniter4/blob/ac2ad223531210bf4624a113469cb099c35e09fe/system/Validation/Rules.php#L214-L229
In line 301 - 308, it have some condition to judge whether the param field(s) of required_without[] have data or not.
The param field is a.*.b in this case, the condition is strpos($field, '.') !== false && empty(dot_array_search($field, $data)).

The function of dot_array_search($field, $data) is search all data of incoming field, in this case it return array of all of a.*.b data.
But if there is only one field in data set, it will only return the string type without array. (This is a bug but I have fixed in PR because empty() function can't judge whether all of array value is empty or not, it will be always be false even all of array value is empty).

array(2) {
  [0]=>
  string(0) ""
  [1]=>
  string(0) ""
}

The condition judge whether the array return by dot_array_search($field, $data) function is empty or not.
if it return false, then this round key of setRule() field will store in the $this->errors[$field] (like this round field a.0.c) as below.
https://github.com/codeigniter4/CodeIgniter4/blob/ac2ad223531210bf4624a113469cb099c35e09fe/system/Validation/Validation.php#L340-L347
And $this->validation->getError('a.1.c') is get error by field in $error array.
This is all of process logic and there is a design problem as next comment.
Thanks for reading.

I find a bug is empty(dot_array_search($field, $data)) only can judge whether the field value is empty or not in one field.
If there are more than two fields in data set, dot_array_search($field, $data) will return all of this $field values in array type, then  empty() function can't judge whether all of values of this return array are empty or not (it will always return false) as shown above.
So I fixed this issue in PR, Add these to judge if dot_array_search() return data in array type.
if (strpos($field, '.') !== false && is_array(dot_array_search($field, $data))) {
    foreach (dot_array_search($field, $data) as $value) {
        if (empty($value)) {
            return false;
        }
    }
}

And this change can all pass in ValidationTest.php and RulesTest.php files unit test.
But this design is when any of required_without[] param field is empty, the key of setRule() field is required (I think this is what the author design).
    public function index()
    {
        $data = [
            'a' => [
                ['b' => 1, 'c' => ''],
                ['b' => '', 'c' => 2],
                ['c' => ''],
            ],
        ];

        $this->validation->setRules([
            'a.*.c' => 'required_without[a.*.b]',
        ])->run($data);

        // This will error occur.
        dd($this->validation->getError('a.0.c'));

        // This will not error occur.
        dd($this->validation->getError('a.1.c'));

        // This will not error occur.
        dd($this->validation->getError('a.2.c'));
    }

In this case, becase a.1.b field doesn't present in data, make all of a.*.c field become required.
And this is why a.0.c and a.2.c fields will get error message, becasue these two fields don't present in data.
After figure out what the author of this class design, I think this is reasonable for this design becasue it conform the word required_without[] means like:

required_without[] param field is main required, if any required_without[] param field don't present in data then the key of setRule() field need to support the main required to become second required.

I think this is make sense.

@kenjis Are these thing and use case reasonable? or anything I miss.

Sorry, I don't get what you say. It is too complicated.
Can you show a realistic use case? Not a or b, but something meaningful.

In this case, becase a.1.b field doesn't present in data, make all of a.*.c field become required.

It seems a.1.b field is present and its value is an empty string.

In your PR:
a.0.c: error
a.1.c: no error
a.2.c: error
But your explanation above is: error, no error, no error.

In my opinion,
When a.0.b field does not pass required check, the a.0.c field will be required.
When a.1.b field does not pass required check, the a.1.c field will be required.
When a.2.b field does not pass required check, the a.2.c field will be required.
So the results should be: pass, pass, error.
But I don't know my opinion is correct or not.

It seems a.1.b field is present and its value is an empty string.

https://github.com/codeigniter4/CodeIgniter4/blob/ac2ad223531210bf4624a113469cb099c35e09fe/system/Validation/Rules.php#L214-L229
at last judge, it seems the empty string also means don't present the data.''

But your explanation above is: error, pass, pass.

Sorry for the mistake comment out, I have been modified.

It doesn't run with a pair of field like a.0.b => a.0.c, a.1.b => a.1.c.
It run with judge all of a.*.b is required or not, then decide all of a.*.c is required or not.
If any of a.*.b doesn't present the data in, then all of a.*.c field need to present in data (I think this is how the field with asterisk run like).
    public function index()
    {
        $data = [
            'a' => [
                ['b' => 1, 'c' => ''],
                ['b' => '', 'c' => 2],
                ['c' => ''],
            ],
        ];

        $this->validation->setRules([
            'a.*.c' => 'required_without[a.*.b]',
        ])->run($data);

        // This will error occur.
        dd($this->validation->getError('a.0.c'));

        // This will not error occur.
        dd($this->validation->getError('a.1.c'));

        // This will error occur.
        dd($this->validation->getError('a.2.c'));
    }

So this is why a.0.c and a.2.c get fail.

Thank you for your explanation!
Okay, I got your logic. And it seems to be implemented well in your PR.
But I don't know it is correct as the specification.
After all, it seems to depend on use cases.
In the case 3 in #5922, my opinion seems appropriate.

I got this logic after reading the Validation class as above show, and I think this is what the original developer design.

In use case of #5922

'beneficiaries_accounts.*.purpose' => [
      'label' => 'PURPOSE',
      'rules' => 'required_without[beneficiaries_accounts.*.account_number]|min_length[3]|max_length[255]',
],

$data = [
    'customer_account_number' => 'A_490',
    'debit_amount'            => '1500',
    'beneficiaries_accounts'  => [
        'account_1' => [
            'account_number' => 'A_103',
            'credit_amount'  => 1000,
            'purpose'        => 'Personal',
        ],
        'account_2' => [
            'account_number' => 'A_258',
            'credit_amount'  => null,
            'purpose'        => 'A',
        ],
    ],
];

In case 3, I don't understand why the required_without[] specification should occur the error because all of beneficiaries_accounts.*.account_number fields already present in the data (like beneficiaries_accounts.account_1.account_number, beneficiaries_accounts.account_2.account_number).
If need the error case, any of beneficiaries_accounts.*.account_number fields need to don't present data, like:
$data = [
    'customer_account_number' => 'A_490',
    'debit_amount'            => '1500',
    'beneficiaries_accounts'  => [
        'account_1' => [
            'account_number' => 'A_103',
            'credit_amount'  => 1000,
            'purpose'        => 'Personal',
        ],
        'account_2' => [
            'account_number' => 'A_258',
            'credit_amount'  => null,
            'purpose'        => 'A',
        ],
        'account_3' => [
            'account_number' => '',
            'credit_amount'  => null,
            'purpose'        => '',
        ],
        'account_4' => [
            'account_number' => 'A_369',
            'credit_amount'  => null,
            'purpose'        => '',
        ],
    ],
];

Both of beneficiaries_accounts.account_3.purpose and beneficiaries_accounts.account_4.purpose will get the error.

In the case 3 in https://github.com/codeigniter4/CodeIgniter4/issues/5922, my opinion seems appropriate.

But I agree with this, this use case is more appropriate using your opinion because it shouldn't have dependency between accounts.

When a.0.b field does not pass required check, the a.0.c field will be required.
When a.1.b field does not pass required check, the a.1.c field will be required.

But I think it need to refactor what required_without specification work to follow the design.

It seems to what required_without rule actually work different from what #5922 expect that validate each array separately.
I think we need:

modify the description of required_without[] rule.
add one more rule to validate each array separately.

Because now on the required_without[] rule work as original designer expect, probably it may also be someone expect and follow this to develop their own project.
@kenjis what do you think?

I think this is what the original developer design.

I don't believe the original developer design. I think the original developer did not consider about fields with * at all.
Because fields with * did not work at all. See #5938.

It seems to what required_without rule actually work different from what https://github.com/codeigniter4/CodeIgniter4/issues/5922 expect that validate each array separately.

Yes, and this issues is the bug report.

@ping-yee I think your PR #6541 is logical, but I can't imagine a real use case.
But the use case of #5922 is a real use case.
If we fix the bug, it is better to support #5922 use case.

Ok, I got it.
I will close my PR then modify the logic to support the #5922 use case.

Closed by #6589


Enhanced Rich Previews for Telegram/Discord/Open Graph

Describe the Feature
I would love to see enhanced rich previews for BlueSky posts in messaging platforms like Telegram and Discord, as well as Open Graph-supported platforms (e.g., Twitter, Facebook). This would make sharing BlueSky posts much more engaging and visually cohesive, similar to the way FixTweet Mosaic handles it.
Key Elements

Rich Previews in Telegram/Discord:

Automatically generate rich previews for shared BlueSky posts that display all included images, not just the first one.
Support for Telegram Instant View for seamless browsing post+gallery within app, creating a fluid experience for users who don’t want to leave the chat platform.

Multi-Image Display:

If a BlueSky post contains multiple images, display all of them in a preview combined. This ensures users get a full visual representation of the post's content without losing context could be available in N+1 image.

Enhanced Open Graph Tags Handling:

Although Open Graph markup is already in place, it would be great if all images in a post could be included in the preview, not just the first one.
Additionally, for posts that require login to view, a preview with a prompt inviting users to open the post as a BlueSky user would be ideal. This would make the experience more consistent and encourage new users to engage directly with BlueSky.

Benefits

Improved engagement by making BlueSky content more accessible and visually appealing on other platforms.
Enhanced user experience by allowing users to preview full content without leaving their current platform.
Greater discoverability and appeal for BlueSky posts in group chats and other social media spaces.

Thank you for considering this enhancement, as it would greatly enrich the experience of sharing BlueSky content across multiple platforms!
Attachments
No response
Describe Alternatives
No response
Additional Context
Currently already implemented via third-party service: https://bsky.app/profile/fxbsky.app with MIT License

+1

happy to review a pull request doing this


no version available for transitive dependencies

Describe the bug
I use Quarkus with quarkus-web-bundler and when I trying to import:
	<dependency>
		<groupId>org.mvnpm</groupId>
		<artifactId>primereact</artifactId>
		<version>10.8.4</version>
		<scope>provided</scope>
	</dependency>

then I get this error:
Could not collect dependencies for project com.acme:hello:jar:1.0.0-SNAPSHOT
[ERROR] No versions available for org.mvnpm:scheduler:jar:[16.6.2,17) within specified range
[ERROR] No versions available for org.mvnpm:scheduler:jar:[16.6.2,17) within specified range

To Reproduce
Steps to reproduce the behavior:

Add the following to pom.xml:

<!-- Add quarkus 3.16.1 -->
..
<dependency>
    <groupId>io.quarkiverse.web-bundler</groupId>
    <artifactId>quarkus-web-bundler</artifactId>
    <version>1.7.3</version>
</dependency>
<dependency>
    <groupId>org.mvnpm</groupId>
    <artifactId>primereact</artifactId>
    <version>10.8.4</version>
    <scope>provided</scope>
</dependency>

Update maven deps
See error

Expected behavior
The lib should be downloaded without error.
Additional context
I used mvnpm for the first time. I don't know if this is really a bug or if I have to take care of downloading the lib scheduler myself but I expect the specified libraries in mvnpm (in this case: primereact) to take care of transitive deps themselves.

Are you using the repository in your settings ?
<settings>
    <profiles>
        <profile>
            <id>mvnpm-repo</id>
            <repositories>
                <repository>
                    <id>central</id>
                    <name>central</name>
                    <url>https://repo.maven.apache.org/maven2</url>
                </repository>
                <repository>
                    <snapshots>
                        <enabled>false</enabled>
                    </snapshots>
                    <id>mvnpm.org</id>
                    <name>mvnpm</name>
                    <url>https://repo.mvnpm.org/maven2</url>
                </repository>
            </repositories>
        </profile>
    </profiles>
</settings>

typically /home/your-username/.m2/settings.xml
You only need to add this on your development laptop, in CI it should then already be synced to maven

Yea that is strange. We need to figure out what dependency is pulling that in transitively. Can you see that in your IDE ?

Ok let me see if I can find it. Hold on

Can you share your pom.xml (or at least a list of all mvnpm deps )

Ok, give me a few mins let me find it

Try to add an exclusion on react-router-dom :
<dependency>
		<groupId>org.mvnpm</groupId>
		<artifactId>react-router-dom</artifactId>
		<version>6.27.0</version>
		<scope>runtime</scope>
                <exclusions>
                    <exclusion>
                        <groupId>org.mvnpm</groupId>
                        <artifactId>scheduler</artifactId>
                    </exclusion>
                </exclusions>
	</dependency>
	```

	You can also then remove the

	```
	<groupId>org.mvnpm</groupId>
	<artifactId>scheduler</artifactId>
	```

	I am still trying to figure out why that version is there. Let me know if this works for you

I still can not see where that version is pulled in. I'll dig some more

I get this error on my laptop with your reproducer, I am reopening and investigating

I fixed some of the issues highlighted by this reproducer. It's' working now for me if you exclude the scheduler:
<dependency>
                        <groupId>org.mvnpm</groupId>
                        <artifactId>react-router-dom</artifactId>
                        <version>5.3.4</version>
                        <scope>provided</scope>
                        <exclusions>
                          <exclusion>
                              <groupId>org.mvnpm</groupId>
                              <artifactId>scheduler</artifactId>
                          </exclusion>
                      </exclusions>
                </dependency>

I'll release a new version a.s.a.p

The problem is that somewhere, a dependency reference a scheduler version that does not exist. I could not find where, excepts that it's somewhere in react-router-dom


A few inconsistencies

Hi,
I've noticed that the pictures here show a dark mode and a transparent navigation bar, which is not available in the app on the latest Version 1.0.1 (which  has actually a 1.0.0 number).
Regardless, everything works great.

I haven't tested it today but for whatever reason, as of today dark mode seems to work now (but there is no switch) and the navigation bar is transparent now too. Yesterday the icon disappeared but today everything seems to have been corrected somehow.


Placeholder cut off if element is hidden initially

I've noticed that if the element is initially hidden (or hidden when the placeholder gets set, e.g. if placeholder interpolation is enabled and the placeholder text gets set "later") then the placeholder text gets cut off. Debugging reveals that the offsetWidth of the  used to calculate the text width is 0 and it looks like that's indeed the case with hidden elements.
My particular scenario is I have the tags input inside a collapsible section which is initially collapsed (it's an advanced search of sorts). The text is "type to find business partners" which gets cut off.
One solution that I can think of is, instead of creating the hidden  used to calculate the 's width once, create the span whenever the resize() function is called and check if the element's visible or not. Then, if the element's NOT visible simply append the  to the document.body, instead of the parent. I implemented this solution and it works (of course, removing any previously created s every time). The only strange thing is that I needed to increase the THRESHOLD to 18, otherwise the very end of the text would get cut off (note, this would happen regardless of text length). I presume it might have something to do with the fact that some CSS selectors which are specific to the span residing inside of ng-tags-input don't apply anymore, but haven't dug through the css yet.
Can you please share your feedback on the issue and other ideas for a fix you might have?
Thanks!

This issue was selected to be spring-cleaned by a script. More information can be found here.
If anyone thinks this was a mistake and this issue should be reopened, please leave a message below explaining why. Before doing so, please consider reading the CONTRIBUTING file.


CUDA autotune table needs updating for CC 7.0 (Volta)

When running autotuned kernels on Volta, the warning is printed:
numba/cuda/compiler.py:234: UserWarning: Could not autotune, using default tpb of 128

This is because the autotune table needs to be updated:
https://github.com/numba/numba/blob/master/numba/cuda/cudadrv/autotune.py#L214-L225

Actually, we should drop this in favor of the routine provided by the driver.

Now, I really need this for pygdf.


Mops dependency

merge this and release a new version of icrc30-mo as soon as the main branch of icrc7.mo has been released under 0.3.1

this is ready for review @panindustrial-dev
maybe squash the commits :D


proper integration of Guard functions with Execution

At the moment the Guard functions use dummy Configurations to create and use a hadoop filesystem instance. Instead, we should expose these functions as Hdfs or Execution actions, so they use the provided configuration and are consistent with the rest of the maestro API.

Note that although the Guard functions are less necessary now that we can get the list of uploaded files from upload or sqoopImport, we still need them if we write a job that deals with files that are already on HDFS.

In the PR review for etl.ebilling-pricinginformation today, Guard.createFlagFile was used via:
Execution.from(createFlagFile(conf.inputs))
There was a PR comment that createFlagFile use the HDFS monad would be better.

Based on the comment by @rowandavies, I will convert to Hdfs unless somebody has a reason to prefer Execution.

Hdfs seems appropriate, and there's an explicit coercion from this to Execution, namely RichExecution.fromHdfs aka hdfs.


Non-dev dependencies?

Is there a reason why mocha-jsdom, sinon, jsdom, etc, is a dependency and not a dev dependency? Yet mocha itself is a dev dependency?
Furthermore, why are there non-dev dependencies to begin with? Enzyme is for running tests in dev. Just seems counter-intuitive to have it setup this way. I also believe this is causing unmet dependencies when running npm install or npm update.

@milesj devDependencies are for developing this module. dependencies are things this module needs to work.

For example, mocha is a dev dep because it's for running enzyme's own tests. mocha-jsdom is used as part of enzyme's actual functionality.
This is all working as intended, and npm install works just fine. If you have a specific unmet dependency issue I'd love to see the output so we can fix it!

I know full well how dependencies work. Why is mocha-jsdom a dependency when it definitely is not required, as I can run tests without mocha? That's the issue.
npm WARN<EMAIL_ADDRESS>requires a peer of mocha@* but none was installed.

But after looking at the source, it was moved to optional. https://github.com/airbnb/enzyme/blob/master/package.json#L82 Yet the one I just downloaded has it under dependencies and I'm using ~1.5. Maybe NPM is out of date? Or we need a minor bump?

v2.0 will be removing all of the test-framework-specific packages, like sinon, jsdom, mocha-jsdom, etc. In its initial release, enzyme was primarily used with mocha, although it certainly works with other testing frameworks. In v2, it will be very clearly usable with other frameworks, and will not include extra dev dependencies.


v1.0.1 Extract only once

Fix bug where extract doesn't remove the node from the queue.

tests pass, code looks good. merging pr


Bump pylutron to 0.2.5

Description:
New version is much more robust against disconnections, fixes a string formatting exception, and adds better logging when uncaught exceptions are thrown.
Related issue (if applicable): fixes #20348
Pull request with documentation for home-assistant.io (if applicable): N/A
Example entry for configuration.yaml (if applicable): N/A
Checklist:

[x ] The code change is tested and works locally.
[x ] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x ] There is no commented out code in this PR.
[x ] I have followed the development checklist

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

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

If the code communicates with devices, web services, or third-party tools:

[ ] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[x ] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[ ] Untested files have been added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

@cdheiser @JonGilmore FYI


Live Preview: All screenshot sizes do not display for Image Slider + Randomizer

After saving a draft of a project, a screenshot tab appears to allow users to view their project at different sizes. Currently all screenshot sizes are not rendering properly. In the two examples below, multiple sizes are not displaying. This does not occur in preview.
Large + Medium do not display
http://staging.autotune.voxmedia.com/projects/curbed-this-test-image/edit
Medium does not display
http://staging.autotune.voxmedia.com/projects/generic-another-test

Navigate to Autotune on staging
Create new Image Slider project
Add image urls and save project
Observe screenshot tab displays (see links above)
Click screenshot tab and browse sizes
Note all screenshot sizes do not render

This also occurs for the Headline Randomizer. All sizes of screenshots are not displaying. In this example, both the Large and Small screens do not display.
http://staging.autotune.voxmedia.com/projects/racked-testing-again


CUDA out of memory

Thanks very much for  the codes!
I tried to train the interactron model with A100, but there was an issue with out of memory, may I ask what caused this problem?
Thanks!

Thanks very much for the codes! I tried to train the interactron model with A100, but there was an issue with out of memory, may I ask what caused this problem? Thanks!

Hello，I have the same issue. Have you resolved this problem？


React step 4

Closes #
{{short description}}
Changelog
New

{{new thing}}

Changed

{{change thing}}

Removed

{{removed thing}}

@jefftmahoney Is this step 3 or step 4?

Closing this - please refer to PR 2011 for the non-messed-up version.


Vulnerability roundup 114: rippled-1.7.3: 1 advisory [9.8]

search, files

[ ] CVE-2022-29077 CVSSv3=9.8 (nixos-21.11, nixos-unstable)

CVE details
CVE-2022-29077
A heap-based buffer overflow exists in rippled before 1.8.5. The vulnerability allows attackers to cause a crash or execute commands remotely on a rippled node, which may lead to XRPL mainnet DoS or compromise. This exposes all digital assets on the XRPL to a security threat.

Scanned versions: nixos-21.11: 3c5ae9be1f1; nixos-unstable: f419dc5763c.
Cc @RaghavSood
Cc @offlinehacker

Marked vulnerable in 1ebd98fe8c115f671826b5684a8ce456b522de72. New upstream versions exist.

Updated to a non vulnerable version in f749f900d48644cae7554d39d14a269db71c7184.


$ref imports generates new types for every yaml file

I've generated API via spring generator for java code by maven plugin and typescript-angular for frontend. I have many of YAML files(to keep the API separated and YAML files short). I am using imports of a model like:
$ref: 'anotheryamlfile.yaml#/components/schemas/Problem'
I tried also
$ref: './anotheryamlfile.yaml#/components/schemas/Problem'
Unfortunately, the ProblemVO class is generated separately for every YAML file(so different types are generated and they cannot be used as one type):

Setting withSeparateModelsAndApi to false doesn't help.
For the maven plugin, I have an execution goal per YAML file. Same for openapi-generator generate by the console.

Hi,
can you write a minimal example with yaml-files and full openapi gradle plugin config. Then we can reproduce the problem.


Eight bit input mode (like Xterm)

Description of the new feature/enhancement
An "eight bit input mode," like XTerm has.

From what I can tell, windows terminal sends alt keys through using escape sequences, but that's not what programs like vim in WSL expect. They expect the 8th bit to be set, like in xterm. This makes using mappings in vim that contain alt not work correctly.
I've been looking at PRs like #6309 because they seem related, but I can't quite tell if this feature already exists, as some of the jargon goes over my head.

So, this is the first credible request we've had for eight-bit input mode since we started shipping expanded VT input mode years back. Would you mind sharing an example of some things that don't work in vim when Alt is sent as Meta?
I think that supporting 8-bit input mode long-term is going to completely damage our ability to support the input of any characters whose codepoints are greater than 0x7f. The world has come a very long way since there were only 127 characters, and reserving an entire additional plane for alted input is going to be a hard sell.

Hmm, I spent some more time looking into it and it seems like vim is the outlier here. With the current behavior, it is not possible to map Alt+(anything) to anything in vim. You have to use workarounds like mapping (anything) instead, which can be annoying because it adds a delay after using the escape key, so the delay length has to be modified, which could cause further errors (though I'm not sure). If it means you'd have to sabotage future character input, though, I guess it's probably not worth it to implement.

Alright, I did a quick investigation of a few of our competitors.
It looks like gnome-terminal (vte) and konsole don't offer 8-bit meta mode any longer.
Given that it'll be really difficult to support and keep our core tenet of supporting more than just ASCII, and that the number of applications that are going to require it will trend towards zero with the inexorable march of time, I'm going to close this one out as, regrettably, Won't Fix
It also seems like it might be impossible for us to support. Windows applications generally receive UTF-16 or "native codepage" encoded input. Many of them, however, immediately convert that input to UTF-8. We can't encode an unjacketed character >= 0x80 (high bit set) in UTF-8 and expect it to come across as a high bit set in a 7-bit ASCII glyph through all of the cross-process communication channels that Windows requires.
Since WSL is just a Windows application, at the end of the day, it has to follow suit. We already have an issue where we can't send mouse coordinates using the legacy system >= 93 because they would require a high bit!

I know this issue is closed but I just wanted to mention that I too would really like to be able to use alt key for binds in Vim while using the Microsoft Terminal.
Everything @ggadget6 mentioned is how I feel too. The workaround makes the Vim experience much worse. In practice it's a case where binding alt keys in Vim isn't possible with the MS terminal in its current state.
Is there any type of workaround to address this without limiting future use? Switching to another terminal is a bit drastic but not being able to bind alt is a big loss. it's a really useful key for performing actions in multiple Vim modes. There's no reasonable substitute in a lot of cases.

I know this issue is closed but I just wanted to mention that I too would really like to be able to use alt key for binds in Vim while using the Microsoft Terminal.
Everything @ggadget6 mentioned is how I feel too. The workaround makes the Vim experience much worse. In practice it's a case where binding alt keys in Vim isn't possible with the MS terminal in its current state.
Is there any type of workaround to address this without limiting future use? Switching to another terminal is a bit drastic but not being able to bind alt is a big loss. it's a really useful key for performing actions in multiple Vim modes. There's no reasonable substitute in a lot of cases.

@ggadget6 Are you maybe trying to map using A- instead of M-?

8-bit mode is useful in *nix terminals because keys are sent via text / ESC sequences, 8-bit parser is able to differentiate  keypress from <ALT+key> combo, which is not possible for 7-bit parser.
windows conhost api is completely different story because the ReadConsoleInput supplies keycodes, it doesnt really need 8-bit mode to improve keyboard support


Use dep in jenkins

hi,
I use the following code to install dep in jenkins
withEnv(["GOPATH=${JENKINS_HOME}/jobs/${JOB_NAME}/builds/${BUILD_ID}"]) {
     checkout scm
     sh "go version"
     sh 'wget https://raw.githubusercontent.com/golang/dep/master/install.sh'
     sh 'sh ./install.sh'

I see in the log that it copy the bin but when it comes to command dep ensure we got error, how to overcome this ?
13:33:41 Fetching https://github.com/golang/dep/releases/latest..
13:33:42 Release Tag = v0.5.0
13:33:42 Fetching https://github.com/golang/dep/releases/tag/v0.5.0..
13:33:42 Fetching https://github.com/golang/dep/releases/download/v0.5.0/dep-linux-amd64..
13:33:51 Setting executable permissions.
13:33:51 Moving executable to /var/jenkins_home/jobs/go-voter/test/builds/22/bin/dep
[Pipeline] sh
13:33:53 + dep ensure
13:33:53<EMAIL_ADDRESS>1: /home/jenkins/workspace/go-voter_test@tmp/durable-
16613f28/script.sh: dep: not found

As written in the log I see that the tool were installed in the bin 22/bin/dep is it related somehow to the path ? if so how should I configure it in jenkins ?

I'm not sure. You should probably consult a Jenkins user guide for help setting the PATH, I think. :(

Going to close this, if you have more information or a suggestion we can take action on please let us know!


Enhance CHM interpolation logic and update tests.

The interpolation parameter now supports a 'None' option, ensuring no interpolation is performed if desired. Adjusted the tests accordingly to accommodate the changes in CHM calculation, including verification for voxel processing and grid orientation. Additionally, revised test cases to handle larger datasets and improved CHM height checks.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files with missing lines
Coverage Δ

pyforestscan/calculate.py
100.00% <100.00%> (ø)

tests/test_calculate.py
100.00% <100.00%> (ø)


Simple question from a newbie re derived attributes in montreal_2014.html

Hi, I'm just getting up to speed on pivottable.js and like it a lot. I'm stuck on a relatively simple task in derived attributes. In the montreal_2014.html code, all I am trying to do is create a new variable called "Precipitation" that is the sum of Total Rain (mm) and Total Snow (cm). Once the new variable Precipitation is created in the derived attributes, I plan to also add it to the aggregators list as well. Adding two existing variables seems simple, but I have yet to get it to work and haven't found any code in the examples to help. Sorry for the newbie question. Thanks<EMAIL_ADDRESS>

What you want to do is created a "derived attribute" like "Gender Imbalance" in this example: http://nicolas.kruchten.com/pivottable/examples/mps.html

Basically something like:
"derivedAttributes": {
    "Precipitation": function(row){return row["Total Rain (mm)"] + row["Total Snow (cm)"];}
}


Add support for DNS Made Easy

Can you please look into supporting DNS Made Easy DNS?
http://www.dnsmadeeasy.com/integration/restapi/

Will need to look into it. The sandbox thing might be adequate for building it, or maybe a 30 day trial.
It “should” be relatively easy if the API is decent.

Totally do-able. I already started work on it. They have a pretty weird authentication scheme, but figured that out.
I think initially will probably just be records, then after Geo can be added later to the provider.

I would love to see that as well. I'm in the process of migrating from DME just because they don't have OctoDNS provider.

I have the "provider" relatively complete. DME has some quirks to deal with (Relative values, Cannot make NS record without there being an A record first, etc.) that I'm trying to deal with.
Then the rest would just be adding tests.
Couple questions:
Do you use ANAME records?
Do you use relative values?

We don't have any ANAME records.
By relative values, do you mean domain records that points to the same domain without specifying the domain part? We try not to have these. In my opinion, you can ignore this case.

Great. I'm probably not going to add in ANAME records because I think they are only specific to DNSMadeEasy.
As for relative, yes you're right on with your description. I'm handling it with dumping relative values, then making them absolute, so they will be absolute in the YAML. If you re-apply the YAML it will delete/create the record again with the absolute value.
That delete/create behavior could be dicey, as there is a period where the record wouldn't exist.

@ross Would like to bounce a couple questions/thoughts off you

DNSMadeEasy allows you to specify relative values, it returns them from the API as relative. Currently, I'm handling it with dumping relative values via the DnsMadeEasyClient, then making them absolute before returning them from the caller, so they will be absolute in the YAML. If you re-apply the YAML it will delete the relative record from the provider and create the record again with the absolute value.

This delete/create behavior could be dicey, as there is a period where the record wouldn't exist. Wondering if you would consider that acceptable and if a note just saying the behavior of the provider, so users are aware.

DNSMadeEasy will not allow you to create a NS record with a relative value if there is no A record already created for it. It will however allow you to create a NS record with an absolute value of a record in the same zone regardless if the A record exists. The latter is the behavior I have written in the client to force absolute values.

At the same time, you cannot delete an A record if an NS record is pointing at it by relative value (this might happen if it was created before using OctoDNS, etc). If OctoDNS ran and needed to change the value, then it would error, as it couldn't change it without deleting it first.

DNSMadeEasy allows you to specify relative values, it returns them from the API as relative. Currently, I'm handling it with dumping relative values via the DnsMadeEasyClient, then making them absolute before returning them to the caller, so they will be absolute in the YAML. If you re-apply the YAML it will delete the relative record from the provider and create the record again with the absolute value.

This delete/create behavior could be dicey, as there is a period where the record wouldn't exist. Wondering if you would consider that acceptable and if a note just saying the behavior of the provider, so users are aware.

There are a couple providers' APIs that don't provide safe ways to update things where you have to delete before you can create. I have https://github.com/github/octodns/issues/144 to actually fix this for CloudFlare as they have an update API which needs to be used rather than delete and create. If the provider doesn't have an update (which atomically makes the change) I don't think there's much we can really do 😞 .

Do you think that we should change OctoDNS to know how to take a relative value from a provider, make it absolute, then compare the absolute YAML value to it to determine if a change needs to take place? This would probably be a relatively easy change in the changes method of ValueMixin and ValuesMixin inside Record

Probably not tbh. I've tried to steer clear of leaking provider specifics into the core model of things. I think translating these is the right way to go since that makes them RFC compliant. Given the workflow of showing diffs before apply them it should be safe and clear what octoDNS is going to do to "fix" the records before people tell it to do so. The end user is always reviewing the changes and giving them the implicit 👍  by adding the --doit flag.

I can only think of adding in another exception to the client that is raised when the API responds saying the action is not allowed.

Is is possible to differentiate between there was a general error and I can't do that b/c it's being used? Seems like the best bet here is just to make the error message as clear as it's reasonably possible to make it.


Deploy the app

TBD:

where to deploy the server
where to deploy the frontend

Check Azure Static Web Apps!

Try as it is described here

Done, mostly in #43 - later just needed to create proper configuration in Azure


Add Loading States for Request & Permit Holder Cards

Notion ticket link

Add Loading States for Request & Permit Holder Tables

Implementation description

Notes

Checklist

[ ] My PR name is descriptive, is in imperative tense and starts with one of the following: [Feature],[Improvement] or [Fix],
[ ] I have run the appropriate linter(s)
[ ] I have requested a review from the RCD team on GitHub, or specific people who are associated with this ticket

Moved to PR #212


PARQUET-2471: Add support for geometry logical type

This is the PoC of https://github.com/apache/parquet-format/pull/240
Jira

[ ] My PR addresses the following Parquet Jira issues and references
them in the PR title. For example, "PARQUET-1234: My Parquet PR"

https://issues.apache.org/jira/browse/PARQUET-XXX
In case you are adding a dependency, check if the license complies with
the ASF 3rd Party License Policy.

Tests

[ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[ ] My commits all reference Jira issues in their subject lines. In addition, my commits follow the guidelines
from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters (not including Jira issue reference)
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Style

[ ] My contribution adheres to the code style guidelines and Spotless passes.

To apply the necessary changes, run mvn spotless:apply -Pvector-plugins

Documentation

[ ] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain Javadoc that explain what it does

Thanks @paleolimbot for the quick review! I've addressed your feedback and also added page index support for geometry stats. BTW, it is a convention that we need PoC on another Parquet implementation to move forward the proposal. I plan to add similar things to parquet-cpp. Do you happen to know any JTS-parity on the C++ side? Or do you have a plan to implement the PoC? I guess there should be a lot of existing code on the GeoParquet side.

@wgtmac The JTS-parity on C++ side is GEOS, which is a C++ port of JTS: https://github.com/libgeos/geos
Note that: GEOS is LGPL 2.1, which is NOT compatible with ASF

Core sedona contributors @Kontinuation and @zhangfengcdt , can you also review this?
@wgtmac Thanks for putting together this PR. I guess you might need some help from the Sedona community regarding the Java geometry implementation together with JTS. We can work together to implement this POC.

Thanks @jiayuasu for your valuable feedback! Yes, it would be great if we can get direct help from geospatial experts!

Close this in favor of https://github.com/apache/parquet-java/pull/2971


perform co-adding step after all corrections/calibrations on each image

Todo

[ ] Move step 11 (corrections) before step 10 (uvotimsum)
[ ] Remove step 9 (sort_by_year) as we will not be summing within the year
[ ] Step 10 (call into uvotimsum) replace step 12, since the summing can now be done in a single step
[ ] Zero point corrections done for each fits file separately
[ ] Update docs with the new order of steps

Current steps

step
script
input
output

08
uvotskylss
*sk_corr.img
output_uvotskylss_{...}_uat_{evt,img}_{FFF}_sk_corr.txt,{...}_uat_{evt,img}_{FFF}_lss_corr.img

09
sort_by_year

files moved into folders

10
uvotimsum

all_{FFF}_{ex,lss,mk,sk}.img,output_uvotimsum_{FFF}_{ex,lss,sk}.txt,sum_{FFF}_{ex,lss,nm,sk}.img,{...}_uat_{evt,img}_{FFF}_mk_corr_new.img

11
corrections

sum_{FFF}_nm_{coi,coilss,coilsszp}.img

12
combine

total_sum_{FFF}_{ex,nm,sk}.fits, sum_{FFF}_ex_r.img, sum_{FFF}_nm_coilsszp_{c,c_r}.img

13
calibration

NGC0628_final_{FFF}_Jy.fits

When finished
When finished should look something like this, with inputs/outputs still to be defined

step
script
input
output

08
uvotskylss
*sk_corr.img
output_uvotskylss_{...}_uat_{evt,img}_{FFF}_sk_corr.txt,{...}_uat_{evt,img}_{FFF}_lss_corr.img

09
corrections

???

10
uvotimsum

???

11
calibration

NGC0628_final_{FFF}_Jy.fits

Notes:

use uvotimsum to combine to a single observation, this would be before applying corrections (so before step 9)
for vectorized std: might think about using a sliding window for calculating percentiles over a window (https://docs.scipy.org/doc/scipy/reference/reference/ndimage.html#module-scipy.ndimage) — e.g. approximate std as 0.5 * (84th - 16th percentile ). Also https://numpy.org/devdocs/reference/generated/numpy.lib.stride_tricks.sliding_window_view.html


Can not download some files

I can download Image from google drive. But can not download Excel、Word or PDF.
Here is the exception:
 com.google.android.gms.common.api.ApiException: 10: This file is not openable.

I don't know why the file is not openable.Because I use the same method to upload Excel and Images.
The Code:
        OpenFileCallback openCallback = new OpenFileCallback() {
            @Override public void onProgress(long bytesDownloaded, long bytesExpected) {
                int progress = (int) (bytesDownloaded * 100 / bytesExpected);
                Log.d(TAG, String.format("Loading progress: %d percent", progress));
            }

            @Override public void onContents(@NonNull DriveContents driveContents) {
                try {
                    InputStream inputStream = driveContents.getInputStream();
                    java.io.File file = new java.io.File(getContext().getCacheDir(),
                        metadata.getOriginalFilename());
                    OutputStream output = new FileOutputStream(file);
                    try {
                        byte[] buffer = new byte[4 * 1024]; // or other buffer size
                        int read;

                        while ((read = inputStream.read(buffer)) != -1) {
                            output.write(buffer, 0, read);
                        }

                        output.flush();
                    } finally {
                        output.close();
                        mDriveResourceClient.discardContents(driveContents);
                    }
                } catch (IOException e) {
                    onError(e);
                }
            }

            @Override public void onError(@NonNull Exception e) {
                // Handle error
                // [START_EXCLUDE]
                Log.e(TAG, "Unable to read contents", e);
                DialogUtil.hideLoadingDialog();
                // [END_EXCLUDE]
            }
        };

        mDriveResourceClient.openFile(driveFile, DriveFile.MODE_READ_ONLY, openCallback);

Hey, i got same issue. I wrote post on StackOverflow (https://stackoverflow.com/questions/47518464/google-drive-api-cant-open-all-file-formats), but nobody answered. I will propably write to google with this issue today. It would be nice to have coment, that you have replicated the issue.

@MikulasVanousek  yes I got the same problem that can't open the office formats and download it, then the code throw the same exception. How do you fix it?

I dont' think it is possible to open office formats with google drive api
On Thu, Jun 28, 2018, 4:43 AM shawsen<EMAIL_ADDRESS>wrote:

@Even201314 https://github.com/Even201314 How do you fix it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gsuitedevs/android-samples/issues/70#issuecomment-400893192,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Af2tUrd1RD_TwBGkeoIj4rNo6qri4yXRks5uBELOgaJpZM4RkN4W
.

@MikulasVanousek Thanks MikulasVanousek .
This google drive api team was so lazy that nobody from team can focuse on it.
I have some question about thumnail.
How do you get the image‘s thumnail by api?

This issue tracker is for reporting bugs in the sample code. For general support options please see this page:
https://developers.google.com/drive/android/support


[#3890] feat(catalog-lakehouse-paimon): Add a basic integrate test code skeleton for Paimon Catalog

What changes were proposed in this pull request?
Add a basic integrate test code skeleton for Paimon Catalog
Why are the changes needed?
Fix: https://github.com/datastrato/gravitino/issues/3890
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Basic ITs.

Hi @FANNG1 could you help review this PR？ Thank you!

LGTM, except minor comments

@FANNG1 please help review again, Thanks!

could you help re-trigger the pipeline? thank you.
CatalogsPageTest > testClickCatalogLink() FAILED
    org.opentest4j.AssertionFailedError: expected: <true> but was: <false>
        at org.junit.jupiter.api.AssertionUtils.fail(AssertionUtils.java:55)
        at org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:40)
        at org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:35)
        at org.junit.jupiter.api.Assertions.assertTrue(Assertions.java:179)
        at com.datastrato.gravitino.integration.test.web.ui.CatalogsPageTest.testClickCatalogLink(CatalogsPageTest.java:396)

@FANNG1 could you help review again? Thanks!

LGTM


Enable OpenSSF Scorecard to enhance security practices across the project

Hi, I'm Harshita. I’m working with CNCF and the Google Open Source Security Team for the GSoC 2024 term. We are collaborating to enhance security practices across various CNCF projects. The goal is to improve security for all CNCF projects by both using OpenSSF Scorecards and implementing its security improvements.
The Open Source Security Foundation (OpenSSF) Scorecard is a tool designed to evaluate the security posture of open-source projects. This has the Scorecard GitHub Action, which automates the process by running security checks on the GitHub repository. By integrating this Action into the repository's workflow, developers can continuously monitor the project’s security posture. The Scorecard checks cover various security best practices and provide scores for multiple categories. Some checks include Code Reviews, Branch Protection, Signed Releases, etc.
The workflow runs on every change in the main branch. It publishes the Scorecard checks' results to the project's security dashboard and includes suggestions on how to solve any issues. This Action has already been adopted by 1800+ projects, with prominent users like Tensorflow, Angular, sos.dev, deps.dev, and many CNCF projects.
Once the Scorecard GitHub Action is set up and running, the results can be displayed as a badge in the repository's README file. This badge serves as a quick indicator of the project's security posture, helping users and contributors evaluate the project's security practices quickly.
Why is this needed:
The OpenSSF Scorecard improves open-source project's security by providing automated, transparent assessments of their security practices. It will help you identify vulnerabilities, adhere to best practices, and continuously enhance your security posture, increasing user trust and reducing the risk of security exploits.
I'll be the one to create the PR to add the scorecard GitHub action, and I will also work with you to remediate the identified vulnerabilities. I'll go through each scorecard check to see where the score has dropped and how it can be improved.
Would you be interested in a PR which adds this Action?
/cc @joycebrum @diogoteles08 @pnacht @nate-double-u

(I didn't get a chance, but I plan to review how OpenSSF Scorecard will help/interact with Helm and update)

@gjenkins8 should I proceed with the PR for this?

(apologies, I thought I updated this previously; I must not have hit the Comment button)
Yes, please enable the github action. We can discuss the specifics of the actions behavior on the PR.
From a manual scan from my laptop, the scan looks fairly reasonable:
RESULTS
-------
Aggregate score: 8.1 / 10

Check scores:
|---------|------------------------|--------------------------------|-----------------------------------------------------------------------------------------------------------------------|
|  SCORE  |          NAME          |             REASON             |                                               DOCUMENTATION/REMEDIATION                                               |
|---------|------------------------|--------------------------------|-----------------------------------------------------------------------------------------------------------------------|
| 10 / 10 | Binary-Artifacts       | no binaries found in the repo  | https://github.com/ossf/scorecard/blob/ea7e27ed41b76ab879c862fa0ca4cc9c61764ee4/docs/checks.md#binary-artifacts       |
|---------|------------------------|--------------------------------|-----------------------------------------------------------------------------------------------------------------------|
| 0 / 10  | Branch-Protection      | branch protection not enabled  | https://github.com/ossf/scorecard/blob/ea7e27ed41b76ab879c862fa0ca4cc9c61764ee4/docs/checks.md#branch-protection      |
|         |                        | on development/release         |                                                                                |
|         |                        | branches                       |                                                                                |
|---------|------------------------|--------------------------------|-----------------------------------------------------------------------------------------------------------------------|
| 9 / 10  | CI-Tests               | 17 out of 18 merged PRs        | https://github.com/ossf/scorecard/blob/ea7e27ed41b76ab879c862fa0ca4cc9c61764ee4/docs/checks.md#ci-tests               |
|         |                        | checked by a CI test -- score  |                                                                                |
|         |                        | normalized to 9                |                                                                                |
|---------|------------------------|--------------------------------|-----------------------------------------------------------------------------------------------------------------------|
| 5 / 10  | CII-Best-Practices     | badge detected: Passing        | https://github.com/ossf/scorecard/blob/ea7e27ed41b76ab879c862fa0ca4cc9c61764ee4/docs/checks.md#cii-best-practices     |
|---------|------------------------|--------------------------------|-----------------------------------------------------------------------------------------------------------------------|
| 10 / 10 | Code-Review            | all changesets reviewed        | https://github.com/ossf/scorecard/blob/ea7e27ed41b76ab879c862fa0ca4cc9c61764ee4/docs/checks.md#code-review            |
|---------|------------------------|--------------------------------|-----------------------------------------------------------------------------------------------------------------------|
| 10 / 10 | Contributors           | project has 71 contributing    | https://github.com/ossf/scorecard/blob/ea7e27ed41b76ab879c862fa0ca4cc9c61764ee4/docs/checks.md#contributors           |
|         |                        | companies or organizations     |                                                                                |
|---------|------------------------|--------------------------------|-----------------------------------------------------------------------------------------------------------------------|
| 10 / 10 | Dangerous-Workflow     | no dangerous workflow patterns | https://github.com/ossf/scorecard/blob/ea7e27ed41b76ab879c862fa0ca4cc9c61764ee4/docs/checks.md#dangerous-workflow     |
|         |                        | detected                       |                                                                                |
|---------|------------------------|--------------------------------|-----------------------------------------------------------------------------------------------------------------------|
| 10 / 10 | Dependency-Update-Tool | update tool detected           | https://github.com/ossf/scorecard/blob/ea7e27ed41b76ab879c862fa0ca4cc9c61764ee4/docs/checks.md#dependency-update-tool |
|---------|------------------------|--------------------------------|-----------------------------------------------------------------------------------------------------------------------|
| 10 / 10 | Fuzzing                | project is fuzzed              | https://github.com/ossf/scorecard/blob/ea7e27ed41b76ab879c862fa0ca4cc9c61764ee4/docs/checks.md#fuzzing                |
|---------|------------------------|--------------------------------|-----------------------------------------------------------------------------------------------------------------------|
| 10 / 10 | License                | license file detected          | https://github.com/ossf/scorecard/blob/ea7e27ed41b76ab879c862fa0ca4cc9c61764ee4/docs/checks.md#license                |
|---------|------------------------|--------------------------------|-----------------------------------------------------------------------------------------------------------------------|
| 10 / 10 | Maintained             | 30 commit(s) and 4 issue       | https://github.com/ossf/scorecard/blob/ea7e27ed41b76ab879c862fa0ca4cc9c61764ee4/docs/checks.md#maintained             |
|         |                        | activity found in the last 90  |                                                                                |
|         |                        | days -- score normalized to 10 |                                                                                |
|---------|------------------------|--------------------------------|-----------------------------------------------------------------------------------------------------------------------|
| ?       | Packaging              | packaging workflow not         | https://github.com/ossf/scorecard/blob/ea7e27ed41b76ab879c862fa0ca4cc9c61764ee4/docs/checks.md#packaging              |
|         |                        | detected                       |                                                                                |
|---------|------------------------|--------------------------------|-----------------------------------------------------------------------------------------------------------------------|
| 9 / 10  | Pinned-Dependencies    | dependency not pinned by hash  | https://github.com/ossf/scorecard/blob/ea7e27ed41b76ab879c862fa0ca4cc9c61764ee4/docs/checks.md#pinned-dependencies    |
|         |                        | detected -- score normalized   |                                                                                |
|         |                        | to 9                           |                                                                                |
|---------|------------------------|--------------------------------|-----------------------------------------------------------------------------------------------------------------------|
| 9 / 10  | SAST                   | SAST tool detected but not run | https://github.com/ossf/scorecard/blob/ea7e27ed41b76ab879c862fa0ca4cc9c61764ee4/docs/checks.md#sast                   |
|         |                        | on all commits                 |                                                                                |
|---------|------------------------|--------------------------------|-----------------------------------------------------------------------------------------------------------------------|
| 9 / 10  | Security-Policy        | security policy file detected  | https://github.com/ossf/scorecard/blob/ea7e27ed41b76ab879c862fa0ca4cc9c61764ee4/docs/checks.md#security-policy        |
|---------|------------------------|--------------------------------|-----------------------------------------------------------------------------------------------------------------------|
| 8 / 10  | Signed-Releases        | 5 out of the last 5 releases   | https://github.com/ossf/scorecard/blob/ea7e27ed41b76ab879c862fa0ca4cc9c61764ee4/docs/checks.md#signed-releases        |
|         |                        | have a total of 5 signed       |                                                                                |
|         |                        | artifacts.                     |                                                                                |
|---------|------------------------|--------------------------------|-----------------------------------------------------------------------------------------------------------------------|
| 0 / 10  | Token-Permissions      | detected GitHub workflow       | https://github.com/ossf/scorecard/blob/ea7e27ed41b76ab879c862fa0ca4cc9c61764ee4/docs/checks.md#token-permissions      |
|         |                        | tokens with excessive          |                                                                                |
|         |                        | permissions                    |                                                                                |
|---------|------------------------|--------------------------------|-----------------------------------------------------------------------------------------------------------------------|
| 10 / 10 | Vulnerabilities        | 0 existing vulnerabilities     | https://github.com/ossf/scorecard/blob/ea7e27ed41b76ab879c862fa0ca4cc9c61764ee4/docs/checks.md#vulnerabilities        |
|         |                        | detected                       |                                                                                |
|---------|------------------------|--------------------------------|-----------------------------------------------------------------------------------------------------------------------|


Window origin doesn't change with resolution

I'm not sure this is really a bug. Can't you move the window?

I'm not able to move the window; alt-tabbing is the usual solution but MonoGame keeps the mouse at the center of the TrueCraft window and it can't be moved. We can add event handlers for Game.OnActivated and Game.OnDeactivated that toggle mouse locking.

I see. FWIW, pressing Tab will unlock the mouse.

Ah, tab did it. Thank you.


Love the work so far, let's chat.

I really like your work on this project so far. I'd love to chat more about your Revit knowledge! How can I reach you directly?

Sorry I just notice this thread. Please contact me directly via WhatsApp or Telegram with phone number +43<PHONE_NUMBER>5

I’ve been working on a general CAD recognition method which could possibly provide more data for your implementation. Please let me know if you are still into this project and we could discuss more details. BTW I left you a message on WhatsApp and Bilibili, we could exchange our wechat there.

Great to hear from you Liangyi. Surely I'd love to reboot the project and discuss it in more detail via WeChat. CAD recognition is exactly the missing piece in coding the plugin. I have sent you the buddy request.

I just started following you great job you do it how i can reach you .im looking for your help for some issues related to rivet api


Onedark Plugin highlights override Codewindow's

I am using navarasu/onedark.vim colorscheme, and with it, I am unable to change CodeWindow's color manually.
The highlight group named in onedark/highlights.lua uses FloatBorder to change the borders of the window instead of Codewindow's built-in CodewindowBorder and CodewindowBackground.
Something interesting happens with this plugin though.
When setting the custom highlights:
vim.api.nvim_set_hl(0, 'CodewindowBorder', {fg = '#ffff00'})
vim.api.nvim_set_hl(0, 'CodewindowBackground', {fg = '#ffff00'})

I do not get the expected outcome. Instead, I get some random chunks inside the window being colored (mostly "grey" parts in this example), and the border being unaffected.
For now I am using vim.api.nvim_set_hl(0, 'FloatBorder', {fg = '#4fa6ed'}) (this also works for bg)

Highlights Disabled
Highlights Enabled
FloatBorder used

Try linking the CodewindowBorder and CodewindowBackground highlight groups to the relevant ones from the highlighting.

I do not get the expected outcome. Instead, I get some random chunks inside the window being colored (mostly "grey" parts in this example), and the border being unaffected.

It's actually probably because "CodewindowBackground" gets used for the dots that do not get any highlight at all. So don't set the foreground to yellow, instead set it to whatever you want those to appear as.

Any change on this?


[ACR] az acr login:Remove the preview flag on '--expose-token'

History Notes:
(Fill in the following template if multiple notes are needed, otherwise PR title will be used for history note.)
[Component Name 1] (BREAKING CHANGE:) (az command:) make some customer-facing change.
[Component Name 2] (BREAKING CHANGE:) (az command:) make some customer-facing change.

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

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

[x] I adhere to the Command Guidelines.

acr

hi @Wwwsylvia is the PR ok to merge now?

@yungezz, yes the PR is ready to merge


New jupyter service

Issue description
Follow up of the newly merged jupyter service (thanks to the authors, that's super cool !):
https://github.com/NixOS/nixpkgs/commit/4d3ce5ca36a145748a4938cb0127c115d8fbacf0 from the PR https://github.com/NixOS/nixpkgs/pull/33673
First of all I've noticed a few errors in the doc (space/missing curly dollar) that generates errors.
For instance if I use the exmaple given for services.jupyter.kernels, I get:
string 'lib/python3.6/site-packages/ipykernel/resources/logo-32x32.png' doesn't represent an absolute path, at /home/teto/dotfiles/nixpkgs/modules/jupyter.nix:35:20
I am looking at getting ihaskell running through this new service which makes ./services/misc/ihaskell.nix redundant  (should we remove it ?). It would be better to have the ihaskell package generate a kernel.json as sagemath does (well it's just copied from upstream "/share/jupyter/kernels/sagemath/kernel.json").
A bit of doc on kernel specs:
nixos/modules/services/development/jupyter/kernel-options.nix
https://jupyter-client.readthedocs.io/en/stable/kernels.html#kernel-specs

I managed to make the ihaskell work with the new service (see https://github.com/gibiansky/IHaskell/issues/920) but it's still impractical since I had to wrap ihaskell etc. We definitely should have packages generate a kernel.json and just load it the jupyter service (eventually using JUPYTER_PATH).

Just to chime in with my experience:

the logo32x32 and logo64x64 docs are incorrect, I couldn't get them to work after trying to point to the right place and just commented them out for now. For the record, they should point here but when I try to do so it says that logo32x32 should either be null or path or something like that.
if running Jupyter behind Nginx, you need to enable proxyWebsockets, for example:"example.com".locations."/" = {
    proxyPass = "http://111.222.333.444:9999";
    proxyWebsockets = true;
}

You should probably also enable all the services.nginx.recommended* options.
argv should be: [ "${env.interpreter}" "-m" "ipykernel_launcher" "-f" "{connection_file}" ], optionally broken up into a list of multiple strings. The last argument {connection_file} seems to be a special flag passed to ipykernel_launcher

Some details on what's necessary in the kernel spec: https://github.com/NixOS/nixpkgs/issues/10713#issuecomment-276938947

@teto You might want to take a look at #61177 and https://github.com/gibiansky/IHaskell/pull/1027 for the ihaskell integration.

Alright, closing. Indeed no longer interested now that I'm using jupyterWIth.