Cannot show repository contents

Connect to gitlist server and get list of repositories.  Click on a repository and get a 500 error.
/var/log/apache2/error.log contains
[Tue Oct 02 14:23:51.749873 2018] [php7:error] [pid 2692] [client <IP_ADDRESS>:58977] PHP Fatal error:  Cannot use 'Object' as class name as it is reserved in /var/www/gitlist/vendor/klaussilveira/gitter/lib/Gitter/Model/Object.php on line 14, referer: http://<IP_ADDRESS>/gitlist/

Ubuntu 18.04.1 in VMware Fusion 10.1.3 VM running on Mac OS 10.13.6

See #765.


Support individual setup of model and optimizer in Lite

What does this PR do?
This PR is providing new APIs for setting up model and optimizers to enable FSDP in #14967.
The design considerations were discussed here.
Before:
Model and optimizers had to be set up jointly.
model = ...
optimizer = Adam(model.parameters())
model, optimizer = self.setup(model, optimizer)

Now:
Jointly setting up model and optimizer is still possible.
model = ...
optimizer = Adam(model.parameters())
model, optimizer = self.setup(model, optimizer)

For some strategies, this is the only way possible (DeepSpeed).
However, there are strategies (FSDP) that require to set up the model first before the optimizer can be created:
model = ...
model = self.setup_model(model)

optimizer = Adam(model.parameters())
optimizer = self.setup_optimizers(optimizer)

This PR introduces these two new APIs setup_model and setup_optimizers and the error messaging for which strategies support which setup procedure.
Does your PR introduce any breaking changes? If yes, please list them.
No.
Before submitting

[x] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[x] Did you make sure to update the documentation with your changes? (if necessary)
[x] Did you write any new necessary tests? (not for typos and docs)
[x] Did you verify new and existing tests pass locally with your changes?
[x] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
I made sure I had fun coding 🙃

This PR is a preparation for #14898. I think it will make most sense to add the docs there for full context.


Fix package

Load cl-lib for using its functions and macros.
Add Package-Requires header for dependency. This is required when installing this package with package.el
Clean up Cask file

@syohex thank you very much for the fix! :)

Just linking this PR with the submission on MELPA and the corresponding issue. :)

https://github.com/milkypostman/melpa/pull/3199
#93


core: Create a Gawk requirement.

[X] Have you followed the guidelines in our Contributing document?
[X] Have you checked to ensure there aren't other open Pull Requests for the same change?
[X] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

In response to #27

Original issue over here: Original issue over here: https://github.com/Linuxbrew/linuxbrew/issues/953

Even CentOS 5, the oldest distro that I know of supported by Linixubrew, satisfies the version requirement, so I feel that doing the version check is overkill. The code can be simplified to a few lines by removing the version check, and simplifies the tests as well.
class GawkRequirement < Requirement
  fatal true
  default_formula "gawk"
  satisfy { which("gawk") }
end

glibc is the only package that will use this requirement due to the bootstrapping issue—others can simply depend_on "gawk"—so I'd suggest pulling this requirement into the glibc formula.

As you wish!

New approach at https://github.com/Linuxbrew/homebrew-core/pull/231

Thanks, Piotr.


Add ci coverage check

Closes #873
Review Checklist

Tests were added to cover all code changes
Documentation was added / updated
Code and tests follow standards in CONTRIBUTING.md

Ambrus, I know this PR is experimental, so I want to thank you for trying this out before offering my feedback. My comments are on the project, not your work :)

I don't support line-level semantic comments, especially to this extent. It's a clutter on the codebase and an abuse of the purpose of having test coverage in the first place. In my opinion attempting to artificially jump to 100, then measuring the drop, is worse in any meaningful way than simply measuring the drop from an honest percentage.
For what it's worth, I would be a bit more amiable to class- or file-level exclusion comments, that isolate entire swathes of functionality. That's at bit more honest and clearly stated, as opposed to "it's inconvenient that this error handling line is not covered".
It's very tempting to use technical solutions to a social problem. In the software engineering industry this is almost always a mistake. I assert that "we have more priorities than code coverage alone" is a social problem, and "sprinkle comments on hundreds of lines to bump a metric" is a technical solution.
I also don't think the stated purpose of cover 100 is pragmatic or realistic. Right now that's at 357 occurrences - a whopping 4% of the code base - which makes me think that "Not meant for further use - existing exclusions are considered TODOs" is unlikely to remain true.
Overall this gets a strong :-1: from me.

@ambrussimon-invenshure Thanks for the PR. 👍
@kofalt
I want a culture where tested code is the default. I want to lean on tools to predictably and consistently promote that culture. I want opting code out of coverage to be visible and explicit.
I view this PR as an effective means to achieve the above.

I don't support line-level semantic comments, especially to this extent. It's a clutter on the codebase and an abuse of the purpose of having test coverage in the first place.

Could you help me understand the extend of your objection here? Is it specifically semantic comment on the same line as the code? Is there a more appealing approach to mark individual lines?

In my opinion attempting to artificially jump to 100, then measuring the drop, is worse in any meaningful way than simply measuring the drop from an honest percentage.

Measuring a drop in percentage means coverage rates for new development needs to be just as good/bad as the old.

For what it's worth, I would be a bit more amiable to class- or file-level exclusion comments, that isolate entire swathes of functionality. That's at bit more honest and clearly stated, as opposed to "it's inconvenient that this error handling line is not covered".

Skipping existing files/modules does nothing to encourage future development within that file/module to be covered.

It's very tempting to use technical solutions to a social problem. In the software engineering industry this is almost always a mistake. I assert that "we have more priorities than code coverage alone" is a social problem, and "sprinkle comments on hundreds of lines to bump a metric" is a technical solution.

The goal is not to achieve 100% coverage for the sake of stating we have 100% coverage.  The goal is to move forward with higher standards for new development.

I also don't think the stated purpose of cover 100 is pragmatic or realistic. Right now that's at 357 occurrences - a whopping 4% of the code base - which makes me think that "Not meant for further use - existing exclusions are considered TODOs" is unlikely to remain true.

I agree with the sentiment. We should be honest about what skipped lines we consider important enough for covering in the next 1-3 months, and use a phrase more specific than cover 100 for those, and use no cover for the chaff.

I want a culture where tested code is the default. I want to lean on tools to predictably and consistently promote that culture.

I think this speaks to the heart of the "solve a social problem with a technical solution" anti-pattern.
My guess is that a lot of projects have those goals, yet very few have adopted something like this strategy.
Offhand, I've never heard of someone doing this. It strikes me as very strange.

Could you help me understand the extend of your objection here?

My objection is with line-level exclusions. No coverage exclusion is great to my mind, but ranked in descending order of palatability: file, class, branch, line. My link above shows one example of my reasoning.
This information is already exposed by better tools that do not require re-implementing a highlighter by hand.

Measuring a drop in percentage means coverage rates for new development needs to be just as good/bad as the old.

Agreed. This is true for both strategies, if I'm understanding you correctly.

Skipping existing files/modules does nothing to encourage future development within that file/module to be covered.

Agreed! This is why I don't like coverage exclusions. Exclusions should be a "throw up our hands, this will never be tested because of effort level / state of the universe" last resort. Not a #TODO.
I think it's noteworthy that a few test frameworks I've ran across don't support exclusions at all, by design. To quote the internet: "Code coverage tells you what you definitely haven't tested, not what you have."

The goal is to move forward with higher standards for new development.

I don't see how this change helps us do that.
I submit that there is no useful advantage to be gained moving from having X% coverage and hoping to obtain X+Y, versus having fake-100% coverage and hoping to obtain < 357 exclusion comments.

I completely agree that this solution is far from elegant, but this is a grey area in my opinion. The question I think is whether
a) there is a nicer (but still feasible!) solution at all or
b) the approach is bad enough to offset the intended benefits*

The goal is to move forward with higher standards for new development.

I don't see how this change helps us do that.

I think the goal here (the intended benefit) is enabling enforcement of adding some tests to any new code. Note that file level exclusions leave way more freedom for avoiding this requirement.
Pertaining to a) above, I was also considering the incremental comparison approach, as I agree that is a "more correct" solution. However, there are some drawbacks there, too:

any refactoring (removing code that's better covered than the avg) may lead to decreased coverage
needs more effort* to implement properly (getting previous cov%, local vs CI)

(Regarding 2., this discussion gave me the idea of always comparing to the latest master cov% from coveralls effectively leaving only 1., but I'm sure there could be edge cases/problems with that too, that I just didn't think about yet.)
Again, I'm neither for or against, just trying help with sharing my 50 cents.

I think the goal here (the intended benefit) is enabling enforcement of adding some tests to any new code.

I agree that this PR might help accomplish that goal, but I disagree with the approach. I think we understand each other there :)

However, there are some drawbacks there, too

I agree with your drawbacks - these are some of the reasons our brief usage of coverall's "mark the PR red if % change is > X" was annoying and useless. This, to me, clearly marks a need for the human reviewer to make a human decision using the information at hand.
This is precisely the same as if I had added 500 lines of untested code with 500 # pragma: no cover comments: a human would subjectively review the PR and respond.

We discussed my opinion in a meeting, but I'll summarize here for transparency.
Ambrus I appreciate your work, thank you for taking the time to give us a real, tangible solution to discuss. I'm glad we looked into this option, but I don't believe the reality of the solution is something I would like to move forward with. In an effort to promote higher testing standards for our work we are sacrificing code cleanliness, transparency of actual coverage, and maintainability, but I believe the biggest problem with this solution is it doesn't directly address the problem of gaining more insight into how a PR changes the coverage.
In the meeting, we discussed using a different tool that will give us that insight. It looks like Codecov does a much better job relaying how a PR would change the coverage that exists, most importantly the coverage of the diff itself. I suggest we investigate using this tool and retire the artificial 100% coverage approach.


Truncates string and bytes

I can see that strings/binary gets truncated at 8000 chars/bytes
Use nvarchar(max) and varbinary(max)
Can I avoid that?

Was not it a default behavior of chars/bytes? I am away for now from my PC, but will do look at this soon.

Would you be able to share your model and your schema? I will play around with it.

Maybe it's defaulting in RepoDb.SqlServer/RepoDb.SqlServer/DbHelpers/SqlServerDbHelper.cs
   private int? GetConvertedSize(string type, int size)
        {
            return (size == -1) ? 8000 : size;
        }

No problem, just need to save a file as bytes or base64 string and 8000 bytes are to little.
But really like what you have created, very clever and easy to understand :-)
Prefer this over EF Core any time.
Way to much magic happens in EF Core for me to feel calm...

Basically just any string in the model:
Property
public byte[] RawDocumentData { get; set; }
SQL
[RawDocumentData] VARBINARY(max)  NOT NULL,
or
Property
public string RawDocumentData { get; set; }
SQl
[RawDocumentData] NVARCHAR(max)  NOT NULL,
When I give RawDocumentData a large string or byte array, they gets truncated to 8000 chars/bytes in SQL Server.

Just verified this bug. Will issue a fix on this soon. It will be a part of version >= 1.11.0-beta5.

This issue has been fixed and will be part of the next release (actual, alpha or beta). You are correct on the code-lines where you lead me on the DbHelper of SQL Server. The reason for that was the historic approach on the statement Preparation which always requires the sizes to be in-placed. It may be failing with SDS, but not on MDS.
My integration tests are all pointed to MDS and by removing the introduced lines (size of 8K at the DbHelper) does not give an error anymore. Hope that explains!
Will close this issue once the solution is deployed.

That just great, thank you so much!
Do you have an ETA on a alpha/beta release in Nuget?
Else I can just build it my self so no hurry :-)
Sorry to ask but what does SDS and MDS correlate to? Can't quess it my self and Google can't help so it make sense :o)

The ETA will depends on the existing discussion on the other issues #415. I need to bring this feature on v1.11.0 - so do your reports.
The SDS and MDS are the SQL Server providers (drivers) we used.
SDS = System.Data.SqlClient
MDS = Microsoft.Data.SqlClient

Arh of course, thanks for explaining :-)
I'll keep an eye that issue.
Have fun...!

@Kodestuen - if you can manage building a new binary for yourself, then that is not a problem. But will definitely update this incident once it is deployed.

This is now a part of the latest release RepoDb v1.11.0.
> Install-Package RepoDb -version 1.11.0


Automate PyPI Release

These creds are just for demonstration purposes. If there is an
organizational PyPI account to use or if one of the listed Baseplate
maintainers wants to supply theirs, let's talk!
The hope here is to do smaller incremental releases and publish them to
PyPI. This would allow Reddit projects that are using wheels to make use
of new functionality and bug fixes before doing a fleetwide release.
@spladug, any help you could lend with the credentials would be much
appreciated.

Very cool! Although publishing to public PyPI will not enable faster rollouts internally immediately because we don't use public PyPI for production (for security/reproducibility). But this is a great step in reducing the complexity of releases.
Let's get some creds set up just for CI rather than using any individual's account. That's more bus-proof and locked-down. We can then remove all the humans from the baseplate project on PyPI.
Looking at the travis docs, it looks like we might want to do this step to add bdist into the mix. If I understand right, this would do the build of the thrift manifests before upload and make it so that installing with pip doesn't require a thrift compiler.
Thank you!
:nail_care:

make it so that installing with pip doesn't require a thrift compiler.

Ah! This was one of my goals.

💇

Cool! Just to confirm: has this been tested to work? It might make sense to fire up a second project on PyPI, take the "on: tags" bit off, and test it there to see that the build works and the resultant wheel looks cromulent.

:nail_care:

Quite a bit of flailing here... I was trying to get Travis to work with the test version of PyPI but didn't have any luck. I resulted to temporarily naming the package to test-baseplate.
On a clean VM, I can pip install test-baseplate. It installs just fine but opening an interpreter and attempting to import baseplate fails with an import error related to Thrift. Installing the python-fbthrfit system package fixes this. I'm honestly not sure how to handle that dependency since fbthrift doesn't seem to be installable via pip. The standard thrift package isn't a suitable stand-in as it's layout is different (fbthrift contains thrift.util which is referenced in baseplate.core).
💇


[Data access request]:

What is the name of your project?
RecordLinkage on HPC
What is the purpose of your project?
The purpose of my research project is to compare the accuracy and speed of probabilistic record linkage packages such as Splink with different backend like DuckDB and Spark,fastLink, and RecordLinkage in High performance compute cluster Hyak at the University of Washington inside a container environment to allow Splink to run with Spark backend in a shared compute resource with no root access. Importantly, I want to compare how Splink with Spark as the backend will be able to handle a much larger data set compared to other packages and see how much faster it will be.
Who is involved in the project? Which of these people will have direct access to the pseudopeople input data?
Abraham Flaxman is the supervisor for this research project and will have access to pseudopeople input data
What funding is the project under? What expectations with respect to open access and access to data come with that funding?
This research project is receiving no funding
We commit to:

[x] be responsive to further questions from interested parties
[X] deprecate and replace our version of the pseudopeople input data when a new version is released

What data would you like to request?

[X] Full US
[X] Rhode Island
[ ] Other (may not be available immediately)

Other data - more explanation
No response

So if I'm understanding correctly, the interest is not so much in the content of the dataset as simply testing the general efficiency of different approaches with a dataset with these parameters?

I would like this use this dataset because of its scale and its realistic simulated data that closely resembles real voter registration data that I have been previously used to a smaller scale of around 100k rows (https://www.ncsbe.gov/results-data/voter-registration-data).

So, is that a yes or no re: content versus structure?

I think it is "yes"

Great! All good with me.

Links send via email.


sniffio._impl.AsyncLibraryNotFoundError: unknown async library, or not in async context

[ERROR] Exception in callback <built-in method _loop_task of builtins.CallbackRunnerHTTP object at 0x7f715067de70>
handle:
Traceback (most recent call last):
File "uvloop/cbhandles.pyx", line 61, in uvloop.loop.Handle._run
File "/app/kairon/chat/server.py", line 258, in main
await app.call(scope=scope, receive=receive, send=send)
File "/usr/local/lib/python3.10/site-packages/fastapi/applications.py", line 292, in call
await super().call(scope, receive, send)
File "/usr/local/lib/python3.10/site-packages/starlette/applications.py", line 122, in call
await self.middleware_stack(scope, receive, send)
File "/usr/local/lib/python3.10/site-packages/elasticapm/instrumentation/packages/asyncio/starlette.py", line 48, in call
return await wrapped(*args, **kwargs)
File "/usr/local/lib/python3.10/site-packages/starlette/middleware/errors.py", line 184, in call
raise exc
File "/usr/local/lib/python3.10/site-packages/starlette/middleware/errors.py", line 162, in call
await self.app(scope, receive, _send)
File "/usr/local/lib/python3.10/site-packages/starlette/middleware/base.py", line 29, in call
response_sent = anyio.Event()
File "/usr/local/lib/python3.10/site-packages/anyio/_core/_synchronization.py", line 79, in new
return get_asynclib().Event()
File "/usr/local/lib/python3.10/site-packages/anyio/_core/_eventloop.py", line 147, in get_asynclib
asynclib_name = sniffio.current_async_library()
File "/usr/local/lib/python3.10/site-packages/sniffio/_impl.py", line 93, in current_async_library
raise AsyncLibraryNotFoundError(
sniffio._impl.AsyncLibraryNotFoundError: unknown async library, or not in async context

Looks like you launched Granian with --opt. As described in the readme, some implementations are not compatible with the optimizations, so just keep those optimizations off (as per default).


Nested Tag Helpers

Suggestion submitted by email from<EMAIL_ADDRESS>As we know, for a webcontrol, the properties and sub-properties which types are complex can be set by the nested tag in the control tag. Although we can customize the taghelper like this, it is a little complex to implement this. We think it would be great if the taghelper framework could help us to do some work so that  the developer of a TagHelper has to write less code.
For example, we define mydatagrid taghelper. It has two attributes: headerstyle and rowstyle, whose types are same: DataStyle.
Now in order to use it as the following way, we have to define four taghelpers: mydatagrid, datastyle, headerstyle and rowstyle. In fact headerstyle and rowstyle extends from datastyle. They are almost same except the taghelper name. We also need to write some code to build the relationship between mydatagrid and its nested taghelpers.
<mydatagrid id="grid1">
<headerstyle forecolor="red" />
<rowstyle forecolor="blue" />
</mydatagrid>

We wish we just have to define two taghelpers: mydatagrid and datastyle. Then we just do some settings in the property “headerstyle” and “rowstyle” of mydatagrid, the taghelper framework can help to process the rest. If it can be done, that would be great.
We see that you plan to add support for restricting which elements can show up under a TagHelper and vice versa. That would be perfect for nested taghelper.

How do you use the four tag helpers today? I'm wondering about a single tag helper instead e.g.
[TargetElement("my-data-grid")]
public class DataGridTagHelper : TagHelper
{
    public DataStyle HeaderStyle { get; set; }
    public DataStyle RowStyle { get; set; }

    // ...
}

and
<my-data-grid header-style="new DataStyle(...)" row-style="new DataStyle(...)">
</my-data-grid>

The user wants to be able to specify the values via attribute OR element. Aka HeaderStyle would be settable via attribute: <my-data-grid header-style="..."></my-data-grid> OR `....``

@DamianEdwards

This is an interesting concept but is getting a little too close to XAML for my liking. Putting on the backlog for further consideration in the future. If anybody wants to take a stab at fleshing out the design a little more that would be welcome.

What about something like a menu?

<a href="<EMAIL_ADDRESS>

this will print all
 items for the root menu.
You can get the ChildContent in the taghelper with await context.GetChildContentAsync()
But is there any way to parse the contents as Razor items with a specific model (like ItemType of the asp:Repeater). Is there any way (other than string parsing) to do this with current tag helpers?

Not really, no. Tag Helpers can't generate new members for their content (like item above), however they can mutate state that's passed to them. Code generation is something we're looking to add to Tag Helpers in the next major release after RTM.

So only existing partial views not "new" partials based on child content.
Thanks

What about tables?

    <column for="Type"/>
    <column for="Name"/>
    <column for="Price"/>
    <column>
        Actions
        Remove
    </column>

I'd love to be able to write tag helpers like the one in @newsash 's post, but I think it's different from what the original request is asking (it looks to me that the original request is just to get parameter values from inner elements instead of attributes.) I like this idea way more.

It would be nice to allow to process HtmlContent with any TagHelpers necessary.
E.g. In inside Process/Async
public class CustomTagHelper : TagHelper
{
    public override void Process(TagHelperContext context, TagHelperOutput output)
    {
           // Allow us to force TagHelper processing on content set here
    }
}

Allow us to force any TagHelperContent to be processed by TagHelpers in one of the following ways:
Add a boolean to TagHelperContent.SetHtmlContent
output.Content.SetHtmlContent(@"<input asp-for=""SomeField"">", processTagHelpers: true);

Provide a method to tell Razor to go and process content with any relevant tag helpers:
output.Content.ApplyTagHelpers();

Provide a generic method that lets us decide which TagHelper should be processed, potentially adding any additional attributes
output.Content.ApplyTagHelper<InputTagHelper>(tag =>
{
    tag.Order = 10;
    // Other Properties
});

It would be nice to allow to process HtmlContent with any TagHelpers necessary.
E.g. In inside Process/Async
public class CustomTagHelper : TagHelper
{
    public override void Process(TagHelperContext context, TagHelperOutput output)
    {
           // Allow us to force TagHelper processing on content set here
    }
}

Allow us to force any TagHelperContent to be processed by TagHelpers in one of the following ways:
Add a boolean to TagHelperContent.SetHtmlContent
output.Content.SetHtmlContent(@"<input asp-for=""SomeField"">", processTagHelpers: true);

Provide a method to tell Razor to go and process content with any relevant tag helpers:
output.Content.ApplyTagHelpers();

Provide a generic method that lets us decide which TagHelper should be processed, optionally adding any additional attributes not set in the content
output.Content.ApplyTagHelper<InputTagHelper>()

// Or with optional Tag pre-processing before beign applied
output.Content.ApplyTagHelper<InputTagHelper>(tag =>
{
    tag.Order = 10;
    // Other Properties
});

No plans to do this right now

No plans to do this right now

Does that mean never? No pressure, I just want to know what step to take next. Should I wait and see if this issue comes back alive or do the hard manual labour in the coal mine and write child tag helpers.
I built TagHelper's for Twitter Cards and Open Graph (Facebook) meta tags by hand using properties of complex types. Last week I also released the Schema.NET project which is 1000 machine generated strongly typed POCO's for schema.org. These can be converted to JSON-LD and used in the  section for better SEO (See Google Structured Data). I was waiting to see what happens with this issue before deciding how to write tag helpers for them.
This issue would help with all three sets of tag helpers I outlined above.

@RehanSaeed - There are a few of things here, so I'll try to be specific.
It's very unlikely that we would ever allow you to 'process' chunks of HTML and and turn them into other tag helpers. This is not something we're investigating, and it would be a significant technical challenge to make this work in way that users would be happy with.

One of the other ideas here is that you could opt-in to getting a DOM for the content inside your tag helper, that would make it easier to parse/rewrite. We're super stoked on this idea, but not actively working on it right now.
This whole theme of, "I want to make a tag helper that does something with its inner content" is something we want to make better, but it will happen a long time from now.

Most of our immediate investments in Razor will be focused on improving our tooling in the short term, we have some catching up to do. We'll be ready to start talking about actual runtime features in maybe 6 months from now, and shipping them in 3.0. That's not a promise of any specific thing getting delivered, that's when we're ready to start prioritizing this work.
Everyone will hopefully get to see a list of our 2.1 planning items soon for some definition of soon. Right now we're still going through the 2.0 release process.

Sounds interesting, I'll sit tight and wait for some magic.


[bug] when send transaction on mobile does not redirect to metamask , which will navigate to the app store

Is there an existing issue for this?

[X] I have searched the existing issues

RainbowKit Version
0.12.7
wagmi Version
0.12.9
Current Behavior
redirect to app store
Expected Behavior
redirect to metamask
Steps To Reproduce
No response
Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
No response
Anything else?
No response

@chungit201 This is unfortunately an issue with MetaMask's Universal Link and Safari. Most wallet providers will display a fallback page in the scenario where the Universal Link redirect fails, but MetaMask instead redirects to the App Store. Failures are typically triggered by using the "Open in New Tab" button in Safari during a dApp WalletConnect flow, which triggers Safari to prevent Universal Link redirects for that app in the future. This can be disabled by using the "Open in MetaMask" button the next time you encountered a MetaMask Universal Link, including with the "WalletConnect" modal that can be accessed from within RainbowKit. An upcoming migration to Deep Links for wallets like MetaMask will mitigate this.


#1611: rewrite LocalDateAssert, LocalDateTimeAssert, LocalTimeAssert, OffsetDateTimeAssert test classes to use assertThatAssertionErrorIsThrownBy

Check List:

Fixes #1611
Unit tests : NA
Javadoc with a code example (on API only) : NA

Thanks for the PR @cgrabmann!

Integrated thanks @cgrabmann!


DASHBUILDE-217: Make it impossible to to open multiple NavItemEditor …

…inputs
The proposed solution is to add handler for BlurEvent, which is fired when the input field loses focus (when user clicks away or starts editing another item in the nav tree).

onBlur causes some side effects like:
1.- Clicking on another item should finish edition in previous one and start in the new one.
2.- It is not possible to elect another entry in the perspective dropdown.
I think the solution should be based on NavTreeEditor coordinating the opening/closing of its children NavItemEditor's.

Proposed alternative solution. NavTreeEditor now has new field which remembers currently edited item. when opening new item previously edited item edition is stopped.
TODO - I'll add test soon.

@jhrcek is this ready to merge already?

@dgutierr Yes, ready to merge if you agree with the changes.

Merged.


Fix typo

A minor nitpick: since "goodbye" is one word, "bye" shouldn't be capitalized.
But otherwise, this is a huge improvement over psql!

:+1: Thanks for the PR @davidcelis.
:tractor:

✨

👍


Configuration to load schema from github

Is your feature request related to a problem? Please describe.
I use the graphql-codegen cli to generate TypeScript types, etc, for my GraphQL schema. graphql-codegen is able to load the schema from GitHub using @graphql-tools/github-loader.
https://github.com/dotansimha/graphql-code-generator/blob/92fdaf4c518cc321fe51d98b82181592f61db485/packages/graphql-codegen-cli/src/graphql-config.ts#L18
I've defined the schema in my .graphqlrc.yaml file to load the schema from GitHub using the following config
documents: graphql/**/*.graphql
schema:
  - 'github:organisation/repository#develop:schema.graphql':
      token: ${GITHUB_TOKEN}
extensions:
  codegen:
    generates:
      ...

This works great, and I'm able to generate what I need..
I'm also using the VSCode GraphQL Extension, which in turn uses the graphql-language-service-server, which in turn uses graphql-config to load my .graphqlrc.yaml file.
However, it doesn't look like it's able to load the schema as I've defined it in my config. Instead I see the following message in the output for the GraphQL Language Server..
graphql-language-service-usage-logs: WARNING: graphql-config error, only highlighting is enabled:
fetch failed
for more information on using 'graphql-config' with 'graphql-language-service-server',
see the documentation at https://www.npmjs.com/package/graphql-language-service-server#user-content-graphql-configuration-file

Describe the solution you'd like
Looking at how graphql-config loads the schema, it doesn't appear to have @graphql-tools/github-loader defined as a loader?
https://github.com/kamilkisiela/graphql-config/blob/6c935dbabd8959bd1c863c683c5336d92aaef4b3/src/extension.ts#L30-L42
Is it possible to add the github loader?
Describe alternatives you've considered
I briefly looked into using something like https://www.graphql-inspector.com to download the schema, and make it available locally, but I'm already using the Schema AST plugin for graphql-codegen, which I think is more suited for that task..
If I do have the schema available locally, how would configure the .graphqlrc.yaml file to download the schema from GitHub, but also point graphql-language-service-server to the local GraphQL schema?

Is it possible to add the github loader?

Yes it is possible to add that loader;
https://www.graphql-config.com/docs/library/author-extensions#registering-loaders
They should add this on their own;
https://github.com/graphql/graphiql/tree/main/packages/graphql-language-service-server
You can create an issue on their repo.

If I do have the schema available locally, how would configure the .graphqlrc.yaml file to download the schema from GitHub, but also point graphql-language-service-server to the local GraphQL schema?

You can have one codegen configuration file that generates schema file then you can have a graphql config file for language server.


ReferenceError: componentHandler is not defined

Hello.
I'm new to Firebase.
I'm trying to run Firebase Realtime Database Quickstart (https://github.com/firebase/quickstart-js/tree/master/database).
I entered "firebase serve" on my terminal and connected to "localhost:5000" on my browser.
Then I succeeded in logging in with my Google account.
However, when I try to submit a new post, an exception occurs.
I have no idea about the exception below, can anyone help me?
FIREBASE WARNING: Exception was thrown by user callback. ReferenceError: componentHandler is not defined     at createPostElement (http://localhost:5000/scripts/main.js:123:3)     at http://localhost:5000/scripts/main.js:265:11     at https://www.gstatic.com/firebasejs/3.2.1/firebase.js:416:375     at Tb (https://www.gstatic.com/firebasejs/3.2.1/firebase.js:288:165)     at uc (https://www.gstatic.com/firebasejs/3.2.1/firebase.js:268:215)     at vc (https://www.gstatic.com/firebasejs/3.2.1/firebase.js:267:837)     at Ph.g.update (https://www.gstatic.com/firebasejs/3.2.1/firebase.js:454:470)     at W.g.update (https://www.gstatic.com/firebasejs/3.2.1/firebase.js:470:437)     at writeNewPost (http://localhost:5000/scripts/main.js:57:36)     at http://localhost:5000/scripts/main.js:323:9  Uncaught ReferenceError: componentHandler is not defined FIREBASE WARNING: Exception was thrown by user callback. ReferenceError: componentHandler is not defined     at createPostElement (http://localhost:5000/scripts/main.js:123:3)     at http://localhost:5000/scripts/main.js:265:11     at https://www.gstatic.com/firebasejs/3.2.1/firebase.js:416:375     at Tb (https://www.gstatic.com/firebasejs/3.2.1/firebase.js:288:165)     at uc (https://www.gstatic.com/firebasejs/3.2.1/firebase.js:268:215)     at vc (https://www.gstatic.com/firebasejs/3.2.1/firebase.js:267:837)     at Ph.g.update (https://www.gstatic.com/firebasejs/3.2.1/firebase.js:454:470)     at W.g.update (https://www.gstatic.com/firebasejs/3.2.1/firebase.js:470:437)     at writeNewPost (http://localhost:5000/scripts/main.js:57:36)     at http://localhost:5000/scripts/main.js:323:9  Uncaught ReferenceError: componentHandler is not defined FIREBASE WARNING: Exception was thrown by user callback. ReferenceError: componentHandler is not defined     at createPostElement (http://localhost:5000/scripts/main.js:123:3)     at http://localhost:5000/scripts/main.js:265:11     at https://www.gstatic.com/firebasejs/3.2.1/firebase.js:416:375     at Tb (https://www.gstatic.com/firebasejs/3.2.1/firebase.js:288:165)     at uc (https://www.gstatic.com/firebasejs/3.2.1/firebase.js:268:215)     at vc (https://www.gstatic.com/firebasejs/3.2.1/firebase.js:267:837)     at Ph.g.update (https://www.gstatic.com/firebasejs/3.2.1/firebase.js:454:470)     at W.g.update (https://www.gstatic.com/firebasejs/3.2.1/firebase.js:470:437)     at writeNewPost (http://localhost:5000/scripts/main.js:57:36)     at http://localhost:5000/scripts/main.js:323:9  Uncaught ReferenceError: componentHandler is not defined FIREBASE WARNING: Exception was thrown by user callback. ReferenceError: componentHandler is not defined     at createPostElement (http://localhost:5000/scripts/main.js:123:3)     at http://localhost:5000/scripts/main.js:265:11     at https://www.gstatic.com/firebasejs/3.2.1/firebase.js:416:375     at Tb (https://www.gstatic.com/firebasejs/3.2.1/firebase.js:288:165)     at uc (https://www.gstatic.com/firebasejs/3.2.1/firebase.js:268:215)     at vc (https://www.gstatic.com/firebasejs/3.2.1/firebase.js:267:837)     at Ph.g.update (https://www.gstatic.com/firebasejs/3.2.1/firebase.js:454:470)     at W.g.update (https://www.gstatic.com/firebasejs/3.2.1/firebase.js:470:437)     at writeNewPost (http://localhost:5000/scripts/main.js:57:36)     at http://localhost:5000/scripts/main.js:323:9  Uncaught ReferenceError: componentHandler is not defined

@dale0713 it seems the Material Design Lite library has not been loaded at that point (not an issue with Firebase, Material Design Liste is a styling library we use in this sample). Could you try removing the ´defer´ keyword in this line in index.html:
´´´

´´´
This will make sure the libabry is loaded right away.

@nicolasgarnier Thank you for your helpful advice. After removing the defer keyword, it works fine.

@nicolasgarnier i dont hav defer keyword still it gives same error


Selection Sort and Cycle Sort in JavaScript

Hi,
I would like to implement using JavaScript the following sorting algorithms.
1.Selection Sort
2.Cycle Sort
Please assign this to me as part of GSSOC'21.

Sure thinf @sukritidawar ! All the best :+1:


Duplicate keyboard assignments

Some keyboard shortcuts interfere with other features:
When typing hex in the tracker, it's impossible to enter values containing a, 1 or 0. Those can still be achieved by entering the nearest hex value that is possible to enter and then clicking the increment button, this is painful however.

This seems to be a problem for F, 4 and 8 now with default key bindings.

I fixed this last week and then broke it again this week 😭

happens. If we're really annoyed by UI regressions, we could find out if gioui is test-/mock-friendly :) but I think "checking from time to time if everything still works" is also a good strategy

it looks test-friendly from what I can tell by inspecting their own tests: https://github.com/gioui/gio/blob/main/widget/editor_test.go

Yeah gioui being mostly stateless imgui it makes testing a real possibility. I really should do that. But the tests need to be carefully decided as I don't want minor pixel adjustments to cause tests to fail.


Update benchmark docker-compose to competition

This PR updates the docker-compose file defined for benchmarks and adapts it to the new competition format.
It launches Webots and the competitor's controller in separate containers. When the participant reset the simulation after they edited the controller, the script uses the 'reset' signal form https://github.com/cyberbotics/webots/pull/5773 to restart the controller service.
It also fixes the idle count on the server monitor.
You can test it here
Tasks

[ ] Remove test "permanentImages" in json before merge

Currently we can set the repository of an image be want to protect. Do we want to have the ability to also select which tags we want to protect or are repositories enough?


Wrong calculation of potential vulnerable files.

„Copyright © 2021 Atruvia AG<EMAIL_ADDRESS>

@ChKemper Would you comment some wrong cases? Since I extracted mitigated count, one jar file should be mapped to only one status. Fat JAR can have both vulnerable and potentially vulnerable files. In this case, I want to return most dangerous status.

Ah Ok. I think then it is fine.
In my tests I have a ZIP file containing one potentiel and one vulnerable.

Anyway, thank you for your code review!


quteqoin failed on first time upload provider settings updated

No more info by now
Try to reproduce with an empty profile

Can't reproduce


Accept Unix-like paths in keep_while conditions

Now the following keep_while conditions are equivalent:
%% Using a native path.
khepri:put(
  StoreId, Path, Value,
  #{keep_while => #{[?THIS_NODE] => Condition}}).

%% Using a Unix-like string path.
khepri:put(
  StoreId, Path, Value,
  #{keep_while => #{"." => Condition}}).

%% Using a Unix-like binary path.
khepri:put(
  StoreId, Path, Value,
  #{keep_while => #{<<".">> => Condition}}).

Pull Request Test Coverage Report for Build 594

11 of 11 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.06%) to 87.64%

Totals

Change from base Build 589:
0.06%

Covered Lines:
1950

Relevant Lines:
2225

💛  - Coveralls


Error: Istio installation failed, incomplete or does not match "istio-new.yaml" - deployment "istio-ingressgateway" exceeded its progress deadline

Bug description
Expected behavior
Istio should be installed without errorrs
Steps to reproduce the bug
istioctl manifest generate
--set values.prometheus.enabled=true
--set components.pilot.enabled=true
--set components.base.enabled=true
--set components.citadel.enabled=true
--set components.galley.enabled=true
--set components.policy.enabled=true
--set components.sidecarInjector.enabled=true
--set components.telemetry.enabled=true
--set values.mixer.adapters.stackdriver.enabled=true
--set values.gateways.enabled=true
--set values.global.mtls.enabled=true
--set values.gateways.istio-ingressgateway.enabled=true
--set values.gateways.istio-ingressgateway.sds.enabled=true
--set values.global.k8sIngress.enabled=true
--set values.global.k8sIngress.enableHttps=true \

istio-new.yaml

kubectl apply -f istio-new.yaml
istioctl verify-install -f istio-new.yaml
Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
How was Istio installed?
istioctl

kubectl get pods -n istio-system
NAME                                      READY   STATUS    RESTARTS   AGE
istio-citadel-657c747d77-9ssjr            1/1     Running   0          30m
istio-galley-5d54bc88b8-pw97s             2/2     Running   0          30m
istio-ingressgateway-598796f4d9-zm2sp     0/1     Running   0          30m
istio-policy-b7678b6b6-2nprr              2/2     Running   0          29m
istio-sidecar-injector-66bd566876-9rdx6   1/1     Running   0          29m
istio-telemetry-597bbb79b6-9f5vm          2/2     Running   0          29m
istiod-7d9c7bdd6-st8lf                    1/1     Running   0          30m
prometheus-b47d8c58c-zwt8r                2/2     Running   0          6m52s

Logs from istio-proxy container from istio-ingressgateway pod -
info Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 9 successful, 0 rejected; lds updates: 0 successful, 8 rejected
Events -
containers with unready status: [istio-proxy]
Readiness probe failed: HTTP probe failed with statuscode: 503

8 rejected

Paste the full logs from the gateway and istiod please, so we can see what was rejected

I think that I have the same problem with this issue.
$istioctl15 version --remote
client version: 1.5.0
ingressgateway version: 1.5.0
ingressgateway version: 1.4.5 <- ingressgateway 1.5.0 is not ready..
pilot version: 1.5.0
data plane version: 1.5.0 (3 proxies)

istiod

2020-03-19T08:28:43.798395Z     warn    ads     ADS:LDS: ACK ERROR   <IP_ADDRESS>:36876 router~~istio-ingres
sgateway-5ddw6479ffd-5qsz4.istio-system~istio-system.svc.cluster.local-108 Internal:Error adding/updating listener(s) <IP_ADDRESS>_443: Invalid path: /etc/certs/cert-chain.pem

ingressgateway

2020-03-19T08:00:25.627366Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cd
s updates: 1 successful, 0 rejected; lds updates: 0 successful, 1 rejected
2020-03-19T08:00:29.629236Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cd
s updates: 1 successful, 0 rejected; lds updates: 0 successful, 1 rejected
2020-03-19T08:01:13.626286Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cd
s updates: 1 successful, 0 rejected; lds updates: 0 successful, 1 rejected
(infinitely repeated this logs)

Unfortunately, I'm not familiar with Istio.
IMHO, Invalid path: /etc/certs/cert-chain.pem  seems to be the cause of my issue.
istio.default secret has cert-chain.pem and other pems.
What do I do for debugging my issue?
Thanks,

8 rejected

Paste the full logs from the gateway and istiod please, so we can see what was rejected

istiod-logs.txt
istio-ingressgateway-logs.txt

"2020-03-19T16:16:12.804303Z    warn    ads     ADS:LDS: ACK ERROR
<IP_ADDRESS>:35108
router~<IP_ADDRESS>~istio-ingressgateway-598796f4d9-db72h.istio-system~istio-system.svc.cluster.local-6
Internal:Error adding/updating listener(s) <IP_ADDRESS>_443: Invalid path:
/etc/istio/ingressgateway-certs/tls.crt
You have some Gateway referencing /etc/istio/ingressgateway-certs/tls.crt
which isn't mounted
On Thu, Mar 19, 2020 at 9:37 AM nikhilbalekundargi<EMAIL_ADDRESS>wrote:

8 rejected
Paste the full logs from the gateway and istiod please, so we can see what
was rejected
istiod-logs.txt
https://github.com/istio/istio/files/4355757/istiod-logs.txt
istio-ingressgateway-logs.txt
https://github.com/istio/istio/files/4355758/istio-ingressgateway-logs.txt
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/22309#issuecomment-601282842, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXON7CCZYJRCSNINQZDRIJC5JANCNFSM4LPA6HPA
.

etc/istio/ingressgateway-certs/tls.crt

Do i need to mount these? I believe this should be part of istio setup? isn't it?

How do you get the logs for Istiod?

Is there a work around or resolution for the issue shown above? Please clarify about exactly what needs to be mounted and how it should be done

I have the same issue.
For some reason, if I change values.global.k8sIngress.gatewayName to something different than ingressgateway e.g. k8s-ingressgateway it becomes green (and if I change it back to ingressgateway it is OK again).
For me it sometimes happens also with egress (Readiness probe returns 503)

I see, yes this is actually a bug with global.k8sIngress.enableHttps=true. This has been fixed in #22227


/noloop doesn't work

Nothing happens. It stopped working at some point.

actor.get_node("Animation") returns null in CommandInterface::callAnimationFramesMethod.
Maybe it has changed how to access the subnodes?

It does work on NixOS with godot 4.2.1. I'm completely lost. I may have some kind of issue in my Arch config messing with all this

I'm closing this issue because it works on other OSs. If it doesn't work for you on Windows, please reopen it. There are issues with no-loop but they are tackled elsewhere


Adding module/port type for CMIS compliant devices

Thanks, good enhancement/fix.  That should have been in the original CMIS checkin.  Accepted, committed, fixed.
Don
From: ashutosh-arrcus<EMAIL_ADDRESS>Sent: Thursday, June 04, 2020 4:33 PM
To: opencomputeproject/oom<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [opencomputeproject/oom] Adding module/port type for CMIS compliant devices (#18)

You can view, comment on, or merge this pull request online at:
https://github.com/opencomputeproject/oom/pull/18
Commit Summary

Adding module/port type for CMIS compliant devices

File Changes

M oom/oomlib.py https://github.com/opencomputeproject/oom/pull/18/files#diff-e7072c657bbd80c773f99717b60219b2  (3)

Patch Links:

https://github.com/opencomputeproject/oom/pull/18.patch
https://github.com/opencomputeproject/oom/pull/18.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/opencomputeproject/oom/pull/18 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AD6VCJYIQZEANEXZQ2HJ6UDRVAVMDANCNFSM4NTCCETQ .  https://github.com/notifications/beacon/AD6VCJ3SRZBJ7KUUHBVXYFLRVAVMDA5CNFSM4NTCCET2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4JM7QFSQ.gif


refactor build command into two files

In a few places we were instantiating the build command purely to get access to its build functionality. This refactors the code into a library which can build flx files and a BuildCommand which calls that library.

most of commands/build.dart moved into flx.dart
commands/build.dart is now just a subclass of FlutterCommand and calls build() methods from the flx library
calls to BuildCommand moved to calls in flx build()
the BuildCommand prints out a success message when it completes

LGTM

We should probably removes calls to Command.inheritFromParent - these seem to be places where we're creating command objects just to call some methods on the objects - not to use them in the args context they might be expecting.

Yeah, that's probably a sign that there's some reusable code that we should factor out of the command.


Add Instrall and update manager

Is your feature request related to a problem? Please describe.
nothing
Describe the solution you'd like
Install and Update manage
Describe alternatives you've considered
Add another data to data.json and merge binary(add, desc~)

Commands

[ ] collection (patch readme and data.json)
[ ] install        (Easy Install)
[ ] update      (Update)

New format of data.json
{
 "Amass": {
  "Data": "| Discovery/DOMAIN | [Amass](https://github.com/OWASP/Amass) | In-depth Attack Surface Mapping and Asset Discovery | ![](https://img.shields.io/github/stars/OWASP/Amass) | ![](https://img.shields.io/github/languages/top/OWASP/Amass) |",
  "Method": "DOMAIN",
  "Type": "Discovery",
  "Install":"brew install amass",
  "update":"brew upgrade amass"
 }
}

Example
Add new  tool
$ whw collection -add https://github.com/hahwul/dalfox

Distribute Readme
$ whw collection -distribute

Install all tools
$ whw install all

Install selection tool
$ whw install dalfox

Update all tools
$ whw update all

Update selection tool
$ whw update dalfox


current running total for a configurable period.

I would like to request a new feature for this node .
The idea is that it should output the current running total for a configurable period.

So each time a message for a certain topic arrives, it should calculate the running total of all the messages received for that topic in the period [ now - configurable period, now] and then immediately output this running total.

A further improvement: when no messages are received within a configurable period for a topic for which we have received a message earlier that it outputs 0 as running total for that topic.  (There is no need to send a 0 again when next time that configurable period has ended).

I would like to use this feature for my water meter; every 5 seconds I receive the number of pulses counted (in many cases only 0, 1 or 2 pulses are counted during this interval) - so it would be interesting to get a running total over an interval of 1 minute (or more) which would tell me the amount of water used in the last minute which I would then display in the node-red dashboard gauge.

another extension - is that besides "running total" we also support a "running average".  I think that this is a simple extension.

I just discovered node-red-node-smooth.
So this node might be a better candidate for this feature request.

I'm closing this, please reopen if the feature is still requested


Missing more detailed information about .clear table data command

Hi, based on documentation here, Azure Data Explorer offers different ways of deleting data. It is described that we can:

Delete data using the retention policy
Delete data by dropping extents
Delete individual rows with .purge or .soft-delete

Information about .clear table data is not present, so I wonder how it differs from the above options. Documentation about that command says only:

Clears the data of an existing table, including streaming ingestion data.

Can you clarify how it works, how it differs from other options, what are the use cases, is the deletion immediately, and what might be the performance impact over the table that is queried frequently and when the data in that table is cleared and re-ingested also frequently?

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

ID: e6dc9cc9-7277-b802-798b-4267d800548f
Version Independent ID: 82cd5f5b-5513-a955-5428-c949ffbda211
Content: Delete data from Azure Data Explorer
Content Source: data-explorer/delete-data.md
Service: data-explorer
GitHub Login: @orspod
Microsoft Alias: orspodek

@dariuszdbr Thanks for the feedback! We are currently investigating and will update you shortly.

We have assigned the issue to the content author . They will evaluate & update the document as appropriate

@BryanTrach-MSFT Thanks so much for taking the time to leave us your comment on our documentation. We're working on an update  for the page based on your suggestions which will be published as soon as possible.
We're closing this as an open issue for now, but feel free to continue to comment here as necessary. We appreciate your contribution to our community.
#please-close

@BryanTrach-MSFT Thanks again for your feedback. We've updated the topic based on your feedback.


Add release notes for 0.12.0 release

Signed-off-by: Janki Chhatbar<EMAIL_ADDRESS>

Pushed an update to address my feedback as @Jaanki requested on Slack.

@skitt @sridhargaddam and @vthapar have pending re-reviews I think


Automatically detect and track flaky tests

tl;dr This pull request proposes configuring tooling to automatically detect and track flaky tests. As I understand it, this has historically required manual effort for Homebrew maintainers. By automating the process, we hopefully reduce the time that maintainers have to spend on the thankless and laborious task of manually identifying flaky tests. 🤞
/cc @MikeMcQuaid for review
Pull request template

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
No. I don't think this is applicable to this pull request, but if it is, please let me know. :bow:
[x] Have you successfully run brew style with your changes locally?
[x] Have you successfully run brew typecheck with your changes locally?
[x] Have you successfully run brew tests with your changes locally?

How it works
At a high-level, setting things up works as follows:

Enhance the test suite to emit JUnit XML test reports.
This is accomplished in e163eb8650cb38d03829cd8aa537a3f32af3682f. Please see the commit message for details.

Enhance the CI workflow to send those test reports to buildpulse.io for analysis.
This is accomplished in 006299dcc148bf1cdebddac55c7b1d581009b528.

Maintainers can access an always-up-to-date list of flaky tests, along with stats on the disruptiveness of each test, how recently it has occurred, etc. Maintainers can also choose to receive daily digests in Slack and weekly digests via email, so that they don't have to remember to check yet another tool. 😅

A few things to have in mind

🐣 To date, BuildPulse has been used primarily by teams working in private repositories. Homebrew/brew would be the first significant open source project using BuildPulse, so we'll probably discover some speedbumps due to the differences in workflows between open source projects versus private projects. I hope you'll bring those speedbumps to my attention (jason@buildpulse.io), because I'd love to find a good way to address them.

🍴 For GitHub Actions, workflows currently need to use GitHub Actions Secrets in order to authenticate when sending test results to BuildPulse. Since forks can't access secrets, this means that forks can't yet send test results to BuildPulse for analysis. Other tools (like CodeCov) have a solution for this kind of thing, and I hope to add support for forks in BuildPulse in the future as well.

🍎 This pull request enables flaky test detection exclusively for the macOS CI job.
CI also runs tests in three other contexts: "tests (no-compatibility mode)", "tests (generic OS)", "tests (Linux)". Before enabling BuildPulse for the other contexts, BuildPulse will need to evolve to accept additional metadata to let you distinguish which context reported a given test result.
Right now, the XML reports produced by rspec_junit_reporter don't distinguish one context's results from another context's results. For reliably detecting flaky tests, if we're sending BuildPulse results for multiple contexts, it will be important to distinguish which context the test is running in.
For example, let's assume that a given test (x) runs in both the "tests (Linux)" context and the "test everything (macOS)" context. And let's say we're running the build multiple times at commit 0abcdef. If test x always passes in the macOS job, and always fails in the Linux job, the test isn't flaky; it's just broken on Linux. :grimacing:
But if we don't know the context associated with each test result, all we'd see is that test x sometimes passes and sometimes fails at commit 0abcdef, and we'd wrongly conclude that the test is flaky. :see_no_evil:
So, for now, we need to pick one context to use for sending test results to BuildPulse. @MikeMcQuaid recommended using the macOS job, since it runs the largest number of tests (e.g. the brew cask ones).

Verifying these changes
Since this pull request makes changes to the macOS CI job, and since that job doesn't run in forks, we can't immediately see the effect of these changes. To work around that limitation (so that reviewers can see the effect of these changes), 1888739cf69963323dfcc179440c6b0f10ff1c3b temporarily updates the macOS job to run in my fork. We can see that the job succeeds (https://github.com/jasonrudolph/brew/runs/2877954175) and that test results were successfully sent to BuildPulse. [screenshot]

These changes all seem good/reasonable to me and I'd love to see us use BuildPulse for this. I think we want a way to guard this to only PRs from Not Forks and master branch builds.

Agreed. I don't think we have the bandwidth to make use of fork data anyway, even if there were was information there that we can't get from CI runs here.

@Homebrew/brew any thoughts or objections on using BuildPulse for this?

❤

@Homebrew/core I think this might be a good tool for us to eventually keep track of flaky brew audit and brew test runs for formulae, too.

❤ for this too. We'll probably have to teach test-bot to produce test output in a format BuildPulse can consume.

Thanks so much for your first contribution!  You rock, @jasonrudolph!

@Homebrew/core I think this might be a good tool for us to eventually keep track of flaky brew audit and brew test runs for formulae, too.

❤ for this too. We'll probably have to teach test-bot to produce test output in a format BuildPulse can consume.

That would be great! I guess we'll need to bring back junit output for homebrew-test-bot (was removed https://github.com/Homebrew/homebrew-test-bot/pull/355)

I guess we'll need to bring back junit output for homebrew-test-bot (was removed Homebrew/homebrew-test-bot#355)

@bayandin Yes! It's relatively self-contained so shouldn't be too tricky. Is this something you might be able to pick up?

I guess we'll need to bring back junit output for homebrew-test-bot (was removed Homebrew/homebrew-test-bot#355)

@bayandin Yes! It's relatively self-contained so shouldn't be too tricky. Is this something you might be able to pick up?

Will do!

@bayandin 😍 I'd consider limiting the output just to e.g. audit and test for now (or anything else that's flaky, maybe install?).

@bayandin 😍 I'd consider limiting the output just to e.g. audit and test for now (or anything else that's flaky, maybe install?).

Yep, I think I'll start with audit and test and then it should be pretty easy to adjust (at least I hope it will be so)


Scalable Variational Gaussian Process Classification

This paper discusses how to implement a scalable GP model for classification http://arxiv.org/pdf/1411.2005.pdf. This script https://github.com/SheffieldML/GPy/blob/master/GPy/core/svgp.py references this paper.
I fit as model as follows:
m = GPy.core.svgp.SVGP(X = X_train_svd, Y = y_train, Z = X_induce, kernel = k, likelihood = GPy.likelihoods.Bernoulli())
When I want to optimize I can use the following:
optimizeWithFreezingZ
However this has the problem that the inducing points will be fixed. From my understanding of the paper, they are able to optimize over the inducing points, so this seems a sub-optimal optimization approach.
The paper mentions that stochastic gradient descent can facilitate dealing with millions of data points. I try to optimize via SGD as follows:
m.optimize_SGD(),
but get the error NameError: global name 'SGD' is not defined. The function optimize_SGD() can be found in lines 268 - 272 of the script https://github.com/SheffieldML/GPy/blob/master/GPy/core/model.py.
Can someone please explain why this error is occurring and how to optimize via SGD?

This is why we need to put the new release out! These things are fixed in the devel branch as far as I know and there exists an optimizer which is called adadelta. The method you mentioned does not exist anymore....

On 22 Mar 2016, at 20:17, IrishBeast01<EMAIL_ADDRESS>wrote:
This paper discusses how to implement a scalable GP model for classification http://arxiv.org/pdf/1411.2005.pdf. This script https://github.com/SheffieldML/GPy/blob/master/GPy/core/svgp.py references this paper.
I fit as model as follows:
m = GPy.core.svgp.SVGP(X = X_train_svd, Y = y_train, Z = X_induce, kernel = k, likelihood = GPy.likelihoods.Bernoulli())
When I want to optimize I can use the following:
optimizeWithFreezingZ
However this has the problem that the inducing points will be fixed. From my understanding of the paper, they are able to optimize over the inducing points, so this seems a sub-optimal optimization approach.
The paper mentions that stochastic gradient descent can facilitate dealing with millions of data points. I try to optimize via SGD as follows:
m.optimize_SGD(),
but get the error NameError: global name 'SGD' is not defined. The function optimize_SGD() can be found in lines 268 - 272 of the script https://github.com/SheffieldML/GPy/blob/master/GPy/core/model.py.
*Can someone please explain why this error is occurring and how to optimize via SGD?
*
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub

Thanks for your reply.
Yes, so I started using adadelta, which to my understanding is a variant of SGD. However when I optimize using it, computationally it takes longer than the default optimization method. I'm assuming this isn't supposed to happen or will it only be faster if I parallelize the optimization procedure?

So its seems that m.optimize_restarts(parallel = True) facilitates such a parallel optimization approach. When I run this command I get the error:
m.optimize_restarts(parallel = True) Traceback (most recent call last):   File "<stdin>", line 1, in <module>   File "/usr/local/lib/python2.7/site-packages/GPy-0.8.8-py2.7-linux-x86_64.egg/GPy/core/model.py", line 104, in optimize_restarts     raise e cPickle.PicklingError: Can't pickle <type 'GPy.util.choleskies_cython._memoryviewslice'>: attribute lookup GPy.util.choleskies_cython._memoryviewslice failed
Is my understanding correct that this parallellizes the optimisation and why do I get an error if so?

Optimize restarts is currently not supported due to how multiprocessing handles functions...

On 24 Mar 2016, at 12:45, IrishBeast01<EMAIL_ADDRESS>wrote:
So its seems that m.optimize_restarts(parallel = True) facilitates such a parallel optimization approach. When I run this command I get the error:
m.optimize_restarts(parallel = True)
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python2.7/site-packages/GPy-0.8.8-py2.7-linux-x86_64.egg/GPy/core/model.py", line 104, in optimize_restarts
raise e
cPickle.PicklingError: Can't pickle <type 'GPy.util.choleskies_cython._memoryviewslice'>: attribute lookup GPy.util.choleskies_cython._memoryviewslice failed
Is my understanding correct that this parallellizes the optimisation and why do I get an error if so?
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub


TAJO-1285 Refactoring Magic Number to HAConstants

HAConstants defines types.
But in HAServiceUtil, just using Magic Numbers 1,2,3,4,5
so this patch just changed them as HAConstants.

Hi @charsyam
+1
Thanks for your contribution.


[Feature request] Allow download (GET) of unrendered file

Allow another Obsidian user to download the file directly into their vault.
Could use a plugin command "Download shared note" that would accept the encrypted URL, and make the GET request with an Accept: text/markdown,text/plain or to indicate that the file should be returned as-is, without the rendered web view.
It isn't clear to me if you could use this to share other kinds of files as well.

That's a super cool idea. I wonder if we could even take this a step further and add a "Download to vault" button to the web viewer that opens Obsidian and stores the note in your vault directly. What do you think?

I was thinking about this because of what I would like to share:

a document that uses leaflet, which means an associated image attachment.
a way to include a button inside obsidian that fetches the magic URL (without the trip through the web viewer).


[Bug]: Asking to pad but the tokenizer does not have a padding token. Please select a token to use as `pad_token

软件环境
- paddlepaddle:develop
- paddlepaddle-gpu: develop 11.8
- paddlenlp:  lastest  4609d07a54ab97974b962b536dde7164ab15db93

重复问题

[X] I have searched the existing issues

错误描述
meta-llama/Meta-Llama-3-8B-Instruct infer error

(…)nstruct/model-00004-of-00004.safetensors:  94%|▉| 1.10G/1.17G [00:13<00:00, 8
(…)nstruct/model-00004-of-00004.safetensors:  95%|▉| 1.11G/1.17G [00:13<00:00, 7
(…)nstruct/model-00004-of-00004.safetensors:  96%|▉| 1.12G/1.17G [00:13<00:00, 8
(…)nstruct/model-00004-of-00004.safetensors:  97%|▉| 1.13G/1.17G [00:13<00:00, 7
(…)nstruct/model-00004-of-00004.safetensors:  98%|▉| 1.14G/1.17G [00:14<00:00, 6
(…)nstruct/model-00004-of-00004.safetensors: 100%|█| 1.17G/1.17G [00:14<00:00, 8
Downloading shards: 100%|█████████████████████████| 4/4 [03:24<00:00, 51.14s/it]
W0613 23:29:27.245162 141364 gpu_resources.cc:119] Please NOTE: device: 0, GPU Compute Capability: 7.0, Driver API Version: 12.0, Runtime API Version: 11.8
W0613 23:29:27.246907 141364 gpu_resources.cc:164] device: 0, cuDNN Version: 8.9.
Loading checkpoint shards: 100%|██████████████████| 4/4 [03:39<00:00, 54.87s/it]
[2024-06-13 23:33:27,358] [    INFO] - All model checkpoint weights were used when initializing LlamaForCausalLM.

[2024-06-13 23:33:27,359] [    INFO] - All the weights of LlamaForCausalLM were initialized from the model checkpoint at meta-llama/Meta-Llama-3-8B-Instruct.
If your task is similar to the task the model of the checkpoint was trained on, you can already use LlamaForCausalLM for predictions without further training.
(…)ama-3-8B-Instruct/generation_config.json: 100%|█| 126/126 [00:00<00:00, 489kB
[2024-06-13 23:33:27,486] [    INFO] - Loading configuration file /home/aistudio/.paddlenlp/models/meta-llama/Meta-Llama-3-8B-Instruct/generation_config.json
[2024-06-13 23:33:27,487] [    INFO] - We are using <class 'paddlenlp.transformers.llama.configuration.LlamaConfig'> to load 'meta-llama/Meta-Llama-3-8B-Instruct'.
[2024-06-13 23:33:27,487] [    INFO] - Loading configuration file /home/aistudio/.paddlenlp/models/meta-llama/Meta-Llama-3-8B-Instruct/config.json
[2024-06-13 23:33:27,488] [    INFO] - Loading configuration file /home/aistudio/.paddlenlp/models/meta-llama/Meta-Llama-3-8B-Instruct/generation_config.json
[2024-06-13 23:33:27,490] [    INFO] - Start predict
[2024-06-13 23:33:27,491] [   ERROR] - Using pad_token, but it is not set yet.
Traceback (most recent call last):
  File "/home/aistudio/work/PaddleNLP/llm/predictor.py", line 1651, in <module>
    predict()
  File "/home/aistudio/work/PaddleNLP/llm/predictor.py", line 1596, in predict
    outputs = predictor.predict(batch_source_text)
  File "/home/aistudio/work/PaddleNLP/llm/predictor.py", line 251, in predict
    tokenized_source = self._preprocess(input_texts)
  File "/home/aistudio/work/PaddleNLP/llm/predictor.py", line 226, in _preprocess
    tokenized_source = self.tokenizer(
  File "/opt/conda/envs/python35-paddle120-env/lib/python3.10/site-packages/paddlenlp/transformers/tokenizer_utils_base.py", line 2248, in __call__
    return self.batch_encode(
  File "/opt/conda/envs/python35-paddle120-env/lib/python3.10/site-packages/paddlenlp/transformers/tokenizer_utils_base.py", line 2523, in batch_encode
    padding_strategy, truncation_strategy, max_length, kwargs = self._get_padding_truncation_strategies(
  File "/opt/conda/envs/python35-paddle120-env/lib/python3.10/site-packages/paddlenlp/transformers/tokenizer_utils_base.py", line 2004, in _get_padding_truncation_strategies
    raise ValueError(
ValueError: Asking to pad but the tokenizer does not have a padding token. Please select a token to use as `pad_token` `(tokenizer.pad_token = tokenizer.eos_token e.g.)` or add a new pad token via `tokenizer.add_special_tokens({'pad_token': '[PAD]'})`.

### 稳定复现步骤 & 代码

!pip install tiktoken
!python predictor.py --model_name_or_path meta-llama/Meta-Llama-3-8B-Instruct --dtype=float16

Using unk_token, but it is not set yet.   same question in qwen2 inference:
[33m[2024-06-13 23:21:55,506] [ WARNING] - if you run ring_flash_attention.py, please ensure you install the paddlenlp_ops by following the instructions provided at https://github.com/PaddlePaddle/PaddleNLP/blob/develop/csrc/README.md
[2024-06-13 23:21:56,948] [    INFO] - We are using <class 'paddlenlp.transformers.qwen2.tokenizer.Qwen2Tokenizer'> to load 'Qwen/Qwen2-7B-Instruct'.
[2024-06-13 23:21:57,310] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:21:57,310] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:21:57,310] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:21:57,310] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:21:57,310] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:21:57,310] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:21:57,310] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:21:57,310] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:21:57,311] [    INFO] - We are using <class 'paddlenlp.transformers.qwen2.configuration.Qwen2Config'> to load 'Qwen/Qwen2-7B-Instruct'.
[2024-06-13 23:21:57,311] [    INFO] - Loading configuration file /home/aistudio/.paddlenlp/models/Qwen/Qwen2-7B-Instruct/config.json
[2024-06-13 23:21:57,312] [    INFO] - We are using <class 'paddlenlp.transformers.qwen2.modeling.Qwen2ForCausalLM'> to load 'Qwen/Qwen2-7B-Instruct'.
[2024-06-13 23:21:57,312] [    INFO] - Loading configuration file /home/aistudio/.paddlenlp/models/Qwen/Qwen2-7B-Instruct/config.json
[2024-06-13 23:21:57,313] [    INFO] - Loading weights file from cache at /home/aistudio/.paddlenlp/models/Qwen/Qwen2-7B-Instruct/model.safetensors.index.json
Downloading shards: 100%|██████████████████████| 4/4 [00:00<00:00, 26255.42it/s]
W0613 23:21:57.318940 134458 gpu_resources.cc:119] Please NOTE: device: 0, GPU Compute Capability: 7.0, Driver API Version: 12.0, Runtime API Version: 11.8
W0613 23:21:57.320240 134458 gpu_resources.cc:164] device: 0, cuDNN Version: 8.9.
Loading checkpoint shards: 100%|██████████████████| 4/4 [03:18<00:00, 49.74s/it]
[2024-06-13 23:25:34,697] [    INFO] - All model checkpoint weights were used when initializing Qwen2ForCausalLM.

[2024-06-13 23:25:34,697] [    INFO] - All the weights of Qwen2ForCausalLM were initialized from the model checkpoint at Qwen/Qwen2-7B-Instruct.
If your task is similar to the task the model of the checkpoint was trained on, you can already use Qwen2ForCausalLM for predictions without further training.
[2024-06-13 23:25:34,700] [    INFO] - Loading configuration file /home/aistudio/.paddlenlp/models/Qwen/Qwen2-7B-Instruct/generation_config.json
[2024-06-13 23:25:34,700] [    INFO] - Generation config file not found, using a generation config created from the model config.
[2024-06-13 23:25:34,701] [    INFO] - We are using <class 'paddlenlp.transformers.qwen2.configuration.Qwen2Config'> to load 'Qwen/Qwen2-7B-Instruct'.
[2024-06-13 23:25:34,701] [    INFO] - Loading configuration file /home/aistudio/.paddlenlp/models/Qwen/Qwen2-7B-Instruct/config.json
[2024-06-13 23:25:34,701] [    INFO] - Loading configuration file /home/aistudio/.paddlenlp/models/Qwen/Qwen2-7B-Instruct/generation_config.json
[2024-06-13 23:25:34,702] [ WARNING] - Can't find generation config, so it will not use generation_config field in the model config
[2024-06-13 23:25:34,703] [    INFO] - Start predict
[2024-06-13 23:25:48,343] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,343] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,343] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,343] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,343] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,343] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,343] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,344] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,344] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,344] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,344] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,344] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,344] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,344] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,344] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,344] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,344] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,344] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,344] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,344] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,345] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,345] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,345] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,345] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,345] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,345] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,345] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,345] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,345] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,345] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,345] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,345] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,345] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,345] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,346] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,346] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,346] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,346] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,346] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,346] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,346] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,346] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,346] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,346] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,346] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,346] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,346] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,347] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,347] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,347] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,347] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,347] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,347] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,347] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,347] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,347] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,347] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,347] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,347] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,347] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,347] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,347] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,348] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,348] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,348] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,348] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,348] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,348] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,348] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,348] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,348] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,348] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,348] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,348] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,348] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,348] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,349] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,349] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,349] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,349] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,349] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,349] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,349] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,349] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,349] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,349] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,349] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,349] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,349] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,349] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,350] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,350] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,350] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,350] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,350] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,350] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,350] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,350] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,350] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,350] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,350] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,350] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,350] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,350] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,350] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,351] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,351] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,351] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,351] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,351] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,351] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,351] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,351] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,351] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,351] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,351] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,351] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,351] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,351] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,351] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,352] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,352] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,352] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,352] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,352] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,352] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,352] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,352] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,352] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,352] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,352] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,352] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,352] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,352] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,353] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,353] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,353] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,353] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,353] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,353] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,353] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,353] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,353] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,353] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,353] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,353] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,353] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,353] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,353] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,354] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,354] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,354] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,354] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,354] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,354] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,354] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,354] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,354] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,354] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,354] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,354] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,354] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,354] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,354] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,355] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,355] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,355] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,355] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,355] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,355] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,355] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,355] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,355] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,355] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,355] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,355] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,355] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,355] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,356] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,356] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,356] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,356] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,356] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,356] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,356] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,356] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,356] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,356] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,356] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,356] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,356] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,357] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,357] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,357] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,357] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,357] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,357] [   ERROR] - Using unk_token, but it is not set yet.
[2024-06-13 23:25:48,357] [   ERROR] - Using unk_token, but it is not set yet.
Traceback (most recent call last):
  File "/home/aistudio/work/PaddleNLP/llm/predictor.py", line 1651, in <module>
    predict()
  File "/home/aistudio/work/PaddleNLP/llm/predictor.py", line 1596, in predict
    outputs = predictor.predict(batch_source_text)
  File "/home/aistudio/work/PaddleNLP/llm/predictor.py", line 253, in predict
    decoded_predictions = self._postprocess(predictions)
  File "/home/aistudio/work/PaddleNLP/llm/predictor.py", line 245, in _postprocess
    decoded_predictions = self.tokenizer.batch_decode(
  File "/opt/conda/envs/python35-paddle120-env/lib/python3.10/site-packages/paddlenlp/transformers/tokenizer_utils_base.py", line 3200, in batch_decode
    return [
  File "/opt/conda/envs/python35-paddle120-env/lib/python3.10/site-packages/paddlenlp/transformers/tokenizer_utils_base.py", line 3201, in <listcomp>
    self.decode(
  File "/opt/conda/envs/python35-paddle120-env/lib/python3.10/site-packages/paddlenlp/transformers/tokenizer_utils_base.py", line 3239, in decode
    return self._decode(
  File "/opt/conda/envs/python35-paddle120-env/lib/python3.10/site-packages/paddlenlp/transformers/qwen2/tokenizer.py", line 294, in _decode
    return super()._decode(
  File "/opt/conda/envs/python35-paddle120-env/lib/python3.10/site-packages/paddlenlp/transformers/tokenizer_utils.py", line 1842, in _decode
    sub_texts.append(self.convert_tokens_to_string(current_sub_text))
  File "/opt/conda/envs/python35-paddle120-env/lib/python3.10/site-packages/paddlenlp/transformers/qwen2/tokenizer.py", line 280, in convert_tokens_to_string
    text = "".join(tokens)
TypeError: sequence item 196: expected str instance, NoneType found

Qwen修复PR：

Qwen修复PR：#8601 LLaMA修复PR：#8630

https://github.com/PaddlePaddle/PaddleNLP/pull/8630并没有修复LLaMA的问题哈，我不知道咋修。

Qwen修复PR：#8601 LLaMA修复PR：#8630

#8630 并没有修复LLaMA的问题哈，我不知道咋修。

LLama3的tokenizer中缺少pad_token，修复代码如下，我看已经加上了
if (isinstance(tokenizer, LlamaTokenizer) or isinstance(tokenizer, Llama3Tokenizer)) and not tokenizer.pad_token:
        tokenizer.pad_token = tokenizer.unk_token

Qwen修复PR：#8601 LLaMA修复PR：#8630

#8630 并没有修复LLaMA的问题哈，我不知道咋修。

LLama3的tokenizer中缺少pad_token，修复代码如下，我看已经加上了
if (isinstance(tokenizer, LlamaTokenizer) or isinstance(tokenizer, Llama3Tokenizer)) and not tokenizer.pad_token:
        tokenizer.pad_token = tokenizer.unk_token

没用的，llama3连unk_token都set不了，这里的代码改动可以先忽略。我们根本上需要同时解决pad_token和unk_token的set问题才行，我猜测，其他token可能也同样无法set。


Required Attribute

Add support for System.ComponentModel.DataAnnotations.RequiredAttribute besides Newtonsoft.Json.JsonRequiredAttribute

@MrWolfPST Thanks for the issue! Would you please elaborate?

I maked some additional tests and I must partial review the issue.
The only way I found for include a mandatory property in the required section of component is decorate property with [JsonProperty(Required = Required.Always)].
Instead if I use JsonRequired or Required attributes, property is not included in the required section.
Anyway the RequiredAttribute is not in the supportet attributes list

Here are the decorators we currently support:

From Newtonsoft.Json
From System.ComponentModel.DataAnnotations

It partially answers your question, though.

Yes I had read. My original request was for add support of RequiredAttribute of System.ComponentModel.DataAnnotations namespace. But seam that also JsonRequiredAttribute have some problem

Let me check.

JsonRequered not working in combination with JsonProperty with property name specified, as described in issue #227

I'm using the latest versions of this and .NET 6 and Azure Functions v4 and The Required Attribute does not seem to work at all.


AnT1nG-Meta-llama

Hello World♡♡♡

Hi! Welcome to our llama-recipe github, if you have any question, please let me know.


openai clarify RPM is really segmented into rps

This document currently states

Requests per minute per model
Davinci-models (002 and later): 120ChatGPT model: 300GPT-4 models: 18All other models: 300

Upon testing and this Q/A https://learn.microsoft.com/en-us/answers/questions/1282041/rate-limits-in-azure-openai-service-how-does-it-wo
It sounds like the limits are actually calculated for the 1 minute boundary, the 10 second boundary and the 1 second boundary. It would be beneficial to clarify that so users don't waste time trying to figure out why they are getting seemingly randomly throttled.
This could just be a ** on the rate limits with this added detail.

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

ID: a8ff3d7a-b044-63c0-4c66-1bed9e894287
Version Independent ID: 649fbdae-45d1-dd59-2482-4d6640b6eb67
Content: Azure OpenAI Service quotas and limits - Azure Cognitive Services
Content Source: articles/cognitive-services/openai/quotas-limits.md
Service: cognitive-services
Sub-service: openai
GitHub Login: @mrbullwinkle
Microsoft Alias: mbullwin

@slynickel
Thanks for your feedback! We will investigate and update as appropriate.

@slynickel apologies for the delay in response. We had new content on this subject we were waiting to release, but couldn't talk about yet because it was tied to the new quota feature that came out last week.
We go more in depth into the nuances of how the rate limits work to address your request here:
https://learn.microsoft.com/en-us/azure/cognitive-services/openai/how-to/quota#understanding-rate-limits

Thanks for the update. Looks good.


I am building a MacOS Desktop app, and I need to achieve the following: when the password input field gains focus, the input method should automatically switch from the Chinese input method to English mode.

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
I am building a MacOS Desktop app, and I need to achieve the following: when the password input field gains focus, the input method should automatically switch from the Chinese input method to English mode.
code:
child: TextField(
    keyboardType: TextInputType.visiblePassword

}
Expected results
I am building a MacOS Desktop app, and I need to achieve the following: when the password input field gains focus, the input method should automatically switch from the Chinese input method to English mode.
code:
child: TextField(
    keyboardType: TextInputType.visiblePassword

}
Actual results
I am building a MacOS Desktop app, and I need to achieve the following: when the password input field gains focus, the input method should automatically switch from the Chinese input method to English mode.
code:
child: TextField(
    keyboardType: TextInputType.visiblePassword

}
Code sample
I am building a MacOS Desktop app, and I need to achieve the following: when the password input field gains focus, the input method should automatically switch from the Chinese input method to English mode.
code:
child: TextField(
    keyboardType: TextInputType.visiblePassword

}
Screenshots or Video
I am building a MacOS Desktop app, and I need to achieve the following: when the password input field gains focus, the input method should automatically switch from the Chinese input method to English mode.
code:
child: TextField(
    keyboardType: TextInputType.visiblePassword

}
Logs
I am building a MacOS Desktop app, and I need to achieve the following: when the password input field gains focus, the input method should automatically switch from the Chinese input method to English mode.
code:
child: TextField(
    keyboardType: TextInputType.visiblePassword

}
Flutter Doctor output
I am building a MacOS Desktop app, and I need to achieve the following: when the password input field gains focus, the input method should automatically switch from the Chinese input method to English mode.
code:
child: TextField(
    keyboardType: TextInputType.visiblePassword

}

Hi @wanyangye
When opening an issue, please fill in the appropriate information in the respective fields in the issue template.
With regard to the issue, It looks like you are asking for assistance on personal code instead of a bug reporting or a proposal/feature request. Please see flutter's community for resources and ask questions like this. You may also get some help if you post it on Stack Overflow as well.
Closing the issue.