Rooter breaks Vim diff mode

When running Vim diff on files in subdirectories of a rooted directory, the second file is not opened correctly.
To reproduce, create the directory structure
dir
  '- subdir
      |- file1.txt
      '- file2.txt

When running vim -d file1.txt file2.txt from subdir, everything works as expected.
Now, create a .git directory in dir, to make this the root:
dir
  |- .git
  '- subdir
      |- file1.txt
      '- file2.txt

When running the same command again, the second window will be empty, and Vim says
"subdir\file2.txt" [New DIRECTORY]

It seems the second file is opened as dir/subdir/subdir/file2.txt instead of dir/subdir/file2.txt.
Running vim -d subdir\file1.txt subdir\file2.txt from dir works, but running from everywhere else, even with absolute file paths, won't work.

No, 3509dfb has the same problem.

Yes, this is on Windows, and I'm running on a clean profile, only plugin is vim-rooter.
It wouldn't be the first escaping problem I've run into on Windows ;-)
I haven't tried on Linux, but I can do that later.

Closing because it's gone quiet.

I‘m having the same issue (on Windows) and I confirm that it‘s specific for Windows as I can not reproduce it on Linux. I‘ll have a closer look...

@pseewald Thank you.

Just to illustrate what is wrong, let‘s assume we have two files in root/dir/file1 and root/dir/file2, with vim-rooter enabled:
As expected:
cd dir; vim file1
:pwd
root
:file
dir/file1

Wrong path when opening 2 windows:
cd dir; vim -o file1 file2
:pwd
root/dir
:file
dir/file1
1Ctrl-g (to show full path)
root/dir/file1
Ctrl-wj (to switch to file2)
1Ctrl-g (to show full path)
root/dir/dir/file2

I have no idea what‘s going on but it seems that changing the working directory at an early stage as vim-rooter does (after BufReadPost) conflicts with the vim mechanism of opening multiple windows (which seems to work differently on Windows than on other systems). I don‘t think it‘s an escaping problem.
Proposed solution: restrict the vim-rooter autocommand for changing the working directory to VimEnter (so dropping BufReadPost, BufEnter). Would that be possible?

Thanks for investigating.  I agree, it doesn't seem like an escaping problem.  It looks to me like a bug in vim.
Re your proposed solution, you can of course add and remove autocommands in your vimrc.  Personally I want vim-rooter to run every time I switch to a buffer because I often have files from different "roots" open and want vim to use the appropriate root when searching, navigating, etc.

Yes this is probably a bug in Vim for Windows and we should not try to fix this within vim-rooter.
However it‘s not possible to remove autocommands defined by plugins in vimrc (since plugins are loaded after vimrc). The workaround needs to be as follows (I leave this here just for documentation):
Create a file $HOME/vimfiles/after/plugin/rooter.vim with the content
augroup rooter
  autocmd!
  autocmd VimEnter * nested if !g:rooter_manual_only | Rooter | endif
  autocmd BufWritePost * nested if !g:rooter_manual_only | call setbufvar('%', 'rootDir', '') | Rooter | endif
augroup END

The reason I haven't looked into the problem further, is that I switched to using lcd, because it worked better with some of my other plugins.
That made the problem go away, so that's also a workaround, unless you depend on using cd.

@pseewald Or even simpler:
autocmd! rooter BufEnter,BufRead

@niboan That's good to know, thanks.  let g:rooter_cd_cmd = 'lcd'


[WIP]: introduce (non-scoped) RawMutex trait

No objections so far, other than maybe we should rename the crates

No objections so far, other than maybe we should rename the crates

yeah, mutex-traits would be fine w/ me, except that then IDK what we would call the main crate...tosc-mutex or something? idk.

lmao, we could choose violence and release the main impls crate as just mutex...

@jamesmunns I think the docs here are now good enough that I'm marking this as reviewable. I'd like to eventually add a guard-based API to BlockingMutex when the underlying mutex implementation can implement RawMutex, but I'll probably do that in a subsequent branch.
I should probably also write a better commit message but i'm lazy.

I should probably also write a better commit message but i'm lazy.

I don't mind defaulting to squash merges.
Could you also please fix the merge conflicts? I probably just caused them with merging #4


Special characters in api_password break streaming updates

Home Assistant release (hass --version): 0.21.2
Python release (python3 --version): Python 3.5.2rc1
Component/platform:
Description of problem: It looks like api_password isn't properly URL-encoded when it's passed in with the URL in GET requests. Logging in is possible, but streaming updates is disabled and it's impossible to re-enable.
Expected: I expect most character classes to work properly in passwords. I certainly expect some sort of validation. I wouldn't expect a given password to function properly with some aspects of the application, but break others.
Problem-relevant configuration.yaml entries and steps to reproduce:
homeassistant:
  name: Home
  latitude: -33
  longitude: 151
  temperature_unit: C
  time_zone: Australia/Sydney

frontend:

http:
  api_password: "abc+123"

Start home-assistant with this configuration.
Log in with the password "abc+123". Console logs the following
16-06-18 03:55:48 INFO (WSGI-server) [homeassistant.components.http] <IP_ADDRESS> - - [18/Jun/2016 03:55:48] "GET /api/bootstrap HTTP/1.1" 200 749 0.000350 16-06-18 03:55:48 INFO (WSGI-server) [homeassistant.components.http] <IP_ADDRESS> - - [18/Jun/2016 03:55:48] "GET /api/stream?api_password=*******&restrict=state_changed,component_loaded,service_registered HTTP/1.1" 401 475 0.000314
Upon login, Streaming updates is disabled. Attempting to enable streaming updates produces an error in the javascript console, but that seems to be an unrelated bug (I get the same result trying to toggle streaming updates whether api_password is enabled or not).

Traceback (if applicable):
The console doesn't log anything untoward, either during login or if the session is left running for a while.
Additional info:
I've only been able to reliably reproduce this with the & character. But I've seen problems with various combinations of $ and () and {}.

I can confirm this issue in 0.24.0. The log spams Login attempt or request with an invalidpassword as long as I have the browser tab with HA open. Also streaming updates are off whenever I refresh the page. Changing to password without special characters is workaround.

Same result when using !secret ? I used !env_var with a $ and I do not see this behavior.

I've now tested with the previous password containing special characters in secrets.yaml and !secret in main config, and can confirm the issue is still present. I.e. that is not a workaround.

Special characters seems to be removed by the werkzeug class Request(BaseRequest, AcceptMixin)
After parsing GET args here special characters show up as spaces in request.args. Special characters are still present in the environ input to self.Request()

I receive this error no matter what password I use.  Including "123456789" or "password"

I've also experienced this issue.  I'm on the latest 29.1 and the password included the equals sign "=" and the plus sign "+".  When I removed them the errors stopped.
I am still getting lots of "Login attempt or request with an invalid password from x.x.x.x" in the logs which I'm not sure is related or not.

any news here?
i have a easy password and have the errors in the log, too.
it is happened after installing samba, letscrypt and duckdns.

It should be fixed as of 0.30. If you're receiving the error without any special characters it's an unrelated bug that's presenting the same error messages.

hi, i have installed version 0.30.1. I try to understand you: can I assume that my error message is based on a another cause?

That's correct.

Ok I understand .. may I ask, what could cause this problem?

Can you create a new issue in github, and provide all of the relevant information? After you've created it you can post a link in this issue.

ok i will try

ok, i reconfigure the component Lets Encrypt again with the tutorial:
https://home-assistant.io/blog/2015/12/13/setup-encryption-using-lets-encrypt/
and to my suprize: I notice in HA log no more failed login attempts.
i cant reach my HA over local IP, but it doesnt matter, because i have now ssl over letsencrypt and no more errors.
thx guys, great and fast community here.

This appears to still be an issue on 0.36.1. When I was using a generated password with special characters (i.e. using LastPass or some other password manager), the streaming updates slider was off and in the browser console there were repeated 401 errors from the /stream URL in the network tab. It looked like the password was properly encoded in the URL parameter, but the API was returning the 401, so perhaps there is something on the server side that isn't properly decoding these?
I've got my setup working now when using a password without the special characters, but if more info is needed I can recreate the issue and report back.

Do you know if this was ever fixed for you? It might have been reintroduced in the switch to websockets. Can you create a new issue with the steps to reproduce and the relevant log entries? You can then link to it here.

I don't know if it was ever fixed from before as I just started using HASS on 0.36.1. I tried to recreate the issue today and couldn't get it to break, so I must have had something conflicting in my configuration.yaml from before. If I see the error again I will create a new issue for it.


Split display/window wrappers

WIP implementation of https://github.com/rust-windowing/softbuffer/issues/37. Currently compiles on Linux, and splits parts of Wayland code to not need duplication for multiple windows.
Seems best to start with this API change before moving on to https://github.com/rust-windowing/softbuffer/issues/40.

Context is expected to be created once per connection, which brings up how often Surfaces are expected to be created. Should it be created once per surface, kept around for the lifetime of that surface, and dropped only when the surface is dropped? Or would it be perfectly cheap to create and drop Surfaces, like so:
match event {
    Event::RedrawRequested => {
        let surface = Surface::new(&context, my_window);
        /* .. */
        drop(surface);
    }
}

If the latter, we should move some of the allocations out of Surface into the Context. In either case, this should be documented.

I'm assuming one would keep the Surface and continue using it. So an allocations that are specific to the surface would be there.

Maybe. Though taking a &Context could be a bit more inconvenient after https://github.com/rust-windowing/softbuffer/issues/40 since that will add more methods to Surface. And then you either have to pass it to all of them, or it's necessary to determine which methods might need something from the context (on some backends).
There could also be weird behavior if you passed a different context, though that probably isn't too much of an issue.
(Perhaps the ideal solution would be a lifetime bound on Surface if Rust had some kind of magical solution to make self-referential structs convenient, but that doesn't exist and makes lifetime bounds often awkward to deal with.)


gnomeExtensions.caffeine: 2020-03-13 -> 37

Motivation for this change
Upgrade gnome-shell-extension caffeine to latest release (from ~14 days ago), no longer requires getting the unstable branch.
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

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


revert retries in web and mobile command executors

in 7.3 we introduced retries for web and mobile command executors. it fixed temporary rare case when esg can't return response in time... at the same time set of complains raised that every retry for mobile and web takes up to 5-10m.
Especially case when driver exited due to the idleTimeout.
let remove retries and test original issue as some improvements delivered in ESG

done: https://github.com/zebrunner/carina/pull/1655

after additional testing retries removed on mobile and keep for the web. at the same time such updates for the web testing:

minimized number of attempts from 10 to 2
don't retry for driver quit operation

confirmed by customers using snapshot build


nixos/kubernetes: add metrics port to dns addon service

Motivation for this change
this is needed so the metrics can be consumed by the prometheus operator
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

IMO this is still needed, the same fix was done 5 years ago in https://github.com/kubernetes/kubernetes/pull/73302.
@Preisschild would you mind rebasing?


Two page layout for tablets

It would be nice to have a two page layout options for landscape orientation on tablets:

This is pretty interesting, but I have no idea how to accomplish this, as we are already using the webView pagination.
Need to look deeper on that.

Also, it's worth pointing out that there are two very different cases in EPUB:

if the publication is a Fixed Layout EPUB, you'll actually display two different resources (probably using two different webviews) and will have to look into the way EPUB handles spreads (left/right page, orientation, double pages)
for a reflowable EPUB, this is indeed tied to how you actually paginate the content in a single webview

Yes, it would be very nice to implement it like what iBook does.


DOMAIN error when running final spec in Behaviors page

When I try to execute the spec at the bottom of the Behaviors page, I get an error. Here's the spec:
---- MODULE flags ----
EXTENDS TLC, Integers
(* --algorithm flags
variables flags = [1..3 -> BOOLEAN], next = TRUE;
begin
  while next do
    with f \in DOMAIN flags, n \in BOOLEAN do
      flags[f] := ~flags[f];
      next := n;
    end with;
  end while;
end algorithm; *)

====

and here's the error I got after running the model checker:
TLC threw an unexpected exception.
This was probably caused by an error in the spec or model.
See the User Output or TLC Console for clues to what happened.
The exception was a java.lang.RuntimeException
: Attempted to apply the operator DOMAIN to a non-function
(a set of the form [S -> T])

When I evaluate [1..3 -> BOOLEAN], its value is
{ <<FALSE, FALSE, FALSE>>,
     <<FALSE, FALSE, TRUE>>,
     <<FALSE, TRUE, FALSE>>,
     <<FALSE, TRUE, TRUE>>,
     <<TRUE, FALSE, FALSE>>,
     <<TRUE, FALSE, TRUE>>,
     <<TRUE, TRUE, FALSE>>,
     <<TRUE, TRUE, TRUE>> }

So I see that flags a set, not a function, which explains the error "Attempted to apply the operator DOMAIN to a non-function". I'm not sure what's the proper way to make flags a function for the three boolean flags.

Yeah my mistake, it's supposed to be flags \in, not flag =. I'll push the
change as soon as I'm off the train.
On Wed, May 17, 2017, 12:11 AM Daniel Mai<EMAIL_ADDRESS>wrote:

When I try to execute the spec at the bottom of the Behaviors
https://learntla.com/pluscal/behaviors/ page, I get an error. Here's
the spec:
---- MODULE flags ----
EXTENDS TLC, Integers
(* --algorithm flags
variables flags = [1..3 -> BOOLEAN], next = TRUE;
begin
while next do
with f \in DOMAIN flags, n \in BOOLEAN do
flags[f] := ~flags[f];
next := n;
end with;
end while;
end algorithm; *)
====
and here's the error I got after running the model checker:
TLC threw an unexpected exception.
This was probably caused by an error in the spec or model.
See the User Output or TLC Console for clues to what happened.
The exception was a java.lang.RuntimeException
: Attempted to apply the operator DOMAIN to a non-function
(a set of the form [S -> T])
When I evaluate [1..3 -> BOOLEAN], its value is
{ <<FALSE, FALSE, FALSE>>,
<<FALSE, FALSE, TRUE>>,
<<FALSE, TRUE, FALSE>>,
<<FALSE, TRUE, TRUE>>,
<<TRUE, FALSE, FALSE>>,
<<TRUE, FALSE, TRUE>>,
<<TRUE, TRUE, FALSE>>,
<<TRUE, TRUE, TRUE>> }
So I see that flags a set, not a function, which explains the error
"Attempted to apply the operator DOMAIN to a non-function". I'm not sure
what's the proper way to make flags a function for the three boolean
flags.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hwayne/learntla/issues/3, or mute the thread
https://github.com/notifications/unsubscribe-auth/ACiXdHHOnHAb4m_ZshvvalBoR1LAbSeHks5r6oFugaJpZM4NdYeV
.

Fixed in https://github.com/hwayne/learntla/commit/ef57679280ca8e50fa126eb38411bfcd256500e1!


判斷家己的函式整理理咧

Coverage increased (+0.4%) to 97.313% when pulling 6b7fbaab570459085ccee4f573d67d6a2c263d05 on 整理程式 into c2320dc7f52920dff86cebe3090f5388d9358099 on master.

Coverage increased (+0.4%) to 97.313% when pulling c1352fa303a6d7a3f6f73d982985f849824da488 on 整理程式 into 0c830ab034ccb319678ce218b1db33fcf68f2f31 on master.


EF 7: Bulk Updates are now supported but docs say otherwise.

"Unfortunately, EF doesn't currently provide APIs for performing bulk updates. Until these are introduced, you can use raw SQL to perform the operation where performance is sensitive:"
This has been implemeented though in EF7.0.
The documentation mentions is here: Basic ExecuteUpdate examples
https://learn.microsoft.com/en-us/ef/core/what-is-new/ef-core-7.0/whatsnew

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

ID: f37e820a-137f-92c9-6662-06fafeac097a
Version Independent ID: 0df73aed-692f-0e53-7562-ed3d8b89c6df
Content: Efficient Updating - EF Core
Content Source: entity-framework/core/performance/efficient-updating.md
Product: entity-framework
Technology: entity-framework-core
GitHub Login: @roji
Microsoft Alias: avickers

Duplicate of #4032

Closing as it's been reported already.


⚠ Bofrost.at has degraded performance

In 870f638, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1580 ms

Resolved: Bofrost.at performance has improved in 0123c01 after 6 minutes.


[AutoPR netapp/resource-manager] Get removal and status code additions

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/4890

(message created by the CI based on PR content)


[BUG] Add-PnPContentTypesFromContentTypeHub -ContentTypes missing column

Reporting an Issue or Missing Feature
In some cases when creating a team and when using Add-PnPContentTypesFromContentTypeHub -ContentTypes to add an contenttype to the sharepoint site->list. One of the columns of the contenttype is missing
Expected behavior
In most of the cases the contenttype from the hub has all the columns.
Actual behavior
One of the columns is missing.
Steps to reproduce behavior
Add-PnPContentTypesFromContentTypeHub -ContentTypes "0x01006E4EB9BA6BA49944B4D15C7BC50B646D"
What is the version of the Cmdlet module you are running?
Running 2.1.1
Which operating system/environment are you running PnP PowerShell on?

[ ] Windows
[ ] Linux
[X ] MacOS
[ ] Azure Cloud Shell
[ X] Azure Functions

hi @Wernbe , looking at your workaround, the problem seems to be coming from the server side and not the cmdlet itself. Would recommend reaching out to Microsoft support for help, we can't do much here, so will move it to discussions.
You can ask them to look at the cmdlet code here:
https://github.com/pnp/powershell/blob/dev/src/Commands/ContentTypes/AddContentTypesFromContentTypeHub.cs


Discrepancies Between Production/Staging Webpack?

There are a few issues with the production and staging versions of webpack.

The favicon appears on staging, not on production
The AbeLincoln font is not imported correctly on production
Content/text is not pulled from the project resource on production

Note the differences between localhost and production:

Production's project description is blank. (Everything after "Welcome to Anti-Slavery Manuscripts")
The font of the main h1 element is very, very different. Everything else seems OK, strangely.

I noticed that if you compare the computed css between the two, the production environment is not receiving the AbrahamLincoln font, which makes me thing there is an issue with the import grabbing info from the fonts folder.

What is this. What is this madness.
Both localhost and production pull AbrahamLincoln.woff properly, but the file that production receives is the default FontAwesome web font. What.

OH SNAP
The server! Maybe the server doesn't serve .woff files? I know it serves .ico files, but perhaps there was some side effect of issue #76 's site config that doesn't identify .woff files as safe to serve, or something.
Compare these two files:

https://www.antislaverymanuscripts.org/favicon.ico
https://www.antislaverymanuscripts.org/AbrahamLincoln.woff

Perhaps this has to do with https://github.com/zooniverse/static/blob/master/sites/www.antislaverymanuscripts.org.conf#L12 ?


Correct Handling of varuint1 Encoding in Wasm Parser

A contract developer has triggered a bug in the in-house parity WebAssembly (Wasm) parser during a deployment, causing the parser to fail with the error: “Wasm preprocessing error: Deserialization error: Invalid table reference (128).” The issue arises from an incorrect handling of the call_indirect opcode in the WebAssembly (Wasm) parser, specifically related to the misinterpretation of a varuint1 field.
The current parser incorrectly parses a field in the call_indirect opcode as an unsigned 8-bit integer (u8) instead of the correct varuint1 format, which is LEB128 encoded. This leads to errors when the field value exceeds the expected range, as seen with a specific deployment where the value was 128 (0x80 in hexadecimal).
Info from Michał:
"It seems there’s a contract developer that somehow managed to trigger a bug in the in-house parity wasm parser with this deploy: https://devnet.make.services/deploys/194988146d2e9beea5a0ad16245dbb15fa34d2ad5837f27192cbb280c38761a3
This wasm triggers parser error “Wasm preprocessing error: Deserialization error: Invalid table reference (128)”
I investigated it with Rafal from CL and it seems the parser in casper-wasm is buggy. According to the spec call_indirect opcode is encoded with a varuint32 field and a varuint1 field (ref: https://github.com/WebAssembly/design/blob/main/Semantics.md#calls). Now, it seems stefan.wasm the value in the call_indirect opcode inside wasm is 128 (in decimal); and the wasm parser parses this incorrectly as u8.
From what I understand varuint1 is leb128 encoded and 128 in dec is 0x80. And 0x80 decoded in leb128 form gioves 0. For whatever reasons all the wasms had literal 0 (all bits 0) encoded, but this one is 128 (0 encoded in leb128 form)
This is the location in the parser where this reserved field is parsed as u8, not varuint1: https://github.com/casper-network/casper-wasm/blob/a38e184578a06210652df6f6d26f6a56303611f7/src/elements/ops.rs#L1088-L1096. There’s Varuint1 type in the code, but I think it’s incorrect - it parses incoming byte as u8, but doesn’t parse it as leb128"

This behavior is related to changes in rust toolchain. It was introduced in the nightly channel between 2024-08-01 and 2024-08-02: https://github.com/rust-lang/rust/compare/f8060d282...28a58f2fa
There doesn't seem to be any WASM-specific code there, so the most likely culprit seems to be the LLVM update from 18 to 19.

In the current version of the parser call_indirect instruction is represented as CallIndirect(signature, table_ref), where the first argument is a reference to a pre-defined function type and the second argument is a reference to a table containing the function to be called.
During parsing it is assumed that the second argument is always equal to 0. This is probably because in the initial WebAssembly MVP a default table was used and actual implementation of this feature was meant to be done in the future.
The second argument is also discarded when processing this instruction in casper-wasmi and instead a constant is used as table index.

Using non-default table references seems to be a part of reference-types proposal: https://github.com/WebAssembly/reference-types
This proposal has also been enabled for wasm32-unknown-unknown target for some time now: https://github.com/rust-lang/rust/blob/master/src/doc/rustc/src/platform-support/wasm32-unknown-unknown.md
It's possible that it did not have an effect until LLVM was updated.

To properly handle current variant of call_indirect we'd have to implement support for reference-types.
This feature in turn depends at least in some part on existing support (at least in the parser) for bulk-memory-operations feature.
Both of those feature have been a part of official WebAssembly spec since early 2021: https://github.com/WebAssembly/spec/commit/7fa2f20a6df4cf1c114582c8cb60f5bfcdbf1be1
'reference_typesis also enabled by default inwasm32-unknown-unknown` Rust target: https://github.com/rust-lang/rust/blob/f734f3d8e73f2118fdf4bdaf35e72ace8a442531/src/doc/rustc/src/platform-support/wasm32-unknown-unknown.md#enabled-webassembly-features
At this point in time Casper team is fine with casper-wasmi targeting the MVP WebAssembly spec and asking people to compile their contracts using a pinned nightly version (2024-08-01) and it was decided that implementing those features would be too time-consuming.
If we decide to follow through with the implementation at some point in the future we'd probably have to refactor our parser to also support bulk-memory-operations in order to update the WebAssembly spec repository used for testing. Currently casper-wasm is using a version from 2019 and casper-wasmi from 2020.
A way to sidestep this issue would be to use a revision from a point in time before those proposals were merged into the official spec and the tests still lived in the proposals directory.


Missing support for SET and CREATE DOMAIN

I've tried the instructions in the README doc using the SportsDB but got this error.
Steps to reproduce the error.
Prepare sample DB.
$ unzip sportsdb_sample_postgresql.zip
$ sudo -u postgres createdb sportsdb_sample
$ sudo -u postgres psql -d sportsdb_sample -f sportsdb_sample_postgresql_20080304.sql

Dump schema.
$ pg_dump --schema-only --no-owner postgres://dbuser:dbpass@localhost/sportsdb_sample > sportsdb_sample.schema.sql

Create migration files.
$ mix ecto.extract.migrations --sql-file sportsdb_sample.schema.sql
Compiling 31 files (.ex)
Generated ecto_extract_migrations app
UNKNOWN 8> SET statement_timeout = 0;
UNKNOWN 9> SET lock_timeout = 0;
UNKNOWN 10> SET idle_in_transaction_session_timeout = 0;
UNKNOWN 11> SET client_encoding = 'UTF8';
UNKNOWN 12> SET standard_conforming_strings = on;
UNKNOWN 13> SELECT pg_catalog.set_config('search_path', '', false);
UNKNOWN 14> SET check_function_bodies = false;
UNKNOWN 15> SET xmloption = content;
UNKNOWN 16> SET client_min_messages = warning;
UNKNOWN 17> SET row_security = off;
UNKNOWN 23> CREATE DOMAIN public.primary_id AS integer;
UNKNOWN 26> SET default_tablespace = '';
UNKNOWN 28> SET default_with_oids = false;
** (Protocol.UndefinedError) protocol Enumerable not implemented for nil of type Atom
    (elixir 1.10.3) lib/enum.ex:1: Enumerable.impl_for!/1
    (elixir 1.10.3) lib/enum.ex:141: Enumerable.reduce/3
    (elixir 1.10.3) lib/enum.ex:3383: Enum.reduce/3
    lib/mix/tasks/ecto_extract_migrations.ex:67: Mix.Tasks.Ecto.Extract.Migrations.run/1
    (mix 1.10.3) lib/mix/task.ex:330: Mix.Task.run_task/3
    (mix 1.10.3) lib/mix/cli.ex:82: Mix.CLI.run_task/2

The error in this case is not from lacking support for SET or CREATE DOMAIN, it was that the code expected schema object types (e.g. custom schemas) to exist which are not used by that db. I added default values and made a new release, and the code now generates migrations for sportsdb. The resulting migrations have an error because the tables don't actually define a primary key, they just have an integer not null field, e.g.
CREATE TABLE public.locations (
    id integer NOT NULL,
    timezone character varying(100),
    latitude character varying(100),
    longitude character varying(100),
    country_code character varying(100)
);

results in ```
defmodule(Sports.Repo.Migrations.Table.Public.Locations) do
use(Ecto.Migration)
def(change) do
create(table("locations", primary_key: false)) do
add(:id, :integer, null: false)
add(:timezone, :"character varying", size: 100)
add(:latitude, :"character varying", size: 100)
add(:longitude, :"character varying", size: 100)
add(:country_code, :"character varying", size: 100)
end
end
end

which gives an error:

```09:25:01.637 [info]  execute "  ALTER TABLE ONLY public.addresses\n  ADD CONSTRAINT fk_add_loc_id__loc_id FOREIGN KEY (location_id) REFERENCES public.locations(id);\n\n"

09:25:01.645 [debug] QUERY ERROR db=7.9ms
  ALTER TABLE ONLY public.addresses
  ADD CONSTRAINT fk_add_loc_id__loc_id FOREIGN KEY (location_id) REFERENCES public.locations(id);

 []
** (Postgrex.Error) ERROR 42830 (invalid_foreign_key) there is no unique constraint matching given keys for referenced table "locations"```

It could be ```
defmodule(Sports.Repo.Migrations.Table.Public.Locations) do
  use(Ecto.Migration)
  def(change) do
    create(table("locations")) do
      add(:timezone, :"character varying", size: 100)
      add(:latitude, :"character varying", size: 100)
      add(:longitude, :"character varying", size: 100)
      add(:country_code, :"character varying", size: 100)
    end
  end
end

but of course that's different from the source schema.
Probably there should be an option to disable generating the foreign key constraints in this case.
It likely makes sense to add support for CREATE DOMAIN as a pass-through SQL. SET is also possible, but most SET statements seem to be defaults, and it probably makes sense to just manually add migrations for them if needed.

The error in this case is not from lacking support for SET or CREATE DOMAIN, it was that the code expected schema object types (e.g. custom schemas) to exist which are not used by that db. I added default values and made a new release, and the code now generates migrations for sportsdb. The resulting migrations have an error because the tables don't actually define a primary key, they just have an integer not null field, e.g.

Is the fixes merged to master branch?

Yes, they are merged


Question: Guidance on switch between server side and client side

Was wondering if anyone could point me to docs and/or discussion regarding how best to setup a blazor project to more readily switch between server-side to client-side. For example in client side every call to the server might need to use HttpClient while on the server-side one could make direct calls to a class or EF to get data. I guess some form of data abstraction with a switch of some kind when client or server is detected? Any nudge in the right direction would be greatly appreciated. Thanks!

Quite related to: https://github.com/aspnet/Blazor.Docs/issues/301

https://github.com/Suchiman/BlazorDualMode

services.AddServerSideBlazor<Client.Startup>() doesn't seems to work


Since symfony/console 6.1: Relying on the static property "$defaultName" for setting a command name is deprecated

Bug Report
the property defaultName on symfony 6.1 or mayor is deprecated

Q
A

BC Break
NO

Version
6.2  and 6.3

Summary
[info] User Deprecated: Since symfony/console 6.1: Relying on the static property "$defaultName" for setting a command name is deprecated. Add the "Symfony\Component\Console\Attribute\AsCommand" attribute to the "Oneup\UploaderBundle\Command\ClearOrphansCommand" class instead.
How to reproduce

Good day all,
I did some work on getting the repo a bit more php8 styled.
Also got rid of some of the deprecation messages.
As mentioned in the PR, we will need to bump this to a new major package version, as this will drop support for php7.
Pull Request: #435

@joesenova your changes are merged in #436 - thank you very much! 🙏


Add basic element check to DOMEventDelegate

fixes #140

Verified that @j3tan has signed the CLA. Thanks for the pull request!


v1.0.8

fixes for latest jam ui changes. added 'search receivables' functionality.

Thank you for the quick updates.  I never realized the useful links injected by the extension.

Thanks!  Let me know if you notice anything wrong.

You bet!


Fix sort command by introducing Contact Index

TODOs (This PR is not ready for review)

[x] Find out what sort actually does
[x] Give index attribute to people
[x] Add index into eduMate.json

{
    "name" : "Bart Lee",
    "phone" : "93288896",
    "email"<EMAIL_ADDRESS>    "address" : "90 Bartley Road",
    "telegramHandle" : "@bartlee",
    "index" : 57,
    "groups" : [ "CCA", "Bartley" ],
    "modules" : [ "BT3102", "BT1101", "CS3240", "CE2134", "CE2112", "CE1102" ]
  },

[x] JsonAdaptedPerson update all their information
[ ] Add relevant test cases for JsonAdaptedPerson and relevant stuff
[x] editCommand will now be based on ContactIndex, not Index
[x] viewCommand will be based on ContactIndex, not Index
[X] sort with reset index capability
Available via sort index
[ ] Index Assigner when you add a command
[ ] Handle contact index not found!
[ ] User Guide (so teammates will be notified of changes)

Sort Command Implementation PR

Testing will be deferred to a separate PR. Please note!


[BUG] Referral system function parameters

Describe the bug
Go to admincp active the referral syste, and try invite players use this.
You have an issue on :
model.account.php
        public function check_if_reward_was_claimed($curUser, $id, $server, $account){             $stmt = $this->website->db('web')->prepare('SELECT TOP 1 id FROM DmN_Refferal_Claimed_Rewards WHERE reward_id = :id AND account = :account AND server = :server AND ref_account = :ref_account');             $stmt->execute([':id' => $id, ':account' => $curUser, ':server' => $server, ':ref_account' => $account]);             return $stmt->fetch();         }
This function have 4 parameters, but on the theme you write only 3 then this cause issue for use the system
On theme file:
if($this->Maccount->check_claimed_referral_rewards($value['id'], $char['Name'], $value['server']) != false)
You can fix this ! :)

@pulseP1986 When you make new release ?
If need help for the system I avaible also :)

if($this->Maccount->check_claimed_referral_rewards($this->session->userdata(['user' => 'username']), $value['id'], $char['Name'], $value['server']) != false) fix in your template if you need


Bug fix: Allow paused VM to migrate

What this PR does / why we need it:
Allow paused VM to migrate. This is currently possible only through VMIM API.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:
Bug fix: API and virtctl invoked migration is not rejected when the VM is paused

/cc @vladikr

Removed the functional test.
@kbidarkar fyi

/approve
Thanks!

/retest-required


SliverReorderableList itemcount

Description
Tests and API docs.

Oh yikes, this is because I used a branch that was merged from master. Let me see if I can create a branch off of your current branch

Oh yikes, this is because I used a branch that was merged from master. Let me see if I can create a branch off of your current branch


[serde-generate] More improvements in C# codegen

Summary

Consistently use lowercase autogenerated field names "value" and "fieldX" to avoid breaking compilation in case of a collision with a class name (e.g. variant Value). This is also more likely to match the rest of the generated code since serde-reflection extracts lowercase field names from Rust. (@mattico We could also add an option to enforce uppercase public fields everywhere, if needed in the future.)
Change .csproj file again to remove some warnings on my laptop.
Support generation of C# files outside of the Serde project

Test Plan
CI

Moved to new PR https://github.com/novifinancial/serde-reflection/pull/81


storyview package having issue with stories test navigation on tap

Steps to reproduce

Download this file: https://github.com/blackmann/story_view/blob/master/example/example.dart
Write test cases for changing the stories on tap using offset values
Run the test

Actual results
It's giving error that pumpAndSettle timed out but it should switch to next story
Logs

Logs
java.lang.Exception: ══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞═════════════════
The following assertion was thrown running a test:
pumpAndSettle timed out

When the exception was thrown, this was the stack:
#0      WidgetTester.pumpAndSettle.<anonymous closure> (package:flutter_test/src/widget_tester.dart:677:11)
<asynchronous suspension>
#1      TestAsyncUtils.guard.<anonymous closure> (package:flutter_test/src/test_async_utils.dart:117:7)
<asynchronous suspension>

The test description was:
Dashboard
═════════════════════════════════════════════════════════════════

at pl.leancode.patrol.PatrolTestRunner.run(PatrolTestRunner.kt:76)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
at androidx.test.internal.runner.TestExecutor.execute(TestExecutor.java:67)
at androidx.test.internal.runner.TestExecutor.execute(TestExecutor.java:58)
at androidx.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:446)
at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:2367)

Patrol version
patrol: ^1.1.4
Patrol Doctor output

Patrol Doctor output
Program adb found in /Users/ashusharma/Library/Android/sdk/platform-tools/adb
Env var $ANDROID_HOME set to /Users/ashusharma/Library/Android/sdk/
Program xcodebuild found in /usr/bin/xcodebuild
Program ideviceinstaller found in /opt/homebrew/bin/ideviceinstaller
Program ios-deploy found in /opt/homebrew/bin/ios-deploy

Flutter Doctor output

Flutter Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.7.12, on macOS 13.4 22F66 darwin-arm64, locale
    en-IN)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.3)
[✓] VS Code (version 1.78.0)
[✓] Connected device (3 available)
[✓] HTTP Host Availability

• No issues found!

This issue is not reproducible. Please read & understand the issue template.

Write test cases for changing the stories on tap using offset values

Please provide such a test.


SyntaxError: Unexpected token '??=' in @redis/client

Description
Issue description:
While running my Next.js application, I encountered a syntax error originating from the @redis/client module.
Error Details:
File<EMAIL_ADDRESS>Line: 195
Error: this[name.toLowerCase()] ??= this[name];
        ^^^
       SyntaxError: Unexpected token '??='

Stack Trace:
- at wrapSafe (internal/modules/cjs/loader.js:1029:16)
- at Module._compile (internal/modules/cjs/loader.js:1078:27)
- at Object.Module._extensions..js (internal/modules/cjs/loader.js:1143:10)
- at Module.load (internal/modules/cjs/loader.js:979:32)
- at Function.Module._load (internal/modules/cjs/loader.js:819:12)
- at Module.require (internal/modules/cjs/loader.js:1003:19)
- at require (internal/modules/cjs/helpers.js:107:18)
- at Object.<anonymous> (/var/app/current/node_modules/@redis/client/dist/index.js:18:18)
- at Module._compile (internal/modules/cjs/loader.js:1114:14)
- at Object.Module._extensions..js (internal/modules/cjs/loader.js:1143:10)

Additional Information:
npm ERR! code ELIFECYCLE

Environment Details:

Node.js version: Node.js 14 running on 64bit Amazon Linux 2/5.8.5
Next.js version:  "next": "^10.0.4",

Node.js Version
14
Redis Server Version
No response
Node Redis Version
No response
Platform
Linux
Logs
No response

You should use node v15 or higher. The last version<EMAIL_ADDRESS>has some breaking changes for the node v14. Also node v14 is deprecated and I suggest you to use v16 or v18 which is LTS for now. Or you can fix your redis to 4.6.0 as a temporary solution.

while i agree that we should all be updating our EOL node versions, patch versions should not introduce breaking changes. i would call dropping support for older node versions a breaking change.

This is a breaking change and should be rolled back.

Can you guys please do a major release if you are updating something that'll break people's working stuff? All morning our builds are failing and while I do agree people should keep their stuff up to date and you do that too, which is great but make major update so it doesnt screw up 100,000 applications that are using this and running fine...

Ya same is happing with us...is there any update on this issue


docs(sdk): Updates the Tables reference docs.

Description

Fixes DOCS-803

What does the PR do?

Removes lengthy text context from heading of tables page (moved to guides)
Improves language of docstrings
Elaborates on confusing docstrings
Standardizes formating

Testing
How was this PR tested?

This seems to brake a relevant test: https://app.circleci.com/pipelines/github/wandb/wandb/30176/workflows/9b224529-b2b2-4b71-a0d1-e559b94e8fba/jobs/971883?invite=true#step-105-42
could you please fix and request a review from a relevant dev?


Packaging up libpostal

Issue description
I'm trying to package up https://github.com/openvenues/libpostal, which uses curl during its make, to download an external file.
Does this mean when we turn this into a Nix expression, we can either A: put the external file as a nix dependency and change the libpostal expression to rely on that external file expression, or B: bring that external file with an extra fetchUrl call within the same libpostal expression?

Yes, an in both cases you get the file with fetchurl and put it where make expects it so it doesn't need to be refetched. I guess you could find yet another way to structure this; I think for a single single-use fetch it is more typical to put the fetchurl invocation in the same .nix file.

Note that data files generated are meant to be able to be updated: https://github.com/openvenues/libpostal#data-files
Does that mean the build expression needs to put these files in a temporary location? How would one do this? Do we always expect that there's a mutable home directory with relevant data files? Or do we just fix them just like the built source code?

I think the ideal case would be to build most of the code, then provide a wrapper that uses prebuilt code and a fixed predownloaded dataset to provide the functionality. If libpostal builds quickly, maybe just fixing the dataset and rebuilding every time is also fine.

https://github.com/openvenues/libpostal/issues/341

@7c6f434c Can you let me know whether pkgconfig will be needed in nativeBuildInputs for this particular package? It seems that only downstream packages would make use of it. The building of libpostal itself doesn't require pkgconfig.

What is the output of fetchurl in this case? If I were to use it on the data files? Here is where they use to specify the data download: https://github.com/openvenues/libpostal/blob/master/src/libpostal_data
Note that the only output binary that libpostal creates is libpostal_data which is used to update or download new data files. In this case, I feel like this means that the data files should be a mutable location. But other then $HOME, where else can mutable data files exist on NixOS?
Alternatively, should then libpostal_data just be removed from $out/bin?

At what moment is data location fixed? I guess if a user can use libpostal_data to download data to some place and tell libpostal to use this place, then the tool can stay.
No idea about pkgconfig being neccessary or not; but if there are no problems without it, then indeed it is not needed as an input.

In theory the location is configurable at both build time and runtime. libpostal_setup_datadir will use the path configured as datadir if passed NULL and otherwise use whatever string is passed.
But in practice it seems it's really the build-time path that matters, there's a method libpostal_setup that calls libpostal_setup_data(NULL) and this is the method used by e.g. the Python bindings.
The libpostal data files aren't really mutable though; there's only one recent released version and the code opens them read-only. I'd package the data files as a fixed-output derivation that runs the downloader script. Then the data dir can be configured as that output path.

Ok in that case I'll just make sure to remove libpostal_data simply because it won't work in this case, as the store path will be immutable.

Ok so I'm getting the idea of using a fixed-output derivation for the data files, in a similar vein to using fetchurl. However I'm looking at using libpostal_data as the build.sh. The problem is that this script appears non-deterministic. Look at:
https://github.com/openvenues/libpostal/blob/027fbc5afc3d825aeab04e4de79b0363b437deec/src/libpostal_data#L122-L123
Furthermore the output of this script isn't just tar.gz files, but performs extraction into a particular directory structure. How do you specify the fixed output hash for this?

Instead of using their download script. It seems I should be able to acquire the data files directly.
let
  version = "v1.0.0";
  classifierData = fetchTarball "https://github.com/openvenues/libpostal/releases/download/${version}/language_classifier.tar.gz";
  libpostalData = fetchTarball "https://github.com/openvenues/libpostal/releases/download/${version}/libpostal_data.tar.gz";
  parserData = fetchTarball "https://github.com/openvenues/libpostal/releases/download/${version}/parser.tar.gz";
in
  ...

However these 3 paths are meant to be composed into a single path with directory structure similar to above. The last_updated* shouldn't be necessary. The above expression would fetch 3 into 3 store paths. What's the right way to do this?

A custom fixed-output derivation is probably the best option.

@CMCDragonkai I've constructed a fixed output derivation here for the libpostal address data:
   parserTarball = nixpkgs.fetchzip {
     url = "https://github.com/openvenues/libpostal/releases/download/v1.0.0/parser.tar.gz";
     sha256 = "193fk4x0j9jwvkcva5rir3zw8nhf994q40xyv59da6mlfxpi6w9q";
     stripRoot = false;
   };

along with another derivation to wrap that
   libpostalData = nixpkgs.stdenv.mkDerivation {
     name = "libpostal-data";
     buildCommand = ''
       mkdir -p $out/data
       ln -s ${parserTarball}/address_parser $out/data/address_parser
       ln -s ${addressBase}/address_parser/transliteration $out/data/transliteration
       ln -s ${addressBase}/address_parser/numex $out/data/numex
       ln -s ${addressBase}/address_parser/address_expansions $out/data/address_expansions
     '';
   };

and finally the derivation to build libpostal
   libpostalc =
     nixpkgs.stdenv.mkDerivation {
       name = "libpostal";
       src = nixpkgs.fetchFromGitHub {
         owner = "openvenues";
         repo = "libpostal";
         rev = "43795a3d903991d3864926393af10c3ec31a161c";
         sha256 = "0i6ij3rjlr4zdf3yz83yadnw8cbgswhmd3717nv0br93hahjyd16";
       };
       buildInputs = with nixpkgs; [ autoreconfHook curl ];
       configureFlags = [ "--datadir=${libpostalData}/data"
                          "--disable-data-download"
                        ];
    };

I'm getting exceptions though when I attempt to use it, the data directory can't be found, which is odd, since I'm specifying the directory as a configure flag (see above), and telling libpostal where the data lives.
  at libpostal_setup_datadir (libpostal.c:266) errno: No such file or directory
ERR   Could not find parser model file of known type
   at address_parser_load (address_parser.c:215) errno: No such file or directory
ERR   Error loading address parser module, dir=(null)
   at libpostal_setup_parser_datadir (libpostal.c:410) errno: No such file or directory
ERR   Error loading transliteration module, dir=(null)
   at libpostal_setup_datadir (libpostal.c:266) errno: No such file or directory
ERR   Could not find parser model file of known type
   at address_parser_load (address_parser.c:215) errno: No such file or directory
ERR   Error loading address parser module, dir=(null)
   at libpostal_setup_parser_datadir (libpostal.c:410) errno: No such file or directory
ERR   Error loading transliteration module, dir=(null)
   at libpostal_setup_datadir (libpostal.c:266) errno: No such file or directory
ERR   Could not find parser model file of known type
   at address_parser_load (address_parser.c:215) errno: No such file or directory
ERR   Error loading address parser module, dir=(null)
   at libpostal_setup_parser_datadir (libpostal.c:410) errno: No such file or directory
ERR   Error loading transliteration module, dir=(null)
   at libpostal_setup_datadir (libpostal.c:266) errno: No such file or directory
ERR   Could not find parser model file of known type
   at address_parser_load (address_parser.c:215) errno: No such file or directory
ERR   Error loading address parser module, dir=(null)
   at libpostal_setup_parser_datadir (libpostal.c:410) errno: No such file or directory
ERR   Error loading transliteration module, dir=(null)
   at libpostal_setup_datadir (libpostal.c:266) errno: No such file or directory
ERR   Could not find parser model file of known type
   at address_parser_load (address_parser.c:215) errno: No such file or directory
ERR   Error loading address parser module, dir=(null)
   at libpostal_setup_parser_datadir (libpostal.c:410) errno: No such file or directory

cc @7c6f434c @CMCDragonkai @albarrentine any thoughts?

What addressBase even is?

@7c6f434c
   addressBase = nixpkgs.fetchzip {
     url = "https://github.com/openvenues/libpostal/releases/download/v1.0.0/libpostal_data.tar.gz";
     sha256 = "1hbckdqizhzznbsfgp5y2b8p074bw97kn766sfmkqmv18j98548n";
     stripRoot = false;
   };

I think you have extra address_parser in your symlinks into addressBase

@7c6f434c I figured it out, I wasn't using the right C function. In regards to the data I ran ./libpostal_data download all datadir and then tar'd it and hosted it somewhere that won't be changed and fetched it separately with nix.

@dmjio Can you construct a PR for the work you have done and link it to this issue?

https://github.com/NixOS/nixpkgs/pull/179613


how do i know is out of sync or not?

I use the Linux version.
After I start the
./omnicored

how do I know is out of sync or not?

You can use the "omni_getinfo" RPC and then compare how many blocks are shown vs. a block explorer such as www.blockchain.info.


add human readable header to operation  page

http://bitshares-explorer.io/#/operations/1.11.147554811
for user quicker identification of where he is at.

added at https://github.com/oxarbitrage/open-explorer/commit/db288a6e2c3c678f49c596336367a80c7ccd656c


update github-workflows to use newer node version

node16 is going to be end-of-life soon, we should switch to a newer node version in .github/workflows

done in #253


Glamorous implementation

Implement Custom Markdown Styling for Workflow Commands
What

Added custom markdown styling support for workflow command outputs
Implemented a configurable markdown styling system through atmos.yaml
Added fallback to built-in default styles when no custom styles are defined
Added new workflow error templates in markdown format
Improved code readability and maintainability in markdown rendering logic

Why

Enhances user experience
Allows users to define their own color schemes and styling preferences
Improves error message readability with consistent formatting and styling
Makes the CLI more accessible by supporting both default and custom color schemes
Follows modern CLI design patterns with rich text formatting

Technical Details

Added markdown settings section in atmos.yaml for custom styling configuration
Implemented style inheritance system (custom styles override built-in defaults)
Added support for styling:

Document text and background colors
Headings (H1-H6) with custom colors and formatting
Code blocks with syntax highlighting
Links with custom colors and underlining
Blockquotes and emphasis styles

Enhanced error handling with structured markdown templates
Added proper fallback mechanisms for style configuration

References

Implements styling using glamour for terminal markdown rendering
Follows ANSI terminal styling standards
Related to workflow command enhancements (#issue_number)

Testing
The implementation has been tested with:

Custom styling configurations in atmos.yaml
Evidence:

Default styling fallback when no custom styles are defined
Evidence:

Various terminal color support levels

Workflow not existent command

https://github.com/charmbracelet/bubbletea
https://github.com/charmbracelet
https://github.com/charmbracelet/glow
https://github.com/charmbracelet/glamour/blob/master/styles/gallery/README.md

Summary by CodeRabbit
Release Notes

New Features

Enhanced workflow command with improved error handling and documentation
Added markdown rendering capabilities with customizable styling
Introduced interactive workflow UI with better error messaging

Documentation

Updated workflow command usage examples
Added detailed error messages for workflow-related operations

Improvements

Refined markdown parsing and rendering
Enhanced terminal user interface for workflow interactions

Dependencies

Updated OPA library version
Updated terminal rendering dependencies

[ ] Document theme/color configuration in atmos.yaml

Please add a few test cases to tests/test_cases.yml


Add MPS3 AN547 Non Secure target

~NOTE: This includes, and depends on #38149. ATM, this means that the last 2 commits in the history are added by this PR.~ Rebased onto current main.
This adds a new target, mps3_an547_nonsecure, that builds TF-M as the Secure world firmware and Zephyr as the Non-secure world firmware.

The CI failure is not related to this PR, so going to merge it and we'll open an issue to track the failure which is due to QEMU.

Okay... turns out CI failure was related to this PR... FYI :-(

It's related to the mps3-an547, but not specifically relating to secure/non-secure. (note that the tests are for the mps3_an547 without the _ns suffix). At least one of the problems is documented in 2 issues: https://github.com/zephyrproject-rtos/zephyr/issues/40970 and https://github.com/zephyrproject-rtos/sdk-ng/issues/420

The other of the problems is documented here: https://github.com/zephyrproject-rtos/zephyr/issues/40569


fix: Updated examples

Refactored examples into separate components for clarity. Added an example passing custom modifiers to the Popper component and to demonstrate the out-of-boundaries hiding.

Thank you! 🙏


Feature/image parser

I added a Parser, that extracts images from the content of the rss feed:

if it's rssv2, it takes the description-Element
if it's atom, it takes the summary and content Element

In addition, the getItemDescription removes the html tags (.replace(/<[^>]+>/g, '');). Perhaps it should go into getElementTextContent function?

Sorry for the slow reply @hkerkhoff . I didn't get around to checking the pull request until now.
I don't like the idea of changing the expected behaviour of the library that is happening in this pull request.

By removing the html elements from the description it could be throwing away valuable information which the clients are expecting. If the user of this library wants to not have the XML or CDATA tags, they can be removed in the client code. I would rather keep this library just returning the pure values.

Finding the image url in the content and description fields is also quite magical and unexpected. As with the change above, I want this library just to return the parsed fields and no do any interpretation of the data. The image of the rss item should be in the correct field in the rss feed. If the user of the library wants to search for images that is ok, but it should be done in the client code.

I will close this pull request without merging it.


Fix button in the Asana board view

Button is back to the board view, but the board task detail view is hijacking the 'focus' event in some way that prevents our listener to be triggered. This solution leaves the user with a dropdown that at least opens on click, but not by tabbing to the input itself. ¯_(ツ)_/¯
ps: I'm open to suggestions towards a solution that goes around whatever this view is doing with the focus event, but I couldn't find one myself. Curious thing is that you can open the console, create an event new Event('focus'), remove all the methods stopImmediatePropagation, stopPropagation, cancelBubble, preventDefault, then dispatch it and it will work. Buuuut if I do that inside the click listener (autocomplete.js L33) it doesn't work.
closes #759

Hmm. Not sure what asana is doing but I did find a way to fix the tabbing too.
Instead of adding the listener to the filter input we can add it to the window with useCapture=true
  window.addEventListener('focus', function(e) {
    if(e.target === that.filter) {
      that.filter.parentNode.classList.add("open");
      that.listItems = that.el.querySelectorAll(that.item);
      that.updateHeight();
    }
  }, true)

@syko amended my last commit with your suggestion.


lateinit property histogramSeries has not been initialized

lateinit var histogramSeries: SeriesApi
charts_view.api.addHistogramSeries(
onSeriesCreated = { series ->
histogramSeries = series
}
)
the issue is, histogramSeries = series never called. any solution?

Hi! Can you make an example project with reproducing of this bug?

@makedonsky94  i just followed the instructions of their official git. (link attached). i'm building on android studio 2020.3.1 with kotlin.
https://github.com/tradingview/lightweight-charts-android

Can you check the version of WebView?

The library supports WebView implementations with version above 51. You can check it here
If you running the example in this repository on virtual device, there might be errors because of old implementations of WebView.

Using Chrome on Samsung Device which have Version 96.0.4664.45. (not working)
tested on emulator pixel5 . faced the same issue. would appreciate if you can please help to figure out.

I just realized that code in the screenshot is expecting that series could be created asynchronously. The method addSeries is  asynchronous and setting data should be placed in lambda onSeriesCreated

Resolved. Thanks for your help!


Cannot createServer with Custom Context in nice-grpc Package

I see that Server can take a special Context (here), however, I could not figure out how to create a server with that context.
import { Server, createContext } from 'nice-grpc';

type CustomType = {
  specialField: string;
}
const server: Server<CustomType> = createServer(); // this fails with: `Type 'Server<{}>' is not assignable to type 'Server<CustomType>'`
const server: Server<CustomType> = createServer<CustomType>(); // I would assume that's how it should be done, but createContext does not take generics

Taking a closer look at the source code, I can see that createServerWithMiddleware function takes a generic, however, this generic can never be accessed from the API user. So I think this can be solved by adding a generic type to createServerWithMiddleware that would get passed on to createServerWithMiddleware

The only way for extra fields to actually appear in the context is through middleware. createServer creates a server with no middleware, so this is the correct behavior. Moreover, by just specifying a generic parameter, you won't get an actual value in the context — there must be some code that sets the value in runtime.
See the authentication middleware example on how to extend the context.

Got it, thanks!


Advices for working with hybrid hexahedral-tetrahedral meshes

Hello everyone,
I would like to work with hybrid hexahedral-tetrahedral meshes in MFEM. At first, I am interested in implementing H1/continuous basis. The configuration at hybrid interfaces is that two tetrahedra can be connected to one hexahedron face. To build a continuous function space from Lagrange finite elements, a solution is to use Qn-basis for hex, a P2n-basis for interface tetrahedra and a Pn-basis for tetrahedra which are not adjacent to hexahedra. Then to add constraints at hybrid interfaces to ensure the continuity.
For more detailed descriptions, there are the following resources:

Ainsworth, M., Davydov, O., & Schumaker, L. L. (2016). Bernstein-Bézier finite elements on tetrahedral–hexahedral–pyramidal partitions. Computer Methods in Applied Mechanics and Engineering, 304, 140-170.

Reberol, M., & Lévy, B. (2016). Low-order continuous finite element spaces on hybrid non-conforming hexahedral-tetrahedral meshes. arXiv preprint arXiv:1605.02626.

From the implementation point of view, there are three type of elements at the same time:

hexahedra (trilinear mappings) with Qn basis
tetrahedra (linear mappings) with Pn basis
interface tetrahedra (quadratic mappings) with P2n basis

and

continuity constraints that can be enforced using the Restriction/Prolongation matrices.

In MFEM, I define a HexTetMesh class, derived from Mesh, to store the hybrid mesh. By re-writting mfem::Load and mfem::GetElementToFaceTable (the STable3D cannot store triangular and quadrilateral faces at the same ting), it seems ok.
I have more difficulties in deciding how to modify the finite element part. The H1_FECollection returns one finite element per Geometry::Type. But I need two types for tetrahedra (normal and interface) and segment (depending if it is a segment of a normal or interface tetrahedron). I could try to add new geometry types but I am afraid that it would lead to lot of code re-writing.
Another possibility I see is to keep the H1_FECollection but to derive a new FiniteElementSpace that would not use the FECollection but my own functions and data structures. But in this case I am also afraid of the consequences.
Ideally, I would like to:

not modify the MFEM code, only write new code / derived classes
write the minimum amount of code

As you are much more familiar with the MFEM code, I would like to hear your insights.  Do you have suggestions on how to proceed ? How would you implement such things ?
Thank you for your help and for providing this awesome library !
Maxence

Hello Maxence,
As far as I can tell, working with the type of meshes and spaces you describe, in MFEM, will require extensions inside the library itself. This should not be a problem - we can work with you to add what is necessary, if you are interested in contributing to MFEM. The first thing to do will be to discuss what approach to take.
One approach is what you describe (let’s call it the non-conforming mesh approach): making the Mesh class (or a derived class) handle non-conforming faces - a quad on one side and 2 triangles on the other side. I'm not sure that this can be done just in a derived class - I think it will require at least some additions in the Mesh class. Of course, one option is to add such support directly in the Mesh class.
If we assume that any two tets adjacent to a hex form a pyramid, then another approach I see (let’s call it the conforming mesh approach) could be to add support for pyramids, something that will be generally useful. Then add special type of bisected H1 finite elements on pyramids and bisected quadrature rules to integrate them. Both the FE and the quadrature can call the appropriate existing tetrahedral FEs and quadratures. One drawback in this approach is that face integrals (think DG) will need to distinguish different types of quad faces - one where both adjacent elements are hexes and another where one is hex and the other a pyramid using a bisected basis. This will not be an issue, if the integrant depends only on the trace (e.g. values and/or tangential derivatives). The problematic case is when the integrand depends on, for example, the normal derivative.
In the non-conforming mesh approach, as you pointed out, the question is how to handle different types of tets. One approach, that may be useful more generally, is to extend the FiniteElementSpace class to support multiple FiniteElementCollections, e.g. based on an array of tags/labels associated with the mesh elements. To support such more general spaces everywhere in the library may require a lot of work and testing. However, starting with support for something simple, like example 1, could be much easier.
In either case, the first step will be to make sure that meshes with mixed types of elements work correctly. I think MFEM v3.2, as is, has problems with such meshes, at least in some cases.
I personally think that the non-conforming approach is probably the better choice, even though adding support for pyramids will also be useful.
Cheers,
Veselin

Hello Veselin,
Thank you for your answer. I am more interested in the non-conforming mesh approach as I want to support the case where the interface tetrahedra do not form a pyramid. It happens when one (or more) tetrahedron is connected to the diagonal of a hex face only by one of his edge (Fig. 1, in the second reference).
For the moment, I have tried something similar to your non-conforming mesh suggestion:

A hex-tet mesh class derived of Mesh
A hex-tet finite element space derived of FiniteElementSpace that have two FiniteElementCollection members

I think it is better to have a separate/derived mesh class as there are additional data-structures that will be queried by the new finite element space (e.g. Is this edge on a hex-diagonal? If so, what is the hex-face id?). My main technical issue is that some member functions of Mesh that I need to modify are not virtual. For the moment I over-write them but eventually it requires explicit pointers in the functions calling them, which involves re-writing the calling functions, etc. I would be happy to contribute and propose changes to the library, but my current approach is very experimental and probably not optimal.
Concerning the derived FiniteElementSpace, I have started by re-writing GetXDofs() functions, but some of them are not virtual, so I have the same difficulties than with the derived Mesh class. A more fundamental problem arises when enforcing the continuity (building the cP matrix): the edge/face DOFs of a order n H1_FECollection are not a subset of the order 2n collection (Lobatto nodes). One solution I see is to duplicate the faces and edges shared by two elements of different type. This means different faces and edges that have the same vertices, I am not sure the current data-structures can handle this.
There are small changes in the current library (in the base classes) that would make the extensions easier, but it would probably add some performance overhead for standard meshes. What is your position on this? I perfectly understand that you would prefer to avoid them.
To be more precise, some examples:

Mesh::GetFaceBaseGeometry which assumes all faces are of the same type
All the DOFs numbering methods in FiniteElementSpace assume that all edges have the same number of dofs
making some base functions virtual

Thank you,
Maxence

Hi Maxence,
Sorry for the delay in my reply.
What you suggest seems reasonable, so feel free to create pull request(s) with any suggestions for extensions and modifications.
Regarding the construction of cP - the local matrix that maps the dofs from the coarse/master (quad) side to the fine/slave (triangles) side can be computed using a new more general version of the method FiniteElement::GetLocalInterpolation - one that supports different types of master and slave elements.
Regards,
Veselin

Hi Veselin,
For the HexTetMesh, HexTetFiniteElementSpace derived classes to work, I made small changes in the core library that you can see in this commit. It seems sufficient for my needs for the moment, I will made a pull request later when I am sure nothing else is required. The rest of the HexTet implementation is not open-source as it is currently a mess with unrelated code mixed in, but I hope to release a clean version before the end of my PhD.
Eventually, I stored all the dofs (masters and slaves) in the edofs, fdofs, bdofs arrays of the FiniteElementSpace (edofs is a new array that act exactly as fdofs, bdofs but for edges).  Then depending of the context, the other functions retrieve only the master or slave dofs. There are also a mess of arrays that store the local configurations (is this edge on the diagonal of a quad? etc). The continuity is enfored by the cP, cR matrices. This implementation works for order one (mix of Q1, P2, P1) and maybe for order two (not sure yet), but I have a hard time debugging the higher orders. Still working on it!
I didn't know about the GetLocalInterpolation, I will surely look into it.
This issue can be closed if it is more convenient for the organization of this GitHub repo. I could re-open it later when I have more information, questions or results.
Best regards,
Maxence

Hi Maxence,
It is great to see the progress you are making! I'll close this issue for now, but please don't hesitate to re-open or ask further questions in the future. Please keep us updated -- we are definitely interested in your project.
Tzanio


use an h1 for the 1st large header on the page

We initially chose to set the first large heading to be an h2, and the smaller sub-heading just before to be an h1.
For SEO and indexing purposes, we need to switch to an h1, and a decorated paragraph before.
So we need to:

re-author all pages to change the h1+h2 to a p>strong and h1
adjust the CSS styles so the h1 & h2 have the red bar at the bottom. also need to fix the 1st h2 styling so it just styles like all other h2s in the page

A good example is http://localhost:3000/us/en/skymiles/how-to-earn-miles/earn-with-delta

@asthabh23 As delta is supposed to start QA on the website starting today, we'll need all regular pages to look good. I thus copied over the page to your drafts https://adobe.sharepoint.com/sites/HelixProjects/Shared Documents/Forms/AllItems.aspx?FolderCTID=0x012000FF16C1F85E2B3849A4CD207A7190B18C&id=%2Fsites%2FHelixProjects%2FShared Documents%2Fsites%2Fdelta%2Fdelta-com%2Fus%2Fen%2Fskymiles%2Fhow-to-earn-miles&viewid=124ad5f1-60ba-476c-ade8-7c1df274ee95# and restored the "clean" overview page for QA review on their end


Can't install print-env

Description : None of installation methods works.
$ kubectl krew install print-env
W0503 09:57:40.128543  540619 install.go:164] failed to install plugin "print-env": install failed: failed to unpack into staging dir: failed to unpack the plugin archive: checksum does not match, want: 247c0329fa51ac84a039113fbb884432568da03d06b767e906371b0b585d3523, got 64695649afbf64c06aed226a4a101e1d9fa8149f3857c8563980e6e3377c20bd
failed to install some plugins: [print-env]: install failed: failed to unpack into staging dir: failed to unpack the plugin archive: checksum does not match, want: 247c0329fa51ac84a039113fbb884432568da03d06b767e906371b0b585d3523, got 64695649afbf64c06aed226a4a101e1d9fa8149f3857c8563980e6e3377c20bd

$ go install github.com/pedrobarco/kubectl-print-env
go: 'go install' requires a version when current directory is not in a module
        Try 'go install github.com/pedrobarco/kubectl-print-env@latest' to install the latest version

$ go install github.com/pedrobarco/kubectl-print-env@latest
go: downloading github.com/pedrobarco/kubectl-print-env v0.1.1
go: github.com/pedrobarco/kubectl-print-env@latest: module github.com/pedrobarco/kubectl-print-env@latest found (v0.1.1), but does not contain package github.com/pedrobarco/kubectl-print-env

$ go install<EMAIL_ADDRESS>go<EMAIL_ADDRESS>module<EMAIL_ADDRESS>found, but does not contain package github.com/pedrobarco/kubectl-print-env

$ go install<EMAIL_ADDRESS>go: downloading github.com/pedrobarco/kubectl-print-env v0.1.0
go<EMAIL_ADDRESS>module<EMAIL_ADDRESS>found, but does not contain package github.com/pedrobarco/kubectl-print-env

$ make build
fatal: No annotated tags can describe '850f2de510a8973556882823287d88953f5f4e2a'.
However, there were unannotated tags: try --tags.
(...)

Jeez, my bad there... I'm sorry for the late response. I'll take a look into it today. Hopefully we'll get this working by the end of the week.

Oh hey you were looking at it the same time as me. I'm wondering if it just needs a new release. I ran this locally, and get what looks like the right hash:
docker run -v $PWD/.krew.yaml:/tmp/template-file.yaml rajatjindal/krew-release-bot:v0.0.43 krew-release-bot template --tag v0.1.1 --template-file /tmp/template-file.yaml

Outputs:
...
  - bin: kubectl-print-env
    uri: https://github.com/pedrobarco/kubectl-print-env/releases/download/v0.1.1/kubectl-print-env_v0.1.1_linux_amd64.tar.gz
    sha256: 64695649afbf64c06aed226a4a101e1d9fa8149f3857c8563980e6e3377c20bd
    selector:
      matchLabels:
        os: linux
        arch: amd64
...

I don't remember what was going on with my CD but it failed when releasing the "broken" one.
I think I can force a new one right now, just to make sure it works via krew.

Here is the run: runs/6795657599. If it doesn't work then I'll have to look into it later.
In the meantime, if you really need the plugin:

checkout the releases  page
make build will work, even if it prints those error messages (that message is a git message saying that it couldn't parse the current tag, nothing to worry about)

The run still failed in the CD stage, I'll dig into this tonight.

I think that view was linking the old failed action because they shared the same commit, but looks like it ran nicely:

And the PR to krew-index was auto-merged:
https://github.com/kubernetes-sigs/krew-index/pull/2331
And I can confirm I can install locally! :tada:
Thanks! This plugin looks quite nice

Oh, you're right! My bad 😄. Thanks!
Nevertheless, I'll not close this issue until I have the remaining installation methods working.
Feel free to create as much issues you want: either bugs or feature requests. Better yet, just fork it and submit a PR.


Update “Extend Kubernetes” concept overview

Rework section index page [preview]
Use more glossary tooltips
Mention APIService more clearly
Shift CRD note to the overview page for API extensions
Also add text to https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/  [preview]

Page previews:
https://deploy-preview-34734--kubernetes-io-main-staging.netlify.app/docs/concepts/extend-kubernetes/
https://deploy-preview-34734--kubernetes-io-main-staging.netlify.app/docs/concepts/extend-kubernetes/compute-storage-net/
https://deploy-preview-34734--kubernetes-io-main-staging.netlify.app/docs/concepts/extend-kubernetes/api-extension/custom-resources/

@sftim Does it make sense to get a technical review?

/lgtm

/approve


[Draft] Generating *.meta.js during production build

This draft PR want to add the feature of the automatic generation of the *.meta.js files. I'm looking for a feedback or a confirmation if this is the appropriate direction.
I'm don't really like the idea to user the replace function to generate the meta filenames, but is the most efficient way that I found since I prefer to avoid to generate twice the metaBlock. Any other ideas ?
In your opinion, we should introduce a flag to enable or disable the generation of these meta files?
Thank you for your feedback!

Hi @guansss,
Do you had a chance to review this PR?
Thanks for your time!

Hi, sorry for the late response! And thank you for this PR, this is a great feature to have!
I wonder why the meta file goes to chunk.auxiliaryFiles? I haven't used it before so I'm not sure what differences it will make.
Using replace to generate the meta filename is definitely okay since the js output's filename is fixed as *.user.js. But there is a pitfall in .replace("user", "meta"), where something like "user-blocker.user.js" will be converted to "meta-blocker.user.js". It should probably be .replace(/\.user\.js$/, ".meta.js").
Having a flag would be nice. I imagine something like options.meta.file or options.meta.outFile?

Thanks for the review! Certainly, regex is the most robust way to perform the replace avoiding problems.
For the auxiliaryFiles I have used this guide as a reference: https://github.com/webpack/webpack/issues/11425#issuecomment-698837871
I understand that we should use them for any file generated during the build that is not a .js or .css.  For this reason, I used them.
For the flag, I was thinking something like options.meta.generate  with true as the default value. The options.meta.file or options.meta.outFile let me think of having the option to specify the meta filename or output file but I won't provide this possibility...or we should?
In the next few days, I will update the PR with the modifications.

Thanks for the update!
In my opinion, the word "generate" fits well, but as an option, it may be a bit too broad and could represent the entire process of converting the original meta.js to the meta comment block (both in *.user.js and *.meta.js). I think at least the word "file" should be included to indicate that we are going to generate an extra file. Maybe options.meta.generateFile?

Changed to options.meta.generateFile it's good!  I've also squashed all the commit into one!


apt: 2.7.14 -> 2.9.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/apt/versions.
meta.description for apt is: Command-line package management tools used on Debian-based systems
meta.homepage for apt is: https://salsa.debian.org/apt-team/apt
meta.changelog for apt is: https://salsa.debian.org/apt-team/apt/-/raw/2.9.2/debian/changelog
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.9.2 with grep in /nix/store/9q0ln05qp2zxjla17ba18pfh8y2nh9pq-apt-2.9.2
found 2.9.2 in filename of file in /nix/store/9q0ln05qp2zxjla17ba18pfh8y2nh9pq-apt-2.9.2

Rebuild report (if merged into master) (click to expand)

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath

apt
python311Packages.python-apt
python312Packages.python-apt
snapcraft

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9q0ln05qp2zxjla17ba18pfh8y2nh9pq-apt-2.9.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A apt https://github.com/r-ryantm/nixpkgs/archive/a6a71942bc81b324c7c892583ac86d732c4c5188.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/a6a71942bc81b324c7c892583ac86d732c4c5188#apt

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9q0ln05qp2zxjla17ba18pfh8y2nh9pq-apt-2.9.2
ls -la /nix/store/9q0ln05qp2zxjla17ba18pfh8y2nh9pq-apt-2.9.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

10 packages built:

apt
apt.dev
apt.doc
apt.man
python311Packages.python-apt
python311Packages.python-apt.dist
python312Packages.python-apt
python312Packages.python-apt.dist
snapcraft
snapcraft.dist

Maintainer pings
cc @AndersonTorres for testing.

@NixOS/nixpkgs-merge-bot merge


recastai is not a constructor

Hi,
returns recastai is not a constructor for nodejs v6.10.2. didn't test with other versions.. please check
const recastai = require('recastai');
const client = new recastai(config.recast);

Hello @gururajmbhandarkar
You just have to edit the following line:
const recastai = require('recastai');
by
const recastai = require('recastai').default;
I already modified the wiki and the README.md
Thanks for your feedback!

Works fine now ! Cheers :) 👍


ctrDRBG Mode 3KeyTDEA has changed to TDES

File - ./include/acvp/acvp_lcl.h
Line Number - 341
Line Content - #define ACVP_DRBG_MODE_3KEYTDEA      "3KeyTDEA"
Should be:
#define ACVP_DRBG_MODE_3KEYTDEA      "TDES"
Or to be more thorough maybe change all occurrences of the word "3KeyTDEA" and "3KEYTDEA" to "TDES" in all of the source code if TDES is the new naming NIST is using.
The ACVP NIST Server changed mode value from "3KeyTDEA" to "TDES":
https://github.com/usnistgov/ACVP/pull/211/files

***ACVP [STATUS][acvp_register:1860]--> Sending registration of capabilities...
***ACVP [INFO][acvp_register:1861]--> [{"acvVersion":"1.0"},{"algorithms":[{"algorithm":"ctrDRBG","revision":"1.0","predResistanceEnabled":[false],"reseedImplemented":false,"capabilities":
[{"mode":"TDES",
"derFuncEnabled":true,"entropyInputLen":[{"max":1048576,"min":112,"increment":8}],"nonceLen":[{"max":512,"min":56,"increment":8}],"persoStringLen":[{"max":1048576,"min":0,"increment":8}],"additionalInputLen":[{"max":1048576,"min":0,"increment":8}],"returnedBitsLen":64}]}]}]
***ACVP [INFO][log_network_status:1442]--> POST Registration...
Status: 200
Url: https://demo.acvts.nist.gov:443/acvp/v1/testSessions
Resp: Recieved
***ACVP [INFO][acvp_parse_test_session_register:2196]--> Received vsid_url=/acvp/v1/testSessions/90643/vectorSets/237114
***ACVP [STATUS][acvp_register:1869]--> Successfully sent registration and received list of vector set URLs

Addressed by PR #425


Check canRetainCheck when saving RetainedStateRegistry

This is mostly @alexvanyo's work from #1253. Unfortunately I couldn't find a way for a PR from a fork to be based on another PR from a different fork.
My changes add the relevant fixes to make sure that saved/restored back stacks (aka back stacks) work with the changes. Primarily this is so that we check both the current back stack and saved backstacks when determining whether we can retain state.
Fixes #1252

Though looks like there's a couple CI failures still


Simple mint shows 0 fees for minting

Fees for simple mint now show always zero, caught by cypress here but also tested manually:

👋

this shows up on loading:

this shows up every time I change price:

i sadly wasn't able to find reason for this while debugging. so open to anyone

need to update @polkadot/api to the latest? https://substrate.stackexchange.com/a/4838
currently we are using<EMAIL_ADDRESS>latest version is<EMAIL_ADDRESS>

need to update @polkadot/api to the latest?

related with kodadot/packages#48 ?

need to update @polkadot/api to the latest?

related with kodadot/packages#48 ?

aahh, I see. yes it might be related with that PR

closed by #4060


Indego integration not working after update to HA 2024.11

Checklist

[X] I have updated to the latest available of the Indego component version.
[X] I have updated to the latest available Home Assistant version.
[X] I have read the README https://github.com/sander1988/Indego/blob/master/README.md) and especially read the part about the KNOWN ISSUES (https://github.com/sander1988/Indego/blob/master/README.md#known-issues).
[X] I have checked hecked for other open or recently closed issues for similar bugs/issues.

The problem
Indego Integration does not start on Home Assistant 2024.11
Expected behavior
A working integration
Steps to reproduce
Update to HA 2024.11
Environment

Indego component release with the issue: 5.7.5
Last working Indego component release (if known):5.7.5
Home Assistant release with the issue: 2024.11.0
Last working Home Assistant release (if known): 2024.10.3
Operating system: HOAS VM on Proxmox

Logs
Logger: homeassistant.config_entries
Bron: config_entries.py:3227
Eerst voorgekomen: 09:28:40 (3 gebeurtenissen)
Laatst gelogd: 09:28:51

Error occurred loading flow for integration indego: cannot import name 'DATA_STORAGE' from 'homeassistant.components.application_credentials' (/usr/src/homeassistant/homeassistant/components/application_credentials/__init__.py)

Logger: homeassistant.config_entries
Bron: config_entries.py:604
Eerst voorgekomen: 09:21:30 (2 gebeurtenissen)
Laatst gelogd: 09:24:22

Error importing platform config_flow from integration indego to set up indego configuration entry: cannot import name 'DATA_STORAGE' from 'homeassistant.components.application_credentials' (/usr/src/homeassistant/homeassistant/components/application_credentials/__init__.py)

Logger: homeassistant.util.loop
Bron: util/loop.py:136
Eerst voorgekomen: 09:24:22 (1 gebeurtenissen)
Laatst gelogd: 09:24:22

Detected blocking call to import_module with args ('custom_components.indego.config_flow',) inside the event loop by integration 'config' at homeassistant/components/config/config_entries.py, line 120: await hass.config_entries.async_reload(entry_id) (offender: /usr/src/homeassistant/homeassistant/loader.py, line 1300: return importlib.import_module(f"{self.pkg_path}.{platform_name}")), please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+config%22 For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#import_module Traceback (most recent call last): File "<frozen runpy>", line 198, in _run_module_as_main File "<frozen runpy>", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module> sys.exit(main()) File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 477, in _handle_request resp = await request_handler(request) File "/usr/local/lib/python3.12/site-packages/aiohttp/web_app.py", line 559, in _handle return await handler(request) File "/usr/local/lib/python3.12/site-packages/aiohttp/web_middlewares.py", line 117, in impl return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 92, in security_filter_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 210, in forwarded_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 26, in request_context_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 86, in ban_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 242, in auth_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 32, in headers_middleware response = await handler(request) File "/usr/src/homeassistant/homeassistant/helpers/http.py", line 73, in handle result = await handler(request, **request.match_info) File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 120, in post await hass.config_entries.async_reload(entry_id)

Additional information
Tried removing and re-installing the integration, but that throws the same errors as above.

i had the same error this morning after upgrading to 2024.11.0
Seems as changing line 9 in custom_components/indego/config_flow.py from
from homeassistant.components.application_credentials import ClientCredential, async_import_client_credential, DOMAIN as AC_DOMAIN, DATA_STORAGE as AC_DATA_STORAGE

to
from homeassistant.components.application_credentials import ClientCredential, async_import_client_credential, DOMAIN as AC_DOMAIN, DATA_COMPONENT as AC_DATA_STORAGE

fixed it.
Maybe @sander1988 can check if this is all that has to be changed ?! Should i write a PR or will you do the change ?

i had the same error this morning after upgrading to 2024.11.0 Seems as changing line 9 in custom_components/indego/config_flow.py

I can confirm, that this does indeed fix the problem. Thanks!! 👍

same error this morning after upgrading to 2024.11.0.
i tryed  changing line 9. Not Working.
When i try to add the indego integration: "500 Internal Server Error Server got itself in trouble"
Indego component release with the issue: 5.7.5
Last working Indego component release (if known):5.7.5
Home Assistant release with the issue: 2024.11.0
Last working Home Assistant release (if known): 2024.10.3
Operating system: HOAS OS on Pi5 8Gb

I tried the fix from @kimzeuner , but I also get the "500 Internal Server Error Server got itself in trouble"
I the logs the following error is then found:
Logger: aiohttp.server
Bron: /usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py:448
Eerst voorgekomen: 13:21:29 (3 gebeurtenissen)
Laatst gelogd: 13:22:57

Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 477, in _handle_request
    resp = await request_handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_app.py", line 559, in _handle
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 92, in security_filter_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 210, in forwarded_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 26, in request_context_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 86, in ban_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 242, in auth_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 32, in headers_middleware
    response = await handler(request)
               ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/http.py", line 73, in handle
    result = await handler(request, **request.match_info)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/decorators.py", line 81, in with_admin
    return await func(self, request, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 74, in wrapper
    return await method(view, request, data, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 172, in post
    return await self._post_impl(request, data)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 179, in _post_impl
    return await super()._post_impl(request, data)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 84, in _post_impl
    result = await self._flow_mgr.async_init(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1301, in async_init
    flow, result = await self._async_init(flow_id, handler, context, data)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1336, in _async_init
    result = await self._async_handle_step(flow, flow.init_step, data)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 517, in _async_handle_step
    result: _FlowResultT = await getattr(flow, method)(user_input)
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/indego/config_flow.py", line 130, in async_step_user
    credentials = self.hass.data[AC_DOMAIN][AC_DATA_STORAGE].async_client_credentials(DOMAIN)
                  ~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
TypeError: 'ApplicationCredentialsStorageCollection' object is not subscriptable

Hy. I was wrong. I allready deleted the indego integration. After a restore and editing the Line 9....working. Dont deleted the indego entity or integration. Just edit and restart.

Did you test with the latest dev version? My last commit did prepare some fixes for changes that are announced to stop working in HA 2025.1 and 2025.6.
This is probably something else, but just to be sure.

@kimzeuner - Please make a PR with the fix you described. I will try to test it soon.

This is where it was changed in the latest release: https://github.com/home-assistant/core/commit/20d4031ed4f6638b2ae192a7b792284ddd769bda
Not sure if changing the import on our side is enough. Might break HA component storage due to domain. But that's based on what is see in the code, can't test right now.

i just tested the latest dev version (5.7.6 is correct ?!) and the error as described in the first post is back. After changing line 9 in the config_flow.py the integration is working again.

changing line 9 in custom_components/indego/config_flow.py
It's work for me
Thanks kimzeuner

Thanks! The integration is working fine again.
I can succesfully install and configure version 5.7.7.

Also here everything seems to work fine after the update!
Thanks


How to configure the veinmining whitelist?

I understand the block tagging system and all that, but how do I add custom tags to a type of block (like all sand)?

To reference a tag from another tag, you'd do #minecraft:sand to reference the sand tag.

To reference a tag from another tag, you'd do #minecraft:sand to reference the sand tag.

right but how do i add the #minecraft:sand tag to the #veindigging:shift_whitelist tag
i can't find anything useful about block tags online

You'll have to do it in a datapack, this might help

I got it, thank you