qtkeychain: Fixes Qt4 build.

Motivation for this change
Not 100% enthusiastic at "fixing" Qt4 build as this is. Why? Because the only use (AFAICT) of Qt4 qtkeychain was tomahawk, which has been marked broken and is abandoned upstream. Furthermore, tomahawk supposedly can be built using Qt5 instead (according to recent unreleased commits). Thus this is untested. I won't be mad, possibly glad if instead we remove the Qt4 attribute of qtkeychain.
Though, in the vein of ZHF #45960, I have this fixed cooked and ready. (I cooked it before I could realize this wouldn't be tested.)
It'll need to be cherry-picked to 18.09.
Things done

✔ Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

✔ NixOS
⬜ macOS
⬜ other Linux distributions

⬜ Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
✅ Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
🆖 Tested execution of all binary files (usually in ./result/bin/)
⬜ Determined the impact on package closure size (by running nix path-info -S before and after)
✔ Fits CONTRIBUTING.md.

@GrahamcOfBorg build qtkeychain libsForQt5.qtkeychain

Success on x86_64-linux (full log)
Attempted: qtkeychain
Partial log (click to expand)
-- Installing: /nix/store/81wisy1pxdkhq0xwis96rzvr05wy4yrp-qtkeychain-qt4-0.9.1/lib/cmake/QtKeychain/QtKeychainConfigVersion.cmake
glibPreFixupPhase
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/81wisy1pxdkhq0xwis96rzvr05wy4yrp-qtkeychain-qt4-0.9.1
shrinking /nix/store/81wisy1pxdkhq0xwis96rzvr05wy4yrp-qtkeychain-qt4-0.9.1/lib/libqtkeychain.so.0.9.1
strip is /nix/store/h0lbngpv6ln56hjj59i6l77vxq25flbz-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/81wisy1pxdkhq0xwis96rzvr05wy4yrp-qtkeychain-qt4-0.9.1/lib
patching script interpreter paths in /nix/store/81wisy1pxdkhq0xwis96rzvr05wy4yrp-qtkeychain-qt4-0.9.1
checking for references to /build in /nix/store/81wisy1pxdkhq0xwis96rzvr05wy4yrp-qtkeychain-qt4-0.9.1...
/nix/store/81wisy1pxdkhq0xwis96rzvr05wy4yrp-qtkeychain-qt4-0.9.1

Success on x86_64-darwin (full log)
Attempted: qtkeychain
Partial log (click to expand)
-- Installing: /nix/store/bkk9h3fld5pjlk2zd9v1bzsj9j459z8z-qtkeychain-qt4-0.9.1/lib/cmake/QtKeychain/QtKeychainConfigVersion.cmake
glibPreFixupPhase
post-installation fixup
strip is /nix/store/df6k4mgdjxciy0f637lryp7c9ln7n1m3-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/bkk9h3fld5pjlk2zd9v1bzsj9j459z8z-qtkeychain-qt4-0.9.1/lib
patching script interpreter paths in /nix/store/bkk9h3fld5pjlk2zd9v1bzsj9j459z8z-qtkeychain-qt4-0.9.1
/nix/store/bkk9h3fld5pjlk2zd9v1bzsj9j459z8z-qtkeychain-qt4-0.9.1/lib/libqtkeychain.0.9.1.dylib: fixing dylib
/nix/store/bkk9h3fld5pjlk2zd9v1bzsj9j459z8z-qtkeychain-qt4-0.9.1/lib/libqtkeychain.0.9.1.dylib: fixing dylib
/nix/store/bkk9h3fld5pjlk2zd9v1bzsj9j459z8z-qtkeychain-qt4-0.9.1/lib/libqtkeychain.0.9.1.dylib: fixing dylib
/nix/store/bkk9h3fld5pjlk2zd9v1bzsj9j459z8z-qtkeychain-qt4-0.9.1

Success on aarch64-linux (full log)
Attempted: qtkeychain
Partial log (click to expand)
-- Installing: /nix/store/1g4gskj4i4sk6qcg240ph1g2yf6c0kvw-qtkeychain-qt4-0.9.1/lib/cmake/QtKeychain/QtKeychainConfigVersion.cmake
glibPreFixupPhase
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/1g4gskj4i4sk6qcg240ph1g2yf6c0kvw-qtkeychain-qt4-0.9.1
shrinking /nix/store/1g4gskj4i4sk6qcg240ph1g2yf6c0kvw-qtkeychain-qt4-0.9.1/lib/libqtkeychain.so.0.9.1
strip is /nix/store/y4ymnvgxygpq05h03kyzbj572zmh6zla-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/1g4gskj4i4sk6qcg240ph1g2yf6c0kvw-qtkeychain-qt4-0.9.1/lib
patching script interpreter paths in /nix/store/1g4gskj4i4sk6qcg240ph1g2yf6c0kvw-qtkeychain-qt4-0.9.1
checking for references to /build in /nix/store/1g4gskj4i4sk6qcg240ph1g2yf6c0kvw-qtkeychain-qt4-0.9.1...
/nix/store/1g4gskj4i4sk6qcg240ph1g2yf6c0kvw-qtkeychain-qt4-0.9.1

Thanks for spotting and fixing this.

I won't be mad, possibly glad if instead we remove the Qt4 attribute of qtkeychain.

That would require us to adapt the dead and broken tomahawk (waste of time), or drop that as well.
Let's merge this for now and consider dropping both tomahawk and qtkeychain from master in the future.

backport: dea9a04ae6f


Import Schema method in .NET SDK or Powershell is missing

In the UI, users are able to use the "Import Schema" button.

Is there a similar feature in the SDK? I could not find any documentation pointing to it.

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

ID: 75402f01-c53e-25e0-6f1c-bc94d797dda1
Version Independent ID: a3dfb190-a12d-37cf-2dfe-034becd60e39
Content: Schema mapping in copy activity
Content Source: articles/data-factory/copy-activity-schema-and-type-mapping.md
Service: data-factory
GitHub Login: @linda33wj
Microsoft Alias: jingwang

@chunla-ms Thank you for reaching out and bringing this to our notice. At this time we are reviewing the feedback and will provide an update as appropriate

@chunla-ms "Import Schema" feature is a UX only gesture.
I would recommend you to please share/provide your feedback in ADF uservoice forum. All the feedback you share, is closely monitored by the Data Factory Product team and will take appropriate action.
Hope this helps.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply and reopen the issue. We will gladly continue the discussion.

@chunla-ms Just curious to know what is your scenario to have this feature available in SDK/Powershell?
Could you please provide additional info about your requirement, so that I can pass to the internal engineering team.
Thank you!

I'm team is building a table level backup system, would be great if this feature could be done using the SDK so I don't have to iterate columns.
We have a lot of tables newly generated everyday and with a lot of sql server instance so I want this to be done dynamically

Thank you for sharing the details. I will pass this info internally.
Meanwhile please post your suggestion/idea in ADF feedback forum.


It says i need teambeefinstaller.exe and i have no idea what it is and how to get it

also will this work on my oculus quest 2?

This is a PCVR mod so will only work with Quest 2 via Link / Airlink.
You can get the installer on the releases page: https://github.com/baggyg/BendyVR/releases/tag/v1.1.0
Unrar the contents.


Create 0000-01-02-chhotusnehesh3.md

created a branch, created a file and made a commit, and opened a pull request

created a branch, created a file and made a commit, and opened a pull request

created a branch, created a file and made a commit, and opened a pull request created a branch, created a file and made a commit, and opened a pull request created a branch, created a file and made a commit, and opened a pull request


illegal/malformed utf-8 in anagram

The JSON in the API is choking on the tests.out file, which is binary. @kdar Is this file something that needs to be shipped to the user, or would it be OK to delete it from the repository and add a gitignore for it?

Opps. Delete it :).

Haha, awesome, thanks!


Add shadow to sidemenu

Add shadow to sidemenu
Make sidemenu icon size configurable

Hi, thanks for the PR. Have you seen the already implemented function setSideShadow?

Hi,
Yes I have seen function setSideShadow. It adds shadow from central panel to side panel. Screenshot is here: https://github.com/MaksymDyomin/SideMenuController/blob/master/screenshots/SideMenuControllerShadow1.png
And it works when side panel is under center panel. For using this function SideMenuController should be configured as following:
SideMenuController.preferences.drawing.sidePanelPosition = .underCenterPanelLeft
SideMenuController.preferences.drawing.centerPanelShadow = true
My pull request adds possibility to configure SideMenuController in different way:
SideMenuController.preferences.drawing.sidePanelPosition = .overCenterPanelLeft
SideMenuController.preferences.drawing.sidePanelShadow = true
This configuration will work if side panel will be over center panel. And shadow will be dropped from side panel to center panel.
Screenshot is here: https://github.com/MaksymDyomin/SideMenuController/blob/master/screenshots/SideMenuControllerShadow2.png

is there a way to change icon size? thanks

Yes, there is.
You can change hamburger icon size:
SideMenuController.preferences.drawing.menuButtonSize = CGSize(width: 18, height: 12)

@MaksymDyomin it says it has no member menuButtonSize

@gulzatique please note that this PR have not been merged. Are you sure you using my fork and branch sidemenu-shadow ?


Node v8.8.0 supports http2 by default. Does this change anything for gRPC?

See https://nodejs.org/en/blog/release/v8.8.0/ for the release notes. Can we slim down the gRPC installation if http2 is built in?

gRPC is in the process of writing a native JavaScript client, which will be based on this, but it will be a few months before it is ready. They also plan on having some kind of dual-installation process so that you get the full C library on Node 6 and the native library on Node 8.

Closing as duplicate of #2697.


fix(#1327) Fix table sorting

Couldn't add a test case to validate the _sort event firing, as the goa-table-sort-header is within a slot and was hard to test with@testing-library/svelte. Open to suggestions on this
Added a small test case on the react component but that isn't the actual the issue

[ ] Sorting does not work in: React App, StoryBook.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Documentation for ignore3vl function

@seut  Would be great if you could take a 1st look.

@matriv looks good to me

@seut update the PR, please check.

i think we should also provide an array example otherwise looks good.

@joemoe Please check my fixups


Adaptive scale behaviour

The adaptive scale seems to behave in a non-intuitive way, I added a print(signal_scale) after line 79 in pag_nodes.py to inspect the values and with 11 steps and 4 PAG scale this is what I get
Adaptive scale  .1: 3.9, 3.9, 3.9, 3.8, 3.8, 3.8, 3.7, 3.7, 3.7, 3.6, 3.6
Adaptive scale .3: 3.9, 1.0, -1., -4., -7., -10, -13, -16, -19, -22, -25
Adaptive scale .5: 3.7, -19, -41, -64, -87, -10, -13, -15, -17, -20, -22
Both .3 and .5 disable PAG after the first step, where one (or at least I) would expect it to decay and zero out only after ~30% and ~50% of the steps respectively, or maybe decay by 10%, 30% and 50% every step, idk, but the way it currently works seems very unintuitive, am I missing something?

This was the attempt to make the implementation from the original repo a little bit more intuitive. Since some users are used to this parameter, I'm reluctant to change it's behavior.
As an alternative, you can chain multiple PAG nodes and set different scale and sigma_start/sigma_end for them to manually schedule pag scaling

I see (though I have no idea how someone would get used to this behavior🤭), I'll just stick to my local edits then, thanks!


Fix typo in conditional examples

Changes
Adds the missing i.
/kind misc
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[ N/A] Includes tests (if functionality changed/added)
[ N/A] Includes docs (if user facing)
[ X] Commit messages follow commit message best practices

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.

😸
/lgtm

gosec is on a roll today! (see https://github.com/tektoncd/triggers/pull/597 as well!)
===============================
==== RUNNING GOLANGCI-LINT ====
===============================
pkg/apis/pipeline/v1beta1/zz_generated.deepcopy.go:690:16: G601: Implicit memory aliasing in for loop. (gosec)
				in, out := &val, &outVal
				           ^
pkg/apis/pipeline/v1beta1/zz_generated.deepcopy.go:736:16: G601: Implicit memory aliasing in for loop. (gosec)
				in, out := &val, &outVal
				           ^
pkg/pod/status.go:119:37: G601: Implicit memory aliasing in for loop. (gosec)
				if err := updateStatusStartTime(&s); err != nil {
				                                ^
pkg/reconciler/pipelinerun/resources/pipelinerunresolution.go:237:46: G601: Implicit memory aliasing in for loop. (gosec)
		r, err := resources.GetResourceFromBinding(&resource, getResource)

/test pull-tekton-pipeline-build-tests

Looks like a flake! Opened https://github.com/tektoncd/pipeline/issues/2840
/test pull-tekton-pipeline-integration-tests

Expected 2 number of successful events from pipelinerun and taskrun but got 3; list of receieved events

wut
/test pull-tekton-pipeline-integration-tests

/test pull-tekton-pipeline-integration-tests

/test pull-tekton-pipeline-integration-tests

/test pull-tekton-pipeline-integration-tests

/test pull-tekton-pipeline-integration-tests

/test pull-tekton-pipeline-integration-tests

/test pull-tekton-pipeline-integration-tests


Breakpoints don't stay disable

I disabled breakpoints for a method using breakpoint browser:

then proceeded to run a test via doit in workspace and ended up hitting the disabled breakpoint:

The first picture of the breakpoint browser shows that there is a disabled breakpoint. But the second picture (copied below) shows that the same breakpoint is not disabled. If the second one is to be believed, then the correct behavior was for the test to stop at the second breakpoint.

Presumably though, there's nothing in your test that enables breakpoints. Also, I assume you didn't manually enable breakpoints from another browser, the transcript, etc between the time you disabled the breakpoint and started the test. That implies Jadeite re-enabled the breakpoint (or all breakpoints) magically.
It's not reproducable, so if it's not too inconvenient, can you add self halt in GsNMethod class>>_enableAllBreaks and GsNMethod>>setBreakAtStepPoint:? These are the two methods that services uses to enable breaks. If it is getting enabled magically through Jadeite, we would get a stack showing the path through services code back to the client command. That would help debugging.

I haven't been using the breakpoint browser recently ... I think I have several issues submitted and I'm waiting for those issues to be addressed (I think this gets them: https://github.com/GemTalk/Jadeite/issues?q=is%3Aopen+is%3Aissue+author%3Adalehenrich+breakpoint+browser).... don't get me wrong ... i want to use the breakpoint browser:)

Not easily reproduced in 3.2.9, presume fixed.


Problem with External Players

Steps to reproduce
1)Enable External Player
2)Set always open Mx player
3)Then just open any episode
Expected behavior
Play in MX player Normally
Actual behavior
Mx sends an error "Can't play this link"
Crash logs
No response
Aniyomi version
<IP_ADDRESS>
Android version
Android 10
Device
Infinix hot 9 play
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extensions repository.
[X] I have tried the troubleshooting guide.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

Steps to reproduce
1)Enable External Player 2)Set always open Mx player 3)Then just open any episode
Expected behavior
Play in VLC or any other player
Actual behavior
Receive an error "Can't play this link"
Crash logs
No response
Aniyomi version
<IP_ADDRESS>
Android version
Android 7.0
Device
Lenovo Tab 7

 Steps to reproduce

1)Enable External Player
2)Set always open Mx player
3)Then just open any episode
 Expected behavior

1)Play in VLC and MX player.
2)Any other video players.
 Actual behavior

1)Receive an error "Can't play this link"
 Aniyomi version

1)<IP_ADDRESS>
 Android version

1)Android 7.0
 Device

1)Lenovo Tab 7

Device: Realms 3 pro
Aniyomi version: <IP_ADDRESS>
Android version: 11
I have same problem with external players.

gogoanime can be played with mpv-android
use a referer
I did try myself it works
@jmir1 mpv-android should be added as an external player

gogoanime can be played with mpv-android use a referer
I did try myself it works

What about vlc?

Check this comment Here

How to change video quality while using external player?

How to change video quality while using external player?

Hold on download icon and it shows options


Associated records are not created with default values

Description
When creating a record with associations, only the top level record is created if all the associated records use default values.  Here is an example of a much larger policy database I'm creating.  The real db has hundreds of settings (all with default values) across more than 15 tables.  Each policy is initially created with just a name.
Actual Behavior
Only the record in the policy table is created.  No records are created in any of the other tables.
Expected Behavior
A record should be created in all of the associated tables with the default values.
Below is the code to reproduce this issue.
package main

import (
	"time"

	"gorm.io/gorm"
)

var (
	mainDBPath string = "test.db"
)

type DBModel struct {
	ID        uint `gorm:"primary_key"`
	PolicyID  uint
	CreatedAt time.Time
	UpdatedAt time.Time
	DeletedAt *time.Time `sql:"index"`
}

type Policy struct {
	gorm.Model
	Name         string         `gorm:"unique;unique_index"`
	Settings     PolicySettings `gorm:"embedded"`
	SettingX     bool           `gorm:"default:false"`
	DefaultInput bool           `gorm:"default:true"`
	Rulesets     Ruleset
	Files        []PolicyFile
	Sources      []Source
}

type PolicySettings struct {
	TestMode    bool          `gorm:"default:false"`
	FileCleanUP bool          `gorm:"default:true"`
	FileAge     time.Duration `default:"24h"`
}

type Source struct {
	DBModel
	URL        string
	SourceType string
}

type PolicyFile struct {
	DBModel
	Filename string
	Filepath string
	Filetype string
}

type Ruleset struct {
	DBModel
	RecommendedDisable bool `gorm:"default:true"`
	RecommendedEnable  bool `gorm:"default:true"`
	RecommendedModify  bool `gorm:"default:true"`
	IPExtraction       bool `gorm:"default:true"`
	JA3Extraction      bool `gorm:"default:true"`
	TestRuleset        bool `gorm:"default:true"`
	FailOnRulesetError bool `gorm:"default:false"`
}

Here is the test code I used to create the table and create a policy.
package main

import (
	"testing"

	"github.com/stretchr/testify/assert"
	"gorm.io/driver/sqlite"
	"gorm.io/gorm"
	"gorm.io/gorm/logger"
	"gorm.io/gorm/schema"
)

func TestCreateTables(t *testing.T) {
	t.Run("DB Test", func(t *testing.T) {
		// Open the Database
		db, err := gorm.Open(sqlite.Open(mainDBPath), &gorm.Config{
			Logger: logger.Default.LogMode(logger.Info),
			NamingStrategy: schema.NamingStrategy{
				SingularTable: true,
			},
		})
		assert.Nil(t, err)

		// Create the tables
		err = db.AutoMigrate(&Policy{})
		assert.Nil(t, err)
		err = db.AutoMigrate(&Ruleset{})
		assert.Nil(t, err)
		err = db.AutoMigrate(&PolicyFile{})
		assert.Nil(t, err)
		err = db.AutoMigrate(&Source{})
		assert.Nil(t, err)
	})
}

func TestCreateDefaultPolicy(t *testing.T) {
	t.Run("DB Test", func(t *testing.T) {
		// Open the Database
		db, err := gorm.Open(sqlite.Open(mainDBPath), &gorm.Config{
			Logger: logger.Default.LogMode(logger.Info),
			NamingStrategy: schema.NamingStrategy{
				SingularTable: true,
			},
		})
		assert.Nil(t, err)

		// Create a new policy with all default settings
		policy := Policy{Name: "policy10"}
		result := db.Create(&policy)
		assert.Nil(t, result.Error)
		db.Save(&policy)
	})
}

Here's the output from creating the tables.
=== RUN   TestCreateTables
=== RUN   TestCreateTables/DB_Test

2022/07/22 12:02:40 /home/james/go/pkg/mod/gorm.io/driver/sqlite@v1.3.6/migrator.go:33
[0.030ms] [rows:-] SELECT count(*) FROM sqlite_master WHERE type='table' AND name="policy"

2022/07/22 12:02:40 /home/james/db-test/main_test.go:25
[10.688ms] [rows:0] CREATE TABLE `policy` (`id` integer,`created_at` datetime,`updated_at` datetime,`deleted_at` datetime,`name` text UNIQUE,`test_mode` numeric DEFAULT false,`file_clean_up` numeric DEFAULT true,`file_age` integer,`setting_x` numeric DEFAULT false,`default_input` numeric DEFAULT true,PRIMARY KEY (`id`))

2022/07/22 12:02:40 /home/james/go/pkg/mod/gorm.io/driver/sqlite@v1.3.6/migrator.go:293
[23.991ms] [rows:0] CREATE INDEX `idx_policy_deleted_at` ON `policy`(`deleted_at`)

2022/07/22 12:02:40 /home/james/go/pkg/mod/gorm.io/driver/sqlite@v1.3.6/migrator.go:33
[0.032ms] [rows:-] SELECT count(*) FROM sqlite_master WHERE type='table' AND name="policy"

2022/07/22 12:02:40 /home/james/go/pkg/mod/gorm.io/driver/sqlite@v1.3.6/migrator.go:111
[0.084ms] [rows:2] SELECT sql FROM sqlite_master WHERE type IN ("table","index") AND tbl_name = "policy" AND sql IS NOT NULL order by type = "table" desc

2022/07/22 12:02:40 /home/james/go/pkg/mod/gorm.io/driver/sqlite@v1.3.6/migrator.go:119
[0.026ms] [rows:-] SELECT * FROM `policy` LIMIT 1

2022/07/22 12:02:40 /home/james/go/pkg/mod/gorm.io/driver/sqlite@v1.3.6/migrator.go:310
[0.027ms] [rows:-] SELECT count(*) FROM sqlite_master WHERE type = "index" AND tbl_name = "policy" AND name = "idx_policy_deleted_at"

2022/07/22 12:02:40 /home/james/go/pkg/mod/gorm.io/driver/sqlite@v1.3.6/migrator.go:33
[0.027ms] [rows:-] SELECT count(*) FROM sqlite_master WHERE type='table' AND name="ruleset"

2022/07/22 12:02:40 /home/james/db-test/main_test.go:27
[4.008ms] [rows:0] CREATE TABLE `ruleset` (`id` integer,`policy_id` integer,`created_at` datetime,`updated_at` datetime,`deleted_at` datetime,`recommended_disable` numeric DEFAULT true,`recommended_enable` numeric DEFAULT true,`recommended_modify` numeric DEFAULT true,`ip_extraction` numeric DEFAULT true,`ja3_extraction` numeric DEFAULT true,`test_ruleset` numeric DEFAULT true,`fail_on_ruleset_error` numeric DEFAULT false,PRIMARY KEY (`id`),CONSTRAINT `fk_policy_rulesets` FOREIGN KEY (`policy_id`) REFERENCES `policy`(`id`))

2022/07/22 12:02:40 /home/james/go/pkg/mod/gorm.io/driver/sqlite@v1.3.6/migrator.go:33
[0.065ms] [rows:-] SELECT count(*) FROM sqlite_master WHERE type='table' AND name="policy"

2022/07/22 12:02:40 /home/james/go/pkg/mod/gorm.io/driver/sqlite@v1.3.6/migrator.go:111
[0.155ms] [rows:2] SELECT sql FROM sqlite_master WHERE type IN ("table","index") AND tbl_name = "policy" AND sql IS NOT NULL order by type = "table" desc

2022/07/22 12:02:40 /home/james/go/pkg/mod/gorm.io/driver/sqlite@v1.3.6/migrator.go:119
[0.051ms] [rows:-] SELECT * FROM `policy` LIMIT 1

2022/07/22 12:02:40 /home/james/go/pkg/mod/gorm.io/driver/sqlite@v1.3.6/migrator.go:310
[0.052ms] [rows:-] SELECT count(*) FROM sqlite_master WHERE type = "index" AND tbl_name = "policy" AND name = "idx_policy_deleted_at"

2022/07/22 12:02:40 /home/james/go/pkg/mod/gorm.io/driver/sqlite@v1.3.6/migrator.go:33
[0.040ms] [rows:-] SELECT count(*) FROM sqlite_master WHERE type='table' AND name="policy_file"

2022/07/22 12:02:40 /home/james/db-test/main_test.go:29
[8.194ms] [rows:0] CREATE TABLE `policy_file` (`id` integer,`policy_id` integer,`created_at` datetime,`updated_at` datetime,`deleted_at` datetime,`filename` text,`filepath` text,`filetype` text,PRIMARY KEY (`id`),CONSTRAINT `fk_policy_files` FOREIGN KEY (`policy_id`) REFERENCES `policy`(`id`))

2022/07/22 12:02:40 /home/james/go/pkg/mod/gorm.io/driver/sqlite@v1.3.6/migrator.go:33
[0.028ms] [rows:-] SELECT count(*) FROM sqlite_master WHERE type='table' AND name="policy"

2022/07/22 12:02:40 /home/james/go/pkg/mod/gorm.io/driver/sqlite@v1.3.6/migrator.go:111
[0.068ms] [rows:2] SELECT sql FROM sqlite_master WHERE type IN ("table","index") AND tbl_name = "policy" AND sql IS NOT NULL order by type = "table" desc

2022/07/22 12:02:40 /home/james/go/pkg/mod/gorm.io/driver/sqlite@v1.3.6/migrator.go:119
[0.024ms] [rows:-] SELECT * FROM `policy` LIMIT 1

2022/07/22 12:02:40 /home/james/go/pkg/mod/gorm.io/driver/sqlite@v1.3.6/migrator.go:310
[0.029ms] [rows:-] SELECT count(*) FROM sqlite_master WHERE type = "index" AND tbl_name = "policy" AND name = "idx_policy_deleted_at"

2022/07/22 12:02:40 /home/james/go/pkg/mod/gorm.io/driver/sqlite@v1.3.6/migrator.go:33
[0.020ms] [rows:-] SELECT count(*) FROM sqlite_master WHERE type='table' AND name="source"

2022/07/22 12:02:40 /home/james/db-test/main_test.go:31
[5.066ms] [rows:0] CREATE TABLE `source` (`id` integer,`policy_id` integer,`created_at` datetime,`updated_at` datetime,`deleted_at` datetime,`url` text,`source_type` text,PRIMARY KEY (`id`),CONSTRAINT `fk_policy_sources` FOREIGN KEY (`policy_id`) REFERENCES `policy`(`id`))
--- PASS: TestCreateTables (0.06s)
    --- PASS: TestCreateTables/DB_Test (0.06s)
PASS
ok      github.com/jlagermann/db-test   0.061s

> Test run finished at 7/22/2022, 12:03:00 PM <

Here's the output from creating a policy.
=== RUN   TestCreateDefaultPolicy/DB_Test

2022/07/22 12:03:55 /home/james/db-test/main_test.go:49
[5.898ms] [rows:1] INSERT INTO `policy` (`created_at`,`updated_at`,`deleted_at`,`name`,`test_mode`,`file_clean_up`,`file_age`,`setting_x`,`default_input`) VALUES ("2022-07-22 12:03:55.924","2022-07-22 12:03:55.924",NULL,"policy10",false,true,0,false,true) RETURNING `id`

2022/07/22 12:03:55 /home/james/db-test/main_test.go:51
[3.856ms] [rows:1] UPDATE `policy` SET `created_at`="2022-07-22 12:03:55.924",`updated_at`="2022-07-22 12:03:55.93",`deleted_at`=NULL,`name`="policy10",`test_mode`=false,`file_clean_up`=true,`file_age`=0,`setting_x`=false,`default_input`=true WHERE `policy`.`deleted_at` IS NULL AND `id` = 1
--- PASS: TestCreateDefaultPolicy (0.01s)
    --- PASS: TestCreateDefaultPolicy/DB_Test (0.01s)
PASS
ok      github.com/jlagermann/db-test   0.015s

> Test run finished at 7/22/2022, 12:04:23 PM <

We don't know if the user wants to create a associated table, what can explicitly specify this behavior is to refer to a non-null value.
// insert into  policies
DB.Create(&Policy{Name: "policy10"}).Error
// insert into rulesets and policies
DB.Create(&Policy{Name: "policy10", Rulesets: Ruleset{RecommendedDisable: true}}).Error

What if the all the defaults for a table are null values?  When I query the db for a policy, I need to get all the settings back, including null values.  If an record does not exist for that policy in an associated table, none of those settings will be returned.

We won't insert the associated zero value, but you can still use a non-null pointer instead.
type Policy struct {
	...
	Rulesets     *Ruleset
}

DB.Create(&Policy{Name: "policy10", Rulesets: &Ruleset{}})

That works for tables that have at least one column with a non-null default, but it's not working for tables where all the defaults are null values.

I don't think inserting null values into an association table is a general requirement, you can implement it in a https://gorm.io/docs/write_plugins.html#Plugin, that is, check the association relationship before creating it, and then fill it with the default value

If I use a non-null pointer to create a policy, I have to have a record for that policy in each table, even if the record would be all null values.  Without the null-value records, I cannot reference any value from that struct.
If I don't use a pointer to create a policy, I will have all the fields from all the tables with the Go defaults for each type.  Then when I lookup the policy it will apply the values from the database over the Go struct defaults.  The challenge with this option is none of the associated records are created unless I refer to a non-null value.
To solve this I created a constructor function to populate at least one non-null value from each table that has a non-null default.
func NewDefaultPolicy(name string) Policy {
	policy := Policy{
		Name:    name,
		Ruleset: Ruleset{RecommendedDisable: true},
		Other:        SomeOtherTable{SomeOtherBool: true},
	}
	return policy
}

I would have been a lot cleaner if db.Create() had an option to automatically create all associated records that have non-null values.


Flow configuration validation

Disable flow runs if configuration doesn't pass validation
Show users validation status & show authors validation details on flow submission page

This should probably be done on the backend: validation logic can be exposed via an ad-hoc Django endpoint, with re-validation occurring whenever whenever flow details are queried.

1bc87ab


Parallel autodiff v2 RFC

This RFC introduces the basic design elements needed to evaluate functions with parallelism during reverse mode autodiff of stan-math.
The RFC aims to introduce

parallel reduce
parallel map

to stan math on the basis of the Intel TBB library. To achieve this, the RFC intends to

refactor the AD tape to allow using multiple processes
refactor nested AD to be compatible with parallelism

A lot of discussions on the topic have taken place in 2019. Here are some links to previous discussions:

Initial PR of first RFC, see here
Parallel autodiff v2 discourse  discussion
Performance evaluation of a prototype on discourse

In contrast to the first RFC, this version now tries to spell out more clearly the requirements needed. Moreover, the Intel TBB is taken for granted as it is now in stan-math.
A rendered version can be found here.

@SteveBronder is your comment related to the current version? The comment is dated May 29th...

Nope! dunno why it was there

While this PR would still be of interest to progress along, there is now an alternative approach available which enables parallelism without refactoring the AD tape (at the cost of some flexibility):
See here:
https://discourse.mc-stan.org/t/parallel-autodiff-v3/12474/22
So we can probably put the review of this at rest for the moment being.

Let's close this one.


Linux armv7 support

On linux/armv7 some symbols are not properly prefixed. Building a project that includes both swift-nio-ssl and swift-crypto, results in the following conflicts:
ld.lld: error: duplicate symbol: CRYPTO_poly1305_init_neon
ld.lld: error: duplicate symbol: CRYPTO_poly1305_update_neon
ld.lld: error: duplicate symbol: CRYPTO_poly1305_finish_neon
ld.lld: error: duplicate symbol: openssl_poly1305_neon2_blocks
ld.lld: error: duplicate symbol: openssl_poly1305_neon2_addmulmod
ld.lld: error: duplicate symbol: vpaes_encrypt_key_to_bsaes
ld.lld: error: duplicate symbol: vpaes_decrypt_key_to_bsaes
ld.lld: error: duplicate symbol: sha512_block_data_order_neon
ld.lld: error: duplicate symbol: sha256_block_data_order_neon
ld.lld: error: duplicate symbol: bsaes_cbc_encrypt
ld.lld: error: duplicate symbol: bsaes_ctr32_encrypt_blocks
ld.lld: error: duplicate symbol: x25519_NEON
ld.lld: error: duplicate symbol: CRYPTO_has_broken_NEON
ld.lld: error: duplicate symbol: CRYPTO_needs_hwcap2_workaround

It looks like CCryptoBoringSSL_boringssl_prefix_symbols.h is generated by vendor-boringssl.sh by building BoringSSL for various architectures and gathering all symbols. There is no official linux/armv7 docker image yet, so at the moment we can't use the same method for adding these symbols, but would it be possible to create a temporary solution, for example by hardcoding these symbols? Or is there any proper solution that could work without requiring an official linux/armv7 docker?

I'd be open to an unofficial docker image, but I don't think hardcoding the symbols themselves is going to work. Another option might be to produce a cross-compilation SDK that supports an armv7 toolchain, which we could then integrate. @MaxDesiatov might be able to help with that.

Swift SDKs can be generated from existing toolchains. Thus we need an armv7 toolchain first to run the generator on it.

We don't have a full toolchain for armv7, but we do have a cross-compiling toolchain (Swift 5.10). This was created with something based on the swift-armv7 repo. However, it is for our own Yocto based system. We can have a look at creating a container image with a cross-compiling toolchain for Debian. This should be usable with the vendor-boringssl.sh script. I guess it will not work well with the SDK generator, though.

Ideally we'd have either a suitable docker container or a toolchain, I don't much mind. Either way we can add that to the build system once we're there.

A container seems like the best option for now. It fits right into the current set-up and takes away some unknowns regarding SDK creation, especially for us being unfamiliar with Swift on MacOS. I submitted a pull request with a container based solution.

Any updates on this? I wonder if the solution provided is not good enough to be used for generating symbols for armv7. Perhaps we can look into generating an SDK that is installable with swift sdk install for example?

I’m currently on vacation so don’t have cycles to review this. But it’s on my to-do list for when I’m back.

Okay, that sounds good. I was going to look to see if we could generate an SDK for Debian armv7 anyways (interested for my own personal projects) so if that is something that would help for this I would be happy to look into it sooner rather than later. We have the ability to build for Debian armv7 and build a docker container, it's just the SDK generation that we don't know how to do yet...

Feel free to submit a PR on the corresponding repo, which already supports a few other distributions that you could use as an example.


Release 1.1.1 has outdated end point

File src/Constants.php  Line number: 28
This https://android.googleapis.com/gcm/send url getting 302.  I think  url should be https://gcm-http.googleapis.com/gcm/send like this

https://github.com/lkorth/php-gcm/blob/master/src/PHP_GCM/Sender.php#L7


Type members are inserted based on their position

This causes major ordering issues for Spork, as the positions often don't add up between files. An easy solution is to unset the source position for type members when building the Spoon tree.

Actually, I think the best solution is to unset the source position of every element.


Request: Ad Blocking

Please add the ability to enable ad blocking. Thank you!
Translated by Google Translate.

Duplicate of #24


Added Ringwood Training domain text file.

read more about us: http://ringwood.training

@nwhitert The first verification stage is complete: the official domain for  Ringwood Training is ringwood.training, to the best of my knowledge. This is just an informational note. The pull request is still under review. The review may take some more time. I greatly appreciate your patience. Here is the proof of domain ownership: https://ringwood.training/

Hello @philipto Thanks for your comments, just to clarify https://ringwood.training/ is our business site which is public. Our emails are handled by rt.vic.edu.au domain, which is what my students will be using to register with to use the Jetbrains suite. This domain is the one I have added to the repository. Is this okay?

@nwhitert Yes, absolutely. It's OK. Thank you for your patience while waiting for a review and processing your request. Pull request merged.

@philipto Thanks 😃


Keystone 4 Roadmap and Maintenance

For background, Keystone 5 is here and we're very excited about it!
However, it's still in alpha, and we don't have a timeline yet for when it will be a comfortable upgrade for people who've built projects on Keystone 4.
So with the future in mind, this issue is for discussing the present, and how we can all shepherd this version of keystone over the next year and support our users.
My proposed plan is this:

Keystone 4 will go into "maintenance" mode; no major refactors or new features will be added (including some WIP features that haven't made it into master yet)
We'll close as many issues and PRs as possible relating to support, feature requests, and things that are out of scope
I'll be putting in time with any contributors who step up to help shepherd bug fixes or minor additions into v4, and manage releases

I think now that Keystone 5 is open, it's reasonable to say that v4 is "feature complete" - if it works for you, that's great! and where there are bugs or minor issues, they should fixed. But in terms of major changes, the core team's attention is on v5 and it is a much more productive project to build new features in.
Long-term project stability is a major concern for Keystone, so if anyone wants to make major changes to v4 to support their own use-case, I believe the best approach would be to fork the project and publish it independently. Major changes in this codebase carry a large risk of breaking other people's projects, and the priority is to keep Keystone 4 stable for everyone using it. We also won't publish any updates that include breaking changes.
npm makes publishing projects under your own scope trivial (for example, I could publish my own fork to @jedwatson/keystone) and if any forks gain significant new features or benefits I'd be happy to point to them in the readme for any other users who want access to those features.
I also want to point out again that while Keystone 5 is not backwards compatible, as it matures we will do our best to provide a good upgrade path for Keystone 4 users.
Help Wanted
For anyone who can help manage the maintenance of Keystone 4, it would be great if you can join the #v4-maintenance channel on our slack and shout out there.
We'll need help:

Closing old issues and PRs that won't be merged, in particular ones that add major features
Identifying meaningful bugs and issues that we should fix, and organising them into a project
Contributing, triaging and reviewing PRs

Being honest, we've had a few false starts maintaining v4 during the development of v5. I'm hoping that by simplifying the scope and being clearer about the workflow we can get some good momentum here and support our v4 community while v5 matures.

Much respect for this post @JedWatson and I think the absolute best step forward. Let's get v4 as bugfree as possible for the people using it right now. I would be happy to help out giving the maintenance mode a fair chance. Limiting the open issues is a good first step, sadly dropping some work, but it has to be done to get v4 forward.

Thanks @JedWatson for the update..  Looking forward to v5!!  Would love to have a chat with you:)

Hi Jed, I'm really sorry to bother you, but there is a bug in Keystone 4 that hasn't been fixed since 2018, and it is still in current version Keystone JS 4.2.1. I don't know how to reopen this issue, but if someone could take a look at this and help fix this bug, me and some other people would really appreciate it.
Here it is: https://github.com/keystonejs/keystone-classic/issues/3374


Adding externalLink to Alert model

It's just that easy!

Fixes: https://github.com/TheHive-Project/TheHive4py/issues/169

Hey ! Is it possible to access this external link when checking related Alerts from a case ?

Hello @yokoulaaa could you create an issue in TheHive to track this feature request? Thanks


Kernel Panic that might be caused by default Jetsam settings

I experienced a kernel panic when trying to switch apps. Only Telegram, Safari and Notability are running in background, but kernel panic just happened. Since I'm using an M1 iPad Pro with 8GB RAM, I believe this has something to do with the 3x Jetsam settings that is default by Dopamine. Plz look into my crash report below.
panic-full-2024-09-15-103701.000.ips.zip

Hi, Can you DM me in discord @nezuko.san

This is a panic caused by a late side effect of smith and landa (kfd kernel exploit), it is unrelated to any setting. It's something that goes wrong sometimes during the jailbreaking process but will only cause a panic much later.

Hi, Can you DM me in discord @nezuko.san

I'd love to but I don't use Discord.


5.1 regression: constraints of generic tuple types are sometimes order-sensitive

Bug Report

🔎 Search Terms

5.1
tuple
array
spread

Possibly related:

https://github.com/microsoft/TypeScript/issues/54048
https://github.com/microsoft/TypeScript/issues/54302

🕗 Version & Regression Information

This changed between versions v5.0.4 and v5.1.3

⏯ Playground Link

I was unable to reproduce: if you could please steer me in the right direction I'm happy to dig more, but I'm a bit stuck on how to debug this
💻 Code

We have an issue using io-ts. If this is a bug with that library, I'll close this here, but I don't think it is.
The TypeScript compiler is complaining about a number of excerpts from the d.ts file, where the compiler doesn't seem to be making sense.
Here's an example error:
node_modules/io-ts/lib/index.d.ts:1151:24 - error TS2344: Type 'CS' does not satisfy the constraint '[Mixed, Mixed, Mixed[]]'.
  Type '[Mixed, Mixed, ...Mixed[]]' is not assignable to type '[Mixed, Mixed, Mixed[]]'.
    Target allows only 3 element(s) but source may have more.

1151 ) => TaggedUnionC<Tag, CS>

The code it's referring to is here:
export interface TaggedUnionC<Tag extends string, CS extends [Mixed, Mixed, ...Array<Mixed>]>
  extends TaggedUnionType<Tag, CS, TypeOf<CS[number]>, OutputOf<CS[number]>, unknown> {}

export declare const taggedUnion: <Tag extends string, CS extends [Mixed, Mixed, ...Mixed[]]>(
  tag: Tag,
  codecs: CS,
  name?: string
) => TaggedUnionC<Tag, CS>

As you can see, the compiler seems to be collapsing the [Mixed, Mixed, ...Array<Mixed>] to [Mixed, Mixed, Mixed[]], which is incorrect. It then doesn't like CS extending [Mixed, Mixed, ...Mixed[]], which it considers incompatible with its incorrect collapsing.
Weirdly, if I tweak the d.ts file by hand, the error goes away:
- export interface TaggedUnionC<Tag extends string, CS extends [Mixed, Mixed, ...Array<Mixed>]>
+ export interface TaggedUnionC<Tag extends string, CS extends [Mixed, Mixed, ...Mixed[]]>

🙁 Actual behavior
Compilation errors
🙂 Expected behavior
Successful compilation

I'm not able to reproduce this error. Can you post a concrete example?

@RyanCavanaugh I tried to put together an MWE but I couldn't figure it out.
For some reason the error only happens with io-ts as a dependency of a dependency. The middle dependency compiles just fine with TS 5.1 and the issue only happens downstream with the transpiled JS and declaration files being used in 5.1.
Do you have any advice on how to get more information from TS, or a good guess at what might be the actual issue for me to narrow my search?

I'd recommend bisecting your situation by removing code from your dependencies, once you minimize this to a minimal repro you might want to just commit node_modules and share that as a repro case.

Okay @RyanCavanaugh @Andarist I've got a minimal repro repo.
Turns out, nothing to do with our code, so either a TS bug, or a bug with another repo (still looks like TS to my uneducated eye, though).
The repro case — in the end — was laughably simple:
import 'mongodb';
import 'io-ts';

☝🏼 this fails to build with a bare-bones tsconfig.json on TypeScript v5.1.3 with the compilation error I mentioned above.
It builds fine on TypeScript v5.0.4.

Please let me know if this is actually a bug with mongodb or io-ts, and I'll move there, but building a project that just depends on one of these  libraries works just fine:
import 'mongodb';
- import 'io-ts';

or
- import 'mongodb';
import 'io-ts';

both work

Also here's the full error dump:
❯ npm run build

><EMAIL_ADDRESS>build
> tsc --pretty

node_modules/io-ts/lib/index.d.ts:771:21 - error TS2344: Type 'CS' does not satisfy the constraint 'Any[]'.
  Type '[Mixed, Mixed, Mixed[]]' is not assignable to type 'Any[]'.
    Type 'Mixed | Mixed[]' is not assignable to type 'Any'.
      Type 'Mixed[]' is not assignable to type 'Type<any, any, any>'.

771   extends UnionType<CS, TypeOf<CS[number]>, OutputOf<CS[number]>, unknown> {}
                        ~~

node_modules/io-ts/lib/index.d.ts:771:32 - error TS2344: Type 'CS[number]' does not satisfy the constraint 'Any'.
  Type 'Mixed | Mixed[]' is not assignable to type 'Type<any, any, any>'.
    Type 'Mixed[]' is missing the following properties from type 'Type<any, any, any>': name, is, validate, encode, and 7 more.

771   extends UnionType<CS, TypeOf<CS[number]>, OutputOf<CS[number]>, unknown> {}
                                   ~~~~~~~~~~

node_modules/io-ts/lib/index.d.ts:771:54 - error TS2344: Type 'CS[number]' does not satisfy the constraint 'Any'.

771   extends UnionType<CS, TypeOf<CS[number]>, OutputOf<CS[number]>, unknown> {}
                                                         ~~~~~~~~~~

node_modules/io-ts/lib/index.d.ts:799:5 - error TS2344: Type 'CS' does not satisfy the constraint 'Any[]'.
  Type '[Mixed, Mixed, Mixed[]]' is not assignable to type 'Any[]'.
    Type 'Mixed | Mixed[]' is not assignable to type 'Any'.
      Type 'Mixed[]' is not assignable to type 'Type<any, any, any>'.

799     CS,
        ~~

node_modules/io-ts/lib/index.d.ts:807:48 - error TS2344: Type 'CS[2]' does not satisfy the constraint 'Any'.
  Type 'Mixed[]' is missing the following properties from type 'Type<any, any, any>': name, is, validate, encode, and 7 more.

807       ? TypeOf<CS[0]> & TypeOf<CS[1]> & TypeOf<CS[2]>
                                                   ~~~~~

node_modules/io-ts/lib/index.d.ts:824:54 - error TS2344: Type 'CS[2]' does not satisfy the constraint 'Any'.
  Type 'Mixed[]' is missing the following properties from type 'Type<any, any, any>': name, is, validate, encode, and 7 more.

824       ? OutputOf<CS[0]> & OutputOf<CS[1]> & OutputOf<CS[2]>
                                                         ~~~~~

node_modules/io-ts/lib/index.d.ts:846:58 - error TS2344: Type '[A, B, C, D, E]' does not satisfy the constraint '[Mixed, Mixed, Mixed[]]'.
  Source has 5 element(s) but target allows only 3.

846 >(codecs: [A, B, C, D, E], name?: string): IntersectionC<[A, B, C, D, E]>
                                                             ~~~~~~~~~~~~~~~

node_modules/io-ts/lib/index.d.ts:850:18 - error TS2344: Type '[A, B, C, D]' does not satisfy the constraint '[Mixed, Mixed, Mixed[]]'.
  Source has 4 element(s) but target allows only 3.

850 ): IntersectionC<[A, B, C, D]>
                     ~~~~~~~~~~~~

node_modules/io-ts/lib/index.d.ts:854:18 - error TS2344: Type '[A, B, C]' does not satisfy the constraint '[Mixed, Mixed, Mixed[]]'.
  Type at position 2 in source is not compatible with type at position 2 in target.
    Type 'C' is not assignable to type 'Mixed[]'.
      Type 'Type<any, any, unknown>' is missing the following properties from type 'Mixed[]': length, pop, push, concat, and 29 more.

854 ): IntersectionC<[A, B, C]>
                     ~~~~~~~~~

node_modules/io-ts/lib/index.d.ts:1139:32 - error TS2344: Type 'CS' does not satisfy the constraint 'Mixed[]'.
  Type '[Mixed, Mixed, Mixed[]]' is not assignable to type 'Mixed[]'.
    Type 'Mixed | Mixed[]' is not assignable to type 'Mixed'.
      Type 'Mixed[]' is missing the following properties from type 'Type<any, any, unknown>': name, is, validate, encode, and 7 more.

1139   extends TaggedUnionType<Tag, CS, TypeOf<CS[number]>, OutputOf<CS[number]>, unknown> {}
                                    ~~

node_modules/io-ts/lib/index.d.ts:1139:43 - error TS2344: Type 'CS[number]' does not satisfy the constraint 'Any'.
  Type 'Mixed | Mixed[]' is not assignable to type 'Type<any, any, any>'.
    Type 'Mixed[]' is not assignable to type 'Type<any, any, any>'.

1139   extends TaggedUnionType<Tag, CS, TypeOf<CS[number]>, OutputOf<CS[number]>, unknown> {}
                                               ~~~~~~~~~~

node_modules/io-ts/lib/index.d.ts:1139:65 - error TS2344: Type 'CS[number]' does not satisfy the constraint 'Any'.

1139   extends TaggedUnionType<Tag, CS, TypeOf<CS[number]>, OutputOf<CS[number]>, unknown> {}
                                                                     ~~~~~~~~~~

node_modules/io-ts/lib/index.d.ts:1151:24 - error TS2344: Type 'CS' does not satisfy the constraint '[Mixed, Mixed, Mixed[]]'.
  Type '[Mixed, Mixed, ...Mixed[]]' is not assignable to type '[Mixed, Mixed, Mixed[]]'.
    Target allows only 3 element(s) but source may have more.

1151 ) => TaggedUnionC<Tag, CS>
                            ~~

Found 13 errors in the same file, starting at: node_modules/io-ts/lib/index.d.ts:771

This can be bisected to this PR https://github.com/microsoft/TypeScript/pull/53672 , cc @ahejlsberg
That being said, this isn't quite a minimal repro case 😉 mongodb and io-ts have a lot of types and it might take a while for somebody to actually reduce this.
Note that reordering those 2 imports also fixes the issue so it's likely a caching bug in the compiler. Things are cached for performance reasons and unfortunately, sometimes issues like this pop up and at times it's hard to fix them. Ideally, the order of declarations shouldn't matter but in practice, it sometimes might.

Maybe something like: "5.1 regression: constraints of generic tuple types are sometimes order-sensitive"

Okay I spotted something as I was skimming the MongoDB type declarations, and it looks like if you comment out this suspicious-looking type (and things that depend on it), everything compiles just fine.
I've pushed the result to the above repo as a new branch: commented-deps
Is this a TypeScript bug or a MongoDB bug?

@Andarist @ahejlsberg this is still broken in 5.1.5. Should it be fixed?

It seems that the fix was supposed to be cherry-picked into 5.1 but the automated job failed, see the comment here. cc @DanielRosenwasser @jakebailey

I just sent #54814 to cherry-pick it by hand. Unfortunate; I totally read that notification in my email but I figured it was already handled...


Error running "vagrant up", M1 MacBook running Big Sur (NS_ERROR_FAILURE)

Issue Type

Bug Report / Support Request

Your Environment
Vagrant 2.2.15
VirtualBox 6.1.18r142142
zsh: command not found: ansible
Your OS

macOS (11.2.3)

Full console output
There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["hostonlyif", "create"]
Stderr: 0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to create the host-only adapter
VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage: error: Context: "RTEXITCODE handleCreate(HandlerArg *)" at line 95 of file VBoxManageHostonly.cpp
Summary
Hi Everyone,
I'm trying to get Drupal VM up and running on a new M1 MacBook running Big Sur and I'm running into an issue :(
Googling the error I pasted above that I recieve when running vagrant up points me to a load of issues where people suggest navigating to "System Preferences > Security & Privacy" and granting VirualBox certain privileges on install, but I was not asked to grant any.
Other suggestions I've seen talk about disabling SIP within MacOS, but I'm thinking that there surely must be a better way to get round this issue.
Any help with this is greatly appreciated!

VirtualBox does unfortunately not work on the M1 chip and might never work https://forums.virtualbox.org/viewtopic.php?f=8&t=100839.
Parallels and VMWare might already have support but currently Drupal VM doesn't directly support those.

Or @geerlingguy what's the status for using Parallels or VMware with Drupal VM?

@oxyc - I used to build VMware fusion base boxes, but because the plugin for Vagrant cost money, along with the license required for VMware to run on my Mac, I found myself paying over $200/year for something I didn't use outside of 'trying to help other people who use it', so it was not worth it to me to keep maintaining/uploading two boxes in parallel.
I wouldn't do anything to hinder support for the other platforms, and most of the configuration would work just the same with another tool, but honestly I have been using Drupal VM a lot less these days (only one personal project is still running on it), and though I don't yet have an M1 Mac (still waiting to see what the 2nd iteration looks like), I've been leaning on native Docker-based environments more :(

We're still heavily using Drupal VM for our WordPress sites (😄) and the few with M1 laptops use ddev for docker environments which works very well. Personally I'm patiently waiting for an invite to GitHub codespaces to see if we can get rid of local environments entirely :)

VirtualBox does unfortunately not work on the M1 chip and might never work https://forums.virtualbox.org/viewtopic.php?f=8&t=98742.
Parallels and VMware might already have support but currently Drupal VM doesn't directly support those.

Urgh! I hadn't even considered the CPU being the issue - I'd assumed it was yet another MacOS quirk.
Thanks for your help anyway @oxyc & @geerlingguy


Can't see diff for raw ipynb files

Bug: Notebook Editor
Steps to cause the bug to occur

Track a valid .ipynb file in git
Makes changes to the file on a another branch
Checkout a new branch and make changes to the file
Attempt to merge the file, creating a conflict
From the VCS view, click on the ipynb file to view conflicts

Actual behavior
Opens the Notebook Editor
Expected behavior
Show the git diff of the raw ipynb file

Your Jupyter and/or Python environment

Question
Answer

Jupyter server running:
Local

Extension version:
2020.2.64397

VS Code version:
1.42.1

Setting python.jediEnabled:
true

Python and/or Anaconda version:
3.7.6 64-bit

OS:
Linux (Ubuntu 18.04)

Virtual environment:
conda

Developer Tools Console Output
-1582709663883.log
Microsoft Data Science for VS Code Engineering Team: @rchiodo, @IanMatthewHuff, @DavidKutu, @DonJayamanne, @greazer

Thank you for letting us know.
I've tried it and I can see this also happens on windows, we'll get to it.

Dup of https://github.com/microsoft/vscode-python/issues/9395


style(coral): Add custom theme

About this change - What it does

Adds custom klaw theme with DS variables (recommended way)

Resolves: #1312
Screenshots
I tried to make screenshots from all views.

trie

❓ ❓ ❓  how can there be test failing 😭  Will check it out!

😭  it was me. I tried around with a potential different styling in Modal and added a "HU" to the text to see that I'm at the right button... and forgot to remove it 🤦♀
Tests, again, saved me ❇ 🙇
Removed, all ✅  locally and pushed the change!


Features to Enable Tornado Chart

We have a requirement to build a tornado chart. PPT has the ability to do this, but it requires customizing a typical bar chart series. This PR additionally has some general features.

catAxisLabelPos:  By default the labels on the tornado chart will be on the 0 axis line. This allows for low (left) and high (right)
valAxisLineShow: Setting to false will hide the axis line (defaults true)
axisLineColor: color of axis lines
gridLineColor: color of grid lines (no features were added to handle line styles)
invertedColors: This is a list of colors, much like chartColors. These are applied if the value is less than zero. PPT defaults to white.
valueBarColors: Forces chartColors on multi-data-series. This is kind of a special switch that was specific to tornado charts. Not sure if it has any other use cases.

Issue #151 added this code.
Thanks @clubajax !

@gitbrent, your welcome, but I don't see the changes in master?


HTTP/2 uses non-daemon threads

The following one-line program does not close properly on Java 9:
public static void main(String[] args) throws IOException {
    System.out.println(new OkHttpClient.Builder().build().newCall(new Request.Builder().url("https://google.de").build()).execute());
}

It hangs for a very significant amount of time after the request is already finished before it allows the program to quit.
This a little modified version works flawlessly and allows the program to quit immediately after the request is finished.
public static void main(String[] args) throws IOException {
    System.out.println(new OkHttpClient.Builder().protocols(Collections.singletonList(Protocol.HTTP_1_1)).build().newCall(new Request.Builder().url("https://google.de").build()).execute());
}

Running on Java 8 also fixes the problem, as there HTTP 1.1 is used, not HTTP 2.0.
The problem is a hanging non-deamon thread called OkHttp google.de.
Here you have the stacktrace of the thread when the program should quit:
"OkHttp google.de@1876" prio=5 tid=0x11 nid=NA runnable
  java.lang.Thread.State: RUNNABLE
	  at java.net.SocketInputStream.socketRead0(SocketInputStream.java:-1)
	  at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
	  at java.net.SocketInputStream.read(SocketInputStream.java:171)
	  at java.net.SocketInputStream.read(SocketInputStream.java:141)
	  at sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:425)
	  at sun.security.ssl.SSLSocketInputRecord.bytesInCompletePacket(SSLSocketInputRecord.java:65)
	  at sun.security.ssl.SSLSocketImpl.bytesInCompletePacket(SSLSocketImpl.java:918)
	  - locked <0x792> (a java.lang.Object)
	  at sun.security.ssl.AppInputStream.read(AppInputStream.java:144)
	  - locked <0x793> (a sun.security.ssl.AppInputStream)
	  at okio.Okio$2.read(Okio.java:140)
	  at okio.AsyncTimeout$2.read(AsyncTimeout.java:237)
	  at okio.RealBufferedSource.request(RealBufferedSource.java:68)
	  at okio.RealBufferedSource.require(RealBufferedSource.java:61)
	  at okhttp3.internal.http2.Http2Reader.nextFrame(Http2Reader.java:95)
	  at okhttp3.internal.http2.Http2Connection$ReaderRunnable.execute(Http2Connection.java:608)
	  at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
	  at java.lang.Thread.run(Thread.java:844)

I find it quite strange that this thread is hanging on a socketRead operation, while the request is already finished successfully.

Dupe of #4009?

No, that's a different thread factory with a different name.
And while making the thread a daemon one might solve the issue that it prevents the program from closing, but isn't the real issue that it waits on a socket read while the request is already finished?

That doc you linked talks about daemon threads. If it would be a daemon thread, it would not prevent the JVM from exiting.
If the socket read is by design, then maybe the thread could be daemon?

Actually you should probably only ever use daemon threads in the whole library. I don't think there is any use-case to block JVM exit from OkHttp.

And even if I do the cleanup suggested in what you linked @dave-r12, the behavior didn't change, because of new Thread(readerRunnable).start(); // Not a daemon thread. that creates that non-daemon thread that prevents the JVM from shutting down. while the docs you linked say OkHttp also uses daemon threads for HTTP/2 connections. These will exit automatically if they remain idle. which is not true in this case.

Ultimately, I think what you are hitting is a fundamental part of the design
https://github.com/square/okhttp/issues/1890

Unlike the connection pool, the dispatcher isn't a natural daemon. A simple main program that makes an async request should complete its request!

So there are cases that would merit a bug fix, but assuming a well written program that completes or cancels requests and does proper cleanup should shutdown in a timely manner.  n.b. I've used OkHttp extensively in command line scripting and haven't had an issue with shutdown.  It feels like you want OkHttp to never block your shutdown no matter how it's used, while part of the design is that it should complete valid work, not corrupt cache directories when possible etc.
That readerRunnable thread should complete very quickly after a clean shutdown.  If you can get it to block shutdown even after you cleanly close OkHttp resources, we should definitely fix that.

This program shuts down immediately with Java 9.  The difference is cleanly closing the response also.
import java.io.IOException;
import okhttp3.OkHttpClient;
import okhttp3.Request;
import okhttp3.Response;

public class X {
  public static void main(String[] args) throws IOException {
    OkHttpClient okHttpClient = new OkHttpClient.Builder().build();
    Response response =
        okHttpClient.newCall(new Request.Builder().url("https://google.de").build()).execute();
    System.out.println(response);
    response.close();
    okHttpClient.dispatcher().executorService().shutdownNow();
    okHttpClient.connectionPool().evictAll();
  }
}

Ah, ok, forgot to close the response, yes.
But even with the response closed like
OkHttpClient okHttpClient = new OkHttpClient.Builder().build();
try(Response response = okHttpClient.newCall(new Request.Builder().url("https://google.de").build()).execute()) {
    System.out.println(response);
}

The JVM does not exit.
I have to manually do
OkHttpClient okHttpClient = new OkHttpClient.Builder().build();
try(Response response = okHttpClient.newCall(new Request.Builder().url("https://google.de").build()).execute()) {
    System.out.println(response);
}
okHttpClient.connectionPool().evictAll();

To get it to close properly.
Why do you need to evict the connection pool manually?
This feels somewhat awkward.
Shouldn't the first code have a state of it should complete valid work already?

Well, I'm glad I could help you with closing the sync response.  I'll leave the debate about the connection pool to others.

Yeah, in our realy code the response was closed properly by using a try-with-resources block, that was just faulty test code :-)

When having a long running program where you don't explicitly end the program it is even worse, because you don't know when you have to shutdown OkHttp manually.

Maybe the correct fix is never calling new Thread(...), and we always use a ThreadPoolExecutor which ultimately could be overridden by a motivated enough client.  But the defaults left as is.

I still wonder why by default a non-daemon thread should block on a socket read while the request is properly finished and its response closed.
This doesn't sound like a sensible default to do.

@JakeWharton I'm not familiar with HTTP 2.0 specifics, but is this relevant?
I do a synchronous request to the server.
I close the response.
And then the program should end.
As I said,

it is probably ok that the actual request that is triggered by client code is done in a non-daemon thread as it should be properly finished
it might also be ok to have the socket read waiting for whatever if that is how HTTP 2.0 works
but that waiting should probably be done in a daemon thread instead

Also, what does happen if a server push or something else is sent but the client code is not interested. Does anything actually happen with the data? Maybe the socket read should only be done in a non-daemon thread or done at all if there is actually some consumer for the information?

Server pushes and control frames are not surfaced at the application layer
and are handled entirely inside the client.
On Tue, May 29, 2018 at 9:09 AM Björn Kautler<EMAIL_ADDRESS>wrote:

@JakeWharton https://github.com/JakeWharton I'm not familiar with HTTP
2.0 specifics, but is this relevant?
I do a synchronous request to the server.
I close the response.
And then the program should end.
As I said,

it is probably ok that the actual request that is triggered by
client code is done in a non-daemon thread as it should be properly finished
it might also be ok to have the socket read waiting for whatever if
that is how HTTP 2.0 works
but that waiting should probably be done in a daemon thread instead

Also, what does happen if a server push or something else is sent but the
client code is not interested. Does anything actually happen with the data?
Maybe the socket read should only be done in a non-daemon thread or done at
all if there is actually some consumer for the information?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/square/okhttp/issues/4029#issuecomment-392769508, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAEEEUW62ljHU_i-fPY6pSHRHGwAPOS1ks5t3UiAgaJpZM4UPEoy
.

But should they prevent orderly shutdown of the application?
For waiting whether there might eventually be some server push or control frame?
If you manually evict, they are also not waited for any longer.
Wouldn't it be enough to wait for their eventually arrival on a daemon thread?

@567legodude So that should be working as shown in the example program I gave above.  If you close all responses cleanly as part of processing them, and then shutdown the client (dispatcher and connection pool).  There shouldn't be any threads left hanging around in that case.

I don't interface with okhttp directly. A library I'm using creates the connections.

And that library now does the close explicitly now too as soon as the PR is merged, as it also has a clean exit point @567legodude. The point is, that in many other situations there is not such a clear exit point, like e. g. in my own Bot, so there I would need to forbid HTTP 2.0 or use a different http library than the library I use brings in anyway.
The point is, that a simple three-liner that does the request, outputs the result and closes the result should cleanly exit immediately, without the need to manually evict socket-reading threads.

Unfortunately I don’t think we can change a thread from daemon to non-daemon at runtime. We’d really need to do that to make HTTP/2 work reasonably. Otherwise a program that’s awaiting an async response would exit prematurely.
Another option is to migrate our HTTP/2 work to NIO, which changes the performance tradeoffs: higher latency but more concurrency.

Which is why I suggested never using raw threads. Ultimately any motivated developer could override to get the behaviour they want.

@swankjesse no you cannot change daemonness after the thread is started.
You would needed to either start a non-daemon thread to do the request blocking and then start a new daemon thread (or better one from a thread pool), doing the waiting non-blocking.
Or maybe if it is easier, or if both things need to be done in the same thread, do both in one daemon thread, but at the beginning start a second non-daemon thread. This one would simply wait for a semaphore and die as soon as it toggles and will be toggled as soon as the actual request is finished. It's sole purpose would be to prevent premature exiting of the JVM.

@yschimke of course you can always make the code what you want, at worst with some bytecode rewriting or forking the project.
But I'd prefer the lib to behave nicely by default, as all users would benefit from that. ;-)

@Vampire the discussion is going around in circles.  It seems like you really don't believe that the behaviour is by design and intended to be a sensible default that works for many different client uses. I hope it's clear that I can understand why this behaviour isn't great for you and not ignoring you.  I'm trying to suggest a way that we could allow you to cleanly override the defaults and take on responsibility for any non-standard behaviour e.g. cache corruption in your app.
But I personally find the discussion not very productive anymore and tone a bit sarcastic and will step back.

@yschimke

discussion not very productive anymore

Why not?
Reasonings are told, suggestions are made.
Possibilities are discussed.
I think it still is productive.

and tone a bit sarcastic

If you had this feeling I'm sorry, there was no bit of sarcasm in my post, I meant what I wrote as I wrote it.

It seems like you really don't believe that the behaviour is by design and intended to be a sensible default that works for many different client uses.

Sure I believe that, but also designs can have bugs / flaws.
And unless you want to make it hard for your users, it should be rethought whether this could be improved.
Even the docs say otherwise. They say "with these three calls you can clear up some resources, but you don't need to" and "for HTTP 2.0 there are some daemon threads started".
Nothing suggests that non-daemon threads are started that you have to manuall cancel to get a clean shutdown.
And even if it would be documented, it would still be a design flaw in my eyes, as a program that does one request synchronously and properly closes the response should not need any further action to cleanly shutdown.

I'm trying to suggest a way that we could allow you to cleanly override the defaults and take on responsibility for any non-standard behaviour e.g. cache corruption in your app.

Thanks, but wouldn't it be nicer to have a good behavior that will not corrupt caches?
Also if with overriding the defaults you mean something like making the daemonness configurable, this would help in my situation as I only do synchronous requests, but maybe not for people that do asynchronous requests, which I will probably also switch to now that I know that OkHttp can do it.
Actually there are already three productive suggestions for a solution here, the one @swankjesse suggested and the two I suggested in response.

This was pre-coffee, so maybe I was too sensitive. I’ll leave you all to it.

We can attempt some refactoring internal to Http2Connection to make the reader a daemon. We’ll need to confirm that when we do that, there’s also an application thread so that a program doesn’t exit while it’s waiting for a callback. And it might break if we later change policy on how threads map to sockets.
The daemon / non-daemon APIs are not very helpful here. It’s particularly awkward to unit test that the program won’t exit prematurely, for example.

I experienced this issue while using Retrofit on a command-line application. The workaround I used at the end of my program is:
    // ... Do stuff, injected with Guice
    // Eventually, I have to block to get results of my queries
    val client = factory.injector.getInstance(classOf[OkHttpClient])
    client.dispatcher().executorService().shutdown()
    // End of the entire program

which is a bit clunky. I'd rather just require blocking for async methods that must complete, since that seems more logical to me from a client-side standpoint and also just seems like better practice in general.
Just from skimming the HTTP/2 spec, would it be possible to make an HTTP/2 call only complete when it reaches the "closed" or even just "half-closed (local)" state here? That would mean that clients would have to wait for all HTTP/2 connections to be closed before exiting their program to guarantee that the connections were successful, which makes sense to me.

@magneticflux- one thing that makes this difficult is that we can’t turn a thread from daemon to non-daemon or vice-versa.

I have also run into this problem. Maybe there could just be a method OkHttpClient#shutdown that does all the internal cleanup and also interrupts any current threads? Or shutdown and shutdownNow?
I get that the threads not being daemon threads is a design decision and don't feel versed enough with the matter at hand to argue whether it's a good decision or not. But I want a way to stop the client without worrying to much about its internal workings. Simply shutting down the ExecutorService won't do any good as that will not stop currently running threads so it is not feasible as a workaround.

I have the same issue. I do not use this library directly but it is used by another one that I use. It is not clear how I need to stop this threads.

I am facing the same issue. Are there official guide how to avoid it? Thanks

We have seen the same issue. Our workaround is to set HTTP 1.1 explicitly in the case when HTTP 2 is not mandatory.
OkHttpClient.Builder builder = new OkHttpClient.Builder();
builder.protocols(Arrays.asList(Protocol.HTTP_1_1));

I use okhttp for jwiki under the hood, and I don't allow clients to interact with the underlying OkHttpClient.
I've worked around this hanging issue the same way as @Lewuathe, forcing OkHttpClient to use HTTP 1.1.  Understood that the HTTP/2 implementation is working as designed, but it would be nice to be able to set a flag when building an OkHttpClient that retains the old behavior.

I'm running into this one as well. May I point out that the documentation actually explicitly claims the opposite behaviour:

OkHttp also uses daemon threads for HTTP/2 connections. These will exit automatically if they remain idle.

We built a new TaskRunner abstraction that will allow HTTP/2 threads to be daemons in 4.3.

Fixed.

@swankjesse when will 4.3 be released?

I'm stilling experiencing hanging threads in Java 11. I'm using version 4.4.0.
Is anyone else still seeing this issue?

That's true for my case too. Even after we start using okhttp 4.3.0, the client still hangs with Java 11.
See: https://github.com/prestosql/presto/issues/1169#issuecomment-570786824

PR to use a daemon thread for clients to be consistent for HTTP/2 and HTTP/1.1
#5834

Will be fixed in 4.5.

will this be backported to 3.x?

No.

I still needed the workaround with HTTP1.1 in the latest (4.10.0) version to prevent a dangling JVM


Valid port types on Passive components

I noticed that linting a passive component won't check for invalid input types. Specifically it didn't notice that "input" is invalid for ports and that it should instead be "sync_input"

This rule requires determining the autocoder input file type, which hasn't really been developed yet.  That said, a lot of effort has recently been put into the linter on the feature branch, could you pull that branch and try it out?  You might be able to determine how to write this rule, if you are clever.

Just FYI, I think this changed. input seems to be a valid type now, see https://github.com/nasa/fprime/blob/d4983cb1c42835a85781f711d37becfdb927eb87/Autocoders/Python/schema/default/common_elements.rng#L79-L89
Also see <port name="cmdIn" data_type="Fw::Cmd"  kind="input" role="Cmd"    max_number="1"> in the GpsTutorial.

interesting, I'll have to try that in a new project


update example to use latest image of hello-osiris

Changes can be viewed here https://github.com/tariq1890/hello-osiris/pull/2


Logo doesn't render from code in README

The link to the logo image is broken. Replace with https://raw.githubusercontent.com/nhs-r-community/assets/main/logo/nhsr-logo.svg

I think I messed up the pull request because I did 5 before 4 so I've overwritten the change you made in 4!

That wouldn't be an issue, because I accidentally created a pull request two times!
Sorry for the trouble!
Is everything fixed and up to date now?

Oh I see 😄 I'm a bit muddled too apologies! If you want to update the second url - the one that just appears in the README to be copied that's great. Not to worry if you want to leave it; I can update later if need be. Thanks for having a go though - it's always difficult making that first pull request so thanks for contributing! Much appreciated 🚀

All sorted now 😃 thanks for persevering! Your contribution is really appreciated and I hope you contribute again in the future!


Synchronization issues with L1 (Sepolia) endpoints

Describe the feature request
The Taiko document https://taiko.xyz/docs/guides/run-a-taiko-node suggests to use Alchemy or Infura when setting up the L1 endpoints.
L1_ENDPOINT_HTTP=
L1_ENDPOINT_WS=
This is an issue as there are 100k rate limits when using these free Alchemy or Infura endpoints and sync will NOT complete.
The proposer or prover endpoints would not be able to sync if the L1 endpoints like that of Alchemy and Infura are rate-limited, unable to provide ability to sync.
Describe alternatives you've considered
I tried to use the Public SEPOLIA RPC https endpoint and it resolved my synchronization issues.
L1_ENDPOINT_HTTP=https://rpc.sepolia.org/
Additional context
Another comment that I would like to point out is that there should be a "bootstrap" so that block synchronization would be faster.
Also setting up a separate TAIKO Sepolia archival node is tedious and takes resources from VPS.

Ok I will try this

thanks @zzlnc4 i added this PR: https://github.com/taikoxyz/taiko-mono/pull/14967
in terms of a "bootstrap" node, the simple-taiko-node client will default to syncing from peers (instead of executing each block), and i believe check that again the verified hashes on chain, but i'm not sure.
@davidtaikocha @cyberhorsey do you know if we have a "fast syncing" / "bootstrap" option for node syncing? perhaps similar to the beacon chain fast checkpoint sync that people use on L1?


Revise the profiler examples and documents

Description
The new profiler API uses new arguments and functions and breaks the examples in https://github.com/apache/incubator-mxnet/tree/master/example/profiler. Also the documents in https://mxnet.incubator.apache.org/faq/perf.html need to be updated

@sxjscience I will file a PR to update the latest CPU performance later.

@sxjscience The examples have been updated in https://github.com/apache/incubator-mxnet/pull/10190
The performance has been updated in https://github.com/apache/incubator-mxnet/pull/10761
@sxjscience could you please close the issue?
Thanks


Refactoring for Formatting and Style

@onuralpszr  I am closing my old draft PR here as you have many things in your already. One thing I need to do with this one: I will need to use the same configs that I used here in yours so I will need to review your PR with this intention as well (not only code-wise). Your PR there is a lot valuable and I dont want to miss a single config here such as line length etc. (I can say I thought about it a lot:)) I mean the most efficient line length.)

@mabulgu  yay ! :) and thank you.


How to train custom data??

i have a small dataset with my language and i want to use pretrained model of you to re-train the model with my data. Please help me to solve this problem. Thanks

First, create a LMDB file using the tool mentioned in README.md. Second, modify the alphabet. Enjoy yourself~


Bc compliance

what

BridgeCrew compliance checks fix
readme updated
code clean up
workflows updated

why

To be able to position our modules as standards compliant
Providing explicit note about policy attached directly to user
removed unnecessary providers dependencies
to stay in sync with all repos

references

https://docs.bridgecrew.io/docs/iam_16-iam-policy-privileges-1

/test all

/test all

Status check failed due to Bridgecrew have an issue: Barak Schoster (Bridgecrew): It seems that if we have 2 suppressions on the same file we have a race condition and only one is saved.

Status check failed due to Bridgecrew have an issue: Barak Schoster (Bridgecrew): It seems that if we have 2 suppressions on the same file we have a race condition and only one is saved.


fix (razzle #1704) by adding support for webpack-dev-server v4

Fixes #1704

Updated package.meta.json and packages/razzle-dev-utils/package.json to allow for v3 and v4 of webpack-dev-server
Updated createConfigAsync.js to build the correct devServer config for v3 or v4 based on the extracted version from webpack-dev-server's version from the package.json
Added a new with-webpack-dev-server-v4 example

Will need to test for version there aswell. But do we really have to swap out the client anymore with newer dev server?

released 4.2.1 with module path fix

@chrisdostert reported issues with createSocketURL


Zoom continuously crashes with Video Conference Mute enabled

Microsoft PowerToys version
0.48.1
Running as admin

[X] Yes

Area(s) with issue?
General
Steps to reproduce

In PowerToys, ensure Administrator mode and enable Video Conference Mute with default settings
Ensure the Zoom process is not already running, kill if necessary, then run Zoom
Wait for about 15 seconds
See popup window saying "Zoom Quit Unexpectedly" (screenshot attached)
Dismiss popup by clicking the "Don't Send" button
NOTE: going forward, dismiss popups as they appear
Click the "Join a Meeting" button; it doesn't work
[Optional] Sign in to Zoom. Note that joining a meeting doesn't work. Note that clicking the settings icon does nothing.
Return to PowerToys
Disable "Video Conference Mute"
Return to Zoom
Wait 10 seconds; dismiss popup window if it appears
Note lack of additional popup windows
Note ability to see settings
Note ability to join meeting

I don't have a video camera on my system, but I've installed OBS Studio which creates a software "camera". I don't use it, but Zoom recognizes it and always seems to want to use it. PowerToys, however, doesn't recognize the OBS camera, even when the camera has been started.
PowerToysReport_2021-10-24-14-21-33.zip

.
✔ Expected Behavior
Zoom allows joining meetings and viewing settings. Zoom runs normally without crashing.
❌ Actual Behavior
Zoom quits repeatedly
Other Software
Zoom v5.8.1 for 64-bit Windows
OBS Studio v27.1.3 for 64-bit Windows

I see the same issue, and I don't have a camera attached, too. No OBS Studio.
PowerToys 0.49.1
Zoom 5.8.3 (1581)

I upgraded to Windows 11 and installed PowerToys and then had nothing but issues with Zoom.  I figured it was a Windows 11 issue so I reinstalled all my Graphics and Audio drivers thinking that was the cause but it didn't fix it.  I resorted to using an old Windows 10 machine for my zoom calls (about 6 per day) which was a pain.
I came across this post and it all made sense.  I disabled the "Video Conference Mute" which was enabled by default and now I can attend my Zoom calls.  Thanks OP for posting this issue.

Having a similar issue with GoToMeeting's desktop client.  It will connect and audio is available but the interface goes unresponsive and the cursor is a spinning circle.  Have to click on it and get the "wait or close" error message.  Closing gives a message about there being a problem with GoToMeeting.

cc: @yuyoyuppe

Could you please mention which camera models do you have?

@yuyoyuppe, I do not have a camera.
Microphone Dropdown:

Camera Dropdown:

Could you please mention which camera models do you have?

I have no camera at all and this still happens to me, so I guess it is not related to any camera model.

Confirming this issue on Zoom and Webex. Enabling Video Conference Mute will cause both applications to crash when trying to start a meeting. Disabling Video Conference Mute will allow normal operation.
I also have no video camera attached to my system.

I also do not have a camera.  Running a desktop.

Thank you for the answers, looks like it happens on some machines with no camera attached. We'll investigate.

Can confirm, I usually disable my camera using a switch on my laptop and when I turn off my camera it always crashes. Tried switching on the camera and the app works well again.

Same here: Latest version of Zoom + latest version of PowerToys on a desktop with no camara = Zoom quit unexpectedly.
And once the "Video Conference Mute" was disabled, Zoom works normally again.

@jaimecbernardo / @yuyoyuppe did this happen before .48?  This is something we should prioritize

For anyone affected by this issue: we might require more info.
Could you please go to %temp% dir in explorer and create an empty file named PowerToysVideoConferenceVerbose.flag. Then try launching Zoom/Teams or any other application which is crashing for you.
That should create PowerToysVideoConference_x86.log/PowerToysVideoConference_x64.log in the same %temp% dir.
Just reply to in this thread with those file(s) attached. Thanks!

PowerToysVideoConference_x86.log

PowerToysVideoConference_x64.log

@yuyoyuppe Suggesting to pin this issue.

cc @dedavis6797

Experiencing the same. Additionally, I cannot disable the Video Conference Mute option in the PowerToys UI. The option is greyed out.
OS: Windows 10 Home, 21H1, Build 19043.1348
CPU: AMD Ryzen 9 5900HS with Radeon Graphics
Dual graphics:  AMD Radeon(TM) Graphics & NVIDIA GeForce RTX 3070 Laptop GPU
Three displays running via my laptop, plugged into two external monitors via a USB-C hub.
External 1 (Set as main display): 3840 x 2160 @ 59.997 Hz
External 2: 1920 x 1080 @ 60 Hz
Internal: 2560 x 1440 @ 165 Hz
PowerToysVideoConference_x86.log
PowerToysVideoConference_x64.log

@jboeke thanks for the report. to actually disable the module, you need to launch PT as admin

@jboeke thanks for the report. to actually disable the module, you need to launch PT as admin

Thank you. Administrative mode enable/disable of the Video Conference Mute seems to stop the Zoom crash, even without a webcam attached.

@BlizZard-bot would you mind sharing your camera model?

@BlizZard-bot like, you Zoom in from 2 devices or it is just a USB camera?  If USB, what is the model?

Like @BlizZard-bot, my laptop doesn't have a built-in camera and I use an external camera (USB) when I need one. Enabling PowerToys Video Conference Mute without connecting the camera makes Zoom crash.
In case it helps, I'm using a Logitech V-u0023 webcam.

Also experiencing this issue. Zoom Support has just brought this GitHub Issue to my attention.
Zoom crashes whenever the "Video Conference Mute" is enabled. Zoom operates perfectly fine after turning it off.
Hardware Details: No Camera connected, USB Microphone attached. Running both Zoom and PowerToys in the newest version.
If I can help with any logs, let me know

@jboeke thanks for the report. to actually disable the module, you need to launch PT as admin

Thank you. Administrative mode enable/disable of the Video Conference Mute seems to stop the Zoom crash, even without a webcam attached.

you will have to change the camera input device in the zoom settings for zoom to work properly again.
I can confirm that this issue also persists in Google Meet on Firefox.

One more thing is that this issue also persists in Google Meet on Firefox, where it just crashes the browser.
As for Google Meet on Chrome, when I change the camera in the settings. It displays Camera Failed in the tiny preview window.
PowerToysVideoConference_x64.log
PowerToysVideoConference_x86.log
Processor	       -  Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz   2.70 GHz
Installed RAM  - 16.0 GB (15.9 GB usable)
System type    - 64-bit operating system, x64-based processor
Graphics Card  - GTX 950
Edition             - Windows 10 Home Single Language
Version            - 21H1
Installed on     - 25-Oct-21
OS build         - 19043.1348
Experience      - Windows Feature Experience Pack 120.2212.3920.0
Display           - 1. Primary Display BENQ GW2280

Similar issues with the mouse highlight issue during screen share. Especially when I share hardware accelerated applications like Photoshop.

Similar issues with the mouse highlight issue during screen share. Especially when I share hardware accelerated applications like Photoshop.

hmm you should create a new issue for this i think

Please disable the Enable autocomplete for the search and replace field option, in the PowerRename setting. It stops the Zoom crash.

I disabled the option to start PowerToys as an administrator and the error no longer occurred.

Video conference mute has to be disabled, if you are gonna use the Zoom desktop app. I didn't find any way to use not disabling.
The log files:
PowerToysVideoConference_x64.log
PowerToysVideoConference_x86.log

Issue persists on Zoom 5.8.7 and PowerToys 0.51.1.
I finally stumbled upon this issue from Zoom forums. Symptoms are inability to open settings window and start/join meetings and after some time crash report (Zoom quit unexpectedly).
Unfortunately current solution is to disable VCM

I have also experienced this behaviour with Webex current version <IP_ADDRESS> and Powertoys 0.49.1. Had to uninstall Powertoys and Webex started working as expected. Really want FancyZones back! I also have a desktop with no camera.

I think Video Conference Mute function should be disabled as default.
Users may not notice that Zoom app continuously crashes at startup is in connection with Powertoys.

@jandkw99 you don't need to uninstall, just disabling the "Conference mute" function should be enough.

@jandkw99 you don't need to uninstall, just disabling the "Conference mute" function should be enough.

Thanks for the response. I reinstalled and needed to enable the 'Run as Administrator' before I could disable the Conference Mute function which then allowed me to use FancyZones again! I believe I tested Webex before running as Admin and it was still failing. Seems like the Conference mute function is enabled by default.

Even with VCM disabled, Zoom still crashing.

@bigeuro Disable each functions of Powertoys to identify the cause of crashing.

came here from opening a case with Zoom. Zoom was crashing constantly and unable to join meetings (as indicated above). During this entire time, I did not have PowerToys running. Zoom's engineers told me to disable "Video Conference Mute" then re-installing Zoom, which I questioned since I wasn't running PowerToys during this entire time. After running PowerToys, then disabling "Video Conference Mute", zoom stopped crashing.
*I do not have a Webcam attached to this computer
After reading through this thread, I performed some additional tests.

Made sure PowerToys was not running. (ran Get-Process *power* and nothing was returned)
Created the file PowerToysVideoConferenceVerbose.flag, and the two log files were instantly created. (If PowerToys isn't running, then what other process is monitoring for this file, and could this be interferring with Zoom even when PowerToys isn't running?
Ran Zoom app
app ran for a few seconds, then the traditional "Zoom quit unexpectedly" shows up
Exited Zoom app
Ran PowerToys as admin
Disabled "Video Conference Mute"
Exited PowerToys
Ran Zoom again, this time no crashing issues.

Attached the two logs files as requested. I'm sure I'm not thinking of the entire PowerToys stack, but if it's not running at all, then shouldn't it not be interfering with Conferencing apps?
PowerToysVideoConference_x64.log
PowerToysVideoConference_x86.log

@Zxurian thank you for the report. We register virtual camera device upon installing PowerToys, that's why it could interfere even when the process is not running.

@yuyoyuppe Do you know why PowerToys are still installed with "Conference mute" enabled by default? I hoped that this issue reported by a lot of people is big enough proof, that there is a bug in this feature affecting many users. So leaving it disabled by default till the solution is found would be easy and fast workaround.

@johny-mnemonic thanks for the suggestion! we actually will disable it by default starting from the next release.

Hi, after several uninstalls and crashes I've figured out this was the problem. Disabling it as default, and warning the user some about "potential crashes can happen if no other camera is available system-wide when using third party apps like zoom, etc.." can be a really nice addition.

Installed latest v0.53.1 build and seems to be much much happier. Zoom functionality is working as expected.

Installed latest v0.53.1 build and seems to be much much happier. Zoom functionality is working as expected.

after the update you need to disable video conference mute from powertoys settings

Please disable the ”Enable auto-complete for the search and replace fields” option, in the PowerRename setting. It stops the Zoom crash.
Windows10 21H1 build 19043.1348 PowerToys 0.51.1 Zoom 5.8.6 (2048)

Big Thanks dear friend, this works for me. I have "Video Conference Mute" disabled. Zoom works now as expected :) !!

The was fixed in in 0.55. Head over to https://aka.ms/installpowertoys to try it out


Feature request: get_arr_int in SegmentationMapOnImage to return multiple segmaps

I have a situation where one image has multiple overlapping segmentation maps, and I want to be able to extract the overlapping segmaps after augmentation.
SegmentationMapOnImage allows for multiple, overlapping segmaps to be input as different channels. However, the get_arr_int method of SegmentationMapOnImage squashes the overlapping maps into one channel. Maybe a parameter could be added to this method to allow the user to make it return the individual maps instead?
EDIT: Looking at the source code I see that all segmaps can be simply accessed from the .arr attribute, so perhaps a method isn't really necessary here. But maybe it should still be in the documentation.

Fantastic, that's exactly what I was looking for :)


Print instances in ASG

Hi,
this is not an issue and I am not sure it belongs here, but I could not think of another place for it. I apologise in advance for this "intrusion" in the issues.
I am using this module and I would like to print the IP addresses of the ASG instances - and I know this is a debated topic and it possibly makes relatively little sense, given the dynamic nature of the ASG.
But it would be useful for my use case.
I tried to achieve this in different ways, and now I have the urge to find out more about what I have done wrong, if there is any correct way to do this, and also possibly about the underlying workings of the module.
I think the following is an issue with timing and with the fact that the depends_on is not enough because the value will be available long before the instances are provisioned.
Thanks in advance for any reply/help.
This is how I create the ASG (the AMI is a public Ubuntu).
# Auto scaling group
  image_id      = "ami-xxxxxxx"
  instance_type = "i3.large"
  security_groups = [ "${aws_security_group.ssh-sg.id}" ]
  asg_name                  = "name-asg"
  vpc_zone_identifier       = flatten([module.vpc.private_subnets])
  health_check_type         = "EC2"
  min_size                  = 3
  max_size                  = 3
  desired_capacity          = 3
  wait_for_capacity_timeout = 0
  key_name                  = "key_name"

  tags = [
    {
      key = "Name"
      value = "cassandra-2-3"
      propagate_at_launch = true
    },
    {
      key                 = "Environment"
      value               = "dev"
      propagate_at_launch = true
    },
    {
      key                 = "Project"
      value               = "project_name"
      propagate_at_launch = true
    },
    {
      key = "owner"
      value = "name.surname"
      propagate_at_launch = true
    },
    {
      key = "expirationDate"
      value = "2020-08-31"
      propagate_at_launch = true
    },
    {
      key = "approver"
      value = "name.surname"
      propagate_at_launch = true
    }
  ]
}

Then I do:
# trying to get the ip of the cassandra ASG EC2 instances
data "aws_instances" "asg_instances" {
  instance_tags = {
    # Use whatever name you have given to your instances
    Project = "project_name"
  }
  depends_on = [module.asg.this_autoscaling_group_id]
}

The depends_on is what I have been trying to use to defer this to after the instances are created.
The first time I run this I get (not suprisingly):
Error: Your query returned no results. Please change your search criteria and try again.

  on main.tf line 143, in data "aws_instances" "asg_instances":
 143: data "aws_instances" "asg_instances" {

The second time:
Apply complete! Resources: 0 added, 4 changed, 0 destroyed.

Outputs:

asg_instances-private-ips = [
  "10.0.3.xxx",
  "10.0.1.yyy",
  "10.0.2.zzz",
]
bastion-host-public-dns = somepublic-dns-name
bastion-host-public-ip = xx.xx.xx.xx
default_security_group_id = sg-xxxxxxx
nat_public_ips = [
  "xx.xx.xx.xx",
]
vpc_id = vpc-xxxxxxxxxx

Is there some way to achieve this so that one does not get an error?

hi @bennythejudge - unfortunately this is not something related to this module and I'm honestly not sure how you would do it with ASG instances coming up and down dynamically. closing this issue here, maybe reach out to the terraform group on stackoverflow?