Slower Performance in Latest Tesseract

Hi,
i have installed Tesseract: 4.00.00dev-690-g1b0379c with Leptonica:  1.74.4 and its working fine with the detection and all, but i have noticed that the performance is slower than before (comparing with 5 months ago tesseract, and leptonica 1.74.1).
in the past the time was around 4 or 5 seconds but lately its almost the double, that command that im using is the normal tesseract detection command which is: **tesseract image results -l lang--tessdata-dir ./tessdata --oem 1 ** , so am i missing something or is there some sort of a parameter that i should add after the updates to the tesseract or leptonica? or any other way to enhance  the performance speed? (for both single thread case or multi thread case)
Thank you

Slower Performance in Latest Tesseract

It's not clear if you comparing a newer 4.00 to older 4.00 or 4.00 to 3.05.

Also, do you use the newest traineddata?

Use traineddata files from tessdata_fast repository  for speed in
recognition.
ShreeDevi

भजन - कीर्तन - आरती @ http://bhajans.ramparivar.com
On Tue, Oct 17, 2017 at 9:00 PM, Amit D<EMAIL_ADDRESS>wrote:

Also, do you use the newest traineddata?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tesseract-ocr/tesseract/issues/1171#issuecomment-337266737,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE2_o_BlcoI0mWe0dClpPN5puFlZejciks5stMgKgaJpZM4P8Rw1
.

or any other way to enhance the performance speed? (for both single thread case or multi thread case)

If you use multi-threading  try disabling OpenMP.
OMP_THREAD_LIMIT=1 tesseract in.png out --oem 1
.

@amitdo actually im comparing the latest (4.00.00dev-690-g1b0379c with Leptonica: 1.74.4 ) with the older version (4.00.00dev-549-g2b854e3 with leptonica 1.74.1)
@Shreeshrii  "tessdata_fast" is a news to me, i'm already using the official traineddata, but i dont know about this one, can you please give me the link to it?, also i already created a tuned LSTM, can i also combine it with the new tessdata_fast as well?
Thank you both

The latest traineddata files are at https://github.com/tesseract-ocr/tessdata_best and https://github.com/tesseract-ocr/tessdata_fast.

Please see https://github.com/tesseract-ocr/tesseract/wiki/TrainingTesseract-4.00#lstmtraining-command-line
If you have the data for your finetuning, you can create the 'faster' integer type of traineddata by using
convert_to_int with stop_training.

@Shreeshrii so i assume that if i fine tuned an LSTM file it won't combine with the new traineddate?  (for example a traineddata from: https://github.com/tesseract-ocr/tessdata_best)
also you mean by "data for your fine tuning" as the following?

and the steps in the link that you have shared are to enhance accuracy, detection speed or both?
@stweil  the difference between "tessdata_best" and "tessdata_fast" is the accuracy vs speed? meaning "tessdata_fast" will be faster in detection but wont be accurate as "tessdata_best" ?
Thanks for the answers

the difference between "tessdata_best" and "tessdata_fast" is the accuracy vs speed? meaning "tessdata_fast" will be faster in detection but wont be accurate as "tessdata_best" ?

tessdata_fast is faster than tessdata_best, yes.
tessdata_best is generally better, but not always. I also noticed cases where tessdata_fast is better. And there are even cases where the old Tesseract gives the best recognition rates of all current tessdata.

if i wanted to fine tune using the tool

For training, you have to start with tessdata_best models. You can create
your traineddata in the integer faster format.
You will have to test with your language and data.
On 18-Oct-2017 7:28 PM, "ibr123"<EMAIL_ADDRESS>wrote:

if i wanted to fine tune using the tool
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tesseract-ocr/tesseract/issues/1171#issuecomment-337600169,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE2_oyx5CIz_10_spwJn3BbM-AvfinFUks5stgQXgaJpZM4P8Rw1
.

if i wanted to fine tune using the tool "lstmtraining" while i'm using the latest Tesseract: (4.00.00dev-690-g1b0379c) can i use .lstmf files (which are generated by tesstrain.sh)file that are created by older Tesseract version, such as (4.00.00dev-549-g2b854e3) ?
meaning are lstmf files compatible between tesseract versions?

You can give it a try. There have been significant changes, that break
compatibility between commits since this is development code in alpha stage.
If you get an error, you will have to recreate the lstmf files.
On 18-Oct-2017 7:34 PM, "ibr123"<EMAIL_ADDRESS>wrote:

if i wanted to fine tune using the tool "lstmtraining" while i'm using the
latest Tesseract: (4.00.00dev-690-g1b0379c) can i use .lstmf files (which
are generated by tesstrain.sh)file that are created by older Tesseract
version, such as (4.00.00dev-549-g2b854e3) ?
meaning are lstmf files compatible between tesseract versions?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tesseract-ocr/tesseract/issues/1171#issuecomment-337601903,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE2_o6UXEXXc9MEveLBjrtgdNMWPYbLNks5stgVbgaJpZM4P8Rw1
.

I do not know about the specific commit numbers you refer to. You may want
to check the github history of commits.
On 18-Oct-2017 7:39 PM, "ShreeDevi Kumar"<EMAIL_ADDRESS>wrote:

You can give it a try. There have been significant changes, that break
compatibility between commits since this is development code in alpha stage.
If you get an error, you will have to recreate the lstmf files.
On 18-Oct-2017 7:34 PM, "ibr123"<EMAIL_ADDRESS>wrote:

if i wanted to fine tune using the tool "lstmtraining" while i'm using
the latest Tesseract: (4.00.00dev-690-g1b0379c) can i use .lstmf files
(which are generated by tesstrain.sh)file that are created by older
Tesseract version, such as (4.00.00dev-549-g2b854e3) ?
meaning are lstmf files compatible between tesseract versions?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tesseract-ocr/tesseract/issues/1171#issuecomment-337601903,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE2_o6UXEXXc9MEveLBjrtgdNMWPYbLNks5stgVbgaJpZM4P8Rw1
.

thanks


How to join the server.

I have setup the docker in hugging face, like in the instructions but can't figure out how to join the server.

 Click on it
You will see agent's ip, region and tunnel what ngrok made to connect to server. This is ip of server

Enter this ip as minecraft server's ip (without tcp://)
Play

I will add this to instructions


µstreamer fails to install

With a completely fresh install of rpios µstreamer fails to install correctly:
Cloning into 'ustreamer'...
remote: Enumerating objects: 188, done.
remote: Counting objects: 100% (188/188), done.
remote: Compressing objects: 100% (141/141), done.
remote: Total 188 (delta 66), reused 103 (delta 35), pack-reused 0
Receiving objects: 100% (188/188), 191.05 KiB | 2.39 MiB/s, done.
Resolving deltas: 100% (66/66), done.
WARNING! WARNING! WARNING!
Streamer has not been installed correctly.```

Looks like it was caused by https://github.com/pikvm/ustreamer/commit/3715c89ec8a5465d88ee672be28ad65c59c4599d ustreamer and ustreamer-dump are no longer created as links to ustreamer.bin and ustreamer-dump.bin.

me too

This is now fixed in 1.0.9.


Broken image links

Expected Behavior
Images should be visible.
Actual Behavior
Images are not visible due to broken links.

Section that requires update
All images on this page.
Additional information
I think this is due to a bug introduced during Gatsby to Hugo migration.
I have made a PR which fixes this.
Note that such edits are needed for each page in the worker docs.

This is included in #3689


[examples] Update core_input_gamepad example

Relaxes the detection criteira so any compatible gamepad can get detected/displayed on the example. Currently it's too restrictive to those three specific strings, which leaves lots of compatible gamepads (ref) appearing as if they were not supported.
Examples of compatible gamepads that appear unsupported on the example: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, etc.

@asdqwe thanks for the review.


Build and publish artifacts against Java 17

Spring Boot 3 and Spring Framework 6 are baselined against Java 17

Resolved in #369


Servering C++ 编译失败

环境
docker images: paddlepaddle/paddle:latest-dev-cuda11.4.1-cudnn8-gcc82
复现
按照 如何编译PaddleServing文档，在 编译paddle-serving-server步骤中 make -j20 这一步出错.

编译时，设置了代理，可以从Github上拉取资源

错误信息
CMake Error at extern_paddle-stamp/download-extern_paddle.cmake:159 (message):
  Each download failed!

    error: downloading 'http://paddle-inference-lib.bj.bcebos.com/2.3.0-rc0/cxx_c/Linux/GPU//paddle_inference.tgz' failed
         status_code: 22
         status_string: "HTTP response code said error"
         log:
         --- LOG BEGIN ---
         Uses proxy env variable http_proxy == 'http://<IP_ADDRESS>:7890'
    Trying <IP_ADDRESS>:7890...

  TCP_NODELAY set

  Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 7890 (#0)

  GET
  http://paddle-inference-lib.bj.bcebos.com/2.3.0-rc0/cxx_c/Linux/GPU//paddle_inference.tgz
  HTTP/1.1

  Host: paddle-inference-lib.bj.bcebos.com

  User-Agent: curl/7.65.0

  Accept: */*

  Proxy-Connection: Keep-Alive

  Mark bundle as not supporting multiuse

  The requested URL returned error: 404 Not Found

  Closing connection 0

         --- LOG END ---
         error: downloading 'http://paddle-inference-lib.bj.bcebos.com/2.3.0-rc0/cxx_c/Linux/GPU//paddle_inference.tgz' failed
         status_code: 22
         status_string: "HTTP response code said error"
         log:
         --- LOG BEGIN ---
         Uses proxy env variable http_proxy == 'http://<IP_ADDRESS>:7890'
    Trying <IP_ADDRESS>:7890...

  TCP_NODELAY set

  Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 7890 (#0)

  GET
  http://paddle-inference-lib.bj.bcebos.com/2.3.0-rc0/cxx_c/Linux/GPU//paddle_inference.tgz
  HTTP/1.1

  Host: paddle-inference-lib.bj.bcebos.com

  User-Agent: curl/7.65.0

  Accept: */*

  Proxy-Connection: Keep-Alive

  Mark bundle as not supporting multiuse

  The requested URL returned error: 404 Not Found

  Closing connection 0

         --- LOG END ---
         error: downloading 'http://paddle-inference-lib.bj.bcebos.com/2.3.0-rc0/cxx_c/Linux/GPU//paddle_inference.tgz' failed
         status_code: 22
         status_string: "HTTP response code said error"
         log:
         --- LOG BEGIN ---
         Uses proxy env variable http_proxy == 'http://<IP_ADDRESS>:7890'
    Trying <IP_ADDRESS>:7890...

  TCP_NODELAY set

  Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 7890 (#0)

  GET
  http://paddle-inference-lib.bj.bcebos.com/2.3.0-rc0/cxx_c/Linux/GPU//paddle_inference.tgz
  HTTP/1.1

  Host: paddle-inference-lib.bj.bcebos.com

  User-Agent: curl/7.65.0

  Accept: */*

  Proxy-Connection: Keep-Alive

  Mark bundle as not supporting multiuse

  The requested URL returned error: 404 Not Found

  Closing connection 0

         --- LOG END ---
         error: downloading 'http://paddle-inference-lib.bj.bcebos.com/2.3.0-rc0/cxx_c/Linux/GPU//paddle_inference.tgz' failed
         status_code: 22
         status_string: "HTTP response code said error"
         log:
         --- LOG BEGIN ---
         Uses proxy env variable http_proxy == 'http://<IP_ADDRESS>:7890'
    Trying <IP_ADDRESS>:7890...

  TCP_NODELAY set

  Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 7890 (#0)

  GET
  http://paddle-inference-lib.bj.bcebos.com/2.3.0-rc0/cxx_c/Linux/GPU//paddle_inference.tgz
  HTTP/1.1

  Host: paddle-inference-lib.bj.bcebos.com

  User-Agent: curl/7.65.0

  Accept: */*

  Proxy-Connection: Keep-Alive

  Mark bundle as not supporting multiuse

  The requested URL returned error: 404 Not Found

  Closing connection 0

         --- LOG END ---
         error: downloading 'http://paddle-inference-lib.bj.bcebos.com/2.3.0-rc0/cxx_c/Linux/GPU//paddle_inference.tgz' failed
         status_code: 22
         status_string: "HTTP response code said error"
         log:
         --- LOG BEGIN ---
         Uses proxy env variable http_proxy == 'http://<IP_ADDRESS>:7890'
    Trying <IP_ADDRESS>:7890...

  TCP_NODELAY set

  Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 7890 (#0)

  GET
  http://paddle-inference-lib.bj.bcebos.com/2.3.0-rc0/cxx_c/Linux/GPU//paddle_inference.tgz
  HTTP/1.1

  Host: paddle-inference-lib.bj.bcebos.com

  User-Agent: curl/7.65.0

  Accept: */*

  Proxy-Connection: Keep-Alive

  Mark bundle as not supporting multiuse

  The requested URL returned error: 404 Not Found

  Closing connection 0

         --- LOG END ---
         error: downloading 'http://paddle-inference-lib.bj.bcebos.com/2.3.0-rc0/cxx_c/Linux/GPU//paddle_inference.tgz' failed
         status_code: 22
         status_string: "HTTP response code said error"
         log:
         --- LOG BEGIN ---
         Uses proxy env variable http_proxy == 'http://<IP_ADDRESS>:7890'
    Trying <IP_ADDRESS>:7890...

  TCP_NODELAY set

  Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 7890 (#0)

  GET
  http://paddle-inference-lib.bj.bcebos.com/2.3.0-rc0/cxx_c/Linux/GPU//paddle_inference.tgz
  HTTP/1.1

  Host: paddle-inference-lib.bj.bcebos.com

  User-Agent: curl/7.65.0

  Accept: */*

  Proxy-Connection: Keep-Alive

  Mark bundle as not supporting multiuse

  The requested URL returned error: 404 Not Found

  Closing connection 0

         --- LOG END ---

CMakeFiles/extern_paddle.dir/build.make:90: recipe for target 'third_party/Paddle/src/extern_paddle-stamp/extern_paddle-download' failed
make[2]: *** [third_party/Paddle/src/extern_paddle-stamp/extern_paddle-download] Error 1
CMakeFiles/Makefile2:487: recipe for target 'CMakeFiles/extern_paddle.dir/all' failed
make[1]: *** [CMakeFiles/extern_paddle.dir/all] Error 2
Makefile:129: recipe for target 'all' failed
make: *** [all] Error 2

日志中显示404错误，请问资源是否确定存在？

我遇到了同样的问题，请问解决了吗

I met the same question too. It seems that the file http://paddle-inference-lib.bj.bcebos.com/2.3.0-rc0/cxx_c/Linux/GPU/x86-64_gcc8.2_avx_mkl_cuda10.2_cudnn7.6.5_trt<IP_ADDRESS>/paddle_inference.tgz doesn't exist. Hoping to get help.

这个问题有大佬解决了吗？我也遇到这个问题了，好烦啊啊啊啊啊啊；能给出个解决办法吗


Display addresses as names if found

This pull request aims to convert Namada addresses to names where possible.
players.csv contains the top 4300 players (pilots and crew) in the Namada Shielded Expedition in the format name, address, public key.

Thanks for this. I may want to modify a little. But can you upload in a format that shows only diffs? Atm it seems everything is removed/replaced, so not suitable for review or merge.


remove redundant namespace qualifiers

@SimonCropp build is failing for some un-needed usings

@Evangelink on it


Suggest

Can user authentication be added?

I'm not against having it in the project, but won't be able to add it for at least a few days. If you'd like to send a PR, I'd welcome the addition!

I'm glad you can adopt this suggestion, and I can only wait because I don't have the ability to collaborate with you right now.

This functionality was added in #16.

Thanks

Merged in, finalizing things and should be able to do a rerelease soon.


Pinned items get reset

When you are logged out or hit reconfigure in settings the pinned items are all reset.  Some of our users report this happens frequently as well.

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

ID: 9a93be98-3e0a-2232-e862-fc8f6048a077
Version Independent ID: 1650400c-2ea4-80bd-7741-fa1e461f0ddc
Content: Pin your favorites in Dynamics 365 for phones and tablets
Content Source: ce/mobile-app/v8/go-mobile/get-started/pin-favorites.md
Service: crm-online
GitHub Login: @mduelae
Microsoft Alias: mkaur

Here's what I heard back.
Please contact this alias<EMAIL_ADDRESS>with the following details:
Which mobile client are they using? Version details? Any pattern, if they observed or is it just a random occurrence. Support team will be able to help.


Add git autopush option when committing (revisited) #62058

Issue #62058
I know that this issue is closed already, but I implemented a basic new feature (button) that commits and push, on the Source Control: Git. I don't know that this is needed but I think it is a great option.

I'll close this as this can be easily contributed as an extension to VS Code.


Mamba model bounty

I finished most of the model architecture code. Probably lots of bugs in forward pass though. I can use tinygrad functions for managing the weights. generate.py should be pretty easy to convert, but i still have work todo in mixin.py and mamba_simple.py
I will remove all the commented code once I am finished. Currently just using it as reference material.
Once I have everything completed should i merge it all into one file or keep the code in separate files?

I finished most of the model architecture code. Probably lots of bugs in forward pass though. I can use tinygrad functions for managing the weights. generate.py should be pretty easy to convert, but i still have work todo in mixin.py and mamba_simple.py
I will remove all the commented code once I am finished. Currently just using it as reference material.
Once I have everything completed should i merge it all into one file or keep the code in separate files?

What do i need to do in order to "lock" a bounty. I thought that it was just significant progress made towards the goal. I guess significant is subjective though.


Decoupling from RocketChat

This project is tightly coupled with RocketChat. It would be interesting to decouple it to make sure that other adapters can use it.

Would be cool, one way to do this is abstracting the adapter methods calls, in a lib file for example, where the methods could be switched according to the actual adapter in use.
Although would really need a closest watching about wich method exists and each adapter to maintain it bugless.
Today I think we are using the following rocketchat adapter's methods:

stream-notify-room
getUserRoles
livechat:transfer
livechat:saveInfo

And we're actually using some attributes from the response object, wich is generated in the adapter too, like res.envelope.user.roomType, res.robot.alias and res.robot.name. Probably would be wise to abstract that in some object too.


iOS HeightRequest does not work

After updating the plug-in to version 5.0.0, HTML is overlapping other stacks on iOS.
On Android, it works perfectly as before.
Previous version 5.0.0.alpha3
<pluginHTML:HtmlLabel Text="{Binding MensagemHTML}" HorizontalOptions="Fill" HeightRequest="100"/>
iOS:

Android:

@FelipeFC Take a look at #135. It seems that code added in Alpha4 is messing with layout of the text. Might be worth making a local build and removing the Setup() method.


[feat]  Add a shortcut to uninstall

Describe the problem
nsis,Now there is only one application shortcut in the start menu
Describe the solution you'd like
tauri Bundle
Alternatives considered
No response
Additional context
No response

I don't know if we want to add this feature, since most applications (at least the one I use) stopped shipping a shortcut for the uninstaller which is better IMO as it doesn't pollute the start menu.
I will still keep this issue open and see if more users desire this feature.
BTW, you can still access the uninstaller relatively easy by double clicking the app icon and selecting uninstall.


Create MOM6 Pan-Antarctic Regional configuration

Progress tracked in  mom6-panan

I don't understand this issue says that the progress is tracked in the repo?
It's a bit confusing. Seems like a resolved issue for me. Right?

Hmm, yeah, no idea. I'll close it. We have a panan config now!


fix: duplicate and old attestations aggregates

Motivation
Right now we are publishing old aggregates (slot -2) instead of the current (slot -1), also we publish several aggregates for the same subcommittee, this will be solved by this PR.
Description
This PR solves both issues explained in 1254, on one hand the old attestation (being slot - 2 the most recen attestation always) was due to picking the slot on ignore/2 from the store (slot - 1) instead of taking it from the current block (slot). For the second issue, duplications was due to a lacking of filtering in the block builder steps, as with sync committees, we need to group attestations by committee index and just keep the ones with the greatest pop count (the most amount of set bits)
Resolves #1254

Now we can see an small amount of attestations per block (previously we had 4/6 even with just one committee)

And we could also see that for a particular slot we have published the most recent attestation:


Content filter

Need ideas how to filter certain horrific inscriptions.
One person cannot do that, need various entities that can control the content on ordinals.com.
Also a quick search finds deepai.org/machine-learning-model/nsfw-detector
Related to https://github.com/casey/ord/issues/1447.
Somewhat related to https://github.com/casey/ord/issues/1477.

Original issue: https://github.com/casey/ord/issues/1465.
Closing...


Website Updated Popup

Pop-up in above image appears twice. Given there is no other action possible, ideal solutions in order would be

Only push updates to live at 4 am, no need for interference.
If there does need to be a refresh, just refresh rather than make me click a button.
Enable me to not refresh the page immediately, and save/ copy my work.

Resolved. When a new website version becomes available, a pop up will no longer appear, forcing the user to refresh the page. Instead, a simple notification message will appear in the app footer.


v-link is not accessible if component is imported

Hi,
Is there any reason why v-link could not be accessible if component is imported?
Console:
[Vue warn]: Failed to resolve directive: link

app.js:
import Vue from 'vue';
import VueRouter from 'vue-router';
import Page3 from './page3';

Vue.use(VueRouter);

const Page2 = Vue.extend({
  template: '<page3></page3>
Working link',
  components: {
    'page3': Page3,
  },
});

const Page1 = Vue.extend({
  template: '<page2></page2>
Working link',
  components: {
    'page2': Page2,
  },
});

const router = new VueRouter({});

router.map({
  '/': {
    name: 'page1',
    component: Page1,
  },
});

const App = Vue.extend({});
router.start(App, '#app');

page3.js (Failed to resolve directive: link):
import Vue from 'vue';

export default Vue.extend({
  template: 'Not working link',
});

app.html:
<!DOCTYPE html>

    <meta charset="utf-8" />
    <title></title>

        <router-view></router-view>

P.S.: is there any service like jsfiddle with browserify support?
Vue.js 1.0.0-beta.4, vue-router: 0.7.1

This is because for Page3, Vue.extend is called before Vue.use(VueRouter).
Vue.use(VueRouter) injects the necessary hooks for components to pick up the $route context.
The simple solution for now is to just export objects in your component modules. There's no need to call Vue.extend there anyway.
This is still somewhat confusing behavior, so I'll fix it in a later release.

The simplest solutions is to change order, but note if you are using babel you will have to use require as imports are hoisted (see https://github.com/babel/babel/issues/1371 for details).
import Vue from 'vue';
import VueRouter from 'vue-router';
import Page3 from './page3';

Vue.use(VueRouter);

const Page3 = require('./page3';);


fix CFGetSystemUptime for linux

The implementation of CFGetSystemUptime() for linux return incorrect values, which make NSThread.sleepForTimeInterval() behave incorrectly :

clock_gettime already return values in seconds and nano sec, there is no need to scale it by __CF1_TSRRate
tv_nsec must be divided<PHONE_NUMBER> to get seconds, not multiplied

good catch; __CF1_TSRRate is actually the cpu clock scale iirc which should have been 1 on linux targets.


Support for Multi-part Archives

I'm attempting to extract rar files that are multi-part (.rar .r01 r.02 etc). Using the unrar tools available out there, I just pass them a single file name (the .rar file) and they extract all the subsequent archives. I'm using archiver as a library and calling archiver.Rar.Open(file, path) then receive this error: writing file: rardecode: archive continues in next volume
Am I missing something, or is this support missing? Thanks!

Seems like support was added in #38 but later removed in #43. Basically OpenReader needs to be used in order to extract multi-part archives.


Installed testing function

Adds a small function (credit @loriab) which allows pytest to be run after a module has been installed as module.test(). This makes it a bit easier to run the tests instead of something like:
py.test -v `import module, os; os.path.abspath(os.path.dirname(module.__file__))`

Can't pytest already easily test an installed module from the command-line?
I think the syntax is:
py.test --pyargs package.module

such as
py.test --pyargs yank.tests.test_mpi

Or is the idea to be able to do this programmatically via a simple Python API?

I think the pyargs is fine for this. Closing.


Implement Floor Switch and Highlighting Gradient on FloorMapScreen

Idea Description
Add a switch to change the floor number on the FloorMapScreen, along with a gradient to make it stand out, as per the design on Figma. The task includes:

Implementing a switch that allows users to change the floor number.
Adding a gradient to highlight the floor switch.

The main goal is to replicate the design and functionality as shown in the provided design.
Reference images and links
https://www.figma.com/file/MbElhCEnjqnuodmvwabh9K/DroidKaigi-2023-App-UI?type=design&node-id=55876-19767&mode=dev

🙋

Thanks! Assigned


test: skip ostree-remount due to issue RHEL-25249

This pull request includes:
We suggest to skip ostree-remount playbook task due to issue https://issues.redhat.com/browse/RHEL-25249 also detected recently in RHEL-9.4
https://github.com/osbuild/rhel-edge-ci/actions/runs/8889962119/job/24409179382
https://github.com/osbuild/rhel-edge-ci/actions/runs/8889962119/job/24409179480

[ ] adequate testing for the new functionality or fixed issue
[ ] adequate documentation informing people about the change such as

[ ] submit a PR for the READMEs listed here
[ ] submit a PR for the osbuild.org website repository if this PR changed any behavior not covered by the automatically updated READMEs

Do we know if the issue is that the service actually fails?  As opposed to the log output being different (or silent), for example.


Add example SVG inputs

Would be useful to give an example usage of the tool, eg. with a button to generate some example input.

Added a few commits ago, you now have the option to add the markup for a 2 dimensional that was drawn from my other solar system project, for which this repo was conceived.
Thank you for your suggestion!


💡 [Feature]: Add a command to attach form customizer to view, add and edit form

🎯 Aim of the feature
We could add a new VS Code command which will under the hood use the CLI for Microsoft 365 m365 spo contenttype set to set the form customizer for a content type on a list.
When running the command it should prompt for the following:

siteUrl
listTitle
Edit form guide (when left empty should not update the edit form)
New form guide (when left empty should not update the new form)
View form guide (when left empty should not update the view form)

📷 Images (if possible) with expected result
No response
🤔 Additional remarks or comments
a script sample for inspiration

Can I work on this one?
If i'm correct, we should also prompt for the Content Type name 🤔

Can I work on this one?
If i'm correct, we should also prompt for the Content Type name 🤔

All yours.
Yes that is correct we should also prompt for content type name which we want to update


Bug: There is no local binary during make start

What happened?

There is no local binary during make start
Two scenarios：

Display successful startup status, but report an error during detection (detection script shows no startup)
Make start detects whether there are binaries locally, and if there are none locally, yes

What did you expect to happen?

Make start to determine whether the binary system is started and modify it based on its status
Scenario 2 can only make build first and then make start

How can we reproduce it (as minimally and precisely as possible)?
make start
Anything else we need to know?
No response
version

```console
$ {name} version
# paste output here
```

Cloud provider

OS version

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here
# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

Install tools

make start 添加一个逻辑， 检测是否执行过 make build 构建了二进制，如果发现没有构建，就先构建，再启动
make check 修复逻辑，按照真实的进程去检测

/accept


External curation teams to increase primary cell count to 30 million

Datasets published in  Q3/Q4:
https://cellxgene.cziscience.com/collections/0faa1af6-e504-4b88-a47b-69347e1bace5
https://cellxgene.cziscience.com/collections/793fdaec-5067-428a-a9db-ecefe135c945
https://cellxgene.cziscience.com/collections/d86517f0-fa7e-4266-b82e-a521350d6d36
https://cellxgene.cziscience.com/collections/d5cad3f0-56b6-4fbe-8f2b-be92a8c7820f
https://cellxgene.cziscience.com/collections/1a486c4c-c115-4721-8c9f-f9f096e10857
https://cellxgene.cziscience.com/collections/bd5230f4-cd76-4d35-9ee5-89b3e7475659
https://cellxgene.cziscience.com/collections/d36ca85c-3e8b-444c-ba3e-a645040c6185
https://cellxgene.cziscience.com/collections/b1a879f6-5638-48d3-8f64-f6592c1b1561
https://cellxgene.cziscience.com/collections/a48f5033-3438-4550-8574-cdff3263fdfd
https://cellxgene.cziscience.com/collections/f8057c47-fcd8-4fcf-88b0-e2f930080f6e
https://cellxgene.cziscience.com/collections/ff668d5d-5b3f-49ee-a007-ff0664bf35ec
https://cellxgene.cziscience.com/collections/0a77d4c0-d5d0-40f0-aa1a-5e1429bcbd7e
https://cellxgene.cziscience.com/collections/35d0b748-3eed-43a5-a1c4-1dade5ec5ca0
https://cellxgene.cziscience.com/collections/e33ffcd3-7cbf-4b8c-b0f4-85587ad5019a
https://cellxgene.cziscience.com/collections/6ff3401b-d72c-4940-a00c-3f0792397082
https://cellxgene.cziscience.com/collections/edb893ee-4066-4128-9aec-5eb2b03f8287
https://cellxgene.cziscience.com/collections/999f2a15-3d7e-440b-96ae-2c806799c08c
https://cellxgene.cziscience.com/collections/2d2e2acd-dade-489f-a2da-6c11aa654028
https://cellxgene.cziscience.com/collections/93eebe82-d8c3-41bc-a906-63b5b5f24a9d
https://cellxgene.cziscience.com/collections/8191c283-0816-424b-9b61-c3e1d6258a77
https://cellxgene.cziscience.com/collections/e75342a8-0f3b-4ec5-8ee1-245a23e0f7cb
https://cellxgene.cziscience.com/collections/17481d16-ee44-49e5-bcf0-28c0780d8c4a
https://cellxgene.cziscience.com/collections/de13e3e2-23b6-40ed-a413-e9e12d7d3910
https://cellxgene.cziscience.com/collections/b0cf0afa-ec40-4d65-b570-ed4ceacc6813
https://cellxgene.cziscience.com/collections/83ed3be8-4cb9-43e6-9aaa-3fbbf5d1bd3a
https://cellxgene.cziscience.com/collections/92fde064-2fb4-41f8-b85c-c6904000b859

From the collections listed above, we have reached 30 million primary cells.


Errors building smart screen sdk

Briefly summarize your issue:
While trying to make the alexa smart screen sdk (point 7.6 of https://developer.amazon.com/pt-BR/docs/alexa/alexa-smart-screen-sdk/ubuntu.html#step-7-build-the-alexa-smart-screen-sdk) it gives me an error.
What behavior are you observing?
When building the SDK it gives me this:
Creating the build directory for the AlexaModule with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
Creating the build directory for the CapabilityAgents with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the ApplicationUtilities with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
Creating the build directory for the Communication with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
Creating the build directory for the SmartScreenClient with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
Creating the build directory for the SampleApp with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
Creating the build directory for the Utils with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
-- Configuring done
-- Generating done
-- Build files have been written to: /home/utente/sdk_folder/ss-build
Scanning dependencies of target VisualCharacteristics
[  2%] Building CXX object modules/Alexa/SmartScreenCapabilityAgents/VisualCharacteristics/src/CMakeFiles/VisualCharacteristics.dir/VisualCharacteristics.cpp.o
[  4%] Linking CXX shared library libVisualCharacteristics.so
[  4%] Built target VisualCharacteristics
Scanning dependencies of target gmock_main
[  7%] Building CXX object modules/Alexa/ThirdParty/googletest-release-1.8.0/googlemock/CMakeFiles/gmock_main.dir/__/googletest/src/gtest-all.cc.o
[  9%] Building CXX object modules/Alexa/ThirdParty/googletest-release-1.8.0/googlemock/CMakeFiles/gmock_main.dir/src/gmock-all.cc.o
[ 11%] Building CXX object modules/Alexa/ThirdParty/googletest-release-1.8.0/googlemock/CMakeFiles/gmock_main.dir/src/gmock_main.cc.o
[ 14%] Linking CXX static library libgmock_main.a
[ 14%] Built target gmock_main
Scanning dependencies of target VisualCharacteristicsTest
[ 16%] Building CXX object modules/Alexa/SmartScreenCapabilityAgents/VisualCharacteristics/test/CMakeFiles/VisualCharacteristicsTest.dir/VisualCharacteristicsTest.cpp.o
[ 19%] Linking CXX executable VisualCharacteristicsTest
[ 19%] Built target VisualCharacteristicsTest
Scanning dependencies of target AlexaPresentation
[ 21%] Building CXX object modules/Alexa/SmartScreenCapabilityAgents/AlexaPresentation/src/CMakeFiles/AlexaPresentation.dir/AlexaPresentation.cpp.o
[ 23%] Linking CXX shared library libAlexaPresentation.so
[ 23%] Built target AlexaPresentation
Scanning dependencies of target AlexaPresentationTest
[ 26%] Building CXX object modules/Alexa/SmartScreenCapabilityAgents/AlexaPresentation/test/CMakeFiles/AlexaPresentationTest.dir/AlexaPresentationTest.cpp.o
[ 28%] Linking CXX executable AlexaPresentationTest
[ 28%] Built target AlexaPresentationTest
Scanning dependencies of target SmartScreenTemplateRunTime
[ 30%] Building CXX object modules/Alexa/SmartScreenCapabilityAgents/TemplateRuntime/src/CMakeFiles/SmartScreenTemplateRunTime.dir/TemplateRuntime.cpp.o
[ 33%] Linking CXX shared library libSmartScreenTemplateRunTime.so
[ 33%] Built target SmartScreenTemplateRunTime
Scanning dependencies of target TemplateRuntimeTest
[ 35%] Building CXX object modules/Alexa/SmartScreenCapabilityAgents/TemplateRuntime/test/CMakeFiles/TemplateRuntimeTest.dir/TemplateRuntimeTest.cpp.o
[ 38%] Linking CXX executable TemplateRuntimeTest
[ 38%] Built target TemplateRuntimeTest
Test project /home/utente/sdk_folder/ss-build/modules/Alexa
      Start  1: AlexaPresentationTest.testNullContextManagerInterface
 1/37 Test  #1: AlexaPresentationTest.testNullContextManagerInterface ......................   Passed    0.07 sec
      Start  2: AlexaPresentationTest.testNullFocusManagerInterface
 2/37 Test  #2: AlexaPresentationTest.testNullFocusManagerInterface ........................   Passed    0.02 sec
      Start  3: AlexaPresentationTest.testNullExceptionSender
 3/37 Test  #3: AlexaPresentationTest.testNullExceptionSender ..............................   Passed    0.02 sec
      Start  4: AlexaPresentationTest.testNullMessageSender
 4/37 Test  #4: AlexaPresentationTest.testNullMessageSender ................................   Passed    0.02 sec
      Start  5: AlexaPresentationTest.testUnknownDirective
 5/37 Test  #5: AlexaPresentationTest.testUnknownDirective .................................   Passed    0.02 sec
      Start  6: AlexaPresentationTest.testMalformedRenderDocumentDirective
 6/37 Test  #6: AlexaPresentationTest.testMalformedRenderDocumentDirective .................   Passed    0.02 sec
      Start  7: AlexaPresentationTest.testMalformedRenderDocumentDirective2
 7/37 Test  #7: AlexaPresentationTest.testMalformedRenderDocumentDirective2 ................   Passed    0.02 sec
      Start  8: AlexaPresentationTest.testMalformedExecuteCommandDirective
 8/37 Test  #8: AlexaPresentationTest.testMalformedExecuteCommandDirective .................   Passed    0.02 sec
      Start  9: AlexaPresentationTest.testMalformedExecuteCommandDirective2
 9/37 Test  #9: AlexaPresentationTest.testMalformedExecuteCommandDirective2 ................   Passed    0.02 sec
      Start 10: AlexaPresentationTest.testExecuteCommandAfterMismatchedAPLCard
10/37 Test #10: AlexaPresentationTest.testExecuteCommandAfterMismatchedAPLCard .............   Passed    0.02 sec
      Start 11: AlexaPresentationTest.testExecuteCommandAfterRightAPL
11/37 Test #11: AlexaPresentationTest.testExecuteCommandAfterRightAPL ......................***Not Run (Disabled)   0.00 sec
      Start 12: AlexaPresentationTest.testAPLClearCard
12/37 Test #12: AlexaPresentationTest.testAPLClearCard .....................................   Passed    1.03 sec
      Start 13: AlexaPresentationTest.testAPLTimeout
13/37 Test #13: AlexaPresentationTest.testAPLTimeout .......................................   Passed    1.03 sec
      Start 14: AlexaPresentationTest.testAPLIdleRespectsGUIActive
14/37 Test #14: AlexaPresentationTest.testAPLIdleRespectsGUIActive .........................   Passed    0.03 sec
      Start 15: AlexaPresentationTest.testAPLIdleRespectsGUIInactive
15/37 Test #15: AlexaPresentationTest.testAPLIdleRespectsGUIInactive .......................   Passed    0.53 sec
      Start 16: AlexaPresentationTest.testAPLIdleRespectsDialogUXWhenGUIInactive
16/37 Test #16: AlexaPresentationTest.testAPLIdleRespectsDialogUXWhenGUIInactive ...........   Passed    0.02 sec
      Start 17: AlexaPresentationTest.testAPLFollowedByAPL
17/37 Test #17: AlexaPresentationTest.testAPLFollowedByAPL .................................   Passed    0.53 sec
      Start 18: AlexaPresentationTest.testSendUserEvent
18/37 Test #18: AlexaPresentationTest.testSendUserEvent ....................................   Passed    0.02 sec
      Start 19: TemplateRuntimeTest.test_nullAudioPlayerInterface
19/37 Test #19: TemplateRuntimeTest.test_nullAudioPlayerInterface ..........................   Passed    0.02 sec
      Start 20: TemplateRuntimeTest.test_nullFocusManagerInterface
20/37 Test #20: TemplateRuntimeTest.test_nullFocusManagerInterface .........................   Passed    0.02 sec
      Start 21: TemplateRuntimeTest.test_nullExceptionSender
21/37 Test #21: TemplateRuntimeTest.test_nullExceptionSender ...............................   Passed    0.02 sec
      Start 22: TemplateRuntimeTest.test_renderInfoCardsPlayersAddRemoveObserver
22/37 Test #22: TemplateRuntimeTest.test_renderInfoCardsPlayersAddRemoveObserver ...........   Passed    0.02 sec
      Start 23: TemplateRuntimeTest.test_unknownDirective
23/37 Test #23: TemplateRuntimeTest.test_unknownDirective ..................................   Passed    0.02 sec
      Start 24: TemplateRuntimeTest.testSlow_renderTemplateDirective
24/37 Test #24: TemplateRuntimeTest.testSlow_renderTemplateDirective .......................   Passed   10.03 sec
      Start 25: TemplateRuntimeTest.test_handleDirectiveImmediately
25/37 Test #25: TemplateRuntimeTest.test_handleDirectiveImmediately ........................   Passed    0.03 sec
      Start 26: TemplateRuntimeTest.testSlow_renderPlayerInfoDirectiveBefore
26/37 Test #26: TemplateRuntimeTest.testSlow_renderPlayerInfoDirectiveBefore ...............   Passed   10.03 sec
      Start 27: TemplateRuntimeTest.test_renderPlayerInfoDirectiveAfter
27/37 Test #27: TemplateRuntimeTest.test_renderPlayerInfoDirectiveAfter ....................   Passed    0.02 sec
      Start 28: TemplateRuntimeTest.test_renderPlayerInfoDirectiveWithoutAudioItemId
28/37 Test #28: TemplateRuntimeTest.test_renderPlayerInfoDirectiveWithoutAudioItemId .......   Passed    0.02 sec
      Start 29: TemplateRuntimeTest.test_malformedRenderPlayerInfoDirective
29/37 Test #29: TemplateRuntimeTest.test_malformedRenderPlayerInfoDirective ................   Passed    0.02 sec
      Start 30: TemplateRuntimeTest.test_renderPlayerInfoDirectiveDifferentAudioItemId
30/37 Test #30: TemplateRuntimeTest.test_renderPlayerInfoDirectiveDifferentAudioItemId .....   Passed    0.02 sec
      Start 31: TemplateRuntimeTest.test_renderPlayerInfoDirectiveWithTwoProviders
31/37 Test #31: TemplateRuntimeTest.test_renderPlayerInfoDirectiveWithTwoProviders .........   Passed    0.02 sec
      Start 32: TemplateRuntimeTest.test_renderPlayerInfoDirectiveAudioStateUpdate
32/37 Test #32: TemplateRuntimeTest.test_renderPlayerInfoDirectiveAudioStateUpdate .........   Passed    0.02 sec
      Start 33: TemplateRuntimeTest.test_focusNone
33/37 Test #33: TemplateRuntimeTest.test_focusNone .........................................   Passed    0.02 sec
      Start 34: TemplateRuntimeTest.test_displayCardCleared
34/37 Test #34: TemplateRuntimeTest.test_displayCardCleared ................................   Passed    0.02 sec
      Start 35: TemplateRuntimeTest.test_reacquireChannel
35/37 Test #35: TemplateRuntimeTest.test_reacquireChannel ..................................   Passed    0.02 sec
      Start 36: TemplateRuntimeTest.testTimer_RenderPlayerInfoAfterPlayerActivityChanged
36/37 Test #36: TemplateRuntimeTest.testTimer_RenderPlayerInfoAfterPlayerActivityChanged ...   Passed    0.02 sec
      Start 37: VisualCharacteristicsTest.testGetCapabilityConfigurations
37/37 Test #37: VisualCharacteristicsTest.testGetCapabilityConfigurations ..................***Not Run (Disabled)   0.00 sec

100% tests passed, 0 tests failed out of 35

Total Test time (real) =  23.94 sec

The following tests did not run:
	 11 - AlexaPresentationTest.testExecuteCommandAfterRightAPL (Disabled)
	 37 - VisualCharacteristicsTest.testGetCapabilityConfigurations (Disabled)
[ 38%] Built target unit
Scanning dependencies of target Communication
[ 40%] Building CXX object modules/Alexa/ApplicationUtilities/Communication/src/CMakeFiles/Communication.dir/WebSocketServer.cpp.o
[ 42%] Building CXX object modules/Alexa/ApplicationUtilities/Communication/src/CMakeFiles/Communication.dir/WebSocketSDKLogger.cpp.o
[ 45%] Linking CXX shared library libCommunication.so
[ 45%] Built target Communication
Scanning dependencies of target SmartScreenClient
[ 47%] Building CXX object modules/Alexa/ApplicationUtilities/SmartScreenClient/src/CMakeFiles/SmartScreenClient.dir/SmartScreenClient.cpp.o
[ 50%] Building CXX object modules/Alexa/ApplicationUtilities/SmartScreenClient/src/CMakeFiles/SmartScreenClient.dir/EqualizerRuntimeSetup.cpp.o
[ 52%] Building CXX object modules/Alexa/ApplicationUtilities/SmartScreenClient/src/CMakeFiles/SmartScreenClient.dir/DeviceSettingsManagerBuilder.cpp.o
[ 54%] Linking CXX shared library libSmartScreenClient.so
[ 54%] Built target SmartScreenClient
Scanning dependencies of target SampleApp
[ 57%] Building CXX object modules/Alexa/SampleApp/src/CMakeFiles/SampleApp.dir/AplCoreConnectionManager.cpp.o
[ 59%] Building CXX object modules/Alexa/SampleApp/src/CMakeFiles/SampleApp.dir/AplCoreEngineSDKLogBridge.cpp.o
[ 61%] Building CXX object modules/Alexa/SampleApp/src/CMakeFiles/SampleApp.dir/AplCoreGuiRenderer.cpp.o
[ 64%] Building CXX object modules/Alexa/SampleApp/src/CMakeFiles/SampleApp.dir/AplCoreMetrics.cpp.o
[ 66%] Building CXX object modules/Alexa/SampleApp/src/CMakeFiles/SampleApp.dir/AplCoreTextMeasurement.cpp.o
[ 69%] Building CXX object modules/Alexa/SampleApp/src/CMakeFiles/SampleApp.dir/ConnectionObserver.cpp.o
[ 71%] Building CXX object modules/Alexa/SampleApp/src/CMakeFiles/SampleApp.dir/ConsolePrinter.cpp.o
[ 73%] Building CXX object modules/Alexa/SampleApp/src/CMakeFiles/SampleApp.dir/FocusBridge.cpp.o
[ 76%] Building CXX object modules/Alexa/SampleApp/src/CMakeFiles/SampleApp.dir/GUILogBridge.cpp.o
[ 78%] Building CXX object modules/Alexa/SampleApp/src/CMakeFiles/SampleApp.dir/GUI/GUIClient.cpp.o
[ 80%] Building CXX object modules/Alexa/SampleApp/src/CMakeFiles/SampleApp.dir/GUI/GUIManager.cpp.o
[ 83%] Building CXX object modules/Alexa/SampleApp/src/CMakeFiles/SampleApp.dir/JsonUIManager.cpp.o
[ 85%] Building CXX object modules/Alexa/SampleApp/src/CMakeFiles/SampleApp.dir/KeywordObserver.cpp.o
[ 88%] Building CXX object modules/Alexa/SampleApp/src/CMakeFiles/SampleApp.dir/LocaleAssetsManager.cpp.o
[ 90%] Building CXX object modules/Alexa/SampleApp/src/CMakeFiles/SampleApp.dir/SampleApplication.cpp.o
[ 92%] Building CXX object modules/Alexa/SampleApp/src/CMakeFiles/SampleApp.dir/SampleEqualizerModeController.cpp.o
[ 95%] Building CXX object modules/Alexa/SampleApp/src/CMakeFiles/SampleApp.dir/main.cpp.o
[ 97%] Building CXX object modules/Alexa/SampleApp/src/CMakeFiles/SampleApp.dir/PortAudioMicrophoneWrapper.cpp.o
[100%] Linking CXX executable SampleApp
[100%] Built target SampleApp
npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
Illegal instruction (core dumped)l: sill install executeActions
modules/GUI/CMakeFiles/GUIClient.dir/build.make:57: recipe for target 'modules/GUI/CMakeFiles/GUIClient' failed
make[2]: *** [modules/GUI/CMakeFiles/GUIClient] Error 132
CMakeFiles/Makefile2:2146: recipe for target 'modules/GUI/CMakeFiles/GUIClient.dir/all' failed
make[1]: *** [modules/GUI/CMakeFiles/GUIClient.dir/all] Error 2
Makefile:129: recipe for target 'all' failed
make: *** [all] Error 2

It's probably a problem with npm. Nodejs is installed.
Tell us what hardware you're using:

[ ] Laptop

Tell us about your OS (Type & version):

[ ] Ubuntu 18.04 LTS

Hi nu00,
What version of node are you running? It might be too old as you are running 18.04 LTS.
Please run the following to get node 12, (tested on Ubuntu 19.10):
curl -sL https://deb.nodesource.com/setup_12.x | bash -
apt-get install nodejs

Hope this helps!

I'm running node 13.x, as suggested in the quick start of the SDKs. Do I've to downgrade to node 12.x?

https://developer.amazon.com/en-US/docs/alexa/alexa-smart-screen-sdk/ubuntu.html
Please try to downgrade, as a core dump suggests the nodejs is have issues running.

I've removed nodejs 13 and installed node 12. It worked just fine, thanks!


Route with dynamic segment considered as static route.

Hi, I have picked up your package recently (due to Theo's video about Tanstack Router).
I have a page with the following URL http://localhost:3000/food/28881
I defined my routeType.ts as follow:
import type { DynamicRoute } from "next-typesafe-url";
import { z } from "zod";

export const Route = {
  routeParams: z.object({
    foodId: z.number(),
  }),
} satisfies DynamicRoute;

export type RouteType = typeof Route;

But when I try to use it in a Link, routeParams is underlined with the error message: Type '{ foodId: number; }' is not assignable to type 'undefined'.
<Link href={$path({route: "/food/[foodId]", routeParams: { foodId: food.id } })} >
{food.name}
</Link>

My codegen file look like this:
import { type RouteType as Route_0 } from "./src/app/food/routeType";
import type { InferRoute, StaticRoute } from "next-typesafe-url";

declare module "@@@next-typesafe-url" {
  interface DynamicRouter {
    "/food": InferRoute<Route_0>;
  }

  interface StaticRouter {
    "/about/fodmap": StaticRoute;
    "/food/[foodId]": StaticRoute;
    "/": StaticRoute;
    "/quiz/willitfodmap": StaticRoute;
  }
}

From what I understood about the package, I think my route should not be in the StaticRouter.
It should be a DynamicRoute.
The error might be due to not using searchParams on this route?
My package.json looks like this:
{
  "type": "module",
  "scripts": {
    "build": "next-typesafe-url && next build",
    "db:push": "dotenv drizzle-kit push:mysql",
    "db:studio": "dotenv drizzle-kit studio",
    "db:ciqual:load": "tsx ./scripts/import-ciqual-data.ts",
    "script": "dotenv tsx",
    "dev": "concurrently  \"next-typesafe-url -w\" \"next dev --turbo\"",
    "dev:url": "next-typesafe-url -w",
    "lint": "next lint",
    "start": "next start"
  },
  "dependencies": {
    "@auth/drizzle-adapter": "^0.3.12",
    "@planetscale/database": "^1.13.0",
    "@radix-ui/react-dropdown-menu": "^2.0.6",
    "@radix-ui/react-slot": "^1.0.2",
    "@radix-ui/react-toggle": "^1.0.3",
    "@radix-ui/react-toggle-group": "^1.0.4",
    "@t3-oss/env-nextjs": "^0.7.1",
    "@tanstack/react-query": "^4.36.1",
    "@trpc/client": "^10.45.0",
    "@trpc/next": "^10.45.0",
    "@trpc/react-query": "^10.45.0",
    "@trpc/server": "^10.45.0",
    "class-variance-authority": "^0.7.0",
    "clsx": "^2.1.0",
    "drizzle-orm": "^0.28.6",
    "geist": "^1.2.0",
    "lucide-react": "^0.294.0",
    "next": "^14.0.4",
    "next-auth": "^4.24.5",
    "next-themes": "^0.2.1",
    "next-typesafe-url": "^4.0.3",
    "react": "18.2.0",
    "react-dom": "18.2.0",
    "server-only": "^0.0.1",
    "superjson": "^2.2.1",
    "tailwind-merge": "^2.2.0",
    "tailwindcss-animate": "^1.0.7",
    "zod": "^3.22.4",
    "zustand": "^4.4.7"
  },
  "devDependencies": {
    "@next/eslint-plugin-next": "^14.0.4",
    "@types/eslint": "^8.56.0",
    "@types/node": "^18.19.4",
    "@types/papaparse": "^5.3.14",
    "@types/react": "^18.2.46",
    "@types/react-dom": "^18.2.18",
    "@typescript-eslint/eslint-plugin": "^6.17.0",
    "@typescript-eslint/parser": "^6.17.0",
    "autoprefixer": "^10.4.16",
    "concurrently": "^8.2.2",
    "dotenv": "^16.3.1",
    "dotenv-cli": "^7.3.0",
    "drizzle-kit": "^0.19.13",
    "eslint": "^8.56.0",
    "mysql2": "^3.6.5",
    "papaparse": "^5.4.1",
    "postcss": "^8.4.32",
    "prettier": "^3.1.1",
    "prettier-plugin-tailwindcss": "^0.5.10",
    "tailwindcss": "^3.4.0",
    "tsx": "^4.7.0",
    "typescript": "^5.3.3"
  },
  "ct3aMetadata": {
    "initVersion": "7.24.0"
  },
  "packageManager"<EMAIL_ADDRESS>}

Should my codegen look like this instead?
import { type RouteType as Route_0} from "./src/app/food/routeType";
import { type RouteType as Route_1} from "./src/app/food/[foodId]/routeType";
import type { InferRoute, StaticRoute } from "next-typesafe-url";

declare module "@@@next-typesafe-url" {
  interface DynamicRouter {
    "/food": InferRoute<Route_0>;
    "/food/[foodId]": InferRoute<Route_1>;
  }

  interface StaticRouter {
    "/about/fodmap": StaticRoute;
    "/": StaticRoute;
    "/quiz/willitfodmap": StaticRoute;
  }
}

OK, I found why my _next-typesafe-url_.d.ts was not generated as expected.
My "/food/[foodId]" routeType file was the only one with a .tsx instead of a .ts (is there a reason why .tsx are not supported?).
However, I am still not able to build the project. The $path error is still there.
Type error: Type '{ foodId: number; }' is not assignable to type 'undefined'.

  26 |                 href={$path({
  27 |                   route: "/food/[foodId]",
> 28 |                   routeParams: { foodId: food.id },
     |                   ^
  29 |                 })}
  30 |               >
  31 |                 {food.name}
 ELIFECYCLE  Command failed with exit code 1.

The intention with only supporting routeType.ts and not routeType.tsx is that there really shouldnt be any jsx code in that file. Ideally the only thing there is the Route and RouteType declaration and export.
As for the $path error, someone else reported something similar- but it is very difficult to diagnose the problem without a reproduction. Are you able to share the code, or a example app with the same problem?
Thanks for trying out the package and reporting the issue

The intention with only supporting routeType.ts and not routeType.tsx is that there really shouldnt be any jsx code in that file. Ideally the only thing there is the Route and RouteType declaration and export.

I understand I create many .tsx in my pages by inattention, and it is a bad habit. Not supporting .tsx makes sense, I was just curious.
For the $path(), I created a minimal reproducible example there: https://github.com/lelabo-m/error-reproduction-minimal-env/tree/next-typesafe-url/path-parameters-inference
If you open the project, and go to the root page (./src/app/page.tsx), you should be able to see that typescript isn't happy with the parameters given to $path.

thank you I will take a look this weekend

I managed to understand what was going on.
_next-typesafe-url_.d.ts is not treated as an ambient file because of the imports in the start of the file.
Therefore, the following is not working:
import { StaticRouter, DynamicRouter } from '@@@next-typesafe-url'; // does not work.

[...]

type Test = "/a_dynamic_route" extends StaticRoutes ? true : false; // will always return true.

I am not an expert on the subject so maybe a specific tsconfig.json or modifying the codegen output path could fix this.
What I learn from this message on StackOverflow,
is that import could be moved into the declaration to make the .d.ts file ambient.
Example of conversion that work:
FROM
import { type RouteType as Route_0 } from "./src/app/food/[foodId]/routeType";
import { type RouteType as Route_1 } from "./src/app/food/routeType";
import { type RouteType as Route_2 } from "./src/app/quiz/[quizId]/routeType";
import { type RouteType as Route_3 } from "./src/app/quiz/routeType";
import type { InferRoute, StaticRoute } from "next-typesafe-url";

declare module "@@@next-typesafe-url" {
  interface DynamicRouter {
    "/food/[foodId]": InferRoute<Route_0>;
    "/food": InferRoute<Route_1>;
    "/quiz/[quizId]": InferRoute<Route_2>;
    "/quiz": InferRoute<Route_3>;
  }

  interface StaticRouter {
    "/about/fodmap": StaticRoute;
    "/admin/dashboard": StaticRoute;
    "/": StaticRoute;
    "/under_construction": StaticRoute;
  }
}

TO
declare module "@@@next-typesafe-url" {
  import type { InferRoute, StaticRoute } from "next-typesafe-url";
  import { type RouteType as Route_0 } from "./src/app/food/[foodId]/routeType";
  import { type RouteType as Route_1 } from "./src/app/food/routeType";
  import { type RouteType as Route_2 } from "./src/app/quiz/[quizId]/routeType";
  import { type RouteType as Route_3 } from "./src/app/quiz/routeType";
  interface DynamicRouter {
    "/food/[foodId]": InferRoute<Route_0>;
    "/food": InferRoute<Route_1>;
    "/quiz/[quizId]": InferRoute<Route_2>;
    "/quiz": InferRoute<Route_3>;
  }

  interface StaticRouter {
    "/about/fodmap": StaticRoute;
    "/admin/dashboard": StaticRoute;
    "/": StaticRoute;
    "/under_construction": StaticRoute;
  }
}

Opened a PR (#85) with a proposed fix in case this issue is relevant and not just a project configuration issue.


Create a Kubernetes Cluster on the Grillo Cloud account

[x] Create resource group
[x] Create a VPC
[x] Create the Kubernetes Cluster

The cluster is up and running


Windows installer: coq might not work if installing over an existing installation

As reported in #213 the Coq installed with the Windows installer might not work it is installed over an existing installation. The installer  should check this and issue a warning.

duplicate of #214.


DistributedApplication XML docs

First pass at bolstering our XML docs for DistributedApplication. More classes to follow but this is one of the central classes.
Microsoft Reviewers: Open in CodeFlow

Did a replacement myself (app host) that we missed I think.


Update from_json docs

This is possible since @samuelcolvin fixed the docs in pydantic-core, see https://github.com/pydantic/pydantic-core/pull/1070

Please review


Non-US keyboards aren't correctly mapped

Tested with PT-PT keyboard.

Tested with french keyboard on Mac OS X, same issue.

Works right now

Non US-keyboards are still incorrectly mapped inside vim.

I've the same issue with a PT-BR keyboard layout.

I got the main culprit, this function seems to remap keys only for US keyboards.
https://github.com/shockone/black-screen/blob/master/src/utils/Common.ts#L222-339

Same issue with ES-ES keyboard

Could you please verify it works in v0.0.42?

Yes, it's working fine on v0.0.42!


one >53 errrors to report, reviewdog aborts GitHubActionLogWriter: "reported too many annotation"

TODO / Remaining bug:
When more than 53 errors are reported by mypy and are not filtered, reviewdog gives up and aborts with the message:
GitHubActionLogWriter: "reported too many annotation"

The error is buried in the middle of the long output:
  /home/runner/work/xen-api/xen-api/scripts/plugins/extauth-hook-AD.py:70:19: error: If x = b'abc' then f"{x}" or "{}".format(x) produces "b'abc'", not "abc". If this is desired behavior, use f"{x!r}" or "{!r}".format(x). Otherwise, decode the bytes  [str-bytes-safe]
  Warning: [mypy] reported by reviewdog 🐶
  In function "fresh_name":

  Raw Output:
  /home/runner/work/xen-api/xen-api/scripts/static-vdis: note: In function "fresh_name":
  reviewdog: GitHubActionLogWriter: reported too many annotation (N=53)
  + reviewdog_exit_val=1
  + echo ::endgroup::
  + [[ false == \t\r\u\e ]]
  Error: [mypy] reported by reviewdog 🐶
  Incompatible types in assignment (expression has type "str", variable has type "int")  [assignment]

  Raw Output:

I know the current GitHub limits, they are also printed in the log:
   Error: reviewdog: Too many results (annotations) in diff.
  You may miss some annotations due to GitHub limitation for annotation created by logging command.
  Please check GitHub Actions log console to see all results.

  Limitation:
  - 10 warning annotations and 10 error annotations per step
  - 50 annotations per job (sum of annotations from all the steps)
  - 50 annotations per run (separate from the job annotations, these annotations aren't created by users)

However, reviewdog should do it's best to report 10 error annotations and 10 warning annotations (and it should also support 10 notice annotations, btw) and if > 10 annotations, the 10th annotation of each kind should be a message that there are more than 10 annotations, which GitHub does not support.
The same may also apply to review comments, but I am not aware of such limit. However, to prevent a DoS from reviewdog, it is likely best if reviewdog replaces the last comment it would be able to add with a "Giving up due to GitHub limit".
In case of too many errors, it may also be nice to merge several erros of the same kind into one error and add "more of the same are omitted due to GitHub annotation limits of 10 annotations per type and step".
Another nice feature would be to mark less important errors not as errors but as warings and notices, so in total 30 annotations could be issued per step.
The biggest problem is that the action-mypy does not fail CI in this case, so the error goes unnoticed:
https://github.com/xenserver-next/xen-api/actions/runs/7706543512/job/21002295649

Thank you, I'll try to remember it.

JSON support merged


No way to pipe input?

Attempting to pipe in Y4M video as one of the clips results in a crash with the following backtrace:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: "Invalid data found when processing input"', src/video.rs:62:51
stack backtrace:
   0: rust_begin_unwind
             at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
             at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/core/src/panicking.rs:142:14
   2: core::result::unwrap_failed
             at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/core/src/result.rs:1814:5
   3: ssimulacra2_rs::video::compare_videos
   4: ssimulacra2_rs::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

As a side note, it would be nice if we could use - instead of /dev/stdin to pipe input in.

Oops, my mistake.  This was not actually being fed Y4M and instead accidentally fed raw YUV with no header.
That said it still would be nice to have - aliased to stdin.

Well, it looks like it is no longer possible to pipe in input in 0.4.0.  My best guess is that this is due to the change from av-metrics-decoders-0.1.10 to av-metrics-decoders-0.2.2, as the former appears to be limited to using strictly ffmpeg, while the latter appears to support vapoursynth.
There appears to be no way to bypass vapoursynth, even when the input file is /dev/stdin or even a named pipe ending in .y4m.

Appears to be working again in 0.4.1.  Thank you Soichiro.


Fix performance issue with setVal on MultiSelect

As suggested in https://github.com/ivaynberg/select2/issues/781#issuecomment-30935226, significantly improves selection performance (90~100x faster) on a list of 2,000 items.
Also see: https://github.com/ivaynberg/select2/issues/905 and https://github.com/ivaynberg/select2/issues/2706
It will take 1s to 'select all' in patched version http://jsfiddle.net/hrro7j6L/3/ and 93s in head version http://jsfiddle.net/hrro7j6L/4/

I see that this is in the 3.5 stable branch, but has not yet been released. Is there any chance of a 3.5.3 release for those of us that aren't ready to upgrade to 4.0 yet?

+1, would like to go to 3.5.3


Fix url parameter encoding

Fixes issue #52
Please note that this fix has one behavior change that I believe should not affect anyone:
Previously you could mix usages of org.lightcouch.URIBuilder#query(String name, Object value) and org.lightcouch.URIBuilder#query(String query) (although I highly doubt that ever worked because it seems there was no proper handling of when to add the ampersand "&" character between the inputs of the two methods).
After this commit the behavior is that the latter form (org.lightcouch.URIBuilder#query(String query)) takes precedence.

You can use the version from my fork.
I'm guessing the project mainteners are too busy to review this relatively big fix (although it's very straight forward).

@iddo thanks for providing a fix for the issue.  I 'm reviewing the changes to make sure it doesn't introduce a breaking change to the previous code.  Thanks.


Integration 0.17.1

Hey there and thank you for opening this pull request! 👋🏼
We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.
Details:
No release type found in pull request title "Integration 0.17.1". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - fix
 - hotfix
 - feat
 - feature
 - chore

/deploy-review


Reject ANN and ALLOW FILTERING queries; improve error messages

Fixes: https://github.com/riptano/VECTOR-SEARCH/issues/13

ANN ordering restrictions do not support ALLOW FILTERING. This PR ensures any query that is configured with ALLOW FILTERING and with an ANN restriction will get an appropriate error message.
Improve the implementation of StatementRestrictions#throwRequiresAllowFilteringError so that it throws an appropriate error message when a vector column is restricted.

While investigating the potential places where the StatementRestrictions suggests using ALLOW FILTERING, I noticed that we do not hit exception in the logic below because hasQueriableIndex goes to true when a query has an ANN restriction. Given how integrated the queriable index logic is, I think this is correct. Just to make sure things work as expected, the tests cover some of the cases where we would otherwise hit the exception in this block:
https://github.com/datastax/cassandra/blob/0cf91bd63bbc0a4d8ae86fc4c1721ec5af708903/src/java/org/apache/cassandra/cql3/restrictions/StatementRestrictions.java#L496-L510

@blerer - please take a look, if you're available.

I don’t think we should reject ALLOW FILTERING for ORDER BY ANN OF?  You should be able to filter the results of the ORDER BY using columns which don’t have an index.
I agree we can’t do the ORDER BY ANN OF itself without an index, but we should be able to  filter on other columns?

Thanks for your review @jakubzytka. I hope to address the feedback tomorrow.

@jbellis @jakubzytka - PTAL, this is ready for review


fix: minor changes to Analysis.Normed.Field.Basic from code review

these changes from code review didn't make it in before bors

bors r+


Add tags to the HSF repos

At present there are no tags present in many of the HSF repos.
Maybe we should consider tagging a repository when it is used for a talk or carpentry?
(I am not sure if such a process is already implemented)

You mean the "topics" under the description? I agree. I already wrote in Slack looking for more people to help to add some.

I meant this one: the tag for a given repo e.g., https://github.com/hsf-training/maintenance/tags
not sure if thats same as what you said.

Oh I see, yeah that's different. This could be done. However, unless one also offers different versions of the deployed webpage, I doubt that this would be of much use for the students.
I do however think that every readme should contain a list of links to the workshops that have taught it.

Oh I see, yeah that's different. This could be done. However, unless one also offers different versions of the deployed webpage, I doubt that this would be of much use for the students.

oh I see. so we cant deploy all the tags at once?

I do however think that every readme should contain a list of links to the workshops that have taught it.

thats a good idea.
For the moment, It would also be good to post the link to the next hackathon in the singularity/docker readme?

I think there's ways to get multiple versions with gh pages, but I think it's probably not worth it (?).
Yes, we can also add a list of past workshops/hackathons to the readmes. Feel free to open PRs adding these links.
Later today I will think about what to do to bring the readmes in a standard format.

Yes if we add list of workshops/hackathons with links in the readme, then it wont be worth to deploy multiple versions.

I will start creating a template in hsf-training/carpentry-cookiecutter.
Though actually this should also go in the HTML version of the modules....


Lock dependency to RSpec 2.x

Since the test suite cannot run with RSpec 3.x, it would be great to lock down the dependency and add a Gemfile so that it is easier to test with RSpec 2 while also having RSpec 3 installed.

@michaelklishin  - Hello.  I hope that you still have this on your radar.
I am considering this PR, but have not come to a decision at this point.
I would like to ask several questions.

Are you aware that the original author of bundler (Yehuda Katz) recommends that Ruby gems not check Gemfile.lock into version control (that is recommended only for Ruby Applications)?  His thinking can be found here:

http://yehudakatz.com/2010/12/16/clarifying-the-roles-of-the-gemspec-and-gemfile/
I would ask for your comments on that please.

What actual problem are you trying to solve?  What caused you to suggest this change at this point in time?  I need details please.

Also, are you aware this this gem reverted a 'bundler/Gemfile' implementation at one point?  See: a072575d1ef9831d7c040d1f6b7a0771b7762e21

Thanks, G

@gmallard I'm happy to remove Gemfile.lock. The problem I'm trying to solve is: I want to run this project's tests and I was unable to do so when RSpec 3 is pulled down. I believe question 3 has the same answer as 1 :)

Alternatively, and perhaps as a good next step, the test suite should be converted to RSpec 3.x. I'm happy to do that in the near future as our team (RabbitMQ) uses this gem's test suite among other suites to test our STOMP plugin.

@michaelklishin - Interestingly another user has broached the subject of Rspec levels. See: https://github.com/stompgem/stomp/issues/114
I wondered if this PR was related to that subject.
I want some more time to think about this.  I will get back to you.
Totally off topic, regarding RabbitMQ:
When I test here I typically use 'rake test' and run the unit tests against live servers.  I generally test against:

ActiveMQ
Apollo
RabbitMQ

Your plugin (at lease one version of it) is exercised frequently.
Thanks, G.

Ideally I would like future stomp gems to:

Install and the specs run with only Rspec 2.14+ installed.
Install and the specs run with only Rspec 3.x installed.
Install and the specs run with both Rspec 2.14+ and Rspec 3.x installed.

I think that can be done and am going to start down that road here, but if you want to attempt that approach also please go ahead.
I would also appreciate any comments you have (pro/con) regarding that approach.  And alternative ideas of course.
Regards, G

@michaelklishin Can you please try the gem code:

In my personal clone: https://github.com/gmallard/stomp
HEAD of branch 'rsvertst'

and let me know if it meets your requirements for RSpec 3.
Please provide detailed feedback if this 'fails'.
Thanks, G.

@gmallard I will give that branch a try next week. I doubt there's any value in supporting RSpec 2.x now or in the future. 3.x has been around since June 2014.

@michaelklishin  Yes, well., one never knows what happens to gem files after they are out in the wild.

@gmallard your branch does work for me with RSpec 3.4. I suggest that it is merged into the mainline. Thank you!


cloud-config strict init mode

Is it possible somehow to force my CoreOS to read the user_data file at every boot?

coreos-cloudinit does read your platform's user_data on every boot. What provider are you using?

I'm using Virtualbox. Looks like it's working now. Most of the time the refreshed data will be attached at the second boot. But if I use a brand now VM image, reading at the first time without problem.


Explicitly set an empty argument list to the oauth2client cmdline

Calling simplegmail from another command-line
tool using argparse, would pass the current options unrelated
of the command to the run_flow call and fail.
The change set empty flags before calling run_flow

@ant31 Sorry for taking so long to get to this. Ignore the revert - I thought about trying parse_known_args to allow for command line args to run_flow, but not sure if it's appropriate and can try later if desired.

Thank you,

thought about trying parse_known_args to allow for command line args to run_flow,

Yes, but you probably want to wait for the use-case, a user needing this feature to implement it.


Added a Step-By-Step Guide For Simulator

Fixes #
Describe the changes you have made in this pr -

Screenshots of the changes (If any) -

Coverage remained the same at 84.266% when pulling 39c7c5b037dfd97e05a8cb9999570ec3e6c1b25f on Sj1218305:master into 1a5c07e53bfe001dab851a45942f176be6e482fa on CircuitVerse:master.

Hello @Sj1218305 , could you close this PR and create a new PR please?


store & show build logs for non-default targets

fixes #787.
Generally the idea is:

we store additional logs next to the default-target logs
the build-details view just shows all files in that folder

Due to lack of web frontend skills I just added a barely functional way to switch through the logs, I would appreciate help here, though I would also be fine with merging the interface as-is.

Interface currently looks like:

@Nemo157 btw, I think this could also be improved by showing a build-status per target, but I definitely wanted to postpone until after #1011

I was wondering if we could just use "is the filename in the releases.doc_targets list" as a proxy for that till we actually track it.


Apply Invalid Styles To Parent(s) of Invalid Field

Currently if a nested field contains an invalid value when an entry is published, and its parent (or parents) are toggled closed, there is nothing to indicate where the invalid field is. This makes it look as if the publish has simply failed without reason and the only way to diagnose the source of the failure is to toggle open all fields until the invalid field is discovered.
How about marking all parent fields of the invalid field as invalid too. This would provide a nice simple breadcrumb trail to the invalid field(s).

Would it be okay if I grabbed this issue? I’m new to contributing, so any extra tips other than following the readme and contributing markdown info are welcome. I also wanted to verify what the is issue as well. From what I understand, if there is a link tag inside of a paragraph tag and there is some problem with the link, it just does not show the error in the cms unless we toggle open all fields, and then we can see the error, but we want to basically have the parent(s) indicate there is a problem within correct?

Closing as duplicate of #5630


When renaming or closing a window/tab the selection does not stay in the correct place

Scenario

Select a window
Hit x to close it.

Expected behavior
The item that is now has the position that the closed window did, should be selected (this would typically be the next item in the list).
Actual behavior:
The selection moves up to the item above the window that was closed
Cause
This is a bug in treecat, where only changed properties are updated, but if you change items you need to change selected as well.

There is a similar behavior on renaming a window, where the selection goes to the top of the list, and the keys are out of sync, it is the same problem where selectedIndex is not being reset after replacing items, because it has not changed.