Add python sdk

Is your feature request related to a problem? Please describe.
Just like we have the openapi generated java client sdk, there needs to be generated Python sdk for python integrations with UC.
Describe the solution you would like
It's important for auto-generated client SDKs to be coversioned with the server with the API spec and the server supporting the spec. Hence it's best if all the auto-generated clients ar in this repo so that all of them can released together. Otherwise it is going to be a major version hell if the server of version x is going to be compatible with java sdk version x (since java is already in this repo), python sdk version y, c++ sdk version z, etc.
I think the best way to proceed is to add the python generation in the sbt project in the same way as that has been added for java.

location: clients/python
open API generation configuration: same as the current python sdk 0.1 released in pypi.

Thanks @tdas!  Linking the related discussion: https://github.com/unitycatalog/unitycatalog/discussions/213

I can take this!

@kevinzwang - sweet, assigned this one to you! 😎

I found this today https://github.com/unitycatalog/unitycatalog-python, was it mean to be maintained as a separate project?

I found this today https://github.com/unitycatalog/unitycatalog-python, was it mean to be maintained as a separate project?

Pulling the code from that repo into here would be one possible method, but we would like to explore using open-source alternatives to Stainless first

@kevinzwang Hey Kevin, at Fern (buildwithfern.com) we offer open-sourced SDK generation and would love to demo an idiomatic python SDK for you. Interested in chatting?


Native Ad - Image Responsiveness Issues

Plugin Version

google_mobile_ads: ^1.2.0
Steps to Reproduce

Create a Native Ad
Create a listview with cards
Try to make the native ad look like the cards like this example: https://lh3.googleusercontent.com/KtEoccHt7kwMVm4GdhwA-DyEcd2DEQCqWZuiQi0z2OoBQOUkD0OUIgnb75iGqHSPCHmsoPjTvVS3LprzHGGDlR2S2YUrIt7fPJZ9=w0
First issue - I was only able to find 2 templates?! Small and medium sizes? The Flutter version of the official documentation is not really clear about it.
I used the medium size template, and just tried to move the image banner to the top of the ad to look more like a card using the xml template file.
Seems easy but to my surprise I was not able to make the banner image fit the card, the image is not using the full size horizontally or vertically properly. And since phone screens are different, the image banner always looks weird on different screens. Screenshot example here: https://drive.google.com/file/d/1AI-hXibMXlQv8_DYQaICfE6XrRdk3RUL/view?usp=sharing
Tried to change the xml file, and tried different sizes in the AdWidget without any success. I'm sure I'm missing something probably simple, but I was not able to find anything about it in the official documentation or examples.

Expected results:
Trying to make the Native Ad to look like a card. Example: https://lh3.googleusercontent.com/KtEoccHt7kwMVm4GdhwA-DyEcd2DEQCqWZuiQi0z2OoBQOUkD0OUIgnb75iGqHSPCHmsoPjTvVS3LprzHGGDlR2S2YUrIt7fPJZ9=w0
Actual results:
The image inside the Native does not fit the card properly, and always looks out of place on different mobile screens: Screenshot example here: https://drive.google.com/file/d/1AI-hXibMXlQv8_DYQaICfE6XrRdk3RUL/view?usp=sharing
I changed the xml template file several times, and tried different sizes in the AdWidget without any success. I'm sure I'm missing something probably simple, but I was not able to find anything about it in the official documentation or examples.

Logs

Hi @ldobreira, Thanks for filing the issue. Can you please share a minimal and complete sample project(which I can directly run with minimal or no changes) to investigate further?

Hi @maheshmnj! Thank you for your fast reply.
Sure, I made an example for you at https://github.com/ldobreira/testnativeadcard
Please let me know what I'm missing.

Hi @maheshmnj, unfortunately, it's not working in all screen sizes... If you change the Container padding around the cards (or emulate other devices) you can easily reproduce the issue... Please check the example at https://imgur.com/a/O9sgOJJ

Thanks for the update @ldobreira, I don't have much idea on the native code. I am labeling this issue for further insights from the team.
sample project can be found here https://github.com/googleads/googleads-mobile-flutter/issues/582#issuecomment-1150510781
cc: @jjliu15

@ldobreira - Can you confirm whether you are using AdMob or Ad Manager?

For Ad Manager, you can request fluid size native ads, which contain assets that expand into the available inventory space.
For AdMob, there is only support for the small and medium templates, which can receive fixed size assets which may create whitespace when inflated into the available inventory space. This occurs because the aspect ratio of the advertiser provided images must be preserved.

@ldobreira - Can you confirm whether you are using AdMob or Ad Manager?
* For Ad Manager, you can request fluid size native ads, which contain assets that expand into the available inventory space.

* For AdMob, there is only support for the small and medium templates, which can receive fixed size assets which may create whitespace when inflated into the available inventory space. This occurs because the aspect ratio of the advertiser provided images must be preserved.

I'm just using Admob.... what should be the standard size for the medium templates?

The standard size for medium rectangle ads is 300x250. This size tends to have more ad inventory available from advertisers. The fixed sizes that tend to have more ad inventory available (and are therefore more likely to serve) follow IAB standard ad size specifications.
Since native ads can be of arbitrary size, there will be whitespace around the ad image whenever the native ad image container is larger than the image asset. For Fluid native assets, whitespace can still occur around the image if the native ad image container has an aspect ratio that doesn't match the image asset aspect ratio.
@ldobreira - since you're using AdMob, I suspect this issue is occurring because the native image asset doesn't match the image container precisely. Unfortunately this is working as intended as not all advertisers campaigns are capable for supporting fluid.
I'll close this issue but feel free to reopen if you think there is a problem with native rendering (e.g. image asset in ad response should actually fit the native ad image container).


Fixed test criteria to match functionality

The following changes reflect how the test should be implemented to ensure proper functionality of the new asset display options.

testtwothre


Post-processing of extracted text > Joining hyphenated words which are common in documents

Often, words will be broken by a hyphen to wrap them into a column. These breaking hyphens would need to be detected, removed and the two parts of the word joined together. Note that distinguishing them from valid occurrences such as a bullet point (see above) may be tricky.
Example:

The  national  effort  to  draw  and  execute strategic  plans  will  benefit  from  financial contribution  of  the  international  communi- ty.  It  will  be  necessary  to  create  conditions so  that  potential  support  is  converted  into actual  support.  For  that  purpose  the administration  shall: –  Establish  a  forest  fund  to  channel  inter- national  funds  meant  for  the  support  of the  implementation  of  this  forest  policy. –  Promote  the  financing  of  capacity  build- ing  and  investments  to  the  private  sec- tor  by  development  banks

Hey team! Please add your planning poker estimate with ZenHub @eurolife @kdutia @opyate

Bullet points seem to use m-dash, and hyphenated words a dash. (difference)


Incompatibility with Forever?

Attempting to use with forever:
sudo supervisor -x forever index.js

Any restart triggered by supervisor on filechange will net the following response / error:
Error: EADDRINUSE, Address already in use
    at Server._doListen (net.js:1100:5)
    at net.js:1071:14
    at Object.lookup (dns.js:159:5)
    at Server.listen (net.js:1065:20)
    ...

I think you're right. I posted this before I had a strong idea of the purpose of Supervisor.. Sorry for the confusion / jumping the gun, and thanks for the friendly heads-up!


UI needs improvement

The UI design needs some touch up

sir i want to contribute to this Repository i have fair experience of android development in kotlin.

Hello Akash, I am glad to hear you're interested in the project. what
specifically do you want to work on? that issue #7 is a bit generalized so
selected some specific functionality or improvements you'd like to add to
the app and let me know. after that we can create issues and i will assign
you there on github.
On Mon, Aug 23, 2021 at 5:40 PM Akash @.***> wrote:

sir i want to contribute to this Repository i have fair experience of
android development in kotlin.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/elysium09/MVVM_Notes/issues/7#issuecomment-903835844,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGJDG6VC4PS43LJNIN5ZJ4TT6JMW3ANCNFSM5CR5X6DQ
.


type: enhancement Add IT translate

Hello,
I've translated the descriptions into Italian, but I'm not sure if I need to do anything else to make it work. If I do, please let me know.
All the tests have passed, of course.
Translation done with ChatGPT, I have checked them quickly, and they seem correct to me.

sorry, I'll check the translations better


Allow to set parameters when connecting to Clickhouse server

Can you allow to set parameter max_partitions_per_insert_block on connect to DB like in clickhouse-client (command clickhouse-client -h <IP_ADDRESS> --max_partitions_per_insert_block=4999 works ok)?
It looks like very useful because for different connection this parameter should be different for better error control.
For example: sql.Open("clickhouse", 'tcp://localhost:9000/?username=test&password=123&database=test&timeout=1s&max_partitions_per_insert_block=4999')

@altush1983 It's implemented now!
Please check it out and let me know if you find any bugs, thanks.


[feature] Install man pages

Hi @shinokada ,
Do you think it is this easy to add something like installing man pages from the repo if it presents there?
I used awesome to install https://github.com/alexmyczko/fnt, which tool has no --help option but has man pages.
Could awesome use the same logic as installing the bash script with the same name to copy the man pages to the right location? :thinking:

Good point!
And thank you for using Awesome package manager.
It seems the package installs the fnt.1 file to the /usr/share/man/man1 directory when you use its make file.
In this case you need to copy the fnt.1 file to the man directory like this:
copy $HOME/.local/share/awesome/fnt/fnt.1 /usr/share/man/man1

Please let me know.


Dynamic creation of service accounts based on rolebinding label selec…

This PR fixes #
Checklist

[x] I have signed the CLA
[x] I have updated/added any relevant documentation

Description
What's the goal of this PR?
Based on https://github.com/FairwindsOps/rbac-manager/issues/137
We have some similar need. We would like to create dynamically a service account in each namespace we request a role binding based on label selectors.
I see the difficulty here, it's not that obvious. This is a suggestion, and I'm ready to take into account your comments.
What changes did you make?
If a service account in an rbac definition does not have a specified namespace, we get the ones from the rolebindings if there are any.
What alternative solution should we consider, if any?
The current way is to have an exhaustive list of services accounts/namespaces.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Otmane TAZI seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for the PR! I'll have to take some time to consider this and test out this implementation.

Hello,
Is there some news?
Can you please rerun the ci/circleci: insights
It shows the message: Vault token expired or not available!
Thanks

Sorry about the long tail on this. I've been re-familiarizing myself with this codebase lately, and I took a look at the implementation here.
I do really like the idea, and I think this is probably how we should have done this originally. However, I am really concerned about the lack of backward-compatibility here with the old way that rbac-manager created service accounts.
Do you have any thoughts on how we could manage that? It's possible we document the changes and do a major release, but I also want to consider how we could do this without breaking existing installations.

Sorry about the long tail on this. I've been re-familiarizing myself with this codebase lately, and I took a look at the implementation here.
I do really like the idea, and I think this is probably how we should have done this originally. However, I am really concerned about the lack of backward-compatibility here with the old way that rbac-manager created service accounts.
Do you have any thoughts on how we could manage that? It's possible we document the changes and do a major release, but I also want to consider how we could do this without breaking existing installations.

Thanks for your feedback, I appreciate.
Concerning the backward compatibility problem, the only difference is when someone creates a service account without specifying a namespace.
If I'm not wrong, in this case, the current context is used. This means we create the service account in the same namespace the rbac-manager is running on, while we give the permissions on the role binding to a service account with the same name, but in each of the rbac namespaces.
The second part does not change, we just make it explicit.
The only difference then is that we create with this change a service account in each namespace pointed by the selector if it does not exist, while previously the user had to create it by himself (Another CR, helm chart...).
There are indeed some situations where this could be a problem even if it's possible to find workarounds.
We could add an optional boolean to the Subject struct, by default to false, that allow to activate this feature. For example "useRoleBindingsSelectors". It will be used only if the subject is a service account and ignored on cluster role bindings.
Let me know if this solution fits you so I can update my PR accordingly,

Hi,
Any reason why this PR was just closed? Would really need this feature as it would reduce repetitive role binding definitions by a lot!
Thank you

Thanks for tour support. I have the same question.


CL assistance

10 hr/week, target 15-20 hr/ week max.

[ ] Install Cubit version 16.06.
[ ] Install Python 3.7.x where x can be any minor version.
[ ] Start a notes.txt document that records the full install path for Cubit and full install path for Python.
[ ] Review 2022-08-23-Getting-Started.pdf file.

[ ]  Install Cubit version 16.06.
[ ]  Install Python 3.7.x where x can be any minor version.
[ ]  Start a notes.txt document that records the full install path for Cubit and full install path for Python.
[ ]  Review 2022-08-23-Getting-Started.pdf file.
[ ]  Create a GitHub account (if you don't already have one, as you will need to do pull requests for this autotwin/mesh repo).

Next:

[ ]  Local: cd ~/autotwin/
[ ]  fork this repo https://github.com/autotwin/mesh
[ ]  then git clone your forked version into the ~/autotwin/ folder
[ ]  create a virtual environment atmeshenv following these instructions https://github.com/autotwin/mesh/blob/main/config/README.md
[ ]  verify .quality and .style shell scripts run to completion

Quoting to track the status

Tasks are completed as of 8/24/22 9:50a MT

In the mesh/examples folder, can you please construct a "stand-alone" (can run from the command line) script called examplar_boxplot.py that makes six exemplar matplotlib box plots.   The result of the script will output a .png that appears similar to this:

You can hard code six different distributions between zero and one using numpy.   This effort will be a template for how we do a study later.
The study later will investigate minimum scaled Jacobian distributions as a function of study number.  Each successive study will try to make the distribution push closer toward unity (away from zero), and have a tighter band on the spread of the distribution.
It doesn't matter so much what the exemplar hard code distributions are, as long as you can

have a minimum value > 0
have a maximum value < 1
assess the 25%ile, 50%ile, and 75%ile
draw a box plot indicating the quartiles as shown above.

Update has been pushed. I ordered the boxes based on increasing median values, so the xlabel case numbers appear wonky. I can change that back, if needed.

Having the xlabel order as you have it is just fine.  The critical step here you achieved, which was to make a small example of a box plot, so we can use it in the larger algorithms later.

I am guessing you already know markdown, but just in case, this guide may be helpful: This markdown guide may be helpful to you: https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet

Having the xlabel order as you have it is just fine. The critical step here you achieved, which was to make a small example of a box plot, so we can use it in the larger algorithms later.

The meeting yesterday helped clear up questions I had regarding this. If your hypothesis is correct, then the xlabel should be in ascending order, assuming we label the box plots along the x-axis using something like cell count (or cell count/volume, I'm not entirely sure the metric used is since FEA is outside my wheelhouse). It might be a little bit extra, but it could be a useful tool to double-check the data.

fyi, i am updating sensitivity.py so it loops over n input files.  more to come later...

Can you please try to tackle this one next?  I think it is in your wheelhouse.

[ ] study the diff I made to your original exemplar_boxplot.py file here: https://github.com/autotwin/mesh/commit/57438156d14acd7fa07a4418e614be0b6231953e#diff-f0e7ce47bf5f87bbee9acad6d7e27dbeaa5d51f641d4a493ba9e98942c2965da

n_studies = 6  # define once-and-for-all, avoid magic numbers later

Just a minor style point that allows code to become D.R.Y. (don't repeat yourself), and allow the code to be array-reflective --- that is if the array size changes, all other downstream code automatically changes (no need to update magic numbers appearing downstream in the code).

Next, and can you tackle this one:

[ ] Review https://github.com/autotwin/mesh/blob/main/examples/sensitivity.py#L33 and https://github.com/autotwin/mesh/blob/main/examples/sensitivity.py#L171
[ ] Can you use your exemplar_boxplot.py source as inspiration to extend sensitivity.py so that the n histograms are plotted at the end of the script?

Next, and can you tackle this one:

[ ]  Review https://github.com/autotwin/mesh/blob/main/examples/sensitivity.py#L33 and https://github.com/autotwin/mesh/blob/main/examples/sensitivity.py#L171
[ ]  Can you use your exemplar_boxplot.py source as inspiration to extend sensitivity.py so that the n histograms are plotted at the end of the script?

Quoting so I can check off the box as I go.

To let you know, it looks like I got bounding_box and cell intervals implemented in .yml input file, so soon we can launch another automated study.  So, more work coming in the pipe!   FYI.

Just wanted to bump the thread. I submitted a merge request from my fork a couple weeks back. Is there anything else you want me working on at the moment?

Thanks for the PR.   I am at a conference this week and will try to get the PR merged.  No other near-term actions until I after a bit the merge.  Thanks also for bumping the thread, email alerted me to the same.  Cheers.

On Sep 13, 2022, at 11:14, calehma @.***> wrote:

Just wanted to bump the thread. I submitted a merge request from my fork a couple weeks back. Is there anything else you want me working on at the moment?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.

Started to refactor this weekend.  Do you mind sending me a Teams invite on my calendar for a day/time that suits you this coming work week (if at all, since you might be too busy, which is fine too).

I moved most of the IO user configuration into .yml files (see https://github.com/autotwin/mesh/blob/main/doc/sphere_mesh_refinement.md#create-inp-files) and have flattened and separated out the concerns from the sensitivity.py script.  So now there are independent scripts that do file IO as follows:

.stl to .inp
.inp to minimum scaled Jacobian .csv

Next, the individual .csv files can be used with the histogram plotting, and I will take that up next week.   This too can use a .yml input file to control things like plot color, line width, etc.
The benefit of the .yml approach is that we separate configuration from methodology.  Then, one methodology can operate on $n$ number of configuration states.  Also, then our methods do not have hard-coding to configuration.
This note is just FYI to explain some of the rationale behind the updates.


Update French documentation

Update French documentation.  Also the text editor I use removed a few trailing spaces at the end of sentences.

Looks good to me !!


Samesite Lax cookie not being set

When running the login test with ApolloGraphQL; the request works fine. However, the cookie is not being set because the browser is blocking the cookie from being set due to SameSite=Lax.
Can anyone offer any guidance on how to get the cookie to be set. I have configured cors to work with the apollographql query studio:
app.use(
    cors({
      origin: ["http://localhost:3000", "https://studio.apollographql.com"],
      credentials: true,
    })
  );

Here is my session configuration:
app.use(
    session ({
      name: "qid",
      store: new RedisStore({client: redisClient, disableTouch: true}),
      cookie: {
        maxAge: 1000 * 60 * 60 * 24 * 365 * 10, // 10 years
        httpOnly: true,
        secure: __prod__, //cookie only works in https
        sameSite: "lax", // csrf
      },
      secret: "keyboard cat",
      resave: false,
      saveUninitialized: false,
    })
  );

Any help is greatly appreciated.

I had the same issue and to make it work I had to set sameSite: 'none' and secure: true.
You will also have to toggle the cookies on in Apollo Studio (click on the gear icon next to the local graphql server url). On the same menu, you will have to add this default header: x-forwarded-proto : https.
The annoying thing is that I have to keep alternating between the cookie settings sameSite: 'none' and sameSite: 'lax' as well as secure: none and secure: __prod__, depending on whether I'm testing the cookies from Apollo Studio or from the browser respectively. Maybe someone can come up with a better solution...

This is driving me nuts! I downgraded both [node-]redis and connect-redis to the versions Ben uses, wondering if that might help. Nope. My cookies are being saved in my redis db at the login mutation, along with the userId. The problem I'm having is that a new sessionID is being generated on every req so that the me Query never works. I've just about Googled myself to death, and I have no idea what's causing that. This happens when using both the Apollo Studio and GraphQL Playground v1.8.10. I'm completely stuck.

This is driving me nuts! I downgraded both [node-]redis and connect-redis to the versions Ben uses, wondering if that might help. Nope. My cookies are being saved in my redis db at the login mutation, along with the userId. The problem I'm having is that a new sessionID is being generated on every req so that the me Query never works. I've just about Googled myself to death, and I have no idea what's causing that. This happens when using both the Apollo Studio and GraphQL Playground v1.8.10. I'm completely stuck.

Did you check that the cookie is actually saved in the browser? express-session shouldn't be creating a new session on every request if there is already a cookie attached.

Yep. Cookie is saved in the browser.

Just cloned this repo and created a fresh database to test. Checked out the 6_sessions branch, and I'm having the SAME issue. So, I'm NOT losing my mind. Each req gets a new req.sessionID. Cookie is saved in the GraphQL Playground v1.8.10 browser and session info is saved in Redis along with the added userId parameter with the login query. When I run the mequery immediately afterward, a new session is generated with a new req.sessionID and, obviously, no userId parameter. Given that there is no userIdto search for, the me query always returns null.
So... what am I missing? I have "request.credentials": "include", set in GraphQL Playground, what else could it be? Is it a CORS issue?

@brimarq  If it was a CORS issue, I believe the request would fail before any session is created. Have you tried to run the requests from the frontend instead?
I actually had a lot of issues while testing the cookies because with the latest versions of Apollo, the GraphQL playground is executing from an external site (Apollo Studio) instead of locally, and I needed to use different configurations depending on whether I was doing the requests from my frontend or from Apollo Studio.

@vgarmes Interesting... on a whim, I just tried again with @benawad 's repo, sending my req with Insomnia, and it works! I didn't want to fool with the new Apollo Studio for the reason you mentioned - because it routes requests to an external site; and, I was frustrated with Altair GraphQL Client trying to send credentials. So, I opted for the older GraphQL Playground, to at least match what Ben was using. I had used that in the past with no issues; but, now it seems to be buggy. There are other issues with it, too - occasionally, the entire window will lock in place on the screen, and I'll have to restart the application. Not good. Insomnia is such a breath of fresh air - I've used it before with REST; I should have known to just stick with it. I'll be going back to my project to test shortly.

@brimarq nice! I will definitely give Insomnia a try, I've heard good stuff about it.

@brimarq I'm curious what was the frustration you had with Altair and sending credentials? 🤔

@brimarq I'm curious what was the frustration you had with Altair and sending credentials? 🤔

Oops... correction... I could send credentials ok, I just couldn't find the cookie. Just checked again this evening and I see it now. I had been looking in the dev tools "Application" tab under Storage -> Cookies, as in Ben's GraphQL Playground example, and it never shows up there. In Altair, the cookie appears in the "Network" tab. In my frustration last night, I completely missed that. Clearly, I should take more frequent breaks. LOL
In Insomnia, the cookie has it's own dedicated tab in the response pane such that you can't miss it.

@brimarq If it was a CORS issue, I believe the request would fail before any session is created. Have you tried to run the requests from the frontend instead?
I actually had a lot of issues while testing the cookies because with the latest versions of Apollo, the GraphQL playground is executing from an external site (Apollo Studio) instead of locally, and I needed to use different configurations depending on whether I was doing the requests from my frontend or from Apollo Studio.
Feel free to check out my repo if it's any help, I recently started the project so I'm using the latest versions of most packages.

I've tried literally everything on this thread and even googled the shit out of myself but this doesn't seem to work, when I run the query I never get the sessions in the application tab, all I get is this

This is my code -> https://github.com/Deveshb15/redemon
can someone help me out over here?

@Deveshb15 did you also set Apollo Studio's default headers to x-forwarded-proto : https ?
I stopped using Apollo Studio because I couldn't bother changing the cookie options every time. So now I'm using Postman instead and had no issues so far.

I had the same issue and to make it work I had to set sameSite: 'none' and secure: true. You will also have to toggle the cookies on in Apollo Studio (click on the gear icon next to the local graphql server url). On the same menu, you will have to add this default header: x-forwarded-proto : https.
The annoying thing is that I have to keep alternating between the cookie settings sameSite: 'none' and sameSite: 'lax' as well as secure: none and secure: __prod__, depending on whether I'm testing the cookies on Apollo Studio or on the frontend respectively. Maybe someone can come up with a better solution...

What I did to address this was set the same headers when creating the URQL client in _app.tsx:
const client = createClient({
  url: "http://localhost:4000/graphql",
  fetchOptions: {
    credentials: "include",
    headers: { "X-Forwarded-Proto": "https" },
  },
});

@some-things
This worked for me, thank you for sharing.

I had a similar issue, I was wrongly setting the cookie options in session middleware.
set option
secure: false


Adding Theme support?

Hi,
With some Telescope builtins I work with `theme = "ivy"' (bottom window and not popup):
https://github.com/nvim-telescope/telescope.nvim#themes
Is there a way to configure telescope-coc to have a theme parameter?
Thanks!
Gil

Does :Telescope coc commands theme=ivy work for you?

Fantastic!
How do I pass the height=0.2 parameter?  I tried:
Telescope coc workspace_diagnostics theme=ivy height=0.2

-- but did not work (sorry, don't really know lua).
Thanks again!

require("telescope").setup({
  extensions = {
    coc = { theme = 'ivy' }
  },
})

Now :Telescope coc commands will use ivy theme.

Thank you.
In case this is helpful, here's how height is passed to the ivy theme for a builtin:
lua require('telescope.builtin').find_files(require('telescope.themes').get_ivy({layout_config={height=0.2}}))

In my mind, the issue might be related to the difference in how builtins are called (with parenthesis for passing arguments) and how extensions are called (with spaces separators??). Then, of course, the implementation of the extension needs to pass the arguments ... (but, again, I do not really code in Neovim/Telescope/lua so I might be way off here).
Thanks again!

Okay, mystery solved:
:lua require("telescope").extensions.coc.workspace_diagnostics(require('telescope.themes').get_ivy({layout_config={height=0.2}, previewer=false}))

I took me some time to get figure out the right nested syntax, and then I found how to call an extension as a function (with arguments).
Sorry for all this verbosity, but I am so happy to be able to use coc this way!
Thanks for all the help.


Revert: UEFI feature from #3638 and #3985

This PR reverts #3638 and #3985 which we think is causing regression for Vmware wrt 4.14 release. If regression is confirmed to go away with the revert, we probably want to go ahead with 4.14 without the feature and attempt to work on the UEFI feature towards 4.15.
cc @pavanaravapalli - hope you understand and we've your support.

@blueorangutan package

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos7 ✔debian. JID-1232

closing due to false alarm


Wait until finalisers for machine class secrets are removed

The destroyMachine should now also wait for machine class secret finalizers to be removed by MCM. This check will kick in with only newer version of MCMs.

Thanks, squash the commits please.

I have squashed the commits as requested.

Thanks.


Roll Flutter Engine from c08a286d60e9 to 30ba71efad37 (1 revision)

https://github.com/flutter/engine/compare/c08a286d60e9...30ba71efad37
2023-02-01<EMAIL_ADDRESS>Roll Skia from 8f33da33edcf to 4b5799677173 (1 revision) (flutter/engine#39318)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC bdero@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


build path should not be hardcoded

One could customize the elixir "version" build path as elixir/version.js has a buildPath parameter to be used in the gulpfile.js
see https://github.com/laravel/elixir/blob/master/tasks/version.js#L24
That's really great, but I suggest to avoid hardcoding build path in elixir PHP helper to be able to customize it there too if needed.

Please fix the cs issues hilighted by styleci.

Prefer to stick to a convention.

If you really want to customize it, you can extend the application class. ;)

Thank you guys for your feedback.
Isn't it a little weird to be able to customize in gulpfile but not in views ?! Maybe I missed something in the docs...
Anyway, thank you Taylor for your work so far and your time on this PR, it's your baby and your are pleased to just do as you wish ;)
Thank you Graham for your suggestion, but for the record I will stick on adding a new elixir_custom function in my custom helpers library till we can finally customize the "versionized" build directory :)


helm template --show-only option path matching is confusing

Output of helm version:
version.BuildInfo{Version:"v3.4.1", GitCommit:"c4e74854886b2efe3321e185578e6db9be0a6e29", GitTreeState:"clean", GoVersion:"go1.14.11"}

Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.5", GitCommit:"e6503f8d8f769ace2f338794c914a96fc335df0f", GitTreeState:"clean", BuildDate:"2020-06-26T03:47:41Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.):
N/A
The helm template flag --show-only, -s seems to have a confusing pattern for selecting the path of the template you want to render when using a local chart.
How to reproduce:
helm create example

# render template
helm template ./example

This will render the template as expected producing output like the following (taking the last rendered template):
...

---
# Source: example/templates/tests/test-connection.yaml
apiVersion: v1
kind: Pod
metadata:
  name: "RELEASE-NAME-example-test-connection"
  labels:
    helm.sh/chart: example-0.1.0
    app.kubernetes.io/name: example
    app.kubernetes.io/instance: RELEASE-NAME
    app.kubernetes.io/version: "1.16.0"
    app.kubernetes.io/managed-by: Helm
  annotations:
    "helm.sh/hook": test
spec:
  containers:
    - name: wget
      image: busybox
      command: ['wget']
      args: ['RELEASE-NAME-example:80']
  restartPolicy: Never

Based on the # Source: example/templates/tests/test-connection.yaml line, I would expect that I could use the following to render just that file:
helm template ./example -s example/templates/tests/test-connection.yaml
Error: could not find template example/templates/tests/test-connection.yaml in chart

However, that does not work. Instead, after a lot of trial and error, I found that the following works:
helm template ./example -s templates/tests/test-connection.yaml

To me it does not seem intuitive that the path displayed on that output is not what you would put for the path. I looked at the code and found where this was happening, and I would like to propose a small change that might make this more straight forward
https://github.com/aro5000/helm/commit/821296f0113dec44ec6bc2f50374797f65b27982
This is the first time I have ever submitted an issue for anything like this so please be patient with me and let me know if there is anything else I need to do or information I can provide. I'm a heavy user of this project and I think all the work happening in this ecosystem is amazing! If the code suggestion does not seem reasonable, please let me know if there is a place where I could maybe make the docs a bit more obvious or if I should submit a PR. I would like to get involved and contribute any way I can!

What happens if the pattern matches multiple filepaths? It is common for
This also allows for undefined behaviour such as -s a matching any file path with the .yaml extension. So I do not believe this is a change that would help.
Perhaps some further documentation around the expected inputs and outputs would be helpful.

@bacongobbler Thanks so much for the feedback! I see what you mean that the behavior is undefined.
Keeping with the same path matching convention, can we assume that it will always try to match starting from the templates/ directory? If so, I'm wondering if this commit would make more sense - basically just taking the file path input and trimming everything before templates/. https://github.com/aro5000/helm/commit/e61e7a9c6128d309cafdd91241d031143946e1bd This works with my example mentioned above.
If I'm wrong that we can't make this assumption, let me know a good place where I could update the documentation! Should it be in the "help" text of the CLI output? Or somewhere else? Thanks again for your feedback and time!

Hi @bacongobbler - just following up on this. I've submitted a PR with a proposed fix for this, but if it is preferred, I'm happy to abandon it for a docs update. Thanks!
#9170


Implementing 'Balanced Resource Utilization' algorithm in scheduler

Current algorithm is simple when considering the resource and may lead to imbalanced resource utilization. Balanced Resource Utilization algorithm can be introduced as a new PriorityFunction so that users could choose to enable it when implementing custom algorithm_provider.
See post at Implementing Balanced Resource Utilization in kubernetes scheduler? - Containers at Google

This was implemented a while ago.


'batch_size' not 'batch-size'

Hi @matthew-z
Thank you for your wonderful implementation of R-net. I am still training and testing it. There is a very minor issue in your README.md, which is batch_size in your setting but not batch-size.

Thank you for pointing out the problem :).
BTW, there are many problems in this implementation......I am trying to fix them.


fix/UserLeaderboard

Hi !
A little PR to fix something related to the UserLeaderboard class. I removed the gamemode from the method MulpyVersus.get_user_leaderboard_in_gamemode() parameters since it wasn't in the __init__ parameters, we can then specify the gamemode in the method UserLeaderboard.get_score_in_gamemode as intended originally I guess :)

Now I see that I'm getting a 404 !

Okay I found the issue ! All good !

Can you merge for me since I didn't use a sign commit ? @AshladBP

Can you merge for me since I didn't use a sign commit ? @AshladBP

Sure, done!


Sequences not returning unique value

My model tests used to pass, I have not changed them and now they fail with "name already exists".
I have looked at and tried many solutions but have not found one that works. Also tried using instance variables in my test and moving instantiation to different blocks, before, it, describe and context.
FactoryGirl.define do
  factory :activity do
    sequence(:name) { |n| "name_#{n}" }
  end
end

RSpec.describe Activity do
  let(:activity) { FactoryGirl.create :activity }

  it "has a valid factory" do
    expect(activity).to be_valid
  end
end

rspec-rails > 3.5
factory_girl_rails > 4.8
ruby > 2.3.3
rails > 4.2.0

I think your problem is not related to FactoryGirl, but rather the fact that your database might not be getting cleaned up. Can you double check that the activities table is empty before the test that is failing?

Thank you for your response. Its working now. That was probably the problem i was fiddling around with rails_helper and spec_helper. My apologies.


"failed to find TestImports-Unit-Tests.xctest in expected locations:" if apple.experimental.tree_artifact_outputs is set to 1

Checkout this branch
Run these commands:

# Generate a project
bazel run //tests/ios/xcodeproj:Test-Imports-App-Project

# Invoke `xcodebuild`
xcodebuild -project tests/ios/xcodeproj/Test-Imports-App-Project.xcodeproj -scheme TestImports-Unit-Tests -destination "id=SOME_VALID_SIM_ID" -PBXBuildsContinueAfterErrors=0 test

You'll hit this err:
Testing failed:
        failed to find TestImports-Unit-Tests.xctest in expected locations: bazel-bin//tests/ios/unit-test/test-imports-app/TestImports-Unit-Tests.xctest bazel-bin//tests/ios/unit-test/test-imports-app/TestImports-Unit-Tests.__internal__.__test_bundle_archive-root/TestImports-Unit-Tests.xctest bazel-bin//tests/ios/unit-test/test-imports-app/TestImports-Unit-Tests.runfiles/_main//tests/ios/unit-test/test-imports-app/TestImports-Unit-Tests.xctest bazel-bin//tests/ios/unit-test/test-imports-app/TestImports-Unit-Tests.runfiles/_main//tests/ios/unit-test/test-imports-app/TestImports-Unit-Tests.zip
        Testing cancelled because the build failed.

The issue doesn't happen if apple.experimental.tree_artifact_outputs is set to 0.

The only two ways I was able to avoid this:

Set transition_support.apple_rule_transition as an incoming edge transition in the legacy_xcodeproj.bzl => xcodeproj rule
Set transition_support.apple_platform_split_transition as an outgoing edge transition in the same rule above for its deps attribute

Both "hacks" require the platform_type and minimum_os_version attributes to be set to something in the rule (rules_apple requirement) and I'm debating if this is even the right approach here. I doesn't make a lot of sense for the project to be opinionated on platform_type/minimum_os_version.
Given that this generator is getting more and more in "life support" mode due to most folks moving to rules_xcodeproj one might want to avoid setting apple.experimental.tree_artifact_outputs=1 when building from this generator as a workaround as I'm not convinced that its worth investing time in adjusting the rule to run well with the latest transitions related changes that landed in rules_ios recently.


Turkish Irrendentism

Having read a couple of articles on the history of Turkey I have discovered that at the time of its creation the Republic of Turkey had originally claimed territories in parts of Syria and Iraq that were outlined in the Misak-ı Millî (National Pact) in 1920 however these goals were later abandoned as by 1923 the Turkish nationalists were beginning to get overextended and the British and French force in both Syria and Iraq seemed to strong to fight against in the Turkish War of Independence. Turkey later signed the Treaty of Lausanne with France and Great Britain that recognised the sovereignty of the Turkish republic however it was forced to give up the claims to parts of Syria and Iraq except the Mosul Viyalet when Turkey continued to claim it as part of its de jure territory until 1926 when it reluctantly gave up the claims to the Mosul Viyalet in an agreement with Iraq under the supervision of the League of Nations. In recent years however with the rise of Recep Tayyip Erdoğan and his party the Justice and Development Party, Turkey has once more looked interested in claiming those regions once more or to gain influence over these areas as for example there are tensions between Turkey and Iraq on who shall control the city and what actions will be done to its inhabitants and the Rojava has recently stalled their offensive on Raqqah in protest of the continuing Turkish offensive on Raqqah.
Map of a de jrue Turkish nation as outlined in the National Pact (made by Foreign Policy magazine)

Sources
http://www.independent.co.uk/news/world/middle-east/iraq-ready-for-war-with-turkey-over-who-should-control-mosul-a7394071.html
http://www.aljazeera.com/news/2016/11/iraq-turkey-tension-rises-battle-mosul-161102062236590.html
http://foreignpolicy.com/2016/10/23/turkeys-religious-nationalists-want-ottoman-borders-iraq-erdogan/
https://www.britannica.com/topic/National-Pact-Turkey-1920
http://www.dailysabah.com/politics/2016/11/23/ypg-turns-its-back-on-us-threatens-to-shut-down-raqqa-operation-1479922147
http://foreignpolicy.com/2016/11/27/raqqa-will-put-trumps-deal-making-to-the-test/

Nice suggestion, the Turkish involvement in Iraq and Syria shows a commitment to Turkmens in the area.
https://en.wikipedia.org/wiki/Battle_of_Mosul_(2016)#Turkish_desire_of_involvement
https://en.wikipedia.org/wiki/Syrian_Turkmen#Turkish_military_intervention_in_Syria

Added a commit for this issue, however I'm keeping the Turkish irrendentism issue open is because when I had tested it, in the 1946 startdate somehow Turkey hadn't any political party leading the country and din't have any armies at all, despite all the commands in the file for both political parties and armies for Turkey.


Setup node project

Either find a suitable minimal boilerplate or create one from scratch.
To have:

express
typescript
prettier
eslint
husky

https://github.com/mjlaufer/node-postgres-starter


Implement Booking Logic with Seat Availability Verification

Create the Booking controller to verify seat availability, reserve seats, and update seat status upon confirmation.

I am interested. Pls assign this issue to me.

Hello @whoisrgxu  , I am assigning this issue to you, please stick with the contribution guidelines.


DOC: remove_node typo in runnables/ graph

URL
https://api.python.langchain.com/en/latest/runnables/langchain_core.runnables.graph.Graph.html
Checklist

[X] I added a very descriptive title to this issue.
[X] I included a link to the documentation page I am referring to (if applicable).

Issue with current documentation:
The code of the remove_node in https://github.com/langchain-ai/langchain/blob/master/libs/core/langchain_core/runnables/graph.py is as follow
 def remove_node(self, node: Node) -> None:
        """Remove a node from the graphm and all edges connected to it."""
        self.nodes.pop(node.id)
        self.edges = [
            edge
            for edge in self.edges
            if edge.source != node.id and edge.target != node.id
        ]
``` graph is spelled graphm

### Idea or request for content:

```python
 def remove_node(self, node: Node) -> None:
        """Remove a node from the **graph** and all edges connected to it."""
        self.nodes.pop(node.id)
        self.edges = [
            edge
            for edge in self.edges
            if edge.source != node.id and edge.target != node.id
        ]

Should replace graphm with graph

URL:
https://github.com/langchain-ai/langchain/pull/23910#event-13407839115
Typo has been fixed(grahm-->graph)


Fix the "Get the code of conduct for a repository" override

We have "overrides" which can add, remove or update parts of the schema.
We currently have an override which adds the "Get the code of conduct for a repository" operation to the schemas for GitHub.com, GHAE and GHES 3.2. These aren't included in the normal bundled schemas because they are marked as deprecated (and thus not to be included in documentation), but we still want to support them in Octokit for users who rely on them.
This PR introduces two changes:

Fix the example reference: We refer to a named example, code-of-conduct-2, but this is not included in current schemas, which breaks the automatic update process. This swaps out that reference to refer to plain-ol' code-of-conduct. I've done a quick comparison and the two historic files seem to be functionally identical 🤷♀
Apply the override in GHES 3.3: The "Get the code of conduct for a repository" API is included in that version as well. (It does not appear in GHES 3.4 or later.)

I'm going to run the update workflow with this branch - see here - just so we can see the output.

@timrogers @nickfloyd fyi when you edit anything in the scripts/overrides/* files, you need to run script run build afterwards in order for the generated/* files to be updated.
In order to create a new release, see https://github.com/octokit/openapi/blob/main/CONTRIBUTING.md#maintainers-only

Thanks for the heads up! I was just trying to get the automated update task running, and this was blocking it. Would it make sense for me to create a PR with the generated/ data?

I got it no worries


New button sentiment and appearance

[ ] design qa (storybook) @pseys
[ ] doc review (site preview) @dplsek
[x] changesets @origami-z
[ ] code review @joshwooding
[x] deprecate cta/primary/secondary tokens @origami-z

Replaces #3924, #3648
Implements #3325, #3325
Other related - #3971

/release-pr

The solid disabled states for caution negative and positive aren't displaying correctly in Salt Next.

The solid disabled states for caution negative and positive aren't displaying correctly in Salt Next.

fixed in a later commit


scenarios/default.js not working in v0.2.0-beta.8?

I have mirage v0.2.0-beta.8 running in an ember-cli 2.3.0 project. Everything is working fine so far, except that the scenarios/default.js is never called. So, my local database is empty.
To be clear, this is in development mode. I understand that the scenarios aren't executed for tests, as noted in #324.
Anyone else run into this with the beta?

Not a bug. Figured it out.


[BUG]: QuickSelect test case is failing

Motivation
Quick Select test case is failing due to this overall PR builds is failing.
Need to fix that !

Examples
No response
Possible workarounds
No response

Hi @appgurueu ,
I think we have to ask or assign @prisojacques to resolve this bug he added the code of quick select.
What's you views on this ?

Hi @appgurueu , I think we have to ask or assign @prisojacques to resolve this bug he added the code of quick select. and this issue should be high priority (because every PR's build are failing due to this.) What's you views on this ?

I'm not sure @prisojacques is responsible; the regressions seems to have been introduced by the switch to a random pivot selection strategy. I'll take a look when I have time.

Hi @appgurueu , I think I've managed to fix this issue in #207 . I've described in more details why I've made each respective change inside my PR. If you have some free time, I would appreciate if you can take a look over it. :blush:

Thank You @vladimir-cucu !
@appgurueu @raklaptudirm please look into this.


Create A Code Of Conduct - An Agreement To Standardize Contribution

Adding A Code Of Conduct Is Like An Agreement To Ensure There Is Acceptable Behaviour When Contributing. Also, We Need To Add Contributing Instructions(CONTRIBUTING.md).

Dude, I think your PR is not gonna be accepted because of #255


Use ocaml-uri for parsing

https://github.com/mirage/ocaml-uri

This is in the codebase now, will mark this as completed


refactor: show 4 decimals in exchanges prices

Summary
Depends on https://github.com/ArdentHQ/arkscan/pull/239
Closes https://app.clickup.com/t/862jvmvtf
Note: this pr only applies while we use usd only on the table, if we decide to change that in the future we are going to require to update the formatters so we can pass the number of decimals/handle the 0s trimming
Checklist

[ ] I checked my UI changes against the design and there are no notable differences
[ ] I checked my UI changes for any responsiveness issues
[ ] I checked my UI changes in light AND dark mode
[ ] I checked my (code) changes for obvious issues, debug statements and commented code
[ ] I opened a corresponding card on Clickup for any remaining TODOs in my code
[ ] I added a short description on how to test this PR (if necessary)
[ ] Documentation (if necessary)
[ ] Tests (if necessary)
[ ] Ready to be merged

@alfonsobries can you fix the conflicts please

@alexbarnsley ✅


💡 CIP-119 DRep metadata images, reading and writing

Area
Delegation Pillar
Is there new design needed?
Yes
What?

GovTool does not support writing or reading DRep images via CIP119 metadata
It would be good to support this

Related issue
Why?

GovTool should follow the ecosystem standards

How?

Redesign the DRep reg and update form to allow image upload
Redesign the DRep directory to show images

(Optional) User Story with acceptance criteria
As a ada holder
I want to be able to see pictures uploaded via DRep metadata
then I can more easily differentiate between DReps at delegation time

A summary of what I found when testing:

Bug: If I enter a description and not a link, the form submits anyways (should error check that a link was added for every description: https://www.loom.com/share/6cfdd4287b3a432198ee58d86d2a96c8. However, the impact is lessened by the fact that the DRep screen following doesn't display blank "description" fields: https://www.loom.com/share/94e3277dc15c4b1da2aeccc5563766e6?sid=a7565e1b-1d19-4f8d-8ca4-5a5db294e412
Four issues in this video: https://www.loom.com/share/ba7a06f37f6d4eab8f47b115121cdbdb?sid=64753f9c-49ba-41f8-87cd-0786a5f13083

The Delegate button shows on the DRep profile page, but shouldn't, as this DRep is me and I have delegated to myself
The Drep profile page should show that I have delegated my own ADA to this DRep and it does not. This page is misssing from the design file, i.e. it has not been done, and we need a new page for it.
The Dashboard shows a confusing message in the Direct Voter card. It tells me that "I can't vote", but this is not true, as I can vote, just not as a Direct Voter. This needs addressing as a design issue as well. In total, we need to construct a table of what Dashboard card says what in all the possible scenarios.
On the Dashboard, inside the DRep card, the DRep name is missing.

Confusing interface due to a design decision: https://www.loom.com/share/4c974de0c8f143a98529e663f78091c9?sid=22bdf60b-4ca7-4081-a8fb-d13114b92f33
I've just delegated to a DRep, but the DRep's Voting power says Zero. I know we decided to only assess DRep Voting Power at epoch boundaries, but this video shows how that decisions negatively impacts the experience. Most users will think there is a bug in the system, as their chosen DRep's Voting Power is expected to increase by the value of their delegation. I can't imagine that many people will want to wait to the epoch boundary to see if their VP has been included.

In the same video, the DRep name is missing from the Drep list

Voting Power messages again confusing in Dashboard: https://www.loom.com/share/5bd75cc661a84236ab06ac497a13fbb6?sid=dc557dd7-9f0a-4b80-9061-3e21f7270435

Changing to Direct Voter from Delegate shows you are still delegated on Dashboard, until manual refresh https://www.loom.com/share/5e41d840076e4951bd7d9590b77f3d89?sid=19e66599-e5a5-4649-8d47-f8baf74f3408 See Video!

Changing to DRep from Direct Voter shows that I'm 'retired' as Direct Voter. This is confusing. https://www.loom.com/share/3adf3e0a93bf42d1ba1a38ef23920ae9?sid=2a7610dd-0446-4673-bf35-32b3d7ed42a4

@m-i-k-e Would it be okay to fix these bugs while implementing the support for DRep images? Or should we split your comment into separate issues and fix it under the scope of these new issues?

This is ready for dev: https://www.figma.com/design/mJTBiUofLfb74Xc3W2U59o/Voltaire---GOV-TOOL?m=auto&node-id=16430-148267&t=8SB5qkNrX94NfBO6-1


Firestore grpc crashes

Step 1: Describe your environment

Xcode version: 13.3.1
Firebase SDK version: 8.15.0
Installation method: CocoaPods
Firebase Component: Firestore
Target platform(s): iOS

Step 2: Describe the problem
Steps to reproduce:
This crash appeared after updating to 8.15.0
Possibly related to https://github.com/firebase/firebase-ios-sdk/issues/9258
We can not reproduce it on our side in debug mode, but see these crashes in production in Crashlytics dashboard.
Relevant Code:
Stack Trace:
Crashed: com.google.firebase.firestore.rpc
0  grpc                           0xc0038 grpc_core::ParsedMetadata<grpc_metadata_batch>::KeyValueVTable(absl::lts_20211102::string_view)::'lambda'(grpc_core::Slice*, absl::lts_20211102::FunctionRef<void (absl::lts_20211102::string_view, grpc_core::Slice const&)>, grpc_core::ParsedMetadata<grpc_metadata_batch>*)::__invoke(grpc_core::Slice*, absl::lts_20211102::FunctionRef<void (absl::lts_20211102::string_view, grpc_core::Slice const&)>, grpc_core::ParsedMetadata<grpc_metadata_batch>*) + 137 (slice_refcount_base.h:137)
1  grpc                           0xc04e0 grpc_core::ParsedMetadata<grpc_metadata_batch>::WithNewValue(grpc_core::Slice, absl::lts_20211102::FunctionRef<void (absl::lts_20211102::string_view, grpc_core::Slice const&)>) const + 184 (parsed_metadata.h:184)
2  grpc                           0xb926c absl::lts_20211102::optional<grpc_core::ParsedMetadata<grpc_metadata_batch> > grpc_core::HPackParser::Parser::ParseIdxKey<grpc_core::HPackParser::String::Intern>(unsigned int) + 1145 (hpack_parser.cc:1145)
3  grpc                           0xb813c grpc_core::HPackParser::Parser::Parse() + 1004 (hpack_parser.cc:1004)
4  grpc                           0xb7f04 grpc_core::HPackParser::ParseInputInner(grpc_core::HPackParser::Input*) + 1334 (hpack_parser.cc:1334)
5  grpc                           0xb7da8 grpc_core::HPackParser::ParseInput(grpc_core::HPackParser::Input, bool) + 1308 (hpack_parser.cc:1308)
6  grpc                           0xb7adc grpc_core::HPackParser::Parse(grpc_slice const&, bool) + 1302 (hpack_parser.cc:1302)
7  grpc                           0xb84c8 grpc_chttp2_header_parser_parse(void*, grpc_chttp2_transport*, grpc_chttp2_stream*, grpc_slice const&, int) + 1381 (hpack_parser.cc:1381)
8  grpc                           0xf53a4 parse_frame_slice(grpc_chttp2_transport*, grpc_slice const&, int) + 626 (parsing.cc:626)
9  grpc                           0xf4f44 grpc_chttp2_perform_read(grpc_chttp2_transport*, grpc_slice const&) + 228 (parsing.cc:228)
10 grpc                           0x48374 read_action_locked(void*, grpc_error*) + 2415 (chttp2_transport.cc:2415)
11 grpc                           0x64e34 grpc_combiner_continue_exec_ctx() + 259 (error.h:259)
12 grpc                           0x884c4 grpc_core::ExecCtx::Flush() + 167 (exec_ctx.cc:167)
13 grpc                           0x84ee4 pollset_work(grpc_pollset*, grpc_pollset_worker**, long long) + 1096 (ev_poll_posix.cc:1096)
14 grpc                           0x86a10 pollset_work(grpc_pollset*, grpc_pollset_worker**, long long) + 323 (ev_posix.cc:323)
15 grpc                           0x69da0 cq_next(grpc_completion_queue*, gpr_timespec, void*) + 1047 (completion_queue.cc:1047)
16 grpcpp                         0x1a46c grpc::CompletionQueue::AsyncNextInternal(void**, bool*, gpr_timespec) + 147 (completion_queue_cc.cc:147)
17 FirebaseFirestore              0x2d89c firebase::firestore::remote::Datastore::PollGrpcQueue() + 141 (datastore.cc:141)
18 FirebaseFirestore              0x13422c firebase::firestore::util::Task::ExecuteAndRelease() + 491 (function.h:491)
19 libdispatch.dylib              0x3db0 _dispatch_client_callout + 20
20 libdispatch.dylib              0xb10c _dispatch_lane_serial_drain + 580
21 libdispatch.dylib              0xbc5c _dispatch_lane_invoke + 408
22 libdispatch.dylib              0x15d78 _dispatch_workloop_worker_thread + 708
23 libsystem_pthread.dylib        0x3804 _pthread_wqthread + 276
24 libsystem_pthread.dylib        0xa75c start_wqthread + 8

Hi igorvoytovich. Thank you for logging this issue. The good news is that, based on the fix for https://github.com/firebase/firebase-ios-sdk/issues/9258 fixing your original problem, this crash probably only happens while the application is shutting down. So hopefully your customers aren't witnessing your app crashing. Next week I'm planning to do an audit of our entire source to fix this sort of crash during application termination. That effort may fix this crash as well. If it does, great! The bad news is that if it doesn't we don't have bandwidth to investigate further at this time due to competing priorities. I'll be sure to post back here whatever I find and will keep you updated, even if that update is "sorry, we cannot investigate at this time".

Hi @dconeybe ,
Thank you very much for such a quick response!
If you need any more information, code examples or anything from me, please let me know.
Have a nice day!

I just merged https://github.com/firebase/firebase-ios-sdk/pull/9885, which may fix this crash. This fix won't make it into the next release, but should make it into the release after that (roughly mid-July 2022). Once that release comes out, please upgrade and reply back as to whether or not you're still experiencing this crash.

This release was now published. @igorvoytovich can you please update and reply back if you still experience this crash?

Hello @dconeybe @ryanwilson,
We just updated to 9.3.0 and have a new crash now. Here is  the stack trace:

We won't ship the 9.3.0 version yet because of it.
Could you please tell if we should create another issue for this one?
Thanks.

@igorvoytovich That new crash is a known issue that we're actively investigating: https://github.com/firebase/firebase-ios-sdk/issues/9985. If you end up finding a reproducible scenario please let us know since the lack of one is making it incredibly difficult to investigate.
Since it sounds like the originally-reported crash is fixed, I'm going to close this issue. But feel free to comment if you disagree or if the crash resurfaces with 9.3.0 or later. Thanks!