Focus on input field crashes the app

Hi,
I'm having an issue with Turbo-ios 7.0.0.rc and all version its versions. As when I focus on the input field the turbo-ios app crashes with the error below.  Anyone faced that problem?
Xcode 14.2, Rails <IP_ADDRESS>, app generated with scaffold

2023-02-21 22:55:11.191251+0100 the-party[48476:1065166] [LayoutConstraints] Unable to simultaneously satisfy constraints.
	Probably at least one of the constraints in the following list is one you don't want.
	Try this:
		(1) look at each constraint and try to figure out which you don't expect;
		(2) find the code that added the unwanted constraint or constraints and fix it.
	(Note: If you're seeing NSAutoresizingMaskLayoutConstraints that you don't understand, refer to the documentation for the UIView property translatesAutoresizingMaskIntoConstraints)
(
    "<NSAutoresizingMaskLayoutConstraint:0x600001ee98b0 h=--& v=--& _UIToolbarContentView:0x144214350.width == 0   (active)>",
    "<NSLayoutConstraint:0x600001e8f200 H:|-(0)-[_UIButtonBarStackView:0x144216a80]   (active, names: '|':_UIToolbarContentView:0x144214350 )>",
    "<NSLayoutConstraint:0x600001e8f250 H:[_UIButtonBarStackView:0x144216a80]-(0)-|   (active, names: '|':_UIToolbarContentView:0x144214350 )>",
    "<NSLayoutConstraint:0x600001e8ba70 'IB_Leading_Leading' H:|-(0)-[_UIModernBarButton:0x143729900]   (active, names: '|':_UIButtonBarButton:0x143729590 )>",
    "<NSLayoutConstraint:0x600001ee8000 'IB_Leading_Leading' H:|-(>=5)-[_UIModernBarButton:0x14372ab50]   (active, names: '|':_UIButtonBarButton:0x143723c40 )>",
    "<NSLayoutConstraint:0x600001e8bac0 'IB_Trailing_Trailing' H:[_UIModernBarButton:0x143729900]-(>=8)-|   (active, names: '|':_UIButtonBarButton:0x143729590 )>",
    "<NSLayoutConstraint:0x600001ee8050 'IB_Trailing_Trailing' H:[_UIModernBarButton:0x14372ab50]-(>=5)-|   (active, names: '|':_UIButtonBarButton:0x143723c40 )>",
    "<NSLayoutConstraint:0x600001ee87d0 'TB_Leading_Leading' H:|-(8)-[_UIModernBarButton:0x14372c2d0'Done']   (active, names: '|':_UIButtonBarButton:0x14372b370 )>",
    "<NSLayoutConstraint:0x600001ee8820 'TB_Trailing_Trailing' H:[_UIModernBarButton:0x14372c2d0'Done']-(0)-|   (active, names: '|':_UIButtonBarButton:0x14372b370 )>",
    "<NSLayoutConstraint:0x600001ee8be0 'UISV-canvas-connection' UILayoutGuide:0x6000004b48c0'UIViewLayoutMarginsGuide'.leading == _UIButtonBarButton:0x143729590.leading   (active)>",
    "<NSLayoutConstraint:0x600001ee8eb0 'UISV-canvas-connection' UILayoutGuide:0x6000004b48c0'UIViewLayoutMarginsGuide'.trailing == _UIButtonBarButton:0x14372b370.trailing   (active)>",
    "<NSLayoutConstraint:0x600001ee8f00 'UISV-spacing' H:[_UIButtonBarButton:0x143729590]-(0)-[UIView:0x1437256e0]   (active)>",
    "<NSLayoutConstraint:0x600001ee8f50 'UISV-spacing' H:[UIView:0x1437256e0]-(0)-[_UIButtonBarButton:0x143723c40]   (active)>",
    "<NSLayoutConstraint:0x600001ee8fa0 'UISV-spacing' H:[_UIButtonBarButton:0x143723c40]-(0)-[UIView:0x14372b1c0]   (active)>",
    "<NSLayoutConstraint:0x600001ee8ff0 'UISV-spacing' H:[UIView:0x14372b1c0]-(0)-[_UIButtonBarButton:0x14372b370]   (active)>",
    "<NSLayoutConstraint:0x600001e8f110 'UIView-leftMargin-guide-constraint' H:|-(0)-[UILayoutGuide:0x6000004b48c0'UIViewLayoutMarginsGuide'](LTR)   (active, names: '|':_UIButtonBarStackView:0x144216a80 )>",
    "<NSLayoutConstraint:0x600001e8f1b0 'UIView-rightMargin-guide-constraint' H:[UILayoutGuide:0x6000004b48c0'UIViewLayoutMarginsGuide']-(0)-|(LTR)   (active, names: '|':_UIButtonBarStackView:0x144216a80 )>"
)

Will attempt to recover by breaking constraint
<NSLayoutConstraint:0x600001e8bac0 'IB_Trailing_Trailing' H:[_UIModernBarButton:0x143729900]-(>=8)-|   (active, names: '|':_UIButtonBarButton:0x143729590 )>

Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger.
The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKitCore/UIView.h> may also be helpful.
2023-02-21 22:55:11.234256+0100 the-party[48476:1065166] [LayoutConstraints] Unable to simultaneously satisfy constraints.
	Probably at least one of the constraints in the following list is one you don't want.
	Try this:
		(1) look at each constraint and try to figure out which you don't expect;
		(2) find the code that added the unwanted constraint or constraints and fix it.
	(Note: If you're seeing NSAutoresizingMaskLayoutConstraints that you don't understand, refer to the documentation for the UIView property translatesAutoresizingMaskIntoConstraints)
(
    "<NSAutoresizingMaskLayoutConstraint:0x600001ee98b0 h=--& v=--& _UIToolbarContentView:0x144214350.width == 0   (active)>",
    "<NSLayoutConstraint:0x600001e8f200 H:|-(0)-[_UIButtonBarStackView:0x144216a80]   (active, names: '|':_UIToolbarContentView:0x144214350 )>",
    "<NSLayoutConstraint:0x600001e8f250 H:[_UIButtonBarStackView:0x144216a80]-(0)-|   (active, names: '|':_UIToolbarContentView:0x144214350 )>",
    "<NSLayoutConstraint:0x600001ee8000 'IB_Leading_Leading' H:|-(>=5)-[_UIModernBarButton:0x14372ab50]   (active, names: '|':_UIButtonBarButton:0x143723c40 )>",
    "<NSLayoutConstraint:0x600001ee8050 'IB_Trailing_Trailing' H:[_UIModernBarButton:0x14372ab50]-(>=5)-|   (active, names: '|':_UIButtonBarButton:0x143723c40 )>",
    "<NSLayoutConstraint:0x600001ee87d0 'TB_Leading_Leading' H:|-(8)-[_UIModernBarButton:0x14372c2d0'Done']   (active, names: '|':_UIButtonBarButton:0x14372b370 )>",
    "<NSLayoutConstraint:0x600001ee8820 'TB_Trailing_Trailing' H:[_UIModernBarButton:0x14372c2d0'Done']-(0)-|   (active, names: '|':_UIButtonBarButton:0x14372b370 )>",
    "<NSLayoutConstraint:0x600001ee8be0 'UISV-canvas-connection' UILayoutGuide:0x6000004b48c0'UIViewLayoutMarginsGuide'.leading == _UIButtonBarButton:0x143729590.leading   (active)>",
    "<NSLayoutConstraint:0x600001ee8eb0 'UISV-canvas-connection' UILayoutGuide:0x6000004b48c0'UIViewLayoutMarginsGuide'.trailing == _UIButtonBarButton:0x14372b370.trailing   (active)>",
    "<NSLayoutConstraint:0x600001ee8f00 'UISV-spacing' H:[_UIButtonBarButton:0x143729590]-(0)-[UIView:0x1437256e0]   (active)>",
    "<NSLayoutConstraint:0x600001ee8f50 'UISV-spacing' H:[UIView:0x1437256e0]-(0)-[_UIButtonBarButton:0x143723c40]   (active)>",
    "<NSLayoutConstraint:0x600001ee8fa0 'UISV-spacing' H:[_UIButtonBarButton:0x143723c40]-(0)-[UIView:0x14372b1c0]   (active)>",
    "<NSLayoutConstraint:0x600001ee8ff0 'UISV-spacing' H:[UIView:0x14372b1c0]-(0)-[_UIButtonBarButton:0x14372b370]   (active)>",
    "<NSLayoutConstraint:0x600001e8f110 'UIView-leftMargin-guide-constraint' H:|-(0)-[UILayoutGuide:0x6000004b48c0'UIViewLayoutMarginsGuide'](LTR)   (active, names: '|':_UIButtonBarStackView:0x144216a80 )>",
    "<NSLayoutConstraint:0x600001e8f1b0 'UIView-rightMargin-guide-constraint' H:[UILayoutGuide:0x6000004b48c0'UIViewLayoutMarginsGuide']-(0)-|(LTR)   (active, names: '|':_UIButtonBarStackView:0x144216a80 )>"
)

Will attempt to recover by breaking constraint
<NSLayoutConstraint:0x600001ee8050 'IB_Trailing_Trailing' H:[_UIModernBarButton:0x14372ab50]-(>=5)-|   (active, names: '|':_UIButtonBarButton:0x143723c40 )>

Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger.
The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKitCore/UIView.h> may also be helpful.
2023-02-21 22:55:11.234893+0100 the-party[48476:1065166] [LayoutConstraints] Unable to simultaneously satisfy constraints.
	Probably at least one of the constraints in the following list is one you don't want.
	Try this:
		(1) look at each constraint and try to figure out which you don't expect;
		(2) find the code that added the unwanted constraint or constraints and fix it.
	(Note: If you're seeing NSAutoresizingMaskLayoutConstraints that you don't understand, refer to the documentation for the UIView property translatesAutoresizingMaskIntoConstraints)
(
    "<NSAutoresizingMaskLayoutConstraint:0x600001ee98b0 h=--& v=--& _UIToolbarContentView:0x144214350.width == 0   (active)>",
    "<NSLayoutConstraint:0x600001e8f200 H:|-(0)-[_UIButtonBarStackView:0x144216a80]   (active, names: '|':_UIToolbarContentView:0x144214350 )>",
    "<NSLayoutConstraint:0x600001e8f250 H:[_UIButtonBarStackView:0x144216a80]-(0)-|   (active, names: '|':_UIToolbarContentView:0x144214350 )>",
    "<NSLayoutConstraint:0x600001ee87d0 'TB_Leading_Leading' H:|-(8)-[_UIModernBarButton:0x14372c2d0'Done']   (active, names: '|':_UIButtonBarButton:0x14372b370 )>",
    "<NSLayoutConstraint:0x600001ee8820 'TB_Trailing_Trailing' H:[_UIModernBarButton:0x14372c2d0'Done']-(0)-|   (active, names: '|':_UIButtonBarButton:0x14372b370 )>",
    "<NSLayoutConstraint:0x600001ee8be0 'UISV-canvas-connection' UILayoutGuide:0x6000004b48c0'UIViewLayoutMarginsGuide'.leading == _UIButtonBarButton:0x143729590.leading   (active)>",
    "<NSLayoutConstraint:0x600001ee8eb0 'UISV-canvas-connection' UILayoutGuide:0x6000004b48c0'UIViewLayoutMarginsGuide'.trailing == _UIButtonBarButton:0x14372b370.trailing   (active)>",
    "<NSLayoutConstraint:0x600001ee8f00 'UISV-spacing' H:[_UIButtonBarButton:0x143729590]-(0)-[UIView:0x1437256e0]   (active)>",
    "<NSLayoutConstraint:0x600001ee8f50 'UISV-spacing' H:[UIView:0x1437256e0]-(0)-[_UIButtonBarButton:0x143723c40]   (active)>",
    "<NSLayoutConstraint:0x600001ee8fa0 'UISV-spacing' H:[_UIButtonBarButton:0x143723c40]-(0)-[UIView:0x14372b1c0]   (active)>",
    "<NSLayoutConstraint:0x600001ee8ff0 'UISV-spacing' H:[UIView:0x14372b1c0]-(0)-[_UIButtonBarButton:0x14372b370]   (active)>",
    "<NSLayoutConstraint:0x600001e8f110 'UIView-leftMargin-guide-constraint' H:|-(0)-[UILayoutGuide:0x6000004b48c0'UIViewLayoutMarginsGuide'](LTR)   (active, names: '|':_UIButtonBarStackView:0x144216a80 )>",
    "<NSLayoutConstraint:0x600001e8f1b0 'UIView-rightMargin-guide-constraint' H:[UILayoutGuide:0x6000004b48c0'UIViewLayoutMarginsGuide']-(0)-|(LTR)   (active, names: '|':_UIButtonBarStackView:0x144216a80 )>"
)

Will attempt to recover by breaking constraint
<NSLayoutConstraint:0x600001ee8820 'TB_Trailing_Trailing' H:[_UIModernBarButton:0x14372c2d0'Done']-(0)-|   (active, names: '|':_UIButtonBarButton:0x14372b370 )>

Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger.
The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKitCore/UIView.h> may also be helpful.
2023-02-21 22:55:11.235715+0100 the-party[48476:1065166] [LayoutConstraints] Unable to simultaneously satisfy constraints.
	Probably at least one of the constraints in the following list is one you don't want.
	Try this:
		(1) look at each constraint and try to figure out which you don't expect;
		(2) find the code that added the unwanted constraint or constraints and fix it.
	(Note: If you're seeing NSAutoresizingMaskLayoutConstraints that you don't understand, refer to the documentation for the UIView property translatesAutoresizingMaskIntoConstraints)
(
    "<NSAutoresizingMaskLayoutConstraint:0x600001ee9950 h=--& v=--& _UIToolbarContentView:0x144214350.height == 0   (active)>",
    "<NSLayoutConstraint:0x600001e8f2a0 V:|-(0)-[_UIButtonBarStackView:0x144216a80]   (active, names: '|':_UIToolbarContentView:0x144214350 )>",
    "<NSLayoutConstraint:0x600001e8f2f0 _UIButtonBarStackView:0x144216a80.bottom == _UIToolbarContentView:0x144214350.bottom   (active)>",
    "<NSLayoutConstraint:0x600001ee9e50 UIImageView:0x14372a730.centerY == _UIModernBarButton:0x143729900.centerY   (active)>",
    "<NSLayoutConstraint:0x600001e8bd40 'IB_Baseline_Baseline' _UIModernBarButton:0x143729900.lastBaseline == UILayoutGuide:0x6000004bc700'UIViewLayoutMarginsGuide'.bottom   (active)>",
    "<NSLayoutConstraint:0x600001e8bd90 'IB_Top_Top' V:|-(>=0)-[_UIModernBarButton:0x143729900]   (active, names: '|':_UIButtonBarButton:0x143729590 )>",
    "<NSLayoutConstraint:0x600001e8bed0 'UIButtonBar.maximumAlignmentSize' _UIButtonBarButton:0x143729590.height == UILayoutGuide:0x6000004b48c0'UIViewLayoutMarginsGuide'.height   (active)>",
    "<NSLayoutConstraint:0x600001e8f160 'UIView-bottomMargin-guide-constraint' V:[UILayoutGuide:0x6000004b48c0'UIViewLayoutMarginsGuide']-(0)-|   (active, names: '|':_UIButtonBarStackView:0x144216a80 )>",
    "<NSLayoutConstraint:0x600001e8bca0 'UIView-bottomMargin-guide-constraint' V:[UILayoutGuide:0x6000004bc700'UIViewLayoutMarginsGuide']-(11)-|   (active, names: '|':_UIButtonBarButton:0x143729590 )>",
    "<NSLayoutConstraint:0x600001e8f0c0 'UIView-topMargin-guide-constraint' V:|-(0)-[UILayoutGuide:0x6000004b48c0'UIViewLayoutMarginsGuide']   (active, names: '|':_UIButtonBarStackView:0x144216a80 )>"
)

Will attempt to recover by breaking constraint
<NSLayoutConstraint:0x600001ee9e50 UIImageView:0x14372a730.centerY == _UIModernBarButton:0x143729900.centerY   (active)>

Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger.
The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKitCore/UIView.h> may also be helpful.
2023-02-21 22:55:11.236395+0100 the-party[48476:1065166] [LayoutConstraints] Unable to simultaneously satisfy constraints.
	Probably at least one of the constraints in the following list is one you don't want.
	Try this:
		(1) look at each constraint and try to figure out which you don't expect;
		(2) find the code that added the unwanted constraint or constraints and fix it.
	(Note: If you're seeing NSAutoresizingMaskLayoutConstraints that you don't understand, refer to the documentation for the UIView property translatesAutoresizingMaskIntoConstraints)
(
    "<NSAutoresizingMaskLayoutConstraint:0x600001ee9950 h=--& v=--& _UIToolbarContentView:0x144214350.height == 0   (active)>",
    "<NSLayoutConstraint:0x600001e8f2a0 V:|-(0)-[_UIButtonBarStackView:0x144216a80]   (active, names: '|':_UIToolbarContentView:0x144214350 )>",
    "<NSLayoutConstraint:0x600001e8f2f0 _UIButtonBarStackView:0x144216a80.bottom == _UIToolbarContentView:0x144214350.bottom   (active)>",
    "<NSLayoutConstraint:0x600001eecf00 UIImageView:0x14372ae80.centerY == _UIModernBarButton:0x14372ab50.centerY   (active)>",
    "<NSLayoutConstraint:0x600001ee82d0 'IB_Baseline_Baseline' _UIModernBarButton:0x14372ab50.lastBaseline == UILayoutGuide:0x6000004bc9a0'UIViewLayoutMarginsGuide'.bottom   (active)>",
    "<NSLayoutConstraint:0x600001ee8320 'IB_Top_Top' V:|-(>=0)-[_UIModernBarButton:0x14372ab50]   (active, names: '|':_UIButtonBarButton:0x143723c40 )>",
    "<NSLayoutConstraint:0x600001ee8460 'UIButtonBar.maximumAlignmentSize' _UIButtonBarButton:0x143723c40.height == UILayoutGuide:0x6000004b48c0'UIViewLayoutMarginsGuide'.height   (active)>",
    "<NSLayoutConstraint:0x600001e8f160 'UIView-bottomMargin-guide-constraint' V:[UILayoutGuide:0x6000004b48c0'UIViewLayoutMarginsGuide']-(0)-|   (active, names: '|':_UIButtonBarStackView:0x144216a80 )>",
    "<NSLayoutConstraint:0x600001ee8230 'UIView-bottomMargin-guide-constraint' V:[UILayoutGuide:0x6000004bc9a0'UIViewLayoutMarginsGuide']-(11)-|   (active, names: '|':_UIButtonBarButton:0x143723c40 )>",
    "<NSLayoutConstraint:0x600001e8f0c0 'UIView-topMargin-guide-constraint' V:|-(0)-[UILayoutGuide:0x6000004b48c0'UIViewLayoutMarginsGuide']   (active, names: '|':_UIButtonBarStackView:0x144216a80 )>"
)

Will attempt to recover by breaking constraint
<NSLayoutConstraint:0x600001eecf00 UIImageView:0x14372ae80.centerY == _UIModernBarButton:0x14372ab50.centerY   (active)>

Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger.
The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKitCore/UIView.h> may also be helpful.
2023-02-21 22:55:11.237023+0100 the-party[48476:1065166] [LayoutConstraints] Unable to simultaneously satisfy constraints.
	Probably at least one of the constraints in the following list is one you don't want.
	Try this:
		(1) look at each constraint and try to figure out which you don't expect;
		(2) find the code that added the unwanted constraint or constraints and fix it.
	(Note: If you're seeing NSAutoresizingMaskLayoutConstraints that you don't understand, refer to the documentation for the UIView property translatesAutoresizingMaskIntoConstraints)
(
    "<NSAutoresizingMaskLayoutConstraint:0x600001ee9950 h=--& v=--& _UIToolbarContentView:0x144214350.height == 0   (active)>",
    "<NSLayoutConstraint:0x600001e8f2a0 V:|-(0)-[_UIButtonBarStackView:0x144216a80]   (active, names: '|':_UIToolbarContentView:0x144214350 )>",
    "<NSLayoutConstraint:0x600001e8f2f0 _UIButtonBarStackView:0x144216a80.bottom == _UIToolbarContentView:0x144214350.bottom   (active)>",
    "<NSLayoutConstraint:0x600001ef0280 UIButtonLabel:0x14372e1d0.centerY == _UIModernBarButton:0x14372c2d0'Done'.centerY + 1.5   (active)>",
    "<NSLayoutConstraint:0x600001ee89b0 'TB_Baseline_Baseline' _UIModernBarButton:0x14372c2d0'Done'.lastBaseline == UILayoutGuide:0x6000004bc8c0'UIViewLayoutMarginsGuide'.bottom   (active)>",
    "<NSLayoutConstraint:0x600001ee8a00 'TB_Top_Top' V:|-(>=0)-[_UIModernBarButton:0x14372c2d0'Done']   (active, names: '|':_UIButtonBarButton:0x14372b370 )>",
    "<NSLayoutConstraint:0x600001ee8b40 'UIButtonBar.maximumAlignmentSize' _UIButtonBarButton:0x14372b370.height == UILayoutGuide:0x6000004b48c0'UIViewLayoutMarginsGuide'.height   (active)>",
    "<NSLayoutConstraint:0x600001e8f160 'UIView-bottomMargin-guide-constraint' V:[UILayoutGuide:0x6000004b48c0'UIViewLayoutMarginsGuide']-(0)-|   (active, names: '|':_UIButtonBarStackView:0x144216a80 )>",
    "<NSLayoutConstraint:0x600001ee8910 'UIView-bottomMargin-guide-constraint' V:[UILayoutGuide:0x6000004bc8c0'UIViewLayoutMarginsGuide']-(11)-|   (active, names: '|':_UIButtonBarButton:0x14372b370 )>",
    "<NSLayoutConstraint:0x600001e8f0c0 'UIView-topMargin-guide-constraint' V:|-(0)-[UILayoutGuide:0x6000004b48c0'UIViewLayoutMarginsGuide']   (active, names: '|':_UIButtonBarStackView:0x144216a80 )>"
)

Will attempt to recover by breaking constraint
<NSLayoutConstraint:0x600001ef0280 UIButtonLabel:0x14372e1d0.centerY == _UIModernBarButton:0x14372c2d0'Done'.centerY + 1.5   (active)>

Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger.
The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKitCore/UIView.h> may also be helpful.

Those are all warnings from Auto Layout. I see similar output when the keyboard is shown/hidden when on a web view. Sometimes with Turbo Native, sometimes not.
Is the app actually crashing? Because from this output it shouldn't be. Unless I missed something in the logs you provided.

Thx @joemasilotti  for looking into this.
 I see that this is not crashing the app nor blocking the requests. With the quickly scaffolded app, I see that this works and post requests are coming in.
Ok, so that is not the issue then.  However, my app is not sending a post requests, it works via browser but not via iOS.
This is some other issue then and its not related to this one.
Closing this.


Update manual demo instructions to ensure compatibility between osm cli and osm-controller

**Please describe what should be documented
The current version of the manual demo doc suggests to build osm cli from source, and use osm install to install the control plane. This however can lead to potential incompatibility issues since the CLI is built from source, while by default osm install command uses an image from a prior release.
To ensure compatibility, the instructions should be updated to use osm install --osm-image-tag <commit-from-which-cli-is-built>
This is to avoid an issue seen in #1491.
**Please suggest where in the repo the document should be located
https://github.com/openservicemesh/osm/blob/main/docs/installation_guide.md

@michelleN  can we prioritize this, more folks keep running into this issue because our docs are not updated.


Ship skills do not work with stolen/bought ships

Targeting Control Systems, Payloads, and Shield Systems do not work with all purchased or commandeered ships, regardless of ship reactor class or any other trait. It seems like the other ship skills (weapon skills) are not working on affected ships either, but have been unable to verify.
Ships that are given to the player, like the Frontier, the Starborn Guardian, Razorleaf, etc. never seem to be affected by this bug.

Game Version
<IP_ADDRESS> + SCP 0.0.2
Language
English (EN)
New Game
Yes
Reproduction Steps
Steal or buy ships until the bug is observed. Exact set of conditions unknown.

Issue should be titled "Ship skills do not work with ALL stolen/bought ships".

Caught this occurring after boarding and commandeering another ship. The ship I was originally on seems to have taken the shield strength of the ship which was boarded, which is substantially less than even the base amount provided by its module.


[BUG]  swagger-typescript generator adds multiple identical import statements if more than one attribute has same ref type

Describe the bug
When an object in the swagger.json file has two attributes with the same ref attribute, the generator adds two identical import statements, resulting in code that doesn't compile.
To Reproduce

Make a controller in a web api project return the following DTO

public class WeatherForecast
{
    public int TemperatureC { get; set; }

    public string? Summary { get; set; }

    public Person Reporter { get; set; }

    public Person SoundEngineer { get; set; }
}

public class Person
{
    public string name { get; set; }
}

Build, then run the swagger generator and then the typescript swagger generator
It should return this non-compiling typescript interface

import { Person } from './person';
import { Person } from './person';

export interface WeatherForecast {
  temperatureC: number;
  summary?: string;
  reporter?: Person;
  soundEngineer?: Person;
}

Expected behavior
Only one import statement for Person should be generated
Environment:

OS: Debian linux on WSL2

Already found and fixed the bug, but don't know how to push it in

+1 - need this fix

Hey! Thanks for the report and recommended fix, I'm going to clean it up a tad bit and then push a PR containing it.
As a side note, I had not been able to test the swagger typescript generator on more complex use cases. Have you all had any other issues?

Thank you very much!
There are two issues we've run into:

Frontend would like to have the possibility to have the index.ts file in a custom location, via options.
Date attributes are generated as strings, but should be generated as Date. A fix for that is here:

diff --git a/packages/core/src/generators/swagger-typescript/build-typescript-representation/parse-schema-object.ts b/packages/core/src/generators/swagger-typescript/build-typescript-representation/parse-schema-object.ts
index dfb4e17..9cca568 100644
--- a/packages/core/src/generators/swagger-typescript/build-typescript-representation/parse-schema-object.ts
+++ b/packages/core/src/generators/swagger-typescript/build-typescript-representation/parse-schema-object.ts
@@ -49,15 +49,27 @@ export function parsePropertyDefintion(
     typeof propertyDefinition.type === 'string' &&
     propertyDefinition.type in builtInTypeMap
   ) {
-    return {
-      type: builtInTypeMap[
-        propertyDefinition.type as keyof typeof builtInTypeMap
-      ],
-      nullable:
-        'nullable' in propertyDefinition
-          ? !!propertyDefinition.nullable
-          : false,
-    };
+    if (
+      propertyDefinition.format === 'date' ||
+      propertyDefinition.format === 'date-time'
+    ) {
+      return {
+        type: 'Date',
+        nullable:
+          'nullable' in propertyDefinition
+            ? !!propertyDefinition.nullable
+            : false,
+      };
+    } else
+      return {
+        type: builtInTypeMap[
+          propertyDefinition.type as keyof typeof builtInTypeMap
+        ],
+        nullable:
+          'nullable' in propertyDefinition
+            ? !!propertyDefinition.nullable
+            : false,
+      };
   } else if (propertyDefinition.type === 'object') {
     return {
       type: 'object',
diff --git a/packages/core/src/generators/swagger-typescript/constants/swagger-ts-type-map.ts b/packages/core/src/generators/swagger-typescript/constants/swagger-ts-type-map.ts
index 3a3afb8..c036396 100644
--- a/packages/core/src/generators/swagger-typescript/constants/swagger-ts-type-map.ts
+++ b/packages/core/src/generators/swagger-typescript/constants/swagger-ts-type-map.ts
@@ -3,6 +3,7 @@ export const builtInTypeMap = {
   integer: 'number',
   string: 'string',
   boolean: 'boolean',
+  date: 'Date',
 };

@Ossur the choice to have Date / DateTime elements reflected as strings in the generated typescript was purposeful, as that is how the front end apps would receive the data unless you are doing some kind of special parsing. See https://stackoverflow.com/questions/69933406/proper-way-to-pass-date-objects-between-a-javascript-typescript-frontend-and-a-a
One company that I worked at patched JSON.parse to detect string properties which looked like a date and autoconvert them, but that's nonstandard so its not something that I'd want to type for by default. I'll do some thinking on this, perhaps we could make it an option.


Upgrade bitcoin

Upgrade bitcoin to use the recently released v0.31.0-rc1.
Done while trying to upgrade bdk.

needs https://github.com/bitcoindevkit/rust-electrum-client/pull/121to move forward

PR has merged but we need a release to push on with this one.

PR has merged but we need a release to push on with this one.

new electrum-client 0.19 is ready to go: https://crates.io/crates/electrum-client/0.19.0

Sorry @RCasatta, you'll have to review a bit carefully please because only half my brain is switched on right now.

ACK 72238d6bea146dbd88a10a5ab7bb696bd7e46feb

https://crates.io/crates/electrsd/0.27.0 released


[modloading-worker-12/ERROR]

[modloading-worker-12/ERROR]: A mod has attempted to access enchantment information before Apotheosis init, this should not happen.
Expected Behaviour
There should be no errors from your mod when all I did was create a new world and enter it.
Environment

Minecraft: 1.15.2
Forge version: 31.2.36
Apotheosis version: 3.2.4
Placebo: 3.1.0
Modpack: Here

Latest log Here
Highlighted Log Section Here
Steps to reproduce

Select Play in Twitch App
Select Play in Minecraft Launcher
Create a new world
Enter world
Exit Minecraft

This is a bug in whatever mod adds this class at com.stereowalker.combat.event.AbominationEvents.<clinit>(AbominationEvents, as they are attempting to access enchantments before they are registered.
You'll have to take it up with them.


Add nxtools to overview.md

adding nxtools opensource documentation

@jodi-boone for visibility

@timwarner-msft
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Upgrade to pnpm v8

It appears our Netlify builds are failing due to pnpm version mismatch. This PR upgrades our version to the latest (v8) to fix them.

Note - compressed-size action will fail cuz it checks out the previous main branch which has the old lockfile and isn't compatible with the new lock file

Merged it as it fixes our workflows for other PR's


@async behavior

using LibSerialPort

list_ports()
ports = get_port_list()

sp = LibSerialPort.open(ports[1], 115200)
set_flow_control(sp)
sp_flush(sp, SP_BUF_BOTH)

@async while isopen(sp)
    while bytesavailable(sp) > 0
        data = readline(sp)
        println(stdout,  "read :$data")
    end
end

I don't know why this blocked REPL. How can I keep receiving while running other codes.

LibSerialPort.jl does not currently support asynchronous I/O in the way in which Julia uses libuv for other types of I/O to enable multi-tasking within a single thread. LibSerialPort.jl calls the blocking C functions of libserialport and these will block the entire task.
By default,  Julia starts up with a single thread of execution, and if libserialport blocks that thread, there is no thread left to run the REPL. Therefore you'd need at least two threads to be able to use a blocking function in libserialport and the REPL concurrently. LibSerialPort.jl is not currently using @threadcall, and neither is it trying to take care of thread safety (#69).

I have wondered whether libserialports is the right vehicle to implement proper multi-threaded serial-port communication for Julia, or whether this shouldn't be done instead on top of libuv, like all ther other file IO. (After all, the operating systems present serial ports as just special files with some additional settings.)

Any update on these thoughts?


Should focus return to top variant when data is loaded?

Open the demo data and click on a gene before analysis is complete. As soon as analysis completes, focus returns to RAI1, which is annoying if you were wanting to look at the gene you selected.

I'm not sure about this.  If you select a variant in a different gene, the focus won't be returned to the first flagged variant.  I think the point of the focus returning to the first selected variant, is to take users directly to the variant card for the 'most important' variant.  I think the autoselecting a variant is good for new users, but might be bad for regular users.  I could also add in a dialog prompt asking users if they want to jump to the highest prioritized variant once the data has finished loading.  @AlistairNWard @mvelinder @tonydisera Anyone have any thoughts on this?

I don't think we should add a dialog. We want to avoid forcing users to have to click too many things.
My opinion is that a new user would probably wait till things are loaded and then they'd be taken to the top variant. Even if you've selected something else, the variant list order should be enough to make it clear what we think is important.
As a returning user, I might be opening up an analysis to quickly check on a variant, or a particular gene. So as soon as gene opens, I'll select the gene I want to look at. That gene comes up, and then I'm suddenly whisked away to another gene and have to go back to reselect what I want.
So, my preference would be that if you selected something you stay with it. If nothing is selected, we take you to the top variant. We don't want to forcing behaviour on the user. Also, if we decided that we would force you to start at the top variant, we should disable the ability to select things while loading since that just introduces confusion (but I don't think we should do that).

@AlistairNWard Sounds good, ill do it that way


infra: Add Codecov badge

Issue #, if available:
Description of changes:
Testing done:
Merge Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.
General

[ ] I have read the CONTRIBUTING doc
[ ] I used the commit message format described in CONTRIBUTING
[ ] I have updated any necessary documentation, including READMEs and API docs (if appropriate)

Tests

[ ] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[ ] I have checked that my tests are not configured for a specific region or account (if appropriate)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #75 (586d899) into main (ee133b1) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #75   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           44        44
  Lines          624       621    -3
  Branches         4         4
=========================================
- Hits           624       621    -3

Impacted Files
Coverage Δ

src/braket/ir/jaqcd/program_v1.py
100.00% <0.00%> (ø)

src/braket/schema_common/schema_base.py
100.00% <0.00%> (ø)

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 ee133b1...586d899. Read the comment docs.

Codecov Report

Merging #75 (586d899) into main (ee133b1) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #75   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           44        44
  Lines          624       621    -3
  Branches         4         4
=========================================
- Hits           624       621    -3

Impacted Files
Coverage Δ

src/braket/ir/jaqcd/program_v1.py
100.00% <0.00%> (ø)

src/braket/schema_common/schema_base.py
100.00% <0.00%> (ø)

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 ee133b1...586d899. Read the comment docs.

Looks good. Would we be adding the coverage thresholds in a separate PR or is a default configuration already being applied here ?

Default threshold is 0 and it's already being applied; I think this is reasonable unless we find out down the line that it's too strict. I won't merge yet; I still need to figure out why the status checks aren't appearing.


[BUG] max line width breaks ampscript code in assets

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
saw it happening with contentblockbyname which tends to have a very longer argument.
Expected Behavior
ampscript code does not get auto-line breaks applied
Steps To Reproduce

Go to '...'
Click on '....'
Run '...'
See error...

Version
6.0.2
Environment

OS:
Node:
npm:

Participation

[X] I am willing to submit a pull request for this issue.

Additional comments
No response

could be fixed by changing .vscode/settings.json:
    "files.associations": {
        "*.html": "AMPscript"
    },
    "[html]": {
        "editor.defaultFormatter": "FiB.beautyAmp"
    },

that way, we no longer apply prettier settings but instead run beautyAmp on the code. tested this myself already and it seems to work

tracked in https://github.com/FiB3/beautyAmpCore2/issues/4


Cache::flush() with Redis Driver is not working

when using Redis as cache driver
Cache::flush not working ,  it don't do anything.
you can reproduce this bug easily, use this command , and check redis-cli -> Keys *

I can't reproduce this.


Add optional links to JSONAPI response

This is helpful for async relationships that are driven by links in the
response, instead of relationship IDs.
JSONAPI Links spec: http://jsonapi.org/format/#document-links
Usage:
import ApplicationSerializer from './application';

export default ApplicationSerializer.extend({
  links: {
    comments: {
      related: function(model) { return `/api/comments?post_id=${model.id}`; },
      self: function(model) { return `/api/posts/${model.id}/comments`; }
   }
});

Not sure what the issue is with Travis, seems unrelated...

Looks like a jshint error?
https://travis-ci.org/samselikoff/ember-cli-mirage/jobs/113739101#L398

I fixed the jshint error (not sure why it didn't show locally). All tests are now passing, it's failing on:
1) import files includes third party libraries in development environment by default:
     AssertionError: expected [] to be a superset of [ Array(4) ]
      at Context.<anonymous> (tests/unit/import-files-test-node.js:30:52)
  2) import files includes third party libraries in test environment by default:
     AssertionError: expected [] to be a superset of [ Array(4) ]
      at Context.<anonymous> (tests/unit/import-files-test-node.js:30:52)
  3) import files includes third party libraries in production when enabled is set to true:
     AssertionError: expected [] to be a superset of [ Array(4) ]
      at Context.<anonymous> (tests/unit/import-files-test-node.js:42:50)

Don't think this has anything to do with the PR...

I noticed that there seems to be a Vim swap file included in the PR (addon/serializers/.json-api-serializer.js.swp). Not sure if that's also causing the test failure. Easy to miss because since it's a binary file github collapses it.

@RSSchermer thanks, good catch! I removed the swap file but looks like it's still failing for the same reason (though all tests pass).

You're correct, it is unrelated. I tried working on it earlier here but haven't gotten anywhere yet.

In the meantime I think landing this API will be great. Could we change the API a bit? I think I'd prefer this:
export default ApplicationSerializer.extend({

  links(model) {
    return {
      comments: {
        related: `/api/comments?post_id=${model.id}`,
        self: `/api/posts/${model.id}/comments`
      }
    }
  }

}

Only one function declaration, and if users need some space to do some munging they already have it, plus we could pass in the request + they could access the this context if they ever need to. What do you think?

:+1: great suggestion. Will get to it this week.

@samselikoff force-pushed change to the API as requested. All tests passing, just the unrelated Mocha issue left.

Also added code to remove data from the relationships payload when links are present. If both nodes are present, looks like ember-data will treat the response as if links did not exist.

sweet! Could you squash these, and I'll merge them in? Thank you for this!

Squashed - thanks! :+1:

:confused: travis magically started working again... oh well, sounds good to me!
Thanks for this!


WIP: Add nixos/nix-darwin module

Initial implementation

Will test, refactor and document in subsequent PRs.


[Proposal] [Validator] [5.1] 'at_least:foo,bar' rule

Sometimes we have a form that does not contain any required fields. For example, an 'edit your account' form.
So, you write validation rules to validate input formats for its optional fields. However, a user can send the form without filling any field. Your validation rules will pass, because no field has the 'required' attribute.
I just had this situation here, and I could (and should) write a custom validation rule. However, it seemed too cumbersome for something simple that should be a one liner. So, I ended up using:
'empty_hidden_field' => 'size:0|required_without_all:field_a,field_b,....,field_N'

...and edited the 'required_without_all' message to be "You need to fill at least one field". It works like a charm, but it's definitely not the right way to do it.
It would be cool if the framework had a built-in validation rule for this not-too-specific case.
It could be something like: 'at_least:foo,bar' or 'at_least:any'

We don't process proposal issues. Issues are only here for the community to share and fix.

So why are there issues tagged by you as "Proposal"?
Where should I post them? Just do a PR and that's all? Is there any place to talk about it before pushing?


help identifying sensors

I have managed to integrate my sofar 5ktlm-g3 inverter in HA, but I need help to identify which is the export to the network and the consumption that I have, I would also appreciate help to create the virtual sensors to be able to configure my energy panel.

It's bit confusing w/ this profile but when comes to power sensors:

ActivePower_PCC_Total is Grid Power
ActivePower_Load_Sys is Load Power

And energy ones are straight forward I think.


Docs: Mozilla Hubs component support

We support https://github.com/MozillaReality/hubs-blender-exporter#using-lightmaps, animations, and the uv animation Hubs component.
This should be documented/linked in the docs.

Related: https://github.com/webaverse/app/issues/627

Related: https://github.com/webaverse/app/issues/627

added here: https://docs.webaverse.com/docs/webaverse/worlds#blender
will add a before/after screenshot when upgrading to v2 https://github.com/webaverse/app/issues/1308


YouTube: Output URLs in "url" field, not IDs

-j --flat-playlist was outputting the video ID instead of the video URL in the "url" element of the JSON.  Now it outputs, e.g.
{"url": "https://youtu.be/uhKejRHODOM", "_type": "url", "ie_key": "Youtube", "id": "uhKejRHODOM", "title": "The Overly Complicated Coffee Order"}

Outputting video ids instead of whole URL is expected for YouTube.


Disable gRPC communication by default

Related to: https://github.com/giantswarm/giantswarm/issues/494
This PR aims to keep the default fleet implementation and use only our GRPC code whenever enable_grpc is true. This means that our registrymux is not working as before, thereby two different fleet versions (etcd and grpc) cannot leave together.
Implementation wise, I used the flag in few places and relocated our grpc code in a different directory to help the reader differ our new implementation from the current one.
To sum up:
enable_grpc: false == Old way of working or in other words only etcd
enable_grpc: true == Use GRPC registry (registrymux). I keep registrymux even if we aren't willing at this moment to be able to have two diff implementations, in order to merge our upstream PR asap.
ping @htr @teemow

lgtm, WFM will follow soon

WFM


Guardian service share a common set of Environment variables

Problem description
The presence of different set of environment variables defined in different file spread all through the guardian services may cause inconsistency and wrong behaviour of the system. All Microservice should share a common set of Environment variables. It has to be provide a unique file to hold all the valid environment variable at system level and a way to define specific service variables. This different set of variables will allow to have a hierarchical definition of the same variables at service level in a way that a developer could redefine some variable in a service specific way. In advance the .env.template.guardian.system file has to be defined to let the developer know the minimum set of necessary variables to be defined in the environment.
Definition of done
The set of variables which is valid all through the system is defined in the file .env.template.guardian.system.
All variables are moved from .env service specific files into .env.<ENV>.guardian.system file. In every single service it is defined a way to describe a set of variables for the specific service. Each service is able to load both the sets of variables: the Guardian system variables and service specific variables and eventually override some of the system variable.
Acceptance criteria
The proper configurations associated with an environment must be selected automatically by just setting the ENV variable in the common .env file. The configurations must be all stored as different files instead of .env files per service.

Current  environment definition:

We are going to implement an environment set defined at root project level that will constitute the base environment for a hierarchical environment defined at each service level. Every of the environment will have his own Environment Ecosystem Name which will be used discriminate which environment is going to spread the session.


Don't panic but return error from NewAccountClient

Changes
TSIA
Tests

[x] make test passing
[x] make fmt applied
[ ] relevant integration tests applied

Codecov Report
Patch and project coverage have no change.

Comparison is base (1504930) 19.29% compared to head (9c57978) 19.29%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #422   +/-   ##
=======================================
  Coverage   19.29%   19.29%
=======================================
  Files          82       82
  Lines        8792     8792
=======================================
  Hits         1696     1696
  Misses       6950     6950
  Partials      146      146

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Feat support win64 (vcpkg+CMake) for rocksdb

YCSB-cpp can now be built on windows, using vcpkg and CMake.
See README.md for usage.

The PR is not intended to merge into this repo. Sorry for the missing. I'll close the PR.

Looks great. :)

Looks great. :)

Thanks.
There's a strange problem. I've just tested with recordcount=100M and threadcount=8 on windows, the StatusThread may randomly exit early(done=true), even though all ClientThreads are still running (the latch->count_ is still 8). The exiting timing varies, maybe at 9s, 30s or several minutes. The ClientThreads will keep running to the end normally.
Yes, I observed 9 sec while the interval is set to 10s. I've not encountered this situation on Linux before, which makes me doubt the precision and resolution of std::chrono on windows.
I tried this change:
// countdown_latch.h:26
return cv_.wait_for(lock, std::chrono::seconds(timeout_sec), [this]{return count_ <= 0;});
// return cv_.wait_for(lock, std::chrono::seconds(timeout_sec)) == std::cv_status::no_timeout;

I run the test another 5 times and the problem didn't appear. I cannot explain why.
Is this a coincide? Am I missing something?

CV is notified only when all ClientThread are terminated, so I think StatusThread should not wake up for reason other than timeout. Still, it might be safe to check the count after wake up.

CV is notified only when all ClientThread are terminated, so I think StatusThread should not wake up for reason other than timeout. Still, it might be safe to check the count after wake up.

You're right. We need to check the count on windows.
After a boring search, I found the reason:
https://devblogs.microsoft.com/oldnewthing/20180201-00/?p=97946
and from cplusplus/wait_for :

Generally, the function is notified to wake up by a call in another thread either to member notify_one or to member notify_all. But certain implementations may produce spurious wake-up calls without any of these functions being called. Therefore, users of this function shall ensure their condition for resumption is met.
If pred is specified (2), the function only blocks if pred returns false, and notifications can only unblock the thread when it becomes true (which is especially useful to check against spurious wake-up calls).

Thanks! I didn't know that since I've never tested it in a Windows environment. I'll fix it soon, or please feel free to submit PR.

Thanks! I didn't know that since I've never tested it in a Windows environment. I'll fix it soon, or please feel free to submit PR.

OK. I've run heavy tests(1G record count and 100M opcount) with rocksdb on windows all day today. It seems there's no problem.
I plan to add support for wiredtiger on windows, along with lmdb and leveldb, before making a PR to this repo.


Unable to run Homebridge on Bootup Raspberry Pi

I followed the instruction [https://github.com/nfarina/homebridge/wiki/Running-HomeBridge-on-a-Raspberry-Pi] to set up auto start on boot.
When I type sudo /etc/init.d/homebridge start, it just doesn't do anything

If it's a bash script you should run it with ./ so it becomes
sudo /etc/init.d/./homebridge start
And don't forget to make it executable with
chmod a+x homebridge

Still does not work for me. The only way to start is homebridge from anywhere, but I want it to start on boot

Probably your init script is incomplete. See “Running Homebridge on Bootup“ in the wiki (https://github.com/nfarina/homebridge/wiki/Running-HomeBridge-on-a-Raspberry-Pi#running-homebridge-on-bootup).
Use the init script template or raw template file AND then modify the top of the file as mentioned in the wiki.
Here is mine:
—
#!/bin/sh
BEGIN INIT INFO
Provides: homebridge
Required-Start:    $network $remote_fs $syslog
Required-Stop:     $remote_fs $syslog
Default-Start:     2 3 4 5
Default-Stop:      0 1 6
Short-Description: Start daemon at boot time
Description:       Enable service provided by daemon.
END INIT INFO
dir="/home/pi"
cmd="DEBUG=* /usr/local/bin/homebridge"
user="pi"
name=basename $0
pid_file="/var/run/$name.pid"
stdout_log="/var/log/$name.log"
stderr_log="/var/log/$name.err"
get_pid() {
cat "$pid_file"
}
is_running() {
[ -f "$pid_file" ] && ps get_pid > /dev/null 2>&1
}
case "$1" in
start)
if is_running; then
echo "Already started"
else
echo "Starting $name"
cd "$dir"
if [ -z "$user" ]; then
sudo $cmd >> "$stdout_log" 2>> "$stderr_log" &
else
sudo -u "$user" $cmd >> "$stdout_log" 2>> "$stderr_log" &
fi
echo $! > "$pid_file"
if ! is_running; then
echo "Unable to start, see $stdout_log and $stderr_log"
exit 1
fi
fi
;;
stop)
if is_running; then
echo -n "Stopping $name.."
kill get_pid
for i in {1..10}
do
if ! is_running; then
break
fi
        echo -n "."
        sleep 1
    done
    echo

    if is_running; then
        echo "Not stopped; may still be shutting down or shutdown may have failed"
        exit 1
    else
        echo "Stopped"
        if [ -f "$pid_file" ]; then
            rm "$pid_file"
        fi
    fi
else
    echo "Not running"
fi
;;
restart)
$0 stop
if is_running; then
echo "Unable to stop, will not attempt to start"
    exit 1
fi
$0 start
;;
status)
if is_running; then
    echo "Running"
else
    echo "Stopped"
    exit 1
fi
;;
*)
echo "Usage: $0 {start|stop|restart|status}"
exit 1
;;

esac
exit 0
—
https://github.com/nfarina/homebridge/wiki/Running-HomeBridge-on-a-Raspberry-Pi#running-homebridge-on-bootup

Am 23.12.2015 um 18:13 schrieb Lam Nguyen<EMAIL_ADDRESS>Still does not work for me. The only way to start is homebridge from anywhere, but I want it to start on boot
—
Reply to this email directly or view it on GitHub https://github.com/nfarina/homebridge/issues/435#issuecomment-166947162.

Thanks, works good

For some reason when I reformatted the drive and restore from backup, it won't start on boot anymore, error and log showed these:
pi@raspberrypi-2:~ $ tail -f /var/log/homebridge.log
Registering platform 'homebridge-legacy-plugins.TelldusLive'
Registering platform 'homebridge-legacy-plugins.ZWayServer'
---
Loaded config.json with 0 accessories and 1 platforms.
---
Loading 1 platforms...
[SmartThings] Initializing SmartThings platform...
Loading legacy platform SmartThings
[SmartThings] Fetching SmartThings devices...
[SmartThings] There was a problem authenticating with SmartThings.

pi@raspberrypi-2:~ $ tail -f /var/log/homebridge.err
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node>
*** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?    s=libdns_sd&e=node&f=DNSServiceRegister>
*** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node>
*** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister>

It starts fine if I run sudo /etc/init.d/homebridge start
No idea what happened

anyone has same issue?

anyone has same issue?

Personally, I prefer to run Homebridge with forever.
Here's my script in /etc/init.d/homebridge
#!/bin/sh

case "$1" in
    start)
        su - pi -c "forever start  --spinSleepTime 5000 --sourceDir=/usr/local/bin homebridge"
        ;;
    stop)
        su - pi -c "forever stopall"
        forever stopall
        ;;
    restart)
        su - pi -c "forever restartall"
        forever restartall
        ;;
    status)
        su - pi -c "forever list"
        forever list
        ;;
esac

exit 0

issue #383

I actually found out this error cause homebridge fails to start on boot. Like I said, It works when I start from /etc/init.d/homebridge start|stop|status
https://github.com/nfarina/homebridge/issues/460

Have you run sudo update-rc.d /etc/init.d/....

I did

I had a similar issue and found my disk space was 0.  Once I freed up space I had to reboot and it auto-launched

Here is my guide in setting up Homebridge on Raspberry Pi to start on boot up and restart on errors. Hope it help!
https://timleland.com/setup-homebridge-to-start-on-bootup/

@timleland I am using the same setup for auto start and it works well.  I notice you use RFswitches as well.  Are you controlling them from homebridge?  If so what plugin are you using?  I have run into problems using any plugin that requires wiringpi and using the systemd auto start method.  I assume its permissions issue where wiring pi is not being run as root.  Any advice on how to get that working?

@frodeaux If you follow my guide on setting up the rf outlets, you can call the codesend program directly from homebridge using cmdswitch2.

Just a quick tip, on latest Node, Homebridge is not located on /usr/local/lib but in /usr/lib. Just change the line cmd="DEBUG=* /usr/local/bin/homebridge" into cmd="DEBUG=* /usr/bin/homebridge" and it works like a charm

@timleland Thanks for your step-by-step guide, worked perfectly (I also had to remove 'local' from one of the steps.
You've provided far better instructions than in the Wiki, perfect for people like myself you a new to coding etc but want to leverage the benefits of Homebridge.
Thanks!

@MrNPP thanks! Glad it helped.

Just a quick tip, on latest Node, Homebridge is not located on /usr/local/lib but in /usr/lib. Just change the line cmd="DEBUG=* /usr/local/bin/homebridge" into cmd="DEBUG=* /usr/bin/homebridge" and it works like a charm

@Maikeximu - that actually help! Thanks!

Hey, I am new with almost no experiance and my english is bad. Do not know if I am in the right topic?
My RBPi 3 is running stretch. I can not get homebridge to run.
this is what I get. Can someone help please.
pi@raspberrypi:~ $ sudo systemctl status homebridge.service -l
● homebridge.service - HomeBridge Service
Loaded: loaded (/lib/systemd/system/homebridge.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2018-02-17 12:14:01 CET; 8min ago
Main PID: 25566 (code=exited, status=1/FAILURE)
feb 17 12:13:59 raspberrypi node[25566]: *** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=node
feb 17 12:13:59 raspberrypi node[25566]: *** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supp
feb 17 12:13:59 raspberrypi node[25566]: *** WARNING *** Please fix your application to use the native API of Avahi!
feb 17 12:13:59 raspberrypi node[25566]: *** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSSer
feb 17 12:14:01 raspberrypi homebridge[25566]: [2018-2-17 12:14:01] Loaded plugin: homebridge-gpio-relay
feb 17 12:14:01 raspberrypi homebridge[25566]: [2018-2-17 12:14:01] Registering accessory 'homebridge-gpio-relay.relay'
feb 17 12:14:01 raspberrypi homebridge[25566]: [2018-2-17 12:14:01] ---
feb 17 12:14:01 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=1/FAILURE
feb 17 12:14:01 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
feb 17 12:14:01 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
lines 1-15/15 (END)

Personally, I prefer to run Homebridge with forever.

Here's my script in /etc/init.d/homebridge
#!/bin/sh
case "$1" in
start)
su - pi -c "forever start  --spinSleepTime 5000 --sourceDir=/usr/local/bin homebridge"
;;
stop)
su - pi -c "forever stopall"
forever stopall
;;
restart)
su - pi -c "forever restartall"
forever restartall
;;
status)
su - pi -c "forever list"
forever list
;;
esac
exit 0

@devbobo  How can you check the status if logged in via SSH using this script on bootup?


Fix temp vars referenced in parameter

As of ES2015 it is illegal for the evaluation of one parameter to reference another parameter or a variable declared in the body of the function. As a result, any time we introduce a temporary variable when we emit a parameter with an initializer or binding pattern when targeting ES2015 or later we must move the evaluation to the body of the function.
This also adds a heuristic to the checker to ensure the correct name resolution for cases where our emit moves the evaluation of the parameter to the body of the function, and thus report an error when a parameter refers to an identifier that is shadowed in the body of the function.
Fixes #36295

@DanielRosenwasser I'd like some feedback on the change to the error message. I'm considering simplifying it to the following:
Parameter '{0}' cannot reference identifier '{1}' declared after it.

/cc @weswigham, @andrewbranch for review as suggested reviewers isn't working.

I think that for initializer, the old message or
The initializer of parameter '{0}' cannot reference '{1}' because it is declared after '{0}'.

or
'{0}' cannot reference '{1}' because it is declared after '{0}'.

both work.
I think that in the case of the binding pattern, you should special case the message to be a variation of that so that we don't confuse people with "or binding pattern"

That message is somewhat redundant, isn't it? The initializer of parameter 'p' cannot reference 'x' because it is declared after 'p'.
The reason I like Parameter '{0}' cannot reference identifier '{1}' declared after it. is that it covers both cases without an extra message.

My suggestion would also be similar to the other existing related message: Parameter '{0}' cannot be referenced in its own initializer, though that also probably needs to be changed to something like: Parameter '{0}' cannot reference itself..

Regarding "cannot reference itself", the reason I might change that one as well is this:
function f({ [a]: a }) {}

Binding a references itself in its own name here, rather than its initializer.

Looking at the errors produced by parameterInitializersForwardReferencing.2.ts , this is a breaking change, isn’t it?
This currently compiles in 3.8.3 (and seems to work in every runtime I’ve tried), but looks like it’s an error in this PR?

Are you trying them in ES2015 or ES5?

Oh sorry. The error is introduced only when using syntax that introduces temporaries. Your example should continue to work fine, but if you do function f(p = a()?.b) {} then it should produce the error.

Ah ok, interesting. So this PR does issue an error where there wasn’t one before, but only in cases where runtime behavior was already broken because of a name/scope conflict introduced by downleveling. Is that right?

Correct. Its the same error we introduce for the same reason when the target is ES5, there are just now more cases that are accurately covered now.

@typescript-bot perf test

I do think if I happened to hit this error, I would have a really hard time understanding why TypeScript thinks that a was declared after the usage in the parameter default. I would definitely think I was witnessing a checker bug. I’m not sure how to concisely explain the problem, though. It seems like we want to nudge users to rename either the inner or the outer variable.

Right now I'm erring on the side of emulating the same behavior as what happens with the ES5 target. We might want to consider improving that messaging across the board, but I don't have an idea of a concise message for that either.

Maybe these?

Parameter '{0}' cannot reference itself.  - For cases that should be considered incorrect regardless of emit target.
Parameter '{0}' cannot reference identifier '{1}' declared after it. - For cases that should be considered incorrect regardless of emit target.
Parameter '{0}' cannot reference identifier '{1}' declared both inside and outside of the function where the parameter is defined due to the current emit target. - For cases due to downleveling.

/cc @DanielRosenwasser

Hmm. The third bullet point is a bit harder to determine while in the middle of resolveName. I think I'll just stick with the messages in the first two bullet points until we have a better idea for the third one.

@DanielRosenwasser should I merge this and discuss changing the messages later, or should I wait?

The messages seem fine overall

(If you feel like they could be better, I encourage you to follow up, but don't let it block merging this)


Mentoring

We would like to support new contributors with mentoring. This would probably need to be lead by the main contributors:
@sarabala1979 @alexec @terrytangyuan etc

Also happy to help here

Happy to help mentor new contributors. Some programs to consider unless we are organizing this ourselves:

https://github.com/cncf/mentoring
https://summerofcode.withgoogle.com/archive/

It seems we have some summer programs for newer programmers to learn to code. I wonder what our scope should be?
I was initially planning on a short term mentorship, i.e the mentor helps the mentee get started with coding, learning the code base, fixing and issue or implementing a feature, getting it reviewed and approved and merged.
Maybe there are other interpretations.

https://jisajournal.springeropen.com/articles/10.1186/s13174-021-00140-z

It seems we have some summer programs for newer programmers to learn to code. I wonder what our scope should be?
I was initially planning on a short term mentorship, i.e the mentor helps the mentee get started with coding, learning the code base, fixing and issue or implementing a feature, getting it reviewed and approved and merged.
Maybe there are other interpretations.

Yes that was exactly my point when asking on slack and I would love that!
But maybe there are other needs too?

It seems we have some summer programs for newer programmers to learn to code. I wonder what our scope should be?

Just to clarify. The students in those programs may not be new programmers. Although they maybe new to open source contributions. For Google Summer of Code (GSoC), for example, it's up to the project maintainers to decide whether to provide a few project ideas and then the students (applicants) will be drafting proposals either based on those ideas or their own ideas. Upon completion of project by the selected students, they will get paid. The mentorship lasts for one summer.

I was initially planning on a short term mentorship, i.e the mentor helps the mentee get started with coding, learning the code base, fixing and issue or implementing a feature, getting it reviewed and approved and merged.
Maybe there are other interpretations.

I just wanted to throw some ideas there but not necessarily a preference. What you mentioned here sounds great and requires less communication overhead. From my past experience with GSoC, there will be a lot of communication overhead to participate the program and select students but the benefit is that the project gets more public exposure and the quality of participants is high with commitment and incentive.

My opinion is very biased since I've done mentoring three times so it would be great to hear from others too.
Argo will first need to apply to be a mentor organization and wait until accepted. The timeline is still TBD: https://developers.google.com/open-source/gsoc/timeline.


Added Chinese language pack

Thanks for pull request. I have this included in the master branch, and the new dev branch (which is a complete refactoring of the code).


[FEATURE] align external_id usage with user stories

Is your feature request related to a problem? Please describe.
add_records(same_record) and add_records(same_record)  might lead to errors
methods like delete_records or filter_by record IDs aren't aligned with the different dataset types. Also, records might need to be updated based on external_id from another database.
Describe the solution you'd like

by default generating a UUID
allowing to overwrite existing external_id

Describe alternatives you've considered
N.A.
Additional context
N.A.

Whenever new information like user feedback is available, I would like to update the corresponding field of the record.
For example, user feedback is not available at the time of record creation but is immensely helpful for annotators. I have a metadata property to filter records with user feedback, so annotators could prioritise them.
Tried:

update_records API doesn't allow updating a particular record’s fields value
add_records API fails due to the UniqueConstraint record_external_id_dataset_id_uq


[BUG] Could not resolve "#node-web-compat"

Describe the bug
I'm facing another version of #66 in combination with yarn berry and esbuild.
Build fails with
X [ERROR] Could not resolve "#node-web-compat"

    .yarn/cache/aws-jwt-verify-npm-3.1.0-1694314cd9-b978817018.zip/node_modules/aws-jwt-verify/dist/esm/jwt-rsa.js:8:30:
      8 │ import { nodeWebCompat } from "#node-web-compat";
        ╵                               ~~~~~~~~~~~~~~~~~~

  You can mark the path "#node-web-compat" as external to exclude it from the bundle, which will
  remove this error.

Workaround is to use a different linker mode in yarn, e.g. pnpm
Versions
Which version of aws-jwt-verify are you using? ^3.1.0
Are you using the library in Node.js or in the Web browser? Node.js
If Node.js, which version of Node.js are you using? (Should be at least 14) 14
If Web browser, which web browser and which version of it are you using?
If using TypeScript, which version of TypeScript are you using? (Should be at least 4) ^4.8.3
To Reproduce
Reproducer can be found here.
Note: I'm not sure where to report this issue, could as well be in yarn or esbuild. I'm just starting here, hoping you can point me further.

Indeed a variant (or duplicate) of #66
aws-jwt-verify uses subpath imports which unfortunately has flaky support in various tools and libs (looking at you jest). Although esbuild has supported it since version 0.13.9 (see https://github.com/evanw/esbuild/issues/1691)
    "imports": {
        "#node-web-compat": {
            "browser": "./node-web-compat-web.js",
            "import": "./node-web-compat-node.js"
        }
    }

The culprit must be the specific interplay of yarn with esbuild, concerning subpath imports. My stack trace shows:
Error: Command failed: /private/tmp/yarn-berry-esbuild-aws-jwt-verify-reproducer/node_modules/.cache/esbuild/pnpapi-esbuild-darwin-64-0.15.7-esbuild --bundle ./src/index.ts --target=node14 --platform=node --outfile=./build/out.js --charset=utf8
    at checkExecSyncError (node:child_process:828:11)
    at Object.execFileSync (node:child_process:863:15)
    at Object.<anonymous> (/private/tmp/yarn-berry-esbuild-aws-jwt-verify-reproducer/.yarn/unplugged/esbuild-npm-0.15.7-9aee421406/node_modules/esbuild/bin/esbuild:183:28)
    at Module._compile (node:internal/modules/cjs/loader:1105:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
    at Object.require$$0.Module._extensions..js (/private/tmp/yarn-berry-esbuild-aws-jwt-verify-reproducer/.pnp.cjs:9008:33)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.require$$0.Module._load (/private/tmp/yarn-berry-esbuild-aws-jwt-verify-reproducer/.pnp.cjs:8848:14)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12) {
  status: 1,
  signal: null,
  output: [ null, null, null ],
  pid: 59761,
  stdout: null,
  stderr: null
}

I recommend to open an issue with esbuild.
We can keep this issue here open for now, but it will need convincing that this is an issue in our library.

reported to esbuild as https://github.com/evanw/esbuild/issues/2545, will keep you updated if it affects this package.

Found out it is a missing feature in yarn https://github.com/yarnpkg/berry/issues/3843. I'll close this as I expect it to work once that is implemented.

yarnpkg/berry#3843 was fixed yesterday. The fix is available in 4.0.0-rc.22. Run yarn set version canary if you want to try it. v4 release is still a little ways off ("may take a couple more months"), but:

[...] what's in master is stable, and I'd recommend you to try it. The only notable difference with stable is that we reserve the right to land a couple more breaking changes in future RCs, but in terms of stability it's almost always better to use RCs than stable.

... according to https://github.com/yarnpkg/berry/discussions/4895
See https://github.com/yarnpkg/berry/issues/3591 for v4 breaking changes. I've seen two mentions of people stumbling over enableGlobalCache default changing from false to true. (Google search: site:yarnpkg.com "enableGlobalCache")

Update: the fix that adds support for the package.json includes field is also in the Yarn 3.2.4 release.


[Vulkan] Can't use a noise texture as uniform texture sampler in shader

Godot version
v4.0.dev.calinou [de917008f]
System information
Linux Manjaro, Vulkan, Intel Kaby Lake
Issue description
Just for fun, I'm trying to write a sky shader for my racer game (it should give improved performance over 2d+viewport+panorama hack used in 3.x)
I discovered that while I can assign a .png noise texture off the net, I CAN NOT assign a NoiseTexture, be it from clicking the New NoiseTexture from the dropdown, or from quick open'ing a saved .tres.
(Possibly related, some other places are also wonky: I can't assign a texture in a mesh's slot, I have to use the override - both result in spewing a load of errors about uniforms not set. This also applies to trying to put a NoiseTexture as a night_sky texture of the PhysicalSky)
Steps to reproduce
See above
Minimal reproduction project
No response

Have you tried reloading the scene? This sounds related to #51361
I have found noise textures to be more annoying, triggering that issue more often than regular textures.

I tried save and reopen, it behaves as though no texture was set upon reopening.

For me it works if I save, then do [Menu] Scene -> Reload Saved Scene


mmlspark lightgbm performs poorly when dealing with unbalanced label dataset compared with native lightgbm

Hello,
I 'm testing some model with mmlspark lightgbm on databricks 10.0 ML(SPARK 3.2, Scala 2.12)
Installed mmlspark version is com.microsoft.ml.spark:mmlspark_2.12:1.0.0-rc3-43-54379bf7-SNAPSHOT
I'm using credit card fraud dataset from kaggle ( https://www.kaggle.com/mlg-ulb/creditcardfraud )
The dataset is heavily unbalanced in target label. Only less than 1 percent of the data is fraud and labeled as 1 and more than 99 percent is labeled as 0.
When I trained the dataset with native lightgbm packages, the performance was very good.
precision was 0.95, recall was 0.763 and roc-auc is 0.978
I only used a few hyperparameters(by the way when boost_from_average=True, the performance was poor on unbalanced dataset)
lgbm_clf = LGBMClassifier(n_estimators=1000, num_leaves=64, boost_from_average=False)
but when I use mmlspark lightgbm, model performance runs poorly.
lgbm_classifier = LightGBMClassifier(featuresCol="features", labelCol="Class"
, numIterations=1000
, boostFromAverage=False)
lgbm_model = lgbm_classifier.fit(train_over_sdf_vectorized)
lgbm_predictions = lgbm_model.transform(test_sdf_vectorized)
precision: 0.0009, recall: 0.0189, roc_auc: 0.4895
I've tested with various hyperparameter settings with hyperopt package for a couple of days. But the result was almost same.
I also tested with another unbalanced dataset such as kaggle's  santander dataset (https://www.kaggle.com/c/santander-customer-satisfaction)
the result was not that bad like credit card fraud dataset(the dataset is less unbalanced than credit card dataset)
However, when tested with native python lightgbm, it showed roc-auc 0.8448. But with mmlspark lightgbm it showed roc-auc 0.71
It seems like mmlspark lightgbm shows heavy performance degradation when dealing with heavily unbalanced dataset compared with native lightgbm.
If you have any recommendation to correct this, that would be big help to me
Best regards.

hi @chulminkw , can you please try:
1.) using very latest synapseml package, com.microsoft.ml.spark:mmlspark_2.12:1.0.0-rc3-43-54379bf7-SNAPSHOT is older than the new synapseml packages and still has the old mmlspark name
2.) setting parameters:
isUnbalance=True
useSingleDatasetMode=True
numThreads=(number of cores on machines)-1
This currently gives fastest performance and best accuracy in our benchmarking
Please let me know if you don't see any improvement.  I can also take a look and try to reproduce the issue.

Also another problem that might occur only in distributed case but not single node - if your minority class appears only in a single partition, the performance may be worse than if it is distributed across the partitions, so it may be good to ensure the data is stratified by class across all partitions.

Hello Ilya Matiach
Thanks for your reply.

The reason I didn't use the latest synapse ml named com.microsoft.azure:synapseml_2.12:0.9.4 was that it showed  an error in initiating LightGBMClassifier. I installed library for the coordinates use: com.microsoft.azure:synapseml_2.12:0.9.4
in databricks community edition with 10.0 ML  Apache Spark 3.2.0 and Scala 12

the error is "java.lang.NoSuchMethodError: spray.json.BasicFormats.$init$(Lspray/json/BasicFormats;)" when I do lgbm_classifier = LightGBMClassifier(featuresCol="features", labelCol="TARGET"
, numIterations=50
, boostFromAverage=False
)
following is the source code and the error messages
from pyspark.ml.feature import VectorAssembler
from pyspark.ml.tuning import CrossValidator, ParamGridBuilder
from pyspark.ml.evaluation import BinaryClassificationEvaluator, MulticlassClassificationEvaluator
from synapse.ml.lightgbm import LightGBMClassifier
vector_assembler = VectorAssembler(inputCols=santander_columns, outputCol="features")
lgbm_classifier = LightGBMClassifier(featuresCol="features", labelCol="TARGET"
, numIterations=50
, boostFromAverage=False
)
lgbm_param_grid = ParamGridBuilder().addGrid(lgbm_classifier.learningRate, [0.01, 0.1]).build()
roc_eval = BinaryClassificationEvaluator(labelCol='TARGET', metricName='areaUnderROC' )
lgbm_cv = CrossValidator(estimator=lgbm_classifier, evaluator=roc_eval, estimatorParamMaps=lgbm_param_grid, numFolds=3, seed=2021)
===============================================>
java.lang.NoSuchMethodError: spray.json.BasicFormats.$init$(Lspray/json/BasicFormats;)V
Py4JJavaError                             Traceback (most recent call last)
 in
9 vector_assembler = VectorAssembler(inputCols=santander_columns, outputCol="features")
10
---> 11 lgbm_classifier = LightGBMClassifier(featuresCol="features", labelCol="TARGET"
12                                      , numIterations=50
13                                      ,isUnbalance=True
/databricks/spark/python/pyspark/init.py in wrapper(self, *args, **kwargs)
112             raise TypeError("Method %s forces keyword arguments." % func.name)
113         self._input_kwargs = kwargs
--> 114         return func(self, **kwargs)
115     return wrapper
116
/local_disk0/spark-941f58d5-9ccf-4ca7-835c-77d57fc48fab/userFiles-0ad410fd-d119-4877-b572-cc282b56aa35/addedFile5753353993912334267synapseml_lightgbm_2_12_0_9_4-a075c.jar/synapse/ml/lightgbm/LightGBMClassifier.py in init(self, java_obj, baggingFraction, baggingFreq, baggingSeed, binSampleCount, boostFromAverage, boostingType, categoricalSlotIndexes, categoricalSlotNames, chunkSize, defaultListenPort, driverListenPort, dropRate, earlyStoppingRound, featureFraction, featuresCol, featuresShapCol, fobj, improvementTolerance, initScoreCol, isProvideTrainingMetric, isUnbalance, labelCol, lambdaL1, lambdaL2, leafPredictionCol, learningRate, matrixType, maxBin, maxBinByFeature, maxDeltaStep, maxDepth, maxDrop, metric, minDataInLeaf, minGainToSplit, minSumHessianInLeaf, modelString, negBaggingFraction, numBatches, numIterations, numLeaves, numTasks, numThreads, objective, parallelism, posBaggingFraction, predictionCol, probabilityCol, rawPredictionCol, repartitionByGroupingColumn, skipDrop, slotNames, thresholds, timeout, topK, uniformDrop, useBarrierExecutionMode, useSingleDatasetMode, validationIndicatorCol, verbosity, weightCol, xgboostDartMode)
283         super(LightGBMClassifier, self).init()
284         if java_obj is None:
--> 285             self._java_obj = self._new_java_obj("com.microsoft.azure.synapse.ml.lightgbm.LightGBMClassifier", self.uid)
286         else:
287             self._java_obj = java_obj
/databricks/spark/python/pyspark/ml/wrapper.py in _new_java_obj(java_class, *args)
64             java_obj = getattr(java_obj, name)
65         java_args = [_py2java(sc, arg) for arg in args]
---> 66         return java_obj(*java_args)
67
68     @staticmethod
/databricks/spark/python/lib/py4j-<IP_ADDRESS>-src.zip/py4j/java_gateway.py in call(self, *args)
1566
1567         answer = self._gateway_client.send_command(command)
-> 1568         return_value = get_return_value(
1569             answer, self._gateway_client, None, self._fqn)
1570
/databricks/spark/python/pyspark/sql/utils.py in deco(*a, **kw)
115     def deco(*a, **kw):
116         try:
--> 117             return f(*a, **kw)
118         except py4j.protocol.Py4JJavaError as e:
119             converted = convert_exception(e.java_exception)
/databricks/spark/python/lib/py4j-<IP_ADDRESS>-src.zip/py4j/protocol.py in get_return_value(answer, gateway_client, target_id, name)
324             value = OUTPUT_CONVERTER[type](answer[2:], gateway_client)
325             if answer[1] == REFERENCE_TYPE:
--> 326                 raise Py4JJavaError(
327                     "An error occurred while calling {0}{1}{2}.\n".
328                     format(target_id, ".", name), value)
Py4JJavaError: An error occurred while calling None.com.microsoft.azure.synapse.ml.lightgbm.LightGBMClassifier.
: java.lang.NoSuchMethodError: spray.json.BasicFormats.$init$(Lspray/json/BasicFormats;)V
at com.microsoft.azure.synapse.ml.logging.LogJsonProtocol$.(BasicLogging.scala:18)
at com.microsoft.azure.synapse.ml.logging.LogJsonProtocol$.(BasicLogging.scala)
at com.microsoft.azure.synapse.ml.logging.BasicLogging.logBase(BasicLogging.scala:31)
at com.microsoft.azure.synapse.ml.logging.BasicLogging.logBase$(BasicLogging.scala:30)
at com.microsoft.azure.synapse.ml.lightgbm.LightGBMClassifier.logBase(LightGBMClassifier.scala:26)
at com.microsoft.azure.synapse.ml.logging.BasicLogging.logClass(BasicLogging.scala:41)
at com.microsoft.azure.synapse.ml.logging.BasicLogging.logClass$(BasicLogging.scala:40)
at com.microsoft.azure.synapse.ml.lightgbm.LightGBMClassifier.logClass(LightGBMClassifier.scala:26)
at com.microsoft.azure.synapse.ml.lightgbm.LightGBMClassifier.(LightGBMClassifier.scala:29)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at py4j.reflection.MethodInvoker.invoke(MethodInvoker.java:247)
at py4j.reflection.ReflectionEngine.invoke(ReflectionEngine.java:380)
at py4j.Gateway.invoke(Gateway.java:250)
at py4j.commands.ConstructorCommand.invokeConstructor(ConstructorCommand.java:80)
at py4j.commands.ConstructorCommand.execute(ConstructorCommand.java:69)
at py4j.GatewayConnection.run(GatewayConnection.java:251)
at java.lang.Thread.run(Thread.java:748)

I tried your recommendation with com.microsoft.ml.spark:mmlspark_2.12:1.0.0-rc3-43-54379bf7-SNAPSHOT
but this version has no parameters named useSingleDatasetMode=True and numThreads. Maybe I should change it to the latest version. However I tested my code with only isUnbalance=True setting.

In kaggle credit card fraud dataset with the extreme unbalanced case,. the recall is extremely good which is more than 0.95, but the precision is extremely bad which is lower than 0.1. So f1 score and roc auc is lower than previous case with isUnbalance=False
In kaggle santander dataset, isUnbalance=True doesn't show much improvement. it showed roc-auc 0.72
I would like to test my code with the latest version with the useSingleDatasetMode=True and numThreads.
Can you please look into the error messages ?

hi @chulminkw it looks like the error is not in synapseml but in a dependency, the spray-json package:
https://github.com/spray/spray-json
synapseml depends on spray-json 1.3.2:
https://github.com/microsoft/SynapseML/blob/master/build.sbt#L32
actually, I also see here 1.3.4, but I'm not sure if this is used or how it is used:
https://github.com/microsoft/SynapseML/blob/f00272ec2dc402ce5521ae5f721195c168e82323/project/build.sbt#L2
I'm actually not sure why this is not working for you.  I wonder if somehow it's picking up a bad version, or there is something else going on.
Maybe you can try the latest coordinates:
com.microsoft.azure:synapseml_2.12:0.9.4-16-ff2aa020-SNAPSHOT
https://mmlspark.azureedge.net/maven
For this PR that was just recently merged:
https://github.com/microsoft/SynapseML/pull/1282
I actually tested that build on databricks and it was working fine.  No idea why it's failing.

Hello, Ilya Matiach, thanks for your effort.
com.microsoft.azure:synapseml_2.12:0.9.4-16-ff2aa020-SNAPSHOT is also not working to me.
I will continue testing that build in another version of databricks cluster.
By the way, can you please tell me what version of cluster of databricks you tested?
However, I'll close the issue, and thanks for your help.

Hello, Ilya Matiach, thanks for your effort.
com.microsoft.azure:synapseml_2.12:0.9.4-16-ff2aa020-SNAPSHOT is also not working to me.
I will continue testing that build in another version of databricks cluster.
By the way, can you please tell me what version of cluster of databricks you tested?
However, I'll close the issue, and thanks for your help.

Hello, Ilya Matiach, thanks for your effort.
com.microsoft.azure:synapseml_2.12:0.9.4-16-ff2aa020-SNAPSHOT is also not working to me.
I will continue testing that build in another version of databricks cluster.
By the way, can you please tell me what version of cluster of databricks you tested?

I was just recently using this on that build for benchmarking:

Hmm, I guess that is an older version of Databricks runtime.  Maybe I need to try the very latest to repro this issue.

also adding @mhamilton723 , it looks like we may need to do a special upgrade to work with latest databricks/spark version.  I'm guessing our package is still on an older version and that may be why it's not working with Databricks 10 ML spark 3.2.0

Nothing verified though.  I need to try out the latest version still to see if I repro the same error.

Thanks for the info.
I'll also look into it.


Created a light and dark mode button in all pages

#74 Added a light and dark mode button in all pages , please review my pull reuest.

@Sneha123-zudo please resolve the conflicts

Done , please have a look now.

@Sneha123-zudo the UI of the original site is changed in tracking, wellness & FAQ Pages, which is not looking appealing. Moreover, the header of the tracking page & rating page are distorted.
Please keep the UI as it was, & resolve the distortion in the above mentioned pages

@Sneha123-zudo the UI of the original site is changed in tracking, wellness & FAQ Pages, which does not look appealing. Moreover, the rating page & the header of the tracking page are distorted.
Please keep the UI as it was, & resolve the distortion in the above mentioned pages


Uncaught Error: spawn /Users/jueying/Library/Application Support/com.github.atom.ShipIt/update.mc...

[Enter steps to reproduce below:]

...
...

Atom Version: 1.2.0
System: Mac OS X 10.11.1
Thrown From: Atom Core
Stack Trace
Uncaught Error: spawn /Users/jueying/Library/Application Support/com.github.atom.ShipIt/update.mcM5Ezy/Atom.app/Contents/Frameworks/Atom Helper.app/Contents/MacOS/Atom Helper ENOENT
At events.js:141

Error: spawn /Users/jueying/Library/Application Support/com.github.atom.ShipIt/update.mcM5Ezy/Atom.app/Contents/Frameworks/Atom Helper.app/Contents/MacOS/Atom Helper ENOENT
    at exports._errnoException (util.js:837:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
    at onErrorNT (internal/child_process.js:344:16)
    at doNTCallback2 (node.js:441:9)
    at process._tickCallback (node.js:355:17)
    at EventEmitter.ipc.sendSync (/Users/jueying/Library/Application Support/com.github.atom.ShipIt/update.mcM5Ezy/Atom.app/Contents/Resources/atom.asar/renderer/api/lib/ipc.js:21:31)
    at BrowserWindow.Object.defineProperty.get [as loadSettings] (/Users/jueying/Library/Application Support/com.github.atom.ShipIt/update.mcM5Ezy/Atom.app/Contents/Resources/atom.asar/renderer/api/lib/remote.js:155:27)
    at Object.windowState (/Users/jueying/Library/Application Support/com.github.atom.ShipIt/update.mcM5Ezy/Atom.app/Contents/Resources/app.asar/src/window-load-settings-helpers.js:17:39)
    at Object.stringify (native)
    at exports.setWindowLoadSettings (/Users/jueying/Library/Application Support/com.github.atom.ShipIt/update.mcM5Ezy/Atom.app/Contents/Resources/app.asar/src/window-load-settings-helpers.js:27:52)

Commands

Config
{
  "core": {
    "themes": [
      "atom-material-ui",
      "atom-material-syntax"
    ],
    "ignoredNames": [
      ".DS_Store",
      ".git",
      ".svn"
    ],
    "projectHome": "/Users/jueying/Code",
    "disabledPackages": [
      "markdown-preview"
    ]
  },
  "editor": {
    "invisibles": {},
    "fontFamily": "menlo",
    "tabLength": 4
  }
}

Installed Packages
# User
No installed packages

# Dev
No dev packages

Duplicate of #9559 and #7399, please subscribe there for updates.


Preview of PostgreSQL 12 and 13

We have used PostgreSQL 12 in development, and would actually prefer to use PostgreSQL 13.
It would be very nice if you could provide PostgreSQL 12 and 13 as a "preview" version, but with lower guarantees etc. This could be solved by adding versions like:

12.0-preview
13.0-preview

Then we could use PostgreSQL 12 in development and less important applications. And Azure would get some experience running PostgreSQL 12 (and 13).
Does this this seem interesting?

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

ID: 63c8d482-9904-74ad-b0ad-5a8fc188510d
Version Independent ID: be1ac595-a36f-ad23-4507-e4bdcfc5ad33
Content: Supported versions - Azure Database for PostgreSQL - Single Server
Content Source: articles/postgresql/concepts-supported-versions.md
Service: postgresql
GitHub Login: @lfittl-msft
Microsoft Alias: lufittl

@kny78 Thank you for reaching out. Since this channel is for driving improvements towards MS Docs, could you provide the URL of the specific documentation that your feedback is applicable to? That way, we are able to make sure your feedback is addressed by the right team.

It was this page:
https://docs.microsoft.com/en-us/azure/postgresql/concepts-supported-versions
The question is also relevant to PostgreSQL Flexible Server

@kny78 Thanks for reaching out! We are actually working on Postgres 13 for Flexible Server already, and should have news on this soon. Note that you can already use Postgres 12 on Flexible Server.
For future service questions like this, you can also email<EMAIL_ADDRESS>

Thanks @lfittl-msft . We are currently located in Norway East, where Flexible server is not available.
Do you know if there is any plans for "PostgreSQL Flexible Server" in Norway East?

@kny78 Plans yes, but we don't have a timeline we can share yet at this point. Would it be an option for you to utilize the North Europe region instead? (already available)

@kny78 Please let us know if you need any further information regarding this. Or we will be going to close this case by EOD.

@kny78 We will proceed to close this issue now.
If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


IMPR/GRID-377 (unopinionated defaults.js)

@joneit @rdepena
Deopinionated defaults. One must opt-in to functionality

@joneit I was supposed to use addProperties right
BROKEN
noDataMessage
Gridlines
RowNumbersAutosizing
Column Dragging


About the tool specific suggestions for improvement

**This is really a great project, it helped me a lot in the real world, if I am free I am very willing to help you improve and improve this project, here I would like to make a few small suggestions for continued progress.

The first point, you can continue to add more AD domain vulnerability detection in the vuln_checks module, such as HiveNightmare, Printspooler family (Nightmare and Demon) and Exchange server vulnerability detection, which is very important, because in reality Exchange is very high privilege, and easy to to attack and if the attack is successful very easy to threaten the domain controller, so I felt the need to add a check for Exchange vulnerability.(CVE-2018-8581, CVE-2020-0688, CVE-2020-16875, CVE-2021-34473, CVE-2021-26855/CVE-2021-27065, CVE-2022-41040/CVE-2022-41082)

The second point is that I think we can add an automated capture of all tour passwords in the pwd_dump module, which can be combined with LaZagne, which is a great tool, you know, in the actual infiltration of the tour passwords are likely to be a breakthrough!!! So I think it's feasible

Having said that, I hope very much that this tool will get better and better, and thank you very much for your open source spirit, keep moving!!!**

Thanks a lot for your feedback. Well appreciated!
I've added Print nightmare, but won't be adding HiveNightmare and Lazagne since those should be executed locally on the Windows machine, and not remotely.
For the collected passwords, most of the pwd_dump uses crackmapexec, so the passwords are already stored in it's database/log.
Regarding the Exchange exploits, that's also a great idea, but I'm not planning on integrating them at the moment. Please feel free to create a pull request with the Exchange checks if you'd like. But I'll close this issue for now.
Thanks !


Language Grammar - Field access expression implicit-target-projection

Hello,
In the language grammar, Field access expressions defines field-access-expression as one of several alternatives including projection and implicit-target-projection. In turn, implicit-target-projection is also defined as projection. I believe the latter is incorrect.
projection requires the presence of an explicit target (i.e. the presence of a primary-expression), which, by definition, shouldn't be expected for an implicit target (e.g. [[Field1]], which Excel accepts as valid but this grammar rule rejects).
It seems like the correct definition for implicit-target-projection should be along the lines of the following:
implicit-target-projection:
  required-projection
  optional-projection

(e.g. eliminate the requirement that a primary-expression be used before the projection)
Can you confirm?
Thank you!

@bgribaudo Thanks for the feedback. Yes, we can confirm. The implicit-target-projection syntax now includes the optional-projection syntax.

Thank you, @DougKlopfenstein!


Design for Limiting file download by # records on the cdd (Need by 1/24)

Context
The custom data download will limit how much data a user can download by assessing the number of records that is returned in a dataset.
When the total number of records returned is more than the configured limit
Then the system displays a modal with the following message: Your query exceeds the record limit of ####. Refine your query to further limit the number of records returned or visit the Bulk Data Files (hyperlink)
AND the download button is disabled

Design needs

Will need design for the modal with the following message: Your query exceeds the record limit of ####. Refine your query to further limit the number of records returned or visit the Bulk Data Files (hyperlink)

Download button being disabled

@tlageman-epa Here are the screens for Limiting the Data Download. https://xd.adobe.com/view/5843045c-99a2-4c6e-b880-2f127f19796f-0d10/
I used the "Alert component" that will appear letting the user know that they need to revise their filter selections before they are able to download. Let me know if you have questions.


irsa-operator fails to remove finalizer

In my e2e test run, cluster deletion is failing in upgrade tests (seems inconsistent), and I tracked it down to irsa-operator failing to remove its finalizer from AWSCluster CR.
These is the error from irsa-operator:
2024-07-30T12:29:37Z	ERROR	Reconciler error	{"controller": "awscluster", "controllerGroup": "infrastructure.cluster.x-k8s.io", "controllerKind": "AWSCluster", "AWSCluster": {"name":"t-tjupwewq9lhluvusov","namespace":"org-t-rgd8t8fdvqpzy4nfad"}, "namespace": "org-t-rgd8t8fdvqpzy4nfad", "name": "t-tjupwewq9lhluvusov", "reconcileID": "4d76889d-140f-4cda-8bc9-1f519610d060", "error": "ConfigMap \"t-tjupwewq9lhluvusov-cluster-values\" not found"}

Looks like that the deletion reconciliation fails as irsa-operator fails to find (I assume already deleted) cluster values ConfigMap.
As a consequence, leftover CRs are piling up in grizzly :see_no_evil:
Does irsa-operator need cluster values ConfigMap here? Can it just ignore if it is not there?

I think I found the problem. On cluster deletion, the IRSA operator first removes the finalizers from the cluster values ConfigMap, and then from the AWSCluster CR (here). When removing the finalizers from AWSCluster, a race condition can occur, where another operator is also removing their finalizers at the same time, in such case the patch operation will fail. There's already a retry mechanism in place for such situations (here).
The problem is (I think) that, during the patching, the k8s client library panics instead of returning an error, so the retry mechanism never kicks in, so the finalizer never gets removed from AWSCluster on the first deletion reconciliation loop. Then subsequent reconciliations fail because the cluster values ConfigMap is already gone.


Add editorDarkTheme improvements to editor

Ticket to back port the improvements to the CodeMirror theming approach made during the block-to-text development.

Issues currently exist in the current approach on staging
Dark mode:

Light mode:


Update config versions for docker build

Update config version in docker build to be consistent with compile locally instruction. (v0.0.6 for Mainnet and v0.0.5 for Amber testnet).
Docs PR: https://github.com/smartbch/docs/pull/61

Codecov Report

Merging #49 (243c27f) into main (8c2bc79) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 243c27f differs from pull request most recent head 95c0557. Consider uploading reports for the commit 95c0557 to get more accurate results

@@           Coverage Diff           @@
##             main      #49   +/-   ##
=======================================
  Coverage   46.41%   46.41%
=======================================
  Files          44       44
  Lines        5737     5737
=======================================
  Hits         2663     2663
  Misses       2734     2734
  Partials      340      340

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 8c2bc79...95c0557. Read the comment docs.


application.get should not support app names

application.get() should not support searching by application name, so that it never returns ambiguous results.
Consumers that care about this use case should be using application.getAll().
Discussed in product call 2021-01-05 as part of the CLI changes with regards to the release of orgs.
See: https://jel.ly.fish/brainstorm-call-product-5jan2021-d6f4871d-c9d9-4deb-82ca-7da2c25034a6

During the product call, it was suggested that the SDK should not offer application.get(appName) because the app name on its own is ambiguous. However, I think that an alternative that would keep with the spirit of the suggestion is for the SDK to require upfront disambiguation in the form of an option that specified the "kind" of application that the caller would like to get: "direct access" (an app that belongs to an org that belongs to the user), "public app" or some other kind. If the app "kind" was not specified, the SDK would throw an error such as "Invalid arguments" (indicating a bug in the caller code, rather than user input ambiguity).

During the product call, it was suggested that the SDK should not offer application.get(appName) because the app name on its own is ambiguous. However, I think that an alternative that would keep with the spirit of the suggestion is for the SDK to require upfront disambiguation in the form of an option that specified the "kind" of application that the caller would like to get: "direct access" (an app that belongs to an org that belongs to the user), "public app" or some other kind. If the app "kind" was not specified, the SDK would throw an error such as "Invalid arguments" (indicating a bug in the caller code, rather than user input ambiguity).

@pdcastro I think that the point was to just make all app related calls unambiguous, but just teaching the users how to use app slug. This wouldn't just solve the public app issue, but also the ambiguous errors that cli users get when using an app name that is used by more than one directly accessible apps (in different orgs). If we go this way, then it would also simplify the CLI code as well, since it will no longer have to follow any  "ambiguous error => show a list of apps to select" flow.
That's a good reminder though to invite you to the respective call I'm planning about direct pine usage in the CLI & UI.

@pdcastro I think that the point was to just make all app related calls unambiguous, but just teaching the users how to use app slug. This wouldn't just solve the public app issue, but also the ambiguous errors that cli users get when using an app name that is used by more than one directly accessible apps (in different orgs). If we go this way, then it would also simplify the CLI code as well, since it will no longer have to follow any  "ambiguous error => show a list of apps to select" flow.
That's a good reminder though to invite you to the respective call I'm planning about direct pine usage in the CLI & UI.