Public schemas

Problem description
As a user, I would like for my schemas to be discoverable beyond just my own business infrastructure silo. Currently, all schemas are stored in an internal database, therefore, we need to add the option to store schemas in a publicly accessible database or distributed storeage.
Requirements
The action of creation a schema must be recorded in a specific topic in Hedera, associated with the specific Authority. The internal database currently used needs to be replaced with an IPFS node[s] for storing all system artefacts.
Definition of Done
Acceptance criteria is fulfilled
Guardian setup/launch creates an IPFS node for content storage (instead of the DB)
Acceptance Criteria:
Database Data Analysis BRD? Silo Architecture? Users and User Group Lists?

As per @sergmetelin  the Mindset we need to have is that Hedera is the Source of Truth. Every single record needs to go to Hedera first. Everything needs to be attested by the Root Authority. All of this needs to be recorded on the Hedera Consensus Service.
As per @sergmetelin , we should use IPFS for now. Everything is public and all SDK’s are available.
Definition Of Done is in the Schemas, there needs to be post a link to the Schema in the topic after we post the Schema on IPFS, we also post a Topic Message. Topic needs to be an auditable log of everything that the Root Authority does. Currently, there is no access to the linked Schema, therefore it is not auditable. Root Authority needs to create a schema, the schema is posted to IPFS, then the ID is posted to the topic. Every Root Authority action needs to be recorded under that topic, every schema, every credential. Policy has its own topic, and Root Authority has its own topic. From the moment the Root Authority came in, the Guardian should be tracking ALL of the events. Its important to have Hedera as a Source of Truth in disaster recovery (DR) situations (Shawn needs to add this as another Issue)
DOD – A Hedera Improvement Proposal, new Features, Frameworks, all in a Public manner needs to be issued describing how this works. This may be an addition to HIP 28 or a HIP 28 Updated. A flag describing how the Policy Engine works. Creating a HIP will be an entirely new Issue, @envisionblockchainpm  to create as an Action Item.

We need to gather more requirements from Hedera on this ticket during todays Grooming.

Next step is to have a discussion on this as per this mornings Scrum.

Next Step for this is to have a meeting with Serg and for Andrey to have a Review Document completed prior to this meeting. Shawn to get Serg's timing on meeting next week for another Discovery Session,

Next step is on Andrey to reach out to Serg for a one on one Tech Talk

@sergmetelin Upon deeper analysis I have concerns that using IPFS here provides any real advantages. I'll summarise them here, and hopefully we can discuss them either in a meeting of asynchronously in the ticket.
There are three options of enabling storage of information on IPFS:

running your own nodes
paying a service provider such as Pinata for hosting content in IPFS
a combination of the two above

To host data on IPFS it requires running you own server, and saving content onto it. By default this information would be only available on this one server (not replicated), and only for the duration while the application/node is running. The data only gets replicated when someone else from elsewhere needs to access the file, and only while it's used by them.
Instantiating and operating an IPFS node is not a trivial task, and is likely to provide a barrier to entry comparable to, if not more severe, using an unfamiliar API. Introducing IPFS technology will complicate Guardian solution architecture. It is much easier and cheaper to achieve geo-replicated and backed-up storage using commercial cloud providers services.
For demo/test environment running your own node seems to be the only option since costs and account setup etc for just with storing test/demo data seems to be unacceptable.
The alternative is to use Pinata service offering for IPFS access. This is simpler since no technical operations are required, and simpler to implement because Pinata offers an API for storage and retrieval. However it involves costs (if the usage goes beyond the very small volume of 'free tier') and complexities of setting up and maintaining accounts. It also introduces dependency on the external commercial service provider.
I propose to instead introduce a solution based on a new set of Guardian APIs for discovering and accessing published schemas and policies on the instance. As such each instance of the Guardian would have a well-known API access point which can be accessed in various ways.

The outcome of the conversation is the following design:

Local Guardian instance includes a DB which contains drafts and 'cached' published policies and schemas
When a schema or a policy version is published it becomes immutable and is uploaded onto the IPFS via nft.storage API. NFT Storage guarantees the permanence of the uploaded info on IPFS.
This should work with the versioning functionality as per #46
There will be another ticket to do with the 'discoverability' of assets (Policies, Schemas) and their 'import' into a Guardian instance

Next step:

@Pyatakov design session with development for the functionality

Alex has this been Designed and have you reviewed with the Development Team?


Hiding markers is still displaying clusters with size 0

Hi,
I'm currently building an interactive map with markers. So my code is adding a map with various markers, then adding a clustering and everything is working fine. Issue is appearing when I'm starting to hide some markers, by using marker.setVisible(false) and then rendering again my clusterer, with markerClusterer.render(). I can see on my map some cluster with size 0 appearing where I've hidden some markers.
Environment details
1.Using script api  <script<EMAIL_ADDRESS>2. Inside a vuejs app
Steps to reproduce

Create a map
Add various markers
Add a clustrer
Render it to see everything is fine
Hide markers dynamically, with a button click for example
Render again the clusterer

You should see like me clusters of size 0
Code example
Rapid fiddle here : https://jsfiddle.net/2vzayxc4/3/
Click on hide button under the map, and zoom out to see it happening.
Thanks for the help, it's driving me crazy ;)

@yanngit Thank you for opening this issue. 🙏
Please check out these other resources that might be applicable:

Support Console - If you have a support contract.
Discord - chat with other developers
StackOverflow - use the google-maps tag
Google Maps Platform issue trackers

This is an automated message, feel free to ignore.

In the previous markerclustererplus there is an option ignoreHidden that would ignore those markers with visible equal false
Can that be added to this version?

The workaround is to remove the marker from the MarkerClusterer when removing from the map or setting visible to false.
There are other related cases that could maybe be addressed:

is marker.getMap() the same as that of the clusterer?
is marker.getMap() null?
marker visibility is false?

So far the only workaround, in my case, is to use the clearMarkers then addMarkers methods.

I worked around this issue by adding the renderer and setting the visibility of a cluster marker like this:
visible: cluster.count > 0,

I encountered the same problem. If you use clearMarker first and then addMarker, the count will be 0.

In the renderer for cluster marker, put "visible: count > 1".


add linda to contributors list

@blindacai, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added Facebook share and tweet feature to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.

Hi @Roshanjossey , I feel this is great for those who don't have much experience with open-source to test the waters as one concern of making pull requests stems from the fear of making mistakes (and basically causing troubles)
Overall your tutorial is thoughtful and straight forward to follow.
During the process, there are 2 places I was not quite sure at first:

Click on Compare & pull request: I saw it both on your repo and my forked one and was not sure which one to click
After clicking the button, I got 'cannot auto merge conflict' and wondered why it showed two lines of changes while I had only added one line
So I watched 2 short Youtube videos and were able to move forward

There are probably many text based and video based tutorials about making pull request, but the value of your project idea it to make it actually happen


Add Metatests

Related #3347
It is expected that the AppVeyor CI failed.
The meta tests run only on AppVeyor CI and locally.
The meta tests by default check only new and changed files from "current" PR (compared with origin/master).
Therefore, the PR for demo includes test files for each type of validation - this is what causes CI tests to fail. These test files should be deleted before merge.
Now check of all files in Repo is blocked. We can allow it if necessary for example for night builds.
After merging the PR we will have to produce every modified file in line with the meta tests.

I think it's more common to use git commit hooks to enforce the sorts of things this PR is trying to catch.

It seems users (IDEs) can silently ignore hooks. So anyway we need scripts to perform approved checks.

An IDE could not ignore a server side hook.

People can all :-)
Even if we add hooks, we still need a script for full code checks, don't we?
With specific regard to hooks, GitHub addins look more attractive. If MSFT can turn such addins for code checks it will be great. Is it possible?

There is code to automatically fix most of the tests you have added here:  https://github.com/PowerShell/DscResource.Tests/blob/dev/MetaFixers.psm1
I'd say we separate the hook issue.  These tests should be identified in some way that we can create a hook, but we need the tests before we can create a hook.

@TravisEz13 Thanks! We should be careful with MetaFixers.psm1:

Not all files is UTF8 (I don't risk to fix this) and some files contain special symbols.
Many test files contain tabs and broken formatting

What is our plan? What should I do next?


Exported subpaths of @libp2p/crypto

Version:

4.1.6

Platform:

Mac OS latest version + linux (docker) in github codespace, both in node.js

Subsystem:

Crypto package
Severity:

Hesitate between high and medium, depending on the scope
Description:
When installing the package @libp2p/crypto in my (nestjs) project, I cannot import any of the package exports so I am unable to use the functions.
I get the following error at runtime :
Error: Package subpath './keys' is not defined by "exports" in ...
But if I go in the package.json, it is well exported. I note, however, that there is no main field in the package.json wich disable the "root" usage (without subpath after the package name)
I first though that my configuration was broken in my codebase so I created another project, simple typescript index.ts setup this time and I get the same error. I get exactly the same issue in a codespace too (so it doesn't seem to come from my machine).
How can I use this package in a node.js project ?
Steps to reproduce the error:

Create a basic typescript project with only a package.json, tsconfig.json and a index.ts file
Install @libp2p/crypto package using your package manager
Put this content in the index.ts :

import { generateKeyPair } from "@libp2p/crypto/keys";

const kpr = generateKeyPair('Ed25519');

console.log(kpr)

Compile and run the project

This is likely the result of 'require' being used instead of 'import' by the compiled typescript.
https://nodejs.org/api/packages.html#conditional-exports

This is likely the result of 'require' being used instead of 'import' by the compiled typescript.
https://nodejs.org/api/packages.html#conditional-exports

@tabcat The import is there : https://github.com/libp2p/js-libp2p/blob/a82ff82211f187e6ad6eef2f73e3221f6fc7b444/packages/crypto/package.json#L60

Can you post your tsconfig.json please?  You may be compiling to CJS instead of ESM.  Otherwise can you please share a link to your project?

@achingbrain I am indeed compiling to CJS but I cannot change this (changing to ESM break everything in nestjs app) Is it possible to add require exports instead ? I am sure I am not the only one with this case.

This is an ESM-only module so adding require exports will not work, since they'd be pointing to ESM files.
There's an example of how to use Helia with nestjs - it uses libp2p so has all the config you need to get it working.
The other option you have is using dynamic imports to load ESM, though you'll need to make sure your transpiler doesn't change import('libp2p') into require('libp2p').

I'll check that, thank you for all your quick answers


ListView Control on a WinForms project does not fire events

Describe the bug
Created a new project in .net Core 3.0
Added a ListView to the form that I populate based on user actions (button click works just fine)
The events on the listview however do not get firred.
To Reproduce
Steps to reproduce the behavior:

Visual Studio 2019, Core 3.0 Release 3.0.100-preview7-012821
Run this the File New  Windows Forms App(.Net Core) Project
My project looks like this

<Project Sdk="Microsoft.NET.Sdk.WindowsDesktop">

  <PropertyGroup>
    <OutputType>WinExe</OutputType>
    <TargetFramework>netcoreapp3.0</TargetFramework>
    <UseWindowsForms>true</UseWindowsForms>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="System.Data.SqlClient" Version="4.7.0-preview7.19362.9" />
    <PackageReference Include="System.Windows.Forms.DataVisualization" Version="1.0.0-prerelease.19218.1" />
  </ItemGroup>
</Project>

The form uses the "normal" template
partial class Form1
{
	/// <summary>
	/// Required designer variable.
	/// </summary>
	private System.ComponentModel.IContainer components = null;

	/// <summary>
	/// Clean up any resources being used.
	/// </summary>
	/// <param name="disposing">true if managed resources should be disposed; otherwise, false.</param>
	protected override void Dispose(bool disposing)
	{
		if (disposing && (components != null))
		{
			components.Dispose();
		}
		base.Dispose(disposing);
	}

	#region Windows Form Designer generated code

	/// <summary>
	/// Required method for Designer support - do not modify
	/// the contents of this method with the code editor.
	/// </summary>
	private void InitializeComponent()
	{
	// controls before ...
	this.ListViewControlItems = new System.Windows.Forms.ListView();
	// other controls after ...

	//
	// ListViewControlItems
	//
	this.ListViewControlItems.Dock = System.Windows.Forms.DockStyle.Fill;
	this.ListViewControlItems.FullRowSelect = true;
	this.ListViewControlItems.HideSelection = false;
	this.ListViewControlItems.Location = new System.Drawing.Point(0, 37);
	this.ListViewControlItems.MultiSelect = false;
	this.ListViewControlItems.Name = "ListViewControlItems";
	this.ListViewControlItems.Size = new System.Drawing.Size(464, 413);
	this.ListViewControlItems.TabIndex = 2;
	this.ListViewControlItems.UseCompatibleStateImageBehavior = false;
	this.ListViewControlItems.View = System.Windows.Forms.View.Details;
	this.ListViewControlItems.SelectedIndexChanged += new System.EventHandler(this.OnSelectedTrainingFileChanged);

	}
}

the "Code Behind" part of the form is like this:
public partial class Form1 : Form
{
	public Form1()
	{
		InitializeComponent();
		ListViewControlItems.Click += ListViewControlItems_Click;
	}

	private void ListViewControlItems_Click( object sender, EventArgs e)
	{
		throw new NotImplementedException();
	}
}

neither the Click event or the SelectedIndexChanged event ever get invoked

Expected behavior
The button click event's get invoked without any problem, I'd expect the Listview to invoke as well. I now add a button to trigger the SelectedIndex change event and works just fine, also knows if any items are selected
private void OnSelectedTrainingFileChanged(object sender, EventArgs e)
{
if (ListViewControlItems.SelectedItems.Count > 0)
{
ConfigPropGrid.SelectedObject = ListViewControlItems.SelectedItems[0].Tag as NativeConfig;
}
else
ConfigPropGrid.SelectedObject = null;
}
Screenshots

Additional context
Build output:
● Started at 19:17:54
1>------ Build started: Project: CATS.ML.Interfaces, Configuration: Debug Any CPU ------
1>You are using a preview version of .NET Core. See: https://aka.ms/dotnet-core-preview
1>CATS.ML.Interfaces -> D:\Source\Cats.ML\CATS.ML.Interfaces\bin\Debug\netstandard2.1\CATS.ML.Interfaces.dll
2>------ Build started: Project: Cats.Deepbook.IBApi, Configuration: Debug Any CPU ------
3>------ Build started: Project: Cats.ML.Core, Configuration: Debug Any CPU ------
4>------ Build started: Project: CATS.ML.Data, Configuration: Debug Any CPU ------
4>You are using a preview version of .NET Core. See: https://aka.ms/dotnet-core-preview
3>You are using a preview version of .NET Core. See: https://aka.ms/dotnet-core-preview
2>Cats.Deepbook.IBApi -> D:\Source\Deepbook\Cats.Deepbook.IBApi\bin\Debug\netcoreapp3.0\Cats.Deepbook.IBApi.dll
3>ML\Data\Versatile\VersatileMLDataSet.cs(103,64,103,89): warning CS0067: The event 'VersatileMLDataSet.OnColumnsWithNoAddedValue' is never used
3>Cats.ML.Core -> D:\Source\Cats.ML\cats.ml.core\bin\Debug\netstandard2.1\Cats.ML.Core.dll
3>Done building project "Cats.ML.Core.csproj".
4>CATS.ML.Data -> D:\Source\Cats.ML\CATS.ML.Data\bin\Debug\netstandard2.1\CATS.ML.Data.dll
5>------ Build started: Project: Cats.Deepbook.Shared, Configuration: Debug Any CPU ------
5>DeeBookNativeBarBuffer.cs(42,81,42,96): warning CS0067: The event 'DeeBookNativeBarBuffer.OnCrazyMovement' is never used
5>Cats.Deepbook.Shared -> D:\Source\Deepbook\Cats.Deepbook.Shared\bin\Debug\netcoreapp3.0\Cats.Deepbook.Shared.dll
5>Done building project "Cats.Deepbook.Shared.csproj".
6>------ Build started: Project: CATS.Deepbook.NetworkTrader, Configuration: Debug Any CPU ------
6>CATS.Deepbook.NetworkTrader -> D:\Source\Deepbook\CATS.Deepbook.NetworkTrader\bin\Debug\netcoreapp3.0\CATS.Deepbook.NetworkTrader.dll
========== Build: 6 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
● Finished at 19:17:56 (total time 2.34s)

dotnet --info
.NET Core SDK (reflecting any global.json):
 Version:   3.0.100-preview7-012821
 Commit:    6348f1068a

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.18362
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\3.0.100-preview7-012821\

Host (useful for support):
  Version: 3.0.0-preview7-27912-14
  Commit:  4da6ee6450

.NET Core SDKs installed:
  2.1.800-preview-009677 [C:\Program Files\dotnet\sdk]
  2.1.800-preview-009696 [C:\Program Files\dotnet\sdk]
  2.1.800 [C:\Program Files\dotnet\sdk]
  2.2.300 [C:\Program Files\dotnet\sdk]
  2.2.400-preview-010195 [C:\Program Files\dotnet\sdk]
  2.2.400-preview-010219 [C:\Program Files\dotnet\sdk]
  2.2.400 [C:\Program Files\dotnet\sdk]
  3.0.100-preview6-012264 [C:\Program Files\dotnet\sdk]
  3.0.100-preview7-012821 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.2.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.2.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.0.0-preview6.19307.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.0.0-preview7.19365.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.2.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.0.0-preview6-27804-01 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.0.0-preview7-27912-14 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 3.0.0-preview6-27804-01 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 3.0.0-preview7-27912-14 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

This issue was moved to dotnet/winforms#1607


Correctly set the Source IP to the received Destination IP with ipv4/ipv6

Previously, the oob data was just stored and sent to WriteMsgUDP but it ignores the Src field when writing. Instead, now it is setting the Src to the original Dst and handling IPv4 IPs over IPv6 correctly.
Unfortunately, we still need the Windows-specific file since ReadMsgUDP is not implemented in Windows:
// BUG(mikio): On NaCl, Plan 9 and Windows, the ReadMsgUDP and
// WriteMsgUDP methods of UDPConn are not implemented.

Additionally, SetControlMessage is not supported on Windows either.
I've tested nothing broke with Windows, and Linux ipv4/ipv6 works as expected.

@miekg Updated to remove any external package dependencies. I also added tests to verify the Linux implementation. I also realized last time I contributed I forgot to update CONTRIBUTORS so I did that as well.

@miekg Added a comment to the package that it was copied from github.com/x/net/internal/socket. We don't need to necessarily keep in sync with them unless the Linux kernel definitions change. I also copied the test and added it.

@miekg good call. Didn't think about that. Moved into an internal directory.

This breaks a test in CoreDNS: https://travis-ci.org/coredns/coredns/jobs/281471373

The problem was actually with #511. I fixed it in #526

@miekg The problem was actually with #511. I fixed it in #526.


Image manifest unclear sentence

"used as a human readable index to the App Container Image" doesn't mean anything to me.  Needs a better description.

@thockin is this sufficient?

PTAL

LGTM


loot: init at 0.23.0

Description of changes
loot is a modding utility for Starfield and some Elder Scrolls and Fallout games.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Priorities
Add a :+1: reaction to pull requests you find important.

Needs rebasing due to conflicts from https://github.com/NixOS/nixpkgs/pull/342877
Maybe just add yourself as a maintainer for the package that was also in that PR (libloot?)?


[Gally]: master <- dev

Automatically created by Git-Ally

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Create UI for receiving DIDCommV2 messages

With local KMS

@jasonhealy pls detail scope (re phase 3)

Support in Agent explorer


Optimizing titiler-image performance

Hi! 👋
This project has been very helpful in meeting my use case for a dynamic tiler of a dataset of images which are not georeferenced.
I have been toying around with it and have found it to function well!
I have been using the LocalTilerFactory and it has shown fine latency on the satelite dataset I have (COG dataset on S3, returned as .jpg tile(is there a faster option?), streaming a zoomin tile takes ~100ms, full zoomout about ~400ms),
And to elaborate I have a very basic usage of the api - reading the tiles of the image in various zooms and rescaling it to fit to browser
But I do want to make adjustments that will allow me to shave as much time as possible to hopefully meet my target time (and obviously latency is just one performance consideration I am keen on optimizing as such with throughput and use case dependant performance)
So I would much appreciate guidance on how can I adapt and tune the tiler for better performance
For clarification, I have read this very helpful "Performance Tuning" guide and used the helpful key points it suggested https://developmentseed.org/titiler/advanced/performance_tuning/
I know much of the performance I can eke out depends on how I deploy the tiler (uvicorn on K8S) so any tips or suggestions both on deployment side of things and on adapting and modifying the tiler project itself (or extending around it) would be very much of help!!
Oh and one more thing, I have tried profiling titiler-image to find areas to improve performance and meanwhile have found that some of the latency comes from the rasterIO env being recreated on every request (when using rasterio.open, although the s3 account never changes), and I wonder the capability and effect of changing this behaviour(?) or any other step of the
Thanks in advance :)

moved to discussion https://github.com/developmentseed/titiler-image/discussions/11


🚀 Feature: Add more ignored commits

Bug Report Checklist

[X] I have tried restarting my IDE and the issue persists.
[X] I have pulled the latest main branch of the repository.
[X] I have searched for related issues and found none that matched my issue.

Overview
These are the currently ignored types of commits:
https://github.com/JoshuaKGoldberg/should-semantic-release/blob/d746446c0620b3393a78d1e8c0884d4ceed0a0da/src/shouldSemanticRelease.ts#L7
That's not the full list of ignorable types though! build:, ci:, style:, refactor:, and test: are other common ones that shouldn't necessitate an automatic release. Let's add them in and update the unit tests.
Additional Info
I found those commit styles on https://www.conventionalcommits.org/en/v1.0.0 (search for "angular").

@all-contributors please add @joshuakgoldberg for ideas.

🤖 Beep boop! This comment was added automatically by all-contributors-auto-action.
Not all contributions can be detected from Git & GitHub alone. Please comment any missing contribution types this bot missed.
...and of course, thank you for contributing! 💙


Test that maps are below max size

This should be failing consistently but isn't. The generated programs aren't interesting enough.

would one of the corpus programs fail consistently?

Yeah, good idea. I think it's worth having both. I'm going to leave this PR here until I've got the rest implemented

includes corpus tests for max map size
! @jystic @tranma

👍


fix for cleverbot 0.2.1

This is a very simple change to address the issue in cleverbot-node that was recently fixed:
https://github.com/fojas/cleverbot-node/issues/11
I realize this repo is deprecated, but I figured that it wasn't worth a separate repository or npm module.

We're in the process of deprecating this repository in favor of separate repositories per script over in #1641 . I can merge this now to get functionality out there, but it'd be better if this was extracted and released as a separate repository.
cc @ajacksified as a previous contributor

Understood. Since I'm not the creator I didn't want to create a separate repository without notifying first. Thanks!

Released in 2.16.2, thanks! cc https://github.com/github/hubot-scripts/pull/1660


[Rendering] The value of place holder changes when a button is clicked

Copied bug from: https://github.com/microsoft/AdaptiveCards/issues/6897
Details from original post:
Target Platforms
NodeJS
SDK Version
1.3
Application Name
Microsoft teams
Problem Description
So, I have a card that has 2 choice sets and 1 Action.Submit (submit button). When I click the button the expected behaviour is the value that I selected should remain in the placeholder section. It works as expected in the bot framework emulator, but in Microsoft teams when I change the value of the choice set and click on the submit button it goes back to the default placeholder. this is the JSON payload for the card.
In this case, When I select a value and click on submit button, it goes back to the default placeholder "Select a value".
Screenshots

Card JSON
{
                    "type": "AdaptiveCard",
                    "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
                    "version": "1.3",
                    "body": [
                        {
                            "type": "Container",
                            "items": [
                                {
                                    "type": "TextBlock",
                                    "wrap": true,
                                    "text": "Select the application name"
                                },
                                {
                                    "type": "Input.ChoiceSet",
                                    "choices": [
                                        {
                                            "title": "API",
                                            "value": "api"
                                        },
                                        {
                                            "title": "UI",
                                            "value": "UI"
                                        },
                                        {
                                            "title": "LE",
                                            "value": "le"
                                        },
                                        {
                                            "title": "Kafka",
                                            "value": "eats Kafka"
                                        }
                                    ],
                                    "placeholder": "Select a value",
                                    "id": "application_value"
                                },
                                {
                                    "type": "ActionSet",
                                    "actions": [
                                        {
                                            "type": "Action.Submit",
                                            "title": "Submit",
                                            "style": "positive",
                                        "data": {
                                            "postback_prop": true,
                                            "postback_activity": "getAppValue"
                                        }
                                        }
                                    ]
                                }
                            ]
                        }
                    ]
                }

Sample Code Language
No response
Sample Code
No response---
Document Details
⚠ Do not edit this section.It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 3fb4394d-25b1-8752-3996-fe3a2934732d
Version Independent ID: 6d391381-89d0-117c-27cc-00043bd26a36
Content: Cards reference - Teams
Content Source: msteams-platform/task-modules-and-cards/cards/cards-reference.md
Product: msteams
GitHub Login: @surbhigupta12
Microsoft Alias: surbhigupta12

We are checking the issue. We will get back to you shortly.

@Prasad-MSFT Any luck?

@Ajaykumar661 -This does seem to be default behaviour of adaptive card that after selecting a particular value in choice set and clicking on submit, it reset back to default state.

@Prasad-MSFT  That doesn't make sense, what if the user wants to validate the selected value. Are you sure this is a default behaviour?

Yes @Ajaykumar661 it is default behaviour of Adaptive card.

@Prasad-MSFT So it's the default button for any button? Like the button for toggling visibility. Just curious.

@Ajaykumar661 - No, toggling visibility button doesn't reset to default after clicking.

@Prasad-MSFT  I'm seeing that behaviour for the toggle button, Can you look into that?

@Ajaykumar661 , Could you please share the card JSON?

@Prasad-MSFT  Yeah sure, the card I'm constructing is a dynamic one. I'll try to replicate the same in designer and get back to you.

{     "type": "AdaptiveCard",     "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",     "version": "1.4",     "body": [         {             "type": "Input.ChoiceSet",             "choices": [                 {                     "title": "enabled",                     "value": "enable"                 },                 {                     "title": "disabled",                     "value": "disable"                 }             ],             "id": "node_id",             "placeholder": "enabled",             "label": "node_1"         },         {             "type": "Input.ChoiceSet",             "choices": [                 {                     "title": "enabled",                     "value": "enable"                 },                 {                     "title": "disabled",                     "value": "disable"                 }             ],             "id": "node_id_2",             "placeholder": "enabled",             "label": "node_2"         },         {             "type": "TextBlock",             "wrap": true,             "isVisible": false,             "id": "warningId",             "text": "Are you sure want to switch traffic ?"         },         {             "type": "ActionSet",             "actions": [                 {                     "type": "Action.Submit",                     "title": "Yes",                     "associatedInputs": "auto",                     "data": {                         "postback_prop": true,                         "postback_activity": "toggleState"                     }                 }             ],             "isVisible": false,             "id": "yId"         },         {             "type": "ActionSet",             "actions": [                 {                     "type": "Action.ToggleVisibility",                     "title": "No",                     "targetElements": [                         "warningId",                         "yId",                         "nId"                     ]                 }             ],             "isVisible": false,             "id": "nId"         }     ],     "actions": [         {             "type": "Action.ToggleVisibility",             "title": "Submit",             "targetElements": [                 "warningId",                 "yId",                 "nId"             ]         }     ] }

@Prasad-MSFT  This is the card. I'll try to attach a gif image if possible for this scenario.

@Ajaykumar661 - We were using below JSON having toggle visibility but without any submit action or choices type, so it was not reverting back to default.
`{
"type": "AdaptiveCard",
"version": "1.2",
"body": [
{
"type": "TextBlock",
"text": "Press the buttons to toggle the images!",
"wrap": true
},
{
"type": "TextBlock",
"text": "Here are some images:",
"isVisible": false,
"id": "textToToggle"
},
{
"type": "ColumnSet",
"columns": [
{
"type": "Column",
"items": [
{
"style": "person",
"type": "Image",
"url": "https://picsum.photos/100/100?image=112",
"isVisible": false,
"id": "imageToToggle",
"altText": "sample image 1",
"size": "medium"
}
]
},
{
"type": "Column",
"items": [
        {
          "type": "Image",
          "url": "https://picsum.photos/100/100?image=123",
          "isVisible": false,
          "id": "imageToToggle2",
          "altText": "sample image 2",
          "size": "medium"
        }
      ]
    }
  ]
}

],
"actions": [
{
"type": "Action.ToggleVisibility",
"title": "Toggle!",
"targetElements": [ "textToToggle", "imageToToggle", "imageToToggle2" ]
},
{
"type": "Action.ToggleVisibility",
"title": "Show!",
"targetElements": [
{
"elementId": "textToToggle",
"isVisible": true
},
{
"elementId": "imageToToggle",
"isVisible": true
},
{
"elementId": "imageToToggle2",
"isVisible": true
}
]
},
{
"type": "Action.ToggleVisibility",
"title": "Hide!",
"targetElements": [
{
"elementId": "textToToggle",
"isVisible": false
},
{
"elementId": "imageToToggle",
"isVisible": false
},
{
"elementId": "imageToToggle2",
"isVisible": false
}
]
}
]
}
`
But while checking your provided JSON , we observed that the selected choice value reverts back to default state after submit action.

@Ajaykumar661 - We observed that the selected choice value reverts back to default state after submit action.

@Prasad-MSFT  For your reference
This is the card I got

Changing the value from enabled to disable.

After changing the value

After clicking on the toggle visibility button it went back to default value that is "enabled"

Yes, this seems to be default behaviour of adaptive card for button functionality

@Ajaykumar661 - If you want to set the selected values after submitting the Card data, you can prepare the card with latest submitted values and send's back the updated card from the server.

@v-chetsh  Like sending a whole new card with updated values?

@Prasad-MSFT  @Wajeed-msft Can you look into this issue? https://github.com/microsoft/AdaptiveCards/issues/6899. This is more crucial than this...

@Prasad-MSFT  We are good to close this window, Thanks for the insights.

We are closing this issue for now, Please feel free to reopen it, if required.

@v-chetsh  @Wajeed-msft @Prasad-MSFT  I'm facing another issue pasted the link above, Can you look into this ?

@Ajaykumar661 - There is no issue attached with the link which you shared. Please recheck and share the correct url

https://github.com/microsoft/AdaptiveCards/issues/6899 @Prasad-MSFT

@Prasad-MSFT You got the right link?

@Ajaykumar661 - Yes, we will check


Modifier -> SwiftUI -> Clipboard: cuttable(for:action:)

Doc: https://developer.apple.com/documentation/swiftui/view/cuttable(for:action:)

[ ] Swift implementation
[ ] Elixir implementation

According to the @supernintendo @carson-katri @shadowfacts we won't support this


[core-rest-pipeline] NodeHttpClient didn't remove EventListener correctly caused MaxListenersExceededWarning

Package Name: @azure/core-rest-pipeline
Package Version: latest

Describe the bug
See discussion. There are two issues

we didn't wait the remove is done in finally https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/core/core-rest-pipeline/src/nodeHttpClient.ts#L181-L191
isStreamComplete would always return un-resolved promise once stream is at the end already: https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/core/core-rest-pipeline/src/nodeHttpClient.ts#L29

How to reproduce:

checkout pr https://github.com/Azure/azure-sdk-for-js/pull/31027
revert core-rest-pipeline
rush build -t @azure-rest/ai-translation-document && rushx unit-test:node
you will see the MaxListenersExceededWarning

Expected behavior
The above two would cause the removal action would not be called here.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

@MaryGao  I'm trying to fix via https://github.com/Azure/azure-sdk-for-js/pull/31077

@MaryGao I'm trying to fix via #31077

There's still the issue for an already completed stream? Those events will not be fired thus the promise not resolving.

rush build -t @azure-rest/ai-translation-document && rushx unit-test:node


Cmake Warning: Calling FetchContent_Populated(...) is deprecated

Probably an easy fix to use FetchContent_MakeAvailable(...) instead as the error describes, since this project already targets cmake_minimum_required(VERSION 3.14).
CMake Warning (dev) at /usr/share/cmake/Modules/FetchContent.cmake:1953 (message):
  Calling FetchContent_Populate(zstd) is deprecated, call
  FetchContent_MakeAvailable(zstd) instead.  Policy CMP0169 can be set to OLD
  to allow FetchContent_Populate(zstd) to be called directly for now, but the
  ability to call it with declared details will be removed completely in a
  future version.
Call Stack (most recent call first):
  cmake_build/_deps/cpptrace-src/CMakeLists.txt:396 (FetchContent_Populate)
This warning is for project developers.  Use -Wno-dev to suppress it.

...

CMake Warning (dev) at /usr/share/cmake/Modules/FetchContent.cmake:1953 (message):
  Calling FetchContent_Populate(libdwarf) is deprecated, call
  FetchContent_MakeAvailable(libdwarf) instead.  Policy CMP0169 can be set to
  OLD to allow FetchContent_Populate(libdwarf) to be called directly for now,
  but the ability to call it with declared details will be removed completely
  in a future version.
Call Stack (most recent call first):
  cmake_build/_deps/cpptrace-src/CMakeLists.txt:431 (FetchContent_Populate)
This warning is for project developers.  Use -Wno-dev to suppress it.

Seen from version v0.6.0 as pulled in by libassert using cmake version 3.30.3.


Don't make elements after enum part of enum 'module'

Q
A

Bug fix?
yes

New feature?
no

Breaking change?
no

Deprecations?
no

Tests added?
yes

Fixed issues

License
Apache-2.0

While generating a TypeScript declaration file for some protobuf messages, I came across a strange issue where no types after an enum was exported were included in the declaration file.  I tracked the issue down to an issue in jsdoc where any export in a file after an enum is exported is considered to be a child of the enum.  It looks like this behavior was added during a fix for #970.
The simple workaround for my case was to define the enum in a separate file, but I'd rather just fix the problem to avoid running into the same problem six months from now, forgetting the solution, and going through the process all over again!

Hello, are there any reasons that blocks merge of this PR?

Merge this 🙏

Can we please get this merged? It is 100% relevant and breaking protobuf.js pbts TypeScript from jsdoc conversion.

Can this be merged yet? Its passed all checks for a month now.

Can this be merged yet? Its passed all checks for a month now.

Bumping this issue

+1

+1, breaking our typescript protobuf.js models as well

Same issue here <3

+1
Can you merge this?

bump! pls merge :)

I was looking at this commit.
https://github.com/jsdoc/jsdoc/commit/1c99ec39eb0fc61be627eec059d87348b8d7a93a
Shouldn't there be a 'module' and a 'member'? The enum shouldn't become a 'module'.
It seems like @exports tag needs a special augmentation to handle the case properly.

Bump! Please merge 🙏

I updated according to latest version: https://github.com/jsdoc/jsdoc/pull/2046 could this be finally merged?


Update release-pio/v0.45.x to Cosmos-SDK version 0.45.6.

Summary
Currently, the release-pio/v0.45.x branch of our Cosmos-SDK fork is on upstream v0.45.4, which is two reversions behind. We should pull in the upstream v0.45.5 and v0.45.6 changes.

v0.45.4 -> v0.45.5: https://github.com/cosmos/cosmos-sdk/compare/v0.45.4...v0.45.5
v0.45.5 -> v0.45.6: https://github.com/cosmos/cosmos-sdk/compare/v0.45.5...v0.45.6

Problem Definition
We are a couple revisions behind on our Cosmos-SDK fork. Assuming we're going to be on v0.45.x a while longer, we should update to use the most recent revision.
Proposal
Merge the v0.45.5 and v0.45.6 changes into our release-pio/v0.45.x branch on our Cosmos-SDK fork.

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

This happened when we updated the branch to v0.45.9: https://github.com/provenance-io/cosmos-sdk/pull/293


Add design badges

ie. Adobe stuff

added in https://github.com/inttter/md-badges/commit/fe14ac4f9ec5b2c21b2a37b2c7159aeefffd6781


Add UOM to TLS handshake timeout

Proposed Changes
VerneMQ expects this value in milliseconds, but since the comment mentions "5 seconds," users may assume it's in seconds and spend a lot of time and curses before figuring this out.
Types of Changes
What types of changes does your code introduce to this project?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes issue #XXXX)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Documentation (correction or otherwise)
[ ] Cosmetics (whitespace, styles...)
[ ] DevOps (Build scripts, pipelines...)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating
the PR. If you're unsure about any of them, don't hesitate to ask on the
mailing list. We're here to help! This is simply a reminder of what we are
going to look for before merging your code.

[x] I have read the CODE_OF_CONDUCT.md document
[ ] All tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if needed)
[ ] Any dependent changes have been merged and published in related repositories
[ ] I have updated changelog (At the bottom of the release version)
[ ] I have squashed all my commits into one before merging

@zmoog thanks!


Add/update every Diamond FF primitive

This should now be complete, although latches are still missing (I'm not sure how to make a latch with Trellis).

I'm not sure how to make a latch with Trellis

The only hard latches in the ECP5 are in the IO tiles but I don't think these have been fuzzed yet. Diamond uses soft logic for all other primitives. This could be implemented similar how to Yosys creates soft latches: https://github.com/YosysHQ/yosys/blob/master/techlibs/ecp5/latches_map.v
There is actually an undocumented "async preload" mode of the flipflops that could be used to create hard latches. But I'm a bit wary relying on this because Diamond's synthesis never uses it (the only way to activate it is with the undocumented ncl route to create post pnr designs). I don't think the nextpnr support for this is complete either, but maybe if someone has an interesting use case I can work on this more.


Workaround for setuptools install_requires bug with pyasn1

When installing service_identity with setup.py install the order of
the install_requires directive causes setuptools to fail to install
pyasn1 with the following error message:
error: The 'pyasn1' distribution was not found and is required by service-identity

The workaround is to switch the order of pyasn1 and pyasn1-modules in
the install_requires directive.
Setuptools issue: https://github.com/pypa/setuptools/issues/498

😮
Could you add a comment to the section that stresses, that the order matters? Thanks!

Done

thanks!


Run autopep8

Fix #11

Sorry, I don't like the automatic formatting via autopep8. I think I will later do that manually (just tab to spaces).

@albertz okay, my autopep8 is redoing just the indent.


fix: only add TLS config if cert file has been written to disk

Issue
Fixes #506.
This likely happens when _configure() is called by something other than _on_server_cert_changed (e.g., a perfectly timed update-status), but when the certificate is already in relation data (or Prometheus has already been related through the certificates interface but the certificate is not ready yet).
Solution
Only add the tls_server_config for Prometheus if the certificate exists on the file sytstem.
The _configure() method is also called by _on_server_cert_changed(), which (sequentially) writes the cert to disk before calling _configure(). This means we don't risk skip adding the TLS configuration with this extra check.
Testing Instructions
It's pretty much a race condition, so it's hard to add a test for it. I guess trying to replicate the issue is something, though of course it doesn't guarantee it.
Release Notes
Only add the tls_server_config for Prometheus if the certificate exists on the file sytstem.

I don't think it's necessarily in the scope of this issue, which is the failed replan; this behavior when TLS is enabled has been implemented in the TLS PR :)
I'll add it anyway!

After noticing the itests were passing locally, rerunning them fixed things :D


[New game]: add tether game

🎮 Game Request
Game logic and basic description

Point down the features
Game points
tether! is game where you wreck as many enemies as possible using your tether, however if an enemy touches your ball then you get obliterated! This game has full mobile and offline support, designed as a progressive web application! This is my group's end-of-the-year project for our CS class.
Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @Aditijainnn , You can't have another issue before completing the previous one 😀
you already have the following 1 open issues 👀 ! :
#4436

Hey @Aditijainnn ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇

Hey @Aditijainnn !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

Hey @Aditijainnn!
We are already having a similar game request in #5111 👀
Make sure you come up with a cool unique idea 😀
Waiting for your new game idea 💗.


Issue #154: make journey-test.sh use exercises

Made bin/journey-test.sh iterate over exercises instead of problems. I've tested the individual lines I've changed and they give the same output as when they were iterating over problems. However I've not been able to run the entire script to test it... Any suggestions for how to do that are very welcome! :)

Yup and this script runs in CI and that works perfectly.  I'm gonna "review" this as approved; feel free to merge whenever you're ready, @FridaTveit.
It is a design goal of the script to both fail fast and give good signal as to what's wrong when something goes wrong.  I'd be happy to work through whatever you're seeing to get it running locally.
What happens when you run the script?

Thanks! :) Well it had lots of complaints about ruby (first that I didn't have it, then that it didn't like version 2.2.6, then that gem needed some update) that I've managed to fix. But now it's saying bin/journey-test.sh: line 180: ./exercism: cannot execute binary file: Exec form                                                                                at error

Looks like the attempt to detect which OS your machine has failed.
What do you get when you run:
$ uname

(p.s. I'm online right now; find me at https://gitter.im/exercism/xjava or https://appear.in/exercism/xjava)

I'm not a rubyist, but this line would appear to reference a Gemfile that's not part of the repo?
https://github.com/exercism/xjava/blob/68684542b474ed154908f9b579f8ec7505a2f083/bin/journey-test.sh#L33

From what I remember from trying to debug this, that Gemfile is from x-api which the script fetches at some point?
An update on how I got on with this: I managed to get most of the script working with help from @jtigger on Saturday. Thanks! :) But now I'm getting this error:
+ ./exercism --config .journey-test.exercism.json fetch java $'hello-world\r'
::1 - - [04/Feb/2017:16:24:28 +0000] "GET /v2/exercises/java/hello-world%0D HTTP/1.1" 404 64 0.0200
2017/02/04 16:24:28 unable to fetch problems (HTTP: 404) - No implementation of ' in track 'java'

Hey Frida... I notice that in the "GET" there's an extra character...
GET /v2/exercises/java/hello-world%0D

That 0x0D or decimal 13: the carriage return character......

Yes, I did notice that but I have no idea where the \r comes from... By the way, should I add the changes I made to the script to make it run on my machine to this review?

I just tried running the script with it iterating over problems instead of exercises and I get the same error. So I guess it's just something strange to do with runnning it on my machine. The script seems to really not like my laptop :P

Hey now!  Well then this script needs a few more lessons in diplomacy 'cause it needs to be running on whatever machine.
I suspect we can tweak this jq query to not emit the CRs...  My work day is firing off, so I can't dig in further right now.

I was able to get the exercise slugs on a single line like this:
cat config.json | jq '.exercises[].slug + " "' --join-output

Does that help?

Great, that worked thanks! :) Now it's just complaining about the symlinks and from issue #148 it looks like they won't work on Windows. So maybe I should just admit defeat as it looks like this is as far as it'll get on my machine... :P

I'd rather dereference the symlinks (i.e. remove them and copy the files) and rely on the journey test to catch problems, than have a core maintainer not have the ability to run the suite on her or his machine (of the OS of her or his choosing).
I'm not saying you have to do that work, Frida, just that I'd rather it go that way.

Sure, that's what I've been doing locally (removing them and copying the files) when I've needed to run tests with symlinks. I just didn't want to cause lots of problems with my uncooperative OS :P
But I'm happy to do that work :) Or do you think they should be good first patch issues?

But I'm happy to do that work :) Or do you think they should be good first patch issues?

I see this as "discovered scope" in this PR — and should be done as part of getting the script "up-to-date".  Yes, please!
To put a finer point on all this: maintainers are an Free Open Source Software product's lifeblood.  Without maintainers, very little gets done.  It's a happystance that we, as maintainers, are delighted by the sheer doing of the work.  But in every way that is in our control, the happy part of that stance should be cultivated.  If there's an apparent conflict between some other need and what would make a maintainer's life better, the latter should usually prevail.
This may seem like a little thing: copying files where there are symlinks.  But even the little things add up.
Thanks for volunteering to do this, @FridaTveit!

Yay, it finally runs on my machine! Happy days! :D

Awesome, nice work @FridaTveit!

Nice work, indeed, @FridaTveit!  I'm also starting to help maintain the Kotlin track.  "Stealing" your work to update the journey test over there too.  So, your efforts are immediately doubled!!


Added ATM-EditText to Inputs category

Added ATM-EditText library, a custom EditText implementation that allows formatting of currency-based numeric inputs with the benefit of customising currency, spacing, delimiter and auto formatting of commas

Thanks for recommending, but we try to only list solid, often used libraries. So let's give your library a bit time to major. Thanks!


Documentation says config_f instead of config

Here: https://focalevents.readthedocs.io/en/latest/cookbook/twitter/search.html#search-parameters
should be config, at least as I read the code.

I think config_f should be correct for the search parameters. In the code, config is the actual dictionary that gets read from the YAML file specified by config_f.
Does that match your understanding of the code?

Ah I see, the issue was with the parser argument name. Thank you!


Failure to load location

I had the following error occur after a HA docker update. To troubleshoot I attempted to reinstall the integration. But now it wont accept any lat long in setup. "Unsupported Lat/Lon"
2023-08-16 14:49:50.362 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Elizabeth South for bureau_of_meteorology Traceback (most recent call last):   File "/lsiopy/lib/python3.11/site-packages/homeassistant/config_entries.py", line 388, in async_setup     result = await component.async_setup_entry(hass, self)              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/config/custom_components/bureau_of_meteorology/__init__.py", line 70, in async_setup_entry     await collector.async_update()   File "/config/custom_components/bureau_of_meteorology/PyBoM/collector.py", line 87, in async_update     self.locations_data = await resp.json()                           ^^^^^^^^^^^^^^^^^   File "/lsiopy/lib/python3.11/site-packages/aiohttp/client_reqrep.py", line 1104, in json     raise ContentTypeError( aiohttp.client_exceptions.ContentTypeError: 0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://api.weather.bom.gov.au/v1/locations/r1fd7h')

HI..
yes, I just received this as well.  I was wondering if it is something on the BOM side...

HI.. yes, I just received this as well. I was wondering if it is something on the BOM side... I haven't done any updates, I just noticed that all the forecasts/observations were not working, so tried to reload the integration, but it failed. I was just about to remove it from HACS and re-add it, but I think it probably won't make any difference. Its a great intergration, so hopefully the BOM has restricted access to the data

I received errors simular to what is shown at the end of my first post. If I manually load the links it works just fine and shows the data that the integration was exposed previously. So I think it might be a change to the structure of the data rather than it being removed.

It's also killing integration already configured

1.1.20 has been released on HACS to address this issue.
I don't believe it was a deliberate action by the BOM but most likely just a library update that imposed a new requirement.
Please report any ongoing issues if it doesn't fix it for you.

I've updated but am still unable to configure location. It used to say "Unsupported Lat/Lon" now it says "Unknown error"
Error in log as follows
2023-08-16 23:16:58.681 ERROR (MainThread) [custom_components.bureau_of_meteorology.config_flow] Unexpected exception Traceback (most recent call last):   File "/config/custom_components/bureau_of_meteorology/config_flow.py", line 66, in async_step_user     await self.collector.get_locations_data()   File "/config/custom_components/bureau_of_meteorology/PyBoM/collector.py", line 35, in get_locations_data     async with aiohttp.ClientSession(headers=headers) as session:                                              ^^^^^^^ NameError: name 'headers' is not defined

I've updated but am still unable to configure location. It used to say "Unsupported Lat/Lon" now it says "Unknown error"
Error in log as follows 2023-08-16 23:16:58.681 ERROR (MainThread) [custom_components.bureau_of_meteorology.config_flow] Unexpected exception Traceback (most recent call last): File "/config/custom_components/bureau_of_meteorology/config_flow.py", line 66, in async_step_user await self.collector.get_locations_data() File "/config/custom_components/bureau_of_meteorology/PyBoM/collector.py", line 35, in get_locations_data async with aiohttp.ClientSession(headers=headers) as session: ^^^^^^^ NameError: name 'headers' is not defined

Yup getting that error after updating to the current build as of this reply, restarted my HA install to reload it all properly but still get it at the moment.

1.1.21 release to fix the configuring problem. I made a type in my haste to do the initial fix.

1.1.21 release to fix the configuring problem. I made a type in my haste to do the initial fix.

Had to use the redownload option to update to this version until reloading the instance. it's working now as it should, moved to having my govee sensor as backup should future issues crop up.

Thanks for the quick fix.  Very much appreciated.   this is by far the best integration for getting accurate weather in Australia,  I setup the pirate weather app, but it not very good...

Thanks for the quick fix Mr. Maker!

Thanks. The update fixed the issue.

1.1.21 release to fix the configuring problem. I made a type in my haste to do the initial fix.

Thanks so much for quick update.


K8SPXC-1520 Set the default value of the enableVolumeExpansion param to false to match v1.15.1

CHANGE DESCRIPTION
Problem:
Short explanation of the problem.
Cause:
Short explanation of the root cause of the issue if applicable.
Solution:
Short explanation of the solution we are providing with this PR.
CHECKLIST
Jira

[ ] Is the Jira ticket created and referenced properly?
[ ] Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
[ ] Does the Jira ticket link to the proper milestone (Fix Version field)?

Tests

[ ] Is an E2E test/test case added for the new feature/change?
[ ] Are unit tests added where appropriate?
[ ] Are OpenShift compare files changed for E2E tests (compare/*-oc.yml)?

Config/Logging/Testability

[ ] Are all needed new/changed options added to default YAML files?
[ ] Are all needed new/changed options added to the Helm Chart?
[ ] Did we add proper logging messages for operator actions?
[ ] Did we ensure compatibility with the previous version or cluster upgrade process?
[ ] Does the change support oldest and newest supported PXC version?
[ ] Does the change support oldest and newest supported Kubernetes version?

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

custom-users-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

pitr-gap-errors-8-0
passed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

pvc-resize-5-7
passed

pvc-resize-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-5-7
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-5-7
failure

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 42 out of 42

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1896/commits/aea0011ad213344fa6c083887647973a4dd07f70
image: perconalab/percona-xtradb-cluster-operator:PR-1896-aea0011a

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

custom-users-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

pitr-gap-errors-8-0
passed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

pvc-resize-5-7
passed

pvc-resize-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-5-7
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-5-7
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 42 out of 42

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1896/commits/aea0011ad213344fa6c083887647973a4dd07f70
image: perconalab/percona-xtradb-cluster-operator:PR-1896-aea0011a

@ptankov please add task number into PR description

I didn't think a task was needed for such a trivial change.

@ptankov please add task number into PR description

I didn't think a task was needed for such a trivial change.

All PRs should have it

@ptankov please add task number into PR description

I didn't think a task was needed for such a trivial change.

All PRs should have it

done

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

custom-users-8-0
failure

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

pitr-gap-errors-8-0
passed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

pvc-resize-5-7
passed

pvc-resize-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
failure

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
failure

upgrade-haproxy-5-7
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-5-7
passed

upgrade-proxysql-8-0
failure

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 42 out of 42

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1896/commits/026773430db7788968b5a42b628285b307fef287
image: perconalab/percona-xtradb-cluster-operator:PR-1896-02677343


Laravel 11.x Compatibility

This is an automated pull request from Shift to update your package code and dependencies to be compatible with Laravel 11.x.
Before merging, you need to:

Checkout the l11-compatibility branch
Review all comments for additional changes
Thoroughly test your package

If you do find an issue, please report it by commenting on this PR to help improve future automation.

:warning: Shift detected a dependency for the laravel/framework. Unless you have a special requirement for depending on the entire Laravel framework, it's recommended to add dependencies for the specific illuminate packages instead.

:information_source: Shift detected you do not have a CI workflow using GitHub Actions. If you would like, Shift can help you get started with the CI Generator. Although the Shift is paid, GitHub Actions is free and having a CI workflow will improve the stability and review process for your package.

:alembic: Using this package? If you would like to help test these changes or believe them to be compatible, you may update your project to reference this branch.
To do so, temporarily add Shift's fork to the repositories property of your composer.json:
{
    "repositories": [
        {
            "type": "vcs",
            "url": "https://github.com/laravel-shift/select.git"
        }
    ]
}

Then update your dependency constraint to reference this branch:
{
    "require": {
        "laravel-enso/select": "dev-l11-compatibility",
    }
}

Finally, run: composer update


how can i use a config attribute to define library paths like RequireJS

I want to  load our private library from our remote static resource server,but i don't know how to do . Can i use a config attribute to define library paths like RequireJS。

I have the same scenario requirement， You will gain a lot by reading this article。 thanks！


when Hyperion is turned off, the brightness of the LED does not returndoes not return brightness

[x] I confirm that this is an issue rather than a question.

Bug report
When I turn off the LED device (LED) for the first time, the brightness remains on the WLED returns to the same level as it was before hyperion turned on, and if I turn on hyperion again with WLED turned on and turn off hyperion, then the brightness of the WLED will be 255. I am currently fixing the problem with the help of Home Assistant
Steps to reproduce
What is expected?
when you turn off the hyperion through the LED device (LED), the brightness level of the LED will return as it was before turning on the hyperion
What is actually happening?
System

Hyperion Server OS:

Distribution:   Windows 10 Version 2009
Architecture:   x86_64
Kernel:         winnt (10.0.19042 (WS: 64))
Root/Admin:     false
Qt Version:     5.15.0
Python Version: 3.10.0

How have you configured the WLED device?

Are there any communication/network failures in the log?

Yes, it's all on for me. I don't notice dumps at WLED since everything works fine, management + frame capture works fine. There are no freezes.

Screenshot

Log output
Hyperion System Summary Report (WLED Monitor), Reported instance: unknown
< ----- System information -------------------- >
Hyperion Server:

Build:           (HEAD detached at df149583) (GitHub-dc6aa4dd/df149583-1637501177)
Build time:      Nov 21 2021 16:50:38
Git Remote:      https://github.com/hyperion-project/hyperion.ng
Version:         2.0.12
UI Lang:         ru (BrowserLang: ru-RU)
UI Access:       advanced
Avail Capt:      v4l2,qt,dx
Config path:     C:/Users/Home/.hyperion
Database:        read/write

Hyperion Server OS:

Distribution:   Windows 10 Version 2009
Architecture:   x86_64
Kernel:         winnt (10.0.19042 (WS: 64))
Root/Admin:     false
Qt Version:     5.15.0
Python Version: 3.10.0
Browser:        Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.69 Safari/537.36 OPR/81.0.4196.60 (Edition Yx 05)

< ----- Configured Instances ------------------ >
0: WLED Livingroom Monitor Running: true
< ----- This instance's priorities ------------ >
100:  VISIBLE! (GRABBER) Owner: Qt
priorities_autoselect: true
< ----- This instance components' status ------->
ALL - true
SMOOTHING - false
BLACKBORDER - true
FORWARDER - false
BOBLIGHTSERVER - false
GRABBER - true
V4L - false
LEDDEVICE - false
< ----- This instance's configuration --------- >
{"backgroundEffect":{"color":[255,138,0],"effect":"Warm mood blobs","enable":false,"type":"effect"},"blackborderdetector":{"blurRemoveCnt":1,"borderFrameCnt":50,"enable":true,"maxInconsistentCnt":10,"mode":"default","threshold":5,"unknownFrameCnt":600},"boblightServer":{"enable":false,"port":19333,"priority":128},"color":{"channelAdjustment":[{"backlightColored":false,"backlightThreshold":0,"blue":[0,0,255],"brightness":100,"brightnessCompensation":100,"cyan":[0,255,255],"gammaBlue":2.2,"gammaGreen":2.2,"gammaRed":2.2,"green":[0,255,0],"id":"default","leds":"*","magenta":[255,0,255],"red":[255,0,0],"white":[255,255,255],"yellow":[255,255,0]}],"imageToLedMappingType":"multicolor_mean"},"device":{"brightness":255,"colorOrder":"rgb","hardwareLedCount":93,"host":"<IP_ADDRESS>","hostList":"NONE","latchTime":0,"overwriteBrightness":true,"overwriteSync":true,"restoreOriginalState":true,"type":"wled"},"effects":{"disable":[""],"paths":["$ROOT/custom-effects"]},"flatbufServer":{"enable":true,"port":19400,"timeout":5},"foregroundEffect":{"color":[0,0,255],"duration_ms":3000,"effect":"Rainbow swirl fast","enable":true,"type":"effect"},"forwarder":{"enable":false,"flat":[],"json":[]},"framegrabber":{"available_devices":"QT","cropBottom":0,"cropLeft":0,"cropRight":0,"cropTop":0,"device":"qt","device_inputs":"0","enable":true,"fps":25,"framerates":"25","height":1080,"input":0,"pixelDecimation":8,"resolutions":"0","width":1920},"general":{"configVersion":"2.0.12","name":"WLED Monitor","previousVersion":"2.0.12","showOptHelp":true,"watchedVersionBranch":"Stable"},"grabberV4L2":{"blueSignalThreshold":0,"cecDetection":false,"cropBottom":0,"cropLeft":0,"cropRight":0,"cropTop":0,"device":"none","enable":false,"encoding":"NO_CHANGE","flip":"NO_CHANGE","fps":15,"fpsSoftwareDecimation":0,"greenSignalThreshold":100,"hardware_brightness":0,"hardware_contrast":0,"hardware_hue":0,"hardware_saturation":0,"height":0,"input":0,"noSignalCounterThreshold":200,"redSignalThreshold":0,"sDHOffsetMax":0.46,"sDHOffsetMin":0.4,"sDVOffsetMax":0.9,"sDVOffsetMin":0.1,"signalDetection":false,"sizeDecimation":8,"width":0},"instCapture":{"systemEnable":true,"systemGrabberDevice":"QT","systemPriority":100,"v4lEnable":false,"v4lGrabberDevice":"NONE","v4lPriority":240},"jsonServer":{"port":19444},"ledConfig":{"classic":{"bottom":27,"edgegap":0,"glength":0,"gpos":0,"hdepth":8,"left":18,"overlap":0,"pblh":0,"pblv":100,"pbrh":100,"pbrv":100,"position":54,"ptlh":0,"ptlv":0,"ptrh":100,"ptrv":0,"reverse":false,"right":18,"top":30,"vdepth":5},"ledBlacklist":[],"matrix":{"cabling":"snake","ledshoriz":1,"ledsvert":1,"start":"top-left"}},"leds":[{"hmax":0.7778,"hmin":0.7407,"vmax":1,"vmin":0.92},{"hmax":0.7407,"hmin":0.7037,"vmax":1,"vmin":0.92},{"hmax":0.7037,"hmin":0.6667,"vmax":1,"vmin":0.92},{"hmax":0.6667,"hmin":0.6296,"vmax":1,"vmin":0.92},{"hmax":0.6296,"hmin":0.5926,"vmax":1,"vmin":0.92},{"hmax":0.5926,"hmin":0.5556,"vmax":1,"vmin":0.92},{"hmax":0.5556,"hmin":0.5185,"vmax":1,"vmin":0.92},{"hmax":0.5185,"hmin":0.4815,"vmax":1,"vmin":0.92},{"hmax":0.4815,"hmin":0.4444,"vmax":1,"vmin":0.92},{"hmax":0.4444,"hmin":0.4074,"vmax":1,"vmin":0.92},{"hmax":0.4074,"hmin":0.3704,"vmax":1,"vmin":0.92},{"hmax":0.3704,"hmin":0.3333,"vmax":1,"vmin":0.92},{"hmax":0.3333,"hmin":0.2963,"vmax":1,"vmin":0.92},{"hmax":0.2963,"hmin":0.2593,"vmax":1,"vmin":0.92},{"hmax":0.2593,"hmin":0.2222,"vmax":1,"vmin":0.92},{"hmax":0.2222,"hmin":0.1852,"vmax":1,"vmin":0.92},{"hmax":0.1852,"hmin":0.1481,"vmax":1,"vmin":0.92},{"hmax":0.1481,"hmin":0.1111,"vmax":1,"vmin":0.92},{"hmax":0.1111,"hmin":0.0741,"vmax":1,"vmin":0.92},{"hmax":0.0741,"hmin":0.037,"vmax":1,"vmin":0.92},{"hmax":0.037,"hmin":0,"vmax":1,"vmin":0.92},{"hmax":0.05,"hmin":0,"vmax":1,"vmin":0.9444},{"hmax":0.05,"hmin":0,"vmax":0.9444,"vmin":0.8889},{"hmax":0.05,"hmin":0,"vmax":0.8889,"vmin":0.8333},{"hmax":0.05,"hmin":0,"vmax":0.8333,"vmin":0.7778},{"hmax":0.05,"hmin":0,"vmax":0.7778,"vmin":0.7222},{"hmax":0.05,"hmin":0,"vmax":0.7222,"vmin":0.6667},{"hmax":0.05,"hmin":0,"vmax":0.6667,"vmin":0.6111},{"hmax":0.05,"hmin":0,"vmax":0.6111,"vmin":0.5556},{"hmax":0.05,"hmin":0,"vmax":0.5556,"vmin":0.5},{"hmax":0.05,"hmin":0,"vmax":0.5,"vmin":0.4444},{"hmax":0.05,"hmin":0,"vmax":0.4444,"vmin":0.3889},{"hmax":0.05,"hmin":0,"vmax":0.3889,"vmin":0.3333},{"hmax":0.05,"hmin":0,"vmax":0.3333,"vmin":0.2778},{"hmax":0.05,"hmin":0,"vmax":0.2778,"vmin":0.2222},{"hmax":0.05,"hmin":0,"vmax":0.2222,"vmin":0.1667},{"hmax":0.05,"hmin":0,"vmax":0.1667,"vmin":0.1111},{"hmax":0.05,"hmin":0,"vmax":0.1111,"vmin":0.0556},{"hmax":0.05,"hmin":0,"vmax":0.0556,"vmin":0},{"hmax":0.0333,"hmin":0,"vmax":0.08,"vmin":0},{"hmax":0.0667,"hmin":0.0333,"vmax":0.08,"vmin":0},{"hmax":0.1,"hmin":0.0667,"vmax":0.08,"vmin":0},{"hmax":0.1333,"hmin":0.1,"vmax":0.08,"vmin":0},{"hmax":0.1667,"hmin":0.1333,"vmax":0.08,"vmin":0},{"hmax":0.2,"hmin":0.1667,"vmax":0.08,"vmin":0},{"hmax":0.2333,"hmin":0.2,"vmax":0.08,"vmin":0},{"hmax":0.2667,"hmin":0.2333,"vmax":0.08,"vmin":0},{"hmax":0.3,"hmin":0.2667,"vmax":0.08,"vmin":0},{"hmax":0.3333,"hmin":0.3,"vmax":0.08,"vmin":0},{"hmax":0.3667,"hmin":0.3333,"vmax":0.08,"vmin":0},{"hmax":0.4,"hmin":0.3667,"vmax":0.08,"vmin":0},{"hmax":0.4333,"hmin":0.4,"vmax":0.08,"vmin":0},{"hmax":0.4667,"hmin":0.4333,"vmax":0.08,"vmin":0},{"hmax":0.5,"hmin":0.4667,"vmax":0.08,"vmin":0},{"hmax":0.5333,"hmin":0.5,"vmax":0.08,"vmin":0},{"hmax":0.5667,"hmin":0.5333,"vmax":0.08,"vmin":0},{"hmax":0.6,"hmin":0.5667,"vmax":0.08,"vmin":0},{"hmax":0.6333,"hmin":0.6,"vmax":0.08,"vmin":0},{"hmax":0.6667,"hmin":0.6333,"vmax":0.08,"vmin":0},{"hmax":0.7,"hmin":0.6667,"vmax":0.08,"vmin":0},{"hmax":0.7333,"hmin":0.7,"vmax":0.08,"vmin":0},{"hmax":0.7667,"hmin":0.7333,"vmax":0.08,"vmin":0},{"hmax":0.8,"hmin":0.7667,"vmax":0.08,"vmin":0},{"hmax":0.8333,"hmin":0.8,"vmax":0.08,"vmin":0},{"hmax":0.8667,"hmin":0.8333,"vmax":0.08,"vmin":0},{"hmax":0.9,"hmin":0.8667,"vmax":0.08,"vmin":0},{"hmax":0.9333,"hmin":0.9,"vmax":0.08,"vmin":0},{"hmax":0.9667,"hmin":0.9333,"vmax":0.08,"vmin":0},{"hmax":1,"hmin":0.9667,"vmax":0.08,"vmin":0},{"hmax":1,"hmin":0.95,"vmax":0.0556,"vmin":0},{"hmax":1,"hmin":0.95,"vmax":0.1111,"vmin":0.0556},{"hmax":1,"hmin":0.95,"vmax":0.1667,"vmin":0.1111},{"hmax":1,"hmin":0.95,"vmax":0.2222,"vmin":0.1667},{"hmax":1,"hmin":0.95,"vmax":0.2778,"vmin":0.2222},{"hmax":1,"hmin":0.95,"vmax":0.3333,"vmin":0.2778},{"hmax":1,"hmin":0.95,"vmax":0.3889,"vmin":0.3333},{"hmax":1,"hmin":0.95,"vmax":0.4444,"vmin":0.3889},{"hmax":1,"hmin":0.95,"vmax":0.5,"vmin":0.4444},{"hmax":1,"hmin":0.95,"vmax":0.5556,"vmin":0.5},{"hmax":1,"hmin":0.95,"vmax":0.6111,"vmin":0.5556},{"hmax":1,"hmin":0.95,"vmax":0.6667,"vmin":0.6111},{"hmax":1,"hmin":0.95,"vmax":0.7222,"vmin":0.6667},{"hmax":1,"hmin":0.95,"vmax":0.7778,"vmin":0.7222},{"hmax":1,"hmin":0.95,"vmax":0.8333,"vmin":0.7778},{"hmax":1,"hmin":0.95,"vmax":0.8889,"vmin":0.8333},{"hmax":1,"hmin":0.95,"vmax":0.9444,"vmin":0.8889},{"hmax":1,"hmin":0.95,"vmax":1,"vmin":0.9444},{"hmax":1,"hmin":0.963,"vmax":1,"vmin":0.92},{"hmax":0.963,"hmin":0.9259,"vmax":1,"vmin":0.92},{"hmax":0.9259,"hmin":0.8889,"vmax":1,"vmin":0.92},{"hmax":0.8889,"hmin":0.8519,"vmax":1,"vmin":0.92},{"hmax":0.8519,"hmin":0.8148,"vmax":1,"vmin":0.92},{"hmax":0.8148,"hmin":0.7778,"vmax":1,"vmin":0.92}],"logger":{"level":"debug"},"network":{"apiAuth":true,"internetAccessAPI":false,"ipWhitelist":[],"localAdminAuth":true,"localApiAuth":false,"restirctedInternetAccessAPI":false},"protoServer":{"enable":true,"port":19445,"timeout":5},"smoothing":{"enable":false},"webConfig":{"crtPath":"","document_root":"","keyPassPhrase":"","keyPath":"","port":8090,"sslPort":8092}}
< ----- Current Log --------------------------- >
2021-12-08T22:07:27.695Z [ WEBSOCKET] (DEBUG) (WebSocketClient.cpp:215:WebSocketClient::sendClose()) Send close to ::1: 1000
2021-12-08T22:07:27.905Z [ WEBSOCKET] (DEBUG) (WebSocketClient.cpp:30:WebSocketClient::WebSocketClient()) New connection from ::1
2021-12-08T22:07:28.110Z [ WEBSOCKET] (DEBUG) (JsonAPI.cpp:122:JsonAPI::handleInstanceSwitch()) Client '::1' switch to Hyperion instance 0
2021-12-08T22:07:28.523Z [ WEBSOCKET] (DEBUG) (JsonAPI.cpp:1090:JsonAPI::handleLoggingCommand()) log streaming activated for client ::1
2021-12-08T22:07:36.187Z [ WEBSOCKET] (DEBUG) (JsonAPI.cpp:1436:JsonAPI::handleLedDeviceCommand()) message: [{"command":"leddevice","ledDeviceType":"wled","subcommand":"discover","tan":851}]
2021-12-08T22:07:36.187Z [ WEBSOCKET] (DEBUG) (JsonAPI.cpp:1460:JsonAPI::handleLedDeviceCommand()) response: [{"devices":[],"ledDeviceType":"wled"}]
2021-12-08T22:07:36.194Z [ WEBSOCKET] (DEBUG) (JsonAPI.cpp:1436:JsonAPI::handleLedDeviceCommand()) message: [{"command":"leddevice","ledDeviceType":"wled","params":{"filter":"info","host":"<IP_ADDRESS>"},"subcommand":"getProperties","tan":213}]
2021-12-08T22:07:36.221Z [ WEBSOCKET] (DEBUG) (JsonAPI.cpp:1470:JsonAPI::handleLedDeviceCommand()) response: [{"properties":{"arch":"esp8266","brand":"WLED","core":"2_7_4_7","freeheap":19584,"fs":{"pmt":1638934217,"t":1024,"u":49},"fxcount":118,"ip":"<IP_ADDRESS>","leds":{"count":93,"fps":25,"maxpwr":0,"maxseg":16,"pwr":0,"rgbw":false,"wv":false},"lip":"<IP_ADDRESS>","live":true,"lm":"Hyperion","lwip":1,"mac":"e8db84ddbe26","maxLedCount":490,"name":"WLED Monitor","ndc":2,"opt":127,"palcount":71,"product":"FOSS","str":false,"udpport":21324,"uptime":123807,"ver":"0.13.0-b5","vid":2111170,"wifi":{"bssid":"50:FF:20:53:B5:91","channel":9,"rssi":-55,"signal":90},"ws":1}}]
2021-12-08T22:07:39.506Z [ LEDDEVICE] (INFO)  Stopped LedDevice 'wled'
2021-12-08T22:07:39.508Z [ LEDDEVICE] (INFO) Start LedDevice 'wled'.
2021-12-08T22:07:39.508Z [ COMPONENTREG] (DEBUG) (ComponentRegister.cpp:41:ComponentRegister::setNewComponentState()) LED device: disabled
2021-12-08T22:07:39.508Z [ LEDDEVICE] (DEBUG) (LedDevice.cpp:148:LedDevice::init()) deviceConfig: [{"brightness":255,"colorOrder":"rgb","currentLedCount":93,"hardwareLedCount":93,"host":"<IP_ADDRESS>","hostList":"NONE","latchTime":0,"overwriteBrightness":true,"overwriteSync":true,"restoreOriginalState":true,"type":"wled"}]
2021-12-08T22:07:39.508Z [ LEDDEVICE] (DEBUG) (LedDevice.cpp:414:LedDevice::setLatchTime()) LatchTime updated to 0ms
2021-12-08T22:07:39.508Z [ LEDDEVICE] (DEBUG) (LedDevice.cpp:445:LedDevice::setRewriteTime()) RewriteTime updated to 0ms
2021-12-08T22:07:39.508Z [ LEDDEVICE] (DEBUG) (LedDeviceWled.cpp:80:LedDeviceWled::init()) DeviceType   : wled
2021-12-08T22:07:39.508Z [ LEDDEVICE] (DEBUG) (LedDeviceWled.cpp:81:LedDeviceWled::init()) LedCount     : 93
2021-12-08T22:07:39.509Z [ LEDDEVICE] (DEBUG) (LedDeviceWled.cpp:82:LedDeviceWled::init()) ColorOrder   : rgb
2021-12-08T22:07:39.509Z [ LEDDEVICE] (DEBUG) (LedDeviceWled.cpp:83:LedDeviceWled::init()) LatchTime    : 0
2021-12-08T22:07:39.509Z [ LEDDEVICE] (DEBUG) (LedDeviceWled.cpp:97:LedDeviceWled::init()) RestoreOrigState  : 1
2021-12-08T22:07:39.509Z [ LEDDEVICE] (DEBUG) (LedDeviceWled.cpp:98:LedDeviceWled::init()) Overwrite Sync.   : 1
2021-12-08T22:07:39.509Z [ LEDDEVICE] (DEBUG) (LedDeviceWled.cpp:99:LedDeviceWled::init()) Overwrite Brightn.: 1
2021-12-08T22:07:39.509Z [ LEDDEVICE] (DEBUG) (LedDeviceWled.cpp:100:LedDeviceWled::init()) Set Brightness to : 255
2021-12-08T22:07:39.510Z [ LEDDEVICE] (DEBUG) (LedDevice.cpp:148:LedDevice::init()) deviceConfig: [{"brightness":255,"colorOrder":"rgb","currentLedCount":93,"hardwareLedCount":93,"host":"<IP_ADDRESS>","hostList":"NONE","latchTime":0,"overwriteBrightness":true,"overwriteSync":true,"port":19446,"restoreOriginalState":true,"type":"wled"}]
2021-12-08T22:07:39.510Z [ LEDDEVICE] (DEBUG) (LedDevice.cpp:414:LedDevice::setLatchTime()) LatchTime updated to 0ms
2021-12-08T22:07:39.510Z [ LEDDEVICE] (DEBUG) (LedDevice.cpp:445:LedDevice::setRewriteTime()) RewriteTime updated to 0ms
2021-12-08T22:07:39.510Z [ LEDDEVICE] (DEBUG) (ProviderUdp.cpp:43:ProviderUdp::init()) Successfully parsed <IP_ADDRESS> as an IP-address.
2021-12-08T22:07:39.510Z [ LEDDEVICE] (DEBUG) (ProviderUdp.cpp:73:ProviderUdp::init()) UDP socket will write to <IP_ADDRESS> port: 19446
2021-12-08T22:07:39.510Z [ LEDDEVICE] (DEBUG) (LedDeviceWled.cpp:131:LedDeviceWled::init()) Hostname/IP  : <IP_ADDRESS>
2021-12-08T22:07:39.510Z [ LEDDEVICE] (DEBUG) (LedDeviceWled.cpp:132:LedDeviceWled::init()) Port         : 19446
2021-12-08T22:07:39.532Z [ LEDDEVICE] (DEBUG) (LedDeviceWled.cpp:211:LedDeviceWled::powerOn()) Disable synchronisation with other WLED devices
2021-12-08T22:07:39.559Z [ COMPONENTREG] (DEBUG) (ComponentRegister.cpp:41:ComponentRegister::setNewComponentState()) LED device: enabled
2021-12-08T22:07:39.589Z [ WEBSOCKET] (DEBUG) (WebSocketClient.cpp:215:WebSocketClient::sendClose()) Send close to ::1: 1000
2021-12-08T22:07:39.807Z [ WEBSOCKET] (DEBUG) (WebSocketClient.cpp:30:WebSocketClient::WebSocketClient()) New connection from ::1
2021-12-08T22:07:40.024Z [ WEBSOCKET] (DEBUG) (JsonAPI.cpp:122:JsonAPI::handleInstanceSwitch()) Client '::1' switch to Hyperion instance 0
2021-12-08T22:07:40.541Z [ WEBSOCKET] (DEBUG) (JsonAPI.cpp:1436:JsonAPI::handleLedDeviceCommand()) message: [{"command":"leddevice","ledDeviceType":"wled","subcommand":"discover","tan":692}]
2021-12-08T22:07:40.541Z [ WEBSOCKET] (DEBUG) (JsonAPI.cpp:1460:JsonAPI::handleLedDeviceCommand()) response: [{"devices":[],"ledDeviceType":"wled"}]
2021-12-08T22:07:40.547Z [ WEBSOCKET] (DEBUG) (JsonAPI.cpp:1436:JsonAPI::handleLedDeviceCommand()) message: [{"command":"leddevice","ledDeviceType":"wled","params":{"filter":"info","host":"<IP_ADDRESS>"},"subcommand":"getProperties","tan":663}]
2021-12-08T22:07:40.572Z [ WEBSOCKET] (DEBUG) (JsonAPI.cpp:1470:JsonAPI::handleLedDeviceCommand()) response: [{"properties":{"arch":"esp8266","brand":"WLED","core":"2_7_4_7","freeheap":19584,"fs":{"pmt":1638934217,"t":1024,"u":49},"fxcount":118,"ip":"<IP_ADDRESS>","leds":{"count":93,"fps":29,"maxpwr":0,"maxseg":16,"pwr":0,"rgbw":false,"wv":false},"lip":"<IP_ADDRESS>","live":true,"lm":"Hyperion","lwip":1,"mac":"e8db84ddbe26","maxLedCount":490,"name":"WLED Monitor","ndc":2,"opt":127,"palcount":71,"product":"FOSS","str":false,"udpport":21324,"uptime":123811,"ver":"0.13.0-b5","vid":2111170,"wifi":{"bssid":"50:FF:20:53:B5:91","channel":9,"rssi":-54,"signal":92},"ws":1}}]
2021-12-08T22:07:47.378Z [ JSONSERVER] (DEBUG) (JsonServer.cpp:105:JsonServer::newConnection()) New connection from: ::ffff:<IP_ADDRESS>
2021-12-08T22:07:49.543Z [ COMPONENTREG] (DEBUG) (ComponentRegister.cpp:41:ComponentRegister::setNewComponentState()) LED device: disabled
2021-12-08T22:07:57.771Z [ COMPONENTREG] (DEBUG) (ComponentRegister.cpp:41:ComponentRegister::setNewComponentState()) LED device: enabled
2021-12-08T22:08:04.741Z [ COMPONENTREG] (DEBUG) (ComponentRegister.cpp:41:ComponentRegister::setNewComponentState()) LED device: disabled
2021-12-08T22:08:20.343Z [ COMPONENTREG] (DEBUG) (ComponentRegister.cpp:41:ComponentRegister::setNewComponentState()) LED device: enabled
2021-12-08T22:08:26.153Z [ COMPONENTREG] (DEBUG) (ComponentRegister.cpp:41:ComponentRegister::setNewComponentState()) LED device: disabled
2021-12-08T22:08:52.564Z [ COMPONENTREG] (DEBUG) (ComponentRegister.cpp:41:ComponentRegister::setNewComponentState()) LED device: enabled
2021-12-08T22:08:56.443Z [ COMPONENTREG] (DEBUG) (ComponentRegister.cpp:41:ComponentRegister::setNewComponentState()) LED device: disabled
2021-12-08T22:09:05.224Z [ COMPONENTREG] (DEBUG) (ComponentRegister.cpp:41:ComponentRegister::setNewComponentState()) LED device: enabled
2021-12-08T22:09:09.179Z [ COMPONENTREG] (DEBUG) (ComponentRegister.cpp:41:ComponentRegister::setNewComponentState()) LED device: disabled
2021-12-08T22:09:20.942Z [ COMPONENTREG] (DEBUG) (ComponentRegister.cpp:41:ComponentRegister::setNewComponentState()) LED device: enabled
2021-12-08T22:09:23.459Z [ COMPONENTREG] (DEBUG) (ComponentRegister.cpp:41:ComponentRegister::setNewComponentState()) LED device: disabled
2021-12-08T22:09:35.315Z [ COMPONENTREG] (DEBUG) (ComponentRegister.cpp:41:ComponentRegister::setNewComponentState()) LED device: enabled
2021-12-08T22:09:39.245Z [ COMPONENTREG] (DEBUG) (ComponentRegister.cpp:41:ComponentRegister::setNewComponentState()) LED device: disabled
2021-12-08T22:09:46.336Z [ COMPONENTREG] (DEBUG) (ComponentRegister.cpp:41:ComponentRegister::setNewComponentState()) LED device: enabled
2021-12-08T22:09:52.314Z [ COMPONENTREG] (DEBUG) (ComponentRegister.cpp:41:ComponentRegister::setNewComponentState()) LED device: disabled
2021-12-08T22:09:58.301Z [ WEBSOCKET] (DEBUG) (JsonAPI.cpp:1090:JsonAPI::handleLoggingCommand()) log streaming activated for client ::1
2021-12-08T22:10:27.919Z [ COMPONENTREG] (DEBUG) (ComponentRegister.cpp:41:ComponentRegister::setNewComponentState()) LED device: enabled
2021-12-08T22:10:31.162Z [ COMPONENTREG] (DEBUG) (ComponentRegister.cpp:41:ComponentRegister::setNewComponentState()) LED device: disabled
2021-12-08T22:10:44.303Z [ COMPONENTREG] (DEBUG) (ComponentRegister.cpp:41:ComponentRegister::setNewComponentState()) LED device: enabled
2021-12-08T22:10:49.088Z [ COMPONENTREG] (DEBUG) (ComponentRegister.cpp:41:ComponentRegister::setNewComponentState()) LED device: disabled
2021-12-08T22:10:55.297Z [ WEBSOCKET] (DEBUG) (JsonAPI.cpp:1099:JsonAPI::handleLoggingCommand()) log streaming deactivated for client  ::1
2021-12-08T22:10:55.297Z [ WEBSOCKET] (DEBUG) (JsonAPI.cpp:1090:JsonAPI::handleLoggingCommand()) log streaming activated for client ::1
2021-12-08T22:10:55.297Z [ WEBSOCKET] (DEBUG) (JsonAPI.cpp:1090:JsonAPI::handleLoggingCommand()) log streaming activated for client ::1

Hi
I retested with the latest WLED version and cannot reproduce the issue.
Maybe you can retest with Hyperion's nightly build to see, if the issue still exists on your end.
I will close the issue for the time being.


Impossible to delete image from Web interface

I run frontend with next yml file:
registry-frontend:
restart: never
image: konradkleine/docker-registry-frontend:v2
container_name: docker-registry-frontend
ports:
- 8443:443
environment:
- ENV_DOCKER_REGISTRY_HOST=bla.bla.com
- ENV_DOCKER_REGISTRY_PORT=443
- ENV_DOCKER_REGISTRY_USE_SSL=1
- ENV_USE_SSL=yes
volumes:
- /opt/docker-registry/certs/domain.crt:/etc/apache2/server.crt
- /opt/docker-registry/certs/domain.key:/etc/apache2/server.key
Web interface work fine, but there are no any controls to delete image or repo

Please look at the README. This feature is currently disabled.


expire comment by composer package version

the idea is to expire a comment when a composer dependency is updated to a certain version, because you e.g. might wanne to cleanup some hacks which are currently required but are not longer after updates of said dependency.
a possible syntax could be similar to the version constraint one, but just with an additional composer package name prefixed
// TODO: phpunit/phpunit:<10 This has to be fixed when updating to phpunit 10.x

see https://github.com/phpstan/phpstan/issues/9056

needs a POC and I am not sure yet, whether I like it.

I do have some working rule in a closed source repo I can share

sure, go ahead :)

sorry, you were too fast :joy:


[Fix] Update AddYourChainButton URL in ChainList page to new support form link

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#3714  👈
#3713
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @jnsdls and the rest of your teammates on  Graphite


[Django 3.0] ImportError: cannot import name 'python_2_unicode_co…

…mpatible' from 'django.utils.encoding'
What changes were proposed in this pull request?
from django.utils.encoding import python_2_unicode_compatible
to
from six import python_2_unicode_compatible

nit: [Django Upgrade] --> [django 3.0]
nit: please include more description/context on the deprecation in the commit message (like I put below..), it helps understand if we are going to break things

done, okay


District hover in the table changes the map and map stats  (#297)

Districts not highlighted on map while hovering table
Fixed bugs for fast changing between country and state
Fixed bug while changing from country map to state map
Merge conflict
Highlight region fixed
Pulled the latest code and solved the merge conflicts
Fixed initial highligting of a region on map on hover of district and state in the table
Fixed multiple districts are highlighted

Co-authored-by: Yogishankar 1<EMAIL_ADDRESS>

@shuklaayush so I'm seeing two tables :P


revert to manual dbmap init

Hey @gdanezis the reason I have not merged this yet is that it does not entirely solve the problem of allowing callers of open to specify the options per table. The impl above forces every caller to use the same configs, which is not ideal.
See this PR for one way we could do it.
It basically gives you a way to specify the options for each table before opening.
This will also enable us solve the Sui-Narwhal db open issue you flagged here which lets Sui specify the table options
Let me know if you want this new approach instead.

@oxade should we close this in favor of #4025 ?

@oxade should we close this in favor of #4025 ?

Yes. Will close once other is merged


add parameter for optional cmdline logging

Coverage decreased (-0.04%) to 91.906% when pulling e545f868ea1c06a4ecb722d659320faa1eaf81dc on SAP:cmdline-optional-logs into e46a6aee096a72f2aa2c49526b33a22a7f8ea09a on cloudfoundry-incubator:master.

Coverage increased (+0.01%) to 91.954% when pulling 4ee51d9eeb1ec169240ac0035895c4c0f27c561e on SAP:cmdline-optional-logs into e46a6aee096a72f2aa2c49526b33a22a7f8ea09a on cloudfoundry-incubator:master.


tpcal

The tpcal.py script, calibrating the xpt2046 touch panel, still uses lvgl v6. I ported it to v7. I created 2 versions: one for portrait and one for landscape more.

Hi @uraich,
Thank for your contribution!

Please rebase your changes. lv_colors.py is already in the repo and your commit tries to re-add it.
Why did you choose to split it to two scripts? Is it possible to change the existing script to support both modes, instead?
Code duplication makes it difficult to maintain the code in the future, and makes it harder to identify your changes by diff.

I combined the two scripts into one as requested. Changing the orientation variable allows to select portrait or landscape mode.
What do I have to do to get rid of the lv_colors? My master branch does have it included now.
Sorry, I am still not too confident with git.

What do I have to do to get rid of the lv_colors? My master branch does have it included now.

I believe that what you need to do is to git pull --rebase from lv_binding_micropython. Rebase means that your changes are "removed" and "re-applied" after pulling recent commits from the server.
After that you would need to do a git push --force to your fork because your existing commits should be replaced by the "re-applied" commits.
Have a look at some git rebase tutorial, they probably explain this much better than I do.

@uraich Did you have a chance to try my suggestion above to rebase this change in order to remove the redundant commit of lv_colors.h?

@uraich I've merged your changes.
Thanks!


Jest Circus does not wait for handleTestEvent completion.

🐛 Bug Report
In custom node environments, tearDown() method runs before testEvent() finishes.
To Reproduce
Consider this test environment:
class JestEnvironmentWebDriver extends NodeEnvironment {

  public async teardown(): Promise<void> {
    await super.teardown();

    console.info('Shutting down WebDriver environment.');
    await this.stopRemoteWebDriver();
  }

  public async handleTestEvent(event: Circus.Event, state: Circus.State): Promise<void> {
	console.info('Started taking screenshot');
    await this.takeScreenshot(event.name, state); // Slow operation.
    console.info('Finished taking screenshot');
  }
}

This prints:
Started taking screenshot
Shutting down WebDriver environment.

Expected behavior
I expect the handleTestEvent promise to be awaited before processing other events, especially calling teardown().
envinfo
  System:
    OS: macOS 10.15.4
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
  Binaries:
    Node: 12.16.1 - ~/.nvm/versions/node/v12.16.1/bin/node
    npm: 6.14.4 - ~/.nvm/versions/node/v12.16.1/bin/npm
  npmPackages:
    jest: 24.9.0 => 24.9.0

Looks like it is not reproducible in jest >= 26.6.3 anymore!


Make listener variables final

Purpose
Fixes #20892
Approach
Flag listener variables as final
Samples
Code
import ballerina/http;
listener http:Listener l = new (8080);
public function main() {
    l = new (8181);
}

Output
error: .::final_l.bal:4:5: cannot assign a value to final 'l'

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.
Maybe there is room for improvement for the error message.

Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[x] Added necessary tests

[ ] Unit Tests
[x] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

This fix should work. But I think we should improve the error message. A Listener variable is implicitly final. But it is not visible in the code. So saying cannot assign a value to final 'l' kind of misleading the developer.

Codecov Report

Merging #20917 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #20917   +/-   ##
=======================================
  Coverage   14.59%   14.59%
=======================================
  Files          51       51
  Lines        1398     1398
  Branches      214      214
=======================================
  Hits          204      204
  Misses       1178     1178
  Partials       16       16

Continue to review full report at Codecov.

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