Update language/zh base branch from release-1.14 to release-1.15

Similar to what we did with release-1.12 to release-1.14. I would like that we can do something similar after release-1.15 rollout.
Relates to #13745
/cc @kubernetes/sig-docs-zh-owners @kubernetes/sig-docs-zh-reviews
/cc @zacharysarah

/language zh
/priority important-longterm

/s/release-1.15/release-1.16
/s/release-1.14/release-1.15

looks like it's time to stop using release-x.y branches as the base branch.
tengqm 11:59 AM
during 1.17 release window, the Chinese localization has been a headache for the release team.
we had a lot of commits directly merged into release-1.16 and only release-1.16 branch
when the release team rebase things back to release-1.16 branch, they saw a lot of conflicts
going forward, maybe we should commit things to master directly since we are kinda catching up with the master branch

idealhack 1:40 PM
agreed, PR to master or a -dev branch

https://kubernetes.slack.com/archives/CE3LNFYJ1/p1575946765043800

Since we're changing the process a little, @chenrui333 or @tengqm can you please add /cc @kubernetes/sig-docs-en-owners on the next switch to master or dev-x.xx? It will help keep everyone in sync!
Thanks @idealhack and @tengqm!

/remove-lifecycle stale

Sure, @jimangel, will keep an eye on it.

cc @kubernetes/sig-docs-zh-owners @kubernetes/sig-docs-zh-reviews ^^^^

this issue is old . can we close this?
/cc @chenrui333

pretty old issue. irrelevant now.
/close

Thanks @tengqm!


Text: letterSpacing and TextAlign.Center break text centering

MaterialTheme {
    Column {
        /*A*/ Text("BLAH", Modifier.border(2.dp, Color.Red), letterSpacing = 10.sp)
        /*B*/ Text("BLAH", Modifier.border(2.dp, Color.Red), letterSpacing = 10.sp, textAlign = TextAlign.Center)
    }
}

Actual:

Expected:
I expect letterSpacing not to add any padding (so that all letters touch the border).
However, if it is meant to do so, then:

B should be centered as A
Not sure about A, probably it's OK, but since it is not explicitly centered, maybe should be as B

Not sure if it's specific to CfD, I'd file it at Google's tracker, but I'm not sure which Jetpack's versions correspond to CfD.

Hi.
letterSpacing get padding in end of text

How to fix it ?

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


typecript added

Fixes

Fixes
Issue Title: FD-011
Github #[issue number]
Created by @[issue author]
Description

Testing Instructions

Checklist

[ ] My pull request has a descriptive title (not a vague title like Update index.md).
[ ] My pull request targets the default branch of the repository (development)
[ ] My commit messages follow best practices.
[ ] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[ ] I tried running the project locally and verified that there are no visible errors.

Release Notes

Decisions

Technical Details

Links

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@marlovigor Please merge your PR into dev. PRs have to be merged into dev first and then merged to the main branch.

there are many merge conflicts with both the base branch main and dev. These will need to be resolved before the PR can get merged.

@lanicemp @SincerelyBrittany can you both take a look at this


Error using HwndWrapper

Hey when I'm using HwndWrapper for a specific window I get this error:
>>> HwndWrapper(app.windows()[0])
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Python27\lib\site-packages\pywinauto\controls\hwndwrapper.py", line 180, in __new__
    return super(HwndWrapper, cls)._create_wrapper(cls, element, HwndWrapper)
  File "C:\Python27\lib\site-packages\pywinauto\base_wrapper.py", line 121, in _create_wrapper
    new_class = cls_spec.find_wrapper(element_info)
  File "C:\Python27\lib\site-packages\pywinauto\controls\hwndwrapper.py", line 137, in find_wrapper
    if regex.match(class_name):
TypeError: expected string or buffer

It seems that the line 129 in "pywinauto\controls\hwndwrapper.py" should be this:
class_name = element.class_name()
Instead of:
class_name = element.class_name

The usage is incorrect because app.windows()[0] already returns HwndWrapper object or its derivative. To make it more clear we may check if we create a copy of HwndWrapper (and hence create it). So thanks for the use case!
Current usage is supposed to get ElementInfo derived argument that has a class_name property (not a method.


Autocompletion for function names

And document install so people know where to put the script, possibly add a make install target. Later on I think we'll be utilizing dynamic autocomplete quite a bit more so it would be cool to get it started.

Might need a replacement for #89 anyway

Hello, i want to try this. Could you please explain a bit more. We need bash autocompletion script or it should be inside of go code?
As i see in master you are already using cobra for cmd parsing?

https://github.com/spf13/cobra#generating-bash-completions-for-your-command

@tj Would you want this Cobra autocomplete stuff in main.go, like Cobra suggests?  I imagine you would want this stuff in a separate file, but I'm not sure.  I'm working on this and would like to have the Cobra stuff where it will end up so let me know.

Hmm from the readme I'm not super clear on what their autocompletion stuff looks like haha. Hopefully we can augment it to support the dynamic function names as well.

Nevermind, I see this is for lambda function names, not Apex functions...

Right, ok.  The apex function autocompletes have been implemented right?  You're only looking for user-specific lambda function name autocompletes, now?

Nah it's for both! We removed the old stuff since it was generated from Docopt, but even getting back apex's would be cool for now, we can add functions later

Ok, the reason I asked that is I see the cobra imports in the command.go files and cobra command stuff in seemingly all of apex functions, like in delete.go.
	Use:     "delete [<name>...]",
	Short:   "Delete functions",
	Example: example,
	RunE:    run,
}````

So that doesn't work?  Obviously I haven't actually used apex yet - working on getting the binary installed now so I can see what works and what doesn't.


ipld resolver serializes data more time then nessicary

It first serialization the data to create the CID then once again to store the data.

for now im getting around this by directly interacting with the blockservice

https://github.com/ipld/interface-ipld-format/issues/32 should resolve this issue.
Can we close this?

Can be closed once https://github.com/ipld/interface-ipld-format/issues/32 is closed. Until then it's an open issue.

@vmx if this one is P0, then  ipld/interface-ipld-format#32 should be as well

cid() is now taking the serialized version of the data, hence it is fixed.


Add concurrency to the scanning script

It's so slow. maybe optionally allow for less recursion for the sake of time

fixed in the last few commits


pylint error in gauge_influx.py

I got this error when run faucet tests (on master)
Running pylint checks
************* Module faucet.gauge_influx
E:101, 8: Super of 'GaugePortStateInfluxDBLogger' has no 'update' member (no-member)
pylint of ../faucet/gauge_influx.py returns an error

Looks like you got a bad push. Sorry about that. git pull and should be
fine.
When the repo moves outside of REANNZ we can automatically enforce this, at
the moment it's a manual check.
On Wed, Aug 2, 2017 at 11:06 AM, truonghuut<EMAIL_ADDRESS>wrote:

I got this error when run faucet tests (on master)
Running pylint checks
************* Module faucet.gauge_influx
E:101, 8: Super of 'GaugePortStateInfluxDBLogger' has no 'update' member
(no-member)
pylint of ../faucet/gauge_influx.py returns an error
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/REANNZ/faucet/issues/797, or mute the thread
https://github.com/notifications/unsubscribe-auth/AEgZ1_JbawE6xquEY795DEJeMKvffWlOks5sT69_gaJpZM4OqZ8D
.


Fixed bugs when running MSM_PELE errors

I added option to choose the lagtimes when making the relaxation time plot and modify a little bit the split_trajectory.py to let me choose the output filename.
Revise --> In freeEnergy/ownbuildMSM.py and freeEnergy/computeDG.py I need to insert "rawData" in the TrajWildBasename (template name for trajectories: traj*). I harcoded it to momentarily identify and solve the issue but I'm sure it must be an easier fix.
Best,
D.

Code looks good, but how did the bug come up? If I recall correctly the code the hardcoding of rawData should not be necessary since in estimateDG.py we create copies of the trajectories in the working folder (as part of the bootstraping) that are later deleted.

Went back to the previous version of the file for problem in MSM. I think now u can accept the PR.


Clear timeout if promise has already resolves to avoid hanging open handle

Checklist

[x] yarn run dist:ci passes on my machine
[x] I have followed the commit message guidelines, with messages suitable for appearing in the changelog

Description

We are getting error from jest when running it with --detectOpenHandles

Atm, the addTimeout is not clearing the timeout when the promise has resolved which is causing this issue

Hey @YOU54F could you help me take a look at the failed CIs? I don' think it is related to my changes

yeah that’s a bit odd, i’ll trigger a ci run from main and give this a run locally and see what’s happening.
are you seeing the error requiring this change only with certain versions of node or jest? has it previously been okay?
thanks for the change. will probably be tomorrow or most likely Friday i get a change to sort ( got a talk tomorrow afternoon )

yeah that’s a bit odd, i’ll trigger a ci run from main and give this a run locally and see what’s happening.
are you seeing the error requiring this change only with certain versions of node or jest? has it previously been okay?
thanks for the change. will probably be tomorrow or most likely Friday i get a change to sort ( got a talk tomorrow afternoon )

Thanks for looking into this.
I think this is probably an issue in previous version of jest too. We are on 29.5.0 atm

Also it is an issue with the timeout not being cleaned up properly, version of jest actually doesnt matter. It just happened to catch the issue when we were using this

@vietanhtran16 @YOU54F I just pushed a pull request that fixes this issue in a different way. I noticed that Jest recommends calling .unref() on timers to prevent open handles, so that's what I added, and it solved the problem for me.
https://github.com/pactflow/pact-msw-adapter/pull/124/files

Closing in favour of #124 which is now merged and released, thanks both


Append congressional district metadata to users address

closes #774
fixes
What changed? Why?

Append congressional district metadata to address on address creation or update.
Script to backfill all addresses with congressional metadata using a zipcode to district number json file or using the google civic api as fallback

How has it been tested?

[x] Locally
[ ] Vercel Preview Branch
[ ] Unit test
[ ] Functional test

We'll also want this to be an inngest fn (or have an inngest fn that calls this) so we can run the backfill in prod with some cron cadence


Add DCO check

Add a travis-ci check to ensure all PR's commits are signed with a DCO.

Can you add a definition of what this means?

@MHBauer Done

I'm not sure what you changed, but to be explicit:

define DCO
explain or link to what it means to agree to it
explain how to do it (git commit -s)
explain that signing off means you are agreeing to the dco

I can do research, but we shouldn't make people do research, or blow off the significance of what signing off is intending to mean.


Update Github Actions workflow files

This PR updates croncheck workflow as follow:

Adds Python 3.6
Removes OS specific installation
Adds en_core_web_sm installation (last check was failed due to this)
Removes Pytorch installation (also for pythonpackage workflow)
Removes redundant flake8 installation (also for pythonpackage workflow)

And also adds torch as a test dependency in setup.py.

Yeah this simplifies things again. LGTM!


Fix BelongsToSelect key with custom OptionLabel

When using a custom OptionLabelFromRecord it used the collection id instead of model's id, fixed with mapWithKeys.

This needs to be fixed in BelongsToManySelect and BelongsToManyCheckboxes too.
See this commit:
https://github.com/laravel-filament/filament/pull/1658/commits/138793fe20e94e1d78bd9908b83d8e01fcdf6917

Added the solution to all BelongsTo coponents and replaced $relationship->getOwnerKeyName() with getKey()

I actually think getOwnerKeyName() is a more correct approach than getKey(), as you may be using a non-primary column as the owner key in the relationship.

I actually think getOwnerKeyName() is a more correct approach than getKey(), as you may be using a non-primary column as the owner key in the relationship.

Will you? Isn't that just the key of the related $record

getOwnerKeyName() will return the primary key name, whereas getKey() will return the actual value of that column, I think it's the same result but with one less step (except if the model has a mutator on the primary key)

I guess ->getKey() won't work with relations that don't use the primary key of the relation, right? Is this even a thing? 😅 Maybe your first version was better.

Ohhh you're right, reverting now

Thanks gents


Use config.php

Since 2.0.2524, plugins can have their own config.php file instead of sharing with general.php.
Would be nice to get set these in their own config.php, (then overridable by a user craft/config/patrol.php)

@timkelty I'm not sure I'll get to this prior to a (planned) major release for Craft 3. Happy to consider a pull request though😉

That's what I figured :). I mostly made the issue to remind myself to PR, but will probably just wait for a Craft 3 version.

@timkelty Cool, I'll leave the issue open then.

@timkelty I almost tackled this today but I realized that if I didn't want to force users to move their configs in config/general.php to config/patro.lphp, I had to add backwards compatibility supports and while not difficult, I decided that I'll just that for the Craft 3 version.

Sounds good.


fix: Remove focus state when no default value exists in Dropdown widget

Description
Fixes #10337
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:white_circle: Total coverage has not changed
// Code coverage diff between base branch:release and head branch: fix/menu-item

Status
File
% Stmts
% Branch
% Funcs
% Lines

:red_circle:
app/client/src/utils/WorkerUtil.ts
89.76 (0)
70.59 (-1.96)
100 (0)
93.33 (0)

:red_circle:
app/client/src/widgets/DropdownWidget/component/index.tsx
82.67 (0)
50 (-0.72)
70 (0)
81.43 (0)

/ok-to-test sha=7e1204c

/ok-to-test sha=dfe50a8

/ok-to-test sha=77882bf

Closing this as issue in favour of v2 changes https://github.com/appsmithorg/appsmith/pull/10359


[X] Yes, I am willing to submit a PR!

Code of Conduct

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

the GitHub workflow has pushed all 1.4.0 images to the docker hub.


any credit history can see?

it just show used all creadit.

Indeed. No history or calculation to find.

Hey, all! We are actively working on providing a clearer in-app status for the tokens. We appreciate your patience and will deploy the first updates as soon as possible so today and over the next couple of days, you can expect a continually improving experience.
Additionally, as we have been working on optimizing the tokens usage and accidentally triggered the limit on the accounts that weren't close to the limit. We've reverted the change so this should now be resolved. I'll close the issue, but in case a problem persist, please open a new one! Thank you for being an early adopter and for your patience as we're ironing out the experience on bolt!


Better error when the user uses a task that's too small

A user was running a salmon task on a @small_task.
No errors were thrown. The task simply ended with a "Success" status, which is confusing.
Insufficient task size should return a more semantic error in task logs.

If a task fails due to lack of resources I can confirm that it will not show a "Success" status.
Closing because this has been around for a while and is vague


fix: special handle Bitcoin Testnet gas price estimator

Description
Closes: 2386
How Has This Been Tested?

[ ] Tested CCTX in localnet
[ ] Tested in development environment
[x] Go unit tests
[ ] Go integration tests
[ ] Tested via GitHub Actions

Summary by CodeRabbit

New Features

Introduced special handling for Bitcoin testnet gas price estimator.
Added functionality to determine the highest fee rate from recent blocks.

Refactor

Updated PostGasPrice function to handle different network types.
Renamed and adjusted test functions for better clarity and usage of specific chain IDs.

Tests

Added new test for recent fee rate retrieval.
Updated existing tests to use specific chain IDs instead of hardcoded values.

👏🏻👏🏻


Day 0 exploit regarding UnitIDs

The difference of IDs between sequentially created units, regardless of which player created them, is 262144 (for probes) plus/minus 2. This can be used to determine how many units your opponent has created since you last created a unit, which can be used to detect ling rushes and among other things.
Proposed fix: have the protocol make a mapping between real unit id and a random tag, then interchange them where appropriate.
See discussion on the discord regarding this.

Closing issue, made a duplicate issue on the proto repo, as this is a proto fix, not an API fix
https://github.com/Blizzard/s2client-proto/issues/161


fix(nexus): add status to chains cli query

Description

Allow filtering the list of chains by status in nexus CLI query

Todos

[ ] Unit tests
[ ] Manual tests
[ ] Documentation
[ ] Connect epics/issues
[ ] Tag type of change
[ ] Upgrade handler

Steps to Test
Expected Behaviour
Other Notes

you are putting two very different things into one PR, fixing vald Eth2 behaviour and the addition of chain status. Please split this

Sorry, forgot to update the base to the release branch, hence all the old commits.


pop up when document has been updated

It would be nice to have a pop up to tell users to refresh the page when the document has been updated. So when they insert a clef on an empty staff or when they merge systems.

Added in a286f4c


Documentation: Add new sections to release doc

Adds some brief documentation on doing manual testing and also how to pull in changes into a release branch.

LGTM


PLAT-10459: Logging configuration example

Ticket
PLAT-10459
Description
As part of the datafeed example a sample logging configuration is
provided, sending logs to the console and to rotating files. This is
mostly here to illustrate how logging can be used in a bot.
Also handled KeyboardInterruptException in the example to avoid the
stacktrace when we quit the application.
The example has been rewritten as a script, if you are ok with that I'll
move other examples as well. It is shorter and easier to understand.
poetry build was failing so the package has been configured properly and
the package's name changed to what is actually published on pypi (might
change later).
Dependencies
N/A
Checklist

[X] Referenced a ticket in the PR title and in the corresponding section
[X] Filled properly the description and dependencies, if any
[N/A] Unit tests updated or added
[N/A] Docstrings added or updated
[X] Updated the documentation in docs folder

Oups I did not update the other examples! Will open another PR for that


fix: Change in description field variable in DayScheduleAdapter

Fixes #1262
Changes:

Instead of getDescription(), getSummary() is called.
Removed unnecessary result variable.

Screenshots for the change:

@the-dagger @mananwason Please review! :+1:

@arp95 Thanks for your opinion. The UI was designed in such a way that the item is having a description field between the title and location and it looks good in that way. It's no harm to change the field to a non null field instead of null description. I hope its okay with you to let mentors decide if its necessary or not :) :+1:

@harshitagupta30
well why i was disapproving was according to the commit guidelines "fix" stands for a bug fix. I think this is not a bug fix going on. Use of a relevant commit message of "whatever" this pr is solving will gice the mentors a better idea.
Cheers!

@arp95 Alright! Thanks for suggestion! I'll update the commit message :+1:


Large font seems to add extra blank space to the right of the floating label

If I specify a font size for my page like this:
<style>
  :root {
    --size: 50px;
  }
</style>

Floating labels seem to leave quite a bit of blank space to the right of the label. Large the font I specify, larger the blank space gets.
Here is a demo: https://codepen.io/coffeeandwork/pen/abQmWje

If you remove that <style> element from the <head> of the page, this problem goes away.

The pure CSS method is working: https://codepen.io/laurentpayot/pen/XWyjYPG
It must be something in JS like textWidth().

I fixed it in this commit https://github.com/beercss/beercss/commit/f658671026451ba201a2f78c3895cdb138f27028. The text width (in px) wasn't dividing by the modified --size.


Warn if directive is not applicable

Some directives may be present in AST places where they are actually inert. This may come as a surprise to the user, and should probably at least result in issuing a compilation time warning.
For example, applying //dd:span on something that is not a function node will do nothing.

Hi @RomainMuller,
I would like to work on this issue.
First of all, I really loved the tech and the thought process behind orchestrion(AOP) and thanks to you and the team at DataDog for all the hard work behind this.
I did take a look at the code base and do have some questions, couldn't find this in the docs.

How can I debug and test this in local env?
I tried building orchestrion binary locally and feeding the samples dir as below by enabling debug/trace logs
 go build .
 cd samples
 ../orchestrion go build -work ./...

Is this the right way to go about it?

Does the build cache include the modified files ?
I can see the modified files with traces added for dep such as net/http,  gorm et al. in the $WORK dir, but I couldn't see the modified files for main.go and other_handlers.go when I ran orchestrion for samples/server

What role does the jobserver aka NATS play in this?

Hey @joobisb

How can I debug and test this in local env?

You should be able to use the snapshot tests for this... in particular go test ./internal/injector -update (these are implemented using golden).

Does the build cache include the modified files ?

If there is no modified file in $WORK then no file has been modified. It's possible some of these files no longer incur modifications because the instrumentation is done library-side.

What role does the jobserver aka NATS play in this?

The jobserver's role is to prevent duplicate effort at large...

It caches the value of the version string addendum that is appended to the output of -V=full invocations of the tools (which go uses to determine the complete -buildid, one of the inputs to the build artifact cache, so that orchestrion instrumented objects are separate to the regular objects); as this can be a little expensive to compute
It does importPath -> package archive resolution for injected dependencies, so that these are done exactly once (preventing the possibility that 2 resolutions of the exact same package happen in parallel, which is a waste of time/resources).


Enable email notifier to send emails for health check failures

Description
This change enables to send email notifications for healthcheck failures on backend trino clusters.
New fields added in the NotifierConfiguration.java class:
enabled - To enable or disable sending emails for healthcheck failures
gatewayInstance - To specify gateway instance name in case there are multiple instances. This will be displayed in the email subject so that one can know in which instance the cluster is unhealthy.
customContent - To provide custom email body in case the default content is not very helpful.

Additional context and related issues

Release notes
( ) This is not user-visible or is docs only, and no release notes are required.
(X) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text:
*

@prakhar10 can you fix the compile failure?

@prakhar10 are you still working on this one or can we close this?

yes, sorry for the delay, i'll get back on this by sunday.


Home Page doesn't exist yet.

Need to add the home page.

Home Page shows the list of currently airing anime.


Automatic updates for mainnet

Purpose
To bring automatic updates to the application. This is done by publishing new releases to GitHub releases alongside normal distribution channels.
This is only enabled for, and only works for mainnet releases.
Changes

Automatic update notification will trigger when an update is available for the application
Update is verified by matching checksum and signature of downloaded binary with published checksum and signature

Assumes public key for verification will be accessible at: "https://distribution.mainnet.concordium.com/tools/concordium-desktop-wallet-pubkey.pem"

Script for generating verification assets (sha256 checksum + signature) of binaries
Updated readme with description of how to use the aforementioned script

Checklist

[x] My code follows the style of this project.
[x] The code compiles without warnings.
[x] I have performed a self-review of the changes.
[x] I have documented my code, in particular the intent of the
hard-to-understand areas.
[x] (If necessary) I have updated the CHANGELOG.

Remember to create a documentation issue to make sure that our user documentation is updated accordingly.


mqtt subscribing to private path had a small bug

The Topic to which the mqtt is subscribing in MqttToRosBridge is wrong with respect to the condition of private path. It should use the member variable _topic_from because that has the private path extracted topic name.

Can this be reviewed? It resolves #19

Hi @kapilPython,
Thank you for your contribution. Your changes look good, could you kindly confirm the comment I added?


[Design] Add support for API error response type based on RFC 7807

I :heart: this! I saw @rynowak's KodKod repo a few days ago and saw this coming. I use something like this (problem+json) in all my APIs.
I can't help thinking this would be even better as middleware, so you could add it to the start of the pipeline and make sure all non-200 responses would be returned in a proper representation.
It would also be nice to be able to map different exceptions to different problem types. Something like options.Handle<ValidationException>(ex => new ValidationProblem(ex)) where ValidationProblem is a derived type from Problem.

@khellang there's a discussion about moving it further up the stack - https://github.com/aspnet/Diagnostics/issues/346. Our plan was to get something going in Mvc and see if we can move the contract to diagnostics so it does the right thing for API responses.

A problem with the dictionary approach and the way it's currently implemented (using nameof) is that you loose the ability to follow the user's preferred casing for JSON since it won't, by default, change casing for dictionary keys. This means that all JSON properties will always be PascalCased using this approach.

I can't help thinking this would be even better as middleware, so you could add it to the start of the pipeline and make sure all non-200 responses would be returned in a proper representation.

Yep. We're starting here.

@khellang - since you've been doing something similar do you have an O/M for problem that you like already? Wondering if we can borrow some inspiration...

Not really much for inspiration...
    /// <summary>
    /// Represents "Problem Details for HTTP APIs"
    /// </summary>
    /// <remarks>
    /// See RFC 7807 - https://tools.ietf.org/html/rfc7807
    /// </remarks>
    public class ProblemDetails
    {
        public static readonly Uri AboutBlank = new Uri("about:blank");

        /// <summary>
        /// A URI reference that identifies the problem type.
        /// </summary>
        /// <remarks>
        /// This specification encourages that, when dereferenced, it provide
        /// human-readable documentation for the problem type (e.g., using HTML).
        /// </remarks>
        public Uri Type { get; set; } = AboutBlank;

        /// <summary>
        /// A short, human-readable summary of the problem type.
        /// </summary>
        /// <remarks>
        /// It SHOULD NOT change from occurrence to occurrence of the problem, except
        /// for purposes of localization (e.g., using proactive content negotiation).
        /// </remarks>
        public string Title { get; set; }

        /// <summary>
        /// The HTTP status code generated by the origin server for this occurrence of the problem.
        /// </summary>
        public int Status { get; set; }

        /// <summary>
        /// A human-readable explanation specific to this occurrence of the problem.
        /// </summary>
        public string Detail { get; set; }

        /// <summary>
        /// A URI reference that identifies the specific occurrence of the problem.
        /// It may or may not yield further information if dereferenced.
        /// </summary>
        public Uri Instance { get; set; } = AboutBlank;
    }

I basically inherit from that to add properties specific to the different problem types. Something like
public class ValidationProblemDetailsModel : ProblemDetailsModel
    {
        public ValidationProblemDetailsModel()
        {
            Errors = new Dictionary<string, string[]>();
        }

        public IDictionary<string, string[]> Errors { get; set; }
    }

🆙 📅

Problem no longer derives from a Dictionary, so that's somewhat cleaner. I made it a property instead to stash arbitrary additional values. Derived types like the ones @khellang uses (sans the error mapping) is supported if you'd rather use strongly typed models. I tried playing around with dyanamic here but since all you do is assign stuff, the programming model doesn't seem nicer.
Wrote a custom Json formatter. Also works with Xml.
Need to figure out how to get it use the right Content-Type. Right now it says application/json. We want it to say application/problem+json.

If you're creating the ObjectResult you can put the content type there.

Closing this in favor of focused set of PRs starting from https://github.com/aspnet/Mvc/pull/6742.


Prevent launching secondary_master for EMBEDDED journal

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/6141/
Test PASSed.

alluxio-bot, merge this please.


Release beta-tensorflow 2.0.2-1.3.0-beta (automated commit)

Release beta-tensorflow 2.0.2-1.3.0-beta (automated commit)
Description:
Initial beta release of TensorFlow community package
https://github.com/mesosphere/dcos-tensorflow/tree/2.0.2-1.3.0
Source URL: https://infinity-artifacts-ci.s3.amazonaws.com/autodelete7d/tensorflow/20171020-185328-pqapRVSMcfXyu2Je/stub-universe-tensorflow.json
Changes since revision -1:
4 files added: [config.json, resource.json, marathon.json.mustache, package.json]
0 files removed: []
0 files changed:

@ArtRand here is the universe PR.

Tested examples from dcos-labs/dcos-tensorflow-tools (specifically mnist, cifar-10, and gan) with this stub-universe on an Enterprise DC/OS cluster on GCE, as well as an Open DC/OS cluster on AWS (both 1.10). All examples deployed correctly and behaved as expected.
The package files also lgtm 👍 .

@imaxxs could I get a review from you too?

LGTM

Looks good.

In there interest of having this ready for Mesoscon I'm okay with it being published as is, but I can't find anyone giving a definitive answer on whether this should be beta or not.

Thanks for the reviews @benclarkwood and @imaxxs. Are any of the changes such that we should hold back the merge until they are done? (Perhaps the beta notes?)
Due to the nature of how TF is used, it is uninstalled and reinstalled repeatedly, and as such making these changes after the fact should not be too much of an issue.

@imaxxs @benclarkwood thanks for your reviews. I have addressed the port types and the misnaming of the dcos virtual network in this PR, but will change the default user in the next release. I'm still waiting on @joerg84 to merge his example changes, but will get that done tomorrow and then merge this PR.

I am closing this PR. New PR incomming.


[VA] Deployment Updates

For tracking needed deployment/service updates for 4.4 release.

[ ] ARM Template deployment
[ ] Dispatch updates

[ ] Utilize dispatch create and dispatch refresh
[ ] Plan for pulling in model subsets as dispatch intents

[ ] Update general model to latest

Related issues:
#827
#837
#790
#752
#702
#324
#117

Fairly minor but could we look to echo some progress along the way as it takes quite a while. The suppression of logging can lead to people thinking it's stopped..


[Bug] Cannot browse the marketplace because "0 recipes to search and transform code across NaN projects"

Logs that might help :
_app-c9d4fa7d6a441b69.js:211 Object undefined
ea @ _app-c9d4fa7d6a441b69.js:211
_app-c9d4fa7d6a441b69.js:211 TypeError: Cannot read properties of undefined (reading 'length')
    at _app-c9d4fa7d6a441b69.js:238:74935
    at eu (_app-c9d4fa7d6a441b69.js:238:70064)
    at _app-c9d4fa7d6a441b69.js:238:92276
    at tF (_app-c9d4fa7d6a441b69.js:238:61085)
    at new tj (_app-c9d4fa7d6a441b69.js:238:60537)
    at rY._promise (_app-c9d4fa7d6a441b69.js:238:92252)
    at rC._trans (_app-c9d4fa7d6a441b69.js:238:70143)
    at rC.bulkPut (_app-c9d4fa7d6a441b69.js:238:74640)
    at rY.<anonymous> (_app-c9d4fa7d6a441b69.js:211:235509) undefined
ea @ _app-c9d4fa7d6a441b69.js:211
_app-c9d4fa7d6a441b69.js:211 TypeError: Cannot read properties of undefined (reading 'length')
    at _app-c9d4fa7d6a441b69.js:238:74935
    at eu (_app-c9d4fa7d6a441b69.js:238:70064)
    at _app-c9d4fa7d6a441b69.js:238:92276
    at tF (_app-c9d4fa7d6a441b69.js:238:61085)
    at new tj (_app-c9d4fa7d6a441b69.js:238:60537)
    at rY._promise (_app-c9d4fa7d6a441b69.js:238:92252)
    at rC._trans (_app-c9d4fa7d6a441b69.js:238:70143)
    at rC.bulkPut (_app-c9d4fa7d6a441b69.js:238:74640)
    at rY.<anonymous> (_app-c9d4fa7d6a441b69.js:211:235509) undefined
ea @ _app-c9d4fa7d6a441b69.js:211
_app-c9d4fa7d6a441b69.js:211 Object undefined
ea @ _app-c9d4fa7d6a441b69.js:211
_app-c9d4fa7d6a441b69.js:211 TypeError: Cannot read properties of undefined (reading 'length')
    at _app-c9d4fa7d6a441b69.js:238:74935
    at eu (_app-c9d4fa7d6a441b69.js:238:70064)
    at _app-c9d4fa7d6a441b69.js:238:92276
    at tF (_app-c9d4fa7d6a441b69.js:238:61085)
    at new tj (_app-c9d4fa7d6a441b69.js:238:60537)
    at rY._promise (_app-c9d4fa7d6a441b69.js:238:92252)
    at rC._trans (_app-c9d4fa7d6a441b69.js:238:70143)
    at rC.bulkPut (_app-c9d4fa7d6a441b69.js:238:74640)
    at rY.<anonymous> (_app-c9d4fa7d6a441b69.js:211:235509) undefined
ea @ _app-c9d4fa7d6a441b69.js:211
_app-c9d4fa7d6a441b69.js:211 Object undefined
ea @ _app-c9d4fa7d6a441b69.js:211
_app-c9d4fa7d6a441b69.js:211 Object undefined
ea @ _app-c9d4fa7d6a441b69.js:211
_app-c9d4fa7d6a441b69.js:211 Object undefined
ea @ _app-c9d4fa7d6a441b69.js:211
_app-c9d4fa7d6a441b69.js:211 TypeError: Cannot read properties of undefined (reading 'length')
    at _app-c9d4fa7d6a441b69.js:238:74935
    at eu (_app-c9d4fa7d6a441b69.js:238:70064)
    at _app-c9d4fa7d6a441b69.js:238:92276
    at tF (_app-c9d4fa7d6a441b69.js:238:61085)
    at new tj (_app-c9d4fa7d6a441b69.js:238:60537)
    at rY._promise (_app-c9d4fa7d6a441b69.js:238:92252)
    at rC._trans (_app-c9d4fa7d6a441b69.js:238:70143)
    at rC.bulkPut (_app-c9d4fa7d6a441b69.js:238:74640)
    at rY.<anonymous> (_app-c9d4fa7d6a441b69.js:211:235509) undefined
ea @ _app-c9d4fa7d6a441b69.js:211
_app-c9d4fa7d6a441b69.js:211 Object undefined
ea @ _app-c9d4fa7d6a441b69.js:211
_app-c9d4fa7d6a441b69.js:211 Object undefined
ea @ _app-c9d4fa7d6a441b69.js:211
_app-c9d4fa7d6a441b69.js:211 Object undefined
ea @ _app-c9d4fa7d6a441b69.js:211
_app-c9d4fa7d6a441b69.js:211 Object undefined
ea @ _app-c9d4fa7d6a441b69.js:211
_app-c9d4fa7d6a441b69.js:211 TypeError: Cannot read properties of undefined (reading 'length')
    at _app-c9d4fa7d6a441b69.js:238:74935
    at eu (_app-c9d4fa7d6a441b69.js:238:70064)
    at _app-c9d4fa7d6a441b69.js:238:92276
    at tF (_app-c9d4fa7d6a441b69.js:238:61085)
    at new tj (_app-c9d4fa7d6a441b69.js:238:60537)
    at rY._promise (_app-c9d4fa7d6a441b69.js:238:92252)
    at rC._trans (_app-c9d4fa7d6a441b69.js:238:70143)
    at rC.bulkPut (_app-c9d4fa7d6a441b69.js:238:74640)
    at rY.<anonymous> (_app-c9d4fa7d6a441b69.js:211:235509) undefined
ea @ _app-c9d4fa7d6a441b69.js:211
_app-c9d4fa7d6a441b69.js:211 Object undefined
ea @ _app-c9d4fa7d6a441b69.js:211

bulkPut(er, eo, ei) {
                let ea = Array.isArray(eo) ? eo : void 0
                  , es = (ei = ei || (ea ? void 0 : eo)) ? ei.allKeys : void 0;
                return this._trans("readwrite", eo=>{
                    let {auto: ei, keyPath: eu} = this.schema.primKey;
                    if (eu && ea)
                        throw new e5.InvalidArgument("bulkPut(): keys argument invalid on tables with inbound keys");
                    if (ea && ea.length !== er.length)
                        throw new e5.InvalidArgument("Arguments objects and keys must have the same length");
                    let ec = er.length
                      , ed = eu && ei ? er.map(rk(eu)) : er;
                    return this.core.mutate({
                        trans: eo,
                        type: "put",
                        keys: ea,
                        values: ed,
                        wantResults: es
                    }).then(({numFailures: er, results: eo, lastResult: ei, failures: ea})=>{
                        if (0 === er)
                            return es ? eo : ei;
                        throw new e2(`${this.name}.bulkPut(): ${er} of ${ec} operations failed`,ea)
                    }
                    )
                }
                )

I meant to publish this in the board for the public service, my bad

@yeikel This was probably just an intermittent failure while the service was being deployed. Please reopen if it is persistent on your end.

@sjungling Do you maybe see anything we could / should do about this?

Btw, I am still seeing it today. Are you still deploying?

Fun fact, navigating to build and back to marketplace magically fixed it

Btw, I am still seeing it today. Are you still deploying?

No, but maybe "again" :-)
If you keep seeing this, we will have to investigate. Thanks for the update!


Metropolis Adjusted Langevin algorithm

Here's a first attempt at merging sgmcmcjax into blackjax. Sorry it took ages to get something done! I've had loads of work and paper deadlines/revisions/etc.. :(
I added the following:

diffusions function:

state includes gradient_state. This is to store stuff that will be needed for fancier gradient estimators (SVRG for example)
iteration number i is set to 0. This should be stored in some kind of state

Gradient estimators

build_grad_log_post builds the gradient function that takes in parameters and the data (which might be a minibatch)
build_gradient_estimation_fn: returns the gradient estimator as well as the function that initialises the gradient state (the gradient at the first iteration will be based on a minibatch of data)

Build kernels:

Build ULA kernel
Build SGLD kernel: same as ULA but you pass in a batch size as well as a random key to initialise the gradient

I did some copy paste from sgmcmcjax, but tried to follow the API that @rlouf suggested. But I'm not sure what the best way is to define state. We need a state for the chain (like for standard mcmc), but we also need state for the gradients (not for this simple gradient estimator, but for SVRG for example).
Anyways have a look at this is let me know what your thoughts are. I added a notebook that runs boths algorithms in notebooks/sgld_ula.ipynb.

Looks great ! The example in the notebook can probably be a test in the test suite instead (we need a test).

@jeremiecoullon I simplified the interface a lot to be able to merge MALA asap. We will need to change a few things for SgLD of course, but let's move more incrementally from one stable state to the next. I just need to add some documentation and this should be ready to merge.

I need to close because I deleted a commit and github did not take it into account in the PR (but it did on the originating branch),


fix: #27 - Implement the "protected branches" API endpoint

Could you please take a look at my PR?

Hi @rbartuzel ! Thank you for the PR!
We are striving to add for all new/fixed features tests for initially configuring, changing and deleting given feature. Can you please add tests for changing branch protection level and for removing protection of a branch?

Hi! I have added tests for changing branch protection level and for removing protection of a branch.

For me using branch names with wildcards doesn't work, because it still uses the old endpoint for unprotecting branches.

Thanks @wadimklincov !
@rbartuzel : how about we:

Make unprotect method call both old API (like it does now) and the new one (like @wadimklincov suggested) to ensure that given branch is really unprotected.

Make unprotect method calls accept 404 as the return code too (we already do that in a few other places, see https://github.com/egnyte/gitlabform/blob/master/gitlabform/gitlab/members.py#L18 as an example).

Add some more tests for unprotecting and protecting:

a) configure protection using old API and switch it to new,
b) the other way around,
?
I think we would have all cases covered then.

@gdubicki Sounds like a good idea, I'll try to fix it.

Hi!
I noticed that it's not required to call unprotect using both api method. Unprotect method from new api can also unprotect branches protected old way.
I modified one of existing test to cover use case with wildcards, and added new ones to cover use case with set protection using old api and updating with new api and vice versa.
If you have any comments or suggestions, just let me know.

Awesome, it works great!
I just have two things I noticed while testing:

if protected: false is set, but the rest of the parameters are still specified, it's still protected
if the branch is removed from the configuration, it still stays protected

I guess the latter one is difficult to do, though.

@wadimklincov thanks for testing!
I fixed first issue but in case of the second, I agree it could be difficult to do.

LGTM. Thanks for implementation @rbartuzel and for the tests @wadimklincov !


Fine-tuning the model on an unseen language pair

Can someone tell me how to fine-tune the IndicTrans2 model for Bhojpuri to English translation?

In order to extend the models to unseen languages, it is necessary to incorporate the representation of tokens specific to the newer languages into the existing vocabulary, along with their corresponding language tags.
This entails expanding the fairseq dictionaries and embedding matrices of the model to ensure compatibility, enabling subsequent fine-tuning for the inclusion of unseen languages.
Regarding Bhojpuri, which is in the Devanagari script and shares linguistic similarities with Hindi and Maithili, it is reasonable to assume that the current vocabulary already contains a satisfactory coverage of the language's subwords.
Therefore a potential quick-fix solution, involves substituting any unused tags in the fairseq dictionary (dict.src.txt) with the Bhojpuri language tag, bho_Deva , post which fine-tuning would be possible.
To accommodate the incorporation of additional languages while preserving the existing performance on other languages, alternative techniques such as adapter-tuning can also be considered.
You can check this repository  for adapter-based fine-tuning.

Thank you for the quick reply! I will try this solution. Sorry to bother you again with silly questions, I am just a beginner in the area of MT. Can you please help me with the following questions?

Yes.
Train a new SPM model on a sample of the data corresponding to the languages you wish to newly introduce. Use this SPM model and binarize the data (You can use prepare_data_joint_training.sh).
Now, update the SPM model provided with IndicTrans2 by adding the new tokens (remember to only add new tokens and ensure no duplicate tokens are being added).
Update the fairseq dicts in a similar way by appending the unique tokens (in the unseen languages) in the IndicTrans2 fairseq dicts and also add the language tags corresponding to the unseen languages. (remember to only add new tokens and ensure no duplicate tokens are being added).

Next, you need to update the embedding matrices of the pretrained checkpoints accordingly to make everything consistent, post which you should be able to finetune this updated checkpoint.
We will add details about how to Fine-tune the model on an unseen language pair in the README and also provide the necessary helper scripts soon.

Thanks again! I was able to start training the Bhojpuri to English model, and will now fine-tune IndicTrans2 on an unseen language as well.

I want to finetune IndicTrans2 model for translation to business language(some word don't need to change while eng-hin lang translation) and retrain the model on another dataset with samantar dataset , can anyone please help me to find out this?


No ability to list Horizontal Pod Autoscalers.

From @bharris47 on December 31, 2016 20:37
Would be nice to be able to view and edit the current state of hpas (cpu percent, min, max, etc).
Copied from original issue: skippbox/cabin-issues#22

The view can be added easily. What would like to edit in them ?

From @bharris47 on January 1, 2017 18:27
Changing the max would be helpful. Being able to see current CPU usage within them would be great. It would also be really useful to be able to create an HPA for a deployment.

ok thanks , we will slate that for a new release cc/ @kemcake

From @CelsoSantos on June 9, 2017 11:7
I too would very much appreciate this functionality

ok, we will most likely open source cabin, so stay tune...


falcon.py -> falcon_plugin.py to fix rel imports for py2.7

Python 2.7 seems to have problems with this import.

Codecov Report

Merging #11 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #11   +/-   ##
=======================================
  Coverage   97.05%   97.05%
=======================================
  Files           3        3
  Lines          34       34
=======================================
  Hits           33       33
  Misses          1        1

Impacted Files
Coverage Δ

falcon_apispec/falcon_plugin.py
96.77% <ø> (ø)

falcon_apispec/__init__.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Cut a new release and uploaded to PyPI. Cheers!
🎉


Distance and Direction WAB widget: A selected tool needs to be deselected between change of tabs

Widget
Distance and Direction WAB widget
Version of widget
2.1 & 2.2
Bug or Enhancement
When changing tabs within the widget any selected tool needs to be deselected otherwise you end up drawing multiple graphics at once

@kgonzago
Fixed please verify all functioning correctly

Verified.


Flaky test in windows GPU CI

In the windows-GPU stage of the CI, different test_random tests fail.
test_random.test_exponential_generator fails on commit 6a293fc but passes after updating README
https://github.com/apache/incubator-mxnet/pull/13595
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Fwindows-gpu/detail/PR-13595/9/pipeline
test_random.test_uniform_generator
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Fwindows-gpu/detail/PR-13681/37/pipeline
Seems to only occur on windows GPU build.
For Q & A and discussion, please start a discussion thread at https://discuss.mxnet.io
Description
(Brief description of the problem in no more than 2 sentences.)
Environment info (Required)
What to do:
1. Download the diagnosis script from https://raw.githubusercontent.com/apache/incubator-mxnet/master/tools/diagnose.py
2. Run the script using `python diagnose.py` and paste its output here.

Package used (Python/R/Scala/Julia):
(I'm using ...)
For Scala user, please provide:

Java version: (java -version)
Maven version: (mvn -version)
Scala runtime if applicable: (scala -version)

For R user, please provide R sessionInfo():
Build info (Required if built from source)
Compiler (gcc/clang/mingw/visual studio):
MXNet commit hash:
(Paste the output of git rev-parse HEAD here.)
Build config:
(Paste the content of config.mk, or the build command.)
Error Message:
(Paste the complete error message, including stack trace.)
Minimum reproducible example
(If you are using your own code, please provide a short script that reproduces the error. Otherwise, please provide link to the existing example.)
Steps to reproduce
(Paste the commands you ran that produced the error.)

What have you tried to solve it?

Another test which failed on Windows GPU :
test_operator_gpu.test_multinomial_generator
The failure is here on Jenkins : http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Fwindows-gpu/detail/PR-13678/24/pipeline


Threefold repetition

Puzzle solution isn't 1. Kf7 because 72. Kf7 would cause threefold repetition:
http://en.lichess.org/training/13110
from source game
http://en.lichess.org/obfiogcm#142

we're done generating puzzles. This code is dormant.


What is the best way for me to take the stream and push it to AWS S3?

I am successfully receiving stream on my server from OBS studio. I am poking my head around but I figure someone should have the answer. How to I take stream and throw it up to AWS S3?

Ideally in h.264 format using ffmpeg to serve from cloudfront with manifest playlist in two different resolutions


Fix typo

In addition, the naming convention in the code is a bit confusing, some are CamelCase some are snake_case. I think it needs to be unified.

I can help with the naming convention if you'd like


☂ package:unified_analytics implementation in flutter tool

Tracker issue for the migration from GA3 to GA4 with the use of package:unified_analytics
Tasks:

Setup the analytics instance to use the same logic as package:usage for initialization

[x] https://github.com/flutter/flutter/pull/134756

Migration of doctor events from DoctorResultEvent

[x] PR in dart-lang/tools to add event: https://github.com/dart-lang/tools/pull/178
[x] PR in flutter/flutter to use new event: https://github.com/flutter/flutter/pull/136647

Migration of build events from BuildEvent

[x] PR in dart-lang/tools to add event: https://github.com/dart-lang/tools/pull/187
[x] PR in flutter/flutter to use new event: https://github.com/flutter/flutter/pull/137562

Migration of hot reload events from HotEvent

[x] PR in dart-lang/tools to add event: https://github.com/dart-lang/tools/pull/193
[x] PR in flutter/flutter to use new event: https://github.com/flutter/flutter/pull/137717

🚫 Migration of event PubResultEvent -- Migration is not necessary since pub will be sending its own events soon

[x] PR in dart-lang/tools to add event: https://github.com/dart-lang/tools/pull/194
[x] PR in flutter/flutter to use new event: https://github.com/flutter/flutter/pull/138012

Migration of event CommandResultEvent and Usage.command

[x] PR in dart-lang/tools to add event: https://github.com/dart-lang/tools/pull/199
[x] PR in flutter/flutter to use new event: https://github.com/flutter/flutter/pull/138165
[x] PR in dart-lang/tools to add commandHasTerminal param: https://github.com/dart-lang/tools/pull/204
[x] PR in flutter/flutter to include commandHasTerminal param: https://github.com/flutter/flutter/pull/138806

🚫 Migration of event AnalyticsConfigEvent

[x] Not necessary because package:unified_analytics already emits an event on opt out/in

Migration of event CodeSizeEvent

[x] PR in dart-lang/tools to add event: https://github.com/dart-lang/tools/pull/200
[x] PR in flutter/flutter to use new event: https://github.com/flutter/flutter/pull/138351

🚫 Migration of event ErrorHandlingEvent

[x] Not necessary because there are no callers of this event

🚫 Migration of event [NullSafetyAnalysisEvent]

[x] PR in dart-lang/tools to add event: https://github.com/dart-lang/tools/pull/202
[x] PR in flutter/flutter to use new event: https://github.com/flutter/flutter/pull/138419

Migration of event UsageEvent – these events are all ios/macos related

[x] PR in dart-lang/tools to add event: https://github.com/dart-lang/tools/pull/206
[x] PR in flutter/flutter to use new event: https://github.com/flutter/flutter/pull/138806

Migration of sendException

[x] PR in dart-lang/tools to add event: https://github.com/dart-lang/tools/pull/206
[x] PR in flutter/flutter to use new event: https://github.com/flutter/flutter/pull/138806

Migration of timing events (sendTiming method)

[x] PR in dart-lang/tools to add event: https://github.com/dart-lang/tools/pull/208
[x] REVERTED PR in flutter/flutter to use new event: https://github.com/flutter/flutter/pull/138896

[x] PR for Relanding in flutter/flutter: https://github.com/flutter/flutter/pull/139299

Migration of the CustomDimensions which are sent from the FlutterCommand.verifyThenRunCommand

[x] PR in dart-lang/tools to add event: https://github.com/dart-lang/tools/pull/211
[x] PR in flutter/flutter to use new event: https://github.com/flutter/flutter/pull/139383

Post migration updates needing to be made

Send enabled features with each event

[x] PR in dart-lang/tools to add parameter: https://github.com/dart-lang/tools/pull/217
[x] PR in flutter/flutter to use new parameter: https://github.com/flutter/flutter/pull/139934

Cherrypicks into stable

[x] PR in flutter/flutter: https://github.com/flutter/flutter/pull/141019

This finally complete! The CP that was merged in today into stable includes the migration for usage values. All other events are expected to make it into stable for the February 2024 release

I'm not sure if this was intentionally reopened, but I'll close again, and ongoing work can be tracked individually instead of in the umbrella.


fixe issues parsing xml file

fixe error for parsing xml file
fixe issue test/test_device.xml not found

@Badzi007 sorry for letting this repo go stale for so long. If you resolve the new conflicts I can get this PR merged and a new version released


Feature: New Action - Reseed button

I would like to be able to reseed for a selected shape.
Especially when drawing squared boxes some seeds give double lines that are obstructing.
Having a button to press (e.g. in Actions) would be nice to have
fa-recycle comes to mind.

Example

I don't think adding a dedicated button for a low-level feature like this is the right way to go --- our guiding principle for Exalidraw is to get the defaults right, and offer limited customization for the rest.
If the behavior on the whole is suboptimal, we should address that instead. We haven't gotten complaints on this yet (apart from yours).
But I agree that there are cases where it would be handy. Whether it warrants a new feature is another matter. If this gets rejected, we could possibly add a shortcut for it, for those that really care.

For reseeding specifically one suggestion would be to reseed by default when you change to the "sloppiness" from architect to Artist or cartoonist.
As UX goes they have already significantly changed the line-style (which is already unique for every drawn shape) so I don't think the line being slightly different while toggling options would be startling.
Ultimately I think the real complaint is is the multi-stroke line or the roughness in general.
draw.io which uses the same underlying library (rough.js) exposes wayyy more options but two things they did for this are

added a "Comic Style" which turns down the "roughness" and sets the disableMultiStroke Parameter for a simpler effect.
exposes a toggle for the disableMultiStroke directly.

(Article on how they use rough.js)
Some quick simple options:

as excalidraw already has an artist and comic "sloppiness" level I'd consider one of them having disableMultiStroke set to true
Choose one of the existing levels (say cartoonist) and if the shape is cartoonist expose a new stroke style of "clean" which is just a toggle of the disableMultiStroke property

That was quick, probably already helpful enough, but also kind of hidden. Thanks.

I think we can close that one!


Scaling up image causes 'body size is too long' error

Hi,
I have a 3.1MB image measuring 2353x1956px (stored in S3). The Lambda function successfully requests an upscaled (2356x1988) version image (returning a 200 status code) but then throws a body size is too long message. When requesting scaled down images, there does not seem to be any errors.
The requesting URL is:

https://redacted/2356x1988/path/to/image/file.jpg

I've also tried:

https://redacted/fit-in/2356x1988/path/to/image/file.jpg
https://redacted/fit-in/2356x1988/filters:upscale()/path/to/image/file.jpg

My Lambda function has a 10 second timeout and has a large memory allocation of ~1.5GB.
Would appreciate any thoughts or advice.
Conor

Hey @lithiumoxide, the "body size is too long" message is a known issue and is typically thrown when the resulting image exceeds the Lambda payload limit of 6 MB. The upscaling might cause the output image to exceed this limit and throw the message you've been seeing.
We've added a workaround to our feature backlog for this solution that could allow users to output images to an S3 bucket of their choice (i.e. a bucket named 'output-images') which would circumvent the payload limit, but don't have an exact ETA for implementation yet. Hope this helps!

We are closing this issue, but please feel free to open the issue again if you any other support.

Are there currently any way of getting the image handler to work with large images? Im getting errors on large files > 7MB + on all other browsers than Chrome.
Is there a workaround that would allow the generated file to be output into S3 and return the url instead?

Still facing the same issue with Image greater than 5MB,
can we get a workaround for this one? or do we need to restrict users to only upload images below certain file size?

Hey @lithiumoxide, the "body size is too long" message is a known issue and is typically thrown when the resulting image exceeds the Lambda payload limit of 6 MB. The upscaling might cause the output image to exceed this limit and throw the message you've been seeing.
We've added a workaround to our feature backlog for this solution that could allow users to output images to an S3 bucket of their choice (i.e. a bucket named 'output-images') which would circumvent the payload limit, but don't have an exact ETA for implementation yet. Hope this helps!

Hey @hayesry any update on this one, thank you!


Support compression

Support compression and add the compress method which user can set the compress flag for a subsequent event emission.

I think nocompress flag also can be an option instead of compress(false).
socket.nocompress.emit('myevent');

Since I think it's fairly rare, a .compress(false) flag should suffice.


fix(components): listbox and radio-group disabled state

This aims at fixing this comment from #815
When they are set to disabled, listbox and radio-group now record the state of their children then set them as disabled.
In #815 listbox uses CSS to disable access to its children.
In current main, radio-group does not keep track of its children's state.
Issues with the current code:

In a disabled listbox, a selected option will still react to hover. This should be addressed by the option component in a separate PR.
The version of the FAST radio-group we inherit from considers disabledChange as private instead of protected in the current codebase (thus the ugly TS workaround).

Note: this doesn't address the radio-group readonly issue.

here's today's mentioned feature. not enough support and won't be of great help here but useful to know about
https://css-tricks.com/custom-state-pseudo-classes-in-chrome/

anyway, as you wrote, this PR tries to go beyond CSS by switching a behavior (disabled) on and off. the cosmetic aspect of that behavior should be left to the child to decide.

talking to myself here, but that's actually not true for a native select. options are not disabled when the select is, but are in practice unreachable.

Just throwing an idea here -
We might be able to extend the appearance mixin disabled selector by it to also apply when a parent is disabled.
That's not a real css feature as host-context hasn't reached maturity.
I did see nice tricks with :has to

Just throwing an idea here - We might be able to extend the appearance mixin disabled selector by it to also apply when a parent is disabled. That's not a real css feature as host-context hasn't reached maturity. I did see nice tricks with :has to select elements by parents. maybe @rachelbt would have references?

yes! I thought about :has as well. my main concern is that css solves the appearance side of the problem, not the functionality. for the radio-group, this means that it could look disabled while still being submitted as part of its parent form.

Just throwing an idea here - We might be able to extend the appearance mixin disabled selector by it to also apply when a parent is disabled. That's not a real css feature as host-context hasn't reached maturity. I did see nice tricks with :has to select elements by parents. maybe @rachelbt would have references?

yes! I thought about :has as well. my main concern is that css solves the appearance side of the problem, not the functionality. for the radio-group, this means that it could look disabled while still being submitted as part of its parent form.
here's a summary of current possible paths at the moment:
setting the disabled state via CSS
pros

consistent with FAST's listbox implementation.
parent-only, children don't have to know/do anything.
keep children state.

cons

limited visually: you can only set a dim veil over children. other solutions require some kind of adherence between the children and the parent (i.e., FAST's options have a dedicated CSS rule acknowledging the parent's disabled state).
what about functionality? a disabled component should not react to user inputs and should be ignored in forms.

setting the disabled state via JS (or attribute)
pros

consistent with FAST's radio-group implementation, although it doesn't keep state as is.
parent-only, children don't have to know/do anything.
appearance and functionality are consistent.

cons

edge-cases (the children list is modified while disabled) to account for when keeping state.
not consistent with native behavior (a disabled select does not set its children options to disabled).

notes

the read-only state for radios shares the same pattern with an additional constraint: the state is only valid when used inside a radio-group. this is the native behavior but we could ignore it.
"the listbox component has no internals related to form association" from FAST's documentation.

https://github.com/Vonage/vivid-3/pull/888#discussion_r1045719265

OK, so the latest commits here go the JS route for you to see what it'd look like. Basically, we keep a record of the children's state when turning the parent (listbox/radio-group) disabled and we restore the recorded state when turning disabled off.
Children updates (add/removal) are monitored and update the records.
It works and doesn't require CSS, but definitely needs more code than the CSS solution. This CSS solution would consist in:

merging @rinaok code in #815
replicating it for radio-group (meaning updating the radios CSS and override the current disabledChanged method)
preventing the radio-group from submitting: this can be achieved by removing its name while disabled, but is it acceptable?

For reference https://github.com/microsoft/fast/issues/6567

Add JIRA ticket VIV-866 - Investigate disable state bug in Fast


Improve the Scaffold.bottomSheet update behavior

Description
Currently, put TextField into Scaffold.bottomSheet may cause the IME show and hide infinite loop, see #71435 and https://github.com/flutter/flutter/issues/71435#issuecomment-736516358 for details.
This change let Scaffold.bottomSheet can be updated without creating a new RO when the new widget has the same key and type.
This patch tries to fix the related issues and waiting for your review and thoughts.
I noticed that #2115 has discussed this behavior, CC @Hixie
Related Issues
Fixes #71435
Fixes #73033
Tests
I added the following tests:
See files.

Yes,I think so. If we don't recreate the RO when just rebuilding scaffold without adding or deleting bootsheet, both of the issues will be fixed.

Yes,I think so. If we don't recreate the RO when just rebuilding scaffold without adding or deleting bootsheet, both of the issues will be fixed.

Yes,I think so. If we don't recreate the RO when just rebuilding scaffold without adding or deleting bootsheet, both of the issues will be fixed.

Awesome! Thanks for explaining!

Yes,I think so. If we don't recreate the RO when just rebuilding scaffold without adding or deleting bootsheet, both of the issues will be fixed.

Awesome! Thanks for explaining!


Use Ctrl-E for hint completion

See #406

Any chance we can get this merged? What is missing?

With #492, you can provide your own conditional binding:
https://github.com/kkawakam/rustyline/blob/master/examples/custom_key_bindings.rs#L45-L51

Fixed in version 8.0.0


Clicking on hardware back button on Android closes the sheet

Hey,
Even though I  have both closeOnDragDown={false} closeOnPressMask={false}, the back button on Android still closes the raw sheet.
Even if I catch the event with BackHandler and return true, it still closes it.
Not sure where to look anymore. Help please :)

Add closeOnPressBack={false}


chore(package): update react packages to v15.6.1

Closes #104
Closes #105
Closes #106

Codecov Report

Merging #107 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #107   +/-   ##
=======================================
  Coverage   91.89%   91.89%
=======================================
  Files           1        1
  Lines          37       37
  Branches        9        9
=======================================
  Hits           34       34
  Misses          3        3

Continue to review full report at Codecov.

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


Errer page

Subject: Errer page
Description:
Every time I access the site or click somewhere an error page appears, it's annoying
Results:
I should have had access to the login page or the requested page
Backend version: develop-7c33e18d
Frontend version:
User Agent: Mozilla/5.0 (Linux; Android 11; SM-A127F) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Mobile Safari/537.36
Page: https://couchers.org/login
User:

not enough info or can't reproduce


Implement liked collection

https://www.w3.org/TR/activitypub/#liked
Collection of everything a given user has liked.

Deprioritizing, Mastodon doesn't actually use or show the liked collection anywhere.


Rename $handler to $next

I think it reads and expresses better the concept.
interface MiddlewareInterface
{
    /**
     * Process an incoming server request and return a response, optionally delegating
     * response creation to a handler.
     *
     * @param ServerRequestInterface $request
     * @param RequestHandlerInterface $next
     *
     * @return ResponseInterface
     */
    public function process(ServerRequestInterface $request, RequestHandlerInterface $next);
}

class AwesomeMiddleware implements MiddlewareInterface
{
    /**
     * {@inheritdoc}
     */
    public function process(ServerRequestInterface $request, RequestHandlerInterface $next)
    {
        $response = $next->handle($request);

        return $response->withHeader('X-Awesome', 'true');
    }
}

What if the $next is not a pointer to another middleware?

In the context of the AwesomeMiddleware class you can never know if it is THE final handler of the request or another middleware, but you can always know that is the NEXT thing to handle the request.

Doesn't that argument cut both ways? You know the $handler is going to generate a response aka "handle the request" so why should it be called $next?

No, because the next may be a middleware, and by the middleware contract it may just process the request.

The type is RequestHandler $handler. Whether or not that handler calls a middleware is completely irrelevant.

So, again, in the context of middleware with the type RequestHandler you know you can call the handle method in the next handler of the request. Calling the variable the same as the type doesn't always make it more clear. In the post by ircmaxell that originate the current changes, it's called frame.
It's a suggestion, to me it reads better, I opened the issue to see if it resonates with more people.
$response = $next->handle($request);

VS
$response = $handler->handle($request);

I opened the issue to see if it resonates with more people.

👍  It does with me.
Using the generic $handler name may have theoretical value but it's unhelpful in practice. And practice trumps theory. For the record I also disagree that it's theoretically better, but maybe I'm wrong on that. But on the "practice" side I'm convinced that $next is the better option.
$next is very important in middlewares, that's how I explain the pattern every single time. With PSR-15 I started to wonder whether I should update my slides or workshop to use $handler instead of $next, but in the end I didn't.
$handler is not helpful, $next makes more sense in real life.

IMHO the issue with $next name is that it may confuse people thinking that it is the next middleware itself, but this is not true. It is a RequestHandler (often a middleware dispatcher) that may or not call the next middleware internally.

Since the FIG repository is the place where this needs to be changed first, can you open a PR there? That would be a better venue for continued discussion. Thanks!


how create ionic app ?: Resolve problem: Cannot find module 'config-chain' (CLI v1.7.11)

first :download and install : node js ; git ; apache ant ; and java .
second:install cordova and ionic with this cmd : npm install -g cordova and after do : npm install -g ionic@alpha
last :ionic start appName.
I had the same problem but I can not find resolved the module 'config- chain '
how i PROCESS I had version 5 node js and I have moved Ionic (2): Ionic @ alpha .but I had to go back on version 4.2.3 node js to create my first application with Ionic .
Je eu le même problème, que j'ai  résolu
comment j'ai resolus j'etait a la version  5 de node js et jai installé ionic 2: Ionic@alpha .mais je suis revenir sur la version 4.2.3 de node  pour créer ma première application avec ionic

Hey there, did this get resolved? If not, could you post the output of ionic info please?

Hello all! As it seems it has been a while since there was any activity on this issue i will be closing it for now. Feel free to comment if you are still running into this issue. Thanks for using Ionic!


Translations in Debug viewlet

VSCode Version: 1.7.2 smoke test
OS Version: Ubuntu 14.04

Steps to Reproduce:

Open code with locale DE, open debug viewlet
"All Exceptions", "Uncaught Exceptions" are not translated
A watch expression that can't be evaluated shows an untranslated: "not available"

The options "All Exception" and "Uncaught Exceptions" are created with the correct translations when a debug extension is used for the first time:

If the locale is changed later, the options are not updated.
@isidorn could you update the options if you notice that the labels don't match any more?
"not available" message: when the debug adapter is running a correct error message is shown (see screenshot above). But when debug session terminates, VS Code shows an untranslated message:

'Not available' was missing a localize call - fixed that.
As for the labels of exception breakpoints I always update them on the ux side once a debug session is started - since these labels are coming from the debug adapter.
So if the locale is changed later the labes should update once a debug session is started.

@isidorn indeed, the exception options turned to English when starting a new debug session with English locale. So this works as designed.


s.blitznote.com port 443: Connection refused

I'm currently getting this error: W: Failed to fetch https://s.blitznote.com/debs/ubuntu/amd64/all/InRelease  Failed to connect to s.blitznote.com port 443: Connection refused.

Thanks — but please send an email in events like this.
The issue tracker is for bugs and ideas.


Add my links to README

Adds Home Assistant my links to the HACS installation page, and the config flow

These are great, thanks for adding


Should be able to select scroll bar to scroll through options

Describe the bug
When using auro-select with a fixed height and a scroll bar is visible, the scroll bar isn't clickable.  It appears that you can click on the menu options below the scroll bar.
To Reproduce
Steps to reproduce the behavior:
The flight search team implemented the work around Geoff suggested for the currency converter.
Scroll down to the bottom of the page and click on the currency converter in the fine print.

Click on flight search
Scroll down to the bottom of the page and click on the currency converter in the fine print.
See error

Expected behavior
A user can click on the scroll bar without closing the bib.
Screenshots

Desktop (please complete the following information):

OS: Windows & Mac appear to both have slightly different experiences

See this issue for background

https://github.com/AlaskaAirlines/auro-select/issues/115

This ticket will be fixed by this, once completed an update and PR will be released to implement the change:

https://github.com/AlaskaAirlines/auro-menu/issues/159


Add make rule and hack/tidy-check.sh to check go mod dependency issues

There is no checker in Antrea to check go.mod and thus some redundant and broken dependencies exist in go.mod and go.sum.
This CL adds a make rule test-tidy which uses the hack/tidy-check.sh to check if the go.mod is tidy. It could be added to CI test to prevent dirty go.mod in future.
Related #18 .

/skip-e2e

/test-e2e

/test-e2e

/test-e2e

/test-e2e

/test-e2e

Thanks Antonin, I have updated accordingly, PTAL.

/test-e2e

It could be added to CI test to prevent dirty go.mod in future.

Looks like the PR have done it, so better to revise the comment?

Sure, updated.

/test-e2e

/skip-e2e


[ibex] Yosys synthesis missing lowrisc_ip

Hi,
Is it planned to support the Yosys design flow in hw/vendor/lowrisc_ibex/syn for the Ibex? If yes, the lowrisc_ip directory is missing in hw/vendor/lowrisc_ibex/vendor. When adding this directory, synthesizing the Ibex works out of the box.
If requested, I can open a PR.
Best,
Pascal

Hah! The problem is that lowrisc_ip is vendored from OpenTitan into Ibex. Then the Ibex RTL is vendored from the Ibex repo into OpenTitan. We drop the lowrisc_ip stuff to avoid vendoring OpenTitan into itself(!). But we're lazy and don't carefully rip out all the supporting code like, it seems, the syn directory.
Can you run the experiments you need from the Ibex repository? That's probably the easiest approach.

Ah, good to know!
Sure, I'll do that.


Request for an event

Please provide the following information

Is this event for college students or professionals?

How many folks do you expect will attend this event? 100-130

When do you want this event? 02.10.2021 and 03.10.2021

Language of the event? English and Telugu

[x] fill this google form.

@himabindu-run can you please share your community name?

Google Developer Students Club GVP Chapter

Received , will be reaching out soon
Thanks


Unknown encoding cl100k_base when building program using pyinstaller

Traceback (most recent call last):   File "voicemain.py", line 16, in <module>   File "<frozen importlib._bootstrap>", line 1027, in _find_and_load   File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked   File "<frozen importlib._bootstrap>", line 688, in _load_unlocked   File "PyInstaller\loader\pyimod02_importers.py", line 385, in exec_module   File "chatsession.py", line 8, in <module>   File "chatsession.py", line 12, in ChatSession   File "tiktoken\registry.py", line 60, in get_encoding ValueError: Unknown encoding cl100k_base [8404] Failed to execute script 'voicemain' due to unhandled exception!
My program works fine when running it from my IDE (PyCharm), though when I try building it with pyinstaller and running the resulting exe file, I get that strange error about the encoding not existing.
Is this an issue with tiktoken?

See the FAQ


HTTP3 + QUIC support

With QUIC support being in most of today's browsers, and tools already excising to enable QUIC within nginx I believe it would be a good idea to add the support to NPM helping users speed up those huge video streams.

It would be nice to be able to use NPM to connect to internet radio servers that use QUIC.

Hope this can be added to NPM. I would imagine if you don't have QUIC Google might rank your site lower copared to a site that does have QUIC. It would also make your site a little fit faster - also leading to a higher ranking.

I totally agree here, this needs to be a top priority.

I was going about the route of using NPM in front of a Docker/container setup only to realize that although the web server I'm running should support QUIC & HTTP/3 unfortunately NPM doesn't. Having NPM in front of any containers/services I start up is very handy but I'd sure like the ability to use QUIC & HTTP/3. Keeping an eye on this.

It's still experimental/beta in Nginx and only available as separate packages/in a separate branch. https://www.nginx.com/blog/binary-packages-for-preview-nginx-quic-http3-implementation/ https://github.com/nginx-quic/nginx-quic
While I lend my support to those asking, I don't think this can/should go anywhere on the NPM side before Nginx merge it into their stable branch.

It's still experimental/beta in Nginx and only available as separate packages/in a separate branch. https://www.nginx.com/blog/binary-packages-for-preview-nginx-quic-http3-implementation/ https://github.com/nginx-quic/nginx-quic
While I lend my support to those asking, I don't think this can/should go anywhere on the NPM side before Nginx merge it into their stable branch.

It's already merged, right?

Yeah.  Time permitting, I think this is ready for @jc21 to action.
https://nginx.org/en/docs/quic.html

Any update on this?

Would be amazing to have it

would be awesome ... no news ?

I hope we will see this added in the near future, I am already using NGINX with HTTP/3 on some of my servers and it can improve things significantly with larger sites!
Please, this needs to be implemented. As the comment above said, it is already in mainline version of NGINX.

so please, me too....
I am waiting for it.....

Also all big Websites now support http/3 (Google, Microsoft, Cloudflare, Amazon, Meta). So I think it is getting time for a implementation.

Any updates?

Any updates?

Any updates?

OpenResty <IP_ADDRESS> added support for HTTP/3.

Hello, I have tried to add HTP3 support for nginx-proxy-manager
If you are interested in this, you can give it a try
docker: https://hub.docker.com/repository/docker/lateautumn233/nginx-proxy-manager/
Source code: https://github.com/lateautumn233/nginx-proxy-manager

Hello, I have tried to add HTP3 support for nginx-proxy-manager
If you are interested in this, you can give it a try
docker: https://hub.docker.com/repository/docker/lateautumn233/nginx-proxy-manager/ Source code: https://github.com/lateautumn233/nginx-proxy-manager

You did what they couldn't do. Thank you

Should this be as simple as replacing docker image in the compose?

Yes
But currently only the amd64 architecture is available
lateautumn233
@.***
---Original---
From: @.>
Date: Sat, Jan 27, 2024 01:21 AM
To: @.>;
Cc<EMAIL_ADDRESS>Subject: Re: [NginxProxyManager/nginx-proxy-manager] HTTP3 + QUIC support(Issue #1550)
Should this be as simple as replacing docker image in the compose?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

Yes But currently only the amd64 architecture is available lateautumn233 @.***
…
---Original--- From: @.> Date: Sat, Jan 27, 2024 01:21 AM To<EMAIL_ADDRESS>Cc: _<EMAIL_ADDRESS>Subject: Re: [NginxProxyManager/nginx-proxy-manager] HTTP3 + QUIC support(Issue #1550) Should this be as simple as replacing docker image in the compose? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID<EMAIL_ADDRESS>
I did it.
It seems H3 is being enabled:
npm-1  | [1/26/2024] [5:28:15 PM] [Migrate  ] › ℹ  info      Current database version: none
npm-1  | [1/26/2024] [5:28:15 PM] [Migrate  ] › ℹ  info      [http3_support] Migrating Up...
npm-1  | [1/26/2024] [5:28:15 PM] [Migrate  ] › ℹ  info      [http3_support] proxy_host Table altered
npm-1  | [1/26/2024] [5:28:15 PM] [Migrate  ] › ℹ  info      [http3_support] redirection_host Table altered
npm-1  | [1/26/2024] [5:28:15 PM] [Migrate  ] › ℹ  info      [http3_support] dead_host Table altered

But, in chrome, only H2 is being used:

I'll debug further later tonight.

Disregard, i had to refresh the NPM ui to get the new option showing :)

Hello, I have tried to add HTP3 support for nginx-proxy-manager
If you are interested in this, you can give it a try
docker: https://hub.docker.com/repository/docker/lateautumn233/nginx-proxy-manager/ Source code: https://github.com/lateautumn233/nginx-proxy-manager

Other architectures
docker push lateautumn233/nginx-proxy-manager:test
I need more testing, and if there are no issues, I will try to contribute upstream

Other architectures docker pull lateautumn233/nginx-proxy-manager:test
I need more testing, and if there are no issues, I will try to contribute upstream

Working a-OK on arm64 (Radxa Rock 5 model B), for me. Page loads confirm http/3 and it's working perfectly. I can finally use NPM again!

FYI, if you haven't seen recently that there is at least 1 open CVE for HTTP/3 + QUIC in Nginx. It was actually the subject of one of the core devs leaving the project and forking Nginx. I'd be careful about pushing this forward as the support is still marked experimental.

Here are the details for reference. https://my.f5.com/manage/s/article/K000138444

It does look like a fixed version was released, however there is a part of me that is concerned that the HTTP/3 + QUIC module is considered experimental still.

FYI, if you haven't seen recently that there is at least 1 open CVE for HTTP/3 + QUIC in Nginx. It was actually the subject of one of the core devs leaving the project and forking Nginx. I'd be careful about pushing this forward as the support is still marked experimental.

Perhaps we should switch to free nginx?

Portainer didn't show that utp port 443 or 80 is open ?

Hi @lateautumn233, I tried your version of NPM + quic enabled but somehow after inspecting the network tab it seems like the protocol doesn't use http3 but instead it uses http/1.1 or http2 (if enabled). I did expose port 443/udp from the docker compose already.
Another thing that I've tried is to add reuseport at the listen directive for quic and it does work if I have only one proxy host. If I add a new proxy host, it will not work with reuseport. Any advise you can give on my situation?

Hi @lateautumn233, I tried your version of NPM + quic enabled but somehow after inspecting the network tab it seems like the protocol doesn't use http3 but instead it uses http/1.1 or http2 (if enabled). I did expose port 443/udp from the docker compose already.
Another thing that I've tried is to add reuseport at the listen directive for quic and it does work if I have only one proxy host. If I add a new proxy host, it will not work with reuseport. Any advise you can give on my situation?

Maybe it's related to this
https://stackoverflow.com/questions/76348128/enabling-quic-http-3-on-multiple-domains-with-nginx-1-25

update pls ?

On my side I siwtched to caddy. Conf file is finally easier. Http3 out of the box

http3 is actually very important, I don't understand why it isn't given priority.

Any update on this? @jc21

hi lateautumn233, i would like to ask if you can update your image on docker-hub. this project added a acme-plugin recently which i use and which does not allow me to use your version.
hopefully that http3-change is gonna be integrated here soon. thanks a lot for your work!


DeepCopy is missing InferSecuritySchemes

I spent some time debugging trying to figure out why calling InferSecuritySchemes on SwaggerGenOptions doesn't seem to work and it look like DeepCopy isn't setting InferSecuritySchemes.
https://github.com/domaindrivendev/Swashbuckle.AspNetCore/blob/4a28652059c93dc95146d962df645bff8953e39f/src/Swashbuckle.As
pNetCore.SwaggerGen/DependencyInjection/ConfigureSwaggerGeneratorOptions.cs#L55-L71
This explains why:
This does not work
builder.Services.AddSwaggerGen(c => c.InferSecuritySchemes());

This works
builder.Services.Configure<SwaggerGeneratorOptions>(opts =>
{
    opts.InferSecuritySchemes = true;
});

cc @captainsafia

Linking the right comment https://github.com/domaindrivendev/Swashbuckle.AspNetCore/commit/e98e4aa651ef244ad123f82c0bd05a3c6d70c3f0
Also @domaindrivendev would be possible to put this in a patch release?

Hi everyone, seems we have the same issue for SecuritySchemesSelector.


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 1230 ms

Resolved: Bofrost.at performance has improved in 644f0e1.


Search fields need labels for accessibility

The 2 input fields with search-query and user-list-filter classes do not have labels which can be found by screen readers or other assistive technology.  It might not be desirable to add a visible label which would be redundant with the placeholder text, but the W3C does offer some alternatives for providing hidden labels which can be used in cases like this.

@zulipbot label "accessibility"

@zulipbot claim


After upgrading to 1.10, docker bridge host ip cannot be access via vpn

before the upgrading, I have correctly configured openvpn server that will route <IP_ADDRESS>, but after upgrading, first the bridge ip changed to <IP_ADDRESS>,and after that route, I cannot still ping <IP_ADDRESS> from other host that in the same vpn network, but that host will be able to ping others, why?

If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
For more information about reporting issues, see CONTRIBUTING.md.
You don't have to include this information if this is a feature request
(This is an automated, informational response)

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

seems mis-configured


Okta Preview migration cleanup

Some steps remain as part of this effort: https://github.com/CDCgov/prime-reportstream/issues/3891
We were waiting due to the possibility of yet another migration to a separate ReportStream instance, but this is off the table for now.

[ ] Audit/remove/lower access to Okta production to a smaller set of folks.
[ ] Remove Okta Prime (test) app from production.
[ ] Any approve urls that may have snuck into Okta Prime app
[ ] Verify Trusted Origin in app
[ ] Remove unused Okta Trusted Origins [On Okta site: admin/access/api/trusted_origins]
[ ] Verify Security -> API list [On Okta site: admin/oauth2/as]
[ ] Remove our own members from groups like all_in-one
[ ] CSP header remove https://hhs-prime.okta.com

Keep in "new items" until decision is made on whether reportstream moves to new okta domain

Unclear if this still needs to be done, but much of it seems to have been done. Would love to prioritize looking at this to gauge the current situation

This was completed but not logged. Closing!


Spoofing not working?

Idk why is it auto translated, but the self check tab shows up that spoofing isnt working and signature also isnt. In revanced youtube I get buffering issues, the video loads around 30 seconds and stops.

That's not an issue, for support move to our links at https://revanced.app

That's not an issue, for support move to our links at https://revanced.app

I asked in discord nobody reply, in the announcement about GmsCore says to open an issue in github

Like I said this is not an issue so move to one of the links


Regenerate literate/literate.html

The literate/literate.html wasn't reflecting the state of literate/literate.literate

Thank you!


release artifacts for release v0.0.3

Release artifacts for Dynamodb Controller v0.0.3.
Release includes:

Support for Table, GlobalTable  and Backup resources
Improved logging with runtime v0.3.0
Documentation for CRDs and CR fields
Metrics service to helm charts
Fixed some issues where Table and Backup statuses weren't correctly
synced with the correct status.
--watch-namespace and --resource-tags flags/parameters for helm
charts

By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license.

/lgtm


remove project.sparseCheckoutDir

Signed-off-by: Stephanie<EMAIL_ADDRESS>What does this PR do?
This PR removes project.sparseCheckoutDir as has no current usage, and no good use case for it.
What issues does this PR fix or reference?
Fixes #385
Is your PR tested? Consider putting some instruction how to test your changes
updated tests
Docs PR

@amisevsk I have pushed a new commit with suggested changes, can you help review again? Thanks


FCL: Check if user's wallet connection is still valid when creating an authorization request

Problem
Currently, FCL remembers when a user logs into a wallet and persists the connection when user comes back to the dApp page. This is great for UX.
When dApp calls the signing function from fcl.currentUser().authorization, FCL creates a POST request to initiate the authorization process.
However, the wallet connection might not be valid anymore at this time, if user comes back to the dApp long after they first logged in.
Currently there is no way for the wallet service to tell FCL that the connection is not valid anymore.
Expected
There may be multiple ways to improve the process.

In the signature authorization request, define a response for the wallet service to tell FCL that the connection has already expired.
Before creating the authorization request, define an API to check if the wallet connection is still valid (maybe from some information that /hook API provided).
In /hook API, the wallet provider tells FCL how long the connection will be valid for.

I'd prefer 2 or 3. They will also work for other future requests to the wallet service other than the signature request.

@orodio
I thought there's only a exp information in postMessage or redirect callback, but not in the response of  /hook?
from https://github.com/onflow/flow-js-sdk/blob/master/packages/fcl/src/wallet-provider-spec/custodial.md#authentication-challenge
Or is it just not documented yet?
I thought the exp in postMessage or redirect callback meant when the "handshake code" will expire, rather when the "wallet connection" will expire. Because in a lot of OAuth handshakes the code is only valid for a very short period of time (like 5 minutes) but once you have exchanged it for the complete connection information it can be used for a longer period of time (like 1 week).

I see, I see.
In the draft spec for the FCL Wallets, i've added an expires field to all services, this would cover Authentication and Authorization, I think this should cover what you are saying. Will need to figure out what that means and how that is handled in FCL, but this should at least give us the ability to respect it in the future.
What are you thinking FCL would do once the ability to Authorize in that particular way has expired?

I think once the connection expires, FCL can either

Log the user out (basically what fcl.unauthenticate() does)
Or better, keeps the user information but add an additional flag to mark the user as inactive. In this case, DApps can still get the address but once there's a signature request, FCL initiates the authn process before the authz process

@boczeratul I like the idea of doing it silently, treating it as if we know roughly who they are, but not how to do things on their behalf.
@boczeratul what do you think about this:

Treat Authn expiry as fcl.unauthenticate()
Treat Authz expiry as fcl.unauthenticate() right before a point that requires an authentication?

@orodio the second solution looks better to me

Looks good to me. So normally wallet providers can set a longer authn expiry like a week, and a shorter authz expiry like a day

@boczeratul I believe we are correctly respecting the expire value you are sending us, which I think solves this issue. Going to close this, if you find any issues with it let us know and I can re-open.