Upgrading k3s leaves orphaned replicasets?

Environmental Info:
K3s Version:
k3s version v1.22.5+k3s1 (405bf79d)
go version go1.16.10

Node(s) CPU architecture, OS, and Version:

Linux rpi401 5.13.0-1015-raspi #17-Ubuntu SMP PREEMPT Thu Jan 13 01:27:28 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux

Cluster Configuration:

1 server; 4 agents. All RPi 4 (8GB). All running Ubuntu 21.10.
Describe the bug:

I've got some orphaned replicasets:
$ kubectl --namespace kube-system get rs
NAME                                DESIRED   CURRENT   READY   AGE
coredns-7448499f4d                  0         0         0       42d
local-path-provisioner-5ff76fc89d   0         0         0       42d
metrics-server-86cbb8457f           0         0         0       42d
traefik-6b84f7cbc                   0         0         0       42d
coredns-85cb69466                   1         1         1       28d
local-path-provisioner-64ffb68fd    1         1         1       28d
metrics-server-9cf544f65            1         1         1       28d
traefik-786ff64748                  1         1         1       28d

Steps To Reproduce:

Not entirely sure, but the 42d would correspond to when I first installed k3s on this cluster, and the 28d would correspond to when I upgraded it.
Installation: https://blog.differentpla.net/blog/2021/12/20/k3s-ubuntu-reinstall/
Upgrade: https://blog.differentpla.net/blog/2022/01/03/upgrading-k3s/
Expected behavior:

I'm assuming that these replicasets should have been deleted.
Actual behavior:

They weren't.
Additional context / logs:

Is it safe to delete them myself?
Backporting

[ ] Needs backporting to older releases

Yeah, we could probably tweak the canned Deployment manifests to set revisionHistoryLimit: 0 to avoid retaining the old replicaset.

It's purely cosmetic, though, right? Other than the (minor) storage required in the DB? Can I just go ahead and delete them?

A cleaner way to do it might be to patch the deployments to set the revisionHistoryLimit to 0, instead of the default 2.

@brandond what's the status of this?

This is purely a cosmetic thing; I'll take a look at addressing it in the next patch cycle though.

This change was just for the packages that are distributed as flat manifests - coredns, metrics-server, and local-storage but not for bundled components like traefik. Due to this, result looks like this:
$ kubectl get rs -A
NAMESPACE     NAME                                DESIRED   CURRENT   READY   AGE
kube-system   coredns-597584b69b                  1         1         1       43m
kube-system   local-path-provisioner-79f67d76f8   1         1         1       43m
kube-system   metrics-server-5f9f776df5           1         1         1       39m
kube-system   traefik-66c46d954f                  1         1         1       38m
kube-system   traefik-bb69b68cd                   0         0         0       43m

So, it will be change it for next release.


JSON Tutorial missing centered_rect function definition

Description

JSON Tutorial missing the centered_rect function definition, which is important for you to progress further through the tutorial.
Screenshots

Additional context

Although not crucial, some sections earlier on in the tutorial do lack some information which would be nice to have, like lacking some use declarations, whilst the code examples expect you to have.
One example is when you create a new terminal variable in Main.rs section let mut terminal = Terminal::new(backend)?;. However the page never imports ratatui::terminal::Terminal into scope. (Its inside ratatui::prelude, so I assume that was accidentally removed at some point)

Thanks for opening the issue @thomas0305!
w.r.t.:

Although not crucial, some sections earlier on in the tutorial do lack some information which would be nice to have, like lacking some use declarations, whilst the code examples expect you to have.
One example is when you create a new terminal variable in Main.rs section let mut terminal = Terminal::new(backend)?;. However the page never imports ratatui::terminal::Terminal into scope. (Its inside ratatui::prelude, so I assume that was accidentally removed at some point)

I'm hoping to work through all the tutorials with a completely fresh state and ensure no information is missing. But that'll probably happen after the crates-tui tutorial is merged (#440).


Node and edge maps in kirigami

This issue is to track progress on handling node and edge maps in kirigami, which currently cause issues when we remap nodes and edges once an SRP is partitioned.
Background
NV allows a user to create a total map (associative array) data type where the keys of the map are nodes or edges.
This can be useful for various purposes, e.g. tracking which edges or nodes a given solution considers or uses.
Maps in NV are total: that is, they are functions that return a value if it is present, or a default value if it is not. For instance, a dict[tnode, bool] containing the nodes 0n and 2n would return false (as a default) if we asked if 3n was in the map (map[3n]).
For reasons I am not familiar with, we have to unroll the maps into tuples before passing them into Z3 (I assume they are not supported).
To do so, we replace instances of types like dict[tnode, bool] with a tuple, where each expression or symbolic variable we use to access the map is converted into an index: see the code here.
As an example, suppose we have the following NV code (taken from map.nv):
include "utils.nv" (* defines mapbetter and mapo *)

type attribute = dict[tnode,option[int]]

let nodes = 2

let edges = {
  0=1;
}

let merge node x y = (* create a new dict using the minimum distance *)
  let f = mapbetter (fun x y -> if x < y then x else y) in
  combine f x y

let trans edge x = (* increase all map values by 1 *)
  map (fun x -> mapo (fun x -> x + 1) x) x

let init node = (* create a new dict with this node's distance as 0 *)
  let m = createDict None in
  match node with
  | 0n -> m[tnode := Some 0]
  | 1n -> m[tnode := Some 0]

Here, I have a map (called a dict in NV) which maps from nodes to option
integers, and returns None if an integer is not found. The simulation
solution will be:
Label(0):[1n:=Some(1u32),0n:=Some(0u32),default:=None]
Label(1):[1n:=Some(0u32),0n:=Some(1u32),default:=None]

Here is the network NV looks at after map unrolling:
type attribute = (option[int32],option[int32])

let nodes = 2

let edges = {1n-0n;0n-1n;}

let merge = fun node~78 -> fun x~79 -> fun y~80 -> (match (x~79,y~80) with
 |
((UnrollingMergeVar1~122,UnrollingMergeVar1~123),(UnrollingMergeVar2~120,UnrollingMergeVar2~121))
-> ((match (UnrollingMergeVar1~122,UnrollingMergeVar2~120) with
 | (None,x~68) -> x~68
 | (x~69,None) -> x~69
 | (Some x~70,Some y~71) -> Some(if x~70 <u32 y~71 then
x~70 else
y~71)
),(match (UnrollingMergeVar1~123,UnrollingMergeVar2~121) with
 | (None,x~68) -> x~68
 | (x~69,None) -> x~69
 | (Some x~70,Some y~71) -> Some(if x~70 <u32 y~71 then
x~70 else
y~71)
))
)

let trans = fun edge~74 -> fun x~75 -> (match x~75 with
 | (UnrollingMapVar~118,UnrollingMapVar~119) -> ((match
UnrollingMapVar~118 with
 | None -> None
 | Some x~63 -> Some(x~63 +u32 1u32)
),(match UnrollingMapVar~119 with
 | None -> None
 | Some x~63 -> Some(x~63 +u32 1u32)
))
)

let init = fun node~72 -> let m~73=(None,None) in
(match node~72 with
 | 0n -> (match node~72 with
 | 1n -> tuple2Set1-1(m~73,Some(0u32))
 | 0n -> tuple2Set0-0(m~73,Some(0u32))
)
 | 1n -> (match node~72 with
 | 1n -> tuple2Set1-1(m~73,Some(0u32))
 | 0n -> tuple2Set0-0(m~73,Some(0u32))
)
)

What's important to see here is that the attribute is now (option[int32], option[int32]). Hence, merge and trans now operate over UnrollingMapVars (the first and second elements of the tuple) and the
init function sets a value in the tuple.
Where partitioning fails
Now, suppose I wanted to partition this network and compute the solutions separately.
First, the side containing 0n:
type attribute = dict[tnode, option[int]]

symbolic h_1_0 : dict[tnode, option[int]]

let nodes = 3 (* one new input node, one new output node *)

let edges = {0-1; 2-0;} (* 1 is the input, 2 is the output *)

let merge n x y = match n with
 | 1n -> x (* don't care what this is *)
 | 2n -> y (* use the solution sent to us; this is a hack and breaks
commutativity *)
 | 0n -> let f = mapbetter (fun x y -> if x < y then x else y) in
  combine f x y

let trans e x = match e with
 | 0-1 -> map (fun x -> mapo (fun x -> x + 1) x) x (* old trans *)
 | 2-0 -> x (* input-to-base does identity *)

let init n = match n with
 (* the base node: I've partially interpreted the expression *)
 | 0n -> let m = createDict None in m[0n := Some 0]
 (* the input node: use a symbolic variable *)
 | 1n -> h_1_0
 (* the output node: use the base node + trans, also a hack *)
 | 2n -> let m = createDict None in m[0n := Some 1]

This all seems fine. We don't have anything too weird going on here, although I haven't given any restrictions on h_1_0 yet. I did have to do something kind of ugly where (init 2n) needs to actually run (init 0n), but I have a separate solution under consideration to avoid that.
Now, let's see what map unrolling this program gives us.
type attribute = (option[int32],option[int32],option[int32])

symbolic h_1_0~62 : (option[int32],option[int32],option[int32])

let nodes = 3

let edges = {0n-2n;1n-0n;}

let merge = fun node~82 -> fun x~83 -> fun y~84 -> (match node~82 with
 | 1n -> x~83
 | 2n -> y~84
 | 0n -> (match (x~83,y~84) with (* ... *))

let trans = fun edge~78 -> fun x~79 -> (match edge~78 with
 | 0n~2n -> (match x~79 with (* ... *))
 | 1n~0n -> x~79
)

let init = fun node~75 -> (match node~75 with
 | 0n -> let m~76=(None,None,None) in
tuple3Set0-0(m~76,Some(0u32))
 | 1n -> h_1_0~62
 | 2n -> let m~77=(None,None,None) in
tuple3Set0-0(m~77,Some(1u32))
)

In the interest of space, I've chosen to hide some of what merge and trans get unrolled to this time. The important thing is we now have a different attribute from before! Our attribute type is now a 3-tuple of option[int32], where each index represents one of the nodes in this SRP, not the original SRP.
So first off, we no longer have the same attributes in both the original SRP and the partitioned SRP. Could this be a problem? Well, fortunately for us, we still have a node named 1n here, so we can actually write a require clause like this:
let pred x = x[1n] = Some 1
require (pred h_1_0)

This constrains h_1_0 to have Some 1 for the index representing the
node 1n. This works, giving us the solution:
Label(0):[1n:=Some(1u32),0n:=Some(0u32),default:=None]

But it only works because there happened to be a node named 1n in the
partitioned SRP. If instead we had this kind of network:
0 -- 1 -- 2 -- 3

And we cut the edge between 0n and 1n, then the NV program for the side containing 0n would look exactly the same, but we wouldn't be able to create a dictionary referring to node 3n. So, this code would fail:
let pred x = x[3n] = Some 3
require (pred h_1_0)

We get back the following error:
In examples/kirigami/map-a.nv:

5|  let pred x = x[3n] = Some 3
                   ~~

error: examples/kirigami/map-a.nv: Node 3 does not appear in the
network! (The highest node value is 2)

This is a wellformedness check, so we could see what happens when we just tell NV not to check the wellformedness of our program. I recently added a flag allowing us to do that (very bad, I know, but useful for testing this). I'll only show the part that causes problems:
type attribute = (option[int32],option[int32],option[int32])

symbolic h_1_0~67 : (option[int32],option[int32],option[int32])

(* uh oh! *)
require ((match 3n with
 | 2n -> tuple3Get2-2(h_1_0~67)
 | 1n -> tuple3Get1-1(h_1_0~67)
 | 0n -> tuple3Get0-0(h_1_0~67)
)) = Some(3u32)

let nodes = 3

let edges = {0n-2n;1n-0n;}

As you can see, 3n doesn't match any statement in the match pattern of require. The NV error we get back is:
error: internal error (encode_pattern): (0n, node)

Much less clear than before.
Essentially, what this means is that any maps over nodes or edges aren't going to work if we unroll them before partitioning. You might say, that doesn't seem so bad, let's just do map unrolling after partitioning. But then we have a different problem: just doing map unrolling takes longer in a partitioned network than verifying the original network! How can this be? I'm not quite sure, but @DKLoehr believes it's due to the implementation of map unrolling.
An alternative option is to use integers instead of nodes.
If I replace type attribute = dict[tnode, option[int]] with type attribute = dict[int, option[int]], map unrolling produces this code:
type attribute = (option[int32],option[int32])

symbolic h_1_0~67 : (option[int32],option[int32])

require tuple2Get1-1(h_1_0~67) = Some(3u32)

Here, the requirement on node 3n (now just 3) was converted into index
1, since map unrolling only creates tuples to capture all of the
integers we create in the program. As an aside, we explicitly forbid non-constant map keys with the exception of nodes and edges, so you wouldn't be able to write code that computes a new integer map key to add to the map forever.
What this basically means is that because maps of nodes and edges are typed based on the network topology, we can't refer to nodes outside the partition in our maps. This also prevents us from doing something like:
let init node =
 let m = createDict None in
 let k = node_to_key node in
 m[k := Some 0]

NV will complain during map unrolling:
Encountered non-variable, non constant map key whose type isn't node or edge: key~78

Now, at this point, I am inclined to ask, "Does checking for a node like 3n violate the whole premise of hiding information about one SRP's internals from another?"
Well, perhaps that is true, in which case we'd prefer to simply require that our hypothesis only let us talk about the information we receive from our neighbour on the other side of the interface, i.e. for this network:
0 -/- 1 -- 2 -- 3

Our hypotheses should only be able to ask things about 0n and 1n, but not 2n or 3n. In that case, because each cut edge introduces an input node, we can successfully remap any tests on extrapartition nodes to tests on the input node. This introduces a new wrinkle for how we should rewrite code like this:
let assert node x =
  match node with
  | 0n -> x[1n] = 1 && x[2n] = 2 && x[3n] = 3
  | _ -> true

which is perfectly acceptable in the original network.
Should it become:
let assert node x =
  match node with
  | 0n -> x[1n] = 1 (* remove all nodes we can't remap *)
  | _ -> true

One might like to know if the tests are bad to begin with, e.g.
let assert node x =
  match node with
  | 0n -> x[1n] = 1 && x[2n] = 15 && x[3n] = 200
  | _ -> true

For the topology above, this property is clearly false, but in order to
determine that here, we would need to be able to recompute what values
could be computed at 2n and 3n without seeing that part of the topology.
My belief is that this type of case is one where we simply can't help
the user in the partitioned world: if we want to be able to test these
types of programs efficiently, having to compute a way to go from a
query on the value for 2n and the value for 3n here would be isomorphic
to computing queries on the global network.
Ways forward
As you can see, it's a tricky problem. Also to note is that currently, regardless of when map
unrolling is performed, the code will still break if given this require clause on the 0n side:
require (h_1_0[3n] = Some 3)

Hence, I think there are a few ways to solve this issue:

Disallow maps with nodes or edges as keys when partitioning. This would mean users would have to use constants instead. We'd essentially be restricting what kinds of problems we can solve.
Remove all references (perhaps with a warning) to nodes or edges that we can no longer access after the network has been partitioned. There are possible implications to this that I haven't considered yet, and this is effectively also restricting what kinds of problems we can solve, but it fits with the logic that the partitioned networks shouldn't be reasoning about things they can't "see".
Make map unrolling respect partitioning and allow references to nodes and edges that were in the original SRP but not in the partitioned SRP. This could lead to more complicated code that may be slower to transform, but might also be the most intuitive. If it leads to additional slowness, that's something else we can look into fixing in the map unrolling code.

The solution implemented in #65 performs partitioning after all other transformations have been completed. This means that map unrolling runs on the monolithic network and generates a larger-than-necessary unrolling for most partitions, but allows code to keep referencing cut keys without any issues post-unrolling. There may of course be ways to break this, but the brittle approach and restrictions for assertions described in the PR attempt to avoid this in the main case of concern, which is dealing with assertions over nodes in solutions.


neovim: New formula

Depends on:

https://github.com/Homebrew/homebrew/pull/43219
https://github.com/Homebrew/homebrew-head-only/pull/159

Neovim has its own formula in https://github.com/neovim/homebrew-neovim
Sorry, I think we should pass this.


Logstash plugin affected by Log4j vulnerability (CVE-2021-44228)?

Hi all,
is the OpenSearch Logstash output plugin affected by the Log4j vulnerability (CVE-2021-44228)?
If this is the case:

When can we expect a patched version?
Is there any workaround we can implement to protect our infrastructure?

See also https://github.com/elastic/logstash/issues/13501
Kind regards,
Dennis

The output plugin itself seemingly is not affected, however Logtstash is. OpenSearch doesn't build Logstash for the distribution offered on OpenSearch.org, so the fix has to come from upstream. Right now, the suggested mitigation is in the Elastic forum post.
It looks like there is a new version of Logtash in the pipe and the team is working on getting a distribution ready for the downloads page of OpenSearch.org currently.

Please see here https://github.com/opensearch-project/logstash-output-opensearch/issues/108


Speed up ark testing

What is the purpose of this PR?
Closes #336. A lot of tests take a significant amount of time to run. This addresses the obvious ones that can be reduced by changing the data size or eliminating operations that don't need testing.
How did you implement your changes
Specifically, we're looking at tests that take 10 or more seconds to run. Stuff like dimensionality reduction and pixel clustering tests.
Remaining issues
The notebook tests in particular are problematic. The ones that test a complete run through using the default params specified in the notebook can only be sped up by changing the underlying data.
Dimensionality reduction is also prohibitively slow, even with a small dataset, because of the bottlenecks inherent in t-SNE and UMAPs implementations. For now, I've removed the test without file saving, might need to rethink this test further.

Parallel builds soon mean this isn't really an issue, can revisit if things become slow again


less: 600 -> 608

Description of changes

Back on a recommended/non-beta version.
http://greenwoodsoftware.com/less/news.608.html
Changes since 600:

Add the --exit-follow-on-close option.
Fix buffer overflow in bin_file.
Fix termlib detection when compiler doesn't accept calls to undeclared functions.
Fix bug in input of non-ASCII characters on Windows.
Escape filenames when invoking LESSCLOSE.
Fix bug using multibyte UTF-8 char in search string with --incsearch.

This contains a security fix, so I'd like a backport to stable.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

This contains a security fix, so I'd like a backport to stable.

I fail to find that one but since we are technically on a beta version on stable we can backport it anyway.

Please wait for at least one of the darwin platforms to finish on ofborg before merging.

@SuperSandro2000 Just over a month since I last asked you to stop merging PRs so quickly. https://github.com/NixOS/nixpkgs/pull/184617#issuecomment-1202264503

The darwin builder seem to be overloaded again or the job is stuck or lost but less build before when targeting staging so thats fine https://logs.nix.ci/?attempt_id=81aeeabe-c504-4052-9c4f-5ff539c0f4c4&key=nixos%2Fnixpkgs.189974

I'll ask again: please stop merging PRs so quickly. There wasn't any urgency here.


assert_alert_text not working when "screenshot_on_step": true in global setting

when "screenshot_on_step": true in global setting then assert_alert_text failing and getting below issue
19:52:29.572 INFO Test execution started: alert
19:52:29.573 INFO Browser: firefox
19:52:29.579 INFO Test started: test
19:52:29.581 INFO Navigate to: 'https://www.web-playground.net//alert'
19:52:42.890 INFO Click alert-button
19:52:43.041 ERROR UnexpectedAlertPresentException: Alert Text: None
Message: Dismissed user prompt dialog: an alert
Traceback (most recent call last):
File "d:\golem_master\golem\test_runner\test_runner.py", line 202, in run_test_function
f(execution.data)
File "D:\golem_project\projects\gole_project\tests\alert.py", line 5, in test
click(('id', 'alert-button'))
File "d:\golem_master\golem\actions.py", line 914, in click
element.click()
File "C:\Users\sunil.rathore\AppData\Local\Programs\Python\Python38-32\lib\contextlib.py", line 120, in exit
next(self.gen)
File "d:\golem_master\golem\actions.py", line 186, in _step
_screenshot_on_step()
File "d:\golem_master\golem\actions.py", line 175, in _screenshot_on_step
_screenshot_on_condition(execution.settings['screenshot_on_step'])
File "d:\golem_master\golem\actions.py", line 154, in _screenshot_on_condition
screenshot_filename = _capture_screenshot(screenshot_name)
File "d:\golem_master\golem\actions.py", line 97, in _capture_screenshot
get_browser().get_screenshot_as_file(screenshot_path)
File "C:\Users\sunil.rathore\AppData\Local\Programs\Python\Python38-32\lib\site-packages\selenium\webdriver\remote\webdriver.py", line 1032, in get_screenshot_as_file
png = self.get_screenshot_as_png()
File "C:\Users\sunil.rathore\AppData\Local\Programs\Python\Python38-32\lib\site-packages\selenium\webdriver\remote\webdriver.py", line 1064, in get_screenshot_as_png
return base64.b64decode(self.get_screenshot_as_base64().encode('ascii'))
File "C:\Users\sunil.rathore\AppData\Local\Programs\Python\Python38-32\lib\site-packages\selenium\webdriver\remote\webdriver.py", line 1074, in get_screenshot_as_base64
return self.execute(Command.SCREENSHOT)['value']
File "C:\Users\sunil.rathore\AppData\Local\Programs\Python\Python38-32\lib\site-packages\selenium\webdriver\remote\webdriver.py", line 321, in execute
self.error_handler.check_response(response)
File "C:\Users\sunil.rathore\AppData\Local\Programs\Python\Python38-32\lib\site-packages\selenium\webdriver\remote\errorhandler.py", line 241, in check_response
raise exception_class(message, screen, stacktrace, alert_text)
selenium.common.exceptions.UnexpectedAlertPresentException: Alert Text: None
19:52:43.182 INFO Test Result: CODE ERROR
Note: if "screenshot_on_step": false in global setting then assert_alert_text  working fine.
reason: it's look like screenshot nt able take when alert present so in this case when click on alert-button so alert come immediately so it's failing.

Looks like Selenium can't take screenshots when there's an alert open. I added a try/except block and when a screenshot cannot be taken it will log a warning

good find!


FIX : docker-compose for development

I'm having trouble getting the docker-compose up command to work for hot-reload 😅.
To enable hot-reload with docker-compose up, we need to modify the Dockerfile and docker-compose.yml.
Can anyone help me fix this problem? 🤔

version: '3.8'
services:
app:
build: .
container_name: alfa-leetcode-api-docker
ports:
- '3000:3000'
restart: always
environment:
- WDS_SOCKET_HOST=<IP_ADDRESS>
- CHOKIDAR_USEPOLLING=true
- WATCHPACK_POLLING=true
volumes:
- .:/usr/src/app
- /usr/src/app/node_modules
command: npm run dev

The issue has been resolved 😀. Thanks for the contribution @merakesh99


Support for commas in complex linetype text

Hi there,
I'm not familiar with the detailed specificiation for .lin files, but I feel that the linetype load function should support commas in the linetype text for complex text-type linetypes.
We are using netDxf to export ground contours, and if there are half metres these should be shown as "19,5m" for example, if the user's culture settings use commas as decimal seperators.
This fails because the following line in ReadLineTypeComplexSegment will split at commas even if they are contained in quotation marks:
string[] tokens = data.Split(',');
In my version I have replaced that with the following:
string[] tokens = System.Text.RegularExpressions.Regex.Split(data, ",(?=(?:[^\"]*\"[^\"]*\")*[^\"]*$)");
I'm not experienced with regex, but this is something I found on the internet that will apparently split at commas, only when they are not contained in quotation marks, and it seems to resolve this issue.
Thanks for all the work on this project.

This is a bug, and the problem is exactly that. In the LIN file the data is stored separated by commas, but splitting, indiscriminately, the data by the commas will also split the text in LinetypeTextSegments if they contain commas.
If that regular expression does that it will work just fine. I just know the basics about them, and the patterns can get very complex.

Resolved in 2.4.1


windows install fails with error 0x80070001

I have a windows vm executed via libvirt, I run it on a physical drive passing it into the guest. when I pass it via sata pt and try to install windows 11 on it, the install fails with error 0x80070001. I had an installation there which resulted with periodic bosd when sata pt was used.
if I pass the /dev node, I don't get the errors but the performance is horrible due to high hdd usage
reproduction can be done using the attached libvirt xml
I'd expect the sata pt to work without any issues like dev node pt.
host info:

Disto: Gentoo
Kernel 6.6.1
QEMU 8.1.2
QEMU cmd: qemu cmd.txt
libvirt 9.9.0
libvirt xml: save.xml.txt

vm info:

Windows 11
SCSI pt virtio controller
virtio-win <IP_ADDRESS>

I've tested the same setup with ubuntu, doing read and write to the device of multiple GB, no issue at all

Hello @daggs1,
I suggest opening this issue with the QEMU community.
If you are using SATA passthrough, virtio-win drivers are not involved.
Best regards,
Yan.

Greetings @YanVugenfirer,
do you say that despite the fact that the same vm doesn't reproduces the issue when running ubuntu still means this is a qemu issue?
Dagg

Hi @daggs1 , first of all, what I mean is that it's not a virtio-win issue.
I would suggest to try using the latest QEMU. Then you can try to understand if this is a distro or QEMU issue. In any case, qemu community is the better place for it.
Best regards,
Yan.


Updates to BinaryData and HttpResponse

Description
Adds writeTo(OutputStream), writeTo(WriteableByteChannel), and writeToAsync(AsynchronousByteChannel) to BinaryData. Enhances HttpResponse.getBodyAsBinaryData() to pass the length of the response to the created BinaryData, if present.
Modifies azure-core-http-okhttp to use the new BinaryData APIs to simplify request sending logic.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

API change check
APIView has identified API level changes in this PR and created following API reviews.
com.azure:azure-core


Ca 73 corona_pd

Added Scrape and Scrape Meta for corona police department.

Overall, this is a great start! Left some comments to help guide you and please feel free to request my review when ready. I'll dig into the Youtube issue you mentioned in #76 in the meantime

@newsroomdev updated according to #83


Drawer opened initially when using navigation animation

Describe the bug
When I using Drawer with navigation animation the drawer seems to be opened initially and goes out during navigation animation.
To Reproduce
Steps to reproduce the behavior:
Create a simple project with 2 pages, let's say splash and home.
Put a drawer in home.
Make splash as start destination.
Navigate to home from splash after 2 to 3 seconds.
Then you can see the visual glitch
Expected behavior
The expected behavior is drawer will be closed initially. But here drawer seems to be opened.
Screenshots?

Environment:

Android OS version: 12(31)
Device: Emulator(12) and Samsung Galaxy M52(12)
Accompanist version: 0.24.11-rc
Compose Version 1.1.1
Kotlin Version 1.6.10

The drawer isn't 'open' - the drawer just displays its contents off screen (to the left) when it is closed.
You shouldn't ever being using a splash screen as your start destination of your app (instead, use the API specifically designed for splash screens) as per the [Principles of Navigation[(https://developer.android.com/guide/navigation/navigation-principles#fixed_start_destination).

But what about screen1 to screen2 navigation with animation where screen2 has a drawer?

The problem remains the same right?


_get_perspective_coeffs is numerically unstable

🐛 Describe the bug
from torchvision.transforms.functional import _get_perspective_coeffs

A = torch.tensor(((1,1),(0,1)), dtype=torch.float32)

offsets = torch.tensor([[1, 1], [-1,-1], [-1, 1], [1, -1]], dtype = torch.float32)
start = 512+ offsets
end = 512 + (A @ offsets.mT).mT

_get_perspective_coeffs(start, end)

Outputs something like:
tensor([ 9.6265e-01, -9.9404e-01,  5.1198e+02, -5.9690e-03,  9.4310e-01,
1.6095e+01, -1.1649e-05, -4.9741e-05])
Which is wrong, correct answer is:
tensor([ 1, -1,  512,  0,  1, 0,  0,  0])
Downstream issues, e.g. when using perspective:
from torchvision.transforms.functional import perspective
import torch
from PIL import Image

H,W = 1024,1024
img = torch.ones(3,H,W)

A = torch.tensor(((1,1),(0,1)), dtype=torch.float32)
center = torch.tensor((H//2, W//2), dtype = torch.float32)[None]
offsets = torch.tensor([[1, 1], [-1,-1], [-1, 1], [1, -1]], dtype = torch.float32)
start = center + offsets
end = center + (A @ offsets.mT).mT

img_p = perspective(img, start, end, fill = (1, 0, 0))
Image.fromarray((255*img_p.permute(1,2,0)).to(torch.uint8).numpy()).save("img.jpg") # artifacts can be seen here

Issue comes from this line:
https://github.com/pytorch/vision/blob/806dba678d5b01f6e8a46f7c48fdf8c09369a267/torchvision/transforms/functional.py#L686
Replacing the float32 precision there with float64 should solve most problems. Note that this function probably should be remade, e.g. it does not currently give any error for inputting 3 points instead of 4.
Versions
torchvision              0.15.2

See https://github.com/pytorch/vision/pull/8249 for related PR


In what sense is EKSA the same as EKS?

Hi 👋 Just a question:
If my k8s manifests work with EKSA, will they definitely work with EKS? Is there some kind of common core / compatibility testing, or is "EKS" just branding?
To ask a similar but not identical question: What is the level of coupling between EKS and EKSA?
Cheers,
Rob

Thanks for quick response!


chore(release): 1.141.0

See CHANGELOG

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 55851ecf3005debc5244bd8ba299b8dcb1978928
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 55851ecf3005debc5244bd8ba299b8dcb1978928
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

Aborted release to fix CDK issues separately

Abandoned to address CDK changes separately


0.1.0 Breaks in Webpack Dev Server

Haven't been able to nail down exactly what's wrong, but after first compile, if i change a source file, and refresh the app, there is an error in the manifest.

v0.0.10 does not exhibit the problem, so I'm pinned to that for now.

Hi @jsg2021
We just released 2.0.0 version of this plugin for webpack 2.
For webpack 1 there is still a branch webpack1 and version 1.0.0 on NPM.
Please consider upgrading to webpack 2 and version 2.0.0 of this plugin.
If this issue still reproduces on 2.0.0 please re-open this issue.
If you really need to have this in 1.0.0, PR's to webpack1 branch are always welcome, but I don't longer plan to fix issues for webpack1.
Thanks!


Add-DbaAgReplica: Use EndpointUrl when creating endpoint

Type of Change

[ ] Bug fix (non-breaking change, fixes # )
[x] New feature (non-breaking change, adds functionality, fixes # )
[ ] Breaking change (effects multiple commands or functionality, fixes # )
[ ] Ran manual Pester test and has passed (.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[ ] Pester test is included
[ ] If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
[ ] Unit test is included
[ ] Documentation
[ ] Build system

We introduced the parameter EndpointUrl a year ago to support environments with a dedicated subnet for the AG interconnect. But we didn't use this parameter when creating the endpoints, so this had to be done with New-DbaEndpoint beforehand.
With this change we will now use EndpointUrl while creating the endpoint.

Seems reasonable and passes tests 👍🏼


Error: connect ETIMEDOUT

It seems like sometimes when I login, it throws this:
Error: connect ETIMEDOUT
    at exports._errnoException (util.js:746:11)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:983:19)

It loads the OpenAuth steam login, and then it will take forever to login, then it will throw that timed out error.
What is going on?
It only started happening recently.

Nevermind, I believe this is a passport-steam issue


[PUI 2.0] Refactor Block utilities

💰 Refactor
Revisit Block layout utilities

Utilize gap utilities
Ensure box model working properly
Remove -up from responsive sizes

Benefits of refactor
Simplify block layouts
Estimates

closing. not moving forward at this time.


iOS tooltip size changes when scrolling

Hi,
when scrolling on iOS Devices the tooltip starts getting weird sizes. I could reproduce this on an iPhone with iOS 10 Beta as well as an iPad running iOS 9.2.1.
iPhone:

iPad:

Hi, thanks for the report.
I am stuck on iOS7 and I have no newer device to address this. I don't know when I will unfortunately. Would you be ready to help me debug?
This bug is weird as the tooltips should not be affected at all by scrolling unless repositionOnScroll is set to true or if the origin is in a scrollable area.
The first thing to do would be to set breakpoints in the private __scrollHandler method to see what happens. I'd need to know if Tooltipster tries to reposition when it shouldn't, or if it's the browser that just goes crazy and can't handle the display of a plain div. Even if it were Tooltipster that was trying to reposition, the next step would be to understand why it fails at it.

Hi,
so I started debugging the plugin and I think I have found part of the problem. __scrollhandler seems to work fine as the reposition is not called from there. The problem seems to be the resize event that is triggered when Safari changes how much of it's interface is shown. As you can see in the screenshots in the initial post, Safari shrinks the navigation bar when you scroll down so that the website gets more space. This behaviour is reversed if you scroll up. This change triggers a resize event which then triggers the repositioning.
$(env.window)
  // reposition on resize
  .on('resize.'+ self.__namespace +'-triggerClose', function(e) {
    self.reposition(e);
  })
  // same as below for parents
  .on('scroll.'+ self.__namespace +'-triggerClose', function(e) {
    self.__scrollHandler(e);
  });

I am not sure when Apple introduced this behaviour. iOS 8 has it. It works on iOS 6 as there the navigation bar just scrolls up with the content. I don't have access to an iOS 7 device at the moment so not sure if the bug is present there.
The next step would be to find out why the positioning is messed up.

Ok, interesting, thank you. It works fine on iOS 7.
I guess it's the Ruler.measure method (line 1346) that returns a wrong size for the tooltip then. Out of the blue like that, I can't figure out why.
You could set a breakpoint at var tooltipBrc = this.__$tooltip[0].getBoundingClientRect(), and remove the visibility: hidden; property of the .tooltipster-ruler rule, it will let you see what happens during the measuring process.

I think I have found the culprit. On my iPhone 5s the geometry.window.size.height is always 460 even though it should be bigger once I start scrolling. This happens because $(window).height() does not return the right height for iOS devices. Details about this problem can be found here.

The window height is the height of the viewport (not the distance to the top of the page), and should not be affected by scrolling. There is indeed this issue with the window height : #560 but I'm not sure that's the problem here.

The problem isn't really the scrolling but the fact that scrolling toggles the "minimal ui" in Safari. This then triggers a resize event. This is all as it should be.

These are the two states Safari can enter. The problem is that in both cases $(window).height() returns 460 for the iPhone 5s. This causes geometry.window.size.height to always be 460 even after the resize event triggered. Which I guess messes up the height calculation.

Yes, I understood what you meant, and you are actually confirming that issue #560 still happens on iOS9/10, so thanks :)
But the size of the window is supposed to be independant from the size of the tooltip. The size of the tooltip is only subject to its contents. What seems to fail here is the measuring of the content.

First I wanted to thank you for taking the time to help with this issue. I really didn't expect such a quick response.
But now back to the topic :-)
After I got the breakpoints in Ruler.measure() to actually work, I found out that tooltipBrc.bottom did not return the right values. If I use tooltipBrc.height instead, everything seems to works fine.
measure: function() {

  this.__forceRedraw();

  var tooltipBrc = this.__$tooltip[0].getBoundingClientRect(),
    result = { size: {
      // brc.width/height are not defined in IE8- but in this
      // case, brc.right/bottom will have the same value
      height: tooltipBrc.height,
      width: tooltipBrc.right
  }};

I'll have to do some cross-browser testing but that's probably not gonna happen until later next week.
Also I do not need IE8 support so for a quick fix, this would work for me.

You're welcome, and thank you for pinning this iOS bug down.
This line should hopefully work cross-browser then:
height: tooltipBrc.height || tooltipBrc.bottom

"Brc" should be "Bcr" by the way, I'll fix the typo.

I released v4.0.5 with the patch, as I saw no reason not to trust tooltipBcr.height when it's defined.
I wish I could get to the bottom of this getBoundingClientRect Safari bug but hey, that's on Apple I guess.
Thanks again!

Thanks. I'll try it next week.

Hi,
I had a quick look and saw that the width should be changed to
width: tooltipBcr.width || tooltipBcr.right

as well.

Okay thank you, added to 4.0.6


Core: Added suppport for non-latin story names/IDs

Issue: #5876
What I did
Added back support for non-latin story names/IDs using slugify
How to test
yarn jest --testPathPattern id.js

I'm closing this in favor of an approach that simply eliminates punctuation but preserves unicode characters. https://github.com/storybooks/storybook/pull/5964


Cancel Timer

Hello,
I was originally just googling for examples of a Timer in a Viewmodel and came across this repo
With regards to the timer used here...
https://github.com/googlecodelabs/android-lifecycles/blob/17c5b6fcec2eb2de3f943557bcca3b209d110671/app/src/main/java/com/example/android/lifecycles/step3_solution/LiveDataTimerViewModel.java#L40
Dont we still need to cancel that in the viewmodel?
Something like....
override fun onCleared() {
super.onCleared()
timer.cancel()
}

When we work with the Activity , it may make sense to cancel onClear (). How do we cancel when we work with the fragment ?

@GorkemKarayel  ... I might of miss understood your question but...
hmmm I've never come across any reason to cancel an onCleared() in a viewmodel. were overiding the onCleared ... So even if you dont overide.. Its still going to happen.

Thanks for reporting this and the feedback! Just submitted a fix!


Fix: Prompting required parameters for skipped targets

Fix issue with parameters being required even when the targets that declare them as required are skipped

Thanks for your contribution! 😄🎉


Only the fist query parameter is sent

Summary
When I call my API through kong, only the first query parameter is passed.
Steps To Reproduce

Create a route: curl -d 'name=ping&request_path=/api/v1/ping&upstream_url=http://ping:3000/' http://localhost:8001/apis/
Test the route: curl localhost:8000/api/v1/ping?host=www.google.fr&customerId=0
Check what was received on the server side: 'No customerId specified' '/api/v1/ping/?host=www%2egoogle%2efr'

Only the host query parameter was passed. The same issue if I switch the parameters, i.e. calling curl localhost:8000/api/v1/ping?customerId=0&host=www.google.fr only passes customerId=0to the service.
Additional Details & Logs

Kong version: 0.9.0
Kong error logs: no messages besides info and notice
Kong access log:

<IP_ADDRESS> - - [25/Oct/2016:09:37:15 +0000] "GET /api/v1/ping/?host=www.google.fr HTTP/1.1" 400 48 "-" "curl/7.29.0"
<IP_ADDRESS> - - [25/Oct/2016:09:41:24 +0000] "GET /api/v1/ping?customerId=0 HTTP/1.1" 400 42 "-" "curl/7.29.0"

Kong configuration (registered APIs/Plugins & configuration file)
Operating System: using mashape/kong:cassandra3 docker image

Am I missing something while creating the route? Why is only the first query parameter being passed?

can you retry with the curl argument quoted, eg;
curl "localhost:8000/api/v1/ping?host=www.google.fr&customerId=0"

That worked. Thanks!


🐛 BUG: wrangler dev doesn't change the headers in the same way as workers do

Which Cloudflare product(s) does this pertain to?
Workers/Other, Wrangler
What version of Wrangler are you using?
3.1.1
What operating system are you using?
Mac
Describe the Bug
Here it's the code of the worker:
// Export a default object containing event handlers
export default {
	// The fetch handler is invoked when this worker receives a HTTP(S) request
	// and should return a Response (optionally wrapped in a Promise)
	async fetch(request: Request, env: Env, ctx: ExecutionContext): Promise<Response> {
		const body = request.body ? await request.text() : '{}';

		const response =  await fetch('http://localhost:8089/some-route', {
			method: 'POST',
			headers: new Headers(request.headers),
			body,
			redirect: 'follow',
		});

		console.log(await response.json());

		return new Response('Hello world!');
	},
};

According to the documentation workers overwrite the accept encoding in the request, where the wrangler dev doesn't.
WIth the following code, when worker is triggered from Postman in the request.headers we can see the Accept-Encoding header with original header (not overwritten). When you send this request from Postman it will be gzip, deflate, br.
And looks like fetch doesn't support other encodings except gzip, meaning that in case of origin server using something else (e.g. Brotli) – then in the console we can see the following error:
error SyntaxError: Unexpected token '
                                     ', "
                                         F������"... is not valid JSON
    at async Object.fetch (worker.js:65:24)
    at async jsonError (worker.js:87:12) {
  stack: SyntaxError: Unexpected token '
                                        ', "
                                            F������"...…s:65:24)
    at async jsonError (worker.js:87:12),
  message: Unexpected token '
                             ', "
                                 F������"... is not valid JSON
}

In Wrangler v3, wrangler dev runs your Worker in a local simulator of the workers environment—https://github.com/cloudflare/miniflare. Unfortunately that means that you won't see all of the behaviour of the rest of the (non-workers) Cloudflare environment locally (small differences in headers is one aspect of that). To test your Worker against the rest of the Cloudflare environment, you can start a remote preview with wrangler dev --remote.

I know this is closed, but I spent several hours debugging why my code isn't working when upgrading from wrangler 2 to 3. It should be marked in the migration guide that the fetch function doesn't work exactly the same. Something  like "when you are seeing unprintable ��� characters after migrating, it's most likely due to you having specified an  Accept-Encoding header that is not supported by the workerd or something.

I have reworded your very helpful message here and added it to where it would have helped me, @penalosa. I never made a PR to the docs, do you think this is a helpful addition: https://github.com/cloudflare/cloudflare-docs/pull/11966?

Added a comment on the linked pull request – brotli support is currently enabled by default in local development.


[DO NOT MERGE]  SIGINT-2205:  [Deprecate] [Jenkins]: synopsys-security-scan plugin

Added a deprecation message to the log.
Added a deprecation message to the README.
Updated the global config title to include [DEPRECATED].
Updated the application name to include [DEPRECATED].
Updated the pipeline syntax title to include [DEPRECATED].
Updated the freestyle title to include [DEPRECATED].

Add the 'Deprecated' label in the index.jelly file


update vendor'd github.com/prometheus/common/config

Updating from https://github.com/prometheus/common/pull/135
Via:
$ govendor update github.com/prometheus/common/config

Fixes: https://github.com/prometheus/prometheus/issues/4173

shouldn't this be done using fetch instead of update  to get the latest from the repo rather than the local copy?
or maybe even include all subpackages
govendor fetch github.com/prometheus/common/...

I always forget the correct commands so I added a simple wiki page with the examples. Feel free to update if you see anything wrong.
https://github.com/prometheus/prometheus/wiki/Updating-a-vendored-package

@krasi-georgiev Good call. I get the various tool commands confused. I ran your fetch command and pushed.

Thanks LGTM :+1:


Add proximity spawners to some buildings

At present the player can run behind any building and hide. They are eventually flushed out by the seeking enemies but we need to push them harder.
We could place proximity spawners inside some % of buildings. These would slowly spawn enemies from the first wave of the level if the player is within X units of them.

[ ] Create proximity activated spawners
[ ] Add a setting to control density of them in the level
[ ] Generate spawners inside some buildings


Replace ObjectSelector with Selector

Fixes https://github.com/holoviz/param/issues/493

Closing; replacing with PR against master


Jirka kbc 1513 create typed table doc

Jira: KBC-1513
Before asking for review make sure that:

[x] New client method(s) has tests
[x] Apiary file is updated
[x] You declared if there is a BC break or not (will affect next release of a client)

@zajca opraveno, jeste jsem to potunil aby to opravdu odpovidalo


How short-lived is short-lived security token?

I'm developing myq-api-relay with this module.
Would it be okay to log in once, and then over the course of many hours or days, call other functions without logging in, or does the security token only last a matter of minutes?
Thanks

I was wondering this too. I couldn't find any information on the timeframe. But I do know that it's at least it's not longer than 2 hours.

For what it's worth - last I messed with this on my own integration, I think I found it sometimes living as short as 15 minutes. It seemed like they really shortened it with the move to V5.

@brbeaird Interesting... for me in my tests I found it lived longer than that. I'll try to confirm today and report back here with the results.

Great question @techied! I ran a quick test since I didn't know myself. Looks like @brbeaird is on the money - the security token expired after 15 minutes for me.
Marking this closed since the question is answered, but happy to have a discussion around the consequences of this.

Thanks for the research @thomasmunduchira !


FlameAudio.audioCache.loadAll

FlameAudio.audioCache.loadAll
static AudioCache audioCache = AudioCache(prefix: 'assets/audio/');
may i change audioCache path?
like
'assets/audio1/'
'assets/audio2/'
'assets/audio3/'
i had many audios  for many folders

You can, but why don't you just have those folders inside of audio?

How to do ?
because i had many different kind of audios
Wouldn't it be better if we put it in a different kind of path
assets/audio/audio1
assets/audio/audio2
assets/audio/audio3

You can, but why don't you just have those folders inside of audio?

How to do ?
because i had many different kind of audios Wouldn't it be better if we put it in a different kind of path
assets/audio/audio1/ assets/audio/audio2/ assets/audio/audio3/

You can actually put audio files in different paths. You will just have to specify the relative path from assets/audio/ while loading those files. For example, if you have a structure like this:
assets
└─ audio
   ├── bgm
   │   ├── bgm1.mp3
   │   ├── bgm2.mp3
   │   └── bgm3.mp3
   └── sfx
       ├── sfx1.mp3
       ├── sfx2.mp3
       └── sfx3.mp3

then your loadAll call would look something like this:
audio.loadAll(['bgm/bgm1.mp3', 'bgm/bgm2.mp3', 'bgm/bgm3.mp3', 'sfx/sfx1.mp3', 'sfx/sfx2.mp3', 'sfx/sfx3.mp3']);

If you really want to change the path that the AudioCache is looking at, which I expect you don't, you can just set a new audioCache in FlameAudio with a new prefix.
FlameAudio.audioCache = AudioCache(prefix: 'assets/');

I would recommend going with @ufrshubham's solution though.

Thanks full


Allow decimals for reduced speed limit KPH values

This patch allows the renamed reduced_speed_limit_kph property to take numbers instead of integers, allowing more precise values for speed limits converted to km/h from mph. This minor change is backward compatible with the previously approved change and only requires approval of the WZDWG co-chairs.

This type change should also be applied to the average_speed_kph properties of the the TrafficSensor and TrafficSensorLaneData objects. There may be additional properties in the spec that should be updated as well, where a speed measurement type is Integer.

@dxpack thanks, added a new issue for it in #219.


Execution failed for task ':app:compileDebugJavaWithJavac'.  来帮忙看看

:app:compileDebugJavaWithJavac
C:\Users\Administrator\Desktop\react native 8.1\git_BDX\BDX\android\app\src\main\java\com\bdx\MainApplication.java:6: 错误: 程序包com.horcrux.svg不存在
import com.horcrux.svg.SvgPackage;
^
C:\Users\Administrator\Desktop\react native 8.1\git_BDX\BDX\android\app\src\main\java\com\bdx\MainApplication.java:28: 错误: 找不到符号
new SvgPackage(),
^
符号: 类 SvgPackage
2 个错误
Incremental compilation of 1 classes completed in 0.521 secs.
:app:compileDebugJavaWithJavac FAILED
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:compileDebugJavaWithJavac'.

Compilation failed; see the compiler error output for details.

I'm closing this since this is outside the scope of the library, and a simple workaround exists.


Url does not pass as expected

This url: https://www.php.net/manual/en/language.oop5.overloading.php#object.call
Gives these results:
{   "value": {     "url": "https://www.php.net/manual/en/language.oop5.overloading.php#object.call",     "normalizedUrl": "https://www.ph/manual/en/language.oop5.overloading.php#object.call",     "removedTailOnUrl": "",     "protocol": "https",     "onlyDomain": "www.ph",     "onlyParams": null,     "onlyUri": "/manual/en/language.oop5.overloading.php#object.call",     "onlyUriWithParams": "/manual/en/language.oop5.overloading.php#object.call",     "onlyParamsJsn": null,     "type": "domain",     "port": null   },   "area": "text" }
When used like so:
Pattern.TextArea.extractAllFuzzyUrls('https://www.php.net/manual/en/language.oop5.overloading.php#object.call');
I'm using this within a browser (firefox 86 on OSX).
I expect the onlyDomain to be www.php.net
Great project btw, just found this bug when messing about with pasting in urls.

You are right. extractAllUrls is currently a recommended method to extract URLs, but extractAllFuzzyUrls is kind of an experimental thing to extract corrupted ones. I will look into extractAllFuzzyUrls for the issue later.


fixes deleteController and isSigned Controller

closes #91

We aren't using passport. Don't use passport.

Then we have to read the token using expressJWT?

yes!

fixed it ,any changes required ? closes #91

No


Maximum call stack size exceeded on iOS Safari

(neat project! 👍 )
Things work great for me on desktop machines, but not on mobile (ios safari).
For example the rotate example results in the stack trace below.
It looks like magick-wasm doesn't have this issue and may work for me, so I'm going to explore that.  I wouldn't have found that project without reading your issues so thanks for sharing your development in the open.
exception thrown: RangeError: Maximum call stack size exceeded.,<?>.wasm-function[194]@[wasm code]
<?>.wasm-function[2078]@[wasm code]
wasm-stub@[native code]
https://knicknic.github.io/wasm-imagemagick/magick.js:131:120835
invoke_iiiiiii@https://knicknic.github.io/wasm-imagemagick/magick.js:131:113258
<?>.wasm-function[2078]@[wasm code]
<?>.wasm-function[1525]@[wasm code]
<?>.wasm-function[2996]@[wasm code]
<?>.wasm-function[436]@[wasm code]
<?>.wasm-function[636]@[wasm code]
<?>.wasm-function[2811]@[wasm code]
<?>.wasm-function[2805]@[wasm code]
<?>.wasm-function[1962]@[wasm code]
wasm-stub@[wasm code]
bb@[native code]
https://knicknic.github.io/wasm-imagemagick/magick.js:131:119263
callMain@https://knicknic.github.io/wasm-imagemagick/magick.js:131:123423
processFiles@https://knicknic.github.io/wasm-imagemagick/magick.js:75:22
https://knicknic.github.io/wasm-imagemagick/magick.js:48:17
doRun@https://knicknic.github.io/wasm-imagemagick/magick.js:131:124045
run@https://knicknic.github.io/wasm-imagemagick/magick.js:131:124268
runCaller@https://knicknic.github.io/wasm-imagemagick/magick.js:131:123045
removeRunDependency@https://knicknic.github.io/wasm-imagemagick/magick.js:131:12921
receiveInstance@https://knicknic.github.io/wasm-imagemagick/magick.js:131:14203
receiveInstantiatedSource@https://knicknic.github.io/wasm-imagemagick/magick.js:131:14492
promiseReactionJob@[native code]

hrm... I should probably just go an upload a different version of wasm-imagemagick to fix the sample.
I do use compiled versions for the following pages that do work on mobile safari.
See https://knicknic.github.io/imagemagick/  (cool page that lets you create links to arbitrary imagemagick commands and save them). The page even works offline.
a website for splitting comics (why I made this library). https://knicknic.github.io/croppy/
As for JS libraries wrapping imagemagick, I would also recommend https://github.com/dlemstra/Magick.WASM .

Thanks for getting back to me.  After some playing around I decided to just rebuild your project from scratch, and after making a few changes it ended up working well.  We are using it for our chest X-ray experiments (see https://acil-bwh.github.io/slowdown-covid19).
Here are the changes I made to the build:
https://github.com/covictory/WASM-ImageMagick/commit/b61d39e832b4ddabe0caf7e3a9b91cae96ca6dd6
I also hacked up the magic.js to suit my needs.  I know that's bad form, but I was a little tired of emscripten at that point and just wanted things to work : ). The edits are flagged with "COVICTORY" in comments.
https://github.com/covictory/site/blob/master/cxr/thirdparty/magick.js
Thanks again,
Steve

this seems to be working as of latest release, see https://knicknic.github.io/imagemagick/rotate/


Messages will "shuffle" and be out of order according to time

Hello, not sure if this is the correct repo to make this issue in. If it's not, please direct me to where I should post this.
Problem: Messages get wildly out of order according to send time and make the conversation hard to follow.
Expected Result: Messages sent stay in the order of which they are sent / received / delivered (with some give and take due to latency or what have you).
Actual Result: I am able to send a message, then receive a reply a couple minutes later. Upon opening the app the original message will display after the reply and further messages can exasperate this problem.
Description: I previously made this comment on issue #570 about my chats being out of order.
The issue I was seeing didn't quite match the topic of that issue and the next comment told me to check my time sync on the mac and my android. Both are pretty close to the actual time and not far enough apart that messages should display incorrectly minutes after they've been sent.
It happens regularly but normally not from a Desktop client unless I'm seeing it happen on the Android client and then open the desktop client. Then it's usually still messed up.
Well today it happened to a message that I had sent like 5 minutes prior. I opened up the desktop client to see if there was any additional information I could find on it. I found in the "Right Click > More... > Message Info" that my original message had a dateCreated value that is later than the dateSent value.
Here's the "original" message
{
     "ROWID": 3343,
     "originalROWID": 3676,
     "guid": < guid here >,
     "handleId": 1,
     "otherHandle": 0,
     "text": <some text here >,
     "subject": null,
     "country": null,
     "_error": 0,
     "dateCreated": "December 11, 2023 9:47:51 AM", // <----- x
     "dateRead": null,
     "dateDelivered": "December 11, 2023 9:42:34 AM", // <--- x
     "isFromMe": true,
     "hasDdResults": false,
     "datePlayed": null,
     "itemType": 0,
     "groupTitle": null,
     "groupActionType": 0,
     "balloonBundleId": null,
     "associatedMessageGuid": null,
     "associatedMessagePart": null,
     "associatedMessageType": null,
     "expressiveSendStyleId": null,
     "handle": null,
     "hasAttachments": false,
     "hasReactions": false,
     "dateDeleted": null,
     "metadata": "{}",
     "threadOriginatorGuid": null,
     "threadOriginatorPart": null,
     "hasApplePayloadData": false,
     "dateEdited": null,
     "wasDeliveredQuietly": false,
     "didNotifyRecipient": false,
     "isBookmarked": false,
     "attachments": [],
     "attributedBody": [
          {
               "string": < message here >,
               "runs": [
                    {
                         "range": [
                              0,
                              380
                         ],
                         "attributes": {
                              "__kIMMessagePartAttributeName": 0,
                              "__kIMFileTransferGUIDAttributeName": null,
                              "__kIMMentionConfirmedMention": null
                         }
                    }
               ]
          }
     ],
     "messageSummaryInfo": [],
     "payloadData": null
}

and here is the "response" message:
{
     "ROWID": 3344,
     "originalROWID": 3677,
     "guid": < guid >,
     "handleId": 1,
     "otherHandle": 0,
     "text": < response text >,
     "subject": null,
     "country": null,
     "_error": 0,
     "dateCreated": "December 11, 2023 9:46:36 AM", // <----- x
     "dateRead": null,
     "dateDelivered": null,
     "isFromMe": false,
     "hasDdResults": false,
     "datePlayed": null,
     "itemType": 0,
     "groupTitle": null,
     "groupActionType": 0,
     "balloonBundleId": null,
     "associatedMessageGuid": null,
     "associatedMessagePart": null,
     "associatedMessageType": null,
     "expressiveSendStyleId": null,
     "handle": {
          "ROWID": 17,
          "originalROWID": 1,
          "address": < address >,
          "formattedAddress": < formatted address >,
          "service": "iMessage",
          "uniqueAddrAndService": "< address >/iMessage",
          "country": "US",
          "color": null,
          "defaultPhone": null,
          "defaultEmail": null
     },
     "hasAttachments": false,
     "hasReactions": false,
     "dateDeleted": null,
     "metadata": "{}",
     "threadOriginatorGuid": null,
     "threadOriginatorPart": null,
     "hasApplePayloadData": false,
     "dateEdited": null,
     "wasDeliveredQuietly": false,
     "didNotifyRecipient": false,
     "isBookmarked": false,
     "attachments": [],
     "attributedBody": [
          {
               "string": < response text >,
               "runs": [
                    {
                         "range": [
                              0,
                              210
                         ],
                         "attributes": {
                              "__kIMMessagePartAttributeName": 0,
                              "__kIMFileTransferGUIDAttributeName": null,
                              "__kIMMentionConfirmedMention": null
                         }
                    }
               ]
          }
     ],
     "messageSummaryInfo": [],
     "payloadData": null
}

This behaviour makes it very difficult to use the android app (I tend to just use the desktop apps which seem not to have this problem) but I don't want to limit myself to only being able to use BlueBubbles at a computer

Could you join our discord so we can troubleshoot more? Ping me @ tneot01

Here's a recap of the discussion and troubleshooting that happened over Discord, recorded here for posterity should anyone else run into this issue:

Tanay = tneotia
seanlowe = pheeonyx
Tanay — 12/11/2023 9:07 PM
Hey, the main way to debug is to see the data inside your imessage database on the Mac
You can download a sqlite viewer like "DB browser for sqlite"
Then open the ~/Library/Application Support/Messages/chat.db
Open the messages table and then find the message you sent as an example by its guid
You will want to look for the date created column and the date delivered column
Send those two values here
If you need more explanation on any of the steps just lmk
pheeonyx — 12/24/2023 11:35 AM
Sorry it took so long to respond but I have the data from those two messages:
first message (originally sent at 9:42 AM)
date (assuming that's date created) was<PHONE_NUMBER>30762368
date_delivered was<PHONE_NUMBER>69100288
second message (originally received at 9:46 AM)
date was<PHONE_NUMBER>70869888  --
side observation: When viewing "message info" in the BB client dateRead is null but in the DB it was 725135321
Tanay — 12/24/2023 3:04 PM
if you received a message that makes no sense that the dateRead has a value
but yeah looks to be an issue with the mac
because the first message date created is 9:47 (and the date delivered is 9:42) so that makes no sense
pheeonyx — 12/24/2023 3:10 PM
How do we know it's an issue with the mac? I can send messages back and forth from the iMessage client on the Mac and it doesn't shuffle around. Are there things I can do, settings or configuration-wise to mitigate this behavior?
Tanay — 12/24/2023 3:12 PM
iMessage seems to order messages internally differently than we do (we dont know exactly how)
we order by date created as it seems to make the most sense
but it is a known issue specifically on macos high sierra, which your bio says you have
pheeonyx — 12/24/2023 3:15 PM
Hm, interesting. Well, thanks for the explanation. If we ever do find out some way to fix it then that'd be phenomenal but I won't hold my breath. Thanks
Tanay — 12/24/2023 3:20 PM
the only way is probably to brute force it and take the date created or date delivered, whichever is earlier

So if we ever come back to this issue and decide to implement that brute-force method, I'd be grateful and willing to help however I can, whether that be testing or coding.


t.throws fails with incorrect output for "actual"

Change the following test in test/throws.js as below:
function fn() {
    throw new TypeError('RegExp');
}

test('throws (RegExp match)', function (t) {
    t.throws(fn, /^RegExp$/);
    t.end();
});

This will fail, as the match is against the stringified TypeError, not just the message, as outlined here.
The TAP output fails with:
not ok test/throws.js ................................... 2/4
Command: "/usr/local/bin/node throws.js"
TAP version 13
ok 1 should throw
not ok 2 should throw
---
  operator: throws
expected:
  "'/^RegExp$/'":
actual:
  "{ [TypeError": |
RegExp] message: 'RegExp' }
...
ok 3 should throw
not ok 4 test/throws.js
---
  exit:    1
command: "/usr/local/bin/node throws.js"
  ...

The actual parameter, if we look in lib/test.js, is the raw Error object, but in the case of a RegExp match, I think it should be the stringified error.
Making the obvious change (making actual be String(caught && caught.error) in this case doesn't seem to work:
not ok test/throws.js ................................... 2/4
Command: "/usr/local/bin/node throws.js"
TAP version 13
ok 1 should throw
not ok 2 should throw
---
  operator: throws
expected:
  "'/^RegExp$/'":
actual:
  "'TypeError": RegExp'
  ...
  ok 3 should throw
not ok 4 test/throws.js
---
  exit:    1
command: "/usr/local/bin/node throws.js"
  ...

since the quotes aren't balanced. However, the test passes with:
test('throws (RegExp match)', function (t) {
    t.throws(fn, /^TypeError: RegExp$/);
    t.end();
});

I think the actual output should be the stringified error, which is an easy enough change, but why are the quotes unbalanced?

That's a good question - and it seems like something worth fixing.

@yangmillstheory .test stringifies its value, so it is already the stringified error :-) I added some tests to close #269 that illustrate how it works.
As for the unbalanced quotes - I think that's something specific to your machine - the output in your second code block has some weirdness too. What OS and node version are you running?
I'm going to close this for now, but we can reopen if there's something we need to do here.


Pass test_runner's experiment flags to dartdevc

The test_runner now allows configurations and command-line options to specify the set of experiments that should be enabled when running a test. This needs to get plumbed through to the implementations. This issue is for doing that to DDC and DDK.

Fixed by https://dart-review.googlesource.com/c/sdk/+/121262.


Bug: Fix android bug on initialize screen

Update RNReanimated Package causing errors on the initial screen for android phones

Fixes https://github.com/rightoneducation/righton-app/issues/112


MWAA CDK stack currently breaking and does not work with CDK v2

Since upgrading to CDK v2, the MWAA stack fails to deploy.

Issue resolved with commit https://github.com/094459/blogpost-cdk-mwaa/commit/4545bb81bf04b8d2ea6f732b59d3dc26aad6b925


Code cleanup.

make flake8 happy
add .gitignore
add setup.cfg
add pip requirements files.
add restore check function.
add command line arguments support.

Do we really need all the requirements in "requirements.txt" and "requirements-dev.txt"?
I would just leave numpy and tensorflow?
All the rest is excellent, and I thank you very much for the amazing contribution to the project! :)
I will merge the request with the modified requirement files. If I missed something about those, please let me know and I will merge them back in!


⚠ Bofrost.at has degraded performance

In 84f0c4e, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1113 ms

Resolved: Bofrost.at performance has improved in d13a308.


Update and fix tests

Several tests failed due to the date/time in the journey() request being out of the timetable period. I fixed that by actually using the current date. I assume this could still fail on public holidays or weekends with a different timetables.
Some others failed because I was running tests on a Windows machine which is using a different encoding when opening files which broke German umlauts. Passing the correct encoding to open() fixes that.
The nasa/requests/journeys_test.py still fails with the following error: location missing or invalid. After double checking the station IDs they seem to be valid and one can still request journeys at https://reiseauskunft.insa.de/ and https://www.insa.de/fahrplanauskunft. No idea why.

I'll make a different version based on this PR as the DB updated their HAFAS tonight and with that changed the journey id format from seperated by the legacy | to #. Thanks tho :3

I fixed the tests a bit different because your fix relied on the fact that timetables don't change. See 7d9c3895cb50afe21862121783c6f24053653fd2 and 64832a38e0985a4709f864f948cb3ecbebaa94d1


spec: type switch evaluation order?

If a type switch contains cases that are interfaces, then it is possible for multiple cases to match. For example, in https://go.dev/play/p/hiq-bYXX-MM the type is both S and fmt.Stringer.
As far as I can tell, the spec doesn't define which of these cases should match.
For expression switches, the spec says "the case expressions, which need not be constants, are evaluated left-to-right and top-to-bottom; the first one that equals the switch expression triggers execution of the statements of the associated case; the other cases are skipped."
As far as I know, type switches behave the same way. It seems that the type switch section needs similar wording.
cc @griesemer

Related Documentation

The Go Programming Language Specification > Statements > Switch statements
The Go Programming Language Specification > Statements > Switch statements

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

The spec says:

A type switch compares types rather than values. It is otherwise similar to an expression switch.

Thanks, I suppose that covers it.


no_std not compiling (esp-idf-sys: Unsupported target)

I already have esp32-nimble working in a std context just fine, but I would also like to get it running in a no_std context as well, since there seems to be a no_std feature.
However, I'm unable to get esp32-nimble to build, getting the following error:
error: failed to run custom build command for `esp-idf-sys v0.33.7`

Caused by:
  process didn't exit successfully: `/home/leon/Desktop/dev/esp32c6-no-std/target/debug/build/esp-idf-sys-823049c3c6f61c3a/build-script-build` (exit status: 1)
  --- stdout
  cargo:rerun-if-env-changed=ESP_IDF_TOOLS_INSTALL_DIR
  cargo:rerun-if-env-changed=ESP_IDF_SDKCONFIG
  cargo:rerun-if-env-changed=ESP_IDF_SDKCONFIG_DEFAULTS
  cargo:rerun-if-env-changed=MCU
  cargo:rerun-if-env-changed=ESP_IDF_SYS_ROOT_CRATE
  cargo:rerun-if-env-changed=ESP_IDF_VERSION
  cargo:rerun-if-env-changed=ESP_IDF_REPOSITORY
  cargo:rerun-if-env-changed=ESP_IDF_CMAKE_GENERATOR
  cargo:rerun-if-env-changed=IDF_PATH
  cargo:rerun-if-env-changed=EXTRA-COMPONENTS
  cargo:rerun-if-env-changed=ESP_IDF_COMPONENTS
  cargo:rerun-if-env-changed=ESP_IDF_COMPONENT_MANAGER

  --- stderr
  Build configuration: BuildConfig {
      esp_idf_tools_install_dir: None,
      esp_idf_sdkconfig: None,
      esp_idf_sdkconfig_defaults: None,
      mcu: None,
      native: NativeConfig {
          esp_idf_version: None,
          esp_idf_repository: None,
          esp_idf_cmake_generator: None,
          idf_path: None,
          extra_components: [],
          esp_idf_components: None,
          esp_idf_component_manager: None,
      },
      esp_idf_sys_root_crate: None,
  }
  Error: Unsupported target 'riscv32imac-unknown-none-elf'

Please see this repo for an example setup. If I remove the esp32-nimble dependency, and remove all references to in in the main.rs, it builds fine. I've also tried with the esp32c3 (riscv32imc-unknown-none-elf), but ultimately, the error is the same (unsupported target).
Am I missing something here, or is there something else that needs to be done to get no_std working?

you are mixing two completely unrelated things her. Yes esp-idf-sys has a feature called no_std but this has nothing to do with the esp-hal no_std project. If you are using esp-idf-sys you always using esp-idf. You can run a no_std rust application on it but that doesn't change the fact that the underlying rust target is still the normal one against esp-idf. You cannot use esp-idf-sys against the rust no_std targets

I see, thanks for the clarification!


context.ShouldRenew does nothing

This is what I have int the Startup class:
            app.UseCookieAuthentication(options =>
            {
                options.AuthenticationScheme = "Cookies";
                options.LoginPath = new PathString("/login");
                options.AccessDeniedPath = new PathString("/denied");
                options.AutomaticAuthenticate = true;
                options.ReturnUrlParameter = "url";
                options.Events = new CookieAuthenticationEvents
                {
                    OnValidatePrincipal = async (context) =>
                    {
                        if (context.Principal.Identity != null && context.Principal.Identity.IsAuthenticated)
                        {
                            var userManager = context.HttpContext.RequestServices.GetRequiredService<IUserManager>();

                            if (DateTimeOffset.UtcNow - context.Properties.IssuedUtc > TimeSpan.FromSeconds(int.Parse(Configuration["Authentication:ValidationInterval"])))
                            {
                                User user = await userManager.ValidateSecurityStampAsync(
                                    context.Principal,
                                    context.Principal.Claims.Where(c => c.Type == ClaimTypes.NameIdentifier).SingleOrDefault()?.Value);
                                if (user != null)
                                {
                                    context.ReplacePrincipal(await userManager.CreateClaimsPrincipalAsync(user));
                                    context.ShouldRenew = true;
                                    return;
                                }
                            }
                            return;
                        }
                        context.RejectPrincipal();
                        await context.HttpContext.Authentication.SignOutAsync("Cookies");
                    }
                };
            });

The method get calls properly but context.ShouldRenew = true apparently does not make the framework to refresh the cookie.

What version of Cookies are you using?
@HaoK?

1.0.0-rc1-final
On Wed, Feb 17, 2016 at 10:58 PM, Chris R<EMAIL_ADDRESS>wrote:

What version of Cookies are you using?
@HaoK https://github.com/HaoK?
—
Reply to this email directly or view it on GitHub
https://github.com/aspnet/Security/issues/694#issuecomment-185425532.

Might be a dup of https://github.com/aspnet/Security/issues/628, which was fixed after RC1.
@HaoK can you confirm?

Yeah this should be fixed already via #628


Ensure InstallVisualStudio.ps1 doesn't mix RTM and preview versions if both are installed

Attempting to resolve https://github.com/aspnet/AspNetCore-Internal/issues/2210

/azp run all

/azp run AspNetCore-ci

This issue is blocking P4 builds, so I don't want to address #8941 just yet. Seems this fix is sufficient to unblock P4 for now.
It appears the VS Build Tools preview version was actually 16 P4, not 16.1 previews. The agents must be stale.

Hey I think this is causing my build to fail: https://dev.azure.com/dnceng/public/_build/results?buildId=150728

@jkotalik Once #9263 is merged, you should be able to rebase onto master and the builds should go through.


Release Google.Cloud.Orchestration.Airflow.Service.V1 version 2.8.0

Changes in this release:
New features

Add IServiceCollection extension methods for client registration where an IServiceProvider is required. (commit 022fab2)

Created release for Google.Cloud.Orchestration.Airflow.Service.V1-2.8.0


fix(@vtmn/svelte): add aria-label for accessibility on VtmnRating

Context
We will implement the VtmnRating component in a list page.
Current:

With VtmnRating:

In order to be iso with the current display, we will have to hide the note, so we will use the "showValue" props to do this.
But for accessibility we need to have an "aria-label" that contains the note.
Changes description

I've added a new props named "ariaLabel" that will allow to manage the aria-label located on the parent div that will contain the note.
With this same props it allows to internationalize the label in English which was in hard.
I took the opportunity to remove the 2 "if" and put an "if else".
I updated storybook with this new props.

Does this introduce a breaking change?

No

@lauthieb & @thibault-mahe
Can we discuss about my review please ? :)

@Tlahey yes for sure, just planned a call.

@Tlahey, @lauthieb, @thibault-mahe  I am not very skillful on Svelte so don't hesitate to challenge me.
-> Isn't possible to pass the aria-label from the ...$restProps ? Instead of creating an attribute for that.

After discussing with you:
rateArticle => $$restProps
ratingStarNote => $$restProps
ratingStarPosition => generated inside the component (1/5, 2/5, etc.)
ratingNumber => deleted
ratingArticle => deleted

@Mig-l @Tlahey I just converted this PR to draft as it still remains some improvements after our discussion.
Feel free to reopen when the PR is ready for review again.
Thanks a lot! :)

thanks @Tlahey @lauthieb and great job @Mig-l thank you for your contribution :)


Unignore Cargo.lock file

see https://blog.rust-lang.org/2023/08/29/committing-lockfiles.html

Mmmm since we don't provide any MSRV, I don't really see the point of committing the lockfile here.

Let's add it then, I don't have a strong opinion here.


New Pattern: aws-codecommit-codepipeline

Build a new pattern to use AWS CodeCommit as source for AWS CodePipeline. Also create AWS EventBridge event rule using the pipeline as target for a commit on defined git branch.
Use Case
Need this feature to invoke AWS CodePipeline once new code is committed on a defined branch.
Proposed Solution
Create a CodePipeline, CodeCommit repository, event rule with CodePipeline as the target.

[X] :wave: I may be able to implement this feature request
[ ] :warning: This feature might incur a breaking change

This is a :rocket: Feature Request

Suggest to generalize this pattern by allowing the user to chose from various Codepipeline supported source repository (CodeCommit, Github, S3, etc.)


How to cancel Observe on Context Deadline Exceeded?

Hi!
I have a situation where I do Observe and the request reaches the server and then ack reaches the client. But the notifications after don't reach the client (because of connectivity issues due to having a moving server). In this case the Observe call will hang until the context I provided times out. So I get an error from the Observe, but in that' case it doesn't return the Observation.
So later when connectivity is restored and the callback is called with notifications I can't cancel it because Observe never returned the Observation.
Would it be possible to return the Observation here and possibly here? Or would that have some negative side effects?
If this is a viable solution I can make a PR.

When investigating this deeper I see that it is in fact cleaned up on error. I don't really understand what is going on in my case then. Will continue my investigation, closing this meanwhile as I don't know what is going on.


Restore XML format to WF configuration section

Summary
Apply XML formatting and link to other pages of configuration section
Contributes to #2038

Thanks, @nemrism, for making the additional changes. I'll merge your PR now.


New collective page: edit sections

User story
As a collective admin, I can re-order / remove / add sections from my collective page.
Best solution for this problem
The base feature is already implemented. Today collective admins need to contact us, then we set a value in settings.collectivePage.sections. It's an array that should contain all the sections that we want to display for the collective, in the order that we want to display them. For section names, check https://github.com/opencollective/opencollective-frontend/blob/7a19d5e85e765c3f333fadc7888b6fc2ad84c501/components/collective-page/_constants.js#L19
Ex:
settings = {
  "collectivePage": {
    "sections": ["about", "updates"]
  }
}

==> What we need now is a way to edit them, with a proper UI/UX..
Metrics
How many collectives change their default sections.
Documentation
We should add animated GIFs demonstrating how to edit sections when this is done.

@lindatalu I'm re-opening, we need an input from design on this issue but it's also an engineering task and we'll loose track of it if we close it.

Link to the Figma file:
https://www.figma.com/file/GF1gQ7fWNfaOAFNwuLeAUl/OC.com-Hotfix-Fixes?node-id=1038%3A454


fix(plugins): increase max violation code length

There is at least one plugin out there whose code length is longer than 5 - having one or more of those plugins configured would trigger a crash when enumerating plugins or looking codes up.
Fixes #54.

lgtm
thanks @agatti


Glimpse fails to launch: "GEGL operation missing"

Describe the bug
Installing glimpse results in a broken application that exits on startup with the message "GEGL operation missing! Glimpse requires the GEGL operation "gegl:introspect". This operation cannot be found. Check your GEGL install and ensure it has been compiled with any dependencies required for Glimpse."
Steps To Reproduce
Steps to reproduce the behavior:

Add pkgs.glimpse to environment.systemPackages
sudo nixos-rebuild switch
Run Glimpse

Expected behavior
Glimpse should work!
Additional context
gimp works fine for me.
Notify maintainers

@ashkitten @erictapen
Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.10.52, NixOS, 21.05.1970.11c662074e2 (Okapi)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.15`
 - channels(ash): `"home-manager-21.05"`
 - channels(root): `"nixos-21.05.1970.11c662074e2"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

Thanks for the report, @sersorrel. Unfortunately I cannot reproduce your issue. Neither on 11c662074e2ae3dddd7e157918b6981de4ce7857 as you reported nor on current nixos-unstable.
Could you elaborate on your setup a bit? Which window manager/desktop environment are you using? Is it possible that you modified glimpse in an overlay?
I'm running Sway (Wayland) and deleted ~/.config/Glimpse and ~/.cache/glimpse before testing to make sure I didn't have any leftover state in my home directory.

I'm using i3wm (with no separate desktop manager); I installed Glimpse by adding it to environment.systemPackages in /etc/nixos/configuration.nix, I don't think there's any chance I did anything special with overlays there. I can't think of anything else I've done that might have affected this – I only installed NixOS a few days ago. I do have Home Manager installed, so I guess is it possible that something I've installed via that is causing a problem? (I don't have that much stuff installed, though, I don't think.) / on my system is a tmpfs, so if something put a file outside of /nix or /home on install and is expecting it to still be there then it'll be unhappy, but I think I tried running Glimpse immediately after installing it with nixos-rebuild switch and it didn't work even then, so it shouldn't be anything related to that.
Deleting ~/.config/Glimpse changes the icon in the popup, which is weird, it looks like this if that directory isn't present at statup:

and like this if I leave the directory there:

but nothing else seems to change. (I noticed there's a gegl-0.4 directory in ~/.cache and ~/.local/share, but removing it doesn't seem to do anything.)

aha, I found the problem: nix-shell -p graphviz --run glimpse works just fine, and adding graphviz to environment.systemPackages fixes it permanently. see e.g. https://dev.getsol.us/T9486

Ooh nice, didn't think about using a pure nix-shell to circumvent already installed packages clouding the issue. Now I'm able to reproduce the issue. Will add graphviz as runtime dependency then.

Looks like Gimp is not affected, as they got it fixed. Glimpse didn't receive that fix, and it won't in the foreseeable future as the project seems to be on hold.


Rework Chapter "Value-Only serialization" + editorial changes

Complete rework of chapter "Value-Only" (IDTA-01001_ValueOnly.adoc)
Examples added for $value payloads other than submodel to make it easy to understand after example for payload of element within Submodel or structured element.
Aditionally editorial changes were made w.r.t. linking (xref).

@mjacoby after discussion in TF API I completely reworked the chapter. Please check again: also your findings should be covered now. Thank you

The schema needs to be checked against the openAPI specification. @sebbader : can we just include it as is?
The followings bugs as far as I can see:

it needs to be "annotations", not "annoation"
Blob/value is not required
EntityValue: statements are not required, entityType is not required any longer
although making sense the metamodel itself does not require Range to be numbers

There are also elements in the schema that are only defined in Part 2, e.g. OperationResultValueOnly
The grammar could be adapted to use the same terms as the schema

@mjacoby please review again, table was completely revised and rules adapted (and corrected)

@BirgitBoss I've responded to the changes/comments

@BirgitBoss I've responded to the changes/comments

Thanks a lot, I added my responses.

https://github.com/admin-shell-io/aas-specs/tree/SeBa/part-2-bugfix-changes is already closed. So branch https://github.com/admin-shell-io/aas-specs/tree/BiBo/ValueOnly should be merged in IDTA-01001_working directly.


Export/import publisher/resource metadata

Currently, harvesting data is input manually. There is no way to export or import this data to/from SQL. Implement in order to provide a proper method of avoiding rework.

Why would you export/import publisher?

As a backup measure. So far, we need to enter publisher/resource
information manually. If there is any problem with the database, currently,
we already would have to reenter 91 publishers and 160 resources.
Once  this process is automated in the indexer to fetch this info from the
IPT url, for instance, this will still be useful to export/import the list
of IPTs to be managed.

Why not simply using a pg_dump -t  ?

I'm always keeping the angle that there should be user interfaces that are
friendly enough so that non IT people can manage harvesting. The way I see
it, that eliminates the dump possibility. What do you think?

The lontra-harvester should be considered an expert tool that requires documentation and an IT person to at least install and updating it. I don't think a such feature should be implemented unless all the other issues are solved. I would rather document the procedure to backup and restore the tables.

I agree it should require an IT person to install and update it (as the versions improve, right?). I also agree we can document  the procedure to backup and restore these basic tables. I also agree we should solve other issues first, but I don't see how that removes the importance of this issue. If the issue makes sense, despite of other priorities, I suppose we should keep it open, right?


getting on moving platform sometimes teleports player momentarily

unsure how or what triggers it

when it doesn't teleport it also doesn't animate the player onto the platform smoothly always but sometimes just insta steps them on

it 100% gets wrong when alternating between two different moving platforms


Nice

No issue, just to say you have designed something nice, attractive. I know you are busy at work, but if you can keep up the work, it is worth it!!

nice theme +1

Thank you! Means a lot to me ❤
I'll be reworking this theme for v1 soon, stay tuned :)

Just wanted to chime in; thanks for the fish! It's a great theme, and I love to use it every day.


Datahub support

Bootstrap a Datahub project using scalding/gradle-waroverlay-plugin + akhikhl/gretty
https://github.com/scalding/gradle-waroverlay-plugin
https://gretty-gradle-plugin.github.io/gretty-doc/index.html
another overlay plugin:
https://plugins.gradle.org/plugin/io.freefair.war-overlay

Datahub is sunset and soon dead, supporting it would be wasted effort


Update renovatebot/github-action action to v41.0.6

This PR contains the following updates:

Package
Type
Update
Change

renovatebot/github-action
action
patch
v41.0.5 -> v41.0.6

Release Notes

renovatebot/github-action (renovatebot/github-action)
v41.0.6
Compare Source
Documentation

update references to ghcr.io/renovatebot/renovate to v39.57.4 (216b79a)
update references to renovatebot/github-action to v41.0.5 (970566c)

Miscellaneous Chores

deps: update actions/cache action to v4.2.0 (96db4e5)
deps: update dependency @types/node to v20.17.7 (1a7b216)
deps: update dependency @types/node to v20.17.8 (68745b9)
deps: update dependency @types/node to v20.17.9 (ea1646e)
deps: update dependency globals to v15.13.0 (8060e0b)
deps: update dependency prettier to v3.4.0 (d2dddad)
deps: update dependency prettier to v3.4.1 (a4f46bb)
deps: update dependency prettier-plugin-packagejson to v2.5.6 (7a9ab3c)
deps: update dependency typescript-eslint to v8.16.0 (23599a9)
deps: update linters to v9.16.0 (e466aa9)
deps: update pnpm to v9.14.3 (f6b57a6)
deps: update pnpm to v9.14.4 (2e78e63)

Build System

deps: lock file maintenance (438d952)

Continuous Integration

deps: update renovate docker tag to v39.40.1 (15c09f8)
deps: update renovate docker tag to v39.42.0 (83f9920)
deps: update renovate docker tag to v39.42.2 (95bcf7b)
deps: update renovate docker tag to v39.42.4 (54eee2c)
deps: update renovate docker tag to v39.43.0 (c19cfba)
deps: update renovate docker tag to v39.45.0 (da37fda)
deps: update renovate docker tag to v39.45.2 (0d8d2be)
deps: update renovate docker tag to v39.47.0 (67923b7)
deps: update renovate docker tag to v39.47.1 (63116a4)
deps: update renovate docker tag to v39.48.0 (cc8bef8)
deps: update renovate docker tag to v39.49.0 (a581096)
deps: update renovate docker tag to v39.49.1 (0555755)
deps: update renovate docker tag to v39.49.3 (fe1e61f)
deps: update renovate docker tag to v39.50.0 (0b11898)
deps: update renovate docker tag to v39.51.0 (e75b8d6)
deps: update renovate docker tag to v39.54.0 (df511ac)
deps: update renovate docker tag to v39.56.3 (eaab103)
deps: update renovate docker tag to v39.57.1 (5caa6c9)
deps: update renovate docker tag to v39.57.2 (dd1183b)
deps: update renovate docker tag to v39.57.4 (b60e78b)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: .github/workflows/renovate.yml
Command failed: install-tool maven 3.9.3
curl: (7) Failed to connect to archive.apache.org port 443: Connection timed out
curl: (7) Failed to connect to archive.apache.org port 443: Connection timed out


Match pattern validator is not working

I updated the framework today. My model's rule is the next:
['alias', 'match', 'pattern' => '/^[a-zA-Z0-9_-]+$/',
    'message' => Yii::t('app', 'Alias can only contain alphanumeric characters, underscores and dashes.')],

I got the next error:
 PHP Fatal Error – yii\base\ErrorException
Class '/^[a-zA-Z0-9_-]+$/' not found

 in W:\vendor\yiisoft\yii2\helpers\BaseHtml.php:2121

Fixed.


Update _index.md

What this PR does / why we need it:
Changed the link for custom installation of Knative because that guide is no longer available.

/lgtm


gpu support for STT & VAD

[x] gpu STT mac
[ ] gpu silero vad mac ? not sure it works
[ ] cuda silero vad windows ? not sure it works
[ ] cuda silero vad linux ? not sure it works
[ ] cuda STT windows (heard it worked for some people)
[ ] cuda STT linux (heard it worked for some people)

/bounty 50
just for the mkl support, will add more bounties for others, typically just a few lines of change to change check cargo.toml and release-app.yml features

@louis030195 The current benchmark is failing

/attempt #318


support for warp vote functions

It seems that numba cuda does not support warp vote functions, like __all __ballot __popc and so on.
Does there any plan for this?

warp vote functions are crutial for some optimazation.
eg. https://devblogs.nvidia.com/parallelforall/cuda-pro-tip-optimized-filtering-warp-aggregated-atomics/

Warp vote functions are implemented: https://numba.readthedocs.io/en/stable/cuda-reference/kernel.html#warp-intrinsics - if any are missing, new issues should be opened for them.


C# semantic tokens broken in latest main

Tracking bug for https://github.com/dotnet/roslyn/pull/58620
VS version: 32104.127.main
Colorization broken in latest main:

Exception:

Fix has been inserted into VS.


Add support for Tuya _TZE200_7eue9vhc

Adding support for Tublar Roller shades _TZE200_7eue9vhc from Zemismart.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 71.609%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5269

Relevant Lines:
7358

💛  - Coveralls

Codecov Report
Base: 71.56% // Head: 71.52% // Decreases project coverage by -0.03% :warning:

Coverage data is based on head (cad654f) compared to base (a1cf999).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##              dev    #1759      +/-   ##
==========================================
- Coverage   71.56%   71.52%   -0.04%
==========================================
  Files         239      239
  Lines        7358     7383      +25
==========================================
+ Hits         5266     5281      +15
- Misses       2092     2102      +10

Impacted Files
Coverage Δ

zhaquirks/tuya/mcu/__init__.py
53.03% <0.00%> (-0.95%)
:arrow_down:

zhaquirks/tuya/ts011f_plug.py
100.00% <0.00%> (ø)

zhaquirks/tuya/air/ts0601_air_quality.py
100.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Gemma OOM

Hello,
I'm encountering an Out Of Memory (OOM) error while trying to proceed with Gemma using the parameters below. I'm working in an environment with 8 A100 GPUs (80GB each).
model_path=${1:-"google/gemma-2-9b-it"}
total_prompts=${2:-1000}
ins_topp=${3:-1}
ins_temp=${4:-1}
res_topp=${5:-1}
res_temp=${6:-0}
res_rep=1
device="0,1,2,3,4,5,6,7"
tensor_parallel=8
gpu_memory_utilization=0.95
n=200
batch_size=200

Thank you.

Hi,
Thanks for the message. To run Gemma-2, you need to first upgrade to the latest vllm. Since vllm does not have the official release for Gemma-2, you may need to build vllm from source.
If, unfortunately, after installing the latest vllm, it is still not working, you may need to decrease the gpu_memory_utilization. For example, you can try gpu_memory_utilization=0.8.
Also, can you please check if your GPUs are not running other scripts?
Please let me know whether this helps! 🥲

I also tried Gemma 2 using vllm==0.5.1. The results are different from those generated using HF transformers. Maybe we need to wait for a stable vllm version.

Thank you for your response. I was using vllm 0.5.1 and encountered a bug with gpu_memory_utilization=0.95 and a tensor size of 8. I also thought it was a Vllm bug and have been waiting, but some people seem to be inferring with gemma-2-it already, so I'm really not sure.

Yes... I think so. I will also try from my side. If they fix that, I will ping this issue.

Hi,
Since the vllm engine is still problematic, I added the HF engine for the Gemma2 series. I also added a series of rules to sanitize instructions for Gemma2. However, since it is HF, the speed would be much slower than vllm...
If you encounter any issues using new scripts, please let me know~

Oh, thank you! I will try it right away.

Hi! We extracted a bit from Gemma 2 27B here. The sanitized version is here. We are now scaling it up!