Update icons sizes in react components

All icon sizes was updated to be 24x24 (from 16x16) in Figma in issue #189, but we forgot to update the sizes in our react components...
With compact we see now that some icons are actually better fit to be 16x16 in those use-cases.
Actions

Do a review on which components should be 24x24 and 16x16.

Adjustments:
Textfield:

Comfortable Input icon: 24px
Helper icon: 16px
Compact input icon: 16px

Search:

Icons 24px

Accordion:

Cheveron icon: 24px


Support !Unpin option

Provide an equivalent to pin-project's !Unpin option.
See https://github.com/tokio-rs/tokio/issues/5901 for the context.

Hi! I would like to take a look at this!


[9.x] Short attribute syntax for Blade Components

This PR implements Caleb's proposal to optionally allow a shorter syntax for passing attributes to Blade Components.
<!-- current syntax -->
<x-profile :user-id="$userId"></x-profile>

<!-- short syntax -->
<x-profile :$userId></x-profile>

<x-profile :$userId />

it seems like it doesn't work for anonymous component (component with only a Blade template and no class)

It does work for anonymous components, but only for non-self-closing notations.
E.g.:
<!-- works... -->
<x-profile :$userId></x-profile>

<!-- broken... -->
<x-profile :$userId />

is there a reason it doesn't work for self-closing ?

See https://github.com/laravel/framework/pull/44413


2727: Search result pois events missing

Short description
Currently for async search not all search results were found with minisearch. The issue is that the indexing was not ready when the query was typed and missing results were not reloaded.
Proposed changes

reload search results when indexing has finished

Side effects

during typing search query the search results change but if we want it async/non blocking, i think we can't find a better solution

Resolved issues

Fixes: #2727
Testing

Go to a location
open the search and type in immediately your search query. All results should be shown

😍 Thanks for the quick fix! I couldn't reproduce the original issue, unfortunately, but it looks right. Would be good for someone with an Android device to check as well, though. Checked on emulated Android and real iOS

checked on android.

On web it flickers if you have a preset query:
http://localhost:9000/kaiserslautern/de/search/?query=krab
I guess this is because we are not waiting for every request to finish in useAllSearchResults as e.g. in this case for me the pois are ready first, minisearch is searching, doesn't find anything, events are added and then there are results. Might be acceptable though (or be done in a spearate issue).
Didn't experience any other issues though. Tested on firefox and android.
However, I was also not able to reproduce the original issue.

Probably that flickering causes the errors on e2e Web Tests :/

On web it flickers if you have a preset query:
http://localhost:9000/kaiserslautern/de/search/?query=krab
I guess this is because we are not waiting for every request to finish in useAllSearchResults as e.g. in this case for me the pois are ready first, minisearch is searching, doesn't find anything, events are added and then there are results. Might be acceptable though (or be done in a spearate issue).
Didn't experience any other issues though. Tested on firefox and android.
However, I was also not able to reproduce the original issue.

Probably that flickering causes the errors on e2e Web Tests :/
Update: There are also some type errors in useAllPossibleSearchResults that should be refactored
I don't have time today for this

Looking into it.

@f1sh1918 opened a PR to fix the flickering. Basically the problem occurs because minisearch is now initialized asynchronously. So the search results are available first, but minisearch has to be initialized after and that takes at least one render. During that time, minisearch is initialized with only some of the possible search results (e.g. just pois). Therefore we have to check if minisearch.documentCount === allSearchResults.length. See #2730.


Esperanto docs

I did the Esperanto documentation translation like I said. This is my first time really using GitHub for something like this (doing a pull request and all this) so I apologise if I did that improperly. But I believe the Esperanto documentation is good to go!

Pull Request Test Coverage Report for Build 166

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.03%) to 96.146%

Totals

Change from base Build 154:
-0.03%

Covered Lines:
278

Relevant Lines:
282

💛  - Coveralls


Add Rendering

Show the fighters fighting and some statistics.

Starting to learn the MonoGame Framework. New commit probably will take a while

Basic rendering is being added. Will be split into smaller issues from now on


Proposed changes for adding type checking to RPTSET parameter list values

This PR adds proposed type checking for RPTSET parameter list values.
@BrianSipos please advise if you would prefer to go a different route with this.

This PR adds proposed type checking for RPTSET parameter list values.
@BrianSipos please advise if you would prefer to go a different route with this.

If possible, it could be better to use amm_type_convert(amm_type_get_builtin(ARI_TYPE_TP)) and similar to make conversions here rather than requiring one strict form for the inputs. With the status result from the conversion used to determine whether the input is valid.
Do you mind prototyping this? And if it works the commit could be added to this PR.

@BrianSipos Added prototype commits for TD/TP (call roll back from PR if needed). What do you think?

@BrianSipos This is ready when you have a chance to take another look. Do have one outstanding question above regarding ari_set_move and ari_deinit.

@BrianSipos Addressed comments from your latest review. Please let me know if you have more questions/concerns.

@BrianSipos Addressed comments from your latest review. Please let me know if you have more questions/concerns.

This is not a code issue but I notice your text ARIs in C comments have bad syntax. The two slash "ari://" is for object reference values not literal values.

@BrianSipos Addressed comments from your latest review. Please let me know if you have more questions/concerns.

This is not a code issue but I notice your text ARIs in C comments have bad syntax. The two slash "ari://" is for object reference values not literal values.

Good catch! Alright, that does it for the outstanding issues on this one.


update readme and main page of docs

@arnauqb this comment is in reference to JOSS review: https://github.com/openjournals/joss-reviews/issues/5776
It would be useful to have a set of commands in the readme on unit tests. For example, what test should someone run on their computer (and how) to make sure that the program is installed correctly?

I second this: Please add information on running the unit tests.

I've added a section on how to run the tests in the main readme and a pointer to the contributing guidelines.


Autocomplete and page scroll

Bug, feature request, or proposal:
Bug
What is the expected behavior?
Autocomplete options should stay near input
What is the current behavior?
Autocomplete options don't change css top property when we scroll on the page.
After scroll autocomplete options don't follow the input position.
What are the steps to reproduce?
https://plnkr.co/edit/I2TAghRrpbzmgQK5SsXd?p=preview
I use the material Docs plunker and add some fake scroll, to reproduce the problem.

None of the Overlay utilising components does. There's a PR for a solution that will block scrolling while any overlay is open, but https://github.com/angular/material2/pull/1971 either there's some problem with it or the assignee is busy.

I got around it by sticking a scroll dispatcher on the body and updating the position manually as the user scrolls, but there are some issues on iOS safari with fixed positioning when the keyboards open.

@fxck would you mind sharing the code that fix it ? having the same issue here

It is perhaps a naive implementation but it seems like a stacking context would be one solution. What don't I get about what the overlay is providing?

Now tracking via #4093


[🐞] server actions can't test in stackblitz.com

Which component is affected?
Starters / CLI
Describe the bug
Doing:
Trying to test the behaviour of server actions using Qwik Starters.
And run() the action when a button is clicked.
Expect:
No problems happen.
Happening:
ErrorResponse: Cross-site POST form submissions are forbidden
    at error (file:///home/projects/qwik-starter-3dlk16/node_modules/@builder.io/qwik-city/vite/index.cjs:24019:14)
    at securityMiddleware (file:///home/projects/qwik-starter-3dlk16/node_modules/@builder.io/qwik-city/vite/index.cjs:23773:11)
    at Object.next (file:///home/projects/qwik-starter-3dlk16/node_modules/@builder.io/qwik-city/vite/index.cjs:23918:22)
    at runNext (file:///home/projects/qwik-starter-3dlk16/node_modules/@builder.io/qwik-city/vite/index.cjs:24150:21)
    at runQwikCity (file:///home/projects/qwik-starter-3dlk16/node_modules/@builder.io/qwik-city/vite/index.cjs:24145:17)
    at eval (file:///home/projects/qwik-starter-3dlk16/node_modules/@builder.io/qwik-city/vite/index.cjs:24546:45) {
  status: 403
}

Reproduction
https://stackblitz.com/edit/qwik-starter-3dlk16?file=src/routes/index.tsx
Steps to reproduce
Go to the link above and click the button in the page.
System Info
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 16.14.2 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 7.17.0 - /usr/local/bin/npm
  npmPackages:
    @builder.io/qwik: ^0.20.1 => 0.20.1
    @builder.io/qwik-city: ^0.5.2 => 0.5.2
    undici: ^5.16.0 => 5.20.0

Additional Information
No response

@manucorporat
I'm still getting the same error on<EMAIL_ADDRESS>and<EMAIL_ADDRESS>Reproduction
I just forked the original Stackblitz linked above and upgraded the dependencies:
https://stackblitz.com/edit/qwik-starter-wc56yu?file=package.json
Clicking the button still fails with ErrorResponse: Cross-site POST form submissions are forbidden

I am experiencing this issue w RC1 as well. How do you call server$ in StackBlitz without the Cross-site error?
Header forwarding (like in railway), .env or vite.config.ts origin?
@mhevery / @manucorporat, it looks like a fix was made but not sure what needs to be done here.

So one thing in regards to this issue is that this check was added on the Qwik side. However, for me, the isDev is always false on StackBlitz.com. This flag comes from somewhere in the build process I assume but couldn't find out why it's false.
If this was fixed, an other error pops up which is on our (StackBlitz) side in regards to transferring ReadableStream.

I have the same issue here
I'm using
<EMAIL_ADDRESS>"^0.100.0",
<EMAIL_ADDRESS>"^0.100.0",
And it's not working locally, with no error response or anything. And on Stackblitz I'm getting ErrorResponse: Cross-site POST form submissions are forbidden

I found the issue with the isDev method. This only happens when the build uses the CJS bundles of Qwik.
The isDev constant is an IIFE, which means that isDev is set to whatever globalThis.qDev is at the point the function is invoked. Whenever this is invoked the very first time, globalThis.qDev always is undefined in case of CJS.
A little bit later, the code block that sets globalThis.qDev gets executed. But at that point in time, it's already too late as isDev is already evaluated and set to false.
As mentioned, this only happens with the CJS bundle of Qwik (which is what's being used on StackBlitz for some reason, have to find out why). Here's a screenshot showing the order of execution.

On local however, the build uses the ESM bundles. The order of execution is different.

So this is an issue with CJS, but maybe also an issue with StackBlitz because it should use the ESM bundles 🤔 .


2024 update and tags?

Hi,
thanks for this template, I plan to use it this year.
Please, can anybody confirm that it is up to date for 2024 call?
Also, in this year docx template there are some tags that should be kept. Should they be added?

Hi! Thank you for your interest :grin:

Please, can anybody confirm that it is up to date for 2024 call?

I've updated the template to contain the changes from the 2024 guide (from here). They're listed on page 25.
I've skimmed the actual template a bit for any other changes and couldn't find anything, but this wasn't done very carefully, so might have missed something.

Also, in this year docx template there are some tags that should be kept. Should they be added?

I can't speak for this year, but in 2022 when I submitted this, they didn't comment on any lack of tags. The best way forward might be to ask someone -- there's a list of support points on the Funding & Tenders portal.

FYI, this is what the guide says about the tags
This document is tagged. Do not delete the tags; they are needed for our internal
processing of information, mostly for statistical gathering. In that light, please
do not move, delete, re-order, alter tags in any way, as they might create problems
in our internal processing tools. Tags do not affect or influence the outcome of
your application.

Hi, I'm glad I found this repo and am going to use it! I love LaTeX. However, I'm also worried about the tags.
So, you meant the tags were also in the official .rtf template in 2022, correct? Anyway, you still used this LaTeX template and didn't receive the comment? @alexfikl
Best wishes!

A quick update:
I found this discussion. It says that adding the tags is highly recommended.
@alexfikl  @Gldkslfmsd

Hi, I'm glad I found this repo and am going to use it! I love LaTeX.

Thank you for your interest!

However, I'm also worried about the tags. So, you meant the tags were also in the official .rtf template in 2022, correct?

Hm, I might have misremebered that. You can check in the official manual on page 25. It says there that version 2.0 of the template updated on 11.07.2022 added tags, but that was after the 2022 submission deadline..
I'll try to add the tags to the document this weekend. PRs are very welcome if you get to it before then. It should be as easy as adding some gray text at the end of some of the section titles.

Hm, I might have misremebered that. You can check in the official manual on page 25. It says there that version 2.0 of the template updated on 11.07.2022 added tags, but that was after the 2022 submission deadline..

I'm apparently bad at reading dates right now, sorry for the confusion!
11.07.2022 is before the submission deadline in September, so the template did have tags even then, as initially stated :grin:

Hi, I'm glad I found this repo and am going to use it! I love LaTeX.您好，我很高兴找到这个存储库并将使用它！我喜欢乳胶。

Thank you for your interest!感谢您的关注！

However, I'm also worried about the tags. So, you meant the tags were also in the official .rtf template in 2022, correct?不过，我也担心标签。那么，您的意思是这些标签也在 2022 年的官方.rtf模板中，对吗？

Hm, I might have misremebered that. You can check in the official manual on page 25. It says there that version 2.0 of the template updated on 11.07.2022 added tags, but that was after the 2022 submission deadline..嗯，我可能记错了。你可以查看官方手册第25页。上面说模板的2.0版本于2022年7月11日更新，添加了标签，但那是在2022年提交截止日期之后。
I'll try to add the tags to the document this weekend. PRs are very welcome if you get to it before then. It should be as easy as adding some gray text at the end of some of the section titles.本周末我将尝试将标签添加到文档中。如果您在此之前获得 PR，我们非常欢迎。它应该像在某些部分标题的末尾添加一些灰色文本一样简单。

Great to know! I will first format my proposal draft using this template. If you don't have spare time to add the tags by then, I'd like to start a PR to do so. Thanks for your incredible contribution again!

Hi, I'm glad I found this repo and am going to use it! I love LaTeX.

Thank you for your interest!

However, I'm also worried about the tags. So, you meant the tags were also in the official .rtf template in 2022, correct?

Hm, I might have misremebered that. You can check in the official manual on page 25. It says there that version 2.0 of the template updated on 11.07.2022 added tags, but that was after the 2022 submission deadline..
I'll try to add the tags to the document this weekend. PRs are very welcome if you get to it before then. It should be as easy as adding some gray text at the end of some of the section titles.

Great to know! I will first format my proposal draft using this template. If you don't have spare time to add the tags by then, I'd like to start a PR to do so. Thanks for your incredible contribution again!

@SongshGeo I've added tags in the latest version (see 0c368492aa8ee1f6c1a1a0cb92a164074a1fdfef). Let me know if you spot any errors!
Unfortunately, the official manual is a bit confusing with the tags. The documented template starting on page 30 has slightly different tags than the empty template starting at page 40 (e.g. the QUA-LIT-QL tag is in a different place). I went with the empty template here, since that should be the one most people will start with.

@SongshGeo I've added tags in the latest version (see 0c36849). Let me know if you spot any errors!
Unfortunately, the official manual is a bit confusing with the tags. The documented template starting on page 30 has slightly different tags than the empty template starting at page 40 (e.g. the QUA-LIT-QL tag is in a different place). I went with the empty template here, since that should be the one most people will start with.

@alexfikl  Hi, I'm glad to be notified! How active you are, Thanks!
I will double-check it when I compile my proposal. :)

@alexfikl
I'm sorry that I forgot to follow up on this issue for a while. I was busy with submission.
The improved package was good. I double-checked the tags one by one before the submission. I indeed changed some tags (I forgot which are the specific ones), but it's super simple by using the latest "mscatags" macro. So, I think this package works very well overall. Thanks for your efforts on this.
BTW, I use markdown for drafting and export the .md to .tex. For this, I created a Lua filter to add the tags automatically. I'd love to share if anyone uses a similar workflow and wants this function.

I double-checked the tags one by one before the submission. I indeed changed some tags (I forgot which are the specific ones), but it's super simple by using the latest "mscatags" macro. So, I think this package works very well overall. Thanks for your efforts on this.

Glad it works for you! Best of luck with your submission :tada:


Create PR to intergrate SubWallet into web3-onboard

PR: https://github.com/blocknative/web3-onboard/pull/1875

The pull request has been merged => Closed issue


Make search route respond to query parameters

Current handled parameters are: q, state, and page, maybe more. E.g.: https://petitions.moveon.org/find/?q=taxes&state=CO&page=2
This is currently blocked on https://github.com/MoveOnOrg/mop/issues/48
See also #42.

Even though this is attached to https://github.com/MoveOnOrg/mop/pull/56, which is why it's blocked, I can still get started on this issue.


Game crashing randomly while playing

Whenever I play, after a certain amount of time, my game crashes via my "internet." I know it isn't my internet becuase of how many times it does this. Could someone look into it?

Is this in all Adonis games or just a single game using Adonis

I'm having the same issue but it doesnt seem to be adonis causing it. Check script activity of the scripts


Terraform Issue Apacheserver

In creating simple terraform for apache server showing below error in main.tf
PS C:\Practice\Terraform> terraform validate .
Error: Missing required argument
on main.tf line 13, in resource "aws_instance" "hello":
13:    connection {
The argument "host" is required, but no definition was found.
connection {
type = "ssh"
user = "ec2-user"
private_key = "${file("./terraform.pem")}"
}
Always showing error for HOST in connection so I put their host = "self.public_ip"
But then machine creating in loop please suggest

also tried      host = "${aws_instance.hello.public_ip}" then its showing

please mention host

connection {
type = "ssh"
user = "ec2-user"
private_key = "${file("./terrafo.pem")}"
host = "${aws_instance.hello.public_ip}"
}
This one works for me thanks


Invalid argument(s): The "any" argument matcher is used outside of method stubbing (via when) or verification (via verify or untilCalled). This is invalid, and results in bad behavior during the next stubbing or verification.

class FakeRequest extends Fake implements RequestOptions{}

setUp((){
registerCallback(FakeRequest())
});

test("should fetch customer info", () async {
    // arrange
    when(() => mockDioClient.get(any())).thenAnswer(
      (_) async => Response(
        data: fixture("customer_fixture.json"),
        requestOptions: any(),
        statusCode: 200,
      ),
    );

    // act
    var result = await profileRemoteDataSourceImpl.getCustomerInfo();

    // assert
    expect(result, testCustomerModel);
    verify(() => mockDioClient.get(Urls.getCustomerInfo));
    verifyNoMoreInteractions(mockDioClient);
  });

Hi @raxahai 👋
Thanks for opening an issue! If you're still having trouble with this can you please share a link to a minimal reproduction sample? It's much easier for me to help if I'm able to reproduce the issue locally, thanks!

Closing for now since this issue is quite old and there isn't a minimal reproduction sample. If this is still a problem please file a new issue with a link to a reproduction sample, thanks!


Default Plotting Parameters

So far there is a plotting_style.yaml file with defaults.
But in the Style Class there are some defaults set as well.
it would be better to:

define all parameters in the yaml file
load the default yaml file in the Style Class
overwrite parameters set in user plotting config

solved in #256


"Băjănești" is listed in the drop-down menu

Description:
"Băjănești" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Băjănești" in the search bar.

Expected results
The location is listed in the drop-down menu as "Băjănești, Argeș (Băbana)".


Form group margin bottom

https://github.com/ovh-ux/ovh-ui-kit-bs/blob/edb2484f4601aa6b044bc458469e81b25d98404d/src/bootstrap/_variables.less#L219
The margin-bottom should be 20px just like oui-field's margin-bottom

This issue has been fixed with https://github.com/ovh-ux/ovh-ui-kit-bs/releases/tag/v1.1.2


angular7-example-app to 7.0.76

Promote angular7-example-app to version 7.0.76

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

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


Improve checks for dtype and shape in dask.array

The testing functions in numpy broadcast their arguments, which was
silently ignoring some bugs in dask.array. This tightens up those
checks, and fixes the bugs that appeared. Summary:

Fix repr bug with empty arrays
Ensure that dtype is passed through in reductions (Fixes #1394).
Turns out bool(np.dtype(...)) is always False (not what I would
expect).
residuals in da.linalg.lstsq returns an array of shape (1,)
instead of a scalar.
da.array.Array._finalize([]) returns an empty array instead of a
scalar with uninitialized memory.

Awesome! Looks like this still needs a regression test for #1394?

The changes to assert_eq to check dtype (and the change to use assert_eq) catch it (I verified).

@jcrist Oh, awesome. Very elegant fix :).

:). Merging now.


⚠ ClamAV has degraded performance

In 402d807, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 568 ms

Resolved: ClamAV performance has improved in 4b69366.


Sample Rosbag

Could you please provide the Rosbag you prepared the demos with?

Any updates on this? This would make the setup much less horrible =D


bug: accessing kubeflex controlplane from within a pod

Describe the bug
I can use your help in accessing a kubeflex controlplane from within a pod.  This is what I have done: (1) kflex init --create-kind on a kind cluster which created the kubeflex kind cluster.  I then created a pod from within kubeflex core cluster (i.e. the kind cluster named kubeflex created in step 1) and issued (2) kflex create cp1 from within.  I can now access cp1 externally using the admin-kubeconfig secret.  But I am not able to access cp1 from within the pod running in the kubeflex core cluster.  Using the cm-kubeconfig points to the same url as admin-kubeconfig and that's not visible from the pod.  I tried using the ingress-nginx that kubeflex created and that didn't help either.  If you happen to have 30min to sit with me on this, I would greatly appreciate it. (edited)
Steps To Reproduce
See above.
Expected Behavior
See above.
Additional Context
No response

Thanks @effi-ofer for opening the issue. I can replicate the issue and see that the generated URL in the cm-kubeconfig is indeed server: https://cp1.localtest.me:9443.

Thanks @pdettori.  If you can tell me what's the proper url, I'll be able to continue while you resolve the code.

I have also realized that the cm-kubeconfig has just the set of permissions required by the subset of controllers run by the kube controller manager. For this reason, there are actually 3 different kubeconfigs:

admin kubeconfig with external URL
admin kubeconfig with cluster internal URL
Controller Manager kubeconfig with cluster internal URL.
For your usage you'd actually need 2. One option is to add another key to the secret admin-kubeconfig for that, would that work for your use case?

That would work for me.  Also, I tried your url suggestion and it worked.  Thank you again.


Correction for raw affiliation Centre Hospitalier Universitaire de Rennes [CHU Rennes] = Rennes University Hospital [Ponchaillou] (2 Rue Henri le Guilloux, 35000 Rennes - France); MOBIDIC - Microenvironment and B-cells: Immunopathology,Cell Differentiation, and Cancer (Université de Rennes - France)

Correction needed for raw affiliation Centre Hospitalier Universitaire de Rennes [CHU Rennes] = Rennes University Hospital [Ponchaillou] (2 Rue Henri le Guilloux, 35000 Rennes - France); MOBIDIC - Microenvironment and B-cells: Immunopathology,Cell Differentiation, and Cancer (Université de Rennes - France)
raw_affiliation_name: Centre Hospitalier Universitaire de Rennes [CHU Rennes] = Rennes University Hospital [Ponchaillou] (2 Rue Henri le Guilloux, 35000 Rennes - France); MOBIDIC - Microenvironment and B-cells: Immunopathology,Cell Differentiation, and Cancer (Université de Rennes - France)
new_rors: 015m7wh34;05qec5a53;05p7fmf80
previous_rors: 015m7wh34;05qec5a53
works_examples: W4380203720;W4363644375;W4386485634;W4313424448;W4389230216
contact: e3da202637256e1c2c35b79be23e2fe8:216b2a20464ba5e9b7468302c05e5849 @ univ-rennes.fr

This issue was accepted and ingested by the OpenAlex team on 2024-10-10. The new affiliations should be visible within the next 7 days.


<< No band/DOS file to parse >>

Hello @sozykinsa ,
First, thank you very much for your program!
I have a question. Which file should I load in order to get the bands/dos or even the optimization evolution? Loading the OUT file returns "File format error. The format of this file is not supported".
I am calling GUI4DFT from inside the folder were the SIESTA output files are. The installation files of GUI4DFT are in other folder.
My system is running Ubuntu 21.04 64 bits.
Regards,
Camps

Thank you for your interest in my program. You are right and you need to open the OUT file. Please send (here or by e-mail<EMAIL_ADDRESS>me an example of a OUT file that causes the mentioned error.

Here is one of the outputs.
BN+CdM4-1Dlinear.zip

The problem was that some of the input parameters were not displayed in the input file (for example, MD.TypeOfRun). I rewrote the program a bit and everything should work now. Check the latest version of the program.
I hope you find my program useful.

Now it works! Thank you.
Note: I use the info about the calculation parameters in an external file as I have several system, this was the way I found to make no mistake on them.


Spec tooling and specs

Added tooling so that we can generate specs from our schema, so that our spec'ing process starts with updating the schema first, leading to less errors and mistakes in the end :)
In schemas\src, add your new properties/elements to the schema

3. Generate the updated spec
If you followed the setup instructions, simply save the file and the spec will be updated! Add any necessary rendering details to the spec.

Review spec
Submit a pull request for your updated spec/schema. The proposed schema in the proposal becomes outdated and should be replaced with a link to the PR.

I'll share more details about this at Monday's meeting. Lots of details about the new proposed spec'ing process are captured here: https://github.com/microsoft/AdaptiveCards/wiki/Project-Management
Microsoft Reviewers: Open in CodeFlow

this is AWESOME! thanks @andrewleader


master and worker nodes fail to run Ignition after installation of CoreOS

Hi, i opened this bug erroneously in ocp4-upi-powervm:
https://github.com/ocp-power-automation/ocp4-upi-powervm/issues/216#issue-934904866

found the root cause of this issue - it's because we're using an unusal network configuration.
We have configured to ibmveth VLANs - one is attached to a a SEA and extends the lab network, the other one (configured with a private IP range) is isolated. We created a LPAR which has two ibmveth adapters for each VLAN configured and we use this machine as a router. Unfortunately, if TCP packages are routed through ibmveth adapters, the RX and TX checksums are broken. So TCP connections cannot be established between the two networks. This can be mitigated by running the "ethtool -K rx off tx off" command - it switches off checksum creation and TCP works fine.
But we did not find a way to automate this when we install CoreOS - so we're able to set up the bootstrap machine, but than bootstrap fails to fetch all arbitrary data - like docker files etc. The other nodes (master and workers) will receive empty data instead from the bootstrap node:
1784.746250] ignition[1248]: GET error: Get "https://api-int.bignumbers-01.saphana.example.com:22623/config/master": EOF
[ **] A start job is running for Ignition (fetch) (29min 46s / no limit)[ 1789.746774] ignition[1248]: GET https://api-int.bignumbers-01.saphana.example.com:22623/config/master: attempt #361
Closing this as a bug - maybe there is a chance to set up CoreOS with such special device settings, but i didn't found any description how to do this.


Provided method for Linux is not working as per examples

Trying to run some az pipeline commands.  First tried using the AzureCLI task but that did not work due to authentication so found this.
This process also does not work with:
WARNING: Failed to store PAT using keyring; falling back to file storage.
WARNING: You can clear the stored credential by running az devops logout.
WARNING: Refer https://aka.ms/azure-devops-cli-auth to know more on sign in with PAT.
When taking the Linux code exactly as is.
Used `ubuntu-latest' and then tried ubuntu-16.04 like documentation stated same result.

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

ID: f9480b69-ca1f-55bc-8505-49c51d9f205e
Version Independent ID: 03df29bf-108d-6ffc-bb3e-b29fb8a1e46c
Content: Azure DevOps CLI in Azure Pipeline YAML - Azure DevOps
Content Source: docs/cli/azure-devops-cli-in-yaml.md
Product: devops
Technology: devops-reference
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

Any update on this?  I am trying to use this method as a way to lever az pipeline commands since it seems they are not natively working with the Azure CLI task https://github.com/Azure/azure-cli-extensions/issues/2935#issuecomment-770909291

@JFolberth - I've contacted the product team to alert them to this issue. You might want to post your problem on  our Developer Community page. YOu may get a solution to your specific problem faster.

@JFolberth - I'm going to close this issue for now. I will continue to work with the product team to update the article to clarify the problems you are having.

@KathrynEE  Please don't close this as it has been recognized as an issue in the community forums. https://developercommunity.visualstudio.com/t/Unable-to-run-az-pipeline-commands-withi/1329403

@JFolberth - reopening.

@JFolberth I found that I can eliminate the warnings by skipping az devops login and instead use the AZURE_DEVOPS_EXT_PAT environment variable, which is known to Azure DevOps CLI extension, like this:
- bash: |
    az pipelines build list
    git pr list
  env:
    AZURE_DEVOPS_EXT_PAT: $(System.AccessToken)
  displayName: 'Show build list and PRs'

I'm still gathering more information and will report back.

#assign steved0x

Hey @steved0x  the issue it appears is azure devops commands won't work with ADO azure hosted agents. Here is a the community ticket I opened up.
https://developercommunity.visualstudio.com/t/Unable-to-run-az-pipeline-commands-withi/1329403
What I am trying to do in a pipeline is access ADO variable groups programmatically but both the CLI commands and native Powershell commands won't authenticate appropriately.

Hey @steved0x  Any luck or update on this one?

I was able to run some variable groups commands (list) in my pipeline and I saw this note in the pipeline run details for that step:

WARNING: Command group 'pipelines variable-group' is in preview and under development. Reference and support levels: https://aka.ms/CLI_refstatus

If you are having trouble with Azure DevOps CLI and variable groups, it may be a result from this?
I have updated the article to show using the AZURE_DEVOPS_EXT_PAT approach which does not give any wanrings on Linux hosted agents, vs piping the PAT into az devops login. I believe the warnings are coming from the different ways that the linux agents are attempting to persist the context for the login across different steps, and I believe it falls back to an alternate storage mechanism. I get the same thing when running az devops commands in Azure Cloud Shell.
I was able to retrieve the variable group id of a variable group (in my example the group is named Fabrikam-2021 by using the following. My approach is a little different, I embedded the name of the variable group vs retrieving it from a parameter, and since my query only returns 1 variable group, I can get the id using [].id vs using the name like in your example. If your command is running locally but not in the pipeline, you could change your variable assignment to use this syntax:
- bash: echo "##vso[task.setvariable variable=variableGroupId]$(az pipelines variable-group list --group-name Fabrikam-2021 --query [].id -o tsv)"
  env:
    AZURE_DEVOPS_EXT_PAT: $(System.AccessToken)
  displayName: 'Get Fabrikam-2021 variable group id'

variables:
- name: variableGroupId

trigger: none

pool:
  vmImage: ubuntu-latest

steps:
- bash: az --version
  displayName: 'Show Azure CLI version'

# Azure DevOps CLI extension call that does not require login or credentials
# since it configures the local environment
- bash: az devops configure --defaults organization=$(System.TeamFoundationCollectionUri) project=$(System.TeamProject) --use-git-aliases true
  displayName: 'Set default Azure DevOps organization and project'

- bash: az pipelines variable-group list --output table
  env:
    AZURE_DEVOPS_EXT_PAT: $(System.AccessToken)
  displayName: 'List variable groups'

- bash: echo "##vso[task.setvariable variable=variableGroupId]$(az pipelines variable-group list --group-name Fabrikam-2021 --query [].id -o tsv)"
  env:
    AZURE_DEVOPS_EXT_PAT: $(System.AccessToken)
  displayName: 'Get Fabrikam-2021 variable group id'

- bash: echo $(variableGroupId)
  displayName: 'Display Fabrikam variable group id'

I'm going to add some examples of assigning the result of an Azure DevOps CLI call to a variable, and then I'm going to close this issue, since the article has been updated and resolves the issue named in the title: "Provided method for Linux is not working as per examples"
All of the examples in this article now run on Linux without the following warnings:

WARNING: Failed to store PAT using keyring; falling back to file storage.
WARNING: You can clear the stored credential by running az devops logout.
WARNING: Refer https://aka.ms/azure-devops-cli-auth to know more on sign in with PAT.

I also added a comment to that developer communities issue that may be helpful to others if they land on that issue.


[Enhancement] Avoid customer confusion with clear message in disabled delivery areas scenario

Expected Behaviour
After a delivery zone has been disabled, it should be clearer for the user trying to order from it that delivery is not available
Actual behaviour
After disabling a delivery zone by setting its cost to -1, this is what a customer sees trying to order from the disabled zone

There is no error message explaining to the customer that they cannot order, just a vague "Delivery not available on all orders"; it is therefore possible to add products to the cart without making the checkout button ever active (as if there was an infinite minimum order).
For example, this is what happens if you try to order from an address not contained in any delivery area; in this way the customer immediately understands that he cannot order

I think, on the customer side, ordering from a disabled zone or outside any zone should give the same error message
Reproduce steps

Create a delivery zone and disable it by setting the cost to -1
From the site try to place an order from this area

Version
v.3.0.4-beta.26

Opened a PR here: https://github.com/tastyigniter/ti-ext-local/pull/38

Opened a PR here: https://github.com/tastyigniter/ti-ext-local/pull/38

@ryanmitchell how about we disable adding items to cart when the checkout button is disabled and display a flash message instead? Then add a new rule to Delivery cart condition to make it invalid when the delivery charge is negative..

@ryanmitchell how about we disable adding items to cart when the checkout button is disabled and display a flash message instead? Then add a new rule to Delivery cart condition to make it invalid when the delivery charge is negative..

Yeah there was quite a bit of code that didnt seem to be being used - I didnt want to touch it for fear of breaking something else.
I'll work on this over the next few days.

Yeah there was quite a bit of code that didnt seem to be being used - I didnt want to touch it for fear of breaking something else.
I'll work on this over the next few days.

Thank you!

Thank you!

Ok, I've updated to use rules and show a warning
Not sure how to disable the checkout button - is that being done somewhere already when delivery isnt available? I cant see it.

Ok, I've updated to use rules and show a warning
Not sure how to disable the checkout button - is that being done somewhere already when delivery isnt available? I cant see it.

Great, the flash message works fine, it stops the delivery condition from being added to the cart. This code disables the checkout button when the cart total is below minimum or delivery charge is unavailable..

Great, the flash message works fine, it stops the delivery condition from being added to the cart. This code disables the checkout button when the cart total is below minimum or delivery charge is unavailable..

Great, so I dont need to do anything?

Great, so I dont need to do anything?

No, we need to throw an exception somewhere in CartManager::addOrUpdateCartItem when deliveryChargeIsUnavailable() is true, that way we can display a flash message when adding an item to cart with delivery unavailable.

No, we need to throw an exception somewhere in CartManager::addOrUpdateCartItem when deliveryChargeIsUnavailable() is true, that way we can display a flash message when adding an item to cart with delivery unavailable.

Sorry meant to update this to say I opened a PR for this

Sorry meant to update this to say I opened a PR for this

Tested and I can confirm is FIXED!

Tested and I can confirm is FIXED!

So, to keep things simple, am reverting the PRs related to this issue. We really don't need another warning message on the delivery cart condition, the existing minimum order total warning should be enough.
Area condition rules should not be used to make delivery totally unavailable. The -1 rule intended purpose is to make delivery unavailable on specified order total not to disable delivery for the area. We already have the offer delivery/collection option to disable delivery/collection and unmarked areas are disabled by default.
tastyigniter/ti-ext-local@29483b3ad5cffec9630ef2ea99f4747765700274


vwire "tag_allowed" field requires a vartype of 'int'

When initially pulling in Panorama templates and parsing an exception is thrown if any value other than int is entered, even though a range or list of numbers are also valid input
Describe the bug
While parsing the template the 'tag-allowed' is assigned a vartype of 'int' so the
parse_value_from_xml_last_tag does not see valid ranges or lists such as '0-4094' as valid and raises an exception
Expected behavior
Parsing should allow for ranges and lists such as 0-4094 , 1-10, or 5,10,20-25, etc.
Current behavior
In base.py, within 'parse_value_from_xml_last_tag' in  the 'Do vartype processing' section

    elif self.vartype == 'int':
        settings[self.param] = int(elm.text)

raises an exception
Possible solution
set the tag-allowed token to a type other than int. Possibly also test using a regex such as ^[0-9,,,-]+$
Steps to reproduce

Create a panorama template with a vwire object with "Tag Allowed" field set to "1-5"
Attempt a call such as "panorama.Template.refreshall(pano)"

Screenshots

Context
I am unable to leverage the pandevice library to manage our Panorama because it cannot successfully parse the existing configuration
Your Environment
Panorama: 80 Templates, 60 Template Stacks, 100+ Device Groups managing a few hundred firewalls

Panorama version 8.1.9
Python 3.8.2
Ubuntu 20.04:

I was able to get it to successfully parse by changing the 'tag-allowed' param from vartype 'int' to 'none' within the class VirtualWire
network.py line 571
        params.append(VersionedParamPath(
            'tag', path='tag-allowed', vartype='none'))

I'm also having this issue, is anyone working to resolve this?

I'm also having this issue, is anyone working to resolve this?

Yesterday I created pull request 232 to remove the vartype from the tag-allowed VersionedParamPath call in network.py. Hopefully it is approved and merged soon.
As a workaround I have manually made the change on my machine and have been using it without problems for weeks now. You can probably do the same.

Thanks for opening this and for the pull request. Sorry for the slow reply.
On the surface this seems like an easy change, but we have to ensure there aren’t previous versions of PAN-OS where we’d break support. We’re confirming this through testing. It’s important to us that older scripts on older PAN-OS continue to work on the latest versions of pandevice.
Will try to get this merged in ASAP, thanks for helping us prioritize it.

Related to PR #232


Duplicate fixer

Codecov Report

Merging #321 into master will increase coverage by 0.09%.
The diff coverage is 79.16%.

@@            Coverage Diff             @@
##           master     #321      +/-   ##
==========================================
+ Coverage   90.90%   91.00%   +0.09%
==========================================
  Files          48       48
  Lines        2992     3069      +77
==========================================
+ Hits         2720     2793      +73
- Misses        272      276       +4

Impacted Files
Coverage Δ

lintreview/processor.py
88.73% <60.00%> (-2.32%)
:arrow_down:

lintreview/git.py
84.79% <72.72%> (+0.90%)
:arrow_up:

lintreview/__init__.py
100.00% <100.00%> (ø)

lintreview/fixers/__init__.py
95.38% <100.00%> (+0.55%)
:arrow_up:

lintreview/repo.py
100.00% <0.00%> (ø)

lintreview/tools/phpmd.py
100.00% <0.00%> (ø)

lintreview/tools/jshint.py
100.00% <0.00%> (ø)

lintreview/tools/ktlint.py
100.00% <0.00%> (ø)

lintreview/tools/tslint.py
100.00% <0.00%> (ø)

lintreview/tools/csslint.py
100.00% <0.00%> (ø)

... and 26 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a946fa6...1229384. Read the comment docs.


`` Function special symbols in text are not supported

$ go version
  go version 1.11

`` Function special symbols in text are not supported

Hello @xhochipe - It is not exactly clear what you are reporting. Did you mean to put a ` inside a raw string literal ? That is not supported.
Please show us a complete sample of code that is not a screenshot which clearly explains what you did, what happened and what you expected to happen. Thanks.

@agnivade  https://github.com/golang/go/issues/24475#event-1556138522  i`m  close issue


Propagate Java system properties to mill server

Currently, one can define system properties via the JAVA_OPTS environment variable. But it is only honored by mill when run with -i / --interactive option.
Solution: propagate the system properties to the running mill server.

I think this can be closed since we now have the -D flag to pass these


[MB-4630] [MB-4631] Support hhg and ntsr shipment type payment service items details

Description
Explain a little about the changes at a high level.
Reviewer Notes
Is there anything you would like reviewers to give additional scrutiny?
Setup
Add any steps or code to run in this section to help others prepare to run your code:
echo "Code goes here"

Code Review Verification Steps

[ ] If the change is risky, it has been tested in experimental before merging.
[ ] Code follows the guidelines for Logging
[ ] The requirements listed in
Querying the Database Safely
have been satisfied.
Any new migrations/schema changes:

[ ] Follow our guidelines for zero-downtime deploys (see Zero-Downtime Deploys)
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change
Jira story for this change

Screenshots
If this PR makes visible UI changes, an image of the finished UI can help reviewers and casual
observers understand the context of the changes. A before image is optional and
can be included at the submitter's discretion.
Consider using an animated image to show an entire workflow instead of using multiple images. You may want to use GIPHY CAPTURE for this! 📸
Please frame screenshots to show enough useful context but also highlight the affected regions.

Messages

:book:
:link: MB-4630, MB-4631

  Generated by :no_entry_sign: dangerJS against ba2a798f13ba38ab435d85299eac3ff3fda83c2a

Messages

:book:
:link: MB-4630, MB-4631

  Generated by :no_entry_sign: dangerJS against ba2a798f13ba38ab435d85299eac3ff3fda83c2a

Hey Duncan, this is looking good! A note on copy - can we make all the service items sentence case, and spell out Domestic? You can refer to Column E in this spreadsheet for the actual labels.

@amanda5iu I think you made a similar request to Donald before and it's a much more involved change than it may appear and would cascade to many places. @Ryan-Koch Can we make a standalone ticket for doing this work it's come up a number of times.

Hey Duncan, this is looking good! A note on copy - can we make all the service items sentence case, and spell out Domestic? You can refer to Column E in this spreadsheet for the actual labels.

@amanda5iu I think you made a similar request to Donald before and it's a much more involved change than it may appear and would cascade to many places. @Ryan-Koch Can we make a standalone ticket for doing this work it's come up a number of times.

Ah, thanks for the heads up. In that case I think we can merge this one :D

I think it's important too, I remember it getting pushed off even back when working on the modal for MTO approval.

Ah, thanks for the heads up. In that case I think we can merge this one :D

I think it's important too, I remember it getting pushed off even back when working on the modal for MTO approval.


Performance issue when having lots of tree-component rows

Description
I have an application where I use Handsontble and Angular-tree-component with lots of rows and columns in HoT and lots of rows in the tree.
When changing or selecting cells in HoT everything feels really sluggish (scrolling still feel super smooth and performant). I can set the ChangeDetectionStrategy to OnPush for the tree-component, but it the same doesn't make a difference for the HoT component... Are there any good practices to increase the performance of HoT? Can I do something similar to changing the ChangeDetectionStrategy?
Demo
https://stackblitz.com/edit/handsontable-tree-component-performance
Thanks!

Hey @ottosson
I do not know how to help you here as once we remove the three-component Handsontable works faster. It looks like you get extra 1000 components that slow down the code. I do not think that this was the desired effect. What you'd like to achieve?

Thank you. This is somewhat what I was thinking as well.
If I set ChangeDetectionStrategy for the tree to OnPush it will perform better, but HoT is still slow. Shouldn't this relieve the change detection mechanism for the whole app?
I guess this isn't really a HoT-problem, but I was hoping that there were some performance tricks I could use for the grid to speed it up. Or is this just an Angular related issue?

I'm not an Angular expert but from a conversation with our programmer we came out to a conclusion that it can be an Angular issue. Especially when ChangeDetectionStrategy doesn't do you any favors.

Right. I guess I'll follow that lead for now. Thanks for taking the time.


Add factories for logits_processors

This is a proposed solution to the guided decoding crash problem.
In vLLM there are two requests that can be used to submit more than one sequence at the same time: the completion request in the legacy OpenAI API, and the generate batch request in the tgis gRPC API. In both cases the sampling params are validated only once and a single SamplingsParam object is shared between all sequences, even when they belong to different sequence groups. The SamplingsParam is mostly a data object, but it has a list of logits processors that are executable. If the logits processors are stateless there is no problem. However, the CFGFSM used by the CFGLogitsProcessor has an internal state that depends on the sequence generated so far and is updated at each iteration. This causes it to raise a KeyError and crash the asyncio event loop.
The first attempted solution added a seq_id parameter to the logits processor call so that it could manage state internally, but that changed the interface that is already used by some external libraries.
The solution proposed here is based on adding factories for stateful logits processors. The basic idea is:

We add processors and factories to the same list so that they are in the correct order
We add a logits_processors list to the SequenceGroupState object
When the SequenceGroup is created, we iterate over the sampling_params.logits_processors
and copy the logits_processors and call the factories to populate SequenceGroupState.logits_processors
The LogitsProcessor(nn.Module) will iterate over the SequenceGroupState.logits_processors instead of
the sampling_params.logits_processors

Here are some diagrams to illustrate the current code structure to better visualize the proposed changes:

The idea is quite simple, but the execution is a bit tricky due to the nature of async code in python where an async call can't call a non-async function that calls an async function. In the PR I tried to support both using LLMEngine directly as well as the AsyncLLMEngine used for serving.
@njhill, I was going to add support to return the processors to the factory, but I realized that it was a little bit more complicated because only the scheduler knows when the sequence is done. Maybe we can add a callback somewhere in the scheduler where we can add the deallocation call. Actually that might be required, because I realized that there is another hidden bug: when sequence are preempted with the recompute policy, that makes the state of the logits processor invalid.

Thanks for the suggestions, @njhill . I didn't want to change too much of the original code so I ended up going overboard with the async cleverness. It's much simpler now.

@maxdebayser after addressing the simple comments above (not necessarily the pooling thing yet), maybe you could open an upstream PR? Then we can continue the discussions with others...

Here's the upstream PR: https://github.com/vllm-project/vllm/pull/5329


block_retrieval_queue: track deep sync status explicitly

To get ready for partial syncing, this removes uses of IsSyncedTlf from the prefetcher, in favor of explicitly passing in the deep-sync-edness of the request from the caller.
@jzila you in particular should look at this one probably.
Issue: KBFS-3523

(I know the diskBlockCacheWrapped still uses IsSyncedTlf to store blocks in the sync cache.  A later PR will deal with that.)

I'm going to review this on my flight tomorrow...there's a lot to think about.

I'd also like you to make a ticket to refactor away from prefetching based on priority, instead moving completely to the action.

@jzila I ended up doing this as part of the same ticket, and will merge it into this PR before merging.  It turned out to be necessary for the next part of partial syncing.  See #1932.


ap function dispatches to wrong argument

From the description:

Dispatches to the ap method of the second argument, if present.

However, the following code prints out CALLED:
var o = {
  ap: function(x){
    console.log('CALLED');
    return x;
  }
}
console.log(R.ap(o, 1)); //CALLED

This also appears to be the wrong way round to what the fanstasy-land spec requires:

A value which has an Apply must provide an ap method. The ap method takes one argument:
ap :: Apply f => f a ~> f (a -> b) -> f b
a.ap(b)
b must be an Apply of a function

From the description:

Dispatches to the ap method of the second argument, if present.

Would you like to submit a pull request to correct this?
Ramda currently targets v0.3.0 of the Fantasy Land specification, which explains why the argument order does not match that of the current version of the specification. #1900 will update Ramda to a more recent version of the specification, if merged.

Ah, that makes sense! I thought I saw something to do with the order of ap's arguments, but couldn't find it again!
I've made a PR for it now: #2004


DependentResource and Workflow Design Details Questions

This issue is a summary some design questions related to dependent resources and workflows.

[ ] Currently if a dependent resource is ready (ReadyCondition) in workflows (so is in a target state) or if is delete process successfully finished (DeletePostCondition) - this can be async - is handled by Conditions. However it might be more convenient especially using it from standalone mode to put this information to ReconcileResult and also provide DeleteResult where the result of those predicates could be added. Also might be a better / more efficient place to check it in the reconcile.
[x] Should we make in all condition names explicit if it is a post or precondition. Ready is a post, Reconcile is a pre-condition. The delete condition already has post in its name. See original design:
https://github.com/java-operator-sdk/java-operator-sdk/issues/850   (only applies to reconcile condition if we decide to change the point above)

After giving more thoughts and implementing samples (Integration tests). Having the postconditions explicit makes more sense. It is good for reusability, also for decoupling the condition related logic. For now I would say we could keep it separated and maybe change if we have some related feedback.

Will close this issue for now, and reopen in case.


problem after add media_kit_video package

problem on Fedora 39
Flutter 3.16.0 • channel stable • https://github.com/flutter/flutter.git
Framework • revision db7ef5bf9f (3 days ago) • 2023-11-15 11:25:44 -0800
Engine • revision 74d16627b9
Tools • Dart 3.2.0 • DevTools 2.28.2

[        ] [ +568 ms] release_bundle_linux-x64_assets: Complete
[        ] [  +66 ms] Persisting file store
[        ] [  +11 ms] Done persisting file store
[        ] [  +14 ms] build succeeded.
[        ] [  +13 ms] "flutter assemble" took 33,822ms.
[        ] [ +170 ms] ensureAnalyticsSent: 156ms
[        ] [        ] Running 0 shutdown hooks
[        ] [        ] Shutdown hooks complete
[        ] [        ] exiting with code 0
[   +1 ms] ninja: build stopped: subcommand failed.
[  +29 ms] Building Linux application... (completed in 38.2s)
[   +1 ms] "flutter linux" took 39,472ms.
[   +4 ms] Build process failed
[        ]
           #0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
           #1      _runBuild (package:flutter_tools/src/linux/build_linux.dart:186:5)
           <asynchronous suspension>
           #2      buildLinux (package:flutter_tools/src/linux/build_linux.dart:80:5)
           <asynchronous suspension>
           #3      BuildLinuxCommand.runCommand (package:flutter_tools/src/commands/build_linux.dart:89:5)
           <asynchronous suspension>
           #4      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1350:27)
           <asynchronous suspension>
           #5      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #6      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
           <asynchronous suspension>
           #7      FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:348:9)
           <asynchronous suspension>
           #8      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #9      FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:294:5)
           <asynchronous suspension>
           #10     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:112:9)
           <asynchronous suspension>
           #11     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #12     main (package:flutter_tools/executable.dart:90:3)
           <asynchronous suspension>

[ +197 ms] ensureAnalyticsSent: 183ms
[   +3 ms] Running 0 shutdown hooks
[        ] Shutdown hooks complete
[        ] exiting with code 1

#595


Mutations before the stop codon confused as StopLosses

Test using genome GRCm38, on transcript ENSMUST00000086738
##fileformat=VCFv4.1
#CHROM	POS	ID	REF	ALT	QUAL	FILTER	INFO	FORMAT

# Insertion before the stop codon: TGA -> TCC TGA
chr1	100484699	.	T	TCCT	5000	.	.	.

This is annotated as
StopLoss(variant=chr1 g.100484699_100484700insCCT, transcript_name=Cntnap5b-001, transcript_id=ENSMUST00000086738, effect_description=p.*1293S (stop-loss))
* aa_ref ="*"
* aa_alt = "S"

This should just be a clean insertion.

Suggested fix.
--- a/varcode/in_frame_coding_effect.py 2016-08-25 00:27:48.959775110 +0200
--- b/varcode/in_frame_coding_effect.py 2016-08-28 12:01:25.121807471 +0200
@@ -77,10 +77,14 @@

     # index of first amino acid which is different from the reference
     aa_mutation_start_offset += len(shared_prefix)
+    aa_original_end_offset = aa_mutation_start_offset + len(aa_ref)

-    if aa_mutation_start_offset == len(transcript.protein_sequence):
-        # if non-silent mutation is at the end of the protein then
-        # should be a stop-loss
+    if len(transcript.protein_sequence) < aa_original_end_offset:
+        # if aa_mutation_start_offset == len(transcript.protein_sequence):
+        # If the ref goes over the stop codon, then this is most likely a
+        # StopLoss. If the ref does not go over the stop codon, but the alt
+        # does, then this is an insertion/substitution close to the end of the
+        # transcript.
         assert aa_ref == "", \
             "Expected end of coding sequence for %s, got '%s'" % (
                 aa_ref)

Fixed by https://github.com/hammerlab/varcode/pull/173


lunar client crashes when on server with resource pack

it crash when it load resource pack i have no idea why it happening or lunar bug?

Minecraft version: 1.20.1
Server software: Paper
Plugin version: 2.4.0-pre1
082d16f1-3ee5-4f11-8b13-44030558dfa8-master.log
83c871bf-3807-4708-95da-9a8c0d563119-master.log
16577732-8c71-4e67-8461-9bd4cd5be3f4-master.log
16577732-8c71-4e67-8461-9bd4cd5be3f4-master.log
082d16f1-3ee5-4f11-8b13-44030558dfa8-master.log
83c871bf-3807-4708-95da-9a8c0d563119-master.log

When and why?
Documentation
Attach photos/videos documenting the bug.

it load fine at first time , second time it crashes

Why arent you using 2.5.0?

i cant find 2.5.0v ,only v0.2.2

i checked in atreno. i dont see texture pack in option server

ooh i understand. i checked plugin it say 2.5.0

sorry i forgot edit the bug report

i thought you was talking about resource pack , lol

STOP SPAMMING.

it turned out it was lunar client bug


SVG Display issue

For #8600

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR)
[x] Title summarizes what is changing
[x] Has a news entry file (remember to thank yourself!)
[ ] Appropriate comments and documentation strings in the code
[ ] Has sufficient logging.
[ ] Has telemetry for enhancements.
[ ] Unit tests & system/integration tests are added/updated
[ ] Test plan is updated as appropriate
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed)
[ ] The wiki is updated with any design decisions/details.

Codecov Report

Merging #8881 into master will decrease coverage by 0.61%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #8881      +/-   ##
==========================================
- Coverage   57.97%   57.35%   -0.62%
==========================================
  Files         527      527
  Lines       27512    27184     -328
  Branches     4141     4141
==========================================
- Hits        15950    15592     -358
- Misses      10690    10719      +29
- Partials      872      873       +1

Impacted Files
Coverage Δ

...nt/datascience/jupyter/invalidNotebookFileError.ts
0% <0%> (-60%)
:arrow_down:

src/client/formatters/serviceRegistry.ts
50% <0%> (-50%)
:arrow_down:

...cience/jupyter/jupyterDebuggerNotInstalledError.ts
33.33% <0%> (-33.34%)
:arrow_down:

...jupyter/kernels/jupyterKernelPromiseFailedError.ts
0% <0%> (-33.34%)
:arrow_down:

...ent/datascience/jupyter/jupyterWaitForIdleError.ts
0% <0%> (-33.34%)
:arrow_down:

...ience/jupyter/jupyterDebuggerRemoteNotSupported.ts
50% <0%> (-30%)
:arrow_down:

src/client/testing/codeLenses/main.ts
42.85% <0%> (-27.15%)
:arrow_down:

...t/datascience/jupyter/jupyterDataRateLimitError.ts
50% <0%> (-25%)
:arrow_down:

.../client/datascience/jupyter/jupyterConnectError.ts
50% <0%> (-25%)
:arrow_down:

src/client/common/utils/icons.ts
75% <0%> (-25%)
:arrow_down:

... and 30 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d84a11e...2168727. Read the comment docs.


Improve formatting of docs

I've only made two minor changes for now, but there a few more changes I'd like to discuss:

Change the docs for xclaim (line 1785) from this:
Changes the ownership of a pending message.
name: name of the stream.
groupname: name of the consumer group.
consumername: name of a consumer that claims the message.
min_idle_time: filter messages that were idle less than this amount of
milliseconds
message_ids: non-empty list or tuple of message IDs to claim
idle: optional. Set the idle time (last time it was delivered) of the
 message in ms
time: optional integer. This is the same as idle but instead of a
 relative amount of milliseconds, it sets the idle time to a specific
 Unix time (in milliseconds).
retrycount: optional integer. set the retry counter to the specified
 value. This counter is incremented every time a message is delivered
 again.
force: optional boolean, false by default. Creates the pending message
 entry in the PEL even if certain specified IDs are not already in the
 PEL assigned to a different client.
justid: optional boolean, false by default. Return just an array of IDs
 of messages successfully claimed, without returning the actual message

to this:
Changes the ownership of a pending message.

``name``: name of the stream.

``groupname``: name of the consumer group.

``consumername``: name of a consumer that claims the message.

``min_idle_time``: filter messages that were idle less than this amount of
milliseconds

``message_ids``: non-empty list or tuple of message IDs to claim

``idle``: optional. Set the idle time (last time it was delivered) of the
message in ms.

``time``: optional integer. This is the same as idle but instead of a
relative amount of milliseconds, it sets the idle time to a specific
Unix time (in milliseconds).

``retrycount``: optional integer. set the retry counter to the specified
value. This counter is incremented every time a message is delivered
again.

``force``: optional boolean, false by default. Creates the pending message
entry in the PEL even if certain specified IDs are not already in the
PEL assigned to a different client.

``justid``: optional boolean, false by default. Return just an array of IDs
 of messages successfully claimed, without returning the actual message.

Similar changes would need to be made for docs of other functions which haven't been formatted yet.

Fix the formatting of an external link here:

I've tried to fix it but can't work out how an inline code element can be inside a link.

I'm all for documentation improvements. Keep sending them in!
I'm not sure how to format an external link either, but we can figure it out.