Add "down" method for migrations

Hello,
I am aware that the use of "down" methods in our migrations is typically unnecessary these days. However, it is still considered standard practice in Laravel, isn't it? With that in mind, I have submitted a pull request to include it.
Thank you for your great work,
George

Sure. I can't see anyone ever needing these tbh but can't hurt.

Thanks!


Api logging

Add logging for the API and adjust the rate limit for the api/v1/uplaodData endpoint to accept up to 50 files/hr from a single IP.

:tada: This PR is included in version 1.6.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Create a README in the xor example

Hello Daniel, hopefully, you will read this pull request. I am Jonathan Richer dit Laflèche and I am 14.
Since a bit long time, I've been watching your lives and tutorials. I am doing a lot of p5 and a little bit of processing because I first strated to learn HTML so javascript kinda came with it and now I am new to the Machine Learning.
I saw in one of your videos that we can create readme so there it is... I hope it will be merged, but if it's not, it's also ok!

I like what you did here. It's very cool! I think Dan would be happy to include the link to your project. Because you are adding this to the Coding Train repository, I think it would be better if you change the wording to be clear the comment is coming from you. Maybe add quotation marks? Something like:
## Variations:

* [NN XOR](https://codemehtm.github.io/nn) by codeMeHtm - "I literally copied this code from the video, but then, I added a little bit more."

Other than that, this is awesome!

@Versatilus Yes, of course! I am going to add it!
Thank you very much!!

Thank you @codeMeHtm!


A bunch of broken links in the Miscellaneous section

Hi there! Hello from SoftwareMansion team 💙
Member of https://membrane.stream/ checkin in here 👋
As you probably might already know we utilize your repo (to some certain extend) Great stuff there!
The other day, we have been doing some testing stuff on our webpage and it has turned out that there are some broken links in your repo that you might want to know about:
in case you want to fix them, here they are:

https://www.encoding.com/android/
https://www.encoding.com/http-live-streaming-hls/
http://www.hometheatersound.com/
https://www.adobe.com/devnet/adobe-media-server/articles/h264_encoding.html
http://web.ece.ucdavis.edu/cerl/ReliableJPEG/Cung/jpeg.html
http://gentlelogic.blogspot.com.br/2011/11/exploring-h264-part-2-h264-bitstream.html
https://www.itu.int/rec/T-REC-H.264-201610-I
https://mahanstreamer.net/

also this one is bit odd: it redirects to a camera manufacturer page (does it suppose to be like that?)

http://www.hkvstar.com/

have a good one!

Thank you, I'll try to check them somewhere in the future :)


how do I assign an OnClickListener to the play/pause button?

Question / Problem
Summary

What I've tried

It's not possible. You should listen through events from YouTubePlayerListener instead.


Replacement of a packages with packages with a differently cased ID causes nuget restore to break

Yes, it's a bit of a mouthful, and a really bizarre problem. The background can be found at http://adamralph.com/2015/03/04/nuget-gallery-casing-woes/
In short, the original package ID was "Bau.XUnit". All versions of it were then removed by the support team. I then pushed several versions of the package with the ID "Bau.Xunit". The ID of the package seemed to change from "Bau.XUnit" to "Bau.Xunit" as expected. However, any download of the package which specifies a specific version (either via install or restore) now fails.
Using Fiddler I've discovered the following:
Install-Package -Prerelease -Id Bau.Xunit

uses the resource:
https://www.nuget.org/api/v2/FindPackagesById()?id='Bau.Xunit'
and this resource responds perfectly, without any error, and the operation goes on to succeed.
Whereas the following (and also nuget restore)
Install-Package -Prerelease -Id Bau.Xunit -Version 0.1.0-beta07

uses the resource:
https://www.nuget.org/api/v2/Packages(Id='Bau.Xunit',Version='0.1.0-beta07')
and this resource returns an error (even though the status code is 200) which the client cannot process, and the operation fails.
Until this is fixed, my package is pretty much dead in the water, since it's impossible to run a restore against it.
In the short term, I'm hoping the support team can find a workaround (they are currently looking into it) and I'm hoping that anyone reading this may be able to help point them in the right direction. In the long term I guess it would be good to fix the root cause to prevent this happening again.

Just took a quick look at the FindPackagesById implementation for a v2 feed: it is actually doing a case-insensitive query on package id, so that call will always work after changing capitalization of any character in the package id.
The other call is querying the Packages collection on the OData endpoint. Given this call fails, I'd assume it is case-sensitive, and given the fact you are calling with the correct (expected) casing, my gut feeling says there's an issue in the data warehouse still referencing the old casing somewhere.
/cc @zhili1208

Hi @xavierdecoster! Yeah I suspected something like that.
I wonder if there's a way it could be manually hacked to align things.
Alternatively, if you can think of a way to completely remove all traces of the package, everywhere, I'd be happy for all version of the package to be removed again, and I can try and re-upload the again?

Just did a 'view source' on the failing call:
https://www.nuget.org/api/v2/FindPackagesById()?id='Bau.Xunit'
The failing call clearly returns a package with id Bau.XUnit instead of Bau.Xunit. If all versions of the package with this casing were removed, then the search endpoint is clearly thinking otherwise.
<?xml version="1.0" encoding="utf-8"?>
<entry xml:base="https://www.nuget.org/api/v2/" xmlns="http://www.w3.org/2005/Atom" xmlns:d="http://schemas.microsoft.com/ado/2007/08/dataservices" xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata">
	<id>https://www.nuget.org/api/v2/Packages(Id='Bau.XUnit',Version='0.1.0-beta07')</id>
	<category scheme="http://schemas.microsoft.com/ado/2007/08/dataservices/scheme" term="NuGetGallery.V2FeedPackage"/>
	<link href="Packages(Id='Bau.XUnit',Version='0.1.0-beta07')" rel="edit" title="V2FeedPackage"/>
	<title type="text">Bau.XUnit</title>
	<summary type="text"/>
	<updated>2014-12-01T21:51:40Z</updated>
	<author>
		<name>Adam Ralph,  Bau contributors</name>
	</author>
	<link href="Packages(Id='Bau.XUnit',Version='0.1.0-beta07')/$value" rel="edit-media" title="V2FeedPackage"/>
	<content src="https://www.nuget.org/api/v2/package/Bau.XUnit/0.1.0-beta07" type="application/zip"/>
	<m:properties>
		<d:Published m:type="Edm.DateTime">2014-12-01T21:51:40.407</d:Published>
		<!-- Removed for brevity -->
	</m:properties>
</entry>

In addition it also contains an exception.
Adding it here for future reference.
<?xml version="1.0" encoding="utf-8"?>
<m:error xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata">
	<m:code>500</m:code>
	<m:message xml:lang="en-US">An error occurred while trying to write an error payload.</m:message>
	<m:innererror>
		<m:message>Cannot transition from state 'Completed' to state 'Error'. Nothing further can be written once the writer has completed.</m:message>
		<m:type>Microsoft.Data.OData.ODataException</m:type>
		<m:stacktrace>at Microsoft.Data.OData.ODataWriterCore.Microsoft.Data.OData.IODataOutputInStreamErrorListener.OnInStreamError()
   at Microsoft.Data.OData.Atom.ODataAtomOutputContext.WriteInStreamErrorImplementation(ODataError error, Boolean includeDebugInformation)
   at Microsoft.Data.OData.Atom.ODataAtomOutputContext.WriteInStreamError(ODataError error, Boolean includeDebugInformation)
   at System.Data.Services.ErrorHandler.WriteErrorWithFallbackForXml(ODataMessageWriter messageWriter, Encoding encoding, Stream responseStream, HandleExceptionArgs args, ODataError error, MessageWriterBuilder messageWriterBuilder)</m:stacktrace>
	</m:innererror>
</m:error>

Yep, I concur. I did a similar analysis.

Not sure the issue is really related to casing at all.
I'm getting the exact same error behavior with my library NanoByte.Common since I released the last update, and I did not change the case.
Valid XML response: https://www.nuget.org/api/v2/Packages(Id='NanoByte.Common',Version='1.1.5')
XML Response with an exception tacked on (looking just like the one above): https://www.nuget.org/api/v2/Packages(Id='NanoByte.Common',Version='1.1.6')

@bastianeicher I can see your issue reproducing, but I'm not sure if the root cause is the same. We are going to take a look at both issues.

@adamralph @bastianeicher we are trying to investigate this issue. Looks like in both your scenarios (edits to the package metadata or deleting/readding a package) we might end up with duplicates in our index. We are trying to both cleanup the index and fix the root cause problem.
A simple workaround for now would be to add another version of your packages either in the form of a -beta-07-0 in @adamralph case. Or <IP_ADDRESS> in @bastianeicher case. Sorry for your troubles, we are working on cleaning this thing out.

Thanks @yishaigalatzer.
Would 0.1.0-beta08 have the same effect? I don't mind increase the beta counter.

Yes it should, let us know if it doesn't.

@yishaigalatzer thank you, uploading beta 8 did the trick - https://www.nuget.org/api/v2/Packages(Id='Bau.Xunit',Version='0.1.0-beta08')
This removes the immediate pressure on me to have this problem fixed :smile:

@yishaigalatzer in case this relevant to your investigation of the issue:
I did not edit to the package metadata and/or delete/readd a package prior to running into the problem.

That makes we wonder if Bau.Xunit simply suffered from some horrible, and hugely unlikely, coincidence.

 The XML declaration must be the first node in the document, and no white space characters are allowed to appear before it. Line 4, position 643.
System.InvalidOperationException: Unable to find version '2.3' of package 'WpfLocalizeExtension'.
   at NuGet.PackageRepositoryHelper.ResolvePackage(IPackageRepository sourceRepository, IPackageRepository localRepository, IPackageConstraintProvider constraintProvider, String packageId, SemanticVersion version, Boolean allowPrereleaseVersions)
   at NuGet.PackageManager.InstallPackage(String packageId, SemanticVersion version, Boolean ignoreDependencies, Boolean allowPrereleaseVersions)
   at NuGet.Commands.InstallCommand.InstallPackage(IFileSystem fileSystem, String packageId, SemanticVersion version)
   at NuGet.Commands.InstallCommand.ExecuteCommand()
   at NuGet.Commands.Command.Execute()
   at NuGet.Program.Main(String[] args)

Response contains this invalid XML:
<?xml version="1.0" encoding="utf-8"?><entry xml:base="https://www.nuget.org/api/v2/" xmlns="http://www.w3.org/2005/Atom" xmlns:d="http://schemas.microsoft.com/ado/2007/08/dataservices" xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"><id>https://www.nuget.org/api/v2/Packages(Id='WpfLocalizeExtension',Version='2.3')</id><category term="NuGetGallery.V2FeedPackage" scheme="http://schemas.microsoft.com/ado/2007/08/dataservices/scheme" /><link rel="edit" title="V2FeedPackage" href="Packages(Id='WpfLocalizeExtension',Version='2.3')" /><title type="text">WpfLocalizeExtension</title><summary type="text">LocalizationExtension is a really easy way to localize any type of DependencyProperties or native Properties on DependencyObjects</summary><updated>2015-02-24T08:52:01Z</updated><author><name>Bernhard Millauer, Uwe Mayer</name></author><link rel="edit-media" title="V2FeedPackage" href="Packages(Id='WpfLocalizeExtension',Version='2.3')/$value" /><content type="application/zip" src="https://www.nuget.org/api/v2/package/WpfLocalizeExtension/2.3.0" /><m:properties><d:Version>2.3</d:Version><d:NormalizedVersion>2.3.0</d:NormalizedVersion><d:Copyright>Bernhard Millauer, Uwe Mayer</d:Copyright><d:Created m:type="Edm.DateTime">2015-02-24T08:46:45.827</d:Created><d:Dependencies>XAMLMarkupExtensions:1.2:</d:Dependencies><d:Description>LocalizationExtension is a really easy way to localize any type of DependencyProperties or native Properties on DependencyObjects</d:Description><d:DownloadCount m:type="Edm.Int32">16932</d:DownloadCount><d:GalleryDetailsUrl>https://www.nuget.org/packages/WpfLocalizeExtension/2.3.0</d:GalleryDetailsUrl><d:IconUrl></d:IconUrl><d:IsLatestVersion m:type="Edm.Boolean">true</d:IsLatestVersion><d:IsAbsoluteLatestVersion m:type="Edm.Boolean">true</d:IsAbsoluteLatestVersion><d:IsPrerelease m:type="Edm.Boolean">false</d:IsPrerelease><d:Language>en-US</d:Language><d:Published m:type="Edm.DateTime">2015-02-24T08:46:45.827</d:Published><d:PackageHash>UdtG8dNtzQO8zv47mV+mVe9IU9q/dj7qCcphxrRj+JF1aT8mlnzNS02ubXaoj7wZXQs/6fest9wJPecRhPYeMg==</d:PackageHash><d:PackageHashAlgorithm>SHA512</d:PackageHashAlgorithm><d:PackageSize m:type="Edm.Int64">16019</d:PackageSize><d:ProjectUrl>https://github.com/SeriousM/WPFLocalizationExtension/</d:ProjectUrl><d:ReportAbuseUrl>https://www.nuget.org/package/ReportAbuse/WpfLocalizeExtension/2.3.0</d:ReportAbuseUrl><d:ReleaseNotes>v2.3
* closes #42
* closes #48
* refs #34</d:ReleaseNotes><d:RequireLicenseAcceptance m:type="Edm.Boolean">true</d:RequireLicenseAcceptance><d:Tags>wpf silverlight phone localization extension globalization resx csv resource language</d:Tags><d:Title>WPF Localization Extension</d:Title><d:VersionDownloadCount m:type="Edm.Int32">435</d:VersionDownloadCount><d:MinClientVersion></d:MinClientVersion><d:LastEdited m:type="Edm.DateTime">2015-02-24T08:48:58.477</d:LastEdited><d:LicenseUrl>https://github.com/SeriousM/WPFLocalizationExtension/blob/master/LICENSE</d:LicenseUrl><d:LicenseNames></d:LicenseNames><d:LicenseReportUrl></d:LicenseReportUrl></m:properties></entry><?xml version="1.0" encoding="utf-8"?><m:error xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"><m:code>500</m:code><m:message xml:lang="en-US">An error occurred while trying to write an error payload.</m:message><m:innererror><m:message>Cannot transition from state 'Completed' to state 'Error'. Nothing further can be written once the writer has completed.</m:message><m:type>Microsoft.Data.OData.ODataException</m:type><m:stacktrace>   at Microsoft.Data.OData.ODataWriterCore.Microsoft.Data.OData.IODataOutputInStreamErrorListener.OnInStreamError()
   at Microsoft.Data.OData.Atom.ODataAtomOutputContext.WriteInStreamErrorImplementation(ODataError error, Boolean includeDebugInformation)
   at Microsoft.Data.OData.Atom.ODataAtomOutputContext.WriteInStreamError(ODataError error, Boolean includeDebugInformation)
   at System.Data.Services.ErrorHandler.WriteErrorWithFallbackForXml(ODataMessageWriter messageWriter, Encoding encoding, Stream responseStream, HandleExceptionArgs args, ODataError error, MessageWriterBuilder messageWriterBuilder)</m:stacktrace></m:innererror></m:error>

The Install-Package WpfLocalizeExtension run in Visual Studio installs the packages correctly (even if I clear the NuGet cache folder).

Installing the package using Install-Package works, but running Update-Package -Reinstall will fail:
PM> Install-Package WpfLocalizeExtension -Verbose
Attempting to resolve dependency 'XAMLMarkupExtensions (≥ 1.2)'.
Installing 'WpfLocalizeExtension 2.3'.
You are downloading WpfLocalizeExtension from Bernhard Millauer,  Uwe Mayer, the license agreement to which is available at https://github.com/SeriousM/WPFLocalizationExtension/blob/master/LICENSE. Check the package for additional dependencies, which may come with their own license agreement(s). Your use of the package and dependencies constitutes your acceptance of their license agreements. If you do not accept the license agreement(s), then delete the relevant components from your device.
Added file 'WPFLocalizeExtension.dll' to folder 'WpfLocalizeExtension.2.3\lib\net35'.
Added file 'WPFLocalizeExtension.xml' to folder 'WpfLocalizeExtension.2.3\lib\net35'.
Added file 'WP7LocalizeExtension.dll' to folder 'WpfLocalizeExtension.2.3\lib\sl4-wp71'.
Added file 'WP7LocalizeExtension.xml' to folder 'WpfLocalizeExtension.2.3\lib\sl4-wp71'.
Added file 'SLLocalizeExtension.dll' to folder 'WpfLocalizeExtension.2.3\lib\sl50'.
Added file 'SLLocalizeExtension.xml' to folder 'WpfLocalizeExtension.2.3\lib\sl50'.
Added file 'WpfLocalizeExtension.2.3.nupkg' to folder 'WpfLocalizeExtension.2.3'.
Successfully installed 'WpfLocalizeExtension 2.3'.
Adding 'XAMLMarkupExtensions 1.2' to Project1.
For adding package 'XAMLMarkupExtensions 1.2' to project 'Project1' that targets 'net45',
>> Assembly references are being added from 'lib\net40'
Added reference 'XAMLMarkupExtensions' to project 'Project1'
Added file 'packages.config'.
Successfully added 'XAMLMarkupExtensions 1.2' to Project1.
Adding 'WpfLocalizeExtension 2.3' to Project1.
For adding package 'WpfLocalizeExtension 2.3' to project 'Project1' that targets 'net45',
>> Assembly references are being added from 'lib\net35'
Added reference 'WPFLocalizeExtension' to project 'Project1'
Added file 'packages.config'.
Successfully added 'WpfLocalizeExtension 2.3' to Project1.

PM> Update-Package -Reinstall WpfLocalizeExtension -Verbose
Removing 'WpfLocalizeExtension 2.3' from Project1.
Removed reference 'WPFLocalizeExtension.dll' from project 'Project1'
Added file 'packages.config'.
Successfully removed 'WpfLocalizeExtension 2.3' from Project1.
Removing 'XAMLMarkupExtensions 1.2' from Project1.
Removed reference 'XAMLMarkupExtensions.dll' from project 'Project1'
Added file 'packages.config'.
Successfully removed 'XAMLMarkupExtensions 1.2' from Project1.
Uninstalling 'WpfLocalizeExtension 2.3'.
Removed file 'WP7LocalizeExtension.dll' to folder 'D:\dev\Project1\packages\WpfLocalizeExtension.2.3\lib\sl4-wp71'.
Removed file 'WP7LocalizeExtension.xml' to folder 'D:\dev\Project1\packages\WpfLocalizeExtension.2.3\lib\sl4-wp71'.
Removed folder 'D:\dev\Project1\packages\WpfLocalizeExtension.2.3\lib\sl4-wp71'.
Removed file 'WPFLocalizeExtension.dll' to folder 'D:\dev\Project1\packages\WpfLocalizeExtension.2.3\lib\net35'.
Removed file 'WPFLocalizeExtension.xml' to folder 'D:\dev\Project1\packages\WpfLocalizeExtension.2.3\lib\net35'.
Removed folder 'D:\dev\Project1\packages\WpfLocalizeExtension.2.3\lib\net35'.
Removed file 'SLLocalizeExtension.dll' to folder 'D:\dev\Project1\packages\WpfLocalizeExtension.2.3\lib\sl50'.
Removed file 'SLLocalizeExtension.xml' to folder 'D:\dev\Project1\packages\WpfLocalizeExtension.2.3\lib\sl50'.
Removed folder 'D:\dev\Project1\packages\WpfLocalizeExtension.2.3\lib\sl50'.
Removed folder 'D:\dev\Project1\packages\WpfLocalizeExtension.2.3\lib'.
Removed file 'WpfLocalizeExtension.2.3.nupkg' to folder 'D:\dev\Project1\packages\WpfLocalizeExtension.2.3'.
Removed folder 'D:\dev\Project1\packages\WpfLocalizeExtension.2.3'.
Successfully uninstalled 'WpfLocalizeExtension 2.3'.
Update-Package : Unexpected XML declaration. The XML declaration must be the first node in the document, and no white space characters are allowed to appear before it. Line 4, position 643.
At line:1 char:1
+ Update-Package -Reinstall WpfLocalizeExtension -Verbose
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Update-Package], Exception
    + FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PowerShell.Commands.UpdatePackageCommand

This is because the client uses different resources for different operations. E.g. for Bau.Xunit 0.7.0, restoration fails but installation succeeds.

@jozefizso please don't mix bugs. Open your own :) at home

@adamralph this should resolve your issue. We we are currently blocking user deletes, and looking for perhaps an obscure race condition based on @bastianeicher. But there is nothing to do here, until we enable a self serve delete at some point in the future.

@yishaigalatzer sorry, I don't understand. What is it that should resolve my issue?

Publishing a new package of version 0.8.0, am I missing something?

@yishaigalatzer Thanks, it wasn't clear what you were referring to.
I don't believe this issue is solved. Yes, we have a workaround, but it involves work for consumers, i.e. upgrading to 0.8.0. Any attempts to perform package restore when using 0.7.0 or earlier will still fail, so the situation is far from ideal.

@adamralph. Yes I agree, we will add at some point proper user level deletes, and we are tracking separately an improvement to the sync mechanism such that deletes don't create duplicates. We will be running a manual re-sync sometimes this week so this index is back in order.
For now we are just not allowing deletes and unlisting is the way to go. (We shouldn't have allowed them anyways through a manual request). And have monitoring in place to understand if this happens again (and a mechanism to fix it manually, until we get to the bottom of the issue)

@adamralph , This issue is related to https://github.com/NuGet/NuGetGallery/issues/2328

@deepakaravindr thanks for the link!

Also related to #2390 (which now has been fixed)


NamedViewDetail cannot be serialised into JSON

This was introduced in 1.7.0-RC1.

Merged into develop.


Unable to open sample1.xml file

I have tried to open the xml/2023-06-19/sample1.xml file with the Viewer. Unfortunately without success.

Is there anything I'm doing wrong? Here are the logs of the application:
warn: Microsoft.AspNetCore.DataProtection.Repositories.FileSystemXmlRepository[60]
      Storing keys in a directory '/root/.aspnet/DataProtection-Keys' that may not be persisted outside of the container. Protected data will be unavailable when container is destroyed.
warn: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[35]
      No XML encryptor configured. Key {8bf02e2f-c698-4382-95c5-c7b41fbe3ef5} may be persisted to storage in unencrypted form.
info: Microsoft.Hosting.Lifetime[0]
      Now listening on: http://[::]:80
info: Microsoft.Hosting.Lifetime[0]
      Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
      Hosting environment: Production
info: Microsoft.Hosting.Lifetime[0]
      Content root path: /publish
warn: Microsoft.AspNetCore.HttpsPolicy.HttpsRedirectionMiddleware[3]
      Failed to determine the https port for redirect.
fail: Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware[1]
      An unhandled exception has occurred while executing the request.
System.ArgumentNullException: Value cannot be null. (Parameter 'source')
   at System.Linq.ThrowHelper.ThrowArgumentNullException(ExceptionArgument argument)
   at System.Linq.Enumerable.Count[TSource](IEnumerable`1 source)
   at AspNetCore.Views_Home_PageLieferschein.ExecuteAsync()
   at Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderPageCoreAsync(IRazorPage page, ViewContext context)
   at Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderPageAsync(IRazorPage page, ViewContext context, Boolean invokeViewStarts)
   at Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderAsync(ViewContext context)
   at Microsoft.AspNetCore.Mvc.ViewFeatures.HtmlHelper.RenderPartialCoreAsync(String partialViewName, Object model, ViewDataDictionary viewData, TextWriter writer)
   at AspNetCore.Views_Home_Results.ExecuteAsync() in /src/Views/Home/Results.cshtml:line 38
   at Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderPageCoreAsync(IRazorPage page, ViewContext context)
   at Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderPageAsync(IRazorPage page, ViewContext context, Boolean invokeViewStarts)
   at Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderAsync(ViewContext context)
   at Microsoft.AspNetCore.Mvc.ViewFeatures.ViewExecutor.ExecuteAsync(ViewContext viewContext, String contentType, Nullable`1 statusCode)
   at Microsoft.AspNetCore.Mvc.ViewFeatures.ViewExecutor.ExecuteAsync(ViewContext viewContext, String contentType, Nullable`1 statusCode)
   at Microsoft.AspNetCore.Mvc.ViewFeatures.ViewExecutor.ExecuteAsync(ActionContext actionContext, IView view, ViewDataDictionary viewData, ITempDataDictionary tempData, String contentType, Nullable`1 statusCode)
   at Microsoft.AspNetCore.Mvc.ViewFeatures.ViewResultExecutor.ExecuteAsync(ActionContext context, ViewResult result)
   at Microsoft.AspNetCore.Mvc.ViewResult.ExecuteResultAsync(ActionContext context)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextResultFilterAsync>g__Awaited|29_0[TFilter,TFilterAsync](ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResultExecutedContextSealed context)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.ResultNext[TFilter,TFilterAsync](State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeResultFilters()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextResourceFilter>g__Awaited|24_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResourceExecutedContextSealed context)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeFilterPipelineAsync()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable scope)
   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger)
   at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.<Invoke>g__Awaited|6_0(ExceptionHandlerMiddleware middleware, HttpContext context, Task task)

Opened a pull request with a fix for this particular file.


feat: add network in use check to compose down

Signed-off-by: Retros<EMAIL_ADDRESS>Close #1425

Can you add an integration test for this scenario?

Can you add an integration test for this scenario?

I may try~

Signed-off-by: Retros

Please use a real name, as explained in https://github.com/cncf/foundation/issues/383#issuecomment-1178254458

Please also update your DCO sign in the PR description.


How to use primary key of self  without "key-generator.type=SNOWFLAKE" config

#2694 question , you fixed it  that add "key-generator.type=SNOWFLAKE" config .   I  want to use primary key of self  based on redis ,and is it  available without  "key-generator.type=SNOWFLAKE" config？it is necessary to be  configured?  how to configure it  based on  primary key of self ? Which version of the production environment is better,  either 3.1.0 version or 4.0.0-RC1 version?

Can you change title of issue to make it more clear?

you can implement ShardingKeyGenerator interface to generate primary key by yourself.
The example can see LeafSegmentKeyGenerator, SnowflakeShardingKeyGenerator or UUIDShardingKeyGenerator.

About the versions question, I can't answer it exactly because I don't know your environment detail.
But I suggest you use 4.0.0-RC1 first.

ok, I'll give it a try.

I defined key type ="PRIMARYKEY-SELF",  how to make DistributeKeyGenerator class effective?

please give me  an answer for the error?  how to load  the DistributeKeyGenerator class

Please add DistributeKeyGenerator to SPI.
If don't know how to add, please search for it.

You know you can tell directly me ，I have searched for it , reference documentation is readed, There is  no about the spi instructions， https://shardingsphere.apache.org/document/current/cn/features/spi/ or others doc ，don't get me wrong, it's my first time to use it

I means you search How to use SPI in google or Baidu.
SPI official document: https://docs.oracle.com/javase/tutorial/sound/SPI-intro.html

Most of the problems have been solved. Thank you for your help！：）


discovery: If unknown NetDisco service discovered, log about it.

Otherwise, known services are logged, ignored are logged, but unknown -
not. Logging them is quite helpful for someone working on adding new
discovery service to NetDisco/HA, and would help to decouple NetDisco
library further: another project may use a generic NetDisco library,
and contribute new service to it, which won't be automatically supported
by HA. But logging about it would be a good hint to HA users that they
can look into supporting it.
Description:
Related issue (if applicable): fixes #
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Example entry for configuration.yaml (if applicable):

Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

Logging them is quite helpful for someone working on adding new discovery service to NetDisco/HA

This came out from working on https://github.com/home-assistant/netdisco/pull/144


add support for "blade deploy" for maven projects

moved to https://github.com/gamerson/liferay-blade-cli/issues/6


Throws error when downloaded resource checksum is correct

Hello, juts a little problem.
When you download Isos, it throw an error about checksum, even if this one is good
I checked the  iso's checksum and it was good.
i Made more tests (other isos) and each time it's the same, trow error ..
best regards

Hi @christophekumor - sorry to hear you're having problems 😭. Can you provide the command and resulting output that you are seeing? It would also be handy to know what version of Lability and PowerShell you're running.


Closes

It closes on its own after a few songs, if I go out of YouTube. If I lock the screen while it's on YouTube, the bug doesn't occur. It's very annoying

I'm on the latest version of YouTube, and latest version of the module (I updated last night to the experiential release). This version seems to be working a lot better. If it continues happening I'll send a log.

There was a fix in the 2.x experimental releases aimed at older versions of the Xposed framwork. If the issue reappears, please open a ticket. I am closing this one then.

No, it's still happening. I can't get a log until Friday. It seems pretty random, but when I open SnapChat it usually closes

Do you use some kind of app killer like greenify? Also, how much RAM does
your device have? Maybe system is closing it due to not having enough free
RAM?
On Wed, Nov 9, 2016, 21:01 Droidking18<EMAIL_ADDRESS>wrote:

No, it's still happening. I can't get a log until Friday. It seems pretty
random, but when I open SnapChat it usually closes
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pylerSM/YouTubeBackgroundPlayback/issues/262#issuecomment-259511328,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMxxbCczfdipKGVdqIIXAPxarvBGSIDtks5q8iaTgaJpZM4KrZZo
.

I used to use an app killer, but stopped because I thought that was the
reason. I checked my RAM usage, but that doesn't seem to be the issue. My
device has 1.3 Gb of RAM, so I'm not sure what the issue is. It seems the
new 2.0.1 update has made it less frequent though, but it still happens. By
the way, I'm running CM 13, if that helps.
On 9 Nov 2016 15:04, "Łukasz Ordon"<EMAIL_ADDRESS>wrote:

Do you use some kind of app killer like greenify? Also, how much RAM does
your device have? Maybe system is closing it due to not having enough free
RAM?
On Wed, Nov 9, 2016, 21:01 Droidking18<EMAIL_ADDRESS>wrote:

No, it's still happening. I can't get a log until Friday. It seems pretty
random, but when I open SnapChat it usually closes
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/pylerSM/YouTubeBackgroundPlayback/
issues/262#issuecomment-259511328>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AMxxbCczfdipKGVdqIIXAPxarvBGSIDtks5q8iaTgaJpZM4KrZZo>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pylerSM/YouTubeBackgroundPlayback/issues/262#issuecomment-259512143,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AP67Knnwg5TPf0cT3lfcbyfADu1f9cikks5q8idmgaJpZM4KrZZo
.


Tweaks and fixes

Ugrades to Ditto 3.0.4-experimental.ditto-core-data.1 and removes the shortName constraint because those aren't supported by DittoCoreData (yet). Couple more tweaks and fixes, see individual commits for details.

@npb12 @texasRanger09 feel free to merge at will. 👍


Deprecated  Predicate hasQualifiedName, getQualifiedName

Introduction of v2.15.3 deprecated the following predicates:

hasQualifiedName, getQualifiedName

These deprecated keywords need to be re-introduced after we after attended to them internally.

No longer needed.


Make computed fields easier to declare

 Issue by sethladd
Originally opened as dart-lang/sdk#13458

I just saw code like this in the wild:
 bindProperty(this, const Symbol('name'), () => notifyProperty(this, const Symbol('statusIcon')));
    bindProperty(this, const Symbol('type'), () => notifyProperty(this, const Symbol('statusIcon')));
    bindProperty(this, const Symbol('value'), () => notifyProperty(this, const Symbol('statusIcon')));
    bindProperty(this, const Symbol('extraValidation'), () => notifyProperty(this, const Symbol('statusIcon')));
    bindProperty(this, const Symbol('minlen'), () => notifyProperty(this, const Symbol('statusIcon')));
    bindProperty(this, const Symbol('maxlen'), () => notifyProperty(this, const Symbol('statusIcon')));
Can we do something better?
Strawman:
computedField(#statusIcon, [#name, #type, #value, ...]);  // assuming multiple fields can trigger a change in one field

 Comment by jmesserly

fyi -- thinking on this more, definitely leaning towards @ComputedField. All of the other approaches suffer from the problem that the dependencies aren't localized near the getter.

Removed Priority-Unassigned label.
Added Priority-High label.

 Comment by sigmundch

Added this to the M8 milestone.

 Comment by seaneagan

Wouldn't this be valid for methods, not just fields?  If a method's return value depends on another property in the model, then how do polymer expressions calling the method, know when they are dirty?
So maybe instead of @ComputedField it could be something like @DependsOn :
class FooElement extends PolymerElement with ObservableMixin {
  String salutation;
  @DependsOn([#salutation])
  getGreeting(String name) => '$salutation $name;
}

 Comment by jmesserly

also, once my Polymer Core change lands it will be easier at least:
   [#name, #type, #value, #extraValidation, #minlen, #maxlen].forEach(
        (x) => bindProperty(#statusIcon, this, x);
I think the Polymer bindProperty is meant to follow the Node.bind style of "name, model, path"

 Comment by jmesserly

So pretty soon you could write this in a much cleaner way with Symbol literals:
    notifyStatus() => notifyProperty(this, #statusIcon)
    bindProperty(this, #name, notifyStatus);
    bindProperty(this, #type, notifyStatus);
    bindProperty(this, #value, notifyStatus);
    bindProperty(this, #extraValidation, notifyStatus);
    bindProperty(this, #minlen, notifyStatus);
    bindProperty(this, #maxlen, notifyStatus);
Or even better:
    [#name, #type, #value, #extraValidation, #minlen, #maxlen].forEach(
        (x) => bindProperty(this, x, () => notifyProperty(this, #statusIcon)));
There's still a few problems in this code:

bindProperty is a bad name. It must be renamed anyway because it conflicts with a Polymer thing (oops). Let's call it onPropertyChange.
bind/notify pattern is annoying.
the requirement to supply "this" is annoying. How come I can't use implicit this? Let's say onPropertyChange, notifyPropertyChange are directly on the Observable mixin.
Writing a getter that depends on so many properties is probably a bad idea. Better to listen on the values and cache the computation in a field:

[#name, #type, #value, #extraValidation, #minlen, #maxlen].forEach(
    (x) => bindProperty(this, x, computeStatusIcon));
computeStatusIcon() {
  statusIcon = ...;
}
As for computedField: it's nice in this example, but I don't know how well it scales to other examples. What if some of those properties come from other objects? That's fairly common at least in Polymer. They make it easy to forward a property from a nested component to your outer component (amusingly, they call this "bindProperty" :) ).
Let's instead make onPropertyChange able to listen on a list of names. Now we could get to:
    // note: both of these are calls to "this.", so it works for other objects too.
    onPropertyChange([#name, #type, #value, #extraValidation, #minlen, #maxlen],
        () => notifyPropertyChange(#statusIcon));
Now we're within getting close distance of computedField, but with the ability to listen on or notify on other objects.
Unfortunately there's still a big flaw here. If what we really have is data *paths*, single Symbols like above won't work. We'd need something more like:
    onPathChange(['entity.name', 'type', 'value', 'extraValidation', 'bounds.min', 'bounds.max'],
        () => notifyPathChange('statusIcon'));
Oy!
You might wonder why we use Strings for paths instead of something else? That's a fair question. The Symbol/String dichotomy is really hard to deal with when many of our names come from HTML, and unfortunately it landed just before MDV did. Now that we have Symbol literals, something like this is more feasible, and worth considering a change to PathObserver:
    [#entity, #name]
That would bring us to something like:
    onPathChange([[#entity, #name], #type, #value, #extraValidation, [#bounds, #min], [#bounds, #max]],
        () => notifyPathChange(#statusIcon));
folding the on+notify together gives us something very close to your original:
    computedField(#statusIcon, [[#entity, #name], #type, #value, #extraValidation, [#bounds, #min], [#bounds, #max]]);
I wonder if it should also be expressed at the meta-level. It seems less error prone to declare this right at the getter:
    @ComputedField(const [const [#entity, #name], #type, #value, #extraValidation, const [#bounds, #min], const [#bounds, #max]])
    get statusIcon => ...;
Another option is just to expose PolymerExpressions conveniently, and use those:
    get statusIcon => const PolymerExpression('... computation of StatusIcon here ... ').value;
Personally, I don't know if any of this is very good. It is the downside of using observers, and having neither read barriers nor statically analyzable expressions. But such is the world we live in.

 Comment by jmesserly

@5 -- the problem with methods is they're only a PolymerExpressions feature. PolymerExpressions could certainly look for an annotation. But putting the annotation on a method would have no meaning at the package:observer layer

 Comment by sigmundch

Added Library-Observe label.

 Comment by sigmundch

Issue dart-lang/observe#33 has been merged into this issue.

cc @jmesserly.

 Comment by jmesserly

Issue dart-lang/sdk#14111 has been merged into this issue.

 Comment by sigmundch

We would love to get to this. We still need to do some design work on it so most likely it wont be done by M8.

Removed this from the M8 milestone.
Added this to the Later milestone.

 Comment by anders-sandholm

Removed Library-Observe label.
Added Pkg-Observe label.

 Comment by sigmundch

Removed this from the Later milestone.
Added this to the M9 milestone.

 Comment by zoechi

This issue was included in a changelist today.  May I ask what's new with this change?

 Comment by clayberg

Removed this from the M9 milestone.
Added this to the 1.1 milestone.

 Comment by sigmundch

Removed this from the 1.1 milestone.
Added this to the 1.2 milestone.

 Comment by jmesserly

The design I proposed in @1 has a flaw. It has no way of expressing list reductions, for example filtering a list of items. So... back to square 1.
Polymer's solution for computed fields is to use *Changed handlers and embrace mutable public fields:
    @observable String firstName, lastName, fullName;
    firstNameChanged() => _computeFullName();
    lastNameChanged() => _computeFullName();
    _computeFullName() {
      fullName = '$firstName $lastName';
    }
... it works, but only inside PolymerElements. And doesn't clearly communicate to API consumers that fullName is recomputed. And recompute won't happen until the microtask runs.

 Comment by jmesserly

so, Polymer has added some Polymer-specific features here that are worth checking out. there's this ObserveProperty thingy:
///     @ObserveProperty('foo.bar baz qux')
///     validate() {
///       // use this.foo.bar, this.baz, and this.qux in validation
///       ...
///     }
makes it easy to do validation or computed properties.
there's also this proposed change:
https://code.google.com/p/dart/issues/detail?id=16342
going to merge this into that bug, since it would essentially make getters "just work"

Added Duplicate label.
Marked as being merged into dart-lang/sdk#16342.


Update project for Xcode 12.1

The current project doesn't compile with Xcode 12

First issue. It raises a signing error

Adding the Code Signing Flag --deep fixes the issue (https://stackoverflow.com/a/60099521/3572934)

Second issue. Tests cannot be compiled with the error "Illegal instruction: 4"

This is a known Nimble issue fixed in the latest version (https://github.com/Quick/Nimble/issues/809)
Updating Quick and Nimble and fixing small breaking changes make it compile and work fine

Third modification: Update to Xcode recommended project settings (enables a warning flag)

Fourth modification: Fix few warnings

note: I haven't pushed Pod sources yet to keep the PR readable. it needs to be pushed before to be merged

          1 Error

:no_entry_sign:
Any changes to library code need a summary in the Changelog.

  Generated by :no_entry_sign: Danger

          1 Warning

:warning:
Big PR

  Generated by :no_entry_sign: Danger

🙇


Nice project but nothing working

Hi,
You project is nice, but but nothing working
Thanks

There needs to be a 'New Item' brand. I added scat-data.sql for adding that data, and fixed another problem that meant you couldn't create the very first transaction. More may be missing for everything to work, but this pushes the ball a little further. New issues can be opened for new specific problems.


auth api failing with 1000-0999 error

March 18 around 00 UTC authentication to aquarea-smart.panasonic.com started failing.
likely due to API change?
https://github.com/cjaliaga/home-assistant-aquarea/issues/105
I believe our connection string looks like this? any request to this enpoint seems to result in the same error/403:
curl -H "Content-Type: application/x-www-form-urlencoded"
-H "Cache-Control: max-age=0"
-H "Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8"
-H "Accept-Encoding: deflate, br" -H "Upgrade-Insecure-Requests: 1"
-H "User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0"
-X POST 'https://aquarea-smart.panasonic.com/remote/v1/api/auth/login?username=panasonic@xxxx&password=xxxxx'

{"errorCode":4194816,"message":[{"errorMessage":"Logged out due to system error. Please login again after a while.","errorCode":"1000-0999","additionalErrorCode":null}],"accessToken":{}}

FWIW - I was able to see web login process to https://authglb.digital.panasonic.com/usernamepassword/login, don't have a setup for sniff the mobile app atm:
<client_id>vf2i6hW5hA2BB2BQGfTHXM4YFyW4I06K</client_id>
<redirect_uri>https://aquarea-smart.panasonic.com/authorizationCallback?lang=en</redirect_uri>
<tenant>pdpauthglb-a1</tenant>
<response_type>code</response_type>
<scope>openid offline_access</scope>
<audience>https://digital.panasonic.com/vf2i6hW5hA2BB2BQGfTHXM4YFyW4I06K/api/v1/</audience>
<_csrf>9OCkcl4F-fgQCE4wTTDWTMQnIHnO-Ek1wBlk</_csrf>
<state>hKFo2SAweUM4X0tybnhUNmZtSUZVdTlfTFVkdjQwZ0Z4TWJHeKFupWxvZ2luo3RpZNkgOG9rMzZOVkNjemJkRlN2a0J1YkN3OHdyczZ3S2RJTmOjY2lk2SB2ZjJpNmhXNWhBMkJCMkJRR2ZUSFhNNFlGeVc0STA2Sxx</state>
<_intstate>deprecated</_intstate>
<username>Panasonic@xxx</username>
<password>xxxx</password>
<lang>en</lang>
<connection>PanasonicID-Authentication</connection>

my attempts to generate/guess/reuse state param for authglb endpoint fail with this error:
{"statusCode":403,"description":"Invalid state","name":"AnomalyDetected","code":"access_denied"}
anyone out there more familiar with this oauth2 aspect?
or is it some kind of secret authglb is expecting to be encoded in the state? fwiw, there was no forced upgrade on mobile app side, Dec 2023 still works with this auth.

Same error happening here.
Thanks.

the good news: this new authglb seems to allow multiple logins. at least when using google login which is an option now (apple id as well; need to register here - https://accountglb.digital.panasonic.com/social first)

Thanks @viliusdidit for all the investigation so far, let's see what we can do. The ideal (in a happy world) solution would be for us to not need to use the username and password and being able to auth as a service/application to Panasonic cloud, get a token, and use that token, with the possibility of getting a refresh_token as well. Unfortunately I don't see that happening.

Thanks @viliusdidit for all the investigation so far, let's see what we can do. The ideal (in a happy world) solution would be for us to not need to use the username and password and being able to auth as a service/application to Panasonic cloud, get a token, and use that token, with the possibility of getting a refresh_token as well. Unfortunately I don't see that happening.

hopefully you can make it happen for all of us somehow 🙌

In case it helps, I noticed this NPM library that takes a different approach: it "impersonates" the iOS app using a different set of APIs.
Just sharing due to the lack of public documentation from Panasonic around their APIs.

Hey guys, I found your issue by searching if someone fixed the new login way to Panasonic Cloud. As nobody did, here is the working code:
https://github.com/Hernas/homebridge-panasonic-heat-pump/commit/dd04fc2b7a207a2648d7ad94bb8eb19052d21bf2
I hope that helps! :)

Thanks a lot @bimusiek, I'll take a look ASAP.

@cjaliaga, I have seen that the fix has been implemented in dedicated branch. I don't know if there are some technical issues to be solved, but if you are afraid of exposing the hard-coded client id, maybe it can be provided by the user during the integration config flow.

The clientId was copied from JS code of OAuth provider at Panasonic so you could fetch it from there. AFAIK it is Panasonic client id from their oauth provider so it is not secret and should not change.

Thanks @lcavalli, as @bimusiek said this Client Id it's not a secret and shouldn't change. Thanks for stepping in 😊
I'm implementing it on this branch: https://github.com/cjaliaga/aioaquarea/blob/7ddd0eac009a23a4b60aea42f20eb36c773281f6/aioaquarea/core.py#L349
To give an update, I'm currently stuck on the response 3 (call with the username and password to https://authglb.digital.panasonic.com/usernamepassword/login). I'll need to check if I'm not sending all the required cookies, the json sent with aiohttp is not properly encoded, something else.. or there's something wrong with my username because the response I get from the endpoint is a Bad Request - 400 invalid username
I'll check with @bimusiek project and my username/password to discard that.

Quick update, it was a silly mistake. Apologies on the slow pace as I'm doing my best mainly on the night on the few spare minutes I have this week, I'm exhausted at the end of the day and I end making this mistakes haha.
My estimation is to have a working solution tomorrow for everyone to test it.

Quick update, it was a silly mistake. Apologies on the slow pace as I'm doing my best mainly on the night on the few spare minutes I have this week, I'm exhausted at the end of the day and I end making this mistakes haha.
My estimation is to have a working solution tomorrow for everyone to test it.

Don't worry, we appreciate your efforts!

Thanks @cjaliaga !!

I have a working version, and I'm sure it will require some refactor but I think the best way is for us to test it and find the edge cases (and maybe not that edge haha) while using it so I'll release a new version with the changes.

I am getting this:
'<' not supported between instances of 'datetime.datetime' and 'NoneType' Cannot connect to host authglb.digital.panasonic.comhttps:443 ssl:default [Name or service not known] Cannot connect to host authglb.digital.panasonic.comhttps:443 ssl:default [Name or service not known] Cannot connect to host authglb.digital.panasonic.comhttps:443 ssl:default [Name or service not known] Cannot connect to host authglb.digital.panasonic.comhttps:443 ssl:default [Name or service not known] Cannot connect to host authglb.digital.panasonic.comhttps:443 ssl:default [Name or service not known] Cannot connect to host authglb.digital.panasonic.comhttps:443 ssl:default [Name or service not known]

@jp-embedded the first error should have been fixed in 0.7.1
The other ones authglb.digital.panasonic.comhttps:443 ssl:default [Name or service not known] Cannot connect to host I think are a result of some request failing breaking the auth flow, and hence the location header resolves to a full URL instead of a path, like here:
https://github.com/cjaliaga/aioaquarea/blob/a8562de53bf72e34a5dd9b246ce62987d6780bb4/aioaquarea/core.py#L299-L317
I'll add verifications in between requests and more logging soon.

0.7.1 works for me. Thank you so much <3

Thanks. Fix was faster then heishamon delivery.
Just one issue for me:
After around 24 hours of updating all entities turned unavailable. Reloading integration fixed it

Same issue happened to me as it did for @vukisz. Entities were unavailable until I reloaded the integration. Now is working fine.

Working! Thanks!

I have a theory about why it didn't try to refresh the data, I think is due to token expiratio and some assumption I took for granted. I'll try to release a hotfix later today.

Just merged #47 that should fix the refresh issue. Publishing 0.7.2 with the fix.

0.7.1 works fine for me.
Thanks for the work you've put into!


[WIP] Developing 1.0 - Iris

Result of Integration 1
Duration: 3 minutes and 59 seconds
Result: Perfect build! All 35 tests passed. :+1:
Test Coverage: 24%

Result of Integration 2
Duration: 4 minutes and 34 seconds
Result: Perfect build! All 36 tests passed. :+1:
Test Coverage: 24%

Result of Integration 4
Duration: 8 minutes and 57 seconds
Result: Perfect build! All 41 tests passed. :+1:
Test Coverage: 27%

Result of Integration 5
Duration: 6 minutes and 29 seconds
Result: Perfect build! All 41 tests passed. :+1:
Test Coverage: 27%


grafana_provisioning_synced - works or not?

What happened?
I think it's feature don't work
Did you expect to see some different?
I want to my provision settings (dashboard, datasources) is dissapear when i delete from "grafana_dashboards" or "grafana_datasources" in defaults/main.yml
How to reproduce it (as minimally and precisely as possible):
I change grafana_provisioning_synced to true and nothings happens
Environment

Role version:
https://github.com/cloudalchemy/ansible-grafana/releases/tag/0.18.0

Ansible version information:
ansible --version
ansible 2.9.6
config file = /etc/ansible/ansible.cfg
configured module search path = ['/home/dude/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python3/dist-packages/ansible
executable location = /usr/bin/ansible
python version = 3.8.5 (default, Jul 28 2020, 12:59:40) [GCC 9.3.0]

Variables:

grafana_provisioning_synced

Ansible playbook execution Logs:

-

Anything else we need to know?:
For example
I add some datasources with provision
# Datasources to configure
grafana_datasources:
 - name: "Prometheus"
   type: "prometheus"
   access: "proxy"
   url: "http://prometheus.XXX:19090"
   basicAuth: true
   basicAuthUser: "XXX"
   basicAuthPassword: "XXX"
   isDefault: true
   jsonData:
     tlsAuth: false
     tlsAuthWithCACert: false
     tlsSkipVerify: true

 - name: "ClickHouse"
   type: "ClickHouse"
   access: "proxy"
   url: "http://XXX:8123"
   basicAuth: false
   isDefault: false
   jsonData:
     tlsAuth: false
     tlsAuthWithCACert: false
     tlsSkipVerify: true

How can i remove one of this (if i already deploy both of this datasources? Just comment in main.yml? Or what?
grafana_provisioning_synced - is this for that?

@inkdude As mentioned in the readme, this is about dashboards. :)

not actual


Move HttpResponseStreamWriter to HttpAbstractions

It doesn't belong in MVC.

@Tratcher @rynowak can we get together to determine the fate of this type?

Discussed and agreed to move to RC.

As discussed with @rynowak in person, we're also moving HttpRequestStreamReader.

Fixed in aspnet/HttpAbstractions/issues/539 and #3940


Save app namespacedname in clusterConditions

This PR modifies the appsetreport CRD by adding a new app field to save the app namespaced name for each cluster. Also working on cleaning up some messages and variable names.

/hold

/unhold

@lennysgarage  Just a reminder that another PR is needed for updating the appsetreport CRD in here
https://github.com/open-cluster-management-io/multicloud-operators-subscription/blob/main/deploy/olm-catalog/multicluster-operators-subscription/manifests/apps.open-cluster-management.io_multiclusterapplicationsetreports.yaml


When I open and kill the app multiple times(over 30 times), multiple blue dots will appear in the picture.

New Issue Checklist

[ ] I have read and understood the CONTRIBUTING guide
[ ] I have read the Documentation
[ ] I have searched for a similar issue in the project and found none

Issue Info

Info
Value

Platform Name
ios

Platform Version
11.3.1

SDWebImage Version
4.4.1

Integration Method
cocoapods

Xcode Version
Xcode 9.3

Repro rate
all the time (100%)

Issue Description and Steps
When I open and kill the app multiple times(over 30 times), multiple blue dots will appear in the picture.
The original full image:

After open and kill the app multiple times:

Sounds really strange. We didn't face this issue from our products. Any good to reproduce this ? 😕

Hi, maybe some additional info can help to solve this problem. Al first, as it was mentioned by @xiaopeijun, image artifacts appear only, when you kill app several times. As I understand, it downloads image multiple times and  SDWebImage saves it to the local cache, using image compression. However, these artifacts appear only at the moment, when image compression goes So, the first idea was to turn off image decompression by this methods
SDWebImageManager.shared().imageDownloader?.shouldDecompressImages = false
SDWebImageManager.shared().imageCache?.config.shouldDecompressImages = false
However, it didn't help and they again appeared. So, I decided to delete the app and reinstall (as I thought, that I will clean local cache), in the result, all image artifacts have disappeared. However, it is not the full solution, as, in some period of time, they have appeared again.

@GaevYuriy SDWebImage store the original image data into your disk cache, not the decompressed one or re-encoded one.  (Until you specify cacheSerializer)
Did you specify anything transformer for the image display ? Such as this delegate here in 4.x

@dreampiggy No, neither cacheSerializer nor any transformer is specified for image display. I use this method to download it. Also, when I checked the cache type in the response handler, it was the memory. And, when I set refreshCached options the problem has disappeared, however it is not a solution, as SDWebImage redownloads the image and save to cache

@GaevYuriy You means, when this strange issue appear, your image instance is from memory cache (SDImageCacheTypeMemory) ? Interesting.
The memory cache now just use NSCache, it should not modify the image instance...
Could you please try to reproduce this issue, and then, set a debug breakpoint, triiger [[SDImageCache sharedImageCache] clearMemory] to remove the memory cache, and let it been retrieve from disk cache to see what happend ?

@xiaopeijun,  I'm not sure if I did it correctly, so I will write my steps

Reproduced bug

Check, image from disk and from memory cache with cacheKey(for URL)

let diskCachedImage = self.imageCache?.imageFromDiskCache(forKey: self.cacheKey(for: url)) let memoryCachedImage = self.imageCache?.imageFromMemoryCache(forKey: self.cacheKey(for: url))
Both of them were with artifacts.

When I called, SDImageCache.shared().clearMemory(), I received disk cache type in response handler and image was still with artifacts

@GaevYuriy From your stops. It seems that the disk cache image data is already been modified. Because I can ensure that the image decoding process will not change the representation of image.
So this time, let's try to figure out the reason. I can give you some steps to check. These step can be done on iPhone simulator to simplify the process.

Firstlly,reinstall your apps, remember one URL that can trigger this issue, download the image original data to desktop, named original.jpg.

Then, check your apps's sandbox and grab the same image to the desktop. You can do this from lldb by using po NSHomeDirectory() (See here). Then find the cache files in ./Documents/Library/Caches/default/com.hackemist.SDWebImageCache.default from documents folder... Copy the image match the URL into desktop, named cache.jpg.

Next, trigger this issue until you see the blut dots. Then, check your app's sandbox again, grab the corrupted image files to desktop, named bug.jpg

Check whether these 3 images are equal. The desired result should be original.jpg == cache.jpg, original.jpg != bug.jpg. If so, we can ensure that the cache files in SDWebImage been modified accidentally.

Maybe I found, what is the problem. So, I did step 1 and step 2, but at step 2 I have already found artifacts, they are small and hardly visible.
Also, in my code, I have a method DispatchQueue.global().async { self.saveImage(toCache: image, for: url) }, when I load the image, I resave it to cache by hand. So, I resave an image from memory to memory, which scales artifacts, so it is the problem. So, now I can say, that this bug appears when SDWebImage saves images to the memory cache.
Original

Comparison with artifacts

@GaevYuriy You means each time you fetched the image (from cache or network), you call SDImageCache.storeImage ? This will cause issue because that method will try to encode thr UIImage memory representation, to thr compressed format image data(By dafault, JPEG for non-alpha image and PNG for alpha image)
Image encoding, which some iOS developer may not be familiar with, have lossy compression or lossless compression. However, JPEG fomat supports only lossy compression. Which means you encode - decode again, the image quantity was effected become worse. If you repeat several time, the final image may not be readable at all.
Through PNG supports lossless compression, however doing this may consume much more unuseful process. It's strongly not to do anything like this. (I guess this is a bug in your business code...Why to store and overwrite a disk image which already exist :consufed)

Per latest comments, closing.


ARROW-5631: [C++] Fix FindBoost targets with cmake3.2

cmake's FindBoost pre 3.5 did not export IMPORTED targets. This also fixes the newly introduced trusty docker image.

A note that this patch does not fully fix the cmake3.2 issue, see https://jira.apache.org/jira/browse/ARROW-5631?filter=-1
But at least it gets a cmake build directory populated.

Looks like @kou introduced that logic here
https://github.com/apache/arrow/commit/f014d76c68a9a977a19f87f7ea77511e4753bb8c
I'm not sure what it's for as we don't use this flag other places in our build system. Some projects use the flag to globally toggle between building SHARED/STATIC when using add_library but we are explicit about this everywhere.

@kou afaik, find_package shouldn't be affected by BUILD_SHARED_LIBS?

I think it's fine to keep the stashing; it seems like it was more likely future proofing

Don't merge for now, it doesn't fix the docker cmake32 image.

rebase with master, ready to land (once it passes tests). This passes locally, minus the linking error fixed by https://github.com/apache/arrow/pull/4635.

It seems that the current changes don't fix anything.
Should we really fix this problem or update title and description of this pull request?

@kou previously cmake didn't even succeed at generating a build folder. The ctest failures are fixed in the PR linked in previous comment (#4635).

Codecov Report

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

@@            Coverage Diff             @@
##           master    #4605      +/-   ##
==========================================
+ Coverage   88.49%   88.91%   +0.41%
==========================================
  Files         890      710     -180
  Lines      110406    96682   -13724
  Branches     1418        0    -1418
==========================================
- Hits        97703    85960   -11743
+ Misses      12422    10722    -1700
+ Partials      281        0     -281

Impacted Files
Coverage Δ

go/arrow/ipc/writer.go

go/arrow/math/uint64_amd64.go

go/arrow/memory/memory_avx2_amd64.go

go/arrow/ipc/file_reader.go

js/src/builder/index.ts

js/src/enum.ts

go/arrow/array/builder.go

js/src/util/fn.ts

js/src/Arrow.node.ts

js/src/schema.ts

... and 170 more

Continue to review full report at Codecov.

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

@ursabot crossbox --help

@ursabot crossbow --help

@ursabot crossbow test

@ursabot crossbow test -g docker

@ursabot crossbow test docker docker-cpp docker-cpp-cmake32 docker-rust

@ursabot crossbow test docker-cpp docker-cpp-cmake32 docker-rust

@ursabot crossbow test docker-c_glib

@kszucs do you know why the badge is at failed? The last one are waiting to be run.

@kou could you check locally with this patch why c_glib docker image fails? I've exausted my debugging of  meson. I think that you need to namespace gandiva's enums.c.
gandiva-glib/meson.build:50:0: ERROR:  Tried to create target "enums.c", but a target of that name already exists.

I'll let you decide if renaming breaks anything.

@ursabot crossbow test docker-c_glib

@ursabot crossbow test docker-r

@ursabot crossbow test -g docker

This fixes the most pressing issues, notably

docker-cpp
docker-cmake32

I fixed also fixed docker-rust, and partly advanced on docker-r and docker-c_glib.

@ursabot crossbow test docker-cpp docker-cpp-cmake32

BTW, I couldn't find any build log on CircleCI.
https://circleci.com/gh/ursa-labs/crossbow/tree/ursabot-46-circle-docker-c_glib shows

And "build" link shows


Better error message for SSL errors

More informative error message for SSL errors

Closing since it's been more than a year since the last activity. Feel free to re-open as needed.


Potatoboard speedrun

Resolves
An ongoing need for speedy potatoes.
Changes
This creates a new database for the fastest time, along with detecting if the new message hitting the potatoboard is faster than ever before. It it is, then it sends an alert to the server news channel.

this would be awesome, but potatoboard isn't supposed to be competitive since it's like starboard. it's for posts people find funny or should be mentioned more, and i feel like adding a speedrun element might make potatoboard a bit bland at times.

this would be awesome, but potatoboard isn't supposed to be competitive since it's like starboard. it's for posts people find funny or should be mentioned more, and i feel (personally) like adding a speedrun element might make potatoboard a bit bland at times.

IMO, it would only encourage people to get more creative and let their charisma show as well as possible. If it’s ideal for all messages on the potatoboard to be great, that would still cause it to be bland. It also adds some friendly competition to make sure people are active, since I expect the record would be pretty fast.

...

IMO, it would only encourage people to get more creative and let their charisma show as well as possible. If it’s ideal for all messages on the potatoboard to be great, that would still cause it to be bland. It also adds some friendly competition to make sure people are active, since I expect the record would be pretty fast.

i do get where you're coming from, but competition might break the potato economy (if you know what i mean) potatos for potatoboard should really only be given imo to posts that DESERVE the potatoes, and not the ones that just want to speedrun and get their name plastered on the channel.

i would change "...before. Only..." to "...before in only..." when scradd is sending the post to potatoboard channel

Why there are ideas for gamify even a mundane thing as a starboard

i decide i agree with jaxon


Maps error

In the terminal on my rpi  I said to find me a map of San Francisco it works on the terminal but in the electron it doesn't display.

yes same problem here from past week .please help anyone
Thnaks :-)

same here

Well I don't think that it's a problem with HTTP as when I ask it to show me a map of India ,the link to the map appears in the terminal from which I am running the MagicMirror , The problem is that it just doesn't show the map.

AI map works fine in browser: localhost/8080, but on electron application nothing is displayed.

hi,
JUST GOT IT WORKING!!
just solved the problem by downgrading the MagicMirror software which runs on an older version of electron.
It looks like the newer version of electron has removed some old features which this repository.

How did you do that
On Mon, Jul 23, 2018, 10:03 PM VH-Tech<EMAIL_ADDRESS>wrote:

hi,
JUST GOT IT WORKING!!
just solved the problem by downgrading the MagicMirror software which runs
on an older version of electron.
It looks like the newer version of electron has removed some old features
which this repository.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/HackerShackOfficial/AI-Smart-Mirror/issues/87#issuecomment-407120277,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ae1M0SbXOikj2l8PWTn0aE8dRtkiQrEAks5uJfrTgaJpZM4VOiUp
.

I actually wasn't able to downgrade MagicMirror as<EMAIL_ADDRESS>is no longer available. So I had to actually burn the image of raspbian running an older version of MagicMirror(which fortunately I had created)
So, what I did was :

burnt that image on the sd card
cloned the HackerShackOfficial/AI-Smart-Mirror repository
followed the steps as given
and just ran it and it worked


Clear existing progress notifications when restarting the language server

If you restart the language server while a progress notification is being shown, that progress notification will exist permanently.

In addition, when rust-analyzers fails to discover the workspace, the progress resource is not freed too, it shows roots scanned: 0/0 indefinitely

In addition, when rust-analyzers fails to discover the workspace, the progress resource is not freed too, it shows roots scanned: 0/0 indefinitely.

Fixed on master

If you restart the language server while a progress notification is being shown, that progress notification will exist permanently.

Seems to be a bug in the client library? Ie, I expect that it should dispose all the resources during shutdown. I wonder why lc.LanguageClient is not disposable even...


Create tool for checking duplicates and live/archive.org version

A small tool for checking duplicates, if the links are down, and that gives you the option to save the link to archive.org or to replace it by the archive.org version if it is down.

It should be done in go | haskell | ocaml with a PEG parser a la parsec.


Create "route action form" example and utilities

In traditional multi-page apps (think PHP) and some JS frameworks (think SvelteKit's actions) it's common for a single route to handle GET or POST requests, and to render different HTML accordingly. This is useful for a) graceful degradation when no JS is available, and b) rendering form errors more easily in response to a malformed or otherwise invalid POST.
#695 allows us to do things like make a POST request to a Leptos <Route/>, but I've had this in stealth mode while trying to figure out the best patterns.
Here's a simplistic example implementing this manually and only using existing APIs. There are several pieces of this that could be refactored out into utilities:

Checking for GET or POST request and responding accordingly
Extracting form data from the request body
Possibly handling multiple actions per route (with something like Svelte's ?create vs ?delete, i.e., named actions via a query param)

use leptos::*;
use leptos_meta::*;
use leptos_router::*;
use serde::{Deserialize, Serialize};

#[component]
pub fn App(cx: Scope) -> impl IntoView {
    // Provides context that manages stylesheets, titles, meta tags, etc.
    provide_meta_context(cx);

    view! { cx,
        <Router>

                <Routes>
                    <Route
                        path=""
                        view=|cx| {
                            view! { cx, <FavoriteColors/> }
                        }
                        methods=&[Method::Get, Method::Post]
                        ssr=SsrMode::Async
                    />
                </Routes>

        </Router>
    }
}

#[derive(Serialize, Deserialize, Clone, Debug, PartialEq, Eq)]
pub enum FavoriteColorFormResult {
    Get,
    PostSuccess {
        color: String,
        number: u32,
    },
    PostErrors {
        color_err: String,
        number_err: String,
    },
    InvalidMethod,
}

#[derive(Serialize, Deserialize, Debug)]
struct FavoriteColorArgs {
    color: String,
    number: String,
}

#[server(FavoriteColorForm, "/api")]
pub async fn favorite_color_form(
    cx: Scope,
) -> Result<FavoriteColorFormResult, ServerFnError> {
    use http::Method;
    use leptos_axum::{extract, RequestParts};

    extract(cx, move |method: Method| async move {
        match method {
            Method::GET => FavoriteColorFormResult::Get,
            Method::POST => {
                // TODO better way to read POST request data
                // i.e., just refactor this bit out into a utility
                let req = expect_context::<RequestParts>(cx);
                let query: FavoriteColorArgs =
                    serde_qs::from_bytes(&req.body).unwrap();

                let color = query.color;
                let number = query.number;
                let color_err = (!["red", "blue", "green"]
                    .contains(&color.to_ascii_lowercase().trim()))
                .then_some(
                    "Sorry, the only good colors are red, blue, and green.",
                );
                let number = number.parse::<u32>().ok();
                let number_err = number.is_none().then_some(
                    "Sorry, the only good colors are red, blue, and green.",
                );
                if color_err.is_some() || number_err.is_some() {
                    FavoriteColorFormResult::PostErrors {
                        color_err: color_err.unwrap_or_default().to_string(),
                        number_err: number_err.unwrap_or_default().to_string(),
                    }
                } else {
                    FavoriteColorFormResult::PostSuccess {
                        color,
                        number: number.unwrap_or_default(),
                    }
                }
            }
            _ => FavoriteColorFormResult::InvalidMethod,
        }
    })
    .await
    .map_err(|_| {
        ServerFnError::ServerError("Trouble extracting server data".into())
    })
}

/// Renders the home page of your application.
#[component]
fn FavoriteColors(cx: Scope) -> impl IntoView {
    // Creates a reactive value to update the button
    view! { cx,

"Welcome to Leptos!"

        <Await
            future=favorite_color_form
            view=|cx, data| {
                view! { cx,
                    // TODO do some real error handling here

{format!("{data:?}")}

                    <form method="POST">

"What's your favorite color?"

                            <input type="text" name="color"/>

"What's your favorite number?"

                            <input type="text" name="number"/>

                        <input type="submit"/>
                    </form>
                }
            }
        />
    }
}

Oh I also need to loosen the extract function bounds to FnOnce. They're based on route handlers which of course need to be Fn but that doesn't apply when calling them inside a server function, of course.

@gbj This looks promising! I tried to add on progressive enhancement with an ActionForm, but I hit a bit of a wall.
I can make a form work with full server rendering following your example, and I can make the ActionForm work with client rendering.
But I'm not sure how to make the ActionForm post to the same route and get either JSON or HTML depending on whether JS/WASM is enabled.

for 0.5.0-rc3 use:
<Await
    future=favorite_color_form
    bind:data
>

{format!("{data:?}")}

    <form method="POST">

"What's your favorite color?"

            <input type="text" name="color"/>

"What's your favorite number?"

            <input type="text" name="number"/>

        <input type="submit"/>
    </form>
</Await>

Hi, I am coming from https://github.com/leptos-rs/leptos/discussions/1544.
I was wondering about ways to progressively enhance this form.
If we had a way to set <ActionForm target="" action=favorite_color_form>, then we could use the strategy above (using Await) when WASM/JS is not available.
Whem WASM/JS are available, we just follow the normal enhanced process.

I just realized that favorite_color_form will always be a POST request since the encoding is the default URL.

I am playing with the example above and I could not make it work properly.
As it is on the example, it only works if the user lands directly into the FavoriteColors component.
If you navigate to a page that contains the FavoriteColors component using router components, the Await will trigger a POST request to the server function.
Did anybody manage to make it work?


New style dstack

New style dstack to support double backprop.

Rebased on top of master.

jenkins, test this please

jenkins, test this please

jenkins, test this please

jenkins, test this please

LGTM!


Improved AutoSuggessBox & Prevent Close of Flyout

Considering #47
1. AutoSuggessBox.

[x] Do not auto-select the first element of the array.

Now if the user select the first element, all the events will return the value of Array[0]

[x] Dispatch 'Select' Event does not make sure to update the current value of the AutoSuggestBox

Fixed and now we will get the updated value.

[x] Adding the 'on:select' event on component allows better mobile performance

Added on select event,

[x] Don't auto select any element for just use the arrow key moving

Selections will be triggered with Enter key when focused on an item
2. Flyout

[x] Don't auto close the flyout when push Enter key

I'll take some time later to look over some changes, although just as an initial thought I think that arrow keys should still move selection as to mirror the behavior of the native control. AutoSuggestBox has probably given me the most trouble out of any of the components in terms of behavior due to how inconsistently it tends to behave, so i'll have to think some things through. 👍

I agree that the AutoSuggestBox is quite a complex component. And yes, come to think of it, in certain cases it should auto-select with the arrow keys. What do you think about an optional prop? <AutoSuggestBox enableAutoSelect={true} /> or something like that?


Signal safety?

From my initial inspection, it looks like Sender::try_send is safe to use inside signal handlers. If this is case, it might be worth documenting since it's a compelling alternative to signal_hook::iterator::Signals.

Not quite - Sender::try_send() might allocate, and allocation might grab an internal lock inside the allocator, do syscalls etc. So it's definitely not signal safe :)