Cannot access page context when using extend-head feature

Issue description
I am incorporating plotly.js graphs into my website, which requires a couple of additional

{{ end }}

When I build the site, the plots won't render, but there are no errors. If I remove the conditional logic, then the plots do render, but the scripts are included in all pages including ones that don't need them.
After some digging, I found that when congos head.html partial calls the extend-head.html partial, it passes .Site as the context, which prevents accessing the page front matter. The issue is fixed when I instead pass . as the context to extend-head.html.
I am opening this as an issue because I think it's a bug, but I can't rule out the possibility of there being other considerations for passing .Site as context. I will note that the sibling partial extend-footer.html does pass the full . context when called.
Example
code
To run the example:

clone branch and build example site with npm run example

git clone --branch bug-repro --single-branch https://github.com/micah-svenson/congo.git

navigate to http://localhost:8008/congo/samples/plotly/

The plot won't render until you change the context of the extend-head.html call from .Site to . as the post mentions.

Theme version
2.6.1
Hugo version
hugo v0.118.2-da7983ac4b94d97d776d7c2405040de97e95c03d+extended darwin/amd64 BuildDate=2023-08-31T11:23:51Z VendorInfo=brew
Which browser rendering engines are you seeing the problem on?
WebKit (Safari)
URL to sample repository or website
https://github.com/micah-svenson/congo/tree/bug-repro
Hugo output or build error messages
No response

Thanks for the issue report. This isn't actually a bug as the use of .Site is intended, however I can see why this is an issue for your use case. The reason it uses the site variable is for performance reasons so that it can cache the partial when the site is built, as normally scripts and things that would be included here would be required site-wide. I have had others report this issue in the past and so I'm open to changing the behaviour as the performance gains are negligible for most sites.
The other option you have to solve your use case is to create a shortcode partial for your plotly graphs so that the required scripts are only included on pages that need them.

Ok, that makes sense. Thanks for the response!
I looked into using a shortcode for the plotly graphs, but the issue I am having there is that the resource script tag is included multiple times on single page if you have more than one plot, which will be a common use case for me. I definitely may be missing something obvious but I couldn't find a way to omit the script tags if a plotly partial had already been included in the current page.
I did a little profiling, and though the scripts are only fetched 1x each, they are executed once for each plot they are included with. This adds 50-100 ms per plot to initial page load , which added up to a ~1 second delay in load time for 5 plots. The code for the plotly partial is included below for context.
{{ $json := .Get "json" }}
{{ $height := .Get "height" | default "200px" }}
{{ $id := .Get "id" }}

If there isn't a solution to creating an isolated partial without performance hits, then I think it could make sense to update the behavior of extend-head. My impression of extend-head was that it allows the user the ability to add arbitrary customizations to the head of the document. It is also the natural place I was looking to add the plotly scripts. I think updating the partial to accept all context would be more flexible and intuitive for users of the theme and would afford an end user more control over customization without direct changes to the theme. It would also behave the same way as extend-footer, which I think would be better from a consistency and usability perspective.
If on the other hand the performance penalty of making this change is too great, then I think it would at least be worth adding some documentation that declares that as expected behavior. I would be happy to submit a PR for any of the above.

Thanks for the extra detail here. I've decided it no longer makes sense to cache the extended head partial as it is just stunting flexibility for no reason. A while back the extended footer partial had the same issue and I removed .Site from there and so it makes little sense to have two different behaviours for the same feature. I'll merge your PR in and that should resolve this issue for you.

Awesome, thank you!


fix: refactor column selection logic for Polars

Related to #340, pola-rs/polars#16242, pola-rs/polars#16250.
This PR provides a quick fix for the column selection logic in Polars. Further investigation may be needed from the team.

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

Project coverage is 85.74%. Comparing base (b290e66) to head (cf83e25).
Report is 10 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #360      +/-   ##
==========================================
+ Coverage   84.72%   85.74%   +1.02%
==========================================
  Files          41       41
  Lines        4346     4329      -17
==========================================
+ Hits         3682     3712      +30
+ Misses        664      617      -47

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

Shoot, thanks for catching this! It seems like there are three behaviors in the new polars release that broke our current approach (afaict this is just a side-effect of us living on the bleeding edge of expand_selector() 😈 ):

quick fix: expand_selector() no longer accepts a list
quick fix: expand_selector() no long accepts a raw string or int
bigger discussion: expand_selector() only sometimes considers .exclude() a selector

I've opened an issue on polars RE the .exclude() behavior:

https://github.com/pola-rs/polars/issues/16448

Here is the docs preview I've pushed to a branch:
https://docs-preview-test--gt-python.netlify.app/articles/intro.html

@machow and @rich-iannone , everything looks great. It seems the developers from Polars are actively supporting and clarifying our use case, which is fantastic.


Accept a DOM element as container option

I want to be able to provide the DOM element of the container directly instead of through a selector.
In my use-case there is no unique selector for the container.

Makes sens, added a fix for this and updated the README. Will publish soon.

Thanks!

Published in v1.1.6

I've just tested the v1.1.6, works great!


fix scrolling issues on chrome (android & desktop)

On Chrome, when only specifying flex: 1 for the inner view, the height of the inner view is the height of the content and not the height of its parent - therefore, scrolling doesn't work. As far as I know it is only true for Chrome (tested on safari for iOS/OSX). The solution is the add height: 100%.
In any way, specifying the height is 100% is a good practice because this is the truth in this case.

BTW, if you want to reproduce the issue, just build any reapp app that has a list (like the hacker news example) and see that scrolling doesn't work in chrome

As a workaround (until this version is published), I manually added this style to the theme:
I added View.js file to app/theme/styles
export default {
    inner: {
      height: '100%'
  },
};

and modified app/theme/styles.js
import { makeStyles } from 'reapp-kit';
const requirer = name => require(`./styles/${name}`);

// override default component styles

export default makeStyles(requirer, [
  'TitleBar',
  'View' // Add View if it's not already here
]);


Feat/741 Known issues modal

closes #750

Adds modal which appears on startup, once dismissed it doesn't appear again as we set a bool in local storage to tell if the user has already dismissed the modal

@candida-d You will probably want to change the language here.
@campbellssource This opens on startup regardless of page. Do you only want to show it on the staking page?

@mattrussell36 I made some suggested changes, but had a quick chat with Michael as well and he suggested that we also link to the known issues in the footer (so the copy reflects that). Can that also be flagged?


[stable/prometheus-operator] Fix coreDns.service.selector to be cored…ns instead of kube-dns

What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

You can make this change yourself in a local deployment. Changing defaults would introduce a breaking change to anyone who is  already using this chart. The specific value depends on the method used to provision the cluster
/hold


Sfx Handler: Batch by dimension + Support for multiple auth tokens

For Sfx handler,

Add ability to batch metrics by some dimension key before sending
them to the provider endpoint
Add ability to use more than one authtoken

Note: This supersedes https://github.com/Yelp/fullerite/pull/324

@poros @dichiarafrancesco @kokje
Cherry picked changes from PR #324 into this. I borked the branch badly (don't ask -_- ).
Did something change in the build system? I am able to successfully run make on local.

Rebased with latest master!

lg2m!


Added support for new event envelope

[ x] - npm test succeeds
[ x] - Code coverage does not decrease (if any source code was changed)
[x ] - If applicable, PR includes appropriate documentation changes

@jmdobry pls review


Add release github action workflow

/assign @wayblink
Please help review and approve.
This PR is used to release binary when a tag is created.
I have tried it in my own repo and you can see it at https://github.com/zhuwenxing/milvus-backup/releases


English language toolchain host

Could you please upload your toolchain to a another server that is english. Ive tried to log into that baidu server but it needs member ship and i cant figure out how to get one.
something like mega upload or something. or even just a zip file in its own repository would be awsome.
Thanks.

Give me your e-mail~

<EMAIL_ADDRESS>

I'll try to use email  ~Later ~Lat ~L


HBASE-21521 Expose master startup status via web UI (#4788) (#5021)

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  1s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 38s
branch-2 passed

+1 :green_heart:
compile
2m 25s
branch-2 passed

+1 :green_heart:
checkstyle
0m 36s
branch-2 passed

+1 :green_heart:
spotless
0m 44s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
1m 28s
branch-2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 20s
the patch passed

+1 :green_heart:
compile
2m 20s
the patch passed

+1 :green_heart:
javac
2m 20s
the patch passed

-0 :warning:
checkstyle
0m 34s
hbase-server: The patch generated 1 new + 9 unchanged - 1 fixed = 10 total (was 10)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
17m 35s
Patch does not cause any errors with Hadoop 2.10.2 or 3.2.4 3.3.4.

+1 :green_heart:
spotless
0m 43s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
1m 34s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 12s
The patch does not generate ASF License warnings.

38m  3s

Subsystem
Report/Notes

Docker
ClientAPI=1.42 ServerAPI=1.42 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5026/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5026

Optional Tests
dupname asflicense javac spotless spotbugs hadoopcheck hbaseanti checkstyle compile

uname
Linux 5c2292ab317c 5.4.0-135-generic #152-Ubuntu SMP Wed Nov 23 20:19:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / ee618d5fdf

Default Java
Eclipse Adoptium-11.0.17+8

checkstyle
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5026/1/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

Max. process+thread count
82 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5026/1/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 10s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m  1s
branch-2 passed

+1 :green_heart:
compile
0m 40s
branch-2 passed

+1 :green_heart:
shadedjars
4m 16s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 25s
branch-2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 43s
the patch passed

+1 :green_heart:
compile
0m 40s
the patch passed

+1 :green_heart:
javac
0m 40s
the patch passed

+1 :green_heart:
shadedjars
4m  8s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 24s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
209m 33s
hbase-server in the patch passed.

231m 29s

Subsystem
Report/Notes

Docker
ClientAPI=1.42 ServerAPI=1.42 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5026/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5026

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 7905be32fe34 5.4.0-135-generic #152-Ubuntu SMP Wed Nov 23 20:19:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / ee618d5fdf

Default Java
Temurin-1.8.0_352-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5026/1/testReport/

Max. process+thread count
2776 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5026/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  4s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 35s
branch-2 passed

+1 :green_heart:
compile
0m 46s
branch-2 passed

+1 :green_heart:
shadedjars
4m 36s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 27s
branch-2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 26s
the patch passed

+1 :green_heart:
compile
0m 48s
the patch passed

+1 :green_heart:
javac
0m 48s
the patch passed

+1 :green_heart:
shadedjars
4m 35s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 26s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
214m 47s
hbase-server in the patch passed.

239m  9s

Subsystem
Report/Notes

Docker
ClientAPI=1.42 ServerAPI=1.42 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5026/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5026

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 121b0756dc11 5.4.0-137-generic #154-Ubuntu SMP Thu Jan 5 17:03:22 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / ee618d5fdf

Default Java
Eclipse Adoptium-11.0.17+8

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5026/1/testReport/

Max. process+thread count
2317 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5026/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Dead project?

This project looks like it is lagging a little from the latest Modernizr ;-)
I might be interested in contributing a bit. Could you give me an idea of the amount of work to port new Modernizr functions?
Did you have some sort of generator to get stub impls from the Modernizr JS?

@jDramaix @PerWiklander is there anything update about this?

I never heard more in this. And now I haven't touch GWT in a few years either (it's all scalajs + react these days).


E492: Not an editor command

When i call :Esformatter is show error:
Error detected while processing function <SNR>48_EsformatterNormal:
line    5:
E492: Not an editor command: :lcdE:\thuviencauhoi\src
line   23:
E492: Not an editor command: :lcdE:\thuviencauhoi

Same error!did anyone resolved this!


Decouple updating Kubernetes and Lokomotive components when updating Lokomotive.

Considering an analogy of Ubuntu system:
Executing sudo apt upgrade doesn't update the Ubuntu operating system , my desire and the command's intention are in sync with each other i.e Upgrade the software packages and that's what I think of Lokomotive components.
If I specifically want to upgrade the operating system to a newer version along with newer version of software packages I would call upon a different command sudo apt dist-upgrade / sudo apt full-upgrade which is what I think of Kubernetes as i.e equivalent of an OS.
Currently Lokomotive does not separate from updating Lokomotive cluster( i.e Kubernetes version) and Lokomotive components when executing lokoctl cluster apply with a newly released Lokomotive version.
What this entails is that the user must consume the lokomotive binary in full (i.e update cluster and the updated components).
This creates a problem if the desire is not to frequently update the Kubernetes versions rather only the Lokomotive components.
As per the latest container-report by Datadog, it was observed that the most popular version of Kubernetes was v1.15 even though it was released 17 months ago. However it is not clear whether this is due to the desire not wanting to do frequent updates or easy hassle free upgrades is a gap in the market, so some research is required to understand the Why.

This is something we should approach very carefully, as implemented, would greatly expand our test matrix. I definitely agree that we should have a good understanding why running older version is the most popular case. To be honest, my guess is that people can't keep up with updates and testing when you have OS -> Kubernetes -> Infrastructure components -> Application Manifests.


Support DATA frames with zero-length application data

Motivation:
DATA frames with zero-length application data would cause the state
machine to wait for more bytes to continue. This could cause consuming
code to deadlock.
Modifications:
Updated the frame parser to only require more data when there are
remaining bytes in the payload and there are zero readable bytes.
Result:
DATA frames with zero-length application data can be parsed.

@swift-nio-bot test this please


User can add items to shopping cart.

Able to add items to a shopping cart that a user would like to purchase.

[ ] Summary: Allow users to add desired items to their shopping cart for later purchase.
[ ] Done criteria: Ensure that users  can click on an item to add to their cart, and the cart updates to reflect the added item.


deleting an open file does not close the tab

when i tried to close the tab of the deleted file (a pasted image) it crashed
thread '<unnamed>' panicked at libs/content/workspace/src/workspace.rs:505:14:
called `Result::unwrap()` on an `Err` value: LbError { kind: FileNonexistent, backtrace: None }
stack backtrace:
   0: _rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::result::unwrap_failed
   3: workspace_rs::workspace::Workspace::open_file

This happens properly on master


[BUG] Blue screen appears when assigned USB MIDI 2.0 driver to a UMP device

Applies To
Driver?
Describe the bug
When try to assign the USB MIDI 2.0 driver to a UMP device, sometimes blue screen appeared.
There may be one out of three successful attempts.
To Reproduce
ZoB.uf2.zip
Please find attached binary which is a firmware of ProtoZOA. It can reproduce this bug.
Note: this firmware has One Group Terminal Block with 16 Group Terminals.

Thanks. Assigned to @AmeNote-Michael

@dmiura have you tried with any other MIDI 2.0 devices, by any chance? (Don't name them here if they are confidential, please). I want to make sure the issue isn't specific to the ProtoZOA. I have a synth behind me that connects with the new driver and sends/receives UMP without problems.

@dmiura actually, the fact that you mentioned a Blue Screen makes me wonder. Was it a green screen or a blue screen? If blue, that means you aren't running the Insider Canary build that is required to support the new USB MIDI 2.0 class driver.

@dmiura I have tried multiple plug / unplugs of the ProtoZOA code you provided with driver. I am up to about 25 times without Green Screen - same question @Psychlist1972 had, are you sure you were running on a system with Canary build?
Were you running an application at same time? I tried to have MIDI Monitor from console app running a couple of times, but of course this needs to be restarted every unplug / plug cycle. Still I had not had a crash.

@Psychlist1972 , @AmeNote-Michael

have you tried with any other MIDI 2.0 devices

Yes, we tried with another MIDI 2.0 device, but this issue didn't occur.

Was it a green screen or a blue screen?

It was Green screen.

are you sure you were running on a system with Canary build?

Yes, we were running on the system with Canary build.
We will  check it again, then I will post if we found additional hint.

@dmiura thank you for the video. Please confirm you are using latest version of driver. The Attestation signed one or one you compiled on your own?
As indicated, I am not getting the same result. Therefore can you please reproduce again and then send resulting crash dump file created by restart (let green screen finish gathering info and send resulting file). I will also try again to reproduce.
Also, have you tried same on a Mac?
Lastly, if willing, you able to share your descriptor code for ZoB? Are you using the latest tusb_ump files from midi2.dev or your own implementation?
Michael

@AmeNote-Michael
I've been writing this report instead of other member who are checking driver behavior.

Please confirm you are using latest version of driver.

usbmidi2.inf_amd64_d320d9eba1fe0f4b\USBMidi2.sys
DriverVer = 12/14/2023,<IP_ADDRESS>
This driver was attached Developer Preview 2

The Attestation signed one or one you compiled on your own?
Unzip USBMIDI2_<IP_ADDRESS>.zip, signature is "Microsoft Corporation"

As indicated, I am not getting the same result

Sometime, it occurred after 10 - 20 seconds, when updated driver. It means it doesn't occur everytime.

Therefore can you please reproduce again and then send resulting crash dump file created by restart (let green screen finish gathering info and send resulting file). I will also try again to reproduce.

I uploaded Criticalfdump.txt  in this comment.
Criticalfdump.txt

Also, have you tried same on a Mac?

There is no problem on Mac

Lastly, if willing, you able to share your descriptor code for ZoB?

Uploaded usb_descriptors.cpp.
usb_descriptors.cpp.zip

Are you using the latest tusb_ump files from midi2.dev or your own implementation?

We are using tusb_ump files downloaded from https://github.com/midi-mma/tinyUSB_ProtoZOA
We will try tusb_ump files from midi2.dev.

If this is related to power management like the other green screen issues, this should be fixed in the next attestation-signed driver.

I met Green Screen on Developer Preview 5, when I update USBMIDI2_<IP_ADDRESS> to ZoB by Device Manager.
It's occurred once three times.
Windows 11 version is 24H2 26063.1
System Log by Event viewer is enclosed.
systemlog.txt

Memory dump file at Green Screen.
MEMORYDUMP.txt

Issue due to improper call in D0Exit power management routine. The D0Entry and D0Exit are not required for this driver implementation anymore as the management of continuous reader moved to Run / Pause state functions managed by KS_Stream. This update is in pull request #301: https://github.com/microsoft/MIDI/pull/301

Reopening until we ship to customers.

There is currently an issue with USBAudio.sys (original MIDI driver) that when you update to USBMidi2.sys, a timeout occurs that USB Midi2.sys does not understand causing crash.
Workaround for the issue is to disconnect the USB device immediately after update to USBMidi2.sys, prior to green screen. Then wait about 10s before re-connecting the USB device.
By removing the USB device, it will force the USB Stack to remove the driver fully and cancel any related resources including the timer.
When you re-insert the USB device, it should install USBMidi2.sys and continue from there.
NOTE: this is regardless if a USB MIDI 1.0 or USB MIDI 2.0 device, the error is going from using the USBAUDIO.sys driver and updating to USBMidi2.sys driver.

To add to what @Amenote-Michael has said:
This is a fix we need to deploy in Windows. There's nothing the new driver can do here.

Assigning to @garydan42 to track when this fix goes into public Windows builds. Changed area to reflect where the problem resides.

Related Issue #198

This is in public Insider builds now.


[WFLY-17933] Eliminating deprecated javax.sql.api module usages

https://issues.redhat.com/browse/WFLY-17933

@ropalka This currently has a conflict, can you please resolve?  Also please remove the rebase-this label once done.

Done @darranl

Sorry @ropalka one more rebase needed


Mark constructors of abstract classes protected

Problem:
Sonar found 6 cases where constructors of abstract classes are declared public:

dropwizard-configuration's BaseConfigurationFactory
dropwizard-configuration ConfigurationException 1, 2
dropwizard-jersey ErrorEntityWriter, LoggingExceptionMapper
dropwizard-migrations CloseableLiquibase

Solution:
Make these constructors protected. You can't construct an abstract class directly.
Result:
I think no change.

@rhowe Thanks for your contribution!
Unfortunately these are breaking changes in public APIs, so we won't be able to apply them until Dropwizard 3.0.0 if at all.

@rhowe Thanks for your contribution!
Unfortunately these are breaking changes in public APIs, so we won't be able to apply them until Dropwizard 3.0.0 if at all.
See also: https://wiki.eclipse.org/Evolving_Java-based_APIs_2

I don't see a problem in not applying this change at all tbh, since I doubt the current state of affairs is really a problem, but is it really a breaking change?
The classes are abstract, which means nothing can call the constructor directly except either themselves or a subclass. Doesn't that mean that declaring the constructor public is equivalent to declaring it protected?

I think we can bring this to 3.0.0, so this can be merged to release/3.0.x IMO.


feat: C'est qui le pro

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

GitHub release
v1.0.0

Your semantic-release bot :package::rocket:


[Bug] PulsarAdminBuilderImpl overrides timeout properties passed through config map

Search before asking

[X] I searched in the issues and found nothing similar.

Version
master commit id 0e149ef
Minimal reproduce step
PulsarAdminBuilder allows configuration of PulsarAdmin either by using the setters on the builder, or by using the loadConf method that takes in a map of configuration properties.
The properties:

readTimeout
connectionTimeout
requestTimeout

can currently only be correctly applied when using the builder setters (e.g. setReadTimeout) because the build() method accesses these as private fields in PulsarAdminBuilderImpl. If these properties are set through the config map, loadConf does not update these private fields. This results in the config values being ignored and overridden by the default values in PulsarAdminBuilderImpl
What did you expect to see?
Properties should be applied correctly using config map or builder methods,
What did you see instead?
Timeout properties passed in via config map get overwritten by the builders default values.
Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

@alpreu Do you want to push a PR to revert https://github.com/apache/pulsar/pull/17313? Anyway, I think we should revert it first.


Update authentication.md

Can someone please have a look into this PR request.

@rahuldimri, what’s the benefit of this PR?

Just correcting the format. Its not going to add any benefit, but it will help us to make the document in correct format going forward as well. All the document headlines need to be started with capital letter.
Let me know if you have any other thought on this.


Http Integration Tests: Create tests to support HTTP(3)

This issue involves creating the below test cases for HTTP as well:
Source: integration_tests/commands/async/

dbsize_test.go
decr_test.go
del_test.go
deque_test.go
discard_test.go

Steps:

Create the corresponding tests for these commands in integration_tests/commands/http.
Use set_test.go as a reference, and how to alter the input and output to match JSON structures from RESP.
Run the tests and fix issues with command parsing in HTTP.

If you need to do anything custom to support HTTP, let @pratikpandey21 @lucifercr07 know.

I'd like to work on this

I don't have the permissions to assign you, but please go ahead and start @shardul08

Hello @shardul08,
There has been no activity on this issue for the past 5 days.
It would be awesome if you keep posting updates to this issue so that we know you are actively working on it.
We are really eager to close this issue at the earliest, hence if we continue to see the inactivity, we will have to reassign the issue to someone else. We are doing this to ensure that the project maintains its momentum and others are not blocked on this work.
Just drop a comment with the current status of the work or share any issues you are facing. We can always chip in to help you out.
Thanks again.

Hello @shardul08,
There has been no activity on this issue for the past 5 days.
It would be awesome if you keep posting updates to this issue so that we know you are actively working on it.
We are really eager to close this issue at the earliest, hence if we continue to see the inactivity, we will have to reassign the issue to someone else. We are doing this to ensure that the project maintains its momentum and others are not blocked on this work.
Just drop a comment with the current status of the work or share any issues you are facing. We can always chip in to help you out.
Thanks again.

Hey @arpitbbhayani can I work on this?

@rigved-telang assigned, thanks for contributing.

Thanks @lucifercr07.

Hello @rigved-telang,
There has been no activity on this issue for the past 5 days.
It would be awesome if you keep posting updates to this issue so that we know you are actively working on it.
We are really eager to close this issue at the earliest, hence if we continue to see the inactivity, we will have to reassign the issue to someone else. We are doing this to ensure that the project maintains its momentum and others are not blocked on this work.
Just drop a comment with the current status of the work or share any issues you are facing. We can always chip in to help you out.
Thanks again.

@arpitbbhayani I am working on it, the test for db_size has been written. This is the first time I am working on DiceDB and with golang which is why the progress is a little slower. Apologies for the delay

Also, I was not putting the issue number in my commits. Will be mindful of this going forward.

Kindly review this PR: https://github.com/DiceDB/dice/pull/1211
@lucifercr07 @pratikpandey21


Permissions / License for use

Hey @sarojaerabelli
by any chance would you consider including a "LICENSE" file to explicitly state how others  are permitted to (or not) to use your work? I realise that you state the following in the setup.py: https://github.com/sarojaerabelli/py-fhe/blob/7a89f53ded4db035e982012535af927036f6aa26/setup.py#L8 but I just wanted to clarify.
I want to take a further look into your implementation to implement a pure python alternative back-end for one of my (heavily in development) libraries but I realized that there was no LICENSE file to elaborate on usage. I could always go through gentries papers to create my own but I figured there is little use in duplicating effort when I can improve on existing work instead to the benefit of all involved. I am particularly keen on the CKKS bootstrapping support for example, even if you describe it in your commits as being slow, as that can always be improved.
Thanks, and let me know how you feel about this use case/ include a LICENSE if you deem it appropriate.

Added the MIT license. Feel free to use it how you wish!


Remove run-script option from Html specimen

Somehow it feels like a really bad idea to parse script tags from HTML code and execute them.
We still have the per-page scripts option if we really need to e.g. instantiate a jQuery date picker or something like that …

I remember: this was added for iframes, i.e. when a component is rendered not directly on a page but in an iframe (we had this option at a certain point a while back), we needed to be able to run a script within the iframe. I think this is no longer needed.

Am 18.11.2015 um 18:22 schrieb Jeremy Stucki<EMAIL_ADDRESS>Somehow it feels like a really bad idea to parse script tags from HTML code and execute them.
We still have the per-page scripts option if we really need to e.g. instantiate a jQuery date picker or something like that …
—
Reply to this email directly or view it on GitHub https://github.com/interactivethings/catalog/issues/67.


Fix snapshot cache issue take 2

Second take on #173, inspired by @svara's comment.

@jayohms, does this flag name work for you?

I would prefer that we main "snapshot" in the flag name so it's clear the cache doesn't refer to anything else. How about snapshotCacheNeedsClearing?

How about isSnapshotCacheStale? That way we can use the is* prefix Swift encourages.

Love it 👍

Closed in favor of #183.

@svara, I closed this in favor of #184 to address @pfeiffer's comment.


Update Deployment Documentation

A simple documentation update that changes the following:

Updates the versioning of Zarf when installed on an isolated network
Updates the referenced version of whisper
Removes the references to Dockerfile.gpu

One of the commits is not signed

One of the commits is not signed

My bad, I'll fix it


$rinserepeat bug

$rinserepeat seems to be bugging out differently on different browsers,
On Firefox, all files are enqueued the same whether or not it is set to true/false.
On Chrome, if the file selection is identical to the last one, they won't be queued
Maybe we should add a new option "$unique" and only allow for new file names in the queue.
I've thought about adding a check against the currently enqueued files before each and every one is pushed to the queue...
Not sure if there is a better way.

Well, $rinserepeat option does exactly what the readme says: it cleans an input after every selection. Can't really reproduce any bugs, for me it works as expected. If for you it does not, please create a fiddle showing that.
There can be some inconsistencies among different browsers when the option is set to false, but that's not what this option is intended to fix. When it's false, it just does nothing, when it's true, it cleans an input allowing you to reselect the same files again, that's it.
As for the uniqueness, it's surely achievable as a new feature, and probably a new option like you've said.


Publishing v0.10.0

Codecov Report
Patch coverage has no change and project coverage change: +0.01% :tada:

Comparison is base (ae12700) 87.69% compared to head (8c56bea) 87.70%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #414      +/-   ##
==========================================
+ Coverage   87.69%   87.70%   +0.01%
==========================================
  Files          39       39
  Lines        8931     8931
==========================================
+ Hits         7832     7833       +1
+ Misses       1099     1098       -1

see 1 file with indirect coverage changes

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


Links don't look like a link when used inside a code line

I've noticed that whenever a link is used inside backticks in markdown, it's hard to know if it's a link and I don't know if that's intentional
Example:

There is no way to know it's a link unless you hover over it, maybe slightly change the styling of it should be better?

thanks!


[customization] Working with custom themes & Extend Theme issue

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
@siriwatknp
Link to live example: https://oxygen-sandbox-git-main-rafcin.vercel.app/
Repo: https://github.com/Rafcin/oxygen-sandbox/tree/main
Steps:

Build the project by running pnpm sandbox:build.
Run pnpm dev
Load the app and use the navigation light dark mode button to see the issue.

Current behavior 😯
I've been confused by the MUI documentation and best practices, and I apologize if any of this is wrong.
So I've been following https://mui.com/material-ui/experimental-api/css-theme-variables/customization/#color-schemes trying to make a component library built on MUI that has a dark and light mode. For the most part, it works, I have a small personal site deployed with it currently, and it works really well! Now when the new 12 MUI release came out on the 6th (https://github.com/mui/material-ui/releases/tag/v5.11.12), I updated the packages, and when I used my site in dev mode, my theme would constantly stay white and use the default theme values. I found out moments ago, when gutting my project and making a minimal reproduction after removing all the important stuff, this issue appeared, and I'm still on version 11. Perhaps this isn't an extended theme issue, or maybe it is; I'm actually really unsure.
Also, this repo contains my little component library I've been working on for a while, I really love MUI and I have an obsession with AirBnB, and this is my attempt at trying to meld the two together. I'm really happy with it, and if you happen to look at the code and see something I should change or improve, let me know, it's not great code, but it's been slowly improving!!!
Edit After writing this, I deployed the app to Vercel, and magically it works on Vercel; I really don't understand the issue now; I have this weird, odd feeling it's Emotion, and Emotion already drives me nuts with the Next 13 issues and all.
Expected behavior 🤔
Usually when you switch modes it should go from dark to light or light to dark depending on the system default.,
Context 🔦
For now, I want to get light and dark themes to work, but my hope with this issue is to raise some more awareness regarding themes and extend MUI components for custom component libraries. It took me a while to make this component library, and I hope to turn this into a component library that has a set of themes people can use and components that are helpful that MUI doesn't offer out of the box. It would be nice to see the theme system be more flexible and work with theme types to be more accessible.
Your environment 🌎

npx @mui/envinfo
 System:
    OS: Linux 5.19 Ubuntu 22.04.2 LTS 22.04.2 LTS (Jammy Jellyfish)
  Binaries:
    Node: 19.7.0 - ~/.nvm/versions/node/v19.7.0/bin/node
    Yarn: 1.22.17 - /usr/bin/yarn
    npm: 9.5.1 - ~/.nvm/versions/node/v19.7.0/bin/npm
  Browsers:
    Chrome: 111.0.5563.64
    Firefox: Not Found
  npmPackages:
    typescript: ^4.9.5 => 4.9.5

It may be related to the changes done in https://github.com/mui/material-ui/pull/35739, but I can't run locally the repository that you've shared. I am on Windows. Can you check if everything is setup correctly? I am getting this error:
@oxygen/sandbox:dev: Module not found: Can't resolve 'swiper/css'

Looks like it's related to some of the last commits on the repo.

You can also try to setup a codesandbox with the reproduction if it's easier.


Compilation Failure

Dear all,
I've been trying to compile and install OpenNI2 on my RaspBerry PI modèle B+ including ARM1176JZF-S core for 3 days, and I cannot fix problems.
Here is what I did in details:
* sudo apt-get install git g++ python libusb-1.0-0-dev freeglut3-dev openjdk-6-jdk graphviz
* sudo apt-get install libudev-dev
keep OpenNI2
* https://github.com/kalectro/OpenNI2.git
Uncompress OpenNI2-gumstix-fixes.zip on Rasp and check the CRC
*CRC is good: 56cc12233eed6aea9efe9f64254d507e183dbef4
___ 1 ____________________________________________________________________
In OpenNI2-Master/ThirdParty/PSCommon/BuildSystem modifying
*CFLAGS +=  -mtune=arm1176jzf-s -mfloat-abi=hard
___ 2 _____________________________________________________________________
The second file is OpenNI2/Redist/Redist.py. Go to line 534 to find this:
* compilation_cmd = "make -j" + calc_jobs_number() + " CFG=" + configuration + " PLATFORM=" + platform + " > " + outfile + " 2>&1"
Then duplicate the line, comment the original and change the copied line:
* compilation_cmd = "make -j1" + " CFG=" + configuration + " PLATFORM=" + platform + " > " + outfile + " 2>&1"
___ 3 ____________________________________________________________________
* cd OpenNI2-gumstix-fixes
* make

Till there evrything seems to be ok.
Compilation took arround 20 min as it is used to be said over the Internet.
___ 4 ____________________________________________________________________
cd ..
cd Redist
sudo python ReleaseVersion.py arm
!!!!!!!!!!!!!!!!!!
and there things goes wrong here is the coplete prompt of the terminal:
sudo python ReleaseVersion.py arm
Path: ..
Output: /home/pi/OpenNI2-gumstix-fixes/Redist/OpenNI-2.1.0-arm
Platform: arm
Compile: Build
Docs: True
Tools: False
make -j1 CFG=Release PLATFORM=Arm > /home/pi/OpenNI2-gumstix-fixes/Redist/build.Release.Arm.txt 2>&1
RC: 512
Compilation failure
!!!!!!!!!!!!!!!!
Please help me! What can I do?

Since you cloned from https://github.com/kalectro/OpenNI2.git which has something like "gumstix-fixes", either direct the issue to that guy or use my version.
My version is known to compile on ubuntu and debian on Raspi.
Regards
Hauke

Many thanks for your answer, I did it but there is no the Redist Folder and I didn't manage to go further.
I finally found the solution by modifying the commondef file like this;
ifndef COMMON_DEFS_MAKE
COMMON_DEFS_MAKE=1
some defaults
ifndef CFG
CFG = Release
endif
find out the platform on which we're running
MACHINE = $(shell uname -m)
ifneq (,$(findstring x86_64,$(MACHINE)))
HOST_PLATFORM = x64
else ifneq (,$(findstring x86,$(MACHINE)))
HOST_PLATFORM = x86
else ifneq (,$(findstring i686,$(MACHINE)))
HOST_PLATFORM = x86
else ifneq (,$(findstring i386,$(MACHINE)))
HOST_PLATFORM = x86
else ifneq (,$(findstring armv6l,$(MACHINE)))
HOST_PLATFORM = Armv6l
else ifneq (,$(findstring arm,$(MACHINE)))
HOST_PLATFORM = Arm
else
DUMMY:=$(error Can't determine host platform)
endif
now check if this is a cross-compilation or not
#ifeq "$(PLATFORM)" ""
PLATFORM = $(HOST_PLATFORM)
#else
ifneq "$(PLATFORM)" "$(HOST_PLATFORM)"
# cross compiling. Take CXX and STAGING_DIR from environment
PLATFORM_UPPER = $(shell echo $(PLATFORM) | tr 'a-z' 'A-Z')
DUMMY:=$(eval CXX = $($(PLATFORM_UPPER)_CXX))
DUMMY:=$(eval TARGET_SYS_ROOT = $($(PLATFORM_UPPER)_STAGING))
ifeq "$(and $(CXX), $(TARGET_SYS_ROOT))" ""
DUMMY:=$(error Cross-Compilation error. Can't find $(PLATFORM_UPPER)_CXX and $(PLATFORM_UPPER)_STAGING)
endif
endif
#endif
PLATFORM = $(HOST_PLATFORM)
expand file list
SRC_FILES_LIST = $(wildcard $(SRC_FILES))
define the intermediate directory
INT_DIR = $(BIN_DIR)/Intermediate/$(PLATFORM)-$(CFG)/$(OUTPUT_NAME)
define output directory
OUT_DIR = $(BIN_DIR)/$(PLATFORM)-$(CFG)
full path to output file
OUTPUT_FILE = $(OUT_DIR)/$(OUTPUT_NAME)
take this file's dir
COMMON_MAK_DIR = $(dir $(lastword $(MAKEFILE_LIST)))
get the OS type
OSTYPE := $(shell uname -s)
platform specific args
include $(COMMON_MAK_DIR)Platform.$(PLATFORM)
endif # COMMON_DEFS_MAKE
and it compile.

Ok to close the issue?

Yes of course!


Added author name to license and package.json

I wanted to know what this was licensed under and saw the copyright was blank. Added you to the license file as well as package.json.

Cool, thanks!


README is outdated

The "motivation" for this library shows outdated code with the object3 and := functions. This is confusing for those who are learning the current version of the core library and trying to understand  how elm-decode-pipeline is different

Fixed on master,  thanks!


[BUG] GET failed with status 429: {"message":"grpc: received message larger than max (70716954 vs. 4194304)

Using ethdo but it calls the go-eth2-client ...
When trying to generate an offline file, I get a 429 error with this command
./ethdo validator credentials set --prepare-offline --connection (eth2 beacon node:3500)
Connections to remote beacon nodes should be secure.  This warning can be silenced with --allow-insecure-connections
Error: failed to process: failed to obtain validators: failed to request validators: GET failed with status 429: {"message":"grpc: received message larger than max (70716973 vs. 4194304)","code":429}
Google seems to indicate that an option should be set:
I solved this problem by assigning the grpc.max_message_length when creating the gRPC stub
    # create the gRPC stub
options = [('grpc.max_message_length', 100 * 1024 * 1024)]
channel = grpc.insecure_channel(server_url, options = options)
stub = prediction_service_pb2_grpc.PredictionServiceStub(channel)

Thanks for the pointer @Eloring ! I needed this option to get it to work:
options = [('grpc.max_receive_message_length', max_message_length)]
I traced the code as best as I could and I can see where the HTTP request is sent but I can't see where options would be set...

It was unrelated to this project ...


83 ux review add sticky progress bar navigation to the side

This merge request adds a sticky header to the tool.
The header contains links to the Wiki and the contact page.

@antw Hai Anthony, would you be able to review this issue?

@antw Hai Anthony, thanks so much for reviewing. It's so nice that you also review on style and best practices, thanks for that. I've implemented your suggested changes, so it should be able to merge now.


Passing doskey alias file to commandline not working

Windows Terminal version
1.13.10733.0
Windows build number
10.0.19044.1645
Other Software
No response
Steps to reproduce
Trying to use an alias.cmd file as mentioned in this issue.
Profile in settings.json:
            {
                "altGrAliasing": true,
                "antialiasingMode": "grayscale",
                "closeOnExit": "graceful",
                "commandline": "cmd.exe /K \"C:\\Users\\Jason\\alias.cmd\"",
                "elevate": false,
                "guid": "{7a1c5dd6-779d-4b81-9599-8cbe559fc419}",
                "hidden": false,
                "historySize": 9001,
                "icon": "ms-appx:///ProfileIcons/{0caa0dad-35be-5f56-a8ff-afceeeaa6101}.png",
                "name": "Command Prompt",
                "snapOnInput": true,
                "startingDirectory": "%USERPROFILE%"
            }

alias.cmd:
@echo off
doskey s=ssh $*

Expected Behavior
No response
Actual Behavior
Commands are not available when I open Terminal, but they become available after I manually run alias.cmd from the Terminal window.

It's only a workaround, but I have my DOSKEY macros defined in CMD's "autorun" file, specified here:
regdir /v /d "HKEY_CURRENT_USER\SOFTWARE\Microsoft\Command Processor"
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Command Processor
  Autorun : REG_SZ : d:\uty\cmdstart.bat

It works.

I misspoke.  My "autorun" file looks like this.
v:\> type u:\cmdstart.bat
@echo off
doskey /macrofile=d:\uty\doskey.txt
chcp 1252 > NUL

FWIW, this works here, that is, the CMD file is executed.
"commandline": "%SystemRoot%\\System32\\cmd.exe /K \"v:\\foo.cmd\""

FWIW, this works here, that is, the CMD file is executed.
"commandline": "%SystemRoot%\\System32\\cmd.exe /K \"v:\\foo.cmd\""

doesn't work for me, unfortunately. I've tried adding the %SystemRoot%\\System32\\ portion and also using / instead of \\. No joy 🙁


Add sinsp_extractor_plugin::id

Return the result of plugin_get_id if that symbol is present, or 0 if
not.
Signed-off-by: Gerald Combs<EMAIL_ADDRESS>
What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area driver-kmod

/area driver-ebpf

/area libscap

/area libsinsp

/area tests

/area proposals

What this PR does / why we need it:
Makes extractor plugin IDs available to sinsp consumers.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

@geraldcombs: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Welcome @geraldcombs! It looks like this is your first PR to falcosecurity/libs 🎉

Hi @geraldcombs. Thanks for your PR.
I'm waiting for a falcosecurity member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: geraldcombs
To complete the pull request process, please assign gnosek after the PR has been reviewed.
You can assign the PR to them by writing /assign @gnosek in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

It looks like this isn't needed (by me, at least). Closing.


Reaction-level visualization upon reaction validation

Closes #269

Displays a visual summary of the reaction at the top of the editor using ord_schema.visualization.generate_text

Note that flag definitions in this file had to be moved so multiple imports didn't lead to conflicting absl flag definitions

Reaction-level validation is triggered after loading the form

Example at http://localhost:5000/dataset/ord-nielsen-example/reaction/0?user=test (I know this isn't a real link, but would make it faster for someone to test on their local deployment) using the new Nielsen example:

This is awesome!


Update debug to the latest version

:tada: This PR is included in version 1.1.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update tests on WW04.1

pls check why the pull request has so many files changed?

upload wrong file


Probe successThreshold value validation not concistent with Bicep

Please provide us with the following information:

This issue is a: (mark with an x)

[X] bug report -> please search issues before submitting
[ ] documentation issue or request
[ ] regression (a behavior that used to work and stopped in a new release)

Issue description
A clear and concise description of the observed issue.
see also https://github.com/microsoft/azure-container-apps/issues/361
This Bicep Probe config is validated in VS, a mouseover shows XX
successThreshold: int
Minimum consecutive successes for the probe to be considered successful after having failed. Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1. Maximum value is 10.

          probes: [
            {
              failureThreshold: 5
              httpGet: {
                path: '/manage/health/liveness' /* /actuator */
                port: 8081
                scheme: 'HTTP'
              }
              initialDelaySeconds: 30
              periodSeconds: 60
              successThreshold: 5
              timeoutSeconds: 30
              type: 'Liveness'
            }
            {
              failureThreshold: 5
              httpGet: {
                path: '/manage/health/readiness' /* /actuator */
                port: 8081
                scheme: 'HTTP'
              }
              initialDelaySeconds: 30
              periodSeconds: 60
              successThreshold: 5
              timeoutSeconds: 30
              type: 'Readiness'
            }
          ]

Steps to reproduce

Deploy an ACA with the above Probe setting  successThreshold: 5
Look at the logs

Expected behavior [What you expected to happen.]
The deployment should be successfull as the VS code the Linter shows 'Maximum value is 10.'
Actual behavior [What actually happened.]
"ContainerAppProbeSuccessThresholdStartupOrLivenessInvalid\",\r\n            \"message\": \"Container 'aca-petcliaca-visits-service' 'Type' probe's SuccessThreshold must be 1.\"\r\n          ***,\r\n          ***\r\n            \"code\": \"ContainerAppProbeSuccessThresholdStartupOrLivenessInvalid\",\r\n            \"message\": \"Container 'aca-petcliaca-api-gateway' 'Type' probe's SuccessThreshold must be 1.\"\r\n          ***\r\n        ]\r\n      ***\r\n    ]\r\n  ***\r\n***"***]***

Screenshots
N/A
Additional context
Bicep from GH Workflow

@ezYakaEagle442 - I think the VS code validation for bicep uses the property definition from the azure-rest-api-spec repo. I don't think it has the logic to validate the min/max values based on the type of the probe. The property description and the error message are consistent though.


Error in chat_postMessage method

I tried the following code:
block = [{"type": "section","text": {"type": "mrkdwn","text": "Erro na consulta " + str(datetime.now())}}]
client_bot.chat_postMessage(channel=channel_id, blocks = block)

And i got the answer:
Failed to run listener function (error: The request to the Slack API failed. (url: https://www.slack.com/api/chat.postMessage)
The server responded with: {'ok': False, 'error': 'invalid_blocks', 'errors': ['invalid_url [json-pointer:/blocks/0/slack_file.url]'], 'response_metadata': {'messages': ['[ERROR] invalid_url [json-pointer:/blocks/0/slack_file.url]']}})

This same code ran successfully about four hours earlier, but now it has this error.
Can anyone help me?

Hey @soilmo , we are investigating this. We are seeing elevated rates of this error; our engineering teams are looking into the issue. Once I have more info I'll post here again.

Thanks! I'll be waiting for good news.

@soilmo I can't reproduce the error you are seeing with the payload you provided in your original post. Are you still seeing this?

@filmaj i tried again and got the same error.
Let me explain better about my situation:
I created a slack bot using Slack Bolt. It works well, but today after lunch, some functions doesn't work. All functions the send images happened this problem.
See print below to understand better:

Sure!
The block is below:

say(

            blocks = [

                {
                    "type": "section",
                    "text": {
                        "type": "plain_text",
                        "text": 'Última atualização: '+str(infos[1])+' '+str(infos[2]) + ' | ITD do IPCA é o mesmo do FOCUS FIC FIA (2020-12-28)'
                    },
                    "accessory": {
                        "type": "image",
                        "slack_file": {
                            "url": infos[0]
                        },
                        "alt_text": "Rentabilidades"
                    }
                }
            ]
        )

Where:
infos[0] = "https://files.slack.com/files-pri/T01J6BY2VEU-F06ERESRXUZ/rentabilidades.png?pub_secret=aa3396340f"

Whoa, you're already using "slack_file": { "url": infos[0] }? We just released that as a brand new feature, like, 4 hours ago?

We believe the issue may be the pub_secret querystring param. Try dropping that?
Also: where are you getting that URL from?

Nice! Exactly! My problem was started about 4 hours ago.
My URL is been created like this:

        client = WebClient(token=SLACK_USER_OAUTH_TOKEN)

        result = client.files_upload(channel=channel_id,file=path, initial_comment = 'Carteira')
        result_url = client.files_sharedPublicURL(file = result['file']['id'])

        website = result_url['file']['permalink_public'].split("https://slack-files.com/")[1]
        team_id = website.split('-')[0]
        file_id = website.split('-')[1]
        pub_secret = website.split('-')[2]
        filename = result_url['file']['name']
        direct_link = "https://files.slack.com/files-pri/" + team_id + "-" + file_id + "/" + filename + "?pub_secret=" + pub_secret

Your suggest is do the following?

        client = WebClient(token=SLACK_USER_OAUTH_TOKEN)

        result = client.files_upload(channel=channel_id,file=path, initial_comment = 'Carteira')
        result_url = client.files_sharedPublicURL(file = result['file']['id'])

        website = result_url['file']['permalink_public'].split("https://slack-files.com/")[1]
        team_id = website.split('-')[0]
        file_id = website.split('-')[1]
        filename = result_url['file']['name']
        direct_link = "https://files.slack.com/files-pri/" + team_id + "-" + file_id + "/" + filename

Sure! I appreciate contribute into this task!
But i dont fix error yet. Now, i tried like this:
client = WebClient(token=SLACK_USER_OAUTH_TOKEN)

result = client.files_upload(channel=channel_id,file=path, initial_comment = 'Rentabilidades')
result_url = client.files_sharedPublicURL(file = result['file']['id'])

website = result_url['file']['permalink']
print(website)

And the block used was:

say(

            blocks = [

                {
                    "type": "section",
                    "text": {
                        "type": "plain_text",
                        "text": 'Última atualização: '+str(infos[1])+' '+str(infos[2]) + ' | ITD do IPCA é o mesmo do FOCUS FIC FIA (2020-12-28)\n'
                    },
                    "accessory": {
                        "type": "image",
                        "slack_file": {
                            "url": infos[0]
                        },
                        "alt_text": "Rentabilidades"
                    }
                }

            ]
        )

I got the same error:

OK, different error.
What is the value of infos[0] in your example?

What kind of token is being used? A bot token or a user token? Does your app implement OAuth flow to retrieve user tokens to make actions on behalf of a user?

I use a bot token to create WebClient object and Bot User OAuth Token when i upload image on slack cloud.
Maybe use these differents codes in the same bot can make this error.

That's a bit of a confusing answer  😅 What I need to know is, do you use an xoxb-... or an xoxp-... token for each of the different Slack API calls? (files.upload, files.sharedPublicURL, chat.postMessage)

Oh, sorry. But yes. Let me show you:
SLACK_BOT_TOKEN: xoxb-...
SLACK_USER_OAUTH_TOKEN: xoxp-...

OK great, that's what I needed to know. And for the chat.postMessage API, which token is used?

@filmaj i solved!! :)
I just use the same token at the following parts:
Starting bot at the beggining of code:

Upload file (image) in slack cloud.

And for send file, i used the method below:

Glad you got it fixed!
FYI, we actually will be rolling back the new slack_file property / feature of image blocks today due to various issues it caused for customers (including the problem you experienced earlier). So please continue using the image_url property as I see you are doing in your last screenshot for the time being.
I will close this issue now but if you have further issues here, feel free to re-open or file a new issue.

Hi!
The same error is happening again.


Update teams-connected-sites.md

Updated the channel site text to remove the incorrect wording that listed standard channels as getting a site.  Standard channels do not get channel sites.  They get a Teams connected parent team site and not a channel site. Please approve these changes.

@Holland-ODSP @AtkinE can either of you help get this updated.  This is a fairly significant incorrect piece of information.

Closing this pull request. Didn't know how to approve the request and the sign off label was not showing under the label tags. Will make the changes and resubmit.


useContractRead throws InvalidAddressError

I see that useBalance accept null address as arg and does not throw any error. However useContractRead does not follow same pattern. This way when user is not connected the address is null and try to call the hook useContractRead using an null address will throw the error. Then trying to add a conditional to the this hook also throws another error:
Uncaught (in promise) Error: `useConfig` must be used within `UseWagmiPlugin`.

How could solve this?
Example 1: Throws InvalidAddressError: Address "null" is invalid.
const { address } = useAccount();

const { data } = useContractRead({
    address,
    abi,
    functionName,
    args: [address.value],
    watch: true,
  });
}

Example 2: Throws Uncaught (in promise) Error: useConfig must be used within UseWagmiPlugin
const { address } = useAccount();

if(address.value){
  useContractRead({
      address,
      abi,
      functionName,
      args: [address.value],
      watch: true,
      onSuccess: (data) => {
        myRef.value = data;
      },
    });
}

@ernaneluis

Because address is a ref whose initial value is null .value will lose the response
I guess because it is not used in setup If you use UseWagmiPlugin

@ernaneluis no way. use @wagmi/core (There will probably be conflicts between packages within use-wagmi and @wagmi/core ) or https://viem.sh/docs/contract/readContract.html#readcontract

@ernaneluis use-wagmi needs to get the client through the UseWagmiPlugin plugin, Also I wonder why you don't want to use UseWagmiPlugin

@ernaneluis Unfortunately I don't understand what you're trying to do Can you provide an example Hope that gives you some advice


chore: ran formatter

Hey. I'm not sure which directory you ran this from but this doesn't look like it honored any of the formatter files. It's generally run per app and not from the top level

@bryannaegele was at the top indeed, I can fix the formatter per project which it requires adding .formatter.exs file

The changes will make sure that if you run mix format form the root, it will respect the nested projects


[T4A2] [T01-T3] Ang Lang Yi

Ready for review.

@maltiso
Some comments added. Please close the PR after reading comments.


fixes #253

Description
Adds support specifying complete URL for tomcat tarbal to install
Issues Resolved
#253
Check List

[ ] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD.
[ ] New functionality includes testing.
[x] New functionality has been documented in the README if applicable
[x] The CLA has been signed. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

Enable support for specifying complete tarball URL for tomcat

Looks like a transient issue with connectivity to apache site. Closing and reopening to run the checks again

I am consistently getting network error only on centos-5 box. Not sure why it is not able to download from that URL
SocketError
      -----------
      Error connecting to http://archive.apache.org/dist/tomcat/tomcat-7/v7.0.42/bin/apache-tomcat-7.0.42.tar.gz - getaddrinfo: Temporary failure in name resolution

      Cookbook Trace:
      ---------------
      /opt/kitchen/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:41:in `run_action'
      /opt/kitchen/cache/cookbooks/compat_resource/files/lib/chef_compat/copied_from_chef/chef/provider.rb:125:in `compile_and_converge_action'
      /opt/kitchen/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:41:in `run_action'

@tas50 I have updated the README using 'specified' instead of 'mentioned'


timely api requests

I don't know what the stance is on use of api, but if you're modifying a page and calling api, it would be cool if you made the api request as soon as user navigates to a page to be modified.
Issues #977 would've benefited from this. Watch links to issues/pr, if they're clicked make an api call, to help modify page to avoid flicker.
I thought about doing myself but got too worried about user navigating straight to the page without redirects, ensuring a call then, since I'm not sure how the features are actually loaded (or basically ajax for that matter), nor that the loading behavior would actually let you do something like this.

I think you're asking to trigger an API call when the user clicks on a link that will require an API call, so it doesn't have to wait for the whole page to be loaded first.
Most of the time we rely on the info on the actual page to make the API call, but if we don't, then sure.
This is somewhat possible already I think, at least on ajaxed pages where the URL changes before pjax:end so we just have to add a new features.onNavigation = cb => addEventListener('pjax:start', cb) and the page detections will automatically work.
You can have two features.add, on onNavigation and the other onAjaxedPage, for example like I did in
https://github.com/sindresorhus/refined-github/blob/bd98bb5a9812a9f0fc63c3992127a2d72f1f1180/source/features/pr-merge-info-enhancements.tsx#L75-L91

Closing this since you’re already working on it 🙂

for example, this should be implemented in #977


Have ArrayObservable.create return an Empty or ScalarObservable if possible.

This could then be used in from and fromArray so the resulting Observable performed better in various operations.

... alternatively, we could have ArrayObservable use the _isScalar and value properties as used in #279 once that lands.


README add ENV variable setup

This is a great addition. Although I think these steps should be in the terraform repo

My initial thought was to put it into Terraform's README as well.

My initial thought was to put it into Terraform's README as well -slack discussion was here.
@benbaumann95 Argument was:
I think it’s more intuitive to see that detailed out on the main repo rather than terraform as that’s probably not where i would have looked initially trying to do this.
Obviously, I'm happy with either option.

I think it would be fine to have it in both, but definitely good to have here as I'm not sure everyone will know to look at the terraform repo when they're still getting used to the set up!

What we need is another section to introduce the terraform project it's not the job of the ENV variable section to introduce terraform project. 1 step at time..... First ENV.

What we need is another section to introduce the terraform project it's not the job of the ENV variable section to introduce terraform project. 1 step at time..... First get ENV section in.

Agreed and agreed!


Redux Dev Tools

Will this work with redux dev tools and redux-react-router?

sure it is working, I'm already using in a couple of projects

My bad, does it work out of the box or is it passed in the options param when configuring the store?

redux-react-firebase it is only for connecting firebase if you need redux dev tools or react-redux-router you need to add them to your store as you normally do


DROOLS-733 - Fixed nondeterminism in jbpm executor tests.

I didn't find a way how to get rid of Thread.sleep(), but at least I got rid of nondeterminism caused by timing of job executor.

Added job executor test for getRequestsByCommand(), minor client fix.

merged into execution server unification branch, thanks @sutaakar


Poly fill help: Unable to get value of the property 'add': object is null or undefined on IE9.

I need help with IE9 poly fill, where to find and how to use it to avoid the above error.
I installed using npm, algoliasearch: ^3.22.1

You can use any polyfill for classList to avoid this error.
Thanks for using algolia!


not capturing console logs if we use any swift POD in the project

How to reproduce the problem ?
The problem is with the POD WBWebViewConsole
Run the attached project in any iOS 8+ devices that has internet connection as it loads a html doc from google drive.
in the html doc … click General/Info/Warning/Debug/Error Log

you will some text appearing on the html page whenever u click any of the above buttons….
To me the library is about capturing the logs that’s generated in html page and thats my use case
whenever u click the button apart from showing some text in html page I am writing some log in background.

now click on the button get logs … and see the logs in Xcode IDE… you will see the all the console logs that’s generated in html

Get logs-> is a native button super imposed on webview..the library lets us read the console logs from wkwebview
..
Now in the POD
u uncomment the following lines
use_frameworks!
pod 'PLCrashReporter'
pod 'XWebView', '~> 0.9.5’

and do pod install
then paste the following code on top of ViewController
import WBWebViewConsole

now u run the project on device and click some buttons in html page and click get logs you can't see comments that's generated in the html page
So what Exactly is the problem:
The below two delegates would get called  in WBWKWebView if any log is wrriten by JS but its not happening
- (void)webView:(WKWebView *)webView decidePolicyForNavigationAction:(WKNavigationAction *)navigationAction decisionHandler:(void (^)(WKNavigationActionPolicy))decisionHandler
- (void)wb_evaluateJavaScript:(NSString *)javaScriptString completionHandler:(void (^)(NSString *, NSError *))completionHandler

But the same delegate which is below gets fired while loading a url
- (void)webView:(WKWebView *)webView decidePolicyForNavigationAction:(WKNavigationAction *)navigationAction decisionHandler:(void (^)(WKNavigationActionPolicy))decisionHandler
Herewith is the project that faces this problem
But while creating the instance of WBWKWebView and loading a URL all the necessary delegates of this class are getting fired.
The above delegates are supposed to fire when a log is written while clicking the button in html page
Note:
If we use swift pod then we have to add it as frameworks only ...we can't just add a single pod as framework every pod will be added as framework only.

I have raised a question in stack overflow as well !

The problem is with the search paths under build settings, which are overriding the other libs paths . Just install one by one the pod .. And it works fine .

Buddy its not working .. I have a doubt that this library won't work if its compiled as Dynamic Framework... But there is no other way ...bcuz if we use any swift lib in pod all the libs in the POD will become Dynamic framework.... I am still looking for solution ...

Thank you for the investigate, Duraiamuthan
When JSBridge init, it will add some "UserScripts" to webview, which source is loaded from [NSBundle mainBundle] in previous version. But if it's in a framework, the resource files is in the framework bundle instead of mainBundle.
This is actually been fixed in the master branch year ago (uses [NSBundle bundleForClass:]), but NOT in the release version.
So I just released version 1.0.2, you can:

pod update
restart Xcode and clean your project
build and run again

Reopen this issue if you still encounter any problem.

Hi ... Thanks for the fix ! I really appreciate your efforts on making the library tremendously awesome ! You are the Rock Star  ! 💯


Errors on kscript invocation

Very first try of kscript with:
kscript -t 'lines.split().select(10,1,12).print()' some_flights.tsv
results in:
Exception in thread "main" java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at Main_Scriptlet_cf6c40ff899dcf3d$Companion.main(Main_Scriptlet_cf6c40ff899dcf3d.kt:6)
at Main_Scriptlet_cf6c40ff899dcf3d.main(Main_Scriptlet_cf6c40ff899dcf3d.kt)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jetbrains.kotlin.runner.AbstractRunner.run(runners.kt:61)
at org.jetbrains.kotlin.runner.Main.run(Main.kt:109)
at org.jetbrains.kotlin.runner.Main.main(Main.kt:119)
Caused by: java.lang.IndexOutOfBoundsException: Index: 9, Size: 3
at java.util.ArrayList.rangeCheck(ArrayList.java:657)
at java.util.ArrayList.get(ArrayList.java:433)
at kscript.text.Row.get(Tables.kt:32)
at kscript.text.PosSelect$process$1.invoke(Tables.kt:103)
at kscript.text.PosSelect$process$1.invoke(Tables.kt:99)
at kotlin.sequences.TransformingSequence$iterator$1.next(Sequences.kt:148)
at kotlin.sequences.TransformingSequence$iterator$1.next(Sequences.kt:148)
at kscript.text.StreamUtilKt.print(StreamUtil.kt:76)
at kscript.text.TablesKt.print(Tables.kt:73)
at kscript.text.TablesKt.print$default(Tables.kt:73)
at Scriptlet_cf6c40ff899dcf3d.(Unknown Source)
... 13 more

Caused by: java.lang.IndexOutOfBoundsException: Index: 9, Size: 3

It happened because the tsv file doesn't have enough columns.

Indeed. But doesn't this make it a problem of your input data/processing logic? To me, it does not seem to be a problem with kscript itself. What do you think?

@holgerbrandl
I don't think this issue is a problem of kscript, either. (I'm not the issuer of this issue. I looked at this issue and experimented a little bit as it is labeled as "help wanted".)

Oh that's "how help" wanted is supposed to be used. I typically assigned it to tickets which seem more to be user support than an actual issue. I'll use a different tag.

Closed due to inactivity. Feel welcome to reopen if needed!


Implement two versions of convert_keras_dot

Manually rerun Linux-conda-ci and it passed, so merge it.


lists compilers up to 0.5.10 2. Moves the latest property to the top of the file for easier editing

This seemed to break compilation, also the changes don't match the description of the PR?

Sorry, I pushed the wrong commit. 🤦♂
#74 is correct.


FeedIterator Diagnostics - supply RangeId along with each batch of changes

Is your feature request related to a problem? Please describe.
Regardless of the configuration being applied, being able to see which ranges are being serviced (in terms of physical rangeids) is critical for troubleshooting feed performance.
While simply logging the value (received 100 items from Range 4) is one use it might be applied to, in some cases, it can be useful for internal routing prioritization too - i.e. "ok we'll stuff something into the log deep down" does not address the need in full.
Describe the solution you'd like
The callback that delivers a set of feed items should in some way convey the range id, as the V2 one did.
Describe alternatives you've considered
I'm not aware of any way to determine where a batch of items came from
Additional context
This is to some degree a restatement of items covered in #616, prompted by #1117. While I like the new APIs, not having this is a deal breaker for moving applications onto any SDK newer than V2, which is a major concern for me.

Is the information exposed as Diagnostics not enough to do that analysis?

https://docs.microsoft.com/en-us/azure/cosmos-db/monitor-cosmos-db#azure-cosmos-db-log-analytics-queries-in-azure-monitor
https://docs.microsoft.com/en-us/azure/cosmos-db/monitor-cosmos-db-reference

It seems like the doc does not mention it, but there used to be a "partitionId" field in the Diagnostics Logs.

While it may be possible to infer it from that (obviously rich) source, the point is that I want to be able to correlate from my logs, that I have 2 instances of my CFP, and the rate of progress per range across those instances. Knowing that there are two things out there querying is a good start, but does not let me troubleshoot a specific CFP node's behavior in terms of the actual changes being observed (or not, as can frequently be the case e.g. if you get a hot partition)

Also, for avoidance of doubt, I/we have stacks of code that emits this context into logs. The fact that this context is being withheld in the >=3 SDK is a significant blocker to adoption of newer SDKs for multiple teams. I can get that one might wish to de-emphasize such ways of troubleshooting, but I fail to see what closing the bottle accomplishes here - perhaps you can explain a little about why you feel its harmful to expose this?

The problem is that the concept of the Partition is tied to the current implementation, it's not a piece of information that comes from the service response. Assuming monitoring information from an implementation detail breaks if the implementation changes.
The current implementation is locking 1 lease to 1 Partition (the LeaseToken is the number of PKRange/Partition), so if you see LeaseToken 0 and 1 assigned to one instance, you assume those 2 Partitions are going to be processed by that instance, and you would be right, now. But the end goal is for the leases to not be locked to a Partition, that a Partition can have multiple Leases and thus increase the scaling support and also enable new scaling scenarios, like being able to have multiple CFP Hosts on single Partition containers.
Let's say now that each Partition can be split across 10 Leases (each lease represents now a range of Partition Key Values), if you have 6 Partitions, you have 60 leases. Each lease will have a LeaseToken that represents the range of PK values, not the Partition, because the Partition is not needed anymore. Since the Partition is not something that comes as a response header, even if the SDK exposed the Lease instance, or LeaseToken, that wouldn't let you understand which Partition the request hit.
In that scenario, obtaining the information from the Diagnostics is more valuable to identify Partition consumption, as the leases won't reflect a particular Partition anymore, you won't be able to determine the Partition from the lease, even if it's exposed to the delegates. So Diagnostics is the one implementation-agnostic source of information. In the Diagnostics you can use the UserAgent (which in the V3 SDK is mapped to the ApplicationName in the CosmosClientOptions) if you want to dissect and understand which instance is querying which Partitions.

Aside from the fact that this sounds much scarier to troubleshoot than the existing mechanism, my main concern here is that any such scheme with multiple readers per partition will exacerbate write amplification effects (leading to more troubleshooting needs...). Or are you saying there's be some mechanism whereby there's a relatively low cost server-side filtering applied and I'm not managing a system where multiple readers are triggering network and server traffic?
For avoidance of doubt, I'm not looking for lease or lease token information to be exposed via the API.

Currently the only way to consume the Change Feed is by the PKRange / Partition (hence the 1 lease 1 Partition approach) but this limits the degree of parallelism to a factor that users cannot control directly, which has been asked many times.
We are working on server-side support to enable a higher granularity filter, which would enable this higher granularity in the leases, and basically be able to read changes from ranges of PK values, regardless of Partition distribution.
The problem in any case is that the Partition/PKRangeId, the piece of information you want to log (at least from what I understood is the ask and the need to troubleshoot hot partitions), is not something that is currently exposed in the REST response, so even if the SDK wanted to expose all the information (pass that down), it just wouldn't be there.
What I don't understand from your comment is your mention of write amplifications. As the CFP is a read-only mechanism, could you elaborate on what do you mean by that and how a higher degree of read parallelism would affect writes?

What I don't understand from your comment is your mention of write amplifications. As the CFP is a read-only mechanism, could you elaborate on what do you mean by that and how a higher degree of read parallelism would affect writes?

If one has 5 Reactors tracking changes using your proposed enhancements, then every write starts triggering 5 reads. This is particularly relevant where one is triggering significant numbers of updates, which normally get 'squashed' per call from a single consumer.
Such a pattern is a common thing to do with Kafka, but of course its design incorporates strong support for scaling out reads.
In the general case, for workloads I'm familiar with, a common pattern is actually to feed from a CFP onto Kafka and let the N readers hang off that; given the write capacity of a Kafka cluster (and the fact you won't encounter rate limiting), it's pretty trivial to manage such a replication chain -- especially if you have good diagnostics as to how far things are behind (and you can drill into partitions that are not yielding reads to the CFP reader) ;) There's also lots of commercial and open-source tooling for such diagnostics.
While I understand the desire people have for such features (pejoratively: pretending Cosmos can and should be able to do all the things Kafka can do), it's critical for me that it doesn't come at the cost of making basic workflows (replicating CFP to a straightforward feed without filtering or major enrichment) harder to troubleshoot than they need to be. Just because someone asked for scissors, doesnt justify blindfolding people with far simpler schemes.

The problem in any case is that the Partition/PKRangeId, the piece of information you want to log (at least from what I understood is the ask and the need to troubleshoot hot partitions), is not something that is currently exposed in the REST response, so even if the SDK wanted to expose all the information (pass that down), it just wouldn't be there.

The piece of information I want to log is the RangeId - the value that's supplied to the lease assignment notification. I guess if that notification is also not being implemented in newer SDKs, the value goes down.
All that remains for me to do is to restate: with the V2 CFP lib, it was possible to cheaply implement a logging scheme which allows me to store sufficient info to allow me to determine why a pile of notifications were delayed between 1:30am and 2:00am 2 weeks ago - I can see the Range Assignments and Read batches (with Range tagging) and can determine if any Ranges did not receive responses (and I can correlate that with the Change Feed Estimation results logged separately). While you're supplying me lots of powerful new abstractions, I'm keen to understand how you propose that I implement something that achieves that same traceability on the V3 stack before we start using them - a new abstraction is worthless without a troubleshooting story when I'm the one with the pager.

The piece of information I want to log is the RangeId - the value that's supplied to the lease assignment notification. I guess if that notification is also not being implemented in newer SDKs, the value goes down.

This is not fully correct. The RangeId is supplied on V2 CFP because the Lease contains a LeaseToken that matches the RangeId, because the lease is basically, 1 per RangeId, so to separate one Lease from the other, we have the RangeId, but only because the degree of parallelism is the RangeId/Partition, again, this is an implementation detail.
If a new implementation, with a different degree of parallelism comes into the picture, then the value that will be logged is that, not the RangeId. For example, let's just say for the sake of argument that we have a container that has 2 Partitions, 0, and 1, and you have 2 CFP instances. Currently, you see logs that say:
[CFP 0] assigned range 0
[CFP 1] assigned range 1
And 0 and 1 are really, Partitions, so in V2, you use this value to diagnose requests across partitions.
But in a higher parallelism scenario, with still 2 Partitions, we could go further and say that each Partition is now subdivided into PK value ranges. So Partition 0 is now PKValueRanges A, B, and C, and Partition 1 is now PKValueRanges D, E, and F. In that scenario, you will see logs like:
[CFP 0] assigned range A
[CFP 1] assigned range B
[CFP 0] assigned range C
[CFP 1] assigned range D
[CFP 0] assigned range E
[CFP 1] assigned range F
Now, the Lease identifier is no longer the Partition/RangeId, so even if it's exposed, you will see A, or C, not RangeId 0 or 1, so if the goal is to track RU usage/Hot partitions, the Lease information won't be useful, and that's when you need to go to Diagnostics. If the ask is explicitly that you want the RangeId, then it is not possible with a lease mechanism that goes further than the RangeId.
Now, if the goal is to track per Lease flows / changes, then this can be exposed, because you'd be getting the LeaseToken (whatever that represents, it doesn't matter) and it will be in sync with the "assigned range" logs.

Thanks for echoing back - I agree there can be confusion in the more complex cases (you explained it well from the off)

Now, if the goal is to track per Lease flows / changes, then this can be exposed, because you'd be getting the LeaseToken (whatever that represents, it doesn't matter) and it will be in sync with the "assigned range" logs.

Yes, this is the goal - being able to track assignments and splits. Also, given me and m any others will be going 1:1 parallelism, having a good story for that basic logging (this batch came from 0 is the ask.

Awesome! Glad to be on the same page 😄
Would it be ok to change the title to something like "Supply LeaseToken..." otherwise RangeId would lead to the ask being wrongly interpreted as needing the partition information (that was my initial interpretation).

I'll see if this can either go on V3 or vNext due to the breaking change nature on the contract

Thanks - from a selfish point of view, V3 isnt any more useful than V4 in terms of whether it'll fit in our environments
I should point out that https://github.com/Azure/azure-cosmos-dotnet-v3/issues/616 is pretty key to adoption for me too as there's lots of code I can't move forward without the equivalent of that facility. Happy to to/fro over there, or do a rebooted version of that issue which separates out the concerns about diagnostics and/or need for access to the LeaseToken which that discusses which duplicates quite a lot of the above.

I'll try to address this, and the other issue, through the reinstatement of the Context (which provides LeaseToken + Raw Response for headers + Checkpoint). As I said, this might get moved to vNextdue to the contract change, and since vNext is already a breaking change in many aspects (see #1119 ), it would be the right place to do it.

That's wonderful to hear - I should be able to make the time to progress the integration as things drop as getting this onto the new stack is something I'm very concerned about. I'm also very hopeful of perf benefits of 1119 (and am ready for https://github.com/jet/propulsion to move to STJ as part of this). I can't envisage there being an issue with taking a vNext dep.

related: https://github.com/Azure/azure-cosmos-dotnet-v3/issues/400


Replace SanchoNet in copy with Voltaire

Intro
The time has come.
We have had fun, but it is time for GovTool to graduate past SanchoNet
What?

Update copy throughout to remove and replace every publicly facing reference "SanchoNet" reference with "Voltaire".
It may also make sense to change wording within code.

(first of a few issues on this)

Do we have new icons prepared for this @m-i-k-e ?

I made the draft with the changes, and I am waiting for the necessary icons to complete the replacing

@m-i-k-e can you help with the icons?

@Ryun1 I've had a talk with Lorenzo, and we are reverting to "Voltaire" in place of Sancho. I've asked @kgrzonka  to sort out all the rebranding stuff (there isn't a lot) in Figma. She will probably get to it tomorrow. There is an issue for this #1640
I will take care of GitBook myself.

I've made the PR that replaces Sancho with Voltaire. You can have a look on the changes on dev

@MSzalowski I've sent you the correct logo, replace it, and I think we're done.


prefix redirect with external url path

We're trying to run Prometheus behind an Nginx Ingress in Kubernetes. We have -external-url set to https://www.example.com/prometheus and -route-prefix to / because we have the rewrite-target option set to /, basically what this does is it truncates the path prefix on actual requests, and makes requests look like they came from root. This causes the current redirect to redirect to https://www.example.com/graph, whereas it should be redirecting to https://www.example.com/prometheus/graph. Which is exactly what this PR implements.
There are many cases that could happen with -external-url and -route-prefix combinations that this should be reviewed carefully.
@fabxc @brian-brazil @juliusv @beorn7 @grobie @mxinden

Curious, would this be considered breaking?

I'd categorize this as a bug fix I think. I cannot really come up with a use case where the current behavior does what one wants. Also the UI is not part of our stability guarantees.

I would also say this is a bug fix as currently with the configuration of those settings you don't get the expected result, and I can't think of a case where that configuration currently does give you the right result.
As a heads up, I would like to introduce the same behavior in the Alertmanager once we have consensus of how to do it in Prometheus. Although I believe there is no redirecting happening in the Alertmanager, just need to know about backlinks (which now that I think about it are probably broken in the new UI /cc @mxinden) and the Alertmanager API should be accessible without the prefix from within the Kubernetes cluster.

👍


Webview as a worker

Dear all.
I want to make an app which works onPuse mode.
The app is a webview to run a website with injected javascript.
But onPuse will stop all app activity.
Can this "react-native-threads" help while the phone is locked?

react-native-threads is paused when the app is put into the background, it will not solve the problem of continuing to run while your app is closed or paused

So as a programmer what is your advice to do such?


Feature request: input spinner

Would it be possible to add an input spinner to lil-gui as per bootstrap-input-spinner https://shaack.com/projekte/bootstrap-input-spinner/ ?
For me, I believe most bases are covered in lil-gui and that this would be a great feature to have.
If you feel that this should be a custom controller, please could I request some information on creating custom controllers for lil-gui and when I have some free time I will try and create this controller.
Many Thanks!

Hi there, I'll consider it!
For now I would suggest adding your own button elements to controller.$widget that call controller.setValue.


Firefox/Safari Domain is not allowed

Rainloop 1.17.0, Safari 17.1/Firefox 120.0, macOS Ventura 13.6.1
When trying to log in getting "Domain is not allowed" error. This is an local installation. Works on Windows Firefox/Chrome/Edge as well as Chrome on macOS Ventura 13.6.1.
Try to log in as normally do on Windows workstation but on Mac.

step 1 Go to the url where the rainloop is installed
Step 2 Add ?admin to the end of the url
Step 3 Login, default username admin, and password 12345
Step 4 Add domain
Step 5 Logout
Step 6 Go the the rain-loop url again without the admin at the end
Step 7 Use the email id and password
Note, This is not a standalone system, but an email client. I assume you have Gsuite365, Microsoft cloud, or any other email server, and you have created email-accounts like<EMAIL_ADDRESS>Note : These websites will also give you the imap, smtp details.


Runtime configuration capabilities

As for now there is a fixed layout and effect chain to process the audio.
In the end we want to be able to work on configurations at runtime.
In order to do that, we need to look into frameworks so that we can

Describe the interface of an effect, e.g. inputs and outputs
Describe how an effect chain is built, e.g. which outputs should be mapped to the inputs of another effect or generator
Store and load effect chains

This should also support asynchronous process, see #2

Maybe have a look at the JUCE Framework how they're doing it? https://docs.juce.com/master/tutorial_audio_processor_graph.html

Many thanks to https://stackoverflow.com/questions/9931738/flask-throwing-working-outside-of-request-context-when-starting-sub-thread/9932189#9932189

Implemented


Admin page- Hardware library management- front-end

We need to have a special admin page for hardware library.
It must have a table with a list of all items and button at the top with a pop-up function to add a new item.
pages.pdf

Implemented in #76


Fix keptn dashboards

This PR:

Closes #23
Fixes the dashboard tiles on "Keptn Workloads" and "Keptn Overview" dashboards

@thisthat we should consider to apply these fixes to klt-examples as well.


[WIP] stablize test_node_merge_catch_up_logs_restart

What have you changed? (mandatory)
Fix https://github.com/tikv/tikv/issues/5202
What are the type of the changes? (mandatory)

Bug fix (change which fixes an issue)

How has this PR been tested? (mandatory)
unit-test
Does this PR affect documentation (docs) or release note? (mandatory)
No

/test

/test

/test

/test

/test


SyntaxError: Unexpected token import

i am trying to implement the react adaptive hooks on my project but i get the following error.

i am using Next.js
my test page code is as follows
import React from 'react';
import Layout from '../components/template/Layout';
import { useNetworkStatus } from 'react-adaptive-hooks/network';

function Test() {
  const { effectiveConnectionType } = useNetworkStatus();
  return (
    <Layout>

test

    </Layout>
  );
}

export default Test;

@eltonjothi @frontcraft
This is one demo project using react-adaptive-hooks package bootstrapped with create-next-app.
Could you please check this webpack configuration?
I think as ESM build is not working server side we need to transpile or use UMD build.
https://github.com/GoogleChromeLabs/adaptive-loading/tree/master/next-show-adaptive-loading
https://adaptive-loading.web.app/next-show-adaptive-loading/

Hey folks. As Anton noted earlier, there was a known issue here when using the hooks in a web framework that also involves server-rendering like Next.js. After speaking with the Next team, our guidance in https://github.com/GoogleChromeLabs/react-adaptive-hooks#server-side-rendering-support is accurate and recommended. We're hopeful we can avoid an extra step here in the future.


Fix key pages' mobile view of the website

Getting Start page mobile view design: prototype   and Figma file Didn't change any content, but changed font sizes and aligns.