Strange polygon shapes at tile borders

Hi,
I optimized segmentation very nicely now and the output looks very nice.
One problem that still occurs is along the edges of the tiles that get created for cellpose.

In the viewer it almost looks like the polygons overlap.
But the polygons in the sdata also look strange:

Any idea what is happening?
I am using patch_width_pixel: 4096 patch_overlap_pixel: 820 but this is also happening with other values along all the edges of segmentation patches.

The squares do not happen too often luckily.
What effect does the overlap have? Will the same protein intensity / transcripts be assigned twice?

Yes, the same protein intensity / transcript will be assigned twice
For transcripts, using Baysor should solve the issue, but for the proteins it's more difficult to solve. I think some people are developing more sophisticated aggregation methods than a simple average. E.g., pixels far from the nucleus would have a small weight when averaging the intensity if the corresponding neighbourhood cell is high for this protein.

ok, that's good to know.
Ty!


Add better comments to requirements.txt

In #5 it was noted that it's not obvious where to add new package requirements.
One may (quite reasonably) assume that test/requirements.txt is a likely place.
This is almost certainly incorrect but was not documented.
This PR adds a comment to the top of each file attempting to clarify.
Unfortunately it's hard for someone who created a file to think into the head
space of someone who didn't so I'd appreciate at least @boyuanxiao and/or @jb803
seeing if the comment makes sense/suggesting better wording.

Heh! Looks like pylint has got more strict on import order. I'll fix as part of this PR.

:+1:


Fix lintDirtyModulesOnly when matching path on Window

I run with lintDirtyModulesOnly option on Window, it doesn't work due to minimatch's problem on Window. After changing minimatch into micromatch it works fine in my case, and performance is a bit better.

Coverage remained the same at 98.718% when pulling 58d57c2e730fd9226b29216365031db9a428f1a8 on MQuy:master into 16c3d41e5694952c98824fa94a9210a33bba2360 on JaKXz:master.

Coverage remained the same at 98.718% when pulling 58d57c2e730fd9226b29216365031db9a428f1a8 on MQuy:master into 16c3d41e5694952c98824fa94a9210a33bba2360 on JaKXz:master.

Coverage remained the same at 98.718% when pulling 58d57c2e730fd9226b29216365031db9a428f1a8 on MQuy:master into 16c3d41e5694952c98824fa94a9210a33bba2360 on JaKXz:master.

@JaKXz, it is quite strange that it causes an error. The only major change is related to micromatch, but this library is used by stylelint ..., it shouldn't be a problem 🤔

The issue is with npm-install-version which we use to install different versions of webpack in tests.
I don't have the cycles atm to look into that package, but please feel free to do the deep dive :)


Add filetype option for fcontext resource

Adds another attribute and uses it to determine the options used in semanage fcontext

Quick feedback - if we don't allow the user to control whether they want to follow symlinks or not, we're modifying default behavior which is a bad idea.
Wanna add an attribute instead (follow_symlink, defaults to true)?

Actually, I don't think we break default behaviour. Since the user has to specify the filetype, symlinks are only not followed if it is set to "l". Am I missing a part (I'm very new to SELinux).
I started with using symlink as an attribute, but this seems more generic.

What is the default of filetype? I missed that it's a new attribute.
Are there any use cases other than "whether to follow symlinks"?
If not, I feel that we should use follow_symlinks instead.
:+1: on the added tests. Is the kitchen passing?

Just noticed the travis fails. I know what I'm doing this weekend! :smile:

filetype has as default value nothing, so it applies to all files. You can use d for directories or l for symlinks (or something else for regular files. It's basically a passthrough to the -f option used by semanage fcontext.
The other use cases are to set something only for directories, or regular files. Could be other use cases too, but they will be extremely specific.
Knife test fails, but because one of the relabels isn't executed before the test it seems. When the fcontext is set to context2, the check for that fails. But if you ssh into the machine, it is applied. I'm guessing it's because the relabel action after a modify isn't triggered immediately. When I changed that behaviour in the lwrp, everything succeeded.

Please rebase against master so we can have some testing

Hi, I've rebased and refactored according to your commits. Let me know if it's OK or not :)

OK. I have read everything and the manual for semanage and your PR has a very good usecase. I will now write some comments so we can ship this

Done adding comments. TY

I will try and fix my validation tests so we'll get a clean bill in Travis.

I've updated according to your comments, but haven't tested properly yet. Kitchen fails on SSH connect on the centos boxes for some reason, don't know why :s
I'll take another look later today, right now it's football time :P

BTW: a general remark. Custom resources has changed significantly since chef 12.5. See https://docs.chef.io/custom_resources.html
I still have to change all my cookbooks too.
And a question about the tests. Is there a reason why you're testing inside the test recipes instead of with a test framework like bats that can be plugged in to kitchen?

RE your remarks:

I don't work with Chef nowdays. When I did (~6mon ago), the backwards compat for custom resources was really bad and broke on a lot of platforms (not mine), so I've decided to stay out of it.
Creating testing infra is annoying. This worked for me at the start and doesn't look so bad now. I don't know how to ensure Chef avoids double relabeling with RSpec, for instance

Thanks for the answers, seems fair enough :)

btw - CI checks passed yay

I see you're rebased on v1.0.0 where relabling is immediate (check the file).
Can you gist the result of the kitchen and attach it here please?

I have traced it some more, and it seems that if you set a context for a symlink, and then create that symlink, the context is not set correctly on that symlink. This is after the failed run:
[vagrant@default-centos-72 www]$ sudo matchpathcon /var/www/tester_symlink2 -V
/var/www/tester_symlink2 has context unconfined_u:object_r:httpd_tmp_t:s0, should be system_u:object_r:httpd_sys_rw_content_t:s0

I think if you create the symlink first and then use the fcontext resource, it will work, so I'll just change that and see what happens.
I have no idea why selinux doesn't set it, and I can't find anything about it ATM.

TIL matchpathcon
Nitzan Raz
http://backslasher.net
On Wed, Sep 28, 2016 at 3:48 PM, Dieter Blomme<EMAIL_ADDRESS>wrote:

I have traced it some more, and it seems that if you set a context for a
symlink, and then create that symlink, the context is not set correctly on
that symlink. This is after the failed run:
[vagrant@default-centos-72 www]$ sudo matchpathcon /var/www/tester_symlink2 -V
/var/www/tester_symlink2 has context unconfined_u:object_r:httpd_tmp_t:s0, should be system_u:object_r:httpd_sys_rw_content_t:s0
I think if you create the symlink first and then use the fcontext
resource, it will work, so I'll just change that and see what happens.
I have no idea why selinux doesn't set it, and I can't find anything about
it ATM.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/BackSlasher/chef-selinuxpolicy/pull/52#issuecomment-250156622,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AG3He_pahFYUnaQ4_ync-bGyQ0bc__hDks5qumICgaJpZM4J0oLQ
.

I've changed, and now only symlink-nomod2 fails, which it should. It can't modify a file context, since there isn't one for "all files" for that location, only one for symlinks.
Is that what you were looking for?

Yep, as far as this test goes. Imma read up about the thing you said about
symlinks though
Nitzan Raz
http://backslasher.net
On Wed, Sep 28, 2016 at 3:53 PM, Dieter Blomme<EMAIL_ADDRESS>wrote:

I've changed, and now only symlink-nomod2 fails, which it should. It can't
modify a file context, since there isn't one for "all files" for that
location, only one for symlinks.
Is that what you were looking for?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/BackSlasher/chef-selinuxpolicy/pull/52#issuecomment-250157777,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AG3He0juKt0bDRdYaXhTF6LcnQ_wKO_pks5qumNAgaJpZM4J0oLQ
.

What  do you mean with TIL matchpathcon?

Today I Learned about matchpathcon

Well the "create does not apply context" is actually true for all fcontexts as far as I remember, so it's not preventative

I did not explain properly - the test should not fail. We should set it up somehow so it'll pass - e.g. use "remove" (which should do nothing) and trigger on failure.
Other than that - looks legit. Will review again this week and waiting for tests to pass
:100:

@daften do you have this enabled?
https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/
I'm not sure how to exploit this even if it is though

Hey,
I have this enabled now. I guess this is how you'd make changes: https://help.github.com/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork/ :)
I'll make sure the test succeeds now, give me an hour or so (lunch break coming up too).

I have deleted the failing test, because there is no way to check that behaviour without a failing test as far as i can see.

Hi
Just got to run the test myself (was quite busy with actual work stuff)
execute[selinux-fcontext-httpd_tmp_t-modify] should not run because we should be able to detect it, so the test IS good but failing because the code is bad :)
We should modify fcontext_defined to take the filetype into account, and then the :modify action will not run (because it'll correctly detect that the context we're talking about does not exist) and we'll pass
Wanna take a poke at it?

Also plz rebase

I put in a couple of hours on this today, but it's not as easy as I thought. I'll think about this again in a couple of days.
We can't release this without this test, because it might introduce weird behavior..

I agree with the testing part, Ill try to put in some more time this week as well!

Now going to rebase. Too bad I forgot to earlier

Finished rebasing. I'm good ot go - you think we're missing anything?

So, something on your mind or we can merge this?

Basically merged in 394cd97c08bb27067db9085a63ccd950121c4184

Thanks for the contribution, please LMK if something breaks!

Will do, sorry for the unresponsiveness, extremely busy with other items at work :s
Thanks for the cooperation/working together, it was fun :)


docs: fix function names in fuzzing test documentation

The introduction of FuzzIntegNoTearDownWithDownload is confusing with the duplicate names in container fuzzer.
Signed off by: Jiongchi Yu<EMAIL_ADDRESS>

/retest

/ok-to-test This file shouldn't affect that though.

/ok-to-test


Are there plans to add TabbedPage?

Hi @maonaoda , sorry for the late reply. I'm kind of packed with my primary work now, so there's no plan to support TabbedPage for now, but if you would like to submit a PR I would be ver welcomed to review and merge it.

For now, I think this plugin https://www.sharpnado.com/full-customizable-tabs-for-maui/ could be a nice alternative for those willing to implement Tabs.


Clean up main.go

Remove signal channel in favor of signal.NotifyContext
Move shutdown context creation after signal wait so that the timeout is valid during shutdown

Thanks for the feedback @SuperQ


feat: output digest for image push

In CI, the digest is useful for deployment after building.

This is already the case for push. Reference of the image is already being printed to stdout.

1- This is a breaking change
2- Could you please describe the change
3- How is this is this fixing it

This is already the case for push. Reference of the image is already being printed to stdout.

It's better to just output the image digest for easier consumption, otherwise it needs to be grepped.
In any case, we are using a different model for our deployment now.


ILI9488 16bit Parallel interface is not working (IDFGH-7920)

Environment

Development Kit:  https://www.makerfabs.com/esp32-s3-parallel-tft-with-touch-ili9488.html
Module or chip used:  ESP32-S3-WROOM-1-N16R2
IDF version : v4.4.1
Build System:  idf.py
Compiler version : (crosstool-NG esp-2021r2-patch3) 8.4.0
Operating System:  Linux
Using an IDE?: VS Code
Power Supply:  USB

Problem Description
LCD is not displaying any characters or color fill while interface with ESP32-S3 using i8080 interface. The kit is working properly with https://github.com/lovyan03/LovyanGFX library.
Expected Behavior
LCD should display the content
Actual Behavior
LCD is not displaying any content.
Code to reproduce this issue
display.zip
Could you please review above code & let me know if changes required.

I don't have a ILI9488 LCD around, I had a quick look at the datasheet, seems like the lcd_cmd_bits and lcd_param_bits are not 16 bits in lenght (while you set them both to 16 in your code).

        .lcd_cmd_bits = 16,
        .lcd_param_bits = 16,

should be changed to 8.
You can upgrade to IDF5.0 to refer to this code:
https://github.com/espressif/esp-idf/blob/master/examples/peripherals/lcd/i80_controller/main/i80_controller_example_main.c

Initially I tried with 8 bit command & parameter size using example from master branch. It is not working. Due to this, I changed it to 16bit. Used following parameter for writing commands with 8 bit length.
esp_lcd_panel_io_tx_param(io, ILI9488_CMD_POWER_CONTROL_1, (uint8_t[]){0x17, 0x15,}, 2);
How many bytes will be transferred from cmd_val register if cmd_cycles count is 0. What is byte order on bus ? For example, 0x1122, will it be { 0x22 0x11 } or { 0x11 0x22}

How many bytes will be transferred from cmd_val register if cmd_cycles count is 0

The hardware will skip the CMD phase, which means, no data saved in cmd_val will be transferred.

What is byte order on bus ? For example, 0x1122, will it be { 0x22 0x11 } or { 0x11 0x22}

LCD is big-endian, e.g. to send command 0x1234, byte 0x12 should appear on the data line first

Thanks. I'm successfully configured display. Setting RD pin as high resolved the issue.
By default ILI9488 is Portrait Mode 320x480. How to configure the ILI9488 & LVGL as 480x320 using ESP32-S3.

I am also wanting to have a lvgl - esp-idf driver for the ili9488 using a parallel interface.
It appears that you have gotten one working.  Are you able to share the code?
I am using an elecrow esp32 RGB terminal (S3).  It works well with the Arduino/LoyvanGFX, but I don't like the confusion of having two frameworks.

Hi @ldharmon, you can use our LCD table: https://github.com/espressif/esp-bsp/blob/master/LCD.md there are links to all tested drivers for esp-idf and LVGL. I recommend to use 'esp_lvgl_port' component for use LVGL.


Consider moving the repository to nuxt-modules/gtag

Describe the feature
It might be a good time to consider moving this repository to nuxt-modules/gtag. Would you be open to this idea?
https://nuxt.com/docs/guide/going-further/modules#joining-nuxt-modules-and-nuxtjs
PS.: I'd be very happy to help if needed with this or overall maintenance!
Additional information

[ ] Would you be willing to help implement this feature?
[ ] Can you think of other implementations of this feature?

Final checks

[X] Check existing issues.

Yeah, I'd gladly move this repo to Nuxt Modules! I'm maintaining Nuxt Plausible already, so it would be a good fit to move this repo as well.
How do we continue. Should I open an issue in nuxt/modules?

Yes please! Creating an issue would be a good starting point :) I'll try to move this forward if it gets stuck for too long without any action being taken.


Update Set-CsMobilityPolicy.md

Removed all instances of EncryptAppData based on Content Idea request 78817 approved by SME Premal Gandhi: The documentation for the cmdlet Set-CsMobilityPolicy contains the parameter '-EncryptAppData', which is not used at all. As agreed with Premal, this parameter should be removed from the documentation.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Set-CsMobilityPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Make NormalParamWrapper pass other inputs

NormalParamWrapper should leave other input untouched, in case they're needed for some other purpose (e.g. intermediate hidden value used for value computation etc.)

broken tests due to share_memory_ cuda error in nightly


FPS calculation

I am research on the calculation of FPS in this project(340 FPS). Is there any explanation on the start and end point? I have tried calculate the forward time through caffe test tool(benchmark), but it showed a little difference. Will it be possible to show the code which you calculate the fps? Thanks a lot!

It’s not measures by Caffe test. It’s measured by running the provided toolbox.

Thank you for reply. I tested the time of predict_single_frame with python tool(time).  The result showed 30fps with over_sample=TRUE and 60fps with  over_sample=FALSE. I am wondering where is the difference between our methods?

It’s not measured by Caffe test. It’s measured by running the provided toolbox.

where is the toolbox?


dfu-util dependency

I'm following the instruction for compiling the Crazyflie 2.1 application but the dfu-util dependency is not installed.

Solved here: https://github.com/micro-ROS/micro-ros-build/pull/79/files#diff-117fcd31fa40a4d80ed049b099c2cbc4R97

Close when https://github.com/micro-ROS/micro-ros-build/pull/79# merged


Use the internal_account/container for status.

When available, we should use the internal_account and
internal_container for the status file tracking. The internal_account
and internal_container are only populated for the sharded containers.
The values are the hidden dot account for the shards (.shards_)
and the shard container in that account, respectively.
Otherwise, if any node has multiple shards, they may collide in the main
container stats tracking.

Coverage increased (+0.1%) to 88.257% when pulling 4f65b43109eaa0194bc6dafe617f13cafb74cd6b on bug/sharded-status-tracking into a5a5ad75c8bf02ec51d77aa43eea20a354b23058 on master.


Where can I find the complete datasets of different networks mentioned in the paper?

Specially the the Arenas email network with 1% noise, how can I get the same dataset with other percent of noise like 5%...?

Hi Weifan,
You can get the dataset from the Koblenz Network collection (http://konect.uni-koblenz.de/networks/arenas-email http://konect.uni-koblenz.de/networks/arenas-email), and basically remove some of the edges with the desired probability.  (You may want to avoid leaving any node completely disconnected.). The format provided in our simple reference example illustrates the kind of format our code accepts, although that could of course be modified.
Best,
Mark

On Nov 29, 2018, at 2:50 AM, WeifanWong<EMAIL_ADDRESS>wrote:
Specially the the Arenas email network with 1% noise, how can I get the same dataset with other percent of noise like 5%...?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/GemsLab/REGAL/issues/2, or mute the thread https://github.com/notifications/unsubscribe-auth/AEUEw8FmMtGSwWiXK2zpmfPYt7Wv2CPVks5uz5HjgaJpZM4Y5Hl7.

Hi Mark, sorry to reply you so late... But it's really nice of you recommend me this website which helps me a lot. I have been confused for a long time by the source of datasets.
Anyway thanks again for your help. And this paper (REGAL) is really nice too.
Best wishes,
Weifan


Unable to use the Library

I'm new to Android and there's very little guidance on how to use the library. In fact, there is only one line on usage and after pasting that line in my activity, It was missing the GlideEngine. I found the GlideEngine online and fixed that issue. But the next parameter was the OnResultCallBack which required the GridImageAdapter and both of these resist in the library but I'm calling the openGallery() function from my Activity so how am I supposed to pass the mAdapter (GridImageAdapter) there? When I don't have it in my activity neither I can access it from the library. I know it must be very easy to use but I just couldn't figure out how to use it as I'm new to the programming. Kindly help with this. Thanks

emmm...  GridImageAdapter is to display photo album pictures，replace GridImageAdapter with Adapter in your project

Thank you :)


PostCss: Custom media queries in vue files

As of this release, PostCSS should be "working everywhere".
And it is. Kind of…
I'm using postcss-preset-env to use the new cool features of CSS. One of the new cool features is "custom media queries".
And here's my problem.
I my "/assets/base.css" i have declared variables and custom media queries. And if i use them in my "base.css" everything is a-ok!
But when i use the exact same custom media query, in my single file component (.vue), the media query is not resolved through postcss-preset-env. Other stuff like, nesting, variables and such is working fine…
Base.css
@custom-media --viewport-ms-max (max-width: 767px);

body {
  font-size: var(--base-font-size, 16px);

  @media (--viewport-lg-min) {
    font-size: 18px;
  }
}

I've already tried not nesting the media query, in the .vue file, but it doesn't help :(
Using only the auto detected postcss.config.js and some plugins (NO nuxt.config.js postCss configuration), here's my postcss.config.js:
module.exports = {
  plugins: {
    stylelint: {},
    'postcss-partial-import': {},
    'postcss-nested': {},
    'postcss-preset-env': {
      browsers: [
        'last 2 versions',
        'ie >= 11',
      ],
      stage: 0,
    },
    'postcss-reporter': {
      clearReportedMessages: true,
    },
  },
};

Can anybody help me how to resolve the media queries in my .vue single file components?

This question is available on Nuxt community (#c7517)

NathanChase:
I had to find out the hard way that custom media queries have to be defined in your postcss.config.js file
I actually just posted about trying to better utilize styleResources to do this with PostCSS and the author of style-resources-loader said that he plans to implement it: https://github.com/yenshih/style-resources-loader/issues/7
Here's my postcss.config.js so you can see how I ended up doing it:
const postCssCustomMedia = require("postcss-custom-media")
const postcssPresetEnv = require("postcss-preset-env")
module.exports = {
  plugins: {
    stylelint: {},
    'postcss-partial-import': {},
    'postcss-nested': {},
    'postcss-custom-media': {
      extensions: {
        '--viewport-xs-min': '(min-width: 0)',
        '--viewport-xs-max': '(max-width: 575px)',
        /* Small medium screen / phablet, large phones */
        '--viewport-ms-min': '(min-width: 576px)',
        '--viewport-ms-max': '(max-width: 767px)',
        /* Small screen / tablet */
        '--viewport-sm-min': '(min-width: 768px)',
        '--viewport-sm-max': '(max-width: 991px)',
        /* Medium screen / desktop */
        '--viewport-md-min': '(min-width: 992px)',
        '--viewport-md-max': '(max-width: 1199px)',
        /* Large screen / wide desktop */
        '--viewport-lg-min': '(min-width: 1200px)',
        '--viewport-lg-max': '(max-width: 1399px)',
        /* X Large screen / X wide desktop */
        '--viewport-xl-min': '(min-width: 1400px)',
      },
    },
    'postcss-preset-env': {
      stage: 0,
      browsers: [
        'last 2 versions',
        'ie >= 11',
      ],
    },
    'postcss-reporter': {
      clearReportedMessages: true,
    },
  },
};

Closing in favor of https://cmty.app/nuxt/nuxt.js/issues/c7516


Commad not added to the $PATH

When building with the base image paketobuildpacks/builder-jammy-base:latest and BP_JATTACH_ENABLED=true, the jattach layer is added, but executable is not added to to path, nor included in any folders included in the path.
cnb@plainly-backend-86787d8f85-hbhzk:/$ ./layers/paketo-buildpacks_jattach/jattach/bin/jattach
jattach 2.2 built on Jan 10 2024

Usage: jattach <pid> <cmd> [args ...]

Commands:
    load  threaddump   dumpheap  setflag    properties
    jcmd  inspectheap  datadump  printflag  agentProperties

cnb@plainly-backend-86787d8f85-hbhzk:/$ jattach
bash: jattach: command not found

cnb@plainly-backend-86787d8f85-hbhzk:/$ echo $PATH
/cnb/process:/cnb/lifecycle:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

Expected Behavior

Command should be in the path.
Steps to Reproduce

I managed to hit it by using the spring boot gradle-based docker image build, setup as:

tasks.named("bootBuildImage") {
    builder = 'paketobuildpacks/builder-jammy-base:latest'
    environment["BP_JATTACH_ENABLED"] = "true"
}

This is mostly likely due to how you're entering the container. The fact that the jattach layer is present, means the launcher will put it on the path, that's guaranteed by the buildpack spec. Problems can occur when you enter a container and bypass the launcher though because it doesn't have a chance to set up the path correctly.
Make sure you're entering the container by invoking the launcher. This happens automatically when your app runs, but you need to specifically invoke the launcher if you're entering a container manually and you want the environment set up.
docker run --rm --entrypoint launcher -it multi-process-app bash

https://buildpacks.io/docs/for-app-developers/how-to/build-outputs/specify-launch-process/#user-provided-shell-process
If that doesn't work, please let me know.

Yea I am trying to enter into a running container on k8s. It seems a bit complex, but this does indeed work:
kubectl exec -n namespace -it container -- /cnb/lifecycle/launcher /bin/bash

Yes, that's what you want for K8s. Glad it's working. Thanks for following up!


fix head

Two changes raced.  We all lost.  Not sure how this made it through checks...

@lavalamp P0

LGTM


return an error when the  last wal segment record is torn.

this ensures that a repair will be run when the last record in a segment is torn.
to reproduce:

kill Prometheus just after a first record is written (before a last record is written).
Start Prometheus. It show no signs of the issue and continues to write records after the torn record. This triggers a dead loop at checkpointing.

most likely the cause for:
https://github.com/prometheus/prometheus/issues/4695
https://github.com/prometheus/prometheus/issues/4842
cc @fabxc , @SuperQ
note to myself :smiling_imp:
the wal records are grouped and written in pages, each  page is 32kb and when the last record doesn't fit in the current page it is split in parts(first,last). So the last record of one page would have the first part of a record and the first record in the next page would have the last part of a record.
So in case of a crash just after writing the first part the next WAL read didn't have a  check to trigger a repair in such cases and the PR fixes this.
Signed-off-by: Krasi Georgiev<EMAIL_ADDRESS>

ping @gouthamve


Visualize probabilty of pick along well

Visualize probabilty of pick along well instead of just returning max probability prediction in each well.

Could also visualize wells across the field in terms of uncertainty of pick or how vertically spread out the top (in terms of most likely to be the top) X number of depth points are in each well. This might be a nice way to identify which wells contribute the most uncertainty to the unit thickness.


SOLR-16390: Tweak clusterprop APIs to be more REST-ful

https://issues.apache.org/jira/browse/SOLR-16390
Description
Solr has slowly been modifying its v2 APIs to align around a more REST-ful model. Many APIs have already been through this re-alignment but many more remain, including a handful of "collection-admin" APIs.
Solution
This PR chips away at this gap by tweaking Solr's "clusterprop" APIs to be more REST-ful:

single property creation+update is now available at PUT /api/cluster/properties/propName {...}
bulk property creation+update is now available at PUT /api/cluster/properties {...}
single property deletion is now available at DELETE /api/cluster/properties/propName

Tests
TODO
Checklist
Please review the following and check all that apply:

[x] I have reviewed the guidelines for How to Contribute and my code conforms to the standards described there to the best of my ability.
[x] I have created a Jira issue and added the issue ID to my pull request title.
[x] I have given Solr maintainers access to contribute to my PR branch. (optional but recommended)
[x] I have developed this patch against the main branch.
[ ] I have run ./gradlew check.
[ ] I have added tests for my changes.
[ ] I have added documentation for the Reference Guide

Currently still TODO:
- [ ] removal of the old '@Endpoint'-based v2 clusterprop APIs
- [ ] tidy, check, test, etc.
- [ ] update ref guide

Superceded by #2788; closing!


Tag entry fields should suggest existing tags

You know, cause it's a good idea and whatnot.

@sethetter are you going to tackle this for Hacktoberfest, or do you even need to since your whole job is making PRs to open source repos?


az webapp traffic-routing set to 100% from any slot other than production causes all function code to be lost

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug
I'm exploring a version of blue/green deployments using the production and a slot of a functionapp. To do this, I deploy to the unactive (0% traffic) slot, test, then change the traffic on that slot to 100%. However, I change the traffic back to 100% on the production slot, the functions all disappear and clients receive 404's when trying to hit any of them. The commands I'm using are az webapp traffic-routing set --distribution production=100 --name *** --resource-group *** and az webapp traffic-routing set --distribution warm=100 --name *** --resource-group ***. If I then change it back to the slot having all the traffic then the production functions reappear
To Reproduce

Create a functionapp  with a slot (referred to as stage in these steps) (we have it on a premium app service plan running node)
deploy some function to the production and slot of the app
run the command az webapp traffic-routing set --distribution stage=100 --name *** --resource-group ***
then run the command az webapp traffic-routing set --distribution production=100 --name *** --resource-group ***
go into the portal and notice that production slot functions are gone (may have to refresh a couple times as it seems sometimes it may take up to 30-60 seconds for them to disappear)
run the command az webapp traffic-routing set --distribution stage=100 --name *** --resource-group *** again
Go back to portal and notice production functions are now back

Expected behavior
production functions do not disappear or cleared or whatever is happening
Environment summary

Install Method: apt-get
CLI version: 2.5.1
OS Version: elementary OS 5.1.4 Hera (Built on Ubuntu 18.04.4 LTS)
Shell: bash

webapp

May be worth mentioning that this also occurs when the commands are run from an Ubuntu 16.04 build agent on Azure Devops

Also worth mentioning, and likely more interesting than the above, when I change the traffic manually in the portal, this issue does not occur which makes me think it is bound to the cli

marking this as functions app since this seems to be specific to functions & we might need to handle this differently with az functionapp traffic-routing command.


[Feature] @nxrocks/nx-flutter:flutter-shared-widget-across multiple project

Is your feature request related to a problem? Please describe
No response
Describe the idea you'd like
I don't how possible it is to have shared widget like a library, component just like the way nx-expo does it
example: Run nx g @nxrocks/nx-flutter:component component-name --project=app-name to generate a new component.
Run nx g @nxrocks/nx-flutter:lib my-lib to generate a library.
Describe alternatives you've considered
nx-expo
Additional context
No response

Hi, I have been able to generate the shareable modules, but how do i use it in another flutter project

Hi @SOG-web
Sorry for the late answer.

Hi, I have been able to generate the shareable modules, but how do i use it in another flutter project

You simply have to reference it in the pubspec.yaml file of the target project, as such:
dependencies:
  flutter:
    sdk: flutter

  my-lib:
    path: '../../libs/my-lib'

A good tutorial can be found here: https://developer.school/tutorials/create-flutter-apps-using-nx-workspaces


Redundant Rootfs on Xavier NX

On a Xavier NX, we want to have redundant Rootfs and a separate data partitioning. Are there some parameters that we could set in our config ?

Hi @om26er
Could you please give us more detail on what we want to do ?

Could you please give us more detail on what we want to do ?

Hey, we are using RAUC (https://rauc.io/) as our update mechanism (mender alternative), things work fine on the RaspberryPi since we were able to get away with using wic. However for tegra, currently with the default partition scheme, it seems to create a single rootfs parition (expected). We are looking to change the schema to have two rootfs (for redundancy) and a separate data partition.
The we'll adapt RAUC to support CBoot mostly using nvbootctrl commands.

All right, to be honest I didn't use RAUC yet. I'm using mender.
You can update the XML file the partitions layout for tegra, you could base how we are doing that via mender.
Let's see with @madisongh or @dwalkes for a better advise.

We are looking to change the schema to have two rootfs (for redundancy) and a separate data partition.

This is exactly what the mender community layer does, so you should be able to leverage this.  See https://github.com/mendersoftware/meta-mender-community/tree/dunfell/meta-mender-tegra/recipes-bsp/tegra-binaries/mender-custom-flash-layout for instance where the flash files are customized to include extra partitions for data and application B partition.
Unfortunately there's no easy way to do this today other than defining your own flash layout files, and even then it's a pain to keep up with incompatible layout changes across L4T upgrades.

Hi @om26er
First you need to modify the partition layout with your custom one. You need to add another partition with name APP_b and another one for the data (the name doesn't matter)
Then you might need to modify the init script to mount the correct APP partition (APP for slot 0 and APP_b for slot1).
platform-preboot used with Xavier family (line 11) should already be detecting the correct rootdev to mount from, as long as you comply with the APP_b naming.
Also, I recall some message from @madisongh stating that only the eMMC version Xavier NX support the dual slot config.

Also, I recall some message from @madisongh stating that only the eMMC version Xavier NX support the dual slot config.

A fix for this went in at https://github.com/OE4T/meta-tegra/pull/494

I used the partition layout that was created for mender, the image builds fine, however while flash it throws
End sector for APP_b, expected at: 33554398, actual: 59729703. I have attached the complete log below.
om26er@HomePC:~/.yocto/cfx-hub/tmp-glibc/deploy/images/jetson-xavier-nx-devkit/output$ ./dosdcard.sh
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands

[   0.0048 ] tegrasign_v2 --key None --getmode mode.txt
[   0.0058 ] Assuming zero filled SBK key
[   0.0060 ]
[   0.0063 ] Generating RCM messages
[   0.0072 ] tegrahost_v2 --chip 0x19 0 --magicid MB1B --appendsigheader mb1_t194_prod.bin zerosbk
[   0.0081 ] Header already present for mb1_t194_prod.bin
[   0.0110 ]
[   0.0120 ] tegrasign_v2 --key None --getmode mode.txt
[   0.0127 ] Assuming zero filled SBK key
[   0.0128 ]
[   0.0138 ] tegrasign_v2 --key None --file mb1_t194_prod_sigheader.bin --offset 2960 --length 1136 --pubkeyhash pub_key.key
[   0.0146 ] Assuming zero filled SBK key
[   0.0151 ]
[   0.0159 ] tegrahost_v2 --chip 0x19 0 --updatesigheader mb1_t194_prod_sigheader.bin mb1_t194_prod_sigheader.hash zerosbk
[   0.0197 ]
[   0.0207 ] tegrabct_v2 --chip 0x19 0 --sfuse tegra194-mb1-soft-fuses-l4t.cfg sfuse.bin
[   0.0217 ]
[   0.0226 ] tegrarcm_v2 --listrcm rcm_list.xml --chip 0x19 0 --sfuses sfuse.bin --download rcm mb1_t194_prod_sigheader.bin 0 0
[   0.0234 ] RCM 0 is saved as rcm_0.rcm
[   0.0265 ] RCM 1 is saved as rcm_1.rcm
[   0.0266 ] RCM 2 is saved as rcm_2.rcm
[   0.0266 ] List of rcm files are saved in rcm_list.xml
[   0.0266 ]
[   0.0266 ] Signing RCM messages
[   0.0275 ] tegrasign_v2 --key None --list rcm_list.xml --pubkeyhash pub_key.key --getmontgomeryvalues montgomery.bin
[   0.0284 ] Assuming zero filled SBK key
[   0.0291 ]
[   0.0291 ] Copying signature to RCM mesages
[   0.0300 ] tegrarcm_v2 --chip 0x19 0 --updatesig rcm_list_signed.xml
[   0.0314 ]
[   0.0314 ] Parsing partition layout
[   0.0323 ] tegraparser_v2 --pt flash.xml.tmp
[   0.0340 ]
[   0.0340 ] Creating list of images to be signed
[   0.0349 ] tegrahost_v2 --chip 0x19 0 --partitionlayout flash.xml.bin --list images_list.xml zerosbk
[   0.0356 ] MB1: Nvheader already present is mb1_t194_prod.bin
[   0.0361 ] Header already present for mb1_t194_prod_sigheader.bin
[   0.0366 ] MB1: Nvheader already present is mb1_t194_prod.bin
[   0.0398 ] Header already present for mb1_t194_prod_sigheader.bin
[   0.0402 ] adding BCH for spe_t194.bin
[   0.0433 ] adding BCH for spe_t194.bin
[   0.0450 ] adding BCH for nvtboot_t194.bin
[   0.0461 ] adding BCH for nvtboot_t194.bin
[   0.0479 ] Header already present for preboot_c10_prod_cr.bin
[   0.0497 ] Header already present for preboot_c10_prod_cr.bin
[   0.0500 ] Header already present for mce_c10_prod_cr.bin
[   0.0502 ] Header already present for mce_c10_prod_cr.bin
[   0.0508 ] adding BCH for mts_c10_prod_cr.bin
[   0.0529 ] adding BCH for mts_c10_prod_cr.bin
[   0.0911 ] Header already present for warmboot_t194_prod.bin
[   0.1287 ] Header already present for warmboot_t194_prod.bin
[   0.1291 ] adding BCH for cboot_t194.bin
[   0.1295 ] adding BCH for cboot_t194.bin
[   0.1342 ] adding BCH for tegra194-p3668-all-p3509-0000.dtb
[   0.1389 ] adding BCH for tegra194-p3668-all-p3509-0000.dtb
[   0.1411 ] adding BCH for tos-trusty_t194.img
[   0.1432 ] adding BCH for tos-trusty_t194.img
[   0.1472 ] adding BCH for eks.img
[   0.1511 ] adding BCH for eks.img
[   0.1512 ] adding BCH for adsp-fw.bin
[   0.1514 ] adding BCH for adsp-fw.bin
[   0.1525 ] adding BCH for camera-rtcpu-rce.img
[   0.1537 ] adding BCH for camera-rtcpu-rce.img
[   0.1566 ] adding BCH for bpmp_t194.bin
[   0.1598 ] adding BCH for bpmp_t194.bin
[   0.1692 ] adding BCH for tegra194-a02-bpmp-p3668-a00.dtb
[   0.1787 ] adding BCH for tegra194-a02-bpmp-p3668-a00.dtb
[   0.1805 ] adding BCH for boot.img
[   0.2001 ] adding BCH for boot.img
[   0.6539 ] adding BCH for tegra194-p3668-all-p3509-0000.dtb
[   1.1085 ] adding BCH for tegra194-p3668-all-p3509-0000.dtb
[   1.1173 ]
[   1.1174 ] Filling MB1 storage info
[   1.1174 ] Generating br-bct
[   1.1185 ] Performing cfg overlay
[   1.1185 ] ['jetson-xavier-nx-devkit.cfg', 'jetson-xavier-nx-devkit-override.cfg']
[   1.1188 ] sw_memcfg_overlay.pl -c jetson-xavier-nx-devkit.cfg -s jetson-xavier-nx-devkit-override.cfg -o /home/om26er/.yocto/cfx-hub/tmp-glibc/deploy/images/jetson-xavier-nx-devkit/output/594246/tmpi3jtr5dh1.cfg
[   1.1419 ]
[   1.1421 ] Updating dev and MSS params in BR BCT
[   1.1421 ] tegrabct_v2 --dev_param tegra194-br-bct-qspi.cfg --sdram /home/om26er/.yocto/cfx-hub/tmp-glibc/deploy/images/jetson-xavier-nx-devkit/output/594246/tmpi3jtr5dh1.cfg --brbct br_bct.cfg --sfuse tegra194-mb1-soft-fuses-l4t.cfg --chip 0x19 0
[   1.1590 ]
[   1.1590 ] Updating bl info
[   1.1600 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x19 0 --updateblinfo flash.xml.bin
[   1.1613 ]
[   1.1613 ] Generating signatures
[   1.1623 ] tegrasign_v2 --key None --list images_list.xml --pubkeyhash pub_key.key
[   1.1629 ] Assuming zero filled SBK key
[   1.2664 ]
[   1.2665 ] Generating br-bct
[   1.2676 ] Performing cfg overlay
[   1.2677 ] ['/home/om26er/.yocto/cfx-hub/tmp-glibc/deploy/images/jetson-xavier-nx-devkit/output/594246/tmpi3jtr5dh1.cfg']
[   1.2677 ] Updating dev and MSS params in BR BCT
[   1.2677 ] tegrabct_v2 --dev_param tegra194-br-bct-qspi.cfg --sdram /home/om26er/.yocto/cfx-hub/tmp-glibc/deploy/images/jetson-xavier-nx-devkit/output/594246/tmpi3jtr5dh1.cfg --brbct br_bct.cfg --sfuse tegra194-mb1-soft-fuses-l4t.cfg --chip 0x19 0
[   1.2864 ]
[   1.2864 ] Updating bl info
[   1.2874 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x19 0 --updateblinfo flash.xml.bin --updatesig images_list_signed.xml
[   1.2900 ]
[   1.2900 ] Updating smd info
[   1.2910 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x19 --updatesmdinfo flash.xml.bin
[   1.2920 ]
[   1.2921 ] Updating Odmdata
[   1.2930 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x19 0 --updatefields Odmdata =0xB8190000
[   1.2942 ]
[   1.2942 ] Get Signed section of bct
[   1.2951 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x19 0 --listbct bct_list.xml
[   1.2960 ]
[   1.2970 ] tegrasign_v2 --key None --list bct_list.xml --pubkeyhash pub_key.key --getmontgomeryvalues montgomery.bin
[   1.2978 ] Assuming zero filled SBK key
[   1.2980 ]
[   1.2980 ] Updating BCT with signature
[   1.2990 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x19 0 --updatesig bct_list_signed.xml
[   1.3001 ]
[   1.3001 ] Generating coldboot mb1-bct
[   1.3012 ] tegrabct_v2 --chip 0x19 0 --mb1bct mb1_cold_boot_bct.cfg --sdram /home/om26er/.yocto/cfx-hub/tmp-glibc/deploy/images/jetson-xavier-nx-devkit/output/594246/tmpi3jtr5dh1.cfg --misc tegra194-mb1-bct-misc-l4t.cfg --scr tegra194-mb1-bct-scr-cbb-mini-p3668.cfg --pinmux tegra19x-mb1-pinmux-p3668-a01.cfg --pmc tegra19x-mb1-padvoltage-p3668-a01.cfg --pmic tegra194-mb1-bct-pmic-p3668-0001-a00.cfg --brcommand tegra194-mb1-bct-reset-p3668-0001-a00.cfg --prod tegra19x-mb1-prod-p3668-0001-a00.cfg --gpioint tegra194-mb1-bct-gpioint-p3668-0001-a00.cfg --device tegra19x-mb1-bct-device-qspi-p3668.cfg
[   1.3021 ] MB1-BCT version: 0x1

[   1.3023 ] Parsing config file :tegra19x-mb1-pinmux-p3668-a01.cfg
[   1.3025 ] Added Platform Config 0 data with size :- 2496

[   1.3035 ] Parsing config file :tegra194-mb1-bct-scr-cbb-mini-p3668.cfg
[   1.3037 ] Added Platform Config 1 data with size :- 19640

[   1.3139 ] Parsing config file :tegra19x-mb1-padvoltage-p3668-a01.cfg
[   1.3142 ] Added Platform Config 2 data with size :- 24

[   1.3145 ] Parsing config file :tegra194-mb1-bct-pmic-p3668-0001-a00.cfg
[   1.3148 ] Added Platform Config 4 data with size :- 348
[   1.3149 ]
[   1.3149 ] Parsing config file :tegra194-mb1-bct-reset-p3668-0001-a00.cfg
[   1.3149 ] Added Platform Config 3 data with size :- 92
[   1.3149 ]
[   1.3149 ] Parsing config file :tegra19x-mb1-prod-p3668-0001-a00.cfg
[   1.3149 ] Added Platform Config 5 data with size :- 128
[   1.3149 ]
[   1.3150 ] Parsing config file :tegra194-mb1-bct-gpioint-p3668-0001-a00.cfg
[   1.3150 ] Added Platform Config 7 data with size :- 392
[   1.3150 ]
[   1.3150 ] Parsing config file :tegra19x-mb1-bct-device-qspi-p3668.cfg
[   1.3150 ] Added Platform Config 9 data with size :- 40
[   1.3150 ]
[   1.3150 ] Updating mb1-bct with firmware information
[   1.3160 ] tegrabct_v2 --chip 0x19 --mb1bct mb1_cold_boot_bct_MB1.bct --updatefwinfo flash.xml.bin
[   1.3168 ] MB1-BCT version: 0x1
[   1.3170 ]
[   1.3170 ] Updating mb1-bct with storage information
[   1.3179 ] tegrabct_v2 --chip 0x19 --mb1bct mb1_cold_boot_bct_MB1.bct --updatestorageinfo flash.xml.bin
[   1.3186 ] MB1-BCT version: 0x1
[   1.3188 ]
[   1.3196 ] tegrahost_v2 --chip 0x19 --align mb1_cold_boot_bct_MB1.bct
[   1.3205 ]
[   1.3214 ] tegrahost_v2 --chip 0x19 0 --magicid MBCT --appendsigheader mb1_cold_boot_bct_MB1.bct zerosbk
[   1.3223 ] adding BCH for mb1_cold_boot_bct_MB1.bct
[   1.3231 ]
[   1.3243 ] tegrasign_v2 --key None --list mb1_cold_boot_bct_MB1_sigheader.bct_list.xml --pubkeyhash pub_key.key
[   1.3253 ] Assuming zero filled SBK key
[   1.3256 ]
[   1.3270 ] tegrahost_v2 --chip 0x19 0 --updatesigheader mb1_cold_boot_bct_MB1_sigheader.bct.encrypt mb1_cold_boot_bct_MB1_sigheader.bct.hash zerosbk
[   1.3285 ]
[   1.3286 ] Generating recovery mb1-bct
[   1.3297 ] tegrabct_v2 --chip 0x19 0 --mb1bct mb1_bct.cfg --sdram /home/om26er/.yocto/cfx-hub/tmp-glibc/deploy/images/jetson-xavier-nx-devkit/output/594246/tmpi3jtr5dh1.cfg --misc tegra194-mb1-bct-misc-flash.cfg --scr tegra194-mb1-bct-scr-cbb-mini-p3668.cfg --pinmux tegra19x-mb1-pinmux-p3668-a01.cfg --pmc tegra19x-mb1-padvoltage-p3668-a01.cfg --pmic tegra194-mb1-bct-pmic-p3668-0001-a00.cfg --brcommand tegra194-mb1-bct-reset-p3668-0001-a00.cfg --prod tegra19x-mb1-prod-p3668-0001-a00.cfg --gpioint tegra194-mb1-bct-gpioint-p3668-0001-a00.cfg --device tegra19x-mb1-bct-device-qspi-p3668.cfg
[   1.3307 ] MB1-BCT version: 0x1

[   1.3310 ] Parsing config file :tegra19x-mb1-pinmux-p3668-a01.cfg
[   1.3313 ] Added Platform Config 0 data with size :- 2496

[   1.3325 ] Parsing config file :tegra194-mb1-bct-scr-cbb-mini-p3668.cfg
[   1.3328 ] Added Platform Config 1 data with size :- 19640

[   1.3436 ] Parsing config file :tegra19x-mb1-padvoltage-p3668-a01.cfg
[   1.3439 ] Added Platform Config 2 data with size :- 24

[   1.3441 ] Parsing config file :tegra194-mb1-bct-pmic-p3668-0001-a00.cfg
[   1.3442 ] Added Platform Config 4 data with size :- 348
[   1.3442 ]
[   1.3442 ] Parsing config file :tegra194-mb1-bct-reset-p3668-0001-a00.cfg
[   1.3442 ] Added Platform Config 3 data with size :- 92
[   1.3442 ]
[   1.3442 ] Parsing config file :tegra19x-mb1-prod-p3668-0001-a00.cfg
[   1.3442 ] Added Platform Config 5 data with size :- 128
[   1.3442 ]
[   1.3442 ] Parsing config file :tegra194-mb1-bct-gpioint-p3668-0001-a00.cfg
[   1.3442 ] Added Platform Config 7 data with size :- 392
[   1.3442 ]
[   1.3442 ] Parsing config file :tegra19x-mb1-bct-device-qspi-p3668.cfg
[   1.3442 ] Added Platform Config 9 data with size :- 40
[   1.3442 ]
[   1.3443 ] Updating mb1-bct with firmware information
[   1.3452 ] tegrabct_v2 --chip 0x19 --mb1bct mb1_bct_MB1.bct --updatefwinfo flash.xml.bin
[   1.3459 ] MB1-BCT version: 0x1
[   1.3460 ]
[   1.3461 ] Updating mb1-bct with storage information
[   1.3470 ] tegrabct_v2 --chip 0x19 --mb1bct mb1_bct_MB1.bct --updatestorageinfo flash.xml.bin
[   1.3477 ] MB1-BCT version: 0x1
[   1.3479 ]
[   1.3488 ] tegrahost_v2 --chip 0x19 --align mb1_bct_MB1.bct
[   1.3497 ]
[   1.3507 ] tegrahost_v2 --chip 0x19 0 --magicid MBCT --appendsigheader mb1_bct_MB1.bct zerosbk
[   1.3515 ] adding BCH for mb1_bct_MB1.bct
[   1.3521 ]
[   1.3533 ] tegrasign_v2 --key None --list mb1_bct_MB1_sigheader.bct_list.xml --pubkeyhash pub_key.key
[   1.3541 ] Assuming zero filled SBK key
[   1.3543 ]
[   1.3553 ] tegrahost_v2 --chip 0x19 0 --updatesigheader mb1_bct_MB1_sigheader.bct.encrypt mb1_bct_MB1_sigheader.bct.hash zerosbk
[   1.3565 ]
[   1.3566 ] Generating coldboot mem-bct
[   1.3574 ] tegrabct_v2 --chip 0x19 0 --sdram /home/om26er/.yocto/cfx-hub/tmp-glibc/deploy/images/jetson-xavier-nx-devkit/output/594246/tmpi3jtr5dh1.cfg --membct /home/om26er/.yocto/cfx-hub/tmp-glibc/deploy/images/jetson-xavier-nx-devkit/output/594246/tmpi3jtr5dh1_1.bct /home/om26er/.yocto/cfx-hub/tmp-glibc/deploy/images/jetson-xavier-nx-devkit/output/594246/tmpi3jtr5dh1_2.bct /home/om26er/.yocto/cfx-hub/tmp-glibc/deploy/images/jetson-xavier-nx-devkit/output/594246/tmpi3jtr5dh1_3.bct /home/om26er/.yocto/cfx-hub/tmp-glibc/deploy/images/jetson-xavier-nx-devkit/output/594246/tmpi3jtr5dh1_4.bct
[   1.3582 ] Packing sdram param for instance[0]
[   1.3715 ] Packing sdram param for instance[1]
[   1.3715 ] Packing sdram param for instance[2]
[   1.3715 ] Packing sdram param for instance[3]
[   1.3715 ] Packing sdram param for instance[4]
[   1.3715 ] Packing sdram param for instance[5]
[   1.3715 ] Packing sdram param for instance[6]
[   1.3716 ] Packing sdram param for instance[7]
[   1.3716 ] Packing sdram param for instance[8]
[   1.3716 ] Packing sdram param for instance[9]
[   1.3716 ] Packing sdram param for instance[10]
[   1.3716 ] Packing sdram param for instance[11]
[   1.3716 ] Packing sdram param for instance[12]
[   1.3716 ] Packing sdram param for instance[13]
[   1.3716 ] Packing sdram param for instance[14]
[   1.3716 ] Packing sdram param for instance[15]
[   1.3716 ]
[   1.3716 ] Getting sector size from pt
[   1.3726 ] tegraparser_v2 --getsectorsize flash.xml.bin sector_info.bin
[   1.3734 ]
[   1.3735 ] BlockSize read from layout is 200

[   1.3742 ] tegrahost_v2 --chip 0x19 0 --blocksize 512 --magicid MEMB --addsigheader_multi /home/om26er/.yocto/cfx-hub/tmp-glibc/deploy/images/jetson-xavier-nx-devkit/output/594246/tmpi3jtr5dh1_1.bct /home/om26er/.yocto/cfx-hub/tmp-glibc/deploy/images/jetson-xavier-nx-devkit/output/594246/tmpi3jtr5dh1_2.bct /home/om26er/.yocto/cfx-hub/tmp-glibc/deploy/images/jetson-xavier-nx-devkit/output/594246/tmpi3jtr5dh1_3.bct /home/om26er/.yocto/cfx-hub/tmp-glibc/deploy/images/jetson-xavier-nx-devkit/output/594246/tmpi3jtr5dh1_4.bct
[   1.3748 ] adding BCH for /home/om26er/.yocto/cfx-hub/tmp-glibc/deploy/images/jetson-xavier-nx-devkit/output/594246/tmpi3jtr5dh1_1.bct
[   1.3760 ]
[   1.3769 ] tegrahost_v2 --chip 0x19 --align mem_coldboot.bct
[   1.3777 ]
[   1.3787 ] tegrahost_v2 --chip 0x19 0 --magicid MEMB --appendsigheader mem_coldboot.bct zerosbk
[   1.3794 ] Header already present for mem_coldboot.bct
[   1.3797 ]
[   1.3809 ] tegrasign_v2 --key None --list mem_coldboot_sigheader.bct_list.xml --pubkeyhash pub_key.key
[   1.3816 ] Assuming zero filled SBK key
[   1.3820 ]
[   1.3829 ] tegrahost_v2 --chip 0x19 0 --updatesigheader mem_coldboot_sigheader.bct.encrypt mem_coldboot_sigheader.bct.hash zerosbk
[   1.3840 ]
[   1.3841 ] Generating recovery mem-bct
[   1.3849 ] tegrabct_v2 --chip 0x19 0 --sdram /home/om26er/.yocto/cfx-hub/tmp-glibc/deploy/images/jetson-xavier-nx-devkit/output/594246/tmpi3jtr5dh1.cfg --membct /home/om26er/.yocto/cfx-hub/tmp-glibc/deploy/images/jetson-xavier-nx-devkit/output/594246/tmpi3jtr5dh1_1.bct /home/om26er/.yocto/cfx-hub/tmp-glibc/deploy/images/jetson-xavier-nx-devkit/output/594246/tmpi3jtr5dh1_2.bct /home/om26er/.yocto/cfx-hub/tmp-glibc/deploy/images/jetson-xavier-nx-devkit/output/594246/tmpi3jtr5dh1_3.bct /home/om26er/.yocto/cfx-hub/tmp-glibc/deploy/images/jetson-xavier-nx-devkit/output/594246/tmpi3jtr5dh1_4.bct
[   1.3856 ] Packing sdram param for instance[0]
[   1.3991 ] Packing sdram param for instance[1]
[   1.3992 ] Packing sdram param for instance[2]
[   1.3992 ] Packing sdram param for instance[3]
[   1.3992 ] Packing sdram param for instance[4]
[   1.3992 ] Packing sdram param for instance[5]
[   1.3992 ] Packing sdram param for instance[6]
[   1.3993 ] Packing sdram param for instance[7]
[   1.3993 ] Packing sdram param for instance[8]
[   1.3993 ] Packing sdram param for instance[9]
[   1.3993 ] Packing sdram param for instance[10]
[   1.3993 ] Packing sdram param for instance[11]
[   1.3993 ] Packing sdram param for instance[12]
[   1.3993 ] Packing sdram param for instance[13]
[   1.3993 ] Packing sdram param for instance[14]
[   1.3993 ] Packing sdram param for instance[15]
[   1.3993 ]
[   1.4004 ] tegrahost_v2 --chip 0x19 --align mem_rcm.bct
[   1.4011 ]
[   1.4020 ] tegrahost_v2 --chip 0x19 0 --magicid MEMB --appendsigheader mem_rcm.bct zerosbk
[   1.4027 ] adding BCH for mem_rcm.bct
[   1.4033 ]
[   1.4044 ] tegrasign_v2 --key None --list mem_rcm_sigheader.bct_list.xml --pubkeyhash pub_key.key
[   1.4052 ] Assuming zero filled SBK key
[   1.4055 ]
[   1.4066 ] tegrahost_v2 --chip 0x19 0 --updatesigheader mem_rcm_sigheader.bct.encrypt mem_rcm_sigheader.bct.hash zerosbk
[   1.4085 ]
[   1.4086 ] Copying signatures
[   1.4094 ] tegrahost_v2 --chip 0x19 0 --partitionlayout flash.xml.bin --updatesig images_list_signed.xml
[   2.0581 ]
[   2.0593 ] tegraparser_v2 --generategpt --pt flash.xml.bin
[   2.0602 ] End sector for APP_b, expected at: 33554398, actual: 59729703
[   2.0605 ]
Error: Return value 4
Command tegraparser_v2 --generategpt --pt flash.xml.bin

@om26er See this wiki page.  Although it specifically mentions Mender, it would apply to your case, too.

@madisongh Thanks, a lot, after quite a bit of effort, I was able to get this thing to work. However I need to mention that with A/B rootfs partiton map, the ROOTFSPART_SIZE needs to be half (a bit less even) for the image to flash. In my case, I went with two 3GB partitions.
The issue that I now face is that while there are two rootfs partitions, nvbootctrl doesn't recognize that. How do I "fix" that ?
root@jetson-xavier-nx-devkit:~# partx /dev/mmcblk0
NR    START      END  SECTORS SIZE NAME              UUID
 1       40  6291495  6291456   3G APP               497ae9ba-d88b-4968-8fd8-015664267756
 2  6291496 12582951  6291456   3G APP_b             5ea3be53-3d4d-4ce2-9689-78785fc2f16b
 3 12582952 12714023   131072  64M kernel            6a2bc88c-02b9-4e4e-866e-691a6e1fb63b
 4 12714024 12845095   131072  64M kernel_b          69b750e9-b456-43f1-86b6-5074a5e19103
 5 12845096 12845991      896 448K kernel-dtb        1b59868f-26dc-4ffb-9403-0120d98a002f
 6 12845992 12846887      896 448K kernel-dtb_b      3a2aca55-16d1-4c7e-b99e-787e99c4c811
 7 12846888 12975911   129024  63M recovery          23cbc564-8f0e-4b63-937d-aa2b41f62972
 8 12975912 12976935     1024 512K recovery-dtb      2ce61b7c-90f7-4653-a8f6-9d5337056176
 9 12976936 12977447      512 256K kernel-bootctrl   5fbc6982-ceb7-499f-9b2b-d84cd527603e
10 12977448 12977959      512 256K kernel-bootctrl_b 66820c04-b4b1-4550-b4ea-512a91d4ad50
11 12977960 13592359   614400 300M RECROOTFS         339eb76b-58fa-44bb-bff3-630c5408561d
12 13592360 30244830 16652471   8G UDA               18ad0d50-aac6-40b4-bae9-e720df930634
root@jetson-xavier-nx-devkit:~# nvbootctrl get-number-slots
1

@om26er

The issue that I now face is that while there are two rootfs partitions, nvbootctrl doesn't recognize that. How do I "fix" that ?

See the note from @lfdmn at https://github.com/OE4T/meta-tegra/issues/499#issuecomment-731761294

Then you might need to modify the init script to mount the correct APP partition (APP for slot 0 and APP_b for slot1).

Ok, I had to run nv_update_engine --enable-ab

Ok, I had to run nv_update_engine --enable-ab

Yes, now I see.  You should be able to use the script at https://github.com/mendersoftware/meta-mender-community/blob/dunfell/meta-mender-tegra/recipes-mender/tegra-state-scripts/files/redundant-boot-install-script as a reference.

@dwalkes Thanks for the link. Looking at the script it seems that we'd have to flash the rootfs update using Nvidia's tool or is that script only flashing the bootloader ? Does Nvidia "block" updating the rootfs using external tools ?

I am going to close this issue now. We now have a redundant filesystem scheme and got our first OTA update working. Thanks everyone.

Looking at the script it seems that we'd have to flash the rootfs update using Nvidia's tool or is that script only flashing the bootloader

nv_update_engine only flashes the bootloader BUP ("Bootloader Update Payload"), see  https://docs.nvidia.com/jetson/l4t/index.html#page/Tegra Linux Driver Package Development Guide/bootloader_update_agx_tx2.html for more details.

@om26er I'm curious to what you had to do, are the steps to setup RAUC with meta-tegra descibed somewhere?

@windelbouwman We were able to get RAUC working on the Xavier NX. There are two main things that we did.

Defined a partitions scheme in OE4T that allowed for redundant rootfs
Patched RAUC to support CBoot https://github.com/rauc/rauc/pull/685

Our current tooling is unfortunately closed-source for now.

Thanks for the hints, I'll give it a try. Where would these patches be stored ideally? Is this patchwork in this layer, or in the rauc update tool?
Where did you apply the modification to the partition table? Using a bbappend file?


CLI progress steps feel one step behind

The progressive display on the CLI (which is my favorite thing ever) sometimes feels like it's behind

The above image is me submitting 3 GPU jobs to the network when it has 2 GPUs
So - the third job is waiting - that is what I would expect
Here are two UX issues from the output in the screenshot above:
running status
The running jobs look like they are still waiting to be "accepted" by the nodes because they say Node accepted the job ...
Perhaps that should say Node running the job ...
waiting to be allocated status
The bottom job has been created and submitted - I would expect a tick next to Creating job for submission to appear right away
I would expect it to be blocked on Finding node(s) for the job (because the other two nodes are busy running their jobs so that would make sense)
The above two things are probably tiny text changes but would make a massive improvement to the UX when using it

Ahhh so I see this code:
model.JobEventBidAccepted: {Message: "Node accepted the job", IsTerminal: false},

// Job is on ComputeNode
model.JobEventRunning: {Message: "Node started running the job", IsTerminal: false},

which clearly is making a dinstinction between JobEventBidAccepted and JobEventRunning - in which case I think perhaps we are not getting a JobEventRunning event

Yeah I've definitely seen the job stuck at the node selection stage, with no green tick, even though I know the job is already running.
Run a long gpu job (e.g. gpu stable diffusion) to recreate this.


CASMTRIAGE-6377-1.5 : Compressed dumpfile causing issues during Keycl…

Description
Fixes CASMTRIAGE-6377 for CSM 1.5
Tested on starlord
Checklist

[ ] If I added any command snippets, the steps they belong to follow the prompt conventions (see example).
[ ] If I added a new directory, I also updated .github/CODEOWNERS with the corresponding team in Cray-HPE.
[ ] My commits or Pull-Request Title contain my JIRA information, or I do not have a JIRA.

/backport release/1.6


Documentation of _bkSgnCntW refers to non-existent parameter _bkSgnCntW

I think this should instead be k (the security parameter).

Development of Byron code has been frozen and only potential security fixes will be applied in the future


Update k8s.io/ja/docs/setup/independent/kubelet-integration/

This is a...

[x] Feature Request
[ ] Bug Report

Problem:
Outdated content content/ja/docs/setup/independent/kubelet-integration.md.
content/en/docs/setup/independent/kubelet-integration.md 3 insertion(+), 3 delettion(-)

Proposed Solution:
Update content content/ja/docs/setup/independent/kubelet-integration.md.
For details, please execute the following command.
git diff 551489f 7b07d19 -- content/en/docs/setup/independent/kubelet-integration.md

Page to Update:
https://kubernetes.io/ja/docs/setup/independent/kubelet-integration/

これやります。

やります
/assign

/close


Build full website, add styling

In this feature, I did the following:

Added Home, Calculator, and Quote pages
Added my own style as per the requirements to improve the look and feel using React Basic Styling
Created a route for each page

@ShoiraTa Thanks for thew review


Dropbox install not working

Hey,
The following method to install Dropbox doesn't seem to be working. Can you confirm ?
Base System: Ubuntu 16.04 LTS 64-bit

@akul08 Can you help out on this? :)

Solved. Pr sent. :+1:


Cannot run app in simulator - None of the apis are hitting. How to contribute ?

How can we contribute to the project when none of the apis are working ?
Can someone please help how to run app in simulator ? Currently all screens are white.

@tariq235 set KsApi.Secrets.isOSS = true, use mock data.

what @shine15 said, but also i believe that should be the default behavior when running the OSS code. please let us know if that is not the case.
we don't allow the OSS code to hit our public API, and instead provide a mock version that serves up hard coded data immediately.

It took me a few minutes to figure out that you have to change public static let isOSS = false to public static let isOSS = true by modifying Secrets.swift under Configs group within Xcode.


download and redirect

update release file link in the history page to redirect the user to release options page and download the file

@khelwood I thought that is what is been requested, may be worth double check with @KatyTaylor

merged into devel


feat: add Shutdown to support graceful quit of HTTP Server

fix: Unify the behavior of Run/RunTLS/RunTLSWithCert. The original RunTLS/RunTLSWithCert did not apply the http.AllowQuerySemicolons and MaxHeaderBytes configuration.
📑 Description
Closes https://github.com/goravel/goravel/issues/?

@coderabbitai summary

✅ Checks

[ ] Added test cases for my code

@hwbrzzl please review again

CI still failed

Codecov Report
Attention: Patch coverage is 76.92308% with 3 lines in your changes missing coverage. Please review.

Please upload report for BASE (v1.2.x@dc868dd). Learn more about missing BASE report.

Files with missing lines
Patch %
Lines

route.go
76.92%
3 Missing :warning:

Additional details and impacted files
@@            Coverage Diff            @@
##             v1.2.x      #83   +/-   ##
=========================================
  Coverage          ?   80.77%
=========================================
  Files             ?       14
  Lines             ?      801
  Branches          ?        0
=========================================
  Hits              ?      647
  Misses            ?      120
  Partials          ?       34

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

This PR is good to go, it can be merged when v1.14.5 is released, I'll do it these two days, you can optimize goravel/fiber first. Thanks a lot 👍


MS Feedback: Avoiding layout goal seems problematic

Avoiding layout goal seems problematic
We can't think of a good design that eliminates the need to perform layout for these scenarios; using our (off thread) display tree state may be out of date and not necessarily backed by a related DOM element. Perhaps there's something we're missing?
The design goals seem conflicting: don't necessarily run layout, yet be able to report thresholdCallbacks:false and get quads with specific pixel-perfect dimensions. We feel like this should land firmly on the side of accurate reporting if we will go through the trouble of notifying at the specific times.

The avoiding layout goal is for the ads use case. For ads, they don't care about the current state of the world. They only care about what happened in the past. That's why the change record includes the element's quads and the viewport's quads. They will be able to do all their work solely based off what's in the change record, which will avoid extra layouts due to things like calling getBoundingClientRect.
Similarly, I would guess that this would be good enough for the delay loading use case.
I expect for the list view use case, you'd still getBoundingClientRect in the callback to get up to date information, so you would force a layout, but that's actually less than or equal to the amount of forced layout you'd get today without PositionObserver.
Make sense?

Closing issue. Please reopen if my previous comment does not address the concerns.


WIP: Nx task caching

What it does (so far)

adds nx for tasks caching
splits up 1 larger rollup file to distributed build scripts (order is no longer important - nx can order these dynamically based on the dependency graph)

What it doesn't do yet (and other tasks)

Nx Cloud distributed cache setup (++token santization)
~benchmarks on build (vs beta  branch)~
cache && segment tests [weird cuz right now only router project has tests (and they don't pass in beta?)]
better parameterization of rollup (getting rid of all the rollup.config files in favor of parameterizing rollup somehow - still need to figure that out)
lint strategy?

^ @tannerlinsley let me know if you have any thoughts on which of these is important right now!

Time Testing
In our branch (segmented build scripts w/ cold cache): pnpm build --skip-nx-cache  40.60s user 4.23s system 331% cpu 13.532 total
In beta branch (1 build script): pnpm build  17.92s user 1.88s system 215% cpu 9.173 total
A bit longer with segmented with a cold cache, but should be a win overall as most of the time part of the cache will be warmed.

Dep Graph:


找不到objectRuntimeType

flutter build ios-framework --release --output=xxxxx

4 fy_flutter build ios-framework --release --output=/Users/foryou/Desktop/Flutter
execFlutter build ios-framework --release --output=/Users/foryou/Desktop/Flutter
The plugin `flutter_boost` is built using an older version of the Android plugin API which assumes that it's running in a full-Flutter environment. It
may have undefined behaviors when Flutter is integrated into an existing app as a module.
The plugin can be updated to the v2 Android Plugin APIs by following https://flutter.dev/go/android-plugin-migration.
Building framework for com.example.roomModule in debug mode...
 ├─Populating Flutter.framework...                                 176ms
 ├─Add placeholder App.framework for debug...                      186ms

Compiler message:
../../../.pub-cache/hosted/pub.flutter-io.cn/flutter_easyrefresh-2.1.2/lib/src/behavior/scroll_behavior.dart:14:24: Error: The method
'objectRuntimeType' isn't defined for the class 'EmptyOverScrollScrollBehavior'.
 - 'EmptyOverScrollScrollBehavior' is from 'package:flutter_easyrefresh/src/behavior/scroll_behavior.dart'
 ('../../../.pub-cache/hosted/pub.flutter-io.cn/flutter_easyrefresh-2.1.2/lib/src/behavior/scroll_behavior.dart').
Try correcting the name to the name of an existing method, or defining a method named 'objectRuntimeType'.
  String toString() => objectRuntimeType(this, 'EmptyScrollBehavior');
                       ^^^^^^^^^^^^^^^^^
Target kernel_snapshot failed: Exception: Errors during snapshot creation: null
Failed to build bundle.

v2.1.3已修复


Confirm connection to repo and existence of master and develop branch in Vagrantfile

This is partially resolved by 4265ec27a6f59e07be0a2da772474c7e8ce1a0a5, however, Windows will still need to be accommodated.


Failed Build: Error while merging dex archives

I experienced failed build due package name. Here the error I get when using v1.0.12:
ERROR
> Task :app:mergeDexStagsecondStagingsec FAILED
~/project-name/node_modules/react-native-disable-battery-optimizations-android/android/build/.transforms/2f8d9ac22f329154eba2ca6aec913408/classes/classes.dex: D8: Type com.reactlibrary.BuildConfig is defined multiple times: ~/project-name/node_modules/react-native-disable-battery-optimizations-android/android/build/.transforms/2f8d9ac22f329154eba2ca6aec913408/classes/classes.dex, ~/project-name/node_modules/react-native-floating-bubble/android/build/.transforms/4f404a63be8db34e91eef9a57a90a10d/classes/classes.dex
com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives:
Learn how to resolve the issue at https://developer.android.com/studio/build/dependencies#duplicate_classes.
Type com.reactlibrary.BuildConfig is defined multiple times: ~/project-name/node_modules/react-native-disable-battery-optimizations-android/android/build/.transforms/2f8d9ac22f329154eba2ca6aec913408/classes/classes.dex, ~/project-name/node_modules/react-native-floating-bubble/android/build/.transforms/4f404a63be8db34e91eef9a57a90a10d/classes/classes.dex

Related error: https://stackoverflow.com/questions/60507686/type-buildconfig-is-defined-multiple-times
CAUSE
Because the package using default name com.reactlibrary which conflict with other library.
SOLUTION
I manage to make it work by changing 3 files: https://github.com/huedaya/react-native-floating-bubble/commit/c6d98b6eb8593d42c631eef8f799d59b56389d41

AndroidManifest.xml
RNFloatingBubbleModule.java
RNFloatingBubblePackage.java

TEMPORARY SOLUTION
For who need quick solution, you can use my fork by changing the package.json:
{
    "dependencies": {
        ...
        "react-native-floating-bubble": "git+https://github.com/huedaya/react-native-floating-bubble",
    }
 }

@janakact

I experienced failed build due package name. Here the error I get when using v1.0.12:
ERROR
> Task :app:mergeDexStagsecondStagingsec FAILED
~/project-name/node_modules/react-native-disable-battery-optimizations-android/android/build/.transforms/2f8d9ac22f329154eba2ca6aec913408/classes/classes.dex: D8: Type com.reactlibrary.BuildConfig is defined multiple times: ~/project-name/node_modules/react-native-disable-battery-optimizations-android/android/build/.transforms/2f8d9ac22f329154eba2ca6aec913408/classes/classes.dex, ~/project-name/node_modules/react-native-floating-bubble/android/build/.transforms/4f404a63be8db34e91eef9a57a90a10d/classes/classes.dex
com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives:
Learn how to resolve the issue at https://developer.android.com/studio/build/dependencies#duplicate_classes.
Type com.reactlibrary.BuildConfig is defined multiple times: ~/project-name/node_modules/react-native-disable-battery-optimizations-android/android/build/.transforms/2f8d9ac22f329154eba2ca6aec913408/classes/classes.dex, ~/project-name/node_modules/react-native-floating-bubble/android/build/.transforms/4f404a63be8db34e91eef9a57a90a10d/classes/classes.dex

Related error: https://stackoverflow.com/questions/60507686/type-buildconfig-is-defined-multiple-times
CAUSE Because the package using default name com.reactlibrary which conflict with other library.
SOLUTION I manage to make it work by changing 3 files: huedaya@c6d98b6

AndroidManifest.xml
RNFloatingBubbleModule.java
RNFloatingBubblePackage.java

TEMPORARY SOLUTION For who need quick solution, you can use my fork by changing the package.json:
{
    "dependencies": {
        ...
        "react-native-floating-bubble": "git+https://github.com/huedaya/react-native-floating-bubble",
    }
 }

Thanks , That Working nice


[BEAM-5884] Fix FieldType comparison in BeamSQL

This should unbreak the failing PostCommit.

@udim

Run Java PreCommit


Okular now extremely slow at rendering EPUB documents

Flipping a page now takes several seconds on some documents. This used to be fast until quite recently. E.g. /nix/store/ldw6mbpz0gkp63gaxq2zpknzvvb46zb8-okular-4.14.3 (KDE 4.14.9) is fast, /nix/store/4p1hdlxpqn56bzgr0lp85jvicsqmrb36-okular-4.14.3 (KDE 4.14.10) is slow.

The KDE5 version is also extremely slow for me. (I much preferred fbreader personally anyway.)
A quick search showed no references to epub slowness elsewhere. @ttuegel: any ideas?

The KDE 5 version is the same (Qt 4 based) for now, but I don't know why either slowed down.

I just noticed the slowness of epub on my relatively fast quad core that is faster with much larger pdf files. Okular version is 0.23.2 on Qt version 4.8.6 (though I'm running plasma 5.5.3, qt version 5.5.1)

Searching this over the internet now yields some similar issues and one bug in the KDE bug tracker https://bugs.kde.org/show_bug.cgi?id=350798.
Apparently disconnected network printers may cause issues.
Do you still experience the slowness when network is disabled or these printers removed ?
If not, the only hint in the above bug is that our build may be wrong... Not very helpful.
Anyway, could you attach examples of such slow files ?

Anyway, could you attach examples of such slow files ?

I can.
http://www.spacians.net/files/spacians.epub
22 seconds to open, scrolling is slow.
Tested at Fedora 22 (so, this bug is distributive-independent), core2duo(3166) + 4Gb RAM.
Nexus 7 with Android 6 opens this file in ~8 seconds (tested DocumentViewer and CoolReader).

BTW, I have no problem with opening PDF, even if they are large or have a lot of pictures embedded. I have no printers in current system also.

Thanks @AlexYeCu.
@edolstra, If this is really distribution independent, then we should file a bug at https://bugs.kde.org and close this issue.

@layus The slowness also happens on systems with no configured printers.

@edolstra
But where, how and why to configure printers at the system without printers?

@AlexYeCu For the current matter, shutting the network down should do it.

@layus, shutting down the network does not make Okular fster. May be there are some different bugs? Just checked: Okular opens spacians.epub in 20+ seconds with and without network, calibre viewer do the same thing in about 3 or less seconds.
Strace shows that Okular freezes  after:
libepub (II):   adding nav point item->navPoint-81 ch80.xhtml (d:1,p:81)
libepub (II):   finished parsing nav map
libepub (II):   finished parsing toc
libepub (II):   found item cover
libepub (II):   found item title_page
libepub (II):   found item ch1
…
libepub (II):   found item ch80
So, all parts of the book parsed and found.
The other thing I`ve noticed, Calibre viewer does not show a cover and starts almost instantly. And Okular shows cover, but starts slow…
Do not know if this information useful or not.

Well, deleting pictures and styles do not make Okular faster…
After removing Misc/com.apple.ibooks.display-options.xml:
libepub (II):   found item ch80
libepub (II):   parsing guides
But still slow.

I created a bug report @ KDE: https://bugs.kde.org/show_bug.cgi?id=359932 after reproducing the issue on archlinux.
My analysis with KCacheGrind seems to indicate that the application spends a lot (66%) of time in libfreetype.so, but it is unclear who calls these functions and why.

@layus Thanks, that should be very helpful. BTW, did you run that on 15.09 or master?

@edolstra I ran my tests on Arch mainly (my main OS at work), but I just tried again with NixOS 16.03pre75806.77f8f35 (Emu). Both nixos.kde{4,5}.okular have the issue.

The upstreambug is open and draw some attention.
They will need testers at some point, so you should definitely subscribe to that bug: https://bugs.kde.org/show_bug.cgi?id=359932
I also think we should close this issue, as it is not related with nix/nixos.

Thanks! I followed the issue upstream.

Are you sure this is the same issue? I'm talking about a performance regression, while that upstream issue talks about some particular epubs being slow.

@edolstra Could you check the qt version used by the different okular versions. I think the issue may come with Qt4.8.7.
I have narrowed the issue between 7acbdcd02b52fd99a826b16c832888dbff64088f and 317dd06aa438fb2e49a578a7bbefc5ed677cdc13... But then the cache misses derivations, and I do not want to bisect local qt/kde builds.
The range contains 16b40c7b which is the most probable cause for the issue.
I have cherry-picked 16b40c7b on top of 7acbdcd02b52fd99a826b16c832888dbff64088f, and we will see if it makes okular freeze.
Hang tight !
PS: I think the upstream issue is related to yours, as the freeze described appeared nearly at the same time as your issue. As I see it,  "Okular freezes on big files" == "Okular is slow on normal files".

The first path (/nix/store/ldw6mbpz0gkp63gaxq2zpknzvvb46zb8-okular-4.14.3) was indeed Qt 4.8.6. The second path is no longer available so I can't check for sure if it was using 4.8.7.
Thanks for looking into this!

And indeed running the fast Okular (/nix/store/ldw6mbpz0gkp63gaxq2zpknzvvb46zb8-okular-4.14.3) with LD_LIBRARY_PATH set to Qt 4.8.7 (to be precise /nix/store/msfjykq61a6mjj8sajaf896r98nk3nkp-qt-4.8.7/lib) makes it slow :-)

Nice ! Now, we only have to bisect qt v4.8.6 to v4.8.7 :grinning:
Fear not:
qt$ git log v4.8.6..v4.8.7 --pretty=oneline | wc -l
164

Only about 8 more steps then :-)

The problem does not seem to come from Qt itself. I have cherry-picked 16b40c7 on top of 7acbdcd, and okular is fast. Something else happens between 7acbdcd and 317dd06.
Any idea how to continue debugging ?

I have rebuilded okular from Fedora 20 okular-14.12.3 and downgraded qt-4 to 4.8.6 from 4.8.7. Opening of epubs is still too slow, but a bit faster: 17 seconds vs. 22 seconds. So, may be there are more than one regression causes the slowdown? Unfortunately the experiment is not clean enough: my system got some updates after previous attempt.

This is also my feeling after many build attempts. The okular as an epub reader has room for improvement :-). I would recommend to use calibre viewer instead.
Okular's implementaion relies on the bloated QTextDocument, a class that can manage enriched html-like documents, undo-redo and more...
Most probably that class received extra features (or even bugfixes) at the cost of efficiency.


[Fix](Row store) fix row store with invalid json string in variant type

Previous we allow invalid text as variant in PR #37794 and store as string type.But in encoding rowstore we CHECK the json is valid and store as jsonb binary field.In this PR we support the invalid json encoding as row store
Proposed changes
Issue Number: close #xxx

run buildall

run buildall


Is table extension also consume licensed table ids

Assume if client have 50 table license and all they have occupied with the new custom tables in the series of 50000 ..now almost 30 base table there is new field addition or custom code written for that table extension will create.
So how the licensed ids will behave in this scenario is there need to procure more 30 more table licenses?
AL Version- 1.22.1
NAV - 2018 on Prem

Hi @StanislawStempin  Any update on this.

Extension objects can use the same IDs as tables.
So you can use ID for example 50100 both for a new table and for a table extension of the base.


Feature: Add estimated file size

I was able to add an estimated file size that seems to estimate okay after a few progress updates.  It checks for changes because ffmpeg sporadically writes to disk and it's probably the most accurate when it writes.
                totalSize = 0;
                prevTotalSize = 0;
                etaSize = "unknown"

                                                if "total_size" in ffmpeg_output:
                                                        totalSize = int(ffmpeg_output.split("=")[1]);
                                                        if(percentage != "unknown" and percentage > 0):
                                                                if(totalSize != prevTotalSize):
                                                                        prevTotalSize = totalSize;
                                                                        etaSize = int(totalSize * (100 / percentage))
                                                                        if(etaSize > (1024*1024*1024)):
                                                                                etaSize = str(round(etaSize / (1024*1024*1024), 2)) + "G";
                                                                        elif(etaSize > (1024*1024)):
                                                                                etaSize = str(round(etaSize / (1024*1024), 2)) + "M";
                                                                        elif(etaSize > 1024):
                                                                                etaSize = str(round(etaSize / (1024), 2)) + "K";

                                                elif "out_time_ms" in ffmpeg_output:
                                                        microseconds = int(ffmpeg_output[12:])
                                                        secs = microseconds / 1_000_000
                                                        if file_duration is not None:
                                                                percentage = round((secs / file_duration) * 100, 1)

                                                elif "speed" in ffmpeg_output:
                                                        speed = ffmpeg_output.split("=")[1].strip()
                                                        speed = 0 if " " in speed or "N/A" in speed else float(speed[:-1])
                                                        if speed != 0:
                                                                eta = (file_duration - secs) / speed
                                                                seconds = round(eta % 60)
                                                                minutes = int(eta / 60)
                                                                hours = int(minutes / 60)
                                                                minutes = round(minutes % 60)
                                                                eta_string = f"{hours}:{minutes:02d}:{seconds:02d}"

                                                        if progress_handler is None:
                                                                print(f"Progress: {percentage}% | Speed: {speed}x | ETA: {eta_string} | Estimated Size: {etaSize}    ", end="\r")
                                                        else:
                                                                progress_handler(percentage, f"{speed}x", eta)

Better FFmpeg Progress no longer shows a progress strings but rather a tqdm progress bar. I do not wish to clog up the progress bar with the estimated filesize.
However, what you can do is send the estimated filesize as an additional argument to progress_handler (right now, only the percentage progress, speed and ETA are passed as arguments). This would allow the user to use the estimated filesize in a custom progress handler.
If you decide to implement this, please submit a pull request rather than opening an issue as the former is more appropriate.
A few things to note:

This is a Python project, where snake_case is the norm rather than camelCase. Variables names such as etaSize should be changed to their snake case equivalent, e.g. eta_size.

I've noticed that some of your conditions are wrapped in a pair of brackets. In python, conditons are not wrapped in a pair of brackets, so lines such as if(totalSize != prevTotalSize): need to be changed to if total_size != prev_total_size:.

Use 1000 rather than 1024 as the norm for filesizes are kilobytes (KB), megabytes (MB) and gigabytes (GB) rather than kibibytes (KiB), mebibytes (MiB) and gibibytes (GiB).

I followed some 90 step guide on how to do a pull request and seen a mention of my edit on https://github.com/CrypticSignal/better-ffmpeg-progress/pulls but when I checked again it was gone.  No email or mention here.  If there was a problem with it, I'm sure you can do the change yourself.

I've been testing the file size estimator and I'm not sure if I want to implement it. It is only accurate right at the end. Here is the output when transcoding a one-minute-long video to H.264 using libx264 at the default preset of medium. The data is in the format percentage progress, total_size (MB), estimated size (MB) and the filesize of the output video is 26.5 MB:
4 0.003556 0.0889
24 1.572864 6.5536
32 3.407872 10.6496
33 3.670016 11.12126
35 4.194304 11.983725
43 6.5536 15.24093
47 7.602176 16.174842
53 8.650752 16.322173
59 9.961472 16.88385
62 11.010048 17.758141
71 13.369344 18.830061
80 14.942208 18.67776
85 15.990784 18.812687
93 17.301504 18.603767
99 25.948329 26.210433

It took until the conversion was >70% complete before the estimate stayed within +/- 1%, and even then it is about 7 MB off the final filesize which is more than 25% off the mark.

Why regards to being unable to submit a pull request, it takes a few clicks so I'm surprised a 90-step guide exists. In case you're wondering, I did not see any pull requests so I certainly haven't discarded a pull request from you.
Don't worry about trying to submit a pull request as I correctly implemented the output filesize estimator myself for testing purposes, but I have refrained from pushing the code to GitHub because as shown in my previous comment, the accuracy is not good enough for my liking until the process is 99% complete.
With that being said, I might add the estimator with a disclaimer that the estimate is not very accurate and should be taken with a grain of salt.

I've only used it when encoding 40 minute tv shows (x265 to x264).  It starts off not too accurate but at around 2% it's accuracy improves enough to closely predict the final size.  It does fluctuate up and down a few megs to the end because of the variable bit rate.

@jmraker The progress_handler function now receives the estimated output filesize. See https://github.com/CrypticSignal/better-ffmpeg-progress/commit/aacadb0f3dacf9c38deb717c58fdb115be3aad9a.
Of course you will need to update the version of better-ffmpeg-progress that you have installed, using pip3 install better-ffmpeg-progress --upgrade.


Inconsistency between moto and boto when DynamoDb Query FilterExpression is empty

I have a conditional DynamoDB Query where, depending on the parameters, I may want to pass a FilterExpression or not.
Initially I wrote it like this:
filter_condition = Attr('permissions').contains('admin') if admins_only else ''
results = table.query(
    KeyConditionExpression=key_condition,
    FilterExpression=filter_condition
)

The tests were all fine, but then when I deployed it, the query failed because:
botocore.exceptions.ClientError: An error occurred (ValidationException) when calling the Query operation: Invalid FilterExpression: The expression can not be empty;

So I had to rewrite my code as:
if admins_only:
    results = table.query(
        KeyConditionExpression=key_condition,
        FilterExpression=Attr('permissions').contains('admin')
    )
else:
    results = table.query(
        KeyConditionExpression=key_condition,
    )

I also tried to pass None instead of the empty string, but then the tests break in moto.
It would be nice if this inconsistency was resolved in moto, it's not the first time I was hit by this.
Thanks.

Thanks for raising this @luisabtrace - marking it as an enhancement to add this validation.


nodejitsu/node-http-proxy is dead. Would you consider switching?

With the last code commit made Dec 6, 2016, and 49 PR in the queue, I'm ready to declare nodejitsu/node-http-proxy dead.
Would you consider using nxtedition/node-http2-proxy instead?

Hi @RichAyotte,
Thanks for spotting node-http2-proxy.
Think any healthy competition is always welcome.
Is there a good comparison for the two libraries?

The project is new and I believe it arose out of the need for http2 support. Perhaps @ronag can tell us more?

@RichAyotte it was built with http2 support, simplicity, and performance in mind.
The API is much smaller and simpler than node-http-proxy. So if there might be some feature that http-proxy-middleware depends on that would have to be implemented inside http-proxy-middleware instead.
Performance wise it has almost zero overhead with as far as I can tell no extra allocations (no closures etc...) that V8 is not able to optimize away.
Also, I believe it much closer follows the HTTP spec for proxy behavior.
Though, you should note that node-http-proxy is much more tested and has lots of unit tests to avoid regressions (which node-http2-proxy doesn't have yet).


Win32Exception.GetErrorMessage throws DllNotFoundException on WPA81

WinRT (on PC) is fine, but on wpa81 in particular, Kernel32's FormatMessage method seems to be unreachable, as shown in the emulator screenshot below.
I've sent an email to a Microsoft DL asking for more info since the MSDN doc for FormatMessage suggests this should work.

This intrigued me so I did a bit of search and what people are saying is that on this platform the old style dlls might not exist to redirect to the API Sets. So the P/Invoke need to be to api-ms-win-core-localization-l1-2-1.dll (Didn't test)

Thanks, @vbfox. I'll draft up a PR to propose how we deal with this.

How rampant do you think this problem is? Do all our P/Invoke methods need to support API sets or is it something that only some kernel32 methods need? Is that an implementation detail of Windows where it's unsafe to use Kernel32.dll at all for modern platforms?

Given that some OS versions require the old DLL name and some require the new one, we need to make one high-level design decision early as to whether we accommodate these differences at runtime or compile time.
Compile time
We compile twice, using #if to switch between kernel32 and the api set name.
This minimizes the DLL size and runtime overhead. We can use NuGet packaging lib\TxM folders to get folks to use the right PInvoke DLL given their target platform. If the TxM options fit well enough, this is a viable option. But it means 2-3X the number of projects in our solution as each project has to compile twice, and we'd use Shared Projects to share code between them.
We may also need to do some clever .NuProj authoring so that the DLLs get laid out in the nupkg appropriately.
Runtime
We double the number of P/Invoke methods and make them all private -- one set point at kernel32 and the other set uses the api set name. We then add yet another set of methods (we're now at triple the number of methods we have today) to make a runtime check and call into the appropriate P/Invoke method based on the OS version.
I'm leaning toward the compile-time option.

The compile-time option looks more appealing now that I've prepared changes for Kernel32.dll. It doesn't require doubling projects. It seems to align nicely with the existing portable/desktop split.

Compilation time seem better and your solution seem clean.
As long as all future platforms support API sets (and it seem to be the direction) I can't think of any problem.
We might want to update the contributing docs on how the correct set should be found and used.
Does it affect only Kernel32 ?

@AArnott I like your solution too. My only concern would be how many #if branches we'll end up having and how easy will be to maintain them.
The following is an example of the FormatMessage function located in 3 differen dlls.

Function Name
Pre Api sets
Windows 10, Windows 8.1 and Windows Server 2012 R2
Windows 8 and Windows Server 2012

FormatMessage
kernel32.dll
api-ms-win-core-localization-l1-2-1.dll
api-ms-win-core-localization-l1-2-0.dll

as you can see we have at least 3 different names.
@vbfox No, it seems to apply to more apis. If you go here and search for EnumServicesStatusEx you will find that function under api-ms-win-service-core-l1-1-1.dll.

@jmelosegui Yikes. I thought the point of API sets was that the method can always be found at the same place regardless of implementation, and yet the method is in different API sets based on Windows version?  But I wonder if the 1-2-1 vs. 1-2.0 is just a version # and we can use the smallest version even on the newest platform? I'll test that out.
So long as that is the case, There is just one #if at the top of each file so while it's tedious, IMO it's manageable.

I've confirmed that we can use the lowest version number in the API Set that it ever appears in and it still works on newer OSs. So I think we're good.


⚠ Bofrost.lu has degraded performance

In 18a740e, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1440 ms

Resolved: Bofrost.lu performance has improved in 79550ad after 6 minutes.


Add cleanup step for Nutanix E2E tests (#4418)

Description of changes:
Manual cherry-pick of #4418
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


Why is RSI indicator value different than RSI value on other platforms?

I was checking the RSI value and noticed that when RSI is 80 on KlineChart it was 77 on tradingview, same data and same period (14 days). I guess the calculation method maybe different. I know it's not a issue but has anyone tried to match the RSI to the tradingview RSI value?

If you know the Tradingview calculation method, I recommend customizing RSI to override.

tradingview RSI indicator using rma(14) to caculate avgGain avgLoss
this may be the reason


MNT: rerender

Hi! This is the friendly automated conda-forge-webservice.
I've started rerendering the recipe as instructed in #1.
If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!
Here's a checklist to do before merging.

[ ] Bump the build number if needed

Fixes #1

@conda-forge-admin rerender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/recipe.yaml) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe/recipe.yaml:

noarch: python recipes should almost always follow the syntax in our documentation. For the host section of the recipe, you should almost always use python ${{ python_min }} for the python entry. For the run section of the recipe, you should almost always use python >=${{ python_min }} for the python entry. For the test.requires section of the recipe, you should almost always use python ${{ python_min }} for the python entry. You may need to override the python_min variable in the conda_build_config.yaml/variants.yaml if the package requires a newer Python version than the currently supported minimum version on conda-forge.

Hi! This is the friendly automated conda-forge-webservice.
I tried to rerender for you but ran into some issues. Please check the output logs of the GitHub actions workflow below for more details. You can also ping conda-forge/core for further assistance or you can try rerendering locally.
The following suggestions might help debug any issues:

Is the recipe/{meta.yaml,recipe.yaml} file valid?
If there is a recipe/conda-build-config.yaml file in the feedstock make sure that it is compatible with the current global pinnnings.
Is the fork used for this PR on an organization or user GitHub account? Automated rerendering via the webservices admin bot only works for user GitHub accounts.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/11749032577.

@conda-forge-admin rerender

@conda-forge-admin rerender

I didn't mean for this one to be merged. Sorry! I was testing some stuff.

I assume you have merge rights for this repo too @beckermr right? Feel free to test things out here!


426 bug msg keyerror data

Users can pass the name of a column that has to be pre-processed more easily with parameterized pre-process columns.

rerun tests

rerun tests

\rerun tests

/rerun tests

@gpucibot merge


Empty torrent list causing the shimmer effect to appear again and again

The getTorrentList is returning null when there is no active torrent which is causing the shimmer effect to appear again and again
Log: flutter: Exception caught in Api Request NoSuchMethodError: Class 'List' has no instance getter 'keys'.
Receiver: Instance(length:0) of '_GrowableList'
Tried calling: keys

#6
Fixed the issue and refactored the code

Hey @pratikbaid3 , can I contribute to this :)

Hey @cv692001. I have actually alreasy resolved the issue in #6


PostCSS plugins to consider adding

Modular scale calculator
https://github.com/kristoferjoseph/postcss-modular-scale
More info on modular scales: http://www.modularscale.com/?100&%&1.067&js&text

postcss-grid-kiss https://github.com/sylvainpolletvillard/postcss-grid-kiss

I don't think these are generally applicable. Closing this issue.


[Feature] support sequence parallel in head layer and embedding layer

Describe the feature
they should not in separated parameter  group
Will you implement it?

[X] I would like to implement this feature and create a PR!

or at least they should not impact the value of global norm


Update setup.py for release

@HDembinski Couple edits to setup.py before releasing the new version (I can also make you co-owner on PyPI). Let me know if there are any other loose ends you can think of that need to be taken care of before releasing (it's been two years since the last time I did this and need to refresh my memory).

@dsaxton If you could add me also to PyPI that would be great, thanks!

For reference, here is the release guide for iminuit: https://github.com/scikit-hep/iminuit/blob/develop/doc/README.md

@HDembinski Agree about the changelog (I'll add that and start working on it soon). What's your username on PyPI? I'll add you as a collaborator. Nice that we can release through GitHub, that simplifies the process a lot.

Started changelog.rst with a few of the changes if you wanted to add some notes about the interface overhaul (might want to have a section that specifically calls out that these are breaking changes).

Sorry, I should have sais it is hdembins on PyPI.

Sorry, I should have said it is hdembins on PyPI.

Should be added as maintainer now

@HDembinski feel free to make / propose edits to the changelog, I'm trying to document most everything from the closed issues

@HDembinski Are you good with the minor suggested edits? Would be nice to get this out if possible (I'll likely need some help with that).

@dsaxton Deleting (yanking) old stuff is fine with me, but most people will never notice it is there. It is up to you :)


feat: store iab string for prebid and gam

did you test by hard coding a string?

One trust handles this for us


Setup PHP Parsing on Static Assets (Folio) Servers

The mobileapp.dosomething.org page needs PHP processing so we don't hit the double-opt-in limit of the MailChimp form. cc: @marahml. @mikefantini We need proper prioritization for this ticket. Whole thing will likely take about 2 hours.

@sheyd i think if this is going to take 2 hours let's just get this up now so we can finish up this job
cc: @marahml

Done and deployed. @lkpttn notified.


Test templates many times

In controller, turn
for idx in self.select_next_template(max_iter=5):
to
while True:

No, do not do that.
Just replace the following line in select_next_template method:
for i in range(max_iter):

to :
while True:


Update devcontainer Dockerfile to jammy 20241217

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

Project coverage is 93.53%. Comparing base (4b11953) to head (3001233).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #814   +/-   ##
=======================================
  Coverage   93.53%   93.53%
=======================================
  Files          20       20
  Lines        2304     2304
=======================================
  Hits         2155     2155
  Misses        149      149

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


Enable comment scanning with PoliCheck

The template has this disabled but @TravisEz13 says it's supposed to be enabled.

Closing because we have moved away from these 1ES based templates.