Adding AllowList for Go

Reasons for making this change:
Allowlisting with .gitignore is a technique for dealing with source trees that can have various different untracked local files such as generated output, packages installed through package managers, “working” files, config for individual developers, etc. Rather than trying to come up with some master list of all possible untracked files and add them to .gitignore, it can be easier to start by ignoring everything and then add specific directories back.
I think the requirements for software development are changing and there is a need to offer an alternative to the denylist.
Links to documentation supporting these rule changes:

https://jasonstitt.com/gitignore-whitelisting-patterns
https://github.com/golang/go

Signed-off-by: kuritka<EMAIL_ADDRESS>

【自动回复】
你好，感谢来信，我是陈东升，会尽快阅读并回信。Hello, thank you for your letter. I am Chen Dongsheng. I will read and reply as soon as possible。

Linking previous PR https://github.com/github/gitignore/pull/3870


Files: ipfs.files.stat RPC call missing error handling

Checklist

[x] This is a bug report, not a question. Ask questions on discuss.ipfs.tech.
[x] I have searched on the issue tracker for my bug.
[x] I am running the latest kubo version or have an issue updating.

Installation method
ipfs-desktop
Version
Kubo version: 0.31.0
Repo version: 16
System version: amd64/windows
Golang version: go1.23.2

Config
{
	"API": {
		"HTTPHeaders": {
			"Access-Control-Allow-Methods": [
				"PUT",
				"POST"
			],
			"Access-Control-Allow-Origin": [
				"http://yoghourt-client.localhost",
				"https://apps.crust.network",
				"http://localhost:3000",
				"http://<IP_ADDRESS>:5001",
				"https://webui.ipfs.io"
			]
		}
	},
	"Addresses": {
		"API": "/ip4/<IP_ADDRESS>/tcp/5001",
		"Announce": [],
		"AppendAnnounce": [],
		"Gateway": "/ip4/<IP_ADDRESS>/tcp/8080",
		"NoAnnounce": [],
		"Swarm": [
			"/ip4/<IP_ADDRESS>/tcp/4001",
			"/ip6/::/tcp/4001",
			"/ip4/<IP_ADDRESS>/udp/4001/quic-v1",
			"/ip4/<IP_ADDRESS>/udp/4001/quic-v1/webtransport",
			"/ip6/::/udp/4001/quic-v1",
			"/ip6/::/udp/4001/quic-v1/webtransport"
		]
	},
	"AutoNAT": {},
	"Bootstrap": [
		"/dnsaddr/bootstrap.libp2p.io/p2p/QmNnooDu7bfjPFoTZYxMNLWUQJyrVwtbZg5gBMjTezGAJN",
		"/dnsaddr/bootstrap.libp2p.io/p2p/QmQCU2EcMqAqQPR2i9bChDtGNJchTbq5TbXJJ16u19uLTa",
		"/dnsaddr/bootstrap.libp2p.io/p2p/QmbLHAnMoJPWSCR5Zhtx6BHJX9KiKNN6tpvbUcqanj75Nb",
		"/dnsaddr/bootstrap.libp2p.io/p2p/QmcZf59bWwK5XFi76CZX8cbJ4BhTzzA3gU1ZjYZcYW3dwt",
		"/ip4/<IP_ADDRESS>/tcp/4001/p2p/QmaCpDMGvV2BGHeYERUEnRQAwe3N8SzbUtfsmvsqQLuvuJ",
		"/ip4/<IP_ADDRESS>/udp/4001/quic-v1/p2p/QmaCpDMGvV2BGHeYERUEnRQAwe3N8SzbUtfsmvsqQLuvuJ",
		"/ip4/<IP_ADDRESS>/tcp/50665/p2p/QmSQgwDz5RbaY8mMCNCfNmwJfTikLWKWRTwFh1cG5mNPfK"
	],
	"DNS": {
		"Resolvers": {}
	},
	"Datastore": {
		"BloomFilterSize": 0,
		"GCPeriod": "1h",
		"HashOnRead": false,
		"Spec": {
			"mounts": [
				{
					"child": {
						"path": "blocks",
						"shardFunc": "/repo/flatfs/shard/v1/next-to-last/2",
						"sync": true,
						"type": "flatfs"
					},
					"mountpoint": "/blocks",
					"prefix": "flatfs.datastore",
					"type": "measure"
				},
				{
					"child": {
						"compression": "none",
						"path": "datastore",
						"type": "levelds"
					},
					"mountpoint": "/",
					"prefix": "leveldb.datastore",
					"type": "measure"
				}
			],
			"type": "mount"
		},
		"StorageGCWatermark": 90,
		"StorageMax": "50GB"
	},
	"Discovery": {
		"MDNS": {
			"Enabled": false
		}
	},
	"Experimental": {
		"FilestoreEnabled": false,
		"GraphsyncEnabled": false,
		"Libp2pStreamMounting": false,
		"OptimisticProvide": false,
		"OptimisticProvideJobsPoolSize": 0,
		"P2pHttpProxy": false,
		"StrategicProviding": false,
		"UrlstoreEnabled": false
	},
	"Gateway": {
		"APICommands": [],
		"DeserializedResponses": null,
		"DisableHTMLErrors": null,
		"ExposeRoutingAPI": null,
		"HTTPHeaders": {},
		"NoDNSLink": false,
		"NoFetch": false,
		"PathPrefixes": [],
		"PublicGateways": null,
		"RootRedirect": ""
	},
	"Identity": {
		"PeerID": "12D3KooWByJZpoKikf5iBccdcgiBm3dCwrxVqgqhJyEXcpQczvrM"
	},
	"Import": {
		"CidVersion": 1,
		"HashFunction": null,
		"UnixFSChunker": null,
		"UnixFSRawLeaves": null
	},
	"Internal": {},
	"Ipns": {
		"RecordLifetime": "",
		"RepublishPeriod": "",
		"ResolveCacheSize": 128
	},
	"Migration": {
		"DownloadSources": [],
		"Keep": ""
	},
	"Mounts": {
		"FuseAllowOther": false,
		"IPFS": "/ipfs",
		"IPNS": "/ipns"
	},
	"Peering": {
		"Peers": [
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/tcp/56620",
					"/ip4/<IP_ADDRESS>/tcp/57747"
				],
				"ID": "QmSQgwDz5RbaY8mMCNCfNmwJfTikLWKWRTwFh1cG5mNPfK"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/tcp/4001"
				],
				"ID": "12D3KooWEJGDnMetpYjteWgsSpeCTLWu77aC1xWb6uAcAYkEwTCZ"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/tcp/4001",
					"/ip4/<IP_ADDRESS>/tcp/4001"
				],
				"ID": "QmdAZQGPofcXyQEndX6ecUX35PvMbkNBWp3fHaAUmu8gDB"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/tcp/4001"
				],
				"ID": "12D3KooWR9KqhHNLjzMhJAoKHvuJyE5txN48gadT8KYfXMRgUKef"
			},
			{
				"Addrs": [
					"/ip6/2a02:c207:2025:4934:cc95::11/tcp/4001"
				],
				"ID": "QmNg3hGN3EsmSxvtWwn4EAPZTtYsgMtkjfUtzqbwYPUiQA"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/tcp/4001"
				],
				"ID": "12D3KooWKKa6v7YTTyTCn7nHfq7erKihRCX7JQc8JezSfVn6Egka"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/tcp/4001"
				],
				"ID": "12D3KooWFdF9yiZHFtya2r6rNLhDT4rn2dsKK43dy2u7jEsbxTMc"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/tcp/4001"
				],
				"ID": "12D3KooWPQZYa7B4CiaDrmVAnqWBH6mySG9p1yWAEc4dpXmCmdQR"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/tcp/4001"
				],
				"ID": "12D3KooWD2njaJAHqx5eSzWi82aDmKvuU6tTB1o6CCTUdzyBMMHZ"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/tcp/4001"
				],
				"ID": "12D3KooWBFccr338AUta4m4hSuyDYFSctcoqG6rwH26SoZ3hTMyb"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/tcp/4003"
				],
				"ID": "12D3KooWPyzih1mhsCsAtEYSj1sSZj2ZgLoxGHrEihCzkdGyET4y"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/tcp/4001"
				],
				"ID": "12D3KooWNKb7KyP4Y9p5qCqkpC5Qo65baCkfCdFrEgNzLsm6vfxF"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/tcp/35371"
				],
				"ID": "QmdAwGXkbdGspCh3vFFXrzrancsJVqyo2ADRbtRn98roaK"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/tcp/4001"
				],
				"ID": "12D3KooWRUMTw53pKr5nvcdq1oANoL9zs9AbcnjJXqPaZaNWc16d"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/tcp/4001"
				],
				"ID": "12D3KooWCBViMDdXaNQj8aiW2MDNdokL2YZp8cm4Lhqea5ijuJ86"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/udp/4001/quic-v1/p2p/12D3KooWQdvwupHorPNSYYLVRx6bgkVnoaSyh9TPfUVKy9CVdGiG/p2p-circuit"
				],
				"ID": "12D3KooWSX2u3CkGsZGv2z9GC2Qy7k81puTuCEwxk7YFWv72nB96"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/udp/4001/quic-v1"
				],
				"ID": "12D3KooWG1rR2yND8c2BpzAzj5c3VeMUFDYFqaPRfXe87w53tDFB"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/udp/4001/quic-v1"
				],
				"ID": "12D3KooWApupf1YgyWo79HiVYa6oQhVa2C2WSh4PCiEK5zHvpWpH"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/udp/4001/quic-v1"
				],
				"ID": "12D3KooWM4AmaKS94S37pGcaKEzTgAGfkX52DD9uNfWV5xfdZHrB"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/udp/4001/quic-v1"
				],
				"ID": "12D3KooWGBrvR2s4D6rPKrZDjV8ZWuugckivj3S85epDus8CrSBY"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/udp/4001/quic-v1"
				],
				"ID": "12D3KooWGS6Q9JU6qsXHokCeLdtK6p7UHD6i1AvKU7oPVXPahF39"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/tcp/4001/quic",
					"/ip4/<IP_ADDRESS>/tcp/4002/quic-v1"
				],
				"ID": "12D3KooWNAiACKeJJuNcfQoyzn6Tp8Nj17hZgskr3RLkyk5bGuem"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/udp/14001/quic",
					"/ip4/<IP_ADDRESS>/tcp/14001"
				],
				"ID": "12D3KooWM8tFisVaU1jLcjkCmjhkeM2X5ruB9i3khXojdY3rdmhv"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/tcp/4001",
					"/ip6/2001:19f0:4400:7f6b:3eec:efff:fe30:4ed6/tcp/4001",
					"/ip4/<IP_ADDRESS>/udp/4001/quic",
					"/ip6/2001:19f0:4400:7f6b:3eec:efff:fe30:4ed6/udp/4001/quic",
					"/ip6/64:ff9b::2d4d:fbfa/tcp/4001"
				],
				"ID": "12D3KooWAEw4RBa1oRyqMXUCzyAbwgvDduRFvi1KzaahSb5Pk61q"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/udp/4001/quic",
					"/ip4/<IP_ADDRESS>/tcp/4001",
					"/ip4/<IP_ADDRESS>/tcp/14001",
					"/ip4/<IP_ADDRESS>/udp/5523/quic",
					"/ip4/<IP_ADDRESS>/tcp/20049",
					"/ip4/<IP_ADDRESS>/udp/7438/quic"
				],
				"ID": "12D3KooWDbPeYWubpE2tyDs3Gp7UgNGmHRgMvyALRNCeL3s77fgv"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/udp/4001/quic",
					"/ip4/<IP_ADDRESS>/tcp/14001",
					"/ip4/<IP_ADDRESS>/tcp/4001",
					"/ip4/<IP_ADDRESS>/tcp/4001",
					"/ip4/<IP_ADDRESS>/udp/4001/quic",
					"/ip4/<IP_ADDRESS>/tcp/14001"
				],
				"ID": "12D3KooWMcAHcs97R49PLZjGUKDbP1fr9iijeepod8fkktHTLCgN"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/tcp/4001",
					"/ip4/<IP_ADDRESS>/udp/4001/quic",
					"/ip6/2605:f700:43:6000::586/tcp/4001",
					"/ip6/2605:f700:43:6000::586/udp/4001/quic",
					"/ip4/<IP_ADDRESS>/tcp/4001",
					"/ip4/<IP_ADDRESS>/udp/4001/quic"
				],
				"ID": "12D3KooWKv5DWMXUb79VfqXUhpvcmnpzvTMJzCNXoGnj7gRwcCni"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/tcp/14001",
					"/ip4/<IP_ADDRESS>/udp/14001/quic"
				],
				"ID": "12D3KooWLy8E6LdKv787Phn7ay6aCbrGWuTZVoFJVZd9eYa9X4Ed"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/tcp/4001",
					"/ip4/<IP_ADDRESS>/udp/4001/quic"
				],
				"ID": "12D3KooWAxiBec7xtxH4DoSfxMkNCqx6we7fNAE6efVc9jijUvmR"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/udp/4001/quic",
					"/ip4/<IP_ADDRESS>/tcp/4001"
				],
				"ID": "12D3KooWT1idFLb714FzYDHknoqKewSEhk2P4xzZZ457QN96Pcad"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/tcp/4001",
					"/ip4/<IP_ADDRESS>/udp/4001/quic"
				],
				"ID": "12D3KooWHBC219eBsHhXnbKHzh6sg2o2jZ9xMtdePbf411zR1w7J"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/udp/4001/quic",
					"/ip4/<IP_ADDRESS>/tcp/4001"
				],
				"ID": "12D3KooWSqf1QsBsgtwKgLZyEkouEwxcfoQSNyQt99539Tq4bY1t"
			},
			{
				"Addrs": [
					"/ip6/64:ff9b::df6f:94c4/tcp/4001",
					"/ip4/<IP_ADDRESS>/tcp/4001",
					"/ip4/<IP_ADDRESS>/udp/4001/quic"
				],
				"ID": "12D3KooWPDDjPuURTNYD2FcdQ5m6oPMevzx8PJLVHBpNZXvpyVcf"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/tcp/4001",
					"/ip4/<IP_ADDRESS>/udp/4001/quic"
				],
				"ID": "12D3KooWQedzx8VGDqaNp2yekWjiHSk3LyGYnTVwruvLP5MZ52Pr"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/tcp/4001",
					"/ip4/<IP_ADDRESS>/udp/4001/quic-v1",
					"/ip4/<IP_ADDRESS>/udp/4001/quic/p2p/12D3KooWAUnz8bi9kbfQMm7dBwCie3NDoXWNqxEnXnRuYTnrkExa/p2p-circuit"
				],
				"ID": "12D3KooWDbcoJ4fxP1Npnea7ocMmJox9UBi6LBhTZSkcDsjUqqVN"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/udp/4001/quic-v1"
				],
				"ID": "12D3KooWPD1eHprh9gocRWsKnaSzjCzRnuzExpH5b3zuDLgF2SAD"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/tcp/4001"
				],
				"ID": "12D3KooWGQg5ehq5sjAJMNQhWEYKeHPL5Fg6UM1iEBNEJ7myHjtj"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/udp/4001/quic-v1"
				],
				"ID": "12D3KooWA2d7YN6bpnHStaMiH1Mjut9cf6jXsGJvynfMNQfH9xke"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/udp/4001/quic-v1"
				],
				"ID": "12D3KooWRrzdcAqucYFbvWL3LodyDBH5p43JScKqfrbxkPn3skQP"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/tcp/4001"
				],
				"ID": "12D3KooWBhjChj4vbxPUgcL924Qv86hG7zwtmwD5tmcNvuk67gEb"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/udp/4001/quic-v1"
				],
				"ID": "12D3KooWKvmNWtbs7Pzok25XTUC2zr4suz6nF5p9jZUYeTiup5Wb"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/udp/4001/quic-v1"
				],
				"ID": "12D3KooWBXuYsNUdPphg9YumyFZBXbnEBtys6jvYBCzzd8zcu7cw"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/udp/4001/quic-v1"
				],
				"ID": "12D3KooWEW9ss3oEW8Gmkgpeq1CX9CXHF71KDvRTUqvzCJL7uDfj"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/udp/4001/quic-v1"
				],
				"ID": "12D3KooWAziziirFEEkrBMfgsJGpvf8ggYMm2MourMYRnRgZtc3f"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/tcp/30402"
				],
				"ID": "12D3KooWNVTNbp7khaUgJZmanLhriV49d9uwWmqYCufLHuh6saY8"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/udp/4001/quic-v1"
				],
				"ID": "12D3KooWKrL2is8r6uAHtkjpS8jjg3uRVw9t4U24LgTppKG36d6v"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/udp/4001/quic-v1"
				],
				"ID": "12D3KooWG4f3aw33NVdZkQBhB4E613xA3paKvChNYJ2Z5enxxrFe"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/tcp/24001"
				],
				"ID": "12D3KooWQh3ZXzp1q3BqKAqozukjA8aN7a4PpR3CEjFG62Qb6z4u"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/udp/4001/quic-v1"
				],
				"ID": "12D3KooWL9DN8DxULnDs1hDonThrtMU5QmM5WVUBpVabH622J3eP"
			},
			{
				"Addrs": [
					"/dnsaddr/bootstrap.libp2p.io"
				],
				"ID": "QmNnooDu7bfjPFoTZYxMNLWUQJyrVwtbZg5gBMjTezGAJN"
			},
			{
				"Addrs": [
					"/dnsaddr/bootstrap.libp2p.io"
				],
				"ID": "QmQCU2EcMqAqQPR2i9bChDtGNJchTbq5TbXJJ16u19uLTa"
			},
			{
				"Addrs": [
					"/dnsaddr/bootstrap.libp2p.io"
				],
				"ID": "QmbLHAnMoJPWSCR5Zhtx6BHJX9KiKNN6tpvbUcqanj75Nb"
			},
			{
				"Addrs": [
					"/dnsaddr/bootstrap.libp2p.io"
				],
				"ID": "QmcZf59bWwK5XFi76CZX8cbJ4BhTzzA3gU1ZjYZcYW3dwt"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/tcp/4001",
					"/ip4/<IP_ADDRESS>/udp/4001/quic-v1"
				],
				"ID": "QmaCpDMGvV2BGHeYERUEnRQAwe3N8SzbUtfsmvsqQLuvuJ"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/udp/4001/quic-v1"
				],
				"ID": "12D3KooWCYsGsPKHDYzn9hUPruV4JEkbpDHkH5oP3eexj6PnR5R6"
			},
			{
				"Addrs": [
					"/ip4/<IP_ADDRESS>/tcp/4001"
				],
				"ID": "12D3KooWQBHnsFP1ZVA99dNTPeZSntoidbPk9iXkMY3Z79LJd21H"
			}
		]
	},
	"Pinning": {
		"RemoteServices": {
			"Filebase": {
				"API": {
					"Endpoint": "https://api.filebase.io/v1/ipfs"
				},
				"Policies": {
					"MFS": {
						"Enable": true,
						"PinName": "",
						"RepinInterval": ""
					}
				}
			}
		}
	},
	"Plugins": {
		"Plugins": null
	},
	"Provider": {
		"Strategy": ""
	},
	"Pubsub": {
		"DisableSigning": false,
		"Router": ""
	},
	"Reprovider": {},
	"Routing": {
		"AcceleratedDHTClient": true,
		"Methods": null,
		"Routers": null
	},
	"Swarm": {
		"AddrFilters": null,
		"ConnMgr": {
			"GracePeriod": "5m0s",
			"HighWater": 5000,
			"LowWater": 2000,
			"Type": "basic"
		},
		"DisableBandwidthMetrics": false,
		"DisableNatPortMap": false,
		"RelayClient": {},
		"RelayService": {},
		"ResourceMgr": {},
		"Transports": {
			"Multiplexers": {},
			"Network": {},
			"Security": {}
		}
	},
	"Version": {}
}

Description
As shown in the figure, when I import a file of 4EiB or larger into a folder that already contains a 4EiB file, the WebGUI file interface becomes unusable. Restarting the IPFS kubo resolves the issue.
cid:bafybeie6tqsijf7j6gpow5q3qdjmtqgscrmd2ijl4olpxanbbptmvh7sui
If someone maliciously shares such CIDs, it could cause others to be unable to use IPFS normally.

Thank you for reporting, I think we are missing error handling in ipfs.files.stat call.
Namely, if it returns Type: error we should display a toast notification with Message:

When importing files, IPFS kubo may not check the size of files and folders, but this issue has been categorized under IPFS WebUI.

Can you assign me this issue? I would love to resolve this!

Can you assign me this issue? I would love to resolve this!

How should I proceed?

Can you assign me this issue? I would love to resolve this!

How should I proceed?

You can proceed by assigning this issue to me in assignees.


Pull in the rematerialization pass into CPU lowering pipeline.

The rematerialization avoids use of stack allocations, instead of using a temporary buffer for one of the intermediate. This allows aggressive fusion herusitcs to be used without requirement of a intermediate stack buffer.

FYI @pzread


Using the organisation field

Many entries in the NIC files reference an organisation. The organisation is a separate entry that can appear later in the file. It is referenced using an ID. Sometimes the only geographic information available concerning an entry is the address of the organisation.
As the organisation entry can appear later in the NIC file, we would have to parse it entirely first to index the organisations so that they can be referenced when parsing the IPv4 NIC entries.

The scope of this task is large and not actionnable yet. Let's close this issue for now and reopen it later if necessary. The tag idea will help find this kind of issues in the future.


Intentionally breaking UI tests to show issue#200

DON'T MERGE
To reproduce issue#200:

Build BPSampleAPP (and generate .xctestrun file)
xcodebuild -workspace Bluepill.xcworkspace -scheme BPSampleApp -sdk iphonesimulator -destination 'platform=iOS Simulator,name=iPhone 7,OS=11.0' build-for-testing -derivedDataPath "./XCTest"
Run bluepill
bluepill -p -f 1 -d "iPhone 7" -T "40" --xctestrun-path "XCTest/Build/Products/BPSampleApp_iphonesimulator11.0-x86_64.xctestrun"  -o "./output" -j -i BPSampleAppUITests

And then check ./output folder for results

ack


Pre-filling from browser keychain in auth dialog

See https://medium.com/opinionated-angularjs/techniques-for-authentication-in-angularjs-applications-7bbf0346acec

In Chrome this already works


Add EXT-X-PROGRAM-DATE-TIME to HLS playlist

It would be nice if the absolute time (either from server or from stream's timecode) were included in the playlist file.
See the specification: http://tools.ietf.org/html/draft-pantos-http-live-streaming-12#section-3.4.5

Agreed, looking to expose #EXT-X-PROGRAM-DATE-TIME in HLS playback


Add send screen

it should be possible to send to an address (manual input) as well as scan a qr code

Flow for sending a payment:

Note: I did https://github.com/get10101/10101/issues/59 as part of this, because send is related to the scanner and it made sense to define the flow together.
We can also keep the scanner screen simpler initially, the buttons there can be removed initially.


Add job configuration version

Rather than storing the full configuration for each job in the database, allow a version string to be set in the config file.
Questions:

Should the version default to a hash of the configuration?
Should version be specific to each job type?

The version is specific for each job definition.

Included in #1133


Fix issue #34

Coverage remained the same at 51.429% when pulling 8f93b4b98091c25650222903f1dd9e4137fa2371 on issue_34 into 137f6423de8fd7ba1c15969eaf48a56597dc9e71 on master.


Update commit_id

build error:
Error:  Failed to execute goal on project hugegraph-loader:
 Could not resolve dependencies for project org.apache.hugegraph:hugegraph-loader:jar:1.0.0:
 Could not find artifact org.apache.hugegraph:hugegraph-client:jar:1.0.0 in central (https://repo.maven.apache.org/maven2) -> [Help 1]

need update the relative path, or just drop the useless ojdbc dependency? (if possible, we can't keep it in apache repo too)


Cluster member unable to install apps

Summary:
A cluster member cannot install apps.
In the event the cluster member is not expected to be able to install apps I would ask why? They should not see apps in the UI then.
Vincent mentioned there's not a whole lot we can do here -- most of our apps deploy at cluster-level and thus need to at least be a cluster owner. A cluster member can only deploy into namespaces they own. -- In this case we should perhaps determine which apps (by testing) will work for cluster member - filter and only display these. The not-so-fun part is this would require testing all apps manually and creating a filter/list and maintaining it.
Environment:
Rancher version: v2.6-head 607fcdde6 pulled at 8/26/21 8:58 am Pacific
Rancher cluster type: single-node docker
Docker version: 20.10
Downstream cluster type: rke2
Downstream K8s version: v1.21.4-rc1+rke2r1
Steps to Reproduce:

Create a cluster as a restricted user. Add a standard user that will be the cluster member.
Log in as the cluster member. Create a project. Try to install the Longhorn app in into this project. The install fails.
Create a namespace in the project. Try to install the Ambassador app into this namespace. The install fails.

Expected Result:
I expected Longhorn to install.
I expected Ambassador to install.
Actual Result:
Longhorn does not install. It gets an error that appears may be rbac related.

Ambassador does not install. It gets an error that appears may be rbac related.

Additional Info:
I tried other apps like monitoring this too failed with similar errors. I suspect most or all apps will not install.

I'm closing this issue in favor of https://github.com/rancher/dashboard/issues/6667, as it is more of an enhancement to allow admins to hide charts.

Re-closing based on Catherine's comment 11/5/2022 -- looks like Zube probably reopened this on accident some time ago.


Switch default branch from 'master' to 'main'

As part of ensuring inclusive language is used throughout all Heroku repositories, we should switch from the current default branch of master to main.
This will involve:

[x] Creating a new branch main, based off current master
[x] Changing the default branch in GitHub to main
[x] Updating the branch protection settings
[x] Updating the target branch of any open PRs
[x] Updating any in-repo code/docs references (such as the Travis badge) -> #422
[x] Checking that there are no branch-specific Travis environment variables set
[x] Checking that Travis still works -> https://travis-ci.com/github/heroku/heroku-buildpack-go/builds/178287407
[x] Checking for any other deep links to this repository in other repos that include the branch name
[x] Update branch-specific URL on https://devcenter.heroku.com/articles/go-support
[ ] Creating a support briefing to mention the change
[ ] Deleting the master branch

Note:
Most users will be consuming this buildpack via the buildpack-registry stable release (using the shorthand alias heroku/go). Some will be using the master branch via a buildpack URL of https://github.com/heroku/heroku-buildpack-go, and others will be pinned to a specific branch or tag using https://github.com/heroku/heroku-buildpack-go#some-branch-or-tag.
In rare cases people may be using the latter form to specify the master branch, even though it's redundant to specify the branch name. Such usages will need to be updated to use either the default-branch GitHub form, or else the shorthand form (recommended).
Also GitHub now redirects any web links (such as the /blob/ URLs) whose branch doesn't exist, which reduces the urgency of catching every stray docs reference:
https://github.blog/changelog/2020-07-17-links-to-deleted-branches-now-redirect-to-the-default-branch/
@W-7869571@

In rare cases people may be using the latter form to specify the master branch

Analysing buildpack URLs used, I found only 1 app using the #master form with this buildpack and it hasn't had a deploy since 2018, so we should be good to just delete the old master branch.


Query Editor document turns into Notebook document

Azure Data Studio Version: master

Steps to Reproduce:

Open a query editor
Click Connect and go connection dialog

Expected: Query editor gets connected
Actual: Sometimes (I've seen it twice so far, but no clear repro yet) the query editor automatically turns into a notebook document.  In the below screen shot the highlight document was a query editor prior to clicking Connect toolbar button.

Closing as duplicate of #5144.


[#3293] feat(spark-connector): update kyuubi to 1.8.2

What changes were proposed in this pull request?
update kyuubi to 1.8.2
Why are the changes needed?
Fix: #3293
Does this PR introduce any user-facing change?
no
How was this patch tested?
existing tests

build ci failed to download node package, retry it.
                org.gradle.internal.resolve.ArtifactResolveException: Could not download node-20.9.0-linux-x64.tar.gz (org.nodejs:node:20.9.0)


Channel shifting

Hello Rob,
I have noticed a problem with the channel assignment.
I use your library to control 24 LEDs separately, sometimes together or in various blink algorithms. Now I have noticed. When I define the channels, it always starts to mix in another one slightly from 6 onwards. So from 6 the 7 is already lit, at 8 clearly the 9, from 12 the 13 and at 22 even channel 23 & 24.
I have written a small example to show you the error.
The channels are switched on one after the other and switched off again after the cycle, in the serial monitor you can see when which channel is written with which value. Unfortunately it does not match reality. At 21 I have 2-3 more LEDs on.
#include "TLC5947.h"
TLC5947 tlc(12, 11, 10,9);      //<--- attencion
int i, an = 4095;

void setup(){
  Serial.begin(9600);
  tlc.begin();
}

void loop(){
  for ( i = 0; i < 24; i++)
  {
    tlc.setPWM(i, an);
    delay(500);
    tlc.write();
    Serial.print(i);
    Serial.print(" = ");
    Serial.println(an);
    if(i == 23){ an = an ?0:4095;}
  }
}

Thanks for reporting,
I will investigate asap

Q: What board do you use?
Hypothesis 0
Wiring problem
Q: do you have pull ups on the data and clock line?
If so what value?
Hypothesis 1
The clocking of bits - in write() function - might be too fast.
Hypothesis 2
The number of bits sent is too large.

hypotheses 2 is most likely.
Can you change in the .cpp file
In the write function
mask = 0x1000
Into
mask = 0x0800
Two times.
In the AVR optimized part
And in the "normal" part

No hardware to test with so I added a counter to count the nr of bits send in write().
It did send 13 bits instead of 12.
That means the hypothesis 2 is confirmed.
A new version 0.2.0 will be build asap
I also want to add an RGB interface to control 8 RGB LEDS, so might take some time.

Hello, thanks for the quick reply.
Nice that you found it right away. I will be happy to test it.
Instead of implementing RGB, I think "daisy chaining" would be more important. Adafruit already offers enough RGB. Your library is characterized by the fact that the channels can be addressed individually.

I still need to but hardware to test the daisy chaining, it is on my (long) TODO list.
Develop branch is expected within 15 minutes.

Develop branch and PR created, build is running.

I changed the .cpp and immediately did a hardware test. Now they are controlled correctly and no longer scatter. Thanks for that.
I still have a few tests to do with this lib and will be happy to report any further problems. If you want to have something tested, I am also happy to help.

F: Welches Board verwenden Sie?

LGT8F328P_Nano

If you could verify the develop branch would be great!

Daisy chaining is mostly

make a configurable max channels
allocate a large enough array to hold all PWM values.

it might be useful to compact 4 x 12 bits in 3 x uint16_t to save some RAM. (optimization).

will create a test branch today.

Created a daisy_chain branch in which the constructor has an extra parameter uint8_t deviceCount.
This may be 1..10 or so as the internal variable _channels is also an uint8_t.
If you want, you can give it a try - I have to attend other tasks

Daisy chain branch is updated after some (dry) test runs with the performance sketch.
An Arduino UNO did work with performance sketch and 30 devices, and failed at 35 devices.
30 devices == 720 channels is using 1440 bytes so memory
performance scales linear with number of devices.
ESP32 - test run 200 devices still worked.
Channels: 4800
SETPWM	884
SETRGB	462
WRITE	24112  (24 milliseconds)

So it looks like the daisy chain is reasonable prepared for a 0.3.0 version of the library.

Wow that's amazing, I was only thinking of 4-5 devices, so 96-120 channels. I'll have a look and give it a try. I'll report back.

Wenn Sie den Entwicklungszweig überprüfen könnten, wäre das großartig!

Had a look at your RGB branch, wrote a little test example, actually I took the Adafruit_RGB example and adapted it to your LIB, works identically. See here:
`#include "TLC5947.h"
// How many boards do you have chained?
#define NUM_TLC5947 1
const int CLOCK = 12;
const int DATA  = 11;
const int LATCH = 10;
const int BLANK = 9;
TLC5947 tlc(CLOCK, DATA, LATCH, BLANK);
void setup() {
Serial.begin(9600);
Serial.println("TLC5947 test");
tlc.begin();
if (BLANK >= 0) {
pinMode(BLANK, OUTPUT);
digitalWrite(BLANK, LOW);
}
}
void loop() {
colorWipe(4095, 0, 0); // "Red" (depending on your LED wiring)
delay(200);
colorWipe(0, 4095, 0); // "Green" (depending on your LED wiring)
delay(200);
colorWipe(0, 0, 4095); // "Blue" (depending on your LED wiring)
delay(200);
rainbowCycle(10);
}
// Fill the dots one after the other with a color
void colorWipe(uint16_t r,  uint16_t g,  uint16_t b) {
for(uint8_t i=0; i<8*NUM_TLC5947; i++) {
tlc.setRGB(i, r, g, b);
tlc.write();
delay(200);
}
}
// Slightly different, this makes the rainbow equally distributed throughout
void rainbowCycle(uint8_t wait) {
uint32_t i, j;
for(j=0; j<4096; j++) { // 1 cycle of all colors on wheel
for(i=0; i< 8NUM_TLC5947; i++) {
Wheel(i, ((i * 4096 / (8NUM_TLC5947)) + j) & 4095);
}
tlc.write();
delay(wait);
}
}
// Input a value 0 to 4095 to get a color value.
// The colours are a transition r - g - b - back to r.
void Wheel(uint8_t ledn, uint16_t WheelPos) {
if(WheelPos < 1365) {
tlc.setRGB(ledn, 3WheelPos, 4095 - 3WheelPos, 0);
} else if(WheelPos < 2731) {
WheelPos -= 1365;
tlc.setRGB(ledn, 4095 - 3WheelPos, 0, 3WheelPos);
} else {
WheelPos -= 2731;
tlc.setRGB(ledn, 0, 3WheelPos, 4095 - 3WheelPos);
}
}`

Good to hear, for me green light to merge the develop branch into master and release 0.2.0
Then the daisy chaining version is next (at least for this repo)

Issue is closed because of the merge, we can open a new one focused on the daisy chaining if needed.
My first actions are to get the build working again, meta data and documentation.


feat(all): Add an API to register an alias name for an existing key

I use aurelia dependency injection in one of my project, which allows other developers to extend the core functionalities and use the DI container in very flexible ways. I found in a few circumstances that it would be useful to register an alias for a key, so an instance or a singleton could be accessed in multiple ways. Currently I use registerHandler() to achieve this, but I wonder if you would also find this useful and accept registerAlias() as a public API.
I tried to follow the contribution guidelines, however the build process in the latest commit is broken. I still created this PR since the code changes are minimal, and I would like to see if you are interested at all.

@echevil I think this is a reasonable feature request and I'd like to have it in the API. However, we are about to make some big internal changes to the DI in order to improve performance and memory. So, I think we should wait until after that work is done and then revisit this.

@EisenbergEffect that's good to know. Thanks

@chen-pang We have merged the new changes into the DI now. The PR you have here won't work against the new version, but I can easily add the alias feature now. I'll get it out in the next release. Thanks!

Thanks!


Raphael/kms

add kms feature, tested and validated with sops

I approve this pull request, thank you.


Document String's 'is_valid_filename()'

Added in commit a20235aeb02c0c9e5ce58c0236f88a19865d571c.

Thanks!

Cherry-picked for 3.1.1.


MatDialogRef.updateSize() is not working as expected

MatDialogRef.updateSize() changes the size of the dialog but the content becomes scrollable instead of using the new size.
What is the expected behavior?
The dialog content should be resize to the specified size
What is the current behavior?
Content is getting clipped off
What are the steps to reproduce?
https://stackblitz.com/edit/angular-tjj2ha

Looks like it is resizing but you have a parent div that its constraining it. ( the div w/ confirmWithPayload switch on it ).

@amcdnl I tried it without switch div around it, it's still behaving the same way.

@playground this is because you placed mat-dialog-actions inside mat-dialog-content. If you move it outside, it works fine.

@willshowell yep, that works. Thx.


Failing python unit tests for multiple resource group parameters on aro extensions.

The unit tests for python started to fail on the following error.
FAIL - HIGH severity: parameter_should_not_end_in_resource_group
    Parameter: aro create, `cluster_resource_group` - A command should only have '--resource-group' as its resource group parameter. However options '--cluster-resource-group' in command 'aro create' end with 'resource-group' or similar.
    Parameter: aro create, `vnet_resource_group_name` - A command should only have '--resource-group' as its resource group parameter. However options '--vnet-resource-group' in command 'aro create' end with 'resource-group' or similar.

The failure is at least in the following prs:

https://github.com/Azure/ARO-RP/pull/763
https://github.com/Azure/ARO-RP/pull/693

Renaming should be an option.

see https://github.com/Azure/azure-cli/blob/5fe403f21d44a839eec1f358702076998bbc2f38/linter_exclusions.yml#L64-L71

we need to set up a linter_exclusions file too, I guess?

@jim-minter @petrkotas
Is this the linter exclusion file that is missing? https://github.com/Azure/ARO-RP/pull/693/files#diff-0bd0f4acbef9aa1d479ae24c9f3232ca


Need to make target=release work on linux and mac

The scons file in several demos check target=release/debug for windows and switch whether or not to include debug symbols.
It seems this may be different on Linux and Mac because neither have specific switches build in. I'm not sure what is required here but need to look into this.

This now works on Linux and Mac. Closing as fixed.


fix: fix upstream bug in smooth-dnd where animationDuration has no default

In the smooth-dnd documentaiton, it says animationDuration has a default of 250, but that's not true (there is none specified). This results in items snapping back suddenly when released.
smooth-dnd is pretty dusty and I don't expect any PRs to be merged, so how about we fix it in this package?
Fixes #6

[commonjs--resolver] Failed to resolve entry for package "vue3-smooth-dnd". The package may have incorrect main/module/exports specified in its package.json.

hey @kknono try using the v0.0.4 version


UTF8 log email

Hi there,
Just to let you know emails from Tracy logger don't decode properly special character.
Maybe you have a hint?
Thanks

Please show code example


how to use disable to disable previous dates?

i want to disable the previous and the current date and it will not be able to select those days

This is how I did it. Any dates that come before setMinimumDate will be disabled. Any dates that come after setMaximumDate will be disabled.
calendarView.state().edit()
.setFirstDayOfWeek(Calendar.SUNDAY)
.setMinimumDate(CalendarDay.from(currentYear, currentMonth, currentDay))
.setMaximumDate(CalendarDay.from(lastYear, lastMonth, lastDay))
.setCalendarDisplayMode(CalendarMode.MONTHS)
.commit();

thanks for the reply @leronj23  :)
i use this block of code:
materialCalendarView.addDecorator(new DayViewDecorator() {
@Override
public boolean shouldDecorate(CalendarDay day) {
CalendarDay date= CalendarDay.today();
return (day.isBefore(date)) ? true : false;
}
        @Override
        public void decorate(DayViewFacade view) {
            view.setSelectionDrawable(getDrawable(R.drawable.drawable_rectangle));
            view.setDaysDisabled(true);
            view.areDaysDisabled();
        }
    });

but the disable dates disappeared, i want to show the dates but it will not be clickable anymore.

This is how you used the code I provided. This is what your activity show have in it.
// Calendar
calendarView = (MaterialCalendarView) findViewById(R.id.calendarView);
calendarView.setSelectionMode(MaterialCalendarView.SELECTION_MODE_MULTIPLE);
calendarView.setOnDateChangedListener(this);
calendarView.state().edit()
.setFirstDayOfWeek(Calendar.SUNDAY)
.setMinimumDate(CalendarDay.from(currentYear, currentMonth, currentDay))
.setMaximumDate(CalendarDay.from(lastYear, lastMonth, lastDay))
.setCalendarDisplayMode(CalendarMode.MONTHS)
.commit();
This is what my shouldDecorate looks like.
@Override
public boolean shouldDecorate(CalendarDay day) {
    return date != null && day.equals(date);
}

i have used it and its working
1 step :-
private static class PrimeDayDisableDecorator implements DayViewDecorator {

    @Override
    public boolean shouldDecorate(final CalendarDay day) {
        CalendarDay date= CalendarDay.today();
        return (day.isBefore(date)) ? true : false;
    }
    @Override
    public void decorate(final DayViewFacade view) {
        view.setDaysDisabled(true);
    }
}

Step 2 :-
in onCreate();
calendarContainer.addDecorator(new PrimeDayDisableDecorator());


Integrate the mixer in the deployment

Jenkins job manager/presubmit started

Jenkins job manager/presubmit failed

Jenkins job manager/presubmit started

Jenkins job manager/presubmit failed

Jenkins job manager/presubmit started

Jenkins job manager/presubmit failed

Jenkins job manager/presubmit started

Jenkins job manager/presubmit failed

Jenkins job manager/presubmit started

Jenkins job manager/presubmit failed

Jenkins job manager/presubmit started

Jenkins job manager/presubmit failed

Jenkins job manager/presubmit started

Jenkins job manager/presubmit failed

Jenkins job manager/presubmit started

Jenkins job manager/presubmit failed

Jenkins job manager/presubmit started

Jenkins job manager/presubmit failed

Jenkins job manager/presubmit passed

Jenkins job manager/presubmit passed

Jenkins job manager/presubmit passed

Feel free to merge.

Jenkins job manager/presubmit passed


MAINTAINERS: ensure the bot tags posix rather than cmsis

Previously, a large number of pull requests involving documentation were being tagged as related to CMSIS rather than POSIX because the CMSIS files blanketed all of doc/services/portability/ in MAINTAINERS.yml.
Be more specific about which sections of the documentation belong to CMSIS and which belong to POSIX.

duplicate?

duplicate #65687?

Yep. Closing this one


` leftovers from dynamic iteration  (debug mode only)

Describe the bug
When rendering  Vec<T> dynamically with <For />, each element is wrapped between  and  (of course, debug mode). The problem is that the upper HTML comment may not get removed with the removal of its related item.
Leptos Dependencies
No other dependencies<EMAIL_ADDRESS>isn't affected and I could confirm this issue with both "abf90358fa60de0334077da5f38fc3cff0494916" and "8096d7c416d6321380a0ce0276d3a64df4d1d0bf"
leptos = { git = "https://github.com/leptos-rs/leptos", rev = "abf90358fa60de0334077da5f38fc3cff0494916" }   # affected
# leptos = { git = "https://github.com/leptos-rs/leptos", rev = "8096d7c416d6321380a0ce0276d3a64df4d1d0bf" } # affected
# leptos = "0.3.0" # not affected

To Reproduce
The code below contains 6 different views. Make sure to un-comment let view = ..... line by line to test with different possibilities.
use leptos::*;

fn main() {
    leptos::mount_to_body(move |cx| {
        view! { cx, <App /> }
    })
}

#[component]
fn App(cx: Scope) -> impl IntoView {
    let (count, set_count) = create_signal(cx, 0);
    let (items, set_items) = create_signal(cx, Vec::<(usize, View)>::new());

    // push a new view every 4-seconds
    set_interval(move || {
        set_count.update(|c| *c += 1);

        set_items.update(move |items| {
            let key = count.get_untracked();

            // test-1 (issue): string literal
            let view_literal = view! { cx, "text node"};

            // test-2 (issue): string slice
            let view_str = view! { cx, {"string slice"} };

            // test-3 (issue): owned string
            let view_string = view! { cx, {"owned-string".to_owned()}};

            // test-4 (issue): direct content (not wrapped in quotes)
            //   -<EMAIL_ADDRESS>won't allow this, and not sure it it's a bug from recent updates.
            let view_direct_content = view! { cx, direct_content};

            // test-5 (issue): the same issue with Fragment containing multiple elements
            let view_fragment = view! { cx,

"line-1"

"line-2"

            };

            // test-6 (no-issue):wrapping content in `HTMLElement` is not a problem
            let view_single_element = view! { cx,

                    "wrapped in a single element"

"line - 1"

"line - 2"

            };

            // un-comment to select a view for testing
            let view = view_literal.into_view(cx);        // test-1 (affected)
            // let view = view_str.into_view(cx);            // test-2 (affected)
            // let view = view_string.into_view(cx);         // test-3 (affected)
            // let view = view_direct_content.into_view(cx); // test-4 (won't compile with<EMAIL_ADDRESS>            // let view = view_fragment.into_view(cx);       // test-5 (affected)
            // let view = view_single_element.into_view(cx); // test-6 (not-affected)

            // push view to list
            items.push((key, view));

            // remove the pushed view, after 2-second timeout
            set_timeout(move || {
                log!("key: {}", key);
                set_items.update(move |items| {
                    items.remove(0);
                });
            }, std::time::Duration::from_secs(2));
        });

    }, std::time::Duration::from_secs(4));

    view! { cx,

"issue with dynamic rendering <For />"

            <For
                each=items
                key=|item| { item.0 }
                view=move |_cx, (_, view)| view
                // view=move |_cx, (_, view)| view! { cx, {view}} // replacing the above line with this won't stop the issue
            />

    }
}

Expected behavior
Full removal of the upper comment after removing its related item from list.
Screenshots

Additional context

Linux
rustc 1.72.0-nightly (1c53407e8 2023-05-28)
this issue is affecting debug mode; trunk build is affected but not trunk build --release

Thanks. This should be resolved now.

Again, This issue is affecting version 0.4.5

This is an issue again in 0.5.4. Minimal repro:
use leptos::*;

#[component]
pub fn App() -> impl IntoView {
    let count = RwSignal::new(0);
    let items = RwSignal::new(Vec::<usize>::new());

    let add = move || {
        count.update(|c| *c += 1);

        items.update(move |items| {
            let key = count.get_untracked();

            items.push(key);
        });
    };

    let remove = move || {
        items.update(move |items| {
            _ = items.remove(0);
        });
    };

    create_effect(move |_| {
        add();
        add();
        add();
        add();
        remove();
        remove();
        remove();
    });

    view! {

"issue with dynamic rendering <For />"

            <For
                each=items
                key=|item| { *item }
                children=move |_| view! { "nothing" }
            />

    }
}

@gbj Can you reopen this please?
If you use For to implement a virtual scroller, you get +10,000s of these comment nodes added just by a bit of scrolling.
This turns into a fatal issue for Chrome and Tauri (probably all webkit browsers) if the container is contenteditable. With just ~2,000 excess comment nodes, the view will become unresponsive. Firefox appears to tolerate comment nodes a little better.
Here is a minimal repro instead of a full virtual scroller. Each click replaces the content of the For. After about a 20 redraws, reaching 2000 nodes, subsequent redraws start to take 10s of seconds in Chrome.

OS: Ubuntu 22.04
Leptos: 0.6.12
Chrome:  125.0.6422.141
Tauri: beta 2

#[derive(Debug, Clone, PartialEq)]
pub struct VirtualItem {
    pub index: usize,
    pub data: String,
}

#[component]
pub fn DemoEditor() -> impl IntoView {
    let need_redraw = create_rw_signal(0);

    let list = create_memo(move |_| {
        (0..100)
            .map(|i| VirtualItem {
                index: i + 100 * need_redraw.get(),
                data: format!("This is item {}\n", i + 100 * need_redraw.get()),
            })
            .collect::<Vec<VirtualItem>>()
    });

    view! {

            <button
                on:click={move |_| need_redraw.update(|f| *f += 1)}
                style="background: red; color: white">Redraw</button>

                <For
                    each=move || list.get()
                    key=|item| item.index
                    let:item >

                        {item.data}

                </For>

    }
}

And a utility function to count the DOM nodes:
function countDOMNodes(node = document.body) {
    let count = 1; // Start with one to count the current node
    node.childNodes.forEach(child => {
        count += countDOMNodes(child); // Recursively count children
    });
    return count;
}

With trunk server --release I do not see the problem with leaking comments but I still see two empty comment nodes for each item. Are they intentional? Given comment nodes are not "free" and have a performance impact, can they be removed too?

This is item 2

@duncanawoods I'm happy to reopen it, with these caveats:

It's not something I will have time to work on in the near future
In the case of the example you give above, there's no point in using <For/> rather than plain iteration: every row is rerendered on every redraw, because the keys are always new (It may be different in your actual example, if you are reusing keys)
I just tested this against the leptos_0.7 branch and it is steady at exactly 308 DOM nodes total, no matter how many redraws (with 0 total comment nodes)

If you want to work on hunting down the debug-mode leaking comments, that's fine by me, but I think my time is better spent getting 0.7 into an alpha and beta state and then to release, as it is doing much better here by all measures! (including removing the excess comments you note)

In a real implementation of a virtual scroller, there is overlap in the items for scroll increments smaller than the view. This is just a minimal repro of the problem without the distraction of scroll events, element sizing and such which requires a half a dozen more signals.
Sounds promising!

If you want to work on hunting down the debug-mode leaking comments, that's fine by me

I've had a quick look and can see a likely problem. The code to remove the comment looks like it is excluded by a not(debug_assertions) conditional compilation:
https://github.com/leptos-rs/leptos/blob/b22f3bb3bdae9a7253751100f743af5509c1512a/leptos_dom/src/components/each.rs#L413-L435
I've tried some printf debugging using trunk serve but with all the generic params in this function, I can't even turn state into strings lol.

I think this one is no longer relevant in 0.7.


Fix table layout issue in ai.contentsafety-readme.md

@danieljurek Could you help approve and merge?


Need for extensive logging mechanism

Issues :
-> Current logging method is not efficient, it is just flooding with same messages  ( as some APIs were called every second).
-> It becomes difficult to analyse the issue, as it misses some important information & floods with same message.
-> Some important logging steps were missed, such as whether model_id set properly, model_client_object created,  model response, whether model response is in the requested json format.
Fix required :
-> Need clean logging mechanism which logs all important steps!

If this issue is not reserved for someone, I will start working on it.

fetch the latest changes.


Don't generate AES-CTR webcrypto keys

Summary
Generating AES-CTR keys causes Safari to print a warning to the console that this is not safe. Safari is right, an authenticated cipher should be preferred.
However, we actually do prefer an authenticated cipher! We use AES-GCM. So why does the warning get printed?
Well, because we essentially do this (pseudocode):
const key = webcrypto.generateKey("AES-CTR") // safari prints a warning accordingly
const keyBytes = webcrypto.exportKey(key)
// key gets stored/passed around like that and then later
const importedKey = webcrypto.importKey("AES-GCM", keyBytes)
// on encryption we use this
webcrypto.encrypt("AES-GCM", importedKey, data)

Problem
We shouldn't generate AES-CTR keys. We also have a constant:
https://github.com/fission-codes/webnative/blob/0e3224706f6565b29e327d7392b88b0e804e5f99/src/fs/protocol/basic.ts#L19
which should definitely either be removed or set to AES-GCM.
Impact

Safari users get a scary warning printed on the console
Future development may accidentally make use of AES-CTR in an unsafe way

Solution
Either

change the constant to AES-GCM or
delete the constant, as it's not actually useful.

Detail
We could delete the constant and replace use sites like this:
https://github.com/fission-codes/webnative/blob/0e3224706f6565b29e327d7392b88b0e804e5f99/src/fs/v1/PrivateTree.ts#L189
With code like this:
import { webcrypto } from "one-webcrypto"

const key = webcrypto.getRandomValues(new Uint8Array(32))

Fixed on next branch.


Magic Numbers in calculation of named Arguments

In Jetpack Compose we have a Modifier called aspectRatio which expects a float value.
To fill this I provided .aspectRatio(ratio = 4f / 3f). MagicNumber detection is by default disabled for named arguments, but still Detekt complains about this because it's a calculation. In my case the above notation provides an easier and more readable solution than the following options

.aspectRatio(ratio = 1.33f)
.aspectRatio(ratio = FOUR_BY_THREE_RATIO)

Is there any way to disable MagicNumber detection for calculations in named arguments for such a case?

Is there any way to disable MagicNumber detection for calculations in named arguments for such a case?

Not at the moment. In the snippet you mentioned, the Magic Numbers instances are found inside an expression. The named arguments is just one of the parent.
We could add a check here:
https://github.com/detekt/detekt/blob/14c0f11e44555cd55dc0940dec722070db4c8b0b/detekt-rules-style/src/main/kotlin/io/gitlab/arturbosch/detekt/rules/style/MagicNumber.kt#L158
To verify if the named argument is one of parent, but I'm unsure this is worth. Moreover it's a one-off that will apply only to named arguments and not to all the other config options. I'm not sure we want to go this way.

Would it work for you if we suppress MagicNumber for all @Compose functions (More prone to false negatives)? This is supported by specifying ignoreAnnotated under each rule. See https://detekt.dev/compose.html#magicnumber

Would it work for you if we suppress MagicNumber for all @Compose functions (More prone to false negatives)?

Closing as a solution was suggested. Feel free to re-open if you wish to discuss further @jakobulbrich


Action button for confirming operations

It would be much more polished for have a bottom aligned action button than a navigation bar button for performing operations.

Closing as invalid; this no longer makes sense as we adopt the new macOS application design.


It is not work when build.

When build my project. All svgs build in public.  Could i build svg inline not in public?
Here is my config.
import { defineConfig } from 'vite';
import react from '@vitejs/plugin-react';
import svgrPlugin from 'vite-plugin-svgr';

// https://vitejs.dev/config/
export default defineConfig({
    plugins: [svgrPlugin(), react()],
});

How did you solve this problem?

I didn't solve this problem because svg is already embedded in the compiled code. The svg in public does not affect the execution of my code


Create React components for annotations

First annotations could be a peak label
One way is to draw a vertical line that is just on top of the peak with the value next to it like:

Would be nice that this value can optionaly be edited

i implemented the this feature, you check it at the current version at githup


Refactored !welcome and fixed(?) member milestones

As per title :)
Fixes:

Milestones (#150)
Display names (#161)

LGTM 👍


Failed on createQuery with exception java.lang.NoSuchMethodError: org/hibernate/query/internal/QueryImpl.

Hi,
I just move to release candidate 4 (1.0.0.CR4), and the same simple query that was working with 1.0.0.CR3 failed now with the following exception:
18:34:55.480 [vert.x-eventloop-thread-0] DEBUG org.hibernate.hql.internal.ast.util.JoinProcessor - Using FROM fragment [device device0_]
18:34:55.480 [vert.x-eventloop-thread-0] DEBUG org.hibernate.hql.internal.antlr.HqlSqlBaseWalker - select >> end [level=1, statement=select]
18:34:55.481 [vert.x-eventloop-thread-0] DEBUG org.hibernate.hql.internal.ast.QueryTranslatorImpl - --- SQL AST ---
 \-[SELECT] QueryNode: 'SELECT'  querySpaces (device)
    +-[SELECT_CLAUSE] SelectClause: '{derived select clause}'
    |  +-[SELECT_EXPR] SelectExpressionImpl: 'device0_.id as id1_0_' {FromElement{explicit,not a collection join,not a fetch join,fetch non-lazy properties,classAlias=null,role=null,tableName=device,tableAlias=device0_,origin=null,columns={,className=com.algosec.objectflow.objectimporter.model.Device}}}
    |  \-[SQL_TOKEN] SqlFragment: 'device0_.created_at as created_2_0_, device0_.updated_at as updated_3_0_, device0_.version as version4_0_, device0_.brand as brand5_0_, device0_.display_name as display_6_0_, device0_.name as name7_0_, device0_.uuid as uuid8_0_'
    \-[FROM] FromClause: 'FROM' FromClause{level=1, fromElementCounter=1, fromElements=1, fromElementByClassAlias=[], fromElementByTableAlias=[device0_], fromElementsByPath=[], collectionJoinFromElementsByPath=[], impliedElements=[]}
       \-[FROM_FRAGMENT] FromElement: 'device device0_' FromElement{explicit,not a collection join,not a fetch join,fetch non-lazy properties,classAlias=null,role=null,tableName=device,tableAlias=device0_,origin=null,columns={,className=com.algosec.objectflow.objectimporter.model.Device}}

18:34:55.481 [vert.x-eventloop-thread-0] DEBUG org.hibernate.hql.internal.ast.ErrorTracker - throwQueryException() : no errors
18:34:55.484 [vert.x-eventloop-thread-0] DEBUG org.hibernate.hql.internal.ast.QueryTranslatorImpl - HQL: FROM com.algosec.objectflow.objectimporter.model.Device
18:34:55.484 [vert.x-eventloop-thread-0] DEBUG org.hibernate.hql.internal.ast.QueryTranslatorImpl - SQL: select device0_.id as id1_0_, device0_.created_at as created_2_0_, device0_.updated_at as updated_3_0_, device0_.version as version4_0_, device0_.brand as brand5_0_, device0_.display_name as display_6_0_, device0_.name as name7_0_, device0_.uuid as uuid8_0_ from device device0_
18:34:55.484 [vert.x-eventloop-thread-0] DEBUG org.hibernate.hql.internal.ast.ErrorTracker - throwQueryException() : no errors
java.util.concurrent.CompletionException: java.lang.NoSuchMethodError: org/hibernate/query/internal/QueryImpl.<init>(Lorg/hibernate/engine/spi/SharedSessionContractImplementor;Lorg/hibernate/engine/query/spi/HQLQueryPlan;Ljava/lang/String;)V (loaded from file:/C:/Users/yaakov.berkovitch/.m2/repository/org/hibernate/hibernate-core/5.4.28.Final/hibernate-core-5.4.28.Final.jar by jdk.internal.loader.ClassLoaders$AppClassLoader@1fa9057e) called from class org.hibernate.reactive.session.impl.ReactiveQueryImpl (loaded from file:/C:/Users/yaakov.berkovitch/.m2/repository/org/hibernate/reactive/hibernate-reactive-core/1.0.0.CR4/hibernate-reactive-core-1.0.0.CR4.jar by jdk.internal.loader.ClassLoaders$AppClassLoader@1fa9057e).
	at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314)
	at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:319)
	at java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1081)
	at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
	at java.base/java.util.concurrent.CompletableFuture.postFire(CompletableFuture.java:610)
	at java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1085)
	at java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:478)
	at org.hibernate.reactive.stage.impl.StageSessionFactoryImpl.lambda$null$0(StageSessionFactoryImpl.java:52)
	at org.hibernate.reactive.stage.impl.StageSessionFactoryImpl$$Lambda$214/000000000000000000.handle(Unknown Source)

The code looks like:
        sessionFactory.withSession(
                session -> session.createQuery("FROM Device", Device.class)
                        .getResultList().toCompletableFuture()
                        .thenApply(rows -> {
                            Collection<Device> result = new ArrayList<>(rows.size());
                            rows.forEach(row -> {
                                result.add((Device) row);
                            });
                            return result.stream();
                        })
        ).exceptionally(throwable -> {
            throwable.printStackTrace();
            return null;
        });

Dependencies:

Hibernate Reactive version 1.0.0.CR4
io.vertx:vertx-pg-client:4.0.3
io.vertx:vertx-core:4.0.3
Spring boot
Junit
Postgres
Java-11

Hibernate Reactive 1.0.0.CR4 won’t work with versions of Hibernate ORM
older than 5.4.31.Final.
Sorry for the inconvenience.
On Fri, 7 May 2021, 09:57 yberkov, @.***> wrote:

Hi,
I just move to release candidate 4 (1.0.0.CR4), and the same simple query
that was working with 1.0.0.CR3 failed now with the following exception:
18:34:55.480 [vert.x-eventloop-thread-0] DEBUG org.hibernate.hql.internal.ast.util.JoinProcessor - Using FROM fragment [device device0_]
18:34:55.480 [vert.x-eventloop-thread-0] DEBUG org.hibernate.hql.internal.antlr.HqlSqlBaseWalker - select >> end [level=1, statement=select]
18:34:55.481 [vert.x-eventloop-thread-0] DEBUG org.hibernate.hql.internal.ast.QueryTranslatorImpl - --- SQL AST ---
-[SELECT] QueryNode: 'SELECT'  querySpaces (device)
+-[SELECT_CLAUSE] SelectClause: '{derived select clause}'
|  +-[SELECT_EXPR] SelectExpressionImpl: 'device0_.id as id1_0_' {FromElement{explicit,not a collection join,not a fetch join,fetch non-lazy properties,classAlias=null,role=null,tableName=device,tableAlias=device0_,origin=null,columns={,className=com.algosec.objectflow.objectimporter.model.Device}}}
|  -[SQL_TOKEN] SqlFragment: 'device0_.created_at as created_2_0_, device0_.updated_at as updated_3_0_, device0_.version as version4_0_, device0_.brand as brand5_0_, device0_.display_name as display_6_0_, device0_.name as name7_0_, device0_.uuid as uuid8_0_'
-[FROM] FromClause: 'FROM' FromClause{level=1, fromElementCounter=1, fromElements=1, fromElementByClassAlias=[], fromElementByTableAlias=[device0_], fromElementsByPath=[], collectionJoinFromElementsByPath=[], impliedElements=[]}
-[FROM_FRAGMENT] FromElement: 'device device0_' FromElement{explicit,not a collection join,not a fetch join,fetch non-lazy properties,classAlias=null,role=null,tableName=device,tableAlias=device0_,origin=null,columns={,className=com.algosec.objectflow.objectimporter.model.Device}}
18:34:55.481 [vert.x-eventloop-thread-0] DEBUG org.hibernate.hql.internal.ast.ErrorTracker - throwQueryException() : no errors
18:34:55.484 [vert.x-eventloop-thread-0] DEBUG org.hibernate.hql.internal.ast.QueryTranslatorImpl - HQL: FROM com.algosec.objectflow.objectimporter.model.Device
18:34:55.484 [vert.x-eventloop-thread-0] DEBUG org.hibernate.hql.internal.ast.QueryTranslatorImpl - SQL: select device0_.id as id1_0_, device0_.created_at as created_2_0_, device0_.updated_at as updated_3_0_, device0_.version as version4_0_, device0_.brand as brand5_0_, device0_.display_name as display_6_0_, device0_.name as name7_0_, device0_.uuid as uuid8_0_ from device device0_
18:34:55.484 [vert.x-eventloop-thread-0] DEBUG org.hibernate.hql.internal.ast.ErrorTracker - throwQueryException() : no errors
java.util.concurrent.CompletionException: java.lang.NoSuchMethodError: org/hibernate/query/internal/QueryImpl.(Lorg/hibernate/engine/spi/SharedSessionContractImplementor;Lorg/hibernate/engine/query/spi/HQLQueryPlan;Ljava/lang/String;)V (loaded from file:/C:/Users/yaakov.berkovitch/.m2/repository/org/hibernate/hibernate-core/5.4.28.Final/hibernate-core-5.4.28.Final.jar by @.) called from class org.hibernate.reactive.session.impl.ReactiveQueryImpl (loaded from file:/C:/Users/yaakov.berkovitch/.m2/repository/org/hibernate/reactive/hibernate-reactive-core/1.0.0.CR4/hibernate-reactive-core-1.0.0.CR4.jar by @.).
at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314)
at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:319)
at java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1081)
at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
at java.base/java.util.concurrent.CompletableFuture.postFire(CompletableFuture.java:610)
at java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1085)
at java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:478)
at org.hibernate.reactive.stage.impl.StageSessionFactoryImpl.lambda$null$0(StageSessionFactoryImpl.java:52)
at org.hibernate.reactive.stage.impl.StageSessionFactoryImpl$$Lambda$214/000000000000000000.handle(Unknown Source)
The code looks like:
    future = sessionFactory.withSession(
            session -> session.createQuery("FROM Device")
                    .getResultList().toCompletableFuture()
                    .thenApply(rows -> {
                        Collection<Device> result = new ArrayList<>(rows.size());
                        rows.forEach(row -> {
                            result.add((Device) row);
                        });
                        return result.stream();
                    })
    ).exceptionally(throwable -> {
        throwable.printStackTrace();
        return null;
    });

Dependencies:

Hibernate Reactive version 1.0.0.CR3
io.vertx:vertx-pg-client:4.0.3
io.vertx:vertx-core:4.0.3
Spring boot
Junit
Postgres
Java-11

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hibernate/hibernate-reactive/issues/746, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEIQ5IBDVY6VC2BZ4GVPSDTMOTRPANCNFSM44JKNPTQ
.

The release post contains a couple more details about it:
https://in.relation.to/2021/04/30/hibernate-reactive-1_0_0_CR4/
On Fri, 7 May 2021, 11:54 Davide D'Alto, @.***> wrote:

Hibernate Reactive 1.0.0.CR4 won’t work with versions of Hibernate ORM
older than 5.4.31.Final.
Sorry for the inconvenience.
On Fri, 7 May 2021, 09:57 yberkov, @.***> wrote:

Hi,
I just move to release candidate 4 (1.0.0.CR4), and the same simple query
that was working with 1.0.0.CR3 failed now with the following exception:
18:34:55.480 [vert.x-eventloop-thread-0] DEBUG org.hibernate.hql.internal.ast.util.JoinProcessor - Using FROM fragment [device device0_]
18:34:55.480 [vert.x-eventloop-thread-0] DEBUG org.hibernate.hql.internal.antlr.HqlSqlBaseWalker - select >> end [level=1, statement=select]
18:34:55.481 [vert.x-eventloop-thread-0] DEBUG org.hibernate.hql.internal.ast.QueryTranslatorImpl - --- SQL AST ---
-[SELECT] QueryNode: 'SELECT'  querySpaces (device)
+-[SELECT_CLAUSE] SelectClause: '{derived select clause}'
|  +-[SELECT_EXPR] SelectExpressionImpl: 'device0_.id as id1_0_' {FromElement{explicit,not a collection join,not a fetch join,fetch non-lazy properties,classAlias=null,role=null,tableName=device,tableAlias=device0_,origin=null,columns={,className=com.algosec.objectflow.objectimporter.model.Device}}}
|  -[SQL_TOKEN] SqlFragment: 'device0_.created_at as created_2_0_, device0_.updated_at as updated_3_0_, device0_.version as version4_0_, device0_.brand as brand5_0_, device0_.display_name as display_6_0_, device0_.name as name7_0_, device0_.uuid as uuid8_0_'
-[FROM] FromClause: 'FROM' FromClause{level=1, fromElementCounter=1, fromElements=1, fromElementByClassAlias=[], fromElementByTableAlias=[device0_], fromElementsByPath=[], collectionJoinFromElementsByPath=[], impliedElements=[]}
-[FROM_FRAGMENT] FromElement: 'device device0_' FromElement{explicit,not a collection join,not a fetch join,fetch non-lazy properties,classAlias=null,role=null,tableName=device,tableAlias=device0_,origin=null,columns={,className=com.algosec.objectflow.objectimporter.model.Device}}
18:34:55.481 [vert.x-eventloop-thread-0] DEBUG org.hibernate.hql.internal.ast.ErrorTracker - throwQueryException() : no errors
18:34:55.484 [vert.x-eventloop-thread-0] DEBUG org.hibernate.hql.internal.ast.QueryTranslatorImpl - HQL: FROM com.algosec.objectflow.objectimporter.model.Device
18:34:55.484 [vert.x-eventloop-thread-0] DEBUG org.hibernate.hql.internal.ast.QueryTranslatorImpl - SQL: select device0_.id as id1_0_, device0_.created_at as created_2_0_, device0_.updated_at as updated_3_0_, device0_.version as version4_0_, device0_.brand as brand5_0_, device0_.display_name as display_6_0_, device0_.name as name7_0_, device0_.uuid as uuid8_0_ from device device0_
18:34:55.484 [vert.x-eventloop-thread-0] DEBUG org.hibernate.hql.internal.ast.ErrorTracker - throwQueryException() : no errors
java.util.concurrent.CompletionException: java.lang.NoSuchMethodError: org/hibernate/query/internal/QueryImpl.(Lorg/hibernate/engine/spi/SharedSessionContractImplementor;Lorg/hibernate/engine/query/spi/HQLQueryPlan;Ljava/lang/String;)V (loaded from file:/C:/Users/yaakov.berkovitch/.m2/repository/org/hibernate/hibernate-core/5.4.28.Final/hibernate-core-5.4.28.Final.jar by @.) called from class org.hibernate.reactive.session.impl.ReactiveQueryImpl (loaded from file:/C:/Users/yaakov.berkovitch/.m2/repository/org/hibernate/reactive/hibernate-reactive-core/1.0.0.CR4/hibernate-reactive-core-1.0.0.CR4.jar by @.).
at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314)
at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:319)
at java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1081)
at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
at java.base/java.util.concurrent.CompletableFuture.postFire(CompletableFuture.java:610)
at java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1085)
at java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:478)
at org.hibernate.reactive.stage.impl.StageSessionFactoryImpl.lambda$null$0(StageSessionFactoryImpl.java:52)
at org.hibernate.reactive.stage.impl.StageSessionFactoryImpl$$Lambda$214/000000000000000000.handle(Unknown Source)
The code looks like:
    future = sessionFactory.withSession(
            session -> session.createQuery("FROM Device")
                    .getResultList().toCompletableFuture()
                    .thenApply(rows -> {
                        Collection<Device> result = new ArrayList<>(rows.size());
                        rows.forEach(row -> {
                            result.add((Device) row);
                        });
                        return result.stream();
                    })
    ).exceptionally(throwable -> {
        throwable.printStackTrace();
        return null;
    });

Dependencies:

Hibernate Reactive version 1.0.0.CR3
io.vertx:vertx-pg-client:4.0.3
io.vertx:vertx-core:4.0.3
Spring boot
Junit
Postgres
Java-11

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hibernate/hibernate-reactive/issues/746, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEIQ5IBDVY6VC2BZ4GVPSDTMOTRPANCNFSM44JKNPTQ
.


Pine Script: Highest and Lowest bar within the completed MACD histogram

I have started to learn pine scripting since last month and as you can expect, I am a beginner.
For the last few days, I've been trying to plot specific information on the chart but it did not go through well.. I would be grateful if you could help me with that...
I am trying to spot the highest bar within the completed MACD histogram(above 0), and the lowest bar within the completed MACD histogram(below 0). I have attached a screenshot for reference.
After spotting the last 2 highests, I would draw a trend line of them..
I know it would sound funny to you...but if someone can help with it or link me a reference, I would be very appreciated. Thank you!

My MACD histogram Pine Script.txt

This has nothing to do with Dart.

Have you solved this bro? can you help me? i am also trying to figure this out


Images in the docs are squashed

Anyone know a fix for this? Tagging @OriolAbril and @juanitorduz

Probably the same as this one: https://github.com/pymc-devs/pymc-examples/issues/671


chore(deps): upgrade jenkins-x/jx3-versions to version 1.1.50

from: https://github.com/jenkins-x/lighthouse.git

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign hferentschik
You can assign the PR to them by writing /assign @hferentschik in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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


Question : Is the repo well maintained and reactive ?

Hello everyone,
I'm asking this simple question because I'm coming from graphene-django and django-graphql-jwt where the repos are..well..quite dead and they didn't follow graphene-python evolutions so bugs remained for months (real monthS).
So since I decided to switch to a more maintained and reliable API framework (DRF), I'd like to know if this one follows quite well DRF and PyJWT evolutions.
I've seen that there's been a call to maintainers so that's also why I'm asking if it is well maintained or not.
Thanks in advance :)

hey, I maintain simplejwt while the owner has release perms. Though I’m
planning on transferring my role pf merging to someone else as school gets
increasingly busy... er when that happens. For now, the repo is up to date
with PyJWT 2.0.1, so I wouldn’t worry too much about maintainership since
PyJWT doesn’t change often. We just don’t add TOO many new features too
quickly. They’ll come, tho.
Hope that somewhat made sense.
On Fri, Jan 29, 2021 at 4:34 AM BRISBOIS Laurent<EMAIL_ADDRESS>wrote:

Hello everyone,
I'm asking this simple question because I'm coming from graphene-django
and django-graphql-jwt where the repos are..well..quite dead and they
didn't follow graphene-python evolutions so bugs remained for months
(real monthS).
So since I decided to switch to a more maintained and reliable API
framework (DRF), I'd like to know if this one follows quite well DRF and
PyJWT evolutions.
I've seen that there's been a call to maintainers so that's also why I'm
asking if it is well maintained or not.
Thanks in advance :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/SimpleJWT/django-rest-framework-simplejwt/issues/365,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOLG4VU2GZDKOAHGAQLBDCTS4J6KPANCNFSM4WYRS4PA
.

hey, I maintain simplejwt while the owner has release perms. Though I’m
planning on transferring my role pf merging to someone else as school gets
increasingly busy... er when that happens. For now, the repo is up to date
with PyJWT 2.0.1, so I wouldn’t worry too much about maintainership since
PyJWT doesn’t change often. We just don’t add TOO many new features too
quickly. They’ll come, tho.
Hope that somewhat made sense.
On Fri, Jan 29, 2021 at 4:34 AM BRISBOIS Laurent<EMAIL_ADDRESS>wrote:

Hello everyone,
I'm asking this simple question because I'm coming from graphene-django
and django-graphql-jwt where the repos are..well..quite dead and they
didn't follow graphene-python evolutions so bugs remained for months
(real monthS).
So since I decided to switch to a more maintained and reliable API
framework (DRF), I'd like to know if this one follows quite well DRF and
PyJWT evolutions.
I've seen that there's been a call to maintainers so that's also why I'm
asking if it is well maintained or not.
Thanks in advance :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/SimpleJWT/django-rest-framework-simplejwt/issues/365,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOLG4VU2GZDKOAHGAQLBDCTS4J6KPANCNFSM4WYRS4PA
.

@laurent-brisbois Check this out to get you started on SimpleJWT with Graphene: https://github.com/graphql-python/graphene/issues/249
Hope that helps.

@laurent-brisbois Check this out to get you started on SimpleJWT with Graphene: graphql-python/graphene#249
Hope that helps.

I do not want to use graphene and such anymore. These libraries appeared to be poorly maintainted.. That's why I switched to DRF and maybe DRF-simpleJWT soon :).


ipptool: MONITOR-JOB directive

Broken out from #221, this issue tracks the addition of a background job monitoring directive of the form:
MONITOR-JOB printer-uri job-id {
    test directives
}

If we do this, it'll happen in the libcups project...


[BUG] Possible MSD-AFQMC error when ndet=1?

Follow up of #266 #265

I updated the title to reflect this may or may not be an issue right? Feel free to change if confirmed.


Fix #3081, set client string encoding.

+1 (after formatting is fixed)

Arf I've just checked the spec:
extANSICodePage (2 bytes): A 16-bit, unsigned integer. ANSI code page descriptor being
used by the client (for a list of code pages, see [MSDN-CP]). This field is ignored by the client
and SHOULD be set to zero by the server.

@hardening Haha - good find - So I guess we can close the PR .. or maybe change it to add a comment containing your findings?

Not sure it's useless, in fact if the client sets it, then the server can read the value, and the answer to the client will be set to 0 and ignored by the client.
So it's a client to server message only...

So after the spec bible examination, I'd tend to +1.


build: Remove --experimental-wasm-bulk-memory flag

The --experimental-wasm-bulk-memory is no longer supported by Chrome.
Running this repo locally against Chrome Version 98.0.4758.80 (Official Build) (arm64), I'm able to run the unit tests without this flag.
With the flag in place, the tests exit early with an error message.

With the flag removed, the tests exit happily.

Do you know if this fixes OOM error? #339

Thanks for the PR!


bash scripts/infer_postnet.sh

| Unknow hparams:  []
Traceback (most recent call last):
File "/home/ai_linux1/Desktop/GITHUB/GeneFace-main/inference/postnet/postnet_infer.py", line 133, in
set_hparams()
File "/home/ai_linux1/Desktop/GITHUB/GeneFace-main/utils/commons/hparams.py", line 46, in set_hparams
assert os.path.exists(args.config)
AssertionError
Do you have any ideas how to solve this problem?thanks

Hello，Do you address this problem,I meet the same question?

Maybe because I name the folder errorly.


Proposal for handling UI exit

The above is just a mockup (ignore that I'm using 0.4.8 as backdrop)
This is a proposal for how to deal with user either wanting to just exit the UI, or shut down Sia altogether.
I removed the window frame (should also add a border)
An X was put back in the upper right hand corner
A Quit button was added on the Overview page
The intended behavior is:
Pressing the X minimizes the UI
Pressing "Quit" will exit the UI and siad
Selecting "Quit" should probably also launch a dialog warning user that the host will be shut down as well, and then provide a Confirm button.

@johnathanhowell is planning on implementing the approach you described in #210, where closing minimizes to tray and the tray contains a "Quit" option. I think this is a good approach, in line with how many apps work when they need to run in the background.

For desired behavior when quitting the UI, what about this?

If there is already an instance of siad running (on the default ports), do not quit siad when quitting the UI.
If no instance of siad is running when the UI starts, the UI starts one and quits it when the UI quits.

This was the desired behavior @DavidVorick mentioned a few weeks ago when we were discussing it.

@VoidingWarranties A remaining problem is users that run a host, started when the UI is opened. When the UI is closed, the host shuts down too in your scheme.

@VoidingWarranties There is already an option in the siad wrapper and defaulted to false in the UI called detached.
if true - run siad as either a detached, background process and doesn't exit it with the UI's closing.
if false - start siad if not already running, close upon the UI's closing.
I didn't make a settings page/plugin ( #47  ) to change said setting, but if you changed it in the config.json manually, you'd see the results.

I think this suggestion of providing buttons to close siad with the UI is approaching the problem from a more typical perspective, but I'd sooner like to see a settings plugin where one can change the persistence of siad.
This means that hosts could set detached to true and renters/whoever else could set/leave it as false

@pmknutsen hmmm good point. I like your suggested approach. Since the host is a special case, perhaps it can be special cased.

If the user isn't running a host, quitting the UI quits siad too.
If the user is running a host, quitting the UI brings up the dialog:
"It looks like you're running a host. Quitting Sia will also stop your host. Would you like to minimize Sia instead?" with the buttons "minimize" and "quit"

@VoidingWarranties Consider also renters and "power users" who want to be up to date on file repairs and blockchain synchronization. I think a shutdown of siad should always be very explicit, with a "Quit" button or similar (unless a different behavior is set by the user in a Settings plugin as suggested by @Mingling94).

Okay, sounds good!
On Wed, Feb 17, 2016 at 11:41 Per Knutsen<EMAIL_ADDRESS>wrote:

@VoidingWarranties https://github.com/VoidingWarranties Consider also
renters and "power users" who want to be up to date on file repairs and
blockchain synchronization. I think a shutdown of siad should always be
very explicit, with a "Quit" button or similar (unless a different behavior
is set by the user in a Settings plugin as suggested by @Mingling94
https://github.com/Mingling94).
—
Reply to this email directly or view it on GitHub
https://github.com/NebulousLabs/Sia-UI/issues/213#issuecomment-185290066
.

Anyway, @johnathanhowell seems to have made improvements with #214 so I'll close this for now.


update is-generator-function

check used in co@4+
btw npm test not works in iojs@2

Coverage remained the same at 100.0% when pulling 306ed041cd0c361f1437b27984eaa98e868036e1 on chorks:master into 4cdb310598d51f3f1614fc6deea4a92b42d09656 on blakeembrey:master.

Are there any reason for the changes, other than because it's what co does?

plus

apply feross/standard (sorry if you dont want it)
change mocha with assertit which is testit on steroids - faster and smaller than mocha
update travis to install and check standard istanbul-harmony and coveralls

Are there any reason for the changes, other than because it's what co does?

amm.. cuz running tests not works on iojs

amm.. cuz running tests not works on iojs

Did you even look at why? node: bad option: --harmony-generators Just remove that option.

Im not trying to force and promote assertit but it is so small and easy.

Did you even look at why?

yea

I'm going to close this issue unless there's a reason for the code change, but I will tidy up the code since I use standard in my more recent projects. I won't, however, be removing mocha and chai.


runAsNonRoot possible ?

Spegel version
0.0.27
Kubernetes distribution
Talos 1.8.3
Kubernetes version
1.31.1
CNI
flannel, I think ? Whatever the default in Talos is
Describe the bug
Spegel won't start with runAsNonRoot, with the configuration container logging this :
{"time":"2024-12-08T12:53:50.440469719Z","level":"ERROR","source":{"function":"main.main","file":"/build/main.go","line":86},"msg":"run exit with error","err":"stat /etc/cri/conf.d/hosts/_backup: permission denied"}

The directory is empty :
❯ talosctl --talosconfig talosconfig -n mynode list /etc/cri/conf.d/hosts/
NODE            NAME
talos-fdm-9ig   .
❯

Explicitly setting runAsNonRoot: false does let it start, and as far as I can tell it works. My question is can I do anything to make it run as non root, is there some specific runAsUser or fsGroup that would make it work, or is root required on Talos ?
If it's required, I'd suggest making a note of that in the compatibility notes as it seems the default does not work.
Thanks

Running as non root is not possible at the moment because the UID is required to communicate with the Containerd socket. This is not specific to Talos but for all Kubernetes flavors.


Feature/support use changelogs ubuntu com

feat: Add support for downloading changelogs from changelogs.ubuntu.com
Using new arg --use-changelogs-ubuntu-com will download changelog direct from
changelogs.ubuntu.com instead of querying launchpad API.
This is useful if it is a kernel that was copied from a private PPA,
for example during an embargoed CVE where the public build for that source
package will not be the most recent and will not contain the most recent
changelog. This option assumes that the package is in the main Ubuntu archive.

Usage example:
❯ ubuntu-package-changelog --entries=1 focal Updates linux-gkeop --use-changelogs-ubuntu-com
linux-gkeop (5.4.0-1048.51) focal; urgency=medium

  [ Ubuntu: 5.4.0-120.136 ]

  * CVE-2022-21123 // CVE-2022-21125 // CVE-2022-21166
    - cpu/speculation: Add prototype for cpu_show_srbds()
    - x86/cpu: Add Jasper Lake to Intel family
    - x86/cpu: Add Lakefield, Alder Lake and Rocket Lake models to the to Intel
      CPU family
    - x86/cpu: Add another Alder Lake CPU to the Intel family
    - Documentation: Add documentation for Processor MMIO Stale Data
    - x86/speculation/mmio: Enumerate Processor MMIO Stale Data bug
    - x86/speculation: Add a common function for MD_CLEAR mitigation update
    - x86/speculation/mmio: Add mitigation for Processor MMIO Stale Data
    - x86/bugs: Group MDS, TAA & Processor MMIO Stale Data mitigations
    - x86/speculation/mmio: Enable CPU Fill buffer clearing on idle
    - x86/speculation/mmio: Add sysfs reporting for Processor MMIO Stale Data
    - x86/speculation/srbds: Update SRBDS mitigation selection
    - x86/speculation/mmio: Reuse SRBDS mitigation for SBDS
    - KVM: x86/speculation: Disable Fill buffer clear within guests
    - x86/speculation/mmio: Print SMT warning

for the record - https://github.com/toabctl/ubuntu-package-changelog/pull/17 is the fix for the problem described here.

I would like to only use the LP API. and given that the problem you described got fixed, are you ok with not merging this?

Close in favour of https://github.com/toabctl/ubuntu-package-changelog/pull/17


Fix issue with moduleName slugify filter

Just a small fix to a moduleName filter. Now slugifying shoud work properly.
Thanks for all your great work, Sindre!

What issue is this fixing?

None of them (I mean there is no open related issue in your repo). Should I create one? The problem in the following: if you try to use few words, separated by space symbol, as your module name (eg.: test module) on the first prompt - the result in package.json will be test module (which is wrong). My small fix will slugify module name and finally it will be test-module.

Should I create one?

No

Thanks for the code review and explanations. Seems slugifying was broken since this PR. I've fixed scoped modules regexp (it was returning true for any module name on prompt, no matter scoped name or not). Now it should work just fine, so the result will be:
Input:
- What do you want to name your module?
> awesome module

Output (package.json):
"name": "awesome-module",
"repository": "username/awesome-module"

Input:
- What do you want to name your module?
> @scoped/module

Output (package.json):
"name": "@scoped/module",
"repository": "username/module"

// @JonnyBurger

Thanks :)

Thanks for the fix! I will fix any issues with my PR in the future, given that I have the chance to. You were too fast :)
Cheera


wormhole receive x-y-z crashes for large files

When sending a large file ~580MB and entering the receive code directly like:
wormhole receive 5-racketeer-music

wormhole crashes with:
ok? (y/N):
transfer rejected
TransferError: transfer rejected

This also breaks the validity of the code so the file has to be sent again generating a new code
when manually doing:
wormhole receive

and entering 5-another-code manually all works fine then.

That sounds like the receiving side correctly negotiated the key, but then the user rejected the transfer by not typing y (or Y or yes) at the prompt, and yeah in the current implementation, rejecting the transfer terminates the program on both sides. This happens before the file is sent (at least when sending single files, rather than a directory). So the size of the file shouldn't matter.
Providing the code on the command line, or entering it manually/interactively, should behave exactly the same (if you type it correctly). Typing it interactively lets you use tab-completion, which might increase the chances that you get it right, but otherwise they ought to do the same thing.
Does that address the problem you saw?

that is correct, if I understand you correctly. An your explanation makes sense then. However, I was just surprised that it automatically assume N as opposed to waiting for user input. That's all fine if that's the desired/implemented behaviour. I just found that a tat counter-intuitive.
Thanks for clarifying.

Hm, fair point, maybe "Y" should be the default. I'll open a separate ticket for that question. Thanks!


Add newline on clicking at the bottom of the document

This would be an extremely convenient feature (like notion).
Currently it kinda gets hard to add newline, if you have a horizontal rule above

Closed in https://github.com/jackyzha0/tabspace/commit/5d4e7e569c435c9a151107a11991f9708e7140bf


[General][All] Add README description for all labs

Currently, the description of the labs is documented on the main page and the individual labs have no documentation of what the lab is all about. Add documentation to individual labs to remove any confusion for the users of bootcamp

Merged  https://github.com/gpuhackathons-org/gpubootcamp/pull/62


[trace] Tracker

[ ] wrap database driver in adapter?

TODO

[ ] #28 add abstraction layer between open tracing interface and implementations

Ref

Dapper https://github.com/at15/go.ice/issues/11
https://github.com/census-instrumentation/opencensus-go
https://rakyll.org/latency-profiling/

talks about os/exec database/sql net/http which we can do in go.ice while go itself does not support it

https://rakyll.org/profiler-labels/ it is supported in opencensus-go, I think we could add this in our tracing library so it can works for opentracing
[ ] https://github.com/lttng never heard of it before ... found when google ceph zipkin (it's a gsoc project I saw in 2016) http://victoraraujo.me/babeltrace-zipkin/
https://github.com/mitchellh/go-server-timing support send timing to browser, just flat span though
https://software.intel.com/en-us/articles/pin-a-dynamic-binary-instrumentation-tool Intel Pin tool ... this should be put into benchhub though ...

not high priority


Updated APIs to match other language clients and opensearch openapi spec

Description
Updated APIs to match other language clients and opensearch openapi spec. APIs added to "_patch" are manually written. Other APIs added are Generated using openapispec.
Deprecated APIs: They are moved into client/_patch.py
list_all_point_in_time, create_point_in_time, health_check, update_audit_config, delete_point_in_time
Newly Added APIs: They are moved into corresponding namespaces
get_all_pits, create_pit, health, update_audit_configuration, delete_all_pits, delete_pit
Issues Resolved
Closes #499, #500, #501
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Hi @florianvazelle, I would greatly appreciate it if you could kindly review this PR and share your feedback whenever it's convenient for you. Thank you!

This looks great! Can we also start adding the generation details in a markdown file? For example, what the patch file is supposed to be? How the generator works etc? I see there is already https://github.com/opensearch-project/opensearch-py/blob/main/DEVELOPER_GUIDE.md#running-python-client-generator

@VachaShah, I'll include these details in my upcoming PR. I'll create a markdown file explaining the generator's functionality and the client structure, including what's placed in patch files. You can find most of the information here, and I'll ensure it's added to the repository soon.

@VachaShah, Shall we merge this


QUnit - Better diff output

For the GSoC project "QUnit - Better diff output", what are the requirements and details??
Any other issues apart the ones mentioned in https://github.com/jquery/qunit/issues/364 ???
@leobalter @jzaefferer Please advice.

#364 is our meta ticket for the topic, that's definitely the best reference.
One thing not mentioned there, that came up with the recent PRs: We should have better tests for diffs. The ones you screenshotted in #764 are a good starting point. A visual test page (failing tests?) would be good for manual, visual verification. Automated tests that somehow prevent regressions would also help, maybe by checking the length of a diff, ensuring that changes to the diff don't make it worse (if longer always means worse).
Another idea: Do some research across JS testing frameworks. See what others to about diffing, if at all. See if we should (eventually) extract our diff module into a standalone module, that other frameworks could use. Should find at least two frameworks actually interested in that before making any changes on our end.
That's two additional tasks I can think of right now. There's probably more.
I'm assuming you're asking this to write your proposal. If you need a reference, this one (for jQuery UI) seems pretty decent to me.

@jzaefferer Do i make a proposal and put it on gist as well??

Sure, that way we can review it before the official submission process starts. Doesn't have to be a gist, anything you can share with us should work.
PS: One question mark is enough ;-)

@jzaefferer Thanks :-D

@jzaefferer @leobalter Hey, I have a doubt in the proposal. How do i make my timeline. I dont know how much time each task could take. How do i decide that?

@jzaefferer I've two questions in my mind:

For the GSOC project do we need to improve the current diff algorithm of @jeresig or as the other tickets suggest that we can use some already existing libraries for diff?

If we are using already existing library I'm not sure why we should extract that module into standalone module (It's already there)?

Thanks.

@gauravmittal1995 take the time since you started your first PR to landing it (you may need to extrapolate that, since its still open). Then multiply that by two and you have a rough estimate. Or just guess. Or assume one week per task. Don't worry too much about it, time estimates are never something to stick strict deadlines to.
@shivamdixit check out #772, that should answer both your questions.

@jzaefferer Thanks

Closing this since there's nothing to discuss here and the underlying diff-related issues are enough.


adding kadane's algorithm in c

Description adding kadane's algorithm in c
Please include a summary of the changes you have made in regard with this issue.
Fixes #(issue number) #287
Type of change
Please delete options that are not relevant

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

Checklist:

[x] I have read the contribution guidelines before making this PR.
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented in my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation (Language folder or any other readme instructed to)
[x] My changes generates no new warnings
[x] I have added tests that prove my fix is effective or that my feature works

in reference to issue #287

in reference to issue #287 update the kadane's algo in c

@YashSaxena9 Again strong sus of plagiarism :
See this: (Maybe I am wrong )
https://gist.github.com/sujaykundu777/a1a72c88291f9ee72aaba02b80159bf7

I did it on my personal IDE.It's the basic code find everywhere same.


Bug when filling in errata table

Originally from https://github.com/metanorma/metanorma-iso/issues/296 @rggibb

Also the Revision history table was problematic, I removed the Table D.1 header, and made the header row repeat at the top of each page .. I think that was only possible once it was reformatted as .docx, and I recall there was a deeper problem that required me to start the table again as a empty table and progressively copy the rows across, but I’m afraid I’ve forgotten the details.
If you don’t know exactly what that might have been, I’ll recreate it and find out. I seem to recall all the tables that may have had double cell boundaries or something that I couldn’t convert back to single cell boundaries ...

Right now we don't support "revision history" natively, maybe we can port something from NIST to OGC?

Originally from: https://github.com/metanorma/metanorma-iso/issues/296
We can probably generalize the Errata model we have for the other flavor.
We can inherit from the BasicDoc "ChangeSet" and "Change" models and make the "Modified node" to support a link and plain text.

(from: https://github.com/metanorma/basicdoc-models)

Am reluctant to implement without evidence of a fixed structure for errata from OGC; and since this seems to have been a joint ISO structure originally, the warrant for this cannot extend to ISO anyway. @ronaldtse?

This presupposes serious engagement with SDOs, to establish their requirements for errata.

@opoudjis pending feedback from OGC now.

Ticker superseded by https://github.com/metanorma/metanorma-ogc/issues/152

Am reluctant to implement without evidence of a fixed structure for errata from OGC; and since this seems to have been a joint ISO structure originally, the warrant for this cannot extend to ISO anyway.

ISO doesn't have Errata, they issue Errata using a new TC or a new revision.


Vulnerability roundup 83: gparted-1.1.0: 1 advisory

search, files

[ ] CVE-2014-7208 (nixos-unstable)

Scanned versions: nixos-unstable: 8130f3c1c2b. May contain false positives.

Looks like false positive.
https://seclists.org/fulldisclosure/2014/Dec/77
 vulnerable version: <=0.14.1 and we are shipping 1.1.0.

Yes, the version match expression in the CVE lacks a leading zero.


Transparent Background AvaloniaView in a Android project

Hello,
I am embedding an AvaloniaView in my AvaloniaUI Android project but can't make this one having a transparent background.
I set the Background to Transparent in the UserControl axaml side
        <UserControl xmlns="https://github.com/avaloniaui"
         xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
         xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
         xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
         xmlns:viewModels="clr-namespace:AvaloniaApplication1.ViewModels"
         mc:Ignorable="d" d:DesignWidth="800" d:DesignHeight="450"
         x:Class="AvaloniaApplication1.Views.MainView"
         Foreground="White"
     Background="Transparent">

In the MainActivity, I made a red layout (to test) and added the AvaloniaView as a child to it.
       _layout = new RelativeLayout(this);
        _layout.SetBackgroundColor(Color.Red);

        _avaloniaView = new AvaloniaView(this);

        (...) // some init code taken from AvaloniaMainActivity

        _avaloniaView.SetBackgroundColor(Color.Transparent); // Added this to be sure
        _avaloniaView.LayoutParameters = new RelativeLayout.LayoutParams(ViewGroup.LayoutParams.MatchParent, ViewGroup.LayoutParams.MatchParent);

        _layout.AddView(_avaloniaView);

But the background keeps beeing black no matter what.
If I launch the windows client (with the MainWindow having Transparent Background and Transparent TransparencyBackgroundFallback), the background is indeed transparent. But Android keeps ignoring it.
Am I missing something ?
Thanks for your help

Here is some screenshots,
The result in android :

The result in windows :

can you try this? https://stackoverflow.com/questions/2176922/how-do-i-create-a-transparent-activity-on-android

Hello,
Thank you for your reply, but the activity itself does not need to be transparent, just the AvaloniaView.
My goal actually is to be able to have the avalonia view in top of some native android view.
In this particular test, the relativeview when the avaloniaview is added have a red background. If the avaloniaview has a transparent background, I should see the red one.

Acc. to @emmauss feedback, I think this issue can be closed as not planned because it seems to be impossible to implement.

Okay going to reopen the issue as I just learned it's not impossible, but currently not possible.


fix issue #1171 - slide alignment issue

Fix issue #1171 and maybe more
Slider doesn't calculate offsets correctly when slider isn't full screen because when componentDidUpdate is called and updates the state based on an initState call it uses the return from Dimensions.get('window') instead of the value from props if there is one. The value that should be used is calculated just before the incorrect value is used.
Bug was evident if you created a slider with a height and width different to the values of Dimensions.get('window'). On initial render it displayed correctly but on swiping you would end up with offsets depending on the difference between props.height/props.width and the values coming from Dimensions.get('window')
This fixes that

LGTM

Thanks for the fix, works great for me. Any idea on when the build issue might be fixed and the next release might be available?

Thanks for the fix, works great for me. Any idea on when the build issue might be fixed and the next release might be available?

Thanks for the fix, works great for me. Any idea on when the build issue might be fixed and the next release might be available?

Thanks for the fix, works great for me. Any idea on when the build issue might be fixed and the next release might be available?


Sender name is clipped from bottom in mobile

Letters like g, y, p etc. are clipped from the bottom in mobile. Check the screenshot below -

@zulipbot claim