Problemă instalare

Am încercat să instalez portalul folosind https://github.com/civictechro/auth-sso/wiki/Tutorial.
Am instalat gitul, Visual Studio-ul, .Net-ul și celelalte. Am făcut baza de date din php cu atribuirea userului pentru baza de date, am dat <npm install bower -g>  și <npm install gulp -p> , iar apoi am intrat în cmd, \auth-sso, am rulat <git submodule update --init --recursive>, iar apoi <dotnet restore>, moment in care am primit erori:
E:\CivicTech\auth-sso\src\GovITHub.Auth.Identity\GovITHub.Auth.Identity.csproj : error NU1605:  GovITHub.Auth.Identity (>= 1.0.0) -> Localization.SqlLocalizer (>= 1.0.10) -> Microsoft.NETCore.App (>= 1.1.2) \r [E:\CivicTech\auth-sso\GovITHub.Auth.Identity.sln]
E:\CivicTech\auth-sso\src\GovITHub.Auth.Identity\GovITHub.Auth.Identity.csproj : error NU1605:  GovITHub.Auth.Identity (>= 1.0.0) -> Microsoft.NETCore.App (>= 1.1.1) [E:\CivicTech\auth-sso\GovITHub.Auth.Identity.sln]
E:\CivicTech\auth-sso\src\GovITHub.Auth.Identity\GovITHub.Auth.Identity.csproj : error NU1605: Detected package downgrade: Microsoft.NETCore.App from 1.1.2 to 1.1.1. Reference the package directly from the project to select a different version. \r [E:\CivicTech\auth-sso\GovITHub.Auth.Identity.sln]
E:\CivicTech\auth-sso\src\GovITHub.Auth.Identity\GovITHub.Auth.Identity.csproj : error NU1605:  GovITHub.Auth.Identity (>= 1.0.0) -> Microsoft.VisualStudio.Web.CodeGeneration.Design (>= 1.1.1) -> Microsoft.NETCore.App (>= 1.1.2) \r [E:\CivicTech\auth-sso\GovITHub.Auth.Identity.sln]
E:\CivicTech\auth-sso\src\GovITHub.Auth.Identity\GovITHub.Auth.Identity.csproj : error NU1605:  GovITHub.Auth.Identity (>= 1.0.0) -> Microsoft.NETCore.App (>= 1.1.1) [E:\CivicTech\auth-sso\GovITHub.Auth.Identity.sln]
E:\CivicTech\auth-sso\src\GovITHub.Auth.Common\GovITHub.Auth.Common.csproj : error NU1605: Detected package downgrade: Microsoft.NETCore.App from 1.1.2 to 1.1.1. Reference the package directly from the project to select a different version. \r [E:\CivicTech\auth-sso\GovITHub.Auth.Identity.sln]
E:\CivicTech\auth-sso\src\GovITHub.Auth.Common\GovITHub.Auth.Common.csproj : error NU1605:  GovITHub.Auth.Common (>= 1.0.0) -> Localization.SqlLocalizer (>= 1.0.10) -> Microsoft.NETCore.App (>= 1.1.2) \r [E:\CivicTech\auth-sso\GovITHub.Auth.Identity.sln]
E:\CivicTech\auth-sso\src\GovITHub.Auth.Common\GovITHub.Auth.Common.csproj : error NU1605:  GovITHub.Auth.Common (>= 1.0.0) -> Microsoft.NETCore.App (>= 1.1.1) [E:\CivicTech\auth-sso\GovITHub.Auth.Identity.sln]```

Pare a fi o problema de versiune .net core 2.0 preview. Eu am instalat local 1.0.4, nu am facut inca trecerea la 2.0.
Ce ouput primesti cand rulezi: dotnet --version?

2.0.0```

Temporar, pana cand facem upgrade-ul la 2.0, instaleaza te rog o versiune mai veche:
https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.0.5-download.md
Daca primesti eroarea de mai sus:

uninstall 1.0.5
uninstall 2.0
install 1.0.5

E:\CivicTech\auth-sso>dotnet --version A fatal error occurred, the required library hostfxr.dll could not be found at C:\Program Files\dotnet

uninstall tot. install 1.0.5

@arcilli Pe mine m-a ajutat asta:
https://stackoverflow.com/questions/42709533/detected-package-downgrade-warning-dotnet-core-vs-2017

L-am rezolvat dându-i repair. Acum la dotnet run primesc blank page cand dau sa accesez localhost:5000 și niște fail-uri la rulare dotnet.
      Executed action GovITHub.Auth.Identity.Controllers.HomeController.Error (GovITHub.Auth.Identity) in 23.015ms
fail: Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware[0]
      An exception was thrown attempting to execute the error handler.
MySql.Data.MySqlClient.MySqlException: AuthenticationFailed ---> MySql.Data.MySqlClient.MySqlException: Access denied for user '<user>'@'localhost' (using password: YES)
   at MySql.Data.MySqlClient.MySqlStream.ReadPacket()
   at MySql.Data.MySqlClient.Authentication.MySqlAuthenticationPlugin.ReadPacket()
   --- End of inner exception stack trace ---
   at MySql.Data.MySqlClient.Authentication.MySqlAuthenticationPlugin.AuthenticationFailed(Exception ex)
   at MySql.Data.MySqlClient.Authentication.MySqlAuthenticationPlugin.ReadPacket()
   at MySql.Data.MySqlClient.Authentication.MySqlAuthenticationPlugin.Authenticate(Boolean reset)
   at MySql.Data.MySqlClient.NativeDriver.Open()
   at MySql.Data.MySqlClient.Driver.Open()
   at MySql.Data.MySqlClient.Driver.Create(MySqlConnectionStringBuilder settings)
   at MySql.Data.MySqlClient.MySqlPool.CreateNewPooledConnection()
   at MySql.Data.MySqlClient.MySqlPool.GetPooledConnection()
   at MySql.Data.MySqlClient.MySqlPool.TryToGetDriver()
   at MySql.Data.MySqlClient.MySqlPool.GetConnection()
   at MySql.Data.MySqlClient.MySqlConnection.Open()
   at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.Open()
   at Microsoft.EntityFrameworkCore.Query.Internal.QueryingEnumerable.Enumerator.BufferlessMoveNext(Boolean buffer)
   at Microsoft.EntityFrameworkCore.Query.QueryMethodProvider.<_ShapedQuery>d__3`1.MoveNext()
   at Microsoft.EntityFrameworkCore.Query.Internal.LinqOperatorProvider.<_TrackEntities>d__15`2.MoveNext()
   at Microsoft.EntityFrameworkCore.Query.Internal.LinqOperatorProvider.ExceptionInterceptor`1.EnumeratorExceptionInterceptor.MoveNext()
   at System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable`1 source, Func`2 keySelector, Func`2 elementSelector, IEqualityComparer`1 comparer)
   at Localization.SqlLocalizer.DbStringLocalizer.SqlStringLocalizerFactory.GetAllFromDatabaseForResource(String resourceKey)
   at Localization.SqlLocalizer.DbStringLocalizer.SqlStringLocalizerFactory.Create(Type resourceSource)
   at Microsoft.Extensions.Localization.StringLocalizer`1..ctor(IStringLocalizerFactory factory)
   at lambda_method(Closure , ServiceProvider )
   at Microsoft.Extensions.Internal.ActivatorUtilities.GetService(IServiceProvider sp, Type type, Type requiredBy, Boolean isDefaultParameterRequired)
   at lambda_method(Closure , IServiceProvider , Object[] )
   at Microsoft.AspNetCore.Mvc.Internal.TypeActivatorCache.CreateInstance[TInstance](IServiceProvider serviceProvider, Type implementationType)
   at Microsoft.AspNetCore.Mvc.Controllers.DefaultControllerFactory.CreateController(ControllerContext context)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeNextResourceFilter>d__22.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ResourceExecutedContext context)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeAsync>d__20.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Builder.RouterMiddleware.<Invoke>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at IdentityServer4.Hosting.IdentityServerMiddleware.<Invoke>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at IdentityServer4.Hosting.FederatedSignOutMiddleware.<Invoke>d__6.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at IdentityServer4.Hosting.AuthenticationMiddleware.<Invoke>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Cors.Infrastructure.CorsMiddleware.<Invoke>d__7.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at IdentityServer4.Hosting.BaseUrlMiddleware.<Invoke>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.<Invoke>d__6.MoveNext()
fail: Microsoft.AspNetCore.Server.Kestrel[13]```

Access denied for user '<user>'@'localhost' (using password: YES) -

in connectionsstrings.json ai setarile pt baza de date la inceput (search dupa <user>)

@tzapzoor, mersi. Le-am actualizat și am aceeași eroare, + că încă la dotnet restore primesc warningul cu versiunea de .NET
C:\Program Files\dotnet\sdk\1.0.4\NuGet.targets(97,5): warning :  GovITHub.Auth.Common.Tests (>= 1.0.0) -> GovITHub.Auth.Common (>= 1.0.0) -> Localization.SqlLocalizer (>= 1.0.10) -> Microsoft.NETCore.App (>= 1.1.2) \r [E:\CivicTech\auth-sso\GovITHub.Auth.Identity.sln]
C:\Program Files\dotnet\sdk\1.0.4\NuGet.targets(97,5): warning :  GovITHub.Auth.Common.Tests (>= 1.0.0) -> Microsoft.NETCore.App (>= 1.1.1) [E:\CivicTech\auth-sso\GovITHub.Auth.Identity.sln]```

@arcilli in folderul test mai este un proiect care trebuie reparat si el la fel cum le-ai reparat pe celelalte. Daca nu merge aceeasi solutie pe care ai folosit-o, poti incerca link-ul pe care l-am pus mai sus.

@tzapzoor, i-am șters liniile alea din fiecare proiect. La dotnet run intră-n buclă infinită și la final

Unhandled Exception: System.Exception: Could not resolve a service of type 'GovITHub.Auth.Common.Data.ConfigurationDataInitializer' for the parameter 'cfgDataInitializer' of method 'Configure' on type 'GovITHub.Auth.Identity.Startup'. ---> System.ArgumentNullException: Value cannot be null.
Parameter name: value
   at Microsoft.EntityFrameworkCore.Utilities.Check.NotEmpty(String value, String parameterName)
   at Microsoft.EntityFrameworkCore.Infrastructure.RelationalOptionsExtension.set_ConnectionString(String value)
   at MySQL.Data.Entity.Extensions.MySQLDbContextOptionsExtensions.UseMySQL(DbContextOptionsBuilder optionsBuilder, String connectionString, Action`1 mysqlOptionsAction)
   at GovITHub.Auth.Identity.Startup.<>c__DisplayClass4_0.<ConfigureServices>b__4(DbContextOptionsBuilder builder) in E:\GovITHub\auth-sso\src\GovITHub.Auth.Identity\Startup.cs:line 102
   at Microsoft.Extensions.DependencyInjection.EntityFrameworkServiceCollectionExtensions.DbContextOptionsFactory[TContext](IServiceProvider applicationServiceProvider, Action`2 optionsAction)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScoped(ScopedCallSite scopedCallSite, ServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, ServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScoped(ScopedCallSite scopedCallSite, ServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, ServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitTransient(TransientCallSite transientCallSite, ServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ServiceProvider.<>c__DisplayClass16_0.<RealizeService>b__0(ServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService(IServiceProvider provider, Type serviceType)
   at Microsoft.AspNetCore.Hosting.Internal.ConfigureBuilder.Invoke(Object instance, IApplicationBuilder builder)
   --- End of inner exception stack trace ---
   at Microsoft.AspNetCore.Hosting.Internal.ConfigureBuilder.Invoke(Object instance, IApplicationBuilder builder)
   at Microsoft.AspNetCore.Hosting.ConventionBasedStartup.Configure(IApplicationBuilder app)
   at Microsoft.AspNetCore.Hosting.Internal.WebHost.BuildApplication()
   at Microsoft.AspNetCore.Hosting.WebHostBuilder.Build()
   at GovITHub.Auth.Identity.Program.Main(String[] args) in E:\GovITHub\auth-sso\src\GovITHub.Auth.Identity\Program.cs:line 10


[GSoC] Visible Component Extensions

Added isContainer, hasCustomMock properties to @DesignerComponent
Add the ability to load Mock scripts for external components
Add the ability to instantiate Mocks from a JS file
Add a fallback implementation for external components which do not provide a custom Mock [WIP]
Added a registry to hold Mock component factories
Added a MockScriptsManager which is responsible for loading, unloading of Mocks

Bugs:

Mocks are not updated when an extension is upgraded.

@pavi2410 Could you write an overview in the pull request to describe what features are in the pull request and how it might be tested?

Sure, I will write an overview for this PR and regarding testing... I haven't thought about it yet. But it's a good idea to write tests. It might save my time needed to test by hand.

@SusanRatiLane I have added commits from https://github.com/pavi2410/appinventor-sources/tree/mvce2 here.

@ewpatton @pavi2410 Is this still being actively developed?

@ewpatton @pavi2410 Is this still being actively developed?

Nope


liz opt out analytics

@lizkirk82  please install this plugin for firefox browser on your laptop.  It will opt you out of google analytics.


Unit file zerotier-systemd-manager.timer does not exist.

Trying to install til on Ubuntu 20.04 I get:
sudo dpkg -i zerotier-systemd-manager_0.3.1_linux_amd64.deb

(Reading database ... 249810 files and directories currently installed.)
Preparing to unpack zerotier-systemd-manager_0.3.1_linux_amd64.deb ...
Unpacking zerotier-systemd-manager (0.3.1) over (0.2.1) ...
+ systemctl daemon-reload
Setting up zerotier-systemd-manager (0.3.1) ...
+ systemctl daemon-reload
+ systemctl enable zerotier-systemd-manager.timer
Failed to enable unit: Unit file zerotier-systemd-manager.timer does not exist.
dpkg: error processing package zerotier-systemd-manager (--install):
 installed zerotier-systemd-manager package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 zerotier-systemd-manager

Any ideas?

Bahr, had some old config files layout around :sweat_smile:
sudo dpkg --purge zerotier-systemd-manager
did the trick :pray:


Not compatible with new jQuery versions (1.9.1 nor 2.0.0)

Not working with jQuery 1.9.1, nor 2.0.0.

Pity this plugin hasn't been updated for a couple of years, it seems to be quite unique.


allow_reuse option on REST calls

Is it possible to specify the allow_reuse parameter when triggering a published pipeline run via REST call? Is there any way to accomplish similar functionality?

@jwa5426 Hope you have self resolved the issue and hence closed it.
If that's not the case and if the issue is related to particular Azure document then as this azure-docs repository deals about feedback related to particular Azure document page (like correcting doc bugs, doc enhancements, product issues related to wrong doc instructions, etc.) so please share the Azure document link and more context around the feedback. Also FYI, going forward if you want to share any feedback related to particular Azure document then I suggest you to please click on 'This page' option at the bottom of referred Azure document and share the feedback. For reference, adding screenshot of the 'Feedback' section that you could ideally find at bottom of an Azure document.

But on the other hand, if you need help in resolving a product related issue or question then I suggest you to ask the question in public forums like Microsoft Q&A, etc. but not here in this azure-docs repository. Hope this clarifies.

@jwa5426 Hope you have self resolved the issue and hence closed it.
If that's not the case and if the issue is related to particular Azure document then as this azure-docs repository deals about feedback related to particular Azure document page (like correcting doc bugs, doc enhancements, product issues related to wrong doc instructions, etc.) so please share the Azure document link and more context around the feedback. Also FYI, going forward if you want to share any feedback related to particular Azure document then I suggest you to please click on 'This page' option at the bottom of referred Azure document and share the feedback. For reference, adding screenshot of the 'Feedback' section that you could ideally find at bottom of an Azure document.

But on the other hand, if you need help in resolving a product related issue or question then I suggest you to ask the question in public forums like Microsoft Q&A, etc. but not here in this azure-docs repository. Hope this clarifies.


feat: support group and teams

Describe the solution you'd like
Add support for group and team based ACLs
Be able to specify repo ACLs for teams and users. Set the default to read-write for new repositories and read-only for public repositories.
Similar to what Gitolite ACLs offer but using SSH instead. Perhaps support importing Gitolite conf syntax

Support for groups and teams is an amazing idea!
If you're already touching the authentication / authorization parts of soft-serve, what do you think about adding support for ldap auth, too?

Hey @jon4hz! That's a fond idea. Soft Serve now can support new backends as long as they implement the interface. The idea I have in mind is to implement different backends as Go plugins.
This is still in the works and the API is subject to change. I would love to hear your thoughts on this 🙂

Hi, sorry for getting back so late. To be honest, I never implemented ldap as backend myself so I'm not sure what the obstacles are. However I did self host gitlab for a short time and I think they are provisioning the ldap users in the same db as the "normal" users.


Remove cluster name local restriction

Issue:
https://github.com/rancher/fleet/issues/1489
Problem
Users can't migrate the local cluster to the fleet-default workspace. Cluster creation is rejected by the webhook. This is the error displayed:
[ERROR] error syncing ‘local’: handler provisioning-cluster-create: failed to create fleet-default/local [provisioning.cattle.io/v1](http://provisioning.cattle.io/v1), Kind=Cluster for provisioning-cluster-create local: admission webhook “[rancherauth.cattle.io](http://rancherauth.cattle.io/)” denied the requeset: cluster name must be 63 characters or fewer, cannot be “local” nor of the form “c-xxxxx”, requeuing

Solution
Remove the local cluster name validation, so users are able to move the local cluster to a different workspace.

Moving the local cluster should not be supported. We will clearly state that moving the local cluster is not supported and hide the move button from the UI


Add a custom badge for SQLAlchemy in README's tech stack section

Create a badge for SQLAlchemy using its logo and put it under the Tech Stack section.
Image: https://www.sqlalchemy.org/img/sqla_logo.png
Tools like shields.io or any other relevant tools can be used to create a custom badge (Just like already mentioned in the README)
Steps:

Go to https://shields.io/
Scroll below to the Your Badge Section.

Leave the label field empty.
Populate the message as SQLAlchemy
Use the colour blue.
Click on the make badge button.
You'll get a URL for the badge.
Add it to the README's tech stack section below the already existing Badges there.

I wish to do this

Hello @Aditya-Gupta1
Thank you for mentioning this issue. I would like to work on this. Please assign this to me and I'll work on it.

I wish to do this

Sure @issac5693. Go ahead and raise a PR for it! 👍
(In an unlikely event if you're not able to raise a PR, please let us know so that someone else may contribute towards it.)

Hello @Aditya-Gupta1
Thank you for mentioning this issue. I would like to work on this. Please assign this to me and I'll work on it.

Hey @AnimeshKumar923. The issues are assigned on a first come first serve basis. But don't worry, there are a lot of things to work on here and I'll let you know once other issues are ready to be worked upon. 😃

Okay. Thank you!

Please assign me to the 20th(contribute.md) one, not the 17th
On Thu, 6 Oct, 2022, 3:27 pm Aditya Gupta, @.***> wrote:

Assigned #17
https://github.com/Aditya-Gupta1/job-application-cli/issues/17 to
@issac5693 https://github.com/issac5693.
—
Reply to this email directly, view it on GitHub
https://github.com/Aditya-Gupta1/job-application-cli/issues/17#event-7532850981,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVDHXMW6OUEVLAZEDWBAHTTWB2PBDANCNFSM6AAAAAAQ6FV6VY
.
You are receiving this because you were assigned.Message ID:
@.***
com>

I've added the steps to complete this issue @issac5693.
Issue #20 can't be assigned as of now since I'm still working on publishing this app to PyPI. Only then I will be able to lay out the steps for contribution for this repo.
Let me know if you still wish to complete #17.

Thanks a lot bro, I'll complete #17
On Thu, 6 Oct, 2022, 4:08 pm Aditya Gupta, @.***> wrote:

I've added the steps to complete this issue @issac5693
https://github.com/issac5693.
Issue #20 https://github.com/Aditya-Gupta1/job-application-cli/issues/20
can't be assigned as of now since I'm still working on publishing this app
to PyPI. Only then I will be able to lay out the steps for contribution for
this repo.
Let me know if you still wish to complete #17
https://github.com/Aditya-Gupta1/job-application-cli/issues/17.
—
Reply to this email directly, view it on GitHub
https://github.com/Aditya-Gupta1/job-application-cli/issues/17#issuecomment-1269782085,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVDHXMU3LUP6FDS44ZGV65TWB2T27ANCNFSM6AAAAAAQ6FV6VY
.
You are receiving this because you were mentioned.Message ID:
@.***>


Flink-5976 Refactoring duplicate Tokenizer in flink-test

There are some duplicate code like this in flink-test, I think refactor this will be better.
public final class Tokenizer implements FlatMapFunction<String, Tuple2<String, Integer>> {

	@Override
	public void flatMap(String value, Collector<Tuple2<String, Integer>> out) {
		// normalize and split the line
		String[] tokens = value.toLowerCase().split("\\W+");

		// emit the pairs
		for (String token : tokens) {
			if (token.length() > 0) {
				out.collect(new Tuple2<String, Integer>(token, 1));
			}
		}
	}
}

Hey @liuyuzhong7! Thanks for the contribution. A few notes:

Could you rebase your branch on top of the master branch. We don't do merge commits. After you've rebased the branch, I will review it (you can force push to your PR branch)
Could you rename the commits and this PR to:[FLINK-5976] [tests] Deduplicate Tokenizer in tests

Could you unset the fix version in the JIRA and set affects version to 1.2.0?

@uce Thanks for review. OK, I'll do it later.


Binding from module to Windows File System

I am running the IOT Edge for Windows 1.1 and am attempting to get persistent storage working.  It appears that IOT Edge for Windows 1.1 runs a Linux docker container that then runs the agent/hub/custom modules inside the linux docker container.  I have been unable to get persistent storage working and cannot find a guide on how to make it work such that the container has access to the Windows file system.
I have reviewed this document, but it does not get the module access to the Windows file system.  https://docs.microsoft.com/en-us/azure/iot-edge/how-to-access-host-storage-from-module?view=iotedge-2018-06.
I tried adding this to the container create options, but it did not work.
{
  "HostConfig": {
    "Binds": [
      "c:\\temp\\Edge\\IotEdgeModule1:/tmp/IotEdgeModule1"
    ]
  }
}

I got this error:
Sep 17 14:44:46 BLAZIN-EFLOW iotedged[6562]: 2021-09-17T14:44:46Z [WARN] - Could not create module iotedgemodule1005
Sep 17 14:44:46 BLAZIN-EFLOW iotedged[6562]: 2021-09-17T14:44:46Z [WARN] -         caused by: invalid mode: /tmp/IotEdgeModule1

Can you please provide the details on how to make this work?

@Steve0212a,
We currently do not support file/folder sharing between the Linux VM and host, but it is something that we are considering to offer in the future.  I believe that binding approach would only work inside the VM.
Could I get you to contact me directly at<EMAIL_ADDRESS>and share whatever details of your scenario that you can with us so that we can take this into consideration as we are exploring the feasibility of enabling this functionality.
Terry Warwick
Microsoft

Hi,
We currently do not support file/folder sharing between the Linux VM and host. For certificate management for IoT Edge, the approach would be the following:

Deploy EFLOW
Copy the certificates from the Windows host to the EFLOW VM using the Copy-EflowVmFile
Provision EFLOW
[Manage certificates on an IoT Edge device]https://docs.microsoft.com/en-us/azure/iot-edge/how-to-manage-device-certificates?view=iotedge-2020-11&tabs=linux

Thanks,
Francisco

Hi, sorry to bring this up on a closed thread, but this is a pretty critical feature for us to begin using EFLOW. Currently we are using Windows containers because they support this but we would really like to switch to EFLOW. Is there any chance that this feature would be supported in a future version of EFLOW and if so an estimated timeline on that? I am willing to share more specific details of our scenario in case it would help or if there is any potential workaround. Thanks!

@Steve0212a,
We currently do not support file/folder sharing between the Linux VM and host, but it is something that we are considering to offer in the future. I believe that binding approach would only work inside the VM.
Could I get you to contact me directly at<EMAIL_ADDRESS>and share whatever details of your scenario that you can with us so that we can take this into consideration as we are exploring the feasibility of enabling this functionality.
Terry Warwick Microsoft

Hi, @TerryWarwick , @fcabrera23. Have you explored the possibility of sharing file/folder between the VM and host?
Background: On our pure Linux devices we are collecting files from shared folders on Windows machines. On some sites we currently can't install separate Linux-devices and have to use EFLOW in these cases.

Hi @bkarrlander,
We are currently working on the file/folder sharing feature, and we expect to have it for our June update, although final date still TBD.
Thanks,
Francisco

Thank you, @fcabrera23. Sounds great.
Regards,
Björn

Hi @bkarrlander,
We are currently working on the file/folder sharing feature, and we expect to have it for our June update, although final date still TBD.
Thanks, Francisco

Hi @fcabrera23, do you have any update on the status of this feature?

Hi @andrewhickman,
We plan to release the feature in our next EFLOW CR release. This update will contain considerable improvements (Folder sharing, Mariner2.0 upgrade, IoT Edge 1.3.0 upgrade), so we are making during that everything works fine. Probably will be released in 1-2 weeks.
Thanks,
Francisco

Hi @fcabrera23,
any news for that? We have the same problem...
We use it for differnt topics, for example we have etablished a deployment process (Bamboo pipline) for the published.nodes.json. And that is just one use case.
But I am strugle to draw the new migration concept, without the folder sharing.
And in the Securitiy review, everyone is very precise when it comes to such topics ;)
Thanks,
Matthias

Hi @Prov-Matthias,
We are releasing the Folder Sharing mechanism in our next EFLOW CR update, probably this week. This will only be supported for Windows 11 for the months while we work on the backport to Win10.
Thanks,
Francisco

Hi @fcabrera23,
Sounds very good :) Can I then assume that Win11 also means Windows Server 2022?
Thanks,
Matthias

Hi @Prov-Matthias,
Windows Server 2019/2022 will be considered in the future. Currently, we will only support Win10/11, although we are open to discussing it with customers.
Thanks,
Francisco

Hi @maggiojoe2,
Thanks for reaching out. We had a Windows dependency that was backported and released with 11C November update. This backporting will enable Folder sharing with Win10 (21H2), Win11, and Win Server 2019 and 2022.
However, we started some tests with these new versions last week, and we found some bugs. We expect to investigate these bugs this week and will have more clarity on an ETA for these versions.
Thanks,
Francisco


How to run wireproxy silently in the background

I run winproxy with the command nohup wireproxy /etc/wireguard/proxy.conf >/dev/null 2>&1 & .
I want to run it in Systemd.  There is a  problem. Stuck for a long time, eventually showing timeout.
I think it's caused by windproxy running in the foreground
[Unit]
Description=WireProxy for WARP
After=network.target
Wants=network.target
Documentation=https://github.com/octeep/wireproxy

[Service]
Type=forking
ExecStart=/usr/bin/wireproxy /etc/wireguard/proxy.conf
RemainAfterExit=yes
Restart=always

[Install]
WantedBy=multi-user.target

I don't use systemd so I can't test this out, but have you tried Type=simple instead of Type=forking?

I think it would be best to add parameters to run in the background in next verion. For example
wireproxy /etc/wireguard/proxy.conf -d

Thank you!

I think it would be best to add parameters to run in the background in next verion. For example
wireproxy /etc/wireguard/proxy.conf -d

Thank you!

I'll address this in the first "official" release version of wireproxy. I think after getting feedbacks from different communities, the codebase is mature enough. I'm gonna rework the command line parsing part, add this feature, and bump the version to v1.0

Glad to hear this exciting news.
Many WARP users have reported such a need.
I also hope the parameter to close wireproxy.

Glad to hear this exciting news. Many WARP users have reported such a need. I also hope the parameter to close wireproxy.

How exactly would the parameter closing wireproxy looks like? Would it be something like wireproxy --close? I am not sure how that work with multiple instances of wireproxy.

How abt like screen?
case 1: one session
[root@srv21706 ~]# screen -SX a quit
[root@srv21706 ~]# screen -ls
No Sockets found in /var/run/screen/S-root.

[root@srv21706 ~]# screen -USdm a
[root@srv21706 ~]# screen -ls
There is a screen on:
        11609.a (Detached)
1 Socket in /var/run/screen/S-root.

[root@srv21706 ~]# screen -SX a quit
[root@srv21706 ~]# screen -ls
No Sockets found in /var/run/screen/S-root.

case 2:  multiple sessions
[root@srv21706 ~]# screen -USdm a
[root@srv21706 ~]# screen -USdm a
[root@srv21706 ~]# screen -USdm a
[root@srv21706 ~]# screen -ls
There are screens on:
        12705.a (Detached)
        12676.a (Detached)
        12631.a (Detached)
3 Sockets in /var/run/screen/S-root.

[root@srv21706 ~]# screen -SX 12705 quit
[root@srv21706 ~]# screen -ls
There are screens on:
        12676.a (Detached)
        12631.a (Detached)
2 Sockets in /var/run/screen/S-root.

[root@srv21706 ~]# screen -SX 12631.a quit
[root@srv21706 ~]# screen -ls
There is a screen on:
        12676.a (Detached)
1 Socket in /var/run/screen/S-root.

Ah, so each instance of wireproxy is named and you can close them by specifying the name of the instance of the wireproxy you want to close. I think we can do that. This also ties in to one of the task in #16 too. I will address this in the future.

I think it would be best to add parameters to run in the background in next verion. For example
wireproxy /etc/wireguard/proxy.conf -d

Thank you!

Daemon flag has been implemented in the latest commit, note that there is also a slight change to how the path of the configuration is passed to wireproxy as well. I've tested the daemon feature on my OpenBSD and Linux machines. Can you confirm that it works for you as well?

@fscarmen also did you manage to get wireproxy working with cloudflare warp? I'm interested in using it as well.

@fscarmen also did you manage to get wireproxy working with cloudflare warp? I'm interested in using it as well.
Edit: nvm got it working

As a bit of off-topic discussion: I wanted to make it working for torrenting, but doesn't look like it works :( the only thing that is working is HTTP tracker updates

Can you confirm that it works for you as well?

Quite practical, now I use systemctl restart wgcf to restart the warp service to indirectly change the warp ip to unlock Netflix.

@fscarmen also did you manage to get wireproxy working with cloudflare warp? I'm interested in using it as well.
Edit: nvm got it working

Yes.

Do you mean by CloudFlare WARP Client for Linux?
https://blog.cloudflare.com/announcing-warp-for-linux-and-proxy-mode
Tonight I will add wireproxy options to the menu.

I don't use systemd so I can't test this out, but have you tried Type=simple instead of Type=forking?

It works. Ths.
'Type=simple' is default, so i remove it.
Now the systemd file content is as follow. ( /usr/lib/systemd/system/wireproxy.service )
[Unit]
Description=WireProxy for WARP
After=network.target
Documentation=https://github.com/fscarmen/warp
Documentation=https://github.com/octeep/wireproxy
[Service]
ExecStart=/usr/bin/wireproxy /etc/wireguard/proxy.conf
RemainAfterExit=yes
Restart=always
[Install]
WantedBy=multi-user.target

I turn on the WireProxy service by systemctl enable --now wireproxy
turn it off by systemctl disable --now wireproxy
change the warp ip (restart service) by systemctl restart wireproxy

I don't use systemd so I can't test this out, but have you tried Type=simple instead of Type=forking?

It works. Ths. 'Type=simple' is default, so i remove it. Now the systemd file content is as follow. ( /usr/lib/systemd/system/wireproxy.service )
[Unit]
Description=WireProxy for WARP
After=network.target
Documentation=https://github.com/fscarmen/warp
Documentation=https://github.com/octeep/wireproxy
[Service]
ExecStart=/usr/bin/wireproxy /etc/wireguard/proxy.conf
RemainAfterExit=yes
Restart=always
[Install]
WantedBy=multi-user.target

I turn on the WireProxy service by systemctl enable --now wireproxy turn it off by systemctl disable --now wireproxy change the warp ip (restart service) by systemctl restart wireproxy

Are you using the latest version? It should be ExecStart=/usr/bin/wireproxy -c /etc/wireguard/proxy.conf.

Are you using the latest version? It should be ExecStart=/usr/bin/wireproxy -c /etc/wireguard/proxy.conf.

Not yet. I fail to cross compile wireproxy in action. The previous version was ok. I guess there is no file: main.go

Are you using the latest version? It should be ExecStart=/usr/bin/wireproxy -c /etc/wireguard/proxy.conf.

Not yet. I fail to cross compile wireproxy in action. The previous version was ok. I guess there is no file: main.go

Ah yes, you should compile with this command: go build ./cmd/wireproxy instead. I will add an instruction in README. Alternatively, you can find it on the Actions tab. I setup a CI to build it for every commits.

@fscarmen do you mind moving this conversation to discussion? I don't think it's appropiate to discuss on an issue tracker. https://github.com/octeep/wireproxy/discussions/25


feat: Bump version

Git fix for https://github.com/Tonomy-Foundation/Tonomy-ID-SDK/actions/runs/8528535400/job/23362637479

:tada: This PR is included in version 0.19.0-development.7 :tada:
The release is available on:

npm package (@development dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


SHOW PARTITIONS FROM  is slow

SHOW PARTITIONS FROM  is slow if there are many partitions.
Talked to Chris, and we'll introduce a map to avoid duplicate computation.

https://github.com/joy-yao/presto/commit/bfbc7b11757346f9012844168a1c4f70ef1f3f46

Merged.


Setup good-fences in tree

Description
Uses https://www.npmjs.com/package/good-fences to specify and enforce which dependencies are allowed within tree.
PR Checklist

Use the check-list below to ensure your branch is ready for PR. If the item is not applicable, leave it blank.

[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.
[ ] My code follows the code style of this project.
[ ] I ran the lint checks which produced no new errors nor warnings for my changes.
[ ] I have checked to ensure there aren't other open Pull Requests for the same update/change.

Does this introduce a breaking change?

[ ] Yes
[x] No

I don't know how to properly integrate this with our incremental build. As was, it warned with:

@fluid-internal/tree: warning: non-conformant script "build"
@fluid-internal/tree: warning:   expect: concurrently npm:build:compile npm:lint && npm run build:docs
@fluid-internal/tree: warning:   actual: concurrently npm:build:compile npm:lint npm:fence && npm run build:docs

If I move the check into lint, it warns with non-conformant script "lint" instead. Similar issue if I make it part of test.
I suspect explicit support would have to be added to fluid-build if we want to support good-fences being run as part of the build.
I however can pragmatically invoke good-fences as a mocha test. I have made this change.

It might be worth adding some simple "_comment" (or something) blocks to the fence files to explain why particular dependency edges are being enforced. Will make it easier for devs to reason about whether or not they can make changes in the future.

It might be worth adding some simple "_comment" (or something) blocks to the fence files to explain why particular dependency edges are being enforced. Will make it easier for devs to reason about whether or not they can make changes in the future.
Excited to see this added to the repo though! I like this tool :)

Right now the actual fences are very much in flux: I'll be updating / clarifying the actual fences in later changes.
For documenting the fence files, it looks like it would be a trivial change to good-fences to make it support json with comments (like tsc does for its config files). I'll look into making a PR upstream for that since I really dislike adding comment fields to json.


req.logIn calls callback twice... sometimes

I've got some code that looks just like this:
console.log('Calling req.logIn()');
req.logIn(session, function (err) {
  console.log('req.logIn() Complete');
  if (err) {
    console.error('[ERROR]');
    console.error(err)
    next(err);
    return;
  }

  console.log('[SUCCESS]');
  next();
  return;
});

In my serialize function I console.log("Serialize complete") on the line before I call done.
And the output I get from a login is (sometimes) this:
Calling req.logIn()
Serialize complete
req.logIn() Complete
SUCCESS
req.logIn() Complete
ERROR
[TypeError: Cannot call method 'indexOf' of undefined]

I opened up node_modules/passport/lib/passport/http/request.js and added a console.log inside this._passport.instance.serializeUser(user, function(err, obj) { ... } and found that it fires twice even though I've verified that my serialize function is only called once and also that I'm only calling done once.
Any ideas?

I can confirm that this is indeed the behavior of req.login(). If the callback throws an (unexpected) Error the callback is called again with that error. Weird?

Can confirm as well.

I can confirm as well in the latest version 0.4.0

Same problem in last version 0.0.4
Also happens with strategy: passport-oauth (2.0)

+1


Completion selections don't change the sorting

#22839 said the recent selection will be pre-selected. However, the Dictionary Completion extension seems not to benefit from this. Is there anything we should do on the extension side?

Do have the setting editor.suggestSelection configured? What is its value?

I didn't change it. It is the default value recentlyUsed.

Ok, you should use recentlyUsedByPrefix then, recentlyUsed stores selection only when typing, e.g a in your sample, hasn't selected a suggestion

Thank you! recentlyUsedByPrefix does the trick.
However, it (recentlyUsed) is a bit confusing. Could you point me to the issue where this feature was introduced, if there is one?


Materialize Button Going Dark on Hover when using in Angular 2 .

When on hover why does it turn black whereas it should glow right ?

Please fill out the issue template  and also make sure to read out contributing guidelines.

@rahulrsingh09 do you use the waves-white class?


all_substrate.pkl

Thanks for your excellent work on ESP. I am wondering where can i find the all_substrate.pkl? Thanks. Is the one called model_ESM_binary_A100_epoch_1_new_split.pkl ？

When you downloaded the data.zip file from zenodo as specfified on the Readme page, after unzipping you should find the all_substrates.pkl file in the folder "data\additional_data".


Fix failing CI.

A previous PR added a third-party tool, cargo nono, in an attempt to
check whether the crate would be no_std compatible.  Because of issues
with the no_std ecosystem, this is nontrivial to check.
For instance, build-dependencies and dependencies have unified feature
selection (https://github.com/rust-lang/cargo/issues/4866), so a build-
or dev- dependency of the crate may enable a std feature in a
transitive dependency.  This means that to actually test no_std
compatibility, what must be tested is the final no_std executable,
not its dependencies, and any errors in dependencies need to be traced
back from the final executable.
As a workaround, various third-party tools (like cargo nono) exist,
but the tool failed to build and broke CI.  As these tools are not as
well-maintained as the core Rust infrastructure, this commit removes
them entirely to reduce maintenance burden in this crate.  no_std
users should check no_std compatibility in their crates.

Closes #50 #51


Batch requests should return 200 OK if successfully processed (even with failed entries)

Describe the bug
Currently, we set the response status of the batch request to an error status when the batch contains one or more errors, but thats not right according to the spec:

When processing the batch, the HTTP response code is 200 Ok if the batch was processed correctly, regardless of the success of the operations within the Batch. To determine the status of the operations, look inside the returned Bundle. A response code on an entry of other than 2xx (200, 202 etc) indicates that processing the request in the entry failed.

To Reproduce
See BundleTest.testTransactionReadDeletedResources()
Expected behavior
A batch request should only return a 400/500 error if there is something wrong with the request itself, not for errors within the batched requests.

Touchstone results are still passing


Add Ambient Weather support

This is an update of my previous PR (#54) to add Ambient Weather support to homebridge-weather-plus. Sorry that it has taken me so long to update the PR for the changes to homebridge-weather-plus, but at the time I was forced to continue to use an older version of Homebridge by a different plugin and then I moved and didn't use Homebridge at all for several years.
I have a question about whether my code is properly setting the station's ObservationTime value. As far as I can this this characteristic is the observation's time in HH:MM:SS format in the time zone that Homebridge is running in. Is that correct?

Any idea of when this update might be available?  I'm excited to give it a try and stop using Weather Underground for this!

I have a question about whether my code is properly setting the station's ObservationTime value. As far as I can this this characteristic is the observation's time in HH:MM:SS format in the time zone that Homebridge is running in. Is that correct?

It looks like different apis implementations handle this differently. OWM and WeeWX are using the timezone of the weather location. WU and Weatherflow are using the device timezone. I could make arguments for both variants :) . What do u prefer?

It looks like different apis implementations handle [ObservationTime] differently. OWM and WeeWX are using the timezone of the weather location. WU and Weatherflow are using the device timezone. I could make arguments for both variants :) . What do u prefer?

It appears that ObservationTime is displayed in the Eve app but I don't see it otherwise used. I'm guessing that the Eve app doesn't adjust it for where my phone is, so if the weather station in in timezone A, homebridge is in timezone B, and my phone is in timezone C, then I would probably prefer the observation time to be reported in timezone C, but since that isn't possible then I think that my second choice would be timezone A. (I just checked by changing the timezone on my phone and found that Eve does not adjust the observation time.)
My current PR wasn't setting the timezone at all, just using UTC. I'll update it to use the weather station timezone.

Is there a way for me to test this new code?  I'm currently still running on v3.3.3 because 3.3.5 broke the wind speed calculation from Weather Underground and hasn't been fixed yet (open issue).  I'd prefer to have this direct integration with Ambient Weather.

Now something is broken with my station and Weather Underground.  I'd really like to have this new update to have native Ambient Weather support.
@dhull @naofireblade Do you expect to have this code live soon?

I just migrated off the deprecated request package, #150 . I would be great if you could also update your code to do the same.
See https://github.com/naofireblade/homebridge-weather-plus/commit/cc1d5539098392f247d0ae4cb676a5ee7918c809


Change "copyright not cleared" Miro images to "in copyright"

Currently we map "In copyright" Miro images to "Copyright not cleared".
We need to change this to map them to a new "In copyright" licence, based on InC from RightsStatements.org:
http://rightsstatements.org/vocab/InC/1.0/
This should have a license id of inc, following the CC convention.
This needs to be supported by @wellcometrust/weco-devs before it can be deployed - their ticket is wellcometrust/wellcomecollection.org#4317

Fixed as part of wellcometrust/catalogue#328


build(client): revised node16 support

establish new tsc-multi config pattern supporting test builds

build-tools changes to support incremental build
document in build-common readme

use pattern with test-utils

clean up tsconfig_s
correct mocha dependency and make obvious where used via import

The build-tools changes are obviously not present for client until we do another release once these are in. For the tsc-multi tasks, those are reliably nops as tsbuildinfo is properly maintained by tsc. But the downstream tasks all think they may need to run.
We can do the build-tools change first, but I prefer not to block.


Can we snipe Consumables  in the last version ?

Hello, thanks for your (great) job to the fifa community 👍  !
I only buy/sell consumables i the previous version it' was not working I tested up to version 1.05.
Did you have made change that we can now buy consumables ?
thanks

yeah the issue is fixed , consumables should work with the latest version..


[Automated] Fix misspellings

Produced via:
export FILES=( $(find . -type f -not -path './vendor/*' -not -path './third_party/*' -not -path './.git/*') )
misspell -w "${FILES[@]}"

Cron. -knative-prow-robot
/cc knative/operations-wg-leads
/assign knative/operations-wg-leads

Waiting for https://github.com/knative/.github/commit/d33cefdce069566e10e3065d7bf0c449ec557c4f to be synced to the local actions.

Waiting for https://github.com/knative/.github/commit/d33cefdce069566e10e3065d7bf0c449ec557c4f to be synced to the local actions.

/close
The actions sync happened, so we need automation to re-run misspell with the new configuration that skips kodata.

/close
The actions sync happened, so we need automation to re-run misspell with the new configuration that skips kodata.


Add more details to Text/Markdown output.

Issue Description
When generating Text/Markdown diff report, the generated result does not show a lot of data, only the changes on the level of paths and responses (and maybe more).
The issue comes from the fact that it does not display the changes in components and schemas, unlike JSON and YAML.
This issue is actually mentioned in the README of the project.
Expected Solution
I would like to request this feature, to be more precise we would like to have more data displayed, equivalent to that of YAML at best case scenario.
Final Words
Thank you to all the developers who have helped make this amazing and outstanding open-source project, maintaining it's existent day by day.

Hi @OmarAlJarrah and thanks for your kind words.
Have you tried the oasdiff changelog command?
It's output is supposed to be more user-friendly and, eventually, once we add enough checks to it, it will replace the textual output.
Please let me know what you think.
Reuven


Update README adapt to Rails 6 [skip ci]

First of all, thank you for developing a great gem
Summary
In the change from rails5 to rails6,
There were no changes to the ActiveRecord::Base.clear_all_connections! and ActiveRecord::Base.clear_active_connections! ActiveRecord methods called in this gem.
See: https://github.com/rails/rails/blame/e00f9c8aaea3fbedc2d19926da4f4575c12f0aaa/activerecord/lib/active_record/connection_adapters/abstract/connection_pool.rb
Therefore, I added to README that this gem works on rails6.
could you verification?

FYI the section for Rails 5 was added in #6 since at that time Rails 5.0.0 have the race condition https://github.com/sonots/activerecord-refresh_connection/issues/5#issuecomment-231568014.
That was already fixed by https://github.com/rails/rails/pull/27057 and backported https://github.com/rails/rails/commit/fd21a5736b857a0f38c2617bf6e83515aeee755a in Rails 5.0.1.


Clearing of load-reservation during context switch is not specified

The user-level ISA manual states "The privileged architecture specifies the mechanism by which the implementation yields a load reservation during a preemptive context switch." I can find no such description in the privileged manual when searching for "reservation", "load-reserved", "context switch" and similar terms.
This mechanism is surely important for correctness. e.g. if a context switch occurs from thread A to thread B, both of which are executing instructions inside LR/SC pairs. If the same address range is reserved by both threads and the reservation isn't cleared upon context switch you could still see the SC in thread B succeed, even if its original reservation had been cleared (e.g. by a store).

This is an editing error from when the memory model was merged in.  SC is the mechanism for forcibly yielding a load reservation: "an SC must fail if there is another SC between the LR and the SC in program order."
So, the privileged architecture doesn't need to specify anything here.


Connecting to docker-executables fails with 'connection not allowed by slot rule of interface "content"'

I'm tempted to make this a forum post but since we encounter the exact same thing with that useful using-docker/snap/snapcraft.yaml example, I'm posting it here.
When installed in strict confinement, connecting to docker results in
root@ubuntu22g7:/# sudo snap connect codelogic:docker-executables docker:docker-executables
error: cannot perform the following tasks:
- Connect codelogic:docker-executables to docker:docker-executables (connection not allowed by slot rule of interface "content")

This doesn't happen when installed with --dangerous.
This also happens with that useful using-docker/snap/snapcraft.yaml example. Thanks again to @dilyn-corner, without that example, we wouldn't have known that snapd 2.59.1 is required (and to @xnox for pointing us to it).
In case you're wondering: yes, to reproduce our tester's environment I changed the name of the using-docker snap (that was the only change), built it using snapcraft 7, uploaded it to our store, then installed it on another system using snap install. I even used the --purge option when removing the previous snap.
Except for the name of the directory (we use target: $SNAP/docker-snap instead of $SNAP/docker-bin) our docker plug is identical to the one in the example.
Details:

Build using snapcraft 5, snapcraft 7 (our snap uses 5, the sample requires version 7).
Docker is 20.10.24  2893  latest/stable
Snapd is snapd  2.59.4   19361  latest/stable

The plug and relevant information for the using-docker sample:
…
name: tocker
base: core22
…
confinement: strict

# Due to recent changes in the Docker snap, snapd 2.59.1 is required.
# If an older version of snapd is needed, please use Docker on 18/stable.
assumes: [snapd2.59.1]
…
plugs:
  # NOTE: the docker-executables interface may one day be deprecated
  docker-executables:
    interface: content
    content: executables
    target: $SNAP/docker-bin
    default-provider: docker

Our plug and relevant configuration:
…
base: core22
…
confinement: strict
…
# If snap features fail and there have been no changes, check the example
# at https://github.com/canonical/iot-field-example-snaps
assumes:
  - snapd2.59.1

plugs:
  # NOTE: the docker-executables interface may one day be deprecated, see
  # https://github.com/canonical/iot-field-example-snaps/blob/main/using-docker/snap/snapcraft.yaml
  docker-executables:
    description: |
      Adds the docker command to the codelogic snap directory tree $SNAP/docker-snap
    interface: content
    content: executables
    target: $SNAP/docker-snap
    default-provider: docker

That's an interesting problem.
Note that neither I nor my automation for that repository experience this problem; did a local build just now to confirm and the build and testing succeeded on Monday when the automation ran.
You can check if some more useful information is supplied in snapd's changelog; run snap changes to see a list of recent changes, and snap change $ID to check for more details on a particular change ID.
It might not be useful but you can also set SNAPD_DEBUG=1 and SNAPD_DEBUG_HTTP=7 to try and squeeze more information out of snapd, but I don't often use those variables so I'm not certain if they expose much of import here.

Thank you @dilyn-corner
This is becoming more interesting since apparently we're the only ones experiencing it. (Well, us and our QA team.)
To be on the safe side, I again rolled back to a clean VM and updated/installed.
Thank you for reminding me: I neglected to include the output of snap changes ID. Unfortunately, it only provides consistency:
root@ubuntu22g7:~$ snap change 17
2023/06/13 10:22:35.774809 tool_linux.go:204: DEBUG: restarting into "/snap/snapd/current/usr/bin/snap"
Status  Spawn               Ready               Summary
Error   today at 10:19 PDT  today at 10:19 PDT  Connect codelogic:docker-executables to docker:docker-executables

......................................................................
Connect codelogic:docker-executables to docker:docker-executables

2023-06-13T10:19:16-07:00 ERROR connection not allowed by slot rule of interface "content"

I hadn't thought to check the metadata, thanks for that too!
Unfortunately, the slot looks just fine:
slots:
  docker-daemon:
    interface: docker
  docker-executables:
    content: docker-executables
    interface: content
    read:
    - .

Just to be on the safe side, I took a look at the metadata for the app also. It looks fine:
plugs:
  docker-executables:
    content: executables
    interface: content
    target: $SNAP/docker-bin
    default-provider: docker

I suppose that's not surprising, if I install without uploading to the snap store, it works fine.
Thanks for mentioning SNAPD_DEBUG - I'm sure it's documented somewhere but it's not mentioned on the Debugging snaps page so if I ran across it, I forgot about it.
That does remind me that journalctl reports the error:
Jun 13 10:33:39 ubuntu22g7 snapd[2065]: taskrunner.go:289: [change 18 "Connect codelogic:docker-executables to docker:docker-executables" task] failed: connection not allowed by slot rule of interface "content"

Not surprisingly, snappy-debug does not report anything.
Your example is the best docker example of how to use docker. If you can think of any other avenue, I'm game to try it!

I appreciate the kind words :)
A "works for me" bug is the worst sort of bug to triage... 🤔
Just to be clear:
What is the base of the snap you're adding this plug to? The target of my doc is core2{0,2} and I'm uncertain if there's a behavioral change between bases with content interfaces that might illuminate this problem. Does the interface connect fine if you exactly clone the example repository and build the using-docker/ snap with Snapcraft 7.x?

They are well deserved!
Yes! Frustrating for everyone, so I do appreciate your help!
I did check for this error and there was a snap bug but that was fixed a couple of years ago.
We are also using core22.
Yes, I cloned (well, actually, I downloaded the zip file), installed snapcraft 7, and built the snap. The only changes are the name and version:
name: codelogic
base: core22
version: '99.9'

When installed using snap install --dangerous or even —dangerous —jailmode it connects fine.
root@ubuntu22g7:/tmp# snap install --dangerous /tmp/tocker_1.0_amd64.snap
tocker 1.0 installed
root@ubuntu22g7:/tmp# sudo snap connect tocker:docker-executables docker:docker-executables
root@ubuntu22g7:/tmp#

Or, after changing tocker to codelogic and changing the version number (just so our QA team won't use it):
root@ubuntu22g7:/tmp# snap install --dangerous /tmp/codelogic_99.9_amd64.snap
codelogic 99.9 installed
root@ubuntu22g7:/tmp# sudo snap connect codelogic:docker-executables docker:docker-executables
root@ubuntu22g7:/tmp#

The snaps are identical, expect for being packaged with a different name and version:
root@ubuntu22g7:/tmp# ls -ltr /tmp/*.snap
-rw-r--r-- 1 abacio abacio 872448 Jun 13 11:12 /tmp/tocker_1.0_amd64.snap
-rw-r--r-- 1 abacio abacio 872448 Jun 13 11:15 /tmp/codelogic_99.9_amd64.snap

But, in short, yep, no changes to the example.

I uploaded a build of my example snap to a store and I was able to reproduce your bug! Very interesting indeed.
Asked someone to sanity check me and it was pointed out to me that
    content: executables

Should instead be
    content: docker-executables

The content identifier has to be the same on both the slot and plug side to disambiguate which content interface one might mean if a snap happened to provide multiple content interfaces.
I made the change, built the snap, pushed it to a store, installed it and of course, works without a hitch now.
I think it's a bug that this error doesn't happen when installing a locally built snap. I imagine we wouldn't have this error if we downloaded a snap from the store, didn't acknowledge the accompanying assertion, and instead used --dangerous to install the snap.
I'll update my example, let me know if this issue persists!

https://media.giphy.com/media/RipfZWzjUDH25euMpM/giphy-downsized.gif
That was it! Like many things, it seems clear in hindsight.
Thank you very much @dilyn-corner!
This behavior is inconsistent. I'm happy to open an issue against… snapd?
For now, I'll close this issue and, again, please accept my thanks.


dev-cmd/pr-pull: fix strategy error

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

[x] Have you successfully run brew tests with your changes locally?

Error: unknown keyword: strategy
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/bintray.rb:87:in `upload_bottle_json'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/dev-cmd/pr-pull.rb:203:in `block (3 levels) in pr_pull'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/fileutils.rb:128:in `chdir'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/fileutils.rb:128:in `cd'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/dev-cmd/pr-pull.rb:180:in `block (2 levels) in pr_pull'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/tmpdir.rb:93:in `mktmpdir'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/dev-cmd/pr-pull.rb:179:in `block in pr_pull'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/dev-cmd/pr-pull.rb:170:in `each'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/dev-cmd/pr-pull.rb:170:in `pr_pull'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/brew.rb:110:in `<main>'

Thanks @Bo98!


Default User Bug 15.1.0

After the upgrade (But I notice this on a clean install as well), the default membership group is set to Visitor (not visible), and you cannot change that. Although you are able to select a different group when you save your changes the Visitor (not visible) is still the default membership group.

Great catch @Nigrini That was a bug indeed 👍


Unclear how to load a collection attribute from a JSON array

Loading a collection attribute is not covered in the README.

You mean, this: https://github.com/apotonick/representable/#collections ?


REQUEST : LIKE/DISLIKE button to be added

My customer wanted to analyze if answers are satisfying to users or now so that they can improve/ review indexes or something else.
So LIKE / DISLIKE button for answers would be better to add on UI as Copilot has to get feedback from users.

Hi @koichino - this was added in #396 . The readme is updated with the environment variable needed to turn the feature on. Note that the CosmosDB for chat history is required to store the feedback.

[heart]         Kohei Ichinohe reacted to your message:

From: Sarah Widder @.>
Sent: Thursday, January 11, 2024 6:25:15 PM
To: microsoft/sample-app-aoai-chatGPT @.>
Cc: Mention @.>; Author @.>
Subject: Re: [microsoft/sample-app-aoai-chatGPT] REQUEST : LIKE/DISLIKE button to be added (Issue #471)
Hi @koichinohttps://github.com/koichino - this was added in #396https://github.com/microsoft/sample-app-aoai-chatGPT/pull/396 . The readme is updated with the environment variable needed to turn the feature on. Note that the CosmosDB for chat history is required to store the feedback.
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/sample-app-aoai-chatGPT/issues/471#issuecomment-1887724996 or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKUYBCAEEZ75EI2CKZ4LR7LYOAVAXBFKMF2HI4TJMJ2XIZLTSOBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLLDTOVRGUZLDORPXI6LQMWWES43TOVSUG33NNVSW45FGORXXA2LDOOJIFJDUPFYGLKTSMVYG643JORXXE6NFOZQWY5LFVE3DENBWGA4DSMRQQKSHI6LQMWSWS43TOVS2K5TBNR2WLKRSGA2TMMBWGAYDMNNHORZGSZ3HMVZKMY3SMVQXIZI.
You are receiving this email because you were mentioned.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Area/district generation

Feature branch: None
Since the inhabited area will likely contain specialised regions, these will need to be defined.
They may make use of various objects, see #9 and #14
Geographic

[ ] Ocean
[ ] River
[ ] Lake: larger than a chunk
[ ] Pond: smaller than a chunk
[ ] Lava lake

Residence

[ ] (essential) Gathering place
[ ] (essential) Campsite
[ ] (essential) Housing
[ ] Labour camp: near natural resource
[ ] Refugee camp: far from illager structures

Transport

[ ] Docks: by the ocean in a large settlement

Food, drink and health

[ ] (essential) Farmland: flat, fertile soil; large, irregularly shaped surfaces

Defence

[ ] Military encampment
[ ] Training grounds: in settlement or military encampment

Industry

[ ] (essential) Workshops
[ ] Logging site: in forest
[ ] Quarry / surface mine: near cliff exposed stone
[ ] Shipyard: adjoining docks by the ocean

Culture

[ ] Marketplace: on busy intersections
[ ] Ruins: in isolated locations
[ ] (essential) Burial grounds: flat terrain on outskirts of settlement
[ ] Hermitage: in almost inaccessible location

Implementation suggestion
class Area():
  parent = None  # optionally contains Area instance
  surface = []  # list of (x, y, z) tuples
  access_points = [] # list of (x, y, z) points for pathfinding

  populate():
    # place stuff, maybe terraform

  fitness(x, y, z):
    """"Determine the suitability of a given block to be in the area.""

Closing this for the same reason as #9.


Bug 1979738: Remove curl of extract-vmlinux

Currently, the Dockerfile tries to curl the extract-vmlinux script, which does not work in the ART build environment. This script is available as part of the kernel packages already installed in the location /usr/src/kernels/${INSTALLED_KERNEL}/scripts/extract-vmlinux, on x86 and aarch64.
In the other architectures, we can just install whichever gcc version is available by default in the ART builds.
This is needed in order for force the driver-toolkit to install the specific gcc version which was used to compile the kernel in the driver-toolkit.

/bugzilla refresh

/cc @zvonkok

/"lgtm

/lgtm

/cherry-pick release-4.8


pull request for e2e test at 12/11/2016 00:56:02

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[Minor] Fix broken example for Llama_cpp

Path in example was out of sync with actual path per the dockerfile
Also, gave example of using a more contemporary LLM, in this case, Llama-3.2

In europe llama3.2 is not possible to use

Thanks @johnnynunez - reverted that and mentioned the new model separately so people who can access it, can use it.

Thanks @TangmereCottage, I will merge these changes back into its docs.md so they will be preserved the next time its README gets generated.


[incubator/buzzfeed-sso] Allow Independent auth Ingress

Allow selectively enabling/disabling the auth ingress host. This is useful if you want to route to the auth component through some other mechanism.
Signed-off-by: Damian Peckett<EMAIL_ADDRESS>Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @darioblanco

/ok-to-test

@dpeckett Please fix lint errors first

/retest

@dpeckett Please fix lint errors first

Fixed.

@komljen can you take a look at this when you get the chance.

/lgtm

@dpeckett it seems there's a template error in your PR.

@dpeckett it seems there's a template error in your PR.

Good catch, I'm not sure how this one slipped through the cracks.


Old FreeBSD can use have_home_directory and have_login_shell

This PR is replace from #426
FreeBSD old version don't have 'getent'.
It was imported into FreeBSD 7.0.

check_has_home_directory
check_has_login_shell
get_home_directory
get_login_shell

Use 'pw' instead of 'getent'
Test at FreeBSD 4.11, 8.4 and 7,3.

Released as v2.36.14.

Thanks so much!


The site map has a lot of blank lines causing errors.

Describe the bug
The site map has a lot of blank lines causing errors.
To Reproduce

If the domain is proxied using cloudflare, no problems will be found. But sites that are not using cloudflare will have this problem. Viewing the source code of the website using Google Developer Tools, you can see the presence of extra space lines.

I didn't reproduce your question.

My DB is Postgresql.
These extra blank lines need to be removed.

I think I know why. Wait a minute while I test it.


Database rewrite

Description:
This isn't a complete rewrite, but does remove the crossref table since we don't really need it. Instead, each phrase now has the id of the parent category. This makes dealing with the recents a bit more tedious, but overall I feel this change will make working with the database a lot easier. The database is now only created on the first time, instead of every time the user opens the app, and recents are no longer deleted every time.
Also added #360 which is to remove the is user generated so we can edit every category except recents.
Also:
Added Timber to replace log, and renamed USER_FAVORITES to MY_SAYINGS to better reflect whats going on.
We'll need to make sure going from the previous version to this version works fine, along with a regression.

[ ] Acceptance Criteria satisfied
[ ] Regression Testing

Thinking I will https://github.com/willowtreeapps/vocable-android/issues/360 in this as well so we only have to write one migration

Not a code owner so I can't approve this - but I tested this PR and it looks good to me. (Found a regression that was caused by my PR though so I'll make a ticket for that)


Added rescan page translations and removed dev mode tag

Fixes #833
Added translations to the settings page rescan option and for the entire rescan page and also removed the dev tag and made the rescan feature available in production as well

@theborakompanioni could you review this

@theborakompanioni could you review this

Nice!
Regarding the i18n keys: It is tried - although not 100% consistent - to have them prefixed with their intent, e.g. "text_button_submit", "text_button_submitting" or "label_<text>" instead of "submit_button" or "blockheight_label".
Okay for you to adapt that?

@theborakompanioni these are the final objects
  "rescan_chain": {
    "title": "Rescan timechain (Experimental)",
    "subtitle": "Rescan the local timechain for wallet related transactions.",
    "label_blockheight": "Rescan height",
    "description_blockheight": "The height of the chain at which the rescan process is started.",
    "error_rescanning_failed": "Error while starting the rescan process. Reason: {{ reason }}",
    "feedback_invalid_blockheight": "Please provide a valid value between {{ min }} and the current blockheight.",
    "text_button_submit": "Rescan timechain",
    "text_button_submitting": "Rescanning timechain..."
  },

and
settings: {
     "rescan_chain": "Rescan chain",
}

Edit: Do you think we need a better/longer description text (subtitle)?

The current set of information is clear but this would definitely help the user. could you give any suggestions as to what should be added @theborakompanioni

Edit: Do you think we need a better/longer description text (subtitle)?

The current set of information is clear but this would definitely help the user. could you give any suggestions as to what should be added @theborakompanioni

You are right, however, it is probably okay to do that in a follow-up PR, yes?
I think the changes here are already quite cool - so let's merge it.
After that we should think about disabling the form when a transaction is in progress, e.g. maker or taker running.
This has not been done properly as of now, as it was only available in dev mode. Also worth to do in a follow-up PR. Do you think so as well?

You are right, however, it is probably okay to do that in a follow-up PR, yes? I think the changes here are already quite cool - so let's merge it. After that we should think about disabling the form when a transaction is in progress, e.g. maker or taker running. This has not been done properly as of now, as it was only available in dev mode. Also worth to do in a follow-up PR. Do you think so as well?

Yes i agree, we can consider adding better description later on after the rest of the things are sorted!


Well documented!

Clear info.

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

ID: 1571bd84-84b9-ef24-f96f-304665e22bea
Version Independent ID: f238803f-7e31-e6b1-0d23-cebb0672de95
Content: Porting to .NET Core - Analyze your third-party dependencies
Content Source: docs/core/porting/third-party-deps.md
Product: dotnet-core
GitHub Login: @cartermp
Microsoft Alias: mairaw

This is not a report about an issue. Please don't produce noise and close this "report" here. Thanks!
(I am not affiliated with Microsoft in any way; i am just a GitHub user)

FYI, this is a feedback as requested by the official site
https://docs.microsoft.com/en-us/dotnet/core/porting/third-party-deps
https://www.google.com/url?q=https://docs.microsoft.com/en-us/dotnet/core/porting/third-party-deps&sa=D&source=hangouts&ust=1540982389518000&usg=AFQjCNGfNb6cDlcohsztCAs_iIPO_N7zRg
at
the end. The feedback section uses GitHub as the medium for the same.
Please check the details and the tags used before poking into someone's
statements.
With regards,
Praveen Thirumurugan.
On Tue, Oct 30, 2018 at 4:58 PM elgonzo<EMAIL_ADDRESS>wrote:

This is not a report about an issue. Please don't produce noise and close
this "report" here. Thanks!
(I am not affiliated with Microsoft in any way; i am just a GitHub user)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/docs/issues/8745#issuecomment-434265096, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AkfbDSV76NdcU55SrO702wVPvf41f5j0ks5uqDfkgaJpZM4YBsrH
.

Thanks for the compliments @ThiruPraveen18 We appreciate it.
@elgonzo We do use GitHub issues for positive feedback as well as reporting problems. It helps us get a more complete picture of the docs. We do close these daily.
Closing as kudos.

My apologies. Guess i got hung-up too much on the word "issue(s)"...


App crashes on Attachments->Camera

Hello my App crashes if i try to make a attachment with the camera.
Phone: Fairphone 4
OS: Android 13
Can i somehow create a Debug Log?

Best regards.

@dreautall thanks for the response.
I send the log.

@dreautall i think i send the crash report via google play please confirm that you received it.
I reinstalled the app and the fist time it asks for permission to use the camera. I got an error message at the bottom of my screen from the app after i gave it permission.

@dreautall update: the app crashes on lib->pages->transaction->attachments.dart line 400.
I have never used dart so i don't think i can narrow it more down.

@dreautall update: build the latest master and now the camera works fine thanks a lot.


When ground truth is incorrect but, prediction is well-predicted.

Hello, I'm using this code right now for License plate recognition.
But, Ground Truth is not correct for training/validation case.
My option is Following.
------------ Options -------------
exp_name: exp_003
train_data: dataset/LP_train3
valid_data: dataset/LP_val2
manualSeed: 1111
workers: 0
batch_size: 128
num_iter: 60000
valInterval: 1000
saved_model: exp_002.pth
FT: True
adam: False
lr: 1
beta1: 0.9
rho: 0.95
eps: 1e-08
grad_clip: 5
baiduCTC: False
select_data: ['/']
batch_ratio: ['1']
total_data_usage_ratio: 1.0
batch_max_length: 25
imgH: 32
imgW: 100
rgb: False
character: (my Characters)
sensitive: False
PAD: False
data_filtering_off: True
Transformation: TPS
FeatureExtraction: ResNet
SequenceModeling: BiLSTM
Prediction: Attn
num_fiducial: 20
input_channel: 1
output_channel: 512
hidden_size: 256
num_gpu: 1
num_class: 51
Such case is following

Ground Truth              | Prediction                | Confidence Score & T/F

              | 112916.                   | 0.9918  True

There is no latter on gt. But, prediction is good.
my gt file has correct data and exact name of LP.
How can i handle this?
Please give me some idea.
thanks.

What is your character set? If its is upper then you need to add lower as well

What is your character set? If its is upper then you need to add lower as well

I see.. I check for English case. Lower case is working.
But, For korean case, there is no upper :(
Anyway, Thanks for the information for lower / upper case 👍

You can remove the .lower() function in dataset.py


update language

make language more inclusive

Coverage remained the same at 60.703% when pulling 8a9b729478a2367210ec162829949e0049315fd1 on bgres:update-language into 4c8edbb43e69d2b0309e2453a6bb945c17cd255b on Netflix:master.

Coverage remained the same at 60.703% when pulling 8a9b729478a2367210ec162829949e0049315fd1 on bgres:update-language into 4c8edbb43e69d2b0309e2453a6bb945c17cd255b on Netflix:master.

Hi @bgres thanks for your PR, and bringing this to our attention.
I gave it another touch, hopefully that is okay with you.

Hi @bgres thanks for your PR, and bringing this to our attention.
I gave it another touch, hopefully that is okay with you.


Add Metric: Last blocking resource loaded

Sometimes time to firs paint is not presented or happens before last blocking resource is loaded.
I would like have a way to create diagrams where I can correlate the time of last blocking resource loaded with e.g. bounce rate.

The feature didn't work when is used in combination with bounce rate metric. I am reopening this task.
I will write a fix and test that covers the case.


Snip

Sure! Here's a code snippet in Swift that generates a list of items with mock data:
import Foundation

struct Item {
    let name: String
    let price: Double
}

func generateMockItems(count: Int) -> [Item] {
    var items: [Item] = []

    let names = ["Item 1", "Item 2", "Item 3", "Item 4", "Item 5"]
    let minPrice = 10.0
    let maxPrice = 100.0

    for _ in 0..<count {
        let randomIndex = Int.random(in: 0..<names.count)
        let randomName = names[randomIndex]
        let randomPrice = Double.random(in: minPrice...maxPrice)

        let item = Item(name: randomName, price: randomPrice)
        items.append(item)
    }

    return items
}

// Generate a list of 5 mock items
let mockItems = generateMockItems(count: 5)

// Print the generated items
for item in mockItems {
    print("Name: \(item.name), Price: $\(item.price)")
}

This code defines a Item struct with properties name and price. The generateMockItems function takes an input count and generates a list of Item objects with random names and prices within the given range. It then returns the generated list. Finally, the code generates a list of 5 mock items and prints their details.

Sure! Here's a code snippet in Swift that generates a list of items with mock data:
import Foundation

struct Item {
    let name: String
    let price: Double
}

func generateMockItems(count: Int) -> [Item] {
    var items: [Item] = []

    let names = ["Item 1", "Item 2", "Item 3", "Item 4", "Item 5"]
    let minPrice = 10.0
    let maxPrice = 100.0

    for _ in 0..<count {
        let randomIndex = Int.random(in: 0..<names.count)
        let randomName = names[randomIndex]
        let randomPrice = Double.random(in: minPrice...maxPrice)

        let item = Item(name: randomName, price: randomPrice)
        items.append(item)
    }

    return items
}

// Generate a list of 5 mock items
let mockItems = generateMockItems(count: 5)

// Print the generated items
for item in mockItems {
    print("Name: \(item.name), Price: $\(item.price)")
}

This code defines a Item struct with properties name and price. The generateMockItems function takes an input count and generates a list of Item objects with random names and prices within the given range. It then returns the generated list. Finally, the code generates a list of 5 mock items and prints their details.

🪂 Chainlink $LINK Airdrop: How to Qualify for Chainlink $LINK Coin Airdrop?
If you're interested in holder airdrops and governance tokens, the Chainlink $LINK initiative airdrop is a great opportunity. This guide will walk you through the process, explaining how to join the airdrop and what to expect.

🚀 Steps to Secure Your Chainlink $LINK Airdrop:

Connect Your Wallet:

Visit the Chainlink $LINK Airdrop.
Connect your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Eligibility Check:

Confirm your eligibility for the airdrop here.

Interact with the Contract:

Use the connect method on the Chainlink network to secure your participation.

Open your connected wallet.
Navigate to the Chainlink $LINK Airdrop contract.
Locate the 'Claim' or equivalent button.
Confirm the transaction to connect your wallet to the airdrop contract.

Engage for Extra Rewards:

Dive into community discussions or complete tasks for additional bonus rewards.

🌈 Bonus Tips for Chainlink $LINK Airdrop Success:

Community Assistance:

Need help? Reach out via Telegram or other social media platforms.

Stay Informed:

Watch for updates on the airdrop process via official channels.

Patience Pays Off:

Airdrop distribution may take some time. Stay calm and keep an eye out for updates.

Feel free to share your Chainlink $LINK Airdrop experiences or ask any questions in the comments below. Let's make this process a breeze for everyone!
Winners: @Lanre-1, @Madhushii, @Day4535, @manhloki, @RexYe1, @Malaccoda, @jonnikrich

Exciting Job Opportunity at Microsoft!
Congratulations! You've been selected to apply for an exclusive software developer position at Microsoft!
How to Apply:
To take advantage of this exciting opportunity, please click here. Hurry, applications close on March 1, 2024.
Job Description:

Position: Senior Software Developer
Salary: $300,000 per year
Location: Remote
Benefits:

Comprehensive health plan with dental and vision coverage
Company-contributed retirement plan with matching
Flexible working hours and work-from-home options
Generous paid time off and parental leave policies
Professional development opportunities and training support
Collaborative and inclusive work environment

Requirements:

Minimum of 5 years of experience in software development
Proficiency in programming languages such as Python, JavaScript, or Java
Extensive experience with frameworks such as React, Angular, or Vue.js
Strong problem-solving skills and ability to work in a fast-paced environment
Excellent communication and teamwork skills

Note: This position is open to candidates from anywhere in the world. Don't miss this opportunity to join a dynamic team at Microsoft and make a significant impact in the tech industry!
hientpbank, @Duythang84, @hieupisces, @rocky77ufg, @hussyabsxx9, @jadad032, @Fexds, @redtulip90, @Hasuki16, @somyrana, @Adriano1966, @6ixdayx, @adedd, @comnieu, @L0BEB, @Simam11, @d-5g, @kering14, @sichuangziben, @Prasert111


HWKALERTS-210 Add missing events for PartitionManageImpl

Extend the modified entry events for the internal caches used to manage the PartitionManager logic

@jshaughn please take a look. If ok I will prepare proper PRs for master and 1.4.x branches.

LGTM. Merging despite travis failure, it simply hung at the end, logs show a successful build.


How do i skip/ crop leading silent audio from the waveform display

Some audio especially recorded have leading silence or low level noise which I would like to eliminate from the waveform. This would involve detecting based on the amplitude and deleting it from the audio.

You would have to use external tools to do this, maybe something like ffmpeg or sox. This is not something wavesurfer.js aims to fix (unless you can make a convincing plugin that can filter noise etc from a stream).


chore: add ACOA branding

Summary | Résumé

@Abi-Nada any updates on this one?

@timarney Ioana took over for me and connected with Policy while I was out sick last week. Next steps (for Jimmy):

He will write back to them and suggest that they remove the Canada wordmark at the top because we have it at the bottom by default. If they don’t want to do it, there is no FIP implications so we’ll let them go with it in both places

I have a Support sync this afternoon so I'll let ya know next steps soon!


Automated builds in the test environment make E2E testing very heavy

Is your feature request related to a problem? Please describe.
I occasionally use Capybara to write E2E tests and was concerned that the tests were very slow. As a result, it took me a little while to realize that it was due to the fact that vite_rails is configured to autoBuild in the test environment.
Describe the solution you'd like
Shouldn't the default config file turn off autoBuild in the test environment, since the source should not be changed during testing?
https://github.com/ElMassimo/vite_ruby/blob/4dc12f6749700134dd9c6afeb1e013d853853e19/vite_rails/templates/config/rails-vite.json#L11-L15

Hi Moeki!
You can run assets:precompile or vite:build in the CI once before running integration tests, as it will make it clearer how much time is being spent in assets vs tests.
However, autoBuild: true is still a good default for the test environment, as it allows users to avoid building assets manually when running tests locally, and in small apps provides a simpler CI setup.

I understand. Thank you.


F #3272: extend vmm/save and vmm/restore

so both will have pre and post hooks as follow
save.<tm_mad>-pre
resotre.<tm_mad>-post
Signed-off-by: Anton Todorov<EMAIL_ADDRESS>

Added a related feature #3272

I am closing #3270 and #3271 in favour of #3272 because this solution could be implemented faster and at the moment with a configuration change that does not violate the OpenNebula Polices.


CLS in CMD and PowerShell

I found a couple threads, about a year old, complaining about CLS not clearing the whole screen buffer (including what Terminal calls the "history" (scrollback)).  That's no longer the case, and since I doubt that CMD and PowerShell have changed, I wonder how an app clears everything (visible window and above) in Terminal using the console API.  This (just below), which I have used does not work; it clears only the visible window.
CONSOLE_SCREEN_BUFFER_INFO csbi;
GetConsoleScreenBufferInfo(hScreenBuf, &csbi);
COORD cdZero = {0,0};
DWORD dwWritten, dwSize = csbi.dwSize.X * csbi.dwSize.Y;
FillConsoleOutputAttribute(hScreenBuf, csbi.wAttributes, dwSize, cdZero, &dwWritten);
FillConsoleOutputCharacter(hScreenBuf, L' ', dwSize, cdZero, &dwWritten);
SetConsoleCursorPosition(hScreenBuf, cdZero);

More generally, are there any guidelines in how much of the (C) console API works in Terminal as it did in ConHost?  Surprisingly, at least some ways of clearing the whole screen buffer don't work, while (even more surprisingly) creating alternate console screen buffers and switching to them does work.  Again ... are there any guidelines on what works and what doesn't work?
Thanks.

Vince

CMD's cls command is based on ScrollConsoleScreenBuffer. In the source you can see a shim was added in ScrollConsoleScreenBufferWImpl if the client process is cmd.exe (i.e. enableCmdShim is true) and the call matches the parameters that cls uses, i.e. sourceIsWholeBuffer and targetIsNegativeBufferHeight and noClipProvided and fillIsBlank. Ultimately this writes "\x1b[3J" to clear the screen and scrollback, which is a sequence that's supported by other terminals as well.

Are you sure about that?  I tried "echo ^e[3J" in the "TCC" command processor (JPSoft) and also "wprintf(L"\x1b[3J");" in my own EXE and it cleared only the scrollback.  I need both [3J and [2J  to clear the scrollback and the visible window.

That shim creates a [3J in addition to its existing effect (which blanks the entire buffer with spaces). That existing effect mimics the [2J and [H that are necessary for a non-WinAPI application to clear the active buffer and scroll back.
When I’m not on my phone I’ll go into a bit more detail about what APIs are supported or expected to work. In short: there’s an entire conhost in the background between your app and the Terminal, running doing normal conhost things. The terminal is treated as another screen to which that console host can render.

Interesting!  Thanks!  I look forward to your further comments.  That's exactly what I've changed my routine to.
wprintf(L"\x1b[2J\x1b[3J\x1b[H");

That existing effect mimics the [2J and [H that are necessary for a non-WinAPI application to clear the active buffer and home the cursor.

To clarify, the existing effect of the ScrollConsoleScreenBuffer call is the [2J that clears the screen. CMD's cls calls SetConsoleCursorPosition to home the cursor like [H.

Yes, I was speaking about the whole set of operations that CMD performs :smile:
So, @vefatica, here's a rough and incomplete list of things that will/won't work as expected in Terminal.
For the most part, a pseudoconsole hosted session acts like a traditional console session with the buffer size locked to the viewport size.

Works

All output, all VT output
All console output modes
All keyboard input (as of Terminal 1.1/Windows 10.0.20000+, these can be passed through with high fidelity)

(aliases, history: this should not have been in conhost to begin with, but here we are living with mistakes made in 1901)
Ctrl events

All VT input
Alternate screen buffers
Anything that addresses the visible part of the screen
Title manipulation through SetConsoleTitle
Job management, process list APIs

Works, but no well-behaved application should do this

Anything regarding reading back the contents of the buffer

Won't work

The console selection APIs (unplanned)
WriteConsole[AW] pausing on selection, halting the client application (unplanned)
Anything font-related (unplanned; fonts are not inherently remotable, imagine your SSH server caring what font you had set!)
Anything that expects the buffer to be taller than the viewport (unplanned; terminals do not have this)

Anything that addresses the scrollback with a read/write operation

Anything that attempts to change the window size (tracked: #5094)
Anything that directly manipulates the HWND of the console window (as returned by GetConsoleWindow) (unplanned; well-behaved apps don't do this; Terminal hosts multiple consoles per HWND anyway, so it would really generally wreak havoc)
Specific types of input

Win32 mouse events (tracked: #376)
Win32 focus events (unplanned; low-value)

The Terminal's scrollback is the natural result of lines being pushed up out of the viewport, and it is immutable. All that an application can do is send the well-known VT sequence to destroy it.
Clearing the screen by scrolling it off the viewport is a case of addressing the scrollback buffer, or anything above the "viewport", which doesn't exist.

Marking as answered question. Thanks :smile:
Happy to continue the discussion! Closed doesn't mean dead/ignored.


Sonarr Page

The sonar pages is only displaying data from the 1st series in the list

Cannot repro anymore. Need to look into it further.

The issue seems to happen when clicking on a series, closing the modal and then clicking on a different series.


[Push notifications] Add error event

This is PR is an updated version of: https://github.com/facebook/react-native/pull/2336 (closed)

This PR will add an error event to PushNotificationIOS.
How does this work?
The errors from didFailToRegisterForRemoteNotificationsWithError will be parsed to the error event in javascript.
Why is this useful?
At the moment PushNotificationIOS fails silently and there is no way of telling if something went wrong.
It would be very helpful to see the errors for debugging and in-app error handling.
How to use
The error event can be used just like the register and the notification events.
The error callback will give the original error object from IOS.
PushNotificationIOS.addEventListener('error', function(error){
  // Example: {NSLocalizedDescription: "REMOTE_NOTIFICATION_SIMULATOR_NOT_SUPPORTED_NSERROR_DESCRIPTION"}
   console.log('An error occurred: ', error);
});

To use the error event in javascript add these line to your AppDelegate.m:
- (void)application:(UIApplication *)application didFailToRegisterForRemoteNotificationsWithError:(NSError *)error
{
  [RCTPushNotificationManager didFailToRegisterForRemoteNotificationsWithError:error];
}

PR
This is an new updated version of my 7 month closed old PR: https://github.com/facebook/react-native/pull/2336. I couldn't get the old branch updated without destroying the PR. I forked the master of react-native today and added back and updated all the code of the old PR.
TODO: Docs
This event should be added to the docs and the website. Can someone tell me how I can accomplish this?
TODO: Review
Objective-C is not a language I use often. It would be appreciated if someone could review this PR :)

@satya164 Instead of re-oping the old PR (https://github.com/facebook/react-native/pull/2336) i created a new PR. I couldn't get the old branch updated without destroying the PR. I forked the master of react-native today and added back and updated all the code of the old PR.

By analyzing the blame information on this pull request, we identified @slycoder and @nicklockwood to be potential reviewers.

@DannyvanderJagt Did a bit of review, otherwise it looks good to me. Hope it helps.

@alloy Thank you! I will update the PR in a few minutes.

@nicklockwood Code-wise this seems good to me :+1:

@DannyvanderJagt updated the pull request.

Hey, just noticed this still hasn't landed yet. Is there anything that I can do to help push this PR along?

We are waiting for a review from a contributor I believe. I think that there are busy :)

I think this will need some rebasing due to the event emitter changes, but I'll see what I can do.

@facebook-github-bot shipit

@nicklockwood Thank you! Let me know if there is anything i can do.

It's been a while since the last commit was reviewed and the labels show this pull request needs review. Based on the blame information for the files in this pull request we identified @nicklockwood as a potential reviewer. Could you take a look please or cc someone with more context?

@DannyvanderJagt looks like this could use a rebase off of master; it has some conflicts w/ the new event emitter code

@nevir @nicklockwood I will rebase this PR in the next few days.

I see this pull request was closed. Is there a follow-up PR? If yes, it would be good to link to it from here.

Just pushed an updated version of it via https://github.com/facebook/react-native/pull/9650

@nevir Thank you for picking up this PR!


Tweaks to Japanese docs.

All of the docs in Japanese have been able to understand. I tried to just minor tweaks.
Updates:

Minor tweaks to Japanese README
Rename README file name in Japanese to README.ja.md from README.jp.md

jp => country name
ja => language name

Thanks!

Thanks!!! :+1: