[TextAnalytics] AnalyzeOperationConvenienceAsync failing in nightly runs

TextAnalytics runs are failing with:

Error message
Azure.RequestFailedException : Requests to the Get analysis status and results Operation under Text Analytics API (v3.2-preview.2) have exceeded rate limit of your current TextAnalytics S pricing tier. Please retry after 1 second. Please contact Azure support service if you would like to further increase the default rate limit.
Status: 429 (Too Many Requests)
ErrorCode: 429
Content:
{"error":{"code":"429","message": "Requests to the Get analysis status and results Operation under Text Analytics API (v3.2-preview.2) have exceeded rate limit of your current TextAnalytics S pricing tier. Please retry after 1 second. Please contact Azure support service if you would like to further increase the default rate limit."}}
Headers:
Retry-After: 1
apim-request-id: f30f8d12-f2a6-4b18-a1c5-ae1ae7a7796c
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
X-Content-Type-Options: nosniff
policy-id: REDACTED
Date: Thu, 20 Jan 2022 02:54:31 GMT
Content-Length: 336
Content-Type: application/json
Stack trace
at Azure.AI.TextAnalytics.TextAnalyticsRestClient.AnalyzeStatusAsync(String jobId, Nullable1 showStats, Nullable1 top, Nullable1 skip, CancellationToken cancellationToken) in D:\a\_work\1\s\sdk\textanalytics\Azure.AI.TextAnalytics\src\Generated\TextAnalyticsRestClient.cs:line 151    at Azure.AI.TextAnalytics.AnalyzeActionsOperation.Azure.Core.IOperation<Azure.AsyncPageable<Azure.AI.TextAnalytics.AnalyzeActionsResult>>.UpdateStateAsync(Boolean async, CancellationToken cancellationToken) in D:\a\_work\1\s\sdk\textanalytics\Azure.AI.TextAnalytics\src\AnalyzeActionsOperation.cs:line 313    at Azure.Core.OperationInternal1.UpdateStateAsync(Boolean async, CancellationToken cancellationToken) in D:\a_work\1\s\sdk\core\Azure.Core\src\Shared\OperationInternalOfT.cs:line 186
at Azure.Core.OperationInternalBase.UpdateStatusAsync(Boolean async, CancellationToken cancellationToken) in D:\a_work\1\s\sdk\core\Azure.Core\src\Shared\OperationInternalBase.cs:line 173
at Azure.Core.OperationInternalBase.UpdateStatusAsync(CancellationToken cancellationToken) in D:\a_work\1\s\sdk\core\Azure.Core\src\Shared\OperationInternalBase.cs:line 80
at Azure.Core.OperationInternalBase.WaitForCompletionResponseAsync(TimeSpan pollingInterval, CancellationToken cancellationToken) in D:\a_work\1\s\sdk\core\Azure.Core\src\Shared\OperationInternalBase.cs:line 142
at Azure.Core.OperationInternal1.WaitForCompletionAsync(TimeSpan pollingInterval, CancellationToken cancellationToken) in D:\a\_work\1\s\sdk\core\Azure.Core\src\Shared\OperationInternalOfT.cs:line 167    at Azure.Core.OperationInternal1.WaitForCompletionAsync(CancellationToken cancellationToken) in D:\a_work\1\s\sdk\core\Azure.Core\src\Shared\OperationInternalOfT.cs:line 145
at Azure.AI.TextAnalytics.AnalyzeActionsOperation.WaitForCompletionAsync(CancellationToken cancellationToken) in D:\a_work\1\s\sdk\textanalytics\Azure.AI.TextAnalytics\src\AnalyzeActionsOperation.cs:line 229
at Azure.AI.TextAnalytics.Samples.TextAnalyticsSamples.AnalyzeOperationConvenienceAsync() in D:\a_work\1\s\sdk\textanalytics\Azure.AI.TextAnalytics\tests\samples\Sample_AnalyzeOperationConvenienceAsync.cs:line 48
at NUnit.Framework.Internal.TaskAwaitAdapter.GenericAdapter1.BlockUntilCompleted()    at NUnit.Framework.Internal.MessagePumpStrategy.NoMessagePumpStrategy.WaitForCompletion(AwaitAdapter awaiter)    at NUnit.Framework.Internal.AsyncToSyncAdapter.Await(Func1 invoke)
at NUnit.Framework.Internal.Commands.TestMethodCommand.RunTestMethod(TestExecutionContext context)
at NUnit.Framework.Internal.Commands.TestMethodCommand.Execute(TestExecutionContext context)
at NUnit.Framework.Internal.Execution.SimpleWorkItem.<>c__DisplayClass4_0.b__0()
at NUnit.Framework.Internal.ContextUtils.<>c__DisplayClass1_01.<DoIsolated>b__0(Object _)    at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location where exception was thrown ---    at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)    at NUnit.Framework.Internal.ContextUtils.DoIsolated(ContextCallback callback, Object state)    at NUnit.Framework.Internal.ContextUtils.DoIsolated[T](Func1 func)
at NUnit.Framework.Internal.Execution.SimpleWorkItem.PerformWork()

For more details check here:

https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1314633&view=results

@jsquire for notification.

Fixed by https://github.com/Azure/azure-sdk-for-net/pull/26418.


XML module does not support HTML5

When parse HTML document with HTML5 tags this error occuried:
Test code:
 html5 = "Test"
 XML.parse_html(html5)

Error:
Tag nav invalid
       *Exception@Exception#initialize:Array(String) +56 [0]
       *XML::Error#initialize:Array(String) +46 [0]
       *XML::Error::new:XML::Error +155 [0]
       *XML::Error::new:XML::Error +76 [0]

Since Nokogiri is fine with it and both use libxml2 we're probably just missing a flag or something.

I installed a crystal 0.7.7 according to the official instructions for Ubuntu (http://crystal-lang.org/docs/installation/on_debian_and_ubuntu.html).

Nokogiri seems to relax all errors, but still produce a node tree:
require "nokogiri"

doc = Nokogiri::HTML("Test")
p doc.errors #=> [#<Nokogiri::XML::SyntaxError: Tag nav invalid>]

Maybe we should do the same. My "problem" with this approach is that you need to explicitly check for errors. The "nav" tag is here in not an error, but other "real" errors would go into this property. But at least it's better than not being able to parse these things.

I just fixed this. Now it doesn't raise and you can get the errors with the errors property. Check the specs in the above commit.

Thanks, asterite!

How do I install the nokogiri module within crystal lang?
I have no idea about it.

You don't. Use the XML module from stdlib.


MCCC-2608 Add license information

Goal
Publish SOPS decrypt GitHub action in Metro digital org as Metro digital org is the right place for all open source projects.

@blazej-budzynski How about adding the license headers to *.json, jest.config.js and *.yaml files. I am not sure if we need it there. I just wanted to confirm on this.

@blazej-budzynski How about adding the license headers to *.json, jest.config.js and *.yaml files. I am not sure if we need it there. I just wanted to confirm on this.

Last time we were told that only source code needs to be commented (so e.g. transpiled js files are also excluded)


Add a statuspage app

@mrchrisadams Migrating this from the old admin env to a public page on https://status.thegreenwebfoundation.org so we can make this visible.
We can extend this later with other statistics.

Seems one of the tests is failing, which is not caused by this change.

Hey @arendjantetteroo does this need anything else?

Some way to deploy this :)
Currently it's just a copy/paste of whats on the server, but would be nice to keep it tracked in git.

Hey @arendjantetteroo - given that the graphite web app let us make these, you reckon we still need this?
We have dashboards like this, and I think we can make them accessible publicly too. This would mean you don't need to use git to make changes.
👍 ?
https://graphite.thegreenwebfoundation.org/dashboard/Rabbit


Add E2E test case for CloudStack node failuredomain label and node name matche

Issue #, if available:
Need E2E test cases to test node labels in control plane and worker node group for CloudStack cluster.
Need E2E test cases to test node name matches for CAPI machine name.
Description of changes:
Add E2E test cases to test node labels in control plane and worker node group for CloudStack cluster.
Add E2E test cases to test node name matches for CAPI machine name.
Testing (if applicable):
2022-10-20T22:40:17.692-0400	V3	Cleaning up long running container	{"name": "eksa_1666319446710418000"}
2022-10-20T22:40:18.880-0400	V4	e2e	Validating control plane failuredomain labels
2022-10-20T22:40:18.880-0400	V4	e2e	node label: 	{"cluster.x-k8s.io/failure-domain": "az-zone1"}
2022-10-20T22:40:19.988-0400	V4	e2e	Validating worker node failuredomain labels	{"worker node group": "md-0"}
2022-10-20T22:40:19.988-0400	V4	e2e	node label: 	{"cluster.x-k8s.io/failure-domain": "az-zone1"}
    cluster.go:516: Validating cluster node status
    cluster.go:528: Validating cluster node version
    cluster.go:535: Validating cluster node and CAPI machine name match
2022-10-20T22:40:21.413-0400	V4	e2e	check node and machine name match: 	{"node name": "eksa-test-3fbdd0f-4gzlg", "CAPI machine name": "eksa-test-3fbdd0f-4gzlg"}
2022-10-20T22:40:21.414-0400	V4	e2e	check node and machine name match: 	{"node name": "eksa-test-3fbdd0f-md-0-74b8f9f8cd-cc5xb", "CAPI machine name": "eksa-test-3fbdd0f-md-0-74b8f9f8cd-cc5xb"}

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

new PR created from main, with only relevant changes


How can EFCore.BulkExtensions influence DbContext connection sequence?

A fresh new console project using VS 2022 and .NET 6:
https://github.com/uhfath/TestBulkExtensionsError
Only EFCore.BulkExtensions and Microsoft.EntityFrameworkCore.SqlServer packages added with a simple DbContext and one model.
When connecting to a remote SQL Server 2019 instance without EFCore.BulkExtensions package installed everything works as expected.
However, when simply installing the EFCore.BulkExtensions package I get the following exception (partially in Russian, so let me know if a translation needed):
A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - Цепочка сертификатов выпущена центром сертификации, не имеющим доверия.)

   at Microsoft.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at Microsoft.Data.SqlClient.TdsParserStateObject.ThrowExceptionAndWarning(Boolean callerHasConnectionLock, Boolean asyncClose)
   at Microsoft.Data.SqlClient.TdsParserStateObject.SNIWritePacket(PacketHandle packet, UInt32& sniError, Boolean canAccumulate, Boolean callerHasConnectionLock)
   at Microsoft.Data.SqlClient.TdsParserStateObject.WriteSni(Boolean canAccumulate)
   at Microsoft.Data.SqlClient.TdsParserStateObject.WritePacket(Byte flushMode, Boolean canAccumulate)
   at Microsoft.Data.SqlClient.TdsParser.TdsLogin(SqlLogin rec, FeatureExtension requestedFeatures, SessionData recoverySessionData, FederatedAuthenticationFeatureExtensionData fedAuthFeatureExtensionData)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.Login(ServerInfo server, TimeoutTimer timeout, String newPassword, SecureString newSecurePassword)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, Boolean applyTransientFaultHandling, String accessToken, DbConnectionPool pool)
   at Microsoft.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
   at Microsoft.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)
   at Microsoft.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
   at Microsoft.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
   at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
   at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
   at Microsoft.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
   at Microsoft.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
   at Microsoft.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
   at Microsoft.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry, SqlConnectionOverrides overrides)
   at Microsoft.Data.SqlClient.SqlConnection.Open(SqlConnectionOverrides overrides)
   at Microsoft.Data.SqlClient.SqlConnection.Open()
   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerConnection.OpenDbConnection(Boolean errorsExpected)
   at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenInternal(Boolean errorsExpected)
   at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.Open(Boolean errorsExpected)
   at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReader(RelationalCommandParameterObject parameterObject)
   at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.Enumerator.InitializeReader(Enumerator enumerator)
   at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.Enumerator.<>c.<MoveNext>b__19_0(DbContext _, Enumerator enumerator)
   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.Execute[TState,TResult](TState state, Func`3 operation, Func`3 verifySucceeded)
   at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.Enumerator.MoveNext()
   at System.Linq.Enumerable.TryGetSingle[TSource](IEnumerable`1 source, Boolean& found)
   at Microsoft.EntityFrameworkCore.Query.Internal.QueryCompiler.Execute[TResult](Expression query)
   at Microsoft.EntityFrameworkCore.Query.Internal.EntityQueryProvider.Execute[TResult](Expression expression)
   at System.Linq.Queryable.Count[TSource](IQueryable`1 source)
   at Program.<Main>$(String[] args) in D:\Projects\TestBulkExtensionsError\TestBulkExtensionsError\Program.cs:line 4

I'm not sure how EFCore.BulkExtensions package is influencing but the exception happens only when it's installed in the project.
Also, when testing the same test app with a local instance with and without EFCore.BulkExtensions everything works fine.
A connection string used for a remote server looks like this:
Server=host_name;Database=database_name;User Id=user_name;Password=password;

Any ideas how these could be related?
P.S. SQL Server 2019 Standard was installed with all the default settings on a Windows Server 2019 Standard.
I've never had this kind of an issue with my other projects using EFCore.BulkExtensions with this server. But they are .Net Core 2x and 3x versions (with old version of EFCore.BulkExtensions).

Not sure about this issue.
One thing that comes to mind, because exception mentions certificate,  is that nuget package after v5 was Signed for strong name, Signing the nuget package #161

I guess that if the issue was from package signing than the project itself wouldn't run or even build correctly,
whereas in this case the problem is only during connection.
I myself seeing this for the first time in my life.

Also first time seeing this.
Maybe try to load source of lib. instead of nuget and see what happens, and to debug it if possible.

Tried it just now.
When cloning the repo and checking out this tag everything works fine.
"Curiouser and curiouser" ©

Have you also tried with latest source v6 ?

We had the same issues with 6.2.3, though we were upgrading from 6.0.9 so not sure where the bug appeared.  Somehow the connection string or underlying code is telling EF core to use SSL encyrption.  Adding TrustServerCertificate will work around the issue.
-- this is the connection string that causes the issue for us:
"ConnectionString": "Server=localhost;Database=MxHuskyBaan;Trusted_Connection=True"

-- this will work around the issue
"ConnectionString": "Server=localhost;Database=MxHuskyBaan;Trusted_Connection=True;TrustServerCertificate=true;"

On our SQL 2019 instance we don't have any SSL certificates installed.  Not sure where in the code its being enabled.  We are using .Net 6 in our application.

All the issue seems to be related to the changes in 6.1.5 where Microsoft.Data.SqlClient was bumped to v4.0.0.  The issue itself is caused by the following change Microsoft made.
Encrypt default value set to true

@borisdj it might be worth adding to the readme, Microsoft.EntityFrameworkCore.SqlServer v6.0.x is using version 2.1.4.  So when using this package you are bumped from 2.1.4 to 4.0 with multiple breaking changes.

SqlClient dependency down to 2.1
Published v6.2.8


Stop updates from old version

It seems this fixed version wants to get updates from the old (Townes) version, when that one is updated. Instead, getting new versions from Github would be great. At least disable the updates from the Townes (non-fixed) version.

Hi @jeffmcneill .. the "fixed" version has an option to disable the updates from the Townes version already.  Just check under General Settings > Miscellaneous (see pic below)

I don't see this option in the latest release. Is it in main?

i have the latest <IP_ADDRESS>.5 and i see the option in Performance > General Settings > Miscellaneous

Thanks @nigrosimone I see the option now. This was released yesterday I think, which is why the earlier release did not show it. Thanks @amiga-500 also for your speedy response to this issue. Happy to be on your version of W3TC. I've used this for years, but it now seems to be working much better. ^_^


Provisioning tool is failing to create new monitoring dashboard.

Seeing this error
module.aiinfra-mig.google_compute_instance_group_manager.mig: Creation complete after 2m9s [id=projects/soumyapani-testing/zones/us-central1-a/instanceGroupManagers/spani-develop-mig]
╷
│ Error: Error creating Dashboard: googleapi: Error 400: Field gridLayout.widgets[11].xyChart.dataSets[0].timeSeriesQuery.timeSeriesQueryLanguage has an invalid value: Could not find a metric named '[workload.googleapis.com/dcgm.gpu.nvlink_traffic_rate](http://workload.googleapis.com/dcgm.gpu.nvlink_traffic_rate)'.
│ Field gridLayout.widgets[13].xyChart.dataSets[0].timeSeriesQuery.timeSeriesQueryLanguage has an invalid value: Could not find a metric named '[workload.googleapis.com/dcgm.gpu.pcie_traffic_rate](http://workload.googleapis.com/dcgm.gpu.pcie_traffic_rate)'.
│ Details:
│ [
│   {
│     "@type": "[type.googleapis.com/google.rpc.DebugInfo](http://type.googleapis.com/google.rpc.DebugInfo)",
│     "detail": "[ORIGINAL ERROR] generic::invalid_argument: com.google.apps.framework.request.BadRequestException: Field gridLayout.widgets[11].xyChart.dataSets[0].timeSeriesQuery.timeSeriesQueryLanguage has an invalid value: Could not find a metric named '[workload.googleapis.com/dcgm.gpu.nvlink_traffic_rate'](http://workload.googleapis.com/dcgm.gpu.nvlink_traffic_rate%27).\nField gridLayout.widgets[13].xyChart.dataSets[0].timeSeriesQuery.timeSeriesQueryLanguage has an invalid value: Could not find a metric named '[workload.googleapis.com/dcgm.gpu.pcie_traffic_rate](http://workload.googleapis.com/dcgm.gpu.pcie_traffic_rate)'. [google.rpc.error_details_ext] { message: \"Field gridLayout.widgets[11].xyChart.dataSets[0].timeSeriesQuery.timeSeriesQueryLanguage has an invalid value: Could not find a metric named \\'[workload.googleapis.com/dcgm.gpu.nvlink_traffic_rate\\'](http://workload.googleapis.com/dcgm.gpu.nvlink_traffic_rate%5C%5C%27).\\nField gridLayout.widgets[13].xyChart.dataSets[0].timeSeriesQuery.timeSeriesQueryLanguage has an invalid value: Could not find a metric named \\'[workload.googleapis.com/dcgm.gpu.pcie_traffic_rate\\'](http://workload.googleapis.com/dcgm.gpu.pcie_traffic_rate%5C%5C%27).\" }"
│   }
│ ]
│
│   with module.aiinfra-default-dashboard.google_monitoring_dashboard.dashboard,
│   on .terraform/modules/aiinfra-default-dashboard/modules/monitoring/dashboard/[main.tf](http://main.tf/) line 22, in resource "google_monitoring_dashboard" "dashboard":
│   22: resource "google_monitoring_dashboard" "dashboard" {
│
╵
Terraform apply failed with error 1.
Listed 0 items.

Until we have the right fix for this issue, can we add a simple sleep for 30 seconds and see if that resolves the issue
https://registry.terraform.io/providers/hashicorp/time/latest/docs/resources/sleep

wip #101

adding a simple depends_on = [aiinfra-compute] does not work since the startup scripts run after the mig is created
adding a sleep n whatever the n is just pawning this problem off to future us

I'm going to see if creating the metricDescriptors before terraform apply will "solve" this issue (until we add more metrics to the dashboard), but I think that #104 might become a high priority.


Cant boot into 1440p UW display

May be related to https://github.com/osy86/HaC-Mini/issues/83
However the fix for that does not work for me.
Describe the bug
Booting into new, 1440p monitor, there is no display after apple logo.
If I switch to the old one after boot, the display works.
If I switch back to the new one, there's nothing.
Booting into old, 1080p monitor, the display is fine.
If I switch to the new one after boot, the display appears and the resolution is correctly set to 1440p. I just can't boot directly into it.
These are both HDMI connections. I installed the OS to the SSD on the old monitor.
Expected behavior
Display on 1440p
Configuration

HaC Mini version: 2
OSX version: 10.15.2
NUC model: NUC8i7HVK
Boot SSD model and protocol: Samsung P871b, SATA
Display port(s) used: HDMI
Display resolution(s): 1080p, 1440p

Modifications
NA
Panic log
NA

I currently use a Dell U3415W (3440x1440p) and it boots natively into this. I am using a miniDP to DP cable.

Another case of user (me) error. My HDMI cable was plugged into the HDMI 1.2 port on my monitor (doh!).
Can also confirm miniDP works great for me. I was gonna switch anyways when my cable arrived.
Closing issue.


Try Grisu-Exact

https://www.reddit.com/r/cpp/comments/i8pgzc/updates_in_grisuexact/
https://github.com/jk-jeon/Grisu-Exact/blob/master/other_files/Grisu-Exact.pdf
https://github.com/jk-jeon/Grisu-Exact

Dragonbox is strictly better


Support evict annotation for namespaces

The operator currently auto-excludes all namespaces with openshift-* or kube-* prefixes from eviction. This makes sense to prevent users from breaking their cluster with the Descheduler, and those are reserved prefixes so users should not be able to create their own namespaces that match the pattern.
However, it may be useful for administrators and support to be able to include certain system namespaces for rebalancing (for example, during and after upgrades). Perhaps we could add a check for the same descheduler.alpha.kubernetes.io/evict annotation on namespaces before assuming they should be excluded. Pods within that namespace would still be subject to the same eviction rules
cc @ingvagabund wdyt?

We might also introduce a new profile which will do this right before/after the upgrade if this is the only use case.

@damemi , @ingvagabund - In addition to the upgrades, the other scenarios I can think of which could possibly disrupt existing core workloads is node/machine replacements/addition/removal. For now, the worker and infra nodes are supported as part of this but in future will be extended to control plane too (subject to change). Another scenario can be a MachineConfig change to cause rolling reboot of nodes in the respective MachineConfigPool (triggered change which is not an upgrade).
Considering above scenarios as well, I think we might need to stretch openshift* namespace inclusion criteria further. WDYT?

Descheduler is very polite by using the eviction API.  We have efforts like openshift/origin#26160 underway to improve our PDB coverage.  If folks using the eviction API can cause excessive disruption in the OpenShift core, that sounds like it's really a missing/miscongured PDB situation to me.  I expect we have some bugs like that today.  Hopefully openshift/origin#26160 turns them up, and we get them fixed.  Once we get them fixed, can we pivot to having the descheduler cover the kube-system and openshift-* namespaces by default?  Because "don't ask about evicting us, we don't handle that well" doesn't seem like a good long-term plan.


Add a LRU cache for Client

To reduce the overhead and increase performance.
e.g: http://avoidwork.github.io/tiny-lru/
Or any other in this list https://github.com/dominictarr/bench-lru

Please refer to the discussion in the dgraph-js-http. Closing for now


Fix date hiding problem

This commit solves the theme can't hide date properly on the main page when "no_date: true", if maintainers find something inappropriate  or have any questions, please do let me know, thanks a lot!

Cheers!

Thanks for your pr! ❤ 👍


Basic flow for rendering custom Column Filter

i. Custom Renderer for Column Filter.

@kumarankit1234 Can we close #8 and review and merge this one instead?


BelongsToManyCheckboxList & BelongsToManyMultiSelect default state got overwritten

Package
filament/forms
Package Version
v2.12.17
Laravel Version
v9.14.1
Livewire Version
v2.10.5
PHP Version
PHP 8.1.3
Bug description
The default state of the BelongsToManyCheckboxList and BelongsToManyMultiSelect got broken when #2519 got merged.
Steps to reproduce

Set up a Model with a belongsToMany relationship.
Set up BelongsToManyCheckboxList form field into the form builder and call ->default()
The form field does not get populated with the default values that was set from the previous step.

Relevant log output
No response

Does #2558 fix this?

I'm sorry for the late response! I was caught up with work last night and didn't have the time to test, but YES #2558 definitely fixed it!
Thank you very much and have a good day!


Library directives support

This PR continues the work started in #7549

:+1:

We should also add a new property to tsconfig.json "types" that act as /// <reference types=".." />.  @RyanCavanaugh is there a reason that was not included?

No, it should be included

:+1:

This PR breaks the optional nature of the host argument in createProgram.

Oops, good catch! Thanks @jbrantly for noticing this, fix will be out shortly


Simple receive_buffer example.

Hi!
Is it possible to have a small example on how does the receive_buffer work?

Raffaele, the main example is this one https://github.com/STEllAR-GROUP/hpx/blob/424334a0a36a56cbc2d9cd0a6db67030928d789d/examples/1d_stencil/1d_stencil_8.cpp but I'll create a simpler one. What is the data structure that you exchange between nodes - just a simple array of doubles, or is there a more complex type wrapped around it?

Raffaele, the main example is this one https://github.com/STEllAR-GROUP/hpx/blob/424334a0a36a56cbc2d9cd0a6db67030928d789d/examples/1d_stencil/1d_stencil_8.cpp but I'll create a simpler one. What is the data structure that you exchange between nodes - just a simple array of doubles, or is there a more complex type wrapped around it?

I exchange just a simple array of double or complex (which is also an array of doubles).

@rasolca Please see #2188 for the example you asked for. Please let us know if that resolves you issue.

Yes, the example is what I was asking for. Thanks.


Allow refinement of 1D (segment) meshes

Allow for the creation of 1D low-order refined meshes with the Mesh(orig_mesh, ref_factor, ref_type) constructor. Also allow for a ref_factor of 1, which is trivial, but could be useful as a "base case" for verifying algorithms.

This also brings up the question of whether PointFiniteElement should be considered a NodalTensorFiniteElement for consistency. This would get rid of a special-case because in the 1D case there is no DofMap for the boundary elements.

Hi, @pazner ,
The code looks good but I'm not sure how to test it.  I wrote a non-trivial mesh with 1D elements embedded in 2D space but GLVis can't visualize it.  Example 1p runs and seems to behave normally.  Do you think you could try your code on this mesh and let us know how it behaves?
Thanks,
Mark
MFEM mesh v1.0

#
# MFEM Geometry Types (see mesh/geom.hpp):
#
# POINT       = 0
# SEGMENT     = 1
# TRIANGLE    = 2
# SQUARE      = 3
# TETRAHEDRON = 4
# CUBE        = 5
#

dimension
1

elements
3
1 1 0 1
2 1 0 2
3 1 0 3

boundary
3
1 0 1
2 0 2
3 0 3

vertices
4
2
0 0
0.5 0.5
-0.5 0.5
0 -1

It looks like it does the right thing, e.g. if we refine with order 2 then we get the mesh below, which is the same as the original but with midpoints added to each of the segments.
MFEM mesh v1.0

#
# MFEM Geometry Types (see mesh/geom.hpp):
#
# POINT       = 0
# SEGMENT     = 1
# TRIANGLE    = 2
# SQUARE      = 3
# TETRAHEDRON = 4
# CUBE        = 5
# PRISM       = 6
#

dimension
1

elements
6
1 1 0 4
1 1 4 1
2 1 0 5
2 1 5 2
3 1 0 6
3 1 6 3

boundary
3
1 0 1
2 0 2
3 0 3

vertices
7
2
0 0
0.5 0.5
-0.5 0.5
0 -1
0.25 0.25
-0.25 0.25
0 -0.5

Works really nicely, Will!
lor-transfer -m ../../data/inline-segment.mesh


Fix remove playing notification issue when app is swiped from recents

Fix GitHub issue #250
When I swipe UAMP away from recents, the removeNowPlayingNotification() isn't called because in the method updateNotification() the metadata is already null if(mediaController.metadata == null) return and notification is stuck in the notification tray and control icons also does not work.

License signed


Is it possible to @link to a particular overload?

For example, say I want to link to another overload of the same function.
JSDoc descends from JavaDoc, which of course has always supported linking to overloads.  Is it a new concept now?

Since javacript doesnt have overloads, JSDoc has no notion of them. how does JavaDoc do linking to overloads? we might be able to implement it with similar syntax

Here's what TSDoc does: https://tsdoc.org/pages/tags/link/
Note they consider how to distinguish between static and instance methods with the same name, among other cases.
JavaDoc supports this set of syntaxes:


Perform v1.9.0 release

Changelog commit goes before the actual release, as it is part of what we distribute as source (and is re-used by downstream packagers).

PTAL

ok to test

LGTM


Type definitions for Vortex Web client vortex-web-client.d.ts

I've been only using JavaScript and TypeScript for a couple of months so maybe I'm wrong but I don't understand with the delivered definition how to specify custom QoS.
In JavaScript it's possible to write:
var dwQos = new dds.DataWriterQos(dds.Partition("chatroom"), dds.Reliability.Reliable, dds.Durability.Persistent);
Qos are sent to server using pairs. So for exemple dds.Reliability.Reliable maps to {"id":5,"k":3}.
With the type definition, I cannot get the same or only deserialization errors.
Thanks.

@Pro ?

Does it work if you leave out the Partition Qos?
I.e. var dwQos = new dds.DataWriterQos(dds.Reliability.Reliable, dds.Durability.Persistent);
I'm currently only using emtpy Qos, but will test it tomorrow.
Can you post a minimal code example (http://stackoverflow.com/help/mcve) which I can check?

@WalterRawley You can use the rest case for a simple example where you can try to reproduce the problem: https://github.com/borisyankov/DefinitelyTyped/blob/2d4c4679bc2b509f27435a4f9da5e2de11258571/vortex-web-client/vortex-web-client-tests.ts

@Pro It doesn't compile (with VS2013). I even didn't catch we should use that way. So to make it compile, I added a "static" instruction for each QoS policy in your definition file:
export class Durability implements Policy {
static Volatile:any;
static TransientLocal:any;
[...]
I'll try this way another day because for now I have another problem running the sample. I don't understand why, but it's not related to this issue.

Should now be fixed: https://github.com/borisyankov/DefinitelyTyped/commit/5037a214342644ce5425c74d41fd1721b2a07a08
Issue can be closed.

Works fine.
Thanks a lot!


Inference server not working with models tuned on <|system|>,<|prompter|>,<|assistant|> or <|im_start|>,<|im_end|> format

Trying to run the vLLM server with https://huggingface.co/Open-Orca/LlongOrca-13B-16k but it returns just white space.
It uses messages formatted as:
<|im_start|>system
You are LlongOrca, a large language model trained by Alignment Lab AI. Write out your reasoning step-by-step to be sure you get the right answers!
<|im_end|>

Also tried https://huggingface.co/OpenAssistant/llama2-13b-orca-8k-3319 but it returns empty.
Message format:
<|system|>system message</s><|prompter|>user prompt</s><|assistant|>

Is it possible to use models that require such different formatting? The vLLM request is abstracted away and only sends messages list. I tried wrapping the content with the special tokens.
The only prompt format that works for me on vLLM server is
### Instruction:
<prompt>
### Response:

from Open-Orca/OpenOrca-Platypus2-13B
Maybe I am missing an argument when running the server?

On further investigation it seems related to the get_conversation_template() function.
It returns the wrong template for the model (Open-Orca/LlongOrca-13B-16k, should be with <|im_start|> and <|im_end|>)
conv= {'name': 'one_shot', 'system_template': '{system_message}', 'system_message': "A chat between a curious human and an artificial intelligence assistant. The assistant gives helpful, detailed, and polite answers to the human's questions.", 'roles': ('Human', 'Assistant'), 'messages': [['Human', 'Got any creative ideas for a 10 year old’s birthday?'], ['Assistant', "Of course! Here are some creative ideas for a 10-year-old's birthday party:\n1. Treasure Hunt: Organize a treasure hunt in your backyard or nearby park. Create clues and riddles for the kids to solve, leading them to hidden treasures and surprises.\n2. Science Party: Plan a science-themed party where kids can engage in fun and interactive experiments. You can set up different stations with activities like making slime, erupting volcanoes, or creating simple chemical reactions.\n3. Outdoor Movie Night: Set up a backyard movie night with a projector and a large screen or white sheet. Create a cozy seating area with blankets and pillows, and serve popcorn and snacks while the kids enjoy a favorite movie under the stars.\n4. DIY Crafts Party: Arrange a craft party where kids can unleash their creativity. Provide a variety of craft supplies like beads, paints, and fabrics, and let them create their own unique masterpieces to take home as party favors.\n5. Sports Olympics: Host a mini Olympics event with various sports and games. Set up different stations for activities like sack races, relay races, basketball shooting, and obstacle courses. Give out medals or certificates to the participants.\n6. Cooking Party: Have a cooking-themed party where the kids can prepare their own mini pizzas, cupcakes, or cookies. Provide toppings, frosting, and decorating supplies, and let them get hands-on in the kitchen.\n7. Superhero Training Camp: Create a superhero-themed party where the kids can engage in fun training activities. Set up an obstacle course, have them design their own superhero capes or masks, and organize superhero-themed games and challenges.\n8. Outdoor Adventure: Plan an outdoor adventure party at a local park or nature reserve. Arrange activities like hiking, nature scavenger hunts, or a picnic with games. Encourage exploration and appreciation for the outdoors.\nRemember to tailor the activities to the birthday child's interests and preferences. Have a great celebration!"]], 'offset': 2, 'sep_style': <SeparatorStyle.ADD_COLON_SINGLE: 1>, 'sep': '\n### ', 'sep2': None, 'stop_str': '###', 'stop_token_ids': None}

The get_conversation_template function comes from FastChat. So this issue may belong there.

When inferencing mistralai/Mistral-7B-Instruct-v0.1 model vLLM using this template instead of this one

how do we go about changing the system prompt?

@horiacristescu I have similar problem. Can you try setting --served-model-name zephyr and then requesting the model under zephyr name. That will actually cause retrieval of the right conversation format. But still, it is returning ChatML special tokens and just generating the conversation on-and-on for me. I still had to add stopping sequences for the special tokens. vLLM it seems to be lacking the stopping on special tokens.


No ticklers

This change is to use timers in the UrlDBFunction (ProcessFunction) to keep iterating over unique domains. This means we don't need ticklers, which cleans up the workflow architecture.

So we no longer have "special" CrawlStateUrls, and we don't need a DomainDBFunction


Serialize accesses to SSL socket factory contexts

Description:
The ssl_ctx_ fields of the ServerSslSocketFactory and ClientSslSocketFactory are accessed and mutated from different threads without external serialization. This is a bug since instances of std::shared_ptr are not thread-safe (though different instances pointing to the same object are). This patch fixes the bug by using a mutex to serialize accesses.
Risk Level: Low
Testing: ran test suite
Docs Changes: n/a
Release Notes: n/a

I am not convinced that such thread protection is needed.  Could you provide documents or sample code to prove it?

Sure. From https://en.cppreference.com/w/cpp/memory/shared_ptr/atomic:
If multiple threads of execution access the same std::shared_ptr object without synchronization
and any of those accesses uses a non-const member function of shared_ptr then a data race
will occur...

Running our internal TSAN against HEAD showed just such a data race between shared_ptr::operator= and shared_ptr::shared_ptr(const shared_ptr&). This is only an issue because the same shared_ptr instance is being used; two shared_ptrs that point to the same data can be interacted with separately by different threads.
I don't know why the CI TSAN didn't catch this, though.

I see.  Thanks.  In that case, we should use Read/Write lock.   For most of Read operations, they should share.
Please use:
std::shared_timed_mutex mutex_;
std::shared_lockstd::shared_timed_mutex lock(mutex_);
std::unique_lockstd::shared_timed_mutex

Yup, reader/writer locks sounds like a good optimization. I've left the locks as absl::Mutex instances since that's what Envoy uses but removed the Lock()/Unlock() calls in favor of the RAII-based approach, substituting the absl classes for std::shared_lock and std::unique_lock.

LGTM.

Can you try retriggering CI?


Enable option to create schema and cred-def even if organization joins ecosystem

Enable the option to create schema and cred-def even if the organization joins the ecosystem
Acceptance criteria:

[ ] Add an option to create schema and cred-def for his own organization

This is completed


CanonFirmwareSoftware/Photography: How to Shoot Lightning 🌩

|How to Shoot LIGHTNING for “Shocking” Landscape Photos (VIDEO) / Shutterbug|

Already implemented


Why is it now minimizing to the system tray?

There is no reason for me to leave your program running 24/7 so why is it minimizing to the tray when I kill the UI now?  At the very least give us the option to not have it minimize to the tray...

Step 1. Right-click the tray icon.
Setp 2. Click on the Exit menu.

...

Don't mistake favors for rights, and start by learning how to ask politely.


Split nt.go into multiple files

Group methods by domain:

wait
wait-for-sync
validate
metrics

/lgtm
/approve


Add RTL support to AppBar

Fixes #11381

 with test

LG
Is #11381 done with this? Does NavigationToolbar need RTL awareness?

Is #11381 done with this?

Yes.

Does NavigationToolbar need RTL awareness?

It does!  Writing the test that @Hixie asked for uncovered that issue.  The updated patch has more changes.  :)

@xster Now with 100% more NavigationToolbar goodness.


Removed run_all_in_graph_and_eager_mode multilable confusion matrix.

@ssaishruthi
You are owner of some files modified in this pull request.
Would you kindly review the changes whenever you have the time to?
Thank you very much.


make wget upgrade-self use no-check-certificate

In a system that needs no-check-certificate, calling wget without it creates a copy of the file that's empty/useless.
So, this makes the default fallback not check certificates.

Why do your system need no-check-certificate?
Almost system does not need it.
You must not decrease the whole security level by resolving a special case, I think.

I'll look into it tomorrow morning when I get to that work location.
At my main work location, wget calls within cygwin always give an error
about not being able to verify certificates and at the location I'm at now,
everything works fine with a default installation.
And AFAIK, the networks here are set up the same (I believe the same IT
folks set up both schools but I'm not sure).
On Mon, Dec 9, 2019 at 4:21 PM kou1okada<EMAIL_ADDRESS>wrote:

Why do your system need no-check-certificate?
Almost system does not need it.
You must not decrease the whole security level by resolving a special
case, I think.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kou1okada/apt-cyg/pull/60?email_source=notifications&email_token=AC5TL7I6BIPC44JFHBHDS3TQXXWWDA5CNFSM4JYC6Q72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGIDMRY#issuecomment-563099207,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC5TL7MBVIGM4XWTYVGNEN3QXXWWDANCNFSM4JYC6Q7Q
.

Does your environment install ca-certificates package correctly?
It provides CA certifications and it is also required from wget.
$ apt-cyg rdepends ca-certificates | grep ^wget
wget                                     1      3       3
$ apt-cyg depends wget | grep ^ca-certificates
ca-certificates                          1      3       3

So, if you install wget, it will be installed automatically.
If it is not installed correctly, apt-cyg dist-upgrade may solve the problem.
I think following suggestions will help people who have similar situations for you.

Catch a failing wget and abort task.
Provide an option to use --no-check-certificate.

But, ignoring the certification for whole environment is a bad idea.

ca-certificates is installed. But I receive:
ERROR: The certificate of ‘raw.githubusercontent.com’ is not trusted.
ERROR: The certificate of ‘raw.githubusercontent.com’ hasn't got a known
issuer.
On Tue, Dec 10, 2019 at 12:07 PM kou1okada<EMAIL_ADDRESS>wrote:

Does your environment install ca-certificates package correctly?
It provides CA certifications and it is also required from wget.
$ apt-cyg rdepends ca-certificates | grep ^wget
wget                                     1      3       3
$ apt-cyg depends wget | grep ^ca-certificates
ca-certificates                          1      3       3
So, if you install wget, it will be installed automatically.
If it is not installed correctly, apt-cyg dist-upgrade may solve the
problem.
I think following suggestions will help people who have similar situations
for you.

Catch a failing wget and abort task.
Provide an option to use --no-check-certificate.

But, ignoring the certification for whole environment is a bad idea.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kou1okada/apt-cyg/pull/60?email_source=notifications&email_token=AC5TL7PZAC43JXLKFRUJ7EDQX4BVLA5CNFSM4JYC6Q72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGMMINA#issuecomment-563659828,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC5TL7LQ5AWR5IJUF7KXCFDQX4BVLANCNFSM4JYC6Q7Q
.

Shouldn't you doubt the security risks with MITM (man in the middle ) attack?
You must check with openssl as below:
$ echo|openssl s_client -connect raw.githubusercontent.com:443
CONNECTED(00000004)
---
Certificate chain
 0 s:C = US, ST = California, L = San Francisco, O = "GitHub, Inc.", CN = www.github.com
   i:C = US, O = DigiCert Inc, OU = www.digicert.com, CN = DigiCert SHA2 High Assurance Server CA
 1 s:C = US, O = DigiCert Inc, OU = www.digicert.com, CN = DigiCert SHA2 High Assurance Server CA
   i:C = US, O = DigiCert Inc, OU = www.digicert.com, CN = DigiCert High Assurance EV Root CA
---
Server certificate
-----BEGIN CERTIFICATE-----
MIIHqDCCBpCgAwIBAgIQCDqEWS938ueVG/iHzt7JZjANBgkqhkiG9w0BAQsFADBw
MQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGlnaUNlcnQgSW5jMRkwFwYDVQQLExB3
d3cuZGlnaWNlcnQuY29tMS8wLQYDVQQDEyZEaWdpQ2VydCBTSEEyIEhpZ2ggQXNz
dXJhbmNlIFNlcnZlciBDQTAeFw0xNzAzMjMwMDAwMDBaFw0yMDA1MTMxMjAwMDBa
MGoxCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpDYWxpZm9ybmlhMRYwFAYDVQQHEw1T
YW4gRnJhbmNpc2NvMRUwEwYDVQQKEwxHaXRIdWIsIEluYy4xFzAVBgNVBAMTDnd3
dy5naXRodWIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxtPx
ijvPpEXyy3Bn10WfoWmKTW753Uv2PusDNmalx/7mqFqi5BqK4xWQHQgSpyhedgtW
IXWCJGHtgFVck+DBAbHiHsE67ewpV1a2l2GpqNCFTU77UsoNVD/xPyx3k+cPX9y8
rqjMiZB3xs1zKDYBkcoBVrA+iO323YkJmCLEXCO2O7b1twLFWkNwMd7e7nteu2uC
MvxNp5Qg22MIn33t2egMPfIDU/TcKDfyaty5+s6F3gzh7eIgnqNQN0T/5fpaYkqd
x8j21QDsIyF/CfSpA5qKLuhluu8xrUbnc0MigX7VThS9PbfxMSQ1cQQfbGdxoQNJ
TNHxXv+ZTXAxKCju5wIDAQABo4IEQjCCBD4wHwYDVR0jBBgwFoAUUWj/kK8CB3U8
zNllZGKiErhZcjswHQYDVR0OBBYEFDCCKdhtTODUosYQSAWAh6i8qukSMHsGA1Ud
EQR0MHKCDnd3dy5naXRodWIuY29tggwqLmdpdGh1Yi5jb22CCmdpdGh1Yi5jb22C
CyouZ2l0aHViLmlvgglnaXRodWIuaW+CFyouZ2l0aHVidXNlcmNvbnRlbnQuY29t
ghVnaXRodWJ1c2VyY29udGVudC5jb20wDgYDVR0PAQH/BAQDAgWgMB0GA1UdJQQW
MBQGCCsGAQUFBwMBBggrBgEFBQcDAjB1BgNVHR8EbjBsMDSgMqAwhi5odHRwOi8v
Y3JsMy5kaWdpY2VydC5jb20vc2hhMi1oYS1zZXJ2ZXItZzUuY3JsMDSgMqAwhi5o
dHRwOi8vY3JsNC5kaWdpY2VydC5jb20vc2hhMi1oYS1zZXJ2ZXItZzUuY3JsMEwG
A1UdIARFMEMwNwYJYIZIAYb9bAEBMCowKAYIKwYBBQUHAgEWHGh0dHBzOi8vd3d3
LmRpZ2ljZXJ0LmNvbS9DUFMwCAYGZ4EMAQICMIGDBggrBgEFBQcBAQR3MHUwJAYI
KwYBBQUHMAGGGGh0dHA6Ly9vY3NwLmRpZ2ljZXJ0LmNvbTBNBggrBgEFBQcwAoZB
aHR0cDovL2NhY2VydHMuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0U0hBMkhpZ2hBc3N1
cmFuY2VTZXJ2ZXJDQS5jcnQwDAYDVR0TAQH/BAIwADCCAfUGCisGAQQB1nkCBAIE
ggHlBIIB4QHfAHYApLkJkLQYWBSHuxOizGdwCjw1mAT5G9+443fNDsgN3BAAAAFa
/UBqBAAABAMARzBFAiBFXsWaC1bup8Q0JgrY9EgIxjqi1v2fA6Zg44iRXSQyywIh
AIzhzU1zlseJh5+yXc5U1I+pgqRmXb1XcPIsGL8oOdwjAHUAVhQGmi/XwuzT9eG9
RLI+x0Z2ubyZEVzA75SYVdaJ0N0AAAFa/UBqZQAABAMARjBEAiBKQMsySmj69oKZ
MeC+MDokLrrVN2tK+OMlzf1T5qgHtgIgRJLNGvfWDmMpCK/iWPSmMsYK2yYyTl9K
btHBtP5WpkcAdgDuS723dc5guuFCaR+r4Z5mow9+X7By2IMAxHuJeqj9ywAAAVr9
QGofAAAEAwBHMEUCIA2n0TbeAa5KbuOpnXpJbnObwckpOsHsaN+2rA7ZA16YAiEA
l7JTnVPdmFcauzwLjgNESMRFtn4Brzm9XJTPJbaWPacAdgC72d+8H4pxtZOUI5eq
kntHOFeVCqtS6BqQlmQ2jh7RhQAAAVr9QGoRAAAEAwBHMEUCIQCqrtuq71J6TM7w
KMWeSAROdTa8f35GoLMImJXONSNHfQIgONvSu/VH5jlZ1+PD+b6ThFF1+pV7wp7w
q+/8xiHUMlswDQYJKoZIhvcNAQELBQADggEBAJl+1i/OG6YV9RWz7/EwwR9UEJKk
jEPAvL2lDQBT4kLBhW/lp6lBmUtGEVrd/egnaZe2PKYOKjDbM1O+g7CqCIkEfmY1
5VyzLCh/p7HlJ3ltgSaJ6qBVUXAQy+tDWWuqUrRG/dL/iRaKRdoOv4cNU++DJMUX
rRJjQHSATb2kyd102d8cYQIKcbCTJC8tqSB6Q4ZEEViKRZvXXOJm66bG8Xyn3N2v
J4k598Gamch/NHrZOXODy3N1vBawTqFJLQkSjU4+Y//wiHHfUEYrpTg92zgIlylk
3svH64hwWd1i3BZ2LTBq46MvQKU2D8wFdtXgbgRAPWohX79Oo6hs0Jghub0=
-----END CERTIFICATE-----
subject=C = US, ST = California, L = San Francisco, O = "GitHub, Inc.", CN = www.github.com

issuer=C = US, O = DigiCert Inc, OU = www.digicert.com, CN = DigiCert SHA2 High Assurance Server CA

---
No client certificate CA names sent
Peer signing digest: SHA512
Peer signature type: RSA
Server Temp Key: X25519, 253 bits
---
SSL handshake has read 3833 bytes and written 430 bytes
Verification: OK
---
New, TLSv1.2, Cipher is ECDHE-RSA-AES128-GCM-SHA256
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
    Protocol  : TLSv1.2
    Cipher    : ECDHE-RSA-AES128-GCM-SHA256
    Session-ID: 8837E1F890B3153AD729B29D632BB165F8F3D21953FF5FE1C18A8256BD660B80
    Session-ID-ctx:
    Master-Key: 2E182D7F449EA6934AF5A9AE0BCEB0849810DD6AC597392958B77A4AFD83F663D0A8DCA65143126E99B1C69061B27748
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    TLS session ticket lifetime hint: 7200 (seconds)
    TLS session ticket:
    0000 - 66 8a e6 2a 60 53 00 d8-8b 4b 1b db b8 2e 89 b1   f..*`S...K......
    0010 - f2 b7 1d 1b dc 61 05 2f-44 a5 13 47 54 19 94 5f   .....a./D..GT.._
    0020 - 85 9d 3f cb 63 05 4f 86-01 5e 98 80 66 ab c3 d4   ..?.c.O..^..f...
    0030 - 71 f8 4c f6 ba bd 05 ca-40 e4 e7 11 25 b3 06 3f<EMAIL_ADDRESS>    0040 - ff fa b0 15 fc e5 dd 4d-a3 53 47 60 62 f8 0d 7f   .......M.SG`b...
    0050 - 1c 9a 9c 62 66 41 9b fb-95 90 65 a1 c3 d4 e4 e5   ...bfA....e.....
    0060 - c5 99 02 f5 e7 81 65 89-ad 7d f8 6a 37 1b 40 59   ......e..}.j7.@Y
    0070 - 3f ac cc 0d 47 6f e4 f7-5b 80 bd be b0 4b b7 d1   ?...Go..[....K..
    0080 - 4f 95 a2 64 9a 3e b1 93-81 a3 bc 83 59 b1 b2 86   O..d.>......Y...
    0090 - 2e ba 1f 58 4a 39 cc a3-1a 88 71 d5 ae b8 ce cf   ...XJ9....q.....
    00a0 - 25 27 e5 3b 04 d5 9a 11-00 b2 8c b2 5f 26 2b 12   %'.;........_&+.
    00b0 - 33 a8 83 18 e8 11 ce ab-ad b8 b8 bb ce 6f 11 68   3............o.h

    Start Time:<PHONE_NUMBER>
    Timeout   : 7200 (sec)
    Verify return code: 0 (ok)
    Extended master secret: yes
---

and
$ echo|openssl s_client -connect raw.githubusercontent.com:443 2>/dev/null| ope
nssl x509 -noout -text
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            08:3a:84:59:2f:77:f2:e7:95:1b:f8:87:ce:de:c9:66
        Signature Algorithm: sha256WithRSAEncryption
        Issuer: C = US, O = DigiCert Inc, OU = www.digicert.com, CN = DigiCert SHA2 High Assurance Server CA
        Validity
            Not Before: Mar 23 00:00:00 2017 GMT
            Not After : May 13 12:00:00 2020 GMT
        Subject: C = US, ST = California, L = San Francisco, O = "GitHub, Inc.", CN = www.github.com
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                RSA Public-Key: (2048 bit)
                Modulus:
                    00:c6:d3:f1:8a:3b:cf:a4:45:f2:cb:70:67:d7:45:
                    9f:a1:69:8a:4d:6e:f9:dd:4b:f6:3e:eb:03:36:66:
                    a5:c7:fe:e6:a8:5a:a2:e4:1a:8a:e3:15:90:1d:08:
                    12:a7:28:5e:76:0b:56:21:75:82:24:61:ed:80:55:
                    5c:93:e0:c1:01:b1:e2:1e:c1:3a:ed:ec:29:57:56:
                    b6:97:61:a9:a8:d0:85:4d:4e:fb:52:ca:0d:54:3f:
                    f1:3f:2c:77:93:e7:0f:5f:dc:bc:ae:a8:cc:89:90:
                    77:c6:cd:73:28:36:01:91:ca:01:56:b0:3e:88:ed:
                    f6:dd:89:09:98:22:c4:5c:23:b6:3b:b6:f5:b7:02:
                    c5:5a:43:70:31:de:de:ee:7b:5e:bb:6b:82:32:fc:
                    4d:a7:94:20:db:63:08:9f:7d:ed:d9:e8:0c:3d:f2:
                    03:53:f4:dc:28:37:f2:6a:dc:b9:fa:ce:85:de:0c:
                    e1:ed:e2:20:9e:a3:50:37:44:ff:e5:fa:5a:62:4a:
                    9d:c7:c8:f6:d5:00:ec:23:21:7f:09:f4:a9:03:9a:
                    8a:2e:e8:65:ba:ef:31:ad:46:e7:73:43:22:81:7e:
                    d5:4e:14:bd:3d:b7:f1:31:24:35:71:04:1f:6c:67:
                    71:a1:03:49:4c:d1:f1:5e:ff:99:4d:70:31:28:28:
                    ee:e7
                Exponent: 65537 (0x10001)
        X509v3 extensions:
            X509v3 Authority Key Identifier:
                keyid:51:68:FF:90:AF:02:07:75:3C:CC:D9:65:64:62:A2:12:B8:59:72:3B

            X509v3 Subject Key Identifier:
                30:82:29:D8:6D:4C:E0:D4:A2:C6:10:48:05:80:87:A8:BC:AA:E9:12
            X509v3 Subject Alternative Name:
                DNS:www.github.com, DNS:*.github.com, DNS:github.com, DNS:*.github.io, DNS:github.io, DNS:*.githubusercontent.com, DNS:githubusercontent.com
            X509v3 Key Usage: critical
                Digital Signature, Key Encipherment
            X509v3 Extended Key Usage:
                TLS Web Server Authentication, TLS Web Client Authentication
            X509v3 CRL Distribution Points:

                Full Name:
                  URI:http://crl3.digicert.com/sha2-ha-server-g5.crl

                Full Name:
                  URI:http://crl4.digicert.com/sha2-ha-server-g5.crl

            X509v3 Certificate Policies:
                Policy: 2.16.840.1.114412.1.1
                  CPS: https://www.digicert.com/CPS
                Policy: <IP_ADDRESS>.2.2

            Authority Information Access:
                OCSP - URI:http://ocsp.digicert.com
                CA Issuers - URI:http://cacerts.digicert.com/DigiCertSHA2HighAssuranceServerCA.crt

            X509v3 Basic Constraints: critical
                CA:FALSE
            CT Precertificate SCTs:
                Signed Certificate Timestamp:
                    Version   : v1 (0x0)
                    Log ID    : A4:B9:09:90:B4:18:58:14:87:BB:13:A2:CC:67:70:0A:
                                3C:35:98:04:F9:1B:DF:B8:E3:77:CD:0E:C8:0D:DC:10
                    Timestamp : Mar 23 22:19:01.508 2017 GMT
                    Extensions: none
                    Signature : ecdsa-with-SHA256
                                30:45:02:20:45:5E:C5:9A:0B:56:EE:A7:C4:34:26:0A:
                                D8:F4:48:08:C6:3A:A2:D6:FD:9F:03:A6:60:E3:88:91:
                                5D:24:32:CB:02:21:00:8C:E1:CD:4D:73:96:C7:89:87:
                                9F:B2:5D:CE:54:D4:8F:A9:82:A4:66:5D:BD:57:70:F2:
                                2C:18:BF:28:39:DC:23
                Signed Certificate Timestamp:
                    Version   : v1 (0x0)
                    Log ID    : 56:14:06:9A:2F:D7:C2:EC:D3:F5:E1:BD:44:B2:3E:C7:
                                46:76:B9:BC:99:11:5C:C0:EF:94:98:55:D6:89:D0:DD
                    Timestamp : Mar 23 22:19:01.605 2017 GMT
                    Extensions: none
                    Signature : ecdsa-with-SHA256
                                30:44:02:20:4A:40:CB:32:4A:68:FA:F6:82:99:31:E0:
                                BE:30:3A:24:2E:BA:D5:37:6B:4A:F8:E3:25:CD:FD:53:
                                E6:A8:07:B6:02:20:44:92:CD:1A:F7:D6:0E:63:29:08:
                                AF:E2:58:F4:A6:32:C6:0A:DB:26:32:4E:5F:4A:6E:D1:
                                C1:B4:FE:56:A6:47
                Signed Certificate Timestamp:
                    Version   : v1 (0x0)
                    Log ID    : EE:4B:BD:B7:75:CE:60:BA:E1:42:69:1F:AB:E1:9E:66:
                                A3:0F:7E:5F:B0:72:D8:83:00:C4:7B:89:7A:A8:FD:CB
                    Timestamp : Mar 23 22:19:01.535 2017 GMT
                    Extensions: none
                    Signature : ecdsa-with-SHA256
                                30:45:02:20:0D:A7:D1:36:DE:01:AE:4A:6E:E3:A9:9D:
                                7A:49:6E:73:9B:C1:C9:29:3A:C1:EC:68:DF:B6:AC:0E:
                                D9:03:5E:98:02:21:00:97:B2:53:9D:53:DD:98:57:1A:
                                BB:3C:0B:8E:03:44:48:C4:45:B6:7E:01:AF:39:BD:5C:
                                94:CF:25:B6:96:3D:A7
                Signed Certificate Timestamp:
                    Version   : v1 (0x0)
                    Log ID    : BB:D9:DF:BC:1F:8A:71:B5:93:94:23:97:AA:92:7B:47:
                                38:57:95:0A:AB:52:E8:1A:90:96:64:36:8E:1E:D1:85
                    Timestamp : Mar 23 22:19:01.521 2017 GMT
                    Extensions: none
                    Signature : ecdsa-with-SHA256
                                30:45:02:21:00:AA:AE:DB:AA:EF:52:7A:4C:CE:F0:28:
                                C5:9E:48:04:4E:75:36:BC:7F:7E:46:A0:B3:08:98:95:
                                CE:35:23:47:7D:02:20:38:DB:D2:BB:F5:47:E6:39:59:
                                D7:E3:C3:F9:BE:93:84:51:75:FA:95:7B:C2:9E:F0:AB:
                                EF:FC:C6:21:D4:32:5B
    Signature Algorithm: sha256WithRSAEncryption
         99:7e:d6:2f:ce:1b:a6:15:f5:15:b3:ef:f1:30:c1:1f:54:10:
         92:a4:8c:43:c0:bc:bd:a5:0d:00:53:e2:42:c1:85:6f:e5:a7:
         a9:41:99:4b:46:11:5a:dd:fd:e8:27:69:97:b6:3c:a6:0e:2a:
         30:db:33:53:be:83:b0:aa:08:89:04:7e:66:35:e5:5c:b3:2c:
         28:7f:a7:b1:e5:27:79:6d:81:26:89:ea:a0:55:51:70:10:cb:
         eb:43:59:6b:aa:52:b4:46:fd:d2:ff:89:16:8a:45:da:0e:bf:
         87:0d:53:ef:83:24:c5:17:ad:12:63:40:74:80:4d:bd:a4:c9:
         dd:74:d9:df:1c:61:02:0a:71:b0:93:24:2f:2d:a9:20:7a:43:
         86:44:11:58:8a:45:9b:d7:5c:e2:66:eb:a6:c6:f1:7c:a7:dc:
         dd:af:27:89:39:f7:c1:9a:99:c8:7f:34:7a:d9:39:73:83:cb:
         73:75:bc:16:b0:4e:a1:49:2d:09:12:8d:4e:3e:63:ff:f0:88:
         71:df:50:46:2b:a5:38:3d:db:38:08:97:29:64:de:cb:c7:eb:
         88:70:59:dd:62:dc:16:76:2d:30:6a:e3:a3:2f:40:a5:36:0f:
         cc:05:76:d5:e0:6e:04:40:3d:6a:21:5f:bf:4e:a3:a8:6c:d0:
         98:21:b9:bd


[ENG-2153] Add employer_id_number to guides

Description

Adds employer_id_number to list of token types
Removes impact level column to reduce noise (instead of updating / adding another column for default vs min impact levels)

Testing required outside of automated testing?

[x] Not Applicable

Screenshots (if appropriate):

Rollback / Rollforward Procedure

[x] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

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


Redirect joining nodes if they contact the wrong leader

Currently, we expect any node that joins an existing group (i.e. start up as a non-leader) to know the correct IP address of the current top-level group leader when it runs the Group constructor. If the joining node contacts a group member that is not the current leader, it will hang forever, because all nodes run the background thread that accepts incoming connections, but only the leader will actually respond to incoming connections (by proposing a new view and then sending it to the joiner).
Instead, it would be better if non-leader nodes responded to incoming connections by replying with the IP address of the current leader and then closing the connection, so that the node attempting to join could retry with the correct IP address.

This has been implemented as of 3bd69e94, which worked correctly after all.

@songweijia, this is what you wanted.


release: 1.0.0

Rename to AppWorks
Remove "Welcome" Page

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@1326550). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #2   +/-   ##
=======================================
  Coverage        ?   57.14%
=======================================
  Files           ?        1
  Lines           ?       70
  Branches        ?       18
=======================================
  Hits            ?       40
  Misses          ?       30
  Partials        ?        0

Continue to review full report at Codecov.

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


Spotify data missing

When requesting a Spotify track URL with LavaSrc, the album & artwork is always missing even though  Spotify's /tracks/ID endpoint does include the album & artwork for the album as seen below:

what version are you running?
did you try it with different tracks?

Just to be sure, where are you expecting the artwork URL & album?
Because v3 does not support album

I mean, you're using LavaSrc v3 with Lavalink v4
That ain't gonna work, I'm honestly surprised it even works
Use LavaSrc v4


redundant definition?

europa 2 - connectors.js
same js file
spotify - connectors.js
https://player.spotify.com/ redirects to https://play.spotify.com/

Yep, spotify-play.js is useless. Can't figure out why it's needed.
onair.evropa2.sk is unavailable for me. Maybe it's worth deleting it? Or is it unavailable just for me?
I can't listen to any music directly on onair.evropa2.cz. But it has redirects to youradio.cz. Don't sure if Evropa2 connector is useful.

onair.evropa2.sk is unavailable for me.

http://www.downforeveryoneorjustme.com/http://onair.evropa2.sk/

I can't listen to any music directly on onair.evropa2.cz. But it has redirects to youradio.cz. Don't sure if Evropa2 connector is useful.

works, but you have to disable ad blockers/social blockers

works, but you have to disable ad blockers/social blockers

Yes, after disabling adblock it started to work. In this case it's enough to drop onair.evropa2.sk from the list.

Yep, spotify-play.js spotify.js is useless. Can't figure out why it's needed.
When sites change urls, they often roll out the changes at different times in different locations.  At one point there was an overlap where both urls were valid.  If we can't be absolutely sure that it's not used in some local, there's really no issue in having an extra, unused domain remain.

The issue should be closed. It's resolved in #1030 and #1085.


Remove starrealms.rb

Homepage shows only a Steam link for OSX on a much higher version than the cask version.

Recommend removal

If there’s a checkbox you can’t complete for any reason, that's okay, just explain in detail why you weren’t able to do so.
After making all changes to the cask:

[ ] brew cask audit --download {{cask_file}} is error-free.
[ ] brew cask style --fix {{cask_file}} reports no offenses.
[ ] The commit message includes the cask’s name and version.

Thank you for the contribution. It was merged directly as 6498b966fe380bc29d9c2343406d522af5139ed1 to keep commit history cleaner. Your contribution is still credited to you.


MAILGUN_DOMAIN='mailgun domain' what will be the domain

I saw your config file[https://github.com/theoomoregbee/US-visa-appointment-notifier/blob/main/.env.example] line-15 asking for MAILGUN_DOMAIN='mailgun domain' but I dont know what value i put it there from the below mailgun info I have...
My mailgun account gave me the following:

`curl -s --user 'api:b84a-72f'
https://api.mailgun.net/v3/sandbox37****************22.mailgun.org/messages
-F from='Mailgun Sandbox<EMAIL_ADDRESS>-F to='Sam<EMAIL_ADDRESS>-F subject='Hello Sam'
-F text='Congratulations Sam, you just sent an email with Mailgun!  You are truly awesome!'

Your guidance will be appreciated. Thank you in advance

The domain that  I used I found under Sending->Domains.  It is the sandboxXXX.mailgun.org value.

Thanks, @jluiz20.

Thanks @jluiz20


Remove the need for setting CORS headers

Issue extracted from https://github.com/ipfs-shipyard/ipfs-desktop/pull/722#pullrequestreview-181190975

Summary
Right now IPFS Desktop is automatically adding CORS headers to $IPFS_PATH/config:
https://github.com/ipfs-shipyard/ipfs-desktop/blob/8f912ce816e2cd2e1c634fe8cdab54e2eb37cedf/src/utils/daemon.js#L59-L64
Without the above, Web UI won't load.
We should look into ways we can make it work without the need for touching API.HTTPHeaders, eg. see how IPFS Companion deals with the same problem.
Background Discussion
@olizilla asked:

I wonder how this could be abused. A fake scheme is a neat trick, but I don't know enough to reason about how it could be exploited if we added it to the list of allowed origins. I guess a site would have have been loaded from the webui:// scheme. What happens if a web-ext is allowed to registered itself as handling that scheme?
What are our other options here?
My main concern is about updating the users config for an external daemon. @lidel what do you think?

@lidel suggested:

Actually.. we have a lot of control over the browser (request headers etc) in IPFS Desktop, just like we do in IPFS Companion.  This means we should not need to set the CORS header in daemon.
Electron (Chromium engine) is adding Origin: null to fetch requests made from webui:// and internal contexts to HTTP API which acts as a sort-of-false-positive trigger for CORS validation, resulting in 403 Forbidden:

Note: IPFS Companion works around this by removing Origin header from requests sent to the API from js-ipfs-http-client running in its background page:

https://github.com/ipfs-shipyard/ipfs-companion/blob/v2.6.2/add-on/src/lib/ipfs-request.js#L107-L144

This makes those requests  "no longer CORS" in view of go-ipfs.
I believe if  we add similar fix to IPFS Desktop the need for origins.push(...) will disappear.

@olizilla perhaps we could make a proxy to communicate directly with the API on the main process and take advantage of the fact that IPFS Redux Bundle can use an window.ipfs object. Although, right now, it is disabled in Web UI.

AFAIK Electron is using postMessage-like interface for communication between processes.
Take a look at ipfs-postmsg-proxy, it solves serialization issues in ipfs-companion around window.ipfs in page context talking to API running in separate webextension process.

Although our solution might not be considered perfect, we don't need to set the CORS headers anymore. I'm closing this!


Added third argument to "is_subclass_of"

Added third argument to "is_subclass_of" (supported from PHP 5.3.9), which caused the following Code Smell message: ""Method call uses 3 parameters, but method signature uses 2 parameters".

 If not, please download the PDF from http://www.jetbrains.org/display/IJOS/Contributor+Agreement and then print it out, sign (mention you github account name there), scan and email to<EMAIL_ADDRESS>


ElectrumX server keeps crashing randomly

From version 1.15.0 ElectrumX server keeps crashing randomly (sometimes daily). If you need more info let me know.
Debian 10.4
Python 3.7.3
Jul 13 05:52:49 server1 electrumx_server[10865]: INFO:Prefetcher:cancelled; prefetcher stopping
Jul 13 05:52:49 server1 electrumx_server[10865]: INFO:SessionManager:closing down server for rpc://<IP_ADDRESS>:8000
Jul 13 05:52:49 server1 electrumx_server[10865]: INFO:SessionManager:closing down server for ssl://all_interfaces:50002
Jul 13 05:52:49 server1 electrumx_server[10865]: INFO:ElectrumX:[156216] disconnected whilst throttled
Jul 13 05:52:50 server1 electrumx_server[10865]: INFO:Controller:shutting down
Jul 13 05:52:50 server1 electrumx_server[10865]: INFO:Controller:shutdown complete
Jul 13 05:52:50 server1 electrumx_server[10865]: ERROR:electrumx:ElectrumX server terminated abnormally
Jul 13 05:52:50 server1 electrumx_server[10865]: Traceback (most recent call last):
Jul 13 05:52:50 server1 electrumx_server[10865]:   File "/home/electrumx/electrumx_server", line 35, in main
Jul 13 05:52:50 server1 electrumx_server[10865]:     asyncio.run(controller.run())
Jul 13 05:52:50 server1 electrumx_server[10865]:   File "/usr/lib/python3.7/asyncio/runners.py", line 43, in run
Jul 13 05:52:50 server1 electrumx_server[10865]:     return loop.run_until_complete(main)
Jul 13 05:52:50 server1 electrumx_server[10865]:   File "/usr/lib/python3.7/asyncio/base_events.py", line 584, in run_until_complete
Jul 13 05:52:50 server1 electrumx_server[10865]:     return future.result()
Jul 13 05:52:50 server1 electrumx_server[10865]:   File "/home/electrumx/electrumx/lib/server_base.py", line 125, in run
Jul 13 05:52:50 server1 electrumx_server[10865]:     await server_task
Jul 13 05:52:50 server1 electrumx_server[10865]:   File "/home/electrumx/electrumx/lib/server_base.py", line 98, in serve
Jul 13 05:52:50 server1 electrumx_server[10865]:     await self.serve(shutdown_event)
Jul 13 05:52:50 server1 electrumx_server[10865]:   File "/home/electrumx/electrumx/server/controller.py", line 134, in serve
Jul 13 05:52:50 server1 electrumx_server[10865]:     await group.spawn(wait_for_catchup())
Jul 13 05:52:50 server1 electrumx_server[10865]:   File "/usr/local/lib/python3.7/dist-packages/aiorpcx/curio.py", line 242, in aexit
Jul 13 05:52:50 server1 electrumx_server[10865]:     await self.join()
Jul 13 05:52:50 server1 electrumx_server[10865]:   File "/usr/local/lib/python3.7/dist-packages/aiorpcx/curio.py", line 211, in join
Jul 13 05:52:50 server1 electrumx_server[10865]:     raise task.exception()
Jul 13 05:52:50 server1 electrumx_server[10865]:   File "/home/electrumx/electrumx/server/block_processor.py", line 681, in fetch_and_process_blocks
Jul 13 05:52:50 server1 electrumx_server[10865]:     await group.spawn(self._process_prefetched_blocks())
Jul 13 05:52:50 server1 electrumx_server[10865]:   File "/usr/local/lib/python3.7/dist-packages/aiorpcx/curio.py", line 242, in aexit
Jul 13 05:52:50 server1 electrumx_server[10865]:     await self.join()
Jul 13 05:52:50 server1 electrumx_server[10865]:   File "/usr/local/lib/python3.7/dist-packages/aiorpcx/curio.py", line 211, in join
Jul 13 05:52:50 server1 electrumx_server[10865]:     raise task.exception()
Jul 13 05:52:50 server1 electrumx_server[10865]:   File "/home/electrumx/electrumx/server/block_processor.py", line 642, in _process_prefetched_blocks
Jul 13 05:52:50 server1 electrumx_server[10865]:     await self.check_and_advance_blocks(blocks)
Jul 13 05:52:50 server1 electrumx_server[10865]:   File "/home/electrumx/electrumx/server/block_processor.py", line 220, in check_and_advance_blocks
Jul 13 05:52:50 server1 electrumx_server[10865]:     await self._maybe_flush()
Jul 13 05:52:50 server1 electrumx_server[10865]:   File "/home/electrumx/electrumx/server/block_processor.py", line 354, in _maybe_flush
Jul 13 05:52:50 server1 electrumx_server[10865]:     await self.flush(True)
Jul 13 05:52:50 server1 electrumx_server[10865]:   File "/home/electrumx/electrumx/server/block_processor.py", line 348, in flush
Jul 13 05:52:50 server1 electrumx_server[10865]:     await self.run_in_thread_with_lock(flush)
Jul 13 05:52:50 server1 electrumx_server[10865]:   File "/home/electrumx/electrumx/server/block_processor.py", line 202, in run_in_thread_with_lock
Jul 13 05:52:50 server1 electrumx_server[10865]:     return await asyncio.shield(run_in_thread_locked())
Jul 13 05:52:50 server1 electrumx_server[10865]:   File "/home/electrumx/electrumx/server/block_processor.py", line 201, in run_in_thread_locked
Jul 13 05:52:50 server1 electrumx_server[10865]:     return await run_in_thread(func, *args)
Jul 13 05:52:50 server1 electrumx_server[10865]:   File "/usr/local/lib/python3.7/dist-packages/aiorpcx/curio.py", line 68, in run_in_thread
Jul 13 05:52:50 server1 electrumx_server[10865]:     return await get_event_loop().run_in_executor(None, func, *args)
Jul 13 05:52:50 server1 electrumx_server[10865]:   File "/usr/lib/python3.7/concurrent/futures/thread.py", line 57, in run
Jul 13 05:52:50 server1 electrumx_server[10865]:     result = self.fn(*self.args, **self.kwargs)
Jul 13 05:52:50 server1 electrumx_server[10865]:   File "/home/electrumx/electrumx/server/block_processor.py", line 347, in flush
Jul 13 05:52:50 server1 electrumx_server[10865]:     self.estimate_txs_remaining)
Jul 13 05:52:50 server1 electrumx_server[10865]:   File "/home/electrumx/electrumx/server/db.py", line 225, in flush_dbs
Jul 13 05:52:50 server1 electrumx_server[10865]:     self.flush_state(batch)
Jul 13 05:52:50 server1 electrumx_server[10865]:   File "plyvel/_plyvel.pyx", line 634, in plyvel._plyvel.WriteBatch.exit
Jul 13 05:52:50 server1 electrumx_server[10865]:   File "plyvel/_plyvel.pyx", line 617, in plyvel._plyvel.WriteBatch.write
Jul 13 05:52:50 server1 electrumx_server[10865]:   File "plyvel/_plyvel.pyx", line 91, in plyvel._plyvel.raise_for_status
Jul 13 05:52:50 server1 electrumx_server[10865]: plyvel._plyvel.CorruptionError: b'Corruption: corrupted compressed block contents'
Jul 13 05:52:51 server1 systemd[1]: electrumx.service: Succeeded.

This looks like there is something wrong with the data. Possibly it got corrupted on the disk. My guess is you will need to delete the data and reinitialize.

You can also theoretically try to repair the database. Change into your data directory and run:
python3 -c "import plyvel; plyvel.repair_db('hist')"
python3 -c "import plyvel; plyvel.repair_db('utxo')"

Thanks! I will try to repair the database and post the results here.

Repairing the database didn't help. It got stock (for more than 1 day) with:
Jul 15 14:15:38 server1 electrumx_server[491]: INFO:History:DB shut down uncleanly.  Scanning for excess history flushes...
I am now trying to reinitialize the database. It is still syncing since more than 40 hours. I will post the results after the sync is done.

"I will post the results after the sync is done."
No update since then, I assume this is resolved and not an electrumX issue but bad disk/hardware etc? Perhaps can be closed.

Sorry for not replying sooner, but the sync took a long time, also because it was crashing during the sync (there is another open issue for this #30) and I also did a full resync of bitcoind just to be sure. Now it works since about a week without a problem. I guess the problem was really the corrupt database. I will close this. Thanks for the help!


Make the ytdl-format flag usable (#27)

This is the PR relative to #27

Merged your PR everything seems good


Import with multiple Jsons

Hi,
I am using the Drawflow library and thank you for such a wonderful Library :)
I have a query related with Editor.Import functionality. Is there any way to import multiple jsons to the same editor? The Jsons which are already saved before.

Hello,
Thank you!
Only one json can be imported at a time.
You can import it as many times as you want.
If you want to import several json, you can transform-them before importing into one.
For this, I would use the uuid, since otherwise the id of the nodes is consecutive.
editor.useuuid = true;

Thank you for the response.
I have already tried the option you suggested. I am using uuid and transforming the Json before importing. It is working as expected.
Thank you once again


Make KARMABOT_TEST_MODE optional

I had to set it in UAT (and now PROD), would be nice to default it to False if not set.

#97 Done. Thx @bbelderbos


Add2 Blend Node in Animation Tree does not Add

Godot version
4.1 stable [970459615]
System information
Godot v4.1.stable.mono - Windows 10.0.19044 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2060 (NVIDIA; <IP_ADDRESS>4) - AMD Ryzen 9 5950X 16-Core Processor (32 Threads)
Issue description
the Add2 node appears to simply blend instead of add.
here is the blend happening in godot 4.1:
https://github.com/godotengine/godot/assets/98141558/57cdaddf-7f8c-41d1-81f2-7fc607fa8f75
here is what it looks like in blender:
https://github.com/godotengine/godot/assets/98141558/661d728f-e015-4fa5-b593-68eb5db58522
Steps to reproduce

create a simple FK rig in blender and create a base animation.
create a additive animation setting the track blend mode to add in blender and position bones and keyframe them to create the animation
export the both animation as replace in blender for export to gltf.
open the glb in godot and create a animation tree and assign the the animation player as the target
add a blend tree and add the animations to the tree
add and Add2 node and blend the 2 animations
observe the issue

Minimal reproduction project
ive attached a small reproduction project with a demo glb containing simple animations
blendbug.zip

I suspect you need to filter out the bones to operate on, which Blended might do automatically

Yes, I do filter them. even if i didnt filter them it should not do that, there are no keyframes for the other bones.

sad to see this was never fixed


clickhouse: <IP_ADDRESS> -> <IP_ADDRESS>

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/clickhouse/versions.
meta.description for clickhouse is: "Column-oriented database management system"
meta.homepage for clickhouse is: "https://clickhouse.tech/"
meta.changelog for clickhouse is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/qawl8zf05gaq8xig096hyxxafnakvkkm-clickhouse-<IP_ADDRESS>/bin/clickhouse-library-bridge had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/qawl8zf05gaq8xig096hyxxafnakvkkm-clickhouse-<IP_ADDRESS>/bin/clickhouse-local had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/qawl8zf05gaq8xig096hyxxafnakvkkm-clickhouse-<IP_ADDRESS>/bin/clickhouse-compressor had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/qawl8zf05gaq8xig096hyxxafnakvkkm-clickhouse-<IP_ADDRESS>/bin/clickhouse-copier had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/qawl8zf05gaq8xig096hyxxafnakvkkm-clickhouse-<IP_ADDRESS>/bin/clickhouse-keeper had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/qawl8zf05gaq8xig096hyxxafnakvkkm-clickhouse-<IP_ADDRESS>/bin/clickhouse-odbc-bridge had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/qawl8zf05gaq8xig096hyxxafnakvkkm-clickhouse-<IP_ADDRESS>/bin/clickhouse-git-import had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/qawl8zf05gaq8xig096hyxxafnakvkkm-clickhouse-<IP_ADDRESS>/bin/clickhouse-static-files-disk-uploader had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/qawl8zf05gaq8xig096hyxxafnakvkkm-clickhouse-<IP_ADDRESS>/bin/clickhouse-keeper-converter had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/qawl8zf05gaq8xig096hyxxafnakvkkm-clickhouse-<IP_ADDRESS>/bin/clickhouse-client had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/qawl8zf05gaq8xig096hyxxafnakvkkm-clickhouse-<IP_ADDRESS>/bin/clickhouse-extract-from-config had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/qawl8zf05gaq8xig096hyxxafnakvkkm-clickhouse-<IP_ADDRESS>/bin/clickhouse-obfuscator had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/qawl8zf05gaq8xig096hyxxafnakvkkm-clickhouse-<IP_ADDRESS>/bin/clickhouse-server had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/qawl8zf05gaq8xig096hyxxafnakvkkm-clickhouse-<IP_ADDRESS>/bin/clickhouse-format had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/qawl8zf05gaq8xig096hyxxafnakvkkm-clickhouse-<IP_ADDRESS>/bin/clickhouse had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/qawl8zf05gaq8xig096hyxxafnakvkkm-clickhouse-<IP_ADDRESS>/bin/clickhouse-report had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/qawl8zf05gaq8xig096hyxxafnakvkkm-clickhouse-<IP_ADDRESS>/bin/clickhouse-benchmark had a zero exit code or showed the expected version
0 of 17 passed binary check by having a zero exit code.
0 of 17 passed binary check by having the new version present in output.
found <IP_ADDRESS> with grep in /nix/store/qawl8zf05gaq8xig096hyxxafnakvkkm-clickhouse-<IP_ADDRESS>
found <IP_ADDRESS> in filename of file in /nix/store/qawl8zf05gaq8xig096hyxxafnakvkkm-clickhouse-<IP_ADDRESS>

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
0 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
clickhouse

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qawl8zf05gaq8xig096hyxxafnakvkkm-clickhouse-<IP_ADDRESS> \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A clickhouse https://github.com/r-ryantm/nixpkgs/archive/b2201f0143fccf7e511d672870c6e99830b8b921.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qawl8zf05gaq8xig096hyxxafnakvkkm-clickhouse-<IP_ADDRESS>
ls -la /nix/store/qawl8zf05gaq8xig096hyxxafnakvkkm-clickhouse-<IP_ADDRESS>/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

clickhouse

Maintainer pings
cc @orivej for testing.

<IP_ADDRESS>9 (or newer) is already out


Can't work with input folder

I set input as my image folder , but its show wrong why ?

Add the path to the parent folder of all image subfolders. This application will automatically create an output subfolder based on the names of your dataset folders, so setting the parent folder path as the input allows it to locate each subfolder and perform efficiently without hesitation


Light client API standardization

The light client syncing API should be standardized and available as a REST API.
Build consensus, write specifications, implement pocs, etc to bring the syncing API to standardization and production.

Create buy-in for other clients to implement. Link to the PR.

Reference: https://github.com/ethereum/beacon-APIs/pull/181

It has been identified in the March 29 call and recently on Twitter that we need should tweak the API to allow for syncing to finalized or to head. cc: @wemeetagain @dapplion

Can we close this for #3952 @wemeetagain ?


gl_generator: update xml-rs to v7 and publish v0.5.6

Bumps bitflags to v1.
Edit: Looks like xml-rs is about to drop bitflags, possibly undoing previous version break(?) Best not to merge yet.

Wouuups I'm sorry, I opened #430 after you and it got merged :/

@Eijebong no problem lol


Prefixed components and SvelteKit's routes being listed as able to be imported.

Hi there! Recently, I've started using this plugin on my SvelteKit projects. And it seems odd that components dedicated to routing or simply named with + are listed as being possibly imported.
It's not possible to import said components because they aren't able to be call on the HTML, but maybe could cause problems in the future?
Also, because of this, the .d.ts file has it syntax highlight broken, at least on VS Code. But it doesn't seem to break its functionality:

I tried using a regex to exclude the SvelteKit's routes from being transformed and listed, but doing this removed the ability to auto-import components in said routes.
Maybe just removing components with special characters such as + from the .d.ts file could be a solution? If there's no issue, I could create a new Pull Request, [trying] fixing it this way.
Knowing it is already impossible to have a <+component/> in the HTML without a syntax error. At least it would remove the confusion for any new developer using or contributing to a repository using the plugin.

Temp fix?
If anyone also had this issue, a sort of “fix” that I used is transforming/removing the path from said components. So it is more explicit that these can't and shouldn't be imported:

/* vite.config.js */
import path from 'node:path';

export default defineConfig({
  plugins: [
    SvelteImport({
      include: [
        /\.svelte/,
        /\.svelte\?svelte/,
      ],
      importPathTransform: (importPath) => {
        // Probably it's better to replace it with a regex of special characters
        if (getFileName(importPath).includes('+'))
          return '';
        else return importPath;
      },
    }),
    // ...
  ]
});

function getFileName(filePath: string): string {
  return path.basename(filePath).replace(path.extname(filePath), '');
}

Result .d.ts file:
// generated by unplugin-svelte-components
// We suggest you to commit this file into source control
declare global {
    const "+layout": typeof import("")["default"]
    const "+page": typeof import("")["default"]

Hi @Guz013, sorry for the delay.
I never thought anyone would tell this plugin to auto import components from src/routes folder or name there components with special characters.
I did release new version that should fix the issue, please try it and let me know if it works for you.
In the new version if you have components that have special characters in their names, the special characters will be removed and the component will be imported without them, for example if you have a component named +Component.svelte it will be imported as Component.svelte and if you have a component named @Component.svelte it will be imported as Component.svelte and so on.
For the src/routes folder case, now +page.svelte, +layout.svelte and +error.svelte will be ignored and not imported, the reason why it was not originally ignored is because when you place a component in src/routes these components are local components to that page and they are not global components, and in case if your component is a global component mostly like you will place it in src/components or src/lib folder, but I understand that you may want to place your global components in src/routes folder and that's why in the new version I added the ability to ignore page,layout and error files in src/routes folder.

Thank you very much for the fast response and fix! I'll upgrade and try this afternoon and notify you if it worked.
I stumbled on this issue before because I actually use this plugin to import everything from src/. Most of the times I've a lot of single-use-components for just one page/route, that it feels strange placing them on something like src/lib or src/components. And auto-importing them, besides making the code looks cleaner without the imports, also helps if I want to move said components to another directory.
So thank you very much! I'll update you soon when I'm able to test it.

@Mohamed-Kaizen, it's fixed! The SvelteKit's routes are being as you said, and components with special characters are being renamed.
But it seems that I encountered another issue, unfortunately, but I'm not totally sure if it is on my end or the plugin's. I'll try to replicate it on a dedicated environment, and create a new issue if necessary. Thanks in advance already!

Created issue #16 related to this.
Sorry for the inconvenience of two issues in a row, this plugin is really useful to me. I really appreciate that you created it, and end up using it in all my current projects, and really want to add it to a template of my workflow. If necessary or there's no issue, I would like to contribute to it somehow.


Better handling for empty places material search

Stops sending places material search events for searches that end up erroring
Adds PlacesList::MaterialSearch::Empty to separate valid from invalid/empty searches
Handles locations.items coming back undefined (https://wrap.sentry.io/issues/5329698806/?alert_rule_id=15082034&alert_type=issue&notification_uuid=96340b34-64da-4370-b3f2-e36a0b939fcd&project=4506864957194240&referrer=slack)

:tada: This PR is included in version 1.39.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Inconsistent results of IWSLT data preprocessing between fairseq 0.6 and 0.9

❓ Questions and Help
What is your question?
I am running two versions of faiseq for neural machine translation, one is 0.6 and the other is 0.9, and find the data preprocessing results of IWSLT (for NMT) are inconsistent. I prepare the dataset following the guide in ./examples/translation/README.md, which includes:

./examples/translation/prepare-iwslt14.sh (for IWSLT-14)
data binarization.

But I find the results of two fairseq versions are different. For example:

IWSLT fairseq-0.6 produces 42MB binarized data, but 21MB for fairseq 0.9.

IWSLT processed by fairseq 0.6: 42MB

IWSLT processed by fairseq 0.9: 21MB

fairseq Version: fairseq 0.6 & fairseq 0.9
PyTorch Version 1.5.1
How you installed fairseq (pip, source): Yes. pip install . --editable
Python version: 3.7.4

This is expected. Newer versions of fairseq use a more efficient mmap data format that requires less disk space.


Discuss removing Collection

In a recent JFX, while discussing #15  we decided to

Create an issue for discussing removal of collections

Maybe someone can recap what the differences between Collection, Label and Vocab are

It might make sense to include Source in that recap, too.
Within our project, we orginally assumed we should use Collection to mark data imports done via scripts (because manual user input via forms is given a default value for Collection, and we needed to be able to target individual imports).
We switched to Source  after asking about the difference between Source and Collection here, partly also because Source cannot be accessed and changed by users, but we were not given a definite answer (and I still don't really know what all of the fields are meant to be used for...).
Relevant quotes from that MM convo:

in [our project] e.g. we use collection to mark entities ingested/created by different projects (...); source was once meant to persist information of the source(file) an entity was imported from

incorrectly is relativ, I'd say as long your usage fits your needs you use it perfectly correct


CSMAALOHA (Throughput, PDR)

Hi. I was running the test code of CSMA ALOHA. But I am getting this kind of output. Here for node 0 all the throughput remains same. for node 1 is also like this. What supposed to be the reason? As each link is different, the throughput should be different. Isn't it? Also, I got 104 Packet Delivery ratio in previous run. I do not know whether that is the correct one or not.
Also, how we can fix the position of the nodes? any suggestion would be helpful.

This seems not to be a bug, but rather a support request to this is not the right place. The numbers are correct


Links not working

Hi,
almost all links mentioned in README.md are not working (return 404):

https://developer.android.com/reference/android/hardware/FingerprintManager.AuthenticationCallback#onAuthenticationSucceeded().html
https://developer.android.com/reference/android/hardware/FingerprintManager/index.html#authenticate().html
https://developer.android.com/reference/android/security/KeyGenParameterSpec.Builder#setUserAuthenticationRequired().html
https://developer.android.com/reference/android/security/KeyGenParameterSpec.html

Thanks for the report. Javadoc references introduced in M preview are not live yet.
Once published, I'll check again the links are correct.

Now Android 23 is live, please update the above links.

Thanks for the reminder.
The links will be fixed in the next push.


Fix cloudsmith package directory structure

clousmith packages became malformed with the switch to CMake because the DESTDIR provided to the Makefile did not include the version tag directory.

@Theodus Thinking about this a bit more, this feels like its getting really oddly complicated because it has pushed the version issue that we were able to sidestep before to the side.
I think this has made it worse than it was.
I think we either need to not use DESTDIR so we can get the version directory automatically made (but install to a different prefix) like we had before.
Or
Well, I'm not sure what the OR is... I think we need the above. Otherwise we end up with weird versioning.
With the nightlies, it will use the version from PONY_VERSION.
With releases, it won't. It will be in a directory named after PONY_VERSION but ponyc --version iw going to return a different value. That's pretty broken in my mind.
Prior to cmake change, we used...
```make install prefix=${BUILD_PREFIX} default_pic=${PIC} arch=${ARCH} ``
and that resulted in no problem because, we were overriding the VERSION and it was placing the correct version directory install path.
I think DESTDIR not doing that is problematic. We can't be doing it like this PR is, its basically reaching inside an abstraction (version handling inside of the Makefile) and messing with it.
The "version" directory should match the output of ponyc --version. This PR doesn't accomplish that.
I think the correct change is to switch from DESTDIR to setting prefix again with no other changes and then everything else should work fine. As well as setting symlink=no where it was before the cmake change.
( see from line 8 to 28 in the Makefile for the rest of my comment )
for nightlies version will be set which means that tag in the makefile will get set to version but either way "tag" will still be the version we use because the Makefile controls that.
 20 symlink := yes
 21 ifdef DESTDIR
 22   prefix := $(DESTDIR)
 23   ponydir := $(prefix)
 24   symlink := no
 25 else
 26   prefix ?= /usr/local
 27   ponydir ?= $(prefix)/lib/pony/$(tag)
 28 endif

See previously we set symlink and prefix directly which means that ponydir was correctly set to $(prefix)/lib/pony/$(tag). The change to DESTDIR from prefix isn't what we wanted.
So, I think the change should be back to using prefix and symlink=no where it was prior to the cmake changes.
Agree? Otherwise, I think we need to pull things apart some more because DESTDIR doesn't do what we want. What DESTDIR does is reasonable, but it isn't what we want when packaging up for CLOUDSMITH releases.

@SeanTAllen I agree.

Closing in favor of #3473


Maven Plugin for Service Proxy

We wanted to run service-proxy in our Maven project, and decided to write this initial plugin.
It works fine for us so far. We run it in isolation from the rest of the plugins.
Please review it and suggest anything you might find inconvenient.
Thank you!

Hi @rydnr,
great contribution. The maven plugin will help me a lot for testing. I am wondering if we should include the plugin into Membrane core or give it a own repository as it is isolated and only depends on Membrane core. We can create the repo or you can do it also on github and we link from the documentation to the repo. It would be great if we can use some lines from your README for that.

The advantage of merging it into the main repo is that we can detect breaking API changes more easily concerning the plugin. (We haven't declared what is public API, and we frequently break some corner during refactoring.)

For that we have continuous Integration
Von meinem iPhone gesendet

Am 19.04.2016 um 08:18 schrieb Tobias Polley<EMAIL_ADDRESS>The advantage of merging it into the main repo is that we can detect breaking API changes more easily concerning the plugin. (We haven't declared what is public API, and we frequently break some corner during refactoring.)
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub

This effectively has been merged in August of 2016.