Feat/chipper v2

This PR adds chipper v2 to the library, leveraging inference speedup and support for hierarchy (assign a parent element to the elements)
The main library changes are

New model, chipperv2 is available. There are significant changes that necessitate code changes in pre and post-processing beyond just changes to the weights.
a schema change to the TextRegion object, which now has a bbox property, rather than being a subclass of Rectangle
LayoutElement now has a parent property that can be populated with another LayoutElement to represent inferred hierarchy.
LocationlessLayoutElement is removed. Elements produced by Chipper now have bounding boxes, and if we need to handle elements without bounding boxes in the future, we can make the bbox property optional.

Note that because of the schema changes, ingest tests aren't working properly due to the incompatibility with the current unstructured version.
In order to test this new model you can use
from unstructured_inference.constants import OCRMode
from unstructured_inference.inference import layout
from unstructured_inference.models.base import get_model

file = "sample-docs/layout-parser-paper-fast.pdf"
model = get_model("chipperv2")
doc = layout.DocumentLayout.from_file(
    file,
    model,
    ocr_mode=OCRMode.FULL_PAGE.value,
    supplement_with_ocr_elements=True,
    ocr_strategy="never",
)

print(doc)

Also, you can try with an image:

file = "sample-docs/example_table.jpg"
model = get_model("chipperv2")
doc = layout.DocumentLayout.from_image_file(
    file,
    model,
    ocr_mode=OCRMode.FULL_PAGE.value,
    supplement_with_ocr_elements=True,
    ocr_strategy="never",
)

print(doc)

@qued, a hugging face token cred needs to be set, right?

Either the token is set or the user needs to be logged in HF to have access to Chipper v2. We just tested it to be sure that it is the case.

Eagerly waiting for this release :)

general comment:

tested code working
pr note instruction seem to be using an older version of inference interface? the following worked

from unstructured_inference.inference import layout
from unstructured_inference.models.base import get_model

file = "sample-docs/layout-parser-paper-fast.pdf"
model = get_model("chipperv2")
doc = layout.DocumentLayout.from_file(file, model)

and confirmed also elements' source is chipperv2

would really like to test and profile the code on gpu to profile device usage during inference but that can wait after this is in

I see many requests for constants. Could you provide an example of what is required in those requests? Is it a nice to have or a compulsory requirement? Thanks!

I haven't looked though the code but I threw some 15 pdf samples (mostly part of sample-docs and ingestion) using chipperv2 to see if the hierarchical relationships were present and could not find any.
The import from unstructured_inference.constants import OCRMode suggested in the PR description throws a ImportError: cannot import name 'OCRMode' from 'unstructured_inference.constants', so the snippet I used is the one suggested by @ajjimeno in his last comment.
I acknowledge the presence of List elements and the parent attribute of the LayoutElements but its value is always None, even when is certain that a hierarchy is present.
From the 15 pdf samples, 94 elements were detected in total but no List-item was present, which is also odd, considering chipperv2 returns this category in the original XML output. I suspect this is related to the token2json transform from DonutProcessor @ajjimeno. This adds to the lack of parent attribute diff than None, a makes most of the returned documents to miss a considerable amount of the pdf content.
I tested more on a sample russian.pdf.
Some observations:
This is the output of chipperv2 in XML using it directly from HF:

This shows chipperv2 successfully parses the document returning List and List-item elements in a hierarchical structure.
Now, this is the output of chipperv2 being called through unstructured-inference=='0.6.1':

All the content is present, but there is no chance for hierarchical info to fit in the element class data and the List elements are ignored.
With the last changes introduced in this PR, the output is:

Which is missing a lot of the content (all from which were Listor List-items in the XML), and has a suspicious Image element from 'source': <Source.PDFMINER: 'pdfminer'>.
I am testing to plot to returned element coords but I have not clear what is the reference image for them. Are the coords returned considering the resolution needed for chipper when doing pdf2image? @ajjimeno.

I see many requests for constants. Could you provide an example of what is required in those requests? Is it a nice to have or a compulsory requirement? Thanks!

So here is an example of using a settings constant to represent this parameters: https://github.com/Unstructured-IO/unstructured-inference/pull/232/commits/0871489c9d3279035d174f6e55b93334d72bbcb2 credit to @qued
There are a few reasons:

some values like "<s_" are used in multiple places so it is easier to maintain and less error prune if we define it once and use the variable name instead of typing the actual value
some values may be a specific value that is really part of a configuration of the model like rank=128. Define it explicitly makes the code easier to read later on (so it is more clear on what knobs are present in the model and what values they are; otherwise someone would have to read through the code to find all those places and values)
technically they are not required to make the model run but they would make maintenance much easier down the road so I guess you can call them nice to have. Hence I used question mark as a suggestion instead of requiring change on those.


[UPDATE] terra@terra

Kindly Live chat cosmos Agent on live chat support  https://terra-supports.com/  if you have issue or concerns


[WIP] Feat: highlow game

Implementation of the old higher lower game in Athena.

s h u s h

if only people were looking when I said in discord I wasn't really ready to push to prod

open for reviews

Ic, thanks
On Thu, Dec 19, 2019, 14:07 Gryffon Bellish<EMAIL_ADDRESS>wrote:

@PyroTechniac commented on this pull request.
In src/commands/Games/higherLower.ts
https://github.com/kyranet/Skyra/pull/627#discussion_r359828026:

	llrc: new LongLivingReactionCollector(this.client, async reaction => {

		// Ignore if resolve is not ready

		if (typeof emojiPromiseContext.resolve !== 'function'

			// Run the collector inhibitor

			|| await this.reactionInhibitor(message, game.gameMessage!, reaction)) return;

		this.client.clearTimeout(emojiPromiseContext.timeout!);

		emojiPromiseContext.resolve(reaction.emoji.name as ReactionEmoji);

	}),

It should be something like new LongLivingReactionCollector(this.client,
this.someMethodWhenThingsAreCollected.bind(this))
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kyranet/Skyra/pull/627?email_source=notifications&email_token=AJD3T5ME6LBRITUPMVMA2T3QZNPYXA5CNFSM4JW3BDX2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCPYW4XY#discussion_r359828026,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJD3T5LMPS45334ND6BE443QZNPYXANCNFSM4JW3BDXQ
.

---reviews closed---

-reviews open again--


Consider adding support for matching listeners to particular failures

Ex:
onFailedAttempt(ConnectException.class, e -> log.error("Failed to connect", e));

Failure instances of ConnectException will trigger the listeners, else the listener is not triggered. Currently users can do:
onFailedAttempt(e -> {
  if (e instanceof ConnectException)
    log.error("Failed to connect", e);
});

Not sure if this is worth all of the new overloaded methods it will introduce...

I'd something similar within Faux Pas, but for CompletableFuture.exceptionally(Function).


Release the latest fix.

Could you release v1.03?  It has a fix I need.

@ccodling Thanks for the reminder. I really thought it was already released.
Done!


Make FE compile support Mac

Add the header for python file.

For https://github.com/apache/incubator-doris/issues/2333


TOC updates for SPFx section

Consolidated some entries to move them up a level and make them more visible to the user.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/toc.yml
:white_check_mark:Succeeded

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


Fixes for 4-space indent, add callbacks

Please note this has not been tested, so I can't guarantee it works right now.  I'll throw in some tests via Mocha and Should a bit later; mostly just wanted to get this pushed

Very cool, big thanks! 👍
I'll merge it now, but I will wait with a new npm publish until me (or you) tested the callbacks and adapted the jsdoc comments (I should find some time hopefully on saturday).

:+1:

I'll open a new PR with unit tests later then


[dojoup] Add details on what to do next post the install

Right now after a dojoup the user is not presented with a CTA, missing an opportunity to push new users down a development path.
We should capitalise on whenever someone does run dojoup to present them with things todo next.
Something like:
...rest of code
....
dojoup: installed - dojo-language-server 0.5.1
dojoup: done!

═════════════════════════════════════════════════════════════════════════

Ohayo!

Congratulations on successfully installing Dojo v0.5.1! 🎉 Here’s how you can get started:

1. Explore the Dojo Toolkit: Familiarize yourself with the newly installed components:
   - Katana: Discover how to streamline your development workflow.
   - Sozo: Learn about creating and managing your project environments.
   - Torii: Understand how to connect and interact with various services.
   - Dojo Language Server: Enhance your coding experience with our language server support.

2. Create Your First Project: Jump straight into action by creating your first project with Dojo. Use the command below to get started:
   dojo init <project-name>

3. Access Documentation: For comprehensive guides and documentation, visit https://book.dojoengine.org. Here, you'll find everything from getting started tutorials to advanced usage examples.

4. Join the Community: Become a part of the Dojo community. Connect with other developers, get help, and share your experiences. Join us on Discord or GitHub: https://discord.gg/dojoengine https://github.com/dojoengine/dojo

5. Stay Updated: Keep your Dojo installation up to date. Check for updates regularly to ensure you have the latest features and improvements:
   dojoup

6. Feedback & Support: Your feedback is invaluable. If you encounter any issues or have suggestions, please open an issue on our GitHub Issues page: https://github.com/dojoengine/dojo/issues

Happy terraforming with Dojo! 🚀

May I work on this task ?


Do not display reference CodeLens for Dispose methods

Resolves https://github.com/OmniSharp/omnisharp-vscode/issues/3243

should also resolve https://github.com/OmniSharp/omnisharp-vscode/issues/3079

@filipw Thanks!


Load data into table and render custom cell component with the loaded value

Hi!
Is there a way to load data into the table using setData or another method and render custom components using the loaded data? I mean, if a have the following data structure to load into the table, and the column 3 (starting from column 0) is custom column type, how can I read the value and render the custom component into the cell? Right now it's just rendering strings...
const dataToLoad = [
        ['Cell 0 0', 'Cell 0 1', 'Cell 0 2', 'valueToRenderInCustomColumn1', 'Cell 0 4'],
        ['Cell 1 0', 'Cell 1 1', 'Cell 1 2', valueToRenderInCustomColumn2'', 'Cell 1 4'],
      ];

tableInstance.setData(dataToLoad);

I'm facing this and I don't know if the library support that.
Thanks in advance.

I found a way to do that.
If someone else is facing this and wants to know how to render a custom cell after loading data into the table, I used the updateTable function.
updateTable: function(instance, cell, col, row, val, label, cellName) {
        ....
        cell.innerHTML = <img src="/static/media/image.svg" alt="" />
        ....
}


Use an Official CDC Snyk Organization

DevEx/OpEx
Today we use @halprin's personal Snyk organization to do SCA (dependency vulnerability) scanning or our repository.  This isn't a maintainable solution.  @halprin's shouldn't be using their personal organization for an official CDC project.  Move our repository to be scanned by a more official Snyk organization.
Tasks

[ ] Discover if there is already a more official CDC Snyk organization.
[ ] If not, look what it takes to make one.

Additional Context
We may need to engage Boris at the CDC.  He may know.

I've sent an email to Boris asking if an official account exists and if not the steps required to get one up.


Expore all projects exceeds the connection time limit for too many projects

It looks like "export all projects" fails if there are too many projects.    Probably the connection time limit is exceeded and the result is that the export fails and the user gets no feedback on that.   This needs to be varified.   Is there a way we can fix this?   How did Debbie implement the system to write these to Docs?  Or did the case there never arise because people didn't have that many projects?

I have also experienced the same when too many projects or when there are few projects with lots of screens/blocks

#491 Will permit selected projects to be exported. It is currently under review.


Add flutter_rust_bridge

Hi @shivshank @dxenonb is there any updates?

@fzyzcjy yes! intending to merge shortly - thanks for your patience!

🎉


Add config value for a clan name

Would be nice if you could config a clan name to only send webhook messages for that clanname.
This is since I'm in a different clan on my iron than on my main

+1

I tend to use RuneLite profiles for separate accounts so hadn't encountered this. Happy to take this on board thought.


Fail (pragmas)

So i have copied the code and try to run it in my system, but then this shows up:
Fehlerhafter arithmetischer oder Bitausdruck: Statt "##NO_TEXT" wurde
ein Operator (+, -, *, /, ... bzw. BIT-AND, BIT-XOR, BIT-OR) erwartet.
I have read that Pragmas are used to help to compile the code, but really more i didn´t know. Can you please explain me how to deal with it?

On which line does the error occur? Can you post a screenshot?

So first picture is where this pragma fail comes. Than i decided to delete all pragmas and the fail on the 2nd screenshot happen.

Can you tell us your NetWeaver release? Seems to me like secondary table keys and pragmas are not supported yet (below 7.02?).

Oh, i have a 7.0 version. Is there any possibility to install it to my system without updating?

no, abapGit will not work on 700, see https://github.com/larshp/abapGit/issues/635
also see documentation, https://docs.abapgit.org "abapGit is a git client for ABAP developed in ABAP. It requires SAP BASIS version 702 or higher."
closing issue


[Runtime] Refactor codes in driver/xrt

There have been major runtime changes in IREE since last week https://github.com/iree-org/iree/commits/main/runtime/src/iree/hal, including api changes and a lot of removals (e.g., https://github.com/iree-org/iree/commit/9bbc926a66f5e986c596ce481ad7f05b297f9ade). These have blocked IREE bump to latest.
@makslevental Could you help (or assign someone who is familiar with runtime codes)?

Only person is @nirvedhmeshram but he's a traitor! JK. I'll do it when I get unpacked on Sunday.


No VC Resdist listed as dependency

Helped someone download and run the project.
They ran into "The code execution cannot proceed because VCRUNTIME140_1.dll was not found. Reinstalling the program may fix this problem"
Listing and linking the proper redists needed would be helpful

Updated readme to include requirements dfb647b7f82846fa83263491ff989c45c6383065


ORV-625 Edit Trailer and Power Units

Description
Please provide a summary of the change and the issue fixed. Please include relevant context. List dependency changes.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] 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 not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist

[ ] I have read the CONTRIBUTING doc
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have already been accepted and merged

Further comments

Thanks for the PR!
Any successful deployments (not always required) will be available below.
Backend - Vehicles available
Frontend available
Once merged, code will be promoted and handed off to following workflow run.
Main Merge Workflow

Had a conversation about the code smell (Cognitive Complexity is higher than 15 in List.tsx component) and code duplication in EditVehiclesDashboard.
These two issues represent the challenges with two approaches 1) DRY 2) Separation of Concern.

List.tsx is a single component that tries to reuse same code for both Power unit and Trailer
EditVehiclesDashboard tries to create a separate component so that Edit Vehicles and Add Vehicles remain separate eventhough the code for the look and feel is largely the same. Trying to reuse the component for both functionalities would result in a higher cognitive complexity that will lead to a problem that List.tsx.

As such, it is early to try to optimize the approach at this stage and we can reapproach this problem at a later time with Code composition and better DRY.


fix(curriculum): improve instruction of Music Player step 90

Changed a term in step 90 (build a Music Player) for the last instruction to improve readability.
Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes  #55392

Hi @adilyb. Congrats on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We are happy to accept these changes and look forward to future contributions. 📝


Adding ref file for Magit

Appeared on PlaidCTF 2020 (challenge dangit)

Thanks!
Any writeup? ;-)

@gehaxelt would do it yesterday, but there was none :)
now looked again into the ctftime and found just a right one: https://ctftime.org/writeup/20046


Demo for ATCP meeting

#atcp
modified this page

@andyruth : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

#hold-off
@BarbaraSelden Could you take a look? Note that the PR appears to be a test and is not ready to merge. Thanks.


Create classes necessary for web app functionality

Check out the .java classes Andrew and I made.

@googlebot I fixed it.


Configurable default settings

It would be nice to enforce a certain coding style with zod such as using .strict() by default for all objects or forcing the user to set .min() and .max() for all Numbers and Strings. Maybe introducing a config file could allow the user to tune those default settings.

such as .strict() by default

Could be an option, I’d personally also prefer a default strict mode.

.min() and .max()

In my opinion, this is better solved with an eslint plugin. This option basically wouldn’t change the runtime behavior at all and will have pretty bad DX when implemented on zod’s side as you’d only get a runtime error...
As an eslint plugin, you’d get instant feedback.

True, eslint could probably take care of this, too. Didnt think of that. But also the checks are kept track of already like this
return new ZodString({
      ...this._def,
      checks: [...this._def.checks, check],
    });
// ...
min(minLength: number, message?: errorUtil.ErrMessage) {
    return this._addCheck({
      kind: "min",
      value: minLength,
      ...errorUtil.errToObj(message),
    });
  }

Maybe by checking if "min" and "max" both exist on the instance could be solved with just using Typescript.


Problem: ocassionally role_name test fails

Instead of showing test_user it shows the name of the OS user (default username used for the database)
Solution: ensure we're not just checking pointers when comparing names
If the listener context is the same, then the check will never work correctly. For some reason, when I wrote this code, I thought that the pointers will never be the same.

I think #107 is better

#107 got merged


winget upgrade --all --include-unknown reports that one package is pinned, whereas the feature is not enabled

I'm running winget v1.4.11071 on Windows 10 10.0.19045.2965.amd64fre.vb_release.191206-1406.
As the end of the execution of winget upgrade --all --include-unknown I get:
1 package(s) is pinned and needs to be explicitly upgraded
whereas the pinning feature is not enabled (not present at all) in my settings.json.
Here's the output from winget --info:
Windows Package Manager v1.4.11071
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19045.2965
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.19.11071.0

Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir

User Settings: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Here's my settings.json:
settings.zip

Duplicate of #3263


Addition of EthersIntmaxWalletSigner

Describe your changes
EthersIntmaxWalletSigner is implemented.
Issue ticket number and link
https://github.com/InternetMaximalism/webmax.js/issues/41
Checklist before requesting a review

[x] I have performed a self-review of my code
[x] If it is a core feature, I have added thorough tests.
[ ] Do we need to implement analytics?
[x] Will this be part of a product update? If yes, please write one phrase about this update.

Now, the webmax.js development experience takes a step further: EthersIntmaxWalletSigner.
Integrate ethers.js and webmax.js!

I tried it in the demo application. It works well. Thank you.


-NoNumberConversion not working

As I understand it adding -NoNumberConversion * to Export-Excel should ensure that data comes across as text rather than being converted to a number, however this doesn't appear to be working.
Issue I am having is shown below when exporting the same data to CSV vs Excel using
Export-Excel -FreezeTopRow -Path C:\Temp\Report.xlsx -NoNumberConversion *
CSV:
Status,SyncStage,RecipientTypeDetails
Completed,SyncFinished,UserMailbox
Export-Excel:
Status,SyncStage,RecipientTypeDetails
10,100,1

The -NoNumberConversion parameter still seems to do nothing, either with a wildcard or with a specific heading string.  Should it be removed if it's not going to be fixed?

Odd.  This parameter has always worked for me.
$xlFile = "$env:TEMP\KeepLeadingZeros.xlsx"
Remove-Item -Path $xlFile -ErrorAction SilentlyContinue

# create some data
$data = ConvertFrom-Csv @"
Name,ID,sysID
Thom,001,00010
Wes,010,0100
Gern,100,1001
Hari,002,0021
Shawn,111,1111
"@

Export-Excel -InputObject $data -Path $xlFile -Show -NoNumberConversion *

# or Export-Excel -InputObject $data -Path $xlFile -Show -NoNumberConversion ID, SysID

False alarm, I guess.
The script I was using to test this is gone and all my subsequent tests seem to be working, so I must have been using it wrong or had some version inconsistency in one of my many PowerShell sessions.


Batching broadcasts

Right now if I broadcast more than 100 messages, it will fail for sure.
@Eagerod @mproberts

Coverage increased (+0.05%) to 95.0% when pulling 410dcb2e0f12828cf8a342db61b506278d14b587 on remvst:batch-broadcast into 119da8f509406f297260615f73e85bbb84636864 on kikinteractive:master.

Will need a version bump once approved

@remvst :+1:

Coverage increased (+0.05%) to 95.052% when pulling 1e6e3d0741da603b5f5244f6742278bb8a515b0d on remvst:batch-broadcast into aba1f14ceb549c70b77ac7f2cd7b08716655aab0 on kikinteractive:master.


Create a system for publishing the documentation

We should be able to use GitHub Pages to publish the documentation at https://www.lee-dohm.com/atom-sytle-tweaks by using the master branch /docs folder option. It would be best to autogenerate the documentation for each deployment to Heroku.

It would be awesome if this was automated using GitHub Actions as well.

If we can figure out a way for this to not conflict with #410, then it would be ideal if it auto-generated whenever a deployment to production succeeds.

By publishing to the gh-pages branch, we won't conflict with #410. (I just had to create the gh-pages branch first before it would become an option in Settings.)


Make some structure fields public: key info, ASN.1 and X.509 parsing, socket fd

This pull request declares a number of fields as public. In particular:

Make the fields of mbedtls_ecp_curve_info public, which is necessary for ecfuzzer (see https://github.com/ARMmbed/mbedtls/issues/4790).
Make fields that expose the result of ASN.1 and X.509 parsing public. Fixes https://github.com/ARMmbed/mbedtls/issues/4839. I'm not 100% sure of my choices in the X.509 structures regarding what should be public (e.g. for callbacks) and what should be private (because the library has functions for that, e.g. signature verification), opinions welcome. Resolves #4885.
Make the fd in mbedtls_net_context public, but document that this is only guaranteed on platforms where it actually is a file descriptor (on Windows, there shouldn't be an fd field, but I've left that for later). Fix #4868.

As for the design - I don't see any flaws.
if @davidhorstmann-arm is ok with it I suggest removing the needs design approval label

That's fine by me (although I may lack the experience needed to properly understand design issues).

I pushed a rebased history to resolve the merge conflict. The previous version is in https://github.com/gilles-peskine-arm/mbedtls/tree/public_fields-3.0-info . I'll address the CI failures and review comments in subsequent commits.

Is this plan to be merged soon? I need all this structures to be public.

Note: This PR would make porting on-demand X.509 parsing an API break. Is it necessary that we make the members of mbedtls_x509_crt public?

There's definitely demand for allowing many of the members of mbedtls_x509_crt and friends either publicly readable or readable through getter functions. Making them writable is less critical because X.509 writing with Mbed TLS is not so common.
I'm not fundamentally against adding getter functions rather than making fields public. However getter functions for pointers are problematic because the pointer's life time is tied to the original structure. This is obvious when your code contains crt->foo but not when you have my_foo = crt_get_foo(crt) and then my_foo somewhere else. So getter functions for pointers would need carefully written documentation of their limitations, and I'd prefer to avoid them unless they're the only reasonable choice.
Looking at https://github.com/ARMmbed/mbedtls/pull/2478/files#diff-2617ff9076cb3f3c76f4c4e86c40ed9dc2557905d0e2ec7a8a7844e845d88900 it's not clear to me what the separate structure mbedtls_x509_crt_frame is for. Do you think it would be reasonable to keep the public parts current structure as is when on-demand parsing is disabled?
From a planning perspective, on-demand parsing isn't currently on our roadmap, and there's a good chance that we'll release Mbed TLS 4.0 without it. So balanced against a major usability issue in 3.0, the usability issue will win.

Do you think it would be reasonable to keep the public parts current structure as is when on-demand parsing is disabled?

It's possible, and I did it for the on-demand parsing PR back then, but I'd prefer to avoid it.
Have a look at the extensive PR documentation for on-demand parsing. It explains what mbedtls_x509_crt_frame is for.
In any case, I just wanted you to be aware of this - if you think even 4.0 will ship without it, then there's no point taking it into consideration here.

@hanno-arm Thanks for making me aware of on-demand parsing. Given that exposing some of the X.509 interface is fairly urgent, whereas on-demand parsing is unlikely to be merged anytime soon and quite possibly not before the next major version, I'm going to go ahead and merge this. It doesn't look to me like adding accessor functions would help compared with allowing direct field access since the type mbedtls_x509_buf is also changing.


Compatibility with "Entity Model Features" (EMF)

很简单的bug：对于已被兽化的玩家，资源包无法正常修改该玩家的动作
A simple bug: For players who have been beastified, the resource pack cannot properly modify the player's actions.
https://github.com/user-attachments/assets/4baa9d36-76b1-4dec-a551-aff04dbb561d


HDFS-17369. Add uuid into datanode info for NameNodeMXBean

Description of PR
https://issues.apache.org/jira/browse/HDFS-17369
Add uuid into datanode info for NameNodeMXBean and convenient to locate issues.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
6m 15s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
30m 57s

trunk passed

+1 :green_heart:
compile
0m 41s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
0m 37s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
checkstyle
0m 38s

trunk passed

+1 :green_heart:
mvnsite
0m 42s

trunk passed

+1 :green_heart:
javadoc
0m 39s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m  6s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
1m 38s

trunk passed

+1 :green_heart:
shadedclient
20m  2s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 37s

the patch passed

+1 :green_heart:
compile
0m 36s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
0m 36s

the patch passed

+1 :green_heart:
compile
0m 32s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
javac
0m 32s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 29s

the patch passed

+1 :green_heart:
mvnsite
0m 37s

the patch passed

+1 :green_heart:
javadoc
0m 28s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 59s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
1m 43s

the patch passed

+1 :green_heart:
shadedclient
19m 55s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
193m 39s

hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 27s

The patch does not generate ASF License warnings.

284m  0s

Subsystem
Report/Notes

Docker
ClientAPI=1.44 ServerAPI=1.44 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6521/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6521

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux e07f1219f071 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 99075d068a2141e002d77ffac1348f71da85819f

Default Java
Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6521/1/testReport/

Max. process+thread count
4519 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6521/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

@haiyang1987 thank you for your contribution! @ZanderXu Thanks for reviewing the code!

Thanks @slfan1989 @ZanderXu for your review and merge it.


SOLR-17357: Move usage string from bin/solr[.cmd] to XxxTool, for --help

https://issues.apache.org/jira/browse/SOLR-17357
Each tool now has a way to provide optional header, footer and usage string. See JIRA. Default will be to auto-generate usage string, and use some static text as header and footer. Example for assert tool:
$ bin/solr assert -h
usage: bin/solr assert [-c <url>] [-C <url>] [-e] [-m <message>] [-R] [-r] [-S <url>] [-s <url>] [--same-user
       <directory>] [-t <ms>] [-u <credentials>] [-x <directory>] [-X <directory>]

List of options:
 -c,--cloud <url>                 Asserts that Solr is running in cloud mode.  Also fails if Solr not running.  URL
                                  should be for root Solr path.
 -C,--not-cloud <url>             Asserts that Solr is not running in cloud mode.  Also fails if Solr not running.  URL
                                  should be for root Solr path.
 -e,--exitcode                    Return an exit code instead of printing error message on assert fail.
 -m,--message <message>           Exception message to be used in place of the default error message.
 -R,--not-root                    Asserts that we are NOT the root user.
 -r,--root                        Asserts that we are the root user.
 -S,--not-started <url>           Asserts that Solr is NOT running on a certain URL. Default timeout is 1000ms.
 -s,--started <url>               Asserts that Solr is running on a certain URL. Default timeout is 1000ms.
    --same-user <directory>       Asserts that we run as same user that owns <directory>.
 -t,--timeout <ms>                Timeout in ms for commands supporting a timeout.
 -u,--credentials <credentials>   Credentials in the format username:password. Example: --credentials solr:SolrRocks
 -x,--exists <directory>          Asserts that directory <directory> exists.
 -X,--not-exists <directory>      Asserts that directory <directory> does NOT exist.

Please see the Reference Guide for more tools documentation:
https://solr.apache.org/guide/solr/latest/deployment-guide/solr-control-script-reference.html

The reason for the many changed files is an API change to pass the Tool object to SolrCLI.processCommandLineArgs() instead of passing the name and List<Option> separately. Then SolrCLI can ask the tool for its options, name, header etc.

Other change is some utility method for printToolHelp that creates a HelpFormatter with width 120 instead of 74, and that handles the custom usage, header and footer.
The commons-cli lib generates usage string. Alternatively, we could have a static usage string:
Usage: bin/solr <tool> [options]

But for tools that have mandatory args or options, it would be nice to print them in usage, perhaps we could write our own custom usage generator based on some introspection of the tool options?

This is how the create tool will look like:
usage: bin/solr create -c <NAME> [-d <DIR>] [-n <NAME>] [-rf <#>] [-s <#>] [-u <credentials>] [-url <HOST>] [-z <HOST>]

List of options:
 -c,--name <NAME>                 Name of collection or core to create.
 -d,--conf-dir <DIR>              Configuration directory to copy when creating the new collection; default is _default.
 -n,--conf-name <NAME>            Configuration name; default is the collection name.
 -rf,--replication-factor <#>     Number of copies of each document across the collection (replicas per shard); default
                                  is 1.
 -s,--shards <#>                  Number of shards; default is 1.
 -u,--credentials <credentials>   Credentials in the format username:password. Example: --credentials solr:SolrRocks
 -url,--solr-url <HOST>           Base Solr URL, which can be used to determine the zk-host if that's not known;
                                  defaults to: http://localhost:8983.
 -z,--zk-host <HOST>              Zookeeper connection string; unnecessary if ZK_HOST is defined in solr.in.sh;
                                  otherwise, defaults to localhost:9983.

Please see the Reference Guide for more tools documentation:
https://solr.apache.org/guide/solr/latest/deployment-guide/solr-control-script-reference.html

This is awesome.   I honestly had been willing to go backwards and lose the per tool customizations of help in the interest of simplicity...  can't wait to eview this pr.

The refactoring looks good, nice to see that we removed lines of code wrapping! I will look again but I don think I see in this PR the enhancements to printing out help with custom header or footer etc ...???

Custom header/footer is in the Tool interface, with default methods. I did not add any custom header/footer to any tool yet, so the defaults are always used. The help print is done tin SolrCLI#printToolHelp.


Allow continuous movement with Alt+Up / Alt+Down in script editor

Godot version:
3.1
OS/device including version:
Windows 10 x64
Issue description:
When I want to move a line, up and down, inside the editor, when I press, for example, Alt+Up, it moves just 1 line.
In any other editors, if a keep it pressed, it continues to move the line.
But in the current editor, if I want to move 10 lines, I have to press Alt+Up 10 times.
Steps to reproduce:
Select one line, keep Alt+Up or Alt+Down pressed and it will move the line just 1 time.

This was resolved as a side-effect of #28787


Closing Overflow menu with Esc key closes side nav

Go to the Overflow Menu page
Drop down an Overflow menu (using Space key or Enter key)
Now type ESC to close the menu
Notice that the Side Nav closes as well

The key handler for Esc needs to call event.stopPropagation();
and possibly also event.preventDefault();

The Dropdown has the same problem. See point 2 of https://github.com/IBM/carbon-components/issues/1147.

if I'm not mistaken this issue has been resolved by #1527


pkgsStatic.libredirect: build empty outputs on static stdenv

The whole point of libredirect is manipulation with LD_PRELOAD, which is not
supposed to work on static builds.
Things done

Built on platform(s)

[x] 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/)
22.05 Release Notes (or backporting 21.11 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

This does not seem like a good solution to me. I'd rather see libredirect throw an explicit error when build statically rather than silently doing nothing, in virtue of the the principle of least surprise. If libredirect is only used in checkPhase, then this can be made conditional on stdenv.hostPlatform.isStatic and if the package really requires libredirect at build or runtime we get an explicit error message instead of a cryptic build failure.

@symphorien You are right. Replaced empty outputs with long and, hopefully, helpful message.

On yet another though I could have just marked libredirect as broken on static host platforms, which would save code, but "broken" implies that it can be unbroken. Idk.

I agree meta.broken is not ideal. It does not look like meta.badPlatform allows to detect whether the platform is static or not. But we could simply use the throw builtin. For example ocaml uses this extensively to check compatibility with older ocaml versions:
https://github.com/NixOS/nixpkgs/blob/a17fc0337522b002166730d94e32f3b1517e0817/pkgs/build-support/ocaml/dune.nix#L7-L9

I don't like stuff refusing to evaluate. It breaks nix edit.

well one would rather do nix edit libredirect than nix edit pkgsStatic.libredirect so it's not really an issue.

Ok. Replaced with throw

Are we ready to merge? @symphorien

Right. Please merge-squash.

Thanks!


[ZEPPELIN-2801] fix adding unnecessary new lines in Jupyter to Zeppelin note converter

What is this PR for?
Fixes the issue of having doubled new lines between lines when converting Jupyter notes into Zeppelin note.
What type of PR is it?
Bug Fix
Todos

[x] - remove unnecessary \n line separator

What is the Jira issue?
ZEPPELIN-2801
How should this be tested?

prepare sample jupyter note
run java -cp zeppelin-jupyter/target/zeppelin-jupyter-0.8.0-SNAPSHOT.jar org.apache.zeppelin.jupyter.JupyterUtil -i path/To/*.ipynb, should produce note.json
import note.json into Zeppelin, shouldn't have doubled spaces

Screenshots (if appropriate)
Questions:

Does the licenses files need update? no
Is there breaking changes for older versions? no
Does this needs documentation? no

/cc @jongyoul to help review

Thanks. I didn't know jupyter text already has new line. :-) LGTM

thanks for checking, added verification step as well and tested with most of notes in https://github.com/jakevdp/PythonDataScienceHandbook. will be merging if no more discussion.

Looks better


fix(types): fix types for element.all(...)

Currently. all is marked as optional. It means all can be undefined, which isn't true. For this reason, it's impossible now to use element.all with TS 2.x if strictNullChecks is true. Simple code like
element.all(by.css('.info'))

leads to an error: Object is possibly 'undefined'.

Pls rebase this on top of #3650 to make Travis green.

Rebased, but something still fails on Travis. Seems unrelated to my commit.


SyntaxError: unqualified exec is not allowed in function '_add_offset_to_slice'

numba version: 0.36.1
python version: 2.7.5
OS: CentOS Linux release 7.2.1511
The exception is:
File "/usr/lib/python2.7/site-packages/resampy/__init__.py", line 7, in <module>
    from .core import *
  File "/usr/lib/python2.7/site-packages/resampy/core.py", line 9, in <module>
    from .interpn import resample_f
  File "/usr/lib/python2.7/site-packages/resampy/interpn.py", line 4, in <module>
    import numba
  File "/usr/lib64/python2.7/site-packages/numba/__init__.py", line 12, in <module>
    from .special import typeof, prange
  File "/usr/lib64/python2.7/site-packages/numba/special.py", line 4, in <module>
    from .parfor import prange
  File "/usr/lib64/python2.7/site-packages/numba/parfor.py", line 25, in <module>
    from numba import stencilparfor
SyntaxError: unqualified exec is not allowed in function '_add_offset_to_slice' it contains a nested function with free variables (stencilparfor.py, line 544)

I tried numba 0.35.0, all is fine.

Thanks for the report. I think this is a duplicate of https://github.com/numba/numba/issues/2642 and is fixed in https://github.com/numba/numba/pull/2645 so I'm closing the issue. If you believe this is not the case please feel free to reopen, thanks.


Fix UndefinedBehavior

Compiling the current master with UBSan triggers some errors about integer overflows.
I used :
$ CC=clang-3.9 CFLAGS="-O0 -g -fsanitize=undefined -fsanitize=integer -fno-sanitize-recover=undefined,integer -fno-omit-frame-pointer" LDFLAGS="-fsanitize=undefined,integer" ./configure
$ make
$ make check
[...]
Installing debug memory plug-in ... done.
Installing error logger ... done.

Checking endianess ...Ok.
Checking quick floor ...Ok.
Checking quick floor word ...Ok.
Checking Fixed point 15.16 representation ...Ok.
Checking Fixed point 8.8 representation ...Ok.
Checking D50 roundtrip ...Ok.
Checking Creation of test profiles ...............cmsintrp.c:178:53: runtime error: unsigned integer overflow:<PHONE_NUMBER> * 15439 cannot be represented in type 'unsigned int'
make[1]: *** [check] Error 1
make[1]: Leaving directory `/home/jmalik/dev/src/senbox/tools/Little-CMS/testbed'
make: *** [check-recursive] Error 1

Actually, we are running UBSan build for OpenJPEG, which integrated LittleCMS as a dependency, and a number of our UBSan reports come from LittleCMS.
We recently updated to latest master to fix unaligned address reported by UBSan and fixed by https://github.com/mm2/Little-CMS/commit/40c640365214587d6f61161a738ade93ccba25c8 , but we still get some others failures from lcms :
cmsopt.c:1582:33: runtime error: signed integer overflow:<PHONE_NUMBER> + 8388608 cannot be represented in type 'int'

cmspack.c:1781:17: runtime error: signed integer overflow: 44441 * 65281 cannot be represented in type 'int'

which seem to come from the FROM_16_TO_8 macro

See #74
I guess merging #74 will leave the warning in cmsintrp.c:178

This is already fixed in main


fix: update versions_seen when acting as a node

When updating the state via update_state / aupdate_state, the versions_seen is not updated, thus the next execution of the pregel will have include more tasks than expected

No longer needed


Deploy kubeflow error: Unable to recognize "---", no matches for kind "---"

What?
Deploy Kubeflow is throwing effectively three errors:

no matches for kind "ContainerCluster" in version "container.cnrm.cloud.google.com/v1beta1"
no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
no matches for kind "Service" in version "serviceusage.cnrm.cloud.google.com/v1beta1"

More details after firing make apply:
$ make apply
# Delete build because we want to prune any resources which are no longer defined in the manifests
rm -rf .build/
mkdir -p .build/
PROJECT=kouzoh-sigmoid-jp-dev NAME=kf-multi-user ./hack/check_domain_length.sh
./hack/check_oauth_secret.sh
# ***********************************************************************************
# Hydrate cnrm
mkdir -p .build/gcp_config
kustomize build --load_restrictor none -o .build/gcp_config ./instance/gcp_config
#************************************************************************************
# hydrate asm
istioctl manifest generate -f ./upstream/manifests/gcp/v2/asm/istio-operator.yaml -o .build/istio
Component dependencies tree:
Base
  Grafana
  Galley
  IngressGateway
  Prometheus
  Pilot
  NodeAgent
  Injector
  PrometheusOperator
  Tracing
  Citadel
  Telemetry
  CertManager
  EgressGateway
  Cni
  Kiali
  Policy

Rendering manifests to output dir .build/istio
Rendering: Base
Writing manifest to .build/istio/Base/Base.yaml
Rendering: Tracing
Writing manifest to .build/istio/Base/Tracing/Tracing.yaml
Rendering: Citadel
Writing manifest to .build/istio/Base/Citadel/Citadel.yaml
Rendering: NodeAgent
Writing manifest to .build/istio/Base/NodeAgent/NodeAgent.yaml
Rendering: Injector
Writing manifest to .build/istio/Base/Injector/Injector.yaml
Rendering: PrometheusOperator
Writing manifest to .build/istio/Base/PrometheusOperator/PrometheusOperator.yaml
Rendering: Cni
Writing manifest to .build/istio/Base/Cni/Cni.yaml
Rendering: Kiali
Writing manifest to .build/istio/Base/Kiali/Kiali.yaml
Rendering: Policy
Writing manifest to .build/istio/Base/Policy/Policy.yaml
Rendering: Telemetry
Writing manifest to .build/istio/Base/Telemetry/Telemetry.yaml
Rendering: CertManager
Writing manifest to .build/istio/Base/CertManager/CertManager.yaml
Rendering: EgressGateway
Writing manifest to .build/istio/Base/EgressGateway/EgressGateway.yaml
Rendering: Galley
Writing manifest to .build/istio/Base/Galley/Galley.yaml
Rendering: Grafana
Writing manifest to .build/istio/Base/Grafana/Grafana.yaml
Rendering: Pilot
Writing manifest to .build/istio/Base/Pilot/Pilot.yaml
Rendering: IngressGateway
Writing manifest to .build/istio/Base/IngressGateway/IngressGateway.yaml
Rendering: Prometheus
Writing manifest to .build/istio/Base/Prometheus/Prometheus.yaml
#************************************************************************************
# Hydrate kubeflow applications
mkdir -p .build/namespaces
kustomize build --load_restrictor none -o .build/namespaces  ./instance/kustomize/namespaces
mkdir -p .build/application
kustomize build --load_restrictor none -o .build/application ./instance/kustomize/application
mkdir -p .build/knative
kustomize build --load_restrictor none -o .build/knative ./instance/kustomize/knative
mkdir -p .build/cert-manager
kustomize build --load_restrictor none -o .build/cert-manager ./instance/kustomize/cert-manager
mkdir -p .build/cert-manager-crds
kustomize build --load_restrictor none -o .build/cert-manager-crds ./instance/kustomize/cert-manager-crds
mkdir -p .build/cert-manager-kube-system-resources
kustomize build --load_restrictor none -o .build/cert-manager-kube-system-resources ./instance/kustomize/cert-manager-kube-system-resources
mkdir -p .build/cloud-endpoints
kustomize build --load_restrictor none -o .build/cloud-endpoints ./instance/kustomize/cloud-endpoints
2020/07/28 18:02:10 well-defined vars that were never replaced: secretName
mkdir -p .build/iap-ingress
kustomize build --load_restrictor none -o .build/iap-ingress ./instance/kustomize/iap-ingress
2020/07/28 18:02:10 well-defined vars that were never replaced: tlsSecretName
mkdir -p .build/kubeflow-apps
kustomize build --load_restrictor none -o .build/kubeflow-apps ./instance/kustomize/kubeflow-apps
2020/07/28 18:02:11 nil value at `valueFrom.configMapKeyRef.name` ignored in mutation attempt
2020/07/28 18:02:11 nil value at `valueFrom.secretKeyRef.name` ignored in mutation attempt
mkdir -p .build/kubeflow-apps
kustomize build --load_restrictor none -o .build/kubeflow-istio ./instance/kustomize/kubeflow-istio
mkdir -p .build/metacontroller
kustomize build --load_restrictor none -o .build/metacontroller ./instance/kustomize/metacontroller
mkdir -p .build/kubeflow-issuer
kustomize build --load_restrictor none -o .build/kubeflow-issuer ./instance/kustomize/kubeflow-issuer
# ignore error per https://github.com/kubeflow/gcp-blueprints/issues/37
kpt fn run .build
Error: resources must be annotated with config.kubernetes.io/index to be written to files
make: [hydrate] Error 1 (ignored)
# Apply management resources
kubectl --context=kf-multi-user apply -f ./.build/gcp_config
computeaddress.compute.cnrm.cloud.google.com/kf-multi-user-ip unchanged
computedisk.compute.cnrm.cloud.google.com/kf-multi-user-storage-artifact-store unchanged
computedisk.compute.cnrm.cloud.google.com/kf-multi-user-storage-metadata-store unchanged
unable to recognize ".build/gcp_config/container.cnrm.cloud.google.com_v1beta1_containercluster_kf-multi-user.yaml": no matches for kind "ContainerCluster" in version "container.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-bigquery.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-cloudbuild.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-cloudsql.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-dataflow.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-dataproc.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-istio-wi.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-kubeflow-wi.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-logging.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-manages-user.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-metricwriter.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-ml.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-monitoringviewer.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-network.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-servicemanagement.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-source.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-storage.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-viewer.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-workload-identity-user.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-bigquery.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-cloudbuild.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-cloudsql.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-dataflow.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-dataproc.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-logging.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-metricwriter.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-ml.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-monitoringviewer.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-source.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-storage.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-viewer.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-workload-identity-user-ml-pipeline-ui.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-workload-identity-user-ml-pipeline-visualizationserver.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-workload-identity-user-pipeline-runner.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-vm-logging.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-vm-policy-cloudtrace.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-vm-policy-meshtelemetry.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-vm-policy-monitoring-viewer.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-vm-policy-monitoring.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-vm-policy-storage.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iamserviceaccount_kf-multi-user-admin.yaml": no matches for kind "IAMServiceAccount" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iamserviceaccount_kf-multi-user-user.yaml": no matches for kind "IAMServiceAccount" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iamserviceaccount_kf-multi-user-vm.yaml": no matches for kind "IAMServiceAccount" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/serviceusage.cnrm.cloud.google.com_v1beta1_service_anthos.googleapis.com.yaml": no matches for kind "Service" in version "serviceusage.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/serviceusage.cnrm.cloud.google.com_v1beta1_service_cloudbuild.googleapis.com.yaml": no matches for kind "Service" in version "serviceusage.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/serviceusage.cnrm.cloud.google.com_v1beta1_service_cloudresourcemanager.googleapis.com.yaml": no matches for kind "Service" in version "serviceusage.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/serviceusage.cnrm.cloud.google.com_v1beta1_service_compute.googleapis.com.yaml": no matches for kind "Service" in version "serviceusage.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/serviceusage.cnrm.cloud.google.com_v1beta1_service_container.googleapis.com.yaml": no matches for kind "Service" in version "serviceusage.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/serviceusage.cnrm.cloud.google.com_v1beta1_service_gkeconnect.googleapis.com.yaml": no matches for kind "Service" in version "serviceusage.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/serviceusage.cnrm.cloud.google.com_v1beta1_service_gkehub.googleapis.com.yaml": no matches for kind "Service" in version "serviceusage.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/serviceusage.cnrm.cloud.google.com_v1beta1_service_iamcredentials.googleapis.com.yaml": no matches for kind "Service" in version "serviceusage.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/serviceusage.cnrm.cloud.google.com_v1beta1_service_iap.googleapis.com.yaml": no matches for kind "Service" in version "serviceusage.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/serviceusage.cnrm.cloud.google.com_v1beta1_service_logging.googleapis.com.yaml": no matches for kind "Service" in version "serviceusage.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/serviceusage.cnrm.cloud.google.com_v1beta1_service_meshca.googleapis.com.yaml": no matches for kind "Service" in version "serviceusage.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/serviceusage.cnrm.cloud.google.com_v1beta1_service_meshconfig.googleapis.com.yaml": no matches for kind "Service" in version "serviceusage.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/serviceusage.cnrm.cloud.google.com_v1beta1_service_meshtelemetry.googleapis.com.yaml": no matches for kind "Service" in version "serviceusage.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/serviceusage.cnrm.cloud.google.com_v1beta1_service_monitoring.googleapis.com.yaml": no matches for kind "Service" in version "serviceusage.cnrm.cloud.google.com/v1beta1"
make: *** [apply-gcp] Error 1
(⎈ |kf-multi-user:default)
~/kubeflow/first-multi                                                                                ⍉
▶ kubectl --context=kf-multi-user apply -f ./.build/gcp_config
computeaddress.compute.cnrm.cloud.google.com/kf-multi-user-ip unchanged
computedisk.compute.cnrm.cloud.google.com/kf-multi-user-storage-artifact-store unchanged
computedisk.compute.cnrm.cloud.google.com/kf-multi-user-storage-metadata-store unchanged
unable to recognize ".build/gcp_config/container.cnrm.cloud.google.com_v1beta1_containercluster_kf-multi-user.yaml": no matches for kind "ContainerCluster" in version "container.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-bigquery.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-cloudbuild.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-cloudsql.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-dataflow.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-dataproc.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-istio-wi.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-kubeflow-wi.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-logging.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-manages-user.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-metricwriter.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-ml.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-monitoringviewer.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-network.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-servicemanagement.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-source.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-storage.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-viewer.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-admin-workload-identity-user.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-bigquery.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-cloudbuild.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-cloudsql.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-dataflow.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-dataproc.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-logging.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-metricwriter.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-ml.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-monitoringviewer.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-source.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-storage.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-viewer.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-workload-identity-user-ml-pipeline-ui.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-workload-identity-user-ml-pipeline-visualizationserver.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-user-workload-identity-user-pipeline-runner.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-vm-logging.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-vm-policy-cloudtrace.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-vm-policy-meshtelemetry.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-vm-policy-monitoring-viewer.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-vm-policy-monitoring.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iampolicymember_kf-multi-user-vm-policy-storage.yaml": no matches for kind "IAMPolicyMember" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iamserviceaccount_kf-multi-user-admin.yaml": no matches for kind "IAMServiceAccount" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iamserviceaccount_kf-multi-user-user.yaml": no matches for kind "IAMServiceAccount" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/iam.cnrm.cloud.google.com_v1beta1_iamserviceaccount_kf-multi-user-vm.yaml": no matches for kind "IAMServiceAccount" in version "iam.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/serviceusage.cnrm.cloud.google.com_v1beta1_service_anthos.googleapis.com.yaml": no matches for kind "Service" in version "serviceusage.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/serviceusage.cnrm.cloud.google.com_v1beta1_service_cloudbuild.googleapis.com.yaml": no matches for kind "Service" in version "serviceusage.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/serviceusage.cnrm.cloud.google.com_v1beta1_service_cloudresourcemanager.googleapis.com.yaml": no matches for kind "Service" in version "serviceusage.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/serviceusage.cnrm.cloud.google.com_v1beta1_service_compute.googleapis.com.yaml": no matches for kind "Service" in version "serviceusage.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/serviceusage.cnrm.cloud.google.com_v1beta1_service_container.googleapis.com.yaml": no matches for kind "Service" in version "serviceusage.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/serviceusage.cnrm.cloud.google.com_v1beta1_service_gkeconnect.googleapis.com.yaml": no matches for kind "Service" in version "serviceusage.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/serviceusage.cnrm.cloud.google.com_v1beta1_service_gkehub.googleapis.com.yaml": no matches for kind "Service" in version "serviceusage.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/serviceusage.cnrm.cloud.google.com_v1beta1_service_iamcredentials.googleapis.com.yaml": no matches for kind "Service" in version "serviceusage.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/serviceusage.cnrm.cloud.google.com_v1beta1_service_iap.googleapis.com.yaml": no matches for kind "Service" in version "serviceusage.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/serviceusage.cnrm.cloud.google.com_v1beta1_service_logging.googleapis.com.yaml": no matches for kind "Service" in version "serviceusage.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/serviceusage.cnrm.cloud.google.com_v1beta1_service_meshca.googleapis.com.yaml": no matches for kind "Service" in version "serviceusage.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/serviceusage.cnrm.cloud.google.com_v1beta1_service_meshconfig.googleapis.com.yaml": no matches for kind "Service" in version "serviceusage.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/serviceusage.cnrm.cloud.google.com_v1beta1_service_meshtelemetry.googleapis.com.yaml": no matches for kind "Service" in version "serviceusage.cnrm.cloud.google.com/v1beta1"
unable to recognize ".build/gcp_config/serviceusage.cnrm.cloud.google.com_v1beta1_service_monitoring.googleapis.com.yaml": no matches for kind "Service" in version "serviceusage.cnrm.cloud.google.com/v1beta1"

Looks like your management cluster wasn't properly set up.
Can you retry steps in https://github.com/kubeflow/gcp-blueprints/tree/master/management?
and verify KCC is properly installed (the missing kinds are CRDs installed by KCC).

In the management, 5th step is creating an error.

Set the name for the management resources in the upstream kustomize package
kpt cfg set ./upstream name ${MGMT_NAME}

I edited some changes in the ./upstream to get make apply working. Definitely did something wrong there.
The error without manual changes:

5th step

▶ kpt cfg set ./upstream name ${MGMT_NAME}
set 0 fields
Error: open upstream/Kptfile: no such file or directory

7th step

▶ make apply
# Delete the directory so any resources that have been removed
# from the manifests will be pruned
rm -rf .build
mkdir -p .build/
mkdir -p .build/cluster
kustomize build ./instance/cluster -o .build/cluster
Error: no matches for OriginalId container.cnrm.cloud.google.com_v1alpha2_ContainerCluster|~X|kf-mgmt; no matches for CurrentId container.cnrm.cloud.google.com_v1alpha2_ContainerCluster|~X|kf-mgmt; failed to find unique target for patch container.cnrm.cloud.google.com_v1alpha2_ContainerCluster|kf-mgmt
make: *** [hydrate] Error 1

Tool Versions:
▶ kpt version
v0.24.0
▶ kustomize version
Version: {Version:kustomize/v3.2.1 ...
▶ gcloud version
Google Cloud SDK 299.0.0
▶ istioctl version
client version: 1.4.10-asm.15

Note, the management cluster needs to be a separate one, looks like you are installing both in the same cluster kf-multi-user.

Are we going to maintain two clusters? Management cluster like a parent one and deploying kubeflow applications using management cluster.

Not sure if related, can you try updated instruction after https://github.com/kubeflow/gcp-blueprints/pull/105 PR? Or probably looks like there's more changes coming in, you might want to wait a few days before all fixes are ready.
@jlewi can you confirm whether current state in this repo works?

Are we going to maintain two clusters? Management cluster like a parent one and another cluster for kubeflow applications that gets created using management cluster.

Yes, we'll have two clusters, the management cluster is meant to provide declarative GCP resource management by Kubernetes resources, it's using https://cloud.google.com/config-connector/docs/overview.
You can potentially use management cluster for any other GCP resource management.

@Bobgy @subodh101 The management cluster is broken per #102 and needs #105 as well as the related PR in kubeflow/manifests ; the pending fixes are needed.

@Bobgy @jlewi
Thanks, it is fixed now.
I was able to successfully deploy it.
Closing the issue.


[Modal][Accessibility] Modal Close Button Outline When Focused

Our modal varies from the Milo's one in how we decorate the close button's icon, which is positioned fixed. This can lead to scenarios that when focused, the outline gets applied in a weird place. This PR is to address that. You can reproduce by tabbing onto the close button. Getting this out will be good before the EDU launch as the SUSI-Light modal will be heavily used.
Resolves: https://jira.corp.adobe.com/browse/MWPW-147350
Test URLs:

Before: https://stage--express--adobecom.hlx.page/express/spotlight/education#susi-light-3
After: https://modal-accessible--express--adobecom.hlx.page/express/spotlight/education#susi-light-3

merging before the launch. Verified and is a low-risk change


fix: quotes were included in the initial GIT commit message

:tada: This issue has been resolved in version 1.5.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


WIP: Topic/monadic chain control

Fixes https://github.com/ambiata/disorder.hs/issues/48

@EduardSergeev how close is this one?

@markhibberd It works. It isn't perfect (in terms of the implementation), but does what it's supposed to do, so I'll try to prepare it for review this week.

@markhibberd More or less mergable now. Here is a toy example of usage: https://github.com/ambiata/napoleon/pull/123
Definitely not a priority now, but can be useful in future.

:+1:


Allow arguments to tests to be gathered asynchronously.

This change allows a developer to specify an argument to a test that is the result of an asynchronous function/operation. For example:
@Test(arguments: await downloadFilesFromInternet())
func readFile(file: File) {
  ...
}

These arguments are resolved at runtime during the test planning stage.

[!NOTE]
This change does not enable throwing arguments. That's more complicated (because we need to potentially handle the errors on an individual basis rather than stopping the entire operation.) I'm leaving it for a separate PR.

@swift-ci please test

@swift-ci please test


Font hinting

Please add support of font hinting. Antialias is fine, but without hinting options many fonts (for example Verdana) looks really ugly.

Use the XFT syntax:
Verdana-10:hinting=True

It work! Xft syntax support work as expected. I simly forgot set hintstyle..
Now it looks like "Verdana-11:antialias=true:encoding=utf8:hinting=1:hintstyle=hintfull:weight=bold" if anyone intresting..
Thanks!
Now i close this ticket.


Section "Changing version of apps in Azure" gives unclear advice

As Functions 3.0 are in GA we would like to upgrade C# functions from 2.0.
The docs says that .csproj should be changed, and that seems straightforward.
In this section it says something about changing FUNCTIONS_EXTENSION_VERSION. But what the implications of the disclaimer are unclear.
"Don't arbitrarily change this setting, because other app setting changes and changes to your function code may be required."
Not changing FUNCTIONS_EXTENSION_VERSION causes the app to deploy successfully, but the health check fails.
I assume because the deployment is v3 and the already deployed function is v2. Upgrading the function in Azure Portal fixes the problem.
Can you take a look at it and update the docs with sufficient migration information?

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

ID: 1df5e2bd-489d-19b2-87d3-d993ebb82021
Version Independent ID: 9e9d9ded-8f40-22be-4654-48c87f2c59e8
Content: Azure Functions runtime versions overview
Content Source: articles/azure-functions/functions-versions.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

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

@estensen Statement is to caution not to randomly/arbitrary switch between versions without taking proper steps that may be required for the target runtime version. For example, if you were migrating a c# HTTP triggered function from v1 to v2, you'd want to update your function's signature to use ILogger interface for logging instead of Tracewriter which is a required code change for v2. The same goes for any other app setting that may be applicable to one runtime version but not in the other.
I hope this clarifies the statement and clears things up. We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion :)


Cancel token doesn't work when: "ResponseType.stream" is used

Package
dio
Version
5.3.3
Operating-System
Linux
Output of flutter doctor -v
[✓] Flutter (Channel stable, 3.13.9, on Ubuntu 23.04 6.2.0-36-generic, locale en_US.UTF-8)
    • Flutter version 3.13.9 on channel stable at /opt/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision d211f42860 (12 days ago), 2023-10-25 13:42:25 -0700
    • Engine revision 0545f8705d
    • Dart version 3.1.5
    • DevTools version 2.25.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    • Android SDK at /home/tomek/Android/Sdk
    • Platform android-34, build-tools 33.0.1
    • ANDROID_HOME = /home/tomek/Android/Sdk
    • Java binary at: /opt/android-studio/jbr/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[✓] Linux toolchain - develop for Linux desktop
    • Ubuntu clang version 15.0.7
    • cmake version 3.25.1
    • ninja version 1.11.1
    • pkg-config version 1.8.1

[✓] Android Studio (version 2022.3)
    • Android Studio at /opt/android-studio
    • Flutter plugin version 75.1.2
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)

[✓] VS Code (version 1.78.2)
    • VS Code at /usr/share/code
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (2 available)
    • Linux (desktop) • linux  • linux-x64      • Ubuntu 23.04 6.2.0-36-generic
    • Chrome (web)    • chrome • web-javascript • Google Chrome 114.0.5735.198

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Dart Version
3.1.5
Steps to Reproduce
Run: https://github.com/tomekit/dio_cancel_issue_stream_get
or use below main.dart file:
import 'package:dio/dio.dart';
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Dio cancellation issue',
      theme: ThemeData(
        colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurpleAccent),
        useMaterial3: true,
      ),
      home: const MyHomePage(title: 'Dio cancellation issue'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({super.key, required this.title});
  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {

  int _downloaded = 0;
  bool _running = false;
  Exception? _failed;
  CancelToken cancelToken = CancelToken();

  @override
  Widget build(BuildContext context) {
    return Scaffold(
        appBar: AppBar(
          backgroundColor: Theme.of(context).colorScheme.inversePrimary,
          title: Text(widget.title),
        ),
        body: Center(
          child: Column(
            mainAxisAlignment: MainAxisAlignment.center,
            children: <Widget>[
              Text('_downloaded: ${_downloaded}, _running: ${_running}, _failed: ${_failed?.toString()},')
            ],
          ),
        ),
        floatingActionButton:
        Stack(
          children: <Widget>[
            Align(
              alignment: Alignment.bottomLeft,
              child: FloatingActionButton(
                onPressed: () async {
                  fetch(ResponseType.bytes);
                },
                tooltip: 'Start bytes',
                child: const Icon(Icons.start),
              ),
            ),
            Align(
              alignment: Alignment.bottomCenter,
              child: FloatingActionButton(
                onPressed: () async {
                  fetch(ResponseType.stream);
                },
                tooltip: 'Start stream',
                child: const Icon(Icons.start),
              ),
            ),
            Align(
              alignment: Alignment.bottomRight,
              child: FloatingActionButton(
                onPressed: () => cancelToken.cancel(),
                tooltip: 'Cancel',
                child: const Icon(Icons.cancel),
              ),
            ),
          ],
        )
    );
  }

  fetch(ResponseType responseType) async {
    final url = "http://ash-speed.hetzner.com/100MB.bin";

    final dio = Dio();

    final options = Options(
      // responseType: ResponseType.bytes, // Works fine
      // responseType: ResponseType.stream, // No effect
      responseType: responseType
    );

    // For ResponseType.bytes purposes
    onReceiveProgress(int sent, int __) {
      setState(() {
        _downloaded = sent;
      });
      return;
    }

    try {

      setState(() {
        _running = true;
        _failed = null;
        cancelToken = CancelToken();
      });

      final response = await dio.get(url, options: options, cancelToken: cancelToken, onReceiveProgress: onReceiveProgress);
      final status = response.statusCode;

      var downloadedTotalStream = 0;
      if (status == 200) {
        await for (final List<int> dataChunk in response.data.stream) {
          downloadedTotalStream += dataChunk.length;
          setState(() {
            _downloaded = downloadedTotalStream;
          });
        }
      } else {
        setState(() {
          _failed = Exception("Status code: $status");
        });
      }

    } catch(e) {
      setState(() {
        _failed = e as Exception;
      });
    }

    setState(() {
      _running = false;
    });
  }
}

Click middle "Start stream" button to start streamed download, then click bottom right: "Cancel" button. Nothing happens in the release mode. In the debug mode your IDE (in my case Android Studio) may (it doesn't happen consistently) capture uncaught exception.

That's unexpected behavior, request doesn't get cancelled.
Click bottom left: "Start bytes" button to start bytes download, then click bottom right: "Cancel" button. DioException is thrown. That's expected behavior, request cancelling takes place.
Expected Result
DioException shall be thrown with type set to DioExceptionType.cancel even if: responseType: ResponseType.stream is used.
Actual Result
DioException isn't thrown when request with responseType: ResponseType.stream gets cancelled.
Test app:

I agree, thanks for the reproduction. I think I have a solution but testing this is kinda hard.
Do you think https://github.com/cfug/dio/issues/1953 is the same problem?

I've been investigated about the cause of the issue.
When we request stream responses, the response body returns immediately.
https://github.com/cfug/dio/blob/bedcc54c91a800a3b1aac0092151ca401f716803/dio/lib/src/transformers/sync_transformer.dart#L60-L63
When you get the response, the request flow is finished. Nothing in the queue was still awaiting, thus the cancel token is no longer effective (because the request is, by a specific aspect, ended). From the flow, we can say the behavior is as desired.
Given the above fact, because you have already obtained the stream, you can use other mechanisms rather than cancel tokens to stop the stream reading.
The issue is nothing related to #1953 and #2028. I understand everyone's issue is urgent to themselves, but referencing unrelated issues will cause redundant information for people who subscribed to those issues, and increase the complexibility for maintainers to find the root cause.
Still, I've tried to improve this and managed to throw the cancel exception for the stream.

But it doesn't look like a proper way to solve it because it depends on implementation in adapters. So I gonna leave this open and continue to investigate to see if we can have a proper solution.

@AlexV525 I already had some changes and tests for this - see #2032


Docs: add changes to documentation (productivity tools)

Include 15 developer tools to make you super productive
Resolves: N/a
See also: N/a

Excellent additions @Terieyenike