Broken workspace rules

Regression?
Yes
System Info and Version
The last working commit is b03f41efec14273cf25c42d4cef326acc36cb319, meaning a443902abca6549839910720b80bd01faf10f387 broke it.
Description
I have these 2 workspace rules in my config:
workspace=w[v1] s[false], gapsin:0, gapsout:0, border:false, shadow:false, rounding:false, decorate:false
workspace=f[1], gapsin:0, gapsout:0, border:false, shadow:false, rounding:false, decorate:false

And I noticed 2 issues:

After opening 2 windows in a workspace, the first one retains the properties of the first workspace rule (it has no border and no rounding)
When I have 2 windows, maximize one of them, only the gaps disappear, the border and rounding stay

How to reproduce

Have the 2 workspace rules
Follow the issues above

Crash reports, logs, images, videos
No response

@MightyPlaza - in case you care

PR above should fix the regressions
however with your rules, floating the only window in a workspace will result in it not getting updated later on when another window gets open which is not a regression from that commit

I know, I already have another issue open for that from a while ago: #5467
Thanks for the PR.


GraphQL CQL-first: batched mutations don't handle LWTs correctly

Data model:
create table foo(k int primary key, v int);
insert into foo(k,v) values(1,1);

A single update works as expected, applied is false and it returns the conflicting value:
mutation {
  update1: updatefoo(value: { k: 1, v: 2 }, ifCondition: { v: { eq: 0 } }) {
    applied
    value { v }
  }
}

# Response:
    "update1": {
      "applied": false,
      "value": {
        "v": 1
      }
    }

However if we batch two of these mutations (stupid query but it is technically valid CQL), the results are incorrect:
mutation @atomic {
  update1: updatefoo(value: { k: 1, v: 2 }, ifCondition: { v: { eq: 0 } }) {
    applied
    value { v }
  }
  update2: updatefoo(value: { k: 1, v: 3 }, ifCondition: { v: { eq: 0 } }) {
    applied
    value { v }
  }
}

# Response:
    "update1": {
      "applied": null,
      "value": {
        "v": 2
      }
    },
    "update2": {
      "applied": null,
      "value": {
        "v": 3
      }
    }

This is because MutationFetcher.executeAsPartOfBatch always reflect the input value:
      return batchContext
          .getExecutionFuture()
          .thenApply(v -> ImmutableMap.of("value", environment.getArgument("value")));

It should invoke toMutationResult instead, like the non-batched variant.
NB: once we do that, we'll run into another issue because the result set cannot be consumed twice; the second mutation will see no rows and assume the mutation has succeeded. We can solve that by making batchContext.getExecutionFuture() a CompletableFuture<Row> (a batch returns at most one row).

a batch returns at most one row

Actually no, a batch can return multiple rows if it operates on different rows in the same partition.

To sum up:
CREATE TABLE foo (k int, cc int, v int) values (k,cc,v);
INSERT INTO foo(k, cc, v) VALUES (1, 1, 1);
INSERT INTO foo(k, cc, v) VALUES (1, 2, 2);

A conditional batch is limited to a single partition, but it can target different rows in that partition. All requests must succeed, otherwise none of them are applied (even non-conditional ones):
cqlsh:test> begin batch
        ... update foo set v=2 where k=1 and cc=1 if v=1;
        ... update foo set v=3 where k=1 and cc=2 if v=4;
        ... apply batch;

 [applied] | k | cc | v
-----------+---+----+---
     False | 1 |  1 | 1
     False | 1 |  2 | 2

We can't rely on a 1:1 mapping from requests to rows because:
a) non-conditional requests don't generate a row:
cqlsh:test> begin batch
        ... update foo set v=2 where k=1 and cc=1;
        ... update foo set v=3 where k=1 and cc=2 if v=4;
        ... apply batch;

 [applied] | k | cc | v
-----------+---+----+---
     False | 1 |  2 | 2

b) rows are sorted by comparator order, regardless of the order of the queries:
cqlsh:test> begin batch
        ... update foo set v=3 where k=1 and cc=2 if v=4;
        ... update foo set v=2 where k=1 and cc=1 if v=1;
        ... apply batch;

 [applied] | k | cc | v
-----------+---+----+---
     False | 1 |  1 | 1
     False | 1 |  2 | 2

c) multiple queries can target the same row (doesn't necessarily make sense but it's technically possible):
cqlsh:test> begin batch
        ... update foo set v=2 where k=1 and cc=1 if v=1;
        ... update foo set v=2 where k=1 and cc=1 if v=3;
        ... apply batch;

 [applied] | k | cc | v
-----------+---+----+---
     False | 1 |  1 | 1

So the proper way to handle results is to look up the primary key for each query.


pronto integration with teamcity

Hello,
I have been wondering if anybody got similar problem when working with TC server. We are automatically building PR friom GH (https://blog.jetbrains.com/teamcity/2013/02/automatically-building-pull-requests-from-github-with-teamcity/). I specify +:refs/pull/(*/merge) in branch specification. And this creates sth called detached branch like this (note - this maybe not a full instruction):
[Updating sources] VCS Root: ah-flights-logger (7s)
[13:57:34][VCS Root: ah-flights-logger] revision: 6f8c020730e17f1cf52a70dee9c8547887c73f42
[13:57:34][VCS Root: ah-flights-logger] [/opt/teamcity/TeamCity/buildAgent/system/git/git-C03074D4.git]: /usr/bin/git show-ref
[13:57:34][VCS Root: ah-flights-logger] [/opt/teamcity/TeamCity/buildAgent/system/git/git-C03074D4.git]: /usr/bin/git ls-remote origin
[13:57:36][VCS Root: ah-flights-logger] [/opt/teamcity/TeamCity/buildAgent/system/git/git-C03074D4.git]: /usr/bin/git show-ref refs/heads/master
[13:57:36][VCS Root: ah-flights-logger] [/opt/teamcity/TeamCity/buildAgent/system/git/git-C03074D4.git]: /usr/bin/git show-ref refs/pull/9/merge
[13:57:36][VCS Root: ah-flights-logger] [/opt/teamcity/TeamCity/buildAgent/system/git/git-C03074D4.git]: /usr/bin/git fetch --progress origin +refs/pull/9/merge:refs/pull/9/merge (1s)
[13:57:38][VCS Root: ah-flights-logger] [/opt/teamcity/TeamCity/buildAgent/system/git/git-C03074D4.git]: /usr/bin/git log -n1 --pretty=format:%H%x20%s 6f8c020730e17f1cf52a70dee9c8547887c73f42 --
[13:57:38][VCS Root: ah-flights-logger] [/opt/teamcity/TeamCity/buildAgent/work/509933754420bea0]: /usr/bin/git config remote.origin.url
[13:57:38][VCS Root: ah-flights-logger] [/opt/teamcity/TeamCity/buildAgent/system/git/git-C03074D4.git]: /usr/bin/git pack-refs
[13:57:38][VCS Root: ah-flights-logger] [/opt/teamcity/TeamCity/buildAgent/work/509933754420bea0]: /usr/bin/git show-ref
[13:57:38][VCS Root: ah-flights-logger] [/opt/teamcity/TeamCity/buildAgent/work/509933754420bea0]: /usr/bin/git ls-remote origin
[13:57:40][VCS Root: ah-flights-logger] [/opt/teamcity/TeamCity/buildAgent/work/509933754420bea0]: /usr/bin/git show-ref refs/remotes/origin/pull/9/merge
[13:57:40][VCS Root: ah-flights-logger] [/opt/teamcity/TeamCity/buildAgent/work/509933754420bea0]: /usr/bin/git log -n1 --pretty=format:%H%x20%s 6f8c020730e17f1cf52a70dee9c8547887c73f42 --
[13:57:40][VCS Root: ah-flights-logger] Commit '6f8c020730e17f1cf52a70dee9c8547887c73f42' is not found in repository. Running 'git fetch'...
[13:57:40][VCS Root: ah-flights-logger] [/opt/teamcity/TeamCity/buildAgent/work/509933754420bea0]: /usr/bin/git fetch --progress origin refs/pull/9/merge (1s)
[13:57:41][VCS Root: ah-flights-logger] [/opt/teamcity/TeamCity/buildAgent/work/509933754420bea0]: /usr/bin/git log -n1 --pretty=format:%H%x20%s 6f8c020730e17f1cf52a70dee9c8547887c73f42 --
[13:57:41][VCS Root: ah-flights-logger] [/opt/teamcity/TeamCity/buildAgent/work/509933754420bea0]: /usr/bin/git config core.autocrlf
[13:57:41][VCS Root: ah-flights-logger] [/opt/teamcity/TeamCity/buildAgent/work/509933754420bea0]: /usr/bin/git checkout -q -f 6f8c020730e17f1cf52a70dee9c8547887c73f42
[13:57:41][VCS Root: ah-flights-logger] Cleaning ah-flights-logger in /opt/teamcity/TeamCity/buildAgent/work/509933754420bea0 the file set ALL_UNTRACKED
[13:57:41][VCS Root: ah-flights-logger] [/opt/teamcity/TeamCity/buildAgent/work/509933754420bea0]: /usr/bin/git clean -f -d -x

Now running pronto on such branch equals getting following error:
/usr/local/bundle/gems/pronto-0.6.0/lib/pronto/git/repository.rb:76:in `target': Object not found - no match for id (2f78ae08fccdded7b2a2cdff4ec3a65a96f04b73) (Rugged::OdbError)
[13:57:52][Step 9/10] 	from /usr/local/bundle/gems/pronto-0.6.0/lib/pronto/git/repository.rb:76:in `head'
[13:57:52][Step 9/10] 	from /usr/local/bundle/gems/pronto-0.6.0/lib/pronto/git/repository.rb:72:in `merge_base'
[13:57:52][Step 9/10] 	from /usr/local/bundle/gems/pronto-0.6.0/lib/pronto/git/repository.rb:15:in `diff'
[13:57:52][Step 9/10] 	from /usr/local/bundle/gems/pronto-0.6.0/lib/pronto.rb:40:in `run'
[13:57:52][Step 9/10] 	from /usr/local/bundle/gems/pronto-0.6.0/lib/pronto/cli.rb:52:in `run'
[13:57:52][Step 9/10] 	from /usr/local/bundle/gems/thor-0.19.1/lib/thor/command.rb:27:in `run'
[13:57:52][Step 9/10] 	from /usr/local/bundle/gems/thor-0.19.1/lib/thor/invocation.rb:126:in `invoke_command'
[13:57:52][Step 9/10] 	from /usr/local/bundle/gems/thor-0.19.1/lib/thor.rb:359:in `dispatch'
[13:57:52][Step 9/10] 	from /usr/local/bundle/gems/thor-0.19.1/lib/thor/base.rb:440:in `start'
[13:57:52][Step 9/10] 	from /usr/local/bundle/gems/pronto-0.6.0/bin/pronto:6:in `<top (required)>'
[13:57:52][Step 9/10] 	from /usr/local/bundle/bin/pronto:22:in `load'
[13:57:52][Step 9/10] 	from /usr/local/bundle/bin/pronto:22:in `<main>'

Locally it works fine. Any ideas how to work with detached branches like this?
Regards
MP

I managed to create a workaround build step like this:
#!/bin/bash -x

PRID=$(expr "%teamcity.build.branch%" : '\([0-9]*\)\/merge')
if [ -z "$PRID" ]
then
  exit 0
fi

git fetch --all
COMMIT=$(git log -n 2 --right-only --pretty='%H' | tail -1)
git branch -a --contains $COMMIT
BRANCH=$(git branch -a --contains $COMMIT | grep 'remotes/' | head -1| sed 's#.*/##g')
rm -rf ./*
git clone -b $BRANCH git@github.com:AirHelp/%PROJECT_NAME%.git
cd %PROJECT_NAME%
GITHUB_ACCESS_TOKEN=%env.GITHUB_ACCESS_TOKEN% PULL_REQUEST_ID=$PRID docker-compose run pronto
cd ..
rm -rf ./*

It works, but just look at this script...

OK. Managed to streamline this a bit:
#!/bin/bash -x
PRID=$(expr "%teamcity.build.branch%" : '\([0-9]*\)\/merge')
if [ -z "$PRID" ]
then
  echo "Cannot run pronto analysis on non-PR branch. Information about PR ID not found."
  exit 0
fi

if [ -d ./%PROJECT_NAME% ]
then
    rm -rf ./%PROJECT_NAME% 2> /dev/null
fi

git clone git@github.com:AirHelp/%PROJECT_NAME%.git
pushd %PROJECT_NAME%
git fetch origin pull/$PRID/head:pronto
git checkout pronto
#rest of the script goes here

So we can close this issue for now :)

@mpluta-airhelp cool, glad you managed to work it out 😄


SyncReadMems read with enable doesn't work in chisel3

import chisel3._

class MyModule extends Module {
  val io = IO(new Bundle {
    val addr = Input(UInt(3.W))
    val en = Input(Bool())
    val out = Output(UInt())
  })

  val mem = SyncReadMem(8, UInt(32.W))
  io.out := mem.read(io.addr, io.en)
}

object Test extends App {
  chisel3.Driver.execute(args, () => new MyModule)
}

Compiling the above code results in a RefNotInitialized exception in Firrtl.

Type of issue

[x] Bug report
[ ] Feature request
[ ] Other enhancement

If the current behavior is a bug, please provide the steps to reproduce the problem:
Run my code above

What is the current behavior?
RefNotInitialized Exception in Firrtl
What is the expected behavior?
No exception

Impact

[x] no functional change
[ ] API addition (no impact on existing code)
[ ] API modification
[ ] unknown

Development Phase

[x] request
[ ] proposal

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. Stack Overflow, gitter, etc)

Below is (I think) a functionally equivalent workaround and effectively what we should be emitting here.
  io.out := DontCare
  when (io.en) {
    io.out := mem.read(io.addr)
  }

Does this happen to be related to the the issue I brought up in the users group:
https://groups.google.com/forum/#!topic/chisel-users/d-outotUNw8
?


feat: Add Dockerfile and nginx-conf configmap

Signed-off-by: TheYoungManLi<EMAIL_ADDRESS>If we want to deploy it in k8s, we should create a configmap for it,
and mount that into container's /etc/nginx/conf.d/default.conf.

/lgtm
/approve


Share Custom Methods #276

Copied from https://github.com/frhagn/Typewriter/issues/276
Is there a way to create a .tst file with custom methods and share this methods across my templates without copy and paste in the template files?
Or a way to create one extension dll, could be both

not before planned migration to new extensibility sdk
https://learn.microsoft.com/en-us/visualstudio/extensibility/visualstudio.extensibility/?view=vs-2022


Incorrect parsing of spaces in arguments

If I call something like archlinux-java-run -- "arg with space", it will run something like /usr/lib/jvm/java-14-openjdk/bin/java arg with space. Note that the quotes around it disappeared, thus splitting that argument into three.
A good way to find these bugs is pasting the code on https://www.shellcheck.net/, which indeed does report a lot of issues, some potentially related to this issue.

I just pushed 7b149f9af5885169413070f7844565f4a2ea6f3c which should fix this issue. Could you do me a favor and test if this works in your environment?
Basically, you can copy the script from git (https://raw.githubusercontent.com/michaellass/archlinux-java-run/master/archlinux-java-run.sh) directly to /usr/bin/archlinux-java-run. The only thing you need to adjust afterwards is that you modify line 30 (https://github.com/michaellass/archlinux-java-run/blob/master/archlinux-java-run.sh#L30) and set JAVADIR to /usr/share/java.
Shellcheck indeed shows a couple of code smells which I will go through at some point in time. However, this issue was a bit more subtle.

WFM

Please release a new version so that I can set it as minimum requirement in my project.

Yeah, this somehow got forgotten right before the finish line. Expect a new release within the next 24 hours.

@piegamesde I just pushed a new version to AUR.

Thank you


404 in readme link

The readme links to https://meeples10.github.io/resource-distribution.html for more info, but that link is a 404

Thanks for the heads up, I'll fix it as soon as I get a chance.

Closed by 99d6ef7.

Closed by 99d6ef7.


When limiting center to bounds, ignore offsets less than a pixel.

This PR contains a fix for #2427 that is much less intrusive than #4074.
In essence, this checks if the calculated offset is less than a pixel, and in that case ignores the offset and uses the current center.
I have verified that this fixes the issue with the example code provided by @emacgillavry: without the fix, I get a slow scroll to the north when the map is in fullscreen, but with it, the map performs as expected.
To me, this looks like a much cleaner solution. Specifying equals per projection might be correct in some sense, but looks like unnecessary complexity to me, if we can avoid it.

Looks great, thanks Per!

Heros! Many thanks for tackling this issue.


Icon to see git blame no longer showing in status bar

I have git blame installed as an extension in VS code, but I no longer see the icon in the status bar so I don't know how to use it anymore. :-(

Hey marywelch-chief!
The extension recently moved from the left side of the status bar to the right side. This change was done to better reflect what vscode intends the two sides to be related to: left is project information and right is for the current file/selection.
It is also possible that you have disabled the status bar item. To check if it has been disabled right click on the status bar and make sure that Git Blame (Extension) has a checkmark.

@marywelch-chief Thank you for asking this question, I thought it was gone, too!

I seem to be having a similar problem, but I do have my git blame enabled.

Hey Alfred. Thank you for the screenshot! In this specific case the extension is hidden as there is no space for it to display. If you change the priority (gitblame.statusBarPositionPriority), disable some other items, or make the window wider somehow it should return.

I was able to see it again once I got vs code on a really big screen...
thank you for the tip on where to look for it.
On Fri, Aug 19, 2022, 5:40 AM Alfred @.***> wrote:

I seem to be having a similar problem, but I do have my git blame enabled.
[image: bilde]
https://user-images.githubusercontent.com/10848252/185601398-15f8d787-2d8f-4268-ad55-2d7dcb11f105.png
—
Reply to this email directly, view it on GitHub
https://github.com/Sertion/vscode-gitblame/issues/130#issuecomment-1220524918,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AX7W66UQGO74QGLHFT6PBILVZ5QAZANCNFSM56FUMR4Q
.
You are receiving this because you were mentioned.Message ID:
@.***>


SqlQuery: drop app QName and WSID from query if exists

pkg/sys/sqlquery/impl.go

take the sql query from ArgumentObject().AsString(field_Query)
drop stuff that determines --wsid presense, we will not use this approach
consider sql query could look like this: select [appOwner.appName.][wsid.]tableName ...

has appOwner.appName. -> consider we want to make the select from that app, obtain and use further IAppStructs for that app
has wsid. -> consider we want to make the select from that wsid, obtain and use further IWorkspace for that wsid

cut off [appOwner.appName.], [wsid.] from the query because sql parser does not understands that, see here
make sqlparser.Parse() be called with the cleaned sql query

update tests

see tests: https://github.com/voedger/voedger/blob/32314794fd814e8ed9d8e367c4e44baa573d07cf/pkg/sys/it/impl_sqlquery_test.go#L502

Try to close with PR #2031
Reopened with dept #2036


Admin privileges

Could you give me admin privileges? I would like to make these help documents on the wiki, but I can't do that unless I'm an admin. And I would like to rename the org to "WurstDevelepers".

Done!


Renaming predicates/functions that use a constant

Rename p1 and only the first one in the following condition gets renamed:
(and (p1 ?t1) (p1 o1))
The code does not find the predicate, unless the name is followed by ) or -.

Fixed in 2.13.0


add Service Pack info in os release

Add service pack information in the osinfo release field for windows
exemple: Build 7601 Service Pack 1

@Rodrigo54: in osInfo() I now added a new attribute servicepack which returns major and minor version of service pack (but I guess this will only apply to older Windows versions and will be 0.0 now on Windows 10). Version 4.2.0 just published


The webpacker compilation lock is global

https://github.com/shakacode/shakapacker/blob/b86a3508fd1f88444f5ca3f81c96a3e31d2ff823/lib/webpacker/compiler.rb#L22-L24
There is a potential problem here. Our lock file is global (created in Dir.tmpdir with a fixed name), so if we have 2 projects using Shakapacker compiling at the same time, then the second will wait for the first to finish and return true without actually compiling :(

Should we use process id in the log file name? Or create it in the working directory?
If an input file changes while we are waiting, do we want to run Webpack again at the end?

Originally posted by @alexeyr-ci1 in https://github.com/shakacode/shakapacker/pull/139#discussion_r913239041

Or create it in the working directory?

This. Or maybe base temp file name on current working directory.

If an input file changes while we are waiting, do we want to run Webpack again at the end?

Good point. I reckon replacing true with compile on line 24 should do the trick.

+1 on temp file in the current directory

Using a tempfile in the active or compilation target directory sounds like a good solution. I'm trying a workaround by setting the TEMP env during compilation

@ahangarha another good one for v7.


refactor: removed context driven fields @context and $schema from DID Document and Schema Document respectively

Context driven fields such as @context and $schema should be added to a Document outside of Blockchain. For instance, @context can be added inside a DID Document Resolver upon querying the DID Document from the Blockchain.

@context is now required because of the JSON-LD signing support.


Change instructions for citations

Currently, we instruct users to input names as Firstname Lastname _and_ for the citations (in Identifying Information) but Lastname, Firstname _and_ for the references.
We should change the citations field instructions to match the references.
This relates to https://github.com/NASA-IMPACT/nasa-apt/issues/825 cc @bwbaker1

https://github.com/NASA-IMPACT/nasa-apt-frontend/pull/581 uses the formatAuthors code to format the authors. We should keep the input consistent for authors across the app.


Add utility to try to rescue frames from a corrupted nd2 file

from nd2 import rescue_nd2

for f in rescue_nd2('bad_file.nd2', frame_shape=(512, 512, 3), dtype='uint16'):
    ...  # do something with the rescued frame

note that frame_shape must be in the shape as it appears on disk, which is usually (Y, X, C)

cc @kevinyamauchi


Change tab filename when switching between splits in the same tab

environment

vim: nvim 0.4.4
vim-airline: latest
OS: Pop!_OS
Have you reproduced with a minimal vimrc: N/A
What is your airline configuration:

let g:airline#extensions#tabline#enabled = 1
let g:airline#extensions#tabline#show_buffers = 0
let g:airline#extensions#tabline#show_splits = 0
let g:airline#extensions#tabline#show_tabs = 1
let g:airline#extensions#tabline#show_tab_nr = 0
let g:airline#extensions#tabline#show_tab_type = 0
let g:airline#extensions#tabline#show_close_button = 0

if you are using terminal:

terminal: GNOME Terminal
$TERM variable: xterm-256color
color configuration (:set t_Co?): gruvbox
if you are using Neovim:
does it happen in Vim: N/A

actual behavior
In a specific tab, when switching to a different split, the filename on the tab doesn't change to the filename of that split.
expected behavior
Although, I could use let g:airline#extensions#tabline#show_splits = 0 I'd like to keep the tabline minimal and instead have the filename on the tab change. This is similar to how lightline behaves if you've ever used it. Could there be a way to do this?

This one may be the same as #2294
Fixing this would make things match the default tab behavior in vim, which changes the name in the tab to match the active/focused window.

Is this a problem that is reproduced in vim8?

Yes, I'm seeing this issue in both vim 8.1 and in neovim 0.5

Is this a bug? I opened this issue as more of a feature request.


Update README.md

Checklist

[x] I made something good today 💐.
[ [x] put links in the correct format: [Tool](link) — description.
[ ] [x]description starts with the lower-case letter and ends with the full stop.
[ ] I put the tool in the alphabetical order.

Optional

[ ] I added the appropriate labels: free, open-source or mac.
[ ] I put the tool only to one category.
[x] I followed Contribution Guidelines.

Thanks for all your contributions!


show gas estimation on buy

Fixes #1066

Changes proposed in this PR:

added gas estimation to buy

closing this, as:

230 lines of code are too much for this functionality
nobody uses ETH mainnet in our market, so usefulness is questionable


docs: update to include readthedocs for clients

Closes #266.

I think in Antora xref is used to link to pages (and sections) that are within Antora's control. To link a location outside of Antora's control use <URL>[<description>]
The if you go to the action's failure there is a link to the workflow that gets spawned on the docs-site repo with the error message
https://github.com/kaskada-ai/docs-site/actions/runs/4941820940/jobs/8834812669


Gridview with Large Database Slowly

I have a employee table, it is contain 3 million row record, I generate model and I generate CRUD..I not change code anymore, it works, but why very slow for access Gridview or actionIndex...
And then I debug, and I check profiling oh
I check and see bad code in https://github.com/yiisoft/yii2/blob/master/framework/data/ActiveDataProvider.php#L164
return (int) $query->limit(-1)->offset(-1)->orderBy([])->count('*', $this->db);

and then I change this code which one
$x = $query->select('max(id) as max_id')->asArray()->one();
return (int)$x['max_id'];
and it solved...
I know my code not universal.. I should get primarykey to detect max data.. please fix it

You change your dataProvider as
$dataProvider = new ActiveDataProvider([
            'query' => $query,
            'totalCount'=> Employee::find()->count()
        ]);


github: run unit tests on CentOS Stream 9 and 8

Run unit tests on CentOS Stream 9 and 8.  This will catch scenarios where we use Go features or libraries not supported by those distributions.

Had to fix the env setting in the config yaml and the CS8 repo is called powertools, not crb.


fix: use new routeOptions object. No more deprecation warnings

This fixes deprecation warnings because Fastify moved these into their own object, routeOptions.

Hello! Thank you for making a PR!
I haven't had the time to look at this closely, but if I understand correctly, this routeOptions object was added in a recent minor version wasn't it? I would rather keep compatibility with the entire v4 line until v5 releases by either adding a fallback or just waiting it out.

Thanks for taking a look! The routeOptions were added in v4.10 which was released in November 2022. I've tested this change back to then.
It's worth noting that this plugin already requires 4.5, so there's a precedent as well.
I'm happy to add backwards compatibility if needed but I'm guessing it should be ok. Anyone using latest fastify with the current version will have two extra log lines for every HTTP request, it's a lot!
Let me know what works best :)

@serdnam what's the best route forward here?

@serdnam apologies for the delay on this. I've updated the PR to include back compatibility

I have published v7.1.0, let me know if you have any issues<EMAIL_ADDRESS>


Organizes Web and Cordova docs

Nice job on the documentation, very helpful.

@dmitrig01 added a new step to the Makefile that runs that compiles the Table of Contents at the top of both guides from comments in branch.js. I kept forgetting to update it. see build_utils/toc_generator.pl

wow nice perl!! @hubt would be proud

haha, last time I wrote this much perl, it went into the cgi-bin folder :-P

great work. i think this is good to go :+1:


Moving models to specific folders by use

These are the changes and the modules affected:

Move image models to nets/image

deeplab.py
unet.py
vit.py
wisenet.py
setr.py

Move time series models to nets/time_series

cnn.py (is this one right?)
imu_transformer.py
inception_time.py
resnet.py

Hello @GabrielBG0 , in relation to:

cnn.py (is this one right?)

Yes, it is right.


Implement decimal format modifier in Sleigh files.

This patch implements dec modifier support for token fields, as in token fields that are marked as such are represented as decimal values from OperandSymbol.print.  I also took the liberty to reserve both bin and oct modifiers (but not implement them yet) as modifiers for token fields.  Documentation was also updated but since I'm not a native English speaker that may need some work.
To get this to work I added a field called base in tokens' XML tags that can carry either 2, 8, 10, or 16 according to the field modifier being used.  Due to this breaking change (new .sla files will load in old Ghidra installations but not the other way around) I also bumped SLA_FORMAT_VERSION to 3.
Now, I understand this is quite a critical bit of code to touch so I'm open to all sort of suggestions on how to get this to merge-level quality - especially the base checking code in OperandSymbol, which I assume can be implemented better but I'm not really familiar with that bit of Ghidra myself.
Another point on which I'd like to get suggestions is what sort of unit tests should be added to exercise this, since the Ghidra team may have some ideas on how to tackle this.
In case anybody wonders, this is needed to get 65C02 support working as there are instruction patterns in the form: :OPCODE^bit imm8 ... where bit is an integer whose token field has the decimal modifier and without this patch it would be rendered as OPCODE0x0 imm8 ....  For the record, said opcodes are BBR, BBS, SMB, and RMB - although it wouldn't surprise me if there are other architectures with similar needs.

Would it be possible to implement #1146 without requiring much work? Could use 754 or something as the number IEEE 754 While not common it would allow for psuedo instructions such as mips li.s $f5,3.141592654 to be disassembled and the float value displayed instead of the following.
lui     at,0x4049
ori     at,at,0xfdb
mtc1    at,$f5

It shouldn't be too hard to get something working, assuming that:

Symbols still hold integer values and convert such data to floating point only when rendering the symbol contents
Ghidra can handle arbitrary precision floating point conversion or only a limited set of token bit lengths can be used for this.

It will involve changes in this patch, though, unless a float/non-float flag is added and then floating point values are rendered using the chosen base (so something like token (0, 31) hex float could be possible).
Still, I'd rather hear from the Ghidra team before trying to add the floating point support so a more general solution can be devised (plus they know where all the conversion bits are located so I don't have to jump around the sourcetree to find the right bit of code :)).

It shouldn't be too hard to get something working, assuming that:

Symbols still hold integer values and convert such data to floating point only when rendering the symbol contents
Ghidra can handle arbitrary precision floating point conversion or only a limited set of token bit lengths can be used for this.

It will involve changes in this patch, though, unless a float/non-float flag is added and then floating point values are rendered using the chosen base (so something like token (0, 31) hex float could be possible).
Still, I'd rather hear from the Ghidra team before trying to add the floating point support so a more general solution can be devised (plus they know where all the conversion bits are located so I don't have to jump around the sourcetree to find the right bit of code :)).

Of course it is best to wait for feedback,  no problem with that.
It's currently possible to display the value as a float by right clicking the value in the listing's instruction field, selecting convert and then float.  There is just currently no way of having sleigh do this automatically.


Intended usage of resulting index.html?

I'm confused on how to use the resulting index.html in my root doc repo after running mkdocs-multirepo --build.
The method I'm using looks fine, but it feels "hacky" and the top level search does not work. Is there a way to display the repositories similar to the way I am in my demo (as opposed to listing them in the left-hand navigation menu like in the docs' demo), but also include a top level search?

My idea was not to use MkDocs for the main page at all, but rather create a standard HTML page, as shown in the example. No markdown, just plain HTML.
Then, you can implement search using a third-party service like DocSearch that crawls over the published subprojects and generates a search index which you can integrate on your main page. This also has nothing to do with MkDocs, it's a generic search service for any website.


Create a hello world tutorial

hello, I want to create a tutorial with a bot studio

Fixed in #58.


[Offtopic] Feedly activity

Recently I have payed attention that number of requests in my instance (https://feed.eugenemolotov.ru) has reduced:
https://feed.eugenemolotov.ru/plots/2019-03-09.png - March 9
https://feed.eugenemolotov.ru/plots/2019-03-10.png - March 10
In access.log I have found out, that feedly reduced activity. Here is greped log for certain query:
https://pastebin.com/cxdDYyQM
Before March 9 (including it) period between certain queries was approx 30 minutes, after march 9 (excluding it) period became 3 hours.
Checked for other clients in access.log, they don't seem to reduce period.
Question: is my instance the only one, who has such behavior?
/cc feedly maintainers: @alexmick @okonet
/cc instance hosters: @captn3m0 @mitsukarenai @sebsauvage

Looks like it has been resolved https://feed.eugenemolotov.ru/plots/2019-03-18.png


fix: Refresh kart umiddelbart når lag aktiveres

A picture tells a thousand words
Before this PR
After this PR

Coverage increased (+0.2%) to 42.046% when pulling 3dbea5ddb92c66182c23e97ab78e485f7e54cc73 on bjornreppen:refresh into 24bc88c3a2485f9a54fc2474e857e42531c71874 on Artsdatabanken:master.


[Feature Request] Add support for SOCKS proxy

Support for sock4/socks5 proxy.

Does SOCKS not work with the current proxy setting?

Note: Insomnia uses curl to send requests to if curl supports is then it should be possible

Note: Insomnia uses curl to send requests to if curl supports is then it should be possible

I found only HTTP proxy in the perference GUI.
curl support socks5, just use:
all_proxy=sock5h://localhost:1080 curl -v www.google.com

Looks like socks4 aed socks5 are supported https://curl.haxx.se/libcurl/c/CURLOPT_PROXY.html
Did you get it working?

I can't even find a GUI option to specify socks proxy in insomnia. I can only see "HTTP Network Proxy" in Application -> Preferences -> General. And there is nothing like "SOCKS Network Proxy" there.
I'm using Insomnia v6.0.1 on debian buster/sid.

That's what I meant. You should be able to put your socks url in there if curl supports it

Correct me if I'm wrong, but it appears that the HTTP section will route only http traffic through the proxy, and HTTPS section will only route https traffic. So if i wanted to route both HTTPS and HTTP traffic, i would need to set both fields to the socks proxy, like this:

Perhaps a UI change could help explain that any of the proxy options here would work: https://curl.haxx.se/libcurl/c/CURLOPT_PROXY.html. Something like a tooltip next to each of the proxy parameters or a link to documentation about supported proxy types would be helpful.

I think that should work. I can't actually remember why I split the config up into HTTP/HTTPS. Probably because that's the way Paw or Postman did it or because MacOS splits the proxy configuration in that way as well.
So did that configuration work for you? I can update the tooltip help text if so.

Just for reference the suggested config worked.

Just for reference the suggested config worked.

What are the different between socks5 and socks5h?

What are the different between socks5 and socks5h? Apology a little bit off-topic!

socks5h = The name of the server you want to connect to is resolved (DNS) by the proxy
socks5 = The name of the server you want to connect to is resolved by your local device

Thank you @xpac1985

reopening because, as far as I can tell, we didn't want the stalebot to close it (we've since removed the stalebot altogether because of similar problems)

hi @dimitropoulos 👋 , I believe this issue is resolved: insomnia supports socks5 proxies via the methods described above: https://github.com/Kong/insomnia/issues/1085#issuecomment-432664923

ahh, gotcha.  thanks!

a melhor solução é usar socks5h://localhost:8080
no meu caso funcionou que foi uma blz. Obrigado pessoal pela ajuda. Deus abençoe vocês.

They should really add this to the documentation.


Get trade.id

How to get trade id(APM) in java spring boot ?
Thank you.

You can use our public API for this purpose.
We typically use GitHub issues for verified bugs, enhancement requests etc.
For general questions, please use our forum instead.


Add bevy wayland feature

Adding this allows the editor UI to work better under wayland without weird xwayland rendering glitches / issues.
This partially fixes the issues in #91 since fullscreen windows now render correctly. The pane glitching is not fixed by this tho

If wayland support is ready for prime-time then we should enable it in bevy by default, and I think we should not enable it here until then

Can I enable the feature just for myself locally somehow? Since xwayland (without this feature flag) bevy is completely borked and borderline unusable

I don't think that's particularly possible. I agree that this is annoying, but I'm also nervous to turn this on locally 🤔

From what I've seen is that in wayland is already enabled by default on the dev branch. So it really doesn't make sense to not already enable it since it works better than xwayland

It's not enabled yet, if it was it would be enabled here too because we are on bevy's main branch

Maybe this is a good opportunity to dogfood it? If users say this is better than not enabling it, I think that merging this is the right call.

I suppose enabling it here would have a manageable impact. I checked and it seems to run fine for me on Wayland with the feature enabled, so I'm cool with enabling it here :)


CMS pages should not be dead ends

There are several pages referencing the CMS, which no longer exists.
https://www.apache.org/dev/cmsadoption.html
includes a link to replacements, but others are dead ends:
https://www.apache.org/dev/cms.html
https://www.apache.org/dev/cmsref.html
https://www.apache.org/dev/cmstest.html
https://www.apache.org/dev/cmstestnotoc.html
These pages should also point to replacements, rather than be a dead end.
Perhaps redirect all the pages to a single page which contains the history and and links to replacements.

+1 to redirecting to a page that briefly explains that the ASF CMS has been replaced and points to the new options. I suppose the canonical URL for those new options is https://infra.apache.org/project-site.html

These pages all have a link to useful information now.
On Mon, Jul 3, 2023 at 5:53 AM Bertrand Delacretaz @.***>
wrote:

+1 to redirecting to a page that briefly explains that the ASF CMS has
been replaced and points to the new options. I suppose the canonical URL
for those new options is https://infra.apache.org/project-site.html
—
Reply to this email directly, view it on GitHub
https://github.com/apache/www-site/issues/234#issuecomment-1617659045,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC3RFXI55E2TMQ2RVWV5YXLXOKCBXANCNFSM6AAAAAAZ4D7M2A
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
Andrew Wetmore
Editor, Moose House Publications https://moosehousepress.com
Editor-Writer, The Apache Software Foundation https://apache.org


Logging in local time

Is it possible to log using local time instead of GMT?

I used a custom layout to log in local time.
http://stackoverflow.com/questions/43992460/logging-in-local-time-in-metrolog/43993585#43993585


Add Automated Testing (and more tests)

We current have 5 broken test (out of a total of 46 tests).  My goal is that we should be able to automate any test that don't interact with a client via Travis on each pr. The tests you have written is very clean so will be easy to adapt them to pytest (thanks!) at the same time I'll fix the rest you have listed here.
If it's any interesting you can track my progress there https://github.com/Hellowlol/plexapi/tree/responses

This is great.  I'm worried about all these branches already.  Feel like I should merge the sphinx stuff in already since it's not really affecting much and we can get docs progressively better as we move forward.

So my initial plan blowed up.. Testing was well under way but i was testing against im own library. Only the responses from pms was over 150mb... I have added a droplet and make a test account for plex. Im gonna send you a friends later. I know nothing about linux so it might take a while xD

Is this on a Digital Ocean node? We should also look into adding Travis CI next? I have a Travis page here, but never used it myself.  I'll figure it out this week or so. -- https://travis-ci.org/mjs7231/python-plexapi

Yes, its running in a Cheap droplet

I got the first test passing in Python 2.7 and Python 3.5 on Travis CI. I'd love to make the rest work. Things we need.

A more extensive library of movies.
Configuration for test movie, shows, etc. I'm not sure if we can drop a configuration file on Travis CI, but we could easily put those into environment variables as well. See variables below.
A way to test client interactions.  Maybe we can spin up a second Digital Ocean image running Gnome or something with Plex Home Theater on it.  Or maybe we omit client and playback testing for now.

[testing]
show_section = TV Shows
show_title = Game of Thrones
show_season = Season 1
show_episode = Winter Is Coming
movie_section = Movies
movie_title = Jurassic World
movie_foreign = Bedside Detective
audio_section = Music
audio_artist = Beastie Boys
audio_album = Licensed To Ill
audio_track = Brass Monkey
photo_section = Photos
photo_album = 2015-12-12 - Family Photo for Christmas card
client = pkkid-home
client_baseurl = http://<IP_ADDRESS>:3005

Possibly worth a try, but Travis may be able to install PHT itself.
http://craigthomas.ca/blog/2014/05/26/travis-ci-and-gui-testing/
https://docs.travis-ci.com/user/installing-dependencies/

I have like 60 test or so that passes to so far. :) I suggest we drop client for now. You can run the tests I'll send you the token, username and password to the account. I intent to test everything so we cache regression bugs.

This is awesome, I'm excited. :man_dancing:

I sent you a mail now. If i ever get enough linux skills ill give you access to the droplet too. There is atleast be 1 tests that fail. I did that on purpose to i know where i was :P

So we have 64 passing tests atm. The pr is starting to get huge. I wanted to add hub and write tests to this to but ill hold off until this is merged.

Closing! We have automated testing now! Thanks so much for the work on this! :+1:


Added missing metrics to default metrics allowlist

This will add the missing metrics that were listed from the issue: #8853, into the default metric allowlist. For issue: #11130, we need to add these metrics to ensure that all OOTB rules and metrics are being evaluated correctly.
Currently, we have:

126 metrics present in the metrics allow-list
135 metrics missing from the metrics allow-list

In order to prevent having a large number of metrics within this list, we will need to determine which metric we need to include/exclude from the allow list. Because adding a ton of metrics will be very expensive.

any impact on the performance? Could you list the number of timeseries for those metrics? Thanks

 Metrics Time Series Tables

#
Metric Name
Time Series

1
aggregator_unavailable_apiservice
219

2
aggregator_unavailable_apiservice_count
0

3
alertmanager_cluster_members
3

4
alertmanager_config_hash
3

5
alertmanager_config_last_reload_successful
3

6
apiserver_client_certificate_expiration_seconds_bucket
585

7
apiserver_client_certificate_expiration_seconds_count
39

8
apiserver_request:burnrate1d
1

9
apiserver_request:burnrate1h
1

10
apiserver_request:burnrate2h
1

11
apiserver_request:burnrate3d
1

12
apiserver_request:burnrate5m
1

13
apiserver_request:burnrate6h
1

14
apiserver_request:burnrate30m
1

15
cco_credentials_requests_conditions
5

16
cluster:alertmanager_routing_enabled:max
1

17
cluster_feature_set
1

18
cluster_version_available_updates
1

19
coredns_health_request_duration_seconds_bucket
102

20
coredns_panic_count_total
6

21
etcd_http_failed_total
0

22
etcd_http_received_total
0

23
etcd_http_successful_duration_seconds_bucket
0

24
etcd_network_peer_round_trip_time_seconds_bucket
102

25
etcd_network_peer_sent_failures_total
3

26
etcd_server_has_leader
3

27
grpc_client_handled_total
33

28
grpc_client_started_total
34

29
grpc_server_handled_total
2261

30
grpc_server_handling_seconds_bucket
150

31
grpc_server_started_total
133

32
haproxy_up
2

33
http_request_duration_seconds_bucket
165

34
http_request_duration_seconds_count
11

35
image_registry_operator_storage_reconfigured_total
1

36
kubelet_node_name
6

37
kubelet_pod_worker_duration_seconds_bucket
144

38
kubeproxy_sync_proxy_rules_duration_seconds_bucket
96

39
kubeproxy_sync_proxy_rules_last_queued_timestamp_seconds
0

40
kubeproxy_sync_proxy_rules_last_timestamp_seconds
6

41
kube_daemonset_status_current_number_scheduled
15

42
kube_daemonset_status_number_available
15

43
kube_daemonset_status_number_misscheduled
15

44
kube_daemonset_updated_number_scheduled
15

45
kube_deployment_metadata_generation
54

46
kube_deployment_spec_replicas
54

47
kube_deployment_status_observed_generation
54

48
kube_deployment_status_replicas_available
54

49
kube_deployment_status_replicas_updated
54

50
kube_hpa_spec_max_replicas
0

51
kube_hpa_status_current_replicas
0

52
kube_hpa_status_desired_replicas
0

53
kube_job_failed
0

54
kube_job_spec_completions
1

55
kube_job_status_succeeded
1

56
kube_node_info
6

57
kube_node_spec_taint
3

58
kube_node_status_allocatable
42

59
kube_node_status_capacity
42

60
kube_poddisruptionbudget_status_desired_healthy
2

61
kube_poddisruptionbudget_status_expected_pods
2

62
kube_pod_container_status_last_terminated_reason
2232

63
kube_pod_container_status_restarts_total
372

64
kube_pod_container_status_waiting_reason
2604

65
kube_pod_status_phase
1140

66
kube_pod_status_ready
684

67
kube_statefulset_metadata_generation
2

68
kube_statefulset_replicas
2

69
kube_statefulset_status_current_revision
2

70
kube_statefulset_status_observed_generation
2

71
kube_statefulset_status_replicas
2

72
kube_statefulset_status_replicas_ready
2

73
kube_statefulset_status_replicas_updated
2

74
kube_statefulset_status_update_revision
2

75
kube_state_metrics_list_total
27

76
kube_state_metrics_watch_total
27

77
mapi_current_pending_csr
1

78
mapi_machine_created_timestamp_seconds
6

79
mapi_mao_collector_up
2

80
mapi_max_pending_csrv
1

81
mcd_drain
6

82
mcd_kubelet_state
6

83
mcd_pivot_err
6

84
mcd_reboot_err
6

85
prometheus_notifications_queue_capacity
2

86
node_filesystem_files
54

87
node_filesystem_files_free
54

88
node_filesystem_readonly
54

89
node_md_disks
0

90
node_md_disks_required
0

91
node_network_receive_errs_total
195

92
node_network_transmit_errs_total
195

93
node_network_up
195

94
node_nf_conntrack_entries
6

95
node_nf_conntrack_entries_limit
6

96
node_quantile:kubelet_pleg_relist_duration_seconds:histogram_quantile
18

97
node_textfile_scrape_error
6

98
node_timex_offset_seconds
6

99
node_timex_sync_status
6

100
openshift_samples_degraded_info
1

101
openshift_samples_failed_imagestream_import_info
76

102
openshift_samples_invalidconfig_info
1

103
openshift_samples_invalidsecret_info
2

104
openshift_samples_retry_imagestream_import_total
0

105
openshift_samples_tbr_inaccessible_info
1

106
prometheus_notifications_queue_length
2

107
prometheus_config_last_reload_successful
2

108
prometheus_notifications_alertmanagers_discovered
2

109
prometheus_notifications_errors_total
6

110
prometheus_notifications_sent_total
6

111
prometheus_operator_list_operations_failed_total
3

112
prometheus_operator_list_operations_total
3

113
prometheus_operator_node_address_lookup_errors_total
1

114
prometheus_operator_reconcile_errors_total
3

115
prometheus_operator_watch_operations_failed_total
3

116
prometheus_operator_watch_operations_total
3

117
prometheus_remote_storage_failed_samples_total
0

118
prometheus_remote_storage_highest_timestamp_in_seconds
2

119
prometheus_remote_storage_queue_highest_sent_timestamp_seconds
0

120
prometheus_remote_storage_shards_desired
0

121
prometheus_remote_storage_shards_max
0

122
prometheus_remote_storage_succeeded_samples_total
0

123
prometheus_rule_evaluation_failures_total
116

124
prometheus_rule_group_iterations_missed_total
116

125
prometheus_target_scrapes_sample_duplicate_timestamp_total
2

126
prometheus_target_scrapes_sample_out_of_order_total
2

127
prometheus_tsdb_compactions_failed_total
2

128
prometheus_tsdb_head_samples_appended_total
2

129
prometheus_tsdb_reloads_failures_total
2

130
template_router_reload_failure
2

131
thanos_querier_store_apis_dns_failures_total
2

132
thanos_querier_store_apis_dns_lookups_total
2

133
time()-cluster_version_operator_update_retrieval_timestamp_seconds
1

134
vector
0

any impact on the performance? Could you list the number of timeseries for those metrics? Thanks

@clyang82 I have listed the time series above.

@dislbenn
for the performance impact, is there a spread sheet which contains the number of time series data for each metrics, for both regular cluster and SNO, similar as https://docs.google.com/spreadsheets/d/1PsmFuGhAiAUY0qrmO6cLsHYYqeVptcb-_iqSbijCWdE/edit?ts=6074f041#gid=0?

@dislbenn
for the performance impact, is there a spread sheet which contains the number of time series data for each metrics, for both regular cluster and SNO, similar as https://docs.google.com/spreadsheets/d/1PsmFuGhAiAUY0qrmO6cLsHYYqeVptcb-_iqSbijCWdE/edit?ts=6074f041#gid=0?

Please try this link: https://docs.google.com/spreadsheets/d/1VUnWd-dcutYAVbZIgYmflxvcIJRKTjC6hR36k_T1C_8/edit#gid=1030587416

@dislbenn today: @randymgeorge @marcolan018 @subbarao-meduri had a long discussion on this. We agreed that for now (point in time statement), we are not going to add more metrics related to the alerts OOTB (except for the ALERTS metric themselves). The reason is 2 fold:

customer can easily add it if they need to after the install
there is memory and storage impact on the Hub for metrics being added. and we want to inform the customer about cost of adding metrics so that they can better decide.


Output tensors as arguments to TT C++ Ops

Output tensors as arguments to TT C++ Ops
Model 1

Linear
Softmax
NLLLoss
SGD
Argmax
ElemwiseBinary/ELEMWISE_BINARY_EQ
Typecast
Sum

Model 2

BatchedMatmul
ElemwiseBinary/ELEMWISE_BINARY_ADD
ElemwiseBinary/ELEMWISE_BINARY_ADDALPHA
ElemwiseBinary/ELEMWISE_BINARY_MUL
ElemwiseUnary/ELEMWISE_UNARY_ADD
ElemwiseUnary/ELEMWISE_UNARY_ASSIGN
ElemwiseUnary/ELEMWISE_UNARY_DIV
ElemwiseUnary/ELEMWISE_UNARY_EXP
ElemwiseUnary/ELEMWISE_UNARY_FILL
ElemwiseUnary/ELEMWISE_UNARY_FILLZERO
ElemwiseUnary/ELEMWISE_UNARY_MUL
ElemwiseUnary/ELEMWISE_UNARY_POW
ElemwiseUnary/ELEMWISE_UNARY_SQRT
ElemwiseUnary/ELEMWISE_UNARY_TANH
Layernorm
Linear
Matmul
Softmax
AdamW
Arange
ClipGradNorm
ElemwiseTernary/ELEMWISE_TERNARY_ADDCDIV
ElemwiseTernary/ELEMWISE_TERNARY_ADDCMUL
Embedding
GenerateRandomBitMask
NLLLoss
NLLLossMeanPre
NLLLossUnreduced
Repeat
RepeatBackward
Sum
Typecast
Where
DropoutScaling
Groupnorm
MaskedFill
Prod
Tril

closing this one as dup to #5044

@muthutt please sync on infra with @arakhmati and @eyonland


Fix test failure in VcrServer

Fix this test failure
https://github.com/linkedin/ambry/actions/runs/6710513633/job/18235864159

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (0204b54) 33.33% compared to head (f502e8a) 17.00%.

Additional details and impacted files
@@              Coverage Diff              @@
##             master    #2638       +/-   ##
=============================================
- Coverage     33.33%   17.00%   -16.34%
+ Complexity     5114     2884     -2230
=============================================
  Files           806      806
  Lines         65339    65339
  Branches       7963     7963
=============================================
- Hits          21781    11109    -10672
- Misses        41861    53411    +11550
+ Partials       1697      819      -878

see 245 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Please don't remove the dark theme, because it will make it harder to read large block of code.

The title pretty much says what needed to be said. Having a white background with different coloured text can make thing extremely hard to read and can do more harm to your eyes than having a black (or dark grey) background with different coloured text makes it far easier to read.

@Danielx64 can you please explain what exactly you are concerned about. We don't have any plans to remove the dark theme.

@Danielx64 can you please explain what exactly you are concerned about. We don't have any plans to remove the dark theme.

There's this issue (https://github.com/microsoft/vscode/issues/87341 ) asking for dark theme to be removed.

Is this even one more layer of trolling?

Is this even one more layer of trolling?

This issue, no, it was a big concern till @dbaeumer stated that they have no plans to remove the dark theme.

r/woooosh

We are not removing the dark theme, sorry for the confusion.


Refactoring random to ParcelsRandom class

This implements #873. Note that this renaming of the random function is not backward-compatibel; users can choose two ways to adapt their code

Change
- from parcels import random
+ from parcels import ParcelsRandom as random

Change
- from parcels import random
+ from parcels import ParcelsRandom

and rename all calls to random functions to ParcelsRandom

On my list - scheduled for Thursday morning


llext-edk: rework, add Python export and more optional information

When building several different EDKs, there's currently no way to avoid mistaking one for another. The goal of this PR is to add metadata to a generated EDK so that the target board / SOC / CPU can be retrieved and checked by downstream projects.
An additional Python-compatible output format is provided for projects that do not use CMake or make.
To implement the above, a number of internal refactors with minimal visible effect have been implemented, with the goal of having more maintainable and extendable code:

the EDK output commands have been refactored into generic functions that take the target file type as a parameter;
flag processing has been made target-agnostic by using placeholders that are expanded in the output functions.

LLEXT EDK documentation has been updated accordingly.
EDIT: updated after review notes.

v3, incorporating @tejlmand notes:

Bash is now Python :slightly_smiling_face:
The list of exported variables is static and considerably reduced
Both the code and the documentation clearly state the added variables reflect Zephyr internals and no stability guarantees are implied.

@tejlmand can you please revisit this? Thanks!

v3, incorporating @tejlmand notes:
* Bash is now Python 🙂

* The list of exported variables is static and considerably reduced

* Both the code and the documentation clearly state the added variables reflect Zephyr internals and no stability guarantees are implied.

Thanks, but before going into details again on this one, then I have opened #79118 as promised.
I know we currently still have the CMake and Makefile export, but I was thinking that it could be beneficial to cover the Python export functionality you need by expanding the schema with the extra info by using the according build_info() function where needed.
This will also move knowledge / ever growing list of settings away from top-level CMakeLists.txt and closer to where the vars are actually defined and used (and thus reducing maintenance on those).
Later we can then update CMake / makefile generation to actually use the information from the build info infrastructure instead of having to keep track of this manually, but that I would take ast a later stage.
Please take a look at #79118 in relation to this PR and give your initial thoughts.
:smile:


chore: add currently learning section

this section will show what I am currently learning and I can always update and delete completed tasks from the list

Resolved issue: https://github.com/akebu6/akebu6/commit/d8e072216421094285637fb5c887edbce05c930d


fix svg for safari browser

calc is not very well supported in safari browsers
fixes #3

Thanks for contributing, can you attach some screenshots of svg card

sure, here it is


Fixed East/West Coordinates

East/West seems to be in the wrong direction, that costed me atleast half and hour of Debugging :D

This messes up the AutoTile, bc it uses the directions. Decide if you want to keep it or change everywhere.

Silly me, I am sorry for that blunder. I think it would be best to fix it :P


[Spool] Actual implementation

This PR is a continuation of https://github.com/apache/pinot/issues/14495 and the next step on https://github.com/apache/pinot/issues/14196.
While previous PRs were focused the machinery to find the common stages and how to replace them in the plan, this one is focused on sending these plans to the servers and how servers deal with them.
The main change is that now send operator may need to send to multiple stages. That implies a change in the protocol, which I made backward compatible by deprecating the old attribute and adding a new one that is repeated. A deprecated attribute can still be used and reserves the id in protobuf. Servers still recognize the old attribute (required in case a new server talks with an old broker) but they first try to read the new attribute (which will be null/empty if sent by an old broker) and in case it is empty, use the old attribute.
To understand the change in the operators is important to understand the topology used by BlockExchange and Mailbox. Mailboxes receive blocks and send them to exactly one worker. They could send the block through memory or GRPC. BlockExchanges are the ones that decide how to distribute the block between different mailboxes. For example BroadcastExchange send the block to all Mailboxes while RandomExchange sends the block to a random mailbox.
With the multi-sender operators we need to send to broadcast the blocks to multiple stages, which they may need to apply another distribution for each worker. What this PR does is to create a new layer of BlockExchanges when a sender is multi-sender. The root of this layer is always a standard BroadcastExchange, but it sends to a new type of SendingMailbox: A BlockExchangeSendingMailbox. This new mailbox is just an adaptor pattern that wraps a BlockExchange and shows it as a SendingMailbox. The BlockExchanges used in this second layer is the one normally used for each stage. Remember that this distribution must the same for all stages in the same multi-sender.
As an example of how it works, you can run the following in ColocatedJoinEngineQuickStart
SET useSpools = true;
explain implementation plan for
select * from userAttributes as a1
join userGroups as a2
on a1.userUUID = a2.userUUID
join userAttributes as a3
on a1.userUUID = a3.userUUID
limit 10

which returns:
[0]@<IP_ADDRESS>:46155|[0] MAIL_RECEIVE(BROADCAST_DISTRIBUTED)
├── [1]@<IP_ADDRESS>:44265|[0] MAIL_SEND(BROADCAST_DISTRIBUTED)->{[0]@<IP_ADDRESS>:46155|[0]} (Subtree Omitted)
├── [1]@<IP_ADDRESS>:34477|[1] MAIL_SEND(BROADCAST_DISTRIBUTED)->{[0]@<IP_ADDRESS>:46155|[0]} (Subtree Omitted)
├── [1]@<IP_ADDRESS>:44185|[2] MAIL_SEND(BROADCAST_DISTRIBUTED)->{[0]@<IP_ADDRESS>:46155|[0]} (Subtree Omitted)
└── [1]@<IP_ADDRESS>:34303|[3] MAIL_SEND(BROADCAST_DISTRIBUTED)->{[0]@<IP_ADDRESS>:46155|[0]}
    └── [1]@<IP_ADDRESS>:34303|[3] SORT LIMIT 10
        └── [1]@<IP_ADDRESS>:34303|[3] MAIL_RECEIVE(HASH_DISTRIBUTED)
            ├── [2]@<IP_ADDRESS>:44265|[0] MAIL_SEND(HASH_DISTRIBUTED)->{[1]@<IP_ADDRESS>:37717|[3],[1]@<IP_ADDRESS>:43409|[1],[1]@<IP_ADDRESS>:43851|[2],[1]@<IP_ADDRESS>:46503|[0]} (Subtree Omitted)
            ├── [2]@<IP_ADDRESS>:34477|[1] MAIL_SEND(HASH_DISTRIBUTED)->{[1]@<IP_ADDRESS>:37717|[3],[1]@<IP_ADDRESS>:43409|[1],[1]@<IP_ADDRESS>:43851|[2],[1]@<IP_ADDRESS>:46503|[0]} (Subtree Omitted)
            ├── [2]@<IP_ADDRESS>:44185|[2] MAIL_SEND(HASH_DISTRIBUTED)->{[1]@<IP_ADDRESS>:37717|[3],[1]@<IP_ADDRESS>:43409|[1],[1]@<IP_ADDRESS>:43851|[2],[1]@<IP_ADDRESS>:46503|[0]} (Subtree Omitted)
            └── [2]@<IP_ADDRESS>:34303|[3] MAIL_SEND(HASH_DISTRIBUTED)->{[1]@<IP_ADDRESS>:37717|[3],[1]@<IP_ADDRESS>:43409|[1],[1]@<IP_ADDRESS>:43851|[2],[1]@<IP_ADDRESS>:46503|[0]}
                └── [2]@<IP_ADDRESS>:34303|[3] SORT LIMIT 10
                    └── [2]@<IP_ADDRESS>:34303|[3] JOIN
                        ├── [2]@<IP_ADDRESS>:34303|[3] MAIL_RECEIVE(HASH_DISTRIBUTED)
                        │   ├── [3]@<IP_ADDRESS>:44265|[0] MAIL_SEND(HASH_DISTRIBUTED)[PARTITIONED]->{[2]@<IP_ADDRESS>:46503|[0]} (Subtree Omitted)
                        │   ├── [3]@<IP_ADDRESS>:34477|[1] MAIL_SEND(HASH_DISTRIBUTED)[PARTITIONED]->{[2]@<IP_ADDRESS>:43409|[1]} (Subtree Omitted)
                        │   ├── [3]@<IP_ADDRESS>:44185|[2] MAIL_SEND(HASH_DISTRIBUTED)[PARTITIONED]->{[2]@<IP_ADDRESS>:43851|[2]} (Subtree Omitted)
                        │   └── [3]@<IP_ADDRESS>:34303|[3] MAIL_SEND(HASH_DISTRIBUTED)[PARTITIONED]->{[2]@<IP_ADDRESS>:37717|[3]}
                        │       └── [3]@<IP_ADDRESS>:34303|[3] JOIN
                        │           ├── [3]@<IP_ADDRESS>:34303|[3] MAIL_RECEIVE(HASH_DISTRIBUTED)
spool here ->           │           │   ├── [4]@<IP_ADDRESS>:44185|[1] MAIL_SEND(HASH_DISTRIBUTED)->{[2]@<IP_ADDRESS>:37717|[3],[2]@<IP_ADDRESS>:43409|[1],[2]@<IP_ADDRESS>:43851|[2],[2]@<IP_ADDRESS>:46503|[0],[3]@<IP_ADDRESS>:37717|[3],[3]@<IP_ADDRESS>:43409|[1],[3]@<IP_ADDRESS>:43851|[2],[3]@<IP_ADDRESS>:46503|[0]} (Subtree Omitted)
                        │           │   └── [4]@<IP_ADDRESS>:44265|[0] MAIL_SEND(HASH_DISTRIBUTED)->{[2]@<IP_ADDRESS>:37717|[3],[2]@<IP_ADDRESS>:43409|[1],[2]@<IP_ADDRESS>:43851|[2],[2]@<IP_ADDRESS>:46503|[0],[3]@<IP_ADDRESS>:37717|[3],[3]@<IP_ADDRESS>:43409|[1],[3]@<IP_ADDRESS>:43851|[2],[3]@<IP_ADDRESS>:46503|[0]}
                        │           │       └── [4]@<IP_ADDRESS>:44265|[0] PROJECT
                        │           │           └── [4]@<IP_ADDRESS>:44265|[0] TABLE SCAN (userAttributes) null
                        │           └── [3]@<IP_ADDRESS>:34303|[3] MAIL_RECEIVE(HASH_DISTRIBUTED)
                        │               ├── [5]@<IP_ADDRESS>:44185|[1] MAIL_SEND(HASH_DISTRIBUTED)->{[3]@<IP_ADDRESS>:37717|[3],[3]@<IP_ADDRESS>:43409|[1],[3]@<IP_ADDRESS>:43851|[2],[3]@<IP_ADDRESS>:46503|[0]} (Subtree Omitted)
                        │               └── [5]@<IP_ADDRESS>:44265|[0] MAIL_SEND(HASH_DISTRIBUTED)->{[3]@<IP_ADDRESS>:37717|[3],[3]@<IP_ADDRESS>:43409|[1],[3]@<IP_ADDRESS>:43851|[2],[3]@<IP_ADDRESS>:46503|[0]}
                        │                   └── [5]@<IP_ADDRESS>:44265|[0] PROJECT
                        │                       └── [5]@<IP_ADDRESS>:44265|[0] TABLE SCAN (userGroups) null
                        └── [2]@<IP_ADDRESS>:34303|[3] MAIL_RECEIVE(HASH_DISTRIBUTED)
spool here ->               ├── [4]@<IP_ADDRESS>:44185|[1] MAIL_SEND(HASH_DISTRIBUTED)->{[2]@<IP_ADDRESS>:37717|[3],[2]@<IP_ADDRESS>:43409|[1],[2]@<IP_ADDRESS>:43851|[2],[2]@<IP_ADDRESS>:46503|[0],[3]@<IP_ADDRESS>:37717|[3],[3]@<IP_ADDRESS>:43409|[1],[3]@<IP_ADDRESS>:43851|[2],[3]@<IP_ADDRESS>:46503|[0]} (Subtree Omitted)
                            └── [4]@<IP_ADDRESS>:44265|[0] MAIL_SEND(HASH_DISTRIBUTED)->{[2]@<IP_ADDRESS>:37717|[3],[2]@<IP_ADDRESS>:43409|[1],[2]@<IP_ADDRESS>:43851|[2],[2]@<IP_ADDRESS>:46503|[0],[3]@<IP_ADDRESS>:37717|[3],[3]@<IP_ADDRESS>:43409|[1],[3]@<IP_ADDRESS>:43851|[2],[3]@<IP_ADDRESS>:46503|[0]}
                                └── [4]@<IP_ADDRESS>:44265|[0] PROJECT
                                    └── [4]@<IP_ADDRESS>:44265|[0] TABLE SCAN (userAttributes) null

TODO:

[x] Fix queries (right now this query return an empty result, which is incorrect).
[x] Automatic tests

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 0.00%. Comparing base (59551e4) to head (6658753).
Report is 1362 commits behind head on master.

:exclamation:  There is a different number of reports uploaded between BASE (59551e4) and HEAD (6658753). Click for more details.
HEAD has 48 uploads less than BASE

Flag
BASE (59551e4)
HEAD (6658753)

integration
7
2

integration2
3
2

temurin
12
2

java-21
7
2

skip-bytebuffers-true
3
1

skip-bytebuffers-false
7
1

unittests
5
0

unittests1
2
0

java-11
5
0

unittests2
3
0

integration1
2
0

custom-integration1
2
0

Additional details and impacted files
@@              Coverage Diff              @@
##             master   #14507       +/-   ##
=============================================
- Coverage     61.75%    0.00%   -61.76%
=============================================
  Files          2436        3     -2433
  Lines        133233        6   -133227
  Branches      20636        0    -20636
=============================================
- Hits          82274        0    -82274
+ Misses        44911        6    -44905
+ Partials       6048        0     -6048

Flag
Coverage Δ

custom-integration1
?

integration
0.00% <ø> (-0.01%)
:arrow_down:

integration1
?

integration2
0.00% <ø> (ø)

java-11
?

java-21
0.00% <ø> (-61.63%)
:arrow_down:

skip-bytebuffers-false
0.00% <ø> (-61.75%)
:arrow_down:

skip-bytebuffers-true
0.00% <ø> (-27.73%)
:arrow_down:

temurin
0.00% <ø> (-61.76%)
:arrow_down:

unittests
?

unittests1
?

unittests2
?

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests
JS Bundle Analysis - Avoid shipping oversized bundles

I think this PR is ready to review

We have some tests that verify that, but in different files. For example:

pinot-query-planner/src/test/resources/queries/ExplainPhysicalPlans.json verifies the plan.
pinot-query-runtime/src/test/resources/queries/Spool.json verifies the result.

TBH there is no test verifying with the plan that spools are used AND the result is correct (ie comparing with h2), although the query in these two cases is the same.


Issue with 502 Bad Gateway and 499 Errors on /api/jobs/<job_id>/preview Endpoint

Actions before raising this issue

[X] I searched the existing issues and did not find anything similar.
[X] I read/searched the docs

Steps to Reproduce
I am experiencing persistent issues with the /api/jobs/<job_id>/preview endpoint in my CVAT setup. The following are the details:
All system was deployed on google cloud cluster of kubernetes, this worked very well during two weeks of hard labelling and export very very heavy weight annotations zip on google cloud storage (I love cvat after that, exceeded all my expectations) but I had an issue with a PVC inside of cluster and after resolve that I cross with this error and I can't resolve.
Error:
When I tried to preview image on jobs tab or inside a job has similar errors

Environment:
CVAT version: [Include your CVAT version or Docker image tag, e.g., cvat/server:latest]
Deployment: Kubernetes
Backend: NGINX, Uvicorn (Unix socket at /tmp/uvicorn.sock)
Issue Details:
When attempting to preview data for a specific job (e.g., /api/jobs/2/preview), I receive a 502 Bad Gateway from the server.
Additionally, the NGINX logs show frequent 499 errors, which indicate the client is closing the connection prematurely.
Log Snippets:
NGINX Access Log:
<IP_ADDRESS> - - [30/Nov/2024:21:02:17 +0000] "GET /api/jobs/2/preview?org= HTTP/1.1" 499 0 "https://preventapp.site/jobs" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36"
Backend Response when accessed directly via Unix socket:
bash
curl -v --unix-socket /tmp/uvicorn.sock http://localhost/api/jobs/2/preview?org=

Connected to localhost (/tmp/uvicorn.sock) port 80 (#0)

GET /api/jobs/2/preview?org= HTTP/1.1
Host: localhost
User-Agent: curl/7.81.0
Accept: /
<
< HTTP/1.1 401 Unauthorized
< content-type: application/vnd.cvat+json
< {"detail":"Authentication credentials were not provided."}
NGINX Error Log:
lua

Permission Listing for Relevant Directories:
Folders for job data are created successfully after new task:
shell
$ ls -l /home/django/data/data/2
drwxrwxrwx 2 django django 4096 Nov 30 20:15 compressed
drwxrwxrwx 2 django django 4096 Nov 30 20:15 original
drwxrwxrwx 2 django django 4096 Nov 30 20:15 raw
Permissions for /tmp/uvicorn.sock (adjusted manually):
shell
$ chmod 777 /tmp/uvicorn.sock
$ ls -l /tmp/uvicorn.sock
srwxrwxrwx 1 django django 0 Nov 30 20:42 /tmp/uvicorn.sock
Steps Taken:
Increased proxy_read_timeout, proxy_send_timeout, and proxy_connect_timeout in nginx.conf.
Verified that /tmp/uvicorn.sock exists and is accessible.
Adjusted client_max_body_size in nginx.conf.
Tested backend response directly with curl (401 Unauthorized).
Confirmed permissions for directories and files in /home/django/data.
Expected Behavior:
The /api/jobs/<job_id>/preview endpoint should return a valid preview for the given job instead of resulting in a 502 Bad Gateway.
Questions:
Is there a specific CVAT image tag or version where this issue is addressed?
Are there additional configurations required to fix the 502 Bad Gateway or 499 errors?
Could the manual permission adjustments for /tmp/uvicorn.sock be related to this issue?
Any guidance or suggestions to resolve this issue would be greatly appreciated!
Expected Behavior
No response
Possible Solution
No response
Context
No response
Environment
No response

Any logs from the server pod?


Feature - Expose database connection string args

That s good to me.
However I am in the middle of a big refactoring of taipy-config. Please let me merge the PR when my PR is ready.

I did merge your code into taipy-core. I close the PR.


installing apps fails, need to update instructions

just got a new pop os machine.
I followed the instructions and went to flathub to install apps but cilcking the install button just downloads a flatpakref
After some googling I found I had to run this:  $ sudo apt install gnome-software-plugin-flatpak
Why isn't this in your instructions???  A new user can't even install apps!!

You probably mean, https://flatpak.org/setup/Pop!_OS as these are the only pop os instructions "we" have.
The correct repo would be https://github.com/flatpak/flatpak.github.io/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc


contextType: convenience API for reading context in a class

View formatted RFC
Note: I just wrote up the RFC. The semantics were designed by @sebmarkbage.

context.Consumer is essentially a proxy for Context, correct? i.e. static contextType can be a consumer. I ask because it would be nice if packages can export their context consumer, but keep the provider private.

import { Consumer } from "some-package";
class Button extends React.Component {
  static contextType = Consumer;
}

prevContext was removed from componentDidUpdate in v16, with the recommendation to store the previous context value on the class instance. Will this be the same recommendation for contextType or will prevContext be brought back?

class Button extends React.Component {
  static contextType = context;
  componentDidMount() {
    this.prevContext = this.context;
  }
  componentDidUpdate() {
    if (this.context !== this.prevContext) {
      // ...
    }
  }
}

ya this is awesome! supporting multiple contexts would be really nice as well, but i see how that would be harder. I would say that if it was feasible it may be worth doing, our apps are more and more looking like withFoo(withBar(Component)) for relay, react-router, react-intl etc.

I'm in favor of not doing anything.

Aren't classes slowly going to get phased out?

subscribing to only one context is actually easy with the  component. Subscribing to multiple contexts is what's annoying in vanilla react but this spec doesn't change that.

We can easily write a connectToContexts([Context1, Context2], (value1, value2) => ({ value1, value2 })  kind of helper today.

This seems difficult to type without React specific hacks in flow/TS.

context.Consumer is essentially a proxy for Context, correct? i.e. static contextType can be a consumer. I ask because it would be nice if packages can export their context consumer, but keep the provider private.

No, we discourage using Consumer for anything other than a render prop. It accidentally is the same object as context today but we’re going to start warning about this. I’ll write up a better explanation next week for why this makes sense. But for now please export Context from libraries directly.

prevContext was removed from componentDidUpdate in v16, with the recommendation to store the previous context value on the class instance. Will this be the same recommendation for contextType or will prevContext be brought back?

This componentDidUpdate argument is already taken by the snapshot so I don’t think we’ll bring it back. Storing it manually still works though.

our apps are more and more looking like withFoo(withBar(Component)) for relay, react-router, react-intl etc.

We have something in the works that helps with this. Will likely post an RFC next week.

Aren't classes slowly going to get phased out?

Even if classes become less relevant we still plan to support them for the observable future. Speeding up the adoption of new context is a high priority which makes this worth the redundancy compromise to us.

This seems difficult to type without React specific hacks in flow/TS.

I don’t see why, can you explain more?

If I'm understanding correctly, you would no longer need to initialize Context outside the class with this change. Is that correct or is that considered an anti-pattern?

If I'm understanding correctly, you would no longer need to initialize Context outside the class with this change. Is that correct or is that considered an anti-pattern?

This change is just a shortcut for ; you still need a matching  somewhere above.

It's great, but!
class Button extends React.Component {
  static contextType = ThemeContext; // Put this here

  render() {
    const theme = this.context; // Then you can use this here
    ...
  }
}

Binding the context through static field always perceived as something alien in React. I hope there is less strange way to do this. E.g.:
class Button extends ThemeContext.Component { // <---
  render() {
    const theme = this.context;
    ...
  }
}

@AlexGalays Okay got it. Still a big fan of the change

@strayiker The API for multiple contexts would be much worse if you did it w/ inheritance.

@mAAdhaTTah Totally agree. But I assume that this RFC for simplest case with single context.

Sounds really cool! I'd also love to see support for multiple contexts if we can agree on an intuitive API.
What about something like this?
class Foo extends React.Component {
  static contextTypes = {
    theme: ThemeContext,
    route: RouteContext
  }

  render() {
    const theme = this.context.theme;
    const route = this.context.route;
  }
}

@cangoektas contextTypes is reserved by the old context api

No, we discourage using Consumer for anything other than a render prop. It accidentally is the same object as context today but we’re going to start warning about this. I’ll write up a better explanation next week for why this makes sense after I get back from React Conf. But for now please export Context from libraries directly.

I'm probably missing some context :smirk: that you'll cover in your explanation. My understanding of the context/context.Consumer parity issue was (based on https://github.com/facebook/react/pull/13829) that the context could be used as an element and that properties could be chained off of the consumer a la context.Consumer.Provider.
As far as actual design goes, this.context would be read only (like the consumer), right? Again, I'm probably missing some context, but I personally would prefer for static contextType to be a consumer, not the full context.

I'd also love to see support for multiple contexts if we can agree on an intuitive API.

It would cause us to allocate intermediate objects on every render. This is too expensive and brings back some of the problems with the legacy context API. Such as making it difficult to type statically.

observedBits is no longer a thing?

It still is but also still unstable. Not an official API and we don't know yet if it will be official.
This particular RFC doesn't include support for it, you'd need to still  use Consumer.

That’s a good point

@pshrmn Thats good feedback. One consideration is that we don’t want to necessarily keep too many concepts and object allocations around by default. It’s also a common useful pattern to allow shadowing contexts to be able to work around issues.
As a library author I’m sympathetic to constraining it in certain use cases too. So if we start with the full context we still have the option to add the ability to pass a Consumer too. That way you can just think of the whole context as a thing but libraries can expose write only versions of those things.
So I think we can actually get what you want without blocking this RFC as a first step.

I want nothing to do with the context API.  Calling other stuff "legacy" is BS.  Not being able to pass int he store directly from my tests is complete BS. WTF @gaearon what are you and the React team doing over there?

Ah so all the people who don't use shallow thumbs down my last post.  Got it.
So, are you going to try to phase out the ability to send store in directly to components in the future like Redux just did?  If you're thinking about it stop.  Many of us test with shallow specifically by passing props directly which is how we actually TDD.  And it's not just a matter of "find another way", it's going to break all our tests as well as we have many benefits we gain by passing in store from tests.

BS: https://github.com/facebook/react/pull/13728 give me a break.

Could you please clarify - what exactly is broken here? What does not work anymore or would be broken in a future?
Could you provide some code you are(were) happy about, and not happy after this change?
I also a shallow-rendering follower, but I could not see any obstacles due to this RFC.

I'm very concerned with the direction Facebook has been going in regards to ignoring isolated testing.  We're already seeing Redux make changes such as outlined here.  The changes that are going to cause friction for many devs are devs who are testing React components shallowly and it does not make sense to have to use something like provider in our tests.  But the way React is going with requiring stuff like Context API in the future, and possibly doing the same (I hope not) which is to prevent being able to pass a store as a prop from shallow tests really limits devs who want to still continue to test in isolation, small focused tests which are easy to maintain and where we do want to be able to pass in simple stores (dummies) for direct testing not through mount and the Provider API.
We have ways we test where we do not need that heaviness in our tests.  Vue supports shallow tests.  I just don't want to see React go so far that we can't shallow anymore.  It's already getting hard to shallow with promoting so many wrapping and nested components, as well as now we're starting to get totally coupled to having to use provider in our tests and mount.  We don't all want that.

Personally I am trying to solve this puzzle as a puzzle.

limited depth components, you may confidently test with mount
and extend providing values for slots in the integration component, you may test with shallow

Today React broke your way to code and test, better to say - your taste or smell. But it's not about React, but about your own code, your way to write it (more about DI/mocking stuff than the code itself).
The real problem here is only one, and it's not related to this issue, it just how it is - enzyme is not a part of React, while behavior of react-test-renderer is not acceptable by majority. And does not contain shallow renderer at all (which is not a problem for limited-depth component).


AMBARI-26194: Ambari host page action button can't work

What changes were proposed in this pull request?
Change prop 'data-toggle' to 'data-bs-toggle', add class to remove caret.
Before:

After:

How was this patch tested?
Manual test.
mvn -T 2C -am test -pl ambari-web -Dmaven.artifact.threads=10 -Drat.skip

I deployed a cluster with your patch ,it indeed resolved, thanks!


Thanks for your work. I tried training it on the monocular endoscopy dataset EndoSALM, but the results were poor.

The color images of the dataset are 320*320, as follows:

The real depth images of the dataset are saved in 32-bit .png format, as follows:

The data loader I wrote is as follows:

My evaluation results were very bad, and the results are as follows:

What do you think is the reason? I changed max_depth to 100

Hi, I haven't worked on such dataset. What is the actual range of your ground-truth? Maybe 100 is too large for your dataset.

嗨，我还没有处理过这样的数据集。您的真实值的实际范围是多少？也许 100 对于您的数据集来说太大了。

Thanks for your reply. The actual range of my data set is 0-100mm. The unit of your code parameter is meter. How should I change it appropriately?
Thanks again for your quick reply.

If the range is 0-100mm, please make sure that your evaluation code can correctly deal with this range.

Where do I need to change the evaluation code to ensure that my code can handle it correctly?
I ran test_simole.py and the results were not good. I used the pre-trained weights of ImageNet from your lite-mono-small, whose input size is 640192, and my data is 320320. Will this affect the training results?

As you can see here the MIN and MAX are defined in the evaluation code. It can be a problem if your actual ground-truth is not in this range.
Any input size is compatible with the pretrained ImageNet weights.

正如您在这里看到的，MIN 和 MAX 在评估代码中定义。如果实际的 ground-truth 不在此范围内，则可能会出现问题。
任何输入大小都与预训练的 ImageNet 权重兼容。

I have changed it there.I think it's a problem with the training effect. But I don't know what causes the poor training effect.

如果您的相机内在是正确的...训练期间的曲线和可视化效果如何？您是否使用 tensorboard 检查过它们？

The training curve changes are as follows:

The visualization effect is as follows:

The visualization looks not bad. But your evaluation results are totally bad. I think the problem is still from your dataset. I saw several papers using Lite-Mono for endoscopy depth estimation and they reported good results.

可视化效果看起来还不错。但是你的评估结果完全糟糕。我认为问题仍然出在你的数据集上。我看到几篇使用 Lite-Mono 进行内窥镜深度估计的论文，它们报告了良好的结果。

OK. I am using the public EndoSLAM dataset, so it should be fine. Maybe there is something wrong with the loader I use to process the data. Can you tell me the title of the paper?

https://scholar.google.com/scholar?hl=en&as_sdt=2005&sciodt=0%2C5&cites=6869562733583933958&scipsc=1&q=endoscopy&btnG=

Thanks for your help.

You are welcome. Please update if you find the reason.

You are welcome. Please update if you find the reason.

OK


Change traces page duration progress bar to a ring icon

a11y requirements make the trace progress bar problematic. A potential replacement is to replace the progress bar with an icon.
Looks pretty good to me. Hopefully no a11y issues? 🙏 Has a benefit of being in the duration column so it's obvious what it's for. Some people either didn't notice the progress bar or didn't know what it meant.
Screenshot:

Thoughts?
The PR code is hacky. If we like this then I'll clean it up.
Microsoft Reviewers: Open in CodeFlow

Why is the FluentProgressRing component not being used? I would strongly suggest using it.
Overall, I do like this idea
fyi: you can do a quick accessibility pass using Accessibility Insights for web

Why is the FluentProgressRing component not being used? I would strongly suggest using it.

It doesn't have a way to change the stroke width, i.e. the thickness of the circle. It doesn't look good when it is a small size.
And it doesn't support completing the remainder of the circle with another color. Many rows have a small dot of purple which doesn't make sense.

@vnbaaij are these improvements possible? I see these properties are configurable in other fluent ui wrappers

We can style most of the FluentProgressRing ourselves as is. This is with the FluentProgressRing and just giving a color to the rest of the ring. I didn't change the stroke width. I think it looks ok.

Better. I think it looks better with a thicker line.
How about sticking with custom SVG for now, and if Fluent UI adds an option in the future for changing the stroke width, then we switch to FluentProgressRing?

Created a feature request for the FluentUI folks: https://github.com/microsoft/fluentui-blazor/issues/1113

We can get close to what you've got with just CSS. It's a little chunkier than yours because we can't change the viewbox, but this is 4px stroke width like yours:

::deep fluent-progress-ring::part(background) {
    stroke: var(--neutral-fill-input-alt-active);
    stroke-width: 4px;
    r: 6px;
}

::deep fluent-progress-ring::part(determinate) {
    stroke-width: 4px;
    r: 6px;
}

We do get a bunch of aria attributes with the FluentProgressRing that'll be helpful for accessibility... just need to add a title attribute and it'll pass, I think. But I'm fine either way. Just trying to provide options.

Updated to use progress ring control.

We can get close to what you've got with just CSS. It's a little chunkier than yours because we can't change the viewbox, but this is 4px stroke width like yours:

This CSS seems correct, but the Value no longer corresponds to the result. For example, 50% no longer displays progress at 50% 😀 You need to add stroke-dashoffset.

Thanks, I see it's definitely off when I hardcode 25%, 50% and 75% values.
I don't think there is a constant stroke-dashoffset that works for all values. It is either too big or too small at 25% and 75%. Lower-level support is needed in the control.

In deed, I'm looking into the possibility of adding a FluentprogressRing.Stroke property, which would be an enumeration of the "normal", " large", " thin" type. This would simplify management of this value.

See https://github.com/microsoft/fluentui-blazor/issues/1113#issuecomment-1855902727

Will be included in the next release of FluentUI.Blazor lib.
See PR https://github.com/microsoft/fluentui-blazor/pull/1121


Add LinesTracker, improve ImageProcessor and fix PointsTracker

This PR introduces multiple changes,

Forces clang-format in files in src/Perception/src/PinHoleCamera.cpp and src/Perception/tests/Features/ArucoDetectorExample.cpp
Fixes bug in PointsTracker class and improves the PointsTrackerTest (See https://github.com/dic-iit/kindyn-vio/issues/10#issuecomment-888268130 for results).
Adds LinesTracker class and LinesTrackerTest and relevant modifications to the composing class ImageProcessor. (See https://github.com/dic-iit/kindyn-vio/issues/11#issuecomment-889095082 for results). The LinesTracker class uses OpenCV's FastLineDetector for detecting lines and KLT tracker for tracking.

cc @traversaro @S-Dafarra let me know if it's ok to merge into master directly or if you would be interested in a quick review?
Closes #11.

cc @traversaro @S-Dafarra let me know if it's ok to merge into master directly or if you would be interested in a quick review?

Feel free to merge directly for me. I can look at the PRs even after it has been merged.

cc @traversaro @S-Dafarra let me know if it's ok to merge into master directly or if you would be interested in a quick review?

I think it is up to you. Which kind of review would you prefer? :grin:

cc @traversaro @S-Dafarra let me know if it's ok to merge into master directly or if you would be interested in a quick review?

I think it is up to you. Which kind of review would you prefer?

A very high-level review on readability of the code would be sufficient, at this stage.

Ubuntu CI failure due to GTSAM, unrelated to the changes in this PR. macOS CI passed. I proceed with merging.


Update README.md

The debian 9.5 builder has been down for 3 weeks.  Remove it until such time as it is able to build again.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

CC: @shahmishal

@swift-ci please smoke test


Package request: plex-desktop

Project description
Streaming media player for Plex
Metadata

homepage URL: https://www.plex.tv/fr/media-server-downloads/#plex-app
source URL: https://snapcraft.io/plex-desktop
license: proprietary
platforms: linux

Unfortunately, this app is only available as a Snap or a Flatpak. It looks like Snap is easier to unpack, as we have one example with Spotify.
There is also an AUR package, which appears to be unmaintened.

would also appreciate this being packaged, the flatpak version does not start for me ( I don't like using flatpak anyways).

It also supports Darwin and Windows.

Just to be clear this is not this package
https://github.com/NixOS/nixpkgs/blob/nixos-23.11/pkgs/applications/video/plex-media-player/default.nix#L47
This is a completely different package with different build steps that just looks the exact same.

Submitted a draft PR that adds this to nixpkgs. What's there now works on my machine™ (3 of them). I'd appreciate people testing this out on different hardware and suggesting any improvements that makes this more reliable. I have a couple more things I'd like to do before officially submitting this.


Invoke-WebRequest hangs in some cases, unless -UseBasicParsing is used

Invoke-WebRequest hangs, 100% of the times, when processing webpages containing specific elements.
Several bug reports on this same topic have been opened on Microsoft Connect in 2014 and 2015 and Microsoft UserVoice later on, but since they have been filed on different platforms and with different topics, Microsoft failed to notice they were all referring to the same issue, so I am consolidating those reports and filing a bug report here on Github:
Steps to reproduce
$URL='http://windows.microsoft.com/en-US/windows-8/system-requirements'
(Invoke-WebRequest -Uri $URL).parsedhtml

other URLs to try:
https://github.com/hluk/CopyQ/releases
http://www.heise.de
http://www.bloomberg.com/professional/downloads/

Expected behavior
Invoke-Webrequest should parse the page and populate several properties, like
ParsedHtml
Links

and others.
Actual behavior
Invoke-WebRequest hangs, sometimes spitting out the message:
Vector smash protection is enabled
Environment data

Verified on PowerShell4 on Windows 8.1:
PSVersion                      4.0
WSManStackVersion              3.0
SerializationVersion           <IP_ADDRESS>
CLRVersion                     4.0.30319.34209
BuildVersion                   6.3.9600.16394
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0}
PSRemotingProtocolVersion      2.2

and PowerShell5 on Windows 10
PSVersion                      5.0.10586.494
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.10586.494
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

For sake of completeness, the abovementioned bug reports from UserVoice are reported here:
https://windowsserver.uservoice.com/forums/301869-powershell/suggestions/13890669--url-http-www-bloomberg-com-professional-down
https://windowsserver.uservoice.com/forums/301869-powershell/suggestions/11515881-invoke-webrequest-hangs-freeze-at-many-websites
https://windowsserver.uservoice.com/forums/301869-powershell/suggestions/15692703-invoke-webrequest-returned-object-hangs-when-acces

This incident needs to be submitted to the Windows UserVoice as this is for PowerShell Open Source.
But interesting enough, in PowerShell v6.0.0-alpha.13, in the (Invoke-WebRequest -Uri $URL) the property ".parsedhtml" doesn't exist.
OS = Windows 10 Insider Preview 14971
PS C:\Program Files\PowerShell\<IP_ADDRESS>> $PSVersionTable
Name                           Value

CLRVersion
SerializationVersion           <IP_ADDRESS>
PSRemotingProtocolVersion      2.3
PSEdition                      Core
WSManStackVersion              3.0
BuildVersion                   <IP_ADDRESS>
GitCommitId                    v6.0.0-alpha.13
PSVersion                      6.0.0-alpha
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
See attached images

Thanks for the quick reply
I had hope that what MS POSH could not do, PSOS could have accomplished :)
Alas, Microsoft does not listen very actively to bug reports :(

Hey @ilgrank , I understand.  The good thing about this is the contribution you provide. There are lots of MVP's looking at this all the time and we can (sort of) redirect the effort to where is needed.  You did Great in providing references to UserVoice posts.
Don't give us on us!  We'll do whatever we can to continue helping in improving PowerShell.
:)
Maximo Trinidad

Thanks @MaximoTrinidad , I really appreciate the effor of all the people here 👍
and of course I hope, as you say, that this will gather the interest of enough people for Microsoft to notice.
I also cross-referenced this issue on Uservoice, so that either side will know :)

Greatly Appreciated!
Max

This doesn't repro with PSCore as CoreCLR has a different web client class that doesn't exhibit the same behavior.

Hi @SteveL-MSFT : As @MaximoTrinidad  suggested some day ago, it seems that PSCore is lacking (among other things) the .AllElements and .ParsedHtml properties.
One of the greatest (IMHO of course) features of (MS) Invoke-WebRequest is the ability to parse web pages in order to return addressable object.
It is a very useful feature, and it is a shame PSCore is missing it :(

@ilgrank please open a separate issue for .allelements and .parsedhtml properties

Thanks @SteveL-MSFT
I opened a new issue here:

Are there any updates on this? Possible workaround?

-UseBasicParsing to avoid hang, the other issue above is to implement parsedhtml

Well, unfortunately, using the "-usebasicparsing" parameter removes the "forms" property from the returned object, thus making the workaround just that: a temporary non-solution.  This problem needs to be fixed.  It is shameful that Microsoft has not fixed this in over 2 years.  Shameful, microsoft.

Maybe useful for some people, but I found a way to work around the issue and have a useable html element:
Function ConvertTo-NormalHTML {
    param([Parameter(Mandatory = $true, ValueFromPipeline = $true)]$HTML)

    $NormalHTML = New-Object -Com "HTMLFile"
    $NormalHTML.IHTMLDocument2_write($HTML.RawContent)
    return $NormalHTML
}

It's a bit silly, but at least you can do something with the html.

Well, unfortunately, using the "-usebasicparsing" parameter removes the "forms" property from the returned object, thus making the workaround just that: a temporary non-solution. This problem needs to be fixed. It is shameful that Microsoft has not fixed this in over 2 years. Shameful, microsoft.

Yeah its pretty terrible.  I have a task on a server that runs an XML import file for Cisco Unified Messaging and it only runs once a month.  Looking at the history it has failed 88% over the past 8 months because of this very issue.


Control Module

Creating Control Module class and moving acceleration&velocity limiting functionalities of the Skill class to the CM

Code looks good! You basically just ported the code though; this should behave the exact same, which was not really the point.

Wasn't that the point? In my mind it was mostly an issue of something being done in the wrong place and moving that functionality. What was the point in your POV then?

Don't forget to fix your TODO's :). Also, I don't like the statics (surprise), but for now this is fine. We're unlikely to create more than one instance of the control module anyways.

Ah yeah, will do. Ill leave it as statics for now, maybe fix it later.


Cannot get oh-my-zsh completion plugins to work

I'm trying to get completions for several oh-my-zsh plugins, but can't get the completions to work.
I use the following line to install/configure vagrant for example:
zplug "plugins/vagrant", from:oh-my-zsh, nice:10

Which works fine in terms of installing, but I get no auto completion when entering vagrant <tab>
I tried playing with nice values and removing them, but it doesn't work.

Fixed. Please update zplug and try again!

Thanks! :trophy:


fix(concurrency): stop the transaction committer when the scheduler is done

This change is

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 78.61%. Comparing base (d924c79) to head (a1b8d05).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1989   +/-   ##
=======================================
  Coverage   78.61%   78.61%
=======================================
  Files          62       62
  Lines        8895     8895
  Branches     8895     8895
=======================================
  Hits         6993     6993
  Misses       1455     1455
  Partials      447      447

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@barak-b-starkware said his flow test got stuck in an infinite loop, so I tried to think of places where the scheduler might get stuck.
This is probably not the bug from Barak's flow test because his flow test does not use the method halt_scheduler, but it is still a bug.

crates/blockifier/src/concurrency/scheduler.rs line 31 at r1 (raw file):

            *self.commit_index_guard < self.scheduler.chunk_size,
            "The commit index must be less than the chunk size, since the scheduler is not done."
        );

Why do we need this assertion? It feels trivial/redundant. What do I miss here?
Code quote:
        assert!(
            *self.commit_index_guard < self.scheduler.chunk_size,
            "The commit index must be less than the chunk size, since the scheduler is not done."
        );


Ability to override neon-js' request timeout

Derived from https://github.com/CityOfZion/neo-js/issues/178

Changes are now in 0.11.0.


Feature : SeparatorType.title's Position, LTRB.

Hi there, Actually I am trying to show circular countdown in which I have used your Slide Coundown as the middle TimerText of Circle. The problem is SeparatorType.title shows on the right side of time only, which makes text go out of Circle if kept diameter less.
Is there any property that set SeparatorType.title position to Bottom, Up, or Left, I could not find any? As I have already used   durationTitle: DurationTitle.enShort(), but it will be nice feature if added.

fixed #49