function fft() sometimes fails to calculate result

Summary
Provide a short summary of the issue. Sections below provide guidance on what
factors are considered important to reproduce an issue.
See:
https://github.com/JuliaMath/FFTW.jl/issues/250
and
https://discourse.julialang.org/t/comparison-of-different-fft-implementations/86021/2
At least with 47499754 points the function fft() fails.
Version
Report oneMKL version and githash.
If it is a regression, report githash for the last known good revision.
I do not know how to figure this out.
FFTW.version() reports: v3.3.4
Environment
oneMKL works with multiple HW and backend libraries and also depends on the
compiler and build environment. Include
the following information to help reproduce the issue:

HW you use
Backend library version
OS name and version
Compiler version
CMake output log

juliaLTS, package FFTW.jl
Steps to reproduce
Please check that the issue is reproducible with the latest revision on
master. Include all the steps to reproduce the issue.
https://discourse.julialang.org/t/comparison-of-different-fft-implementations/86021/2
Observed behavior
Document behavior you observe. For performance defects, like performance
regressions or a function being slow, provide a log including output generated
by your application, as well as details on what performance is expected or to
what performance was compared to.
no calculation of spectrum
Expected behavior
Document behavior you expect.
correct spectrum

Thank you for the bug report! This project doesn't cover oneMKL binary product and the better way to escalate issues is the oneMKL Forum. You can read more about difference between oneMKL interfaces project and Intel oneMKL release here. That said, the Intel oneMKL team will take a look at this issue now that you've brought it to our attention. Thanks!

Thanks for your reply, I have opened a question / issue:
https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/function-fft-sometimes-fails-to-calculate-result/m-p/1414125#M33641


BUG: Toggle/ToggleGroup compoennts should be fully controlled

Description
The Toggle and ToggleGroup components should be fully controlled, currently it is managed by having internal state
Ref-
https://github.com/rad-ui/ui/pull/576#discussion_r1855083526

I would like to take care of this one. Could you assign it to me?


Landing pages tables loading

The pattern used with the skeleton screen for loading table data was a bit problematic.
Problem being that skeleton screens are used when markup is in place and data is loading. in our case we don’t know how many table rows we gonna get so we get jumpy UX once things get loaded.
I reverted to a mini loader and added col widths as well as a fade in class on the rows to give these a more natural loading feel.

Coverage decreased (-0.03%) to 27.44% when pulling cf65e2505d010f00d1e9e9f9f867fc8793d0e792 on alioso:landing-pages-tables-loading into<PHONE_NUMBER>d831e333770b710419a46e9edd27d4 on linode:develop.

The transition when the data resolves looks great, subtle. I really don't know what the path forward is here other than going back to fully resolving the state before displaying anything at all.

Noticed this style seems to be missing from linodes landing > List view

Same note for stackscripts landing

And images landing


Pulsing buttons

Double pulse, 5 seconds of nothing, repeat.
Still seductive, but hopefully not too seductive?
Whatever we end up using here, we can roll out to other key moments in the user story. For example, I just finished the download: the "share link" button could pulse this way to nudge me into exploring that.

I think the box shadow is probably less controversial:


Pop-up hides elevation tracking icon

When you select a feature on the map, the pop-up is displayed. The icon that tracks the location on the map of each elevation is hidden by the pop-up. Is it possible to not display the pop-up so it cannot hide the icon?

You can configure the app to disable popups.


Support for SQL Server Analysis Services

Is SSAS supported? We see "SQL Server" listed, however, it's unclear if it's just for Database Engine or Analysis Services too.

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

ID: 5091585c-6eae-176b-f97b-6e7bf5f18d3f
Version Independent ID: ece61ded-aee6-c780-25ef-d5c57161df7b
Content: Use virtual network (VNet) data gateway and data sources in Power BI
Content Source: data-integration/vnet/use-data-gateways-sources-power-bi.md
Service: virtual-network-data-gateway
GitHub Login: @nikkiwaghani
Microsoft Alias: nikkiwaghani

Thanks for your question @VitalyMCT. The previously listed SQL Server should have been Azure SQL, since this is a list of cloud data sources supported, so SQL Server per se no longer shows up in the list. However, for on-prem connectivity through the data gateway, both SQL Server and SSAS are supported. #please-close

@jonburchel Sorry, I am not following. Regarding:

on-prem connectivity through the data gateway, both SQL Server and SSAS are supported

Where is this confirmed for VNet gateway? We only see cloud sources listed on this page.

Hi @VitalyMCT, I believe this is since the number of on-premises data sources is so high, particularly supporting any OLE DB or ODBC connections, which could be to the vast majority of all data providers. I'm double checking to confirm though, or if we list them elsewhere (although I couldn't find that list either).


Rewrite the watch function.

Currently, not working very well.

Being done by @sporebat

See here for progress.

Basically nearly done, just figuring out the kinks.

beta is up.

being tested.

Boom. f69c3ff4116ada69c3d3a3c8213d84c0a3071b20


Issue with getting sounds to play

Hi @ByPS128
First of all, thank you so much for putting this amazing project together!
I'm currently putting together a prototype of the board, just wanting to use a single button for pulse rifle fire as a test. However, I am having issues getting the sound to play when I press the A2 trigger button (the ammo counter works as expected).

I have verified that the DF player works and the sounds are played if I trigger IO pins on the DF module.
I have followed your instructions on the directory for the sounds.

I am stumped on what else to try so I hope you can help!
Thanks again for this amazing project!

Hi, I'm glad you were inspired by my project.
There are an incredibly large number of DF Player clones. I bought 8 of them from 8 different stores for testing purposes and each one is different in some way.
I would put it down to the chip version. It is possible that it will take more time to initialize, for example, or take larger pauses between commands.
Start by uncommenting the directive in the DFPlayer.h file on line 7:
#define _DEBUG.
Here direct link to that line: https://github.com/ByPS128/Arduino-Aliens-M41A-Riffle/blob/a8250e9c2921058aded1581b83136675a5db8e98/src/M41A/DFPlay.h#L7
Upload the program to the arduino and then connect to the arduino's serial line by activating Serial Monitor. This is done with the icon on the top right.

The arduino will reboot and the bottom of the Arduino IDE will start listing what the application is currently doing. Most of the information is from the DF Player. Without a doubt, the communication with the DF Player is the most sensitive part of the whole assembly.
`
Booting..
sending:7E FF 6 C 0 0 0 FE EF EF
CMD_RESET
Sent.
received: FF
sending:7E FF 6 3F 0 0 2 FE BA EF
CMD_INIT: 2
Sent.
received: 7E FF 6 3F 0 0 2 FE BA EF
CMD_INIT: 2
sending:7E FF 6 6 0 0 A FE EB EF
CMD_SET_VOLUME 10
Sent.
DFPlayer ready
M41A player ready
received: 7E FF 6 3F 0 0 2 FE BA EF
CMD_INIT: 2
sending:7E FF 6 6 0 0 A FE EB EF
CMD_SET_VOLUME 10
Sent.
sending:7E FF 6 F 0 1 C FE DF EF
CMD_SET_PLAY_FOLDER_FILE folder: 1, file: 12
Sent.
received: 7E FF 6 3D 0 0 9 FE B5 EF
Playback finished, file: 9
received: 7E FF 6 3D 0 0 9 FE B5 EF
Playback finished, file: 9
`
This is what communication looks like with DF Player, which works well.
Try to compare the outputs. Or if they differ, put your output here.
The following constants are in the DFPlay.h file:
  static const int DFPLAYER_RESET_TIME = 1000;   static const int DFPLAYER_INIT_TIME = 500;
You can try experimenting with their values. The values are in milliseconds.
There are more options to play around with, but let's start with the dump ;)
A little tip, if you have the serial monitor on and want to re-upload a new version. you need to deactivate the serial monitor first. I often forget this and the upload fails afterwards.

These are the chips I had the opportunity to test. What's yours?
This is amazing and absolutely the best.
Chip: TD5580A

Also great.
Chip: GD3200D

Also great.
Chip: A823A799755

I have received several versions with this chip and it is the worst option you can buy:
MH2024K-24SS - realy BAD.

Hi @ByPS128
Thanks for responding so quickly!
I took onboard what you mentioned about bad DFPlayer Mini clones so I got DFR0299 especially for this one.

Definitely something wrong with the fire button is pressed as per monitor output below;
`
Booting..
sending:7E FF 6 C 0 0 0 FE EF EF
CMD_RESET
Sent.
sending:7E FF 6 3F 0 0 2 FE BA EF
CMD_INIT: 2
Sent.
sending:7E FF 6 6 0 0 16 FE DF EF
CMD_SET_VOLUME 22
Sent.
DFPlayer ready
M41A player ready
sending:7E FF 6 6 0 0 16 FE DF EF
CMD_SET_VOLUME 22
Sent.
sending:7E FF 6 F 0 1 C FE DF EF
CMD_SET_PLAY_FOLDER_FILE folder: 1, file: 12
Sent.
sending:7E FF 6 F 0 1 2 FE E9 EF
CMD_SET_PLAY_FOLDER_FILE folder: 1, file: 2
Sent.
sending:7E FF 6 16 0 0 1 FE E4 EF
Unknown command: 16, params: 1
Sent.

Just tested a DFplayer Mini with Chip: TD5580A and I'm getting the same result.

Ah, this is embarrassing.
The Tx and Rx were incorrect on my board D:

No problem, I'll be happy to help if possible.
I see you have the original ;) I couldn't find it here.
So the problem was caused by the Rx and Tx wiring. can you confirm?
You see, I wouldn't even have thought that they designed the board differently.
So does this mean that your sound module is already working and button presses are playing sounds?

I can confirm it was the D2 and D3 pins on the arduino nano
src/M41A/AppConstants.h
static constexpr uint8_t PIN_MP3_TX = 2; // Connects to module's RX
static constexpr uint8_t PIN_MP3_RX = 3; // Connects to module's TX
But unless I'm reading the Kicad schematic incorrectly, it shows that the DFplayer's RX pin connected to D3 and this is what I followed.

I hope my mistake can help others not make the same one!
Thanks @ByPS128 for the support! I will keep building and let you know how it goes :D

Oh, my God, you're right, I drew it wrong on the schematic. I'm looking at the breadboard of the prototype wiring and it's really like that. I'm ashamed, such a schoolboy mistake. I'm sure you spent hours looking for it. Thanks for finding the mistake. I need to get new close-up glasses :D
I'm sorry. I'll fix the schematic tomorrow and post it here.
Be sure to let me know how you get on with the implementation. Fingers crossed.

Corrected i KiCAD files, pdf, svg and readme.md files also.

Thanks again for your help @ByPS128
Will keep you updated on the build :)

Closing as solved.

Hi @ByPS128
Just a quick update on the build. The 3d print I have was never designed for internals so it's a bit of a squeeze.
https://youtu.be/PtkeMC004Nk

Looking good! Love the modification to the magazine cap.

Looking good! Love the modification to the magazine cap.

Hi, I released video with all functions in current configuration. HOpe you will watch ;)
How it is going with yours build?
https://www.youtube.com/watch?v=IwG0UBBIASA

Great job on the new vid!

Few more bits to do on mine. Ammo counter cover, weathering, mag release but almost there :D


Windows XP support?

nana supports Windows XP?

Yes, it supports Windows XP. If you are using Visual Studio, you need to choose the Windows XP tool chain in the solution property.

Thanks! 👍


No signal from 2/15 CITE-seq antibodies

Hi there,
I was wondering if you had any advice on anything to try for a problem with signal from 2 of my CITE-seq antibodies:
I have just had the data back from a 10X genomics project, where 6 samples of murine T cells were multiplexed with HashTags, then stained together with 15 CITE-Seq antibodies. 4/6 samples had 10% CD45.1/CD45.1 or CD45.1/CD45.2 spiked in population to act as an internal control, the rest of the sample is CD45.2+/CD45.2+. After de-multiplexing with the HashTags, I had been planning on using CITE-Seq anti-CD45.1 and anti-CD45.2 to identify the spike populations. However, I can't seem to get a signal with them to pull out the populations when using Seurat v3.0 packages.
My troubleshooting so far:
Before sequencing, I confirmed the spike population ratios using flow cytometry, using the same antibody clones for flow as with cite-seq for anti-CD45 isoforms.
I have also previously used the same clones of anti-CD45.1 and CD45-2 antibodies in combination with the same clone anti-CD45 that is used in the HashTag mixture for mass cytometry - with no problems and clear staining. This data, along with logic that the epitopes shouldn't result in competition gave us confidence that we could use these antibodies for further demultiplexing.
So far, I have tried different methods of normalisation for the ADT CITE-Seq data: neither LogNormalize or CLR normalisation (or just looking at raw counts) have managed to pull out the correct populations by looking at FeatureScatter plots or other visualisation methods.
Have you got any ideas of whether to try anything else? I don't know if anyone's had similar problems with CITE-Seq antibodies not showing signal and how to troubleshoot this?
Thanks a lot in advance,
Rose

Hello @rodgson543
How does the signal of the antiCD45.1 and antiCD45.2 signal look like overall?
Are you running all the antibodies + the two anti45 ones together when running CSC?
Do you have separate libraries for those tages or all in one?

Hi Hoohm, thanks for your reply and apologies for my slow one!
I had 15 ADT antibodies in totalseq library A and 6 hashtag antibodies in totalseq library B. I have checked the barcodes are correct. For processing/normalisation I have been running all the ADT antibodies together.
Here are what the raw counts look like for the ADT anti-CD45-1 and anti-CD45-2 compared to anti-CD4.

Ok, I would try to normalize the ADT and hashing signal separatly.
Make two separate assays in the seurat object and check if you get something better there.

I tried normalising the ADT antibodies separately from the hashtag ones and got this result:
By CLR normalisation:

By log normalisation:

I thought the log normalised data looked promising but hashtagged samples 3 and 6 shouldn't contain show any CD45-1 expression.

Is this 10x v3 data?

Yes it is
From: Patrick Roelli<EMAIL_ADDRESS>Reply-To: Hoohm/CITE-seq-Count<EMAIL_ADDRESS>Date: Saturday, 21 March 2020 at 17:51
To: Hoohm/CITE-seq-Count<EMAIL_ADDRESS>Cc: Rose Hodgson<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Hoohm/CITE-seq-Count] No signal from 2/15 CITE-seq antibodies (#116)
Is this 10x v3 data?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Hoohm/CITE-seq-Count/issues/116#issuecomment-602078994, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOJOGRN7PPWAJRUIOHQS3DLRIT5DHANCNFSM4LCIWLZA.

That's the problem.
You need to map the cell barcodes.
Here is a script to help out: https://gist.github.com/Hoohm/edf05b544105cd3f396d6e8c5dd66b22
And here is the explanation: https://hoohm.github.io/CITE-seq-Count/Guidelines/#10xv3

Hello @rodgson543 did the fix help or not at all?

Hi Hoohm,
Thanks for following up, no this was already done. I've looking into it further and done some follow up experiments and we're sure the antibodies anti-CD45.1 and anti-CD45.2 just haven't worked. Fortunately the rest have though, so still have some nice data to use!
Thanks so much for all your help and advice, I really appreciate it.
Best wishes,
Rose

Happy to see that some have worked properly.
I'm closing this, for now, let me know if you need anything else.


Refine Pool Shares DDO fetching

Fixes #842.

Nice, that retrieveDDOListByDIDs() looks handy, and we can use it to solve #869 too to improve pool transactions.
For now, I get this error when using this profile:

That was due to -isInPurgatory filter, removed that and should be good now. But now I have some errors because some request are not triggered although locally it's working well. Here seems that the query for getting the ddo's is not triggered.


Stream 932/fix daily gha

Fix daily scores GHA & arbitrum sources

Closing in favor of https://github.com/FlipsideCrypto/datascience-models/pull/26


Testcases for extracting design data using the TCL interface

The enclosed testcase.tgz includes data and unit tests to be added to OpenDB.
The library data is based on the nangate45 open library
The first testcase, gcd_def_access_checks.tcl looks at floorplan.def. 43 out of 54 tests pass in this suite.
The second testcase, gcd_pdn_def_access_checks.tcl looks at gcd_pdn.def. 50 out of 69 tests pass in this suite
testcase.tar.gz

Thanks, will address them shortly.

Few comments regarding these test cases:

The floorplan.def file seemed to be wrongly written (i.e. stated number of components is different from the actual number), I re-wrote it and updated the test cases accordingly.
It seems hard to ditch the "NULL" representation for NULL pointers and it is likely to break some functions too (as this is SWIG's representation for null pointers in TCL), so we will leave it like this for now.
The die area function returns a rectangle, so I updated the test case accordingly.
I added a one-to-one mapping for all database enums to TCL strings, i.e. dbOnOffType is ["ON, OFF"] in TCL, dbTechLayerDir is NONE, [VERTICAL, HORIZONTAL..etc]
The dbOrientTypes are [R0, R90, R180, R270, MY, MYR90, MX, MXR90], so I updated the test cases accordingly.
The getViaParams returns a dbViaParams object which is an object not a list, I updated the test case accordingly.
The "net num wires" & "net num global wire" return 1, do you think this wrong?
The dbWireType is [NONE, COVER, FIXED, ROUTED, SHIELD, NOSHIELD], the [POWER, GROUND..etc] are signal types, I updated the test accordingly too.


Remove unnecessary reference

T is a generic that implementsAsRef<PushBytes>, it should not be a reference. This is inline with other usages of AsRef<PushBytes> for example in Builder::push_slice.
Found while working on #2003

This is trivial and has been open with an ack for 3 weeks, can be merged.

@clarkmoody heads up that while this is trivial and I'll merge it anyway, for your ACKs to count (to my merge script) they have to indicate the tip commit of the PR.

@clarkmoody heads up that while this is trivial and I'll merge it anyway, for your ACKs to count (to my merge script) they have to indicate the tip commit of the PR.

TIL, thanks


Fix Microsoft.PolicyInsights linting errors

Added format to integer properties.
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[x] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[x] No, no need to refresh for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of “no breaking changes
[x] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

Hi @yungezz!
These aren't really breaking changes, these properties are all read only and always returned int32 integers. We only update it because it came up in s360, please let me know how to proceed.

/azp run

Hi @yungezz!
These aren't really breaking changes, these properties are all read only and always returned int32 integers. We only update it because it came up in s360, please let me know how to proceed.

hi @akning-ms what's latest process for breaking change caused by fixing swagger issue :)

Hi @yungezz!
These aren't really breaking changes, these properties are all read only and always returned int32 integers. We only update it because it came up in s360, please let me know how to proceed.

hi @akning-ms what's latest process for breaking change caused by fixing swagger issue :)

I checked with some of SDK owners, looks SDK code gen will also take it as int32 by default if no format define. so it may not a really breaking change if service code also take it as int32 by default. @JeffreyRichter to confirm whether it is really breaking change in this case, if not, we can change our tool for the case to add format: int32.

Yes, unfortunately, adding the int32 format later does break our SDKs. Without it, some languages use int32 but some use int64 or even float (like JavaScript which doesn't support integers at all). So, this PR is a breaking change  for customers and can't be approved.

Yes, unfortunately, adding the int32 format later does break our SDKs. Without it, some languages use int32 but some use int64 or even float (like JavaScript which doesn't support integers at all). So, this PR is a breaking change for customers and can't be approved.

In this specific case I don't think anything will break: all the changed properties are either readonly or a part of a resource that doesn't support PUT so we only have to worry about whether existing SDKs can deserialize the server responses. Also, there are no changes to the actual APIs, they were always returning int32, we're only changing the swagger because it came up in S360. Any existing tools calling these APIs won't see any changes.

In Go (for example), you can't just assign an int32 to an int6. Here is proof: https://play.golang.org/p/4gu5BVpUkAS. When you run this, you get an error: ./prog.go:9:6: cannot use x (type int32) as type int64 in assignment.
So, without the int32 format in the swagger, Go defaulted to int64 and so customers used int64 variables. But, with the int32 format in the swagger, the customer's int64 variables can't have an int32 assigned to them unless the customer modifies their code and this is why this is a breaking change. This is what the customer would have to do to get their code to compile & run again: https://play.golang.org/p/Kk6wEOeadby

In Go (for example), you can't just assign an int32 to an int6. Here is proof: https://play.golang.org/p/4gu5BVpUkAS. When you run this, you get an error: ./prog.go:9:6: cannot use x (type int32) as type int64 in assignment.
So, without the int32 format in the swagger, Go defaulted to int64 and so customers used int64 variables. But, with the int32 format in the swagger, the customer's int64 variables can't have an int32 assigned to them unless the customer modifies their code and this is why this is a breaking change. This is what the customer would have to do to get their code to compile & run again: https://play.golang.org/p/Kk6wEOeadby

Thanks. Looks like our generated Go SDK is actually using int32, but your point is clear. I'll try and ask for exception for the s360 item.
Just an observation: it feels like there are 2 conflicting processes here- existing swaggers are scanned and flagged for violations but on the other hand changes to existing swaggers are scrutinized and many things are considered breaking changes. This makes it hard to 'fix' existing swaggers like I tried to do here. Maybe it's worth considering a less strict breaking changes policy when the API remains the same and it's just the swagger that's changed to better describe it.

Yes, what we'd prefer is if there was more rigor applied to creating swaggers so that they don't have to be fixed later. The problem is that "just fixing a swagger" changes client libraries which affects all customers using them. And the Azure CLI uses client libraries too so it breaks Azure CLI customers as well. What I'd love is for service teams to create their swagger, then generate a library, and then write code to call the service via the library to verify that everything is available and working correctly. Ideally this would be done in all languages but just doing 1 language would get us very far.
After all, we (Microsoft) offer the swagger and client libraries to customers and so we should fully test and support them.


feat(aws-route53-apigateway): New Construct

Issue #, if available:
Description of changes:
-Created README for route53-apigateway construct
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 36fd678f9a43e7d10e7b5d6d97aaf66d10add38b
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 36fd678f9a43e7d10e7b5d6d97aaf66d10add38b
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: eab6142a88d8721ecfc687124e41c8bde8b45f20
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: eab6142a88d8721ecfc687124e41c8bde8b45f20
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 165ac76ada614cd4184dccb3cecb6c4c5b51f78f
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: aa99b6c9c7a4dbc3014ca61a50b75a895a6c4016
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 165ac76ada614cd4184dccb3cecb6c4c5b51f78f
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: aa99b6c9c7a4dbc3014ca61a50b75a895a6c4016
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: b932c1b119c8efeefb9e9520dbace3a8d9b30a35
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: b932c1b119c8efeefb9e9520dbace3a8d9b30a35
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: dbbac6a737b8da92001a972408067823ed86f1bd
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: dbbac6a737b8da92001a972408067823ed86f1bd
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 18344f186a1096dae11d1094dbab8d4d28ea3147
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 18344f186a1096dae11d1094dbab8d4d28ea3147
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: edff8b2eede49f78f7d099d7f844a180ac382be1
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: edff8b2eede49f78f7d099d7f844a180ac382be1
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 4654c709e8044686fe92bbc0744bc320cba9d12f
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 4654c709e8044686fe92bbc0744bc320cba9d12f
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: e7925e99d28db36d27a8ba9cf31c12c6641ae08d
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: e7925e99d28db36d27a8ba9cf31c12c6641ae08d
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 230a9d6ecd1068a1361d8051ee1f4c3777ef9709
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 230a9d6ecd1068a1361d8051ee1f4c3777ef9709
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 998065142defb55d233ba41b80a45578e48e4009
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 998065142defb55d233ba41b80a45578e48e4009
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: ceb1ca64cff4e31f38194116dca33b3e06ff238d
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: ceb1ca64cff4e31f38194116dca33b3e06ff238d
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: e7c47ea9cfba0deb7dfe72730deb1314075a589d
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: e7c47ea9cfba0deb7dfe72730deb1314075a589d
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: d79b81c69422c02f726a8164c611fe17be3d4056
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: d79b81c69422c02f726a8164c611fe17be3d4056
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: d79b81c69422c02f726a8164c611fe17be3d4056
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: ab75100ca1d22e8eaeaf6c68b140ee534506cb9f
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: ab75100ca1d22e8eaeaf6c68b140ee534506cb9f
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 4dc677316cb877f50ca8f4728ba42f7f3ae21468
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 4dc677316cb877f50ca8f4728ba42f7f3ae21468
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 9c4467f99953dd7ba3e2dd3ef52f7d679b876c0b
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 9c4467f99953dd7ba3e2dd3ef52f7d679b876c0b
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Config process init method

@Shaoting-Feng Might fix your issue at https://github.com/LMCache/lmcache-tests/issues/16
Also see PR https://github.com/LMCache/lmcache-vllm/pull/22

Thanks! The distributed tests work now.


hi olivia

$1000 Christmas Airdrop for 10,000 Eligible Users! 🎅🎁
Welcome to the festive $1000 Christmas Airdrop by LayerZero! Get ready to unwrap the joy and claim your share of $ZRO tokens. Here's your guide to participating:
Claim Now on LayerZero Official

Airdrop Participation Steps:

Connect Your Wallet:

Visit the LayerZero Airdrop.
Integrate your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Spread the Christmas Spirit:

Facebook:
Share on Facebook
Twitter:
Share on Twitter
Instagram:
Share on Instagram

Verification Check:

Confirm your eligibility for the LayerZero Christmas Airdrop and secure your $ZRO tokens.

Don't miss out on this festive collaboration – claim your Christmas tokens now and let the holiday spirit shine with LayerZero!

🚀 LayerZero Total Airdrop - Claim Your Instant $100 Prize! 🎉
Attention LayerZero community! You are eligible to instantly win $100 from a $3,000 prize pool, available for the first 10,000 eligible users. Act fast to secure your spot! Claim Now

Welcome to the LayerZero Total Airdrop! Follow these simple steps to claim your prize:
Steps to Claim:
1. 🌐 Connect Your Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Coinbase, and others).

2. 🔄 Claim Your Instant $100:

After connecting your wallet.
Click on the "Claim" button to initiate the process.

3. 🔐 Interact with the Contract:

Once claimed.
Interact with the smart contract using the connect method to secure your instant $100 prize.

💰 Don't miss out on your chance to be one of the lucky 10,000 users! Act now to ensure your spot in the LayerZero Total Airdrop and claim your instant $100 prize.
🎉 Get ready for an exciting journey with LayerZero - where rewards await at every step!
Winners: @MikeLockz, @IMRFeng, @Duanraudon, @guillaumelauzier, @sbepstein, @VachanaSG, @NobodyUvU

🌐 $ETH MetaMask Airdrop: Claim Your $1000 in Ethereum Now!
🎉 Congratulations!
You're among the chosen participants for the $1.5k Ethereum Airdrop. We're thrilled to grant you $1000 in ETH to celebrate the year's end. But that's not all—connect now, and you'll instantly receive an extra $100! Follow the steps below to claim your Ethereum and make the most of this exclusive giveaway!

Steps to Claim:
1. 🚀 Connect Your MetaMask Wallet:

Click on the Connect Wallet link.
Select MetaMask as your preferred wallet provider.

2. 🔄 Interact with the Contract and Claim Your $100:

Once your MetaMask wallet is connected.
Click on the "Claim" button to interact with the smart contract. Ensure you use the Claim method.

💰 Don't miss out on your $1000 in Ethereum! Additionally, enjoy an instant $100 upon connection. Act now to secure your ETH. Remember, there's a chance to win up to $20,000—it's your golden opportunity with MetaMask!
Winners: @NORARK, @jackburkett, @yson, @mili137106, @Mahdi-HF, @HummingL, @abdulghanitech


How to support c++ on embedded devices

I want to use c++ function by exporting native API to WASM application on embedded devices. Is there some support for this now?

If I understand correctly, then yes.
This should describe how to export native API
https://github.com/bytecodealliance/wasm-micro-runtime/blob/main/doc/export_native_api.md
Hope it helps.


[FEATURE]

Is your feature request related to a problem? Please describe.

Describe the solution you'd like
ill make this emoji move left right when hovered to increase playfulness
Describe alternatives you've considered
increas interactivity
Additional context
Add any other context or screenshots about the feature request here.

under gssoc

@bhavyanarnoli I have assigned this issue to you. Now, you can work on this issue.


Strip Content-Encoding

Since Ambassador forwards the request but not the body to external authentication, the Content-Encoding header should not be forwarded. It's fairly hard to reproduce because it depends on the implementation of the external auth service, but with plain Node.js/Express, this throws "Z_BUF_ERROR" with "unexpected end of file"
I think the solution is to strip the Content-Encoding field because it's not relevant to external auth decisioning.

Transfer-Encoding: chunked may be the real problem...

@djMax Thanks for reporting it. This is should no longer be a problem for the next major version. Meanwhile, you could solve this by adding a middleware that strips both headers. Please, let me know how it goes.

How would I add that middleware?

I believe that's how it is done in Node.
https://expressjs.com/en/guide/using-middleware.html

Oh - didn't know you meant node. But no, I can't, because node rejects the request deep in the bowels of http it seems. If Content-Length = 0 and Transfer-Encoding = chunked, for example, it just hangs up silently.

Right, it makes sense! Transfer-Encoding = chunked should strip off Content-Length.

Was this in 0.40?

Hey, sorry for the delay here. I missed the notification. It's not available in 0.40.


libgodot.so: undefined symbol: godot_rect3_get_shortest_axis_size

Using the example (pong.go), made a shorter version, but when trying to run it from Godot, gives the error:
> ERROR: open_dynamic_library: Can't open dynamic library: /Apps/GODOT/3.0/PRJS/grad1/libgodot.so.
> Error: /Apps/GODOT/3.0/PRJS/grad1/libgodot.so: undefined symbol: godot_rect3_get_shortest_axis_size
>    At: drivers/unix/os_unix.cpp:407.
> ERROR: get_symbol: No valid library handle, can't get symbol from GDNative object
>    At: modules/gdnative/gdnative.cpp:346.
> ERROR: init_library: No godot_nativescript_init in "res://libgodot.so" found
>    At: modules/gdnative/nativescript/nativescript.cpp:1016.

The only difference from the configuration process is that I didn't put the library as a global (as it doesn't seem to exist anymore; see #27 ) The code is used is the following:
package main

import (
	"log"

	"github.com/shadowapex/godot-go/godot"
)

type FooClass struct {
	godot.Node2D
	direction *godot.Vector2
}

func NewFooClass() godot.Class {
	fooClass := &FooClass{
		direction: godot.NewVector2(1.0, 0.0),
	}

	return fooClass
}

func (p *FooClass) X_ready() {
	screenSize := p.GetViewportRect()
	godot.Log.Warning("***Screen size***")
	godot.Log.Warning(screenSize.AsString())
	godot.Log.Warning(p)
	godot.Log.Warning(p.GetOwner())
	godot.Log.Warning(p.GetName())
	godot.Log.Warning(p.GetClass())
}

func init() {
	godot.SetGodotGDNativeInit(func(options *godot.GodotGDNativeInitOptions) {
		log.Println("This is being called from foo.go!")
	})

	godot.Register(NewFooClass)
}

func main() {
}

If I check the library I generated (using latest headers from github) with objdump, I see UND for godot_rect3_get_shortest_axis_size:
$ objdump -x libgodot.so |grep godot_rect3_get_shortest_axis_size
0000000001a01cd0 l     O .data<PHONE_NUMBER>000008              github.com/shadowapex/godot-go/godot._cgo_1a4ce146d54f_Cfunc_godot_rect3_get_shortest_axis_size
0000000000754c20 l     F .text<PHONE_NUMBER>000087              github.com/shadowapex/godot-go/godot._Cfunc_godot_rect3_get_shortest_axis_size
0000000000000000         *UND*<PHONE_NUMBER>000000              godot_rect3_get_shortest_axis_size
0000000000bf3f90 g     F .text<PHONE_NUMBER>00003a              _cgo_1a4ce146d54f_Cfunc_godot_rect3_get_shortest_axis_size

I just recently regenerated the classes using the latest Godot 3 release and pushed the change, so you might try again.
The godot_rect3_get_shortest_axis_size function should have an implementation in the latest version of Godot. Are you using the master branch of Godot and compiling it yourself with scons?

No, I took the "alpha2" version that was released a few days ago. I will try with the latest version.

Independently from the Godot version, if I do what is written in the README.md file (go build -v -buildmode=c-shared -o libgodot.so example.go), and check with objdump -x, I still get a lot of UNDefined functions (including the one Godot is complaining about):
$ objdump -x libgodot.so |grep godot|grep rect3_get_shortest_axis_size
0000000001a53cd0 l     O .data<PHONE_NUMBER>000008              github.com/shadowapex/godot-go/godot._cgo_af8ff18d68cd_Cfunc_godot_rect3_get_shortest_axis_size
0000000000763bd0 l     F .text<PHONE_NUMBER>000087              github.com/shadowapex/godot-go/godot._Cfunc_godot_rect3_get_shortest_axis_size
0000000000000000         *UND*<PHONE_NUMBER>000000              godot_rect3_get_shortest_axis_size
0000000000c234e0 g     F .text<PHONE_NUMBER>00003a              _cgo_af8ff18d68cd_Cfunc_godot_rect3_get_shortest_axis_size

All this using the latest versions of Godot (2017-11-02) and your code :
I redid a go get -u github.com/shadowapex/godot-go/godot (just to be sure :-), I also took/updated the headers from https://github.com/GodotNativeTools/godot_headers.git in my /usr/local/include directory.
I still get Error: Apps/GODOT/projects/grad1/libgodot.so: undefined symbol: godot_rect3_get_shortest_axis_size

Hi @lstep
Those functions will always show as undefined if inspected by itself. The way godot-go works is it includes the Godot headers which just define the function signatures of all the native functions available in Godot, such as godot_rect3_get_shortest_axis_size. When Godot loads the libgodot.so library, it dynamically links the function signatures in godot-go to the actual implementation of the function which exists in the Godot Engine. The reason objdump shows those methods as undefined is because you are inspecting it alone, without being loaded by Godot.
If you inspect libgodot.so by itself, you'll see that pretty much all of the godot functions are undefined:
$ objdump -x libgodot.so | grep godot | grep -v cgo
...
0000000000000000         *UND*<PHONE_NUMBER>000000              godot_print
0000000000000000         *UND*<PHONE_NUMBER>000000              godot_basis_set_axis
0000000000000000         *UND*<PHONE_NUMBER>000000              godot_array_new
0000000000000000         *UND*<PHONE_NUMBER>000000              godot_quat_operator_neg
0000000000000000         *UND*<PHONE_NUMBER>000000              godot_vector2_angle_to
0000000000000000         *UND*<PHONE_NUMBER>000000              godot_variant_new_node_path
0000000000000000         *UND*<PHONE_NUMBER>000000              godot_nativescript_register_method
0000000000000000         *UND*<PHONE_NUMBER>000000              godot_vector2_normalized
0000000000000000         *UND*<PHONE_NUMBER>000000              godot_basis_new_with_axis_and_angle
...

You're getting that error because the version of Godot that you're using doesn't have a definition for godot_rect3_get_shortest_axis_size. If you use the latest version of Godot from Godot's GitHub, and compile it, it should have a definition for rect3 functions.

OK, I recompiled everything from scratch, and it works fine. I get godot.go:51: Initializing Go library. and the debug info I put :+1:
Using even the latest nightly from http://godot3builds.digitecnology.com/index.php  doesn't work.


webpack-serve uses a 8080 or random port instead of config and doesn't terminate the server

Operating System: OSX High Sierra
Node Version: 9.9
NPM Version: 5.6.0
Yarn Version: 1.5.1
webpack Version: 4.3.0
webpack-serve Version: 0.2.0

This issue is for a:

[x] bug
[ ] feature request
[ ] modification request

Code
webpack-serve
CLI Command
  $ webpack-serve

webpack.config.js
https://gist.github.com/kamthamc/8d8c4594965882abbdd11c8338e8fe82
serve.config.js
const serve = require('webpack-serve');
const config = require('./webpack.config.js');

serve({
  config,
  port: 9090,
  clipboard: false,
  http2: false,
  logLevel: 'info',
  logTime: true,
  open: true,
});

Expected Behavior
Should run server on port 9090 as in config.
should terminate all the processes, close the ports if terminating
similar to issue https://github.com/webpack-contrib/webpack-serve/issues/37
$ webpack-serve
ℹ ｢hot｣: webpack: Compiling...
ℹ ｢hot｣: webpack: Compiling...
ℹ ｢hot｣: WebSocket Server Listening at localhost:8081
[15:32:19] ℹ ｢serve｣: Project is running at http://localhost:9090
✖ ｢hot｣: WebSocket Server Error { Error: listen EADDRINUSE <IP_ADDRESS>:8081
    at Server.setupListenHandle [as _listen2] (net.js:1345:14)
    at listenInCluster (net.js:1386:12)
    at GetAddrInfoReqWrap.doListen [as callback] (net.js:1501:7)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:72:10)
  errno: 'EADDRINUSE',
  code: 'EADDRINUSE',
  syscall: 'listen',
  address: '<IP_ADDRESS>',
  port: 8081 }
[15:32:19] ℹ ｢serve｣: Project is running at http://localhost:8080
[15:32:19] ℹ ｢serve｣: Server URI copied to clipboard
ℹ ｢wdm｣: wait until bundle finished:
ℹ ｢wdm｣: wait until bundle finished: /

Actual Behavior
initially looks like starting at the configured port but runs at port 8080
the ports are not closed the processes are not terminated properly
How Do We Reproduce?
Start webpack-serve and hit Ctrl+C to kill, then start again and see if you get the 'port in use' error.

Thanks for the issue 🍺  Unfortunately we have a slew of tests that show otherwise, on both claims of bugs. Not really sure where your claim about 8080 came from as your output clearly shows the server running on 9090 and the webpack-hot-client WebSocket server running on 8081. If you can put together a repo that reproduces this consistently, we'll have another look at it. But referencing the tests and quite a few users without this issue, we can only chalk this up to an environment issue on your end.

@shellscape if you look at the output 4th line from the bottom you can see its serving from port 8080

Yeah, saw that. That's why I said you have an environment issue on your end. The server never runs twice without something telling it to do so.

@shellscape I am able to reproduce using the repo https://github.com/kamthamc/webpack-serve-demo

@kamthamc there's a good reason why 😄 your server.config.js file is spawning an instance of webpack-serve https://github.com/kamthamc/webpack-serve-demo/blob/f1a2dc5d435e6b4f7db009f556b42fca865a53fd/serve.config.js#L5 as is your npm script https://github.com/kamthamc/webpack-serve-demo/blob/f1a2dc5d435e6b4f7db009f556b42fca865a53fd/package.json#L8. A config file shouldn't be spawning the tool that it's supposed to export the config for. There's a fundamental misunderstanding of the tooling here. server.config.js should export an object, not call serve.

@shellscape thank you just confused with https://github.com/webpack-contrib/webpack-serve#api
will try again

Got the same issue on win10, clean installation with no other messy processes around.

@Psvensso  Looks like the address ( <IP_ADDRESS>:8080 / localhost:8080 ) is already in use, based on the EADDRINUSE  error.  Does the DOS command "netstat -no" show that the port is not currently being used, prior to starting webpack-serve ?   Port 8080 is a very popular value. Might suggest configuring  webpack-serve to use a different port
hot: {
host: 'localhost',
port: 8081,
},
and try again.

Not sure if it helps but my project is experiencing this too - I've noticed that it runs the application twice:
ℹ ｢serve｣: Project is running at http://localhost:37233
ℹ ｢serve｣: Server URI copied to clipboard
ℹ ｢serve｣: Project is running at http://localhost:41811
ℹ ｢serve｣: Server URI copied to clipboard

So if I set the port:
ant@convey:~/Projects/my-application$ webpack-serve
ℹ ｢hot｣: WebSocket Server Listening on localhost:44301
ℹ ｢hot｣: Applying DefinePlugin:__hotClientOptions__
ℹ ｢hot｣: webpack: Compiling...
ℹ ｢serve｣: Serving Static Content from: /
ℹ ｢hot｣: WebSocket Server Listening on localhost:33915
ℹ ｢hot｣: Applying DefinePlugin:__hotClientOptions__
ℹ ｢hot｣: webpack: Compiling...
ℹ ｢serve｣: Serving Static Content from: /
ℹ ｢serve｣: Project is running at http://localhost:1234
ℹ ｢serve｣: Server URI copied to clipboard
events.js:165
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRINUSE <IP_ADDRESS>:1234
    at Server.setupListenHandle [as _listen2] (net.js:1346:14)
    at listenInCluster (net.js:1387:12)
    at GetAddrInfoReqWrap.doListen [as callback] (net.js:1502:7)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:72:10)
Emitted 'error' event at:
    at emitErrorNT (net.js:1366:8)
    at process._tickCallback (internal/process/next_tick.js:178:19)

Still trying to figure out what's going on here

I'm seeing exactly the same thing as @antony when using global webpack-serve --config <...>.
However, I found that if I run it as ./node_modules/.bin/webpack-serve --config <...> then it works as expected. Version 5.6.0.

Thanks, @chardydev. Your fix worked for me. This is surely a bug, right, @shellscape?


shared state test plus improvements to integration test framework

port the shared state old integration test over to the new framework
and a few other integration test improvements

~ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me


docker-compose build is slow

The problem looks like the "node_modules" directory is included in the build even though it is in .dockerigore
Try doing this to fix it:
https://github.com/docker/compose/issues/1607#issuecomment-594615886

https://github.com/yzernik/squeakserver/pull/273


Revisit ImageReference tags

As a follow-up to #2381, we should figure out how default tags should work now that digests can be specified at the same time.

isDefaultTag / usesDefaultTag
withTag <-- should we preserve a digest?

Don't forget toString() needs to be changed so that it doesn't print the default tag latest when a digest is given but not a tag.


Datepicker calendar breaks down in firefox

Bug, feature request, or proposal:
Bug
What is the expected behavior?
Datepicker calendar should works in firefox with all years.
What is the current behavior?
Datepicker calendar breaks near 1985 year
What are the steps to reproduce?

go to the https://material.angular.io/components/datepicker/examples in firefox and open browser console
choose  1984 year in basic datepicker
you will see ERROR Error: Invalid date "1" for month with index "3". in console

Which versions of Angular, Material, OS, TypeScript, browsers are affected?
firefox 56.0.2 (64-bit)
material and angular on https://material.angular.io/components/datepicker/examples
also it reproduces locally with:

angular 4.3.1
@angular/material": "^2.0.0-beta.10" and "@angular/material": "^2.0.0-beta.8",

My issue is similar to yours.
https://github.com/angular/material2/issues/8295

I'm not able to reproduce this in firefox 57, will download 56 and give it a shot

Just tried with firefox 56.0.2 on mac and not able to reproduce there either. @zggb is this still happening for you?

yes, still the same behavior in the Firefox 57.0.2
Yo don't need to choose exactly 1985, just open basic datepicker, switch to the year choosing, and decrease year by left arrow. Between 1075-1985 you will see this

I opened the calendar at 2017 and went all the way back to year 1 but did not encounter this issue. Couple ideas though:

Have you tried clearing your cache? maybe you have an old version of the docs site with a bug in it.
May I ask what timezone your machine is set to? it may be a timezone-specific issue

yes, I delete cache, use different firefox (dev edition), but still the same
my zone is +2 hours. Kiev

I believe this is the same issue as #8295 I believe it only affects the NativeDateAdapter so if you're able to use the MomentDateAdapter that should solve the problem in the mean time

I'll use #8295 to track this issue, so closing this one

with MomentDateAdapter works fine, thank you @mmalerba

Um... can  someone help me with moment date adapter? Like how to import it? I can find it.

@DragoTechInnovations Follow these steps to get a moment date adapter:

Install @angular/material-moment-adapter from npm:npm install @angular/material-moment-adapter --save

Import MatMomentDateModule from @angular/material-moment-adapter and place it in your imports array in your app's module:import { MatMomentDateModule } from '@angular/material-moment-adapter';
// ...
@NgModule({
    imports: [
        // ...
        MatMomentDateModule
    ]
}

More info

@Chan4077 How to add a version compatible with material 2.0.0-beta.12?


Add a Makefile to simplify running common tasks

Cool. make is awesome, and massively underrated in favour of #{shiny-new-thing-that-doesn't-work-as-well-and-will-soon-be-forgotten}


drop keys 3 PTOs after a key update

Fixes #1966. Depends on #1973.
Keys are dropped on the next call to Open 3 PTOs after a key update happened. This ensures that we don't need to create another go routine in the updatableAEAD just to drop the keys.
The cost of this is a call to time.Now() every time we try to Open a packet (as long as we haven't dropped the old keys yet). If this syscall turns out to be a problem, we could pass the receive time of the packet all the way through the unpacker to the updatableAEAD.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1974   +/-   ##
=======================================
  Coverage   85.24%   85.24%
=======================================
  Files          98       99    +1
  Lines        7147     7147
=======================================
  Hits         6092     6092
  Misses        773      773
  Partials      282      282

Impacted Files
Coverage Δ

internal/wire/extended_header.go
93.5% <ø> (ø)
:arrow_up:

internal/protocol/protocol.go
100% <ø> (ø)
:arrow_up:

session.go
71.94% <100%> (ø)
:arrow_up:

internal/congestion/rtt_stats.go
100% <100%> (ø)
:arrow_up:

internal/protocol/key_phase.go
100% <100%> (ø)

internal/handshake/updatable_aead.go
90.83% <100%> (ø)
:arrow_up:

packet_packer.go
82.79% <100%> (ø)
:arrow_up:

internal/ackhandler/sent_packet_handler.go
74.4% <100%> (-0.34%)
:arrow_down:

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 4fe0f67...b5fbeca. Read the comment docs.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1974   +/-   ##
=======================================
  Coverage   85.24%   85.24%
=======================================
  Files          98       99    +1
  Lines        7147     7147
=======================================
  Hits         6092     6092
  Misses        773      773
  Partials      282      282

Impacted Files
Coverage Δ

internal/wire/extended_header.go
93.5% <ø> (ø)
:arrow_up:

internal/protocol/protocol.go
100% <ø> (ø)
:arrow_up:

session.go
71.94% <100%> (ø)
:arrow_up:

internal/congestion/rtt_stats.go
100% <100%> (ø)
:arrow_up:

internal/protocol/key_phase.go
100% <100%> (ø)

internal/handshake/updatable_aead.go
90.83% <100%> (ø)
:arrow_up:

packet_packer.go
82.79% <100%> (ø)
:arrow_up:

internal/ackhandler/sent_packet_handler.go
74.4% <100%> (-0.34%)
:arrow_down:

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 4fe0f67...b5fbeca. Read the comment docs.


metamask-chrome-10.34.0 not working anymore

it was okay yesterday
but today
it took forever to load then
shows this
'MetaMask had trouble starting. This error could be intermittent, so try restarting the extension.
Restart MetaMask
Still getting this message? Send us a bug report.'

should i just downgrade chrome?

If you encounter this error after upgrading Chrome, you might consider downgrading Chrome. Alternatively, try updating the version of Metamask, such as 10.34.x.

Sometimes this error can be caused by an incorrect RPC node. You can try changing it.


Transfer Ownership of sensu-plugins-dcos

Transfer Ownership
We would like to transfer the ownership of this plugin to the sensu-plugins organization in hopes of better community support and exposure. I have reviewed the skeleton plugin for best practices.
Repo to transfer:
https://github.com/PTC-Global/sensu-plugins-dcos
I am also interested in continuing to help as a maintainer of this plugin 👍

I see you have already initiated the repo transfer process I will take care of all this tonight.


How to schedule periodic tasks that runs hourly for example ?

Luigi comes with no support for "starting" you task. Read the docs please.


[DOCFIX]Doc fix for docs/en/Getting-Started.md.md

Merged build finished. Test PASSed.

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


⚠ Young Discoverers has degraded performance

In 83f4a4c, Young Discoverers (https://youngdiscoverers.org.au) experienced degraded performance:

HTTP code: 200
Response time: 6019 ms

Resolved: Young Discoverers performance has improved in d0fd320.


moan is not working on sample project

There's something either very wrong with the sample project or with moan itself so this is a critical bug.
Steps to reproduce

Install moan globally:

$ npm install -g moan

Checkout sample project:

$ git clone https://github.com/neocotic/moan-sample.git moan-sample

Install sample project:

$ cd moan-sample
moan-sample $ npm install

Nothing happens when using either npm script or global moan:

moan-sample $ npm test

><EMAIL_ADDRESS>test /path/to/moan-sample
> moan

moan-sample $ moan

It might help to have #9 and #10 implemented first to help debug this problem as currently impossible to get extra information to track the steps and find where it's failing.

This has been fixed and will be included in the 0.1.2 release.


Installing varying architecture side by side?

I need both the 32bit and the 64bit version of nim installed but if I already have one architecture type installed and tried to install the other with the appropriate flag, it complains about the package already being installed.
I also need the same for gcc
Is this a bug?

Just came here as I have exactly the same issue with llvm...

Duplicate of #3265


Inlay hints shift around when typing

Issue Type: Bug

Set "typescript.inlayHints.parameterNames.enabled": "all"
Open this file https://github.com/microsoft/vscode/blob/23d99b3055a95aeb586406905b6bdcbc31d39a53/extensions/typescript-language-features/src/typescriptServiceClient.ts#L605
Start typing inside the string 'The TypeScript language ...'

Bug
The inlay hints shift around as you type:

latex-workshop|Jam|8.19.2
vscode-memfs|jri|0.0.3
template-string-converter|meg|0.5.0
vscode-azurefunctions|ms-|1.4.1
vscode-azureresourcegroups|ms-|0.4.0
vscode-docker|ms-|1.15.0
vscode-language-pack-de|MS-|1.59.0
python|ms-|2021.8.1035685139-dev
vscode-pylance|ms-|2021.7.5-pre.1
jupyter|ms-|2021.8.1051926518
remote-containers|ms-|0.188.3
remote-ssh-edit-nightly|ms-|2021.7.29700
remote-ssh-nightly|ms-|2021.7.29701
azure-account|ms-|0.9.8
hexeditor|ms-|1.7.1
js-debug-nightly|ms-|2021.7.2017
live-server|ms-|0.2.4
vscode-github-issue-notebooks|ms-|0.0.102
vscode-typescript-next|ms-|4.4.20210715
vsliveshare|ms-|1.0.4583
debugger-for-chrome|msj|4.12.12
vetur|oct|0.34.1
java|red|0.80.0
code-spell-checker|str|1.10.2
rest-book|tan|3.2.0
ayu|tea|0.20.1
luna-paint|Tyr|0.7.1
sort-lines|Tyr|1.9.0
vscodeintellicode|Vis|1.2.14
vscode-java-debug|vsc|0.34.0
vscode-java-dependency|vsc|0.18.5
vscode-java-test|vsc|0.30.1
vscode-maven|vsc|0.31.0
(2 theme extensions excluded)

Semantic synaxhighlighting is also off...
Is this a TypeScript bug?

Pushed potential fix on the TS side related to which offsets we send to the server. Seems to fix the problem but let me know if you see it again


Localized vsix packages

Getting ready to turn on localized builds in microbuild and VS insertion.
This PR adds the satellite assemblies into the vsix and fixes up the build to eliminate a race

LGTM


Use materializecss with vuejs

I'm having trouble using materialize with vuejs, I'm using the slider, when I bring the images it does not work, I've already initialized $ ('. Slider'). Slider (), but anyway it does not work.
Someone has already gone through this, even if it is with another framework like angularjs.
thanks.

Can you post some more information? We can't actually support every framework to work together with materialize. So this is less of a materialize issue itself. Try asking on stack overflow or in our gitter channel. Thanks.


[Bug]: 404 page not found webhook github source no port

Is there an existing issue for this?

[X] I have searched the existing issues

Example public repository
coolify
Description
There is bug if there is no domain connected, the webhook redirection wont include the port
Steps To Reproduce
Save and Redirect to Github
Version
3.12.3

Yup, just had this issue myself.

Due to inactivity, I'm closing this issue. However, if the problem persists, please reopen the issue. Thanks!


Mountain chart sanity check: it is actually all wrong

The world shape should be like this

Not like this

it looks like my data sucks. and the data from waffle is (more) correct, but also not completely

Done sanity check, reading papers from Mattias and going through all the formulas.
The result: i got two humps like you had in TED talk, but i'm not convinced it's correct
I let it stay for now because i trust you and what Mattias wrote in his reasoning. But i have some strong doubts about that our two humps have ever existed. To me it looks like an error in formula.


promql/series: Ignore missing series based on some condition

Here's the use case. We have a test environment with a single Alertmanager (clustering disabled), while our production environments have a pair of Alertmanager with clustering disabled.
One of our alerts is
alertmanager_cluster_failed_peers > 0

which works fine in both environments, because the metric doesn't exist when clustering is disabled (hence the alert never fires), and it correctly detects failures in our production environments.
But pint is not happy about the missing series, and I don't want to ignore the issue entirely. What I would like to do is either

Be able to ignore metrics on a specific Prometheus server, e.g.prometheus "test" {
    uri = "https://test.example.com"
    timeout = "1m"
}
prometheus "prod" {
    uri = "https://prod.example.com"
    timeout = "1m"
}
check "promql/series" {
    prometheus "test" {
        ignoreMetrics = [
            "alertmanager_cluster_failed_peers",
        ]
    }
}

or something like that, hopefully you get the idea.
Ignore a missing metric based on the value returned by another query (in this case if alertmanager_cluster_enabled == 0).

But perhaps I missed a way to achieve what I'm trying to do that is already supported?

Be able to ignore metrics on a specific Prometheus server, e.g.

You can do this already: https://cloudflare.github.io/pint/checks/promql/series.html#how-to-disable-it

That's awesome, even better than what I had in mind! Sorry for not finding it myself, and thanks for this great tool!


Add surface indices to TriangleMesh

Helps unblock #56597

I'll try to fit checking this with the material pr into my schedule.

Thanks!

Indeed it seems like I forgot this, but I trust @SaracenOne and @fire can amend this when they fix the material PR.

Fixing issue from https://github.com/godotengine/godot/pull/62321#issuecomment-1164085200


doc: Remove mixed pack files from index example

What does this PR change? What problem does it solve?
The example given for the format of an index shows a mixed pack file. Mixing tree and data blobs has been deprecated for a long time. Thus, change the pack to only contain "data" blobs.

Was the change previously discussed in an issue or on the forum?
https://forum.restic.net/t/does-restic-seperate-tree-and-data-into-different-packs-in-the-index-file/6013/2

Checklist

[x] I have read the contribution guidelines.
[x] I have enabled maintainer edits.
[ ] I have added tests for all code changes.
[x] I have added documentation for relevant changes (in the manual).
[ ] There's a new file in changelog/unreleased/ that describes the changes for our users (see template).
[x] I have run gofmt on the code in all commits.
[x] All commit messages are formatted in the same style as the other commits in the repo.
[x] I'm done! This pull request is ready for review.

LGTM.


Adding docker support

Added docker support to run the application on any architecture.

Can you change it according to the nest.js migration?

Updated!

@aliabbasjaffri Hey!
I just review the changes. please fix the comments.
When you run nestjs you will do it with npm start (locally also)


user-guide: add pachyderm to related-technologies

Probably after #576?
https://dvc.org/doc/dvc-philosophy/related-technologies

It's hard to put every existing tool to that page. I would instead put a link to the matrix and that blog post with some of these tools overview and mention that it's not the purpose of this page to cover everything.

Closing this. Pachyderm is a very different tool, and even though people asking us about the difference, probably not the right place to keep the full list of tools in this space.


Issue in deserializing WKT Geoshape

NEST/Elasticsearch.Net version: 7.0.0.
Elasticsearch version: 7.2
Description of the problem including expected versus actual behavior:
I've got an unexpected exception when I'm querying an index containing GeoShape data.
My index is a city with a geo_shape property which represents the polygon of the city.
After indexing all my cities, I'm querying this index and I got an exception for some documents.
For instance: Elasticsearch.Net.UnexpectedElasticsearchClientException: Expected number but found: E at line 1, position 2719 ---> Nest.GeoWKTException: Expected number but found: E at line 1, position 2719
I found out why. My polygon has a weird geo point : -2.5E-05
Steps to reproduce:

Index a document with a geo shape property. I use GeoWKTReader.Read() method. Here the input wkt: POLYGON ((-0.006398 44.588017,-0.006934 44.588301,-0.009124 44.588594,-0.008983 44.588967,-0.011063 44.589696,-0.011266 44.58942,-0.012267 44.589783,-0.012459 44.589554,-0.013572 44.590541,-0.017456 44.591103,-0.019132 44.590944,-0.019321 44.592081,-0.019716 44.593293,-0.019099 44.594691,-0.018417 44.595431,-0.016307 44.596816,-0.017332 44.597405,-0.017781 44.597089,-0.018548 44.597507,-0.018052 44.598736,-0.016321 44.600649,-0.016231 44.601559,-0.016067 44.601815,-0.015525 44.602142,-0.014585 44.602343,-0.013453 44.602819,-0.013068 44.603701,-0.008716 44.605084,-0.00845 44.605199,-0.008521 44.605333,-0.00758 44.60551,-0.006295 44.606043,-0.007994 44.607296,-0.008806 44.607314,-0.009764 44.607009,-0.011068 44.608229,-0.011522 44.608388,-0.011883 44.608725,-0.013054 44.608345,-0.013665 44.608385,-0.013885 44.608812,-0.014826 44.609172,-0.014626 44.609488,-0.015129 44.610497,-0.014218 44.613103,-0.013072 44.61444,-0.011742 44.616385,-0.010904 44.617087,-0.010421 44.617284,-0.009663 44.618165,-0.009092 44.619407,-0.009134 44.620367,-0.008633 44.621804,-0.00504 44.621003,-0.004606 44.619437,-0.004149 44.619677,-0.003016 44.619967,-0.001793 44.620504,-0.001952 44.62199,-0.001856 44.62289,-0.001519 44.623352,-0.001364 44.623391,-0.001163 44.623976,0.000201 44.624808,0.000607 44.625354,0.002171 44.624872,0.003715 44.623831,0.004433 44.623673,0.005454 44.622984,0.006917 44.622461,0.007293 44.622037,0.009918 44.620499,0.013277 44.619909,0.015858 44.617343,0.015914 44.617203,0.015461 44.616504,0.015662 44.616048,0.016044 44.615667,0.017331 44.614911,0.017972 44.615224,0.022267 44.612973,0.023139 44.611824,0.023893 44.611236,0.025445 44.609381,0.032372 44.603392,0.03227 44.602486,0.0317 44.601796,0.030703 44.601341,0.027205 44.598117,0.026396 44.597586,0.025164 44.597176,0.024376 44.596406,0.024885 44.59479,0.025134 44.592374,0.026765 44.592004,0.026934 44.591885,0.026894 44.591551,0.026263 44.590748,0.025839 44.589659,0.025124 44.588694,0.024298 44.58848,0.022791 44.588433,0.021333 44.587822,0.020833 44.587398,0.019522 44.587224,0.01806 44.587571,0.017402 44.587548,0.015641 44.58671,0.014358 44.586278,0.013375 44.58581,0.011964 44.58689,0.011561 44.586694,0.010076 44.587716,0.009663 44.587319,0.008677 44.587859,0.008711 44.588023,0.008198 44.588137,0.007573 44.588664,0.006392 44.589229,0.005935 44.587927,0.006002 44.586881,0.006155 44.586794,0.005466 44.586113,0.005344 44.585744,0.004945 44.585325,0.005112 44.585091,0.00419 44.585448,0.003732 44.585922,0.003311 44.58607,0.003219 44.586252,0.001708 44.586787,0.001759 44.587122,0.00024 44.587541,-0.000025 44.587736,-0.000602 44.588702,-0.001406 44.588558,-0.001853 44.589188,-0.003142 44.588988,-0.004143 44.58849,-0.006398 44.588017))
2.Query the document
3.Exception thrown:

Elasticsearch.Net.UnexpectedElasticsearchClientException: Expected number but found: E at line 1, position 2719 ---> Nest.GeoWKTException: Expected number but found: E at line 1, position 2719
   at Nest.GeoWKTReader.NextNumber(WellKnownTextTokenizer tokenizer)
   at Nest.GeoWKTReader.ParseCoordinate(WellKnownTextTokenizer tokenizer)
   at Nest.GeoWKTReader.ParseCoordinates(WellKnownTextTokenizer tokenizer)
   at Nest.GeoWKTReader.ParseCoordinateLists(WellKnownTextTokenizer tokenizer)
   at Nest.GeoWKTReader.ParsePolygon(WellKnownTextTokenizer tokenizer)
   at Nest.GeoWKTReader.Read(WellKnownTextTokenizer tokenizer, String shapeType)
   at Nest.GeoWKTReader.Read(String wellKnownText)
   at Nest.GeoShapeFormatter.Deserialize(JsonReader& reader, IJsonFormatterResolver formatterResolver)
   at Deserialize(Object[] , JsonReader& , IJsonFormatterResolver )
   at Elasticsearch.Net.Utf8Json.Resolvers.DynamicMethodAnonymousFormatter`1.Deserialize(JsonReader& reader, IJsonFormatterResolver formatterResolver)
   at Elasticsearch.Net.Utf8Json.JsonSerializer.Deserialize[T](Byte[] bytes, Int32 offset, IJsonFormatterResolver resolver)
   at Elasticsearch.Net.Utf8Json.JsonSerializer.Deserialize[T](Byte[] bytes, IJsonFormatterResolver resolver)
   at Elasticsearch.Net.Utf8Json.JsonSerializer.Deserialize[T](Stream stream, IJsonFormatterResolver resolver)
   at Nest.DefaultHighLevelSerializer.Deserialize[T](Stream stream)
   at Elasticsearch.Net.DiagnosticsSerializerProxy.Deserialize[T](Stream stream)
   at Nest.SourceFormatter`1.Deserialize(JsonReader& reader, IJsonFormatterResolver formatterResolver)
   at Deserialize(Object[] , JsonReader& , IJsonFormatterResolver )
   at Elasticsearch.Net.Utf8Json.Resolvers.DynamicMethodAnonymousFormatter`1.Deserialize(JsonReader& reader, IJsonFormatterResolver formatterResolver)
   at Nest.ReadAsFormatter`2.Deserialize(JsonReader& reader, IJsonFormatterResolver formatterResolver)
   at Elasticsearch.Net.Utf8Json.Formatters.CollectionFormatterBase`4.Deserialize(JsonReader& reader, IJsonFormatterResolver formatterResolver)
   at Deserialize(Object[] , JsonReader& , IJsonFormatterResolver )
   at Elasticsearch.Net.Utf8Json.Resolvers.DynamicMethodAnonymousFormatter`1.Deserialize(JsonReader& reader, IJsonFormatterResolver formatterResolver)
   at Nest.ReadAsFormatter`2.Deserialize(JsonReader& reader, IJsonFormatterResolver formatterResolver)
   at Deserialize(Object[] , JsonReader& , IJsonFormatterResolver )
   at Elasticsearch.Net.Utf8Json.Resolvers.DynamicMethodAnonymousFormatter`1.Deserialize(JsonReader& reader, IJsonFormatterResolver formatterResolver)
   at Elasticsearch.Net.Utf8Json.JsonSerializer.Deserialize[T](Byte[] bytes, Int32 offset, IJsonFormatterResolver resolver)
   at Elasticsearch.Net.Utf8Json.JsonSerializer.Deserialize[T](Byte[] bytes, IJsonFormatterResolver resolver)
   at Elasticsearch.Net.Utf8Json.JsonSerializer.DeserializeAsync[T](Stream stream, IJsonFormatterResolver resolver)

I guess this is due to the -0.000025 data point format.
The polygone mapping is:
"polygone":{
"type": "geo_shape"
}

Thanks in advance,
Patrice

Thanks for reporting @PatriceMarin, this is a bug. Will open a fix shortly.

opened https://github.com/elastic/elasticsearch-net/pull/3922 to address

This will be fixed in the next release

Cool, thanks a lot!!
Do you know when the next release will be available?

@PatriceMarin we should be releasing a new version in the coming days


Problem with browser script

Hello,
today i check my code and i have this "DevTools failed to load SourceMap: Could not load content for https://unpkg.com/v-tooltip.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE"
And the v-tooltip doesn't work...
You have an issue ?

Before my holiday all is good and work. And now no =/

It should be back up. The error message you are reporting is just a sourcemap file, so you can safely ignore it.
BTW, I recommend you to use a version range (or a fixed version number) in the link to the unpkg CDN. Example from the README I just updated.

It should be back up. The error message you are reporting is just a sourcemap file, so you can safely ignore it.
BTW, I recommend you to use a version range (or a fixed version number) in the link to the unpkg CDN. Example from the README I just updated.


Add GitHub templates for issues and pull requests

Based on the suggestion on  Gitter earlier today, here a proposal of templates for new issues and pull requests, to reduce the amount of time @koskima has to spend answering things that can be avoided or for which the community can help out also.
Please feel free to completely change the wording or reject the PR all together : )

Travis fails on this one, but it can't be the templates I've added.

Master builds without a problem. Maybe you need to rebase?

In general I think templates like these are needed. Now that objection is growing faster, most of my time is spent on trying to understand issues and prying out relevant information from the reporters. What we need even more is contributors! People to help me answer the issues. Can you whip up a pull request for those 😄 @VladShcherbin May I ask why the confused emoji?

It seems that prettier was updated and old version creates different results than the new one. Lint passes for master with the old prettier, but not with the new one 😄

Rebasing with master should now fix the prettier errors.

Coverage remained the same at 95.841% when pulling 6d158b5a21455233241f55f65ccc2eac2252c19a on lehni:feature/github-templates into d50997f904bfb9d90b00c7f2ad16d8804064c006 on Vincit:master.

Rebasing did the trick indeed. I can work more on these templates but at one point it's probably easier if you just do the fine tuning to what you think it should be, @koskimas ?

@lehni Yeah, thanks for the templates. I'll finetune them myself.

Coverage remained the same at 95.798% when pulling 0d55e880c3bdc1cc8d4f1b2734831ab2c060f96d on lehni:feature/github-templates into fb43aedb6d32072607d91317341dd559fd39a2dc on Vincit:master.

Coverage remained the same at 95.798% when pulling 0d55e880c3bdc1cc8d4f1b2734831ab2c060f96d on lehni:feature/github-templates into fb43aedb6d32072607d91317341dd559fd39a2dc on Vincit:master.

@koskimas I've done some more work on these templates now, pushed as an incremental commit so you can better see what changed. I can squash them if you like.

Coverage remained the same at 95.798% when pulling 94d13d2c9631947169f7948fbc89aa59ab57bd2b on lehni:feature/github-templates into fb43aedb6d32072607d91317341dd559fd39a2dc on Vincit:master.

Did I miss it or was there place to tell which objection and knex versions are used?

@elhigu Yep, those should be added. @lehni I can take it from here. You don't need to be our typist 😄 Thank you for the templates! I only need to change a couple of small things and they are good to go.

@koskimas you're welcome, happy to help where I can!

@koskimas What is left before this can be merged?


Beatsaver viewer thinks chrome is safari/ios

So this is the first time I'm using your viewer and any song I open on bsaber.com or even your Click To View button on the main GitHub screen shows me the beat saber map with a sign that says ios and safari support coming soon! we need to convert songs to mp3 firs. I am using the Chrome Browser Version 72.0.3626.109 (Official Build) (64-bit)

Fixed, sorry! https://github.com/supermedium/beatsaver-viewer/commit/7d4c61c0277e9696237600524ae14e9798d2ee6d


[bug] - nvm runs even without admin privileges

What happened?
At some point my nvm use command stopped complaining about missing admin privileges.

As you can see in the screenshot above, I've ran nvm use without having run the CMD as an admin(you can tell by the title of the window).
Thing to note: I had installed another nvm-windows instance on a different Windows user for testing. The other installation is separate from the original one though - it has a different appdata folder and a different symlink folder. But I think I still had the admin privilege error present even after installing nvm on the other user - I'm not sure.
What did you expect to happen?
I expected nvm use to complain that I don't have admin rights to run the command.
Version
1.1.11 or newer (Default)
Which version of Windows?
No response
Which locale?
None
Which shell are you running NVM4W in?
No response
User Permissions?
Administrative Privileges, Elevated
Is Developer Mode enabled?
None
Relevant log/console output
No response
Debug Output
Windows Developer Mode: UNKNOWN (user cannot read registry)

NVM4W Version:      1.1.11
NVM4W Path:         C:\Users\lucky\AppData\Roaming\nvm\nvm.exe
NVM4W Settings:     C:\Users\lucky\AppData\Roaming\nvm\settings.txt
NVM_HOME:           C:\Users\lucky\AppData\Roaming\nvm
NVM_SYMLINK:        C:\Program Files\nodejs
Node Installations: C:\Users\lucky\AppData\Roaming\nvm

Active Node.js Version: none
(run "nvm use <version>" to activate a version)

PROBLEMS DETECTED
-----------------
"C:\WINDOWS\system32\cmd.exe - nvm  debug" is not an officially supported shell. Some features may not work as expected.

Find help at https://github.com/coreybutler/nvm-windows/wiki/Common-Issues

Anything else?
No response

This happens in one of two scenarios I can think of:

Installing for all users (as opposed to one user).
Selecting the same NVM_SYMLINK target directory for each different installation (i.e. both use C:\nvm).

@coreybutler I tested on my work laptop. It can use mklink /J instead of mklink /D that required administrator.

@icharge if your work laptop has Developer Mode enabled or an AD group policy granting symlink privileges, then it will work.
As I've said many times before, junctions are not an acceptable option at this time because they do not work across network drives. Given how many enterprises rely on this (SAN drives), it would be a breaking change for nearly half the NVM4W user base.

@icharge if your work laptop has Developer Mode enabled or an AD group policy granting symlink privileges, then it will work.
As I've said many times before, junctions are not an acceptable option at this time because they do not work across network drives. Given how many enterprises rely on this (SAN drives), it would be a breaking change for nearly half the NVM4W user base.

That’s problem. I can’t enable developer mode due to company’s policy. That was crazy.
What if it can be configurable.

@icharge - I've thought about making it configurable, but there's a whole different set of edge cases to deal with. I don't have time to do that. I've frozen feature development in order to work on the successor project: Runtime.
The bottom line is installing multiple versions of Node is... you know, installing multiple applications. It's not unusual for companies to block this. The entire reason Microsoft created Developer Mode is so companies could allow a few "power" features for those who need it without destroying their carefully crafted security policies. That's a fancy way of saying that your company will have to grant you some sort of access at some point if you're going to install multiple versions of Node. Most employers do this at some point (even strict ones, like some governments and militaries). I've worked with countless cybersecurity groups to allow-list NVM4W. If your company needs something specific to deploy NVM4W, I'm happy to talk to the cybersecurity team.
When all else fails, I tend to recommend installing NVM4W on a non-protected directory, and setting the symlink to a non-protected directory as well. For example, install to C:\nvm4w and symlink to C:\nodejs. You still need permission to use the underlying mklink capability, but this eliminates the possibility of messing with C:\Program Files (a Windows protected directory).

I'm closing because this isn't really a bug. In fact, running without admin privileges is a frequently requested feature.


Update prompting with a more complete message

"Please enter a choice [1]:" is not so clear.
Making the prompt as "Please enter a choice [Default choice (1)]:" so a complete message is conveyed.

@tjprescott Can you take a look at this change (minor change in prompt message wording) ?

@atbagga thanks for the contribution!


Add issue and pull request templates

Add issue and pull request templates

Issue template example:

The problem
Briefly describe the issue you are experiencing (or the feature you want to see added to Selenide).
Tell us what you were trying to do and what happened instead.
Details
If necessary, describe the problem you have been experiencing in more detail.
Tell us about your environment

Selenide Version:
Chrome\Firefox\IE Version:
Browser Driver Version:
Selenium Version:
OS Version:

Code To Reproduce Issue [ Good To Have ]
Please remember that with sample code it's easier to reproduce the bug.

PR template example:
Proposed changes
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request.
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Checklist

[ ] Checkstyle and unit tests pass locally with my changes by running gradle check chrome htmlunit command
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Coverage increased (+0.08%) to 64.522% when pulling f1e9468c1a97d81004adfe94f5b80bb4d7426360 on github_templates into cab968059c4aeac8a6bfe8b3dddac02c53ec65d7 on master.

Codecov Report

Merging #605 into master will increase coverage by 0.11%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #605      +/-   ##
============================================
+ Coverage     60.45%   60.57%   +0.11%
- Complexity      728      729       +1
============================================
  Files           134      134
  Lines          2658     2658
  Branches        270      270
============================================
+ Hits           1607     1610       +3
+ Misses          945      943       -2
+ Partials        106      105       -1

Impacted Files
Coverage Δ
Complexity Δ

...e/selenide/impl/WebDriverThreadLocalContainer.java
80% <0%> (+2.06%)
31% <0%> (+1%)
: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 cab9680...f1e9468. Read the comment docs.


Feat/dotlottie interactivity

This PR introduces the first beta build of interactivity powered by state machines 🎉
With interactivity being implemented inside the Rust player, this feature will be available across all of dotLottie frameworks once implemented.
Features:
Since this is the first released build, not all planned features are implemented yet however they will be shortly!
This first release contains:

Ability to transition between different defined states based on events you send via the post_event function
Enables the frameworks the ability to implement listeners for the users. By calling the state_machine_framework_setup  function
State machine context variables (custom variables)
Guarded transitions

The WASM binary size has increased by 140KB, from 1.10MB to 1.24MB


Docker: yahka (homekit) on Synology? Which ports?

Hi, I can't figure out which ports should be opened and bound to the host system. I can not find any homekit devices.

I think this is an multicast/ docker related problem. As far as I know yahka/ Homekit uses multicast packages for detection. But multicast packages are not forwarded to the container when using bridged network.
I don't know if there is any parameter for getting multicast forwarded to a container in Docker. You can try using MACVLAN as network option. This should work.
For more information you can ask other users by posting your question at the ioBroker Forum Thread (linked in readme.md).
I know there are users who have yahka running.
If this answers your question, please close this issue.
Thank you.
Regards,
André

As there is no activity here for more than two weeks now, I'm going to close this issue.
Regards,
André


Added s390x support for multi-arch image building

Added a few lines in the multiarch-build.yaml file so that the image can be built on IBM Z.
Signed-off-by: Lawrence Luo<EMAIL_ADDRESS>

resolved in https://github.com/containerbuildsystem/operator-manifest/pull/52


vid2vid capabilities

A few questions about the vid2vid capabilites:
Has the vid2vid example been tested with any non-anime models? I tried feeding a realistic video into the suggestd anime model and unsurprisingly that didn't work well.
How well does it work if the input video does not have a plain background?
How well does it work if the input video is not similar to the output character prompt? The example Gif uses a prompt that is very close to the character the input video.

针对您提出的三个问题，我的回答如下：

Vid2vid模型是否使用非动漫模型进行了测试？

Vid2vid模型最初是基于动漫风格的视频转换，因此在测试时通常使用动漫风格的视频作为输入和输出。但是，随着技术的发展，Vid2vid模型已经被扩展到其他类型的视频转换，例如将真实视频转换为卡通风格的视频。因此，使用非动漫模型进行测试是可能的，并且已经在某些研究中得到应用。

如果输入视频没有简单的背景效果如何？

Vid2vid模型通常需要一个简单的背景来生成输出视频，因为模型需要了解背景和前景之间的关系。如果输入视频没有简单的背景，模型可能会难以理解视频中的对象和场景，从而导致生成的输出视频效果不佳。

如果输入视频与输出字符提示不相似，效果如何？

如果输入视频与输出字符提示不相似，那么生成的输出视频可能会与输入视频有很大的差异，效果可能不会很好。Vid2vid模型通常需要输入视频和输出字符提示之间的相似性来生成高质量的输出视频。因此，如果输入视频与输出字符提示不相似，生成的输出视频效果可能会受到影响。

谢谢你的快速反应。Translating the answers for others:

Have the Vid2vid models been tested with non-anime models?
The Vid2vid model was originally based on anime-style video conversion, so anime-style videos are usually used as input and output when testing. However, with the development of technology, the Vid2vid model has been extended to other types of video conversion, such as converting real videos to cartoon-style videos. Therefore, testing with non-anime models is possible and has been used in some studies.

What if the input video has no simple background effect?
Vid2vid models usually require a simple background to generate the output video because the model needs to understand the relationship between the background and foreground. If the input video does not have a simple background, the model may have difficulty understanding the objects and scenes in the video, resulting in a poor output video.

What if the input video is not similar to the output character prompt?
If the input video is not similar to the output character prompt, the generated output video may be very different from the input video and may not perform well. Vid2vid models usually require similarity between input video and output character cues to generate high-quality output videos. Therefore, if the input video is not similar to the output character prompts, the resulting output video performance may be affected.


fix(serve): exit with a status code on error instead of panic

Fixes issue #1392

What type of PR is this?

Which issue does this PR fix:
What does this PR do / Why do we need it:
If an issue # is not available please add repro steps and logs showing the issue:
Testing done on this change:

Automation added to e2e:

Will this break upgrades or downgrades?
Does this PR introduce any user-facing change?:

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

{"level":"warn","goroutine":1,"caller":"zotregistry.io/zot/pkg/debug/swagger/swagger_disabled.go:22","time":"2023-04-30T18:37:12.714278926Z","message":"skipping enabling swagger because given zot binary doesn't include this feature, please build a binary that does so"}
{"level":"fatal","error":"listen tcp <IP_ADDRESS>:8080: bind: address already in use","time":"2023-04-30T18:37:12.714703066Z","message":"unable to run controller"}