@rollup/plugin-inject incompatible despite being in the list

Describe the bug
The plugin @rollup/plugin-inject is in the list of compatible plugins linked in the docs but it raises warnings.
Using the vanilla JS template, the warnings are:
19:04:27 [vite] warning: rollup-plugin-inject: failed to parse /home/projects/vite-rollup-plugin-inject-mre-z1z9rb/style.css. Consider restricting the plugin to particular files via options.include
  Plugin: inject
  File: /home/projects/vite-rollup-plugin-inject-mre-z1z9rb/style.css
Sourcemap for "/home/projects/vite-rollup-plugin-inject-mre-z1z9rb/node_modules/vite/dist/client/client.mjs" points to missing source files
Sourcemap for "/home/projects/vite-rollup-plugin-inject-mre-z1z9rb/node_modules/vite/dist/client/env.mjs" points to missing source files

If the plugin config is set to enforce: 'post', then the sourcemap warnings remain:
Sourcemap for "/home/projects/vite-rollup-plugin-inject-mre-z1z9rb/node_modules/vite/dist/client/client.mjs" points to missing source files
Sourcemap for "/home/projects/vite-rollup-plugin-inject-mre-z1z9rb/node_modules/vite/dist/client/env.mjs" points to missing source files

Note: The warning seems to disappear sometimes after editing main.js in the provided stackblitz project, so try to refresh the page after making changes.
Reproduction
https://stackblitz.com/edit/vite-rollup-plugin-inject-mre-z1z9rb?file=main.js
Steps to reproduce
npm install && npm run dev
System Info
See stackblitz.

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

You'd need enforce: 'post' or pass the include: '**/*.js' option to work. You could send a PR to https://github.com/patak-dev/vite-rollup-plugins to update it. The sourcemap warning could be something we can fix on our side though, but it should be harmless in practice and doesn't make the plugin incompatible.


NOT WORKING SOLVED ISSUE : Error loading the dashboard strategy

Discussed in https://github.com/AalianKhan/mushroom-strategy/discussions/120

Originally posted by insol-do January 25, 2024
After trying to make the fix from the resolved issue, it it still not working.
Followed below...
https://github.com/AalianKhan/mushroom-strategy/discussions/90

Duplicate of #120


complete file handling for resources

This PR aims to complete the file handling for resources by rendering and handling them with vuejs. As long as no other information is provided it should be handled as work-in-progress.
These known issues are still to be fixed:

[X] csrf_token missing on upload of new resource
[X] rendering of existing resources with vuejs
[ ] if no name is present, the resource name can not be edited

These features are already implemented:

[X] render resources with vuejs
[X] make resource removable
[X] make resource name editable

These known issues are still to be fixed:

[ ] if no name is present, the resource name can not be edited

To handle this, i´m thinking about validating the form input on upload such that every resource must have a name. This is not fixing the mentioned issue completely, as we then also have to make sure that the name of the resource can not deleted by editing it afterwards.
@jnsdrtlf Do you think we should implement the input validation or add functionality to edit "empty" resource namesas an alternative?

Resource names should probably not be empty. Requiring names sounds beneficial. The resource Model already states nullable=False:
https://github.com/desklab/doku/blob/ee6e779260905af6afe3186ebc23cd67c3efca61/doku/models/resource.py#L17

Simply adding the required attribute to the ´´ element should do the trick
<input type="text" name="name" required>

This check should also be implemented for the POST request in flask.

Besides the POST and PUT confusion this looks good to me. Regarding POST and PUT, have you checked the API requests in JavaScript?

I assume the API requests in JavaScript are correct as they use put in updateResource and post in createResource.
https://github.com/desklab/doku/blob/bd7d7e7c4b67656a6312e27c00e16ada1467bf1a/doku/static/src/api/resource.js#L6-L11
I fixed the confusion in doku/blueprints/api/v1/resource.py  in 0acfef9715a4f76d85c4922bc0fd8060e09888dd.


[Tabular][HPO] fixes to HPO performance charts

Description of changes:
Improvements to HPO perfomance metrics charts

now actual metric is displayed instead of generic validation_performance
metric with 'less is better' are now displayed correctly without inverted -1 multiplier

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Job PR-863-2 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-863/2/index.html

Job PR-863-2 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-863/2/index.html


Compatibility issue with Django 3.0 due to django.utils.six

Django 3.0 scheduled for December removed Python 2 compatibility APIs used by django-material (django.utils.six).
See https://docs.djangoproject.com/en/dev/releases/3.0/#removed-private-python-2-compatibility-apis

Thank you for noticing!
New django-material release would be soon


ValueError: shape mismatch in ocropus-gpageseg

When I run ocropus-gpageseg on the following image:

I get a ValueError which prevents any lines from being extracted:
$ ocropus-gpageseg -n --minscale 10 --maxcolseps 0 book-703662b.crop/0001.bin.png

########## /usr/local/bin/ocropus-gpageseg -n --minscale 10 --maxcolsep

book-703662b.crop/0001.bin.png
scale 13.8564064606
computing segmentation
computing column separators
computing lines
propagating labels
spreading labels
number of lines 4
finding reading order
writing lines
1: (slice(3L, 32L, None), slice(3L, 607L, None))
Traceback (most recent call last):
  File "/usr/local/bin/ocropus-gpageseg", line 435, in safe_process1
    process1(job)
  File "/usr/local/bin/ocropus-gpageseg", line 408, in process1
    binline = psegutils.extract_masked(1-cleaned,l,pad=args.pad,expand=args.expand)
  File "/usr/local/lib/python2.7/site-packages/ocrolib/toplevel.py", line 213, in argument_checks
    result = f(*args,**kw)
  File "/usr/local/lib/python2.7/site-packages/ocrolib/psegutils.py", line 114, in extract_masked
    line = where(mask,line,amax(line))
ValueError: shape mismatch: objects cannot be broadcast to a single shape

I believe ocropus-gpageseg isn't supposed to be run on the .bin.png file, but on the original .png file; it will look for the .bin.png file on its own.
(It should still work on pure binary PNG images anyway, so I'll look at that. Or maybe you could see whether you can come up with a patch.)

The README indicates that it should be:
# perform binarization
./ocropus-nlbin tests/ersch.png -o book

# perform page layout analysis
./ocropus-gpageseg 'book/????.bin.png'

Does it need to be updated? I'll see if I can figure out what's going on, too.

Did you generate the .bin.png files in some other way than with ocropus-nlbin?
PNG files come in two varieties: binary and full color; both can contain binary images, however. They turn into rank 2 or rank 3 arrays inside Python, and some image processing operations only work on one or the other, some work on both.

ocropus-gpageseg works on binarized images, that is on .bin.png. You may need to look how your binarized images were generated. Run ocropus-nlbin to confirm for few images.

That image is generated by ocropus-nlbin. Here's the original:

and my sequence of commands:
$ ocropus-nlbin -n 703662b.crop.png -o /tmp/book
# 703662b.crop.png
=== 703662b.crop.png 1
flattening
/usr/local/lib/python2.7/site-packages/scipy/ndimage/interpolation.py:532: UserWarning: From scipy 0.13.0, the output shape of zoom() is calculated with round() instead of int() - for these inputs the size of the returned array has changed.
  "the returned array has changed.", UserWarning)
estimating skew angle
estimating thresholds
rescaling
703662b.crop.png lo-hi (0.60 0.95) angle  0.0
writing

$ ocropus-gpageseg -n --minscale 10 --maxcolseps 0 /tmp/book/0001.bin.png

########## /usr/local/bin/ocropus-gpageseg -n --minscale 10 --maxcolsep

/tmp/book/0001.bin.png
scale 13.8564064606
computing segmentation
computing column separators
computing lines
propagating labels
spreading labels
number of lines 4
finding reading order
writing lines
1: (slice(3L, 32L, None), slice(3L, 607L, None))
Traceback (most recent call last):
  File "/usr/local/bin/ocropus-gpageseg", line 435, in safe_process1
    process1(job)
  File "/usr/local/bin/ocropus-gpageseg", line 408, in process1
    binline = psegutils.extract_masked(1-cleaned,l,pad=args.pad,expand=args.expand)
  File "/usr/local/lib/python2.7/site-packages/ocrolib/toplevel.py", line 213, in argument_checks
    result = f(*args,**kw)
  File "/usr/local/lib/python2.7/site-packages/ocrolib/psegutils.py", line 114, in extract_masked
    line = where(mask,line,amax(line))
ValueError: shape mismatch: objects cannot be broadcast to a single shape

I believe the issue is that the detected lines are too close to the edge of the image. Adding ~10px of padding to all sides of the binarized image makes the error go away.


the command is invalid

after running "docker run --rm -it -p 8000:80 -p 8001:443 -e ASPNETCORE_URLS="https://+;http://+" -e ASPNETCORE_HTTPS_PORT=8001 -e ASPNETCORE_Kestrel__Certificates__Default__Password="password" -e ASPNETCORE_Kestrel__Certificates__Default__Path=\https\aspnetapp.pfx -v %USERPROFILE%.aspnet\https:C:\https\ mcr.microsoft.com/dotnet/core/samples:aspnetapp"
I get
C:\Program Files\Docker\Docker\resources\bin\docker.exe: Error response from daemon: %!U(string=is not a valid Windows path)SERPROFILE%!(MISSING).aspnet\https.
See 'C:\Program Files\Docker\Docker\resources\bin\docker.exe run --help'.
the guide is either wrong or incomplete
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 3e087007-7838-e0f9-d713-22182a5d9704
Version Independent ID: 2f32c7c3-8667-0e88-495b-c0c888572964
Content: Hosting ASP.NET Core Images with Docker over HTTPS
Content Source: aspnetcore/security/docker-https.md
Product: aspnet-core
Technology: aspnetcore-security
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

That's a good error message, look at your path, it's not valid

sorry, the editor here seems to be cutting the slash. I literally try the command from the article

and the "%USERPROFILE%.aspnet\https" is a valid path on my machine.

sorry, the editor here seems to be cutting the slash. I literally try the command from the article

and the "%USERPROFILE%.aspnet\https" is a valid path on my machine.

I was getting this and found out that it doesn't work in powershell because %USERPROFILE% isn't resolved in powershell you have to use $env:USERPROFILE. The command in the docs does work for cmd prompt though. @koshdim


request_too_old? but no check for request_time_invalid?

An API client of ours was implementing an HTTP client for our web service and in helping them get it right they finally succeeded in correctly constructing the signature, but the HTTP_DATE was a day in the future and the request authenticated successfully.
This raised the question of whether or not a more thorough invalid date check is needed.
Should the authentic? method check that a request is both not too old and not too new? Perhaps neither more than 15 minutes in the past and future?

Thanks for brining this up! Yes, this should probably be addressed and #119 has already started on it.


[Init Pois-2] errors again

I have that issue again

chain looks good

cess bucket stat looks good too

do I need to do something to fix it? Last time I created new wallet to fix it. But I think that's not a good option.

now I have that issue on 3 of my nodes

I created new wallet, edited config with seed phrase of that new wallet, now node works good. Hope that bug will be fixed


Different permissions for different number's of shops?

in the spigot webiste on the page about this plugin, it says how to set the default number of shops a person can make but it mentions that they can make more if they have permissions to do so.
How can i set these permissions?  I use the PEX plugin for permissions but i don't see any nodes for shopchest number of shops...
Thanks for the help!  This is a wonderful plugin and my users love it!

It's shopchest.limit.X where X stands for the limit you want to give the player.

Thanks!


[Proposal] Add Code of Conduct

Proposal
Please add link on the README.md to the Code of Conduct which applies to crystal repository and all of its subprojects' repositories (i.e. crystal-lang author).
Examples

Rails

Golang

Why would we need one? I'm closer to NCoC in this regard.

Ummm...
https://github.com/crystal-lang/crystal/blob/master/CODE_OF_CONDUCT.md

IME a lot of people see a CoC as the universal solution for equality, but:

It's only as good as it's enforced. All a CoC ultimately ends up being is a moderator's guidebook.
People have a tendency to go a little crazy with CoC invocations. It has a tendency to make them cry foul at the slightest offense, followed by a heated debate about what exactly the CoC enforces.
Related to the above: it's filled with fluffy words, but it's also very vague. The discretion is ultimately the moderators, which leads back to the first point.
Ultimately, in my experience, it does nothing.  If someone wants to be racist, they'll still be racist. A vague, abstract document is hardly going to deter them any more than moderators already would.

Well, actually there is one already. I had to look for it because no-one used it as an "argument" even in the hottest of arguments I remember. Maybe it's because there's still very lil' politicking goin' on in here... and personally, I'd like this to continue, whether there is a CoC or not.


updating dev

please make sure the package json is proper while merging since we are doing from main to dev in this rare case


Update the Train the Trainer Verbiage

Marketing came back to us this week and requested that we make minor changes specifically around the "Train-the-Trainer" phrase in our AI Tour materials. Please complete the following tasks to ensure compliance:

[ ]  Change "train-the-trainer" to "session-delivery-resources" in the folder structure
[ ] Add boiler plate text (see below) to the top of the "session-delivery-resources" readme
[ ] Change any in-text mentions of "train the trainer" to some version of "deliver this session."

Once all three items have been completed, please mark this issue as complete.
"session-delivery-resources" boiler plate markdown:
The following resources are intended for a presenter to learn and deliver the session.

@softchris @gloveboxes can you please have a look at this and fix the missing items?


Dep Upgrades

This commit represents the current production version of OpenFarm (already deployed).

Coverage remained the same at 96.09% when pulling de1f7294ed73fc8e7183fb5b3f3d8e22efc1c01b on RickCarlino:master into 4acd46061617b2c7f7e222be5c6eadf95f00a8ab on openfarmcc:master.


GEP: TLS ALPN Routing

What would you like to be added:
A way to configure routing decisions based on the application protocols present in the TLS client hello of a TLS connection.
The TLSRoute is a good candidate for supporting this as it is a similar feature to SNI routing which is already handled by TLSRoute. Both SNI and ALPN are present in the TLS client hello and allow for TLS passthrough.
The initial discussion on this subject is here.
Why this is needed:
This would allow service owners to route to different backends behind a single domain based on the protocol the client supports.
For example if you have http/2 and mqtt clients connecting to example.com:443 you could use the application protocols in the TLS client hello to route these clients to different backends that are able to handle the respective protocol.

Sounds like this would be reasonable to add. The next logical step would appear to be more GEP work so we can build consensus on how this would work:
/triage accepted
/kind gep
However this doesn't appear to be something we must have for GA, which is our current main focus so we consider it a low priority until GA is complete:
/priority backlog

The discussion around adding support for routing decisions based on the application protocols present in the TLS client hello of a TLS connection is ongoing. The proposal suggests extending the TLSRoute to handle this feature as it is similar to SNI routing, which is already supported.
The addition would allow service owners to route to different backends behind a single domain based on the protocol the client supports. For example, if you have http/2 and mqtt clients connecting to example.com:443, you could use the application protocols in the TLS client hello to route these clients to different backends that can handle the respective protocol.
The initial discussion on this subject is available in Issue #1683, and a more detailed GEP (Gateway Enhancement Proposal) is available in Issue #1958.
Although the proposal seems reasonable, the main focus for the Kubernetes community is currently on Gateway API reaching GA (General Availability). Therefore, the priority of this feature is considered low until GA is complete.

@ibilalkayy As an external contributor I have time to work on the GEP and implementation of this feature but understandably this still requires time from maintainers to review and give feedback. Should I expect feedback on #1974 time permitting, or will any attention on this be held off until after GA?

You can expect some feedback in the meantime, it's just a matter of all of us who volunteer on this project having limited bandwidth between now a GA, and GA related things will get the highest priority. To help get attention, smaller iterations introducing only bite-sized chunks of a proposal at a time (e.g. just providing a tldr and some goals) can be helpful which looks like the approach you've taken here. I'll make some time personally to look it over soon thank you for taking the time to submit it! :vulcan_salute:

Just as an additional use case for this, ALPN support for gateway listeners or tlsroutes would be really nice for serving north/south traffic for postgres workloads.
Postgres (at least libpq) 17 is using a custom string for ALPN called "postgresql".
So Gateways with tls listeners + tlsroutes trying TLS Mode as Terminate should be able to respond for ALPN requests for this custom query. So this flexibility comes in handy in this case (tls termination for upstream workloads running custom ALPN protocols).


Broken link re: dioxus cli plugins

Specific Demand
Found a broken link in the cli readme for further docs regarding plugins [Dioxus CLI Document (https://dioxuslabs.com/cli/configure.html). Was hoping to create a plugin using the standalone tailwind cli that ties into dioxus' hot realod, I often forget to start the cli in watch mode while running the dev server, which can get a bit annoying.
Implement Suggestion
Would be grateful for any more info about plugins, happy to help get any outdated docs back up to speed in the process

The docs now live at https://github.com/DioxusLabs/dioxus/tree/master/packages/cli/docs/src/plugin, soon they will be moving to the main dioxus website (https://github.com/DioxusLabs/docsite/pull/67).
The plugin system was reworked in https://github.com/DioxusLabs/docsite/pull/67, but it needs to be moved over to the new location in the main Dioxus repo. I think as part of that PR a tailwind plugin was implemented

Awesome, thank you!

The plugin docs are now removed until the plugin system is finished


More publish overloads for binary payloads and SubscribeAllAsync method

This fixes the issue when byte[], Memory<byte> and ReadOnlyMemory<byte> payloads are passed to publish methods.
Also adds the SubscribeAllAsync() method for convenient enumeration for subscribers.

Just complicating the API too much for what it offers. They can be implemented as extension methods later by the library or end devs.


Cached bad response: ValueError: Expected dict_keys(['answer']) but got dict_keys([])

If running an evaluation but the model messes up the output formatting, litellm will still cache it because the response was valid, just not correct schema.
If this happens enough to cancel the evaluation, all of your good requests are trapped b/c the parsed examples are still there.
I think I should probably be able to specify retries for bad formatting.
Currently I don't increase the number of errors I allow, but thats another solution. Seems much more prevalent for stupider models or models without few shot examples yet, but even with 3 good bootstrapped examples 3.2 1B wasnt able to get through the evaluation set.
I could see the current caching behavior technically being desired but it isnt fun from a user experience perspective
cc @okhat @Shangyint

I can work on this once we agree on a direction

I've had similar experience behavior with caching for other web search APIs where bad (but valid) http response got cached too. Is there a way to wrap the caching function with the schema parsing code, so that an error could be thrown or retried internally to prevent caching for the failing cases.

@isaacbmiller I'm unsure I understand the issue. Just make sure the retry has a different temperature or a slightly different prompt? Why would you retry the identical prompt request?

For any temperature > 0, there is some chance that if a prompt fails once that does not mean that it will fail again the second time.
For evaluation its fine to be like - yep the model cant do it, mark as no, move on.
For any less error tolerant situation(still with temp > 0), and I would want to retry until I get a correct parse.
1B only errored for probably 20/500 examples, so clearly it is smart enough to maybe get it with another retry.

Yes, retry with temperature + 0.0001 * retry_idx

or pass cache=False

self.module(question=..., config(temperature=..., cache=...))

Are you just looking for BootstrapRS's argument that's called max_rounds


Add two new function to the $printingFunctions array.

WP 4.3 introduced _deprecated_constructor().
WP 4.6 will introduce _deprecated_hook().

It looks like you added tests for _deprecate_hook() but not _deprecated_constructor(). Was that intentional? I'm not sure that it is necessary for us to test every single function, but I thought that I would point it out anyway.

Was that intentional?

Someone is paying attention :sunglasses:
Yes, that was intentional, I didn't really see the need as 99% of the time the function will be called like this:
_deprecated_constructor( __CLASS__, '4.5.0' );

Ref: https://developer.wordpress.org/reference/functions/_deprecated_constructor/
Still easy enough to add one if you like.

Still easy enough to add one if you like.

Nope, that's fine. :shipit:


Lots of unconnected containers just get put in one long line

It would be nicer if they weren't: it makes the view very width-heavy

I think the new layout rules basically solves this?

Not really, unconnected containers still get put in a single line.
On Fri, Sep 18, 2015 at 5:49 PM, Peter Bourgon<EMAIL_ADDRESS>wrote:

I think the new layout rules basically solves this?
—
Reply to this email directly or view it on GitHub
https://github.com/weaveworks/scope/issues/375#issuecomment-141406836.


java.io.IOException: Content-Length (2472) and stream length (9805) disagree

java.io.IOException: Content-Length (2472) and stream length (9805) disagree
at okhttp3.ResponseBody.bytes(ResponseBody.kt:330)

https://github.com/google/cronet-transport-for-okhttp/blob/eba6b03e2e5a7b659023047122a0a44c835f6bc7/java/com/google/net/cronet/okhttptransport/ResponseConverter.java#L117-L120
when server use compression methods like Gzip,Brotli and ect.The returned Content-Length is not equal to the actual stream length(Cronet has decompressed the compressed data)
https://github.com/google/cronet-transport-for-okhttp/blob/eba6b03e2e5a7b659023047122a0a44c835f6bc7/java/com/google/net/cronet/okhttptransport/OkHttpBridgeRequestCallback.java#L252-L256

Thank you for the report! I'll take a look.

This has been addressed in 64c95224ff839291df0a6f30655d0e4a4b515d14


No Relations imported!

Hello, first thanks for that plugin.
I have one to many relations in my collection, for that field also data is not importing, how can I do that?
For export there is no problem, all relations are exported, but while importing the exported file all relations discarded.
Thanks in advance.
Please let me know if you need any further details.

I also have the same question, but structure should the data have in csv file for relations. Something like
[id1, id2] ?

In the exported csv file that I'm trying to import, the relation exists in a column in the following format
[{"id":1, "xx":"xx",....},{"id":2,"yy":"yy",....}].
I can also see this data in the analyzed table before importing, but no relations are imported into collections.

I also tried various fromats but non of them are working, also with _id . For one-one relation works perfect with the id as an string. But with one-many relation i cannot find the way to make it works yet

@satiye i solved it! you need to add the property "relationType": "MANY_RELATIONS" to the strapi model settings.json


EPG doesn't appear in Windows application

Describe the bug
Added m3u by link or via file import. Pasted xml.gz EPG URL from m3u file, "Fetching EPG" message appears and no EPG appears even after 30 minutes of waiting. No EPG related errors in devtools...
epg.xml.gz is 35 MB size. Maybe it is too big? You can download it from here to check it out.
Desktop (please complete the following information):

Windows exe application
OS: Windows 10

Any update on this?


Improve each template literal infer

Summary
Small improvement to continue the work done mainly on this PR to improve type safety/inference on the Template literals syntax of .each.
Currently, when using the template literals syntax with .each, the args type is inferred if you don't provide the generic type argument.
If all inputs (variables inside the template literal) are of the same type, the args will be inferred to the same type.
import {test} from '@jest/globals';
test.each`
  a    | b    | expected
  ${1} | ${2} | ${3}
  ${3} | ${4} | ${7}
  ${5} | ${6} | ${11}
`('template literal example same type', ({a, b, expected}) => {
  // all arguments are of type `number` because all inputs (a, b, expected) are of type `number`
});

But if the inputs are of different types, the args will be inferred to type unknown.
import {test} from '@jest/globals';
test.each`
  a    | b    | expected
  ${1} | ${2} | ${'three'}
  ${3} | ${4} | ${'seven'}
  ${5} | ${6} | ${'eleven'}
`('template literal example different types', ({a, b, expected}) => {
  // Without the generic argument explicitly provided, args types would default to `unknown`
});

This PR aims to improve the type inference for this second case. Now, args will be inferred to a type representing the union of all input types (automatically inferred from the input types inside the template literal).
import {test} from '@jest/globals';
test.each`
  a    | b    | expected
  ${1} | ${2} | ${'three'}
  ${3} | ${4} | ${'seven'}
  ${5} | ${6} | ${'eleven'}
`('template literal example different types', ({a, b, expected}) => {
  //All arguments are of type `number | string` because some inputs (a, b) are of type `number` and some others (expected) are of type `string`
});

This provides more type safety IMO because otherwise, with type unknown you can cast to non-permitted types without any warning. It will also encourage the use of an explicitly provided generic which is the safest solution regarding types currently.
Test plan
The tests already existed but were expecting unknown. I updated them.

https://github.com/jestjs/jest/releases/tag/v30.0.0-alpha.4


iPad Sidecar support

I imagine this is probably impossible for various "Apple reasons", but if it was possible, the ability to change the levels on an iPad connected by Sidecar would be amazing.

Unfortunatelly this is not possible at the moment as threre is no way to change the brightness of a Sidecar display from macOS. The upcoming versions of the app will be able to detect Virutal displays (like SideCar) at least.

The upcoming 3.1.0 will have some support for Airplay, screen sharing, Sidecar as well as DisplayLink devices in the form of display shading. This is a software based technique which is inferior to gamma control (which is also software based). Notably, mouse cursor will not be dimmed and also during full screen transitions there are irregularities. But still, this is better than nothing.


[WIP]code cleanup

NPE
resource  created using "try-with-resources"
Bump jackson-databind from 2.11.0 to <IP_ADDRESS>

Hi @CalvinKirs be careful when you merge PR to dev, we get [WIP] in the commit title

Hi @CalvinKirs be careful when you merge PR to dev, we get [WIP] in the commit title

Sorry, I forget to update the commit log and PR title :(


hasNotch returns false on OnePlus 6t

Summary
Has notch returns false on OnePlus 6t

Version
0.26.4

Affected OS
Android

OS Version
9

"react": "16.6.3",
"react-native": "0.57.8",
"react-native-device-info": "^0.26.4",
react-native-device-info is not work

@Eddie-CooRo this should be fixed from 0.26.1 onwards. See pull request: https://github.com/rebeccahughes/react-native-device-info/pull/563


Applying Clang Format and Rate Limiter

Apply Clang Format
Add implementation of leaky bucket rate limiter(rate_limit.hpp)

Codecov Report

Merging #20 (7d432d2) into master (ea8c9e7) will increase coverage by 0.33%.
The diff coverage is 92.72%.

@@            Coverage Diff             @@
##           master      #20      +/-   ##
==========================================
+ Coverage   92.18%   92.51%   +0.33%
==========================================
  Files          14       16       +2
  Lines        1676     1871     +195
==========================================
+ Hits         1545     1731     +186
- Misses        131      140       +9

Impacted Files
Coverage Δ

include/libasyik/error.hpp
72.72% <ø> (ø)

include/libasyik/sql.hpp
59.70% <59.70%> (-3.38%)
:arrow_down:

include/libasyik/internal/asio_internal.hpp
80.55% <80.55%> (-2.66%)
:arrow_down:

src/service.cpp
89.09% <87.75%> (ø)

tests/test_http.cpp
90.98% <90.85%> (-0.71%)
:arrow_down:

src/http.cpp
93.26% <93.26%> (+0.71%)
:arrow_up:

include/libasyik/http.hpp
95.62% <95.52%> (+0.97%)
:arrow_up:

include/libasyik/memcache.hpp
97.70% <97.70%> (+2.89%)
:arrow_up:

tests/test_service.cpp
99.07% <99.04%> (-0.02%)
:arrow_down:

include/libasyik/rate_limit.hpp
100.00% <100.00%> (ø)

... and 9 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Prepare KV tests for msrest 0.4.15

@schaabs I'm releasing a new version of msrest that improves the exception message when the JSON is correct OData v4 (i.e. error/code and error/message). This changes slightly the exception message your the KV exception, and requires a tiny fix your in your test case. I think this is ok, but need you for confirm.
This version works both with current and future msrest (so CI should be green).
Thanks

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1494   +/-   ##
=======================================
  Coverage   55.07%   55.07%
=======================================
  Files        3454     3454
  Lines       84233    84233
=======================================
  Hits        46395    46395
  Misses      37838    37838

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 14cf536...e1cfe1c. Read the comment docs.


Fix RxList.removeWhere calls 'ever' multiple times

A single call to RxList.removeWhere will call "ever" multiple times.
The same goes for retainWhere.
It should pass the following test, but in fact it does not.
    final list = [1, 2, 3].obs;
    var count = 0;
    ever<List<int>>(list, (value) {
      count++;
    });
    list.removeWhere((element) => element == 2);
    await Future.delayed(Duration.zero);
    expect(count, 1);

So I fixed it.
Pre-launch Checklist

[ ] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making or feature I am adding, or @jonataslaw said the PR is test-exempt.
[x] All existing and new tests are passing.

Thanks!
LGTM


[Tests] Stop writing log files to disk do it in memory

Try to switch to an in memory logger per test, its a really bad idea to write to files as you have already discovered :)

Fixed in https://github.com/aspnet/Identity/pull/335


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 1092 ms

Resolved: Bofrost.at performance has improved in 8e10489 after 9 minutes.


LH-2776 uppercase K and M

https://sharehouse.atlassian.net/browse/LH-2776?atlOrigin=eyJpIjoiMTYyYTQ3ZmMzNmVjNDJlMjk0YmMzNTg0OWRmNDVhMjYiLCJwIjoiaiJ9
I've added a new custom locale for the specific Product-x requirements.
Once this is merged, all that will be required in @ui-kit/src/lib/formatter/number.ts will be:
require('numeral/locales/lh-en-us');
and then setting the locale with
  numeral.locale('lh-en-us');

@chika-kasymov Yes for that I will make another PR on product-x-frontend.


Fixing Netplugin disconnect

NetpluginDisconnect trigger exposed issue with vxlan vrep creation with ofport not found error.
First suspicion was ovsdb operation being async would need more retries. Also cherry picked sukhesh's commit in this area.

@abhinandanpb as discussed, let's change only the retry for now.

ping @jojimt


Create News "2018-11-14-community-fund-locks-in"

Automatically generated by Netlify CMS

and @kierenhyl can you please link to the page which requires review in the PR description. eg.
https://deploy-preview-190--navhub.netlify.com/news/2018-11-14-community-fund-locks-in/


Cannot exclude a folder from automatic project generation using Terragrunt

Example config:
generate_projects:
  include: "terraform/**"
  exclude: "**/secrets/**"
  terragrunt_parsing:
    parallel: true
    createProjectName: true
    createWorkspace: true
    defaultWorkflow: default

workflows:
  default:
    plan:
      steps:
        - init
        - plan
        - run: echo "Hello World"

In short I'm attempting to exclude any folder with the name secrets from the automatic project generation.
I tried the above but it does not attempt to work. Am I holding this wrong?

Hey @rtizzy thanks for flagging! Documentation is not so clear about this but the include exclude flags are only supported for terraform project generation and not yet implemented for terragrunt generation (confusing I know)
We need to implement support for this in terragrunt using these flags


chore: build dist

That should be a pre commit hook :/

Can you please push a new tag & version and then also npm publish? Thanks :)

(not working on eHealth today)

sure, np

[jo@localhost data-models]$ npm version patch
v1.20.1
[jo@localhost data-models]$ git push --tags
Writing objects: 100% (5/5), 870 bytes | 0 bytes/s, done.
To git@github.com:eHealthAfrica/data-models.git
 * [new tag]         v1.20.1 -> v1.20.1
[jo@localhost data-models]$ npm publish
npm ERR! You do not have permission to publish 'data-models'. Are you logged in as the correct user? : data-models

[jo@localhost data-models]$ npm publish
+<EMAIL_ADDRESS>


Introduced ClientType and refactored

I ran into an issue with token requests for a "Public" client and not supplying the client_secret.
I've introduce a client type property that can be either public, or confidential.
The rules are in the RFC 6749, but to summarise they are.
client_credentials: MUST authenticate with the client_secret.
However Refresh_token, password, and authorization_code support "Public" clients, who can't securely keep their client_secret, so it's not necessary to send them.
Furthermore if the above public clients have any secret associated with them, or the requests supply a password then authentication with the client_secret MUST take place.

Hi after reading the spec for  dynamic client registration (https://tools.ietf.org/html/draft-ietf-oauth-dyn-reg-29), maybe it worth changing the ClientType field to AuthMethod instead? with values "none", "client_secret_post","client_secret_basic" as described here:
token_endpoint_auth_method
String indicator of the requested authentication method for the
token endpoint.  Values defined by this specification are:
  *  "none": The client is a public client as defined in OAuth 2.0
     and does not have a client secret.
  *  "client_secret_post": The client uses the HTTP POST parameters
     defined in OAuth 2.0 section 2.3.1.
  *  "client_secret_basic": the client uses HTTP Basic defined in
     OAuth 2.0 section 2.3.1

Currently the code does not check that the request is made with either method, which would be correct according to the registration draft.
Also, this would conflict with the global allowSecretInParams config value. Perhaps it would be better to remove this config value entirely and drive this functionality on client per client basis with the AuthMethod field instead?

I'm thinking about this change, because it changes a core interface, so all users of the library would need to change their implementations, and I normally would avoid doing it.

Hi, yes breaking changes would need to be carefully considered.
How do you envisage that this change would mess with implementations?
The core changes were made in unexported methods like getClientAuth, handleClientCredentialsRequest etc. So it would be unlikely that people have coded against an internal implementation.
The most noticeable public change would be the addition of AuthMethod to the client struct, which we could make sure that it defaults to a sane value for the existing storage implementations.
Or is there something that I'm missing?

The GetType method on the Client interface. If the DefaultClient implementation was used no code change was needed, but it not it will require changes to their source codes.

I see, that would potentially require implementers to change their source code.
I'll have a look to see if there any non breaking alternatives.


Feat/extcodehash

Pull Request type

Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Resolves: #131
What is the new behavior?

Alrighty!


Add real-time exclusions to eval pipeline exclusions

We already had the infrastructure in place to manually exclude certain forecast date locations from the evaluation pipeline due to poor/ unrealistic wastewater data. This now adds functionality to exclude the forecast date: locations that we chose to exclude in real-time Hub submission.
This is because we produeced a metadata.yaml within the forecasts folder for each forecast date where we listed the locations we chose not to submit the wastewater model for.
Can use this to create the following table in our config:
> table
$location
 [1] "MN" "OH" "IL" "OH" "CO" "TX" "OH" "PA" "FL" "NY" "FL" "OH" "PA" "VA" "IN" "IL" "ID" "OH" "UT" "VA"
[21] "KS" "NY" "UT" "OH" "MN" "MN" "MN"

$forecast_date
 [1] "2024-02-05" "2024-02-05" "2024-02-05" "2024-02-12" "2024-02-12" "2024-02-12" "2024-02-19" "2024-02-19"
 [9] "2024-02-19" "2024-02-19" "2024-02-26" "2024-02-26" "2024-02-26" "2024-02-26" "2024-02-26" "2024-02-26"
[17] "2024-03-04" "2024-03-04" "2024-03-04" "2024-03-04" "2024-03-11" "2024-03-11" "2024-03-11" "2024-03-11"
[25] "2024-01-15" "2024-01-22" "2024-01-29"

Note, I know this is somewhat hardcoded to current implementation. I think thats okay for now, can DRYify later if needed to make more generalizable but I see this as mostly a one off use case for only the purpose of gathering the info in these yaml files in this format

@dylanhmorris I merged this into fix-targets-pipeline bc this is the branch with the wwinference and other latest changes and didn't want to not have this incorporates


Deprecation of _v1 versions of AF_XDP structs

The Linux kernel keeps _v1 versions of (some) updated structs for backwards compatibility with programs written for older kernel versions using AF_XDP. These older struct versions are not exposed via header and have to be skipped in the build.rs checking due to that. This means they cannot be automatically checked for changes or removal.
The newer versions of the deprecated structs work with older versions of the kernel, newer fields will be ignored/not filled.
This issue is linked in the deprecation notice in the code. Please comment here if you are using these structs.

No deprecation as of now, see https://github.com/rust-lang/libc/pull/4163


Update React guide with import and export

Updates the guide based on the new additions to the example on airbrake-js's GitHub repo:
https://github.com/airbrake/airbrake-js/pull/687
Screenshot of updated doc

Thanks @sgray!


Update data-lake-analytics-data-lake-tools-get-started.md

update the Prerequisites part for Data Lake Tools for Visual Studio.

Hi @zxzxy1988, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (xiaoyzhu). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

@edmacauley @mumian
Please verify this change. Thanks!


Add date range picker

Add date range picker to single content item page in order to let end users get metrics for the time period in which they are interested in. Use last 30 days as default time period if none is specified.
No styling on the radio buttons as a component will be coming in the future which handles this.
Change the id's of charts and tables to make them easier to query. The date is not an important part of the chart because there will only be one per query and if we display two different time series on the same chart it could be difficult to handle.

 (3) Add date range section to the Single Performance Page (EPIC 2)


Add a Gitter chat badge to README.md

ElemeFE/element now has a Chat Room on Gitter
@Leopoldthecoder has just created a chat room. You can visit it here: https://gitter.im/ElemeFE/element.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

...居然还有这种 PR


Does exercise #82 skipped deliberately?

Sorry, my bad: https://github.com/erhant/moonmath/commit/42d7a685910fb3c6573cbae341c5bad082f9a1c4. I was in mine fork and didn't double check. X)


swagger-core JSON not compliant with Swagger 2.0 spec

Hello.  I was very excitet to use swagger-diff (http://swagger.io/using-swagger-to-detect-breaking-api-changes/) to detect breaking changes to our APIs.
However, I was very sad to see it fail:
/Users/dvancouvering/.rvm/gems/ruby-2.1.2/gems/hashie-3.3.2/lib/hashie/extensions/coercion.rb:46:in `rescue in set_value_with_coercion': Cannot coerce property "info" from Hash to Swagger::V2::Info: The property 'vendorExtensions' is not defined for Swagger::V2::Info. (Hashie::CoercionError)
Research shows that it is using the swagger-rb gem to parse the JSON being returned from a swagger source.  In this case the source is a JAX-RS endpoint where I am using the annotations from swagger-api/swagger-annotations.
The JSON schema they are using is the Swagger 2.0 JSON schema at https://github.com/swagger-api/swagger-spec/blob/master/schemas/v2.0/schema.json
If you look there are a number of inconsistencies between what this JSON schema defines and what is returned by your tool.   Please see below for some examples.
Are you aware of this?  Is there work ongoing to resolve this?  I am tempted to go into your source and try and fix it to be compliant but if this is already being done no need for me to duplicate effort.
== Some detailed examples ===
From the JSON delivered by swagger-api:
info: {
version: "1.0.0",
title: "",
vendorExtensions: { }
},
In the Swagger 2.0 JSON Schema:
"info": {
"type": "object",
"description": "General information about the API.",
"required": [
"version",
"title"
],
vendorExtensions is present in the swagger-api JSON, but is not defined in the schema.
In the output from swagger-api, this is an example pathItem:
/chroniccondition: {
get: {...},
vendorExtensions: {... },
empty: false,
operations: [...]
In the Swagger 2.0 JSON Schema definition for paths
"pathItem": {
"type": "object",
"additionalProperties": false,
"patternProperties": {
"^x-": {
"$ref": "#/definitions/vendorExtension"
}
},
"properties": {
"$ref": {
"type": "string"
},
"get": {
"$ref": "#/definitions/operation"
},
"put": {
"$ref": "#/definitions/operation"
},
"post": {
"$ref": "#/definitions/operation"
},
"delete": {
"$ref": "#/definitions/operation"
},
"options": {
"$ref": "#/definitions/operation"
},
"head": {
"$ref": "#/definitions/operation"
},
"patch": {
"$ref": "#/definitions/operation"
},
"parameters": {
"$ref": "#/definitions/parametersList"
}
}
}
Note, no reference to "empty" or to the "operations" array, both of which are present in the swagger-api output.
Thanks,
David

Well I'm quite sure that we are generating valid swagger in our projects.  From what your posting, it looks to me like you may be using the Swagger POJOs from the swagger-models project, but not the SwaggerSerializer class?  That's a requirement to turn them into JSON.  Please post back here if I'm misreading your intent.

I am not sure which one we are using.  We are basically installing a
servlet that delivers the Swagger JSON as a separate endpoint on a Tomcat
web application, using JerseyJaxrsConfig.  We annotate all of our REST
endpoints using annotations like @ApiParam and @ApiOperation, and magic
happens when we invoke the JerseyJaxrs endpoint below...
Is there a different way we should be doing this?

Jersey2Config
com.wordnik.swagger.jersey.config.JerseyJaxrsConfig

api.version
1.0.0

swagger.api.basepath
${planservice_url}

2

On Mon, Nov 2, 2015 at 4:02 PM Tony Tam<EMAIL_ADDRESS>wrote:

Well I'm quite sure that we are generating valid swagger in our projects.
From what your posting, it looks to me like you may be using the Swagger
POJOs from the swagger-models project, but not the SwaggerSerializer class?
That's a requirement to turn them into JSON. Please post back here if I'm
misreading your intent.
—
Reply to this email directly or view it on GitHub
https://github.com/swagger-api/swagger-core/issues/1533#issuecomment-153197551
.

I do see that we have the swagger-models jar in the classpath.  How would we go about using SwaggerSerializer with our servlet?

We are following the instructions here:
https://github.com/swagger-api/swagger-core/wiki/Swagger-Core-Jersey-2.X-Project-Setup-1.5
And it is generating the output I described above.
This sure seems like a bug because the page above specifically says it is generating Swagger 2.0 output, but in the output from the /swagger.json endpoint, there are fields being added that are not part of the Swagger 2.0 JSON schema.
Sorry if I'm missing something

Here in the Swagger 2.0 spec referred to from
https://github.com/swagger-api/swagger-core/wiki/Swagger-Core-Jersey-2.X-Project-Setup-1.5
It has the Info object like this:
https://github.com/swagger-api/swagger-spec/blob/master/versions/2.0.md#infoObject
Note there is no field called vendorExtensions, but that is included in the output from the /swagger.json endpoint
And here is the pathItem object
https://github.com/swagger-api/swagger-spec/blob/master/versions/2.0.md#pathItemObject
And there is no reference to the "empty" or "operations" fields which show up in the output from the /swagger.json endpoint

OK, so this is very strange.  I just pulled down the jersey-jaxrs sample from here
https://github.com/swagger-api/swagger-samples/tree/master/java/java-jersey2
Built it and ran it, and it is producing what appears to be compliant json.
Sadly, swagger-diff still fails with a stupid error
"Swagger version swagger is not currently supported"
But now I need to figure out why your example generates different JSON than ours, when the configuration looks to be exactly the same and we are just using the standard annotations...  Clearly some digging is necessary.

I'm happy to help, but (a) swagger-diff is not the official way to validate swagger compliance and (b) you're not following those instructions.
First off, the dependency listed here:
https://github.com/swagger-api/swagger-core/wiki/Swagger-Core-Jersey-2.X-Project-Setup-1.5#concrete-class-selection
Is quite different from what you're using.  com.wordnik was deprecated over a year ago.  Please use this as your dependency:
<dependency>
  <groupId>io.swagger</groupId>
  <artifactId>swagger-jersey2-jaxrs</artifactId>
  <version>1.5.4</version>
</dependency>

This is the latest release version of swagger-core.
Next, your web.xml here:
<servlet-class>com.wordnik.swagger.jersey.config.JerseyJaxrsConfig</servlet-class>

Is pointing to the older version of swagger (note the com.wordnik).  Use the proper package, which is shown here:
https://github.com/swagger-api/swagger-core/wiki/Swagger-Core-Jersey-2.X-Project-Setup-1.5#package-scanning--concrete-class-selection
Finally, there are samples that do all this for you, which you'll probably have an easier time following.  For jersey2:
https://github.com/swagger-api/swagger-samples/tree/master/java/java-jersey2
I know it can be frustrating getting things working, but if our own tools couldn't validate against our own specification, something would really be wrong.

Yes, thanks, I saw those com.wordnik references just 20 minutes ago and
fixed them and was sure that would do it, and sadly still got the weird
results, even though your sample doesn't generate them.  I have peered
closely at the sample code and XML files compared it with my own and can
find no difference.  But clearly a difference exists or I wouldn't get
different output.
I agree swagger-diff is not an official compliance tester.  But I want to
use it :( and so far have been unable to because of the JSON output I'm
getting.
I'll report back any findings
On Mon, Nov 2, 2015 at 7:41 PM Tony Tam<EMAIL_ADDRESS>wrote:

I'm happy to help, but (a) swagger-diff is not the official way to
validate swagger compliance and (b) you're not following those instructions.
First off, the dependency listed here:
https://github.com/swagger-api/swagger-core/wiki/Swagger-Core-Jersey-2.X-Project-Setup-1.5#concrete-class-selection
Is quite different from what you're using. com.wordnik was deprecated
over a year ago. Please use this as your dependency:

io.swagger
swagger-jersey2-jaxrs
1.5.4

This is the latest release version of swagger-core.
Next, your web.xml here:
com.wordnik.swagger.jersey.config.JerseyJaxrsConfig
Is pointing to the older version of swagger (note the com.wordnik). Use
the proper package, which is shown here:
https://github.com/swagger-api/swagger-core/wiki/Swagger-Core-Jersey-2.X-Project-Setup-1.5#package-scanning--concrete-class-selection
Finally, there are samples that do all this for you, which you'll probably
have an easier time following. For jersey2:
https://github.com/swagger-api/swagger-samples/tree/master/java/java-jersey2
I know it can be frustrating getting things working, but if our own tools
couldn't validate against our own specification, something would really be
wrong.
—
Reply to this email directly or view it on GitHub
https://github.com/swagger-api/swagger-core/issues/1533#issuecomment-153232321
.

You need to ensure that the SwaggerSerializers are enabled.  They are what turn the POJOs into the swagger objects correctly.

Well, I gave it another try after carefully making sure that the two XML files looked the same.  So this time I had success!
swagger-diff is still barfing but I think that's a bug in swagger-diff.  Your JSON looks great now.
Thanks for your help (and patience :)).

Closing for now. Please reopen if needed.

Just so you know, the root cause of the bug was a subtle difference you
probably want to document in your migration guide:
In the old Swagger you included com.wordnik.swagger.jersey.listing
In the new 1.5.4 version of Swagger, you need to include
io.swagger.jaxrs.listing
Note the switch from "jersey" to "jaxrs"
That made all the difference.
Also, as a note, when a libraries has an incompatible change so that
existing compiled code will no longer work (such as changing the package
names), that should be considered a major version change, not a patch
version change (e.g. from 1.5.3 to 1.5.4).
See http://semver.org:
Given a version number MAJOR.MINOR.PATCH, increment the:

MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compatible
manner, and
PATCH version when you make backwards-compatible bug fixes.

Thanks!
David
On Tue, Nov 3, 2015 at 3:05 PM Ron<EMAIL_ADDRESS>wrote:

Closed #1533 https://github.com/swagger-api/swagger-core/issues/1533.
—
Reply to this email directly or view it on GitHub
https://github.com/swagger-api/swagger-core/issues/1533#event-453814943.

Thanks for the feedback. I believe what you mentioned here is covered by https://github.com/swagger-api/swagger-core/wiki/1.3--1.5-Migration#jax-rs-providers.
As for the versioning, that change was introduced in 1.5.0 not 1.5.4, a major version.

Thanks.  I must have missed that, sorry aboutthat.
It's weird we were using 1.5.3 with the wordnik package and it was working
fine :(
1.5.0 is a minor version.  2.0 would be a major version.
On Tue, Nov 3, 2015 at 4:28 PM Ron<EMAIL_ADDRESS>wrote:

Thanks for the feedback. I believe what you mentioned here is covered by
https://github.com/swagger-api/swagger-core/wiki/1.3--1.5-Migration#jax-rs-providers
.
As for the versioning, that change was introduced in 1.5.0 not 1.5.4, a
major version.
—
Reply to this email directly or view it on GitHub
https://github.com/swagger-api/swagger-core/issues/1533#issuecomment-153532742
.

Not in our book ;) We don't really follow semver officially.

We probably could have done better with the versioning for 1.5.x but as ron said, this change is history.

LOL yes spilt milk.  As a user though it would reduce surprises.  Thanks
for all you do!!
On Wed, Nov 4, 2015 at 4:40 PM Tony Tam<EMAIL_ADDRESS>wrote:

We probably could have done better with the versioning for 1.5.x but as
ron said, this change is history.
—
Reply to this email directly or view it on GitHub
https://github.com/swagger-api/swagger-core/issues/1533#issuecomment-153916472
.


Support types IPAddress and IPEndpoint

Be able to bind / convert to these types. IPEndpoint seems to be .NET Core 3 only.

I'll take a look at this one, got some knowledge on sockets


Fix merging multiple meshes that have different flip face winding

Fix for issue https://github.com/zeux/meshoptimizer/issues/315

Thanks!


tests: add test to Datepicker, change date format

tests #821

Nice job! I will have a look later but @darrenvong should look as well

Can you rebase from develop as well when you next get a chance to look through this please? The build is failing on some old code that's not your fault and it's been fixed since!

This was such a mess, I spend 3 hours debugging, trying to get single letter formats (like M/D/YYYY) to work with typing. In the end I just decided to convert them to the respective double letter.


Using it under docker

`$ docker compose up -d --build
[+] Running 56/5
✔ phpmyadmin 18 layers [⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿]      0B/0B      Pulled                                                                                18.0s
✔ kibana 13 layers [⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿]      0B/0B      Pulled                                                                                51.7s
✔ mysql 8 layers [⣿⣿⣿⣿⣿⣿⣿⣿]      0B/0B      Pulled                                                                                17.6s
✔ mailcatcher 6 layers [⣿⣿⣿⣿⣿⣿]      0B/0B      Pulled                                                                                14.6s
✔ elasticsearch 6 layers [⣿⣿⣿⣿⣿⣿]      0B/0B      Pulled                                                                                50.2s
[+] Building 33.0s (10/10) FINISHED                                                                                docker:default
=> [wordpress internal] load build definition from Dockerfile                                                                                0.0s
=> => transferring dockerfile: 458B                                                                                0.0s
=> [wordpress internal] load metadata for docker.io/ministryofjustice/intranet-base:latest                                                                                2.3s
=> [wordpress auth] ministryofjustice/intranet-base:pull token for registry-1.docker.io                                                                                0.0s
=> [wordpress internal] load .dockerignore                                                                                0.0s
=> => transferring context: 74B                                                                                0.0s
=> [wordpress internal] load build context                                                                                0.3s
=> => transferring context: 52.54MB                                                                                0.3s
=> [wordpress 1/5] FROM docker.io/ministryofjustice/intranet-base:latest@sha256:c5c1ee14d1c5573ff5c3c26ad219f38eebaeb3933659c36a19557af1ed4e3fd0                                                  22.5s
=> => resolve docker.io/ministryofjustice/intranet-base:latest@sha256:c5c1ee14d1c5573ff5c3c26ad219f38eebaeb3933659c36a19557af1ed4e3fd0                                                             0.0s
=> => sha256:ca448c2d211cc83cb51cae1878c4e5ef8574860e7b3659b2258a23e2f1a32516 11.28kB / 11.28kB                                                                                0.0s
=> => sha256:1c87975145eecf0193b9ed0a5affccc1e1c22c7c540155eeca9ad11fd581c451 4.09kB / 4.09kB                                                                                0.0s
=> => sha256:2b55860d4c667a7200a0cb279aec26777df61e5d3530388f223ce7859d566e7a 30.43MB / 30.43MB                                                                                1.8s
=> => sha256:c5c1ee14d1c5573ff5c3c26ad219f38eebaeb3933659c36a19557af1ed4e3fd0 2.38kB / 2.38kB                                                                                0.0s
=> => sha256:8e058277d049672ae8bcf8ab552c3062972fc8aa5796eea147e4642a9aff1709 15.21kB / 15.21kB                                                                                0.8s
=> => sha256:cac814e1eefde971c99c23b7f5ed84e427a693244cc9be90521ccb7ba9c410c5 53.97MB / 53.97MB                                                                                10.9s
=> => sha256:7973af5aec3655bb21c50e8decfe2eeee119d033467527912bd52c75688ab0cc 282.26MB / 282.26MB                                                                                15.6s
=> => sha256:7e863d092a5ad5ffa0c016951f91f03d32ab91c9b653f6049b2f892e625d9bf4 699.42kB / 699.42kB                                                                                2.5s
=> => extracting sha256:2b55860d4c667a7200a0cb279aec26777df61e5d3530388f223ce7859d566e7a                                                                                0.6s
=> => extracting sha256:8e058277d049672ae8bcf8ab552c3062972fc8aa5796eea147e4642a9aff1709                                                                                0.0s
=> => sha256:8ce37feaab37e5420d19fe91d07ca5fc91f9a1b443dd77e16c7a96c673ad975b 124.08kB / 124.08kB                                                                                3.1s
=> => sha256:1012105fb646e2fb01c39d534ef60800cb7999244409d064ca8e7e456cd007dd 1.44MB / 1.44MB                                                                                3.9s
=> => sha256:77f5118a534af1be22b08590ea86a66fe06e5127614daa1879aae8e5be107959 27.59MB / 27.59MB                                                                                7.0s
=> => sha256:37b70bc744994942a1df04b60f70387bd2e86e3755e22a1f56cc9211f8d66325 33.05kB / 33.05kB                                                                                7.6s
=> => sha256:743c08e3a366490e0a59da341032a1bc4aa0e3d1932f694acb93e90dec555429 1.13kB / 1.13kB                                                                                8.6s
=> => sha256:e416b513396c7fd105515e0fba27d7f0668704853518c96dbf3a901ac254ebc5 701B / 701B                                                                                9.4s
=> => sha256:51f79ba91c4c26a52e31b1ac7f8041d948219e7618c1605f8e36fce52e4f3820 498B / 498B                                                                                10.6s
=> => sha256:bc6d1d2c60b287e5b112b8aa536be72f98cd6bf73123feca3dc8f8d8f874dfd9 3.11kB / 3.11kB                                                                                10.9s
=> => extracting sha256:cac814e1eefde971c99c23b7f5ed84e427a693244cc9be90521ccb7ba9c410c5                                                                                1.0s
=> => sha256:e00c63e0fcfbc74ffdf2613f798ffb62728544f2a1d7d5eb8716552a877a10d1 489B / 489B                                                                                11.5s
=> => sha256:0c42ed8cc2b8870b7d1aaf7458fe829506947c4d98b3fe932b304a85a323d824 29.65kB / 29.65kB                                                                                11.8s
=> => sha256:bd7593b9ded326698e6880bb1fa13737fd338cd4c13214fdee58401de80d8ea6 3.42kB / 3.42kB                                                                                12.2s
=> => sha256:23da015f7c16e8544f3a53d7d49ddfa39dd6f0fde4bdcd539509add2ee32fd8c 1.88kB / 1.88kB                                                                                12.4s
=> => sha256:de91aa45071aa9074b0966b78672a56d1615de51c9d91e1abe186901bad62092 1.05kB / 1.05kB                                                                                12.8s
=> => sha256:3a6cf7fb2d7aa53a3ba14f57088a54c7f4a20a0630db8f7e8854e867e79f4d63 321.26kB / 321.26kB                                                                                13.1s
=> => sha256:e25fb78d48fb861fb0bf98fbc0b79b9f9c84b739f039558b4f8d014c581205d0 97B / 97B                                                                                13.5s
=> => extracting sha256:7973af5aec3655bb21c50e8decfe2eeee119d033467527912bd52c75688ab0cc                                                                                5.7s
=> => extracting sha256:7e863d092a5ad5ffa0c016951f91f03d32ab91c9b653f6049b2f892e625d9bf4                                                                                0.0s
=> => extracting sha256:8ce37feaab37e5420d19fe91d07ca5fc91f9a1b443dd77e16c7a96c673ad975b                                                                                0.0s
=> => extracting sha256:1012105fb646e2fb01c39d534ef60800cb7999244409d064ca8e7e456cd007dd                                                                                0.0s
=> => extracting sha256:77f5118a534af1be22b08590ea86a66fe06e5127614daa1879aae8e5be107959                                                                                0.7s
=> => extracting sha256:37b70bc744994942a1df04b60f70387bd2e86e3755e22a1f56cc9211f8d66325                                                                                0.0s
=> => extracting sha256:743c08e3a366490e0a59da341032a1bc4aa0e3d1932f694acb93e90dec555429                                                                                0.0s
=> => extracting sha256:e416b513396c7fd105515e0fba27d7f0668704853518c96dbf3a901ac254ebc5                                                                                0.0s
=> => extracting sha256:51f79ba91c4c26a52e31b1ac7f8041d948219e7618c1605f8e36fce52e4f3820                                                                                0.0s
=> => extracting sha256:bc6d1d2c60b287e5b112b8aa536be72f98cd6bf73123feca3dc8f8d8f874dfd9                                                                                0.0s
=> => extracting sha256:0c42ed8cc2b8870b7d1aaf7458fe829506947c4d98b3fe932b304a85a323d824                                                                                0.0s
=> => extracting sha256:e00c63e0fcfbc74ffdf2613f798ffb62728544f2a1d7d5eb8716552a877a10d1                                                                                0.0s
=> => extracting sha256:bd7593b9ded326698e6880bb1fa13737fd338cd4c13214fdee58401de80d8ea6                                                                                0.0s
=> => extracting sha256:23da015f7c16e8544f3a53d7d49ddfa39dd6f0fde4bdcd539509add2ee32fd8c                                                                                0.0s
=> => extracting sha256:de91aa45071aa9074b0966b78672a56d1615de51c9d91e1abe186901bad62092                                                                                0.0s
=> => extracting sha256:3a6cf7fb2d7aa53a3ba14f57088a54c7f4a20a0630db8f7e8854e867e79f4d63                                                                                0.0s
=> => extracting sha256:e25fb78d48fb861fb0bf98fbc0b79b9f9c84b739f039558b4f8d014c581205d0                                                                                0.0s
=> [wordpress 2/5] ADD . /bedrock                                                                                0.9s
=> [wordpress 3/5] WORKDIR /bedrock                                                                                0.0s
=> [wordpress 4/5] RUN mv docker/conf/nginx/server.conf /etc/nginx/sites-available/                                                                                0.2s
=> ERROR [wordpress 5/5] RUN chmod +x bin/* && sleep 1 &&     bin/composer-auth.sh &&     make build &&     rm -f auth.json                                                                        6.9s

[wordpress 5/5] RUN chmod +x bin/* && sleep 1 &&     bin/composer-auth.sh &&     make build &&     rm -f auth.json:
1.427 bin/build.sh
1.493 Composer plugins have been disabled for safety in this non-interactive session. Set COMPOSER_ALLOW_SUPERUSER=1 if you want to allow plugins to run as root/super user.
1.493 Do not run Composer as root/super user! See https://getcomposer.org/root for details
1.544 Installing dependencies from lock file (including require-dev)
1.547 Verifying lock file contents can be installed on current platform.
1.560 Package operations: 64 installs, 0 updates, 0 removals
1.561   - Downloading johnpbloch/wordpress-core-installer (2.0.0)
1.561   - Downloading koodimonni/composer-dropin-installer (1.4)
1.562   - Downloading composer/installers (v1.12.0)
1.562   - Downloading php-http/discovery (1.19.2)
1.562   - Downloading acf/advanced-custom-fields-pro (6.1.6)
1.562   - Downloading ralouphie/getallheaders (3.0.3)
1.563   - Downloading psr/http-message (2.0)
1.563   - Downloading psr/http-factory (1.0.2)
1.563   - Downloading guzzlehttp/psr7 (2.6.2)
1.563   - Downloading firebase/php-jwt (v6.10.0)
1.564   - Downloading alphagov/notifications-php-client (5.0.0)
1.564   - Downloading symfony/polyfill-mbstring (v1.28.0)
1.564   - Downloading mtdowling/jmespath.php (2.7.0)
1.564   - Downloading guzzlehttp/promises (2.0.2)
1.564   - Downloading symfony/deprecation-contracts (v3.4.0)
1.565   - Downloading psr/http-client (1.0.3)
1.565   - Downloading guzzlehttp/guzzle (7.8.1)
1.565   - Downloading aws/aws-crt-php (v1.2.4)
1.565   - Downloading aws/aws-sdk-php (3.295.8)
1.565   - Downloading clue/stream-filter (v1.7.0)
1.565   - Downloading johnpbloch/wordpress-core (6.4.2)
1.565   - Downloading johnpbloch/wordpress (6.4.2)
1.566   - Downloading koodimonni-language/core-en_gb (6.4.2)
1.566   - Downloading ministryofjustice/like-button-for-wordpress (dev-main a67d6e0)
1.566   - Downloading ministryofjustice/notify-for-wordpress (dev-main 832ae0c)
1.566   - Downloading ministryofjustice/php-markdown-extra (dev-main af8e1dd)
1.566   - Downloading ministryofjustice/wp-moj-components (3.5.1)
1.566   - Downloading ministryofjustice/wp-moj-elasticsearch (2.3.3)
1.566   - Downloading ministryofjustice/wp-rewrite-media-to-s3 (dev-php8-code-update 693cd89)
1.566   - Downloading symfony/polyfill-ctype (v1.28.0)
1.567   - Downloading oscarotero/env (v1.2.0)
1.567   - Downloading php-http/promise (1.3.0)
1.567   - Downloading phpstan/phpstan (1.10.55)
1.567   - Downloading rector/rector (0.15.25)
1.567   - Downloading roots/wp-password-bcrypt (1.1.0)
1.567   - Downloading psr/container (2.0.2)
1.567   - Downloading symfony/service-contracts (v3.4.1)
1.568   - Downloading symfony/http-client-contracts (v3.4.0)
1.568   - Downloading psr/log (3.0.0)
1.568   - Downloading symfony/http-client (v7.0.2)
1.568   - Downloading symfony/polyfill-php80 (v1.28.0)
1.568   - Downloading symfony/options-resolver (v7.0.0)
1.568   - Downloading http-interop/http-factory-guzzle (1.2.0)
1.568   - Downloading php-http/message-factory (1.1.0)
1.568   - Downloading php-http/message (1.16.0)
1.568   - Downloading php-http/httplug (2.4.0)
1.569   - Downloading php-http/client-common (2.7.1)
1.569   - Downloading php-http/guzzle7-adapter (1.0.0)
1.569   - Downloading jean85/pretty-package-versions (2.0.5)
1.569   - Downloading sentry/sentry (3.22.1)
1.569   - Downloading squizlabs/php_codesniffer (3.8.0)
1.570   - Downloading vlucas/phpdotenv (v2.6.9)
1.570   - Downloading wpackagist-plugin/classic-editor (1.6.3)
1.570   - Downloading wpackagist-plugin/cms-tree-page-view (1.6.8)
1.570   - Downloading wpackagist-plugin/co-authors-plus (3.5.15)
1.570   - Downloading wpackagist-plugin/debug-bar (1.1.4)
1.570   - Downloading wpackagist-plugin/debug-bar-elasticpress (3.1.0)
1.570   - Downloading wpackagist-plugin/elasticpress (5.0.1)
1.570   - Downloading wpackagist-plugin/ewww-image-optimizer (7.2.3)
1.570   - Downloading wpackagist-plugin/query-monitor (3.15.0)
1.571   - Downloading wpackagist-plugin/simple-301-redirects (2.0.9)
1.571   - Downloading wpackagist-plugin/totalpoll-lite (4.9.9)
1.571   - Downloading wpackagist-plugin/wp-document-revisions (3.5.0)
1.584   0/63 [>---------------------------]   0%
2.615  11/63 [====>-----------------------]  17%
2.756  16/63 [=======>--------------------]  25%    Failed to download ministryofjustice/wp-moj-components from dist: The 'https://composer.wp.dsd.io/dist/ministryofjustice/wp-moj-components/ministryofjustice-wp-moj-components-bc735aaab6ee2d67e6afed2fad6399ecf9accf05-zip-447db5.zip' URL could not be accessed (HTTP 403): HTTP/2 403
2.794     Now trying to download from source
2.796     Failed to download ministryofjustice/wp-moj-elasticsearch from dist: The 'https://composer.wp.dsd.io/dist/ministryofjustice/wp-moj-elasticsearch/ministryofjustice-wp-moj-elasticsearch-9bfb7e185fb3adeafd26ed3ae96d67e22523f2fc-zip-80fb6b.zip' URL could not be accessed (HTTP 403): HTTP/2 403
2.796     Now trying to download from source
2.903
2.903  21/63 [=========>------------------]  33%
3.204  27/63 [============>---------------]  42%
3.607  34/63 [===============>------------]  53%
3.909  38/63 [================>-----------]  60%
4.312  47/63 [====================>-------]  74%
4.881  51/63 [======================>-----]  80%
5.809  58/63 [=========================>--]  92%
6.809  63/63 [============================] 100%
6.857 In AuthHelper.php line 205:
6.857
6.857   The 'https://composer.wp.dsd.io/dist/acf/advanced-custom-fields-pro/acf-adv
6.857   anced-custom-fields-pro-6.1.6.zip' URL could not be accessed (HTTP 403): HT
6.857   TP/2 403
6.857
6.857
6.857 install [--prefer-source] [--prefer-dist] [--prefer-install PREFER-INSTALL] [--dry-run] [--download-only] [--dev] [--no-suggest] [--no-dev] [--no-autoloader] [--no-progress] [--no-install] [--audit] [--audit-format AUDIT-FORMAT] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--apcu-autoloader-prefix APCU-AUTOLOADER-PREFIX] [--ignore-platform-req IGNORE-PLATFORM-REQ] [--ignore-platform-reqs] [--] [...]
6.857
6.882 make: *** [Makefile:5: build] Error 255

failed to solve: process "/bin/sh -c chmod +x bin/* && sleep 1 &&     bin/composer-auth.sh &&     make build &&     rm -f auth.json" did not complete successfully: exit code: 2
$ docker --version
Docker version 25.0.3, build 4debf41
$ cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.3 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.3 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy
$ uname -a
Linux ikigai 6.5.0-18-generic #18~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb  7 11:40:03 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
$ `

Hello. Where can I find documentation about this private repository?
Private composer repository
The private composer repository composer.wp.dsd.io contains premium and custom WordPress plugins.
Access to this repository is restricted. Refer to internal documentation for further details.

Hi @sekroots - whilst our code is public, some dependencies remain private.
Please, feel free to use something like Satis to create your own repository or indeed, remove the private dependencies to allow composer to run.
Good luck, apologies for the delay in responding.

Thanks a lot.
On Fri, Mar 1, 2024 at 6:57 PM Damien Wilson @.***>
wrote:

Hi @sekroots https://github.com/sekroots - whilst our code is public,
some dependencies remain private.
Please, feel free to use something like Satis
https://github.com/composer/satis to create your own repository or
indeed, remove the private dependencies to allow composer to run.
Good luck, apologies for the delay in responding.
—
Reply to this email directly, view it on GitHub
https://github.com/ministryofjustice/intranet/issues/467#issuecomment-1973982585,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYT2GHG2NCSIVVWZ2T7MPVTYWD2VNAVCNFSM6AAAAABDUEUDE6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZTHE4DENJYGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

You're most welcome. Have a great day.


CanonicalVote and CanonicalProposal now correctly encode/decode BlockId

Closes #663.
Correctly encode/decode CanonicalBlockId for CanonicalVote and CanonicalProposal. See issue for more details.

[X] Referenced an issue explaining the need for the change
[ ] Updated all relevant documentation in docs
[X] Updated all code comments where relevant
[ ] Wrote tests
[X] Updated CHANGELOG.md

Codecov Report

Merging #664 (444e94f) into master (0b1962a) will increase coverage by 0.1%.
The diff coverage is 37.5%.

@@           Coverage Diff            @@
##           master    #664     +/-   ##
========================================
+ Coverage    38.9%   39.0%   +0.1%
========================================
  Files         184     184
  Lines       12811   12809      -2
  Branches     2929    2926      -3
========================================
+ Hits         4984    4997     +13
+ Misses       7583    7566     -17
- Partials      244     246      +2

Impacted Files
Coverage Δ

light-client/tests/model_based.rs
0.2% <ø> (ø)

tendermint/src/block/id.rs
73.6% <ø> (ø)

tendermint/src/proposal/canonical_proposal.rs
54.7% <25.0%> (-2.2%)
:arrow_down:

tendermint/src/vote/canonical_vote.rs
61.9% <50.0%> (+3.5%)
:arrow_up:

tendermint/src/hash.rs
50.5% <0.0%> (-3.3%)
:arrow_down:

light-client/src/utils.rs
17.4% <0.0%> (+2.0%)
: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 0b1962a...444e94f. Read the comment docs.

All right, regression tests were added.
The first problem with regression tests is that there is supposed to be an original test case at the "before" state of the change that you compare to and shame on me: the CanonicalVote and CanonicalProposal structs didn't have tests at all.
So I added a few unit tests to check the domain knowledge about these types. As we implement more domain knowledge, hopefully this gets extended more and possibly used for regression testing.
The second problem was that regression tests are supposed to prove that the rest of the system behaves similarly as before and only the area of change are affected. CanonicalVote and CanonicalProposal are used in signing and although signing has tests (which still pass), but not the specific case where the block ID is present but with an empty hash. So I added this specific test to the signing tests. The proof is that all signing still passes and builds the sameprotobuf bytestream as they do in Go.


[tool_crash] ProcessException: End-of-central-directory signature not found. Either this file is not a zipfile, or it constitutes one disk of a multi-part archive

Detailed error:
[tool_crash] ProcessException: The command failedStdout:Stderr:[/home/ramamoorthy/snap/flutter/common/flutter/bin/cache/downloads/storage.googleapis.com/flutter_infra/flutter/4654fc6cf6416daae78eac2c211ad84c46e21625/linux-x64/artifacts.zip]  End-of-central-directory signature not found.  Either this file is not  a zipfile, or it constitutes one disk of a multi-part archive.  In the  latter case the central directory and zipfile comment will be found on  the last disk(s) of this archive.unzip:  cannot find zipfile directory in one of /home/ramamoorthy/snap/flutter/common/flutter/bin/cache/downloads/storage.googleapis.com/flutter_infra/flutter/4654fc6cf6416daae78eac2c211ad84c46e21625/linux-x64/artifacts.zip or        /home/ramamoorthy/snap/flutter/common/flutter/bin/cache/downloads/storage.googleapis.com/flutter_infra/flutter/4654fc6cf6416daae78eac2c211ad84c46e21625/linux-x64/artifacts.zip.zip, and cannot find /home/ramamoorthy/snap/flutter/common/flutter/bin/cache/downloads/storage.googleapis.com/flutter_infra/flutter/4654fc6cf6416daae78eac2c211ad84c46e21625/linux-x64/artifacts.zip.ZIP, period. Command: unzip, OS error code: 9
Command
flutter --no-color --no-version-check precache

Steps to Reproduce

...
...
...

Logs
ProcessException: The command failed
Stdout:

Stderr:
[/home/ramamoorthy/snap/flutter/common/flutter/bin/cache/downloads/storage.googleapis.com/flutter_infra/flutter/4654fc6cf6416daae78eac2c211ad84c46e21625/linux-x64/artifacts.zip]
  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive.  In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive.
unzip:  cannot find zipfile directory in one of /home/ramamoorthy/snap/flutter/common/flutter/bin/cache/downloads/storage.googleapis.com/flutter_infra/flutter/4654fc6cf6416daae78eac2c211ad84c46e21625/linux-x64/artifacts.zip or
        /home/ramamoorthy/snap/flutter/common/flutter/bin/cache/downloads/storage.googleapis.com/flutter_infra/flutter/4654fc6cf6416daae78eac2c211ad84c46e21625/linux-x64/artifacts.zip.zip, and cannot find /home/ramamoorthy/snap/flutter/common/flutter/bin/cache/downloads/storage.googleapis.com/flutter_infra/flutter/4654fc6cf6416daae78eac2c211ad84c46e21625/linux-x64/artifacts.zip.ZIP, period.
 Command: unzip, OS error code: 9

#0      RunResult.throwException (package:flutter_tools/src/base/process.dart:172:5)
#1      _DefaultProcessUtils.runSync (package:flutter_tools/src/base/process.dart:463:17)
#2      _PosixUtils.unzip (package:flutter_tools/src/base/os.dart:221:19)
#3      ArtifactUpdater._downloadArchive (package:flutter_tools/src/cache.dart:1511:18)
#4      _rootRunUnary (dart:async/zone.dart:1198:47)
#5      _CustomZone.runUnary (dart:async/zone.dart:1100:19)
#6      _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
#7      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
#8      Future._propagateToListeners (dart:async/future_impl.dart:725:32)
#9      Future._completeWithValue (dart:async/future_impl.dart:529:5)
#10     Future._asyncCompleteWithValue.<anonymous closure> (dart:async/future_impl.dart:567:7)
#11     _rootRun (dart:async/zone.dart:1190:13)
#12     _CustomZone.run (dart:async/zone.dart:1093:19)
#13     _CustomZone.runGuarded (dart:async/zone.dart:997:7)
#14     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:1037:23)
#15     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#16     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#17     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
#18     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:169:5)

[✓] Flutter (Channel beta, 1.22.0-12.1.pre, on Linux, locale en_IN)
    • Flutter version 1.22.0-12.1.pre at /home/ramamoorthy/snap/flutter/common/flutter
    • Framework revision 8b3760638a (5 days ago), 2020-09-15 17:47:13 -0700
    • Engine revision 4654fc6cf6
    • Dart version 2.10.0 (build 2.10.0-110.3.beta)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /home/ramamoorthy/Android/Sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: /home/ramamoorthy/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[✓] Android Studio (version 4.0)
    • Android Studio at /home/ramamoorthy/android-studio
    • Flutter plugin version 49.0.2
    • Dart plugin version 193.7547
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.49.1)
    • VS Code at /usr/share/code
    • Flutter extension version 3.14.1

[✓] Connected device (2 available)
    • Web Server (web) • web-server • web-javascript • Flutter Tools
    • Chrome (web)     • chrome     • web-javascript • Google Chrome 84.0.4147.105

• No issues found!

Flutter Application Metadata
No pubspec in working directory.

I run into the same error after a down and upgrade of the flutter sdk
Downloading darwin-arm64 tools...                                   5,1s
[/Users/rekire/dev/flutter/bin/cache/downloads/storage.googleapis.com/flutter_infra_release/flutter/74d16627b940bb15e50891f82cad6c3e3465bd6d/darwin-arm64/artifacts.zip]
End-of-central-directory signature not found.  Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive.  In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip:  cannot find zipfile directory in one of /Users/rekire/dev/flutter/bin/cache/downloads/storage.googleapis.com/flutter_infra_release/flutter/74d16627b940bb15e50891f82cad6c3e3465bd6d/darwin-arm64/artifacts.zip or
/Users/rekire/dev/flutter/bin/cache/downloads/storage.googleapis.com/flutter_infra_release/flutter/74d16627b940bb15e50891f82cad6c3e3465bd6d/darwin-arm64/artifacts.zip.zip, and cannot find /Users/rekire/dev/flutter/bin/cache/downloads/storage.googleapis.com/flutter_infra_release/flutter/74d16627b940bb15e50891f82cad6c3e3465bd6d/darwin-arm64/artifacts.zip.ZIP, period.
Downloading darwin-arm64 tools...                                   4,2s
[/Users/rekire/dev/flutter/bin/cache/downloads/storage.googleapis.com/flutter_infra_release/flutter/74d16627b940bb15e50891f82cad6c3e3465bd6d/darwin-arm64/artifacts.zip]
End-of-central-directory signature not found.  Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive.  In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip:  cannot find zipfile directory in one of /Users/rekire/dev/flutter/bin/cache/downloads/storage.googleapis.com/flutter_infra_release/flutter/74d16627b940bb15e50891f82cad6c3e3465bd6d/darwin-arm64/artifacts.zip or
/Users/rekire/dev/flutter/bin/cache/downloads/storage.googleapis.com/flutter_infra_release/flutter/74d16627b940bb15e50891f82cad6c3e3465bd6d/darwin-arm64/artifacts.zip.zip, and cannot find /Users/rekire/dev/flutter/bin/cache/downloads/storage.googleapis.com/flutter_infra_release/flutter/74d16627b940bb15e50891f82cad6c3e3465bd6d/darwin-arm64/artifacts.zip.ZIP, period.
Flutter could not download and/or extract https://storage.googleapis.com/flutter_infra_release/flutter/74d16627b940bb15e50891f82cad6c3e3465bd6d/darwin-arm64/artifacts.zip. Ensure you have network connectivity and all of the required dependencies listed at flutter.dev/setup.
The original exception was: ProcessException: The command failed


Add New button of F&F modal does not look right.

Does not look right.

Verified this issue on dev app v1.7.9(309)


Fix documentation for auth_request directive

The correct endpoint is /oauth2/auth

thanks!

related: #226
(for an un-authed user to sign-in, the other paths under /oauth2 need to proxy to oauth2_proxy)


[ISSUE #1846] Dledger model change into pipeline manner to improve performance

What is the purpose of the change
Dledger model change into pipeline manner to improve performance
closes #1846
Brief changelog
1.Implement asyncPutMessage in dledger commitlog
2.move serialization out of lock
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage decreased (-0.1%) to 50.791% when pulling 6ad7487713619fa2ac7f26b34ece62c7dd0398ff on RongtongJin:dledger_async into 3974677f04815609951c17059d85d3795eb51247 on apache:develop.

@zhangjidi2016 @Aaron-He  You can review this pr, please.Thanks.

Codecov Report

Merging #1847 into develop will decrease coverage by 0.12%.
The diff coverage is 76.41%.

@@              Coverage Diff              @@
##             develop    #1847      +/-   ##
=============================================
- Coverage      45.81%   45.68%   -0.13%
+ Complexity      4298     4296       -2
=============================================
  Files            547      547
  Lines          35971    36029      +58
  Branches        4770     4782      +12
=============================================
- Hits           16481    16461      -20
- Misses         17433    17499      +66
- Partials        2057     2069      +12

Impacted Files
Coverage Δ
Complexity Δ

...apache/rocketmq/common/message/MessageDecoder.java
78.04% <ø> (ø)
24.00 <0.00> (ø)

...pache/rocketmq/store/dledger/DLedgerCommitLog.java
72.33% <76.41%> (-0.64%)
57.00 <9.00> (+8.00)
:arrow_down:

...tmq/logappender/log4j2/RocketmqLog4j2Appender.java
35.00% <0.00%> (-10.00%)
3.00% <0.00%> (-1.00%)

...e/rocketmq/client/impl/consumer/RebalanceImpl.java
46.61% <0.00%> (-9.17%)
33.00% <0.00%> (-3.00%)

...org/apache/rocketmq/store/ha/WaitNotifyObject.java
75.00% <0.00%> (-7.70%)
10.00% <0.00%> (-1.00%)

...pache/rocketmq/test/listener/AbstractListener.java
66.66% <0.00%> (-7.41%)
9.00% <0.00%> (-1.00%)

...ketmq/client/impl/consumer/PullMessageService.java
75.55% <0.00%> (-4.45%)
9.00% <0.00%> (-1.00%)

...ache/rocketmq/common/stats/MomentStatsItemSet.java
39.13% <0.00%> (-4.35%)
5.00% <0.00%> (-1.00%)

...he/rocketmq/client/impl/consumer/ProcessQueue.java
60.00% <0.00%> (-2.80%)
32.00% <0.00%> (ø%)

...ava/org/apache/rocketmq/filter/util/BitsArray.java
59.82% <0.00%> (-2.57%)
30.00% <0.00%> (-1.00%)

... and 13 more

Continue to review full report at Codecov.

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


Changing the order of the arguments making most optional

Minimizing the count of 'needed' args to construct rocPyDecode, only codec_id needed, all other args are optional with default values.

@essamROCm please resolve the conflicts for this PR. Thanks.

I resolved the conflict, should be able to merge now.


Build fails in util/pcre.h due to missing #include

Describe the bug, including details regarding any error messages, version, and platform.

You can install re2's dev package via your package manager
The issue is because arrow uses outdated re2 if it cannot find one in system I think


Identity stitching not updating traits in single table layout

Summary
jitsu.identify(123456, {email<EMAIL_ADDRESS>mobile: "5556668877"); adds identify events to clickhouse destination, and properly add user_id and context_traits_email, however; only user_id is updated on previous anonymous records. Isn't it more correct to update traits as well ? This is especially important when user_id is not used (or set to null), because we need to query by traits rather than user_id.
System configuration and versions
Latest jitsu 2.8.2
Artifacts (logs, etc)

Hi @ardabeyazoglu
We couldn't reproduce this issue on our setups.
Could you please check the following:

That Identity Stitching is still enabled in connection settings – jitsu 2.8.2 has a bug that could lead to disabling of Identity Stitching on changing Functions setup.
Please check the "API Destinations & Functions Logs" tab in the Data -> Live Events section for the CH connection. It must contain a line like that one: *** events for anonymous id: *** was updated with id fields: {"userId":"***","context":{"traits":{***}}} by Message ID:*** Please check whether all expected traits are mentioned in these messages.
Please confirm that you select from the destination table using FINAL keyword. With Clickhouse we rely on eventual de-duplication of MergeTree engines family.

Thanks, I will check as soon as i have time.


[Enhancement]: Alphabet Learning Game

Is your enhancement request related to a problem? Please describe.➕
Game enhancement

Game is not working.

https://github.com/kunjgit/GameZone/assets/114330097/6969146a-53b3-4532-8960-dfcf8d3386a2
Describe the solution you'd like
Solution steps

Resolve all the conflicts of the js.
Importing all the sound files.
Making functionable all the buttons as mentioned in README file.

Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @Avdhesh-Varshney !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

/assign

Hey @Avdhesh-Varshney ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


Edit the help.xml file.

Copy edit.

@gmaxey Could you update the plugin jar with the latest help file edits from Jennifer? Be sure to bump up the version (just the third digit would be fine for the doc edits).

Done, version 1.4.1


Remove local web server & Carthage

[x] I've read, understood, and done my best to follow the CONTRIBUTING guidelines.

This pull request includes (pick all that apply):

[ ] Bugfixes
[ ] New features
[x] Breaking changes
[x] Documentation updates
[ ] Unit tests
[ ] Other

Summary
Conduit CI has been broken for a long time (since March 2020):

Last successful cron build was 10 months ago
Last successful PR build was also 10 months ago

This is mainly because the local web-server used for unit and integration tests was outdated. As new versions of Ruby and Python have been released, and our systems and CI servers upgraded, the local server stopped running. Quite some good tech-debt we had queued.
Implementation

Remove local web servers

httpbin has been replaced with calls to https://httpbin.org (as we originally had). Video assets have been reduced in size for faster round-trips during testing.
oauth-test-server has been removed and not replaced (a handful of tests have been disabled for now)

Project and workspace files have been removed to simplify the codebase and maintenance efforts.
Carthage support has also been removed, might be added later as XCFramework if there is public demand.
Travis CI has been removed
GitHub Actions have been set up for CI

Test Plan

Run all tests with swift test or from Xcode

@tiltem this subset of tests have been broken for a long time (since CI stopped running).  I've been looking for a replacement for oauth-test-server, but unfortunately haven't found a good solution yet. My intention is to have those tests running later on.


Wildcards are not working as expected

I just want to start off with a big thanks for this library, I had just started on creating a similar extension to test logging, when I stumbled upon this gem. Absolute life-saver.
I did however come across an issue and I'm not sure whether I'm using the extension wrong, or if it's an actual bug.
Here is my Mock-setup:
redisClient.Setup(x => x.SetAsync<BuyIntention>(It.IsAny<string>(), It.IsAny<BuyIntention>(), It.IsAny<CancellationToken>())).Throws(new Exception("Exception thrown"));
The code to log the exception
 _logger.LogError(exception, $"Exception thrown trying to set ID {id} for Aggregate {aggregateId}");
In my test, I've added the following line to my Assert:
logger.VerifyLog(c => c.LogError(It.Is<Exception>(e => e.Message.Contains("Exception thrown")), $"*ID {id}*Aggregate {aggregateId}*"));
Which results in a Moq.VerifyLogException;
Expected invocation on the mock at least once, but was never performed:
Yet, when I remove the wildcards and check for the entire string:
logger.VerifyLog(c => c.LogError(It.Is<Exception>(e => e.Message.Contains("Exception thrown")), $"Exception thrown trying to set ID {id} for Aggregate {aggregateId}"));
The test is succesful.
This is an acceptable work-around for now, however, I would like to use the wildcards, since the specifications only state that we should at least log the ID and the AggregateID the code is trying to store in Redis.

Thank you @Jertimmer for your appreciation and also for submitting this issue.
A fix has been pushed into the 1.1.9 version.


Update OidcConfiguration.java

Why can't you just use 'ClientAuthenticationMethod.parse(auth);' directly with the existing setter? Is this just about adding a convenience method that saves  a few keystrokes or does it provide some other value?

@ror6ax thanks for the PR
@mmoayyed in Shiro (with a shiro.ini file), this is necessary to be able to set the ClientAuthenticationMethod


duplicated errors when validators raise ValidationError

Bug
As a work around for #619 I tried the following
from pydantic import VERSION, BaseModel, Union, validator
from typing_extensions import Literal
print('pydantic version:', VERSION)

class Foo(BaseModel):
    model_type: Literal['foo']
    f: int

class Bar(BaseModel):
    model_type: Literal['bar']
    b: int

class MyModel(BaseModel):
    foobar: Union[Foo, Bar]

    @validator('foobar', pre=True)
    def check_action(cls, v):
        if isinstance(v, dict):
            model_type = v.get('model_type')
            if model_type == 'foo':
                return Foo(**v)
            if model_type == 'var':
                return Bar(**v)
        return v

MyModel(foobar={'model_type': 'foo', 'f': 'x'})

Output:
pydantic version: 0.32.1
Traceback (most recent call last):
  File "test.py", line 31, in <module>
    MyModel(foobar={'model_type': 'foo', 'f': 'x'})
  File "pydantic/main.py", line 275, in pydantic.main.BaseModel.__init__
  File "pydantic/main.py", line 785, in pydantic.main.validate_model
pydantic.error_wrappers.ValidationError: 2 validation errors for MyModel
foobar -> f
  value is not a valid integer (type=type_error.integer)
foobar -> f
  value is not a valid integer (type=type_error.integer)

When validators raise ValidationError the errors are duplicated.
Won't be that common, but should be fixed.

I was being dumb, just that I didn't have whole=True, I've added a test to demonstrate this.


Visual artifacts when using OmniLights with volumetric fog enabled (likely related to clustering)

Godot version: Git 87ae50990
OS/device including version: Fedora 31, GeForce GTX 1080 (NVIDIA 440.100)
Issue description: Visual artifacts can be seen when using OmniLights with volumetric fog enabled. This is likely related to clustering.

Steps to reproduce: Add several OmniLights to a scene with volumetric fog enabled and use freelook to navigate in the scene. You will likely encounter a clustering artifact sooner or later.
Minimal reproduction project: volumetric_fog_clustering_bug.zip

I can still reproduce this in https://github.com/godotengine/godot/commit/a22c7eff0.

Fog Atomospheric.zip
Can reproduce with spot lights too.
https://cdn.discordapp.com/attachments/604227989550530561/780566268427632660/Screen_Recording_2020-11-23_at_2.51.04_PM.mov

atmospheric fog on
auto exposure
geometry as in project file

I think I fixed this in https://github.com/godotengine/godot/pull/53353

I can't reproduce this on 4.0.alpha15, closing.