decorators can be arbitrary expressions

I think pypa has an issue if a decorator is something other than a name.  For example if I run this code in Pyston:
class C(object):
    def __init__(self):
        self._x = None

    @property
    def x(self):
        """I'm the 'x' property."""
        return self._x

    @x.setter
    def x(self, value):
        self._x = value

    @x.deleter
    def x(self):
        del self._x

It works fine with the CPython parser, but with pypa it hits: NameError: global name 'x.setter' is not defined.  I haven't really investigated, but it seems like it's just parsing the entire region as a single name?

This might be rather a problem in the translation within pyston than a pypa issue. When using the parser test application (which I use to dump the AST) it's actually telling me that it is a dotted name. Which is the correct classification. I will have to check the pyston ast translation code to see if this is really the case.
And yes it is parsing it as a single name, however the 'dotted': True portion says that the name is accessing members of an object. The whole thing has to be split by  the dots.
$ ./parser-test test.py
Parsing successfull

[Module]
  - body:
    [Suite]
      - items: [
            [ClassDef]
              - bases:
                [Name]
                  - context: Load
                  - dotted: False
                  - id: object
              - body:
                [Suite]
                  - items: [
                        [FunctionDef]
                          - args:
                            [Arguments]
                              - args: <NULL>
                              - arguments: [
                                    [Name]
                                      - context: Param
                                      - dotted: False
                                      - id: self
                                    ]
                              - defaults: [
                                    <NULL>
                                    ]
                              - kwargs: <NULL>
                              - keywords: []
                          - body:
                            [Suite]
                              - items: [
                                    [Assign]
                                      - targets: [
                                            [Attribute]
                                              - attribute:
                                                [Name]
                                                  - context: Store
                                                  - dotted: False
                                                  - id: _x
                                              - context: Store
                                              - value:
                                                [Name]
                                                  - context: Load
                                                  - dotted: False
                                                  - id: self
                                            ]
                                      - value:
                                        [Name]
                                          - context: Load
                                          - dotted: False
                                          - id: None
                                    ]
                          - decorators: []
                          - name:
                            [Name]
                              - context: Store
                              - dotted: False
                              - id: __init__

                        [FunctionDef]
                          - args:
                            [Arguments]
                              - args: <NULL>
                              - arguments: [
                                    [Name]
                                      - context: Param
                                      - dotted: False
                                      - id: self
                                    ]
                              - defaults: [
                                    <NULL>
                                    ]
                              - kwargs: <NULL>
                              - keywords: []
                          - body:
                            [Suite]
                              - items: [
                                    [DocString]
                                      - doc: I'm the 'x' property.

                                    [Return]
                                      - value:
                                        [Attribute]
                                          - attribute:
                                            [Name]
                                              - context: Load
                                              - dotted: False
                                              - id: _x
                                          - context: Load
                                          - value:
                                            [Name]
                                              - context: Load
                                              - dotted: False
                                              - id: self
                                    ]
                          - decorators: [
                                [Name]
                                  - context: Load
                                  - dotted: False
                                  - id: property
                                ]
                          - name:
                            [Name]
                              - context: Store
                              - dotted: False
                              - id: x

                        [FunctionDef]
                          - args:
                            [Arguments]
                              - args: <NULL>
                              - arguments: [
                                    [Name]
                                      - context: Param
                                      - dotted: False
                                      - id: self

                                    [Name]
                                      - context: Param
                                      - dotted: False
                                      - id: value
                                    ]
                              - defaults: [
                                    <NULL>

                                    <NULL>
                                    ]
                              - kwargs: <NULL>
                              - keywords: []
                          - body:
                            [Suite]
                              - items: [
                                    [Assign]
                                      - targets: [
                                            [Attribute]
                                              - attribute:
                                                [Name]
                                                  - context: Store
                                                  - dotted: False
                                                  - id: _x
                                              - context: Store
                                              - value:
                                                [Name]
                                                  - context: Load
                                                  - dotted: False
                                                  - id: self
                                            ]
                                      - value:
                                        [Name]
                                          - context: Load
                                          - dotted: False
                                          - id: value
                                    ]
                          - decorators: [
                                [Name]
                                  - context: Load
                                  - dotted: True
                                  - id: x.setter
                                ]
                          - name:
                            [Name]
                              - context: Store
                              - dotted: False
                              - id: x

                        [FunctionDef]
                          - args:
                            [Arguments]
                              - args: <NULL>
                              - arguments: [
                                    [Name]
                                      - context: Param
                                      - dotted: False
                                      - id: self
                                    ]
                              - defaults: [
                                    <NULL>
                                    ]
                              - kwargs: <NULL>
                              - keywords: []
                          - body:
                            [Suite]
                              - items: [
                                    [Delete]
                                      - targets:
                                        [Attribute]
                                          - attribute:
                                            [Name]
                                              - context: Del
                                              - dotted: False
                                              - id: _x
                                          - context: Del
                                          - value:
                                            [Name]
                                              - context: Load
                                              - dotted: False
                                              - id: self
                                    ]
                          - decorators: [
                                [Name]
                                  - context: Load
                                  - dotted: True
                                  - id: x.deleter
                                ]
                          - name:
                            [Name]
                              - context: Store
                              - dotted: False
                              - id: x
                        ]
              - decorators: []
              - name:
                [Name]
                  - context: Store
                  - dotted: False
                  - id: C
            ]
  - kind: Module

I see, it should be converted to a type 'Attribute' instead.

This should be already handled with commit f52cb8a9
But the attribute assignment is not correctly handled yet.
See issue #16

From what I can tell this should be solved already, so I will close this now. Please reopen if this is not the case. Thanks.


Allow adding extra fields to all discovered entities

We can accept extra set of fields that will be added to all discovered entities.
Example:
EXTRA_ENTITY_FIELDS="zmon_environment:staging"

Those fields will affect how we sync the entities.

We would very much like to have this. Our use case is similar to your example e.g. having an environment field to distinguish between production and test environments in alerts.


Improve documentation

I agree with the description of bpaf here. I just spent ten minutes looking at its docs and I'm completely overwhelmed. There is no ready-to-run example in the top-level crate docs. I took a guess and thought maybe OptionParser was where to start, but I just got more confused. The docs say it's a "ready to run Parser," but it doesn't actually implement the Parser trait? And then it says it's created with Parser::to_options, but Parser is a trait... So how do I create it?
I had to click around for quite some time before finally finding a real example. I didn't go there originally because it's call "unusual" and I didn't want an unusual example. I just wanted a standard example.
The API surface area is huge and there are a lot of moving pieces. The API is further obscured, IMO, by the use of generics. The top-level crate docs start with a single sentence about what the crate does and then immediately launches into "Design considerations for types produced by the parser," and I have no idea what the heck that means. I go to expand "A few examples," and all I see are incomplete code snippets that don't use the library at all.
https://github.com/nicoburns/blessed-rs/issues/90

Maybe give winnow a perusal for ideas as it has functional roots and is heavily trait based.

Will take a look, suggestions about tutorials make sense as well. I have something in place but probably not enough.

I'd recommend making the examples complete instead of punting on that
I'd recommend showing usage examples. I made trycmd specifically so I could test these usage examples.

All the API functions come with examples that are complete apart from fn main() { println!("{:?}", options().run()) } to run the parser. As well as expected output (this also serves as a test to make sure that derive and combinatoric examples are identical).
See here, examples for shell completion contain expected output as well.

All the API functions come with examples that are complete apart from fn main() { println!("{:?}", options().run()) } to run the parser. As well as expected output (this also serves as a test to make sure that derive and combinatoric examples are identical).

I was talking about the tutorial which has this message:

Most of the examples stop at defining the Parser, to be able to run them you need to convert your Parser into OptionParser with Parser::to_options.

https://docs.rs/bpaf/latest/bpaf/_combinatoric_tutorial/index.html
In Winnow's tutorial, I write out a full program but then hide the parts that were specified in a previous code block within the same section (I might do it sometimes between sections, unsure)

I see. Will change them to be the same style as the rest of examples, thanks.

Came up with this, for now it reintroduces intro and combinatoric tutorials. Is that less confusing?
https://pacak.github.io/bpaf/bpaf/_documentation/

imo "forward", "backward" and table of content for non-reference documentation doesn't quite make sense and it felt harder to navigate.  For example, I go to the tutorial page, thinking I'm going to get a tutorial, but instead I get links out to tutorials.  Upon further looking, I guess that was the ToC but that wasn't clear.  For winnow, I link directly to the first page of the tutorial to avoid this "follow a link to follow a link" problem.
It also appears there are child pages within the tutorial? Or actually multiple tutorials?
Also, I would recommend maintaining two documentation paths, like clap does.  Some combinatoric concerns are more advanced for derive users while derive has some specific topics.  It is also weird to see the code, the primary communication of the tutorial, be hidden.
With this in mind, I'd recommend making the derive and combiantoric tutorial vastly different (unlike claps).  The derive can focus on high level concepts (these are flags, these are subcommands), then delegate to the combinatoric tutorial which does a ground-up approach, then come back to show how to mix the combinatoric API into the derive, unlocking the full power.
In general, the first tutorial (?) feels more like its explaining CLI concepts than introducing bpaf to me.
The navigation links, while nifty, then dominate most of the view, making it harder to standout from the content.

It also appears there are child pages within the tutorial? Or actually multiple tutorials?

Currently there's a combinatoric tutorial, I'm working on derive one, then there will be a blurb about picking the right types with some extra external links. Then documentation generation, completions so "follow a link to follow a link" is inevitable.
I'm not sure about making derive and combinatoric tutorials different. At this point they are different ways to express the same ideas. Derive generates the same code as I would write by hand in combine mode. There's a WIP branch that achieves 100% feature parity so if you want you can stick with just derive.

It is also weird to see the code, the primary communication of the tutorial, be hidden.

Hmm... Full examples and their output are hidden, code I'm trying to communicate with is visible. Will check how it looks like when expanded.

In general, the first tutorial (?) feels more like its explaining CLI concepts than introducing bpaf to me.

Terminology mostly. Plus I saw questions like "what do I put in the metavar" and "I don't want to pass the name, just the value" (this was about clap) so setting terminology straight is important.

The navigation links, while nifty, then dominate most of the view, making it harder to standout from the content.

Yea, will probably tweak them to stand out less.

Terminology mostly. Plus I saw questions like "what do I put in the metavar" and "I don't want to pass the name, just the value" (this was about clap) so setting terminology straight is important.

That is a lot of space taken up in establishing terminology.  I expect you'll lose a lot of people in that section and likely for the rest of the tutorial.  It needs to be briefer and along with practical aspects of moving forward.
I thought the collapsed examples in this "terminology" section were meant to be teaching me how to do these things which is why I was thrown off so much.

Interesting. I know that there are people out there that don't know this stuff so this is useful for some. Added a better indication that this stuff is optional
And moved most of the docs over to a new structure
https://pacak.github.io/bpaf/bpaf/index.html

Only did a quick look so far, but my frustrations in navigating it are still there.
The quick start also feels all over the place.

I almost missed the collapsed sections

Just decide on an example and show it without collapsing.  Maybe the output can stay collapsed

The cargo add command is for derive but a combiantoric example  is included (and listed first)
I'm assuming dull_colors is the preferred style since its referenced but wanted to call it out here in case it isn't

Only did a quick look so far, but my frustrations in navigating it are still there.

Nesting? I can probably flatten things a bit (or a lot), but not sure if that's the right approach. I'm assuming people start with intro, and one or both tutorials. After that there's not much point going back there. Howtos are covering specific problems - I'll add more at some point, but just knowing what there is usually enough. Reference is useful for quick navigation and theory for those who are interested. Links right and left are similar to those of Rust book but each works within a category, I've seen those used in other documentation too.
Removing expanding in tutorials is probably a good idea, will try that.

The cargo add command is for derive but a combiantoric example is included (and listed first)
I'm assuming dull_colors is the preferred style since its referenced but wanted to call it out here in case it isn't

Enabling derive is a safe default - this way both APIs are working, same with dull_color - a safe default. Feature flags are documented somewhere and I'm assuming people can adjust it later - stuff like autocomplete and documentation generation is locked behind feature flags as well.

Nesting?

Nesting might not be bad but I would linking directly to the first page of the tutorial, rather than the table of content so they immediately see what they are looking for rather than taking multiple steps.  I also kept getting confused because I expected the "next" links to take me to the first page of the tutorial from the table of content, much like you get with mdbook.
The how to nesting is annoying.  I have to know what I want is considered "exotic" (cargo isn't) before I can see the list (and then everything is collapsed there as well).

Reference

The reference link confused me because docs.rs/bpaf is the reference.  For me, a more specific title would help.  For example, in winnow, the closest equivalent is "List of combinators"

Enabling derive is a safe default - this way both APIs are working, same with dull_color - a safe default. Feature flags are documented somewhere and I'm assuming people can adjust it later - stuff like autocomplete and documentation generation is locked behind feature flags as well.

The further you get into the documentation, the more users you will lose.  There will be enough users who will think derive is needed for the example they are looking at.  There will also be the users who will get confused and, though it can be resolved, it adds a ding against the package in their mind.  Enough of those and they will walk away.

Nesting might not be bad but I would linking directly to the first page of the tutorial
There's multiple independent tutorials, that's the problem. I can flatten it into something like

- tutorials
  - basic options
  - combinatoric
  - derive
  - autocomplete
- howto
  - parsing strange things
  - dealing with cargo

etc. Do you think that's better?

The reference link confused me because docs.rs/bpaf is the reference.

It's a structured reference that I'm removing from the front page and a list of things rustdoc managed to find, sorted alphabetically.

For me, a more specific title would help.

Currently it says this: "Structured API reference - Links to all the functions grouped by purpose". How would you call it instead?

There will be enough users who will think derive is needed for the example they are looking at.
Hmm... Worst thing that can happen is that they will spend an extra 3 seconds compiling syn and proc-macro. I can list both lines with or without colorization, if you think that's better, but in this case if they pick the wrong line - the worst thing is that examples are not going to work.

I used cargo as an example.  I would recommend flattening the entire "parse strange things" section.  You could have that be a header with the items being bullets under it, much like winnow which was a generalization of the cookbook in clap because i found I needed more than just cookbook entries.  Naming this "special topics" would also provide a great place to put the applicative docs, putting them down a level, de-emphasizing them.

For me, a more specific title would help.

Currently it says this: "Structured API reference - Links to all the functions grouped by purpose". How would you call it instead?

I would say that is a bad sign to the purpose of the document if you can't name it.
Looking again at the page, almost everything on it ("improving user experience" being the one exception) is related to the lifetime of Parser.
Some ideas

Put it on trait Parser
Name it related to Parser, like "Lifecycle of a Parser"
Put it back on the landing page but be more brief and clearer

Another tip: could you make code examples in the tutorial match exactly the "shell" examples, so if you have a shell example of ls --time --reverse then the next code Combinatoric example should contain these --time and --reverse examples so it's easier to match the output to code
I know you have a separate output section at the bottom, but maybe use the same output (if you want to have a shorter version) at the top as well so that all examples (shorter at the top and longer at the bottom) are consistent

Another tip: could you make code examples in the tutorial match exactly the "shell" examples,

You mean include implementation for bits like this?
$ cargo --help
$ ls -la
$ ls --time --reverse

Original idea was to give an example for specific primitives in terms of familiar programs then how you would write it in terms of bpaf. I guess implementing the same options as familiar examples works better. Will look into that :+1:

Familiarity is nice, but you don't have to break it. For example, in your app's example you have --release Build artifacts in release mode, but then why doesn't cargo's example at the top also have cargo build --release?
So it'd be something like

short examples without help
code covering at least the same flags as in the short examples (but could also add extra) but with comments
longer help output

Just went through the tutorial again and trying to navigate it makes me want to rage close the tab.

The navigation links overwhelm most views, distracting me from the actual material.
When I click on a tutorial, the "next" link takes me to the next tutorial, not the next page in that tutorial

None of this is new and I just don't have the patience at this time to deal with fighting the navigation to check the rest of the content / organization.

Another big issue with the docs is lack of search: the official docs' search engine only finds various  api-related fields (like function names), so if I wanted to find how to order my arguments in help, and search for order, I get nothing even though there is a helpful tutorial that contains that word and explains that struct's field order is preserved for some args
Is it possible to somehow tweak the official docs engine to allow for searching within your tutorials etc.?

The way to tweak this is limited to adding #[doc(alias = "order")] but the search will only show it on an exact match last i checked.

but the search will only show it on an exact match last i checked.

I think I'll go with your suggestion to have everything on a single struct parametrized by other struct. Everything is going to be on a single page and I should be able to add meaningful sections to the right as well. Proof of concept for that exists, slowly messing with some other internal details I'd like to change as well to make everything more accessible.

Yeah, exact match limits are part of the problem, but also you can't alias everything the use might ask, like help order with full-text search would find this tutorial text

If you are using positional parsers - they must go to the right-most side and will run in
the order you specify them. For named parsers order affects only the --help message.

For now I have to resort to just using a text editor's search functionality, which beats nothing, but doesn't support fuzzy search like any decent search would.
Maybe at least the examples could be published as a github-page with some js search plugin? Or at least you could google-search through the site, which would still be a big improvement.
I've tried google-searching the current docs site, but it seems tutorial pages aren't indexed?


Added SAND#

Sorry.  Another pull request to add the SAND #.

@william76 -- Do you have insight into why this test failed?  The article looks fine to me.

not sure, looks like something caused an unhandled error in the script.
I'm in Albuquerque attending the Kokkos Usersgroup meeting today, I'll have a look at the script and see if I can figure out what's going on in a bit. =)

@curfman
I took a quick look at the metadata on this article and found a couple issues.
The meatadata is:
<!---
Publish: preview
Categories: reliability, development
Topics: testing, continuous integration testing, documentation
Tags: bssw-blog-article
Level: 2
Prerequisites: default
Aggregate: none

SAND #: SAND2019-4553 S
Image owned or licensed by Sandia
--->

The traceback on the checker came from the empty line in the metadata.  That's a bug and I'll get that fixed on the checker script.
The other thing that the script didn't hit but would also cause a problem in the metadata is the line:
Image owned or licensed by Sandia

This doesn't fit into the key: value formatting that we expect to see in the metadata section by the checker...  We should discuss whether or not freeform text should be allowed in our metadata.  If we do this, we should put some constraints in place or add a new catch-all rule such as free form text lines should have a # on column 1 or a : or something so I can write the checker to properly ignore those lines rather than trying to make sure it's a properly formatted metadata entry.


Update Project to follow Android build best practices

Convert gradle build scripts from groovy to kotlinscript for better IDE integration and code completion
Migrate raw gradle includes statements into a build plugin.
update Gradle to 8.10+
upgrade AGP to 8.7.1+
move dependency declaration to a version catalog
(gradle/libs.version.toml) (using the default location)
create a dependency bundle for the ftc dependencies ('libs.bundles.ftc')

FWIW, I already did this in a clean branch and can issue a PR for that, but seems like something that would make using the repo much simpler.

We internally working on how to update our tooling and evaluating the side-effects of such an update to teams who may be using older versions of Android Studio without an easy update path (e.g. school teams). Updating the tooling is not merely an exercise in bumping version numbers; this repository is merely an autogenerated output of an internal repository with a much more complicated build process, which uses Gradle features that completely break the build in newer versions.

@Windwoes please consider adding comments to the relevant places in the build documenting why this older version is kept.  I unknowingly went through the update process myself and was about to submit a PR when I saw this.

The Ladybug problems are addressed in 10.1.1.
As to the rest, the repository you see here is built from a private development repository.  Both need to build and the public repository depends heavily on how the private repository is being built.  Changing how this is all done is not on FIRST's roadmap at present.


Disable access for unprivileged users

Disable edit drpolicy for un-priviliged users.
BZ: https://bugzilla.redhat.com/show_bug.cgi?id=2166376
Signed-off-by: Timothy Asir<EMAIL_ADDRESS>

For admin:

For un-privileged users: Edit option is disabled

don't pollute generic component, control disabling it from outside...
cc @GowthamShanmugam

we should show reason for disabling as well... we need to check with UX for generic message...
ex: "don't have access"

This patch disable the kebab menu and a tool tips will be shown for app users.  I will send a follow up enhancement PR for disabling each of the kebab items separately.

Admin user:

App user:

/test odf-console-e2e-aws
/test images

/test odf-console-e2e-aws

@GowthamShanmugam Please review

/test odf-console-e2e-aws

A few more changes are required as per a recent discussion:

On the DRPolicy list page, make the connected application popover link to hyphen(-) when the user dont have to create permission or connected application count is 0

Disabling dashbaord access for unprivileged users: https://github.com/red-hat-storage/odf-console/pull/665

For the unprivileged users it gives count 0 and this issue more like genuine for every users/admin and feeling not related to users privilege so shall we send a patch separably?

/test odf-console-e2e-aws

/test images
/test odf-console-e2e-aws

/lgtm

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/lgtm

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/hold
Please update the title correctly it's currently not updating the BZ.

/hold Please update the title correctly it's currently not updating the BZ.

also, we don't have all acks on BZ (we are not blocked on that and can still merge the PRs, but since we are post FF correct way is to get all acks)...

/retest

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/test odf-console-e2e-aws

ci/prow/odf-console-e2e-aws

ci/prow/odf-console-e2e-aws

ci/prow/odf-console-e2e-aws

ci/prow/odf-console-e2e-aws

ci/prow/odf-console-e2e-aws

/test odf-console-e2e-aws

/test odf-console-e2e-aws

Rebased with latest master

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/cherry-pick release-4.13

/test odf-console-e2e-aws

/test odf-console-e2e-aws

@TimothyAsirJeyasing this PR is stuck for a long while, plz check what's the issue and why it is not getting merged...

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/hold
tests are failing due to changes to kebab.

/test odf-console-e2e-aws

/test odf-console-e2e-aws

@TimothyAsirJeyasing Plz add BZ link to the PR's description and also prioritise this PR... this PR is open for a long while and tests are failing again and again... check the issue and fix it...

/test odf-console-e2e-aws

fix the lint errors which are added by this PR (in kebab.tsx file)...

LGTM
cc: @bipuladh to take a look

BZ: https://bugzilla.redhat.com/show_bug.cgi?id=2166376

LGTM
cc: @bipuladh to take a look

CI is failing...

LGTM cc @SanjalKatiyar

tests are failing again and again for this PR (for a long time)... we can merge once CI passes...

/test odf-console-e2e-aws

/hold cancel

/lgtm

/cherry-pick release-4.13

/cherry-pick release-4.13-compatibility

@TimothyAsirJeyasing once this is merged and backport PRs are ready, plz update the title of the backport PRs and add bug number and get the PRs tagged...


Selecting index view manually

We were able to select the index manually but the selected view was not being changed. This change changes the index as well as the view.

@christianhelle Can you look at this please.

dont. this is breaking. Did not test properly. needs more change than this. can you please revert this.


Vim doesn't allow preceding method calls with a logical NOT operator, like !mylist->empty()

Describe the bug
Currently it is not possible to precede a method call with a logical NOT operator, for example: !mylist->empty().
To Reproduce
Run vim --clean -S tmp.vim, with
" tmp.vim
if !range(5)->empty()
    echo 'List not empty'
endif

Vim will print the following error:
E745: Using a List as a Number

At the moment we have to put the expression inside parentheses, like !(range(5)->empty()), or use the old syntax !empty(range(5)).
Expected behavior
I would have expected this to work just like in other languages. If it can't be implemented, maybe it could be mentioned somewhere in the documentation.
Environment
Vim version 8.2.1046

You could also reverse the :if syntax:
if range(5)->empty()
  echo "List empty"
else
  echo "List not empty"
endif

or even
if range(5)->empty()
  " do nothing
else
  echo "List not empty"
endif

Best regards,
Tony.

When using expr1->func()  the question is whether the prefix is applied to expr1 or to the whole.
The example in the code mentions "-1.0->method()". Her the "-" needs to be applied to expr1.
But in your example the "!" applies to the whole.
It gets even more tricky: "!-1.0->method()".  Then the "-" applies to expr1 and "!" to the whole.


proxy/grpcproxy/cache/store.go: fixed TODO: use marshalTo to reduce

modified proxy/grpcproxy/cache/store.go function keyFunc to use marshalTo instead of marshal

did this make a performance difference? if not, should probably avoid premature optimization and keep it simple

i have not measured the performance, but since access to the sliceRangeRequestMarshal is synchronized, multiple routines cannot marshal the RangeRequests independently, there can be a dip in performance.

@xiang90  @heyitsanthony what should be done about this.


1.86 release breaks Coder station

Type: Bug
The latest 1.86 release breaks compatibility with my Coder station. I've rolled back to 1.85, but you keep automatically updating me to 1.86! This problem does not rely on updating or rolling back any plugins, it's directly related to the core VSCode version. When trying to connect all I see are constant "Can't get server logs" messages or such, which eventually time out and throw an error.
 Interim workaround is to disable automatic update (in Settings) and then install 1.85.2

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Update Pages “home”

Automatically generated by Netlify CMS

👷 Deploy Preview for parsimony-dev processing.
🔨 Explore the source changes: 0998fcf1d360da3a5fdc9e06262531db3d8767fb
🔍 Inspect the deploy log: https://app.netlify.com/sites/parsimony-dev/deploys/618833dd892f650007f9b64a


Can we add a default vagrant  file?

Can not run make build in Mac os. I think if we could add a default vagrant  file will be better.

make build should run on macos now.
Also we added a vagrant file to run e2e tests.
See https://github.com/istio/istio/blob/master/tests/e2e/README.md#using-a-local-vm


KNeighborsClassifier_MinMaxScaler

Added meta desciption for both the submit files.
remove the inputs in filepath,target and features

changes are done

Change the Heading Title of the file currently it says Classifier with Robust

done


Event handling config simplification

Introduced new concept for Event Processing Configuration.
There is a split between Event Processing Configuration and Event Processing Configurer.
Both of them, together with ModuleConfiguration, are implemented by EventProcessingModule.
Added processing group type selectors.
Resolves #740

I've pushed some javadoc adjustments just now. Feel free to review them.


Indent markdown code snippet

Currently if I add some code block as such:

Hello World

it does not format the indentions. Is there a way to do this or any idea on how to achieve this?
Wanting the result to be something like this:

      Hello World

You could indent your code before insert. This does not seems to be related to this package anyhow.


Render issue/PR templates

EDIT: this has been partially implemented, but your help is needed to improve it as described in: https://github.com/sindresorhus/refined-github/pull/3504
You can pick up where I left off

Issue/PR templates are easy to dismiss and the links in it are not clickable.
What if we rendered them? (via GitHub’s "preview comment" feature)
BeforeAfter

To keep in mind:

this won't work for all templates (like https://github.com/babel/babel/issues/new/choose), but it may be worth trying

it could be opt-in by each template, for example "Only if it starts with Instructions: or similar keywords"

we might have to display the render under the field to avoid moving the field down
we probably can't delete the field’s content because some templates have to be filled by the user

@fregante using this as a basic non-intrusive checklist for tasks sounds a lot useful than having to handle user input inputs along with it too. It just sounds more complicated (even if we find a very optimised solution for it).

https://github.blog/changelog/2021-06-23-issues-forms-beta-for-public-repositories/ !!

Yooooooooo! Turning this into a meta issue 👇


Error when using rodauth-rails with ruby-oci8

I use rodauth-rails (1.15.0) with sequel-activerecord_connection (1.4.1) and sequel (5.84.0).
When trying to login I get the following error message:
"undefined method `raw_oci_connection' for an instance of OCI8EnhancedAutoRecover"
I tried with ruby-oci8 (2.2.14) and (2.2.13 x64-mingw-ucrt). Any suggestions how I can solve the issue?

Yes, with the actual version from the sequel-activerecord_connection master branch it works! Thanks a lot!

Great, just released version 1.4.2 with the fix.


BossBar helper

this pr adds bossbar to velt/helpers

Rename namespacekey method to namespaceKey
Make getBossBar, getBossBars, and createBossBar also part of helpers

it's already a part of helpers?

I mean helpers directly.

I mean helpers directly.

as in remove the crafting interface?

Nah, I just mean add the bossbar methods directly to helpers as well as an alias.

Alternatively bossbar.create and bossbar.get would be better since it doesn't mean you have to repeat the bossbar name twice


In Problem Description

@MinMah23
In section 4.1 Problem Description (Page 3), you started the paragraph with the introduction of the system. But I guess this section should mainly focuses on the your solution toward the problem in "PROBLEM SPACE".

Also, first paragraph seems like repetition of the Introduction paragraph.

@DeeshaPatel
As I got, this section is allocated to describe the problem and focused on the part that we want to solve, the picture that you attached, also emphasizes to talk about the problem not the solution. I described my problem details at the first paragraph and then at the second paragraph, I talked about my area of solution which is describing and simulating the system. Do you think I should omit the first paragraph? so when is the right place for the problem's details?


Ensure DomainAdjust removes remoting requirement for io worker capabi…

…lity before removing the capability.
Needed for WFCORE-808. Currently WF full just nukes the subsystem and the io worker capability never gets unregistered. Which is a bug. WFCORE-808 fixes that but that leads to missing capability problems if the requirement isn't removed first.

Linux Build 7048 is now running using a merge of b6180817e1ba9db00c09877ad2f9925ef982bf49

Windows Build 2102 is now running using a merge of b6180817e1ba9db00c09877ad2f9925ef982bf49

Linux with security manager Build 1923 is now running using a merge of b6180817e1ba9db00c09877ad2f9925ef982bf49

Linux with security manager Build 1923 outcome was SUCCESS using a merge of b6180817e1ba9db00c09877ad2f9925ef982bf49
Summary: Tests passed: 872, ignored: 280 Build time: 0:06:26

Windows Build 2102 outcome was FAILURE using a merge of b6180817e1ba9db00c09877ad2f9925ef982bf49
Summary: Tests failed: 2 (2 new), passed: 2941, ignored: 344, muted: 2 Build time: 0:50:47
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.clustering.messaging.ClusteredMessagingTestCase.testClusteredQueue: <no details avaliable>

org.jboss.as.test.clustering.messaging.ClusteredMessagingTestCase.testClusteredTopic: <no details avaliable>

Linux Build 7048 outcome was FAILURE using a merge of b6180817e1ba9db00c09877ad2f9925ef982bf49
Summary: Tests failed: 1 (1 new), passed: 2942, ignored: 344, muted: 2 Build time: 0:52:16
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.ejb.remote.entity.bmp.BMPRemoteEntityBeanTestCase.testGetEJBLocalHome: <no details avaliable>


Update README.md

Updating readme for https://mitre.sharepoint.com/sites/tacoma-list/SitePages/Repository-Requirement.aspx
Pull requests into the Cypress Validation Utility require the following. Submitter and reviewer should :white_check_mark: when done. For items that are not-applicable, note it's not-applicable ("N/A") and :white_check_mark:.
Submitter:

[ ] This pull request describes why these changes were made.
[ ] Code diff has been done and been reviewed

Reviewer 1:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose

@lmd59  would be also good to include how to install or use the project (or a link to in-depth instructions if necessary) and how to run the tests. Could you add that briefly?


Add -std flags to generated build files

This fixes CLion not using the correct C++ (and I guess C) standard in conjuction with meson's cpp_std option.
CLion doesn't seem to do anything with some other flags I tried, like -fopenmp, so we can ignore that for now.

Thanks! Great work. :+1:


Revert "Move CR name length validation to kubebuilder markers (#3665)"

This reverts commit cc4809062d8933060c6ae8547111cea7ec66dbf7.

Description
same as https://github.com/Dynatrace/dynatrace-operator/pull/3802 (it's not technically a cherry-pick)
How can this be tested?
same as https://github.com/Dynatrace/dynatrace-operator/pull/3802

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Please upload report for BASE (main@da71084). Learn more about missing BASE report.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3803   +/-   ##
=======================================
  Coverage        ?   65.01%
=======================================
  Files           ?      395
  Lines           ?    21315
  Branches        ?        0
=======================================
  Hits            ?    13857
  Misses          ?     6131
  Partials        ?     1327

Flag
Coverage Δ

unittests
65.01% <100.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Serialization of SAP Standard Includes in a Z-function group

We have an enhancement of the material master in a Z-function group. This Z-function group contains a lot of SAP Standard Includes. AbapGIT generates during the serialization also files that contains these SAP Standard Includes. Is this a bug? Will the deserialization overwrite the SAP Standard Includes?

The repository must include only objects that are part of the associated SAP package (or sub-packages). Therefore, none of the SAP standard includes should be serialized.
https://github.com/abapGit/abapGit/blob/main/src/objects/zcl_abapgit_object_fugr.clas.abap#L594
The select above is not sufficient to filter out includes that are part of standard function groups (since they don't have a tadir entry).
Determining the function group and then package will take too long. Try adding a select for all entries on trdir for the includes and eliminate all that have cnam and unam = 'SAP' (or like 'SAP%').

@mbtools
I made a test and created a new function group with the include LSEWBSYM.

It will be staged

I tried to find out how SE80 is determining the package and the original function group

I found this coding, it determines the function group of the include

I think we should add it to the method.
What do you think?

Let me see if I understand: For each include, determine the function group based on the logic in your screenshot and compare it to the function group we are serializing. If it's different, then skip this include.
Sound good to me.

Thanks @mbtools I will take care on it, when I find some time.

@mbtools I solved it with the pull request #5134
the include LSEWBSYM will be excluded from staging and the repo view

how the serialize runtime for your big repo after this change?

@mbtools
I checked it whith the Serialization Performance Test Tool:
Only the FUGR with the Material Master enhancement without the new check: 5,797720 sec.
Only the FUGR with the Material Master enhancement with the new check: 0,550587 sec.
The whole repository (7.587 objects) without the new check :165,141670 sec.
The whole repository (7.587 objects) with the new check: 139,610175 sec.

good improvement. as I mentioned, you might want to look into DB tuning next.


[ML-290] Add logger to improve messages output

closes #260
Add logger for cpp code to make output clean

@argentea could you rebase since there are updates for fixing code scan.

@argentea Thanks for your work! Do you mind I close the PR and @minmingzhu will create another PR based on your branch.

@argentea Thanks for your work! Do you mind I close the PR and @minmingzhu will create another PR based on your branch.

Please.

Thanks! Continue to work on #358


Setting Security Group When Creating Environment

When using pac admin create there is not an option to set the Security Group to secure access to that environment.
Microsoft.PowerApps.Administration.PowerShell New-AdminPowerAppEnvironment command has this option and this omission is the only thing stopping us moving over to using the pac cli instead. Is this option supported and something that I've missed/upcoming/no longer supported?
Thanks

+1 on this

Agreed, we have a similar challenge!

Agreed, we have a similar challenge

Converting to discussion so people can vote on it


⚠ Bofrost.at has degraded performance

In f756cd9, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1869 ms

Resolved: Bofrost.at performance has improved in efe7c39.


Region Folding doesn't work with JSX multi-line comments

Type: Bug
The following does not work with region folding in JSX:

    {/* #region Region */}

    {/* #endregion */}

However, the following does work:

    {
        // #region Region
    }

    {
        // #endregion
    }

The latter is not how VSCode creates comments in VSCode by default (when you press cmd + /) and it is quite clunky
VS Code version: Code 1.76.1 (Universal) (5e805b79fcb6ba4c2d23712967df89a089da575b, 2023-03-08T16:32:09.831Z)
OS version: Darwin arm64 22.3.0
Modes:
Sandboxed: No

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.76.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Add option for install behind http_proxy

Proposed Changes
Added the option to install from behind an http proxy.
If configured (false by default), it puts your http_proxy + https_proxy + no_proxy env vars into a k3s(-agent).service.d/http_proxy.conf file, before anything gets installed.
This way k3s can access the internet for images etc through the proxy.
Also added env vars to the playbooks, defaulted to '', so ansible can still download the binaries and manifests even if you're behind a proxy.
In the reset main.yml I thought I'd add a conditional task.
So it doesn't try to remove the http_proxy files and errors out when you don't have them enabled/installed.

The majority of the time it failed with the gurumeditation state error and when it did go past that, it couldn't resolve DNS.
I've ran this both with http_proxy enabled and disabled, installed fine in both environments.)
Checklist

[x] Tested locally
[x] Ran site.yml playbook
[x] Ran reset.yml playbook
[ ] Did not add any unnecessary changes
[x] Ran pre-commit install at least once before committing
[ ] 🚀

Thank you!  Sorry about the CI woes.  It's been pretty flaky lately.

Yeah no worries. I thought it might override the already existing proxy env vars on the runner/vagrant hosts, but according to this (printing out the ansible_facts), they're not set. So that shouldn't(?) be an issue?
Now I'm thinking it might not like the default(''), checks are currently running for a default({}) instead.
If that works, I'll tidy up the environment: in the playbooks a bit and add a new commit to this

Seems like it's fine now, if vagrant decides to cooperate.
Please retry the checks, reran them on the fork, they're all nice and green


Does not even work ...

I assume this is dead as dead can be ...

Works fine for me...

@eduardoinnorway what is your error message? It's work for me. Can you provide a trace?


GlowBrush shows on all desktops

When using GlowBrush on a MetroWindow, the GlowBrush outline shows on all virtual desktops in Windows 10. If you're running from Visual Studio, the WPF inspection tools will show with it, though if you click on them, it will take you back to the desktop that actually contains the window.
Steps to reproduce:

Create a WPF project that uses MetroWindow
Set GlowBrush to any color
Press Win+Tab and switch to a different virtual desktop
See glow without window

Expected behavior:
No glow on desktops that don't have the window
Environment:

MahApps.Metro v2.0.0-alpha0490
Win10 1903
Visual Studio 2019 16.3.3
.NET Core 3.0

Repo
I'm experiencing the problem with this repo, but I can try to put together a simple demo repo if you need me to.

@Herohtar I moved this to ControlzEx, because the Glow lives there https://github.com/ControlzEx/ControlzEx/issues/92


maven: 3.9.4 -> 3.9.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/maven/versions.
meta.description for maven is: Build automation tool (used primarily for Java projects)
meta.homepage for maven is: https://maven.apache.org/
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.9.5 in filename of file in /nix/store/810cmjnzj42zn2b4inv1ksdv5f4rmaly-apache-maven-3.9.5

Rebuild report (if merged into master) (click to expand)

20 total rebuild path(s)

20 package rebuild(s)

First fifty rebuilds by attrpath
cryptomator
dbeaver
digital
forge-mtg
gephi
global-platform-pro
java-language-server
jd-cli
jetbrains.idea-community
jetbrains.idea-ultimate
kotlin-language-server
ktfmt
lemminx
maven
maven3
ns-usbloader
scenebuilder
schemaspy
slipstream
tabula-java

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/810cmjnzj42zn2b4inv1ksdv5f4rmaly-apache-maven-3.9.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A maven https://github.com/r-ryantm/nixpkgs/archive/447f9d611da6a6ee5a54c75033684591bf25e101.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/447f9d611da6a6ee5a54c75033684591bf25e101#maven

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/810cmjnzj42zn2b4inv1ksdv5f4rmaly-apache-maven-3.9.5
ls -la /nix/store/810cmjnzj42zn2b4inv1ksdv5f4rmaly-apache-maven-3.9.5/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

19 packages built:

cryptomator
dbeaver
digital
forge-mtg
gephi
global-platform-pro
java-language-server
jd-cli
jetbrains.idea-community
jetbrains.idea-ultimate
kotlin-language-server
ktfmt
lemminx
maven
ns-usbloader
scenebuilder
schemaspy
slipstream
tabula-java

Maintainer pings
cc @cko for testing.

@ofborg build java-language-server java-language-server.passthru.tests


Lint for Python files that are not used in any step

Problem
It's possible to add scripts to the steps/ folder which are used in building a step, but not considered part of a step's dependencies.
This happened for UN WPP (#524) and we didn't notice it for a long time. There might be other datasets with this problem too.
Proposed solution
We should add a lint step that scans the steps/data/ folder for these cases and fails in CI if there are any spare Python files that are unaccounted for.

Triaging as "important", since it's a potential correctness issue, and estimating at 1d, since you basically need to create a version of the DAG that extends to the file level.

Since this is important to catch errors, tagging it as "pinned".

Examples in the wild: ``etl/steps/data/garden/energy/*/owid_energy_variable_mapping.csv`

We've lived without it this far, calling it "nice to have"


fix: turn off the alert message on user cancel

What
turn off the alert message on user cancel.
Video
https://user-images.githubusercontent.com/47862474/161610412-2e68aba8-c0a3-4017-8b79-ee581eaaadbd.mp4
Fixes bug(s)

#1477

Part of

https://github.com/openfoodfacts/smooth-app/issues/525
(please be as granular as possible)

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@35457d3). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             develop   #1496   +/-   ##
=========================================
  Coverage           ?   9.07%
=========================================
  Files              ?     158
  Lines              ?    6414
  Branches           ?       0
=========================================
  Hits               ?     582
  Misses             ?    5832
  Partials           ?       0

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 35457d3...e8efba6. Read the comment docs.


Is stackedit is being maintained?

Yeah. It's insane. #1 google search result for "online markdown editor" 6 years of development and then... nothing.

I'm wondering the same thing. I like the editor but don't really want to be using something that isn't being maintained

@benweet what about moving the project under some OSS organization and giving maintainer rights to multiple people? Would that work? I like this project too would love to see it being developed further.

@katomaso Given the license couldn't folks who are interested fork the project into a new org and begin actively maintaining it there?

@katomaso @jsuar -- I'm down for forking to a new repo and hosting in my org. Is there really interest in this?
Might have to disable a bunch of features (pay walls, server side PDF generation, but we could get it going...)

@ortonomy I actually switched to https://github.com/marktext/marktext so I probably wouldn't participate. Thanks for the offer 👍

No worries @jsuar -- just checked out marktext, it's lovely but currently borked on macos and you can't sync to a cloud store, it's all local files... less happy about that.

@ortonomy I hear ya. It was a hell of a search to find a good live markdown editor. Marktext looks nice but does have some annoying bugs. I'm getting around the local files issue by using a Github repo which is less than ideal. I've been floating an idea of integrating some kind of encryption either before pushing to the repo or wrapped around the entire editing process (so I'd have encryption at rest too). I really want to "own" as much of the data so I avoided a lot of the other editors out there. Using a repo or cloud but encrypting before uploading would be pretty sweet. Kind of the local first mindset.

@ortonomy Interested, if you make a fork. First check if there is a good existing fork.

I like the looks of StackEdit, but with the github repo seeing no commits for 14 months, I'm wondering if it's a good choice ?   I've got my account setup, and seems to be syncing with Google Drive just fine, so going to try it out.

@katomaso @jsuar -- I'm down for forking to a new repo and hosting in my org. Is there really interest in this?

Yeah I could be interested

@bendtherules -- good point. But there are 2.4K Forks! what do we do!?

I had this same question, leading me to this issue 1641.  Unfortunately, it was after I started using this that I discovered there is no maintenance at all. I would for sure have interest in a fork of this that would continue its maintenance, as well as the paywall features. If the developer is not active on the project, there should be no payments to use it. Given the age of this issue, I will start looking for another option, especially one that I can share, even if it is restricted to those in a GSuite org.


[Frontend] - Clean editor on workspace change

If user change workspace the workflow editor data must be clean.
If the user has a built workflow on editor page and decide to change workspace we will be rendering a workflow with wrong pieces on editor page.
The backend validation denies the user request to create the workflow but I think it is better to clean the workflow page as well since the current workflow data is useless.
We can add a warning to workspace change if there is any data on workflow editor, something like:
You have an unsaved workflow for this workspace, are you sure you want to change the workspace? Your unsaved workflow will be lost
What you think about it?
@nathan-vm @luiztauffer

I agree with that


add support to change tasks filtering order in ui

As a starting point, we should make it possible to add ascending/descending filter to Started/Updated column.

Closed in #29


[Enhancement] Support type conversion between float text and int

Search before asking

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

Description
Doris can support type conversion for float text to float, and float to int, but cannot support type conversion for float text to int.
See below,

And in mysql, float text can be converted to signed integer.

So I think the float text conversion to int should be supported in Doris.
Solution
support cast('float text' as int)
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

It works on nerieds.


Unable to run example app in widows

When trying to build the windows app getting the following error
D:\flutter_projects\flutter_desktop_webview_auth-main\example\build\windows\packages\Microsoft.Windows.ImplementationLibrary\include\wil\resource.h(2543,38): error C2440: 'specialization': cannot convert from 'overloaded-function' to 'unknown-type' [D:\flutter_projects\flutter_desktop_webview_auth-main\example\build\windows\plugins\desktop_webview_auth\desktop_webview_auth_plugin.vcxproj]
D:\flutter_projects\flutter_desktop_webview_auth-main\example\windows\flutter\ephemeral.plugin_symlinks\desktop_webview_auth\windows\desktop_webview_auth_plugin.cpp(20,10): fatal error C1083: Cannot open include file: 'atlstr.h': No such file or directory [D:\flutter_projects\flutter_desktop_webview_auth-main\example\build\windows\plugins\desktop_webview_auth\desktop_webview_auth_plugin.vcxproj]
Exception: Build process failed.

You have to install ATL library from Visual Studio Installer, see this comment :
https://github.com/mogol/flutter_secure_storage/issues/356#issuecomment-1026828307


[Document Request] Include Comperhensive Documentation on how to change PORT

There are lots of different methods online on how to change the port used by React-Native which is a breaking feature if port 8081 is blocked. There should be a tool created or good documentation that is updated with the steps in order to run React-Native, not on port 8081.
McAfee uses this port and is required on many corporate servers and closing the process is not recommended.
I'd like to see this included in Getting Started // Troubleshooting.

This docs helps you?
$ react-native start --port=8088

https://facebook.github.io/react-native/docs/troubleshooting#using-a-port-other-than-8081


[Feature] Make read access to PICS files public

Feature description
I'm a developer looking into Matter and need to evaluate the Matter Test Harness (for effort and feasibility estimations), but it is impossible to execute any tests since the PICS files are not accessible:

https://groups.csa-iot.org/wg/members-all/document/31907 requires membership
https://github.com/CHIP-Specifications/chip-test-plans is a dead link

Please provide access to the PICS files to non-members (since associate membership is only  for companies that are certifying a product produced by an existing Participant member under the Certification Transfer Program).
Use Cases
[Use Case 1] Possibility to use the Matter TH as regression test framework for a product.
[Use Case 2] We need a clear picture of the efforts involved in testing Matter products before becoming a CSA member.
Test Cases
No response
Additional Information
EDIT: I created this issue as instructed by the CSA, which informed me about the restriction for associate memberships (only available for companies that use the Certification Transfer Program).

Any input would be greatly appreciated.


remove image width/height suggestion

#88 @thedaviddias, I think it's better to just remove the width/height suggestion. It would be nice to have more people's opinions on this, but for me it just causes too much confusion.

What about the fact that all testing tools today flag when width and height are missing (WebPageTest, GTMetrix, Lighthouse...)?

Are you referring to "Serve images that are appropriately-sized to save cellular data and improve load time" (from a Lighthouse audit I just ran)? If so, then I agree that is a useful suggestion.
If you're referring to adding width and height attributes on all img tags, then I don't agree and Lighthouse doesn't seem to flag it either (in my audit I just ran).

@thedaviddias could you paste the message(s) from the audit tool(s) please? That will really help me to understand what the suggestion is.


[main] Include vendor and other changes in update-to-head.sh

As it was, it is missing some vendor changes created by
make generate-release
Signed-off-by: Pierangelo Di Pilato<EMAIL_ADDRESS>

/cherry-pick release-next


Error After Updating Container Station

My QNAP NAS updated container station and I am now getting this error when I try to start the container. This has been running solid since we got it working back in December. Any ideas?

This is an issue with QNAP NAS itself, not with the container.  See https://github.com/jlesage/docker-crashplan-pro/issues/113.

I removed the container and re-downloaded it and now I get an error that the server is not able to connect. I used the command to create the container from #12 that you gave me
docker run -d --name=crashplan-pro-gui-1 -p 5800:5800 -e USER_ID=500 -e GROUP_ID=100 -v /share/CACHEDEV1_DATA/Container/config/crashplan-pro:/config:rw -v /share/CACHEDEV1_DATA:/storage:ro jlesage/crashplan-pro
Is there something that needs to be changed in this now to get it to work properly?

Can you show the exact error you have?

It just says Server Disconnected Code 1006
The container shows as running but I don't know how to see what is going on.

Ah, did you try to clear the browser's cache?

 Sorry to bother you X.X. It was the browser cache and the one thing I didn't think of haha.

Hey no problem.
Great that it's now working!


The template deployment error show that  "pergb2018" is not a valid option for price tier now.

New-AzureRmResourceGroupDeployment : 12:34:33 PM - Resource Microsoft.OperationalInsights/workspaces 'AIAPOC' failed with message '{
"error": {
"code": "BadRequest",
"message": "Pricing tier doesn't match the subscription's billing model. Read http://aka.ms/PricingTierWarning for more details."
}
Noted that i have just executed the same template last week. This option is still valid on last week

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

ID: e7651b7e-278e-2839-e9f4-cee3d8c8d60b
Version Independent ID: 45386b9f-a8e3-a398-c0da-880fbdd76abb
Content: Use Azure Resource Manager templates to Create and Configure a Log Analytics Workspace
Content Source: articles/azure-monitor/platform/template-workspace-configuration.md
Service: log-analytics
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

@ericcwk  Thanks for the Comment. We are actively investigating and will get back to you soon.

Thanks for letting us know on this @ericcwk.
Looks like it is related to https://github.com/MicrosoftDocs/azure-docs/issues/6901 issue. Check if this can help you to resolve the issue.
In other words, the error "Pricing tier doesn't match the subscription's billing model. Read http://aka.ms/PricingTierWarning for more details" is seen if you try to create a log analytics workspace by opting pricing tier as "Per GB" (in Azure portal) or "PerGB2018" (in ARM template) by having your subscription currently in an older pricing model (with access to multiple pricing tiers). To resolve the error, change the monitoring pricing model from the subscription on the Pricing model selection page under Monitor > Usage and estimated costs.
Please find below screenshots for reference.

@ericcwk At this point it appears that there's no edits or updates needed for the documentation. Closing this issue for now. If there are further questions regarding this matter or questions or feedback on the documentation, please do let us know and we will gladly continue the discussion.


merge docker and vm configs

[ ] provisioning
[ ] settings.py
[ ] fixtures
[ ] SECRET_KEY
[ ] ansible simplification
[ ] docker as artifact?

See GH-94


An error when I run pip install -e .

Hi, I'm new to qlever-control, and I'm testing the qlever performances with my ttl data.
I added a new Qleverfiles in /src/qlever/Qleverfiles (for my data), and I want to revuild qlever-contol but it doesn't work.
I made a new Qleverfile like below:
# Qleverfile for hike, use with https://github.com/ad-freiburg/qlever-control
#
# qlever index
# qlever start

[data]
NAME         = hike
DESCRIPTION  = hike address data

[index]
INPUT_FILES     = address.ttl.gz
CAT_INPUT_FILES = zcat ${INPUT_FILES}
SETTINGS_JSON   = { "ascii-prefixes-only": true, "num-triples-per-batch": 10000000, "parallel-parsing" : true" }
STXXL_MEMORY    = 10G

[server]
PORT               = 7001
ACCESS_TOKEN       = ${data:NAME}
MEMORY_FOR_QUERIES = 20G
CACHE_MAX_SIZE     = 10G

[runtime]
SYSTEM = docker
IMAGE  = docker.io/adfreiburg/qlever:latest

[ui]
UI_CONFIG = hike

After making a new Qleverfile, I run the below codes but I got an error.
cd qlever-control
pip install -e .

The error said there is no setup.py. How can I rebuild qlever-control?
ERROR: File "setup.py" not found. Directory cannot be installed in editable mode: /home/hike/qlever/qlever-control
(A "pyproject.toml" file was found, but editable mode currently requires a setup.py based build.)

I updated pip version, and solved it!


Fix capabilities check

Proposed change(s)
fixed path
Useful links (GitHub issues, forum threads, etc.)

Types of change(s)

[*] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Code refactor (non-breaking change which refactor the code)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update only
[ ] Other (please describe)

Testing and Verification

1st command
2nd command
...

Test Configuration
Mini Pupper Version

Raspberry Pi OS version

Checklist

[*] I have read the CONTRIBUTING guidelines.
[*] I have checked to ensure there aren't other open Pull Requests for the same change.

Other comments

wrong PR


Update copyright year in README.md

Update the copyright year from 2023 to 2024.
CLA: trivial

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

This would be updated before release automatically. But I assume it is OK to update it also on the master branch by this PR.

OK with CLA: trivial

This PR is in a state where it requires action by @openssl/committers but the last update was 30 days ago

This PR is no longer viable, as the copyright was updated during our release of 3.3.0-alpha1, on the 20th of March.


Android platform FD leak

Hi
When we used Flutter on Android platform, some crashes occurred. We checked and found that it was caused by FD leakage. Every time we opened a new page of Flutter, FD would increase.Android has limits on FD, which can cause a crash if exceeded.
We found that only Mail's GPU architecture caused this problem. Mali (GPU)

This is the log of fd growing all the time.
Can you help us fix this problem? thanks  (=^_^=)
flutter doctor

I also meet this crash
so serious
pls fix this asap!!!!

Hi @Carpeiem007
Unfortunately, the version you're using is outdated and is no longer supported, it's not feasible to provide any bug fixes for such an old version of Flutter.
I kindly advise you to update to the latest Fluter stable, if you encounter this issue, please comment below with the details from the latest stable, including steps to replicate the issue.
Can you please upgrade to the latest  stable and try again
Execute the following commands to upgrade
flutter channel stable
flutter upgrade --force
flutter doctor -v
If the problem persists, can you please provide your flutter doctor -v with the upgrade, complete reproducible minimal code sample, and complete flutter run --verbose logs running the minimal code sample?
Thank you

Hi @Carpeiem007
Unfortunately, the version you're using is outdated and is no longer supported, it's not feasible to provide any bug fixes for such an old version of Flutter.
I kindly advise you to update to the latest Fluter stable, if you encounter this issue, please comment below with the details from the latest stable, including steps to replicate the issue.
Can you please upgrade to the latest stable and try again
Execute the following commands to upgrade
flutter channel stable
flutter upgrade --force
flutter doctor -v
If the problem persists, can you please provide your flutter doctor -v with the upgrade, complete reproducible minimal code sample, and complete flutter run --verbose logs running the minimal code sample?
Thank you

I used 2.2.3-stable version without this problem, but I would like to ask, what caused it? Can you tell me? Can I fix it if I don't upgrade it? We cannot upgrade the version at this time.

@Carpeiem007
We can investigate the cause if it reproduces on the stable.
Given your last message I feel safe to close this issue, if you disagree please write in the comments and I will reopen it.
Thank you


ver 2.0a - Displaying artist info on click (server side+components+store), css in progress

Merged after confirming it's okay to do so. :p


Return tuple-structs from db methods where necessary

I have taken to using the pattern of using a tuple-struct to contain a tuple of data types that will be used to create a response type with From.
I would like to return these from DB methods instead of the current un-annotaetd tuple.
Ideally, everything in the routes directory should be able convert directly to the desired response using From::from().

I switched to returning normal structs from db methods instead.


[native_pdf_renderer] Windows implementation

I believe this windows implementation implements all functionality currently supported by native_pdf_renderer

The files failing the formatting CI stage are the unedited windows example bootstrapping files generated by the flutter tool. Could re-format them but excluding them from the CI format stage may a better option.

@Jon-Salmon thanks for you contribution!

@Jon-Salmon after check i got error:

from here
https://github.com/rbcprolabs/packages.flutter/blob/ba142a8934cd858cce5252467ddd618e2da34b6d/packages/native_pdf_renderer/windows/DownloadProject.cmake#L179
verbbose:

Flutter:
Flutter 2.0.5 • channel stable • https://github.com/flutter/flutter.git
Framework • revision adc687823a (13 days ago) • 2021-04-16 09:40:20 -0700
Engine • revision b09f014e96
Tools • Dart 2.12.3

System:
version: win10 20H2
build: 19042.928

For next i see not exists binary in releases

and replace here
https://github.com/rbcprolabs/packages.flutter/blob/ba142a8934cd858cce5252467ddd618e2da34b6d/packages/native_pdf_renderer/windows/CMakeLists.txt#L13
link to latest stable release with binary for windows
https://github.com/bblanchon/pdfium-binaries/releases/download/chromium%2F4475/pdfium-windows-x64.zip
run and got a another error:

"выход из программы" - exit from programm
"с кодом" - with code
but my another flutter windows application works normally on it PC:

hmm, works only when i run with administrator privilegies

Good spot with the pdfium releases, could go for something like this https://github.com/Jon-Salmon/packages.flutter/commit/c4d54cc7c70d53e909539b82e8a0502992b37fb6 (inspired by the flutter printing package).
I didn't find that I needed to run as admin, I can try things next week.


Problem running on iPod Touch

Hi,
The extension runs fine on all devices I've tested so far but the iPod Touch, when the user logs in (or if it's already logged on) the Game Center, it throws an exception:
AudioStreamBasicDescription:  2 ch,  44100 Hz, 'lpcm' (0x00000029) 32-bit little-endian float, deinterleaved
2015-04-25 21:27:13.637 xxx[187:907] Game Center is available
2015-04-25 21:27:13.650 xxx[187:907] Game Center is available
2015-04-25 21:27:13.655 xxx[187:907] Game Center is available
2015-04-25 21:27:13.662 xxx[187:907] Authenticating local user...
2015-04-25 21:27:13.797 xxx[187:907] Game Center is available
2015-04-25 21:27:13.803 xxx[187:907] Authenticating local user...
2015-04-25 21:27:17.459 xxx[187:907] Game Center: You are logged in to game center.
2015-04-25 21:27:17.559 xxx[187:907] -[GKPlayerInternal generateIdentityVerificationSignatureWithCompletionHandler:]: unrecognized selector sent to instance 0x1f5b0e30
2015-04-25 21:27:17.568 xxx[187:907] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[GKPlayerInternal generateIdentityVerificationSignatureWithCompletionHandler:]: unrecognized selector sent to instance 0x1f5b0e30'
*** First throw call stack:
(0x336992a3 0x3b31997f 0x3369ce07 0x3369b531 0x335f2f68 0x3b73111f 0x3b7304b7 0x3b731dcb 0x3366cf3b 0x335dfebd 0x335dfd49 0x371922eb 0x354f5301 0x88a4d 0xc83f9 0x782223 0x79c189 0x73f6e1 0x7573e7 0x759e93 0x79155f 0x75023 0x3b750b20)
libc++abi.dylib: terminate called throwing an exception
Hope it can be helpful to solve this issue.
If you need anything else just let me know.

Can you include what iOS version you are using and what generation iPod Touch?

@haysclark sure, sorry for the delay. iPod Touch 4th generation, iOS 6.1.6, please let me know if there is anything else I can do to help.

This seems to be an iOS 6 problem, i also get the crash on an iPhone 4 with iOS 6.0.1


Get android to build again

Changes that had to be made:

Remove JAVA_HOME variable as openjdk gets added to path automatically at least for adoptium, and because it's installed to "C:/Program Files" you can't get the jdk commands to work because of the white space in the path.

Updated commands to use d8 and jrt (with relative path since JAVA_HOME is gone)

The xcopy command wouldn't work for me with the full path, it kept saying too many arguments or something? it works on cmd by itself though.

There were lots of other problems that I came across while doing this, for example some android emulator targets wouldn't load (29, 30) while older ones and 33 did work. Also there's a comment somewhere saying raylib supports target 29 but I kept getting incompatible abi errors, maybe that was the emulator though. The only one I got to compile was 33 here https://cdn.discordapp.com/attachments/1065746993592422400/1131328440709156964/image.png.
For some reason the make process doesn't finish by itself and you have to use ctrl-c even though it was successful?
I'm not using android myself right now just wanted to save others some time, it would be more interesting for me if raylib supported older targets as those emulators run much more smoothly. I'm not sure why the minimal target is at 29/android 10?
Lastly, I don't know enough about android to review this PR https://github.com/raysan5/raylib-game-template/pull/21/files so I can't help with that. I only needed the d8 command from it.

@lesleyrs Not sure if this assumption will work for all users:

Remove JAVA_HOME variable as openjdk gets added to path automatically at least for adoptium

It could be that users rely on another Java installation and not OpenJDK, so not sure how safe is assuming those tools will be in the system path...

I reviewed the other related PR and it seems there are multiple conflics so I decided to keep the previous one.


AppCrash using Power Button on taskbar to shut down VM

When pressing and holding the Power button and then selecting to Shut Down the VM, it starts to shut down and then hangs until I click on the window.  When I cluck on the window I get the following error:
Problem Event Name:	APPCRASH
Application Name:	LeapdroidVM.exe
Application Version:	<IP_ADDRESS>
Application Timestamp:	57e9aa1e
Fault Module Name:	LeapdroidVM.exe
Fault Module Version:	<IP_ADDRESS>
Fault Module Timestamp:	57e9aa1e
Exception Code:	c0000005
Exception Offset:<PHONE_NUMBER>0224d6
OS Version:	6.1.76<IP_ADDRESS>.256.48
Locale ID:	1033
Additional Information 1:	a6fd
Additional Information 2:	a6fd894d80d400a88a34b8cba82a7919
Additional Information 3:	835c
Additional Information 4:	835cecfeb866ae094c0e55388222affc

On another VM that I created, same problem just a different error:
**Problem signature:
Problem Event Name:	APPCRASH
Application Name:	LeapdroidVM.exe
Application Version:	<IP_ADDRESS>
Application Timestamp:	57e9aa1e
Fault Module Name:	VBoxVMM.dll
Fault Module Version:	<IP_ADDRESS>49
Fault Module Timestamp:	57a40004
Exception Code:	c0000005
Exception Offset:<PHONE_NUMBER>12bf56
OS Version:	6.1.76<IP_ADDRESS>.256.48
Locale ID:	1033
Additional Information 1:	e4f2
Additional Information 2:	e4f283b89154711fb5eb9a3d7ffbb02e
Additional Information 3:	55f3
Additional Information 4:	55f30cf1f36c87f10dc9178564a8d388


Set user agent string for gcloud

for analytics tracking:

Figure out what user agent string we want (e.g. gcloud-eclipse)
Set the environment variable "CLOUDSDK_METRICS_ENVIRONMENT" to "gcloud-eclipse" or whatever) when invoking gcloud

see https://github.com/GoogleCloudPlatform/gcloud-intellij/blob/master/google-cloud-tools-plugin/src/com/google/cloud/tools/intellij/appengine/cloud/AppEngineAction.java#L89

Please make sure this works on Mac and Windows too.


Step 3 error

When I run this command:
python -u tools/train_detic.py --config-file projects/Detic/configs/ovd/Detic_V3Det-OVD-Base_IN_CLIP_R5021k_640b64_4x_ft4x_max-size.yaml --num-gpus 4
It will work normally for a while but at some point it will report an error：
Traceback (most recent call last):
File "train_detic.py", line 292, in
launch(
File "/root/autodl-tmp/detectron2/engine/launch.py", line 67, in launch
mp.spawn(
File "/root/miniconda3/lib/python3.8/site-packages/torch/multiprocessing/spawn.py", line 240, in spawn
return start_processes(fn, args, nprocs, join, daemon, start_method='spawn')
File "/root/miniconda3/lib/python3.8/site-packages/torch/multiprocessing/spawn.py", line 198, in start_processes
while not context.join():
File "/root/miniconda3/lib/python3.8/site-packages/torch/multiprocessing/spawn.py", line 140, in join
raise ProcessExitedException(
torch.multiprocessing.spawn.ProcessExitedException: process 0 terminated with signal SIGSEGV
root@autodl-container-52ea4dbaa0-6c92efdf:~/autodl-tmp# /root/miniconda3/lib/python3.8/multiprocessing/resource_tracker.py:216: UserWarning: resource_tracker: There appear to be 128 leaked semaphore objects to clean up at shutdown
warnings.warn('resource_tracker: There appear to be %d '
What am I supposed to do?

It is hard to decide the exact error with your information. Can you try to run with single GPU and debug mode with the following command:
CUDA_LAUNCH_BLOCKING=1 python -u tools/train_detic.py --config-file projects/Detic/configs/ovd/Detic_V3Det-OVD-Base_IN_CLIP_R5021k_640b64_4x_ft4x_max-size.yaml --num-gpus 1

@yhcao6
I will get this report:
Traceback (most recent call last):
File "tools/train_detic.py", line 292, in
launch(
File "/root/autodl-tmp/detectron2/engine/launch.py", line 82, in launch
main_func(*args)
File "tools/train_detic.py", line 271, in main
do_train(cfg, model, resume=args.resume)
File "tools/train_detic.py", line 172, in do_train
for data, iteration in zip(data_loader, range(start_iter, max_iter)):
File "/root/autodl-tmp/projects/Detic/detic/data/custom_dataset_dataloader.py", line 297, in iter
for d in self.dataset:
File "/root/miniconda3/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 628, in next
data = self._next_data()
File "/root/miniconda3/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 1313, in _next_data
return self._process_data(data)
File "/root/miniconda3/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 1359, in _process_data
data.reraise()
File "/root/miniconda3/lib/python3.8/site-packages/torch/_utils.py", line 543, in reraise
raise exception
IndexError: Caught IndexError in DataLoader worker process 1.
Original Traceback (most recent call last):
File "/root/miniconda3/lib/python3.8/site-packages/torch/utils/data/_utils/worker.py", line 302, in _worker_loop
data = fetcher.fetch(index)
File "/root/miniconda3/lib/python3.8/site-packages/torch/utils/data/_utils/fetch.py", line 58, in fetch
data = [self.dataset[idx] for idx in possibly_batched_index]
File "/root/miniconda3/lib/python3.8/site-packages/torch/utils/data/_utils/fetch.py", line 58, in
data = [self.dataset[idx] for idx in possibly_batched_index]
File "/root/autodl-tmp/detectron2/data/common.py", line 90, in getitem
data = self._map_func(self._dataset[cur_idx])
File "/root/autodl-tmp/detectron2/data/common.py", line 154, in getitem
start_addr = 0 if idx == 0 else self._addr[idx - 1].item()
IndexError: index<PHONE_NUMBER>26735 is out of bounds for axis 0 with size 537492

It seems an error about the dataset index error, but I didn't met that error before. By my experience there are two possible solutions:

Decrease the batchsize, change  this line to DATASET_BS: [8, 32]
https://github.com/V3Det/Detectron2-V3Det/blob/7005952ea3a9eafea901b482f7fc8289b43de1cb/projects/Detic/configs/ovd/Detic_V3Det-OVD-Base_IN_CLIP_R5021k_640b64_4x_ft4x_max-size.yaml#L31
Decrease dataloader num workers, change this line to NUM_WORKERS: 1
https://github.com/V3Det/Detectron2-V3Det/blob/7005952ea3a9eafea901b482f7fc8289b43de1cb/projects/Detic/configs/ovd/Detic_V3Det-OVD-Base_IN_CLIP_R5021k_640b64_4x_ft4x_max-size.yaml#L39


Test page: Added share option

It can be quite useful to share a link to the test page with a specific language but it wasn't possible to share the highlighted text as well.
This PR adds a "Share" link to the test page. The link points to the test page with the current language + text in the URL hash. The link is automatically updated after changes to the current language or text.
Example

The href of the "Share" link is #language=markup&text=%3Cb%3Efoo%3C%2Fb%3E.

I like this idea; would be helpful for people to file bugs too. Can we update the bug template to include suggesting a link to this page?

In this case, I should probably replace the link with a button that copies the link into the user's clipboard.

I added a little popup around the link.


Converting .when Guarded Namespaces

A mixin such as @mixin flex-wrap($fw) when ($fw = wrap) { in less doesn't convert over.

#11 is a duplicate but has more detail so closing this one.


DeprecationWarning: SingleEntryPlugin was renamed to EntryPlugin - ReactJS start/build

Bug report

What is the current behavior?
When i run start or build reactjs script i have:
DeprecationWarning: SingleEntryPlugin was renamed to EntryPlugin
If the current behavior is a bug, please provide the steps to reproduce.

Eject create-react-app
Update webpack from v.4.42.0 to v.5.1.3
Run npm start or npm run build

What is the expected behavior?
The launch of the ReactJS dev server was expected.

Other relevant information:
webpack version:  5.1.3
Node.js version: 13.13.0
Operating System: OS X El Captain v.10.11.6
Additional tools: -

Fix the deprecation, answer in the deprecation message:
DeprecationWarning: SingleEntryPlugin was renamed to EntryPlugin

You need to report about this to create-react-app, sorry, we can't fix it on our side


Fix recipe tests for TransformerASR

This PR fixes the recipe tests for TransformerASR, which broke after merging https://github.com/speechbrain/speechbrain/pull/2262. The reason is that, when using the full encoder-decoder model we set memory_mask=src_mask, which seems incorrect. The expected shape for memory_mask is [target_sequence_length, source_sequence_length], while the expected shape for src_mask is [source_sequence_length, source_sequence_length]. The tests were not failing before merging https://github.com/speechbrain/speechbrain/pull/2262 because src_mask was hardcoded as None (which is the default value for causal=False).

I ran the recipe tests and everything seems to work. Thank you @lucadellalib


Copy to clipboard feature for code block

I adapted a solution for a "copy to clipboard" icon for code blocks from here.
It's up to date with #148. Consider merging that one first. Enjoy the demonstration below.

:)

No problem at all. Thanks for the excellent project, as I found it 😁


thumbnailCard title too long will be ellipsis

I used thumbnailCard with long title.
The Text will be ellipsis if the text in title is too long.
Is there any options to change  thumbnailCard title style for this case

Hi @NoDirective, unfortunately it looks like titles have a max length of 20 in the Bot Framework SDK. Allowing Web Chat to change the styling of the title would not increase the allowable text. As it stands, this is not a feature our team will be implementing in the immediate future.

Hi @corinagum
Thank you for your answer.
I am sorry that I did not describe my question clearly.
The title of thumbnailCard  is showed with ellipsis.
And in Devtools , I could see all text of the title .
Is there any options to change thumbnailCard title style for this case.
So I could see the all of them , no by ellipsis.

@NoDirective,. thanks for the extra detail!
It turns out the max character length is completely arbitrary and does not apply to this situation. :) sorry for my incorrect statement above.
Since there is no character limit, the details you have provided appear reasonable. I'm going to edit your original message with the details you provided and add this to our Backlog for future triage.


test for .ts files not working

Acknowledgements

[X] I read the documentation and searched existing issues to avoid duplicates
[X] I understand this is a bug tracker and anything other than a proven bug will be closed
[X] I understand this is a free project and relies on community contributions
[X] I read and understood the Contribution guide

Minimal reproduction URL
https://stackblitz.com/edit/node-hzy2ii?file=package.json,bar.test.ts
Problem & expected behavior (under 200 words)
When you run tsx --test , the file bar.test.ts is not executed.
https://tsx.is/node-enhancement#test-runner
Bugs are expected to be fixed by those affected by it

[ ] I'm interested in working on this issue

Compensating engineering work will speed up resolution and support the project

[ ] I'm willing to offer $10 for financial support

Same here, specifying file path patterns through shell or using explicit filename works ok.
Reverting to .js files for tests for now

how did you manage to solve with file path pattern?
i tried both tsx --test **/*.test.?[cm][jt]s and tsx --test '**/*.test.?[cm][jt]s' without success.
Thank you

@ficu88 are you on a version of Node before v21? I'm on v20 and get the same behavior.
From the description in the PR that adds test runner support, the feature only works on Node v21 and above.
If that's correct, perhaps the "fix" is to amend the docs to mention the Node version requirements for the test runner integration.
Side note for the maintainer: Respectfully the two comments marked as off-topic were helpful for me. For those who can't upgrade to Node v21+ any workaround is useful!

are you on a version of Node before v21?

See the reproduction Node version:
❯ node -v
v18.20.3

If that's correct, perhaps the "fix" is to amend the docs to mention the Node version requirements for the test runner integration.

Happy to accept a PR, would you be open to working on one?

Respectfully the two comments marked as off-topic were helpful for me. For those who can't upgrade to Node v21+ any workaround is useful!

As a maintainer, my priority is to serve sponsors first, then contributors, and finally users.
For sponsors needing a workaround, I'm happy to offer support directly via the sponsors-only repo.
The Issues tab is a place for contributors to collaborate and fix bugs to benefit all tsx users, and it's distracting/unproductive when the thread is polluted with workaround noise by non-contributors.

I opened #665 but I couldn't find any instructions for how to contribute to docs specifically. So I don't know how to validate my changes.
I maintain a completely free open source library on my own time so it's not realistic for me to sponsor. I'm sure there are many others in similar situations who are really happy with tsx, but can't upgrade their node version for whatever reason.
So for those people here's what I used until I can upgrade Node.js and make use of the built-in support in tsx. And who knows, it might be useful as inspiration for a similar feature in this repo.
// test/index.ts
import { glob } from 'glob'
import { run } from 'node:test';
import { spec } from 'node:test/reporters';
import { fileURLToPath } from 'url';

// Replacement for tsx's "test runner" feature until we can upgrade the project's minimum Node.js version to v21+.
// https://github.com/privatenumber/tsx/issues/663
const parentDir = fileURLToPath(new URL('./', import.meta.url));
const files = await glob(`${parentDir}/**/*.test.ts`)

run({files})
  .on('test:fail', () => {
    process.exitCode = 1;
  })
  .compose(new spec())
  .pipe(process.stdout);

Then tsx works splendidly with npx tsx test/index.ts

Yeah, feel free to open a PR to update the docs.
Explanation is in the PR: https://github.com/privatenumber/tsx/pull/410#issue-2007959217