Loop back into await/1 after processing a response

If more than one responder matches a message, the robot will send multiple
responses. The console adapter, however, was only able to handle one respose
for each line of input it received. Fix this by making await/1 call itself
after a successful match, to receive any further messages waiting in the
mailbox.

Sorry, I haven't yet thought of a clean way to test this -- at least not without introducing arbitrary delays to wait for console output being generated, etc.

Added a test that  should do the job; however,  it has a 500ms sleep period so one might want to tag it as "slow" or something, and force it to be specifically included when running tests. What do you think?

The test now passes a much more reasonable 100ms timeout to be used by await in Hedwig.Adapters.Console.Connection (only when testing), so that might make special tagging a non-issue for now (since there aren't yet at least a hundred gazillion tests to run; on my machine, tests finish in ~0.3s).

:+1:


[webview_flutter] Migrate plugin to federated architecture

Use case
Migrate the "webview_flutter" package to the federated plugin architecture. This would result in the following benefits:

Makes it easier to add support for additional platforms (specifically desktop support e.g. Windows, macOS and Linux);
Allows for easier separation of concerns especially when different platforms require different configuration settings;
The federated architecture also makes it easier to write automated tests and guard the API;
Confirms to the architecture of most other Flutter plugins, making it easier for developers to understand the project layout and contribute to the project.

Proposal
To migrate the in_app_purchase package to federated architecture we should take the following steps:

[ ] Move the webview_flutter into its own subdirectory ("webview_flutter/webview_flutter") flutter/plugins#4152;
[ ] Create the webview_flutter_platform_interface package;

[ ] Copy the LICENSE file from the webview_flutter package;
[ ] Add a CHANGELOG.md file;
[ ] Define a pubspec.yaml file;
[ ] Create a README.md file;
[ ] Define the platform interface in webview_flutter_platform.dart;
[ ] Implement the default implementation in method_channel_webview_flutter.dart;

[ ] Create an Android implementation of the webview_flutter_platform_interface in a separate webview_flutter_android package;
[ ] Create an iOS implementation of the webview_flutter_platform_interface in a separate webview_flutter_darwin package;
[ ] Refactor package webview_flutter to use the webview_flutter_android and webview_flutter_darwin packages.

One wrinkle is that it already uses the federated structure at a code level, just not a package level, so it already has a platform interface that is part of the public API. We'll either need to re-export the platform interface from a stub file in the app-facing package, or move it as a breaking change.
For ease of migration for any existing out-of-repo implementations, I think the latter is the better option. We can remove it at some later point.

Re-exposing seems a good intermediate and easy to solve solution to me. We could even mark the stub deprecated and point developers to the new platform interface. Should be very small change for developers if we leave the class name and method signatures the same. Developers simply need to add a new dependency and update the import statement.


Keras

Hey!
Could you please upload the model to be used with keras?

@AzazelHD
Perhaps this will be considered in the future, but there is no such plan at the moment. Of course, you can try it.


Add two missing converters for flask in the docs

All the converters are from werkzeug's builtin converters.
Documentation: http://werkzeug.pocoo.org/docs/dev/routing/#builtin-converters

Ping @davidism, is there any problems before merging this PR?


Impossible to flash/communicate

I'm having troubles to flash or connect my devkit v1. It arrived my home 2 days ago and I was not able to flash it or at least communicate with it.
 I connect my devkit v1 via USB to microUSB with the CP2102 USBtoUARP, then the blue led of the ESP8266 blinks twice and stop. After this I can see the SSID "AI_THINKER_DA7E19" and connect to it, I got a <IP_ADDRESS> and the device .1. It answers to the ping but there is not webserver. Now I try to flash it, first I tried with Linux and ESPTool,
# python2 esptool.py --port /dev/ttyUSB0 write_flash 0x00000 firmware.bin
Connecting...

A fatal error occurred: Failed to connect to ESP8266

Well I read somewhere it could be a bug with ESPtool with high values of baudrate, so I tried with --baud 9600 but the same output also with different baudrates. Meanwhile the program is in the state connecting..., the blue led blinks. I tried to reset with the Flash button pressed and the same result, nothing change. Also I tried wiring the GPIO0 to GND but still the same error.
Now it is the turn for Windows, I tried with the nodemcu-flasher, the driver was correctly install and the port is assigned correctly too. Select the COM port and set the baudrate to 9600 and flash. The log says Begin to find ESP8266 enters in a loop and the blue led blinks every 1/2 seconds. Just to point it out, in the tab operation not appears any mac, it says "Waiting...". Just like before I changed the Baudrate and I tried all of them but nothing happens. (I also press flash and reset like before but nothing)

After all this troubles I tried to communicate with the devkit via Serial port with putty and Screen. The connection seems to be established but nothing appears in it. Pressing RST it should write something... garbage or some characters but nothing.
I don't know if I'm doing something wrong or the devkit it's broken. Some solution or tip?
Thank you
PD: I posted it in the old devkit repository, now it is in the correct repository.
EDIT:
@mrmonteith answered in the other repository.
I'm trying to remember when I first tried this. I think I used the flasher tool. You start the attempt at transfer, hold down the reset and flasher button, release the flasher button and then about a half second or so after release the reset. I don't have my device in front of me to check. Of course I only had to do it one time and I've had mine for about month. Hope it helps anyway.

I tried too, but no works it.

Same issue here... Still can't flash the firmware...

change the USB cable.. had the same issue, resolved after changing the cable.

And here same issue. I operate PC Windows 10, And Android...,.But it's waiting for mac

Found this page when dealing with the same problem. Swapped out USB cables to no avail. A little bit more searching and I found this which wound up fixing it for me - maybe it might be helpful to others:
http://kig.re/2014/12/31/how-to-use-arduino-nano-mini-pro-with-CH340G-on-mac-osx-yosemite.html

Hey, did you ever figure this one out? I'm having pretty much the same issue on a Mac with a nodeMCU Amica board (uses a CP102 USB-UART bridge, installed the SiLab driver, etc). I have tried multiple baud rates but always get the same response: A fatal error occurred: Failed to connect to Espressif device: Timed out waiting for packet header.
I have tried multiple USB cables and multiple NodeMCUs to no avail. Really bummed right now...

@JayPalm did you try the link I listed in my last comment?

Facing the same issue.. Anyone found the cause of the problem? or a solution that worked..

Any luck yet?  I had a couple of thoughts.  Mostly around possibly weak components.  Do you have any sort of oscilloscope? I bought a Hantek digital one that connects to the computer and does fairly good.  That would go a long ways to checking things like power supply voltages and noise on the lines.   But without you can still probably locate the issue.   A couple of things you can try.  That is put a capacitor between 3v3 and Gnd as an extra filter.  USB interfaces are notoriously noisy.    There is also an Espressif forum for issues with the ESP8266 and ESP32 devices.  You might post there too.

Just reconnect the usb cable keeping the flasher open
Look for log for below line ->

Note:Detect serial port changed.
Note:Auto MAP serial port.Port-->COM5
Then you should be able to flash. Looks like the tool cannot detect already connected device.

i had same issue. i change usb cable and tried different values for advanced setting on Nodemcu. and it worked by
-Baudrate 9600, -flash size 4Mbyte, -flash speed 26.7mhz, -spi mode DIO

Try holding down the GPIO/reset button on your MCU, and then flash whilst still holding down. This worked for me.

Same issue. Won't flash

Just reconnect the usb cable keeping the flasher open
Look for log for below line ->

Note:Detect serial port changed.
Note:Auto MAP serial port.Port-->COM5

Then you should be able to flash. Looks like the tool cannot detect already connected device.

Just reconnect the usb cable keeping the flasher open
Look for log for below line ->

Note:Detect serial port changed.
Note:Auto MAP serial port.Port-->COM5

Then you should be able to flash. Looks like the tool cannot detect already connected device.

That's not the issue, it's able to detect the right com port right from the start

That's not the issue, it's able to detect the right com port right from the start

did you try by another usb cable. i had same issue and changed the cable. i tried by my printers cable and it worked :)
and i attached the picture of working settings on my ESP8266 -ESP 01

Okay I resolved this for me. You just need to hold down the flash button until you the status bar moving forward after pressing flash

Mine was fixed by putting the board to an oven for two minutes. Looks like a weak components issue

I am also having the same issue. It says “waiting mac” however my FTDI and ESP is flashing red and the ESP was also flashing blue for a couple seconds then stopped. Is there anything I am doing wrong here?

I had the same problem but i solved it, it was my usb port. Looks like it the current of that one was to low. So try a different usb port!


How to build adaptive NSGAII based on pymoo

I want to implement an adaptive NSGAII with a mutation probability related to the number of iterations. How can I achieve this

You can achieve this with a custom callback:
from pymoo.core.callback import Callback

class MyCallback(Callback):
    def notify(self, algorithm):
        if algorithm.n_gen > 10:
           algorithm.mutation = ...


Set Up is near impossible in intel Visual Studio 2022 in Windows 11 for Python

This issue has been moved from a ticket on Developer Community.

[severity:It's more difficult to complete my work]
While attempt to use Python is really too difficult to get it to work. Setting the right environment. I notice this: I am in an Intel mainboard. However, in other my AMD mainboard is working fine.

Original Comments
Feedback Bot on 11/28/2022, 11:07 PM:
(private comment, text removed)

Original Solutions
(no solutions)

Hi there, could you share a little bit more about the issues you're experiencing? What specific issues have you encountered? That will help us further investigate the issues. Thanks!

Going to close this out. If the issue still persists, please reopen with the information requested. Thanks.😊


pre-fix for motion

This disable export for spring animations as a temporary fix to avoid a bug that hinders export.
Implementing export for spring is coming up next.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

6 of 6 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.06%) to 80.589%

Totals

Change from base Build<PHONE_NUMBER>:
0.06%

Covered Lines:
527

Relevant Lines:
647

💛  - Coveralls


time: Ticker CPU behavior with for-range and for-select

What version of Go are you using (go version)?

$ go version
go version go1.13 darwin/amd64

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/xiao/Library/Caches/go-build"
GOENV="/Users/xiao/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=" -mod="
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/xiao/.go"
GOPRIVATE=""
GOPROXY="https://goproxy.cn,https://goproxy.io,direct"
GOROOT="/usr/local/Cellar/go/1.13/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.13/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/xiao/fancy/Code/ad_go/go-app/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/9d/7xkt00_57_z5jc0vc334wd080000gn/T/go-build401848648=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?
The following code is a simplified version of the online service, after long time running(>a week), CaseOne will cause much more CPU usage than CaseTwo, (online service cpu problem be fixed after modifying to caseTwo);
package main

import (
	"fmt"
	"github.com/labstack/echo/v4"
	"time"
)

func CaseOne() {
	ticker := time.NewTicker(time.Millisecond * 10)
	i := 0
	for range ticker.C {
		if i % 100000 == 0{
			fmt.Println("i:", i)
		}
		i++
	}
}

func CaseTwo() {
	ticker := time.NewTicker(time.Millisecond * 10)
	i := 0
	for {
		select {
		case <- ticker.C:
			if i % 100000 == 0{
				fmt.Println("i:", i)
			}
			i++
		}
	}
}

func main()  {

	go CaseOne()

	//go CaseTwo()

	e := echo.New()
	e.GET("/ping", func(context echo.Context) error {
		context.String(200, "pong")
		return nil
	})
	e.Start("<IP_ADDRESS>:8888")
}

What did you expect to see?
same behavior, normal cpu usage.
What did you see instead?
after long time running, CaseOne cause service much more CPU usage than CaseTwo. (500% CPU : 10% CPU in average)

@HuanGong please upgrade to Go 1.15.2 and confirm if the problem still exists.
Also, is it necessary to run a http server to demonstrate this issue? This program
package main

import (
        "fmt"
        "time"
)

func CaseOne() {
        ticker := time.NewTicker(time.Millisecond * 10)
        i := 0
        for range ticker.C {
                if i%100000 == 0 {
                        fmt.Println("i:", i)
                }
                i++
        }
}

func CaseTwo() {
        ticker := time.NewTicker(time.Millisecond * 10)
        i := 0
        for {
                select {
                case <-ticker.C:
                        if i%100000 == 0 {
                                fmt.Println("i:", i)
                        }
                        i++
                }
        }
}

func main() {

        go CaseOne()

        CaseTwo()
}

consumes a low amount of CPU under Go 1.15.2

thanks for your reply, http server is not the must, just for simulating the closest environment to online service.

@HuanGong using the program I supplied above, can you reproduce the problem?

@davecheney  seems fixed.

@davecheney  seems fixed.


Fix typo saying "more than" to "less than"

There were conflicts with the .RData file and GitHub browser wasn't permitting me to resolve them.


Wiki: use of $GOPATH

Not sure how I can put this into the project. It might not be an issue:
I was thinking about if it would make sense to use $GOPATH instead of the fullpath in the examples of the wiki?
So, instead of
export JAYCONFIG=$HOME/godev/workspace/src/github.com/blue-jay/blueprint/env.json

just:
export JAYCONFIG=$GOPATH/src/github.com/blue-jay/blueprint/env.json

Thanks!

Yep, that does make sense. I updated all the OS pages in the Wiki: https://github.com/blue-jay/blueprint/wiki

Thanks!


New feature for friendly_name??

Hi, Awesome work, thanks a lot !!
I live in Japan.
I set Japanese name(2-byte font) by 'friendly_name' each sensors/switch.
Could you plz support 'friendly_name' ?

What happens if you enter your 'friendly name' in the name attribute? I am a bit confused by the difference between the friendly name and name, my current understanding is, that it is essentially the same thing - in the past we used to have mandatory entity_id and optional friendly name, but as the config slowly moves from yaml, we do not set entity_id manually and the friendly name is just the name. But I might be wrong...

Thanks to reply, bruxy70.
I'll try to explain why I want friendly_name id.
When I enter the Japanese language into a name of entity like below,

- platform: garbage_collection
  name: '金属ごみ'
  frequency: "weekly"
  verbose_state: true
  collection_days: "sat"

However, the word "金属" is automatically changed into a chinese language transribe.
Like this,

sensor.jin_shu_gomi
("jin_shu" is Chinese and "ごみ" is Japanese.)

the word above is nothing to mean for Japanese people.
So,I expect the name of entity is only alphanumeric.
In most cases, HA changes KANJI into a chinese transribe.
If it's adopted a friendly_name,I think it will be solved this issue.
For exmple;

- platform: garbage_collection
  name: garbage_burnable
  friendly_name: '可燃ゴミ'
  verbose_state: true
  frequency: "weekly"
  collection_days:
  - mon
  - thu

- platform: garbage_collection
  name: garbage_mixpaper
  friendly_name: 'ミックスペーパー'
  verbose_state: true
  frequency: "weekly"
  collection_days: "sat"

- platform: garbage_collection
  name: garbage_metal
  friendly_name: '小物金属/粗大'
  frequency: "weekly"
  verbose_state: true
  collection_days: "sat"

Ok, get it. But what you describe is, you want to manually define the entity_id, not the friendly_name.
The name or (friendly name) is what Home Assistant displays on the screen. name and friendly_name is the same thing.  I think name is used recently as it is shorter.  If you look in the sensor attributes, you will see. I have tried to define both, but it does not do anything, it just overwrites itself with what is in name.
sensor.jin_shu_gomi is entity id. It is generated automatically. It is not shown anywhere for the user, it is internal to HA - why is it an issue?

Ok. I got it, too.
I'll wait for you code the way to change the entity_id.
Thanks.

After some research, I decided to come up with a quick fix, that should solve your issue. I think I might be breaking the rules a bit, so I will keep looking at better solutions. But it should do the trick. After you update to v1.14, you can go to Configuration/Entity Registry and change the entity_id. Let me know if it worked.

@k1asa, I just made a new release with the permanent solution for your request. This will be a breaking change for you. Please review the release notes. In your case I think you should move the configuration from YAML to the GUI config from the Integrations page.


Python-level middlewares for transforming values

It would be neat if we could have something like plugins that sit between the client object and the C client.
There's really only one way to go here if so: expose a much cleaner cut of the C API and implement all composite operations and stuff in Python. This will have implications for performance and such, so is it really relevant?
This spawns as a discussion from #22 and #23

I'm using memcached in php for "frontend" and python for "backend" tasks (like replicating stuff for users).
Currently all libs are kinda shitty ;) If i can match algorithm (and now both php-memcached and pylibmc are using libmemcached "ketama algorithm" for this) i cannot match flags and types of data...  It would be awesome if something could work with libmemcached and could be extended.
Also i wrote some code for my library. All in python with implementation of few methods from memcache api (with binary protocol) but the consistent hashing is kinda slugish in python (i need to rewrite it or make some cache/other changes/dunno).
So if You want somebody to work with on the python/C pylibmc version just write ;) I'm up for a job in python.
And i think it could be done faster than we think. If only PylibMC_Client_get could return for example dictionary like:
{"flag" : 1, data: "something"} without using _PylibMC_parse_memcached_value  it could be parsed in python without any problems. And default pickle/unpickle thing should be as fast as in C (i think).

#23 discusses that approach, what I would like to see then is some alternative base class which doesn't do any decoding/encoding at all; perhaps something like RawClient? I think a dict would be nice, but really it would be better to create a result class that whose str(x) returns the byte data and has a result.flags attribute.

Another issue with this approach is that I would much prefer to break up the now rather huge _pylibmcmodule.c into more useful subcomponents; I tried this once and the problem is that there are a lot of static symbols that need to be shared across compilation units. I'm no compiler pro, so if somebody could chime in on how to break up Python C extensions over multiple compilation units, I'm all ears.

This is now doable I believe


Preparation for mirroring repo

I'm trying to mirror the repo into my namespace (similar to AJSON in AG). There are a few things that abaplint can't do automatically:

Adjusting variable names (lx to lx_error)

Reorder definitions with BEGIN/END to top (https://github.com/abaplint/abaplint/issues/1505)

Method chaining (702)

Do you mind if I make these adjustment in a PR?

Sure, feel free to PR.
A bit tentative about lx - I do like this style - but let's do it too


Adding Rabby's open-sourced relay service after WalletConnect v1.0 relay servers' shutdown

Issue
WalletConnect v1.0 relay server is expected to be offline on 28 June, 2023. To ensure uninterrupted usage and connectivity following the official v1.0 server shutdown, we are proposing the integration of Rabby's open-sourced relay service. This relay service, maintained by Rabby, will guarantee continued connection between Dapps and Wallets using WalletConnect for users.
Solution
We have included Rabby's self-host relay(https://derelay.rabby.io/) address in the web3 Wallet Connect kit, ensuring that users can connect to Dapp using WalletConnect. This address will become effective once the official relay server shuts down.
Testing plan
We have thoroughly tested the solution in both the testing environment and the live online environment. Based on our testing, we are confident that the solution will enable users to connect to Dapps using WalletConnect without any issues.

@heisenberg-2077 Is there a reason Rabby is taking this approach versus supporting v2? Are there blockers we need to relay to the WalletConnect team?

Will close for now.


Add uuid field to Page model

Related issue: #6162
Possibly resolves: #6917.
Takes care of adding the field and generating initial values (based on url_path) via a data migration.
Any further changes relating to #6162 can be added via separate PRs.
The most contentious part of this is probably the data migration, as that will quite obviously take a while to run on sites with large numbers of pages. Thankfully, we're only supporting Django 2.2 and later now, so we can utilise bulk_update(). We can likely increase the batch size used here in order to blast through things more quickly. Does anybody know if we have any 'minimum requirements' anywhere that would help indicate how much memory we have to play with?

Thanks for submitting this @ababic!
This actually overlaps a bit with a proposal that I wanted to make at some point in the future, which was to introduce a locale (FK to a Locale model) and translation_key (UUID) fields on Page. In my proposal, the UUID would only be unique within a locale and not for the whole instance (the same UUID will be shared between translations of the same page), but a locale/UUID combination would be globally unique. Effectively, the UUID would still represent a single page, but that page could exist in multiple languages on a Wagtail instance.

Cheers for taking a look @kaedroho. I considered the translation stuff when adding this, and I think the use-cases are similar, but different. This is more like an 'alternative primary key' - so I believe the value here should be universally unique. translation_key in your example has different requirements, and so would simply be separate field.
Off-topic, but I wonder whether introducing a PageTranslation model would be valuable there, and translation_key would become a ForeignKey to that model? That way, you could store a reference to the 'original language version' there (amongst other things), and you could use translation_id to identify translations just as efficiently?

Off-topic, but I wonder whether introducing a PageTranslation model would be valuable there, and translation_key would become a ForeignKey to that model? That way, you could store a reference to the 'original language version' there (amongst other things), and you could still use the translation_id column on the Page model to identify related pages as efficiently?

Sort of like the TranslatableObject model in the translation app? https://github.com/wagtail/wagtail-localize/blob/master/wagtail_localize/translation/models.py#L39
I had considered this, but I went with the translation key approach mainly because it was easy to set the default value, so there won't be any cases where the field is None to handle. This might not be much of a problem if this was implemented in core though!

EDIT: Hmm, actually, you got me thinking now. None would be beneficial as it would tell us the page has no translations, which might optimise some queries... We only need to set it when copy_for_translation is called.

This exactly :) Also, it could be convenient to have a model at that level in case it were needed in future (to store data relevant to all translations of a page)

Closing due to lack of interest


Add @impl true to the callbacks injected in sql adapters

Avoid compiler warnings

@rbino which warnings? I see no warnings when compiling the ecto_sql project. Which Elixir version are you running on?

$ elixir -v
Erlang/OTP 20 [erts-9.1] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:10] [hipe] [kernel-poll:false]

Elixir 1.6.3 (compiled with OTP 19)

Just tested with a fresh empty project, adding
{:ecto_sql, github: "elixir-ecto/ecto_sql"}

to mix.exs, mix deps.get and mix.compile gives me:
...
Compiling 23 files (.ex)
warning: module attribute @impl was not set for function transaction/3 callback (specified in Ecto.Adapter.Transaction). This either means you forgot to add the "@impl true" annotation before the definition or that you are accidentally overriding this callback
  lib/ecto/adapters/postgres.ex:99
warning: module attribute @impl was not set for function stream/5 callback (specified in Ecto.Adapter.Queryable). This either means you forgot to add the "@impl true" annotation before the definition or that you are accidentally overriding this callback
  lib/ecto/adapters/postgres.ex:99
warning: module attribute @impl was not set for function rollback/2 callback (specified in Ecto.Adapter.Transaction). This either means you forgot to add the "@impl true" annotation before the definition or that you are accidentally overriding this callback
  lib/ecto/adapters/postgres.ex:99
warning: module attribute @impl was not set for function init/1 callback (specified in Ecto.Adapter). This either means you forgot to add the "@impl true" annotation before the definition or that you are accidentally overriding this callback
  lib/ecto/adapters/postgres.ex:99
warning: module attribute @impl was not set for function in_transaction?/1 callback (specified in Ecto.Adapter.Transaction). This either means you forgot to add the "@impl true" annotation before the definition or that you are accidentally overriding this callback
  lib/ecto/adapters/postgres.ex:99

warning: module attribute @impl was not set for function checkout/3 callback (specified in Ecto.Adapter). This either means you forgot to add the "@impl true" annotation before the definition or that you are accidentally overriding this callback
  lib/ecto/adapters/postgres.ex:99

warning: module attribute @impl was not set for macro __before_compile__/1 callback (specified in Ecto.Adapter). This either means you forgot to add the "@impl true" annotation before the definition or that you are accidentally overriding this callback
  lib/ecto/adapters/postgres.ex:99

warning: module attribute @impl was not set for function transaction/3 callback (specified in Ecto.Adapter.Transaction). This either means you forgot to add the "@impl true" annotation before the definition or that you are accidentally overriding this callback
  lib/ecto/adapters/mysql.ex:117

warning: module attribute @impl was not set for function stream/5 callback (specified in Ecto.Adapter.Queryable). This either means you forgot to add the "@impl true" annotation before the definition or that you are accidentally overriding this callback
  lib/ecto/adapters/mysql.ex:117

warning: module attribute @impl was not set for function rollback/2 callback (specified in Ecto.Adapter.Transaction). This either means you forgot to add the "@impl true" annotation before the definition or that you are accidentally overriding this callback
  lib/ecto/adapters/mysql.ex:117

warning: module attribute @impl was not set for function init/1 callback (specified in Ecto.Adapter). This either means you forgot to add the "@impl true" annotation before the definition or that you are accidentally overriding this callback
  lib/ecto/adapters/mysql.ex:117

warning: module attribute @impl was not set for function in_transaction?/1 callback (specified in Ecto.Adapter.Transaction). This either means you forgot to add the "@impl true" annotation before the definition or that you are accidentally overriding this callback
  lib/ecto/adapters/mysql.ex:117

warning: module attribute @impl was not set for function checkout/3 callback (specified in Ecto.Adapter). This either means you forgot to add the "@impl true" annotation before the definition or that you are accidentally overriding this callback
  lib/ecto/adapters/mysql.ex:117

warning: module attribute @impl was not set for macro __before_compile__/1 callback (specified in Ecto.Adapter). This either means you forgot to add the "@impl true" annotation before the definition or that you are accidentally overriding this callback
  lib/ecto/adapters/mysql.ex:117

Generated ecto_sql app
...

I see. Those were improved on Elixir v1.7 which is why I didnt see it locally!


docs: added new example

with nextjs 14 (app router) vite (tanstack router) shadcn/ui
Description
Apps and Packages

admin: a Next.js app
super-admin: Vite + React and Ant design app and using tanstack router and jotai for state management
web: another Next.js app
ui: a stub React component library shared by both web and docs applications (🚀 powered by shadcn/ui)
eslint-config-custom: eslint configurations (includes eslint-config-next and eslint-config-prettier)
tsconfig: tsconfig.jsons used throughout the monorepo

@Parthvsquare 👋
Looking at our other examples, this proposal doesn't quite fit the mold.

We already have examples for Next.js and Vite, so we don't want to duplicate.
We keep the examples extremely light and simple, so the application with Ant Design, TanStack Router, and Jotai doesn't really fit what we're looking for.

That said, we do want a shadcn/ui example! Do you think you could make one, starting with the basic example and replacing the ui package with shadcn/ui?

@anthonyshew
should i close this and make a new PR? or edit the current one?

We already have examples for Next.js and Vite, so we don't want to duplicate

Yes, but we don't have for both in one app folder

should i close this and make a new PR? or edit the current one?

Edit this one works. 👍

Yes, but we don't have for both in one app folder

The kitchen-sink example has multiple frameworks in one example. It doesn't specifically have Next.js + Vite out of the box  - but the Remix app could quickly be adapted to a Vite application.


Pattern rule does not work correctly.

For some reason, jsonschema does not handle pattern rule correctly.
from jsonschema import validate

schema = {
    "type" : "object",
    "properties" : {
        "price" : {"type" : "string", 'pattern': '^[a-z]+$'},
    },
}

# Works
validate(instance={ "price" : 'badstring\n\n'}, schema=schema)

# Does not work
validate(instance={ "price" : 'badstring\n'}, schema=schema)

Please don't file bugs saying entire large swaths of functionality don't work -- jsonschema is fairly well tested.
In your case, yes, that's what $ does in Python regexes. See the documentation on regexes for the $ character, as well as simply trying re.search('^[a-z]+$', 'badstring\n\n').


Fixes #19 - 0 is not undefined anymore in labels

Handle y=0 while x=undefined with care
Explanation
Before we were getting the bug when y = 0 and x = undefined which would cause value to be undefined
Really that should give use a label of 0 and so value should be 0 as well
Also tagging @MartinMuzatko since already submitted a fix : )

+1


Aztec Code

Would be nice to have support for Aztec Code too (https://en.wikipedia.org/wiki/Aztec_Code)

+1

Hi, I would love to implement it but I dont have all required information to so so :(

For me it is solved by using Mint (binary) to generate the Aztec barcode. Not as nice as doing it in Go but my knowledge of Go is not good enough to port an existing Aztec encoder to it.

I've started porting the aztec code generation from zxing.
I would normally not do this because I started this project to learn how different barcodes are encoded from scratch.
But I guess its better to learn from other peoples code, then not learning anything :)

Cool! I would definitely switch to using Aztec generation through go lang!
I learned a lot by porting PDF417 barcodes from PHP to Go :)

Hey, please test this and let me know if there are any issues...

Seems working for my use case (encoding 2 space-padded int64 seperated with a dash). This is much appreciated!!


NextJS - Support for defaultProps

Hello guys,
I installed the lite version on a Next.js v14 project and encountered a warning. I'm wondering if this issue is something that is planned to be addressed in future versions of react-share-lite or react-share-kit?
Warning: h: Support for defaultProps will be removed from function components in a future major release. Use JavaScript default parameters instead.
I'm using PNPM, Next 14.1.0

See that warning in my end as well
Warning: p: Support for defaultProps will be removed from function components in a future major release. Use JavaScript default parameters instead.
    at p (webpack-internal:///(ssr)/./node_modules/react-share-kit/dist/index.es.js:34:32147)
    at a (webpack-internal:///(ssr)/./node_modules/react-share-kit/dist/index.es.js:34:34514)
    at div
    at Share (webpack-internal:///(ssr)/./app/cal_view/[id]/components/sidebar/Share.tsx:15:18)
    at div
    at div
    at div

See that warning in my end as well
Warning: p: Support for defaultProps will be removed from function components in a future major release. Use JavaScript default parameters instead.
    at p (webpack-internal:///(ssr)/./node_modules/react-share-kit/dist/index.es.js:34:32147)
    at a (webpack-internal:///(ssr)/./node_modules/react-share-kit/dist/index.es.js:34:34514)
    at div
    at Share (webpack-internal:///(ssr)/./app/cal_view/[id]/components/sidebar/Share.tsx:15:18)
    at div
    at div
    at div

I'm moving to https://next-share.js.org/ @Berdugo1994


client-only: add layer

The meta-mender-client-only layer enables the Mender client to be installed and operated without the full integration in place.
Changelog: Title
Ticket: None

@kacf yes that exactly is the purpose, for some reasons:

makes it easy to get started with Mender on Yocto without having to do the full integration
allows for UMs to use other, existing mechanisms such as SWupdate, RAUC, ...

Great, makes a lot of sense!

@kacf the key idea is to be as little intrusive as possible. I also thought about pouring this into a MENDER_FEATURE like mender-standalone or whatever, but in any case that requires more effort, respectively creates more friction and clashes in more places. This way, at least to get started, the process matches developer expectations: add a layer, add something to IMAGE_INSTALL. Thats why I'd like to go this route, at least for the first iteration.

I see the incentive, but I actually think this really belongs in the core layer. And the fixes that will inevitably result from this work are all very welcome, it's an overlooked area up until now.
I think if we just stay very disciplined, this shouldn't create a lot of friction. And by this I mean:

For the non-integration case, when just installing the client, we don't require any MENDER_FEATURES to be turned on.
When all features are off, I think it's better to not think of the image as "not a Mender image, there are definitely no rootfs updates", but rather "this is a custom image, we don't know if it has rootfs updates or not, so let's not assume anything".
Due to the last point, we must be careful that all image changes outside the recipe itself and its files, are strictly kept out of the build when no features are turned on.

That means no symlinks to data partitions.
It also means no device_type file, though we could offer this file in a separate recipe, or as a PACKAGECONFIG. The reason this is important is that this file by its very nature lives on a persistent partition. But in the non-integration case, we don't know where this partition is, so we should not offer it out of the box unless you ask for it.

What do you think? Am I overthinking it, or is there something there?

@kacf You are not overthinking it, this is actually the reason why it took so long to come with this solution, and why I asked so many questions. The key conclusion I took is "in a perfect world, solution for this would go into meta-mender-core, but I'm not sure when the required effort could be spent". Because it also requires figuring out the places where the recipes are not clean right now.
Then, how to fine tune the client installation where applicable. Still use MENDER_FEATURES? The same ones? Or add a mender-client-only feature which means this and is mutually exclusive with mender-image?
Also some experimentation I did was adding a new mender-client-only package which then pulls in mender-client, as opposed to a .bbappend.
In the long run we should strive for it, I completely agree. But until that is done, better to have something not perfect but good enough, instead of nothing. :-)


🐛 Bug Report: not able to start a new backstage project using Docker tutorial

📜 Description
I'm not able to start a new backstage project with Docker.
👍 Expected behavior
Containers should run smoothly
👎 Actual Behavior with Screenshots
Error:
➜  backstage-test git:(main) ✗ docker run -it -p 7007:7007 backstage
Loaded config from app-config.yaml, app-config.production.yaml
{"level":"info","message":"Found 1 new secrets in config that will be redacted","service":"backstage"}
{"level":"info","message":"Created UrlReader predicateMux{readers=azure{host=dev.azure.com,authed=false},bitbucketCloud{host=bitbucket.org,authed=false},github{host=github.com,authed=false},gitlab{host=gitlab.com,authed=false},awsS3{host=amazonaws.com,authed=false},fetch{}","service":"backstage"}
Backend failed to start up Error: Failed to connect to the database to make sure that 'backstage_plugin_catalog' exists, Error: connect ECONNREFUSED <IP_ADDRESS>:5432
    at /app/node_modules/@backstage/backend-common/dist/index.cjs.js:985:17
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async CatalogBuilder.build (/app/node_modules/@backstage/plugin-catalog-backend/dist/index.cjs.js:4952:22)
    at async createPlugin$4 (/app/packages/backend/dist/index.cjs.js:82:40)
    at async main (/app/packages/backend/dist/index.cjs.js:228:29)

👟 Reproduction steps
I'm following this tutorial here
https://backstage.io/docs/deployment/docker
and using this Dockerfile (also from the tutorial)
FROM node:16-bullseye-slim

# Install sqlite3 dependencies. You can skip this if you don't use sqlite3 in the image,
# in which case you should also move better-sqlite3 to "devDependencies" in package.json.
RUN --mount=type=cache,target=/var/cache/apt,sharing=locked \
    --mount=type=cache,target=/var/lib/apt,sharing=locked \
    apt-get update && \
    apt-get install -y --no-install-recommends libsqlite3-dev python3 build-essential && \
    yarn config set python /usr/bin/python3

# From here on we use the least-privileged `node` user to run the backend.
USER node

# This should create the app dir as `node`.
# If it is instead created as `root` then the `tar` command below will fail: `can't create directory 'packages/': Permission denied`.
# If this occurs, then ensure BuildKit is enabled (`DOCKER_BUILDKIT=1`) so the app dir is correctly created as `node`.
WORKDIR /app

# This switches many Node.js dependencies to production mode.
ENV NODE_ENV production

# Copy repo skeleton first, to avoid unnecessary docker cache invalidation.
# The skeleton contains the package.json of each package in the monorepo,
# and along with yarn.lock and the root package.json, that's enough to run yarn install.
COPY --chown=node:node yarn.lock package.json packages/backend/dist/skeleton.tar.gz ./
RUN tar xzf skeleton.tar.gz && rm skeleton.tar.gz

RUN --mount=type=cache,target=/home/node/.cache/yarn,sharing=locked,uid=1000,gid=1000 \
    yarn install --frozen-lockfile --production --network-timeout 300000

# Then copy the rest of the backend bundle, along with any other files we might want.
COPY --chown=node:node packages/backend/dist/bundle.tar.gz app-config*.yaml ./
RUN tar xzf bundle.tar.gz && rm bundle.tar.gz

CMD ["node", "packages/backend", "--config", "app-config.yaml"]

nvm use node 16

npx @backstage/plugin-app-backend

yarn install --frozen-lockfile

yarn tsc

yarn build:backend

docker image build . -f packages/backend/Dockerfile --tag backstage

docker run -it -p 7007:7007 backstage

📃 Provide the context for the Bug.
No response
🖥 Your Environment
No response
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

This line is pretty interesting: Backend failed to start up Error: Failed to connect to the database to make sure that 'backstage_plugin_catalog' exists, Error: connect ECONNREFUSED <IP_ADDRESS>:5432 looks like one of the app-config.yaml files looks like it's trying to connect to postgres instead of sqlite. Is that something that you expected?

I'm currently looking into running Backstage in Docker at my company and I solved this issue by either setting ENV NODE_ENV to development instead of production, so its like this ENV NODE_ENV development, if you want to use Docker for local development.
You can also fill in the details for a PostgreSQL database in your app-config.production.yaml and it should be able to startup.
If you dont want to use a database I assume you could use SQLite instead of PostgreSQL in app-config.production.yaml.

I had the same issue that it was trying to connect to localhost:5432.
For me, the app-config.**production**.yaml still had the postgres-database in the database section for some reason? I changed it to better-sqlite3 (like in hte app-config.yaml) and then it worked!

If you run into the Failed to connect to the database to make sure that '...' exists error it means that your Backstage instance is configured to use PostgreSQL but it's not able to connect to it.
Configuration is selected via the command line args, by default app-config.yaml and app-config.local.yaml will be loaded if present. The recommended docker setup explicitly sets this to only --config app-config.yaml though. If you want to use additional or different config files, you'd use for example --config app-config.yaml --config app-config.production.yaml. More on all of that here: https://backstage.io/docs/conf/writing#configuration-files
The NODE_ENV is used to select the behavior of many Node.js packages at runtime, but it will not select the config that is used. For example, setting NODE_ENV=production will cause certain Backstage backend startup failures to be reported as errors that halt the startup, instead of warnings.
SQLite is not recommended for use in production as it does not persist your data and does not perform well once you go beyond a small deployment.

It's crazy i still have this problem.
Here's my app-config.yaml
app:
  title: Test Backstage
  baseUrl: http://localhost:3000

organization:
  name: testorg

backend:
  # Used for enabling authentication, secret is shared by all backend plugins
  # See https://backstage.io/docs/auth/service-to-service-auth for
  # information on the format
  # auth:
  #   keys:
  #     - secret: ${BACKEND_SECRET}
  baseUrl: http://localhost:7007
  listen:
    port: 7007
    # Uncomment the following host directive to bind to specific interfaces
    # host: <IP_ADDRESS>
  reading:
    allow:
      - host: raw.githubusercontent.com
  csp:
    connect-src: ["'self'", 'http:', 'https:']
    # Content-Security-Policy directives follow the Helmet format: https://helmetjs.github.io/#reference
    # Default Helmet Content-Security-Policy values can be removed by setting the key to false
  cors:
    origin: http://localhost:3000
    methods: [GET, HEAD, PATCH, POST, PUT, DELETE]
    credentials: true
  # This is for local development only, it is not recommended to use this in production
  # The production database configuration is stored in app-config.production.yaml
  database:
    client: pg
    connection:
      host: localhost
      port: 5432
      user: postgres
      password: secret
  # workingDirectory: /tmp # Use this to configure a working directory for the scaffolder, defaults to the OS temp-dir

proxy:
  ### Example for how to add a proxy endpoint for the frontend.
  ### A typical reason to do this is to handle HTTPS and CORS for internal services.
  # '/test':
  #   target: 'https://example.com'
  #   changeOrigin: true

# Reference documentation http://backstage.io/docs/features/techdocs/configuration
# Note: After experimenting with basic setup, use CI/CD to generate docs
# and an external cloud storage when deploying TechDocs for production use-case.
# https://backstage.io/docs/features/techdocs/how-to-guides#how-to-migrate-from-techdocs-basic-to-recommended-deployment-approach
techdocs:
  builder: 'local' # Alternatives - 'external'
  generator:
    runIn: 'docker' # Alternatives - 'local'
  publisher:
    type: 'local' # Alternatives - 'googleGcs' or 'awsS3'. Read documentation for using alternatives.

scaffolder:
  # see https://backstage.io/docs/features/software-templates/configuration for software template options

catalog:
  import:
    entityFilename: catalog-info.yaml
    pullRequestBranchName: backstage-integration
  rules:
    - allow: [Component, System, API, Resource, Location]
  locations:
    # Local example data, file locations are relative to the backend process, typically `packages/backend`
    - type: file
      target: ../../examples/entities.yaml

    # Local example template
    - type: file
      target: ../../examples/template/template.yaml
      rules:
        - allow: [Template]

    # Local example organizational data
    - type: file
      target: ../../examples/org.yaml
      rules:
        - allow: [User, Group]

    ## Uncomment these lines to add more example data
    # - type: url
    #   target: https://github.com/backstage/backstage/blob/master/packages/catalog-model/examples/all.yaml

    ## Uncomment these lines to add an example org
    # - type: url
    #   target: https://github.com/backstage/backstage/blob/master/packages/catalog-model/examples/acme-corp.yaml
    #   rules:
    #     - allow: [User, Group]

My Dockerfile
# This dockerfile builds an image for the backend package.
# It should be executed with the root of the repo as docker context.
#
# Before building this image, be sure to have run the following commands in the repo root:
#
# yarn install
# yarn tsc
# yarn build:backend
#
# Once the commands have been run, you can build the image using `yarn build-image`

FROM node:16-bullseye-slim

# Install sqlite3 dependencies. You can skip this if you don't use sqlite3 in the image,
# in which case you should also move better-sqlite3 to "devDependencies" in package.json.
RUN --mount=type=cache,target=/var/cache/apt,sharing=locked \
    --mount=type=cache,target=/var/lib/apt,sharing=locked \
    apt-get update && \
    apt-get install -y --no-install-recommends libsqlite3-dev python3 build-essential python3-pip && \
    pip3 install mkdocs-techdocs-core==1.1.7 && \
    yarn config set python /usr/bin/python3

# From here on we use the least-privileged `node` user to run the backend.
USER node

# This should create the app dir as `node`.
# If it is instead created as `root` then the `tar` command below will fail: `can't create directory 'packages/': Permission denied`.
# If this occurs, then ensure BuildKit is enabled (`DOCKER_BUILDKIT=1`) so the app dir is correctly created as `node`.
WORKDIR /app

# This switches many Node.js dependencies to production mode.
ENV NODE_ENV development

# Copy repo skeleton first, to avoid unnecessary docker cache invalidation.
# The skeleton contains the package.json of each package in the monorepo,
# and along with yarn.lock and the root package.json, that's enough to run yarn install.
COPY --chown=node:node yarn.lock package.json packages/backend/dist/skeleton.tar.gz ./
RUN tar xzf skeleton.tar.gz && rm skeleton.tar.gz

RUN --mount=type=cache,target=/home/node/.cache/yarn,sharing=locked,uid=1000,gid=1000 \
    yarn install --frozen-lockfile --production --network-timeout 300000

# Then copy the rest of the backend bundle, along with any other files we might want.
COPY packages/backend/dist/bundle.tar.gz app-config.yaml app-config.production.yaml ./
RUN tar xzf bundle.tar.gz && rm bundle.tar.gz

CMD ["node", "packages/backend", "--config", "app-config.yaml", "--config", "app-config.production.yaml"]

I run yarn build:backend then docker image build . -f packages/backend/Dockerfile --tag backstage and  docker run -it -p 7008:7008 backstage
I still end up with this error:
2023-07-04 19:36:46 Loaded config from app-config.yaml, app-config.production.yaml
2023-07-04 19:36:46 2023-07-04T18:36:46.075Z backstage info Found 4 new secrets in config that will be redacted
2023-07-04 19:36:46 2023-07-04T18:36:46.092Z backstage info Created UrlReader predicateMux{readers=azure{host=dev.azure.com,authed=false},bitbucketCloud{host=bitbucket.org,authed=false},github{host=github.com,authed=true},gitlab{host=gitlab.com,authed=false},awsS3{host=amazonaws.com,authed=false},fetch{}
2023-07-04 19:36:46 Backend failed to start up Error: Failed to connect to the database to make sure that 'backstage_plugin_catalog' exists, Error: connect ECONNREFUSED <IP_ADDRESS>:5432
2023-07-04 19:36:46     at /app/node_modules/@backstage/backend-common/dist/index.cjs.js:963:17
2023-07-04 19:36:46     at processTicksAndRejections (node:internal/process/task_queues:96:5)
2023-07-04 19:36:46     at async CatalogBuilder.build (/app/node_modules/@backstage/plugin-catalog-backend/dist/cjs/CatalogBuilder-26406e82.cjs.js:4829:22)
2023-07-04 19:36:46     at async createPlugin$4 (/app/packages/backend/dist/index.cjs.js:82:40)
2023-07-04 19:36:46     at async main (/app/packages/backend/dist/index.cjs.js:229:29)

I am trying to demo techdocs to my company but this has dragged me back for some days. I tried the external builder option with awsS3 but strangely enough, i'm stuck with a path problem.

@Umoren you'll need to setup your docker container with some production config that points to a postgres instance. Right now it's looking for postgres on localhost, and postgres isn't going to be running inside the container. You'll need to inject some environment variables into a container which would get used in the app-config.production.yaml to point at a running postgres instance somewhere.
Something like:
backend:
  database:
    client: pg
    connection:
      host: ${POSTGRES_HOST}
      port: ${POSTGRES_PORT}
      user: ${POSTGRES_USER}
      password: ${POSTGRES_PASSWORD}

Inside app-config.production.yaml and make sure that those env vars are set when running the container somewhere.

Where is your postgres running?
I like to use Docker Compose for devoping backstage with a postgres container next to it like this.
version: '3'
services:
  postgres:
    image: postgres:13.9-alpine
    container_name: postgresql
    environment:
      - POSTGRES_DB=backstage
      - POSTGRES_USER=backstage
      - POSTGRES_PASSWORD=backstage123
    ports:
      - 5432:5432
    volumes:
      - backstage_data:/var/lib/postgresql/data
      - /etc/localtime:/etc/localtime:ro
    restart: always
    network_mode: host
  backstage:
    image: registry.theflyingbirds.net/backstage:latest
    container_name: tfb_backstage
    ports:
      - 7007:7007
      - 3000:3000
    environment:
      - POSTGRES_HOST=<IP_ADDRESS>
      - POSTGRES_PORT=5432
      - POSTGRES_USER=backstage
      - POSTGRES_PASSWORD=backstage123
    network_mode: host
volumes:
  backstage_data:

If you can't use host network, then you would type "postgres" as the POSTGRESS_HOST for Backstage.
I also had problems connecting to my postgres in Docker if I had postgres running locally in Windows as a service.

Through trial and error I found that running a docker image without app-config.production.yaml in the build throws an error. But it does run with this minimal configuration.
bash-3.2$ cat app-config.production.yaml
backend:
  database:
    client: better-sqlite3
    connection: ':memory:'

I want to use a dockerised backstage in a local environment and hope the in-memory database will work ok 🤞

I can't believe I have to find this info here.  I followed the exact same steps and got an auth error first and then the database one.
I got it to work by doing the following before building the docker image:
node -p 'require("crypto").randomBytes(24).toString("base64")'
use that output ( say bla123bla) in the auth snippet ( root of file : ) :
Also comment out the database and replace with the above so the snippet becomes :
backend:
  database:
    client: better-sqlite3
    connection: ':memory:'
  auth:
    keys:
      - secret: 5o7UMI5xPDBxC5SgknGINtXirTkR8LUd
auth:
  providers:
    guest: null

Then build the container and start it.
I get errors then about the guest user, which given the config is not surprising.
I suggest adding the above with a working admin user config to the docs so one gets it to work and then hints to config for production being in a deployed or local setup.
I was just looking to run it as a local app.
If anyone can update the snippet to have an admin user, that would be great.


Make it so applying and removing patches are repeatable without errors

There are a number of issues with dealing with patches for the CUDF repo. This fixes some of them. It does not fix submodule update --init as that happens externally. It also does not fix other parts of upmerging a branch unless you have unapplied the patches before hand.  Sadly it also does not provide any good way to do development work on CUDF using the submodule as your development environment.
What this does do it make it so that if you apply patches to CUDF and try to build again without removing those patches it should work.

build

What's here looks OK.
What about the dangerous and surprising behavior of specifying submodule.patch.skip=true as discussed in #2497 (comment)? If this is an artifact of how the validate build works, maybe we should change the name of the property to something less "inviting" for developers to try, as this won't do what they think it does.

That is a good point. At a minimum I need to document it better. Thinking about it I am trying to understand the use case fro it. Originally I put it in as a way to skip the apply/unapply steps. But then I used it as a part of the CI process to auto upmerge CUDF, which made @gerashegalov want to lock it down so we don't accidentally build the plugin without the patches being installed. But I don't see that being the case any more.  Perhaps I can move it back to what it was originally intended to be and document it better to let people know that there is a foot/gun here no matter what it does.

build

build

@gerashegalov I added in the direct test, and you were also right that git apply is much cleaner than patch.  Please take another look


[Map Pack] RumpleMiniPack

A familiar bug happened to this map pack, that doubled displayed amount of content due to .zip files inside a .zip file.

URL: https://unrealarchive.org/mappacks/unreal-tournament-2004/vehicle-ctf/R/rumpleminipack_0b2e17c8.html
Hash: 0b2e17c8261aa7dfe13c444299b37a4ed4700156
Current name: RumpleMiniPack

Fixed


Upgrade Guava and remove duplicate

Describe your problem(s)
Need upgrade guava and remove duplicate guava jars in the pack

The following PRs will achieve the subject.

https://github.com/wso2/carbon-mediation/pull/1597
https://github.com/wso2/wso2-synapse/pull/1905
https://github.com/wso2/orbit/pull/593
https://github.com/wso2/carbon-apimgt/pull/11081
https://github.com/wso2/orbit/pull/604
https://github.com/wso2/carbon-business-messaging/pull/710
https://github.com/wso2/carbon-analytics-common/pull/787
https://github.com/wso2/carbon-event-processing/pull/322

Closing as all PRs are merged.


external mqtt credentials

What happened?
missing username password and clientid for external mqtt server
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
No response
Adapter version
2.7.4
Log
No response

Hi, the MQTT connection type was only an experiment and will not be developed further as the websocket connection is superior in this case.
Therefore, please switch to the websocket connection, as the MQTT connection type will be removed in the future.

I personally switched back to MQTT adapter because the websocket connection is not stable enough for my setup. MQTT works perfect. Bad to hear that you will not support it. Is there a chanse that someone else maintain the MQTT part of this adapter?

Hi @Eistee82, I decided to add the feature because some users seem to have problems with the websocket.
Can you please test the dev branch?
https://github.com/o0shojo0o/ioBroker.zigbee2mqtt/tree/external-mqtt-credentials-%23148

I no longer use this adapter. Im now using the MQTT Adapter with a script wich extends the Datapoints. So I can't test this for now.


Only supports default group

The group id appears to be hard coded to 1 in the sql file. It would be nice if group name or id could be supplied as a parameter to the install.

The 1 means that the domain is enabled, Pi-hole docs  has some information about the database. But it would be nice if we can use the Group management, I will think about how to implement it

I will think about how to implement it

@anudeepND I think I have this figured out. Will submit a P/R that accomplishes this soon.


TensorArray.stack should accept axis as argument

Describe the feature and the current behavior/state.
Currently there is:
TensorArray.stack(name=None) -> tf.Tensor

If we want to have stacking along a different axis, we must manually transpose using:
myTensorArray = tf.TensorArray(dtype=tf.float32, size=6, element_shape=(2, 3))
# [6, 2, 3]
res = myTensorArray.stack()
axis = 1
*perm, = range(len(res.shape))
perm[0], perm[axis] = perm[axis], perm[0]
# [2, 6, 3]
res_correct = tf.transpose(res, perm)

NOTE: I could have directly written out the perm parameter, but what if you're writing a library where you want to be able to stack along user-defined axis?
Will this change the current api? How?
New definition could directly do this:
TensorArray.stack(axis=0, name=None) -> tf.Tensor

Who will benefit with this feature?
Anyone who uses TensorArray.stack and doesn't want to stack on 0th dimension.
Any Other info.
Performance implication of stacking along non-0 axis should be considered and clearly explained in docs if significant.
EDIT: Other APIs in TensorArray should also be considered to be consistent. For example
TensorArray.concat(name=None) ->tf.Tensor
TensorArray.unstack(value, name=None) ->tf.Tensor

Related to: https://github.com/tensorflow/tensorflow/issues/8369

`def tf_array_stack(tf_array, axis=0):
stacked = tf_array.stack()
if axis!=0:
num = stacked.shape[0]
splits = [tf.squeeze(t) for t in tf.split(stacked, num)]
stacked = tf.stack(splits, axis=axis)
return stacked

`

Hi,
Thank you for opening this issue. Since this issue has been open for a long time, the code/debug information for this issue may not be relevant with the current state of the code base.
The Tensorflow team is constantly improving the framework by fixing bugs and adding new features. We suggest you try the latest TensorFlow version with the latest compatible hardware configuration which could potentially resolve the issue. If you are still facing the issue, please create a new GitHub issue with your latest findings, with all the debugging information which could help us investigate.
Please follow the release notes to stay up to date with the latest developments which are happening in the Tensorflow space.


How to handle uploads?

Is there any simple way to upload a File Object via vue-mc?

Doing some progress i achieve by creating a new method and overwriting all data to FormData
https://gist.github.com/stephandesouza/b7722252419f44b72bad86f6225945e6

I think we could probably create an upload method alongside fetch, save, and delete?

There's an upload method on master now, but not released yet. I'll come back to this issue to let you know when there is a stable release but will close for now.

Yea @rtheunissen getting a protocol error now, might override it by using a lot of the saveData saveHeaders, did you want a PR to fix this?


change gradlew permissions

:star: PR built and available in a preview environment dlish-spring-boot-http-gradle-pr-3 here


Changes in https://github.com/microsoft/kiota/pull/3921 result in incrrorect generation of inline anyof and array enum types.

Latests generation at https://dev.azure.com/microsoftgraph/Graph Developer Experiences/_build/results?buildId=130660&view=logs&j=0c914960-8b50-5299-c9aa-dd3c9595168e&t=97dbd468-8cc6-5acc-f2af-de93eaf8bad9 fails due to changes in https://github.com/microsoft/kiota/pull/3921
Referenced types of enum in an anyOf or array are incorrectly generated as inline types.
e.g. the reason property is generated as RejectPostRequestBody_reason.cs rather than a collection of micrososft.graph.rejectedReasons
requestBody:
        description: Action parameters
        content:
          application/json:
            schema:
              type: object
              properties:
                reason:
                  anyOf:
                    - $ref: '#/components/schemas/microsoft.graph.rejectReason'
                    - type: object
                      nullable: true
                callbackUri:
                  type: string
                  nullable: true
        required: true

Hi @andrueastman,
Thanks for reporting this.
Why would you expect the reason property to be a collection? It's not described as an array.
The fact that the type is getting inlined because of the change is concerning though.

Thanks for clearing this up @baywet. The issue does seem to be with inlining.
I made the mistake of thinking it had to do with collections due to other examples I was looking at that met the criteria such as
acceptedModalities here.
requestBody:
        description: Action parameters
        content:
          application/json:
            schema:
              type: object
              properties:
                callbackUri:
                  type: string
                mediaConfig:
                  $ref: '#/components/schemas/microsoft.graph.mediaConfig'
                acceptedModalities:
                  type: array
                  items:
                    anyOf:
                      - $ref: '#/components/schemas/microsoft.graph.modality'
                      - type: object
                        nullable: true
                participantCapacity:
                  maximum:<PHONE_NUMBER>
                  minimum: -2147483648
                  type: integer
                  format: int32
                  nullable: true
                callOptions:
                  anyOf:
                    - $ref: '#/components/schemas/microsoft.graph.incomingCallOptions'
                    - type: object
                      nullable: true


Fix Empty FileCollections Error

Applying both the kotlin android plugin and the android library plugin is a typical use case.
 It passes by replacing reduce with reduceOrNull + falling back to empty project.files() collection.

Although the general approach to automatically picking up sourceSets from other plugins needs some work.
afterEvaluate is unrecommended and introduces ordering issues, this plugin should instead be reacting to others being applied and not waiting until it thinks every other plugin is properly applied

@efemoney Feel free to fix! It would be much appreciated.
Ah yea, contributions are definitely welcome in that area as it was just something I figured I'd add for convenience real quick. Would love to remove usages of afterEvaluate.

@tylerbwong needed to run ktlintFormat. Should be good to merge now 👍🏾

@tylerbwong will there be a release soon? this is blocking us from updating for now

@efemoney I'll cut a release later today.

Thanks!


Auto swapping to testing build

Describe the bug
Every time I boot my Bazzite it shows I have an update becasuse is in the testing builds, I don't know why but every time I reboot it turns back to testing, it's so tedious...
What did you expect to happen?
Just stay to stable builds.
Output of rpm-ostree status
No response
Hardware
No response
Extra information or context
No response

Give the output of rpm-ostree status in the terminal in Desktop Mode and paste it here.


PermissionError: [Errno 13] Permission denied when trying to run a command

Somehow I run into "Permission denied" when trying to run any command from tui (running from cli is ok). I get the following trace:
$ python3 demo.py tui
Running demo.py add
Traceback (most recent call last):
  File "/home/user/util/demo.py", line 89, in <module>
    cli(obj={})
  File "/usr/lib/python3/dist-packages/click/core.py", line 1128, in __call__
    return self.main(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/core.py", line 1053, in main
    rv = self.invoke(ctx)
  File "/usr/lib/python3/dist-packages/click/core.py", line 1659, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/lib/python3/dist-packages/click/core.py", line 1395, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
    return __callback(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/decorators.py", line 26, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/home/lexxpluss/.local/lib/python3.10/site-packages/trogon/trogon.py", line 292, in wrapped_tui
    Trogon(app, app_name=name, click_context=ctx).run()
  File "/home/lexxpluss/.local/lib/python3.10/site-packages/trogon/trogon.py", line 260, in run
    os.execvp(program_name, arguments)
  File "/usr/lib/python3.10/os.py", line 574, in execvp
    _execvpe(file, args)
  File "/usr/lib/python3.10/os.py", line 615, in _execvpe
    raise saved_exc
  File "/usr/lib/python3.10/os.py", line 607, in _execvpe
    exec_func(fullname, *argrest)
PermissionError: [Errno 13] Permission denied

Any ideas would be helpful?

For ad-hoc scripts like this, make sure to check those 3 things:

The execute bit is set on the script file (e.g. with chmod +x demo.py)
The current directory is on your PATH env var (e.g. export PATH=$PATH:.)
The script's first line defines how it should be run (e.g. have #!/usr/bin/env python as a first line in the file)

All those allow you to run your script as demo.py add (the way Trogon wants to run it). Notice it doesn't run it as ./demo.py ... (where you don't need #2) nor python ./demo.py ... (where all of the above are not needed)

Thanks! Yes, running it as an executable Python script worked.


View Specifications Screen not working correctly

The View Specifications screen has some issues.  Use the example here: https://credreg.net/page/t3mapping#mapping as a guide for your understanding of how this screen should work.
First Issue: The screen never fully loads. Many of the tiles continue to display the flashing "dot" :

Second issue: For tiles that do load and show a percentage greater than zero mapped, no mappings are displayed on the right:

@excelsior - This is still an issue.
I logged on as joe+asn13.  When  Go to View Specifications > Organization, I still get the flashing dot that never fully loads (Issue 1 above).
When I look at the "Course" spine, The page loads, but the percentages don't seem correct.  For example, most of them show 100% even though only 1 organization has mapped to the spine.  Another example is the field "Address Apartment Room or Suite Number" which shows 90% even though the predicate is "Identical".


ERROR: Operation returned an invalid status 'OK'

Let me preface this with a statement that I am very inexperienced with Kubernetes, Docker, containers, etc.
I am running Windows 10.0.19043 Build 19043 with follow Az CLI and extensions.

I am trying to install the Application services extension (Preview) by generally following along this YouTube video:
https://youtu.be/17-EADOoJv0
Things seem fine until az k8s-extension create command.
It spins for several minutes and then ends with a misleading ERROR: Operation returned an invalid status 'OK' message.
OK means good to me.
Here is a screenshot of the command error:

Again, I may have absolutely gotten something wrong in my local Docker+Kubernetes+KIND configuration.
I was able to onboard my Kubernetes cluster into Azure Arc and even enable the Azure Defender for Kubernetes extension.
I'm not sure if I made a mistake or if there is a bug in this very new version of the extension.

Tried a few troubleshooting steps:
https://docs.microsoft.com/en-us/azure/azure-arc/kubernetes/troubleshooting

Thank you @ronhowe. Although this is not part of a Jumpstart scenario you are trying here, I was able to repro the issue on both the CAPI and AKS-based scenarios we have for Azure Arc-enabled app services.

I am looping @apwestgarth for visibility and insights.

Thanks for following up!

@ronhowe i followed up with the team. We have a Resource Provider (RP) that will be rolled out soon to fix the 'invalid status' error. The extension itself is working and installed, it's the API reporting-back that has the bug.

@ronhowe i followed up with the team. We have a Resource Provider (RP) fix that will be rolled out soon to fix the 'invalid status' error. The extension itself is working and installed, it's the API reporting-back that has the bug.

Thanks!
Is there an ETA on that so that I can try things after it has been deployed?

@ronhowe end of this week but let me update here and I can verify this in the Jumpstart automations

I may try tinkering again if I got confirmation of it being live.
I really appreciate the feedback.  I'm super new to Kubernetes, let along Azure Arc for Kubernetes.  I want to be sure I'm using good tooling so the only thing to blame for it not working is me!  :)

@ronhowe since i was able to repro, you are fine. allow me a few more days to validate.
Also, instead of doing this locally, I highly recommend using one of the Azure Arc-enabled app services Jumpstart scenarios here.

@ronhowe can you confirm this is still happening?

@ronhowe can you confirm this is still happening?

I've moved on from this project.  It will take me a bit of time to try again.  I'm interested in providing the feedback, but it will take me some time.  If I am not able to provide a response by end-of-week (2022-01-09), then assume I will be unable to provide additional feedback and you can resolve this issue or take other appropriate SDLC actions.

Thank you @ronhowe, I will go ahead and close this for now.


fix -Wsign-compare warnings

@jet47, please, fix the same warning at
modules/core/src/matrix.cpp:3493:75: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]

:+1:


add dockerfile

Adds a Dockerfile that I think that further reduces the hurdle for building and flashing code for the esp as it basically ships the whole the toolchain. It's basically a one liner to build and deploy software to an esp, no need to setup a toolchain etc.
docker run -v "$(pwd):/espflash" --device=/dev/ttyUSB0 -ti esp-rs/espflash --release --tool=cargo --chip=esp32 --example=esp32 --features="xtensa-lx-rt/lx6 xtensa-lx/lx6 esp32-hal" /dev/ttyUSB0

This assumes that the image has already been deployed to the docker hub (in this example I assume it's deployed to esp-rs/espflash. For manual building the image right now:
git clone --depth 1 https://github.com/esp-rs/espflash.git
cd espflash
docker build -t esp-rs/espflash .

Thanks!


Only change the default param

Сhange default param to currentWindow: false.
it is probably more convenient to use from the beginning.
Because without this parameter the script rarely reloads the page, only when I managed to switch very quickly to the browser window. This can be confused

Thank you! Hope this won't cause any problem... I'm currently not an active user of this tool, so I'm relying on your expertise here! :)

@dmitry-pogorelov @xpl currentWindow = false doesn't work for me. currentWindow = true works. Why ? I am new to chrome extensions, hoping a explanation

currentWindow: true is the way to go


Fix a debug info regression introduced with async support.

This patch removes a heuristic to promote all debug intrinsics pointing into
allocas to llvm.dbg.declare() intrinsics and instead more accurate classifies
variables in async contexts by adding the missing cases alloc_box and
alloc_stack cases.
rdar://78977132

Explanation: Fix a debug info regression that causes an LLVM assertion failure and incorrect debug info in optimized code.
Scope: Debug info / optimized code
Risk: change only affects debug info
Issue:  rdar://78977132

@swift-ci test

@swift-ci nominate

This was actually caught by the modified inlined-generics testcase, but I didn't pay enough attention to that at the time, not realizing what problem this would cause in the backend.


chore: refactor ef core tests

:tada: This PR is included in version 6.5.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Scroll up by tapping a status bar on iOS does NOT work after a hot restart with PrimaryScrollController

Steps to Reproduce

Execute flutter run on the code sample
Hot restart
Drag down and tap on the status bar to scroll up

Expected results:
Scroll to the top on tapping a status bar works after a hot restart
Actual results:
Scroll to the top on tapping a status bar does NOT work after a hot restart

Code sample

import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({super.key, required this.title});

  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: ListView.builder(
        controller: PrimaryScrollController.of(context),
        itemCount: 100,
        itemBuilder: (context, index) => ListTile(
          leading: Text(
            index.toString(),
          ),
        ),
      ),
    );
  }
}

Logs

[✓] Flutter (Channel stable, 3.0.2, on macOS 12.4 21F79 darwin-arm,
    locale en-US)
    • Flutter version 3.0.2 at /Users/heeyunlee/fvm/versions/3.0.2
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision cd41fdd495 (6 days ago), 2022-06-08 09:52:13
      -0700
    • Engine revision f15f824b57
    • Dart version 2.17.3
    • DevTools version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK
    version 32.1.0-rc1)
    • Android SDK at /Users/heeyunlee/Library/Android/sdk
    • Platform android-32, build-tools 32.1.0-rc1
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      11.0.11+0-b60-7772763)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google
      Chrome

[✓] Android Studio (version 2021.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      11.0.11+0-b60-7772763)

[✓] VS Code (version 1.68.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.42.0

[✓] Connected device (4 available)
    • Pixel 4a (mobile)      • 0A301JEC212254                       •
      android-arm64  • Android 12 (API 32)
    • iPhone 12 Pro (mobile) • FDBB3C7F-05A3-4DAB-8778-60D74534E5D6 •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-15-5
      (simulator)
    • macOS (desktop)        • macos                                •
      darwin-arm64   • macOS 12.4 21F79 darwin-arm
    • Chrome (web)           • chrome                               •
      web-javascript • Google Chrome 102.0.5005.115

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

https://user-images.githubusercontent.com/32585133/173683390-569ce104-dd9b-4dc0-a3ef-2405b1c53b0a.mov

Hi @heeyunlee, thanks for filing the issue.
This issue is reproducible on the latest stable and master channels with provided sample code.

Demo
https://user-images.githubusercontent.com/104349824/173791876-d304fc64-a584-48d5-ba9b-cc1b44c4fbc5.mp4

flutter doctor -v
[✓] Flutter (Channel stable, 3.0.2, on macOS 12.2.1 21D62 darwin-x64, locale en-VN)
    • Flutter version 3.0.2 at /Users/huynq/Documents/GitHub/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision cd41fdd495 (4 days ago), 2022-06-08 09:52:13 -0700
    • Engine revision f15f824b57
    • Dart version 2.17.3
    • DevTools version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-32, build-tools 31.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] Android Studio (version 4.1)
    • Android Studio at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/201.7042882/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] Android Studio
    • Android Studio at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-1/203.7185775/Android Studio Preview.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6842174)

[✓] IntelliJ IDEA Community Edition (version 2020.3.3)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] IntelliJ IDEA Community Edition (version 2022.1.1)
    • IntelliJ at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/IDEA-C/ch-0/221.5591.52/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.67.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.42.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-x64     • macOS 12.2.1 21D62 darwin-x64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 102.0.5005.115

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

[✓] Flutter (Channel master, 3.1.0-0.0.pre.1251, on macOS 12.2.1 21D62 darwin-x64, locale en-VN)
    • Flutter version 3.1.0-0.0.pre.1251 at /Users/huynq/Documents/GitHub/flutter_master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 0c0087f805 (2 hours ago), 2022-06-14 21:48:06 -0400
    • Engine revision f8c0dc87bc
    • Dart version 2.18.0 (build 2.18.0-189.0.dev)
    • DevTools version 2.14.0

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-32, build-tools 31.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] Android Studio (version 4.1)
    • Android Studio at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/201.7042882/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[!] Android Studio
    • Android Studio at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-1/203.7185775/Android Studio Preview.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

[✓] IntelliJ IDEA Community Edition (version 2020.3.3)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] IntelliJ IDEA Community Edition (version 2022.1.1)
    • IntelliJ at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/IDEA-C/ch-0/221.5591.52/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.68.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.42.0

[✓] Connected device (3 available)
    • SM T225 (mobile) • R9JT3004VRJ • android-arm64  • Android 11 (API 30)
    • macOS (desktop)  • macos       • darwin-x64     • macOS 12.2.1 21D62 darwin-x64
    • Chrome (web)     • chrome      • web-javascript • Google Chrome 102.0.5005.115

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

This issue may be a part of Proposal Refactor Scroll To Top iOS


Update README.md

Why do you want to remove this section? I don't see that info duplicated in Setting up


Third Level Sidebar

Description
example usage: https://docs-do3q8e9re-evidence.vercel.app/
https://github.com/user-attachments/assets/a8803e8b-6340-4cf7-a19b-4e9b36e97787
Outstanding questions

Sidebar links At the moment, it is possible to make the second level links clickable, or have them as unclickable use sidebar_link=false, but either way, due to an existing issue with breadcrumbs, those pages are generated anyway. Example in live docs - Should we fix this behaviour in this PR?
Collapsable? Should the second level headers be collapsable sidebar_collapsable=true Example MaterialUI

if so, should they be collapsable by default
should collapsable be open or closed by default sidebar_collapsable_initial=open, or should only the current page's section be expanded

Checklist

[x] For UI or styling changes, I have added a screenshot or gif showing before & after
[x] I have added a changeset
[x] I have added to the docs where applicable
[ ] I have added to the VS Code extension where applicable

Sidebar links At the moment, it is possible to make the second level links clickable, or have them as unclickable use sidebar_link=false, but either way, due to an existing issue with breadcrumbs, those pages are generated anyway. Example in live docs - Should we fix this behaviour in this PR?

No, that should be fixed in a separate PR.

Collapsable? Should the second level headers be collapsable sidebar_collapsable=true Example MaterialUI

In my opinion, yes they should be collapsible

if so, should they be collapsable by default

In my opinion, yes they should be collapsible by default
should collapsable be open or closed by default sidebar_collapsable_initial=open, or should only the current page's section be expanded
In my opinion, they should be open by default.
I view collapsing as a way to hide stuff you're not looking for in a busy sidebar. Have everything visible at the start, but allow the end user to temporarily hide things to make it easier to find what they're looking for

Okay various fixes and changes in here, see docs deploy for example
Done:

Slide transitions between active pages in the border: Note that these do not have a visible effect if you are navigating between pages where the load time > transition time. Try the deploy pages for some fast loading pages to see this effect
Removed bolding from second level headers
Hide pages with no children and sidebar_link=false
Add configuration option to EvidenceDefaultLayout to disable third level sidebar completely (backwards compat)

Not done:

Collapsable sections

Users have the flexibility to have all sidebar elements as links - which means side elements would have potentially two roles: nav to link / toggle accordion.
IMO there is not a great tradeoff that has a good UI for this. cf Docusaurus which is bad
We can add this in the future if it becomes a request


Questions about the Evaluations

StyleTTS's ref mel requires a single audio as input, which may result in the style vector only being similar to the ref wav, but somewhat different from other waves of the same speaker. May I ask if the ref mel you use for evaluations is gt or randomly selected from the dataset during your evaluation stage?

If you meant the samples in the "Zero-Shot Speaker Adaptation" section on the demo page here, it is randomly selected from the dataset (not included on the demo page because all samples are very similar to each other in the VCTK dataset). For more samples you can refer to the StyleTTS 2 demo page that includes samples generated by StyleTTS LibriTTS model and the reference audio: https://styletts2.github.io/


fix(marketplace-weights-info): fixed marketplace weights info

This change uses the weights from the pallet instead of the ones provided in parachain runtime configuration.
I think we should try to centralize the weights in the parachain runtime configuration.
I am also fine ignoring this improvement for now. Let me know what you think.


feat: add readthedocs-sphinx-search

Replace pydata theme's built-in search with search as you type
Note: for an unknown reason, the PR build doesn't actually have functional search. It can be previewed on this build of the branch itself which does work and is presumably reflective of how it will actually work when merged: https://dash-user-docs.readthedocs.io/projects/core/en/v19-rtd-sphinx-search
https://dash-docs--50.org.readthedocs.build/projects/core/en/50/

@rmdash @strophy Somewhat a proof-of-concept, but it seems to work. The visual appeal could definitely be improved by a CSS expert. Looking for feedback on actually using this search option and how much more should be done before merging.
Probably a fitting meme for this effort...

@rmdash @strophy Somewhat a proof-of-concept, but it seems to work. The visual appeal could definitely be improved by a CSS expert. Looking for feedback on actually using this search option and how much more should be done before merging.
Probably a fitting meme for this effort...

Ser, you get a cookie


Added Radix Sort in C# language

Have you read the Contributing Guidelines on Pull Requests?
Yes
Description
Added Radix sort in C# language.
Checklist

[*] I've read the contribution guidelines.
[*] I've checked the issue list before deciding what to submit.
[*] I've edited the README.md and link to my code.

Related Issues or Pull Requests
#2599

This same Code file has been pushed into a similar PR as well: https://github.com/TesseractCoding/NeoAlgo/pull/2707


Can we geocode transactions

We have millions of transactions, this won't be cheap, fast, and easy.

What if we used a paid geocode service like OpenCage to get through the backlog of historical transactions, and then switched to a free service (up to 75K hits a month) to keep up with quarterly transaction updates?
We'd need a scheduled service on our end to batch process transactions daily.

I see that Code for America Labs is organized as a 501(c3), so maybe the national organization could help us get an Esri non-profit license:. The non-profit license includes service credits that we could spend to access their online geocoder.

The Esri Nonprofit Organization Program (NPOP) is designed to provide qualified nonprofit organizations with an affordable way to acquire Esri solutions. All applicants undergo a review process upon submission of the NPOP application that considers formal tax-exempt status and the mission of the organization. In the United States, this is signified by your 501(c3) designation and National Taxonomy of Exempt Entities (NTEE) category. For international applicants, your organization’s eligibility and tax-exempt verification will be determined by your local Esri distributor as part of the application process.
NPOs generally considered for NPOP membership include noncommercial entities with humanitarian, conservation, and community services missions. Commercial, governmental, or organizations with a primary focus on economic development, as well as primary, secondary, or higher education institutions are not eligible for the NPOP. While educational service organizations with a specific conservation, humanitarian or community service mission may qualify, we strongly encourage universities and other higher education organizations to explore Esri’s GIS for Education programs.

Here is a roundup of geocoding services. It's circa 2017, but still a good starting point.
I need to know more about the addresses we need to geocode to understand which of these services would work best (cost, capabilities):

How many addresses do we already have?
How many do we add each quarter?
Are these residential addresses, commercial, or both?
Do we need precise latitude and longitude of the address?
Do we need to tie these addresses to legislative districts?

I'll try to answer (1) to (3) myself as soon as I get the dataset.

There are roughly 1M unique addresses for the accounts in transactions part of the data. Bring in the voter data and we are talking 13M+ for the 2020 snapshot.
Services are thus prohibitively expensive or frustratingly slow because free source limit to 1000-5000 records per batch.
We need to think of a local geocoder that can be run as part of the ingestion process like Degauss or Pelias.
other answers. We are not under CFA's 501c3 umbrella, besides using commercial sources like ESRI(particularly ESRI and MS) are discouraged in the larger community.

There is an import date that can be used as an indicator of new records. The dedupe/linkage process requires a complete purge and rebuild with the current methods used. But geocoding could be limited to an appropriate subset.
Both residental and commercial
4 & 5. We don't have specific requirements for geocoding, but deisgning with the most flexibility for possible uses is best. So lat/long/census divisions/legaslative districts(local, federal)

Where is local for us? Do we have cloud infrastructure for apps like Degauss or Pelias?

We need to think of a local geocoder that can be run as part of the ingestion process like Degauss or Pelias.

I guess it was fast easy and cheap/ Downloaded the degauss package and process about 1M account addresses with lat, long, and census block. Tweaking the parameters to get most matches.

The degauss docker container process 850K record in 30-40 minutes with a match rate of +95%.
Opening a new ticket to add a code block to the data import to process new records.