add_menu_page/admin_menu conflicts with other plugins.

I was having issues where the menu page would not be linked inside of the admin navigation. In particular I found this issue was happening when ACF Pro was activated http://www.advancedcustomfields.com/ I tried to track down where the conflict was happening and found that if I prevented ACF from generating it's  menu page the auth0 menu page link appeared.
Considering that ACF is one of the most popular plugins for wordpress I thought it would reasonable that both plugins should work together.
When comparing the method that each plugin creates it's admin page, I found that both plugins were in fact using the correct action "admin-menu" to hook into, but ACF has set it's priority and accepted arguments whereas wp-auth0 used the defaults.
Here is ACF's action
add_action('admin_menu', array($this,'admin_menu'), 99, 0);

And now wp-auth0's
add_action( 'admin_menu', array(__CLASS__, 'init_menu') );

If I add a priority to wp-auth0 of 99+ the conflict resolves itself. Or if I remove the priority argument from ACF the conflict resolves itself. I am not positive what is best practice here, to use the defaults or set a custom priority. I will post a duplicate issue one the ACF plugin github, so that hopefully these types of conflicts can be avoided.

thx @mikemcguire, we'll take a look

I set up a priority with decimals hoping it wont get overridden by other plugin.
It should be ready in the next release.
Thanks @mikemcguire


[feature-request] Introduce a process runtime

Today, the OCI runtime can be used to create a container that closely resembles a process running natively on the host. However, there are some use cases where a process would also require full access to the host filesystem. Therefore, I'd like to propose the creation of a new runtime in containerd, capable of managing uncontained processes. Such a runtime would allow containerd to manage the lifecycle of components that need to co-exist with containerd on the same host, such as the kubelet or the kube-proxy.
Ideally, this should be applicable for both Windows and Linux.
cc @stevvooe

Why not bind-mount the host filesystem and chroot?

Why not bind-mount the host filesystem and chroot?

Can you do either of these things on windows?

@AkihiroSuda as @alexmavr stated this could be used to manage the lifecycle of components that do not fit in the container model such as processes on windows but still get the benefits of using a single management point.

This is being done in a separate project as it probably isn't a good fit for containerd mainline


Behavior with AppBarLayout

Trying to use this lib together with AppBarLayout, to scroll Toolbar up before scrolling view itself. For this, i wrapped table containing layout to NestedScrollView, but can't achieve proper work - looks like TableLayout does not support such behavior. Could you please take a look?

@formatBCE Did you solve it?

@tifezh yes, i managed to make it working by forking and digging into code.
You may see my fork https://github.com/formatBCE/AdaptiveTableLayout,
but be aware, that a lot was changed there to support dynamic data sets as well.

Could you tell me what part of code you changed to fix this issue?

@namtran4194 sorry for late response - had busy days.
Changes were made in AdaptiveTableLayout class:

@Override  public boolean onDown(MotionEvent e) {      // stop smooth scrolling      if (!mScrollerRunnable.isFinished()) {          mScrollerRunnable.forceFinished();      }      startNestedScroll(ViewCompat.SCROLL_AXIS_VERTICAL);      return true;  }
here "startNestedScroll" was added.

"scrollBy" method fixed - without that fix nested scroll was laggy as hell.

All rows regarding to NestedScrollingChildHelper were added - field and methods, look at the end of file.

I suppose, it's enough to get it working. If there's any troubles - inform me please, i will continue to dig.

Hi @formatBCE, thx for using this library.
I see you did a good job )) Feel free to create pull request. We will integrate this changes in our library.
With best regards Cleveroad team.

Hey @yarovoiag! Will make it asap, thanks! :)


Navbar Improved

What is the change?
Navbar icon was not properly alligned and the buttons were not responsive originally
Related issue?
close: #433
How was it tested?
I tested the code locally on my system.
Checklist:
Before you create this PR, confirm all the requirements listed below by checking the checkboxes [x]:

[x] Have you followed the Contribution Guidelines while contributing.
[x] Have you checked there aren't other open Pull Requests for the same update/change?
[x] Have you made corresponding changes to the documentation?
[x] Your submission doesn't break any existing feature.
[x] Have you tested the code before submission?

Screenshots or Video:

closing PR for now. reopen if required


columnFooter has undefined/Nan/Infinity/-Infinity values when data is grouped

See Plunkr:
http://plnkr.co/edit/6djeNT1fex39E9c4vwNE
It's an edit of the one found here:
http://ui-grid.info/docs/#/tutorial/105_footer
I simply added a group on the name column.

@PaulL1 grouping is your bailiwick, yes? :)

The problem is likely to be that grouping adds labels into the grouping subtotals, which means the aggregation cannot work any more.  More importantly, when you use footer aggregation with grouping it aggregates the group header rows as well as the core data, and therefore gets the wrong answer.  Footer aggregation and grouping are not compatible.

@swalters: do you have any objection if I modify aggregation (in the footers) to ignore any group header rows?  It'd still aggregate tree headers, as they are part of the data, but group headers are added by grouping, and therefore not part of the base data.

OK, looking at this again, it's actually working as designed, albeit that is not obvious to users.  When you have all the rows collapsed, there's no visible rows to aggregate, so it basically returns null/NaN etc.  Aggregation only totals visible rows, and grouping makes most of the rows invisible.  If you expand one of the groups it starts working, although the values that it gives aren't overly useful.
I'll write something into the tutorials that makes it clear that column footers and grouping don't go well together.


Add clarity to poorly written else-if-statements-ii assignment. A stu…

…dent of mine, Bob Senoff, pointed out that the wording is misleading

LGTM 👍


Objects to encapsulate whitelist

This is an experiment with adding real objects to represent the whitelist instead of a deeply nested hash. See sanitize-whitelist for the implementation.
Advantages

#dup with a block can be called on existing whitelists to create a new whitelist with modifications
the whitelist is frozen after it is initialized or dup'd.
#to_h converts it to the hash that the sanitize gem expects

Example
class MySanitizationFilter < HTML::Pipeline::SanitizationFilter
  CUSTOM_WHITELIST = WHITELIST.dup do
    remove "object"
    allow "time"
    element(:all).allow("id")
    element("span").allow("class")
  end

  def whitelist
    CUSTOM_WHITELIST
  end
end

/cc @jch @mastahyeti @ptoomey3 @mislav @josh

I'm not going to push this forward at the moment, so I'm going to close it out.


Update README.adoc

@objectiser could you please review.
(jira batch is not rendering)

Now the badge renders correctly (at least on my host). I still would like to update this for the cases when the badge is not rendered.

@pavolloffay Thanks!


(Enhancement) #773 Scroll bar in tabs that are not necessary

Closes #773

@alongoni please, resolve the conflict so it's deployed properly and we can review from the PR-deploy.

Travis automatic deployment:
https://pr791--safereact.review.gnosisdev.com/app


Design Issue - Cluster Overview

The white spacing above the headers and below the percentag bars seem wonky, but I'm assuming the white space above and below the dividing bars are the same. The header text is aligned to the top of the box, but the bottom is not lined up.
Can we consider either making the content aligned in the middle of the dividing lines so that the white space is more equal from top/bottom?
I added some lines to try and explain what I wrote above.

[ ] Progress bars should be left justified so they line up.

THe original issue about the spacing is still not fixed in cluster overview.

Closed in favor of sizzle: https://github.com/rancher/dashboard/issues/819


karma coverage for domain/

CodeEvalResultObjectFactory, CorrectnessTestObjectFactory, FeedbackObjectFactory, SnapshotObjectFactory
see issue #222

currently karma coverage looks like this on my local branch:

@eyurko please take another look when you have time! thanks :)


Missing type annotation in PyCharm when using Model.parse_obj()

Initial Checks

[X] I have searched GitHub for a duplicate issue and I'm sure this is something new
[X] I have searched Google & StackOverflow for a solution and couldn't find anything
[X] I have read and followed the docs and still think this is a bug
[X] I am confident that the issue is with pydantic  (not my code, or another library in the ecosystem like FastAPI or mypy)

Description
I like using the help feature of PyCharm (pressing F1 on a variable) to see which type it has.
This works well when creating a model using a dict or just the constructor call but PyCharm displays "None" when using Model.parse_obj().
In case that's a bug in PyCharm instead, I am happy to report it there, as well.

Example Code
import pydantic

class M(pydantic.BaseModel):
    val: int = 1

def test():
    instance = M(val=1)
    parse_obj = M.parse_obj({"val": 1})

Python, Pydantic & OS Version
pydantic version: 1.9.1
            pydantic compiled: True
                 install path: /Users/cleancoder/Library/Caches/pypoetry/virtualenvs/juice-report-m7V9HNF8-py3.9/lib/python3.9/site-packages/pydantic
               python version: 3.9.9 (main, Nov 30 2021, 17:19:58)  [Clang 13.0.0 (clang-13<IP_ADDRESS>)]
                     platform: macOS-12.5.1-arm64-arm-64bit
     optional deps. installed: ['devtools', 'dotenv', 'email-validator', 'typing-extensions']

Affected Components

[ ] Compatibility between releases
[ ] Data validation/parsing
[ ] Data serialization - .dict() and .json()
[ ] JSON Schema
[ ] Dataclasses
[ ] Model Config
[ ] Field Types - adding or changing a particular data type
[ ] Function validation decorator
[ ] Generic Models
[X] Other Model behaviour - construct(), pickling, private attributes, ORM mode
[ ] Settings Management
[ ] Plugins and integration with other tools - mypy, FastAPI, python-devtools, Hypothesis, VS Code, PyCharm, etc.

I wanted to start a PR on that but just noticed that in a clean environment, this problem does not occur and PyCharm displays the type correctly. Closing for now.


"[HMR] bundle rebuilding" is running on and on

When I run the app for the 1st time everything is OK. Bundles are generated etc..
After a simple change in client side code, the HMR rebuild the component but does not stop:

I have to shut down IISExpress/host and run application again.
I don't see any errors in the console, tslint has no errors, webpack builds without any errors.
Wny ida why is this happening?

I had the same issue, cpu and memory are up high as a result.
I turned off HotModuleReplacement to resolve this issue

@robertcck Yep, that's the only solution I found. BTW do you use primeng? I read in other discussions that it might actually cause the HMR issue.

When copy our app code in app folder we have the same issue.

Hello again,
this happened when i added/imported css in vendor,
i am not sure what couses your problem to happen but i just wanted to notice.
for example, this actions made my situation same HMR build again and again,
when using primeng its css coused some problems..
when i tryed to add custom angular material theme like exactly described on their site.
good luck

Are you using Visual Studio 2017?

@crh225 I have this setting in my csproj file.

Ps.
Today again i faced with this problem,
problem was coused by PrimeNg Editor Component, I am not installing with npm using source code of PrimeNg becouse i need some custom needs on their component.
and when i remove Editor/Quill from project HMR runs perfectly...

this problem hitting again ...
could someone find certain solution ?

I was facing the same issue today with [HMR] bundle rebuilt
Removing "allowJs": true in tsconfig.json made the trick.

I was also facing this issue, fixed by removing "declaration": true in tsconfig.json.

tsconfig is a little clean now. so if allowJs was the issue it shouldn't happen anymore. As always I cannot reproduce this. Closing this one until someone ca see this issue again in a specific scenario. Thanks

I am facing this issue.
I am using VS 2107. And I have set allowJS to true. removing allowJS property fixes the issue. but I need this property to be set to true as I need to use some js files (which are not yet converted to typescript).

@nimishsakalkale I am sure you can use javascript file in any project. You somehow need to exclude it from typescript compilation if that isn't the requirement.
try some of the suggestions describe here and here.

@asadsahi  Adding  wwwroot and ClientApp/dist to the tsconfig.json exclude list fixed the problem. Thank you.

@sylvaincaillot THANKING YOU! New to this and you have saved the day haha


Mainmenu Mods

Describe your bug here.
When I turn off mod (restart game) and I do exit
Crash Log or logcat logs (if existing)
Null Object Reference
flixel/graphics/frames/FlxAtlasFrames.hx [line 401]
flixel/graphics/frames/FlxAtlasFrames.hx [line 247]
source/objects/Alphabet.hx [line 435]
source/objects/Alphabet.hx [line 360]
Type.hx [line 90]
flixel/group/FlxGroup.hx [line 338]
source/objects/Alphabet.hx [line 222]
source/objects/Alphabet.hx [line 88]
source/objects/Alphabet.hx [line 37]
source/states/TitleState.hx [line 520]
source/states/TitleState.hx [line 577]
source/backend/MusicBeatState.hx [line 247]
source/backend/MusicBeatState.hx [line 134]
source/states/TitleState.hx [line 513]
flixel/FlxState.hx [line 222]
flixel/FlxGame.hx [line 752]
flixel/FlxGame.hx [line 682]
flixel/FlxGame.hx [line 556]
openfl/events/EventDispatcher.hx [line 444]
openfl/display/DisplayObject.hx [line 1400]

Are you modding a build from source or with Lua?
Source
What is your build target?
Android
Did you edit anything in this build? If so, mention or summarize your changes.
No, I didn't

upstream issue


[OAP-1610][SQL-Data-Source-Cache][SDLe]Modify pom.xml to pass SDLe BDBA binaries vulnerabilities scanning

What changes were proposed in this pull request?
OAP will release as a binary product, and offer users jars, so it should comply with intel SDL rules. After executing BDBA scanning binaries for known vulnerabilities, some jar dependencies should exclude or upgrade 3rd party  components which have security vulnerabilities in the pom.xml.
Fixed: #1610    [SQL Data Source Cache]
How was this patch tested?
Pass BDBA scanning for known vulnerabilities.
Also pass vmemcache Binary 3TB TPCDS

@HongW2019  Please make sure that there are no problems in the integration testing.


A question about navigation

I'm using this template, It works well. But I have a question, how to keep the ViewModel when changing screen?

May I ask, is there any apparent reason, why data package is not in main but at the top level in the structure?


Docs.MS Release Updates for azure_media_analytics_edge

Update docs metadata and targeting for release of azure_media_analytics_edge

Docs Build status updates of commit 7e28ced:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-services/preview/media-analytics-edge-readme.md
:warning:Warning
View (azure-python-preview)
Details

ci-configs/packages-preview.json
:white_check_mark:Succeeded

docs-ref-services/preview/media-analytics-edge-readme.md

Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 7e28ced:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-services/preview/media-analytics-edge-readme.md
:warning:Warning
View (azure-python-preview)
Details

ci-configs/packages-preview.json
:white_check_mark:Succeeded

docs-ref-services/preview/media-analytics-edge-readme.md

Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Closing in favor of combined commit here.

Closing in favor of combined commit here.


Update event-4769.md

Add details to some of the error logging details...

Why

Closes #[Issue Number]

Changes

@HerbertMauerer Thanks for the contribution. I've made some minor edits and merged this PR.


Tweek Image Re-sizing

Make sure images are re-sizing properly

Users can now modify their own settings for better options.


added_about_page

Added new page called About Data Triad and updated index.vue to reflect new page creation.

A bit more detail for you...
The page will end up something like this (the styles/layout aren't done here, just an idea of the structure)
<template>

About Data Triad

Vision

        Vision: Cultivating a dynamic community of local and virtual data scientists focused on
        employing data for actionable and engaging applications.

Mission

 Empowering and enhancing the practical application of data science.

    <Events />

</template>


demo uses v2 of API, but pydocusign does not support v2 yet

i wrote an app using this library based on the assumption that v2 of the API was supported (based on the implementation in the demo).  Reverting to v1 is causing regressions.  This app's demo should probably be tested against v1, to prevent further confusion.

It should be fixed in 1.2


Format ATTs in Appendix

Fixed up the formatting of the ATTs in the Appendix to be consistent with the rest of the report

Fixed ATTs in appendix


NXP: Added RT1021, RT1052, RT1064; update RT1062.

From Zephyr hal_nxp before it started to use mcux-sdk.

Thanks @GrixaYrev


refactor!: change universalReceiverDelegate(..) to universalReceiver(..)

What does this PR introduce?
Breaking Change 🚫

Removing the LSP1UniversalReceiverDelegate function, interface and interfaceId.
Switch universalReceiverDelegate(..) function to universalReceiver(..)
Change the logic in LSP0/LSP9 universalReceiver function

From:
- Checking LSP1_DELEGATE interfaceId
- Calling the universalReceiverDelegate(msg.sender, msg.value, typeId, data)
To:
- Checking LSP1 interfaceId
- Calling the universalReceiver(typeId, data) appended with extra 52 calldata containing: bytes20(msg.sender) and bytes32(msg.value)
Periphery

Add logic in LSP9 where only reentrant URDs can setData on the Vault.

This will fix the fact that Mapped UniversalReceiverDelegate couldn't set data before, and will fix the condition of setting data in normal calls.
Before, the main UniversalReceiverDelegate (URD) was able to setData on the vault, even if the URD was not reacting on the call. This behavior made the URD act like an access contract to setData on the vault, where this is completely not the behavior wanted. The main intention of allowing the URD to setData is to react on incoming calls and notification and avoid nesting calls with the owner of the UP (KeyManager for example) - to the UP - to the vault -- to setData.
The new behavior applied:
When a call will be forwarded to a UniversalReceiverDelegate contract in the LSP9Vault, the address of this contract is saved in the storage, and this address can setData only in the same tx.

It would be good to explain briefly in the PR description this:

Change the logic in LSP0/LSP9 universalReceiver function

What was changed compare to before? Like what's the old behaviour + what is the new behaviour?
In very brief, without too much details.
Bust just to understand what is the change.

@CJ42 Already described here


required exports missing in install.md

export PATH=$ZZROOT/bin:$PATH
export LD_LIBRARY_PATH=$ZZROOT/lib:$ZZROOT/lib64:$LD_LIBRARY_PATH
Without them zzlibx24.sh fails.

thanks for the info!

Still I can't get zzopencv compile...
Please find logs attached.
CMakeOutput.log
CMakeError.log
BTW, is there a Docker image with denseflow working?
I tried vlali/denseflow:local and found no denseflow inside.

what's the gcc version?
googling the error msg, maybe https://github.com/opencv/opencv/issues/9493 helps.

gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
Maybe the issue is cudnn missing? Could not find, if it's required for opencv...
output.log

cuda and cuddn are required. this repo only provides gpu version.

docker is a good feature to add. hope someone can give a pr


Removed GCC High and DoD information

per IM request

Docs Build status updates of commit 93bcb32:
:clock10: Full build: the average full build time is 17 min(s) 38 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 93bcb32:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/connect-to-scc-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Connect-IPPSSession.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit fa936f6:
:clock10: Full build: the average full build time is 17 min(s) 38 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit fa936f6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/connect-to-scc-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Connect-IPPSSession.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 913f0c0:
:clock10: Full build: the average full build time is 17 min(s) 40 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 913f0c0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/connect-to-scc-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Connect-IPPSSession.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 92478c3:
:clock10: Full build: the average full build time is 17 min(s) 40 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 92478c3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/connect-to-scc-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Connect-IPPSSession.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit b37d81d:
:clock10: Full build: the average full build time is 17 min(s) 40 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit b37d81d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/connect-to-scc-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Connect-IPPSSession.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Source Installation: "kaldi already exists and is not empty"

Hello,
Trying to follow the source-install instructions from the README, and it has the following. First it says to:
git clone https://github.com/pykaldi/pykaldi.git
cd pykaldi

but later it says to
git clone -b pykaldi https://github.com/pykaldi/kaldi

At which point, git clone throws a fit, because there's already a "kaldi" directory. Any idea how to workaround this?

You dont need to run the git command manually, you can simply run the
install_kaldi.sh script in tools. Sorry for the confusion, we'll soon
upgrade the Readme
See also the instructions on PyKaldi @
https://github.com/uhh-lt/kaldi-model-server
Am Fr., 11. Juni 2021 um 19:41 Uhr schrieb cdleong @.***

:

Hello,
Trying to follow the source-install instructions from the README, and it
has the following. First it says to:
git clone https://github.com/pykaldi/pykaldi.git
cd pykaldi
but later it says to
git clone -b pykaldi https://github.com/pykaldi/kaldi
At which point, git clone hrows a fit. Any idea how to workaround this?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pykaldi/pykaldi/issues/277, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACKGA6RK4PDGVIFP34PWQETTSJDGHANCNFSM46RFSM3Q
.

Oh, I gotcha. So install_kaldi.sh will work without having to clone the special branch first?

yes it includes the correct clone command
Am Fr., 11. Juni 2021 um 20:25 Uhr schrieb cdleong @.***

:

Oh, I gotcha. So install_kaldi.sh will work without having to clone the
special branch first?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/pykaldi/pykaldi/issues/277#issuecomment-859762490,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACKGA6S6ELPCRPGHRSJ2PALTSJIKXANCNFSM46RFSM3Q
.


Clicking homepage video to pause will not pause

When I click "Play" on the video on the homepage, it will play.
However, if I click the body of the video in order to pause it, it will not pause. It only pauses when I click the pause button.
I could see how this could be determined as "expected behavior", but I thought I would bring it someone's attention as it surprised me.
I am using Chrome Version 81 on Windows 10.
I reproduced using Chrome, Version 81 on Windows 10 on browserstack.
Would this project be open to using an open source media player for videos? I've found the HTML5 video element to be quite buggy in it's implementation throughout browsers and that might be a more simplistic solution in the long run.

I could reproduce this on the live version using chromium, but not locally. Actually, the video doesn't really work locally on chromium. I tried with #994 but i didn't notice any difference.

I think this bug can be closed, as I just tested this after the most recent Chrome update (version 83), and it seems to be working fine now.


Conditionally Stream PageData : Universal vs Server

Describe the bug
Hi,
I'm facing a challenge with handling data streaming only conditionally for client-side rendering.
To stream some data only for CSR, I use in my +page.server.ts file :
export const load: PageServerLoad = async ({ fetch, isDataRequest }) => {
  // fetching some data ...
  return {
    someData: isDataRequest ? someData : await someData,
  };
};

This setup works perfectly for server-side rendering (SSR), but since the data is fetched from a public API, I want the client to make the request itself and not the server when we are not in a server-side context.
To accommodate this, in my +page.ts file, I have the following implementation:
import { browser } from '$app/environment'; // replace isDataRequest
export const load: PageLoad = async ({ fetch }) => {
  // fetching some data ...
  return {
    someData: browser ? someData : await someData,
  }
};

While this approach works, it leads to an undesired effect. Since the page.ts file is executed both by the server and the client, the page initially renders with someData having a value from the server. Subsequently, it redraws with someData being a Promise, causing the {#await} block to enter a pending status. Finally, when the promise resolves, it triggers another redraw.
I understand that this behavior is expected due to the nature of SvelteKit's universal rendering, where PageLoad is called by both the server and the client. However, I'm seeking guidance on the correct approach to handle this scenario.
I'm looking for suggestions on how to effectively handle data streaming for client-side rendering in SvelteKit without causing the unwanted redraw effect. Any insights or best practices would be greatly appreciated.
Reproduction
Use +page.server.ts OR +page.ts with +page.svelte.
Both +page.server.ts and +page.ts do the same exact work
// +page.server.ts
export const load: PageServerLoad = async ({ fetch, isDataRequest }) => {
  const someData = async () => {
    // fetching some data
    await new Promise(r => setTimeout(r, 5000));

    return {};
  })();

  return {
    someData: isDataRequest ? someData : await someData,
  };
};

// +page.ts
import { browser } from '$app/environment'; // replace isDataRequest
export const load: PageLoad = async ({ fetch }) => {
  const someData = async () => {
    // fetching some data
    await new Promise(r => setTimeout(r, 5000));

    return {};
  })();

  return {
    someData: browser ? someData : await someData,
  }
};

// +page.svelte
<script lang="ts">
  export let data: PageData;
</script>

{#await data.someData}
  loading some data ...
{:then mydata}
  {JSON.stringify(mydata)}
{/await}

Logs
No response
System Info
System:
    OS: macOS 14.2.1
    CPU: (8) x64 Intel(R) Core(TM) i7-8557U CPU @ 1.70GHz
    Memory: 271.61 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.20.0 - ~/.nvm/versions/node/v18.20.0/bin/node
    npm: 10.5.0 - ~/.nvm/versions/node/v18.20.0/bin/npm
  Browsers:
    Chrome: 123.0.6312.87
    Safari: 17.2.1
  npmPackages:
    svelte: ^4.0.5 => 4.2.12

Severity
annoyance

Firstly it feels odd to use both server and shared load in this case. The shared load function should be enough here. Bit i dont think you can stream data coming from +page.ts loads?
You could also take a look at svelte-query to cache the data client side and provide your loading strategy of choice


support for international locales.

Looks like we need to rewrite this to support other keys.
For example I need soon:
key client https://developers.google.com/maps/documentation/business/clientside/#client_id
and key libraries https://developers.google.com/maps/documentation/javascript/libraries
So we need implementation like
export default function googleMapLoader(api:string | object)

string to support previous behavior and object for a new
Where object keys is url query params.
so I can to load googleMap as before using api key, or use new api prop, with all keys I need
like
<GoogleMap api={{
  client: 'mysuperclient',
  libraries: 'a,b,c',
  ...etc
}}

If both new api object and old apiKey both presented we need to give a warning in dev mode and use api object.

May be rename api to other name something like bootstrapURLParams or something more good.

+1

Fixed here
https://github.com/istarkov/google-map-react/commit/862a6e85c45d6c9533e4dd9791969593a141cd91
Usage
<GoogleMap
  bootstrapURLKeys={{
    key: API_KEY,
    language: 'ru',
    ...otherUrlParams,
  }}
>
...


mobile: update bazelw to pull bazelisk 1.15.0

This pulls in a number of small but useful fixes: https://github.com/bazelbuild/bazelisk/compare/v1.10.1...v1.15.0
Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/assign @keith

Now that we have this wrapper in this repo, perhaps we could consider moving it up to the root directory so it's available even outside of mobile/ stuff.

/retest


Add env variable SOTO_CROSS_COMPILE to enable cross compile of package

This is a complete hack, but without https://bugs.swift.org/browse/SR-13761 being fixed soto-core requires the if statement at the base of the Package.swift. This causes cross compilation to fail as the Package.swift is read by macOS and the switch on which OS is being run fails.

Closing this as this is resolved on the v7.0 branch


Is yt-dlp ever planning to add metadata to individual chapters when using --split-chapters?

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I remove or skip any mandatory* field

Checklist

[X] I'm requesting a feature unrelated to a specific site
[X] I've looked through the README
[X] I've verified that I'm running yt-dlp version 2022.10.04 (update instructions) or later (specify commit)
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Provide a description that is worded well enough to be understood
I read in the bugtracker how you would have to redo the --split-chapters feature for it to work, so is this ever gonna be a planned feature? If not, is there a way you can replace the (title) metadata with the file name in the config file? Right now it looks like this
 the top is the file name and the bottom is what vlc reads as the title metadata (theyre all the same name).

This is my config file if it helps
Provide verbose output that clearly demonstrates the problem

[ ] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
No response

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[x]  I understand that I will be blocked if I remove or skip any mandatory* field

Checklist

[x]  I'm requesting a feature unrelated to a specific site
[x]  I've looked through the README
[x]  I've verified that I'm running yt-dlp version 2022.10.04 (update instructions) or later (specify commit)
[x]  I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[x]  I've read the guidelines for opening an issue

Provide a description that is worded well enough to be understood
I read in the bugtracker how you would have to redo the --split-chapters feature for it to work, so is this ever gonna be a planned feature? If not, is there a way you can replace the (title) metadata with the file name in the config file? Right now it looks like this   the top is the file name and the bottom is what vlc reads as the title metadata (theyre all the same name).  This is my config file if it helps
Provide verbose output that clearly demonstrates the problem

[ ]  Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ]  Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
No response

see this here - https://superuser.com/questions/996223/using-ffmpeg-to-copy-metadata-from-one-file-to-another would this work ??

im not that good with programming stuff. is there a certain command from this that i should paste into the config file?

you should have ffmpeg already installed with yt-dlp.

thank you, ill try this and post the results

https://github.com/yt-dlp/yt-dlp/issues/951

i tried the code and it didnt seem to replace the chapters title metadata with the file name, but making the title metadata blank looks like it worked for vlc
#--parse-metadata "chapter:(?P)"

i tried the code and it didnt seem to replace the chapters title metadata with the file name, but making the title metadata blank looks like it worked for vlc
#--parse-metadata "chapter:(?P)"

how to use for -o "chapter:%%(title)s\%%(section_number)03d. %%(section_title)s.%%(ext)s"


Unnecessary precision in float values

A row is defined in the database like this: myfield float DEFAULT NULL
This field has a value of 0.2
A type definition has a field like this: MyField   float64   gorm:"column:myfield"
When we get this here, it shows a value like 0.20000000298023224.
How do we get it to be with normal precision?
I tested this out with a small piece of code as below and am unable to see the same issues:
CREATE TABLE test_numbers (
          id bigint(20) NOT NULL AUTO_INCREMENT primary key,
          f float default null,
          fp float(13,8) default null,
          d double default null,
          dp double precision(13,8) default null
        ) ENGINE=InnoDB DEFAULT CHARSET=latin1;

package main

import (
    "fmt"

    _ "github.com/go-sql-driver/mysql"
    "github.com/jinzhu/gorm"
)

type Model struct {
    F  float64 `gorm:"column:f"`
    FP float64 `gorm:"column:fp"`
    D  float64 `gorm:"column:d"`
    DP float64 `gorm:"column:dp"`
}

func main() {
    connStr := "root:@tcp(localhost:3306)/mydb?parseTime=true"
    db, err := gorm.Open("mysql", connStr)

    if err != nil {
        fmt.Println(err)
        return
    }

    var models []Model
    db.Table("test_numbers").Find(&models)
    for _, v := range models {
        fmt.Printf("\n%+v\n", v)
    }
}

Not sure why I was unable to replicate it in independent code, but I changed the sql field type to double in my other code and it started working as expected with only required precision.

I've the same issue, using float32 or float64 does not solve, how I can do? the SQL created field (using MySql) is double instead of float...

I've the same issue, to translate type data float in sql to gorm model, the data IconPosX and IconPosY always 0.
this my . struct :
type Icons struct {
Id int gorm:"column(id);
Name string gorm:"column(name);
IconPosX float32 gorm:"column(icon_pos_x);FLOAT(5,2);"
IconPosY float32 gorm:"column(icon_pos_y);FLOAT(5,2);"
}
in the sql database IconPosX and IconPosY type data is FLOAT(5,2)


set cpu/memory resource requests and limits

What type of PR is this?

type::chore
What this PR does / why we need it:
Sets memory requests and limits for staging and prod cluster
Which issue(s) this PR fixes:

Fixes #
na
Special notes for your reviewer:

Steps to reproduce

set the same resources
Does this PR introduce a user-facing change?

NONE

Does this PR require documentation?

NONE

@divolgin see below for most recent usage
prometheus last long living deployment
5/26 - 6/2

datadog last 30 days
requests based on highest average

@divolgin  see above for usage metrics


No loading of new Scene

I have been trying to create two buttons to switch between two scenes (and more in the future), but the loadScene command just doesn't want to work if you click on the buttons. The scene looks great, but the buttons don't work. Does anybody have an idea why?
Thanks in advance, Johan

1

2

// Assigning actions to buttons:
document.getElementById('Image_1').addEventListener('click', function() {
    viewer.loadScene("Mudflat1");
});
document.getElementById('Image_2').addEventListener('click', function() {
    viewer.loadScene("Mudflat2");
});

To see the current version online:
https://people.zeelandnet.nl/jvdkoppel/Panos/BESE.html

Hello, please change
#1
pannellum.viewer('panorama', {
to
myViewer = pannellum.viewer('panorama', {
#2
viewer.loadScene("Mudflat1");
to
myViewer.loadScene("Mudflat1");

Ah, an object. It worked! Thanks


upstream 4.13-2

This PR was added to follow the agent release 4.13 which finally resolved a websockets reconnect issue (see https://github.com/jenkinsci/docker-inbound-agent/pull/268)

Thank you @jforge!


Consinder adding WithConfBindMount method for configured conf directory for Redis resource

The Redis container image supports setting a custom conf directory so that a custom redis.conf file can be used to initialize the Redis server. We should consider adding an extension method to make it easy to configure this, e.g.:
/// <summary>
/// Adds a bind mount for the conf folder to a Redis container resource.
/// </summary>
/// <param name="builder">The resource builder.</param>
/// <param name="source">The source directory on the host containing the <c>redis.conf</c> file to mount into the container.</param>
/// <returns>The <see cref="IResourceBuilder{T}"/>.</returns>
public static IResourceBuilder<RedisResource> WithConfBindMount(this IResourceBuilder<RedisResource> builder, string source)
    => builder.WithBindMount(source, "/usr/local/etc/redis", isReadOnly: false)
              .WithArgs("/usr/local/etc/redis/redis.conf");

How would this interact with deployment scenarios or do you see this more as a debugging thing?

It would result in a bind mount for the resource in all cases (assuming publishing as a container). Folks can use if statements to only call it in the context they want, or we can consider expanding the Publish/Run prefixes to these kinds of methods too (which I'm a fan of), e.g. RunWithConfBindMount.


Organise Folders and Files

Working on that Right now.  I've Created 2 Milestones (the bigger Picture that the Issues at hand can go inside of) and 2 Labels (where I'm first labeling out the Issues to help narrow down Design from Programming and more labels if needed.  Currently connecting the Issues with labels and taking further steps I went over a few times from LinkedInLearning Course on Github Issues and Projects for Teams with Teresa Luz Miller (I think the Github they had as an example may be missing or I may have typed it wrong before...


Allow raw years (2020) as date strings in CSV / JSON files.

Fixes #560

Yeah, the problem is actually a bit subtle.  It's related to the fact that CSVs don't differentiate numbers from strings so we have to infer the type and if you had a raw number date (2022) we would parse it to a number.  I realized though that we can "fix" that and force the date column to be parsed as a string.  That's probably a bit cleaner.  So I went ahead and tweaked the logic to do that.


DefaultAzureCredential authentication path throws NotImplementedError on Windows 10

What happened:
On Windows 10:
Including 'anon':False in the storage_options throws NotImplementedError on asyncio.get_child_watcher().attach_loop(self.loop)
What you expected to happen:
DefaultAzureCredentials are used to authenticate
Minimal Complete Verifiable Example:
On Windows 10:
import pandas as pd
url = "abfs://..."
pd.read_parquet(url, storage_options={"anon":False, "account_name":"..."})

Anything else we need to know?:
Providing the credentials directly (thus avoiding the call to get_child_watcher) works fine:
from azure.identity.aio import DefaultAzureCredential as AIODefaultAzureCredential
import pandas as pd
url = "abfs://..."
pd.read_parquet(url, storage_options={"anon":False, "account_name":"...", 'credential':AIODefaultAzureCredential()})

Environment:

Dask version: 2021.8,1
adlfs version: 2021.8.2
fsspec version: 2021.7.0
Python version: 3.8.8
Operating System: Windows 10
Install method (conda, pip, source): pip

Man, I've faced the same problem here.
My workaround was (you can see it in my fork, i'm preparing it for PR):
In get_default_azure_credential, I removed the asyncio part (Windows does not have get_child_watcher implemented, this function is Unix only):
https://github.com/gabrieldaiha/adlfs/blob/9d5283f5630e500f71d1ab91e7cc24e8c6592afb/adlfs/spec.py#L532-L539
I moved the get_default_azure_credential call from do_connect function to the init function, like get_service_principal_credential does.
I added a new weakref.finalize to async credentials too, in order to avoid Unclosed Client Session ERROR in the exit of the program
https://github.com/gabrieldaiha/adlfs/blob/9d5283f5630e500f71d1ab91e7cc24e8c6592afb/adlfs/spec.py#L455-L466

I think this issue is fixed by #328, thus it can be closed.


kubelet does not reload recreated immutable configmap, unclear documentation

What happened?
With immutable configmaps and secrets are not watched by the kubelet. This also means it does not refresh the loaded content when they are deleted and recreated.
The documentation of immutable configmaps though is misleading on how this needs to be handled by pods:
https://kubernetes.io/docs/concepts/configuration/configmap/#configmap-immutable

Once a ConfigMap is marked as immutable, it is not possible to revert this change nor to mutate the contents of the data or the binaryData field. You can only delete and recreate the ConfigMap. Because existing Pods maintain a mount point to the deleted ConfigMap, it is recommended to recreate these pods.

This to me implies deleting and recreating the configmap and restarting the pods using it is sufficient, but it is not as the kublet will still have the old version loaded and won't update it until it is restarted.
This behavior is more or less expected but the documentation should be more explicit about this pitfall.
What did you expect to happen?
The documentation should state that immutable objects mounted into pods need to be deleted and recreated with a different name in order for the (recreated) pods to see the new version reliably.
How can we reproduce it (as minimally and precisely as possible)?
Start a deployment with an immutable configmap mounted. Change it, delete and recreate it with the same name and restart the deployment.
Pods on the kubelet will still have the old version until the kubelet is restarted and then the pods restarted.
see https://github.com/kubernetes/website/issues/42359#issuecomment-1663582989 for an example deployment
Anything else we need to know?
No response
Kubernetes version

$ kubectl version
Server Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.3", GitCommit:"25b4e43193bcda6c7328a6d147b1fb73a33f1598", GitTreeState:"clean", BuildDate:"2023-06-15T00:36:28Z", GoVersion:"go1.20.5", Compiler:"gc", Platform:"linux/amd64"}

Cloud provider
bare metall
OS version
No response
Install tools

Container runtime (CRI) and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)

I believe from the evidence here that we may be able build a test case where, starting from a namespace that contains:

no ConfigMaps
no Pods

can create a ConfigMap and a Pod that references the ConfigMap, and (because of what was previously in that namespace) see the old ConfigMap loaded into that Pod. Even if the new ConfigMap is not marked as immutable.
The period where that's possible might be quite short though.

This sounds more plausible;  starting from a namespace that contains:

no ConfigMaps
some running Pods that reference a previous immutable ConfigMaps

create a new ConfigMap (same name) and a new Pod. You may observe that the new Pod appears to have loaded the wrong data, from the old ConfigMap.
We might need to define that you should delete every object that could have had a reference to that old ConfigMap - potentially including cluster-scoped objects such as IngressClasses and ValidatingAdmissionPolicies.
Advising people to create the replacement ConfigMap with a different name is not enough; we cannot assume that a different user is aware of the potential problems around use of the old name.

We might be able to detect in-use immutable ConfigMaps (within the control plane), and do something around finalizing them. That mechanism could eventually enable sending a warning when an immutable ConfigMap is deleted whilst still in use.

I recommend that SIG Architecture chip in here.
/sig architecture

/assign @pegasas

Hi, @sftim ,
I do the test case that you mentioned in Azure Kubernetes 1.25.11,
apiVersion: v1
kind: ConfigMap
metadata:
  name: special-config
  namespace: default
data:
  special.how: test
immutable: true

and
apiVersion: v1
kind: Pod
metadata:
  name: ubuntu
  labels:
    app: ubuntu
spec:
  containers:
  - image: ubuntu
    command:
      - "sleep"
      - "3650d"
    env:
      - name: SPECIAL_LEVEL_KEY
        valueFrom:
          configMapKeyRef:
            name: special-config
            key: special.how
    imagePullPolicy: IfNotPresent
    name: ubuntu
  restartPolicy: Always

and I create these 2 in k8s cluster, and echo the key:
kubectl exec -it ubuntu -- /bin/sh
# echo $SPECIAL_LEVEL_KEY
very

and after I delete the cm, it keeps the same value:
kubectl exec -it ubuntu -- /bin/sh
# echo $SPECIAL_LEVEL_KEY
very

The motivation for Immutable ConfigMap/Secret is to avoid watching them. Since they are immutable, you get what is in it, and treat it as constant. You don't care about the future changes to them, they are immutable after all. If you want to watch them, especially for updates, you won't use immutable ConfigMap/Secret.
Protecting ConfigMap/Secret in use is another topic. See KEP 2840.

The test case explained in https://github.com/kubernetes/website/issues/42359#issuecomment-1663073555 covers already documented behavior; if that's the test case, I don't think we need to make a docs change.
I thought you were concerned about ConfigMap removal and recreation with a new uid @juliantaylor, where a new Pod might see the old ConfigMap.

Protecting a configmap from being deleted while it is in use is not sufficient, a configmap or secret name cannot be reused after it has been deleted until all kubelets have been restarted or you risk a pod seeing old content.
This likely also happens long after all pods using the old version are long gone (create deployment and cm, delete it, wait some time redeploy with different configmap), though I have not explicitly verified longer timescales.
The practical solution to this is to have immutable configmaps and secrets name contain the checksum of its content. That way it is almost impossible for wrong data to end in a pod even when the kubelet runs for a long time.
This practice should be mentioned in the documentation.
If you can fix the underlying issue all the better, but as stated the point of immutable is to reduce api requests and watches, so watching for deletes is not an sensible option.
Possibly you could have the kubelet refetch the object when it is required but only if it already exists as immutable in its caches.

The practical solution to this is to have immutable configmaps and secrets name contain the checksum of its content.

Let's make sure we know what (replicable) problem we're helping people to avoid, before we triage this as accepted.

ok here the reproducer I stated in the beginning written out:
---
apiVersion: apps/v1
kind: Deployment
metadata:
  annotations:
  name: cm-test
spec:
  replicas: 7
  selector:
    matchLabels:
      app: cm-test
  template:
    metadata:
      labels:
        app: cm-test
    spec:
      terminationGracePeriodSeconds: 1
      volumes:
        - name: cm
          configMap:
            name: testcm
      containers:
      - image: debian:bookworm
        command:
          - bash
          - "-c"
          - 'while true; do echo -n "$NODENAME "; md5sum /cm/script.py || true; sleep 20; done'
        imagePullPolicy: Always
        name: test
        securityContext:
          runAsUser: 1000
        volumeMounts:
          - name: cm
            mountPath: /cm
        env:
          - name: NODENAME
            valueFrom:
              fieldRef:
                apiVersion: v1
                fieldPath: spec.nodeName
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: testcm
data:
  script.py: "content7"
immutable: true

kubectl apply -f deployment.yaml
logs:
kworker-be-sandbox-iz2-bap004 f4a40d590cbb53290e7ba914e24a346c  /cm/script.py
kubectl delete cm testcm
sed -i -e "s/content7/content8/" deployment.yaml
kubectl apply -f deployment.yaml
logs (same checksum)
kworker-be-sandbox-iz2-bap004 f4a40d590cbb53290e7ba914e24a346c  /cm/script.py

restart the kubelet or launch on a node teh pod was not on yet and you get the new content

full delete of the deployment does seem to refresh the configmap, so kubelet may have something to cleanup unused configmaps, in that case protecting deletion in use would work

Any updates? Unless it can be trivially fixed and released fast, I just want the documentation to be updated to make the existing semantics of immutable objects clearer.

@juliantaylor the Kubernetes project is open source and the documentation is largely maintained by volunteers.
Depending on how much you want a fix, you could:

volunteer to fix it yourself - see https://kubernetes.io/docs/contribute/
pay someone else to fix it
keep waiting

However, we first want to make sure we understand what needs fixing, or made more clear. Can you help with that part?

Hi, @juliantaylor ,

The practical solution to this is to have immutable configmaps and secrets name contain the checksum of its content. That way it is almost impossible for wrong data to end in a pod even when the kubelet runs for a long time.
This practice should be mentioned in the documentation.

You aim to add this into docs as a supplement, right?
I think the community thinks the immutable secret feature is designed as immutable, you treat it as constant and don't care about the future changes to them.
I think your scenario may obey our design rule.
What do you think?

Yeah, indeed it fits this behavior you mentioned.
However, I think it may mislead users to delete and recreate immutable secrets.
If you want to modify the secret, you should use the secret directly rather than immutable secrets.
We do not encourage this behavior because it is not by design.

The motivation for Immutable ConfigMap/Secret is to avoid watching them. Since they are immutable, you get what is in it, and treat it as constant. You don't care about the future changes to them, they are immutable after all. If you want to watch them, especially for updates, you won't use immutable ConfigMap/Secret.
Protecting ConfigMap/Secret in use is another topic. See KEP 2840.

The test case explained in #42359 (comment) covers already documented behavior; if that's the test case, I don't think we need to make a docs change.
I thought you were concerned about ConfigMap removal and recreation with a new uid @juliantaylor, where a new Pod might see the old ConfigMap.

I believe that this is what @tengqm and @sftim trying to clarify in the comments above.

I am concerned about the existing documentation implying deleting and recreating a immutable configmap/secret and restarting pods is safe to do which it is not due to the potential serving of stale content.
I'm also fine with updating it to say do not ever delete and recreate an immutable secret or configmap and remove the whole section about doing it and restarting pods. But in this case it should also be mentioned why as it is may not immediately obvious to the reader that this is unsafe and yet deletion is allowed by the API.
As for why one would use immutable configmaps, in large clusters with many larges nodes and pods the many many configmap watches do put some load on the API. The majority of configmaps never to barely ever changes e.g. root CA certificates and many deployment use versioned configurationmaps anyway (each change creates a new configmap).
So we mark as many configmaps as we can immutable even if they do occasionally change as its just free load reduction.
While updating some stuff which did not use versioned configmaps we discovered this behaviour. Why it behaves like this is clear after the fact, but needing to discover it in the first place should not be needed after reading the immutable documentation which I would like to see fixed.

May this is better at discouraging changing immutable objects:

Once a ConfigMap is marked as immutable, it is not possible to revert this change nor to mutate the contents of the data or the binaryData field. Deletion of an immutable ConfigMap should be avoided as when one recreates the immutable ConfigMap with the same name at a latter time the old deleted content may still be served from caches.

Possibly one could also clarify how long the deleted configmap/secret can be cached which I assume is as long as something in the cluster references it (e.g. a still running pod with the deleted cm mounted).

Possibly one could also clarify how long the deleted configmap/secret can be cached which I assume is as long as something in the cluster references it (e.g. a still running pod with the deleted cm mounted).

I think this is a good point for "clarify how long the deleted configmap/secret can be cached".
Then it will become not binding to this character.
we could finds a suitable place to add this into document if there is not any description right now.

Let's clarify that you should prefer to use a new name for your update to an immutable ConfigMap or Secret. If you want to use the same name, you have to first make sure that every existing reference to the old object (not just Pods, any reference) has been cleaned up.

As of today, the official docs are not clear on this subject. In both the ConfigMap and Secrets concepts pages, it states:

Once a Secret or ConfigMap is marked as immutable, it is not possible to revert this change nor to mutate the contents of the data field. You can only delete and recreate the Secret. Existing Pods maintain a mount point to the deleted Secret - it is recommended to recreate these pods.

This does not hint the user on the fact that recreated pods may still get old stale value, at least if used as environment variables. The message as it is actually suggests (IMO clearly states) that when an immutable secret actually changes, it is sufficient to recreate it and the consuming pods, which is not correct.
It took us quite some time to figure out, as we have been seeing inconsistent behavior when scheduling a pod across nodes (some nodes would see the new value, and others the old value). For an end user, this does not make any sense. From an administrator perspective, it took some time to isolate the issue and the particular level in the stack (kubelet? container runtime? race issues?) where the issue was originating. It is also breaks the assumption that the state of the cluster is seen consistently across command line users, kubelets and other observers such as operator (we are using the ExternalSecrets operator, so that's one extra layer that we had to debug and exclude from the loop to understand the problem).
IMO it should be worded about this way:

Once a Secret or ConfigMap is marked as immutable, it is not possible to revert this change nor to mutate the contents of the data field. You can only delete and recreate the Secret. Even so, the kubelet does not watch for changes on immutable Secrets and ConfigMaps, so newly created pods may still get stale data. In case one wants to ensure that the new data values are used, the suggested course of action in this case is to recreate the Secret or ConfigMap under a new name.

However, I would strongly prefer a solution that fixes the root issue, and have the kubelet check the uid or something of the requested secret/configmap, and purge its internal cache based on that.

Repeating https://github.com/kubernetes/website/issues/42359#issuecomment-1699700091 for clarity
Let's clarify that you should prefer to use a new name for your update to an immutable ConfigMap or Secret. If you want to use the same name, you have to first make sure that every existing reference to the old object (not just Pods, any reference) has been cleaned up.

It may be worse than this and that you also need to reboot nodes that have previously run Pods using the old ConfigMap, or go fix Kubernetes bugs, or whatever. However, we should nonetheless be recommending a straightforward approach: stop using the name of a ConfigMap or Secret that was once marked as immutable; make a new one instead.


Select or Custom fields do not work in Nova 4.x

See fields changed to Select in #2536

This may be better as a text field with suggestions - https://nova.laravel.com/docs/4.0/resources/fields.html#text-field


python311Packages.pyinsteon: 1.5.0 -> 1.5.1

Changelog: https://github.com/pyinsteon/pyinsteon/releases/tag/1.5.1
Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 255665 run on x86_64-linux 1

2 packages failed to build:

python310Packages.pyinsteon
python310Packages.pyinsteon.dist

3 packages built:

home-assistant-component-tests.insteon
python311Packages.pyinsteon
python311Packages.pyinsteon.dist

Part of #251878


Modded ores (other than betterend) do not generate in BetterEnd biomes

Modded ores (other than betterend) do not generate in BetterEnd biomes.
I destroyed islands in the end with commands to verify.
BCLib 1.2.2
BetterEnd 1.0.0

BetterEnd doesn't change how other mods adding their ores, if another mod don't handling other mods biomes - it is issue on its side

Isn't it possible to accept ores that spawn in Basic Biomes in BetterEnd Biomes?

There are no any ores in Vanilla End biomes. If another mod adds ore - it should add it into other modded biomes too using Fabric API

I new to Fabric modding. How do I reference a BetterEnd biome in biome list, when I register an ore generation?

I new to Fabric modding. How do I reference a BetterEnd biome in biome list, when I register an ore generation?

This is done with Biome Modification API, like this:
BiomeModifications.addFeature(
	// Check that biome is in End (Simple variant)
	context -> context.getBiome().getBiomeCategory().equals(BiomeCategory.THEEND),
	Decoration.UNDERGROUND_DECORATION,
	ore // Your Ore ResourceKey
);

If you don't want to use categories and want your ore to appear in specific biomes:
BiomeModifications.addFeature(
	// someBiomeKey is a biome ResourceKey
	context -> context.getBiomeKey().equals(someBiomeKey),
	Decoration.UNDERGROUND_DECORATION,
	ore // Your Ore ResourceKey
);


Update DataFrame shuffle method selection docs

This PR updates the DataFrame shuffle method selection docs. It replaces references to the method= keyword argument with the dask.config.set(shuffle=...) command and shuffle= keyword argument.
Closes #3886

Thanks @jrbourbeau !


New version: Ablaze.Floorp.Daylight version 11.8.0

Pull request has been created with komac v2.0.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

For moderators
This account is automated by Github Actions and the source code was created by CoolPlayLin. If you have any questions about any pull request, don't hesitate to ping @Exorcism0666, I'll get a notification.

[!important]
Please carefully review these Pull Request before merging. If it is a Pull Request for removing incorrect content and the URLs are issue, free upon manual checking, please close this Pull Request directly. (It is best to inform Exorcism0666 of the closure.)

良い一日をお過ごしください！

Automatic Validation ended with:

2024-01-18T05:30:22.0840108Z ##[error] Manifest Error: The multi file manifest has inconsistent field values. [PackageVersion] Value: 11.7.1 File: Ablaze.Floorp.Daylight.locale.ja-JP.yaml

(Automated response - build 602.)


BaseWrapper.prototype.trigger has a bad implementation

Subject of the issue
The method Vue#$emit accepts the name of the event an any number of the parameters that all being sent to the function - event handler.
But in test BaseWrapper.prototype.trigger accepts only one parameter after the event name.
Steps to reproduce
in the code:
<template lang='pug'>
my-component(@my_signal="my_signal")
</template>

<script>
…
 methods: {
  my_signal(...args) {
      console.log(args)
  }
},
…
</script>

in the test:
wrapper.find(…).trigger('my_signal', 1, 2)

Expected behaviour
it should be printed [1, 2]
Actual behaviour
it is printed [1]
Possible Solution
I think it is quite clear, there must be implemented the transfer of more than one argument.
BaseWrapper.prototype.trigger = function (eventString, ...args) {

trigger is designed to work with DOM events, as opposed to custom ones. Please see the documentation.
If you'd like to activate a custom event, how about:
wrapper.vm.$emit('customEvent', 1, 2, 3)

That will work!

trigger is designed to work with DOM events, as opposed to custom ones. Please see the documentation.
If you'd like to activate a custom event, how about:
wrapper.vm.$emit('customEvent', 1, 2, 3)

That will work!

No, it does not. I have a component "my-component", that emits a custom event "my_signal". Please write a test for the parent component using jest that function my_signal is called with 2 parameters when my-component emits the signal.

Can you fork this repo and make a PR with your minimal failing case? That would make it easier to debug and fix the problem.


Refactor parameter handling in ACA infra

Description
Updated WriteToManifest method to simplify parameter handling and moved method call. Added AddContainerAppsInfrastructureWithParameterReference test to validate manifest and Bicep template generation.
Fixes #6313
Checklist

Is this feature complete?

[x] Yes. Ready to ship.
[ ] No. Follow-up changes expected.

Are you including unit tests for the changes and scenario tests if relevant?

[x] Yes
[ ] No

Did you add public API?

[ ] Yes

If yes, did you have an API Review for it?

[ ] Yes
[ ] No

Did you add <remarks /> and <code /> elements on your triple slash comments?

[ ] Yes
[ ] No

[x] No

Does the change make any security assumptions or guarantees?

[ ] Yes

If yes, have you done a threat model and had a security review?

[ ] Yes
[ ] No

[x] No

Does the change require an update in our Aspire docs?

[ ] Yes

Link to aspire-docs issue:

[x] No

Microsoft Reviewers: Open in CodeFlow

Looks like some of the parameters are getting omitted. In AddContainerAppsInfrastructureAddsDeploymentTargetWithContainerAppToProjectResources the missing parameters are:
            "outputs_azure_container_apps_environment_id": "{.outputs.AZURE_CONTAINER_APPS_ENVIRONMENT_ID}",
            "outputs_azure_container_registry_endpoint": "{.outputs.AZURE_CONTAINER_REGISTRY_ENDPOINT}",
            "api_containerimage": "{api.containerImage}"

Yep, should be fixed now.

Looks good.


Arm64 builds

Emulator somewhat working on arm64.
I managed to find a place to get the arm64 emulator binaries. From the android studio editor release notes on August 16, 2020 (https://developer.android.com/studio/releases/emulator#emulator_for_arm64_hosts) it says your can now build the Emulator for ARM64 hosts - "Linux emulator source code now supports cross compilation from x86_64 to arm64 hosts, enabling running arm64 system images with KVM virtualization."
I took my jetson nano (as that is the platform I am interested in running this on) and flashed a fresh sd card installation following the jetson getting started pages as it had been a while since I booted it up. I also needed to install python3 and the google source REPO tool which was unsuccessful when I did it through sudo apt-get install repo so I had to install it using the manual method.
Then, I checked out the android source repository following the instructions from the release notes. Unfortunately, even with a 64GB sd card and a fresh installation with nothing else installed, the sd card ran out of space when it was checking out all the files. The next day, I did the same steps on my ubuntu x86 machine, as the release notes also state that you can cross compile from x64 to arm64. This time I had enough space to check out the repository, just a heads up, it was over 50GB in total. I attempted to build the Emulator targeting arm64, but it failed on some tests and I am not sure why. I found another page that listed some dependencies to install before building, so I installed them and tried again.
In the time that it spent building, which was multiple hours before it would fail, I came across another github issue (https://github.com/google/android-emulator-container-scripts/issues/192).  Reading this, I discovered that you can in fact download the prebuilt arm64 emulator binaries from the android CI artifact server. You want the "aosp-emu-master-dev" branch, aosp is android open source project. https://ci.android.com/builds/branches/aosp-emu-master-dev/grid. From arm64 emulator is under the linux_aarch64 heading in the emulator section, and you can download the lastest passing build which will be a green box. The link I used was https://ci.android.com/builds/submitted/8574552/emulator-linux_aarch64/latest and then clicked on sdk-repo-linux_aarch64-emulator-8574552.zip (its ~2GB btw).
I setup a docker image following this readme, and only installed "platform-tools" and "platforms;android-31" from the sdk manager. I manually extracted and moved the contents of the sdk-repo-linux_aarch64-emulator-8574552.zip to sdk/emulator. I then tried to install the "system-images;android-31;default;arm64-v8a" system image, but the sdkmanager kept refusing to because the emulator dependency was not installed - something like "error: missing emulator dependency not found." I tried to find a way to trick/prove to the sdkmanager that the emulator package was installed but I could not find any way of doing this. So I resorted to trying to download a system image manually. I found this website: https://androidsdkmanager.azurewebsites.net/AndroidSystemImages which seems a little sketch, however, all the links on the website are dl.google.com links so I went ahead and downloaded the ARM 64 v8a System Image api 31. The direct link is https://dl.google.com/android/repository/sys-img/android/arm64-v8a-31_r03.zip. I then extracted and moved the contents of the zip to sdk/system-images/android-31/default/arm64-v8a.
Next, I tried to make an emulator using the commands from the readme, but after prompting if I wanted to created a new hardware profile, the avdmanager also failed with error "error: missing emulator dependency not found." I resorted to created the emulator manually. This comment from the other github issue helped a lot: https://github.com/google/android-emulator-container-scripts/issues/192#issuecomment-885198418. I needed to create three files, advancedFeatures.ini, config.ini, and test.ini to create the avd. You can see them in the changed files in the pull request.
In the end, I was able to start the emulator using a modified command: emulator @test -no-audio -no-boot-anim -no-window -gpu swiftshader_indirect -qemu -cpu max -machine gic-version=max
I followed the instructions for the vnc docker image and built that as well, and was able to start the emulator using the same command but without the -no-window argument. unfortunately, the window does not seem to render correctly, It is a mangled black screen right now but it definitely shows up. When I close the emulator the "saving state" ui element seems to fix some of the other mangled UI elements for some reason. Will look into getting the window to render properly over vnc later but it is a start.

The git lfs objects did not upload (which is probably a good thing now that I think about it) because this is a fork and github disables creating new lfs objects on forks. So you will have to download the emulator binaries and system images yourself.

Hi @leonitousconforti thank you so much for your investigation.  I tried what you wrote, and was able to run emulator on ARM Ubunt 20.04 on AWS.  The emulator doesn't work as it is supposed to, but it is a big step forward that we were able to get to a point where we can run an emulator, thank you for figuring all that out.
I've tried three different ci build artifacts for aarch64, 7176368, 8574552, and 8572378.  Out of those, 8572378 which happened to the first build I tried, worked the best, as in that some window showed up with starting animation while the other two builds didn't.

My hopes are not so high that we will have a working build as they are just artifacts of some people developing on the android team and if they do have working arm Linux build, they would publish it...
I won't merge this PR for now, but will keep it open for updates in the future.  Once we get a working solution I will merge, then also publish a PR to the original repo.

Tried adding
GLDirectMem = on to advancedFeatures.ini as per
https://docs.microsoft.com/en-us/answers/questions/465493/android-emulator-vulkan-1dll-not-found.html
but got the same result.

Hey any luck? Wish I could help on these testings but they are just too complicated to me.


Extends should merge ports

docker-compose source code: https://github.com/docker/compose/blob/master/compose/config/config.py#L1150

There might be an edge case when canonicalizing the address (e.g. <IP_ADDRESS>:1234:1234/tcp and 1234:1234/tcp might be considered equal, but not by docker-compose)


app info button/menu entry

would it be possible to add a button/menu entry that brought the user to the app into dialog found in system settings?
This because ending a process from there seems to be more potent than ending it from inside OSMonitor.

I added it to the new version, which will be released in a few, I will close the ticket after the new version is stable.

Thanks. So far it seems to work right when using the long press menu, but the landscape view needs a bit more work (button brings up the logs window, and the logs button is vertical-ish).


TypeError: Failed to parse URL from ./extensions/github.copilot-nightly-1.83.50/dist/tree-sitter.wasm

It looks like GH Copilot fails to work in E24, maybe related to the global fetch now being present in node.js 18:
Extension Host] [ERROR] [promptlib proxy] [2023-04-25T06:54:59.539Z] TypeError: Failed to parse URL from /Users/bpasero/.vscode-exploration/extensions/github.copilot-nightly-1.83.50/dist/tree-sitter.wasm
    at Object.fetch (node:internal/deps/undici/undici:14152:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) (at console.<anonymous> (/Applications/Visual Studio Code - Exploration.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:98:155677))
I @ console.ts:137

ERR [Extension Host] [ERROR] [promptlib proxy] [2023-04-25T06:54:59.542Z] Error: Worker thread exited with code 1.
    at Worker.<anonymous> (/Users/bpasero/.vscode-exploration/extensions/github.copilot-nightly-1.83.50/dist/extension.js:8:1235149)
    at Worker.emit (node:events:513:28)
    at Worker.[kOnExit] (node:internal/worker:280:10)
    at Worker.<computed>.onexit (node:internal/worker:200:20)

The underlying issue is from Emscripten https://github.com/emscripten-core/emscripten/commit/eab875588e7517e6ba86883be010d38b93f914bd, it will be addressed if copilot bumps web-tree-sitter to v0.20.8 https://github.com/tree-sitter/tree-sitter/issues/1765

Looks like https://github.com/tree-sitter/tree-sitter/releases/tag/v0.20.8 is out. @bmuskalla could Copilot update?

Yes, we'll update soon https://github.com/github/copilot-client/issues/1982

@bmuskalla any updates?

The team is still working on it but got sidetracked by more important issues

@SmallLemur Any updates here? Thanks!

@joaomoreno web-tree-sitter was updated. This should be working as of copilot-nightly-1.89.162

Thanks @deepak1556! I'll watch there


Missing Firewall Rule

The page is missing a firewall rule. The communication between VMs will not work unless you:
New-NetFirewallRule –DisplayName "Allow ICMPv4-In" –Protocol ICMPv4

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

ID: 0f0990fc-9834-bde3-5e06-071c75fa89a5
Version Independent ID: 96f5df37-aa95-443d-2500-37665179ce89
Content: Quickstart: Create a virtual network - Azure portal - Azure Virtual Network
Content Source: articles/virtual-network/quick-create-portal.md
Service: virtual-network
GitHub Login: @KumudD
Microsoft Alias: kumud

Thank you for your feedback! We will review and update as appropriate.

Hello @KyleLJohnson, apologies for the delayed response here. The documentation has been updated with the requested content. We will now proceed to close this issue out. Thank you for the feedback.


Limit max size of displayed filters on structured logs and traces pages

Description
Add maximum width to filter buttons. Goal is to keep the UI pretty with big data. The full value is available via a tooltip or by clicking filter button to open the dialog.
Before:

After:

Checklist

Is this feature complete?

[x] Yes. Ready to ship.
[ ] No. Follow-up changes expected.

Are you including unit tests for the changes and scenario tests if relevant?

[ ] Yes
[x] No

Did you add public API?

[ ] Yes

If yes, did you have an API Review for it?

[ ] Yes
[ ] No

Did you add <remarks /> and <code /> elements on your triple slash comments?

[ ] Yes
[ ] No

[x] No

Does the change make any security assumptions or guarantees?

[ ] Yes

If yes, have you done a threat model and had a security review?

[ ] Yes
[ ] No

[x] No

Does the change require an update in our Aspire docs?

[ ] Yes

Link to aspire-docs issue:

[x] No

Microsoft Reviewers: Open in CodeFlow

Why is there space here?

How did you pick the width of 350px?
An issue in the original screenshot is that the label and textbox don't break together:

Even with a width of 350px, is it possible that the line breaks as in the first screenshot? Would be good to keep these two together.

Why is there space here?

The content is right aligned. It's still right aligned when wrapped to a new line.

How did you pick the width of 350px?

I picked it to balance showing most or all filter content most of the time, and showing too much and breaking the UI.

An issue in the original screenshot is that the label and textbox don't break together:

Even with a width of 350px, is it possible that the line breaks as in the first screenshot? Would be good to keep these two together.

Wrapping splits, them apart if the width is too large or the browser window is too small. Limiting the filter width like the PR does is the best way I know to keep them together.


TS2395: Individual declarations in merged declaration 'TypedUseSelectorHook' must be all exported or all local.

What version of React, ReactDOM/React Native, Redux, and React Redux are you using?

React: 17.0.2
ReactDOM/React Native: 17.0.2
Redux:
React Redux:7.1.24

What is the current behavior?
When I use the react-redux with the typescript, I want to  generate a approach with the TypedUseSelectorHook  from react-redux, but I got the error: TS2395: Individual declarations in merged declaration 'TypedUseSelectorHook' must be all exported or all local.
What is the expected behavior?
I can't continue with this error
Which browser and OS are affected by this issue?
MacOS bigsur11.6.2 and Chrome 100.0.4896.127(arm 64)
Did this work in previous versions of React Redux?

[ ] Yes

Oh ,it's my fault ,I don't use the TypedUseSelectorHook , it's woks when I execute it,


feat: Zeromorph changes for full Goblin

This PR adds polynomial "concatenation" functionality into ZeroMorph.
The idea behind concatenation is the following: given several polynomials (for example, $X_1$, $X_2$, $X_3$, $X_4$, $Y_1$, $Y_2$, $Y_3$, $Y_4$)  of length n, we want to show that the set of values in $X$ polynomials is identical to the values in $Y$.The way we can do it is with a grand product argument, however sumcheck complexity of the grand product argument is quadratic in the number of polynomials that are used in the GP (we have to extend the univariate to the degree d and then we need to multiply those (d+1) elements d times). However, if we were to perform the same grand product instead on polynomials $X= (X_1|X_2|X_3|X_4)$ and $Y=(Y_1|Y_2|Y_3|Y_4)$, the length of the sumcheck would increase 4 times, but the degree d would decrease proportionately.
So let's say we have an original circuit of length n, where all non-permutation relations are satisfied (including on $X_i$ and $Y_i$ polynomials). However, for the grand product argument we extend the polynomials to length $k\cdot n$ , where $k$ is a power of 2. Then we use the property of Zeromorph that it uses univariate commitments for commiting to multilinear polynomials. Because of this property, the final univariate opening of $X$ at challenge $x$ is equivalent to opening $X_1+x^n\cdot X_2+x^{2n}\cdot X_3+x^{3n}\cdot X_4$. So what we do in Zeromorph is substitute the opening of a concatenated polynomial by opening of a polynomial derived from a combination of $X_i$ polynomials multiplied by powers of $x$. This allows us to have fewer commitments and avoid shifts to prove the composition of concatenated polynomials
Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge.

[ ] If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag.
[ ] I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code.
[ ] Every change is related to the PR description.
[ ] I have linked this pull request to relevant issues (if any exist).

Benchmark results
No metrics with a significant change found.

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit 15a522ba and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,444
179,588
716,132

l1_rollup_calldata_gas
222,960
868,220
3,449,276

l1_rollup_execution_gas
842,047
3,595,328
22,204,645

l2_block_processing_time_in_ms
2,032 (+2%)
7,567
29,904 (-1%)

note_successful_decrypting_time_in_ms
294 (+1%)
869
3,171 (-3%)

note_trial_decrypting_time_in_ms
96.0 (+3%)
76.3 (+1%)
135

l2_block_building_time_in_ms
20,600 (-1%)
81,780
326,454

l2_block_rollup_simulation_time_in_ms
11,961 (-1%)
47,437
188,401

l2_block_public_tx_process_time_in_ms
8,593 (+1%)
34,210
137,571

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
21,871 (-1%)
42,453 (-1%)

note_history_successful_decrypting_time_in_ms
2,023 (-2%)
3,963 (-3%)

note_history_trial_decrypting_time_in_ms
121
145 (+1%)

node_database_size_in_bytes
1,630,865
1,101,119

pxe_database_size_in_bytes
29,748
59,307

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
763 (-1%)
61,697
18,905

private-kernel-ordering
125 (-1%)
24,297
8,153

base-rollup
1,765 (-1%)
656,428
873

root-rollup
173 (+2%)
4,072
1,097

private-kernel-inner
788 (-1%)
81,568
18,905

public-kernel-private-input
568
41,519
18,905

public-kernel-non-first-iteration
406
41,561
18,905

merge-rollup
15.2
2,592
873

Miscellaneous
Transaction sizes based on how many contracts are deployed in the tx.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
8,787
27,547

Handed off to @ledwards2225, became https://github.com/AztecProtocol/aztec-packages/pull/3343


Provide multiple authentication servers through a drop down menu (or even better use ldap)

I think LDAP is currently used. So close it maybe?


Moving landmarks to change facial expression

Hey there!
I'm working on a digital art project for school and I would like to be able to change the facial expression of the person looking at the camera.
Right now I succesfully managed to map the texture of my face on the 3d mesh generated by mediapipe: I was wondering if anyone know how I can move some of the landmarks of the mesh (in order, for example to distort the mapped texture in a smile).
I'll provide my code down below.
Any help will be much appreciated! Thank you!
Project.zip

Hi @Caroljpeg,
Could you please elaborate your query with complete details. thank you


Avoid setup.py when using cmd_classes

This is wip and requires an experimental branch of versioningit but seems to be working ok. Not to be merged before that has been approved upstream

After the latest changes to versioningit this needs a rething


Modifier.placeholder sometimes prevent Coil from loading image

Describe the bug
When I use Coil image to load multiple images, with Modifier.placeholder applied to display the loading status, some of them fail to complete the loading.
It is strange that I need so many circumstances to reproduce this: if I use any other view in the if (url == null) block, the error will not happen. A scrollable container and Modifier.alpha(0.9f) are also necessary.
In my example I use the same image, but the error persists when different urls are used.
I've debugged it and it looks like it happens because of this code block - since Coil can't start drawing until Painter.onDraw is called, which won't happen(or may not happen?) if you don't call drawContent. I tried changing condition contentAlpha in 0.01f..0.99f to contentAlpha < 0.99f, and it solves the problem.
To Reproduce
@Composable
fun TestView() {
    var url by remember { mutableStateOf<String?>(null) }
    LaunchedEffect(Unit) {
        delay(1000)
        url = "https://download.samplelib.com/png/sample-boat-400x300.png"
    }

    Row(
        modifier = Modifier
            .horizontalScroll(rememberScrollState())
    ) {
        if (url == null) {
            TestCell(null)
        } else {
            TestCell(url)
        }
    }
}

@Composable
private fun TestCell(url: String?) {
    Row {
        repeat(3) {
            val modifier = Modifier
                .alpha(0.9f)
                .size(100.dp)
                .background(Color.Gray)
            if (url != null) {
                AsyncImage(url, contentDescription = null, modifier = modifier)
            } else {
                Box(modifier)
            }
        }
    }
}

@Composable
private fun AsyncImage(
    data: Any?,
    modifier: Modifier = Modifier,
    contentDescription: String?,
    alignment: Alignment = Alignment.Center,
    contentScale: ContentScale = ContentScale.Fit,
) {
    val painter = rememberAsyncImagePainter(
        model = ImageRequest.Builder(LocalContext.current)
            .data(data)
            .crossfade(true)
            .build(),
        contentScale = contentScale,
    )
    val shimmer by remember(painter) {
        derivedStateOf {
            painter.state is AsyncImagePainter.State.Loading
        }
    }
    Image(
        painter = painter,
        contentDescription = contentDescription,
        contentScale = contentScale,
        alignment = alignment,
        modifier = modifier
            .placeholder(
                visible = shimmer,
                color = Color.Gray,
            )
    )
}

Expected behavior
I expect all three image views to be displayed when loading finishes. The bug also reproduces when app restarts and coil is loading from disk cache, so it's not network error.
Screenshots?
With my sample code first image is always in loading state:

Environment:

Android OS version: 13
Device: Google Pixel 5
Accompanist version: 0.30.0, 0.31.0-alpha

Doesn't coil have its own placeholders?


For implementation with TLB, if a virtual address hit both 2M-pte and 4K-pte, shoud page fault arise?

For implementation with TLB, it is possible that a virtual address hit both 2M-pte and 4K-pte and the translation result may be different. Should page fault arise, or use 2M-pte, or use 4K-pte?

The Priv spec has this non-normative note that answers your question:
It is permitted for multiple address-translation cache entries to co-exist for the same address.
This represents the fact that in a conventional TLB hierarchy, it is possible for multiple entries
to match a single address if, for example, a page is upgraded to a superpage without first clearing
the original non-leaf PTE’s valid bit and executing an SFENCE.VMA with rs1=x0, or if multiple
TLBs exist in parallel at a given level of the hierarchy. In this case, just as if an SFENCE.VMA
is not executed between a write to the memory-management tables and subsequent implicit read
of the same address: it is unpredictable whether the old non-leaf PTE or the new leaf PTE is
used, but the behavior is otherwise well defined.


v2ray: 4.34.0 -> 4.35.1

Motivation for this change
Bump version.
Also handle SRI hash produced by nix unstable in update script.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 115437 1

1 package built:

v2ray


feat(toggle): Adding BEM class naming

Business as usual. Adding BEM classes to the toggle widget (using
refinementList internally)

LGTM but I'm not super fan of PR with changes that are not related to the subject (here changes in tests, the part with the regex)

The test was really too tied to the code, and the usage message wasn't even correct. I felt like opening a PR for that was too nitpicky, but why not.

The test was really too tied to the code

But now the test is less specific, I mean the test could pass while the usage would not be up to date or completely broken.
Yes it's tied to the implementation but that's the goal no?

But now the test is less specific, I mean the test could pass while the usage would not be up to date or completely broken.

That was actually the case :). The usage message was out of sync with the jsdoc that itself was out of sync with the code. Still, we had a green test.
With the regexp the test is less specific (we only test that we fire a usage warning in case of bad usage, without checking the usage message), but at least this will not give us a false sense of security.
I don't think testing for a full string equality here will help us, this is just a copy-paste magnet and in the end the correctness of the usage message is not tested, we just test that this is the same string in the code and the tests.

You are right @pixelastic let's keep things simple (and sorry I like to rant too much it seems ;P)

No problem @bobylito, this was an interesting concern


E2E - Tests seem flaky because retry isn't counted

E2E has become flaky recently. While the straightforward cause should be migration from CRACO to Webpack, if you look at the test results it appears that test retries are not counted.
The following result seems to show that 3 out of 4 runs passed, so shouldn't this be regarded as the test eventually passed?
https://github.com/hawtio/hawtio-next/actions/runs/8795104020/job/24135649636
Error:  Failures:
Error:  Attributes and values.Example #1.2
[INFO]   Run 1: PASS
Error:    Run 2: The collection with text elements: [AllowUseOriginalMessage, false, ApplicationContextClassName, org.springframework.boot.loader.launch.LaunchedClassLoader, CamelDescription, null, CamelId, SampleCamel, CamelVersion, 4.4.0, ClassResolver, org.apache.camel.impl.engine.DefaultClassResolver, DeltaProcessingTime, 0, ExchangesCompleted, 12, ExchangesFailed, 0, ExchangesInflight, 0, ExchangesTotal, 12, ExternalRedeliveries, 0, FailuresHandled, 0, FirstExchangeCompletedExchangeId, 5D7E7B9B7D9EEEF-0000000000000000, FirstExchangeCompletedTimestamp, 2024-04-23T05:08:05Z, FirstExchangeFailureExchangeId, null, FirstExchangeFailureTimestamp, null, GlobalOptions, null, HeadersMapFactoryClassName, org.apache.camel.impl.engine.DefaultHeadersMapFactory, IdleSince, 57954, LastExchangeCompletedExchangeId, 5D7E7B9B7D9EEEF-000000000000000B, LastExchangeCompletedTimestamp, 2024-04-23T05:09:00Z, LastExchangeCreatedTimestamp, 2024-04-23T05:09:00Z, LastExchangeFailureExchangeId, null, LastExchangeFailureTimestamp, null, LastProcessingTime, 0, Load01, , Load05, , Load15, , LogMask, false, ManagementName, SampleCamel, ManagementStatisticsLevel, Default, MaxProcessingTime, 10, MeanProcessingTime, 1, MessageHistory, true, MinProcessingTime, 0, PackageScanClassResolver, org.apache.camel.spring.boot.FatJarPackageScanClassResolver, Redeliveries, 0, ResetTimestamp, 2024-04-23T05:08:04Z, ShutdownNowOnTimeout, true, StartedRoutes, 0, StartTimestamp, 2024-04-23T05:08:04Z, State, Suspended, StatisticsEnabled, true, Throughput, 0.00, Timeout, 45, TimeUnit, SECONDS, TotalProcessingTime, 12, TotalRoutes, 2, Tracing, false, Uptime, 1m52s, UptimeMillis, 112962, UseBreadcrumb, false, UseDataType, false, UseMDCLogging, false]
should contain all of the following text elements: [State, Started]
but could not find these elements: [Started]
Collection: table tbody tr td
Screenshot: file:/hawtio-test-suite/tests/hawtio-test-suite/build/reports/tests/1713848999092.2.png
Page source: file:/hawtio-test-suite/tests/hawtio-test-suite/build/reports/tests/1713848999092.2.html
Timeout: 20 s.
[INFO]   Run 3: PASS
[INFO]   Run 4: PASS

@mmuzikar Could you take a look at this please?

Should be fixed by https://github.com/hawtio/hawtio/pull/3410, I did some experiments, the different passes were not configured properly and thus not counted.


Add disable effect on buttons.

https://app.zeplin.io/project/62b9dba49dd2b211410e608e/screen/635c072bf964ca340b364a15
https://user-images.githubusercontent.com/5349154/217023556-d1fd1e04-8eee-4074-bb62-ad803ef86d52.png

Bing initially did the work in #1052, but later another feature, #1048, was merged first and had the necessary changes. Closing this issue as a duplicate.

Duplicate of #1048.


Add pudl0117 to pudl_collections.json

Coverage remained the same at 100.0% when pulling 3e0381bee3851f8c706ef2eef42d41940f668d51 on pudl0117 into 023f2c51f89af3fec08e1d7ec0c15a053da4370a on master.

Coverage remained the same at 100.0% when pulling 7eee76009d5d08b37538e706a3b212ae05442f56 on pudl0117 into 023f2c51f89af3fec08e1d7ec0c15a053da4370a on master.


Configure user id for openldap properly

What do you think? An alternative would be that we check for isExternal() for external name or external id instead of external id

What do you think? An alternative would be that we check for isExternal() for external name or external id instead of external id

Yes may be easier and less migration pain if we check both.

will merge it anyway. better setup.


Updating to WinUI 2.6.1

Description

Updates the XCG to use WinUI 2.6.1.
Motivation and Context

Fixes #738
How Has This Been Tested?

Tested locally on x86 and x64
Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

@anawishnoff could you please add a release to the GitHub releases page?

@Poopooracoocoo I haven't done that in the past, it looks like releases were automated. So I'll need to look into how it's done/what we've done in the past - stay tuned.